hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
88525ca373d6c27ca925fc02f42c683a | 23.007 | 20.2.6 BM-SC functionality | |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 20.2.6.1 SGmb path failure | In deployments without a Diameter Agent between the BM-SC and the MBMS GW, the BM-SC shall detect an SGmb path failure using either:
- mechanisms as specified in the Diameter Base Protocol (e.g. transport connection failure, MBMS GW peer not responding, Diameter Device-Watchdog-Request and Device-Watchdog-Answer messag... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 20.2.6.2 MB2-C path failure | In deployments without a Diameter Agent between the BM-SC and the GCS AS, the BM-SC shall detect an MB2-C path failure using either:
- mechanisms as specified in the Diameter Base Protocol (e.g. transport connection failure, GCS AS peer not responding, Diameter Device-Watchdog-Request and Device-Watchdog-Answer message... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 20.2.7 PGW functionality | |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 20.2.7.1 S5 path failure | The PGW may support invoking the PGW triggered SGW restoration procedure (see clause 27.2.3) when detecting a path failure to an SGW (see clause 20.2.1). If so, after detecting a path failure to an SGW, the PGW should maintain the S5 bearer contexts eligible for restoration and proceed with the PGW triggered SGW restor... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 20.2.8 GCS AS functionality | |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 20.2.8.1 MB2-C path failure | In deployments without a Diameter Agent between the BM-SC and the GCS AS, the GCS AS shall detect an MB2-C path failure using either:
- mechanisms as specified in the Diameter Base Protocol (e.g. transport connection failure, BM-SC peer not responding, Diameter Device-Watchdog-Request and Device-Watchdog-Answer message... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 20.2.9 Sx interface functionality | |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 20.2.9.1 Sxa path failure | If the path to the SGW-U is down, the SGW-C should handle this as SGW-U Failure without Restart, see clause 16.1A.4.
If the path to the SGW-C is down, the SGW-U should handle this as SGW-C Failure without Restart, see clause 16.1A.3. |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 20.2.9.2 Sxb path failure | If the path to the PGW-U is down, the PGW-C should handle this as PGW-U Failure without Restart, see clause 17.1A.4.
If the path to the PGW-C is down, the PGW-U should handle this as PGW-C Failure without Restart, see clause 17.1A.3. |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 20.3 User plane path failure detection and handling | |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 20.3.1 General | GTP-U entities shall support detection of path failure by using Echo Request / Echo Response messages in the following way. A path counter shall be reset each time an Echo Response is received on the path and incremented when the T3-RESPONSE timer expires for any Echo Request message sent on the path. The path shall be... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 20.3.2 MBMS GW functionality | |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 20.3.2.1 SGi-mb path failure | An MBMS GW may support the detection of an SGi-mb path failure.
NOTE 1: How an MBMS GW detects an SGi-mb path failure is implementation specific. E.g. an MBMS GW can monitor the receipt of downlink user plane from the BM-SC (synchronization sequences are transmitted continuously e.g. in case of MBSFN transmissions, eve... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 20.3.3 BM-SC functionality | |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 20.3.3.1 SGi-mb path failure | Upon receipt of a Session Termination Request message from an MBMS GW with a terminating cause signalling a user plane failure, the BM-SC may attempt to re-establish the MBMS session via the same MBMS GW (using different user plane resources over SGi-mb) or an alternative MBMS GW.
When re-establishing the MBMS session,... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 20.3.4 With Control and User plane Separation of SGW or PGW nodes | With a split SGW or PGW (see 3GPP TS 23.214 [42]), user plane path failure detection and handling shall be supported as specified in clause 20.3.1 with the following additional requirements:
- upon detecting a GTP-U user plane path failure, the SGW-U or PGW-U shall report the user plane path failure to the SGW-C or PGW... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 20.3.5 SGW functionality | |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 20.3.5.1 S1-U path failure | An SGW, with or without CUPS support, may optionally support the following S1-U path failure notification feature.
If the feature is supported and deployed in the network, after detecting a S1-U user plane path failure:
- If the SGW decides to keep the bearer contexts associated with the failed path (e.g. when the oper... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 20.3.6 MME functionality | |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 20.3.6.1 S1-U path failure | An MME may optionally support the following S1-U path failure notification feature.
If the feature is supported and deployed in the network, after receiving the cause code "S1-U Path Failure" in a Create Session Response or a Modify Bearer Response or a Modify Access Bearer Response or a Downlink Data Notification or a... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 21 Error Indication handling | |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 21.1 General | The following clauses specify a network element behaviour, if it receives a GTPv1-U Error Indication message. The reception of the message triggers a node internal procedure and/or a Control Plane procedure (GTPv1-C, GTPv2, RANAP, S1-AP).
For the PMIP based S5/S8 interface, an error in the form of an ICMP message is us... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 21.2 GGSN | GTP error indication message shall be handled as follows:
- If the GGSN receives a GTP error indication for a PDP context that has the DTI flag set (i.e. from an RNC), the GGSN should not delete the associated PDP context but mark it as invalid. Any subsequent packets arriving for an invalid PDP context should be disca... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 21.3 Gn/Gp SGSN | GTP error indication message shall be handled as follows:
- If the SGSN receives a GTP error indication from a GGSN, the SGSN shall delete its PDP context and may notify the Operation and Maintenance network element. Additionally it shall send a Deactivate PDP Context Request message to the MS with cause "re-activation... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 21.4 S4 SGSN | GTP error indication message shall be handled as follows:
- If the S4-SGSN receives a GTP error indication from a SGW, the S4-SGSN shall delete its Bearer context and may notify the Operation and Maintenance network element. Additionally it shall send a Deactivate PDP Context Request message to the MS with cause "re-ac... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 21.5 RNC or NodeB | GTP error indication message shall be handled as follows:
- When the RNC receives GTP error indication from the SGSN, it shall initiate the RAB Release procedure with the error cause "GTP Resources Unavailable" and shall immediately locally release the RAB (i.e. without waiting for a response from the SGSN).
- If the R... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 21.6 eNodeB | GTP error indication message shall be handled as follows:
- If the eNodeB receives a GTP error indication from the SGW over an S1-U tunnel not doing indirect forwarding, it shall initiate the E-RAB Release procedure and immediately locally release the E-RAB (i.e. without waiting for a response from the MME). If the MME... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 21.7 SGW | GTP error indication message shall be handled as follows:
- For an 'Active' mode UE having a user plane connection with an RNC, i.e. SGW has F-TEIDs assigned by RNC for user plane for the UE,when the SGW receives a GTP Error Indication for a Bearer Context that has the DTI flag set (i.e. from an RNC), the SGW should no... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 21.8 PGW | GTP error indication message shall be handled as follows:
- If the PGW receives a GTP error indication from a SGW/a TWAN /an ePDG for the bearer other than the default bearer, the PGW shall delete its Bearer context and may notify the Operation and Maintenance network element.
- If the PGW receives a GTP error indicati... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 21.9 MBMS GW | GTP Error Indication message shall be handled as follows:
- If the MBMS GW receives a GTP Error Indication from a SGSN, the MBMS GW shall delete its Bearer context and may notify the Operation and Maintenance network element. |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 21.10 ePDG | GTP error indication message shall be handled as follows:
- If the ePDG receives a GTP error indication from a PGW for the bearer other than the default bearer, the ePDG shall delete its Bearer context and may notify the Operation and Maintenance network element.
- If the ePDG receives a GTP error indication from a PGW... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 21.11 TWAN | GTP error indication message shall be handled as follows:
- If the TWAN receives a GTP error indication from a PGW for the bearer other than the default bearer, the TWAN shall delete its Bearer context and may notify the Operation and Maintenance network element.
- If the TWAN receives a GTP error indication from a PGW... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 21.12 MME | GTP error indication message shall be handled as follows:
- If the MME receives a GTP error indication from an SGW, the MME shall delete its Bearer context and may notify the Operation and Maintenance network element. Additionally the MME shall deactivate the corresponding PDN connection towards the UE with the cause "... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 22 Downlink Data Notification Handling at MME/S4 SGSN | If the MME/S4 SGSN receives a Downlink Data Notification message from the SGW as a result of the SGW having received an Error Indication message from the eNodeB/RNC or S4-SGSN over S4 User Plane, the MME/S4 SGSN should perform the following:
- If the UE is in IDLE state, upon receipt of the Downlink Data Notification m... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 23 General partial failure handling procedures | The partial failure handling is an optional feature for MME, SGW, ePDG, TWAN and PGW. Partial failure handling is an optional feature between SGW-C, PGW-C, SGW-U and PGW-U for split SGW and PGW (see 3GPP TS 23.214 [42]).
For split SGW and PGW, the description in this clause related to SGW applies to SGW-C and PGW appli... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 24 Restoration of data in the PCRF | |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 24.1 Restart of the PCRF | |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 24.1.0 PCRF Restart | PCRF storage of PCC contexts is volatile. When a PCRF fails, the PCC contexts and Diameter sessions affected by the failure are lost in the PCRF.
When a PCRF receives a non-initial message for which no Diameter session exists, it shall discard the message and return a Diameter error indication to the originating PCRF c... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 25 Network triggered service restoration procedure | |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 25.1 General | The network triggered service restoration procedure is an optional feature for the MME, S4-SGSN and SGW. A node that supports this feature shall support the network triggered service restoration procedure without ISR as specified in clause 25.2 and the network triggered service restoration procedure with ISR as specifi... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 25.2 Network triggered service restoration procedure without ISR | |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 25.2.1 General | The following requirements shall apply if the MME or S4-SGSN and the SGW support this feature.
If an SGW detects that an MME or S4-SGSN has restarted (see clause 18 "GTP-C based restart procedures"), instead of removing all the resources associated with the peer node, the SGW shall maintain the PDN connection table dat... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 25.2.2 SGW procedure | Upon receipt of the first downlink user plane or control plane packet on a maintained S5/S8 bearer or PCC signalling from PCRF, the SGW shall immediately send a Downlink Data Notification message including the IMSI to the respective MME or S4-SGSN. In addition, depending on the received downlink packet type the SGW sha... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 25.2.3 MME/SGSN procedure | Upon receipt of a Downlink Data Notification message including the IMSI, the MME or S4-SGSN shall respond to the SGW with a Downlink Data Notification Acknowledge message and should page and force the UE to re-attach to the network. The paging area and subscriber's identity i.e. IMSI or S-TMSI/P-TMSI used during the pa... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 25.3 Network triggered service restoration procedure with ISR | |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 25.3.1 General | The following requirements shall apply if the involved MME, S4-SGSN and SGW support the ISR feature and the network triggered service restoration feature.
NOTE: The procedure in this clause does not consider the case where one of ISR associated nodes, i.e. the MME or the S4-SGSN, does not support the network triggered ... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 25.3.2 SGW procedure | If an SGW detects that an ISR associated CN node (i.e. MME or S4-SGSN) has restarted (see clause 18), the SGW shall maintain all the PDN connection table data and MM bearer contexts associated with the non-failed and the restarted ISR associated nodes, and start a timer controlling the maximum duration during which the... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 25.3.3 MME/S4-SGSN procedure | If an MME/S4-SGSN detects a restart of an ISR associated counterpart (see clause 18), the MME/S4-SGSN shall wait for the next RAU/TAU procedure to deactivate ISR.
NOTE: As an implementation option, an MME/S4-SGSN may internally mark the ISR as not active, but this should not be visible in messages sent to the SGW.
The ... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 26 Mobile terminated CS service delivery via an alternative MME in MME pool | This procedure is an optional feature for VLR and MME. It enables the network to continue delivering mobile terminated CS services to UEs via an alternative MME in the MME pool where the UE is located when the MME to which the UE was registered fails without restart or fails for a long duration.
NOTE 1: UEs in idle mod... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 27 Restoration of PDN connections after an SGW failure | |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 27.1 General | The procedures specified in this clause enable to restore in the EPC the PDN connections affected by an SGW failure with or without restart, and thus to resume delivery of downlink data towards the UE with minimum service interruption and with minimal signalling in the network.
All the procedures specified in this clau... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 27.2 Restoration of PDN connections after an SGW failure for UEs without ISR | |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 27.2.1 General | The PGW triggered SGW restoration procedure is an optional add-on feature for the MME/S4-SGSN, SGW and PGW on top of the MME/S4-SGSN triggered SGW restoration procedure as specified in clause 27.2.2. A node that supports the PGW triggered SGW restoration procedure shall support the requirements specified in clause 27.2... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 27.2.2 MME/S4-SGSN triggered SGW restoration | |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 27.2.2.1 General | The following requirements shall apply if the MME/S4-SGSN, the SGW, the PGW, and the PCRF support this feature.
The MME/S4-SGSN, PGW, and PCRF for PMIP based S5, shall know by local configuration whether this MME/S4-SGSN triggered SGW restoration procedure is supported in the PLMN, i.e. by peer PGWs, PCRFs and MME/S4-S... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 27.2.2.2 MME/S4-SGSN procedure | After detecting an SGW failure, the MME/S4-SGSN should attempt to restore the PDN connections eligible for restoration for all the UEs affected by the SGW failure, i.e. including UEs in ECM_IDLE / PMM-IDLE / GPRS STANDBY not engaged in any Service Request, or Connection Resume procedure or other mobility procedure. The... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 27.2.2.3 PGW procedure | The PGW shall maintain the PDN connections affected by the SGW failure and eligible for restoration for an operator configurable period (T-Release-PDN timer), as specified in clause 27.2.2.1.
The PGW should maintain the GBR bearers of the PDN connections eligible for restoration for an operator configurable period (T-R... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 27.2.2.4 PCRF procedure | If the PGW rejects an IP-CAN session modification procedure with the rejection cause as specified in clause 27.2.2.3, the PCRF should maintain the corresponding IP-CAN session and refrain from sending any further IP-CAN session modification request to the PGW until being notified by the PGW that the PDN connection is r... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 27.2.2.5 SGW procedure | After the SGW restarts, the SGW shall not send Error indication message for a configurable period when the SGW receives a GTP-U PDU for which no Bearer context exists.
NOTE: The period needs to be longer than the time required for the peer node to detect the restart of the SGW, e.g. the interval between two echo reques... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 27.2.3 PGW triggered SGW restoration | |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 27.2.3.1 General | The following requirements shall apply if the MME/S4-SGSN, the SGW and the PGW support this feature.
NOTE: The PGW triggered SGW restoration procedure does not require any further requirements from the PCRF than those already specified for the MME/S4-SGSN triggered SGW restoration procedure in clause 27.2.2.1.
The PGW ... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 27.2.3.2 MME/S4-SGSN procedure | During normal mode of operation (i.e. before SGW failure with/without restart):
The MME/S4-SGSN supporting the PGW triggered SGW restoration procedure shall include the MME/S4-SGSN identifier IE in existing signalling over the S11/S4 interface, i.e. in
- Create Session Request messages during an E-UTRAN Initial Attach,... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 27.2.3.3 SGW procedure | During normal mode of operation (i.e. before SGW failure with/without restart):
The SGW shall forward the MME/S4-SGSN identifier IE to the PGW in existing signalling over the S5 interface if it is received over S11/S4 interface.
During SGW restoration procedure:
Upon receipt of a PGW Downlink Triggering Notification me... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 27.2.3.4 PGW procedure | During normal mode of operation (i.e. before SGW failure with/without restart):
The PGW shall store the MME/S4-SGSN identifier received in the last Create Session Request or Modify Bearer Request message (for GTP based S5) or Proxy Binding Update (for PMIP based S5) per PDN connection. If the PGW receives a Modify Bear... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 27.3 Restoration of PDN connections after an SGW failure for UEs with ISR | |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 27.3.1 MME/S4-SGSN triggered SGW restoration for UEs with ISR | |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 27.3.1.1 General | The requirement specified in clause 27.3.1.2 shall apply on top of the MME/S4-SGSN triggered SGW restoration procedure specified in clause 27.2.2 and the involved MME and S4-SGSN additionally support the ISR feature.
NOTE: The procedure in this clause does not consider the case where one of ISR associated nodes, i.e. t... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 27.3.1.2 MME/S4-SGSN procedure | The MME/S4-SGSN shall restore the PDN connections of the affected UEs after the SGW failure as follows:
1) for UEs initiating an intra MME/S4-SGSN TAU/RAU procedure:
- the MME/S4 SGSN shall perform the SGW relocation procedure as specified in clause 27.2.2, and inform the UE in the related TAU/RAU Accept message to dis... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 27.3.2 PGW triggered SGW restoration for UEs with ISR | |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 27.3.2.1 General | The requirement specified in clause 27.3.2.2 shall apply on top of the PGW triggered SGW restoration procedure specified in clause 27.2.3 and the involved MME and S4-SGSN additionally support the ISR feature.
NOTE: The procedure in this clause does not consider the case where one of ISR associated nodes, i.e. the MME o... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 27.3.2.2 MME/S4-SGSN procedure | If the MME/S4-SGSN receives a PGW Downlink Triggering Notification message containing MME/S4-SGSN Identifier from the SGW for those UEs affected by the failed SGW, the MME/S4-SGSN shall behave as specified in clause 27.2.3.2 and additionally send ISR Status Indication message with "Paging Indication" over the S3 interf... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 28 Restoration of data in the CSS | |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 28.1 Restart of the CSS | The periodic backup of CSS data to non-volatile storage is mandatory.
When a CSS restarts after failure it shall perform the following actions for the subscriber data records that have been affected by the CSS fault:
- reload all data from the non-volatile back-up;
- send a "Reset" message to each VLR where one or more... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 29 MBMS Heartbeat procedure | The BM-SC, MBMS GW and GCS AS may support the MBMS Heartbeat procedure over the SGmb or MB2-C reference point to probe the liveliness and detect the restart of a peer MBMS node.
This procedure is optional to support and use for MBMS deployments without an intermediate Diameter Agent between the BM-SC and the MBMS GW or... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 30 Restoration of the SCEF | |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 30.1 Restart of the SCEF | When an SCEF restarts after failure and has lost all or parts of his data, it shall reply to a report from MME, SGSN or HSS containing a SCEF reference ID for which it has no data with an error cause "SCEF_REFERENCE_ID_UNKNOWN" in the reply indicating that the SCEF reference ID provided in the message does not exist in... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 30.1.1 Mobile Originated NIDD procedure | During the Mobile Originated NIDD procedure, if the MME receives a MO-Data-Answer from the SCEF with a failure cause that UE cannot be found, the MME shall deactivate the corresponding PDN connection towards the UE with the cause "re-activation required", or initiate an explicit detach procedure with reattached require... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 31 Restoration of PDN connections after a PGW-C/SMF change | |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 31.1 General | The procedure specified in this clause enables to restore in the EPC the PDN connections affected by an PGW-C/SMF failure with or without restart or scale-in operation, and thus to maintain the UE connectivity to the PDN and corresponding services with minimum service interruption and minimal signalling in the network ... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 31.2 PDN connection establishment or mobility to EPC | The PDN connection shall be established as defined in 3GPP TS 23.401 [15] with the following additions.
Figure 31.2-1: PDN connection establishment
1. During the PDN connection establishment or when a PDU session is moved from 5GS to EPS without the N26 interface or from EPC/ePDG to EPS, the MME may signal in the Creat... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 31.3 MME triggered PDN connection restoration | The MME may trigger a PDN connection restoration to move the PDN connection to a different PGW-C/SMF in the same PGW-C/SMF Set, e.g. when detecting that the PGW-C/SMF currently serving the PDN connection is not reachable, as defined in this clause.
The MME may trigger this procedure for a specific PDN connection, e.g. ... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 31.4 PGW triggered PDN connection restoration | The PGW-C/SMF currently supporting a PDN connection, or a new PGW-C/SMF from the same PGW-C/SMF set, may trigger a PDN connection restoration to move the PDN connection to a different PGW-C/SMF as defined in this clause.
This may happen e.g. when a PGW-C/SMF is de-instantiated (scale-in operation), or when a new PGW-C/... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 31.5 Inter-MME or AMF-MME mobility | During inter-MME mobility, the source MME shall transfer the PGW Change Info to the target MME, if available.
During an inter-MME mobility procedure, if the PDN connection is pending to be restored at the source MME, i.e. when the source MME has started the PDN connection restoration procedure (see clauses 31.4 and 31.... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 31.6 Restoration of PDN connections and PFCP sessions associated with a specific FQ-CSID, Group ID or PGW-C/SMF IP Address | |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 31.6.1 General | To reduce signalling latency and achieve a better load balancing among PGW-C/SMFs in a Set, an PGW-C/SMF, MME, ePDG supporting S2b over GTPv2 and UPF may support the procedures specified in this clause. These procedures enable an SMF/PGW-C to request MME/ePDG supporting S2b over GTPv2/UPF to move PDN connections and PF... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 31.6.2 Allocation of Group Id or FQ-CSID to a PDN connection or a PFCP session | To optimize the resource utilization for PDN connection(s) and/or PFCP session(s), e.g. to meet different traffic requirements for different APNs/DNNs and/or DCNs/Network Slices, and also to facilitate moving a (sub)set of PDN connections/PFCP sessions among a PGW-C/SMF set, e.g. for a partial or complete PGW-C/SMF fai... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 31.6.3 Restoration of PDN connections associated with an FQ-CSID, Group ID or PGW-C/SMF IP Address | When there is a need to change the PGW-C/SMF controlling certain PDN connections, e.g. when a partial or complete PGW-C/SMF failure takes place, in order to trigger the MME(s) to re-establish the PDN connections that need to be taken over by a different PGW-C/SMF (e.g. PDN connections affected by the partial or complet... |
88525ca373d6c27ca925fc02f42c683a | 23.007 | 31.6.4 Restoration of PFCP sessions associated with an FQ-CSID, Group ID or PGW-C/SMF IP Address | When there is a need to change the PGW-C/SMF controlling certain PFCP sessions, e.g. when a partial or complete failure takes place, the PGW-C/SMF (either the PGW-C/SMF serving the PFCP sessions or another PGW-C/SMF in the same Set taking over the control of the PFCP sessions) may send a PFCP Session Set Modification R... |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 0 Scope | The present document provides details concerning information to be stored in the different entities storing data within a 3GPP network concerning mobile subscriber. A list of entities storing subscriber data is provided in clause 1.
Clause 2 contains all details concerning the definition of the parameters, often given ... |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 0.1 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non‑specific.
- For a specific reference, subsequent revisions do not apply.
- Fo... |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 0.2 Abbreviations | For the purposes of the present document, the abbreviations listed in 3GPP TR 21.905 [1] apply.
GEO Geosynchronous Orbit
LEO Low Earth Orbit
MEO Medium Earth Orbit
NCGI NR Cell Global Identity
NR New Radio
RG Residential Gateway |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 1 Introduction | |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 1.1 Definition | The term subscriber data is used to designate all information associated with a subscription which is required for service provisions, identification, authentication, routing, call handling, GPRS mode transmission, charging, subscriber tracing, operation and maintenance purposes. Some subscriber data are referred to as... |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 1.2 Storage facilities | This specification considers subscriber data stored by the following types of network functions:
- Home subscriber server (HSS) which contains all permanent subscriber data and all relevant temporary subscriber data to support the call control and session management entities of the different Domains and Subsystems.
- H... |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 1.3 Subscriber data in other functional units | The individual Subscriber Authentication Key Ki defined in 3GPP TS 43.020 [31] is stored in the Authentication Centre (AuC); it is also stored in the SIM and therefore available in the MS. Version numbers of algorithms A3 and A8 may also be stored in the AuC.
Bootstrapping Server Function (BSF) handles subscriber's boo... |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 1.4 Subscriber data in WLAN-IW functional units | This specification considers subscriber data stored in the following types of functional unit for I‑WLAN:
- 3GPP AAA Server which contains all subscriber data necessary to maintain WLAN Direct IP Access and WLAN 3GPP IP Access.
- 3GPP AAA Proxy which contains subscriber data necessary to perform AAA proxy functionality... |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2 Definition of subscriber data for CS and PS domain | |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.1 Data related to subscription, identification and numbering | |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.1.1 Data defining the subscription profile |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.