hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
595
| content
stringlengths 0
6.67M
|
|---|---|---|---|
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. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.1.3 MSISDNs for multinumbering option | If the HPLMN allocates different MSISDNs for different Basic Services (see 3GPP TS 29.007 [28]), these numbers are conditionally stored as permanent data in the HLR. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.1.3.1 The Basic MSISDN indicator | The Basic MSISDN is defined in 3GPP TS 23.012 [8]. The Basic MSISDN indicator marks the MSISDN to be used as Basic MSISDN.
It is permanent subscriber data stored conditionally in the HLR. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.1.3.2 The MSISDN-Alert indicator | The MSISDN-Alert is defined in 3GPP TS 23.040 [10]. The MSISDN-Alert indicator marks the MSISDN to be used as MSISDN-Alert.
It is permanent subscriber data stored conditionally in the HLR. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.1.4 Temporary mobile subscriber identity (TMSI) | Temporary mobile subscriber identity (TMSI) is defined in 3GPP TS 23.003 [5].
The TMSI is temporary subscriber data and is conditionally stored in the VLR. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.1.5 Packet-Temporary Mobile Subscriber Identity (P-TMSI) | Packet-Temporary Mobile Subscriber Identity (P-TMSI) is defined in 3GPP TS 23.003 [5]. Its usage is described in 3GPP TS 23.060 [11]. P-TMSI is accompanied by the P-TMSI Signature, see clause 2.3.7.
The P-TMSI is temporary subscriber data and is conditionally stored in the SGSN. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.1.6 Temporary Link Layer Identifier (TLLI) | Temporary Link Layer Identifier (TLLI) is defined in 3GPP TS 23.003 [5]. It is derived from the P-TMSI by the MS and occurs in the variants Local TLLI and Foreign TLLI. The TLLI is temporary subscriber data and is conditionally stored in the SGSN. For use of TLLI see 3GPP TS 23.060 [11]. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.1.7 Random TLLI | Random TLLI is chosen randomly by the MS. It is defined in 3GPP TS 23.003 [5]. Random TLLI is short living temporary subscriber data and is conditionally stored in the SGSN. For use of Random TLLI see 3GPP TS 23.060 [11].
A Random TLLI may be used if no valid P-TMSI is available. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.1.8 Local Mobile Station Identity (LMSI) | Local Mobile Station Identity (LMSI) is defined in 3GPP TS 23.003 [5]. The LMSI is temporary subscriber data. The LMSI may be stored in the VLR; if it is received in the HLR it must be stored there. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.1.9 International Mobile Equipment Identity (IMEI) | International Mobile Equipment Identity (IMEI) is defined in 3GPP TS 23.003 [5]. The IMEI is temporary subscriber data and is conditionally stored in the HSS, SGSN, S4-SGSN, GGSN, MME, SGW, PGW, ePDG and 3GPP AAA Server. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.1.10 External Identifier Set | The External Identifier set contains one or more External Identifier as defined in 3GPP TS 23.003 [5].
Any one of the External Identifier from the IMSI's External Identifier Set shall uniquely identify a single subscriber (IMSI).
The External Identifier Set is permanent subscriber data and is stored in the HSS and conditionally in the SCEF. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.1.11 UE radio capability ID | The UE radio capability ID is defined in 3GPP TS 23.003 [5]. Its usage is described in 3GPP TS 23.401 [74].
The UE radio capability ID is temporary subscriber data and is conditionally stored in the MME. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.2 Data related to Mobile Station types | |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.2.1 Mobile Station Category | Mobile Station Category has a structure identical to that of "Calling Party's Category" defined in ISUP (ITU‑T Recommendation Q.763 [38]).
The following values of category shall be supported:
- ordinary subscriber.
The category is assigned per IMSI.
Mobile Station Category is permanent subscriber data and is stored in HLR and VLR. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.2.2 LMU Identifier (GSM only) | The LMU identifier is part of the subscriber data for a Type A LMU, when associated with an NSS based SMLC, and serves to distinguish a Type A LMU from a normal MS. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.2.3 International Mobile Equipment Identity and Software Version (IMEISV) | International Mobile Equipment Identity and Software Version (IMEISV) is defined in 3GPP TS 23.003 [5]. The IMEISV is temporary subscriber data and is conditionally stored in the VLR, SGSN, HLR, S4-SGSN, GGSN, MME, SGW, PGW, ePDG and 3GPP AAA Server. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.3 Data related to authentication and ciphering | |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.3.1 Random Number (RAND), Signed Response (SRES) and Ciphering Key (Kc) | Random Number (RAND), Signed Response (SRES) and Ciphering Key (Kc) form a triplet vector used for authentication and encryption as defined in 3GPP TS 43.020 [31].
For GSM users, triplet vectors are calculated in the 2G AuC and provided to the 2G HLR (see GSM 12.03 [36]), and for UMTS users triplet vectors are derived from quintuplet vectors in the 3G HLR or 3G VLR, if needed (see 3GPP TS 33.102 [52]).
A set of up to 5 triplet values are sent from the 2G HLR to the VLR and the SGSN on request. These data are temporary subscriber data conditionally stored in the VLR and the SGSN. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.3.2 Random Challenge (RAND), Expected Response (XRES), Cipher Key (CK), Integrity Key(IK) and Authentication Token(AUTN), KASME | Random Challenge (RAND), Expected Response (XRES), Cipher Key (CK), Integrity Key(IK) and Authentication Token (AUTN) form a quintuplet vector used for user authentication, data confidentiality and data integrity as defined in 3GPP TS 33.102 [52].
Random Challenge (RAND), Expected Response (XRES), Key for Access Security Management Entity (KASME) and Authentication Token (AUTN) form an EPS vector used for user authentication, data confidentiality and data integrity as defined in 3GPP TS 33.401 [73].
When both HLR and VLR or SGSN are 3G, a set of quintuplet vectors are calculated in the AuC, and up to 5 quintuplets are sent from the HLR to the VLR and to the SGSN on request (see 3GPP TS 29.002 [27]). These data are temporary subscriber data conditionally stored in the HLR, the VLR and the SGSN.
When the HLR is 2G and the VLR or SGSN are 3G, quintuplet vectors are derived by the 3G VLR or SGSN from the received triplet vectors from the HLR, if needed (see 3GPP TS 33.102 [52]). |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.3.3 The Ciphering Key Sequence Number (CKSN) | The Ciphering Key Sequence Number (CKSN) is used to ensure GSM authentication information (Kc) consistency between the MS and the VLR and between the MS and the SGSN.
CKSN and its handling are defined in 3GPP TS 24.008 [26] and 3GPP TS 43.020 [31]. It is a temporary subscriber data and is stored in the VLR and in the SGSN. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.3.4 The Key Set Identifier (KSI) | The Key Set Identifier (KSI) is used to ensure UMTS authentication information (CK and IK) consistency between the MS and the VLR and between the MS and the SGSN.
For EPS the Key Set Identifier (KSI also noted KSIASME ) is used to ensure EPS authentication information (KASME) consistency between the MS and the MME.
KSI and its handling are defined in UMTS TS 24.008 [26] and UMTS TS 33.102 [52]. It is temporary subscriber data and is stored in the VLR and the SGSN.
KSIASME and its handling are defined in 3GPP TS 23.401[74]. It is temporary subscriber data and is stored in the MME. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.3.5 Selected Ciphering Algorithm | Selected Ciphering Algorithm is defined in 3GPP TS 23.060 [21].
Selected Ciphering Algorithm is temporary subscriber data stored in the SGSN. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.3.6 Current Kc | Current Kc is defined in 3GPP TS 43.020 [31].
Current Kc is temporary subscriber data stored in the SGSN. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.3.7 P-TMSI Signature | P-TMSI Signature is defined in TSs 3GPP TS 23.003 [5] and 3GPP TS 23.060 [21]. It is used for identification checking purposes.
P-TMSI Signature is temporary subscriber data and is conditionally stored in the SGSN. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.3.8 Access Network Identity (ANID) | Access Network Identity is defined in TSs 3GPP TS 24.302 [82] and 3GPP TS 29.273 [78].
ANID is temporary subscriber data stored in HSS and 3GPP AAA server. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.3.9 Key Status | Key Status is defined in 3GPP TS 25.413 [120].
Key Status is temporary subscriber data stored in VLR and SGSN. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.4 Data related to roaming | |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.4.1 Mobile Station Roaming Number (MSRN) | Mobile Station Roaming Number (MSRN) is defined in 3GPP TS 23.003 [5].
NOTE: There may be more than one MSRN simultaneously per IMSI.
The MSRN is short-lived temporary subscriber data stored in the VLR. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.4.2 Location Area Identification (LAI) | Location Area Identification (LAI) is defined in 3GPP TS 23.003 [5].
The LAI is temporary subscriber data and is stored in the VLR. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.4.3 Routing Area Identification (RAI) | Routing Area Identification (RAI) is defined in 3GPP TS 23.003 [5].
The RAI is temporary subscriber data and is stored in the SGSN. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.4.4 Void | |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.4.5 VLR number | VLR number is defined in 3GPP TS 23.003 [5].
The VLR number is temporary subscriber data and is stored in the HLR. Absence of the VLR number in HLR indicates that the mobile station is deregistered for non-GPRS or the subscriber has not a non-GPRS subscription in the HLR. The VLR number is stored in the SGSN with the Gs interface option. For usage of the VLR number in SGSN, please refer to 3GPP TS 23.060 [21].
The VLR number is temporary subscriber data and is stored in the CSS. Absence of the VLR number in the CSS indicates that no subsequent update of the CSG subscription information is needed at the VLR upon CSG subscription change. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.4.6 MSC number | MSC number is defined in 3GPP TS 23.003 [5].
The MSC number is temporary subscriber data and is stored in the HLR and conditionally in the VLR. For absence of the MSC number in the HLR, the remarks on VLR number apply accordingly, see clause 2.4.5. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.4.7 HLR number | HLR number is defined in 3GPP TS 23.003 [5].
The HLR number may be stored in the VLR and Gn/Gp-SGSN. It is received as a mandatory parameter in the updating location accepted message. This data may be needed to retrieve subscribers to be restored after HLR reset.
The HLR number is temporary subscriber data and may optionally be stored in the VLR and Gn/Gp-SGSN. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.4.8 GSN number | |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.4.8.0 General | GSN number occurs as SGSN number and as GGSN number. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.4.8.1 SGSN number | SGSN number is the SS7 address of the SGSN . It is defined in 3GPP TS 23.003 [5].
The SGSN number is temporary subscriber data and is stored in the HLR for a GPRS subscription. It is conditionally stored in the VLR if the Gs interface is installed. Absence of the SGSN number in the HLR indicates that the mobile station is deregistered for GPRS or the subscriber has no GPRS subscription in the HLR. Absence of the SGSN number in the VLR indicates that there is no association between the VLR and the SGSN for this MS. The SGSN number is to be distinguished from the SGSN address described in clause 2.13.10.
The SGSN number is temporary subscriber data and is stored in the CSS. Absence of the SGSN number in the CSS indicates that no subsequent update of the CSG subscription information is needed at the SGSN upon CSG subscription change. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.4.8.2 GGSN number | GGSN number is the SS7 address of the GGSN .It is defined in 3GPP TS 23.003 [5]. Its usage is described in 3GPP TS 23.060 [21]. It is contained in the GGSN-list stored in the HLR and does not appear as separate subscriber data. Cf. clause 2.13.11. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.4.8.3 IWF number | IWF number is the SS7 address of the IWF. It has the same format as a "VLR number" or "SGSN number" which are defined in 3GPP TS 23.003 [5]. Its usage is described in 3GPP TS 29.305 [83]. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.4.9 MLC number | The MLC number occurs as an SMLC number and as a GMLC number. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.4.9.1 SMLC number (GSM only) | The SMLC number is the E.164 address of an NSS based SMLC.
The SMLC number is permanent data that may be stored in an MSC in association with either a set of IMSIs belonging to LMUs controlled by the SMLC or a set of cell identifiers belonging to the geographic area served by the SMLC. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.4.9.2 GMLC number | The GMLC number is the E.164 address of the GMLC. One or more GMLC numbers may be stored in the MS subscriber data in the HLR and downloaded to the VLR and SGSN. These GMLC numbers identify the GMLCs for the particular MS from which a location request for this MS may be confined for particular LCS clients. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.4.10 Subscription restriction | Subscription restriction is a parameter indicating whether or not certain restrictions apply to the subscription. The parameter takes either of the following values (see also GSM 02.13 [36]):
- accessible area for service;
- all GSM PLMNs;
- one national and all foreign GSM PLMNs;
- regionally restricted (part of a GSM PLMN in one country);
- regionally restricted plus all other GSM PLMNs.
The HLR/HSS associates location updating information with subscription restriction. It deregisters the MS if the PLMN is not allowed and sets:
- the MSC area restricted flag if the MSC area is not allowed, see clause 2.4.12;
- SGSN area restricted flag if the SGSN area is not allowed, see clause 2.4.14.
Handling of Regionally Restricted Subscription is defined in clause 2.4.11. By operator agreement, regional restriction in parts of different GSM PLMNs is also possible.
The subscription restriction is permanent subscriber data and is stored in the HLR. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.4.11 Regional Subscription Information | If a mobile subscriber has a regional subscription, the HLR/HSS shall store a list of up to ten Regional Subscription Zone Identities (RSZIs) per Network Destination Code (NDC) of the PLMN involved. The structure of RSZI is defined in 3GPP TS 23.003 [5]; since it is composed of the PLMN identification (CC NDC) and the Zone Code it is sufficient to store the Zone Code List per CC NDC.
On updating the MME, VLR or the SGSN, the HLR/HSS identifies the VPLMN and NDC given by the VLR or SGSN number or VPLMN-Id and transfers the pertaining Zone Code List to the VLR or SGSN or MME. The VLR or SGSN or MME derives from the Zone Code List the allowed and not allowed MSC or SGSN or MME areas and location areas; it sets the "LA not allowed flag" should the target LAI of the mobile station be excluded, and it informs the HLR/HSS should the MSC or SGSN or MME area be excluded. Signalling of cause value "location area not allowed" towards the mobile station is defined in TSs 3GPP TS 29.002 [27] and 3GPP TS 24.008 [26]. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.4.11.1 RSZI lists | The RSZI lists are permanent subscriber data stored conditionally in the HLR/HSS. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.4.11.2 Zone Code List | The VLR and the SGSN and the MME shall store as permanent and conditional subscriber data at least those Zone Codes by which they are affected. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.4.12 MSC area restricted flag | MSC area restricted flag is a parameter which can take either of the following values:
- MSC area restricted;
- MSC area not restricted.
The parameter is set in the HLR during updating of the VLR. Handling of unsupported services and information received from the VLR based on national roaming or regionally restricted subscription (clause 2.4.11) determine its value. The parameter contributes to the "MS Not Reachable" state for handling of terminating traffic in the HLR. The default value is "MSC area not restricted".
The MSC area restricted flag is temporary subscriber data and is contained in the HLR. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.4.13 LA not allowed flag | The LA not allowed flag is set in the VLR depending on National Roaming, Regionally Restricted Subscription and Roaming Restriction Due To Unsupported Feature, see 3GPP TS 29.002. It is applied to restrict service on a location area basis.
The LA not allowed flag is temporary subscriber data stored in the VLR. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.4.14 SGSN area restricted flag | SGSN area restricted flag is a parameter which can take either of the following values:
- SGSN area restricted;
- SGSN area not restricted.
The parameter is set in the HLR during updating of the SGSN. Handling of unsupported services and information received from the SGSN based on national roaming or regionally restricted subscription (clause 2.4.11) determine its value. The parameter contributes to the "MS Not Reachable" state for handling of terminating traffic in the HLR. The default value is "SGSN area not restricted".
The SGSN area restricted flag is temporary subscriber data and is contained in the HLR.
2.4.14a RA not allowed flag
The RA not allowed flag is set in the SGSN depending on National Roaming, Regionally Restricted Subscription and Roaming Restricted in the SGSN Due To Unsupported Feature, see 3GPP TS 29.002. It is applied to restrict service on a routing area basis.
The RA not allowed flag is temporary subscriber data stored in the SGSN.
2.4.14b TA not allowed flag
The TA not allowed flag is set in the MME depending on National Roaming, Regionally Restricted Subscription and Roaming Restricted in the MME Due To Unsupported Feature, see 3GPP TS 29.272[81]. It is applied to restrict service on a tracking area basis.
The TA not allowed flag is temporary subscriber data stored in the MME. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.4.15 Service restriction data induced by roaming | If in the course of roaming or at updating of the VLR or SGSN or MMEthe HLR/HSS is informed that the VLR or SGSN or MME does not support certain sensitive services or features, or, the HLR/HSS is informed in data request that the VLR or the SGSN or the MME supports only specific services, features or phases which do not correspond to subscribed services, features or phases, the HLR/HSS takes appropriate measures to restrict service for the mobile station in that VLR or SGSN or MME by setting and sending network induced replacing services such as available services, features or phases, barring programs or the roaming restriction for the MSC or SGSN or MME area.
These network-induced data have to be kept separate in the HLR, and where possible as discussed below in the VLR, from the permanent subscriber data of the call barring supplementary services, from the barring related data that can be modified by the subscriber or from the permanent regional subscription data.
These network-induced data have to be kept separate in the HLR/HSS, and where possible as discussed below in the SGSN and MME, from the permanent regional subscription data.
The network induced data take precedence over the subscriber data of the user where they are in conflict. If, in the course of roaming, restrictions caused by a service are lifted, the original subscriber data have to be re-installed both in HLR, in SGSN, in MME and in VLR when applicable, regarding any remaining restrictions due to other service replacements.
All network-induced restriction data are temporary subscriber data.
For ODB, 3GPP TS 23.015 [9] recommends mainly barring programs to replace this feature. The replacing barring data are conditionally stored in the HLR and VLR. In the VLR they cannot be distinguished from the permanent supplementary services data with the available signalling means, and no additional storage is needed. Interrogation shall reflect in both HLR and VLR the valid setting of the replacing temporary data; to prevent interference with Subscriber Controlled Input and to inform the customer on the restriction, the "control of barring services" subscription option is also temporarily set to the value "by the service provider".
CUG is also replaced by Outgoing Call Barring as described in 3GPP TS 23.085 [18].
Roaming restriction in the MSC area due to unsupported features is used to replace AoCC, see 3GPP TS 23.086, and Zone Codes for regional subscription, see clause 2.4.11 and 3GPP TS 29.002. A flag in the HLR and the VLR, see clause 2.4.15.2, collects the sources of network-induced roaming restriction which are also kept separate by the HLR.
Roaming restriction in the SGSN area due to unsupported features is used to replace Zone Codes for regional subscription, see clause 2.4.11 and 3GPP TS 29.002. A flag in the HLR and the SGSN, see clause 2.4.15.3, collects the sources of network-induced roaming restriction which are also kept separate by the HLR.
Roaming restriction in the MME area due to unsupported features is used to replace Zone Codes for regional subscription, see clause 2.4.11 and 3GPP TS 29.272[81]. A flag in the HSS and the MME, see clause 2.4.15.3a, collects the sources of network-induced roaming restriction which are also kept separate by the HSS. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.4.15.1 ODB-induced barring data | ODB-induced barring data are temporary data stored conditionally in the HLR; they include the necessary replacing barring programs for outgoing and incoming calls depending on the ODB profile. The subscription option "control of barring services" is set to "by the service provider". The corresponding barring supplementary services for outgoing calls are set by the HLR and sent to the VLR. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.4.15.2 Roaming restriction due to unsupported feature | Roaming restriction due to unsupported feature is a parameter which indicates that one or several services or features are not supported by the MSC, resulting in roaming restriction in the MSC area. It can take either of the following values:
- roaming restricted;
- roaming not restricted.
The parameter governs the "LA not allowed flag" in the VLR (see clause 2.4.13) and the "MSC area restricted flag" in the HLR (see clause 2.4.12); see also 3GPP TS 29.002.
The flag "roaming restriction due to unsupported feature" is temporary subscriber data stored in the VLR and in the HLR. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.4.15.3 Roaming restricted in the SGSN due to unsupported feature | Roaming restricted in the SGSN due to unsupported feature is a parameter which indicates that one or several services or features are not supported by the SGSN, resulting in roaming restriction in the SGSN area. It can take either of the following values:
- roaming restricted;
- roaming not restricted.
The parameter governs the "RA not allowed flag" in the SGSN (see clause 2.4.14a) and the "SGSN area restricted flag" in the HLR (see clause 2.4.14); see also 3GPP TS 29.002.
The flag "roaming restricted in the SGSN due to unsupported feature" is temporary subscriber data stored in the SGSN and in the HLR.
2.4.15.3a Roaming restricted in the MME due to unsupported feature
Roaming restricted in the MME due to unsupported feature is a parameter which indicates that one or several services or features are not supported by the MME, resulting in roaming restriction in the MME area. It can take either of the following values:
- roaming restricted;
- roaming not restricted.
The parameter governs the "TA not allowed flag" in the MME (see clause 2.4.14b).
The flag "roaming restricted in the MME due to unsupported feature" is temporary subscriber data stored in the MME and in the HSS. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.4.16 Cell Global ID or Service Area ID | The Cell Global ID or Service Area ID indicates the cell global identity of the cell in GSM (see 3GPP TS 23.003 [5]) or the service area identification of the service area in UMTS (see 3GPP TS 23.003 [5]) in which the MS is currently in radio contact or in which the MS was last in radio contact. The VLR and SGSN shall update the stored Cell Global ID or Service Area ID at establishment of every radio connection.
The cell ID is temporary subscriber data stored in the VLR and SGSN. It is conditional data, the VLR and SGSN shall store it whenever the subscriber data is marked as confirmed by radio contact.
The Cell Global ID or Service Area ID is temporary subscriber data stored in SGSN and GGSN/PDN-GW.
2.4.16A E-UTRAN Cell Global ID
The E-UTRAN Cell Global ID indicates the cell global identity of the cell in EPS (see 3GPP TS 23.003 [5]) in which the MS is currently in radio contact or in which the MS was last in radio contact.
The E-UTRAN Cell Global ID is temporary subscriber data stored in MME, PDN-GW and, when received via the SGs interface, in the VLR.
2.4.16B NR Cell Global Identity (NCGI)
The NR Cell Global Identity indicates the cell global identity of the cell in 5GS (see 3GPP TS 23.003 [5]) in which the UE is currently in radio contact or in which the UE was last in radio contact.
The NR Cell Global Identity is temporary subscriber data stored in AMF, SMF. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.4.17 Localised Service Area Information | If a mobile subscriber has a localised service area subscription, the HLR shall store a list of up to 20 Localised Service Area Identities (LSA IDs) per PLMN. The structure of LSA ID is defined in 3GPP TS 23.003 [5].
On updating the VLR or the Gn/Gp-SGSN, the HLR identifies the VPLMN given by the VLR or SGSN number and transfers the applicable LSA ID List to the VLR or Gn/Gp-SGSN. The VLR or Gn/Gp-SGSN derives from the LSA ID List the allowed LSA(s), priority of each LSA, the preferential access indicator, the active mode support indicator and active mode indication and the "LSA only access" indicator. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.4.17.1 LSA Identity | LSA Identity (LSA ID) is defined in 3GPP TS 23.003 [5]. The element uniquely identifies a LSA. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.4.17.2 LSA Priority | Localised Service Area Priority (LSA Priority) is defined in GSM 08.08. The LSA Priority is permanent subscriber data stored conditionally in the HLR.
2.4.17.2A LSA Preferential Access Indicator
The Localised Service Area Preferential Access Indicator defines if the subscriber shall be favoured in cells belonging to the LSA at resource allocation compared to other subscribers. The LSA Preferential Access Indicator is permanent subscriber data stored conditionally in the HLR.
2.4.17.2B LSA Active Mode Support Indicator
The Localised Service Area Active Mode Support Indicator defines if cells belonging to the LSA shall be favoured for the subscriber compared to other cells at resource allocation. The LSA Active Mode Indicator is permanent subscriber data stored conditionally in the HLR. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.4.17.3 LSA Only Access Indicator | The LSA Only Access Indicator defines if the subscriber is only allowed within its subscribed LSAs. The LSA Only Access Indicator is permanent subscriber data stored conditionally in the HLR. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.4.17.4 LSA Active Mode Indicator | The Localised Service Area Active Mode Indicator defines if the LSA Identity of the cell in which the MS is currently in radio contact with shall be indicated to the subscriber in active mode. The LSA Active Mode Indicator is permanent subscriber data stored conditionally in the HLR. |
539f847bb6cd6c0ba766caacc29710d4 | 23.008 | 2.4.17.5 VPLMN Identifier | The VPLMN Identifier identifies the VPLMN in which an LSA Identity is applicable. This identifier is not applicable to Universal LSA IDs as defined in 3GPP TS 23.003 [5]. The VPLMN identifier is permanent subscriber data stored conditionally in the HLR. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.