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
β |
|---|---|---|---|---|---|---|---|
4,801 | 5.7.3 Carrier frequency and EARFCN | The carrier frequency in the uplink and downlink is designated by the E-UTRA Absolute Radio Frequency Channel Number (EARFCN) in the range 0 β 262143. The relation between EARFCN and the carrier frequency in MHz for the downlink is given by the following equation, where FDL_low and NOffs-DL are given in Table 5.7.3-1 and NDL is the downlink EARFCN. FDL = FDL_low + 0.1(NDL β NOffs-DL) The relation between EARFCN and the carrier frequency in MHz for the uplink is given by the following equation where FUL_low and NOffs-UL are given in Table 5.7.3-1 and NUL is the uplink EARFCN. FUL = FUL_low + 0.1(NUL β NOffs-UL) Table 5.7.3-1: E-UTRA channel numbers | 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 | 5.7.3 |
4,802 | 5.9.7 Internal-Group Identifier | The subscription data for an UE in UDR may associate the subscriber with groups. A group is identified by an Internal-Group Identifier. NOTE 1: A UE can belong to a limited number of groups, the exact number is defined in stage 3 specifications. NOTE 2: In this Release of the specification, the support of groups is only defined in non-roaming case. The Internal-Group Identifier(s) corresponding to an UE are provided by the UDM to the SMF as part Session Management Subscription data and (when PCC applies to a PDU Session) by the SMF to the PCF. The SMF may use this information to apply local policies and to store this information in CDR. The PCF may use this information to enforce AF requests as described in clause 5.6.7. The Internal-Group Identifier(s) corresponding to an UE are provided by the UDM to the AMF as part of Access and Mobility Subscription data. The AMF may use this information to apply local policies (such as Group specific NAS level congestion control defined in clause 5.19.7.5). | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.9.7 |
4,803 | 16.9.3.2 Scheduled Resource Allocation | NG-RAN can dynamically allocate resources to the UE via the SL-RNTI on PDCCH(s) for NR sidelink communication. In addition, NG-RAN can allocate sidelink resources to a UE with two types of configured sidelink grants: - With type 1, RRC directly provides the configured sidelink grant only for NR sidelink communication; - With type 2, RRC defines the periodicity of the configured sidelink grant while PDCCH can either signal and activate the configured sidelink grant, or deactivate it. The PDCCH is addressed to SL-CS-RNTI for NR sidelink communication. Besides, NG-RAN can also semi-persistently allocate sidelink resources to the UE via the SL Semi-Persistent Scheduling V-RNTI on PDCCH(s) for V2X sidelink communication. For the UE performing NR sidelink communication, there can be more than one configured sidelink grant activated at a time on the carrier configured for sidelink transmission. When beam failure or physical layer problem occurs on MCG, the UE can continue using the configured sidelink grant Type 1 until initiation of the RRC connection re-establishment procedure as specified in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [12]. During handover, the UE can be provided with configured sidelink grants via handover command, regardless of the type. If provided, the UE activates the configured sidelink grant Type 1 upon reception of the handover command or execution of CHO. The UE can send sidelink buffer status report to support scheduler operation in NG-RAN. For NR sidelink communication, the sidelink buffer status reports refer to the data that is buffered in for a group of logical channels (LCG) per destination in the UE. Eight LCGs are used for reporting of the sidelink buffer status reports. Two formats, which are SL BSR and truncated SL BSR, are used. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.9.3.2 |
4,804 | 5.16.4.6 QoS for Emergency Services | Local regulation may require supporting emergency calls from an unauthorised UE. In such a case, the SMF may not have subscription data. Additionally, the local network may want to provide Emergency Services support differently than what is allowed by a UE subscription. Therefore, the initial QoS parameters used for establishing Emergency Services are configured in the V-SMF (local network) in the SMF Emergency Configuration Data. This functionality is used by the UE Requested PDU Session Establishment procedure when establishing Emergency Services. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.16.4.6 |
4,805 | 4.4.2.1 Architecture to support SMS over NAS | Figure 4.4.2.1-1 shows the non-roaming architecture to support SMS over NAS using the Service-based interfaces within the Control Plane. Figure 4.4.2.1-1: Non-roaming System Architecture for SMS over NAS Figure 4.4.2.1-2 shows the non-roaming architecture to support SMS over NAS using the reference point representation. Figure 4.4.2.1-2: Non-roaming System Architecture for SMS over NAS in reference point representation NOTE 1: SMS Function (SMSF) may be connected to the SMS-GMSC/IWMSC/SMS Router via one of the standardized interfaces as shown in TS 23.040[ Technical realization of the Short Message Service (SMS) ] [5]. NOTE 2: UDM may be connected to the SMS-GMSC/IWMSC/SMS Router via one of the standardized interfaces as shown in TS 23.040[ Technical realization of the Short Message Service (SMS) ] [5]. NOTE 3: Each UE is associated with only one SMS Function in the registered PLMN. NOTE 4: SMSF re-allocation while the UE is in RM-REGISTERED state in the serving PLMN is not supported in this Release of the specification. When serving AMF is re-allocated for a given UE, the source AMF includes SMSF identifier as part of UE context transfer to target AMF. If the target AMF, e.g. in the case of inter-PLMN mobility, detects that no SMSF has been selected in the serving PLMN, then the AMF performs SMSF selection as specified in clause 6.3.10. NOTE 5: To support MT SMS domain selection by IP-SM-GW/SMS Router, IP-SM-GW/SMS Router may connect to SGs MSC, MME and SMSF via one of the standardized interfaces as shown in TS 23.040[ Technical realization of the Short Message Service (SMS) ] [5]. Figure 4.4.2.1-3 shows the roaming architecture to support SMS over NAS using the Service-based interfaces within the Control Plane. Figure 4.4.2.1-3: Roaming architecture for SMS over NAS Figure 4.4.2.1-4 shows the roaming architecture to support SMS over NAS using the reference point representation. Figure 4.4.2.1-4: Roaming architecture for SMS over NAS in reference point representation | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.4.2.1 |
4,806 | 6.2.4 UE maximum output power with additional requirements | Additional ACLR and spectrum emission requirements can be signalled by the network to indicate that the UE shall also meet additional requirements in a specific deployment scenario. To meet these additional requirements, Additional Maximum Power Reduction (A-MPR) is allowed for the output power as specified in Table 6.2.2-1. Unless stated otherwise, an A-MPR of 0 dB shall be used. For UE Power Class 1, 2 and 3 the specific requirements and identified subclauses are specified in Table 6.2.4-1 along with the allowed A-MPR values that may be used to meet these requirements. The allowed A-MPR values specified in tables of this clause are in addition to the allowed MPR requirements specified in subclause 6.2.3. Table 6.2.4-1: Additional Maximum Power Reduction (A-MPR) Table 6.2.4-2: A-MPR for "NS_07" Table 6.2.4-3: A-MPR for "NS_10" Table -4: A-MPR requirements for "NS_04" for Power Class 3 UE Table -4a: A-MPR requirements for "NS_04" for Power Class 2 UE For a power class 2 capable UE operating in Band 41, A-MPR according to Table 6.2.4-4 for power class 3 is allowed when an IE P-max as defined in [7] of 23 dBm or lower is indicated in the cell or if the uplink/downlink configuration is 0 or 6. Table 6.2.4-5: A-MPR for "NS_11" Table 6.2.4-6: A-MPR for "NS_12" Table 6.2.4-7: A-MPR for "NS_13" Table 6.2.4-8: A-MPR for "NS_14" Table 6.2.4-9: A-MPR for "NS_15" for E-UTRA highest channel edge > 845 MHz and β€ 849 MHz Table 6.2.4-10: A-MPR for "NS_15" for E-UTRA highest channel edge β€ 845 MHz Table 6.2.4-11: A-MPR for "NS_16" with channel lower edge at β₯807 MHz and <808.5 MHz Table 6.2.4-12: A-MPR for "NS_16" with channel lower edge at β₯808.5 MHz and <812 MHz Table 6.2.4-13: A-MPR for "NS_16" with channel lower edge at β₯812 MHz Table 6.2.4-14: A-MPR for "NS_19" Table 6.2.4-15: A-MPR for "NS_20" Table 6.2.4-16: A-MPR for "NS_21" Table 6.2.4-17: A-MPR for "NS_22" Table 6.2.4-18: A-MPR for "NS_05" Table 6.2.4-18E: A-MPR requirements for "NS_05" for Cat-M2 power class 3 UE Table 6.2.4-19: A-MPR for "NS_24" Table 6.2.4-20: A-MPR for "NS_25" Table 6.2.4-21: A-MPR for "NS_26" Table 6.2.4-22: A-MPR for "NS_27" Table 6.2.4-23: A-MPR for "NS_28" Table 6.2.4-24: A-MPR for "NS_29" Table 6.2.4-25: A-MPR for "NS_30" Table 6.2.4-26: A-MPR for "NS_31" Table 6.2.4-27: A-MPR for βNS_36β Table 6.2.4-28: A-MPR for "NS_38" Table 6.2.4-29: A-MPR for "NS_39" Table 6.2.4-30a: A-MPR for "NS_40" Table 6.2.4-30b: A-MPR for "NS_40" Table 6.2.4-31: A-MPR for "NS_41" Table 6.2.4-32: A-MPR for βNS_42β Table 6.2.4-32a: Void Table 6.2.4-32b: Void Table 6.2.4-33: A-MPR for βNS_43β Table 6.2.4-34: A-MPR requirements for βNS_44β for Power Class 2 UE Table 6.2.4-34a: A-MPR for "NS_56" Table 6.2.4-34b: A-MPR for "NS_06" for Power Class 1 UE in Band 12 For PRACH, PUCCH and SRS transmissions, the allowed A-MPR is according to that specified for PUSCH QPSK modulation for the corresponding transmission bandwidth. For each TTI pattern, the A-MPR shall be evaluated per Teval period as specified in table 6.2.4-35 and given by the maximum value taken over the transmission(s) within that period; the maximum A-MPR over the TREF is then applied for TREF. Table 6.2.4-35: A-MPR evaluation period For the UE maximum output power modified by A-MPR, the power limits specified in subclause 6.2.5 apply. Table 6.2.4-36: A-MPR requirements for NS_UAV_70 (Power Class 3) | 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.2.4 |
4,807 | 8.2.3.3.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.3.1-4 based on single carrier requirement specified in Table 8.2.3.3.1-2 and Table 8.2.3.3.1-3, with the addition of the parameters in Table 8.2.3.3.1-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. For TDD FDD CA with FDD PCell and 3DL CCs, the requirements are specified in Table 8.2.3.3.1-5 based on single carrier requirement specified in Table 8.2.3.3.1-2 and Table 8.2.3.3.1-3, with the addition of the parameters in Table 8.2.3.3.1-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. For TDD FDD CA with FDD PCell and 4DL CCs, the requirements are specified in Table 8.2.3.3.1-6 based on single carrier requirement specified in Table 8.2.3.3.1-2 and Table 8.2.3.3.1-3, with the addition of the parameters in Table 8.2.3.3.1-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. For TDD FDD CA with FDD PCell and 5DL CCs, the requirements are specified in Table 8.2.3.3.1-7 based on single carrier requirement specified in Table 8.2.3.3.1-2 and Table 8.2.3.3.1-3, with the addition of the parameters in Table 8.2.3.3.1-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. For TDD FDD CA with FDD PCell and 6DL CCs, the requirements are specified in Table 8.2.3.3.1-8 based on single carrier requirement specified in Table 8.2.3.3.1-2 and Table 8.2.3.3.1-3, with the addition of the parameters in Table 8.2.3.3.1-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. For TDD FDD CA with FDD PCell and 7DL CCs, the requirements are specified in Table 8.2.3.3.1-9 based on single carrier requirement specified in Table 8.2.3.3.1-2 and Table 8.2.3.3.1-3, with the addition of the parameters in Table 8.2.3.3.1-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. The test coverage for different number of component carriers is defined in 8.1.2.4. Table 8.2.3.3.1-1: Test Parameters for Multi-Layer Spatial Multiplexing (FRC) for CA Table 8.2.3.3.1-2: Single carrier performance with different bandwidths for multiple CA configurations for FDD PCell and SCell (FRC) Table 8.2.3.3.1-3: Single carrier performance with different bandwidths for multiple CA configurations for TDD SCell (FRC) Table 8.2.3.3.1-4: Minimum performance for multiple CA configurations with 2DL CCs (FRC) Table 8.2.3.3.1-5: Minimum performance for multiple CA configurations with 3DL CCs (FRC) Table 8.2.3.3.1-6: Minimum performance for multiple CA configurations with 4DL CCs (FRC) Table 8.2.3.3.1-7: Minimum performance for multiple CA configurations with 5DL CCs (FRC) Table 8.2.3.3.1-8: Minimum performance for multiple CA configurations with 6DL CCs (FRC) Table 8.2.3.3.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.3.1 |
4,808 | 6.12.1 Description | The increased density of access nodes needed to meet future performance objectives poses considerable challenges in deployment and management (e.g. backhaul availability, backhaul capacity and scalability). The use of wireless backhaul for such access nodes helps to address some of the challenges. Wireless self-backhauling in the radio access network can enable simpler deployment and incremental rollout by reducing reliance on the availability of wired backhaul at each access node location. Network planning and installation efforts can be reduced by leveraging plug and play type features -- self-configuration, self-organizing, and self-optimization. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.12.1 |
4,809 | 8.1.2.3B Applicability and test rules for different TDD-FDD CA configurations and bandwidth combination sets | The performance requirement for TDD-FDD CA UE demodulation tests in Clause 8 are defined independent of CA configurations and bandwidth combination sets specified in Clause 5.6A.1. For UEs supporting different CA configurations and bandwidth combination sets, the applicability and test rules are defined for the tests for 2 DL TDD-FDD CA in Table 8.1.2.3B-1 and in Table 8.1.2.3B-2 for 3 or more DL TDD-FDD CA. For simplicity, CA configuration below refers to combination of CA configuration and bandwidth combination set. Table 8.1.2.3B-1: Applicability and test rules for CA UE demodulation tests for TDD-FDD CA with 2 DL CCs Table 8.1.2.3B-2: Applicability and test rules for CA UE demodulation tests for TDD-FDD CA with 3 or more DL 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.1.2.3B |
4,810 | 5.3.5.7 AS Security key update | The UE shall: 1> if UE is connected to E-UTRA/EPC or E-UTRA/5GC: 2> upon reception of sk-Counter as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10]: 3> update the S-KgNB key based on the KeNB key and using the received sk-Counter value, as specified in TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [30] for EN-DC, or TS 33.501[ Security architecture and procedures for 5G System ] [11] for NGEN-DC; 3> derive the KRRCenc and KUPenc keys as specified in TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [30] for EN-DC, or TS 33.501[ Security architecture and procedures for 5G System ] [11] for NGEN-DC; 3> derive the KRRCint and KUPint keys as specified in TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [30] for EN-DC or TS 33.501[ Security architecture and procedures for 5G System ] [11] for NGEN-DC. 1> else if this procedure was initiated due to reception of the masterKeyUpdate: 2> if the nas-Container is included in the received masterKeyUpdate: 3> forward the nas-Container to the upper layers; 2> if the keySetChangeIndicator is set to true: 3> derive or update the KgNB key based on the KAMF key, as specified in TS 33.501[ Security architecture and procedures for 5G System ] [11]; 2> else: 3> derive or update the KgNB key based on the current KgNB key or the NH, using the nextHopChainingCount value indicated in the received masterKeyUpdate, as specified in TS 33.501[ Security architecture and procedures for 5G System ] [11]; 2> store the nextHopChainingCount value; 2> derive the keys associated with the KgNB key as follows: 3> if the securityAlgorithmConfig is included in SecurityConfig: 4> derive the KRRCenc and KUPenc keys associated with the cipheringAlgorithm indicated in the securityAlgorithmConfig, as specified in TS 33.501[ Security architecture and procedures for 5G System ] [11]; 4> derive the KRRCint and KUPint keys associated with the integrityProtAlgorithm indicated in the securityAlgorithmConfig, as specified in TS 33.501[ Security architecture and procedures for 5G System ] [11]; 3> else: 4> derive the KRRCenc and KUPenc keys associated with the current cipheringAlgorithm, as specified in TS 33.501[ Security architecture and procedures for 5G System ] [11]; 4> derive the KRRCint and KUPint keys associated with the current integrityProtAlgorithm, as specified in TS 33.501[ Security architecture and procedures for 5G System ] [11]. NOTE 1: Ciphering and integrity protection are optional to configure for the DRBs. 1> else if this procedure was initiated due to reception of the sk-Counter (UE is in NE-DC, or NR-DC, or is configured with SN terminated bearer(s)) or if the procedure was initiated due to selection of an sk-Counter for conditional reconfiguration execution for subsequent CPAC (UE is in NR-DC): 2> derive or update the secondary key (S-KgNB or S-KeNB) based on the KgNB key and using the received or selected sk-Counter value, as specified in TS 33.501[ Security architecture and procedures for 5G System ] [11]; 2> derive the KRRCenc key and the KUPenc key as specified in TS 33.501[ Security architecture and procedures for 5G System ] [11] using the ciphering algorithms indicated in the RadioBearerConfig associated with the secondary key (S-KgNB or S-KeNB) as indicated by keyToUse; 2> derive the KRRCint key and the KUPint key as specified in TS 33.501[ Security architecture and procedures for 5G System ] [11] using the integrity protection algorithms indicated in the RadioBearerConfig associated with the secondary key (S-KgNB or S-KeNB) as indicated by keyToUse; NOTE 2: If the UE has no radio bearer configured with keyToUse set to secondary and receives the sk-Counter without any RadioBearerConfig with keyToUse set to secondary, the UE does not consider it as an invalid reconfiguration. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.5.7 |
4,811 | β MeasObjectToAddModList | The IE MeasObjectToAddModList concerns a list of measurement objects to add or modify. MeasObjectToAddModList information element -- ASN1START -- TAG-MEASOBJECTTOADDMODLIST-START MeasObjectToAddModList ::= SEQUENCE (SIZE (1..maxNrofObjectId)) OF MeasObjectToAddMod MeasObjectToAddMod ::= SEQUENCE { measObjectId MeasObjectId, measObject CHOICE { measObjectNR MeasObjectNR, ..., measObjectEUTRA MeasObjectEUTRA, measObjectUTRA-FDD-r16 MeasObjectUTRA-FDD-r16, measObjectNR-SL-r16 MeasObjectNR-SL-r16, measObjectCLI-r16 MeasObjectCLI-r16, measObjectRxTxDiff-r17 MeasObjectRxTxDiff-r17, measObjectRelay-r17 SL-MeasObject-r16, measObjectNR-SL-v1800 MeasObjectNR-SL-v1800 } } -- TAG-MEASOBJECTTOADDMODLIST-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | β |
4,812 | 5.2.2.2.17 Namf_Communication_NonUeN2MessageTransfer service operation | Service operation name: Namf_Communication_NonUeN2MessageTransfer Description: NF Service Consumer requests to transfer a non-UE specific message to NG-RAN node(s) via N2. Input, Required: N2 Message Container. Input, Optional: TAI List, RAT Selector (ng-eNB or gNB), Global RAN Node List, Send Write-Replace-Warning-Indication, Send Stop-Warning-Indication. Output, Required: N2 Information Transfer Result. Output, Optional: PWS Result Data. PWS Result Data is included when parts of a PWS received message have not been comprehended or were missing, or if the message contained logical errors. It may contain the Unknown Tracking Area List which may be present in the associated PWS response message. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.2.2.17 |
4,813 | 4.4.3.3 Integrity protection and verification | The sender shall use its locally stored NAS COUNT as input to the integrity protection algorithm. The receiver shall use the NAS sequence number included in the received message (or estimated from the 5 bits of the NAS sequence number received in the message) and an estimate for the NAS overflow counter as defined in clause 4.4.3.1 to form the NAS COUNT input to the integrity verification algorithm. The algorithm to calculate the integrity protection information is specified in 3GPP TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [19], and the integrity protection shall include octets 6 to n of the security protected NAS message, i.e. the sequence number IE and the NAS message IE. The integrity protection of the SERVICE REQUEST message is defined in clause 9.9.3.28. In addition to the data that is to be integrity protected, the constant BEARER ID, DIRECTION bit, NAS COUNT and NAS integrity key are input to the integrity protection algorithm. These parameters are described in 3GPP TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [19]. After successful integrity protection validation, the receiver shall update its corresponding locally stored NAS COUNT with the value of the estimated NAS COUNT for this NAS message. Integrity verification is not applicable when EIA0 is used. | 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 | 4.4.3.3 |
4,814 | 6.6.3B Spurious emission for UL-MIMO | For UE supporting UL-MIMO, the requirements for Spurious emissions which are caused by unwanted transmitter effects such as harmonics emission, parasitic emissions, intermodulation products and frequency conversion products are specified at each transmit antenna connector. For UEs with two transmit antenna connectors in closed-loop spatial multiplexing scheme, the requirements in subclause 6.6.3 apply to each transmit antenna connector. The requirements shall be met with the UL-MIMO configurations specified in Table 6.2.2B-1. If UE is configured for transmission on single-antenna port, the general requirements in subclause 6.6.3 apply. | 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.3B |
4,815 | 16.9.6 SL DRX 16.9.6.1 General | Sidelink supports SL DRX for unicast, groupcast, and broadcast. Similar parameters as defined in clause 11 for Uu (on-duration, inactivity-timer, retransmission-timer, cycle) are defined for SL to determine the SL active time for SL DRX. During the SL active time, the UE performs SCI monitoring for data reception (i.e., PSCCH and 2nd stage SCI on PSSCH). The UE may skip monitoring of SCI for data reception during SL DRX inactive time. The actual parameters supported for each cast type (unicast, groupcast, broadcast) are specified in the following clauses. The SL active time of the RX UE includes the time in which any of its applicable SL on-duration timer(s), SL inactivity-timer(s) or SL HARQ retransmission timer(s) (for any of unicast, groupcast, or broadcast) are running. In addition, the slots associated with announced periodic transmissions by the TX UE and the time in which a UE is expecting CSI report following a CSI request (for unicast) are considered as SL active time of the RX UE. The time for the unicast link establishment procedure and the time for the PC5 RRC reconfiguration with initial SL DRX configuration procedure as specified in clause 5.28.2 of TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [6] are considered as SL active time of the RX UE. The TX UE maintains a set of timers corresponding to the SL DRX timers in the RX UE(s) for each pair of source/destination L2 ID for unicast or destination L2 ID for groupcast/broadcast. When data is available for transmission to one or more RX UE(s) configured with SL DRX, the TX UE selects resources taking into account the active time of the RX UE(s). The UE can determine from SIB12 whether the gNB supports SL DRX or not. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.9.6 |
4,816 | 5.3.5.13 Conditional Reconfiguration 5.3.5.13.1 General | The network configures the UE with one or more candidate target SpCells in the conditional reconfiguration. The UE evaluates the condition of each configured candidate target SpCell. The UE applies the conditional reconfiguration associated with one of the target SpCells which fulfils associated execution condition. The network can also configure the UE with one or more candidate target PCells associated with one or more candidate target PSCells. The UE evaluates the conditions for the candidate target PCells and the associated candidate target PSCells in parallel and applies a target configuration that include PCell and PSCell for which the associated execution conditions are fullfiled. If there are multiple candidate PSCells associated with one candidate target PCell, the network provides multiple conditional configurations for the same candidate target PCell, i.e., each configuration contains one MCG configuration (for the same candidate target PCell) and one SCG configuration (for one of the multiple associated candidate PSCells). For this case, the network may also provide a complementary CHO only configuration, i.e., there is execution condition only for candidate PCell. The network provides the configuration parameters for the target SpCell(s) in the condRRCReconfig. In NR-DC, the UE may receive two independent conditionalReconfiguration: - a conditionalReconfiguration associated with MCG, that is included in the RRCReconfiguration message received via SRB1; and - a conditionalReconfiguration, associated with SCG, that is included in the RRCReconfiguration message received via SRB3, or, alternatively, included within a RRCReconfiguration message embedded in a RRCReconfiguration message received via SRB1. In this case: - the UE maintains two independent VarConditionalReconfig, one associated with each conditionalReconfiguration; - the UE independently performs all the procedures in clause 5.3.5.13 for each conditionalReconfiguration and the associated VarConditionalReconfig, unless explicitly stated otherwise; - the UE performs the procedures in clause 5.5 for the VarConditionalReconfig associated with the same cell group like the measConfig. In EN-DC, the VarConditionalReconfig is associated with the SCG. In NE-DC and when no SCG is configured, the VarConditionalReconfig is associated with the MCG. The UE performs the following actions based on a received ConditionalReconfiguration IE: 1> if the ConditionalReconfiguration contains the condReconfigToRemoveList: 2> perform conditional reconfiguration removal procedure as specified in 5.3.5.13.2; 1> if the ConditionalReconfiguration contains the condReconfigToAddModList: 2> perform conditional reconfiguration addition/modification as specified in 5.3.5.13.3; 1> if the ConditionalReconfiguration contains the scpac-ReferenceConfiguration: 2> perform subsequent CPAC reference configuration addition/removal as specified in 5.3.5.13.6; 1> if the ConditionalReconfiguration contains the sk-CounterConfiguration: 2> perform sk-CounterList addition/modification/removal as specified in 5.3.5.13.7; 1> if the ConditionalReconfiguration contains the servingSecurityCellSetId: 2> if the current VarServingSecurityCellSetID includes servingSecurityCellSetId: 3> replace the servingSecurityCellSetId value within VarServingSecurityCellSetID with the received servingSecurityCellSetID; 2> else: 3> store the received servingSecurityCellSetId within VarServingSecurityCellSetID. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.5.13 |
4,817 | 5.29.4 User Plane handling | User Plane management as defined for 5GS in clause 5.8 is applicable to 5G LAN-type services with the following clarifications: - There are three types of traffic forwarding methods allowed for 5G VN communication: - N6-based, where the UL/DL traffic for the 5G VN communication is forwarded to/from the DN; NOTE 1: Optionally a L2TP tunnel can be established over N6 as described in clause 5.8.2.16. - N19-based, where the UL/DL traffic for the 5G VN group communication is forwarded between PSA UPFs of different PDU sessions via N19. N19 is based on a shared User Plane tunnel connecting PSA UPFs of a single 5G VN group. - Local switch, where traffic is locally forwarded by a single UPF if this UPF is the common PSA UPF of different PDU Sessions for the same 5G VN group. - For UPFs served by a single SMF Set, the SMF instance(s) in the SMF set handles the user plane paths of the 5G VN group, including: - The SMF instance(s) may prefer to select a single PSA UPF for as many PDU sessions (targeting the same 5G VN group) as possible, in order to implement local switch on the UPF. - (if needed) Establishing N19 tunnels between PSA UPFs served by the same SMF set to support N19-based traffic forwarding. - If multiple SMF (Set)s are serving a 5G VN, user plane forwarding between UPFs served by different SMF (Set)s can be achieved via the DN (i.e. N6) or via user plane tunnels on N6/N19 as described in clause 5.29.3. NOTE 2: The above user plane tunnels may be using GTP-U or IETF VPN. For example, for IP-type traffic, the traffic routing can be based on routing protocols or pre-configured IP address ranges/prefixes corresponding different SMF sets; for ethernet-type traffic, the traffic routing can be based on the learned MAC address over the user plane tunnels between UPFs controlled by different SMF sets, etc. How to implement such user plane tunnels configured between these UPFs is up to network implementation and deployment. - For Ethernet PDU Session, the SMF may instruct the UPF(s) to classify frames based on VLAN tags, and to add and remove VLAN tags, on frames received and sent on N6 or N19 or internal interface ("5G VN internal"), as described in clause 5.6.10.2. NOTE 3: For handling VLAN tags for traffic on N6, TSP ID could also be used as described in clause 6.2.2.6 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]. Further description on User Plane management for 5G VN groups is available in clause 5.8.2.13. When N6-based traffic forwarding is expected, after creation of a 5G VN group the AF can influence the traffic routing for all the members of the 5G VN group, by providing information identifying the traffic, DNAI(s) suitable for selection and an optional indication of traffic correlation together with a 5G VN External Group ID identifying the 5G VN group in an AF request sent to the PCF, as described in clause 5.6.7. If the optional indication of traffic correlation is provided, it means the PDU sessions of the 5G VN group member UEs should be correlated by a common DNAI in the user plane for the traffic. The PCF transforms the AF request into policies that apply to PDU Sessions of the 5G VN group and sends the policies to the SMF. According to the policies, the SMF (re)selects DNAI(s) for the PDU Sessions and configures their UP paths to route the traffic to the selected DNAI(s). If the policies include the traffic correlation indication, the SMF (re)selects a common DNAI for the PDU Sessions so that the traffic of the 5G VN group is routed to the common DNAI. NOTE 4: When receiving a new PDU session establishment request for a 5G VN group, to avoid unnecessary N19 tunnels between UPFs, SMF can check previously selected UPFs for the same 5G VN group, and decide whether a previously selected UPF could serve the requested PDU session. NOTE 5: N19 tunnel(s) can be established between a new UPF and other UPF(s) that belongs to a 5G VN group when the new UPF is selected for the 5G VN group during PDU session establishment. The N19 tunnel(s) to a UPF can be released during or after PDU session release when there is no more PDU sessions for a 5G VN group in that UPF. Establishment or release of the N19 tunnels at the UPF is performed within a group-level N4 Session. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.29.4 |
4,818 | 4.15.6.3 Expected UE Behaviour parameters | These Expected UE Behaviour parameters characterise the foreseen behaviour of a UE or a group of UEs. Sets of these parameters may be provided via the NEF to be stored as part of the subscriber data. Each parameter within the Expected UE Behaviour shall have an associated validity time. The validity time indicates when the Expected UE Behaviour parameter expires and shall be deleted by the related NFs. The validity time may be set to indicate that the particular Expected UE Behaviour parameter has no expiration time. When the validity time expires, the related NFs delete their local copy of the associated Expected UE Behaviour parameter(s). In addition, each parameter within the Expected UE Behaviour may have a confidence and/or accuracy level associated with it. The confidence level indicates a probability assertion for the associated Expected UE Behaviour parameter and the accuracy level indicates the performance of the estimator (e.g. AI/ML model) used for the prediction. The provision procedure of the Expected UE Behaviour is realized by external parameter provision procedure defined in clause 4.15.6.2. The Expected UE Behaviour parameters stored as AMF-Associated Expected UE Behaviour parameters which is per UE level and SMF-Associated Expected UE Behaviour parameters which is per PDU session level in UDM. AMF retrieves the AMF-Associated Expected UE Behaviour parameters from UDM which may related to both PDU session(s) and SMS transmission. SMF retrieves the SMF-Associated Expected UE Behaviour parameters from UDM for the specific PDU session. AMF and SMF uses the Expected UE Behaviour parameters as described in clause 5.4.6.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. Table 4.15.6.3-1: Description of Expected UE Behaviour parameters The Expected UE Moving Trajectory and the Expected Time and Day of Week in Trajectory may be used by the AMF. All other parameters may be used by the AMF and by the SMF. The Scheduled Communication Type and the Traffic Profile should not be used by the AMF to release the UE when NAS Release Assistance Information from the UE is available. In the case of NB-IoT UEs, the parameters may be forwarded to the RAN to allow optimisation of Uu resource allocation for NB-IoT UE differentiation. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.15.6.3 |
4,819 | 4.1.1.1.1a Integrity protection for emergency call (Iu mode only) | The network should initiate the security mode procedure for an emergency call, in the same way as it would for any other call except in the cases defined in sub-clause "Security Procedures Not Applied" in 3GPP TS 33.102[ 3G security; Security architecture ] [5a]. For the establishment of a MM connection for an emergency call when no other MM connection is established (e.g. for an emergency call initiated without a SIM/USIM no other MM connections can exist) the decision on whether or not to apply the security procedures shall be made by the network as defined in the subclause "Emergency Call Handling" in 3GPP TS 33.102[ 3G security; Security architecture ] [5a]. If the MM connection was established locally due to the SRVCC handover of a PDN connection for emergency bearer services for which the "null integrity protection algorithm" EIA0 has been used while in S1 mode or for which integrity protection has not been activated while in Iu mode, the network need not apply the security procedures for this call. If the MM connection was established locally due to the 5G-SRVCC handover from NG-RAN to UTRAN of an emergency PDU session for which the "null integrity protection algorithm" 5G-IA0 has been used while in N1 mode, the network need not apply the security procedures for this call. For an attach for emergency bearer services, (e.g. initiated without a SIM/USIM) the decision on whether or not to apply the security procedures shall be made by the network as defined in the subclause "Emergency Call Handling" in 3GPP TS 33.102[ 3G security; Security architecture ] [5a]. After intersystem change from S1 mode to Iu mode with a PDN connection for emergency bearer services for which the "null integrity protection algorithm" EIA0 has been used while in S1 mode, the network need not apply the security procedures for this connection. For an initial registration for emergency services, (e.g. initiated without a SIM/USIM) the decision on whether or not to apply the security procedures shall be made by the network as defined in the clause J.2 of 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [170]. After 5G-SRVCC handover from NG-RAN to UTRAN with an emergency PDU session for which the "null integrity protection algorithm" 5G-IA0 has been used while in N1 mode, the network need not apply the security procedures for this connection. | 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.1.1.1a |
4,820 | 4.3.1.6.3 Successful executions of outgoing handover to the cells outside the RN per handover cause | This measurement provides the number of successful executions of outgoing handovers to the cells outside the RN per handover cause. CC. Receipt at the RN of UE CONTEXT RELEASE [10] over the X2 from the DeNB following a successful handover. Each X2AP UE CONTEXT RELEASE message received is added to the relevant per handover cause measurement, the possible causes are included in TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [9]. The sum of all supported per cause measurements shall equal the total number of executions of outgoing handovers to the cells outside the RN. In case only a subset of per cause 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 causes supported plus a possible sum value identified by the .sum suffix. HO.InterRNOutSucc.Cause where Cause identifies the cause for handover. 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.3.1.6.3 |
4,821 | 6.9 Connectivity models 6.9.2.1 General | The 5G system shall support the relaying of traffic between a remote UE and a gNB using one or more relay UEs. The 5G system shall support same traffic flow of a remote UE to be relayed via different indirect network connection paths. The 5G system shall support different traffic flows of a remote UE to be relayed via different indirect network connection paths. The connection between a remote UE and a relay UE shall be able to use 3GPP RAT or non-3GPP RAT and use licensed or unlicensed band. The connection between a remote UE and a relay UE shall be able to use fixed broadband technology. The 5G system shall support indirect network connection mode in a VPLMN when a remote UE and a relay UE subscribe to different PLMNs and both PLMNs have a roaming agreement with the VPLMN. The 5G system shall be able to support a UE using simultaneous indirect and direct network connection mode. The network operator shall be able to define the maximum number of hops supported in their networks when using relay UEs. The 5G system shall be able to manage communication between a remote UE and the 5G network across multi-path indirect network connections. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.9 |
4,822 | 5.4.3.4 NAS security mode control completion by the network | The MME shall, upon receipt of the SECURITY MODE COMPLETE message, stop timer T3460. From this time onward the MME shall integrity protect and encipher all signalling messages with the selected NAS integrity and ciphering algorithms. If the SECURITY MODE COMPLETE message contains a Replayed NAS container message IE with an ATTACH REQUEST or TRACKING AREA UPDATE REQUEST message, the MME shall complete the ongoing attach or tracking area updating procedure by considering the ATTACH REQUEST or TRACKING AREA UPDATE REQUEST message contained in the Replayed NAS message container IE as the message that triggered the 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.4.3.4 |
4,823 | 5.3.7b Specific requirements for UE when receiving non-integrity protected reject messages | This clause specifies the requirements for a UE that is not configured to use timer T3245 (see 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [15A] or 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [17]) and receives an ATTACH REJECT, TRACKING AREA UPDATE REJECT or SERVICE REJECT message without integrity protection with specific EMM causes. NOTE 1: Additional UE requirements for this case, requirements for other EMM causes, and requirements for the case when the UE receives an integrity protected reject message are specified in clauses 5.5.1, 5.5.3 and 5.6.1. The UE may maintain a list of PLMN-specific attempt counters and a list of PLMN-specific PS-attempt counters (see 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13]). The maximum number of possible entries in each list is implementation dependent. Additionally, the UE may maintain one counter for "SIM/USIM considered invalid for non-GPRS services" events and one counter for "SIM/USIM considered invalid for GPRS services" events (see 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13]). If the UE maintains the above lists of attempt counters and the event counters, a UE supporting N1 mode, shall store them in its non-volatile memory. The UE shall erase the lists and reset the event counters to zero when the UICC containing the USIM is removed. The counter values shall not be affected by the activation or deactivation of power saving mode or MICO mode (see 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54]). If the UE receives an ATTACH REJECT, TRACKING AREA UPDATE REJECT or SERVICE REJECT message without integrity protection with EMM cause value #3, #6, #7, #8, #11, #12, #13, #14, #15, #31 or #35 before the network has established secure exchange of NAS messages for the NAS signalling connection, the UE shall start timer T3247 (see 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13]) with a random value uniformly drawn from the range between 30 minutes and 60 minutes, if the timer is not running, and take the following actions: 1) if the EMM cause value received is #3, #6, #7 or #8, and a) if the UE maintains a counter for "SIM/USIM considered invalid for GPRS services" events and the counter has a value less than a UE implementation-specific maximum value, the UE shall: i) set the EPS update status to EU3 ROAMING NOT ALLOWED (and shall store it according to clause 5.1.3.3) and shall delete any GUTI, last visited registered TAI, TAI list and eKSI; - if the EMM cause value received is #3, #6 or #8, delete the list of equivalent PLMNs if any; - increment the counter for "SIM/USIM considered invalid for GPRS services" events; - if the EMM cause value received is #3, #6 or #8, and if the UE maintains a counter for "SIM/USIM considered invalid for non-GPRS services" and the counter has a value less than a UE implementation-specific maximum value, increment the counter; - if an attach, tracking area updating or a service request procedure was performed, reset the attach attempt counter, the tracking area updating attempt counter or the service request attempt counter, respectively; - if A/Gb mode or Iu mode is supported by the UE, handle the GMM parameters GPRS attach attempt counter, routing area updating attempt counter or service request attempt counter, GMM state, GPRS update status, P-TMSI, P-TMSI signature, RAI, GPRS ciphering key sequence number as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] for the case when the GPRS attach, routing area updating or service request procedure is rejected with the GMM cause of the same value in a NAS message without integrity protection; - if the UE is operating in single-registration mode and the EMM cause value received is #3, #6 or #7, handle the 5GMM parameters 5GMM state, 5GS update status, registration attempt counter or service request attempt counter, 5G-GUTI, last visited registered TAI, TAI list and ngKSI as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] for the case when the registration request or service request procedure performed over 3GPP access is rejected with the 5GMM cause with the same value in a NAS message without integrity protection; - if the UE is operating in single-registration mode and the EMM cause value received is #8, set the 5GMM state to 5GMM-DEREGISTERED, the 5GS update status to 5U3 ROAMING NOT ALLOWED, shall reset the registration attempt counter and shall delete any 5G-GUTI, last visited registered TAI, TAI list and ngKSI for 3GPP access; - store the current TAI in the list of "forbidden tracking areas for roaming", memorize the current TAI was stored in the list of "forbidden tracking areas for roaming" for non-integrity protected NAS reject message and enter the state EMM-DEREGISTERED.LIMITED-SERVICE; and - search for a suitable cell in another tracking area or in another location area according to 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [21]; or ii) proceed as specified in clauses 5.5.1, 5.5.3 and 5.6.1; - increment the counter for "SIM/USIM considered invalid for GPRS services" events; and - if the EMM cause value received is #3, #6 or #8, and if the UE maintains a counter for "SIM/USIM considered invalid for non-GPRS services" and the counter has a value less than a UE implementation specific maximum value, increment the counter; and b) else the UE shall proceed as specified in clauses 5.5.1, 5.5.3 and 5.6.1; 2) if the EMM cause value received is #12, #13 or #15, the UE shall additionally proceed as specified in clauses 5.5.1, 5.5.3 and 5.6.1; 3) if the EMM cause value received is #11, #14 or #35 and the UE is in its HPLMN or EHPLMN (if the EHPLMN list is present), - the UE shall set the EPS update status to EU3 ROAMING NOT ALLOWED (and shall store it according to clause 5.1.3.3) and shall delete any GUTI, last visited registered TAI, TAI list and eKSI. The UE shall delete the list of equivalent PLMNs. Additionally, if an attach, tracking area updating or service request procedure was performed, the UE shall reset the attach attempt counter or the tracking area updating attempt counter or the service request attempt counter, respectively; - for the EMM cause #11 and #14, if A/Gb mode or Iu mode is supported by the UE, the UE shall in addition handle the GMM parameters GMM state, GPRS update status, P-TMSI, P-TMSI signature, RAI, GPRS ciphering key sequence number and GPRS attach attempt counter or routing area updating attempt counter or service request attempt counter as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] for the case when the procedure is rejected with the GMM cause with the same value in a NAS message without integrity protection; - for the EMM cause #35, if A/Gb mode or Iu mode is supported by the UE, the UE shall in addition handle the GMM parameters GMM state, GPRS update status, P-TMSI, P-TMSI signature, RAI, GPRS ciphering key sequence number and GPRS attach attempt counter or routing area updating attempt counter or service request attempt counter as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] for the case when the procedure is rejected with the GMM cause value #11 in a NAS message without integrity protection; - if the UE is operating in single-registration mode and the EMM cause value received is #11, the UE shall in addition handle the 5GMM parameters 5GMM state, 5GS update status, registration attempt counter or service request attempt counter, 5G-GUTI, last visited registered TAI, TAI list and ngKSI as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] for the case when the registration request procedure or service request procedure performed over 3GPP access is rejected with the 5GMM cause with the same value in a NAS message without integrity protection; - if the UE is operating in single-registration mode and the EMM cause value received is #14 or #35, the UE shall in addition set the 5GMM state to 5GMM-DEREGISTERED, the 5GS update status to 5U3 ROAMING NOT ALLOWED, shall reset the registration attempt counter or service request attempt counter, and shall delete any 5G-GUTI, last visited registered TAI, TAI list and ngKSI for 3GPP access; - the UE shall store the current TAI in the list of "forbidden tracking areas for roaming", memorize the current TAI was stored in the list of "forbidden tracking areas for roaming" for non-integrity protected NAS reject message and enter the state EMM-DEREGISTERED.LIMITED-SERVICE; and - the UE shall search for a suitable cell in another tracking area or in another location area in the same PLMN according to 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [21]; 4) if the EMM cause value received is #11 or #35 and the UE is not in its HPLMN or EHPLMN (if the EHPLMN list is present), in addition to the UE requirements specified in clause 5.5.1, 5.5.3 and 5.6.1, if the UE maintains a list of PLMN-specific attempt counters and the PLMN-specific attempt counter for the PLMN sending the reject message has a value less than a UE implementation-specific maximum value, the UE shall increment the PLMN-specific attempt counter for the PLMN; 5) if the EMM cause value received is #14 and the UE is not roaming in its HPLMN or EHPLMN (if the EHPLMN list is present), in addition to the UE requirements specified in clause5.5.1, 5.5.3 and 5.6.1, if the UE maintains a list of PLMN-specific PS-attempt counter and the PLMN-specific PS-attempt counter of the PLMN sending the reject message has a value less than a UE implementation-specific maximum value, the UE shall increment the PS-attempt counter of the PLMN; and 6) if the EMM cause value received is #31 for a UE that has indicated support for CIoT optimizations, the UE may discard the message or alternatively the UE should: - set the EPS update status to EU3 ROAMING NOT ALLOWED (and shall store it according to clause 5.1.3.3); - store the current TAI in the list of "forbidden tracking areas for roaming", memorize the current TAI was stored in the list of "forbidden tracking areas for roaming" for non-integrity protected NAS reject message; and - search for a suitable cell in another tracking area according to 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [21]. Upon expiry of timer T3247, the UE shall - remove all tracking areas from the list of "forbidden tracking areas for regional provision of service" and the list of "forbidden tracking areas for roaming", which were stored in these lists for non-integrity protected NAS reject message; - set the USIM to valid for EPS services, if - the UE does not maintain a counter for "SIM/USIM considered invalid for GPRS services" events; or - the UE maintains a counter for "SIM/USIM considered invalid for GPRS services" events and this counter has a value less than a UE implementation-specific maximum value; - set the USIM to valid for non-EPS services, if - the UE does not maintain a counter for "SIM/USIM considered invalid for non-GPRS services" events; or - the UE maintains a counter for "SIM/USIM considered invalid for non-GPRS services" events and this counter has a value less than a UE implementation-specific maximum value; - if the UE maintains a list of PLMN-specific attempt counters, for each PLMN-specific attempt counter that has a value greater than zero and less than a UE implementation-specific maximum value, remove the respective PLMN from the extension of the "forbidden PLMNs" list; - if the UE maintains a list of PLMN-specific PS-attempt counters, for each PLMN-specific PS-attempt counter that has a value greater than zero and less than a UE implementation-specific maximum value, remove the respective PLMN from the "forbidden PLMNs for GPRS service" list. If the resulting "forbidden PLMNs for GPRS service" list is empty, the UE shall re-enable the E-UTRA capability (see clause 4.5); - if the UE is supporting A/Gb mode or Iu mode, perform the actions as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] for the case when timer T3247 expires; - if the UE is supporting N1 mode, perform the actions as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54], clause 5.3.20.2 for the case when timer T3247 expires; and - initiate an EPS attach procedure or tracking area updating procedure, if still needed, dependent on EMM state and EPS update status, or perform PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6]. If the UE maintains a list of PLMN-specific attempt counters and PLMN-specific PS-attempt counters, when the UE is switched off, the UE shall, for each PLMN-specific attempt counter that has a value greater than zero and less than the UE implementation-specific maximum value, remove the respective PLMN from the forbidden PLMN list. When the USIM is removed, the UE should perform this action. NOTE 2: If the respective PLMN was stored in the extension of the "forbidden PLMNs" list, then according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6] the UE will delete the contents of this extension when the UE is switched off or the USIM is removed. | 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.7b |
4,824 | 5.5.2.12 Effective measurement window configuration | The UE shall: 1> if effectiveMeasWindowConfig is set to setup: 2> if an effective measurement window configuration is already setup: 3> release the effective measurement window configuration; 2> setup an effective measurement window configuration indicated by the effectiveMeasWindowConfig in accordance with the received windowOffsetPeriodicity (providing periodicity and offset for the following condition), i.e., the first subframe of each window occurs at an SFN and subframe meeting the following condition: SFN mod T = FLOOR(offset/10); subframe = offset mod 10; with T = periodicity/10; 1> else if effectiveMeasWindowConfig is set to release: 2> release the effective measurement window configuration; NOTE: The SFN and subframe of the PCell is used in the effective measurement window calculation. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.5.2.12 |
4,825 | 4.13.1.1 Number of octets of outgoing LWA PDUs transmitted over Xw interface | a) This measurement provides the number of octets of outgoing LWA PDUs transmitted by the eNB over Xw interface to WT. b) CC. c) On receipt of DL DATA DELIVERY STATUS frame by the eNB from WT indicating the downlink LWA PDUs have been successfully transmitted over the Xw interface (see TS 36.465[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN) and Wireless Local Area Network (WLAN); Xw interface user plane protocol ] [24]), the measurement is incremented by 1 for each octet of the successfully transmitted downlink LWA PDUs. d) An integer value (unit MBps). e) LWI.LwaPduXwDlOctet f) EP_Xw (Contained by ENBFunction) g) Valid for packet switched traffic. h) 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.13.1.1 |
4,826 | 5.5.1.3.6A Mobility and periodic registration update for an emergency services fallback not accepted by the network | If the mobility and periodic registration update request triggered upon receiving a request from the upper layers to perform an emergency services fallback: - fails due to an abnormal case described in subclause 5.5.1.3.7, the UE shall perform the procedures as described in subclause 5.5.1.3.7; - cannot be accepted by the network as described in subclause 5.5.1.3.5, the UE shall perform the procedures as described in subclause 5.5.1.3.5; or - fails due to receiving the AUTHENTICATION REJECT message, the UE shall perform the procedures as described in subclauses 5.4.1.2.2.11, 5.4.1.2.3.1, 5.4.1.2.3A.1 or 5.4.1.3.5. If the mobility and periodic registration update request triggered upon receiving a request from the upper layers to perform an emergency services fallback fails due to abnormal case b) in subclause 5.5.1.3.7, the UE shall inform the upper layers of the failure to access the network. NOTE 1: This can result in the upper layers requesting implementation specific mechanisms, e.g. 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 ] [14] can result in the emergency call being attempted to another IP-CAN. If the mobility and periodic registration update request triggered upon receiving a request from the upper layers to perform an emergency services fallback fails due to abnormal cases c), d), e) or g), cannot be accepted or fails due to receiving the AUTHENTICATION REJECT message and the UE does not attempt to select an E-UTRA cell connected to EPC or 5GCN as described in subclause 5.5.1.3.5 and the UE is camped on NR or E-UTRA cell connected to 5GCN in the same PLMN where the last mobility and periodic registration update request was attempted, the UE shall inform the upper layers of the failure of the procedure. NOTE 2: This can result in the upper layers requesting implementation specific mechanisms, e.g. 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 ] [14] can result in the emergency call being attempted to another IP-CAN. | 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.3.6A |
4,827 | 29.2 UE radio capability ID | The UE radio capability ID is an identifier used to represent a set of UE radio capabilities, defined in 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [119] and in 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [72], composed as shown in figure 29.2-1. Figure 29.2-1: Structure of UE radio capability ID The UE radio capability ID is composed of the following elements (each element shall consist of hexadecimal digits only): 1) Type Field (TF): identifies the type of UE radio capability ID. The following values are defined: - 0: manufacturer-assigned UE radio capability ID; - 1: network-assigned UE radio capability ID; and - 2 to F: spare values for future use. 2) The Vendor ID is an identifier of UE manufacturer. This is defined by a value of Private Enterprise Number issued by Internet Assigned Numbers Authority (IANA) in its capacity as the private enterprise number administrator, as maintained at https://www.iana.org/assignments/enterprise-numbers/enterprise-numbers. Its length is 8 hexadecimal digits. This field is present only if the Type Field is set to 0; NOTE: The private enterprise number issued by IANA is a decimal number in the range between 0 and 4294967295 that needs to be converted to a fixed length 8 digit hexadecimal number when used within the UE Radio Capability ID. E.g. 32473 is converted to 00007ED9. 3) The Version ID is the current Version ID configured in the UCMF. This field is present only if the Type Field is set to 1. Its length is 2 hexadecimal digits. 4) Radio Configuration Identifier (RCI): identifies the UE radio configuration. Its length is 11 hexadecimal digits. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 29.2 |
4,828 | 4.11.0a.2a.10 UE Policy Container delivery via EPS | This procedure is initiated when the PCF for the UE decides to update URSP and to provide to the UE via EPS. Based on UE Policy Association Modification initiated by the PCF for the UE in 4.11.0a.2a.6 and PCF initiated SM Policy Association Modification in 4.11.0a.2a.3, the updated URSP Rule included UE Policy Container is received by SMF+PGW-C. The SMF+PGW-C transfers the received UE Policy Container via ePCO to the UE by initiating the bearer modification without QoS update procedure as described in 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]. Figure 4.11.0a.2a.10-1: UE Policy Container delivery via EPS procedure 0. PCF for the UE decides to update UE policy. 1. The PCF for the UE creates the UE Policy Container including UE policy information, and sends the UE Policy Container in the Npcf_UEPolicyControl_UpdateNotify Request as described in step 3 of clause 4.11.0a.2a.6. If the PCF for the UE has not subscribed to be notified by the PCF for the PDU Session, the PCF for the UE subscribes to the PCF for the PDU Session to be notified about the UE response to an update of UE policy information by including "Result of UE Policy Container delivery via EPS" PCRT in this message. If the AF requested to PCF for the UE to report on the outcome of the UE Policies delivery as specified in clause 4.15.6.7, "Result of UE Policy Container delivery via EPS" PCRT shall be included in this message. 2. The PCF for the PDU Session sends a response to the PCF for the UE. 3. The PCF for the PDU Session initiates SM Policy Association Modification procedure as described in step 4 of clause 4.11.0a.2a.3. The PCF for the PDU Session transfers the UE Policy Container by Npcf_SMPolicyControl_UpdateNotify Request for the selected PDN connection for the related UE in EPC. If the PCF for the PDU Session received "Result of UE Policy Container delivery via EPS" PCRT in step 1, the PCF for the PDU Session subscribes to the SMF+PGW-C with "Result of UE Policy Container delivery via EPS" PCRT. 4. The SMF+PGW-C sends a response to the PCF for the PDU Session. 5. The SMF+PGW-C initiates the bearer modification without bearer QoS update procedure, as described in clause 5.4.3 of TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [3]. The UE includes the result of UE Policy delivery in response via ePCO. NOTE: The ePCO container for UE Policy delivery response is specified by Stage 3. 6. The SMF+PGW-C transparently forwards the response of the UE to the PCF for the PDU Session by using Npcf_SMPolicyControl_Update Request. The message includes the indication that "Result of UE Policy Container delivery via EPS" PCRT was met. If the SMF+PGW-C received rejection (e.g. due to paging failure) from Update Bearer Request message in step 5, then the SMF+PGW-C sends the delivery failure result with an appropriate reason (e.g. such that UE is temporarily not reachable) and the indication of "Result of UE Policy Container delivery via EPS" PCRT was met to the PCF for the PDU Session. 7. The PCF for the PDU Session transparently forwards the response from the UE, or the delivery failure result provided by SMF+PGW-C to the PCF for the UE by using Npcf_UEPolicyControl_Update Request. The message includes the indication of "Result of UE Policy Container delivery via EPS" PCRT was met. If the AF requested to PCF for the UE to report on the outcome of the UE Policies delivery as specified in clause 4.15.6.7, the PCF for the UE reports the outcome of the UE Policies delivery to the AF with the received result from the PCF for the PDU Session. 8. The PCF for the UE sends a response to the PCF for the PDU Session. 9. The PCF for the PDU Session sends a response to the SMF+PGW-C. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.11.0a.2a.10 |
4,829 | 8.2.5 Control Plane for trusted non-3GPP Access | Figure 8.2.5-1: Control Plane before the NWt connection is established between UE and TNGF Figure 8.2.5-2: Control Plane after the NWt connection is established between UE and TNGF Large NAS messages may be fragmented by the "inner IP" layer or by TCP. Figure 8.2.5-3: Control Plane for establishment of user-plane via TNGF In the above figures 8.2.5-2 and 8.2.5-3, the UDP protocol may be used between the UE and TNGF to enable NAT traversal for IKEv2 and IPsec traffic. The NWt connection is defined in clause 4.2.8.3 and in clause 4.12a.2.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 8.2.5 |
4,830 | β SL-QoS-Profile | The IE SL-QoS-Profile is used to give the QoS parameters for a sidelink QoS flow. Need codes or conditions specified for SL-QoS-Profile do not apply, in case SL-QoS-Profile is included in SidelinkUEInformationNR. SL-QoS-Profile information element -- ASN1START -- TAG-SL-QOS-PROFILE-START SL-QoS-Profile-r16 ::= SEQUENCE { sl-PQI-r16 SL-PQI-r16 OPTIONAL, -- Need R sl-GFBR-r16 INTEGER (0..4000000000) OPTIONAL, -- Need R sl-MFBR-r16 INTEGER (0..4000000000) OPTIONAL, -- Need R sl-Range-r16 INTEGER (1..1000) OPTIONAL, -- Need R ... } SL-PQI-r16 ::= CHOICE { sl-StandardizedPQI-r16 INTEGER (0..255), sl-Non-StandardizedPQI-r16 SEQUENCE { sl-ResourceType-r16 ENUMERATED {gbr, non-GBR, delayCriticalGBR, spare1} OPTIONAL, -- Need R sl-PriorityLevel-r16 INTEGER (1..8) OPTIONAL, -- Need R sl-PacketDelayBudget-r16 INTEGER (0..1023) OPTIONAL, -- Need R sl-PacketErrorRate-r16 INTEGER (0..9) OPTIONAL, -- Need R sl-AveragingWindow-r16 INTEGER (0..4095) OPTIONAL, -- Need R sl-MaxDataBurstVolume-r16 INTEGER (0..4095) OPTIONAL, -- Need R ... } } -- TAG-SL-QOS-PROFILE-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | β |
4,831 | 13.4.2 SRB5 | SRB5 is supported in NR-DC, but not in EN-DC, NGEN-DC and NE-DC. The decision to establish SRB5 is taken by the SN, which provides the SRB5 configuration using an SN RRC message. SRB5 establishment and release can be done at Secondary Node Addition and Secondary Node Change. SRB5 reconfiguration can be done at Secondary Node Modification procedure. SRB5 is used to send RRC messages (i.e., MeasurementReportAppLayer message) including application layer measurement report information directly to the SN. SRB5 is modelled as one of the SRBs defined in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [4] and uses the NR-DCCH logical channel type. When the SCG is released, SRB5 is released. | 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.2 |
4,832 | 4.9.1.4 Inter NG-RAN node N2 based handover, Cancel | Prior to sending a Handover Command to the UE, the source NG-RAN node may attempt cancellation of handover during the handover procedure. The reason for cancellation may include timer expiration, internal failure within the source NG-RAN node or UE returned to source cell etc. The handover cancellation is initiated by sending a Handover Cancel request to the source AMF. This is done in order to release the resources reserved for the handover in the target system. The AMF shall cancel the handover resources as defined in clause 4.11.1.2.3 for case the source RAN is NG-RAN. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.9.1.4 |
4,833 | 10.5.6.5A Re-attempt indicator | The purpose of the Re-attempt indicator information element is to indicate a condition under which the MS is allowed, in the current PLMN for the same APN, to re-attempt an EPS session management procedure (see 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120]) corresponding to the session management procedure which was rejected by the network. The Re-attempt indicator information element is coded as shown in figure 10.5.6.5A and table 10.5.6.5A. Figure 10.5.6.5A: Re-attempt indicator information element Table 10.5.6.5A: Re-attempt 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.5A |
4,834 | 4.3.1.4.5 Attempted outgoing inter-frequency handovers β non gap-assisted measurement | This measurement provides the number of attempted outgoing inter-frequency handovers, when measurement gaps are not used [12]. CC. Transmission of the RRCConnectionReconfiguration message by the eNB/RN to UE triggering the handover, indicating the attempt of an outgoing inter-frequency handover when measurement gaps are not used (see TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8]). A single integer value. HO.InterFreqNoMeasGapOutAtt 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.3.1.4.5 |
4,835 | 15.5.2.5 O&M Requirements | All automatic changes of the HO and/or reselection parameters for mobility robustness optimisation shall be within the ranges allowed by OAM and specified below. The following control parameters shall be provided by OAM to control MRO behaviour: - Maximum deviation of Handover Trigger: this parameter defines the maximum allowed absolute deviation of the Handover Trigger, from the default point of operation defined by the parameter values assigned by OAM. - Minimum time between Handover Trigger changes: this parameter defines the minimum allowed time interval between two Handover Trigger change performed by MRO. This is used to control the stability and convergence of the algorithm. Furthermore, in order to support the solutions for detection of mobility optimisation, the parameter Tstore_UE_cntxt shall be configurable by the OAM system. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 15.5.2.5 |
4,836 | β FeatureSetEUTRA-UplinkId | The IE FeatureSetEUTRA-UplinkId identifies an uplink feature set in E-UTRA list (see TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10]. The first element in that list is referred to by FeatureSetEUTRA-UplinkId = 1. The FeatureSetEUTRA-UplinkId =0 is used when the UE does not support a carrier in this band of a band combination. FeatureSetEUTRA-UplinkId information element -- ASN1START -- TAG-FEATURESETEUTRAUPLINKID-START FeatureSetEUTRA-UplinkId ::= INTEGER (0..maxEUTRA-UL-FeatureSets) -- TAG-FEATURESETEUTRAUPLINKID-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | β |
4,837 | 8.3.2.4.1 Minimum requirement with Same Cell ID (with single NZP CSI-RS resource) | The requirements are specified in Table 8.3.2.4.1-3, with the additional parameters in Table 8.3.2.4.1-1 and Table 8.3.2.4.1-2. The purpose of this test is to verify the UE capability of supporting non quasi-colocated antenna ports when the UE receives DCI format 2D in a scenario where the two transmission point share the same Cell ID. In particular the test verifies that the UE, configured with quasi co-location type B, performs correct tracking and compensation of the timing difference between two transmission points, channel parameters estimation and rate matching according to the βPDSCH RE Mapping and Quasi-Co-Location Indicatorβ (PQI) signalling defined in [6], configured according to Table 8.3.2.4.1-2. In Tables 8.3.2.4.1-1 and 8.3.2.4.1-2, transmission point 1 (TP 1) is the serving cell and transmission point 2 (TP 2) transmits PDSCH. The downlink physical channel setup for TP 1 is according to Table C.3.4-1 and for TP 2 according to Table C.3.4-2. Table 8.3.2.4.1-1: Test Parameters for quasi co-location type B: same Cell ID Table 8.3.2.4.1-2: Configurations of PQI and DL transmission hypothesis for each PQI set Table 8.3.2.4.1-3: Minimum performance for quasi co-location type B: same Cell ID | 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.3.2.4.1 |
4,838 | 4.3.2.7 Handling of keys at intersystem change from Iu mode to A/Gb mode | At inter-system change from Iu mode to A/Gb mode, ciphering may be started (see 3GPP TS 44.018[ None ] [84]) without any new authentication procedure. Deduction of the appropriate security key for ciphering in A/Gb mode, depends on the current GSM/UMTS security context stored in the MS and the network. The ME shall handle the GSM ciphering key and a potential GSM Kc128 according to table 4.3.2.7.1. Table 4.3.2.7.1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Inter-system change from Iu mode to A/Gb mode NOTE: A USIM with UMTS security context, passes the UMTS ciphering key, the UMTS integrity key and the derived GSM ciphering key to the ME independent on the current radio access being UTRAN or GERAN. | 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.3.2.7 |
4,839 | 4.7.5 Mobile IAB 4.7.5.1 General | Mobile IAB introduces the mobile IAB-node, which is a RAN node that provides NR access links to UEs and an NR backhaul link to a parent node, and that can conduct physical mobility across the RAN area. The mobile IAB-node includes a mobile IAB-MT and a mobile IAB-DU. Mobile IAB supports the same functionality as IAB unless explicitly specified. The following enhancements/restrictions only apply to mobile IAB: The mobile IAB-node uses the mobile IAB-node authorization procedure defined in TS 38.401[ NG-RAN; Architecture description ] [4] and the MBSR authorization procedure defined in TS 23.501[ System architecture for the 5G System (5GS) ] [3]. A RAN node operating as a mobile IAB-node shall not concurrently operate as an IAB-node. During network integration, the RAN node shall indicate whether it intends to operate as a mobile IAB-node or as an IAB-node via an indicator in the RRCSetupComplete message. The parent node indicates support for mobile IAB-nodes by broadcasting a mobile-IAB-specific indicator in SIB1. The mobile IAB-node shall not have descendent nodes. A mobile-IAB cell shall therefore not broadcast any indication that it is a suitable parent node for IAB-nodes or mobile IAB-nodes. The cell of a mobile IAB-DU may indicate to UEs via a SIB1 indicator that it is a mobile-IAB cell. The mobile IAB-node uses the mobile IAB-node network integration procedure as defined in TS 38.401[ NG-RAN; Architecture description ] [4]. The mobile IAB-MT can perform the mobile IAB-MT migration procedures via Xn handover and/or via NG handover as defined in TS 38.401[ NG-RAN; Architecture description ] [4]. The mobile IAB-MT can also perform the mobile IAB-node recovery procedure as defined in TS 38.401[ NG-RAN; Architecture description ] [4]. The mobile IAB-node can perform the mobile IAB-DU migration procedure, where a new logical mobile IAB-DU is established on the mobile IAB-node and the initial logical mobile IAB-DU is released some time later. During this procedure, the UEs connected via the mobile IAB-node are handed over from the initial logical mobile IAB-DU, referred to as the source logical mobile IAB-DU, to the new logical mobile IAB-DU, referred to as the target logical mobile IAB-DU. The details of this procedure are defined in TS 38.401[ NG-RAN; Architecture description ] [4]. Enhancements related to BAP for mobile IAB-DU migration are defined in TS 38.340[ NR; Backhaul Adaptation Protocol (BAP) specification ] [31]. When a RAN node is operating as a mobile IAB node, dual connectivity for this node is not supported. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 4.7.5 |
4,840 | 5.8.2.8.4 Support of PFD Management | The NEF (PFDF) shall provide PFD(s) to the SMF on the request of SMF (pull mode) or on the request of PFD management from NEF (push mode), as described in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]. In addition, the NEF (PFDF) may subscribe to NWDAF to be notified or request to get PFD "Determination analytics" for known applications (as specified in TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [86]) and may decide whether to create, update, or delete PFD(s) based on the NWDAF analytics as specified in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]. The SMF shall provide the PFD(s) to the UPF, which have active PDR(s) with the application identifier corresponding to the PFD(s). The SMF supports the procedures in clause 4.4.3.5 of TS 23.502[ Procedures for the 5G System (5GS) ] [3], for management of PFDs. PFD(s) is cached in the SMF, and the SMF maintains a caching timer associated to the PFD(s). When the caching timer expires and there's no active PCC rule that refers to the corresponding application identifier, the SMF informs the UPF to remove the PFD(s) identified by the application identifier using the PFD management message. When a PDR is provided for an application identifier corresponding to the PFD(s) that are not already provided to the UPF, the SMF shall provide the PFD(s) to the UPF (if there are no PFD(s) cached, the SMF retrieves them from the NEF (PFDF) as specified in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]). When any update of the PFD(s) is received from NEF (PFDF) by SMF (using "push" or "pull" mode), and there are still active PDRs in UPF for the application identifier, the SMF shall provision the updated PFD set corresponding to the application identifier to the UPF using the PFD management message. NOTE 1: SMF can assure not to overload N4 signalling while managing PFD(s) to the UPF, e.g. forwarding the PFD(s) to the right UPF where the PFD(s) is enforced. When the UPF receives the updated PFD(s) from either the same or different SMF for the same application identifier, the latest received PFD(s) shall overwrite any existing PFD(s) stored in the UPF. NOTE 2: For the case a single UPF is controlled by multiple SMFs, the conflict of PFD(s) corresponding to the same application identifier provided by different SMF can be avoided by operator enforcing a well-planned NEF (PFDF) and SMF/UPF deployment. When a PFD is removed/modified and this PFD was used to detect application traffic related to an application identifier in a PDR of an N4 session and the UPF has reported the application start to the SMF as defined in clause 4.4.2.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3] for the application instance corresponding to this PFD, the UPF shall report the application stop to the SMF for the corresponding application instance identifier if the removed/modified PFD in UPF results in that the stop of the application instance is not being able to be detected. If the PFDs are managed by local O&M procedures, PFD retrieval is not used; otherwise, the PFDs retrieved from NEF (PFDF) override any PFDs pre-configured in the SMF. When all the PFDs retrieved from the NEF (PFDF) for an application identifier are removed, the pre-configured PFDs are used. The SMF shall provide either the PFDs retrieved from NEF (PFDF) or the pre-configured PFDs for an application identifier to the UPF. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.8.2.8.4 |
4,841 | 16.9.6.3 Groupcast/Broadcast | For groupcast/broadcast, SL DRX is configured commonly among multiple UEs based on QoS profile and Destination L2 ID. Multiple SL DRX configurations can be supported for each of groupcast/broadcast. SL on-duration timer, SL inactivity-timer, SL HARQ RTT and SL HARQ retransmission timers are supported for groupcast. Only SL on-duration timer is supported for broadcast. SL DRX cycle, SL on-duration, and SL inactivity timer (only for groupcast) are configured per QoS profile. The starting offset and slot offset of the SL DRX cycle is determined based on the destination L2 ID. The SL HARQ RTT timer (only for groupcast) and SL HARQ retransmission timer (only for groupcast) are not configured per QoS profile or per destination L2 ID. For groupcast, the RX UE maintains a SL inactivity timer for each destination L2 ID, and selects the largest SL inactivity timer value if multiple SL inactivity timer values associated with different QoS profiles are configured for that L2 ID. For groupcast and broadcast, the RX UE maintains a single SL DRX cycle (selected as the smallest SL DRX cycle of any QoS profile of that L2 ID) and single SL on-duration (selected as the largest SL on-duration of any QoS profile of that L2 ID) for each destination L2 ID when multiple QoS profiles are configured for that L2 ID. For groupcast, SL HARQ RTT timer and SL HARQ retransmission timer are maintained per SL process at the RX UE. SL HARQ RTT timer can be set to different values to support both HARQ enabled and HARQ disabled transmissions. A default SL DRX configuration, common between groupcast and broadcast, can be used for a QoS profile which is not mapped onto any non-default SL DRX configuration(s). The default SL DRX configuration for groupcast and broadcast can also be used for discovery message in sidelink discovery in clause 16.9.5 and relay discovery messages in clause 16.12.3, for ProSe Direct Link Establishment Request message as specified in TS 24.554[ Proximity-services (ProSe) in 5G System (5GS) protocol aspects; Stage 3 ] [55], and for Direct Link Establishment Request message as specified in TS 24.587[ Vehicle-to-Everything (V2X) services in 5G System (5GS); Stage 3 ] [53]. In-coverage TX and RX UEs in RRC_IDLE/RRC_INACTIVE obtain their SL DRX configuration from SIB. UEs (TX or RX) in RRC_CONNECTED can obtain the SL DRX configuration from SIB, or from dedicated RRC signalling during handover. For the out of coverage case, the SL DRX configuration is obtained from pre-configuration. For groupcast, the TX UE restarts its timer corresponding to the SL inactivity timer for the destination L2 ID (used for determining the allowable transmission time) upon reception of new data with the same destination L2 ID. TX profile is introduced to ensure compatibility for groupcast and broadcast communication between UEs supporting/not-supporting SL DRX functionality. A TX profile is provided by upper layers to AS layer and identifies one or more sidelink feature group(s). Multiple TX profiles with the support of SL DRX and without the support of SL DRX can be associated to a destination L2 ID. For a given destination L2 ID, all TX and RX UEs should be configured with the same set of TX profile(s). A UE only assumes SL DRX for the given destination L2 ID when all the associated TX profiles correspond to support of SL DRX. A UE assumes no SL DRX for the given destination L2 ID if there is no associated TX profile. An RX UE determines that SL DRX is used if all destination L2 IDs of interest are assumed to support SL DRX. For groupcast, when the UE is in RRC_CONNECTED and using mode 1 resource allocation, the UE reports each destination L2 ID and associated SL DRX on/off indication to the gNB supporting SL DRX. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.9.6.3 |
4,842 | 6.2.10 AF | The Application Function (AF) interacts with the 3GPP Core Network in order to provide services, for example to support the following: - Application Function influence on traffic routing (see clause 5.6.7); - Application Function influence on Service Function Chaining (see clause 5.6.16.2); - Accessing Network Exposure Function (see clause 5.20); - Interacting with the Policy and charging control framework (see clause 5.14); - Time synchronization service (see clause 5.27.1.8); - IMS interactions with 5GC (see clause 5.16). - Support PDU Set Handling as defined in clause 5.37.5. Based on operator deployment, Application Functions considered to be trusted by the operator can be allowed to interact directly with relevant Network Functions. Application Functions not allowed by the operator to access directly the Network Functions shall use the external exposure framework (see clause 7.3) via the NEF to interact with relevant Network Functions. The functionality and purpose of Application Functions are only defined in this specification with respect to their interaction with the 3GPP Core Network. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 6.2.10 |
4,843 | 16.16 ECN marking for L4S and congestion information exposure | In order to support ECN marking for L4S at gNB as specified in TS 23.501[ System architecture for the 5G System (5GS) ] [3], SMF provides ECN marking request per QoS flow level to the gNB as part of PDU Session Resource Management procedure. If the gNB supports ECN marking, it provides the status indication back to the SMF which is used by the SMF as specified in TS 23.501[ System architecture for the 5G System (5GS) ] [3]. During Xn Handover Preparation procedure, source gNB provides the ECN marking request to target gNB. For ECN marking for L4S at UPF, SMF requests the gNB to report congestion information per QoS flow level as part of PDU Session Resource Management procedure. If the gNB supports ECN marking for L4S at UPF, it provides the status indication back to the SMF which is used by SMF as specified in TS 23.501[ System architecture for the 5G System (5GS) ] [3]. During Xn Handover Preparation procedure, source gNB provides the ECN marking UPF request to target gNB. For congestion reporting from gNB to UPF, SMF requests the gNB to report congestion information per QoS flow level as part of PDU Session Resource Management procedure. If the NG-RAN supports congestion information reporting, it provides the status indication back to the SMF which is used by the SMF as specified in TS 23.501[ System architecture for the 5G System (5GS) ] [3]. During Xn Handover Preparation procedure, source gNB provides the congestion information request to target gNB. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.16 |
4,844 | 8.10.4.2.1 FDD | The parameters specified in Table 8.10.4.2.1-1 are valid for all FDD TM9 localized ePDCCH tests with 4Rx unless otherwise stated. Table 8.10.4.2.1-1: Test Parameters for Localized EPDCCH with TM9 and 4Rx For the parameters specified in Table 8.10.4.2.1-1 the average probability of a missed downlink scheduling grant (Pm-dsg) shall be below the specified value in Table 8.10.4.2.1-2. EPDCCH subframe monitoring is configured and the subframe monitoring requirement in EPDCCH restricted subframes is statDTX of 99.9%. The downlink physical setup is in accordance with Annex C.3.2. Table 8.10.4.2.1-2: Minimum performance Localized EPDCCH with TM9 and 4Rx Antenna ports | 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.10.4.2.1 |
4,845 | 4.9.2.1 Handover of a PDU Session procedure from untrusted non-3GPP to 3GPP access (non-roaming and roaming with local breakout) | Clause 4.9.2.1 specifies how to hand over a UE from a source Untrusted non-3GPP access to a target 3GPP access and how a UE can handover a PDU Session from untrusted non-3GPP access to 3GPP access. It is based on the PDU Session Establishment procedure for 3GPP access as specified in clause 4.3.2. Figure 4.9.2.1-1: Handover of a PDU Session procedure from untrusted non-3GPP access to 3GPP access (non-roaming and roaming with local breakout) 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. 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.1 (PDU Session Establishment for Non-roaming and Roaming with Local Breakout). When sending the PDU Session Establishment Accept, within the N1 SM container and in the N2 SM information, the SMF shall 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) that are applicable to the PDU Session for the target access. 3. If the User Plane of the PDU Session is activated in non-3GPP access, the SMF executes the release of resources 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. If the UE is moving to the NB-IoT RAT type of 3GPP access, the PDU Session Establishment request would be rejected by AMF when the UP resources exceeds the UE's maximum number of supported UP resources as described in clause 5.4.5.2.4 of TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [25]. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.9.2.1 |
4,846 | 6.1.2 Types of 5GSM procedures | Three types of 5GSM procedures can be distinguished: a) Procedures related to PDU sessions: These procedures are initiated by the network and are used for authentication and authorization or manipulation of PDU sessions: 1) PDU authentication and authorization; 2) network-requested PDU session modification; 3) network-requested PDU session release; and 4) service-level authentication and authorization. This procedure is initiated by the UE and to request for establishment of PDU sessions or to perform handover of an existing PDU session between 3GPP access and non-3GPP access, or to transfer an existing PDN connection in the EPS to the 5GS: UE-requested PDU session establishment. b) Transaction related procedures: These procedures are initiated by the UE to request for handling of PDU sessions, i.e. to modify a PDU session, or to release a PDU session: 1) UE-requested PDU session modification; and 2) UE-requested PDU session release. This procedure is initiated by the 5G ProSe UE-to-network relay UE and is used for the manipulation of PDU sessions: - remote UE report. A successful transaction related procedure initiated by the UE triggers the network to execute one of the following procedures related to PDU session; network-requested PDU session modification procedure or network-requested PDU session release procedure. The UE treats the start of the procedure related to the PDU session as completion of the transaction related procedure. c) Common procedure: The following 5GSM procedure can be related to a PDU session or to a procedure transaction: 5GSM status 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.1.2 |
4,847 | 5.3.5.5.6 RLF Timers & Constants configuration | The UE shall: 1> if the received rlf-TimersAndConstants is set to release: 2> if any DAPS bearer is configured: 3> use values for timers T301, T310, T311 and constants N310, N311 for the target cell group, as included in ue-TimersAndConstants received in SIB1; 2> else: 3> use values for timers T301, T310, T311 and constants N310, N311, as included in ue-TimersAndConstants received in SIB1; 1> else: 2> if any DAPS bearer is configured: 3> configure the value of timers and constants for the target cell group in accordance with received rlf-TimersAndConstants; 2> else: 3> (re-)configure the value of timers and constants in accordance with received rlf-TimersAndConstants; 3> stop timer T310 for this cell group, if running; 3> stop timer T312 for this cell group, if running; 3> reset the counters N310 and N311. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.5.5.6 |
4,848 | β SIB9 | SIB9 contains information related to GPS time and Coordinated Universal Time (UTC). The UE may use the parameters provided in this system information block to obtain the UTC, the GPS and the local time. NOTE: The UE may use the time information for numerous purposes, possibly involving upper layers e.g. to assist GPS initialisation, to synchronise the UE clock. SIB9 information element -- ASN1START -- TAG-SIB9-START SIB9 ::= SEQUENCE { timeInfo SEQUENCE { timeInfoUTC INTEGER (0..549755813887), dayLightSavingTime BIT STRING (SIZE (2)) OPTIONAL, -- Need R leapSeconds INTEGER (-127..128) OPTIONAL, -- Need R localTimeOffset INTEGER (-63..64) OPTIONAL -- Need R } OPTIONAL, -- Need R lateNonCriticalExtension OCTET STRING OPTIONAL, ..., [[ referenceTimeInfo-r16 ReferenceTimeInfo-r16 OPTIONAL -- Need R ]], [[ eventID-TSS-r18 INTEGER (0..63) OPTIONAL -- Need R ]] } -- TAG-SIB9-STOP -- ASN1STOP NOTE 1: The UE may use this field together with the leapSeconds field to obtain GPS time as follows: GPS Time (in seconds) = timeInfoUTC (in seconds) - 2,524,953,600 (seconds) + leapSeconds, where 2,524,953,600 is the number of seconds between 00:00:00 on Gregorian calendar date 1 January, 1900 and 00:00:00 on Gregorian calendar date 6 January, 1980 (start of GPS time). | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | β |
4,849 | 16.11 Minimization of Service Interruption | In case of a disaster, a radio access network can experience outage, which can result in that UEs belonging to the network experience service interruptions. For this scenario, another network not affected by the disaster, which during non-disaster situations is considered by the UEs as a forbidden network, can allow roaming of the UEs belonging to the network experiencing such disaster service interruptions. Such roaming is referred to as disaster roaming. This is further described in clause 5.40 of TS 23.501[ System architecture for the 5G System (5GS) ] [3] and 3.10 of TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [47]. To allow such disaster roaming, a cell can broadcast a list of PLMNs with disaster conditions for which disaster roaming is offered. Disaster roaming service is provided only for the area that covers the area with disaster condition. Further, to be able to control the load that disaster roaming UEs put on a cell, the cell can broadcast access control parameters applicable specifically for disaster roaming UEs. Access attempts of disaster roaming UEs are based on Access Identity 3. The network can for example set the access control parameters for Access Identity 3 so that access attempts of disaster roaming UEs are more likely to be barred compared to non-disaster roaming UEs. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.11 |
4,850 | β SL-InterUE-CoordinationConfig | The IE SL-InterUE-CoordinationConfig is used to configure the sidelink inter-UE coordination (between a UE, UE-A, and a peer UE, UE-B) parameters. SL-InterUE-CoordinationConfig information element -- ASN1START -- TAG-SL-INTERUE-COORDINATIONCONFIG-START SL-InterUE-CoordinationConfig-r17 ::= SEQUENCE { sl-InterUE-CoordinationScheme1-r17 SL-InterUE-CoordinationScheme1-r17 OPTIONAL, -- Need M sl-InterUE-CoordinationScheme2-r17 SL-InterUE-CoordinationScheme2-r17 OPTIONAL, -- Need M ... } SL-InterUE-CoordinationScheme1-r17 ::= SEQUENCE { sl-IUC-Explicit-r17 ENUMERATED {enabled, disabled} OPTIONAL, -- Need M sl-IUC-Condition-r17 ENUMERATED {enabled, disabled} OPTIONAL, -- Need M sl-Condition1-A-2-r17 ENUMERATED {disabled} OPTIONAL, -- Need M sl-ThresholdRSRP-Condition1-B-1-Option1List-r17 SEQUENCE (SIZE (1..8)) OF SL-ThresholdRSRP-Condition1-B-1-r17 OPTIONAL, -- Need M sl-ThresholdRSRP-Condition1-B-1-Option2List-r17 SEQUENCE (SIZE (1..8)) OF SL-ThresholdRSRP-Condition1-B-1-r17 OPTIONAL, -- Need M sl-ContainerCoordInfo-r17 ENUMERATED {enabled, disabled} OPTIONAL, -- Need M sl-ContainerRequest-r17 ENUMERATED {enabled, disabled} OPTIONAL, -- Need M sl-TriggerConditionCoordInfo-r17 INTEGER (0..1) OPTIONAL, -- Need M sl-TriggerConditionRequest-r17 INTEGER (0..1) OPTIONAL, -- Need M sl-PriorityCoordInfoExplicit-r17 INTEGER (1..8) OPTIONAL, -- Need M sl-PriorityCoordInfoCondition-r17 INTEGER (1..8) OPTIONAL, -- Need M sl-PriorityRequest-r17 INTEGER (1..8) OPTIONAL, -- Need M sl-PriorityPreferredResourceSet-r17 INTEGER (1..8) OPTIONAL, -- Need M sl-MaxSlotOffsetTRIV-r17 INTEGER (1..8000) OPTIONAL, -- Need M sl-NumSubCH-PreferredResourceSet-r17 INTEGER (1..27) OPTIONAL, -- Need M sl-ReservedPeriodPreferredResourceSet-r17 INTEGER (1..16) OPTIONAL, -- Need M sl-DetermineResourceType-r17 ENUMERATED {uea, ueb} OPTIONAL, -- Need M ... } SL-InterUE-CoordinationScheme2-r17 ::= SEQUENCE { sl-IUC-Scheme2-r17 ENUMERATED {enabled} OPTIONAL, -- Need R sl-RB-SetPSFCH-r17 BIT STRING (SIZE (10..275)) OPTIONAL, -- Need M sl-TypeUE-A-r17 ENUMERATED {enabled} OPTIONAL, -- Need R sl-PSFCH-Occasion-r17 INTEGER (0..1) OPTIONAL, -- Need M sl-SlotLevelResourceExclusion-r17 ENUMERATED {enabled} OPTIONAL, -- Need R sl-OptionForCondition2-A-1-r17 INTEGER (0..1) OPTIONAL, -- Need M sl-IndicationUE-B-r17 ENUMERATED {enabled, disabled} OPTIONAL, -- Need M ..., [[ sl-DeltaRSRP-Thresh-v1720 INTEGER (-30..30) OPTIONAL -- Need M ]] } SL-ThresholdRSRP-Condition1-B-1-r17 ::= SEQUENCE { sl-Priority-r17 INTEGER (1..8), sl-ThresholdRSRP-Condition1-B-1-r17 INTEGER (0..66) } -- TAG-SL-INTERUE-COORDINATIONCONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | β |
4,851 | β RLF-TimersAndConstants | The IE RLF-TimersAndConstants is used to configure UE specific timers and constants. RLF-TimersAndConstants information element -- ASN1START -- TAG-RLF-TIMERSANDCONSTANTS-START RLF-TimersAndConstants ::= SEQUENCE { t310 ENUMERATED {ms0, ms50, ms100, ms200, ms500, ms1000, ms2000, ms4000, ms6000}, n310 ENUMERATED {n1, n2, n3, n4, n6, n8, n10, n20}, n311 ENUMERATED {n1, n2, n3, n4, n5, n6, n8, n10}, ..., [[ t311 ENUMERATED {ms1000, ms3000, ms5000, ms10000, ms15000, ms20000, ms30000} ]] } -- TAG-RLF-TIMERSANDCONSTANTS-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | β |
4,852 | 13.2.2 Other configuration by the Intranet or ISP (IPv6 only) | When using IPv6, in some situations the MS may need additional configuration information from the Intranet or ISP besides the IP address. It may for example be IMS related configuration options (see 3GPP TS 24.229[ IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 ] [47]). If the MS is DHCP capable and the IPv6 address has been allocated using Stateless Address Autoconfiguration, the MS may use a procedure as in the example below to configure additional external network protocol parameters, or other parameters that apply to the Intranet or ISP. The GGSN shall in this case indicate to the MS that there is additional configuration information to retrieve by setting the O-flag in the Router Advertisements. This shall be configured per APN in the GGSN. The following description bullet items describe an example of a signal flow, where the MS directs an Information-Request to the All_DHCP_Relay_Agents_and_Servers multicast address. The MS may also direct the message to a specific server instead of all servers. For a detailed description of the DHCPv6 messages refer to the DHCPv6 IETF RFC 3315 [46]. The sequence is depicted in figure 16f. 1) A Router Advertisement with the O-flag set, is sent from GGSN to TE to indicate to it to retrieve other configuration information. 2) The TE sends an INFORMATION-REQUEST message with the IP destination address set to the All_DHCP_Relay_Agents_and_Servers multicast address defined in the DHCPv6 IETF RFC 3315 [46]. The source address shall be the link-local address of the MS. The DHCP relay agent in the GGSN shall forward the message. 3) DHCP servers receiving the forwarded INFORMATION-REQUEST message, reply by sending a RELAY-REPLY message, with the "Relay Message" option including a REPLY message with the requested configuration parameters. The TE chooses one of the possibly several REPLY messages and extracts the configuration information. EXAMPLE: In the following example a request for information with use of DHCPv6 from end to end is shown. Figure 16f: DHCPv6 Other configuration 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.2 |
4,853 | 9.11.3.80 PEIPS assistance information | The purpose of the PEIPS assistance information, information element is to transfer the required assistance information to indicate the paging subgroup used when paging the UE. The coding of the information element allows combining different types of PEIPS assistance information. The PEIPS assistance information, information element is coded as shown in figure 9.11.3.80.1, figure 9.11.3.80.2, figure 9.11.3.80.3 and table 9.11.3.80.1. The PEIPS assistance information is a type 4 information element, with a minimum length of 3 octets. Figure 9.11.3.80.1: PEIPS assistance information information element Figure 9.11.3.80.2: PEIPS assistance information type βtype of information= "000" Figure 9.11.3.80.3: PEIPS assistance information type βtype of information= "001" Table 9.11.3.80.1: PEIPS assistance information 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 | 9.11.3.80 |
4,854 | 20.3.1 Session start procedure | The BM-SC initiates the MBMS session start procedure when it is ready to send data. This informs the MBMS GW of the imminent start of the transmission and MBMS session attributes are provided to the MBMS GWs included in the list of downstream nodes in BM-SC. The bearer plane is allocated. BM-SC and MBMS GW shall at least support IP unicast encapsulation of IP multicast datagrams, which shall be default mode of sending user plane data. BM-SC may support IP multicast encapsulation of user plane IP multicast datagrams and MBMS GW also may support this mode of operation. Figure 20.3.1.1: MBMS Session Start procedure 1. The BM-SC sends an RAR message to indicate the impending start of the transmission and to provide the session attributes to the MBMS GWs listed in the "list of downstream nodes" parameter of the corresponding MBMS Bearer Context. BM-SC may indicate to MBMS GW that BM-SC supports sending the user plane IP multicast data without IP unicast encapsulation. In such case BM-SC shall send multicast source address as specified by IETF RFC 4604 [73] and IETF RFC 4607 [74] and the user plane multicast destination address. If IP unicast mode is used, the BM-SC shall also require the MBMS GW to select one UDP port for the reception of the user plane data for the related MBMS service (identified by TMGI and Flow ID). The BM-SC may also indicate its intent to use IP multicast encapsulation of IP multicast datagrams across Sgi-mb. In this case, the BM-SC shall specify an Sgi-mb (transport) destination multicast IP address associated with the MBMS bearer context, as well as the source UDP port. The inclusion of these data shall mean IP multicast encapsulation of IP multicast datagram is the only offered multicast mode over Sgi-mb. The destination UDP port for IP multicast transport shall be fixed as port number 927. The BM-SC shall also specify the (transport) multicast source address. The BM-SC shall indicate the M1 interface information of local MBMS information as specified in 3GPP TS 23.285[ Architecture enhancements for V2X services ] [112] if the BM-SC determines to use the local MBMS information. 2. The MBMS GW creates an MBMS Bearer Context, stores the session attributes in the MBMS Bearer Context, initiates session start procedure towards the MMEs/SGSNs in its list of MBMS control plane nodes and sends an RAA message to the BM-SC. In case MBMS GW receives BM-SC multicast source address, which indicates BM-SC support for both modes of sending user plane data, MBMS GW decides in which mode MBMS GW shall receive the user plane data. In case MBMS GW decides to receive unicast encapsulated data, then MBMS GW shall send own IP address for user plane to BM-SC and the MBMS GW shall also indicate the UDP port on which the user plane data shall be received. In case MBMS GW decides to receive IP multicast packets, then MBMS GW shall join the multicast group as specified by IETF RFC 4604 [73] and IETF RFC 4607 [74], and indicate to BM-SC about the decision. In case MBMS GW decides to use M1 interface information of local MBMS information, the MBMS GW skips the allocation procedure for IP multicast distribution. If configured, the MBMS GW sends the RAA message after receiving the first session start response (when positive) message from any MME. | 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 | 20.3.1 |
4,855 | 8.4.1.1 EN-DC | This clause gives the SgNB addition procedure in EN-DC given that en-gNB consists of gNB-CU and gNB-DU(s), as shown in Figure 8.4.1.1-1. Figure 8.4.1.1-1: SgNB addition procedure in EN-DC 1~8: refer to TS 37.340[ Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Overall Description; Stage-2 ] [12]. a1. After receiving the SGNB ADDITION REQUEST message from MeNB, the gNB-CU sends the UE CONTEXT SETUP REQUEST message to the gNB-DU to create a UE context. As specified in TS 37.340[ Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Overall Description; Stage-2 ] [12], in the course of a Secondary Node Change, the UE CONTEXT SETUP REQUEST message may contain source cell group configuration to allow gNB-DU to perform delta configuration. a2. The gNB-DU responds to the gNB-CU with the UE CONTEXT SETUP RESPONSE message. In case the gNB-DU receives the UE CONTEXT SETUP REQUEST message without the source cell group configuration or in the course of a Secondary Node Change as specified in TS 37.340[ Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Overall Description; Stage-2 ] [12] or if the gNB-DU decides to perform full configuration after receiving the source cell group configuration, it shall perform full configuration and indicate that it has applied full configuration in the UE CONTEXT SETUP RESPONSE message. NOTE: On Inter-gNB-CU Mobility, same method is performed to achieve full configuration and delta configuration. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 8.4.1.1 |
4,856 | 8.17.3.1 IAB inter-CU topology adaptation procedure | During the inter-CU topology adaptation for a single-connected IAB-node, the IAB-MT migrates from an old parent node to a new parent node, where the old and the new parent nodes are served by different IAB-donor-CUs. Without loss of generality, the old parent node is referred to as source parent node, and the new parent node is referred to as target parent node. Figure 8.17.3.1-1 shows an example of the topology adaptation procedure, where the IAB-MT is migrated from a source IAB-donor-CU to a target IAB-donor-CU. In this procedure, the migrating IAB-node becomes a boundary IAB-node since its IAB-DU retains F1AP with the source IAB-donor-CU while its IAB-MT obtains RRC connectivity with the target IAB-donor-CU. Figure 8.17.3.1-1: IAB inter-CU topology adaptation procedure 1. The source IAB-donor-CU sends an Xn HANDOVER REQUEST message to the target IAB-donor-CU . This message may include the migrating IAB-nodeβs TNL address information in the RRC container. 2. The target IAB-donor-CU sends a UE CONTEXT SETUP REQUEST message to the target parent node IAB-DU, to create the UE context for the migrating IAB-MT and to set up the bearers, which the migrating IAB-MT uses for its signaling, and, optionally, data traffic. 3. The target parent node IAB-DU responds to the target IAB-donor-CU with a UE CONTEXT SETUP RESPONSE message. 4. The target IAB-donor-CU performs admission control and provides the new RRC configuration as part of the HANDOVER REQUEST ACKNOWLEDGE message. The RRC configuration includes a BAP address for the boundary node in the target IAB-donor-CUβs topology, a default BH RLC channel and a default BAP routing ID configuration for UL F1-C/non-F1 traffic mapping on the target path. The RRC configuration may include the new TNL address(es) anchored at the target IAB-donor-DU for the migrating node. 5. The source IAB-donor-CU sends a UE CONTEXT MODIFICATION REQUEST message to the source parent node IAB-DU, which includes the received RRCReconfiguration message from the target IAB-donor-CU. 6. The source parent node IAB-DU forwards the received RRCReconfiguration message to the migrating IAB-MT. 7. The source parent node IAB-DU responds to the source IAB-donor-CU with the UE CONTEXT MODIFICATION RESPONSE message. 8. The migrating IAB-MT performs a random access procedure at the target parent node IAB-DU. 9. The migrating IAB-MT responds to the target parent node IAB-DU with an RRCReconfigurationComplete message. 10. The target parent node IAB-DU sends an UL RRC MESSAGE TRANSFER message to the target IAB-donor-CU, to convey the received RRCReconfigurationComplete message. 11. The target IAB-donor-CU triggers the path switch procedure for the migrating IAB-MT, if needed. 12. The target IAB-donor-CU sends UE CONTEXT RELEASE message to the source IAB-donor-CU. NOTE: The XnAP UE IDs of the migrating node are retained at target and source IAB-donor-CU as long as the target path is used for transport of traffic between the migrating node and the source IAB-donor-CU. 13. The source IAB-donor-CU may release BH RLC channels and BAP-sublayer routing entries on the source path between source parent IAB-node of the migrating IAB-node and the source IAB-donor-DU. 14. The target IAB-donor-CU configures BH RLC channels and BAP-sublayer routing entries on the target path between the migrating IAB-node and target IAB-donor-DU, as well as DL mappings on the target IAB-donor-DU for the migrating IAB-nodeβs target path. These configurations support the transport of F1-C traffic on the target path. 15. The F1-C connection between the migrating IAB-node and the source IAB-donor-CU are switched to the target path using the new TNL address information of the migrating IAB-node. The migrating IAB-node may report the new TNL address information it wants to use for F1-U traffic to the source IAB-donor-CU, via the gNB-DU CONFIGURATION UPDATE message. In case IPsec tunnel mode is used for TNL protection, the migrating IAB-node may use MOBIKE (IETF RFC 4555 [29]) to migrate the IPsec tunnel to the new IP outer addresses. After the completion of the MOBIKE procedure, the migrating IAB-DU initiates an F1AP gNB-DU Configuration Update procedure from which the IAB-donor-CU can conclude whether the existing inner IP address(es) (e.g., for SCTP association) and the DL F-TEID can be reused. If new TNL addresses for F1-C traffic are configured, new SCTP association(s) between the migrating IAB-node and the F1-terminating IAB-donor-CU may be established using the new TNL address information of the migrating IAB-node. The migrating IAB-node sends an F1AP gNB-DU CONFIGURATION UPDATE message to the F1-terminating IAB-donor-CU, which may include new (outer) IP addresses and corresponding new (inner) IP address for the F1-U traffic to be switched to the target path. 16. The source IAB-donor-CU sends an IAB TRANSPORT MIGRATION MANAGEMENT REQUEST message to the target IAB-donor-CU, to provide the context of the traffic to be offloaded. The message may include the new DL TNL address information necessary for the target IAB-donor-CU to configure or modify DL mappings on the target IAB-donor-DU. 17. The target IAB-donor-CU may configure or modify BH RLC channels and BAP-sublayer routing entries on the target path between the migrating IAB-node and target IAB-donor-DU, as well as DL mappings on the target IAB-donor-DU for the migrating IAB-nodeβs target path. These configurations may support the transport of UP and non-UP traffic on the target path. 18. The target IAB-donor-CU responds to the source IAB-donor-CU with an IAB Transport Migration Management Response message, to provide the mapping information for the traffic to be offloaded. The message includes the L2 info that is used in the target IAB-donor-CUβs topology and necessary to configure the migrating IAB-node with the UL mappings of traffic indicated in step 16. The message includes the DSCP/IPv6 Flow Label values used to configure the DL mappings of traffic indicated in step 16. 19. The F1-U connections of the migrating IAB-node with the source IAB-donor-CU are switched to use the migrating IAB-nodeβs new TNL address(es). The source IAB-donor-CU provides to the IAB-DU of the migrating IAB-node the updated UL BH information for the traffic indicated in step 16, based on the UL BH information received from the target IAB-donor-CU in step 18. The source IAB-donor-CU may also update the UL BH information associated with non-UP traffic. This step may use UE associated signaling or non-UE associated signaling in E1 and/or F1 interface. Implementation must ensure the avoidance of potential race conditions, i.e., that no conflicting configurations are concurrently performed using UE-associated and non-UE-associated procedures. 20. The steps 16 to 19 may be repeated, if needed, where the source IAB-donor-CU can request the offload of further traffic, or the modification or release of offloaded traffic. The target IAB-donor-CU can fully or partially reject addition or modification requests by the source IAB-donor-CU. The target IAB-donor-CU may request the modification of the L2 transport for the offloaded traffic in the target IAB-donor-CUβs topology using the IAB TRANSPORT MIGRATION MODIFICATION REQUEST message. The source IAB-donor-CU reconfigures the UL BH mappings accordingly, and acknowledges the modification via the IAB TRANSPORT MIGRATION MODIFICATION RESPONSE message. The target IAB-donor-CU may further reconfigure the TNL addresses of the migrating IAB-node via RRC. The traffic offload through the inter-CU topology adaptation procedure for the migrating IAB-node can be fully revoked. The non-F1-terminating IAB-donor-CU can initiate the full revoking of traffic offload by executing the XnAP Handover Preparation procedure for the migrating IAB-MT. After the migrating IAB-MT is handed over in reverse direction, i.e., from the non-F1-terminating IAB-donor-CU to the F1-terminating IAB-donor-CU, the traffic of the migrating IAB-nodeβs IAB-DU is routed again along the former source path. The F1-terminating IAB-donor-CU can initiate the full revoking of traffic offload by requesting the release of all offloaded traffic from the non-F1-terminating IAB-donor-CU by sending the IAB TRANSPORT MIGRATION MANAGEMENT REQUEST to the non-F1-terminating IAB-donor-CU. This message may trigger the XnAP Handover Preparation procedure for the migrating IAB-MT towards the F1-terminating IAB-donor-CU. The F1-terminating IAB-donor-CU may request full or partial release of the offloaded traffic from the non-F1-terminating IAB-donor-CU via the IAB TRANSPORT MIGRATION MANAGEMENT REQUEST message. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 8.17.3.1 |
4,857 | 9.3.31.1 User-user | Some networks may only support a maximum length of 35 octets. Procedures for interworking are not currently defined and are for further study. R98 and earlier versions of this protocol specified a minimum length of 3 octets for this information element (not counting the IEI). To avoid interworking problems with mobile stations supporting only R98 or earlier versions of the protocol, the network shall deliver the User information message to these mobile stations only if the length of the User-user IE is greater or equal to 3 octets (not counting the IEI). | 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 | 9.3.31.1 |
4,858 | 10.8 Cross Carrier Scheduling | Cross-carrier scheduling with the Carrier Indicator Field (CIF) allows the PDCCH of a serving cell to schedule resources on another serving cell but with the following restrictions: - When cross-carrier scheduling from an SCell to PCell is not configured, PCell can only be scheduled via its PDCCH; - When cross-carrier scheduling from an SCell to PCell is configured: - PDCCH on that SCell can schedule PCell's PDSCH and PUSCH; - PDCCH on the PCell can schedule PCell's PDSCH and PUSCH but cannot schedule PDSCH and PUSCH on any other cell; - Only one SCell can be configured to be used for cross-carrier scheduling to PCell. - When an SCell is configured with a PDCCH, that cell's PDSCH and PUSCH are always scheduled by the PDCCH on this SCell; - When an SCell is not configured with a PDCCH, that SCell's PDSCH and PUSCH are always scheduled by a PDCCH on another serving cell; - The scheduling PDCCH and the scheduled PDSCH/PUSCH can use the same or different numerologies. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 10.8 |
4,859 | 5.2.3.4 Recall present | In the "recall present" state, the call control entity in the mobile station waits for acceptance of the Recall by the user. Once confirmation is received, the mobile station indicates acceptance of a recall by - sending a SETUP message to its peer entity in the network; - starting Timer T303; and - entering the "call initiated" state and proceeding as described in subclause 5.2.1.1. The MS shall ensure that the contents of the Bearer Capability IE(s) and Supported Codec List IE sent in the SETUP message are the same as the Bearer Capability IE(s) and Supported Codec List IE in the previous CC-ESTABLISHMENT CONFIRMED message related to this Network Initiated MO Call. In the "recall-present" state, if the user of a mobile station is User Determined User Busy then a RELEASE COMPLETE message shall be sent with cause #17 "user busy" In the "recall-present" state. If the user of a mobile station wishes to reject the recall then a RELEASE COMPLETE message shall be sent with cause #21 "call rejected". In either case, the mobile shall release the connection in accordance with subclause 5.4.2 On receipt of the SETUP message in the "recall present" state, the network shall stop timer T334 and proceed as specified in subclause 5.2.1.2. If the call control entity of the network does not receive a SETUP message before the expiry of timer T334, then the network shall send a RELEASE COMPLETE message to the mobile using cause #102 "recovery on timer expiry", release the MM connection, enter the "null" state and shall inform all appropriate entities within the network. Figure 5.7b/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Recall acceptance or rejection by user | 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.2.3.4 |
4,860 | 4.4.11 CSG Subscriber Server | CSG Subscriber Server (CSS) is an optional element that stores CSG subscription data for roaming subscribers. The CSS stores and provides VPLMN specific CSG subscription information to the MME. The CSS is accessible from the MME via the S7a interface. The CSS is always in the same PLMN as the current MME. If the same CSG ID exists in both CSS subscription data and HSS subscription data, the CSG subscription data from the HSS shall take precedence over the data from CSS. Figure 4.4.11-1 illustrates CSS connected to MME. Figure 4.4.11-1: CSS connected to MME | 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") | 4.4.11 |
4,861 | 5.3.4B.4 Establishment of S1-U bearer during Data Transport in Control Plane CIoT EPS Optimisation | Figure 5.3.4B.4-1: Establishment of S1-U bearer during Data Transport in Control Plane CIoT EPS Optimisation UE or MME can use this procedure if the UE and MME successfully negotiate S1-U data transfer or User Plane CIoT EPS Optimisation in addition to Control Plane CIoT EPS Optimisation based on the Preferred and Supported Network Behaviour as defined in clause 4.3.5.10. The MME either because it has received the NAS message as defined in steps 2-3 or the MME decides that S1-U based data transfer is now preferred e.g. determined by the size of data transferred in UL and DL using Control Plane CIoT EPS Optimisation triggers the establishment of S1-U bearer(s). The MME checks if the UE can support the establishment of required number of additional user plane radio bearers based on the maximum number of user plane radio bearers indicated by UE in the UE Network Capability IE as defined in clause 5.11.3. If the MME takes the decision that S1-U data transfer is now preferred steps 2-3 are not needed. 1. UE is sending and receiving data in NAS PDUs using the Control Plane CIoT EPS Optimisation. 2. The UE may be triggered to establish user plane bearers and sends a Control Plane Service Request with an active flag towards the MME encapsulated in an RRC message to the eNodeB. The RRC message and this NAS message are described in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [5] and TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [46] respectively. 3. The eNodeB forwards the Control Plane Service Request with active flag to MME. NAS message is encapsulated in an S1-AP UL NAS Transport Message (NAS message, TAI+ECGI of the serving cell, S-TMSI, CSG ID, CSG access Mode). Details of this step are described in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [5]. If the MME receives the Control Plane Service Request with active flag defined in steps 2-3 it shall establish S1-U bearer(s) and execute the transfer. If the MME cannot handle the procedure associated to the Control Plane Service Request with active flag, it shall reject it. CSG ID is provided if the UE sends the NAS message via a CSG cell or a hybrid cell. CSG access mode is provided if the UE sends the NAS message via a hybrid cell. If the CSG access mode is not provided but the CSG ID is provided, the MME shall consider the cell as a CSG cell.If a CSG ID is indicated and CSG access mode is not provided, and there is no subscription data for this CSG ID and associated PLMN or the CSG subscription is expired, the MME rejects the Control Plane Service Request with an appropriate cause. The UE shall remove the CSG ID and associated PLMN of the cell where the UE has initiated the service request procedure from the Allowed CSG list, if present. 4. The MME shall send any remaining UL data over S11-U and in order to minimize the possible occurrence of out of order DL data e.g. caused by earlier DL data which were sent on the Control Plane may send a Release Access Bearers Request message to the Serving GW that requests the release of all S11-U bearers for the UE. The MME locally deletes any existing ROHC context used for Control Plane CIoT EPS Optimisation, and other S11-U related information in UE context, including TEID (DL) for the S11-U, etc, but not the Header Compression Configuration. NOTE: The MME may use the "Delay Downlink Packet Notification Request" causing the Serving GW to not send Downlink Data Notifications as described in clause 5.3.4.2 to minimize the impact of possible Downlink Data Notifications this step may cause. 5. If the Serving GW receives the Release Access Bearers Request message it releases all MME related information (address and downlink TEIDs) for the UE and responds with a Release Access Bearers Response message to the MME. Other elements of the UE's Serving GW context are not affected. If downlink packets arrive for the UE, the Serving GW starts buffering downlink packets received for the UE and initiating the "Network Triggered Service Request" procedure, described in clause 5.3.4.3. 6. The MME sends S1-AP Initial Context Setup Request (Serving GW address, S1-TEID(s) (UL), EPS Bearer QoS(s), Security Context, MME Signalling Connection Id, Handover Restriction List, CSG Membership Indication, Service Accept) message to the eNodeB for all PDN connections that MME has not included Control Plane Only Indicator in ESM request. The MME responds to the UE with a Service Accept message. The eNodeB stores the Security Context, MME Signalling Connection Id, EPS Bearer QoS(s) and S1-TEID(s) in the UE RAN context. The step is described in detail in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [5]. Handover Restriction List is described in clause 4.3.5.7 "Mobility Restrictions". 7. If the Control Plane Service Request is performed via a hybrid cell, CSG Membership Indication indicating whether the UE is a CSG member shall be included in the S1-AP message from the MME to the RAN. Based on this information, the RAN can perform differentiated treatment for CSG and non-CSG members. The eNodeB performs the radio bearer establishment procedure. The user plane security is established at this step, which is described in detail in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [5]. The UE needs to locally delete any existing ROHC context used for Control Plane CIoT EPS Optimisation. When the user plane radio bearers are setup, EPS bearer state synchronization is performed between the UE and the network, i.e. the UE shall locally remove any EPS bearer for which the MME has not included Control Plane Only Indicator in ESM request and for which no radio bearers are setup. If the radio bearer for a default EPS bearer is not established, the UE shall locally deactivate all EPS bearers associated to that default EPS bearer. 8. As the user plane radio bearers are setup the UE shall use user plane bearers to transfer data PDUs, except for EPS bearers the MME has included Control Plane Only Indicator in ESM request and for which Control Plane CIoT EPS Optimisation is still be used. The uplink data from the UE can now be forwarded by eNodeB to the Serving GW. The eNodeB sends the uplink data to the Serving GW address and TEID provided in the step 6. The Serving GW forwards the uplink data to the PDN GW. 9. The eNodeB sends an S1-AP message Initial Context Setup Complete (eNodeB address, List of accepted EPS bearers, List of rejected EPS bearers, S1 TEID(s) (DL)) to the MME. This step is described in detail in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [5]. 10. The MME sends a Modify Bearer Request message (eNodeB address, S1 TEID(s) (DL) for the accepted EPS bearers, Delay Downlink Packet Notification Request, RAT Type) per PDN connection to the Serving GW. If the Serving GW supports Modify Access Bearers Request procedure and if there is no need for the Serving GW to send the signalling to the PDN GW, the MME may send Modify Access Bearer Request (eNodeB address(es) and TEIDs for downlink user plane for the accepted EPS bearers, Delay Downlink Packet Notification Request) per UE to the Serving GW to optimise the signalling. The Serving GW is now able to transmit downlink data towards the UE. 11. The Serving GW shall return a Modify Bearer Response (Serving GW address and TEID for uplink traffic) to the MME as a response to a Modify Bearer Request message, or a Modify Access Bearers Response (Serving GW address and TEID for uplink traffic) as a response to a Modify Access Bearers Request message. If the Serving GW cannot serve the MME Request in the Modify Access Bearers Request message without S5/S8 signalling other than to unpause charging in the PDN GW or without corresponding Gxc signalling when PMIP is used over the S5/S8 interface, it shall respond to the MME with indicating that the modifications are not limited to S1-U bearers, and the MME shall repeat its request using a Modify Bearer Request message per PDN connection. | 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.3.4B.4 |
4,862 | 4.14.2 Stand-alone non-public network (SNPN) | If the UE is not SNPN enabled, the UE is always considered to be not operating in SNPN access operation mode. If the UE is SNPN enabled, the UE can operate in SNPN access operation mode. Details of activation and deactivation of SNPN access operation mode at the SNPN-enabled UE are up to UE implementation. The functions and procedures of NAS described in the present document are applicable to an SNPN and an SNPN-enabled UE unless indicated otherwise. The key differences brought by the SNPN to the NAS layer are as follows: a) instead of the PLMN selection process, the SNPN selection process is performed by a UE operating in SNPN access operation mode (see 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5] and 3GPP TS 24.502[ Access to the 3GPP 5G Core Network (5GCN) via non-3GPP access networks ] [18] for further details on the SNPN selection); b) a "permanently forbidden SNPNs" list and a "temporarily forbidden SNPNs" list are managed per access type independently (i.e. 3GPP access or non-3GPP access) and, if the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, per entry of the "list of subscriber data" or, if the UE supports access to an SNPN using credentials from a credentials holder, per the PLMN subscription, by a UE operating in SNPN access operation mode instead of forbidden PLMN lists. If the UE supports onboarding services in SNPN, an additional "permanently forbidden SNPNs" list for onboarding services and an additional "temporarily forbidden SNPNs" list for onboarding services are managed. If the UE supports access to an SNPN providing access for localized services in SNPN, an additional "permanently forbidden SNPNs for access for localized services in SNPN" list and an additional "temporarily forbidden SNPNs for access for localized services in SNPN" list per entry of the "list of subscriber data" and per the PLMN subscription are managed for 3GPP access only. These lists shall be maintained across activation and deactivation of SNPN access operation mode; NOTE 0: On timer T3245 expiry when the UE supports access to an SNPN using credentials from a credentials holder using PLMN subscription, and the UE is not operating in SNPN access operation mode, as an implementation option the UE can delete the list of "temporarily forbidden SNPNs" and "permanently forbidden SNPNs" and additionally the list of "permanently forbidden SNPNs for access for localized services in SNPN" and list of "temporarily forbidden SNPNs for access for localized services in SNPN" if the UE supports access to an SNPN providing access for localized services in SNPN. c) inter-system change to and from S1 mode is not supported; d) void; e) CAG is not supported in SNPN access operation mode; f) with respect to the 5GMM cause values: 1) 5GMM cause values #74 "Temporarily not authorized for this SNPN" and #75 "Permanently not authorized for this SNPN" are supported whereas these 5GMM cause values cannot be used in a PLMN; and 2) 5GMM cause values #11 "PLMN not allowed", #31 "Redirection to EPC required", #73 "Serving network not authorized", and #76 "Not authorized for this CAG or authorized for CAG cells only" are not supported whereas these 5GMM cause values can be used in a PLMN; g) a list of "5GS forbidden tracking areas for roaming" and a list of "5GS forbidden tracking areas for regional provision of service" are managed per SNPN and, if the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, entry of the "list of subscriber data" or, if the UE supports access to an SNPN using credentials from a credentials holder,PLMN subscription (see 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]); h) when accessing SNPN services via a PLMN using 3GPP access, access to 5GCN of the SNPN is performed using 5GMM procedures for non-3GPP access, 5GMM parameters for non-3GPP access, the UE is performing access to SNPN over non-3GPP access and the UE is not operating in SNPN access operation mode over 3GPP access. When accessing PLMN services via a SNPN using 3GPP access, access to 5GCN of the PLMN is performed using 5GMM procedures for non-3GPP access, 5GMM parameters for non-3GPP access, the UE is not performing access to SNPN over non-3GPP access, and the UE is operating in SNPN access operation mode over 3GPP access. From the UE's NAS perspective, accessing PLMN services via an SNPN and accessing SNPN services via a PLMN are treated as untrusted non-3GPP access. If the UE is accessing the PLMN using non-3GPP access, the access to 5GCN of the SNPN via PLMN is not specified in this release of the specification . Emergency services are not supported in an SNPN when a UE accesses SNPN services via a PLMN; i) when registered to an SNPN, the UE shall use only the UE policies provided by the registered SNPN; j) inclusion of a TAI of an SNPN other than the registered SNPN, into the registration area is not supported. The AMF of an SNPN shall only include into the registration area one or more TAIs of the registered SNPN; j1) inclusion of a TAI of an SNPN other than the registered SNPN, into the LADN service area is not supported. The AMF of an SNPN shall only include one or more TAIs of the registered SNPN into the LADN service area; j2) inclusion of a TAI of an SNPN other than the registered SNPN, into the allowed area or the non-allowed area, of the 3GPP access service area restrictions is not supported. The AMF of an SNPN shall include only one or more TAIs of the registered SNPN into the allowed area or the non-allowed area, of the 3GPP access service area restrictions; k) void; l) void; m) UE mobility between SNPNs in 5GMM-CONNECTED mode is supported when the SNPNs are equivalent SNPNs for the selected entry of the "list of subscriber data" or the selected PLMN subscription. UE mobility between SNPNs in 5GMM-IDLE mode is supported when the UE supports access to an SNPN using credentials from a credentials holder or when the SNPNs are equivalent SNPNs or both for the selected entry of the "list of subscriber data" or the selected PLMN subscription. UE mobility between an SNPN and a PLMN is not supported; n) CIoT 5GS optimizations are not supported; o) void; p) when registering or registered to an SNPN, the UE shall handle the 5GS mobile identity as described in subclause 5.5.1.2.2; q) when registering or registered to an SNPN, the UE shall only consider: 1) a last visited registered TAI visited in the same SNPN as an available last visited registered TAI; or 2) a last visited registered TAI visited using the same entry of the "list of subscriber data" or the same PLMN subscription as an available last visited registered TAI, if the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both; NOTE 1: If the last visited registered TAI is assigned by an SNPN other than the current SNPN, the serving AMF can determine the SNPN assigning the last visited registered TAI using the NID provided by the UE. r) emergency service fallback is not supported; s) when registering or registered for onboarding services in SNPN, the UE shall not provide the requested NSSAI to the network; s1) when performing initial registration for onboarding services in SNPN, the UE shall set the 5GS registration type value to "SNPN onboarding registration"; t) when registering or registered for onboarding services in SNPN, the AMF shall not provide the configured NSSAI, the allowed NSSAI or the rejected NSSAI to the UE, shall use the S-NSSAI included in the AMF onboarding configuration data for onboarding services in SNPN and shall not perform NSSAA procedure for S-NSSAI used for onboarding services in SNPN; u) the UE can access an SNPN indicating that onboarding is allowed using default UE credentials for primary authentication in order for the UE to be configured with one or more entries of the "list of subscriber data"; x) eCall over IMS is not supported in SNPN access operation mode and the UE ignores any USIM configuration for eCall only mode; y) when registering or registered for onboarding services in SNPN, the AMF shall store in the 5GMM context of the UE an indication that the UE is registered for onboarding services in SNPN; z) a UE with multiple valid entries of "list of subscriber data", or one or more valid USIMs and one or more valid entries of "list of subscriber data", capable of initiating and maintaining simultaneous separate registration states over 3GPP access with PLMN(s) or SNPN(s), using identities and credentials associated with those entries of "list of subscriber data", or USIMs and entries of "list of subscriber data", and supporting one or more of the N1 NAS signalling connection release, the paging indication for voice services, the reject paging request, the paging restriction and the paging timing collision control may use procedures defined for MUSIM UE, even if the UE does not include multiple valid USIMs; za) when the UE is registering or registered for onboarding services in SNPN, the network slice admission control is not performed; NOTE 2: If the network determines that the UE cannot register to the onboarding SNPN due to lack of resources for the network slice used for onboarding, the AMF can reject the UE with 5GMM cause #22 "congestion". zb) when the UE is registered for onboarding services in SNPN (as specified in subclause 3.1), the UE determines that the number dialled is an emergency number, and emergency services are not supported in the SNPN, the UE shall perform a local de-registration and utilize 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] to select a domain for the emergency session attempt; and NOTE 4: The UE can select PS domain for emergency session attempt. v) proximity based services (5G ProSe as specified in 3GPP TS 24.554[ Proximity-services (ProSe) in 5G System (5GS) protocol aspects; Stage 3 ] [19E]) are not supported. | 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.14.2 |
4,863 | 3.3 Symbols | For the purposes of the present document, the following symbols apply: Gb Interface between an SGSN and a BSC. Gi Reference point between Packet Domain and an external packet data network. Gmb Reference point between GGSN and BM-SC. Gn Interface between two GSNs within the same PLMN. Go Interface between a GGSN and a PDF. Gp Interface between two GSNs in different PLMNs. The Gp interface allows support of Packet Domain network services across areas served by the co-operating PLMNs. Gs Interface between an SGSN and MSC. Iu Interface between the RNS and the core network. It is also considered as a reference point. Pk Reference Point between GGSN and Presence Network Agent. R The reference point between a non-ISDN compatible TE and MT. Typically this reference point supports a standard serial interface. S2a It provides the user plane with related control and mobility support between trusted non-3GPP IP access and P-GW. S2b It provides the user plane with related control and mobility support between ePDG and P-GW. S2c It provides the user plane with related control and mobility support between UE and P-GW. This reference point is implemented over trusted and/or untrusted non-3GPP Access and/or 3GPP access. S5 Interface between a S-GW and a P-GW within the same PLMN. S8 Interface between a S-GW and a P-GW in different PLMNs. Sgi The reference point between the EPC based PLMN and the packet data network. Sgi-mb The reference point between BM-SC and MBMS GW for MBMS data delivery. SGmb The reference point for the control plane between BM-SC and MBMS GW. T6a Reference point used between SCEF and serving MME. T6b Reference point used between SCEF and serving SGSN. Um The interface between the MS and the fixed network part in A/Gb mode. The Um interface is the A/Gb mode network interface for providing packet data services over the radio to the MS. The MT part of the MS is used to access the GSM services through this interface. Uu Interface between the mobile station (MS) and the fixed network part in Iu mode. The Uu interface is the Iu mode network interface for providing packet data services over the radio to the MS. The MT part of the MS is used to access the UMTS services through this interface. | 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 | 3.3 |
4,864 | 5.7.3.4 Setting the contents of MeasResultSCG-Failure | The UE shall set the contents of the MeasResultSCG-Failure as follows: 1> for each MeasObjectNR configured on NR SCG for which a measId is configured and measurement results are available: 2> include an entry in measResultPerMOList; 2> if there is a measId configured with the MeasObjectNR and a reportConfig which has rsType set to ssb: 3> set ssbFrequency to the value indicated by ssbFrequency as included in the MeasObjectNR; 2> if there is a measId configured with the MeasObjectNR and a reportConfig which has rsType set to csi-rs: 3> set refFreqCSI-RS to the value indicated by refFreqCSI-RS as included in the associated measurement object; 2> if a serving cell is associated with the MeasObjectNR: 3> set measResultServingCell to include the available quantities of the concerned cell and in accordance with the performance requirements in TS 38.133[ NR; Requirements for support of radio resource management ] [14]; 2> set the measResultNeighCellList to include the best measured cells, ordered such that the best cell is listed first, and based on measurements collected up to the moment the UE detected the failure, and set its fields as follows; 3> ordering the cells with sorting as follows: 4> based on SS/PBCH block if SS/PBCH block measurement results are available and otherwise based on CSI-RS; 4> using RSRP if RSRP measurement results are available, otherwise using RSRQ if RSRQ measurement results are available, otherwise using SINR; 3> for each neighbour cell included: 4> include the optional fields that are available. NOTE: The measured quantities are filtered by the L3 filter as configured in the mobility measurement configuration. The measurements are based on the time domain measurement resource restriction, if configured. Exclude-listed cells are not required to be reported. 1> if available, set the locationInfo as in 5.3.3.7 according to the otherConfig associated with the NR SCG. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.7.3.4 |
4,865 | 5.2.18.3.5 Nucmf_UECapabilityManagement_Notify service operation | Service Operation name: Nucmf_UECapabilityManagement_Notify Description: Producer NF provides notifications about changes in UCMF to subscribed consumer NF. Inputs, Required: Notification Type ("creation", "deletion", "Added IMEI/TAC in Manufacturer Assigned operation requested list", "Removed IMEI/TAC from Manufacturer Assigned operation requested list", "Removed UE Radio Capability ID from Manufacturer Assigned operation requuested list"). Inputs, Optional: If Notification Type is set to "creation": One or more UCMF dictionary entries, each UCMF dictionary entry consisting of a UE Radio Capability ID and the corresponding UE Radio Access Capability. If Notification Type is set to "deletion": One or more UE Radio Capability IDs. If Notification Type is set to "Added IMEI/TAC in Manufacturer Assigned operation requested list" or "Removed IMEI/TAC from Manufacturer Assigned operation requested list", one or more IMEI/TACs, if Notification type is "Removed UE Radio Capability ID from Manufacturer Assigned operation requested list, one or more PLMN assigned UE radio Capability IDs. Outputs, Required: None. Outputs, Optional: None. The Manufacturer Assigned operation requested list is defined in clause 5.11.3a of TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13] and clause 5.4.4.1a of the present document. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.18.3.5 |
4,866 | 4.3.13 Closed Subscriber Group functions | Closed Subscriber Group identifies a group of subscribers who are permitted to access one or more CSG cells of the PLMN as a member of the CSG for a HeNB. The following CSG related functions are defined: - CSG subscription handling function stores and updates the user's CSG subscription data at the UE and the network. - For closed mode, CSG access control function ensures a UE has valid subscription at a CSG where it performs an access. - Admission and rate control function is used to provide different admission and rate control for CSG and non-CSG members for a hybrid CSG cell. - CSG charging function enables per CSG charging for a subscriber consuming network services via a CSG cell or a hybrid cell. - CSG Paging Optimisation function is optionally used to filter paging messages as described in clause 5.3.4.3. - VPLMN Autonomous CSG roaming function is optionally supported whereby a VPLMN, if allowed by the HPLMN, stores and manages VPLMN specific CSG subscription information for roaming UEs without interaction with the HSS. - CSG membership verification without updating the User CSG Information in the Core Network in the case of Dual Connectivity when the Secondary eNodeB is a hybrid access eNodeB. | 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") | 4.3.13 |
4,867 | 4.9.1 Handover procedures in 3GPP access 4.9.1.1 General | These procedures are used to hand over a UE from a source NG-RAN node to a target NG-RAN node using the Xn or N2 reference points. This can be triggered, for example, due to new radio conditions, load balancing or due to specific service e.g. in the presence of QoS Flow for voice, the source NG-RAN node being NR may trigger handover to E-UTRA connected to 5GC. As defined in TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [10] a generic mechanism exists for the source NG-RAN node to retrieve information on the level of support for a certain feature at the target NG-RAN side associated with an NGAP IE. The mechanism makes use of the Source to Target and Target to Source transparent containers. The Inter NG-RAN node N2 based handover procedure specified in clause 4.9.1.3 may also be used for intra-NG-RAN node handover. NOTE: One use case for intra-NG-RAN handover to be performed by the Inter NG-RAN node N2 based handover procedure is when an NG-RAN node serves a satellite access system that covers more than one country. In such a situation, the UE might move from a "cell" in one country into a "cell" in another country and the NG-RAN node may need to cause the AMF to change to an AMF serving the UE's new country. The RRC Inactive Assistance Information is included in N2 Path Switch Request Ack message for Xn based handover or Handover Request message for N2 based handover (see clause 5.3.3.2.5 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]). | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.9.1 |
4,868 | 8.2.4.2 Old P-TMSI signature | The UE shall include this IE if the UE holds a valid P-TMSI signature, P-TMSI and RAI, and the TIN either indicates "P-TMSI" or is deleted. If the UE is configured for "AttachWithIMSI" as specified in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [15A] or 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [17] and is attaching in a new PLMN that is neither the registered PLMN nor in the list of equivalent PLMNs, the UE shall not include this IE. | 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 | 8.2.4.2 |
4,869 | 11.1 EAP based secondary authentication by an external DN-AAA server 11.1.1 General | This sub-clause specifies support for optional to use secondary authentication between the UE and an external data network (DN). The EAP framework specified in RFC 3748 [27] shall be used for authentication between the UE and a DN-AAA server in the external data network. The SMF shall perform the role of the EAP Authenticator. In the non-roaming scenario, the SMF shall perform the role of EAP Authenticator. And In the local break out scenario, the V-SMF of visited nework shall perform the role of EAP Authenticator. In the Home Routed deployment scenario, the H-SMF shall perform the role of the EAP Authenticator and the V-SMF shall transport the EAP messages exchanged between the UE and H-SMF. It shall rely on the external DN-AAA server to authenticate and authorize the UE's request for the establishment of PDU sessions. Between the UE and the SMF, EAP messages shall be sent in the SM NAS message. This message is received at the AMF over N1 and delivered to the SMF over N11 using either the Nsmf_PDUSession_CreateSMContext service operation or the Nsmf_PDUSession_Update SM Context service operation, as specified in TS23.502 [8]. The SMF that takes the role of the EAP authenticator communicates with the external DN-AAA over N4 and N6 via the UPF. The SMF invokes the Namf_Communication_N1N2MessageTransfer service operation to transfer the N1 NAS message containing the EAP message, towards the UE via the AMF. Following clauses describe the procedures for initial Authentication and Re-Authentication with the external DN-AAA server. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 11.1 |
4,870 | 8.10.1.1.14 HST-SFN performance | 8.10.1.1.14.1 Minimum Requirement for Rel-16 further enhanced HST The requirements are specified in Table 8.10.1.1.14.1-2, with the addition of the parameters in Table 8.10.1.1.14.1-1 and the downlink physical channel setup according to Annex C.3.2. The purpose of this test is to verify UE performance in the HST-SFN-500 scenario. The test for HST-SFN-500 scenario defined in B.3B is applied when highSpeedEnhDemodFlag2-r16 [7] is received. Table 8.10.1.1.14.1-1: Test Parameters for UE performance in HST-SFN-500 scenario (FRC) Table 8.10.1.1.14.1-2: Minimum performance UE in HST-SFN-500 scenario (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.10.1.1.14 |
4,871 | 15.2 Structure of TMGI | Temporary Mobile Group Identity (TMGI) is used within MBMS to uniquely identify Multicast and Broadcast bearer services. TMGI is composed as shown in figure 15.2.1. Figure 15.2.1: Structure of TMGI The TMGI is composed of three parts: 1) MBMS Service ID consisting of three octets. MBMS Service ID consists of a 6-digit fixed-length hexadecimal number between 000000 and FFFFFF. MBMS Service ID uniquely identifies an MBMS bearer service within a PLMN. The structure of MBMS Service ID for services for Receive only mode is defined in 3GPP TS 24.116[ Stage 3 aspects of system architecture enhancements for TV services ] [118]. 2) Mobile Country Code (MCC) consisting of three digits. The MCC identifies uniquely the country of domicile of the BM-SC, except for the MCC value of 901, which does not identify any country and is assigned globally by ITU; 3) Mobile Network Code (MNC) consisting of two or three digits (depending on the assignment to the PLMN by its national numbering plan administrator). The MNC identifies the PLMN which the BM-SC belongs to, except for the MNC value of 56 when the MCC value is 901, which does not identify any PLMN. For more information on the use of the TMGI, see 3GPP TS 23.246[ Multimedia Broadcast/Multicast Service (MBMS); Architecture and functional description ] [52]. Any TMGI with MCC=901 and MNC=56 is used only for services for Receive Only Mode (see TS 23.246[ Multimedia Broadcast/Multicast Service (MBMS); Architecture and functional description ] [52] and 3GPP TS 24.116[ Stage 3 aspects of system architecture enhancements for TV services ] [118]). | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 15.2 |
4,872 | 4.3.1.1.1 Attempted outgoing intra-eNB/RN handovers per handover cause | This measurement provides the number of attempted outgoing intra-eNB/RN handovers per handover cause. CC. Transmission of the RRCConnectionReconfiguration message by the eNB/RN to the UE triggering the intra-eNB/RN handover (see TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8]). Each RRCConnectionReconfiguration message transimtted is added to the relevant per handover cause measurement, the possible causes are included in TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [9]. The sum of all supported per cause measurements shall equal the total number of outgoing intra-eNB/RN handover events. In case only a subset of per cause 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 causes supported plus a possible sum value identified by the .sum suffix. HO.IntraEnbOutAtt.Cause where Cause identifies the cause for handover. 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.3.1.1.1 |
4,873 | 6.4.2 Requirements 6.4.2.1 General | The 5G system shall minimize control and user plane resource usage for data transfer from send only UEs. The 5G system shall minimize control and user plane resource usage for stationary UEs (e.g. lower signalling to user data resource usage ratio). The 5G system shall minimize control and user plane resource usage for transfer of infrequent small data units. The 5G system shall optimize the resource use of the control plane and/or user plane for transfer of small data units. The 5G system shall optimize the resource use of the control plane and/or user plane for transfer of continuous uplink data that requires both high data rate (e.g. 10 Mbit/s) and very low end-to-end latency (e.g. 1-10 ms). The 5G network shall optimize the resource use of the control plane and/or user plane to support high density connections (e.g. 1 million connections per square kilometre) taking into account, for example, the following criteria: - type of mobility support; - communication pattern (e.g. send-only, frequent or infrequent); - characteristics of payload (e.g. small or large size data payload); - characteristics of application (e.g. provisioning operation, normal data transfer); - UE location; - timing pattern of data transfer (e.g. real time or non-delay sensitive). The 5G system shall efficiently support service discovery mechanisms where UEs can discover, subject to access rights: - status of other UEs (e.g. sound on/off); - capabilities of other UEs (e.g. the UE is a relay UE) and/or; - services provided by other UEs (e.g. the UE is a colour printer). The 5G system shall be able to minimise the amount of wireless backhaul traffic (e.g. consolidating data transmissions to 1 larger rather than many smaller), when applicable (e.g. providing service in an area subject to power outages). The 5G system shall support small form factor UEs with single antenna. NOTE: Small form factor UEs are typically expected to have the diagonal less than 1/5 of the lowest supported frequency wave length. Satellite access related resource efficiency requirements are covered in clause 6.46.5. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.4.2 |
4,874 | 6.1.3.2.2 Unsuccessful Secondary PDP Context Activation Procedure initiated by the MS 6.1.3.2.2.1 General | Upon receipt of an ACTIVATE SECONDARY PDP CONTEXT REQUEST message, the network may reject the MS initiated PDP context activation by sending an ACTIVATE SECONDARY PDP CONTEXT REJECT message to the MS. The message shall contain a cause code that typically indicates one of the following: # 26: insufficient resources; # 30: activation rejected by GGSN, Serving GW or PDN GW; # 31: activation rejected, unspecified; # 32: service option not supported; # 33: requested service option not subscribed; # 34: service option temporarily out of order; # 41: semantic error in the TFT operation; # 42: syntactical error in the TFT operation; # 43: unknown PDP context; # 44: semantic errors in packet filter(s); # 45: syntactical errors in packet filter(s); # 46: PDP context without TFT already activated; # 48: request rejected, Bearer Control Mode violation; # 56: collision with network initiated request; # 60: bearer handling not supported; # 65: maximum number of PDP contexts reached; or # 95 - 111: protocol errors. The network may include a Back-off timer value IE in the ACTIVATE SECONDARY PDP CONTEXT REJECT message. If the Back-off timer value IE is included and the SM cause value is different from #26 "insufficient resources" and #65 "maximum number of PDP contexts reached", the network may include the Re-attempt indicator IE to indicate whether the MS is allowed to attempt a bearer resource allocation procedure in the PLMN for the same in S1 mode, and whether another attempt in A/Gb and Iu mode or in S1 mode is allowed in an equivalent PLMN. If the ACTIVATE SECONDARY PDP CONTEXT REQUEST message is related to an already active LIPA PDN connection or SIPTO at the local network PDN connection, then the network shall reply with an ACTIVATE SECONDARY PDP CONTEXT REJECT message with cause code #60 "bearer handling not supported". If a PDP context for the TI given in the Linked TI IE exists, then the TFT in the ACTIVATE SECONDARY PDP CONTEXT REQUEST message is checked by the network for different types of TFT IE errors as specified in subclause 6.1.3.2.3. Upon receipt of an ACTIVATE SECONDARY PDP CONTEXT REJECT message, the MS shall stop timer T3380 and enter the state PDP-INACTIVE. | 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.3.2.2 |
4,875 | 5.27.1.4 DS-TT and NW-TT Time Synchronization functionality | This clause describes the support of Time Synchronization functionality supported by the 5G System. Synchronization between UPF/NW-TT and NG-RAN is outside scope of 3GPP. DS-TT and NW-TT may support the following PTP instance types: - Boundary Clock as defined in IEEE Std 1588 [126] as described in clause 5.27.1.1; - End-to-End Transparent Clock as defined in IEEE Std 1588 [126] as described in clause 5.27.1.1; - Peer-to-Peer Transparent Clock as defined in IEEE Std 1588 [126] as described in clause 5.27.1.1; - PTP Relay instance as defined in IEEE Std 802.1AS [104]. Editor's note: Support for external networks operating with IEEE Std 1588-2008 [107] is for further study. DS-TT and NW-TT may support the following transports for PTP: - IPv4 as defined in IEEE Std 1588 [126] Annex C; - IPv6 as defined in IEEE Std 1588 [126] Annex D; IEEE Std 802.3 [131] (Ethernet) as defined in IEEE Std 1588 [126] Annex E. For operation as a Boundary clock or as a Transparent Clock, DS-TT and NW-TT may support the following path and link delay measurement methods: - Delay request-response mechanism as described in clause 11.3 of IEEE Std 1588 [126]; - Peer-to-peer delay mechanism as defined in clause 11.4 of IEEE Std 1588 [126]. DS-TT and NW-TT may support acting as a PTP grandmaster, i.e. may support generating (g)PTP Announce, Sync and Follow_Up messages. DS-TT and NW-TT supporting (g)PTP shall support one or more PTP profiles as described in clause 20.3 of IEEE Std 1588 [126], i.e.: - Default PTP Profiles in IEEE Std 1588 [126], Annex I; - IEEE Std 802.1AS [104] PTP profile for transport of timing as defined in IEEE Std 802.1AS [104] Annex F; - SMPTE Profile for Use of IEEE Std 1588 [126] Precision Time Protocol in Professional Broadcast Applications ST 2059-2:2015 [127]. TSN AF and TSCTSF may determine the PTP functionalities supported by DS-TT and NW-TT and may configure PTP instances in DS-TT and NW-TT using port and user plane node management information exchange as described in Annex K, clause K.2. NOTE: How the TSN AF or TSCTSF assigns NW-TT port(s) of one NW-TT to different PTP instances is up to implementation. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.27.1.4 |
4,876 | β PDSCH-ServingCellConfig | The IE PDSCH-ServingCellConfig is used to configure UE specific PDSCH parameters that are common across the UE's BWPs of one serving cell. PDSCH-ServingCellConfig information element -- ASN1START -- TAG-PDSCH-SERVINGCELLCONFIG-START PDSCH-ServingCellConfig ::= SEQUENCE { codeBlockGroupTransmission SetupRelease { PDSCH-CodeBlockGroupTransmission } OPTIONAL, -- Need M xOverhead ENUMERATED { xOh6, xOh12, xOh18 } OPTIONAL, -- Need S nrofHARQ-ProcessesForPDSCH ENUMERATED {n2, n4, n6, n10, n12, n16} OPTIONAL, -- Need S pucch-Cell ServCellIndex OPTIONAL, -- Cond SCellAddOnly ..., [[ maxMIMO-Layers INTEGER (1..8) OPTIONAL, -- Need M processingType2Enabled BOOLEAN OPTIONAL -- Need M ]], [[ pdsch-CodeBlockGroupTransmissionList-r16 SetupRelease { PDSCH-CodeBlockGroupTransmissionList-r16 } OPTIONAL -- Need M ]], [[ downlinkHARQ-FeedbackDisabled-r17 SetupRelease { DownlinkHARQ-FeedbackDisabled-r17 } OPTIONAL, -- Need M nrofHARQ-ProcessesForPDSCH-v1700 ENUMERATED {n32} OPTIONAL -- Need R ]] } PDSCH-CodeBlockGroupTransmission ::= SEQUENCE { maxCodeBlockGroupsPerTransportBlock ENUMERATED {n2, n4, n6, n8}, codeBlockGroupFlushIndicator BOOLEAN, ... } PDSCH-CodeBlockGroupTransmissionList-r16 ::= SEQUENCE (SIZE (1..2)) OF PDSCH-CodeBlockGroupTransmission DownlinkHARQ-FeedbackDisabled-r17 ::= BIT STRING (SIZE (32)) -- TAG-PDSCH-SERVINGCELLCONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | β |
4,877 | 16.6 AF Authorization for network slice quota-usage information notification/retrieval 16.6.2 General | If an AF is deployed within the 3GPP operator domain, an S-NSSAI is allowed to be sent to the AF. The baseline procedure for notifying the AF slice usage information (e.g. number of UEs and PDU Sessions in the slice indicated by the S-NSSAI) and the procedure for retrieving slice usage information by the AF are defined in TS 23.502[ Procedures for the 5G System (5GS) ] [8]. If an AF is deployed outside the 3GPP operator domain, an S-NSSAI is not allowed to be sent to the AF as required in clasue 5.9.2.3. The procedure for notifying the AF slice usage information (e.g. number of UEs and PDU Sessions in the slice indicated by the S-NSSAI) and the procedure for retrieving slice usage information by the AF are described in clause 16.6.3. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 16.6 |
4,878 | 8.2.1.3.6 Minimum Requirement 2 Tx Antenna Port (network-based CRS interference mitigation) | The requirements are specified in Table 8.2.1.3.6-2, with the addition of parameters in Table 8.2.1.3.6-1 and the downlink physical channel setup according to Annex C.3.2. The purpose is to verify the performance of open-loop spatial multiplexing performence with 2 transmit antennas when the PDSCH transmission in the serving cell is interfered by CRS of one dominant interfering cell with network-based CRS interference mitigation. In Table 8.2.1.3.6-1, Cell 1 is the serving cell, and Cell 2 is interfering cell. The downlink physical channel setup is according to Annex C.3.2 for each of Cell 1 and Cell 2 respectively. Table 8.2.1.3.6-1: Test parameters for Larger Delay CDD (FRC) with network-based CRS interference mitigation Table 8.2.1.3.6-2: Minimum performance Large Delay CDD (FRC) with network-based CRS interference mitigation | 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.1.3.6 |
4,879 | 9.3 5G Timing Resiliency | The 5G system shall be able to collect charging information based on the timing source (e.g., the source in use, start and stop of source usage). The 5G system shall be able to collect charging information per UE for use of a timing source (e.g., start/stop time and source used by a UE, timing source used by UE, holdover capability). The 5G system shall be able to collect charging information on 5G system timing resiliency (e.g., resiliency KPIs, holdover capability, number of UEs using a certain timing source). The 5G system shall be able to collect charging information per application using 5G timing resiliency, including 3rd party application, (e.g., timing resiliency KPIs, holdover capability, number of UEs using a certain timing source). | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 9.3 |
4,880 | 5.5.3.1 Status enquiry procedure | Whenever a call control entity wishes to check the call state of its peer entity, it may initiate the status enquiry procedure. NOTE: This may, in particular, apply to procedural error conditions described in clause 8. A call control entity initiates the status enquiry procedure by sending the STATUS ENQUIRY message and starting timer T322. The value of T322 is implementation dependent in the MS and set in the network by the network operator. While timer T322 is running, the call control entity shall not send further STATUS ENQUIRY messages. Upon receipt of a STATUS ENQUIRY message, the receiver shall respond with a STATUS message, reporting the current call state and cause value #30 "response to STATUS ENQUIRY". Receipt of the STATUS ENQUIRY shall not result in a state change relating to any protocol and connection of the receiver. If a STATUS message is received that contains cause value #30 "response to status enquiry", timer T322 shall be stopped and further appropriate actions taken, based on the information in that STATUS message, relative to the current state of the receiver of the STATUS message. These further "appropriate actions" are implementation dependent. However, the actions prescribed in subclause 5.5.3.2 shall apply. If a clearing message is received while timer T322 is running, timer T322 shall be stopped, and call clearing shall continue. If timer T322 expires, the STATUS ENQUIRY message may be retransmitted maximally once. If T322 expires after the STATUS ENQUIRY has been transmitted the maximum number of times, clearing of the call shall be initiated with cause value #41, "temporary failure", in the first call clearing message. | 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.5.3.1 |
4,881 | 10.5.3.13 Emergency Number List | The purpose of this information element is to encode emergency number(s) for use within the country where the IE is received. The Emergency Number List information element is coded as shown in figure 10.5.84c/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The Emergency Number List IE is a type 4 information element with a minimum length of 5 octets and a maximum length of 50 octets. NOTE 1: The length contains the number of octets used to encode the Emergency Service Category Value and the Number digits. NOTE 2: The number digit(s) in octet 5 precedes the digit(s) in octet 6 etc. The number digit, which would be entered first, is located in octet 5, bits 1 to 4. The contents of the number digits are coded as shown in table 10.5.118/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . NOTE 3: If the emergeny number contains an odd number of digits, bits 5 to 8 of the last octet of the respective emergency number shall be filled with an end mark coded as "1111". Figure 10.5.84c/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Emergency Number List information element Table 10.5.97aa/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Emergency Number List 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.3.13 |
4,882 | 5.7.3.3 Failure type determination for (NG)EN-DC | The UE shall set the SCG failure type as follows: 1> if the UE initiates transmission of the SCGFailureInformationNR message due to T310 expiry: 2> set the failureType as t310-Expiry; 1> else if the UE initiates transmission of the SCGFailureInformationNR message due to T312 expiry: 2> set the failureType as any value and set the failureType-v1610 as t312-Expiry; 1> else if the UE initiates transmission of the SCGFailureInformationNR message to provide reconfiguration with sync failure information for an SCG: 2> set the failureType as synchReconfigFailureSCG; 1> else if the UE initiates transmission of the SCGFailureInformationNR message to provide random access problem indication from SCG MAC: 2> if the random access procedure was initiated for beam failure recovery: 3> set the failureType as randomAccessProblem and set the failureType-v1610 as beamFailureRecoveryFailure; 2> else: 3> set the failureType as randomAccessProblem; 1> else if the UE initiates transmission of the SCGFailureInformationNR message to provide indication from SCG RLC that the maximum number of retransmissions has been reached: 2> set the failureType as rlc-MaxNumRetx; 1> else if the UE initiates transmission of the SCGFailureInformationNR message due to SRB3 integrity check failure: 2> set the failureType as srb3-IntegrityFailure; 1> else if the UE initiates transmission of the SCGFailureInformationNR message due to Reconfiguration failure of NR RRC reconfiguration message: 2> set the failureType as scg-reconfigFailure; 1> else if the UE initiates transmission of the SCGFailureInformationNR message due to consistent uplink LBT failures: 2> set the failureType as any value and set the failureType-v1610 as scg-lbtFailure; 1> else if connected as an IAB-node and the SCGFailureInformationNR is initiated due to the reception of a BH RLF indication on BAP entity from the SCG: 2> set the failureType as any value and set failureType-v1610 as bh-RLF. 1> else if the UE initiates transmission of the SCGFailureInformationNR message due to beam failure of the PSCell while the SCG is deactivated: 2> set the failureType as any value and set failureType-v1610 as beamFailure. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.7.3.3 |
4,883 | 5.5.1.2.2a S1-based DAPS handover, normal | This procedure describes the S1-based DAPS handover in the normal case. Figure 5.5.1.2.2a-1: S1-based DAPS handover 1. Step 1 to step 9b are performed as described in clause 5.5.1.2.2 with the following changes: The Source to Target Transparent Container which is included in Handover Required message in step 2 in clause 5.5.1.2.2 will contain the DAPS Information if DAPS HO is supported by source eNodeB and source MME and DAPS HO is requested for one or more DRBs as described in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [5]. If DAPS HO is supported by the target eNodeB and target MME and the DAPS Information is received for one or more DRBs in the Source to Target transparent container, the target eNodeB provides the DAPS Response Information in the Target to Source transparent container in Handover Request Acknowledge message in step 5a in clause 5.5.1.2.2. 2. The source eNodeB sends the eNodeB Early Status Transfer message to the target eNodeB via the MME(s) to convey the PDCP and HFN status of the E-RABs for which PDCP status preservation applies, as specified in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [5]. For the DRBs not subject to DAPS, step 10 to step 10c in clause 5.5.1.2.2 may be performed. If there is an MME relocation the source MME sends this information to the target MME via the Forward Access Context Notification message which the target MME acknowledges. The source MME or, if the MME is relocated, the target MME, sends the information to the target eNodeB via the MME Early Status Transfer message. 3. This step is the same as step 11 in clause 5.5.1.2.2. 4. This step is the same as step 12 in clause 5.5.1.2.2. 5. This step is the same as step 13 in clause 5.5.1.2.2 with the difference that the Notify Source eNodeB IE is included in the Handover Notify message. 6. This step is the same as step 14 in clause 5.5.1.2.2 with following changes: If there is an MME relocation and the target MME receives this Notify Source eNodeB information from the target eNodeB, the target MME provides the Notify Source eNodeB information via the Forward Relocation Complete Notification message. 7. If the Notify Source eNodeB IE is provided in either step 5 or step 6, the source MME sends the Handover Success message to source eNodeB to inform the source eNodeB that the UE has successfully accessed the target eNodeB. 8. The Source eNodeB initiates the eNodeB Status Transfer message for the DRB(s) subject to DAPS. This step is the same as step 10 in clause 5.5.1.2.2. 9. Steps 15 to 21b in clause 5.5.1.2.2 are performed. | 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.5.1.2.2a |
4,884 | 6.8B.1 MPDCCH formats | The MPDCCH formats are defined as in Clause 6.8A.1 with the following exceptions: - The term EPDCCH is replaced by MPDCCH. - The MTC physical downlink control channel carries downlink control information and is transmitted across consecutive BL/CE DL subframes. Within each of the BL/CE DL subframes an MPDCCH is transmitted using an aggregation of one or several consecutive enhanced control channel elements (ECCEs) where each ECCE consists of multiple enhanced resource element groups (EREGs), defined in clause 6.2.4A. - For frame structure type 2, - If repetition is not configured for the MPDCCH, the number of EREGs per ECCE is given by Table 6.8A.1-1. If repetition is configured for the MPDCCH, the number of EREGs per ECCE is given by Table 6.8B.1-1. - For those special subframes where the MPDCCH is not supported, these special subframes are considered BL/CE DL subframes for both MPDCCH and PDSCH transmission, only if they are indicated as BL/CE DL subframe by higher layer signalling. - For an MPDCCH associated with 2 or 4 PRBs, if repetition is not configured for the MPDCCH, the supported MPDCCH formats are given by Table 6.8A.1-2. Otherwise, the supported MPDCCH formats are given by Table 6.8B.1-2. However, for MPDCCH format 5, the equation defining the relation between ECCE index and EREG index does not apply and the number of ECCEs refers to the MPDCCH mapping to the REs of the 2+4 PRB set as defined in Clause 6.8B.5. Table 6.8B.1-1: Number of EREGs per ECCE, , for frame structure type 2. Table 6.8B.1-2: Supported MPDCCH formats | 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 | 6.8B.1 |
4,885 | 5.5.3.2.1 Mapping to physical resources for basic SRS | The sequence shall be multiplied with the amplitude scaling factor in order to conform to the transmit power specified in clause 5.1.3.1 in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [4], and mapped in sequence starting with to resource elements on antenna port according to where is the number of antenna ports used for sounding reference signal transmission and the relation between the index and the antenna port is given by Table 5.2.1-1. The set of antenna ports used for sounding reference signal transmission is configured independently for periodic and each configuration of aperiodic sounding. The quantity is the frequency-domain starting position of the sounding reference signal and for and is the length of the sounding reference signal sequence defined as where is given by Table 5.5.3.2-1 through Table 5.5.3.2-4 for each uplink bandwidth . The cell-specific parameter srs-BandwidthConfig, and the UE-specific parameter srs-Bandwidth, are given by higher layers. For UpPTS, shall be reconfigured to if this reconfiguration is enabled by the cell-specific parameter srsMaxUpPts given by higher layers, otherwise if the reconfiguration is disabled ,where is a SRS BW configuration and is the set of SRS BW configurations from the Tables 5.5.3.2-1 to 5.5.3.2-4 for each uplink bandwidth , is the number of format 4 PRACH in the addressed UpPTS and derived from Table 5.7.1-4. The frequency-domain starting position is defined by where for normal uplink subframes is defined by and for UpPTS by The quantity is given by where the relation between the index and the antenna port is given by Table 5.2.1-1, is given by the UE-specific parameter transmissionComb or transmissionComb-ap for periodic and each configuration of aperiodic transmission, respectively, provided by higher layers for the UE, and is frequency position index. The variable is equal to 0 for UpPTS in the first half frame and equal to 1 for UpPTS in the second half frame of a radio frame. The frequency hopping of the sounding reference signal is configured by the parameter , provided by higher-layer parameter srs-HoppingBandwidth. Frequency hopping is not supported for aperiodic transmission, except for additional SRS. If frequency hopping of the sounding reference signal is not enabled (i.e., ), the frequency position index remains constant (unless re-configured) and is defined by where the parameter is given by higher-layer parameters freqDomainPosition and freqDomainPosition-ap for periodic and each configuration of aperiodic transmission, respectively. If frequency hopping of the sounding reference signal is enabled (i.e., ), the frequency position indexes are defined by where is given by Table 5.5.3.2-1 through Table 5.5.3.2-4 for each uplink bandwidth , where regardless of the value on Table .2-1 through Table 5.5.3.2-4, and counts the number of UE-specific SRS transmissions, where is UE-specific periodicity of SRS transmission defined in clause 8.2 of TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [4], is SRS subframe offset defined in Table 8.2-2 of TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [4] and is the maximum value of for a certain configuration of SRS subframe offset. The sounding reference signal shall be transmitted in the last symbol of the uplink subframe. Table 5.5.3.2-1: and , , values for the uplink bandwidth of Table 5.5.3.2-2: and , , values for the uplink bandwidth of Table 5.5.3.2-3: and , , values for the uplink bandwidth of Table 5.5.3.2-4: and, , values for the uplink bandwidth of | 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.5.3.2.1 |
4,886 | 10.2.1.3 UE in RM-REGISTERED state requests a PDU Session for IMS Emergency services | The UE initiates the UE requested PDU session establishment procedure to receive emergency services as specified in clause 5.16.4 in TS 23.501[ System architecture for the 5G System (5GS) ] [2]. Since the UE already has a current 5G security context when it attempts to set up an IMS Emergency Session, the UE shall use this 5G security context to protect NAS, RRC and UP traffic. If the AMF successfully validates the PDU Session request for emergency bearer services using the current 5G security context, the AMF may accept this request and setup a PDU session. If the AMF attempts to re-authenticate the UE after receiving a correctly integrity protected request for emergency bearer services based on the current NAS security context and the authentication failed and if the serving network policy does not allow unauthenticated IMS Emergency Sessions, the UE and AMF shall proceed as for the initial registration error scenario as described in clause 6.1.3. If the AMF attempts to re-authenticate the UE after receiving a correctly integrity protected request for emergency bearer services based on the current NAS security context and the authentication failed and the serving network policy allows unauthenticated IMS Emergency Sessions, then the set up of the emergency bearers shall proceed in one of the two ways: a) The set-up proceeds according to clause 10.2.2. In this case, there is no need for the UE to re-attach, and the AMF requests the use of the NULL ciphering and integrity algorithms in the same way as described in clause 10.2.2.2 for the case of Emergency registration by UEs in limited service state. NOTE 1: If the authentication failure is detected in the AMF then the UE is not aware of the failure in the AMF, but still needs to be prepared, according to the conditions specified in TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] , to accept a NAS SMC from the AMF requesting the use of the NULL ciphering and integrity algorithms. NOTE 2: Regardless of if the authentication failed in the UE or in the AMF, the AMF can assume that the UE will accept that NULL integrity and ciphering algorithms are selected in the security mode control procedure b) The UE and the AMF continues using the current security context as described below for the case when primary authentication is executed while setting up a PDU session for emergency services. If primary authentication procedure is executed while setting up a PDU Session for emergency bearer services, the AMF and UE shall behave as follows: UE behavior: - Upon successful authentication verification in the UE, the UE shall continue using the current security context. - Alternatively, upon authentication verification failure in the UE, the UE shall send a failure message to the AMF and shall continue using the current security context. If the UE receives a NAS security mode command selecting NULL integrity and ciphering algorithms, the UE shall accept this as long as the IMS Emergency session progresses. AMF behavior: - If the serving network policy allows unauthenticated IMS Emergency Sessions, the AMF, after the unsuccessful authentication verification of the UE, should not send a reject an Authentication Reject message and continue using the current security context with the UE. - After receiving both, the EC Indication and the failure message from the UE, the AMF shall continue using the current security context with the UE for establishing an emergency bearer. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 10.2.1.3 |
4,887 | 9.5.4.2 TDD | For the parameters specified in Table 9.5.4.2-1, the minimum performance requirement in Table 9.5.4.2-2 is defined as a) The ratio of the throughput obtained when transmitting based on UE reported RI and that obtained when transmitting with fixed rank 1 shall be 1; b) The ratio of the throughput obtained when transmitting based on UE reported RI and that obtained when transmitting with fixed rank 2 shall be β₯ ο§ο²; In Table 9.5.4.2-1, Cell 1 is the serving cell, and Cell 2 and Cell 3 are the aggresso cells. The downlink physical channel setup for Cell 1 is according to Annex C.3.2 and for Cell 2 and Cell 3 is according to Annex C.3.3, respectively. The CRS assistance information [7] including Cell 2 and Cell 3 is provided. Table 9.5.4.2-1: RI Test (TDD) Table 9.5.4.2-2: Minimum requirement (TDD) | 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 | 9.5.4.2 |
4,888 | 4.3.5.7 Mobility Restrictions | Mobility Restrictions comprises the functions for restrictions to mobility handling of a UE in E-UTRAN access. The Mobility Restriction functionality is provided by the UE, the radio access network and the core network. Mobility Restriction functionality in state ECM-IDLE is executed in UE based on information received from the core network. Mobility Restriction functionality in state ECM-CONNECTED is executed in the radio network and the core network. In state ECM-CONNECTED, the core network provides the radio network with a Handover Restriction List. The Handover Restriction List specifies roaming, area and access restrictions. If roaming restriction to GERAN or UTRAN access needs to be enforced, a MME that is connected to eNodeBs that may handover or invoke release with redirection to UTRAN or GERAN is configured with a list of HPLMN IDs that are permitted to access GERAN or UTRAN unless restricted by the UE individual access restriction information received from HSS. | 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") | 4.3.5.7 |
4,889 | 5.7.6 Handling of Wild Card APN | When the wild card APN is present in the subscription context, the UE is authorized to connect to APNs which are not present in the subscription context. When a request is received for registering a PDN GW ID and there is no PDN subscription context with this APN, the nodes (HSS/MME/ S4 SGSN) shall store the PDN GW ID - APN relation for the UE. When a request is received for deregistering of PDN GW ID and there is no PDN subscription context with this APN, the nodes (HSS/MME/S4 SGSN) shall delete the PDN GW ID - APN relation from the list of APN - PDN GW ID relations. | 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.7.6 |
4,890 | 13.4.3.2 RAN Overload Handling | In NR-DC, when RAN overload happens in the node which receives the QoE reports from the UE, the node may coordinate with its peer node to reconfigure the QoE reporting path, by sending the QoE Reporting Path Request in the QMC Coordination Request IE, via the SN modification procedure. When neither the MN nor the SN is able to receive the QoE reports due to RAN overload, the network can indicate to the UE to pause QoE reporting, as specified in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [3]. | 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.2 |
4,891 | 4.7.4.1.3 MS initiated combined GPRS detach procedure completion | When the DETACH REQUEST message is received by the network, a DETACH ACCEPT message shall be sent to the MS, if the detach type IE value indicates that the detach request has not been sent due to switching off. Depending on the value of the detach type IE the following applies: GPRS/IMSI detach: The MS is marked as inactive in the network for GPRS and for non-GPRS services. The network and the MS shall deactivate the PDP contexts, the MBMS contexts and deactivate the logical link(s), if any. The States GMM-DEREGISTERED and MM NULL are entered in both the MS and the network. In Iu mode, if the detach has been sent due to switching off, then the network shall release the resources in the lower layers for this MS (see 3GPP TS 25.331[ None ] [23c]). IMSI detach: The MS is marked as inactive in the network for non-GPRS services. State MM NULL is entered in the MS and the network. | 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.7.4.1.3 |
4,892 | 28.3.2.3.3 NRF URI | In absence of any other local configuration available in the vNRF, the API URIs of the hNRF shall be constructed by deriving the API root (see 3GPP TS 29.501[ 5G System; Principles and Guidelines for Services Definition; Stage 3 ] [128]) as follows: - the authority part shall be set to the NRF FQDN as specified in 28.3.2.3.2 - the scheme shall be "https" - the port shall be the default port for the "https" scheme, i.e. 443. - the API prefix optional component shall not be used EXAMPLE: For an MCC = 012 and MNC = 345, the API root of the NRF services shall be: "https://nrf.5gc.mnc345.mcc012.3gppnetwork.org/" | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 28.3.2.3.3 |
4,893 | 10.5.3.8 Time Zone | The purpose of this information element is to encode the offset between universal time and local timein steps of 15 minutes. The Time Zone information element is coded as shown in figure 10.5.83/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.96/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The Time Zone is a type 3 information element with a length of 2 octets. Figure 10.5.83/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Time Zone information element Table 10.5.96/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Time Zone 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.3.8 |
4,894 | 4.2.3.3 Network Triggered Service Request | This procedure is used when the network needs to signal (e.g. N1 signalling to UE, Mobile-terminated SMS, User Plane connection activation for PDU Session(s) to deliver mobile terminating user data) with a UE. When the procedure is triggered by SMSF, PCF, LMF, GMLC, NEF, AMF or UDM, the SMF (and UPF, if applicable) in the following figure should be replaced by the respective NF. For MT-SMS delivery request from SMSF, see also procedures defined in clause 4.13.3.6, clause 4.13.3.7 and clause 4.13.3.8. If the UE is in CM-IDLE state or CM-CONNECTED state in 3GPP access, the network initiates a Network Triggered Service Request procedure. If the UE is in CM-IDLE state and asynchronous type communication is not activated, the network sends a Paging Request to (R)AN/UE. The Paging Request triggers the UE Triggered Service Request procedure in the UE. If asynchronous type communication is activated, the network stores the received message and forward the message to the (R)AN and/or the UE (i.e. synchronizes the context with the (R)AN and/or the UE) when the UE enters CM-CONNECTED state. If the UE is in CM-IDLE state in non-3GPP access and if the UE is simultaneously registered over 3GPP and non-3GPP accesses in a PLMN, the network shall initiate a Network Triggered Service Request procedure over 3GPP access. If the UE is in CM-IDLE state in 3GPP access and in CM-CONNECTED state in non-3GPP access and if the UE is simultaneously registered over 3GPP and non-3GPP accesses in the same PLMN, the network may initiate a Network Triggered Service Request procedure for 3GPP access via non-3GPP access. For this procedure, the impacted SMF and UPF are all under control of the PLMN serving the UE, e.g. in Home Routed roaming case the SMF and UPF in HPLMN are not involved. The procedure below covers the following non exhaustive list of use-cases for 3GPP access (detailed conditions of when the steps apply are stated in the procedure below): - The SMF needs to setup N3 tunnel to deliver downlink packet to the UE for a PDU Session and the UE is in CM-IDLE state: Step 3a contains an N2 message and Step 4b (paging) is performed. - The SMF needs to setup N3 tunnel to deliver downlink packet to the UE for a PDU Session and the UE is in CM-CONNECTED state: Step 3a contains an N2 message and Step 4a (UP reactivation) is performed. - NF (e.g. SMF, SMSF, PCF or LMF) needs to send an N1 message to the UE, using the Namf_Communication_N1N2MessageTransfer service operation and the UE is in CM-IDLE state: Step 3a contains an N1 message, Step 3b contains cause "Attempting to reach UE" and Step 4b (paging) occurs. - The LMF triggers AMF, using the Namf_Communication_N1N2MessageTransfer service operation, to setup a NAS connection with the UE and the UE is in CM-IDLE state: Step 3b contains cause "Attempting to reach UE" and step 4b (paging) occurs. - The GMLC triggers AMF, using the Namf_Location_ProvideLocation service operation, to setup a NAS connection with the UE and the UE is in CM-IDLE state: Step 4b (paging) occurs. - The PCF needs to send a message to the UE, using the Npcf_AMPolicyControl_Create Response service operation, or the Npcf_AMPolicyControl_UpdateNotify service operation and the UE is in CM-IDLE state: Step 3a contains a message and step 4b (paging) occurs. - NF (e.g. SMSF or SMF) triggers AMF, using the Namf_MT_EnableUEReachability service operation, to setup a NAS connection with the UE and the UE is in CM-IDLE state: The trigger is specific to the procedure and Step 4b (paging) occurs. As described in clause 4.2.4.2, the AMF may also trigger the Network Triggered Service Request before the AMF sends a UE Configuration Update. Figure 4.2.3.3-1: Network Triggered Service Request 1. When a UPF receives downlink data for a PDU Session and there is no AN Tunnel Info stored in UPF for the PDU Session, based on the instruction from the SMF (as described in clause 5.8.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]), the UPF may buffer the downlink data (steps 2a and 2b), or forward the downlink data to the SMF (step 2c). 2a. UPF to SMF: Data Notification (N4 Session ID, Information to identify the QoS Flow for the DL data packet, DSCP). - On arrival of the first downlink data packet for any QoS Flow, the UPF shall send Data Notification message to the SMF, if the SMF has not previously notified the UPF to not send the Data Notification to the SMF (in which case the next steps are skipped). - If the UPF receives downlink data packets for another QoS Flow in the same PDU Session, the UPF shall send another Data Notification message to the SMF. - If the Paging Policy Differentiation feature (as specified in clause 5.4.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]) is supported by the UPF and if the PDU Session type is IP, the UPF shall also include the DSCP in TOS (IPv4) / TC (IPv6) value from the IP header of the downlink data packet and the information to identify the QoS Flow for the DL data packet. 2b. SMF to UPF: Data Notification Ack. 2c. The UPF forwards the downlink data packets towards the SMF if the SMF instructed the UPF to do so (i.e. the SMF will buffer the data packets). - If the Paging Policy Differentiation feature is supported by the SMF and if the PDU Session type is IP, the SMF determines the Paging Policy Indicator based on the DSCP in TOS (IPv4) / TC (IPv6) value from the IP header of the received downlink data packet and identifies the corresponding QoS Flow from the QFI of the received DL data packet. 3a. [Conditional] SMF to AMF: Namf_Communication_N1N2MessageTransfer (SUPI, PDU Session ID, N1 SM container (SM message), N2 SM information (QFI(s), QoS profile(s), CN N3 Tunnel Info, S-NSSAI), Area of validity for N2 SM information, ARP, Paging Policy Indicator, 5QI, N1N2TransferFailure Notification Target Address, Extended Buffering support), or NF to AMF: Namf_Communication_N1N2MessageTransfer (SUPI, N1 message). The SMF shall not include both N1 SM Container and N2 SM Information in Namf_Communication_N1N2MessageTransfer unless the N1 SM Container is related to the N2 SM Information. If this step is triggered by a notification from UPF, upon reception of a Data Notification message, for a PDU Session corresponding to a LADN, the SMF takes actions as specified in clause 5.6.5 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The SMF may notify the UPF that originated the Data Notification to discard downlink data for the PDU Sessions and/or to not provide further Data Notification messages. Otherwise, the SMF determines whether to contact the AMF. The SMF does not contact the AMF: - if the SMF had previously been notified that the UE is unreachable; or - if the UE is reachable only for regulatory prioritized service and the PDU Session is not for regulatory prioritized service. The SMF determines the AMF and invokes the Namf_Communication_N1N2MessageTransfer to the AMF including the PDU Session ID of the PDU Session. If this step is triggered by a notification from the UPF in step 2a, the SMF determines the PDU Session ID based on the N4 Session ID received in step 2a. The SMF determines whether Extended Buffering applies based on local policy and the capability of the SMF (for SMF-based buffering) or the capability of the UPF (for UPF-based buffering). If Extended Buffering applies, the SMF includes "Extended Buffering support" indication in Namf_Communication_N1N2MessageTransfer. If the SMF, while waiting for the User Plane Connection to be activated, receives any additional Data Notification message or, in the case that the SMF buffers the data packets, additional data packets for a QoS Flow associated with a higher priority (i.e. ARP priority level) than the priority indicated to the AMF in the previous Namf_Communication_N1N2MessageTransfer, or the SMF derive a different Paging Policy Indicator according to the additional Data Notification or the DSCP of the data packet, the SMF invokes a new Namf_Communication_N1N2MessageTransfer indicating the higher priority or different Paging Policy Indicator to the AMF. If the SMF, while waiting for the User Plane to be activated, receives a message from a new AMF other than the one to which the SMF invoked theNamf_Communication_N1N2MessageTransfer, the SMF re-invokes the Namf_Communication_N1N2MessageTransfer towards the new AMF. When supporting Paging Policy Differentiation, the SMF determines the Paging Policy Indicator related to the downlink data that has been received from the UPF or triggered the Data Notification message, based on the DSCP as described in clause 5.4.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] and indicates the Paging Policy Indicator in the Namf_Communication_N1N2MessageTransfer. NOTE 1: AMF may receive request message(s) from other network functions which leads to signalling towards UE/RAN, e.g. Network-initiated Deregistration, SMF initiated PDU Session Modification. If the UE is in CM-CONNECTED state and the AMF only delivers N1 message towards UE, the flow continues in step 6 below. The N2 SM information is optional and is not provided e.g. in the case that the SMF only wants to send an N1 message such as PDU Session Modification Command with only updating the UE with a PCO. For PDU session with user plane in Suspend mode (i.e. applying User Plane CIoT 5GS Optimisation as specified in clause 5.31.8 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]) for 3GPP access, the SMF uses Namf_MT_EnableUEReachability service operation if there is neither N1 SM container nor N2 SM information to be delivered by SMF. 3b. [conditional] The AMF responds to the SMF. If the UE is in CM-IDLE state at the AMF and the AMF is able to page the UE the AMF sends a Namf_Communication_N1N2MessageTransfer response to the SMF immediately to indicate to the SMF that AMF is attempting to reach UE and the N2 SM information provided in step 3a, may be ignored by the AMF once the UE is reachable and the SMF may be asked to provide the N2 SM information again. While waiting for the UE to respond to a previous paging request, if the AMF receives an Namf_Communication_N1N2MessageTransfer Request message with the same or a lower priority than the previous message triggering the paging, or if the AMF has determined not to trigger additional paging requests for this UE based on local policy, the AMF rejects the Namf_Communication_N1N2MessageTransfer Request message. If the UE is in CM-CONNECTED state at the AMF then the AMF sends a Namf_Communication_N1N2MessageTransfer response to the SMF immediately to indicate that the N1/N2 message has been sent out. If the UE is in CM-IDLE state and the AMF determines that the UE is not reachable for paging, the AMF shall send an Namf_Communication_N1N2MessageTransfer response to the NF from which AMF received the request message in step 3a to indicate that the UE is not reachable, or the AMF performs asynchronous type communication and stores the UE context based on the received message, it shall send an Namf_Communication_N1N2MessageTransfer response to indicate that asynchronous type communication is invoked. If asynchronous type communication is invoked, the AMF initiates communication with the UE and (R)AN when the UE is reachable e.g. when the UE enters CM-CONNECTED state. If the AMF detects that the UE context contains Paging Restriction Information, the AMF may block the paging for this UE, based on local policy and the stored Paging Restriction Information (see clause 5.38.1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]). If the AMF blocks paging, the AMF sends Namf_Communication_N1N2MessageTransfer response with an indication that its request has been rejected due to restricted paging to the NF from which AMF received the request message in step 3a. If the AMF has determined the UE is unreachable for the SMF (e.g. due to the UE in MICO mode, the UE using extended idle mode DRX or the UE is only registered over non-3GPP access and its state is CM-IDLE), then the AMF rejects the request from the SMF. The AMF may include in the reject message an indication that the SMF need not trigger the Namf_Communication_N1N2MessageTransfer Request to the AMF, if the SMF has not subscribed to the event of the UE reachability. If the SMF included the Extended Buffering Support indication, the AMF indicates the Estimated Maximum Wait time, in the reject message, for the SMF to determine the Extended Buffering time. If the UE is in MICO mode, the AMF determines the Estimated Maximum Wait time based on the next expected periodic registration by the UE or by implementation. If the UE is using extended idle mode DRX, the AMF determines the Estimated Maximum Wait time based on the start of the next Paging Time Window. The AMF stores an indication that the SMF has been informed that the UE is unreachable. If the AMF has determined the UE is reachable and the AMF detects the UE is in a Non-Allowed Area unless the request from the SMF is for regulatory prioritized service, the AMF rejects the request from the SMF and notifies the SMF that the UE is reachable only for regulatory prioritized service. The AMF stores an indication that the SMF has been informed that the UE is reachable only for regulatory prioritized service. If the AMF cannot determine whether the UE is in a Non-Allowed Area (e.g. due to UE's Registration Area containing both Allowed area and Non-Allowed Area), the procedure continues in step 4. If the Registration procedure with AMF change is in progress when the old AMF receives the Namf_Communication_N1N2MessageTransfer, the old AMF may reject the request with an indication that the Namf_Communication_N1N2MessageTransfer has been temporarily rejected. Upon reception of an Namf_Communication_N1N2MessageTransfer response with an indication that its request has been temporarily rejected, the SMF shall start a locally configured guard timer and wait for any message to come from an AMF. Upon reception of a message from an AMF, the SMF shall re-invoke the Namf_Communication_N1N2MessageTransfer (with N2 SM info and/or N1 SM info) to the AMF from which it received the message. Otherwise the SMF takes the step 3c at expiry of the guard timer. If the SMF decides that the control plane buffering applies, the SMF shall request UPF to start forwarding the downlink data PDU towards the SMF. 3c. [Conditional] SMF responds to the UPF SMF may notify the UPF about the User Plane setup failure. If the SMF receives an indication from the AMF that the UE is unreachable or reachable only for regulatory prioritized service and the SMF determines that Extended Buffering does not apply, the SMF may, based on network policies, either: - indicate to the UPF to stop sending Data Notifications; - indicate to the UPF to stop buffering DL data and discard the buffered data; - indicate to the UPF to stop sending Data Notifications and stop buffering DL data and discard the buffered data; or - refrains from sending further Namf_Communication_N1N2MessageTransfer message for DL data to the AMF while the UE is unreachable. Then the SMF subscribes to the AMF for UE reachability event notifications. Based on operator policies, the SMF applies the pause of charging procedure as specified in clause 4.4.4. If the SMF receives an indication from the AMF that the Namf_Communication_N1N2MessageTransfer message requested from an SMF has been temporarily rejected, the SMF may, based on network policies, indicate to the UPF to apply temporary buffering. If the SMF receives an "Estimated Maximum Wait time" from the AMF and Extended Buffering applies, the SMF may either: - If the DL data buffering in the SMF applies, store the DL Data for an Extended Buffering time. The SMF does not send any additional Namf_Communication_N1N2MessageTransfer message if subsequent downlink data packets are received. If the Extended Buffering timer expires, the SMF discards the buffered downlink data. - If the DL data buffering in the UPF applies, send a Failure indication with an indication to the UPF to buffer the DL data with an Extended Buffering time and optionally a DL Buffering Suggested Packet Count. The Suggested Number of Downlink Packets network configuration parameter (if available) may be used to derive the value for DL Buffering Suggested Packet Count. The SMF may also indicate to the UPF to stop sending Data Notifications. The Extended Buffering time is determined by the SMF and should be larger or equal to the Estimated Maximum Wait time received from the AMF. If the UPF receives an Extended Buffering indication from the SMF, the UPF initiates Extended Buffering of the downlink data and starts an Extended Buffering timer. If the Extended Buffering timer expires, the UPF discards the buffered downlink data. 4a. [Conditional] If the UE is in CM-CONNECTED state in the access associated with the PDU Session ID received from the SMF in step 3a, the steps 4 to 22 in UE Triggered Service Request procedure (see clause 4.2.3.2) are performed for this PDU Session (i.e. establish the radio resources and in the case that the User Plane is to be activated, to establish the N3 tunnel) without sending a Paging message to the (R)AN node and the UE. In step 12 of clause 4.2.3.2, the AMF does not send the NAS Service Accept message to the UE. The rest of this procedure is omitted. 4b. [Conditional] If the UE is in CM-IDLE state in 3GPP access and the PDU Session ID received from the SMF in step 3a has been associated with 3GPP access and based on local policy the AMF decides to notify the UE through 3GPP access even when UE is in CM-CONNECTED state for non-3GPP access, the AMF may send a Paging message to NG-RAN node(s) via 3GPP access. If the UE is simultaneously registered over 3GPP and non-3GPP accesses in the same PLMN, the UE is in CM-IDLE state in both 3GPP access and non-3GPP access and the PDU Session ID in step 3a is associated with non-3GPP access, the AMF sends a Paging message with associated access "non-3GPP" to NG-RAN node(s) via 3GPP access. If the UE is in RM-REGISTERED state and CM-IDLE and reachable in 3GPP access, the AMF sends a Paging message (NAS ID for paging, Registration Area list, Paging DRX length, Paging Priority, access associated to the PDU Session, Enhanced Coverage Restricted information, WUS Assistance Information) to (R)AN node(s) belonging to the Registration Area(s) in which the UE is registered, then the NG-RAN node pages the UE, including the access associated to the PDU Session in the paging message if received from the AMF, see TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [12]. If extended idle mode DRX was accepted by the AMF in the last registration procedure, the AMF includes extended idle mode DRX cycle length and Paging Time Window in the Paging message. The AMF shall ensure that the correct Paging DRX length is provided based on the accepted UE Specific DRX of the current RAT. NOTE 2: The usage of the Access associated with a PDU Session when paging an UE is defined in clause 5.6.8 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. NOTE 3: This step is performed also when the UE and the network support User Plane CIoT 5GS Optimisation and the previous RRC connection has been suspended. For PDU session in Suspend mode, the SMF uses the service operation as described in step 3a. Different paging strategies may be configured in the AMF for different combinations of DNN, Paging Policy Indicator (if supported), ARP and 5QI. For RRC_INACTIVE state, the paging strategies may be configured in the (R)AN for different combinations of Paging Policy Indicator, ARP and 5QI. Paging Priority is included only: - if the AMF receives an Namf_Communication_N1N2MessageTransfer message with an ARP value associated with priority services (e.g. MPS, MCS), as configured by the operator. - if the AMF receives an Nudm_SDM_Notification message for a change in priority subscription (e.g. MPS), with a priority value as configured by the operator. - One Paging Priority level can be used for multiple ARP values. The mapping of ARP values to Paging Priority level (or levels) is configured by operator policy in the AMF and in NG-RAN. The (R)AN may prioritise the paging of UEs according to the Paging Priority. If the AMF, while waiting for a UE response to the Paging Request message sent without Paging Priority, receives an Namf_Communication_N1N2MessageTransfer message, which indicates an ARP value associated with priority services (e.g. MPS, MCS), as configured by the operator, the AMF shall send another paging message with the suitable Paging Priority. For subsequent received Namf_Communication_N1N2MessageTransfer messages with the same or higher priority, the AMF may determine whether to send the Paging message with suitable Paging Priority based on local policy. If the AMF has assigned PEIPS Assistance Information, the AMF shall provide the information. The NG-RAN uses this information as described in TS 23.501[ System architecture for the 5G System (5GS) ] [2]. Paging strategies may include: - paging retransmission scheme (e.g. how frequently the paging is repeated or with what time interval); - determining whether to send the Paging message to the (R)AN nodes during certain AMF high load conditions; - whether to apply sub-area based paging (e.g. first page in the last known cell-id or TA and retransmission in all registered TAs). NOTE 4: Setting of Paging Priority in the Paging message is independent from any paging strategy. The AMF and the (R)AN may support further paging optimisations in order to reduce the signalling load and the network resources used to successfully page a UE by one or several of the following means: - by the AMF implementing specific paging strategies (e.g. the N2 Paging message is sent to the (R)AN nodes that served the UE last); - by the AMF considering Information On Recommended Cells And NG-RAN nodes provided by the (R)AN at transition to CM-IDLE state. The AMF takes the (R)AN nodes related part of this information into account to determine the (R)AN nodes to be paged and provides the information on recommended cells within the N2 Paging message to each of these (R)AN nodes; - by the (R)AN considering the Paging Attempt Count Information provided by the AMF at paging. If the UE Radio Capability for Paging Information is available in the AMF, the AMF adds the UE Radio Capability for Paging Information in the N2 Paging message to the (R)AN nodes. If the Information On Recommended Cells And (R)AN nodes For Paging is available in the AMF, the AMF shall take that information into account to determine the (R)AN nodes for paging and when paging a (R)AN node, the AMF may transparently convey the information on recommended cells to the (R)AN node. The AMF may include in the N2 Paging message(s) the paging attempt count information. The paging attempt count information shall be the same for all (R)AN nodes selected by the AMF for paging. If the AMF has Paging Assistance Data for CE capable UE stored in the UE Context in AMF and Enhanced Coverage is not restricted for the UE then the AMF shall include Paging Assistance Data for CE capable UE in the N2 paging message for all NG-RAN nodes selected by the AMF for paging. The AMF may include in the N2 Paging message(s) the WUS Assistance Information, if available. If the WUS Assistance Information is included by the N2 Paging message, the NG-eNB takes it into account when paging the UE (see TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [46]). The AMF may include in the N2 paging message the PLMN ID(s) of Serving PLMN and equivalent PLMN(s) supported by NG-RAN and corresponding CAG information per PLMN ID which including an Allowed CAG list and optionally an indication whether the UE is only allowed to access 5GS via CAG cells, if available. If the above information is included in N2 paging message, the NG-RAN node may take it into account when determining the cells where paging will be performed (see TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [10]). If the UE and NG-eNB support WUS, then: - if the NGAP Paging message contains the Assistance Data for Recommended Cells IE (see TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [10]), the NG-eNB shall only broadcast the UE's Wake Up Signal in the last used cell; - else (i.e. the Assistance Data for Recommended Cells IE is not included in the NGAP Paging message) the eNodeB should not broadcast the UE's Wake Up Signal. If the network supports the Paging Cause Indication for Voice Service feature and if the UE context in the AMF indicates that the UE supports the Paging Cause Indication for Voice Service feature, the AMF should provide the Voice Service Indication in the NGAP Paging message only when the AMF detects that the downlink data which triggers the Paging message is related to voice service, as specified in clause 5.38.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If the NG RAN supporting the Paging Cause Indication for Voice Service feature receives the Voice Service Indication, it provides the Voice Service Indication in the Paging message and sends the Paging message to the UE. 4c. [Conditional] If the UE is simultaneously registered over 3GPP and non-3GPP accesses in the same PLMN and the UE is in CM-CONNECTED state in 3GPP access and the PDU Session ID in step 3a is associated with non-3GPP access, the AMF sends a NAS Notification message containing the non-3GPP Access Type to the UE over 3GPP access and sets a Notification timer. Step 5 is omitted. If the UE is simultaneously registered over 3GPP and non-3GPP accesses in the same PLMN and the UE is in CM-CONNECTED state for non-3GPP access and in CM-IDLE for 3GPP access and if the PDU Session ID in step 3a is associated with 3GPP access and based on local policy the AMF decides to notify the UE through non-3GPP access, the AMF may send a NAS Notification message containing the 3GPP Access Type to the UE over non-3GPP access and sets a Notification timer. If the network supports the Paging Cause Indication for Voice Service feature and if the UE context in the AMF indicates that the UE supports the Paging Cause Indication for Voice Service feature and the AMF detects that the downlink data is related to voice service, as specified in clause 5.38.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], the AMF shall send Paging message over 3GPP access as specified in step 4b. NOTE 5: This step is performed also when the UE and the network support User Plane CIoT 5GS Optimisation in 3GPP access and the previous RRC connection has been suspended. 5. [Conditional] AMF to SMF: Namf_Communication_N1N2Transfer Failure Notification. The AMF supervises the paging procedure with a timer. If the AMF receives no response from the UE to the Paging Request message, the AMF may apply further paging according to any applicable paging strategy described in step 4b. The AMF notifies the SMF by sending Namf_Communications_N1N2MessageTransfer Failure Notification to the Notification Target Address provided by the SMF in step 3a if the UE does not respond to paging, unless the AMF is aware of an ongoing MM procedure that prevents the UE from responding, i.e. the AMF receives an N14 Context Request message indicating that the UE performs Registration procedure with another AMF. When a Namf_Communication_N1N2Transfer Failure Notification is received, SMF informs the UPF (if applicable). Procedure for pause of charging at SMF is specified in clause 4.4.4. 6. If the UE is in CM-IDLE state in 3GPP access, upon reception of paging request for a PDU Session associated to 3GPP access, the UE shall initiate the UE Triggered Service Request procedure (clause 4.2.3.2) or, if the UE is enabled to use User Plane CIoT 5GS Optimisation and there is suspended access stratum context stored in the UE, the UE initiates the Connection Resume in CM-IDLE with Suspend procedure (clause 4.8.2.3). To support the buffered data forwarding, the SMF instruct the UPF to establish a Data forwarding tunnel between the old UPF and the new UPF or to the PSA as described at steps 6a, 7a, 8a of clause 4.2.3.2. If the UE is in CM-IDLE state in 3GPP access and is using the Multi-USIM Paging Rejection feature (see clause 5.38 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]), upon reception of paging request and if the UE determines not to accept the paging, the UE attempts to send a Reject Paging Indication via the UE Triggered Service Request procedure (clause 4.2.3.2) unless it is unable to do so e.g. due to UE implementation constraints. If the UE is in CM-IDLE state in both non-3GPP and 3GPP accesses, upon reception of paging request for a PDU Session associated to non-3GPP access, the UE shall initiate the UE Triggered Service Request procedure (clause 4.2.3.2) which shall contain the List Of Allowed PDU Sessions that, according to UE policies and whether the S-NSSAIs of these PDU Sessions are within the Allowed NSSAI or Partially Allowed NSSAI, if the serving cell is in a TA where the S-NSSAIs are supported or in a serving cell where the S-NSSAIs are available (according to clause 5.15.18 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]) for 3GPP access, can be re-activated over the 3GPP access. If there is no PDU Session that can be re-activated over the 3GPP access, the UE includes an empty List Of Allowed PDU Sessions. If the AMF receives a Service Request message from the UE via non-3GPP access as described in clause 4.12.4.1 (e.g. because the UE successfully connects to a non-3GPP access), the AMF stops the paging procedure and processes the received Service Request procedure. If the AMF receives the Service Request message and the List Of Allowed PDU Sessions provided by the UE does not include the PDU Session for which the UE was paged, the AMF notifies the SMF that the UE was reachable but did not accept to re-activate the PDU Session by invoking Namf_EventExposure_Notify service as described in step 4 of clause 4.2.3.2. If the UE is in CM-IDLE state in non-3GPP access and in CM-CONNECTED state in 3GPP access, upon reception of NAS Notification message over 3GPP access containing the non-3GPP Access Type, the UE shall initiate the UE Triggered Service Request procedure (clause 4.2.3.2) with the List Of Allowed PDU Sessions that, according to UE policies and whether the S-NSSAIs of these PDU Sessions are within the Allowed NSSAI or Partially Allowed NSSAI, if the serving cell is in a TA where the S-NSSAIs are supported or in a serving cell where the S-NSSAIs are available (according to clause 5.15.18 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]) for 3GPP access, can be re-activated over the 3GPP access. If there is no PDU Session that can be re-activated over the 3GPP access, the UE include an empty List Of Allowed PDU Sessions. When the AMF receives the Service Request message and the List of Allowed PDU Sessions provided by the UE does not include the PDU Session for which the UE was notified, the AMF notifies the SMF that the UE was reachable but did not accept to re-activate the PDU Session by invoking Namf_EventExposure_Notify service. If the AMF receives a Service Request message from the UE via non-3GPP access as described in clause 4.12.4.1 (e.g. because the UE successfully connects to a non-3GPP access), the AMF stops the Notification timer and processes the received Service Request procedure. - Alternatively, if the UE is in CM-IDLE state in non-3GPP access with the Mobility Management back-off timer running, upon reception of Paging Message over 3GPP access containing the non-3GPP Access Type, the UE on stopping the back-off timer (for both accesses), shall initiate the UE Triggered Service Request procedure (clause 4.12.4.1) over non-3GPP access if non-3GPP access is available. When the AMF receives a Service Request message from the UE via non-3GPP access, the AMF stops the Paging timer and processes the received Service Request. NOTE 6: A scenario where the UE is CM-IDLE over non-3GPP access and yet non-3GPP access is available, is when the UE over the non-3GPP access is running the Mobility Management back-off timer and network has released the NAS signalling connection upon service reject. If the UE is in CM-IDLE state in 3GPP access and in CM-CONNECTED state in non-3GPP access, upon reception of NAS Notification message over non-3GPP access identifying the 3GPP access type, the UE shall initiate the UE triggered Service Request procedure (clause 4.2.3.2) over the 3GPP access when 3GPP access is available. The Multi-USIM UE may not be able to trigger Service Request procedure (clause 4.2.3.2) over the 3GPP access to response the NAS Notification, e.g. due to UE implementation constraints. If the AMF does not receive the Service Request message before Notification timer expires, the AMF may either page the UE through 3GPP access or notify the SMF that the UE was not able to re-activate the PDU Session. The User Plane of all PDU Sessions for URLLC shall be activated during the Service Request procedure if the UE initiates the Service Request from 3GPP access in CM-IDLE state as described in clause 4.2.3.2. 6a. After receiving the Reject Paging Indication, the AMF notifies the SMF using the Namf_Communication_N1N2MessageTransfer Failure Notification that the UE rejected the page and no user plane connection will be established. The UE remains reachable for future paging attempts. If the AMF detects the UE is in a Non-Allowed Area unless the request from the SMF is for regulatory prioritized service, the AMF rejects the request from the SMF and notifies the SMF that the UE is reachable only for regulatory prioritized service. The AMF stores an indication that the SMF has been informed that the UE is reachable only for regulatory prioritized service. 7. If the AMF has paged the UE to trigger the Service Request Procedure, the AMF shall initiate the UE configuration update procedure as defined in clause 4.2.4.2 to assign a new 5G-GUTI. If the UE response in the Service Request includes a Reject Paging Indication, the AMF triggers the release of the UE as specified in clause 4.2.3.2. 8. The UPF transmits the buffered downlink data toward UE via (R)AN node which performed the Service Request procedure. If data is buffered in the SMF, the SMF delivers buffered downlink data to the UPF. The network also sends downlink signalling to the UE if the procedure is triggered due to request from other NFs, as described in step 3a. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.2.3.3 |
4,895 | 7.7.5 Unexpected GTP Message | If a GTP entity receives an unexpected initial message (see clause 4.2 "Protocol stack"), for example a known message that is sent over an interface for which the message is not defined, or a message that is sent over an interface for which the message is defined, but the direction is incorrect, then the GTP entity shall silently discard the message and shall log an error. If a GTP entity receives an unexpected triggered message which is not a request message (see clause 4.2 "Protocol stack"), for example a message for which there is no corresponding outstanding request, it shall discard the message and may log an error. When a GTP entity receives an unexpected triggered message, which is a request message, triggered by a command message, i.e. the MSB of the sequence number is set "1", e.g. in Create/Update/Delete Bearer Request messages, the GTP entity may continue to handle the request, e.g. to accept the Delete Bearer Request message. NOTE: Whether to accept or reject such a message is implementation specific. | 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.7.5 |
4,896 | 6.5.1.5 Abnormal cases in the UE | The following abnormal cases can be identified: a) T3482 expired On the first expiry of the timer T3482: - if the PDN CONNECTIVITY REQUEST message was sent with request type set to "emergency" or "handover of emergency bearer services" in a stand-alone PDN connectivity procedure, then the UE shall: a) inform the upper layers of the failure to establish the emergency bearer; or NOTE: This can result in the upper layers requesting establishment of a CS emergency call (if not already attempted in the CS domain), or other implementation specific mechanisms, e.g. 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] can result in the emergency call being attempted to another IP-CAN. b) detach locally, if not detached already, attempt EPS attach for emergency bearer services. - otherwise, the UE shall resend the PDN CONNECTIVITY REQUEST and shall reset and restart timer T3482. This retransmission is repeated four times, i.e. on the fifth expiry of timer T3482, the UE shall abort the procedure, release the PTI allocated for this invocation and enter the state PROCEDURE TRANSACTION INACTIVE. b) T3447 is running The UE shall not send a PDN CONNECTIVITY REQUEST message when the UE is in EMM-CONNECTED mode after the UE attached without PDN connection, unless: - establishment of a PDN connection for emergency bearer services is requested; - the UE is a UE configured to use AC11 β 15 in the selected PLMN; or - a network initiated signalling message has been received. The PDN CONNECTIVITY REQUEST message can be sent, if still necessary, when timer T3447 expires. c) Collision of UE requested PDN connectivity procedure and NAS signalling connection release The UE may immediately retransmit the PDN CONNECTIVITY REQUEST message and stop, reset and restart timer T3482, if the following conditions apply: 1) the original UE requested PDN connectivity procedure was initiated over an existing NAS signalling connection; and 2) the previous transmission of the PDN CONNECTIVITY REQUEST message was not initiated due to timer T3482 expiry. | 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.5.1.5 |
4,897 | 4.2.2.3 Piggybacked Messages | A piggybacked initial message is carried as a concatenation after a triggered response message and they share a common IP header (see Figure 4.2.0-2). The IP Source Address for the IP packet containing both the triggered response message and the piggybacked initial message shall be the same as the IP Address used for the triggered response message. The IP Destination Address for the IP packet containing both the triggered response message and the piggybacked initial message shall be the same as the IP Address used for the triggered response message. | 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 | 4.2.2.3 |
4,898 | 10.18.2 PSCell change failure | One of the functions of self-optimization for PSCell change is to detect PSCell change failures that occur due to Too late PSCell change or Too early PSCell change, or Triggering PSCell change to wrong PSCell. These problems are defined as follows: - Too late PSCell change: an SCG failure occurs after the UE has stayed for a long period of time in the PSCell; a suitable different PSCell is found based on the measurements reported from the UE. - Too early PSCell change: an SCG failure occurs shortly after a successful PSCell change from a source PSCell to a target PSCell or a PSCell change failure occurs during the PSCell change procedure; source PSCell is still the suitable PSCell based on the measurements reported from the UE. - Triggering PSCell change to wrong PSCell: an SCG failure occurs shortly after a successful PSCell change from a source PSCell to a target PSCell or a PSCell change failure occurs during the PSCell change procedure; a suitable PSCell different with source PSCell or target PSCell is found based on the measurements reported from the UE. In the definition above, the "successful PSCell change" refers to the UE state, namely the successful completion of the RA procedure. MN performs initial analysis to identify the node that caused the failure. The MN may use the SCG Failure Information Report procedure to verify whether intra-SN PSCell change has been triggered in the last serving SN and stores the SCG Failure Information for the time needed to receive possible response from the last serving SN. If the failure is caused by a source SN, the MN forwards then the SCG Failure Information to the source SN. The node responsible for the last PSCell change (the source SN, the last serving SN or the MN) performs the final root cause analysis. | 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 | 10.18.2 |
4,899 | β PUCCH-SpatialRelationInfo | The IE PUCCH-SpatialRelationInfo is used to configure the spatial setting for PUCCH transmission and the parameters for PUCCH power control, see TS 38.213[ NR; Physical layer procedures for control ] , [13], clause 9.2.2. PUCCH-SpatialRelationInfo information element -- ASN1START -- TAG-PUCCH-SPATIALRELATIONINFO-START PUCCH-SpatialRelationInfo ::= SEQUENCE { pucch-SpatialRelationInfoId PUCCH-SpatialRelationInfoId, servingCellId ServCellIndex OPTIONAL, -- Need S referenceSignal CHOICE { ssb-Index SSB-Index, csi-RS-Index NZP-CSI-RS-ResourceId, srs PUCCH-SRS }, pucch-PathlossReferenceRS-Id PUCCH-PathlossReferenceRS-Id, p0-PUCCH-Id P0-PUCCH-Id, closedLoopIndex ENUMERATED { i0, i1 } } PUCCH-SpatialRelationInfoExt-r16 ::= SEQUENCE { pucch-SpatialRelationInfoId-v1610 PUCCH-SpatialRelationInfoId-v1610 OPTIONAL, -- Need S pucch-PathlossReferenceRS-Id-v1610 PUCCH-PathlossReferenceRS-Id-v1610 OPTIONAL, --Need R ... } PUCCH-SRS ::= SEQUENCE { resource SRS-ResourceId, uplinkBWP BWP-Id } -- TAG-PUCCH-SPATIALRELATIONINFO-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | β |
4,900 | 4.3.2.1.2 Successful outgoing inter-RAT handovers per handover cause | This measurement provides the number of successful outgoing inter-RAT handovers per cause target cell specific. CC. Receipt of a S1AP message UE CONTEXT RELEASE COMMAND sent from the MME/DeNB to the source eNB, indicating a successful IRAT handover (see TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [9]). Each UE CONTEXT RELEASE COMMAND message received is added to the relevant per handover cause measurement, the possible causes are included in TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [9]. The sum of all supported per cause measurements shall equal the total number of outgoing inter-RAT handover events. In case only a subset of per cause measurements is supported, a sum subcounter will be provided first. All IRAT handovers to the neighbouring cells in non-eUTRAN are measured. Each measurement is an integer value. The number of measurements is equal to the number of causes supported plus a possible sum value identified by the .sum suffix. HO.IartOutSucc.Cause where Cause indicating the cause for handover. EUtranCellFDD EUtranCellTDD GSMRelation UTRANRelation CDMA2000Relation 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.2.1.2 |
Subsets and Splits
No saved queries yet
Save your SQL queries to embed, download, and access them later. Queries will appear here once saved.