hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
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 restoration procedure with the following modifications:
- for GTP-based S5, the PGW shall include the PGW F-TEID for control plane in the PGW Downlink Triggering Notification message;
- for PMIP-based S5, the PGW shall include the PGW IP address and uplink GRE key for control plane in the PMIP Update Notification message; |
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 messages during periods when there is no need for other MB2 signalling); or
- the MBMS Heartbeat procedure (see clause 29), if this procedure is supported.
In deployments with a Diameter Agent between the BM-SC and the GCS AS, the GCS AS shall detect an MB2-C path failure using the MBMS Heartbeat procedure (see clause 29).
NOTE 1: A transport connection failure does not allow to identify a failure of the remote MBMS peer. Likewise, it is not possible to rely on Diameter Device-Watchdog-Request / Answer messages to test the responsiveness of the remote MBMS node during periods when there is no need for other MB2 signalling as these messages are only exchanged between Diameter peers with a direct transport connection.
Upon detecting a non-transient MB2-C path failure, the GCS AS shall assume that all the TMGIs that had been assigned by the BM-SC have been de-allocated and that all the related MBMS bearers have been deactivated.
The GCS AS may restore the MBMS delivery e.g. via a different BM-SC using the MB2-C procedures specified in 3GPP TS 29.468 [36]. |
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 considered to be down if the counter exceeds N3-REQUESTS.
Upon detecting a path failure, the network node should notify the failure via the Operation and Maintenance system and may either
- delete the bearer contexts associated with the path in failure; or
- maintain the bearer contexts associated with the path in failure during an operator configurable maximum path failure duration. The network node shall delete the maintained resources if the path is still down when this duration expires.
An MME may also perform relevant restoration procedure(s) if the S1-U path failure notification feature as specified in the following clause(s) is supported.
NOTE 1: During transient path failures (e.g. path failures not exceeding few minutes at most), maintaining the bearer contexts associated with the peer's IP address enables the delivery of end user services (when the path is re-established again) and also avoids unnecessary signalling in the network for restoring those bearers.
NOTE 2: It is not intended to maintain bearer contexts during long path failures (e.g. exceeding few minutes at most) as this would imply undesirable effects like undue charging. |
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, even if there is no MBMS user data to be sent).
Upon detecting a non-transient SGi-mb path failure (operator configurable maximum path failure duration), based on operator's policy, the MBMS GW may tear down the affected MBMS sessions by sending MBMS Session Stop Request message(s) to the MME/SGSN(s) serving the MBMS sessions and Session Termination Request message(s) to the BM-SC with a terminating cause signalling a user plane failure.
NOTE 2: This enables to free corresponding radio resources in E-UTRAN/UTRAN and to attempt to re-establish the MBMS session(s). |
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, the BM-SC shall encode the MBMS Session Start Request with the same contents as in the original MBMS Session Start Request (or per the last MBMS Session Update Request sent by the BM-SC if the original parameters were updated) with the following exceptions:
- the BM-SC shall set the "MBMS session re-establishment indication" flag to signal that this message is used to re-establish an MBMS session;
- if no absolute start time ("MBMS data transfer start" parameter) has been sent, the BM-SC may change the relative start time ("time to MBMS data transfer" parameter) to fasten the restoration of the MBMS service in E-UTRAN;
- the BM-SC should set the estimated session duration to a value corresponding to the remaining duration of the session;
- the BM-SC shall provide the new user plane resources assigned to the MBMS session over SGi-mb.
If the MBMS session is not re-established and if it was activated by a Group Communication Service Application Server(s) (GCS AS), the BM-SC shall notify the GCS AS that the MBMS session has been deactivated. |
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-C respectively, by sending an PFCP Node Report Request (see 3GPP TS 29.244 [43]) including a User Plane Path Failure Report with the IP address of the remote GTP-U peer(s) towards which a failure has been detected;
- upon detecting a failed GTP-U user plane path become recovered, the SGW-U or PGW-U shall report the user plane path recovery to the SGW-C or PGW-C respectively, by sending an PFCP Node Report Request (see 3GPP TS 29.244 [43]) including a User Plane Path Recovery Report with the IP address of the remote GTP-U peer(s) associated with the user plane path recovered;
- upon being notified about the user plane path failure, when deciding to delete the bearer contexts associated with the path in failure, the SGW-C or PGW-C shall modify or delete the affected PFCP sessions in the SGW-U or PGW-U.
NOTE: The SGW-C and PGW-C need to take care to smooth the signalling load towards the SGW-U and PGW-U if a large number of PFCP sessions are affected by the user plane path failure.
An SGW-C may support S1-U path failure notification feature as specified in clause 20.3.5.
20.3.4A Reporting of a Peer GTP-U Entity Restart
When Control Plane and User Plane Separation (CUPS) is deployed, to reduce massive amount of Sx signalling to report the receiving of GTP-U Error Indication messages and to perform subsequent PFCP Session Modification for PFCP sessions affected by the peer GTP-U restart, a user plane function (SGW-U or PGW-U) and a control plane function (SGW-C or PGW-C) may optionally support reporting of a peer GTP-U entity restart.
A GTP-U entity, e.g. in a SGW-U or a PGW-U, may detect the restart of the peer GTP-U entity as specified in clause 18A.
When the user plane function detects the peer GTP-U entity has restarted via receiving one or more GTP-U Error Indication message(s) or Echo Request/Response message(s) containing a larger Recovery Time Stamp, and when the control plane function supports Reporting of a GTP-U Entity Restart, it shall send a PFCP Node Report Request message to the control plane function to report that:
- the peer GTP-U entity identified by Remote GTP-U Peer IE has restarted; and
- all PFCP sessions associated with the restarted peer GTP-U entity have been modified by the user plane function, i.e. the F-TEID(s) that had been allocated by the restarted GTP-U entity have been removed from the FARs and the Apply-Action in these FARs changed to BUFF and NOCP, if the restarted GTP-U entity is a RNC or eNB.
NOTE: The UP function can learn if the restarted GTP-U entity is a RNC or eNB by using the Destination Interface Type included in the Forwarding Parameters in the FAR (which contains the F-TEID that had been allocated by the restarted GTP-U entity).
The control plane function shall send a PFCP Node Report Response message to acknowledge the receipt of the report of the peer GTP-U entity restart; and the control plane may further behave as if it receives a GTP-U Error Indication Report for those PFCP sessions affected by the peer GTP-U entity restart, e.g. to trigger Downlink Data Notification procedure as part of Network Triggered Service Request procedure if the restarted GTP-U entity is a RNC or eNB. (see also clauses 21.7 and 21.8) |
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 operator configurable maximum path failure duration timer has not expired), the SGW shall notify the MME of the S1-U path failure in subsequent signalling procedures associated with those PDN connections that are affected by the failed S1-U path as follows:
- when the SGW receives a Create Session Request message with eNodeB F-TEID(s), e.g. in an S1/X2 handover with SGW relocation procedure, or a Modify Bearer Request message or a Modify Access Bearer Request message, e.g. in a Service Request procedure:
- if all default bearer contexts are associated with failed S1-U paths, the SGW shall reject the request messages with the cause code "S1-U Path Failure" at the message level;
- if the bearer context(s) associated with the failed S1-U path(s) is not the default bearer context, the SGW may partially accept the Create Session Request or the Modify Bearer Request message and shall include the cause code "S1-U Path Failure" at the bearer context level for the bearer context(s) associated with failed S1-U path(s);
- if at least one of default bearers among multiple PDN connections from the same UE is not associated with the failed S1-U path, the SGW may partially accept the Modify Access Bearer Request message including the cause code "S1-U Path Failure" at the bearer context level for the bearer context associated with failed S1-U path;
- at reception of downlink packets to be sent towards an S1-U bearer associated with a failed S1-U path, the SGW shall send a Downlink Data Notification message with the cause code "S1-U Path Failure".
- If the SGW decided to delete the bearer contexts associated with the failed path, the SGW shall include a cause code "S1-U path failure" in the Delete Bearer Request message. |
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 Delete Bearer Request message:
- the MME shall derive the S1-U path information (e.g. the eNB F-TEID and the SGW F-TEID) from the UE Context and mark it as failed, and the MME shall store such information for a configurable period, and before the configured period is expired;
- the MME should avoid selecting the SGW with a failed S1-U path towards the eNB for subsequent PDN connection establishment procedures and mobility procedures with SGW relocation;
- if an alternative SGW without an S1-U path failure is available, the MME shall perform an SGW relocation procedure at a Service Request procedure for the PDN Connection(s) where the default bearer is associated with a failed S1-U path as specified in clause 5.10.4 of 3GPP TS 23.401 [15].
- if an alternative SGW without an S1-U path failure is available, the MME should perform an SGW relocation procedure for all active PDN connections where the default bearer is associated with the failed S1-u path as specified in clause 5.10.4 of 3GPP TS 23.401 [15].
- the MME should deactivate the corresponding PDN connections using the "reactivation requested" cause value as specified in clause 5.10.3 of 3GPP TS 23.401 [15] if it receives a Delete Bearer Request with the cause "S1-U Path Failure" for deleting the PDN connection;
- the MME shall deactivate the corresponding E-RAB for the bearer context(s) associated with failed S1-U path(s) if it receives a Delete Bearer Request message with the cause "S1-U Path Failure" for deleting dedicated bearer context(s). |
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 used instead of a GTPv1-U Error Indication message for the Error Indication handling. |
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 discarded. The GGSN shall inform the SGSN that the GGSN received a GTP error indication from RNC. The SGSN shall re-establish the tunnel between the SGSN and GGSN as specified in 3GPP TS 29.060 [8], which sets the related PDP context as valid again in the GGSN. The GGSN then forwards any subsequent downlink packets to the SGSN.
- If the GGSN receives a GTP error indication for a PDP context that has the no DTI flag set (i.e. from an SGSN), the GGSN shall delete its PDP context and may notify the Operation and Maintenance network element. |
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 required"
- If the SGSN receives a GTP error indication from the RNC it shall locally release the RAB. The SGSN should preserve the associated PDP context. The SGSN may initiate the RAB Assignment procedure in order to re-establish the RAB.
- For MBMS, when an Error Indication is received from an SGSN, the receiving GGSN shall delete all information associated with the relevant SGSN in its MBMS Bearer Context and the GGSN may notify the Operation and Maintenance network element. In addition, for broadcast mode the GGSN may request the re-establishment of the MBMS Bearer Context by sending an MBMS Session Start Request message (see clause 7.5A.2.5 of 3GPP TS 29.060 [8]). Furthermore, if the GGSN serves only one downstream SGSN for MBMS data transfer and the GGSN does not support the re-establishment procedure, the GGSN shall delete its MBMS Bearer Context together with the affected MBMS UE Context(s). |
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-activation required"
- If the S4-SGSN receives a GTP error indication from the RNC it shall locally release the RAB. The S4-SGSN should preserve the associated Bearer context. The S4-SGSN may initiate the RAB Assignment procedure in order to re-establish the RAB. |
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 RNC receives a GTP error indication from the GGSN (i.e. if Direct Tunnel is established), it shall initiate the RAB Release procedure with the error cause "GTP Resources Unavailable" and immediately locally release the RAB (i.e. without waiting for a response from the SGSN). The SGSN shall delete the related PDP context at the SGSN and send a Deactivate PDP Context Request message to the MS with cause "re-activation required".
- If the RNC receives a GTP error indication from the SGW (i.e. if Direct Tunnel is established), it shall initiate the RAB Release procedure with the error cause "GTP Resources Unavailable" and immediately locally release the RAB (i.e. without waiting for a response from the SGSN). The SGSN shall delete the related PDP context and send a Deactivate PDP Context Request message to the MS with the cause "re-activation required". If the deleted PDP context is a primary PDP context, the SGSN shall set the "Tear down indicator" bit in the Deactivate PDP Context Request message. The SGSN may also optionally send a Delete Bearer Command or a Delete Session Request message to the SGW if the deleted PDP context is a secondary PDP context or a primary PDP context respectively.
NOTE: Sending a Delete Bearer Command or a Delete Session Request message to the SGW can help the SGSN to determine whether the GTP error indication was due to the release of the bearer context or the release of the UE context in the SGW. |
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 receives the E-RAB Release Indication for a default bearer that is not the last default bearer of a UE or that the UE has a SCEF PDN connection or that the UE supports Attach without PDN connectivity as specified in clause 5.3.8.3 of 3GPP TS 23.401 [15], the MME should send a Delete Session Request to the SGW. Additionally the MME may also send a Deactivate EPS Bearer Context Request to the UE with the ESM cause set to "Reactivation Requested" if the MME has decided to restore the PDN connection based on operator policy, QCI and/or ARP and/or APN. If the MME receives the E-RAB Release Indication for the last default bearer of a UE and the UE does not have a SCEF PDN connection and the UE does not support Attach without PDN connectivity as specified in clause 5.3.8.3 of 3GPP TS 23.401 [15], the MME shall initiate a MME initiated Detach procedure with the detach type "re-attach required". If the MME receives the UE Context Release Request from the eNB, the MME shall send a Release Access Bearers Request to the SGW but if the SGW responds with a "context not found" cause and the UE does not have a SCEF PDN connection and the UE does not support Attach without PDN connectivity, then the MME shall initiate a MME initiated Detach procedure with the detach type "re-attach required".
- If the eNodeB receives a GTP error indication from a peer eNodeB over an X2-U direct forwarding tunnel or from an SGW over an S1-U indirect forwarding tunnel, the eNodeB may ignore the error indication received over the forwarding tunnels or delete the forwarding tunnel context locally without deleting the EPS bearers.
- For dual connectivity case as specified in 3GPP TS 36.300 [32]:
- If the MeNodeB receives a GTP error indication from the SGW over an S1-U tunnel, 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 MeNodeB/SeNodeB receives a GTP error indication from the peer SeNodeB/MeNodeB, the MeNodeB/SeNodeB shall delete the X2-U tunnel locally;
- If the SeNodeB receives a GTP error indication from the SGW over an S1-U tunnel, it shall delete the S1-U tunnel locally;
- The MeNodeB and SeNodeB may initiate an additional dual connectivity procedure(s) as specified in 3GPP TS 36.300 [32]. |
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 not delete the associated Bearer Context but delete all the RNC GTP-U tunnel TEIDs for this MS and sends a Downlink Data Notification message to the SGSN (the complete behaviour is specified in clause 22). Then the SGW starts buffering downlink packets received for this MS.
- For an 'Active' mode UE having a user plane connection with an eNB, i.e. SGW has F-TEIDs assigned by eNB for user plane for the UE, when the SGW receives a GTP Error Indication for a Bearer Context from an eNodeB, the SGW should not delete the associated Bearer Context but delete all the eNodeB GTP-U tunnel TEIDs for this UE and sends a Downlink Data Notification message to the MME (the complete behaviour is specified in clause 22). Then the SGW starts buffering downlink packets received for this UE.
- For a UE having an S11 user plane connection with an MME, i.e. SGW has S11-U F-TEIDs assigned by MME for user plane for the UE, when the SGW receives a GTP Error Indication for a Bearer Context from an MME, the SGW may:
- delete all the Bearer contexts associated with the PDN connection (identified by the default bearer) and notify the Operation and Maintenance network element, or as an alternative,
- delete the MME GTP-U tunnel TEID for this UE and send a Downlink Data Notification message to the MME to re-establish the user plane path without deleting the PDN connection (the complete behaviour is specified in clause 22). Then the SGW starts buffering downlink packets received for this UE.
- If the SGW receives a GTP error indication from S4-SGSN for a Bearer Context other than the default bearer when S4-U is used, the SGW may delete its Bearer context and may notify the Operation and Maintenance network element, or as an alternative, the SGW may send Downlink Data Notification message to the S4-SGSN to re-establish the user plane path without deleting the bearer context.
- If the SGW receives a GTP error indication from S4-SGSN for the default bearer when S4-U is used, the SGW may delete all the Bearer contexts associated with the PDN connection (identified by the default bearer) and may notify the Operation and Maintenance network element, or as an alternative, the SGW may send Downlink Data Notification message to the S4-SGSN to re-establish the user plane path without deleting the PDN connection.
- If the SGW receives a GTP error indication from a PGW for the bearer other than the default bearer, the SGW shall delete its Bearer context and may notify the Operation and Maintenance network element.
- If the SGW receives a GTP error indication from a PGW for the default bearer, the SGW shall delete all the Bearer contexts associated with the PDN connection (identified by the default bearer) and may notify the Operation and Maintenance network element. The SGW may send the Delete Bearer Request for the default bearer to the MME/S4 SGSN to delete the associated PDN connection.
PMIP error indication message shall be handled as follows:
- If the SGW receives an ICMP message from a PGW that indicates the UE specific error indication, as specified in the 3GPP TS 29.275 [16], the SGW may delete the associated PDN connection (identified by the GRE key included in the ICMP message) and may notify the Operation and Maintenance network element. In this case, the SGW may also:
- send the Delete Bearer Request for the default bearer to the MME/S4 SGSN to delete the associated PDN connection, and/or,
- perform other implementation specific actions, such as: sending messages to release other external resources (e.g. PCC messages). |
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 indication from a SGW/a TWAN /an ePDG for the default bearer, the PGW shall delete all the Bearer contexts associated with the PDN connection (identified by the default bearer) and may notify the Operation and Maintenance network element.
PMIP error indication message shall be handled as follows:
- If the PGW receives an ICMP message from an SGW/an ePDG/a Trusted Non-3GPP IP access node that indicates the UE specific error indication as specified in the 3GPP TS 29.275 [16], the PGW may delete the associated PDN connection (identified by the GRE key included in the ICMP message) and may notify the Operation and Maintenance network element. |
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 for the default bearer, the ePDG shall delete all the Bearer contexts associated with the PDN connection (identified by the default bearer) and initiate the release of the corresponding SWu instance (i.e. IKEv2 tunnel). The ePDG may notify the Operation and Maintenance network element.
PMIP error indication message shall be handled as follows:
- If the ePDG receives an ICMP message from a PGW that indicates the UE specific error indication as specified in the 3GPP TS 29.275 [16], the ePDG may delete the associated PDN connection (identified by the GRE key included in the ICMP message) and initiate the release of the corresponding SWu instance (i.e. IKEv2 tunnel) . The ePDG may notify the Operation and Maintenance network element. |
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 for the default bearer, the TWAN shall delete all the Bearer contexts associated with the PDN connection (identified by the default bearer) and may initiate the release of the corresponding WLAN specific resource. The TWAN may notify the Operation and Maintenance network element.
PMIP error indication message shall be handled as follows:
- If the TWAN receives an ICMP message from a PGW that indicates the UE specific error indication as specified in the 3GPP TS 29.275 [16], the TWAN may delete the associated PDN connection (identified by the GRE key included in the ICMP message) and may initiate the release of the corresponding WLAN specific resource. The TWAN may notify the Operation and Maintenance network element. |
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 "re-activation required", or initiate an explicit detach with reattached required procedure, as appropriate, see 3GPP TS 24.301 [19]. |
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 message, the MME/S4 SGSN shall perform the Network Triggered Service Request procedure as specified in 3GPP TS 23.060 [5] and 3GPP TS 23.401 [15].
- If the UE is in CONNECTED state, upon receipt of the Downlink Data Notification message, the MME shall perform S1 Release procedure and perform Network Triggered Service Request procedure as specified in 3GPP TS 23.401 [15].
- If the UE is in CONNECTED state, upon receipt of the Downlink Data Notification message and Direct Tunnel is used, the S4-SGSN shall perform Iu Release procedure and perform Network Triggered Service Request procedure as specified in 3GPP TS 23.060 [5] if the cause value included in Downlink Data Notification is "Error Indication received from RNC/eNodeB/S4-SGSN",
- If the UE is in CONNECTED state, upon receipt of the Downlink Data Notification message and Direct Tunnel is not used, the S4-SGSN should re-establish all of the S4-U bearers of this UE if the cause value included in Downlink Data Notification is "Error Indication received from RNC/eNodeB/S4-SGSN".
Upon receipt of a Downlink Data Notification message from the SGW, caused by an Error Indication message received from the MME over the S11 User Plane, the MME should perform the following if the UE is known by the MME:
- If the UE is in IDLE state, the MME shall perform the Network Triggered Service Request procedure as specified in 3GPP TS 23.401 [15].
- If the UE is in CONNECTED state, the MME may perform an S1 Release procedure and a Network Triggered Service Request procedure as specified in 3GPP TS 23.401 [15], or as an alternative, the MME may keep the existing S1 signalling connection and just send a Modify Bearer Request message to the SGW to re-establish the S11-U tunnel.
If the MME receives a Downlink Data Notification message from the SGW as a result of the SGW having detected a S1-U path failure, and if the MME supports S1-U path failure notification feature, the MME shall behave as specified in clause 20.3.6. |
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 applies to PGW-C as well.
A partial failure handling feature may be used when a hardware or software failure affects a significant number of PDN connections while a significant number of PDN connections are unaffected. This feature may also be used for the degenerate case of a full/complete failure of a remote node (MME or PGW) in order to cleanup hanging PDN connections associated with the failed node. When it is impossible to recover the affected PDN connections (for example, using implementation-specific session redundancy procedures), it is useful to inform the peer nodes about the affected PDN connections for recovery on the peer nodes. Such a notification could be performed using an identifier that represents a large set of PDN connections rather than on individual PDN connection basis.
NOTE 1: If a hardware or software failure happens to impact only an insignificant number of PDN connections the node experiencing the fault need not treat the failure as a partial fault but may tear down connections one by one.
For the purposes of partial fault handling the term "node" refers to an entity that takes the role of an MME, PGW, ePDG, TWAN or SGW as defined in an SAE network.
A PDN Connection Set Identifier (CSID) shall identify a set of PDN connections within a node that may belong to an arbitrary number of UEs. A CSID is an opaque parameter local to a node. Each node that supports the feature maintains a local mapping of CSID to its internal resources. When one or more of those resources fail, the corresponding one or more fully qualified CSIDs are signalled to the peer nodes.
The fully qualified CSID (FQ-CSID) is the combination of the node identity and the CSID assigned by the node which together globally identifies a set of PDN connections.
NOTE 2: The node identifier in the FQ-CSID is required since two different nodes may use the same CSID value. A partial fault in one node should not cause completely unrelated PDN connections to be removed accidentally.
The node identifier shall be globally unique across all 3GPP EPS networks. Its format is defined in 3GPP TS 29.274 [13]
For the purposes of partial fault handling the term peer is used as follows: For a particular PDN connection two nodes are peers if both nodes are used for that PDN connection. For a PDN Connection Set the nodes are peers if they have at least one PDN connection in the PDN Connection Set where both nodes are used for that PDN connection. In particular PGW and MME are generally peers for the purposes of partial fault handling.
An FQ-CSID is established in a node and stored in peer nodes in the PDN connection at the time of PDN connection establishment, or during a node relocation, and used later during partial failure handling in messages defined in 3GPP TS 29.274 [13] and 3GPP TS 29.275 [16]. Each node that support the feature, including the MME, SGW, ePDG, TWAN and the PGW, shall maintain the FQ-CSID provided by every other peer node for a PDN connection. The FQ-CSIDs stored by PDN connection are later used to find the matching PDN connections when a FQ-CSID is received from a node reporting a partial fault for that FQ-CSID.
With the exception of the GTPv2 Delete PDN Connection Set Request and PMIPv6 Binding Revocation Indication BRI messages, each feature supporting MME, SGW, ePDG, TWAN or PGW shall assign only one FQ-CSID for itself in messages and each FQ-CSID shall have exactly one CSID within the FQ-CSID.
Following rules shall apply for all the nodes:
1) If a node (MME, SGW, ePDG, TWAN or PGW) supports the partial failure handling feature, it shall generate and include its own FQ-CSID during the PDN connection establishment, node relocation procedures. Explicit list of the relevant GTPv2 messages is given in the respective clauses (14.3 "Partial Failure Handling at MME", 16.2 "Partial Failure Handling at SGW", 17B.2 "Partial Failure Handling at ePDG", 17C.2 "Partial Failure Handling at TWAN" and 17.2 "Partial Failure Handling at PGW"). A node that supports partial failure handling feature shall also store peers' FQ-CSIDs.
2) Additionally, if an SGW supports partial failure handling feature, it shall forward the peer node's (of an MME or of a PGW, depending on the direction) FQ-CSID and also Delete Connection Set Request/Response messages. Also, if the SGW detects the full/complete failure of an MME or PGW, e.g., through the Echo Request/Echo Response procedure, it may send a Delete PDN Connection Set Request (or PMIPv6 Binding Revocation Indication with G bit set) message containing all of the FQ-CSIDs of the associated hanging PDN connections of the failed node to the corresponding remote node (MME or PGW) .
3) If a node that supports partial failure handling feature receives peer node's FQ-CSID during the procedures, which are specified in Rule 1, it shall conclude that the peer node supports the feature. Subsequently, the node shall store the peer node's FQ-CSID and shall send appropriate partial failure handling messages to the peer.
4) If a node that supports partial failure handling feature does not receive the peer's FQ-CSID during the procedures, which are specified in Rule 1, it shall conclude that the peer node does not support the feature.
5) A node that supports partial failure handling feature shall not send any FQ-CSID IE or any partial failure handling specific messages to the peer node if the sender is aware (see Rule 4) that the receiver does not support the feature.
6) If a node does not support the partial failure handling feature, it shall ignore any received FQ-CSID IE or any partial failure handling specific message.
7) During session management procedures as specified in 3GPP TS 23.401 [15] and 3GPP TS 23.402 [18] (such as a dedicated bearer activation/deactivation/update), a node supporting the partial failure handling feature may update its FQ-CSID to the supporting peer node(s) in the Create Bearer Request/Response, Delete Bearer Request/Response or Update Bearer Request/Response.
NOTE 3: FQ-CSID handling for the Initial Attach and various handover cases are addressed in clauses 14, 16 and 17.
In addition to the above requirements, for split SGW and PGW, the following applies:
1) If a node (SGW-C, SGW-U, PGW-C or PGW-U) supports the partial failure handling feature, it shall generate and include its own FQ-CSID during the Sx Session Establishment procedure.
2) The SGW-C shall initiate Sx Session Modification procedure to update the SGW-U with the MME FQ-CSID, PGW-C FQ-CSID if changed;
3) The PGW-C shall initiate Sx Session Modification procedure to update the PGW-U with the MME FQ-CSID, SGW-C FQ-CSID, TWAN FQ-CSID, or ePDG FQ-CSID if changed;
4) The SGW-C and the PGW-C may change its FQ-CSID during a Sx Session Modification procedure if its SEID is changed;
5) When the node (SGW-C, SGW-U, PGW-C or PGW-U) detects that it has undergone a partial failure, it shall send a Sx Session Set Deletion Request message containing all the its CSIDs of the component(s) failing to its peer node;
6) For a SGW-C or a PGW-C, it shall also send Sx Session Set Deletion Request to the SGW-U or PGW-U respectively containing MME FQ-CSID, ePDG FQ-CSID, TWAN FQ-CSID, PGW-C FQ-CSID or SGW-C FQ-CSID if it receives the corresponding GTPv2 message Delete PDN Connection Set Request message containing those FQ-CSID.
7) The SGW-C and the PGW-C shall initiate the restoration procedure to restore the Sx Sessions affected by the partial failure in the SGW-U or the PGW-U in the same way as specified in the clause 16.1A.3 for the SGW-U failure and 17.1A.3 for the PGW-U failure respectively, when receiving an Sx Session Set Deletion Request message including a SGW-U or a PGW-U FQ-CSID(s) which is associated with the partial failure from the SGW-U or the PGW-U.
Figure 23-1 illustrates FQ-CSID establishment during the Attach or PDN connection establishment procedures for 3GPP E-UTRAN access as specified in the above rules.
Figure 23-1: FQ-CSID establishment during the Attach or PDN establishment procedure for 3GPP E-UTRAN access
1. If an MME supports partial failure handling, the MME shall send own FQ-CSID to SGW with a Create Session Request message across S11 interface.
The MME's FQ-CSID indicates to the SGW that MME supports partial failure handling. If the SGW does not receive MME's FQ-CSID, then the SGW shall never send partial failure handling related messages or IEs to the MME.
If the SGW does not support partial failure handling, then the SGW shall silently discard MME's FQ-CSID.
If the SGW does support partial fault handling it shall store the MME's FQ-CSID in it's PDN connection table.
2. If the SGW supports partial failure handling, the SGW shall forward MME's FQ-CSID to PGW with a Create Session Request message or a Proxy Binding Update message across S5/S8 interface. The SGW shall also include own FQ-CSID into the message.
The SGW's FQ-CSID indicates to the PGW that the SGW supports partial failure handling.
If the PGW does not support partial failure handling, then the PGW shall silently discard both FQ-CSIDs.
3. If the SGW has indicated the support for partial failure handling to PGW, then the PGW, which supports the feature shall send own FQ-CSID back to the SGW with a Create Session Response message or a Proxy Binding Acknowledgement message across S5/S8 interface. PGW's FQ-CSIDs in the S5/S8 Create Session Response or a Proxy Binding Acknowledgement message indicates to the SGW that PGW supports partial failure handling.
If the SGW has not indicated support for partial failure handling, then PGW shall never send partial failure handling related messages or IEs to the SGW.
4. If the MME has indicated the support for partial failure handling to SGW, then the SGW, which supports the feature, shall forward PGW's FQ-CSID to MME with a Create Session Response message across S11 interface. The SGW shall also include own FQ-CSID into the message.
Figure 23-2 illustrates FQ-CSID establishment during the Attach or PDN connection establishment procedures for untrusted non-3GPP access as specified in the above rules.
Figure 23-2: FQ-CSID establishment during the Attach or PDN establishment procedure for non-3GPP access
1. If an ePDG/TWAN supports partial failure handling, the ePDG/TWAN shall send own FQ-CSID to PGW with a Create Session Request message across GTPv2 based S2b/S2a interface or a Proxy Binding Update message across PMIPv6 based S2b/S2a interface.
The ePDG's/TWAN's FQ-CSID indicates to the PGW that ePDG/TWAN supports partial failure handling. If the PGW does not receive ePDG's/TWAN's FQ-CSID, then the PGW shall never send partial failure handling related messages or IEs to the ePDG/TWAN.
2. If the PGW supports partial failure handling, it shall store the ePDG's/TWAN's FQ-CSID in its PDN connection table and it shall send own FQ-CSID back to the ePDG/TWAN with a Create Session Response message across GTPv2 based S2b/S2a interface or a Proxy Binding Acknowledgement message across PMIPv6 based S2b/S2a interface. PGW's FQ-CSIDs in the Create Session Response or Proxy Binding Acknowledgement indicates to the ePDG/TWAN that PGW supports partial failure handling. The ePDG/TWAN shall then store the PGW's FQ-CSID in its PDN connection table.
If the PGW does not support partial failure handling, then the PGW shall silently discard ePDG's/TWAN's FQ-CSID.
Figure 23-3 illustrates FQ-CSID establishment during the Sx Session Establishment procedure for 3GPP access, with a split SGW, as specified in the above rules.
Figure 23-3: FQ-CSID establishment during the Sx Session Establishment procedure
1. If an SGW-C supports partial failure handling, the SGW-C shall send its own FQ-CSID and MME FQ-CSID to the SGW-U in the Sx Session Establishment Request.
2. If the SGW-U supports partial failure handling, it shall store the SGW-C FQ-CSID and MME FQ-CSID for the related Sx Session and it shall send its own FQ-CSID back to the SGW-C in the Sx Session Establishment Response message. The SGW-U's FQ-CSID in the Create Session Establishment Response implicitly indicates to the SGW-C that SGW-U supports partial failure handling. The SGW-C shall then store the SGW-U's FQ-CSID for the related Sx Session. If the SGW-C does not receive an SGW-U FQ-CSID from the SGW-U, then the SGW-C shall not further send partial failure handling related messages or IEs to the SGW-U.
If the SGW-U does not support partial failure handling, then the SGW-U shall silently discard the SGW-C's FQ-CSID and MME FQ-CSID.
Figure 23-4 illustrates FQ-CSID establishment during the Sx session Establishment procedure with a split PGW as specified in the above rules.
Figure 23-4: FQ-CSID establishment during the Sx session establishment procedure
1. If a PGW-C supports partial failure handling, the PGW-C shall send its own FQ-CSID, SGW-C FQ-CSID, TWAN FQ-CSID, ePDG FQ-CSID and MME FQ-CSID to PGW-U in the Sx Session Establishment Request.
2. If the PGW-U supports partial failure handling, it shall store the PGW-C FQ-CSID, SGW-C FQ-CSID, TWAN FQ-CSID, ePDG FQ-CSID and MME FQ-CSID for the related Sx Session and it shall send its own FQ-CSID back to the PGW-C in the Sx Session Establishment Response message. The PGW-U's FQ-CSIDs in the Sx Session Establishment Response implicitly indicates to the PGW-C that PGW-U supports partial failure handling. The PGW-C shall then store the PGW-U's FQ-CSID for the related Sx Session. If the PGW-C does not receive a PGW-U FQ-CSID from the PGW-U, then the PGW-C shall not further send partial failure handling related messages or IEs to the PGW-U.
If the PGW-U does not support partial failure handling, then the PGW-U shall silently discard PGW-C's FQ-CSID.
Figure 23-5 illustrates FQ-CSID establishment during the Sx Session Establishment procedures to provide the PGW-C FQ-CSID to the SGW-U after receiving a PGW-C FQ-CSID in Create Session Response from PGW-C on the S5/S8 interface.
Figure 23-5: FQ-CSID establishment to provide a PGW-C FQ-CSID to the PGW-U
1. If an SGW-C supports partial failure handling and the SGW-U has indicated its support of partial failure in the Sx Session Establishment Response, the SGW-C shall send PGW-C FQ-CSID received on S5/S8 interface to the SGW-U in an Sx Session Modification Request.
2. If the SGW-U supports partial failure handling, it shall store the PGW-C FQ-CSID for the related Sx Session and send a reply to the SGW-C.
If the SGW-U does not support partial failure handling, then the SGW-U shall silently discard the PGW-C's FQ-CSID. |
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 client. |
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 specified in clause 25.3 if it supports Idle mode Signalling Reduction (ISR) (see 3GPP TS 23.401 [15] and 3GPP TS 23.060 [5]).
The network triggered restoration procedure without ISR shall apply to UEs for which ISR is not active at the time the ISR associated node fails. The network triggered restoration procedure with ISR shall apply to UEs for which ISR is active at the time the ISR associated node fails. Both procedures may run in parallel if there is a mix of UEs with ISR and without ISR at the time the ISR associated node fails.
For the PMIP based S5/S8 case, the terminology "S5/S8 bearer" used through clause 25 shall be read as "S5/S8 IP traffic flow" within the GRE tunnel. The detailed concepts of the "IP traffic flow" are specified in 3GPP TS 23.402 [18]. |
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 data and MM bearer contexts for some specific S5/S8 bearer contexts eligible for network initiated service restoration, and initiate the deletion of the resources associated with all the other S5/S8 bearers.
NOTE 1: This enables the SGW to still receive downlink user plane or control plane data from the PGW or from a PCRF (PMIP based S5/S8) for the maintained S5/S8 bearers.
The S5/S8 bearers eligible for network initiated service restoration are determined based on operator's policy, e.g. based on the QCI and/or ARP and/or APN, and such operator's policy shall be applicable for both the SGW and the MME/SGSN. The Delay Tolerant Connection Indication (DTCI), if set, may also be used to determine that the S5/S8 bearer is not eligible for network initiated service restoration, based on operator's policy when using QCI and/or ARP and/or APN is not sufficient, e.g. for Home routed roaming scenario.
Emergency PDN connections for users without authenticated IMSI do not need to be maintained by the SGW and cannot be restored at the initiative of the network.
NOTE 2: Users with an emergency call in progress can re-attach and re-establish the emergency PDN connection after detecting the loss of the signalling connection with the RAN. IMS Emergency PSAP callback is not supported for unauthenticated users with an emergency registration but without an emergency call in progress.
If at least one S5/S8 bearer needs to be maintained, the SGW shall also start a timer controlling the maximum duration during which those bearers shall be maintained. There is one operator configurable timer per SGW. The timer value may be equal to the periodic tracking area update timer (timer T3412) as specified in 3GPP TS 24.301 [19] or the periodic routing area update timer (timer T3312) as specified in 3GPP TS 24.008 [20]. This timer ensures that the S5/S8 bearers eligible for network initiated service restoration are maintained until the corresponding UE reattaches to the network. If the timer expires, the maintained resources shall be locally deleted assuming that the corresponding UE might have reattached to the network via a different SGW.
The SGW shall not release the default bearer of a PDN connection for which one or more dedicated bearers are maintained. Any downlink user plane or control plane packet received on a default bearer which is not eligible for network initiated service restoration but which is maintained for dedicated bearer(s) eligible for such procedure shall be silently discarded by the SGW.
When releasing the maintained S5/S8 bearers, the SGW may optionally perform other implementation specific actions such as messages to clear other external resources (e.g. PCC messages to clear the resources in the PCRF or GTP/PMIP messages to release the corresponding PDN connection in the PGW).
If the SGW receives a Create Session Request message for a UE for which some S5/S8 bearers are maintained, the SGW shall delete all the bearers for this UE and proceed with the Create Session Request message handling as specified in 3GPP TS 29.274 [13]. |
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 shall proceed as follows:
- if the received downlink packet contains user plane data, the SGW shall silently discard it but the SGW shall continue maintaining the corresponding bearers. If the SGW receives another downlink user plane packet for an ARP value other than the ARP included in the Downlink Data Notification sent before, it shall proceed as specified in clause 5.3.4.3 "Network Triggered Service Request" of 3GPP TS 23.401 [15] with the exception that the packet shall be discarded by the SGW.
- For the S5/S8 GTP case:
- if the received downlink packet contains a control plane message other than a Delete Bearer Request message then the SGW may reject the message and shall continue maintaining the corresponding bearers. If the SGW receives another control plane message for an ARP value other than the ARP included in the Downlink Data Notification sent before, it shall proceed as specified in clause 5.3.4.3 "Network Triggered Service Request" of 3GPP TS 23.401 [15] with the exception that the message may be rejected by the SGW.
- if the received downlink packet contains the Delete Bearer Request message, the SGW shall accept the message, and shall release the corresponding S5/S8 bearer(s) immediately.
- For the S5/S8 PMIP case:
- if the received packet contains a control plane message other than the message of the Gateway Control and QoS Rules Provision procedure as specified in 3GPP TS 29.213 [21] clause 4.4.3 which results in the SGW to decide to deactivate an existing dedicated bearer, then the SGW may reject the message and shall continue maintaining the corresponding bearers. If the SGW receives another control plane message for an ARP value other than the ARP included in the Downlink Data Notification sent before, it shall proceed as specified in clause 5.3.4.3 "Network Triggered Service Request" of 3GPP TS 23.401 [15] with the exception that the message may be rejected by the SGW.
- if the received downlink packet contains the message of the Gateway Control and QoS Rules Provision procedure as specified in 3GPP TS 29.213 [21] clause 4.4.3 which results in the SGW to decide to deactivate an existing dedicated bearer, the SGW shall accept the message, and shall release the corresponding S5/S8 bearer(s) immediately.
The SGW may send the Downlink Data Notification message including the IMSI to the respective MME or S4-SGSN, if there is some DL data buffered for a UE when detecting the MME or S4-SGSN restart.
NOTE: For a UE using a power saving feature, DL data can be buffered for an extended duration in the SGW. The above requirement can allow the MME or S4-SGSN to restore the service to such a UE at the next occasion the UE becomes reachable. The SGW needs to pace the sending of Downlink Data Notification to the MME or S4-SGSN to avoid signalling storms over S11 and S4.
The SGW may send the Downlink Data Notification message to another MME or S4-SGSN (the same type of mobility node as the failed one) located in the same pool as the failed node if the SGW cannot send it to the failed MME or S4-SGSN (e.g. because it did not restart). It is an implementation/deployment matter how an SGW becomes aware that an MME/S4-SGSN has failed and has not restarted. |
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 paging procedure is implementation dependent. The MME or S4-SGSN may support and apply this procedure to a UE using extended idle mode DRX, and if so, they shall page the UE with the S-TMSI/P-TMSI.
NOTE 1: Upon receiving a page message with
- the IMSI, the UE starts the reattach procedure as specified in clause 5.6.2.2.2 of 3GPP TS 24.301 [19] and clause 4.7.9.1.2 of 3GPP TS 24.008 [20];
- the S-TMSI, the UE starts the service request procedure which is rejected by the MME with Cause #10 – Implicitly detached; the UE then re-attaches to the network as specified in clause 5.6.2.2.1 of 3GPP TS 24.301 [19];
- the P-TMSI, in case of Iu mode, the UE starts the service request procedure which is rejected by the S4-SGSN with Cause #10 – Implicitly detached; the UE then re-attaches as specified in clauses 4.7.9.1.1 and 4.7.13 of 3GPP TS 24.008 [20];
- the P-TMSI, in case of A/Gb mode, the UE sends any LLC frame and subsequently re-attaches to the network as specified in clause 8.1.4 of 3GPP TS 23.060 [5].
NOTE 2: Paging in the MME or S4-SGSN serving area will cause excessive use of radio resources. How to reduce the paging area is implementation dependent.
NOTE 3: It is the responsibility of the MME/S4 SGSN to avoid unnecessary IMSI Paging.
NOTE 4: How the restarted or alternative MME/S4-SGSN knows the UE's DRX parameter or the extended DRX parameters to page the UE is implementation dependent.
NOTE 5: A restarted MME will not receive S1AP UE Context Active message as part of UE initiated Connection Resume procedure, since the eNB would have deleted the AS context for all UEs associated with this MME after detecting the MME restart.
The MME or S4-SGSN may request the SGW to immediately release the maintained S5/S8 bearers by sending the "Downlink Data Notification Acknowledge" message or a "Downlink Data Notification Failure Indication" message with the specific cause "UE already re-attached", e.g. if the UE has already re-attached to the network. The Downlink Data Notification Acknowledge and Downlink Data Notification Failure Indication shall include the IMSI to identify the UE context in the SGW. |
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 service restoration procedure.
In the rest of this clause, the term "non-failed" node refers to the CN node (MME or S4-SGSN) that remains in normal operation during this procedure, as opposed to the "restarted" node which refers to the CN node (MME or S4-SGSN) that has failed and restarted.
The procedure in the SGW towards the restarted node differs from the procedure towards the non-failed ISR associated node (see clause 25.3.2). |
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 SGW shall consider that ISR is still active. There is one operator configurable timer per SGW. The timer value may be set to a value that is the greater value of the periodic tracking area update timer (timer T3412) as specified in 3GPP TS 24.301 [19] and the periodic routing area update timer (timer T3312) as specified in 3GPP TS 24.008 [20]. This timer ensures that the SGW can still send Downlink Data Notification messages to the restarted MME or S4-SGSN until the corresponding UE learns that ISR is deactivated. If the timer expires, the SGW shall deactivate ISR by locally releasing the resources for the maintained restarted CN node (i.e. restarted CN node control plane F-TEID).
Upon receipt of the downlink user plane or control plane packet on a maintained S5/S8 bearer for a UE in idle mode or in connected state with the failed CN node, the SGW shall initiate the network triggered service request procedure towards the non-failed CN node as specified in 3GPP TS 23.401 [15] clause 5.3.4.3. In addition, if the S5/S8 bearer is eligible for network initiated service restoration, the SGW shall also immediately send a Downlink Data Notification message including the IMSI towards the restarted CN node as specified in clause 25.2.2. The SGW shall continue to forward downlink user plane or control plane packet for a UE in connected state in the non-failed ISR associated node.
The S5/S8 bearers eligible for network initiated service restoration are determined by the SGW based on operator's policy e.g. based on the QCI and/or ARP and/or APN.
Emergency PDN connections for users without authenticated IMSI do not need to be maintained by the SGW and cannot be restored at the initiative of the network.
NOTE 0: Users with an emergency call in progress can re-attach and re-establish the emergency PDN connection after detecting the loss of the signalling connection with the RAN. IMS Emergency PSAP callback is not supported for unauthenticated users with an emergency registration but without an emergency call in progress.
The SGW may send the Downlink Data Notification message with the IMSI to another MME or S4-SGSN (the same type of mobility node as the failed one) in the same MME or S4-SGSN pool if the SGW cannot send it to the failed MME or S4-SGSN (e.g. because it did not restart). It is an implementation/deployment matter how an SGW becomes aware that an MME/S4-SGSN has failed and has not restarted.
Upon receipt of a Downlink Data Notification message including the IMSI, the restarted CN node shall respond to the SGW with a Downlink Data Notification Acknowledge message and should page the UE and force it to re-attach to the network as specified in clause 25.2.
NOTE 1: If the UE camps under the service area of the restarted CN node, then the UE re-attaches to the network (see NOTE 1 in clause 25.2.3).
If the paging is successful (i.e. Modify Bearer Request is received) for the non-failed ISR associated CN node, the SGW may send a Stop Paging Indication message including the IMSI to the restarted CN node (or the alternative node in the same pool to which the Downlink Data Notification message with the IMSI has been sent before) to stop the paging procedure.
If the SGW receives a Create Session Request message as part of Initial Attach procedure for a UE for which the PDN connections, MM bearer context and ISR state have been maintained, the SGW shall stop the timer, deactivate ISR, and delete the maintained resources associated to the restarted CN node (i.e. CN node control plane F-TEID). The SGW may additionally send a Stop Paging Indication message to the non-failed ISR associated CN node to stop the paging procedure.
NOTE 2: The SGW may have already deleted the restarted CN node resources since Delete Session Request from non-failed ISR associated CN node may arrive earlier than the Create Session Request message.
If the non-failed ISR associated CN node received a Cancel Location message from HSS/HLR with "Initial Attach procedure" Cancellation Type, the non-failed CN node shall delete all the bearer contexts and send Delete Session Request message(s) to SGW. The SGW shall then release all the resources for this UE and sends one of the following messages to PGWs involved to release all the resources maintained in the PGWs as specified in 3GPP TS 23.401 [15] and 3GPP TS 23.402[18].
- For the GTP based S5/S8 case, Delete Session Request message(s)
- For the PMIP based S5/S8 case, PBU message(s) with Lifetime set to "0"
The SGW shall stop the timer and delete the resources for the maintained restarted CN node (i.e. restarted CN node control plane F-TEID) if it receives one of the following messages while the timer is running:
- a Modify Bearer Request message indicating that ISR is not active, e.g. from the non-failed CN node during a TAU/RAU procedure; or
- a Modify Bearer Request message indicating that ISR is active from another mobility management node with the same type as the restarted node. |
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 non-failed CN node may initiate the GUTI Relocation or P-TMSI Relocation Procedure with a non-broadcast TAI or RAI to force the UE to perform the TAU/RAU procedure for ISR deactivation, e.g. if a signalling connection is established with the UE following receipt of a Downlink Data Notification message.
If afterwards the non-failed MME/S4-SGSN receives TAU/RAU Request, then the MME/S4-SGSN shall inform the UE in the TAU/RAU Accept message to disable ISR as specified in 3GPP TS 23.401[15] and 3GPP TS 23.060 [5]. The non-failed CN node shall send a Modify Bearer Request message to the SGW, even if the MME/S4-SGSN did not change during the TAU/RAU, to request the SGW to disable ISR and to update the SGW with the latest RAT Type and Serving Network values. Upon receipt of that message, the SGW shall disable ISR and shall stop sending Downlink Data Notification message with IMSI to the restarted CN node. |
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 mode are not aware of an MME failure until they need to send some uplink data or signalling (e.g. a periodic Tracking Area Update) or until they are forced to re-attach e.g. via the network trigerred service restoration procedure. Without support of the procedure defined in this clause, UEs that remain under LTE may not be able to receive mobile terminated CS services for a long duration after an MME failure without restart or a long MME failure.
The following requirements shall apply if the VLR and MME support this feature.
When the VLR has to page the UE for a mobile terminated CS service (e.g. upon receipt of an incoming CS call), if the VLR detects that the MME serving the UE is no longer in service, the VLR should send an SGs paging request with a CS restoration indicator to one alternative MME in the same MME pool. The VLR should load-balance the paging requests among the available MMEs in the pool during the restoration procedure.
The VLR may know the set of MMEs pertaining to the same MME pool by local configuration or by checking the MME Group ID within the MME name that MMEs signal to the VLR in the SGsAP-LOCATION-UDATE-REQUEST, SGsAP-RESET-INDICATION or SGsAP-RESET-ACK messages. The MME should send an SGsAP-RESET-INDICATION message to the VLR after restart.
The VLR may detect that an MME is no longer in service if there are no more SCTP associations in service with that MME.
NOTE 2: Semi-permanent SCTP associations are established between the MME and VLR, i.e. the SCTP associations remain up under normal circumstances.
The VLR should adjust its paging retransmission delay to avoid requesting again the UE to re-attach before the restoration procedure completes.
The MME shall behave as specified in clause 14.1.3 upon receipt of an SGs paging request not including the CS restoration indicator.
The MME shall accept the SGs paging request and proceed as follows upon receipt of an SGs paging request including the CS restoration indicator:
- if the IMSI is unknown by the MME, or if the IMSI is known and the UE is marked as EMM-DEREGISTERED, the MME shall send the paging request with the location information provided by the VLR, regardless of the value of the "MME-Reset" indicator. If no such location information is provided, the MME may either page the UE in all the tracking areas corresponding to that MME or in the tracking areas served by the MME and by the VLR, or reject the paging request per operator policy. The paging request shall include the IMSI and the CN domain indicator set to "PS" to request the UE to re-attach;
- if the IMSI is known by the MME and the UE is considered to be attached to both EPS and non-EPS services or for SMS only (for an SGs paging request with an 'SMS indicator'), the MME shall page the UE based on the location information stored in the MME.
The MME may support and apply this procedure to a UE using extended idle mode DRX for MT-SMS service, and if so, the MME shall page the UE with the S-TMSI.
NOTE 3: How the alternative MME knows the UE's DRX parameter or the extended DRX parameters to page the UE is implementation dependent.
Upon receipt of a paging request including the IMSI and the CN domain indicator set to "PS", or upon receipt of a Service Reject with Cause #10 – Implicitly detached (when using S-TMSI paging), the UE re-attaches to one MME of the pool (that may not be necessarily the MME that initiated the paging procedure towards the UE) and a new SGs association is established with the VLR. This may be a different VLR than the VLR that initiated the SGs paging procedure, e.g. if Intra Domain Connection of RAN Nodes to Multiple CN Nodes is deployed for GERAN or UTRAN (see 3GPP TS 23.236 [24]).
NOTE 4: The UE can receive a Service Reject with Cause #10 – "Implicitly detached" upon being paged by an alternative MME with the S-TMSI assigned by the MME that has failed. The UE then re-attaches to the network as specified in clause 5.6.2.2.1 of 3GPP TS 24.301 [19].
If the new SGs association is established towards the same VLR, the VLR should repeat the SGs paging request after the UE has re-attached to non-EPS services. The MT CS service or SMS is then delivered according to normal procedures.
If the new SGs association is established towards a different VLR, the MT CS service may be delivered via the new VLR using Mobile Terminating Roaming Retry or Mobile Terminating Roaming Forwarding (see 3GPP TS 23.018 [23]); the on-going MT SMS is retransmitted by the SMS-SC using the existing SMS procedures (SMS alert).
Subsequent MT CS services are delivered as per normal procedures.
NOTE 5: A UE with ISR active before the MME failure and using GERAN or UTRAN radio access will not receive the paging request sent by the alternative MME. The VLR can deliver the MT CS service by paging the UE on the A/Iu interface as per existing principles of 3GPP TS 29.118 [14] when the UE does not respond to a first paging on the SGs interface. Paging the UE on the A interface fails if the network operates in NMO I and the UE is in PS connected mode in GERAN.
See 3GPP TS 29.118 [14] for a comprehensive description. |
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 clause are optional to support.
The procedures specified in clause 27.2 apply to UEs for which ISR is not active when the SGW fails. The procedures specified in clause 27.3 apply to UEs for which ISR is active when SGW fails. The procedures specified in these clauses only apply to PDN connections established between MME/S4-SGSN and PGW pertaining to the same operator, i.e. for non-roaming and roaming scenarios with local breakout. The MME/S4-SGSN and the PGW shall behave as per the restoration requirements specified in clauses 14.1A.1 and 17.1A.1 for PDN connections established between nodes pertaining to different operators, i.e. as if the remote peer node does not support these SGW restoration procedures.
The procedures specified for an SGW in clauses 27.2 and 27.3 apply as well to an SGW-C. An SGW-C shall always apply in addition the related PFCP procedures towards the SGW-U.
NOTE 1: The applicability of these procedures is restricted to PDN connections established between MME/S4-SGSN and PGW pertaining to the same operator to ensure, simply by local configuration, that MME/S4-SGSN and PGWs apply the same logic i.e. same operator's policies when determining whether and which PDN connections should be restored. This enables to restore in particular IMS PDN connections (even in roaming scenarios, for which local break out is used).
NOTE 2: The use of these SGW restoration procedures may be extended by Service Level Agreements to PDN connections established between MME/S4-SGSN and PGW pertaining to different operators, i.e. for roaming scenarios with home routed traffic, but this is not further considered in 3GPP specifications. |
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.2 and in clause 27.2.3. |
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-SGSNs. The PGW shall assume that either all or none of the MMEs/S4-SGSNs in the PLMN support this procedure.Upon detecting an SGW failure with or without restart (relying on restart counter as specified in clause 18 "GTP-C based restart procedures" and clause 19 "PMIP based restart procedures", or implementation e.g. preconfigured path failure timer), the MME/S4-SGSN and PGW shall maintain the bearers and MM contexts of the PDN connections affected by the SGW failure and eligible for restoration, instead of removing associated resources as per procedures specified in clauses 14.1A.1 and 17.1A.1.
For PMIP based S5, when the PCRF detects an SGW failure or restart, the PCRF shall maintain the IP-CAN sessions and delete locally the Gxc sessions affected by the SGW failure.
NOTE 1: The PGW notifies the PCRF about the termination of IP-CAN sessions associated to PDN connections that are not restored by the MME/S4-SGSN within an operator configurable period.
The PDN connections eligible for restoration are determined by the MME/S4-SGSN and PGW based on same operator's policies, e.g. based on QCI, ARP and/or APN.
NOTE 2: The PCRF is not aware of which PDN connections are eligible for restoration. When the PGW detects an SGW failure, the PGW requests the PCRF to terminate IP-CAN sessions associated to PDN connections affected by the SGW failure and not eligible for restoration.
Maintaining the PDN connections affected by the SGW failure enables the MME/S4-SGSN to restore the corresponding bearers of the UE by selecting a new SGW or the restarted SGW. These PDN connections are maintained for an operator configurable period (T-Release-PDN timer), which is locally provisioned on MME/S4-SGSN and PGW, that by default should cover the periodic tracking area update timer (timer T3412) as specified in 3GPP TS 24.301 [19] or the periodic routing area update timer (timer T3312) as specified in 3GPP TS 24.008 [20]. After the expiry of the T-Release-PDN timer the MME/S4-SGSN and the PGW should delete any EPS bearer contexts that have not been restored via a new or the restarted SGW.
NOTE 3: The PGW's capability of supporting this SGW restoration procedure is stored per PDN and per UE by the serving MME/S4-SGSN. For a UE with multiple active PDN connections, some PGWs may support the SGW restoration procedure while others do not support the same. E.g. SGW restoration procedure may be supported for a PDN connection with local breakout while not supported for another PDN connection with home routed traffic. The restoration procedures upon SGW failure specified in clauses 14.1A.1 and 17.1A.1 apply to the PDN connections for which the SGW restoration procedure is not supported or not applicable. |
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 MME/S4-SGSN shall control the pace of the SGW relocations to avoid core network node overload. The MME/S4-SGSN should prioritize the SGW relocation for UEs engaged in a Service Request, or a Connection Resume, or RAU/TAU procedures or having GBR bearers over UEs which are not engaged in any mobility procedure and that do not have a signalling connection to the MME/S4-SGSN nor GBR bearers. The MME/S4-SGSN should also prioritize the SGW relocation for UEs with an emergency PDN connection.
The MME/S4-SGSN may further prioritize the PDN connections to restore, e.g. for UEs ECM_IDLE / PMM-IDLE / GPRS STANDBY not engaged in any Service Request or Connection Resume procedure, based on operator's policy e.g. based on the QCI and/or APN. Besides, the MME/SGSN may use the subscribed Restoration Priority per APN, if received from the HSS, and if permitted per service level agreements for in-bound roamers, to determine the relative restoration priority among PDN connections to the same APN. The MME/SGSN may use a locally configured value as default restoration priority if the restoration priority for a user's PDN connection is not received from the HSS or not permitted by service level agreement for in-bound roamers.
NOTE 1: This is to allow all the affected UEs to be reconnected to the network in a relatively short time (that is function of the speed of the SGW relocations that the MME/S4-SGSN performs, based on implementation and the network load) so that downlink packets may be delivered to the UEs with minimum service interruption.
NOTE 2: Prioritizing the restoration of emergency PDN connections can enable to preserve emergency calls in progress for authenticated and unauthenticated users, and enable PSAP to call back authenticated users with an emergency registration but without an emergency call in progress.
NOTE 3: The Restoration Priority can e.g. allow to restore with a higher priority users with an IMS voice subscription over IMS users without an IMS voice subscription.
To restore the PDN connection(s) of a UE, the MME/S4-SGSN shall perform an SGW relocation procedure by sending a Create Session Request message (per PDN connection to restore) to the new or restarted SGW as per the steps 8-11 of a Tracking Area Update procedure with Serving GW change in clause 5.3.3.1 in 3GPP TS 23.401[15]. For PDN connections with GBR bearers existing before the SGW failure, the MME/S4-SGSN may either request to restore or remove the GBR bearers in the Create Session Request (e.g. depending on how quickly the PDN connection is restored). The MME/S4-SGSN shall restore the PDN connections of the affected UEs after the SGW failure as follows:
1) for UEs in ECM_IDLE/PMM-IDLE/GPRS STANDBY state:
- the MME/S4-SGSN shall select a new SGW or the restarted SGW based on the last visited TAI/RAI. When Dedicated Core Networks are deployed, the UE Usage Type shall also be used for the SGW selection as specified in 3GPP TS 29.303 [37];
- the MME/S4-SGSN shall then perform an SGW relocation procedure as specified above.
2) for UEs in ECM_CONNECTED/PMM-CONNECTED/GPRS READY state not engaged in any mobility procedure (TAU/RAU, Handover):
- the MME/S4-SGSN shall release the S1/Iu/radio resources; if the eNodeB/RNC detects the SGW failure, the eNodeB/RNC may request the MME/S4-SGSN to release the S1/Iu resources;
- the MME/S4-SGSN shall then handle these UEs as specified for UEs in ECM_IDLE/PMM-IDLE/GPRS STANDBY state, or for UEs performing a mobility procedure if the UE performs subsequently such a mobility procedure (e.g. a Service Request to re-establish the S1/Iu/radio bearers);
- as an exception to these rules, for UTRAN without direct tunnel and GERAN, the S4-SGSN may perform SGW relocation while keeping the UEs in PMM-CONNECTED/GPRS READY state (i.e. without tearing down the Iu/radio resources) because S4 user plane is used and the SGW failure remains not visible to the radio network.
NOTE 4: An SGW failure with restart may be visible to the radio network and cause bearers to be released for bearers with on-going uplink traffic if an Error Indication is received from the SGW before the S4-SGSN detects the SGW restart.
3) for UEs in ECM-IDLE/PMM-IDLE/GPRS STANDBY state initiating a Service Request procedure or a Connection Resume procedure:
- the MME/S4-SGSN shall first perform the SGW relocation procedure as specified above and then continue with the Service Request or the Connection Resume procedure since the MME/S4-SGSN has no valid SGW F-TEID to send in the S1-AP Initial Context Setup Request towards the eNodeB or in the Iu RAB Assignment Request message towards the RNC if Direct Tunnel is used.
4) for UEs initiating an intra-MME or intra-S4-SGSN TAU/RAU procedure:
- the MME/S4-SGSN shall perform the SGW relocation procedure as specified above before the TAU/RAU procedure;
5) for UEs initiating an inter-MME/SGSN TAU/RAU procedure:
- If both the source and target MME/S4-SGSNs support this SGW restoration procedure, the source MME/S4-SGSN should indicate to the target MME/S4-SGSN in the GTPv2 Context Response message that an SGW relocation procedure is needed due to an earlier SGW failure. Upon reception of such indication, the target MME/S4-SGSN shall perform the SGW relocation procedure as specified above and then proceed with the TAU/RAU procedure. The source MME/S4-SGSN may perform the SGW relocation procedure as specified above before responding to the GTPv2 Context Request message if the target MME/S4-SGSN does not support the SGW restoration procedure, e.g. during inter-PLMN RAU/TAU procedures when the target PLMN does not support the SGW restoration procedure.
6) for UEs in ECM-CONNECTED/PMM-CONNECTED/GPRS READY state for which a handover procedure is initiated:
- The source MME/S4-SGSN should reject the Handover Required / Relocation Required message received from the RAN (for UEs with PDN connection(s) affected by an earlier SGW failure that have not been restored yet); the MME/S4-SGSN should then release the S1/Iu/radio resources of these UEs to force them to enter idle mode. The MME/S4-SGSN shall then proceed with the procedures specified above for UEs in ECM_IDLE/PMM-IDLE/GPRS STANDBY state, or for UEs performing a mobility procedure if the UE performs subsequently such a mobility procedure (e.g. a Service Request to re-establish the S1/Iu/radio bearers).
NOTE 5: S1/Iu/radio resources of UEs in ECM-CONNECTED/PMM-CONNECTED/GPRS READY state affected by an SGW failure are released very shortly after the SGW failure. Therefore only very few UEs affected an SGW failure and with PDN connections not restored yet may be subject to a handover, e.g. handovers taking place just after the SGW failure before the eNodeB/RNC or the MME/S4-SGSN release the S1/Iu/radio resources. This is why it is not necessary to support SGW relocation during Intra/Inter-CN handover procedures.
After detecting a combined SGW/PGW failure, the MME/S4-SGSN behavior shall be same as in the case when an MME/S4-SGSN receives the optional PGW Restart Notification message. Either of the following shall apply:
- MME/S4-SGSN behavior is determined by clause 16.1A.2 "PGW Failure";
- PDN connections can be restored by the MME (this does not apply to S4-SGSN), as specified in clause 31.3 "MME triggered PDN connection restoration". |
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-Release-GBR), which should be much shorter than the T-Release-PDN timer. Upon expiry of the T-Release-GBR timer, the PGW shall release GBR bearers that have not been restored yet and inform the PCRF about the corresponding PCC rule inactivation, with a cause as specified in 3GPP TS 29.212 [25].
NOTE: This is a safeguard mechanism to avoid e.g. overcharging the user in IMS for sessions not already terminated by IMS (e.g. by the far end user of a VoIP call).
The PGW shall discard downlink packets received for a PDN connection maintained after an SGW failure that has not been restored yet.
The PGW shall stop charging for PDN connections maintained after an SGW failure which have not been restored yet.
If the IP-CAN Session Modification Request is received for a PDN connection maintained after an SGW failure but not restored yet, the PGW shall reject the request if the request contains the installation/modification of PCC rules and other policy decisions (e.g. change of APN-AMBR), however the P-GW shall accept to remove the PCC rule if the removal of PCC rules is included in the request. The PGW shall accept an IP-CAN Session Modification Request if it only includes the removal of PCC rules. Refer to 3GPP TS 29.212 [25] clause B.3.14 for the detail. For these IP-CAN sessions for which an IP-CAN session modification has been rejected, the PGW shall subsequently inform the PCRF when the PDN connection is restored as specified in clause B.3.14 of 3GPP TS 29.212 [25]. This would enable the PCRF to update the PCC rules in the PGW if necessary. After the PDN connection is restored, the PGW shall initiate the bearer modification/deactivation procedure if necessary to modify or remove the resources associated with the PCC rules that were removed during the SGW failure.
The PGW shall accept an IP-CAN Session Termination Request received for a PDN connection maintained after an SGW failure but not restored yet, with an acceptance cause as specified in 3GPP TS 29.212 [25] and release the affected PDN connection locally. If subsequently the MME/S4-SGSN attempts to restore the PDN connection, the PGW shall reject the Modify Bearer Request (for GTP based S5) or the Proxy Binding Update (for PMIP based S5) with the cause "Context Not Found" as specified in 3GPP TS 29.274 [13] and 3GPP TS 29.275 [16] after the corresponding PDN connection has been released locally. |
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 restored.
For PMIP based S5, the PCRF cannot send any message to the SGW once the Gxc session in the PCRF is removed. The PCRF may however behave as for GTP based S5, e.g. send signalling to the PGW via the Gx interface. The Gxc session is restored when the PCRF receives Gateway Control Session Establishment from the SGW as specified in 3GPP TS 29.212 [25]. |
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 request messages. This ensures that the MME/SGSN or PGW does not deactivate the bearers before it detects the SGW failure and triggers the restoration procedure. |
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 shall know by local configuration whether this PGW triggered SGW restoration procedure is supported in the PLMN. The MME/S4-SGSN/SGW may know the same by local configuration. When supported in the PLMN, the PGW supporting this procedure should be configured with the address of alternative(s) SGW(s) also supporting this procedure. The PGW shall assume that either all or none of the MMEs/S4-SGSNs in the PLMN support the procedure. All MMEs/S4-SGSNs in an MME/S4-SGSN pool should support this procedure when it is deployed.
The PGW triggered SGW restoration procedure does not apply to emergency PDN connections for users without authenticated IMSI.
NOTE: The MME/S4-SGSN can prioritize the restoration of emergency PDN connections (see clause 27.2.2.2). IMS Emergency PSAP callback is not supported for unauthenticated users with an emergency registration but without an emergency call in progress. |
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, a UE requested PDN connectivity, and a PDP Context Activation procedure;
- Create Session Request message during TAU/RAU procedures with a SGW change;
- Create Session Request message during X2 based handover/Enhanced SRNS Relocation procedure with a SGW change;
- Modify Bearer Request message during Inter-RAT Handover procedures with/without a SGW change;
- Modify Bearer Request message during Intra-RAT handover procedure with a SGW change;
- Modify Bearer Request message during Inter-RAT TAU/RAU procedures without a SGW change;
- Modify Bearer Request message over S11/S4 if the message is deemed to be sent to the PGW due to other reasons, e.g. reporting ULI, time zone.
During SGW restoration procedure:
Upon receipt of a PGW Downlink Triggering Notification message for which it cannot find a UE context corresponding to the received IMSI, the MME/S4-SGSN shall send a PGW Downlink Triggering Acknowledge message with the rejection cause code "Context Not Found" to the SGW to inform the SGW that the PGW Downlink Triggering Notification message has been received by the MME/S4-SGSN. If the PGW Downlink Triggering Notification message contains an MME/S4-SGSN identifier, the MME/S4-SGSN shall also include the IMSI and the MME/S4-SGSN identifier in the PGW Downlink Triggering Acknowledge message.
Upon receipt of a PGW Downlink Triggering Notification message for which it can find a UE context corresponding to the received IMSI, the MME/S4-SGSN shall send a PGW Downlink Triggering Acknowledge message back to the SGW with an acceptance cause code, and perform S-TMSI/P-TMSI paging as part of Network Initiated Service Request procedure as specified in clause 5.3.4.3 of 3GPP TS 23.401 [15] and in clause 6.12.1A of 3GPP TS 23.060 [5]. When receiving a Service Request message from the UE, the MME/S4-SGSN shall perform the SGW restoration procedure as specified in the clause 27.2.2 with the addition that the MME/S4-SGSN shall include the MME/S4-SGSN identifier IE in the create session request message. |
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 message (or a PMIP Update Notification message with the Notification Reason set to "PGW Downlink Trigger Notification") from a PGW, the SGW shall send the PGW Downlink Triggering Notification message to the MME/S4-SGSN identified by the MME/S4-SGSN identifier if present in the message. If no MME/S4-SGSN identifier is received from the PGW, the SGW shall send the PGW Downlink Triggering Notification message to all the MME/S4-SGSN within the MME/S4-SGSN pool as known by local configuration. The SGW shall then send a PGW Downlink Triggering Acknowledge message (or a PMIP Update Notification Acknowledgement message) back to the PGW with an acceptance cause code.
If the SGW receives a PGW Downlink Triggering Acknowledge message from an MME/S4-SGSN with the rejection cause code "Context Not Found" and with an IMSI and an MME/S4-SGSN identifier, the SGW shall then send a PGW Downlink Triggering Notification message, including the IMSI (as received in the PGW Downlink Triggering Acknowledge message), to all the MME/S4-SGSN within the MME/S4-SGSN pool as known by local configuration, except to the MME/S4-SGSN identified by the MME/S4-SGSN identifier received in the Downlink Triggering Acknowledge message.
The MME/S4-SGSN may have more than one IP address on the S11/S4 interface configured, but the PGW Downlink Triggering Notification should be sent only once per MME/S4-SGSN per local configuration in the SGW. |
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 Bearer Request without MME/SGSN identifier, it shall delete the stored MME/S4-SGSN identifier.
NOTE 1: This allows the PGW to have the serving MME/S4-SGSN address whenever there is S5 signalling message. However this cannot ensure that the PGW is always aware of the current serving MME/S4-SGSN address. E.g. during an inter-MME HO without SGW change, the current serving MME/S4-SGSN address will not be propagated to the PGW if there is no S5 signalling.
During SGW restoration procedure:
When downlink data packets or signalling other than an IP-CAN Session Termination Request arrives at the PGW, for a PDN connection associated with a failed SGW and that has not been restored yet (as specified in clause 27.2.2), and the PDN connection is eligible for PGW initiated Downlink triggering based on operator's policies, e.g. for IMS PDN connection, the PGW shall proceed as follows:
- the PGW shall select a SGW (i.e. the restarted or an alternative SGW) which supports the PGW triggered SGW restoration procedure, based on local configuration;
- for GTP-based S5, the PGW shall then send a PGW Downlink Triggering Notification message including the IMSI and the MME/S4-SGSN identifier if available;
- for PMIP-based S5, the PGW shall then send an PMIP Update Notification message as specified in IETF RFC 7077 [26] to indicate it is a PGW initiated downlink triggering notification, including the IMSI and the MME/S4-SGSN Identifier when it is available;
- the PGW should not send a new PGW Downlink Triggering Notification message (for GTP-based S5) or Update Notification message (for PMIP-based S5) in very short time if it continues to receive subsequent downlink data or signalling for the same PDN connection. It is an implementation option how many times/how frequently the PGW should send subsequent PGW Downlink Triggering Notification message (for GTP-based S5) or Update Notification message (for PMIP-based S5) before discarding the downlink packets or rejecting signalling.
- the PGW shall handle an IP-CAN Session Modification Request received from the PCRF as specified in clause B.3.14 of 3GPP TS 29.212 [25] as if the PDN connection had not been affected by the SGW failure i.e. was in a normal state . After accepting an IP-CAN session modification request, if the MME/S4-SGSN does not restore the PDN connection shortly after the PGW initiated triggering, the PGW shall report the modification failure to the PCRF with a cause as specified in clause B.3.14 of 3GPP TS 29.212 [25].
The PGW shall behave as specified in clause 27.2.2.3 if the PGW receives an IP-CAN Session Termination Request for a PDN connection associated with a failed SGW and that has not been restored yet.
NOTE 2: To ensure the delivery of downlink data, it is implementation specific whether the PGW buffers or not the downlink data until the PDN connection is restored. The application functions e.g. P-CSCF for IMS, may also retransmit the data packets.
NOTE 3: The operator policies for PDN connections eligible for restoration (i.e. to be maintained upon SGW failure as per clause 27.2.2) and PDN connections eligible for PGW initiated downlink triggering may differ, i.e. the PDN connections eligible for PGW initiated downlink triggering may be a subset of the PDN connections eligible for restoration. |
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. the MME or the S4-SGSN, does not support the MME/S4-SGSN triggered SGW restoration procedure. |
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 disable ISR as specified in 3GPP TS 23.401[15] and 3GPP TS 23.060 [5].
2) for UEs in ECM-IDLE/PMM-IDLE/GPRS STANDBY state initiating a Service Request procedure:
- the MME/S4 SGSN shall perform the SGW relocation procedure as specified in clause 27.2.2 and initiate the GUTI Relocation or P-TMSI Relocation procedure with a non-broadcast TAI or RAI to force the UE to perform the TAU/RAU procedure for ISR deactivation.
3) for UEs in ECM-CONNECTED/PMM-CONNECTED/GPRS READY state engaged in any handover or inter MME/S4-SGSN TAU/RAU procedure:
- it shall be handled as specified in clause 27.2.2.
4) for UEs in ECM-IDLE/PMM-IDLE/GPRS STANDBY state which are not engaged in any Service Request or other mobility procedure:
- In networks supporting PGW triggered SGW restoration proactive paging of UEs in ECM-IDLE/PMM-IDLE/GPRS STANDBY state shall not be initiated.
The MME/S4-SGSN shall page the UE to bring the UE to ECM-CONNECTED/PMM-CONNECTED. If the paging is successful and the UE initiates the Service Request procedure, the MME/S4-SGSN shall perform the SGW relocation procedure as specified in clause 27.2.2 and initiate the GUTI Relocation or P-TMSI Relocation Procedure with a non-broadcast TAI or RAI to force the UE to perform the TAU/RAU procedure for ISR deactivation as specified in clause 5.3.4.3 of 3GPP TS 23.401[15]. If paging the UE fails, the MME or S4-SGSN should adjust its paging retransmission strategy (e.g. limit the number of short spaced retransmissions) to take into account the fact that the UE might be in GERAN/UTRAN or E-UTRAN coverage. If the associated MME/S4-SGSN receives ISR Status Indication with "deactivation Indication" from S4-SGSN/MME, the MME/S4-SGSN shall release the UE session locally. Otherwise after retrying the paging procedure, the MME/S4-SGSN may release locally the PDN connection context and UE MM context assuming the UE is in GERAN/UTRAN or E-UTRAN coverage area.
MME/S4-SGSN should handle UEs in ECM-CONNECTED/PMM-CONNECTED and involved in any handover or inter MME/S4-SGSN TAU/RAU procedure first before paging of UEs in ECM-IDLE/PMM-IDLE/GPRS STANDBY to minimise paging of UEs. Furthermore the sequence on how UEs in ECM-IDLE/PMM-IDLE/GPRS STANDBY can be paged to avoid overload are implementation dependent.
The MME/S4-SGSN which initiates the SGW restoration procedure should send ISR Status Indication with "ISR deactivation Indication" to the ISR associated S4-SGSN/MME to release the PDN connection context and UE MM context.
NOTE 1: The PDN connection context and UE MM context can be released after the timer (T-Release-PDN timer), which is used for maintaining the context, expires, as specified in clause 27.2.2.1.
NOTE 2: The MME will only perform the SGW reselection for the UEs camping on the LTE, ISR activated UEs can camp in the GERAN/UTRAN, so paging is needed.
The S4-SGSN will only perform the SGW reselection for the UEs camping on the GERAN/UTRAN, ISR activated UEs can camp in the LTE, so paging is needed.
NOTE 3: It is the responsibility of the MME/S4-SGSN to avoid Paging Overload. |
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 or the S4-SGSN, does not support the PGW triggered SGW restoration procedure. |
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 interface to the ISR associated S4-SGSN/MME over the existing GTP-C tunnel between the S4-SGSN and the MME.
The ISR associated S4-SGSN/MME, which receives ISR Status Indication message with "Paging Indication", shall perform P-TMSI/S-TMSI paging as part of the Network Initiated Service Request procedure as specified in clause 27.3.1.2.
After the MME/S4-SGSN receiving NAS message Service Request, the MME/S4-SGSN shall behave as specified in the clause 27.3.1.2. |
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 of its MSs may be registered to the CSS. This causes each VLR concerned to mark each relevant roaming user record "Location Information Not Confirmed by CSS", and
- send a "Reset" message to each SGSN where one or more of its MSs may be registered to the CSS. This causes each SGSN to mark each relevant MM context "Location Information Not Confirmed by CSS".
- send a "Reset" message to each MME where one or more of its UEs may be registered to the CSS. |
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 GCS AS. A BM-SC, MBMS GW or GCS AS which support the MBMS restoration procedures as specified in this specification shall support and use the MBMS Heartbeat procedure for MBMS deployments with an intermediate Diameter Agent between the BM-SC and MBMS GW or GCS AS.
The restart of a peer MBMS node is detected using a Restart-Counter AVP. The Restart-Counter AVP contains a value that is incremented monotonically whenever the MBMS node restarts with loss of previous states.
The MBMS Heartbeat Request and Answer messages shall contain the Restart-Counter AVP set to the local restart counter of the sending node. Other MBMS messages sent over the SGmb or MB2-C reference point may also contain the Restart-Counter AVP if contacting the peer node for the first time or if the local restart counter has been incremented.
Upon receipt of a Restart-Counter AVP in a MBMS Heartbeat Request or Answer or in any other SGmb or MB2-C signalling message, the receiving node shall compare the value of the received Restart-Counter AVP with the previous Restart counter value stored for this peer entity and
- if no previous value was stored, the Restart counter value received in the SGmb or MB2-C signalling message shall be stored for the peer;
- if the value of the received Restart-Counter AVP is greater than the Restart-Counter previously received from the same MBMS node, the receiver shall consider that the peer MBMS node has restarted.
An intermediate Diameter Agent shall not modify the Restart-Counter AVP when proxying SGmb or MB2-C signalling between the BM-SC and MBMS GW or GCS AS.
The BM-SC, MBMS GW and GCS AS shall support the detection of an SGmb or MB2-C path failure by sending an MBMS Heartbeat Request message periodically when no other signalling is exchanged over those interfaces between those nodes. The MBMS Heartbeat Request message shall be repeated one or more times if no MBMS Heartbeat Answer is received. The SGmb or MB2-C path shall be considered to be down if the peer MBMS node does not respond to a configured number of consecutive MBMS Heartbeart Requests. MBMS Heartbeat Requests shall only be sent on a per node basis (i.e. not on a per MBMS session basis).
See 3GPP TS 29.061 [31] and 3GPP TS 29.468 [35] for further details. |
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 the SCEF.
If an HSS receives a reply message with error cause set to "SCEF_REFERENCE_ID_UNKNOWN", it shall stop reporting and delete the event localy.
If an MME/SGSN receives reply message with error cause set to "SCEF_REFERENCE_ID_UNKNOWN", it shall stop reporting, initiate a notification to the HSS with cause "SCEF_REFERENCE_ID_UNKNOWN" and delete the event.
An HSS receiving a notification with cause "SCEF_REFERENCE_ID_UNKNOWN", it shall delete the event localy. |
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 required procedure, as appropriate, see 3GPP TS 24.301 [19]. |
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 (e.g. no signalling wih the UE).
The procedure specified in this clause is optional to support for the MME, ePDG supporting S2b over GTPv2, SGW and PGW-C/SMF.
This procedure applies for combo PGW-C/SMF that are deployed in an PGW-C/SMF set (i.e. a set of PGW-C/SMF instances that are functionally equivalent and inter-changeable and that share the same contexts, see clause 5.21.3 of 3GPP TS 23.501 [45]).
In scenarios where a PGW-C/SMF becomes no longer available (e.g. PGW-C/SMF failure without restart, scale-in operation causing a PGW-C/SMF to be de-instantiated from the PGW-C/SMF set) or that require to change the PGW-C/SMF of a PDN connection, other PGW-C/SMFs from the same PGW-C/SMF set may take over the control of the PDN connections that were served by the PGW-C/SMF that is no longer available. When a PGW-C/SMF fails with restart, the restarted PGW-C/SMF should continue supporting the same PDN connections, if possible. When a PGW-C/SMF of a PGW-C/SMF set fails with or without restart, the Recovery (Restart Counter) shall not be incremented over S5/S8 (assuming the PDN connection context is still available in the PGW-C/SMF set).
The restoration of a PDN connection may be triggered by the MME (e.g. when the SGW detects and reports to the MME that the PGW-C has failed) or by the ePDG supporting S2b over GTPv2, or by the PGW-C/SMF (e.g. scale-in operation or PGW-C/SMF reselection by another network function such as PCF).
The procedure supports the restoration of Home Routed PDN connections, if the VPLMN and HPLMN support this procedure. If the VPLMN or HPLMN does not support this procedure, the existing behaviour applies, e.g. the MME and SGW clears all PDN connections of the PGW-C/SMF when detecting the failure or restart of the PGW-C/SMF and the MME may request UEs to release and reactivate some PDN connections (e.g. IMS PDN connections).
Clause 31.6 defines procedures to enable to restore a set of PDN connections affected by a PGW-C/SMF failure with or without restart, or scale-in operation, associated with specific FQ-CSIDs, Group IDs or PGW-C/SMF IP addresses. |
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 Create Session Request that it supports this procedure by settingthe Restoration of PDN connections after an PGW-C/SMF Change Support Indication in the Indication Flags IE. If the SGW also supports this feature, it shall relay this indication towards the PGW.
2. If the Create Session Request indicates support of this procedure and the PGW supports the Restoration of PDN connections after a PGW-C/SMF change procedure specified in clause 31, the PGW-C/SMF shall return a PGW Change Info IE in the Create Session Response, that the SGW shall relay transparently towards the MME. The PGW Change Info IE shall contain the PGW Set FQDN or Alternative PGW-C/SMF FQDN or IP Addresses of PGW/SMFs in the set. Receipt of this information indicates to the MME that this procedure is supported by the SGW and PGW-C/SMF for the PDN connection and that alternative PGW-C/SMF instances may be found using the PGW Set FQDN or the Alternative PGW FQDN or IP addresses, if the PGW-C/SMF becomes no longer reachable.
Likewise, a PDU session shall be moved from 5GS to EPS with the N26 interface as defined in clause 4.11 of 3GPP TS 23.502 [46] with the following additions:
- the MME may signal that it supports this procedure by setting the Restoration of PDN connections after an PGW-C/SMF Change Support Indication in the Indication Flags IE in:
- the Create Session Request during 5GS to EPS Idle mode mobility using N26 interface (see clause 4.11.1.3.2 of 3GPP TS 23.502 [46]); and
- in the Modify Bearer Request during an 5GS to EPS handover using N26 interface (see clause 4.11.1.2.1 of 3GPP TS 23.502 [46]);
- If the SGW also supports this feature, it shall relay this indication in the Modify Bearer Request towards the PGW;
- If the Modify Bearer Request received by the PGW-C/SMF indicates support of this procedure and the PGW supports the Restoration of PDN connections after a PGW-C/SMF change procedure specified in clause 31, the PGW-C/SMF shall return a PGW Change Info IE (with the same content as described above) in the Modify Bearer Response, that the SGW shall relay transparently towards the MME. This provides the same indication as described above to the MME.
31.2A PDN connection establishment or mobility to EPC/ePDG
The PDN connection shall be established as defined in clause 7.2.4 of 3GPP TS 23.402 [18] with the following additions.
Figure 31.2A-1: PDN connection establishment
1. During the PDN connection establishment or when a PDU session is moved from 5GS or EPS to EPC/ePDG, the ePDG may signal in the Create Session Request that it supports this procedure by setting the Restoration of PDN connections after an PGW-C/SMF Change Support Indication in the Indication Flags IE.
2. If the Create Session Request indicates support of this procedure and the PGW supports the Restoration of PDN connections after a PGW-C/SMF change procedure specified in clause 31, the PGW-C/SMF shall return a PGW Change Info IE in the Create Session Response. The PGW Change Info IE shall contain the PGW Set FQDN or Alternative PGW-C/SMF FQDN or IP Addresses of PGW/SMFs in the set. Receipt of this information indicates to the ePDG that this procedure is supported by PGW-C/SMF for the PDN connection and that alternative PGW-C/SMF instances may be found using the PGW Set FQDN or the Alternative PGW FQDN or IP addresses, if the PGW-C/SMF becomes no longer reachable.
Likewise, a PDU session shall be moved from 5GS to EPC/ePDG as defined in clause 4.11.4 of 3GPP TS 23.502 [46] with the following additions:
- the ePDG may signal that it supports this procedure by setting the Restoration of PDN connections after an PGW-C/SMF Change Support Indication in the Indication Flags IE in the Create Session Request during handover from 5GS to EPC/ePDG (see clause 4.11.4.2 of 3GPP TS 23.502 [46]); and
- If the Create Session Request received by the PGW-C/SMF indicates support of this procedure and the PGW supports the Restoration of PDN connections after a PGW-C/SMF change procedure specified in clause 31, the PGW-C/SMF shall return a PGW Change Info IE (with the same content as described above) in the Create Session Response to provides the same indication as described above to the ePDG. |
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. upon receiving a Modify Bearer Response message for this PDN connection with the cause code set to "Remote peer not responding", or for all PDN connections served by a PGW-C/SMF, e.g. when receiving a PGW Restart Notification from the SGW with the cause "PGW not responding" or when the MME determines that the PGW-C/SMF has failed.
Figure 31.3-1: MME triggered PDN connection restoration
1. The PGW-C/SMF fails without restart from the PGW-C/SMF set.
2a-2b. The MME sends a Modify Bearer Request message to the SGW, e.g., to report a User Location Information change, the SGW shall respond with the Modify Bearer Response message with the cause code set to "Remote peer not responding" when the SGW detects that the PGW-C/SMF is not responding.
2c-2d. When detecting that the PGW-C/SMF has failed, the SGW-C shall send a PGW Restart Notification to the MME as specified in clause 16.1A.2 and the MME shall respond with a PGW Restart Notification Acknowledge message.
When detecting that a PGW-C/SMF has failed, the SGW-C and MME shall maintain the contexts of the PDN connections served by that PGW-C/SMF for which this procedure is supported.
3. The MME should select an alternative PGW-C/SMF using the PGW Change Info received earlier from the PGW-C/SMF for the PDN connection (for the scenario described as step 2a-2b) or for all PDN connections associated with the failed PGW (for the scenario described as step 2c).
4. The MME shall send a Create Session Request towards the newly selected PGW-C/SMF, via the same or a different SGW, as specified in clause 7.2.1 of 3GPP TS 29.274 [13],including (among others) a PGW Change Indication, S5/S8-U F-TEIDs for dedicated bearers (if dedicated bearers were established before moving the PDN connection to the new PGW-C/SMF) and the Linked EPS Bearer ID identifying the default bearer of the PDN connection, and without setting the Operation Indication to "1". The MME may defer doing so until it needs to send signalling to the SGW or PGW-C. The MME should reuse the same SGW if possible, since the PDN connection restoration remains then transparent to the eNodeB. The PGW Change Indication tells the SGW and PGW-C/SMF that this is a request to move an existing PDN connection to the new PGW-C/SMF.
NOTE 1: The MME includes the S5/S8-U PGW F-TEIDs in the Create Session Request to the SGW. The SGW includes the S5/S8-U SGW F-TEIDs in the Create Session Request to the PGW.
5. The new PGW-C/SMF shall identify the PDN connection context using the UE's identity (i.e. IMSI or IMEI) and the Linked EPS Bearer Identity received in the Create Session Request. If it can take over the PDN connection, it shall return a Create Session Response towards the SGW and MME as specified in clause 7.2.2 of 3GPP TS 29.274 [13], including (among others) the new S5/S8 PGW F-TEID for control plane, its PGW node name, the S5/S8-U PGW F-TEID for the default bearer and S5/S8 PGW F-TEIDs for dedicated bearers (if any). The PGW-C/SMF shall not change the UE's IP address.
The SGW and MME shall update their PDN connection context with the information received from the PGW-C/SMF. Any subsequent control plane procedure between the MME, SGW and PGW shall take place as defined in existing procedures.
If the MME reselected a different SGW, the MME shall update the eNB with the new SGW's S1-U F-TEID using the MME triggered Serving GW relocation procedure (see clause 5.10.4 of 3GPP TS 23.401 [15]).
6. The MME shall update the PGW identity in the HSS.
7. The HSS shall respond the Notify Request. Upon detecting that the association between APN and PGW-C/SMF FQDN is changed, if an active subscription from the UDM exists for the UE to be notified on the change of the data, the HSS shall notify the UDM as specified in Figure 5.3.4-5 of clause 5.3.4 of 3GPP TS 23.632 [47].
NOTE 2: An active subscription from the UDM can exist e.g. to notify the AMF registered for the UE for non-3GPP access.
NOTE 3: The PDN connection restoration procedure specified in this clause does not require any specific handling from the HSS and UDM.
31.3A ePDG triggered PDN connection restoration
The ePDG supporting S2b over GTPv2 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 ePDG may trigger this procedure for a specific PDN connection, e.g. upon receiving no response to a request message for this PDN connection, or for all PDN connections served by a PGW-C/SMF, e.g. when the ePDG determines that the PGW-C/SMF has failed.
Figure 31.3A-1: ePDG triggered PDN connection restoration
1. The PGW-C/SMF fails without restart from the PGW-C/SMF set.
2. The ePDG detects that the PGW-C/SMF has failed as specified in clause 20.1.
When detecting that a PGW-C/SMF has failed, the ePDG shall maintain the contexts of the PDN connections served by that PGW-C/SMF for which this procedure is supported.
3. The ePDG should select an alternative PGW-C/SMF using the PGW Change Info received earlier from the PGW-C/SMF.
4. The ePDG shall send a Create Session Request towards the newly selected PGW-C/SMF, as specified in clause 7.2.1 of 3GPP TS 29.274 [13], including (among others) a PGW Change Indication, S2b-U ePDG F-TEIDs for dedicated bearers (if dedicated bearers were established before moving the PDN connection to the new PGW-C/SMF) and the Linked EPS Bearer ID identifying the default bearer of the PDN connection. The ePDG may defer doing so until it needs to send signalling to the PGW-C. The PGW Change Indication tells the PGW-C/SMF that this is a request to move an existing PDN connection to the new PGW-C/SMF.
5. The new PGW-C/SMF shall identify the PDN connection context using the UE's identity (i.e. IMSI or IMEI) and the Linked EPS Bearer Identity received in the Create Session Request. If it can take over the PDN connection, it shall return a Create Session Response towards the ePDG, as specified in clause 7.2.2 of 3GPP TS 29.274 [13], including (among others) the new S2b PGW F-TEID for control plane, its PGW node name, the S2b-U PGW F-TEID for the default bearer and S2b-U PGW F-TEIDs for dedicated bearers (if any). The PGW-C/SMF shall not change the UE's IP address.
The ePDG shall update their PDN connection context with the information received from the PGW-C/SMF. Any subsequent control plane procedure between the ePDG and PGW shall take place as defined in existing procedures.
6. The new PGW-C/SMF shall update the PGW identity in the 3GPP AAA Server, and the 3GPP AAA server will further populate the PGW identity to the HSS as specified in clause 12.1.4 of 3GPP TS 23.402 [18]. The new PGW-C/SMF shall update the PGW identity to the UDM as specified in clause 4.11.4.3.6 of 3GPP TS 23.502 [46] if S6b is not deployed between SMF+PGW-C and 3GPP AAA Server. |
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/SMF from the same PGW-C/SMF set is reselected for the PDN connection upon a request from the PCF or the PGW-U/UPF and, more generally, when the PGW-C/SMF supporting a PDN connection is no longer available and a new PGW-C/SMF of the same PGW-C/SMF set needs to send signalling to the SGW or MME, before the MME has triggered a PDN connection restoration.
Figure 31.4-1: PGW triggered PDN connection restoration
1. The PGW-C/SMF currently supporting the PDN connection or another PGW-C/SMF from the same PGW-C/SMF set determines that the PDN connection needs to be moved to a different PGW-C/SMF, e.g. during a PGW-C/SMF set scale-in operation, or e.g. due to PCF or PGW-U/UPF reselecting an alternative PGW-C/SMF from the same PGW-C/SMF set due to the PGW-C/SMF serving the PDN connection being unavailable and this triggers bearer signalling towards the MME.
2 or 3. The PGW-C/SMF currently supporting the PDN connection or the new PGW-C/SMF taking over the PDN connection may send an Update Bearer Request for the default bearer towards the SGW immediately or send Create Bearer Request (or a Update Bearer Request or a Delete Bearer Request) when the PGW-C/SMF needs to send this signalling towards the SGW and MME, including the PGW Change Info IE. The SGW shall relay transparently the PGW Change Info IE towards the MME. The PGW Change Info IE shall contain the new S5/S8 PGW IP address for control plane. The PGW-C/SMF may also include the Sender F-TEID for Control Plane IE containing a new S5/S8 PGW F-TEID for control plane. The Create/Update/Delete Bearer Response message shall be sent over S5/S8 using the S5/S8 PGW TEID for control plane received in the Sender F-TEID for Control Plane IE, if any, otherwise using the S5/S8 PGW TEID for control plane earlier assigned to the PDN connection.
NOTE 1: The MME and SGW need not know whether the Create/Update/Delete Bearer Request is originated by the same (step 2a) or a new (step 2b) PGW-C/SMF from the PGW-C/SMF Set.
NOTE 2: When establishing a PDN connection with a PGW-C/SMF of a PGW-C/SMF set, the PGW S5/S8 TEID for control plane that the PGW-C/SMF assigns in the PGW S5/S8 F-TEID for control plane needs not be unique within the PGW-C/SMF set. When the Create/Update/Delete Bearer Request is originated by the new PGW-C/SMF (step 2b), the new PGW-C/SMF can provide a new S5/S8 PGW F-TEID for control plane in the Sender F-TEID for Control Plane IE including the TEID with which it expects to receive the Create/Update/Delete Bearer Response. This new S5/S8 PGW F-TEID for control plane can be a same or different F-TEID than the S5/S8 PGW F-TEID for control plane assigned in the subsequent Create Session Response in step 5.
4. Same as step 4 of Figure 31.3-1, with the MME including in the Create Session Request the new S5/S8 PGW-C/SMF IP address received in the PGW Change Info.
5. Same as step 5 of Figure 31.3-1.
6. Same as step 6 of Figure 31.3-1.
31.4A Combined SGW-C/PGW-C/SMF triggered PDN connection restoration
A combined SGW-C/PGW-C/SMF currently supporting a PDN connection, or a new SGW-C/PGW-C/SMF from the same SGW-C/PGW-C/SMF set, may trigger a PDN connection restoration to move the PDN connection to a different SGW-C/PGW-C/SMF as defined in clause 31.4 with the following addition:
- In step 2, the (new) SGW-C/PGW-C/SMF may include a New S11 SGW-C IP Address IE in the PGW Change Info IE to request the MME to send a Create Session Request message towards the new S11 SGW-C IP address, so to enable to reuse the existing PFCP session and avoid extra signalling towards RAN to update uplink TEID at the user plane function. The (new) SGW-C/PGW-C/SMF may also include the Sender F-TEID for Control Plane IE containing a new S11 SGW-C F-TEID for control plane.
- In steps 3a and 3b, the Create/Update/Delete Bearer Response message shall be sent over S11 using the new S11 SGW-C TEID for control plane received in the Sender F-TEID for Control Plane IE, if any, otherwise using the S11 SGW-C TEID for control plane earlier assigned to the UE context.- In step 4, the MME should send the Create Session Request message towards the SGW as indicated in the New S11 SGW-C IP Address IE in the PGW Change Info IE.
NOTE: The MME can still select a new SGW other than as indicated by the New SGW-C IP Address IE when the MME determines that that SGW is more suitable for the UE e.g. based on the local policies and UE location.
31.4B PGW triggered PDN connection restoration towards ePDG
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/SMF from the same PGW-C/SMF set is reselected for the PDN connection upon a request from the PCF or the PGW-U/UPF and, more generally, when the PGW-C/SMF supporting a PDN connection is no longer available and a new PGW-C/SMF of the same PGW-C/SMF set needs to send signalling to the ePDG, before the ePDG has triggered a PDN connection restoration.
Figure 31.4B-1: PGW triggered PDN connection restoration towards ePDG
1. The PGW-C/SMF currently supporting the PDN connection or another PGW-C/SMF from the same PGW-C/SMF set determines that the PDN connection needs to be moved to a different PGW-C/SMF, e.g. during a PGW-C/SMF set scale-in operation, or e.g. due to PCF or PGW-U/UPF reselecting an alternative PGW-C/SMF from the same PGW-C/SMF set due to the PGW-C/SMF serving the PDN connection being unavailable and this triggers bearer signalling towards the ePDG.
2 or 3. The PGW-C/SMF currently supporting the PDN connection or the new PGW-C/SMF taking over the PDN connection may send an Update Bearer Request for the default bearer towards the ePDG immediately or send Create Bearer Request (or a Update Bearer Request or a Delete Bearer Request) when the PGW-C/SMF needs to send this signalling towards the ePDG, including the PGW Change Info IE. The PGW Change Info IE shall contain the new S2b PGW IP address for control plane. The PGW-C/SMF may also include the Sender F-TEID for Control Plane IE containing a new S2b PGW F-TEID for control plane. The Create/Update/Delete Bearer Response message shall be sent over S2b using the new S2b PGW TEID for control plane received in the Sender F-TEID for Control Plane IE, if any, otherwise using the S2b PGW TEID for control plane earlier assigned to the PDN connection.
NOTE 1: The ePDG needs not know whether the Create/Update/Delete Bearer Request is originated by the same (step 2a) or a new (step 2b) PGW-C/SMF from the PGW-C/SMF Set.
NOTE 2: When establishing a PDN connection with a PGW-C/SMF of a PGW-C/SMF set, the PGW S2b TEID for control plane that the PGW-C/SMF assigns in the PGW S2b F-TEID for control plane needs not be unique within the PGW-C/SMF set. When the Create/Update/Delete Bearer Request is originated by the new PGW-C/SMF (step 2b), the new PGW-C/SMF can provide a new S2b PGW F-TEID for control plane in the Sender F-TEID for Control Plane IE including the TEID with which it expects to receive the Create/Update/Delete Bearer Response. This new S2b PGW F-TEID for control plane can be a same or different F-TEID than the S2b PGW F-TEID for control plane assigned in the subsequent Create Session Response in step 5.
4. Same as step 4 of Figure 31.3A-1, with the ePDG including in the Create Session Request the new S5/S8 PGW-C/SMF IP address received in the PGW Change Info.
5. Same as step 5 of Figure 31.3A-1.
6. Same as step 6 of Figure 31.3A-1. |
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.3) for one or more PDN connections but not yet for this PDN connection, or when the source MME has sent the Create Session Request towards the new PGW-C/SMF but it has not yet received the Create Session Response message, the source MME shall set the Pending PDN connection Restoration Indication in the MME/SGSN/AMF UE EPS PDN Connections IE to "1" to request the target MME to perform the PDN connection restoration instead of contacting the PGW-C/SMF identified in the "PGW S5/S8 IP Address for Control Plane or PMIP" IE. In addition, the source MME shall include the New PGW-C/SMF IP Address and the New PGW Node Name IEs when available, e.g. when the PDN connection was requested to be moved to a specific new PGW-C/SMF during a PGW triggered PDN connection restoration procedure, or when the source MME has selected an alternative PGW-C/SMF and sent the Create Session request message to the new PGW-C/SMF to restore the PDN connection but it had not received the Create Session Response yet.
NOTE 1: A legacy target MME not supporting the Pending PDN connection Restoration Indication will contact the old PGW-C/SMF and the signalling procedure towards the old PGW-C/SMF will fail; if the target MME supports a PDN connection restoration after a PGW-C/SMF change procedure, it can select an alternative PGW-C/SMF based on the PGW Change Info included in the Forward Relocation Request message and Context Response message if available.
NOTE 2: For the case when the source MME has sent the Create Session request message to the new PGW-C/SMF to restore the PDN connection but it has not received the Create Session Response yet, the new PGW-C/SMF handles the collision when it receives the Create Session Request message originated from the target MME as specified in clause 7.2.1 of 3GPP TS 29.274 [13].
Likewise, during a EPS to 5GS mobility procedure, if the PDN connection is pending to be restored at the source MME, the source MME shall set the Pending PDN connection Restoration Indication in the MME/SGSN/AMF UE EPS PDN Connections IE to "1" to request the target AMF to perform the PDN connection restoration first instead of contacting the PGW-C/SMF identified in the "PGW S5/S8 IP Address for Control Plane or PMIP" IE. The AMF shall perform an NRF based service discovery to find an alternative PGW-C/SMF to create the corresponding PDU session in 5GS, either using the New PGW Node Name / New PGW-C/SMF IP Address if present, or selecting an alternative PGW from the PGW Change Info IE. When restoring the PDN connection to an alternative PGW-C/SMF, the AMF shall include a PGW Change Indication in the Create SmContext Request message, and the V/I-SMF shall forward the PGW Change Indication (if received) to the (H-)SMF.
During a 5GS to EPS mobility procedure (See also clauses 4.11.1.2.1 and 4.11.1.3.2 of 3GPP TS 23.502 [46]), the PGW Change Info shall be populated as part of the MME/SGSN/AMF UE EPS PDN Connections IE from the source AMF to the target MME, if available. For a Home-routed PDU session or a PDU session with an I-SMF, the (H-)SMF may pass the PGW Change Info in the EpsPdnCnxInfo to the V/I-SMF prior to the 5GS to EPS mobility procedure, to enable the V/I-SMF to include the PGW Change Info in the EpsPdnCnxContainer as part of the SmContextRetrievedData. For a non-roaming PDU session without I-SMF, the PGW-C/SMF may include the PGW Change Info directly in the EpsPdnCnxContainer.
NOTE 3: Passing the PGW Change Info from the SMF/AMF to the MME during an 5GS to EPS mobility enables the target MME to reselect an alternative PGW-C/SMF if the anchor PGW-C/SMF handling the PDU session fails before or during the handover. Requirements specified in clause 31.2 allow the target MME to reselect an alternative PGW-C/SMF if the anchor PGW-C/SMF handling the PDU session fails after the handover execution. |
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 PFCP sessions associated with certain FQ-CSIDs (when partial failure handling is supported), Group IDs or PGW-C/SMF IP Addresses, to (another) PGW-C/SMF(s) in the set, without causing massing signalling.
NOTE: The FQ-CSID can only be used in the procedure specified in this clause when the partial failure feature (using FQ-CSID) is deployed and used (not to force the NF to use a Group ID). For a network where the partial failure feature is not deployed, a Group ID or a PGW-C/SMF IP address needs to be used.
The requirements specified in this clause shall apply in addition to the previous requirements specified in clause 31. |
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 failure or a scale-in operation, a PGW-C/SMF in a PGW-C/SMF Set may:
- allocate a globally unique Group Id in the PGW Change Info IE in the Create Session Response message for a PDN connection during a PDN connection creation procedure and mobility procedure moved from 5GC without N26, or in the Modify Bearer Response for a PDN connection moved from 5GC with N26, and update the Group Id associated to the PDN connection, if necessary, in subsequent Create/Update/Delete Bearer Request messages (see also 3GPP TS 29.274 [13]);
- allocate a globally unique Group Id in the PFCP Session Establishment Request message for a PFCP session during a PFCP session establishment procedure and update the Group Id, if necessary, in subsequent PFCP Session Modification Request messages (see also clause 5.22.X of 3GPP TS 29.244 [43]).
Alternatively, if partial failure handling is supported and deployed, the PGW-C/SMF may assign an FQ-CSID to a PDN connection and/or a PFCP session as specified in clause 23.
Subsequently, e.g. when a partial or a complete failure takes place affecting all PDN connections and PFCP sessions which are sharing either the same FQ-CSID or the same Group ID (see clause 31.6.1), a PGW-C/SMF in a PGW-C/SMF Set may trigger the restoration procedure for those affected PDN connections/PFCP sessions as specified in clauses 31.6.3 and 31.6.4. |
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 complete failure), a PGW-C/SMF (either the one which experienced the partial failure or is shutting down, or another one in the same set) may trigger the PGW triggered PDN connection restoration procedure specified in clause 31.4 towards the MME or in clause 31.4a towards the ePDG, with the following additional requirements:
- in steps 2a or 2b, the PGW Change Info IE shall additionally include one or more PGW-C/SMF FQ-CSID(s) or one or more Group ID(s) or one or more PGW-C Control Plane IP Address(es), to request the MME/ePDG to re-establish all the PDN connections associated with the PGW-C/SMF FQ-CSID(s) or Group ID(s), or having their PGW S5/S8/ S2a/S2b F-TEID containing one of the PGW-C Control Plane IP Address(es), towards the new S5/S8/S2b PGW IP address for control plane. The PGW-C/SMF may instruct the MME/ePDG to move sessions associated with different PGW-C/SMF FQ-CSIDs, Group Ids or PGW-C/SMF Control Plane IP addresses to different PGW-C/SMF addresses.
31.6.3A Restoration of PDN connections associated with an FQ-CSID, Group ID or PGW-C/SMF IP Address for a combined SGW/PGW/SMF Set
When there is a need to change the combined SGW/PGW-C/SMF controlling certain PDN connections, e.g. when a partial or complete SGW/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 combined SGW/PGW-C/SMF (e.g. PDN connections affected by the partial or complete failure), a combined SGW/PGW-C/SMF (either the one which experienced the partial failure or is shutting down, or another one in the same set) may trigger the Combined SGW-C/PGW-C/SMF triggered PDN connection restoration procedure specified in clause 31.4a, with the following additional requirements:
- in steps 2a or 2b, the PGW Change Info IE shall additionally include one or more PGW-C/SMF FQ-CSID(s) or one or more Group ID(s) or one or more PGW-C Control Plane IP Address(es), to request the MME to re-establish all the PDN connections associated with the PGW-C/SMF FQ-CSID(s) or Group ID(s), or having their PGW S5/S8/ S2a/S2b F-TEID containing one of the PGW-C Control Plane IP Address(es), towards the new S5/S8 PGW IP address and the new S11 SGW-C IP Address IE for control plane. The combined SGW/PGW-C/SMF may instruct the MME to move sessions associated with different PGW-C/SMF FQ-CSIDs, Group Ids or PGW-C/SMF Control Plane IP addresses to different PGW-C/SMF addresses. |
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 Request message to the PGW-U/UPF(s) to request the PGW-U/UPF(s) to send subsequent PFCP Session Report Request messages to the alternative PGW-C/SMF (as indicated in the Alternative SMF IP Address IE) for the PFCP sessions which are associated with the FQ-CSID(s) or Group ID(s), or which have their CP F-SEID containing one of the PGW-C/SMF IP Address(es) as shown in Figure 31.6.4-1. The PGW-C/SMF may instruct the UP function to move sessions associated with different PGW-C/SMF FQ-CSID(s), Group Ids or PGW-C/SMF IP addresses, to different PGW-C/SMF addresses. Figure 31.6.4-1: PGW-C/SMF initiated PFCP Session Set Modification procedure NOTE: This procedure enables a PGW-C/SMF from the same set to take the control of multiple PFCP sessions proactively, without causing massing signalling (per PFCP session) towards the PGW-U/UPF. The use of this procecure can reduce signalling latency and achieve a better load balancing among PGW-C/SMFs. Annex A (informative): Change history Date TSG # TSG Doc. CR Rev Cat Subject/Comment New Apr 1999 Transferred to 3GPP CN1 CN#03 Approved at CN#03 3.0.0 CN#04 001 GPRS restoration procedures 3.1.0 CN#06 002r2 Authentication Enhancements 3.2.0 CN#06 003 Support of VLR and HLR Data Restoration procedures with LCS 3.2.0 CN#07 004 Support of VLR and HLR Data Restoration procedures with LCS 3.3.0 CN#08 005 Clarifications on GSM vs. UMTS specific parts 3.4.0 CN#11 Release 4 after CN#11 4.0.0 CN#16 007 Removal of an optional IMSI paging after SGSN restart 4.1.0 CN#16 Release 5 after CN#16 5.0.0 CN#22 011r1 Restoration of data in RA update 5.1.0 CN#23 008r3 Change of Restart Counter definition for enhanced GTP 6.0.0 CN#25 012 Error Indication during an ongoing MBMS data transfer 6.1.0 CN#25 013 Restoration of GSNs in MBMS 6.1.0 CT#30 0014 Incorrect References 6.2.0 CT#32 0019r1 Correction for Usage of Cancel Location for Supercharger 7.0.0 CT#40 0020r2 EPS Restoration 8.0.0 CT#41 0021r3 Moving restoration procedures from TS 23.060 into TS 23.007 8.1.0 CT#41 0023r2 Node Restart Restoration Procedures for PGW, SGW and MME 8.1.0 CT#42 0027r2 RNC failure aligns with TS23.060 8.2.0 CT#42 0028 Restoration procedures for SGs interface 8.2.0 CT#42 0033r5 Partial Failure Handling 8.2.0 CT#42 0037r1 PMIP Path management / Restoration Clean-up 8.2.0 CT#43 0030r5 Moving the description of the restoration procedures (from 29.274) to 23.007 8.3.0 CT#43 0038r4 Partial fault handling finalization 8.3.0 CT#44 0043r1 FQ-CSID corrections 8.4.0 CT#44 0047r1 SGSN and SGW handling in case RNC/BSC Failure (Iu mode) using S4 8.4.0 CT#44 0045r1 General on PMIP based restart procedure 9.0.0 CT#45 0065r1 Essential corrections to the partial failure support 9.1.0 0051 Removal of Editor's note 0053r1 Restoration of data in MBMS GW 0058r1 Echo usage for GTPv2 0063r3 Error Indication cleanup 0064r4 Restoration of data in E-UTRAN CT#46 0066 Paging signalling optimization after SGSN failure 9.2.0 0067 Paging signalling optimization after MME failure 0068 Error Indication for MBMS 0072r1 Removal of Editor's Notes for Partial Failure 0078r1 Error Indication Handling for MBMS 0080 Alignment of eNodeB failure clause 0082r3 Alignment of RNC/BSC failure clause CT#47 0091 Bulk Binding Revocation Indication 9.3.0 0082r2 Clarifications to eNodeB failure 0092r1 Reference corrections 0095r1 Restart counter correction CT#48 0100r1 Essential correction to Error Indication message handling for the default bearer 9.4.0 0076r4 Cleanup of hanging PDN connections/bearers 0097r1 Failure of remote nodes 0107r1 Optimization on hanging PDN connection cleanup 10.0.0 CT#49 0115 Data Restoration for SMS 10.1.0 0117 GTP-C based restart procedures 0121 Partial Failure handling CT#50 0135r1 Heartbeat Request 10.2.0 0129r1 ePDG Partial Failure 0133r1 Restoration of data in the ePDG 0131r1 Error Indication handling in PGW and ePDG 0132 ePDG/PGW restart and restoration 0130r1 PGW Restart Notification 0124 Essential correction to the MME and PGW restoration procedure CT#51 0142r2 Timing for sending Downlink Data Notification as a result of the SGW having received an Error Indication message from the eNodeB/RNC 10.3.0 0151r1 Unclearness of Downlink Data Notification Handling at MME/S4 SGSN as a result of the SGW having received an Error Indication message from the eNodeB/RNC 0155 eNodeB failure 0154r1 RNC failure 0148r2 Error Indication in SGW 0145r1 Error Indication for SGW 0146r5 PCRF Failure and Restoration 0152r2 Handling of UE specific Error Indication over the PMIP 0156r5 MME/SGSN restart and restoration procedure CT#52 0166r2 SGW behavior when it receives GTP error indication from S4-SGSN 10.4.0 0160r1 Fix wrong statement for the IMSI page in the Network triggered service restoration procedure 0164r2 Clarification on Network triggered service restoration procedure 0167r2 Gateway Control and QoS Policy Rules Provision Procedure handling at SGW 0161r1 Moving PCRF Restoration text under appropriate heading 0162 eNB Error Indication Handling 0163r3 MME/SGSN restart with ISR CT#53 0169r2 Signalling path failure handling 10.5.0 0175r1 Downlink Data Notification Handling at MME/S4 SGSN 0170r1 User plane path failure handling 0171r1 PMIP alighnment for the network triggered service restoration procedure CT#54 0183 Inter MME and intra SGW HO/TAU procedures 10.6.0 0176 NTSR with ISR active 0190 DDN message in the service restoration procedure 0185r2 Essential correction to Partial failure CT#54 0178 FQ-CSID Reporting 11.0.0 0168r5 CS service restoration after MME failure 0177r1 PGW restoration CT#55 0193r1 Error Indication Handling on S2a 11.1.0 0194r2 Restoration of data in the TWAN for S2a 0195r2 TWAN partial failure 0196r1 Restoration of data in the PGW for S2a 0198r1 Correction on the S4-SGSN failure 0199r1 S1 path failure handling 0201r2 IP Address of the node sending the recovery IE CT#56 0191r1 SGW Restoration procedure 11.2.0 0204r1 Missing SGSN behavior in the PGW failure 0206r1 PGW triggered SGW restoration procedure 0208 Corrections to external resources cleanup upon SGW failure CT#57 0210r2 Restoration of Data for VCSG 11.3.0 0211r1 Downlink Data Notification message handling in S4 SGSN CT#58 0209r3 PCC and PMIP impacts for the SGW restoration procedure 11.4.0 0212 Corrections to reference titles 0215r1 Handling of emergency PDN connections during EPC node restoration 0216 Corrections to reference errors 0217r3 SGW failure when ISR is active 0214r4 Handling of VLR Failure without Restart CT#58 0224r1 SGSN handling of VLR restart 11.5.0 0225r1 Fixing editor's notes in SGW restoration procedure 0226r1 The inclusion of the MME/S4-SGSN identifier IE CT#59 0218r1 Corrections to reference error for periodic location update timer 12.0.0 0220r1 MME/SGSN behaviour upon MBMS-GW restart 0221r1 eMBMS service restoration upon MCE failure or M3AP path failure 0222r1 eMBMS service restoration upon MME/SGSN restart 0223r2 Sm path failure handling CT#60 0228 Trigger for re-establishing MBMS sessions upon an M3AP path recovery 12.1.0 0239r1 MME behaviour upon MBMS GW restart 0240r SGSN behaviour upon MBMS GW restart 0237r1 BM-SC failure 0238r1 MBMS GW behaviour upon MME/SGSN restart 0236r2 MCE behavior on MME restart and MME behavior on MCE restart 0232r1 Contents of MBMS Session Start Request when re-establishing MBMS sessions 0231r2 SGmb path failure 0230r1 BM-SC behaviour upon MBMS GW restart 0229r1 Moving the control of an MBMS session to another MME 0241r2 Sn-path failure 0245r1 SGSN behaviour upon SGW restart 0234 Restoration Priority during SGW and PGW restoration procedures 0243r2 Delete Bearer Request triggered by PMIP error indication message 0242r1 Stop Paging Indication in service restoration procedure with ISR CT#61 0246r1 MBMS Session Start Request received for an on-going MBMS bearer service 12.2.0 0247r1 MBMS Session duration 0248r1 BM-SC behaviour during SGmb path failure 0249r1 MCE behavior on MME restart 0250r1 Release of resources at old MME/SGSN during transient Sm path failure 0251r1 Separate Clause for MCE and RNC restoration functionality 0252r2 Correct S-GW behaviors when a peer P-GW failed 0253r1 Correct wrong NOTE reference 0255r2 Handling of VLR Failure without Restart for MO SMS Sep 2013 Clause numbers correcterd in clause 17A.2. Style correction also in clause 27.2.2.2. 12.2.1 Dec 2013 0265r2 Correction of reference to Update Notifications for Proxy Mobile IPv6 12.3.0 0271r2 Error handling when the PCC rule is removed due to the S-GW restoration support 0256r1 Cause "GTP Resources Unavailable" handling at the SGSN 0258r6 Restoration of warning message delivery upon eNB failure/restart 0259 M3AP path recovery 0261r2 S4-SGSN procedure upon RNC and Iu path failure 0266r2 Non transient SGmb path failure 0267r2 Detection of peer MBMS node restart and SGmb path failure/recovery 0268r2 Non-transient SGi-mb path failure Mar 2014 0263r6 SGW behaviour upon GTP Error indication 12.4.0 0277r1 Correct the PCRF procedure during the SGW restoration 0273r1 Update the reference of IETF draft Update Notifications for Proxy Mobile IPv6 to RFC 7077 0282r2 Handling of "GTP Resources Unavailable" cause in S4-SGSN 0275r1 PWS Restart Indication parameters Jun 2014 0274r3 Sm path failure recovery 12.5.0 0283r1 SGmb path failure recovery 0288r1 M1 and/or M3/Iu resources modification during MBMS session re-establishment 0289 MCE Failure 0291r1 SGmb path failure 0284r1 Handling of E-RAB Release due to GTPU error indication for default bearer at MME 0296r2 Update SGW behaviours after receiving PMIP error indication 0285 PWS Restart Indication parameters 0286r2 HeNB ID verification in the PWS Restart Indication message 0287r2 Routing of PWS messages to HeNBs 0298r2 SGW restoration when S5 path failure occurs 0290 Restoring the (S)Gs associations during tracking/routing area update procedures Sep 2014 0300r2 Correct procedure name for PDN connection deactivation 12.6.0 0301r3 Handling of GTP Error Indication for Dual connectivity 0302r2 Restoration for HSS Reset 0304r1 Remove Editor's note for S5 path failure Dec 2014 0307 Warning Area List in Write-Replace Warning Request during PWS restoration 12.7.0 0308r1 Serial Number in Write-Replace Warning Request during PWS restoration 0309 GCSE restoration procedures upon BM-SC restart 0310r1 GCSE restoration procedures upon GCS AS restart 0311r1 GCSE restoration procedures upon MB2-C path failure 0312 GCSE restoration procedures upon SGi-mb path failure 0314r1 GTP-C based restart procedures for HRPD Mar 2015 0316r2 SGW restoration procedure in PMIP case 12.8.0 Mar 2015 0317r1 Deferring GBR bearers deactivation upon S1 Reset or S1AP path failure 13.0.0 Jun 2015 0318r1 MCE configuration update after an MBMS restoration 13.1.0 Sep 2015 0320r1 HSS Reset 13.2.0 Dec 2015 0321r2 Services restoration for UEs using extended idle mode DRX 13.3.0 0326r2 DTCI for restoration procedure 0323r1 Implementation mistake of CR 0309 and CR 0310 0324r2 HSS restart MONTE impacts 0325r2 SCEF restart and MONTE impacts 0327r2 SGW Restoration in Dedicated Core Network Mar 2016 0329r2 HSS restart and resultant MONTE impacts 13.4.0 0330r2 Restart of SCEF 0331r1 Correct the partial failure handling on SGW 0332r1 S11-U Error Indication handling 0334r3 Behaviours upon receipt of unknown NIDD 0335r3 Enhance restoration procedure to be compatible with SCEF PDN connection and Attach without PDN connectivity 0336r2 Connection Resume procedure used during restoration 2016-06 CT#72 CP-160228 0337 3 MME handling of GTP Error Indication and MO-Data-Answer (failure) 13.5.0 2016-06 CT#72 CP-160231 0338 2 PGW restoration in NBIFOM case 13.5.0 2016-06 CT#72 CP-160234 0340 3 Restoration impact on the introduction of UE context retention at SCTP recovery 13.5.0 2016-06 CT#72 CP-160217 0341 1 Behaviours upon receipt of unknown NIDD (SGSN case) 14.0.0 2016-09 CT#73 CP-160422 0343 1 Failure case for NBIFOM 14.1.0 2017-03 CT#75 CP-170043 0344 1 Restoration Support for V2X Service 14.2.0 2017-03 CT#75 CP-170040 0345 1 Network triggered service restoration for PSM UE 14.2.0 2017-06 CT#76 CP-171036 0348 1 User Plane Path Failure with Control and User Plane Separation of SGW and PGW 14.3.0 2017-06 CT#76 CP-171023 0350 1 Service Restoration for UEs in extended DRX mode 14.3.0 2017-06 CT#76 CP-171036 0351 3 CUPS restoration procedures in SGW-C and SGW-U 14.3.0 2017-06 CT#76 CP-171036 0352 2 Partial failure handling for CUPS 14.3.0 2017-06 CT#76 CP-171036 0353 2 CUPS restoration procedures PGW-C and PGW-U 14.3.0 2017-06 CT#76 CP-171036 0354 1 CUPS restoration procedures 14.3.0 2017-12 CT#78 CP-173019 0355 - Clarification on SGmb path failure 14.4.0 2018-06 - - - - Update to Rel-15 version (MCC) 15.0.0 2018-09 CT#81 CP-182079 0357 - Corrections on CUPS restorations 15.1.0 2018-09 CT#81 CP-182078 0358 2 S1-U Path Failure Enhancement 15.1.0 2019-03 CT#83 CP-190040 0359 5 Recovery Time Stamp in PFCP 15.2.0 2019-06 CT#84 CP-191024 0363 2 Corrrections to the restoration procedures for PFCP entities 15.3.0 2019-09 CT#85 CP-192096 0364 - Heartbeat procedure 15.4.0 2019-12 CT#86 CP-193041 0368 - GTP Recovery Counter and GSN node behaviour 16.0.0 2019-12 CT#86 CP-193045 0365 1 PFCP Association Setup Request with same Node ID 16.0.0 2019-12 CT#86 CP-193045 0367 1 Reestablishment of PFCP sessions after a UP function restart 16.0.0 2020-03 CT#87e CP-200038 0369 - The Source IP Address in Heartbeat Request message 16.1.0 2020-03 CT#87e CP-200038 0370 1 The Recovery Time Stamp in PFCP Session Establishment Request message 16.1.0 2020-03 CT#87e CP-200021 0371 1 URCMP based restart procedures 16.1.0 2020-12 CT#90e CP-203061 0372 3 Restoration of PDN connections after a PGW-C/SMF change 17.0.0 2021-06 CT#92e CP-211043 0373 2 Restoration of PFCP sessions and PDN connections affected by a partial or complete failure 17.1.0 2021-06 CT#92e CP-211043 0374 2 Combined S/PGW restart 17.1.0 2021-09 CT#93e CP-212033 0375 1 B Restoration of PDN connections served by a combined SGW/PGW in a Set 17.2.0 2021-12 CT#94e CP-213095 0376 - B SGW IP Address for a combined SGW/PGW/SMF 17.3.0 2022-03 CT#95e CP-220033 0379 3 B ePDG support of Restoration of PDN connections after a PGW-C/SMF change 17.4.0 2022-03 CT#95e CP-220033 0380 1 B New SGW IP Address when moving PDN connections for a combined SGW/PGW/SMF set 17.4.0 2022-03 CT#95e CP-220037 0378 1 B Detection and reporting of the restart of a GTP-U entity 17.4.0 2022-03 CT#95e CP-220086 0381 1 B Enhanced handling at user plane path failure 17.4.0 2022-03 Editorial corrections 17.4.1 2022-09 CT#97e CP-222023 0382 - B Populating PGW Change Info during 5GS to EPS mobility procedure 18.0.0 2022-12 CT#98e CP-223046 0384 1 F PGW triggered PDN connection restoration 18.1.0 2023-06 CT#100 CP-221074 0386 1 A PGW-C TEID in Update Bearer Response during PGW triggered PDN connection restoration 18.2.0 2023-06 CT#100 CP-221074 0388 - A Corrections to Restoration of PDN connections after a PGW-CSMF change 18.2.0 2023-06 CT#100 CP-221074 0390 1 A MME or ePDG triggered PDN connection restoration 18.2.0 2023-06 Editorial correction in section 31.4 18.2.1 2023-12 CT#102 CP-233044 0391 - F Operation Indication in the Create Session Request 18.3.0 2024-03 CT#103 CP-240061 0393 - A IEs in CSReq/CSRsp during an MME or ePDG triggered PDN connection restoration 18.4.0 2024-06 CT#104 CP-241055 0397 1 A IEs in Create Session Request/Response during the restoration of a PDN connection after a PGW-C/SMF change 18.5.0 2024-06 CT#104 CP-241050 0395 1 F PGW Restart Notification and Acknowledgement 18.5.0 2024-09 CT#105 CP-242033 0398 1 B PDN Connection Restoration Indication 19.0.0 2024-12 CT#106 CP-243032 0399 - B Including Pending PDN Connection Restoration Indication during EPS to 5GS mobility 19.1.0 |
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 by reference to other specifications, and where the parameter is to be stored.
Table 1 in clause 3 gives a summary overview and clause 4 identifies the reference information required for accessing the information.
In this specification, if there is no specific indication, the following principles apply:
- "SGSN" refers to an SGSN which may support the Gn and Gp interfaces or the S4 interface or both.
- "S4-SGSN" refers to an SGSN which only supports the S4 interface.
- "Gn/Gp-SGSN" refers to an SGSN which only supports the Gn and Gp interfaces. |
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.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".
[2] 3GPP TS 22.002: "Circuit Bearer Services (BS) supported by a Public Land Mobile Network (PLMN)".
[3] Void
[4] Void
[5] 3GPP TS 23.003: "Numbering, addressing and identification".
[6] 3GPP TS 23.007: "Restoration procedures".
[7] 3GPP TS 23.009: "Handover procedures".
[8] 3GPP TS 23.012: "Location Management Procedures".
[9] 3GPP TS 23.015: "Technical realization of Operator Determined Barring (ODB)".
[10] 3GPP TS 23.040: "Technical realization of the Short Message Service (SMS)".
[11] 3GPP TS 22.060: "General Packet Radio Service (GPRS); Service description; Stage 1".
[12] 3GPP TS 23.067: "Enhanced Multi‑Level Precedence and Preemption service (EMLPP); Stage 2".
[13] Void
[14] 3GPP TS 23.081: "Line identification supplementary services; Stage 2".
[15] Void
[16] Void
[17] Void
[18] 3GPP TS 23.085: "Closed User Group (CUG) Supplementary Service; Stage 2".
[19] Void
[20] Void
[21] 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service Description; Stage 2".
[22] Void
[23] Void
[24] Void
[25] 3GPP TS 23.135: "Multicall supplementary service; Stage 2"
[26] 3GPP TS 24.008: "Mobile radio interface Layer 3 specification; Core network protocols; Stage 3".
[27] 3GPP TS 29.002: "Mobile Application Part (MAP) specification".
[28] 3GPP TS 29.007: "General requirements on interworking between the Public Land Mobile Network (PLMN) and the Integrated Services Digital Network (ISDN) or Public Switched Telephone Network (PSTN)".
[29] 3GPP TS 29.060: "General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp interface".
[30] 3GPP TS 42.032: "Digital cellular telecommunications system (Phase 2+); Immediate Service Termination (IST) Service description - Stage 1".
[31] 3GPP TS 43.020: "Digital cellular telecommunications system (Phase 2+); Security-related network functions".
[32] 3GPP TS 43.035: "Digital cellular telecommunications system (Phase 2+); Immediate Service Termination (IST); Stage 2".
[33] 3GPP TS 43.068: "Digital cellular telecommunications system (Phase 2+); Voice Group Call Service (VGCS); Stage 2".
[34] 3GPP TS 43.069: "Digital cellular telecommunications system (Phase 2+); Voice Broadcast Service (VBS); Stage 2".
[35] 3GPP TS 23.071: "Location Services (LCS); Functional Description; Stage 2".
[36] GSM 12.03: "Digital cellular telecommunications system (Phase 2+) (GSM); Security management".
[37] 3GPP TS 52.008: "GSM Subscriber and equipment trace".
[38] ITU-T Recommendation Q.763: "Signalling System No. 7 - ISDN User Part formats and codes".
[39] ANSI T1.113: "Signalling System No7 (SS7); Integrated Services Digital Network (ISDN) User Part"
[40] 3GPP TS 32. 250: "Telecommunication Management; Charging management; Circuit Switched (CS) domain charging".
[41] 3GPP TS 32. 251: "Telecommunication Management; Charging management; Packet Switched (PS) domain charging".
[42] 3GPP TS 23.228: "IP Multimedia Subsystem (IMS); Stage 2".
[43] 3GPP TS 29.228: "IP Multimedia (IM) Subsystem Cx and Dx interfaces; Signalling flows and message contents".
[44] 3GPP TS 29.229: "Cx and Dx Interfaces based on the Diameter protocol; Protocol details".
[45] IETF RFC 3261: "SIP: Session Initiation Protocol".
[46] IETF RFC 2396: "Uniform Resource Identifiers (URI): Generic Syntax".
[47] Void
[48] IETF RFC 4282: "The Network Access Identifier".
[49] 3GPP TS 33.203: "3G security; Access security for IP-based services".
[50] 3GPP TS 23.002: "Network Architecture".
[51] IETF RFC 3588: "Diameter Base Protocol".
[52] 3GPP TS 33.102: "3G Security; Security Architecture".
[53] 3GPP TS 23.218: "IP Multimedia (IM) session handling; IM call model; Stage 2".
[54] 3GPP TS 29.328: "IP Multimedia Subsystem (IMS) Sh interface signalling flows and message contents".
[55] Void
[56] 3GPP TS 23.271: "Location Services (LCS); Functional description; Stage 2".
[57] 3GPP TS 23.221: "Architectural requirements ".
[58] 3GPP TS 33.220: "Generic Authentication Architecture (GAA);Generic bootstrapping architecture".
[59] 3GPP TS 29.109 "Zh and Zn Interfaces based on the Diameter protocol; Protocol details".
[60] IETF RFC 3548: "The Base16, Base32, and Base64 Data Encodings".
[61] 3GPP TS 23.251: "Network Sharing; Architecture and Functional Description".
[62] 3GPP TS 23.234, Release 12: "3GPP Systen to WLAN Interworking System Description, Stage 2".
[63] 3GPP TS 29.234, Release 11: "3GPP system to Wireless Local Area Network (WLAN), Stage 3".
[64] 3GPP TS 32.422: "Subscriber and equipment trace: Trace control and configuration management".
[65] 3GPP TS 32.421: "Subscriber and equipment trace: Trace concepts and requirements".
[66] 3GPP TS 32.252, Release 11: "Telecommunication management; Charging management; Wireless Local Area Network (WLAN) charging".
[67] 3GPP TS 32.299: "Telecommunication management; Charging management; Diameter charging applications".
[68] 3GPP TS 24.229: "IP Multimedia Call Control Protocol based on SIP and SDP – stage 3"
[69] Void
[70] 3GPP TS 23.018: "Basic call handling; Technical realization".
[71] 3GPP TS 23.292: "IP Multimedia Subsystem (IMS) Centralized Services"
[72] Void
[73] 3GPP TS 33.401: "3GPP System Architecture Evolution (SAE); Security architecture"
[74] 3GPP TS 23.401: "General Packet Radio Service (GPRS) enhancements for
Evolved Universal Terrestrial Radio Access Network
(E-UTRAN) access"
[75] 3GPP TS 29.274: "Evolved GPRS Tunneling Protocol for Control Plane"
[76] 3GPP TS 32.298: "Telecommunication Management; Charging Management; Charging Data Record (CDR) parameter classification."
[77] 3GPP TS 23.402: "Architecture enhancements for non-3GPP accesses "
[78] 3GPP TS 29.273: "3GPP EPS AAA Interfaces"
[79] 3GPP TS 29.275: "Proxy Mobile IPv6 (PMIPv6) based Mobility and Tunneling protocols"
[80] 3GPP TS 23.216: "Single Radio Voice Call Continuity (SRVCC), Stage 2"
[81] 3GPP TS 29.272: "MME Related Interfaces Based on Diameter Protocol"
[82] 3GPP TS 24.302: "Access to the 3GPP Evolved Packet Core (EPC) via non-3GPP access networks; Stage 3"
[83] 3GPP TS 29.305: "InterWorking Function (IWF) between MAP based and Diameter based interfaces"
[84] 3GPP TS 32.251: "Telecommunication management; Charging management; Packet Switched (PS) domain charging"
[85] 3GPP TS 23.246: "Multimedia Broadcast/Multicast Service (MBMS); Architecture and functional description; Stage 2".
[86] 3GPP TS 24.312: "Access Network Discovery and Selection Function (ANDSF) Management Object (MO)".
[87] 3GPP TS 23.237: "IP Multimedia Subsystem (IMS) Service Continuity; Stage 2".
[88] 3GPP TS 36.300: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2".
[89] 3GPP TS 23.167: "IP Multimedia Subsystem (IMS) emergency sessions".
[90] 3GPP TS 29.212: "Policy and Charging Control (PCC); Reference points".
[91] 3GPP TS 23.139: "3GPP System-Fixed Broadband Access Network Interworking; Stage 2".
[92] 3GPP TS 33.234, Release 12: "WLAN Interworking Security".
[93] 3GPP TS 23.107: "Quality of Service (QoS) concept and architecture ".
[94] Void
[95] 3GPP TS 23.468: "Group Communication System Enablers for LTE (GCSE_LTE); stage 2".
[96] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification".
[97] 3GPP TS 36.323: "Evolved Universal Terrestrial Radio Access (E-UTRA); Packet Data Convergence Protocol (PDCP) Specification".
[98] 3GPP TS 23.303: "Proximity-based services (ProSe); stage 2".
[99] 3GPP TS 29.344: "Proximity-services (ProSe) Function to Home Subscriber Server (HSS) aspects; Stage 3".
[100] 3GPP TS 24.334: "Proximity-services (ProSe) User Equipment (UE) to ProSe function protocol aspects; Stage 3".
[101] 3GPP TS 36.413: "Evolved Universal Terrestrial Radio Access Network; (E-UTRAN); S1 Application Protocol (S1AP)".
[102] 3GPP TS 23.682: "Architecture enhancements to facilitate communications with packet data networks and applications".
[103] 3GPP TS 29.336: "Home Subscriber Server (HSS) diameter interfaces for interworking with packet data networks and applications".
[104] IETF RFC 4995: "The RObust Header Compression (ROHC) Framework".
[105] 3GPP TS 24.301: "Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3".
[106] 3GPP TS 29.128: "Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) interfaces for interworking with packet data networks and applications ".
[107] 3GPP TS 23.285: "Architecture enhancements for V2X services; Stage 2".
[108] 3GPP TS 29.388: "V2X Control Function to V2X Control Function to Home Subscriber Server (HSS) aspects (V4)".
[109] 3GPP TS 29.389: "Inter-V2X Control Function Signalling aspects (V6); Stage 3".
[110] IETF RFC 6696: "EAP Extensions for the EAP Re-authentication Protocol (ERP)".
[111] 3GPP TS 24.323: "3GPP IP Multimedia Subsystem (IMS) service level tracing management object (MO)".
[112] 3GPP TS 23.501: "System Architecture for the 5G System; Stage 2".
[113] 3GPP TS 23.502: "Procedures for the 5G System; Stage 2"..
[114] 3GPP TS 29.503: "5G System; Unified Data Management Services"
[115] 3GPP TS 23.379: "Functional architecture and information flows to support Mission Critical Push To Talk (MCPTT); Stage 2".
[116] 3GPP TS 33.501: "Security Architecture and Procedures for 5G System".
[117] 3GPP TS 35.206: "An example algorithm set for the 3GPP authentication and key generation functions f1, f1*, f2, f3, f4, f5 and f5*; Document 2: Algorithm specification".
[118] 3GPP TS 35.231: "A second example algorithm set for the 3GPP authentication and key generation functions f1, f1*, f2, f3, f4, f5 and f5*; Document 1: Algorithm specification ".
[119] 3GPP TS 29.505: "5G System; Usage of the Unified Data Repository services for Subscription Data ".
[120] 3GPP TS 23.316: "Wireless and wireline convergence access support for the 5G System (5GS)".
[121] 3GPP TS 23.273: "5G System (5GS) Location Services (LCS); Stage 2".
[122] IETF RFC 7616: "HTTP Digest Access Authentication".
[123] IETF RFC 4648: "The Base16, Base32, and Base64 Data Encodings". |
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 permanent subscriber data, i.e. they can only be changed by administration means. Other data are temporary subscriber data which may change as a result of normal operation of the system.
Unless shown to be conditional, all data items are considered to be mandatory. |
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.
- Home location register (HLR) which contains all permanent subscriber data and all relevant temporary subscriber data for all mobile subscribers permanently registered in the HLR for CS and PS Domains.
NOTE 0: according to 3GPP TS 23.002 [50] HLR is a subset of the HSS functionality.
- CSG subscriber server (CSS) which contains Closed Subscriber Group information data for inbound roaming UEs to enable VPLMN autonomous CSG roaming in CS and PS domains.
- Visitor location register (VLR) which contains all subscriber data required for call handling and other purposes for mobile subscribers currently located in the area controlled by the VLR.
- Serving GPRS Support Node (SGSN) which contains all subscriber data required for GPRS mode transmission and other purposes for mobile subscribers currently located in the area controlled by the SGSN.
- Gateway GPRS Support Node (GGSN) which contains all subscriber data required for GPRS mode transmission for mobile subscribers using any service provided by the GGSN.
- Mobility Management Entity (MME) which contains all subscriber data required for EPS mode transmission and other purposes for mobile subscribers currently located in the area controlled by the MME.
- Serving GW (S-GW) which contains all subscriber data required for EPS mode transmission for mobile subscribers currently served by the S-GW.
- PDN GW (P-GW) which contains all subscriber data required for EPS mode transmission for mobile subscribers using any service provided by the P-GW.
- ePDG which contains all subscriber data required for EPS mode transmission for mobile subscribers currently served by the ePDG via a non 3GPP access.
- Gateway Mobile Location Center (GMLC) which contains all subscriber data required for external clients of the Location Services (LCS).
- In GSM, Serving Mobile Location Center (SMLC) which contains all LMU data required to manage location measurements in LMUs.
NOTE 1: A type A LMU is a network entity that shares many of the attributes of an MS including subscription data in the HLR and identification using an IMSI.
- Serving Call Session Control Function (S-CSCF) which handles the session states in the IP Multimedia (IM) Subsystem. Further definition of the S-CSCF is provided in 3GPP 23.228 [42].
- SUPL (Secure User Plane Location) Location Platform (SLP) provides user location information to the ProSe Function. Further information is provided in 3GPP TS 23.303 [98].
- ProSe Function is the logical function that is used for network related actions required for Proximity services more details are provided in 3GPP TS 23.303 [98].
- ProSe Application Server stores EPC ProSe User IDs and ProSe Function IDs and performs the mapping of Application Layer User IDs and EPC ProSe User Ids (see 3GPP TS 23.303 [98]).
- V2X Control Function is the logical function that is used for network related actions required for V2X services more details are provided in 3GPP TS 23.285 [107].
- UDM, AMF, SMF, SMSF, AUSF and NEF in 5G System (see 3GPP TS 23.501 [112] and 3GPP TS 23.502 [113]).
NOTE 2: Whether a node stores data for later usage in the UDR (externally) is not reflected, the description only reflects that the node holds data logically. Whether storage of data is performed internally or externally is out of scope of this specification.
In addition, subscriber data may also be stored in the following functional unit:
- Group Call Register (GCR) which contains all data required for configuration, set-up and handling of voice group and voice broadcast calls. This encompasses subscribers identities (mobile as well as fixed network) who are nominated as dispatchers for one or several groups within the area controlled by the GCR.
NOTE 3: The data stored in the GCR is not strictly "subscriber data". Description of GCR data is therefore out of scope of this specification and is covered in the corresponding specifications for enhanced Multi Level Precedence and Pre-emption Service (eMLPP), Voice Group Call Service (VGCS) and Voice Broadcast Service (VBS) instead (3GPP TS 23.067 [12], 3GPP TS 43.068 [33] and 3GPP TS 43.069 [34]).
NOTE 4: The MME, SGSN and ePDG Emergency Configuration Data, which are applied for all emergency bearer services, are not subscriber data and therefore out of the scope of this specification. See 3GPP TS 23.401 [74], 3GPP TS 23.060 [21] and 3GPP TS 23.402 [77]. |
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 bootstrapping information after bootstrapping procedure in Generic Authentication Architecture (GAA) system. A bootstrapping procedure creates security association between an UE and a BSF. Using the stored user's bootstrapping information and the security association the BSF can provide security services to network application functions (NAF) contacted by the UE. Functions of the BSF are defined in 3GPP TS 33.220 [58] and 3GPP TS 29.109 [59].
NOTE: It is for further study whether or not other types of functional units containing mobile subscriber parameters are to be included in this specification. Such units could include encryption key distribution centres, maintenance centres, etc. |
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 in the VPLMN and to provide charging inter operator settlement functionality.
- Packet Data Gateway (PDG) which contains all subscriber data necessary to manage WLAN 3GPP IP Access tunnels.
- WLAN Access Gateway (WAG) which contains all subscriber data necessary to manage a per user firewall between the WLAN-AN and PLMN and to perform per tunnel charging. |
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 | |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.1.1.1 International Mobile Subscriber Identity (IMSI) | International Mobile Subscriber Identity (IMSI) is defined in 3GPP TS 23.003 [5].
IMSI is permanent subscriber data. IMSI is stored in HLR, HSS, CSS, VLR, SGSN, S4-SGSN, GGSN, MME, S-GW, P-GW, ePDG, SCEF and SMLC. For Anonymous Access, IMSI is not used in SGSN nor in GGSN. The IMSI serves as the root of the subscriber data pseudo-tree.
For emergency attached UEs without IMSI (e.g; UICCless UE) or with an unauthenticated IMSI, IMEI is used instead of IMSI to identify the UE. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.1.1.2 Network Access Mode (NAM) | The Network Access Mode (NAM) defines if the subscriber is registered to get access to the CS domain (non-GPRS/EPS), to the PS domain (GPRS/EPS) or to both domains using 3GPP access networks. NAM describes the first level of the subscriber data pseudo-tree below the IMSI root. It is permanent subscriber data stored in the HSS/HLR and the SGSN with the Gs interface option, and the MME with the SGs interface option. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.1.1.3 IMSI Unauthenticated indicator | For an emergency attached UE with an unauthenticated IMSI, the IMSI Unauthenticated indicator is set to reflect that the IMSI is unauthenticated. See 3GPP TS 23.401 [74], 3GPP TS 23.060 [21] and 3GPP TS 23.402 [77].
The IMSI Unauthenticated indicator is a temporary subscriber data stored in the MME, S-GW, P-GW, SGSN, S4-SGSN, GGSN and ePDG. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.1.2 Mobile Station International ISDN Number (MSISDN) | Mobile Station ISDN Number (MSISDN) is defined in 3GPP TS 23.003 [5].
The MSISDN is permanent subscriber data and is conditionally stored in HLR, VLR, SGSN, GGSN, HSS, MME, S-GW, P-GW, SCEF, 3GPP AAA Server and ePDG(for GTP-based S2b only), and is optionally stored in CSS. If the multinumbering option applies, the MSISDN stored in the VLR and in the Gn/Gp-SGSN is the Basic MSISDN, see clause 2.1.3.1. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.