hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.34 Support for Time Reference Information Distribution
| Support for time reference information distribution in RRC is specified in TS 36.331 [37].
This feature is optional. When it is supported, it enables the operator to control, based on subscription, whether to deliver time reference information to a UE. The MME receives the indication from the HSS that the UE is subscr... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.4 Network elements
| |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.4.1 E-UTRAN
| E-UTRAN is described in more detail in TS 36.300 [5].
In addition to the E-UTRAN functions described in TS 36.300 [5], E-UTRAN functions include:
- Header compression and user plane ciphering and integrity protection (for user plane data sent across S1-U);
- MME selection when no routing to an MME can be determined ... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.4.2 MME
| MME functions include:
- NAS signalling;
- NAS signalling security;
- Inter CN node signalling for mobility between 3GPP access networks (terminating S3);
- UE Reachability in ECM-IDLE state (including control, execution of paging retransmission and optionally Paging Policy Differentiation);
- Tracking Area list m... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.4.3 Gateway
| |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.4.3.1 General
| Two logical Gateways exist:
- Serving GW (S‑GW);
- PDN GW (P‑GW).
NOTE: The PDN GW and the Serving GW may be implemented in one physical node or separated physical nodes.
|
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.4.3.2 Serving GW
| The Serving GW is the gateway which terminates the user plane interface towards E-UTRAN (except when user data is transported using the Control Plane CIoT EPS Optimisation).
For each UE associated with the EPS, at a given point of time, there is a single Serving GW.
The functions of the Serving GW, for both the GTP-b... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.4.3.3 PDN GW
| The PDN GW is the gateway which terminates the SGi interface towards the PDN.
If a UE is accessing multiple PDNs, there may be more than one PDN GW for that UE, however a mix of S5/S8 connectivity and Gn/Gp connectivity is not supported for that UE simultaneously.
PDN GW functions include for both the GTP-based and t... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.4.4 SGSN
| In addition to the functions described in TS 23.060 [7], SGSN functions include:
- Inter EPC node signalling for mobility between 2G/3G and E-UTRAN 3GPP access networks;
- PDN and Serving GW selection: the selection of S‑GW/P‑GW by the SGSN is as specified for the MME;
- Handling UE Time Zone as specified for the MM... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.4.5 GERAN
| GERAN is described in more detail in TS 43.051 [15].
|
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.4.6 UTRAN
| UTRAN is described in more detail in TS 25.401 [16].
|
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.4.7 PCRF
| |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.4.7.1 General
| PCRF is the policy and charging control element. PCRF functions are described in more detail in TS 23.203 [6].
In non-roaming scenario, there is only a single PCRF in the HPLMN associated with one UE's IP-CAN session. The PCRF terminates the Rx interface and the Gx interface.
In a roaming scenario with local breakout... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.4.7.2 Home PCRF (H-PCRF)
| The functions of the H-PCRF include:
- terminates the Rx reference point for home network services;
- terminates the S9 reference point for roaming with local breakout;
- associates the sessions established over the multiple reference points (S9, Rx), for the same UE's IP-CAN session (PCC session binding).
The func... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.4.7.3 Visited PCRF (V-PCRF)
| The functions of the V-PCRF include:
- terminates the Gx and S9 reference points for roaming with local breakout;
- terminates Rx for roaming with local breakout and visited operator's Application Function.
The functionality of V-PCRF is described in TS 23.203 [6].
|
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.4.8 PDN GW's associated AAA Server
| The PDN Gateway may interact with a AAA server over the SGi interface. This AAA Server may maintain information associated with UE access to the EPC and provide authorization and other network services. This AAA Server could be a RADIUS or Diameter Server in an external PDN network, as defined in TS 29.061 [38]. This A... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.4.9 HeNB subsystem
| A HeNB subsystem consists of a HeNB, optionally a HeNB GW and optionally a Local GW.
The Local IP Access and SIPTO at the Local Network with L-GW function collocated with the HeNB functions are achieved using a Local GW (L-GW) collocated with the HeNB.
Figure 4.4.9-1 illustrates the architecture for LIPA and/or SIPTO... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.4.10 DeNB
| DeNB function is described in more detail in TS 36.300 [5].
DeNB provides the necessary S/P‑GW functions for the operation of RNs connected to the DeNB.
In order to provide the Relay Function the DeNB shall support the following P-GW functions:
- IP address allocation for the UE functionality of the RN;
- Downlink ... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.4.11 CSG Subscriber Server
| CSG Subscriber Server (CSS) is an optional element that stores CSG subscription data for roaming subscribers. The CSS stores and provides VPLMN specific CSG subscription information to the MME. The CSS is accessible from the MME via the S7a interface. The CSS is always in the same PLMN as the current MME.
If the same ... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.4.12 RAN Congestion Awareness Function
| The RAN Congestion Awareness Function (RCAF) is an element that provides RAN User Plane Congestion Information (RUCI) to the PCRF to enable the PCRF to take the RAN user plane congestion status into account for policy decisions.
The RCAF collects information related to user plane congestion from the RAN's OAM system b... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.4.13 UCMF
| The UCMF is used for storage of dictionary entries corresponding to either PLMN-assigned or UE manufacturer-assigned UE Radio Capability IDs. An MME may subscribe with the UCMF to obtain from the UCMF new values of UE Radio Capability ID that the UCMF assigns for the purpose of caching them locally.
Provisioning of UE... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.5 Void
| |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.6 EPS Mobility Management and Connection Management states
| |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.6.1 General
| The EPS Mobility Management (EMM) states describe the Mobility Management states that result from the mobility management procedures e.g. Attach and Tracking Area Update procedures.
Two EMM states are described in this document:
- EMM-DEREGISTERED.
- EMM-REGISTERED.
NOTE 1: Other specifications may define more deta... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.6.2 Definition of main EPS Mobility Management states
| |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.6.2.1 EMM-DEREGISTERED
| In the EMM‑DEREGISTERED state, the EMM context in MME holds no valid location or routing information for the UE. The UE is not reachable by a MME, as the UE location is not known.
In the EMM-DEREGISTERED state, some UE context can still be stored in the UE and MME, e.g. to avoid running an AKA procedure during every A... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.6.2.2 EMM-REGISTERED
| The UE enters the EMM-REGISTERED state by a successful registration with an Attach procedure to either E-UTRAN or GERAN/UTRAN. The MME enters the EMM-REGISTERED state by a successful Tracking Area Update procedure for a UE selecting an E-UTRAN cell from GERAN/UTRAN or by an Attach procedure via E-UTRAN. In the EMM-REGI... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.6.3 Definition of EPS Connection Management states
| |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.6.3.1 ECM-IDLE
| A UE is in ECM-IDLE state when no NAS signalling connection between UE and network exists. In ECM-IDLE state, a UE performs cell selection/reselection according to TS 36.304 [34] and PLMN selection according to TS 23.122 [10].
Except for UEs that have had their RRC connection suspended, as described in clause 5.3.4A, ... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.6.3.2 ECM-CONNECTED
| The UE location is known in the MME with an accuracy of a serving eNodeB ID. The mobility of UE is handled by the handover procedure, except for when the NB-IoT is being used, in which case there are no handover procedures.
The UE performs the tracking area update procedure when the TAI in the EMM system information i... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.6.4 State transition and functions
|
Figure 4.6.4-1: EMM state model in UE
Figure 4.6.4-2: EMM state model in MME
Figure 4.6.4-3: ECM state model in UE
Figure 4.6.4-4: ECM state model in MME
|
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.7 Overall QoS concept
| |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.7.1 PDN connectivity service
| The Evolved Packet System provides connectivity between a UE and a PLMN external packet data network. This is referred to as PDN Connectivity Service.
The IP PDN Connectivity Service supports the transport of traffic flow aggregate(s), consisting of one or more Service Data Flows (SDFs).
NOTE: The concept of SDF is d... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.7.2 The EPS bearer
| |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.7.2.1 The EPS bearer in general
| For E-UTRAN access to the EPC the PDN connectivity service is provided by an EPS bearer for GTP-based S5/S8, and if IP is in use, by an EPS bearer concatenated with IP connectivity between Serving GW and PDN GW for PMIP-based S5/S8.
In this release of the specifications, dedicated bearers are only supported for the IP... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.7.2.2 The EPS bearer with GTP-based S5/S8
|
Figure 4.7.2.2-1: Two Unicast EPS bearers (GTP-based S5/S8)
An EPS bearer is realized by the following elements:
- In the UE, the UL TFT maps a traffic flow aggregate to an EPS bearer in the uplink direction;
- In the PDN GW, the DL TFT maps a traffic flow aggregate to an EPS bearer in the downlink direction;
- A... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.7.2.3 The EPS bearer with PMIP-based S5/S8
| See clause 4.10.3 in TS 23.402 [2].
|
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.7.3 Bearer level QoS parameters
| The EPS bearer QoS profile includes the parameters QCI, ARP, GBR and MBR, described in this clause. This clause also describes QoS parameters which are applied to an aggregated set of EPS Bearers: APN‑AMBR and UE‑AMBR.
Each EPS bearer (GBR and Non-GBR) is associated with the following bearer level QoS parameters:
- Q... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.7.4 Support for Application / Service Layer Rate Adaptation
| The E‑UTRAN/UTRAN and the UE support the RFC 3168 [55] Explicit Congestion Notification (ECN), as described in TS 36.300 [5], TS 25.401 [16] and TS 26.114 [56]. The IP level ECN scheme enables the E‑UTRAN/UTRAN to trigger a rate adaptation scheme at the application / service / transport layer. To make sufficient time a... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.7.5 Application of PCC in the Evolved Packet System
| The Evolved Packet System applies the PCC framework as defined in TS 23.203 [6] for QoS policy and charging control. PCC functionality is present in the AF, PCEF and PCRF.
An EPS needs to support both PCEF and PCRF functionality to enable dynamic policy and charging control by means of installation of PCC rules based ... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.7.6 Bearer Control Mode in EPC
| The Bearer Control Mode (BCM) for E-UTRAN access is always UE/NW. Hence, explicit signalling between the UE and the network to determine BCM for E-UTRAN access does not occur.
GERAN/UTRAN/E-UTRAN capable UEs negotiate the BCM of a PDN Connection applicable for GERAN/UTRAN access during E-UTRAN Initial Attach and durin... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.7.7 Support of rate control of user data using CIoT EPS Optimisation
| |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.7.7.1 General
| The rate of user data sent to and from a UE (e.g. a UE using CIoT EPS Optimisations) can be controlled in two different ways:
- Serving PLMN Rate Control
- APN Rate Control
Serving PLMN Rate Control is intended to allow the Serving PLMN to protect its MME and the Signalling Radio Bearers in the E-UTRAN from the load... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.7.7.2 Serving PLMN Rate Control
| The Serving PLMN Rate Control value is configured in the MME.
NOTE 1: Homogeneous support of Serving PLMN Rate Control in a network is assumed.
At PDN connection establishment, the MME may inform the UE and PDN GW/SCEF (as specified in TS 24.301 [46] and TS 29.274 [43]) of any per PDN connection local Serving PLMN Ra... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.7.7.3 APN Rate Control
| The APN Rate Control is configured in the PDN GW or in the SCEF. The PDN GW or SCEF can send an APN Uplink Rate Control command to the UE using the PCO information element.
The APN Uplink Rate Control applies to data PDUs sent on that APN by either Data Radio Bearers (S1-U) or Signalling Radio Bearers (NAS Data PDUs).... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.7.8 Inter-UE QoS for NB-IoT UEs using Control Plane CIoT EPS Optimisation
| To allow the E-UTRAN to prioritise resource allocation between different NB-IoT UEs when some of the UEs are using the Control Plane CIoT EPS Optimisation, the eNodeB may request, based on configuration, the MME to supply the eNodeB with the negotiated QoS profile for any UE that is using the Control Plane CIoT EPS Opt... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.8 Compatibility Issues
| |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.8.1 Network Configuration for Interaction with UTRAN/GERAN
| GPRS idle mode mobility within GERAN or UTRAN and also between GERAN and UTRAN specifies a set of sequence number handling functions, e.g. the exchange of sequence numbers during Routing Area Update procedures. EPS idle mode mobility procedures don't specify any such sequence number mappings for IRAT mobility scenarios... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.9 Paging Policy Differentiation
| Paging policy differentiation is an optional feature that allows the MME, based on operator configuration, to apply different paging strategies as defined in clause 5.3.4.3 for different traffic or service types provided within the same PDN connection.
When it supports Paging Policy Differentiation feature, the Servin... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.10 Introduction of CIoT EPS Optimisations
| CIoT EPS Optimisations provide improved support of small data transfer. One optimisation is based on User Plane transport of user data and is referred to as User Plane CIoT EPS Optimisation. Another optimisation, known as Control Plane CIoT EPS Optimisation, transports user data or SMS messages via MME by encapsulating... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.11 User Plane CIoT EPS Optimisation
| The User Plane CIoT EPS Optimisation functionality enables support for transfer of user plane data without the need for using the Service Request procedure to establish Access Stratum (AS) context in the serving eNodeB and UE.
If the following preconditions are met:
- UE and MME support User Plane CIOT EPS Optimisati... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.12 Supporting up to 15 EPS bearers per UE
| A UE attached to WB-E-UTRAN access, including for dual connectivity using E-UTRAN access as described in clause 4.3.2a, may support 8 or 15 EPS bearers. To enable support of establishing 15 EPS bearers, it requires the EPC connected to the E-UTRAN access to support 15 EPS bearers for such UEs.
If the UE supports 15 EP... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.13 Introduction of satellite support for Cellular IoT
| |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.13.1 General
| This clause describes the functionality for supporting Cellular IoT over satellite access. Support for WB-E-UTRAN, NB-IoT and LTE-M satellite access is specified in TS 36.300 [5]. The description for satellite access in this specification is applicable to both transparent satellite payload and regenerative satellite pa... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.13.2 Support of RAT types defined in EPC for satellite access
| In the case of satellite access with WB-E-UTRAN, NB-IoT or LTE-M, the RAT Types values "WB-E-UTRAN(LEO)", "WB-E-UTRAN(MEO)", " WB-E-UTRAN(GEO)", " WB-E-UTRAN(OTHERSAT)", "NB-IoT(LEO)", "NB-IoT(MEO)", "NB-IoT(GEO)", "NB-IoT(OTHERSAT)", "LTE-M(LEO)", "LTE-M(MEO)", "LTE-M(GEO)" and "LTE-M(OTHERSAT)" are used in EPC to dis... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.13.3 Network/Access selection for satellite access
| Network/Access selection principles specified in clause 4.3.2.2 also apply for satellite access for Cellular IoT.
In the case of satellite access for Cellular IoT, a UE with location capability (i.e. GNSS capability) should use its awareness of its location to select a PLMN that is allowed to operate the UE location a... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.13.4 Verification of UE location
| In order to ensure that the regulatory requirements are met, the network may be configured to enforce that the selected PLMN is allowed to operate in the current UE location by verifying the UE location during EMM and ESM procedures. In this case, when the MME receives the User Location Information (ULI) for a UE using... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.13.5 Use of extended NAS timers
| Whenever the UE is accessing the network using a satellite RAT, the MME and the UE shall set the NAS timers long enough according to this satellite RAT, as specified in TS 24.301 [46].
|
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.13.6 Support of Tracking Area Update
| A moving cell for NB-IoT, LTE-M or WB-E-UTRAN satellite access may indicate support for one or more Tracking Areas Codes (TACs) for each PLMN (see clause 4.13.7). A UE that is registered with a PLMN may access a cell and does not need to perform a Tracking Area Update procedure for mobility reasons as long as at least ... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.13.7 Tracking Area handling
| For Cellular IoT over satellite access with moving cells, in order to ensure that each TA is Earth-stationary, even if the radio cells are moving across the Earth's surface, the E-UTRAN may change the TAC values that are broadcast in a cell's system information as the cell moves, as described in TS 36.331 [37].
E-UTRA... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.13.8 Enhanced support of discontinuous network coverage for satellite access
| |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.13.8.1 General
| Basic support for discontinuous coverage is specified in clause 4.3.5.2 and clause 4.3.17.7. The present clause 4.13.8 provides additional optional enhancements to discontinuous coverage:
- Mobility management and power saving optimization, see clause 4.13.8.2; and
- Coverage availability information provisioning to ... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.13.8.2 Mobility Management and UE Power Saving Optimization
| For satellite access that provides discontinuous network coverage, and in case both the UE and the network support Enhanced Discontinuous Coverage, then the Mobility Management and UE Power Saving Optimization functionality may be used.
If both the UE and the network indicate support for "Enhanced Discontinuous Covera... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.13.8.3 Coverage availability information provisioning to the UE
| A UE may use satellite coverage availability information for satellite access to support discontinuous coverage operations. Satellite coverage availability information can be provided to a UE by an external server via a PDN Connection or SMS. The protocol and format of satellite coverage availability information via PD... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.13.8.4 Coverage availability information provisioning to the MME
| The MME may use satellite coverage availability information to support satellite access by UEs with discontinuous coverage operation. Satellite coverage availability information may be provisioned to the MME by O&M.
NOTE 1: In this release of the specification there is no support for provisioning of satellite coverage... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.13.8.5 Paging
| In the case of satellite access that provides discontinuous network coverage, the MME may utilize sub-area paging (e.g. first page in the last known ECGI or TA and retransmission in all registered TAs). The MME may utilize the location information as received at or before the S1 release due to the discontinuous coverag... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.13.8.6 Overload control
| The MME and UE may only use the procedure defined in this clause if both the UE and MME indicate "Enhanced Discontinuous Coverage Support", see clause 4.13.8.1.
In order to avoid a large number of UEs causing excessive signalling load on the network when leaving coverage or re-gaining coverage after being out of cover... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.13.9 Support of Store and Forward Satellite operation
| |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.13.9.1 General
| The Store and Forward Satellite operation applies in E-UTRAN with satellite access and is suitable for delay-tolerant communication services (e.g. CIoT/MTC, SMS, etc.). If the satellite does not support Store and Forward Satellite operation and there is no feeder link connection to the ground network, then the satellit... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.13.9.2 Transition between S&F mode and non S&F mode
| If a UE is attached to a PLMN using satellite operating in S&F mode, the UE follows the existing AS and NAS procedures to access a satellite that is not operating in S&F mode (either TN or NTN eNodeB) and vice versa.
In order to ensure smooth idle mode transition from S&F mode to non S&F mode, if the old (S&F capable)... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.13.10 UE Coarse Location information for NB-IoT satellite access
| As described in clause 4.13.4, in the case of NB-IoT, the MME may request the UE to report its Coarse Location Information for location verification purposes. In addition, as described in TS 36.300 [5] and TS 36.413 [36], the eNB may request, in a S1-AP Initial UE message, the MME to provide the Coarse Location Informa... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.13.11 S1 interface and connection management for regenerative satellite payload
| The S1 Removal procedure defined in TS 36.413 [36] can be used to remove the interface between an eNodeB and an MME in a controlled manner, e.g. when the eNodeB is leaving the service area of an MME when using regenerative satellite payload.
|
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.14 Support of Disaster Roaming with Minimization of Service Interruption in EPS
| |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.14.1 General
| Subject to operator policy and national/regional regulations, EPS provides Disaster Roaming service in EPS for the UEs from PLMN(s) with Disaster Condition in 5GS. The UE shall attempt Disaster Roaming only if:
- there is no available PLMN which is allowable except PLMN/E-UTRAN combinations available only for Disaster... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.14.2 UE configuration and provisioning for Disaster Roaming
| A UE supporting Disaster Roaming service in EPS is configured with the following information:
- Optionally, indication of whether disaster roaming in EPS is enabled in the UE;
- Optionally, indication of 'applicability of "lists of PLMN(s) to be used in disaster condition" provided by a VPLMN';
- Optionally, list of... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.14.3 Disaster Condition Notification and Determination
| The E-UTRAN cell in the PLMN that provides Disaster Roaming service in EPS, broadcasts an indication of accessibility for Disaster Roaming service in EPS and optionally, a 'list of one or more PLMN(s) with Disaster Condition for which Disaster Roaming service in EPS is offered by the available PLMN' in the impacted are... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.14.4 Attach Procedure or TAU procedure for Disaster Roaming service in EPS
| For a UE to receive Disaster Roaming service in EPS from a PLMN providing Disaster Roaming service in EPS, the UE sends a NAS Attach Request message with Attach Type value set to "Disaster Roaming Attach" or TAU request message with Update Type value set to "Disaster Roaming Update":
- When the MME in the PLMN providi... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.14.5 Handling when a Disaster Condition is no longer applicable
| When a UE detects a Disaster Condition is no longer applicable, the UE performs PLMN selection as described in TS 23.122 [10] and TS 24.301 [46] and may return to the PLMN previously with Disaster Condition.
A PLMN providing Disaster Roaming service in EPS:
- May trigger the Disaster Inbound Roaming UEs to return to ... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.14.6 Prevention of signalling overload related to Disaster Condition and Disaster Roaming service
| The load control, congestion and overload control mechanism specified in clause 5.19 and access control and barring specified in TS 36.331 [37] and TS 22.011 [67] can be used to mitigate the load caused by UE requesting the Disaster Roaming service in EPS in the PLMN providing Disaster Roaming service in EPS and return... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5 Functional description and information flows
| |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.1 Control and user planes
| |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.1.0 General
| NOTE:
- Refer to TS 23.402 [2] for the corresponding protocol stack for PMIP based S5/S8.
- Refer to TS 23.203 [6] for the corresponding protocol stack for Policy Control and Charging (PCC) function related reference points.
|
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.1.1 Control Plane
| |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.1.1.1 General
| The control plane consists of protocols for control and support of the user plane functions:
- controlling the E-UTRA network access connections, such as attaching to and detaching from E-UTRAN;
- controlling the attributes of an established network access connection, such as activation of an IP address;
- controlli... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.1.1.3 UE - MME
|
Legend:
- NAS: The NAS protocol supports mobility management functionality and user plane bearer activation, modification and deactivation. It is also responsible of ciphering and integrity protection of NAS signalling.
- LTE-Uu: The radio protocol of E-UTRAN between the UE and the eNodeB is specified in TS 36.300 ... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.1.1.4 SGSN - MME
|
Legend:
- GPRS Tunnelling Protocol for the control plane (GTP‑C): This protocol tunnels signalling messages between SGSN and MME (S3).
- User Datagram Protocol (UDP): This protocol transfers signalling messages. UDP is defined in RFC 768 [26].
Figure 5.1.1.4-1: Control Plane for S3 Interface
|
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.1.1.5 SGSN - S‑GW
|
Legend:
- GPRS Tunnelling Protocol for the control plane (GTP‑C): This protocol tunnels signalling messages between SGSN and S‑GW (S4).
- User Datagram Protocol (UDP): This protocol transfers signalling messages. UDP is defined in RFC 768 [26].
Figure 5.1.1.5-1: Control Plane for S4 interface
|
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.1.1.6 S‑GW - P‑GW
|
Legend:
- GPRS Tunnelling Protocol for the control plane (GTP‑C): This protocol tunnels signalling messages between S‑GW and P‑GW (S5 or S8).
- User Datagram Protocol (UDP): This protocol transfers signalling messages between S‑GW and P‑GW. UDP is defined in RFC 768 [26].
Figure 5.1.1.6-1: Control Plane for S5 a... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.1.1.7 MME - MME
|
Legend:
- GPRS Tunnelling Protocol for the control plane (GTP‑C): This protocol tunnels signalling messages between MMEs (S10).
- User Datagram Protocol (UDP): This protocol transfers signalling messages between MMEs. UDP is defined in RFC 768 [26].
Figure 5.1.1.7-1: Control Plane for S10 interface
|
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.1.1.8 MME - S‑GW
|
Legend:
- GPRS Tunnelling Protocol for the control plane (GTP‑C): This protocol tunnels signalling messages between MME and S‑GW (S11).
- User Datagram Protocol (UDP): This protocol transfers signalling messages. UDP is defined in RFC 768 [26].
Figure 5.1.1.8-1: Control Plane for S11 interface
|
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.1.1.9 MME - HSS
|
Legend:
- Diameter: This protocol supports transferring of subscription and authentication data for authenticating/authorizing user access to the evolved system between MME and HSS (S6a). Diameter is defined in RFC 3588 [31].
- Stream Control Transmission Protocol (SCTP): This protocol transfers signalling messages... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.1.1.10 MME - EIR
|
Legend:
- Diameter: This protocol supports UE identity check procedure between MME and EIR (S13). Diameter is defined in RFC 3588 [31].
- Stream Control Transmission Protocol (SCTP): This protocol transfers signalling messages. SCTP is defined in RFC 4960 [35].
Figure 5.1.1.10-1: Control Plane for S13 interface
|
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.1.1.11 Void
| |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.1.1.12 MME - CSS
|
Legend:
Diameter: This protocol supports transferring of CSG subscription data for roaming subscribers only between MME and CSS (S7a). Diameter is defined in RFC 3588 [31].
Stream Control Transmission Protocol (SCTP): This protocol transfers signalling messages. SCTP is defined in RFC 4960 [35].
Figure 5.1.1.1... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.1.1.13 MME - RCAF
|
Legend:
Nq-AP: This application layer protocol supports the IMSI and APN retrieval procedure between the RCAF and the MME.
Stream Control Transmission Protocol (SCTP): This protocol transfers signalling messages. SCTP is defined in RFC 4960 [35].
Figure 5.1.1.13-1: Control Plane for Nq interface
|
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.1.2 User Plane
| |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.1.2.1 UE - P‑GW user plane with E-UTRAN
|
Legend:
- GPRS Tunnelling Protocol for the user plane (GTP‑U): This protocol tunnels user data between eNodeB 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 ... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.1.2.3 UE - PDN GW user plane with 2G access via the S4 interface
|
Legend:
- GPRS Tunnelling Protocol for the user plane (GTP‑U): This protocol tunnels user data between SGSN 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 IP packets.
- UDP/IP: These are the backbone network protocols used for routing user data and ... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.1.2.4 UE - PDN GW user plane with 3G access via the S12 interface
|
Legend:
- GPRS Tunnelling Protocol for the user plane (GTP‑U): This protocol tunnels user data between UTRAN 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 IP packets.
- UDP/IP: These are the backbone network protocols used for routing user data and... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 5.1.2.5 UE - PDN GW user plane with 3G access via the S4 interface
|
NOTE: Please refer to TS 23.402 [2] for the corresponding stack for PMIP based S5/S8.
Legend:
- GPRS Tunnelling Protocol for the user plane (GTP‑U): This protocol tunnels user data between UTRAN and the SGSN, between SGSN and S‑GW as well as between the S‑GW and the P‑GW in the backbone network. GTP shall encapsu... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.