hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.8.4 SGSN selection function
| The SGSN selection function selects an available SGSN to serve a UE. The selection is based on network topology, i.e. the selected SGSN serves the UE's location and for overlapping SGSN service areas, the selection may prefer SGSNs with service areas that reduce the probability of changing the SGSN. When a MME/SGSN sel... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.8.5 Selection of PCRF
| The PDN GW and AF may be served by one or more PCRF nodes in the HPLMN and, in roaming with local breakout scenarios, one or more PCRF nodes in the VPLMN.
The selection of PCRF and linking of the different UE's PCC sessions over the multiple PCRF interfaces (e.g. Rx session, Gx session, S9 session etc.) for a UE IP CA... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.9 IP network related functions
| |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.9.1 Domain Name Service function
| The Domain Name Service function resolves logical PDN GW names to PDN GW addresses. This function is standard Internet functionality according to RFC 1034 [17], which allows resolution of any name to an IP address (or addresses) for PDN GWs and other nodes within the EPS.
|
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.9.2 DHCP function
| The Dynamic Host Configuration Function allows to deliver IP configuration information for UEs. This function is standard Internet functionality according to RFC 2131 [19], RFC 8415 [94] and RFC 4039 [25].
|
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.9.3 Explicit Congestion Notification
| 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].
|
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.10 Functionality for Connection of eNodeBs to Multiple MMEs
| An eNodeB may connect to several MMEs. This implies that an eNodeB must be able to determine which of the MMEs, covering the area where an UE is located, should receive the signalling sent from a UE. To avoid unnecessary signalling in the core network, a UE that has attached to one MME should generally continue to be s... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.11 E-UTRAN Sharing Function
| E‑UTRAN Sharing is an agreement between operators and shall be transparent to the user. This implies that an E‑UTRAN UE needs to be able to discriminate between core network operators available in a shared radio access network and that these operators can be handled in the same way as operators in non-shared networks. ... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.12 IMS Emergency Session Support
| |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.12.1 Introduction
| Clause 4.3.12 IMS Emergency Session provides an overview about functionality for emergency bearer services in a single clause. This overview applies to eCall Over IMS unless stated otherwise. The specific functionality is described in the affected procedures and functions of this specification. For discrepancies betwee... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.12.2 Architecture Reference Model for Emergency Services
| According to clause 4.2, the non-roaming architectures (Figure 4.2.1-1 and Figure 4.2.1-2) and roaming architecture with the visited operator's application function (Figure 4.2.2-3) apply for emergency services. The other roaming architectures with services provided by the home network do not apply for emergency servic... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.12.3 Mobility and Access Restrictions for Emergency Services
| When Emergency Services are supported and local regulation requires Emergency Sessions to be provided regardless of mobility or access restrictions, the Mobility Restrictions in clause 4.3.5.7, should not be applied to UEs receiving emergency services. When the E-RABs for emergency bearers are established, the ARP valu... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.12.4 PDN GW selection function (3GPP accesses) for Emergency Services
| When a PDN GW is selected for IMS emergency services support, the PDN GW selection function described in clause 4.3.8.1 for normal bearer services is applied to the Emergency APN or the MME selects the PDN GW directly from the MME Emergency Configuration Data. If the PDN GW selection function described in clause 4.3.8.... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.12.5 QoS for Emergency Services
| Where local regulation require supporting calls from an unauthorised caller, the MME may not have subscription data. Additionally, the local network may want to provide IMS emergency services support differently than what is allowed by a UE subscription. Therefore, the initial QoS values used for establishing emergency... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.12.6 PCC for Emergency Services
| Dynamic PCC is used for UEs establishing emergency service, the procedures are as described in TS 23.203 [6]. When establishing emergency bearer services with a PDN GW, according to clause 4.7.5, the PCRF provides the PDN GW with the QoS parameters, including an ARP value reserved for the emergency bearers to prioritiz... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.12.7 Load re-balancing between MMEs for Emergency Services
| As per load re-balancing procedures in clause 4.3.7.3, the MME is allowed to off-load ECM-CONNECTED mode UEs by initiating S1 Release procedures. When a UE is in ECM-CONNECTED mode with an active emergency bearer service, the MME should not release the UE for load re-balancing. The MME should wait until the UE initiate... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.12.8 IP Address Allocation
| Emergency bearer service is provided by the serving PLMN. The UE and PLMN must have compatible IP address versions in order for the UE to obtain a local emergency PDN connection. IP address allocation in the serving PLMN is provided per clause 5.3.1 with the exception that the PDN GW associated with the emergency APN s... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.12.9 Handling of PDN Connections for Emergency Bearer Services
| The default and dedicated EPS bearers of a PDN Connection associated with the emergency APN shall be dedicated for IMS emergency sessions and shall not allow any other type of traffic. The emergency bearer contexts shall not be changed to non-emergency bearer contexts and vice versa. The PDN GW shall block any traffic ... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.12.10 ISR function for Emergency Bearer Services
| When UE has only emergency bearer service, ISR does not apply.
|
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.12.11 Support of eCall Only Mode
| For service requirements for eCall only mode, refer to TS 22.101 [80].
A UE configured for eCall Only Mode shall remain in EMM-DEREGISTERED state, shall camp on a network cell when available but shall refrain from any Mobility Management or other signalling with the network. The UE may instigate Mobility Management an... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.13 Closed Subscriber Group functions
| Closed Subscriber Group identifies a group of subscribers who are permitted to access one or more CSG cells of the PLMN as a member of the CSG for a HeNB. The following CSG related functions are defined:
- CSG subscription handling function stores and updates the user's CSG subscription data at the UE and the network.... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.14 Location Service functions
| LCS procedures are described in the LCS stage 2 specification, see TS 23.271 [57].
In addition, in the Detach and Bearer Deactivation procedures, the MME shall inform the S-GW of the last known location of the UE, and shall provide information to enable the determination of the time at which the UE was in that locatio... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.15 Selected IP Traffic Offload (SIPTO) function
| The SIPTO function enables an operator to offload certain types of traffic at a network node close to that UE's point of attachment to the access network. The SIPTO function specified in this TS applies to IP PDN Types and Ethernet and Non-IP PDN Types.
SIPTO above RAN can be achieved by selecting a set of GWs (S-GW a... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.16 Local IP Access (LIPA) function
| The LIPA function enables a UE connected via a HeNB to access other entities in the same residential/enterprise network without the user plane traversing the mobile operator's network except HeNB subsystem.
The Local IP Access is achieved using a Local GW (L-GW) collocated with the HeNB.
LIPA is established by the UE... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.17 Support for Machine Type Communications (MTC)
| |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.17.1 General
| This clause provides an overview about functionality for Machine Type Communications according to service requirements described in TS 22.368 [66]. The specific functionality is described in the affected procedures and features of this and other specifications. For discrepancies between this overview clause and the det... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.17.2 Overview of protection from Potential MTC Related Overload
| The number of MTC devices may be several orders of magnitude greater than "traditional" devices. Many (but not all) MTC devices will be relatively stationary and/or generate low volumes of traffic. However, these UEs have the capability to generate normal quantities of signalling. As normal signalling from large number... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.17.3 Optimising periodic TAU Signalling
| To reduce network load from periodic TAU signalling and to increase the time until the UE detects a potential need for changing the RAT or PLMN (e.g. due to network problems) the longer values of the periodic TAU timer and Mobile Reachable timer shall be supported.
A long periodic RAU/TAU timer value may be locally co... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.17.4 UE configuration and usage of indicators
| A subscriber can by agreement with its operator be required to use UEs that are configured (see TS 24.368 [69]) to support one or more of the following options:
- UE configured for low access priority; and/or
- UE configured with a permission for overriding low access priority, which is only applicable for a UE that ... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.17.5 Void
| |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.17.6 Support of UEs configured for low access priority, Extended Access Barring and permission for override
| The feature is specified in TS 23.060 [7] clause 5.3.13.6.
|
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.17.7 High latency communication
| Functions for High latency communication may (depending on operator configuration) be used to handle mobile terminated (MT) communication with UEs being unreachable while using power saving functions (e.g. UE Power Saving Mode (see clause 4.3.22) or extended idle mode DRX (see clause 5.13a)) or UEs that are using a sat... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.17.8 Support for Non-IP Data Delivery (NIDD)
| |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.17.8.1 General
| The support of Non-IP data is part of the CIoT EPS Optimisations. A PDN Type "Non-IP" is used for Non-IP data. The Non-IP data delivery to SCS/AS is accomplished by one of two mechanisms:
- Delivery using SCEF as defined in clause 4.3.17.8.3.2.
- Delivery using a Point-to-Point (PtP) SGi tunnel as defined in clause 4... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.17.8.3 Delivery mechanism
| |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.17.8.3.1 General
| At each PDN connectivity request, the MME decides which delivery mechanism (SCEF based delivery or SGi based delivery) is used for delivering the Non-IP data between RAN and AS. An indication associated with the used APN determines if SCEF based delivery or SGi based delivery shall be used.
|
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.17.8.3.2 SCEF based delivery
| When the MME decides to use SCEF based delivery mechanism for Non-IP data, a PDN connection is established towards the selected SCEF. Such a PDN Connection is also known as an "SCEF Connection". The APN used for SCEF based delivery is an FQDN, which either resolves to an SCEF hostname or to an SCEF IP address.
The SCE... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.17.8.3.3 SGi based delivery
| |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.17.8.3.3.1 General
| When support of Non-IP data is provided at the SGi interface, different point-to-point tunnelling techniques may be used. Point-to-point tunnelling by UDP/IP encapsulation can be used as described in clause 4.3.17.8.3.3.2 below. Other techniques as described in clause 4.3.17.8.3.3 below may be used.
Support for the SG... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.17.8.3.3.2 SGi PtP tunnelling based on UDP/IP
| SGi PtP tunnelling based on UDP/IP may be used to deliver Non-IP data to AS via SGi.
A point-to-point tunnel is used by the P-GW towards the AS. The tunnel parameters (i.e. destination IP address and UDP port) for SGi PtP tunnelling based on UDP/IP are pre-configured on the P-GW. IP address allocation procedures for P... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.17.8.3.3.3 Other SGi PtP tunnelling mechanisms
| SGi PtP tunnelling mechanisms such as PMIPv6/GRE, L2TP, GTP-C/U, etc, may be used to deliver Non-IP data to AS via SGi. The general handling of such delivery mechanisms is as described below.
A point-to-point tunnel is established by the P-GW towards the AS. Depending on the type of protocol employed on the SGi PtP tu... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.17.9 Service Gap Control
| Service Gap Control is an optional feature intended for MTC/CIoT UEs to control the frequency at which these UEs can access the network. That is, to ensure a minimum time gap between consecutive Mobile Originated data communications initiated by the UE. This helps reducing peak load situations when there are a large nu... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.18 Multimedia Priority Service
| |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.18.1 General
| Multimedia Priority Service (MPS) allows certain subscribers (i.e. Service Users as per TS 22.153 [68]) priority access to system resources in situations such as during congestion, creating the ability to deliver or complete sessions of a high priority nature. Service Users are government-authorized personnel, emergenc... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.18.2 IMS-based Multimedia Priority Services
| |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.18.2.1 Originating IMS-based MPS Session
| IMS based MPS sessions are permitted to be originated from any UE, in addition to MPS-subscribed UEs.
The MPS-subscribed UE, based on the MPS IMS subscription information, operator's policy and national/regional regulations, may be given priority treatment for the default bearer and the EPS bearer carrying IMS signall... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.18.2.2 Terminating IMS-based MPS Session
| The terminating network identifies the priority of the IMS-based MPS session and applies priority treatment to ensure that the call is delivered with priority to the terminating user (either a Service User or normal user).
If the existing ARP of the default or dedicated EPS bearer that is used to transport IMS signall... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.18.3 Priority EPS Bearer Services
| The Service User receives on demand priority treatment according to its MPS profile, i.e. On-Demand. If the Service User is not authorized to use on-demand priority request, the Service User receives priority treatment (i.e. appropriate ARP and QCI ) at initial attach for all bearers, based on user profile data stored ... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.18.4 CS fallback
| CS Fallback allows users to fallback to GERAN/UTRAN/1x RTT while in E-UTRAN access thus allowing the network to transfer the call towards GERAN/UTRAN CS domain. In order to ensure that a priority CSFB call to/from a service user is given proper priority treatment in the EPS, MPS subscription indicates the user's CS pri... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.18.5 Network Congestion Controls for MPS
| Based on regional/national requirements and network operator policy, MPS shall be exempted from network congestion controls up to the point where further exemptions cause network instability. The MME should not apply NAS level congestion control for mobile initiated signalling with establishment cause set to highPriori... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.18.6 Load Re-balancing between MMEs for MPS
| When a UE is in ECM-CONNECTED mode with a bearer having an ARP associated with MPS, the MME should not release the UE for load re-balancing, except under critical conditions such as the need to perform an MME node restart. The MME should wait until the UE initiates a TAU or becomes ECM-IDLE before initiating load re-ba... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.19 Core Network node resolution
| |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.19.1 General
| The indication of mapped or native GUTI shall be signalled by the UE to the MME as an explicit indication in Attach Request and TAU Request messages. The indication of mapped or native P-TMSI/RAI shall be signalled by the UE to the SGSN as an explicit indication in Attach Request and RAU Request messages. The MME/SGSN ... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.19.2 MSB in LAC and MME Group ID
| For PLMNs deployed with such mechanism the MME differentiates between a GUMMEI mapped from P-TMSI/RAI and a native GUMMEI based on the value of most significant bit of the MME Group ID; i.e. the MSB is set to "0" then the GUMMEI is mapped from P-TMSI/RAI and if MSB is set to "1", the GUMMEI is a native one, as specifie... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.19.3 Explicit Indication
| For PLMNs deployed with such mechanism the MME differentiates between a GUTI mapped from P-TMSI/RAI or a native GUTI based on the explicit indication sent by the UE.
For PLMNs deployed with such mechanism the S4-SGSN differentiates between a P-TMSI/RAI mapped from GUTI or a native P-TMSI/RAI based on the explicit indi... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.20 Relaying function
| |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.20.1 General
| The relaying function enables an operator to improve and extend the coverage area by having a Relay Node (RN) wirelessly connected to an eNodeB serving the RN, called Donor eNodeB (DeNB), via a modified version of the E-UTRA radio interface called the Un interface as specified in TS 36.300 [5].
The relaying function a... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.20.2 RN startup and attach procedure
| |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.20.2.1 General
| The startup procedure for the Relay Node is based on the normal UE attach procedure and consists of the following two phases:
- Phase I: Attach for RN preconfiguration.
- Phase II: Attach for RN operation (MME of the RN).
NOTE: When the certificate-based solution is used, the RN uses USIM-INI in Phase I and USIM-RN ... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.20.2.2 Attach for RN preconfiguration
| The RN attaches to the E-UTRAN/EPC as a UE at power-up (i.e. the RN shall not include the RN indication in the RRC Connection establishment signalling). The eNodeB treats the RN as a normal UE when performing MME selection.
Because the eNodeB does not indicate that this is a RN in the S1 interface Initial UE message, ... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.20.2.3 Attach for RN operation
| To start relay operations, the normal attach procedure, with the following exceptions, is applied:
- The RN and the USIM-RN perform local security operations (e.g. establishment of a secure channel between them) as specified in TS 33.401 [41];
- The RN selects a cell from the list acquired during Phase I;
- The RN e... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.20.3 DeNB E-RAB activation/modification
| This procedure is used by the DeNB to change the EPS bearer allocation for the RN. The procedure is the same as the normal network-initiated bearer activation/modification procedure with the exception that the S-GW/P‑GW functionality (steps 1 and 6) is performed by the DeNB.
Figure 4.3.20.3-1: DeNB-initiated bearer ... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.21 Core Network assisted eNodeB parameters tuning
| |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.21.1 CN Assistance Information
| Core Network assisted eNodeB parameters tuning aids the eNodeB to minimize the UE state transitions and achieve optimum network behaviour. How the eNodeB uses the Core Network assistance information is not in scope of this specification and is implementation specific.
Core Network assistance information may be derived... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.21.2 Void
| |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.21.3 Core Network Assistance Procedures
| The MME provides CN assistance information to the eNodeB if available, during the setup of the S1 signalling connection (e.g., Attach, Service Request).
The following figure is a high level description of the transfer of information from an MME to eNodeB during a service request procedure.
Figure 4.3.21.3-1: Core N... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.21.4 Wake Up Signal Assistance
| |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.21.4.1 General
| The RAN and UE may use a Wake Up Signal (WUS) to reduce the UE's idle mode power consumption. The RAN sends the WUS shortly before the UE's paging occasion. The WUS feature enables UEs to determine that in the paging occasions immediately following their WUS occasion they will not be paged if their WUS is not transmitt... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.21.4.2 Group Wake Up Signal
| To support the Group Wake Up Signal feature, the WUS Assistance Information is used by the eNodeB to help determine the WUS group used when paging the UE (see TS 36.300 [5]).
The content of the WUS Assistance Information consists of the paging probability information. The paging probability information provides a metr... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.22 UE Power Saving Mode
| A UE may adopt a PSM that is described in TS 23.682 [74]. If a UE is capable of adopting a PSM and it wants to use the PSM it shall request an Active Time value and may request a Periodic TAU/RAU Timer value during every Attach and TAU procedures, which are handled as described in TS 23.682 [74]. The UE shall not reque... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.23 Access network selection and traffic steering based on RAN-assisted WLAN interworking
| As described in TS 36.300 [5], TS 36.304 [34], TS 36.331 [37] and TS 25.331 [33], UTRAN and E-UTRAN may provide RAN assistance parameters to the UE via RRC signalling. The RAN assistance parameters may e.g. include E-UTRAN signal strength and quality thresholds, WLAN channel utilization thresholds, WLAN backhaul data r... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.24 RAN user plane congestion management function
| |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.24.1 General
| The user plane congestion management function addresses how the system can effectively mitigate RAN user plane congestion in order to reduce the negative impact on the perceived service quality. The congestion mitigation measures include traffic prioritization, traffic reduction and limitation of traffic, and shall be ... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.24.2 RAN user plane congestion mitigation in the RAN
| Editor's note: Text to be added depending on the outcome of the UPCON study.
|
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.24.3 RAN user plane congestion mitigation in the CN
| RAN user plane congestion mitigation in the CN uses RAN OAM information, collected by the RAN Congestion Awareness Function (RCAF), to detect congestion. The RAN Congestion Awareness Function is further described in clause 4.4.12. This functionality is applicable only in the case of UTRAN/E-UTRAN accesses.
NOTE 1: The... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.25 Dedicated Core Networks (DCNs)
| |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.25.1 General
| This feature enables an operator to deploy multiple DCNs within a PLMN with each DCN consisting of one or multiple CN nodes. Each DCN may be dedicated to serve specific type(s) of subscriber. This is an optional feature and enables DCNs to be deployed for one or multiple RATs (e.g. GERAN, UTRAN, E-UTRAN, WB-E-UTRAN and... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.25.2 Considerations for Roaming
| In the case of roaming, if the HPLMN of the visiting UE does not support DCNs, i.e. doesn't provide the UE Usage Type, the serving MME/SGSN may select the DCN that serves the UE using operator specific policies based on other subscription or UE provided information.
In the case of roaming, if the HPLMN provides the UE... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.25.3 Considerations for Network Sharing
| If the network supports the MOCN configuration for network sharing (see TS 23.251 [24]), each network sharing operator has separate CN(s). Mechanisms for selection of serving operator for supporting and non-supporting UEs are defined in TS 23.251 [24]. Each of the sharing operators may deploy one or more DCNs.
If Sele... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.26 Support for Monitoring Events
| The Monitoring Events feature is intended for monitoring of specific events in 3GPP system and making such monitoring event information available via the Service Capability Exposure Function (SCEF). The architecture and related functions to support Monitoring Events are defined in TS 23.682 [74].
|
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.27 Paging Enhancements
| |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.27.1 Paging for Enhanced Coverage
| Support of UEs in Enhanced Coverage is specified in TS 36.300 [5].
Whenever S1 is released and Information for Enhanced Coverage is available for the UE, the eNodeB sends it to the MME as described in clause 5.3.5.
The MME stores the received Information for Enhanced Coverage and includes it in every subsequent Pagin... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.28 Restriction of use of Enhanced Coverage
| Support of UEs in Enhanced Coverage is specified in TS 36.300 [5].
The usage of Enhanced Coverage may require use of extensive resources (e.g. radio and signalling resources) from the network. This feature enables the operator to prevent specific subscribers from using Enhanced Coverage.
The UE indicates its capabili... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.29 3GPP PS Data Off
| |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.29.1 General
| This feature, when activated by the user, prevents transport via 3GPP access of all IP packets, Ethernet data and non-IP data except for those related to 3GPP PS Data Off Exempt Services. The 3GPP PS Data Off Exempt Services are a set of operator services, defined in TS 23.221 [27], that are the only allowed services w... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.30 Unlicensed spectrum aggregation (LAA/LWA/LWIP/NR-U)
| Unlicensed spectrum aggregation in EPS can use either LTE Licensed-Assisted Access (LAA) that is using the Carrier Aggregation (CA) RAN configuration defined in TS 36.300 [5], or LWA/LWIP aggregation using WLAN or NR-U as secondary RAT that is using the Dual Connectivity architecture defined in clause 4.3.2a and TS 36.... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.31 Subscription handling for Aerial UEs
| This clause describes subscription information handling in order to support operating Aerial UE function over E-UTRAN as defined in TS 36.300 [5] and TS 36.331 [37].
The eNodeB supporting Aerial UE function handling uses the per user information supplied by the MME to determine whether or not to allow the UE to use Ae... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.32 Support for Integrated access and backhaul (IAB)
| |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.32.1 IAB architecture and functional entities
| Integrated access and backhaul (IAB) enables wireless in-band and out-of-band relaying of NR Uu access traffic via NR Uu backhaul links.
At high level, IAB has the following characteristics:
- IAB uses the CU/DU architecture defined in TS 38.401 [90], and the IAB operation via F1 (between IAB-donor and IAB-node) is i... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.32.2 System enhancements to support IAB
| In IAB operation, the IAB-UE interacts with the EPC using procedures defined for UE. The IAB-node gNB-DU only interacts with the IAB-donor-CU and follows the CU/DU design defined in TS 38.401 [90].
For the IAB-UE operation, the existing UE authentication methods as defined in TS 33.401 [41] apply. For EPC, only USIM b... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.32.3 Data handling and QoS support with IAB
| Control plane and user plane protocol stacks for IAB operation are defined in TS 38.300 [93].
|
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.32.4 Mobility support with IAB
| For UEs, all existing NR intra-RAT mobility and dual-connectivity procedures are supported with IAB. During UE mobility or dual-connectivity procedures, backhaul channels including IAB layer may be updated. This update is carried out by the IAB-donor-CU and signalled to the IAB-nodes via RRC and/or F1-C. The update is ... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.32.5 Charging support with IAB
| IAB-donor has all the information regarding the UE and the IAB-node and corresponding mapping of the bearers. The PDN connection for the UE and IAB-node are separate from IAB-node onwards to the core network. Therefore, the existing charging mechanism as defined in clause 5.7A can be used to support IAB.
|
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.33 Support for Multi-USIM UE
| |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.33.1 General
| A network and a Multi-USIM UE may support one or more of the following features for Multi-USIM UE operation:
- Connection Release, as described in clause 4.3.33.2.
- Paging Cause Indication for Voice Service, as described in clause 4.3.33.3.
- Reject Paging Request, as described in clause 4.3.33.4.
- Paging Timing ... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.33.2 Connection Release
| A Multi-USIM UE may request to be released to ECM-IDLE state for a USIM due to activity on another USIM if both the UE and the network indicate to each other the Connection Release feature is supported. A Multi-USIM UE indicates that it requests to be released to ECM-IDLE state for the USIM by initiating the Service Re... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.33.3 Paging Cause Indication for Voice Service
| A Multi-USIM UE and the network may support the Paging Cause Indication for Voice Service feature.
The MME that supports Paging Cause Indication for Voice Service feature should provide a Voice Service Indication in the S1AP Paging message for the MMTel voice service, only if the UE indicates the Paging Cause Indicati... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.33.4 Reject Paging Request
| A Multi-USIM UE may respond to a page for a USIM with an indication to the MME that the UE does not accept the paging and requests to be released to ECM-IDLE state after sending this response, if both UE and network indicate to each other the Reject Paging Request feature is supported.
Upon being paged, the Multi-USIM... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.33.5 Paging Timing Collision Control
| To avoid possible paging occasion collision and to enhance the likelihood that paging is received successfully for different USIMs, a Multi-USIM UE may provide, for at least one USIM, a Requested IMSI Offset value that is used for the determination of paging occasions. Upon reception of a Requested IMSI Offset value fr... |
b043aa03d2112b1c3a444522800f3b3a | 23.401 | 4.3.33.6 Paging Restriction
| A Multi-USIM UE and the network may support Paging Restriction. A Multi-USIM UE, if the MME indicates that the network supports Paging Restriction feature, may indicate Paging Restriction Information in an Extended Service Request or a Tracking Area Update Request (including the case where the Tracking Area Update is p... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.