Search is not available for this dataset
doc_id
int64 1
6.72k
⌀ | Section
stringlengths 5
247
⌀ | Content
stringlengths 501
147k
⌀ | Source
stringclasses 456
values | Document Title
stringclasses 22
values | Working Group
stringclasses 21
values | Series Subject
stringclasses 9
values | Subclause
stringlengths 1
13
⌀ |
|---|---|---|---|---|---|---|---|
1,401 | – CGI-InfoEUTRALogging | The IE CGI-InfoEUTRALogging indicates EUTRA cell related information, which is reported by the UE as part of RLF reporting procedure. CGI-InfoEUTRALogging information element -- ASN1START -- TAG-CGI-INFOEUTRALOGGING-START CGI-InfoEUTRALogging ::= SEQUENCE { plmn-Identity-eutra-5gc PLMN-Identity OPTIONAL, trackingAreaCode-eutra-5gc TrackingAreaCode OPTIONAL, cellIdentity-eutra-5gc BIT STRING (SIZE (28)) OPTIONAL, plmn-Identity-eutra-epc PLMN-Identity OPTIONAL, trackingAreaCode-eutra-epc BIT STRING (SIZE (16)) OPTIONAL, cellIdentity-eutra-epc BIT STRING (SIZE (28)) OPTIONAL } -- TAG-CGI-INFOEUTRALOGGING-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
1,402 | 4.10.1.2 Average sub-band CQI | This measurement provides the average value of the sub-band CQI (Channel Quality Indicator) reported by UEs in the cell. A subband is a set of k contiguous PRBs where k is a function of system bandwidth. Note the last subband in set S may have fewer than k contiguous PRBs depending on . The number of subbands for system bandwidth given by is defined by. The subbands shall be indexed in the order of increasing frequency and non-increasing sizes starting at the lowest frequency. CC This measurement is obtained by computing the average value of the sub-band CQI reported by UEs in the cell within the measurement granularity period. One value is produced for each sub-band. The number of sub-bands depends on the bandwidth used, as specified in [18]. When spatial multiplexing is used, CQI for both code words should be considered. Float value. CARR.AvgSubCQI.SubbandX where SubbandX represents the sub-band index, as specified in [18]. EUtranCellFDD EUtranCellTDD Valid for packet switching. EPS | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.10.1.2 |
1,403 | I.10.4.2 Support for N5CW devices in SNPN with CH | N5CW devices may use the credentials from a Credentials Holder AAA server to access SNPN services via trusted WLAN access. Figure I.10.4.2-1: Procedure for trusted WLAN access using Credentials Holder AAA Server 0 prior conditions and assumptions are described in step 0 in clauses 7A.2.4 and I.2.2.2.2. 1-5 as specified in clause 7A.2.4. In addition, if the construction of SUCI as described in clause 6.12 cannot be used and if the employed EAP method supports SUPI privacy, the UE may send an anonymous SUCI based on configuration.. 6-8 are replaced by the steps 3-15 in clause I.2.2.2.2. 9-14 as specified in clause 7A.2.4. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | I.10.4.2 |
1,404 | 4.25.4 NEF Anchored Mobile Originated Data Transport | Figure 4.25.4-1 illustrates the NEF Anchored Mobile Originated Data Transport procedure. Figure 4.25.4-1: NEF Anchored Mobile Originated Data Transport procedure 1. The UE sends a NAS message with unstructured data according to steps 1-4 of the procedure for UPF anchored Mobile Originated Data Transport in Control Plane CIoT 5GS Optimisation (see clause 4.24.1). The Reliable Data Service header is included if the Reliable Data Service is enabled. 2. [Conditional] In the case of home-routed roaming the V-SMF sends the Nsmf_PDUSession_TransferMOData request to the H-SMF including MO small data. 3. The (H-)SMF sends the Nnef_SMContext_Delivery Request (User Identity, PDU session ID, unstructured data) message to the NEF. 4. When the NEF receives the unstructured data and finds an NEF PDU Session context and the related T8 Destination Address, then it sends the unstructured data to the AF that is identified by the T8 Destination address in a Nnef_NIDD_DeliveryNotify Request (GPSI, unstructured data, Reliable Data Service Configuration). If no T8 Destination address is associated with the UE's PDN connection, the data is discarded, the Nnef_NIDD_DeliveryNotify Request is not sent and the flow continues at step 6. The Reliable Data Service Configuration is used to provide the AF with additional information such as indicate if an acknowledgement was requested and port numbers for originator application and receiver application, when the Reliable Data Service is enabled. Editor's note: It is left to Stage 3 whether or not the NEF aggregates Nnef_NIDD_DeliveryNotify Request messages to the AF. 5. The AF responds to the NEF with a Nnef_NIDD_DeliveryNotify Response (Cause). 6. The NEF sends Nnef_SMContext_Delivery Response to the SMF. If the NEF cannot deliver the data, e.g. due to missing AF configuration, the NEF sends an appropriate error code to the SMF. 7. [Conditional] In the case of home-routed roaming, the H-SMF responds to the V-SMF with a Nsmf_PDUSession_TransferMOData (Result Indication) Response. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.25.4 |
1,405 | 5.46 Assistance to AI/ML Operations in the Application Layer 5.46.1 General | This clause describes the list of 5GC enablers to support the following AI/ML operations in the Application layer over the 5G System: - AI/ML operation splitting between AI/ML endpoints; - AI/ML model/data distribution and sharing; - Distributed/Federated Learning. NOTE 1: Requirements on 5G System assistance to AI/ML operations in the Application layer are specified in clause 6.40 of TS 22.261[ Service requirements for the 5G system ] [2]. The AF may subscribe to NEF monitoring events as described in clause 4.15.3.2.3 of TS 23.502[ Procedures for the 5G System (5GS) ] [3] in order to assist its application AI/ML operations. For example, the AF may subscribe to session inactivity time monitoring event in order to assist the AI/ML application server in scheduling available UE(s) to participate in the AI/ML operation (e.g. Federated Learning). In addition, the AF may subscribe to NEF to be notified on the traffic volume exchanged between the UE and the AI/ML application server in order to assist the AF with the transfer of AI/ML data. The AF that aims to provide an AI/ML operation may request assistance from the 5GC as described in clause 5.46.2. The AF initially provides a list of target member UE(s) and at least one filtering criterion, when subscribing to the NEF to be notified about a subset list of UE(s) (i.e. list of candidate UE(s)) that fulfil certain filtering criteria. Details of the procedures are described in clause 4.15.13 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. This subset list of UE(s) may become the member UE(s) used in the AI/ML operation depending on the AF's final decision, considering its internal logic. Alternatively, the AF may select the list of UEs for the AI/ML operation without NEF involvement as described in Annex I of TS 23.502[ Procedures for the 5G System (5GS) ] [3]: in this case, the AF determines a list of UEs without any assistance from the NEF and may use, for example, NWDAF analytics to assist with the AI/ML operation over 5G System. The AF may request the network to provide a recommended time window for the AI/ML operation using the Planned Data Transfer with QoS (PDTQ) requirements and procedures as described in clause 6.1.2.7 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45] and in clause 4.16.15 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. At the time or during the AI/ML operation, the AF may request the serving NEF to provide QoS for a list of UEs. Each UE is identified by its UE IP address. The AF may subscribe to QoS Monitoring which may include also Consolidated Data Rate monitoring as described in clause 5.45 and in clause 4.15.6.13 of TS 23.502[ Procedures for the 5G System (5GS) ] [3] for those AF requests for QoS that result in a successful resource allocation. The AF provides QoS parameters that are derived from the performance requirements listed in clause 7.10 of TS 22.261[ Service requirements for the 5G system ] [2]. As a result of the AF subscription to NEF to provide the subset list of UE(s) that fulfil certain filtering criteria, the AF may be notified about changes in the subset list of UE(s) and in such a case the AF may determine a updated list of UEs used in the AI/ML operation from the new subset list of UE(s) provided by NEF, and the AF may request a new recommended time window for the AI/ML operation using the Planned Data Transfer with QoS (PDTQ) requirements as described in clause 6.1.2.7 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45] and in clause 4.16.15 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. The AF may request the NEF to provide QoS for the updated list of UEs, each identified by UE IP address, that results in QoS resources previously allocated to some UEs to be released, while QoS resources for other UEs to be allocated and QoS monitoring to be initiated. The AF may also subscribe to, or request Network Data Analytics as defined in TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [86], such as End-to-end data volume transfer time analytics, DN performance analytics, Network performance analytics, UE mobility analytics, WLAN performance analytics etc. in order to assist its AI/ML operations. The AF hosting an AI/ML based application may provision the Expected UE Behaviour parameters captured in Table 4.15.6.3-1 of TS 23.502[ Procedures for the 5G System (5GS) ] [3] and/or the Application-Specific Expected UE Behaviour parameter(s) captured in Table 4.15.6.3f-1 of TS 23.502[ Procedures for the 5G System (5GS) ] [3] to the 5GC. The parameters may be provisioned with corresponding confidence and/or accuracy levels, and a threshold may also be provided to the UDM by the NF (e.g. AMF or SMF) subscribing to such externally provisioned parameters as described in clause 4.15.6.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. In addition, the following principles apply when 5GS assists the AI/ML operation at the application layer: - AF requesting 5GS assistance to AI/ML operations in the application layer shall be authorized by the 5GC using the existing mechanisms. NOTE 2: In this Release, assistance to AI/ML operations in the application layer is not supported for roaming UEs. NOTE 3: Policy and charging control as defined in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45] can be used for traffic related to AI/ML operations as described in clause 6.40.1 of TS 22.261[ Service requirements for the 5G system ] [2]. Capabilities based on Flow Based Charging can be used together with an appropriate PCF configuration for charging differentiation between AI/ML traffic and other type of traffic from the same application. As long as the AF can provide different filter information as described in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45] for the AI/ML traffic and the other type of traffic from the same application in the procedures utilized for the resource request, the PCF can assign different rating groups (i.e. charging key) or rating group + service-ids based on an appropriate PCF configuration. The UPF will then handle such traffic accordingly. This enables charging of AI/ML traffic according to operator's policies. - Application AI/ML decisions and their internal operation logic reside at the AF and UE application client and is out of scope of 3GPP. - Based on application logic, it is the application decision whether to request assistance from 5GC, e.g. for the purpose of selection of Member UEs that participate in certain AI/ML operation. - In this Release, 5GS assistance to AI/ML operations in the application layer is conducted within a single slice. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.46 |
1,406 | 4.2.2.4 Number of E-RAB successfully released | This measurement provides the number of E-RABs successfully released. The measurement is split into subcounters per E-RAB QoS level (QCI). CC On transmission by the eNodeB/RN of an E-RAB RELEASE RESPONSE or UE CONTEXT RELEASE COMPLETE, or E-RAB Release Indication or a RESET ACKNOWLEDGE to MME/DeNB; or E-RAB is released successfully by the eNB/RN after receiving PATH SWITCH REQUEST ACKNOWLEDGE or PATH SWITCH REQUEST FAILED messageby which some or all E-RABs in the corresponding PATH SWITCH REQUEST are to be released; or the E-RAB is released successfully at the source EUtran cell by the eNB/RN after receiving RRCConnectionReconfigurationComplete message from the UE, indicating a successful intra-eNB/RN handover (see TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8]); or the E-RAB released successfully by source eNB/RN after receiving UE CONTEXT RELEASE from another eNB/DeNB; or on receipt by the eNB/RN of a RESET ACKNOWLEDGE message from MME/DeNB . E ach corresponding E-RAB successfully released is added to the relevant measurenment per QCI, the possible QCIs are included in TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [9] , the same E-RAB shall not be counted repeatly but only one in case it appears more than one time in the same or different messages triggering this measurement. The sum of all supported per QCI measurements shall equal the total number of E-RABs fully released. In case only a subset of per QCI measurements is supported, a sum subcounter will be provided first. Each measurement is an integer value. The number of measurements is equal to the number of QCIs plus a possible sum value identified by the .sum suffix. The measurement name has the form ERAB.RelSuccNbr.QCI where QCI identifies the E-RAB level quality of service class. EUtranCellFDD EUtranCellTDD Valid for packet switched traffic EPS | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.2.2.4 |
1,407 | – SRS-CarrierSwitching | The IE SRS-CarrierSwitching is used to configure for SRS carrier switching when PUSCH is not configured and independent SRS power control from that of PUSCH. SRS-CarrierSwitching information element -- ASN1START -- TAG-SRS-CARRIERSWITCHING-START SRS-CarrierSwitching ::= SEQUENCE { srs-SwitchFromServCellIndex INTEGER (0..31) OPTIONAL, -- Need M srs-SwitchFromCarrier ENUMERATED {sUL, nUL}, srs-TPC-PDCCH-Group CHOICE { typeA SEQUENCE (SIZE (1..32)) OF SRS-TPC-PDCCH-Config, typeB SRS-TPC-PDCCH-Config } OPTIONAL, -- Need M monitoringCells SEQUENCE (SIZE (1..maxNrofServingCells)) OF ServCellIndex OPTIONAL, -- Need M ... } SRS-TPC-PDCCH-Config ::= SEQUENCE { srs-CC-SetIndexlist SEQUENCE (SIZE(1..4)) OF SRS-CC-SetIndex OPTIONAL -- Need M } SRS-CC-SetIndex ::= SEQUENCE { cc-SetIndex INTEGER (0..3) OPTIONAL, -- Need M cc-IndexInOneCC-Set INTEGER (0..7) OPTIONAL -- Need M } -- TAG-SRS-CARRIERSWITCHING-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
1,408 | 7.6.1 In-band blocking | In-band blocking is defined for an unwanted interfering signal falling into the UE receive band or into the first 15 MHz below or above the UE receive band at which the relative throughput shall meet or exceed the minimum requirement for the specified measurement channels. For CA configurations including Band 46, in-band blocking in Band 46 is defined for a 20 MHz unwanted interfering signal falling into the UE receive band or into the first 60 MHz below or above the UE receive band (Table 7.6.1.1A-0a and Table 7.6.1.1A-0b). For CA configurations including Band 49, in-band blocking in Band 49 is defined for an unwanted interfering signal falling into the UE receive band or into the first 60 MHz below or above the UE receive band (Table 7.6.1.1A-0a and Table 7.6.1.1A-0b). | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 7.6.1 |
1,409 | 6.35 Service Function Chaining 6.35.2 General Requirements | The following requirements apply for supporting enhancement of service function chaining for 5G networks: - The network operator shall be able to define and modify service function chaining policies for steering traffic on per application per UE basis through required service function chaining with ordered service functions to improve the user’s QoE. - Service functions chaining policies shall be able to distinguish between upstream and downstream traffic. - The coexistence of traffic with and without service function chaining shall be supported. - Service function chaining shall provide suitable means for authorized third parties to request a chain of service functions provided by the network operator based on operator’s service function chaining policies. - In case of roaming, the HPLMN shall be able to apply traffic steering policies and service function chaining polices for home routed traffic. - In case of roaming with local breakout, the HPLMN shall be able to provide the traffic steering policies and service function chaining policies to the VPLMN providing local breakout with support of service function chaining. - Service function chaining shall support deployments where the Hosted Services are provided by the operator and deployments where the Hosted Services are provided by a third party. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.35 |
1,410 | 5.17.5 Service Exposure in Interworking Scenarios 5.17.5.1 General | Clause 4.3.5 shows the Service Exposure Network Architecture in scenarios where for EPC-5GC Interworking is required. In scenarios where interworking between 5GS and EPC is possible, the network configuration is expected to associate UEs with SCEF+NEF node(s) for Service Capability Exposure. The SCEF+NEF hides the underlying 3GPP network topology from the AF (e.g. SCS/AS) and hides whether the UE is served by 5GC or EPC. If the service exposure function that is associated with a given service for a UE is configured in the UE's subscription information, then an SCEF+NEF identity shall be used to identify the exposure function. For example, if a UE is capable of switching between EPC and 5GC, then the SCEF ID that is associated with any of the UE's APN configurations should point to an SCEF+NEF node. For external exposure of services related to specific UE(s), the SCEF+NEF resides in the HPLMN. Depending on operator agreements, the SCEF+NEF in the HPLMN may have interface(s) with NF(s) in the VPLMN. The SCEF+NEF exposes over N33 the same API as the SCEF supports over T8. If CAPIF is not supported, the AF is locally configured with the API termination points for each service. If CAPIF is supported, the AF obtains the service API information from the CAPIF core function via the Availability of service APIs event notification or Service Discover Response as specified in TS 23.222[ Common API Framework for 3GPP Northbound APIs ] [64]. The common state information shall be maintained by the combined SCEF+NEF node in order to meet the external interface requirements of the combined node. The common state information includes at least the following data that needs to be common for the SCEF and NEF roles of SCEF+NEF: - SCEF+NEF ID (must be the same towards the AF). - SCEF+NEF common IP address and port number. - Monitoring state for any ongoing monitoring request. - Configured set of APIs supported by SCEF+ NEF. - PDN Connection/PDU Session State and NIDD Configuration Information, including Reliable Data Service state information. - Network Parameter Configuration Information (e.g. Maximum Response Time and Maximum Latency). The SCEF+NEF need not perform the same procedures for the configuration of monitoring events towards the HSS+UDM twice. For example, if the HSS+UDM is deployed as a combined node, a monitoring event only need to be configured by the SCEF+NEF just once. The SCEF+NEF may configure monitoring events applicable to both EPC and 5GC using only 5GC procedures towards UDM. In this case, the SCEF+NEF shall indicate that the monitoring event is also applicable to EPC (i.e. the event must be reported both by 5GC and EPC) and may include a SCEF address (i.e. if the event needs to be configured in a serving node in the EPC and the corresponding notification needs to be sent directly to the SCEF). If the HSS and UDM are deployed as separate network entities, UDM shall use HSS services to configure the monitoring event in EPC as defined in TS 23.632[ User data interworking, coexistence and migration; Stage 2 ] [102]. The UDM shall return an indication to SCEF+NEF of whether the configuration of the monitoring event in EPC was successful. In the case that the UDM reports that the configuration of a monitoring event was not possible in EPC, then the SCEF+NEF may configure the monitoring event using EPC procedures via the HSS as defined in TS 23.682[ Architecture enhancements to facilitate communications with packet data networks and applications ] [36]. NOTE 1: The SCEF+NEF uses only 5GC procedures to configure monitoring events in EPC and 5GC. NOTE 2: In terms of the CAPIF, the SCEF+NEF is considered a single node. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.17.5 |
1,411 | 4.4 Functions | The following functions are supported by MAC sublayer: - mapping between logical channels and transport channels; - multiplexing of MAC SDUs from one or different logical channels onto transport blocks (TB) to be delivered to the physical layer on transport channels; - demultiplexing of MAC SDUs from one or different logical channels from transport blocks (TB) delivered from the physical layer on transport channels; - scheduling information reporting; - error correction through HARQ; - priority handling between UEs by means of dynamic scheduling; - priority handling between logical channels of one MAC entity; - Logical Channel prioritisation; - transport format selection; - radio resource selection for SL. The location of the different functions and their relevance for uplink and downlink respectively is illustrated in Table 4.4-1. Table 4.4-1: MAC function location and link direction association. | 3GPP TS 36.321 | Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification | RAN2 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 4.4 |
1,412 | 4.4.3 Charging services Reference point | The common charging architectures are mapped into the specific domain/subsystem/service charging architectures in the respective middle tier TSs, which contain in their reference point representation, the following reference points: N28: Reference point between PCF and CHF defined in TS 23.501[ System architecture for the 5G System (5GS) ] [215]. N40: Reference point between SMF and the CHF in the same PLMN defined in clause 4.2 of TS 32.255[ Telecommunication management; Charging management; 5G data connectivity domain charging; Stage 2 ] [15]. N41: Reference point between AMF and CHF in HPLMN defined in clause 4.2.2 of TS 32.256[ Charging management; 5G connection and mobility domain charging; Stage 2 ] [16]. N42: Reference point between AMF and CHF in VPLMN defined in clause 4.2.2 of TS 32.256[ Charging management; 5G connection and mobility domain charging; Stage 2 ] [16]. N44: Reference point between NEF and CHF defined in clause 4.4 of TS 32.254[ Telecommunication management; Charging management; Exposure function Northbound Application Program Interfaces (APIs) charging ] [14]. N45: Reference point between IMS Node and CHF defined in clause 4.4 of TS 32.260[ Telecommunication management;Charging management;IP Multimedia Subsystem (IMS) charging ] [20]. N46: Reference point between SMSF and CHF defined in clause 4.4 of TS 32.274[ Telecommunication management; Charging management; Short Message Service (SMS) charging ] [34]. N47: Reference point between SMF and the CHF in different PLMNs defined in clause 4.2 of TS 32.255[ Telecommunication management; Charging management; 5G data connectivity domain charging; Stage 2 ] [15]. N48: Reference point between 5G DDNMF and the CHF in different PLMNs defined in clause 4.4 of TS 32.277[ Telecommunication management; Charging management; Proximity-based Services (ProSe) charging ] [37]. N49: Reference point between EES and CHF defined in clause 4.2.3 of TS 32.257[ Telecommunication management; Charging management; Edge computing domain charging ] [17]. N100: Reference point between MMS node and CHF defined in clause 4.4 of TS 32.270[ Telecommunication management; Charging management; Multimedia Messaging Service (MMS) charging ] [30]. N101: Reference point between MB-SMF and the CHF in the same PLMN defined in clause 4.2 of TS 32.255[ Telecommunication management; Charging management; 5G data connectivity domain charging; Stage 2 ] [15]. N107: Reference point between two CHFs defined in clause 4.2 of TS 32.255[ Telecommunication management; Charging management; 5G data connectivity domain charging; Stage 2 ] [15] and clause 4.2.2 of TS 32.256[ Charging management; 5G connection and mobility domain charging; Stage 2 ] [16] | 3GPP TS 32.240 | Telecommunication management; Charging management; Charging architecture and principles | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.4.3 |
1,413 | 6.6.2.1.1 Minimum requirement | The power of any UE emission shall not exceed the levels specified in Table 6.6.2.1.1-1 for the specified channel bandwidth. Table 6.6.2.1.1-1: General E-UTRA spectrum emission mask NOTE: As a general rule, the resolution bandwidth of the measuring equipment should be equal to the measurement bandwidth. However, to improve measurement accuracy, sensitivity and efficiency, the resolution bandwidth may be smaller than the measurement bandwidth. When the resolution bandwidth is smaller than the measurement bandwidth, the result should be integrated over the measurement bandwidth in order to obtain the equivalent noise bandwidth of the measurement bandwidth. | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.6.2.1.1 |
1,414 | 10.5 Other information elements | The different formats (V, LV, T, TV, TLV) and the five categories of information elements (type 1, 2, 3, 4, and 6) are defined in 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [20]. The first octet of an information element in the non-imperative part contains the IEI of the information element. If this octet does not correspond to an IEI known in the message, the receiver shall determine whether this IE is of type 1 or 2 (i.e. it is an information element of one octet length), an IE of type 4 (i.e. that the next octet is the length indicator indicating the length of the remaining of the information element) or an IE of type 6 (i.e. that the next 2 octets are the length indicator indicating the length of the remaining of the information element (see 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [20]). This allows the receiver to jump over unknown information elements and to analyse any following information elements. The information elements which are common for at least two of the three protocols Radio Resources management, Mobility Management and Call Control, are listed in subclause 10.5.1. The information elements for the protocols Mobility Management and Call Control are listed in subclauses 10.5.3 and 10.5.4 respectively. Default information element identifiers are listed in annex K. NOTE: Different information elements may have the same default information element identifier if they belong to different protocols. The descriptions of the information element types in subclauses 10.5.1, 10.5.3, and 10.5.4 are organized in alphabetical order of the IE types. Each IE type is described in one subclause. The subclause may have an introduction: - possibly explaining the purpose of the IE; - possibly describing whether the IE belongs to type 1, 2, 3, 4 or 5; - possibly indicating the length that the information element has if it is either type 5 or if it is used in format TV (type 1 and 3) or TLV (type 4). A figure of the subclause defines the structure of the IE indicating: - possibly the position and length of the IEI. (However it depends on the message in which the IE occurs whether the IE contains an IEI.); - the fields the IE value part is composed of; - possibly the position and length of the length indicator. (However it depends on the IE type whether the IE contains a length indicator or not.); - possibly octet numbers of the octets that compose the IE (see clause a) below). Finally, the subclause contains tables defining the structure and value range of the fields that compose the IE value part. The order of appearance for information elements in a message is defined in clause 9. The order of the information elements within the imperative part of messages has been chosen so that information elements with 1/2 octet of content (type 1) go together in succession. The first type 1 information element occupies bits 1 to 4 of octet N, the second bits 5 to 8 of octet N, the third bits 1 to 4 of octet N + 1 etc. If the number of type 1 information elements is odd then bits 5 to 8 of the last octet occupied by these information elements contains a spare half octet IE in format V. Where the description of information elements in the present document contains bits defined to be "spare bits", these bits shall set to the indicated value (0 or 1) by the sending side, and their value shall be ignored by the receiving side. With few exceptions, spare bits are indicated as being set to "0" in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 10.5 |
1,415 | D.3.4 3G SGSN to MME combined hard handover and SRNS relocation procedure | The 3G Gn/Gp SGSN to MME Combined Hard Handover and SRNS Relocation procedure is illustrated in Figure D.3.4-1. Any steps descriptions that are from TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [7] are shown as italic text and remain unmodified. In those step descriptions an MS stands for UE, new SGSN for new MME and GGSN for P-GW. The procedure between E-UTRAN eNodeB and UE, and between E-UTRAN eNodeB and MME are compliant with the equivalent procedure parts in clause 5.5: Handover. If emergency bearer services are ongoing for the UE, the MME checks as part of the Tracking Area Update in the execution phase, if the handover is to a restricted area and if so MME releases the non-emergency bearers as specified in clause 5.10.3. Figure D.3.4-1: 3G Gn/Gp SGSN to MME combined hard handover and SRNS relocation procedure 1. The source RNC decides to initiate a handover to E-UTRAN. 2. The source SRNC sends a Relocation Required message (Relocation Type, Cause, Source ID, Target ID, Source RNC To Target RNC Transparent Container) to the old SGSN. The source SRNC shall set Relocation Type to "UE Involved". Source RNC To Target RNC Transparent Container includes the necessary information for relocation co-ordination, security functionality and RRC protocol context information (including MS Capabilities). NOTE 1: This step is unmodified compared to pre-Rel-8. The target eNodeB acts as the target RNC. NOTE 1a: The Target ID identifies an eNodeB. With Rel-8 Iu functionality this is an eNodeB ID. As an implementations option for supporting introduction scenarios with pre-Rel8 SGSNs the source RNC may be configured to use RNC IDs instead of eNodeB IDs to identify a target eNodeB. The Cause is relayed transparently by the SGSN to the MME and the MME maps RANAP cause code to an S1AP cause code. Source RNC to Target RNC Transparent Container carries information for the target eNodeB. This container is relayed transparently by the SGSN. 3. The old SGSN determines from the Target ID if the SRNS relocation is intra-SGSN SRNS relocation or inter-SGSN SRNS relocation. In the case of inter-SGSN SRNS relocation the old SGSN initiates the relocation resource allocation procedure by sending a Forward Relocation Request message (IMSI, Tunnel Endpoint Identifier Signalling, MM Context, PDP Context, Target Identification, RAN Transparent Container, RANAP Cause, GCSI) to the new SGSN. For relocation to an area where Intra Domain Connection of RAN Nodes to Multiple CN Nodes is used, the old SGSN may – if it provides Intra Domain Connection of RAN Nodes to Multiple CN Nodes -have multiple target SGSNs for each relocation target in a pool area, in which case the old SGSN will select one of them to become the new SGSN, as specified in TS 23.236[ Intra-domain connection of Radio Access Network (RAN) nodes to multiple Core Network (CN) nodes ] [30]. PDP context contains GGSN Address for User Plane and Uplink TEID for Data (to this GGSN Address and Uplink TEID for Data, the old SGSN and the new SGSN send uplink packets). At the same time a timer is started on the MM and PDP contexts in the old SGSN (see Routing Area Update procedure in clause "Location Management Procedures (Iu mode)"). The Forward Relocation Request message is applicable only in the case of inter-SGSN SRNS relocation. The old SGSN 'sets' the GCSI flag if the MM context contains GPRS CAMEL Subscription Information. NOTE 2: This step is unmodified compared to pre-Rel-8. The new MME acts as the new SGSN, and the P-GW as the GGSN. The GGSN user plane address and uplink TEID are the P-GW user plane address and TEID. The MME maps the PDP context parameters to EPS bearers. 4. The MME selects a Serving GW and sends a Create Session Request (bearer context(s) with PDN GW addresses and TEIDs for uplink traffic, APN-AMBR, Serving Network, UE Time Zone) message per PDN connection to the target Serving GW. For relocation from Gn/Gp SGSN, the target MME provides the APN-AMBR if not received explicitly from the Gn/Gp SGSN based on the mapping from MBR (as specified in Annex E) to the Serving GW. 5. The Serving GW allocates the S-GW addresses and TEIDs for the uplink traffic on S1_U reference point (one TEID per bearer). The target Serving GW sends a Create Session Response (Serving GW addresses and uplink TEID(s) for user plane) message back to the target MME. 6. The new MME requests the target eNodeB to establish the bearer(s) by sending the message Handover Request (UE Identifier, S1AP Cause, CN Domain Indicator, KeNB, NAS Security Parameters to E-UTRAN, EPS Bearers to be setup list, Source to Target Transparent Container, Serving GW Address(es) and TEID(s) for User Traffic Data, Handover Restriction List). S1AP Cause indicates the RANAP Cause as received from SGSN. Source to Target Transparent Container contains the RAN Transparent Container as received from SGSN. The NAS Security Parameters to E-UTRAN includes the NAS Integrity Protection and Ciphering algorithm(s), eKSI and NONCEMME information elements. Handover Restriction List is sent if it is available in the Target MME; it is described in clause 4.3.5.7. If the MME did not receive the UE Network Capability information from the old SGSN, then the MME will not have received information on the E-UTRAN Integrity Protection and Encryption algorithms that the UE supports. In this case, the MME can assume that the UE supports both EIA1/EEA1 and EIA2/EEA2. NOTE 3: The MME derives K'ASME from CK and IK in the MM context and associates it with eKSI, as described in TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [41] and selects NAS Integrity Protection and Ciphering algorithms(s). eKSI and key derivation parameters are targeted for UE. The MME and UE derive the NAS keys and KeNB from K'ASME. If the MME shares an EPS security association with the UE, the MME may activate this native EPS security context by initiating a NAS SMC procedure after having completed the handover procedure. The MME shall not request the target eNodeB to establish EPS GBR bearers with maximum bitrate set to 0 and those EPS bearers should not be included in the EPS Bearers to be setup list and should be deactivated by the MME. For the remaining EPS Bearer Contexts the MME ignores any Activity Status Indicator within an EPS Bearer Context and requests the target eNodeB to allocate resources for all the remaining EPS Bearer Contexts. The MME shall compute the UE-AMBR, according to clause 4.7.3, based on explicit APN-AMBR values received from the Gn/Gp SGSN. If explicit APN-AMBR values are not received by the MME, a local UE-AMBR shall be included in the 'EPS Bearers be setup list ' IE. The local UE-AMBR is described in clause Annex E. "Data forwarding not possible" indication per bearer shall be included in the 'EPS Bearers to be setup list' if the target MME decides the corresponding bearer will not be subject to data forwarding. NOTE 4: The MME derives the security parameters from the security parameters received from the SGSN. NOTE 5: An MME that supports handovers from pre-Rel-8 3G SGSNs derives from the RNC ID received from old SGSN an eNodeB address. 7. The target eNodeB allocates the requested resources and returns the applicable parameters to the target MME in the message Handover Request Acknowledge (Target to Source Transparent Container, EPS Bearers setup list, EPS Bearers failed to setup list, Cause). The target eNodeB shall ignore it if the number of radio bearers in the Source to Target Transparent container does not comply with the number of bearers requested by the MME and allocate bearers as requested by the MME. The target eNodeB inserts the information provided by the MME (KSI, selected NAS Integrity Protection and Ciphering algorithm(s), NONCEMME) and selected AS integrity and ciphering algorithm(s) into the UTRAN RRC message, which is contained in the Target to Source Transparent Container. 8. If 'Indirect Forwarding' and relocation of Serving GW apply the target MME sends a Create Indirect Data Forwarding Tunnel Request message (IMSI, MME Tunnel Endpoint Identifier for Control Plane, MME Address for Control plane, Target eNodeB Address and TEID(s) for DL user plane) to the Serving GW. The allocation of a new Serving GW by steps 4 and 5 the MME shall consider as a Serving GW change. 9. The Serving GW returns a Create Indirect Data Forwarding Tunnel Response (Cause, Serving GW DL TEID(s)) message to the source MME. If the Serving GW doesn't support data forwarding, an appropriate cause value shall be returned. 10. When resources for the transmission of user data between target RNC and new SGSN have been allocated and the new SGSN is ready for relocation of SRNS, the Forward Relocation Response (Cause, RAN Transparent Container, RANAP Cause, Target-RNC Information) message is sent from the new SGSN to the old SGSN. This message indicates that the target RNC is ready to receive from source SRNC the forwarded downlink PDUs, i.e., the relocation resource allocation procedure is terminated successfully. RAN transparent container and RANAP Cause are information from the target RNC to be forwarded to the source SRNC. The Target RNC Information, one information element for each RAB to be set up, contains the RNC Tunnel Endpoint Identifier and RNC IP address for data forwarding from the source SRNC to the target RNC. The Forward Relocation Response message is applicable only in the case of inter-SGSN SRNS relocation. For each RAB, if the MME has determined no Data forwarding, i.e. the data forwarding from the source RNC to the target eNodeB is not required, the MME indicates the reserved TEID and IP address parameters to the old SGSN in the Target RNC Information. The packets received on that reserved TEID and IP address are discarded. NOTE 6: The new MME acts as the new SGSN, and the target eNodeB as the target SRNC. RANAP Cause indicates the Cause as received from target eNodeB. RAN Transparent Container contains the Target to Source Transparent Container as received from eNodeB. 11. The old SGSN continues the relocation of SRNS by sending a Relocation Command message (Target RNC To Source RNC Transparent Container, RABs To Be Released, RABs Subject To Data Forwarding) to the source SRNC. The old SGSN decides the RABs to be subject for data forwarding based on QoS, and those RABs shall be contained in RABs subject to data forwarding. For each RAB subject to data forwarding, the information element shall contain RAB ID, Transport Layer Address, and Iu Transport Association. These are the same Transport Layer Address and Iu Transport Association that the target RNC had sent to new SGSN in Relocation Request Acknowledge message, and these are used for forwarding of downlink N-PDU from the source SRNC to the target RNC. The source SRNC is now ready to forward downlink user data directly to the target RNC over the Iu interface. This forwarding is performed for downlink user data only. NOTE 7: This step is unmodified compared to pre-Rel-8. The target eNodeB acts as the target RNC, and the new MME acts as the new SGSN. The forwarding of downlink user data from source SRNC may go directly to target eNodeB or via the Serving GW. 12. The source SRNC may, according to the QoS profile, begins the forwarding of data for the RABs to be subject for data forwarding. NOTE 8: The order of steps, starting from step 7 onwards, does not necessarily reflect the order of events. For instance, source RNC may start data forwarding (step 7), send the RRC message to MS (step 8) and forward SRNS Context message to the old SGSN (step 9) almost simultaneously. The data forwarding at SRNS relocation shall be carried out through the Iu interface, meaning that the GTP-PDUs exchanged between the source SRNC and the target RNC are duplicated in the source SRNC and routed at the IP layer towards the target RNC. For each radio bearer which uses lossless PDCP the GTP-PDUs related to transmitted but not yet acknowledged PDCP-PDUs are duplicated and routed at IP layer towards the target RNC together with their related downlink PDCP sequence numbers. The source RNC continues transmitting duplicates of downlink data and receiving uplink data. Before the serving RNC role is not yet taken over by target RNC and when downlink user plane data starts to arrive to target RNC, the target RNC may buffer or discard arriving downlink GTP-PDUs according to the related QoS profile. NOTE 9: This step is unmodified compared to pre-Rel-8. The target eNodeB acts as the target SRNC. The data forwarding may go directly to target eNodeB or alternatively go via the Serving GW if so decided by new MME in the preparation phase. 13. Before sending the RRC message the uplink and downlink data transfer shall be suspended in the source SRNC for RABs, which require delivery order. The RRC message is for example Physical Channel Reconfiguration for RNS to RNS relocation, or Intersystem to UTRAN Handover for BSS to RNS relocation, or Handover from UTRAN Command for BSS relocation, or Handover Command for BSS to BSS relocation. When the source SRNC is ready, the source RNC shall trigger the execution of relocation of SRNS by sending to the MS the RRC message provided in the Target RNC to source RNC transparent container, e.g., a Physical Channel Reconfiguration (UE Information Elements, CN Information Elements) message. UE Information Elements include among others new SRNC identity and S-RNTI. CN Information Elements contain among others Location Area Identification and Routing Area Identification. When the MS has reconfigured itself, it sends an RRC message e.g., a Physical Channel Reconfiguration Complete message to the target SRNC. If the Forward SRNS Context message with the sequence numbers is received, the exchange of packets with the MS may start. If this message is not yet received, the target RNC may start the packet transfer for all RABs, which do not require maintaining the delivery order. NOTE 10: This step is unmodified compared to pre-Rel-8. This text is valid for the RRC message sent from source RNC to the UE. When the UE has got access to target eNodeB it sends the HO to E-UTRAN Complete message. This RRC message received as part of Target to Source Transparent Container, includes information about the selected security algorithms and related key information. Based on this information, the UE selects the same algorithms for the NAS if the KSI value indicates that the MME has no security association with the UE. If the KSI value indicates that the MME has a security association with the UE, but the UE has lost the security context of the E-UTRAN side (error case), the UE will start Attach procedure on the E-UTRAN side 14. There is no RAN context transfer during inter RAT handovers with E-UTRAN. If the source RNC originates any SRNC contexts the MME acknowledges the receipt towards the SGSN and ignores the message content. NOTE 11: This step is unmodified compared to pre-Rel-8. The new MME acts as the new SGSN, and the target eNodeB as the target SRNC. 15. When the UE has successfully accessed the target eNodeB, the target eNodeB informs the target MME by sending the message Handover Notify (TAI+ECGI). The UE shall implicitly derive the EPS bearers for which an E-RAB was not established from the HO from UTRAN Command and deactivate them locally without an explicit NAS message at this step. If Dual Connectivity is activated for the UE, the PSCell ID shall be included in the Handover Notify message. 16. Upon receipt of Handover Notify message, if the SRNS Relocation is an inter SGSN SRNS relocation, the new SGSN signals to the old SGSN the completion of the SRNS relocation procedure by sending a Forward Relocation Complete message. Upon receipt of the Relocation Complete message the new MME starts a timer. NOTE 12: This step is unmodified compared to pre-Rel-8 except that the Handover Notify message is received instead of a Relocation Complete message. The new MME acts as the new SGSN. 17. The target MME will now complete the handover procedure by informing the Serving GW that the target MME is now responsible for all the bearers the UE have established. This is performed in the message Modify Bearer Request (Cause, Tunnel Endpoint Identifier Control Plane, MME Address for Control Plane, eNodeB Address(es) and TEID(s) for User Traffic, RAT type, APN-AMBR, User Location Information, PSCell ID) per PDN connection. If the PDN GW requested UE's location information and/or User CSG information (determined from the UE context), the MME also includes the User Location Information IE and/or User CSG Information IE in this message. If the UE Time Zone has changed, the MME includes the UE Time Zone IE in this message. If the MME has received PSCell ID in step 15, the MME shall include it in this message. The MME releases the non-accepted bearers by triggering the bearer release procedure as specified in clause 5.4.4.2. If the Serving GW receives a DL packet for a non-accepted bearer, the Serving GW drops the DL packet and does not send a Downlink Data Notification to the MME. 18. The Serving GW informs the PDN GW the APN-AMBR and the change of for example the RAT type that e.g. can be used for charging, by sending the message Modify Bearer Request (APN-AMBR, Serving Network, PDN Charging Pause Support Indication) per PDN connection. The S-GW also includes User Location Information IE and/or UE Time Zone IE and/or User CSG Information IE if it is present in step 17. The Serving GW allocates DL TEIDs on S5/S8 even for non-accepted bearers. The PDN GW must acknowledge the request with the message Modify Bearer Response (Default bearer id, APN Restriction, PDN Charging Pause Enabled Indication (if PDN GW has chosen to enable the function)). When the UE moves from Gn/Gp SGSN to the MME, the PDN GW shall send the APN restriction of each bearer context to the Serving GW. 19. The Serving GW acknowledges the user plane switch to the target MME via the message Modify Bearer Response (Cause, Tunnel Endpoint Identifier Control Plane, Serving GW Address for Control Plane, Default bearer id, APN restriction). The Serving GW shall forward the received APN Restriction to the MME. At this stage the user plane path is established for all bearers between the UE, target eNodeB, Serving GW and PDN GW. 20. Upon receiving the Relocation Complete message or, if it is an inter-SGSN SRNS relocation, the Forward Relocation Complete message, the old SGSN sends an Iu Release Command message to the source RNC. When the RNC data-forwarding timer has expired, the source RNC responds with an Iu Release Complete message. NOTE 13: This step is unmodified compared to pre-Rel-8. 21. The UE initiates a Tracking Area Update procedure when one of the conditions listed in clause "Triggers for tracking area update" applies. The target MME knows that an IRAT Handover has been performed for this UE as it received the bearer context(s) by handover messages and therefore the target MME performs only a subset of the TA update procedure, specifically it excludes the context transfer procedures between source SGSN and target MME. The target MME gets the subscribed UE-AMBR value and the subscribed APN-AMBR value from the HSS during the TA update procedure. If the Subscription Data received from the HSS (during the TAU) contains information that is necessary for the E-UTRAN to be aware of (e.g. a restriction in the UE's permission to use NR as a secondary RAT, Unlicensed Spectrum in the form of LAA/LWA/LWIP/NR-U (as specified in clause 4.3.30) or a combination of them), or an existing UE context in the MME indicates that the UE is not permitted to use NR as a secondary RAT, Unlicensed Spectrum or a combination of them, and the MME has not provided this information to the target eNodeB during step 6 (the Handover Request), then the MME sends an updated Handover Restriction List in the Downlink NAS Transport message that it sends to E-UTRAN. 22. The target MME calculates UE-AMBR as defined in clause 4.7.3. If this calculated value is different from the UE-AMBR computed during step 6, or the APN-AMBR mapped from the subscribed MBR is different from the subscribed APN-AMBR, or the mapped subscribed QoS profile (i.e. the subscribed QoS profile mapped according to Annex E) of the default bearer is different from the EPS Subscribed QoS profile received from the HSS, the new MME shall initiate Subscribed QoS Modification procedure as described in clause 5.4.2.2, Figure 5.4.2.2-1. 23. When the timer started in step 16 expires the new MME releases the resources that have been allocated for indirect forwarding. If the SRNS Relocation is inter-SGSN, then the following CAMEL procedure calls shall be performed (see referenced procedures in TS 23.078[ Customised Applications for Mobile network Enhanced Logic (CAMEL) Phase 4; Stage 2 ] [29]) C1) CAMEL_GPRS_PDP_Context_Disconnection, CAMEL_GPRS_Detach and CAMEL_PS_Notification. They are called in the following order: - The CAMEL_GPRS_PDP_Context_Disconnection procedure is called several times: once per PDP context. The procedure returns as result "Continue". - Then the CAMEL_GPRS_Detach procedure is called once. The procedure returns as result "Continue". - Then the CAMEL_PS_Notification procedure is called once. The procedure returns as result "Continue". The new SGSN shall determine the Maximum APN restriction based on the received APN Restriction of each PDP context from the GGSN and then store the new Maximum APN restriction value. If the SRNS Relocation is intra-SGSN, then the above mentioned CAMEL procedures calls shall not be performed. If Routing Area Update occurs, the SGSN shall determine whether Direct Tunnel can be used based on the received GPRS CAMEL Subscription Information. If Direct Tunnel can not be maintained the SGSN shall re-establish RABs and initiate the Update PDP Context procedure to update the IP Address and TEID for Uplink and Downlink data. If Routing Area Update occurs, then the following CAMEL procedure calls shall be performed (see referenced procedures in TS 23.078[ Customised Applications for Mobile network Enhanced Logic (CAMEL) Phase 4; Stage 2 ] [29]): NOTE 14: This CAMEL handling is unmodified compared to pre-Rel-8. NOTE 15: CAMEL procedure calls C2 and C3 were omitted intentionally from this procedure since EPS does not support CAMEL procedure calls. NOTE 16: Handover Reject procedure is performed as defined in clause 5.5.2.2.4. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | D.3.4 |
1,416 | 4.15.6.3d ECS Address Configuration Information Parameters | AF provided ECS Address Configuration Information that an AF may provide to the 5GC is described in Table 4.15.6.3d-1. The AF may associate ECS Address Configuration Information with a group of UE or with any UE. Multiple AF may configure 5GC with AF provided ECS Address Configuration Information. The Subscription provided ECS Address Configuration Information that a SMF may receive is described in Table 4.15.6.3d-2 For non-roaming and LBO cases, the ECS Address Configuration Information is provided to SMF as Session Management Subscription data. The ECS Address Configuration Information is associated with a DNN and S-NSSAI included in the message from UDM. For HR cases, when the HPLMN has the knowledge of EACI in the VPLMN, the ECS Address Configuration Information is provided to H-SMF as Session Management Subscription data. The ECS Address Configuration Information is associated with a DNN, S-NSSAI and PLMN ID included in the message from UDM. The SMF is not expected to understand the internal structure of ECS Address Configuration Information. Table 4.15.6.3d-1: Description of ECS Address Configuration Information provided by the AF Table 4.15.6.3d-2: Description of Subscription provided ECS Address Configuration Information (as sent to the SMF) | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.15.6.3d |
1,417 | – N3C-IndirectPathAddChange | The IE N3C-IndirectPathAddChange indicates the N3C indirect path related configuration used by N3C remote UE. N3C-IndirectPathAddChange information element -- ASN1START -- TAG-N3C-INDIRECTPATHADDCHANGE-START N3C-IndirectPathAddChange-r18 ::= SEQUENCE { n3c-RelayIdentification-r18 SEQUENCE { n3c-CellGlobalId-r18 SEQUENCE { n3c-PLMN-Id-r18 PLMN-Identity, n3c-CellIdentity-r18 CellIdentity }, n3c-C-RNTI-r18 RNTI-Value } OPTIONAL, -- Cond N3CIndirectPathAddChange ... } -- TAG-N3C-INDIRECTPATHADDCHANGE-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
1,418 | 5.2.6.2.2 Nnef_EventExposure_Subscribe operation | Service operation name: Nnef_EventExposure_Subscribe Description: the consumer subscribes to receive an event, or if the event is already defined in NEF, then the subscription is updated. Inputs, Required: (Set of) Event ID(s) as specified in clause 4.15.3.1 or Npcf_PolicyAuthorization_Notify and Naf_EventExposure_Subscribe service operation, Target of Event Reporting (GPSI, SUPI, UE IPv4 address(es), UE IPv6 prefix(es), External Group Identifier, S-NSSAI, Internal Group Identifier, UE addressing information (IP or MAC address), or indication that any UE is targeted), Event Reporting Information defined in Table 4.15.1-1, Notification Target Address (+ Notification Correlation ID), MTC Provider Information. Inputs, Optional: Event Filter, (set of) External Application Identifier(s), Subscription Correlation ID (in the case of modification of the event subscription), Expiry time, list of group member UE(s) whose subscription to event notification(s) are removed or added for a group-based event notification subscription, operation indication (cancellation or addition), DNN, S-NSSAI, Idle Status Indication request (if UE reachability or Availability after DDN failure reporting is requested). Outputs, Required: When the subscription is accepted: Subscription Correlation ID, Expiry time (required if the subscription can be expired based on the operator's policy). Outputs, Optional: First corresponding event report is included, if available (see clause 4.15.1). External Identifier (representing an AF specific UE Identifier). | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.6.2.2 |
1,419 | 7.2.12 Delete Indirect Data Forwarding Tunnel Request | The Delete Indirect Data Forwarding Tunnel Request message is sent on the S4/S11 interface by the SGSN/MME to the SGW to delete the Indirect Forwarding Tunnels in the Source SGW/Target SGW as part of the following procedures: - S1-based handover - UTRAN Iu mode to E-UTRAN Inter RAT handover - GERAN A/Gb mode to E-UTRAN Inter RAT handover - E-UTRAN to UTRAN Iu mode Inter RAT handover - E-UTRAN to GERAN A/Gb mode Inter RAT handover - MME to SGSN combined hard handover and SRNS relocation procedure - SGSN to MME combined hard handover and SRNS relocation procedure - Inter RAT handover Cancel - S1-based handover Cancel - Optimised Active Handover: E-UTRAN Access to CDMA2000 HRPD Access - EPS to 5GS handover using N26 interface - 5GS to EPS handover using N26 interface - N26 based Handover cancel Table 7.2.12-1: Information Element in Delete Indirect Data Forwarding Tunnel Request | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 7.2.12 |
1,420 | 4.3.1.3.3 Number of handover failures related with MRO | This measurement provides the number of outgoing handover related events that fail related with MRO. Handover related events include normal successful handovers and all failure events by which a UE in RRC connected state changes its serving cell without following a normal handover. Different MRO failure cases are found in [12]. The measurement includes separate counters for the number of handover failures classified as “too early”, “too late” and “to wrong cell”. The measurement for the too late handover is split to subcounters indicating the threshold of the serving cell itself was not crossed and the threshold of the neighbour cell was not crossed in UE measurements before handover in case the handover is triggered by more than one threshold of the measurement report triggering events, the subcounters are only needed if more than one threshold of the measurement report triggering events is used and using single or multiple thresholds is vendor specific. CC The measurements of too early handovers, too late handovers and to wrong cell handovers are obtained respectively by accumulating the number of failure events related to handover which are identified by the eNB according to the definitions in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [12]. Besides being added to the measurement of total too late handovers, each too late handover (identified by the eNB according to the definitions in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [12]) is also added to the relevant subcounter indicating the threshold of the serving cell itself configured in the measurement report triggering events (see 36.331 [18]) was not crossed or the threshold of the neighbour cell configured in the measurement report triggering events was not crossed if more than one threshold triggering a measurement report is configured to the UEs for the involved neighbour relation and the following UE measurement results are available for both cells involved in the too late handover - rsrpResult of “measResultLastServCell” and - rsrpResult of the subject neighbour cell in “measResultNeighCells” in a) the “RLF report” IE in the received RRC message “UEInformationResponse” (see 36.331 [18]), in case both cells involved in the too late handover belong to the same eNB, or b) the “UE RLF Report Container” IE in the received X2 message “RLF Indication”, in case the cells involved in the too late handover belong to different eNBs. The uncrossed threshold (of the serving itself and the neighbour) is identified by comparing the UE measurement results above with the configured thresholds (adding the corresponding hysteresis, see 36.331 [18]) of the measurement report triggering events, - if the threshold of the serving cell itself was not crossed, the observed too late handover is then added to the subcounter (HO.OutFail.TooLateOwnNotCrossed) indicating the threshold of the serving cell was not crossed - if the threshold of the neighbor cell itself was not crossed, the observed too late handover is then added to the subcounter (HO.OutFail.TooLateNeighborNotCrossed) indicating the threshold of the neighbour cell was not crossed - if the thresholds of both the serving cell itself and the neighbour cell were not crossed, then this too late handover is added to both subcounters (HO.OutFail.TooLateOwnNotCrossed and HO.OutFail.TooLateNeighborNotCrossed) indicating the threshold of serving cell itself was not crossed and the threshold of the neighbour cell was not crossed - if no threshold was not crossed, then this handover is only added to the measurement of total too late handovers but not to the subcounter indicating the threshold of the serving cell itself was not crossed or the threshold of the neighbour cell was not crossed. If only one threshold triggring the measurement report is configured to the UEs for the involved neighbour relation or the UE measurements above are not available, the observed too late handover is only added to the measurement of total too late handovers but not to the subcounter indicating the threshold of the serving cell itself was not crossed or the threshold of the neighbour cell was not crossed. Each measurement is an integer value. The measurements are named HO.OutFail.TooEarly HO.OutFail.TooLate Which indicates the total number of too late handovers identified by the eNB according to the definitions in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [12]. HO.OutFail.TooLateOwnNotCrossed Which indicates the number of too late handovers for which the threshold of the serving cell itself was not crossed. HO.OutFail.TooLateNeighborNotCrossed Which indicates the number of too late handovers for which the threshold of the neighbor cell was not crossed. HO.OutFail.ToWrongCell Which indicates the number of “handover to wrong cell” cases on the NR (NR AB in Annex A.13) towards the target cell (see 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [12]). It is up to the eNodeB to decide whether or not the HO parameters of this NR are problematic in the “handover to wrong cell” case. HO.OutFail.HwcReestablish Which indicates the number of “handover to wrong cell” cases on the NR (NR AC in Annex A.13) towards the cell with which the UE attempts to re-establish the radio link connection (see 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [12]). It is up to the eNodeB to decide whether or not the HO parameters of this NR are problematic in the “handover to wrong cell” case. EUtranRelation Valid for packet switched traffic EPS | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.3.1.3.3 |
1,421 | A.3.7 Guidelines on use of lists with elements of SEQUENCE type | Where an information element has the form of a list (the SEQUENCE OF construct in ASN.1) with the type of the list elements being a SEQUENCE data type, an information element shall be defined for the list elements even if it would not otherwise be needed. For example, a list of PLMN identities with reservation flags is defined as in the following example: -- /example/ ASN1START PLMN-IdentityInfoList ::= SEQUENCE (SIZE (1..6)) OF PLMN-IdentityInfo PLMN-IdentityInfo ::= SEQUENCE { plmn-Identity PLMN-Identity, cellReservedForOperatorUse ENUMERATED {reserved, notReserved} } -- ASN1STOP rather than as in the following (bad) example, which may cause generated code to contain types with unpredictable names: -- /bad example/ ASN1START PLMN-IdentityList ::= SEQUENCE (SIZE (1..6)) OF SEQUENCE { plmn-Identity PLMN-Identity, cellReservedForOperatorUse ENUMERATED {reserved, notReserved} } -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | A.3.7 |
1,422 | 16.18.5 Interference Detection and Mitigation for Aerial UE Communication | For interference detection, an Aerial UE can be configured with RRM event A3, A4, A5 or AxHy that triggers measurement report when individual (per cell) RSRP values for a configured number of cells fulfil the configured event. Once such condition is met and a measurement report is sent, the list of triggered cells is updated when subsequent cell(s) fulfil the event. However, further measurement reports are not sent while the list of triggered cells remains larger than or equal to the configured number of cells unless reportOnLeave is configured (see TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [12] for details). | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.18.5 |
1,423 | – SL-MeasIdList | The IE SL-MeasIdList concerns a list of SL measurement identities to add or modify for a destination, with for each entry the sl-MeasId, the associated sl-MeasObjectId and the associated sl-ReportConfigId. SL-MeasIdList information element -- ASN1START -- TAG-SL-MEASIDLIST-START SL-MeasIdList-r16 ::= SEQUENCE (SIZE (1..maxNrofSL-MeasId-r16)) OF SL-MeasIdInfo-r16 SL-MeasIdInfo-r16 ::= SEQUENCE { sl-MeasId-r16 SL-MeasId-r16, sl-MeasObjectId-r16 SL-MeasObjectId-r16, sl-ReportConfigId-r16 SL-ReportConfigId-r16, ... } SL-MeasId-r16 ::= INTEGER (1..maxNrofSL-MeasId-r16) -- TAG-SL-MEASIDLIST-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
1,424 | 6.2.9 N3IWF | The functionality of N3IWF in the case of untrusted non-3GPP access includes the following: - Support of IPsec tunnel establishment with the UE: The N3IWF terminates the IKEv2/IPsec protocols with the UE over NWu and relays over N2 the information needed to authenticate the UE and authorize its access to the 5G Core Network. - Termination of N2 and N3 interfaces to 5G Core Network for control - plane and user-plane respectively. - Relaying uplink and downlink control-plane NAS (N1) signalling between the UE and AMF. - Handling of N2 signalling from SMF (relayed by AMF) related to PDU Sessions and QoS. - Establishment of IPsec Security Association (IPsec SA) to support PDU Session traffic. - Relaying uplink and downlink user-plane packets between the UE and UPF. This involves: - De-capsulation/ encapsulation of packets for IPSec and N3 tunnelling. - Enforcing QoS corresponding to N3 packet marking (e.g. DSCP), taking into account QoS requirements associated to such marking received over N2. QoS includes 5QI, the Priority Level (if explicitly signalled) and optionally, the ARP priority level. NOTE: Based on operator policy and/or regional/national regulations, the N3IWF can apply a different DSCP value to the outer ESP tunnel packet than the DSCP value of the inner IP packet. - Packet marking, e.g. setting the DSCP value based on the Establishment cause on N2, and based on 5QI, the Priority Level (if explicitly signalled) and optionally, the ARP priority level on N3. - Local mobility anchor within untrusted non-3GPP access networks using MOBIKE per IETF RFC 4555 [57]. - Supporting AMF selection. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 6.2.9 |
1,425 | 5.2.5 Subscriber privacy | The UE shall support 5G-GUTI. The SUPI should not be transferred in clear text over NG-RAN except routing information, e.g. Mobile Country Code (MCC) and Mobile Network Code (MNC). The Home Network Public Key shall be stored in the USIM. The protection scheme identifier shall be stored in the USIM. The Home Network Public Key Identifier shall be stored in the USIM. The SUCI calculation indication, either USIM or ME calculating the SUCI, shall be stored in USIM. The ME shall support the null-scheme.If the home network has not provisioned the Home Network Public Key in USIM, the SUPI protection in initial registration procedure is not provided. In this case, the null-scheme shall be used by the ME. Based on home operator's decision, indicated by the USIM, the calculation of the SUCI shall be performed either by the USIM or by the ME. NOTE 1: If the SUCI calculation indication is not present, the calculation is in the ME. In case of an unauthenticated emergency call, privacy protection for SUPI is not required. Provisioning, and updating the Home Network Public Key, Home Network Public Key Identifier, protection scheme identifier, Routing Indicator, and SUCI calculation indication in the USIM shall be in the control of the home network operator. NOTE 2: The provisioning and updating of the Home Network Public Key, Home Network Public Key Identifier, protection scheme identifier, and SUCI calculation indication is out of the scope of the present document. It can be implemented using, e.g. the Over the Air (OTA) mechanism. Routing Indicator can be updated, e.g., by OTA or as defined in clause 6.15. Subscriber privacy enablement shall be under the control of the home network of the subscriber. The UE shall only send the PEI in the NAS protocol after NAS security context is established, unless during emergency registration when no NAS security context can be established. The Routing Indicator shall be stored in the USIM. If the Routing Indicator is not present in the USIM, the ME shall set it to a default value as defined in TS 23.003[ Numbering, addressing and identification ] [19]. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 5.2.5 |
1,426 | Resume Notification | The Resume Notification message should be sent on the S11 interface by the MME to the SGW and forwarded on the S5/S8 interface by the SGW to the PGW as part of the resume procedure returning back to E-UTRAN in the case of CS fallback or SRVCC. The Resume Notification message should also be sent on the S4 interface by the SGSN to the SGW and forwarded on the S5/S8 interface by the SGW to the PGW as part of the resume procedure returning from SRVCC to HSPA if there is no Modify Bearer Request message sent to the SGW and PGW as specified in 3GPP TS 23.216[ Single Radio Voice Call Continuity (SRVCC); Stage 2 ] [43]. The SGW may also send a Resume Notification message to the PGW on the S5/S8 interface upon receipt from the MME/S4-SGSN of a (non-empty) Modify Bearer Request used as an implicit resume of the suspended bearers in the SGW and in the PGW (see 3GPP TS 23.216[ Single Radio Voice Call Continuity (SRVCC); Stage 2 ] [43] clauses 6.2.2.1 and 6.3.2.1, 3GPP TS 23.272[ Circuit Switched (CS) fallback in Evolved Packet System (EPS); Stage 2 ] [21] clauses 6.3, 6.5 and 7.4) if the conditions of presence of the IEs in the Modify Bearer Request specified in table 7.2.7-1 do not require any IE to be sent over S5/S8 to the PGW. NOTE: This is an alternative to sending over S5/S8 a Modify Bearer Request used as an implicit resume with zero IE(s), see clause 7.2.7. After receiving a Resume Notification message or a Modify Bearer Request used as an implicit resume of the suspended bearers, the SGW/PGW clears suspended status for all the non-GBR bearers. The PGW shall forward packets it receives for the UE. If the suspended bearers are of the type S4-U GTP-U, the SGW shall forward over the S4-U interface, packets it receives for the UE, upon receipt of Resume Notification. Table 7.4.3-1 specifies the presence requirements and conditions of the IEs in the message. Table -1: Information Element in Resume Notification | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | Resume |
1,427 | 2.12 Structure of the Truncated 5G-S-Temporary Mobile Subscriber Identity (Truncated 5G-S-TMSI) | The Truncated 5G-S-TMSI is a 40 bit UE identifier constructed from the 5G-S-TMSI. It is used in RRC Connection Re-Establishment for the control plane for NB-IoT as described in 3GPP TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [91]. The Truncated 5G-S-TMSI shall be constructed from the Truncated AMF set ID, the Truncated AMF Pointer and the Truncated 5G-TMSI: <Truncated 5G-S-TMSI> = <Truncated AMF set ID><Truncated AMF Pointer><Truncated 5G-TMSI> Truncated AMF set ID is n least significant bits of AMF Set ID, where n is no greater than 10 bits. Truncated AMF Pointer is m least significant bits of AMF Pointer, where m is no greater than 6 bits. Truncated 5G-TMSI is (40-n-m) least significant bits of 5G-TMSI. The values n and m are configurable based on network deployment. The value n+m shall be larger or equal to 8 bits. NOTE: Depending on network deployment it is up to operator configuration to ensure that Truncated AMF Set ID and Truncated AMF Pointer identify the AMF uniquely, and that Truncated 5G-TMSI identifies the UE uniquely within the serving AMF. The NG-RAN and AMF are configured with the values n and m respectively, and NG-RAN is configured with how to recreate AMF Set ID from Truncated AMF Set ID, AMF Pointer from Truncated AMF Pointer, and 5G-TMSI from Truncated 5G-TMSI. The configuration of these parameters are specific to each PLMN. The AMF configures the UE with the Truncated 5G-S-TMSI Configuration that provides the sizes of the components of the Truncated 5G-S-TMSI as described in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [125] during the Registration and UE Configuration Update procedures. For Network Sharing, the sharing NG-RAN is configured with the respective values n and m that are specific to each PLMN, and AMF is configured with the same values n and m as ones configured on NG-RAN per PLMN. The AMF configures the UE with the corresponding values n and m according to the PLMN which the UE accesses to during the Registration procedure. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 2.12 |
1,428 | 5.5.1.2.3 5GMM common procedure initiation | The network may initiate 5GMM common procedures, e.g. the identification, authentication and security procedures during the registration procedure, depending on the information received in the REGISTRATION REQUEST message. If two NAS security mode control procedures are needed to signal an entire unciphered REGISTRATION REQUEST message followed by signalling of selected EPS NAS security algorithms, both NAS security mode control procedures should be initiated as part of 5GMM common procedures of the ongoing registration procedure (see subclause 5.4.2.4). During a registration procedure with 5GS registration type IE set to "emergency registration", if the AMF is configured to support emergency registration for unauthenticated SUCIs, the AMF may choose to skip the authentication procedure even if no 5G NAS security context is available and proceed directly to the execution of the security mode control procedure. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.5.1.2.3 |
1,429 | 5.4.7.2.2 Network slice-specific EAP message reliable transport procedure accepted by the UE | When the upper layers provide an EAP-response message associated with the HPLMN S-NSSAI or the SNPN S-NSSAI, the UE shall create a NETWORK SLICE-SPECIFIC AUTHENTICATION COMPLETE message. The UE shall set the EAP message IE of the NETWORK SLICE-SPECIFIC AUTHENTICATION COMPLETE message to the EAP-response message. The UE shall set the S-NSSAI IE of the NETWORK SLICE-SPECIFIC AUTHENTICATION COMPLETE message to the HPLMN S-NSSAI or the SNPN S-NSSAI associated with the EAP-response message. The UE shall send the NETWORK SLICE-SPECIFIC AUTHENTICATION COMPLETE message. Apart from this action, the network slice-specific authentication and authorization procedure is transparent to the 5GMM layer of the UE. Upon receipt of a NETWORK SLICE-SPECIFIC AUTHENTICATION COMPLETE message, the AMF shall stop timer T3575 and: a) pass the EAP-response message received in the EAP message IE of the NETWORK SLICE-SPECIFIC AUTHENTICATION COMPLETE message associated with the HPLMN S-NSSAI or the SNPN S-NSSAI in the S-NSSAI IE to the upper layers; or b) provide the EAP-response message received in the EAP message IE of the NETWORK SLICE-SPECIFIC AUTHENTICATION COMPLETE message associated with the HPLMN S-NSSAI or the SNPN S-NSSAI in the S-NSSAI IE to the AAA-S via the NSSAAF. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.4.7.2.2 |
1,430 | 7.7.1A Minimum requirements for CA | For inter-band carrier aggregation with one component carrier per operating band and the uplink assigned to one E-UTRA band the spurious response requirements are defined with the uplink active on the band(s) other than the band whose downlink is being tested. The throughput measured in each downlink with Finterferer in Table 7.6.2.1A-0 and Table 7.6.2.1A-0a at spurious response frequencies shall be ≥ 95% of the maximum throughput of the reference measurement channels as specified in Annexes A.2.2, A.2.3 and A.3.2 (with one sided dynamic OCNG Pattern OP.1 FDD/TDD for the DL-signal as described in Annex A.5.1.1/A.5.2.1) with parameters specified in Tables 7.7.1-1 and 7.7.1-2. The UE shall meet these requirements for each component carrier while all downlink carriers are active. For inter-band carrier aggregation with one component carrier per operating band and the uplink active in two E-UTRA bands, the spurious response requirements applicable specified above shall be met with the transmitter power for the uplink set to 7 dB below PCMAX_L,c for each serving cell c. For E-UTRA CA configurations including an operating band without uplink band or an operating band with an unpaired DL part (as noted in Table 5.5-1), the requirements for all downlinks shall be met with the single uplink carrier active in each band capable of UL operation. For E-UTRA CA configurations listed in Table 7.3.1A-0a under conditions for which reference sensitivity for the operating band being tested is N/A, the spurious response requirements of subclause 7.7.1A do not apply. For intra-band contiguous carrier aggregation the downlink SCC(s) shall be configured at nominal channel spacing to the PCC. For FDD, the PCC shall be configured closest to the uplink band. All downlink carriers shall be active throughout the test. The uplink output power shall be set as specified in Table 7.7.1A-1 with the uplink configuration set according to Table 7.-1 for the applicable carrier aggregation configuration. For UE(s) supporting one uplink carrier, the uplink configuration of the PCC shall be in accordance with Table 7.3.1-2. The throughput of each carrier shall be ≥ 95% of the maximum throughput of the reference measurement channels as specified in Annexes , A.2.3 and A.3.2 (with one sided dynamic OCNG Pattern OP.1 FDD/TDD for the DL-signal as described in Annex /A.5.2.1) with parameters specified in Tables 7.7.1A-1 and 7.7.1A-2. For operating bands with an unpaired DL part (as noted in Table 5.5-1), the requirements also apply for an SCC assigned in the unpaired part with parameters specified in Tables 7.7.1A-1 and 7.7.1A-2 For intra-band non-contiguous carrier aggregation with one uplink carrier and two or more downlink sub-blocks, the spurious response requirements are defined with the uplink configuration in accordance with Table 7.3.1A-3. For this uplink configuration, the UE shall meet the requirements for each sub-block as specified in subclauses 7.7.1 and 7.7.1A for one component carrier and two component carriers per sub-block, respectively. The requirements apply with all downlink carriers active. For intra-band non-contiguous carrier aggregation with two uplink carriers and two or more downlink carriers, the spurious response requirements applicable specified above shall be met with the transmitter powers for the uplinks set to PCMAX_L,c – 7 dBm. Table 7.7.1A-1: Spurious response parameters Table 7.7.1A-2: Spurious response For combinations of intra-band and inter-band carrier aggregation and one uplink carrier assigned to one E-UTRA band, the requirement is defined with the uplink active in a band other than that supporting the downlink(s) under test. The uplink configuration shall be in accordance with Table 7.3.1A-3 when the uplink is active in the band supporting two or more non-contiguous component carriers, Table 7.3.1A-1 when the uplink is active in a band supporting two contiguous component carriers and in accordance with Table 7.3.1-2 when the uplink is active in a band supporting one carrier per band. The downlink PCC shall be configured closer to the uplink operating band than the downlink SCC(s) when the uplink is active in band(s) supporting contiguous aggregation. For the two or more non-contiguous component carriers within the same band, Pwanted in Table 7.6.2.1A-0 is set using RIBNC = 0 dB for all sub-block gaps (Table 7.3.1A-3) while a band supporting contiguously aggregated carriers the out-of-band blocking parameters in Table 7.7.1-1 are replaced by those specified in Table 7.7.1A-1. For each downlink the UE shall meet the spurious-response requirements applicable for inter-band carrier aggregation with one component carrier per operating band. All downlink carriers shall be active throughout the tests and the requirements for the downlinks shall be met with the single uplink carrier active in each band capable of UL operation. | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 7.7.1A |
1,431 | – SL-PosPreconfigurationNR | The IE SL-PosPreconfigurationNR includes the sidelink pre-configured parameters used for NR sidelink positioning. Need codes or conditions specified for subfields in SL-PosPreconfigurationNR do not apply. SL-PosPreconfigurationNR information elements -- ASN1START -- TAG-SL-POSPRECONFIGURATIONNR-START SL-PosPreconfigurationNR-r18 ::= SEQUENCE { sl-PosPreconfigFreqInfoList-r18 SEQUENCE (SIZE (1..maxNrofFreqSL-r16)) OF SL-FreqConfigCommon-r16 OPTIONAL, ... } -- TAG-SL-POSPRECONFIGURATIONNR-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
1,432 | 4.5.1.2 Abnormal cases | Mobile station side: a) RR connection failure without "Extended Wait Time" received from lower layers or IMSI deactivation If an RR connection failure occurs, except in the following implementation option case a.1, or the IMSI is deactivated during the establishment of an MM connection, the MM connection establishment is aborted, timers T3230 is stopped, and an indication is given to the CM entity that requested the MM connection establishment. This shall be treated as a rejection for establishment of the new MM connection, and the MM sublayer shall release all active MM connections. a.1) RR connection failure in Iu mode (i.e. RRC connection release) with, for example, cause "Normal", "User inactivity" or "Directed signalling connection re-establishment" (see 3GPP TS 25.331[ None ] [23c] and 3GPP TS 44.118[ None ] [111]) The MM connection establishment procedure shall be initiated again, if the following conditions apply: i) The original MM connection establishment was initiated over an existing RRC connection; and ii) No SECURITY MODE COMMAND message and no Non-Access Stratum (NAS) messages relating to the CS signalling connection (e.g. CS authentication procedures, see subclause 4.3.2), were received after the CM SERVICE REQUEST message was transmitted. NOTE 1: The RRC connection release cause that triggers the re-initiation of the MM connection establishment procedure is implementation specific. b) T3230 expiry If T3230 expires (i.e. no response is given but a RR connection is available) the MM connection establishment is aborted and the requesting CM sublayer is informed. If no other MM connection exists then the mobile station shall proceed as described in subclause 4.5.3.1 for release of the RR connection. Otherwise the mobile station shall return to the MM sublayer state where the request of an MM connection was received, i.e. to MM sublayer state MM connection active. Other ongoing MM connections (if any) shall not be affected. c) Reject cause values #95, #96, #97, #99, #100, #111 received The same actions as on timer expiry shall be taken by the mobile station. d) Random access failure or RR connection establishment failure without "Extended Wait Time" received from lower layers If the mobile station detects a random access failure or RR connection establishment failure during the establishment of an MM connection, it aborts the MM connection establishment and gives an indication to the CM entity that requested the MM connection establishment. NOTE 2: Further actions of the mobile station depend on the RR procedures and MM specific procedures during which the abnormal situation has occurred and are described together with those procedures. e) Access barred because of access class control or EAB The MM connection establishment shall not be initiated. The MS stays in the current serving cell and applies normal cell reselection process. The MM connection establishment may be initiated by CM layer if it is still necessary, i.e. when access is granted or because of a cell change. f) Indication that a CS fallback to GERAN or UTRAN has failed If EMM indicates that the CS fallback to GERAN or UTRAN failed, the MM sublayer shall abort the MM connection establishment and inform the requesting CM sublayer. g) "Extended wait time" for CS domain from the lower layers The MS shall abort the MM connection establishment and stop timer T3230 if still running. If the CM SERVICE REQUEST message contained the low priority indicator set to "MS is configured for NAS signalling low priority", the MS shall start timer T3246 with the "Extended wait time" value. In other cases the MS shall ignore the "Extended wait time". The MM connection establishment is started, if still necessary, when timer T3246 expires or is stopped. h) Timer T3246 is running The MM connection establishment shall not be initiated unless the MS is establishing an emergency call or the MS is an MS configured to use AC11 – 15 in selected PLMN. The MS stays in the current serving cell and applies normal cell reselection process. The MM connection establishment is started, if still necessary, when timer T3246 expires or is stopped. Network side: a) RR connection failure The actions to be taken upon RR connection failure within a MM common procedure are described together with that procedure. A RR connection failure occurring outside such MM common procedures, shall trigger the release of all active MM connections if any. b) Invalid message or message content Upon reception of an invalid initial message or a CM SERVICE REQUEST message with invalid content, a CM SERVICE REJECT message shall be returned with one of the following appropriate Reject cause indications: # 95: Semantically incorrect message # 96: Mandatory information element error # 97: Message type non-existent or not implemented # 99: Information element non-existent or not implemented # 100: Conditional IE error # 111: Protocol error, unspecified When the CM SERVICE REJECT message has been sent, the network may start RR connection release if no other MM connections exist or if the abnormal condition also has influence on the other MM connections. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.5.1.2 |
1,433 | 6.2.7 UDM | The Unified Data Management (UDM) includes support for the following functionality: - Generation of 3GPP AKA Authentication Credentials. - User Identification Handling (e.g. storage and management of SUPI for each subscriber in the 5G system). - Support of de-concealment of privacy-protected subscription identifier (SUCI). - Access authorization based on subscription data (e.g. roaming restrictions). - UE's Serving NF Registration Management (e.g. storing serving AMF for UE, storing serving SMF for UE's PDU Session). - Support to service/session continuity e.g. by keeping SMF/DNN assignment of ongoing sessions. - MT-SMS delivery support. - Lawful Intercept Functionality (especially in outbound roaming case where UDM is the only point of contact for LI). - Subscription management. - SMS management. - 5G-VN group management handling. - Support of external parameter provisioning (Expected UE Behaviour parameters or Network Configuration parameters). - Support for the Disaster Roaming as described in clause 5.40. - Support for the control of time synchronization service based on subscription data as described in clause 5.27.1.11. To provide this functionality, the UDM uses subscription data (including authentication data) that may be stored in UDR, in which case a UDM implements the application logic and does not require an internal user data storage and then several different UDMs may serve the same user in different transactions. NOTE 1: The interaction between UDM and HSS, when they are deployed as separate network functions, is defined in TS 23.632[ User data interworking, coexistence and migration; Stage 2 ] [102] and TS 29.563[ 5G System; Home Subscriber Server (HSS) services for interworking with Unified Data Management (UDM); Stage 3 ] [103] or it is implementation specific. NOTE 2: The UDM is located in the HPLMN of the subscribers it serves, and access the information of the UDR located in the same PLMN. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 6.2.7 |
1,434 | 5.1.3 Confidentiality | The following security features are provided with respect to confidentiality of data on the network access link: - cipher algorithm agreement: the property that the MS and the SN can securely negotiate the algorithm that they shall use subsequently; - cipher key agreement: the property that the MS and the SN agree on a cipher key that they may use subsequently; - confidentiality of user data: the property that user data cannot be overheard on the radio access interface; - confidentiality of signalling data: the property that signalling data cannot be overheard on the radio access interface; Cipher key agreement is realised in the course of the execution of the mechanism for authentication and key agreement (see 6.3). Cipher algorithm agreement is realised by means of a mechanism for security mode negotiation between the user and the network (see 6.4.5). This mechanism also enables the selected ciphering algorithm and the agreed cipher key to be applied in the way described in 6.6. | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | 5.1.3 |
1,435 | 6.14.2.1 Procedure for steering of UE in VPLMN during registration | The security procedure for the case where the UE registers with VPLMN AMF is described below in figure 6.14.2.1-1: Figure 6.14.2.1-1: Procedure for providing list of preferred PLMN/access technology combinations during registration in VPLMN 1) The UE initiates registration by sending Registration Request message to the VPLMN AMF. 2-3) The VPLMN AMF executes the registration procedure as defined in sub-clause 4.2.2.2.2 of 3GPP TS 23.502[ Procedures for the 5G System (5GS) ] [8]. As part of the registration procedure, the VPLMN AMF executes primary authentication of the UE and then initiates the NAS SMC procedure, after the authentication is successful. 4-5) The VPLMN AMF invokes the Nudm_UECM_Registration message to the UDM and registers access with the UDM as per step 14a in sub-clause 4.2.2.2.2 of 3GPP TS 23.502[ Procedures for the 5G System (5GS) ] [8]. 6) The VPLMN AMF invokes Nudm_SDM_Get service operation message to the UDM to get amongst other information the Access and Mobility Subscription data for the UE (see step 14b in sub-clause 4.2.2.2.2 of 3GPP TS 23.502[ Procedures for the 5G System (5GS) ] [8]). 7) The UDM decides to send the Steering of Roaming Information, and obtains a list of preferred PLMN/access technology combinations and optional additional SoR information (e.g. SOR-CMCI and the "Store the SOR-CMCI in the ME" indicator), or a secured packet list as described in TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [53]. NOTE 1: Additional SoR information (e.g. SOR-CMCI and the "Store the SOR-CMCI in the ME" indicator) can only be added when the AMF supports SoR transparent container. If the UDM determines that the UE is configured to not expect to receive Steering of Roaming Information at initial registration and if the UDM determines that no change of the "Operator Controlled PLMN Selector with Access Technology" list stored in the UE is needed, then the UDM may not piggyback Steering of Roaming Information at all in the Nudm_SDM_Get response and hence the following steps are omitted. 8-9) The UDM shall invoke Nausf_SoRProtection service operation message to the AUSF to get SoR-MAC-IAUSF and CounterSoR as specified in sub-clause 14.1.3 of this document. The UDM shall select the AUSF that holds the latest KAUSF of the UE. If the HPLMN decides that the UE is to acknowledge the successful security check of the received Steering of Roaming Information, then the UDM shall set accordingly the ACK Indication included in the Nausf_SoRProtection service operation message to signal that it also needs the expected SoR-XMAC-IUE, as specified in sub-clause 14.1.3 of this document. NOTE 2: At reception of Nausf_SoRProtection_Protect request from the UDM, if the SoR header is not included in the request, the AUSF constructs the SOR header, as described in clause 9.11.3.51 of TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [35], based on the information received from the UDM, i.e. ACK Indication and list of preferred PLMN/access technology combinations or secured packet (if provided); otherwise, if the SoR header is contained in the request, the AUSF uses the received SoR header in the calculation of SoR-MAC-IAUSF.. The details of the CounterSoR are specified in sub-clause 6.14.2.3 of this document. The inclusion of the Steering List and the SoR header in the calculation of SoR-MAC-IAUSF allows the UE to verify that the received Steering of Roaming Information is not tampered with or removed by the VPLMN. The expected SoR-XMAC-IUE allows the UDM to verify that the UE received the Steering of Roaming Information. 10) The UDM responds to the Nudm_SDM_Get service operation to the VPLMN AMF, which shall include the SoR transparent container as specified in clause 6.1.6.3.2 of TS 29.503[ 5G System; Unified Data Management Services; Stage 3 ] [93] if the VPLMN AMF support SoR transparent container, or shall include individual IEs comprising the ACK Indication, the list of preferred PLMN/access technology combinations or secured packet (if provided), SoR-MAC-IAUSF and CounterSoR within the Access and Mobility Subscription data. If the UDM requests an acknowledgement, it shall temporarily store the expected SoR-XMAC-IUE. 11) If the SoR transparent container is received from the UDM, the VPLMN AMF shall include the received SoR transparent container in the Registration Accept message and send it to the UE. If the individual IEs are received from the UDM, the VPLMN AMF shall construct the SOR header based on the ACK Indication and the list of preferred PLMN/access technology combinations or secured packet (if provided) received from the UDM and include it in the SOR transparent container as specified in clause 9.11.3.51 of TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [35]. The vPLMN shall also include SoR-MAC-IAUSFand CounterSoR(both also received from the UDM) in the constructed SoR transparent container, and convey the constructed SoR transparent container to the UE in the Registration Accept message. 12) On receiving the Registration Accept message with the SoR transparent container from the AMF the UE shall calculate the SoR-MAC-IAUSF in the same way as the AUSF (as specified in Annex A.17) on the SoR transparent container, including the CounterSoR and the SoR header, and verifies whether it matches the SoR-MAC-IAUSF value received in the Registration Accept message. Based on the SoR-MAC-IAUSF verification outcome, the behaviour of the UE is specified in TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [53]. 13) If the UDM has requested an acknowledgement from the UE and the UE verified that the SoR transparent container received in step 12 has been provided by the HPLMN, then the UE shall send the Registration Complete message to the serving AMF. The UE shall generate the SoR-MAC-IUE as specified in Annex A.18 and includes the generated SoR-MAC-IUE in a SOR transparent container in the Registration Complete message. 14) The AMF sends a Nudm_SDM_Info request message to the UDM. If a transparent container with the SoR-MAC-IUE was received in the Registration Complete message, then if the AMF supports SoR transparent container, the AMF shall include the received SoR transparent container in SoR transparent container in the Nudm_SDM_Info request message, otherwise, the AMF shall include the SoR-MAC-IUE in the received SoR transparent container in the Nudm_SDM_Info request message. 15) If the HPLMN indicated that the UE is to acknowledge the successful security check of the received Steering of Roaming Information in step 10, then the UDM shall compare the received SoR-MAC-IUE with the expected SoR-XMAC-IUE that the UDM stored temporarily in step 10. If the UDM supports Home triggered authentication (see clause 6.1.5), the UDM based on its local policy may decide to trigger a primary authentication to refresh the SoR counter based on the value of counter received in step 9. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.14.2.1 |
1,436 | D.6.7 UE policy network classmark | The purpose of the UE policy network classmark information element is to provide the UE with information about the policy aspects of the network. The UE policy network classmark information element is coded as shown in figure D.6.7.1 and table D.6.7.1. The UE policy network classmark is a type 4 information element with a minimum length of 3 octets and a maximum length of 5 octets. Figure D.6.7.1: UE policy network classmark information element Table D.6.7.1: UE policy network classmark information element | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | D.6.7 |
1,437 | 8.2.3.1.1 Minimum Requirement for FDD PCell | For TDD FDD CA with FDD PCell and 2DL CCs, the requirements are specified in Table 8.2.3.1.1-4 based on single carrier requirement specified in Table 8.2.3.1.1-2 and Table 8.2.3.1.1-3, with the addition of the parameters in Table 8.2.3.1.1-1 and the downlink physical channel setup according to Annex C.3.2. For TDD FDD CA with FDD PCell and 3DL CCs, the requirements are specified in Table 8.2.3.1.1-5 based on single carrier requirement specified in Table 8.2.3.1.1-2 and Table 8.2.3.1.1-3, with the addition of the parameters in Table 8.2.3.1.1-1 and the downlink physical channel setup according to Annex C.3.2. For TDD FDD CA with FDD PCell and 4DL CCs, the requirements are specified in Table 8.2.3.1.1-6 based on single carrier requirement specified in Table 8.2.3.1.1-2 and Table 8.2.3.1.1-3, with the addition of the parameters in Table 8.2.3.1.1-1 and the downlink physical channel setup according to Annex C.3.2. For TDD FDD CA with FDD PCell and 5DL CCs, the requirements are specified in Table 8.2.3.1.1-7 based on single carrier requirement specified in Table 8.2.3.1.1-2 and Table 8.2.3.1.1-3, with the addition of the parameters in Table 8.2.3.1.1-1 and the downlink physical channel setup according to Annex C.3.2. For TDD FDD CA with FDD PCell and 6DL CCs, the requirements are specified in Table 8.2.3.1.1-8 based on single carrier requirement specified in Table 8.2.3.1.1-2 and Table 8.2.3.1.1-3, with the addition of the parameters in Table 8.2.3.1.1-1 and the downlink physical channel setup according to Annex C.3.2. For TDD FDD CA with FDD PCell and 7DL CCs, the requirements are specified in Table 8.2.3.1.1-9 based on single carrier requirement specified in Table 8.2.3.1.1-2 and Table 8.2.3.1.1-3, with the addition of the parameters in Table 8.2.3.1.1-1 and the downlink physical channel setup according to Annex C.3.2. The test coverage for different number of component carriers is defined in 8.1.2.4. Table 8.2.3.1.1-1: Test Parameters for CA Table 8.2.3.1.1-2: Single carrier performance with different bandwidths for multiple CA configurations for FDD PCell and SCell (FRC) Table 8.2.3.1.1-3: Single carrier performance with different bandwidths for multiple CA configurations for TDD SCell (FRC) Table 8.2.3.1.1-4: Minimum performance for multiple CA configurations with 2DL CCs (FRC) Table 8.2.3.1.1-5: Minimum performance for multiple CA configurations with 3DL CCs (FRC) Table 8.2.3.1.1-6: Minimum performance for multiple CA configurations with 4DL CCs (FRC) Table 8.2.3.1.1-7: Minimum performance for multiple CA configurations with 5DL CCs (FRC) Table 8.2.3.1.1-8: Minimum performance for multiple CA configurations with 6DL CCs (FRC) Table 8.2.3.1.1-9: Minimum performance for multiple CA configurations with 7DL CCs (FRC) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.2.3.1.1 |
1,438 | – SL-IndirectPathAddChange | The IE SL-IndirectPathAddChange specifies the configuration information of SL indirect path for SL indirect path addition/change in MP. SL-IndirectPathAddChange information element -- ASN1START -- TAG-SL-INDIRECTPATHADDCHANGE-START SL-IndirectPathAddChange-r18 ::= SEQUENCE { sl-IndirectPathRelayUE-Identity-r18 SL-SourceIdentity-r17, sl-IndirectPathCellIdentity-r18 CellIdentity, t421-r18 ENUMERATED {ms50, ms100, ms150, ms200, ms500, ms1000, ms2000, ms10000}, ... } -- TAG-SL-INDIRECTPATHADDCHANGE-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
1,439 | 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 clause 5.10.3. Figure 5.4.4.2-1: MME initiated Dedicated Bearer Deactivation NOTE 1: For a PMIP-based S5/S8, procedure steps (A) and steps (B) are defined in TS 23.402[ Architecture enhancements for non-3GPP accesses ] [2]. Steps 3, 4, 5 and 9 concern GTP based S5/S8 0. Radio bearers for the UE in the ECM-CONNECTED state may be released due to local reasons (e.g. abnormal resource limitation or radio conditions do not allow the eNodeB to maintain all the allocated GBR bearers: it is not expected that non-GBR bearers are released by the eNodeB unless caused by error situations). The UE deletes the bearer contexts related to the released radio bearers. 1. When the eNodeB releases radio bearers in step 0, it sends an indication of bearer release to the MME. This indication may be e.g. the Bearer Release Request (EPS Bearer Identity) message to the MME, or alternatively Initial Context Setup Complete, Handover Request Ack and UE Context Response, Path Switch Request may also indicate the release of a bearer. The eNodeB includes the ECGI and TAI in the indication sent to the MME. The eNodeB also includes the PSCell ID if Dual Connectivity is active for the UE in the RAN. If the PLMN has configured secondary RAT reporting and the eNodeB has Secondary RAT usage data to report, the Secondary RAT usage data is included. 2. The MME sends the Delete Bearer Command (EPS Bearer Identity, User Location Information, UE Time Zone, RAN/NAS Release Cause if available, Secondary RAT usage data, PSCell ID) message per PDN connection to the Serving GW to deactivate the selected dedicated bearer. RAN/NAS Release Cause indicates the RAN release cause and/or the NAS release cause. RAN/NAS Release Cause is only sent by the MME to the PDN GW if this is permitted according to MME operator's policy. If the MME received Secondary RAT usage data in step 1, the MME shall include it in this message. If MME received PSCell ID in step 1, the MME shall include it in this message. 3. The Serving GW sends the Delete Bearer Command (EPS Bearer Identity, User Location Information, UE Time Zone, RAN/NAS Release Cause, Secondary RAT usage data) message per PDN connection to the PDN GW. The Serving GW includes the Secondary RAT usage data it in this message if it was received in the previous message and if PGW secondary RAT usage data reporting is active. 4. If PCC infrastructure is deployed, the PDN GW informs the PCRF about the loss of resources by means of a PCEF-initiated IP-CAN Session Modification procedure as defined in TS 23.203[ Policy and charging control architecture ] [6] and provides the User Location Information, UE Time Zone and RAN/NAS Release cause (if available) received in the Delete Bearer Command from the S-GW if requested by the PCRF as defined in TS 23.203[ Policy and charging control architecture ] [6]. The PCRF sends an updated PCC decision to the PDN GW. NOTE 2: User Location Information and UE Time Zone might not be available if the MME or the Serving GW are of a previous release and did not provide this information. 5. The PDN GW sends a Delete Bearer Request (EPS Bearer Identity) message to the Serving GW. 6. The Serving GW sends the Delete Bearer Request (EPS Bearer Identity) message to the MME. 7. Steps between steps 4 and 7, as described in clause 5.4.4.1, are invoked. This is omitted if the bearer deactivation was triggered by the eNodeB in step 0 and step 1. This is also omitted if the MME initiated bearer release due to failed bearer set up during handover, the UE and the MME deactivate the failed contexts locally without peer-to peer ESM signalling. 8. The MME deletes the bearer contexts 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 (ECGI), Secondary RAT usage data) message. The MME includes the Secondary RAT usage data if it received this in step 7 from the eNodeB. 9. The Serving GW deletes the bearer context related to the deactivated EPS bearer and acknowledges the bearer deactivation to the PDN GW by sending a Delete Bearer Response (EPS Bearer Identity, Secondary RAT usage data) message. The Serving GW includes the Secondary RAT usage data if it was received in step 8 and if PGW secondary RAT usage data reporting is active. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.4.4.2 |
1,440 | 19.7.3 External Group Identifier | An External Group Identifier identifies a group made up of one or more subscriptions associated to a group of IMSIs. The External Group Identifier shall have the form groupname@realm as specified in clause 2.1 of IETF RFC 4282 [53]. The groupname part format of the External Group Identifier shall contain a Local Identifier as specified in 3GPP TS 23.682[ Architecture enhancements to facilitate communications with packet data networks and applications ] [98]. The realm part format of the External Group Identifier shall contain a Domain Identifier as specified in 3GPP TS 23.682[ Architecture enhancements to facilitate communications with packet data networks and applications ] [98]. As specified in clause 4 of IETF RFC 4282 [53], the Domain Identifier shall be a duly registered Internet domain name. The combination of Local Identifier and Domain Identifier makes the External Group Identifier globally unique. The result of the External Group Identifier form is: "<Local Identifier>@<Domain Identifier>" An example of an External Group Identifier is: Local Identifier in use: "Group1"; Domain Identifier = "domain.com"; Which gives the External Group Identifier as: [email protected] | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 19.7.3 |
1,441 | I.1 Causes related to nature of request | Cause value = 8 Operator Determined Barring This cause code is used by the network to indicate that the requested service was rejected by the SGSN due to Operator Determined Barring. Cause value = 24 MBMS bearer capabilities insufficient for the service This cause code is used by the network to indicate that an MBMS context activation request was rejected by the network, because the MBMS bearer capabilities are insufficient for the MBMS service. Cause value = 25 LLC or SNDCP failure (A/Gb mode only) This cause code is used by the MS indicate that a PDP context is deactivated because of a LLC or SNDCP failure (e.g. if the SM receives a SNSM-STATUS.request message with cause "DM received " or " invalid XID response ", see 3GPP TS 44.065[ Mobile Station (MS) - Serving GPRS Support Node (SGSN); Subnetwork Dependent Convergence Protocol (SNDCP) ] [78]) Cause value = 26 Insufficient resources This cause code is used by the MS or by the network to indicate that a PDP context activation request, secondary PDP context activation request, PDP context modification request, or MBMS context activation request cannot be accepted due to insufficient resources. Cause value = 27 Missing or unknown APN This cause code is used by the network to indicate that the requested service was rejected by the external packet data network because the access point name was not included although required, or if the access point name could not be resolved. Cause value = 28 Unknown PDP address or PDP type This cause code is used by the network to indicate that the requested service was rejected by the external packet data network because the PDP address or type could not be recognised. Cause value = 29 User authentication failed This cause code is used by the network to indicate that the requested service was rejected by the external packet data network due to a failed user authentication. Cause value = 30 Activation rejected by GGSN, Serving GW or PDN GW This cause code is used by the network to indicate that the requested service was rejected by the GGSN, Serving GW or PDN GW. Cause value = 31 Activation rejected, unspecified This cause code is used by the network or by the MS to indicate that the requested service was rejected due to unspecified reasons. Cause value = 32 Service option not supported This cause code is used by the network when the MS requests a service which is not supported by the PLMN. Cause value = 33 Requested service option not subscribed See Annex G, clause 4. Cause value = 34 Service option temporarily out of order See Annex G, clause 4. Cause value = 35 NSAPI already used This cause code may be used by a network to indicate that the NSAPI requested by the MS in the PDP context activation request is already used by another active PDP context of this MS. Never to be sent, but can be received from a R97/R98 network at PDP context activation Cause value = 36 Regular deactivation This cause code is used to indicate a regular MS or network initiated PDP context deactivation or a regular network initiated MBMS context deactivation. Cause value = 37 QoS not accepted This cause code is used by the MS if the new QoS cannot be accepted that were indicated by the network in the PDP Context Modification procedure. Cause value = 38 Network failure This cause code is used by the network to indicate that the requested service is rejected due to an error situation in the network. Cause value = 39 Reactivation requested This cause code is used by the network to request a PDP context reactivation (e.g. after a GGSN restart or after selection of a different GGSN by the network for Selected IP Traffic Offload). Cause value = 40 Feature not supported This cause code is used by the MS to indicate that the PDP context activation or the MBMS context activation initiated by the network is not supported by the MS. Cause value = 41 semantic error in the TFT operation. This cause code is used by the network or the MS to indicate that there is a semantic error in the TFT operation included in a secondary PDP context activation request or an MS-initiated PDP context modification or a network requested secondary PDP context activation. Cause value = 42 syntactical error in the TFT operation. This cause code is used by the network or the MS to indicate that there is a syntactical error in the TFT operation included in a secondary PDP context activation request or an MS-initiated PDP context modification or a network requested secondary PDP context activation. Cause value = 43 unknown PDP context This cause code is used by the network or the MS to indicate that the PDP context identified by the Linked TI IE in the secondary PDP context activation request or a network requested secondary PDP context activation is not active. Cause value = 44 semantic errors in packet filter(s) This cause code is used by the network or the MS to indicate that there is one or more semantic errors in packet filter(s) of the TFT included in a secondary PDP context activation request or an MS-initiated PDP context modification or a network requested secondary PDP context activation. Cause value = 45 syntactical error in packet filter(s) This cause code is used by the network or the MS to indicate that there is one or more syntactical errors in packet filter(s) of the TFT included in a secondary PDP context activation request or an MS-initiated PDP context modification or a network requested secondary PDP context activation. Cause value = 46 PDP context without TFT already activated This cause code is used by the network or the MS to indicate that it has already activated a PDP context without TFT. Cause value = 47 Multicast group membership time-out This cause code is used by the network to indicate that the MBMS context is deactivated because the timer supervising the IGMP group membership interval (see RFC 3376 [107], subclause 8.4) or the MLD multicast listener interval (see RFC 2710 [108], subclause 7.4, and RFC 3810 [148], subclause 9.4) expired. Cause value = 48 Request rejected, Bearer Control Mode violation This cause code is used by the network or the MS to indicate that the requested service was rejected because of Bearer Control Mode violation. Cause value = 50 PDP type IPv4 only allowed This cause code is used by the network to indicate that only PDP type IPv4 is allowed for the requested PDN connectivity. Cause value = 51 PDP type IPv6 only allowed This cause code is used by the network to indicate that only PDP type IPv6 is allowed for the requested PDN connectivity. Cause value = 52 single address bearers only allowed This cause code is used by the network to indicate that the requested PDN connectivity is accepted with the restriction that only single IP version bearers are allowed. Cause value = 56 Collision with network initiated request. This cause code is used by the network to indicate that the MS-initiated request was rejected since the network has requested a secondary PDP context activation for the same service using a network-initiated procedure. Cause value = 57 PDP type IPv4v6 only allowed This cause code is used by the network to indicate that only PDP types IPv4, IPv6 or IPv4v6 are allowed for the requested PDN connectivity. Cause value = 58 PDP type non IP only allowed This cause code is used by the network to indicate that only PDP type non IP is allowed for the requested PDN connectivity. Cause value = 60 Bearer handling not supported This cause code is used by the network to indicate that the procedure requested by the MS was rejected because the bearer handling is not supported. Cause value = 65 Maximum number of PDP contexts reached This cause code is used by the network to indicate that the procedure requested by the MS was rejected as the network has reached the maximum number of simultaneously active PDP contexts for the MS. Cause value = 66 Requested APN not supported in current RAT and PLMN combination This cause code is used by the network to indicate that the procedure requested by the MS was rejected because the requested APN is not supported in the current RAT and PLMN. Cause value = 112 APN restriction value incompatible with active PDP context. This cause code is used by the network to indicate that the PDP context(s) or MBMS context(s) have an APN restriction value that is not allowed in combination with a currently active PDP context. Restriction values are defined in 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [74], subclause 15.4. Cause value = 113 Multiple accesses to a PDN connection not allowed This ESM cause is used by the network to indicate that multiple accesses to a PDN connection for NBIFOM is not allowed. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | I.1 |
1,442 | 8.7.17 TDD (1024QAM and up to 4 Rx supported) | The common parameters are specified in Table 8.7.17-1 for UE which is capable of supporting 1024QAM. Table 8.7.17-1: Common Test Parameters (TDD) The UE capability for 1024QAM is signalled per band or per band combination, hence the SDR tests with the mixed modulation orders and the mixed receiver antenna numbers across CC-s are specified. For UE not supporting CA and supporting 1024QAM, the TB success rate shall be higher than 85% when PDSCH is scheduled with FRC in Table 8.7.17-4 according the UE capability. The maximum supported channel bandwidth and MIMO layer are configured during the test. For UE supporting CA and supporting 1024QAM at least on one CC for a supported CA configuration, the SDR requirements are specified as follows: - If UE is capable of supporting 256QAM, the TB success rate shall be higher than 85% on each CC when PDSCH-s are scheduled with FRC-s in Table 8.7.17-3 for the transmission with 256QAM and Table 8.7.17-4 for the transmission with 1024QAM according to the reported capability of supported modulation order for the determined CA configuration. - If UE is not capable of supporting 256QAM, the TB success rate shall be higher than 85% on each CC when PDSCH-s are scheduled with FRC-s in Table 8.7.17-2 for the transmission with 64QAM and Table 8.7.17-4 for the transmission with 1024QAM according to the reported capability of supported modulation order for the determined CA configuration. For UE supporting 1024 QAM, the SDR requirement with 64QAM and 256QAM only is not applicable. The CA configuration or band for single carrier, bandwidth combination or bandwidth for single carrier, modulation order on each CC and MIMO layer on each CC are determined by the following procedure. - Among all the supported CA configurations which support 1024QAM at least on one CC, select one set of {CA configuration or a band, bandwidth combination or bandwidth, modulation order on each CC, MIMO layer on each CC}, which leads to the largest equivalent aggregated bandwidth. The equivalent aggregated bandwidth is defined as Where N is the number of CCs, represents the MIMO layer, represents the bandwidths on each CC, [ is the scaling factor according to the supported modulation order on each CC, where Mi = 0.75 is used if the maximum modulation order of CC i is 64QAM, Mi = 1 is used if the maximum modulation order of CC i is 256QAM, and Mi = 1.25 is used if the maximum modulation order of CC i is 1024QAM.] - When there are multiple sets of {CA configuration or a band, bandwidth combination or bandwidth, modulation order on each CC, MIMO layer on each CC} which can reach the same equivalent aggregated bandwidth, select one among the sets with the largest number of CCs supporting 1024QAM. - When there are multiple sets of {CA configuration or a band, bandwidth combination or bandwidth, modulation order on each CC, MIMO layer on each CC} which can reach the same equivalent aggregated bandwidth with the same number of CCs supporting 1024QAM, select one among the sets with the largest number of CCs supporting 4 layer. - The procedure applies also for the single carrier operating band instead of CA configuration, and bandwidth instead of bandwidth combination. The TB success rate for single carrier or on each CC for CA is defined as 100%*NDL_correct_rx/ (NDL_newtx + NDL_retx), where NDL_newtx is the number of newly transmitted DL transport blocks, NDL_retx is the number of retransmitted DL transport blocks, and NDL_correct_rx is the number of correctly received DL transport blocks. The TB success rate shall be sustained during at least 300 frames. Table 8.7.17-2: Per-CC FRC for SDR test(TDD 64QAM) Table 8.7.17-3: Per-CC FRC for SDR test (TDD 256QAM) Table 8.7.17-4: Per-CC FRC for SDR test (TDD 1024QAM) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.7.17 |
1,443 | 4.11.0a.2a.6 UE Policy Association Modification initiated by the PCF for the UE | The following impacts are applicable to clause 4.16.12.2 (UE Policy Association Modification initiated by the PCF procedure): In the non-roaming case, the V-PCF is not involved, the AMF is replaced by the PCF for the PDU Session, and the role of the H-PCF is performed by the PCF for the UE. For the Home Routed roaming scenarios, the V-PCF is not involved, the AMF is replaced by the H-PCF for the PDU Session, and the role of the H-PCF is performed by the H-PCF for the UE. For the LBO roaming scenarios, the AMF is replaced by the V-PCF for the PDU Session, the role of the V-PCF is performed by the V-PCF for the UE and the role of the H-PCF is performed by the H-PCF for the UE. - Steps 1a, 1c, 2a, 2c and 2d: These steps are not applicable for Home Routed roaming, since the V-PCF is not involved. - Step 3: The (H-)PCF may create the UE policy container including UE policy information as defined in clause 6.1.2.2.2 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. The (H-) PCF checks whether the UE Policy Association for the UE is established for a UE in EPS by checking the RAT-Type of the UE Policy Association and in this case the (H-)PCF may send the UE Policy Container in the Npcf_UEPolicyControl_UpdateNotify Request. The (H-)PCF may provide updated PCRTs over the UE policy association. For Home Routed roaming, the V-PCF for a UE is not involved, therefore the Service Parameters provided by the AF from the VPLMN are not used by the H-PCF as input for the generation of the URSP rules. NOTE: Steps 5 and 6 are executed only in LBO roaming. - Step 5: In case the UE Policy Association is for a UE in EPS, the (V-) PCF for the UE provides the UE Policy Container and/or policy control triggers to the (V-) PCF for the PDU Session. - Step 6: The (V-) PCF for the PDU session sends a response to the (V-) PCF for the UE. - Steps 7, 8 and 9 are replaced by steps 10-13 of procedure UE Policy Association Establishment in EPS from clause 4.11.0a.2a.5. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.11.0a.2a.6 |
1,444 | Context Request | The new MME/SGSN shall send the Context Request message to the old MME/SGSN on S3/S16/S10 interface as a part of TAU/RAU procedure and UTRAN/GERAN to E-UTRAN/UTRAN (HSPA) SRVCC procedure to get the MM and EPS bearer Contexts for the UE. NOTE 1: During UTRAN/GERAN to E-UTRAN/UTRAN (HSPA) SRVCC procedure as specified in 3GPP TS 23.216[ Single Radio Voice Call Continuity (SRVCC); Stage 2 ] [43], the GUTI, RAI IE, P-TMSI IE and P-TMSI Signature IE, are not received directly from the UE but from the MSC Server over Sv interface. The new MME shall send the Context Request message to the old AMF on N26 interface as a part of an 5GS to EPS Idle mode Mobility using N26 interface procedure, to get the MM and EPS bearer Contexts for the UE. The new AMF shall send the Context Request message to the old MME on N26 interface as a part of an EPS to 5GS Idle mode registration using N26 interface procedure, to get the MM and EPS bearer Contexts for the UE. If the sending/new node is a MME, it shall include in the Context Request message: - the GUTI IE and Complete TAU Request Message IE, if the GUTI or the indication of mapped or native GUTI received from UE indicates the old node is a MME, as specified in clause 2.8.2.2.2 and 2.10.2.1.2 of 3GPP TS 23.003[ Numbering, addressing and identification ] [2]. - the RAI IE and the P-TMSI IE, which are derived from the GUTI received from UE, and the P-TMSI Signature that was received intact from the UE, if the GUTI or the indication of mapped or native GUTI indicates the old node is an SGSN as specified in clause 2.8.2.2.2 of 3GPP TS 23.003[ Numbering, addressing and identification ] [2]. If the sending/new node is an SGSN, it shall include RAI IE, P-TMSI IE and P-TMSI Signature IE in the Context Request message. If the receiving/old node is an MME, it shall construct GUTI according to the RAI IE, P-TMSI IE and P-TMSI Signature IE (see the mapping relationship between RAI, P-TMSI, P-TMSI signature and GUTI defined in 3GPP TS 23.003[ Numbering, addressing and identification ] [2]), and find UE context via this GUTI. If the sending/new node is an AMF, it shall include the GUTI IE, which is derived from the 5G-GUTI received from UE, and the Complete TAU Request Message IE in the Context Request message, if the AMF receives a mapped GUTI from the UE, that is indication that the old node is an MME, as specified in clause 2.10.2.2.2 of 3GPP TS 23.003[ Numbering, addressing and identification ] [2]. If the receiving/old node is an AMF, it shall construct 5G-GUTI from the GUTI IE (see the mapping relationship between GUTI and 5G-GUTI defined in 3GPP TS 23.003[ Numbering, addressing and identification ] [2]), and find UE context via this 5G-GUTI. The new MME differentiates the type of the old node as specified in clause 2.8.2.2.2 of 3GPP TS 23.003[ Numbering, addressing and identification ] [2]. If the old node is an SGSN, the GUTI shall be mapped to RAI and P-TMSI by the new MME; if the old node is a MME, the new MME include GUTI IE and Complete TAU Request Message IE in the Context Request message. The Mapping between temporary and area identities is defined in 3GPP TS 23.003[ Numbering, addressing and identification ] [2]. The Target PLMN ID IE shall be used in old SGSN/MME in order to decide whether un-used authentication vectors to be distributed to new SGSN/MME/AMF or not. Distribution and use of authentication vectors between different serving network domains are specified in 3GPP TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [12]. The AMF shall not transmit un-used authentication vectors to an MME and shall discard any un-used authentication vectors received from an MME, regardless of whether the MME and AMF pertain to the same or different serving network domains. Table -1 specifies the presence requirements and conditions of the IEs in the message. Table -1: Information Elements in a Context Request | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | Context |
1,445 | 6.8.1.2.1 Transition from CM-IDLE to CM-CONNECTED | The UE sends an initial NAS message to initiate transition from CM-IDLE to CM-CONNECTED state (see TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [35]. If a full native 5G NAS security context is already available in the UE and the AMF, then the UE shall directly take into use the available full 5G NAS security context and use it to protect the initial NAS message using the distinct pair of NAS COUNTs together with the NAS connection identifier for this access. If the UE is simultaneously registered over both 3GPP access and non-3GPP access in the same AMF, then if there is a need for the AMF to take a new partial 5G NAS security context into use on this access (access A), derived from primary authentication executed on a different access, then the AMF needs to send a NAS SMC to the UE on this access (access A) in order to take the new partial 5G NAS security context also into use on this access as described in clause 6.4.2.2. On transitions to CM-CONNECTED, the AMF should be able to check whether a new authentication is required, e.g. because of prior inter-provider handover. If the UE is simultaneously registered over both 3GPP access and non-3GPP access in the same AMF, then if a new primary authentication is run, then the new derived partial 5G NAS security context needs to be taken into use on this access (access A) with a NAS SMC using the distinct pair of NAS COUNTs for this access. But the new derived partial 5G NAS security context also needs to be taken into use on the other accesses (access B) with a NAS SMC using the distinct pair of NAS COUNTs for the respective access as part of the NAS procedure as described in clause 6.4.2.2. When cryptographic protection for radio bearers is established RRC protection keys and UP protection keys shall be generated as described in sub-clause 6.2.3.1 while KAMF is assumed to be already available in the AMF. The initial NAS message shall be integrity protected by the current 5G NAS security context if such exists using the distinct pair of NAS COUNTs together with the NAS connection identifier for this access. If no current 5G NAS security context exists the ME shall signal "no key available" in the initial NAS message. KAMF may have been established in the AMF as a result of a primary authentication run on this access or on a different access, or as a result of a 5G security context transfer from another AMF during N2 handover or idle mode mobility. When the gNB/ng-eNB releases the RRC connection, the UE and the gNB/ng-eNB shall delete the keys they store such that state in the network for CM-IDLE state UEs will only be maintained in the AMF. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.8.1.2.1 |
1,446 | 6.1.2 Requirements 6.1.2.1 General | The serving 5G network shall support providing connectivity to home and roaming users in the same network slice. In shared 5G network configuration, each operator shall be able to apply all the requirements from this clause to their allocated network resources. The 5G system shall be able to support IMS as part of a network slice. The 5G system shall be able to support IMS independent of network slices. For a UE authorized to access multiple network slices of one operator which cannot be simultaneously used by the UE (e.g. due to radio frequency restrictions), the 5G system shall be able to support the UE to access the most suitable network slice in minimum time (e.g. based on the location of the UE, ongoing applications, UE capability, frequency configured for the network slice). 5G system shall minimize signalling exchange and service interruption time for a network slice, e.g. when restrictions related to radio resources change (e.g., frequencies, RATs). For a roaming UE activating a service/application requiring a network slice not offered by the serving network but available in the area from other network(s), the HPLMN shall be able to provide the UE with prioritization information of the VPLMNs with which the UE may register for the network slice. The 5G system shall be able to minimize power consumption of a UE (e.g. reduce unnecessary cell measurements), in an area where no authorized network slice is available. When a UE moves out of the service area of a network slice for an active application, the 5G system shall be able to minimize impact on the active applications (e.g., providing early notification). NOTE 1: Various methods can be used to detect whether the UE moves toward the border area and to notify the UE. The 5G system shall support a mechanism for a UE to select and access network slice(s) based on UE capability, ongoing application, radio resources assigned to the slice, and policy (e.g., application preference). The 5G system shall support a mechanism to optimize resources of network slices (e.g., due to operator deploying different frequency to offer different network slices) based on network slice usage patterns and policy (e.g., application preference) of a UE or group of UEs For UEs that have the ability to obtain service from more than one VPLMN simultaneously, the following requirements apply: - When a roaming UE with a single PLMN subscription requires simultaneous access to multiple network slices and the network slices are not available in a single VPLMN, the 5G system shall enable the UE to: - be registered to more than one VPLMN simultaneously; and - use network slices from more than one VPLMN simultaneously - The HPLMN shall be able to authorise a roaming UE with a single PLMN subscription to be registered to more than one VPLMN simultaneously in order to access network slices of those VPLMNs. - The HPLMN shall be able to provide a UE with permission and prioritisation information of the VPLMNs the UE is authorised to register to in order to use specific network slices. NOTE 2: The above requirements assume certain UE capabilities, e.g. the ability to be connected to more than one PLMN simultaneously. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.1.2 |
1,447 | 13.2.1.1 Address allocation using DHCPv4 | The following description bullet items describe the DHCPv4 signal flow. For a detailed description of the DHCP messages refer to RFC 2131 [26] and RFC 1542 [27]. The end-to-end protocol configuration is depicted in figure 16c. 1) The TE and MT exchange several AT commands carrying the QoS and other parameters requested by the TE, and requesting the activation of a PDP context of PDP type IP. The TE selects the APN of the configured Intranet/ISP offering a DHCP service, or the APN consisting of the Reserved Service Label for DHCP that the user has subscribed to. In the latter case the TE will be connected to a PLMN operator-configured service provider offering a DHCP service (according to the APN selection rules). 2) The MT sends the Activate PDP Context Request message to the SGSN with an empty PDP address field. 3) The SGSN selects a GGSN based on the APN requested by the MS and sends a Create PDP Context Request message to that GGSN. The GGSN replies with a Create PDP Context Response message. If the GGSN has not been configured by the operator to use external PDN address allocation with DHCP for the requested APN, the cause shall be set to ‘Service not supported’. No IP address is assigned at this point; the PDP address returned by the GGSN is set to 0.0.0.0, indicating that the IP address is not yet assigned and shall be negotiated by the TE with the Intranet/ISP after the PDP context activation procedure. 4) Depending on the cause value received in the Create PDP Context Response the SGSN sends either an Activate PDP Context Accept or an Activate PDP Context Reject back to the MT. In case of a successful activation the PDP context is established with the PDP address set to 0.0.0.0. 5) Upon reception of the Activate PDP Context Accept, the MT sends an AT response to the TE that acknowledges the completion of the PDP context activation procedure. 6) The TE sends a DHCPDISCOVER message with the IP destination address set to the limited broadcast address (all 1s). The GGSN will pass the DHCPDISCOVER to the DHCP relay agent which will relay the request to the DHCP server configured for the APN of the PDP context. If more than one DHCP server is configured for a given APN, the request will be sent to all of them. The DHCP relay agent will add enough information to the DHCPDISCOVER message to be able to relay the replies back to the MS. How this is done is out of the scope of 3GPP standardisation. 7) DHCP servers receiving the DHCPDISCOVER request reply by sending a DHCPOFFER message including an offered IP address. The DHCP relay agent forwards the replies to the proper MS. 8) The TE chooses one of the possibly several DHCPOFFERs and sends a DHCPREQUEST confirming its choice and requesting additional configuration information. The relay agent relays the DHCPOFFER as explained in step 6. 9) The selected DHCP server receives the DHCPREQUEST and replies with a DHCPACK containing the configuration information requested by the TE. The DHCP relay agent relays the DHCPACK to the TE. 10) The DHCP relay agent passes the allocated IP address to the GGSN which stores it in the corresponding PDP context. The GGSN then initiates a PDP context modification procedure by sending an Update PDP Context Request to the appropriate SGSN with the End User Address information element set to the allocated IP address. 11) The SGSN sends a Modify PDP Context Request to the MT with the allocated IP address in the PDP Address information element. The MT acknowledges by sending a Modify PDP Context Accept to the SGSN. 12) The SGSN sends an Update PDP Context Response to the GGSN. The PDP context has been successfully updated with the allocated IP address. EXAMPLE: In the following example a successful PDP context activation with use of DHCP from end to end is shown. Figure16d: DHCPv4 signal flow | 3GPP TS 29.061 | Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) | CT WG3 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 13.2.1.1 |
1,448 | 10.5.6.18 Notification indicator | The purpose of the Notification indicator information element is to inform the MS about an event which is relevant for the upper layer using a PDP context or having requested a session management procedure. The Notification indicator information element is coded as shown in figure 10.5.159/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.174/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The Notification indicator is a type 4 information element with 3 octets length. Figure 10.5.159/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Notification indicator information element Table 10.5.174/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Notification indicator information element | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 10.5.6.18 |
1,449 | 4.15.3.2.3 NEF service operations information flow | The procedure is used by the AF to subscribe to event notifications, to modify group-based subscriptions to event notification and to explicitly cancel a previous subscription (see clause 4.15.1). Cancelling is done by sending Nnef_EventExposure_Unsubscribe request identifying the subscription to cancel with Subscription Correlation ID. The notification steps 6 to 8 are not applicable in cancellation case. Figure 4.15.3.2.3-1: Nnef_EventExposure_Subscribe, Unsubscribe and Notify operations 1. The AF subscribes to one or several Event(s) (identified by Event ID) and provides the associated notification endpoint of the AF by sending Nnef_EventExposure_Subscribe request. Event Reporting Information defines the type of reporting requested (e.g. one-time reporting, periodic reporting or event based reporting, for Monitoring Events). If the reporting event subscription is authorized by the NEF, the NEF records the association of the event trigger and the requester identity. The subscription may also include Maximum number of reports and/or Maximum duration of reporting IE and optionally MTC Provider Information. If subscription to group-based event notifications are removed or added for certain UEs in a group of UEs for which there is an event notification subscription, the AF provides impacted UE information (e.g. SUPI, MSISDN or External Identity) with operation indication which is either cancellation or addition to NEF via Nnef_EventExposure_Subscribe without cancelling the entire group-based event notification subscription. 2. [Conditional - depending on authorization in step 1] The NEF subscribes to received Event(s) (identified by Event ID) and provides the associated notification endpoint of the NEF to UDM by sending Nudm_EventExposure_Subscribe request. The NEF may either receive DNN, S-NSSAI from AF in step 1 or maps the AF-Identifier into DNN and S-NSSAI combination based on local configuration and include DNN, S-NSSAI in the request. If the reporting event subscription is authorized by the UDM, the UDM records the association of the event trigger and the requester identity. Otherwise, the UDM continues in step 4 indicating failure. If Nnef_EventExposure_Subscribe with update is received in step 1 indicating removal of event notification subscription for certain UEs in a group of UEs for which there is an event notification subscription, the NEF provides impacted UE information (e.g. SUPI, MSISDN or External Identity) with operation indication (cancellation) to UDM via Nudm_EventExposure_Subscribe without cancelling the entire group-based event notification subscription. If the Maximum Number of Reports applies to the event subscription, the NEF sets the stored number of reports of the indicated UE(s) to Maximum Number of Reports. If Nnef_EventExposure_Subscribe with update is received in step 1 indicating addition of event notification subscription for certain UEs in a group of UEs for which there is an event notification subscription, the NEF provides impacted UE information (e.g. SUPI, MSISDN or External Identity) with operation indication (addition) to UDM via Nudm_EventExposure_Subscribe. 3a. [Conditional] If the requested event (e.g. monitoring of Loss of Connectivity) requires AMF assistance, then the UDM sends the Namf_EventExposure_Subscribe to the AMF serving the requested user. The UDM sends the Namf_EventExposure_Subscribe request to the all serving AMF(s) (if subscription applies to a UE or a group of UE(s)), or all the AMF in the same PLMN as the UDM (if subscription applies to any UE). NOTE 1: If the UE, which is a member of a group, registers with an AMF which does not have group event subscription(s) for that group, then the UDM creates subscriptions to those event(s) with the AMF during the Registration procedure in clause 4.2.2.2.2. As the UDM itself is not the Event Receiving NF, the UDM shall additionally provide the notification endpoint of itself besides the notification endpoint of NEF. Each notification endpoint is associated with the related (set of) Event ID(s). This is to assure the UDM can receive the notification of subscription change related event. If the subscription applies to a group of UE(s), the UDM shall include the same notification endpoint of itself, i.e. Notification Target Address (+ Notification Correlation Id), in the subscriptions to all UE's serving AMF(s). NOTE 2: The same notification endpoint of UDM is to help the AMF identify whether the subscription for the requested group event is same or not when a new group member UE is registered. If Nudm_EventExposure_Subscribe with update is received in step 2 indicating removal of event notification subscription for certain UEs in a group of UEs for which there is an event notification subscription, the UDM provides impacted UE information (e.g. SUPI, MSISDN) with operation indication (cancellation) to AMF via Namf_EventExposure_Subscribe without cancelling the entire group-based event notification subscription, for the event monitored by AMF. If Nudm_EventExposure_Subscribe with update is received in step 2 indicating addition of event notification subscription for certain UEs in a group of UEs for which there is an event notification subscription, the UDM provides impacted UE information (e.g. SUPI, MSISDN) with operation indication (addition) to AMF via Namf_EventExposure_Subscribe for the event monitored by AMF. 3b. [Conditional] AMF acknowledges the execution of Namf_EventExposure_Subscribe. 3c. [Conditional] If the requested event (e.g. PDU Session Status) requires SMF assistance, then the UDM sends the Nsmf_EventExposure_Subscribe Request message to each SMF where at least one UE identified in step 2 has a PDU session established. The NEF notification endpoint received in step 2 is included in the message. NOTE 3: In the home routed case, the UDM sends the subscription to the V-SMF via the H-SMF. 3d-e. [Conditional] If the requested event (e.g. UserDataUsageMeasures) requires UPF assistance, the SMF sends the request to the UPF including the NEF notification endpoint received in step 3c according to step 4 in Figure 4.15.4.5.2-1. 3f. [Conditional] The SMF acknowledges the execution of Nsmf_EventExposure_Subscribe. 4. [Conditional] UDM acknowledges the execution of Nudm_EventExposure_Subscribe. If the subscription is applicable to a group of UE(s) and the Maximum number of reports is included in the Event Report information in step 1, the Number of UEs (including all group member UEs irrespective of their registration state) is included in the acknowledgement. If AMF or SMF provides the first event report in step 3b or step 3d, the UDM includes the event report in the acknowledgement. 5. NEF acknowledges the execution of Nnef_EventExposure_Subscribe to the requester that initiated the request. If the NEF has received the first event report already in step 4, the NEF includes the event report in the acknowledgement. 6a - 6b. [Conditional - depending on the Event] The UDM (depending on the Event) detects the event occurs and sends the event report, by means of Nudm_EventExposure_Notify message to the associated notification endpoint of the NEF along with the time stamp. NEF may store the information in the UDR along with the time stamp using either Nudr_DM_Create or Nudr_DM_Update service operation as appropriate. If Nudm_EventExposure_Subscribe with update is received in step 2 indicating removal of event notification subscription for certain UEs in a group of UEs for which there is an event notification subscription, the UDM shall stop the event notification for the impacted UEs. If Maximum number of Reports is applied, the UDM shall set the number of reports of the indicated UE(s) to Maximum Number of Reports for the events monitored by UDM. If Nudm_EventExposure_Subscribe with update is received in step 2 indicating addition of event notification subscription for certain UEs in a group of UEs for which there is an event notification subscription, the UDM shall create subscription to the event notification for the impacted UEs so as to detect the monitored event and send the event report for such impacted UEs. 6c - 6d. [Conditional - depending on the Event] The AMF detects the event occurs and sends the event report, by means of Namf_EventExposure_Notify message to associated notification endpoint of the NEF along with the time stamp. NEF may store the information in the UDR along with the time stamp using either Nudr_DM_Create or Nudr_DM_Update service operation as appropriate. If the AMF has a maximum number of reports stored for the UE or the individual member UE, the AMF shall decrease its value by one for the reported event. If Namf_EventExposure_Subscribe with update is received in step 3a indicating removal of event notification subscription for certain UEs in a group of UEs for which there is an event notification subscription, the AMF shall stop the event notification for the impacted UEs. If Maximum number of Reports is applied, the AMF shall set the number of reports of the indicated UE(s) to Maximum Number of Reports. If Namf_EventExposure_Subscribe with update is received in step 3a indicating addition of event notification subscription for certain UEs in a group of UEs for which there is an event notification subscription, the AMF shall create subscription to the event notification for the impacted UEs so as to detect the monitored event and send the event report for such impacted UEs. For both step 6a and step 6c, when the maximum number of reports is reached and if the subscription is applied to a UE, The NEF unsubscribes the monitoring event(s) to the UDM and the UDM unsubscribes the monitoring event(s) to AMF serving for that UE. For both step 6a and step 6c, when the maximum number of reports is reached for an individual group member UE, the NEF uses the Number of UEs received in step 4 and the Maximum number of reports to determine if reporting for the group is complete. If the NEF determines that reporting for the group is complete, the NEF unsubscribes the monitoring event(s) to the UDM and the UDM unsubscribes the monitoring event(s) to all AMF(s) serving the UEs belonging to that group. NOTE 4: If an expiry time as specified in clause 6.2.6.2.6 of TS 29.518[ 5G System; Access and Mobility Management Services; Stage 3 ] [18] is not included in the event subscription, then the life time of the event subscription needs to be controlled by other means as there is no time based cancellation at all even if any group member UEs fail to register. When the Maximum duration of reporting expires in the NEF, the UDM and the AMF, then each of these nodes shall locally unsubscribe the monitoring event. 6e - 6f. [Conditional - depending on the Event] When the SMF detects a subscribed event, the SMF sends the event report, by means of Nsmf_EventExposure_Notify message, to the associated notification endpoint of the NEF provided in step 3c. NEF may store the information in the UDR along with the time stamp using either Nudr_DM_Create or Nudr_DM_Update service operation as appropriate. 6g - 6h. [Conditional - depending on the Event] When the UPF detects a subscribed event, the UPF sends the event report, by means of Nupf_EventExposure_Notify message, to the associated notification endpoint of the NEF provided by the SMF to UPF as part of step 3c. The NEF may store the information in the UDR along with the time stamp using either Nudr_DM_Create or Nudr_DM_Update service operation as appropriate. 7. [Conditional - depending on the Event in steps 6a-6f] The NEF forwards to the AF the reporting event received by either Nudm_EventExposure_Notify and/or Namf_EventExposure_Notify. In the case of the PDU Session Status event, the NEF maps it to an PDN Connectivity Status notification when reporting to the AF. 8. [Conditional - depending on the Event] The AMF detects the subscription change related event occurs, e.g. Subscription Correlation ID change due to AMF reallocation or addition of new Subscription Correlation ID due to a new group UE registered, it sends the event report, by means of Namf_EventExposure_Notify message to the associated notification endpoint of the UDM. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.15.3.2.3 |
1,450 | 5.4.2.1 HARQ entity | There is one HARQ entity at the MAC entity for each Serving Cell with configured uplink, which maintains a number of parallel HARQ processes allowing transmissions to take place continuously while waiting for the HARQ feedback on the successful or unsuccessful reception of previous transmissions. The number of parallel HARQ processes per HARQ entity is specified in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [2], clause 8. NB-IoT has one or two UL HARQ processes. When the physical layer is configured for uplink spatial multiplexing, as specified in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [2], there are two HARQ processes associated with a given TTI. Otherwise there is one HARQ process associated with a given TTI. At a given TTI, if an uplink grant is indicated for the TTI, the HARQ entity identifies the HARQ process(es) for which a transmission should take place. It also routes the received HARQ feedback (ACK/NACK information), MCS and resource, relayed by the physical layer, to the appropriate HARQ process(es). In asynchronous HARQ operation, a HARQ process is associated with a TTI based on the received UL grant except for UL grant in RAR. Except for NB-IoT UE configured with a single HARQ process, each asynchronous HARQ process is associated with a HARQ process identifier. For UL transmission with UL grant in RAR and for transmission using PUR, HARQ process identifier 0 is used. HARQ feedback is not applicable for asynchronous UL HARQ except if mpdcch-UL-HARQ-ACK-FeedbackConfig is configured. In autonomous HARQ operation, HARQ feedback is applicable. When TTI bundling is configured, the parameter TTI_BUNDLE_SIZE provides the number of TTIs of a TTI bundle. TTI bundling operation relies on the HARQ entity for invoking the same HARQ process for each transmission that is part of the same bundle. Within a bundle HARQ retransmissions are non-adaptive and triggered without waiting for feedback from previous transmissions according to TTI_BUNDLE_SIZE. The HARQ feedback of a bundle is only received for the last TTI of the bundle (i.e the TTI corresponding to TTI_BUNDLE_SIZE), regardless of whether a transmission in that TTI takes place or not (e.g. when a measurement gap occurs). A retransmission of a TTI bundle is also a TTI bundle. TTI bundling is not supported when the MAC entity is configured with one or more SCells with configured uplink. Uplink HARQ operation is asynchronous for NB-IoT UEs, BL UEs or UEs in enhanced coverage except for the repetitions within a bundle, in serving cells configured with pusch-EnhancementsConfig, serving cells operating according to Frame Structure Type 3, for HARQ processes scheduled using short TTI, for HARQ processes scheduled using Short Processing Time, and for HARQ processes associated with an SPS configuration with totalNumberPUSCH-SPS-STTI-UL-Repetitions or totalNumberPUSCH-SPS-UL-Repetitions except for the repetitions within a bundle. For serving cells configured with pusch-EnhancementsConfig, NB-IoT UEs, BL UEs or UEs in enhanced coverage, the parameter UL_REPETITION_NUMBER provides the number of transmission repetitions within a bundle. For each bundle, UL_REPETITION_NUMBER is set to a value provided by lower layers. Bundling operation relies on the HARQ entity for invoking the same HARQ process for each transmission that is part of the same bundle. Within a bundle HARQ retransmissions are non-adaptive and are triggered without waiting for feedback from previous transmissions according to UL_REPETITION_NUMBER. An uplink grant corresponding to a new transmission of the bundle is only received after the last repetiton of the bundle if mpdcch-UL-HARQ-ACK-FeedbackConfig is not configured. An uplink grant corresponding to a retransmission of the bundle is only received after the last repetition of the bundle. For UEs configured with mpdcch-UL-HARQ-ACK-FeedbackConfig, repetitions within a bundle are stopped if an UL HARQ-ACK feedback or an uplink grant corresponding to a new transmission of the bundle is received on PDCCH during the bundle transmission. A retransmission of a bundle is also a bundle. For a SPS configuration with totalNumberPUSCH-SPS-STTI-UL-Repetitions or totalNumberPUSCH-SPS-UL-Repetitions (TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8]), the parameter totalNumberPUSCH-SPS-STTI-UL-Repetitions or totalNumberPUSCH-SPS-UL-Repetitions provides the number of transmission repetitions within a configured grant bundle. Bundling operation relies on the HARQ entity invoking the same HARQ process for each transmission that is part of the same bundle. Within a bundle HARQ retransmissions are non-adaptive and are triggered without waiting for feedback from previous transmissions. TTI bundling is not supported for RN communication with the E-UTRAN in combination with an RN subframe configuration. For transmission of Msg3 during Random Access (see clause 5.1.5) TTI bundling does not apply. For UEs configured with pusch-EnhancementsConfig performing contention free Random Access, NB-IoT UEs, BL UEs or UEs in enhanced coverage, uplink repetition bundling is used for transmission of Msg3. For each TTI, the HARQ entity shall: - identify the HARQ process(es) associated with this TTI, and for each identified HARQ process: - if an uplink grant has been indicated for this process and this TTI: - if the received grant was addressed neither to a Temporary C-RNTI nor to a PUR-RNTI on PDCCH and if the NDI provided in the associated HARQ information has been toggled compared to the value in the previous transmission of this HARQ process; or - if the uplink grant was received on PDCCH for the C-RNTI and the HARQ buffer of the identified process is empty; or - if the uplink grant was provided by RRC for transmission using PUR; or - if the uplink grant was received in a Random Access Response: - if there is a MAC PDU in the Msg3 buffer and the uplink grant was received in a Random Access Response: - if the MAC PDU in the Msg3 buffer contains the Data Volume and Power Headroom Report MAC control element: - the MAC entity shall update the Data Volume and Power Headroom Report MAC control element in the MAC PDU in the Msg3 buffer. - if the UE is an NB-IoT UE and cqi-Reporting is configured by upper layers: - the MAC entity shall update the MAC PDU in the Msg3 buffer in accordance with the DL channel quality measurement result. - obtain the MAC PDU to transmit from the Msg3 buffer. - else if the uplink grant is a configured grant with totalNumberPUSCH-SPS-STTI-UL-Repetitions or totalNumberPUSCH-SPS-UL-Repetitions and if a retransmission within a bundle is triggered for another configured grant with totalNumberPUSCH-SPS-STTI-UL-Repetitions or totalNumberPUSCH-SPS-UL-Repetitions in this TTI: - ignore the uplink grant. - else if the MAC entity is configured with semiPersistSchedIntervalUL shorter than 10 subframes and if the uplink grant is a configured grant, and if the HARQ buffer of the identified HARQ process is not empty, and if HARQ_FEEDBACK of the identified HARQ process is NACK; or if the MAC entity is configured with ul-SchedInterval shorter than 10 subframes and if the uplink grant is a preallocated uplink grant, and if the HARQ buffer of the identified HARQ process is not empty, and if HARQ_FEEDBACK of the identified HARQ process is NACK: - instruct the identified HARQ process to generate a non-adaptive retransmission. - else: - if the UL HARQ operation is synchronous, and the uplink grant is a preallocated uplink grant, and a MAC PDU has previously been obtained from the "Multiplexing and assembly" entity during this handover attempt: - ignore the uplink grant; - else: - obtain the MAC PDU to transmit from the "Multiplexing and assembly" entity, if any; - if a MAC PDU to transmit has been obtained: - deliver the MAC PDU and the uplink grant and the HARQ information to the identified HARQ process; - instruct the identified HARQ process to trigger a new transmission. - else: - flush the HARQ buffer of the identified HARQ process. - else: - if the MAC entity is configured with skipUplinkTxSPS and if the uplink grant received on PDCCH was addressed to the Semi-Persistent Scheduling C-RNTI or to the UL Semi-Persistent Scheduling V-RNTI and if the HARQ buffer of the identified process is empty; or - if UL HARQ operation is autonomous for the identified HARQ process and if the uplink grant is a configured UL grant and if the HARQ buffer of the identified process is empty; or - if the previous uplink grant delivered to the HARQ entity for the same HARQ process was a configured uplink grant for which the UL HARQ operation was autonomous, and if the corresponding UL grant size was different from the UL grant size indicated by the uplink grant for this TTI: - ignore the uplink grant; - else: - deliver the uplink grant and the HARQ information (redundancy version) to the identified HARQ process; - if UL HARQ operation is autonomous for the identified HARQ process and if the uplink grant is a configured UL grant: - instruct the identified HARQ process to generate a non adaptive retransmission. - else: - instruct the identified HARQ process to generate an adaptive retransmission. - else, if the HARQ buffer of this HARQ process is not empty: - instruct the identified HARQ process to generate a non-adaptive retransmission; - if the non-adaptive retransmission collides with a transmission of another HARQ process scheduled using Short Processing Time: - instruct the identified HARQ process to generate a positive acknowledgement (ACK) of the data in the corresponding TB. When determining if NDI has been toggled compared to the value in the previous transmission the MAC entity shall ignore NDI received in all uplink grants on PDCCH for its Temporary C-RNTI and PUR-RNTI. | 3GPP TS 36.321 | Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification | RAN2 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 5.4.2.1 |
1,451 | 5.3.6.1 Service description | The 3GPP circuit-switched multimedia call is based on the 3G-324M (see 3GPP TS 26.111[ Codec for circuit switched multimedia telephony service; Modifications to H.324 ] [80]), which is a 3GPP-variant of the ITU-T Recommendation H.324 [146]. CS Multimedia telephony is a Bearer Service, which utilizes the Synchronous Transparent Data service (BS30), see 3GPP TS 22.002[ Circuit Bearer Services (BS) supported by a Public Land Mobile Network (PLMN) ] [3]. At the multimedia call setup the required call type, 3G-324M, is indicated, for the network to be able to invoke appropriate interworking functionality. In the peer end the H.324 information is used to invoke the terminal application. In addition to H.324 indication the terminal must select Information Transfer Capability (ITC) for the multimedia call. The 'correct' ITC depends on the peer end and the transporting networks; an all-ISDN call is a UDI/RDI call, and a call, which involves PSTN, is an analog "3.1 kHz audio" call. For the case when the setup of a multimedia call is not successful, fallback to speech is specified. Users may also request a service change between UDI/RDI multimedia and speech modes during a call (see 3GPP TS 23.172[ Technical realization of Circuit Switched (CS) multimedia service UDI/RDI fallback and service modification; Stage 2 ] [97]). | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.3.6.1 |
1,452 | 4.2.11 Network Slice Admission Control Function (NSACF) procedures 4.2.11.1 General | The Network Slice Admission Control Function procedures are performed for an S-NSSAI which is subject to Network Slice Admission Control (NSAC) as described in TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If charging needs to be enabled, the NSACF may act as a NF (CTF) and interact with the CHF to support the Event based charging as defined in TS 32.290[ Telecommunication management; Charging management; 5G system; Services, operations and procedures of charging using Service Based Interface (SBI) ] [42]. Depending on the NSAC architecture deployed in the network, three options of NSAC procedures are defined: - Option 1: The NSAC procedure for number of UEs or PDU sessions for an S-NSSAI is based on non-Hierarchal NSAC architecture. The corresponding procedures are described in clause 4.2.11.2 and clause 4.2.11.4 respectively. - Option 2: The NSAC procedure for number of UEs or PDU sessions for an S-NSSAI is based on centralized NSAC architecture. The corresponding procedures are described in clause 4.2.11.2 and clause 4.2.11.4 respectively. - Option 3: The NSAC procedure for number of UEs or PDU sessions for an S-NSSAI is based on hierarchical NSAC architecture. The corresponding procedures are described in clause 4.2.11.2a and clause 4.2.11.4a respectively. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.2.11 |
1,453 | 6.3.5 Handling of APN based congestion control | The network may detect and start performing the APN based congestion control when one or more APN congestion criteria as specified in 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [10] are met. The network may store an APN congestion back-off time on a per UE and congested APN basis. If the UE does not provide an APN for a non-emergency PDN connection, then the MME uses the APN which is used in PDN GW selection procedure as congested APN. When APN based congestion control is active, the network may reject session management requests except the modification of bearer resources requests from UEs or disconnect existing PDN connections with ESM cause value #26 "insufficient resources". In the UE, EPS session management timers T3396 for APN based congestion control are started and stopped on a per APN basis. The APN associated with T3396 is the APN provided by the UE when the PDN connection is established. If no APN is included in the PDN CONNECTIVITY REQUEST or, when applicable, in the ESM INFORMATION RESPONSE message, then T3396 is associated with no APN. For this purpose the UE shall memorize the APN provided to the network during the PDN connection establishment. The timer T3396 associated with no APN will never be started due to any ESM procedure related to an emergency PDN connection. If the timer T3396 associated with no APN is running or is deactivated, it does not affect the ability of the UE to request an emergency PDN connection. If timer T3396 is running or is deactivated, the UE is allowed to indicate change of the 3GPP PS data off UE status, initiate PDN disconnection procedure, initiate bearer resource modification procedure to release of bearer resources for the respective APN, and if the UE is a UE configured to use AC11 – 15 in selected PLMN, then the UE is allowed to initiate an attach procedure or any EPS session management procedure for the respective APN. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.3.5 |
1,454 | 13.4.3.1 QoE Measurement Collection Activation and Reporting in NR-DC | For a UE in NR-DC, either the MN or the SN can generate QoE configuration(s) and transmit the configuration to the UE. If both the MN and the SN send QoE configurations to the UE, the MN and the SN do not use the same set of application layer measurement configuration identities, which means there is a unique ID for QoE configurations across MN and SN. For a UE in NR-DC, the MN and the SN may coordinate QoE measurement collection activation and reporting as follows: For management-based QoE activation, the MN: - Allocates the application layer measurement configuration ID, and indicates it to the SN if needed; - Determines whether the MN or the SN sends the QoE configuration to the UE, in case the SN inquires the MN. For management-based QoE measurement configurations received directly by the SN from OAM, the SN may perform UE selection. For a selected UE, the SN indicates to the MN the QoE reference of the management-based QoE session and, separately for the QoE reports and RAN visible QoE reports, the SN indicates whether it is going to receive the corresponding reports via the MN (using SRB4) or using SRB5. Upon receiving the request, the MN can decide and notify the SN whether the MN sends the QoE and RAN Visible QoE configuration to the UE, or whether the SN should send the configuration(s) to the UE. The SN can send a QoE and a RAN Visible QoE measurement configuration directly to the UE via SRB3, or in a transparent container to the MN, which then sends the configuration to the UE via SRB1. For management-based QoE configurations received from OAM and for signalling-based QoE configurations, the MN can only send the configuration to the UE via SRB1, and the UE can send the QoE reports via SRB4 or SRB5. For a UE in NR-DC, both SRB4 and SRB5 can be configured simultaneously for QoE reporting. The network explicitly indicates to the UE whether to send QoE reports via SRB4 or SRB5, per QoE reference, separately for QoE reports and RAN visible QoE reports. The SRB for QoE reporting can be changed during the application session. The command for changing the SRB used for reporting may be sent to the UE by the node that configured that specific QoE configuration. The node that currently receives the QoE reports via the Uu interface can request from the peer node that the QoE reporting leg is switched to the peer node per QoE Reference. The leg switch for QoE reporting needs to be approved by both nodes serving the UE. RAN visible QoE reports can be sent via the same SRB as the QoE reports pertaining to the same QoE reference, or via a different SRB. RAN visible QoE reports can be sent to the SN directly via SRB5, or via the MN using SRB4. If encapsulated QoE reports cannot be sent because the SRB configured for the encapsulated QoE reporting is not available, the UE continues to store the reports until the SRB is available or the QoE configuration is released. If RAN visible QoE reports cannot be sent because the SRB configured for RAN visible QoE measurement reporting is not available, the UE discards the RAN visible QoE report. The MN should inform the SN that a UE is configured with a management-based QoE/RAN visible QoE measurement configuration. If the MN has configured the UE with QoE measurements, and if the UE is configured to send the QoE reports to the SN, then, if the MN decides that the SN forwards the reports directly to the MCE, the MN should indicate to the SN the QoE reference, the MCE IP address and the application layer measurement configuration ID. If the SN has configured the UE with QoE measurements, and if the UE is configured to send the QoE reports to the MN, then, if the SN decides that the MN forwards the reports directly to the MCE, the SN should indicate to the MN the QoE reference and the MCE IP address. If the SN has released a QoE configuration towards a UE, the SN should inform the MN. When SCG is deactivated, for QoE configurations configured to use SRB5 for QoE reporting, it is up to network implementation to reconfigure the reporting leg to SRB4, release the QoE configuration or pause the QoE reporting. For UL data arrival on SRB5 while the SCG is deactivated, the UE does not indicate to the MN that it has QoE report to transmit over SRB5 for the purpose of SCG activation. When the SCG is released, the UE releases all the QoE measurements configured by the SCG and discards the unsent QoE reports configured to be reported via SRB5. In order to allow the transmission of application layer measurement reports which exceed the maximum PDCP SDU size, the network can inform the UE whether the MN allows RRC segmentation of MeasurementReportAppLayer message via SRB4 and whether the SN allows RRC segmentation of MeasurementReportAppLayer message via SRB5. | 3GPP TS 37.340 | Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Overall Description; Stage-2 | RAN2 | 3GPP Series : 37 , Multiple radio access technology aspects | 13.4.3.1 |
1,455 | 16.12.6.2 Switching from direct to indirect path | The gNB can select a L2 U2N Relay UE in any RRC state i.e., RRC_IDLE, RRC_INACTIVE, or RRC_CONNECTED, as a target L2 U2N Relay UE for direct to indirect path switch. For service continuity of L2 U2N Remote UE, the following procedure is used, in case of the L2 U2N Remote UE switching from direct to indirect path under the same gNB via a L2 U2N Relay UE in RRC_CONNECTED: Figure 16.12.6.2-1: Procedure for L2 U2N Remote UE intra-gNB switching from direct to indirect path via a L2 U2N Relay UE in RRC_CONNECTED 1. The L2 U2N Remote UE reports one or multiple candidate L2 U2N Relay UE(s) and Uu measurements, after it measures/discovers the candidate L2 U2N Relay UE(s): - The L2 U2N Remote UE filters the appropriate L2 U2N Relay UE(s) according to relay selection criteria before reporting. The L2 U2N Remote UE shall report only the L2 U2N Relay UE candidate(s) that fulfil the higher layer criteria; - The reporting includes at least a L2 U2N Relay UE ID, a L2 U2N Relay UE' s serving cell ID, and a sidelink measurement quantity information. SD-RSRP is used as sidelink measurement quantity. 2. The gNB decides to switch the L2 U2N Remote UE to a target L2 U2N Relay UE. Then the gNB sends an RRCReconfiguration message to the target L2 U2N Relay UE, which includes at least the L2 U2N Remote UE's local ID and L2 ID, Uu Relay RLC channel and PC5 Relay RLC channel configuration for relaying, and bearer mapping configuration. 3. The gNB sends the RRCReconfiguration message to the L2 U2N Remote UE. The RRCReconfiguration message includes at least the L2 U2N Relay UE ID, Remote UE's local ID, PC5 Relay RLC channel configuration for relay traffic and the associated end-to-end Uu radio bearer(s). The L2 U2N Remote UE stops User Plane and Control Plane transmission over the direct path after reception of the RRCReconfiguration message from the gNB. 4. The L2 U2N Remote UE establishes PC5-RRC connection with target L2 U2N Relay UE. 5. The L2 U2N Remote UE completes the path switch procedure by sending the RRCReconfigurationComplete message to the gNB via the L2 U2N Relay UE. 6. The data path is switched from direct path to indirect path between the L2 U2N Remote UE and the gNB. In case the selected L2 U2N Relay UE for direct to indirect path switch is in RRC_IDLE or RRC_INACTIVE, after receiving the path switch command, the L2 U2N Remote UE establishes a PC5 link with the L2 U2N Relay UE and sends the RRCReconfigurationComplete message via the L2 U2N Relay UE, which triggers the L2 U2N Relay UE to enter RRC_CONNECTED state. The procedure for L2 U2N Remote UE switching to indirect path in Figure 16.12.6.2-1 can be also applied for the case that the selected L2 U2N Relay UE for direct to indirect path switch is in RRC_IDLE or RRC_INACTIVE with the exception that the RRCReconfiguration message is sent from the gNB to the L2 U2N Relay UE after the L2 U2N Relay UE enters RRC_CONNECTED state, which happens during step 5. For service continuity of L2 U2N Remote UE, the following procedure is used, in case of the L2 U2N Remote UE switching from direct to indirect path via a L2 U2N Relay UE in RRC_CONNECTED under another gNB: Figure 16.12.6.2-2: Procedure for L2 U2N Remote UE inter-gNB switching from direct to indirect path via a L2 U2N Relay UE in RRC_CONNECTED 1. The L2 U2N Remote UE reports one or multiple candidate L2 U2N Relay UE(s) and Uu measurements to the source gNB, after it measures/discovers the candidate L2 U2N Relay UE(s): - The L2 U2N Remote UE filters the appropriate L2 U2N Relay UE(s) according to relay selection criteria before reporting. The L2 U2N Remote UE shall report only the L2 U2N Relay UE candidate(s) that fulfil the higher layer criteria; - The reporting includes at least a L2 U2N Relay UE ID, a L2 U2N Relay UE's serving cell ID, and a sidelink measurement quantity information. SD-RSRP is used as sidelink measurement quantity. 2. The source gNB decides to trigger path switch for the L2 U2N Remote UE onto indirect path of the target gNB, based on MeasurementReport and RRM information. 3. The source gNB sends a HANDOVER REQUEST message to the target gNB to prepare the path switch at the target side. The HANDOVER REQUEST message includes Remote UE L2 ID and a list of candidate target relay UE IDs belonging to one cell. 4. Admission Control may be performed by the target gNB. 5. The target gNB selects one target Relay UE from the list of candidate Relay UEs provided by the source gNB, and sends the RRCReconfiguration message to L2 U2N Relay UE for relaying configuration, which includes at least the L2 U2N Remote UE's local ID and L2 ID, Uu Relay RLC channel and PC5 Relay RLC channel configuration for relaying, and bearer mapping configuration. 6. The target gNB sends the HANDOVER REQUEST ACKNOWLEDGE message to the source gNB, which contains new RRC configuration for L2 U2N Remote UE. 7. The source gNB sends the RRCReconfiguration message to the L2 U2N Remote UE, which includes at least the L2 U2N Relay UE ID, Remote UE's local ID, PC5 Relay RLC channel configuration for relay traffic and the associated Uu end-to-end radio bearer(s). The L2 U2N Remote UE stops User Plane and Control Plane transmission over the direct path after reception of the RRCReconfiguration message from the source gNB. 8. The source gNB sends the SN STATUS TRANSFER message to the target gNB to convey the uplink PDCP SN receiver status and the downlink PDCP SN transmitter status of the L2 U2N Remote UE's DRBs for which PDCP status preservation applies (i.e. for RLC AM). 9. The L2 U2N Remote UE establishes PC5 connection with L2 U2N Relay UE. 10. The L2 U2N Remote UE sends the RRCReconfigurationComplete message to target gNB via the L2 U2N Relay UE. 11. The data path is switched from direct path to indirect path between the L2 U2N Remote UE and the target gNB via the target L2 U2N Relay UE. 12. The target gNB sends the UE CONTEXT RELEASE message to inform the source gNB about the success of the path switch. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.12.6.2 |
1,456 | 4.9.2.3.1 The target AMF is in the PLMN of the N3IWF | Figure 4.9.2.3.1 -1: Handover of a PDU Session procedure from untrusted non-3GPP access to 3GPP access (home routed roaming) 1. If the UE is not registered via 3GPP access, the UE shall initiate Registration procedure as defined in clause 4.2.2.2.2. The NG-RAN selects the same AMF as the one used via non-3GPP access. 2. The UE performs a PDU Session Establishment procedure with the PDU Session ID of the PDU Session to be moved as specified clause 4.3.2.2.2 (PDU Session Establishment for Home Routed Roaming). The AMF selects the same V-SMF as the one used via non-3GPP access. In the Nsmf_PDUSession_Update Response the H-SMF shall include all QoS information for the QoS Flow(s) applicable to the PDU Session for the target access so that when sending the PDU Session Establishment Accept, within the N1 SM container and in the N2 SM information, the V-SMF can include all QoS information (e.g. QoS Rule(s) in N1 SM container, QFI(s) and QoS Profile(s) in N2 SM information) for the QoS Flow(s) acceptable according to VPLMN policies. In case of Handover for a PDU Session eligible to EPS Interworking, the Nsmf_PDUSession_Update Response should also contain: EPS bearer context(s), linked EBI. 3. If the User Plane of the PDU Session is activated in non-3GPP access, the V-SMF executes the release of resource in non-3GPP access by initiating a Namf_Communication_N1N2MessageTransfer (to send N2 resource release request) which triggers performing steps 4 to 7 specified in clause 4.12.7, followed by step 7a/7b specified in clause 4.3.4.2 in order to release the resources over the source non-3GPP access. Because the PDU Session shall not be released, the SMF shall not send the PDU Session Release Command to the UE. Hence, in steps 4 and 7 of clause 4.12.7 as well as in step 7a of clause 4.3.4.2, the messages do not include the N1 SM container but only the N2 Resource Release Request (resp. Ack). Since the PDU Session is not to be released, the SMF shall not execute step 11 of clause 4.3.4.2 and the SM context between the AMF and the SMF is maintained. If the User Plane of the PDU Session is deactivated in non-3GPP access, this step is skipped. The steps 2 and 3 shall be repeated for all PDU Sessions to be moved from to untrusted non-3GPP access to 3GPP access. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.9.2.3.1 |
1,457 | 11 UE Power Saving | The PDCCH monitoring activity of the UE in RRC connected mode is governed by DRX, BA, DCP and cell DTX (see clause 15.4.2.3). When DRX is configured, the UE does not have to continuously monitor PDCCH. DRX is characterized by the following: - on-duration: duration that the UE waits for, after waking up, to receive PDCCHs. If the UE successfully decodes a PDCCH, the UE stays awake and starts the inactivity timer; - inactivity-timer: duration that the UE waits to successfully decode a PDCCH, from the last successful decoding of a PDCCH, failing which it can go back to sleep. The UE shall restart the inactivity timer following a single successful decoding of a PDCCH for a first transmission only (i.e. not for retransmissions); - retransmission-timer: duration until a retransmission can be expected; - cycle: specifies the periodic repetition of the on-duration followed by a possible period of inactivity (see figure 11-1 below); - active-time: total duration that the UE monitors PDCCH. This includes the "on-duration" of the DRX cycle, the time UE is performing continuous reception while the inactivity timer has not expired, and the time when the UE is performing continuous reception while waiting for a retransmission opportunity. Figure 11-1: DRX Cycle A SL UE can be configured with DRX, in which case, PDCCH providing SL grants can be send to the UE only during its active time. When BA is configured, the UE only has to monitor PDCCH on the one active BWP i.e. it does not have to monitor PDCCH on the entire DL frequency of the cell. A BWP inactivity timer (independent from the DRX inactivity-timer described above) is used to switch the active BWP to the default one: the timer is restarted upon successful PDCCH decoding and the switch to the default BWP takes place when it expires. In addition, the UE may be indicated, when configured accordingly, whether it is required to monitor or not the PDCCH during the next occurrence of the on-duration by a DCP monitored on the active BWP. If the UE does not detect a DCP on the active BWP, it does not monitor the PDCCH during the next occurrence of the on-duration, unless it is explicitly configured to do so in that case. A UE can only be configured to monitor DCP when connected mode DRX is configured, and at occasion(s) at a configured offset before the on-duration. More than one monitoring occasion can be configured before the on-duration. The UE does not monitor DCP on occasions occurring during active-time, measurement gaps, BWP switching, or when it monitors response for a CFRA preamble transmission for beam failure recovery (see clause 9.2.6), in which case it monitors the PDCCH during the next on-duration. If no DCP is configured in the active BWP, UE follows normal DRX operation. When CA is configured, DCP is only configured on the PCell. One DCP can be configured to control PDCCH monitoring during on-duration for one or more UEs independently. Power saving in RRC_IDLE and RRC_INACTIVE can also be achieved by UE relaxing neighbour cells RRM measurements when it meets the criteria determining it is in low mobility and/or not at cell edge. UE power saving may be enabled by adapting the DL maximum number of MIMO layers by BWP switching. Power saving is also enabled during active-time via cross-slot scheduling, which facilitates UE to achieve power saving with the assumption that it won't be scheduled to receive PDSCH, triggered to receive A-CSI or transmit a PUSCH scheduled by the PDCCH until the minimum scheduling offsets K0 and K2. Dynamic adaptation of the minimum scheduling offsets K0 and K2 is controlled by PDCCH. Serving Cells of a MAC entity may be configured by RRC in two DRX groups with separate DRX parameters. When RRC does not configure a secondary DRX group, there is only one DRX group and all Serving Cells belong to that one DRX group. When two DRX groups are configured, each Serving Cell is uniquely assigned to either of the two groups. The DRX parameters that are separately configured for each DRX group are on-duration and inactivity-timer. UE power saving in RRC_IDLE/RRC_INACTIVE may be achieved by providing the configuration for TRS with CSI-RS for tracking in TRS occasions. The TRS in TRS occasions may allow UEs in RRC_IDLE/RRC_INACTIVE to sleep longer before waking-up for its paging occasion. The TRS occasions configuration is provided in SIB17. The availability of TRS in the TRS occasions is indicated by L1 availability indication. These TRSs may also be used by the UEs configured with eDRX. UE power saving may be achieved by UE relaxing measurements for RLM/BFD. When configured, UE determines whether it is in low mobility state and/or whether its serving cell radio link quality is better than a threshold. The configuration for low mobility and good serving cell quality criterion is provided through dedicated RRC signalling. RLM and BFD relaxation may be enabled/disabled separately through RRC Configuration. Additionally, RLM relaxation may be enabled/disabled on per Cell Group basis while BFD relaxation may be enabled/disabled on per serving cell basis. The UE is only allowed to perform RLM and/or BFD relaxation when relaxed measurement criterion for low mobility and/or for good serving cell quality is met. If configured to do so, the UE shall trigger reporting of its RLM and/or BFD relaxation status through UE assistance information if the UE changes its respective RLM and/or BFD relaxation status while meeting the UE minimum requirements specified in TS 38.133[ NR; Requirements for support of radio resource management ] [13]. UE power saving may also be achieved through PDCCH monitoring adaptation mechanisms when configured by the network, including skipping of PDCCH monitoring and Search space set group (SSSG) switching. In this case UE does not monitor PDCCH during the PDCCH skipping duration except for the cases as specified in TS 38.213[ NR; Physical layer procedures for control ] [38], or monitors PDCCH according to the search space sets applied in SSSG. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 11 |
1,458 | 5.2.3 Resource blocks | A physical resource block is defined as consecutive SC-FDMA symbols in the time domain and consecutive subcarriers in the frequency domain, where and are given by Table 5.2.3-1. A physical resource block in the uplink thus consists of resource elements, corresponding to one slot in the time domain and 180 kHz in the frequency domain. Table 5.2.3-1: Resource block parameters The relation between the physical resource block number in the frequency domain and resource elements in a slot is given by 5.2.3A Resource unit Resource units are used to describe the mapping of PUSCH using sub-PRB allocations to resource elements for BL/CE UEs. A resource unit is defined as SC-FDMA symbols in the time domain and consecutive subcarriers in the frequency domain, where and are given by Table 5.2.3A-1. Table 5.2.3A-1: Supported combinations of , , and for PUSCH using sub-PRB allocations for Frame Structure type 1 and Frame Structure type 2. | 3GPP TS 36.211 | Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation | RAN1 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 5.2.3 |
1,459 | – CodebookParameters | The IE CodebookParameters is used to convey codebook related parameters. CodebookParameters information element -- ASN1START -- TAG-CODEBOOKPARAMETERS-START CodebookParameters ::= SEQUENCE { type1 SEQUENCE { singlePanel SEQUENCE { supportedCSI-RS-ResourceList SEQUENCE (SIZE (1.. maxNrofCSI-RS-Resources)) OF SupportedCSI-RS-Resource, modes ENUMERATED {mode1, mode1andMode2}, maxNumberCSI-RS-PerResourceSet INTEGER (1..8) }, multiPanel SEQUENCE { supportedCSI-RS-ResourceList SEQUENCE (SIZE (1.. maxNrofCSI-RS-Resources)) OF SupportedCSI-RS-Resource, modes ENUMERATED {mode1, mode2, both}, nrofPanels ENUMERATED {n2, n4}, maxNumberCSI-RS-PerResourceSet INTEGER (1..8) } OPTIONAL }, type2 SEQUENCE { supportedCSI-RS-ResourceList SEQUENCE (SIZE (1.. maxNrofCSI-RS-Resources)) OF SupportedCSI-RS-Resource, parameterLx INTEGER (2..4), amplitudeScalingType ENUMERATED {wideband, widebandAndSubband}, amplitudeSubsetRestriction ENUMERATED {supported} OPTIONAL } OPTIONAL, type2-PortSelection SEQUENCE { supportedCSI-RS-ResourceList SEQUENCE (SIZE (1.. maxNrofCSI-RS-Resources)) OF SupportedCSI-RS-Resource, parameterLx INTEGER (2..4), amplitudeScalingType ENUMERATED {wideband, widebandAndSubband} } OPTIONAL } CodebookParameters-v1610 ::= SEQUENCE { supportedCSI-RS-ResourceListAlt-r16 SEQUENCE { type1-SinglePanel-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-Resources)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, type1-MultiPanel-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-Resources)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, type2-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-Resources)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, type2-PortSelection-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-Resources)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL } OPTIONAL } CodebookParametersAddition-r16 ::= SEQUENCE { etype2-r16 SEQUENCE { -- R1 16-3a Regular eType 2 R=1 etype2R1-r16 SEQUENCE { supportedCSI-RS-ResourceListAdd-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) }, -- R1 16-3a-1 Regular eType 2 R=2 etype2R2-r16 SEQUENCE { supportedCSI-RS-ResourceListAdd-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) } OPTIONAL, -- R1 16-3a-2: Support of parameter combinations 7-8 paramComb7-8-r16 ENUMERATED {supported} OPTIONAL, -- R1 16-3a-3: Support of rank 3,4 rank3-4-r16 ENUMERATED {supported} OPTIONAL, -- R1 16-3a-4: CBSR with soft amplitude restriction amplitudeSubsetRestriction-r16 ENUMERATED {supported} OPTIONAL } OPTIONAL, etype2-PS-r16 SEQUENCE { -- R1 16-3b Regular eType 2 R=1 PortSelection etype2R1-PortSelection-r16 SEQUENCE { supportedCSI-RS-ResourceListAdd-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) }, -- R1 16-3b-1 Regular eType 2 R=2 PortSelection etype2R2-PortSelection-r16 SEQUENCE { supportedCSI-RS-ResourceListAdd-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) } OPTIONAL, -- R1 16-3b-2: Support of rank 3,4 rank3-4-r16 ENUMERATED {supported} OPTIONAL } OPTIONAL } CodebookComboParametersAddition-r16 ::= SEQUENCE { -- R1 16-8 Mixed codebook types type1SP-Type2-null-r16 SEQUENCE { supportedCSI-RS-ResourceListAdd-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) } OPTIONAL, type1SP-Type2PS-null-r16 SEQUENCE { supportedCSI-RS-ResourceListAdd-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) } OPTIONAL, type1SP-eType2R1-null-r16 SEQUENCE { supportedCSI-RS-ResourceListAdd-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) } OPTIONAL, type1SP-eType2R2-null-r16 SEQUENCE { supportedCSI-RS-ResourceListAdd-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) } OPTIONAL, type1SP-eType2R1PS-null-r16 SEQUENCE { supportedCSI-RS-ResourceListAdd-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) } OPTIONAL, type1SP-eType2R2PS-null-r16 SEQUENCE { supportedCSI-RS-ResourceListAdd-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) } OPTIONAL, type1SP-Type2-Type2PS-r16 SEQUENCE { supportedCSI-RS-ResourceListAdd-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) } OPTIONAL, type1MP-Type2-null-r16 SEQUENCE { supportedCSI-RS-ResourceListAdd-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) } OPTIONAL, type1MP-Type2PS-null-r16 SEQUENCE { supportedCSI-RS-ResourceListAdd-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) } OPTIONAL, type1MP-eType2R1-null-r16 SEQUENCE { supportedCSI-RS-ResourceListAdd-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) } OPTIONAL, type1MP-eType2R2-null-r16 SEQUENCE { supportedCSI-RS-ResourceListAdd-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) } OPTIONAL, type1MP-eType2R1PS-null-r16 SEQUENCE { supportedCSI-RS-ResourceListAdd-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) } OPTIONAL, type1MP-eType2R2PS-null-r16 SEQUENCE { supportedCSI-RS-ResourceListAdd-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) } OPTIONAL, type1MP-Type2-Type2PS-r16 SEQUENCE { supportedCSI-RS-ResourceListAdd-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) } OPTIONAL } CodebookParametersfetype2-r17 ::= SEQUENCE { -- R1 23-9-1 Basic Features of Further Enhanced Port-Selection Type II Codebook (FeType-II) fetype2basic-r17 SEQUENCE (SIZE (1.. maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16), -- R1 23-9-2 Support of M=2 and R=1 for FeType-II fetype2R1-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r17)) OF INTEGER (0.. maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, -- R1 23-9-4 Support of R = 2 for FeType-II fetype2R2-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r17)) OF INTEGER (0.. maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, -- R1 23-9-3 Support of rank 3, 4 for FeType-II fetype2Rank3Rank4-r17 ENUMERATED {supported} OPTIONAL } CodebookComboParameterMixedType-r17 ::= SEQUENCE { -- R1 23-9-5 Active CSI-RS resources and ports for mixed codebook types in any slot type1SP-feType2PS-null-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, type1SP-feType2PS-M2R1-null-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, type1SP-feType2PS-M2R2-null-r1 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, type1SP-Type2-feType2-PS-M1-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, type1SP-Type2-feType2-PS-M2R1-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, type1SP-eType2R1-feType2-PS-M1-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, type1SP-eType2R1-feType2-PS-M2R1-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, type1MP-feType2PS-null-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, type1MP-feType2PS-M2R1-null-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, type1MP-feType2PS-M2R2-null-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, type1MP-Type2-feType2-PS-M1-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, type1MP-Type2-feType2-PS-M2R1-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, type1MP-eType2R1-feType2-PS-M1-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, type1MP-eType2R1-feType2-PS-M2R1-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL } CodebookComboParameterMultiTRP-r17::= SEQUENCE { -- R1 23-7-1b Active CSI-RS resources and ports in the presence of multi-TRP CSI -- {Codebook 2, Codebook 3} =(NULL, NULL} nCJT-null-null SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, nCJT1SP-null-null SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, -- {Codebook 2, Codebook 3} = {( {"Rel 16 combinations in FG 16-8"} nCJT-Type2-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, nCJT-Type2PS-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, nCJT-eType2R1-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, nCJT-eType2R2-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, nCJT-eType2R1PS-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, nCJT-eType2R2PS-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, nCJT-Type2-Type2PS-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, nCJT1SP-Type2-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, nCJT1SP-Type2PS-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, nCJT1SP-eType2R1-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, nCJT1SP-eType2R2-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, nCJT1SP-eType2R1PS-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, nCJT1SP-eType2R2PS-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, nCJT1SP-Type2-Type2PS-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, -- {Codebook 2, Codebook 3} = {"New Rel17 combinations in FG 23-9-5"} nCJT-feType2PS-null-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, nCJT-feType2PS-M2R1-null-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, nCJT-feType2PS-M2R2-null-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, nCJT-Type2-feType2-PS-M1-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, nCJT-Type2-feType2-PS-M2R1-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, nCJT-eType2R1-feType2-PS-M1-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, nCJT-eType2R1-feType2-PS-M2R1-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, nCJT1SP-feType2PS-null-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, nCJT1SP-feType2PS-M2R1-null-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, nCJT1SP-feType2PS-M2R2-null-r1 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, nCJT1SP-Type2-feType2-PS-M1-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, nCJT1SP-Type2-feType2-PS-M2R1-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, nCJT1SP-eType2R1-feType2-PS-M1-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, nCJT1SP-eType2R1-feType2-PS-M2R1-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL } CodebookParametersAdditionPerBC-r16::= SEQUENCE { -- R1 16-3a Regular eType 2 R=1 etype2R1-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, -- R1 16-3a-1 Regular eType 2 R=2 etype2R2-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, -- R1 16-3b Regular eType 2 R=1 PortSelection etype2R1-PortSelection-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, -- R1 16-3b-1 Regular eType 2 R=2 PortSelection etype2R2-PortSelection-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL } CodebookComboParametersAdditionPerBC-r16::= SEQUENCE { -- R1 16-8 Mixed codebook types type1SP-Type2-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, type1SP-Type2PS-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, type1SP-eType2R1-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, type1SP-eType2R2-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, type1SP-eType2R1PS-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, type1SP-eType2R2PS-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, type1SP-Type2-Type2PS-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, type1MP-Type2-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, type1MP-Type2PS-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, type1MP-eType2R1-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, type1MP-eType2R2-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, type1MP-eType2R1PS-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, type1MP-eType2R2PS-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, type1MP-Type2-Type2PS-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL } CodebookParametersfetype2PerBC-r17 ::= SEQUENCE { -- R1 23-9-1 Basic Features of Further Enhanced Port-Selection Type II Codebook (FeType-II) fetype2basic-r17 SEQUENCE (SIZE (1.. maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16), -- R1 23-9-2 Support of M=2 and R=1 for FeType-II fetype2R1-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r17)) OF INTEGER (0.. maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, -- R1 23-9-4 Support of R = 2 for FeType-II fetype2R2-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r17)) OF INTEGER (0.. maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL } CodebookComboParameterMixedTypePerBC-r17 ::= SEQUENCE { -- R1 23-9-5 Active CSI-RS resources and ports for mixed codebook types in any slot type1SP-feType2PS-null-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, type1SP-feType2PS-M2R1-null-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, type1SP-feType2PS-M2R2-null-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, type1SP-Type2-feType2-PS-M1-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, type1SP-Type2-feType2-PS-M2R1-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, type1SP-eType2R1-feType2-PS-M1-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, type1SP-eType2R1-feType2-PS-M2R1-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, type1MP-feType2PS-null-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, type1MP-feType2PS-M2R1-null-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, type1MP-feType2PS-M2R2-null-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, type1MP-Type2-feType2-PS-M1-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, type1MP-Type2-feType2-PS-M2R1-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, type1MP-eType2R1-feType2-PS-M1-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, type1MP-eType2R1-feType2-PS-M2R1-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL } CodebookComboParameterMultiTRP-PerBC-r17::= SEQUENCE { -- R1 23-7-1b Active CSI-RS resources and ports in the presence of multi-TRP CSI -- {Codebook 2, Codebook 3} =(NULL, NULL} nCJT-null-null SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, nCJT1SP-null-null SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, -- {Codebook 2, Codebook 3} = {( {"Rel 16 combinations in FG 16-8"} nCJT-Type2-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, nCJT-Type2PS-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, nCJT-eType2R1-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, nCJT-eType2R2-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, nCJT-eType2R1PS-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, nCJT-eType2R2PS-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, nCJT-Type2-Type2PS-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, nCJT1SP-Type2-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, nCJT1SP-Type2PS-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, nCJT1SP-eType2R1-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, nCJT1SP-eType2R2-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, nCJT1SP-eType2R1PS-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, nCJT1SP-eType2R2PS-null-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, nCJT1SP-Type2-Type2PS-r16 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, -- {Codebook 2, Codebook 3} = {"New Rel17 combinations in FG 23-9-5"} nCJT-feType2PS-null-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, nCJT-feType2PS-M2R1-null-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, nCJT-feType2PS-M2R2-null-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, nCJT-Type2-feType2-PS-M1-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, nCJT-Type2-feType2-PS-M2R1-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, nCJT-eType2R1-feType2-PS-M1-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, nCJT-eType2R1-feType2-PS-M2R1-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, nCJT1SP-feType2PS-null-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, nCJT1SP-feType2PS-M2R1-null-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, nCJT1SP-feType2PS-M2R2-null-r1 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, nCJT1SP-Type2-feType2-PS-M1-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, nCJT1SP-Type2-feType2-PS-M2R1-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, nCJT1SP-eType2R1-feType2-PS-M1-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, nCJT1SP-eType2R1-feType2-PS-M2R1-r17 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL } CodebookParametersetype2DopplerCSI-r18 ::= SEQUENCE { -- R1 40-3-2-1: Support of Rel-16-based doppler CSI eType2Doppler-r18 SEQUENCE { supportedCSI-RS-ResourceList-r18 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16), valueY-P-SP-CSI-RS-r18 INTEGER (1..3), valueY-A-CSI-RS-r18 INTEGER (1..3), scalingfactor-r18 ENUMERATED {n1, n2, n4} }, -- R1 40-3-2-1a: Support of Rel-16-based doppler measurement with N4>1 eType2DopplerN4-r18 SEQUENCE { supportedCSI-RS-ReportSettingList1-r18 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16), supportedCSI-RS-ReportSettingList2-r18 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) } OPTIONAL, -- R1 40-3-2-1a-1: DD unit size when A-CSI-RS is configured for CMR N4>1 ddUnitSize-A-CSI-RS-CMR-r18 ENUMERATED {supported} OPTIONAL, -- R1 40-3-2-2: Support R=2 for Rel-16-based doppler codebook eType2DopplerR2-r18 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, -- R1 40-3-2-3: Support X=1 based on first and last slot of WCSI, for Rel-16-based doppler codebook eType2DopplerX1-r18 ENUMERATED {supported} OPTIONAL, -- R1 40-3-2-3a: Support X=2 CQI based on 2 slots for Rel-16-based doppler codebook eType2DopplerX2-r18 ENUMERATED {supported} OPTIONAL, --R1 40-3-2-7: support of l = (n – nCSI,ref ) for CSI reference slot for Rel-16 based doppler codebook eType2DopplerL-N4D1-r18 ENUMERATED {supported} OPTIONAL } CodebookParametersfetype2DopplerCSI-r18 ::= SEQUENCE { -- R1 40-3-2-4: Support of Rel-17-based doppler CSI feType2Doppler-r18 SEQUENCE { supportedCSI-RS-ResourceList-r18 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16), valueY-A-CSI-RS-r18 INTEGER (1..3), scalingfactor-r18 ENUMERATED {n1, n2, n4} }, -- R1 40-3-2-5: Support of M=2 and R=1 for Rel-17-based doppler codebook feType2DopplerM2R1-r18 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, -- R1 40-3-2-6: Support R=2 for Rel-17-based doppler codebook feType2DopplerR2-r18 SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesExt-r16)) OF INTEGER (0..maxNrofCSI-RS-ResourcesAlt-1-r16) OPTIONAL, --R1 40-3-2-7a: Support of l = (n – nCSI,ref ) for CSI reference slot for Rel-17 based doppler codebook feType2DopplerL-N4D1-r18 ENUMERATED {supported} OPTIONAL } CodebookVariantsList-r16 ::= SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesAlt-r16)) OF SupportedCSI-RS-Resource SupportedCSI-RS-Resource ::= SEQUENCE { maxNumberTxPortsPerResource ENUMERATED {p2, p4, p8, p12, p16, p24, p32}, maxNumberResourcesPerBand INTEGER (1..64), totalNumberTxPortsPerBand INTEGER (2..256) } SupportedCSI-RS-ReportSettingList-r18 ::= SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesAlt-r16)) OF SupportedCSI-RS-ReportSetting-r18 SupportedCSI-RS-ReportSetting-r18 ::= SEQUENCE { maxN4-r18 ENUMERATED {n1, n2, n4, n8}, maxNumberTxPortsPerResource-r18 ENUMERATED {p2, p4, p8, p12, p16, p24, p32}, maxNumberResourcesPerBand-r18 INTEGER (1..64), totalNumberTxPortsPerBand-r18 INTEGER (2..256) } -- TAG-CODEBOOKPARAMETERS-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
1,460 | 13.13 IMEI based identity | The IMEI based identity shall take the form of a SIP URI (see IETF RFC 3261 [26]). The IMEI based identity is included in P-Preferred-Identity header field of SIP INVITE request by the UE and used in cases of unauthenticated emergency sessions as specified in clause 5.1.6.8.2 of 3GPP TS 24.229[ IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 ] [81]. A SIP URI for an IMEI based identity shall take the form "sip:user@domain" where by the user part shall contain the IMEI. The IMEI shall be encoded according to ABNF of imeival as defined in IETF RFC 7254 [79]. The domain part shall contain the home network domain named derived as specified in clause 13.2. An example for the case when the UE has a home network domain name of operator.com is: EXAMPLE 1: "sip:[email protected]" An example for 3GPP systems, when the UE with no ISIM application has a home network domain name of ims.mnc015.mcc234.3gppnetwork.org derived from the same example IMSI from clause 13.2 is: EXAMPLE 2: "sip:[email protected]" | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 13.13 |
1,461 | 4.5.5 Exception handling and avoiding double barring | Access attempts are allowed to proceed without further access control checking in order to avoid double barring for any service request or registration procedure initiated for the purpose of NAS signalling connection recovery or following a fallback indication from the lower layers (see subclauses 5.3.1.2 and 5.3.1.4). NOTE 1: The case of NAS signalling connection recovery also includes the cases where the UE was in S1 mode when the RRC connection failure occurred. For any service request or registration procedure of this kind the UE determines an access category as specified in subclause 4.5.1 and 4.5.2 or 4.5.2A, unless a different access category is specified in the rest of the present subclause. NOTE 2: Although the access control checking is skipped, the access category is determined for the specific access attempt in order to derive an RRC establishment cause. There are several services or an MO IMS registration related signalling for which the NAS needs to be informed when the service starts and stops, - because, while the service is ongoing or the MO IMS registration related signalling is ongoing, the mapping of other access attempts to a specific access category can be affected; and - in order to avoid double barring at the start of these services or at the start of the MO IMS registration related signalling. These services are: a) emergency service; b) MMTEL voice; c) MMTEL video; d) SMSoIP; e) SMS over NAS; f) 5GC-MO-LR procedure; g) UE-requested policy provisioning procedure for V2XP, ProSeP or both; and h) CIoT user data transfer over the control plane. The UE considers an emergency service a) as started when 5GMM receives a request from upper layers to register for emergency services or to establish a PDU session with request type = "initial emergency request" or "existing emergency PDU session". It considers the emergency service as stopped when this PDU session is released. In addition, the UE considers an emergency service a) as started when the 5GMM receives a request from the upper layers to perform emergency services fallback and performs emergency services fallback as specified in subclause 4.13.4.2 of 3GPP TS 23.502[ Procedures for the 5G System (5GS) ] [9]. In this case, the UE considers the emergency service as stopped when: - the emergency PDU session established during the emergency services fallback is released if the UE has moved to an E-UTRA cell connected to 5GCN; or - the service request procedure involved in the emergency services fallback is completed otherwise. While an emergency service a) is ongoing, any access attempt triggered by the initiation of a registration, de-registration or service request procedure or by an uplink user data packet to be sent for an emergency PDU session with suspended user-plane resources is mapped to access category 2 = emergency. Once the emergency service has successfully passed access control, then as long as the service is ongoing, the following access attempts are allowed to proceed without further access control checking in order to avoid double barring: - any service request procedure related to the PDU session associated with request type = "initial emergency request" or "existing emergency PDU session"; and - any uplink user data packet to be sent for a PDU session with suspended user-plane resources associated with request type = "initial emergency request" or "existing emergency PDU session". NOTE 3: Although the access control checking is skipped, the mapping is performed in order to derive an RRC establishment cause. For services b) to h) the 5GMM receives explicit start and stop indications from the upper layers. For the case of handover of ongoing services b) to d) from non-3GPP access, the 5GMM receives an additional explicit handover of ongoing service from non-3GPP access indication from the upper layers. The 5GMM may receive an additional explicit "call-pull-initiated" indication from the upper layers (see 3GPP TS 24.174[ Support of multi-device and multi-identity in the IP Multimedia Subsystem (IMS); Stage 3 ] [13D]). Once the service has successfully passed access control, then as long as the service is ongoing, the following access attempts are allowed to proceed without further access control checking in order to avoid double barring: - for services b), c) and d): 1) any service request procedure related to the PDU session established for DNN = "IMS" except between receiving from the lower layers an indication that access barring is applicable for all access categories except categories 0 and 2, or access barring is applicable for all access categories except category 0, and receiving from the lower layers an indication that the barring is alleviated for the access category determined for the access attempt; 2) any uplink user data packet to be sent for a PDU session with suspended user-plane resources established for DNN = "IMS" except between receiving from the lower layers an indication that access barring is applicable for all access categories except categories 0 and 2, or access barring is applicable for all access categories except category 0, and receiving from the lower layers an indication that the barring is alleviated for the access category determined for the access attempt; and 3) any start of the MO IMS registration related signalling; - for service d), if the upper layers have indicated a DNN used for SMSoIP and the indicated DNN used for SMSoIP is different from "IMS": 1) any service request procedure related to the PDU session established for the DNN used for SMSoIP except between receiving from the lower layers an indication that access barring is applicable for all access categories except categories 0 and 2, or access barring is applicable for all access categories except category 0, and receiving from the lower layers an indication that the barring is alleviated for access category 6; and 2) any uplink user data packet to be sent for a PDU session with suspended user-plane resources established for the DNN used for SMSoIP except between receiving from the lower layers an indication that access barring is applicable for all access categories except categories 0 and 2, or access barring is applicable for all access category except category 0, and receiving from the lower layers an indication that the barring is alleviated for access category 6. For the MO IMS registration related signalling, the 5GMM receives explicit start and stop indications from the upper layers. Once the MO IMS registration related signalling has successfully passed access control, then as long as the MO IMS registration related signalling is ongoing, the following access attempts are allowed to proceed without further access control checking in order to avoid double barring: 1) any service request procedure related to the PDU session established for DNN = "IMS" and for the DNN used for SMSoIP, if the upper layers have indicated a DNN used for SMSoIP and the indicated DNN used for SMSoIP is different from "IMS", except between receiving from the lower layers an indication that access barring is applicable for all access categories except categories 0 and 2, or access barring is applicable for all access categories except category 0 and receiving from the lower layers an indication that the barring is alleviated for the access category determined for the access attempt; and 2) any uplink user data packet to be sent for a PDU session with suspended user-plane resources established for DNN = "IMS" and for the DNN used for SMSoIP except between receiving from the lower layers an indication that access barring is applicable for all access categories except categories 0 and 2, or access barring is applicable for all access categories except category 0 and receiving from the lower layers an indication that the barring is alleviated for the access category determined for the access attempt; While an MMTEL voice call is ongoing: - any service request procedure related to the PDU session established for DNN = "IMS" is mapped to access category 4; - any uplink user data packet to be sent for a PDU session with suspended user-plane resources established for DNN = "IMS" is mapped to access category 4; and - any: 1) service request procedure; or 2) registration procedure; initiated in 5GMM-IDLE mode or 5GMM-IDLE mode with suspend indication for the purpose of NAS signalling connection recovery or following a fallback indication from the lower layers (see subclause 5.3.1.2 and 5.3.1.4) is mapped to access category 4. While an MMTEL video call is ongoing and no MMTEL voice call is ongoing: - any service request procedure related to the PDU session established for DNN = "IMS" is mapped to access category 5; - any uplink user data packet to be sent for a PDU session with suspended user-plane resources established for DNN = "IMS" is mapped to access category 5; and - any: 1) service request procedure; or 2) registration procedure; initiated in 5GMM-IDLE mode or 5GMM-IDLE mode with suspend indication for the purpose of NAS signalling connection recovery or following a fallback indication from the lower layers (see subclause 5.3.1.2 and 5.3.1.4) is mapped to access category 5. While an SMSoIP is ongoing, no MMTEL video call is ongoing and no MMTEL voice call is ongoing: - any service request procedure related to the PDU session established: 1) for DNN = "IMS"; or 2) for the DNN used for SMSoIP, if the upper layers have indicated a DNN used for SMSoIP and the indicated DNN used for SMSoIP is different from "IMS"; is mapped to access category 6; and - any uplink user data packet to be sent for a PDU session with suspended user-plane resources established: 1) for DNN = "IMS"; or 2) for the DNN used for SMSoIP, if the upper layers have indicated a DNN used for SMSoIP and the indicated DNN used for SMSoIP is different from "IMS"; is mapped to access category 6; and - any: 1) service request procedure; or 2) registration procedure; initiated in 5GMM-IDLE mode or 5GMM-IDLE mode with suspend indication for the purpose of NAS signalling connection recovery or following a fallback indication from the lower layers (see subclause 5.3.1.2 and 5.3.1.4) is mapped to access category 6. While an SMS over NAS is ongoing, no SMSoIP is ongoing, no MMTEL video call is ongoing and no MMTEL voice call is ongoing: - any: 1) service request procedure; or 2) registration procedure; initiated in 5GMM-IDLE mode or 5GMM-IDLE mode with suspend indication for the purpose of NAS signalling connection recovery or following a fallback indication from the lower layers (see subclause 5.3.1.2 and 5.3.1.4) is mapped to access category 6. While an MO IMS registration related signalling is ongoing, no SMSoIP is ongoing, no MMTEL video call is ongoing and no MMTEL voice call is ongoing: - any service request procedure related to the PDU session established: 1) for DNN = "IMS"; and 2) for the DNN used for SMSoIP, if the upper layers have indicated a DNN used for SMSoIP and the indicated DNN used for SMSoIP is different from "IMS"; is mapped to access category 9; and - any uplink user data packet to be sent for a PDU session with suspended user-plane resources established: 1) for DNN = "IMS"; and 2) for the DNN used for SMSoIP, if the upper layers have indicated a DNN used for SMSoIP and the indicated DNN used for SMSoIP is different from "IMS"; is mapped to access category 9; and - if no SMS over NAS is ongoing, any: 1) service request procedure; or 2) registration procedure; initiated in 5GMM-IDLE mode for the purpose of NAS signalling connection recovery or following a fallback indication from the lower layers (see subclause 5.3.1.2 and 5.3.1.4) is mapped to access category 9. While a 5GC-MO-LR procedure is ongoing, no SMS over NAS is ongoing, no SMSoIP is ongoing, no MO IMS registration related signalling is ongoing, no MMTEL video call is ongoing, and no MMTEL voice call is ongoing: - any: 1) service request procedure; or 2) registration procedure; initiated in 5GMM-IDLE mode or 5GMM-IDLE mode with suspend indication for the purpose of NAS signalling connection recovery or following a fallback indication from the lower layers (see subclauses 5.3.1.2 and 5.3.1.4) is mapped to access category 3. While a UE-requested policy provisioning procedure for V2XP, ProSeP or both (see 3GPP TS 24.587[ Vehicle-to-Everything (V2X) services in 5G System (5GS); Stage 3 ] [19B] and 3GPP TS 24.554[ Proximity-services (ProSe) in 5G System (5GS) protocol aspects; Stage 3 ] [19E]), no 5GC-MO-LR procedure is ongoing, no SMS over NAS is ongoing, no SMSoIP is ongoing, no MMTEL video call is ongoing, and no MMTEL voice call is ongoing: - any: 1) service request procedure; or 2) registration procedure; initiated in 5GMM-IDLE mode for the purpose of NAS signalling connection recovery or following a fallback indication from the lower layers (see subclauses 5.3.1.2 and 5.3.1.4) is mapped to access category 3. While CIoT user data transfer over the control plane is ongoing, no 5GC-MO-LR procedure is ongoing, no SMS over NAS is ongoing, no SMSoIP is ongoing, no MMTEL video call is ongoing, and no MMTEL voice call is ongoing, any service request procedure initiated in 5GMM-IDLE mode following a fallback indication from the lower layers (see subclause 5.3.1.4) is mapped to access category 7. NOTE 3: Although the access control checking is skipped, the mapping is performed in order to derive an RRC establishment cause. If an access category is determined and the access control checking is skipped, the NAS shall determine the RRC establishment cause from one or more determined access identities and the access category as specified in subclause 4.5.6, the NAS shall initiate the procedure to send the initial NAS message for the access attempt and shall provide the RRC establishment cause to lower layers. If the UE receives from the lower layers an indication that access barring is applicable for all access categories except categories 0 and 2, or access barring is applicable for all access categories except category 0: a) if an MMTEL voice call or MMTEL video call is ongoing: 1) if the UE is operating in the single-registration mode and the UE's usage setting is "voice centric", the UE may attempt to select an E-UTRA cell connected to EPC. If the UE finds a suitable E-UTRA cell connected to EPC, it then proceeds with the appropriate EMM specific procedures and, if necessary, ESM procedures to make a PDN connection providing access to IMS available; see subclause 4.8.2 and 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15]; and 2) if the UE is operating in the dual-registration mode, the UE may proceed in S1 mode with the appropriate EMM specific procedures and ESM procedures to make a PDN connection providing access to IMS available; see subclause 4.8.3 and 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15]; and b) if SMSoIP is ongoing or an MO IMS registration related signalling is ongoing: 1) if the UE is operating in the single-registration mode, the UE may attempt to select an E-UTRA cell connected to EPC. If the UE finds a suitable E-UTRA cell connected to EPC, it then proceeds with the appropriate EMM specific procedures and, if necessary, ESM procedures to make a PDN connection providing access to IMS available; see subclause 4.8.2 and 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15]; and 2) if the UE is operating in the dual-registration mode, the UE may proceed in S1 mode with the appropriate EMM specific procedures and ESM procedures to make a PDN connection providing access to IMS available; see subclause 4.8.3 and 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15]. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.5.5 |
1,462 | 8.2.2.4.1B Enhanced Performance Requirement Type A – Single-Layer Spatial Multiplexing 2 Tx Antenna Port with TM4 interference model | The requirements are specified in Table 8.2.2.4.1B-2, with the addition of the parameters in Table 8.2.2.4.1B-1 and the downlink physical channel setup according to Annex C.3.2. The purpose of these tests is to verify the closed loop rank-one performance with wideband precoding with two transmit antennas when the PDSCH transmission in the serving cell is interfered by PDSCH of two dominant interfering cells applying transmission mode 4 interference model defined in clause B.5.3. In Table 8.2.2.4.1B-1, Cell 1 is the serving cell, and Cell 2, 3 are interfering cells. The downlink physical channel setup is according to Annex C.3.2 for each of Cell 1, Cell 2 and Cell 3, respectively. Table 8.2.2.4.1B-1: Test Parameters for Single-Layer Spatial Multiplexing (FRC) with TM4 interference model Table 8.2.2.4.1B-2: Enhanced Performance Requirement Type A, Single-Layer Spatial Multiplexing (FRC) with TM4 interference model | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.2.2.4.1B |
1,463 | – UTRA-FDD-Q-OffsetRange | The IE UTRA-FDD-Q-OffsetRange is used to indicate a frequency specific offset to be applied when evaluating triggering conditions for measurement reporting. The value is in dB. Value dB-24 corresponds to -24 dB, value dB-22 corresponds to -22 dB and so on. UTRA-FDD-Q-OffsetRange information element -- ASN1START -- TAG-UTRA-FDD-Q-OFFSETRANGE-START UTRA-FDD-Q-OffsetRange-r16 ::= ENUMERATED { dB-24, dB-22, dB-20, dB-18, dB-16, dB-14, dB-12, dB-10, dB-8, dB-6, dB-5, dB-4, dB-3, dB-2, dB-1, dB0, dB1, dB2, dB3, dB4, dB5, dB6, dB8, dB10, dB12, dB14, dB16, dB18, dB20, dB22, dB24} -- TAG-UTRA-FDD-Q-OFFSETRANGE-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
1,464 | 28.3.2.3 PLMN level and Home NF Repository Function (NRF) FQDN 28.3.2.3.1 General | When an NF is instantiated, it may register with a PLMN level NF Repository Function (NRF). It may then discover other NF instance(s) in the 5GC by querying the PLMN level NRF. The IP address of the PLMN level NRF can be provisioned into the NF, or the NF can be pre-configured with the FQDN of the PLMN level NRF. If the PLMN level NRF addresses and FDQN are not provisioned into the NF, the NF self-constructs the PLMN level NRF FQDN as per the format specified in clause 28.3.2.3.2. For NF discovery across PLMNs, the NRF (e.g vNRF) shall self-construct the PLMN level NRF FQDN of the target PLMN (e.g hNRF) as per the format specified in clause 28.3.2.3.2, and the hNRF URI as per the format specified in subsclause 28.3.2.3.3, if the NRF has not obtained the NRF FQDN of the target PLMN. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 28.3.2.3 |
1,465 | 6.2.1 Principles of PTI handling for 5GSM procedures | When the UE or the network initiates a transaction related procedure (i.e. a procedure consisting of more than one message and the messages are related), it shall include a valid PTI value in the message header of the request message or of the command message. If a response message is sent as result of a received request message or a received command message, the sending entity shall include in the response message the PTI value received within the request message or within the command message (see examples in figure 6.2.1.1, figure 6.2.1.2, and figure 6.2.1.3). If a command message is sent as result of a received request message, the sending entity shall include in the command message the PTI value received with the request message (see examples in figure 6.2.1.3). If a command message is not sent as result of a received request message, the sending entity shall include in the command message the PTI value set to "no procedure transaction identity assigned" (see examples in figure 6.2.1.4). Figure 6.2.1.1: UE-requested transaction related procedure accepted by the network Figure 6.2.1.2: UE-requested transaction related procedure rejected by the network Figure 6.2.1.3: UE-requested transaction related procedure triggering a network-requested transaction related procedure Figure 6.2.1.4: network-requested transaction related procedure not triggered by a UE-requested transaction related procedure | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.2.1 |
1,466 | 4.1.2.2 The update Status | In parallel with the sublayer states described in subclause 4.1.2.1 and which control the MM sublayer protocol, an update status exists. The update status pertains to a specific subscriber embodied by a SIM/USIM. This status is defined even when the subscriber is not activated (SIM/USIM removed or connected to a switched-off ME). It is stored in a non volatile memory in the SIM/USIM. The update status is changed only as a result of a location updating procedure attempt (with the exception of an authentication failure and of some cases of CM service rejection). In some cases, the update status is changed as a result of a GPRS attach, GPRS routing area update, service request network initiated GPRS detach procedure or due to change in LAI while timer T3246 running. U1 UPDATED The last location updating attempt was successful (correct procedure outcome, and the answer was acceptance from the network). With this status, the SIM/USIM contains also the LAI of the LA where the subscriber is registered, and possibly valid TMSI, GSM ciphering key, UMTS integrity key, UMTS ciphering key and ciphering key sequence number. Furthermore, if the ME supports any A5 ciphering algorithm that requires a 128-bit ciphering key and a USIM is in use, then the ME may contain a valid GSM Kc128. The "Location update status" stored on the SIM/USIM shall be "updated". U2 NOT UPDATED The last location updating attempt made failed procedurally (no significant answer was received from the network, including the cases of failures or congestion inside the network). For this status, the SIM/USIM can contain a valid LAI of the location area to which the subscriber was registered, and possibly also a valid TMSI, GSM ciphering key, UMTS integrity key, UMTS ciphering key and ciphering key sequence number. For compatibility reasons, all these fields shall be set to the "deleted" value if the LAI is deleted. However the presence of other values shall not be considered an error by the mobile station. Furthermore, if the ME supports any A5 ciphering algorithm that requires a 128-bit ciphering key and a USIM is in use, then the ME shall delete the GSM Kc128 stored if the LAI is deleted. The "Location update status" stored on the SIM/USIM shall be "not updated". U3 ROAMING NOT ALLOWED The last location updating attempt run correctly, but the answer from the network was negative (because of roaming or subscription restrictions). For this status, the SIM/USIM can contain a valid LAI, TMSI, GSM ciphering key, UMTS integrity key, UMTS ciphering key or ciphering key sequence number. For compatibility reasons, all these fields shall be set to the "deleted" value if the LAI is deleted. However the presence of other values shall not be considered an error by the mobile station. Furthermore, if the ME supports any A5 ciphering algorithm that requires a 128-bit ciphering key and a USIM is in use, then the ME shall delete the GSM Kc128 stored if the LAI is deleted. The "Location update status" stored on the SIM/USIM shall be "Location Area not allowed". U4 UPDATING DISABLED Location updating has been disabled. For this status, the SIM/USIM does not contain any valid LAI, TMSI, GSM ciphering key, UMTS integrity key, UMTS ciphering key or ciphering key sequence number. For compatibility reasons, all these fields shall be set to the "deleted" value at the moment the status is set to eCALL INACTIVE. However the presence of other values shall not be considered an error by the mobile station. Furthermore, if the ME supports any A5 ciphering algorithm that requires a 128-bit ciphering key and a USIM is in use, then the ME shall delete the GSM Kc128 stored at the moment the status is set to eCALL INACTIVE. The "Location update status" stored on the SIM/USIM shall be "not updated". | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.1.2.2 |
1,467 | 28.5.2 Telescopic FQDN | The FQDN of the NF services or the authority part of URIs in another PLMN, may be appended with the PLMN Network Domain of the request initiating PLMN, as the trailing part to form a Telescopic FQDN as specified in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [124]. The Telescopic FQDN shall be constructed as follows: <Label representing FQDN from other PLMN>.<FQDN of the SEPP in the request initiating PLMN>, where: - FQDN from other PLMN is the FQDN of the other PLMN NF (for e.g. returned in the NF Discovery Response) or the authority part of URIs from other PLMN, which may be rewritten by the other PLMN SEPP for topology hiding. The request initiating PLMN SEPP shall replace the other PLMN FQDN with a label; NOTE 1: How a SEPP constructs the label to replace the other PLMN FQDN is implementation specific. The label replacement is required in order to avoid multiple subdomains in the FQDN since the SEPP presents wildcard certificates on behalf of the other PLMN and only single level subdomain is allowed in a wildcard certificate as per IETF RFC 2818 [127]. NOTE 2: FQDN from other PLMN includes the network domain of the other PLMN. - FQDN of the SEPP in the request initiating PLMN is the identifier of the SEPP in the request initaiting PLMN (e.g. VPLMN). | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 28.5.2 |
1,468 | 11.2.3 Timers of GPRS session management | Table 11.2c/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : GPRS session management timers - MS side NOTE 1: Typically, the procedures are aborted on the fifth expiry of the relevant timer. Exceptions are described in the corresponding procedure description. NOTE 2: The back-off timer is used to describe a logical model of the required MS behaviour. This model does not imply any specific implementation, e.g. as a timer or timestamp. NOTE 3: Reference to back-off timer in this section can either refer to use of timer T3396 or to use of a different packet system specific timer within the MS. Whether the MS uses T3396 as a back-off timer or it uses different packet system specific timers as back-off timers is left up to MS implementation. Table 11.2d/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : GPRS session management timers - network side NOTE 4: Typically, the procedures are aborted on the fifth expiry of the relevant timer. Exceptions are described in the corresponding procedure description. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 11.2.3 |
1,469 | 8.6 Access Point Name (APN) | Access Point Name (APN) is transferred via GTP tunnels. The sending entity copies the value part of the APN into the Value field of the APN IE. Figure 8.6-1: Access Point Name (APN) The encoding the APN field follows 3GPP TS 23.003[ Numbering, addressing and identification ] [2] clause 9.1. The content of the APN field shall be the full APN with both the APN Network Identifier and APN Operator Identifier being present as specified in 3GPP TS 23.003[ Numbering, addressing and identification ] [2] clauses 9.1.1 and 9.1.2, 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [35] Annex A and 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [3] clauses 4.3.8.1. NOTE: The APN field is not encoded as a dotted string as commonly used in documentation. | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 8.6 |
1,470 | 6.1.2.2.8 MBMS-ACTIVE | This state indicates that the MBMS context is active. Figure 6.2/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Session management states for PDP context handling on the network side (overview) It shall be noted, that figure 6.2/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] applies to both the PDP context activation procedure and the secondary PDP context activation procedure, though the distinction in messages regarding the activation of PDP contexts is not shown here for simplicity. Figure 6.2a/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Session management states for MBMS context handling on the network side (overview) | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.1.2.2.8 |
1,471 | 5.5.1 Description | There is a requirement to provide separation between UAVs. A collision incident can cause property damage, interference to a UAS’s objectives, and may pose a safety threat. Therefore, regardless of network conditions, a service to ensure separation between UAVs is desirable. When in visual line-of-sight to the UAV operator, separation can be provided manually through command & control mechanisms. The UAV operator is responsible to maintain well-clear separation from other aircraft, buildings, and other obstacles. When beyond visual line-of-sight, the UAV operator may be offered video or instrumental feedback to manually maintain separation. In addition, a UTM may offer a separation service as documented in clause 5.2 of the present document. When out of coverage and out of visual line-of-sight, there can be no manual input and there can be no UTM-offered separation service. In this scenario, a distributed separation service is desirable. | 3GPP TS 22.825 | Study on Remote Identification of Unmanned Aerial Systems (UAS) | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 5.5.1 |
1,472 | 6.2.11 UDR | The Unified Data Repository (UDR) supports the following functionality: - Storage and retrieval of subscription data by the UDM. - Storage and retrieval of policy data by the PCF. - Storage and retrieval of structured data for exposure. - Application data (including Packet Flow Descriptions (PFDs) for application detection, AF request information for multiple UEs, 5G-VN group information for 5G-VN management). - Storage and retrieval of NF Group ID corresponding to subscriber identifier (e.g. IMPI, IMPU, SUPI). The Unified Data Repository is located in the same PLMN as the NF service consumers storing in and retrieving data from it using Nudr. Nudr is an intra-PLMN interface. NOTE 1: Deployments can choose to collocate UDR with UDSF. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 6.2.11 |
1,473 | 6.1.3.23 GNSS Validity Duration Report MAC Control Element | The GNSS Validity Duration Report MAC Control Element is identified by a MAC PDU subheader with LCID as specified in table 6.2.1-2. It has a fixed size and consists of a single octet defined as follows (Figure 6.1.3.23-1): - R: Reserved bit, set to 0; - GNSS Validity Duration: the field corresponds to the remaining GNSS validity duration defined in the TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8]. Figure 6.1.3.23-1: GNSS Validity Duration Report MAC control element | 3GPP TS 36.321 | Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification | RAN2 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.1.3.23 |
1,474 | D.1.1 Overview | The UE provides the PCF with a list of one or more stored UE policy section identifiers (UPSIs) during the UE-initiated UE state indication procedure. The UPSI is composed of two parts: a) a PLMN ID part containing: 1) the PLMN ID for the PLMN; or 2) the PLMN ID part of the SNPN identity for the SNPN; of the PCF which provides the UE policies; and b) a UE policy section code (UPSC) containing a value assigned by the PCF. During the UE-initiated UE state indication procedure, the UE also provides the PCF with the UE policy related capabilities such as the UE's support for ANDSP, the UE's support for URSP provisioning in EPS, and the UE's OS Id. During the network-requested UE policy management procedure, the PCF provides the UE with one or more UE policy sections containing UE policies. The UE processes the received UE policy sections, each identified by the UPSI, received from the PCF and informs the PCF of the result. In the present annex, the condition that the PLMN ID part of the UPSI is referring to the HPLMN shall be considered as fulfilled only if the PLMN ID is equal to the HPLMN code derived from the IMSI. NOTE: This is also applicable if the UE has a non-empty EHPLMN list, even if the EHPLMN list does not include the PLMN ID derived from the IMSI. The UE can also request the PCF to provide V2XP as specified in 3GPP TS 24.587[ Vehicle-to-Everything (V2X) services in 5G System (5GS); Stage 3 ] [19B]. The UE can also request the PCF to provide ProSeP as specified in 3GPP TS 24.554[ Proximity-services (ProSe) in 5G System (5GS) protocol aspects; Stage 3 ] [19E]. The UE can also request the PCF to provide A2XP as specified in 3GPP TS 24.577[ Aircraft-to-Everything (A2X) services in 5G System (5GS) protocol aspects; Stage 3 ] [60]. The UE can also request the PCF to provide RSLPP as specified in 3GPP TS 24.514[ Ranging based services and sidelink positioning in 5G system(5GS); Stage 3 ] [62]. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | D.1.1 |
1,475 | 5.8.2.19.2 Buffering at UPF | When the SMF decided to activate buffering in UPF, the SMF shall inform the UPF to start buffering packets for this PDU Session. The SMF provides instructions to the UPF for at least the following behaviour: - buffer downlink packets with the following additional options: - reporting the arrival of first downlink packet (for a QoS Flow or a service data flow), and/or - reporting the first discarded downlink packet (for a service data flow), or - drop downlink packets with the following additional options: - reporting the first discarded downlink packet (for a service data flow). - buffer uplink packets. When the SMF instructs the UPF for a service data flow to buffer downlink packets and to report the first discarded downlink packet, the SMF shall also instruct the UPF to report the arrival of the first downlink packet for this service data flow to enable the SMF check if this is also the first report for the QoS Flow (as described below). Buffering in the UPF may be configured based on timers or the amount of downlink data to be buffered. The SMF decides whether buffering timers or amount of downlink data are handled by the UPF or SMF. After starting buffering, when the first downlink packet (of a QoS Flow or a service data flow) arrives, UPF shall inform the SMF if it is setup to report. UPF sends a Downlink Data Report to the SMF via N4 unless specified otherwise and indicates the PDR by which the downlink packet was received. If the SMF receives a Downlink Data Report for a service data flow, the SMF shall also check if this is the first report for the QoS Flow corresponding to the PDR. If so, the SMF shall also proceed as described in clause 5.4.3.1. After starting buffering, when the first downlink packet (of a service data flow) in a configured period of time that has been buffered is discarded by the UPF because the configured buffering time or amount of downlink data to be buffered is exceeded, the UPF shall inform the SMF if it is setup to report. UPF sends a Downlink Data Report to the SMF via N4 and indicates the PDR by which the discarded downlink packet was received. A new report is sent if the SMF terminates and subsequently re-activates the buffering action at the UPF and the UPF again receives downlink packets. NOTE: For the notification about the downlink data delivery status "buffered" or "discarded" related to packets from a particular AF as part of the Nsmf_EventExposure service, it is expected that a PDR with a traffic filter identifying that AF as source and a Forwarding Action rule with action "buffer" is installed. When the UP connection of the PDU Session is activated, the SMF updates the UPF of the change in buffering state. The buffered downlink packets, if any, are then forwarded to the (R)AN by the UPF. If the UP connection of the PDU Session has been deactivated for a long time, the SMF may indicate the UPF to stop buffering for this PDU Session. The SMF may indicate to the UPF to start or stop the buffering of uplink packets of an application associated to the PCC rule as described in clause 6.3.5 of TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [130]. When the buffering of uplink packets is stopped the UPF shall forward all buffered uplink packets before it forwards any new uplink packets. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.8.2.19.2 |
1,476 | 24.3A ProSe Application Code Prefix | The ProSe Application Code Prefix as described in 3GPP TS 23.303[ Proximity-based services (ProSe); Stage 2 ] [103] is to be used with a ProSe Application Code Suffix. The ProSe Application Code Prefix has the same composition and format as the ProSe Application Code, with the following exceptions: - The temporary identity part of the ProSe Application Code Prefix is of variable length. The length of the temporary identity part shall be incremented in multiple of 8, with a minimum size of 8 bits and a maximum size of 152 bits. - The sum of the length of the ProSe Application Code Prefix and the length of the ProSe Application Code Suffix shall be 184 bits. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 24.3A |
1,477 | 5.20 External Exposure of Network Capability | The Network Exposure Function (NEF) supports external exposure of capabilities of network functions. External exposure can be categorized as Monitoring capability, Provisioning capability, Policy/Charging capability, Analytics reporting capability and Member UE selection capability. The Monitoring capability is for monitoring of specific event for UE in 5G System and making such monitoring events information available for external exposure via the NEF. The Provisioning capability is for allowing external party to provision of information which can be used for the UE in 5G System. The Policy/Charging capability is for handling access and mobility management, QoS and charging policies for the UE based on the request from external party. The Analytics reporting capability is for allowing an external party to fetch or subscribe/unsubscribe to analytics information generated by 5G System (this is further defined in TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [86]). The Member UE selection capability is for allowing an external party to acquire one or more list(s) of candidate UE(s) (among the list of target member UE(s) provided by the AF) and additional information that is based on the assistance information generated by 5G System based on some defined filtering criteria, the details are explained in clause 4.15.13 in TS 23.502[ Procedures for the 5G System (5GS) ] [3]. Monitoring capability is comprised of means that allow the identification of the 5G network function suitable for configuring the specific monitoring events, detect the monitoring event, and report the monitoring event to the authorised external party. Monitoring capability can be used for exposing UE's mobility management context such as UE location, reachability, roaming status, and loss of connectivity. Monitoring capability can also be used for exposing QoS monitoring result. AMF stores URRP-AMF information in the MM context to determine the NFs that are authorised to receive direct notifications from the AMF. UDM stores URRP-AMF information locally to determine authorised monitoring requests when forwarding indirect notifications. The Monitoring capability also allows AF to subscribe to the group status changes for a group, either a 5G VN group as described in clause 5.29.2, as well as a group configured by OA&M. In this case the AF is notified if the group member list is updated or a group member is no longer subscribed to the group. Provisioning capability allows an external party to provision the Expected UE Behaviour or the 5G-VN group information or DNN and S-NSSAI specific Group Parameters or ECS Address Configuration Information or service specific information to 5G NF via the NEF. The provisioning comprises of the authorisation of the provisioning external third party, receiving the provisioned external information via the NEF, storing the information, and distributing that information among those NFs that use it. The externally provisioned data can be consumed by different NFs, depending on the data. In the case of provisioning the Expected UE Behaviour, the externally provisioned information which is defined as the Expected UE Behaviour parameters in clause 4.15.6.3 of TS 23.502[ Procedures for the 5G System (5GS) ] [3] or Network Control parameter in clause 4.15.6.3a of TS 23.502[ Procedures for the 5G System (5GS) ] [3] consists of information on expected UE movement, Expected UE Behaviour parameters or expected Network Configuration parameter. The provisioned Expected UE Behaviour parameters may be used for the setting of mobility management or session management parameters of the UE. In the case of provisioning the 5G-VN group information the externally provisioned information is defined as the 5G-VN group parameters in clause 4.15.6.7 of TS 23.502[ Procedures for the 5G System (5GS) ] [3] and it consists of some information on the 5G-VN group. In the case of the provisioning the DNN and S-NSSAI specific Group Parameters, the externally provisioned information is defined in clause 4.15.6.14 of TS 23.502[ Procedures for the 5G System (5GS) ] [3] and clause 5.20b. In the case of provisioning ECS address, the externally provisioned information is defined as the ECS Address Configuration Information in clause 4.15.6.3d of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. The affected NFs are informed via the subscriber data update as specified in clause 4.15.6.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. The externally provisioned information which is defined as the Service Parameters in clause 4.15.6.7 of TS 23.502[ Procedures for the 5G System (5GS) ] [3] consists of service specific information used for supporting the specific service in 5G system. The provisioned Service Parameters may be delivered to the UEs. The affected NFs are informed of the data update. Policy/Charging capability is comprised of means that allow the request for session and charging policy, enforce QoS policy, apply accounting functionality and requests to influence access and mobility management policies. It can be used for specific QoS/priority handling for the session of the UE, and for setting applicable charging party or charging rate. Analytics reporting capability is comprised of means that allow discovery of type of analytics that can be consumed by external party, the request for consumption of analytics information generated by NWDAF. Member UE selection capability is comprised of means that allows filtering and providing one or more list(s) of candidate UE(s) (among the list of target member UE(s) provided by the AF) and additional information that can be consumed by external party, the request for consumption of UE list generated by external party. An NEF may support CAPIF functions for external exposure as specified in clause 6.2.5.1. An NEF may support exposure of NWDAF analytics as specified in TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [86]. The NEF may support exposure of 5GS and/or UE availability and capabilities for time synchronization service as specified in clause 5.27.1.8. An NEF may support exposure of event based notifications and reports for NSACF as specified in clause 5.15.11. An AF may only be able to identify the target UE of an AF request for external exposure of 5GC capabilities (e.g. Data Provisioning or for Event Exposure for a specific UE) by providing the UE's address information. In this case the NEF first needs to retrieve the Permanent identifier of the UE before trying to fulfil the AF request. The NEF may determine the Permanent identifier of the UE, as described in clause 4.15.3.2.13 of TS 23.502[ Procedures for the 5G System (5GS) ] [3], based on: - the address of the UE as provided by the AF; this may be an IP address or a MAC address; - the corresponding DNN and/or S-NSSAI information: this may have been provided by the AF or determined by the NEF based on the requesting AF; this is needed if the UE address is an IP address. The NEF may provide an AF specific UE Identifier to the AF: - that has explicitly requested a translation from the address of the UE to a unique UE identifier (via Nnef_UEId service); or - that has implicitly requested a translation from the address of the UE to a AF specific UE Identifier by requesting external exposure about an individual UE identified by its address. The AF may have its own means to maintain the AF specific UE Identifier through, e.g. an AF session. After the retrieval of an AF specific UE Identifier the AF shall not keep maintaining a mapping between this identifier and the UE IP address as this mapping may change. The AF specific UE Identifier shall not correspond to a MSISDN; it is represented as a GPSI in the form of an External Identifier. When used as an AF specific UE identifier, the External Identifier provided by the 5GCN shall be different for different AF. NOTE 1: This is to protect user privacy. NOTE 2: The AF specific UE identifier is ensured to be unique across different AFs as defined in TS 23.003[ Numbering, addressing and identification ] [19] by configuration. Such configuration is assumed to be coordinated between the different involved entities (e.g. NEF(s) and UDM/UDR). NOTE 3: Based on policies, the NEF can be configured to enforce restriction on the usage of AF specific UE identifier (e.g. rejection of a service request from AF not authorized to use the UE identifier). | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.20 |
1,478 | 5.4.5 NAS transport procedure(s) 5.4.5.1 General | The purpose of the NAS transport procedures is to provide a transport of payload between the UE and the AMF. The type of the payload is identified by the Payload container type IE and includes one of the following: a) a single 5GSM message; b) SMS; c) an LPP message (see 3GPP TS 37.355[ LTE Positioning Protocol (LPP) ] [26]); c1) an SLPP message (see 3GPP TS 38.355[ NR; Sidelink Positioning Protocol (SLPP); Protocol Specification ] [26A]); d) an SOR transparent container; e) a UE policy container; f) a UE parameters update transparent container; g) a location services message (see 3GPP TS 24.080[ Mobile radio interface layer 3 supplementary services specification; Formats and coding ] [13A]); h) a CIoT user data container; i) a Service-level-AA container; j) a UPP-CMI container; or k) Multiple payloads. For payload type a) to e), g) and h), along with the payload, the NAS transport procedure may transport the associated information (e.g. PDU session information for 5GSM message payload). For payload type k), the Payload container IE consists a list of payload container entries, where each of payload container entry contains the payload and optional associated information (e.g. PDU session information for 5GSM message payload). NOTE: Payload type can be set to "Multiple payloads" if there are more than one payloads to be transported using the NAS transport procedures. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.4.5 |
1,479 | C.4.4.2 Network specific identifier-based SUPI | The following test data set corresponds to ECIES-based encryption in the UE for network specific identifier-based SUPI and ECIES Profile B. SUPI is: [email protected] ECIES test data The Scheme Output is computed in the UE as defined in Figure C.3.2-1 of clause C.3.2 with following data: Home Network Public Key: uncompressed: '0472DA71976234CE833A6907425867B82E074D44EF907DFB4B3E21C1C2256EBCD15A7DED52FCBB097A4ED250E036C7B9C8C7004C4EEDC4F068CD7BF8D3F900E3B4', if compressed: '0272DA71976234CE833A6907425867B82E074D44EF907DFB4B3E21C1C2256EBCD1' Home Network Private Key (Not available in the UE, provided here only for test purposes): 'F1AB1074477EBCC7F554EA1C5FC368B1616730155E0041AC447D6301975FECDA' Eph. Public Key(scheme output for Profile B always applies point compression for Eph. public key as specified in clause C.3.4.2 above): compressed: '03759BB22C563D9F4A6B3C1419E543FC2F39D6823F02A9D71162B39399218B244B' Eph. Private Key: '90A5898BD29FFA3F261E00E980067C70A2B1B992A21F5B4FEF6D4DF69FE804AD' Eph. Shared Key: 'BC3529ED79541CF8C007CE9806330F4A5FF15064D7CF4B16943EF8F007597872' Eph. Enc. Key: '84F9A78995D39E6968047547ECC12C4F' Scheme-input corresponding to the plaintext-block: '766572796C6F6E67757365726E616D6531' Cipher-text vaue: 'BE22D8B9F856A52ED381CD7EAF4CF2D525' Eph. mac key: '39D5517E965F8E1252B61345ED45226C5F1A8C69F03D6C91437591F0B8E48FA0' MAC-tag value: '3CDDC61A0A7882EB' Scheme Output: ecckey03759BB22C563D9F4A6B3C1419E543FC2F39D6823F02A9D71162B39399218B244B.cipBE22D8B9F856A52ED381CD7EAF4CF2D525.mac3CDDC61A0A7882EB | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | C.4.4.2 |
1,480 | A.8 Monitor of ARQ and HARQ performance | Reliable Packet Delivery is one of the important Performance factor for a better User experience. HARQ retransmissions at the MAC layer ensure reliable packet delivery In addition, RLC can be configured to operate in acknowledged mode for those applications that need very low packet drops and can tolerate a slightly higher delay from RLC retransmissions. If a MAC PDU is not delivered, HARQ takes care of retransmitting (upto a maximum configurable number). If all the retransmissions fail at MAC layer, and if RLC is configured to operate in acknowledged mode, RLC’s ARQ mechanism will take care of any residual packet errors. It is important to a) maintain the block error rate or packet error rate within tolerable limits b) ensure that HARQ retransmissions take care of most packet errors, instead of relying on RLC layer retransmissions (which would increase the delay). So, it is important to monitor the performance of these schemes. ARQ Performance if viewed at QCI level can help in monitoring the distribution for each of the services. HARQ Performance if viewed at MCS (Modulation Coded Scheme) can help in monitoring the MCS Performance also. | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | A.8 |
1,481 | 5.3.7 Handling of the Local Emergency Numbers List and the Extended Local Emergency Numbers List | The Local Emergency Numbers List and the Extended Local Emergency Numbers list contain additional local emergency numbers used by the serving network. These lists can be downloaded by the network to the UE at successful registration and subsequent registration updates. There is only one Local Emergency Numbers List and only one Extended Local Emergency Numbers list in the UE. The Local Emergency Numbers List can be updated with EMM procedures if the UE is in S1 mode, with GMM and MM procedures if the UE is in A/Gb or Iu mode, and with 5GMM procedures, as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54], if UE is in N1 mode. The Extended Local Emergency Numbers List can be updated with EMM procedures if the UE is in S1 mode and with 5GMM procedures, as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54], if UE is in N1 mode. The UE shall use the stored Local Emergency Numbers List and the stored Extended Local Emergency Numbers List received from the network in addition to the emergency numbers stored on the USIM or user equipment to detect that the number dialled is an emergency number. If the UE determines that the number dialled is an emergency number, the procedures specified in 3GPP TS 23.167[ IP Multimedia Subsystem (IMS) emergency sessions ] [45] and 3GPP TS 24.229[ IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 ] [13D] are utilised to select a domain for the emergency session attempt. If the domain selected for the emergency session attempt is the PS domain, then the UE shall perform the session establishment procedures specified in 3GPP TS 24.229[ IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 ] [13D] to initiate an emergency session. If the domain selected for the emergency session attempt is the CS domain (e.g. the UE has selected GERAN or UTRAN radio access technology), then the UE shall use the stored Local Emergency Numbers List, in addition to the emergency numbers stored on the USIM and the ME, to determine if: - the UE is to send an EXTENDED SERVICE REQUEST message: 1) for CS fallback, indicating "mobile originating CS fallback or 1xCS fallback"; or 2) for CS fallback for emergency call, indicating "mobile originating CS fallback emergency call or 1xCS fallback emergency call"; and - the call control entity of the UE specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] is to send an EMERGENCY SETUP message or a SETUP message to the network. NOTE 1: The checking of whether the dialled number is an emergency number and the determination of whether an emergency call is to be initiated in the CS domain, can end once a match is found. The Extended Local Emergency Numbers List does not apply when the CS domain is selected. NOTE 2: The user equipment can use the emergency numbers in each of the stored lists to assist the end user in determining whether the dialled number is intended for an emergency service or for another destination, e.g. a local directory service. The possible interactions with the end user are implementation specific. NOTE 3: A UE that supports procedures specified in 3GPP TS 24.302[ Access to the 3GPP Evolved Packet Core (EPC) via non-3GPP access networks; Stage 3 ] [48], can get additional local emergency numbers through those procedures, which can be used based on operator policy, see 3GPP TS 24.302[ Access to the 3GPP Evolved Packet Core (EPC) via non-3GPP access networks; Stage 3 ] [48]. The network may send a Local Emergency Numbers List or an Extended Local Emergency Numbers List or both, in the ATTACH ACCEPT message or in the TRACKING AREA UPDATE ACCEPT message, by including the Emergency number list IE and the Extended emergency number list IE, respectively. The user equipment shall store the Local Emergency Numbers List and the Extended Local Emergency Numbers List, as provided by the network. The Local Emergency Numbers List stored in the user equipment shall be replaced on each receipt of the Emergency number list IE. The Extended Local Emergency Numbers List stored in the user equipment shall be replaced on each receipt of the Extended emergency number list IE. The received Local Emergency Numbers List or the received Extended Local Emergency Numbers list or both shall be provided to the upper layers. The emergency number(s) received in the Emergency number list IE are valid only in networks in the same country as the PLMN from which this IE is received. If no Local Emergency Numbers List is contained in the ATTACH ACCEPT message or in the TRACKING AREA UPDATE ACCEPT message, then the stored Local Emergency Numbers List in the user equipment shall be kept, except if the user equipment has successfully registered to a PLMN in a country different from that of the PLMN that sent the list. The emergency number(s) received in the Extended emergency number list IE are valid only in: - networks in the same country as the PLMN from which this IE is received, if the Extended Emergency Number List Validity (EENLV) field within the Extended emergency number list IE indicates "Extended Local Emergency Numbers List is valid in the country of the PLMN from which this IE is received"; and - the PLMN from which this IE is received, if the EENLV field within the Extended emergency number list IE indicates "Extended Local Emergency Numbers List is valid only in the PLMN from which this IE is received". If no Extended Local Emergency Numbers List is contained in the ATTACH ACCEPT message or in the TRACKING AREA UPDATE ACCEPT message, and the registered PLMN has not changed, then the stored Extended Local Emergency Numbers List in the user equipment shall be kept. If no Extended Local Emergency Numbers List is contained in the ATTACH ACCEPT message or in the TRACKING AREA UPDATE ACCEPT message, but the registered PLMN has changed, then: - if the last received indication in the EENLV field within the Extended emergency number list IE indicates "Extended Local Emergency Numbers List is valid only in the PLMN from which this IE is received", the stored Extended Local Emergency Numbers List in the user equipment shall be deleted; and - if the last received indication in the EENLV field within the Extended emergency number list IE indicates "Extended Local Emergency Numbers List is valid in the country of the PLMN from which this IE is received" the list shall be kept except if the user equipment has successfully registered to a PLMN in a country different from that of the PLMN that sent the list. NOTE: To prevent the misrouting of emergency calls, all operators within a country need to follow the regulation or agree on the setting of the Extended emergency number list IE in accordance to national agreement – either to indicate validity within a country or to indicate validity only within the PLMN. The Local Emergency Numbers List and the Extended Local Emergency Numbers List shall be deleted at switch off and removal of the USIM. The user equipment shall be able to store up to ten entries in the Local Emergency Numbers List and up to twenty entries in the Extended Local Emergency Numbers List, received from the network. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.3.7 |
1,482 | 4.1 Security domains | Figure 4-1 gives an overview of security architecture. Figure 4-1: Overview of the security architecture The figure illustrates the following security domains: - Network access security (I): the set of security features that enable a UE to authenticate and access services via the network securely, including the 3GPP access and Non-3GPP access, and in particularly, to protect against attacks on the (radio) interfaces. In addition, it includes the security context delivery from SN to AN for the access security. - Network domain security (II): the set of security features that enable network nodes to securely exchange signalling data and user plane data. - User domain security (III): the set of security features that secure the user access to mobile equipment. - Application domain security (IV): the set of security features that enable applications in the user domain and in the provider domain to exchange messages securely. Application domain security is out of scope of the present document. - SBA domain security (V): the set of security features that enables network functions of the SBA architecture to securely communicate within the serving network domain and with other network domains . Such features include network function registration, discovery, and authorization security aspects, as well as the protection for the service-based interfaces. SBA domain security is a new security feature compared to TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [10]. - Visibility and configurability of security (VI): the set of features that enable the user to be informed whether a security feature is in operation or not. NOTE: The visibility and configurability of security is not shown in the figure. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 4.1 |
1,483 | 5.8.9.1.3 Reception of an RRCReconfigurationSidelink by the UE | The UE shall perform the following actions upon reception of the RRCReconfigurationSidelink: 1> if the RRCReconfigurationSidelink includes the sl-ResetConfig: 2> perform the sidelink reset configuration procedure as specified in 5.8.9.1.10; 1> if the RRCReconfigurationSidelink includes the slrb-ConfigToReleaseList: 2> for each entry value included in the slrb-ConfigToReleaseList that is part of the current UE sidelink configuration; 3> perform the sidelink DRB release procedure, according to clause 5.8.9.1a.1; 1> if the RRCReconfigurationSidelink includes the slrb-ConfigToAddModList: 2> for each slrb-PC5-ConfigIndex value included in the slrb-ConfigToAddModList that is not part of the current UE sidelink configuration: 3> if sl-MappedQoS-FlowsToAddList is included: 4> apply the SL-PQFI included in sl-MappedQoS-FlowsToAddList; 3> perform the sidelink DRB addition procedure, according to clause 5.8.9.1a.2; 2> for each slrb-PC5-ConfigIndex value included in the slrb-ConfigToAddModList that is part of the current UE sidelink configuration: 3> if sl-MappedQoS-FlowsToAddList is included: 4> add the SL-PQFI included in sl-MappedQoS-FlowsToAddList to the corresponding sidelink DRB; 3> if sl-MappedQoS-FlowsToReleaseList is included: 4> remove the SL-PQFI included in sl-MappedQoS-FlowsToReleaseList from the corresponding sidelink DRB; 3> if the sidelink DRB release conditions as described in clause 5.8.9.1a.1.1 are met: 4> perform the sidelink DRB release procedure according to clause 5.8.9.1a.1.2; 3> else if the sidelink DRB modification conditions as described in clause 5.8.9.1a.2.1 are met: 4> perform the sidelink DRB modification procedure according to clause 5.8.9.1a.2.2; 1> if the RRCReconfigurationSidelink includes the sl-RLC-BearerToReleaseList: 2> for each entry value included in the sl-RLC-BearerToReleaseList that is part of the current UE sidelink configuration; 3> perform the additional sidelink RLC bearer release procedure, according to clause 5.8.9.1a.5; 1> if the RRCReconfigurationSidelink includes the sl-RLC-BearerToAddModList: 2> for each SL-RLC-BearerConfigIndex value included in the sl-RLC-BearerToAddModList that is not part of the current UE sidelink configuration: 3> perform the additional sidelink RLC bearer addition procedure, according to clause 5.8.9.1a.6; 2> for each SL-RLC-BearerConfigIndex value included in the sl-RLC-BearerToAddModList that is part of the current UE sidelink configuration: 3> perform the additional sidelink RLC bearer modification procedure, according to clause 5.8.9.1a.6; 1> if the RRCReconfigurationSidelink includes the sl-CarrierToReleaseList: 2> for each entry value included in the sl-CarrierToReleaseList that is part of the current UE sidelink configuration; 3> perform the sidelink carrier release procedure, according to clause 5.8.9.1b.1; 1> if the RRCReconfigurationSidelink includes the sl-CarrierToAddModList: 2> for each sl-Carrier-Id value included in the sl-CarrierToAddModList that is not part of the current UE sidelink configuration: 3> perform the sidelink carrier addition procedure, according to clause 5.8.9.1b.2; 2> for each sl-Carrier-Id value included in the sl-CarrierToAddModList that is part of the current UE sidelink configuration: 3> perform the carrier modification procedure, according to clause 5.8.9.1b.2; 1> if the RRCReconfigurationSidelink message includes the sl-MeasConfig: 2> perform the sidelink measurement configuration procedure as specified in 5.8.10; 1> if the RRCReconfigurationSidelink message includes the sl-CSI-RS-Config: 2> apply the sidelink CSI-RS configuration; 1> if the RRCReconfigurationSidelink message includes the sl-LatencyBoundCSI-Report: 2> apply the configured sidelink CSI report latency bound; 1> if the RRCReconfigurationSidelink includes the sl-RLC-ChannelToReleaseListPC5: 2> for each SL-RLC-ChannelID value included in the sl-RLC-ChannelToReleaseListPC5 that is part of the current UE sidelink configuration; 3> perform the PC5 Relay RLC channel release procedure, according to clause 5.8.9.7.1; 1> if the RRCReconfigurationSidelink includes the sl-RLC-ChannelToAddModListPC5: 2> for each sl-RLC-ChannelID-PC5 value included in the sl-RLC-ChannelToAddModListPC5 that is not part of the current UE sidelink configuration: 3> perform the PC5 Relay RLC channel addition procedure, according to clause 5.8.9.7.2; 2> for each sl-RLC-ChannelID-PC5 value included in the sl-RLC-ChannelToAddModListPC5 that is part of the current UE sidelink configuration: 3> perform the PC5 Relay RLC channel modification procedure according to clause 5.8.9.7.2; 1> if the RRCReconfigurationSidelink message includes the sl-DRX-ConfigUC-PC5; and 1> if the UE accepts the sl-DRX-ConfigUC-PC5: 2> configure lower layers to perform sidelink DRX operation according to sl-DRX-ConfigUC-PC5 for the associated destination as defined in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3]; 1> if the RRCReconfigurationSidelink message includes the sl-LatencyBoundIUC-Report: 2> apply the configured sidelink IUC report latency bound; 1> if the RRCReconfigurationSidelink message includes the sl-LocalID-PairToReleaseList or sl-LocalID-PairToAddModList: 2> configure SRAP entity to perform NR sidelink L2 U2U relay operation accordingly for the end-to-end PC5 connection peer L2 U2U Remote UE as defined in TS 38.351[ NR; Sidelink Relay Adaptation Protocol (SRAP) Specification ] [65]; 1> if the RRCReconfigurationSidelink message includes the sl-MappingToAddModListPC5 or sl-MappingToReleaseListPC5: 2> configure lower layers to perform NR sidelink L2 U2U relay operation according to mapping between end-to-end sidelink bearer of L2 U2U Remote UE and egress PC5 Relay RLC channel as defined in TS 38.351[ NR; Sidelink Relay Adaptation Protocol (SRAP) Specification ] [65]; 1> if the UE is unable to comply with (part of) the configuration included in the RRCReconfigurationSidelink (i.e. sidelink RRC reconfiguration failure): 2> continue using the configuration used prior to the reception of the RRCReconfigurationSidelink message; 2> set the content of the RRCReconfigurationFailureSidelink message; 3> submit the RRCReconfigurationFailureSidelink message to lower layers for transmission; 1> if the RRCReconfigurationSidelink message includes the sl-SFN-DFN-Offset: 2> if the sl-SFN-DFN-Offset is set to setup: 3> apply the configured SFN-DFN time offset; 2> if the sl-SFN-DFN-Offset is set to release: 3> release the received sl-SFN-DFN-Offset; 1> else: 2> set the content of the RRCReconfigurationCompleteSidelink message; 3> if the UE rejects the sidelink DRX configuration sl-DRX-ConfigUC-PC5 received from the peer UE: 4> include the sl-DRX-ConfigReject in the RRCReconfigurationCompleteSidelink message; 4> consider no sidelink DRX to be applied for the corresponding sidelink unicast communication; 3> submit the RRCReconfigurationCompleteSidelink message to lower layers for transmission; NOTE 1: When the same logical channel is configured with different RLC mode by another UE, the UE handles the case as sidelink RRC reconfiguration failure. NOTE 2: It is up to the UE implementation whether or not to indicate the rejection to the peer UE for a received sidelink DRX configuration. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.8.9.1.3 |
1,484 | 4.11.1.3.3 EPS to 5GS Mobility Registration Procedure (Idle and Connected State) using N26 interface | Figure 4.11.1.3.3-1 describes the mobility registration procedure from EPS to 5GS when N26 is supported for idle and connected states. Figure 4.11.1.3.3-1: EPS to 5GS mobility for single-registration mode with N26 interface 1. The Registration procedure is triggered, e.g. the UE moves into NG-RAN coverage. Step 2 to 9 except step 5, 6 and 8 follow the Registration procedure in clause 4.2.2 with following enhancement. 2. The UE sends Registration Request with registration type set to "Mobility Registration Update". The UE includes 5G-GUTI mapped from EPS GUTI as the old GUTI, the native 5G-GUTI (if available) as additional GUTI and indicating that the UE is moving from EPC. The UE includes the UE Policy Container containing the list of PSIs, indication of UE support for ANDSP and OSId if available. When the Registration Request is triggered due to UE mobility from EPS to 5GS, if the UE has locally deleted the EPS bearer which has allocated 5GS parameters and the EPS bearer status has not been synchronized with the network, the UE shall include the EPS bearer status in the Registration Request. If the UE has not received mapped 5GS QoS parameters from the network for PDN connection(s), the UE locally releases those PDN connection(s). The Additional GUTI is provided both in Idle state and Connected state, if available. The Additional 5G-GUTI enables the AMF to retrieve the UE's MM context from the old AMF (if available). The UE includes the S-NSSAIs associated with the established PDN connections in the Requested NSSAI in RRC and NAS (as described in clause 5.15.7 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]). In the case of Configured NSSAI applicable to this PLMN or an Allowed NSSAI are not present in the UE, the associated HPLMN S-NSSAI(s) shall be provided in the mapping of Requested NSSAI in the NAS as described in clause 5.15.5.2.1 TS 23.501[ System architecture for the 5G System (5GS) ] [2]. In the case of idle mode mobility the UE additionally includes a TAU request message integrity protected using the EPS security context (for further security verification by the MME) in the Registration Request. If the UE holds a native 5G-GUTI for this PLMN then the UE also includes the GUAMI part of the native 5G-GUTI in RRC to enable the NG-RAN to route the Registration Request to the same AMF (if available) and otherwise the UE provides in RRC signalling a GUAMI mapped from the EPS GUTI and indicates it as "Mapped from EPS". The UE integrity protects the Registration Request message using a 5G security context (if available). 3-4. Steps 2-3 of clause 4.2.2.2.2 are performed. In the case of idle mode mobility, the AMF derives S-NSSAIs values for the Serving PLMN based on the S-NSSAIs values for the HPLMN, received in NAS Registration Request, associated with the established PDN connections, the AMF may send the S-NSSAIs values for the HPLMN to NSSF by invoking Nnssf_NSSelection_Get service operation and NSSF provides corresponding S-NSSAIs values for VPLMN to AMF. NOTE 1: In connected mode mobility, the AMF devices S-NSSAIs values during the handover procedure. Steps 5 and 8 are not performed when this procedure is part of EPS to 5GS handover. 5a. [Conditional] This step is only performed for IDLE mode mobility. The AMF derives the MME address and 4G GUTI from the old 5G-GUTI and sends Context Request to MME including EPS GUTI mapped from 5G-GUTI and the TAU request message according to TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13]. The MME validates the TAU message. 5b. [Conditional] If step 5a is performed, step 5 from clause 5.3.3.1 (Tracking Area Update procedure with Serving GW change) in TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13] is performed with the modification captured in clause 4.11.1.5.3. The AMF converts the received EPS MM Context into the 5GS MM Context. The received EPS UE context includes IMSI, ME Identity, UE EPS security context, UE Network Capability and EPS Bearer context(s) and may also include LTE-M Indication. The MME EPS Bearer context includes for each EPS PDN connection the IP address and FQDN for the S5/S8 interface of the SMF+PGW-C and APN. If the SCEF connection is invoked, the MME EPS Bearer context includes the SCEF+NEF ID of the PDN connection, EBI, APN, User Identity. The AMF disregards any LTE-M Indication received in the EPS UE context and instead takes into account the LTE M Indication received from NG-RAN, at step 1. The AMF can determine the whether the UE is performing Inter-RAT mobility to or from NB-IoT based on the received "TAI of last TAU" in the EPC MM Context and the RAT Type used for the Registration Request. If the Context Response includes the FQDN for the S5/S8 interface of the SMF+PGW-C, the AMF queries the NRF in serving PLMN by issuing the Nnrf_NFDiscovery_Request including the FQDN for the S5/S8 interface of the SMF+PGW-C and the NRF provides the IP address or FQDN of the N11/N16 interface of the SMF+PGW-C. If the Context Response includes an SCEF+NEF ID, the AMF performs the SMF selection. The Context Response may include new information Return Preferred. Return Preferred is an indication by the MME of a preferred return of the UE to the last used EPS PLMN at a later access change to an EPS shared network. Based on the Return Preferred indication, the AMF may store the last used EPS PLMN ID in UE Context. If the AMF cannot retrieve the address of the corresponding SMF for a PDN connection, it will not move the PDN connection to 5GS. Step 6 is performed only if the AMF is different from the old AMF and the old AMF is in the same PLMN as the AMF. 6a. [Conditional] If the UE includes the 5G-GUTI as Additional GUTI in the Registration Request message, the AMF sends message to the old AMF. The old AMF validates the Registration request message. The AMF retrieves UE's SUPI and MM Context, event subscription information by each consumer NF and the list of SM PDU Session ID/associated SMF ID for the UE using one of the following three options: - AMF may invoke the Namf_Communication_UEContextTransfer to the old AMF identified by the additional 5G-GUTI; or - if the old AMF and the AMF are in the same AMF Set and UDSF is deployed, AMF may invoke Nudsf_UnstructuredDataManagement_Query service operation for the UE identified by the additional 5G-GUTI from the UDSF; or - if the old AMF and the AMF are in the same AMF Set, AMF may use implementation specific means to share UE context. 6b. [Conditional] If step 6a is performed, the response is performed as described in step 5 in clause 4.2.2.2.2. If a native 5G security context for 3GPP access is available in the AMF (or has been retrieved in step 6a), the AMF may continue to use this security context. Otherwise, the AMF shall either derive a mapped security context from the EPS security context obtained from the MME or initiate an authentication procedure to the UE. If the new AMF determines that the UE has emergency PDU Session and the AMF is configured to allow emergency services for unauthenticated UE, the new AMF behaves as follows: - If the UE has only an emergency PDU Session, the AMF either skips the authentication and security procedure in step 7 or accepts that the authentication may fail and continues the Mobility Registration Update procedure; or - If the UE has both emergency and non emergency PDU Sessions and authentication fails, the AMF continues the Mobility Registration Update procedure and deactivates all the non-emergency PDU Sessions as specified in clause 4.3.4.2. NOTE 2: The new AMF can determine if a PDU Session is used for emergency service by checking whether the DNN matches the emergency DNN. 7. [Conditional] If the AMF determines to initiate the authentication procedure to the UE in step 6b (e.g. the AMF can not obtain the UE MM context from AMF or other reasons), steps 8-9 of clause 4.2.2.2.2 are optionally performed. 7a. In the case of idle mode mobility, the AMF decide whether a new AMF needs to be selected. If a new AMF is to be selected, the AMF reroute the Registration request to the new AMF as described in clause 4.11.1.3.4, where the initial AMF refers to the AMF. 8. [Conditional] If step 5b is performed and the AMF accepts to serve the UE, the AMF sends Context Acknowledge (Serving GW change indication) to MME according to TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13]. 9. Steps 11-12 of clause 4.2.2.2.2 are optionally performed. 10. Void. 11. Steps 13-14e of clause 4.2.2.2.2 are performed: This includes that if an MM context is retrieved from the old AMF in step 6 (i.e. corresponding to an existing UE registration for non-3GPP access in 5GC), then the AMF indicates to the UDM that the AMF identity to be registered in the UDM applies to both 3GPP and non-3GPP accesses by sending separate/independent Nudm_UECM_Registration service operations for "3GPP Access" and "non-3GPP Access". 12. Void. 13. Void. 14-14f. Step 16 of clause 4.2.2.2.2 (AM Policy Association Establishment) is optionally performed. In the home-routed roaming case and connected state mobility, based on the S-NSSAI value for the Serving PLMN of the PDU Session(s), the AMF decides whether V-SMF change is needed or not. - If the V-SMF reallocation is not needed and if the two values (i.e. the S-NSSAI value configured in AMF for interworking and S-NSSAI value for the Serving PLMN) are different, the AMF invokes Nsmf_PDUSession_UpdateSMContext (PDU Session ID, S-NSSAI value for the Serving PLMN). - If V-UPF is not changed, the V-SMF updates 5G AN with the new S-NSSAI of VPLMN by sending a N2 SM message to 5G AN via AMF. - If V-UPF is changed, the V-SMF performs procedure as specified in clause 4.23.4.2 with the difference that I-SMF/I-UPF in clause 4.23.4.2 is replaced by V-SMF/V-UPF and with the following modification: - In step 11 of clause 4.2.3.2 referenced by clause 4.23.4.2, the V-SMF includes in N2 SM information with the new S-NSSAI of the VPLMN. - If the V-SMF change is needed, the AMF performs as the case of I-SMF change defined in clause 4.23.4.3 with the difference that I-SMF in clause 4.23.4.3 is replaced by V-SMF and with following modifications: - In step 3 of clause 4.23.4.3, the AMF sends indication of no NG-RAN change to the new V-SMF. - In step 4a of clause 4.23.4.3, when the new V-SMF retrieves SM context from the old V-SMF, the new V-SMF sends indication of no NG-RAN change as it is received in step 3. - In step 4b of clause 4.23.4.3, as the old V-SMF receives the indication of no NG-RAN change, the old V-SMF returns additional N3 tunnel information of NG-RAN. - In step 6 of clause 4.23.4.3, the new I-SMF should reuse the N3 tunnel information of NG-RAN received from old I-SMF/SMF. - In step 9 of clause 4.23.4.3, when the new V-SMF sends a Nsmf_PDUSession_CreateSMContext Response, the new V-SMF includes PDU Session Resource Modify in N2 SM information. In the home-routed roaming case and idle state mobility, the AMF selects a default V-SMF per PDU Session and invokes Nsmf_PDUSession_CreateSMContext service operation of the V-SMF to create an association with the AMF. It includes UE EPS PDN Connection, MSISDN as a GPSI if received from MME, H-SMF ID, S-NSSAI and indicates all the PDU Session(s) to be re-activated as received in the Registration request message along with List Of PDU Sessions To Be Activated. The S-NSSAI is the S-NSSAI configured in AMF for interworking, which is associated with default V-SMF. The V-SMF creates the association and based on the received SMF ID, the V-SMF invokes Nsmf_PDUSession_Create request service operation of the H-SMF and provides the information received from the AMF. Before invoking PDUSession_Create service operation, the V-SMF request the V-UPF to provide the CN tunnel info. In the home-routed roaming case and idle state mobility, the V-SMF provides the QoS constraints of the VPLMN to the H-SMF. The subsequent handling is performed as follows: - The H-SMF finds the corresponding PDU Session based on the PDN Connection Context in the request. The H-SMF initiates N4 Session modification procedure to establish the CN tunnel for the PDU Session. The tunnel info for PDU Session is allocated by PGW-U+UPF and provided to the SMF+PGW-C. The H-SMF responds V-SMF with the PDU Session ID corresponding to the PDN Connection Context in the request, the allocated EBI(s) information, the S-NSSAI of the PDU Session, S-NSSAI of HPLMN, UE EPS PDN connection(s) and other PDU session parameters, such as PDU Session Type, Session AMBR in the Nsmf_PDUSession_Create response. - The V-SMF updates its SM contexts and returns a Nsmf_PDU_Session_CreateSMContextResponse message including the information received from the H-SMF. The V-SMF updates the V-UPF of the CN tunnel info of SMF+PGW-C. The V-SMF also includes the N2 SM Context in the response message sent to the AMF if the corresponding PDU Session is in the received List Of PDU Sessions To Be Activated. The V-SMF stores an association of the PDU Session ID and the H-SMF ID. The AMF stores the V-SMF ID and it also stores S-NSSAI and the allocated EBI(s) associated to the PDU Session ID. Based on the S-NSSAI value for the Serving PLMN of the PDU Session(s) the AMF decides whether V-SMF relocation is needed or not. - If V-SMF relocation is not needed and if the two values (i.e. the S-NSSAI value configured in AMF for interworking and S-NSSAI value for the Serving PLMN) are different, the AMF sends the S-NSSAI value for the Serving PLMN to V-SMF by invoking Nsmf_PDUSession_UpdateSMContext service operation. If V-UPF change is not needed, the V-SMF updates NG RAN with the S-NSSAI value for the Serving PLMN via N2 SM message. If V-UPF change is needed, the V-SMF performs procedure as specified in clause 4.23.4.2 with the difference that I-SMF/I-UPF is replaced with V-SMF/V-UPF and with the following modification: - In step 11 of clause 4.2.3.2 referenced by clause 4.23.4.2, the V-SMF includes in N2 SM information with the new S-NSSAI of the VPLMN. - If V-SMF relocation is needed, the AMF performs V-SMF relocation as defined in clause 4.23.4.3. In the case of home-routed roaming scenario, the V-SMF may apply VPLMN policies as described in TS 23.501[ System architecture for the 5G System (5GS) ] [2], clause 5.17.1.3. In non-roaming and LBO cases and idle state mobility, AMF invokes Nsmf_PDUSession_CreateSMContext Request (UE EPS PDN Connection) service operation of the SMF+PGW-C and indicates all the PDU Session(s) to be re-activated as received in the Registration request message along with List Of PDU Sessions To Be Activated. This step is performed for each PDN Connection and the corresponding SMF+PGW-C address/ID in the UE context the AMF received in Step 6. The SMF+PGW-C finds the corresponding PDU Session based on the PDN Connection Context in the request. If the P-GW-C+SMF (H-SMF in the case of home-routed roaming case) determines that seamless session continuity from EPS to 5GS is not supported for the PDU Session, (e.g. if PDU Session ID was not received by the SMF+PGW-C for the PDN connection or PDU Session ID was received but mapped 5GS parameters were not provided to the UE due to 5GS interworking not supported), then it does not provide SM information for the corresponding PDU Session but includes the appropriate cause code for rejecting the PDU Session transfer within the N2 SM Information. The PDN connection(s) not further transferred to 5GC are locally released at the SMF+PGW-C. Otherwise, if session continuity from EPS to 5GS is supported for the PDU Session, the SMF+PGW-C finds the corresponding PDU Session based on the PDN Connection Context in the request. The SMF+PGW-C initiates N4 Session modification procedure to establish the CN tunnel for the PDU Session. If the SMF+PGW-C has not yet registered for this PDU Session ID, the SMF+PGW-C registers with the UDM using Nudm_UECM_Registration (SUPI, DNN, PDU Session ID) for a given PDU Session as in step 4 of PDU Session Establishment Procedure in clause 4.3.2. The tunnel info for PDU Session is allocated by PGW-U+UPF and provided to the SMF+PGW-C. The SMF+PGW-C updates its SM contexts and returns the AMF a Nsmf_PDUSession_CreateSMContext Response message including the PDU Session ID corresponding to the PDN Connection Context in the request, the allocated EBI(s) information, the S-NSSAI of the PDU Session and the N2 SM Context if the corresponding PDU Session is in the received List Of PDU Sessions To Be Activated. The AMF stores an association of the PDU Session ID and the SMF ID, S-NSSAI and the allocated EBI(s) associated to the PDU Session ID. Based on the allocated EBI(s) information received from all the related SMF+PGW-C for this UE, an EPS bearer status, which reflects all existing EPS bearer, is generated by the AMF. NOTE 3: For Connected State mobility registration, the release of CN tunnels for EPS bearers and UDM registration for the session corresponding to the PDU session is performed in the handover execution phase. If the PDN Type of a PDN Connection in EPS is non-IP and it was originally established as Ethernet PDU Session when UE was camping in 5GS (known based on local context information that was set to PDU Session Type Ethernet in UE and SMF), the PDU Session Type in 5GS shall be set to Ethernet by the SMF and UE. If the PDN type of a PDN Connection in EPS is non-IP and is locally associated in UE and SMF to PDU Session Type Unstructured, the PDU Session Type in 5GS shall be set to Unstructured by the SMF and UE. NOTE 4: If the non-IP PDN Type is originally established as Ethernet PDU Session, it means that Ethernet PDN Type is not supported in EPS. If the AMF has received the EPS Bearer Status in the Registration Request from UE, the AMF shall send the EPS Bearer Status to all corresponding SMF+PGW-Cs. If the SMF+PGW-C receives the EPS Bearer Status from AMF, the SMF+PGW-C shall check whether the EPS bearer(s) has been deleted by UE but not notified to network. If yes, the SMF+PGW-C shall release those EPS bearer(s), the corresponding 5G QoS Rule(s) and the QoS Flow level QoS parameters locally. If the SCEF+NEF ID is provided to the SMF, the SMF establishes the SMF-NEF connection as described in steps 2-3 from clause 4.25.2, the SMF provides the SCEF+NEF ID, EBI, APN, User Identity to the SCEF+NEF and the SCEF+NEF updates the SM contexts and returns the NEF ID, PDU Session ID, DNN and User Identity to the SMF. If the UE is performing Inter-RAT mobility to or from NB-IoT, the (H-)SMF will maintain, reconnect, release or leave PDU Session handling to the local VPLMN policy in the case of roaming for each PDU session according to the "PDU Session continuity at inter RAT mobility" subscription information. If the (H-)SMF does not have "PDU Session continuity at inter RAT mobility" for a PDU session, the (H-)SMF retrieves it from the UDM before determining any action. The SMF may use local policy to determine the handling a PDU Session if "PDU Session continuity at inter RAT mobility" cannot be retrieved from the UDM. After the step 14a, the SMF+PGW-C receives the SM context create request from AMF and the SMF+PGW-C awares that the UE returns back from EPS. When the SMF+PGW-C notifies the PCF for the PDU session of changing RAT from EPS to 5GS, the PCF for the PDU session checks if there exists a UE policy association in EPS for the UE and in that case, request the termination of such UE Policy Association to the PCF for a UE. 15 - 16a. HSS+UDM cancels the location of the UE in the MME as defined in steps 13 - 14 from clause 5.3.3.1 (Tracking Area Update procedure with Serving GW change) in TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13]. Subsequently, the steps 18 - 19 from clause 5.3.3.1 (Tracking Area Update procedure with Serving GW change) in TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13] are also executed with the following modification: According to configuration, for the PDN connections which are anchored in a standalone PGW, the MME initiates PDN connection release procedure as specified in TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13]. 17-18. These steps follow the steps 21, 21b and 22 of Registration procedure in clause 4.2.2.2.2. The Registration Accept message shall include the updated 5G-GUTI to be used by the UE in that PLMN over any access. If the active flag was included in the Registration request, The AMF may provide NG-RAN with a Mobility Restriction List taking into account the last used EPS PLMN ID and the Return preferred indication. The Mobility Restriction List contains a list of PLMN IDs as specified by TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The Allowed NSSAI in the Registration Accept message shall contain at least the S-NSSAIs corresponding to the active PDN Connection(s) and the corresponding mapping to the HPLMN S-NSSAIs. The AMF shall include the EPS bearer status, which is generated at step 14, in the Registration Accept message. Based on the received EPS bearer status information, the UE shall check whether there are QoS Flow(s) existing locally but no associated EPS bearer(s) in the received EPS bearer status. The UE shall locally delete the 5G QoS Rule(s) and QoS Flow level QoS parameters of the QoS Flow(s) if the associated EPS bearer(s) do not exist in the received EPS bearer status. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.11.1.3.3 |
1,485 | 5.5.2.3.1 Network-initiated de-registration procedure initiation | The network initiates the de-registration procedure by sending a DEREGISTRATION REQUEST message to the UE (see example in figure 5.5.2.3.1.1). NOTE 1: If the AMF performs a local de-registration, it will inform the UE with a 5GMM messages (e.g. SERVICE REJECT message or REGISTRATION REJECT message) with 5GMM cause #10 "implicitly de-registered" only when the UE initiates a 5GMM procedure. The network may include a 5GMM cause IE to specify the reason for the DEREGISTRATION REQUEST message. The network shall start timer T3522. The network shall indicate whether re-registration is needed or not in the De-registration type IE. The network shall also indicate via the access type whether the de-registration procedure is: a) for 3GPP access only; b) for non-3GPP access only; or c) for 3GPP access, non-3GPP access or both when the UE is registered in the same PLMN for both accesses. If the network de-registration is triggered due to network slice-specific authentication and authorization failure or revocation as specified in subclause 4.6.2.4, then the network shall set the 5GMM cause value to #62 "No network slices available" in the DEREGISTRATION REQUEST message. In addition, if the UE supports extended rejected NSSAI, the AMF shall include the Extended rejected NSSAI IE in the DEREGISTRATION REQUEST message; otherwise, the AMF shall include the Rejected NSSAI IE in the DEREGISTRATION REQUEST message. In roaming scenarios, if the Extended rejected NSSAI IE is included in the DEREGISTRATION REQUEST message, the AMF shall provide mapped S-NSSAI(s) for the rejected NSSAI. If the UE supports extended rejected NSSAI and the network de-registration is triggered due to mobility management based network slice admission control as specified in subclause 4.6.2.5, then the network shall set the 5GMM cause value to #62 "No network slices available" in the DEREGISTRATION REQUEST message. In addition, the network may include a back-off timer value for each S-NSSAI with the rejection cause "S-NSSAI not available due to maximum number of UEs reached" in the Extended rejected NSSAI IE of the DEREGISTRATION REQUEST message. If the network de-registration is triggered for a UE supporting CAG due to CAG restrictions, the network shall set the 5GMM cause value to #76 "Not authorized for this CAG or authorized for CAG cells only" and should include the "CAG information list" in the CAG information list IE or the Extended CAG information list IE in the DEREGISTRATION REQUEST message. NOTE 2: If the UE supports extended CAG information list, the CAG information list can be included either in the CAG information list IE or Extended CAG information list IE. NOTE 3: It is unexpected for network to send REGISTRATION REJECT message to the UE with 5GMM cause value #76 in non-CAG cell and not indicate "Indication that the UE is only allowed to access 5GS via CAG cells" for the serving PLMN in the Extended CAG information list or the CAG information list. If the network de-registration is triggered for a UE not supporting CAG due to CAG restrictions, the network shall operate as described in bullet g) of subclause 5.5.2.3.5. If the network de-registration is triggered because the network determines that the UE is in a location where the network is not allowed to operate, see 3GPP TS 23.502[ Procedures for the 5G System (5GS) ] [9], the network shall set the 5GMM cause value in the DEREGISTRATION REQUEST message to #78 "PLMN not allowed to operate at the present UE location". If the network de-registration is triggered due to: a) an unsuccessful outcome of an ongoing UUAA-MM procedure; b) an UUAA revocation notification received from the UAS-NF for a UE supporting UAS service requesting UAS services; or c) the UE not allowed to use UAS services via 5GS due to a change of the aerial UE subscription information, then the network shall set the 5GMM cause value in the DEREGISTRATION REQUEST message to #79 "UAS services not allowed". NOTE 4: If the UE supporting UAS service has requested other services than UAS services, or if there are other ongoing network slice-specific authentication and authorization on pending NSSAIs, it is then an operator policy or configuration decision whether to keep the UE supporting UAS service registered to the network, but that UE supporting UAS services is not allowed to access UAS services via 5GS as specified in 3GPP TS 23.256[ Support of Uncrewed Aerial Systems (UAS) connectivity, identification and tracking; Stage 2 ] [6AB]. If the network de-registration is triggered for a UE supporting MINT due to a disaster condition no longer being applicable in the current location of the UE, the network shall set the 5GMM cause value to #11 "PLMN not allowed" and may include a disaster return wait range in the Disaster return wait range IE in the DEREGISTRATION REQUEST message. If the network de-registration is triggered because the AMF determines that, by UE subscription and operator's preferences, all of the TAIs received from the satellite NG-RAN are forbidden for roaming or for regional provision of service, the AMF shall include the TAI(s) in: a) the Forbidden TAI(s) for the list of "5GS forbidden tracking areas for roaming" IE; or b) the Forbidden TAI(s) for the list of "5GS forbidden tracking areas for regional provision of service" IE; or c) both; in the DEREGISTRATION REQUEST message. If the network de-registration is triggered because the AMF determines that the UE operating as an IAB-node by subscription is not authorized for IAB-node operation, the AMF shall set the 5GMM cause value to #36 "IAB-node operation not authorized" in the DEREGISTRATION REQUEST message. If the network de-registration is triggered for a UE operating as MBSR due to the UE no longer being allowed to operate as MBSR based on the UE subscription and the local policy and the UE is allowed to operate as a UE, then the network shall indicate "re-registration required" in the De-registration type IE of the DEREGISTRATION REQUEST message based on the local policy. If the network de-registration is triggered due to the UE that was not allowed for MBSR operation becoming allowed to operate as MBSR based on the UE subscription and the local policy, then the network shall indicate "re-registration required" in the De-registration type IE of the DEREGISTRATION REQUEST message. The AMF shall trigger the SMF to release locally the PDU session(s) over the indicated access(es), if any, for the UE and enter state 5GMM-DEREGISTERED-INITIATED. If a PDU session is associated with one or more multicast MBS sessions, the SMF shall consider the UE as removed from the associated multicast MBS sessions. Figure 5.5.2.3.1.1: Network-initiated de-registration procedure | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.5.2.3.1 |
1,486 | 4.2.4.2.2 Substate, ATTEMPTING-TO-ATTACH | The MS: - shall initiate GPRS attach on the expiry of timers T3311, T3302, or T3346; - shall initiate GPRS attach when entering a new PLMN, if timer T3346 is running and the new PLMN is not equivalent to the PLMN where the MS started timer T3346, the PLMN identity of the new cell is not in one of the forbidden PLMN lists and the location area this cell is belonging to is not in one of the lists of forbidden LAs; - may initiate GPRS attach for emergency bearer services (UTRAN Iu mode only) even if timer T3346 is running; - shall initiate GPRS attach when the routing area of the serving cell has changed, if timer T3346 is not running, the PLMN identity of the new cell is not in one of the forbidden PLMN lists and the location area this cell is belonging to is not in one of the lists of forbidden LAs; - shall if entry into this state was caused by b) or d) with cause "Retry upon entry into a new cell" of subclause 4.7.3.1.5, perform GPRS attach when a new cell is entered; - shall if entry into this state was caused by c) or d) with cause different from "Retry upon entry into a new cell" of subclause 4.7.3.1.5, not perform GPRS attach when a new cell is entered; - shall use requests for non-GPRS services from CM layers to trigger the combined GPRS attach procedure, if timer T3346 is not running and the network operates in network operation mode I. Depending on which of the timers T3311 or T3302 is running the MS shall stop the relevant timer and act as if the stopped timer has expired; and - may initiate GPRS attach upon request of the upper layers to establish a PDN connection for emergency bearer services (UTRAN Iu mode only). | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.2.4.2.2 |
1,487 | 8.2.1A Information Element with an IE Type Extension field | Figure 8.2.1A-1 depicts the format of an information element with an IE Type Extension field. Figure 8.2.1A-1: Information Element with an IE Type Extension field The IE Type in octet 1 of an information element with an IE Type Extension field shall be set to 254. Such IE shall be further identified by the value encoded in the IE Type Extension field in octets 5 and 6. The value of the IE Type Extension shall be encoded in full hexadecimal representation (binary, not ASCII encoding) from 256 up to 65535. This field indicates the type of the Information Element and the valid values of the IE type Extension field are defined in clause 8.1. The semantics of the Length and Instance field remain the same as specified in clause 8.2.1. | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 8.2.1A |
1,488 | 5.1.4 Random Access Response reception | Once the Random Access Preamble is transmitted and regardless of the possible occurrence of a measurement gap or a Sidelink Discovery Gap for Transmission or a Sidelink Discovery Gap for Reception, and regardless of the prioritization of V2X sidelink communication described in clause 5.14.1.2.2, the MAC entity shall monitor the PDCCH of the SpCell for Random Access Response(s) identified by the RA-RNTI defined below, in the RA Response window which starts at the subframe that contains the end of the preamble transmission,as specified in TS 36.211[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation ] [7], plus three subframes and has length ra-ResponseWindowSize. If the UE is a BL UE or a UE in enhanced coverage: - if the random access preamble was transmitted in a non-terrestrial network: - RA Response window starts at the subframe that contains the end of the last preamble repetition plus 3 subframes plus UE-eNB RTT and has length ra-ResponseWindowSize for the corresponding enhanced coverage level; - else: - RA Response window starts at the subframe that contains the end of the last preamble repetition plus three subframes and has length ra-ResponseWindowSize for the corresponding enhanced coverage level. If the UE is an NB-IoT UE: - if the random access preamble was transmitted in a non-terrestrial network: - RA Response window starts at the subframe that contains the end of the last preamble repetition plus X subframes plus UE-eNB RTT and has length ra-ResponseWindowSize for the corresponding enhanced coverage level, where value X is determined from Table 5.1.4-1 based on the used preamble format and the number of NPRACH repetitions; - else: - RA Response window starts at the subframe that contains the end of the last preamble repetition plus X subframes and has length ra-ResponseWindowSize for the corresponding enhanced coverage level, where value X is determined from Table 5.1.4-1 based on the used preamble format and the number of NPRACH repetitions. Table 5.1.4-1: Subframes between preamble transmission and RA Response Window in NB-IoT The RA-RNTI associated with the PRACH in which the Random Access Preamble is transmitted, is computed as: RA-RNTI= 1 + t_id + 10*f_id where t_id is the index of the first subframe of the specified PRACH (0≤ t_id <10), and f_id is the index of the specified PRACH within that subframe, in ascending order of frequency domain (0≤ f_id< 6) except for NB-IoT UEs, BL UEs or UEs in enhanced coverage. If the PRACH resource is on a TDD carrier, the f_id is set to , where is defined in clause 5.7.1 of TS 36.211[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation ] [7]. For BL UEs and UEs in enhanced coverage, RA-RNTI associated with the PRACH in which the Random Access Preamble is transmitted, is computed as: RA-RNTI=1+t_id + 10*f_id + 60*(SFN_id mod (Wmax/10)) where t_id is the index of the first subframe of the specified PRACH (0≤ t_id <10), f_id is the index of the specified PRACH within that subframe, in ascending order of frequency domain (0≤ f_id< 6), SFN_id is the index of the first radio frame of the specified PRACH, and Wmax is 400, maximum possible RAR window size in subframes for BL UEs or UEs in enhanced coverage. If the PRACH resource is on a TDD carrier, the f_id is set to , where is defined in clause 5.7.1 of TS 36.211[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation ] [7]. For NB-IoT UEs, the RA-RNTI associated with the PRACH in which the Random Access Preamble is transmitted, is computed as: RA-RNTI=1 + floor(SFN_id/4) + 256*carrier_id where SFN_id is the index of the first radio frame of the specified PRACH and carrier_id is the index of the UL carrier associated with the specified PRACH. The carrier_id of the anchor carrier is 0. For NB-IoT UEs operating in TDD mode, the RA-RNTI associated with the PRACH in which the Random Access Preamble is transmitted, is computed as: RA-RNTI = 1 + floor(SFN_id/4) + 256*(H-SFN mod 2) where SFN_id is the index of the first radio frame of the specified PRACH and H-SFN is the index of the first hyper frame of the specified PRACH. The PDCCH transmission and the PRACH resource are on the same carrier. The MAC entity may stop monitoring for Random Access Response(s) after successful reception of a Random Access Response containing Random Access Preamble identifiers that matches the transmitted Random Access Preamble. - If a downlink assignment for this TTI has been received on the PDCCH for the RA-RNTI and the received TB is successfully decoded, the MAC entity shall regardless of the possible occurrence of a measurement gap or a Sidelink Discovery Gap for Transmission or a Sidelink Discovery Gap for Reception, and regardless of the prioritization of V2X sidelink communication described in clause 5.14.1.2.2: - if the Random Access Response contains a Backoff Indicator subheader: - set the backoff parameter value as indicated by the BI field of the Backoff Indicator subheader and Table 7.2-1, except for NB-IoT where the value from Table 7.2-2 is used. - else, set the backoff parameter value to 0 ms. - if the Random Access Response contains a Random Access Preamble identifier corresponding to the transmitted Random Access Preamble (see clause 5.1.3), the MAC entity shall: - consider this Random Access Response reception successful and apply the following actions for the serving cell where the Random Access Preamble was transmitted: - process the received Timing Advance Command (see clause 5.2); - indicate the preambleInitialReceivedTargetPower and the amount of power ramping applied to the latest preamble transmission to lower layers (i.e., (PREAMBLE_TRANSMISSION_COUNTER – 1) * powerRampingStep); - if the SCell is configured with ul-Configuration-r14, ignore the received UL grant otherwise process the received UL grant value and indicate it to the lower layers; - if, except for NB-IoT, ra-PreambleIndex was explicitly signalled and it was not 000000 (i.e., not selected by MAC): - consider the Random Access procedure successfully completed. - else if, the UE is an NB-IoT UE, ra-PreambleIndex was explicitly signalled and it was not 000000 (i.e., not selected by MAC) and ra-CFRA-Config is configured: - consider the Random Access procedure successfully completed. - the UL grant provided in the Random Access Response message is valid only for the configured carrier (i.e. UL carrier used prior to this Random Access procedure). - else: - if the Random Access Preamble was selected by the MAC entity; or - if the UE is an NB-IoT UE, the ra-PreambleIndex was explicitly signalled and it was not 000000 and ra-CFRA-Config is not configured: - set the Temporary C-RNTI to the value received in the Random Access Response message no later than at the time of the first transmission corresponding to the UL grant provided in the Random Access Response message; - if the Random Access Preamble associated with EDT was transmitted and UL grant provided in the Random Access Response message is not for EDT: - indicate to upper layers that EDT is cancelled due to UL grant not being for EDT; - for CP-EDT, flush the Msg3 buffer. - for UP-EDT, update the MAC PDU in the Msg3 buffer in accordance with the uplink grant received in the Random Access Response. - if the Random Access Preamble associated with EDT was transmitted, the UL grant was received in a Random Access Response for EDT, and there is a MAC PDU in the Msg3 buffer: - if the TB size according to edt-SmallTBS-Enabled and as described in clause 8.6.2 and 16.3.3 of TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [2] does not match the size of the MAC PDU in the Msg3 buffer: - the MAC entity shall update the MAC PDU in the Msg3 buffer in accordance with the TB size. - if this is the first successfully received Random Access Response within this Random Access procedure; or - if CP-EDT is cancelled due to the UL grant provided in the Random Access Response message not being for EDT: - if the transmission is not being made for the CCCH logical channel, indicate to the Multiplexing and assembly entity to include a C-RNTI MAC control element in the subsequent uplink transmission; - obtain the MAC PDU to transmit from the "Multiplexing and assembly" entity and store it in the Msg3 buffer. NOTE 1: When an uplink transmission is required, e.g., for contention resolution, the eNB should not provide a grant smaller than 56 bits (or 88 bits for NB-IoT) in the Random Access Response. NOTE 2: If within a Random Access procedure, an uplink grant provided in the Random Access Response for the same group of Random Access Preambles has a different size than the first uplink grant allocated during that Random Access procedure, the UE behavior is not defined except for EDT. If no Random Access Response or, for NB-IoT UEs, BL UEs or UEs in enhanced coverage for mode B operation, no PDCCH scheduling Random Access Response is received within the RA Response window, or if none of all received Random Access Responses contains a Random Access Preamble identifier corresponding to the transmitted Random Access Preamble, the Random Access Response reception is considered not successful and the MAC entity shall: - if the notification of power ramping suspension has not been received from lower layers: - increment PREAMBLE_TRANSMISSION_COUNTER by 1; - if the UE is an NB-IoT UE, a BL UE or a UE in enhanced coverage: - if PREAMBLE_TRANSMISSION_COUNTER = preambleTransMax-CE + 1: - if the Random Access Preamble is transmitted on the SpCell: - indicate a Random Access problem to upper layers; - if NB-IoT: - consider the Random Access procedure unsuccessfully completed; - else: - if PREAMBLE_TRANSMISSION_COUNTER = preambleTransMax + 1: - if the Random Access Preamble is transmitted on the SpCell: - indicate a Random Access problem to upper layers; - if the Random Access Preamble is transmitted on an SCell: - consider the Random Access procedure unsuccessfully completed. - if in this Random Access procedure, the Random Access Preamble was selected by MAC: - based on the backoff parameter, select a random backoff time according to a uniform distribution between 0 and the Backoff Parameter Value; - delay the subsequent Random Access transmission by the backoff time; - else if the SCell where the Random Access Preamble was transmitted is configured with ul-Configuration-r14: - delay the subsequent Random Access transmission until the Random Access Procedure is initiated by a PDCCH order with the same ra-PreambleIndex and ra-PRACH-MaskIndex; - if the UE is an NB-IoT UE, a BL UE or a UE in enhanced coverage: - increment PREAMBLE_TRANSMISSION_COUNTER_CE by 1; - if PREAMBLE_TRANSMISSION_COUNTER_CE = maxNumPreambleAttemptCE for the corresponding enhanced coverage level + 1: - reset PREAMBLE_TRANSMISSION_COUNTER_CE; - consider to be in the next enhanced coverage level, if it is supported by the Serving Cell and the UE, otherwise stay in the current enhanced coverage level; - if the UE is an NB-IoT UE: - if the Random Access Procedure was initiated by a PDCCH order: - select the PRACH resource in the list of UL carriers providing a PRACH resource for the selected enhanced coverage level for which the carrier index is equal to ((Carrier Indication from the PDCCH order) modulo (Number of PRACH resources in the selected enhanced coverage)); - consider the selected PRACH resource as explicitly signalled; - proceed to the selection of a Random Access Resource (see clause 5.1.2). | 3GPP TS 36.321 | Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification | RAN2 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 5.1.4 |
1,489 | 4.5.10 Distribution of DL total PRB ssage | a) This measurement provides the distribution of samples with total usage (in percentage) of physical resource blocks (PRBs) on the downlink in different ranges. This measurement is a useful measure of whether a cell is under high loads or not in the scenario which a cell in the downlink may experience high load in certain short times (e.g. in a second) and recover to normal very quickly. b) CC c) Each measurement sample is obtained according to the definition in TS 36.314[ Evolved Universal Terrestrial Radio Access (E-UTRA); Layer 2 - Measurements ] [11] clause 4.1.10.1. Depending on the value of the sample, the proper bin of the counter is increased. The number of samples during one measurement period is provided by the operator. d) A set of integers. Each representing the (integer) number of samples with a DL total PRB percentage usage in the range represented by that bin. e) RRU.PrbTotDlDist.BinX, which indicates the distribution of DL PRB Usage for all traffic. f) EUtranCellFDD EUtranCellTDD g) Valid for packet switched traffic h) EPS i) The distribution information is a key input to network capacity planning and load balancing. | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.5.10 |
1,490 | 4.22.2.3 MA PDU Session establishment with 3GPP access connected to EPC and non-3GPP access connected to 5GC 4.22.2.3.1 General | This clause applies to the case where, for a PDU Session, multi-access connectivity via both EPC (over 3GPP access) and 5GC (over non-3GPP access) is supported and allowed in the UE and network. In this case, multi-access connectivity using ATSSS via both 3GPP access to EPC and non-3GPP access to 5GC may be provided as described in this clause. For this scenario, the general principles for ATSSS as described in clause 5.32 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] apply, with the additions provided in this clause 4.22.2.3. A Multi-Access PDU Session may be extended with user-plane resources via an associated PDN Connection on 3GPP access in EPC. This enables a scenario where a MA PDU Session can simultaneously be associated with user-plane resources on 3GPP access network connected to EPC and non-3GPP access connected to 5GC. Such a PDN Connection in EPS would thus be associated with multi-access capability in the UE and PGW-C+SMF. NOTE: To the MME and SGW this is a regular PDN Connection and the support for ATSSS is transparent to MME and SGW. The UE may operate in either single-registration mode or dual-registration mode in 3GPP access. Irrespective of whether the UE operates in single-registration mode or dual-registration mode in 3GPP access, it is assumed that the UE supports simultaneous registrations for non-3GPP access in 5GC and 3GPP access in EPC. The ATSSS rules are provided from the PGW-C+SMF to the UE via SM NAS signalling over 5GC, as described in clause 5.32.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. ATSSS rules are not provided via the EPC. When a UE establishes a MA PDU Session in 5GS, the UE indicates whether it supports 3GPP access leg over EPC. Based on the UE capability, the SMF determines whether the non-3GPP access should be released or not when the MA PDU Session is moved to EPS as described in clause 4.22.6.2. After the establishment of a MA PDU Session and setting up user-plane resources in 3GPP access in EPC and non-3GPP access in 5GC, the UE distributes the uplink traffic across the two access networks as described in clause 5.32.1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. Similarly, the PDU Session Anchor UPF performs distribution of downlink traffic across the two access networks as described in clause 5.32.1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The PMF protocol may be used via any user plane connection, i.e. via 3GPP access in EPC or non-3GPP access in 5GC. The PCF functionality to support ATSSS, as described in clause 5.32.1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] and TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20] applies also in the case of interworking with EPC. When the 3GPP access leg of a MA PDU Session using both 3GPP and non-3GPP access connected to 5GC is transferred to EPC, the PDU Session continues to work as a MA PDU Session using E-UTRAN/EPC and non-3GPP access connected to 5GC, as described in clause 4.22.6. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.22.2.3 |
1,491 | 14.10 Soft buffer test (CA) | The purpose of this test is to verify the maximum number of bits per TTI supported by the V2X UE with UE SL-C-RX Category 4 for UEs supporting V2X CA. For CA with 2 SL CCs, the requirements are specified in Table 14.10-3, based on single carrier requirement specified in Table 14.10-2, with the test parameters specified in Table 14.10-1. For CA with 3 SL CCs, the requirements are specified in Table 14.10-4, based on single carrier requirement specified in Table 14.10-2, with the test parameters specified in Table 14.10-1. Table 14.10-1: Test Parameters Table 14.10-2: Single carrier performance with different bandwidths for multiple CA configurations Table 14.10-3: Minimum performance for CA with 2 SL CCs Table 14.10-4: Minimum performance for CA with 3 SL CCs | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 14.10 |
1,492 | 5.5.2.2.5 Abnormal cases on the network side | The following abnormal cases can be identified: a) Detach request received in a CSG cell for which the UE has no valid CSG subscription If the UE initiates a detach procedure in a CSG cell the CSG ID of which is not valid for the UE, and the detach procedure is not due to "switch off", the network shall proceed as follows: - if the detach type is "IMSI detach" and the UE has a PDN connection for emergency bearer services active, the MME shall send a DETACH ACCEPT message and deactivate all non-emergency EPS bearers, if any, by initiating an EPS bearer context deactivation procedure; - otherwise, the network shall initiate the detach procedure. The MME shall send a DETACH REQUEST message including the EMM cause #25,"not authorized for this CSG". b) Lower layers indication of non-delivered NAS PDU due to handover If the DETACH ACCEPT message could not be delivered due to an intra MME handover and the target TA is included in the TAI list, then upon successful completion of the intra MME handover the MME shall retransmit the DETACH ACCEPT message. If a failure of the handover procedure is reported by the lower layer and the S1 signalling connection exists, the MME shall retransmit the DETACH ACCEPT message. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.5.2.2.5 |
1,493 | 4.11.0a.11 SMF+PGW-C initiated bearer modification without bearer QoS update | To support URSP Provisioning in EPS, the following enhancement to clause 5.4.3 of TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13] applies: - Step 1 The PCF provides UE Policy Container, which is received from the PCF for the UE as specified in clause 4.11.0a.2a.6, to the SMF+PGW-C in (PCF-initiated) IP-CAN Session Modification procedure as specified in clause 4.11.0a.3. - Steps 2~5 The UE Policy Container in ePCO is sent by the SMF+PGW-C to the UE via SGW and MME - Steps 6~9 The UE sends UE Policy delivery result to the SMF+PGW-C via MME and SGW. - Steps 10 The SMF+PGW-C reports the UE Policy delivery result to the PCF as specified in clause 4.11.0a.2a.2.3. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.11.0a.11 |
1,494 | 5.30 Support for non-public networks 5.30.1 General | A Non-Public Network (NPN) is a 5GS deployed for non-public use, see TS 22.261[ Service requirements for the 5G system ] [2]. An NPN is either: - a Stand-alone Non-Public Network (SNPN), i.e. operated by an NPN operator and not relying on network functions provided by a PLMN, or - a Public Network Integrated NPN (PNI-NPN), i.e. a non-public network deployed with the support of a PLMN. NOTE: An NPN and a PLMN can share NG-RAN as described in clause 5.18. Stand-alone NPN are described in clause 5.30.2 and Public Network Integrated NPNs are described in clause 5.30.3. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.30 |
1,495 | 5.6.2.3.3 Abnormal cases on the network side | The following abnormal case can be identified: a) Void b) ATTACH REQUEST message received when paging procedure is ongoing. If an integrity-protected ATTACH REQUEST message is received from the UE and successfully integrity checked by the network, the network shall abort the paging procedure. If the ATTACH REQUEST message received is not integrity protected, or the integrity check is unsuccessful, the paging procedure shall be progressed. The paging procedure shall be aborted when the EPS authentication procedure performed during attach procedure is completed successfully. c) TRACKING AREA UPDATE REQUEST message received in response to a CS SERVICE NOTIFICATION message If the network receives a TRACKING AREA UPDATE REQUEST message in response to a CS SERVICE NOTIFICATION message, the network shall progress the tracking area updating procedure. NOTE: After completion of the tracking area updating procedure the UE can accept or reject the CS fallback by sending an EXTENDED SERVICE REQUEST message. d) DETACH REQUEST message received in response to a CS SERVICE NOTIFICATION message If the network receives a DETACH REQUEST message with detach type "IMSI detach" or "combined EPS/IMSI detach" in response to a CS SERVICE NOTIFICATION message, the network shall progress the detach procedure. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.6.2.3.3 |
1,496 | 13.2.3.5 Provisioning of the policies in the SEPP | The SEPP shall contain an interface that the operator can use to manually configure the protection policies in the SEPP. The SEPP shall be able to store and process the following policies for outgoing messages: - A generic data-type encryption policy; - Roaming partner specific data-type encryption policies that will take precedence over a generic data-type encryption policy if present; - NF API data-type placement mappings; - Multiple modification policies, to handle modifications that are specific per IPX provider and modification policies that are specific per IPX provider and roaming partner. The SEPP shall also be able to store and process the following policies for incoming messages during the initial connection establishment via N32-c: - Roaming partner specific data-type encryption policies; - Roaming partner specific modification policies that specify which fields can be modified by which of its IPX providers. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 13.2.3.5 |
1,497 | 8.13.1.1.2 Minimum Requirement Multi-Layer Spatial Multiplexing 4 Tx Antenna Port for dual connectivity | For dual connectivity the requirements are specified in Table 8.13.1.1.2-3 for 2DL CCs and Table 8.13.1.1.2-4 for 3DL CCs, based on single carrier requirement specified in Table 8.13.1.1.2-2, with the addition of the parameters in Table 8.13.1.1.2-1 and the downlink physical channel setup according to Annex C.3.2. The purpose of these tests is to verify the closed loop rank-two performance with wideband and frequency selective precoding by using dual connectivity transmission. Table 8.13.1.1.2-1: Test Parameters for Multi-Layer Spatial Multiplexing (FRC) for dual connectivity Table 8.13.1.1.2-2: Single carrier performance for multiple DC configurations Table 8.13.1.1.2-3: Minimum performance Multi-Layer Spatial Multiplexing (FRC) for dual connectivity with 2 DL CCs Table 8.13.1.1.2-4: Minimum performance Multi-Layer Spatial Multiplexing (FRC) for dual connectivity with 3DL CCs | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.13.1.1.2 |
1,498 | 4.23.11.4 Xn based handover with removal of intermediate SMF | This procedure is used to hand over a UE from a Source NG-RAN to a Target NG-RAN using Xn interface(in this case the AMF is unchanged) and the AMF decides that removal of intermediate I-SMF is needed. This procedure is used for non-roaming or local breakout roaming scenario. The call flow is shown in figure 4.23.11.4-1. Figure 4.23.11.4-1: Xn based inter NG-RAN handover with removal of intermediate SMF 1. Step 1 is the same as described in clause 4.9.1.2.2. 2. For each PDU Session Rejected in the list of PDU Sessions received in the N2 Path Switch Request, the AMF sends Nsmf_PDUSession_UpdateSMContext Request to source I-SMF and then the source I-SMF sends the Nsmf_PDUSession_Update Request to SMF forwarding the failure cause. The SMF decides whether to release the PDU Session. The rest of this procedure applies for each PDU Session To Be Switched. 3a. The AMF performs I-SMF selection as described in clause 5.34.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] and the AMF decides to remove I-SMF in this case. 3b. The AMF sends Nsmf_PDUSession_CreateSMContext Request (SUPI, PDU Session ID, AMF ID, PDU Session To Be Switched with N2 SM Information (Secondary RAT usage data), UE Location Information, UE presence in LADN service area, Target NG-RAN Tunnel Info) to the SMF. 4a. [Conditional] SMF to I-UPF: N4 Session Establishment Request (Target NG-RAN Tunnel Info, UL CN Tunnel Info of the UPF (PSA)). The SMF may select an I-UPF based on UPF Selection Criteria according to clause 6.3.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If an I-UPF is selected, an N4 Session Establishment Request message is sent to the I-UPF. The target NG-RAN Tunnel Info is included in the N4 Session Establishment Request message. 4b. I-UPF to SMF: N4 Session Establishment Response. The I-UPF sends an N4 Session Establishment Response message to the I-SMF. The UL and DL CN Tunnel Info of I-UPF is sent to the I-SMF. 5a. SMF to UPF (PSA): N4 Session Modification Request (DL CN Tunnel Info of the I-UPF if I-UPF is selected, or Target NG-RAN Tunnel Info if I-UPF is not selected). The SMF provides the DL CN Tunnel Info of the I-UPF to the UPF (PSA) if I-UPF is selected. If an I-UPF is not selected, the SMF provides the target NG-RAN Tunnel Info to the UPF (PSA). If different CN Tunnel Info need to be used by PSA UPF, i.e. the CN Tunnel Info for N3 and N9 are different, the SMF retrieves the new CN Tunnel Info from UPF. 5b. UPF (PSA) to SMF: N4 Session Modification Response. If different CN Tunnel Info needs to be used by PSA UPF, i.e. the CN Tunnel Info for N3 and N9 are different, the CN Tunnel Info is allocated by the UPF and provided to the SMF. The PDU Session Anchor responds with the N4 Session Modification Response message after requested PDU Sessions are switched. PDU Session Anchor sends one or more "end marker" packets for each N3/N9 tunnel on the old path immediately after switching the path, the source NG-RAN shall forward the "end marker" packets to the target NG-RAN. At this point, PDU Session Anchor starts sending downlink packets to the Target NG-RAN via I-UPF. 6a. [Conditional] SMF to I-UPF: N4 Session Modification Request (UL CN Tunnel Info of the UPF (PSA)). If the UL CN Tunnel Info of the UPF (PSA) has been changed, the SMF provides the UL CN Tunnel Info of the UPF (PSA) to I-UPF. 6b. I-UPF to SMF: N4 Session Modification Response. The I-UPF responds with the N4 Session Modification Response message. 7. In order to assist the reordering function in the Target NG-RAN, the PDU Session Anchor sends one or more "end marker" packets for each N3/N9 tunnel on the old path immediately after switching the path, the source NG-RAN shall forward the "end marker" packets to the target NG-RAN. 8. SMF to AMF: Nsmf_PDUSession_CreateSMContext Response (UL CN Tunnel Info of the I-UPF if I-UPF is selected, or CN Tunnel Info (on N3) of UPF (PSA) if I-UPF is not selected, updated CN PDB in the QoS parameters for accepted QoS Flows). The SMF may update the CN PDB in the response or using a separate PDU Session Modification procedure, based on local configuration. The SMF sends an Nsmf_PDUSession_CreateSMContext response to the AMF. 9. Step 9 is same as step 7 defined in clause 4.9.1.2.2. 10a. AMF to source I-SMF: Nsmf_PDUSession_ReleaseSMContext request (I-SMF only Indication). The AMF sends Nsmf_PDUSession_ReleaseSMContext request to source I-SMF. The I-SMF only indication is included in this message to avoid invoking resource release in SMF. 10b. Source I-SMF to source I-UPF: N4 Session Release Request/Response. The source I-SMF sends N4 Session Release Request to source I-UPF in order to release resources for the PDU Session. 10c. Source I-SMF to AMF: Nsmf_PDUSession_ReleaseSMContext Response. The source I-SMF responds to AMF with Nsmf_PDUSession_ReleaseSMContext response. 11-12. Steps 11-12 are same as steps 8-9 defined in clause 4.9.1.2.2. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.23.11.4 |
1,499 | 4.15.6.7 Service specific parameter provisioning 4.15.6.7.1 General | This clause describes the procedures for enabling the AF to provide service specific parameters to 5G system via NEF. The AF may issue requests on behalf of applications not owned by the PLMN serving the UE. NOTE 1: In the case of architecture without CAPIF support, the AF is locally configured with the API termination points for the service. In the case of architecture with CAPIF support, the AF obtains the service API information from the CAPIF core function via the Availability of service APIs event notification or Service Discover Response as specified in TS 23.222[ Common API Framework for 3GPP Northbound APIs ] [54]. The AF request sent to the NEF contains the information as below: 1) Service Description. Service Description is the information to identify a service the Service Parameters are applied to. The Service Description in the AF request can be represented by the combination of DNN and S-NSSAI, an AF-Service-Identifier or an External Application Identifier. 2) Service Parameters. Service Parameters are the service specific information which needs to be provisioned in the Network and delivered to the UE in order to support the service identified by the Service Description. VPLMN ID(s) that indicates the PLMN(s) where the AF guidance on URSP determination and all its RSD(s), applies. 3) Target UE(s) or a group of UEs or PLMN ID(s) of inbound roamers. Target UE(s) or a group of UEs or PLMN ID(s) of inbound roamers indicate the UE(s) who the Service Parameters shall be delivered to. Individual UEs can be identified by GPSI, or an IP address/Prefix or a MAC address. Groups of UEs are identified by an External Group Identifiers as defined in TS 23.682[ Architecture enhancements to facilitate communications with packet data networks and applications ] [23]. If identifiers of target UE(s) or a group of UEs or PLMN ID(s) of inbound roamers are not provided, then the Service Parameters shall be delivered to any UEs of the PLMN of the NEF using the service identified by the Service Description. 4) Subscription to events. The AF may subscribe to notifications about the outcome of the UE Policies delivery due to service specific parameter provisioning. The NEF authorizes the AF request received from the AF and stores the information in the UDR as "Application Data". The Service Parameters are delivered to the targeted UE by the PCF when the UE is reachable. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.15.6.7 |
1,500 | 17.5.3 Session stop procedure | The BM-SC initiates the MBMS session stop procedure when it considers the MBMS session terminated. Typically this will happen when there is no more MBMS data expected to be transmitted for a sufficiently long period of time to justify the release of bearer plane resources in the network. Figure 28: MBMS Session Stop procedure 1. The BM-SC sends a RAR message to all GGSNs listed in the "list of downstream nodes" parameter of the affected MBMS Bearer Context to indicate that the MBMS session is terminated and the bearer plane resources can be released. 2. The GGSN sets the state attribute of its MBMS Bearer Context to ‘Standby’ and sends a RAA message to the BM-SC. An AAR message is not mandated for the Gmb application in response to a RAR- RAA command exchange. | 3GPP TS 29.061 | Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) | CT WG3 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 17.5.3 |
Subsets and Splits