hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
1.47k
| content
stringlengths 0
6.67M
|
|---|---|---|---|
495b59b986f98d41912141cabbec196e
|
23.401
|
5.5.2.1 E-UTRAN to UTRAN Iu mode Inter RAT handover
| |
495b59b986f98d41912141cabbec196e
|
23.401
|
5.5.2.1.1 General
|
Pre-conditions:
- The UE is in ECM-CONNECTED state (E-UTRAN mode).
If emergency bearer services are ongoing for an UE, handover to the target RNC is performed independent of the Handover Restriction List. The SGSN checks, as part of the Routing Area Update in the execution phase, if the handover is to a restricted area and if so SGSN deactivate the non-emergency PDP context as specified in TS 23.060 [7], clause 9.2.4.2.
If emergency bearer services are ongoing for the UE, the source MME evaluates the handover to the target CSG cell independent of the UE's CSG subscription. If the handover is to a CSG cell that the UE is not subscribed, the target RNC will only accept the emergency bearers and the target SGSN deactivates the non-emergency PDP contexts that were not accepted by the target RNC as specified in TS 23.060 [7], clause 9.2.4.2.
|
495b59b986f98d41912141cabbec196e
|
23.401
|
5.5.2.1.2 Preparation phase
|
Figure 5.5.2.1.2-1: E-UTRAN to UTRAN Iu mode Inter RAT HO, preparation phase
1. The source eNodeB decides to initiate an Inter-RAT handover to the target access network, UTRAN Iu mode. At this point both uplink and downlink user data is transmitted via the following: Bearer(s) between UE and source eNodeB, GTP tunnel(s) between source eNodeB, Serving GW and PDN GW.
If the UE has an ongoing emergency bearer service the source eNodeB shall not initiate PS handover to a UTRAN cell that is not IMS voice capable.
NOTE 1: The process leading to the handover decision is outside of the scope of this specification.
2. The source eNodeB sends a Handover Required (S1AP Cause, Target RNC Identifier, CSG ID, CSG access mode, Source to Target Transparent Container) message to the source MME to request the CN to establish resources in the target RNC, target SGSN and the Serving GW. The bearers that will be subject to data forwarding (if any) are identified by the target SGSN in a later step (see step 7 below). When the target cell is a CSG cell or a hybrid cell, the source eNodeB shall include the CSG ID of the target cell. If the target cell is a hybrid cell, the CSG access mode shall be indicated.
3. The source MME determines from the 'Target RNC Identifier' IE that the type of handover is IRAT Handover to UTRAN Iu mode. The source MME selects the target SGSN as described in clause 4.3.8.4 on "SGSN Selection Function". The Source MME initiates the Handover resource allocation procedure by sending a Forward Relocation Request (IMSI, Target Identification, CSG ID, CSG Membership Indication, MM Context, PDN Connections, MME Tunnel Endpoint Identifier for Control Plane, MME Address for Control plane, Source to Target Transparent Container, RAN Cause, MS Info Change Reporting Action (if available), CSG Information Reporting Action (if available), UE Time Zone, ISR Supported, Serving Network) message to the target SGSN. The information ISR Supported is indicated if the source MME and associated Serving GW are capable to activate ISR for the UE. When ISR is activated the message should be sent to the SGSN that maintains ISR for the UE when this SGSN is serving the target identified by the Target Identification. This message includes all PDN Connections active in the source system and for each PDN Connection includes the associated APN, the address and the uplink Tunnel endpoint parameters of the Serving GW for control plane, and a list of EPS Bearer Contexts. RAN Cause indicates the S1AP Cause as received from source eNodeB. The old Serving Network is sent to target MME to support the target MME to resolve if Serving Network is changed.
The source MME shall perform access control by checking the UE's CSG subscription when CSG ID is provided by the source eNodeB. If there is no subscription data for this CSG ID or the CSG subscription is expired, and the target cell is a CSG cell, the source MME shall reject the handover with an appropriate cause unless the UE has emergency bearer services.
The source MME includes the CSG ID in the Forward Relocation Request when the target cell is a CSG cell or hybrid cell. When the target cell is a hybrid cell, or if there are one or several emergency bearers and the target cell is a CSG cell, the CSG Membership Indication indicating whether the UE is a CSG member shall be included in the Forward Relocation Request message.
The MM context includes information on the EPS Bearer context(s). The source MME does not include any EPS Bearer Context information for "Non-IP" bearers or for any SCEF connection. If none of the UE's EPS Bearers can be supported by the selected target SGSN, the source MME rejects the handover attempt by sending a Handover Preparation Failure (Cause) message to the Source eNodeB.
NOTE 2: If the handover is successful, the source MME will signal to the SGW and/or SCEF to release any non-included EPS Bearers after step 6 of the Execution procedure. The non-included bearers are locally released by the UE following the Bearer Context Status synchronisation that occurs during the Routing Area Update at step 10 of the Execution procedure.
The target SGSN maps the EPS bearers to PDP contexts 1-to-1 and maps the EPS Bearer QoS parameter values of an EPS bearer to the Release 99 QoS parameter values of a bearer context as defined in Annex E
Prioritization of PDP Contexts is performed by the target core network node, i.e. target SGSN.
The MM context contains security related information, e.g. supported ciphering algorithms as described in TS 29.274 [43]. Handling of security keys is described in TS 33.401 [41].
The target SGSN shall determine the Maximum APN restriction based on the APN Restriction of each bearer context in the Forward Relocation Request, and shall subsequently store the new Maximum APN restriction value.
If SIPTO at the Local Network is active for a PDN connection in the architecture with stand-alone GW the source MME shall include the Local Home Network ID of the source cell in the PDN Connections corresponding to the SIPTO at the Local Network PDN connection.
4. The target SGSN determines if the Serving GW is to be relocated, e.g., due to PLMN change. If the Serving GW is to be relocated, the target SGSN selects the target Serving GW as described under clause 4.3.8.2 on "Serving GW selection function", and sends a Create Session Request message (IMSI, SGSN Tunnel Endpoint Identifier for Control Plane, SGSN Address for Control plane, PDN GW address(es) for user plane, PDN GW UL TEID(s) for user plane, PDN GW address(es) for control plane, and PDN GW TEID(s) for control plane, the Protocol Type over S5/S8, Serving Network) per PDN connection to the target Serving GW. The Protocol Type over S5/S8 is provided to Serving GW which protocol should be used over S5/S8 interface.
The target SGSN establishes the EPS Bearer context(s) in the indicated order. The SGSN deactivates, as provided in step 7 of the execution phase, the EPS Bearer contexts which cannot be established.
4a. The target Serving GW allocates its local resources and returns a Create Session Response (Serving GW address(es) for user plane, Serving GW UL TEID(s) for user plane, Serving GW Address for control plane, Serving GW TEID for control plane) message to the target SGSN.
5. The target SGSN requests the target RNC to establish the radio network resources (RABs) by sending the message Relocation Request (UE Identifier, Cause, CN Domain Indicator, Integrity protection information (i.e. IK and allowed Integrity Protection algorithms), Encryption information (i.e. CK and allowed Ciphering algorithms), RAB to be setup list, CSG ID, CSG Membership Indication, Source RNC to Target RNC Transparent Container, Service Handover related information). If the Access Restriction is present in the MM context, the Service Handover related information shall be included by the target SGSN for the Relocation Request message in order for RNC to restrict the UE in connected mode to handover to the RAT prohibited by the Access Restriction.
For each RAB requested to be established, RABs To Be Setup shall contain information such as RAB ID, RAB parameters, Transport Layer Address, and Iu Transport Association. The RAB ID information element contains the NSAPI value, and the RAB parameters information element gives the QoS profile. The Transport Layer Address is the Serving GW Address for user plane (if Direct Tunnel is used) or the SGSN Address for user plane (if Direct Tunnel is not used), and the Iu Transport Association corresponds to the uplink Tunnel Endpoint Identifier Data in Serving GW or SGSN respectively.
Ciphering and integrity protection keys are sent to the target RNC to allow data transfer to continue in the new RAT/mode target cell without requiring a new AKA (Authentication and Key Agreement) procedure. Information that is required to be sent to the UE (either in the Relocation Command message or after the handover completion message) from RRC in the target RNC shall be included in the RRC message sent from the target RNC to the UE via the transparent container. More details are described in TS 33.401 [41].
The Target SGSN shall include the CSG ID and CSG Membership Indication when provided by the source MME in the Forward Relocation Request message.
In the target RNC radio and Iu user plane resources are reserved for the accepted RABs. Cause indicates the RAN Cause as received from source MME. The Source RNC to Target RNC Transparent Container includes the value from the Source to Target Transparent Container received from the source eNodeB.
If the target cell is a CSG cell, the target RNC shall verify the CSG ID provided by the target SGSN, and reject the handover with an appropriate cause if it does not match the CSG ID for the target cell. If the target cell is in hybrid mode, the target RNC may use the CSG Membership Indication to perform differentiated treatment for CSG and non-CSG members. If the target cell is a CSG cell, and if the CSG Membership Indication is "non member", the target RNC only accepts the emergency bearers.
5a. The target RNC allocates the resources and returns the applicable parameters to the target SGSN in the message Relocation Request Acknowledge (Target RNC to Source RNC Transparent Container, RABs setup list, RABs failed to setup list).
Upon sending the Relocation Request Acknowledge message the target RNC shall be prepared to receive downlink GTP PDUs from the Serving GW, or Target SGSN if Direct Tunnel is not used, for the accepted RABs.
Each RABs setup list is defined by a Transport Layer Address, which is the target RNC Address for user data, and the Iu Transport Association, which corresponds to the downlink Tunnel Endpoint Identifier for user data.
Any EPS Bearer contexts for which a RAB was not established are maintained in the target SGSN and the UE. These EPS Bearer contexts shall be deactivated by the target SGSN via explicit SM procedures upon the completion of the routing area update (RAU) procedure.
6. If 'Indirect Forwarding' and relocation of Serving GW apply and Direct Tunnel is used the target SGSN sends a Create Indirect Data Forwarding Tunnel Request message (Target RNC Address and TEID(s) for DL data forwarding) to the Serving GW. If 'Indirect Forwarding' and relocation of Serving GW apply and Direct Tunnel is not used, then the target SGSN sends a Create Indirect Data Forwarding Tunnel Request message (SGSN Address and TEID(s) for DL data forwarding) to the Serving GW.
Indirect forwarding may be performed via a Serving GW which is different from the Serving GW used as the anchor point for the UE.
6a. The Serving GW returns a Create Indirect Data Forwarding Tunnel Response (Cause, Serving GW Address(es) and Serving GW DL TEID(s) for data forwarding) message to the target SGSN.
7. The target SGSN sends the message Forward Relocation Response (Cause, SGSN Tunnel Endpoint Identifier for Control Plane, SGSN Address for Control Plane, Target to Source Transparent Container, Cause, RAB Setup Information, Additional RAB Setup Information, Address(es) and TEID(s) for User Traffic Data Forwarding, Serving GW change indication) to the source MME. Serving GW change indication indicates a new Serving GW has been selected. The Target to Source Transparent Container contains the value from the Target RNC to Source RNC Transparent Container received from the target RNC.
The IE 'Address(es) and TEID(s) for User Traffic Data Forwarding' defines the destination tunnelling endpoint for data forwarding in target system, and it is set as follows:
- If 'Direct Forwarding' applies, or if 'Indirect Forwarding' and no relocation of Serving GW apply and Direct Tunnel is used, then the IE 'Address(es) and TEID(s) for User Traffic Data Forwarding' contains the addresses and GTP-U tunnel endpoint parameters to the Target RNC received in step 5a.
- If 'Indirect Forwarding' and relocation of Serving GW apply, then the IE 'Address(es) and TEID(s) for User Traffic Data Forwarding' contains the addresses and DL GTP-U tunnel endpoint parameters to the Serving GW received in step 6. This is independent from using Direct Tunnel or not.
- If 'Indirect Forwarding' applies and Direct Tunnel is not used and relocation of Serving GW does not apply, then the IE 'Address(es) and TEID(s) for User Traffic Data Forwarding' contains the DL GTP-U tunnel endpoint parameters to the Target SGSN.
8. If "Indirect Forwarding" applies, the Source MME sends the message Create Indirect Data Forwarding Tunnel Request (Address(es) and TEID(s) for Data Forwarding (received in step 7)), EPS Bearer ID(s)) to the Serving GW used for indirect forwarding.
Indirect forwarding may be performed via a Serving GW which is different from the Serving GW used as the anchor point for the UE.
8a. The Serving GW returns the forwarding parameters by sending the message Create Indirect Data Forwarding Tunnel Response (Cause, Serving GW Address(es) and TEID(s) for Data Forwarding). If the Serving GW doesn't support data forwarding, an appropriate cause value shall be returned and the Serving GW Address(es) and TEID(s) will not be included in the message.
|
495b59b986f98d41912141cabbec196e
|
23.401
|
5.5.2.1.3 Execution phase
|
Figure 5.5.2.1.3-1: E-UTRAN to UTRAN Iu mode Inter RAT HO, execution phase
NOTE: For a PMIP-based S5/S8, procedure steps (A) and (B) are defined in TS 23.402 [2]. Step (B) shows PCRF interaction in the case of PMIP-based S5/S8. Steps 8 and 8a concern GTP based S5/S8
The source eNodeB continues to receive downlink and uplink user plane PDUs.
1. The source MME completes the preparation phase towards source eNodeB by sending the message Handover Command (Target to Source Transparent Container, E-RABs to Release List, Bearers Subject to Data Forwarding List). The "Bearers Subject to Data forwarding list" IE may be included in the message and it shall be a list of 'Address(es) and TEID(s) for user traffic data forwarding' received from target side in the preparation phase (Step 7 of the preparation phase) when 'Direct Forwarding' applies, or the parameters received in Step 8a of the preparation phase when 'Indirect Forwarding' applies.
The source eNodeB initiates data forwarding for bearers specified in the "Bearers Subject to Data Forwarding List". The data forwarding may go directly to target RNC or alternatively go via the Serving GW if so decided by source MME and or/ target SGSN in the preparation phase.
2. The source eNodeB will give a command to the UE to handover to the target access network via the message HO from E-UTRAN Command. This message includes a transparent container including radio aspect parameters that the target RNC has set-up in the preparation phase. The details of this E-UTRAN specific signalling are described in TS 36.300 [5].
Upon the reception of the HO from E-UTRAN Command message containing the Handover Command message, the UE shall associate its bearer IDs to the respective RABs based on the relation with the NSAPI and shall suspend the uplink transmission of the user plane data.
3. If the PLMN has configured Secondary RAT usage data reporting and the source eNodeB has Secondary RAT usage data to report, the eNodeB sends the RAN Usage data report message (Secondary RAT usage data) to the MME. Since the handover is an inter-RAT handover, the MME continues with the Secondary RAT usage data reporting procedure as in clause 5.7A.3. The reporting procedure in clause 5.7A.3 is only performed if PGW secondary RAT usage reporting is active.
4. The UE moves to the target UTRAN Iu (3G) system and executes the handover according to the parameters provided in the message delivered in step 2. The procedure is the same as in step 6 and 8 in clause 5.2.2.2 in TS 43.129 [8] with the additional function of association of the received RABs and existing Bearer Id related to the particular NSAPI.
The UE may resume the user data transfer only for those NSAPIs for which there are radio resources allocated in the target RNC.
5. When the new source RNC-ID + S-RNTI are successfully exchanged with the UE, the target RNC shall send the Relocation Complete message to the target SGSN. The purpose of the Relocation Complete procedure is to indicate by the target RNC the completion of the relocation from the source E-UTRAN to the RNC. After the reception of the Relocation Complete message the target SGSN shall be prepared to receive data from the target RNC. Each uplink N-PDU received by the target SGSN is forwarded directly to the Serving GW.
For SIPTO at the Local Network with stand-alone GW architecture, the target RNC shall include the Local Home Network ID of the target cell in the Relocation Complete message.
6. Then the target SGSN knows that the UE has arrived to the target side and target SGSN informs the source MME by sending the Forward Relocation Complete Notification (ISR Activated, Serving GW change) message. If indicated, ISR Activated indicates to the source MME that it shall maintain the UE's context and that it shall activate ISR, which is only possible when the S‑GW is not changed. The source MME will also acknowledge that information. A timer in source MME is started to supervise when resources in Source eNodeB and Source Serving GW (for Serving GW relocation) shall be released.
When the timer expires and ISR Activated is not indicated by the target SGSN the source MME releases all bearer resources of the UE. If Serving GW change is indicated and this timer expires the source MME deletes the EPS bearer resources by sending Delete Session Request (Cause, Operation Indication) messages to the Source Serving GW. The operation Indication flag is not set, that indicates to the Source Serving GW that the Source Serving GW shall not initiate a delete procedure towards the PDN GW. If ISR has been activated before this procedure, the cause indicates to the Source S‑GW that the Source S‑GW shall delete the bearer resources on the other old CN node by sending Delete Bearer Request message(s) to that CN node.
Upon receipt of the Forward Relocation Complete Acknowledge message the target SGSN starts a timer if the target SGSN allocated S‑GW resources for indirect forwarding.
For all bearers that were not included in the Forward Relocation Request message sent in step 3, the MME now releases them by sending a Delete Bearer Command to the SGW, or, the appropriate message to the SCEF.
7. The target SGSN will now complete the Handover procedure by informing the Serving GW (for Serving GW relocation this will be the Target Serving GW) that the target SGSN is now responsible for all the EPS Bearer Contexts the UE has established. This is performed in the message Modify Bearer Request (SGSN Tunnel Endpoint Identifier for Control Plane, NSAPI(s), SGSN Address for Control Plane, SGSN Address(es) and TEID(s) for User Traffic for the accepted EPS bearers (if Direct Tunnel is not used) or RNC Address(es) and TEID(s) for User Traffic for the accepted EPS bearers (if Direct Tunnel is used) and RAT type, ISR Activated) per PDN connection. As it is a mobility from E-UTRAN, if the target SGSN supports location information change reporting, the target SGSN shall include the User Location Information (according to the supported granularity) in the Modify Bearer Request, regardless of whether location information change reporting had been requested in the previous RAT by the PDN GW. If the PDN GW requested User CSG information (determined from the UE context), the SGSN also includes the User CSG Information IE in this message. If the UE Time Zone has changed, the SGSN includes the UE Time Zone IE in this message. If Serving GW is not relocated but the Serving Network has changed or if the SGSN has not received any old Serving Network information from the old MME, the SGSN includes the new Serving Network IE in this message. In network sharing scenarios Serving Network denotes the serving core network. If indicated, the information ISR Activated indicates that ISR is activated, which is only possible when the S‑GW is not changed. When the Modify Bearer Request does not indicate ISR Activated and S‑GW is not changed, the S‑GW deletes any ISR resources by sending a Delete Bearer Request to the other CN node that has bearer resources on the S‑GW reserved.
The SGSN releases the non-accepted EPS Bearer contexts by triggering the Bearer Context deactivation procedure. If the Serving GW receives a DL packet for a non-accepted bearer, the Serving GW drops the DL packet and does not send a Downlink Data Notification to the SGSN.
8. The Serving GW (for Serving GW relocation this will be the Target Serving GW) may inform the PDN GW(s) the change of for example for Serving GW relocation or the RAT type that e.g. can be used for charging, by sending the message Modify Bearer Request per PDN connection. The S‑GW also includes User Location Information IE and/or UE Time Zone IE and/or User CSG Information IE if they are present in step 7. Serving Network should be included if it is received in step 7 or in step 4 in clause 5.5.2.1.2. For Serving GW relocation, the Serving GW allocates DL TEIDs on S5/S8 even for non-accepted bearers and may include the PDN Charging Pause Support Indication. The PDN GW must acknowledge the request with the message Modify Bearer Response. In the case of Serving GW relocation, the PDN GW updates its context field and returns a Modify Bearer Response (Charging Id, MSISDN, PDN Charging Pause Enabled Indication (if PDN GW has chosen to enable the function), etc.) message to the Serving GW. The MSISDN is included if the PDN GW has it stored in its UE context. If location information change reporting is required and supported in the target SGSN, the PDN GW shall provide MS Info Change Reporting Action in the Modify Bearer Response.
If PCC infrastructure is used, the PDN GW informs the PCRF about the change of, for example, the RAT type.
If the Serving GW is relocated, the PDN GW shall send one or more "end marker" packets on the old path immediately after switching the path. The source Serving GW shall forwards the "end marker" packets to the source eNodeB.
9. The Serving GW (for Serving GW relocation this will be the Target Serving GW) acknowledges the user plane switch to the target SGSN via the message Modify Bearer Response (Cause, Serving GW Tunnel Endpoint Identifier for Control Plane, Serving GW Address for Control Plane, Protocol Configuration Options, MS Info Change Reporting Action). At this stage the user plane path is established for all EPS Bearer contexts between the UE, target RNC, target SGSN if Direct Tunnel is not used, Serving GW (for Serving GW relocation this will be the Target Serving GW) and PDN GW.
If the Serving GW does not change, the Serving GW shall send one or more "end marker" packets on the old path immediately after switching the path.
10. When the UE recognises that its current Routing Area is not registered with the network, or when the UE's TIN indicates "GUTI", the UE initiates a Routing Area Update procedure with the target SGSN informing it that the UE is located in a new routing area. It is RAN functionality to provide the PMM-CONNECTED UE with Routing Area information.
The target SGSN knows that an IRAT Handover has been performed for this UE as it received the bearer context(s) by handover messages and therefore the target SGSN performs only a subset of the RAU procedure, specifically it excludes the context transfer procedures between source MME and target SGSN.
For a UE supporting CIoT EPS Optimisations, the UE uses the bearer status information in the RAU Accept to identify any non-transferred bearers that it shall locally release.
11. When the timer started at step 6 expires, the source MME sends a Release Resources message to the Source eNodeB. The Source eNodeB releases its resources related to the UE.
When the timer started in step 6 expires and if the source MME received the Serving GW change indication in the Forward Relocation Response message, it deletes the EPS bearer resources by sending Delete Session Request (Cause, Operation Indication, Secondary RAT usage data) messages to the Source Serving GW. The operation indication flag is not set, that indicates to the Source Serving GW that the Source Serving GW shall not initiate a delete procedure towards the PDN GW. Secondary RAT usage data is included if it was received in step 3. The Source Serving GW acknowledges with Delete Session Response (Cause) messages. If ISR has been activated before this procedure, the cause indicates to the Source S‑GW that the Source S‑GW shall delete the bearer resources on the other old CN node by sending Delete Bearer Request message(s) to that CN node.
12. If indirect forwarding was used then the expiry of the timer at source MME started at step 6 triggers the source MME to send a Delete Indirect Data Forwarding Tunnel Request message to the S‑GW to release the temporary resources used for indirect forwarding.
13. If indirect forwarding was used and the Serving GW is relocated, then the expiry of the timer at target SGSN started at step 6 triggers the target SGSN to send a Delete Indirect Data Forwarding Tunnel Request message to the target S‑GW to release temporary resources used for indirect forwarding.
|
495b59b986f98d41912141cabbec196e
|
23.401
|
5.5.2.1.4 E-UTRAN to UTRAN Iu mode Inter RAT handover Reject
|
The Target RNC may reject the use of the Handover procedure if none of the requested RABs in the Relocation Request message could be established. In this case no UE context is established in the target SGSN/RNC and no resources are allocated. The UE remains in the Source eNodeB/MME.
Figure 5.5.2.1.4-1: E-UTRAN to UTRAN Iu mode Inter RAT HO reject
1. The Step 1 to 5 in the flow are identical to the ones in clause 5.5.2.1.2.
6. If the Target RNC fails to allocate any resources for any of the requested RABs it sends a Relocation Failure (Cause) message to the Target SGSN. When the Target SGSN receives the Relocation Failure message from Target RNC the Target SGSN clears any reserved resources for this UE.
7. This step is only performed for Serving GW relocation, i.e. if Steps 4/4a have been performed. The Target SGSN deletes the EPS bearer resources by sending Delete Session Request (Cause) messages to the Target Serving GW. The Target Serving GW acknowledges with Delete Session Response (Cause) messages.
8. The Target SGSN sends the Forward Relocation Response (Cause) message to the Source MME.
9. When the Source MME receives the Forward Relocation Response message it send a Handover Preparation Failure (Cause) message to the Source eNodeB.
|
495b59b986f98d41912141cabbec196e
|
23.401
|
5.5.2.2 UTRAN Iu mode to E-UTRAN Inter RAT handover
| |
495b59b986f98d41912141cabbec196e
|
23.401
|
5.5.2.2.1 General
|
The UTRAN Iu mode to E-UTRAN Inter RAT handover procedure takes place when the network decides to perform a handover. The decision to perform PS handover from UTRAN Iu mode to E-UTRAN is taken by the network based on radio condition measurements reported by the UE to the UTRAN RNC.
If emergency bearer services are ongoing for the UE, the MME checks as part of the Tracking Area Update in the execution phase, if the handover is to a restricted area and if so MME releases the non-emergency bearers as specified in clause 5.10.3.
If emergency bearer services are ongoing for the UE, the source SGSN evaluates the handover to the target CSG cell independent of the UE's CSG subscription. If the handover is to a CSG cell that the UE is not subscribed, the target eNodeB only accepts the emergency bearers and the target MME releases the non-emergency PDN connections that were not accepted by the target eNodeB as specified in clause 5.10.3.
|
495b59b986f98d41912141cabbec196e
|
23.401
|
5.5.2.2.2 Preparation phase
|
Figure 5.5.2.2.2-1: UTRAN Iu mode to E-UTRAN Inter RAT HO, preparation phase
1. The source RNC decides to initiate an Inter-RAT handover to the E-UTRAN. At this point both uplink and downlink user data is transmitted via the following: Bearers between UE and source RNC, GTP tunnel(s) between source RNC, source SGSN (only if Direct Tunnel is not used), Serving GW and PDN GW.
NOTE 1: The process leading to the handover decision is outside of the scope of this specification.
2. The source RNC sends a Relocation Required (Cause, Target eNodeB Identifier, CSG ID, CSG access mode, Source RNC Identifier, Source RNC to Target RNC Transparent Container) message to the source SGSN to request the CN to establish resources in the target eNodeB, Target MME and the Serving GW. The bearers that will be subject to data forwarding (if any) are identified by the target MME in a later step (see step 7 below). When the target cell is a CSG cell or a hybrid cell, the source RNC shall include the CSG ID of the target cell. If the target cell is a hybrid cell, the CSG access mode shall be indicated.
3. The source SGSN determines from the 'Target eNodeB Identifier' IE that the type of handover is IRAT Handover to E-UTRAN. The source SGSN selects the target MME as described in clause 4.3.8.3 on "MME Selection Function". The Source SGSN initiates the Handover resource allocation procedure by sending Forward Relocation Request (IMSI, Target Identification, CSG ID, CSG Membership Indication, MM Context, PDN Connections, SGSN Tunnel Endpoint Identifier for Control Plane, SGSN Address for Control plane, Source to Target Transparent Container, RAN Cause, MS Info Change Reporting Action (if available), CSG Information Reporting Action (if available), UE Time Zone, ISR Supported, Serving Network, Change to Report (if present)) message to the target MME. This message includes all EPS Bearer contexts corresponding to all the bearers established in the source system and the uplink Tunnel endpoint parameters of the Serving GW. If the information ISR Supported is indicated, this indicates that the source SGSN and associated Serving GW are capable to activate ISR for the UE. When ISR is activated the message should be sent to the MME that maintains ISR for the UE when this MME is serving the target identified by the Target Identification. RAN Cause indicates the Cause as received from source RNC. The Source to Target Transparent Container contains the value from the Source RNC to Target RNC Transparent Container received from the Source RNC. The old Serving Network is sent to target MME to support the target MME to resolve if Serving Network is changed.
Change to Report flag is included by the source SGSN if reporting of change of UE Time Zone, or Serving Network, or both towards Serving GW / PDN GW was deferred by the source SGSN.
The source SGSN shall perform access control by checking the UE's CSG subscription when CSG ID is provided by the source RNC. If there is no subscription data for this CSG ID or the CSG subscription is expired, and the target cell is a CSG cell, the source SGSN shall reject the handover with an appropriate cause unless the UE has emergency bearer services.
The source SGSN includes the CSG ID in the Forward Relocation Request when the target cell is a CSG cell or hybrid cell. When the target cell is a hybrid cell, or if there are one or several emergency bearers and the target cell is a CSG cell, the CSG Membership Indication indicating whether the UE is a CSG member shall be included in the Forward Relocation Request message.
This message includes all PDN Connections active in the source system and for each PDN Connection includes the associated APN, the address and the uplink tunnel endpoint parameters of the Serving GW for control plane, and a list of EPS Bearer Contexts.
Prioritization of EPS Bearer Contexts is performed by the target core network node.
The MM context contains security related information, e.g. UE Network capabilities and used UMTS integrity and ciphering algorithm(s) as well as keys, as described in clause 5.7.2 (Information Storage for MME).
The target MME selects the NAS ciphering and integrity algorithms to use. These algorithms will be sent transparently from the target eNodeB to the UE in the Target to Source Transparent Container (EPC part).
The MME establishes the EPS bearer(s) in the prioritized order. The MME deactivates, as provided in step 8 of the execution phase, the EPS bearers which cannot be established.
The target MME shall determine the Maximum APN restriction based on the APN Restriction of each bearer context received in the Forward Relocation Request, and shall subsequently store the new Maximum APN restriction value.
If SIPTO at the Local Network is active for a PDN connection in the architecture with stand-alone GW the source SGSN shall include the Local Home Network ID of the source cell in the PDN Connections corresponding to the SIPTO at the Local Network PDN connection.
4. The target MME determines if the Serving GW is to be relocated, e.g., due to PLMN change. If the Serving GW is to be relocated, the target MME selects the target Serving GW as described under clause 4.3.8.2 on "Serving GW selection function". The target MME sends a Create Session Request message (IMSI, MME Address and TEID, MME Tunnel Endpoint Identifier for Control Plane, MME Address for Control plane, PDN GW address(es) for user plane, PDN GW UL TEID(s) for user plane, PDN GW address for control plane, and PDN GW TEID(s) for control plane, the Protocol Type over S5/S8, Serving Network) per PDN connection to the target Serving GW. The Protocol Type over S5/S8 is provided to Serving GW which protocol should be used over S5/S8 interface.
4a. The target Serving GW allocates its local resources and returns them in a Create Session Response (Serving GW address(es) for user plane, Serving GW UL TEID(s) for user plane, Serving GW Address for control plane, Serving GW TEID for control plane) message to the target MME.
5. The target MME requests the target eNodeB to establish the bearer(s) by sending the message Handover Request (UE Identifier, S1AP Cause, KeNB, allowed AS Integrity Protection and Ciphering algorithm(s), NAS Security Parameters to E-UTRAN, EPS Bearers to be setup list, CSG ID, CSG Membership Indication, Source to Target Transparent Container). The NAS Security Parameters to E‑UTRAN includes the NAS Integrity Protection and Ciphering algorithm(s), eKSI and NONCEMME are targeted for the UE. S1AP Cause indicates the RAN Cause as received from source SGSN. The Source to Target Transparent Container contains the value from the RAN Transparent Container received from the source SGSN.
NOTE 2: The target MME derives K'ASME from CK and IK in the MM context and associates it with eKSI, as described in TS 33.401 [41] and selects NAS Integrity Protection and Ciphering algorithm(s). The MME and UE derive the NAS keys and KeNB from K'ASME. If the MME shares an EPS security association with the UE, the MME may activate this native EPS security context by initiating a NAS SMC procedure after having completed the handover procedure.
For each EPS bearer requested to be established, 'EPS Bearers To Be Setup' IE shall contain information such as ID, bearer parameters, Transport Layer Address, "Data forwarding not possible" indication, and S1 Transport Association. The target MME ignores any Activity Status Indicator within an EPS Bearer Context and requests the target eNodeB to allocate resources for all EPS Bearer Contexts received from the source side. The Transport Layer Address is the Serving GW Address for user data, and the S1 Transport Association corresponds to the uplink Tunnel Endpoint Identifier Data. "Data forwarding not possible" indication shall be included if the target MME decides the corresponding bearer will not be subject to data forwarding.
The target MME shall include the CSG ID and CSG Membership Indication when provided by the source SGSN in the Handover Request message.
The information about the selected NAS ciphering and integrity protection algorithm(s), KSI and NONCEMME will be sent transparently from the target eNodeB to the UE in the Target to Source Transparent Container, and in the message UTRAN HO Command from source RNC to the UE. This will then allow data transfer to continue in the new RAT/mode target cell without requiring a new AKA (Authentication and Key Agreement) procedure. More details are described in TS 33.401 [41].
If the target cell is a CSG cell, the target eNodeB shall verify the CSG ID provided by the target MME, and reject the handover with an appropriate cause if it does not match the CSG ID for the target cell. If the target eNodeB is in hybrid mode, it may use the CSG Membership Status to perform differentiated treatment for CSG and non-CSG members. If the target cell is a CSG cell, and if the CSG Membership Indication is "non member", the target eNodeB only accepts the emergency bearers.
5a. The target eNodeB allocates the requested resources and returns the applicable parameters to the target MME in the message Handover Request Acknowledge (Target to Source Transparent Container, EPS Bearers setup list, EPS Bearers failed to setup list). The target eNodeB shall ignore it if the number of radio bearers in the Source to Target Transparent container does not comply with the number of bearers requested by the MME and allocate bearers as requested by the MME. Upon sending the Handover Request Acknowledge message the target eNodeB shall be prepared to receive downlink GTP PDUs from the Serving GW for the accepted EPS bearers.
The target eNodeB selects AS integrity and ciphering algorithm(s). In addition to the information provided by the MME (eKSI, NAS Integrity Protection and Ciphering algorithm(s) and NONCEMME), the target eNodeB inserts AS integrity and ciphering algorithm(s) into the UTRAN RRC message, which is contained in the Target to Source Transparent Container.
6. If 'Indirect Forwarding' and relocation of Serving GW apply the target MME sends a Create Indirect Data Forwarding Tunnel Request message (Target eNodeB Address, TEID(s) for DL data forwarding) to the Serving GW.
Indirect forwarding may be performed via a Serving GW which is different from the Serving GW used as the anchor point for the UE.
6a. The Serving GW returns a Create Indirect Data Forwarding Tunnel Response (Cause, Serving GW Address(es) and Serving GW DL TEID(s) for data forwarding) message to the target MME.
7. The target MME sends the message Forward Relocation Response (Cause, List of Set Up RABs, EPS Bearers setup list, MME Tunnel Endpoint Identifier for Control Plane, RAN Cause, MME Address for control plane, Target to Source Transparent Container, Address(es) and TEID(s) for Data Forwarding, Serving GW change indication) to the source SGSN. Serving GW change indication indicates whether a new Serving GW has been selected. The Target to Source Transparent Container includes the value from the Target to Source Transparent Container received from the target eNodeB.
The IE 'Address(es) and TEID(s) for User Traffic Data Forwarding' defines the destination tunnelling endpoint for data forwarding in target system, and it is set as follows. If 'Direct Forwarding' or if 'Indirect Forwarding' but no relocation of Serving GW applies, then the IEs 'Address(es) and TEID(s) for Data Forwarding' contains the forwarding DL GTP-U tunnel endpoint parameters to the eNodeB received in step 5a.
If 'Indirect Forwarding' and relocation of Serving GW apply the IEs 'Address(es) and TEID(s) for Data Forwarding' contains the DL GTP-U tunnel endpoint parameters to the Target eNodeB or to the forwarding Serving GW received in step 6a.
8. If "Indirect Forwarding" applies, the source SGSN shall send the message Create Indirect Data Forwarding Tunnel Request (Address(es) and TEID(s) for Data Forwarding (received in step 7)) to the Serving GW used for indirect forwarding.
Indirect forwarding may be performed via a Serving GW which is different from the Serving GW used as the anchor point for the UE.
8a. The Serving GW returns the forwarding user plane parameters by sending the message Create Indirect Data Forwarding Tunnel Response (Cause, Serving GW Address(es) and TEID(s) for data forwarding). If the Serving GW doesn't support data forwarding, an appropriate cause value shall be returned and the Serving GW Address(es) and TEID(s) will not be included in the message.
|
495b59b986f98d41912141cabbec196e
|
23.401
|
5.5.2.2.3 Execution phase
|
Figure 5.5.2.2.3-1: UTRAN Iu mode to E-UTRAN Inter RAT HO, execution phase
NOTE: For a PMIP-based S5/S8, procedure steps (A) and (B) are defined in TS 23.402 [2]. Step (B) shows PCRF interaction in the case of PMIP-based S5/S8. Steps 9 and 9a concern GTP based S5/S8.
The source RNC continues to receive downlink and uplink user plane PDUs.
1. The source SGSN completes the preparation phase towards source RNC by sending the message Relocation Command (Target RNC to Source RNC Transparent Container, RABs to be Released List, RABs Subject to Data Forwarding List). The "RABs to be Released list" IE will be the list of all NSAPIs (RAB Ids) for which a Bearer was not established in Target eNodeB. The "RABs Subject to Data forwarding list" IE may be included in the message and it shall be a list of 'Address(es) and TEID(s) for user traffic data forwarding' received from target side in step 7 of the preparation phase when 'Direct Forwarding' applies. If 'Indirect Forwarding' is applicable and Direct Tunnel is used the "RABs Subject to Data Forwarding List" IE includes the parameters received in Step 8a of the preparation phase. If 'Indirect Forwarding' is applicable and Direct Tunnel is not used the "RABs Subject to Data Forwarding List" IE includes the source SGSN address(es) and TEID(s) allocated for indirect data forwarding by Source SGSN. The Target RNC to Source RNC Transparent Container contains the value from the Target to Source Transparent Container received from the target MME.
2. The source RNC will command to the UE to handover to the target eNodeB via the message HO from UTRAN Command. The access network specific message to UE includes a transparent container including radio aspect parameters that the target eNodeB has set-up in the preparation phase.
The source RNC may initiate data forwarding for the indicated RABs/EPS Bearer contexts specified in the "RABs Subject to Data Forwarding List". The data forwarding may go directly to target eNodeB, or alternatively go via the Serving GW if so decided by source SGSN and/or target MME in the preparation phase.
Upon the reception of the HO from UTRAN Command message containing the Relocation Command message, the UE shall associate its RAB IDs to the respective bearers ID based on the relation with the NSAPI and shall suspend the uplink transmission of the user plane data.
3. Void.
4. The UE moves to the E-UTRAN and performs access procedures toward target eNodeB.
5. When the UE has got access to target eNodeB it sends the message HO to E-UTRAN Complete.
The UE shall implicitly derive the EPS bearers for which an E-RAB was not established from the HO from UTRAN Command and deactivate them locally without an explicit NAS message at this step.
6. When the UE has successfully accessed the target eNodeB, the target eNodeB informs the target MME by sending the message Handover Notify (TAI+ECGI, Local Home Network ID).
For SIPTO at the Local Network with stand-alone GW architecture, the target eNodeB shall include the Local Home Network ID of the target cell in the Handover Notify message.
7. Then the target MME knows that the UE has arrived to the target side and target MME informs the source SGSN by sending the Forward Relocation Complete Notification (ISR Activated, Serving GW change) message. If ISR Activated is indicated, this indicates to the source SGSN that it shall maintain the UE's contexts and activate ISR, which is only possible when the S‑GW is not changed. The source SGSN shall also acknowledge that information. A timer in source SGSN is started to supervise when resources in the in Source RNC and Source Serving GW (for Serving GW relocation) shall be released
Upon receipt of the Forward Relocation Complete Acknowledge message the target MME starts a timer if the target MME applies indirect forwarding.
8. The target MME will now complete the Inter-RAT Handover procedure by informing the Serving GW (for Serving GW relocation this will be the Target Serving GW) that the target MME is now responsible for all the bearers the UE have established. This is performed in the message Modify Bearer Request (Cause, MME Tunnel Endpoint Identifier for Control Plane, EPS Bearer ID, MME Address for Control Plane, eNodeB Address(es) and TEID(s) for User Traffic for the accepted EPS bearers and RAT type, ISR Activated) per PDN connection. As it is a mobility from UTRAN, if the target MME supports location information change reporting, the target MME shall include the User Location Information (according to the supported granularity) in the Modify Bearer Request, regardless of whether location information change reporting had been requested in the previous RAT by the PDN GW. If the PDN GW requested User CSG information (determined from the UE context), the MME also includes the User CSG Information IE in this message. If either the UE Time Zone has changed or Forward Relocation Request message from source SGSN indicated pending UE Time Zone change reporting (via Change to Report flag), the MME includes the UE Time Zone IE in this message. If either Serving GW is not relocated but the Serving Network has changed or Forward Relocation Request message from source SGSN indicated pending Serving Network change reporting (via Change to Report flag), the MME includes the new Serving Network IE in this message. If indicated, the information ISR Activated indicates that ISR is activated, which is only possible when the S‑GW was not changed. When the Modify Bearer Request does not indicate ISR Activated and S‑GW is not changed, the S‑GW deletes any ISR resources by sending a Delete Bearer Request to the other CN node that has bearer resources on the S‑GW reserved.
The MME releases the non-accepted dedicated bearers by triggering the bearer release procedure as specified in clause 5.4.4.2. If the Serving GW receives a DL packet for a non-accepted bearer, the Serving GW drops the DL packet and does not send a Downlink Data Notification to the MME.
If the default bearer of a PDN connection has not been accepted by the target eNodeB and there are other PDN connections active, the MME shall handle it in the same way as if all bearers of a PDN connection have not been accepted. The MME releases these PDN connections by triggering the MME requested PDN disconnection procedure specified in clause 5.10.3.
9. The Serving GW (for Serving GW relocation this will be the Target Serving GW) may inform the PDN GW the change of for example for Serving GW relocation or the RAT type that e.g. can be used for charging, by sending the message Modify Bearer Request per PDN connection. The S‑GW also includes User Location Information IE and/or UE Time Zone IE and/or User CSG Information IE if they are present in step 8. Serving Network should be included if it is received in step 8 or in step 4 in clause 5.5.2.2.2. For Serving GW relocation, the Serving GW allocates DL TEIDs on S5/S8 even for non-accepted bearers and may include the PDN Charging Pause Support Indication. The PDN GW must acknowledge the request with the message Modify Bearer Response. In the case of Serving GW relocation, the PDN GW updates its context field and returns a Modify Bearer Response (Charging Id, MSISDN, PDN Charging Pause Enabled Indication (if PDN GW has chosen to enable the function), etc.) message to the Serving GW. The MSISDN is included if the PDN GW has it stored in its UE context. If location information change reporting is required and supported in the target MME, the PDN GW shall provide MS Info Change Reporting Action in the Modify Bearer Response.
If PCC infrastructure is used, the PDN GW informs the PCRF about the change of, for example, the RAT type.
If the Serving GW is relocated, the PDN GW shall send one or more "end marker" packets on the old path immediately after switching the path in order to assist the reordering function in the target eNodeB. The source Serving GW shall forward the "end marker" packets to the source SGSN or RNC.
10. The Serving GW (for Serving GW relocation this will be the Target Serving GW) acknowledges the user plane switch to the target MME via the message Modify Bearer Response (Cause, Serving GW Tunnel Endpoint Identifier for Control Plane, Serving GW Address for Control Plane, Protocol Configuration Options, MS Info Change Reporting Action). At this stage the user plane path is established for all bearers between the UE, target eNodeB, Serving GW (for Serving GW relocation this will be the Target Serving GW) and PDN GW.
If the Serving GW does not change, the Serving GW shall send one or more "end marker" packets on the old path immediately after switching the path in order to assist the reordering function in the target eNodeB.
11. The UE initiates a Tracking Area Update procedure when one of the conditions listed in clause "Triggers for tracking area update" applies.
The target MME knows that an IRAT Handover has been performed for this UE as it received the bearer context(s) by handover messages and therefore the target MME performs only a subset of the TA update procedure, specifically it excludes the context transfer procedures between source SGSN and target MME.
If the Subscription Data received from the HSS (during the TAU in step 11) contains information that is necessary for the E-UTRAN to be aware of (e.g. a restriction in the UE's permission to use NR as a secondary RAT, Unlicensed Spectrum in the form of LAA/LWA/LWIP/NR-U (as specified in clause 4.3.30) or a combination of them), or an existing UE context in the MME indicates that the UE is not permitted to use NR as a secondary RAT or Unlicensed Spectrum or a combination of them and the MME has not provided this information to the target eNodeB during step 5 of the handover preparation phase, then the MME sends an updated Handover Restriction List in the Downlink NAS Transport message that it sends to RAN. If the UE is not allowed to use NR as Secondary RAT, the MME indicates that to the UE in TAU Accept message.
12. When the timer started in step 7 expires the source SGSN will clean‑up all its resources towards source RNC by sending the Iu Release Command to the RNC. When there is no longer any need for the RNC to forward data, the source RNC responds with an Iu Release Complete message.
When the timer started in step 7 expires and if the source SGSN received the Serving GW change indication in the Forward Relocation Response message, it deletes the EPS bearer resources by sending Delete Session Request (Cause, Operation Indication) messages to the Source Serving GW. The operation Indication flag is not set, that indicates to the Source Serving GW that the Source Serving GW shall not initiate a delete procedure towards the PDN GW. The Source Serving GW acknowledges with Delete Session Response (Cause) messages. If ISR has been activated before this procedure, the cause indicates to the Source S‑GW that the Source S‑GW shall delete the bearer resources on the other old CN node by sending Delete Bearer Request message(s) to that CN node.
13. If indirect forwarding was used then the expiry of the timer at source SGSN started at step 7 triggers the source SGSN to send a Delete Indirect Data Forwarding Tunnel Request message to the S‑GW to release the temporary resources used for indirect forwarding.
14. If indirect forwarding was used and the Serving GW is relocated, then the expiry of the timer at target MME started at step 7 triggers the target MME to send a Delete Indirect Data Forwarding Tunnel Request message to the target S‑GW to release temporary resources used for indirect forwarding.
|
495b59b986f98d41912141cabbec196e
|
23.401
|
5.5.2.2.4 UTRAN Iu mode to E-UTRAN Inter RAT handover reject
|
The Target eNodeB may reject the use of the Handover procedure if none of the requested EPS bearers in the Handover Request message could be established. In this case no UE context is established in the target MME/eNodeB and no resources are allocated. The UE remains in the Source RNC/SGSN.
Figure 5.5.2.2.4-1: UTRAN Iu mode to E-UTRAN Inter RAT HO reject
1. Steps 1 to 5 in the flow are identical to the ones in clause 5.5.2.2.2.
6. If the Target eNodeB fails to allocate any resources for any of the requested EPS Bearers it sends a Handover Failure (Cause) message to the Target MME. When the Target MME receives the Handover Failure message from Target eNodeB the Target MME clears any reserved resources for this UE.
7. This step is only performed for Serving GW relocation, i.e. if Steps 4/4a have been performed. The Target MME deletes the EPS bearer resources by sending Delete Session Request (Cause) messages to the Target Serving GW. The Target Serving GW acknowledges with Delete Session Response (Cause) messages.
8. The Target MME sends the Forward Relocation Response (Cause) message to the Source SGSN.
9. When the Source SGSN receives the Forward Relocation Response message it send a Relocation Preparation Failure (Cause) message to the Source RNC.
|
495b59b986f98d41912141cabbec196e
|
23.401
|
5.5.2.3 E-UTRAN to GERAN A/Gb mode Inter RAT handover
| |
495b59b986f98d41912141cabbec196e
|
23.401
|
5.5.2.3.1 General
|
The procedure is based on Packet-switched handover for GERAN A/Gb mode defined in TS 43.129 [8].
Pre-conditions:
- The UE is in ECM-CONNECTED state (E-UTRAN mode);
- The BSS must support PFM, Packet Flow Management, procedures.
|
495b59b986f98d41912141cabbec196e
|
23.401
|
5.5.2.3.2 Preparation phase
|
Figure 5.5.2.3.2-1: E-UTRAN to GERAN A/Gb Inter RAT HO, preparation phase
1. The source eNodeB decides to initiate an Inter RAT Handover to the target GERAN A/Gb mode (2G) system. At this point both uplink and downlink user data is transmitted via the following: Bearer(s) between UE and Source eNodeB, GTP tunnel(s) between Source eNodeB, Serving GW and PDN GW.
If the UE has an ongoing emergency bearer service the source eNodeB shall not initiate PS handover to GERAN.
NOTE 1: The process leading to the handover decision is outside of the scope of this specification
2. The source eNodeB sends a Handover Required (S1AP Cause, Target System Identifier, Source to Target Transparent Container) message to the Source MME to request the CN to establish resources in the Target BSS, Target SGSN and the Serving GW. The bearers that will be subject to data forwarding (if any) are identified by the target SGSN in a later step (see step 7 below).
The 'Target System Identifier' IE contains the identity of the target global cell Id.
3. The Source MME determines from the 'Target System Identifier' IE that the type of handover is IRAT Handover to GERAN A/Gb mode. The Source MME selects the Target SGSN as described in clause 4.3.8.4 on "SGSN Selection Function". The Source MME initiates the Handover resource allocation procedure by sending a Forward Relocation Request (IMSI, Target Identification (shall be set to "empty"), MM Context, PDN Connections, MME Tunnel Endpoint Identifier for Control Plane, MME Address for Control plane, Source to Target Transparent Container, Packet Flow ID, XID parameters (if available), Target Cell Identification, MS Info Change Reporting Action (if available), CSG Information Reporting Action (if available), UE Time Zone, ISR Supported, RAN Cause, Serving Network) message to the target SGSN. If the information ISR Supported is indicated, this indicates that the source MME and associated Serving GW are capable to activate ISR for the UE. When ISR is activated the message should be sent to the SGSN that maintains ISR for the UE when this SGSN is serving the target identified by the Target Identification. This message includes all PDN Connections active in the source system and for each PDN Connection includes the associated APN, the address and the uplink Tunnel endpoint parameters of the Serving GW for control plane, and a list of EPS Bearer Contexts. The old Serving Network is sent to target MME to support the target MME to resolve if Serving Network is changed. In network sharing scenarios Serving Network denotes the serving core network.
The MM context includes information on the EPS Bearer context(s). If none of the UE's EPS Bearers can be supported by the selected target SGSN, the source MME rejects the handover attempt by sending a Handover Preparation Failure (Cause) message to the Source eNodeB.
NOTE 2: If the handover is successful, the source MME will signal to the SGW and/or SCEF to release any non-included EPS Bearers after step 8 of the Execution procedure. The non-included bearers are locally released by the UE following the Bearer Context Status synchronisation that occurs during the Routing Area Update at step 13 of the Execution procedure.
The target SGSN maps the EPS bearers to PDP contexts 1-to-1 and maps the EPS Bearer QoS parameter values of an EPS bearer to the Release 99 QoS parameter values of a bearer context as defined in Annex E.
Prioritization of PDP Contexts is performed by the target core network node, i.e. target SGSN.
If the Source MME supports IRAT Handover to GERAN A/Gb procedure it has to allocate a valid PFI during the bearer activation procedure. RAN Cause indicates the S1AP Cause as received from the source eNodeB. The Source to Target Transparent Container includes the value from the Source to Target Transparent Container received from the source eNodeB.
The MM context contains security related information, e.g. supported ciphering algorithms, as described in TS 29.274 [43]. Handling of security keys is described in TS 33.401 [41].
The target SGSN selects the ciphering algorithm to use. This algorithm will be sent transparently from the target SGSN to the UE in the NAS container for Handover (part of the Target to Source Transparent Container). The IOV-UI parameter, generated in the target SGSN, is used as input to the ciphering procedure and it will also be transferred transparently from the target SGSN to the UE in the NAS container for Handover. More details are described in TS 33.401 [41].
When the target SGSN receives the Forward Relocation Request message the required EPS Bearer, MM, SNDCP and LLC contexts are established and a new P-TMSI is allocated for the UE. When this message is received by the target SGSN, it begins the process of establishing PFCs for all EPS Bearer contexts.
When the target SGSN receives the Forward Relocation Request message it extracts from the EPS Bearer Contexts the NSAPIs and SAPIs and PFIs to be used in the target SGSN. If for a given EPS Bearer Context the target SGSN does not receive a PFI from the source MME, it shall not request the target BSS to allocate TBF resources corresponding to that EPS Bearer Context. If none of the EPS Bearer Contexts forwarded from the source MME has a valid PFI allocated the target SGSN shall consider this as a failure case and the request for Handover shall be rejected.
If when an SAPI and PFI was available at the source MME but the target SGSN does not support the same SAPI and PFI for a certain NSAPI as the source MME, the target SGSN shall continue the Handover procedure only for those NSAPIs for which it can support the same PFI and SAPI as the source MME. All EPS Bearer contexts for which no resources are allocated by the target SGSN or for which it cannot support the same SAPI and PFI (i.e. the corresponding NSAPIs are not addressed in the response message of the target SGSN), are maintained and the related SAPIs and PFIs are kept. These EPS Bearer contexts may be modified or deactivated by the target SGSN via explicit SM procedures upon RAU procedure.
The source MME shall indicate the current XID parameter settings if available (i.e. those XID parameters received during a previous IRAT Handover procedure) to the target SGSN. If the target SGSN can accept all XID parameters as indicated by the source MME, the target SGSN shall create a NAS container for Handover indicating 'Reset to the old XID parameters'. Otherwise, if the target SGSN cannot accept all XID parameters indicated by the source MME or if no XID parameters were indicated by the source MME, the target SGSN shall create a NAS container for Handover indicating Reset (i.e. reset to default parameters).
The target SGSN shall determine the Maximum APN restriction based on the APN Restriction of each bearer context received in the Forward Relocation Request, and shall subsequently store the new Maximum APN restriction value.
If SIPTO at the Local Network is active for a PDN connection in the architecture with stand-alone GW the source MME shall include the Local Home Network ID of the source cell in the PDN Connections corresponding to the SIPTO at the Local Network PDN connection.
4. The target SGSN determines if the Serving GW is to be relocated, e.g., due to PLMN change. If the Serving GW is to be relocated, the target SGSN selects the target Serving GW as described under clause 4.3.8.2 on "Serving GW selection function", and sends a Create Session Request message (IMSI, SGSN Tunnel Endpoint Identifier for Control Plane, SGSN Address for Control plane, PDN GW address(es) for user plane, PDN GW UL TEID(s) for user plane, PDN GW address(es) for control plane, and PDN GW TEID(s) for control plane, the Protocol Type over S5/S8, Serving Network) per PDN connection to the target Serving GW. The Protocol Type over S5/S8 is provided to Serving GW which protocol should be used over S5/S8 interface.
4a. The target Serving GW allocates its local resources and returns a Create Session Response (Serving GW address(es) for user plane, Serving GW UL TEID(s) for user plane, Serving GW Address for control plane, Serving GW TEID for control plane) message to the target SGSN.
5. The target SGSN establishes the EPS Bearer context(s) in the indicated order. The SGSN deactivates, as provided in step 9 of the execution phase, the EPS Bearer contexts which cannot be established.
The Target SGSN requests the Target BSS to establish the necessary resources (PFCs) by sending the message PS Handover Request (Local TLLI, IMSI, Cause, Target Cell Identifier, PFCs to be set-up list, Source RNC to Target BSS Transparent Container and NAS container for handover). The target SGSN shall not request resources for which the Activity Status Indicator within a EPS Bearer Context indicates that no active bearer exists on the source side for that PDP context. The Cause indicates the RAN Cause as received from the source MME. The Source RNC to Target BSS Transparent Container contains the value from the Source to Target Transparent Container received from the source MME. All EPS Bearer Contexts indicate active status because E-UTRAN does not support selective RAB handling.
Based upon the ABQP for each PFC the target BSS makes a decision about which PFCs to assign radio resources. The algorithm by which the BSS decides which PFCs that need resources is implementation specific. Due to resource limitations not all downloaded PFCs will necessarily receive resource allocation. The target BSS allocates TBFs for each PFC that it can accommodate.
The target BSS shall prepare the 'Target to Source Transparent Container' which contains a PS Handover Command including the EPC part (NAS container for Handover) and the RN part (Handover Radio Resources).
5a. The Target BSS allocates the requested resources and returns the applicable parameters to the Target SGSN in the message PS Handover Request Acknowledge (Local TLLI, List of set-up PFCs, Target BSS to Source RNC Transparent Container, Cause). Upon sending the PS Handover Request Acknowledge message the target BSS shall be prepared to receive downlink LLC PDUs from the target SGSN for the accepted PFCs.
Any EPS Bearer contexts for which a PFC was not established are maintained in the target SGSN and the related SAPIs and PFIs are kept. These EPS Bearer contexts shall be deactivated by the target SGSN via explicit SM procedures upon the completion of the routing area update (RAU) procedure.
6. If indirect forwarding and relocation of Serving GW applies the target SGSN sends a Create Indirect Data Forwarding Tunnel Request message (Target SGSN Address(es) and TEID(s) for DL data forwarding) to the Serving GW used for indirect packet forwarding.
Indirect forwarding may be performed via a Serving GW which is different from the Serving GW used as the anchor point for the UE.
6a. The Serving GW returns a Create Indirect Data Forwarding Tunnel Response (Cause, Serving GW DL Address(es) and TEID(s) for data forwarding) message to the target SGSN.
7. The Target SGSN sends the message Forward Relocation Response (Cause, SGSN Tunnel Endpoint Identifier for Control Plane, SGSN Address for Control Plane, Target to Source Transparent Container, RAN Cause, List of set-up PFIs, Address(es) and TEID(s) for User Traffic Data Forwarding, Serving GW change indication) to the Source MME. Serving GW change indication indicates a new Serving GW has been selected. RAN Cause indicates the Cause as received from the target BSS. The Target to Source Transparent Container includes the value from the Target BSS to Source RNC Transparent Container received from the target BSS.
If 'Indirect Forwarding' and relocation of Serving GW applies, then the IEs 'Address(es) and TEID(s) for User Traffic Data Forwarding' contain the DL GTP-U tunnel endpoint parameters received in step 6a. Otherwise the IEs 'Address(es) and TEID(s) for User Traffic Data Forwarding' contains the DL GTP-U tunnel endpoint parameters to the Target SGSN.
The target SGSN activates the allocated LLC/SNDCP engines as specified in TS 44.064 [23] for an SGSN originated Reset or 'Reset to the old XID parameters'.
8. If "Indirect Forwarding" applies, the Source MME sends the message Create Indirect Data Forwarding Tunnel Request (Address(es) and TEID(s) for Data Forwarding (received in step 7)) to the Serving GW used for indirect packet forwarding.
Indirect forwarding may be performed via a Serving GW which is different from the Serving GW used as the anchor point for the UE.
8a. The Serving GW returns the forwarding user plane parameters by sending the message Create Indirect Data Forwarding Tunnel Response (Cause, Serving GW Address(es) and TEID(s) for Data Forwarding). If the Serving GW doesn't support data forwarding, an appropriate cause value shall be returned and the Serving GW Address(es) and TEID(s) will not be included in the message.
|
495b59b986f98d41912141cabbec196e
|
23.401
|
5.5.2.3.3 Execution phase
|
Figure 5.5.2.3.3-1: E-UTRAN to GERAN A/Gb mode Inter RAT HO, execution phase
NOTE 1: For a PMIP-based S5/S8, procedure steps (A) and (B) are defined in TS 23.402 [2]. Step (B) shows PCRF interaction in the case of PMIP-based S5/S8. Steps 10 and 10a concern GTP based S5/S8
The source eNodeB continues to receive downlink and uplink user plane PDUs.
1. The Source MME completes the preparation phase towards Source eNodeB by sending the message Handover Command (Target to Source Transparent Container (PS Handover Command with RN part and EPC part), E‑RABs to Release List, Bearers Subject to Data Forwarding List), S1AP Cause. The "Bearers Subject to Data forwarding list" may be included in the message and it shall be a list of 'Address(es) and TEID(s) for user traffic data forwarding' received from target side in the preparation phase (Step 7 of the preparation phase for Direct Forwarding, else parameters received in Step 8a of the preparation phase). S1AP Cause indicates the RAN Cause as received from the target SGSN.
Source eNodeB initiate data forwarding for the bearers specified in the "Bearers Subject to Data Forwarding List". The data forwarding may go directly i.e. to target SGSN or alternatively go via the Serving GW if so decided by source MME and/or target SGSN in the preparation phase.
2. The Source eNodeB will give a command to the UE to handover to the Target Access System via the message HO from E-UTRAN Command. This message includes a transparent container including radio aspect parameters that the Target BSS has set-up in the preparation phase (RN part). This message also includes the XID and IOV-UI parameters received from the Target SGSN (EPC part).
Upon the reception of the HO from E-UTRAN Command message containing the Handover Command message, the UE shall associate its bearer IDs to the respective PFIs based on the relation with the NSAPI and shall suspend the uplink transmission of the user plane data.
3. If the PLMN has configured Secondary RAT usage data reporting and the source eNodeB has Secondary RAT usage data to report, the eNodeB sends the RAN Usage data report message (Secondary RAT usage data) to the MME. Since the handover is an inter-RAT handover, the MME continues with the Secondary RAT usage data reporting procedure as in clause 5.7A.3. The reporting procedure in clause 5.7A.3 is only performed if PGW secondary RAT usage reporting is active.
4. The UE moves to the Target GERAN A/Gb (2G) system and performs executes the handover according to the parameters provided in the message delivered in step 2. The procedure is the same as in step 6 in clause 5.3.2.2 in TS 43.129 [8] with the additional function of association of the received PFI and existing Bearer Id related to the particular NSAPI.
5. After accessing the cell using access bursts and receiving timing advance information from the BSS in step 4, the UE processes the NAS container and then sends one XID response message to the target SGSN via target BSS. The UE sends this message immediately after receiving the Packet Physical Information message containing the timing advance or, in the synchronised network case, immediately if the PS Handover Access message is not required to be sent.
Upon sending the XID Response message, the UE shall resume the user data transfer only for those NSAPIs for which there are radio resources allocated in the target cell. For NSAPIs using LLC ADM, for which radio resources were not allocated in the target cell, the UE may request for radio resources using the legacy procedures.
If the Target SGSN indicated XID Reset (i.e. reset to default XID parameters) in the NAS container included in the HO from E-UTRAN Command message, and to avoid collision cases the mobile station may avoid triggering XID negotiation for any LLC SAPI used in LLC ADM, but wait for the SGSN to do so (see step 12). In any case the mobile station may avoid triggering XID negotiation for any LLC SAPI used in LLC ABM, but wait for the SGSN to do so (see step 12a).
This step is the same as specified in clause 5.3.2.2 in TS 43.129 [8].
6. Upon reception of the first correct RLC/MAC block (sent in normal burst format) from the UE to the Target BSS, the Target BSS informs the Target SGSN by sending the message PS Handover Complete (IMSI, and Local TLLI, Request for Inter RAT Handover Info). The target BSS that supports inter-RAT PS handover to UTRAN shall, when the INTER RAT HANDOVER INFO was not included in the Source BSS to Target BSS transparent container received in the PS HANDOVER REQUEST message as specified in TS 48.018 [42], request the INTER RAT HANDOVER INFO from the target SGSN by setting the 'Request for Inter RAT Handover Info' to '1'.
7. The Target BSS also relays the message XID Response to the Target SGSN. Note, the message in step 6 and 7 may arrive in any order in the Target SGSN.
8. Then the Target SGSN knows that the UE has arrived to the target side and Target SGSN informs the Source MME by sending the Forward Relocation Complete Notification (ISR Activated, Serving GW change) message. If ISR Activated is indicated, the source MME shall maintain the UE's contexts and activate ISR, which is only possible when the S‑GW is not changed. The Source MME will also acknowledge that information. A timer in source MME is started to supervise when resources in Source eNodeB and Source Serving GW (for Serving GW relocation) shall be released.
Upon receipt of the Forward Relocation Complete Acknowledge message the target SGSN starts a timer if the target SGSN allocated S‑GW resources for indirect forwarding.
For all bearers that were not included in the Forward Relocation Request message sent in step 3, the MME now releases them by sending a Delete Bearer Command to the SGW, or, the appropriate message to the SCEF.
9. The Target SGSN will now complete the Handover procedure by informing the Serving GW (for Serving GW relocation this will be the Target Serving GW) that the Target SGSN is now responsible for all the EPS Bearer Context(s) the UE has established. This is performed in the message Modify Bearer Request (SGSN Tunnel Endpoint Identifier for Control Plane, NSAPI(s), SGSN Address for Control Plane, SGSN Address(es) and TEID(s) for User Traffic for the accepted EPS bearers and RAT type, ISR Activated) per PDN connection. As it is a mobility from E-UTRAN, if the target SGSN supports location information change reporting, the target SGSN shall include the User Location Information (according to the supported granularity) in the Modify Bearer Request, regardless of whether location information change reporting had been requested in the previous RAT by the PDN GW. If the PDN GW requested User CSG information (determined from the UE context), the SGSN also includes the User CSG Information IE in this message. If the UE Time Zone has changed, the SGSN includes the UE Time Zone IE in this message. If Serving GW is not relocated but the Serving Network has changed or if the SGSN has not received any old Serving Network information from the old MME, the SGSN includes the new Serving Network IE in this message. In network sharing scenarios Serving Network denotes the serving core network. If indicated, ISR Activated indicates that ISR is activated, which is only possible when the S‑GW was not changed. When the Modify Bearer Request does not indicate ISR Activated and S‑GW is not changed, the S‑GW deletes any ISR resources by sending a Delete Bearer Request to the other CN node that has bearer resources on the S‑GW reserved.
The SGSN releases the non-accepted EPS Bearer contexts by triggering the EPS Bearer context deactivation procedure. If the Serving GW receives a DL packet for a non-accepted bearer, the Serving GW drops the DL packet and does not send a Downlink Data Notification to the SGSN.
10. The Serving GW (for Serving GW relocation this will be the Target Serving GW) may inform the PDN GW the change of, for example, for Serving GW relocation or the RAT type, that e.g. can be used for charging, by sending the message Modify Bearer Request per PDN connection. The S‑GW also includes User Location Information IE and/or UE Time Zone IE and/or User CSG Information IE if they are present in step 9. Serving Network should be included if it is received in step 9 or in step 4 in clause 5.5.2.3.2. For Serving GW relocation, the Serving GW allocates DL TEIDs on S5/S8 even for non-accepted bearers and may include the PDN Charging Pause Supported Indication. The PDN GW must acknowledge the request with the message Modify Bearer Response. In the case of Serving GW relocation, the PDN GW updates its context field and returns a Modify Bearer Response (Charging Id, MSISDN, PDN Charging Pause Enabled Indication (if PDN GW has chosen to enable the function), etc.) message to the Serving GW. The MSISDN is included if the PDN GW has it stored in its UE context. If location information change reporting is required and supported in the target SGSN, the PDN GW shall provide MS Info Change Reporting Action in the Modify Bearer Response.
If PCC infrastructure is used, the PDN GW informs the PCRF about the change of, for example, the RAT type.
If the Serving GW is relocated, the PDN GW shall send one or more "end marker" packets on the old path immediately after switching the path. The source Serving GW shall forward the "end marker" packets to the source eNodeB.
11. The Serving GW (for Serving GW relocation this will be the Target Serving GW) acknowledges the user plane switch to the Target SGSN via the message Modify Bearer Response (Cause, Serving GW Tunnel Endpoint Identifier for Control Plane, Serving GW Address for Control Plane, Protocol Configuration Options, MS Info Change Reporting Action). At this stage the user plane path is established for all EPS Bearer contexts between the UE, Target BSS, Target SGSN, Serving GW (for Serving GW relocation this will be the Target Serving GW) and PDN GW.
If the Serving GW does not change, the Serving GW shall send one or more "end marker" packets on the old path immediately after switching the path.
12. If the Target SGSN indicated XID Reset (i.e. reset to default XID parameters) in the NAS container included in the HO from E-UTRAN Command message, then on receipt of the PS Handover Complete the Target SGSN initiates an LLC/SNDCP XID negotiation for each LLC SAPI used in LLC ADM. In this case if the Target SGSN wants to use the default XID parameters, it shall send an empty XID Command. If the Target SGSN indicated 'Reset to the old XID parameters' in the NAS container, no further XID negotiation is required for LLC SAPIs used in LLC ADM only.
12a. The Target SGSN (re-)establishes LLC ABM for the EPS Bearer contexts which use acknowledged information transfer. During the exchange of SABM and UA the SGSN shall perform LLC/SNDCP XID negotiation.
These steps (12 and 12a) are the same as specified in clause 5.3.2.2 in TS 43.129 [8].
13. After the UE has finished the reconfiguration procedure the UE shall initiate the Routing Area Update procedure.
NOTE 2: The RAU procedure is performed regardless if the UE has this routing area registered or not, as specified by TS 43.129 [8]. This is needed e.g. to update the START-PS value stored in the 2G-SGSN. The START_PS is delivered to SGSN in INTER RAT HANDOVER INFO parameter of RAU Complete message when requested by SGSN in RAU Accepted.
The target SGSN knows that an IRAT Handover has been performed for this UE as it received the bearer context(s) by handover messages and therefore the target SGSN performs only a subset of the RAU procedure, specifically it excludes the context transfer procedures between source MME and target SGSN.
For a UE supporting CIoT EPS Optimisations, the UE uses the bearer status information in the RAU Accept to identify any non-transferred bearers that it shall locally release.
13a. Upon reception of the PS Handover Complete message with the 'Request for Inter RAT Handover Info' set to '1', the SGSN should send then PS Handover Complete Acknowledge (TLLI, INTER RAT HANDOVER INFO) to the target BSS.
NOTE 3: An SGSN that does not recognize the "Request for Inter RAT Handover Info" in the PS Handover Complete message will not send the PS Handover Complete Acknowledge message back to the BSS.
The target BSS receiving the PS Handover Complete Acknowledge message shall set the 'Reliable INTER RAT HANDOVER' to '1' in the PS Handover Required message in any subsequent PS handover to GERAN A/Gb mode. The target BSS failing to receive the PS Handover Complete Acknowledge message shall set the 'Reliable INTER RAT HANDOVER' to '0' in the PS Handover Required message in any subsequent PS handover to GERAN A/Gb mode. The Target BSS shall, upon receipt of the INTER RAT HANDOVER INFO in the PS Handover Complete Acknowledge message, overwrite its current INTER RAT HANDOVER INFO with this new one.
14. When the timer started at step 8 expires, the source MME sends a Release Resources message to the source eNodeB. The Source eNodeB releases its resources related to the UE.
When the timer started in step 8 expires and if the source MME received the Serving GW change indication in the Forward Relocation Response message, it deletes the EPS bearer resources by sending Delete Session Request (Cause, Operation Indication, Secondary RAT usage data) messages to the Source Serving GW. The operation Indication flag is not set, that indicates to the Source Serving GW that the Serving GW changes and the Source Serving GW shall not initiate a delete procedure towards the PDN GW. Secondary RAT usage data is included if it was received in step 3. The Source Serving GW acknowledges with Delete Session Response (Cause) messages. If ISR has been activated before this procedure, the cause indicates to the Source S‑GW that the Source S‑GW shall delete the bearer resources on the other old CN node by sending Delete Bearer Request message(s) to that CN node.
15. If indirect forwarding was used then the expiry of the timer at source MME started at step 8 triggers the source MME to send a Delete Indirect Data Forwarding Tunnel Request message to the S‑GW to release the temporary resources used for indirect forwarding.
16. If indirect forwarding was used and the Serving GW is relocated, then the expiry of the timer at target SGSN started at step 8 triggers the target SGSN to send a Delete Indirect Data Forwarding Tunnel Request message to the target S‑GW to release temporary resources used for indirect forwarding.
|
495b59b986f98d41912141cabbec196e
|
23.401
|
5.5.2.3.4 E-UTRAN to GERAN A/Gb mode Inter RAT handover reject
|
The Target BSS may reject the use of the Handover procedure if none of the requested PFCs in the PS Handover Request message could be established. In this case no UE context is established in the target SGSN/BSS and no resources are allocated. The UE remains in the Source eNodeB/MME.
Figure 5.5.2.3.4-1: E-UTRAN to GERAN A/Gb Inter RAT HO reject
1. Steps 1 to 5 in the flow are identical to the ones in clause 5.5.2.3.2.
6. If the Target BSS fails to allocate any resources for any of the requested PFCs it sends a PS Handover Request Nack (Cause) message to the Target SGSN. When the Target SGSN receives the PS Handover Request Nack message from Target BSS the Target SGSN clears any reserved resources for this UE.
7. This step is only performed for Serving GW relocation, i.e. if Steps 4/4a have been performed. The Target SGSN deletes the EPS bearer resources by sending Delete Session Request (Cause) messages to the Target Serving GW. The Target Serving GW acknowledges with Delete Session Response (Cause) messages.
8. The Target SGSN sends the Forward Relocation Response (Cause) message to the Source MME.
9. When the Source MME receives the Forward Relocation Response message it send a Handover Preparation Failure (Cause) message to the Source eNodeB.
|
495b59b986f98d41912141cabbec196e
|
23.401
|
5.5.2.4 GERAN A/Gb mode to E-UTRAN Inter RAT handover
| |
495b59b986f98d41912141cabbec196e
|
23.401
|
5.5.2.4.1 General
|
The procedure is based on Packet-switched handover for GERAN A/Gb mode, defined in TS 43.129 [8].
Pre-conditions:
- The UE is in READY state (GERAN A/Gb mode);
- The UE has at least one PDP/EPS Bearer Context established;
- The BSS must support PFM, Packet Flow Management, procedures.
|
495b59b986f98d41912141cabbec196e
|
23.401
|
5.5.2.4.2 Preparation phase
|
Figure 5.5.2.4.2-1: GERAN A/Gb mode to E-UTRAN inter RAT HO, preparation phase
1. The source access system, Source BSS, decides to initiate an Inter-RAT Handover to the E-UTRAN. At this point both uplink and downlink user data is transmitted via the following: Bearers between UE and Source BSS, BSSGP PFC tunnel(s) between source BSS and source SGSN, GTP tunnel(s) between Source SGSN, Serving GW and PDN GW.
NOTE 1: The process leading to the handover decision is outside of the scope of this specification.
2. The source BSS sends the message PS handover Required (TLLI, Cause, Source Cell Identifier, Target eNodeB Identifier, Source eNodeB to Target eNodeB Transparent Container and active PFCs list) to Source SGSN to request the CN to establish resources in the Target eNodeB, Target MME and the Serving GW.
NOTE 2: In contrast to most inter-RAT handover preparation phases, this Source to Target Transparent Container does not contain the UE's target RAT radio capabilities.
3. The Source SGSN determines from the 'Target eNodeB Identifier' IE that the type of handover is IRAT PS Handover to E-UTRAN. The Source SGSN selects the Target MME as described in clause 4.3.8.3 on "MME Selection Function". The Source SGSN initiates the Handover resource allocation procedure by sending message Forward Relocation Request (IMSI, Target Identification, MM Context, PDN Connections, SGSN Tunnel Endpoint Identifier for Control Plane, SGSN Address for Control plane, Source to Target Transparent Container, RAN Cause, Packet Flow ID, SNDCP XID parameters, LLC XID parameters, MS Info Change Reporting Action (if available), CSG Information Reporting Action (if available), UE Time Zone, ISR Supported, Serving Network) to the target MME. When ISR is activated the message should be sent to the MME that maintains ISR for the UE when this MME is serving the target identified by the Target Identification. If indicated, the information ISR Supported indicates that the source SGSN and associated Serving GW are capable to activate ISR for the UE. This message includes all PDN Connections active in the source system and for each PDN Connection includes the associated APN, the address and the uplink tunnel endpoint parameters of the Serving GW for control plane, and a list of EPS Bearer Contexts established in the source system. The EPS Bearer Contexts indicate the PFIs and the XID parameters related to those EPS Bearer Contexts, and the uplink Tunnel endpoint parameters of the Serving GW. The old Serving Network is sent to target MME to support the target MME to resolve if Serving Network is changed. In network sharing scenarios Serving Network denotes the serving core network.
The RAN Cause includes the value from the Cause IE received from the source BSS. Source to Target Transparent Container includes the value from the Source eNodeB to Target eNodeB Transparent Container received from the source BSS.
The MM context includes information on the EPS Bearer context(s). If none of the UE's EPS Bearers can be supported by the selected target MME, the source SGSN rejects the handover attempt by sending a PS Handover Required Negative Acknowledge (Cause) message to the Source BSS.
NOTE 3: If the handover is successful, the source SGSN will signal to the SGW and/or SCEF to release any non-included EPS Bearers after step 6 of the Execution procedure. The non-included bearers are locally released by the UE following the Bearer Context Status synchronisation that occurs during the Tracking Area Update at step 12 of the Execution procedure.
Prioritization of EPS Bearer Contexts is performed by the target core network node.
The MME establishes the EPS bearer(s) in the prioritized order. The MME deactivates, as provided in step 8 of the execution phase, the EPS bearers which cannot be established.
The MM context contains security related information, e.g. supported ciphering algorithms as described in TS 29.274 [43]. Handling of security keys is described in TS 33.401 [41].
For the EPS Bearer Context with traffic class equals 'Background', the source SGSN shall indicate via the Activity Status Indicator IE that radio bearers shall be established on the target side.
The target MME shall determine the Maximum APN restriction based on the APN Restriction of each bearer context received in the Forward Relocation Request, and shall subsequently store the new Maximum APN restriction value.
4. The target MME determines if the Serving GW is to be relocated, e.g. due to PLMN change. If the Serving GW is to be relocated, the target MME selects the target Serving GW as described under clause 4.3.8.2 on "Serving GW selection function". The target MME sends a Create Session Request message (IMSI, MME Tunnel Endpoint Identifier for Control Plane, MME Address for Control plane, PDN GW address(es) for user plane, PDN GW UL TEID(s) for user plane, PDN GW address for control plane, and PDN GW TEID(s) for control plane, the Protocol Type over S5/S8, Serving Network) per PDN connection to the target Serving GW. The Protocol Type over S5/S8 is provided to Serving GW which protocol should be used over S5/S8 interface.
4a. The target Serving GW allocates its local resources and returns them in a Create Session Response (Serving GW address(es) for user plane, Serving GW UL TEID(s) for user plane, Serving GW Address for control plane, Serving GW TEID for control plane) message to the target MME.
5. The Target MME will request the Target eNodeB to establish the Bearer(s) by sending the message Handover Request (UE Identifier, S1AP Cause, Integrity protection information (i.e. IK and allowed Integrity Protection algorithms), Encryption information (i.e. CK and allowed Ciphering algorithms), EPS Bearers to be setup list, Source to Target Transparent Container, Handover Restriction List). The Target MME ignores any Activity Status Indicator within an EPS Bearer Context and requests the eNodeB to allocate resources for all EPS Bearer Contexts received from the source side. The S1AP Cause includes the value from the RAN Cause IE received from the source SGSN. The target eNodeB shall ignore it if the number of radio bearers in the Source to Target Transparent container does not comply with the number of bearers requested by the MME and allocate bearers as requested by the MME. Handover Restriction List is sent if it is available in the Target MME; it is described in clause 4.3.5.7.
For each EPS bearer requested to be established, 'EPS Bearers To Be Setup' IE shall contain information such as ID, bearer parameters, Transport Layer Address, "Data forwarding not possible" indication, and S1 Transport Association. The Transport Layer Address is the Serving GW Address for user data, and the S1 Transport Association corresponds to the uplink Tunnel Endpoint Identifier Data. "Data forwarding not possible" indication shall be included if the target MME decides the corresponding bearer will not be subject to data forwarding.
The ciphering and integrity protection keys will be sent transparently from the target eNodeB to the UE in the Target to Source Transparent Container, and in the message PS Handover Command from source BSS to the UE. This will then allow data transfer to continue in the new RAT/mode target cell without requiring a new AKA (Authentication and Key Agreement) procedure. More details are described in TS 33.401 [41].
5a. The Target eNodeB allocates the request resources and returns the applicable parameters to the Target MME in the message Handover Request Acknowledge (Target to Source Transparent Container, S1AP Cause, EPS Bearers setup list, EPS Bearers failed to setup list). Upon sending the Handover Request Acknowledge message the target eNodeB shall be prepared to receive downlink GTP PDUs from the Serving GW for the accepted EPS bearers.
6. If 'Indirect Forwarding' and relocation of Serving GW apply, the target MME sends a Create Indirect Data Forwarding Tunnel Request message (Target eNodeB Address(es) and TEID(s) for DL data forwarding) to the Serving GW.
Indirect forwarding may be performed via a Serving GW which is different from the Serving GW used as the anchor point for the UE.
6a. The Serving GW returns a Create Indirect Data Forwarding Tunnel Response (Cause, Serving GW Address(es) and DL TEID(s) for data forwarding) message to the target MME.
7. The Target MME sends the message Forward Relocation Response (Cause, List of Set Up PFCs, MME Tunnel Endpoint Identifier for Control Plane, RAN Cause, MME Address for control plane, Target to Source Transparent Container, Address(es) and TEID(s) for Data Forwarding, Serving GW change indication) to the Source SGSN. Serving GW change indication indicates whether a new Serving GW has been selected. The RAN Cause includes the value from the S1AP Cause IE received from the target eNodeB. The Target to Source Transparent Container includes the value from the Target to Source Transparent Container received from the target eNodeB.
If 'Direct Forwarding' applies or if 'Indirect Forwarding' but no relocation of Serving GW applies, then the IEs 'Address(es) and TEID(s) for Data Forwarding' contain the DL GTP-U tunnel endpoint parameters to the eNodeB received in step 5a. If 'Indirect Forwarding' and relocation of Serving GW apply the IEs 'Address(es) and TEID(s) for Data Forwarding' contain the DL GTP-U tunnel endpoint parameters to the Serving GW received in step 6a.
8. If 'Indirect Forwarding' applies, the source SGSN shall send the message Create Indirect Data Forwarding Tunnel Request (Address(es) and TEID(s) for Data Forwarding (received in step 7)) to the Serving GW used for indirect packet forwarding.
Indirect forwarding may be performed via a Serving GW which is different from the Serving GW used as the anchor point for the UE.
8a. The Serving GW returns the forwarding user plane parameters by sending the message Create Indirect Data Forwarding Tunnel Response (Cause, Serving GW Address(es) and TEID(s) for Data Forwarding). If the Serving GW doesn't support data forwarding, an appropriate cause value shall be returned and the Serving GW Address(es) and TEID(s) will not be included in the message.
|
495b59b986f98d41912141cabbec196e
|
23.401
|
5.5.2.4.3 Execution phase
|
Figure 5.5.2.4.3-1: GERAN A/Gb mode to E-UTRAN Inter RAT HO, execution phase
NOTE: For a PMIP-based S5/S8, procedure steps (A) are defined in TS 23.402 [2]. Steps 9 and 9a concern GTP based S5/S8.
The source SGSN continues to receive downlink and uplink user plane PDUs.
When source SGSN receives the Forward Relocation Response message it may start downlink N-PDU relay and duplication to the target eNodeB (for Direct Forwarding) or via the Serving GW (for Indirect Forwarding), and the target eNodeB may start blind transmission of downlink user data towards the UE over the allocated radio channels.
1. The Source SGSN completes the preparation phase towards Source BSS by sending the message PS HO Required Acknowledge (TLLI, List of Set Up PFCs, Target RNC to Source BSS Transparent Container, Cause). This message includes all PFIs that could be established on the Target side. The Cause includes the value from the RAN Cause IE received from the target MME. The Target RNC to Source BSS Transparent Container includes the value from the Target to Source Transparent Container received from the target MME.
Before sending the PS Handover Required Acknowledge message, the source SGSN may suspend downlink data transfer for any EPS Bearer contexts.
Before sending the PS Handover Command message to the UE the source BSS, may try to empty the downlink BSS buffer for any BSS PFCs.
2. The Source BSS will command the UE to handover to the target eNodeB via the message PS Handover Command. The access system specific message to UE includes a transparent container including radio aspect parameters that the Target eNodeB has set-up in the preparation phase.
3. Void.
4. The UE moves to the E-UTRAN and performs access procedures toward Target eNodeB.
5. When the UE has got access to Target eNodeB it sends the message HO to E-UTRAN Complete.
The UE shall implicitly derive the EPS bearers for which an E-RAB was not established from the PS Handover Command and deactivate them locally without an explicit NAS message at this step.
6. When the UE has successfully accessed the Target eNodeB, the Target eNodeB informs the Target MME by sending the message Handover Notify (TAI+ECGI). As a separate activity the Target eNodeB retrieves the UE E-UTRA capability information using the procedure for UE Radio Capability Handling (see clause 5.11.2).
If Dual Connectivity is activated for the UE, the PSCell ID shall be included in the Handover Notify message.
7. Then the Target MME knows that the UE has arrived to the target side and Target MME informs the Source SGSN by sending the Forward Relocation Complete Notification (ISR Activated, Serving GW change) message. If indicated, ISR Activated indicates to the source SGSN that it shall maintain the UE's contexts and activate ISR, which is only possible when the S‑GW is not changed. The Source SGSN shall also acknowledge that information. When the Forward Relocation Complete Notification message has been received and there is no longer any need for the SGSN to forward data, the SGSN stops data forwarding. A timer in source SGSN is started to supervise when resources in the Source Serving GW (for Serving GW relocation) shall be released.
Upon receipt of the Forward Relocation Complete Acknowledge message the target MME starts a timer if the target MME applies indirect forwarding.
8. The Target MME will now complete the Handover procedure by informing the Serving GW (for Serving GW relocation this will be the Target Serving GW) that the Target MME is now responsible for all the EPS bearers the UE have established. This is performed in the message Modify Bearer Request (Cause, MME Tunnel Endpoint Identifier for Control Plane, EPS Bearer ID(s), MME Address for Control Plane, eNodeB Address(es) and TEID(s) for User Traffic for the accepted EPS bearers and RAT type, ISR Activated, User Location Information, PSCell ID) per PDN connection. As it is a mobility from GERAN, if the target MME supports location information change reporting, the target MME shall include the User Location Information (according to the supported granularity) in the Modify Bearer Request, regardless of whether location information change reporting had been requested in the previous RAT by the PDN GW. If the PDN GW requested User CSG information (determined from the UE context), the MME also includes the User CSG Information IE in this message. If the UE Time Zone has changed, the MME includes the UE Time Zone IE in this message. If the Serving GW is not relocated but the Serving Network has changed or if the MME has not received any old Serving Network information from the old SGSN, the MME includes the new Serving Network IE in this message. If indicated, ISR Activated indicates that ISR is activated, which is only possible when the S‑GW was not changed. When the Modify Bearer Request does not indicate ISR Activated and S‑GW is not changed, the S‑GW deletes any ISR resources by sending a Delete Bearer Request to the other CN node that has bearer resources on the S‑GW reserved. If the MME has received PSCell ID in step 6, it shall include it in Modify Bearer Request.
The MME releases the non-accepted dedicated bearers by triggering the bearer release procedure as specified in clause 5.4.4.2. If the Serving GW receives a DL packet for a non-accepted bearer, the Serving GW drops the DL packet and does not send a Downlink Data Notification to the MME.
If the default bearer of a PDN connection has not been accepted by the target eNodeB and there are other PDN connections active, the MME shall handle it in the same way as if all bearers of a PDN connection have not been accepted. The MME releases these PDN connections by triggering the MME requested PDN disconnection procedure specified in clause 5.10.3.
9. The Serving GW (for Serving GW relocation this will be the Target Serving GW) informs the PDN GW(s) the change of, for example, for Serving GW relocation or the RAT type, that e.g. can be used for charging, by sending the message Modify Bearer Request per PDN connection. The S‑GW also includes User Location Information IE and/or UE Time Zone IE and/or User CSG Information IE if they are present in step 8. Serving Network should be included if it is received in step 8 or in step 4 in clause 5.5.2.4.2. For Serving GW relocation, the Serving GW allocates DL TEIDs on S5/S8 even for non-accepted bearers and PDN Charging Pause Support Indication shall be included. The PDN GW must acknowledge the request with the message Modify Bearer Response (Charging Id, MSISDN, PDN Charging Pause Enabled Indication (if PDN GW has chosen to enable the function), etc.) to the Serving GW. If location information change reporting is required and supported in the target MME, the PDN GW shall provide MS Info Change Reporting Action in the Modify Bearer Response.
If PCC infrastructure is used, the PDN GW informs the PCRF about the change of, for example, the RAT type.
If the Serving GW is relocated, the PDN GW shall send one or more "end marker" packets on the old path immediately after switching the path in order to assist the reordering function in the target eNodeB. The source Serving GW shall forward the "end marker" packets to the source SGSN.
10. The Serving GW (for Serving GW relocation this will be the Target Serving GW) acknowledges the user plane switch to the Target MME via the message Modify Bearer Response (Cause, Serving GW Tunnel Endpoint Identifier for Control Plane, Serving GW (for Serving GW relocation this will be the Target Serving GW) Address for Control Plane, Protocol Configuration Options, MS Info Change Reporting Action). At this stage the user plane path is established for all bearers between the UE, Target eNodeB, Serving GW (for Serving GW relocation this will be the Target Serving GW) and PDN GW.
If the Serving GW does not change, the Serving GW shall send one or more "end marker" packets on the old path immediately after switching the path in order to assist the reordering function in the target eNodeB.
11. When the timer at the source SGSN started in step 7 expires the Source SGSN will clean-up all its resources towards Source BSS by performing the BSS Packet Flow Delete procedure.
12. The UE initiates a Tracking Area Update procedure when one of the conditions listed in clause "Triggers for tracking area update" applies.
The target MME knows that an IRAT Handover has been performed for this UE as it received the bearer context(s) by handover messages and therefore the target MME performs only a subset of the TA update procedure, specifically it excludes the context transfer procedures between source SGSN and target MME.
If the Subscription Data received from the HSS (during the TAU in step 12) contains information that is necessary for the E-UTRAN to be aware of (e.g. a restriction in the UE's permission to use NR as a secondary RAT, Unlicensed Spectrum in the form of LAA/LWA/LWIP/NR-U (as specified in clause 4.3.30) or a combination of them), or an existing UE context in the MME indicates that the UE is not permitted to use NR as a secondary RAT, Unlicensed Spectrum or a combination of them and the MME has not provided this information to the target eNodeB during step 5 of the handover preparation phase, then the MME sends an updated Handover Restriction List in the Downlink NAS Transport message that it sends to E-UTRAN. If the UE is not allowed to use NR as Secondary RAT, the MME indicates that to the UE in TAU Accept message.
13. When the timer at the source SGSN started in step 7 expires and if the source SGSN received the Serving GW change indication in the Forward Relocation Response message, it deletes the EPS bearer resources by sending Delete Session Request (Cause, Operation Indication) messages to the Source Serving GW. The operation Indication flag is not set, that indicates to the Source Serving GW that the Source Serving GW shall not initiate a delete procedure towards the PDN GW. The Source Serving GW acknowledges with Delete Session Response (Cause) messages. If ISR has been activated before this procedure, the cause indicates to the Source S‑GW that the Source S‑GW shall delete the bearer resources on the other old CN node by sending Delete Bearer Request message(s) to that CN node.
14. If indirect forwarding was used then the expiry of the timer at source SGSN started at step 7 triggers the source SGSN to send a Delete Indirect Data Forwarding Tunnel Request message to the S‑GW to release the temporary resources used for indirect forwarding.
15. If indirect forwarding was used and the Serving GW is relocated, then the expiry of the timer at target MME started at step 6 triggers the target MME to send a Delete Indirect Data Forwarding Tunnel Request message to the target S‑GW to release temporary resources used for indirect forwarding.
|
495b59b986f98d41912141cabbec196e
|
23.401
|
5.5.2.4.4 GERAN A/Gb mode to E-UTRAN Inter RAT handover reject
|
The Target eNodeB may reject the use of the Handover procedure if none of the requested EPS bearers in the Handover Request message could be established. In this case no UE context is established in the target MME/eNodeB and no resources are allocated. The UE remains in the Source BSS/SGSN.
Figure 5.5.2.4.4-1: GERAN A/Gb mode to E-UTRAN inter RAT HO reject
1. Steps 1 to 5 in the flow are identical to the ones in clause 5.5.2.4.2.
6. If the Target eNodeB fails to allocate any resources for any of the requested EPS Bearers it sends a Handover Failure (Cause) message to the Target MME. When the Target MME receives the Handover Failure message from Target eNodeB the Target MME clears any reserved resources for this UE.
7. This step is only performed for Serving GW relocation, i.e. if Steps 4/4a have been performed. The Target MME deletes the EPS bearer resources by sending Delete Session Request (Cause) messages to the Target Serving GW. The Target Serving GW acknowledges with Delete Session Response (Cause) messages.
8. The Target MME sends the Forward Relocation Response (Cause) message to the Source SGSN.
9. When the Source SGSN receives the Forward Relocation Response message it send a PS Handover Required Negative Acknowledge (Cause) message to the Source BSS.
|
495b59b986f98d41912141cabbec196e
|
23.401
|
5.5.2.5 Inter RAT handover Cancel
| |
495b59b986f98d41912141cabbec196e
|
23.401
|
5.5.2.5.1 General
|
Instead of completing the handover procedure, the source RAN node (eNodeB, RNC or BSS) may at any time during the handover procedure, up to the time when a handover command message is sent to the UE cancel the handover. The reason for cancelling may be e.g. due to a timer expiration or due to other events within the source RAN node and is initiated by sending a handover cancel PDU to the source EPC node (MME or SGSN).
A handover cancel PDU shall also be sent by the source RAN node after a handover command message is sent to the UE for the case where the handover fails and the UE returns to the old cell or radio contact with the UE is lost. This is done in order to release the resources reserved for the Handover in the target system.
|
495b59b986f98d41912141cabbec196e
|
23.401
|
5.5.2.5.2 Source RAN to Target RAN Inter RAT handover Cancel
|
Figure 5.5.2.5.2-1: Inter RAT handover Cancel
1. The source RAN decides to cancel the previously requested relocation of Handover resources. This may be due to not enough accepted bearers, UE returned to source cell or any other reason.
2. The source RAN sends a Cancel message with a Cause to the source EPC node (SGSN or MME). If the source RAN is:
a) BSS the message sent is PS Handover Cancel (Cause),
b) RNC the message sent is Relocation Cancel (Cause), or
c) eNodeB the message sent is Handover Cancel (Cause).
3. The source EPC node terminates the relocation towards the target side by sending a Relocation Cancel Request (IMSI) message to the target EPC node. The Source EPC node also resumes operation on the resources in the source side.
4. The target EPC node triggers the release of resources in the target RAN and also releases its own resources allocated for this handover.
5. This step is only performed for Serving GW relocation. The Target EPC node deletes the EPS bearer resources by sending Delete Session Request (Cause) messages to the Target Serving GW. The Target Serving GW acknowledges with Delete Session Response (Cause) messages.
6. The target EPC node acknowledge the release of all resources on the target side by returning a Relocation Cancel Response (Cause) message to the source EPC node.
7. The source EPC node returns a Cancel acknowledge message to the source RAN. If the source RAN is:
a) BSS there will be no acknowledge message sent to the source BSS,
b) RNC the message sent is Relocation Cancel Acknowledge (Cause), or
c) eNodeB the message sent is Handover Cancel Acknowledge (Cause).
8. If indirect forwarding tunnel is setup during handover preparation then cancellation of handover triggers the source MME/SGSN to send a Delete Indirect Data Forwarding Tunnel Request message to the S‑GW to release the temporary resources used for indirect forwarding.
9. If indirect forwarding tunnel is setup during handover preparation and serving GW is relocated then cancellation of handover triggers the target MME/SGSN to send a Delete Indirect Data Forwarding Tunnel Request message to the S‑GW to release the temporary resources used for indirect forwarding.
|
495b59b986f98d41912141cabbec196e
|
23.401
|
5.6 Network Assisted Cell Change
|
Network Assisted Cell Change (NACC) is a means that enables better performance for packet data services upon inter-cell change for those networks that do not support PS Handover. It reduces the service interruption time for UEs in active mode upon cell change by providing in the source cell, prior to the cell change, system information of a target cell allowing packet access.
Within the scope of this specification, NACC is applicable for inter-RAT cell changes from a source E‑UTRAN cell towards a target GERAN cell.
When the UE changes from a source E-UTRAN cell towards a target GERAN cell, the UE locally deactivates ISR by setting its TIN from "RAT-related TMSI" to "GUTI", if any EPS bearer context activated after the ISR was activated in the UE exists.
When the UE changes from a source E-UTRAN cell in connected mode towards a target GERAN cell from the same RA via Cell Change Order that is not for CS fallback and the ISR is active, the UE locally deactivates ISR by setting its TIN from "RAT-related TMSI" to "GUTI".
|
495b59b986f98d41912141cabbec196e
|
23.401
|
5.6.1 Architecture Principles for E-UTRAN to GERAN NACC
|
Introducing NACC from E‑UTRAN to GERAN follows the principles of the Network Assisted Cell Change between UTRAN and GERAN as described in TS 25.413 [22] and TS 23.060 [7]. It specifies the RAN Information Management (RIM) procedures as specified in clause 5.15 and depicted in figure 5.6‑1.
Figure 5.6-1: E-UTRAN to GERAN NACC basic network architecture
The support for the NACC from E‑UTRAN to GERAN has the following impacts on E‑UTRAN / GERAN architecture:
- Affected nodes: BSC, eNodeB, MME, SGSN;
- Affected network interfaces: Gb, Iu, S3, Gn, S1;
- Affected radio interfaces: Um and Uu.
|
495b59b986f98d41912141cabbec196e
|
23.401
|
5.6.2 Void
| |
495b59b986f98d41912141cabbec196e
|
23.401
|
5.7 Information storage
|
This clause describes information storage structures required for the EPS when 3GPP access only is deployed. Information storage for the case where non 3GPP accesses are deployed is in TS 23.402 [2].
|
495b59b986f98d41912141cabbec196e
|
23.401
|
5.7.1 HSS
|
IMSI is the prime key to the data stored in the HSS. The data held in the HSS is defined in Table 5.7.1-1 here below.
The table below is applicable to E‑UTRAN in stand-alone operation only.
Table 5.7.1-1: HSS data
Field
Description
IMSI
IMSI is the main reference key.
MSISDN
The basic MSISDN of the UE (Presence of MSISDN is optional).
IMEI / IMEISV
International Mobile Equipment Identity - Software Version Number
External Identifier List
External Identifier(s) used in the external network(s) to refer to the subscription. See TS 23.682 [74] for more information.
MME Identity
The Identity of the MME currently serving this UE.
MME Capabilities
Indicates the capabilities of the MME with respect to core functionality e.g. regional access restrictions.
MS PS Purged from EPS
Indicates that the EMM and ESM contexts of the UE are deleted from the MME.
ODB parameters
Indicates that the status of the operator determined barring
Access Restriction
Indicates the access restriction subscription information. It may include different values for HPLMN and roaming case. It includes separate settings for WB-E-UTRAN and NB-IoT. It includes restriction information on the use of NR as a secondary RAT for user plane connectivity, the use of Unlicensed Spectrum (in the form of LAA, or LWA/LWIP, or NR-U).
EPS Subscribed Charging Characteristics
The charging characteristics for the UE, e.g. normal, prepaid, flat-rate, and/or hot billing subscription.
Trace Reference
Identifies a record or a collection of records for a particular trace.
Trace Type
Indicates the type of trace, e.g. HSS trace, and/or MME/ Serving GW / PDN GW trace.
OMC Identity
Identifies the OMC that shall receive the trace record(s).
Subscribed-UE-AMBR
The Maximum Aggregated uplink and downlink MBRs to be shared across all Non-GBR bearers according to the subscription of the user.
APN-OI Replacement
Indicates the domain name to replace the APN OI when constructing the PDN GW FQDN upon which to perform a DNS resolution. This replacement applies for all the APNs in the subscriber's profile. See TS 23.003 [9] clause 9.1.2 for more information on the format of domain names that are allowed in this field.
RFSP Index
An index to specific RRM configuration in the E-UTRAN
Additional RRM Policy Index
An index to additional RRM configuration in the E-UTRAN
URRP-MME
UE Reachability Request Parameter indicating that UE activity notification from MME has been requested by the HSS.
CSG Subscription Data
The CSG Subscription Data is a list of CSG IDs per PLMN and for each CSG ID optionally an associated expiration date which indicates the point in time when the subscription to the CSG ID expires; an absent expiration date indicates unlimited subscription.
For a CSG ID that can be used to access specific PDNs via Local IP Access, the CSG ID entry includes the corresponding APN(s).
VPLMN LIPA Allowed
Specifies per PLMN whether the UE is allowed to use LIPA.
IAB-Operation Allowed
Indicates that the subscriber is allowed for IAB-operation
EPLMN list
Indicates the Equivalent PLMN list for the UE's registered PLMN.
Subscribed Periodic RAU/TAU Timer
Indicates a subscribed Periodic RAU/TAU Timer value
Extended idle mode DRX cycle length
Indicates a subscribed extended idle mode DRX cycle length value.
RAT specific Subscribed Paging Time Window
Indicates a Subscribed Paging Time Window value for the associated RAT, NB-IoT, WB-E-UTRAN or both.
MPS CS priority
Indicates that the UE is subscribed to the eMLPP or 1x RTT priority service in the CS domain.
UE-SRVCC- Capability
Indicates whether the UE is UTRAN/GERAN SRVCC capable or not.
MPS EPS priority
Indicates that the UE is subscribed to MPS in the EPS domain.
UE Usage Type
Indicates the usage characteristics of the UE for use with Dedicated Core Networks (see clause 4.3.25).
Group ID-list
List of the subscribed group(s) that the UE belongs to
Communication Patterns
Indicates per UE the Communication Patterns and their corresponding validity times as specified in TS 23.682 [74].The Communication Patterns are not provided to the SGSN.
Monitoring Event Information Data
Describes the monitoring event configuration information. See TS 23.682 [74] for more information.
PDN Connection Restriction
Indicates whether the establishment of the PDN connection is restricted for the UE.
Enhanced Coverage Restricted
Specify PLMN(s) with Enhanced Coverage restrictions.
Acknowledgements of downlink NAS data PDUs
Indicates whether acknowledgement of downlink NAS data PDUs for Control Plane CIoT EPS Optimisation is disabled for this UE (enabled by default).
Service Gap Time
Used to set the Service Gap timer for Service Gap Control (see clause 4.3.17.9).
Time Reference Information Distribution Indication
Indicates whether the UE is subscribed to receive time reference information in access stratum.
Each subscription profile contains one or more PDN subscription contexts:
Context Identifier
Index of the PDN subscription context (Note 8).
PDN Address
Indicates subscribed IP address(es).
PDN Type
Indicates the subscribed PDN Type (IPv4, IPv6, IPv4v6, Non-IP, Ethernet)
APN-OI Replacement
APN level APN-OI Replacement which has same role as UE level APN-OI Replacement but with higher priority than UE level APN-OI Replacement. This is an optional parameter. When available, it shall be used to construct the PDN GW FQDN instead of UE level APN-OI Replacement.
Access Point Name (APN)
A label according to DNS naming conventions describing the access point to the packet data network (or a wildcard) (NOTE 6).
Invoke SCEF Selection
Indicates whether this APN is used for establishing PDN connection to the SCEF
SCEF ID
Indicates the FQDN or IP address of the SCEF which is to be selected for this APN. It is required if "Invoke SCEF Selection" indicator is set.
SIPTO permissions
Indicates whether the traffic associated with this APN is prohibited for SIPTO, allowed for SIPTO excluding SIPTO at the local network, allowed for SIPTO including SIPTO at the local network or allowed for SIPTO at the local network only (NOTE 7).
LIPA permissions
Indicates whether the PDN can be accessed via Local IP Access. Possible values are: LIPA-prohibited, LIPA-only and LIPA-conditional.
WLAN offloadability
Indicates whether the traffic associated with this APN is allowed to be offloaded to WLAN using the WLAN/3GPP Radio Interworking feature or if it shall be kept on 3GPP access (see clause 4.3.23). The indication may contain separate values per RAT (E-UTRA and UTRA).
EPS subscribed QoS profile
The bearer level QoS parameter values for that APN's default bearer (QCI and ARP) (see clause 4.7.3).
Subscribed-APN-AMBR
The maximum aggregated uplink and downlink MBRs to be shared across all Non-GBR bearers, which are established for this APN.
EPS PDN Subscribed Charging Characteristics
The charging characteristics of this PDN Subscribed context for the UE, e.g. normal, prepaid, flat-rate, and/or hot billing subscription. The charging characteristics is associated with this APN.
VPLMN Address Allowed
Specifies per VPLMN whether for this APN the UE is allowed to use the PDN GW in the domain of the HPLMN only, or additionally the PDN GW in the domain of the VPLMN.
PDN GW identity
The identity of the PDN GW used for this APN. The PDN GW identity may be either an FQDN or an IP address. The PDN GW identity refers to a specific PDN GW.
PDN GW Allocation Type
Indicates whether the PDN GW is statically allocated or dynamically selected by other nodes. A statically allocated PDN GW is not changed during PDN GW selection.
PDN continuity at inter RAT mobility
Provides for this APN how to handle a PDN connection when UE the moves between "broadband" (WB-E-UTRAN and UTRAN) and "narrowband" (NB-IoT, GPRS, EC-GSM-IoT). Possible values are: maintain the PDN connection; disconnect the PDN connection with a reactivation request; disconnect PDN connection without reactivation request; or to leave it to local VPLMN policy.
PLMN of PDN GW
Identifies the PLMN in which the dynamically selected PDN GW is located.
Homogenous Support of IMS Voice over PS Sessions for MME
Indicates per UE and MME if "IMS Voice over PS Sessions" is homogeneously supported in all TAs in the serving MME or homogeneously not supported, or, support is non-homogeneous/unknown, see clause 4.3.5.8A.
List of APN ‑ PDN GW ID relations (for PDN subscription context with wildcard APN):
APN - P‑GW relation #n
The APN and the identity of the dynamically allocated PDN GW of a PDN connection that is authorised by the PDN subscription context with the wildcard APN. The PDN GW identity may be either an FQDN or an IP address. The PDN GW identity refers to a specific PDN GW.
Update Location Timestamp
The timestamp information is the timestamp that is included in the last Update Location Request message (see clause 4.13.9), or the time when the last Update Location Request is received by the HSS if the timestamp is absent from the Update Location Request message.
NOTE 1: IMEI and SVN are stored in HSS when the Automatic Device Detection feature is supported, see clause 15.5 of TS 23.060 [7].
NOTE 2: The 'EPS subscribed QoS profile' stored in HSS is complementary to the legacy 'GPRS subscribed QoS profile'.
NOTE 3: Void.
NOTE 4: How to indicate which of the PDN subscription contexts stored in the HSS is the default one for the UE is defined in stage 3.
NOTE 5: To help with the selection of a co-located or topologically appropriate PDN GW and Serving GW, the PDN GW identity shall be in the form of an FQDN.
NOTE 6: The "Access Point Name (APN)" field in the table above contains the APN-NI part of the APN.
NOTE 7: In this specification, the values "prohibited for SIPTO" and " allowed for SIPTO excluding SIPTO at the local network" correspond to the pre Rel‑12 values "prohibited for SIPTO" and "allowed for SIPTO". Actual coding of these values belongs to Stage 3 domain.
NOTE 8: There may be at most three default APNs for a given user. One default APN can belong to either of the three PDN types of "IPv4", "IPv6", or "IPv4v6", one default APN can belong to PDN type of "Non-IP" and another default APN can belong to PDN type of "Ethernet".
An expired CSG subscription should not be removed from the HSS subscription data before it is removed from the UE's Allowed CSG list or Operator CSG list. When a CSG subscription is cancelled it should be handled as an expired subscription in HSS subscription data to allow for removing it from UE's Allowed CSG list or Operator CSG list first.
One (and only one) of the PDN subscription contexts stored in the HSS may contain a wild card APN (see TS 23.003 [9]) in the Access Point Name field.
The PDN subscription context marked as the default one shall not contain a wild card APN.
The PDN subscription context with a wildcard APN shall not contain a statically allocated PDN GW.
If the LIPA permission and SIPTO permission flags are both included for a particular APN, they shall be set in a consistent manner, e.g. if the LIPA permission is set to LIPA-only or LIPA-conditional, the SIPTO permission shall be set to SIPTO-prohibited. Conversely, if the SIPTO permission indicates the APN is a SIPTO-allowed APN, the LIPA permission shall be set to LIPA-prohibited. A SIPTO-allowed APN is an APN for which the SIPTO permission is set to allowed for SIPTO excluding SIPTO at the local network, allowed for SIPTO including SIPTO at the local network or allowed for SIPTO at the local network only.
|
495b59b986f98d41912141cabbec196e
|
23.401
|
5.7.2 MME
|
The MME maintains MM context and EPS bearer context information for UEs in the ECM-IDLE, ECM‑CONNECTED and EMM-DEREGISTERED states. Table 5.7.2-1 shows the context fields for one UE.
Table 5.7.2-1: MME MM and EPS bearer Contexts
Field
Description
IMSI
IMSI (International Mobile Subscriber Identity) is the subscriber's permanent identity.
IMSI-unauthenticated-indicator
This is an IMSI indicator to show the IMSI is unauthenticated.
Alternative IMSI
The Alternative IMSI is derived from the Accepted IMSI Offset used for Paging Timing Collision Control.
RLOS-indicator
This is indication to show that the UE is RLOS attached.
MSISDN
The basic MSISDN of the UE. The presence is dictated by its storage in the HSS.
MM State
Mobility management state ECM-IDLE, ECM-CONNECTED, EMM-DEREGISTERED.
GUTI
Globally Unique Temporary Identity.
ME Identity
Mobile Equipment Identity – (e.g. IMEI/IMEISV) Software Version Number
Tracking Area List
Current Tracking area list
TAI of last TAU
TAI of the TA in which the last Tracking Area Update was initiated.
E-UTRAN Cell Global Identity
Last known E-UTRAN cell
E-UTRAN Cell Identity Age
Time elapsed since the last E-UTRAN Cell Global Identity was acquired
PS Cell Global Identity
Last known Primary Cell of Secondary Cell Group
PS Cell Age
Time elapsed since the last Primary Cell of Secondary Cell Group Identity was acquired
CSG ID
Last known CSG ID when the UE was active
CSG membership
Last known CSG membership of the UE when the UE was active
Access mode
Access mode of last known ECGI when the UE was active
Authentication Vector
Temporary authentication and key agreement data that enables an MME to engage in AKA with a particular user. An EPS Authentication Vector consists of four elements:
a) network challenge RAND,
b) an expected response XRES,
c) Key KASME,
d) a network authentication token AUTN.
UE Radio Access Capability
UE radio access capabilities including WB-E-UTRAN capabilities but not NB-IoT capabilities.
UE Radio Capability ID
If RACS is supported, uniquely identifies a set of UE radio access capabilities
LTE-M Indication
Indicates the UE is a LTE-M UE and the UE Radio Access Capability includes LTE Cat- M1 or LTE Cat-M1 and LTE Cat-M2. This is based on indication from the E-UTRAN provides.
NB-IoT specific UE Radio Access Capability
NB-IoT specific UE radio access capabilities.
MS Classmark 2
GERAN/UTRAN CS domain core network classmark (used if the MS supports SRVCC to GERAN or UTRAN).
MS Classmark 3
GERAN CS domain radio network classmark (used if the MS supports SRVCC to GERAN).
Supported Codecs
List of codecs supported in the CS domain (used if the MS supports SRVCC to GERAN or UTRAN).
UE Network Capability
UE network capabilities including security algorithms and other capabilities.
MS Network Capability
For a GERAN and/or UTRAN capable UE, this contains information needed by the SGSN.
UE Specific DRX Parameters
UE specific DRX parameters for A/Gb mode, Iu mode and WB-E-UTRAN S1‑mode.
UE Specific DRX Parameter for NB-IoT
UE Specific DRX Parameter for NB-IoT S1-mode.
Active Time value for PSM
UE specific Active Time value allocated by MME for power saving mode handling.
Extended idle mode DRX parameters
Negotiated extended idle mode DRX parameters for S1-mode.
RAT specific Subscribed Paging Time Window
Indicates a Subscribed Paging Time Window value for the associated RAT, NB-IoT, WB-E-UTRAN or both.
Selected NAS Algorithm
Selected NAS security algorithm
eKSI
Key Set Identifier for the main key KASME. Also indicates whether the UE is using security keys derived from UTRAN or E-UTRAN security association.
KASME
Main key for E-UTRAN key hierarchy based on CK, IK and Serving network identity
NAS Keys and COUNT
KNASint, K_NASenc, and NAS COUNT parameter.
Selected CN operator id
Selected core network operator identity (to support network sharing as defined in TS 23.251 [24]).
Recovery
Indicates if the HSS is performing database recovery.
Access Restriction
The access restriction subscription information. For this purpose, WB-E-UTRAN and NB-IoT are separate RATs. In addition, it includes restriction information on the use of NR as secondary RAT for user plane connectivity, the use of Unlicensed Spectrum (in the form of LAA, or LWA/LWIP, or NR-U).
Communication Patterns
Indicates per UE the Communication Patterns and their corresponding validity times as specified in TS 23.682 [74]. The Communication Patterns are not provided to the SGSN.
ODB for PS parameters
Indicates that the status of the operator determined barring for packet oriented services.
APN-OI Replacement
Indicates the domain name to replace the APN-OI when constructing the PDN GW FQDN upon which to perform a DNS resolution. This replacement applies for all the APNs in the subscriber's profile. See TS 23.003 [9] clause 9.1.2 for more information on the format of domain names that are allowed in this field.
MME IP address for S11
MME IP address for the S11 interface (used by S‑GW)
MME TEID for S11
MME Tunnel Endpoint Identifier for S11 interface.
S‑GW IP address for S11/S4
S‑GW IP address for the S11 and S4 interfaces
S‑GW TEID for S11/S4
S‑GW Tunnel Endpoint Identifier for the S11 and S4 interfaces.
SGSN IP address for S3
SGSN IP address for the S3 interface (used if ISR is activated for the GERAN and /or UTRAN capable UE)
SGSN TEID for S3
SGSN Tunnel Endpoint Identifier for S3 interface (used if ISR is activated for the E-UTRAN capable UE)
eNodeB Address in Use for S1-MME
The IP address of the eNodeB currently used for S1-MME.
eNodeB UE S1AP ID
Unique identity of the UE within eNodeB.
MME UE S1AP ID
Unique identity of the UE within MME.
Subscribed UE-AMBR
The Maximum Aggregated uplink and downlink MBR values to be shared across all Non-GBR bearers according to the subscription of the user.
UE-AMBR
The currently used Maximum Aggregated uplink and downlink MBR values to be shared across all Non-GBR bearers.
EPS Subscribed Charging Characteristics
The charging characteristics for the UE e.g. normal, prepaid, flat rate and/or hot billing.
Subscribed RFSP Index
An index to specific RRM configuration in the E-UTRAN that is received from the HSS.
Subscribed Additional RRM Policy Index
An index to additional RRM configuration in the E-UTRAN that is received from the HSS
RFSP Index in Use
An index to specific RRM configuration in the E-UTRAN that is currently in use.
Additional RRM Policy Index in Use
An index to additional RRM configuration in the E-UTRAN that is currently in use
Trace reference
Identifies a record or a collection of records for a particular trace.
Trace type
Indicates the type of trace
Trigger id
Identifies the entity that initiated the trace
OMC identity
Identifies the OMC that shall receive the trace record(s).
URRP-MME
URRP-MME indicating that the HSS has requested the MME to notify the HSS regarding UE reachability at the MME
DL Data Buffer Expiration Time
When extended buffering of DL data has been invoked for UEs that uses power saving functions e.g. PSM, this time is when the buffer will expire in the Serving GW.
Suggested number of buffered downlink packets
Suggested number of buffered downlink packets at extended buffering. This is an optional parameter.
CSG Subscription Data
The CSG Subscription Data is associated lists of CSG IDs for the visiting PLMN and the equivalent PLMNs to the visiting PLMN, and for each CSG ID optionally an associated expiration date which indicates the point in time when the subscription to the CSG ID expires; an absent expiration date indicates unlimited subscription.
For a CSG ID that can be used to access specific PDNs via Local IP Access, the CSG ID entry includes the corresponding APN(s).
LIPA Allowed
Specifies whether the UE is allowed to use LIPA in this PLMN.
IAB-Operation Allowed
Indicates that the subscriber is allowed for IAB-operation.
Subscribed Periodic RAU/TAU Timer
Indicates a subscribed Periodic RAU/TAU Timer value.
MPS CS priority
Indicates that the UE is subscribed to the eMLPP or 1x RTT priority service in the CS domain.
MPS EPS priority
Indicates that the UE is subscribed to MPS in the EPS domain.
Voice Support Match Indicator
An indication whether the UE radio capabilities are compatible with the network configuration (e.g. whether the SRVCC and frequency support by the UE matches those that the network relies upon for voice coverage). The MME uses it as an input for setting the IMS voice over PS Session Supported Indication.
Homogenous Support of IMS Voice over PS Sessions
Indicates per UE if "IMS Voice over PS Sessions" is homogeneously supported in all TAs in the serving MME or homogeneously not supported, or, support is non-homogeneous/unknown, see clause 4.3.5.8A.
UE Radio Capability for Paging Information - WB-E-UTRAN
Information used by the eNodeB to determine the timing of paging events and/or enhance the paging towards the UE (see clause 5.11.4). The UE Radio Capability for Paging Information is defined in TS 36.413 [36].
UE Radio Capability for Paging Information - NB-IoT
Information used by the eNodeB to determine the timing of paging events and/or enhance the paging towards the UE (see clause 5.11.4). The UE Radio Capability for Paging Information is defined in TS 36.413 [36].
Information On Recommended Cells And eNodeBs For Paging
Information sent by the eNodeB, and used by the MME when paging the UE to help determining the eNodeBs to be paged as well as to provide the information on recommended cells to each of these eNodeBs, in order to optimise the probability of successful paging while minimizing the signalling load on the radio path.
Paging Attempt Count
Information provided by the MME and used by the eNodeB to optimise signalling load and the use of network resources to successfully page a UE.
Information for Enhanced Coverage
Information for Enhanced Coverage level and cell ID provided by the last eNodeB the UE was connected to.
CE mode B Support Indicator
Indicates whether CE mode B is supported by the UE. The MME receives this from eNodeB (see TS 36.413 [36]).
Enhanced Coverage Restricted
Specifies whether the UE is restricted to use enhanced coverage feature or not.
CE mode B Restricted
Specifies whether the UE is restricted to use CE mode B (i.e. Coverage Extension mode B) or not.
UE Usage Type
Indicates the usage characteristics of the UE for use with Dedicated Core Networks (see clause 4.3.25).
Group ID-list
List of the subscribed group(s) that the UE belongs to
Monitoring Event Information Data
Describes the monitoring event configuration information. See TS 23.682 [74] for more information.
Delay Tolerant Connection
Indicates that the PDN connection is delay tolerant such that the PDN GW supports holding the procedure, after receiving a reject with a cause indicating that UE is temporarily not reachable due to power saving, until the PDN GW receives a message indicating that the UE is available for end to end signalling
PDN Connection Restriction
Indicates whether the establishment of the PDN connection is restricted for the UE.
Acknowledgements of downlink NAS data PDUs
Indicates whether acknowledgement of downlink NAS data PDUs for Control Plane CIoT EPS Optimisation is disabled for this UE (enabled by default).
Service Gap Time
Used to set the Service Gap timer for Service Gap Control (see clause 4.3.17.9).
Time Reference Information Distribution Indication
Indicates whether the UE is subscribed to receive time reference information in access stratum.
List of APN Rate Control Statuses
Indicates for each APN, the APN Rate Control Status (see clause 4.7.7.3).
WUS Assistance Information
Assistance information for determining the WUS group (see TS 36.300 [5]).
For each active PDN connection:
APN in Use
The APN currently used. This APN shall be composed of the APN Network Identifier and the default APN Operator Identifier, as specified in TS 23.003 [9], clause 9.1.2. Any received value in the APN OI Replacement field is not applied here.
APN Restriction
Denotes the restriction on the combination of types of APN for the APN associated with this EPS bearer Context.
APN Subscribed
The subscribed APN received from the HSS.
PDN Type
IPv4, IPv6, IPv4v6, Non-IP or Ethernet.
SCEF ID
The IP address of the SCEF currently being used for providing PDN connection to the SCEF.
IP Address(es)
IPv4 address and/or IPv6 prefix
NOTE: The MME might not have information on the allocated IPv4 address. Alternatively, following mobility involving a pre-release 8 SGSN, this IPv4 address might not be the one allocated to the UE.
Header Compression Configuration
ROHC configuration and context(s) for IP header compression for Control Plane CIoT EPS Optimisation.
EPS PDN Charging Characteristics
The charging characteristics of this PDN connection, e.g. normal, prepaid, flat-rate and/or hot billing.
APN-OI Replacement
APN level APN-OI Replacement which has same role as UE level APN-OI Replacement but with higher priority than UE level APN-OI Replacement. This is an optional parameter. When available, it shall be used to construct the PDN GW FQDN instead of UE level APN-OI Replacement.
SIPTO permissions
Indicates whether the traffic associated with this APN is prohibited for SIPTO, allowed for SIPTO excluding SIPTO at the local network, allowed for SIPTO including SIPTO at the local network or allowed for SIPTO at the local network only.
Local Home Network ID
If SIPTO@LN is enabled for this PDN connection it indicates the identity of the Local Home Network to which the (H)eNB belongs.
LIPA permissions
Indicates whether the PDN can be accessed via Local IP Access. Possible values are: LIPA-prohibited, LIPA-only and LIPA-conditional.
WLAN offloadability
Indicates whether the traffic associated with this PDN Connection is allowed to be offloaded to WLAN using the WLAN/3GPP Radio Interworking feature or if it shall be kept on 3GPP access (see clause 4.3.23). The indication may contain separate values per RAT (E-UTRA and UTRA).
VPLMN Address Allowed
Specifies whether the UE is allowed to use the APN in the domain of the HPLMN only, or additionally the APN in the domain of the VPLMN.
PDN GW Address in Use (control plane)
The IP address of the PDN GW currently used for sending control plane signalling.
PDN GW TEID for S5/S8 (control plane)
PDN GW Tunnel Endpoint Identifier for the S5/S8 interface for the control plane. (For GTP-based S5/S8 only).
MS Info Change Reporting Action
Need to communicate change in User Location Information to the PDN GW with this EPS bearer Context.
CSG Information Reporting Action
Need to communicate change in User CSG Information to the PDN GW with this EPS bearer Context.
This field denotes separately whether the MME/SGSN are requested to send changes in User CSG Information for (a) CSG cells, (b) hybrid cells in which the subscriber is a CSG member and (c) hybrid cells in which the subscriber is not a CSG member.
Presence Reporting Area Action
Need to communicate a change of UE presence in Presence Reporting Area. This field denotes separately the PRA identifier(s), and the list(s) of the Presence Reporting Area elements (if provided by the PDN GW). The status (i.e. active or inactive) for each Presence Reporting Area is stored in the MME when dynamic resource handling for Presence Reporting Area is configured in the MME.
EPS subscribed QoS profile
The bearer level QoS parameter values for that APN's default bearer (QCI and ARP) (see clause 4.7.3).
Subscribed APN-AMBR
The Maximum Aggregated uplink and downlink MBR values to be shared across all Non-GBR bearers, which are established for this APN, according to the subscription of the user.
APN-AMBR
The Maximum Aggregated uplink and downlink MBR values to be shared across all Non-GBR bearers, which are established for this APN, as decided by the PDN GW.
PDN GW GRE Key for uplink traffic (user plane)
PDN GW assigned GRE Key for the S5/S8 interface for the user plane for uplink traffic. (For PMIP-based S5/S8 only)
Default bearer
Identifies the EPS Bearer Id of the default bearer within the given PDN connection.
low access priority
Indicates that the UE requested low access priority when the PDN connection was opened.
NOTE: The low access priority indicator is only stored for the purpose to be included in charging records.
PDN continuity at inter RAT mobility
Provides for this APN how to handle a PDN connection when UE the moves between "broadband" (WB-E-UTRAN and UTRAN) and "narrowband" (NB-IoT, GPRS, EC-GSM-IoT). Possible values are: maintain the PDN connection; disconnect the PDN connection with a reactivation request; disconnect PDN connection without reactivation request; or to leave it to local VPLMN policy.
For each bearer within the PDN connection:
EPS Bearer ID
An EPS bearer identity uniquely identifies an EP S bearer for one UE accessing via E-UTRAN
TI
Transaction Identifier
S-GW IP address for S1-u/S11-u
IP address of the S‑GW for the S1-u interface. Also IP address of the S-GW for the S11-u interface if no separation of S1-U and S11-U is required. The S11-u interface is used for Control Plane CIoT EPS Optimisation.
S-GW IP address for S11-u
IP address of the S‑GW for the S11-u interfaces if S11-u is separated from S1-u. The S11-u interface is used for Control Plane CIoT EPS Optimisation.
S-GW TEID for S1-u/S11-u
Tunnel Endpoint Identifier of the S‑GW for the S1-u interface. Also Tunnel Endpoint Identifier of the S-GW for the S11-u interface if no separation of S1-U and S11-U is required. The S11-u interface is used for Control Plane CIoT EPS Optimisation.
S-GW TEID for S11-u
Tunnel Endpoint Identifier of the S‑GW for the S11-u interface if S11-u is separated from S1-u. The S11-u interface is used for Control Plane CIoT EPS Optimisation.
MME IP address for S11-u
MME IP address for the S11-u interface (Used by the S-GW). The S11-u interface is used for Control Plane CIoT EPS Optimisation.
MME TEID for S11-u
MME Tunnel Endpoint Identifier for the S11-u interface (Used by the S-GW). The S11-u interface is used for Control Plane CIoT EPS Optimisation.
PDN GW TEID for S5/S8 (user plane)
P‑GW Tunnel Endpoint Identifier for the S5/S8 interface for the user plane. (Used for S‑GW change only).
NOTE: The PDN GW TEID is needed in MME context as S‑GW relocation is triggered without interaction with the source S‑GW, e.g. when a TAU occurs. The Target S‑GW requires this Information Element, so it must be stored by the MME.
PDN GW IP address for S5/S8 (user plane)
P GW IP address for user plane for the S5/S8 interface for the user plane. (Used for S‑GW change only).
NOTE: The PDN GW IP address for user plane is needed in MME context as S‑GW relocation is triggered without interaction with the source S‑GW, e.g. when a TAU occurs. The Target S GW requires this Information Element, so it must be stored by the MME.
EPS bearer QoS
QCI and ARP
optionally: GBR and MBR for GBR bearer
TFT
Traffic Flow Template. (For PMIP-based S5/S8 only)
Serving PLMN-Rate-Control
The Serving PLMN-Rate-Control limits the maximum number of NAS Data PDUs per deci hour sent per direction (uplink/downlink) using the Control Plane CIoT EPS Optimisation for a PDN connection.
The MME Emergency Configuration Data is used instead of UE subscription data received from the HSS, for all emergency bearer services that are established by an MME on UE request.
Table 5.7.2-2: MME Emergency Configuration Data
Field
Description
Emergency Access Point Name (em APN)
A label according to DNS naming conventions describing the access point used for Emergency PDN connection (wild card not allowed).
Emergency QoS profile
The bearer level QoS parameter values for Emergency APN's default bearer (QCI and ARP). The ARP is an ARP value reserved for emergency bearers.
Emergency APN-AMBR
The Maximum Aggregated uplink and downlink MBR values to be shared across all Non-GBR bearers, which are established for the Emergency APN, as decided by the PDN GW.
Emergency PDN GW identity
The statically configured identity of the PDN GW used for emergency APN. The PDN GW identity may be either an FQDN or an IP address.
Non-3GPP HO Emergency PDN GW identity
The statically configured identity of the PDN GW used for emergency APN when a PLMN supports handover to non-3GPP access. The PDN GW identity may be either an FQDN or an IP address.(NOTE 1)
NOTE: The FQDN always resolves to one PDN GW.
NOTE 1: QCI for Emergency APN's default bearer is set per operator configuration.
The MME RLOS Configuration Data is used, for all RLOS PDN connection that are established by an MME on UE request instead of UE subscription data received from HSS.
Table 5.7.2-3: MME RLOS Configuration Data
Field
Description
Restricted Local Operator Services Access Point Name (RLOS APN)
A label according to DNS naming conventions describing the access point used for RLOS PDN connection (wild card not allowed).
RLOS QoS profile
The bearer level QoS parameter values for RLOS APN's default bearer (QCI and ARP).
RLOS APN-AMBR
The Maximum Aggregated uplink and downlink MBR values to be shared across all Non-GBR bearers, which are established for the RLOS APN, as decided by the PDN GW.
RLOS PDN GW identity
The statically configured identity of the PDN GW used for RLOS APN. The PDN GW identity may be either an FQDN or an IP address.
NOTE: The FQDN always resolves to one PDN GW.
NOTE 2: QCI and ARP for RLOS APN's default bearer is set per operator configuration.
|
495b59b986f98d41912141cabbec196e
|
23.401
|
5.7.3 Serving GW
|
The Serving GW maintains the following EPS bearer context information for UEs. Table 5.7.3-1 shows the context fields for one UE.
For emergency attached or RLOS attached UEs which are not authenticated, IMEI is stored in context.
Table 5.7.3-1: S‑GW EPS bearer context
Field
Description
E-UTRAN
UTRAN/
GERAN
IMSI
IMSI (International Mobile Subscriber Identity) is the subscriber permanent identity.
X
X
IMSI-unauthenticated-indicator
This is an IMSI indicator to show the IMSI is unauthenticated.
X
X
ME Identity
Mobile Equipment Identity (e.g. IMEI/IMEISV).
X
X
MSISDN
The basic MSISDN of the UE. The presence is dictated by its storage in the HSS.
X
X
Selected CN operator id
Selected core network operator identity (to support network sharing as defined in TS 23.251 [24]).
X
X
LTE-M Indication
Information used by the core network to differentiate traffic from category M UEs for charging purposes, where different values of M (e.g. M1, M2) are defined in TS 36.306 [82].
X
MME TEID for S11
MME Tunnel Endpoint Identifier for the S11 interface
X
MME IP address for S11
MME IP address the S11 interface.
X
S‑GW TEID for S11/S4 (control plane)
S‑GW Tunnel Endpoint Identifier for the S11 Interface and the S4 Interface (control plane).
X
X
S‑GW IP address for S11/S4 (control plane)
S‑GW IP address for the S11 interface and the S4 Interface (control plane).
X
X
SGSN IP address for S4 (control plane)
SGSN IP address for the S4 interface (Used by the S‑GW).
X
SGSN TEID for S4 (control plane)
SGSN Tunnel Endpoint Identifier for the S4 interface.
X
Trace reference
Identifies a record or a collection of records for a particular trace.
X
X
Trace type
Indicates the type of trace
X
X
Trigger id
Identifies the entity that initiated the trace
X
X
OMC identity
Identifies the OMC that shall receive the trace record(s).
X
X
Last known Cell Id
This is the last location of the UE known by the network
X
(NOTE 1)
X
(NOTE 1)
Last known Cell Id age
This is the age of the above UE location information
X
(NOTE 1)
X
(NOTE 1)
DL Data Buffer Expiration Time
The time until the Serving GW buffers DL data, when the MME has requested extended buffering in an DDN Ack (e.g. when a UE is in PSM).
X
X
Serving PLMN-Rate-Control
For inclusion on Serving GW CDR to allow post processing of CDRs and permit detection of abusive UEs.
X
For each PDN Connection:
NOTE: The following entries are repeated for each PDN.
APN in Use
The APN currently used, as received from the MME or S4 SGSN.
X
X
PDN Type
IPv4, IPv6, IPv4v6, Non-IP or Ethernet. (This information is needed by the SGW in order to determine whether to perform Paging Policy Differentiation).
X
EPS PDN Charging Characteristics
The charging characteristics of this PDN connection, e.g. normal, prepaid, flat-rate and/or hot billing.
X
X
P‑GW Address in Use (control plane)
The IP address of the P‑GW currently used for sending control plane signalling.
X
X
P‑GW TEID for S5/S8 (control plane)
P‑GW Tunnel Endpoint Identifier for the S5/S8 interface for the control plane. (For GTP-based S5/S8 only).
X
X
P‑GW Address in Use (user plane)
The IP address of the P‑GW currently used for sending user plane traffic. (For PMIP-based S5/S8 only)
X
X
P‑GW GRE Key for uplink traffic (user plane)
PDN GW assigned GRE Key for the S5/S8 interface for the user plane for uplink traffic. (For PMIP-based S5/S8 only)
X
X
S‑GW IP address for S5/S8 (control plane)
S‑GW IP address for the S5/S8 for the control plane signalling.
X
X
S‑GW TEID for S5/S8 (control plane)
S‑GW Tunnel Endpoint Identifier for the S5/S8 control plane interface. (For GTP-based S5/S8 only).
X
X
S‑GW Address in Use (user plane)
The IP address of the S‑GW currently used for sending user plane traffic. (For PMIP-based S5/S8 only)
X
X
S‑GW GRE Key for downlink traffic (user plane)
Serving GW assigned GRE Key for the S5/S8 interface for the user plane for downlink traffic. (For PMIP-based S5/S8 only)
X
X
Default Bearer
Identifies the default bearer within the PDN connection by its EPS Bearer Id. (For PMIP based S5/S8.)
X
X
For each EPS Bearer within the PDN Connection:
NOTE: The following entries defining the EPS Bearer specific parameters are included within the set of parameters defining the PDN Connection.
EPS Bearer Id
An EPS bearer identity uniquely identifies an EPS bearer for one UE accessing via E-UTRAN
X
X
TFT
Traffic Flow Template
X
X
P‑GW Address in Use (user plane)
The IP address of the P‑GW currently used for sending user plane traffic. (For GTP-based S5/S8 only).
X
X
P‑GW TEID for S5/S8 (user plane)
P‑GW Tunnel Endpoint Identifier for the S5/S8 interface for the user plane. (For GTP-based S5/S8 only).
X
X
S‑GW IP address for S5/S8 (user plane)
S‑GW IP address for user plane data received from PDN GW. (For GTP-based S5/S8 only).
X
X
S‑GW TEID for S5/S8 (user plane)
S‑GW Tunnel Endpoint Identifier for the S5/S8 interface for the user plane. (For GTP-based S5/S8 only).
X
X
S‑GW IP address for S1-u, S12, S4 (user plane) and S11-u
S‑GW IP address for the S1-u interface (used by the eNodeB), for the S12 interface (used by the RNC) and for the S4 interface (used by the SGSN). Also S‑GW IP address for the S11-u interface (used by the MME) if no separation of S1-U and S11-U is required. The S11-u interface is used for Control Plane CIoT EPS Optimisation.
X
X
S‑GW IP address for S11-u
S‑GW IP address for the S11-u interface (used by the MME). if S11-u is separated from S1-u. The S11-u interface is used for Control Plane CIoT EPS Optimisation.
X
S‑GW TEID for S1-u, S12, S4 (user plane) and S11-u
S‑GW Tunnel Endpoint Identifier for the S1-u interface, for the S12 interface (used by the RNC) and for the S4 interface (used by the SGSN). Also S‑GW Tunnel Endpoint Identifier for the S11-u interface (used by the MME) if no separation of S1-U and S11-U is required. The S11-u interface is used for Control Plane CIoT EPS Optimisation.
X
X
S‑GW TEID for S11-u
S‑GW Tunnel Endpoint Identifier for the S11-u interface (used by the MME) if S11-u is separated from S1-u. The S11-u interface is used for Control Plane CIoT EPS Optimisation.
X
MME IP address for S11-u
MME IP address for the S11-u interface (Used by the S-GW). The S11-u interface is used for Control Plane CIoT EPS Optimisation.
X
MME TEID for S11-u
MME Tunnel Endpoint Identifier for the S11-u interface (Used by the S-GW). The S11-u interface is used for Control Plane CIoT EPS Optimisation.
X
eNodeB IP address for S1-u
eNodeB IP address for the S1-u interface (Used by the S‑GW).
X
eNodeB TEID for S1-u
eNodeB Tunnel Endpoint Identifier for the S1-u interface.
X
RNC IP address for S12
RNC IP address for the S12 interface (Used by the S‑GW).
X
RNC TEID for S12
RNC Tunnel Endpoint Identifier for the S12 interface.
X
SGSN IP address for S4 (user plane)
SGSN IP address for the S4 interface (Used by the S‑GW).
X
SGSN TEID for S4 (user plane)
SGSN Tunnel Endpoint Identifier for the S4 interface.
X
EPS Bearer QoS
ARP, GBR, MBR, QCI.
X
X
Charging Id
Charging identifier, identifies charging records generated by S‑GW and PDN GW.
X
X
NOTE 1: The "Last Known Cell Id Age" is stored so that when UE location information is made available from both E-UTRAN and UTRAN/GERAN, the Serving GW can determine the "Last Known Cell Id".
|
495b59b986f98d41912141cabbec196e
|
23.401
|
5.7.4 PDN GW
|
The PDN GW maintains the following EPS bearer context information for UEs. Table 5.7.4-1 shows the context fields for one UE.
For emergency attached or RLOS attached UEs which are not authenticated, IMEI is stored in context.
Table 5.7.4-1: P‑GW context
Field
Description
E-UTRAN
UTRAN/
GERAN
IMSI
IMSI (International Mobile Subscriber Identity) is the subscriber permanent identity.
X
X
IMSI-unauthenticated-indicator
This is an IMSI indicator to show the IMSI is unauthenticated.
X
X
ME Identity
Mobile Equipment Identity (e.g. IMEI/IMEISV).
X
X
MSISDN
The basic MSISDN of the UE. The presence is dictated by its storage in the HSS.
X
X
Selected CN operator id
Selected core network operator identity (to support network sharing as defined in TS 23.251 [24]).
X
X
RAT type
Current RAT
X
X
LTE-M Indication
Information used by the core network to differentiate traffic from Category M UEs for charging purposes, where different values of M (e.g. M1, M2) are defined in TS 36.306 [82].
X
Trace reference
Identifies a record or a collection of records for a particular trace.
X
X
Trace type
Indicates the type of trace
X
X
Trigger id
Identifies the entity that initiated the trace
X
X
OMC identity
Identifies the OMC that shall receive the trace record(s).
X
X
For each APN in use:
NOTE: The following entries are repeated for each APN.
APN in use
The APN currently used, as received from the S-GW.
X
X
APN AMBR
The maximum aggregated uplink and downlink MBR values to be shared across all Non-GBR bearers, which are established for this APN.
X
X
APN Rate Control
The APN-Rate-Control limits the maximum number of uplink/downlink packets and the maximum number of additional exception report packets per a specific time unit (e.g. minute, hour, day, week) for this APN. It includes an indication as to whether or not Exception reports may still be sent when the limit has been met.
X
For each PDN Connection within the APN:
NOTE: The following entries are repeated for each PDN connection within the APN.
IP Address(es)
IPv4 address and/or IPv6 prefix.
X
X
PDN type
IPv4, IPv6, IPv4v6, Non-IP or Ethernet.
X
X
S‑GW Address in Use (control plane)
The IP address of the S‑GW currently used for sending control plane signalling.
X
X
S‑GW TEID for S5/S8 (control plane)
S‑GW Tunnel Endpoint Identifier for the S5/S8 interface for the control plane. (For GTP-based S5/S8 only).
X
X
S‑GW Address in Use (user plane)
The IP address of the S‑GW currently used for sending user plane traffic. (For PMIP-based S5/S8 only).
X
X
S‑GW GRE Key for downlink traffic (user plane)
Serving GW assigned GRE Key for the S5/S8 interface for the user plane for downlink traffic. (For PMIP-based S5/S8 only).
X
X
P‑GW IP address for S5/S8 (control plane)
P‑GW IP address for the S5/S8 for the control plane signalling.
X
X
P‑GW TEID for S5/S8 (control plane)
P‑GW Tunnel Endpoint Identifier for the S5/S8 control plane interface. (For GTP-based S5/S8 only).
X
X
P‑GW Address in Use (user plane)
The IP address of the P‑GW currently used for sending user plane traffic. (For PMIP-based S5/S8 only).
X
X
P‑GW GRE Key for uplink traffic (user plane)
PDN GW assigned GRE Key for the S5/S8 interface for the user plane for uplink traffic. (For PMIP-based S5/S8 only).
X
X
MS Info Change Reporting support indication
The MME and/or SGSN serving the UE support(s) procedures for reporting User Location Information and/or User CSG Information.
X
X
MS Info Change Reporting Action
Denotes whether the MME and/or the SGSN is/are requested to send changes in User Location Information change.
X
X
CSG Information Reporting Action
Denotes whether the MME and/or the SGSN is/are requested to send changes in User CSG Information change.
This field denotes separately whether the MME/SGSN are requested to send changes in User CSG Information for (a) CSG cells, (b) hybrid cells in which the subscriber is a CSG member, and (c) hybrid cells in which the subscriber is not a CSG member, or any combination of the above.
X
X
Presence Reporting Area Action
Denotes whether the MME and/or the SGSN is/are requested to send changes of UE presence in Presence Reporting Area.This field denotes separately the Presence Reporting Area identifier and the list of Presence Reporting Area elements.
X
X
BCM
The negotiated Bearer Control Mode for GERAN/UTRAN.
X
Default Bearer
Identifies the default bearer within the PDN connection by its EPS Bearer Id. The default bearer is the one which is established first within the PDN connection. (For GTP based S5/S8 or for PMIP based S5/S8 if multiple PDN connections to the same APN are supported).
X
X
EPS PDN Charging Characteristics
The charging characteristics of this PDN connection e.g. normal, prepaid, flat-rate and/or hot billing.
Serving PLMN-Rate-Control
The Serving PLMN-Rate-Control limits the maximum number of uplink/downlink messages per a specific time unit (e.g. minute, hour, day, week) for a PDN connection.
X
3GPP PS Data Off Status
Current 3GPP PS Data Off status of the UE.
For each EPS Bearer within the PDN Connection:
NOTE 1: The following entries defining the EPS Bearer specific parameters are included within the set of parameters defining the PDN Connection.
NOTE 2: The following entries are stored only for GTP-based S5/S8.
EPS Bearer Id
An EPS bearer identity uniquely identifies an EPS bearer for one UE accessing via E-UTRAN
X
X
TFT
Traffic Flow Template
X
X
S‑GW Address in Use (user plane)
The IP address of the S‑GW currently used for sending user plane traffic.
X
X
S‑GW TEID for S5/S8 (user plane)
S‑GW Tunnel Endpoint Identifier for the S5/S8 interface for the user plane.
X
X
P‑GW IP address for S5/S8 (user plane)
P‑GW IP address for user plane data received from PDN GW.
X
X
P‑GW TEID for S5/S8 (user plane)
P‑GW Tunnel Endpoint Identifier for the GTP Based S5/S8 interface for user plane.
X
X
EPS Bearer QoS
ARP, GBR, MBR, QCI.
X
X
Charging Id
Charging identifier, identifies charging records generated by S‑GW and PDN GW.
X
X
|
495b59b986f98d41912141cabbec196e
|
23.401
|
5.7.5 UE
|
The UE maintains the following context information. Table 5.7.5-1 shows the context fields. A GERAN or UTRAN capable UE maintains in addition the context information as described in a similar UE context table in TS 23.060 [7].
Table 5.7.5-1: UE context
Field
Description
IMSI
IMSI (International Mobile Subscriber Identity) is the subscriber's permanent identity.
EMM State
Mobility management state EMM-REGISTERED, EMM-DEREGISTERED.
GUTI
Globally Unique Temporary Identity.
ME Identity
Mobile Equipment Identity – (e.g. IMEI/IMEISV) Software Version Number.
Tracking Area List
Current Tracking area list.
last visited TAI
A TAI which is contained in the TA list the UE registered to the network and which identifies the tracking area last visited by the UE.
Selected NAS Algorithm
Selected NAS security algorithm.
Selected AS Algorithm
Selected AS security algorithms.
eKSI
Key Set Identifier for the main key KASME. Also indicates whether the UE is using security keys derived from UTRAN or E-UTRAN security association
KASME
Main key for E-UTRAN key hierarchy based on CK, IK and Serving network identity.
NAS Keys and COUNT
KNASint, KNASenc, and NAS COUNT parameter.
Temporary Identity used in Next update (TIN)
This parameter is used internally by the UE to memorise which temporary ID it has to indicate in the Attach Request and RAU/TAU Request as specified in clause 4.3.5.6.
UE Specific DRX Parameters
Preferred E-UTRAN DRX cycle length
Active Time value for PSM
UE specific Active Time value allocated by MME for power saving mode handling.
Extended idle mode DRX parameters
Extended idle mode DRX parameters received from the MME.
Allowed CSG list
The Allowed CSG list, which is under both user and operator control, indicates the list of CSG IDs and the associated PLMN where the UE is a member.
Operator CSG list
The Operator CSG list, which is under exclusive Operator control, indicates the list of CSG IDs and the associated PLMN where the UE is a member.
Service Gap Time
Used to set the Service Gap timer for Service Gap Control (see clause 4.3.17.9).
For each active PDN connection:
APN in Use
The APN currently used. This APN shall be composed of the APN Network Identifier and the default APN Operator Identifier, as specified in TS 23.003 [9], clause 9.1.2.
APN AMBR
The maximum aggregated uplink and downlink MBR to be shared across all Non-GBR bearers, which are established for this APN.
Assigned PDN Type
The PDN Type assigned by the network (IPv4, IPv6, IPv4v6, Non-IP or Ethernet).
IP Address(es)
IPv4 address and/or IPv6 prefix
Header Compression Configuration
ROHC configuration and context(s) for IP header compression for Control Plane CIoT EPS Optimisation.
Default Bearer
Identifies the default bearer within the PDN connection by its EPS Bearer Id. The default bearer is the one which is established first within the PDN connection.
WLAN offloadability
Indicates whether the traffic associated with this PDN Connection is allowed to be offloaded to WLAN using the WLAN/3GPP Radio Interworking feature or if it shall be kept on 3GPP access (see clause 4.3.23). The indication may contain separate values per RAT (E-UTRA and UTRA).
APN Rate Control
The APN-Rate-Control limits the maximum number of uplink packets and the maximum number of additional exception report packets per a specific time unit (e.g. minute, hour, day, week) for this APN. It includes an indication as to whether or not Exception reports may still be sent when the limit has been met.
Serving PLMN-Rate-Control
The Serving PLMN-Rate-Control limits the maximum number of NAS Data PDUs per deci hour sent uplink using the Control Plane CIoT EPS Optimisation for a PDN connection.
For each EPS Bearer within the PDN connection
EPS Bearer ID
An EPS bearer identity uniquely identifies an EPS bearer for one UE accessing via E-UTRAN.
TI
Transaction Identifier
EPS bearer QoS
GBR and MBR for GBR bearer.
TFT
Traffic Flow Template.
|
495b59b986f98d41912141cabbec196e
|
23.401
|
5.7.6 Handling of Wild Card APN
|
When the wild card APN is present in the subscription context, the UE is authorized to connect to APNs which are not present in the subscription context.
When a request is received for registering a PDN GW ID and there is no PDN subscription context with this APN, the nodes (HSS/MME/ S4 SGSN) shall store the PDN GW ID - APN relation for the UE.
When a request is received for deregistering of PDN GW ID and there is no PDN subscription context with this APN, the nodes (HSS/MME/S4 SGSN) shall delete the PDN GW ID - APN relation from the list of APN - PDN GW ID relations.
|
495b59b986f98d41912141cabbec196e
|
23.401
|
5.7.7 CSS
|
Please refer to TS 23.008 [28] for the content of the information storage for the CSS.
5.7A Charging
5.7A.1 General
Accounting functionality is provided by the Serving GW and the PDN GW. When a Secondary RAT may be used, the Serving GW and PDN GW can be assisted by the E-UTRAN (see clause 5.7A.4).
The Serving GW shall be able to collect and report for each UE accounting information, i.e. the amount of data transmitted in uplink and downlink direction categorized with the QCI and ARP pair per UE per PDN connection. For GTP-based S5/S8 the accounting information is collected and reported per bearer.
The Serving GW shall not collect UE accounting information for packets that are being processed for the sole purpose of indirect forwarding.
The Serving GW for inter-operator charging, and the PDN GW shall be able to interface the OFCS according to charging principles and through reference points specified in TS 32.240 [51].
The PDN GW shall be able to provide charging functionality for each UE according to TS 23.203 [6]. The PDN GW data collection for charging and usage monitoring purposes can be temporarily paused as described in clause 5.3.6A.
A PDN GW without a Gx interface shall be able to support flow based online and offline charging based on local configuration and interaction with the Online and Offline Charging Systems.
The Online Charging System may provide a PRA identifier(s) to the PDN GW to subscribe to notifications about changes of UE presence in Presence Reporting Area as defined in the TS 23.203 [6]. For UE-dedicated Presence Reporting Areas the Online Charging System also provides the list(s) of the elements comprising each subscribed UE-dedicated Presence Reporting Area.
The PDN GW shall be able to collect and report, for each UE, accounting information, i.e. the amount of data received and transmitted in uplink and downlink direction categorized with the QCI and ARP pair per UE per PDN connection. For GTP-based S5/S8 the accounting information is collected and reported per bearer. The PDN GW data collection can be temporarily paused as described in clause 5.3.6A based on operator configuration in the PDN GW.
NOTE: A consequence of pausing the PDN GW data collection is that PDN GW accounting information may not correspond to the volume that traversed the PDN GW and it is therefore not possible to verify accounting information collected at the Serving GW for inter-operator charging.
The Charging identifier(s) generated by the PDN GW per bearer for GTP-based S5/S8 and per PDN connection for PMIP-based S5/S8 and the PDN GW address for control signalling enables the correlation of the reporting from a Serving GW and a PDN GW. The Charging identifier is uniquely assigned within the PDN GW.
The PDN GW receives Charging Characteristics from the Serving GW through GTP-S5/S8, or through PMIP for PMIP-based S5/S8. The handling of the Charging Characteristics in the P‑GW is defined in TS 32.251 [44].
To enable CSG charging function for a subscriber consuming network services via a CSG cell or a hybrid cell, User CSG Information is transferred to the PDN GW as indicated by CSG Information Reporting Action. User CSG Information includes CSG ID, access mode and CSG membership indication. CSG membership indication of whether the UE is a member of the CSG is included if the access mode is hybrid.
The valid CSG information shall be available in the serving GW and PDN GW in connected mode.
The PCRF shall, if deployed, provide User CSG Information reporting rules to the PDN GW at Attach and PDN Connectivity Request. PDN GW sets the CSG Information Reporting Action IE according to the User CSG Information reporting rules and sends it to Serving GW and MME.
To enable the MME to signal the correct RAT Type (NB-IoT or WB-E-UTRAN) to the SGW and PDN GW for accounting information generation purposes, the eNodeB informs the MME of the RAT Type and TAC associated with each cell in the S1 SETUP REQUEST and eNodeB CONFIGURATION UPDATE messages (TS 36.413 [36]). If the eNodeB signals WB-EUTRAN and the UE is of Category M from the UE's radio capability, the MME reports RAT Type LTE-M to the SGW. See clause 5.11.5 for more details.
5.7A.2 Usage Data Reporting for Secondary RAT
When a Secondary RAT can be used in conjunction with E-UTRAN, the HPLMN or VPLMN operator may wish to record the data volume sent on the Secondary RAT.
In order to reduce the complexity of this procedure, and to align with existing per EPS bearer accounting procedures, the following principles are used in this release:
a) The PLMN locally activates the Secondary RAT Usage Data Reporting by E-UTRAN O&M. The activation can happen separately for Data Volume Reporting of NR and Unlicensed Spectrum. If the PLMN uses this feature, it should ensure that this functionality is supported by all eNodeBs that support NR, Unlicensed Spectrum aggregation (if used to record data volume sent over unlicensed spectrum) as a Secondary RAT.
b) The E-UTRAN reports uplink and downlink data volumes to the EPC for the Secondary RAT on a per EPS bearer basis and per time interval.
NOTE 1: Secondary RAT includes access type NR and usage data reporting for Secondary RAT includes reporting of the combination of NR usage as defined in TS 37.340 [85].
c) At X2 handover and S1 handover, the source eNodeB reports the data volumes to the EPC. The reported data volume excludes data forwarded to the target RAN node.
d) At S1 Release, Connection Suspend, and EPS Bearer Deactivation the eNodeB reports the data volumes to the EPC.
e) To assist "partial CDR" generation at the Serving GW and the PDN GW, E-UTRAN O&M can instruct the E-UTRAN to also make periodic reports if no event has triggered a report before the period expires.
NOTE 2: The timing of these periodic E-UTRAN reports is not expected to align with the timing of partial CDR generation. Hence the frequency of E-UTRAN reports might be greater than that of partial CDR generation.
NOTE 3: RAN needs to be able to partition the measurements in a report to indicate usage that occurred before and after an absolute time. An example of the absolute time is that RAN is configured to partition data usage reports that occurred before and after midnight.
f) As an option, the Serving Gateway sends the data volume reports on to PDN GWs identified in bilateral roaming agreements.
5.7A.3 Secondary RAT Usage Data Reporting Procedure
The procedure in Figure 5.7A.3-1 may be used to report Secondary RAT usage data from eNodeB to the MME. It is executed by the eNodeB to report the Secondary RAT usage data information which is then included in messages on S11 towards Serving GW and S5/S8 interface to the PGW (e.g. during I-RAT handover procedures, S1 handover, X2 handover). This then further uses existing EPC signalling of the procedures involved.
The procedure in Figure 5.7A.3-2 may be used to report the Secondary RAT usage data from MME to the Serving GW. Optionally, it is used to report the Secondary RAT usage data from Serving GW to the PDN GW when the reporting to PDN GW is activated.
If the Secondary RAT usage data is provided by an S1AP message from eNodeB to MME other than the one indicated in Figure 5.7A.3-1, the procedures in clause 5.7A.3-2 may be used to transfer the secondary RAT usage data to the Serving GW and PDN GW (e.g. during S1 Release procedure). The eNodeB may also provide the user location information, e.g. ECGI, PSCell ID.
During IRAT handovers, the procedures 5.7A.3-1 to 5.7A.3-2 in its entirety is executed to provide reporting of Secondary RAT usage data to the Serving GW and to the PDN GW if PGW secondary RAT usage data reporting is active.
Handover related signalling of IRAT procedures may be used to provide reporting of Secondary RAT usage data to the Serving GW instead of the signalling of figure 5.7A.3-2, when PGW secondary RAT usage data reporting is not active.
Figure 5.7A.3-1: RAN Secondary RAT usage data Reporting procedure
1. The eNodeB, if it supports Dual Connectivity with Secondary RAT (using NR radio (see clause 4.3.2a on Support for Dual Connectivity), using unlicensed spectrum in the form of LAA/LWA/LWIP/NR-U (see clause 4.3.30)) and it is configured to report Secondary RAT usage data for the UE, depending on certain conditions documented in this specification, it shall send a RAN usage data Report message to the MME including the Secondary RAT usage data for the UE. The eNodeB will send only one RAN usage report for a UE when the UE is subject to handover by RAN. The RAN usage data report includes a handover flag to indicate when the message is sent triggered by X2-handover.
If Dual Connectivity is active or had been activated by that eNodeB, the eNodeB shall add the PSCell ID (and the time elapsed since the Dual Connectivity was released if Dual Connectivity is no longer activated) to the RAT usage data Report message.
In the case of X2 handover, the MME is expected to handle a secondary RAT data reporting received from the source eNodeB within a short time after Path Switch Request by forwarding it to the SGW, e.g. using the GW Secondary RAT usage data Reporting procedure.
Figure 5.7A.3-2: GW Secondary RAT usage data Reporting procedure
The eNodeB, if it supports Dual Connectivity with Secondary RAT (using NR radio (see clause 4.3.2a on Support for Dual Connectivity), using unlicensed spectrum in the form of LAA/LWA/LWIP/NR-U (see clause 4.3.30)) and it is configured to report Secondary RAT usage data for the UE, it shall send include the Secondary RAT usage data for the UE to the MME in certain messages depending on certain conditions documented elsewhere in this TS.
Secondary RAT usage reporting from the eNodeB is provided using S1 signalling message which are either at the UE level (eg. Path Switch Request, etc), or at bearer level (eg. E-RAB modification indication, Deactivate bearer response, etc.) as captured in relevant clauses in this specification. If Secondary RAT usage report is provided in bearer level signalling message by the eNodeB, the Secondary RAT usage report is related only to the specific bearer.
1. The MME forwards the Secondary RAT usage data and User Location Information, PSCell ID to the SGW in a Change Notification Request (Secondary RAT usage data) message. If the SGW is requested to forward Secondary RAT usage data to the PGW, the MME includes a flag causing the SGW to forward this to the PGW. Also, the MME informs the Serving GW if the secondary RAT usage data shall not be processed by the Serving GW (e.g. during Serving GW relocation when the usage data is to be forwarded via the target Serving GW).
2. The Serving GW may, based on flags received in the previous message and local configuration in the Serving GW, send the Change Notification (Secondary RAT usage data) message to the PDN GW.
3. The PDN GW acknowledges receiving the Secondary RAT usage data for the UE by a Change Notification Ack() message to the Serving GW.
4. The SGW acknowledges by sending a Change Notification ack() message back to the MME.
5.7A.4 Secondary RAT Periodic Usage Data Reporting Procedure
Periodic reporting of the Secondary RAT usage data is an optional function. When eNodeB, as defined in bullet e) of clause 5.7A.2, is configured with a "time interval for Secondary RAT usage data reporting", the eNodeB shall send a RAN Usage Data Report message for periodic reporting purposes to the MME only when this timer expires for a UE for which Secondary RAT usage data reporting is ongoing. The timer runs from the last usage reporting for the UE. The MME also indicates to SGW if secondary RAT usage data reporting to the PGW is active.
The procedures 5.7A.3-1 to 5.7A.3-2 in its entirety is executed to provide periodic reporting of Secondary RAT usage data to the Serving GW and to the PDN GW when PGW secondary RAT usage data reporting is active. At use for periodic usage data reporting, the procedure 5.7A.3-1 uses signalling from eNodeB which does not include a handover flag.
|
495b59b986f98d41912141cabbec196e
|
23.401
|
5.8 MBMS
|
MBMS is a point-to-multipoint service in which data is transmitted from a single source entity to multiple recipients. Transmitting the same data to multiple recipients allows network resources to be shared.
Support of MBMS for EPS is defined in TS 23.246 [13].
|
495b59b986f98d41912141cabbec196e
|
23.401
|
5.9 Interactions with other services
| |
495b59b986f98d41912141cabbec196e
|
23.401
|
5.9.1 Location Reporting Procedure
|
This procedure is used by an MME to request the eNodeB to report where the UE is currently located when the target UE is in ECM-CONNECTED state. The need for the eNodeB to continue reporting ceases when the UE transitions to ECM-IDLE. This procedure may be used for services that require accurate cell identification (e.g. for emergency services, lawful intercept, charging). When Dual Connectivity is activated, the PSCell information is only reported if requested by the MME. In the case of satellite access for Cellular IoT, this procedure may be used by the MME to determine the TAI where the UE is geographically located.
Figure 5.9.1-1: Location Reporting Procedure
1) The MME sends a Location Reporting Control message to the eNodeB. The Location Reporting Control message shall identify the UE for which reports are requested, the requested location information and may contain information such as reporting type. Requested location information is TAI+EGCI, and if requested by the MME, PSCell ID.
Reporting type indicates whether the message is intended to trigger:
- a single stand‑alone report about the current Cell ID serving the UE; or
- start the eNodeB to report whenever the UE changes cell.
In addition, the MME shall be able to control whether or not the RAN reports changes in the UE's PSCell ID.
NOTE 1: Requesting reports whenever the UE changes cell can increase signalling load on multiple interfaces. Requesting reports for changes in PSCell ID can further increase signalling load. Hence it is recommended that any such reporting is only applied for a limited number of subscribers.
2) The eNodeB sends a Location Report message informing the MME about the location of the UE which shall include the requested location information.
If the MME requests UE location, in the case of satellite access for Cellular IoT, the eNodeB provides all broadcast TAIs to the MME as part of the ULI. The eNodeB also reports the TAI where the UE is geographically located if this TAI can be determined. The cell and TAI reporting by eNodeB refer to a fixed cell and fixed TA in which a UE is geographically located. As part of the User Location Information, eNodeB also reports one or more TACs for the Selected PLMN as described in TS 36.413 [36], but it is not guaranteed that the UE is always located in one of these TACs.
3) The MME can send a Cancel Location Reporting message to inform the eNodeB that it should terminate location reporting for a given UE. This message is needed only when the reporting was requested for a reporting period.
NOTE 2: Location reporting is transferred during X2 handover, although new control signalling is not transferred during an active handover.
|
495b59b986f98d41912141cabbec196e
|
23.401
|
5.9.2 Location Change Reporting Procedure
| |
495b59b986f98d41912141cabbec196e
|
23.401
|
5.9.2.1 General
|
The PDN GW may request for each PDN connection independently whether the MME shall report changes of ECGI/eNodeB ID/TAI (by using the "MS Info Change Reporting Action" parameter) and/or the UE entering/leaving a Presence Reporting Area (by using the "Presence Reporting Area Action" parameter) and/or whether the MME shall report changes of user CSG information (by using "CSG Information Reporting Action" parameter) to the PDN GW.
This reporting (any combination of "MS Info Change Reporting Action" and/or "Presence Reporting Area Action" and/or "CSG Information Reporting Action") may be controlled by the PDN GW at the following procedures:
- Attach,
- Tracking Area Update (when inducing a Modify Bearer procedure to the PDN GW),
- Inter-RAT Mobility to E-UTRAN (when inducing a Modify Bearer procedure to the PDN GW),
- Dedicated bearer activation,
- PDN GW initiated bearer modification with bearer QoS update,
- PDN GW initiated bearer modification without bearer QoS update,
- UE requested PDN connectivity,
- UE requested bearer resource modification.
The "Presence Reporting Area Action" and "Presence Reporting Area Information" parameters apply to all procedures listed above but, within this specification, their usage has only been described in the message flows related with the Attach and the UE requested PDN connectivity procedures.
The reporting of UE entering/leaving a Presence Reporting Area is further described in clause 5.9.2.2.
The PDN GW may also request the MME to stop any of the above mentioned types of reporting. The MME shall obey the last explicit instruction received from the PDN GW or source MME.
During both mobility management and session management procedures, the MME shall indicate to the PDN GW the support of reporting location changes (using the MS Info Change Reporting support indication):
- If ECGI/eNodeB ID/TAI information is permitted to be sent to the PDN GW according to MME operator's policy,
- If CSG information is permitted to be sent to the PDN GW according to MME operator's policy.
The MME may be configured to report ECGI/eNodeB ID/TAI changes only when one or more E-RAB(s) are established. Otherwise the MME shall report ECGI/eNodeB ID/TAI changes as soon as detected.
If the level of support changes during a mobility management procedure then the MME shall indicate the current level of support to the S-GW and shall in addition provide ECGI/eNodeB ID/TAI even if the PDN GW has not requested this information. This could for example happen during MME change when the level of support indicated by the old MME is not the same as in the new MME.
NOTE 1: The inclusion of ECGI/eNodeB ID/TAI will trigger a Modify Bearer Request message from S-GW to the PDN GW and therefore this will make sure that the new level of support reaches the PDN GW.
At change of Serving Node (MME/S4-SGSN), the old Serving Node provides the new serving node with "MS Info Change Reporting Action" as previously requested by the PDN GW. The new Serving Node takes the "MS Info Change Reporting Action" immediately into account with the exception that, at mobility between a S4-SGSN and a MME, the new MME (respectively S4-SGSN) does not take into account the "MS Info Change Reporting Action" received from the S4-SGSN (respectively MME) but assumes that no location information change reporting is requested for the target RAT. At a change of RAT type between EUTRAN and UTRAN or between EUTRAN and GERAN, if location information change reporting is required in the target RAT, the PDN GW shall request "MS Info Change Reporting Action" from the new Serving Node (MME or S4-SGSN). Upon inter-RAT mobility, if the target MME/S4-SGSN supports location information change reporting, the target MME/S4-SGSN shall include the User Location Information in the Create Session Request / Modify Bearer Request, regardless of whether location Information change reporting had been requested in the previous RAT by the PDN GW.
The PDN GWPDN GW shall not request the MME to report location changes if it has not received the indication for corresponding support from the MME.
NOTE 2: For E-UTRAN access, homogeneous support of reporting changes of UE presence in a Presence Reporting Area in a network is assumed: When the PCRF configuration indicates that reporting changes of UE presence in a Presence Reporting Area is supported for E-UTRAN, this means it is supported by all the PDN GWPDN GW, all MME and all the SGW including the MME and SGW working in network sharing mode. If change of UE presence in Presence Reporting Area reporting is not supported, the PCRF may instead activate location information change reporting at cell, eNodeB or tracking area level.
The following procedure shall be used for location change reports to the PDN GWPDN GW where the report is not combined with other mobility management or session management signalling. The procedure shall only apply when the MME has been explicitly requested to report location changes.
The following procedure can be used for MO Exception Data Counter reporting where the report is not combined with other mobility management or session management signalling. The MME only includes the MO Exception data counter if the RRC establishment cause is set to "MO exception data" and the UE is accessing via the NB-IoT RAT. The MME maintains the MO Exception Data Counter for Serving PLMN Rate Control purposes (see clause 4.7.7.2). The MME may immediately send the MO Exception Data Counter to the Serving GW. Alternatively, in order to reduce signalling, the MME may send the MO Exception Data Counter to the Serving GW as described in TS 29.274 [43]. The SGW and PDN GWPDN GW indicate each use of this RRC establishment cause by the related counter on its CDR.
NOTE 3: Due to the increased signalling load, it is recommended that ECGI/eNodeB ID/TAI or CSG reporting is only applied for a limited number of subscribers.
Figure 5.9.2.1-1 represents the ECGI change triggering a report of change in ECGI, and/or the User CSG information change triggering a report of change in user CSG information. The figure also shows the reporting of a TAI change and/or when a UE enters or leaves a Presence Reporting Area.
Figure 5.9.2.1-1: Notification of the ECGI, TAI and/or user CSG information changes
1a. the MME has received an ECGI information Update from the eNodeB.
1b. The MME detects that the user CSG information has changed by comparing with the MME stored user CSG information, or
1c. The MME detects that the TAI of the UE has changed, or
1d. The MME detects that the UE has entered or left a Presence Reporting Area defined for this UE.
NOTE 4: It is possible that these changes are triggered at same time.
2. If the MME has been requested to report location changes to the PDN GWPDN GW for the UE (under the conditions specified in clause 5.9.2), the MME shall send the Change Notification message to the SGW indicating the new ECGI, TAI and/or user CSG information. The MME stores the notified user CSG information. If the MME has been requested to report a change of UE presence in Presence Reporting Area (under the conditions specified in clause 5.9.2), the MME shall send the Change Notification message including the Presence Reporting Area Information comprising the area identifier(s) and indication(s) on whether the UE is inside or outside the area(s). If MME decides to reactivate one or more of the inactive Presence Reporting Area(s), the Presence Reporting Area Information in this message also comprises the reactivated PRA identifier(s), and indication(s) on whether the UE is inside or outside the reactivated area(s).
3. The SGW forwards the Change Notification message to the PDN GWPDN GW. If dynamic PCC is deployed, and location changes need to be conveyed to the PCRF, then the PDN GWPDN GW shall send this information to the PCRF as defined in TS 23.203 [6]. If Presence Reporting Area Information has been received, the PDN GWPDN GW shall forward the Presence Reporting Area Information to the PCRF, to the OCS or to both as defined in TS 23.203 [6].
4. The PDN GW sends the Change Notification Ack to the SGW.
5. The SGW forwards the Change Notification Ack to the MME.
|
495b59b986f98d41912141cabbec196e
|
23.401
|
5.9.2.2 Reporting at Presence Reporting Area entering and leaving
|
In some use cases policy control/charging decisions, such as QoS modification or charging rate change depend on whether the UE is located inside or outside a specific area of interest (Presence Reporting Area), and especially on whether the UE enters or leaves that specific area of interest.
A Presence Reporting Area can be:
- Either a "UE-dedicated Presence Reporting Area", defined in the subscriber profile and composed of a short list of TAs/RAs, or eNodeBs and/or cells/SAs in a PLMN;
- Or a "Core Network predefined Presence Reporting Area", predefined in MME/SGSN and composed of a short list of TAs/RAs, or eNodeBs and/or cells/SAs in a PLMN.
NOTE 1: eNodeBs are identified via the Global eNodeB ID IE defined in TS 36.413 [36].
NOTE 2: Change of UE presence in Presence Reporting Area reporting does not apply to roaming.
The reporting of changes of UE presence in Presence Reporting Area is for a specific UE and is triggered as defined in TS 23.203 [6]. The PDN GW may request to Start/Stop reporting of changes of UE presence for one or more Presence Reporting Area(s) by using the Presence Reporting Area Action parameter. For UE-dedicated Presence Reporting Areas, the reporting request (Start) shall contain the PRA identifier(s) and the list(s) of TAs/RAs, or eNodeBs and/or cells/SAIs composing the Presence Reporting Area(s). For Core Network predefined Presence Reporting Areas, the reporting request (Start) shall contain the PRA identifier(s). The request to Stop a reporting contains the PRA identifier(s).
Each Core Network predefined Presence Reporting Area can be configured with a priority level in the MME/S4-SGSN. In order to prevent overload, the MME/S4-SGSN may set the reporting for one or more of the received Presence Reporting Area(s) to inactive under consideration of the priority configured for each of Core Network predefined Presence Reporting Area(s), while storing the reporting request for this Presence Reporting Area in the user context.
Upon reception of a request for change of UE presence in Presence Reporting Area reporting, the MME/S4-SGSN shall report to the PDN GW via the SGW the Presence Reporting Area Information comprising the PRA identifier(s) and indication(s) on whether the UE is inside or outside the Presence Reporting Area(s). If the UE is in ECM-IDLE state, the MME may either bring the UE into ECM-CONNECTED state, or, report based on the UE's last known location and when the UE was there. One or more Presence Reporting Area may be set for a given PDN connection at a time. The serving node if needed only sets the reporting of UE presence in a Presence Reporting Area to inactive when receiving the reporting request for this Presence Reporting Area. If the MME/S4-SGSN decides to set the reporting of UE presence in one or more of the received Presence Reporting Area(s) to inactive, the MME/S4-SGSN shall also report the inactive Presence Reporting Area(s).
The MME/S4-SGSN shall notify the PDN GW when the UE enters or leaves a Presence Reporting Area, and no notifications are sent for UE movements inside or outside a Presence Reporting Area. The report of the change of UE presence in Presence Reporting Area shall contain the Presence Reporting Area Information comprising the PRA identifier(s) and indication(s) on whether the UE is inside or outside the area(s). A report shall be sent if the UE presence is different to the last one reported.
The MME/S4-SGSN may be configured with a PRA identifier which refers to a Set of Core Network predefined Presence Reporting Areas. The PDN GW may request Start reporting for this Set of Presence Reporting Areas by only indicating this PRA identifier in the Presence Reporting Area Action. When the Presence Reporting Area(s) to be reported belong to a set of Core Network predefined Presence Reporting Areas in which the MME/S4-SGSN is requested to report on change of UE presence, the MME/S4-SGSN shall additionally add to the report the PRA identifier of the Set of Core Network predefined Presence Reporting Areas.
Upon change of serving EPC node (MME, S4-SGSN), the PRA identifier(s) and if provided by the PDN GW the list(s) of Presence Reporting Area elements are transferred for all PDN connections as part of MM Context information to the target serving node during the mobility procedure. If one or more Presence Reporting Area(s) was set to inactive, the target serving node may decide to reactivate one or more of the inactive Presence Reporting Area(s). The target serving node indicates per PDN connection to the corresponding PDN GW the PRA identifier(s) and whether the UE is inside or outside the Presence Reporting Area(s) as well as the inactive Presence Reporting Area(s), if any.
NOTE 3: The target serving node cannot set the Presence Reporting Area(s) received from the source serving node to inactive.
|
495b59b986f98d41912141cabbec196e
|
23.401
|
5.9.3 IMSI and APN information retrieval procedure
|
This procedure is used by the RCAF to determine the UEs that are served by a congested eNodeB or E-UTRAN cell and the APNs of the active PDN connections of these UEs. This information is used to determine the PCRFs serving these UEs and subsequently report RAN user-plane congestion information (RUCI) to the PCRFs. The decision whether the RCAF requests MME to retrieve the list of UEs on eNodeB or E-UTRAN cell level is up to operator configuration.
NOTE 1: The details of congestion reporting to the PCRF are specified in TS 23.203 [6].
The RCAF determines the MMEs that are serving the congested eNodeB or E-UTRAN cell based on the Tracking Area Identities served by the congested eNodeB or E-UTRAN cell. For further details on the related DNS procedure see TS 29.303 [61]. The following steps are applied to all MMEs serving the congested eNodeB or E-UTRAN cell.
NOTE 2: In network sharing scenarios the RCAF belongs to the RAN operator. In this case it is up to inter-operator agreements and operator configuration which sharing partner's MMEs the RCAF queries IMSI and APN information from.
Figure 5.9.3-1: IMSI and APN information retrieval procedure
1. The RCAF sends an IMSI/APN information request to the MME. The request shall identify whether the request refers to an eNodeB or an E-UTRAN cell and shall contain the related eNodeB ID or ECGI.
NOTE 3: The eNodeB ID is defined in TS 36.413 [36].
2. The MME sends the IMSI/APN information response to the RCAF. The response shall contain the list of UEs (identified by the IMSIs) served by the eNodeB or E-UTRAN cell and the list of APNs of the active PDN connections of each IMSI.
If the RCAF requested the IMSI/APN information on E-UTRAN cell level, then the MME first determines the list of UEs served by that E-UTRAN cell. The MME may achieve this by querying the eNodeB that the E-UTRAN cell belongs to for the exact ECGI for all UEs served by this eNodeB using the Location Reporting procedure (clause 5.9.1).
NOTE 4: Applying the Location Reporting feature due to an E-UTRAN cell level RCAF request can increase S1-MME interface signalling load.
NOTE 5: In order for RCAF to maintain the list of impacted UEs (identified by the IMSIs) (and related APN information) for a congested cell, the RCAF needs to regularly receive IMSI/APN information updates from the MME. The details of whether the RCAF needs to query the MME regularly or whether the MME updates the RCAF regularly without further explicit requests from the RCAF is specified in Stage 3.
|
495b59b986f98d41912141cabbec196e
|
23.401
|
5.10 Multiple-PDN support and PDN activation for UEs supporting "Attach without PDN connectivity"
| |
495b59b986f98d41912141cabbec196e
|
23.401
|
5.10.1 General
|
The EPS shall support simultaneous exchange of traffic to multiple PDNs through the use of separate PDN GWs or a single PDN GW. The usage of multiple PDNs is controlled by network policies and defined in the user subscription EPS Optimisation.
The EPS shall support UE-initiated connectivity establishment in order to allow multiple PDN connections to one or more PDNs. It shall be possible for a UE to initiate disconnection from any PDN.
All simultaneously active PDN connections of a UE that are associated with the same APN shall be provided by the same PDN‑GW.
UE support for multiple PDN connections is optional.
If the Control Plane CIoT EPS Optimisation is supported:
- a PDN connection of Non-IP PDN Type may also be served by an SCEF (see TS 23.682 [74]); multiple PDN connections of Non-IP PDN Type may be served by the same or multiple SCEFs; and
- the MME decides, based on APN Configuration information, whether a PDN connection is served by an SCEF or a PDN GW.
|
495b59b986f98d41912141cabbec196e
|
23.401
|
5.10.2 UE requested PDN connectivity
|
The UE requested PDN connectivity procedure for an E-UTRAN is depicted in figure 5.10.2-1. The procedure allows the UE to request for connectivity to an additional PDN over E-UTRAN including allocation of a default bearer, if the UE already has active PDN connections over E-UTRAN. This procedure may also be used when a UE has set "Attach without PDN Connectivity is supported" in the Preferred Network behaviour at attach time and the network has acknowledged its support to the UE. If so, the UE may remain attached without a Default PDN connection and, at any time, request a PDN connection to be established. This procedure is also used to request for connectivity to an additional PDN over E-UTRAN, if the UE is simultaneously connected to E-UTRAN and a non-3GPP access and the UE already has active PDN connections over both accesses. The PDN connectivity procedure may trigger one or multiple Dedicated Bearer Establishment procedures to establish dedicated EPS bearer(s) for that UE.
An emergency attached or RLOS attached UE shall not initiate any PDN Connectivity Request procedure. A normal attached UE shall request a PDN connection for emergency services when Emergency Service is required and an emergency PDN connection is not already active.
The UE supporting 15 EPS bearers as defined in clause 4.12 shall not initiate a UE requested PDN connectivity procedure if it has already 8 EPS bearers established and the UE has not received an Indication for support of 15 EPS bearers per UE or has received cause #65 "maximum number of EPS bearers reached".
Figure 5.10.2-1: UE requested PDN connectivity
NOTE 1: For a PMIP-based S5/S8, procedure steps (A) are defined in TS 23.402 [2]. Steps 3, 4, 5 and 13a/b concern GTP based S5/S8.
NOTE 2: The UE also uses this procedure to request re-establishment of existing PDN connectivity upon handover from non-3GPP accesses.
NOTE 3: The steps in (B) are executed only upon handover from non-3GPP access or if Presence Reporting Area Information is received from the MME.
NOTE 4: When using the Control Plane CIoT EPS Optimisation, steps 7 and 8 are modified and 9 and 10 are skipped.
1. The UE initiates the UE Requested PDN procedure by the transmission of a PDN Connectivity Request (APN, PDN Type, Protocol Configuration Options, Request Type, Header Compression Configuration) message. If the UE was in ECM-IDLE mode, this NAS message is preceded by the Service Request procedure if any of the exiting PDN connections were using the User Plane without CIoT EPS Optimisation, or, if the user plane was used just with User Plane CIoT EPS Optimisations, a Connection Resume Procedure is executed instead. PDN type indicates the requested IP version (IPv4, IPv4v6, IPv6, Non-IP, Ethernet).
The MME verifies that the APN provided by UE is allowed by subscription. If the APN provided by the UE is not allowed by subscription, based on operator policy, the MME may reject the request from the UE with an appropriate cause, or accept the request by replacing the UE requested APN with a network supported APN. The MME uses that network supported APN for the remainder of this procedure, except that the MME provides to the UE the same APN that the UE requested. If the UE did not provide an APN, the MME shall use the APN from the default PDN subscription context, and, use this APN for the remainder of this procedure.
Protocol Configuration Options (PCO) are used to transfer parameters between the UE and the Network and are sent transparently through the MME and the Serving GW. The Protocol Configuration Options may include the Address Allocation Preference, which indicates that the UE prefers to obtain an IPv4 address only after the default bearer activation by means of DHCPv4. If the UE has UTRAN or GERAN capabilities, it shall send the NRSU in the PCO to indicate the support of the network requested bearer control in UTRAN/GERAN. The UE sends the ETFTU in the PCO to indicate the support of the extended TFT filter format. The Request Type indicates "initial request" if the UE requests new additional PDN connectivity over the 3GPP access network for multiple PDN connections, the Request Type indicates "handover" when the UE is performing a handover from non-3GPP access and the UE has already established connectivity with the PDN over the non-3GPP access.
The UE shall indicate Request Type "Emergency" when it requests a PDN connection for emergency services.
If the message is being sent via a HeNB which has a collocated L-GW, it includes the L-GW address in the Uplink NAS transport message to the MME.
If a UE indicated Control Plane CIoT EPS Optimisation supported in Preferred Network Behaviour and supports header compression, it shall include the Header Compression Configuration, unless "Non-IP" or "Ethernet" PDN type is indicated. The Header Compression Configuration includes the information necessary for the ROHC channel setup. Optionally, the Header Compression Configuration may also include additional header compression context setup parameters, if the UE already has the application traffic information, e.g. the target server IP address.
The UE shall include in the PCO the 3GPP PS Data Off UE Status, which indicates whether the user has activated or deactivated 3GPP PS Data Off.
In the case of satellite access for Cellular IoT, the MME may verify the UE location as described in clause 4.13.4.
2. If the MME receives a PDN Connectivity Request from an emergency attached or RLOS attached UE or the PDN Connectivity Request is for normal services and the mobility or access restrictions do not allow the UE to access normal services the MME shall reject this request.
If the Request Type indicates "Emergency" and the MME is not configured to support PDN connections for emergency services the MME shall reject the PDN Connectivity Request with an appropriate reject cause.
If the Request Type is not set to "Emergency", and the UE has indicated support for Attach without PDN Connectivity, and the network supports Attach without PDN Connectivity, and the PDN Connection Restriction is set in the subscriber data, then the MME should reject the PDN Connectivity Request with an appropriate cause value.
If the Request Type indicates "Emergency", the MME derives a PDN GW from the MME Emergency Configuration Data or the MME selects a PDN GW as described in clause 4.3.12.4 on PDN GW Selection Function (3GPP accesses) according to the Emergency APN in the MME Emergency Configuration Data. This selection shall provide a PDN GW from visited PLMN only.
If the Request Type indicates "Emergency" and the MME is configured to support PDN connections for emergency services, it uses the MME Emergency Configuration Data for the bearer establishment in this step and ignores any subscription data limitation.
If the Request Type indicates "Handover", the MME uses the PDN GW stored in the Subscription Data retrieved by the MME during the Update Location performed at attach. If the Request Type indicates "initial request" the MME selects a PDN GW as described in clause 4.3.8.1 on PDN GW Selection Function (3GPP accesses).
If the UE provided APN is authorized for LIPA according to the user subscription, the MME shall use the CSG Subscription Data to authorize the connection.
If the subscription context does not indicate that the APN is for a PDN connection to an SCEF the MME allocates a Bearer Id, and sends a Create Session Request (IMSI, MSISDN, MME TEID for control plane, RAT type, LTE-M RAT type reporting to PGW flag, PDN GW address, PDN Address, Default EPS Bearer QoS, PDN Type, subscribed APN-AMBR, APN, EPS Bearer Id, Protocol Configuration Options, Handover Indication, ME Identity, User Location Information (ECGI and TAI), UE Time Zone, User CSG Information, MS Info Change Reporting support indication, Selection Mode, Charging Characteristics, Trace Reference, Trace Type, Trigger Id, OMC Identity, Maximum APN Restriction, Dual Address Bearer Flag) message to the Serving GW. If Control Plane CIoT EPS Optimisation applies, then the MME shall also indicate S11-U tunnelling of NAS user data and send its own S11-U IP address and MME DL TEID for DL data forwarding by the SGW.
If the MME determines the PDN connection shall only use the Control Plane CIoT EPS Optimisation, the MME shall include a Control Plane Only PDN Connection Indicator in Create Session Request.
For PDN type "non-IP", if the APN subscription data indicate a SCEF connection needs to be used, then the MME allocates an EPS Bearer Identity for the Default Bearer associated with the UE and established connection to the SCEF address indicated in subscription data according to TS 23.682 [74] and the steps 2,3,4,5,6 are not executed. The rest of the interactions with the UE apply as specified below.
The RAT type is provided in this message for the later PCC decision. The RAT type shall enable NB-IoT, LTE-M and WB-E-UTRAN to be differentiated by the PDN-GW The MSISDN is included if the MME has it stored for that UE. Handover Indication is included if the Request Type indicates "handover". Selection Mode indicates whether a subscribed APN was selected, or a non-subscribed APN sent by the UE was selected. The P‑GW may use Selection Mode when deciding whether to accept or reject the default bearer activation. For example, if an APN requires subscription, the P‑GW is configured to accept only the default bearer activation that requests a subscribed APN as indicated by Selection Mode. Charging Characteristics indicates which kind of charging the bearer context is liable for.
The charging characteristics for the PS subscription and individually subscribed APNs as well as the way of handling Charging Characteristics and whether to send them or not to the P‑GW is defined in TS 32.251 [44]. The MME shall include Trace Reference, Trace Type, Trigger Id, and OMC Identity if S‑GW and/or P‑GW trace is activated. The MME shall copy Trace Reference, Trace Type, and OMC Identity from the trace information received from the HLR or OMC.
The Maximum APN Restriction denotes the most stringent restriction as required by any already active bearer context. If there are no already active bearer contexts, this value is set to the least restrictive type (see clause 15.4 of TS 23.060 [7]). If the P‑GW receives the Maximum APN Restriction, then the P‑GW shall check if the Maximum APN Restriction value does not conflict with the APN Restriction value associated with this bearer context request. If there is no conflict the request shall be allowed, otherwise the request shall be rejected with sending an appropriate error cause to the UE.
If the PDN subscription context contains a subscribed IPv4 address and/or IPv6 prefix, the MME indicates it in the PDN address. The MME may change the requested PDN type according to the subscription data for this APN as described in clause 5.3.1.1. The MME shall set the Dual Address Bearer Flag when the PDN type is set to IPv4v6 and all SGSNs which the UE may be handed over to are Release 8 or above supporting dual addressing, which is determined based on node pre-configuration by the operator.
If there is an APN Rate Control Status in the MME MM Context for the UE, the MME forwards it to the SGW.
Based on UE and Serving GW capability of supporting MT-EDT, Communication Pattern parameters or local policy, the MME may indicate to Serving GW that MT-EDT is applicable for the PDN Connection.
3. The Serving GW creates a new entry in its EPS Bearer table and sends a Create Session Request (IMSI, MSISDN, Serving GW Address for the user plane, Serving GW TEID of the user plane, Serving GW TEID of the control plane, RAT type, Default EPS Bearer QoS, PDN Type, PDN Address, subscribed APN-AMBR, APN, Bearer Id, Protocol Configuration Options, Handover Indication, ME Identity, User Location Information (ECGI), UE Time Zone, User CSG Information, MS Info Change Reporting support indication, PDN Charging Pause Support indication, Selection Mode, Charging Characteristics, Trace Reference, Trace Type, Trigger Id, OMC Identity, Maximum APN Restriction, Dual Address Bearer Flag, APN Rate Control Status) message to the PDN GW indicated in the PDN GW address received in the previous step. After this step, the Serving GW buffers any downlink packets it may receive from the PDN GW until receives the message in step 13 below. The MSISDN is included if received from the MME. If the Handover Indication is included, the Serving GW includes it in the Create Session Request message.
If the Serving GW has received the Control Plane Only PDN Connection Indicator in step 2, the Serving GW informs the PDN GW this information in Create Session Request. The Serving GW and PDN GW shall indicate the use of CP only on their CDRs.
P-GWs shall not perform any checks of Maximum APN Restriction if Create Default Bearer Request includes emergency APN.
If the PDN GW detects that the 3GPP PS Data Off UE Status has changed, the PDN GW shall indicate this event to the charging system for offline and online charging.
4. If dynamic PCC is deployed and the Handover Indication is not present, the PDN GW may employ an IP‑CAN Session Establishment procedure as defined in TS 23.203 [6] with the PCRF to get the default PCC rules for the UE. This may lead to the establishment of a number of dedicated bearers following the procedures defined in clause 5.4.1 in association with the establishment of the default bearer which is described in Annex F.
The RAT type is provided to the PCRF by the PDN GW if received by the previous message. If the PDN GW/PCEF is configured to activate predefined PCC rules for the default bearer, the interaction with the PCRF is not required (e.g. operator may configure to do this) at the moment.
The ETFTU is provided to the PCRF by the PDN GW, if received in the PCO from the UE and the PDN GW supports the extended TFT filter format. If the PCRF decides that the PDN connection may use extended TFT filters, it shall return the ETFTN indicator to the PDN GW for inclusion in the protocol Configuration Options returned to the UE.
The PCRF may modify the APN-AMBR and the QoS parameters (QCI and ARP) associated with the default bearer in the response to the PDN GW as defined in TS 23.203 [6].
If the PCC is configured to support emergency services and dynamic PCC is deployed, the PCRF, based on the Emergency APN, sets the ARP of the PCC rules to a value that is reserved for emergency services and the authorization of dynamic PCC rules as described in TS 23.203 [6]. If dynamic PCC is not deployed, the PDN GW is configured to set the ARP to a value that is reserved for emergency services.
If dynamic PCC is deployed and the Handover Indication is present, the PDN GW executes a PCEF‑Initiated IP‑CAN Session Modification procedure with the PCRF as specified in TS 23.203 [6] to report the new IP‑CAN type. Depending on the active PCC rules, the establishment of dedicated bearer for the UE may be required. The establishment of those bearers shall take place in combination with the default bearer activation as described in Annex F. This procedure can continue without waiting for a PCRF response. If changes to the active PCC rules are required, the PCRF may provide them after the handover procedure is finished.
In both cases (Handover Indication is present or not), if dynamic PCC is not deployed, the PDN GW may apply local QoS policy. This may lead to the establishment of a number of dedicated bearers for the UE following the procedures defined in clause 5.4.1 in combination with the establishment of the default bearer, which is described in Annex F.
If the CSG information reporting triggers are received from the PCRF, the PDN GW should set the CSG Information Reporting Action IE accordingly.
If 3GPP PS Data Off status is received in the PCO from the UE and PDN GW supports 3GPP PS Data Off, the PDN GW shall provide the 3GPP PS Data Off status to the PCRF. If the PCRF supports 3GPP PS Data Off, it shall return 3GPP PS Data Off support to the PDN GW for inclusion in the PCO returned to the UE.
If the 3GPP PS Data Off UE Status indicates that 3GPP PS Data Off is activated for the UE, the PDN GW shall enforce the PCC rules for downlink traffic to be used when 3GPP PS Data Off is activated.
If received, the PDN GW may take the APN Rate Control Status into account when encoding the APN Rate Control parameters in Protocol Configuration Options and when enforcing the APN Rate Control as described in clause 4.7.7.3.
5. The P‑GW creates a new entry in its EPS bearer context table and generates a Charging Id for the Default Bearer. The new entry allows the P‑GW to route user plane PDUs between the S‑GW and the packet data network, and to start charging. The way the P‑GW handles Charging Characteristics that it may have received is defined in TS 32.251 [44].
The PDN GW returns a Create Session Response (PDN GW Address for the user plane, PDN GW TEID of the user plane, PDN GW TEID of the control plane, PDN Type, PDN Address, EPS Bearer Id, EPS Bearer QoS, Protocol Configuration Options, Charging Id, Prohibit Payload Compression, APN Restriction, Cause, MS Info Change Reporting Action (Start) (if the PDN GW decides to receive UE's location information during the session), CSG Information Reporting Action (Start) (if the PDN GW decides to receive UE's User CSG information during the session), Presence Reporting Area Action (if the PDN GW decides to receive notifications about a change of UE presence in Presence Reporting Area), PDN Charging Pause Enabled indication (if PDN GW has chosen to enable the function), APN-AMBR, Delay Tolerant Connection) message to the Serving GW. The PDN GW takes into account the received PDN type, the Dual Address Bearer Flag and the policies of operator when the PDN GW selects the PDN type to be used as follows. If the received PDN type is IPv4v6 and both IPv4 and IPv6 addressing are possible in the PDN but the Dual Address Bearer Flag is not set, or only single IP version addressing for this APN is possible in the PDN, the PDN GW selects a single IP version (either IPv4 or IPv6). If the received PDN type is IPv4 or IPv6, the PDN GW uses the PDN type if it is supported in the PDN, otherwise an appropriate error cause will be returned. The PDN GW allocates a PDN Address according to the selected PDN Type If the PDN GW has selected a PDN type different from the received PDN Type, the PDN GW indicates together with the PDN type IE a reason cause to the UE why the PDN type has been modified, as described in clause 5.3.1.1. PDN Address may contain an IPv4 address for IPv4 and/or an IPv6 prefix and an Interface Identifier. If the PDN has been configured by the operator so that the PDN addresses for the requested APN shall be allocated by usage of DHCPv4 only, or if the PDN GW allows the UE to use DHCPv4 for address allocation according to the Address Allocation Preference received from the UE, the PDN Address shall be set to 0.0.0.0, indicating that the IPv4 address shall be negotiated by the UE with after completion of the Default Bearer Activation procedure. For external PDN addressing for IPv6, the PDN GW obtains the IPv6 prefix from the external PDN using either RADIUS or Diameter client function. In the PDN Address field of the Create Session Response, the PDN GW includes the Interface Identifier and IPv6 prefix. The PDN GW sends Router Advertisement to the UE after default bearer establishment with the IPv6 prefix information for all cases. If the PDN address is contained in the Create Session Request, the PDN GW shall allocate the IPv4 address and/or IP6 prefix contained in the PDN address to the UE. If Handover Indication indicates "Handover", the PDN Address Information shall contain the same IP address the UE obtained during PDN connectivity establishment over the non-3GPP access. The PDN GW derives the BCM based on the NRSU and operator policy. The PDN GW derives whether the extended TFT filter format is to be used based on the ETFTU, ETFTN received from the PCRF and operator policy. Protocol Configuration Options contains the BCM, ETFTN as well as optional PDN parameters that the P‑GW may transfer to the UE. These optional PDN parameters may be requested by the UE, or may be sent unsolicited by the P‑GW. Protocol Configuration Options are sent transparently through the MME.
If the PDN type is Non-IP or Ethernet, the PDN-GW uses the APN and IMSI to determine what local actions to perform before answering the Serving GW.
The PDN GW includes a Delay Tolerant Connection indication if the PDN GW supports receiving a rejection cause from the SGW indicating that the UE is temporarily not reachable due to power saving, and holding mobile terminated procedures until the PDN GW receives a message indicating that the UE is available for end to end signalling.
When the Handover Indication is present, the PDN GW does not yet send downlink packets to the S‑GW; the downlink path is to be switched at step 13a.
If the PDN GW is an L-GW, it does not forward downlink packets to the S-GW. The packets will only be forwarded to the HeNB at step 10 via the direct user plane path for Local IP Access.
If the 3GPP PS Data Off UE Status was present in the Create Session Request PCO, and if the network supports 3GPP PS Data Off, the PDN GW shall include the 3GPP PS Data Off Support Indication in the Create Session Response PCO.
6. The Serving GW returns a Create Session Response (PDN Type, PDN Address, Serving GW address for User Plane, Serving GW TEID for User Plane, Serving GW TEID for control plane, EPS Bearer Id, EPS Bearer QoS, PDN GW address and TEID (GTP-based S5/S8) or GRE key (PMIP-based S5/S8) at the PDN GW for uplink traffic, Protocol Configuration Options, Prohibit Payload Compression, APN Restriction, Cause, MS Info Change Reporting Action (Start), CSG Information Reporting Action (Start), Presence Reporting Area Action, APN-AMBR, DTC) message to the MME. The DL TFT for PMIP-based S5/S8 is obtained from interaction between the Serving GW and the PCRF as described in clause 5.6.1 of TS 23.402 [2], when PCC is deployed; otherwise, the DL TFT IE is wildcarded, matching any downlink traffic. If the UE indicates the Request Type as "Handover", this message also serves as an indication to the MME that the S5/S8 bearer setup and update has been successful. At this step the GTP tunnel(s) over S5/S8 are established
If Control Plane CIoT EPS Optimisation applies, and if MME doesn't include Control Plane Only PDN Connection Indicator in the Create Session Request:
- If separation of S11-U from S1-U is required, the Serving GW shall include the Serving GW IP address and TEID for S11-U and additionally the Serving GW IP address and TEID for S1-U in the Create Session Response.
- Otherwise if separation of S11-U from S1-U is not required, the Serving GW includes the Serving GW IP address and TEID for S11-U in Create Session Response.
7. If an APN Restriction is received, then the MME shall store this value for the Bearer Context and the MME shall check this received value with the stored value for the Maximum APN Restriction to ensure there are no conflicts between values. If the consequence of this check results in the PDN connectivity being rejected, the MME shall initiate a Bearer Deactivation and return an appropriate error cause. If the PDN Connectivity Request is accepted, the MME shall determine a (new) value for the Maximum APN Restriction. If there is no previously stored value for Maximum APN Restriction, then the Maximum APN Restriction shall be set to the value of the received APN Restriction.
The P-GW shall ignore Maximum APN restriction if the request includes the Emergency APN.
For emergency service MME shall not deactivate bearer(s), if present, to maintain valid APN restriction combination.
If the MS Info Change Reporting Action (Start) and/or the CSG Information Reporting Action (Start) are received for this bearer context, then the MME shall store this for the bearer context and the MME shall report to that P-GW via the S-GW whenever a UE's Location Information and/or User CSG Information change occurs that meets the P-GW request, as described in clause 15.1.1a of TS 23.060 [7]. If Presence Reporting Area Action is received for this bearer context, the MME shall store this information for the bearer context and shall report to that P-GW via the S-GW whenever a change of UE presence in a Presence Reporting Area is detected, as described in clause 5.9.2.2.
The MME may need to modify the UE AMBR, which has been assigned to the eNodeB, based on the subscribed UE-AMBR and the updated set of APN-AMBRs in use. The principles to determine the UE-AMBR are described in clause 4.7.3.
The MME sends PDN Connectivity Accept Session Management Request (APN, PDN Type, PDN Address, EPS Bearer Id, Protocol Configuration Options, Header Compression Configuration, Control Plane Only Indicator) message to the UE. If the PDN connection uses the user plane over the radio, this message is contained in an S1_MME control message Bearer Setup Request (EPS Bearer QoS, UE-AMBR, PDN Connectivity Accept, S1-TEID) to the eNodeB. However, if Control Plane CIoT EPS Optimisation applies to the PDN connection, an S1-AP Downlink NAS transport message is used. The S1-AP Initial Context Setup Request message includes the TEID at the Serving GW used for user plane and the address of the Serving GW for user plane. If the PDN type is set to "Non-IP" the MME includes it in the S1-AP Initial Context Setup Request so that the eNodeB disables header compression. If the PDN type is set to "Ethernet" the MME includes it in the S1-AP Initial Context Setup Request so that any eNodeB header compression functionality can act appropriately. In addition, if the PDN connection is established for Local IP Access, the corresponding S1 Initial Context Setup Request message includes a Correlation ID for enabling the direct user plane path between the HeNB and the L-GW. If the PDN connection is established for SIPTO at the Local Network with L‑GW function collocated with the (H)eNB, the corresponding S1-AP Initial Context Setup Request includes a SIPTO Correlation ID for enabling the direct user plane path between the (H)eNB and the L-GW. LIPA and SIPTO do not apply to Control Plane CIoT EPS Optimisation.
NOTE 5: In this release of the 3GPP specification the Correlation ID and SIPTO Correlation ID is set equal to the user plane PDN GW TEID (GTP-based S5) or GRE key (PMIP-based S5) that the MME has received in step 6.
In the PDN Connectivity Accept message, the MME does not include the IPv6 prefix within the PDN Address. The MME includes the APN-AMBR and the EPS Bearer QoS parameter QCI into the Session Management Request. Furthermore, if the UE has UTRAN or GERAN capabilities and the network supports mobility to UTRAN or GERAN, the MME uses the EPS bearer QoS parameters to derive the corresponding PDP context parameters QoS Negotiated (R99 QoS profile), Radio Priority, Packet Flow Id and TI and includes them in the Session Management Request. If the UE indicated in the UE Network Capability that it does not support BSS packet flow procedures, then the MME shall not include the Packet Flow Id. MME will not send the S1 Bearer Setup Request message until any outstanding S1 Bearer Setup Response message for the same UE has been received or timed out. If the APN-AMBR has changed the MME may update the UE-AMBR if appropriate. The MME may include an indication whether the traffic of this PDN Connection is allowed to be offloaded to WLAN, as described in clause 4.3.23. If the UE has indicated PDN type "Non-IP" or "Ethernet", the MME and PDN GW shall not change PDN type.
If the MME or PDN GW has changed the PDN Type, an appropriate reason cause shall be returned to the UE as described in clause 5.3.1.1.
If Control Plane CIoT EPS Optimisation applies for an IP PDN connection, and the UE has sent in the PDN Connectivity Request the Header Compression Configuration, the MME shall include the Header Compression Configuration in the PDN Connectivity Accept message. The MME also binds the uplink and downlink ROHC channels to support header compression feedback signalling. If the UE has included ROHC context setup parameters in Header Compression Configuration in the PDN Connectivity Request, the MME may acknowledge ROHC context setup parameters. If the ROHC context is not established during the PDN connection establishment procedure, before using the compressed format for sending the data, the UE and the MME need to establish the ROHC context with ROHC IR packet based on Header Compression Configuration.
If the MME based on local policy determines the PDN connection shall only use the Control Plane CIoT EPS Optimisation, the MME shall include a Control Plane Only Indicator in the Session Management Request. For PDN connections with an SCEF, the MME shall always include the Control Plane Only Indicator. If there is an existing SGi PDN connection for this UE for which the MME included a Control Plane Only Indicator, the MME shall include it also for the additional SGi PDN connection. If the MME did not include a Control Plane Only Indicator for any of the existing SGi PDN connections of this UE, the MME shall not include it for the additional SGi PDN connection. A UE receiving the Control Plane Only Indicator, for a PDN connection shall only use the Control Plane CIoT EPS Optimisation for this PDN connection.
NOTE 6: The MME decision whether to include a Control Plane Only Indicator to an SGi PDN connection for a UE that previously had no SGi connections will impact other potential subsequent SGi PDN connections for that UE.
8. If the eNodeB received an S1-AP Initial Context Setup Request, the eNodeB sends RRC Connection Reconfiguration to the UE including the PDN Connectivity Accept message.
If the eNodeB received an S1-AP Downlink NAS Transport message containing the NAS PDN Connectivity Accept message, the eNode B sends a RRC Direct Transfer message to the UE and the steps 9 and 10 are not executed.
The UE shall store the QoS Negotiated, Radio Priority, Packet Flow Id and TI, which it received in the Session Management Request IE, for use when accessing via GERAN or UTRAN. The UE may provide EPS Bearer QoS parameters to the application handling the traffic flow. The application usage of the EPS Bearer QoS is implementation dependent. The UE shall not reject the RRC Connection Reconfiguration on the basis of the EPS Bearer QoS parameters contained in the Session Management Request.
If the UE receives an IPv4 address set to 0.0.0.0, it may negotiate the IPv4 address with DHCPv4 as specified in TS 29.061 [38], If the UE receives an IPv6 interface identifier, it may wait for the Router Advertisement from the network with the IPv6 prefix information or it may send a Router Solicitation if necessary.
NOTE 7: The IP address allocation details are described in clause 5.3.1 on "IP Address Allocation".
9. The UE sends the RRC Connection Reconfiguration Complete to the eNodeB.
10. The eNodeB send an S1-AP Bearer Setup Response to the MME. The S1-AP message includes the TEID of the eNodeB and the address of the eNodeB used for downlink traffic on the S1_U reference point.
If the Correlation ID or SIPTO Correlation ID is included in the Bearer Setup Request, the eNodeB shall use the included information to establish a direct user plane path to the L-GW and forward uplink data for Local IP Access or SIPTO at the Local Network with L-GW function collocated with the (H)eNB accordingly.
11. The UE NAS layer builds a PDN Connectivity Complete message including EPS Bearer Identity. The UE then sends a Direct Transfer (PDN Connectivity Complete) message to the eNodeB.
12. The eNodeB sends an Uplink NAS Transport (PDN Connectivity Complete) message to the MME.
After the PDN Connectivity Accept message and once the UE (if applicable to the PDN type) has obtained a PDN Address Information, the UE can then send uplink packets towards the eNodeB which may then be tunnelled by the MME to the Serving GW and PDN GW, or transferred by the MME to an SCEF (see TS 23.682 [74]), as per subscription information related to APN discussed above in step 2. If the UE requested for a dual address PDN type (IPv4v6) to a given APN and was granted a single address PDN type (IPv4 or IPv6) by the network with a reason cause indicating that only single IP version per PDN connection is allowed, the UE should request for the activation of a parallel PDN connection to the same APN with a single address PDN type (IPv4 or IPv6) other than the one already activated. If the UE receives no reason cause in step 8 in response to a IPv4v6 PDN type and it receives an IPv6 Interface Identifier apart from the IPv4 address or 0.0.0.0 in the PDN Address field, it considers that the request for a dual address PDN was successful. It can wait for the Router Advertisement from the network with the IPv6 prefix information or it may send Router Solicitation if necessary.
13. Upon reception of the Bearer Setup Response message in step 10 and the PDN Connectivity Complete message in step 12, the MME sends a Modify Bearer Request (EPS Bearer Identity, eNodeB address, eNodeB TEID, Handover Indication, Presence Reporting Area Information) message to the Serving GW. If the Control Plane CIoT EPS Optimisation applies and the PDN connection is not served via a SCEF type of connectivity, steps 13 and 14 are executed only if the MME needs to report a change of UE presence in Presence Reporting Area, otherwise, if the PDN connection is served by SCEF, steps 13,14, 15, and 16 are not executed. If Request Type indicates "handover", the Handover Indication is also included. If the MME has been requested to report a change of UE presence in Presence Reporting Area, the MME includes in this message the Presence Reporting Area Information comprising the PRA identifier(s) and indication(s) on whether the UE is inside or outside the area(s). When receiving the request for reporting change of UE presence in Presence Reporting Area, and the MME decides not to activate reporting UE presence in one or more of the received Presence Reporting Area(s), the MME reports also the inactive Presence Reporting Area(s) in this message.
13a. If the Handover Indication is included in step 13, the Serving GW sends a Modify Bearer Request (Handover Indication) message to the PDN GW to prompt the PDN GW to tunnel packets from non 3GPP IP access to 3GPP access system and immediately start routing packets to the Serving GW for the default and any dedicated EPS bearers established. If Presence Reporting Area Information is included in step 13, the Serving GW sends a Modify Bearer Request (Presence Reporting Area Information) message to the PDN GW.
NOTE 8: The PDN GW forwards the Presence Reporting Area Information to the PCRF, to the OCS or to both as defined in TS 23.203 [6].
13b. The PDN GW acknowledges by sending Modify Bearer Response to the Serving GW.
14. The Serving GW acknowledges by sending Modify Bearer Response (EPS Bearer Identity) to the MME. The Serving GW can then send its buffered downlink packets.
15. After the MME receives Modify Bearer Response in step 14, if Request type does not indicate handover and an EPS bearer was established and if the subscription data indicates that the user is allowed to perform handover to non-3GPP accesses and if this is the first PDN connection associated with this APN and if the MME selected a PDN GW that is different from the PDN GW identity which was previously indicated by the HSS in the PDN subscription context, the MME shall send a Notify Request including the PDN GW address and the APN to the HSS for mobility with non-3GPP accesses. The message shall include information that identifies the PLMN in which the PDN GW is located.
For an unauthenticated or roaming UE, if the Request Type of the UE requested connectivity procedure indicates "Emergency", the MME shall not send any Notify Request to the HSS. For a non-roaming authenticated UE, based on operator configuration (e.g. on whether Voice over WLAN is supported or not by the operator), if the Request Type indicates "Emergency", the MME may send a Notify Request to the HSS including the "PDN GW currently in use for emergency services", which comprises the PDN GW address and an indication that the PDN connection is for emergency services. The HSS shall store it as part of the UE context for emergency services.
16. In the case of non-emergency services, the HSS stores the PDN GW identity and the associated APN. In the case of emergency services, the HSS stores the "PDN GW currently in use for emergency services". Then the HSS sends a Notify Response to the MME.
NOTE 9: For handover from non-3GPP access, the PDN GW initiates resource allocation deactivation procedure in the trusted/untrusted non-3GPP IP access as specified in TS 23.402 [2].
|
495b59b986f98d41912141cabbec196e
|
23.401
|
5.10.3 UE or MME requested PDN disconnection
|
The UE or MME requested PDN disconnection procedure for an E-UTRAN is depicted in figure 5.10.3-1. The procedure allows the UE to request for disconnection from one PDN. Bearers including the default bearer of this PDN shall be deleted during this procedure. The procedure also allows the MME to initiate the release of a PDN connection.
This procedure is also used as part of the SIPTO function when the MME determines that GW relocation is desirable. In this situation the MME deactivates the PDN connection(s) relevant to SIPTO-allowed APN(s) using the "reactivation requested" cause value, and the UE should then re-establish those PDN connection(s).
NOTE 1: The deactivation with reactivation requested does not work with pre-Rel‑9 LTE UEs.
It shall be possible to configure the MME to deactivate a PDN connection, for PDN GW relocation due to SIPTO above RAN, only when UE is in ECM-IDLE mode or during a Tracking Area Update procedure without established RAB(s).
This procedure is not used to terminate the last PDN connection unless "Attach without PDN Connectivity is supported" in the Preferred Network behaviour indicated by the UE at attach time is supported by the network and the UE at any time it requires the last PDN connection to be disconnected. The UE uses the UE-initiated Detach procedure in clause 5.3.8.2 to disconnect the last PDN connection. The MME uses the MME-initiated Detach procedure in clause 5.3.8.3 to release the last PDN connection.
Figure 5.10.3-1: UE or MME requested PDN disconnection
NOTE 2: For a PMIP-based S5/S8, procedure steps (A) are defined in TS 23.402 [2]. Steps 3, 4 and 5 concern GTP based S5/S8.
NOTE 3: If after step 6, the MME determines that PDN being disconnected has no active bearers in the E-UTRAN, (e.g. because data is transported using Control Plane CIoT EPS Optimisation) steps 7, 8. 10a and 10b are modified to only transfer the indicated ESM signalling messages and steps 9a and 9b are skipped.
1. The procedure is triggered by either step 1a or step 1b.
1a. The UE initiates the UE requested PDN disconnection procedure by the transmission of a PDN Disconnection Request (LBI) message. The LBI indicates the default bearer associated with the PDN connection being disconnected. If the UE was in ECM-IDLE mode, this NAS message is preceded by the Service Request procedure if any of the exiting PDN connections were using the User Plane without CIoT EPS Optimisation, or, if the user plane was used just with User Plane CIoT EPS Optimisations, a Resume Procedure is executed instead.
1b. The MME decides to release the PDN connection. This may be e.g. due to change of subscription, lack of resources, due to SIPTO if the PDN connection serves a SIPTO-allowed APN or on receiving a PDN GW Restart Notification from the Serving GW as specified in TS 23.007 [72]. If the UE is in ECM-IDLE state and the reason for releasing PDN connection is "reactivation requested" e.g. due to SIPTO, the MME initiates paging via Network Triggered Service Request procedure in clause 5.3.4.3 from step 3a onwards in order to inform UE of the request.
2. If the PLMN has configured secondary RAT usage reporting, the MME shall perform step 7 through 10 before step 2 onwards. If the PDN connection was served by a P-GW, the EPS Bearers in the Serving GW for the particular PDN connection are deactivated by the MME by sending Delete Session Request (Cause, LBI, User Location Information (ECGI), Secondary RAT usage data) to the Serving GW. This message indicates that all bearers belonging to that PDN connection shall be released. If the UE Time Zone has changed, the MME includes the UE Time Zone IE in this message. For PDN connection to the SCEF the MME indicates to the SCEF the connection for the UE is no longer available according to TS 23.682 [74] and steps 2,3,4,5,6 are not executed. If the MME received Secondary RAT usage data in step 9b, the MME shall include it in this Delete Session Request message.
3. The Serving GW sends Delete Session Request (Cause, LBI, User Location Information (ECGI), Secondary RAT usage data) to the PDN GW. The S‑GW also includes User Location Information IE and/or UE Time Zone IE if it is present in step 2. The Serving GW also includes the Secondary RAT usage data in this message if it was present in step 2 and if PDN GW secondary RAT usage data reporting is active.
4. The PDN GW acknowledges with Delete Session Response (optionally, APN Rate Control Status).
5. The PDN GW employs the PCEF-initiated IP‑CAN Session Termination procedure as defined in TS 23.203 [6] to indicate to the PCRF that the IP-CAN session is released if PCRF is applied in the network. If requested the PDN GW indicates User Location Information and/or UE Time Zone Information to the PCRF as defined in TS 23.203 [6].
6. The Serving GW acknowledges with Delete Session Response (optionally, APN Rate Control Status).
If received, the MME stores the APN Rate Control Status in the MM context.
7. If the UE is in ECM IDLE state and the PDN disconnection is decided by the MME, the MME shall delete the corresponding contexts of the PDN connection locally, steps 7 to 10b are skipped except if the MME has decided to restore certain PDN connections as specified in TS 23.007 [72] or for other reasons e.g. SIPTO. The MME initiates the deactivation of all Radio Bearers associated with the PDN connection to the eNodeB by sending the Deactivate Bearer Request message to the eNodeB. The MME shall re-calculate the UE-AMBR (see clause 4.7.3). This S1-AP message carries the list of EPS bearers to be released, the new UE-AMBR, and a NAS Deactivate EPS Bearer Context Request (LBI) message. The MME builds a NAS message Deactivate EPS Bearer Context Request including the EPS Bearer Identity, and includes it in the S1-AP Deactivate Bearer Request message.
If the network wants to trigger GW relocation (e.g. for SIPTO), the NAS message Deactivate EPS Bearer Context Request includes the request for reactivation of the same PDN connection via the same APN by the UE.
If the MME released the PDN connection due to failed bearer set up during handover, the UE and the MME deactivate the failed contexts locally without peer-to peer ESM signalling.
NOTE 4: If the UE is in ECM‑IDLE state and the PDN disconnection is decided by the MME, the EPS bearer state is synchronized between the UE and the network at the next ECM‑IDLE to ECM‑CONNECTED transition (e.g. Service Request or TAU procedure).
8. The eNodeB sends the RRC Connection Reconfiguration message including the corresponding bearers to be released and the NAS Deactivate EPS Bearer Context Request (LBI) message to the UE.
9a. The UE releases all resources corresponding to the PDN connection and acknowledges this by sending the RRC Connection Reconfiguration Complete message to the eNodeB.
9b. The eNodeB sends an acknowledgement of the deactivation to the MME. If the PLMN has configured secondary RAT usage reporting and the eNodeB has Secondary RAT usage data to report, the Secondary RAT usage data is included.
10a. The UE NAS layer builds a Deactivate EPS Bearer Context Accept message. The UE then sends a Direct Transfer (Deactivate EPS Bearer Context Accept) message to the eNodeB.
If the Deactivate EPS Bearer Context Request message from the MME indicated reactivation requested, the UE starts the UE initiated PDN connection request procedure as specified in clause 5.10.2 by using the same APN of the released PDN connection.
10b. The eNodeB sends an Uplink NAS Transport (Deactivate EPS Bearer Context Accept) message to the MME.
The MME determines the Maximum APN Restriction for the remaining PDN connections and stores this new value for the Maximum APN Restriction.
|
495b59b986f98d41912141cabbec196e
|
23.401
|
5.10.4 MME triggered Serving GW relocation
|
The MME triggered Serving GW relocation procedure for E-UTRAN is depicted in figure 5.10.4-1. The procedure allows the MME to trigger Serving GW relocation due to events other than those described in the mobility scenarios (see clause 5.3.3.1 and clause 5.5.1). Such scenario exists during the establishment of a SIPTO at local network PDN connection with stand-alone GW or during the establishment of a SIPTO above RAN PDN connection.
Figure 5.10.4-1: MME triggered Serving GW relocation
1. The Serving GW relocation procedure may be triggered by the MME due to events that may benefit from a Serving GW relocation other than those described in the mobility events scenarios.
2. If the MME determines that the Serving GW is to be relocated then it selects a new Serving GW according to clause 4.3.8.2. The MME sends a Create Session Request (bearer context(s) with PDN GW addresses and TEIDs (for GTP-based S5/S8) or GRE keys (for PMIP-based S5/S8) at the PDN GW(s) for uplink traffic, eNodeB address(es) and TEIDs for downlink user plane for the existing EPS bearers, the Protocol Type over S5/S8, Serving Network) message per PDN connection to the new Serving GW. The new Serving GW allocates the S‑GW addresses and TEIDs for the uplink traffic on S1_U reference point (one TEID per bearer). The Protocol Type over S5/S8 is provided to Serving GW which protocol should be used over S5/S8 interface. If the PDN GW requested UE's location info, the MME also includes the User Location Information IE in this message. If the PDN GW requested UE's User CSG information (determined from the UE context), the MME includes the User CSG Information IE in this message if the User CSG Information has changed.
3. The new Serving GW assigns addresses and TEIDs (one per bearer) for downlink traffic from the PDN GW. The Serving GW allocates DL TEIDs on S5/S8. It sends a Modify Bearer Request (Serving GW addresses for user plane and TEID(s), Serving Network) message per PDN connection to the PDN GW(s). The S‑GW also includes User Location Information IE and/or UE Time Zone IE and/or User CSG Information IE if it is present in step 2. The PDN GW updates its context field and returns a Modify Bearer Response (Charging Id, MSISDN, etc.) message to the Serving GW. The MSISDN is included if the PDN GW has it stored in its UE context. The PDN GW starts sending downlink packets to the new GW using the newly received address and TEIDs. These downlink packets will use the new downlink path via the new Serving GW to the eNodeB. This step is performed for all connected PDN-GWs for that specific UE.
4. The new Serving GW sends a Create Session Response (Serving GW addresses and uplink TEID(s) for user plane) message back to the MME. The MME starts a timer, to be used in step 6.
5. The MME sends a Bearer Modify Request (Serving GW addresses and uplink TEID(s) for user plane, Secondary RAT usage data request) message to eNodeB. The eNodeB starts using the new Serving GW address(es) and TEID(s) for forwarding subsequent uplink packets and sends a Bearer Modify Response message to the MME. If the PLMN has configured secondary RAT usage reporting, the MME may request the eNodeB for Secondary RAT usage data in the Bearer Modify request message. If the eNodeB has Secondary RAT usage data, it provides it in the Bearer Modify Response message.
5a. If Secondary RAT usage data is included in the previous message and if PDN GW Secondary RAT usage reporting is active, the MME uses the Secondary RAT usage data reporting procedure as described in clause 5.7A.3 figure 5.7A.3-2 to provide this information to the Serving GW and PDN GW. The MME includes a flag that the Serving GW shall not process this information and forward it to the PDN GW.
6. When the timer has expired after step 4, the MME releases the bearer(s) in the old Serving GW by sending a Delete Session Request message (Cause, Operation Indication, Secondary RAT usage data). The operation Indication flag is not set, that indicates to the old Serving GW that the old Serving GW shall not initiate a delete procedure towards the PDN GW. The old Serving GW acknowledges with Delete Session Response messages. The MME includes the Secondary RAT usage data if the eNodeB had provided it to the MME in step 5.
If the Serving GW relocation procedure towards a new Serving GW fails, based on operator policy, the MME should go back to the old Serving GW and disconnects the affected PDN connections (e.g. SIPTO at local network) that are no longer allowed to remain connected.
|
495b59b986f98d41912141cabbec196e
|
23.401
|
5.11 UE Capability Handling
| |
495b59b986f98d41912141cabbec196e
|
23.401
|
5.11.1 General
|
The UE Capability information is made up of the UE Radio Capability information and the UE Core Network Capability information.
The UE Radio Capability for Paging Information is separate from both the UE Radio Capability information and the UE Core Network Capability information. While some of the UE Radio Capability for Paging Information may be used to enhance the paging in the E-UTRAN, other E-UTRAN features are critically dependent upon it (see TS 36.300 [5]).
|
495b59b986f98d41912141cabbec196e
|
23.401
|
5.11.2 UE Radio Capability Handling
|
The UE Radio Capability information contains information on RATs that the UE supports (e.g. power class, frequency bands, etc). Consequently, this information can be sufficiently large (e.g. >50 octets for a UE supporting a small number of frequency bands; or multiple kilo bytes for a UE supporting many frequency bands and a large multiplicity of combinations of these frequency bands) that it is undesirable to send it across the radio interface at every transition from ECM‑IDLE to ECM‑CONNECTED. To avoid this radio overhead, the MME stores the UE Capability information during ECM‑IDLE state and the MME shall, if it is available, send its most up-to-date UE Radio Capability information to the E‑UTRAN in the S1 interface INITIAL CONTEXT SETUP REQUEST message unless the UE is performing an Attach procedure or a Tracking Area Update procedure for the "first TAU following GERAN/UTRAN Attach" or for a "UE radio capability update".
NOTE 1: The UTRAN Radio Capabilities are excluded from the information stored in the MME owing to issues with the handling of dynamic UMTS security parameters.
If a UE supports both NB-IoT and WB-E-UTRAN, the UE handles the UE Radio capability information as follows:
- When the UE is camping on NB-IoT the UE provides only NB-IoT UE radio capabilities to the network.
- When the UE is camping on WB-E-UTRAN, the UE provides UE radio capabilities including WB-E-UTRAN UE radio capabilities but not NB-IoT UE radio capabilities to the network.
In order to handle the distinct UE radio capabilities, the MME stores a separate NB-IoT specific UE Radio Capability information when the UE provides the UE Radio Capability information while camping on NB-IoT.
When the UE is camping on NB-IoT, the MME sends, if available, the NB-IoT specific UE Radio Capability information to the E-UTRAN.
When the UE is camping on WB-E-UTRAN, the MME sends, if available, UE radio capabilities including WB-E-UTRAN UE radio capabilities but not NB-IoT radio capabilities.
For a UE that supports NR as a Secondary RAT, the UE's NR radio capabilities are contained within the UE Radio Capability IE.
If the UE is performing an Attach procedure or a Tracking Area Update procedure for the "first TAU following GERAN/UTRAN Attach" or for "UE radio capability update", the MME shall delete (or mark as deleted) any UE Radio Capability information that it has stored, and, if the MME sends an S1 interface INITIAL CONTEXT SETUP REQUEST or UE RADIO CAPABILITY MATCH REQUEST message during that procedure, the MME shall not send any UE Radio Capability information to the E‑UTRAN in that message. This triggers the E‑UTRAN to request the UE Radio Capability from the UE and to upload it to the MME in the S1 interface UE CAPABILITY INFO INDICATION message. The size of the UE Radio Capability information may be greater than can be carried in single RRC message but less than the maximum size of messages on the S1 interface. In this case, to obtain the information that it needs the RAN should send multiple requests to the UE for different sub-sets of UE Radio Capability information (e.g. one request per RAT). Then the RAN shall combine these subsets (excluding UTRAN and NB-IoT capabilities) into a single UE Radio Capability IE and upload it to the MME in the S1 interface UE CAPABILITY INFO INDICATION message.
The MME stores the UE Radio Capability information, and includes it in further INITIAL CONTEXT SETUP REQUEST or UE RADIO CAPABILITY MATCH REQUEST messages in other cases than Attach procedure, Tracking Area Update procedure for the "first TAU following GERAN/UTRAN Attach" and "UE radio capability update" procedure.
If the UE is performing a Service Request (or other) procedure and the MME does not have UE Radio Capability information available (or it is available, but marked as "deleted"), then the MME sends an S1 interface INITIAL CONTEXT SETUP REQUEST message to the E‑UTRAN without any UE Radio Capability information in it. This triggers the E‑UTRAN to request the UE Radio Capability from the UE and upload it to the MME in the S1 interface UE CAPABILITY INFO INDICATION message.
NOTE 2: This use of the INITIAL CONTEXT SETUP REQUEST message means that for a signalling only procedure such as a periodic Tracking Area Update, the UE Radio Capability would not be sent to the E‑UTRAN.
NOTE 3: If a "first TAU following GERAN/UTRAN Attach" Tracking Area Update is performed during ECM-CONNECTED mode, e.g. after an inter RAT handover, no INITIAL CONTEXT SETUP REQUEST is sent and the UE Radio Capability information in the MME will remain deleted until the next ECM-IDLE to ECM-CONNECTED transition (or later, e.g. if the next activity from the UE is another Tracking Area Update).
When the CIoT EPS Optimisations do not apply, if the MME has not stored the UE Radio Capability information, in order to obtain UE radio capability for paging information, the MME can trigger the retrieval of the UE Radio Capability information by indicating UE Radio Capability request in DOWNLINK NAS TRANSPORT message during Attach or TAU procedure.
For the CIoT EPS Optimisations, during the Attach procedure or the Tracking Area Update procedure e.g. for the "first TAU following GERAN/UTRAN Attach", or mobility between a cell that does not broadcast SystemInformationBlockType31(-NB) and an E-UTRA cell that broadcasts SystemInformationBlockType31(-NB)), if the MME does not send an S1 interface INITIAL CONTEXT SETUP REQUEST to the E-UTRAN, the MME should obtain the UE Radio Capability information by sending either the DOWNLINK NAS TRANSPORT message indicating UE Radio Capability request or the CONNECTION ESTABLISHMENT INDICATION message without UE Radio Capability information included to the E-UTRAN. This triggers the E‑UTRAN to request the UE Radio Capability from the UE and upload it to the MME in the S1 interface UE CAPABILITY INFO INDICATION message, as specified in TS 36.300 [5]. In subsequent ECM connections, if the MME does not send an S1 interface INITIAL CONTEXT SETUP REQUEST to the E‑UTRAN, the MME sends the UE Radio Capability to the E-UTRAN in the CONNECTION ESTABLISHMENT INDICATION message or DOWNLINK NAS TRANSPORT message.
The UE Radio Capability is not provided directly from one CN node to another. It will be uploaded to the MME when the E-UTRAN requests the UE Radio Capability information from the UE.
During handover via the MME (both intra RAT and inter RAT), the radio capability information for the source and target 3GPP RATs (with the possible exception of UTRAN and E-UTRAN) are transferred in the "source to target transparent container". Information on additional 3GPP RATs is optionally transferred in the "source to target transparent container".
At handover, transfer of the radio capability information related to the source and/or additional RATs is beneficial as it avoids the need for the target RAT to retrieve the information from the UE prior to a subsequent inter-RAT handover. However, there may be situations where the size of the UE Radio Capability may be too large for the information on all of the UE's RATs to be carried in a single message on one or more of the network interfaces involved in the handover. Hence, the source RAN shall ensure that the size of the UE Radio Capability information does not cause the size of the "source to target transparent container" to exceed the limits that can be handled by interfaces involved in the handover (e.g. Iu interface (TS 25.413 [22]) and, following SRVCC, E interface (TS 29.002 [86])). This may result in some radio capability information being omitted from the "source to target transparent container" at inter-RAT handover.
In the case that a source RAN node omits some radio capability information from the "source to target transparent container" at handover, the source RAN node shall ensure that any future target RAN node can detect that that radio capability information has been omitted.
Owing to issues with dynamic UTRAN security parameters, special rules apply to the handling of the UTRAN radio capability information at inter-RAT handover (see e.g. the HandoverPreparationInformation message description in TS 36.331 [37] and the usage of the PS Handover Complete Ack message in TS 43.129 [8] and TS 48.018 [42])
To allow for the addition of future radio technologies, frequency bands, and other enhancements, the MME shall store the UE Radio Capability Information as defined in TS 23.008 [28].
The E‑UTRAN stores the UE Radio Capability information, received in the S1 interface INITIAL CONTEXT SETUP REQUEST message or obtained from the UE, for the duration of the RRC connection for that UE. Before any handover attempt from E‑UTRAN to UTRAN, the E‑UTRAN retrieves the UE's UTRAN Radio Capabilities from the UE.
If the UE's non-UTRAN UE Radio Capability information changes while in ECM-IDLE state (including cases of being in GERAN/UTRAN coverage), the UE shall perform a Tracking Area Update indicating "UE radio capability update" when it next returns to E‑UTRAN coverage. When the UE is in ECM-IDLE with AS information stored (as defined in clause 4.11 for User Plane CIOT EPS optimisation), NAS shall trigger AS to establish a new RRC connection and not resume the existing one in order to send Tracking Area Update indicating "UE radio capability update". As a result of this, the access stratum in the UE will discard the AS information and establish a new RRC connection as defined in TS 36.331 [37].
The UE shall perform a Tracking Area Update procedure at every change between a cell that does not broadcast SystemInformationBlockType31(-NB) and an E-UTRA cell that broadcasts SystemInformationBlockType31(-NB). This Tracking Area Update shall indicate that the Tracking Area Update is for a "UE radio capability update".
The MME may also request for Voice Support Match Information. If requested, the eNodeB then derives and provides an indication to the MME whether the UE radio capabilities are compatible with the network configuration (e.g. whether the UE supports the frequency bands that the network may rely upon for providing "full" PS voice coverage or whether the UE supports the SRVCC configuration of the network e.g. E-UTRAN to GERAN) as defined in clause 5.3.14.
The signalling of the UE Radio Access Capabilities described in this clause can be optimised by means of the RACS feature defined in clause 5.11.3a.
|
495b59b986f98d41912141cabbec196e
|
23.401
|
5.11.3 UE Core Network Capability
|
The UE Core Network Capability is split into the UE Network Capability IE (mostly for E-UTRAN access related core network parameters) and the MS Network Capability IE (mostly for UTRAN/GERAN access related core network parameters) and contains capabilities, e.g. for CIoT, NAS/AS security algorithms (that also indicate support for EPS-UPIP), etc. Both the UE Network Capability and the MS Network Capability are transferred between CN nodes at MME to MME, MME to SGSN, SGSN to SGSN, and SGSN to MME changes.
In order to ensure that the UE Core Network Capability information stored in the MME is up to date (e.g. to handle the situation when the USIM is moved into a different device while out of coverage, and the old device did not send the Detach message; and the cases of inter-RAT Tracking Area Update), the UE shall send the UE Core Network Capability information to the MME during the Attach and non-periodic Tracking Area Update procedure within the NAS message.
The MME shall store always the latest UE Core Network Capability received from the UE. Any UE Core Network Capability that an MME receives from an old MME/SGSN is replaced when the UE provides the UE Core Network Capability with Attach and the Tracking Area Update signalling. The MME shall remove the stored MS Network Capability, if MS Network Capability is not included in Attach or non-periodic Tracking Area Update signalling e.g. UE is only capable of E-UTRAN.
If the UE's UE Core Network Capability information changes (in either ECM-CONNECTED or in ECM-IDLE state (including cases of being in GERAN/UTRAN coverage and having ISR activated)), the UE shall perform a Tracking Area Update ('type' different to 'periodic') when it next returns to E‑UTRAN coverage - see clause 5.3.3.0.
If the UE supports multiple user plane radio bearers on the NB-IoT RAT (see TS 36.306 [82], TS 36.331 [37]), then the UE shall indicate this in the UE Network Capability IE.
If the UE supports, the RACS feature defined in clause 5.11.3a, and in this specification for the impact on the EPS procedures, then the UE shall indicate this in the UE Network Capability IE.
If the UE supports dual connectivity with NR (see clause 4.3.2a), then the UE shall indicate its support in a NAS indicator.
If the UE supports Service Gap Control (see clause 4.3.17.9), then the UE shall indicate this in the UE Network Capability IE.
If a UE operating two or more USIMs, supports and intends to use one or more Multi-USIM features (see clause 4.3.33) in a PLMN, it shall indicate in the UE Core Network Capability for this USIM in this PLMN that it supports these one or more Multi-USIM features, i.e. by means of one or more of the Connection Release Supported, Paging Cause Indication for Voice Service Supported, Reject Paging Request Supported, Paging Timing Collision Control Supported, and Paging Restriction Supported. Otherwise, the UE with the capabilities of Multi-USIM features shall indicate these one or more Multi-USIM features are not supported.
A UE not operating two or more USIMs shall indicate the Multi-USIM features are not supported.
NOTE: It is not necessary for a UE operating two or more USIMs to use Multi-USIM features with all USIMs.
If the UE supports Enhanced support of discontinuous network coverage for satellite access (see clause 4.3.18.1), then the UE shall indicate this in the UE Network Capability IE.
In the case of satellite access for NB-IoT, if the UE supports reporting its Coarse Location Information via NAS, then the UE shall indicate this in the UE Network Capability IE.
To allow for the addition of future features, the MME shall store the UE Network Capability and the MS Network Capability even if either or both is larger than specified in TS 24.008 [47]/TS 24.301 [46], up to a maximum size of 32 octets for each IE.
If the UE is enabled for Store and Forward Satellite operation (see clause 4.13.9), then the UE shall indicate "S&F Capability" in the UE Network Capability IE.
5.11.3a UE Radio Capability Signalling optimization
With the increase of the size of UE radio capabilities driven e.g. by additional frequency bands and combinations thereof for E-UTRA and NR, an efficient approach to signal UE Radio Access Capability information over the radio interface and other network interfaces is defined with RACS.
In this Release of the specification, RACS does not apply to NB-IOT (terrestrial or satellite).
RACS works by assigning an identifier to represent a set of UE radio capabilities. This identifier is called UE Radio Capability ID. A UE Radio Capability ID can be either UE manufacturer-assigned or PLMN-assigned, as specified in clause 5.2.7. The UE Radio Capability ID is an alternative to the signalling of the UE Radio Capability information over the radio interface, within E-UTRAN, from E-UTRAN to NG-RAN, from MME to E-UTRAN and between CN nodes supporting RACS.
The UCMF (UE radio Capability Management Function) stores all UE Radio Capability ID mappings in a PLMN and is responsible for assigning every PLMN-assigned UE Radio Capability ID in this PLMN, see clause 4.4.13. The UCMF shall be configured with a Version ID for PLMN assigned UE Radio Capability IDs, defined in clause 4.4.13.
The UCMF stores the UE Radio Capability IDs alongside the UE Radio Capability information and the UE Radio Capability for Paging they map to. Each UE Radio Capability ID stored in the UCMF can be associated to one or both UE radio capabilities formats specified in TS 38.331 [89] and TS 36.331 [37]. The two UE radio capabilities formats shall be identifiable by the MME and UCMF and the MME shall store the TS 36.331 [37] format only.
An E-UTRAN which supports RACS can be configured to operate with one of two modes of operation when providing the UE radio capabilities to the MME when the E-UTRAN executes a UE Radio Capability Enquiry procedure (see TS 36.331 [37]) to retrieve UE radio capabilities from the UE.
- Mode of operation A): The E-UTRAN provides to the MME both UE Radio Capability formats (i.e. the TS 36.331 [37] format and TS 38.331 [89] format). The E-UTRAN derives one of the formats using local transcoding of the other format it receives from the UE and extracts the E-UTRAN UE Radio Capability for Paging and NR UE Radio Capability for Paging from the UE Radio capabilities.
- Mode of operation B): The E-UTRAN provides to the MME the TS 36.331 [37] format only.
In a PLMN supporting RACS only in EPS, Mode of Operation B shall be configured.
If the PLMN supports RACS in both EPS and 5GS:
- If RAN nodes in the EPS and 5GS are configured in Mode of operation B, then the UCMF shall be capable to transcode between TS 38.331 [89] and TS 36.331 [37] formats. The UCMF shall be able to generate the RAT-specific UE Radio Capability for Paging information from the UE Radio capabilities.
- If E-UTRAN is configured to operate according to Mode A, then also the NG-RAN shall be configured to operate according to mode A and the UMCF is not required to transcode between TS 38.331 [89] and TS 36.331 [37] formats. The MME shall provide the UCMF with the UE Radio Capability for Paging information.
When the E-UTRAN updates the MME with new UE radio capabilities information, the MME provides the information obtained from the E-UTRAN to the UCMF even if the MME already stores a UE Radio Capability ID for the UE. The UCMF then returns a value of UE Radio Capability ID. If the value is different from the one stored in the MME, the MME updates the UE Radio Capability ID it stores and provides this new value to the E-UTRAN (if applicable) and to the UE.
PLMN-assigned UE Radio Capability ID is assigned to the UE using the GUTI Reallocation procedure, Attach Accept or TAU Accept as defined in present specification. In order to be able to interpret the UE Radio Capability ID a network entity or node may store a local copy of the mapping between the UE Radio Capability ID and its corresponding UE Radio Capability information i.e. a dictionary entry. When no mapping is available between a UE Radio Capability ID and the corresponding UE Radio Capability information in a network entity or node, this network entity or node shall be able to retrieve it and store it.
- An MME which supports RACS shall store such UE Radio Capability ID mapping at least for all the UEs that it serves that have a UE Radio Capability ID assigned.
- The E-UTRAN performs local caching of the UE Radio Capability information for the UE Radio Capability IDs for the UEs it is serving, and potentially for other UE Radio Capability IDs according to suitable local policies.
- When the E-UTRAN needs to retrieve the mapping of a UE Radio Capability ID to the corresponding UE Radio Capability information, it queries the MME using S1 signalling defined in TS 36.413 [36].
- When the MME needs to get the UE Radio Capability Information and the UE Radio Capability for Paging associated to a UE Radio Capability ID it provides the UE Radio capability ID to the UCMF with an indication that it is requesting the TS 36.331 [37] format, and the UCMF returns a mapping of the UE Radio Capability ID to the corresponding UE Radio Capability information in TS 36.331 [37] format to the MME along with the E-UTRAN UE Radio Capability for Paging.
- When the MME needs to obtain a PLMN assigned UE Radio Capability ID for a UE from the UCMF, it provides the UE Capability information it has for the current radio configuration of the UE and the IMEI/TAC for the UE. The MME shall provide to the UCMF the UE Radio Capability information (and at least in Mode A, the UE Radio Capability for Paging) obtained from the E-UTRAN in one or both the TS 38.331 [89] and TS 36.331 [37] formats depending on how the RAN is configured. The UCMF stores the association of IMEI/TAC with this UE Radio Capability ID and the UE Radio Capability information and the UE Radio Capability for Paging in all the formats it receives. The UE Radio Capability information formats the MME provides shall be identifiable at the UCMF.
- UEs, MMEs and RAN nodes which support RACS learn the current value of the Version ID when a new PLMN assigned UE Radio Capability ID is received from the UCMF and the Version ID it contains is different from the ones in their PLMN assigned UE Radio Capability ID cache. For a PLMN, PLMN assigned UE Radio Capability IDs related to old values (i.e. not current value) of the Version ID can be removed from cache but, if so, prior to removing any cached PLMN-assigned UE radio Capability IDs with the current value of the Version ID. The MME, RAN and UE may still continue to use the stored PLMN assigned UE Radio Capability IDs with old values of the Version ID, until these are purged from cache. If an out of date PLMN assigned UE Radio Capability ID is removed from an MME cache, the MME shall proceed to assign a new PLMN assigned UE Radio Capability ID to all the UEs for which the UE context includes the removed PLMN-assigned UE Radio Capability ID, using the GUTI Reallocation procedure, or when these UEs perform a Tracking Area Update. If the MME attempts to resolve a PLMN assigned UE Radio capability ID with an old Version ID, the UCMF shall return an error code indicating that this Version ID is no longer current.
- If at any time the MME has neither a valid UE Radio Capability ID nor any stored UE radio capabilities for the UE, the MME may trigger the RAN to provide the UE Radio Capability information and subsequently request the UCMF to allocate a UE Radio Capability ID.
- The RAN, in order to support MOCN network sharing scenarios, shall be capable to cache PLMN assigned UE Radio Capability IDs per PLMN ID.
A network may utilise the PLMN-assigned UE Radio Capability ID, without involving the UE, e.g. for use with legacy UEs.
Mutual detection of the support of the RACS feature happens between directly connected E-UTRAN nodes and between E-UTRAN and MME using protocol means as defined in TS 36.413 [36] and TS 36.423 [76]. To allow for a mix of RACS-supporting and non-RACS-supporting RAN nodes over the X2 interfaces, the UE Radio Capability ID should be included in the Path Switch signalling during X2 based handover and Handover Request during S1 based handover between MME and E-UTRAN. In addition, RACS-supporting RAN nodes can be discovered across inter-CN node boundaries during S1 handover using the "RACS Indication" in "Target eNB to Source eNB Transparent Container" within the HANDOVER REQUEST ACKNOWLEDGE message to indicate that that target eNodeB is able to acquire the UE radio capabilities through reception of the UE Radio Capability ID in future mobility actions, as defined in TS 36.413 [36]. The support of RACS by peer MMEs or AMFs is based on configuration in a PLMN or across PLMNs.
A UE that supports WB-EUTRA and/or NR indicates its support for RACS to MME using UE Core Network Capability as defined in clause 5.11.3.
A UE that supports RACS and is already assigned with an applicable UE Radio Capability ID in the PLMN, shall signal the UE Radio Capability ID in Attach procedure, as defined in clause 5.3.2, and Tracking Area Update procedure, as defined in clause 5.3.3 and based on triggers defined in TS 24.301 [46]. If both PLMN-assigned and UE manufacturer-assigned UE Radio Capability IDs are available in the UE and applicable in the PLMN, the UE shall signal the PLMN-assigned UE Radio Capability ID. The UE shall delete the PLMN-assigned UE Radio Capability ID(s) for the related PLMN upon receiving an indication from this PLMN.
When a PLMN decides to request a particular type of UE to use UE manufacturer-assigned UE Radio Capability ID(s):
- The UCMF sends either a Nucmf_UECapabilityManagement_Notify or URCMP Event Notification Request message defined in TS 29.674 [91] to the MME including either a list of UE Radio Capability IDs (if the UE was previously using any PLMN assigned IDs) or the IMEI/TAC values corresponding to UE types that are requested to use UE manufacturer-assigned UE Radio Capability ID. These values are stored in a "UE Manufacturer Assigned operation requested list" in the MME.
- The MME uses the GUTI reallocation command message, Attach Accept message or Tracking Area Update Accept message to request the UE to delete all the PLMN-assigned UE Radio Capability ID(s) for this PLMN if the UE is, respectively, registering or is registered with PLMN assigned UE Radio Capability ID or IMEI/TAC values matching one value in the UE manufacturer-assigned operation requested list.
NOTE 1: It is expected that in a given PLMN the UCMF and MMEs will be configured to either use a UE manufacturer-assigned operation requested list based on a list of PLMN assigned UE Radio Capability IDs or a list of TACs, but not both.
NOTE 2: The strategy for triggering of the deletion of PLMN-assigned UE Radio Capability ID(s) in the UE by the MME is implementation-specific (e.g. can be used only towards UEs in ECM-Connected state).
- a UE that receives indication to delete the all the PLMN-assigned UE Radio Capability IDs in the Attach Accept message, Tracking Area Update Accept message or GUTI reallocation command message, deletes any PLMN-assigned UE Radio Capability IDs for this PLMN. The UE proceeds to register with a UE manufacturer-assigned UE Radio Capability ID that is applicable to the current UE Radio configuration.
- When the "UE Manufacturer Assigned operation requested list" contains PLMN assigned UE Radio Capability IDs, the UCMF shall avoid re-assigning PLMN assigned UE Radio Capability IDs that were added to the "UE Manufacturer Assigned operation requested list" in the MMEs to any UE.
- The MME stores a PLMN assigned ID in the UE manufacturer-assigned operation requested list for a time duration that is implementation specific, but TACs are stored until the UCMF require to remove certain TACs from the list (i.e. the list of TACs which are requested to use UE manufacturer-assigned UE Radio Capability IDs in the MME and UCMF is synchronised at all times).
- The UCMF can request at any time the MME to remove PLMN assigned ID(s) or TAC(s) values form the UE manufacturer-assigned operation requested list.
NOTE 3: The MME can decide to remove a UE Radio Capability ID related to selected PLMN from the "UE Manufacturer Assigned operation requested list" list e.g. because no UE with that UE Radio Capability ID has connected to the network for long time. If later a UE with such UE Radio Capability ID connects to the network, the MME contacts the UCMF to resolve the UE Radio Capability ID, and at this point the UCMF can trigger again the deletion of the UE Radio Capability ID by including this in the UE manufacturer-assigned operation requested list of the MME.
The serving MME stores the UE Radio Capability ID for a UE in the UE context and provides this UE Radio Capability ID to E-UTRAN as part of the UE context information using S1 signalling. During inter PLMN mobility, the new MME shall delete the UE Radio Capability ID received from the old MME, unless the operator policy indicates that all UE Radio Capability IDs used in the old PLMN are also valid in the new PLMN.
NOTE 4: If MME decides to allocate TAIs of multiple PLMN IDs as part of Tracking Area to the UE then MME provides the UE Radio Capability ID of the new selected PLMN to the eNodeB during UE mobility, whether the UE Radio Capability ID is taken from stored UE context previously assigned by the same new selected PLMN or generated freshly each time a new PLMN is selected is up to MME implementation.
The UE stores the PLMN-assigned UE Radio Capability ID in non-volatile memory when in EMM-DEREGISTERED state and can use it again when it registers in the same PLMN.
NOTE 5: It is assumed that UE does not need to store the access stratum information (i.e. UE-EUTRA-Capability and UE-NR-Capability specified in TS 36.331 [37] and TS 38.331 [89], respectively) that was indicated by the UE to the network when the PLMN-assigned UE Radio Capability ID was assigned by the network. However, it is assumed that the UE does store the related UE configuration (e.g. whether or not GERAN or UTRAN or MBMS is enabled/disabled).
At any given time at most one UE Radio Capability ID is stored in the UE context in CN and RAN.
The number of PLMN-specific UE Radio Capability IDs that the UE stores in non-volatile memory is left up to UE implementation. However, to minimise the load (e.g. from radio signalling) on the Uu interface and to provide smoother inter-PLMN mobility (e.g. at land borders) the UE shall be able to store at least the latest 16 PLMN-assigned UE Radio Capability IDs (along with the PLMN that assigned them). This number is independent of the UE manufacturer-assigned UE Radio Capability ID(s) the UE may store.
It shall be possible for a UE to change, e.g. upon change in its usage settings, the set of UE radio capabilities in time and signal the associated UE Radio Capability ID, if available. The UE stores the mapping between the UE Radio Capability ID and the corresponding UE Radio Capability information for every UE Radio Capability ID it stores.
If the UE's Radio Capability information changes and there is no associated UE Radio Capability ID for the updated UE Radio Capability information, the UE shall perform the Tracking Area Update procedure for "UE radio capability update" as defined in clause 5.11.2.
The UE shall perform a Tracking Area Update procedure at every change between a cell that does not broadcast SystemInformationBlockType31(-NB) and an E-UTRA cell that broadcasts SystemInformationBlockType31(-NB). This Tracking Area Update shall either include the UE Radio Capability ID applicable to the new area, or, shall indicate that the Tracking Area Update is for a "UE radio capability update".
The E-UTRAN may apply RRC filtering of UE radio capabilities when it retrieves the UE Radio Capability information from the UE as defined in TS 36.331 [37].
NOTE 6: In a RACS supporting PLMN, the filter of UE radio capabilities configured in E-UTRAN is preferably as wide in scope as possible (e.g PLMN-wide). In this case, it corresponds e.g. to the super-set of bands, band-combinations and RATs the PLMN deploys and not only to the specific E-UTRAN node or region.
NOTE 7: If the filter, included in the UE Radio Capability information, of UE radio capabilities configured in two E-UTRAN nodes is different, during handover between these two nodes, it is possible that the target E-UTRAN node might need to enquire the UE for its UE Radio Capability information again and trigger re-allocation of a PLMN-assigned UE Radio Capability ID leading to extra signalling. Additionally, a narrow filter might reduce the list of candidate target nodes.
If a UE supports both NB-IoT and possibly other RATs the UE handles the RACS procedures as follows:
- Since there is no support for RACS in NB-IoT, if the UE supports RACS in non-NB-IoT RATs (i.e. for WB-EUTRA and/or NR):
- NB-IoT specific UE Radio Capability information is handled in UE, RAN and MME according to clause 5.11.2.
- when the UE is not camping on NB-IoT, the UE provides UE radio capabilities for other RATs but not NB-IoT UE radio capabilities, according to TS 36.331 [37]. As a result the UE Radio Capability ID that is assigned by the network corresponds only to the UE radio capabilities of the non-NB-IoT RATs. The UE uses the UE Radio Capability IDs assigned only in Attach and TAU procedures performed over non-NB-IoT RATs.
Support for RACS in 5GS is defined in TS 23.501 [83] and TS 23.502 [84].
|
495b59b986f98d41912141cabbec196e
|
23.401
|
5.11.4 UE Radio Capability for Paging Information
|
Depending upon the features implemented in the E-UTRAN, this procedure may assist the E-UTRAN in optimising the radio paging procedures, or this procedure can be essential for mobile terminating services to succeed.
Using procedures specified in TS 36.413 [36], the eNodeB shall upload the UE Radio Capability for Paging Information to the MME in the S1 interface UE CAPABILITY INFO INDICATION message (in a separate IE from the UE Radio Capability). As specified in TS 36.331 [37], the UE Radio Capability for Paging Information may contain UE Radio Paging Information provided by the UE to the eNodeB, and other information derived by the eNodeB (e.g. band support information) from the UE Radio Capability information.
The UE Radio Capability for Paging Information for NB-IoT and WB-E-UTRAN are separately stored in the MME. The RAT Type (derived from the UE's Tracking Area Code) is used to determine which RAT the information relates to.
The handling of the UE Radio Capability for Paging Information with RACS is described in clause 5.11.3a.
If a UE supports both NB-IoT and WB-E-UTRAN, the UE and eNodeB handle the UE Radio Capability for Paging Information as follows:
- when the UE is camping on NB-IoT the UE provides only NB-IoT information to the network;
- when the UE is camping on WB-E-UTRAN, the UE provides only WB-E-UTRAN information to the network.
Typically, this information is sent to the MME at the same time as the eNodeB uploads the UE Radio Capability information. The MME stores the UE Radio Capability for Paging Information in the MME context. When it needs to page, the MME provides the UE Radio Capability for Paging Information for that RAT to the eNodeB as part of the S1 paging message. The eNodeB may use the UE Radio Capability for Paging Information to enhance the paging towards the UE and/or to calculate when or how to broadcast paging information or the Wake Up Signal to the UE, see TS 36.304 [34].
If the UE is performing an Attach procedure or a Tracking Area Update procedure for the "first TAU following GERAN/UTRAN/ Attach" or for "UE radio capability update", the MME shall delete all UE Radio Capability for Paging Information that it has stored for that UE.
If the UE Radio Capability for Paging Information changes for either RAT, the UE shall follow the same procedures as if the UE Radio Capability changes.
During a change of MME, the old MME includes in the MM context in the Context Response message the UE Radio Capability for Paging of the UE if available. If the RAT type is indicated by the new MME, then the old MME includes the UE Radio Capability for Paging for the corresponding RAT type, if available.
In order to handle the situations of connected mode inter-MME change, the UE Radio Capability for Paging Information is sent to the target MME as part of the MM Context information.
The UE Radio Capability for Paging Information is only applicable for MMEs, i.e. it is not applicable for SGSNs. Therefore, it will not be included by MME during context transfers towards SGSNs.
|
495b59b986f98d41912141cabbec196e
|
23.401
|
5.11.5 UE Radio Capability for Category M Differentiation
|
This functionality is used by the Core Network to be able to identify traffic to/from Category M UEs for charging differentiation.
The eNodeB determines whether a UE is of Category M from the UE's radio capability if UE signals one or more of the specific Category M. The eNodeB then indicates to the MME whether the UE is Category M using the "LTE-M Indication" information in S1-AP message(s) used to upload the UE Radio Capabilities to the MME.
Typically this is at the same time as the eNodeB uploads the UE Radio Capability information. When the UE is of Category M, the MME receives one "LTE-M Indication" from eNB irrespective of whether the UE supports terrestrial WB-E-UTRAN or satellite WB-E-UTRAN or both and irrespective of whether the UE Radio Capability information of the UE is retrieved from terrestrial or satellite access eNB. The MME stores the "LTE-M Indication" in the MME context.
If the UE context in MME contains the "LTE-M Indication" the MME indicates to the S-GW that the RAT type of the UE is one of the LTE-M RAT types in every Create Session Request message and every Modify Bearer Request message, so this is handled for charging and PCC purposes. The MME additionally takes into account whether the UE is accessing over terrestrial WB-E-UTRAN or satellite WB-E-UTRAN when determine the LTE-M RAT type. If the MME requests the SGW to pass LTE-M RAT type to the PDN GW, based on operator policy (e.g. based on roaming agreements or based on the need to pass the LTE-M RAT type information to PGW also), the MME informs the Serving GW that it is requested to relay the LTE-M RAT type to the PGW also. Otherwise, the Serving GW indicates WB-E-UTRAN RAT type to the PDN GW.
In order to handle the situations of inter-MME change, the "LTE-M Indication" is sent from the source MME to the target MME as part of the MM Context information. The UE Radio Capability for Category M Differentiation is only applicable for MMEs, i.e. it is not applicable for SGSNs. Therefore, it will not be included during context transfers from and towards SGSNs.
|
495b59b986f98d41912141cabbec196e
|
23.401
|
5.12 Warning message delivery
| |
495b59b986f98d41912141cabbec196e
|
23.401
|
5.12.1 General
|
Warning message delivery is similar to Cell Broadcast Service defined in TS 23.041 [48], it permits a number of unacknowledged Warning messages to be broadcast to UEs within a particular area.
The maximum size of the Warning message for E-UTRAN is different from that of UTRAN/GERAN.
When S1-flex is used, the eNodeB may receive duplicated Warning messages.
For details on the Warning system message delivery, see TS 23.041 [48].
|
495b59b986f98d41912141cabbec196e
|
23.401
|
5.12.2 Void
| |
495b59b986f98d41912141cabbec196e
|
23.401
|
5.12.3 Void
| |
495b59b986f98d41912141cabbec196e
|
23.401
|
5.13 Discontinuous Reception and UE Specific DRX Parameter handling
|
During the Attach and Tracking/Routing Area Update procedures in E-UTRAN, UTRAN and/or GERAN, the UE can signal its UE Specific DRX Parameters to the Core Network (MME in the E-UTRAN case and SGSN in UTRAN/GERAN case).
In E-UTRAN and UTRAN, the UE may signal that it wishes to use the DRX cycle length broadcast in the RAN's System Information. Alternatively, the UE can propose a DRX cycle length separately for WB-EUTRA and NB-IoT. For NB-IoT, the cell broadcasts an indication of support of UE specific DRX for NB-IoT in that cell, and the UE can request UE specific DRX for NB-IoT during Attach and Tracking Area Update procedures irrespective of whether the cell broadcasts that support indication. The MME shall accept the value proposed by the UE for WB-E-UTRAN. For NB-IoT the MME should accept the UE requested value, but subject to operator policy the MME may change the UE requested values. The MME shall respond to the UE with the Accepted DRX parameter for NB-IoT.
In each S1 interface Page Request message, the MME shall send the UE Specific DRX Parameters for the UE's current RAT (to help determine the DRX cycle length) and information derived from the IMSI (which defines when the UE will be awake from its sleep mode). Details are specified in TS 36.304 [34].
NOTE 1: To ease backward compatibility with Pre-Release 8 SGSNs, the UTRAN and E-UTRAN DRX cycle lengths are encoded in the same field within the TS 24.008 [47] DRX parameter information element.
At MME to MME, MME to SGSN and SGSN to MME mobility, the UE Specific DRX Parameters for RATs other than NB-IoT are sent from the old CN node to the new CN node as part of the MM context information and (except for NB-IoT) should not be sent by the UE in the Tracking Area Update message.
NOTE 2: it is assumed that all SGSNs are Release 99 or newer and hence support storage of the Release '99 encoding of the TS 24.008 [47] DRX parameter information element.
During Attach and non-periodic Tracking Area Update procedures on NB-IoT cells, the UE shall ensure that it has provided the MME with any UE Specific DRX parameter that applies to NB-IoT and optionally UE specific DRX parameter that applies for WB-E-UTRAN.
If a CN node receives UE Specific DRX Parameters in a dedicated message from the UE (e.g. in a Tracking Area Update or Attach message), then the CN node updates any stored information with the information supplied by the UE and uses the UE provided information in preference to any information that might be received from another CN node during the same procedure.
If the UE wishes to alter its GERAN or UTRAN/WB-E-UTRAN/NB-IoT UE Specific DRX Parameters while in E-UTRAN, then it shall send a Tracking Area Update Request message to the MME containing its new UE Specific DRX Parameters. If ISR had been activated for the UE, then the UE shall deactivate ISR by setting its TIN to "GUTI" so that the UE performs a Routing Area Update when it next enters GERAN/UTRAN coverage. When the UE performs that Routing Area Update, the SGSN will receive the updated DRX parameters within the MM context information sent by the MME and hence the UE should not include them again in the Routing Area Update Request message.
If the UE wishes to alter its WB-E‑UTRAN/UTRAN or GERAN DRX Parameters while in GERAN or UTRAN coverage, then the UE shall send a Routing Area Update Request message to the SGSN containing its new UE DRX Parameters. If ISR has been activated, the UE shall deactivate ISR by setting its TIN to "P-TMSI" so that the UE performs a Tracking Area Update when it next returns to E‑UTRAN coverage. When the UE performs that Tracking Area Update, the MME will receive the updated DRX parameters (excluding the one for NB-IoT) within the MM context information sent by the SGSN and hence the UE should not include them again in the Tracking Area Update message.
For NB-IoT, the UE shall apply the DRX cycle broadcast in the cell by the RAN unless it has received Accepted DRX parameters for NB-IoT from the MME and the cell supports UE specific DRX for NB-IoT, in which case the UE shall apply either the DRX cycle broadcast in the cell or the Accepted DRX parameters for NB-IoT, as defined in TS 36.304 [34].
5.13a Extended Idle mode Discontinuous Reception (DRX)
The extended idle mode DRX value range is described in TS 23.682 [74].
A UE and the core network may negotiate the use of extended idle mode DRX as described in TS 23.682 [74]. The MME includes the extended idle mode DRX cycle length in paging message to assist the eNodeB in paging the UE
For extended idle mode DRX cycle length of 5.12s, the network should follow regular paging strategy as defined in clause 5.13
For extended idle mode DRX cycle length of 10.24s or longer, the following applies:
If the UE decides to request for extended idle mode DRX, the UE includes an extended idle mode DRX parameters information element in the attach request and/or TAU request message. The UE may also include the UE specific DRX parameters for regular idle mode DRX according to clause 5.13. The extended idle mode DRX parameters information element includes the idle mode DRX length.
The MME decides whether to accept or reject the UE request for enabling extended idle mode DRX as described in TS 23.682 [74]. If the MME accepts the extended idle mode DRX, the MME based on operator policies and, if available, the extended idle mode DRX cycle length value in the subscription data from the HSS, may also provide different values of the extended idle mode DRX parameters than what was requested by the UE. The MME taking into account the RAT specific Subscribed Paging Time Window, the UEs current RAT -NB-IOT or WB-E-UTRAN) and local policy also assigns a Paging Time Window length to be used, and provides this value to the UE during Attach/TAU procedures together with the extended idle mode DRX cycle length in extended idle mode DRX parameter. If the MME accepts the use of extended idle mode DRX, the UE shall apply extended idle mode DRX based on the received extended idle mode DRX length, the UEs current RAT -NB-IOT or WB-E-UTRAN) and RAT specific Paging Time Window length. If the UE does not receive the extended idle mode DRX parameters information element in the relevant accept message because the SGSN/MME rejected its request or because the request was received by SGSN/MME not supporting extended idle mode DRX, the UE shall apply its regular discontinuous reception as defined in clause 5.13.
NOTE: The extended idle mode DRX cycle length requested by UE takes into account requirements of applications running on the UE. Subscription based determination of eDRX cycle length can be used in those rare scenarios when applications on UE cannot be modified to request appropriate extended idle mode DRX cycle length. The network accepting extended DRX while providing an extended idle mode DRX cycle length value longer than the one requested by the UE, can adversely impact reachability requirements of applications running on the UE.
When the UE has bearers for emergency bearer services, the UE and MME follow regular discontinuous reception as defined in clause 5.13 and shall not use the extended idle mode DRX. Extended idle mode DRX parameters may be negotiated while the UE has bearers for emergency bearer services. When the bearers for emergency bearer services are released, the UE and MME shall reuse the negotiated extended idle mode DRX parameters in the last TAU/Attach procedure.
When the UE is attached for RLOS services, the UE and the MME follow regular discontinuous reception as defined in clause 5.13 and shall not use the extended idle mode DRX.
The UE shall include the extended idle mode DRX parameters information element in each TAU message if it still wants to use extended idle mode DRX. At MME to MME, MME to SGSN and SGSN to MME mobility, the extended idle mode DRX parameters are not sent from the old CN node to the new CN node as part of the MM context information.
If extended idle mode DRX is enabled, the MME handles paging as defined in TS 23.682 [74].
If the MME is requested to monitor Reachability for Data and the UE is about to become reachable for paging, the MME sends a Monitoring Report message to the address that was indicated in the related Monitoring Request as described in TS 23.682 [74].
|
495b59b986f98d41912141cabbec196e
|
23.401
|
5.14 Configuration Transfer procedure
|
The purpose of the Configuration Transfer is to enable the transfer of information between two eNodeBs at any time via S1 interface and the Core Network. An example of application is to exchange the eNodeBs IP addresses in order to be able to use X2 interface between the eNodeBs for Self-Optimised Networks (SON), as specified in TS 36.413 [36].
|
495b59b986f98d41912141cabbec196e
|
23.401
|
5.14.1 Architecture Principles for Configuration Transfer
|
Configuration Transfer between two eNodeBs follows the principles used by RAN Information Management (RIM) procedures (see clause 5.15) between UTRAN, E-UTRAN and GERAN i.e. providing a generic mechanism for the exchange of arbitrary information between applications belonging to the RAN nodes. However Configuration Transfer is only used for intra- E-UTRAN information exchange whereas RIM procedures are designed for inter-RAT information exchange involving GERAN/UTRAN. Such a separate procedure allows avoiding impacts to other RAT access systems when transferred information is added or modified.
The information is transferred via the MME core network node(s). In order to make the information transparent for the Core Network, the information is included in an E-UTRAN transparent container that includes source and target eNodeB addresses, which allows the Core Network nodes to route the messages. If the information is to be transferred between a source eNodeB and a target en-gNB via a target eNodeB for Dual Connectivity with E-UTRAN as Master RAN node and NR as Secondary RAN node as defined in TS 37.340 [85], the source eNodeB indicates the target en-gNB and may indicate the connected target eNodeB as described in TS 36.300 [5], and the target eNode B further transfers the E-UTRAN transparent container to the en-gNB transparently. The mechanism is depicted in figure 5.14 1. An example for such transferred information is the SON information, as specified in TS 36.413 [36].
Figure 5.14-1: inter E-UTRAN Configuration Transfer basic network architecture
The E-UTRAN transparent containers are transferred from the source E-UTRAN node to the destination E-UTRAN node by use of Configuration Transfer messages.
An eNodeB Configuration Transfer message is used from the eNodeB to the MME over S1 interface, a MME Configuration Transfer message is used from the MME to the eNodeB over S1 interface, and a Configuration Transfer Tunnel message is used to tunnel the E-UTRAN transparent container from a source MME to a target MME over the S10 interface.
Each Configuration Transfer message carrying the E-UTRAN transparent container is routed and relayed independently by the core network node(s). Any relation between messages is transparent for the MME, i.e. a request/response exchange between applications, for example SON applications, is routed and relayed as two independent messages by the MME. An MME supporting the Configuration Transfer procedures provides addressing, routing and relaying functions.
|
495b59b986f98d41912141cabbec196e
|
23.401
|
5.14.2 Addressing, routing and relaying
| |
495b59b986f98d41912141cabbec196e
|
23.401
|
5.14.2.1 Addressing
|
All the Configuration Transfer messages contain the addresses of the source and destination RAN nodes. An eNodeB is addressed by the Target eNodeB Identifier. For Dual Connectivity with E-UTRAN as Master RAN node and NR as Secondary RAN node as defined in TS 37.340 [85], the destination RAN node includes the candidate en-gNB Identifier and may include a target eNodeB Identifier for the target eNodeB which is X2 connected to the candidate en-gNB and a TAI associated with the en-gNB.
|
495b59b986f98d41912141cabbec196e
|
23.401
|
5.14.2.2 Routing
|
The following description applies to all the Configuration Transfer messages used for the exchange of the E-UTRAN transparent container.
The source RAN node sends a message to its MME including the source and destination addresses. The MME uses the destination address to route the message encapsulated in a GTPv2 message to the correct MME via the S10 interface (see TS 29.274 [43]).
The MME connected to the target eNodeB decides which RAN node to send the message to, based on the destination address. For Dual Connectivity with E-UTRAN as Master RAN node and NR as Secondary RAN node as defined in TS 37.340 [85], target eNodeB decides which candidate en-gNB to send the message to, based on the destination address.
|
495b59b986f98d41912141cabbec196e
|
23.401
|
5.14.2.3 Relaying
|
The MME performs relaying between GTPv2 messages as described in TS 29.274 [43]. The MME performs relaying between S1 and S10 messages as described in TS 36.413 [36], TS 23.501 [83] and TS 29.274 [43]. The Target eNodeB performs relaying between S1 and X2 message as described in TS 36.413 [36] and TS 36.423 [76].
|
495b59b986f98d41912141cabbec196e
|
23.401
|
5.14.2.4 Applications using the Configuration Transfer procedures
|
The RAN node applications, which use the Configuration Transfer procedures, are fully transparent for the MME. These applications are described in RAN specifications. An example of application is the transfer of information required for Self-Optimised Networks (SON).
|
495b59b986f98d41912141cabbec196e
|
23.401
|
5.15 RAN Information Management (RIM) procedures
| |
495b59b986f98d41912141cabbec196e
|
23.401
|
5.15.1 General
|
The RAN Information Management (RIM) procedures provide a generic mechanism for the exchange of arbitrary information between applications belonging to the RAN nodes. The RAN information is transferred via the MME and SGSN core network node(s). In order to make the RAN information transparent for the Core Network, the RAN information is included in a RIM container that shall not be interpreted by the Core Network nodes.
The RIM procedures are optional both in the RAN and the CN nodes. For the Gb interface the use of RIM procedures is negotiated at start/restart of the Gb link. For the Iu interface there is no negotiation of using RIM procedures or not at Iu link start/restart.
The RAN information is transferred in RIM containers from the source RAN node to the destination RAN node by use of messages. Source and destination RAN nodes can be E-UTRAN, UTRAN or GERAN. Each message carrying the RIM container is routed and relayed independently by the core network node(s). Any relation between messages is transparent for the MME/SGSN, i.e. a request/response exchange between RIM applications, for example, is routed and relayed as two independent messages by the MME/SGSN.
The interfaces which will be used are the Gb, the Iu, the S1, Gn and the S3 interfaces. The RAN information in the RIM container shall be transparent for the Core Network. An MME or SGSN supporting the RIM procedures provides addressing, routing and relaying functions.
|
495b59b986f98d41912141cabbec196e
|
23.401
|
5.15.2 Addressing, routing and relaying
| |
495b59b986f98d41912141cabbec196e
|
23.401
|
5.15.2.1 Addressing
|
All the messages used for the exchange of RAN information contain the addresses of the source and destination RAN nodes. A BSS is addressed by Routing Area Identity (RAI) + Cell Identity (CI) of one of its cells. An eNodeB is addressed by the Target eNodeB Identifier. An RNC is addressed by Global RNC-Id as defined in TS 23.003 [9].
|
495b59b986f98d41912141cabbec196e
|
23.401
|
5.15.2.2 Routing
|
The following description applies to all the messages used for the exchange of RAN information.
The source RAN node sends a message to its MME or SGSN including the source and destination addresses. The SGSN/MME uses the destination address to route the message encapsulated in a GTP message to the correct MME/SGSN via the S3 or Gn interface.
The MME/SGSN connected to the destination RAN node decides which RAN node to send the message to based on the destination address.
|
495b59b986f98d41912141cabbec196e
|
23.401
|
5.15.2.3 Relaying
|
The SGSN performs relaying between BSSGP messages, RANAP messages and GTP messages as described in TS 48.018 [42], TS 25.413 [22], TS 29.060 [14] and TS 29.274 [43]. The MME performs relaying between S1 and S3/Gn messages as described in TS 36.413 [36] and TS 29.274 [43] / TS 29.060 [14].
|
495b59b986f98d41912141cabbec196e
|
23.401
|
5.15.3 Applications using the RIM Procedures
|
The RAN node applications, which use the RIM procedures, are fully transparent for the MME and SGSN. These applications are described in RAN specifications. An example between E-UTRAN and GERAN is the Network Assisted Cell Change described in TS 48.018 [42], TS 25.413 [22] and TS 36.413 [36]. An example between E-UTRAN and UTRAN is the exchange of SON related information described in TS 36.413 [36]
|
495b59b986f98d41912141cabbec196e
|
23.401
|
5.16 MME-initiated procedure on UE's CSG membership change
|
If the UE is in ECM-CONNECTED state and connected via a CSG cell and the MME detects that the UE's CSG membership to that cell has expired, the MME shall send an S1AP UE CONTEXT MODIFICATION REQUEST message to the eNodeB which includes an indication that the CSG membership of the UE has expired. The eNodeB receiving this indication may initiate a handover to another cell. If the UE is not handed over the eNodeB should initiate the S1 release procedure with an appropriate cause. The MME initiates S1 release after a configurable time if the UE is not handed over or released by the CSG cell. If the CSG membership expires for a UE with ongoing emergency bearer service, no indication that the CSG membership of the UE has expired is sent to the eNodeB and the MME shall deactivate all non-emergency PDN connections.
If the UE is in ECM-CONNECTED state and connected via a hybrid cell and the MME detects that the UE's CSG membership to that cell has changed or expired, and the CSG Information Reporting Action indicates User CSG Information shall be reported to the P‑GW then the MME shall modify the last known CSG membership and send a Change Notification message to the Serving GW with User CSG Information to indicate the CSG membership change. The Serving GW shall send the Change Notification message with the User CSG Information to the PDN GW. The MME shall also send the S1AP UE CONTEXT MODIFICATION REQUEST message to the eNodeB which includes an indication of whether the UE is a CSG member. Based on this information the eNodeB may perform differentiated treatment for CSG and non-CSG members. MME shall release the impacted LIPA PDN connection if the LIPA CSG authorization data for this CSG cell is no longer valid due to UE's CSG membership changed or expired.
|
495b59b986f98d41912141cabbec196e
|
23.401
|
5.17 Home eNodeB Multicast Packet Forwarding Function
|
A Home eNodeB L-GW should receive and process multicast group membership report messages (e.g. according to RFC 3376 [62] / RFC 3810 [63]) sent either by the network accessed by LIPA or by the UE. Based upon these messages, the L-GW should forward multicast IP datagrams sent by the UE to the network accessed by LIPA, or from the network accessed by LIPA to the UE, as appropriate.
The UE may implement RFC3376 [62] or RFC 3810 [63] to report multicast groups that the UE seeks to receive.
To make UPnP/DLNA service advertisements sent with an IP TTL=1 available to UEs that employ LIPA, a proxying function in the L-GW may be implemented, e.g. to retransmit UPnP service advertisements to UEs after changing the source address. This proxying to the UE shall not be performed if the multicast packet is transmitted with an IPv4 or IPv6 link-local source address, RFC 3927 [64], RFC 4291 [65].
|
495b59b986f98d41912141cabbec196e
|
23.401
|
5.18 HPLMN Notification with specific indication due to MME initiated Bearer removal
|
When initiating a Delete Session Request procedure, the MME shall add an appropriate cause code facilitating the operator of the P-GW to take appropriate action (e.g. Alarm, O&M action by operator's management network) if needed.
NOTE: This is for the HPLMN operator to be able to differentiate Delete Session Request procedures due to a failure case (e.g. due to a QoS parameter mismatch at Initial Attach) from Delete Session Request procedures that are executed in cases not related to any failure conditions (e.g. due to a Tracking Area Update). Action taken by the HPLMN operator is outside the scope of 3GPP specification.
|
495b59b986f98d41912141cabbec196e
|
23.401
|
5.19 Procedures to support Dedicated Core Networks
| |
495b59b986f98d41912141cabbec196e
|
23.401
|
5.19.1 NAS Message Redirection Procedure
|
When DCNs are used, these steps are used to reroute a NAS message (and thereby a UE) from one CN node to another CN node during Attach, TAU or RAU procedure. These steps are also used by the MME/SGSN or HSS initiated Dedicated Core Network Reselection procedure in clause 5.19.3.
Figure 5.19.1-1: NAS Message Redirection Procedure
The procedure is started when a first new MME/SGSN decides to move the handling of an Attach Request, TAU Request or RAU Request to another CN node.
1. The first new MME/SGSN sends a Reroute NAS Message Request (original RAN message, reroute parameters, Additional GUTI/P-TMSI, UE Usage Type, and optionally the IMSI) to the RAN Node. The reroute parameter is a MMEGI (for E-UTRAN) or Null-NRI/SGSN Group ID (for UTRAN/GERAN) corresponding to the DCN that corresponds to the UE Usage Type. A UE provided Additional GUTI/P-TMSI (if available) from the NAS Request message is included. The MME/SGSN may determine the MMEGI or Null-NRI/SGSN Group ID corresponding to the DCN using DNS procedures. The original RAN message is the complete PDU received from the RAN which contains the original NAS Request message and all RAN IEs. The UE Usage Type shall be included, if available. For the condition to include the IMSI, see step 6 in clause 5.19.2.
2. The RAN node's NNSF selects a new MME/SGSN based on the MMEGI or Null-NRI/SGSN Group ID and possibly also based on an Additional GUTI/P-TMSI. If Additional GUTI/P-TMSI identifies an MME/SGSN within the set of valid nodes identified by MMEGI or Null-NRI/SGSN Group ID, it should be the selected node. Otherwise a valid CN node corresponding to the MMEGI or Null-NRI/SGSN Group ID will be selected. If no valid MME/SGSN is available within the set of valid nodes identified by MMEGI or Null-NRI/SGSN Group ID, the RAN node selects an MME/SGSN from the default DCN or selects the MME/SGSN that sent the Reroute Request, based on operator configuration. The MME/SGSN is selected from the network corresponding to the selected CN operator.
3. Dependent on RAT, the eNodeB/RNC sends the Initial UE message to the selected MME/SGSN or the BSC sends the UL-Unitdata message to the selected SGSN. The initial UE message/UL-Unitdata message includes the NAS Request message, the MMEGI or Null-NRI/SGSN Group ID, UE Usage Type and the IMSI if received from the first SGSN/MME in step 1. The MMEGI or Null-NRI/SGSN Group ID indicates that the message is a rerouted message and the second new MME/SGSN shall not reroute the NAS message. The UE Usage Type shall be included if received in the Reroute NAS Message Request to be used by the second new MME/SGSN to select SGW and PDN GW (see clauses 4.3.8.1 and 4.3.8.2).
|
495b59b986f98d41912141cabbec196e
|
23.401
|
5.19.2 Attach, TAU and RAU procedure for Dedicated Core Network
|
When DCNs are used, the Attach, TAU and RAU procedures in this clause apply.
Figure 5.19.2-1: Attach,TAU and RAU procedure for Dedicated Core Network
1. Attach, TAU, or RAU procedure is initiated as specified in the relevant clauses of this specification and TS 23.060 [7]. The relevant steps of the procedure as specified in the figure above are executed. The following modifications apply:
- In the RRC Connection Complete message transferring the NAS Request message, the UE provides the DCN-ID, if available. If the UE has a PLMN specific DCN-ID the UE shall provide this value and if no PLMN specific DCN-ID exist the pre-provisioned default standardized DCN-ID shall be provided, if pre-provisioned in the UE. The RAN node selects a DCN and a serving MME/SGSN within the network of the selected core network operator based on the DCN-ID and configuration in the RAN node. The NAS Request message is sent to the selected node. The DCN-ID is provided by the RAN to the MME/SGSN together with the NAS Request message.
- E-UTRAN Initial Attach Procedure (clause 5.3.2.1 (Figure 5.3.2.1-1)) and Combined GPRS/IMSI Attach procedure (TS 23.060 [7] clause 6.5.3 (Figure 22)): In the Identification Response message, the old MME/SGSN provides UE Usage Type parameter, if available.
- Tracking area update procedure (clause 5.3.3.1 (Figure 5.3.3.1-1) and 5.3.3.2 (Figure 5.3.3.2-1)): In the Context Response message, the old MME/SGSN provides UE Usage Type parameter, if available.
- Routing area update procedure (clause 5.3.3.3 (Figure 5.3.3.3-1) and 5.3.3.6 (Figure 5.3.3.6-1), TS 23.060 [7] clauses 6.9.1.2.2 (Figure 33), 6.9.1.2.2a (Figure 33a), 6.9.1.3.2 (Figure 35), 6.9.2.1 (Figure 36), 6.9.2.1a (Figure 36a), 6.13.1.1.1 (Figure 52), 6.13.2.1.1 (Figure 54), 6.13.2.1.2 (Figure 54-2), 6.13.2.2.1 (Figure 55), 6.13.2.2.2 (Figure 55-2)): In the Context Response message, the old MME/SGSN provides UE Usage Type parameter, if available.
2. If the (first) new MME/SGSN, i.e. the MME/SGSN that has not received any MMEGI or Null-NRI/SGSN Group ID from RAN, does not have sufficient information to determine whether it should serve the UE, it sends an Authentication Information Request message to the HSS requesting UE Usage Type by adding the parameter "Send UE Usage Type" flag in the message. The MME/SGSN may also request one or more authentication vectors in addition to the UE Usage Type. The (first) new MME/SGSN has sufficient information in the following cases and may then skip this step and step 3:
i. The (first) new MME/SGSN has received the UE Usage Type from the old MME/SGSN in the Identification Response (for Attach) or Context Response (for TAU/RAU) message or Forward Relocation Request (for Handover).
ii. Based on configuration in the (first) new MME/SGSN and UE context information, the MME/SGSN is able to determine whether it should serve the UE.
This step and redirection of NAS message (i.e. step 5 onwards) shall not be performed for TAU/RAU procedure triggered in connected mode, e.g. during handover.
3. The HSS, if supporting DCNs, provides the UE Usage Type in the Authentication Information Answer message, if any is stored for the UE. The UE Usage Type is returned by the HSS in addition to requested authentication vectors.
4. If the (first) new MME/SGSN determines that it shall not reroute the NAS message to another CN node, the MME/SGSN either continues from the designated step as stated in the figure above or depending on operator configuration rejects the NAS request message and the NAS procedure ends in this step. The NAS message is rejected with parameters, e.g. backoff timer, such that the UE does not immediately re-initiate the NAS procedure.
The MME/SGSN sends the DCN-ID, if available, for the DCN to the UE in the NAS Accept message. The UE updates its stored DCN-ID parameter for the serving PLMN if DCN-ID for serving PLMN is changed.
5. If the (first) new MME/SGSN determines that it should reroute the NAS request message to another CN node, the procedure is a TAU or RAU procedure and UE context was received from the old MME/SGSN, the (first) new MME sends a Context Acknowledge message with cause code indicating that the procedure is not successful. The old MME/SGSN shall continue as if Context Request was never received.
6. If the (first) new MME/SGSN determines that it should reroute the NAS request message to another CN node, it uses the "NAS Message Redirection Procedure" in clause 5.19.1. The NAS message is re-routed to a (second) new MME/SGSN. If the IMSI was retrieved unencrypted from the UE by the (first) new MME/SGSN in step 1, the (first) new MME/SGSN shall include the IMSI in the Reroute Message Request.
7. The (second) new MME/SGSN, i.e. the MME/SGSN that receives the rerouted NAS message from RAN with MMEGI or Null-NRI/SGSN Group ID, performs NAS procedure as stated for E-UTRAN in this specification and for GERAN/UTRAN in TS 23.060 [7] from the steps shown in the figure above. The following modifications apply:
- E-UTRAN Initial Attach Procedure (clause 5.3.2.1 (Figure 5.3.2.1-1)) and Combined GPRS/IMSI Attach procedure (TS 23.060 [7] Clause 6.5.3 (Figure 22)): In the Identification Response message, the old MME/SGSN provides UE Usage Type parameter, if available.
- Tracking area update procedure (clause 5.3.3.1 (Figure 5.3.3.1-1) and 5.3.3.2 (Figure 5.3.3.2-1)): In the Context Response message, the old MME/SGSN provides UE Usage Type parameter, if available.
- If the IMSI was received from the first (new) MME/SGSN as part of the NAS Message Redirection Procedure, the second (new) MME/SGSN does not have to retrieve the IMSI from the UE.
- Routing area update procedure (clause 5.3.3.3 (Figure 5.3.3.3-1) and 5.3.3.6 (Figure 5.3.3.6-1), TS 23.060 [7] clauses 6.9.1.2.2 (Figure 33), 6.9.1.2.2a (Figure 33a), 6.9.1.3.2 (Figure 35), 6.9.2.1 (Figure 36), 6.9.2.1a (Figure 36a), 6.13.1.1.1 (Figure 52), 6.13.2.1.1 (Figure 54), 6.13.2.1.2 (Figure 54-2), 6.13.2.2.1 (Figure 55), 6.13.2.2.2 (Figure 55-2)): In the Context Response message, the old MME/SGSN provides UE Usage Type parameter, if available.
- The MME/SGSN sends the DCN-ID, if available, for the new DCN to the UE in the NAS Accept message. The UE updates its stored DCN-ID parameter for the serving PLMN if DCN-ID for serving PLMN is changed.
If network sharing and the Selected PLMN information is not provided by the UE, the SGSN may also include the PLMN ID of selected CN operator in the NAS Accept message.
The (second) new MME/SGSN shall not reroute the NAS message to another CN node since the Initial UE message/UL-Unitdata message from RAN includes MMEGI or Null-NRI/SGSN Group ID. The (second) new MME/SGSN either completes the NAS procedure as stated above or depending on operator configuration rejects the NAS request message and the NAS procedure ends. When rejecting the NAS request, an appropriate cause and backoff time should be included.
In the case of TAU or RAU procedure, the (second) new MME/SGSN may check (e.g. based on the indication that the NAS message has been rerouted and on local configuration) if the PDN GW (for one or more PDN connection(s)) of the UE needs to be changed. If the PDN GW needs to be changed, the (second) new MME/SGSN initiates Detach with reattach required or PDN disconnection with reactivation required procedure after the completion of the TAU or RAU procedure.
5.19.2a Impacts to Handover Procedures
When DCNs are used, the impacts to the handover procedures are captured as below.
- Forward Relocation Request message: When MME changes during handover, in the step where Forward Relocation Request message is sent from the Source MME/SGSN to Target MME/SGSN, the source MME/SGSN also includes the UE Usage Type, if available, in the message. This applies to the following clauses and step:
- 5.5.1.2.2 S1-based handover, normal: Step 3
- 5.5.2.1.2 Preparation phase (E-UTRAN to UTRAN Iu mode Inter RAT handover): Step 3
- 5.5.2.2.2 Preparation phase (UTRAN Iu mode to E-UTRAN Inter RAT handover): Step 3
- 5.5.2.3.2 Preparation phase (E-UTRAN to GERAN A/Gb mode Inter RAT handover): Step 3
- 5.5.2.4.2 Preparation phase (GERAN A/Gb mode to E-UTRAN Inter RAT handover): Step 3
- Selection of new SGW: In the step, subsequent to the Forward Relocation Request message, in which the target MME/SGSN determines if the Serving GW is to be relocated, if the target MME/SGSN supports DCN, the target MME/SGWN also determines if the existing Serving GW supports the DCN for the UE based on UE Usage Type of the UE, locally configured operator's policies as well as UE related context information available at the target network, e.g. information about roaming. This applies to the following clauses and step:
- 5.5.1.2.2 S1-based handover, normal: Step 4
- 5.5.2.1.2 Preparation phase (E-UTRAN to UTRAN Iu mode Inter RAT handover): Step 4
- 5.5.2.2.2 Preparation phase (UTRAN Iu mode to E-UTRAN Inter RAT handover): Step 4
- 5.5.2.3.2 Preparation phase (E-UTRAN to GERAN A/Gb mode Inter RAT handover): Step 4
- 5.5.2.4.2 Preparation phase (GERAN A/Gb mode to E-UTRAN Inter RAT handover): Step 4
- Handover from service area where DCN is not used to an area where DCN is supported: When handover occurs from a service area where DCN is not used to a service area where DCN is supported and the MME or SGSN changes, the target MME or SGSN obtains the UE Usage Type information from the HSS during the subsequent TAU or RAU procedure. If the target MME/SGSN determines that the Serving GW does not support the UE Usage Type, the target MME/SGSN triggers the Serving GW relocation as part of the handover procedures described in clause 5.5. If the target MME or SGSN does not serve the UE Usage type, the handover procedure should complete successfully and then the target MME or SGSN may use the procedure in clause 5.19.3 Step 5 onwards, to change the serving DCN of the UE.
|
495b59b986f98d41912141cabbec196e
|
23.401
|
5.19.3 MME/SGSN or HSS initiated Dedicated Core Network Reselection
|
If DCNs are deployed, this procedure is used by the HSS to update (i.e. add, modify or delete) the UE Usage Type subscription parameter in the serving node. This procedure may result in change of serving node of the UE. This procedure may also be used for MME/SGSN initiated serving node change for UEs, e.g. when configuration about the UE Usage Types served by MME/SGSN is changed. This procedure may also be used after a handover procedure by the target MME/SGSN to redirect a UE to a serving node of another DCN. If UE assisted DCN selection feature is supported by the Core Network, the UE is provided with the new DCN-ID. The subscription change may be applied to a large number of UEs and similar considerations as in the case of MME/SGSN rebalancing specified in clause 4.3.7.3 should be applied to avoid sudden redirection of UEs that could overload the core network nodes (and possibly the RAN if paging is needed). Figure 5.19.3-1: MME/SGSN or HSS Initiated Dedicated Core Network Reselection Steps 1 and 2 apply for HSS initiated Dedicated Core Network Reselection procedure only. 1. The HSS sends an Insert Subscriber Data Request (IMSI, Subscription Data) message to the MME/SGSN. The Subscription Data includes UE Usage Type information or UE Usage Type withdrawal information. NOTE 1: If the UE Usage Type subscription change or withdrawal needs to be applied for a large number of subscribers, the HSS should stagger the insertion of subscription changes to serving nodes, e.g. based on OAM. 2. The MME/SGSN updates the stored Subscription Data and acknowledges the Insert Subscriber Data Request message by returning an Insert Subscriber Data Answer (IMSI) message to the HSS. The procedure ends if the MME/SGSN can continue to serve the UE. 3. If the MME/SGSN decides to transfer the UE immediately to another CN or if the MME/SGSN determines that DCN-ID immediately needs to be updated and the UE is in idle-mode, the MME/SGSN pages the UE. Alternatively the MME waits until the UE becomes active. If MME/SGSN decides to transfer the UE to another CN either Steps 4 through 7 or Step 8 occur. Steps 4 through 7 occur if the UE is already in connected mode or UE enters connected mode by initiating data transfer. Step 8 occurs if the UE is in idle mode and performs a TAU/RAU procedure. If the MME/SGSN determines that only DCN-ID shall be updated in the UE (i.e. serving CN node is kept) only step 4 and 5 occurs. 4. Either triggered by the paging or by uplink data the UE initiates NAS connection establishment. Alternatively the UE initiates NAS connection establishment by sending a TAU/RAU Request. 5. When a NAS connection already exists or when a NAS connection is established for initiating data transfer, the MME/SGSN triggers the GUTI Reallocation/P-TMSI Reallocation procedure. If DCN-ID is available and the MME/SGSN determines that the UE shall be updated with a new DCN-ID, the new DCN-ID shall be included in the GUTI Reallocation Command/P-TMSI Reallocation Command. If the MME/SGSN determines that a CN node re-selection needs to be performed, a non-broadcast TAI/RAI shall be included. 6. The MME/SGSN releases RAN resources and UE is moved to idle mode. NOTE 2: If a large number of UEs need to be offloaded the MME/SGSN should not release RAN resources for all UEs immediately to avoid sudden redirection of UEs that could overload the core network nodes (and possibly the RAN if paging is needed). The MME/SGSN should wait until the release is performed due to inactivity. 7. The non-broadcast TAI/RAI triggers the UE to immediately start the TAU/RAU procedure. If available, the new DCN-ID shall be sent from the UE to the RAN. The MME/SGSN receives the TAU/RAU Request message. 8. The UE performs a TAU/RAU request. The MME/SGSN receives the TAU/RAU Request message. 9. If the UE Usage Type for the UE has been added or modified and if it is not served by the MME/SGSN, or if the UE Usage Type has been withdrawn from the HSS subscription data and subscriptions without UE Usage Type are not served by the MME/SGSN, the MME/SGSN triggers the NAS Message redirection procedure of clause 5.19.1 to redirect the UE. This is followed by step 7 of clause 5.19.2 where the TAU/RAU procedure completes at the MME of the selected DCN. Annex A (informative): Void Annex B (informative): Void Annex C (informative): Void Annex D (normative): Interoperation with Gn/Gp SGSNs D.1 General Considerations This annex specifies interworking between the EPS and 3GPP 2G and/or 3G SGSNs, which provide only Gn and Gp interfaces but no S3, S4 or S5/S8 interfaces, i.e. these Gn/Gp SGSNs provide no functionality that is introduced specifically for the EPS or for interoperation with the E-UTRAN. Interoperation scenarios for operating E-UTRAN with a PLMN maintaining Gn/Gp SGSNs are supported only with a GTP-based S5/S8. NOTE: PMIP-based S5/S8 may be used, but does not support handovers between the Gn/Gp SGSN and MME/S‑GW. The S5/S8 interface for the Operator with Gn/Gp SGSNs will be GTP-based, but can be changed to PMIP-based S5/S8 when the Gn/Gp SGSNs evolve to S4 SGSNs. For these interoperation scenarios the GERAN/UTRAN has to support interoperation with E‑UTRAN. TS 23.682 [74] defines the Monitoring Events feature, and TS 23.060 [7] specifies that the Monitoring Events feature for the Gn/Gp SGSN is not supported. Therefore, during interoperation with Gn/Gp SGSNs Monitoring Event information shall not be expected by the MME/S4-SGSN from a Gn/Gp SGSN, nor shall the MME/S4-SGSN or the HSS transfer Monitoring Event information to a Gn/Gp SGSN. This applies to all operations defined in this annex. D.2 Interoperation Scenario D.2.1 Roaming interoperation scenario In the roaming scenario the vPLMN operates Gn/Gp 2G and/or 3G SGSNs as well as MME and S‑GW for E-UTRAN access. The hPLMN operates a P‑GW. Roaming and inter access mobility between Gn/Gp 2G and/or 3G SGSNs and an MME/S‑GW are enabled by: - Gn functionality as specified between two Gn/Gp SGSNs, which is provided by the MME, and - Gp functionality as specified between Gn/Gp SGSN and Gn/Gp GGSN that is provided by the P‑GW. All this Gp and Gn functionality bases on GTP version 1 only. The architecture for interoperation with Gn/Gp SGSNs in the non-roaming case is illustrated in Figure D.2.1-1. Figure D.2.1-1: Roaming architecture for interoperation with Gn/Gp SGSN D.2.2 Non-roaming interoperation scenario In the non-roaming scenario the PLMN operates Gn/Gp 2G and/or 3G SGSNs as well as MME and S‑GW for E-UTRAN access. Intra PLMN roaming and inter access mobility between Gn/Gp 2G and/or 3G SGSNs and an MME/S‑GW are enabled by: - Gn functionality as specified between two Gn/Gp SGSNs, which is provided by the MME, and - Gn functionality as specified between Gn/Gp SGSN and Gn/Gp GGSN that is provided by the P‑GW. All this Gn functionality is based on GTP version 1 only. The architecture for interoperation with Gn/Gp SGSNs in the non-roaming case is illustrated in Figure D.2.2-1. Figure D.2.2-1: Non-roaming Architecture for interoperation with Gn/Gp SGSNs NOTE: If the Rel-7 SGSN applies Direct Tunnel there is a user plane connection between P‑GW and UTRAN. D.3 Interoperation procedures D.3.1 General The interoperation procedures describe information flows for Gn/Gp SGSNs and other EPS network elements. All messages between Gn/Gp SGSN and MME, between Gn/Gp SGSN and HSS and between Gn/Gp SGSN and P‑GW as well as the therein contained information elements are the same as specified for the adequate TS 23.060 [7] procedures that are between Gn/Gp SGSNs. These messages and procedure step descriptions are taken from TS 23.060 [7] for explanatory purposes only. These descriptions are in italic text and shall not be modified by the interoperation procedures. It cannot be assumed that the messages and procedure step descriptions that are taken from TS 23.060 [7] will be updated when modifications or corrections are performed for TS 23.060 [7]. If there are any discrepancies for these messages and procedure step descriptions TS 23.060 [7] takes precedence. The messages between the MME and any other node than the Gn/Gp SGSN as well as the therein contained information elements are the same as specified in the main body of this technical specification for the inter RAT Routing Area Update procedure. If there are any discrepancies for these messages the descriptions from the main body of this Technical Specification take precedence. An operator that has pre-Rel‑8 SGSNs in its network should use separate EPS bearers for IPv4 and IPv6 addressing, such that both addresses can be maintained when moving to a pre-Rel‑8 SGSN from a Rel‑8 SGSN or MME (see clause 5.3.1). This is configured into the SGSN and MME nodes which set the Dual Address Bearer Flag depending on whether a UE may or may not be handed over to a pre-Rel‑8 SGSN, as specified in clauses 5.3.2.1 and 5.10.2. An operator supporting emergency services shall not have pre-Rel-9 SGSNs in its network where a UE may be handed over. D.3.2 Void D.3.3 MME to 3G SGSN combined hard handover and SRNS relocation procedure The MME to 3G Gn/Gp SGSN Combined Hard Handover and SRNS Relocation procedure is illustrated in Figure D.3.3-1. Any steps descriptions that are from inter Gn/Gp SGSNs procedures of TS 23.060 [7] are shown as italic text and remain unmodified. In those step descriptions an MS stands for UE, old SGSN for old MME and GGSN for P‑GW. The procedure parts between E-UTRAN eNodeB and UE, and between E-UTRAN eNodeB and MME are compliant with the equivalent procedure parts in clause "5.5 Handover". If emergency bearer services are ongoing for the UE, handover to the target RNC is performed independent of the Handover Restriction List. The SGSN checks, as part of the Routing Area Update in the execution phase, if the handover is to a restricted area and if so SGSN deactivate the non-emergency PDP context as specified in TS 23.060 [7], clause 9.2.4.2. Figure D.3.3-1: MME to 3G SGSN combined hard handover and SRNS relocation procedure 1. The source eNodeB decides to initiate a handover to the target access network, UTRAN Iu mode. At this point both uplink and downlink user data is transmitted via the following: Bearer(s) between UE and source eNodeB, GTP tunnel(s) between source eNodeB, Serving GW and PDN GW. 2. The source eNodeB sends a Handover Required (S1AP Cause, Target RNC Identifier, Source to Target Transparent Container) message to the source MME to request the CN to establish resources in the target RNC and the target SGSN. The bearers that will be subject to data forwarding (if any) are identified by the new SGSN in a later step (see step 5 below). 3. The old MME sends a Forward Relocation Request message (IMSI, Tunnel Endpoint Identifier Signalling, MM Context, PDP Context, Target Identification, RAN Transparent Container, RANAP Cause, GCSI) to the new SGSN. For relocation to an area where Intra Domain Connection of RAN Nodes to Multiple CN Nodes is used, the old MME may have multiple new Gn/Gp SGSNs for each relocation target in a pool area, in which case the old MME will select one of them to become the new Gn/Gp SGSN, as specified in TS 23.236 [30]. PDP context contains GGSN Address for User Plane and Uplink TEID for Data (to this GGSN Address and Uplink TEID for Data, the Serving GW and the new SGSN send uplink packets). At the same time a timer is started on the MM and PDP contexts in the old MME (see Routing Area Update procedure in clause "Location Management Procedures (Iu mode)"). The old MME does not set any GCSI flag as the MME has no GPRS CAMEL Subscription Information. The S1AP Cause received from eNodeB is indicated as RANAP Cause. The Source to Target Transparent Container received from eNodeB is indicated as RAN Transparent Container. The MM context includes information on the EPS Bearer context(s). The old MME does not include any EPS Bearer Context information for "Non-IP" bearers, or for any SCEF connection, or for "Ethernet" bearers. If none of the MS's EPS Bearers can be supported by the selected new SGSN, the old MME rejects the handover attempt by sending a Handover Preparation Failure (Cause) message to the Source eNodeB. NOTE 1: If the handover is successful, the old MME will signal to the SGW and/or SCEF to release any non-included EPS Bearers after step 15. The non-included bearers are locally released by the MS following the PDP context status synchronisation that occurs during the Routing Area Update at step 17. NOTE 2: The GGSN user plane address and uplink TEID are the old P‑GW user plane address and TEID. The MME maps the EPS bearer parameters to PDP contexts. 4. The new SGSN sends a Relocation Request message (Permanent NAS UE Identity, Cause, CN Domain Indicator, Source RNC To Target RNC Transparent Container, RAB To Be Setup) to the target RNC. For each RAB requested to be established, RABs To Be Setup shall contain information such as RAB ID, RAB parameters, Transport Layer Address, and Iu Transport Association. SGSN shall not establish RABs for PDP contexts with maximum bitrate for uplink and downlink of 0 kbit/s. The list of RABs requested by the new SGSN may differ from list of RABs established in the Source RNC contained in the Source-RNC to target RNC transparent container. The target RNC should not establish the RABs (as identified from the Source-RNC to target RNC transparent container, Service Handover related information) that did not exist in the source RNC prior to the relocation. The RAB ID information element contains the NSAPI value, and the RAB parameters information element gives the QoS profile. The Transport Layer Address is the SGSN Address for user data, and the Iu Transport Association corresponds to the uplink Tunnel Endpoint Identifier Data. The new SGSN may decide to establish Direct Tunnel unless it has received a 'set' GCSI flag from the old SGSN. If the new SGSN decides to establish Direct Tunnel, it provides to the target RNC the GGSN's Address for User Plane and TEID for Uplink data. If the Access Restriction is present in the MM context, the Service Handover related information shall be included by the target SGSN for the Relocation Request message in order for RNC to restrict the UE in connected mode to handover to the RAT prohibited by the Access Restriction. After all the necessary resources for accepted RABs including the Iu user plane are successfully allocated, the target RNC shall send the Relocation Request Acknowledge message (Target RNC To Source RNC Transparent Container, RABs Setup, RABs Failed To Setup) to the new SGSN. Each RAB to be setup is defined by a Transport Layer Address, which is the target RNC Address for user data, and the Iu Transport Association, which corresponds to the downlink Tunnel Endpoint Identifier for user data. The transparent container contains all radio-related information that the MS needs for the handover, i.e. a complete RRC message (e.g., Physical Channel Reconfiguration in UTRAN case, or Handover From UTRAN, or Handover Command in GERAN Iu mode case) to be sent transparently via CN and source SRNC to the MS. For each RAB to be set up, the target RNC may receive simultaneously downlink user packets both from the source SRNC and from the new SGSN. NOTE 3: This step for the new SGSN is unmodified compared to pre-Rel-8. If the new SGSN decides to establish Direct Tunnel, it provides to the target RNC the P‑GW Address for User Plane and TEID for Uplink data. The UE acts as the MS; the old eNodeB acts as the source SRNC. 5. When resources for the transmission of user data between target RNC and new SGSN have been allocated and the new SGSN is ready for relocation of SRNS, the Forward Relocation Response (Cause, RAN Transparent Container, RANAP Cause, Target-RNC Information) message is sent from the new SGSN to the old SGSN. This message indicates that the target RNC is ready to receive from source SRNC the forwarded downlink PDUs, i.e., the relocation resource allocation procedure is terminated successfully. RAN transparent container and RANAP Cause are information from the target RNC to be forwarded to the source SRNC. The Target RNC Information, one information element for each RAB to be set up, contains the RNC Tunnel Endpoint Identifier and RNC IP address for data forwarding from the source SRNC to the target RNC. The Forward Relocation Response message is applicable only in the case of inter-SGSN SRNS relocation. NOTE 4: This step is unmodified compared to pre-Rel-8. The old MME acts as the old SGSN, and the source eNodeB as the source SRNC. 6. If 'Indirect Forwarding' applies the source MME sends a Create Indirect Data Forwarding Tunnel Request message (IMSI, MME Tunnel Endpoint Identifier for Control Plane, MME Address for Control plane, Target RNC Address and TEID(s) for DL user plane) to the Serving GW. 7. The Serving GW returns a Create Indirect Data Forwarding Tunnel Response (Cause, Serving GW DL TEID(s)) message to the source MME. If the Serving GW doesn't support data forwarding, an appropriate cause value shall be returned. 8. The source MME completes the preparation phase towards source eNodeB by sending the message Handover Command (Target to Source Transparent Container, Bearers Subject to Data Forwarding List, S1AP Cause). "Bearers Subject to Data forwarding list" may be included in the message and it shall be a list of 'Address(es) and TEID(s) for user traffic data forwarding' received from target side in the preparation phase (Step 5) in the case of direct forwarding or received from the Serving GW in the preparation phase (Step 7) in the case of indirect forwarding. RANAP Cause as received from new SGSN is indicated as S1AP Cause. RAN Transparent Container as received from new SGSN is indicated as Target to Source Transparent Container. 9. The source eNodeB initiates data forwarding for bearers specified in the "Bearers Subject to Data Forwarding List". The data forwarding may go directly to target RNC or alternatively go via the Serving GW if so decided by source MME in the preparation phase. 10. The source eNodeB will give a command to the UE to handover to the target access network via the message HO from E-UTRAN Command. This message includes a transparent container including radio aspect parameters that the target RNC has set-up in the preparation phase. The details of this E-UTRAN specific signalling are described in TS 36.300 [5]. 11. If the PLMN has configured Secondary RAT usage data reporting and the source eNodeB has Secondary RAT usage data to report, the eNodeB sends the RAN data report message (Secondary RAT usage data) to the MME. Since the handover is an inter-RAT handover, the MME continues with the Secondary RAT usage data reporting procedure as in clause 5.7A.3. The reporting procedure in clause 5.7A.3 is only performed if PGW secondary RAT usage reporting is active. NOTE 5: The source eNodeB does not send any RAN contexts towards the target RNC. 12. The target RNC shall send a Relocation Detect message to the new SGSN when the relocation execution trigger is received. For SRNS relocation type "UE Involved", the relocation execution trigger may be received from the Uu interface; i.e., when target RNC detects the MS on the lower layers. When the Relocation Detect message is sent, the target RNC shall start SRNC operation. NOTE 6: This step is unmodified compared to pre-Rel-8. 13. When the MS has reconfigured itself, it sends an RRC message e.g., a Physical Channel Reconfiguration Complete message to the target SRNC. The UE locally deactivates ISR by setting its TIN from "RAT-related TMSI" to "GUTI", if any EPS bearer context activated after the ISR was activated in the UE exists. 14. When the target SRNC receives the appropriate RRC message, e.g. Physical Channel Reconfiguration Complete message or the Radio Bearer Release Complete message in UTRAN case, or the Handover To UTRAN Complete message or Handover Complete message in GERAN case, i.e. the new SRNC‑ID + S‑RNTI are successfully exchanged with the MS by the radio protocols, the target SRNC shall initiate a Relocation Complete procedure by sending the Relocation Complete message to the new SGSN. The purpose of the Relocation Complete procedure is to indicate by the target SRNC the completion of the relocation of the SRNS to the CN. NOTE 7: This step is unmodified compared to pre-Rel-8. The UE acts as the MS. 15. Upon receipt of Relocation Complete message, if the SRNS Relocation is an inter SGSN SRNS relocation, the new SGSN signals to the old SGSN the completion of the SRNS relocation procedure by sending a Forward Relocation Complete message. A timer in source MME is started to supervise when resources in Source eNodeB and Source Serving GW shall be released. For all bearers that were not included in the Forward Relocation Request message sent in step 3, the MME now releases them by sending a Delete Bearer Command to the SGW, or, the appropriate message to the SCEF. NOTE 8: For the SGSN this step is unmodified compared to pre-Rel-8. The old MME acts as the old SGSN, and the source eNodeB as the source SRNC. 16. Upon receipt of the Relocation Complete message, the CN shall switch the user plane from the source RNC to the target SRNC. If the SRNS Relocation is an inter-SGSN SRNS relocation or if Direct Tunnel was established in intra-SGSN SRNS relocation, the new SGSN sends Update PDP Context Request messages (new SGSN Address, SGSN Tunnel Endpoint Identifier, QoS Negotiated, serving network identity, CGI/SAI, User CSG Information, RAT type, MS Info Change Reporting support indication, NRSN, DTI) to the GGSNs concerned. The SGSN shall send the serving network identity to the GGSN. If Direct Tunnel is established the SGSN provides to GGSN the RNC's Address for User Plane and TEID for Downlink data and shall include the DTI to instruct the GGSN to apply Direct Tunnel specific error handling procedure as described in clause 13.8. NRSN indicates SGSN support of the network requested bearer control. The GGSNs update their PDP context fields and return an Update PDP Context Response (GGSN Tunnel Endpoint Identifier, Prohibit Payload Compression, APN Restriction, MS Info Change Reporting Action, CSG Information Reporting Action, BCM) message. The Prohibit Payload Compression indicates that the SGSN should negotiate no data compression for this PDP context. The PDN GW shall include a Charging Id to be used at the SGSN as the Charging Id for reporting usage for this PDP context. The PDN GW shall include the Charging Id in the offline charging data. NOTE 9: This step is unmodified compared to pre-Rel-8. The P‑GW acts as the GGSN. 17. After the MS has finished the reconfiguration procedure and if the new Routing Area Identification is different from the old one or if the MS' TIN indicates "GUTI", the MS initiates the Routing Area Update procedure. See clause "Location Management Procedures (Iu mode)". For a MS supporting CIoT EPS Optimisations, the MS uses the PDP context status information in the RAU Accept to identify any non-transferred bearers that it shall locally release. NOTE 10: It is only a subset of the RA update procedure that is performed, since the MS is in PMM‑CONNECTED state. NOTE 11: This step is unmodified compared to pre-Rel-8. The UE acts as the MS. The old EPS bearer information in old MME and Serving GW is removed as part of the Routing Area Update procedure. 18. When the timer started in step 15 expires, the source MME deletes the EPS bearer resources by sending Delete Session Request (Cause, Operation Indication, Secondary RAT usage data) messages to the Serving GW because the new SGSN is a Gn/Gp SGSN, which is derived from using GTPv1 for relocation signalling between new Gn/Gp SGSN and old MME. The new Gn/Gp SGSN does not signal any Serving GW change. The operation Indication flag is not set, that indicates to the Serving GW that the Serving GW shall not initiate a delete procedure towards the PDN GW. Secondary RAT usage data was included if it was received in step 11a. The Source Serving GW acknowledges with Delete Session Response (Cause) messages. If ISR is activated the cause indicates to the old S‑GW that the old S‑GW shall delete the bearer resources on the other old CN node by sending Delete Bearer Request message(s) to that CN node. If resources for indirect forwarding have been allocated then these are released. When the timer started in step 15 expires, the source MME sends a Release Resources message to the source eNodeB. When the Release Resources message has been received and there is no longer any need for the eNodeB to forward data, the source eNodeB releases its resources. If the SRNS Relocation is inter-SGSN, then the following CAMEL procedure calls shall be performed (see referenced procedures in TS 23.078 [29]) NOTE 12: The C1 CAMEL procedure call was omitted intentionally from this procedure since EPS does not support CAMEL procedure calls. The other CAMEL procedure calls are unmodified compared to pre-Rel‑8. The new SGSN shall determine the Maximum APN restriction based on the received APN Restriction of each PDP context from the GGSN and then store the new Maximum APN restriction value. If the SRNS Relocation is intra-SGSN, then the above mentioned CAMEL procedures calls shall not be performed. If Routing Area Update occurs, the SGSN shall determine whether Direct Tunnel can be used based on the received GPRS CAMEL Subscription Information. If Direct Tunnel can not be maintained the SGSN shall re-establish RABs and initiate the Update PDP Context procedure to update the IP Address and TEID for Uplink and Downlink data. If Routing Area Update occurs, then the following CAMEL procedure calls shall be performed (see referenced procedures in TS 23.078 [29]): C2) CAMEL_GPRS_Routing_Area_Update_Session and CAMEL_PS_Notification. They are called in the following order: - The CAMEL_GPRS_Routing_Area_Update_Session procedure is called. The procedure returns as result "Continue". - Then the CAMEL_PS_Notification procedure is called. The procedure returns as result "Continue". C3) CAMEL_GPRS_Routing_Area_Update_Context. This procedure is called several times: once per PDP context. It returns as result "Continue". For C2 and C3: refer to Routing Area Update procedure description for detailed message flow. NOTE 13: Handover Reject is performed as defined in clause 5.5.2.1.4, excluding steps 4 and 7. D.3.4 3G SGSN to MME combined hard handover and SRNS relocation procedure The 3G Gn/Gp SGSN to MME Combined Hard Handover and SRNS Relocation procedure is illustrated in Figure D.3.4-1. Any steps descriptions that are from TS 23.060 [7] are shown as italic text and remain unmodified. In those step descriptions an MS stands for UE, new SGSN for new MME and GGSN for P‑GW. The procedure between E-UTRAN eNodeB and UE, and between E-UTRAN eNodeB and MME are compliant with the equivalent procedure parts in clause 5.5: Handover. If emergency bearer services are ongoing for the UE, the MME checks as part of the Tracking Area Update in the execution phase, if the handover is to a restricted area and if so MME releases the non-emergency bearers as specified in clause 5.10.3. Figure D.3.4-1: 3G Gn/Gp SGSN to MME combined hard handover and SRNS relocation procedure 1. The source RNC decides to initiate a handover to E-UTRAN. 2. The source SRNC sends a Relocation Required message (Relocation Type, Cause, Source ID, Target ID, Source RNC To Target RNC Transparent Container) to the old SGSN. The source SRNC shall set Relocation Type to "UE Involved". Source RNC To Target RNC Transparent Container includes the necessary information for relocation co‑ordination, security functionality and RRC protocol context information (including MS Capabilities). NOTE 1: This step is unmodified compared to pre-Rel-8. The target eNodeB acts as the target RNC. NOTE 1a: The Target ID identifies an eNodeB. With Rel-8 Iu functionality this is an eNodeB ID. As an implementations option for supporting introduction scenarios with pre-Rel8 SGSNs the source RNC may be configured to use RNC IDs instead of eNodeB IDs to identify a target eNodeB. The Cause is relayed transparently by the SGSN to the MME and the MME maps RANAP cause code to an S1AP cause code. Source RNC to Target RNC Transparent Container carries information for the target eNodeB. This container is relayed transparently by the SGSN. 3. The old SGSN determines from the Target ID if the SRNS relocation is intra-SGSN SRNS relocation or inter-SGSN SRNS relocation. In the case of inter-SGSN SRNS relocation the old SGSN initiates the relocation resource allocation procedure by sending a Forward Relocation Request message (IMSI, Tunnel Endpoint Identifier Signalling, MM Context, PDP Context, Target Identification, RAN Transparent Container, RANAP Cause, GCSI) to the new SGSN. For relocation to an area where Intra Domain Connection of RAN Nodes to Multiple CN Nodes is used, the old SGSN may – if it provides Intra Domain Connection of RAN Nodes to Multiple CN Nodes -have multiple target SGSNs for each relocation target in a pool area, in which case the old SGSN will select one of them to become the new SGSN, as specified in TS 23.236 [30]. PDP context contains GGSN Address for User Plane and Uplink TEID for Data (to this GGSN Address and Uplink TEID for Data, the old SGSN and the new SGSN send uplink packets). At the same time a timer is started on the MM and PDP contexts in the old SGSN (see Routing Area Update procedure in clause "Location Management Procedures (Iu mode)"). The Forward Relocation Request message is applicable only in the case of inter-SGSN SRNS relocation. The old SGSN 'sets' the GCSI flag if the MM context contains GPRS CAMEL Subscription Information. NOTE 2: This step is unmodified compared to pre-Rel-8. The new MME acts as the new SGSN, and the P‑GW as the GGSN. The GGSN user plane address and uplink TEID are the P‑GW user plane address and TEID. The MME maps the PDP context parameters to EPS bearers. 4. The MME selects a Serving GW and sends a Create Session Request (bearer context(s) with PDN GW addresses and TEIDs for uplink traffic, APN-AMBR, Serving Network, UE Time Zone) message per PDN connection to the target Serving GW. For relocation from Gn/Gp SGSN, the target MME provides the APN-AMBR if not received explicitly from the Gn/Gp SGSN based on the mapping from MBR (as specified in Annex E) to the Serving GW. 5. The Serving GW allocates the S‑GW addresses and TEIDs for the uplink traffic on S1_U reference point (one TEID per bearer). The target Serving GW sends a Create Session Response (Serving GW addresses and uplink TEID(s) for user plane) message back to the target MME. 6. The new MME requests the target eNodeB to establish the bearer(s) by sending the message Handover Request (UE Identifier, S1AP Cause, CN Domain Indicator, KeNB, NAS Security Parameters to E-UTRAN, EPS Bearers to be setup list, Source to Target Transparent Container, Serving GW Address(es) and TEID(s) for User Traffic Data, Handover Restriction List). S1AP Cause indicates the RANAP Cause as received from SGSN. Source to Target Transparent Container contains the RAN Transparent Container as received from SGSN. The NAS Security Parameters to E‑UTRAN includes the NAS Integrity Protection and Ciphering algorithm(s), eKSI and NONCEMME information elements. Handover Restriction List is sent if it is available in the Target MME; it is described in clause 4.3.5.7. If the MME did not receive the UE Network Capability information from the old SGSN, then the MME will not have received information on the E-UTRAN Integrity Protection and Encryption algorithms that the UE supports. In this case, the MME can assume that the UE supports both EIA1/EEA1 and EIA2/EEA2. NOTE 3: The MME derives K'ASME from CK and IK in the MM context and associates it with eKSI, as described in TS 33.401 [41] and selects NAS Integrity Protection and Ciphering algorithms(s). eKSI and key derivation parameters are targeted for UE. The MME and UE derive the NAS keys and KeNB from K'ASME. If the MME shares an EPS security association with the UE, the MME may activate this native EPS security context by initiating a NAS SMC procedure after having completed the handover procedure. The MME shall not request the target eNodeB to establish EPS GBR bearers with maximum bitrate set to 0 and those EPS bearers should not be included in the EPS Bearers to be setup list and should be deactivated by the MME. For the remaining EPS Bearer Contexts the MME ignores any Activity Status Indicator within an EPS Bearer Context and requests the target eNodeB to allocate resources for all the remaining EPS Bearer Contexts. The MME shall compute the UE-AMBR, according to clause 4.7.3, based on explicit APN-AMBR values received from the Gn/Gp SGSN. If explicit APN-AMBR values are not received by the MME, a local UE-AMBR shall be included in the 'EPS Bearers be setup list ' IE. The local UE-AMBR is described in clause Annex E. "Data forwarding not possible" indication per bearer shall be included in the 'EPS Bearers to be setup list' if the target MME decides the corresponding bearer will not be subject to data forwarding. NOTE 4: The MME derives the security parameters from the security parameters received from the SGSN. NOTE 5: An MME that supports handovers from pre-Rel-8 3G SGSNs derives from the RNC ID received from old SGSN an eNodeB address. 7. The target eNodeB allocates the requested resources and returns the applicable parameters to the target MME in the message Handover Request Acknowledge (Target to Source Transparent Container, EPS Bearers setup list, EPS Bearers failed to setup list, Cause). The target eNodeB shall ignore it if the number of radio bearers in the Source to Target Transparent container does not comply with the number of bearers requested by the MME and allocate bearers as requested by the MME. The target eNodeB inserts the information provided by the MME (KSI, selected NAS Integrity Protection and Ciphering algorithm(s), NONCEMME) and selected AS integrity and ciphering algorithm(s) into the UTRAN RRC message, which is contained in the Target to Source Transparent Container. 8. If 'Indirect Forwarding' and relocation of Serving GW apply the target MME sends a Create Indirect Data Forwarding Tunnel Request message (IMSI, MME Tunnel Endpoint Identifier for Control Plane, MME Address for Control plane, Target eNodeB Address and TEID(s) for DL user plane) to the Serving GW. The allocation of a new Serving GW by steps 4 and 5 the MME shall consider as a Serving GW change. 9. The Serving GW returns a Create Indirect Data Forwarding Tunnel Response (Cause, Serving GW DL TEID(s)) message to the source MME. If the Serving GW doesn't support data forwarding, an appropriate cause value shall be returned. 10. When resources for the transmission of user data between target RNC and new SGSN have been allocated and the new SGSN is ready for relocation of SRNS, the Forward Relocation Response (Cause, RAN Transparent Container, RANAP Cause, Target-RNC Information) message is sent from the new SGSN to the old SGSN. This message indicates that the target RNC is ready to receive from source SRNC the forwarded downlink PDUs, i.e., the relocation resource allocation procedure is terminated successfully. RAN transparent container and RANAP Cause are information from the target RNC to be forwarded to the source SRNC. The Target RNC Information, one information element for each RAB to be set up, contains the RNC Tunnel Endpoint Identifier and RNC IP address for data forwarding from the source SRNC to the target RNC. The Forward Relocation Response message is applicable only in the case of inter-SGSN SRNS relocation. For each RAB, if the MME has determined no Data forwarding, i.e. the data forwarding from the source RNC to the target eNodeB is not required, the MME indicates the reserved TEID and IP address parameters to the old SGSN in the Target RNC Information. The packets received on that reserved TEID and IP address are discarded. NOTE 6: The new MME acts as the new SGSN, and the target eNodeB as the target SRNC. RANAP Cause indicates the Cause as received from target eNodeB. RAN Transparent Container contains the Target to Source Transparent Container as received from eNodeB. 11. The old SGSN continues the relocation of SRNS by sending a Relocation Command message (Target RNC To Source RNC Transparent Container, RABs To Be Released, RABs Subject To Data Forwarding) to the source SRNC. The old SGSN decides the RABs to be subject for data forwarding based on QoS, and those RABs shall be contained in RABs subject to data forwarding. For each RAB subject to data forwarding, the information element shall contain RAB ID, Transport Layer Address, and Iu Transport Association. These are the same Transport Layer Address and Iu Transport Association that the target RNC had sent to new SGSN in Relocation Request Acknowledge message, and these are used for forwarding of downlink N‑PDU from the source SRNC to the target RNC. The source SRNC is now ready to forward downlink user data directly to the target RNC over the Iu interface. This forwarding is performed for downlink user data only. NOTE 7: This step is unmodified compared to pre-Rel-8. The target eNodeB acts as the target RNC, and the new MME acts as the new SGSN. The forwarding of downlink user data from source SRNC may go directly to target eNodeB or via the Serving GW. 12. The source SRNC may, according to the QoS profile, begins the forwarding of data for the RABs to be subject for data forwarding. NOTE 8: The order of steps, starting from step 7 onwards, does not necessarily reflect the order of events. For instance, source RNC may start data forwarding (step 7), send the RRC message to MS (step 8) and forward SRNS Context message to the old SGSN (step 9) almost simultaneously. The data forwarding at SRNS relocation shall be carried out through the Iu interface, meaning that the GTP-PDUs exchanged between the source SRNC and the target RNC are duplicated in the source SRNC and routed at the IP layer towards the target RNC. For each radio bearer which uses lossless PDCP the GTP-PDUs related to transmitted but not yet acknowledged PDCP-PDUs are duplicated and routed at IP layer towards the target RNC together with their related downlink PDCP sequence numbers. The source RNC continues transmitting duplicates of downlink data and receiving uplink data. Before the serving RNC role is not yet taken over by target RNC and when downlink user plane data starts to arrive to target RNC, the target RNC may buffer or discard arriving downlink GTP-PDUs according to the related QoS profile. NOTE 9: This step is unmodified compared to pre-Rel-8. The target eNodeB acts as the target SRNC. The data forwarding may go directly to target eNodeB or alternatively go via the Serving GW if so decided by new MME in the preparation phase. 13. Before sending the RRC message the uplink and downlink data transfer shall be suspended in the source SRNC for RABs, which require delivery order. The RRC message is for example Physical Channel Reconfiguration for RNS to RNS relocation, or Intersystem to UTRAN Handover for BSS to RNS relocation, or Handover from UTRAN Command for BSS relocation, or Handover Command for BSS to BSS relocation. When the source SRNC is ready, the source RNC shall trigger the execution of relocation of SRNS by sending to the MS the RRC message provided in the Target RNC to source RNC transparent container, e.g., a Physical Channel Reconfiguration (UE Information Elements, CN Information Elements) message. UE Information Elements include among others new SRNC identity and S‑RNTI. CN Information Elements contain among others Location Area Identification and Routing Area Identification. When the MS has reconfigured itself, it sends an RRC message e.g., a Physical Channel Reconfiguration Complete message to the target SRNC. If the Forward SRNS Context message with the sequence numbers is received, the exchange of packets with the MS may start. If this message is not yet received, the target RNC may start the packet transfer for all RABs, which do not require maintaining the delivery order. NOTE 10: This step is unmodified compared to pre-Rel-8. This text is valid for the RRC message sent from source RNC to the UE. When the UE has got access to target eNodeB it sends the HO to E-UTRAN Complete message. This RRC message received as part of Target to Source Transparent Container, includes information about the selected security algorithms and related key information. Based on this information, the UE selects the same algorithms for the NAS if the KSI value indicates that the MME has no security association with the UE. If the KSI value indicates that the MME has a security association with the UE, but the UE has lost the security context of the E-UTRAN side (error case), the UE will start Attach procedure on the E-UTRAN side 14. There is no RAN context transfer during inter RAT handovers with E-UTRAN. If the source RNC originates any SRNC contexts the MME acknowledges the receipt towards the SGSN and ignores the message content. NOTE 11: This step is unmodified compared to pre-Rel-8. The new MME acts as the new SGSN, and the target eNodeB as the target SRNC. 15. When the UE has successfully accessed the target eNodeB, the target eNodeB informs the target MME by sending the message Handover Notify (TAI+ECGI). The UE shall implicitly derive the EPS bearers for which an E-RAB was not established from the HO from UTRAN Command and deactivate them locally without an explicit NAS message at this step. If Dual Connectivity is activated for the UE, the PSCell ID shall be included in the Handover Notify message. 16. Upon receipt of Handover Notify message, if the SRNS Relocation is an inter SGSN SRNS relocation, the new SGSN signals to the old SGSN the completion of the SRNS relocation procedure by sending a Forward Relocation Complete message. Upon receipt of the Relocation Complete message the new MME starts a timer. NOTE 12: This step is unmodified compared to pre-Rel-8 except that the Handover Notify message is received instead of a Relocation Complete message. The new MME acts as the new SGSN. 17. The target MME will now complete the handover procedure by informing the Serving GW that the target MME is now responsible for all the bearers the UE have established. This is performed in the message Modify Bearer Request (Cause, Tunnel Endpoint Identifier Control Plane, MME Address for Control Plane, eNodeB Address(es) and TEID(s) for User Traffic, RAT type, APN-AMBR, User Location Information, PSCell ID) per PDN connection. If the PDN GW requested UE's location information and/or User CSG information (determined from the UE context), the MME also includes the User Location Information IE and/or User CSG Information IE in this message. If the UE Time Zone has changed, the MME includes the UE Time Zone IE in this message. If the MME has received PSCell ID in step 15, the MME shall include it in this message. The MME releases the non-accepted bearers by triggering the bearer release procedure as specified in clause 5.4.4.2. If the Serving GW receives a DL packet for a non-accepted bearer, the Serving GW drops the DL packet and does not send a Downlink Data Notification to the MME. 18. The Serving GW informs the PDN GW the APN-AMBR and the change of for example the RAT type that e.g. can be used for charging, by sending the message Modify Bearer Request (APN-AMBR, Serving Network, PDN Charging Pause Support Indication) per PDN connection. The S‑GW also includes User Location Information IE and/or UE Time Zone IE and/or User CSG Information IE if it is present in step 17. The Serving GW allocates DL TEIDs on S5/S8 even for non-accepted bearers. The PDN GW must acknowledge the request with the message Modify Bearer Response (Default bearer id, APN Restriction, PDN Charging Pause Enabled Indication (if PDN GW has chosen to enable the function)). When the UE moves from Gn/Gp SGSN to the MME, the PDN GW shall send the APN restriction of each bearer context to the Serving GW. 19. The Serving GW acknowledges the user plane switch to the target MME via the message Modify Bearer Response (Cause, Tunnel Endpoint Identifier Control Plane, Serving GW Address for Control Plane, Default bearer id, APN restriction). The Serving GW shall forward the received APN Restriction to the MME. At this stage the user plane path is established for all bearers between the UE, target eNodeB, Serving GW and PDN GW. 20. Upon receiving the Relocation Complete message or, if it is an inter-SGSN SRNS relocation, the Forward Relocation Complete message, the old SGSN sends an Iu Release Command message to the source RNC. When the RNC data-forwarding timer has expired, the source RNC responds with an Iu Release Complete message. NOTE 13: This step is unmodified compared to pre-Rel-8. 21. The UE initiates a Tracking Area Update procedure when one of the conditions listed in clause "Triggers for tracking area update" applies. The target MME knows that an IRAT Handover has been performed for this UE as it received the bearer context(s) by handover messages and therefore the target MME performs only a subset of the TA update procedure, specifically it excludes the context transfer procedures between source SGSN and target MME. The target MME gets the subscribed UE-AMBR value and the subscribed APN-AMBR value from the HSS during the TA update procedure. If the Subscription Data received from the HSS (during the TAU) contains information that is necessary for the E-UTRAN to be aware of (e.g. a restriction in the UE's permission to use NR as a secondary RAT, Unlicensed Spectrum in the form of LAA/LWA/LWIP/NR-U (as specified in clause 4.3.30) or a combination of them), or an existing UE context in the MME indicates that the UE is not permitted to use NR as a secondary RAT, Unlicensed Spectrum or a combination of them, and the MME has not provided this information to the target eNodeB during step 6 (the Handover Request), then the MME sends an updated Handover Restriction List in the Downlink NAS Transport message that it sends to E-UTRAN. 22. The target MME calculates UE-AMBR as defined in clause 4.7.3. If this calculated value is different from the UE-AMBR computed during step 6, or the APN-AMBR mapped from the subscribed MBR is different from the subscribed APN-AMBR, or the mapped subscribed QoS profile (i.e. the subscribed QoS profile mapped according to Annex E) of the default bearer is different from the EPS Subscribed QoS profile received from the HSS, the new MME shall initiate Subscribed QoS Modification procedure as described in clause 5.4.2.2, Figure 5.4.2.2-1. 23. When the timer started in step 16 expires the new MME releases the resources that have been allocated for indirect forwarding. If the SRNS Relocation is inter-SGSN, then the following CAMEL procedure calls shall be performed (see referenced procedures in TS 23.078 [29]) C1) CAMEL_GPRS_PDP_Context_Disconnection, CAMEL_GPRS_Detach and CAMEL_PS_Notification. They are called in the following order: - The CAMEL_GPRS_PDP_Context_Disconnection procedure is called several times: once per PDP context. The procedure returns as result "Continue". - Then the CAMEL_GPRS_Detach procedure is called once. The procedure returns as result "Continue". - Then the CAMEL_PS_Notification procedure is called once. The procedure returns as result "Continue". The new SGSN shall determine the Maximum APN restriction based on the received APN Restriction of each PDP context from the GGSN and then store the new Maximum APN restriction value. If the SRNS Relocation is intra-SGSN, then the above mentioned CAMEL procedures calls shall not be performed. If Routing Area Update occurs, the SGSN shall determine whether Direct Tunnel can be used based on the received GPRS CAMEL Subscription Information. If Direct Tunnel can not be maintained the SGSN shall re-establish RABs and initiate the Update PDP Context procedure to update the IP Address and TEID for Uplink and Downlink data. If Routing Area Update occurs, then the following CAMEL procedure calls shall be performed (see referenced procedures in TS 23.078 [29]): NOTE 14: This CAMEL handling is unmodified compared to pre-Rel-8. NOTE 15: CAMEL procedure calls C2 and C3 were omitted intentionally from this procedure since EPS does not support CAMEL procedure calls. NOTE 16: Handover Reject procedure is performed as defined in clause 5.5.2.2.4. D.3.5 Routing Area Update The Routing Area Update procedure takes place when a UE that is registered with an MME selects a UTRAN or GERAN cell served by a Gn/Gp SGSN. In this case, the UE changes to a Routing Area that the UE has not yet registered with the network. This procedure is initiated by an idle state or by a connected state UE. The Routing Area Update procedure is illustrated in Figure D.3.5-1. Any step descriptions that are taken from TS 23.060 [7] for a Gn/Gp SGSN are shown as italic text and remain unmodified. In that step descriptions an MS stands for UE, old SGSN for old MME and GGSN for P‑GW. The old MME behaves towards the new Gn/Gp SGSN always like an old Gn/Gp 3G-SGSN, regardless of whether the new Gn/Gp SGSN is a 2G-SGSN or a 3G-SGSN. Figure D.3.5-1: Routing Area Update procedure 0. The UE selects a UTRAN or GERAN cell. This cell is in a Routing Area that the UE not yet registered with the network or the UE reselects a UTRAN or GERAN cell and the TIN indicates "GUTI". The UE in ECM‑CONNECTED state may change to the GERAN cell through Network Assisted Cell Change (NACC). 1. The MS sends a Routing Area Update Request (old P‑TMSI, old RAI, old P‑TMSI Signature, Update Type, follow on request, Classmark, MS Network Capability, additional P‑TMSI/RAI, KSI) to the new SGSN. Update Type shall indicate RA update, periodic RA update, Combined RA / LA Update or Combined RA / LA Update with IMSI attach requested. The BSS shall add the Cell Global Identity including the RAC and LAC of the cell where the message was received before passing the message to the SGSN. The SRNC shall add the Routing Area Identity before forwarding the message to the 3G-SGSN. Classmark contains the MS GPRS multislot capabilities and supported GPRS ciphering algorithms as defined in TS 24.008 [47]. The SGSN may use, as an implementation option, the follow-on request indication to release or keep the Iu connection after the completion of the RA update procedure. If the UE's TIN indicates "GUTI" and the UE holds a valid GUTI then the UE indicates the GUTI as the old P‑TMSI and old RAI. If the UE's TIN indicates "P‑TMSI" or "RAT‑related TMSI" and the UE holds a valid P‑TMSI and related RAI then these two elements are indicated as old P‑TMSI and old RAI. Mapping a GUTI to a P‑TMSI and an RAI is specified in TS 23.003 [9]. If the UE holds a valid P‑TMSI and related RAI and the old P-TMSI and old RAI indicate a P-TMSI/RAI mapped from a GUTI, then the UE indicates these parameters as additional P‑TMSI/RAI. The Gn/Gp SGSN shall ignore this additional P‑TMSI/RAI. The old P‑TMSI is indicated in the RAU Request message for Iu‑mode only. For Gb mode the TLLI is derived from the value that is determined as the old P‑TMSI according to the rules above. The routing parameter that is signalled in the RRC signalling to the RNC for routing to the SGSN is derived from the identifier that is signalled as the old P‑TMSI according to the rules above. For a combined MME/SGSN the RAN is configured to route the NRI(s) of this combined node to the same combined node. The RAN is also configured to route NRI(s) of P‑TMSIs that are generated by the UE's mapping of the GUTIs allocated by the combined node. Such a RAN configuration may also be used for separate nodes to avoid changing nodes in the pool caused by inter RAT mobility. KSI is mapped from an eKSI identifying a KASME if the UE indicates a P‑TMSI mapped from GUTI in the information element "old P‑TMSI". KSI identifies a (CK, IK) pair if the UE indicates a P‑TMSI in the information element "old P‑TMSI". 2. The new SGSN sends SGSN Context Request (old RAI, TLLI or old P-TMSI, old P‑TMSI Signature, New SGSN Address) to the old SGSN to get the MM and PDP contexts for the MS. If the new SGSN provides functionality for Intra Domain Connection of RAN Nodes to Multiple CN Nodes, the new SGSN may derive the old SGSN from the old RAI and the old P-TMSI (or TLLI) and send the SGSN Context Request message to this old SGSN. Otherwise, the new SGSN derives the old SGSN from the old RAI. In any case the new SGSN will derive an SGSN that it believes is the old SGSN. This derived SGSN is itself the old SGSN, or it is associated with the same pool area as the actual old SGSN and it will determine the correct old SGSN from the P-TMSI (or TLLI) and relay the message to that actual old SGSN. NOTE 2: A GUTI mapped to a P-TMSI/RAI provides an old RAI that uniquely identifies an old MME then there is no need to relay between MME in the old pool, regardless whether the new SGSN supports such functionality or not. Mapping a GUTI to a P‑TMSI and an RAI is specified in Annex H. The old SGSN validates the old P‑TMSI Signature and responds with an appropriate error cause if it does not match the value stored in the old SGSN. This should initiate the security functions in the new SGSN. If the security functions authenticate the MS correctly, the new SGSN shall send an SGSN Context Request (old RAI, TLLI, MS Validated, New SGSN Address) message to the old SGSN. MS Validated indicates that the new SGSN has authenticated the MS. If the old P‑TMSI Signature was valid or if the new SGSN indicates that it has authenticated the MS, the old SGSN starts a timer. If the MS is not known in the old SGSN, the old SGSN responds with an appropriate error cause. If the UE with emergency bearers is not authenticated in the old MME (in a network supporting unauthenticated UEs) the old MME continues the procedure with sending a Context Response and starting the timer also when it cannot validate the Context Request. If the UE uses power saving functions and the old MME indicates Buffered DL Data Waiting, the new SGSN invokes data forwarding and user plane setup corresponding to clause 5.3.3.1A. NOTE 3: For the new SGSN, this step is unmodified compared to pre-Rel-8. The MME (called old SGSN in above description) needs to provide SGSN functionality. 2b. The old 3G SGSN responds with an SGSN Context Response (MM Context, PDP Contexts) message. For each PDP context the old 3G-SGSN shall include the GTP sequence number for the next uplink GTP PDU to be tunnelled to the GGSN and the next downlink GTP sequence number for the next PDU to be sent to the MS. Each PDP Context also includes the PDCP sequence numbers if PDCP sequence numbers are received from the old SRNS. The new 3G-SGSN shall ignore the MS Network Capability contained in MM Context of SGSN Context Response only when it has previously received an MS Network Capability in the Routing Area Request. The GTP sequence numbers received from the old 3G-SGSN are only relevant if delivery order is required for the PDP context (QoS profile). NOTE 4: This step is for the Gn/Gp SGSN unmodified compared to pre-Rel-8. The MME (old SGSN in this step) maps EPS bearers one-to-one to PDP contexts and provides the Release 99 parameters of the bearer QoS profile to the new SGSN. The Gn signalling between the new Gn/Gp SGSN and the old CN node has no capabilities to indicate ISR Activated or ISR Supported. The GTP and PDCP sequence numbers are not relevant as the network does not configure usage of "delivery order required" and does not configure loss less UTRAN PDCP as described in clause "compatibility issues". For UE using CIoT EPS Optimisation without any activated PDN connection, there is no PDP Context(s) included in the SGSN Context Response message. The MME (old SGSN in this step) only transfers the PDP Context(s) that the new SGSN supports. If not supported, PDP Context(s) of non-IP PDN connection are not transferred to the new SGSN. PDP Context(s) of Ethernet PDN connection are not transferred to the new SGSN. If the PDP Context(s) of a PDN connection has not been transferred, the MME shall consider all bearers of that PDN connection as failed and release that PDN connection by triggering the MME requested PDN disconnection procedure specified in clause 5.10.3. 3. Security functions may be executed. These procedures are defined in clause "Security Function" in TS 23.060 [7]. Ciphering mode shall be set if ciphering is supported. If the SGSN Context Response message did not include IMEISV and ADD is supported by the SGSN, the SGSN retrieves the IMEISV from the MS. If the security functions fail (e.g. because the SGSN cannot determine the HLR address to establish the Send Authentication Info dialogue), the Inter SGSN RAU Update procedure fails. A reject shall be returned to the MS with an appropriate cause. NOTE 5: This step is unmodified compared to pre-Rel-8. 4. The new SGSN sends an SGSN Context Acknowledge message to the old SGSN. The old MME (which is the old SGSN from the new SGSN's point of view) marks in its context that the information in the GWs and the HSS are invalid. This triggers the GWs, and the HSS to be updated if the UE initiates a Tracking Area Update procedure back to the old MME before completing the ongoing Routing Area Update procedure. If the security functions do not authenticate the MS correctly, then the routing area update shall be rejected, and the new SGSN shall send a reject indication to the old SGSN. The old MME shall continue as if the SGSN Context Request was never received. NOTE 6: The new SGSN's operation is unmodified compared to pre-Rel-8. The old MME/S-GW (old SGSN from the new SGSN's point of view) does not forward any data towards the new SGSN. 5. Void. 6. The new SGSN sends Update PDP Context Request (new SGSN Address, TEID, QoS Negotiated, serving network identity, CGI/SAI, User CSG Information, RAT type, MS Info Change Reporting support indication, NRSN) to the GGSNs concerned. The SGSN shall send the serving network identity to the GGSN. NRSN indicates SGSN support of the network requested bearer control. The SGSN shall only indicate that it supports the procedure if it supports it and it is indicated that the MS also supports it in the SGSN Context Response message as described above. If the NRSN is not included in the Update PDP Context Request message the GGSN shall, following this procedure, perform a GGSN-Initiated PDP Context Modification to change the BCM to 'MS-Only' for all PDP-Address/APN-pairs for which the current BCM is 'MS/NW'. The GGSNs update their PDP context fields and return Update PDP Context Response (TEID, Prohibit Payload Compression, APN Restriction, MS Info Change Reporting Action, CSG Information Reporting Action, BCM). The Prohibit Payload Compression indicates that the SGSN should negotiate no data compression for this PDP context. NOTE 9: This step is unmodified compared to pre-Rel-8. For UE using CIoT EPS Optimisation without any activated PDN connection, the steps 6 and 13 are skipped. 7. The new SGSN informs the HLR of the change of SGSN by sending Update Location (SGSN Number, SGSN Address, IMSI, IMEISV, Update Type, Homogenous Support of IMS Voice over PS Sessions) to the HLR. IMEISV is sent if the ADD function is supported. Update Type indicates "normal update". For "Homogenous Support of IMS Voice over PS Sessions", see clause 5.3.8A of TS 23.060 [7]. NOTE 10: This step is unmodified compared to pre-Rel-8. Clarification about update type added to show that this is the trigger for the HSS to cancel only an old SGSN and not also an old MME. 8. The HLR sends Cancel Location (IMSI, Cancellation Type) to any old SGSN with Cancellation Type set to Update Procedure. The old SGSN removes the MM and EPS bearer contexts. The old SGSN acknowledges with Cancel Location Ack (IMSI). NOTE 11: For the Gn/Gp SGSN the HSS interoperation is unmodified compared to earlier standards Releases. 9. The HLR sends Insert Subscriber Data (IMSI, GPRS Subscription Data) to the new SGSN. The new SGSN validates the UE's presence in the (new) RA. If due to regional subscription restrictions or access restrictions the MS is not allowed to be attached in the RA, the SGSN rejects the Routing Area Update Request with an appropriate cause, and may return an Insert Subscriber Data Ack (IMSI, SGSN Area Restricted) message to the HLR. If the network supports the MOCN configuration for network sharing, the SGSN may, if the MS is not a 'Network Sharing Supporting MS', in this case decide to initiate redirection by sending a Reroute Command to the RNS, as described in TS 23.251 [24] instead of rejecting the Routing Area Update Request. If all checks are successful, the SGSN constructs an MM context for the MS and returns an Insert Subscriber Data Ack (IMSI) message to the HLR. NOTE 12: This step is unmodified compared to pre-Rel-8. 10. The HLR acknowledges the Update Location by sending Update Location Ack (IMSI) to the new SGSN. NOTE 13: This step is unmodified compared to pre-Rel-8. 11. If the new SGSN is a 2G-SGSN: The new SGSN validates the MS's presence in the new RA. If due to roaming restrictions or access restrictions the MS, is not allowed to be attached in the SGSN, or if subscription checking fails, the new SGSN rejects the routing area update with an appropriate cause. If all checks are successful, the new SGSN constructs MM and PDP contexts for the MS. A logical link is established between the new SGSN and the MS. The new SGSN responds to the MS with Routing Area Update Accept (P‑TMSI, P‑TMSI Signature, Receive N‑PDU Number, PDP context status). Receive N‑PDU Number contains the acknowledgements for each acknowledged-mode NSAPI used by the MS, thereby confirming all mobile-originated N‑PDUs successfully transferred before the start of the update procedure. If the new SGSN is a 3G-SGSN: The new SGSN validates the MS's presence in the new RA. If due to roaming restrictions or access restrictions the MS is not allowed to be attached in the RA, or if subscription checking fails, the SGSN rejects the routing area update with an appropriate cause. If the network supports the MOCN configuration for network sharing, the SGSN may, if the MS is not a 'Network Sharing Supporting MS', in this case decide to initiate redirection by sending a Reroute Command to the RNS, as described in TS 23.251 [24] instead of rejecting the routing area update. If all checks are successful, the new SGSN establishes MM context for the MS. The new SGSN responds to the MS with Routing Area Update Accept (P-TMSI, VLR TMSI, P-TMSI Signature). For a MS with ongoing emergency bearer services, the new 3G-SGSN accepts the Routing Area Update Request and deactivates the non-emergency PDP contexts as specified in clause 9.2.4.2 in TS 23.060 [7]. When receiving the RAU Accept message and there is no ISR Activated indication the UE shall set its TIN to "P‑TMSI". With the PDP context status information, the MS shall deactivate all those bearers contexts locally which are active in the MS, but are indicated by the SGSN as being inactive. NOTE 13a: A Gn/Gp SGSN never indicates ISR Activated as it does not support ISR. NOTE 14: For the SGSN this step is unmodified compared earlier standards Releases. N-PDU numbers are not relevant as the network does not configure usage of acknowledged mode NSAPIs as described in clause "compatibility issues". 12. If the new SGSN is a 2G-SGSN: The MS acknowledges the new P‑TMSI by returning a Routing Area Update Complete (Receive N‑PDU Number) message to the SGSN. Receive N‑PDU Number contains the acknowledgements for each acknowledged-mode NSAPI used by the MS, thereby confirming all mobile-terminated N‑PDUs successfully transferred before the start of the update procedure. If Receive N‑PDU Number confirms reception of N‑PDUs that were forwarded from the old SGSN, these N‑PDUs shall be discarded by the new SGSN. LLC and SNDCP in the MS are reset. If the new SGSN is a 3G-SGSN: The MS confirms the reallocation of the TMSIs by returning a Routing Area Update Complete message to the SGSN. NOTE 15: This step is unmodified compared to pre-Rel-8. N-PDU numbers are not relevant as the network does not configure usage of acknowledged mode NSAPIs as described in clause "compatibility issues". 13. When the timer started in step 2) expires the old MME releases any RAN and Serving GW resources. If the PLMN has configured Secondary RAT usage data reporting, the MME first releases RAN resource before releasing Serving GW resources. When the MME receives Secondary RAT usage data from eNodeB in the S1 UE Context Release complete message, the MME continues with the Secondary RAT usage data reporting procedure using change notification message as described in clause 5.7A.3. The reporting procedure in clause 5.7A.3 is only performed if PGW secondary RAT usage reporting is active. The old MME deletes the EPS bearer resources by sending Delete Session Request (Cause; Operation Indication, Secondary RAT usage data) messages to the Serving GW. The operation Indication flag is not set, that indicates to the old Serving GW that the old Serving GW shall not initiate a delete procedure towards the PDN GW. Secondary RAT usage data is included if it was received from the source eNodeB in the S1 UE Context Release complete message. The old MME derives from the GTPv1 context transfer signalling that the new SGSN is a Gn/Gp SGSN and therefore any old S‑GW resources are released by the old MME. A Gn/Gp SGSN does not signal any S‑GW change. If the old S‑GW has due to ISR a control connection with another CN node (MME or SGSN) the cause indicates to the old S‑GW that the old S‑GW shall delete the bearer resources on the other old CN node by sending Delete Bearer Request message(s) to that other old CN node. If the old MME has an S1-MME association for the UE, the source MME sends a S1-U Release Command to the source eNodeB when receiving the SGSN Context Acknowledge message from the new SGSN. The RRC connection is released by the source eNodeB. The source eNodeB confirms the release of the RRC connection and of the S1-U connection by sending a S1-U Release Complete message to the source MME. If the PLMN has configured Secondary RAT usage data reporting and the source eNodeB has Secondary RAT usage data to report, the source eNodeB includes Secondary RAT usage data in this message. NOTE 16: The new SGSN may initiate RAB establishment after execution of the security functions, or wait until completion of the RA update procedure. For the MS, RAB establishment may occur any time after the Routing Area Update Request is sent. In the case of a rejected routing area update operation, due to regional subscription, roaming restrictions, access restrictions (see TS 23.221 [27] and TS 23.008 [28]) or because the SGSN cannot determine the HLR address to establish the locating updating dialogue, the new SGSN shall not construct an MM context. A reject shall be returned to the MS with an appropriate cause and the PS signalling connection shall be released. Upon return to idle, the MS shall act according to TS 23.122 [10]. If the network supports the MOCN configuration for network sharing, the SGSN may, if the MS is not a 'Network Sharing Supporting MS', in this case decide to initiate redirection by sending a Reroute Command to the RNS, as described in TS 23.251 [24] instead of rejecting the routing area update. If the new SGSN is unable to update the PDP context in one or more GGSNs, the new SGSN shall deactivate the corresponding PDP contexts as described in clause "SGSN-initiated PDP Context Deactivation Procedure". This shall not cause the SGSN to reject the routing area update. The PDP Contexts shall be sent from old to new SGSN in a prioritized order, i.e. the most important PDP Context first in the SGSN Context Response message. (The prioritization method is implementation dependent, but should be based on the current activity). The new SGSN shall determine the Maximum APN restriction based on the received APN Restriction of each PDP context from the GGSN and then store the new Maximum APN restriction value. If the new SGSN is unable to support the same number of active PDP contexts as received from old SGSN, the new SGSN should use the prioritisation sent by old SGSN as input when deciding which PDP contexts to maintain active and which ones to delete. In any case, the new SGSN shall first update all contexts in one or more GGSNs and then deactivate the context(s) that it cannot maintain as described in clause "SGSN-initiated PDP Context Deactivation Procedure". This shall not cause the SGSN to reject the routing area update. NOTE 17: If MS was in PMM-CONNECTED state the PDP Contexts are sent already in the Forward Relocation Request message as described in clause "Serving RNS relocation procedures" of TS 23.060 [7]. If the routing area update procedure fails a maximum allowable number of times, or if the SGSN returns a Routing Area Update Reject (Cause) message, the MS shall enter IDLE state. NOTE 18: The C1 CAMEL procedure call was omitted intentionally from this procedure since EPS does not support CAMEL procedure calls. The other CAMEL procedure calls are unmodified compared to pre-Rel-8. The CAMEL procedure calls shall be performed, see referenced procedures in TS 23.078 [29]: C2) CAMEL_GPRS_Routing_Area_Update_Session and CAMEL_PS_Notification. They are called in the following order: - The CAMEL_GPRS_Routing_Area_Update_Session procedure is called. The procedure returns as result "Continue". - Then the CAMEL_PS_Notification procedure is called. The procedure returns as result "Continue". C3) CAMEL_GPRS_Routing_Area_Update_Context. D.3.6 Gn/Gp SGSN to MME Tracking Area Update The Gn/Gp SGSN to MME Tracking Area Update procedure is illustrated in Figure D.3.6-1. Any steps descriptions that are from TS 23.060 [7] are shown as italic text and remain unmodified. In those step descriptions an MS stands for UE, new SGSN for new MME, old SGSN for old Gn/Gp SGSN, GGSN for P‑GW, and HLR for HSS. The new MME behaves towards the old Gn/Gp SGSN always like a Gn/Gp 3G-SGSN, regardless of whether the old Gn/Gp SGSN is a 2G-SGSN or a 3G-SGSN. Figure D.3.6-1: Gn/Gp SGSN to MME Tracking Area Update procedure NOTE 1: For a PMIP-based S5/S8, procedure steps (A) are defined in TS 23.402 [2]. Steps 13 and 15 concern GTP based S5/S8. 1. One of the triggers described in clause 5.3.3.0 for starting the TAU procedure occurs. 2. The UE sends to the eNodeB a Tracking Area Update Request (last visited TAI, P‑TMSI Signature, old GUTI, UE Core Network Capability, Preferred Network behaviour, active flag, EPS bearer status, additional GUTI, eKSI, NAS sequence number, NAS-MAC, KSI) message together with RRC parameters indicating the Selected Network and the old GUMMEI. In the RRC connection establishment signalling associated with the TAU Request, the UE indicates its support of the CIoT EPS Optimisations relevant for MME selection. If the UE's TIN indicates "GUTI" or "RAT‑related TMSI" and the UE holds a valid GUTI then the old GUTI indicates this valid GUTI. If the UE's TIN indicates "P‑TMSI" and the UE holds a valid P‑TMSI and related RAI then these two elements are indicated as the old GUTI. Mapping a P‑TMSI and an RAI to a GUTI is specified in Annex H. If the UE holds a valid GUTI and the old GUTI indicates a GUTI mapped from a P-TMSI and RAI, then the UE indicates the native GUTI. If the old GUTI indicates a GUTI mapped from a P-TMSI and RAI, and the UE has a valid P-TMSI signature, the P-TMSI signature shall be included. The RRC parameter "old GUMMEI" takes its value from the identifier that is signalled as the old GUTI according to the rules above. For a combined MME/SGSN the eNodeB is configured to route the MME‑code(s) of this combined node to the same combined node. This eNodeB is also configured to route MME‑code(s) of GUTIs that are generated by the UE's mapping of the P‑TMSIs allocated by the combined node. Such an eNodeB configuration may also be used for separate nodes to avoid changing nodes in the pool caused by inter RAT mobility. NOTE 2: In the scenario of this flow the UE's TIN indicates "P‑TMSI" and therefore the UE indicates a P‑TMSI as the old GUTI. The last visited TAI is included if the UE has any in order to help the MME to produce a good list of TAIs for any subsequent TAU Accept message. Selected Network indicates the network that is selected. Active flag is a request by UE to activate the radio and S1 bearers for all the active EPS Bearers by the TAU procedure. The EPS bearer status indicates each EPS bearer that is active within the UE. The UE's ISR capability is included in the UE Core Network Capability element. If the UE has valid EPS security parameters, the TAU Request message shall be integrity protected by the NAS‑MAC in order to allow validation of the UE by the MME. eKSI, NAS sequence number and NAS‑MAC are included if the UE has valid EPS security parameters. NAS sequence number indicates the sequential number of the NAS message. KSI is included if the UE indicates a GUTI mapped from a P‑TMSI in the information element "old GUTI". If a UE includes a Preferred Network Behaviour, this defines the Network Behaviour the UE is expecting to be available in the network as defined in clause 4.3.5.10. 3. The eNodeB derives the MME address from the RRC parameters carrying the old GUMMEI, the indicated Selected Network and the RAT (NB-IoT or WB-E-UTRAN). If that GUMMEI is not associated with the eNodeB, or the GUMMEI is not available, the eNodeB selects the MME as described in clause 4.3.8.3 on "MME Selection Function". The eNodeB forwards the TAU Request message together with the TAI+ECGI and RAT type of the cell from where it received the message and with the Selected Network to the MME. The RAT type shall distinguish between NB-IoT and WB-E-UTRAN types. To assist Location Services, the eNodeB indicates the UE's Coverage Level to the MME. 4. The new MME sends SGSN Context Request (old RAI, P‑TMSI, old P‑TMSI Signature, New SGSN Address) to the old SGSN to get the MM and PDP contexts for the UE. The new MME shall support functionality for Intra Domain Connection of RAN Nodes to Multiple CN Nodes, i.e. the MME derives the old SGSN from the old RAI and the old P-TMSI (or TLLI). When the internal structure of the pool area where the MS roamed from is not known, the new MME derives the old SGSN from the old RAI as described at clause 5.8 in TS 23.060 [7]. For this case, the new MME derives an SGSN that it believes is the old SGSN. This derived SGSN is itself the old SGSN, or it is associated with the same pool area as the actual old SGSN and it will determine the correct old SGSN from the P-TMSI (or TLLI) and relay the message to that actual old SGSN. 5. If the old SGSN is a 2G-SGSN: The old 2G-SGSN validates the old P‑TMSI Signature and responds with an appropriate error cause if it does not match the value stored in the old 2G SGSN. This should initiate the security functions in the new SGSN. If the security functions authenticate the MS correctly, the new SGSN shall send an SGSN Context Request (old RAI, old PTMSI, MS Validated, New SGSN Address) message to the old SGSN. MS Validated indicates that the new SGSN has authenticated the MS. If the old P‑TMSI Signature was valid or if the new SGSN indicates that it has authenticated the MS, the old SGSN stops assigning SNDCP N‑PDU numbers to downlink N‑PDUs received, and responds with SGSN Context Response (MM Context, PDP Contexts). If the MS is not known in the old SGSN, the old SGSN responds with an appropriate error cause. The old SGSN stores New SGSN Address, to allow the old SGSN to forward data packets to the new SGSN. Each PDP Context includes the SNDCP Send N‑PDU Number for the next downlink N‑PDU to be sent in acknowledged mode to the MS, the SNDCP Receive N‑PDU Number for the next uplink N‑PDU to be received in acknowledged mode from the MS, the GTP sequence number for the next downlink N‑PDU to be sent to the MS and the GTP sequence number for the next uplink N‑PDU to be tunnelled to the GGSN. The old SGSN starts a timer and stops the transmission of N-PDUs to the MS. The new SGSN shall ignore the MS Network Capability contained in MM Context of SGSN Context Response only when it has previously received an MS Network Capability in the Routing Area Request. If the old SGSN is a 3G-SGSN: The old 3G-SGSN validates the old P‑TMSI Signature and responds with an appropriate error cause if it does not match the value stored in the old SGSN. This should initiate the security functions in the new SGSN. If the security functions authenticate the MS correctly, the new SGSN shall send an SGSN Context Request (IMSI, old RAI, MS Validated) message to the old 3G-SGSN. MS Validated indicates that the new SGSN has authenticated the MS. If the old P‑TMSI Signature was valid or if the new SGSN indicates that it has authenticated the MS, the old SGSN starts a timer. If the MS is not known in the old SGSN, the old 3G-SGSN responds with an appropriate error cause. If the UE with emergency bearers is not authenticated in the old MME (in a network supporting unauthenticated UEs) the old MME continues the procedure with sending a Context Response and starting the timer also when it cannot validate the Context Request. The old 3G SGSN responds with an SGSN Context Response (MM Context, PDP Contexts) message. For each PDP context the old 3G SGSN shall include the GTP sequence number for the next uplink GTP PDU to be tunnelled to the GGSN and the next downlink GTP sequence number for the next PDU to be sent to the MS. Each PDP Context also includes the PDCP sequence numbers if PDCP sequence numbers are received from the old SRNS. The new 3G-SGSN shall ignore the MS Network Capability contained in MM Context of SGSN Context Response only when it has previously received an MS Network Capability in the Routing Area Request. The GTP sequence numbers received from the old 3G-SGSN are only relevant if delivery order is required for the PDP context (QoS profile). If the UE uses power saving functions and the DL Data Buffer Expiration Time for the UE has not expired, the old Gn/Gp-SGSN indicates Buffered DL Data Waiting. When this is indicated, the new MME invokes data forwarding and user plane setup corresponding to clause 5.3.3.1A. NOTE 3: In this step, the new "SGSN" shall be understood to be a new "MME" and the old SGSN stores new SGSN Address, to allow the old SGSN to forward data packets to the new "S‑GW or eNodeB". This step describes both the 2G and 3G SGSN variants due to combining the 2G or 3G SGSN to MME TAU into a single procedure. NOTE 4: For the old SGSN, this step is unmodified compared to pre-Rel-8. The MME (called new SGSN in above description) must provide SGSN functionality which includes mapping PDP contexts to EPS bearer information. SNDCP, GTP and PDCP sequence numbers are not relevant for the MME as the network does not configure usage of "delivery order required", does not configure acknowledged mode NSAPIs (SNDCP) and does not configure loss less UTRAN PDCP as described in clause "compatibility issues". 6. Security functions may be executed. Procedures are defined in clause 5.3.10 on Security Function. If the SGSN Context Response message from the old SGSN did not include IMEISV, the MME shall retrieve the ME Identity (the IMEISV) from the UE. 7. If the new MME identifies that the RAT type has changed, the MME checks the subscription information to identify for each APN whether to maintain the PDN connection, disconnect the PDN connection with a reactivation request, or, disconnect the PDN connection without reactivation request. If the MME decides to deactivate a PDN connection it performs MME-initiated PDN Connection Deactivation procedure after the tracking area update procedure is completed but before the S1/RRC interface connection is released. Existing ESM cause values as specified in TS 24.301 [46] (e.g. #39, "reactivation requested"; #66 "Requested APN not supported in current RAT and PLMN combination"; and for a dedicated bearer, possibly #37 "EPS QoS not accepted") are used to cause predictable UE behaviour. If all the PDN connections are disconnected and the UE does not support "attach without PDN connectivity", the MME shall request the UE to detach and reattach. The new MME sends an SGSN Context Acknowledge message to the old SGSN. This informs the old SGSN that the new SGSN is ready to receive data packets belonging to the activated PDP contexts. The old SGSN marks in its context that the MSC/VLR association and the information in the GGSNs and the HLR are invalid. This triggers the MSC/VLR, the GGSNs, and the HLR to be updated if the MS initiates a Routing area update procedure back to the old SGSN before completing the ongoing routing area update procedure. If the security functions do not authenticate the UE correctly, then the Tracking area update shall be rejected, and the new MME shall send a reject indication to the old SGSN. The old SGSN shall continue as if the SGSN Context Request was never received. NOTE 5: in the italic text of this step, new "SGSN" shall be understood as to be a new "MME". The MME needs to map PDP contexts received from Gn/Gp SGSN into EPS bearer information. The GGSN address(es) and TEIDs map to the PDN GW address(es) and TEIDs respectively. The MME maps PDP contexts to EPS bearers one-to-one and it translates the release 99 QoS parameters to the EPS bearer QoS parameters. NOTE 6: The SGSN operation is unmodified compared to pre-Rel-8. The MME indicates reserved TEID and IP address parameters from an S-GW to the old SGSN so that the old Gn/Gp SGSN can forward data packets when needed. The S-GW discards any packets received from old Gn/Gp SGSN. NOTE 7: The Gn signalling between the new MME and the old Gn/Gp SGSN has no capabilities to indicate ISR Supported or ISR Activated. If there is no PDP context at all and the CIoT EPS Optimisation without PDN connection is not applied, the MME rejects the TAU Request. For UE using CIoT EPS Optimisation without any activated PDN connection, the steps 9, 10, 11, 12 and 13 are skipped. 8. The old SGSN or the old RNC forward data to the S-GW and the S-GW discards these data. 9. The new MME adopts the bearer contexts received from the SGSN as the UE's EPS bearer contexts to be maintained by the new MME. The new MME maps the PDP contexts to the EPS bearers 1-to-1 and maps the Release 99 QoS parameter values of a PDP context to the EPS Bearer QoS parameter values of an EPS bearer as defined in Annex E. The MME establishes the EPS bearer(s) in the indicated order. The MME deactivates the EPS bearers which cannot be established. The MME verifies the EPS bearer status received from the UE with the bearer contexts received from the old SGSN and releases any network resources related to EPS bearers that are not active in the UE. If the UE has no PDP context, the MME rejects the TAU Request. The new MME selects a Serving GW and sends an Create Session Request (IMSI, MME Address and TEID, PDN GW address and TEID, EPS Bearer QoS, serving network identity, ME Identity, User Location Information IE, UE Time Zone IE, User CSG Information IE, RAT type, MS Info Change Reporting support indication, NRS (received from the SGSN)) message per PDN connection to the Serving GW. The MME shall send the serving network identity to the Serving GW. The new MME does not indicate ISR Activated. 10. The Serving GW creates contexts and informs the PDN GW(s) about the change of the RAT type. The Serving GW sends a Modify Bearer Request (Serving GW Address and TEID, RAT type, ME Identity, User Location Information IE, UE Time Zone IE, User CSG Information IE, MS Info Change Reporting support indication, PDN Charging Pause Support indication) message per PDN connection to the PDN GW(s) concerned. 11. If dynamic PCC is deployed, and RAT type information needs to be conveyed from the PDN GW to the PCRF, then the PDN GW shall send RAT type information to the PCRF by performing an IP‑CAN Session Modification procedure as defined in TS 23.203 [6]. NOTE 8: The PDN GW does not need to wait for the PCRF response, but continues in the next step. If the PCRF response leads to an EPS bearer modification the PDN GW should initiate a bearer update procedure. 12. The PDN GW updates its context field and returns a Modify Bearer Response (PDN GW address and TEID, MSISDN, Default bearer id, Charging Id, MS Info Change Reporting Action (Start) (if the PDN GW decides to receive UE's location information during the session), CSG Information Reporting Action (Start) (if the PDN GW decides to receive UE's User CSG information during the session), PDN Charging Pause Enabled indication (if PDN GW has chosen to enable the function), APN Restriction) message to the Serving GW. The MSISDN is included if the PDN GW has it stored in its UE context. When the UE moves from Gn/Gp SGSN to the MME, the PDN GW shall send the APN restriction of each bearer context to the Serving GW. 13. The Serving GW updates its context and returns an Create Session Response (Serving GW address and TEID for user plane, PDN GW address and TEID, Serving GW Address and TEID for the control plane, Default bearer id, APN restriction) message to the new MME. The message also includes MS Info Change Reporting Action (Start) and/or CSG Information Reporting Action (Start) if they are included in step 12. The Serving GW shall forward the received APN Restriction to the MME. When the MME receives the Create Session Response message, the MME checks if there is a "Availability after DDN Failure" monitoring event or a "UE Reachability" monitoring event configured for the UE in the MME and in such a case sends an event notification (see TS 23.682 [74] for further information). 14. To ensure the release of all UE resources in the Gn/Gp SGSN the new MME informs the HSS of the change of the serving core network node by sending an Update Location Request (MME Address, IMSI, ME Identity, ULR-Flags, MME Capabilities, Homogenous Support of IMS Voice over PS Sessions) message to the HSS. The ME Identity is included if the SGSN Context Response did not contain the IMEISV. Because of interoperation with an Gn/Gp SGSN, which the new MME identifies from the GTPv1 Context Response signalling, the ULR-Flags indicates "Single-Registration-Indication". The MME capabilities indicate the MME's support for regional access restrictions functionality. For "Homogenous Support of IMS Voice over PS Sessions", see clause 4.3.5.8A. 15. If the MME changes, then the HSS cancels any old MME. The HSS sends a Cancel Location (IMSI, Cancellation type) message to the old MME, with a Cancellation Type set to Update Procedure. 16. The old MME removes the MM context. The old MME releases any local bearer resources and it deletes the EPS bearer resources by sending Delete Session Request (Cause, Operation Indication) messages to the Serving GW. The operation Indication flag is not set, that indicates that the S‑GW shall not initiate a delete procedure towards the PDN GW. If ISR is activated then the cause indicates to the old S‑GW that the old S‑GW shall delete the bearer resources on the other old CN node by sending Delete Bearer Request message(s) to that CN node. The old MME acknowledges with a Cancel Location Ack (IMSI) message. 17. The HSS cancels any old SGSN node as the ULR-Flags indicates "Single-Registration-Indication". The HSS sends a Cancel Location (IMSI, Cancellation Type) message to the old SGSN. The old SGSN removes the contexts. If the timer started in step 5 is not running, the old SGSN removes the MM context. Otherwise, the contexts are removed when the timer expires. It also ensures that the MM context is kept in the old SGSN for the case the UE initiates another TAU procedure before completing the ongoing TAU procedure to the new MME. NOTE 9: In all other mobility scenarios a new CN node initiates only cancellation of an old CN node of the same type via HSS. In this scenario here (Gn/Gp SGSN to MME TAU) the new MME, by indicating single registration, initiates in addition the cancellation of the old Gn/Gp SGSN via HSS to make sure that any PDP contexts of the UE are properly released. MME and S4 SGSN release PDP/PDN contexts based on context transfer signalling. 18. On receipt of Cancel Location, if the MS is PMM CONNECTED in the old SGSN, the old SGSN sends an Iu Release Command message to the old SRNC. 19. When the data-forwarding timer has expired, the SRNS responds with an Iu Release Complete message. 20. The old SGSN acknowledges with a Cancel Location Ack (IMSI) message. 21. The new MME validates the UE's presence in the (new) TA. If all checks are successful, the MME constructs an MM context for the UE, the HLR acknowledges the Update Location by sending Update Location Ack (IMSI, Subscription Data) message to the new MME. If the Update Location is rejected by the HSS, the MME rejects the TAU Request from the UE with an appropriate cause sent in the TAU Reject message to the UE. 22. If due to regional subscription restrictions or access restrictions the UE is not allowed to access the TA: - For UEs with ongoing emergency bearer services, the new MME accepts the Tracking Area Update Request and releases the non-emergency bearers as specified in clause 5.10.3. - For all other cases, the new MME rejects Tracking Area Update Request with an appropriate cause to the UE and notifies the HSS of rejection (details of this notification is stage 3 detail). The new MME responds to the UE with a Tracking Area Update Accept (GUTI, TAI-list, EPS bearer status, NAS sequence number, NAS-MAC, ISR Activated, Supported Network Behaviour) message. Restriction list shall be sent to eNodeB as eNodeB handles the roaming restrictions and access restrictions in the Intra E-UTRAN case. If the "active flag" is set in the TAU Request message the user plane setup procedure can be activated in conjunction with the TAU Accept message. The procedure is described in detail in TS 36.300 [5]. The messages sequence should be the same as for the UE triggered Service Request procedure specified in clause 5.3.4.1 from the step when MME establishes the bearer(s). If the active flag is set the MME may provide the eNodeB with Handover Restriction List. Handover Restriction List is described in clause 4.3.5.7 "Mobility Restrictions". The EPS bearer status indicates the active bearers in the network. The UE removes any internal resources related to bearers not marked active in the received EPS bearer status. If the EPS bearer status information was in the TAU Request, the MME shall indicate the EPS bearer status to the UE. For UE using CIoT EPS Optimisation without any activated PDN connection, there is no EPS bearer status included in the TAU Accept message. The MME indicates the CIoT optimisations it supports and prefers in the Supported Network Behaviour information as defined in clause 4.3.5.10. When receiving the TAU Accept message and there is no ISR Activated indication the UE shall set its TIN to "GUTI". NOTE 10: In the case of interoperation with Gn/Gp SGSNs, ISR Activated is never indicated by the MME as the SGSN does not support ISR, which the new MME recognises from Gn interface signalling that does not support ISR indications. If the Subscription Data received from the HSS (during the TAU) contains information that is necessary for the E-UTRAN to be aware of (e.g. a restriction in the UE's permission to use NR as a secondary RAT, Unlicensed Spectrum in the form of LAA/LWA/LWIP/NR-U (as specified in clause 4.3.30) or a combination of them), or an existing UE context in the MME indicates that the UE is not permitted to use NR as a secondary RAT, Unlicensed Spectrum or a combination of them, then the MME sends an updated Handover Restriction List in the Downlink NAS Transport message that it sends to E-UTRAN. If the UE is not allowed to use NR as Secondary RAT, the MME indicates that to the UE in TAU Accept message. 23. If the GUTI was included in the TAU Accept message, the UE acknowledges the message by returning a Tracking Area Update Complete message to the MME. When the "Active flag" is not set in the TAU Request message and the Tracking Area Update was not initiated in ECM-CONNECTED state, the MME releases the signalling connection with UE, according to clause 5.3.5. NOTE 11: The new MME may initiate E‑RAB establishment (see TS 36.413 [36]) after execution of the security functions (step 5), or wait until completion of the TA update procedure. For the UE, E‑RAB establishment may occur any time after the TA update request is sent (step 2). 24. The target MME calculates UE-AMBR as defined in clause 4.7.3. If the local UE-AMBR provided by the MME as defined in Annex E is different from the corresponding derived UE-AMBR, or the APN-AMBR mapped from the subscribed MBR is different from the subscribed APN-AMBR, or the mapped subscribed QoS profile (i.e. the subscribed QoS profile mapped according to Annex E) of the default bearer is different from the EPS Subscribed QoS profile received from the HSS, the new MME shall initiate Subscribed QoS Modification procedure as described in clause 5.4.2.2, Figure 5.4.2.2-1. In the case of a rejected tracking area update operation, due to regional subscription, roaming restrictions, or access restrictions (see TS 23.221 [27] and TS 23.008 [28]) the new MME should not construct a bearer context. In the case of receiving the subscriber data from HSS, the new MME may construct an MM context and store the subscriber data for the UE to optimise signalling between the MME and the HSS. A reject shall be returned to the UE with an appropriate cause and the S1 connection shall be released. Upon return to idle, the UE shall act according to TS 23.122 [10]. If the new MME is unable to update the bearer context in one or more P‑GWs, the new MME shall deactivate the corresponding bearer contexts as described in clause "MME Initiated Dedicated Bearer Deactivation Procedure". This shall not cause the MME to reject the tracking area update. The PDP Contexts shall be sent from old SGSN to new SGSN (MME) in a prioritized order, i.e. the most important PDP Context first in the SGSN Context Response message. (The prioritization method is implementation dependent, but should be based on the current activity). The new MME shall determine the Maximum APN restriction based on the received APN Restriction of each bearer context from the P‑GW and then store the new Maximum APN restriction value. If there are active EPS GBR bearers with maximum bitrate set to 0, the MME should initiate MME Initiated Dedicated Bearer Deactivation (as specified in clause 5.4.4.2) to deactivate the related EPS bearer Context. If the new MME is unable to support the same number of active bearer contexts as received from old SGSN, the new MME should use the prioritisation sent by old SGSN as input when deciding which bearer contexts to maintain active and which ones to delete. In any case, the new MME shall first update all contexts in one or more P‑GWs and then deactivate the context(s) that it cannot maintain as described in clause "MME Initiated Dedicated Bearer Deactivation Procedure". This shall not cause the MME to reject the tracking area update. NOTE 12: If MS (UE) was in PMM-CONNECTED state the PDP Contexts are sent already in the Forward Relocation Request message as described in clause "Serving RNS relocation procedures" of TS 23.060 [7]. If the tracking area update procedure fails a maximum allowable number of times, or if the MME returns a Tracking Area Update Reject (Cause) message, the UE shall enter EMM DEREGISTERED state. If the Update Location Ack message indicates a reject, this should be indicated to the UE, and the UE shall not access non-PS services until a successful location update is performed. The CAMEL procedure calls shall be performed, see referenced procedures in TS 23.078 [29]: C1) CAMEL_GPRS_PDP_Context_Disconnection, CAMEL_GPRS_Detach and CAMEL_PS_Notification. They are called in the following order: - The CAMEL_GPRS_PDP_Context_Disconnection procedure is called several times: once per PDP context. The procedure returns as result "Continue". - Then the CAMEL_GPRS_Detach procedure is called once. The procedure returns as result "Continue". - Then the CAMEL_PS_Notification procedure is called once. The procedure returns as result "Continue". NOTE 13: This CAMEL handling is unmodified compared to pre-Rel-8. NOTE 14: CAMEL procedure calls C2 and C3 were omitted intentionally from this procedure since EPS does not support CAMEL procedure calls. D.3.7 E-UTRAN to GERAN A/Gb mode Inter RAT handover D.3.7.1 General The interoperation procedures describe information flows for Gn/Gp SGSNs and other EPS network elements. All messages between SGSN and MME, between SGSN and BSS, between SGSN and HSS and between SGSN and P‑GW (GGSN in TS 43.129 [8]) as well as the therein contained information elements are the same as specified for the adequate TS 43.129 [8] procedures. These messages and procedure step descriptions are taken from TS 43.129 [8] for explanatory purposes only. These descriptions are in italic text and shall not be modified by the interoperation procedures. It cannot be assumed that the messages and procedure step descriptions that are taken from TS 43.129 [8] will be updated when modifications or corrections are performed for TS 43.129 [8]. If there are any discrepancies for these messages and procedure step descriptions TS 43.129 [8] takes precedence. The messages between the MME and any other node than the Gn/Gp SGSN as well as the therein contained information elements are the same as specified in the main body of this technical specification for the IRAT handover E‑UTRAN to/from GERAN A/Gb mode procedure (clauses 5.5.2.3 and 5.5.2.4). These descriptions are in bold italic text and should be modified simultaneously when clauses 5.5.2.3 or 5.5.2.4 are updated. If there are any discrepancies, the procedure step descriptions in clauses 5.5.2.3 or 5.5.2.4 take precedence. D.3.7.2 Preparation phase Figure D.3.7.2-1: E-UTRAN to GERAN A/Gb Inter RAT HO, preparation phase 1. The source eNodeB decides to initiate an Inter RAT Handover to the target GERAN A/Gb mode (2G) system. At this point both uplink and downlink user data is transmitted via the following: Bearer(s) between UE and Source eNodeB, GTP tunnel(s) between Source eNodeB, Serving GW and PDN GW. If the UE has an ongoing emergency bearer service the source eNodeB shall not initiate PS handover to GERAN. NOTE 1: The process leading to the handover decision is outside of the scope of this specification 2. The source eNodeB sends a Handover Required (Cause, Target System Identifier, Source BSS to Target BSS Transparent Container) message to the Source MME to request the CN to establish resources in the Target BSS, Target SGSN and the Serving GW. The bearers that will be subject to data forwarding (if any) are identified by the new SGSN in a later step (see step 8 below). The 'Target System Identifier' IE contains the identity of the target global cell Id. NOTE 2: This step is unmodified compared to clause 5.5.2.3.2. The target SGSN acts as the new SGSN. 3 The old SGSN determines from the Target Cell Identifier that the type of handover is inter-RAT/mode handover. In the case of Inter-RAT/ mode Inter-SGSN PS handover, the old SGSN initiates the PS Handover resource allocation procedure by sending a Forward Relocation Request (IMSI, Tunnel Endpoint Identifier Control Plane, RANAP Cause, Target Cell Identifier, MM Context, PDP Contexts, Packet Flow ID, SNDCP XID parameters, LLC XID parameters, PDP Context Prioritisation, Source BSS To Target BSS Transparent Container [RN part] in the BSS Container, Source RNC Id, SGSN Address for control plane) message to the new SGSN. If the old SGSN supports PS handover procedures then it has to allocate a valid PFI according to clause 4.4.1 during the PDP Context activation procedure. Each PDP context contains the GGSN Address for User Plane and the Uplink TEID for Data (to this GGSN Address and Uplink TEID for Data the old SGSN and the new SGSN send uplink packets). The MM context includes information on the EPS Bearer context(s). If none of the UE's EPS Bearers can be supported by the selected target SGSN, the old SGSN rejects the handover attempt by sending a Handover Preparation Failure (Cause) message to the Source eNodeB. NOTE 3: If the handover is successful, the old SGSN will signal to the SGW and/or SCEF to release any non-included EPS Bearers after step 8 of the Execution procedure. The non-included bearers are locally released by the MS following the PDP Context Status synchronisation that occurs during the Routing Area Update at step 13 of the Execution procedure. The MM context contains security related information, e.g. supported ciphering algorithms as described in TS 29.060 [14]. The relation between GSM and UMTS security parameters is defined in TS 33.102 [40], The new SGSN selects the ciphering algorithm to use. This algorithm will be sent transparently from the new SGSN to the MS. The IOV-UI parameter generated in the new SGSN and used, as input to the ciphering procedure will also be transferred transparently from the new SGSN to the MS. When the new SGSN receives the Forward Relocation Request message the required PDP, MM, SNDCP and LLC contexts are established and a new P-TMSI is allocated for the MS. When this message is received by the new SGSN it begins the process of establishing PFCs for all PDP contexts. When the new SGSN receives the Forward Relocation Request message it extracts from the PDP Contexts the NSAPIs and SAPIs and PFIs to be used in the new SGSN. If for a given PDP Context the new SGSN does not receive a PFI from the old SGSN, it shall not request the target BSS to allocate TBF resources corresponding to that PDP Context. If none of the PDP Contexts forwarded from the old SGSN has a valid PFI allocated the new SGSN shall consider this as a failure case and the request for PS handover shall be rejected. In the case when an SAPI and PFI was available at the old SGSN but the new SGSN does not support the same SAPI and PFI for a certain NSAPI as the old SGSN, the new SGSN shall continue the PS handover procedure only for those NSAPIs for which it can support the same PFI and SAPI as the old SGSN. All PDP contexts for which no resources are allocated by the new SGSN or for which it cannot support the same SAPI and PFI (i.e. the corresponding NSAPIs are not addressed in the response message of the target SGSN), are maintained and the related SAPIs and PFIs are kept. These PDP contexts may be modified or deactivated by the new SGSN via explicit SM procedures upon RAU procedure. The old SGSN shall indicate the current XID parameter settings if available (i.e. those negotiated at the old SGSN when the MS was in A/Gb mode or received during a previous inter-SGSN PS handover) to the new SGSN. If the new SGSN can accept all XID parameters as indicated by the old SGSN, the new SGSN shall create a NAS container for PS HO indicating 'Reset to the old XID parameters'. Otherwise, if the new SGSN cannot accept all XID parameters indicated by the old SGSN or if no XID parameters were indicated by the old SGSN, the new SGSN shall create a NAS container for PS HO indicating Reset (i.e. reset to default parameters). NOTE 4: This step is unmodified compared to pre-Rel-8. The Source eNodeB acts as the source RNC, Source MME acts as the old SGSN, and the PDN GW acts as the GGSN. 4. The new SGSN sends a PS Handover Request (Local TLLI, IMSI, Cause, Target Cell Identifier, Source BSS to Target BSS Transparent Container (RN part), PFCs To Be Set Up List, NAS container for PS HO) message to the target BSS. The new SGSN shall not request resources for PFCs associated with PDP contexts with maximum bit rate for uplink and downlink of 0 kbit/s or for which the Activity Status Indicator within the PDP Context indicates that no active RAB exists on the source side. 5. Based upon the ABQP for each PFC the target BSS makes a decision about which PFCs to assign radio resources. The algorithm by which the BSS decides which PFCs that need resources is implementation specific. Due to resource limitations not all downloaded PFCs will necessarily receive resource allocation. The target BSS allocates TBFs for each PFC that it can accommodate. 6. The target BSS shall prepare the Target BSS to Source BSS Transparent Container which contains a PS Handover Command including the CN part (NAS container for PS HO) and the RN part (PS Handover Radio Resources). 7. Target BSS shall send the PS Handover Request Acknowledge message (Local TLLI, List of Set Up PFCs, Target BSS to Source BSS Transparent Container) message to the new SGSN. Upon sending the PS Handover Request Acknowledge message the target BSS shall be prepared to receive downlink LLC PDUs from the new SGSN for the accepted PFCs. Any PDP contexts for which a PFC was not established are maintained in the new SGSN and the related SAPIs and PFIs are kept. These PDP contexts may be modified or deactivated by the new SGSN via explicit SM procedures upon the completion of the routing area update (RAU) procedure. 8. The new SGSN passes the assigned list of TEIDs for each PDP context for which a PFC was assigned in the RAB setup information IE in the Forward Relocation Response (Cause, List of Set Up PFCs, Target BSS to Source BSS Transparent Container) in the BSS Container, Tunnel Endpoint Identifier Control Plane, SGSN Address for User Traffic, Tunnel Endpoint Identifier Data II) message to the old SGSN. The NSAPIs of the active PDP Contexts received in the Forward Relocation Request message for which the PS handover continues, i.e. for which resources are allocated for the PFCs in the target BSS, are indicated in this message. The Tunnel Endpoint Identifier Data II, one information for each PDP context, is the tunnel endpoint of the new SGSN and is used for data forwarding from the Source eNodeB, via the new SGSN, to the target BSS. The new SGSN activates the allocated LLC/SNDCP engines as specified in TS 44.064 [23] for an SGSN originated Reset or 'Reset to the old XID parameters'. When the old SGSN receives the Forward Relocation Response message and it decides to proceed with the handover, the preparation phase is finished and the execution phase will follow. 9. If 'Indirect Forwarding' applies, the source MME sends a Create Indirect Data Forwarding Tunnel Request message (Cause, SGSN Address(es) and TEID(s) for Data Forwarding) to the Serving GW. Cause indicates that the bearer(s) are subject to data forwarding. Indirect forwarding may be performed via a Serving GW which is different from the Serving GW used as the anchor point for the UE. 9a. The Serving GW returns a Create Indirect Data Forwarding Tunnel Response (Cause, Serving GW Address(es) and TEID(s) for Data Forwarding) message to the target MME. If the Serving GW doesn't support data forwarding, an appropriate cause value shall be returned and the Serving GW Address(es) and TEID(s) will not be included in the message. NOTE 5: This step is mostly unmodified compared to pre-Rel-8. The Source MME acts as the old SGSN, and the PDN GW acts as the GGSN. D.3.7.3 Execution phase Figure D.3.7.3-1: E-UTRAN to GERAN A/Gb mode Inter RAT HO, execution phase The source eNodeB continues to receive downlink and uplink user plane PDUs. 1. The Source MME completes the preparation phase towards Source eNodeB by sending the message Handover Command (Target BSS to Source BSS Transparent Container (PS Handover Command with RN part and EPC part), Bearers Subject to Data Forwarding List). The "Bearers Subject to Data forwarding list" may be included in the message and it shall be a list of 'Address(es) and TEID(s) for user traffic data forwarding' received from target side in the preparation phase (Forward Relocation Response message (Step 8)). Source eNodeB initiate data forwarding for the bearers specified in the "Bearers Subject to Data Forwarding List". The data forwarding goes directly to target SGSN decided in the preparation phase. 2. The Source eNodeB will give a command to the UE to handover to the Target Access System via the message HO from E-UTRAN Command. This message includes a transparent container including radio aspect parameters that the Target BSS has set-up in the preparation phase (RN part). This message also includes the XID and IOV-UI parameters received from the Target SGSN (EPC part). Upon the reception of the HO from E-UTRAN Command message containing the Handover Command message, the UE shall associate its bearer IDs to the respective PFIs based on the relation with the NSAPI and shall suspend the uplink transmission of the user plane data. NOTE 1: This step is unmodified compared to clause 5.5.2.3.3. The target SGSN acts as the new SGSN. 3. If the PLMN has configured Secondary RAT usage data reporting and the source eNodeB has Secondary RAT usage data to report, the eNodeB sends the RAN Usage data report message (Secondary RAT usage data) to the MME. Since the handover is an inter-RAT handover, the MME continues with the Secondary RAT usage data reporting procedure as in clause 5.7A.3. The reporting procedure in clause 5.7A.3 is only performed if PGW secondary RAT usage reporting is active. NOTE 2: The source eNodeB does not send any RAN context towards the target BSS. 4. The MS executes the handover according to the parameters provided in the message delivered in step 2. The procedure is the same as in step 6 in clause 5.1.4.2 in TS 43.129 [8] with the additional function of association of the received PFI and existing RAB Id related to the particular NSAPI as described in clause 4.4.1 in TS 43.129 [8]. The UE locally deactivates ISR by setting its TIN from "RAT-related TMSI" to "GUTI", if any EPS bearer context activated after the ISR was activated in the UE exists. 5/7. After accessing the cell using access bursts and receiving timing advance information from the BSS in step 2, the MS processes the NAS container and then sends one XID Response message to the new SGSN. The MS sends this message immediately after receiving the Packet Physical Information message containing the timing advance or, in the synchronised network case, immediately if the PS Handover Access message is not required to be sent (see clause 6.2 in TS 43.129 [8]). Upon sending the XID Response message, the MS shall resume the user data transfer only for those NSAPIs for which there are radio resources allocated in the target cell. For NSAPIs using LLC ADM for which radio resources were not allocated in the target cell the MS may request for radio resources using the legacy procedures. NOTE 3: If the new SGSN indicated Reset (i.e. reset to default parameters) in the NAS container for PS HO included in the Handover from UTRAN Command message (UTRAN) or the Handover from GERAN Iu Command message, in order to avoid collision cases the mobile station may avoid triggering XID negotiation for any LLC SAPI used in LLC ADM, but wait for the SGSN to do so (see step 12). In any case the mobile station may avoid triggering XID negotiation for any LLC SAPI used in LLC ABM, but wait for the SGSN to do so (see step 12a). NOTE 4: This step is unmodified compared to pre-Rel-8. The message "HO from E-UTRAN Command" acts as the "Handover from UTRAN Command" message (UTRAN) or the "Handover from GERAN Iu Command" message. 6. Upon reception of the first correct RLC/MAC block (sent in normal burst format) from the MS the target BSS sends a PS Handover Complete (Local TLLI, Handover Complete Status) message to inform the new SGSN that the MS has arrived in the target cell. Each uplink N-PDU received by the new SGSN via the target BSS is then forwarded directly to the GGSN. A timer in source MME is started to supervise when resources in Source eNodeB and Source Serving GW shall be released. NOTE 5: This step is unmodified compared to pre-Rel-8. The PDN GW acts as the GGSN. 8. Upon receiving the PS Handover Complete message, the new SGSN send a Forward Relocation Complete message to the old SGSN to indicate completion of the PS handover procedures. The old SGSN responds with a Forward Relocation Complete Acknowledge message. For all bearers that were not included in the Forward Relocation Request message sent in step 3, the old SGSN now releases them by sending a Delete Bearer Command to the SGW, or, the appropriate message to the SCEF. NOTE 6: This step is unmodified compared to pre-Rel-8. The Source MME acts as the old SGSN. 9/11. The new SGSN sends an Update PDP Context Request (new SGSN Address, TEID, QoS Negotiated) message to the GGSN concerned. The GGSN updates the PDP context fields and returns an Update PDP Context Response (TEID) message. From now on the GGSN sends new incoming downlink IP packets to the new SGSN instead of to the old SGSN. The PDN GW shall include a Charging Id to be used at the SGSN as the Charging ID for reporting usage for this PDP context. The PDN GW shall include the Charging Id in the offline charging data. NOTE 7: This step is unmodified compared to pre-Rel-8. The Source MME acts as the old SGSN, and the PDN GW acts as the GGSN. 12. If the new SGSN indicated Reset (i.e. reset to default parameters) in the NAS container for PS HO included in the Handover from UTRAN Command message (UTRAN) or the Handover from GERAN Iu Command message, then on receipt of the PS Handover Complete the new SGSN initiates an LLC/SNDCP XID negotiation for each LLC SAPI used in LLC ADM. In this case if the SGSN wants to use the default parameters, it shall send an empty XID Command. If the new SGSN indicated 'Reset to the old XID parameters' in the NAS container for PS HO, no further XID negotiation is required for LLC SAPIs used in LLC ADM only. NOTE 8: This step is unmodified compared to pre-Rel-8. The message "HO from E-UTRAN Command" acts as the "Handover from UTRAN Command" message (UTRAN) or the "Handover from GERAN Iu Command" message. 12a. The new SGSN (re-)establishes LLC ABM for the PDP contexts which use acknowledged information transfer. During the exchange of SABM and UA the SGSN shall perform LLC/SNDCP XID negotiation. 13. The MS sends a Routing Area Update Request (Old P-TMSI, Old RAI, Old P-TMSI signature, Update Type) message to the new SGSN informing it that the source cell belongs to a new routing area. The MS shall send this message immediately after message 5, see TS 23.060 [7]. The new SGSN knows that a handover has been performed for this MS and can therefore exclude the SGSN context procedures which normally are used within the RA Update procedure. For a MS supporting CIoT EPS Optimisations, the MS uses the PDP context status information in the RAU Accept to identify any non-transferred bearers that it shall locally release. For further descriptions of the Routing Area Update procedure see TS 43.129 [8], clauses 5.5.2.3 and 5.6.1.1.1. NOTE 9: The RAU procedure is performed regardless if the routing area is changed or not, as specified by TS 43.129 [8]. 14. When the timer started at step 8 expires, the source MME sends a Release Resources message to the source eNodeB. The Source eNodeB releases its resources related to the UE. Additionally, the source MME deletes the EPS bearer resources by sending Delete Session Request (Cause, Operation Indication, Secondary RAT usage data) messages to the Serving GW. The operation Indication flag is not set, that indicates to the Serving GW that it shall not initiate a delete procedure towards the PDN GW. Secondary RAT usage data was included if it was received in step 3a. The Serving GW acknowledges with Delete Session Response (Cause) messages. If ISR is activated then the cause indicates to the old Serving GW that the old Serving GW shall delete the bearer resources on the other old CN node by sending Delete Bearer Request message(s) to that CN node. 15. When the timer started in step 8 expires and if resources for indirect forwarding have been allocated then they are released. D.3.8 GERAN A/Gb mode to E-UTRAN Inter RAT handover D.3.8.1 General See clause D.3.7.1. D.3.8.2 Preparation phase Figure D.3.8.2-1: GERAN A/Gb mode to E-UTRAN inter RAT HO, preparation phase 1. The source BSS decides to initiate a PS handover. At this point both uplink and downlink user data is transmitted via the following: TBFs between MS and source BSS, BSSGP PFCs tunnel(s) between source BSS and old SGSN, GTP tunnel(s) between old SGSN and GGSN. NOTE 1: The UE acts as MS, and the PDN GW acts as the GGSN. 2. The source BSS sends the message PS handover Required (TLLI, Cause, Source Cell Identifier, Target eNodeB Identifier, Source to Target Transparent Container (RN part), and active PFCs list) to Source SGSN to request the CN to establish resources in the Target eNodeB, Target MME and the Serving GW. NOTE 2: The Source SGSN acts as the Old SGSN. NOTE 3: As an implementations option for supporting introduction scenarios with pre-Rel8 SGSNs the source BSS may be configured to use RNC IDs instead of eNodeB IDs to identify a target eNodeB. The Cause is relayed transparently by the SGSN to the MME and the MME maps the BSSGP cause code to an S1AP cause code. Source to Target Transparent Container carries information for the target eNodeB. This container is relayed transparently by the SGSN. 3. The Source SGSN determines from the 'Target eNodeB Identifier' IE that the type of handover is IRAT PS Handover to E-UTRAN. The Source SGSN initiates the Handover resource allocation procedure by sending message Forward Relocation Request (IMSI, Target Identification, MM Context, PDP Context, SGSN Tunnel Endpoint Identifier for Control Plane, SGSN Address for Control plane, Source to Target Transparent Container (RN part), Packet Flow ID, SNDCP XID parameters, LLC XID parameters) to the target MME. This message includes all PDP contexts that are established in the source system indicating the PFIs and the XID parameters related to those PDP Contexts, and the uplink Tunnel endpoint parameters of the Serving GW. The PDP Contexts shall be sent in a prioritized order, i.e. the most important PDP Context first. The prioritization method is implementation dependent, but should be based on the current activity. NOTE 3: Assigning the highest priority to the PDP context without TFT could be done to get service continuity for all ongoing services regardless of the number of supported EPS bearers in the UE and network. The target MME maps the PDP contexts to the EPS bearers 1-to-1 and maps the Release 99 QoS parameter values of a PDP context to the EPS Bearer QoS parameter values of an EPS bearer as defined in Annex E. The MME establishes the EPS bearer(s) in the indicated order. The MME deactivates the EPS bearers which cannot be established. The MM context contains security related information, e.g. supported ciphering algorithms as described in TS 29.060 [14]. For the PDP Context with traffic class equals 'Background', the source SGSN shall indicate via the Activity Status Indicator IE that EPS bearers shall be established on the target side. NOTE 4: The Source SGSN acts as the old SGSN. 4. The target MME selects the Serving GW as described under clause 4.3.8.2 on "Serving GW selection function". The target MME sends a Create Session Request message (IMSI, MME Tunnel Endpoint Identifier for Control Plane, MME Address for Control plane, PDN GW address(es) for user plane, PDN GW UL TEID(s) for user plane, PDN GW address for control plane, and PDN GW TEID(s) for control plane, the Protocol Type over S5/S8, APN-AMBR, Serving Network) per PDN connection to the Serving GW. The Protocol Type over S5/S8 is provided to Serving GW which protocol should be used over S5/S8 interface. For relocation from Gn/Gp SGSN, the target MME provides the APN-AMBR if not received explicitly from the Gn/Gp SGSN based on the mapping from MBR (as specified in Annex E) to the Serving GW 4a. The Serving GW allocates its local resources and returns them in a Create Session Response (Serving GW address(es) for user plane, Serving GW UL TEID(s) for user plane, Serving GW Address for control plane, Serving GW TEID for control plane) message to the target MME. 5. The Target MME will request the Target eNodeB to establish the Bearer(s) by sending the message Handover Request (UE Identifier, S1AP Cause, Integrity protection information (i.e. IK and allowed Integrity Protection algorithms), Encryption information (i.e. CK and allowed Ciphering algorithms), EPS Bearers to be setup list, Source to Target Transparent Container). The Target MME shall not request resources for which the Activity Status Indicator within a PDP Context indicates that no active bearer exists on the source side for that PDP Context. For each EPS bearer requested to be established, 'EPS Bearers To Be Setup' IE shall contain information such as ID, bearer parameters, Transport Layer Address, "Data forwarding not possible" indication and S1 Transport Association. The Transport Layer Address is the Serving GW Address for user data, and the S1 Transport Association corresponds to the uplink Tunnel Endpoint Identifier Data. "Data forwarding not possible" indication shall be included if the target MME decides the corresponding bearer will not be subject to data forwarding. The target MME shall not request the target eNodeB to establish EPS GBR bearers with maximum bitrate set to 0 and those EPS bearers should not be included in the EPS Bearers to be setup list and should be deactivated by the MME. For the remaining EPS Bearer Contexts the MME ignores any Activity Status Indicator within an EPS Bearer Context and requests the target eNodeB to allocate resources for all the remaining EPS Bearer Contexts. The ciphering and integrity protection keys will be sent transparently from the target eNodeB to the UE in the Target to Source Transparent Container, and in the message PS Handover Command from source BSS to the UE. This will then allow data transfer to continue in the new RAT/mode target cell without requiring a new AKA (Authentication and Key Agreement) procedure. The MME shall compute the UE-AMBR, as per clause 4.7.3, based on explicit APN-AMBR values received from the Gn/Gp SGSN. If explicit APN-AMBR values are not received by the MME, a local UE-AMBR shall be included in the 'EPS Bearers be setup list ' IE. The local UE-AMBR is described in Annex E. 5a. The Target eNodeB allocates the request resources and returns the applicable parameters to the Target MME in the message Handover Request Acknowledge (Target to Source Transparent Container, EPS Bearers setup list, EPS Bearers failed to setup list). Upon sending the Handover Request Acknowledge message the target eNodeB shall be prepared to receive downlink GTP PDUs from the Serving GW for the accepted EPS bearers. The target eNodeB shall ignore it if the number of radio bearers in the Source to Target Transparent container does not comply with the number of bearers requested by the MME and allocate bearers as requested by the MME. 6. If 'Indirect Forwarding' applies, the target MME sends a Create Indirect Data Forwarding Tunnel Request message (Cause, Target eNodeB Address(es), TEID(s) for DL user plane) to the Serving GW. Cause indicates that the bearer(s) are subject to data forwarding. 6a. The Serving GW returns a Create Indirect Data Forwarding Tunnel Response (Cause, Serving GW Address(es) and TEID(s) for Data Forwarding) message to the target MME. If the Serving GW doesn't support data forwarding, an appropriate cause value shall be returned and the Serving GW Address(es) and TEID(s) will not be included in the message. 7. The Target MME sends the message Forward Relocation Response (Cause, List of Set Up PFCs, MME Tunnel Endpoint Identifier for Control Plane, BSSGP cause, MME Address for control plane, Target to Source Transparent Container, Address(es) and TEID(s) for Data Forwarding) to the Source SGSN. If 'Direct Forwarding' is applicable, then the IEs 'Address(es) and TEID(s) for Data Forwarding' contains the DL GTP-U tunnel endpoint parameters to the eNodeB. If 'Indirect Forwarding' applies the IEs 'Address(es) and TEID(s) for Data Forwarding' contain the DL GTP-U tunnel endpoint parameters to the Serving GW. NOTE 5: The Source SGSN acts as the old SGSN. D.3.8.3 Execution phase Figure D.3.8.3-1: GERAN A/Gb mode to E-UTRAN Inter RAT HO, execution phase NOTE 1: For a PMIP-based S5/S8, procedure steps (A) are defined in TS 23.402 [2]. Steps 9 and 9a concern GTP based S5/S8. The old SGSN continues to receive downlink and uplink user plane PDUs. When old SGSN receives the Forward Relocation Response message it may start downlink N-PDU relay and duplication to the target eNodeB, and the target eNodeB may start blind transmission of downlink user data towards the UE over the allocated radio channels. 1. The Source SGSN completes the preparation phase towards Source BSS by sending the message PS HO Required Acknowledge (TLLI, List of Set Up PFCs, Target to Source Transparent Container). This message includes all PFIs that could be established on the Target side. Before sending the PS Handover Required Acknowledge message, the source SGSN may suspend downlink data transfer for any PDP contexts. Before sending the PS Handover Command message to the UE the source BSS, may try to empty the downlink BSS buffer for any BSS PFCs. NOTE 2: The Source SGSN acts as the old SGSN. 2. The Source BSS will command the UE to handover to the target eNodeB via the message PS Handover Command. The access system specific message to UE includes a transparent container including radio aspect parameters that the Target eNodeB has set-up in the preparation phase. 3. There is no RAN context transfer during inter RAT handovers with E-UTRAN. If the source SGSN originates any SRNS contexts the MME acknowledges the receipt towards the SGSN and ignores the message content. 4. The UE moves to the E-UTRAN and performs access procedures toward Target eNodeB. 5. When the UE has got access to Target eNodeB it sends the message HO to E-UTRAN Complete. The UE shall implicitly derive the EPS bearers for which an E-RAB was not established from the PS Handover Command and deactivate them locally without an explicit NAS message at this step. 6. When the UE has successfully accessed the Target eNodeB, the Target eNodeB informs the Target MME by sending the message Handover Notify. Upon receipt of the Handover Notify message the target MME starts a timer if the target MME applies indirect forwarding. 7. Then the Target MME knows that the UE has arrived to the target side and Target MME informs the old SGSN by sending the Forward Relocation Complete () message. The old SGSN will also acknowledge that information. When the Forward Relocation Complete message has been received and there is no longer any need for the Old SGSN to forward data, the old SGSN stops data forwarding. A timer in old SGSN is started to supervise when resources shall be released. 8. The Target MME will now complete the Handover procedure by informing the Serving GW (for Serving GW relocation this will be the Target Serving GW) that the Target MME is now responsible for all the EPS bearers the UE have established. This is performed in the message Modify Bearer Request (Cause, MME Tunnel Endpoint Identifier for Control Plane, EPS Bearer ID(s), MME Address for Control Plane, eNodeB Address(es) and TEID(s) for User Traffic for the accepted EPS bearers, PDN GW addresses and TEIDs (for GTP-based S5/S8) or GRE keys (for PMIP-based S5/S8) at the PDN GW(s) for uplink traffic and RAT type) per PDN connection. If any EPS bearers are to be released the MME triggers the bearer release procedure as specified in clause 5.4.4.2. If the Serving GW receives a DL packet for a non-accepted bearer, the Serving GW drops the DL packet and does not send a Downlink Data Notification to the MME. NOTE 3: The text regarding "Target Serving GW" shall be ignored. 9. The Serving GW (for Serving GW relocation this will be the Target Serving GW) informs the PDN GW(s) the change of, for example, for Serving GW relocation or the RAT type, that e.g. can be used for charging, by sending the message Modify Bearer Request per PDN connection. Serving Network should be included in this message if it is received in step 4. For Serving GW relocation, the Serving GW allocates DL TEIDs on S5/S8 even for non-accepted bearers. The PDN GW must acknowledge the request with the message Modify Bearer Response (APN Restriction). When the UE moves from Gn/Gp SGSN to the MME, the PDN GW shall send the APN restriction of each bearer context to the Serving GW. If PCC infrastructure is used, the PDN GW informs the PCRF about the change of, for example, the RAT type. The Modify Bearer Response also indicates the identity of the default bearer and the Charging Id towards the S‑GW. NOTE 4: The text regarding "Target Serving GW" shall be ignored. 10. The Serving GW (for Serving GW relocation this will be the Target Serving GW) acknowledges the user plane switch to the Target MME via the message Modify Bearer Response (Cause, Serving GW Tunnel Endpoint Identifier for Control Plane, Serving GW (for Serving GW relocation this will be the Target Serving GW) Address for Control Plane, Protocol Configuration Options, PDN GW addresses and TEIDs (for GTP-based S5/S8) or GRE keys (for PMIP-based S5/S8) at the PDN GW(s) for uplink traffic, APN Restriction).The Serving GW shall forward the received APN Restriction to the MME. At this stage the user plane path is established for all bearers between the UE, Target eNodeB, Serving GW (for Serving GW relocation this will be the Target Serving GW) and PDN GW. In addition, the Modify Bearer Response indicates the identity of the default bearer towards the MME. 11. When the timer started in step 7 expires the Source SGSN will clean-up all its resources towards Source BSS by performing the BSS Packet Flow Delete procedure. When the timer started in step 6 expires the target MME releases the resources that have been allocated for indirect forwarding. NOTE 5: The text regarding "Target Serving GW" shall be ignored. 12. The RAN triggers the UE to initiate a Tracking Area Update procedure with the target MME. It is RAN functionality to provide the ECM CONNECTED UE with the trigger information. The target MME knows that an IRAT Handover has been performed for this UE as it received the bearer context(s) by handover messages and therefore the target MME performs only a subset of the TA update procedure, specifically it excludes the context transfer procedures between source SGSN and target MME. The target MME gets the subscribed UE-AMBR value and the subscribed APN-AMBR value from the HSS during the TA update procedure. If the Subscription Data received from the HSS (during the TAU) contains information that is necessary for the E-UTRAN to be aware of (e.g. a restriction in the UE's permission to use NR as a secondary RAT, Unlicensed Spectrum in the form of LAA/LWA/LWIP/NR-U (as specified in clause 4.3.30) or a combination of them), or an existing UE context in the MME indicates that the UE is not permitted to use NR as a secondary RAT, Unlicensed Spectrum or a combination of them, and the MME has not provided this information to the target eNodeB during step 5 of the Handover preparation phase, then the MME sends an updated Handover Restriction List in the Downlink NAS Transport message that it sends to E-UTRAN. 13. The target MME calculates UE-AMBR as defined in clause 4.7.3. If this calculated value is different from the UE-AMBR computed during step 6, or the APN-AMBR mapped from the subscribed MBR is different from the subscribed APN-AMBR, or the mapped subscribed QoS profile (i.e. the subscribed QoS profile mapped according to Annex E) of the default bearer is different from the EPS Subscribed QoS profile received from the HSS, the new MME shall initiate Subscribed QoS Modification procedure as described in clause 5.4.2.2, Figure 5.4.2.2-1 Annex E (normative): Mapping between EPS and Release 99 QoS parameters This annex specifies how the QoS parameter values of an EPS bearer are mapped to/from the Release 99 QoS parameter values of a PDP context in PDN GW, S4-SGSN and MME. Within this specification, different names are used for the QoS parameters of a PDP context e.g. "R99 QoS profile" and "R99 QoS parameters", but nevertheless the whole QoS IE as described in TS 24.008 [47] is referred to including the R99 and R97/98 QoS attributes. This means that the MME performs QoS mapping, populates and forwards both R99 and R97/98 QoS attributes towards the UE in S1 mode, if the UE supports A/Gb mode or Iu mode or both. The MME also performs QoS mapping, populates and forwards both R99 and R97/98 QoS attributes also on Gn when deployed in the interoperation scenarios as listed in Annex D, clause D.2. The S4-SGSN performs QoS mapping, populates and forwards either both R99 and R97/98 QoS attributes or only R97/98 QoS attributes towards the UE in Iu mode and A/Gb mode. The P-GW performs QoS mapping, populates and forwards both R99 and R97/98 QoS attributes over Gn/Gp when deployed in the interoperation scenarios as listed in Annex D, clause D.2. The following mapping rules hold: - There is a one-to-one mapping between an EPS bearer and a PDP context. - When EPS bearer QoS parameters are mapped to Release 99 QoS parameters the pre-emption capability and the pre-emption vulnerability information of the EPS bearer ARP are ignored and the priority of the EPS bearer parameter ARP is mapped to the Release 99 bearer parameter ARP, as described in table E.1. Table E.1: Mapping of EPS bearer ARP to Release 99 bearer parameter ARP EPS Bearer ARP Priority Value Release 99 bearer parameter ARP Value 1 to H 1 H+1 to M 2 M+1 to 15 3 When Release 99 QoS parameters are mapped to EPS bearer QoS parameters the pre-emption capability and the pre-emption vulnerability information of the EPS bearer ARP are set based on operator policy in the entity that performs the mapping. The Release 99 bearer parameter ARP is mapped to the priority level information of the EPS bearer parameter ARP as described in table E.2. Table E.2: Mapping of Release 99 bearer parameter ARP to EPS bearer ARP Release 99 bearer parameter ARP Value EPS Bearer ARP Priority Value 1 1 2 H+1 3 M+1 The values of H (high priority) and M (medium priority) can be set according to operator requirements to ensure proper treatment of users with higher priority level information. The minimum value of H is 1. The minimum value of M is H+1. From Release 9 onwards, the priority of the EPS bearer parameter ARP is mapped one-to-one to/from the Evolved ARP parameter of a PDP context, if the network supports this parameter. NOTE 1: The setting of the values for H and M may be based on the SGSN mapping from the Release 99 bearer parameter ARP to the ARP parameter that is used for UTRAN/GERAN. NOTE 2: After a handover from UTRAN/GERAN to E-UTRAN the ARP parameter of the EPS bearer can be modified by the P‑GW to re-assign the appropriate priority level, pre-emption capability and pre-emption vulnerability setting. NOTE 3: A mapping from the EPS bearer parameter ARP to the Release 99 bearer parameter ARP is not required for a P‑GW when connected to an SGSN via Gn/Gp as any change of the bearer ARP parameter may get overwritten by the SGSN due to subscription enforcement. However, the P‑GW should not combine services with different EPS bearer ARP values onto the same PDP context to enable a modification of the bearer ARP without impacting the assignment of services to bearers after a handover to E-UTRAN. - The EPS bearer parameters GBR and MBR of a GBR EPS bearer are mapped one-to-one to/from the Release 99 bearer parameters GBR and MBR of a PDP context associated with Traffic class 'conversational' or 'streaming'. - When EPS bearer QoS parameters are mapped to Release 99 QoS parameters the Release 99 bearer parameter MBR of PDP contexts associated with Traffic Class 'interactive' or 'background' is set equal to the value of the authorized APN-AMBR. If the APN-AMBR is modified while the UE accesses the EPS through E‑UTRAN, the UE shall also set the Release 99 bearer parameter MBR to the new APN-AMBR value for all non-GBR PDP contexts of this PDN connection. The P‑GW shall enforce the APN-AMBR across all PDP contexts with Traffic Class 'interactive' and 'background' for that APN. The MME or S4-SGSN may attempt to transfer APN-AMBR and UE-AMBR to a Gn/Gp SGSN - When Release 99 QoS parameters are mapped to EPS bearer QoS parameters the AMBR for the corresponding APN shall be set equal to the MBR value of the subscribed QoS profile. At handover from a Gn/Gp SGSN the MME or S4-SGSN shall provide this APN-AMBR value, if not explicitly received from the Gn/Gp SGSN, to the Serving GW and the PDN GW for each PDN connection. It is required that the subscribed MBR in the HLR/HSS is set to the desired APN-AMBR value for all subscribed APNs which may lead to a selection of a P‑GW. The UE derives the APN-AMBR from the value of the MBR of a PDP context created by the PDP Context Activation Procedure as described in TS 23.060 [7]. NOTE 5: If the pre-Rel-8 UE with the updated subscribed MBR is connected to a GGSN, the GGSN can downgrade the MBR of the PDP contexts based on either local policy or PCC (where the MBR per QCI information is provided to the PCEF). NOTE 6: From Release 9 onwards, the APN-AMBR is available on Gn/Gp. - For handover from a Gn/Gp SGSN and if the MME does not receive AMBR values from the Gn/Gp SGSN, the MME provides a local UE-AMBR to the eNodeB until MME gets the EPS subscribed UE-AMBR. When the MME gets the subscribed UE‑AMBR value from the HSS, it calculates the UE-AMBR (UE-AMBR=MIN (subscribed UE-AMBR, sum APN-AMBR of all active APNs)). Then it compares this value with the local UE-AMBR and if the local UE-AMBR is different from the corresponding derived UE-AMBR, the MME initiates HSS Initiated Subscribed QoS Modification procedure to notify the derived UE-AMBR to the eNodeB. NOTE 7: The local UE-AMBR may be for example based on the summing up of the APN-AMBR values of all active APNs of the UE or on internal configuration. - A standardized value of the EPS bearer parameter QCI is mapped one-to-one to/from values of the Release 99 parameters Traffic Class, Traffic Handling Priority, Signalling Indication, and Source Statistics Descriptor as shown in Table E.3. NOTE 8: When mapping to QCI=2 or QCI=3, the Release 99 parameter Transfer Delay is used in addition to the four Release 99 parameters mentioned above. - When EPS bearer QoS parameters are mapped to Release 99 QoS parameters the setting of the values of the Release 99 parameters Transfer Delay and SDU Error Ratio is derived from the corresponding QCI's Packet Delay Budget and Packet Loss Rate, respectively. When Packet Loss Rate parameter is further mapped to Release 99 QoS parameter Reliability Class (TS 23.107 [59], table 7), the Residual BER is considered <= 2*10-4. Also when Release 99 QoS parameters are mapped to EPS bearer QoS parameters the values of the Release 99 parameter SDU Error Ratio are ignored. - The setting of the values of all other Release 99 QoS is based on operator policy pre-configured in the MME and S4-SGSN. - In networks that support mobility from E‑UTRAN to UTRAN/GERAN, if the UE has indicated support of UTRAN or GERAN, the EPS network shall provide the UE with the Release 99 QoS parameters in addition to the EPS bearer QoS parameters within EPS bearer signalling. Table E.3: Mapping between standardized QCIs and Release 99 QoS parameter values QCI Traffic Class Traffic Handling Priority Signalling Indication Source Statistics Descriptor 1 Conversational N/A N/A Speech 2 Conversational N/A N/A Unknown (NOTE 1) 3 Conversational N/A N/A Unknown (NOTE 2) 4 Streaming N/A N/A Unknown (NOTE 3) 5 Interactive 1 Yes N/A 6 Interactive 1 No N/A 7 Interactive 2 No N/A 8 Interactive 3 No N/A 9 Background N/A N/A N/A NOTE°1: When QCI 2 is mapped to Release 99 QoS parameter values, the Transfer Delay parameter is set to 150 ms. When Release 99 QoS parameter values are mapped to a QCI, QCI 2 is used for conversational/unknown if the Transfer Delay parameter is greater or equal to 150 ms. NOTE°2: When QCI 3 is mapped to Release 99 QoS parameter values, the Transfer Delay parameter is set to 80 ms as the lowest possible value, according to TS 23.107 [59]. When Release 99 QoS parameter values are mapped to a QCI, QCI 3 is used for conversational/unknown if the Transfer Delay parameter is lower than 150 ms. NOTE 3: When QCI 4 is mapped to Release 99 QoS parameter values, it is mapped to Streaming/Unknown and the SDU Error Ratio is set to 10-5 as the closest available value according to TS 23.107 [59]. When Release 99 QoS parameter values are mapped to a QCI, Streaming/Unknown and Streaming/Speech are both mapped to QCI 4. Annex F (normative): Dedicated bearer activation in combination with the default bearer activation at Attach and UE requested PDN connectivity procedures For WB-E-UTRAN, it shall be possible for the PDN GW to initiate the activation of dedicated bearers (as specified in clause 5.4.1) as part of the attach procedure (as specified in clause 5.3.2.1) or as part of the UE requested PDN connectivity procedure (as specified in clause 5.10.2) over WB-E‑UTRAN. However, the result of the dedicated bearer activation procedure shall be logically separate from the Attach procedure, meaning that the result of the Attach procedure is not dependent on whether the Dedicated bearer activation procedure succeeds or not. On the other hand, the dedicated bearer activation may only be regarded as successful if the Attach procedure completes successfully. The messages of the Dedicated bearer activation can be sent together with the messages of the Attach procedure or of the UE requested PDN connectivity procedure (i.e. Attach accept or PDN Connectivity Accept), as shown in the Figure and explanation below. On the S1 and Uu interfaces the messages for the default bearer activation at Attach and UE requested PDN connectivity procedures and for the Dedicated Bearer Activation procedure are combined into a single message. If the MME has sent an Attach Accept message towards the eNodeB, and then the MME receives a Create Bearer Request before the MME receives the Attach Complete message, the MME shall wait for the Attach procedure to complete before the MME continues with Dedicated Bearer Activation procedure. It shall be possible that multiple dedicated bearers can simultaneously be activated in the signalling flow shown below. Figure F.1: Dedicated bearer activation in combination with the default bearer activation at attach or UE requested PDN connectivity NOTE 1: Parameters related to dedicated bearer activation are written in italics. Figure F.1 describes the activation of dedicated bearer(s) in combination with the default bearer activation either as part of the Attach procedure (with specific steps 1a, 7a, 10a) or as part of the UE requested PDN connectivity procedure (with specific steps 1b, 7b, 10b). The following steps below require special attention: 5. (On the P‑GW-S‑GW interface) Create Session Response message of the Attach procedure or UE‑requested PDN connectivity procedure is combined with Create Bearer Request message of the Dedicated Bearer Activation Procedure 6. (On the S‑GW-MME interface) Create Session Response message of the Attach procedure or UE‑requested PDN connectivity procedure is combined with the Create Bearer Request message of the Dedicated Bearer Activation Procedure 7a. For Attach procedure: If the MME receives a Create Session Response message combined with a Create Bearer Request message, the MME shall send the S1-AP Initial Context Setup Request message to the eNodeB, including the NAS parts for both the Attach Accept message of the Attach procedure and the Bearer Setup Request of the Dedicated Bearer Activation Procedure. NOTE 2: The MME shall not send a Bearer Setup Request message of a new Dedicated Bearer Activation procedure to the eNodeB before sending the Attach Accept message of the Attach procedure to the eNodeB. If the MME has already sent the Attach Accept message of the Attach procedure to the eNodeB, the MME shall wait for the Attach Complete message to arrive before sending a separate Bearer Setup Request of a Dedicated Bearer Activation procedure. 7b. For UE requested PDN connectivity procedure: If the MME receives a Create Session Response message combined with a Create Bearer Request message, the MME shall send the S1-AP Bearer Setup Request message to the eNodeB, including the NAS parts for both the PDN Connectivity Accept message and the Bearer Setup Request of the Dedicated Bearer Activation Procedure. 8-9. The radio bearer establishment of the default and dedicated bearer(s) is performed in the same RRC message. 10a. For Attach procedure: The eNodeB sends the S1-AP Initial Context Setup Response message to the MME. The MME shall be prepared to receive this message either before or after, some or all, of the Uplink NAS Uplink Transport messages sent in step 12. 10b. For UE requested PDN connectivity procedure: The eNodeB sends the S1-AP Bearer Setup Response message to the MME. The MME shall be prepared to receive this message either before or after, some or all, of the Uplink NAS Uplink Transport messages sent in step 12. 11. For the Attach procedure: The UE sends the eNodeB a Direct Transfer message containing the Attach Complete (Session Management Response for the Default Bearer) message as response of the attach procedure, and Direct Transfer messages containing the Session Management Responses of the dedicated bearer setup procedure. For the UE requested PDN connectivity procedure: The UE NAS layer builds a PDN Connectivity Complete (Session Management Response) for the Default Bearer Activation and Dedicated Bearer Activation Procedures. The UE then sends Direct Transfer (PDN Connectivity Complete) message to the eNodeB. The NAS messages to establish the EPS bearers shall be handled individually by the UE and be sent in separate RRC Direct Transfer messages. 12. The eNodeB sends an Uplink NAS Transport message to the MME, which contains the NAS messages from the RRC message in step 11. There may be multiple Uplink NAS Transport messages when the UE sends multiple RRC messages containing NAS messages in step 11. 13. Upon reception of the response messages in both step 10 and step 12, the Modify Bearer Request message of the Attach procedure or UE requested PDN connectivity procedure is combined with the Create Bearer Response message of the Dedicated Bearer Activation Procedure. After that, the Serving GW continues with sending a Create Bearer Response message to the PDN GW. Annex G (informative): Void Annex H (normative): Mapping between temporary and area identities The mapping between temporary and area identities is defined in TS 23.003 [9]. Annex I (informative): Guidance for contributors to this specification The following guidance is provided for drafting figures for this specification that contain specific steps which are different in TS 23.402 [2] due to the PMIP-based S5/S8 interface: - Message flows to this specification will contain the complete procedures applicable for GTP-based S5/S8 only. - In this specification, clause(s) of a message flow that is different for PMIP-based S5/S8 interface are shown surrounded by shaded box indexed by an upper-case letter in ascending order, e.g. "A", "B", "C", etc. For example, at the bottom of the flow, the following text should be included: "NOTE: Procedure steps (A) and (B) for an PMIP-based S5/S8 interface are defined in TS 23.402 [2]." - Further guidance for drafting procedures for TS 23.402 [2] can be found in that specification itself. Annex J (informative): High Level ISR description J.1 General description of the ISR concept Idle state Signalling Reduction (ISR) aims at reducing the frequency of TAU and RAU procedures caused by UEs reselecting between E-UTRAN and GERAN/UTRAN which are operated together. Especially the update signalling between UE and network is reduced. But also network internal signalling is reduced. To some extent the reduction of network internal signalling is also available when ISR is not used or not activated by the network. UMTS described already RAs containing GERAN and UTRAN cells, which also reduces update signalling between UE and network. The combination of GERAN and UTRAN into the same RAs implies however common scaling, dimensioning and configuration for GERAN and UTRAN (e.g. same RA coverage, same SGSN service area, no GERAN or UTRAN only access control, same physical node for GERAN and UTRAN). As an advantage it does not require special network interface functionality for the purpose of update signalling reduction. ISR enables signalling reduction with separate SGSN and MME and also with independent TAs and RAs. Thereby the interdependency is drastically minimized compared with the GERAN/UTRAN RAs. This comes however with ISR specific node and interface functionality. SGSN and MME may be implemented together, which reduces some interface functions but results also in some dependencies. ISR support is mandatory for E-UTRAN UEs that support GERAN and/or UTRAN and optional for the network. ISR requires special functionality in both the UE and the network (i.e. in the SGSN, MME and Serving GW) to activate ISR for a UE. For this activation, the MME/SGSN detects whether S-GW supports ISR based on the configuration and activates ISR only if the S-GW supports the ISR. The network can decide for ISR activation individually for each UE. Gn/Gp SGSNs do not support ISR functionality. No specific HSS functionality is required to support ISR. NOTE. A Release 7 HSS needs additional functionality to support the 'dual registration' of MME and SGSN. Without such an upgrade, at least PS domain MT Location Services and MT Short Messages are liable to fail. It is inherent functionality of the MM procedures to enable ISR activation only when the UE is able to register via E-UTRAN and via GERAN/UTRAN. For example, when there is no E-UTRAN coverage there will be also no ISR activation. Once ISR is activated it remains active until one of the criteria for deactivation in the UE occurs, or until SGSN or MME indicate during an update procedure no more the activated ISR, i.e. the ISR status of the UE has to be refreshed with every update. When ISR is activated this means the UE is registered with both MME and SGSN. Both the SGSN and the MME have a control connection with the Serving GW. MME and SGSN are both registered at HSS. The UE stores MM parameters from SGSN (e.g. P-TMSI and RA) and from MME (e.g. GUTI and TA(s)) and the UE stores session management (bearer) contexts that are common for E-UTRAN and GERAN/UTRAN accesses. In idle state the UE can reselect between E-UTRAN and GERAN/UTRAN (within the registered RA and TAs) without any need to perform TAU or RAU procedures with the network. SGSN and MME store each other's address when ISR is activated. When ISR is activated and downlink data arrive, the Serving GW initiates paging processes on both SGSN and MME. In response to paging or for uplink data transfer the UE performs normal Service Request procedures on the currently camped-on RAT without any preceding update signalling (there are however existing scenarios that may require to perform a RAU procedure prior to the Service Request even with ISR is activated when GERAN/UTRAN RAs are used together, as specified in clause 6.13.1.3 of TS 23.060 [7]). The UE and the network run independent periodic update timers for GERAN/UTRAN and for E-UTRAN. When the MME or SGSN do not receive periodic updates MME and SGSN may decide independently for implicit detach, which removes session management (bearer) contexts from the CN node performing the implicit detach and it removes also the related control connection from the Serving GW. Implicit detach by one CN node (either SGSN or MME) deactivates ISR in the network. It is deactivated in the UE when the UE cannot perform periodic updates in time. When ISR is activated and a periodic updating timer expires the UE starts a Deactivate ISR timer. When this timer expires and the UE was not able to perform the required update procedure the UE deactivates ISR. Part of the ISR functionality is also available when ISR is not activated because the MM contexts are stored in UE, MME and SGSN also when ISR is not active. This results in some reduced network signalling, which is not available for Gn/Gp SGSNs. These SGSNs cannot handle MM and session management contexts separately. Therefore all contexts on Gn/Gp SGSNs are deleted when the UE changes to an MME. The MME can keep their MME contexts in all scenarios. J.2 Usage of the TIN The UE may have valid MM parameters both from MME and from SGSN. The "Temporary Identity used in Next update" (TIN) is a parameter of the UE's MM context, which identifies the UE identity to be indicated in the next RAU Request or TAU Request message. The TIN also identifies the status of ISR activation in the UE. The TIN can take one of the three values, "P-TMSI", "GUTI" or "RAT-related TMSI". The UE sets the TIN when receiving an Attach Accept, a TAU Accept or RAU Accept message as specified in table 4.3.5.6-1. "ISR Activated" indicated by the RAU/TAU Accept message but the UE not setting the TIN to "RAT-related TMSI" is a special situation. Here the UE has deactivated ISR due to special situation handling (see clause J.6). By maintaining the old TIN value the UE remembers to use the RAT TMSI indicated by the TIN when updating with the CN node of the other RAT. Only if the TIN is set to "RAT-related TMSI" ISR behaviour is enabled for the UE, i.e. the UE can change between all registered areas and RATs without any update signalling and it listens for paging on the RAT it is camped on. If the TIN is set to "RAT-related TMSI", the UE's P-TMSI and RAI as well as its GUTI and TAI(s) remain registered with the network and valid in the UE. When ISR is not active the TIN is always set to the temporary ID belonging to the currently used RAT. This guarantees that always the most recent context data are used, which means during inter-RAT changes there is always context transfer from the CN node serving the last used RAT. The UE identities, old GUTI IE and additional GUTI IE, indicated in the next TAU Request message, and old P-TMSI IE and additional P-TMSI/RAI IE, indicated in the next RAU Request message depend on the setting of TIN and are specified in table 4.3.5.6-2. The UE indicates also information elements "additional GUTI" or "additional P-TMSI" in the Attach Request, TAU or RAU Request. These information elements permit the MME/SGSN to find the already existing UE contexts in the new MME or SGSN, when the "old GUTI" or "old P-TMSI" indicate values that are mapped from other identities. J.3 ISR activation The information flow in Figure J.3-1 shows an example of ISR activation. For explanatory purposes the figure is simplified to show the MM parts only. The process starts with an ordinary Attach procedure not requiring any special functionality for support of ISR. The Attach however deletes any existing old ISR state information stored in the UE. With the Attach request message, the UE sets its TIN to "GUTI". After attach with MME, the UE may perform any interactions via E-UTRAN without changing the ISR state. ISR remains deactivated. One or more bearer contexts are activated on MME, Serving GW and PDN GW, which is not shown in the figure. The first time the UE reselects GERAN or UTRAN it initiates a Routing Area Update. This represents an occasion to activate ISR. The TIN indicates "GUTI" so the UE indicates a P-TMSI mapped from a GUTI in the RAU Request. The SGSN gets contexts from MME. When the MME sends the context to the SGSN, the MME includes the ISR supported indication only if the involved S-GW supports the ISR. After the ISR activated, both CN nodes keep these contexts because ISR is being activated. The SGSN establishes a control relation with the Serving GW, which is active in parallel to the control connection between MME and Serving GW (not shown in figure). The RAU Accept indicates ISR activation to the UE. The UE keeps GUTI and P-TMSI as registered, which the UE memorises by setting the TIN to "RAT-related TMSI". The MME and the SGSN are registered in parallel with the HSS. After ISR activation, the UE may reselect between E-UTRAN and UTRAN/GERAN without any need for updating the network as long as the UE does not move out of the RA/TA(s) registered with the network. The network is not required to activate ISR during a RAU or TAU. The network may activate ISR at any RAU or TAU that involves the context transfer between an SGSN and an MME. The RAU procedure for this is shown in Figure J.3-1. ISR activation for a UE, which is already attached to GERAN/UTRAN, with a TAU procedure from E-UTRAN works in a very similar way. Figure J.3-1: ISR Activation example J.4 Downlink data transfer Figure J.4-1 shows a downlink data transfer to an idle state UE when ISR is activated. The Serving GW receives downlink data. Because of activated ISR, the Serving GW has control connections with both MME and SGSN and sends therefore downlink data notifications to both nodes. MME and SGSN start their paging procedures, which results in paging of the UE in the registered RA and TA(s) in parallel. In the example illustrated in Figure J.4-1 it is assumed that the UE camps on E-UTRAN. So the UE responds to paging as usual with Service Request. This triggers the MME to setup the user plane connection between eNodeB and Serving GW. The downlink data are transferred to the UE. When the UE camps on UTRAN/GERAN it performs the paging response as specified for these access systems without any required update or other signalling before. The downlink data are then transferred via UTRAN/GERAN to the UE. Figure J.4-1: Downlink data transfer with ISR active J.5 ISR deactivation Deactivation of ISR for the UE does not require any specific functionality. The status of ISR activation is refreshed in every RAU and TAU Accept message. If there is no explicit indication of ISR Activated in these messages then ISR is deactivated and the UE sets its TIN to "GUTI" or "P-TMSI", as specified in Table 4.3.5.6-1. This causes always ISR deactivation when a UE performs a RAU with a Gn/Gp SGSN of any standards release as these SGSNs never indicate "ISR Activated" to the UE. J.6 Handling of special situations Situations may occur that cause unsynchronized state information in the UE, MME and SGSN. Such situations are: - Modification of any EPS bearer context or PDP context which was activated before the ISR is activated in the UE; - At the time when the UE moves from E-UTRAN to GERAN/UTRAN or moves from GERAN/UTRAN to E-UTRAN, if any EPS bearer context or PDP context activated after the ISR was activated in the UE exists; - Missing periodic TA or RA updates, e.g. because the coverage of a RAT is lost or the RAT is no more selected by the UE (this may result also in implicit detach by SGSN or MME); - CN node change resulting in context transfer between the same type of CN nodes (SGSN to SGSN or MME to MME); - Serving GW change (both with and without UE mobility); - Change of the UE specific DRX parameters; - Change of the UE Core Network Capabilities; - E-UTRAN selection by a UTRAN-connected UE (e.g. when in URA_PCH to release Iu on UTRAN side); E-UTRAN selection from GERAN READY state; - GERAN selection by an E-UTRAN-connected UE via Cell Change Order that is not for CS fallback. There are no ISR specific procedures to handle such situations to avoid additional complexity and error cases. All special situations that cause context in the UE, MME and SGSN to become asynchronous are handled by ISR deactivation. The normal RAU/TAU procedures synchronize contexts in MME and SGSN and activate ISR again when wanted by the network. Some specific handling is defined to enable combined MME/SGSN. For this the UE signals at UTRAN RRC level always an Intra Domain NAS Node Selector (IDNNS) derived from the ID signalled as P-TMSI (also when mapped from GUTI). At E-UTRAN RRC level the UE indicates the GUMMEI derived from the GUTI that is signalled in the TAU Request message (also when derived from P-TMSI). This handling is performed by the UE independent from the network configuration. It is not visible to the UE whether MME and SGSN are combined. Given the IP-based architecture of EPS and the IP-based applications such establishment and deactivation of the EPS bearer or PDP context can happen frequently before the UE changes the RAT e.g. a UE asking for delivery of an SMS (over IP) or starting a VoIP over IMS, an entirely new EPS bearer or PDP context may be established for that purpose. Then, after the application/service is finished, the newly established EPS bearer or PDP context gets deactivated. In such particular situation the deactivation of the ISR at the UE and hence performing a RAU or TAU update when the UE changes the RAT is not needed. Preventing the UE from deactivating the ISR in this case ensures an efficient usage of the UE's battery power and reduces the unnecessary signalling load that is seen as the key objective to be achieved by introducing the ISR feature. Thus, UE only locally deactivates ISR when bearer existed at the time of ISR is activated, or when UE changes RAT with bearers which are created after ISR is activated. Annex K (informative): Isolated E-UTRAN Operation for Public Safety K.1 General description of the IOPS concept Isolated E-UTRAN Operation for Public Safety (IOPS) provides the ability to maintain a level of communications for public safety users, via an IOPS-capable eNodeB (or set of connected IOPS-capable eNodeBs), following the loss of backhaul communications. The Isolated E-UTRAN mode of operation is also applicable to the formation of a Nomadic EPS deployment, i.e. a deployment of one or more standalone IOPS-capable eNodeBs, creating a serving radio access network without backhaul communications and also providing local connectivity \(e.g. for IP or Ethernet) and services to public safety users in the absence of normal EPS infrastructure availability. This annex provides implementation and deployment guidelines for the operation of public safety networks in the no backhaul (to Macro EPC) scenario using a Local EPC approach. K.2 Operation of isolated public safety networks using a Local EPC K.2.1 General Description This approach to the provision of isolated operation (e.g. when there is no S1 connectivity to the macro EPC) assumes that the IOPS-capable eNodeB is co-sited with, or can reach, a Local EPC instance which is used in IOPS mode. The Local EPC instance includes at least MME, SGW/PDN GW and HSS functionality. A PLMN identity is dedicated to IOPS mode of operation and is broadcast in System Information by the eNodeB when IOPS mode is in operation. Only authorized IOPS-enabled UEs can access a PLMN indicated as an IOPS PLMN. Support of application services over the IOPS network will be based upon the LTE-Uu radio interface and EPS bearer services supported by the Local EPC. An IOPS network will provide local connectivity services, i.e. for an IP PDN type, IP address assignment and local routing in the IOPS network. For an IP PDN type, During the attachment procedure to the local EPC a local IP address is assigned to the UE as per the standard procedure when attaching to a Macro EPC. The Local EPC acts as a router among the UEs locally attached to the same IOPS network. When operating in IOPS mode IOPS-enabled UEs only use the appropriate USIM credentials defined in the UICC, i.e. those defined exclusively for use in an IOPS PLMN. K.2.2 UE configuration An IOPS-enabled UE has the dedicated IOPS PLMN identity configured in a separate dedicated USIM application as an HPLMN along with the Access Class status of 11 or 15, subject to regional/national regulatory requirements and operator policy. NOTE: Access Class 15 can be reserved for use by network operator personnel who are responsible for critical recovery operations of the network. An IOPS-enabled UE can display information on available PLMNs, including the IOPS PLMN, assisting the user to activate an appropriate USIM application. Subject to user preferences, e.g. to maintain a group communication, the user can perform a manual USIM application switch at any time. When an authorized IOPS-enabled UE, with the dedicated IOPS USIM application activated, selects an IOPS-mode cell, it selects the dedicated IOPS PLMN identity, attaches to the IOPS PLMN (supported by the Local EPC) and is authenticated using security procedures as specified in TS 33.401 [41] and the security credentials from the active IOPS USIM application. K.2.3 IOPS network configuration An IOPS network can comprise either: - a Local EPC and a single isolated IOPS-capable eNodeB, which may be co-located or have connectivity to the Local EPC; or - a Local EPC and two or more IOPS-capable eNodeBs, which have connectivity to a single Local EPC. Existing procedures described in TS 36.300 [5] can be used to achieve dynamic configuration of the S1-MME interface. An IOPS-capable eNodeB can be pre-provisioned with IP endpoint information, relating to the MMEs of one or more candidate Local EPC instances. For each local MME in turn the eNodeB can try to initialize a SCTP association. Once SCTP connectivity has been established, the eNodeB and local MME exchange application level configuration data over the S1-MME application protocol with the S1 Setup Procedure (see TS 36.413 [36]). In line with local operator policies the eNodeB can be provisioned with the IP endpoint of a preferred Local EPC MME instance and the IP endpoints of one or more alternative Local EPC MME instances. The alternative Local EPC instances will be used if an S1-MME path cannot be established with the local MME of the preferred Local EPC instance. All Local EPCs deployed by a public safety authority / operator assume the same PLMN-Id. In order to achieve the broadcast of different TAIs on separate IOPS networks the TACs broadcast by the cells of eNodeBs connected to different Local EPCs are distinct to ensure the required UE mobility behaviour (see clause K.2.5). Therefore, the TAC broadcast by the cells of an eNodeB operating in IOPS mode will be dependent upon the Local EPC to which the eNodeB has established an S1-MME connection. If the scope of service of a Local EPC is a single eNodeB, then all cells served by the eNodeB share the same TAC (assigned for use in IOPS mode) and neighbouring eNodeBs that are also operating in IOPS mode with the same dedicated PLMN-Id are assigned different TACs (resulting in different TAIs) so a TAU attempt is triggered upon mobility. If multiple eNodeBs are configured to be served by a single Local EPC, configuration of TAIs for IOPS can be done according to local operator policies in such a way that a reselection to a cell operating a PLMN in normal mode always triggers an attach request. If sharing the same PLMN-Id, it is assumed the TAC assigned to cells in a Nomadic EPS would be different from the TACs assigned to infrastructure eNodeBs operating in IOPS mode, so as to trigger a TAU between these systems. The support by IOPS network entities of S1-flex and/or eMBMS is up to local operator policy and configuration. K.2.4 IOPS network establishment/termination The decision by an IOPS-capable eNodeB to enter IOPS mode of operation is made in accordance with the local policies of the RAN operator. Such policies can be affected by any RAN sharing agreements that are in place. In situations when the backhaul to the Macro EPC is lost and an eNodeB can start IOPS mode of operation based on local policies, or an eNodeB is deployed as part of a Nomadic EPS, the following eNodeB behaviour is expected: - If the eNodeB can reach a Local EPC for IOPS mode of operation, the eNodeB uses the Local EPC. - If the eNodeB cannot reach a Local EPC, then the eNodeB enters a state where UEs do not attempt to select the cells under its control. In this release of the specification IOPS networks will be established by the independent actions of each eNodeB entering IOPS mode of operation. An IOPS network comprising two or more eNodeBs will be established as a result of multiple eNodeBs entering IOPS mode of operation and establishing S1-MME paths to the local MME of the same Local EPC instance. An eNodeB in IOPS mode of operation, indicates/broadcasts the IOPS PLMN cell(s) as "Not Barred" & "Reserved for Operator Use", for the IOPS PLMN identity, as defined in TS 36.304 [34]. This "Cell Reserved for Operator Use" feature will allow the IOPS-enabled UEs to get access to the IOPS network while barring other non-IOPS-enabled UEs in the same area. The dedicated IOPS USIM application configuration (clause K.2.2) is restricted to use only by users authorised to access a network in IOPS mode of operation. When a backhaul to the Macro EPC is re-established, the S1 connections to the Local EPC are released according to the local IOPS network policies, to move the UEs to Idle mode, and IOPS mode of operation ceases. The PLMN identity of the Macro EPC is announced by the eNodeB so that UEs reselect the normal PLMN and attach afresh to the Macro EPC. Figure K.2.4-1 provides an example of the basic steps involved in IOPS network establishment, access and termination. Figure K.2.4-1: Example of Local EPC based IOPS operation 1) The UE is attached to the Macro EPC accessing normal application (e.g. MCPTT) services. 2) The eNodeB detects loss of the backhaul to the Macro EPC and in accordance with local operator policies decides to activate IOPS mode of operation. The eNodeB prevents any UEs from selecting the cell, using a suitable mechanism such as cell barring, until step 3 and step 4 are completed. 3) Local EPC is activated. NOTE 1: Steps 1, 2 and 3 are not applicable for the Nomadic EPS case. 4) The eNodeB establishes an S1 link to the Local EPC. 5) The eNodeB broadcasts the PLMN identity for IOPS operation with the Local EPC and indicates the IOPS PLMN cell(s) as "Not Barred" & "reserved" for operator use. 6) The UE detects the IOPS PLMN-Id and a decision is made to switch USIM application and the UE activates the IOPS USIM application. NOTE 2: It is out of scope of this specification how the decision is made to switch USIM application. 7) The UE selects the IOPS PLMN-Id. 8) The UE attaches to the Local EPC and, for an IP PDN type, obtains a local IP address, if authorised. 9) Public safety services supported by the IOPS network can be accessed at this time. 10) At some point in time the eNodeB detects that the backhaul to the Macro EPC has been restored. 11) S1 connections to the Local EPC are released according to the IOPS network policies to move the UEs to idle mode. 12) The eNodeB stops its IOPS mode of operation and the Local EPC is de-activated. 13) The eNodeB establishes an S1 link to the Macro EPC. 14) The PLMN-Id of the Macro EPC is announced and the normal TAIs of the Macro EPC are advertised by the eNodeB so that UEs reselect the normal PLMN. 15) The UE detects the PLMN-Id of the Macro EPC and a decision is made to switch USIM application and the UE activates the normal USIM application. NOTE 3: It is out of scope of this specification how the decision is made to switch USIM application. 16) The UE selects the normal PLMN-Id. 17) The UE attaches as normal to the Macro EPC, if authorised. K.2.5 UE mobility A number of distinct UE mobility scenarios can be identified given the following assumptions: - multiple eNodeBs can be configured to be served by a single Local EPC; - a single dedicated PLMN-Id will be advertised by all eNodeBs operating in IOPS mode (of a given public safety authority/operator); - the TACs broadcast by cells (eNodeBs) served by different Local EPCs will be different. The mobility scenarios that can be distinguished are: 1. UE transitions from a cell controlled by the normal macro EPC to a cell operating in IOPS mode; 2. UE transitions from a cell operating in IOPS mode to a cell controlled by the normal macro EPC; 3. UE transitions from a cell operating in IOPS mode whose eNodeB is served by one Local EPC to a cell also operating in IOPS mode whose eNodeB is served by a different Local EPC (Inter-IOPS network cell transition); 4. UE transitions between cells operating in IOPS mode whose eNodeB(s) are served by the same Local EPC (Intra-IOPS network cell transition). The expected mobility behaviour in each of these scenarios is summarised in Table K.2.5-1. Table K.2.5-1: UE mobility behaviour ECM STATE MOBILITY TRANSITION IDLE MODE CONNECTED MODE Normal mode cell to IOPS mode cell Cell re-selection and USIM application switch: - UE performs cell re-selection based Radio link failure followed by cell re-selection: - UE performs radio measurements but source and target cells are on different IOPS mode cell to Normal mode cell upon radio measurements and no suitable cell is found. - UE switches USIM application. - UE performs cell selection and a suitable cell is found. - UE initiates Attach procedure towards Local/Normal EPC. networks. The PLMN-Id of the target cell is not supported by the subscription details in the currently selected USIM application. Handover does not occur. - Radio link failure occurs and UE returns to Idle Mode. - UE proceeds as per behaviour for Idle Mode. Intra-IOPS network cell transition Idle Mode mobility as per normal EPC mobility. As per normal EPC Connected mode mobility procedures. Inter-IOPS network cell transition Idle Mode mobility as per normal EPC mobility. As per normal EPC Connected mode mobility procedures. Annex L (informative): Optimised EPS Architecture option for CIoT L.1 Introduction The EPS Optimised for CIoT includes the support of the following characteristics: - Ultra low UE power consumption. - Large number of devices per cell. - Narrowband spectrum RATs. - Enhanced coverage level. The EPS Optimised for CIoT supports traffic patterns that is different as compared to the normal UEs and may support only sub-set and necessary functionalities as compared with the existing EPS. An EPS Optimised for CIoT can be enabled by having sub-set of functionalities implemented in single logical entity C-SGN (CIoT Serving Gateway Node). C-SGN is described in clause L.4. Mobility and Attach procedures are performed as described in other clauses for corresponding entities MME, S-GW and P-GW. The Core Network node involved in the EPS Architecture optimised for CIoT can be deployed as DCNs within a PLMN. L.2 Non-Roaming Architecture Figure L.2-1: Optimised EPS architecture option for CIoT - Non-roaming architecture L.3 Roaming architecture Figure L.3-1: Optimised EPS architecture option for CIoT - Roaming architecture L.4 C-SGN The C-SGN (CIoT Serving Gateway Node) is a combined node EPC implementation option that minimizes the number of physical entities by collocating EPS entities in the control and user planes paths (e.g. MME, S-GW, P-GW), which may be preferred in CIoT deployments. The external interfaces of C-SGN implementation option are the interfaces of the respective EPC entity supported by the C-SGN, such as MME, S-GW, and P-GW. A C-SGN supports sub-set and necessary functionalities compared with the existing EPS core network elements and also supports at least some of the following CIoT EPS Optimisations: - Control Plane CIoT EPS Optimisation for small data transmission. - User Plane CIoT EPS Optimisation for small data transmission. - Necessary security procedures for efficient small data transmission. - SMS without combined attach for NB-IoT only UEs. - Paging optimisations for coverage enhancements. - Support for non-IP data transmission via SGi tunnelling and/or SCEF. - Support for Attach without PDN connectivity. Annex M (informative): Functions and procedures over NB-IoT RAT In the case of conflict between the information in this Annex and other information in the main body of the present document, the information in the main body takes precedence. The following tables list the functions and procedures that are: - Supported or not supported over NB-IoT RAT, including whether for CP CIoT EPS Optimisation only, UP CIoT EPS Optimisation only or both. - Optional for the UE and/or network when using NB-IoT RAT. NOTE: The tables M-1 to M-5 are ordered by clause number according to the present specification. The table M-6 is ordered by clause number according to TS 23.682 [74]. The notation "CP/UP/Both" indicates whether a particular item is supported for CP CIoT EPS Optimisation only, UP CIoT EPS Optimisation only or both. Table M-1: Clause 4 Concepts Clause Clause title Support NB-IoT RAT CP/UP/Both UE NW 4.3.3 IP header compression RoHC (NAS) Yes CP Optional Optional RoHC (AS) Yes UP Optional Optional 4.3.5 Mobility management functions Yes Both Inter-RAT idle mode NAS mobility (WB-E_UTRAN, UTRAN, GERAN) Yes Both Reachability management Yes Both ISR Optional ISR Optional TA list management (2) Yes Both ISR Yes Both Optional Mobility restrictions Yes Both IMS voice over PS session supported indication No N/A N/A N/A Voice domain preference and UE usage setting No N/A N/A N/A Preferred and supported network behaviour Yes Both 4.3.7.1a.2 GTP-C Overload Control Yes CP N/A 4.3.7.4 MME control of overload Yes Both N/A Extended Access Barring No N/A N/A N/A 4.3.7.4.2.7 Control Plane data specific NAS level congestion control Yes CP 4.3.12 IMS emergency session No N/A N/A N/A 4.3.12a Support of Restricted Local Operator Service No N/A N/A N/A 4.3.13 Closed Subscriber Group No N/A N/A N/A 4.3.17 Support for MTC Low access priority Yes Both Optional Non-IP data delivery (NIDD) Yes Both NIDD SCEF Yes CP N/A (1) Optional (3) NIDD SGi Yes Both N/A (1) Optional (3) 4.3.18 Multimedia Priority Service No N/A N/A N/A 4.3.22 Power Save Mode Yes Both Optional Optional 4.3.27a Restriction of use of Enhanced Coverage for voice centric UE No N/A N/A N/A 4.3.27b Restriction of use of Enhanced Coverage for data centric UE No N/A N/A N/A 4.3.28 Restriction of use of Enhanced Coverage Yes Both Optional 4.3.29 3GPP PS Data Off Yes Both Optional Optional 4.7 QoS PDN connection to SCEF Yes CP Optional Dedicated bearer No N/A N/A N/A GBR bearer No N/A N/A N/A Non-GBR bearer Yes UP Rate control (Serving PLMN) Yes CP Optional Rate control (APN) Yes Both Optional 4.7.8 Inter-UE QoS for NB-IoT UEs using Control Plane CIoT EPS Optimisation Yes Yes N/A Optional 4.10 CIoT EPS Optimisation UP Yes UP Optional Optional CP Yes CP NOTE 1: Whether the non-IP PDN connection is provided via SCEF or over SGi is transparent to the UE. NOTE 2: Required for inter-RAT idle mode mobility. NOTE 3: At least one of NIDD SCEF and NIDD SGi is required. Table M-2: Clause 5.3 Authentication, security and location management Clause Clause title Support NB-IoT RAT CP/UP/Both UE NW 5.3.1 IP address allocation (1) Yes Both Not required for NIDD 5.3.2 Attach procedure Yes Both Normal attach Yes Both Optional (2) Attach without PDN connectivity Yes Both Optional (2) Optional Emergency attach No N/A N/A N/A SMS transfer without Combined Attach Yes Both Optional 5.3.3 TAU procedure Yes (3) Both 5.3.4 Service request procedures Yes Both (4) 5.3.4A Connection Suspend procedure Yes UP 5.3.4B Data transport in CP CIoT EPS Optimisation Yes CP Reliable data delivery with hop-by-hop acknowledgement Yes CP N/A Optional 5.3.5 S1 release procedure Yes (5) 5.3.5A Connection resume procedure Yes UP 5.3.6A PDN GW pause of charging procedure Yes Both N/A Optional 5.3.7 GUTI reallocation procedure Yes Both 5.3.8 Detach procedure Yes (6) Both 5.3.10 Security function Yes Both AS security Yes UP NAS security Yes Both 5.3.14 UE radio capability match request No (7) N/A N/A N/A NOTE 1: Incl. attach without PDN connectivity. NOTE 2: At least one of Normal attach and Attach without PDN connectivity is required. NOTE 3: Incl. inter RAT. NOTE 4: Also supported with CP CIoT EPS Optimisation when the UE/MME also support S1-U data transfer or UP CIoT EPS Optimisation. NOTE 5: Releases the S11-U bearer in the case of CP CIoT EPS Optimisation. RRC Connection release is used with the UE. NOTE 6: ISR aspects optional. NOTE 7: IMS Voice not supported over NB-IoT. Table M-3: Clause 5.4 Session management, QoS and interaction with PCC Clause Clause title Support NB-IoT RAT CP/UP/Both UE NW 5.4.1 Dedicated bearer activation No N/A N/A N/A 5.4.2 Bearer modification with QoS update Yes UP Optional Optional 5.4.3 PDN GW initiated bearer modification without bearer QoS update Yes UP 5.4.4 Bearer deactivation Yes UP 5.4.5 UE-requested bearer resource modification Yes Both Optional with CP CIoT EPS Optimisation 5.4.7 E-UTRAN initiated ERAB modification procedure No (1) N/A N/A N/A 5.4.8 E-UTRAN initiated UE context modification procedure No (1) N/A N/A N/A NOTE 1: Dual connectivity not supported over NB-IoT RAT. Table M-4: Clauses 5.5 and 5.6 Handover and NACC Clause Clause title Support NB-IoT RAT CP/UP/Both UE NW 5.5 Handover No 5.5.1 Intra-E-UTRAN handover No N/A N/A N/A 5.5.2 Inter RAT handover No N/A N/A N/A 5.6 Network assisted cell change No N/A N/A N/A Table M-5: Misc. Clause Clause title Support NB-IoT RAT CP/UP/Both UE NW 5.8 MBMS (2) (2) (2) (2) (2) 5.10 Multiple PDN support and PDN activation for UEs supporting Attach without PDN connectivity Yes (1) Both 5.11 UE capability handling Yes Both 5.12 Warning message delivery No N/A N/A N/A 5.13 DRX and UE-specific DRX parameter handling Yes Both 5.13a Extended idle mode DRX Yes Both Optional Optional 5.15 RAN information management procedures No N/A N/A N/A 5.16 MME-initiated procedure on UE's CSG membership change No N/A N/A N/A 5.17 HeNB multicast packet forwarding function No N/A N/A N/A NOTE 1: Multiple PDN optional. NOTE 2: See Table M-6. Table M-6:MTC/CIoT-related items in TS 23.682 [74] Clause Clause title Support NB-IoT RAT CP/UP/Both UE NW 4.5.14.3 Reliable Data Service Yes CP Optional Optional 4.5.15, 5.14 Support of Packet Flow Description management via SCEF Yes Both N/A Optional 4.5.16 MSISDN-less MO-SMS via T4 Yes Both Optional Optional 4.5.18 MBMS user service for UEs using power saving functions Yes Both Optional Optional 4.5.19 Enhancements to Location Services for CIoT Yes Both Optional Optional NOTE: This table lists MTC/CIoT-related items in TS 23.682 [74] not otherwise specified in the present specification. Annex N (informative): Satellite coverage availability information The protocol and format of satellite coverage availability information to be provisioned to the UE via a PDN connection or SMS is not defined in this release of the specification, but this annex provides some examples on the information that constitutes input to the source of satellite coverage availability information e.g. external server and the output it provides to the UE. Satellite coverage availability information can be indicated to the UE by indications corresponding to whether or not coverage is available for a specific satellite RAT Type for a particular location and time, where: - these indications can be Boolean "True" (e.g. coverage available) and "False" (coverage not available); - locations can correspond to grid points in a fixed array (e.g. rectangular, hexagonal); - coverage availability times may occur at fixed periodic intervals; and - coverage availability information is per RAT Type. The information provisioned to the UE can include coverage information on only one PLMN or multiple PLMNs. If Satellite coverage availability information indicates coverage is available then additional information on whether PLMN is allowed to operate in that location can be provided to the UE. In order for the source of satellite coverage availability information to provide accurate information to the UE, a UE might indicate for example the following information to a source of satellite coverage availability information (e.g. an external server): - Serving PLMN ID (if not already known or implied). - One or more satellite RAT Types (where satellite coverage availability information is then expected for these one or more RAT Types). - List of supported satellite frequency bands (if not implied by the particular RAT Types). - Present UE location (e.g. latitude and longitude) for a reference grid point (e.g. the most Southerly and then most Westerly grid point). - Type of Array (e.g. rectangular or hexagonal). - Minimum elevation angle. Based on the above information provided by the UE, satellite coverage availability information could be delivered to the UE as a sequence of time durations for each grid point where each time duration includes an indication of coverage availability or unavailability one example of many alternatives as illustrated below for a particular grid point with N different durations: Satellite coverage availability information at a given grid point = <N> <Binary 0 or 1><Duration 1> <Binary 0 or 1><Duration 2> . . . . <Binary 0 or 1><Duration N> The above would be concatenated for all of the grid points to produce the satellite coverage availability information. When SMS is used to deliver the satellite coverage availability information, the UE input and satellite coverage availability information output can be delivered in a series of concatenated SMS messages using possibly the same format. Annex O (informative): Example Models of Store and Forward Satellite operation O.1 Introduction This annex provides guidance on deployment options to support Store and Forward Satellite operation. O.2 Model A: Split MME architecture In this architecture option (see Figure O.2-1): 1. eNB is onboard the satellite. 2. MME is split into two functions: a. MME-onboard: the MME part which is onboard the satellite. MME-onboard is in charge of (1) handling the S1 interface with the onboard eNB and (2) handling the NAS protocol signalling from/to UEs via the onboard eNB. b. MME-ground: the MME part which is on the ground network. MME-ground is in charge of handling the rest of interfaces towards other CN functions (e.g. S6a towards HSS, SGd towards SMS-GMSC/IWMSC /SMS Router, T6a towards SCEF, T6ai towards IWF-SCEF, S11 towards SGW). Figure O.2-1: "Split-MME" architecture for supporting Store and Forward Satellite operation for SMS and CP CIoT services The split-MME architecture has below principles: 1. An MME-ground is associated with at least one MME-onboard. An MME-onboard is associated with a Satellite ID identifier. The MME-ground together with the associated MME-onboard(s) behave jointly as a single MME entity. 2. How MME-onboard(s) interacts with MME-ground and how synchronization of the UE context between them is done is outside the scope of 3GPP. NOTE: Based on implementation, the UE context can be uploaded on a subset of MME-onboard(s) or all MME-onboard(s) associated with MME-ground. 3. When a UE initiates a MO procedure that needs an interaction with a core network node on the ground, the MME-onboard stores the MO procedure transaction if the feeder link is not available and synchronizes with the MME-ground when the feeder link becomes available. The MME-ground executes the procedure with the ground network nodes and syncs back the UE context with the MME-onboard when the feeder link becomes available. 4. The MO data is stored in the MME-onboard when the service link is available and the feeder link is unavailable, and transferred to the MME-ground when the feeder link becomes available. The MT data is stored in the MME-ground when the feeder link is unavailable and transferred to the MME-onboard when the feeder link becomes available. The MME-ground determines the satellite through which to send MT data and the MT data is sent to the respective MME-onboard and stored in the MME-onboard when the feeder link is available, and transferred to the UE when service link becomes available. 5. For MO SMS, if the feeder link is not available upon reception of the MO SMS the MME-onboard can store the MO-SMS and can immediately send the delivery report (i.e. RP-ACK) to the UE i.e. as if the MO-SMS has already been successfully delivered to the Service Centre (SC). Once the feeder link is established the MO-SMS is forwarded to the SC. Subsequently the SC sends the RP-ACK to the UE. The MME-ground can also discard the RP-ACK received from the SC. 6. To support UE location verification on satellite, the E-SMLC, if needed, can be deployed on satellite to perform the verification of UE location functionality. 7. For the monitoring event which allows the SCS/AS to be notified of Store and Forward Satellite operation (see clauses 5.6.1.11 and 5.6.3.10 of TS 23.682 [74]) the SCS/AS communicates with HSS and MME-ground to configure and/or delete Monitoring Event. 8. For data transfer, only Control Plane CIoT EPS Optimization applies. 9. During attach procedure, if a UE indicated Control Plane CIoT EPS Optimisation supported in Preferred Network Behaviour, and the UE included the ESM message container, it is handled based on implementation between the MME-onboard and ground CN entities. For example, before or after the successful authentication and Security Mode Command procedure, after the MME-onboard rejects the initial attach of the UE (see clause 4.13.9), the MME-onboard interacts with the MME-ground when the feeder link is available. Then, the MME-ground performs the PDN connection establishment procedure (steps 12-16 of Figure 5.3.2.1-1) with SGW. The MME-ground synchronizes with the MME-onboards regarding the default PDN connection establishment procedure results. After establishing the service link, when the UE initiates the attach procedure with a new MME-onboard again, the new MME-onboard sends Attach Accept message after the successful establishment of the PDN connection. O.3 Model B: Full EPC in each satellite O.3.1 General This clause describes an example of Model B for support of Store and Forward Satellite operation as defined in clause 4.13.9. O.3.2 Architecture and Principles of Operation An example architecture of Model B is shown in Figure O.3.2-1. Each satellite contains the functionally of an eNB plus a full EPC that can include an MME, SGW, PGW, HSS, E-SMLC, SMSC etc. Each satellite further includes an endpoint proxy function that emulates the behaviour of a real endpoint (e.g. an AF) from the perspective of a UE. There is also store and forward functionality on the ground that can be part of, or connected to, an NTN Gateway and that contains the proxy functionality. NOTE: This architecture does not support roaming. Figure O.3.2-1: Example Architecture of Model B Editor's note: Security aspects of the usage of the S&F Proxy are FFS. For Model B, the signalling and procedures used between a UE and satellite to support UE access and UE services in Store and Forward Satellite operation are the same as used between a UE and serving PLMN for normal satellite access except for the differences described in clause 4.13.9. A UE thus sees the onboard eNB and EPC as being equivalent to a serving PLMN for normal operation. Some PLMN services cannot be available for Store and Forward Satellite operation due to subscription restriction for a UE or lack of support by the onboard eNB and/or EPC. A UE accesses and attaches to a satellite for Model B as described in clause 4.13.9. The onboard EPC can obtain the UE location and verify that the UE is allowed to access the PLMN that was selected by the UE. The UE can then establish PDN connections to the onboard EPC and utilise them for the services that are supported in Store and Forward Satellite operation. Depending on what is supported by the onboard eNB and EPC, the UE can perform mobile originated (MO) transactions such as sending SMS, and sending data (e.g. using IP or non-IP protocols) using User Plane or Control Plane CIoT EPS optimisation. Each MO transaction is transferred by the onboard EPC to the onboard endpoint proxy which stores transaction data and signalling (e.g. SMS, data,) and associated protocol and remote endpoint data. The onboard endpoint proxy also returns responses to the UE at a transport and application level that are necessary to allow correct transport and application protocol operation, avoid timeouts and enable a user (if participating) to be aware of the one way communication status. Shortly before satellite coverage will be lost, the onboard EPC can detach the UE. The UE can detach locally if the UE based on implementation can infer the satellite coverage has already moved out of the area where the UE is located. After the UE loses coverage and when the satellite obtains a feeder link to a ground based portion of the serving PLMN selected by the UE for the Attach, the satellite (or the onboard endpoint proxy) transfers data for the UE (e.g. the IMSI and last known UE location), and all of the stored data and signalling for the UE MO transactions, to an S&F function for the serving PLMN. The S&F function might contain a proxy that stores the data and signalling for the UE MO transactions and then forwards the data and signalling for each MO transaction to the associated remote endpoint. The proxy can also receive and store data and signalling for mobile terminated (MT) transactions that can be returned by the remote endpoints to the UE. The S&F function and proxy can simulate continuous reachability of the UE. The MT transaction data and signalling for the UE (e.g. the IMSI) received and stored by the proxy are transferred to one or more satellites that are expected to later provide coverage to the UE. When MT data is transferred to the satellite(s), the onboard endpoint proxy subscribes to the reachability of the UE and optional PDN connectivity status related information for data transmission, e.g. T8 destination address for non-IP data, UE IP address for IP data. When the UE accesses and attaches to the satellite, the endpoint proxy sends MT data to the UE based on the notification from onboard EPC, e.g. sends non-IP data to the T8 destination address or replaces the target IP address for IP data to UE's IP address and sends to PGW. O.3.3 Support of MO and MT Transactions An MO or MT transaction for Model B can correspond to: - Transfer of an SMS message. - Transfer of data to or from a remote endpoint using Control Plane CIoT EPS optimisation or User Plane. Annex P (informative): Change history Change history Date Meeting TDoc CR Rev Cat Subject/Comment New version 2013-06 SP-60 SP-130225 2518 1 A Clarification that IMSVoPS is MMTEL 12.1.0 2013-06 SP-60 SP-130225 2520 2 A Immediate Cancel Location ACK during HSS-initiated detach procedure 12.1.0 2013-06 SP-60 SP-130324 2521 3 B ISR handling in SIPTO at local network 12.1.0 2013-06 SP-60 SP-130324 2538 3 C Direct user plane path establishment for SIPTO at local network on eNodeB 12.1.0 2013-06 SP-60 SP-130305 2540 1 A Clarification on operations related to dual priority 12.1.0 2013-06 SP-60 SP-130232 2541 5 D Correct inconsistency with Stage 1 regarding support for emergency bearer services in the serving network 12.1.0 2013-06 SP-60 SP-130310 2546 5 F Correction to PDN Deactivation for SIPTO@LN 12.1.0 2013-06 SP-60 SP-130232 2557 2 B Individual subscription migration and subscriber troubleshooting 12.1.0 2013-06 SP-60 SP-130232 2559 1 B Addition of End Marker Support for Handover Scenarios with SGW Relocation 12.1.0 2013-06 SP-60 SP-130310 2561 - F Correction on the applicability of SIPTO@LN at a CSG cell 12.1.0 2013-06 SP-60 SP-130232 2562 3 C Use of Low Access Priority Indication to select MME 12.1.0 2013-06 SP-60 SP-130232 2566 3 F Use of MM backoff timer for voice centric devices 12.1.0 2013-09 SP-61 SP-130375 2528 2 A Interoperation between MME and Gn/Gp SGSN 12.2.0 2013-09 SP-61 SP-130384 2567 2 B Introduction of GTP-c Load Control 12.2.0 2013-09 SP-61 SP-130374 2569 2 A Clarifications on QoS and roaming 12.2.0 2013-09 SP-61 SP-130384 2571 2 B GTP-C overload handling 12.2.0 2013-09 SP-61 SP-130379 2574 2 F Correction of SIPTO at Local Network 12.2.0 2013-09 SP-61 SP-130375 2576 1 A Fix equivalent PLMN list handling 12.2.0 2013-09 SP-61 SP-130385 2578 2 C Addition of a note in general description of inter-RAT HO 12.2.0 2013-09 SP-61 SP-130372 2582 2 A Reporting ULI and TimeZone at Network-initiated bearer release related procedures 12.2.0 2013-09 SP-61 SP-130378 2584 2 A Avoiding PDN GW relocation when radio and S1 bearers are active 12.2.0 2013-09 SP-61 SP-130379 2585 1 F Correction of Local Home Network 12.2.0 2013-09 SP-61 SP-130379 2587 1 F Clarification on deactivating SIPTO@LN upon idle mode mobility 12.2.0 2013-12 SP-62 SP-130524 2554 4 A DL traffic mapping alignment with TS 23.060. 12.3.0 2013-12 SP-62 SP-130524 2590 1 A Clarification on the handling non-MM message during handover 12.3.0 2013-12 SP-62 SP-130726 2594 12 B Core Network assisted eNodeB parameters tuning 12.3.0 2013-12 SP-62 SP-130524 2597 2 A Handling of uplink packet filters and definition for a valid state of the TFT setting 12.3.0 2013-12 SP-62 SP-130669 2598 6 B PDN GW and SGW Charging alignment in downlink 12.3.0 2013-12 SP-62 SP-130526 2600 1 F Correction on the conditions for including the Local Home Network ID 12.3.0 2013-12 SP-62 SP-130526 2602 1 F Clarification for Optimisation of LIPA and SIPTO@LN paging 12.3.0 2013-12 SP-62 SP-130529 2603 9 B Introducing UE Power Saving Mode 12.3.0 2013-12 SP-62 SP-130540 2605 2 F Addition of a note addressing the behavior of network side during inter-RAT 3GPP PS Handover 12.3.0 2013-12 SP-62 SP-130526 2607 1 F Deactivate ISR for SIPTO@LN 12.3.0 2013-12 SP-62 SP-130526 2610 - F Correction in Local Home Network ID definition 12.3.0 2013-12 SP-62 SP-130526 2611 1 F Corrections in handover and TAU/RAU procedures related to SIPTO at local network 12.3.0 2013-12 SP-62 SP-130526 2612 - F Correcting reference to the SIPTO@LN clause 12.3.0 2013-12 SP-62 SP-130534 2613 2 F Use of LAPI for MME/SGSN selection during handover 12.3.0 2013-12 SP-62 SP-130523 2616 - A Local deactivation of ISR to resume packet services 12.3.0 2013-12 SP-62 SP-130524 2621 3 A Fix downlink packet delivery failure due to crash with mobility event 12.3.0 2013-12 SP-62 SP-130533 2622 - B HPLMN Notification with specific indication due to MME initiated Bearer removal 12.3.0 2013-12 SP-62 SP-130534 2623 5 B Reporting ULI and TimeZone at MME-initiated bearer related procedures 12.3.0 2013-12 SP-62 SP-130533 2624 - F Correction on the network management functions 12.3.0 2013-12 SP-62 SP-130533 2625 2 F Rollback behaviour for EPC 12.3.0 2013-12 SP-62 SP-130583 2627 5 B Introduction of ULI reporting at PCC area level 12.3.0 2013-12 SP-62 SP-130585 2629 3 B Introduction of ULI reporting only when the UE is in 'CONNECTED' state 12.3.0 2013-12 SP-62 SP-130534 2632 1 F Modification on Inter-RAT Handover from UTRAN/GERAN to E-UTRAN 12.3.0 2014-03 SP-63 SP-140111 2634 2 F Corrections for the PDN GW pause of charging functionality 12.4.0 2014-03 SP-63 SP-140106 2635 2 F Corrections for presence reporting area based location reporting 12.4.0 2014-03 SP-63 SP-140108 2636 2 F Delayed release of UE IP address during inter-RAT 3GPP PS Handover 12.4.0 2014-03 SP-63 SP-140106 2637 2 B Presence Reporting Area provided by OCS 12.4.0 2014-03 SP-63 SP-140104 2638 3 F Power Saving Mode applicability 12.4.0 2014-03 SP-63 SP-140111 2641 2 F Fix downlink message delivery failure due to crash with mobility event 12.4.0 2014-03 SP-63 SP-140098 2644 - A Correction of IETF reference on prefix delegation 12.4.0 2014-06 SP-64 SP-140255 2654 1 A Add PCO handling to the PDN GW initiated bearer modification procedure 12.5.0 2014-06 SP-64 SP-140377 2655 2 F PDN GW pause of charging functionality and inter-operator charging 12.5.0 2014-06 SP-64 SP-140272 2656 1 F Correction of possible PDN GW actions during PDN connection termination 12.5.0 2014-06 SP-64 SP-140262 2658 3 B Introduction of Dual Connectivity Function 12.5.0 2014-06 SP-64 SP-140256 2660 3 A IRAT handover MME handling 12.5.0 2014-06 SP-64 SP-140251 2663 1 A Correction on priority paging 12.5.0 2014-06 SP-64 SP-140377 2672 - F Handling of MME UE S1AP ID in case of S1 release 12.5.0 2014-06 SP-64 SP-140257 2679 5 F Clarifying when the PDN GW can set ULI reporting, CSG reporting and PRA reporting 12.5.0 2014-06 SP-64 SP-140263 2680 1 F Clarification on ISR for PSM UE 12.5.0 2014-06 SP-64 SP-140257 2681 1 F Clarifications for presence reporting area based location reporting 12.5.0 2014-06 SP-64 SP-140263 2683 2 F Clarifications for Power Savings Mode 12.5.0 2014-06 SP-64 SP-140263 2684 9 F CN Assistance information for eNodeB parameters setting 12.5.0 2014-06 SP-64 SP-140256 2689 2 A Clarification on MME behaviour on roaming situation 12.5.0 2014-06 SP-64 SP-140377 2693 3 F Inter PLMN handover for emergency bearer service 12.5.0 2014-06 SP-64 SP-140377 2694 5 F Correction to the MME initiated bearer setup during the TAU procedure 12.5.0 2014-06 SP-64 SP-140377 2695 1 F PDN GW initiated bearer request message arrival during the TAU 12.5.0 2014-06 SP-64 SP-140257 2696 3 F Correction of ULI reporting only when the UE is in 'CONNECTED' state 12.5.0 2014-06 SP-64 SP-140270 2697 4 B Traffic steering for RAN-based WLAN interworking solution 12.5.0 2014-06 SP-64 SP-140262 2707 4 B Introduction of Dual Connectivity Operation 12.5.0 2014-06 SP-64 SP-140377 2715 2 F Correction on the description of Location Service function 12.5.0 2014-09 SP-65 SP-140427 2722 1 B Changes and corrections related to GTP-C Load/Overload Control feature 12.6.0 2014-09 SP-65 SP-140490 2727 4 F Clarifications for PRA reporting 12.6.0 2014-09 SP-65 SP-140424 2735 3 F Update of 'WLAN offloadability' indication via NAS 12.6.0 2014-09 SP-65 SP-140429 2723 1 F Clarification on roaming subscription corresponding to specific RAT for TS 23.401 13.0.0 2014-09 SP-65 SP-140428 2728 2 B Introducing RAN Congestion Awareness Function 13.0.0 2014-09 SP-65 SP-140428 2733 2 B Introduction of User plane congestion management function 13.0.0 2014-12 SP-66 SP-140688 2731 7 B Paging policy differentiation for IMS voice 13.1.0 2014-12 SP-66 SP-140675 2746 - A Handling of E-UTRAN Inter RAT Handover information at PS Handover from GERAN 13.1.0 2014-12 SP-66 SP-140686 2747 2 A Paging enhancements for Low Complexity UE 13.1.0 2014-12 SP-66 SP-140680 2752 1 A Correction of the CN assisted eNodeB parameter tuning 13.1.0 2014-12 SP-66 SP-140686 2754 1 A Pending Subscription Change 13.1.0 2014-12 SP-66 SP-140684 2756 - A Support of non-seamless offloading with RAN rules 13.1.0 2014-12 SP-66 SP-140684 2758 1 A Clarification on the RAN assistance parameters based on RAN WGs agreements 13.1.0 2014-12 SP-66 SP-140674 2759 3 A Clarifications for TFT handling 13.1.0 2014-12 SP-66 SP-140685 2761 1 A Clarifications for Multimedia Priority Services 13.1.0 2014-12 SP-66 SP-140684 2764 1 A Clarification of WLAN offload indication from MME in E-UTRAN 13.1.0 2014-12 SP-66 SP-140678 2769 2 A QoS handling at inter-RAT mobility 13.1.0 2014-12 SP-66 SP-140672 2773 1 A Correction of 'extended wait timers' in RRC signalling 13.1.0 2014-12 SP-66 SP-140685 2779 1 A Correction to the Low Access Priority Indication use by the network 13.1.0 2014-12 SP-66 SP-140689 2780 3 F Adding interoperability aspects between RAN and CN for the CN-based solution 13.1.0 2014-12 SP-66 SP-140669 2786 1 A Handling CS Service Notification received during handover 13.1.0 2014-12 SP-66 SP-140685 2789 1 A Clarification to non-3GPP access to 3GPP access handover procedure 13.1.0 2014-12 SP-66 SP-140687 2790 2 A E-UTRAN initiated E-RAB modification procedure update 13.1.0 2014-12 SP-66 SP-140689 2797 - C MME - RCAF interface 13.1.0 2014-12 SP-66 SP-140670 2810 1 A UE capability storage in the MME 13.1.0 2015-03 SP-67 SP-150024 2805 5 F Enhancements when determine the list of UEs served by a E-UTRAN cell 13.2.0 2015-03 SP-67 SP-150109 2812 2 A Paging priority setting in the MME 13.2.0 2015-03 SP-67 SP-150021 2821 1 A Clarify handling of "MS Info Change Reporting Action" at change of Serving Node for an UE. 13.2.0 2015-03 SP-67 SP-150025 2822 4 B Group specific NAS Level congestion control 13.2.0 2015-03 SP-67 SP-150109 2825 1 A Downlink packet delivery failure during mobility event 13.2.0 2015-03 SP-67 SP-150027 2840 2 C Paging Priority for Push To Talk 13.2.0 2015-03 SP-67 SP-150027 2842 1 F Fixing the MME behaviour for NAS message transfer 13.2.0 2015-06 SP-68 SP-150230 2831 1 A Correcting ESM re-activation attempts at PLMN change when only one IP version is supported by the network 13.3.0 2015-06 SP-68 SP-150234 2837 11 B Introduce the Dedicated Core Network (DECOR) feature 13.3.0 2015-06 SP-68 SP-150237 2843 2 B APN and group specific NAS Level congestion control 13.3.0 2015-06 SP-68 SP-150236 2850 2 B Update to PSM to support monitoring events 13.3.0 2015-06 SP-68 SP-150236 2851 2 B Support for Monitoring Events 13.3.0 2015-06 SP-68 SP-150237 2853 - C MCC CR Implementation correction: Group specific NAS Level congestion control 13.3.0 2015-06 SP-68 SP-150239 2857 1 F Paging priority and ARP Priority level: extension of CR2812r2 to CR2840r2 13.3.0 2015-06 SP-68 SP-150229 2861 3 A MS Info Change Reporting Action at change of Serving Node (MME <--> SGSN): Update of call Flows 13.3.0 2015-06 SP-68 SP-150238 2862 3 B Introducing functions for High latency communication 13.3.0 2015-06 SP-68 SP-150234 2864 3 B Adding support for load re-balancing within DCN 13.3.0 2015-06 SP-68 SP-150239 2865 - F User CSG Information in TAU/RAU with SGW change procedure 13.3.0 2015-06 SP-68 SP-150237 2866 3 F Group specific NAS Level congestion control for multiple APNs 13.3.0 2015-06 SP-68 SP-150236 2871 2 B Monitoring event configuration in the HSS and MME 13.3.0 2015-06 SP-68 SP-150235 2872 2 B HSS and MME updates for AESE 3GPP resource optimisations based on providing predictable communication patterns of a UE to the MME 13.3.0 2015-06 SP-68 SP-150230 2876 1 A Dual connectivity handling for the failed E-RAB(s) 13.3.0 2015-06 SP-68 SP-150237 2877 1 F Clarification of Group specific NAS Level congestion control 13.3.0 2015-06 SP-68 SP-150284 2869 2 A Clarification on Network Triggered Service Request 13.3.0 2015-09 SP-69 SP-150502 2883 3 B Introducing eDRX for High latency communication 13.4.0 2015-09 SP-69 SP-150502 2884 - F Non-Applicability of HLCom Monitoring Events feature to Gn/Gp-SGSN 13.4.0 2015-09 SP-69 SP-150501 2887 1 B Introducing the solution for S/P-GW retransmissions when handling Network originated control plane procedure 13.4.0 2015-09 SP-69 SP-150501 2889 2 B Introducing extended Idle mode DRX feature to LTE 13.4.0 2015-09 SP-69 SP-150505 2891 - F Add reference to the MME/SGSN selection function 13.4.0 2015-09 SP-69 SP-150505 2892 3 B Paging optimisations 13.4.0 2015-09 SP-69 SP-150490 2894 1 A Adding PSM parameters in the MME/UE contexts 13.4.0 2015-09 SP-69 SP-150502 2895 1 F Clarification of High latency communication 13.4.0 2015-09 SP-69 SP-150496 2898 1 F Corrections for dedicated core network procedures 13.4.0 2015-09 SP-69 SP-150496 2900 1 F Enhanced HO procedure for DECOR 13.4.0 2015-09 SP-69 SP-150491 2902 - A Correction of Access network selection and traffic steering based on RAN-assisted WLAN interworking 13.4.0 2015-09 SP-69 SP-150493 2903 2 B Add informative annex containing implementation and deployment guidelines for IOPS 13.4.0 2015-12 SP-70 SP-150609 2905 3 F Update for UE Reachability Notifications 13.5.0 2015-12 SP-70 SP-150615 2906 2 B UE radio capability for paging optimisation 13.5.0 2015-12 SP-70 SP-150603 2912 4 F Correct inconsistencies in the description of USIM switching 13.5.0 2015-12 SP-70 SP-150606 2915 3 F UE Usage Type in handovers 13.5.0 2015-12 SP-70 SP-150611 2916 9 B Paging for extended idle mode DRX in LTE 13.5.0 2015-12 SP-70 SP-150603 2920 1 F Corrections related to public safety network operator and IOPS network 13.5.0 2015-12 SP-70 SP-150606 2921 2 F UE Usage Type in Re-route message 13.5.0 2015-12 SP-70 SP-150615 2924 1 F Correction to PDN GW initiated bearer deactivation 13.5.0 2015-12 SP-70 SP-150796 2926 4 F Clarification of QoS modifications restrictions 13.5.0 2015-12 SP-70 SP-150606 2927 2 F Retrieval of UE Usage Type from HSS 13.5.0 2015-12 SP-70 SP-150615 2928 3 F Inclusion of RAN/NAS Cause in Delete Bearer Response 13.5.0 2015-12 SP-70 SP-150611 2929 1 F Clarification on using eDRX in case of emergency bearer services 13.5.0 2015-12 SP-70 SP-150615 2935 3 B Addition of CRLWI support 13.5.0 2015-12 SP-70 SP-150606 2936 1 F Providing IMSI in DÉCOR redirection procedure 13.5.0 2015-12 SP-70 SP-150606 2943 - F Enhanced HO procedure for DECOR 13.5.0 2015-12 SP-70 SP-150737 2917 3 B Enhanced Coverage for paging in LTE 13.5.0 2016-03 SP-71 SP-160161 2930 11 B Introduction of solution 18 - suspend and resume procedure 13.6.0 2016-03 SP-71 SP-160161 2934 9 B Introducing support for Non-IP data for CIoT 13.6.0 2016-03 SP-71 SP-160161 2941 5 B Introducing CIoT Optimisations 13.6.0 2016-03 SP-71 SP-160161 2942 13 B Introduction of Control Plane CIoT EPS optimisation 13.6.0 2016-03 SP-71 SP-160161 2948 8 B Introduction of support for NB-IoT 13.6.0 2016-03 SP-71 SP-160161 2951 9 B Introduction of attach procedure changes for CIoT EPS Optimisation. 13.6.0 2016-03 SP-71 SP-160156 2953 - A Correction in MME triggered Serving GW relocation procedure 13.6.0 2016-03 SP-71 SP-160161 2954 3 B Detach procedure for CIoT optimisation 13.6.0 2016-03 SP-71 SP-160163 2958 1 F Fix wrong wording on DNS procedure for DECOR 13.6.0 2016-03 SP-71 SP-160161 2959 4 B TAU procedure update for CIoT EPS Optimisation 13.6.0 2016-03 SP-71 SP-160163 2961 1 F Alignment of support for DECOR in shared networks 13.6.0 2016-03 SP-71 SP-160161 2965 2 B CIoT-centric single node EPS architecture 13.6.0 2016-03 SP-71 SP-160164 2966 2 F Handling of a 5.12s eDRX cycle 13.6.0 2016-03 SP-71 SP-160162 2976 2 F List of External Identifiers in the Subscription Data 13.6.0 2016-03 SP-71 SP-160161 2977 2 B UE Capability Handling for Control Plane CIoT EPS optimisation 13.6.0 2016-03 SP-71 SP-160161 2980 4 B Disabling IRAT mobility to and from NB-IOT 13.6.0 2016-03 SP-71 SP-160161 2981 3 B Support for overload control 13.6.0 2016-03 SP-71 SP-160161 2982 2 B HLcom feature update for CP optimisation 13.6.0 2016-03 SP-71 SP-160161 2985 1 B RAU procedure update for CIoT EPS Optimisation 13.6.0 2016-03 SP-71 SP-160161 2986 3 B TAU procedure update with Gn/Gp SGSN for CIoT EPS optimisation 13.6.0 2016-03 SP-71 SP-160161 2988 2 B Handover for non-NB-IoT devices using CIoT optimisations 13.6.0 2016-03 SP-71 SP-160161 2989 1 B DRX handling for NB-IoT 13.6.0 2016-03 - - - - - MCC correction to change positions of (new) clauses 4.10 and 4.11 for more logical clause ordering 13.6.1 2016-06 SP-72 SP-160292 2956 7 B Support of CSG, LIPA, and SIPTO@LN functions for dual connectivity 13.7.0 2016-06 SP-72 SP-160298 2964 2 B Priority Treatment based on RRC Establishment Cause 13.7.0 2016-06 SP-72 SP-160286 2992 3 F Alignment of S11-U procedures with stage 3 13.7.0 2016-06 SP-72 SP-160286 2993 3 F Correction of CIoT inter-RAT handover conditions 13.7.0 2016-06 SP-72 SP-160286 2994 4 F Corrections for Header Compression in CP optimisation 13.7.0 2016-06 SP-72 SP-160286 2995 8 F Simultaneous support for CP and UP optimisation 13.7.0 2016-06 SP-72 SP-160286 2996 1 F Paging for CE in CP optimisation 13.7.0 2016-06 SP-72 SP-160286 2997 3 F Support for SMS using CP optimisation 13.7.0 2016-06 SP-72 SP-160286 2998 4 C Active flag handling for Control Plane CIoT Optimisation 13.7.0 2016-06 SP-72 SP-160286 2999 8 F Support for rate control of CIoT data 13.7.0 2016-06 SP-72 SP-160286 3000 1 F IRAT stage 3 reattach alignment 13.7.0 2016-06 SP-72 SP-160298 3002 1 F 'UE reachability' event reports for UEs using extended idle mode DRX 13.7.0 2016-06 SP-72 SP-160286 3008 1 F Introduction of S11-U TEID for Control Plane CIoT EPS optimisation 13.7.0 2016-06 SP-72 SP-160286 3012 1 F Clarification of the S1 release procedure usage in context of CIOT CP EPS Optimisation 13.7.0 2016-06 SP-72 SP-160286 3013 1 F Alignment of MME selection in Attach and TAU procedures with clause 4.3.8.3 'MME selection function' 13.7.0 2016-06 SP-72 SP-160286 3014 1 F Network features need to be consistent across TAI LIST 13.7.0 2016-06 SP-72 SP-160286 3015 4 F RRC layer impacts and System information usage in attach procedure 13.7.0 2016-06 SP-72 SP-160286 3017 - F Clarification on CIoT EPS Optimisation conflicting terminology 13.7.0 2016-06 SP-72 SP-160286 3022 - F Handover support for Header Compression in CP optimisation 13.7.0 2016-06 SP-72 SP-160289 3023 2 F Pending data and user inactivity 13.7.0 2016-06 SP-72 SP-160286 3026 3 F Support for UP optimisation from CP optimisation in ECM-IDLE state 13.7.0 2016-06 SP-72 SP-160286 3035 2 F Correction on MME overload control for CIOT 13.7.0 2016-06 SP-72 SP-160286 3041 1 F Introduction of Connection Establishment Indication procedure 13.7.0 2016-06 SP-72 SP-160286 3042 - F Updates of handover procedures for CIoT Optimisation 13.7.0 2016-06 SP-72 SP-160286 3046 1 F MME selection for CIoT Optimisation 13.7.0 2016-06 SP-72 SP-160286 3049 1 F TAU trigger for Preferred Network Behaviour change 13.7.0 2016-06 SP-72 SP-160286 3051 - F Handling of Exception Reports in the Core Network 13.7.0 2016-06 SP-72 SP-160299 2971 5 B Addition of eCall for IMS Emergency Services 14.0.0 2016-06 SP-72 SP-160303 3024 2 B UE assisted DCN selection 14.0.0 2016-09 SP-73 SP-160653 3050 8 B Support of Multiple PRAs 14.1.0 2016-09 SP-73 SP-160648 3052 1 B Adding support for NonIP & SCEF in GERAN 14.1.0 2016-09 SP-73 SP-160633 3058 1 A Clarifying PDN GW & SCEF role in APN Rate Control 14.1.0 2016-09 SP-73 SP-160649 3059 1 C Load balancing for MMEs with multiple DCN support 14.1.0 2016-09 SP-73 SP-160633 3062 1 A Clarification of new active flag handling for CP CIoT EPS Optimisation 14.1.0 2016-09 SP-73 SP-160649 3063 1 B Relation between the Usage Type and DCN ID 14.1.0 2016-09 SP-73 SP-160649 3064 2 B The DCN ID related serving PLMN information 14.1.0 2016-09 SP-73 SP-160633 3068 - A Updates of eDRX for NB-IoT 14.1.0 2016-09 SP-73 SP-160633 3072 1 A Voice related indication for NB-IoT 14.1.0 2016-09 SP-73 SP-160633 3074 1 A Priority handling of NAS signalling and CIoT data over NAS 14.1.0 2016-09 SP-73 SP-160649 3078 1 F Clarification on usage of default standardized or PLMN specific DCN-ID. 14.1.0 2016-09 SP-73 SP-160633 3083 - A Transfer of cell/TAC's RAT type to MME 14.1.0 2016-09 SP-73 SP-160634 3085 1 A Release Assistance Information for pair of packets 14.1.0 2016-09 SP-73 SP-160652 3087 1 B Handling of handovers for emergency sessions over WLAN 14.1.0 2016-09 SP-73 SP-160659 3088 2 C Operator management of eDRX parameters 14.1.0 2016-09 SP-73 SP-160634 3091 2 A Clarification on S1-U establishment during CP optimisation is in use 14.1.0 2016-09 SP-73 SP-160634 3094 - A Correction of Connection Suspend 14.1.0 2016-09 SP-73 SP-160634 3099 1 A Correction to reporting of MO exception data 14.1.0 2016-09 SP-73 SP-160652 3100 1 B PDN GW selection for emergency services with unauthenticated UEs 14.1.0 2016-09 SP-73 SP-160658 3101 1 B Adding eNodeB change reporting in Location Change Reporting Procedure 14.1.0 2016-09 SP-73 SP-160634 3105 2 A Multiple DRB capability handling 14.1.0 2016-09 SP-73 SP-160649 3106 - C DCN Congestion Control 14.1.0 2016-09 SP-73 SP-160649 3107 1 C DCN-ID update 14.1.0 2016-09 SP-73 SP-160634 3109 1 A Clarification on CP only indicator for SGi PDN connections 14.1.0 2016-09 SP-73 SP-160635 3111 1 A Correction on Bearer Synchronization for UP CIoT EPS optimisation 14.1.0 2016-09 SP-73 SP-160635 3112 2 A Control Plane Only PDN Connection Indication in PDN setup 14.1.0 2016-09 SP-73 SP-160635 3120 2 A Handling of S11-U bearer during service request procedure 14.1.0 2016-09 SP-73 SP-160635 3122 1 A Correction of UE-AMBR and APN-AMBR handling for CIoT EPS Optimisation 14.1.0 2016-09 SP-73 SP-160658 3123 1 B Adding eNodeB change reporting to message flows 14.1.0 2016-09 SP-73 SP-160635 3128 3 A Clarification on NAS level congestion for exception reporting. 14.1.0 2016-09 SP-73 SP-160635 3129 1 A Clarification on EAB and low access priority indication in RRC over NB-IOT 14.1.0 2016-12 SP-74 SP-160807 3070 4 A NAS PDU retransmission strategy for CIoT Optimisation 14.2.0 2016-12 SP-74 SP-160817 3130 1 F Corrections for allowing seamless handovers of emergency sessions to WLAN 14.2.0 2016-12 SP-74 SP-160823 3131 4 C Reliable UE delivery based on hop-by-hop acknowledgements (5c) 14.2.0 2016-12 SP-74 SP-160823 3135 4 B Authorization of use of Coverage Enhancement 14.2.0 2016-12 SP-74 SP-160825 3137 1 F Clarifying the UE behaviour for switch to UP 14.2.0 2016-12 SP-74 SP-160807 3139 - A Correction of handling of resume cause 14.2.0 2016-12 SP-74 SP-160807 3141 1 A APN Rate Control and emergency bearer service 14.2.0 2016-12 SP-74 SP-160823 3143 2 B Control Plane data back-off timer introduction 14.2.0 2016-12 SP-74 SP-160825 3144 2 F Missing indirect forwarding tunnel deletion in TAU with SGW change 14.2.0 2016-12 SP-74 SP-160823 3145 2 B Support for Inter-UE QoS for NB-IoT Control Plane Optimisation 14.2.0 2016-12 SP-74 SP-160807 3148 2 A Aligning specifications - no RAT type in the Initial UE Message 14.2.0 2016-12 SP-74 SP-160807 3151 1 A Correction on MT Data transport using CP CIoT EPS Optimisation 14.2.0 2016-12 SP-74 SP-160823 3152 3 B CIoT_KI7_Sol9 - Overload Start for control plane data 14.2.0 2016-12 SP-74 SP-160818 3153 2 F MME report for set of PRA 14.2.0 2016-12 SP-74 SP-160807 3154 1 A Clarification on APN Rate Control 14.2.0 2016-12 SP-74 SP-160823 3156 2 B UE radio capability handling for UEs supporting NB-IoT and WB-E-UTRAN 14.2.0 2016-12 SP-74 SP-160808 3158 - A Correction to reporting of MO exception data 14.2.0 2016-12 SP-74 SP-160810 3159 1 A UE Usage Type Withdraw 14.2.0 2016-12 SP-74 SP-160826 3161 4 B Introduction of PS Data Off feature 14.2.0 2016-12 SP-74 SP-160823 3163 2 B Location service message size adaptation according to coverage level 14.2.0 2016-12 SP-74 SP-160823 3164 2 B Inter-RAT idle mode mobility to and from NB-IoT 14.2.0 2017-03 SP-75 SP-170053 3167 1 F RAB Setup information in the IRAT handover 14.3.0 2017-03 SP-75 SP-170050 3169 2 F Corrections of UE capability information to eNodeB for CP CIoT UEs 14.3.0 2017-03 SP-75 SP-170050 3170 1 F Correction of CE authorization in TAU 14.3.0 2017-03 SP-75 SP-170050 3171 1 F Support for restriction of Enhanced coverage restriction per RAT 14.3.0 2017-03 SP-75 SP-170050 3172 2 F Enhanced Coverage Restricted parameter in S1-AP in TAU 14.3.0 2017-03 SP-75 SP-170050 3173 1 F Location reporting using Control Plane CIOT EPS Optimisation 14.3.0 2017-03 SP-75 SP-170043 3175 2 A No need to support UE requested bearer resource modification for CP CIOT 14.3.0 2017-03 SP-75 SP-170043 3177 4 A No support for Serving PLMN Rate Control across multiple PDN connections 14.3.0 2017-03 SP-75 SP-170043 3179 1 A Indication for support of User Plane CIOT Optimisation to E-UTRAN 14.3.0 2017-03 SP-75 SP-170043 3181 4 A Correction of Serving PLMN rate control 14.3.0 2017-03 SP-75 SP-170050 3188 1 F Restriction of use of Coverage Enhancement clarification for roaming UEs 14.3.0 2017-03 SP-75 SP-170042 3195 3 A Priority Treatment based on RRC Establishment Cause 14.3.0 2017-03 SP-75 SP-170052 3200 1 C TS 23.401 support for transport level packet marking 14.3.0 2017-03 SP-75 SP-170050 3202 2 F Correction to the Control Plane data back-off timer 14.3.0 2017-03 SP-75 SP-170042 3209 1 A Restriction of CE Mode B with dedicated bearer requirements 14.3.0 2017-06 SP-76 SP-170370 3210 3 F Clarification for PDN GW handling of IMS services at 3GPP PS Data Off activation 14.4.0 2017-06 SP-76 SP-170361 3214 1 A Correction Serving PLMN Rate Control and APN Rate Control 14.4.0 2017-06 SP-76 SP-170361 3219 1 A Correction of forwarding of MO Exception Data Counter 14.4.0 2017-06 SP-76 SP-170367 3221 2 F Handling of emergency call numbers received from WLAN 14.4.0 2017-06 SP-76 SP-170365 3222 1 F Radio capabilities for eCall Only Mode 14.4.0 2017-06 SP-76 SP-170369 3231 - F Clarification for congestion control for default APN 14.4.0 2017-06 SP-76 SP-170369 3233 - F Removal of UE-AMBR from Inter-UE QoS for NB-IoT UEs using Control Plane CIoT EPS Optimisation 14.4.0 2017-06 SP-76 SP-170363 3236 2 A Handling of CE Mode B support for "Voice Centric" UEs 14.4.0 2017-06 SP-76 SP-170361 3248 2 A PDN-Connection-Restricted flag 14.4.0 2017-06 SP-76 SP-170372 3252 2 F Voice/Video support for "Data Centric" UEs operating in CE Mode A/B 14.4.0 2017-06 SP-76 SP-170369 3254 1 F Clarification on mobility support between NB-IoT and GPRS 14.4.0 2017-06 SP-76 SP-170375 3225 5 B TS 23.401 Subscription Control for EPC_DC_NR 15.0.0 2017-06 SP-76 SP-170513 3234 3 B PDN GW selection for 5GC UE 15.0.0 2017-06 SP-76 SP-170375 3257 1 B UE capability handling for EPC_DC_NR 15.0.0 2017-09 SP-77 SP-170728 3255 1 B Updated scope for Dual Connectivity with other RATs 15.1.0 2017-09 SP-77 SP-170728 3258 2 B Per EPS bearer, RAN selection of DC (or non-DC) usage 15.1.0 2017-09 SP-77 SP-170719 3260 2 A Corrections to PDN GW handling of UE Data Off Status 15.1.0 2017-09 SP-77 SP-170723 3262 1 A Alignment with eNodeB and MME CP Relocation Indication procedures 15.1.0 2017-09 SP-77 SP-170728 3267 5 B Secondary RAT related data usage reporting 15.1.0 2017-09 SP-77 SP-170716 3271 2 A Correction on the condition for stopping Control Plane back-off timer at the UE 15.1.0 2017-09 SP-77 SP-170728 3272 6 B Indication NR is available to use 15.1.0 2017-09 SP-77 SP-170728 3273 1 B NAS UE indicator for Dual Connectivity with NR 15.1.0 2017-09 SP-77 SP-170715 3277 1 A DCNs without HSS subscription information 15.1.0 2017-09 SP-77 SP-170728 3279 1 F Subscription Control for EPC_DC_NR 15.1.0 2017-09 SP-77 SP-170728 3285 3 B Control of Secondary RAT data volume reporting 15.1.0 2017-09 SP-77 SP-170732 3286 2 F Handling of multiple CP parameter sets 15.1.0 2017-09 SP-77 SP-170729 3289 2 C 23.401 PCEF Support for Data Off phase 2 15.1.0 2017-09 SP-77 SP-170716 3291 1 A Correction for Data Centric UEs 15.1.0 2017-09 SP-77 SP-170728 3299 1 B RAN specification reference for EN-DC 15.1.0 2017-09 SP-77 SP-170728 3300 1 F Clarification to DC procedure when NR is used as secondary RAT 15.1.0 2017-09 SP-77 SP-170713 3301 2 A No support of dedicated bearers for NB-IoT 15.1.0 2017-09 SP-77 SP-170713 3304 1 A Correction of header compression for CP optimisation 15.1.0 2017-09 SP-77 SP-170728 3306 - B Subscription Control for EPC_DC_NR: handover from Gn/Gp SGSN 15.1.0 2017-09 SP-77 SP-170713 3314 - A Correction of APN rate control enforcement and exceptional MO data 15.1.0 2017-09 SP-77 SP-170713 3316 - A Correction of forwarding of MO Exception Data Counter 15.1.0 2017-09 SP-77 SP-170726 3319 - A CP only UE support of bearer modification and HC negotiation 15.1.0 2017-12 SP-78 SP-170912 3295 1 A Correction of capability indication for downlink NAS data PDU acknowledgment 15.2.0 2017-12 SP-78 SP-170909 3321 1 A Correction of APN Rate Control - interoperability with legacy UEs 15.2.0 2017-12 SP-78 SP-170914 3324 1 A Update of TAU procedure with SGW change and data forwarding 15.2.0 2017-12 SP-78 SP-170920 3325 3 C Secondary RAT related data usage reporting improvements 15.2.0 2017-12 SP-78 SP-170920 3326 3 F Secondary RAT related data usage reporting format from RAN 15.2.0 2017-12 SP-78 SP-170920 3327 1 F Secondary RAT related data usage reporting corrections 15.2.0 2017-12 SP-78 SP-170924 3328 4 B Introduction of Service Gap Control 15.2.0 2017-12 SP-78 SP-170921 3331 - C Clarification on UE behaviour when receiving single list of Exempt Services - TS 23.401 15.2.0 2017-12 SP-78 SP-170920 3332 1 F Clarification of the case that HSS provide the Access Restriction 15.2.0 2017-12 SP-78 SP-170926 3335 4 B Enhanced VoLTE performance CR for TS 23.401 15.2.0 2017-12 SP-78 SP-170909 3340 1 A Non-IP protection from broadcast messages 15.2.0 2017-12 SP-78 SP-170920 3342 - F Correction on the update of RAN in subscription change 15.2.0 2017-12 SP-78 SP-170924 3344 1 C Reliable Data Service with PtP SGi Tunnelling 15.2.0 2017-12 SP-78 SP-170912 3346 4 A S11-U interface separation from S1-U interface 15.2.0 2017-12 SP-78 SP-170912 3348 3 A Data support for "voice centric" UE supporting CE mode B 15.2.0 2017-12 SP-78 SP-170924 3353 2 F Modify Bearer Request during TAU 15.2.0 2017-12 SP-78 SP-170909 3356 2 A UE CIoT capability in RRC Connection Establishment request for TAU 15.2.0 2017-12 SP-78 SP-170927 3357 1 B Data volume reporting when secondary RAT is using unlicensed spectrum 15.2.0 2017-12 SP-78 SP-170927 3358 1 B RAT Restriction when secondary RAT is using unlicensed spectrum 15.2.0 2017-12 SP-78 SP-170924 3359 3 C Use of ARP priority level in addition to QCI for packet handling 15.2.0 2017-12 SP-78 SP-170920 3360 1 F Correcting the condition for selection of PGW and SGW for NR as secondary RAT 15.2.0 2017-12 SP-78 SP-170920 3362 2 F Corrections to secondary RAT usage data reporting 15.2.0 2017-12 SP-78 SP-170912 3364 2 A Non-overlapping MMECs for CP CIOT EPS Optimisation 15.2.0 2017-12 SP-78 SP-170919 3365 2 B Dual registration supported indicator from MME 15.2.0 2017-12 SP-78 SP-170915 3367 2 A Clarification on PS Data Off status reporting - TS 23.401 15.2.0 2017-12 SP-78 SP-170920 3368 1 F Cleanup related to Secondary RAT related data usage reporting 15.2.0 2017-12 SP-78 SP-170941 3372 3 F Correction to Enhanced Coverage restriction 15.2.0 2017-12 SP-78 SP-170918 3375 1 A CIoT corrections related to PDN Connections 15.2.0 2017-12 SP-78 SP-170924 3376 - D Editorial corrections for CIoT 15.2.0 2018-03 SP-79 SP-180113 3378 1 F Alignment CR for storing CE mode B UE capability in MME 15.3.0 2018-03 SP-79 SP-180113 3381 2 F Clarification on PRA reporting in ECM-IDLE state 15.3.0 2018-03 SP-79 SP-180085 3391 1 A Addition of EC restriction parameter in S1 AP PAGING message 15.3.0 2018-03 SP-79 SP-180113 3392 2 C MME handling of unsupported APN 15.3.0 2018-03 SP-79 SP-180112 3396 3 B Feature definition for supporting 15 EPS bearers 15.3.0 2018-03 SP-79 SP-180090 3398 1 F Interworking aspects of EPS with 5GS are captured in 23.501 and 23.502 15.3.0 2018-03 SP-79 SP-180111 3403 1 F Alignment with stage-3 reporting and access restriction for unlicensed spectrum 15.3.0 2018-03 SP-79 SP-180108 3405 1 F Missing identification of step in clause 5.3.8.4 15.3.0 2018-03 SP-79 SP-180089 3407 1 A Correction to eNodeB CP Relocation Indication procedure 15.3.0 2018-06 SP-80 SP-180498 3350 4 B Additional parameters for NB-IoT UE Uu operation optimisation 15.4.0 2018-06 SP-80 SP-180496 3404 6 B Identification of LTE-M (eMTC) traffic 15.4.0 2018-06 SP-80 SP-180496 3408 5 F Correction of APN Rate Control for PDN connection release and re-establishment 15.4.0 2018-06 SP-80 SP-180496 3410 3 F Alignment with CT1/RAN on handling of S1AP CONNECTION ESTABLISHMENT INDICATION 15.4.0 2018-06 SP-80 SP-180497 3411 4 B Subscription for Aerial UE in 3GPP system 15.4.0 2018-06 SP-80 SP-180495 3412 2 F Clarification of using more than eight EPS bearers with EPS 15.4.0 2018-06 SP-80 SP-180496 3413 1 F Alignment with CT WG1 for handling of Connection Resume Requests at Service Gap 15.4.0 2018-06 SP-80 SP-180472 3416 1 A 3GPP PS Data Off Clarification 15.4.0 2018-06 SP-80 SP-180472 3418 1 A Correction of non-3GPP to E-UTRAN handovers 15.4.0 2018-06 SP-80 SP-180495 3419 2 B UE Capability for supporting 15 EPS bearers 15.4.0 2018-06 SP-80 SP-180495 3420 2 B Network support for increased number of bearers 15.4.0 2018-06 SP-80 SP-180471 3423 5 F Radio efficient handling of large UE radio capabilities at inter-RAT and SRVCC handover 15.4.0 2018-06 SP-80 SP-180492 3426 3 F Handling of very large UE radio capabilities for the anticipated EN-DC UEs 15.4.0 2018-06 SP-80 SP-180471 3429 - A Handling of large UE radio capabilities at inter-RAT and SRVCC handover 15.4.0 2018-06 SP-80 SP-180495 3430 - C Support for 15 bearers in PGWs across PLMN 15.4.0 2018-06 SP-80 SP-180496 3436 1 B Introducing Early Data Transmission for Control Plane CIoT EPS optimization 15.4.0 2018-06 SP-80 SP-180496 3438 3 F Applicability of Service Gap Control in idle and connected mode 15.4.0 2018-06 SP-80 SP-180496 3440 4 F MME request for UE Radio Capabilities 15.4.0 2018-06 SP-80 SP-180492 3441 2 F Secondary RAT Usage Reporting with multiple PDN connection 15.4.0 2018-09 SP-81 SP-180729 3443 1 F Negotiation of long periodic TAU timer value 15.5.0 2018-09 SP-81 SP-180729 3444 6 F UE Radio Capability Update using TAU procedure 15.5.0 2018-09 SP-81 SP-180729 3445 5 C Further proposal for subscribed PTW length 15.5.0 2018-09 SP-81 SP-180729 3446 1 F Corrections for ARP priority level 15.5.0 2018-09 SP-81 SP-180729 3448 8 F Clarification on EDT procedure 15.5.0 2018-09 SP-81 SP-180725 3450 1 F Correction on Secondary RAT data usage report 15.5.0 2018-09 SP-81 SP-180729 3451 - F UE radio capabilities - alignment with rSRVCC from GERAN 15.5.0 2018-09 SP-81 SP-180728 3452 5 B Traffic Profile for NB-IoT UE Uu operation optimisation 15.5.0 2018-09 SP-81 SP-180711 3458 1 A Corrections to re-negotiation of header compression configuration 15.5.0 2018-09 SP-81 SP-180729 3459 2 F Correction of APN Rate Control Status in bearer deactivation 15.5.0 2018-09 SP-81 SP-180730 3454 2 B Enhancement of network event reporting 16.0.0 2018-12 SP-82 SP-181095 3461 3 A AS RAI system impacts 16.1.0 2018-12 SP-82 SP-181080 3467 1 A Reporting PS Data Off status change when SM back off timer is running 16.1.0 2018-12 SP-82 SP-181080 3471 1 A PS Data Off supporting non-IP data 16.1.0 2018-12 SP-82 SP-181082 3473 1 A Correction of reference in Control Plane NAS congestion control 16.1.0 2018-12 SP-82 SP-181096 3475 3 F Corrections to Dual Connectivity with NR feature 16.1.0 2018-12 SP-82 SP-181095 3477 3 A RAT specific subscribed PTW length 16.1.0 2018-12 SP-82 SP-181095 3480 2 A Corrections to Service Gap Control 16.1.0 2018-12 SP-82 SP-181095 3486 1 A Correction of Serving PLMN Rate Control 16.1.0 2018-12 SP-82 SP-181095 3489 - A Correction of Secondary RAT periodic reporting description 16.1.0 2018-12 SP-82 SP-181095 3490 1 A End marker and ERAB Modification for Dual Connectivity 16.1.0 2019-03 SP-83 SP-190163 3491 4 B Support for Restricted Local Operator Services in EPC 16.2.0 2019-03 SP-83 SP-190153 3494 - A End marker and ERAB Modification interaction for Dual Connectivity 16.2.0 2019-03 SP-83 SP-190175 3498 2 B Dedicated Bearers for Ethernet in EPC 16.2.0 2019-03 SP-83 SP-190175 3499 2 B Subscriber RRM Group as additional parameter to SPID/RFSP 16.2.0 2019-06 SP-84 SP-190406 3501 1 C Dedicated Bearers for Ethernet in EPC 16.3.0 2019-06 SP-84 SP-190424 3502 4 C Avoiding UE indicating RLOS access in RRC Signalling 16.3.0 2019-06 SP-84 SP-190425 3503 3 B Adds UE Radio Capability ID in signalling procedures 16.3.0 2019-06 SP-84 SP-190404 3507 2 A TNL Address discovery for EN-DC 16.3.0 2019-06 SP-84 SP-190406 3508 2 B Dedicated Bearers for Ethernet in EPC - IOPS / LIPA / SIPTO@LN aspects 16.3.0 2019-06 SP-84 SP-190403 3509 3 A Updating LCS procedures for location reporting for multiple cells 16.3.0 2019-06 SP-84 SP-190425 3510 1 B EPS architecture supporting RACS 16.3.0 2019-06 SP-84 SP-190406 3512 1 C Ethernet packet filters in TFT 16.3.0 2019-06 SP-84 SP-190403 3514 - A Secondary Cell ID Reporting - completion and signalling efficiency 16.3.0 2019-06 SP-84 SP-190399 3516 - A Interworking aspects of EPS with 5GS are captured in 23.501 and 23.502 16.3.0 2019-09 SP-85 SP-190622 3518 - F Correction on the number of PDN types stored per APN in the subscription data 16.4.0 2019-09 SP-85 SP-190617 3519 3 F Correction on support of RACS 16.4.0 2019-09 SP-85 SP-190622 3524 - F Aligning Create Session Request parameters with 29.274 16.4.0 2019-09 SP-85 SP-190622 3525 1 F Use of EDT in User Plane CIOT EPS Optimisation 16.4.0 2019-09 SP-85 SP-190617 3526 2 C Handling of NB-IOT radio capabilities and RACS in EPS 16.4.0 2019-09 SP-85 SP-190603 3530 1 A Location Reporting: LI and signalling load 16.4.0 2019-09 SP-85 SP-190603 3532 1 A Location Reporting: periodic PSCell ID reporting 16.4.0 2019-09 SP-85 SP-190616 3536 1 F UE attached for access to RLOS and emergency call 16.4.0 2019-09 SP-85 SP-190617 3537 1 F Some corrections and clarifications on RACS procedure 16.4.0 2019-09 SP-85 SP-190622 3539 1 C MME Functionality to Control Emergency Call Bearer Support Indicator 16.4.0 2019-12 SP-86 SP-191088 3520 2 F Corrections of PLMN assigned Capability signalling 16.5.0 2019-12 SP-86 SP-191331 3527 3 F UE Radio Capability ID allocation in EPS 16.5.0 2019-12 SP-86 SP-191089 3538 5 F Assistance indication for WUS grouping 16.5.0 2019-12 SP-86 SP-191088 3541 3 F Clarification on UE capability update 16.5.0 2019-12 SP-86 SP-191059 3542 8 B Introduction of MT-EDT 16.5.0 2019-12 SP-86 SP-191087 3543 1 F Fixing incorrectly implemented 23.401 CR3491 16.5.0 2019-12 SP-86 SP-191087 3544 1 F Avoiding RRC release due to inactivity for PARLOS 16.5.0 2019-12 SP-86 SP-191089 3547 2 B Unlicensed Spectrum for NR-U 16.5.0 2019-12 SP-86 SP-191088 3549 6 F removing requirement that TAC+SV is used to identify UE model in manufacturer assigned ID 16.5.0 2019-12 SP-86 SP-191089 3552 1 F SMS transmission in Communication pattern parameters 16.5.0 2019-12 SP-86 SP-191087 3553 1 F PSM,ISR and extended idle mode DRX handling in RLOS 16.5.0 2019-12 SP-86 SP-191086 3555 1 B Support for IAB in EPS 16.5.0 2019-12 SP-86 SP-191088 3561 2 F Inclusion of Version Identifier in PLMN assigned ID 16.5.0 2019-12 SP-86 SP-191086 3570 - B Support for IAB indication and authorization in EPS 16.5.0 2019-12 SP-86 SP-191065 3571 1 F System support for NB-IoT Paging across Multiple Carriers and/or WUS with WB-EUTRAN <-> NB-IoT mobility 16.5.0 2020-03 SP-87E SP-200061 3558 2 B Introduction of support for UE-specific DRX for NB-IoT 16.6.0 2020-03 SP-87E SP-200061 3577 1 F WUS assistance clarifications 16.6.0 2020-03 SP-87E SP-200081 3578 2 F Addition of PSCell ID in E-RAB modification procedure 16.6.0 2020-03 SP-87E SP-200074 3579 - F RAC ID during inter-PLMN handover case 16.6.0 2020-03 SP-87E SP-200081 3581 4 F Clarification of MME handling for secondary RAT data reporting 16.6.0 2020-03 SP-87E SP-200081 3586 - F Subscription parameter for NR-U access restriction 16.6.0 2020-03 SP-87E SP-200074 3587 1 F Deletion of UE Radio Capability ID using GUTI reallocation 16.6.0 2020-03 SP-87E SP-200074 3588 - D Editorial updates in RACS clauses 16.6.0 2020-03 SP-87E SP-200081 3589 1 F MT-EDT related update 16.6.0 2020-03 SP-87E SP-200074 3593 1 F Correction on UCMF event notification for PLMN assigned ID(s) 16.6.0 2020-07 SP-88E SP-200421 3583 4 F System support for Wake Up Signal 16.7.0 2020-07 SP-88E SP-200436 3595 1 F Missing the Radio Capability Filtering linkage to the UE Radio Capability ID 16.7.0 2020-07 SP-88E SP-200436 3596 1 F UE radio capability for EPS 16.7.0 2020-07 SP-88E SP-200436 3597 2 F Support of multiple radio capability formats 16.7.0 2020-07 SP-88E SP-200436 3598 1 F Clarification on Version ID 16.7.0 2020-07 SP-88E SP-200552 3599 1 F Correction to handling of Service Gap timer for regulatory prioritized services 16.7.0 2020-07 SP-88E SP-200607 3602 2 B Alignment CR for DAPS HO 16.7.0 2020-07 SP-88E SP-200552 3604 1 F UE specific DRX for NB-IoT RAN support clarification 16.7.0 2020-09 SP-89E SP-200685 3605 1 F Mobility procedure across ePLMNs 16.8.0 2020-09 SP-89E SP-200672 3607 - A Providing Recommended Cells for Paging information by WUS-capable eNodeBs for all UEs 16.8.0 2020-09 SP-89E SP-200684 3610 - F Corrections to Initial Attach for PARLOS 16.8.0 2020-09 SP-89E SP-200686 3611 1 F Further corrections to SGC handling 16.8.0 2020-12 SP-90E SP-200959 3614 1 F Missing description of inter-RAT handover from NR to EN-DC 16.9.0 2021-03 SP-91E SP-210082 3619 1 F Correcting APN-OI replacement specification mismatch between stage 2 and stage 3 16.10.0 2021-03 SP-91E SP-210080 3623 1 F UTRAN and manufacturer assigned UE Radio Capability ID 16.10.0 2021-03 SP-91E SP-210085 3620 1 B Multimedia Priority Service (MPS) Phase 2 support for Data Transport Service 17.0.0 2021-03 SP-91E SP-210087 3621 1 C Passing PSCell ID to SGW 17.0.0 2021-03 SP-91E SP-210086 3624 1 B Introduction of Paging Cause feature 17.0.0 2021-03 SP-91E SP-210086 3625 1 B Introduction of Leaving procedure - SR based 17.0.0 2021-03 SP-91E SP-210087 3629 - D 23.401 Inclusive language review 17.0.0 2021-06 SP-92E SP-210362 3618 2 B paging reception for MUSIM device 17.1.0 2021-06 SP-92E SP-210323 3622 5 B Function Description for Multi-USIM devices 17.1.0 2021-06 SP-92E SP-210362 3627 2 B Introduction of Reject Paging Indication response to paging using SR 17.1.0 2021-06 SP-92E SP-210362 3630 4 B Introduction of MUSIM capability exchange 17.1.0 2021-06 SP-92E SP-210362 3634 4 B Introduction of Paging Cause feature 17.1.0 2021-06 SP-92E SP-210362 3637 - D Terminology alignment: Removal of Leaving from the Leaving/Release Request indication 17.1.0 2021-06 SP-92E SP-210362 3639 1 F Clarification related to EPS Leaving procedure 17.1.0 2021-06 SP-92E SP-210361 3642 1 B Additional authorization functionality in support of MPS for Data Transport Service 17.1.0 2021-09 SP-93E SP-210910 3644 1 A Handling of UE Radio Capability for Paging 17.2.0 2021-09 SP-93E SP-210935 3645 1 B EPS User Plane Integrity Protection with minimal core network changes 17.2.0 2021-09 SP-93E SP-211130 3646 2 F UE indication of support for Paging Timing Collision Control 17.2.0 2021-09 SP-93E SP-210932 3647 - F Update Paging Cause Feature in EPS 17.2.0 2021-09 SP-93E SP-210936 3648 1 F ARP PL applied by MME per local configruation 17.2.0 2021-09 SP-93E SP-210932 3649 1 F MUSIM Terminology Alignment 17.2.0 2021-09 SP-93E SP-210932 3650 - F MUSIM and CIOT 17.2.0 2021-09 SP-93E SP-210932 3652 1 F Clarification on removing condition of paging restriction and IMSI Offset 17.2.0 2021-09 SP-93E SP-210932 3654 - F Terminologies Correction 17.2.0 2021-09 SP-93E SP-210910 3657 1 A Correction to deletion procedure for PLMN-assigned UE Radio Capability IDs 17.2.0 2021-12 SP-94E SP-211548 3658 3 F MUSIM capabilities in Emergency Attach 17.3.0 2021-12 SP-94E SP-211302 3659 - F Removal of MUSIM mode 17.3.0 2021-12 SP-94E SP-211284 3663 3 B Introduction of Satellite support for Cellular IoT 17.3.0 2021-12 SP-94E SP-211302 3664 1 F On Paging restrictions handling 17.3.0 2021-12 SP-94E SP-211302 3665 1 F On Connection Release and Paging Restriction during a mobility TAU in a TA outside the current Registration Area 17.3.0 2021-12 SP-94E SP-211284 3667 2 C Support for IoT NTN with discontinuous coverage 17.3.0 2021-12 SP-94E SP-211284 3668 1 C IoT NTN: Ensure use of MME in the country where UE is located 17.3.0 2021-12 SP-94E SP-211304 3670 1 F Correction to MME handling EPS bearer QoS 17.3.0 2021-12 SP-94E SP-211302 3677 1 F Adding Alternative IMSI to the MM Context in the MME 17.3.0 2021-12 SP-94E SP-211302 3678 1 F Clarification on paging restrictions 17.3.0 2022-03 SP-95E SP-220064 3679 1 F MUSIM capabilities in TAU for Emergency attached UE 17.4.0 2022-03 SP-95E SP-220068 3680 1 F Remove the EN on UPIP for EPS 17.4.0 2022-03 SP-95E SP-220066 3681 1 F Correction for Restriction of use of Enhanced Coverage 17.4.0 2022-03 SP-95E SP-220061 3683 1 F IoT NTN: Alignment of TA Handling for moving cells with NR NTN 17.4.0 2022-03 SP-95E SP-220061 3684 - F Removing Registration Area 17.4.0 2022-03 SP-95E SP-220066 3687 1 F Clarification on handling of UE radio capability for paging when MME changes 17.4.0 2022-03 SP-95E SP-220063 3689 - F Paging priority correction for MPS 17.4.0 2022-03 SP-95E SP-220061 3690 - F Limited service emergency call over satellite 17.4.0 2022-03 SP-95E SP-220064 3692 1 F Correction on MUSIM Paging Cause feature 17.4.0 2022-06 SP-96 SP-220405 3682 2 F IoT NTN: Removal of Indication of country of UE location 17.5.0 2022-06 SP-96 SP-220405 3694 1 F Removal of unnecessary LTE-M satellite Indication in S1-AP 17.5.0 2022-06 SP-96 SP-220411 3695 1 F Handling of ARP for IMS voice service in home routed roaming 17.5.0 2022-06 SP-96 SP-220407 3696 1 F Acceptance and Rejection of Paging Restriction Information 17.5.0 2022-06 SP-96 SP-220405 3698 - F IoT NTN: Alignment of TA handling for moving cells with NR NTN 17.5.0 2022-06 SP-96 SP-220411 3701 F Detection of RACS support at target during S1 and X2 handover 17.5.0 2022-09 SP-97E SP-220789 3703 1 F ULI provision with PScell information 17.6.0 2022-09 SP-97E SP-220768 3706 1 A Removal of misaligned text with stage-3 17.6.0 2022-09 SP-97E SP-220784 3708 1 F MME sends forbidden TAI(s) to UE 17.6.0 2022-09 SP-97E SP-220784 3710 - F RAN Initiated UE Context Release for UE using IoT satellite access 17.6.0 2022-12 SP-98E SP-221077 3707 5 F Handling of radio capabilities across TN and NTN IoT 17.7.0 2022-12 SP-98E SP-221077 3717 1 F Clarification on UE deactivation of AS function 17.7.0 2022-12 SP-98E SP-221077 3719 4 C Idle mode handling for UEs with different E-UTRA RAC in TN and NTN 17.7.0 2022-12 SP-98E SP-221081 3718 2 B Verification of UE location update in 23.401 18.0.0 2023-03 SP-99 SP-230070 3713 2 B MPS when access to EPC is WLAN 18.1.0 2023-03 SP-99 SP-230069 3720 1 B Identifier availability for Lawful Interception during Inter-MME/ MME-5GS handover 18.1.0 2023-06 SP-100 SP-230451 3721 10 B Support of mobility management and power saving with discontinuous coverage 18.2.0 2023-06 SP-100 SP-230480 3723 1 A Removal of EN on handling of extended NAS timers 18.2.0 2023-06 SP-100 SP-230480 3727 1 A Correction to UE AS deactivation 18.2.0 2023-06 SP-100 SP-230479 3730 2 A Clarification on IAB Authorization 18.2.0 2023-06 SP-100 SP-230481 3731 - F MPS when access to EPC is WLAN correction 18.2.0 2023-09 SP-101 SP-230838 3739 - A Replacing obsoleted RFCs related to DHCPv6 with RFC 8415 18.3.0 2023-09 SP-101 SP-230841 3741 - F Satellite Coverage Availability Information - IoT NTN 18.3.0 2023-09 SP-101 SP-230841 3743 4 F Clarification on satellite discontinuous coverage 18.3.0 2023-09 SP-101 SP-230841 3744 3 F Discontinuous coverage update to remove EN and alignments 18.3.0 2023-09 SP-101 SP-230841 3745 2 F Handling on congestion control and UE behaviour 18.3.0 2023-12 SP-102 SP-231248 3746 4 F Correcting the reference for UE radio capability update procedure 18.4.0 2023-12 SP-102 SP-231239 3753 2 A PDN GW selection for IMS emergency calls with GateWay Core Network sharing 18.4.0 2023-12 SP-102 SP-231249 3755 2 F Update on support of discontinuous coverage for satellite access 18.4.0 2023-12 SP-102 SP-231249 3756 1 F Clarification on Extended Idle Mode DRX and discontinous coverage 18.4.0 2023-12 SP-102 SP-231249 3757 1 F Discontinuous coverage overload control priority users term alignment 18.4.0 2023-12 SP-102 SP-231249 3758 1 F Satellite RAT Types in TS 23.401 18.4.0 2024-03 SP-103 SP-240115 3762 5 F Mechanisms for UE location reporting for NB-IoT satellite access 18.5.0 2024-06 SP-104 SP-240602 3740 11 F Clarification on the handling of Operator defined QCIs at inter-PLMN Handover 18.6.0 2024-06 SP-104 SP-240589 3771 2 F Corrections on Estimated Maximum Wait Time for Discontinuous Coverage for Satellite Access 18.6.0 2024-06 SP-104 SP-240589 3772 3 F Unavailability configuration during attach 18.6.0 2024-06 SP-104 SP-240586 3774 2 A Support of TAU in Cellular IoT 18.6.0 2024-06 SP-104 SP-240589 3776 2 F Clarification on Discontinuous coverage for satellite access 18.6.0 2024-06 SP-104 SP-240602 3779 2 F Update of UE location verification for NTN for regulatory requirements 18.6.0 2024-09 SP-105 SP-241256 3814 2 F Applying MME determined unavailability values 18.7.0 2024-09 SP-105 SP-241272 3796 1 B Subscription control for time reference information delivery in EPS 19.0.0 2024-09 SP-105 SP-241266 3797 2 B MPS support for Messaging 19.0.0 2024-12 SP-106 SP-241485 3800 13 B Introduction to Split MME architecture 19.1.0 2024-12 SP-106 SP-241485 3801 24 B Introduction of Store and Forward feature in EPC 19.1.0 2024-12 SP-106 SP-241485 3815 10 B Support of Store and Forward Satellite Operation 19.1.0 2024-12 SP-106 SP-241484 3821 1 F Update table on CIoT functionalities for UE specific DRX for NB-IOT 19.1.0 2024-12 SP-106 SP-241485 3824 11 B Procedures for Store and Forward Satellite Operations 19.1.0 2024-12 SP-106 SP-241469 3828 1 A Clarification on congestion control 19.1.0 2024-12 SP-106 SP-241484 3830 1 F Handling stale PDN sessions at P-GW 19.1.0 2024-12 SP-106 SP-241490 3833 2 F MPS priority paging for MT SMS 19.1.0 2024-12 SP-106 SP-241476 3835 1 A Handling of Coarse UE location 19.1.0 2025-03 SP-107 SP-250040 3849 1 F Terminology correction and clarification for Store and Forward Satellite Operation 19.2.0 2025-03 SP-107 SP-250040 3854 1 B Support of Attach with PDN connection for split MME architecture 19.2.0 2025-03 SP-107 SP-250040 3861 6 B Procedure updates for S&F 19.2.0 2025-03 SP-107 SP-250040 3867 16 B Support of S&F Monitoring List in S&F Mode 19.2.0 2025-03 SP-107 SP-250040 3879 1 F HSS table clarification 19.2.0 2025-03 SP-107 SP-250040 3880 3 F UE Detach for S&F Mode Access 19.2.0 2025-03 SP-107 SP-250040 3881 6 C Transition between S&F Mode and Normal Mode 19.2.0 2025-03 SP-107 SP-250040 3885 - B Support for satellite access with regenerative payload 19.2.0 2025-03 SP-107 SP-250040 3887 1 F Clarification on S&F wait timer 19.2.0 2025-03 SP-107 SP-250040 3889 2 F Clarification on support of Store and Forward Satellite Operation 19.2.0 2025-03 SP-107 SP-250040 3894 2 F Clarification on the condition for UE indicating S&F capability 19.2.0 2025-03 SP-107 SP-250040 3897 2 F Clarification related to terminology and on MME providing list in detach procedure 19.2.0
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
1 Scope
|
The present document specifies the application enabling layer platform architecture, capabilities and services to efficiently support storage and delivery for the application content/data for vertical applications as part of SEAL services specified in 3GPP TS 23.434 [4].
This work takes into consideration the existing stage 1 and stage 2 work within 3GPP related to data delivery and 3GPP system user plane aspects specified in 3GPP TS 22.261 [2] and 3GPP TS 23.501 [5].
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
2 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.261: "Service requirements for the 5G system; Stage 1".
[3] 3GPP TS 23.222: "Functional architecture and information flows to support Common API Framework for 3GPP Northbound APIs; Stage 2".
[4] 3GPP TS 23.434: "Service Enabler Architecture Layer for Verticals (SEAL); Functional architecture and information flows".
[5] 3GPP TS 23.501: "System architecture for the 5G System (5GS); Stage 2".
[6] 3GPP TS 23.502: "Procedures for the 5G System (5GS); Stage 2".
[7] 3GPP TS 23.503: "Policy and charging control framework for the 5G System (5GS); Stage 2".
[8] 3GPP TS 23.548: "5G System Enhancements for Edge Computing ".
[9] 3GPP TS 23.554: "Application architecture for MSGin5G Service; Stage 2".
[10] 3GPP TS 23.558: "Architecture for enabling Edge Applications".
[11] 3GPP TS 28.104: "Management and orchestration; Management Data Analytics (MDA)".
[12] 3GPP TS 28.541: "Management and orchestration; 5G Network Resource Model (NRM); Stage 2 and stage 3".
[13] 3GPP TS 23.436: "Functional architecture and information flows for Application Data Analytics Enablement Service".
[14] 3GPP TS 26.501: "5G Media Streaming (5GMS); General description and architecture".
[15] 3GPP TS 26.506: "5G Real-time Media Communication Architecture (Stage 2)".
[16] 3GPP TS 23.303: "Proximity-based Services (ProSe); Stage 2".
[17] 3GPP TS 23.304: "Proximity based Services (ProSe) in the 5G System (5GS)".
[18] ITU‑T Recommendation P.1203.3: "Parametric bitstream-based quality assessment of progressive download and adaptive audiovisual streaming services over reliable transport - Quality integration module".
[19] 3GPP TS 23.288: "Architecture enhancements for 5G System (5GS) to support network data analytics services".
[20] 3GPP TS 26.118: "Virtual Reality (VR) profiles for streaming applications".
[21] 3GPP TS 23.435: "Procedures for Network Slice Capability Exposure for Application Layer Enablement Service".
[22] 3GPP TS 23.482: "Functional architecture and information flows for AIML Enablement Service".
[23] 3GPP TS 23.542: "Application layer support for Personal IoT Network".
[24] 3GPP TS 23.682: "Architecture enhancements to facilitate communications with packet data networks and applications".
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
3 Definitions of terms, symbols and abbreviations
| |
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
3.1 Terms
|
For the purposes of the present document, the terms given in 3GPP TR 21.905 [1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [1].
Application connection: Association between the VAL client and the VAL service to provide the VAL service.
Application traffic: a set of signaling messages or a set of media packet constituting a application service flow. E.g., one or more picture(s) may be an application traffic, the audio stream and the video stream are two different application traffic.
Crossflow QoS measurement is an E2E measurement between SEALDD client and SEALDD server that considers multi-modal traffic routes in combination of uplink direction and downlink direction for same application.
Multi-modal SEALDD flows: a set of individual SEALDD flows that are associated with each other for a particular application that requires synchronization among the individual SEALDD flows.
SEALDD–S connection: Association between the SEALDD server and the VAL server to achieve data delivery of the application traffic. One application connection may have one SEALDD-S connection, e.g., for all the application traffic flows, or have more SEALDD-S connections, e.g., one for application signaling flow, and the other or application media traffic flow(s). A SEALDD-S connection shall be uniquely identified between the VAL server and the SEALDD server.
SEALDD-S flows: a set of packets have the same attributes, e.g., the same 5-tuple, media type. The application traffic flow may be mapped to one ore more SEALDD-S flow(s). A SEALDD-S flow should be uniquely identified with the SEALDD-S connection.
SEALDD-UU connection: Association between the SEALDD server and the SEALDD client to achieve the data delivery of the application traffic from the VAL server or the VAL client. One SEALDD-S connection may be associated with one SEALDD-UU connection or multiple SEALDD-UU connections. A SEALDD-UU connection shall be uniquely identified between the SEALDD client and the SEALDD server.
SEALDD-UU flows: a set of packets have the same attributes, e.g., the same 5-tuple, media type, QoS requirements. One SEALDD-S flow(s) may be mapped to one or multiple SEALDD-UU flows. A SEALDD-UU flow should be uniquely identified with the SEALDD-UU connection.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
3.2 Symbols
|
None
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
3.3 Abbreviations
|
For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [1].
AF Application Function
CAPIF Common API Framework for northbound APIs
DD Data Delivery
EAS Edge Application Server
EDN Edge Data Network
NRM Network Resource Management
SBA Service Based Architecture
SCEF Service Capability Exposure Function
SEAL Service Enabler Architecture Layer for verticals
SEALDD SEAL Data Delivery
URSP UE Route Selection Policy
VAL Vertical Application Layer
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
4 Overview
| |
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
4.1 General
|
This clause gives a functionality overview for SEALDD service.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
4.2 Application signalling and data transmission
|
This SEALDD functionality provides a mechanism for application signalling data transmission and application media data transmission between VAL client(s) and VAL server(s). The SEALDD enabled regular connection management procedures (e.g. connection establishment, connection deletion) are specified in clause 9.2. For supporting URLLC feature, the SEALDD layer establishes E2E redundant transmission with packet duplication and elimination, as specified in clause 9.3.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
4.3 Transmission quality measurement and transmission optimization
|
The transmission quality measurement procedure specified in clause 9.7, supports the E2E transmission quality measurement between SEALDD client and SEALDD server, and exposes the transmission reports to VAL servers and other consumers (e.g. SEALDD server, NSCE server, etc). Based on the SEALDD enabled E2E transmission measurement result, the SEALDD layer provides transmission optimization scheme (e.g. triggering redundant transmission, switching another SEALDD server) to improve transmission quality by interacting with 5GC. The transmission optimization procedures are specified in clause 9.9.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
4.4 Data transmission rate control
|
The SEALDD layer provides the differentiated data delivery service with different bandwidth/transmission rate experience for VAL users, considering the network conditions (e.g. QoS monitoring, ECN marking for L4S report), which is described in clause 9.8.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
4.5 Service continuity support
|
This functionality is provided to support service continuity due to UE mobility or load balance. The SEALDD layer maintains the transport layer connection by interacting SEALDD context, and requesting 5GC to perform seamless data transmission (e.g. IP replacement procedure, simultaneous connectivity). The service continuity support procedures are specified in clause 9.6.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
4.6 Data storage
|
The SEALDD server supports the data storage and storage management for VAL server, SEALDD client and other SEALDD servers, etc, the corresponding procedure is specified in clause 9.5.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
4.7 Background Data Transfer
|
This SEALDD functionality enables to keep data transmission costs lower by favouring time windows for data transfer to/from specific UEs in a geographical area, e.g. during non-busy hours, that are less costly and able to handle larger bitrates. The background data transfer procedures are specified in clause 9.11.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
5 Business relationships
| |
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
5.1 General
|
The clause specifies the business relationships between the various stakeholders like VAL user, VAL service provider, SEALDD provider and PLMN operator.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
5.2 Business relationship option-A
|
Figure 5.2-1 shows the business relationship option-A that exist and that are needed to support a single VAL user.
Figure 5.2-1: Business relationship option-A for VAL services
The VAL user belongs to a VAL service provider based on a VAL service agreement between the VAL user and the VAL service provider. The VAL service provider may have VAL service agreements with several VAL users. The VAL user may have VAL service agreements with several VAL service providers.
The VAL service provider and the PLMN operator may be part of the same organization, in which case the business relationship between the two is internal to a single organization.
The VAL service provider may have SEAL provider arrangements with multiple SEAL providers and the SEAL provider may have PLMN operator service arrangements with multiple PLMN operators. The SEAL provider and the VAL service provider or the PLMN operator may be part of the same organization, in which case the business relationship between the two is internal to a single organization.
The PLMN operator may have PLMN operator service arrangements with multiple VAL service providers and the VAL service provider may have PLMN operator service arrangements with multiple PLMN operators. As part of the PLMN operator service arrangement between the VAL service provider and the PLMN operator, PLMN subscription arrangements may be provided which allows the VAL UEs to register with PLMN operator network.
NOTE: The roaming cases are not discussed in this release.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
5.3 Business relationship option-B
|
Figure 5.3-1 shows the business relationship option-B that exist and that are needed to support a single VAL user.
Figure 5.3-1: Business relationship option-B for VAL services
The VAL user belongs to a VAL service provider based on a VAL service agreement between the VAL user and the VAL service provider. The VAL service provider may have VAL service agreements with several VAL users. The VAL user may have VAL service agreements with several VAL service providers.
The VAL user may have PLMN operator service arrangements with the PLMN operator. The PLMN operator service arrangement includes the UE subscription arrangement which allows the VAL UEs to register with operator network.
The VAL service provider may have SEALDD provider arrangements with multiple SEALDD providers and the SEALDD provider may have SEALDD provider arrangements with multiple VAL service providers.
The PLMN operator may have PLMN operator service arrangements with multiple SEALDD service providers and the SEALDD service provider may have PLMN operator service arrangements with multiple PLMN operators. The SEALDD service provider and the PLMN operator may be part of the same organization, in which case the business relationship between the two is internal to a single organization.
NOTE: The roaming cases are not discussed in this release.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
6 Architectural requirements
| |
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
6.1 General
| |
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
6.1.1 Description
|
The general architecture requirements specified in clause 4.1 of 3GPP TS 23.434 [4] are applicable for SEALDD service. This clause specifies the general requirements for SEALDD service.
|
3e37dc0922bf713bab29d41e3b7c43c3
|
23.433
|
6.1.2 Requirements
|
[AR-6.1.2-a] The SEALDD service shall provide a discovery mechanism to support data delivery between VAL client(s) and VAL servers(s) considering different deployments of VAL server(s) (e.g. cloud or edge).
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.