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
⌀ |
|---|---|---|---|---|---|---|---|
6,401 | 6.1.1.4.1 Serving network name | The serving network name is used in the derivation of the anchor key. It serves a dual purpose, namely: - It binds the anchor key to the serving network by including the serving network identifier (SN Id). - It makes sure that the anchor key is specific for authentication between a 5G core network and a UE by including a service code set to "5G". In 5G AKA, the serving network name has a similar purpose of binding the RES* and XRES* to the serving network. The serving network name is the concatenation of a service code and the SN Id with a separation character ":" such that the service code prepends the SN Id. NOTE: No parameter like 'access network type' is used for serving network name as it relates to a 5G core procedure that is access network agnostic. The SN Id identifies the serving PLMN and, except for standalone non-public networks, is defined as SNN-network-identifier in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [35]. NOTE 1: For standalone non-public networks, the definition of SN Id is given in Annex I.3. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.1.1.4.1 |
6,402 | 4.5.1.4 Abnormal cases | The behaviour upon abnormal events is described together with the relevant RR procedure or MM common procedure. In addition, the following abnormal events can be identified: a) Indication that a CS fallback to GERAN or UTRAN has failed If EMM indicates that the CS fallback to GERAN or UTRAN failed, the MM sublayer shall abort the paging response procedure. b) Paging message for an MS which is IMSI attached for GPRS and for non-GPRS services in order to obtain GPRS services and "SMS-only service" An MS that received the GPRS-SMS indicator set to "0" at the last combined GPRS attach or combined routing area updating procedure may ignore the paging for CS services. An MS that requested "SMS-only service" in the combined GPRS attach procedure or combined routing area updating procedure may ignore the paging for CS services. NOTE: A network that is compliant with the earlier versions of the protocol will implicitly indicate to the MS that the delivery of SMS via GPRS is always supported, i.e. as GPRS-SMS indicator set to "0", even if it does not provide this support to the MS. The MS can learn whether SMS over GPRS is provided by using the mechanism defined in 3GPP TS 24.011[ Point-to-Point (PP) Short Message Service (SMS) support on mobile radio interface ] [22], subclause 2.6. If the MS learns that SMS over GPRS is provided, the MS can ignore paging for CS services. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.5.1.4 |
6,403 | N.2.2.2 Security policy aspects | When dual connectivity is used for redundant transmission, both of the two PDU sessions are initially established via the MN. The SMF(s) shall provide a UP security policy for each of the two PDU sessions to the MN during the PDU session establishment procedure as described in clause 6.6.1. The UP security policy from the SMF(s) for the two PDU sessions used for redundant data transmission shall have the same setting for encryption and for integrity protection. The network (UDM and/or SMF) shall ensure that all the redundant PDU sessions based on the information sent by the UE as described in TS 23.501[ System architecture for the 5G System (5GS) ] [2] shall have same UP security policy setting. The MN shall be preconfigured or shall have access to the supported security capabilities in the available SN(s), (i.e. to whether UP integrity protection is supported in the SN or not). The MN shall take the received UP security policy into account when selecting the SN. MN shall ensure that the first and the redundant PDU sessions shall have the same UP security activation status. If the "Preferred" option of the UP security policy is not allowed to be used for URLLC service at the SMF or UDM, which means the SMF or UDM can guaranteethe UP security policy for the first and the redundant PDU sessions are the same and only contains "Not needed", or "Required", then the MN shall forward the UP security policy to the SN as described in clause 6.10. If the "Preferred" option of the UP security policy is allowed to be used for URLLC services, the following enhancements for the mechanism as described in clause 6.10 for Dual Connectivity shall be applied： - The MN shall make the decision on UP encryption protection and integrity protection according to the UP security policy for these two redundant data transmissions. The MN shall store the applied UP security activation status used for the DRB’s established for the first PDU session between the MN and the UE. Then, the MN shall provide the UP security activation status applied for the first PDU session to the SN, when offloading the DRB’s for the second PDU session to the SN. - The SN shall use the UP security activation status received from the MN to activate the UP security for the DRB’s established for the redundant PDU session between the SN and the UE. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | N.2.2.2 |
6,404 | – Uu-RelayRLC-ChannelConfig | The IE Uu-RelayRLC-ChannelConfig is used to configure an RLC entity, a corresponding logical channel in MAC for Uu Relay RLC channel between L2 U2N Relay UE and network, or between a N3C relay UE and network in case of MP. Uu-RelayRLC-ChannelConfig information element -- ASN1START -- TAG-UU-RELAYRLC-CHANNELCONFIG-START Uu-RelayRLC-ChannelConfig-r17::= SEQUENCE { uu-LogicalChannelIdentity-r17 LogicalChannelIdentity OPTIONAL, -- Cond RelayLCH-SetupOnly uu-RelayRLC-ChannelID-r17 Uu-RelayRLC-ChannelID-r17, reestablishRLC-r17 ENUMERATED {true} OPTIONAL, -- Need N rlc-Config-r17 RLC-Config OPTIONAL, -- Cond RelayLCH-Setup mac-LogicalChannelConfig-r17 LogicalChannelConfig OPTIONAL, -- Cond RelayLCH-Setup ... } -- TAG-UU-RELAYRLC-CHANNELCONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
6,405 | 7A.2.1 Authentication for trusted non-3GPP access | This clause specifies how a UE is authenticated to 5G network via a trusted non-3GPP access network. This is based on the specified procedure in TS 23.502[ Procedures for the 5G System (5GS) ] [8] clause 4.12a.2.2 "Registration procedure for trusted non-3GPP access". The authentication procedure is similar to the authentication procedure for Untrusted non-3GPP access defined in clause 7.2.1 with few differences, which are mentioned below: Figure 7A.2.1-1: Registration \ Authentication and PDU Session establishment for trusted non-3GPP access 0. The UE selects a PLMN and a TNAN for connecting to this PLMN by using the Trusted Non-3GPP Access Network selection procedure specified in TS 23.501[ System architecture for the 5G System (5GS) ] [2] clause 6.3.12. During this procedure, the UE discovers the PLMNs with which the TNAN supports trusted connectivity (e.g. "5G connectivity"). 1. A layer-2 connection is established between the UE and the TNAP. In case of IEEE 802.11 [80], this step corresponds to an 802.11 [80] Association. In case of PPP, this step corresponds to a PPP LCP negotiation. In other types of non-3GPP access (e.g. Ethernet), this step may not be required. 2-3. An EAP authentication procedure is initiated. EAP messages shall be encapsulated into layer-2 packets, e.g. into IEEE 802.3/802.1x packets, into IEEE 802.11/802.1x packets, into PPP packets, etc. The UE provides a NAI that triggers the TNAP to send a AAA request to a TNGF. Between the TNAP and TNGF the EAP packets are encapsulated into AAA messages. 4-10. An EAP-5G procedure is executed as specified in clause 7.2.1with the following modifications: - The EAP-5G packets shall not be encapsulated into IKEv2 packets. The UE shall also include a UE Id in the AN parameter, e.g. a 5G-GUTI if available from a prior registration to the same PLMN. - A KTNGF as specified in clause Annex A.9 (equivalent to KN3IWF) is created in the UE and in the AMF after the successful authentication. The KTNGF is transferred from the AMF to TNGF in step 10a (within the N2 Initial Context Setup Request). - The TNAP is a trusted entity. The TNGF shall generate the KTNAP as specified in Annex A.22 and transfers it from TNGF to TNAP in step 10b (within a AAA message). - After receiving the TNGF key from AMF in step 10a, the TNGF shall send to UE an EAP-Request/5G-Notification packet containing the "TNGF Contact Info", which includes the IP address of TNGF. After receiving an EAP-Response/5G-Notification packet from the UE, the TNGF shall send message 10d containing the EAP-Success packet. 11. The common TNAP key is used by the UE and TNAP to derive security keys according to the applied non-3GPP technology and to establish a security association to protect all subsequent traffic. In case of IEEE 802.11 [80], the KTNAP is the Pairwise Master Key (PMK) and a 4-way handshake is executed (see IEEE 802.11 [80]) which establishes a security context between the WLAN AP and the UE that is used to protect unicast and multicast traffic over the air. All messages between UE and TNAP are encrypted and integrity protected from this step onwards. NOTE 1: whether step 11 is performed out of the scope of this document. The current procedure assumes the encryption protection over Layer-2 between UE and TNAP is to be enabled. 12. The UE receives IP configuration from the TNAN, e.g. with DHCP. 13. The UE shall initiate an IKE_INIT exchange with the TNGF. The UE has received the IP address of TNGF during the EAP-5G signalling in step 9b, subsequently, the UE shall initiate an IKE_AUTH exchange and shall include the same UE Id (i.e. SUCI or 5G-GUTI) as in the UE Id provided in step 5. The common KTIPSe is used for mutual authentication. The key KTIPSec is derived as specified in Annex A.22.NULL encryption is negotiated as specified in RFC 2410 [81]. After step 13c, an IPsec SA is established between the UE and TNGF (i.e. a NWt connection) and it is used to transfer all subsequent NAS messages. This IPsec SA does not apply encryption but only apply integrity protection. 14. After the NWtp connection is successfully established, the TNGF responds to AMF with an N2 Initial Context Setup Response message. 14a. The AMF may determine whether the TNGF is appropriate for the slice selected as defined in clause 4.12.2.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [8]. If it is compatible with the selected TNGF, then proceed with steps 15 to step 19. Otherwise, the AMF shall proceed with step 20 to step 22, and step 15 to step 19 are skipped. Case a): 15. Finally, the NAS Registration Accept message is sent by the AMF and is forwarded to UE via the established NWt connection. 16-18. The UE initiates a PDU session establishment. This is carried out exactly as specified in TS 23.502[ Procedures for the 5G System (5GS) ] [8] clause 4.12a.5. The TNGF may establish one or more IPSec child SA’s per PDU session. 19. User plane data for the established PDU session is transported between the UE and TNGF inside the established IPSec child SA Case b:) 20. The AMF may trigger the UE policy update procedure and update the UE policy as defined in step 17 and step 18 in clause 4.12a.2.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [8]. 21. The AMF shall send a Registration Reject message via TNGF to the UE as defined in step 19 to step21 in clause 4.12a.2.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [8]. The Registration Reject message is ciphered and integrity protected, and a new 5G-GUTI is provided to the UE. 22. The UE shall decipher and verify the integrity of the Registration Reject message. If verification is successful, then the UE proceeds with step 21 in clause 4.12.2.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [8], and sends an integrity protected Registration request message to the AMF via a new selected TNGF.. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 7A.2.1 |
6,406 | 28.3.2.2 N3IWF FQDN 28.3.2.2.1 General | The N3IWF Fully Qualified Domain Name (N3IWF FQDN) shall be constructed using one of the following formats, as specified in clause 6.3.6 of 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [119]: - Operator Identifier based N3IWF FQDN; - Tracking Area Identity based N3IWF FQDN; - the N3IWF FQDN configured in the UE by the HPLMN. - SNPN Identifier based N3IWF FQDN. NOTE 1: If the N3IWF FQDN is configured in the UE by HPLMN, it can have a different format than those specified in the following clauses. The actual format is out of 3GPP scope. The Visited Country FQDN for N3IWF is used by a roaming UE to determine whether the visited country mandates the selection of an N3IWF in this country. The Visited Country FQDN for N3IWF shall be constructed as specified in clause 28.3.2.2.4. The Replacement field used in DNS-based Discovery of regulatory requirements shall be constructed as specified in clause 28.3.2.2.5.1. The Visited Country FQDN for SNPN N3IWF is used by a UE in the visited country to determine whether the visited country mandates the selection of an N3IWF in this country for the SNPN identified by the SNPN Identifier provided by the UE. The Visited Country FQDN for SNPN N3IWF shall be constructed as specified in clause 28.3.2.2.6. The Replacement field used in DNS-based Discovery of SNPN N3IWF for regulatory requirements shall be constructed as specified in clause 28.3.2.2.7.2. The Visited Country FQDN for N3IWF supporting Onboarding is used by a UE in the visited country to determine whether the visited country mandates the selection of an N3IWF in this country for onboarding services. The Visited Country FQDN with N3IWF supporting Onboarding shall be constructed as specified in clause 28.3.2.2.4.3. The Replacement field used in DNS-based Discovery of regulatory requirements shall be constructed as specified in clause 28.3.2.2.5.3. The Visited Country FQDN for SNPN N3IWF supporting Onboarding is used by a UE in the visited country to determine whether the visited country mandates the selection of an SNPN N3IWF in this country for onboarding services. The Visited Country FQDN with SNPN N3IWF supporting Onboarding shall be constructed as specified in clause 28.3.2.2.6.2. The Replacement field used in DNS-based Discovery of SNPN N3IWF for regulatory requirements shall be constructed as specified in clause 28.3.2.2.7.2 NOTE 2: The DNS can be configured to return no records for the visited country regardless of the SNPN ID provided by the UE. This addresses the scenario that the visited country in general does not mandate selection of a local N3IWF. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 28.3.2.2 |
6,407 | 5.2.5.7.2 Npcf_EventExposure_Subscribe service operation | Service operation name: Npcf_EventExposure_Subscribe. Description: The consumer NF uses this service operation to subscribe to or modify event reporting for a group of UE(s) or any UE accessing a combination of (DNN, S-NSSAI). NF Consumers: NEF. Inputs, Required: NF ID, Target of Event Reporting (Internal Group Identifier or indication that any UE accessing a combination of (DNN, S-NSSAI)is targeted, (set of) Event ID(s) defined in clause 5.2.5.7.1, Notification Target Address (+ Notification Correlation ID) and Event Reporting Information defined in Table 4.15.1-1. Inputs, Optional: Event Filter (s) associated with each Event ID, Expiry time. Outputs, Required: Operation execution result indication. When the subscription is accepted: Subscription Correlation ID, Expiry time (required if the subscription can be expired based on the operator's policy). Outputs, Optional: First corresponding event report is included, if corresponding information is available (see clause 4.15.1). The NF consumer subscribes to the event notification by invoking Npcf_EventExposure to the PCF. The PCF allocates a Subscription Correlation ID for the subscription and responds to the consumer NF with the Subscription Correlation ID. Event receiving NF ID identifies the NF that shall receive the event reporting. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.5.7.2 |
6,408 | 6.34.2 Requirements | The 5G system shall support the communication services for critical medical applications. The associated requirements are described: - in 3GPP TS 22.104[ Service requirements for cyber-physical control applications in vertical domains ] [21] for the requirements related to controlling both local or remote robotic diagnosis or surgery systems, - in 3GPP TS 22.263[ Service requirements for Video, Imaging and Audio for Professional Applications (VIAPA) ] [28] for the requirements related to high quality medical imaging and augmented reality systems located in hybrid operating rooms, in remote healthcare facilities or ambulances, - in 3GPP TS 22.261[ Service requirements for the 5G system ] clause 7.5 for the requirements on the support of tele-diagnosis or tele-monitoring systems, - in 3GPP TS 22.261[ Service requirements for the 5G system ] clauses 6.10, 8.2 and 8.9 for the requirements on the security of medical data that fulfil regulatory requirements. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.34.2 |
6,409 | .2 Modify Bearer Failure Indication | The Modify Bearer Failure Indication shall be sent on the S5/S8 interface by the PGW to the SGW and on the S11 interface by the SGW to the MME as part of failure of HSS Initiated Subscribed QoS Modification procedure, or when the SQCI flag or the PSCI flag is set to the Context Response message. It shall also be sent on the S5/S8 interface by the PGW to the SGW and on the S4 interface by the SGW to the SGSN as part of failure of HSS Initiated subscribed QoS modification, or when the SQCI flag or the PSCI flag is set to the Context Response message. It shall also be sent on the S2a/S2b interface by the PGW to the TWAN/ePDG as part of failure of HSS Initiated Subscribed QoS Modification procedure. Cause IE indicates that an EPS bearer has not been updated in the PGW. Possible Cause values are specified in Table 8.4-1. Message specific cause values are: - "Context not found" - "Service denied". Table .2-1: Information Elements in a Modify Bearer Failure Indication Table 7.2.14-2: Overload Control Information within Modify Bearer Failure Indication | 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 | .2 |
6,410 | 28.3.2.11 5G DDNMF FQDN | The UE may construct the 5G DDNMF FQDN to discover the 5G DDNMF as specified in 3GPP TS 23.304[ Proximity based Services (ProSe) in the 5G System (5GS) ] [143]. The 5G DDNMF FQDN shall be constructed as follows: "ddnmf.5gc.mnc<MNC>.mcc<MCC>.pub.3gppnetwork.org" where the <MCC> and <MNC> shall identify the PLMN where the 5G DDNMF is located. Both the "<MNC>" and "<MCC>" fields are 3 digits long. If there are only 2 significant digits in the MNC, one "0" digit shall be inserted at the left side to fill the 3 digits coding of MNC in the 5G DDNMF FQDN. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 28.3.2.11 |
6,411 | 4.8.1 UE not using satellite E-UTRAN access | In WB-S1 mode, a UE operating in category CE can operate in either CE mode A or CE mode B (see 3GPP TS 36.306[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio access capabilities ] [44]). If a UE that supports CE mode B and operates in WB-S1 mode not using satellite E-UTRAN access, the UE's usage setting is not set to "voice centric" (see 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [10]), and a) the use of enhanced coverage is not restricted for the UE; or b) CE mode B is not restricted for the UE (see 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [10]); the UE shall apply the value of the applicable NAS timer indicated in tables 10.2.1 and indicated in table 10.3.1 for WB-S1/CE mode. A UE that supports CE mode B and operates in WB-S1 mode not using satellite E-UTRAN access shall not apply the value of the applicable NAS timer indicated in table 10.2.1 and table 10.3.1 for WB-S1/CE mode before receiving an indication from the network that the use of enhanced coverage is not restricted as described in this clause. The NAS timer value obtained is used as described in the appropriate procedure clause of this specification. The NAS timer value shall be calculated at start of a NAS procedure, and shall not be re-calculated until the NAS procedure is completed, restarted or aborted. The support of CE mode B by a UE is indicated to the MME by lower layers and shall be stored by the MME. When an MME that supports WB-S1 mode performs NAS signalling with a UE not using satellite E-UTRAN access, which supports CE mode B and operates in WB-S1 mode and the MME determines that: a) the use of enhanced coverage is not restricted for the UE; or b) CE mode B is not restricted for the UE (see 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [10]); the MME shall calculate the value of the applicable NAS timer indicated in tables 10.2.2 and indicated in table 10.3.2 for WB-S1/CE mode. The NAS timer value obtained is used as described in the appropriate procedure clause of this specification. The NAS timer value shall be calculated at start of a NAS procedure and shall not be re-calculated until the NAS procedure is completed, restarted or aborted. | 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.8.1 |
6,412 | – SL-UE-SelectedConfig | IE SL-UE-SelectedConfig specifies sidelink communication configurations used for UE autonomous resource selection. SL-UE-SelectedConfig information element -- ASN1START -- TAG-SL-UE-SELECTEDCONFIG-START SL-UE-SelectedConfig-r16 ::= SEQUENCE { sl-PSSCH-TxConfigList-r16 SL-PSSCH-TxConfigList-r16 OPTIONAL, -- Need R sl-ProbResourceKeep-r16 ENUMERATED {v0, v0dot2, v0dot4, v0dot6, v0dot8} OPTIONAL, -- Need R sl-ReselectAfter-r16 ENUMERATED {n1, n2, n3, n4, n5, n6, n7, n8, n9} OPTIONAL, -- Need R sl-CBR-CommonTxConfigList-r16 SL-CBR-CommonTxConfigList-r16 OPTIONAL, -- Need R ul-PrioritizationThres-r16 INTEGER (1..16) OPTIONAL, -- Need R sl-PrioritizationThres-r16 INTEGER (1..8) OPTIONAL, -- Need R ... } -- TAG-SL-UE-SELECTEDCONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
6,413 | 6.6.1A Occupied bandwidth for CA | For inter-band carrier aggregation with one component carrier per operating band and the uplink active in two E-UTRA bands the occupied bandwidth is defined per component carrier. Occupied bandwidth is the bandwidth containing 99 % of the total integrated mean power of the transmitted spectrum on assigned channel bandwidth on the component carrier. The occupied bandwidth shall be less than the channel bandwidth specified in Table 6.6.1-1. For intra-band contiguous carrier aggregation the occupied bandwidth is a measure of the bandwidth containing 99 % of the total integrated power of the transmitted spectrum. The OBW shall be less than the aggregated channel bandwidth defined in subclause . For intra-band non-contiguous carrier aggregation sub-block occupied bandwidth is defined as the bandwidth containing 99 % of the total integrated mean power of the transmitted spectrum on the sub-block. In case the sub-block consist of one component carrier the occupied bandwidth of the sub-block shall be less than the channel bandwidth specified in Table 6.6.1-1. For combinations of intra-band and inter-band carrier aggregation with three uplink component carriers (up to two contiguously aggregated carriers per band), the occupied bandwidth is the bandwidth containing 99 % of the total integrated mean power of the transmitted spectrum on each E-UTRA band. The OBW shall be less than the channel bandwidth as specified in Table 6.6.1-1 for the E-UTRA band supporting one component carrier. The OBW shall be less than the aggregated channel bandwidth as specified in subclause 5.6A for the E-UTRA band supporting two contiguous component carriers. | 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.1A |
6,414 | 4.15.10 AF specific UE ID retrieval | This clause contains the detailed description and the procedures for the AF specific UE ID retrieval. The AF specific UE Identifier is represented by the External Identifier as defined in TS 23.003[ Numbering, addressing and identification ] [33]. NOTE 1: After retrieving AF specific UE ID, the AF can invoke NEF provided services (e.g. location monitoring). Figure 4.15.10-1: AF specific UE ID retrieval 1. AF requests to retrieve UE ID via the Nnef_UEId_Get service operation. The request message shall include UE address (IP address or MAC address) and AF Identifier, it may include, Port Number associated with the IP address, MTC Provider Information, Application Port ID, IP domain. The MTC Provider Information identifies the MTC Service Provider and/or MTC Application. If available, the AF may also provide the corresponding DNN and/or S-NSSAI. NOTE 2: The MTC Provider Information can be used by any type of Service Providers (MTC or non-MTC) or Corporate or External Parties for, e.g. to distinguish their different customers. NOTE 3: The combination of IP address and Port Number can be used by 5GC to derive the UE private IP address assigned by 5GC if the UE is behind a NAT, see steps 3-6 below. NOTE 4: The Application Port ID is as defined in Nnef_Trigger_Delivery. NOTE 5: The NEF can validate the provided MTC Provider Information and override it to a NEF selected MTC Provider Information based on configuration. How the NEF determines the MTC Provider Information, if not present, is left to implementation (e.g. based on the requesting AF). 2. The NEF authorizes the AF request. If the authorisation is not granted, the NEF replies to the AF with a Result value indicating authorisation failure; otherwise the NEF proceeds with the following steps. The NEF determines corresponding DNN and/or S-NSSAI information: this may have been provided by the AF or is determined by the NEF based on the requesting AF Identifier, MTC Provider Information. If the NEF has received a Port Number in step 1, based on configuration, the NEF may recognize the address received is an IP address which is different from the actual private UE IP address assigned by 5GC, i.e. the UE is behind a NAT in UPF. If so, the NEF performs steps 3 to 6. Otherwise, steps 3 to 6 are skipped. 3. The NEF uses the Nnrf_NFDiscovery service operation to obtain the address of the UPF implementing NAT functionality for the UE (public) IP address. The request includes the UE (public) IP address. The NEF may also include the DNN and S-NSSAI associated with the AF ID, as well as the IP domain. 4. The NRF responds with a Nnrf_NFDiscovery response message including the UPF address of the UPF implementing NAT functionality for the UE (public) IP address. 5. The NEF uses the Nupf_GetUEPrivateIPaddrAndIdentifiers_Get service operation to request UE's (private) IP address from the UPF. The request includes the UE (public) IP address and Port Number and optionally IP domain, DNN and S-NSSAI associated with the AF ID. 6. The UPF responds with the Nupf_GetUEPrivateIPaddrAndIdentifiers_Get response message including UE's IP address and optionally, the IP domain. If the UPF has applied a NAT functionality, the UE's IP address returned by the UPF is the private UE IP address. If IP domain of UE private IP address is returned from UPF, it always takes precedence regardless of whether the IP domain information also provided by AF when it invokes Nnef_UEId_Get service operation. If UPF has the SUPI or GPSI of the UE, the UPF may return SUPI or GPSI and in this case steps 7-8 are skipped. NOTE 6: The SUPI/GPSI is only available when the SMF provides it to the UPF for the purposes defined in TS 29.244[ Interface between the Control Plane and the User Plane nodes ] [69]. 7-8. The NEF uses the Nbsf_Management_Discovery service operation with UE address and IP domain and /or DNN and/or S-NSSAI to retrieve the session binding information of the UE. If no SUPI is received in the session binding information from the BSF, the NEF replies to the AF with a Result value indicating that the UE ID is not available. 9. The NEF interacts with UDM to retrieve the AF specific UE Identifier via the Nudm_SDM_Get service operation. The request message includes SUPI or GPSI and at least one of Application Port ID, MTC Provider Information or AF Identifier. 10. The UDM responds to the NEF with an AF specific UE Identifier represented as an External Identifier for the UE which is uniquely associated with the Application Port ID, MTC provider Information and/or AF Identifier. 11. The NEF further responds to the AF with the information (including the AF specific UE Identifier represented as an External Identifier) received from the UDM. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.15.10 |
6,415 | 4.9.3 Signalling procedures | NR RRC signalling is utilized to configure the NCR-MT to receive side control information from a gNB, which is used by the NCR-Fwd to determine whether and how to amplify-and-forward RF signals. If the side control configuration is removed, the NCR-Fwd ceases its amplifying-and-forwarding function. When the NCR-MT is in RRC_CONNECTED state, the NCR-Fwd may amplify-and-forward RF signals based on the side control information received from the gNB. The NCR-MT does not support RRM measurements in RRC_CONNECTED. When the NCR-MT transitions from RRC_CONNECTED state to RRC_INACTIVE state, the NCR-Fwd may continue to amplify-and-forward RF signals in accordance with the last side control information received from the gNB. When the NCR-MT is in RRC_INACTIVE state, the NCR-Fwd ceases to amplify-and-forward RF signals if no suitable cell is detected, or if the NCR-MT selects a different cell than the last serving cell on which side control configuration was received. When an NCR-MT in RRC_INACTIVE state determines degradation of the NCR-Fwd backhaul link beam, then the NCR-Fwd should cease amplifying-and-forwarding RF signals, and the NCR-MT should attempt to resume its RRC connection (with cause value mo-Signalling). The criteria to evaluate backhaul beam degradation are left to the NCR-node implementation. When the NCR-MT transitions from RRC_CONNECTED state to RRC_IDLE, the NCR-Fwd ceases any amplifying-and-forwarding of RF signals. How an NCR-MT transitions back from RRC_IDLE state to RRC_CONNECTED state is left to NCR-node or network implementation. An NCR-MT can detect RLF on the control link as specified in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] clause 5.3.10 [12]. When RLF is detected, the NCR-MT performs the RRC re-establishment procedure as specified in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [12]. During the RRC re-establishment procedure, the NCR-Fwd ceases to amplify-and-forward RF signals. After successfully performing the RRC re-establishment procedure, the NCR-MT waits for the new side control configuration for the NCR-Fwd to resume the amplifying-and-forwarding of RF signals. An NCR-MT can also perform Beam Failure Detection (BFD) and Beam Failure Recovery (BFR) as described in clause 9.2.8. Once the NCR-MT detects beam failure in the control link, the NCR-Fwd should cease amplifying-and-forwarding RF signals until BFR is completed. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 4.9.3 |
6,416 | 9.5.12 Modify PDP context accept (Network to MS direction) | This message is sent by the network to the MS to acknowledge the modification of an active PDP context. See table 9.5.12/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Message type: modify PDP context accept (NeTWORK to ms direction) Significance: global Direction: Network to MS Table 9.5.12/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : modify PDP context ACCEPT (NETWORK to MS direction) message content | 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.5.12 |
6,417 | 5.3.4.3.4 Network Slice based cell reselection and Random Access | When one or more S-NSSAI(s) are associated with NSAG(s), the UE may perform Network Slice based cell reselection and Random Access as described in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [27], TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [50], TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [28], TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [143] and TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [47]. When providing NSAG Information to the UE, the AMF shall also provide the NSAG priority information for the NSAGs provided in the NSAG Information. The AMF determines the NSAG priority information based on configured local policy of the serving PLMN or SNPN. NOTE 1: How the AMF assigns the NSAG priority information per UE is not specified but AMF can take into account information like e.g. UE MM capabilities, Subscribed S-NSSAIs and HPLMN. NOTE 2: The AMF can assign same priority value for NSAGs provided in the NSAG Information. If the UE has received NSAG Information from the AMF, the UE shall use the NSAG Information provided by the AMF for cell reselection and Random Access as described below. If the UE has not received any NSAG Information from the AMF, the UE shall not use Network Slice based cell reselection and Random Access at all. The UE NAS provides to the UE AS the NSAG Information as received from the AMF and the S-NSSAIs in the Allowed NSSAI and any Partially Allowed NSSAI as input to cell reselection, except when the UE intends to register with a new (including any S-NSSAIs rejected partially in the RA) set of S-NSSAIs with a Requested NSSAI different from the current Allowed NSSAI and any Partially Allowed NSSAI, in which case the UE NAS provides to the UE AS layer the NSAG Information as received from the AMF and the S-NSSAIs in the Requested NSSAI, and this may trigger a cell reselection, before sending the Registration Request including the new Requested NSSAI. For Network Slice based Random Access, different Random Access resources may be assigned to different NSAG(s). The UE determines Random Access configuration among NSAGs that are published in SIB for Random Access and that are associated to the S-NSSAIs triggering the access. If the signalling transaction triggering the access attempt is related to more than one network slice, and the S-NSSAIs of these network slices are associated with more than one NSAG for Random Access, the NSAG with the highest priority is selected. NOTE 3: How the UE NAS provides the NSAGs priorities to UE AS is based internal UE interface, and not specified. When a S-NSSAI is replaced by an Alternative S-NSSAI for a UE supporting the Network Slice Replacement feature (see clause 5.15.19) then the AMF provides updated NSAG information also including the Alternative S-NSSAI to the UE when the Alternative S-NSSAI was not part of the UE Configured NSSAI and is Added to the UE configured NSSAI. The NSAG priority may take into account the Alternative S-NSSAI is a replacement of the replaced NSSAI if the Alternative S-NSSAI is not part of the UE subscription. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.3.4.3.4 |
6,418 | 4.13.8.6 Overload control | The MME and UE may only use the procedure defined in this clause if both the UE and MME indicate "Enhanced Discontinuous Coverage Support", see clause 4.13.8.1. In order to avoid a large number of UEs causing excessive signalling load on the network when leaving coverage or re-gaining coverage after being out of coverage, the MME may determine a Maximum Time Offset controlling when UEs are allowed to initiate NAS signalling with the network, as described in this clause. In this case, the MME determines this Maximum Time Offset based on network configuration, high priority access and priority services. The MME sends this Maximum Time Offset to individual UEs during the Attach or TAU procedures. If the UE receives this Maximum Time Offset from the network in an Attach or TAU Accept, the UE shall replace any previously received Maximum Time Offset on the same RAT type and PLMN with this one. When the UE knows a later time at which coverage will be lost and when the UE does not send a TAU Request to the MME in advance (see clause 4.13.8.2), the UE determines a random value up to the minimum of the latest Maximum Time Offset for this PLMN and RAT type and the time until coverage will be lost. The UE shall send the TAU Request at the time when coverage will be lost less the random value to the MME indicating the loss of coverage. Upon returning to coverage after being out of coverage due to discontinuous coverage, the UE sets the discontinuous coverage wait timer value to a random value up to and including the latest Maximum Time Offset for this PLMN and RAT type, and starts this timer. The UE shall not initiate any NAS signalling on that RAT Type and PLMN while the discontinuous coverage wait timer is running. The UE shall stop the discontinuous coverage wait timer and initiate NAS signalling if the UE receives paging message, has pending emergency services or when UE enters a Tracking Area outside the current Tracking Area List. | 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.13.8.6 |
6,419 | 4.3.18.3 Priority EPS Bearer Services | The Service User receives on demand priority treatment according to its MPS profile, i.e. On-Demand. If the Service User is not authorized to use on-demand priority request, the Service User receives priority treatment (i.e. appropriate ARP and QCI ) at initial attach for all bearers, based on user profile data stored in the HSS/SPR and authorized by the PCRF (see TS 23.203[ Policy and charging control architecture ] [6], clause 7.2). An On-Demand Service User requires explicit invocation/revocation via SPR MPS user profile update (see TS 23.203[ Policy and charging control architecture ] [6], clause 7.5). Since MPS user profile are part of inputs for PCC rules, the update will trigger PCC rules modification to achieve appropriate ARP and QCI settings for bearers (see TS 23.203[ Policy and charging control architecture ] [6], clause 7.4.2). When the eNodeB receives mobile initiated signalling with establishment cause set to highPriorityAccess, the eNodeB handles the RRC connection request with priority. When the MME receives and verifies mobile initiated signalling with establishment cause set to highPriorityAccess, the MME establishes the S1 bearer with priority. Based on MPS EPS priority subscription, MME can verify whether the UE is permitted to handle the request preferentially comparing to other UEs not prioritized. An AF for MPS Priority Service is used to provide Priority EPS Bearer Services using network-initiated resource allocation procedures (via interaction with PCC) for originating accesses. NOTE: Use of 3rd party AF for MPS services for Service Users is outside the scope of 3GPP specification. | 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.18.3 |
6,420 | 8.13.3.5.2 Minimum Requirement for TDD PCell | The purpose of these tests is to verify the closed loop rank-two performance with wideband and frequency selective precoding. For TDD FDD DC with TDD PCell and 2DL CCs, the requirements are specified in Table 8.13.3.5.2-4 based on single carrier requirement specified in Table 8.13.3.5.2-2 and Table 8.13.3.5.2-3, with the addition of the parameters in Table 8.13.3.5.2-1 and the downlink physical channel setup according to Annex C.3.2. The test coverage for different number of component carriers is defined in 8.1.2.4. Table 8.13.3.5.2-1: Test Parameters for Multi-Layer Spatial Multiplexing (FRC) for DC Table 8.13.3.5.2-2: Single carrier performance with different bandwidths for multiple DC configurations for FDD SCell (FRC) Table 8.13.3.5.2-3: Single carrier performance with different bandwidths for multiple DC configurations for TDD PCell and SCell (FRC) Table 8.13.3.5.2-4: Minimum performance for multiple DC configurations with 2DL 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.13.3.5.2 |
6,421 | 5.8.9.4.3 Transmission of MasterInformationBlockSidelink message | The UE shall set the contents of the MasterInformationBlockSidelink message as follows: 1> if in coverage on the frequency used for the NR sidelink communication/positioning as defined in TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [20]. 2> set inCoverage to true; 2> if tdd-UL-DL-ConfigurationCommon is included in the received SIB1: 3> set sl-TDD-Config to the value representing the same meaning as that is included in tdd-UL-DL-ConfigurationCommon, as described in TS 38.213[ NR; Physical layer procedures for control ] , clause 16.1 [13]; 2> else: 3> set sl-TDD-Config to the value as specified in TS 38.213[ NR; Physical layer procedures for control ] [13], clause 16.1; 2> if syncInfoReserved is included in an entry of configured sl-SyncConfigList corresponding to the concerned frequency from the received SIB12: 3> set reservedBits to the value of syncInfoReserved in the received SIB12; 2> else: 3> set all bits in reservedBits to 0; 1> else if out of coverage on the frequency used for NR sidelink communication/positioning as defined in TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [20]; and the concerned frequency is included in sl-FreqInfoToAddModList/sl-FreqInfoToAddModListExt in RRCReconfiguration or in sl-FreqInfoList/sl-FreqInfoListSizeExt within SIB12: 2> set inCoverage to true; 2> set reservedBits to the value of the corresponding field included in the preconfigured sidelink parameters (i.e. sl-PreconfigGeneral in SidelinkPreconfigNR defined in 9.3); 2> set sl-TDD-Config to the value representing the same meaning as that is included in the corresponding field included in the preconfigured sidelink parameters (i.e. sl-PreconfigGeneral in SL-PreconfigurationNR defined in 9.3) as described in TS 38.213[ NR; Physical layer procedures for control ] , clause 16.1 [13]; 1> else if out of coverage on the frequency used for NR sidelink communication/positioning as defined in TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [20]; and the UE selects GNSS as the synchronization reference and sl-SSB-TimeAllocation3 is not configured for the frequency used in SidelinkPreconfigNR: 2> set inCoverage to true; 2> set reservedBits to the value of the corresponding field included in the preconfigured sidelink parameters (i.e. sl-PreconfigGeneral in SidelinkPreconfigNR defined in 9.3); 2> set sl-TDD-Config to the value representing the same meaning as that is included in the corresponding field included in the preconfigured sidelink parameters (i.e. sl-PreconfigGeneral in SL-PreconfigurationNR defined in 9.3) as described in TS 38.213[ NR; Physical layer procedures for control ] , clause 16.1 [13]; 1> else if the UE has a selected SyncRef UE (as defined in 5.8.6): 2> set inCoverage to false; 2> set sl-TDD-Config and reservedBits to the value of the corresponding field included in the received MasterInformationBlockSidelink; 1> else: 2> set inCoverage to false; 2> set reservedBits to the value of the corresponding field included in the preconfigured sidelink parameters (i.e. sl-PreconfigGeneral in SidelinkPreconfigNR defined in 9.3); 2> set sl-TDD-Config to the value representing the same meaning as that is included in the corresponding field included in the preconfigured sidelink parameters (i.e. sl-PreconfigGeneral in SL-PreconfigurationNR defined in 9.3) as described in TS 38.213[ NR; Physical layer procedures for control ] , clause 16.1 [13]; 1> set directFrameNumber and slotIndex according to the slot used to transmit the SLSS, as specified in 5.8.5.3; 1> submit the MasterInformationBlockSidelink to lower layers for transmission upon which the procedure ends; | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.8.9.4.3 |
6,422 | – CellGroupConfig | The CellGroupConfig IE is used to configure a master cell group (MCG) or secondary cell group (SCG). A cell group comprises of one MAC entity, a set of logical channels with associated RLC entities and of a primary cell (SpCell) and one or more secondary cells (SCells). For an NCR-MT, the CellGroupConfig IE is also used to provide the configuration of side control information for the NCR-Fwd access link. CellGroupConfig information element -- ASN1START -- TAG-CELLGROUPCONFIG-START -- Configuration of one Cell-Group: CellGroupConfig ::= SEQUENCE { cellGroupId CellGroupId, rlc-BearerToAddModList SEQUENCE (SIZE(1..maxLC-ID)) OF RLC-BearerConfig OPTIONAL, -- Need N rlc-BearerToReleaseList SEQUENCE (SIZE(1..maxLC-ID)) OF LogicalChannelIdentity OPTIONAL, -- Need N mac-CellGroupConfig MAC-CellGroupConfig OPTIONAL, -- Need M physicalCellGroupConfig PhysicalCellGroupConfig OPTIONAL, -- Need M spCellConfig SpCellConfig OPTIONAL, -- Need M sCellToAddModList SEQUENCE (SIZE (1..maxNrofSCells)) OF SCellConfig OPTIONAL, -- Need N sCellToReleaseList SEQUENCE (SIZE (1..maxNrofSCells)) OF SCellIndex OPTIONAL, -- Need N ..., [[ reportUplinkTxDirectCurrent ENUMERATED {true} OPTIONAL -- Cond BWP-Reconfig ]], [[ bap-Address-r16 BIT STRING (SIZE (10)) OPTIONAL, -- Need M bh-RLC-ChannelToAddModList-r16 SEQUENCE (SIZE(1..maxBH-RLC-ChannelID-r16)) OF BH-RLC-ChannelConfig-r16 OPTIONAL, -- Need N bh-RLC-ChannelToReleaseList-r16 SEQUENCE (SIZE(1..maxBH-RLC-ChannelID-r16)) OF BH-RLC-ChannelID-r16 OPTIONAL, -- Need N f1c-TransferPath-r16 ENUMERATED {lte, nr, both} OPTIONAL, -- Need M simultaneousTCI-UpdateList1-r16 SEQUENCE (SIZE (1..maxNrofServingCellsTCI-r16)) OF ServCellIndex OPTIONAL, -- Need R simultaneousTCI-UpdateList2-r16 SEQUENCE (SIZE (1..maxNrofServingCellsTCI-r16)) OF ServCellIndex OPTIONAL, -- Need R simultaneousSpatial-UpdatedList1-r16 SEQUENCE (SIZE (1..maxNrofServingCellsTCI-r16)) OF ServCellIndex OPTIONAL, -- Need R simultaneousSpatial-UpdatedList2-r16 SEQUENCE (SIZE (1..maxNrofServingCellsTCI-r16)) OF ServCellIndex OPTIONAL, -- Need R uplinkTxSwitchingOption-r16 ENUMERATED {switchedUL, dualUL} OPTIONAL, -- Need R uplinkTxSwitchingPowerBoosting-r16 ENUMERATED {enabled} OPTIONAL -- Need R ]], [[ reportUplinkTxDirectCurrentTwoCarrier-r16 ENUMERATED {true} OPTIONAL -- Need N ]], [[ f1c-TransferPathNRDC-r17 ENUMERATED {mcg, scg, both} OPTIONAL, -- Need M uplinkTxSwitching-2T-Mode-r17 ENUMERATED {enabled} OPTIONAL, -- Cond 2Tx uplinkTxSwitching-DualUL-TxState-r17 ENUMERATED {oneT, twoT} OPTIONAL, -- Cond 2Tx uu-RelayRLC-ChannelToAddModList-r17 SEQUENCE (SIZE(1..maxUu-RelayRLC-ChannelID-r17)) OF Uu-RelayRLC-ChannelConfig-r17 OPTIONAL, -- Need N uu-RelayRLC-ChannelToReleaseList-r17 SEQUENCE (SIZE(1..maxUu-RelayRLC-ChannelID-r17)) OF Uu-RelayRLC-ChannelID-r17 OPTIONAL, -- Need N simultaneousU-TCI-UpdateList1-r17 SEQUENCE (SIZE (1..maxNrofServingCellsTCI-r16)) OF ServCellIndex OPTIONAL, -- Need R simultaneousU-TCI-UpdateList2-r17 SEQUENCE (SIZE (1..maxNrofServingCellsTCI-r16)) OF ServCellIndex OPTIONAL, -- Need R simultaneousU-TCI-UpdateList3-r17 SEQUENCE (SIZE (1..maxNrofServingCellsTCI-r16)) OF ServCellIndex OPTIONAL, -- Need R simultaneousU-TCI-UpdateList4-r17 SEQUENCE (SIZE (1..maxNrofServingCellsTCI-r16)) OF ServCellIndex OPTIONAL, -- Need R rlc-BearerToReleaseListExt-r17 SEQUENCE (SIZE(1..maxLC-ID)) OF LogicalChannelIdentityExt-r17 OPTIONAL, -- Need N iab-ResourceConfigToAddModList-r17 SEQUENCE (SIZE(1..maxNrofIABResourceConfig-r17)) OF IAB-ResourceConfig-r17 OPTIONAL, -- Need N iab-ResourceConfigToReleaseList-r17 SEQUENCE (SIZE(1..maxNrofIABResourceConfig-r17)) OF IAB-ResourceConfigID-r17 OPTIONAL -- Need N ]], [[ reportUplinkTxDirectCurrentMoreCarrier-r17 ReportUplinkTxDirectCurrentMoreCarrier-r17 OPTIONAL -- Need N ]], [[ prioSCellPRACH-OverSP-PeriodicSRS-r17 ENUMERATED {enabled} OPTIONAL -- Need R ]], [[ ncr-FwdConfig-r18 SetupRelease { NCR-FwdConfig-r18 } OPTIONAL, -- Cond NCR autonomousDenialParameters-r18 SetupRelease {AutonomousDenialParameters-r18} OPTIONAL, -- Need M nonCollocatedTypeMRDC-r18 ENUMERATED { type1 } OPTIONAL, -- Need R nonCollocatedTypeNR-CA-r18 ENUMERATED { type1 } OPTIONAL, -- Need R uplinkTxSwitchingMoreBands-r18 SetupRelease { UplinkTxSwitchingMoreBands-r18 } OPTIONAL -- Need M ]] } -- Serving cell specific MAC and PHY parameters for a SpCell: SpCellConfig ::= SEQUENCE { servCellIndex ServCellIndex OPTIONAL, -- Cond SCG reconfigurationWithSync ReconfigurationWithSync OPTIONAL, -- Cond ReconfWithSync rlf-TimersAndConstants SetupRelease { RLF-TimersAndConstants } OPTIONAL, -- Need M rlmInSyncOutOfSyncThreshold ENUMERATED {n1} OPTIONAL, -- Need S spCellConfigDedicated ServingCellConfig OPTIONAL, -- Need M ..., [[ lowMobilityEvaluationConnected-r17 SEQUENCE { s-SearchDeltaP-Connected-r17 ENUMERATED {dB3, dB6, dB9, dB12, dB15, spare3, spare2, spare1}, t-SearchDeltaP-Connected-r17 ENUMERATED {s5, s10, s20, s30, s60, s120, s180, s240, s300, spare7, spare6, spare5, spare4, spare3, spare2, spare1} } OPTIONAL, -- Need R goodServingCellEvaluationRLM-r17 GoodServingCellEvaluation-r17 OPTIONAL, -- Need R goodServingCellEvaluationBFD-r17 GoodServingCellEvaluation-r17 OPTIONAL, -- Need R deactivatedSCG-Config-r17 SetupRelease { DeactivatedSCG-Config-r17 } OPTIONAL -- Cond SCG-Opt ]] } ReconfigurationWithSync ::= SEQUENCE { spCellConfigCommon ServingCellConfigCommon OPTIONAL, -- Need M newUE-Identity RNTI-Value, t304 ENUMERATED {ms50, ms100, ms150, ms200, ms500, ms1000, ms2000, ms10000}, rach-ConfigDedicated CHOICE { uplink RACH-ConfigDedicated, supplementaryUplink RACH-ConfigDedicated } OPTIONAL, -- Need N ..., [[ smtc SSB-MTC OPTIONAL -- Need S ]], [[ daps-UplinkPowerConfig-r16 DAPS-UplinkPowerConfig-r16 OPTIONAL -- Need N ]], [[ sl-PathSwitchConfig-r17 SL-PathSwitchConfig-r17 OPTIONAL -- Cond DirectToIndirect-PathSwitch ]], [[ rach-LessHO-r18 RACH-LessHO-r18 OPTIONAL -- Need N ]] } DAPS-UplinkPowerConfig-r16 ::= SEQUENCE { p-DAPS-Source-r16 P-Max, p-DAPS-Target-r16 P-Max, uplinkPowerSharingDAPS-Mode-r16 ENUMERATED {semi-static-mode1, semi-static-mode2, dynamic } } SCellConfig ::= SEQUENCE { sCellIndex SCellIndex, sCellConfigCommon ServingCellConfigCommon OPTIONAL, -- Cond SCellAdd sCellConfigDedicated ServingCellConfig OPTIONAL, -- Cond SCellAddMod ..., [[ smtc SSB-MTC OPTIONAL -- Need S ]], [[ sCellState-r16 ENUMERATED {activated} OPTIONAL, -- Cond SCellAddSync secondaryDRX-GroupConfig-r16 ENUMERATED {true} OPTIONAL -- Need S ]], [[ preConfGapStatus-r17 BIT STRING (SIZE (maxNrofGapId-r17)) OPTIONAL, -- Cond PreConfigMG goodServingCellEvaluationBFD-r17 GoodServingCellEvaluation-r17 OPTIONAL, -- Need R sCellSIB20-r17 SetupRelease { SCellSIB20-r17 } OPTIONAL -- Need M ]], [[ plmn-IdentityInfoList-r17 SetupRelease {PLMN-IdentityInfoList} OPTIONAL, -- Cond SCellSIB20-Opt npn-IdentityInfoList-r17 SetupRelease {NPN-IdentityInfoList-r16} OPTIONAL -- Cond SCellSIB20-Opt ]] } SCellSIB20-r17 ::= OCTET STRING (CONTAINING SystemInformation) DeactivatedSCG-Config-r17 ::= SEQUENCE { bfd-and-RLM-r17 BOOLEAN, ... } GoodServingCellEvaluation-r17 ::= SEQUENCE { offset-r17 ENUMERATED {db2, db4, db6, db8} OPTIONAL -- Need S } SL-PathSwitchConfig-r17 ::= SEQUENCE { targetRelayUE-Identity-r17 SL-SourceIdentity-r17, t420-r17 ENUMERATED {ms50, ms100, ms150, ms200, ms500, ms1000, ms2000, ms10000}, ... } IAB-ResourceConfig-r17 ::= SEQUENCE { iab-ResourceConfigID-r17 IAB-ResourceConfigID-r17, slotList-r17 SEQUENCE (SIZE (1..5120)) OF INTEGER (0..5119) OPTIONAL, -- Need M periodicitySlotList-r17 ENUMERATED {ms0p5, ms0p625, ms1, ms1p25, ms2, ms2p5, ms5, ms10, ms20, ms40, ms80, ms160} OPTIONAL, -- Need M slotListSubcarrierSpacing-r17 SubcarrierSpacing OPTIONAL, -- Need M ... } IAB-ResourceConfigID-r17 ::= INTEGER(0..maxNrofIABResourceConfig-1-r17) ReportUplinkTxDirectCurrentMoreCarrier-r17 ::= SEQUENCE (SIZE(1.. maxSimultaneousBands)) OF IntraBandCC-CombinationReqList-r17 IntraBandCC-CombinationReqList-r17::= SEQUENCE { servCellIndexList-r17 SEQUENCE (SIZE(1.. maxNrofServingCells)) OF ServCellIndex, cc-CombinationList-r17 SEQUENCE (SIZE(1.. maxNrofReqComDC-Location-r17)) OF IntraBandCC-Combination-r17 } IntraBandCC-Combination-r17::= SEQUENCE (SIZE(1.. maxNrofServingCells)) OF CC-State-r17 CC-State-r17::= SEQUENCE { dlCarrier-r17 CarrierState-r17 OPTIONAL, -- Need N ulCarrier-r17 CarrierState-r17 OPTIONAL -- Need N } CarrierState-r17::= CHOICE { deActivated-r17 NULL, activeBWP-r17 INTEGER (0..maxNrofBWPs) } AutonomousDenialParameters-r18 ::= SEQUENCE { autonomousDenialSlots-r18 ENUMERATED {n2, n5, n10, n15, n20, n30}, autonomousDenialValidity-r18 ENUMERATED {n200, n500, n1000, n2000} } RACH-LessHO-r18 ::= SEQUENCE { targetNTA-r18 ENUMERATED {zero, source} OPTIONAL, -- Need R tci-StateID-r18 TCI-StateId OPTIONAL, -- Cond MobileIAB dg-beam-r18 SSB-Index OPTIONAL, -- Cond DG-RACH-LessHO ... } UplinkTxSwitchingMoreBands-r18::= SEQUENCE { uplinkTxSwitchingBandList-r18 SEQUENCE (SIZE (1..maxSimultaneousBands)) OF FreqBandIndicatorNR OPTIONAL, -- Need M uplinkTxSwitchingBandPairList-r18 UplinkTxSwitchingBandPairList-r18 OPTIONAL, -- Need M uplinkTxSwitchingAssociatedBandDualUL-List-r18 UplinkTxSwitchingAssociatedBandDualUL-List-r18 OPTIONAL, -- Need M ... } UplinkTxSwitchingBandPairList-r18::= SEQUENCE (SIZE (1.. maxULTxSwitchingBandPairs)) OF UplinkTxSwitchingBandPairConfig-r18 UplinkTxSwitchingBandPairConfig-r18::= SEQUENCE { bandInfoUL1-r18 UplinkTxSwitchingBandIndex-r18, bandInfoUL2-r18 UplinkTxSwitchingBandIndex-r18, switchingOptionConfigForBandPair-r18 ENUMERATED {switchedUL, dualUL}, switching2T-Mode-r18 ENUMERATED {enabled} OPTIONAL, -- Need R ... } UplinkTxSwitchingAssociatedBandDualUL-List-r18::= SEQUENCE (SIZE (0..maxSimultaneousBands)) OF UplinkTxSwitchingAssociatedBandDualUL-r18 UplinkTxSwitchingAssociatedBandDualUL-r18::= SEQUENCE { transmitBand-r18 UplinkTxSwitchingBandIndex-r18, associatedBand-r18 UplinkTxSwitchingBandIndex-r18 } UplinkTxSwitchingBandIndex-r18::= INTEGER (1..maxSimultaneousBands) -- TAG-CELLGROUPCONFIG-STOP -- ASN1STOP NOTE: In case of change of AS security key derived from S-KgNB/S-KeNB, if reconfigurationWithSync is not included in the masterCellGroup, the network releases all existing MCG RLC bearers associated with a radio bearer with keyToUse set to secondary. In case of change of AS security key derived from KgNB/KeNB, if reconfigurationWithSync is not included in the secondaryCellGroup, the network releases all existing SCG RLC bearers associated with a radio bearer with keyToUse set to primary. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
6,423 | 4.2A Handling of NAS signalling low priority indication | A UE configured for NAS signalling low priority (see 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [15A], 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [17]) indicates this by including the Device properties IE in the appropriate NAS message and setting the low priority indicator to "MS is configured for NAS signalling low priority", except for the following cases in which the UE shall set the low priority indicator to "MS is not configured for NAS signalling low priority": - the UE is performing an attach for emergency bearer services; - the UE has a PDN connection for emergency bearer services established and is performing EPS mobility management procedures, or is establishing a PDN connection for emergency bearer services; - the UE configured for dual priority is requested by the upper layers to establish a PDN connection with the low priority indicator set to "MS is not configured for NAS signalling low priority"; - the UE configured for dual priority is performing EPS session management procedures related to the PDN connection established with low priority indicator set to "MS is not configured for NAS signalling low priority"; - the UE configured for dual priority has a PDN connection established by setting the low priority indicator to "MS is not configured for NAS signalling low priority" and is performing EPS mobility management procedures; - the UE is performing a service request procedure for a CS fallback emergency call or 1xCS fallback emergency call; - the UE is a UE configured to use AC11 – 15 in selected PLMN; or - the UE is responding to paging. The network may use the NAS signalling low priority indication for NAS level mobility management congestion control and APN based congestion control. If the NAS signalling low priority indication is provided in a PDN CONNECTIVITY REQUEST message, the MME stores the NAS signalling low priority indication within the default EPS bearer context activated due to the PDN connectivity request 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 | 4.2A |
6,424 | 5.5.1.2.4 Attach accepted by the network | During an attach for emergency bearer services, if not restricted by local regulations, the MME shall not check for mobility and access restrictions, regional restrictions, subscription restrictions, or perform CSG access control when processing the ATTACH REQUEST message. The network shall not apply subscribed APN based congestion control during an attach procedure for emergency bearer services. During an attach for access to RLOS, the MME shall not check for access restrictions, regional restrictions and subscription restrictions when processing the ATTACH REQUEST message. If the attach request is accepted by the network, the MME shall send an ATTACH ACCEPT message to the UE and start timer T3450. If the attach request included the PDN CONNECTIVITY REQUEST message in the ESM message container information element to request PDN connectivity, the MME when accepting the attach request shall: - send the ATTACH ACCEPT message together with an ESM DUMMY MESSAGE contained in the ESM message container information element and discard the ESM message container information element included in the attach request if: - the UE indicated support of EMM-REGISTERED without PDN connection in the UE network capability IE of the ATTACH REQUEST message; - the MME supports EMM-REGISTERED without PDN connection and PDN connection is restricted according to the user's subscription data; - the attach type is not set to "EPS emergency attach" or "EPS RLOS attach"; and - the request type of the UE requested PDN connection is not set to "handover of emergency bearer services", "emergency" or "RLOS"; - otherwise, send the ATTACH ACCEPT message together with an ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message contained in the ESM message container information element to activate the default bearer (see clause 6.4.1). In WB-S1 mode, the network may also initiate the activation of dedicated bearers towards the UE by invoking the dedicated EPS bearer context activation procedure (see clause 6.4.2). In NB-S1 mode the network shall not initiate the activation of dedicated bearers. If EMM-REGISTERED without PDN connection is supported by the UE and the MME, and the UE included an ESM DUMMY MESSAGE in the ESM message container information element of the ATTACH REQUEST message, the MME shall send the ATTACH ACCEPT message together with an ESM DUMMY MESSAGE contained in the ESM message container information element. If the attach request is accepted by the network, the MME shall delete the stored UE radio capability information or the UE radio capability ID, if any. In NB-S1 mode, if the attach request is accepted by the network, the MME shall set the EMC BS bit to zero in the EPS network feature support IE included in the ATTACH ACCEPT message to indicate that support of emergency bearer services in NB-S1 mode is not available. If the UE has included the UE network capability IE or the MS network capability IE or both in the ATTACH REQUEST message, the MME shall store all octets received from the UE, up to the maximum length defined for the respective information element. NOTE 1: This information is forwarded to the new MME during inter-MME handover or to the new SGSN during inter-system handover to A/Gb mode or Iu mode. NOTE 2: For further details concerning the handling of the MS network capability and UE network capability in the MME see also 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [10]. If the UE specific DRX parameter was included in the DRX Parameter IE in the ATTACH REQUEST message, the MME shall replace any stored UE specific DRX parameter with the received parameter and use it for the downlink transfer of signalling and user data in WB-S1 mode. In NB-S1 mode, if the DRX parameter in NB-S1 mode IE was included in the ATTACH REQUEST message, the MME shall provide to the UE the Negotiated DRX parameter in NB-S1 mode IE in the ATTACH ACCEPT message. The MME shall replace any stored UE specific DRX parameter in NB-S1 mode with the negotiated DRX parameter and use it for the downlink transfer of signalling and user data in NB-S1 mode. NOTE 3: In NB-S1 mode, if a DRX parameter was included in the Negotiated DRX parameter in NB-S1 mode IE in the ATTACH ACCEPT message, then the UE stores and uses the received DRX parameter in NB-S1 mode (see 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [21]). If the UE did not receive a DRX parameter in the Negotiated DRX parameter in NB-S1 mode IE, or if the Negotiated DRX parameter in NB-S1 mode IE was not included in the ATTACH ACCEPT message, then the UE uses the cell specific DRX value in NB-S1 mode (see 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [21]). In NB-S1 mode, if the UE requested "SMS only" in the Additional update type IE, supports NB-S1 mode only and the MME decides to accept the attach request for EPS services and "SMS only", the MME shall indicate "SMS only" in the Additional update result IE and shall set the EPS attach result IE to "EPS only" in the ATTACH ACCEPT message. The MME shall include the extended DRX parameters IE in the ATTACH ACCEPT message only if the extended DRX parameters IE was included in the ATTACH REQUEST message, and the MME supports and accepts the use of eDRX. If - the UE supports WUS assistance; and - the MME supports and accepts the use of WUS assistance, then the MME shall determine the negotiated UE paging probability information for the UE, store it in the EMM context of the UE, and if the UE is not attaching for emergency bearer services, the MME shall include it in the Negotiated WUS assistance information IE in the ATTACH ACCEPT message. The MME may take into account the UE paging probability information received in the Requested WUS assistance information IE when determining the negotiated UE paging probability information for the UE. NOTE 4: Besides the UE paging probability information requested by the UE, the MME can take local configuration or previous statistical information for the UE into account when determining the negotiated UE paging probability information for the UE (see 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [10]). The MME shall assign and include the TAI list the UE is registered to in the ATTACH ACCEPT message. The MME shall not assign a TAI list containing both tracking areas in NB-S1 mode and tracking areas in WB-S1 mode. The UE, upon receiving an ATTACH ACCEPT message, shall delete its old TAI list and store the received TAI list. NOTE 5: When assigning the TAI list, the MME can take into account the eNodeB's capability of support of CIoT EPS optimization. The MME may include T3412 extended value IE in the ATTACH ACCEPT message only if the UE indicates support of the extended periodic timer T3412 in the MS network feature support IE in the ATTACH REQUEST message. The MME shall include the T3324 value IE in the ATTACH ACCEPT message only if the T3324 value IE was included in the ATTACH REQUEST message, and the MME supports and accepts the use of PSM. If the MME supports and accepts the use of PSM, and the UE included the T3412 extended value IE in the ATTACH REQUEST message, then the MME shall take into account the T3412 value requested when providing the T3412 value IE and the T3412 extended value IE in the ATTACH ACCEPT message. NOTE 6: Besides the value requested by the UE, the MME can take local configuration or subscription data provided by the HSS into account when selecting a value for T3412 (3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [10] clause 4.3.17.3). If the UE indicates support for EMM-REGISTERED without PDN connection in the ATTACH REQUEST message and the MME supports EMM-REGISTERED without PDN connection, the MME shall indicate support for EMM-REGISTERED without PDN connection in the EPS network feature support IE of the ATTACH ACCEPT message. The UE and the MME shall use the information whether the peer entity supports EMM-REGISTERED without PDN connection as specified in the present clause 5 and in clause 6. If the UE requests "control plane CIoT EPS optimization" in the Additional update type IE, indicates support of control plane CIoT EPS optimization in the UE network capability IE and the MME decides to accept the requested CIoT EPS optimization and the attach request, the MME shall indicate "control plane CIoT EPS optimization supported" in the EPS network feature support IE. If the UE indicates support for enhanced discontinuous coverage in the ATTACH REQUEST message, and the MME supports enhanced discontinuous coverage, the MME shall indicate "Enhanced discontinuous coverage supported" in the EPS network feature support IE of the ATTACH ACCEPT message. If the MME supports NB-S1 mode, non-IP or Ethernet PDN type, inter-system change with 5GS, UAS services or the network wants to enforce the use of DNS over (D)TLS (see 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]), then the MME shall support the Extended protocol configuration options IE. NOTE 7: Support of DNS over (D)TLS is based on the informative requirements as specified in 3GPP TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [19] and it is implemented based on the operator requirement. If the MME supports the Extended protocol configuration options IE and the UE indicated support of the Extended protocol configuration options IE, then the MME shall set the ePCO bit to "extended protocol configuration options supported" in the EPS network feature support IE of the ATTACH ACCEPT message. If the UE indicates support for restriction on use of enhanced coverage in the ATTACH REQUEST message, and the network decides to restrict the use of enhanced coverage for the UE, then the MME shall set the RestrictEC bit to "Use of enhanced coverage is restricted" in the EPS network feature support IE of the ATTACH ACCEPT message. If the UE has indicated support for the control plane data back-off timer, and the MME decides to activate the congestion control for transport of user data via the control plane, then the MME shall include the T3448 value IE in the ATTACH ACCEPT message. If the UE indicates support for dual connectivity with NR in the ATTACH REQUEST message, and the MME decides to restrict the use of dual connectivity with NR for the UE, then the MME shall set the RestrictDCNR bit to "Use of dual connectivity with NR is restricted" in the EPS network feature support IE of the ATTACH ACCEPT message. If the UE indicates support for N1 mode in the ATTACH REQUEST message and the MME supports inter-system interworking with 5GS, the MME may set the IWK N26 bit to either: - "interworking without N26 interface not supported" if the MME supports N26 interface; or - "interworking without N26 interface supported" if the MME does not support N26 interface in the EPS network feature support IE in the ATTACH ACCEPT message. If the UE requests ciphering keys for ciphered broadcast assistance data in the ATTACH REQUEST message and the MME has valid ciphering key data applicable to the UE's subscription, then the MME shall include the ciphering key data in the Ciphering key data IE of the ATTACH ACCEPT message. If the UE indicates support of the NAS signalling connection release in the ATTACH REQUEST message and the network decides to accept the NAS signalling connection release, then the MME shall set the NAS signalling connection release bit to "NAS signalling connection release supported" in the EPS network feature support IE of the ATTACH ACCEPT message. If the UE indicates support of the paging indication for voice services in the ATTACH REQUEST message and the network decides to accept the paging indication for voice services, then the MME shall set the paging indication for voice services bit to "paging indication for voice services supported" in the EPS network feature support IE of the ATTACH ACCEPT message. Upon receipt of ATTACH ACCEPT message with the paging indication for voice services bit set to "paging indication for voice services supported", the UE NAS layer informs the lower layers that paging indication for voice services is supported. Otherwise, the UE NAS layer informs the lower layers that paging indication for voice services is not supported. If the UE indicates support of the reject paging request in the ATTACH REQUEST message and the network decides to accept the reject paging request, then the MME shall set the reject paging request bit to "reject paging request supported" in the EPS network feature support IE of the ATTACH ACCEPT message. If the UE indicates support of the paging restriction in the ATTACH REQUEST message, and the MME sets: - the reject paging request bit to "reject paging request supported"; - the NAS signalling connection release bit to "NAS signalling connection release supported"; or - both of them; in the EPS network feature support IE of the ATTACH ACCEPT message, and the network decides to accept the paging restriction, then the MME shall set the paging restriction bit to "paging restriction supported" in the EPS network feature support IE of the ATTACH ACCEPT message. If the UE indicates support of the paging timing collision control in the ATTACH REQUEST message and the network decides to accept the paging timing collision control, then the MME shall set the paging timing collision control bit to "paging timing collision control supported" in the EPS network feature support IE of the ATTACH ACCEPT message. If the MUSIM UE has included a Requested IMSI offset IE in the ATTACH REQUEST message and if the MME supports paging timing collision control, the MME shall include the Negotiated IMSI offset IE in the ATTACH ACCEPT message, and the MME shall set the IMSI offset value to: - A value that is different than what the UE has provided, if the MME has a different value; or - A value that is same as what the UE has provided, if the MME does not have a different value; and the MME shall calculate an alternative IMSI value using the IMSI offset value and store it in the UE context as specified in 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [10]. The alternative IMSI value is used for deriving the paging occasion as specified in 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [21]. If the MUSIM UE has not included a Requested IMSI offset IE in the ATTACH REQUEST message, the MME shall erase any stored alternative IMSI value for that UE, if available. The MME shall set the redir-policy bit to "Unsecured redirection to GERAN or UTRAN not allowed" in the Network policy IE of the ATTACH ACCEPT message if unsecured redirection to a GERAN or UTRAN cell is not allowed in the current PLMN. Otherwise, the redir-policy bit shall be set to "Unsecured redirection to GERAN or UTRAN allowed". The MME may include the T3447 value IE set to the service gap time value in the ATTACH ACCEPT message if: - the UE has indicated support for service gap control; and - a service gap time value is available in the EMM context. If the network supports signalling for a maximum number of 15 EPS bearer contexts and the UE indicated support of signalling for a maximum number of 15 EPS bearer contexts in the ATTACH REQUEST message, then the MME shall set the 15 bearers bit to "Signalling for a maximum number of 15 EPS bearer contexts supported" in the EPS network feature support IE of the ATTACH ACCEPT message. Upon receiving the ATTACH ACCEPT message, the UE shall stop timer T3410. The GUTI reallocation may be part of the attach procedure. When the ATTACH REQUEST message includes the IMSI or IMEI, or the MME considers the GUTI provided by the UE is invalid, or the GUTI provided by the UE was assigned by another MME, the MME shall allocate a new GUTI to the UE. The MME shall include in the ATTACH ACCEPT message the new assigned GUTI together with the assigned TAI list. In this case the MME shall enter state EMM-COMMON-PROCEDURE-INITIATED as described in clause 5.4.1. For a shared network, the TAIs included in the TAI list can contain different PLMN identities. The MME indicates the selected core network operator PLMN identity to the UE in the GUTI (see 3GPP TS 23.251[ Network sharing; Architecture and functional description ] [8B]). If the ATTACH ACCEPT message contains a GUTI, the UE shall use this GUTI as the new temporary identity. The UE shall delete its old GUTI and store the new assigned GUTI. If no GUTI has been included by the MME in the ATTACH ACCEPT message, the old GUTI, if any available, shall be kept. If A/Gb mode or Iu mode is supported in the UE, the UE shall set its TIN to "GUTI" when receiving the ATTACH ACCEPT message. If the ATTACH ACCEPT message contains the T3412 extended value IE, then the UE shall use the value in T3412 extended value IE as periodic tracking area update timer (T3412). If the ATTACH ACCEPT message does not contain T3412 extended value IE, then the UE shall use the value in T3412 value IE as periodic tracking area update timer (T3412). If the ATTACH ACCEPT message contains the T3324 value IE, then the UE shall use the included timer value for T3324 as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13], clause 4.7.2.8. If the ATTACH ACCEPT message contains the DCN-ID IE, then the UE shall store the included DCN-ID value together with the PLMN code of the registered PLMN in a DCN-ID list in a non-volatile memory in the ME as specified in annex C. If the ATTACH ACCEPT message contains Negotiated IMSI offset IE, the MUSIM UE shall forward the IMSI offset value to lower layers. If the ATTACH ACCEPT message does not contain Negotiated IMSI offset IE, the MUSIM UE shall indicate to lower layers to erase any IMSI offset value, if available. The MME may also include a list of equivalent PLMNs in the ATTACH ACCEPT message. Each entry in the list contains a PLMN code (MCC+MNC). The UE shall store the list as provided by the network, and if the attach procedure is neither for emergency bearer services nor for access to RLOS, the UE shall remove from the list any PLMN code that is already in the list of "forbidden PLMNs" or in the list of "forbidden PLMNs for GPRS service". In addition, the UE shall add to the stored list the PLMN code of the registered PLMN that sent the list. The UE shall replace the stored list on each receipt of the ATTACH ACCEPT message. If the ATTACH ACCEPT message does not contain a list, then the UE shall delete the stored list. If the MME received the list of TAIs from the satellite E-UTRAN as described in 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [10], and determines that, by UE subscription and operator's preferences, any but not all TAIs in the received list of TAIs is forbidden for roaming or for regional provision of service, the MME shall include the TAI(s) in: a) the Forbidden TAI(s) for the list of "Forbidden tracking areas for roaming" IE; b) the Forbidden TAI(s) for the list of "Forbidden tracking areas for regional provision of service" IE; or c) both, in the ATTACH ACCEPT message. If the attach procedure is neither for emergency bearer services nor for access to RLOS, and if the PLMN identity of the registered PLMN is a member of the list of "forbidden PLMNs" or the list of "forbidden PLMNs for GPRS service", any such PLMN identity shall be deleted from the corresponding list(s). The network informs the UE about the support of specific features, such as IMS voice over PS session, location services (EPC-LCS, CS-LCS), emergency bearer services, or CIoT EPS optimizations, in the EPS network feature support information element. In a UE with IMS voice over PS capability, the IMS voice over PS session indicator and the emergency bearer services indicator shall be provided to the upper layers. The upper layers take the IMS voice over PS session indicator into account as specified in 3GPP TS 23.221[ Architectural requirements ] [8A], clause 7.2a and clause 7.2b, when selecting the access domain for voice sessions or calls. When initiating an emergency call, the upper layers also take both the IMS voice over PS session indicator and the emergency bearer services indicator into account for the access domain selection. In a UE with LCS capability, location services indicators (EPC-LCS, CS-LCS) shall be provided to the upper layers. When MO-LR procedure is triggered by the UE's application, those indicators are taken into account as specified in 3GPP TS 24.171[ Control Plane Location Services (LCS) procedures in the Evolved Packet System (EPS) ] [13C]. If the RestrictDCNR bit is set to "Use of dual connectivity with NR is restricted" in the EPS network feature support IE of the ATTACH ACCEPT message, the UE shall provide the indication that dual connectivity with NR is restricted to the upper layers. The UE supporting N1 mode shall operate in the mode for inter-system interworking with 5GS as follows: - if the IWK N26 bit in the EPS network feature support IE is set to "interworking without N26 interface not supported", the UE shall operate in single-registration mode; - if the IWK N26 bit in the EPS network feature support IE is set to "interworking without N26 interface supported" and the UE supports dual-registration mode, the UE may operate in dual-registration mode; or NOTE 9: The registration mode used by the UE is implementation dependent. - if the IWK N26 bit in the EPS network feature support IE is set to "interworking without N26 interface supported" and the UE only supports single-registration mode, the UE shall operate in single-registration mode. The UE shall treat the interworking without N26 interface indicator as valid in the entire PLMN and equivalent PLMNs. The interworking procedures required for coordination between 5GMM and EMM without N26 interface are specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54]. If the redir-policy bit is set to "Unsecured redirection to GERAN or UTRAN not allowed" in the Network policy IE of the ATTACH ACCEPT message, the UE shall set the network policy on unsecured redirection to GERAN or UTRAN for the current PLMN to "Unsecured redirection to GERAN or UTRAN not allowed" and indicate to the lower layers that unsecured redirection to a GERAN or UTRAN cell is not allowed. If the redir-policy bit is set to "Unsecured redirection to GERAN or UTRAN allowed" or if the Network policy IE is not included in the ATTACH ACCEPT message, the UE shall set the network policy for the current PLMN to "Unsecured redirection to GERAN or UTRAN allowed" and indicate to the lower layers that unsecured redirection to a GERAN or UTRAN cell is allowed. The UE shall set the network policy on unsecured redirection to GERAN or UTRAN to "Unsecured redirection to GERAN or UTRAN not allowed" and indicate this to the lower layers when any of the following events occurs: - the UE initiates an EPS attach or tracking area updating procedure in a PLMN different from the PLMN where the UE performed the last successful EPS attach or tracking area updating procedure; - the UE is switched on; or - the UICC containing the USIM is removed. If the UE has initiated the attach procedure due to manual CSG selection and receives an ATTACH ACCEPT message; and the UE sent the ATTACH REQUEST message in a CSG cell, the UE shall check if the CSG ID and associated PLMN identity of the cell are contained in the Allowed CSG list. If not, the UE shall add that CSG ID and associated PLMN identity to the Allowed CSG list and the UE may add the HNB Name (if provided by lower layers) to the Allowed CSG list if the HNB Name is present in neither the Operator CSG list nor the Allowed CSG list. When the UE receives the ATTACH ACCEPT message combined with the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message, and if the UE has requested PDN connectivity the UE shall forward the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message to the ESM sublayer. Upon receipt of an indication from the ESM sublayer that the default EPS bearer context has been activated, the UE shall send an ATTACH COMPLETE message together with an ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT message contained in the ESM message container information element to the network. Additionally, the UE shall reset the attach attempt counter, enter state EMM-REGISTERED, and set the EPS update status to EU1 UPDATED. If EMM-REGISTERED without PDN connection is supported by the UE and the MME, and the UE receives the ATTACH ACCEPT message combined with an ESM DUMMY MESSAGE, the UE shall send an ATTACH COMPLETE message together with an ESM DUMMY MESSAGE contained in the ESM message container information element to the network. If the UE receives the ATTACH ACCEPT message from a PLMN for which a PLMN-specific attempt counter or PLMN-specific PS-attempt counter is maintained (see clause 5.3.7b), then the UE shall reset these counters. If the UE maintains a counter for "SIM/USIM considered invalid for GPRS services", then the UE shall reset this counter. When the UE receives any ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST messages during the attach procedure, and if the UE has requested PDN connectivity the UE shall forward the ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message(s) to the ESM sublayer. The UE shall send a response to the ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message(s) after successful completion of the attach procedure. If the attach procedure was initiated in S101 mode, the lower layers are informed about the successful completion of the procedure. NOTE 10: For the UE supporting non-IP or Ethernet PDN type or UAS services, if the UE receives the ATTACH ACCEPT message and the ePCO bit in the EPS network feature support IE is not set to "extended protocol configuration options supported", the UE can perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6] with the current PLMN considered as the lowest priority after the completion of the attach procedure. Upon receiving an ATTACH COMPLETE message, the MME shall stop timer T3450, enter state EMM-REGISTERED and consider the GUTI sent in the ATTACH ACCEPT message as valid. If the T3448 value IE is present in the received ATTACH ACCEPT message, the UE shall: - stop timer T3448 if it is running; and - start timer T3448 with the value provided in the T3448 value IE. If the UE is using EPS services with control plane CIoT EPS optimization, the T3448 value IE is present in the ATTACH ACCEPT message and the value indicates that this timer is either zero or deactivated, the UE shall consider this case as an abnormal case and proceed as if the T3448 value IE is not present. If the UE has indicated "service gap control supported" in the ATTACH REQUEST message and: - the ATTACH ACCEPT message contains the T3447 value IE, then the UE shall store the new T3447 value, erase any previous stored T3447 value if exists and use the new T3447 value with the T3447 timer next time it is started; or - the ATTACH ACCEPT message does not contain the T3447 value IE, then the UE shall erase any previous stored T3447 value if exists and stop the T3447 timer if running. In WB-S1 mode, if the UE has set the RACS bit to "RACS supported" in the UE network capability IE of the ATTACH REQUEST message, the MME may include a UE radio capability ID IE or a UE radio capability ID deletion indication IE in the ATTACH ACCEPT message. In WB-S1 mode, if the UE has set the RACS bit to "RACS supported" in the UE network capability IE of the ATTACH REQUEST message and the ATTACH ACCEPT message includes: - a UE radio capability ID deletion indication IE set to "Network-assigned UE radio capability IDs deletion requested", the UE shall delete any network-assigned UE radio capability IDs associated with the registered PLMN stored at the UE, then the UE shall, after the completion of the ongoing attach procedure, initiate a tracking area updating procedure as specified in clause 5.5.3 over the existing NAS signalling connection; or - a UE radio capability ID IE, the UE shall store the UE radio capability ID as specified in annex C. If the UE receives the Forbidden TAI(s) for the list of "forbidden tracking areas for roaming" IE in the ATTACH ACCEPT message, the UE shall store the TAI(s) included in the IE which are belonging to the serving PLMN or equivalent PLMN(s), if not already stored, into the list of "forbidden tracking areas for roaming" and ignore the TAI(s) which do not belong to the serving PLMN or equivalent PLMN(s). If the UE receives the Forbidden TAI(s) for the list of "forbidden tracking areas for regional provision of service" IE in the ATTACH ACCEPT message, the UE shall store the TAI(s) included in the IE which are belonging to the serving PLMN or equivalent PLMN(s), if not already stored, into the list of "forbidden tracking areas for regional provision of service" and ignore the TAI(s) which do not belong to the serving PLMN or equivalent PLMN(s). If for discontinuous coverage, the UE receives the Unavailability configuration IE in the ATTACH ACCEPT message and the End of unavailability report bit is set to "UE does not need to report end of unavailability", the UE is not required to trigger tracking area update procedure when the unavailability period duration has ended. If the UE does not receive the Unavailability configuration IE or the End of unavailability report bit is set to "UE needs to report end of unavailability", the UE should trigger tracking area update procedure when the unavailability period duration has ended. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.5.1.2.4 |
6,425 | 10.5.3.12 Daylight Saving Time | The purpose of this information element is to encode the Daylight Saving Time in steps of 1 hour. The Daylight Saving Time information element is coded as shown in figure 10.5.84b/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.97a/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The Daylight Saving Time is a type 4 information element with a length of 3 octets. Figure 10.5.84b/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Daylight Saving Time information element Table 10.5.97a/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Daylight Saving Time 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.12 |
6,426 | 8.51.7 gNodeB ID | The Target Type is gNodeB ID for an EPS to 5GS handover to a target gNodeB. In this case the coding of the Target ID field shall be coded as depicted in Figure 8.51.7-1. Figure 8.51.7-1: Target ID for Type gNode ID The gNodeB ID Length field, in bits 1 to 6 of octet 9, indicates the length of the gNodeB ID in number of bits. The gNodeB ID consists of 22 to 32 bits. The coding of the gNodeB ID is the responsibility of each administration. Coding using full hexadecimal representation (binary, not ASCII encoding) shall be used. Bit 1 of Octet 13 is the least significant bit. The most significant bit is determined as follows: - if the gNodeB ID Length is 32, bit 8 of octet 10 is the most significant bit; - if the gNodeB ID Length is 24, bit 8 of octet 11 is the most significant bit; all the bits of octet 10 shall be set to 0 by the sender and ignored by the receiver; - if the gNodeB ID Length is between 22 and 31, other than 24, the most significant bit is the bit determined by the operation "gNodeB ID Length modulo 8", of octet 10 if the length is greater than 24, or of octet 11 if the length is smaller than 24. All the bits from bit 8 of octet 10 down to the most significant bit (excluded) shall be set to 0 by the sender and ignored by the receiver. The 5GS TAC consists of 3 octets. Bit 8 of Octet 14 is the most significant bit and bit 1 of octet 16 the least significant bit. The coding of the tracking area code is the responsibility of each administration. Coding using full hexadecimal representation (binary, not ASCII encoding) shall be used. | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 8.51.7 |
6,427 | 7.3.2.3 Other performance requirements | The 5G system shall be able to provide the 5G positioning services with a TTFF less than 30 s and, for some 5G positioning services, shall support mechanisms to provide a TTFF less than 10 s. NOTE 1: In some services, a TTFF of less than 10s can only be achievable at the expense of a relaxation of some other performances (e.g. horizontal accuracy can be 1 m or 3 m after 10 s TTFF, and reach a steady state accuracy of 0,3 m after 30 s). The 5G system shall support a mechanism to determine the UE's velocity with a positioning service availability of 99%, an accuracy better than 0,5 m/s for the speed and an accuracy better than 5 degree for the 3-Dimension direction of travel. The 5G system shall support a mechanism to determine the UE's heading with an accuracy better than 30 degrees (0,54 rad) and a positioning service availability of 99,9 % for static users and with an accuracy better than 10 degrees (0,17 rad) and a positioning service availability of 99 % for users up to 10 km/h. For power consumption aspects for various usage scenarios see TS 22.104[ Service requirements for cyber-physical control applications in vertical domains ] [21] Low power high accuary positioning use cases and example scenarios for Industrial IoT devices can be found in 3GPP TS 22.104[ Service requirements for cyber-physical control applications in vertical domains ] [21]. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 7.3.2.3 |
6,428 | 6.6.2.3 Remote UE report procedure accepted by the network | Upon receipt of the REMOTE UE REPORT message, the SMF shall send a REMOTE UE REPORT RESPONSE message to the UE. The SMF shall include the PTI from the REMOTE UE REPORT message. The SMF shall set the EAP message IE to an EAP-success message or an EAP-failure message to be sent to the 5G ProSe layer-3 remote UE if the EAP-success message or the EAP-failure message is received from the DN. Upon receipt of the REMOTE UE REPORT RESPONSE message, the UE shall stop timer T3586 and enter the state PROCEDURE TRANSACTION INACTIVE. | 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.6.2.3 |
6,429 | 4.5.2 Session Management Subscriber Data Update Notification to SMF | Whenever the session management subscriber data is changed for a user in the UDM/UDR and if the SMF subscribed for the update of the session management subscriber data to be notified, the UDM shall notify these changes to the affected SMF by the means of invoking Nudm_SDM_Notification service operation. Then the SMF modifies the session management subscriber data in the UE SM context. The Nudm_SDM_Notification service operation specified in clause 5.2.3.3 is used by the UDM to update session management subscriber data stored in the SMF. The SMF initiates appropriate action according to the changed subscriber data, e.g. including: - initiating an SMF initiated PDU Session Modification procedure; or - initiating an SMF initiated PDU Session Release procedure. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.5.2 |
6,430 | 13.2.4.4 Protection using JSON Web Encryption (JWE) 13.2.4.4.0 General | The SEPP shall use JSON Web Encryption (JWE) as specified in RFC 7516 [59] for the protection of reformatted HTTP messages between the SEPPs. All encryption methods supported by JWE are AEAD methods, i.e. methods that encrypt and integrity protect in one single operation and can additionally integrity protect additional data. The dataToIntegrityProtectAndCipher and dataToIntegrityProtect blocks shall be input to JWE as plaintext and JWE Additional Authenticated Data (AAD) respectively. The JWE AEAD algorithm generates JWE encrypted text (ciphertext) and a JWE Authentication Tag (Message Authentication Code). The ciphertext is the output from symmetrically encrypting the plaintext, while the authentication tag is a value that verifies the integrity of both the generated ciphertext and the Additional Authenticated Data. The Flattened JWE JSON Serialization syntax shall be used to represent JWE as a JSON object. The session key shared between the two SEPPs, as specified in clause 13.2.4.4.1, shall be used as the Content Encryption Key (CEK) value to the algorithm indicated in the Encryption algorithm ("enc") parameter in the JOSE header. The algorithm ("alg") parameter in the JOSE header denoting the key exchange method shall be set to "dir", i.e. "Direct use of a shared symmetric key as the CEK". The 3GPP profile for supported cipher suites in the "enc" parameter is described in clause 13.2.4.9. The generated JWE object shall be transmitted on the N32-f interface in the payload body of a SEPP to SEPP HTTP/2 message. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 13.2.4.4 |
6,431 | 5.3.13.1a Conditions for resuming RRC Connection for NR sidelink communication/discovery/V2X sidelink communication | For NR sidelink communication/discovery an RRC connection is resumed only in the following cases: 1> if configured by upper layers to transmit NR sidelink communication and related data is available for transmission: 2> if the frequency on which the UE is configured to transmit NR sidelink communication is included in sl-FreqInfoList/sl-FreqInfoListSizeExt within SIB12 provided by the cell on which the UE camps; and if the valid version of SIB12 does not include sl-TxPoolSelectedNormal for the concerned frequency; 1> if configured by upper layers to transmit NR sidelink discovery and related data is available for transmission: 2> if the UE is configured by upper layers to transmit NR sidelink L2 U2N relay discovery messages and sl-L2U2N-Relay is included in SIB12; or 2> if the UE is configured by upper layers to transmit NR sidelink L3 U2N relay discovery messages and sl-L3U2N-RelayDiscovery is included in SIB12; or 2> if the UE is configured by upper layers to transmit NR sidelink non-relay discovery messages and sl-NonRelayDiscovery is included in SIB12: 3> if the frequency on which the UE is configured to transmit NR sidelink discovery is included in sl-FreqInfoList/sl-FreqInfoListSizeExt within SIB12 provided by the cell on which the UE camps; and if the valid version of SIB12 does not include sl-DiscTxPoolSelected or sl-TxPoolSelectedNormal for the concerned frequency; For L2 U2N Relay UE in RRC_INACTIVE, an RRC connection establishment is resumed in the following cases: 1> if any message is received from the L2 U2N Remote UE via SL-RLC0 as specified in 9.1.1.4 or SL-RLC1 as specified in 9.2.4; or 1> if RemoteUEInformationSidelink containing the connectionForMP is received from a L2 U2N Remote UE as specified in 5.8.9.8.3; For V2X sidelink communication an RRC connection resume is initiated only when the conditions specified for V2X sidelink communication in clause 5.3.3.1a of TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10] are met. NOTE: Upper layers initiate an RRC connection resume (except if the RRC connection resume is initiated at the L2 U2N Relay UE upon reception of a message from a L2 U2N Remote UE via SL-RLC0 or SL-RLC1). The interaction with NAS is left to UE implementation. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.13.1a |
6,432 | 5.10.3 UE or MME requested PDN disconnection | The UE or MME requested PDN disconnection procedure for an E-UTRAN is depicted in figure 5.10.3-1. The procedure allows the UE to request for disconnection from one PDN. Bearers including the default bearer of this PDN shall be deleted during this procedure. The procedure also allows the MME to initiate the release of a PDN connection. This procedure is also used as part of the SIPTO function when the MME determines that GW relocation is desirable. In this situation the MME deactivates the PDN connection(s) relevant to SIPTO-allowed APN(s) using the "reactivation requested" cause value, and the UE should then re-establish those PDN connection(s). NOTE 1: The deactivation with reactivation requested does not work with pre-Rel-9 LTE UEs. It shall be possible to configure the MME to deactivate a PDN connection, for PDN GW relocation due to SIPTO above RAN, only when UE is in ECM-IDLE mode or during a Tracking Area Update procedure without established RAB(s). This procedure is not used to terminate the last PDN connection unless "Attach without PDN Connectivity is supported" in the Preferred Network behaviour indicated by the UE at attach time is supported by the network and the UE at any time it requires the last PDN connection to be disconnected. The UE uses the UE-initiated Detach procedure in clause 5.3.8.2 to disconnect the last PDN connection. The MME uses the MME-initiated Detach procedure in clause 5.3.8.3 to release the last PDN connection. Figure 5.10.3-1: UE or MME requested PDN disconnection NOTE 2: For a PMIP-based S5/S8, procedure steps (A) are defined in TS 23.402[ Architecture enhancements for non-3GPP accesses ] [2]. Steps 3, 4 and 5 concern GTP based S5/S8. NOTE 3: If after step 6, the MME determines that PDN being disconnected has no active bearers in the E-UTRAN, (e.g. because data is transported using Control Plane CIoT EPS Optimisation) steps 7, 8. 10a and 10b are modified to only transfer the indicated ESM signalling messages and steps 9a and 9b are skipped. 1. The procedure is triggered by either step 1a or step 1b. 1a. The UE initiates the UE requested PDN disconnection procedure by the transmission of a PDN Disconnection Request (LBI) message. The LBI indicates the default bearer associated with the PDN connection being disconnected. If the UE was in ECM-IDLE mode, this NAS message is preceded by the Service Request procedure if any of the exiting PDN connections were using the User Plane without CIoT EPS Optimisation, or, if the user plane was used just with User Plane CIoT EPS Optimisations, a Resume Procedure is executed instead. 1b. The MME decides to release the PDN connection. This may be e.g. due to change of subscription, lack of resources, due to SIPTO if the PDN connection serves a SIPTO-allowed APN or on receiving a PDN GW Restart Notification from the Serving GW as specified in TS 23.007[ Restoration procedures ] [72]. If the UE is in ECM-IDLE state and the reason for releasing PDN connection is "reactivation requested" e.g. due to SIPTO, the MME initiates paging via Network Triggered Service Request procedure in clause 5.3.4.3 from step 3a onwards in order to inform UE of the request. 2. If the PLMN has configured secondary RAT usage reporting, the MME shall perform step 7 through 10 before step 2 onwards. If the PDN connection was served by a P-GW, the EPS Bearers in the Serving GW for the particular PDN connection are deactivated by the MME by sending Delete Session Request (Cause, LBI, User Location Information (ECGI), Secondary RAT usage data) to the Serving GW. This message indicates that all bearers belonging to that PDN connection shall be released. If the UE Time Zone has changed, the MME includes the UE Time Zone IE in this message. For PDN connection to the SCEF the MME indicates to the SCEF the connection for the UE is no longer available according to TS 23.682[ Architecture enhancements to facilitate communications with packet data networks and applications ] [74] and steps 2,3,4,5,6 are not executed. If the MME received Secondary RAT usage data in step 9b, the MME shall include it in this Delete Session Request message. 3. The Serving GW sends Delete Session Request (Cause, LBI, User Location Information (ECGI), Secondary RAT usage data) to the PDN GW. The S-GW also includes User Location Information IE and/or UE Time Zone IE if it is present in step 2. The Serving GW also includes the Secondary RAT usage data in this message if it was present in step 2 and if PDN GW secondary RAT usage data reporting is active. 4. The PDN GW acknowledges with Delete Session Response (optionally, APN Rate Control Status). 5. The PDN GW employs the PCEF-initiated IP-CAN Session Termination procedure as defined in TS 23.203[ Policy and charging control architecture ] [6] to indicate to the PCRF that the IP-CAN session is released if PCRF is applied in the network. If requested the PDN GW indicates User Location Information and/or UE Time Zone Information to the PCRF as defined in TS 23.203[ Policy and charging control architecture ] [6]. 6. The Serving GW acknowledges with Delete Session Response (optionally, APN Rate Control Status). If received, the MME stores the APN Rate Control Status in the MM context. 7. If the UE is in ECM IDLE state and the PDN disconnection is decided by the MME, the MME shall delete the corresponding contexts of the PDN connection locally, steps 7 to 10b are skipped except if the MME has decided to restore certain PDN connections as specified in TS 23.007[ Restoration procedures ] [72] or for other reasons e.g. SIPTO. The MME initiates the deactivation of all Radio Bearers associated with the PDN connection to the eNodeB by sending the Deactivate Bearer Request message to the eNodeB. The MME shall re-calculate the UE-AMBR (see clause 4.7.3). This S1-AP message carries the list of EPS bearers to be released, the new UE-AMBR, and a NAS Deactivate EPS Bearer Context Request (LBI) message. The MME builds a NAS message Deactivate EPS Bearer Context Request including the EPS Bearer Identity, and includes it in the S1-AP Deactivate Bearer Request message. If the network wants to trigger GW relocation (e.g. for SIPTO), the NAS message Deactivate EPS Bearer Context Request includes the request for reactivation of the same PDN connection via the same APN by the UE. If the MME released the PDN connection due to failed bearer set up during handover, the UE and the MME deactivate the failed contexts locally without peer-to peer ESM signalling. NOTE 4: If the UE is in ECM-IDLE state and the PDN disconnection is decided by the MME, the EPS bearer state is synchronized between the UE and the network at the next ECM-IDLE to ECM-CONNECTED transition (e.g. Service Request or TAU procedure). 8. The eNodeB sends the RRC Connection Reconfiguration message including the corresponding bearers to be released and the NAS Deactivate EPS Bearer Context Request (LBI) message to the UE. 9a. The UE releases all resources corresponding to the PDN connection and acknowledges this by sending the RRC Connection Reconfiguration Complete message to the eNodeB. 9b. The eNodeB sends an acknowledgement of the deactivation to the MME. If the PLMN has configured secondary RAT usage reporting and the eNodeB has Secondary RAT usage data to report, the Secondary RAT usage data is included. 10a. The UE NAS layer builds a Deactivate EPS Bearer Context Accept message. The UE then sends a Direct Transfer (Deactivate EPS Bearer Context Accept) message to the eNodeB. If the Deactivate EPS Bearer Context Request message from the MME indicated reactivation requested, the UE starts the UE initiated PDN connection request procedure as specified in clause 5.10.2 by using the same APN of the released PDN connection. 10b. The eNodeB sends an Uplink NAS Transport (Deactivate EPS Bearer Context Accept) message to the MME. The MME determines the Maximum APN Restriction for the remaining PDN connections and stores this new value for the Maximum APN Restriction. | 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.10.3 |
6,433 | 8.3.1.1E Enhanced Performance Requirement Type B – Single-layer Spatial Multiplexing with TM3 interference model | The requirements are specified in Table 8.3.1.1E-2, with the addition of the parameters in Table 8.3.1.1E-1 and the downlink physical channel setup according to Annex C.3.2. The purpose of these tests is to verify closed loop rank one performance on one of the antenna ports 7 or 8 without a simultaneous transmission on the other antenna port in the serving cell when the PDSCH transmission in the serving cell is interfered by PDSCH of two interfering cells applying transmission mode 3 interference model defined in clause B.6.2. In 8.3.1.1E-1, Cell 1 is the serving cell, and Cell 2, 3 are interfering cells. The downlink physical channel setup is according to Annex C.3.2 for each of Cell 1, Cell 2 and Cell 3, respectively. Table 8.3.1.1E-1: Test Parameters for Testing CDM-multiplexed DM RS (Single-layer) with TM3 interference model Table 8.3.1.1E-2: Minimum Performance for Enhanced Performance Requirement Type B, CDM-multiplexed DM RS with TM3 interference model | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.3.1.1E |
6,434 | 4.7.7.3a 128-bit packet-switched GSM ciphering key | The ME and the network may derive and store a 128-bit packet-switched GSM key or GPRS GSM Kc128 from an established UMTS security context. If the GPRS GSM Kc128 exits, then it is also part of the UMTS security context. The ME with a USIM in use shall compute a new GPRS GSM Kc128 using the GPRS UMTS ciphering key and the GPRS UMTS integrity key from an established UMTS security context as specified in 3GPP TS 33.102[ 3G security; Security architecture ] [5a]. The new GPRS GSM Kc128 shall be stored only in the ME. The ME shall overwrite the existing GPRS GSM Kc128 with the new GPRS GSM Kc128. The ME shall delete the GPRS GSM Kc128 at switch off, when the USIM is disabled as well as under the conditions identified in the subclause 4.1.3.2 and 4.7.7.4. The ME with a USIM in use shall apply the GPRS GSM Kc128 when in A/Gb mode a GEA ciphering algorithm that requires a 128-bit ciphering key is taken into use. The network shall compute the GPRS GSM Kc128 using the GPRS UMTS integrity key and the GPRS UMTS ciphering key from an established UMTS security context as specified in 3GPP TS 33.102[ 3G security; Security architecture ] [5a] only when in A/Gb mode a GEA ciphering algorithm that requires a 128-bit ciphering key is to be used. In A/Gb mode, if the MS supports integrity protection, the information in the Ciphering Algorithm IE together with the IMSI from the USIM shall be stored in a non-volatile memory in the ME at MS power off. The information stored in the Ciphering Algorithm IE can only be used if the IMSI from the USIM matches the IMSI stored in the ME non-volatile memory at MS power on; otherwise the MS shall delete the Ciphering Algorithm IE. | 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.7.3a |
6,435 | – CA-ParametersEUTRA | The IE CA-ParametersEUTRA contains the E-UTRA part of band combination parameters for a given MR-DC band combination. NOTE: If additional E-UTRA band combination parameters are defined in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10], which are supported for MR-DC, they will be defined here as well. CA-ParametersEUTRA information element -- ASN1START -- TAG-CA-PARAMETERSEUTRA-START CA-ParametersEUTRA ::= SEQUENCE { multipleTimingAdvance ENUMERATED {supported} OPTIONAL, simultaneousRx-Tx ENUMERATED {supported} OPTIONAL, supportedNAICS-2CRS-AP BIT STRING (SIZE (1..8)) OPTIONAL, additionalRx-Tx-PerformanceReq ENUMERATED {supported} OPTIONAL, ue-CA-PowerClass-N ENUMERATED {class2} OPTIONAL, supportedBandwidthCombinationSetEUTRA-v1530 BIT STRING (SIZE (1..32)) OPTIONAL, ... } CA-ParametersEUTRA-v1560 ::= SEQUENCE { fd-MIMO-TotalWeightedLayers INTEGER (2..128) OPTIONAL } CA-ParametersEUTRA-v1570 ::= SEQUENCE { dl-1024QAM-TotalWeightedLayers INTEGER (0..10) OPTIONAL } -- TAG-CA-PARAMETERSEUTRA-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
6,436 | 5.9 MAC Reset | If a reset of the MAC entity is requested by upper layers, the MAC entity shall: - initialize Bj for each logical channel to zero; - except for pur-TimeAlignmentTimer, if configured, stop (if running) all timers; - except for pur-TimeAlignmentTimer, if configured, consider all timeAlignmentTimers as expired and perform the corresponding actions in clause 5.2; - set the NDIs for all uplink HARQ processes to the value 0; - stop, if any, ongoing RACH procedure; - discard explicitly signalled ra-PreambleIndex and ra-PRACH-MaskIndex, if any; - flush Msg3 buffer; - cancel, if any, triggered Scheduling Request procedure; - cancel, if any, triggered Buffer Status Reporting procedure; - cancel, if any, triggered Power Headroom Reporting procedure; - cancel, if any, triggered Recommended bit rate query procedure; - cancel, if any, triggered Timing Advance Reporting procedure; - flush the soft buffers for all DL HARQ processes; - for each DL HARQ process, consider the next received transmission for a TB as the very first transmission; - release, if any, Temporary C-RNTI; - clear, if any, Differential Koffset. If a partial reset of the MAC entity is requested by upper layers, for a serving cell, the MAC entity shall for the serving cell: - set the NDIs for all uplink HARQ processes to the value 0; - flush all UL HARQ buffers; - stop all running drx-ULRetransmissionTimers; - stop all running UL HARQ RTT timers; - stop, if any, ongoing RACH procedure; - discard explicitly signalled ra-PreambleIndex and ra-PRACH-MaskIndex, if any; - flush Msg3 buffer; - release, if any, Temporary C-RNTI. | 3GPP TS 36.321 | Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification | RAN2 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 5.9 |
6,437 | 8.2.1.4.1F Minimum Requirement Single-Layer Spatial Multiplexing 4 Tx Antenna Ports with CRS assistance information | The requirements are specified in Table 8.2.1.4.1F-2, with the addition of parameters in Table 8.2.1.4.1F-1. In Table 8.2.1.4.1F-1, Cell 1 is the serving cell, and Cell 2 and Cell 3 are the aggressor cells. The downlink physical channel setup is according to Annex C.3.2 for each of Cell 1, Cell 2 and Cell 3, respectively. The CRS assistance information [7] is provided to the UE and includes information on Cell 2 and Cell 3. The purpose of the test is to verify the closed loop single layer TM4 performance under assumption that UE applies CRS interference mitigation in the scenario with 4 CRS antenna ports in the serving and aggressor cells. Table 8.2.1.4.1F-1: Test Parameters Table 8.2.1.4.1F-2: Minimum Performance for PDSCH | 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.4.1F |
6,438 | 5.6.4.2 UE initiated generic transport of NAS messages | Upon request from an application to send a message encapsulated in the generic transport of NAS message, the EMM entity in the UE initiates the procedure by sending an UPLINK GENERIC NAS TRANSPORT message including the corresponding message in the generic message container IE. The application may also request additional information to be included in the UPLINK GENERIC NAS TRANSPORT message in the Additional information IE. The content, coding and interpretation of this information element are dependent on the particular application. The UE shall indicate the application protocol using the generic transport in the corresponding generic message container type. When receiving the UPLINK GENERIC NAS TRANSPORT message, the EMM entity in the MME shall provide the contents of the generic message container IE and the generic message container type IE to the corresponding application. If included, the EMM entity in the MME shall also provide the contents of the Additional information 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 | 5.6.4.2 |
6,439 | 17.2.1 Home network realm | The home network realm shall be in the form of an Internet domain name, e.g. operator.com, as specified in IETF RFC 1035 [19] and IETF RFC 1123 [20]. The home network realm consists of one or more labels. Each label shall consist of the alphabetic characters (A-Z and a-z), digits (0-9) and the hyphen (-) in accordance with IETF RFC 1035 [19]. Each label shall begin and end with either an alphabetic character or a digit in accordance with IETF RFC 1123 [20]. The case of alphabetic characters is not significant. The UE shall derive the home network realm from the IMSI as described in the following steps: 1. take the first 5 or 6 digits, depending on whether a 2 or 3 digit MNC is used (see 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [27], 3GPP TS 51.011[ Specification of the Subscriber Identity Module - Mobile Equipment (SIM-ME) interface ] [66]) and separate them into MCC and MNC; if the MNC is 2 digits then a zero shall be added at the beginning; 2. use the MCC and MNC derived in step 1 to create the "mnc<MNC>.mcc<MCC>.3gppnetwork.org" network realm; 3. add the label "gan." to the beginning of the network realm. An example of a home network realm is: IMSI in use: 234150999999999; Where: MCC = 234; MNC = 15; MSIN = 0999999999, Which gives the home network realm: gan.mnc015.mcc234.3gppnetwork.org. NOTE: If it is not possible for the UE to identify whether a 2 or 3 digit MNC is used (e.g. SIM is inserted and the length of MNC in the IMSI is not available in the "Administrative data" data file), it is implementation dependent how the UE determines the length of the MNC (2 or 3 digits). | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 17.2.1 |
6,440 | 28.4.4 Network Slice Instance Identifier (NSI ID) | A Network Slice Instance Identifier (NSI ID) uniquely identifies a Network Slice Instance (NSI) within a PLMN or SNPN, when multiple NSIs of a same Network Slice are deployed and there is a need to differentiate between them in the 5GC. See 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [119] for the definition of the Network Slice Instance. An NSI may be associated with one or more S-NSSAIs, and an S-NSSAI may be associated with one or more NSIs. The NSI ID is defined as an operator specific string (see clause 6.1.6.2.2 of 3GPP TS 29.510[ 5G System; Network function repository services; Stage 3 ] [130]). | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 28.4.4 |
6,441 | 13.3 SCG UE history information | The MN stores and correlates the UE History Information from MN and SN(s) as long as the UE stays in MR-DC, forwards UE History Information and optional UE History Information from the UE to its connected SNs. The resulting information is then used by SN for dual-connectivity operation. The SN is in charge of collecting SCG UE history information and providing the collected information to the MN. If the UE stays in a PSCell for a duration exceeding the maximum value of the Time Stay parameter, the SN may store the PSCell information with consecutive entries using the same PSCell identity. The total stay time in this PSCell is the sum of stay time for all consecutive PSCell with the same identity. The SN shall provide the collected SCG UE history information, if available, to the MN in the following procedures: - the SN Release, and SN initiated SN Change procedures - the MN initiated SN Modification procedure if requested by the MN in this procedure - the SN initiated SN modification procedure upon PSCell change if subscribed in the SN Addition procedure When the target NG-RAN node receives the SCG UHI from the source NG-RAN node via Handover Request message for CHO, the target NG-RAN node updates the time UE stayed in cell of the latest PSCell entry (i.e. the source PSCell) when the UE successfully accesses to a candidate cell of the target NG-RAN node. The updated value of the time UE stayed in the source PSCell is equal to the value received from the source NG-RAN node during the Handover Preparation plus the time from receiving Handover Request message from the source NG-RAN node to receiving RRC Reconfiguration Complete message from the UE. When the target SN receives the SCG UHI from the MN via SN Addition Request message for CPC, the target SN updates the time UE stayed in the cell of the latest PSCell entry (i.e. the source PSCell) when the UE successfully accesses to a candidate cell of the target SN. The updated value of the time UE stayed in the latest PSCell is equal to the value received from the MN via the SN Addition Request message plus the time from receiving SN Addition Request message from the MN to receiving SN Reconfiguration Complete from the MN. | 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.3 |
6,442 | 5.4.2.7 Abnormal cases | a) Lower layer failure: Upon detection of lower layer failure before the AUTHENTICATION RESPONSE message is received, the network shall abort the procedure. b) Expiry of timer T3460: The network shall, on the first expiry of the timer T3460, retransmit the AUTHENTICATION REQUEST message and shall reset and start timer T3460. This retransmission is repeated four times, i.e. on the fifth expiry of timer T3460, the network shall abort the authentication procedure and any ongoing EMM specific procedure and release the NAS signalling connection. c) Authentication failure (EMM cause #20 "MAC failure"): The UE shall send an AUTHENTICATION FAILURE message, with EMM cause #20 "MAC failure" according to clause 5.4.2.6, to the network and start timer T3418 (see example in figure 5.4.2.7.1). Furthermore, the UE shall stop any of the retransmission timers that are running (e.g. T3410, T3417, T3421 or T3430). Upon the first receipt of an AUTHENTICATION FAILURE message from the UE with EMM cause #20 "MAC failure", the network may initiate the identification procedure described in clause 5.4.4. This is to allow the network to obtain the IMSI from the UE. The network may then check that the GUTI originally used in the authentication challenge corresponded to the correct IMSI. Upon receipt of the IDENTITY REQUEST message from the network, the UE shall send the IDENTITY RESPONSE message. NOTE 1: Upon receipt of an AUTHENTICATION FAILURE message from the UE with EMM cause #20 "MAC failure", the network may also terminate the authentication procedure (see clause 5.4.2.5). If the GUTI/IMSI mapping in the network was incorrect, the network should respond by sending a new AUTHENTICATION REQUEST message to the UE. Upon receiving the new AUTHENTICATION REQUEST message from the network, the UE shall stop the timer T3418, if running, and then process the challenge information as normal. If the GUTI/IMSI mapping in the network was correct, the network should terminate the authentication procedure by sending an AUTHENTICATION REJECT message (see clause 5.4.2.5). If the network is validated successfully (an AUTHENTICATION REQUEST message that contains a valid SQN and MAC is received), the UE shall send the AUTHENTICATION RESPONSE message to the network and shall start any retransmission timers (e.g. T3410, T3417, T3421 or T3430) if they were running and stopped when the UE received the first failed AUTHENTICATION REQUEST message. If the UE receives the second AUTHENTICATION REQUEST message while T3418 is running, and the MAC value cannot be resolved, the UE shall follow the procedure specified in this clause, item c, starting again from the beginning, or if the message contains a UMTS authentication challenge, the UE shall follow the procedure specified in item d. If the SQN is invalid, the UE shall proceed as specified in item e. Figure 5.4.2.7.1: Authentication failure procedure (EMM cause #20 "MAC failure" or #26 "non-EPS authentication unacceptable") d) Authentication failure (EMM cause #26 "non-EPS authentication unacceptable"): The UE shall send an AUTHENTICATION FAILURE message, with EMM cause #26 "non-EPS authentication unacceptable", to the network and start the timer T3418 (see example in figure 5.4.2.7.1). Furthermore, the UE shall stop any of the retransmission timers that are running (e.g. T3410, T3417, T3421 or T3430). Upon the first receipt of an AUTHENTICATION FAILURE message from the UE with EMM cause #26 "non-EPS authentication unacceptable", the network may initiate the identification procedure described in clause 5.4.4. This is to allow the network to obtain the IMSI from the UE. The network may then check that the GUTI originally used in the authentication challenge corresponded to the correct IMSI. Upon receipt of the IDENTITY REQUEST message from the network, the UE shall send the IDENTITY RESPONSE message. NOTE 2: Upon receipt of an AUTHENTICATION FAILURE message from the UE with EMM cause #26 "non-EPS authentication unacceptable", the network may also terminate the authentication procedure (see clause 5.4.2.5). If the GUTI/IMSI mapping in the network was incorrect, the network should respond by sending a new AUTHENTICATION REQUEST message to the UE. Upon receiving the new AUTHENTICATION REQUEST message from the network, the UE shall stop the timer T3418, if running, and then process the challenge information as normal. If the GUTI/IMSI mapping in the network was correct, the network should terminate the authentication procedure by sending an AUTHENTICATION REJECT message (see clause 5.4.2.5). e) Authentication failure (EMM cause #21 "synch failure"): The UE shall send an AUTHENTICATION FAILURE message, with EMM cause #21 "synch failure", to the network and start the timer T3420 (see example in figure 5.4.2.7.2). Furthermore, the UE shall stop any of the retransmission timers that are running (e.g. T3410, T3417, T3421 or T3430). Upon the first receipt of an AUTHENTICATION FAILURE message from the UE with the EMM cause #21 "synch failure", the network shall use the returned AUTS parameter from the authentication failure parameter IE in the AUTHENTICATION FAILURE message, to re-synchronise. The re-synchronisation procedure requires the MME to delete all unused authentication vectors for that IMSI and obtain new vectors from the HSS. When re-synchronisation is complete, the network shall initiate the authentication procedure. Upon receipt of the AUTHENTICATION REQUEST message, the UE shall stop the timer T3420, if running. NOTE 3: Upon receipt of two consecutive AUTHENTICATION FAILURE messages from the UE with EMM cause #21 "synch failure", the network may terminate the authentication procedure by sending an AUTHENTICATION REJECT message. If the network is validated successfully (a new AUTHENTICATION REQUEST message is received which contains a valid SQN and MAC) while T3420 is running, the UE shall send the AUTHENTICATION RESPONSE message to the network and shall start any retransmission timers (e.g. T3410, T3417, T3421 or T3430), if they were running and stopped when the UE received the first failed AUTHENTICATION REQUEST message. If the UE receives the second AUTHENTICATION REQUEST message while T3420 is running, and the MAC value cannot be resolved, the UE shall follow the procedure specified in item c or if the message contains a UMTS authentication challenge, the UE shall proceed as specified in item d; if the SQN is invalid, the UE shall follow the procedure specified in this clause, item e, starting again from the beginning. Figure 5.4.2.7.2: Authentication failure procedure (EMM cause #21 "synch failure") Upon receipt of an AUTHENTICATION REJECT message, the UE shall perform the actions as specified in clause 5.4.2.5. f) Network failing the authentication check: If the UE deems that the network has failed the authentication check, then it shall request RRC to locally release the RRC connection and treat the active cell as barred (see 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [21]). The UE shall start any retransmission timers (e.g. T3410, T3417, T3421 or T3430), if they were running and stopped when the UE received the first AUTHENTICATION REQUEST message containing an incorrect authentication challenge data causing the authentication failure. g) Transmission failure of AUTHENTICATION RESPONSE message or AUTHENTICATION FAILURE message indication from lower layers (if the authentication procedure is triggered by a tracking area updating procedure or an attach procedure) The UE shall stop any of the timers T3418 and T3420, if running, and re-initiate the tracking area updating procedure if the authentication procedure is triggered by a tracking area updating procedure. The UE shall stop any of the timers T3418 and T3420, if running, and re-initiate the attach procedure if the authentication procedure is triggered by an attach procedure. h) Transmission failure of AUTHENTICATION RESPONSE message or AUTHENTICATION FAILURE message indication with TAI change from lower layers (if the authentication procedure is triggered by a service request procedure) The UE shall stop any of the timers T3418 and T3420, if running. If the current TAI is not in the TAI list, the authentication procedure shall be aborted and a tracking area updating procedure shall be initiated. If the current TAI is still part of the TAI list, it is up to the UE implementation how to re-run the ongoing procedure that triggered the authentication procedure. i) Transmission failure of AUTHENTICATION RESPONSE message or AUTHENTICATION FAILURE message indication without TAI change from lower layers (if the authentication procedure is triggered by a service request procedure) The UE shall stop any of the timers T3418 and T3420, if running. It is up to the UE implementation how to re-run the ongoing procedure that triggered the authentication procedure. j) Lower layers indication of non-delivered NAS PDU due to handover If the AUTHENTICATION REQUEST message could not be delivered due to an intra MME handover and the target TA is included in the TAI list, then upon successful completion of the intra MME handover the MME shall retransmit the AUTHENTICATION REQUEST message. If a failure of handover procedure is reported by the lower layer and the S1 signalling connection exists, the MME shall retransmit the AUTHENTICATION REQUEST message. k) Change of cell into a new tracking area If the UE detects the current TAI is not in the TAI list occurs before the AUTHENTICATION RESPONSE message is sent, the UE may discard sending the AUTHENTICATION RESPONSE message to the network and continue with the initiation of tracking area updating procedure as described in clause 5.5.3. l) AUTHENTICATION REJECT message is received without integrity protection and none of the timers T3416, T3418 and T3420 is running If an AUTHENTICATION REJECT message is received and if none of the timers T3416, T3418 and T3420 is running, then the UE shall discard the AUTHENTICATION REJECT message. Additionally, the UE may request RRC to locally release the RRC connection and treat the active cell as barred (see 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [21]). For items c, d, and e if the UE does not have a PDN connection for emergency bearer services established, is not establishing a PDN connection for emergency bearer services, does not have a PDN connection for RLOS established and is not establishing a PDN connection for RLOS: The UE shall stop any of the timers T3418 and T3420, if running, and the UE enters EMM-IDLE mode, e.g. upon detection of a lower layer failure, release of the NAS signalling connection, or as the result of an inter-system handover to A/Gb mode, Iu mode or N1 mode. The UE shall deem that the network has failed the authentication check or that the source of the authentication challenge is not genuine and proceed as described in item f if any of the following occurs: - the timer T3418 or T3420 expires; - the UE detects any combination of the authentication failures: EMM cause #20 "MAC failure", #21 "synch failure", or #26 "non-EPS authentication unacceptable", during three consecutive authentication challenges. The authentication challenges shall be considered as consecutive only if the authentication challenges causing the second and third authentication failure are received by the UE while the timer T3418 or T3420 started after the previous authentication failure is running. For items c, d, and e if the UE has a PDN connection for emergency bearer services established, is establishing a PDN connection for emergency bearer services, has a PDN connection for RLOS established, or is establishing a PDN connection for RLOS: 1) The UE shall stop any of the timers T3418 and T3420, if running, and the UE enters EMM-IDLE mode, e.g. upon detection of a lower layer failure, release of the NAS signalling connection, or as the result of an inter-system handover to A/Gb mode, Iu mode or N1 mode. 2) Depending on local requirements or operator preference for emergency bearer services, if the UE has a PDN connection for emergency bearer services established or is establishing a PDN connection for emergency bearer services, the MME need not follow the procedures specified for the authentication failure specified in the present clause. The MME may respond to the AUTHENTICATION FAILURE message by initiating the security mode control procedure selecting the "null integrity protection algorithm" EIA0, "null ciphering algorithm" EEA0 or may abort the authentication procedure and continue using the current security context, if any. The MME shall deactivate all non-emergency EPS bearer contexts, if any, by initiating an EPS bearer context deactivation procedure. If there is an ongoing PDN connectivity procedure, the MME shall deactivate all non-emergency EPS bearer contexts upon completion of the PDN connectivity procedure. The network shall consider the UE to be attached for emergency bearer services only. If a UE has a PDN connection for emergency bearer services established or is establishing a PDN connection for emergency bearer services and sends an AUTHENTICATION FAILURE message to the MME with the EMM cause appropriate for these cases (#20, #21, or #26, respectively) and receives the SECURITY MODE COMMAND message before the timeout of timer T3418 or T3420, the UE shall deem that the network has passed the authentication check successfully, stop timer T3418 or T3420, respectively, and execute the security mode control procedure. If a UE has a PDN connection for emergency bearer services established or is establishing a PDN connection for emergency bearer services when timer T3418 or T3420 expires, the UE shall not deem that the network has failed the authentication check and not behave as described in item f. Instead the UE shall continue using the current security context, if any, deactivate all non-emergency EPS bearer contexts, if any, by initiating UE requested PDN disconnect procedure. If there is an ongoing PDN connectivity procedure, the UE shall deactivate all non-emergency EPS bearer contexts upon completion of the PDN connectivity procedure. The UE shall start any retransmission timers (e.g. T3410, T3417, T3421 or T3430) if: - they were running and stopped when the UE received the AUTHENTICATION REQUEST message and detected an authentication failure; and - the procedures associated with these timers have not yet been completed. The UE shall consider itself to be attached for emergency bearer services only. 3) Depending on local regulation and operator policy, if the UE has a PDN connection for RLOS established or is establishing a PDN connection for RLOS, the MME need not follow the procedures specified for the authentication failure specified in the present clause. The MME may respond to the AUTHENTICATION FAILURE message by initiating the security mode control procedure selecting the "null integrity protection algorithm" EIA0, "null ciphering algorithm" EEA0 or may abort the authentication procedure and continue using the current security context, if any. The network shall consider the UE to be attached for access to RLOS. If a UE has a PDN connection for RLOS established or is establishing a PDN connection for RLOS and sends an AUTHENTICATION FAILURE message to the MME with the EMM cause appropriate for these cases (#20, #21, or #26, respectively) and receives the SECURITY MODE COMMAND message before the timeout of timer T3418 or T3420, the UE shall deem that the network has passed the authentication check successfully, stop timer T3418 or T3420, respectively, and execute the security mode control procedure. If a UE has a PDN connection for RLOS established or is establishing a PDN connection for RLOS when timer T3418 or T3420 expires, the UE shall not deem that the network has failed the authentication check and not behave as described in item f. Instead the UE shall continue using the current security context, if any. The UE shall start any retransmission timers (e.g. T3410, T3417, T3421 or T3430) if: - they were running and stopped when the UE received the AUTHENTICATION REQUEST message and detected an authentication failure; and - the procedures associated with these timers have not yet been completed. The UE shall consider itself to be attached for access to RLOS. | 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.2.7 |
6,443 | A.3.3 Message definition | Each PDU (message) type is specified in an ASN.1 clause similar to the one shown in the example below. -- /example/ ASN1START RRCConnectionReconfiguration ::= SEQUENCE { rrc-TransactionIdentifier RRC-TransactionIdentifier, criticalExtensions CHOICE { c1 CHOICE{ rrcConnectionReconfiguration-r8 RRCConnectionReconfiguration-r8-IEs, spare3 NULL, spare2 NULL, spare1 NULL }, criticalExtensionsFuture SEQUENCE {} } } RRCConnectionReconfiguration-r8-IEs ::= SEQUENCE { -- Enter the IEs here. ... } -- ASN1STOP Hooks for critical and non-critical extension should normally be included in the PDU type specification. How these hooks are used is further described in clause A.4. Critical extensions are characterised by a redefinition of the PDU contents and need to be governed by a mechanism for protocol version agreement between the encoder and the decoder of the PDU, such that the encoder is prevented from sending a critically extended version of the PDU type, which is not comprehended by the decoder. Critical extension of a PDU type is facilitated by a two-level CHOICE structure, where the alternative PDU contents are alternatives within the inner level c1 CHOICE. Spare alternatives (i.e., spare3 down to spare1 in this case) may be included within the c1 CHOICE. The number of spare alternatives to be included in the original PDU specification should be decided case by case, based on the expected rate of critical extension in the future releases of the protocol. Further critical extension, when the spare alternatives from the original specifications are used up, is facilitated using the criticalExtensionsFuture in the outer level CHOICE. In PDU types where critical extension is not expected in the future releases of the protocol, the inner level c1 CHOICE and the spare alternatives may be excluded, as shown in the example below. -- /example/ ASN1START RRCConnectionReconfigurationComplete ::= SEQUENCE { rrc-TransactionIdentifier RRC-TransactionIdentifier, criticalExtensions CHOICE { rrcConnectionReconfigurationComplete-r8 RRCConnectionReconfigurationComplete-r8-IEs, criticalExtensionsFuture SEQUENCE {} } } RRCConnectionReconfigurationComplete-r8-IEs ::= SEQUENCE { -- Enter the fields here. ... } -- ASN1STOP Non-critical extensions are characterised by the addition of new information to the original specification of the PDU type. If not comprehended, a non-critical extension may be skipped by the decoder, whilst the decoder is still able to complete the decoding of the comprehended parts of the PDU contents. Non-critical extensions at locations other than the end of the message or other than at the end of a field contained in a BIT or OCTET STRING are facilitated by use of the ASN.1 extension marker "...". The original specification of a PDU type should normally include the extension marker at the end of the sequence of information elements contained. Non-critical extensions at the end of the message or at the end of a field that is contained in a BIT or OCTET STRING may be facilitated by use of an empty sequence that is marked OPTIONAL e.g. as shown in the following example: -- /example/ ASN1START RRCMessage-r8-IEs ::= SEQUENCE { field1 InformationElement1, field2 InformationElement2, nonCriticalExtension SEQUENCE {} OPTIONAL } -- ASN1STOP The ASN.1 clause specifying the contents of a PDU type may be followed by a field description table where a further description of, e.g., the semantic properties of the fields may be included. The general format of this table is shown in the example below. The field description table is absent in case there are no fields for which further description needs to be provided e.g. because the PDU does not include any fields, or because an IE is defined for each field while there is nothing specific regarding the use of this IE that needs to be specified. The field description table has one column. The header row shall contain the ASN.1 type identifier of the PDU type. The following rows are used to provide field descriptions. Each row shall include a first paragraph with a field identifier (in bold and italic font style) referring to the part of the PDU to which it applies. The following paragraphs at the same row may include (in regular font style), e.g., semantic description, references to other specifications and/or specification of value units, which are relevant for the particular part of the PDU. The parts of the PDU contents that do not require a field description shall be omitted from the field description table. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | A.3.3 |
6,444 | 5.2.3.2.1 NORMAL-SERVICE | The UE: - shall initiate normal and combined tracking area updating (according to conditions given in clause 5.5.3); - shall perform periodic tracking area updating (see clause 5.5.3) except when attached for emergency bearer services (see clause 5.3.5); - shall initiate a tracking area updating on the expiry of timer T3411; - shall respond to paging; and NOTE: As an implementation option, the MUSIM UE is allowed to not respond to paging based on the information available in the paging message, e.g. voice service indication. - if configured for eCall only mode as specified in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [17], shall perform the eCall inactivity procedure at expiry of timer T3444 or T3445 (see clause 5.5.4). | 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.2.3.2.1 |
6,445 | 4.11.1.5.4 Session Management | 4.11.1.5.4.1 PDN Connection Request The UE Requested PDN Connectivity Procedure specified in clause 5.10.2 of TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13] is impacted as shown in in Figure 4.11.1.5.4.1-1 when interworking with 5GS is supported. Figure 4.11.1.5.4.1-1: Impacts to UE Requested PDN Connectivity Procedure 1. UE sends a PDN connectivity Request to the MME as specified in Step 1 in clause 5.10.2 of TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13] with the following modification: - If the UE is 5G NAS capable and the Request type is "initial request", the UE shall allocate a PDU Session ID and include it in the PCO. The PDU Session ID shall be unique across all other PDN connections of the UE. 2. The relevant steps of the procedure as specified in the figure above are executed. In step 4 of TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13], IP Session Establishment/Modification procedure is replaced by SM Policy Association Establishment/Modification procedure as specified in clauses 4.16.4 and 4.16.5. 3. Step 6 as specified in clause 5.10.2 of TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13] is executed with the following modification: - If the SMF+PGW-C accepts to provide interworking of the PDN connection with 5GC, the SMF+PGW-C shall allocate 5G QoS parameters corresponding to PDN connection, e.g. Session AMBR, QoS rules and QoS Flow level QoS parameters if needed for the QoS Flow(s) associated with the QoS rule(s) and then include them in PCO. - If the SMF+PGW-C accepts to provide interworking of the PDN connection with 5GC, the SMF+PGW-C shall determine the S-NSSAI associated with the PDN connection based on the operator policy and send the S-NSSAI together with the PLMN ID to the UE in the PCO. - If the SMF+PGW-C accepts to provide interworking of the PDN connection with 5GC the SMF+PGW-C, if Small Data Rate Control is used, provides the Small Data Rate Control parameters to the UE in the PCO. 4. The relevant steps of the procedure as specified in the figure above are executed. 5. Step 8 as specified in clause 5.10.2 of TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13] with the following modification: - If 5G QoS parameters are included in the PCO, the UE shall store them. If 5G QoS parameters are not included in the PCO, the UE shall note that session continuity for this PDN connection on mobility to 5G is not provided by the network. - If the S-NSSAI and the PLMN ID associated with the PDN connection are included in the PCO, the UE shall store them. - If the Small Data Rate Control parameters are included in the PCO, the UE shall store them. 6. The relevant steps of the procedure as specified in the figure above are executed. 4.11.1.5.4.2 UE or MME Requested PDN Disconnection The procedure as specified in clause 5.10.3 of TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13] applies with the following modification: Step 8. (RRC Connection Reconfiguration): On receiving the NAS Deactivate EPS Bearer Context Request(LBI) message, if the UE has mapped 5G parameters for the PDU session, the UE deletes the corresponding mapped 5GS PDU session. In addition if the SMF+PGW-C has registered to HSS+UDM for this PDN connection before, the SMF+PGW-C invokes the Nudm_UECM_Deregistration service operation to notify the UDM to remove the association between the SMF+PGW-C identity and the associated DNN and PDU Session Id as described in the step 12 of clause 4.3.4.2. If there is no PDN connection for the associated (DNN, S-NSSAI) handled by the SMF+PGW-C, the SMF+PGW-C unsubscribes from Session Management Subscription data changes notification with the HSS+UDM by means of the Nudm_SDM_Unsubscribe (SUPI, DNN, S-NSSAI) service operation as described in step 12 of clause 4.3.4.2. 4.11.1.5.4.3 Dedicated Bearer Activation, Bearer Modification and Bearer Deactivation The procedures specified in clauses 5.4.1 through 5.4.5 of TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13] apply with the following modifications: - PCRF initiated IP-CAN Modification in TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13] is replaced with PCF initiated SM Policy Association Modification as specified in clause 4.16.5.2. PCEF initiated IP-CAN Session Modification/Termination TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13] is replaced with SM Policy Association Modification/Termination as specified in clauses 4.16.5 and 4.16.6. - In the step where the PDN-GW sends a Create Bearer Request, i.e.: - Step 2 in clause 5.4.1 of TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13] (Dedicated Bearer Activation). the PCO includes mapped 5GS QoS parameters for the EPS bearer being created. - In the step where the PDN-GW sends an Update Bearer Request, i.e.: - Step 2 in clause 5.4.2.1 of TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13] (PDN GW initiated bearer modification with bearer QoS update). - Step 5 in clause 5.4.2.2 of TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13] (HSS Initiated Subscribed QoS Modification). - Step 2 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] (PDN GW initiated bearer modification without bearer QoS update) if TFT or APN-AMBR is being modified. the PCO includes the modification to the mapped 5GS QoS parameters, if impacted by the modification, corresponding to the EPS bearer being modified. - In the step where the UE receives the NAS Session Management message from the MME which contains the PCO relayed via the MME, i.e.: - Step 5 in clause 5.4.1 of TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13] (Dedicated Bearer Activation). - Step 5 in clause 5.4.2.1 of TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13] (PDN GW initiated bearer modification with bearer QoS update). - Step 5 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] (PDN GW initiated bearer modification without bearer QoS update) if TFT or APN-AMBR is being modified. the UE updates the mapped 5G QoS parameters as included in the PCO from the PDN-GW. - In the step where the UE receives EPS bearer request message, i.e.: - Step 5 in clause 5.4.4.1 of TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13] (PDN GW initiated bearer deactivation). the UE also deletes the mapped 5GS QoS flow and its associated parameter. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.11.1.5.4 |
6,446 | 4.3.1.3.1 Attempted outgoing handovers per handover cause | This measurement provides the number of attempted outgoing handovers per handover cause and LTE target cell specific. CC. Transmission of the RRCConnection reconfiguration message to UE triggering the intra-RAT 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] . In case of CA, this attempted handover is only added to the neighbour cell relation from the source EUTRAN cell, through which the RRCConnectionReconfiguration message is sent to the UE, to the target EUTRAN cell appointed in the “MobilityControlInfo” IE of the RRCConnectionReconfiguration message. The sum of all supported per cause measurements shall equal the total number of outgoing 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.OutAttTarget.Cause where Cause identifies the cause for handover EUtranRelation Valid for packet switched traffic EPS | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.3.1.3.1 |
6,447 | – SlotFormatCombinationsPerCell | The IE SlotFormatCombinationsPerCell is used to configure the SlotFormatCombinations applicable for one serving cell (see TS 38.213[ NR; Physical layer procedures for control ] [13], clause 11.1.1). SlotFormatCombinationsPerCell information element -- ASN1START -- TAG-SLOTFORMATCOMBINATIONSPERCELL-START SlotFormatCombinationsPerCell ::= SEQUENCE { servingCellId ServCellIndex, subcarrierSpacing SubcarrierSpacing, subcarrierSpacing2 SubcarrierSpacing OPTIONAL, -- Need R slotFormatCombinations SEQUENCE (SIZE (1..maxNrofSlotFormatCombinationsPerSet)) OF SlotFormatCombination OPTIONAL, -- Need M positionInDCI INTEGER(0..maxSFI-DCI-PayloadSize-1) OPTIONAL, -- Need M ..., [[ enableConfiguredUL-r16 ENUMERATED {enabled} OPTIONAL -- Need R ]] } SlotFormatCombination ::= SEQUENCE { slotFormatCombinationId SlotFormatCombinationId, slotFormats SEQUENCE (SIZE (1..maxNrofSlotFormatsPerCombination)) OF INTEGER (0..255) } SlotFormatCombinationId ::= INTEGER (0..maxNrofSlotFormatCombinationsPerSet-1) -- TAG-SLOTFORMATCOMBINATIONSPERCELL-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
6,448 | 16.14.3.3 Measurements | The same principle as described in 9.2.4 applies to measurements in NTN unless hereunder specified. The network can configure: - multiple SMTCs in parallel per carrier and for a given set of cells depending on UE capabilities; - measurement gaps based on multiple SMTCs; - assistance information (e.g., ephemeris, Common TA parameters, ) provided in SIB19 for UE to perform measurement on neighbour cells in RRC_IDLE/RRC_INACTIVE/RRC_CONNECTED. NW-controlled adjustment of SMTCs can be based on UE assistance information reported in RRC_CONNECTED. A UE in RRC_IDLE/RRC_INACTIVE can adjust SMTCs based on its location and assistance information in SIB19. UE assistance information consists of the service link propagation delay difference(s) between serving the cell and neighbour cell(s). For a UE in Idle/Inactive mode it's up to UE implementation whether to perform NTN neighbour cell measurements on a cell indicated in SIB3/SIB4 but not included in SIB19. For a UE in Connected mode, it's up to UE implementation whether to perform NTN neighbour cell measurements on a cell included in the measurement configuration but not included in SIB19. UE can perform time-based and location-based measurements on neighbour cells in RRC_IDLE/RRC_INACTIVE: - The timing and location information associated to the serving cell is provided in SIB19; - Timing information refers to the UTC time when the serving cell stops serving the current geographical area; - Location information refers: - In the quasi-Earth fixed cell scenario, to the reference location of the serving cell and a distance threshold to the reference location. - In the Earth moving cell scenario, to the reference location of the serving cell at the epoch time and a distance threshold to the reference location. The time-based measurement initiation may be applicable for the feeder link switchover case for cell (re)selection. Measurement rules for cell re-selection based on timing information and location information are specified in clause 5.2.4.2 in TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [10]. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.14.3.3 |
6,449 | 5.1.3.2.3.9 EMM-DEREGISTERED.eCALL-INACTIVE | The substate EMM-DEREGISTERED.eCALL-INACTIVE is chosen in the UE when: - the UE is configured for eCall only mode as specified in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [17]; - timer T3444 and timer T3445 have expired or are not running; - a PLMN has been selected as specified in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6]; - the UE does not need to perform an eCall over IMS; and - the UE does not need to perform a call to a non-emergency MSISDN or URI for test or terminal reconfiguration service. In this substate, the UE shall not initiate any signalling towards the network, except to originate an eCall over IMS, or a call to a non-emergency MSISDN or URI for test or terminal reconfiguration service. | 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.1.3.2.3.9 |
6,450 | – CSI-ResourcePeriodicityAndOffset | The IE CSI-ResourcePeriodicityAndOffset is used to configure a periodicity and a corresponding offset for periodic and semi-persistent CSI resources, and for periodic and semi-persistent reporting on PUCCH. both, the periodicity and the offset are given in number of slots. The periodicity value slots4 corresponds to 4 slots, value slots5 corresponds to 5 slots, and so on. CSI-ResourcePeriodicityAndOffset information element -- ASN1START -- TAG-CSI-RESOURCEPERIODICITYANDOFFSET-START CSI-ResourcePeriodicityAndOffset ::= CHOICE { slots4 INTEGER (0..3), slots5 INTEGER (0..4), slots8 INTEGER (0..7), slots10 INTEGER (0..9), slots16 INTEGER (0..15), slots20 INTEGER (0..19), slots32 INTEGER (0..31), slots40 INTEGER (0..39), slots64 INTEGER (0..63), slots80 INTEGER (0..79), slots160 INTEGER (0..159), slots320 INTEGER (0..319), slots640 INTEGER (0..639) } -- TAG-CSI-RESOURCEPERIODICITYANDOFFSET-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
6,451 | Annex E (informative): Communication models for NF/NF services interaction E.1 General | This annex provides a high level description of the different communication models that NF and NF services can use to interact which each other. Table E.1-1 summarizes the communication models, their usage and how they relate to the usage of an SCP. Table E.1-1: Communication models for NF/NF services interaction summary Model A - Direct communication without NRF interaction: Neither NRF nor SCP are used. Consumers are configured with producers' "NF profiles" and directly communicate with a producer of their choice. Model B - Direct communication with NRF interaction: Consumers do discovery by querying the NRF. Based on the discovery result, the consumer does the selection. The consumer sends the request to the selected producer. Model C - Indirect communication without delegated discovery: Consumers do discovery by querying the NRF. Based on discovery result, the consumer does the selection of an NF Set or a specific NF instance of NF set. The consumer sends the request to the SCP containing the address of the selected service producer pointing to a NF service instance or a set of NF service instances. In the latter case, the SCP selects an NF Service instance. If possible, the SCP interacts with NRF to get selection parameters such as location, capacity, etc. The SCP routes the request to the selected NF service producer instance. Model D - Indirect communication with delegated discovery: Consumers do not do any discovery or selection. The consumer adds any necessary discovery and selection parameters required to find a suitable producer to the service request. The SCP uses the request address and the discovery and selection parameters in the request message to route the request to a suitable producer instance. The SCP can perform discovery with an NRF and obtain a discovery result. Figure E.1-1 depicts the different communication models. Figure E.1-1: Communication models for NF/NF services interaction | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | Annex |
6,452 | 10.5.4.14 Connected subaddress | The purpose of the connected subaddress information element is to identify a subaddress associated with the connected party of a call. The connected subaddress information element is coded as shown in figure 10.5.100/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The connected subaddress is a type 4 information element with a minimum length of 2 octets and a maximum length of 23 octets. Figure 10.5.100/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] The coding for Type of subaddress, odd/even indicator, and subaddress information is in table 10.5.119/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 10.5.4.14 |
6,453 | B.2.1 APN Rate Control in the PGW | To enable APN rate control it shall be configured in the PGW per APN. The APN rate control parameters, if configured, shall consist of: - the maximum number of DL user data packets per time unit, - the maximum number of UL user data packets per time unit, - an indication whether the UE is allowed to send additional exception reports when the limit for the UL APN rate control has been reached , and - if UE supports it, the maximum number of additional UL exception reports per time unit. Possible time units shall be, minute, hour, day or week. If the UE does not indicate APN rate control support, the GGSN/PGW may refrain from providing APN rate control information to the UE. NOTE 1: The UE indicates support for APN rate control with help of an indicator in the Protocol Configuration Options IE (PCO IE) or the Extended Protocol Configuration Options IE (ePCO IE), see 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [54] or 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [84] for IE definition. The APN rate control indicator within the PCO/ePCO IE is received at IP-CAN session establishment. NOTE 2: The UE and network support of the ePCO IE, is indicated with help of the Indication IE. The ePCO support indication within the Indication IE can be received at IP-CAN session establishment or at IP-CAN session modification. See 3GPP TS 29.274[ 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 ] [81] for IE definition. If the APN rate control is supported by the UE and the Indication IE is received indicating support of ePCO IE at the IP-CAN session establishment request and the PGW supports the ePCO IE, the PGW shall in the reply, if configured for the APN used, include APN UL rate control parameters in the ePCO IE, see 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [54] for IE definition. If the ePCO IE is not supported the PGW shall use the PCO IE. The GGSN shall use the PCO IE. If the APN rate control UL parameter(s) is modified and the ePCO IE is supported, the PGW shall initiate an IP-CAN session modification procedure and include the APN UL rate control parameters in the ePCO IE. If the ePCO IE is not supported the PGW shall use the PCO IE. The GGSN shall use the PCO IE. The GGSN/PGW shall enforce the APN rate control per UE and APN according to the configuration for DL and may enforce APN rate control for UL, e.g. when the PGW have indicated to the UE that the UE is not allowed to send exception reports when the limit for the UL APN rate control has been reached. NOTE 3: The UE locally enforces this uplink APN rate control instruction. The UE considers this APN rate control instruction as valid until it receives a new one from the GGSN/PGW. | 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 | B.2.1 |
6,454 | 9.2.15 Location updating request | This message is sent by the mobile station to the network either to request update of its location file (normal updating or periodic updating) or to request IMSI attach. See table 9.2.17/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Message type: LOCATION UPDATING REQUEST Significance: dual Direction: mobile station to network Table 9.2.17/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : LOCATION UPDATING REQUEST message content NOTE: In A/Gb mode, the maximum number of octets that can be transferred is 20. | 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.2.15 |
6,455 | A.1 Utilization of the BSIC | A BSIC is allocated to each cell. A BSIC can take one of 64 values. In each cell the BSIC is broadcast in each burst sent on the SCH, and is then known by all MSs which synchronise with this cell. The BSIC is used by the MS for several purposes, all aiming at avoiding ambiguity or interference which can arise when an MS in a given position can receive signals from two cells using the same BCCH frequency. Some of the uses of the BSIC relate to cases where the MS is attached to one of the cells. Other uses relate to cases where the MS is attached to a third cell, usually somewhere between the two cells in question. The first category of uses includes: - The three least significant bits of the BSIC indicate which of the 8 training sequences is used in the bursts sent on the downlink common channels of the cell. Different training sequences allow for a better transmission if there is interference. The group of the three least significant bits of the BSIC is called the BCC (Base station Colour Code). - The BSIC is used to modify the bursts sent by the MSs on the access bursts. This aims to avoid one cell correctly decoding access bursts sent to another cell. The second category of uses includes: - When in connected mode, the MSs measure and report the level they receive on a number of frequencies, corresponding to the BCCH frequencies of neighbouring cells in the same network as the used cell. Along with the measurement result, the MS sends to the network the BSIC which it has received on that frequency. This enables the network to discriminate between several cells which happen to use the same BCCH frequency. Poor discrimination might result in faulty handovers. - The content of the measurement report messages is limited to information for 6 neighbour cells. It is therefore useful to limit the reported cells to those to which handovers are accepted. For this purpose, each cell provides a list of the values of the three most significant bits of the BSICs which are allocated to the cells which are useful to consider for handovers (usually excluding cells in other PLMNs). This information enables the MS to discard information for cells with non-conformant BSICs and not to report them. The group of the three most significant bits of the BSIC is called the NCC (Network Colour Code). It should be noted that when in idle mode, the MS identifies a cell (for cell selection purposes) according to the cell identity broadcast on the BCCH and not by the BSIC. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | A.1 |
6,456 | 4.17 5GS mobility management in NB-N1 mode | A UE in NB-N1 mode (see 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [25A]) shall calculate the value of the applicable NAS timer indicated in table 10.2.1 plus 240s. The timer value obtained is used as described in the appropriate procedure subclause of this specification. The NAS timer value shall be calculated at start of a NAS procedure and shall not re-calculate the use of the NAS timer value until the NAS procedure is completed, restarted or aborted. When an AMF that supports NB-N1 mode performs NAS signalling with a UE, which is using NB-N1 mode, the AMF shall calculate the value of the applicable NAS timer indicated in table 10.2.2 plus 240s. The timer value obtained is used as described in the appropriate procedure subclause of this specification. The NAS timer value shall be calculated at start of a NAS procedure and shall not re-calculate the use of the NAS timer value until the NAS procedure is completed, restarted or aborted. | 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.17 |
6,457 | 9.11.3.75 Extended rejected NSSAI | The purpose of the Extended rejected NSSAI information element is to identify a collection of rejected S-NSSAIs if UE supports extended rejected NSSAI. The Extended rejected NSSAI information element is coded as shown in figure 9.11.3.75.1, figure 9.11.3.75.2 and table 9.11.3.75.1. The Extended rejected NSSAI is a type 4 information element with a minimum length of 5 octets and a maximum length of 90 octets. Figure 9.11.3.75.1: Extended rejected NSSAI information element Figure 9.11.3.75.2: Partial extended rejected NSSAI list – type of list = 000 Figure 9.11.3.75.3: Partial extended rejected NSSAI list – type of list = 001 Figure 9.11.3.75.4: Rejected S-NSSAI Table 9.11.3.75.1: Extended rejected NSSAI 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.75 |
6,458 | 8.9.15 IAB-donor-CU-based NR Cell Identity (NCI) (re-)configuration for mobile IAB cells | The NCIs of the cells served by a mobile IAB-DU configured by the OAM can be reconfigured by the F1-terminating IAB-donor-CU serving the mobile IAB-DU, in case of an NCI collision with cells of other gNB-DUs served by the IAB-donor-CU. The reconfiguration of NCI pertains to the reconfiguration of the cellLocalId part of the NCI, where the new cellLocalId(s) are based on a list of NCIs that has been configured on this F1-terminating IAB-donor-CU. The value change of cellLocalId(s) shall be indicated to the OAM system of the mobile IAB-DU following the NCI reconfiguration. The mobile IAB-DU can notify OAM about the reconfigured cellLocalId(s) using notifications specified in TS 28.532[ Management and orchestration; Generic management services ] [33]. NOTE: This shall not affect the existing procedure of configuring NCGI of cells served by a stationary gNB-DU via the OAM. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 8.9.15 |
6,459 | 6.2.5.1.3 UL user data packet matching | For PDU session of IPv4, IPv6, IPv4v6 or Ethernet PDU session type, upon receiving an UL user data packet from the upper layers for transmission via a PDU session, the UE shall attempt to associate the UL user data packet with: a) the QFI of a signalled QoS rule associated with the PDU session which has a set of packet filters containing a packet filter for UL direction matching the UL user data packet or containing a packet filter for both UL and DL directions matching the UL user data packet; or b) the QFI of a derived QoS rule associated with the PDU session which has the packet filter for UL direction matching the UL user data packet; by evaluating the QoS rules in increasing order of their precedence values until the UL user data packet is associated with a QFI or all QoS rules are evaluated. For PDU session of unstructured PDU session type, upon receiving an UL user data packet from the upper layers for transmission via a PDU session, the UE shall associate the UL user data packet with the QFI of the default QoS rule associated with the PDU session. If the UL user data packet is associated with a QFI, the UE shall pass the QFI along the UL user data packet to the lower layers for transmission. NOTE: Marking of the UL user data packet with the QFI is performed by the lower layers. If all QoS rules are evaluated and the UL user data packet is not associated with a QFI, the UE shall discard the UL user data packet. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.2.5.1.3 |
6,460 | Annex B (normative): Contention resolution for RACH access | When checking whether contention resolution was successful a MAC entity considers the MAC header structures shown below for the processing of a MAC PDU containing a UE Contention Resolution Identity MAC control element. Figure B-1: MAC header structures containing a UE Contention Resolution Identity MAC control element NOTE 1: For Case 1 (only Contention Resolution ID is carried), the resulting MAC PDU content is of fixed size and UE interprets the rest of MAC PDU data (if any) as padding without MAC subheader for padding. NOTE 2: For Case 2 to Case 6, LCID of '00001' is applicable only when UE supports the CIoT EPS User Plane optimisation. NOTE 3: Case 7 and Case 8 are only applicable to EDT when the UE supports the CIoT EPS User Plane optimisation. For NB-IoT UE, n is 1 or 2. For BL UE or a UE in enhanced coverage, n is from 1 to 8. NOTE 4: In Case 7, if n is 1, there is no L field after the subheader of MAC SDU for DTCH. | 3GPP TS 36.321 | Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification | RAN2 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | Annex |
6,461 | 6.6.2.2 Remote UE report procedure initiation | In order to initiate the 5G ProSe remote UE report procedure, the UE shall create a REMOTE UE REPORT message. The UE shall include information of newly connected or disconnected 5G ProSe remote UEs to the network in the REMOTE UE REPORT message by setting the values of the Remote UE context connected IE or the Remote UE context disconnected IE to the 5G ProSe remote UE identities that are being connected or disconnected, respectively. The UE shall set the Remote UE ID with: a) the UP-PRUK ID of the 5G ProSe remote UE, if the security for 5G ProSe communication via 5G ProSe UE-to-network relay is performed over user plane as specified in 3GPP TS 33.503[ Security Aspects of Proximity based Services (ProSe) in the 5G System (5GS) ] [56]; b) the CP-PRUK ID of the 5G ProSe remote UE, if the security for 5G ProSe communication via 5G ProSe UE-to-network relay is performed over control plane as specified in 3GPP TS 33.503[ Security Aspects of Proximity based Services (ProSe) in the 5G System (5GS) ] [56]; or c) the PEI of the 5G ProSe remote UE, if the RSC is specific for emergency services as specified in 3GPP TS 24.554[ Proximity-services (ProSe) in 5G System (5GS) protocol aspects; Stage 3 ] [19E], and the 5G ProSe remote UE is identified by a PEI. If the UE sets the Remote UE ID with the PRUK ID of the 5G ProSe remote UE and the UP-PRUK ID is in 64-bit string format, the UE shall include the HPLMN ID of the 5G ProSe remote UE. If the UE allocated an IPv4 address to a 5G ProSe remote UE and enabled UDP usage to the 5G ProSe remote UE, the UE shall include in the REMOTE UE REPORT message the UDP port range assigned to the 5G ProSe remote UE in the NAT function of 5G ProSe layer-3 UE-to-network relay. If the UE allocated an IPv4 address to a 5G ProSe remote UE and enabled TCP usage to the 5G ProSe remote UE, the UE shall include in the REMOTE UE REPORT message the TCP port range assigned to the 5G ProSe remote UE in the NAT function of 5G ProSe layer-3 UE-to-network relay. The UE shall set the PDU session ID IE to the value of the PDU session associated with the 5G ProSe remote UE connected to the 5G ProSe layer-3 UE-to-network relay UE or disconnected from the 5G ProSe layer-3 UE-to-network relay UE. The UE shall allocate a PTI value currently not used and shall set the PTI IE of the REMOTE UE REPORT message to the allocated PTI value. The UE shall transport the REMOTE UE REPORT message and the PDU session ID, using the NAS transport procedure as specified in subclause 5.4.5, and the UE shall start timer T3586 (see example in figure 6.6.2.2.1). Figure 6.6.2.2.1: Remote UE report 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.6.2.2 |
6,462 | 5.4.2.4 Authentication completion by the network | Upon receipt of an AUTHENTICATION RESPONSE message, the network stops the timer T3460 and checks the correctness of RES (see 3GPP TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [19]). If the authentication procedure has been completed successfully and the related eKSI is stored in the EPS security context of the network, the network shall include a different eKSI value in the AUTHENTICATION REQUEST message when it initiates a new authentication procedure. Upon receipt of an AUTHENTICATION FAILURE message, the network stops the timer T3460. In the case where the EMM cause #21 "synch failure" is received, the core network may renegotiate with the HSS/AuC and provide the UE with new authentication parameters. | 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.2.4 |
6,463 | 4.3.1.3 Charging Gateway Function | The CDRs produced by the CDF are transferred immediately to the Charging Gateway Function (CGF) via the Ga reference point. The CGF acts as a gateway between the 3GPP network and the BD. It uses the Bx reference point for the transfer of CDR files to the BD. The entity relationship between the CDF and the CGF is m:1, i.e. one or more CDFs may feed CDRs into a single CGF. The CGF comprises the following main functions: - CDR reception from the CDF via the Ga reference point in near real-time. The protocols that may cross the Ga reference point are specified in TS 32.295[ Telecommunication management; Charging management; Charging Data Record (CDR) transfer ] [54]. - CDR pre-processing: - Validation, Consolidation and (Re-) Formatting of CDRs. - CDR error handling. - Persistent CDR storage. - CDR routing and filtering, i.e. storing CDRs on separate files based on filtering criteria such as CDR type, CDR parameters, originating CDF, etc. - CDR File Management, e.g. file creation, file opening / closure triggers, file deletion. - CDR file transfer to the BD. For further details of those functions see TS 32.297[ Telecommunication management; Charging management; Charging Data Record (CDR) file format and transfer ] [52]. | 3GPP TS 32.240 | Telecommunication management; Charging management; Charging architecture and principles | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.3.1.3 |
6,464 | – ReportConfigToAddModList | The IE ReportConfigToAddModList concerns a list of reporting configurations to add or modify. ReportConfigToAddModList information element -- ASN1START -- TAG-REPORTCONFIGTOADDMODLIST-START ReportConfigToAddModList ::= SEQUENCE (SIZE (1..maxReportConfigId)) OF ReportConfigToAddMod ReportConfigToAddMod ::= SEQUENCE { reportConfigId ReportConfigId, reportConfig CHOICE { reportConfigNR ReportConfigNR, ..., reportConfigInterRAT ReportConfigInterRAT, reportConfigNR-SL-r16 ReportConfigNR-SL-r16 } } -- TAG-REPORTCONFIGTOADDMODLIST-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
6,465 | 5.5.2.5.2 Source RAN to Target RAN Inter RAT handover Cancel | Figure 5.5.2.5.2-1: Inter RAT handover Cancel 1. The source RAN decides to cancel the previously requested relocation of Handover resources. This may be due to not enough accepted bearers, UE returned to source cell or any other reason. 2. The source RAN sends a Cancel message with a Cause to the source EPC node (SGSN or MME). If the source RAN is: a) BSS the message sent is PS Handover Cancel (Cause), b) RNC the message sent is Relocation Cancel (Cause), or c) eNodeB the message sent is Handover Cancel (Cause). 3. The source EPC node terminates the relocation towards the target side by sending a Relocation Cancel Request (IMSI) message to the target EPC node. The Source EPC node also resumes operation on the resources in the source side. 4. The target EPC node triggers the release of resources in the target RAN and also releases its own resources allocated for this handover. 5. This step is only performed for Serving GW relocation. The Target EPC node deletes the EPS bearer resources by sending Delete Session Request (Cause) messages to the Target Serving GW. The Target Serving GW acknowledges with Delete Session Response (Cause) messages. 6. The target EPC node acknowledge the release of all resources on the target side by returning a Relocation Cancel Response (Cause) message to the source EPC node. 7. The source EPC node returns a Cancel acknowledge message to the source RAN. If the source RAN is: a) BSS there will be no acknowledge message sent to the source BSS, b) RNC the message sent is Relocation Cancel Acknowledge (Cause), or c) eNodeB the message sent is Handover Cancel Acknowledge (Cause). 8. If indirect forwarding tunnel is setup during handover preparation then cancellation of handover triggers the source MME/SGSN to send a Delete Indirect Data Forwarding Tunnel Request message to the S-GW to release the temporary resources used for indirect forwarding. 9. If indirect forwarding tunnel is setup during handover preparation and serving GW is relocated then cancellation of handover triggers the target MME/SGSN to send a Delete Indirect Data Forwarding Tunnel Request message to the S-GW to release the temporary resources used for indirect forwarding. | 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.2.5.2 |
6,466 | 8.7.2 Conditional IE errors | When the MS upon receipt of an RR, MM or CC message diagnoses a "missing conditional IE" error or an "unexpected conditional IE" error or when it receives an RR, MM or CC message containing at least one syntactically incorrect conditional IE, it shall ignore the message except for the fact that, if an RR connection exists, it shall return a status message (STATUS, or MM STATUS depending on the PD) with cause value # 100 "conditional IE error". When the MS upon receipt of a GMM or SM message diagnoses a "missing conditional IE" error or an "unexpected conditional IE" error or when it receives a GMM or SM message containing at least one syntactically incorrect conditional IE, it shall ignore the message and it shall return a status message (GMM STATUS or SM STATUS depending on the PD) with cause value # 100 "conditional IE error". When the network receives a message and diagnose a "missing conditional IE" error or an "unexpected conditional IE" error or when it receives a message containing at least one syntactically incorrect conditional IE, the network shall either - try to treat the message (the exact further actions are implementation dependent), or - ignore the message except that it should return a status message (STATUS, MM STATUS, GMM STATUS or SM STATUS depending on the protocol discriminator) with cause # 100 "conditional IE error". | 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 | 8.7.2 |
6,467 | G.2 Cause related to subscription options | Cause value = 11 PLMN not allowed This cause is sent to the MS if it requests service, or if the network initiates a detach request, in a PLMN where the MS, by subscription or due to operator determined barring is not allowed to operate. Cause value = 12 Location Area not allowed This cause is sent to the MS if it requests service, or if the network initiates a detach request, in a location area where the HPLMN determines that the MS, by subscription, is not allowed to operate. NOTE 1: If cause #12 is sent to a roaming subscriber the subscriber is denied service even if other PLMNs are available on which registration was possible. Cause value = 13 Roaming not allowed in this location area This cause is sent to an MS which requests service, or if the network initiates a detach request, in a location area of a PLMN which by subscription offers roaming to that MS but not in that location area. Cause value = 15 No Suitable Cells In Location Area This cause is sent to the MS if it requests service, or if the network initiates a detach request, in a location area where the MS, by subscription, is not allowed to operate, but when it should find another allowed location area or tracking area in the same PLMN or an equivalent PLMN. NOTE 2: Cause #15 and cause #12 differ in the fact that cause #12 does not trigger the MS to search for another allowed location area on the same PLMN. Cause value = 25 Not authorized for this CSG This cause is sent to the MS if it requests access, or if the network initiates a detach request, in a CSG cell where the MS either has no subscription to operate or the MS's subscription has expired and it should find another cell in the same PLMN or an equivalent PLMN. NOTE 3: The MS not supporting CSG will not receive cause# 25, as such a MS is not supposed to try to access a CSG cell. | 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 | G.2 |
6,468 | 16.10.5.3.5 Service Continuity in RRC_INACTIVE | Mobility procedures for multicast reception allow the UE in RRC_INACTIVE state to continue receiving MBS service(s) when changing cells without resuming RRC connection if the PTM configuration of the new cell can be acquired by the UE from the multicast MCCH after cell reselection. During an active MBS multicast session, the UE is required to resume RRC connection to get the PTM configuration if the PTM configuration is not provided on the multicast MCCH of the new cell. Even if the UE in RRC_INACTIVE state received indication to stop monitoring PDCCH addressed by G-RNTI for an MBS multicast session in the source cell, the UE acquires MCCH in the reselected cell after cell reselection. The gNB may indicate in the multicast MCCH the list of neighbour cells providing the same MBS multicast service(s) for UEs in RRC_INACTIVE state as provided in the serving cell. This allows the UE, e.g., to resume RRC connection without reading SIB24 and multicast MCCH of the neighbour cell, if the interested service which is activated is not available to the UE in RRC_INACTIVE state. The gNB may provide an indication on cell PDCP COUNT synchronization for an MBS session with PTM configuration in RRCRelease message. If indicated by the gNB, all cells within the RNA are synchronized in terms of PDCP COUNT value to the MRBs of the corresponding MBS service, and the order of MRBs within the list of multicast MRB configuration for the same MBS multicast session in the multicast MCCH message of the last serving cell and (re)selected cell within the RNA should be consistent. Upon reselection to a cell indicated as synchronized in terms of PDCP COUNT value, the UE does not initialize the PDCP state variables. Otherwise, the UE initializes the PDCP state variables as defined in TS 38.323[ NR; Packet Data Convergence Protocol (PDCP) specification ] [8]. The UE may be configured with dedicated frequency priorities in RRCRelease message which the UE applies during cell reselection while receiving data of MBS multicast session in RRC_INACTIVE state. The UE receiving multicast session(s) in RRC_INACTIVE state triggers RRC connection resumption if the latest measured RSRP or RSRQ of the serving cell becomes lower than the threshold configured by the network. The threshold can be configured per MBS session via RRCRelease message or multicast MCCH. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.10.5.3.5 |
6,469 | 19.4.2.10 Global eNodeB-ID for eNodeB | The Global eNodeB-ID is used to identify eNodeBs globally which is composed of the concatenation of MCC, MNC and the eNodeBID. The MCC and MNC are the same as included in the E-UTRAN Cell Global Identifier (ECGI) (see clause 19.6). A subdomain name shall be derived from the MNC and MCC by adding the label "enb" to the beginning of the Home Network Realm/Domain (see clause 19.2). The Global eNodeB-ID FQDN shall be constructed as: enb<eNodeB-ID>.enb.epc.mnc<MNC>.mcc<MCC>.3gppnetwork.org The <eNodeB-ID> shall be coded using a full hexadecimal representation. If there are less than 4 significant digits in < eNodeB-ID>, "0" digit(s) shall be inserted at the left side to fill the 4 digit coding. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 19.4.2.10 |
6,470 | 4.11.5.9a Network Slice Admission Control in 5GS for maximum number of UE with at least one PDU session and one PDN connection | Support of NSAC in conjunction with interworking with EPC for maximum number of UE with at least one PDU session/PDN connection is described in clause 5.15.11.5a of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. For option 1, the same mechanisms in clause 4.2.11.2 (Number of UEs per network slice availability check and update procedure) is used with the following additions: - The SMF+PGW-C invokes this procedure when the UE establishes the first PDU Session/PDN Connection and when the last PDU Session/PDN Connection associated with the network slice is released. In this case, the AMF in figure 4.2.11.2-1 is replaced with SMF+PGW-C. - Step 2: The SMF+PGW-C includes in the message the S-NSSAI, identity of SMF+PGW-C, UE ID and update flag. The update flag may include either 'increase', 'decrease' or 'update' values. - Step 2: The AMF ID is replaced by the SMF+PGW-C ID. - Step 3: The 'update' value indicates that for existing UE registration the Access Type is to be replaced with a new Access Type during inter access mobility. If the update flag parameter from the SMF+PGW-C indicates update value, the NSACF locates the existing entry with UE ID and NF ID and replaces the Access Type in the existing entry. The NSACF may take the Access Type into account for UE counting based on local policy. If there was one UE entry in the new Access Type with same NF ID then NSACF may not increase the count again. If there was one UE entry in the new Access Type with different NF ID then NSACF may add this new NF ID in the UE entry and not increase the count. If there was one entry with same NF ID in the old Access Type then NSACF may remove the UE entry and decrease the count. Editor's note: Step 3 needs to be further discussed/completed to cover both cases when the access type is considered and not considered. - The NSACF determines whether or not to accept the request as described in clause 5.15.11.5a of TS 23.501[ System architecture for the 5G System (5GS) ] [2] NOTE 1: EAC mode is not applicable here. For option 2, the same mechanisms in clause 4.2.11.4 (Number of PDU Sessions per network slice availability check and update procedure) are used with the following additions: - The NSACF also counts the maximum number UE with at least one PDU session/PDN connection based on the update value received from SMF+PGW-C. - If the update flag parameter from the SMF/SMF+PGW-C anchoring the PDU session/PDN connections indicates update, the NSACF locates the existing entry with UE ID and NF ID and replaces the Access Type in the existing entry. The NSACF may take the Access Type into account for UE counting based on local policy. If there was one UE entry in the new Access Type with same NF ID then NSACF may not increase the count again. If there was one UE entry in the new Access Type with different NF ID then NSACF may add this new NF ID and not increase the count. If there was one entry with same NF ID in the old Access Type then NSACF may remove the UE entry and decrease the count. - The NSACF determines whether to accept the request as described in clause 5.15.11.5a of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. - The NSACF performs other actions in addition to the above to keep track of the last PDU Session/Connection released so as to decrease the count for the number of Registered UEs with at least one PDU Session/one PDN Connection. NOTE 2: EAC mode is not applicable here. If Hierarchical NSAC architecture is deployed in the network, there are the following additional enhancements: - For option 2, the NSAC for number of UEs and NSAC for number of PDU sessions/PDN connections shall be handled within the same NSACF. - For both options, when the local maximum number of UEs with at least one PDU Session/PDN Connection or local threshold is reached, the NSACF may interact with the Primary NSACF before it returns the response back to the SMF+PGW-C. For more details on handling between the NSACF and Primary NSACF see clause 4.2.11.2a. NOTE 3: For both options, given that the SMF+PGW-C can not provide the UE already registered indication to NSACF, hence when the NSACF interacts with Primary NSACF, the Primary NSACF will not manage the UE entry by itself. - For NSAC for number of PDU Sessions, when the local maximum number is reached, the NSACF may interact with the Primary NSACF before it returns the response back to the SMF+PGW-C. For more details on handling between the NSACF and Primary NSACF see clause 4.2.11.4a. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.11.5.9a |
6,471 | 4.3.1.2.2 Attempted outgoing inter-eNB handover executions per handover cause | This measurement provides the number of attempted outgoing inter-eNB handovers per handover cause. CC. Transmission of the RRC ConnectionReconfiguration message to UE triggering the handover from the source eNB to the target eNB, indicatingthe attempt of an outgoing inter-eNB handover (see TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8]). The sum of all supported per cause measurements shall equal the total number of outgoing inter-eNB handover event 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]. 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.InterEnbOutAtt.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.2.2 |
6,472 | 5.3.10.4.1 AS security mode command procedure | The MME triggers the RRC level AS security mode command procedure by sending the needed security parameters to the eNodeB. This enables ciphering of the UP traffic and ciphering and integrity protection of the RRC signalling as described in TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [41]. NOTE: The integrity protection of the UP traffic is enabled using RRC reconfiguration procedure as described in TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [41]. | 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.10.4.1 |
6,473 | 5.5.1.3.2 Combined attach procedure initiation | If the UE is in EMM state EMM-DEREGISTERED, the UE initiates the combined attach procedure by sending an ATTACH REQUEST message to the network, starting timer T3410 and entering state EMM-REGISTERED-INITIATED (see example in figure 5.5.1.2.2.1). The UE shall include the TMSI status IE if no valid TMSI is available. Furthermore, if the UE has stored a valid location area identification, the UE shall include it in the Old location area identification IE in the ATTACH REQUEST message. If the UE has stored a valid TMSI, the UE shall include the TMSI based NRI container IE in the ATTACH REQUEST message. If the UE initiates a combined attach procedure for EPS services and "SMS only", the UE shall indicate "SMS only" in the Additional update type 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 | 5.5.1.3.2 |
6,474 | 6.2.2B UE maximum output power for UL-MIMO | For UE with two transmit antenna connectors in closed-loop spatial multiplexing scheme, the maximum output power for any transmission bandwidth within the channel bandwidth is specified in Table B-1. The requirements shall be met with the UL-MIMO configurations specified in Table 6.2.2B-2. For UE supporting UL-MIMO, the maximum output power is measured as the sum of the maximum output power at each UE antenna connector. The period of measurement shall be at least as defined in Table 6.2.2B-0. Table 6.2.2B-0: Measurement period for UE maximum output power for UL-MIMO Table 6.2.2B-1: UE Power Class for UL-MIMO in closed loop spatial multiplexing scheme The default power class for an operating band is Power Class 3 unless otherwise stated. For a power class 2 capable UE operating on Band 41, when an IE P-max as defined in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [7] of 23 dBm or lower is indicated in the cell or if the uplink/downlink configuration is 0 or 6, the requirements for power class 2 are not applicable and the corresponding requirements for a power class 3 UE shall apply. For each supported frequency band other than Band 41, the UE shall: - if the UE supports a different power class than the UE default power class for the band and the supported power class enables the higher maximum output power than that of the default power class: - if the band is a TDD band whose frame configuration is 0 or 6; or - if the IE P-Max as defined in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [7] is not provided; or - if the IE P-Max as defined in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [7] is provided and set to the maximum output power of the default power class or lower; - meet all requirements for the default power class of the operating band in which the UE is operating and set its configured transmitted power as specified in sub-clause 6.2.5; - else (i.e the IE P-Max as defined in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [7] is provided and set to the higher value than the maximum output power of the default power class): - meet all requirements for the supported power class and set its configured transmitted power as specified in sub-clause 6.2.5; Table 6.2.2B-2: UL-MIMO configuration in closed-loop spatial multiplexing scheme If UE is configured for transmission on single-antenna port, the requirements in subclause 6.2.2 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.2.2B |
6,475 | 5.2.5.9.2 Npcf_PDTQPolicyControl_Create service operation | Service operation name: Npcf_PDTQPolicyControl_Create Description: This service is to create the PDTQ policy. Inputs, Required: ASP identifier, Number of UEs, list of Desired time windows, QoS reference or individual QoS parameters as described in clause 6.1.3.22 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. Inputs, Optional: S-NSSAI, DNN, Network Area Information, Request for notification, Alternative Service Requirements. Outputs, Required: One or more PDTQ policies, PDTQ Reference ID. Outputs, Optional: None. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.5.9.2 |
6,476 | 9.2.3.1A FDD (With channelMeasRestriction configured) | The following requirements apply to UE Category ≥2. For the parameters specified in table 9.2.3.1A-1, and using the downlink physical channels specified in tables C.3.2-1 and C.3.2-2, the reported offset level of the wideband spatial differential CQI for codeword #1 (Table 7.2-2 in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [6]) shall be used to determine the wideband CQI index for codeword #1 as wideband CQI1 = wideband CQI0 – Codeword 1 offset level The wideband CQI1 shall be within the set {median CQI1 -1, median CQI1, median CQI1 +1} for more than 90% of the time, where the resulting wideband values CQI1 shall be used to determine the median CQI values for codeword #1. For both codewords #0 and #1, the PDSCH BLER using the transport format indicated by the respective median CQI0 – 1 and median CQI1 – 1 shall be less than or equal to 0.1. Furthermore, for both codewords #0 and #1, the PDSCH BLER using the transport format indicated by the respective median CQI0 + 1 and median CQI1 + 1 shall be greater than or equal to 0.1. Table 9.2.3.1A-1: PUCCH 1-1 static test (FDD) | 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.2.3.1A |
6,477 | 5.2.6.4.2 Nnef_ParameterProvision_Update service operation | Service operation name: Nnef_ParameterProvision_Update Description: The consumer updates the UE related information (e.g. Expected UE Behaviour, Network Configuration parameters, Location Privacy Indication parameters, ECS Address Configuration Information) or 5G VN Group related information (e.g. 5G VN group data, 5G VN membership management), or for Multicast MBS related information or DNN and S-NSSAI specific Group Parameters, DNN, S-NSSAI. Inputs, Required: AF Identifier, Transaction Reference ID. Inputs, Optional: GPSI or UE addressing information, External Group ID, at least one of the Expected UE Behaviour parameters (optionally with associated confidence and/or accuracy levels) or at least one of the Application-Specific Expected UE Behaviour parameters (optionally with associated confidence and/or accuracy levels) or at least one of the Network Configuration parameters or 5G VN related information or ECS Address Configuration Information, Validity Time or Location Privacy Indication parameters, MTC Provider Information, or Multicast MBS related information, DNN and S-NSSAI specific Group Parameters, DNN, S-NSSAI, PLMN IDs. Outputs, Required: Operation execution result indication. Outputs, Optional: Transaction specific parameters, if available. External Identifier (representing an AF specific UE Identifier). For Multicast MBS related information, refer to TS 23.247[ Architectural enhancements for 5G multicast-broadcast services ] [78]. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.6.4.2 |
6,478 | 8.9.1 UE Initial Access | The signalling flow for UE Initial access involving E1 and F1 is shown in Figure 8.9.1-1. Figure 8.9.1-1: UE Initial Access procedure involving E1 and F1 Steps 1-8 are defined in clause 8.1. 9. The gNB-CU-CP sends the BEARER CONTEXT SETUP REQUEST message to establish the bearer context in the gNB-CU-UP. 10 The gNB-CU-UP sends the BEARER CONTEXT SETUP RESPONSE message to the gNB-CU-CP, including F1-U UL TEID and transport layer address allocated by the gNB-CU-UP. Steps 11-13 are defined in clause 8.1. 14. The gNB-CU-CP sends the BEARER CONTEXT MODIFICATION REQUEST message to the gNB-CU-UP, including F1-U DL TEID and transport layer address allocated by the gNB-DU. 15. The gNB-CU-UP sends the BEARER CONTEXT MODIFICATION RESPONSE message to the gNB-CU-CP. Steps 16-22 are defined in clause 8.1. NOTE: Steps 14-15 and steps 16-17 can happen in parallel, but both are before step 18. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 8.9.1 |
6,479 | 9.2.3.4.2 C-plane handling | As in intra-NR RAN handover, in intra-NR RAN CHO, the preparation and execution phase of the conditional handover procedure is performed without involvement of the 5GC; i.e. preparation messages are directly exchanged between gNBs. The release of the resources at the source gNB during the conditional handover completion phase is triggered by the target gNB. The figure below depicts the basic conditional handover scenario where neither the AMF nor the UPF changes: Figure 9.2.3.4.2-1: Intra-AMF/UPF Conditional Handover 0/1. Same as step 0, 1 in Figure 9.2.3.2.1-1 of clause 9.2.3.2.1. 2. The source gNB decides to use CHO. 3. The source gNB requests CHO for one or more candidate cells belonging to one or more candidate gNBs. A CHO request message is sent for each candidate cell. 4. Same as step 4 in Figure 9.2.3.2.1-1 of clause 9.2.3.2.1. 5. The candidate gNB(s) sends CHO response (HO REQUEST ACKNOWLEDGE) including configuration of CHO candidate cell(s) to the source gNB. The CHO response message is sent for each candidate cell. 6. The source gNB sends an RRCReconfiguration message to the UE, containing the configuration of CHO candidate cell(s) and CHO execution condition(s). NOTE 1: CHO configuration of candidate cells can be followed by another reconfiguration from the source gNB. NOTE 1a: A configuration of a CHO candidate cell cannot contain a DAPS handover configuration. 7. The UE sends an RRCReconfigurationComplete message to the source gNB. 7a If early data forwarding is applied, the source gNB sends the EARLY STATUS TRANSFER message. 8. The UE maintains connection with the source gNB after receiving CHO configuration, and starts evaluating the CHO execution conditions for the candidate cell(s). If at least one CHO candidate cell satisfies the corresponding CHO execution condition, the UE detaches from the source gNB, applies the stored corresponding configuration for that selected candidate cell, synchronises to that candidate cell and completes the RRC handover procedure by sending RRCReconfigurationComplete message to the target gNB. The UE releases stored CHO configurations after successful completion of RRC handover procedure. 8a/b The target gNB sends the HANDOVER SUCCESS message to the source gNB to inform that the UE has successfully accessed the target cell. In return, the source gNB sends the SN STATUS TRANSFER message following the principles described in step 7 of Intra-AMF/UPF Handover in clause 9.2.3.2.1. NOTE 2: Late data forwarding may be initiated as soon as the source gNB receives the HANDOVER SUCCESS message. 8c. The source gNB sends the HANDOVER CANCEL message toward the other signalling connections or other candidate target gNBs, if any, to cancel CHO for the UE. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 9.2.3.4.2 |
6,480 | 4.23.12.3A EPS to 5GS Idle mode mobility using N26 interface with Data forwarding and I-SMF insertion | For EPS to 5GS Mobility registration procedure using N26 with data forwarding and I-SMF insertion, the procedure "EPS to 5GS Idle Mobility using N26 interface with data forwarding" defined in clause 4.11.1.3.3A for the home routed-roaming case is re-used, with the following change: - The V-SMF is replaced by I-SMF and H-SMF is replaced by SMF, V-UPF is replaced by I-UPF. - The V-SMF selection is replaced by the I-SMF selection. - The V-CN Tunnel Info is replaced by Tunnel Info at I-UPF, H-CN Tunnel Info is replaced by Tunnel Info at UPF(PSA). - Data forwarding tunnel resource is established and the tunnel information is exchanged through N26 interface. Data buffered in Serving GW is forwarded to UE via I-SMF/I-UPF. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.23.12.3A |
6,481 | 8.2.18.1 Message definition | The SERVICE REJECT message is sent by the AMF to the UE in order to reject the service request procedure. See table 8.2.18.1.1. Message type: SERVICE REJECT Significance: dual Direction: network to UE Table 8.2.18.1.1: SERVICE REJECT message content NOTE: It is possible for AMFs compliant with version 17.7.0 or 17.8.0 of this specification to send the Forbidden TAI(s) for the list of "5GS forbidden tracking areas for roaming" IE with IEI of value "3B" for this message or the Forbidden TAI(s) for the list of "5GS forbidden tracking areas for regional provision of service" IE with IEI of value "3C" for this message. | 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 | 8.2.18.1 |
6,482 | – SecurityModeCommand | The SecurityModeCommand message is used to command the activation of AS security. Signalling radio bearer: SRB1 RLC-SAP: AM Logical channel: DCCH Direction: Network to UE SecurityModeCommand message -- ASN1START -- TAG-SECURITYMODECOMMAND-START SecurityModeCommand ::= SEQUENCE { rrc-TransactionIdentifier RRC-TransactionIdentifier, criticalExtensions CHOICE { securityModeCommand SecurityModeCommand-IEs, criticalExtensionsFuture SEQUENCE {} } } SecurityModeCommand-IEs ::= SEQUENCE { securityConfigSMC SecurityConfigSMC, lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension SEQUENCE{} OPTIONAL } SecurityConfigSMC ::= SEQUENCE { securityAlgorithmConfig SecurityAlgorithmConfig, ... } -- TAG-SECURITYMODECOMMAND-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
6,483 | 8.7.14 TDD DC (4 Rx) | The parameters specified in Table 8.7.14-1 are valid for all TDD tests for 4Rx capable UEs unless otherwise stated. Table 8.7.14-1: Common Test Parameters (TDD) For UE not supporting 256QAM, the TB success rate shall be higher than 85% when PDSCH are scheduled with FRC in Table 8.7.14-2 with the downlink physical channel setup according to Annex C.3.2. For UE supporting 256QAM, the TB success rate shall be higher than 85% when PDSCH are scheduled with FRC in Table 8.7.14-3 with the downlink physical channel setup according to Annex C.3.2. For UE supporting 256QAM, the requirement with 64QAM is not applicable. The TB success rate is defined as 100%*NDL_correct_rx/ (NDL_newtx + NDL_retx), where NDL_newtx is the number of newly transmitted DL transport blocks, NDL_retx is the number of retransmitted DL transport blocks, and NDL_correct_rx is the number of correctly received DL transport blocks. The TB success rate across CGs shall be sustained during at least 300 frames. Table 8.7.14-2: Per-CC FRC for SDR test (TDD 64QAM) Table 8.7.14-3: Per-CC FRC for SDR test (TDD 256QAM) DC configuration, bandwidth combination and MIMO layer on each CC is determined by following procedure. - Select one DC bandwidth combination among all supported DC configurations with bandwidth combination and MIMO layer on each CC that leads to largest equivalent aggregated bandwidth among all DC bandwidth combinations supported by UE. Equivalent aggregated bandwidth is defined as where is number of CCs, and is MIMO layer and bandwidth of CC . - When there are multiple sets of {DC configuration, bandwidth combination, MIMO layer} with same largest aggregated bandwidth, select one among sets with largest number of 4 layer 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.7.14 |
6,484 | 4.2.1.10 Number of E-RABs successfully established for incoming HOs | This measurement provides the number of E-RABs successfully established for incoming HOs. The measurement is split into subcounters per E-RAB QoS level (QCI). CC On transmission by the eNB of a X2AP HANDOVER REQUEST ACKNOWLEDGE or S1AP HANDOVER REQUEST ACKNOWLEDGE message, or on transmission by the eNB of the RRCConnectionReconfiguration message to the UE triggering the intra-eNB handover (see TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8]) after the E-RABs in this message are successfully established in the target E-UTRAN cell. Each E-RAB successfully established is added to the relevant measurement per QCI, the possible QCIs are included in TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [9]. The sum of all supported per QCI measurements shall equal the total number of E-RABs successfully setup. In case only a subset of per QCI measurements is supported, a sum subcounter will be provided first. Each measurement is an integer value. The number of measurements is equal to the number of QCIs plus a possible sum value identified by the .sum suffix. The measurement name has the form ERAB.EstabIncHoSuccNbr.QCI where QCI identifies the E-RAB level quality of service class. EUtranCellFDD EUtranCellTDD Valid for packet switched traffic EPS | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.2.1.10 |
6,485 | 5.10.2.3 Multicast MCCH information acquisition by the UE | A UE configured to receive an MBS multicast service in RRC_INACTIVE shall: 1> if the procedure is triggered by a multicast MCCH information change notification: 2> start acquiring the MBSMulticastConfiguration message on multicast MCCH in the concerned cell from the slot in which the change notification was received; 1> if the UE moves to a different cell providing SIB24; or 1> if the UE receives RRCRelease configuring the UE to receive MBS multicast in RRC_INACTIVE which doesn't include PTM configuration for at least one multicast session for which the UE is not indicated to stop monitoring the G-RNTI: 2> acquire the MBSMulticastConfiguration message on multicast MCCH in the concerned cell at the next repetition period. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.10.2.3 |
6,486 | 7.1 System information handling | In MR-DC, the SN is not required to broadcast system information other than for radio frame timing and SFN. System information for initial configuration is provided to the UE by dedicated RRC signalling via the MN. The UE acquires, at least, radio frame timing and SFN of SCG from the PSS/SSS and MIB (if the SN is an eNB) / NR-PSS/SSS and PBCH (if the SN is a gNB) of the PSCell. In EN-DC, SN may broadcast system information to allow only IAB-MT to access the SN. NOTE: The option that the SN does not broadcast system information other than radio frame timing and SFN relies on proper OAM configuration. Additionally, upon change of the relevant system information of a configured SCell, the network releases and subsequently adds the concerned SCell (with updated system information), via one or more RRC reconfiguration messages sent on SRB1 or SRB3, if configured. | 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 | 7.1 |
6,487 | 28.3.2.8 AMF Instance FQDN | The AMF Instance FQDN shall uniquely identify an AMF instance. The AMF Instance FQDN shall be constructed as: pt<AMF Pointer>.set<AMF Set Id>.region<AMF Region Id>.amfi.5gc.mnc<MNC>.mcc<MCC>.3gppnetwork.org where - <MNC> = 3 digits - <MCC> = 3 digits If there are only 2 significant digits in the MNC, one "0" digit shall be inserted at the left side to fill the 3 digits coding of MNC in the AMF Instance FQDN. - <AMF Pointer>, <AMF Set Id> and <AMF Region Id> are the hexadecimal strings of the AMF Pointer, AMF Set ID and AMF Region ID. If there are less than 2 significant digits in <AMF Pointer> or <AMF Region Id>, "0" digit(s) shall be inserted at the left side to fill the 2 digits coding of the AMF Pointer or AMF Region Id respectively. If there are less than 3 significant digits in <AMF Set Id>, "0" digit(s) shall be inserted at the left side to fill the 3 digits coding. As an example, the AMF Instance FQDN for the AMF Pointer 12 (hexadecimal), AMF Set 1, AMF Region 48 (hexadecimal), MCC 345 and MNC 12 is coded as: "pt12.set001.region48.amfi.5gc.mnc012.mcc345.3gppnetwork.org" | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 28.3.2.8 |
6,488 | 5.2.2.4.3 Actions upon reception of SIB2 | Upon receiving SIB2, the UE shall: 1> if in RRC_IDLE or in RRC_INACTIVE or in RRC_CONNECTED while T311 is running: 2> if, for the entry in frequencyBandList with the same index as the frequency band selected in clause 5.2.2.4.2, the UE supports at least one additionalSpectrumEmission in the nr-NS-PmaxList within the frequencyBandList or 2> if, for the entry in frequencyBandListAerial with the same index as the frequency band selected in clause 5.2.2.4.2, the UE supports at least one additionalSpectrumEmission in the nr-Ns-PmaxListAerial within the frequencyBandListAerial: 3> if the UE is aerial UE and it supports at least one additionalSpectrumEmission values in nr-NS-PmaxListAerial within the frequencyBandListAerial: 4> apply the first listed additionalSpectrumEmission which it supports among the values included in nr-NS-PmaxListAerial within frequencyBandListAerial; 3> else: 4> apply the first listed additionalSpectrumEmission which it supports among the values included in nr-NS-PmaxList within frequencyBandList; 3> if the additionalPmax is present in the same entry of the selected additionalSpectrumEmission within nr-NS-PmaxList or nr-NS-PmaxListAerial: 4> apply the additionalPmax; 3> else: 4> apply the p-Max; 3> if the UE selects a frequency band (from the procedure in clause 5.2.2.4.2) for the supplementary uplink: 4> if, for the entry in frequencyBandListSUL with the same index as the frequency band selected in clause 5.2.2.4.2, the UE supports at least one additionalSpectrumEmission in the nr-NS-PmaxList within the frequencyBandListSUL: 5> apply the first listed additionalSpectrumEmission which it supports among the values included in nr-NS-PmaxList within frequencyBandListSUL; 5> if the additionalPmax is present in the same entry of the selected additionalSpectrumEmission within nr-NS-PmaxList: 6> apply the additionalPmax; 5> else: 6> apply the p-Max; 4> else: 5> apply the p-Max. 2> else: 3> apply the p-Max; | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.2.2.4.3 |
6,489 | 4.3.12.3a Reachability Management for UE in ECM-IDLE state | An emergency attached UE when its periodic TAU update timer expires shall not initiate a periodic TAU procedure but enter EMM-DEREGISTERED state. For emergency attached UEs the MME runs a mobile reachable timer with a similar value to the UE's periodic TAU timer. Any time after expiry of this timer the MME may change the EMM state of an emergency attached UE to EMM-DEREGISTERED. The MME assigns the periodic TAU timer value to emergency attached UE. This timer keeps the UE emergency attached after change to EMM-IDLE state to allow for a subsequent emergency service without a need to emergency attach again. | 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.12.3a |
6,490 | 6.1.3.1.5 Abnormal cases | The following abnormal cases can be identified: a) Expiry of timers In the mobile station: On the first expiry of the timer T3380, the MS shall resend the ACTIVATE PDP CONTEXT REQUEST and shall reset and restart timer T3380. This retransmission is repeated four times, i.e. on the fifth expiry of timer T3380, the MS shall release all resources possibly allocated for this invocation and shall abort the procedure; no automatic PDP context activation re-attempt shall be performed; and - if the ACTIVATE PDP CONTEXT REQUEST message was sent with request type set to "emergency", then the MS may inform the upper layers of the failure to establish the emergency bearer. NOTE: This can result in the upper layers requesting establishment of a CS emergency call (if not already attempted in the CS domain) or initiating 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 ] [95] can result in the emergency call being attempted to another IP-CAN. On the network side: On the first expiry of the timer T3385, the network shall resend the message REQUEST PDP CONTEXT ACTIVATION and shall reset and restart timer T3385. This retransmission is repeated four times, i.e. on the fifth expiry of timer T3385, the network shall release possibly allocated resources for this activation and shall abort the procedure. b) Collision of MS initiated and network requested PDP context activation If the MS uses dynamic PDP addressing that turns out to collide with the network requested PDP address, then there is no detection of collision specified but left for network implementation. c) MS initiated PDP context activation request for an already activated PDP context (on the network side) i) If the network receives a ACTIVATE PDP CONTEXT REQUEST message with the same combination of APN, PDP type and PDP address as an already activated PDP context, the network shall deactivate the existing PDP context and, if any, all the linked PDP contexts (matching the combination of APN, PDP type and PDP address), locally without notification to the MS and proceed with the requested PDP context activation. ii) Alternatively (different combination of APN, PDP type and PDP address), if the NSAPI matches that of an already activated PDP context, then the network shall deactivate only the existing PDP context locally without notification to the MS and proceed with the requested PDP context activation. It is an implementation option if the parameters used for comparison described in clause i) and ii) are the parameters provided in the (current and previous) ACTIVATE PDP CONTEXT REQUESTs or the parameters which are the result of the application of the selection rules defined in 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [74] Annex A.2. The parameter provided in the current ACTIVATE PDP CONTEXT REQUEST can not be compared to the actually used parameters (result of application of selection rules defined in 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [74] Annex A.2) of the previously activated PDP contexts. If the network receives an ACTIVATE PDP CONTEXT REQUEST message with request type "emergency" and there already is a PDN connection for emergency bearer services existing, the network shall reject the request with cause code #31 "activation rejected, unspecified". d) Network initiated PDP context activation request for an already activated PDP context (on the mobile station side) If the MS receives a REQUEST PDP CONTEXT ACTIVATION message with the same combination of APN, PDP type and PDP address as an already activated PDP context, the MS shall deactivate the existing PDP context and, if any, all the linked PDP contexts (matching the combination of APN, PDP type and PDP address) locally without notification to the network and proceed with the requested PDP context activation. e) Additional MS initiated PDP context activation request received from an MS that is attached for emergency bearer services: If the MS is attached for emergency bearer services the network shall only accept the PDP context activation request for emergency services. The network shall reject any other PDP context activation request with cause code #31 "activation rejected, unspecified". f) Reception of the ACTIVATE PDP CONTEXT ACCEPT message and Bearer Control Mode violation If the Selected Bearer Control Mode indicates other value than 'MS only' in the ACTIVATE PDP CONTEXT ACCEPT message although the protocol configuration options information element was not present or the MS Support of Network Requested Bearer Control indicator was not present in the protocol configuration options information element of the corresponding ACTIVATE PDP CONTEXT REQUEST message, the MS shall ignore the Selected Bearer Control Mode parameter received from the network and apply Bearer Control Mode 'MS only' for all active PDP contexts sharing the same PDP Address and APN. Figure 6.3/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : MS initiated PDP context activation procedure Figure 6.4/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Network initiated PDP context activation procedure | 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.1.5 |
6,491 | Annex E (informative): Change history 4 General principles | The general principles guiding the definition of NG-RAN architecture as well as the NG-RAN interfaces are the following: - Logical separation of signalling and data transport networks. - NG-RAN and 5GC functions are fully separated from transport functions. Addressing scheme used in NG-RAN and 5GC shall not be tied to the addressing schemes of transport functions. The fact that some NG-RAN or 5GC functions reside in the same equipment as some transport functions does not make the transport functions part of the NG-RAN or the 5GC. - Mobility for an RRC connection is fully controlled by the NG-RAN. - The NG-RAN interfaces are defined along the following principles: - The functional division across the interfaces have as few options as possible. - Interfaces are based on a logical model of the entity controlled through this interface. - One physical network element can implement multiple logical nodes. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | Annex |
6,492 | 8.4 User data forwarding | Upon EN-DC specific activities, user data forwarding may be performed for E-RABs for which the bearer type change from/to MN terminated bearer to/from SN terminated bearer is performed. The behaviour of the node from which data is forwarded is the same as specified for the "source eNB" for handover, the behaviour of the node to which data is forwarded is the same as specified for the "target eNB" for handover. For MR-DC with 5GC, user data forwarding may be performed between NG-RAN nodes whenever the logical node hosting the PDCP entity changes. The behaviour of the node from which data is forwarded is the same as specified for the "source NG-RAN node" for handover, the behaviour of the node to which data is forwarded is the same as specified for the "target NG-RAN node" for handover. For SN change involving full configuration, the source SN behaviour is the same as the description as specified in intra-system data forwarding in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [2] for the source eNB or TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [3] for the source NG-RAN node, respectively. In case that a DRB DL forwarding tunnel was established, the target SN may identify the PDCP SDUs for which delivery was attempted by the source SN, by the presence of the PDCP SN in the forwarded GTP-U packet and may discard them. For mobility scenarios which involve more than two RAN nodes, either direct or indirect data forwarding may be applied. Two transport layer addresses of different versions may be provided to enable that the source RAN node can select either IPv4 or IPv6. Direct data forwarding from source SN to target NG-RAN node and from source NG-RAN node to target SN for mobility scenario is supported. Direct data forwarding from source SN to target SN for SN change scenario is also supported. In case of NR-DC to NR-DC handover, direct data forwarding from source SN to target MN, from source SN to target SN and from source MN to target SN is supported. Direct data forwarding for inter-system handover is specified in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [3]. If a gNB and an en-gNB are involved in direct data forwarding and realised within the same network entity, inter-system handover to and from EN-DC allows direct data forwarding being performed in a node-internal way, in which case the source RAN node provides a UE context reference to the target side as described in clause 10.16. If the gNB and en-gNB are not realised within the same network entity, direct data forwarding for inter-system handover to and from en-gNB/gNB could be supported if there is direct connectivity between the two nodes. For MR-DC with 5GC, offloading of QoS flows within one PDU session may be performed between NG-RAN nodes. The handling of End Marker packets in case of NG-RAN initiated PDU session split is described in clause 10.14.3 and 10.14.4. | 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 | 8.4 |
6,493 | 5.4.1.2.4.4 Abnormal cases on the network side | The following abnormal cases can be identified: a) Expiry of timer T3560. The AMF shall, on the first expiry of the timer T3560, retransmit the AUTHENTICATION REQUEST message and shall reset and start timer T3560. This retransmission is repeated four times, i.e. on the fifth expiry of timer T3560, the AMF shall abort the EAP based primary authentication and key agreement procedure and any ongoing 5GMM specific procedure, and release the N1 NAS signalling connection. b) Lower layers indication of non-delivered NAS PDU due to handover. If the AUTHENTICATION REQUEST message could not be delivered due to an intra AMF handover and the target TA is included in the TAI list, then upon successful completion of the intra AMF handover the AMF shall retransmit the AUTHENTICATION REQUEST message. If a failure of handover procedure is reported by the lower layer and the N1 NAS signalling connection exists, the AMF shall retransmit the AUTHENTICATION REQUEST message. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.4.1.2.4.4 |
6,494 | 5.2.6.7 Nnef_TrafficInfluence service 5.2.6.7.1 General | Service description: This service provides: - Request authorization of NF Service Consumer requests. - Request parameter mapping from NF Service Consumer requests to 5GC parameters and vice versa as described in clause 5.6.7 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. - NF Service Consumer request routing (forwarding) to actual NF Service Producer to influence traffic routing decisions as described in clause 5.6.7 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") | 5.2.6.7 |
6,495 | – Phy-ParametersSharedSpectrumChAccess | The IE Phy-ParametersSharedSpectrumChAccess is used to convey the physical layer capabilities specific for shared spectrum channel access. Phy-ParametersSharedSpectrumChAccess information element -- ASN1START -- TAG-PHY-PARAMETERSSHAREDSPECTRUMCHACCESS-START Phy-ParametersSharedSpectrumChAccess-r16 ::= SEQUENCE { -- 10-32 (1-2): SS block based SINR measurement (SS-SINR) for unlicensed spectrum ss-SINR-Meas-r16 ENUMERATED {supported} OPTIONAL, -- 10-33 (2-32a): Semi-persistent CSI report on PUCCH for unlicensed spectrum sp-CSI-ReportPUCCH-r16 ENUMERATED {supported} OPTIONAL, -- 10-33a (2-32b): Semi-persistent CSI report on PUSCH for unlicensed spectrum sp-CSI-ReportPUSCH-r16 ENUMERATED {supported} OPTIONAL, -- 10-34 (3-6): Dynamic SFI monitoring for unlicensed spectrum dynamicSFI-r16 ENUMERATED {supported} OPTIONAL, -- 10-35c (4-19c): SR/HARQ-ACK/CSI multiplexing once per slot using a PUCCH (or HARQ-ACK/CSI piggybacked on a PUSCH) when SR/HARQ- -- ACK/CSI are supposed to be sent with different starting symbols in a slot for unlicensed spectrum -- 10-35 (4-19): SR/HARQ-ACK/CSI multiplexing once per slot using a PUCCH (or HARQ-ACK/CSI piggybacked on a PUSCH) when SR/HARQ- -- ACK/CSI are supposed to be sent with the same starting symbol on the PUCCH resources in a slot for unlicensed spectrum mux-SR-HARQ-ACK-CSI-PUCCH-OncePerSlot-r16 SEQUENCE { sameSymbol-r16 ENUMERATED {supported} OPTIONAL, diffSymbol-r16 ENUMERATED {supported} OPTIONAL } OPTIONAL, -- 10-35a (4-19a): Overlapping PUCCH resources have different starting symbols in a slot for unlicensed spectrum mux-SR-HARQ-ACK-PUCCH-r16 ENUMERATED {supported} OPTIONAL, -- 10-35b (4-19b): SR/HARQ-ACK/CSI multiplexing more than once per slot using a PUCCH (or HARQ-ACK/CSI piggybacked on a PUSCH) when -- SR/HARQ ACK/CSI are supposed to be sent with the same or different starting symbol in a slot for unlicensed spectrum mux-SR-HARQ-ACK-CSI-PUCCH-MultiPerSlot-r16 ENUMERATED {supported} OPTIONAL, -- 10-36 (4-28): HARQ-ACK multiplexing on PUSCH with different PUCCH/PUSCH starting OFDM symbols for unlicensed spectrum mux-HARQ-ACK-PUSCH-DiffSymbol-r16 ENUMERATED {supported} OPTIONAL, -- 10-37 (4-23): Repetitions for PUCCH format 1, 3, and 4 over multiple slots with K = 2, 4, 8 for unlicensed spectrum pucch-Repetition-F1-3-4-r16 ENUMERATED {supported} OPTIONAL, -- 10-38 (5-14): Type 1 configured PUSCH repetitions over multiple slots for unlicensed spectrum type1-PUSCH-RepetitionMultiSlots-r16 ENUMERATED {supported} OPTIONAL, -- 10-39 (5-16): Type 2 configured PUSCH repetitions over multiple slots for unlicensed spectrum type2-PUSCH-RepetitionMultiSlots-r16 ENUMERATED {supported} OPTIONAL, -- 10-40 (5-17): PUSCH repetitions over multiple slots for unlicensed spectrum pusch-RepetitionMultiSlots-r16 ENUMERATED {supported} OPTIONAL, -- 10-40a (5-17a): PDSCH repetitions over multiple slots for unlicensed spectrum pdsch-RepetitionMultiSlots-r16 ENUMERATED {supported} OPTIONAL, -- 10-41 (5-18): DL SPS downlinkSPS-r16 ENUMERATED {supported} OPTIONAL, -- 10-42 (5-19): Type 1 Configured UL grant configuredUL-GrantType1-r16 ENUMERATED {supported} OPTIONAL, -- 10-43 (5-20): Type 2 Configured UL grant configuredUL-GrantType2-r16 ENUMERATED {supported} OPTIONAL, -- 10-44 (5-21): Pre-emption indication for DL pre-EmptIndication-DL-r16 ENUMERATED {supported} OPTIONAL, ... } -- TAG-PHY-PARAMETERSSHAREDSPECTRUMCHACCESS-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
6,496 | 9.3.1 Security header type | Bits 5 to 8 of the first octet of every EPS Mobility Management (EMM) message contain the Security header type IE. This IE includes control information related to the security protection of a NAS message. The total size of the Security header type IE is 4 bits. The Security header type IE can take the values shown in table 9.3.1. Table 9.3.1: Security header type An EMM message received with the security header type encoded as 0000 shall be treated as not security protected, plain NAS message. A protocol entity sending a not security protected EMM message shall send the message as plain NAS message and encode the security header type as 0000. | 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 | 9.3.1 |
6,497 | 4.16.1.5 Successful Secondary Node Additions with SN terminated bearers | a) This measurement provides the number of successful Secondary Node Additions with SN terminated bearers. b) CC c) On transmission by the MN of an SgNB reconfiguration complete message to SN (after MN receives RRCConnectionReconfigurationComplete message) from UE with path switch. SGNB Addition Trigger Indication (TS 36.423[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 Application Protocol (X2AP) ] [10]) excludes SN change, inter-eNB HO, intra-eNB HO. d) Each measurement is an integer value. e) The measurement name has the form ENDC.SNAdditionSuccWithSnErab. f) EUtranCellFDD EUtranCellTDD 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.16.1.5 |
6,498 | 5.3.4A Connection Suspend procedure | This procedure is used by the network to suspend the connection if the UE and the network support User Plane CIoT EPS Optimisation (see TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [5]). Figure 5.3.4A-1: eNodeB initiated Connection Suspend procedure 1. The eNodeB initiates the Connection Suspend procedure to the MME, see TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [36]. The eNodeB indicates to the MME that the UE's RRC connection is to be suspended upon which MME enters ECM-IDLE. Data related to the S1AP association, UE Context and bearer context, necessary to resume the connection is kept in the eNodeB, UE and the MME. If the eNodeB supports WUS, the eNodeB should include the Information On Recommended Cells And eNodeBs For Paging in the S1 UE Context Suspend Request message; otherwise, the eNodeB may include the Information On Recommended Cells And eNodeBs For Paging in the S1 UE Context Suspend Request message. If available, the MME shall store this information to be used when paging the UE. The eNodeB includes Information for Enhanced Coverage, if available, in the S1 UE Context Suspend Request message. If the PLMN has configured secondary RAT reporting and the eNodeB has Secondary RAT usage data to report, the Secondary RAT usage data is included. If Dual Connectivity was activated by that eNodeB at the time of the Connection Suspend or earlier by that eNodeB, the eNodeB shall include the last known PSCell ID and the time elapsed since the Dual Connectivity was released. If Service Gap Control is being applied to the UE (see clause 4.3.17.9) and the Service Gap timer is not already running, the Service Gap timer shall be started in the MME when entering ECM-IDLE, unless the connection was initiated after a paging of an MT event, after a TAU procedure without any active flag or signalling active flag set or after a TAU procedure for network access for regulatory prioritized services like Emergency services or exception reporting. 1a-d. If the eNodeB provided Secondary RAT usage data in step 1 and if PGW secondary RAT usage data reporting is active, the MME initiates the Secondary RAT usage data reporting procedure in clause 5.7A.3 as illustrated in figure 5.7A.3-2. 2. The MME sends a Release Access Bearers Request (Secondary RAT usage data) message to the Serving GW that requests the release of all S1-U bearers for the UE. If Secondary RAT usage data was received in step 1, Secondary RAT usage data is included in this message. The message indicates that the SGW is the target for the reporting. 3. The Serving GW releases all eNodeB 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. NOTE: Based on operator policy any received Indication of "Abnormal Release of Radio Link" may be used by Serving GW in subsequent decisions to trigger PDN charging pause if the feature has been enabled on that PDN. The Serving GW informs the MME in the Release Access Bearer Response message about release of S1-U bearers. 4. The MME sends an S1AP: UE Context Suspend Response message to the eNodeB to successfully terminate the Connection Suspend procedure initiated by the eNodeB, see TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [36]. 5. The eNodeB sends RRC message to suspend the RRC Connection towards 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 ] [5]). If Service Gap Control is being applied for the UE (see clause 4.3.17.9) and the Service Gap timer is not already running, the Service Gap timer shall be started in the UE when entering ECM-IDLE, unless the connection was initiated as a response to paging of an MT event, after a TAU procedure without any active flag or signalling active flag set or after a TAU procedure for network access for regulatory prioritized services like Emergency services or exception reporting. | 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.4A |
6,499 | 4.15.3.2.13 Handling AF requests when the UE is identified via UE addressing information | An AF may request, via the NEF, the Event Exposure (as defined in clause 4.15.3) or the parameter provisioning (as defined in clause 4.15.6) targeting an individual UE, identifying the target UE by providing UE addressing information. In this case the 5GC first needs to retrieve a UE Identifier based on: - the UE addressing information as provided by the AF: this may correspond to an UE IP address as allocated by 5GC or to a MAC address of the UE (when Ethernet PDU Sessions are targeted), - the corresponding DNN and/or S-NSSAI: this may have been provided by the AF or, alternatively, determined by the NEF using the identity of the AF. The NEF retrieves the UE Identifier by executing step 2 to 6 of the AF specific UE Identifier retrieval procedure described in clause 4.15.10. Once this is done, the 5GC may carry out the action requested by the AF and may deliver back to the AF an External Identifier representing an AF specific UE Identifier (as defined in TS 23.501[ System architecture for the 5G System (5GS) ] [2]). This AF specific UE Identifier may later be used by the AF to issue further requests about the same UE. NOTE: The AF can use UE addressing information to identify the UE in a subscription request, but once received, this UE addressing information is translated into a GPSI and then the 5GC considers the subscription is associated with the GPSI and not with the UE address any more. The AF may have its own means to maintain the AF specific UE Identifier through, e.g. an AF session. After the retrieval of an AF specific UE Identifier the AF shall not keep maintaining a mapping between the returned AF specific UE Identifier and the UE IP address as this mapping may change. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.15.3.2.13 |
6,500 | 16a.3a.2 Accounting Update | During the life of a bearer some information related to this bearer may change. Upon occurrence of the following events the P-GW may send an Accounting Request (Interim) to the Diameter server: RAT change, S-GW address change and QoS change. Interim updates are also used when the IPv4 address is allocated/released/re-allocated for deferred IPv4 addressing for the PDN type IPv4v6. When the P-GW receives a signalling request (e.g. Modify Bearer Request in case of GTP-based S5/S8) that indicates the occurrence of one of these chargeable events, the P-GW may send an Accounting Request (Interim) to the Diameter server to update the necessary information related to this bearer. The P-GW need not wait for the Diameter Accounting Answer message from the Diameter server before sending the response for the triggering signalling message (e.g. Modify Bearer Response). The P-GW may delete the bearer if the Accounting Answer is not received from the Diameter server. The P-GW may also send interim updates at the expiry of an operator configured time limit. The message flow in figure 25d.2 provides an example for Diameter Accounting Update procedure on Sgi interface, which is applicable for GTP based S5/S8: Figure 25d.2: Diameter accounting update for bearer modification | 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 | 16a.3a.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.