hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.1.2.6 UE - P‑GW user plane with Control Plane CIoT EPS Optimisations
|
Legend:
- GTP-u (GPRS Tunnelling Protocol User plane): This protocol tunnels user data between MME and the S‑GW as well as between the S‑GW and the P‑GW in the backbone network. GTP shall encapsulate all end user packets. End user Ethernet packets are only used with a combined PDN GW+SMF (as specified in TS 23.501 [... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.2 Identities
| |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.2.1 EPS bearer identity
| An EPS bearer identity uniquely identifies an EPS bearer for one UE accessing via E-UTRAN. The EPS Bearer Identity is allocated by the MME. When using an EPS Radio Bearer, there is a one to one mapping between EPS RB and EPS Bearer, and the mapping between EPS RB Identity and EPS Bearer Identity is made by E-UTRAN. The... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.2.2 Globally Unique Temporary UE Identity
| The MME shall allocate a Globally Unique Temporary Identity (GUTI) to the UE. The GUTI is defined in TS 23.003 [9].
|
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.2.3 Tracking Area Identity (TAI)
| This is the identity used to identify tracking areas. The Tracking Area Identity is constructed from the MCC (Mobile Country Code), MNC (Mobile Network Code) and TAC (Tracking Area Code).
A TAI should be associated with a single time zone. All TAIs served by one eNodeB shall be in the same time zone.
NOTE: Changes in... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.2.5 MME S1-AP UE Identity (MME S1-AP UE ID)
| This is the temporary identity used to identify a UE on the S1-MME reference point within the MME. It is unique within the MME.
|
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.2.6 Closed Subscriber Group ID
| A CSG ID is a unique identifier within the scope of PLMN defined in TS 23.003 [9] which identifies a Closed Subscriber Group (CSG) in the PLMN associated with a CSG cell or group of CSG cells.
|
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.2.7 UE Radio Capability ID
| The UE Radio Capability ID is a short pointer with format defined in TS 23.003 [9] that is used to uniquely identify a set of UE Radio Capabilities (excluding UTRAN and NB-IoT capabilities). The UE Radio Capability ID is assigned either by the serving PLMN or by the UE manufacturer, as follows:
- UE manufacturer-assig... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.3 Authentication, security and location management
| |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.3.1 IP address allocation
| |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.3.1.1 General
| The procedures of clause 5.3.1 apply to UEs activating a PDN connection of PDN Type IPv4, IPv6 or IPv4v6. Part of it also applies for PDN Type Non-IP when SGi PtP Tunnelling based on UDP/IP, see clause 4.3.17.8, is used. The procedures of clause 5.3.1 do not apply to UEs activating a PDN connection of PDN Type Ethernet... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.3.1.2 IP address allocation, renewal and release mechanisms for GTP based S5/S8
| |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.3.1.2.1 IPv4 address allocation via default bearer activation and release via PDN connection release
| An IPv4 address may be provided to the UE as part of the default bearer activation and the IPv4 address is released when PDN connection associated with the IPv4 address is released.
When the PLMN allocates an IPv4 address, it is the PDN GW responsibility to allocate and release the IPv4 address. The PDN GW may use an ... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.3.1.2.2 Allocation, renewal and release of the IPv6 default prefix via IPv6 stateless address autoconfiguration
| When the PLMN allocates an IPv6 prefix, it is the PDN GW responsibility to allocate and release the IPv6 prefix. The PDN GW may use an internal IPv6 prefix pool in this case. The PDN GW allocates a globally unique /64 IPv6 prefix via Router Advertisement to a given UE.
When an IPv6 prefix is allocated from an external... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.3.1.2.3 IPv6 parameter configuration via stateless DHCPv6
| The UE may use stateless DHCPv6 for additional parameter configuration. The PDN GW acts as the DHCP server. When PLMN based parameter configuration is used, the PDN GW provides the requested parameters from locally provisioned database. When external PDN based parameter configuration is used, the PDN GW obtains the req... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.3.1.2.4 IPv4 address allocation, renewal and release and IPv4 parameter configuration via DHCPv4
| When the PLMN allocates an IPv4 address, it is the PDN GW responsibility to allocate, renew and release the IPv4 address.
When external PDN allocation is used, the PDN GW functions as a DHCPv4 server towards the UE. The PDN GW may act as a DHCP Client when interacting with a DHCPv4 server in the external PDN in order ... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.3.1.2.5 Void
| |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.3.1.2.6 IPv6 Prefix Delegation via DHCPv6
| Optionally a single network prefix shorter than the default /64 prefix may be assigned to a PDN connection. In this case, the /64 default prefix used for IPv6 stateless autoconfiguration will be allocated from this network prefix; the remaining address space from the network prefix can be delegated to the PDN connectio... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.3.2 Attach procedure
| |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.3.2.1 E-UTRAN Initial Attach
| A UE/user needs to register with the network to receive services that require registration. This registration is described as Network Attachment. The always-on connectivity for UE/users of the EPS may be enabled by establishing a default EPS bearer during Network Attachment. The PCC rules applied to the default EPS bea... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.3.2.2 UTRAN/GERAN Initial Attach
| When a UE attaches to UTRAN/GERAN, it executes the normal attach procedure as defined in TS 23.060 [7]. When the UE needs an IP address, it initiates PDP context activation procedure as defined in TS 23.060 [7].
This procedure along with PDP context activation is also used to establish the first PDN connection over UT... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.3.3 Tracking Area Update procedures
| |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.3.3.0 Triggers for tracking area update
| A stand-alone tracking area update (with or without S‑GW change, described in clauses 5.3.3.1 and 5.3.3.2 respectively) occurs when a GPRS-attached or E‑UTRAN-attached UE experiences any of the following conditions:
- UE detects it has entered a new TA that is not in the list of TAIs that the UE registered with the ne... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.3.3.1 Tracking Area Update procedure with Serving GW change
|
Figure 5.3.3.1-1: Tracking Area Update procedure with Serving GW change
NOTE 1: For a PMIP-based S5/S8, procedure steps (A) and (B) are defined in TS 23.402 [2]. Steps 9 and 10 concern GTP based S5/S8.
NOTE 2: In the case of Tracking Area Update without MME change the signalling in steps 4, 5, 7 and steps 12-17 are... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.3.3.2 E-UTRAN Tracking Area Update without S‑GW Change
|
Figure 5.3.3.2-1: E-UTRAN Tracking Area Update without S‑GW change
NOTE 1: For a PMIP-based S5/S8, procedure steps (A) are defined in TS 23.402 [2]. Steps 12 and 14 concern GTP based S5/S8.
NOTE 2: In the case of Tracking Area Update without MME change the signalling in steps 4, 5, 7 and steps 9-19 are skipped. A c... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.3.3.3 Routing Area Update with MME interaction and without S‑GW change
| The Routing Area Update without S‑GW change procedure takes place when a UE that is registered with an MME selects a UTRAN or GERAN cell and the S‑GW is not changed by the procedure. 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 ECM... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.3.3.4 Void
| |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.3.3.5 Void
| |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.3.3.6 Routing Area Update with MME interaction and with S‑GW change
| The Routing Area Update with S‑GW change procedure takes place when a UE that is registered with an MME selects a UTRAN or GERAN cell and the S‑GW is changed by the procedure. 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 ECM-IDLE s... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.3.4 Service Request procedures
| |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.3.4.1 UE triggered Service Request
|
Figure 5.3.4.1-1: UE triggered Service Request procedure
The Service Request procedure in this clause is triggered by the UE in:
a) ECM-IDLE state to establish user plane radio bearers for the UE;
b) ECM-IDLE state to establish user plane radio bearers even if the UE applies Control Plane CIoT EPS Optimisation, wh... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.3.4.2 Handling of abnormal conditions in UE triggered Service Request
| Under certain conditions, the current UE triggered Service Request procedure can cause unnecessary Downlink Packet Notification messages which increase the load of the MME.
This can occur when uplink data sent in step 6 causes a response on the downlink which arrives at the Serving GW before the Modify Bearer Request ... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.3.4.3 Network Triggered Service Request
|
Figure 5.3.4.3-1: Network triggered Service Request procedure
If the MME needs to signal with the UE that is in ECM-IDLE state, e.g. to perform the MME/HSS-initiated detach procedure for the ECM-IDLE mode UE or the S‑GW receives control signalling (e.g. Create Bearer Request or Update Bearer Request), the MME starts... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.3.5 S1 release procedure
| This procedure is used to release the logical S1-AP signalling connection (over S1-MME) and all S1 bearers (in S1-U) for a UE. This Procedure releases the S11-U bearer in Control Plane CIoT EPS Optimisation (except in the case of buffering in MME), instead of the S1-U bearer. The procedure will move the UE from ECM-CON... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.3.6 Void
|
5.3.6A PDN GW Pause of Charging procedure
The PDN GW Pause of Charging procedure is optionally supported by the Serving GW and PDN GW and has the purpose to limit a mismatch between PDN GW and Serving GW charging volume and packet counts. Generally, it aims for the PDN GW charging and usage monitoring data to more a... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.3.7 GUTI Reallocation procedure
| The MME may initiate the GUTI Reallocation procedure to reallocate the GUTI and/or TAI list at any time when a signalling association is established between UE and MME. The GUTI Reallocation procedure allocates a new GUTI and/or a new TAI list and/or PLMN-assigned UE Radio Capability ID to the UE. The GUTI and/or the T... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.3.8 Detach procedure
| |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.3.8.1 General
| The Detach procedure allows:
- the UE to inform the network that it does not want to access the EPS any longer, and
- the network to inform the UE that it does not have access to the EPS any longer.
The UE is detached either explicitly or implicitly:
- Explicit detach: The network or the UE explicitly requests deta... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.3.8.2 UE-initiated Detach procedure
| The Detach procedure when initiated by the UE is described in clauses 5.3.8.2.1 and 5.3.8.2.2.
|
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.3.8.2.1 UE-initiated Detach procedure for E-UTRAN
| Figure 5.3.8.2-1 shows the case when UE camps on E-UTRAN and Detach Request is sent to MME.
Figure 5.3.8.2-1: UE-Initiated Detach Procedure - UE camping on E-UTRAN
NOTE 1: For a PMIP-based S5/S8, procedure steps (A) are defined in TS 23.402 [2]. Steps 6, 7 and 8 concern GTP based S5/S8
1. The UE sends NAS message ... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.3.8.2.2 UE-initiated Detach procedure for GERAN/UTRAN with ISR activated
| Figure 5.3.8.2-2 shows the case when UE with ISR Activated camps on GERAN/UTRAN and Detach Request is sent to SGSN. Refer to clause 6.6.1 of TS 23.060 [7] for the UE-initiated Detach procedure when ISR is not activated.
Figure 5.3.8.2-2: UE-Initiated Detach Procedure - UE camping on GERAN/UTRAN, ISR activated
1. Th... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.3.8.3 MME-initiated Detach procedure
| The MME-Initiated Detach procedure when initiated by the MME is illustrated in Figure 5.3.8.3-1.
This procedure may be also used as part of the SIPTO function when the MME determines that GW relocation is desirable for all PDN connection(s) serving SIPTO-allowed APNs. The MME initiates the "explicit detach with reatta... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.3.8.4 HSS-initiated Detach procedure
| The HSS-Initiated Detach procedure is initiated by the HSS. The HSS uses this procedure for operator-determined purposes to request the removal of a subscriber's MM and EPS bearer at the MME and also at the SGSN if both an MME and an SGSN are registered in the HSS.
For UEs with emergency EPS bearers, the MME/SGSN shal... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.3.9 HSS User Profile management function procedure
| |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.3.9.1 General
| The HSS user profile management function allows the HSS to update the HSS user profile stored in the MME. Whenever the HSS user profile is changed for a user in the HSS, and the changes affect the HSS user profile stored in the MME, the MME shall be informed about these changes by the means of the following procedure:
... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.3.9.2 Insert Subscriber Data procedure
| The Insert Subscriber Data procedure is illustrated in Figure 5.3.9.2-1.
Figure 5.3.9.2-1: Insert Subscriber Data procedure
1. The HSS sends an Insert Subscriber Data (IMSI, Subscription Data) message to the MME.
2. The MME updates the stored Subscription Data and acknowledges the Insert Subscriber Data message by... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.3.9.3 Purge function
| The Purge function allows an MME to inform the HSS that it has deleted the subscription data and MM context of a detached UE. The MME may, as an implementation option, delete the subscription data and MM context of an UE immediately after the implicit or explicit detach of the UE. Alternatively the MME may keep for som... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.3.10 Security Function
| |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.3.10.1 General
| The security functions include:
- Guards against unauthorised EPS service usage (authentication of the UE by the network and service request validation).
- Provision of user identity confidentiality (temporary identification and ciphering).
- Provision of user data and signalling confidentiality (ciphering).
- Prov... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.3.10.2 Authentication and Key Agreement
| EPS AKA is the authentication and key agreement procedure that shall be used over E-UTRAN, between the UE and MME. EPS AKA is specified in TS 33.401 [41].
|
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.3.10.3 User Identity Confidentiality
| An M-TMSI identifies a user between the UE and the MME. The relationship between M-TMSI and IMSI is known only in the UE and in the MME.
|
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.3.10.4 User Data and Signalling Confidentiality
| |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.3.10.4.0 General
| There are two different levels of the security associations between the UE and the network.
i) RRC and UP security association is between the UE and E‑UTRAN. The RRC security associations protect the RRC signalling between the UE and E‑UTRAN (integrity protection and ciphering). The UP security association is between ... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.3.10.4.1 AS security mode command procedure
| The MME triggers the RRC level AS security mode command procedure by sending the needed security parameters to the eNodeB. This enables ciphering of the UP traffic and ciphering and integrity protection of the RRC signalling as described in TS 33.401 [41].
NOTE: The integrity protection of the UP traffic is enabled us... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.3.10.4.2 NAS Security Mode Command procedure
| The MME uses the NAS Security Mode Command (SMC) procedure to establish a NAS security association between the UE and MME, in order to protect the further NAS signalling messages. This procedure is also used to make changes in the security association, e.g. to change the security algorithm.
Figure 5.3.10.4.2-1: NAS ... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.3.10.5 ME identity check procedure
| The Mobile Equipment Identity Check Procedure permits the operator(s) of the MME and/or the HSS and/or the PDN GW to check the Mobile Equipment's identity (e.g. to check that it has not been stolen, or, to verify that it does not have faults).
The ME Identity can be checked by the MME passing it to an Equipment Identi... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.3.11 UE Reachability procedures
| |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.3.11.1 General
| There are two procedures necessary for any service related entity that would need to be notified by the reachability of the UE at EPC NAS level:
- UE Reachability Notification Request procedure; and
- UE Activity Notification procedure.
|
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.3.11.2 UE Reachability Notification Request procedure
| The UE Reachability Notification Request procedure is illustrated in Figure 5.3.11.2-1.
Figure 5.3.11.2-1: UE Reachability Notification Request Procedure
1) If a service-related entity requests the HSS to provide an indication regarding UE reachability on EPS, the HSS stores the service-related entity and sets the ... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.3.11.3 UE Activity Notification procedure
| The UE Activity Notification procedure is illustrated in Figure 5.3.11.3-1.
Figure 5.3.11.3-1: UE Activity Procedure
1) The MME receives an indication regarding UE reachability, e.g. an Attach Request message from the UE or MME receive an indication from S‑GW that UE has handed over to non-3GPP coverage.
2) If the... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.3.12 Update CSG Location Procedure
| The Update CSG Location procedure takes place when the SGSN/MME needs to retrieve the CSG subscription information of the UE from the CSS.
Figure 5.3.12-1: Update CSG Location Procedure
1. The SGSN/MME sends Update CSG Location Request (MME Identity, IMSI, MSISDN) to the CSS. The MSIDSN is included if available.
2... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.3.13 CSS subscription data management function procedure
| |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.3.13.1 General
| The CSS subscription data management function allows the CSS to update the CSS subscription data stored in the MME.
The CSS subscription data is stored and managed in the MME independently from the Subscription Data received from the HSS.
Whenever the CSS subscription data is changed for a user in the CSS, and the ch... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.3.13.2 Insert CSG Subscriber Data procedure
| The Insert CSG Subscriber Data procedure is illustrated in Figure 5.3.13.2-1.
Figure 5.3.13.2-1: Insert CSG Subscriber Data procedure
1. The CSS sends an Insert CSG Subscriber Data (IMSI, CSG Subscription Data) message to the MME.
2. The MME updates the stored CSG Subscription Data and acknowledges the Insert CSG ... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.3.14 UE Radio Capability Match Request
| If the MME, e.g. based on SRVCC capability in NAS, UE Usage Type or local policy, requires more information on the UE radio capabilities support to be able to set the IMS voice over PS Session Supported Indication (see clause 4.3.5.8), then the MME may send a UE Radio Capability Match Request message to the eNodeB. Thi... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.4 Session Management, QoS and interaction with PCC functionality
| |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.4.1 Dedicated bearer activation
| The dedicated bearer activation procedure for a GTP based S5/S8 is depicted in figure 5.4.1-1. This procedure shall not be used when the UE is accessing over NB-IoT (i.e. RAT Type = NB-IoT).
Figure 5.4.1-1: Dedicated Bearer Activation Procedure
NOTE 1: Steps 3-10 are common for architecture variants with GTP based ... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.4.2 Bearer modification with bearer QoS update
| |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.4.2.1 PDN GW initiated bearer modification with bearer QoS update
| The PDN GW initiated bearer modification procedure (including EPS Bearer QoS update) for a GTP based S5/S8 is depicted in figure 5.4.2.1-1. This procedure is used in cases when one or several of the EPS Bearer QoS parameters QCI, GBR, MBR or ARP are modified (including the QCI or the ARP of the default EPS bearer e.g. ... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.4.2.2 HSS Initiated Subscribed QoS Modification and MME initiated QoS modification
| The HSS Initiated Subscribed QoS Modification for a GTP-based S5/S8 is depicted in figure 5.4.2.2-1 where steps 1, 1a, are executed. The MME initiated QoS modification can happen, e.g. at Inter-PLMN mobility if there is a QoS Change upon Inter-PLMN mobility.
Figure 5.4.2.2-1: HSS Initiated Subscribed QoS Modificatio... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.4.3 PDN GW initiated bearer modification without bearer QoS update
| The bearer modification procedure without bearer QoS update is used to update the TFT for an active default or dedicated bearer, to modify the APN-AMBR, to retrieve User Location from the MME, to inform PCO to UE or to instruct the MME (e.g. to activate/deactivate the location reporting).
The procedure for a GTP based... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.4.4 Bearer deactivation
| |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.4.4.1 PDN GW initiated bearer deactivation
| The bearer deactivation procedure for a GTP based S5/S8 is depicted in figure 5.4.4.1-1. This procedure can be used to deactivate a dedicated bearer or deactivate all bearers belonging to a PDN address. If the default bearer belonging to a PDN connection is deactivated, the PDN GW deactivates all bearers belonging to t... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 7a The UE NAS layer builds a Deactivate EPS Bearer Context Accept message including EPS Bearer Identity. The UE then sends a Direct Transfer (Deactivate EPS Bearer Context Accept) message to the eNodeB.
| 7b. The eNodeB sends an Uplink NAS Transport (Deactivate EPS Bearer Context Accept) message to the MME.
7c. If the UE receives the Detach Request message from the MME in the step 4a, the UE sends a Detach Accept message to the MME any time after step 4a. The eNodeB forwards this NAS message to the MME along with the T... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 8b The SGSN deletes PDP Context related to the deactivated EPS bearer and acknowledges the bearer deactivation to the Serving GW by sending a Delete Bearer Response (EPS Bearer Identity, User Location Information (CGI/SAI)) message. If extended idle mode DRX is enabled, then the SGSN acknowledges the bearer deactivatio... | 9. If ISR is activated, after receiving the two Delete Bearer Response messages from the MME and the SGSN, or if ISR is not activated, after receiving the Delete Bearer Response messages from the MME, the Serving GW deletes the bearer context related to the deactivated EPS bearer acknowledges the bearer deactivation to... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.4.4.2 MME Initiated Dedicated Bearer Deactivation
| MME initiated Dedicated Bearer Deactivation is depicted in Figure 5.4.4.2-1 below. This procedure deactivates dedicated bearers. Default bearers are not affected. To initiate the release of the full PDN connection including the default bearer, the MME uses the UE or MME requested PDN disconnection procedure defined in ... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.4.5 UE requested bearer resource modification
| The UE requested bearer resource modification procedure for an E-UTRAN is depicted in figure 5.4.5-1. The procedure allows the UE to request for a modification of bearer resources (e.g. allocation or release of resources) for one traffic flow aggregate with a specific QoS demand. Alternatively, the procedure allows the... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.4.6 Void
| |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.4.7 E-UTRAN initiated E-RAB modification procedure
| When SCG bearer option is applied to support dual connectivity operation, this procedure is used to transfer bearer contexts to and from Secondary eNodeB (see TS 36.300 [5]) or Secondary gNodeB (see TS 37.340 [85]). During this procedure, both the MME and Serving GW are never relocated. The presence of IP connectivity ... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.4.8 E-UTRAN initiated UE Context Modification procedure
| When split bearer option is applied to support dual connectivity operation, this procedure is used is by the eNodeB to request the modifications on the established UE Context. In the current version of the specification, this procedure is only used for membership verification, as described in TS 36.300 [5].
Figure 5... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.5 Handover
| |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.5.1 Intra-E-UTRAN handover
| |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.5.1.1 X2-based handover
| |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.5.1.1.1 General
| These procedures are used to hand over a UE from a source eNodeB to a target eNodeB using the X2 reference point. In these procedures the MME is unchanged. Two procedures are defined depending on whether the Serving GW is unchanged or is relocated. In addition to the X2 reference point between the source and target eNo... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.5.1.1.2 X2-based handover without Serving GW relocation
| This procedure is used to hand over a UE from a source eNodeB to a target eNodeB using X2 when the MME is unchanged and decides that the Serving GW is also unchanged. The presence of IP connectivity between the Serving GW and the source eNodeB, as well as between the Serving GW and the target eNodeB is assumed.
Figu... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.5.1.1.3 X2-based handover with Serving GW relocation
| This procedure is used to hand over a UE from a source eNodeB to a target eNodeB using X2 when the MME is unchanged and the MME decides that the Serving GW is to be relocated. The presence of IP connectivity between the source Serving GW and the source eNodeB, between the source Serving GW and the target eNodeB, and be... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.5.1.2 S1-based handover
| |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.5.1.2.1 General
| The S1-based handover procedure is used when the X2-based handover cannot be used. The source eNodeB initiates a handover by sending Handover Required message over the S1-MME reference point. This procedure may relocate the MME and/or the Serving GW. The source MME selects the target MME. The MME should not be relocate... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.5.1.2.2 S1-based handover, normal
| This procedure describes the S1-based handover in the normal case, clause 5.5.1.2.3 describes it when the procedure is rejected by the target eNodeB or the target MME and clause 5.5.1.2.4 describes when the procedure is canceled by the source eNodeB.
Figure 5.5.1.2.2-1: S1-based handover
NOTE 1: For a PMIP-based S5... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.5.1.2.3 S1-based handover, Reject
| The Target eNodeB rejects the use of the Handover procedure if none of the requested 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. Further, the Target MME rejects the handover request and clears all resour... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.5.1.2.4 S1-based handover, Cancel
| Instead of completing the handover procedure, the source eNodeB 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 MME shall cancel the handover resources as defined in clause 5.5.2.5.1 for case the source RAN is eNodeB.
|
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.5.2 Inter RAT handover
| |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.5.2.0 General
| During Inter RAT handover indirect forwarding may apply for the downlink data forwarding performed as part of the handover. From its configuration data the MME knows whether indirect forwarding applies and it allocates a downlink data forwarding path on a Serving GWs for indirect forwarding. From its configuration data... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.5.2.1 E-UTRAN to UTRAN Iu mode Inter RAT handover
| |
b043aa03d2112b1c3a444522800f3b3a | 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 ar... |
b043aa03d2112b1c3a444522800f3b3a | 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 tunne... |
b043aa03d2112b1c3a444522800f3b3a | 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 ... |
b043aa03d2112b1c3a444522800f3b3a | 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 UT... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.5.2.2 UTRAN Iu mode to E-UTRAN Inter RAT handover
| |
b043aa03d2112b1c3a444522800f3b3a | 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 ong... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.