Search is not available for this dataset
doc_id
int64 1
6.72k
⌀ | Section
stringlengths 5
247
⌀ | Content
stringlengths 501
147k
⌀ | Source
stringclasses 456
values | Document Title
stringclasses 22
values | Working Group
stringclasses 21
values | Series Subject
stringclasses 9
values | Subclause
stringlengths 1
13
⌀ |
|---|---|---|---|---|---|---|---|
4,701 | 10.5.3.7 Follow-on Proceed | The purpose of the Follow-on Proceed information element is to indicate that an MM connection may be established on an existing RR connection. The Follow-on Proceed information element is coded as shown in figure 10.5.82/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The Follow-on Proceed is a type 2 information element. Figure 10.5.82/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Follow-on Proceed 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.7 |
4,702 | 4.5.5.2 Distribution of RACH preambles sent | This measurement provides the distribution of number of RACH preambles sent by the UE as reported by the UEs inside the UEInformationResponse message CC This measurement is obtained by incrementing the measurement bin corresponding to the value of IE numberOfPreamblesSent-r9 ([8] clause 6.2.2) reported by UE inside UEInformationResponse message. The measurement is incremented each time a UEInformationResponse message containing rach-Report-r9 IE is received. Each measurement is an integer value. RRU.RachPreambleDist.BinX where BinX represents the bin. Note: Number of bins and the range for each bin is left to implementation. 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.5.5.2 |
4,703 | 5.4A Short Physical Uplink Control Channel 5.4A.1 General | The short physical uplink control channel, SPUCCH, carries uplink control information. Simultaneous transmission of SPUCCH and PUSCH from the same UE where both SPUCCH and PUSCH is using either slot or subslot transmission is supported if enabled by higher layers (see simultaneousPUCCH-PUSCH in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [9]). For frame structure type 2 and in UpPTS, transmission of SPUCCH is not supported. SPUCCH supports multiple formats as shown in Table 5.4A-1 and Table 5.4A-2 with different number of bits carried by each SPUCCH. Table 5.4A-1: SPUCCH formats for slot transmission Table 5.4A-2: SPUCCH formats for subslot transmission The quantity represents the bandwidth of the SPUCCH format 4 as defined by clause 5.4A.4.1, and and are defined in Table 5.4A.4.1-1 and Table 5.4A.4.2-1, respectively. SPUCCH formats 1/1a/1b use a cyclic shift, , which varies with the symbol number and the slot number as described in clause 5.4. | 3GPP TS 36.211 | Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation | RAN1 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 5.4A |
4,704 | 8.7 Aggregate Maximum Bit Rate (AMBR) | Aggregate Maximum Bit Rate (AMBR) is transferred via GTP tunnels. The sending entity copies the value part of the AMBR into the Value field of the AMBR (APN-AMBR) IE. AMBR is defined in clause 9.9.4.2 of 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [23], but it shall be encoded as shown in Figure 8.7-1 as Unsigned32 binary integer values in kbps (1000 bits per second). Figure 8.7-1: Aggregate Maximum Bit Rate (AMBR) The APN-AMBR for uplink and the APN-AMBR for downlink may require converting values in bits per second to kilo bits per second when the APN-AMBR for uplink and the APN-AMBR for downlink are received from an interface other than GTPv2 interface. If such conversions result in fractions, then the value of APN-AMBR for uplink and the APN-AMBR for downlink shall be rounded upwards. NOTE: The encoding in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [23] is different from the encoding within this specification. | 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.7 |
4,705 | C.2 Null-scheme | The null-scheme shall be implemented such that it returns the same output as the input, which applies to both encryption and decryption. When using the null-scheme, the SUCI does not conceal the SUPI and therefore the newly generated SUCIs do not need to be fresh. NOTE 1: The reason for mentioning the non-freshness is that, normally, in order to attain unlinkability (i.e., to make it infeasible for over-the-air attacker to link SUCIs together), it is necessary for newly generated SUCIs to be fresh. But, in case of the null-scheme, the SUCI does not conceal the SUPI. So unlinkability is irrelevant. NOTE 2: The null-scheme provides no privacy protection. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | C.2 |
4,706 | 4.14.2.2 Number of successful WLAN additions to the LWIP WLAN mobility set | a) This measurement provides the number of successful WLAN additions to the LWIP WLAN mobility set. b) CC c) On receipt of RRCConnectionReconfigurationComplete message corresponding to transmitted RRCConnectionReconfiguration message which includes the wlan-ToAddList in the lwip-MobilityConfig of lwip-Configuration information element (see TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8]). d) An integer value e) LWI.LwipWlanAddSucc f) WLANMobilitySet 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.14.2.2 |
4,707 | 4.7.7.9 Handling of keys at intersystem change from A/Gb mode to Iu mode | At an inter-system change from A/Gb mode to Iu mode, ciphering and integrity may be started (see 3GPP TS 25.331[ None ] [23c]) without any new authentication and ciphering procedure. Deduction of the appropriate security keys for ciphering and integrity check in Iu mode, depends on the current GSM/UMTS security context stored in the MS and the network. The ME shall handle the GPRS UMTS ciphering key and the GPRS UMTS integrity key according to table 4.7.7.9.1. Table 4.7.7.9.1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Inter-system change from A/Gb mode to Iu mode NOTE: A USIM with UMTS security context, passes the GPRS UMTS ciphering key, the GPRS UMTS integrity key and the derived GPRS GSM ciphering key to the ME independent on the current radio access being UTRAN or GERAN. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.7.7.9 |
4,708 | 9.11.3.98 Type 6 IE container | The purpose of the Type 6 IE container information element is to transfer type 6 IEs of format TLV-E explicitly specified for inclusion in this information element for the respective message. NOTE: Use of this information element is intended only for type 6 IEs added to a message in Rel-18 or later. The rules for the IEI value encoding specified in 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [11], subclause 11.2.4, are not applicable for the IEIs of the type 6 IEs within the Type 6 IE container information element. These IEIs can take any value in the range 00 to FF (hexadecimal). The type 6 IE container information element is coded as shown in figure 9.11.3.98.1, figure 9.11.3.98.2 and table 9.11.3.98.1. The type 6 IE container is a type 6 information element with a minimum length of 6 octets. Figure 9.11.3.98.1: Type 6 IE container information element Figure 9.11.3.98.2: Type 6 IE container contents Table 9.11.3.98.1: Type 6 IE container contents | 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.98 |
4,709 | K.2.5 UE mobility | A number of distinct UE mobility scenarios can be identified given the following assumptions: - multiple eNodeBs can be configured to be served by a single Local EPC; - a single dedicated PLMN-Id will be advertised by all eNodeBs operating in IOPS mode (of a given public safety authority/operator); - the TACs broadcast by cells (eNodeBs) served by different Local EPCs will be different. The mobility scenarios that can be distinguished are: 1. UE transitions from a cell controlled by the normal macro EPC to a cell operating in IOPS mode; 2. UE transitions from a cell operating in IOPS mode to a cell controlled by the normal macro EPC; 3. UE transitions from a cell operating in IOPS mode whose eNodeB is served by one Local EPC to a cell also operating in IOPS mode whose eNodeB is served by a different Local EPC (Inter-IOPS network cell transition); 4. UE transitions between cells operating in IOPS mode whose eNodeB(s) are served by the same Local EPC (Intra-IOPS network cell transition). The expected mobility behaviour in each of these scenarios is summarised in Table K.2.5-1. Table K.2.5-1: UE mobility behaviour | 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") | K.2.5 |
4,710 | 4 Overview | Unlike previous 3GPP systems that attempted to provide a 'one size fits all' system, the 5G system is expected to be able to provide optimized support for a variety of different services, different traffic loads, and different end user communities. Various industry white papers, most notably, the NGMN 5G White Paper [2], describe a multi-faceted 5G system capable of simultaneously supporting multiple combinations of reliability, latency, throughput, positioning, and availability. This technology revolution is achievable with the introduction of new technologies, both in access and the core, such as flexible, scalable assignment of network resources. In addition to increased flexibility and optimization, a 5G system needs to support stringent KPIs for latency, reliability, throughput, etc. Enhancements in the radio interface contribute to meeting these KPIs as do enhancements in the core network, such as network slicing, in-network caching and hosting services closer to the end points. A 5G system also supports new business models such as those for IoT and enterprise managed networks. Drivers for the 5G KPIs include services such as Uncrewed Aerial Vehicle (UAV) control, Augmented Reality (AR), and factory automation. Network flexibility enhancements support self-contained enterprise networks, installed and maintained by network operators while being managed by the enterprise. Enhanced connection modes and evolved security facilitate support of massive IoT, expected to include tens of millions of UEs sending and receiving data over the 5G network. Flexible network operations are the mainstay of the 5G system. The capabilities to provide this flexibility include network slicing, network capability exposure, scalability, and diverse mobility. Other network operations requirements address the necessary control and data plane resource efficiencies, as well as network configurations that optimize service delivery by minimizing routing between end users and application servers. Enhanced charging and security mechanisms handle new types of UEs connecting to the network in different ways. The enhanced flexibility of the 5G system also allows to cater to the needs of various verticals. For example, the 5G system introduces the concept of non-public networks providing exclusive access for a specific set of users and specific purpose(s). Non-public networks can, depending on deployment and (national) regulations, support different subsets of 5G functionality. In this specification 5G network requirements apply to both NPNs and PLMNs, unless specified otherwise. Additionally, there are specific requirements dedicated only to NPNs or PLMNs, which are indicated accordingly. More information can be found in Section 6.25. Mobile Broadband (MBB) enhancements aim to meet a number of new KPIs. These pertain to high data rates, high user density, high user mobility, highly variable data rates, deployment, and coverage. High data rates are driven by the increasing use of data for services such as streaming (e.g. video, music, and user generated content), interactive services (e.g. AR), and IoT. These services come with stringent requirements for user experienced data rates as well as associated requirements for latency to meet service requirements. Additionally, increased coverage in densely populated areas such as sports arenas, urban areas, and transportation hubs has become essential for pedestrians and users in urban vehicles. New KPIs on traffic and connection density enable both the transport of high volumes of data traffic per area (traffic density) and transport of data for a high number of connections (e.g. UE density or connection density). Many UEs are expected to support a variety of services which exchange either a very large (e.g. streaming video) or very small (e.g. data burst) amount of data. The 5G system will handle this variability in a resource efficient manner. All of these cases introduce new deployment requirements for indoor and outdoor, local area connectivity, high user density, wide area connectivity, and UEs travelling at high speeds. Another aspect of 5G KPIs includes requirements for various combinations of latency and reliability, as well as higher accuracy for positioning. These KPIs are driven by support for both commercial and public safety services. On the commercial side, industrial control, industrial automation, UAV control, and AR are examples of those services. Services such as UAV control will require more precise positioning information that includes altitude, speed, and direction, in addition to horizontal coordinates. Support for Massive Internet of Things (MIoT) brings many new requirements in addition to those for the enhanced KPIs. The expansion of connected things introduces a need for significant improvements in resource efficiency in all system components (e.g. UEs, IoT devices, radio, access network, core network). The 5G system also aims to enhance its capability to meet KPIs that emerging V2X applications require. For these advanced applications, the requirements, such as data rate, reliability, latency, communication range and speed, are made more stringent. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 4 |
4,711 | 4.11.0a.2a.9 UE Policy Association termination initiated by the PCF for a UE | The procedure is based on clause 4.16.13.2 (UE Policy Association Termination initiated by the PCF procedure) with the following differences: In the non-roaming case, the V-PCF is not involved, the AMF is replaced by the PCF for the PDU Session, and the role of the H-PCF is performed by the PCF for the UE. For the LBO roaming scenarios, the AMF is replaced by the V-PCF for the PDU Session, the role of the V-PCF is performed by the V-PCF for the UE. In the Home Routed roaming scenario, the V-PCF is not involved. The AMF is replaced by the PCF for PDU Session in HPLMN, and the role of the H-PCF for the UE is performed by the PCF for the UE in HPLMN. When the UE is in EPS, the UE Policy Association has been established by the (V-) PCF for PDU Session as described in clause 4.11.0a.2a.5. - Step 4: Change the AMF to the PCF for PDU Session. The PCF for UE may notify the PCF for PDU Session of the removal of the UE Policy Association via Npcf_UEPolicyControl_UpdateNotify service operation. - Step 5: Change the AMF to the PCF for PDU Session. - Step 6: Change AMF to the PCF for PDU Session and refer to the step 2 to step 5 in clause 4.11.0a.2a.8. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.11.0a.2a.9 |
4,712 | 4.4.5 Ciphering of NAS signalling messages | The use of ciphering in a network is an operator option subject to AMF configuration. When operation of the network without ciphering is configured, the AMF shall indicate the use of "null ciphering algorithm" 5G-EA0 (see subclause 9.11.3.34) in the current 5G NAS security context for all UEs. For setting the security header type in outbound NAS messages, the UE and the AMF shall apply the same rules irrespective of whether the "null ciphering algorithm" or any other ciphering algorithm is indicated in the 5G NAS security context. When the UE establishes a new N1 NAS signalling connection, it shall apply security protection to the initial NAS message as described in subclause 4.4.6. The UE shall start the ciphering and deciphering of NAS messages when the secure exchange of NAS messages has been established for an N1 NAS signalling connection. From this time onward, unless explicitly defined, the UE shall send all NAS messages ciphered until the N1 NAS signalling connection is released, or the UE performs inter-system change to S1 mode. The AMF shall start ciphering and deciphering of NAS messages as described in subclause 4.4.2.5. From this time onward, except for the SECURITY MODE COMMAND message, the AMF shall send all NAS messages ciphered until the N1 NAS signalling connection is released, or the UE performs inter-system change to S1 mode. Ciphering is never applied directly to 5GSM messages, but to the 5GMM message in which the 5GSM message is included. Once the encryption of NAS messages has been started between the AMF and the UE, the receiver shall discard the unciphered NAS messages which shall have been ciphered according to the rules described in this specification. If the "null ciphering algorithm" 5G-EA0 has been selected as a ciphering algorithm, the NAS messages with the security header indicating ciphering are regarded as ciphered. Details of ciphering and deciphering of NAS signalling messages are specified in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]. | 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.4.5 |
4,713 | 4.7.3.1.3 GPRS attach accepted by the network | During an attach for emergency bearer services, if not restricted by local regulations, the network 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. If the GPRS attach request is accepted by the network, an ATTACH ACCEPT message is sent to the MS. In A/Gb mode, if the MS indicates support of integrity protection in the MS network capability IE in the ATTACH REQUEST message, and if the network supports integrity protection, then the network shall store all octets received from the MS in the MS network capability IE and in the MS Radio Access Capability IE, up to the maximum length defined for the respective information element. NOTE 1: The network needs to store the MS network capability IE and the MS Radio Access Capability IE exactly as received from the MS and network is not allowed to ignore the "higher" octets sent by the MS even if the network does not support any features indicated in the higher octets. Otherwise the replay check of the MS network capability and the MS Radio Access Capability will fail in the MS. In A/Gb mode, if a UMTS security context is available in the network and if the MS indicates support of integrity protection in the ATTACH REQUEST message and the network supports integrity protection, and if integrity protection of the ATTACH REQUEST message is successfully verified in the LLC layer in the network, then if the network decides to re-authenticate the MS or select a new integrity algorithm or ciphering algorithm, the network shall initiate an authentication and ciphering procedure. In A/Gb mode, if a UMTS security context is available in the network and if the MS indicates support of integrity protection in the ATTACH REQUEST message and the network supports integrity protection if integrity protection of the ATTACH REQUEST message is successfully verified in the LLC layer in the network , the network may decide to continue using the stored: GPRS GSM Kint integrity key, the GPRS GSM Kc128 ciphering key, the GPRS GSM ciphering algorithm and the GPRS GSM integrity algorithm in the LLC layer without initiating an authentication and ciphering procedure. If the MS and network continue to use the same ciphering mode as when the MS was previously attached to the network, ciphering or no ciphering, the ciphering mode is re-established without the need to run an authentication and ciphering procedure. The network shall replay the MS network capability IE and the MS radio access capability IE received from the MS in the ATTACH REQUEST message, by including the MS network capability IE and the MS radio access capability IE in the ATTACH ACCEPT message to the MS. The GMM layer in the network shall assign the stored GPRS GSM Kint key, the GPRS GSM Kc128 key, the GPRS GSM integrity algorithm and the GPRS GSM ciphering algorithm to the LLC layer. The GMM layer in the network shall then indicate to the LLC layer that it shall start integrity protection and ciphering in the LLC layer before sending the ATTACH ACCEPT message to the MS. If the integrity protection of the ATTACH REQUEST message is not successfully verified in the LLC layer or if the ATTACH REQUEST message is received without integrity protection, then the network shall progress the ATTACH REQUEST message and initiate an authentication and ciphering procedure in order to authenticate the MS and activate integrity protection and ciphering in the MS. In A/Gb mode, if a UMTS security context is available in the network and if the MS indicates support of integrity protection in the ATTACH REQUEST message and the network supports integrity protection, and if the network is not able to verify the message authentication code in the LLC layer protecting the ATTACH REQUEST message, due to the LLC layer at the network not having been configured yet with the integrity key and integrity algorithm for this MS, then the network shall progress the ATTACH REQUEST message at GMM layer anyway. If the CKSN included in the ATTACH REQUEST message belongs to an UMTS security context available in the network, then the network may re-establish integrity protection and ciphering of layer 3 signalling messages in the LLC layer without initiating an authentication and ciphering procedure. In A/Gb mode, if the MS indicates support of integrity protection of user plane data in the MS network capability IE in the ATTACH REQUEST message, and if the network supports and accepts integrity protection of user plane data, then the network shall indicate integrity protection of user plane data to the MS in the ATTACH ACCEPT message. The MS shall indicate to the LLC layer to start integrity protection of user plane data after the reception of the ATTACH ACCEPT message. The same GPRS GSM Kint key and the same GPRS GSM integrity algorithm used for integrity protection of layer 3 signalling messages shall be used for integrity protection of user plane data in the LLC layer. The network shall indicate to the LLC layer to start integrity protection of user plane data after sending off the ATTACH ACCEPT message to the MS. If the network does not indicate to the MS in the ATTACH ACCEPT message that it accepts the use of integrity protection of user plane, and if the MS does not accept such a network, then the MS shall detach from the network. The P-TMSI reallocation may be part of the GPRS attach procedure. When the ATTACH REQUEST includes the IMSI or IMEI, the SGSN shall allocate the P-TMSI. The P-TMSI that shall be allocated is then included in the ATTACH ACCEPT message together with the routing area identifier. The network shall, in this case, change to state GMM-COMMON-PROCEDURE-INITIATED and shall start timer T3350 as described in subclause 4.7.6. Furthermore, the network may assign a P-TMSI signature for the GMM context which is then also included in the ATTACH ACCEPT message. If the LAI or PLMN identity that has been transmitted in the ATTACH ACCEPT message is a member of any of the "forbidden" lists, any such entry shall be deleted. If the attach procedure is for emergency bearer services, the "forbidden" lists shall remain unchanged. Additionally, the network shall include the radio priority level to be used by the MS for mobile originated SMS transfer in the ATTACH ACCEPT message. In a shared network, if the MS is a network sharing supporting MS, the network shall indicate the PLMN identity of the CN operator that has accepted the GPRS attach request in the RAI contained in the ATTACH ACCEPT message; if the MS is a network sharing non-supporting MS, the network shall indicate the PLMN identity of the common PLMN (see 3GPP TS 23.251[ Network sharing; Architecture and functional description ] [109]). If the PLMN identity of the common PLMN included in the RAI does not identify the CN operator that has accepted the GPRS attach request, the network may include the PLMN identity of the CN operator that has accepted the GPRS attach request in the ATTACH ACCEPT message. In a multi-operator core network (MOCN) with common GERAN, the network shall indicate in the RAI the common PLMN identity (see 3GPP TS 23.251[ Network sharing; Architecture and functional description ] [109]). If the common PLMN identity included in the RAI does not identify the CN operator that has accepted the GPRS attach request, the network may include the PLMN identity of the CN operator that has accepted the GPRS attach request in the ATTACH ACCEPT message. If the MS has indicated in the ATTACH REQUEST message that it supports PS inter-RAT handover from GERAN to UTRAN Iu mode, the network may include in the ATTACH ACCEPT message a request to provide the Inter RAT information container. If the MS has included the MS network capability IE or the UE network capability IE or both in the ATTACH REQUEST message, the network shall store all octets received from the MS, up to the maximum length defined for the respective information element. NOTE 2: This information is forwarded to the new SGSN during inter-SGSN handover or to the new MME during intersystem handover to S1 mode. If the DRX parameter was included in the DRX Parameter IE in the ATTACH REQUEST message, the network shall replace any stored DRX parameter with the received parameter and use it for the downlink transfer of signalling and user data. The network 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 network supports and accepts the use of eDRX. In A/Gb mode, the Cell Notification information element shall be included in the ATTACH ACCEPT message by the network which indicates that the Cell Notification is supported by the network. In Iu mode, the network should prolong the PS signalling connection if the mobile station has indicated a follow-on request pending in ATTACH REQUEST. The network may also prolong the PS signalling connection without any indication from the mobile terminal. The MS, receiving an ATTACH ACCEPT message, stores the received routing area identification, stops timer T3310, resets the GPRS attach attempt counter, resets the routing area updating attempt counter, resets the service request attempt counter, enters state GMM-REGISTERED and sets the GPRS update status to GU1 UPDATED. If the message contains a P-TMSI, the MS shall use this P-TMSI as the new temporary identity for GPRS services. In this case, an ATTACH COMPLETE message is returned to the network. The MS shall delete its old P-TMSI and shall store the new one. If no P-TMSI has been included by the network in the ATTACH ACCEPT message, the old P-TMSI, if any available, shall be kept. If the message contains a P-TMSI signature, the MS shall use this P-TMSI signature as the new temporary signature for the GMM context. The MS shall delete its old P-TMSI signature, if any is available, and shall store the new one. If the message contains no P-TMSI signature, the old P-TMSI signature, if available, shall be deleted. If the network supports delivery of SMS via GPRS (3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [74]) and this delivery is enabled (see 3GPP TS 29.272[ Evolved Packet System (EPS); Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) related interfaces based on Diameter protocol ] [150]), then the network shall include the Additional network feature support IE in the ATTACH ACCEPT message and set the GPRS-SMS indicator. If the network supports the extended protocol configuration options IE and the MS indicated support of the extended protocol configuration options IE, then the network shall include the Additional network feature support IE in the ATTACH ACCEPT message and set the ePCO IE indicator to "extended protocol configuration options IE supported". Upon receiving the ATTACH ACCEPT message an MS supporting S1 mode shall set the TIN to "P-TMSI". If the network has requested the provision of Inter RAT handover information, the MS shall return an ATTACH COMPLETE message including the Inter RAT handover information IE to the network. The network may also send a list of "equivalent PLMNs" in the ATTACH ACCEPT message. Each entry of the list contains a PLMN code (MCC+MNC). The mobile station shall store the list, as provided by the network, and if the GPRS attach procedure is not for emergency bearer services, any PLMN code that is already in the "forbidden PLMN" list shall be removed from the "equivalent PLMNs" list before it is stored by the mobile station. If the mobile station is operating in MS operation mode C or the mobile station is supporting S1 mode, it shall also remove any PLMN code that is already in the list of "forbidden PLMNs for GPRS service" before storing the list. In addition the mobile station shall add to the stored list the PLMN code of the registered PLMN that sent the list. All PLMNs in the stored list shall be regarded as equivalent to each other for PLMN selection, cell selection/re-selection and handover. The stored list in the mobile station shall be replaced on each occurrence of the ATTACH ACCEPT message. If no list is contained in the message, then the stored list in the mobile station shall be deleted. An MS attached for emergency bearer services shall delete the stored list when the MS enters the state GMM-DEREGISTERED. The list shall be stored in the mobile station while switched off so that it can be used for PLMN selection after switch on. The network 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 network supports and accepts the use of PSM. If the network supports and accepts the use of PSM, and the MS included the T3312 extended value IE in the ATTACH REQUEST message, then the network shall take into account the T3312 value requested when providing the Periodic RA update timer IE and the T3312 extended value IE in the ATTACH ACCEPT message. NOTE 3: Besides the value requested by the MS, the network can take local configuration into account when selecting a value for T3312 (see 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [74] subclause 5.3.13.54). In A/Gb mode, if the MS indicates support for restriction on use of enhanced coverage in the ATTACH REQUEST message, and the network restricts enhanced coverage for the MS, then the network shall set the RestrictEC bit to "Enhanced coverage restricted" in the Additional network feature support IE of the ATTACH ACCEPT message. In Iu mode, if the network wishes to prolong the PS signalling connection (for example, if the mobile station has indicated "follow-on request pending" in ATTACH REQUEST message) the network shall indicate the "follow-on proceed" in the ATTACH ACCEPT message. If the network wishes to release the PS signalling connection, the network shall indicate "no follow-on proceed" in the ATTACH ACCEPT message. After that in Iu mode, the mobile station shall act according to the follow-on proceed flag included in the Attach result information element in the ATTACH ACCEPT message (see subclause 4.7.13). In A/Gb mode, if the ATTACH ACCEPT message contains the Cell Notification information element, then the MS shall start to use the LLC NULL frame to perform cell updates. The network receiving an ATTACH COMPLETE message stops timer T3350, changes to GMM-REGISTERED state and considers the P-TMSI sent in the ATTACH ACCEPT message as valid. If the ATTACH ACCEPT message contains the T3312 extended value IE, then the MS shall use the value in T3312 extended value IE as periodic routing area update timer (T3312). If the ATTACH ACCEPT message does not contain T3312 extended value IE, then the MS shall use the value in the Periodic RA update timer IE as periodic routing area update timer (T3312). If the ATTACH ACCEPT message contains the T3324 value IE, then the MS shall use the included timer value for T3324 as specified in subclause 4.7.2.8. If the ATTACH ACCEPT message contains the DCN-ID IE, then the MS 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 described in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120], annex C. In a shared network or in a multi-operator core network (MOCN) with common GERAN, if the ATTACH ACCEPT message contains the DCN-ID IE and the PLMN identity of the CN operator IE, the MS shall store the included DCN-ID value with the PLMN identity indicated in the PLMN identity of the CN operator IE, and the included DCN-ID value with the PLMN identity indicated in the RAI in a DCN-ID list in a non-volatile memory in the ME as described in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120], annex C. If the MS receives the ATTACH ACCEPT message from a PLMN for which a PLMN-specific attempt counter or PLMN-specific PS-attempt counter is maintained (see subclause 4.1.1.6A), then the MS shall reset these counters. If the MS maintains a counter for "SIM/USIM considered invalid for GPRS services", then the MS shall reset this counter. The network may also send a Local Emergency Numbers List with local emergency numbers in the ATTACH ACCEPT, by including the Emergency Number List IE. The mobile equipment shall store the Local Emergency Numbers List, as provided by the network. The Local Emergency Numbers List stored in the mobile equipment shall be replaced on each receipt of the Emergency Number List IE. The received Local Emergency Numbers List shall be provided to the upper layers. The emergency number(s) received in the Emergency Number List IE are valid only in networks in the same country as the cell on which this IE is received. If no list is contained in the ATTACH ACCEPT message, then the stored Local Emergency Numbers List in the mobile equipment shall be kept, except if the mobile equipment has successfully registered to a PLMN in a country different from that of the PLMN that sent the Local Emergency Numbers List. The mobile equipment shall use the stored Local Emergency Numbers List of emergency numbers received from the network in addition to the emergency numbers stored on the SIM/USIM or ME to detect that the number dialled is an emergency number. NOTE 4: The mobile equipment may use the Local Emergency Numbers List to assist the end user in determining whether the dialled number is intended for an emergency service or for another destination, e.g. a local directory service. The possible interactions with the end user are implementation specific. NOTE 5: An MS that supports procedures specified in 3GPP TS 24.302[ Access to the 3GPP Evolved Packet Core (EPC) via non-3GPP access networks; Stage 3 ] [156], can get additional local emergency numbers through those procedures, which can be used based on operator policy (see 3GPP TS 24.302[ Access to the 3GPP Evolved Packet Core (EPC) via non-3GPP access networks; Stage 3 ] [156]) to detect that the number dialled is an emergency number. The Local Emergency Numbers List shall be deleted at switch off and removal of the SIM/USIM. The mobile equipment shall be able to store up to ten local emergency numbers received from the network. If the MS has initiated the attach procedure due to manual CSG selection and receives an ATTACH ACCEPT message, and the MS sent the ATTACH REQUEST message in a CSG cell, the MS shall check if the CSG ID and associated PLMN identity of the cell are contained in the Allowed CSG list. If not, the MS shall add that CSG ID and associated PLMN identity to the Allowed CSG list and the MS 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. In A/Gb mode, if a UMTS security context is available, if the MS indicates support of integrity protection in the ATTACH REQUEST message and the network supports integrity protection, then if the MS receives replayed capabilities IE’s in ATTACH ACCEPT, then the MS shall check if the replayed MS network capability IE and replayed MS Radio Access Capability IE received in the ATTACH ACCEPT message has not been altered compared to the MS network capability IE and the MS Radio Access Capability IE that the MS sent to the network in ATTACH REQUEST message. If the replayed MS network capability IE and the replayed MS Radio Access Capability IE are not the same, then the MS shall ignore the ATTACH ACCEPT message. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.7.3.1.3 |
4,714 | 4.3.2.13 Derivation of keys at CS to PS SRVCC handover from A/Gb mode to Iu mode | At change from A/Gb mode to Iu mode due to CS to PS SRVCC handover (see 3GPP TS 23.216[ Single Radio Voice Call Continuity (SRVCC); Stage 2 ] [126]), the MS shall derive a UMTS security context for the PS domain from the current GSM or UMTS security context for the CS domain. At change from A/Gb mode to Iu mode due to CS to PS SRVCC handover, ciphering may be started and integrity protection shall be started (see 3GPP TS 25.331[ None ] [23c]) without any new authentication procedure. Derivation of the appropriate security keys for ciphering and integrity protection for the PS domain in Iu mode depends on the current GSM or UMTS security context for the CS domain stored in the MS and the network. The ME shall handle the PS UMTS ciphering key and the PS UMTS integrity key according to table 4.3.2.13.1. Table 4.3.2.13.1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : CS to PS SRVCC handover from A/Gb mode to Iu mode The network shall replace an already established GSM or UMTS security context for the PS domain, if any, when the CS to PS SRVCC handover from A/Gb mode to Iu mode has been completed successfully. If the CS to PS SRVCC handover from A/Gb mode to Iu mode has not been completed successfully, the MS and the network shall delete the new derived GSM or UMTS security context for the PS domain. Additionally, the network shall delete the already established GSM or UMTS security context for the PS domain, if the GPRS CKSN of the already established GSM or UMTS security context is equal to the GPRS CKSN of the new derived GSM or UMTS security context for the PS domain. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.3.2.13 |
4,715 | A.16 Monitoring of Energy Saving | Beside monitoring of the energy consumption it is also important to differentiate if the cell unavailability or the failure of the RRC connection establishment happens because of Energy Saving as Energy Saving Management feature is by the Operator on purpose. Therefore such failures should be distinguishable from other network failures, therefore should be counted separately. With the separate cell unavailability counter due to Energy Saving makes it possible to deduct the cell downtime due to Energy Savings from the total cell outage. | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | A.16 |
4,716 | 28.3.2.9 SMF Set FQDN | An SMF Set within an operator's network is identified by its NF Set ID as defined in clause 28.12, with NFType set to "smf". For an SMF Set within an operator's PLMN, a subdomain name shall be derived from the MNC and MCC by adding the label "smfset" to the beginning of the Home Network Realm/Domain (see clause 28.2). The SMF Set FQDN shall be constructed as follows: set<Set Id>.smfset.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 Set FQDN. - <Set Id> is the string representing the Set ID part within the NF Set ID defined in clause 28.12. EXAMPLE: "set12. smfset.5gc.mnc012.mcc345.3gppnetwork.org" (for the SMF set from MCC 345, MNC 12 and SetID "12") NOTE: The labels preceding the ".3gppnetwork.org" domain correspond to the NF Set ID definition in clause 28.12. For an SMF Set within an operator's Stand-alone Non-Public Network (SNPN), the SMF Set FQDN shall be constructed from its Network Identifier (NID), MNC and MCC or an SNPN domain name pre-configured in the NF, as follows: set<Set Id>.smfset.5gc.nid<NID>.mnc<MNC>.mcc<MCC>.3gppnetwork.org or set<Set Id>.smfset.<SNPN domain name> where - <MNC> and <MCC> shall be encoded as specified above; - NID shall be encoded as hexadecimal digits as specified in clause 12.7; - <SNPN domain name> is a domain name chosen by the SNPN operator. EXAMPLE: "set12.smfset.5gc.nid000007ed9d5.mnc012.mcc345.3gppnetwork.org" (for an SMF set from MCC 345, MNC 12, NID 000007ed9d5 (hexadecimal) and SetID "12") | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 28.3.2.9 |
4,717 | 5.30.2.10.3 Onboarding Network is a PLMN | 5.30.2.10.3.1 General A UE configured with PLMN credentials in USIM for primary authentication may register with a PLMN for the provisioning of SO-SNPN credentials. 5.30.2.10.3.2 Network selection and Registration This clause applies only when the UE is not in SNPN access mode. When the UE is using PLMN credentials for accessing a PLMN as the Onboarding Network (ONN), then regular network selection, as per TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [17] and regular initial registration procedures apply, as per TS 23.502[ Procedures for the 5G System (5GS) ] [3]. After successfully registering to the ON-PLMN, the UE is provisioned with the SO-SNPN credentials via User Plane as in clause 5.30.2.10.4.4. NOTE: When Onboarding network is a PLMN and the UE's subscription only allows for Remote Provisioning, then based on PLMN policies, the AMF can start an implementation specific timer once the UE has registered to the PLMN. Expiry of this timer triggers the AMF to deregister the UE from the PLMN. This specific timer is used to prevent registered UEs that are only allowed for Remote Provisioning from staying at the PLMN indefinitely. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.30.2.10.3 |
4,718 | – CA-ParametersNRDC | The IE CA-ParametersNRDC contains dual connectivity related capabilities that are defined per band combination. CA-ParametersNRDC information element -- ASN1START -- TAG-CA-PARAMETERS-NRDC-START CA-ParametersNRDC ::= SEQUENCE { ca-ParametersNR-ForDC CA-ParametersNR OPTIONAL, ca-ParametersNR-ForDC-v1540 CA-ParametersNR-v1540 OPTIONAL, ca-ParametersNR-ForDC-v1550 CA-ParametersNR-v1550 OPTIONAL, ca-ParametersNR-ForDC-v1560 CA-ParametersNR-v1560 OPTIONAL, featureSetCombinationDC FeatureSetCombinationId OPTIONAL } CA-ParametersNRDC-v15g0 ::= SEQUENCE { ca-ParametersNR-ForDC-v15g0 CA-ParametersNR-v15g0 OPTIONAL } CA-ParametersNRDC-v1610 ::= SEQUENCE { -- R1 18-1: Semi-static power sharing mode1 between MCG and SCG cells of same FR for NR dual connectivity intraFR-NR-DC-PwrSharingMode1-r16 ENUMERATED {supported} OPTIONAL, -- R1 18-1a: Semi-static power sharing mode 2 between MCG and SCG cells of same FR for NR dual connectivity intraFR-NR-DC-PwrSharingMode2-r16 ENUMERATED {supported} OPTIONAL, -- R1 18-1b: Dynamic power sharing between MCG and SCG cells of same FR for NR dual connectivity intraFR-NR-DC-DynamicPwrSharing-r16 ENUMERATED {short, long} OPTIONAL, asyncNRDC-r16 ENUMERATED {supported} OPTIONAL } CA-ParametersNRDC-v1630 ::= SEQUENCE { ca-ParametersNR-ForDC-v1610 CA-ParametersNR-v1610 OPTIONAL, ca-ParametersNR-ForDC-v1630 CA-ParametersNR-v1630 OPTIONAL } CA-ParametersNRDC-v1640 ::= SEQUENCE { ca-ParametersNR-ForDC-v1640 CA-ParametersNR-v1640 OPTIONAL } CA-ParametersNRDC-v1650 ::= SEQUENCE { supportedCellGrouping-r16 BIT STRING (SIZE (1..maxCellGroupings-r16)) OPTIONAL } CA-ParametersNRDC-v16a0 ::= SEQUENCE { ca-ParametersNR-ForDC-v16a0 CA-ParametersNR-v16a0 OPTIONAL } CA-ParametersNRDC-v1700 ::= SEQUENCE { -- R1 31-9: Indicates the support of simultaneous transmission and reception of an IAB-node from multiple parent nodes simultaneousRxTx-IAB-MultipleParents-r17 ENUMERATED {supported} OPTIONAL, condPSCellAdditionNRDC-r17 ENUMERATED {supported} OPTIONAL, scg-ActivationDeactivationNRDC-r17 ENUMERATED {supported} OPTIONAL, scg-ActivationDeactivationResumeNRDC-r17 ENUMERATED {supported} OPTIONAL, beamManagementType-CBM-r17 ENUMERATED {supported} OPTIONAL } CA-ParametersNRDC-v1720 ::= SEQUENCE { ca-ParametersNR-ForDC-v1700 CA-ParametersNR-v1700 OPTIONAL, ca-ParametersNR-ForDC-v1720 CA-ParametersNR-v1720 OPTIONAL } CA-ParametersNRDC-v1730 ::= SEQUENCE { ca-ParametersNR-ForDC-v1730 CA-ParametersNR-v1730 OPTIONAL } CA-ParametersNRDC-v1760 ::= SEQUENCE { ca-ParametersNR-ForDC-v1760 CA-ParametersNR-v1760 } CA-ParametersNRDC-v1800 ::= SEQUENCE { ca-ParametersNR-ForDC-v1800 CA-ParametersNR-v1800 OPTIONAL, -- R1 55-6d: Capability on the number of CCs for monitoring a maximum number of BDs and non-overlapped CCEs per span for MCG and for -- SCG when configured for NR-DC operation with Rel-16 PDCCH monitoring on all the serving cells pdcch-BlindDetectionNRDC-r18 SEQUENCE(SIZE (1..maxNrofPdcch-BlindDetection-r17)) OF PDCCH-BlindDetectionMixed1-r18 OPTIONAL } PDCCH-BlindDetectionMixed1-r18::= SEQUENCE { pdcch-BlindDetectionCG-UE-Mixed-r18 SEQUENCE{ pdcch-BlindDetectionMCG-UE-Mixed-r18 PDCCH-BlindDetectionCG-UE-Mixed-r18, pdcch-BlindDetectionSCG-UE-Mixed-r18 PDCCH-BlindDetectionCG-UE-Mixed-r18 } } -- TAG-CA-PARAMETERS-NRDC-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
4,719 | 5.1.5 Coordination between 5GMM and GMM | Coordination between 5GMM and GMM states is not required. Regardless whether the UE is operating in single-registration mode or dual-registration mode, a) if the UE considers the SIM/USIM invalid for any of: 3GPP access in N1 mode, S1 mode, A/Gb mode or Iu mode, then it considers the SIM/USIM invalid for all of them; and b) if the UE considers the USIM invalid for 5GS services for any of: 3GPP access in N1 mode, S1 mode, A/Gb mode or Iu mode, then it considers the USIM invalid for 5GS services for all of them. | 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.1.5 |
4,720 | 6.10.3A.1 Sequence generation | For any of the antenna ports , the reference-signal sequence is defined by . For non-BL/CE UEs, the pseudo-random sequence is defined in clause 7.2. The pseudo-random sequence generator shall be initialised with at the start of each subframe where - and shall be replaced by and , respectively, for the EPDCCH - and shall be replaced by and , respectively, for the SPDCCH - , , and - is configured by higher layers. The EPDCCH/SPDCCH set to which the EPDCCH/SPDCCH associated with the demodulation reference signal belong is denoted . For BL/CE UEs, the same scrambling sequence is applied per subframe to the demodulation reference signal associated with MPDCCH for a given block of subframes. The subframe number of the first subframe in each block of consecutive subframes, denoted as , satisfies . For the block of subframes, the scrambling sequence generator shall be initialised with where and is the absolute subframe number of the first downlink subframe intended for MPDCCH. The MPDCCH transmissions span consecutive subframes, including subframes that are not BL/CE DL subframes where the MPDCCH transmission is postponed. For BL/CE UEs, - if the MPDCCH transmission is associated with P-RNTI or SC-RNTI: - for frame structure type 1 and for frame structure type 2 - otherwise - for UEs assuming CEModeA (according to the definition in Clause 12 of [4]) or configured with CEModeA. - for frame structure type 1 and for frame structure type 2 for UEs assuming CEModeB (according to the definition in Clause 12 of [4]) or configured with CEModeB. The quantities and are configured by higher layers. The MPDCCH set to which the MPDCCH associated with the demodulation reference signal belong is denoted . For an MPDCCH associated with a 2+4 PRB set as defined in [4], is used to generate the scrambling sequence for the 6 PRBs as well as for the 2 PRBs and 4 PRBs. | 3GPP TS 36.211 | Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation | RAN1 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.10.3A.1 |
4,721 | 5.2.2.4.2 Actions upon reception of the SIB1 | Upon receiving the SIB1 the UE shall: 1> store the acquired SIB1; 1> if the access is for NTN: 2> if the UE is in RRC_IDLE or in RRC_INACTIVE, or if the UE is in RRC_CONNECTED while T311 is running; and 2> if the cellBarredNTN in the acquired SIB1 is set to barred or the cellBarredNTN is not included in the acquired SIB1: 3> consider the cell as barred in accordance with TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [20]; 3> perform cell re-selection to other cells on the same frequency as the barred cell as specified in TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [20], upon which the procedure ends; 1> if the access is for ATG: 2> if the UE is in RRC_IDLE or in RRC_INACTIVE, or if the UE is in RRC_CONNECTED while T311 is running; and 2> if the cellBarredNTN in the acquired SIB1 is set to barred or the cellBarredNTN is not included in the acquired SIB1: 3> consider the cell as barred in accordance with TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [20]; 3> perform cell re-selection to other cells on the same frequency as the barred cell as specified in TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [20]; 1> if the UE is a RedCap UE and it is in RRC_IDLE or in RRC_INACTIVE, or if the RedCap UE is in RRC_CONNECTED while T311 is running: 2> if intraFreqReselectionRedCap is not present in SIB1: 3> consider the cell as barred in accordance with TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [20]; 3> perform barring as if intraFreqReselectionRedCap is set to allowed, upon which the procedure ends; 2> else: 3> if the cellBarredRedCap1Rx is present in the acquired SIB1 and is set to barred and the UE is equipped with 1 Rx branch; or 3> if the cellBarredRedCap2Rx is present in the acquired SIB1 and is set to barred and the UE is equipped with 2 Rx branches; or 3> if the halfDuplexRedCapAllowed is not present in the acquired SIB1 and the UE supports only half-duplex FDD operation: 4> consider the cell as barred in accordance with TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [20]; 4> perform barring based on intraFreqReselectionRedCap as specified in TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [20], upon which the procedure ends; 1> if the UE supports NES cell DTX/DRX and it is in RRC_IDLE or in RRC_INACTIVE, or if the UE supporting NES cell DTX/DRX is in RRC_CONNECTED while T311 is running: 2> if cellBarred in the acquired MIB is set to barred: 3> if cellBarredNES is absent in the acquired SIB1: 4> consider the cell as barred in accordance with TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [20]; 4> perform cell re-selection to other cells on the same frequency as the barred cell as specified in TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [20]; 1> if the UE is an eRedCap UE and it is in RRC_IDLE or in RRC_INACTIVE, or if the eRedCap UE is in RRC_CONNECTED while T311 is running: 2> if intraFreqReselection-eRedCap is not present in SIB1: 3> consider the cell as barred in accordance with TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [20]; 3> perform barring as if intraFreqReselection-eRedCap is set to allowed upon which the procedure ends; 2> else: 3> if the cellBarred-eRedCap1Rx is present in the acquired SIB1 and is set to barred and the UE is equipped with 1 Rx branch; or 3> if the cellBarred-eRedCap2Rx is present in the acquired SIB1 and is set to barred and the UE is equipped with 2 Rx branches; or 3> if the halfDuplexRedCapAllowed is not present in the acquired SIB1 and the UE supports only half-duplex FDD operation: 4> consider the cell as barred in accordance with TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [20]; 4> perform barring based on intraFreqReselection-eRedCap as specified in TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [20] upon which the procedure ends; 1> if the cellAccessRelatedInfo contains an entry of a selected SNPN or PLMN and in case of PLMN the UE is either allowed or instructed to access the PLMN via a cell for which at least one CAG ID is broadcast: 2> in the remainder of the procedures use npn-IdentityList, trackingAreaCode, and cellIdentity for the cell as received in the corresponding entry of npn-IdentityInfoList containing the selected PLMN or SNPN; 1> else if the cellAccessRelatedInfo contains an entry with the PLMN-Identity of the selected PLMN: 2> in the remainder of the procedures use plmn-IdentityList, trackingAreaCode, trackingAreaList, and cellIdentity for the cell as received in the corresponding PLMN-IdentityInfo containing the selected PLMN; 1> if the UE in RRC_INACTIVE is configured for feature(s) that it does not support in current serving cell: 2> not use the corresponding configuration in current serving cell; NOTE 0: The requirement above applies only to UE that indicates different support of UE capabilities for TN and NTN. 1> if in RRC_CONNECTED while T311 is not running: 2> disregard the frequencyBandList, if received, while in RRC_CONNECTED; 2> forward the cellIdentity to upper layers; 2> forward the trackingAreaCode to upper layers, if included; 2> forward the trackingAreaList to upper layers, if included; 2> forward the received posSIB-MappingInfo to upper layers, if included; 2> apply the configuration included in the servingCellConfigCommon; 2> if the UE has a stored valid version of a SIB or posSIB, in accordance with clause 5.2.2.2.1, that the UE requires to operate within the cell in accordance with clause 5.2.2.1: 3> use the stored version of the required SIB or posSIB; 2> else: 3> acquire the required SIB or posSIB requested by upper layer as defined in clause 5.2.2.3.5; NOTE 1: Void. 1> else: 2> if the UE supports one or more of the frequency bands indicated in the frequencyBandList or frequencyBandListAerial for downlink for TDD, or one or more of the frequency bands indicated in the frequencyBandList or frequencyBandListAerial for uplink for FDD, and they are not downlink only bands, and 2> if the UE is IAB-MT or supports at least one additionalSpectrumEmission in the nr-NS-PmaxList or nr-NS-PmaxListAerial for a supported band in the downlink for TDD, or a supported band in uplink for FDD, and 2> if the UE supports an uplink channel bandwidth with a maximum transmission bandwidth configuration (see TS 38.101[ None ] -1 [15], TS 38.101[ None ] -2 [39], and TS 38.101[ None ] -5 [75]) which - is smaller than or equal to the carrierBandwidth (indicated in uplinkConfigCommon for the SCS of the initial uplink BWP or, for (e)RedCap UE, of the (e)RedCap-specific initial uplink BWP if configured), and which - is wider than or equal to the bandwidth of the initial uplink BWP or, for (e)RedCap UE, of the (e)RedCap-specific initial uplink BWP if configured, and 2> if the UE supports a downlink channel bandwidth with a maximum transmission bandwidth configuration (see TS 38.101[ None ] -1 [15], TS 38.101[ None ] -2 [39], and TS 38.101[ None ] -5 [75]) which - is smaller than or equal to the carrierBandwidth (indicated in downlinkConfigCommon for the SCS of the initial downlink BWP or, for (e)RedCap UE, of the (e)RedCap-specific initial downlink BWP if configured), and which - is wider than or equal to the bandwidth of the initial downlink BWP or, for (e)RedCap UE, of the (e)RedCap-specific initial downlink BWP if configured, and 2> if frequencyShift7p5khz is present and the UE supports corresponding 7.5kHz frequency shift on this band; or frequencyShift7p5khz is not present, and 2> if the UE is not a RedCap UE, or if the UE is a RedCap UE and halfDuplexRedCapAllowed is present, or if the UE is a RedCap UE and the RedCap UE supports full-duplex FDD operation on this band: 3> if neither trackingAreaCode nor trackingAreaList is provided for the selected PLMN nor the registered PLMN nor PLMN of the equivalent PLMN list: 4> consider the cell as barred in accordance with TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [20]; 4> perform cell re-selection to other cells on the same frequency as the barred cell as specified in TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [20]; 3> else if UE is IAB-MT and if iab-Support is not provided for the selected PLMN nor the registered PLMN nor PLMN of the equivalent PLMN list nor the selected SNPN nor the registered SNPN nor SNPN of the equivalent SNPN list: 4> consider the cell as barred in accordance with TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [20]; 3> else if UE is NCR-MT and if ncr-Support is not provided: 4> consider the cell as barred in accordance with TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [20]; 3> else if UE is a mobile IAB-MT and if mobileIAB-Support is not provided for the selected PLMN nor the registered PLMN nor PLMN of the equivalent PLMN list nor the selected SNPN nor the registered SNPN nor SNPN of the equivalent SNPN list: 4> consider the cell as barred in accordance with TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [20]; Editor's Note: FFS whether a cell can be barred for a mobile IAB-MT. 3> else: 4> apply a supported uplink channel bandwidth with a maximum transmission bandwidth which - is contained within the carrierBandwidth indicated in uplinkConfigCommon for the SCS of the initial uplink BWP or, for (e)RedCap UEs, (e)RedCap-specific initial uplink BWP, if configured, and which - is wider than or equal to the bandwidth of the initial BWP for the uplink or, for a (e)RedCap UE, of the (e)RedCap-specific initial uplink BWP if configured; 4> apply a supported downlink channel bandwidth with a maximum transmission bandwidth which - is contained within the carrierBandwidth indicated in downlinkConfigCommon for the SCS of the initial downlink BWP or, for (e)RedCap UEs, (e)RedCap-specific initial downlink BWP, if configured, and which - is wider than or equal to the bandwidth of the initial BWP for the downlink or, for a (e)RedCap UE, of the (e)RedCap-specific initial downlink BWP if configured; 4> if the UE is aerial UE and it supports at least one frequency band in the frequencyBandListAerial, for FDD from frequencyBandListAerial for uplink, or for TDD from frequencyBandListAerial for downlink, for which the UE supports at least one of the additionalSpectrumEmission values in nr-NS-PmaxListAerial, if present: 5> select the first frequency band in the frequencyBandListAerial, for FDD from frequencyBandListAerial for uplink, or for TDD from frequencyBandListAerial for downlink, which the UE supports and for which the UE supports at least one of the additionalSpectrumEmission values in nr-NS-PmaxListAerial; 4> else: 5> select the first frequency band in the frequencyBandList, for FDD from frequencyBandList for uplink, or for TDD from frequencyBandList for downlink, which the UE supports and for which the UE supports at least one of the additionalSpectrumEmission values in nr-NS-PmaxList, if present, and for RedCap UEs if the halfDuplexRedCapAllowed is not present, for which the UE supports full-duplex FDD operation; 4> forward the cellIdentity to upper layers; 4> forward the trackingAreaCode to upper layers; 4> forward the trackingAreaList to upper layers, if included; 4> forward the received posSIB-MappingInfo to upper layers, if included; 4> forward the PLMN identity or SNPN identity or PNI-NPN identity to upper layers; 4> if in RRC_INACTIVE and the forwarded information does not trigger message transmission by upper layers: 5> if the serving cell does not belong to the configured ran-NotificationAreaInfo: 6> initiate an RNA update as specified in 5.3.13.8; 5> if configured to receive MBS multicast in RRC_INACTIVE and not indicated to stop monitoring G-RNTI for at least one MBS multicast session: 6> if SIB24 is not scheduled in SIB1 in the cell after cell selection or cell reselection: 7> initiate an RRC connection resume procedure for multicast reception as specified in 5.3.13.1d; 4> forward the ims-EmergencySupport to upper layers, if present; 4> forward the eCallOverIMS-Support to upper layers, if present; 4> forward the UAC-AccessCategory1-SelectionAssistanceInfo or UAC-AC1-SelectAssistInfo for the selected PLMN/SNPN to upper layers, if present and set to a, b or c; 4> if the UE is in SNPN access mode: 5> forward the imsEmergencySupportForSNPN indicators with the corresponding SNPN identities to upper layers, if present; 4> apply the configuration included in the servingCellConfigCommon; 4> apply the specified PCCH configuration defined in 9.1.1.3; 4> if the UE has a stored valid version of a SIB, in accordance with clause 5.2.2.2.1, that the UE requires to operate within the cell in accordance with clause 5.2.2.1: 5> use the stored version of the required SIB; 4> if the UE has not stored a valid version of a SIB, in accordance with clause 5.2.2.2.1, of one or several required SIB(s), in accordance with clause 5.2.2.1: 5> for the SI message(s) that, according to the si-SchedulingInfo, contain at least one required SIB and for which si-BroadcastStatus is set to broadcasting: 6> acquire the SI message(s) as defined in clause 5.2.2.3.2; 5> for the SI message(s) that, according to the si-SchedulingInfo, contain at least one required SIB and for which si-BroadcastStatus is set to notBroadcasting: 6> trigger a request to acquire the SI message(s) as defined in clause 5.2.2.3.3; 4> if the UE has a stored valid version of a posSIB, in accordance with clause 5.2.2.2.1, of one or several required posSIB(s), in accordance with clause 5.2.2.1: 5> use the stored version of the required posSIB; 4> if the UE has not stored a valid version of a posSIB, in accordance with clause 5.2.2.2.1, of one or several posSIB(s) in accordance with clause 5.2.2.1: 5> for the SI message(s) that, according to the posSI-SchedulingInfo, contain at least one requested posSIB and for which posSI-BroadcastStatus is set to broadcasting: 6> acquire the SI message(s) as defined in clause 5.2.2.3.2; 5> for the SI message(s) that, according to the posSI-SchedulingInfo, contain at least one requested posSIB for which posSI-BroadcastStatus is set to notBroadcasting: 6> trigger a request to acquire the SI message(s) as defined in clause 5.2.2.3.3a; 4> if the UE is aerial UE and it supports at least one additionalSpectrumEmission values in nr-NS-PmaxListAerial within frequencyBandListAerial in uplinkConfigCommon for FDD or in downlinkConfigCommon for TDD: 5> apply the first listed additionalSpectrumEmission which it supports among the values included in nr-NS-PmaxListAerial within frequencyBandListAerial in uplinkConfigCommon for FDD or in downlinkConfigCommon for TDD; 4> else: 5> apply the first listed additionalSpectrumEmission which it supports among the values included in nr-NS-PmaxList within frequencyBandList in uplinkConfigCommon for FDD or in downlinkConfigCommon for TDD; 4> if the additionalPmax is present in the same entry of the selected additionalSpectrumEmission within nr-NS-PmaxList or nr-NS-PmaxListAerial: 5> apply the additionalPmax for UL; 4> else: 5> apply the p-Max in uplinkConfigCommon for UL; 4> if supplementaryUplink is present in servingCellConfigCommon; and 4> if the UE supports one or more of the frequency bands indicated in the frequencyBandList for the supplementaryUplink; and 4> if the UE supports at least one additionalSpectrumEmission in the nr-NS-PmaxList for a supported supplementary uplink band; and 4> if the UE is not a RedCap UE, or if the UE is a RedCap UE and halfDuplexRedCapAllowed is present, or if the UE is a RedCap UE and the RedCap UE supports full-duplex FDD operation on the frequency bands indicated in the frequencyBandList for the supplementaryUplink; and 4> if the UE supports an uplink channel bandwidth with a maximum transmission bandwidth configuration (see TS 38.101[ None ] -1 [15] and TS 38.101[ None ] -2 [39]) which - is smaller than or equal to the carrierBandwidth (indicated in supplementaryUplink for the SCS of the initial uplink BWP), and which - is wider than or equal to the bandwidth of the initial uplink BWP of the SUL: 5> consider supplementary uplink as configured in the serving cell; 5> select the first frequency band in the frequencyBandList for the supplementaryUplink which the UE supports and for which the UE supports at least one of the additionalSpectrumEmission values in nr-NS-PmaxList, if present, and for RedCap UEs if the halfDuplexRedCapAllowed is not present, for which the UE supports full-duplex FDD operation; 5> apply a supported supplementary uplink channel bandwidth with a maximum transmission bandwidth which - is contained within the carrierBandwidth (indicated in supplementaryUplink for the SCS of the initial uplink BWP), and which - is wider than or equal to the bandwidth of the initial BWP of the SUL; 5> apply the first listed additionalSpectrumEmission which it supports among the values included in nr-NS-PmaxList within frequencyBandList for the supplementaryUplink; 5> if the additionalPmax is present in the same entry of the selected additionalSpectrumEmission within nr-NS-PmaxList for the supplementaryUplink: 6> apply the additionalPmax in supplementaryUplink for SUL; 5> else: 6> apply the p-Max in supplementaryUplink for SUL; NOTE 2: For an out of coverage L2 U2N Remote UE in RRC_IDLE or RRC_INACTIVE receiving SIB1 from its connected L2 U2N Relay UE, it is up to Remote UE implementation whether to consider and apply the following parameters: frequencyBandList, carrierBandwidth, frequencyShift7p5khz, frequency band, channel bandwidth, the configuration included in the servingCellConfigCommon, the specified PCCH configuration, additionalSpectrumEmission, additionalPmax, and p-Max. 2> else: 3> consider the cell as barred in accordance with TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [20]; and 3> perform barring as if intraFreqReselection, or intraFreqReselectionRedCap for RedCap UEs, or intraFreqReselection-eRedCap for eRedCap UEs, is set to notAllowed; | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.2.2.4.2 |
4,722 | 4.3.5.3 Change of SSC mode 3 PDU Session Anchor with IPv6 Multi-homed PDU Session | Clause 4.3.5.3 describes a procedure for service continuity with SSC mode 3 that uses the multi-homed PDU Session described in clause 5.6.4.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. In this case the SMF prepares a new PDU Session Anchor first and then notifies the UE of the existence of a new IP prefix, as depicted in figure 4.3.5.3-1. This procedure is applicable only to PDU Sessions of IPv6 type. Figure 4.3.5.3-1: Change of PDU Session Anchor with IPv6 Multi homed PDU Session The UE has an established PDU Session with the PDU Session Anchor (i.e. UPF1 in Figure 4.3.5.3-1). The PDU Session's User Plane involves at least the (R)AN and the PDU Session Anchor. 1. At some point the SMF decides to allocate the PDU Session with a new PDU Session Anchor. 2. The SMF selects a new UPF and using N4 configures the UPF as a new PDU Session Anchor (i.e. UPF2 in Figure 4.3.5.3-1) of the multi-homed PDU Session. In the process a new IPv6 prefix (IP@2) is allocated for the PDU Session. If the PCF has subscribed to the IP allocation/release event, the SMF performs a Session Management Policy Modification procedure as defined in clause 4.16.5 to provide the new allocated IPv6 prefix to the PCF. The PCF invokes Nbsf_Management_Update service operation to register the tuple (IPv6 prefix, PCF id) for the PDU session identified by (SUPI, DNN, S-NSSAI) in the BSF. If the runtime coordination between 5GC and AF is enabled based on local configuration, according to the indication of "AF acknowledgment to be expected" included in AF subscription to SMF events, the SMF sends an early notification to the AF after the new UPF (new PSA) is selected and waits for a notification response from the AF. If the SMF receives a negative notification response from the AF, the SMF may stop the procedure. This is further defined in Figure 4.3.6.3-1. 3. The SMF selects a Branching Point (BP) UPF as described in Clause of 6.3.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The selection of BP UPF may consider the location of UPF1 and UPF2 to ensure a suitable location of the BP UPF relative to the UPF1 and the UPF2. NOTE 1: If BP UPF is co-located with one of PDU Session Anchors, steps between SMF and BP UPF can be skipped. 4. The SMF configures via N4 the UPF selected in step 3 (BP UPF in Figure 4.3.5.3-1) as a Branching Point for the multi-homed PDU Session. It provides the Branching Point with the necessary UL traffic forwarding rules (related with the prefix of the IPv6 source address of UL traffic). Also, the SMF provides AN Tunnel Info for N3 tunnel setup and CN Tunnel Info for N9 tunnel setup to the BP UPF and obtains CN Tunnel Info from the BP UPF. 5-6. The SMF performs N4 Session Modification procedure with PSAs. During this procedure, the SMF provides CN Tunnel Info received from the BP UPF to set up an N9 tunnel between BP and PSAs. The SMF may also indicate local PSA2 to buffer the uplink data. 7. The SMF invokes the Namf_Communication_N1N2MessageTransfer service operation containing N2 SM Information with CN Tunnel Info for the N3 tunnel setup. 8. The AMF sends an N2 Request including N2 SM Information received from the SMF to the (R)AN. The (R)AN acknowledges to the AMF with an N2 Response. 9a. The AMF carries the N2 Response sent by the (R)AN to the SMF by invoking the Nsmf_PDUSession_UpdateSMContext service operation. 9b. The SMF responds to Nsmf_PDUSession_UpdateSMContext service operation from the AMF. 10-11. If the runtime coordination between 5GC and AF is enabled based on local configuration as specified in clause 4.3.6.3, according to the indication of "AF acknowledgment to be expected" is included in AF subscription to SMF events, the SMF sends a late notification to the AF and waits for a notification response from the AF. If the SMF receives a negative notification response from the AF, the SMF may stop the procedure. This is further defined in Figure 4.3.6.3-1. The SMF notifies the UE of the availability of the new IP prefix. This is performed using an IPv6 Router Advertisement message (RFC 4861 [6]). The SMF sends a Router Advertisement to the UE via the new PSA with a new prefix (IP@2) and sends another Router Advertisement to the UE via the old PSA with the old prefix (IP@1) and zero value in the preferred lifetime field and a value in the valid lifetime field according to RFC 4862 [8]. The UE shall update the valid lifetime of the old prefix (IP@1) to the signalled value regardless of the remaining lifetime. The valid lifetime value indicates the time how long the SMF is willing to keep the old prefix. The valid lifetime value may be decided by SMF based on local configuration. The UE starts using IP@2 for all new traffic and may also proactively move existing traffic flow (where possible) from IP@1 to IP@2. NOTE 2: The mechanisms used by the UE to proactively move existing traffic flows from one IP prefix to another are outside the scope of 3GPP specifications. 12. After the timer expires, the SMF releases the UE's old IPv6 prefix (IP@1). At this point the UE implicitly releases the old IP prefix. The SMF sends an N4 Session Modification Request to the BP to release UP resource for N9 tunnel between the BP and old PSA. 13. The SMF releases the old PDU Session context with the old PDU Session Anchor (UPF1 in Figure 4.3.5.3-1). If the PCF has subscribed to the IP allocation/release event, the SMF performs a Session Management Policy Modification procedure as defined in clause 4.16.5 to notify the PCF of the IPv6 prefix release. The PCF shall invoke Nbsf_Management_Update service operation to remove the tuple (IPv6prefix, PCF id) for the PDU session identified by (SUPI, DNN,S-NSSAI) in BSF. 14-18. The SMF may optionally release the Branching Point from the User Plane path. In step 14, the SMF may also indicate PSA2 to stop buffering and start forwarding uplink data. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.3.5.3 |
4,723 | 6.3.21 MFAF discovery and selection | Multiple instances of MFAF may be deployed in a network. The MFAF selection function is supported by the DCCF. The DCCF shall utilize the NRF to discover MFAF instance(s) unless MFAF information is available by other means, e.g. locally configured on the DCCF. The MFAF selection function in the DCCF selects a MFAF instance based on the available MFAF instances. The following factors may be considered by the DCCF for MFAF selection: - S-NSSAI; - NF Types of the Data Sources handled by the MFAF; - NF Set IDs of the Data Sources handled by the MFAF; - MFAF Serving Area information, i.e. list of TAIs for which the MFAF may receive data from Data Sources. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 6.3.21 |
4,724 | 13a.2.2.1 Request for Signalling Server Address | When an MS/UE indicates a request for a P-CSCF address in the PCO IE in a Create PDP Context Request message on GERAN/UTRAN or for E-UTRAN in initial access request (e.g. Attach Request, PDN Connectivity Request), the GGSN/P-GW shall respond with one or more P-CSCF server addresses if preconfigured for this APN. If the GGSN/P-GW has no P-CSCF address available, the GGSN/P-GW shall ignore the request. If the GGSN/P-GW provides more than one P-CSCF IPv4/IPv6 address in the response, the GGSN/P-GW shall sort the addresses with the highest priority P-CSCF server first in the PCO IE. The GGSN/P-GW may use different prioritisations for different Mses/UEs, e.g. for load sharing between the P-CSCF servers. The GGSN/P-GW may use a keep alive mechanism and/or other type based on local policy (e.g. statistical monitoring) to be able to detect a failure of P-CSCF address(es) preconfigured in the APN. The keep alive mechanism should make use of STUN or CRLF as specified for the UE in 3GPP TS 24.229[ IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 ] [47], clause K.2.1.5. As an alternative, ICMP echo request/response may be used. The GGSN/P-GW shall then provide only those P-CSCF address(es) that are available in a Create PDP Context Response/Create Session Response. The coding of the PCO IE is described in the 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [54]. This procedure shall be followed regardless of whether or not the MS/UE uses a dedicated PDP context/EPS bearer for IMS signalling, and irrespective of the Gx status for the APN. | 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 | 13a.2.2.1 |
4,725 | 5.31.20 Category M UEs differentiation | This functionality is used by the network to identify traffic to/from Category M UEs, e.g. for charging differentiation. A Category M UE using E-UTRA shall provide a Category M indication to the NG-RAN during RRC Connection Establishment procedure as defined in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [51]. When the UE has provided a Category M indication to the NG-RAN during RRC Connection Establishment, the NG-RAN shall provide an LTE-M Indication to the AMF in the Initial UE Message (see clause 4.2.2.2.1 of TS 23.502[ Procedures for the 5G System (5GS) ] [3] and TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [34]). When the AMF receives an LTE-M Indication from NG-RAN in an Initial UE Message or from an MME during EPS to 5GS handover, the AMF shall store the LTE-M Indication in the UE context, consider that the RAT type is LTE-M and signal it accordingly to the SMSF during registration procedure for SMS over NAS, to the SMF during PDU Session Establishment or PDU Session Modification procedure. The PCF will also receive the RAT Type as LTE-M, when applicable, from the SMF during SM Policy Association Establishment or SM Policy Association Modification procedure. The NFs generating CDRs shall include the LTE-M RAT type in their CDRs. Upon AMF change or inter-system mobility from 5GS to EPS, the source AMF shall provide the "LTE-M Indication" to the target AMF or MME as part of the UE context. During EPS to 5GS Mobility Registration Procedure, the AMF shall disregard any "LTE-M Indication" received from the MME in the UE context (see TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [26]), and take into account the "LTE-M Indication" received from NG-RAN, as specified above. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.31.20 |
4,726 | 6.4.9 Emergency call handling | PLMNs shall support an emergency call teleservice as defined in TS 22.003[ Circuit Teleservices supported by a Public Land Mobile Network (PLMN) ] [32] which fulfils the additional service requirements defined in TS 22.101[ Service aspects; Service principles ] [33]. The PS domain of a PLMN may support establishment of PS connections for the purposes of IP multimedia subsystem emergency sessions as defined in TS 23.167[ IP Multimedia Subsystem (IMS) emergency sessions ] [34] which fullfills service requirements defined in TS 22.101[ Service aspects; Service principles ] . IMS Emergency Session Support in the PS domain is specified in TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [9]. | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | 6.4.9 |
4,727 | 5.28.5.3 DetNet node configuration mapping in 5GS | The TSCTSF maps the parameters in the DetNet YANG configuration to 5GS parameters as defined in clause 6.1.3.23b of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]. The TSCTSF determines the UE address to bind the DetNet configuration as follows: - When available, the TSCTSF uses the identity of the incoming and outgoing interface to determine the affected UE address and whether the flow is uplink or downlink or UE-to-UE. - If there is no incoming interface for UL traffic, the TSCTSF may determine the UE address based on the source IP address of the UL traffic in the DetNet configuration, or using local configuration to map the DetNet flow information to the UE address. If there is no incoming interface for traffic with an outgoing interface on the device side, the TSCTSF may determine whether the flow is UE-to-UE based on the source IP address of the traffic in the DetNet configuration, or using local configuration. NOTE 1: The incoming interface is optional in the DetNet YANG configuration. It is assumed that any IP prefix on the device side is reachable via, at most, a single device side interface. Thus if the flow source IP address is available and belongs to a prefix associated with a device side interface, that interface can be uniquely determined as the incoming interface for the flow. NOTE 2: If there is no incoming interface for the UL traffic or no incoming interface for traffic with outgoing interface on the device side, the details on how the TSCTSF uses local configuration are not specified. - When the information on IP addresses or IP prefixes not directly assigned to the port but reachable via the port is available as described in clause 5.28.5.2, the TSCTSF also takes such info into account. - If the flow is UE-to-UE, two PDU Sessions will be affected for the flow, and the TSCTSF breaks up the requirements to individual requirements for the PDU Sessions. The TSCTSF provides a response to the DetNet controller regarding the success of the configuration setup. When both the TSCTSF and the DetNet controller support 3GPP extensions to the IETF draft-ietf-detnet-yang [154], the TSCTSF may provide 5GS specific status code information on the result of the configuration to the DetNet controller. NOTE 3: The 3GPP extension to the IETF draft-ietf-detnet-yang [154] is defined in 3GPP as a YANG model which imports draft-ietf-detnet-yang [154] and adds the 3GPP specific parameters. The 3GPP defined YANG model uses the 3GPP namespace as defined in IETF RFC 5279 [158]. If the status of the flow changes later on for any reason, the TSCTSF notifies the DetNet controller. Upon release of a PDU Session that is part of the existing DetNet configuration, the PCF notifies the TSCTSF of the PDU Session release, and TSCTSF notifies the DetNet controller on the status of the flow. The 5GS routing is not modified by the configuration received from the DetNet controller. Still the TSCTSF may verify whether the explicit routing information provided by the DetNet controller is in line with the 5GS mapping of IP addresses and prefixes to PDU sessions. The verification may be based on whether the source or destination IP address in the DetNet flow on the given port corresponds to the IP address or prefix associated with the given PDU Session. Based on operator configuration, the TSCTSF may use other criteria (not routing related) to determine whether to accept or reject a given DetNet configuration. 5GS DetNet Node can forward via its device side interface IP packets destined not only to the UE's IP address or prefix but also to a range of IPv4 addresses or IPv6 IP prefixes according to one or more Framed Routes or prefixes delegated to the UE by IPv6 prefix delegation. To facilitate this, the additional IP addresses used for framed routes and IPv6 prefix delegation are exposed by the SMF to the TSCTSF via the PCF and the TSCTSF may expose them to the DetNet controller, as defined in clause 5.28.5.2. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.28.5.3 |
4,728 | 8.2.2.2 UE - AMF | Legend: - NAS-MM: The NAS protocol for MM functionality supports registration management functionality, connection management functionality and user plane connection activation and deactivation. It is also responsible of ciphering and integrity protection of NAS signalling. 5G NAS protocol is defined in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [47] - 5G-AN Protocol layer: This set of protocols/layers depends on the 5G-AN. In the case of NG-RAN, the radio protocol between the UE and the NG-RAN node (eNodeB or gNodeB) is specified in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [30] and TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [27]. In the case of non-3GPP access, see clause 8.2.4. Figure 8.2.2.2-1: Control Plane between the UE and the AMF | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 8.2.2.2 |
4,729 | 7.4.6 Alert MME Notification | An Alert MME Notification message shall be sent on the S3 interface by the MME to the associated SGSN as part of an SGs Non-EPS alert procedure (see 3GPP TS 29.118[ Mobility Management Entity (MME) - Visitor Location Register (VLR) SGs interface specification ] [22]) when ISR is activated, except under the conditions specified in 3GPP TS 23.272[ Circuit Switched (CS) fallback in Evolved Packet System (EPS); Stage 2 ] [21], to request to receive a notification when any activity from the UE is detected. Table 7.4.6-1 specifies the presence requirements and the conditions of the IEs in the message. Table 7.4.6-1: Information Element in Alert MME Notification | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 7.4.6 |
4,730 | 6.8.10.2 SRVCC from circuit switched GERAN to HSPA | SRVCC handover from circuit switched GERAN to HSPA is defined in TS 23.216[ Single Radio Voice Call Continuity (SRVCC); Stage 2 ] [37]. Figure 20: SRVCC handover from GERAN to HSPA The numbering in the following clauses refers to the signalling numbering in Figure 20. In the following, the term "latest" keys refer to the keys from the latest UMTS AKA or GSM AKA run respectively. If the current UMTS or GSM security context is mapped from an EPS security context and no AKA has been run in the current CS access, the term "latest" keys refer to the keys from the currently active UMTS or GSM security context 2. For UMTS subscribers, the source MSC server enhanced for SRVCC shall generate a NONCEMSC and derive CK'PS and IK'PS from this NONCEMSC and the latest CKCS and IKCS. The derivation shall be according to annex B.6. For The source MSC server enhanced for SRVCC shall further set the KSI'PS equal to the KSICS associated with the latest key set for UMTS subscribers, For GSM susbscribers, the source MSC server enhanced for SRVCC shall derive GPRS Kc' from the generated NONCEMSC and the latest GSM Kc. The derivation shall be according to annex B.7. The MSC server enhanced for SRVCC shall further set the CKSN'PS equal to CKSNCS associated with the latest key set for GSM subscribers. For UMTS subscribers, the MSC server enhanced for SRVCC shall transfer the CK'PS/IK'PS and the KSI'PS, to the target SGSN in the CS to PS handover request. For GSM subscribers, the MSC server enhanced for SRVCC shall transfer the GPRS Kc' and the CKSN'PS, to the target SGSN in the CS to PS handover request. NOTE 1: The MSC server enhanced for SRVCC does not include any authentication vectors in the CS to PS HO request, since this could result in that authentication vectors intended for use only in the CS domain would end up being used in a PS domain by accident. NOTE 2: The MSC server enhanced for SRVCC does not include any UE security capability information in the CS to PS HO request, since the target SGSN either has this information available, or will retrieve the information from the old SGSN. 3 and 4. The target SGSN can request context information for the UE from an old SGSN. The target SGSN shall discard any CKPS, IKPS, GPRS Kc, CKSNPS and KSIPS received from an old SGSN. If the target SGSN received any authentication vectors from the old SGSN, the target SGSN shall process these authentication vectors according to clause 6.3.4 of the present document. 5. If the target SGSN received a GPRS Kc' and a CKSN'PS from the MSC server enchanced for SRVCC, then the target SGSN shall compute CK' PS and IK'PS from the GPRS Kc' using functions c4 and c5 of the present document. The target SGSN shall associate the CK' PS and IK'PS with KSI'PS, which shall be set equal to CKSN'PS received from the source MSC server enhanced for SRVCC. SGSN shall send the CK'PS, IK'PS to the target RNC. 6a. The target RNC shall include the transparent container (RRCConnectionReconfiguration message) sent to the source BSC via the core network. 7. The target SGSN shall include the transparent container received from the target RNC in the CS to PS HO Response message sent to source MSC server enhanced for SRVCC. 8. Source MSC server enhanced for SRVCC shall include the transparent container and the NONCEMSC in the CS to PS HO command sent to the source BSC. 9. The source BSC shall include the transparent container and the NONCEMSC in the CS to PS HO command sent to the ME. NOTE: This CS to PS HO command is optionally ciphered for GERAN. For UMTS subscribers, the ME shall derive CK'PS and IK'PS. The derivation shall be done according to annex B.6, using the NONCEMSC received in the CS to PS HO command, the latest CKCS and IKCS. The ME shall set KSI'PS equal to KSICS and associate the newly derived keys with KSI'PS. If the USIM supports storage of GPRS Kc, the ME shall derive GPRS Kc' from CK'PS and IK'PS using the function c3 of the present specification. The ME shall associate the GPRS Kc' with CKSN'PS which shall be set equal to KSI’PS. The ME shall overwrite the stored parameters CKPS, IKPS , KSIPS , GPRS ciphering key Kc and GPRS CKSN PS if any, with the derived parameters CK’PS, IK’PS, KSI’PS, GPRS ciphering key Kc’ and GPRS CKSN’ PS in both ME and USIM when the SRVCC handover has been completed successfully.. For GSM subscribers, the ME shall derive GPRS Kc' according to annex B.7, using the NONCEMSC received in the CS to PS HO command and the latest GSM Kc. The ME shall set CKSN'PS equal to CKSNCS associated with the latest GSM security context and associate it with the GPRS Kc'. The ME shall in this case also derive CK'PS and IK'PS from the GPRS Kc' using the c4 and c5 functions of the present specification. The ME shall associate the CK'PS and IK'PS with KSI'PS which shall be set equal to CKSN'PS. The ME shall overwrite the stored parameters 64-bit GPRS ciphering key Kc and GPRS CKSNPS, if any, with the derived parameters GPRS ciphering key Kc’ and GPRS CKSN’PS in both ME and SIM when the SRVCC handover has been completed successfully. 10. .The ME sends the CS to PS handover confirmation message to the target RNC and the CK'PS and IK'PS shall become the active key set both in the ME and in the RNC. If the SRVCC handover fails, the ME and the network shall discard all changes of state as specified above. | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | 6.8.10.2 |
4,731 | 12.3.3 Node level overload control | Node level overload control refers to advertising of the overload information at node level, i.e. overload information at node level granularity, and applying the mitigation policies towards the target node based on this information. This helps in preventing severe overload and hence potential breakdown of the GTP-C node. When a GTP-C entity determines that the offered incoming signalling traffic is growing (or is about to grow) beyond its nominal capacity, it may signal an Overload Control Information IE to instruct its GTP-C peers to reduce the offered load accordingly. Overload Control is performed independently for each direction between two GTP-C entities. Overload Control may run concurrently, but independently, for each direction between the two GTP-C entities. Overload control of SGW originated traffic towards the MME/S4-SGSN shall rely on Downlink Data Notification throttling, as specified in clause 4.3.7.4.1a of 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [3] and 5.3.6.5 of 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [35], with the addition that the SGWs should be allowed, by configuration, to throttle DDN requests for low priority, as well as normal priority traffic (the SGW shall then throttle by priority DDN requests for low priority traffic). | 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 | 12.3.3 |
4,732 | 5.32.5.3 Access Availability/Unavailability Report | If required by the network in the Measurement Assistance Information, the UE shall provide access availability/unavailability reports to the network. How the UE detects the unavailability and the availability of an access is based on implementation. The CM state of a UE is not a factor when determining whether the 3GPP access is available. When the UE detects the unavailability/availability of an access, it shall: - build a PMF-Access Report containing the access type and an indication of availability/unavailability of this access; - send the PMF-Access Report to the UPF via the user plane. The UPF shall acknowledge the PMF-Access Report received from the UE. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.32.5.3 |
4,733 | 9.1.2 Field format and mapping | When a field is contained within a single octet, the lowest numbered bit of the field represents the least significant bit. When a field extends over more than one octet, the order of bit values progressively decreases as the octet number increases. In that part of the field contained in a given octet, the lowest numbered bit represents the least significant bit. The most significant bit of the field is represented by the highest numbered bit of the lowest numbered octet of the field. The least significant bit of the field is represented by the lowest numbered bit of the highest numbered octet of the field. For example, a bit number can be identified as a couple (o, b) where o is the octet number and b is the relative bit number within the octet. Figure 9.1.2.1 illustrates a field that spans from bit (1, 3) to bit (2, 7). The most significant bit of the field is mapped on bit (1, 3) and the least significant bit is mapped on bit (2, 7). Figure 9.1.2.1: Field mapping convention | 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.1.2 |
4,734 | 5.6.9.2.3 SSC Mode 3 | For PDU Session of SSC mode 3, the network allows the establishment of UE connectivity via a new PDU Session Anchor to the same data network before connectivity between the UE and the previous PDU Session Anchor is released. When trigger conditions apply, the network decides whether to select a PDU Session Anchor UPF suitable for the UE's new conditions (e.g. point of attachment to the network). In this Release of specification, SSC mode 3 only applies to IP PDU Session type and to any access type. In the case of a PDU Session of IPv4 or IPv6 or IPv4v6 type, during the procedure of change of PDU Session Anchor, the following applies: a. For a PDU Session of IPv6 type, the new IP prefix anchored on the new PDU Session Anchor may be allocated within the same PDU Session (relying on IPv6 multi-homing specified in clause 5.6.4.3), or b. The new IP address and/or IP prefix may be allocated within a new PDU Session that the UE is triggered to establish. After the new IP address/prefix has been allocated, the old IP address/prefix is maintained during some time indicated to the UE via NAS signalling (as described in clause 4.3.5.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]) or via Router Advertisement (as described in clause 4.3.5.3 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]) and then released. If a PDU Session of SSC mode 3 has multiple PDU Session Anchors (i.e. in the case of multi-homed PDU Sessions or in the case that UL CL applies to a PDU Session of SSC mode 3), the additional PDU Session Anchors may be released or allocated. SSC mode 3 is optional to be supported in the UE. NOTE: Features depending on SSC mode 3 will not work with the lack of support for SSC mode 3 in the UE. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.6.9.2.3 |
4,735 | 16a.3.4 Server-Initiated PDP context termination | Diameter is used as the protocol between the GGSN and a Diameter server or proxy for applications (e.g. MMS) to deliver information related to GPRS user session. However some IP applications could need to interwork with the GGSN to terminate a particular PDP context. For this purpose, the Diameter server or proxy may send a Diameter ASR to the GGSN along with the NSAPI necessary to identify the particular PDP context to be terminated. As depicted in figure 25d, the GGSN should react by deleting the corresponding PDP context. If the GGSN deletes the corresponding PDP context, it need not wait for the DeletePDPContextResponse from the SGSN before sending the ASA to the server. The absence of the NSAPI in the Diameter ASR message indicates to the GGSN that all PDP contexts for this particular user and sharing the same user session shall be deleted. The PDP contexts belonging to the same IP-CAN session are identified by the Diameter Session-Id. If a user has the same user IP address for different sets of PDP contexts towards different networks, only the PDP contexts linked to the one identified by the Diameter Session-Id shall be deleted. NOTE: As showed on figure 25d, the GGSN need not wait for the DeletePDPContextResponse from the SGSN to send the ASA to the Diameter server. Figure 25d: PDP Context deletion with Diameter | 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.3.4 |
4,736 | 5.3.1.3 Release of the N1 NAS signalling connection | The signalling procedure for the release of the N1 NAS signalling connection is initiated by the network. In N1 mode, upon indication from lower layers that the access stratum connection has been released, the UE shall enter 5GMM-IDLE mode and consider the N1 NAS signalling connection released. If the UE in 3GPP access is configured for eCall only mode as specified in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [22] then: - if the N1 NAS signalling connection that was released had been established for eCall over IMS was released, the UE shall start timer T3444; and - if the N1 NAS signalling connection that was released had been established for a call to an HPLMN designated non-emergency MSISDN or URI for test or terminal reconfiguration service was released, the UE shall start timer T3445. The UE shall start the timer T3447 if not already running when the N1 NAS signalling connection is released as specified in subclause 5.3.17. To allow the network to release the N1 NAS signalling connection, the UE: a) shall start the timer T3540 if the UE receives any of the 5GMM cause values #7, #11, #12, #13, #15, #27, #31, #62, #72, #73, #74, #75, #76, #78and the UE does not consider the received 5GMM cause value as abnormal case as specified in subclauses 5.5.1.2.7, 5.5.1.3.7 and 5.5.2.3.4; a1) shall start the timer T3540 if the UE receives a SERVICE REJECT, case i) in subclause 5.6.1.7 is applicable and the procedure was started from 5GMM-IDLE mode; b) shall start the timer T3540 for a UE in 3GPP access if: 1) the UE receives a REGISTRATION ACCEPT message which does not include a Pending NSSAI IE or UE radio capability ID deletion indication IE; 2) the UE has set the Follow-on request indicator to "No follow-on request pending" in the REGISTRATION REQUEST message; 3) the UE has not included the Uplink data status IE in the REGISTRATION REQUEST message, or the UE has included the Uplink data status IE in the REGISTRATION REQUEST message but the REGISTRATION ACCEPT message indicates that no user-plane resources of any PDU sessions are to be re-established; 4) the UE has not included the Allowed PDU session status IE or has included the Allowed PDU session status IE indicating there is no PDU session(s) for which the UE allowed the user-plane resource to be re-established over 3GPP access in the REGISTRATION REQUEST message, or the UE has included the Allowed PDU session status IE in the REGISTRATION REQUEST message but the REGISTRATION ACCEPT message does not indicate that any user-plane resources of any PDU sessions are to be re-established; 5) the registration procedure has been initiated in 5GMM-IDLE mode, or the UE has set Request type to "NAS signalling connection release" in the UE request type IE in the REGISTRATION REQUEST message and the N1 NAS signalling connection release bit is set to "N1 NAS signalling connection release supported" in the 5GS network feature support IE of the REGISTRATION ACCEPT message; 6) the user-plane resources for PDU sessions have not been set up, except for the case the UE has set Request type to "NAS signalling connection release" in the UE request type IE in the REGISTRATION REQUEST message and the N1 NAS signalling connection release bit is set to "N1 NAS signalling connection release supported" in the 5GS network feature support IE of the REGISTRATION ACCEPT message; 7) the UE need not request resources for V2X communication over PC5 reference point (see 3GPP TS 23.287[ Architecture enhancements for 5G System (5GS) to support Vehicle-to-Everything (V2X) services ] [6C]); 8) the UE has included unavailability information and has not included the start of unavailability period in the REGISTRATION REQUEST message; 9) the UE need not request resources for 5G ProSe direct discovery over PC5 or 5G ProSe direct communication over PC5 (see 3GPP TS 23.304[ Proximity based Services (ProSe) in the 5G System (5GS) ] [6E]); and 10) the UE need not request resources for A2X communication over PC5 reference point (see 3GPP TS 23.256[ Support of Uncrewed Aerial Systems (UAS) connectivity, identification and tracking; Stage 2 ] [6AB]); NOTE 1: The lower layers indicate when the user-plane resources for PDU sessions are successfully established or released. c) shall start the timer T3540 if the UE receives a REGISTRATION REJECT message indicating: the 5GMM cause value #9 or #10; d) shall start the timer T3540 if the UE receives a SERVICE REJECT message indicating: the 5GMM cause value #9, #10; or the 5GMM cause value #28 and with no emergency PDU session has been established; e) shall start the timer T3540 if: 1) the UE receives a CONFIGURATION UPDATE COMMAND message containing the Configuration update indication IE with the Registration bit set to "registration requested" and with: i) either new allowed NSSAI information or new configured NSSAI information or both included; ii) the network slicing subscription change indication; or iii) no other parameters; and 2) the user-plane resources for PDU sessions have not been set up; f) shall start the timer T3540 for a UE in 3GPP access if: 1) the UE receives a SERVICE ACCEPT message; 2) for the case that the UE sent the: i) SERVICE REQUEST message, the UE did not set the Service type IE to "signalling" or "high priority access", the UE has not included the Uplink data status IE in the SERVICE REQUEST message, or the UE has included the Uplink data status IE in the SERVICE REQUEST message but the SERVICE ACCEPT message indicates that no user-plane resources of any PDU sessions are to be re-established; or ii) CONTROL PLANE SERVICE REQUEST message, the UE did not set the Control plane service type IE to "emergency services fallback", the UE has not included the Uplink data status IE in the CONTROL PLANE SERVICE REQUEST message, or the UE has included the Uplink data status IE in the CONTROL PLANE SERVICE REQUEST message but the SERVICE ACCEPT message indicates that no user-plane resources of any PDU sessions are to be re-established; 3) the UE has not included the Allowed PDU session status IE or has included the Allowed PDU session status IE indicating there is no PDU session(s) for which the UE allowed the user-plane resource to be re-established over 3GPP access in the SERVICE REQUEST message or the CONTROL PLANE SERVICE REQUEST message, or the UE has included the Allowed PDU session status IE in the SERVICE REQUEST message or the CONTROL PLANE SERVICE REQUEST message but the SERVICE ACCEPT message does not indicate that any user-plane resources of any PDU sessions are to be re-established; 4) the service request procedure has been initiated in 5GMM-IDLE mode; 5) the user-plane resources for PDU sessions have not been set up; 6) the UE need not request resources for V2X communication over PC5 reference point (see 3GPP TS 23.287[ Architecture enhancements for 5G System (5GS) to support Vehicle-to-Everything (V2X) services ] [6C]); 7) the UE need not request resources for 5G ProSe direct discovery over PC5 or 5G ProSe direct communication over PC5 (see 3GPP TS 23.304[ Proximity based Services (ProSe) in the 5G System (5GS) ] [6E]); and 8) the UE need not request resources for A2X communication over PC5 reference point (see 3GPP TS 23.256[ Support of Uncrewed Aerial Systems (UAS) connectivity, identification and tracking; Stage 2 ] [6AB]); NOTE 2: The lower layers indicate when the user-plane resources for PDU sessions are successfully established or released. g) may start the timer T3540 if the UE receives any of the 5GMM cause values #3 or #6 or if it receives an AUTHENTICATION REJECT message; h) shall start the timer T3540 for a UE in 3GPP access upon completion of the configuration update procedure or the registration procedure if the UE does not have an emergency PDU session and: 1) the UE received a CONFIGURATION UPDATE COMMAND message or a REGISTRATION ACCEPT message while camping on a CAG cell and none of the CAG-ID(s) supported by the current CAG cell is authorized based on "Allowed CAG list" of the entry for the current PLMN in the received "CAG information list"; 2) the UE received a CONFIGURATION UPDATE COMMAND message or a REGISTRATION ACCEPT message while camping on a non-CAG cell and the entry for the current PLMN in the received "CAG information list" includes an "indication that the UE is only allowed to access 5GS via CAG cells"; or 3) the UE received a CONFIGURATION UPDATE COMMAND message while camping on a CAG cell and the entry for the current PLMN in not included in the received "CAG information list"; or i) shall start the timer T3540 for a UE in 3GPP access if: 1) the UE receives a SERVICE ACCEPT message; and 2) the UE: - has set Request type to "NAS signalling connection release" in the UE request type IE in the SERVICE REQUEST message or CONTROL PLANE SERVICE REQUEST message; or - has set Request type to "Rejection of paging" in the UE request type IE in the SERVICE REQUEST message or CONTROL PLANE SERVICE REQUEST message and the UE receives a CONFIGURATION UPDATE COMMAND message; j) shall start the timer T3540 if: 1) the UE receives the 5GMM cause value #22 along with a T3346 value in the SERVICE REJECT message, the value indicates that the timer T3346 is neither zero nor deactivated and the service request procedure has been initiated in 5GMM-IDLE mode; or 2) the UE receives the 5GMM cause value #22 along with a T3346 value in the message different from the SERVICE REJECT message, and the value indicates that the timer T3346 is neither zero nor deactivated; or k) shall start the timer T3540 if the UE receives a DEREGISTRATION ACCEPT message. l) shall start the timer T3540 after the completion of the de-registration procedure, if the UE receives a DEREGISTRATION REQUEST message and the de-registration type indicates "re-registration required". Upon expiry of T3540, - in cases a), a1), b), f), g), h), i), j) and k) the UE shall locally release the established N1 NAS signalling connection; - in cases c) and d) the UE shall locally release the established N1 NAS signalling connection and the UE shall initiate the registration procedure as described in subclause 5.5.1.3 or 5.6.1.5; or - in case e), the UE shall locally release the established N1 NAS signalling connection and perform a new registration procedure as specified in subclause 5.5.1.3.2. - in case l), the UE shall locally release the established N1 NAS signalling connection and initiate the registration procedure as specified in subclause 5.5.1.2.2. In case a), - upon receiving a request from the upper layers to perform emergency services fallback only for a UE in 3GPP access or establishing an emergency PDU session, the UE shall stop timer T3540 and shall locally release the N1 NAS signalling connection, before proceeding as specified in subclause 5.5.1. In case b) and f), - upon an indication from the lower layers that the user-plane resources for PDU sessions are set up, the UE shall stop timer T3540 and may send uplink signalling via the existing N1 NAS signalling connection or user data via user plane. If the uplink signalling is associated with emergency services fallback only for a UE in 3GPP access or establishing an emergency PDU session, the UE shall stop timer T3540 and send the uplink signalling via the existing N1 NAS signalling connection; In case b), f) and i), - upon receipt of a DEREGISTRATION REQUEST message, the UE shall stop timer T3540 and respond to the network-initiated de-registration request via the existing N1 NAS signalling connection as specified in subclause 5.5.2.3; - upon receipt of a message of a network-initiated 5GMM common procedure , the UE shall stop timer T3540 and respond to the network-initiated 5GMM common procedure via the existing N1 NAS signalling connection as specified in subclause 5.4; - if there is no user-plane resources established for PDU sessions, upon receiving a request from the upper layers to perform emergency services fallback only for a UE in 3GPP access or establishing an emergency PDU session, the UE shall stop timer T3540 and shall locally release the N1 NAS signalling connection, before proceeding as specified in subclause 5.6.1; - if there is no user-plane resources established for PDU sessions, upon receiving a request from the upper layers to perform services other than emergency services fallback only for a UE in 3GPP access or establishing an emergency PDU session, the UE shall wait for the local release of the established N1 NAS signalling connection upon expiry of timer T3540 or wait for timer T3540 being stopped, before initiating NAS signalling; - upon receipt of a DL NAS TRANSPORT message, the UE shall stop timer T3540 and may send uplink signalling via the existing N1 NAS signalling connection; - upon reception of NOTIFICATION message as specified in subclause 5.6.3.1 case a), the UE shall stop timer T3540 and send uplink signalling via the existing N1 NAS signalling connection; or - upon initiation of registration procedure for mobility and periodic registration update as specified in subclause 5.5.1.2.7 for cases h), i), j), subclause 5.5.1.3.7 for cases j), k) or subclause 5.5.1.3.2 for case a), the UE shall stop timer T3540. In case c) and d), - upon an indication from the lower layers that the access stratum connection has been released, the UE shall stop timer T3540 and perform a new registration procedure as specified in subclause 5.5.1.3.5 or 5.6.1.5. - upon receiving a request from the upper layers to perform emergency services fallback only for a UE in 3GPP access or establishing an emergency PDU session, the UE shall stop timer T3540 and shall locally release the N1 NAS signalling connection, before proceeding as specified in subclause 5.5.1. In case e), - upon an indication from the lower layers that the access stratum connection has been released, the UE shall stop timer T3540 and perform a new registration procedure as specified in subclause 5.5.1.3.2. - upon an indication from the lower layers that the user-plane resources for PDU sessions are set up, the UE shall stop timer T3540 and may send user data via user plane. NOTE 3: In this case, the new registration procedure is performed when the UE moves to the 5GMM-IDLE mode. - upon receiving a request from the upper layers to perform emergency services fallback only for a UE in 3GPP access or establishing an emergency PDU session, the UE shall stop timer T3540 and shall locally release the N1 NAS signalling connection, before proceeding as specified in subclause 5.5.1. If the UE had set the Follow-on request indicator to "Follow-on request pending" in the REGISTRATION REQUEST message due to pending uplink signalling but cannot send the pending signalling due to new service area restrictions received or due to network not supporting the feature as indicated in the REGISTRATION ACCEPT message (for example UE set the "Follow-on request pending" to send SMS over NAS but AMF notified "SMS over NAS not allowed") and if there is no further pending data or signalling and user plane resources have not been set up, the UE may locally release the established N1 NAS signalling connection upon completion of the registration procedure. NOTE 4: the UE is allowed to inform the lower layers that there is no 5GMM or 5GSM messages need to be sent over non-3GPP access if the UE receives a REGISTRATION REJECT message over non-3GPP access or a SERVICE REJECT message over non-3GPP access. If the timer T3540 is not running when the UE enters state 5GMM-DEREGISTERED.PLMN-SEARCH or 5GMM-REGISTERED.PLMN-SEARCH, the UE may locally release the N1 NAS signalling connection. | 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.3.1.3 |
4,737 | 4.15.9.3.3 Time synchronization service modification | Figure 4.15.9.3.3-1: Time synchronization service modification 1. To update an existing time synchronization service configuration of the PTP instance, the AF invokes a Nnef_TimeSynchronization_ConfigUpdate service operation providing the corresponding PTP instance reference. 2. The NEF invokes the Ntsctsf_TimeSynchronization_ConfigUpdate service operation with the corresponding TSCTSF. The AF that is part of the operator's trust domain may invoke the services directly with the TSCTSF. 3. The TSCTSF checks whether the AF requested parameters in the update request comply with the stored Time Synchronization Subscription data as defined in clause 5.27.1.11 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], for that, the TSCTSF retrieves the Time Synchronization Subscription data from UDM as defined in clause 4.15.9.2. If the Ntsctsf_TimeSynchronization_ConfigUpdate request includes or updates the Spatial validity condition and the Spatial validity condition is allowed per the subscription, the TSCTSF determines the UE's presence in the updated Spatial validity condition as specified in steps 3-7 of the time synchronization activation procedure in clause 4.15.9.3.2. - If the AF updates the clock quality acceptance criteria in step 1, the TSCTSF determines the clock acceptance criteria upon a time synchronization failure/degradation/improvement as specified in step 9 of the time synchronization activation procedure in clause 4.15.9.3.2. If AF provides clock quality acceptance criteria in step 1, and it was not available when the service was activated, the TSCTSF subscribes for notifications for changes in the NG-RAN and UPF/NW-TT timing synchronization status, as described in clause 4.15.9.5.1: - To determine the impacted UEs due to a timing synchronization status update reported by the NG-RAN, the TSCTSF follows the operation described in clause 5.27.1.12 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. - To determine the impacted UEs due to a timing synchronization status update reported by the UPF/NW-TT, the TSCTSF verifies if the UPF/NW-TT is configured to send (g)PTP messages to the UEs/DS-TTs. 4. The TSCTSF responds with the Ntsctsf_TimeSynchronization_ConfigUpdate response where the AF may include an indication that the UE(s) are (not) present in the Requested Coverage Area (in cases when the AF has requested the service for a specific area). 5. The NEF responds with the Nnef_TimeSynchronization_ConfigUpdate. 6-7. The TSCTSF uses the PTP instance reference included in the Ntsctsf_TimeSynchronization_ConfigUpdate request to identify the time synchronization service configuration and the corresponding AF sessions. If the Ntsctsf_TimeSynchronization_ConfigUpdate request includes updated service parameters for the PTP instance and if the corresponding DS-TT(s) and NW-TT are suitable with the parameters (e.g. requested PTP instance type, transport protocol and PTP profile), the TSCTSF uses the procedures described in clause K.2.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] to update the PTP instance(s) in the DS-TT(s) and NW-TT. If the Ntsctsf_TimeSynchronization_ConfigUpdate request includes one or more UE identities to be added to the PTP instance, if the corresponding DS-TT(s) are suitable with the parameters (e.g. requested PTP instance type, transport protocol and PTP profile) in the time synchronization service configuration as identified by the PTP instance reference in the request: - the TSCTSF adds the suitable AF-sessions to the list of AF-sessions that are associated with the time synchronization service configuration; and - the TSCTSF uses the procedures described in clause K.2.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] to initialize and activate the PTP instance(s) in the corresponding DS-TT(s). - the TSCTSF uses the procedure in clause 4.15.9.4 to modify or activate the 5G access stratum time distribution for the UEs that are added to the impacted PTP instance. If the Ntsctsf_TimeSynchronization_ConfigUpdate request includes one or more UE identities to be removed to the PTP instance, the TSCTSF removes the corresponding AF-sessions from the list of AF-sessions associated with the time synchronization configuration. The TSCTSF uses the procedure in clause 4.15.9.4 to remove the 5G access stratum time distribution parameters for the UEs that are removed from the impacted PTP instance. 8. The TSCTSF notifies the NEF (or AF) with the Ntsctsf_TimeSynchronization_ConfigUpdateNotify service operation, containing the PTP instance reference and the current state of the time synchronization service configuration, including and whether there was a change in the UE's presence in the Spatial validity condition (in cases when the AF has requested the service for a specific area) and/or whether there was a change in network's timing synchronization status as described in clause 5.27.1.12 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] including the clock quality acceptance criteria result. 9. The NEF notifies the AF with the Nnef_TimeSynchronization_ConfigUpdateNotify service operation, containing the PTP instance reference, the current state of the time synchronization service configuration, network's time synchronization status and clock quality acceptance criteria result, if provided by Ntsctsf_TimeSynchronization_ConfigUpdateNotify. Based on the notification, the AF decides whether to modify the service configured for the UE of a PTP instance using Ntsctsf_TimeSynchronization_ConfigUpdate service, or whether to deactivate it using Nnef_TimeSynchronization_ConfigDelete service. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.15.9.3.3 |
4,738 | 4.22.2.3.2 PDN Connections and Multi Access PDU Sessions | When the UE wants to request a new PDN Connection in EPC and wants to use this PDN Connection as user-plane resource associated with a MA PDU Session: - The UE requests establishment of a new PDN Connection when the UE is registered via 3GPP access in EPS using PDN Connection Establishment procedure. The UE provides via PCO to PGW-C+SMF the following information: - An indication that the PDN Connection is requested to be associated with a MA PDU Session - The UE's ATSSS capabilities as described in clause 5.32.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] (i.e. whether the UE is capable of supporting the ATSSS-LL functionality, the MPTCP functionality, the MPQUIC functionality, or any combination of them). - The MME may select a PGW-C+SMF as described in TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13] and clause 4.11.0a.4. NOTE 1: The selection of PGW-C+SMF in the correct 5GC slice requires the same mapping between EPC and 5GC slices as required for single-access PDU sessions. In order to select an ATSSS capable PGW-C+SMF it is assumed that the operator deployment ensures that all PGW-C+SMF(s) configured to support the specific APN in this network slice are also capable to support ATSSS. There is however no assumption that all PGW-U+UPFs need to support ATSSS, since PGW-C+SMF can make a selection of PGW-U+UPF taking the multi-access properties into account. - The PGW-C+SMF determines based its capabilities whether the request can be accepted. The PCF decides whether the multi-access connectivity is allowed or not based on operator policy and subscription data, as described in clause 4.22.2. The PGW-C+SMF provides the following information in the PCO to the UE: - An indication whether the request for using the PDN Connection for MA-PDU Session is accepted or not. - If the UE has indicated that it is capable of supporting the MPTCP functionality and/or the MPQUIC functionality and the PGW-C+SMF accepts to activate the MPTCP functionality and/or the MPQUIC functionality, then the network provides MPTCP proxy information and/or MPQUIC proxy information to the UE, as described in clause 5.32.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. - UE Measurement Assistance Information (as described in clause 5.32.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]). After the PDN Connection establishment: - If the UE registers to 5GC and wants to add non-3GPP user-plane resources, then the UE shall send a PDU Session Establishment Request over this access containing a "MA PDU Request" indication as described in clause 5.32.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. NOTE 2: Adding the PDU Session connectivity and user plane resources over non-3GPP access in 5GS allows the PGW-C+SMF to provide ATSSS rules to the UE. When the UE wants to request a new MA PDU Session in 5GC/non-3GPP access, the description in clause 5.32.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], applies. After the MA PDU Session establishment in 5GS/non-3GPP access, the description in clause 5.32.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], applies with the following additions: - If the UE is registered to EPC and wants to add user-plane resources on 3GPP access over EPC, then the UE shall send a PDN Connection Establishment Request over this access containing a "handover" indication and include a "MA PDU Request" indication in the PCO as well as the PDU Session ID of the existing MA PDU Session on non-3GPP access over 5GC. - When the UE deregisters from the EPC access (but remains registered on the 5GC access), the MME will notify the PGW-C+SMF that the PDN Connection is released, as described in TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13]. The SMF can then notify the UPF that the access type has become unavailable. In order to support EPS interworking when Ethernet type PDN Connection is not supported in EPS, the UE may use non-IP type PDN Connection when the UE establishes a PDN Connection in EPS as an added 3GPP access leg of an Ethernet type MA PDU Session. In this case, the UE and SMF shall locally associate the PDN Connection as an Ethernet type PDU Session as described in TS 23.501[ System architecture for the 5G System (5GS) ] [2]. When Ethernet type PDN Connection is not supported in EPS, the UE does not request to establish a PDN Connection with "MA PDU Request" indication before the UE registers to 5GS and establishes MA PDU Session over non-3GPP access. A UE that has an established MA-PDU session over non-3GPP access in 5GC and 3GPP access in EPS, may be able to use EN-DC for the 3GPP access leg. Depending on the RAT types supported by the UE, the PDN connection may also be handed over to 3GPP access in 5GC. For a UE supporting both E-UTRAN/EPC access and NG-RAN/5GC access, the user plane resources for 3GPP access may be moved between E-UTRAN/EPC access and NG-RAN/5GC access as described in clause 5.17.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The PDU Session and User Plane resources active over non-3GPP access are not affected by such inter 3GPP access RAT change. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.22.2.3.2 |
4,739 | 9.9.4.27 Header compression configuration status | The purpose of the Header compression configuration status information element is to indicate the status of the Header compression configuration for each EPS bearer using Control plane CIoT EPS optimisation that can be identified by an EPS bearer identity. The Header compression configuration status information element is a type 4 information element with 4 the length of 4 octets. Figure 9.9.4.27.1: Header compression configuration status information element Table 9.9.4.27.1: Header compression configuration status information element | 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.9.4.27 |
4,740 | 6.6.3.3.26 Minimum requirement (network signalled value “NS_30”) | When "NS_30" is indicated in the cell, the power of any UE emission for E-UTRA channels assigned within 5150-5350 MHz, 5470-5725 MHz and 5725-5850 MHz shall not exceed the levels specified in Table 6.6.3.3.26-1, Table 6.6.3.3.26-2 and Table 6.6.3.3.26-3, respectively. These requirements also apply for the frequency ranges that are less than FOOB (MHz) in Table 6.6.3.1-1 from the edge of the channel bandwidth. Table 6.6.3.3.26-1: Additional requirements for E-UTRA channels assigned within 5150-5350 MHz Table 6.6.3.3.26-2: Additional requirements for E-UTRA channels assigned within 5470-5725 MHz Table 6.6.3.3.26-3: Additional requirements for E-UTRA channels assigned within 5725-5850 MHz | 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.3.3.26 |
4,741 | 5.4.5.2.6 Abnormal cases in the UE | The following abnormal cases can be identified: a) The lower layers indicate that the access attempt is barred. The UE shall not start the UE-initiated NAS transport procedure. The UE stays in the current serving cell and applies the normal cell reselection process. If the access category for the access attempt is 6 due to a request from upper layers to send a mobile originated SMS over NAS and the UE is registered to the network via both 3GPP access and non-3GPP access, the UE may transmit the UL NAS TRANSPORT message via non-3GPP access, if available. Otherwise, the UE-initiated NAS transport procedure is started, if still needed, when the lower layers indicate that the barring is alleviated for the access category with which the access attempt was associated. aa) The lower layers indicate that: 1) access barring is applicable for all access categories except categories 0 and 2 and the access category with which the access attempt was associated is other than 0 and 2; or 2) access barring is applicable for all access categories except category 0 and the access category with which the access attempt was associated is other than 0. The UE shall proceed as specified for case a. For additional UE requirements see subclause 4.5.5. b) If the Payload container type IE is set to "N1 SM information", the Request type IE is set to "initial request" or "MA PDU request" and registration procedure for mobility and periodic registration update is pending due to receipt by the UE of new network slicing information via the generic UE configuration update procedure with re-registration request; and an emergency PDU session exists then: 1) The UE shall not send the UL NAS TRANSPORT message; and 2) The UL NAS TRANSPORT message can be sent, if still necessary, after a successful procedure for mobility and periodic registration update. c) Transmission failure of the UL NAS TRANSPORT message with change in the current TAI. If the current TAI is not in the TAI list, the UE-initiated NAS transport procedure shall be aborted and a registration procedure for mobility and periodic registration update shall be initiated. The UL NAS TRANSPORT message can be sent, if still necessary, after a successful procedure for mobility and periodic registration update. If: 1) the current TAI is still part of the TAI list; 2) the UL NAS TRANSPORT message is sent to transport a 5GSM message associated with an S-NSSAI included in the partially allowed NSSAI; and 3) the current TAI is not in the list of TAs where the S-NSSAI is allowed, then the UE-initiated NAS transport procedure shall be aborted. Otherwise, it is up to the UE implementation how to re-run the ongoing procedure that triggered the UE-initiated NAS transport procedure. d) Transmission failure of the UL NAS TRANSPORT message indication without change in the current TAI. It is up to the UE implementation how to re-run the ongoing procedure that triggered the UE-initiated NAS transport procedure. e) Void. f) Timer T3447 is running. The UE shall not send the UL NAS TRANSPORT message unless: 1) the Payload container type IE is set to "N1 SM information" and: i) the Request type IE is set to: A) "initial emergency request"; B) "existing emergency PDU session"; or C) "modification request" and the PDU session being modified is an emergency PDU session (see error cases described in subclause 6.4.1.3 and subclause 6.3.2.3); or ii) the Request type IE is not included and the PDU session modification procedure is used to indicate a change of 3GPP PS data off UE status for a PDU session; 2) the UE is a UE configured for high priority access in selected PLMN; 3) a paging request triggered the establishment of the current NAS signalling connection; or 4) the UE in 5GMM-CONNECTED mode receives mobile terminated signalling or downlink data over the user-plane. The UL NAS TRANSPORT message can be sent, if still necessary, when timer T3447 expires or timer T3447 is stopped. g) The lower layers indicate that the RRC connection has been suspended. The UE shall abort the UE-initiated NAS transport procedure. h) Timer T3346 is running. The UE shall not send the UL NAS TRANSPORT message unless: 1) the Payload container type IE is set to "N1 SM information" and: i) the Request type IE is set to: A) "initial emergency request"; B) "existing emergency PDU session"; or C) "modification request" and the PDU session being modified is an emergency PDU session; or ii) the Request type IE is not included and the PDU session modification procedure is used to indicate a change of 3GPP PS data off UE status for a PDU session; or 2) the UE is a UE configured for high priority access in selected PLMN or SNPN. The UL NAS TRANSPORT message can be sent, if still necessary, when timer T3346 expires. i) NAS MAC calculation indication from lower layers. If lower layers indicate to calculate an NAS MAC, the UE shall calculate an NAS MAC as specified in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24] and then provide the calculated NAS MAC and 5 least significant bits of the uplink NAS COUNT used to calculate the NAS MAC to lower layers (see 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [25A]). The UE shall increase the uplink NAS COUNT by one after the calculation of the NAS MAC. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.4.5.2.6 |
4,742 | 5.5.2.3.2 Mapping to physical resources | The sequence shall be multiplied with the amplitude scaling factor and mapped in sequence starting with to resource elements on antenna port . The mapping shall be in increasing order of first, then . The set of values for and the relation between the index and the antenna port number shall be identical to the values used for the corresponding SPUCCH transmission. The values of the symbol index in a slot and a subslot are given by Table 5.5.2.3.2-1 and Table 5.5.2.3.2-2 respectively. Table 5.5.2.3.2-1: Demodulation reference signal location for different slot-SPUCCH formats Table 5.5.2.3.2-2: Demodulation reference signal location for different subslot-SPUCCH formats | 3GPP TS 36.211 | Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation | RAN1 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 5.5.2.3.2 |
4,743 | 8.10.1.1.13 Performance requirements for DCI format 2D and non Quasi Co-located Antenna Ports | 8.10.1.1.13.1 Minimum requirements for QCL Type C and 3 Layers Spatial Multiplexing The requirements are specified in Table 8.10.1.1.13.1-3, with the additional parameters in Table 8.10.1.1.13.1-1 and Table 8.10.1.1.13.1-2. The purpose of this test is to verify the UE capability of supporting non quasi-colocated antenna ports when the UE receives DCI format 2D in a scenario with non-coherent joint transmission from two transmission points. The test verifies that the UE configured with quasi co-location type C performs correct tracking and compensation of the frequency and time difference between two transmission points, channel parameters estimation, channel estimation and rate matching behaviour according to the ‘PDSCH RE Mapping and Quasi-Co-Location Indicator’ signalling defined in [6]. In Table 8.10.1.1.13.1-1, transmission point 1 (TP 1) is the serving cell transmitting PDCCH, synchronization signals, PBCH and PDSCH, and transmission point 2 (TP 2) has different Cell ID and transmits PDSCH. In the test the PDSCH is transmitted from TP 1 and TP 2. The downlink physical channel setup for TP 1 is according to Annex C.3.2 and for TP 2 according to Annex C.3.2. Table 8.10.1.1.13.1-1: Test Parameters Table 8.10.1.1.13.1-2: Configurations of PQI and DL transmission hypothesis for each PQI set Table 8.10.1.1.13.1-3: Performance Requirements 8.10.1.1.13.2 Minimum requirements for QCL Type C and 4 Layers Spatial Multiplexing The requirements are specified in Table 8.10.1.1.13.2-3, with the additional parameters in Table 8.10.1.1.13.2-1 and Table 8.10.1.1.13.2-2. The purpose of this test is to verify the UE capability of supporting non quasi-colocated antenna ports when the UE receives DCI format 2D in a scenario with non-coherent joint transmission from two transmission points. The test verifies that the UE configured with quasi co-location type C performs correct tracking and compensation of the frequency and time difference between two transmission points, channel parameters estimation, channel estimation and rate matching behaviour according to the ‘PDSCH RE Mapping and Quasi-Co-Location Indicator’ signalling defined in [6]. In Table 8.10.1.1.13.2-1, transmission point 1 (TP 1) is the serving cell transmitting PDCCH, synchronization signals, PBCH and PDSCH, and transmission point 2 (TP 2) has different Cell ID and transmits PDSCH. In the test the PDSCH is transmitted from TP 1 and TP 2. The downlink physical channel setup for TP 1 is according to Annex C.3.2 and for TP 2 according to Annex C.3.2. Table 8.10.1.1.13.2-1: Test Parameters Table 8.10.1.1.13.2-2: Configurations of PQI and DL transmission hypothesis for each PQI set Table 8.10.1.1.13.2-3: Performance Requirements | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.10.1.1.13 |
4,744 | – CSI-MeasConfig | The IE CSI-MeasConfig is used to configure CSI-RS (reference signals) belonging to the serving cell in which CSI-MeasConfig is included, channel state information reports to be transmitted on PUCCH on the serving cell in which CSI-MeasConfig is included and channel state information reports on PUSCH triggered by DCI received on the serving cell in which CSI-MeasConfig is included. See also TS 38.214[ NR; Physical layer procedures for data ] [19], clause 5.2. CSI-MeasConfig information element -- ASN1START -- TAG-CSI-MEASCONFIG-START CSI-MeasConfig ::= SEQUENCE { nzp-CSI-RS-ResourceToAddModList SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-Resources)) OF NZP-CSI-RS-Resource OPTIONAL, -- Need N nzp-CSI-RS-ResourceToReleaseList SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-Resources)) OF NZP-CSI-RS-ResourceId OPTIONAL, -- Need N nzp-CSI-RS-ResourceSetToAddModList SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-ResourceSets)) OF NZP-CSI-RS-ResourceSet OPTIONAL, -- Need N nzp-CSI-RS-ResourceSetToReleaseList SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-ResourceSets)) OF NZP-CSI-RS-ResourceSetId OPTIONAL, -- Need N csi-IM-ResourceToAddModList SEQUENCE (SIZE (1..maxNrofCSI-IM-Resources)) OF CSI-IM-Resource OPTIONAL, -- Need N csi-IM-ResourceToReleaseList SEQUENCE (SIZE (1..maxNrofCSI-IM-Resources)) OF CSI-IM-ResourceId OPTIONAL, -- Need N csi-IM-ResourceSetToAddModList SEQUENCE (SIZE (1..maxNrofCSI-IM-ResourceSets)) OF CSI-IM-ResourceSet OPTIONAL, -- Need N csi-IM-ResourceSetToReleaseList SEQUENCE (SIZE (1..maxNrofCSI-IM-ResourceSets)) OF CSI-IM-ResourceSetId OPTIONAL, -- Need N csi-SSB-ResourceSetToAddModList SEQUENCE (SIZE (1..maxNrofCSI-SSB-ResourceSets)) OF CSI-SSB-ResourceSet OPTIONAL, -- Need N csi-SSB-ResourceSetToReleaseList SEQUENCE (SIZE (1..maxNrofCSI-SSB-ResourceSets)) OF CSI-SSB-ResourceSetId OPTIONAL, -- Need N csi-ResourceConfigToAddModList SEQUENCE (SIZE (1..maxNrofCSI-ResourceConfigurations)) OF CSI-ResourceConfig OPTIONAL, -- Need N csi-ResourceConfigToReleaseList SEQUENCE (SIZE (1..maxNrofCSI-ResourceConfigurations)) OF CSI-ResourceConfigId OPTIONAL, -- Need N csi-ReportConfigToAddModList SEQUENCE (SIZE (1..maxNrofCSI-ReportConfigurations)) OF CSI-ReportConfig OPTIONAL, -- Need N csi-ReportConfigToReleaseList SEQUENCE (SIZE (1..maxNrofCSI-ReportConfigurations)) OF CSI-ReportConfigId OPTIONAL, -- Need N reportTriggerSize INTEGER (0..6) OPTIONAL, -- Need M aperiodicTriggerStateList SetupRelease { CSI-AperiodicTriggerStateList } OPTIONAL, -- Need M semiPersistentOnPUSCH-TriggerStateList SetupRelease { CSI-SemiPersistentOnPUSCH-TriggerStateList } OPTIONAL, -- Need M ..., [[ reportTriggerSizeDCI-0-2-r16 INTEGER (0..6) OPTIONAL -- Need R ]], [[ sCellActivationRS-ConfigToAddModList-r17 SEQUENCE (SIZE (1..maxNrofSCellActRS-r17)) OF SCellActivationRS-Config-r17 OPTIONAL, -- Need N sCellActivationRS-ConfigToReleaseList-r17 SEQUENCE (SIZE (1..maxNrofSCellActRS-r17)) OF SCellActivationRS-ConfigId-r17 OPTIONAL -- Need N ]], [[ ltm-CSI-ReportConfigToAddModList-r18 SEQUENCE (SIZE (1..maxNrofLTM-CSI-ReportConfigurations-r18)) OF LTM-CSI-ReportConfig-r18 OPTIONAL, -- Need N ltm-CSI-ReportConfigToReleaseList-r18 SEQUENCE (SIZE (1..maxNrofLTM-CSI-ReportConfigurations-r18)) OF LTM-CSI-ReportConfigId-r18 OPTIONAL -- Need N ]] } -- TAG-CSI-MEASCONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
4,745 | – SIB2 | SIB2 contains cell re-selection information common for intra-frequency, inter-frequency and/or inter-RAT cell re-selection (i.e. applicable for more than one type of cell re-selection but not necessarily all) as well as intra-frequency cell re-selection information other than neighbouring cell related. SIB2 information element -- ASN1START -- TAG-SIB2-START SIB2 ::= SEQUENCE { cellReselectionInfoCommon SEQUENCE { nrofSS-BlocksToAverage INTEGER (2..maxNrofSS-BlocksToAverage) OPTIONAL, -- Need S absThreshSS-BlocksConsolidation ThresholdNR OPTIONAL, -- Need S rangeToBestCell RangeToBestCell OPTIONAL, -- Need R q-Hyst ENUMERATED { dB0, dB1, dB2, dB3, dB4, dB5, dB6, dB8, dB10, dB12, dB14, dB16, dB18, dB20, dB22, dB24}, speedStateReselectionPars SEQUENCE { mobilityStateParameters MobilityStateParameters, q-HystSF SEQUENCE { sf-Medium ENUMERATED {dB-6, dB-4, dB-2, dB0}, sf-High ENUMERATED {dB-6, dB-4, dB-2, dB0} } } OPTIONAL, -- Need R ... }, cellReselectionServingFreqInfo SEQUENCE { s-NonIntraSearchP ReselectionThreshold OPTIONAL, -- Need S s-NonIntraSearchQ ReselectionThresholdQ OPTIONAL, -- Need S threshServingLowP ReselectionThreshold, threshServingLowQ ReselectionThresholdQ OPTIONAL, -- Need R cellReselectionPriority CellReselectionPriority, cellReselectionSubPriority CellReselectionSubPriority OPTIONAL, -- Need R ... }, intraFreqCellReselectionInfo SEQUENCE { q-RxLevMin Q-RxLevMin, q-RxLevMinSUL Q-RxLevMin OPTIONAL, -- Need R q-QualMin Q-QualMin OPTIONAL, -- Need S s-IntraSearchP ReselectionThreshold, s-IntraSearchQ ReselectionThresholdQ OPTIONAL, -- Need S t-ReselectionNR T-Reselection, frequencyBandList MultiFrequencyBandListNR-SIB OPTIONAL, -- Need S frequencyBandListSUL MultiFrequencyBandListNR-SIB OPTIONAL, -- Need R p-Max P-Max OPTIONAL, -- Need S smtc SSB-MTC OPTIONAL, -- Need S ss-RSSI-Measurement SS-RSSI-Measurement OPTIONAL, -- Need R ssb-ToMeasure SSB-ToMeasure OPTIONAL, -- Need S deriveSSB-IndexFromCell BOOLEAN, ..., [[ t-ReselectionNR-SF SpeedStateScaleFactors OPTIONAL -- Need N ]], [[ smtc2-LP-r16 SSB-MTC2-LP-r16 OPTIONAL, -- Need R ssb-PositionQCL-Common-r16 SSB-PositionQCL-Relation-r16 OPTIONAL -- Cond SharedSpectrum ]], [[ ssb-PositionQCL-Common-r17 SSB-PositionQCL-Relation-r17 OPTIONAL -- Cond SharedSpectrum2 ]], [[ smtc4list-r17 SSB-MTC4List-r17 OPTIONAL -- Need R ]], [[ frequencyBandList-v1760 MultiFrequencyBandListNR-SIB-v1760 OPTIONAL, -- Need R frequencyBandListSUL-v1760 MultiFrequencyBandListNR-SIB-v1760 OPTIONAL -- Need R ]], [[ frequencyBandListAerial-r18 MultiFrequencyBandListNR-Aerial-SIB-r18 OPTIONAL -- Need S ]] }, ..., [[ relaxedMeasurement-r16 SEQUENCE { lowMobilityEvaluation-r16 SEQUENCE { s-SearchDeltaP-r16 ENUMERATED { dB3, dB6, dB9, dB12, dB15, spare3, spare2, spare1}, t-SearchDeltaP-r16 ENUMERATED { s5, s10, s20, s30, s60, s120, s180, s240, s300, spare7, spare6, spare5, spare4, spare3, spare2, spare1} } OPTIONAL, -- Need R cellEdgeEvaluation-r16 SEQUENCE { s-SearchThresholdP-r16 ReselectionThreshold, s-SearchThresholdQ-r16 ReselectionThresholdQ OPTIONAL -- Need R } OPTIONAL, -- Need R combineRelaxedMeasCondition-r16 ENUMERATED {true} OPTIONAL, -- Need R highPriorityMeasRelax-r16 ENUMERATED {true} OPTIONAL -- Need R } OPTIONAL -- Need R ]], [[ cellEquivalentSize-r17 INTEGER(2..16) OPTIONAL, -- Cond HSDN relaxedMeasurement-r17 SEQUENCE { stationaryMobilityEvaluation-r17 SEQUENCE { s-SearchDeltaP-Stationary-r17 ENUMERATED {dB2, dB3, dB6, dB9, dB12, dB15, spare2, spare1}, t-SearchDeltaP-Stationary-r17 ENUMERATED {s5, s10, s20, s30, s60, s120, s180, s240, s300, spare7, spare6, spare5, spare4, spare3, spare2, spare1} }, cellEdgeEvaluationWhileStationary-r17 SEQUENCE { s-SearchThresholdP2-r17 ReselectionThreshold, s-SearchThresholdQ2-r17 ReselectionThresholdQ OPTIONAL -- Need R } OPTIONAL, -- Need R combineRelaxedMeasCondition2-r17 ENUMERATED {true} OPTIONAL -- Need R } OPTIONAL -- Need R ]] } RangeToBestCell ::= Q-OffsetRange -- TAG-SIB2-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
4,746 | 6.1.2.2 Management | The 5G system shall allow the operator to create, modify, and delete a network slice. The 5G system shall allow the operator to define and update the set of services and capabilities supported in a network slice. The 5G system shall allow the operator to configure the information which associates a UE to a network slice. The 5G system shall allow the operator to configure the information which associates a service to a network slice. The 5G system shall allow the operator to assign a UE to a network slice, to move a UE from one network slice to another, and to remove a UE from a network slice based on subscription, UE capabilities, the access technology being used by the UE, operator's policies and services provided by the network slice. The 5G system shall support a mechanism for the VPLMN, as authorized by the HPLMN, to assign a UE to a network slice with the needed services or to a default network slice. The 5G system shall enable a UE to be simultaneously assigned to and access services from more than one network slice of one operator. Traffic and services in one network slice shall have no impact on traffic and services in other network slices in the same network. Creation, modification, and deletion of a network slice shall have no or minimal impact on traffic and services in other network slices in the same network. The 5G system shall support scaling of a network slice, i.e. adaptation of its capacity. The 5G system shall enable the network operator to define a minimum available capacity for a network slice. Scaling of other network slices on the same network shall have no impact on the availability of the minimum capacity for that network slice. The 5G system shall enable the network operator to define a maximum capacity (e.g., number of UEs, number of data sessions) for a network slice. The 5G system shall enable the network operator to define a priority order between different network slices in case multiple network slices compete for resources on the same network. The 5G system shall support means by which the operator can differentiate policy control, functionality and performance provided in different network slices. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.1.2.2 |
4,747 | 4.3.2a Authentication procedure used for a UMTS authentication challenge | The purpose of the authentication procedure is fourfold (see 3GPP TS 33.102[ 3G security; Security architecture ] [5a]): First to permit the network to check whether the identity provided by the mobile station is acceptable or not; Second to provide parameters enabling the mobile station to calculate a new UMTS ciphering key; Third to provide parameters enabling the mobile station to calculate a new UMTS integrity key; Fourth to permit the mobile station to authenticate the network. The cases where the authentication procedure should be used are defined in 3GPP TS 33.102[ 3G security; Security architecture ] [5a]. The UMTS authentication procedure is always initiated and controlled by the network. However, there is the possibility for the MS to reject the UMTS authentication challenge sent by the network. The MS shall support the UMTS authentication challenge, if a USIM is inserted. A UMTS security context is established in the MS and the network when a UMTS authentication challenge is performed in A/Gb mode or in Iu mode. After a successful UMTS authentication, the UMTS ciphering key, the UMTS integrity key, the GSM ciphering key and the ciphering key sequence number, are stored both in the network and the MS. Furthermore, in A/Gb mode both the ME and the network may derive and store a GSM Kc128 as part of the UMTS security context as described in the subclause 4.3.2.3a. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.3.2a |
4,748 | B.1 Representation of IMEI | The International Mobile station Equipment Identity and Software Version number (IMEISV), as defined in clause 6, is a 16 digit decimal number composed of three distinct elements: - an 8 digit Type Allocation Code (TAC); - a 6 digit Serial Number (SNR); and - a 2 digit Software Version Number (SVN). The IMEISV is formed by concatenating these three elements as illustrated below: Figure A.1: Composition of the IMEISV The IMEI is complemented by a check digit as defined in clause 3. The Luhn Check Digit (CD) is computed on the 14 most significant digits of the IMEISV, that is on the value obtained by ignoring the SVN digits. The method for computing the Luhn check is defined in Annex B of the International Standard "Identification cards - Numbering system and registration procedure for issuer identifiers" (ISO/IEC 7812 [3]). In order to specify precisely how the CD is computed for the IMEI, it is necessary to label the individual digits of the IMEISV, excluding the SVN. This is done as follows: The (14 most significant) digits of the IMEISV are labelled D14, D13 ... D1, where: - TAC = D14, D13 ... D7 (with D7 the least significant digit of TAC); - SNR = D6, D5 ... D1 (with D1 the least significant digit of SNR). | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | B.1 |
4,749 | Annex G (normative): Support of algorithm change features | UEA2 and UIA2 have been developed as back up algorithms which should be installed in RNCs as soon as possible so that they are available for use in the hopefully unlikely event that the current algorithms UEA1 and UIA1 become compromised. Therefore it is reasonable to expect that operators will have been able to upgrade all their RNCs before the new algorithms need to be enabled. Consequently, algorithm change is only required at inter-network handover. Based on the above assumptions, the following feature shall be supported: - Encryption/integrity algorithm change at SRNC relocation with hard inter-network handover. Based on the above assumptions, the following features do not have to be supported: - Encryption/integrity algorithm change at "UE not involved" SRNC relocation for both the DCH and FACH cases. NOTE: Only applies to intra-network case, since Iur is not supported between operators. - Encryption/integrity algorithm change at SRNC relocation with hard intra-network handover. | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | Annex |
4,750 | 19.4.2.9.2 Operator Identifier based ePDG FQDN | The ePDG Fully Qualified Domain Name (ePDG FQDN) contains an Operator Identifier that shall uniquely identify the PLMN where the ePDG is located. The ePDG FQDN is composed of seven labels. The last three labels shall be "pub.3gppnetwork.org". The third and fourth labels together shall uniquely identify the PLMN. The first two labels shall be "epdg.epc". The ePDG FQDN shall be constructed as follows: "epdg.epc.mnc<MNC>.mcc<MCC>.pub.3gppnetwork.org" In the roaming case, the UE can utilise the services of the VPLMN or the HPLMN (see 3GPP TS 23.402[ Architecture enhancements for non-3GPP accesses ] [68] and 3GPP TS 24.302[ Access to the 3GPP Evolved Packet Core (EPC) via non-3GPP access networks; Stage 3 ] [77]). In this case, the Operator Identifier based ePDG FQDN shall be constructed as described above, but using the MNC and MCC of the VPLMN or the HPLMN. In order to guarantee inter-PLMN DNS translation, the <MNC> and <MCC> coding used in the "epdg.epc. mnc<MNC>.mcc<MCC>.pub.3gppnetwork.org" format of the Operator Identifier based ePDG FQDN shall be: - <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 ePDG FQDN. As an example, the Operator Identifier based ePDG FQDN for MCC 345 and MNC 12 is coded in the DNS as: "epdg.epc.mnc012.mcc345.pub.3gppnetwork.org". | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 19.4.2.9.2 |
4,751 | 4.22.6.2.5 5GS to EPS mobility without N26 interface | Based on the signalling flow in Figure 4.11.2.2-1, the procedure is performed with the following differences and modifications: - In step 10 (and step 13 in clause 4.11.2.4.1), if the MA PDU Session is established in both 3GPP and non-3GPP accesses and the MA PDU Session is moved to EPS and if the UE and the network does not support MA PDU Session with 3GPP access connected to EPC, the PGW-C + SMF triggers the MA PDU Session Release procedure over non-3GPP access. PGW-C + SMF and UE locally release the context related to ATSSS operation, e.g. ATSSS rules and Measurement Assistance Information for the relevant session. If the UE and the network support MA PDU Session with 3GPP access connected to EPC, the UE includes a "MA PDU Request" indication and the PDU Session ID in the PCO, the SMF should keep the user-plane resources over non-3GPP access in 5GC and use the PDN Connection as the 3GPP access leg of the MA PDU Session. - In step 13, during the additional PDN Connectivity Procedure, if the MA PDU Session is established in both 3GPP and non-3GPP accesses and if the UE and the network support MA PDU Session with 3GPP access connected to EPC, the UE includes a "MA PDU Request" indication and the PDU Session ID in the PCO, the SMF should keep the user-plane resources over non-3GPP access in 5GC and use the PDN Connection as the 3GPP access leg of the MA PDU Session. If the UE and the network does not support MA PDU Session with 3GPP access connected to EPC and the MA PDU Session is moved to EPS, the PGW-C + SMF triggers the MA PDU Session Release procedure over non-3GPP access. PGW-C + SMF and UE locally release the context related to ATSSS operation, e.g. ATSSS rules and Measurement Assistance Information for the relevant session(s). - Step 14 is also performed for the MA PDU session(s) transferred to EPS. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.22.6.2.5 |
4,752 | 19.4.2.9A.5 Replacement field used in DNS-based Discovery of regulatory requirements for emergency services | The requirements specified in clause 19.4.2.9.5 for the Replacement field used in DNS-based Discovery of regulatory requirements shall apply with the following modification. The replacement field shall take the form of an Operator Identifier based Emergency ePDG FQDN as specified in clause 19.4.2.9A.2. As an example, the NAPTR records associated to the Visited Country FQDN for MCC 345, and for MNC 012, 013 and 014, are provisioned in the DNS as: sos.epdg.epc.mcc345.visited-country.pub.3gppnetwork.org ; IN NAPTR order pref. flag service regexp replacement IN NAPTR 100 999 "" "" sos.epdg.epc.mnc012.mcc345.pub.3gppnetwork.org IN NAPTR 100 999 "" "" sos.epdg.epc.mnc013.mcc345.pub.3gppnetwork.org IN NAPTR 100 999 "" "" sos.epdg.epc.mnc014.mcc345.pub.3gppnetwork.org | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 19.4.2.9A.5 |
4,753 | – Phy-ParametersMRDC | The IE Phy-ParametersMRDC is used to convey physical layer capabilities for MR-DC. Phy-ParametersMRDC information element -- ASN1START -- TAG-PHY-PARAMETERSMRDC-START Phy-ParametersMRDC ::= SEQUENCE { naics-Capability-List SEQUENCE (SIZE (1..maxNrofNAICS-Entries)) OF NAICS-Capability-Entry OPTIONAL, ..., [[ spCellPlacement CarrierAggregationVariant OPTIONAL ]], [[ -- R1 18-3b: Semi-statically configured LTE UL transmissions in all UL subframes not limited to tdm-pattern in case of TDD PCell tdd-PCellUL-TX-AllUL-Subframe-r16 ENUMERATED {supported} OPTIONAL, -- R1 18-3a: Semi-statically configured LTE UL transmissions in all UL subframes not limited to tdm-pattern in case of FDD PCell fdd-PCellUL-TX-AllUL-Subframe-r16 ENUMERATED {supported} OPTIONAL ]] } NAICS-Capability-Entry ::= SEQUENCE { numberOfNAICS-CapableCC INTEGER(1..5), numberOfAggregatedPRB ENUMERATED {n50, n75, n100, n125, n150, n175, n200, n225, n250, n275, n300, n350, n400, n450, n500, spare}, ... } -- TAG-PHY-PARAMETERSMRDC-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
4,754 | Annex I (normative): Security requirements for RNCs in exposed locations I.1 General | RNCs may be deployed at exposed locations where they run a higher risk of physical attack than RNCs in physically protected parts of the operator domain. For such deployments, RNCs adhering to the security requirements in this Annex should be used. RNCs in other deployments are not required to adhere to these requirements. RNCs may be found in exposed locations e.g. when RNC and NB are co-located in one node (collapsed RNC / NBs). NOTE: These security requirements have been modelled after those in clause 5.3 of TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [28]. These requirements apply in addition to the security requirements stated for Iu and Iur interfaces in Annex D of TS 33.210[ Network Domain Security (NDS); IP network layer security ] [39]. | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | Annex |
4,755 | 5.3.5 Handling of the periodic tracking area update timer and mobile reachable timer (S1 mode only) | The periodic tracking area updating procedure is used to periodically notify the availability of the UE to the network. The procedure is controlled in the UE by timer T3412. The value of timer T3412 is sent by the network to the UE in the ATTACH ACCEPT message and can be sent in the TRACKING AREA UPDATE ACCEPT message. The UE shall apply this value in all tracking areas of the list of tracking areas assigned to the UE until a new value is received. If timer T3412 received by the UE in an ATTACH ACCEPT or TRACKING AREA UPDATE ACCEPT message contains an indication that the timer is deactivated or the timer value is zero, then timer T3412 is deactivated and the UE shall not perform the periodic tracking area updating procedure. Timer T3412 is reset and started with its initial value, when the UE changes from EMM-CONNECTED to EMM-IDLE mode. Timer T3412 is stopped when the UE enters EMM-CONNECTED mode or the EMM-DEREGISTERED state. If the UE is attached for emergency bearer services, and timer T3412 expires, the UE shall not initiate a periodic tracking area updating procedure, but shall locally detach from the network. When the UE is camping on a suitable cell, it may re-attach to regain normal service. When a UE is not attached for emergency bearer services, and timer T3412 expires, the periodic tracking area updating procedure shall be started and the timer shall be set to its initial value for the next start. If the UE is not attached for emergency bearer services, and is in a state other than EMM-REGISTERED.NORMAL-SERVICE when timer T3412 expires, the periodic tracking area updating procedure is delayed until the UE returns to EMM-REGISTERED.NORMAL-SERVICE. NOTE 1: When the UE returns to EMM-REGISTERED.NORMAL-SERVICE and it needs to initiate other EMM procedure than the periodic tracking area updating procedure then, based on UE implementation, the EMM procedure can take precedence. If ISR is activated, the UE shall keep both timer T3412 and timer T3312. The two separate timers run in the UE for updating MME and SGSN independently. The UE shall start timer T3423, if timer T3412 expires, and timer T3346 is running or the UE is in one of the following states: - EMM-REGISTERED.NO-CELL-AVAILABLE; - EMM-REGISTERED.PLMN-SEARCH; - EMM-REGISTERED.UPDATE-NEEDED; or - EMM-REGISTERED.LIMITED-SERVICE. The UE shall initiate the tracking area updating procedure and stop timer T3423 when it enters state EMM-REGISTERED.NORMAL-SERVICE before timer T3423 expires. After expiry of timer T3423 the UE shall set its TIN to "P-TMSI". If timer T3423 expires the UE shall memorize that it has to initiate a tracking area updating procedure when it returns to state EMM-REGISTERED.NORMAL-SERVICE. If the UE is attached to both EPS and non-EPS services, and if timer T3412 expires or timer T3423 expires when the UE is in EMM-REGISTERED.NO-CELL-AVAILABLE state, then the UE shall initiate the combined tracking area updating procedure indicating "combined TA/LA updating with IMSI attach" when the UE returns to EMM-REGISTERED.NORMAL-SERVICE state. When the network includes T3412 extended value IE in the ATTACH ACCEPT message or TRACKING AREA UPDATE ACCEPT message, the network uses timer T3412 extended value IE as the value of timer T3412. The network supervises the periodic tracking area updating procedure of the UE by means of the mobile reachable timer. If the UE is not attached for emergency bearer services, the mobile reachable timer shall be longer than T3412. In this case, by default, the mobile reachable timer is 4 minutes greater than timer T3412. If ISR is not activated, the network behaviour upon expiry of the mobile reachable timer is network dependent, but typically the network stops sending paging messages to the UE on the first expiry, and may take other appropriate actions. If the UE is attached for emergency bearer services, the MME shall set the mobile reachable timer with a value equal to timer T3412. When the mobile reachable timer expires, the MME shall locally detach the UE. The mobile reachable timer shall be reset and started with the value as indicated above, when the MME releases the NAS signalling connection for the UE. The mobile reachable timer shall be stopped when a NAS signalling connection is established for the UE. Upon expiry of the mobile reachable timer the network shall start the implicit detach timer. The value of the implicit detach timer is network dependent. If ISR is activated, the default value of the implicit detach timer is 4 minutes greater than timer T3423. If the implicit detach timer expires before the UE contacts the network, the network shall implicitly detach the UE. If the MME includes timer T3346 in the TRACKING AREA UPDATE REJECT message or the SERVICE REJECT message and timer T3346 is greater than timer T3412, the MME sets the mobile reachable timer and the implicit detach timer such that the sum of the timer values is greater than timer T3346. If the network includes the T3324 value IE in the ATTACH ACCEPT message or TRACKING AREA UPDATE ACCEPT message, and if the UE is not attached for emergency bearer services and has no PDN connection for emergency bearer services the MME shall set the active timer to a value equal to the value of timer T3324. NOTE 2: Timer T3324 is specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13]. If the UE has established a PDN connection for emergency services after receiving the timer T3324 value IE in the ATTACH ACCEPT message or the last TRACKING AREA UPDATE ACCEPT message, the active timer shall not be started. The active timer shall be reset and started with the value as indicated above, when the MME releases the NAS signalling connection for the UE. The active timer shall be stopped when an NAS signalling connection is established for the UE. The network behaviour upon expiry of the active timer is network dependent, but typically the network stops sending paging messages to the UE on the first expiry, and may take other appropriate actions. NOTE 3: ISR is not activated when the network includes the T3324 value IE in the ATTACH ACCEPT message or TRACKING AREA UPDATE ACCEPT message. The implicit detach timer shall be stopped when a NAS signalling connection is established for the UE. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.3.5 |
4,756 | 5.3.5.6.4 DRB release | The UE shall: 1> for each drb-Identity value included in the drb-ToReleaseList that is part of the current UE configuration; or 1> for each drb-Identity value that is to be released as the result of full configuration according to 5.3.5.11: 2> release the PDCP entity and the drb-Identity; 2> if SDAP entity associated with this DRB is configured: 3> indicate the release of the DRB to SDAP entity associated with this DRB (TS 37.324[ Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Service Data Adaptation Protocol (SDAP) specification ] [24], clause 5.3.3); 2> if the DRB is associated with an eps-BearerIdentity: 3> if a new bearer is not added either with NR or E-UTRA with same eps-BearerIdentity: 4> indicate the release of the DRB and the eps-BearerIdentity of the released DRB to upper layers. NOTE 1: The UE does not consider the message as erroneous if the drb-ToReleaseList includes any drb-Identity value that is not part of the current UE configuration. NOTE 2: Whether or not the RLC and MAC entities associated with this PDCP entity are reset or released is determined by the CellGroupConfig. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.5.6.4 |
4,757 | 28.7.4 Emergency NAI for Limited Service State | This clause describes the format of the UE identification when UE is performing an emergency registration and IMSI is not available or not authenticated. The Emergency NAI for Limited Service State shall take the form of an NAI, and shall have the form username@realm as specified in clause 2.2 of IETF RFC 7542 [126]. The exact format shall be: imei<IMEI>@sos.invalid NOTE: The top level domain ".invalid" is a reserved top level domain, as specified in IETF RFC 2606 [64], and is used here due to the fact that this NAI never needs to be resolved for routing. or if IMEI is not available, mac<MAC>@sos.invalid For example, if the IMEI is 219551288888888, the Emergency NAI for Limited Service State then takes the form of [email protected]. For example, if the MAC address is 44-45-53-54-00-AB, the Emergency NAI for Limited Service State then takes the form of [email protected], where the MAC address is represented in hexadecimal format without separators. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 28.7.4 |
4,758 | 4.3.8.3 MME selection function | The MME selection function selects an available MME for serving a UE. The selection is based on network topology, i.e. the selected MME serves the UE's location and for overlapping MME service areas, the selection may prefer MMEs with service areas that reduce the probability of changing the MME. When a MME/SGSN selects a target MME, the selection function performs a simple load balancing between the possible target MMEs. In networks that deploy dedicated MMEs/SGSNs for UEs configured for low access priority, the possible target MME selected by source MME/SGSN is typically restricted to MMEs with the same dedication. When a MME/SGSN supporting DCNs selects a target MME, the selected target MME should be restricted to MMEs that belong to the same DCN. The DNS procedure may be used by the source CN node to select the target MME from a given DCN. If both low access priority and UE Usage Type parameter are used for MME selection, selection based on UE Usage type parameter overrides selection based on the low access priority indication. When a MME supporting CIoT EPS Optimisation(s) selects a target MME, the selected MME should all support the CIoT EPS Optimisations applicable to the given UE's attachment. if the source MME is unable to find a target MME matching all CIoT EPS Optimisation(s) applicable to a given UE's attachment, then the source MME, based on implementation, selects a target MME which provides the CIoT EPS Optimisation(s) best applicable to that UE's attachment. When an eNodeB selects an MME, the eNodeB may use a selection function which distinguishes if the GUMMEI is mapped from P-TMSI/RAI or is a native GUMMEI. The indication of mapped or native GUMMEI shall be signalled by the UE to the eNodeB as an explicit indication. The eNodeB may differentiate between a GUMMEI mapped from P-TMSI/RAI and a native GUMMEI based on the indication signalled by the UE. Alternatively, the differentiation between a GUMMEI mapped from P-TMSI/RAI and a native GUMMEI may be performed based on the value of most significant bit of the MME Group ID, for PLMNs that deploy such mechanism. In this case, if the MSB is set to "0" then the GUMMEI is mapped from P-TMSI/RAI and if MSB is set to "1", the GUMMEI is a native one. Alternatively the eNodeB makes the selection of MME only based on the GUMMEI without distinguishing on mapped or native. When an eNodeB selects an MME, the selection shall achieve load balancing as specified in clause 4.3.7.2. When an eNodeB selects an MME, the selection shall consider the IAB support capability if the UE includes an IAB-Indication in the RRC connection establishment signalling as defined in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [37]. When the UE attempts to establish a signalling connection and the following conditions are met: - the eNodeB serves more than one country (e.g. it supports E-UTRA satellite access); and - the eNodeB knows in what country the UE is located; and - the eNodeB is connected to MMEs serving different PLMNs of different countries; and - the UE provides an S-TMSI or GUMMEI, which indicates an MME serving a different country to where the UE is currently located; and - the eNodeB is configured to enforce selection of the MME based on the country the UE is currently located; then the eNodeB shall select an MME serving a PLMN corresponding to the UE's current location. How the eNodeB selects the MME in this case is defined in TS 36.410[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 general aspects and principles ] [92]. When DCNs are deployed, to maintain a UE in the same DCN when the UE enters a new MME pool area, the eNodeB's NNSF should have configuration that selects, based on the MMEGIs or NRIs of neighbouring pool areas, a connected MME from the same DCN. Alternately, for PLMN wide inter-pool intra-RAT mobility, the operator may divide up the entire MMEGI and NRI value space into non-overlapping sets with each set allocated to a particular DCN. In this case all eNodeBs may be configured with the same MME selection configuration. If UE assisted DCN selection feature is supported and a DCN-ID is provided by the UE, the DCN-ID shall be used in the eNodeB for MME selection to maintain the same DCN when the serving MME is not available. When selecting an MME for a UE that is using the NB-IoT RAT, and/or for a UE that signals support for CIoT EPS Optimisations in RRC signalling (as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [37], for NB-IoT, UE indicates whether it supports "User Plane CIoT EPS Optimisation" and "EPS Attach without PDN Connectivity". And for WB-E-UTRAN, UE indicates whether it supports "Control Plane CIoT EPS Optimisation", "User Plane CIoT EPS Optimisation" and "EPS Attach without PDN Connectivity"), the eNodeB's MME selection algorithm shall select an MME taking into account the MME's support (or non-support) for the Release 13 NAS signalling protocol. When DCN are deployed for the purpose of CIoT EPS Optimisation, UE included CIoT EPS Optimisation information in the RRC signalling, may depending on eNodeB configuration, be used to perform initial DCN selection. When Restricted Local Operator Services feature is supported, a UE initiates access to Restricted Local Operator Services via RRC signalling as defined in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [37]. The UE included RLOS indication in RRC signalling may be used by the eNodeB to select an appropriate MME. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.3.8.3 |
4,759 | 9.11.3.93 N3IWF identifier | The purpose of the N3IWF identifier information element is to enable the network to assign the UE, a suitable N3IWF for the requested NSSAI. The N3IWF identifier information element is coded as shown in figure 9.11.3.93.1, figure 9.11.3.93.2, figure 9.11.3.93.3 and table 9.11.3.93.1. The N3IWF identifier information element is a type 4 information element with a minimum length of 7 octets. Figure 9.11.3.93.1: N3IWF identifier information element Figure 9.11.3.93.2: N3IWF address entry (N3IWF identifier type = "IPv4", "IPv6" or "IPv4v6") Figure 9.11.3.93.3: N3IWF identifier entry (N3IWF identifiertype ="FQDN") Table 9.11.3.93.1: N3IWF address entry | 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.93 |
4,760 | 4.7.7.5 Authentication not accepted by the network | If the authentication response (RES or SRES) is not valid, the network response depends upon the type of identity used by the MS in the first message: - If the P-TMSI has been used, the network may decide to initiate the identification procedure. If the IMSI given by the MS differs from the one the network had associated with the P-TMSI, the authentication should be restarted with the correct parameters. If the IMSI provided by the MS is the expected one (i.e. authentication has really failed), the network should send an AUTHENTICATION AND CIPHERING REJECT message to the mobile station. - If the IMSI has been used, or the network decides not to try the identification procedure, an AUTHENTICATION AND CIPHERING REJECT message should be transferred to the MS. Upon receipt of an AUTHENTICATION AND CIPHERING REJECT message, a) if the message has been successfully integrity checked by the lower layers, the MS shall set the GPRS update status to GU3 ROAMING NOT ALLOWED and shall delete the P-TMSI, P-TMSI signature, RAI and GPRS ciphering key sequence number stored. If available, also the TMSI, LAI and ciphering key sequence number shall be deleted and the update status shall be set to U3 ROAMING NOT ALLOWED. The SIM/USIM shall be considered as invalid until switching off or the SIM/USIM is removed. If the MS maintains a counter for "SIM/USIM considered invalid for GPRS services", then the MS shall set this counter to MS implementation-specific maximum value. If the MS maintains a counter for "SIM/USIM considered invalid for non-GPRS services", then the MS shall set this counter to MS implementation-specific maximum value. If S1 mode is supported by the MS, the MS shall in addition handle the EMM parameters EMM state, EPS update status, last visited registered TAI, TAI list, GUTI and KSIASME as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120] for the case when an EPS authentication is not accepted by the network. b) if the message is received without integrity protection, then the MS shall start timer T3247 with a random value uniformly drawn from the range between 30 minutes and 60 minutes, if the timer is not running (see subclause 4.1.1.6A). Additionally, the MS shall: - if the MS maintains a counter for "SIM/USIM considered invalid for GPRS services" events and the counter has a value less than an MS implementation-specific maximum value, proceed as specified in subclause 4.1.1.6A, list item 6.a) for the case an ATTACH REJECT or ROUTING AREA UPDATE REJECT message is received without integrity protection; and - otherwise proceed as specified under list item a) above for the case that the message has been successfully checked by the lower layers. List item b) above is also applicable, if the message is received in A/Gb mode. If the AUTHENTICATION AND CIPHERING REJECT message is received, the MS shall abort any GMM procedure, shall stop any of the retransmission timers that are running (e.g. T3310, T3317, T3330, T3321, T3318 or T3320 and shall enter state GMM-DEREGISTERED. In UTRAN Iu mode, depending on local regulations or operator preference for emergency bearer services, if the MS has a PDN connection for emergency bearer services established or is establishing a PDN connection for emergency bearer services, the SGSN need not follow the procedures specified for the authentication failure in the present subclause, the SGSN can continue with the ongoing GMM specific procedure or Session Management procedure. Upon completion of the GMM procedure or Session management procedure, the SGSN shall deactivate all non-emergency PDP contexts, if any, by initiating a PDP context deactivation procedure. The network shall consider the MS to be attached for emergency bearer services only. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.7.7.5 |
4,761 | 9.11.3.92 SNPN list | The purpose of the SNPN list information element is to provide a list of SNPN identities. The SNPN list information element is coded as shown in figure 9.11.3.92.1, table 9.11.3.92.1, figure 9.11.3.92.2 and table 9.11.3.92.2. The SNPN list is a type 4 information element with a minimum length of 11 octets and a maximum length of 137 octets. Figure 9.11.3.92.1: SNPN list information element Table 9.11.3.92.1: SNPN list information element Figure 9.11.3.92.2: SNPN identity i Table 9.11.3.92.2: SNPN identity i | 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.92 |
4,762 | C.3.3 Profile 3: management of sequence numbers which are entirely time-based | Generation of sequence numbers: This follows the scheme for the generation of sequence numbers specified in Annex C.1.1.3. The following parameter values are suggested for reference: Time unit of the clock: It has to be chosen in such a way that no two requests for a batch of authentication vectors arrive during one time unit. Value = 0.1 seconds Length of in bits = 5. Start conditions: GLC = 1 and, for all users, DIF = 0. Verification of sequence numbers in the USIM: This is done according to the handling of sequence numbers in the USIM specified in Annex C.2. Length of the array: a = 32. This satisfies the requirement in section 6.3.2 that the mechanism for the verification of sequence numbers shall ensure that a sequence number can still be accepted if it is among the last x sequence numbers generated. Protection against wrap around: Choose = 228. Choosing = 228 means that an attack to force the counter in the USIM to wrap around would require at least SEQmax/ = 215 > 32.000 successful authentications (cf. note 6 of C.2.3). Note 7 of C.2.3 does not apply. Age limit for sequence numbers: The use of such a limit is optional. The choice of a value for the parameter L affects only the USIM. It has no impact on the choice of other parameters and it entirely up to the operator, depending on his security policy. Therefore no particular value is suggested here. To give an example: if the policy stipulates that authentication vectors older than x time units shall be rejected then L has to be set to x. User anonymity: the value of SQN does not allow to trace the user over longer periods. Therefore, there may be no need to conceal SQN by an anonymity key as specified in section 6.3. | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | C.3.3 |
4,763 | 5.5 Transport Channels | The physical layer offers information transfer services to MAC and higher layers. The physical layer transport services are described by how and with what characteristics data are transferred over the radio interface. An adequate term for this is "Transport Channel". This should be clearly separated from the classification of what is transported, which relates to the concept of logical channels at MAC sublayer. Downlink transport channel types are: 1. Broadcast Channel (BCH) characterised by: - fixed, pre-defined transport format; - requirement to be broadcast in the entire coverage area of the cell, either as a single message or by beamforming different BCH instances. 2. Downlink Shared Channel (DL-SCH) characterised by: - support for HARQ; - support for dynamic link adaptation by varying the modulation, coding and transmit power; - possibility to be broadcast in the entire cell; - possibility to use beamforming; - support for both dynamic and semi-static resource allocation; - support for UE discontinuous reception (DRX) to enable UE power saving. 3. Paging Channel (PCH) characterised by: - support for UE discontinuous reception (DRX) to enable UE power saving (DRX cycle is indicated by the network to the UE); - requirement to be broadcast in the entire coverage area of the cell, either as a single message or by beamforming different BCH instances; - mapped to physical resources which can be used dynamically also for traffic/other control channels. Uplink transport channel types are: 1. Uplink Shared Channel (UL-SCH) characterised by: - possibility to use beamforming; - support for dynamic link adaptation by varying the transmit power and potentially modulation and coding; - support for HARQ; - support for both dynamic and semi-static resource allocation. 2. Random Access Channel(s) (RACH) characterised by: - limited control information; - collision risk. Sidelink transport channel types are: 1. Sidelink broadcast channel (SL-BCH) characterised by: - pre-defined transport format. 2. Sidelink shared channel (SL-SCH) characterised by: - support for unicast transmission, groupcast transmission and broadcast transmission; - support for both UE autonomous resource selection and scheduled resource allocation by NG-RAN; - support for both dynamic and semi-static resource allocation when UE is allocated resources by the NG-RAN; - support for HARQ; - support for dynamic link adaptation by varying the transmit power, modulation and coding; - support for SL discontinuous reception (SL DRX) to enable UE power saving. Association of transport channels to physical channels is described in TS 38.202[ NR; Services provided by the physical layer ] [20]. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.5 |
4,764 | 4.3.12.5 QoS for Emergency Services | Where local regulation require supporting calls from an unauthorised caller, the MME may not have subscription data. Additionally, the local network may want to provide IMS emergency services support differently than what is allowed by a UE subscription. Therefore, the initial QoS values used for establishing emergency bearer services are configured in the MME in the MME Emergency Configuration Data. NOTE: For IMS emergency services prior to this Release of this specification, dynamic PCC support was not required in the specifications. In such cases, the PDN GW sets the ARP value that is reserved for emergency services, which the PDN GW bases on the usage of the Emergency APN. This functionality is used by the Attach procedure and by the UE Requested PDN Connectivity procedure, in both cases when establishing emergency bearer services. | 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.5 |
4,765 | 6.6.2.2.2 Minimum requirement (network signalled value "NS_04") | Additional spectrum emission requirements are signalled by the network to indicate that the UE shall meet an additional requirement for a specific deployment scenario as part of the cell handover/broadcast message. When "NS_04" is indicated in the cell, the power of any UE emission shall not exceed the levels specified in Table 6.6.2.2.2-1. Table 6.6.2.2.2-1: Additional requirements NOTE: As a general rule, the resolution bandwidth of the measuring equipment should be equal to the measurement bandwidth. However, to improve measurement accuracy, sensitivity and efficiency, the resolution bandwidth may be smaller than the measurement bandwidth. When the resolution bandwidth is smaller than the measurement bandwidth, the result should be integrated over the measurement bandwidth in order to obtain the equivalent noise bandwidth of the measurement bandwidth. | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.6.2.2.2 |
4,766 | 5.35A.6 Providing cell ID/TAC of MBSR for services | The TAC and cell ID broadcasted by the MBSR cell(s) are configured as specified in TS 38.470[ NG-RAN; F1 general aspects and principles ] [165]. After the MBSR is authorized as defined in 5.35A.4, when a UE is served by a cell of this MBSR, the IAB-donor-CU may provide 'Additional ULI' in addition to User Location Information, in N2 messages. The 'Additional ULI' is the ULI of the IAB-UE. The AMF may consider the 'Additional ULI' when it determines UE location and manages the UE location related functions (e.g. Mobility Restrictions). When the AMF provides user location information to other NFs (e.g. LMF as specified in clause 5.9 of TS 23.273[ 5G System (5GS) Location Services (LCS); Stage 2 ] [87]) for a UE connected via MBSR, the AMF may also send the Additional ULI received via N2 messages. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.35A.6 |
4,767 | – NZP-CSI-RS-Resource | The IE NZP-CSI-RS-Resource is used to configure Non-Zero-Power (NZP) CSI-RS transmitted in the cell where the IE is included, which the UE may be configured to measure on (see TS 38.214[ NR; Physical layer procedures for data ] [19], clause 5.2.2.3.1). A change of configuration between periodic, semi-persistent or aperiodic for an NZP-CSI-RS-Resource is not supported without a release and add. NZP-CSI-RS-Resource information element -- ASN1START -- TAG-NZP-CSI-RS-RESOURCE-START NZP-CSI-RS-Resource ::= SEQUENCE { nzp-CSI-RS-ResourceId NZP-CSI-RS-ResourceId, resourceMapping CSI-RS-ResourceMapping, powerControlOffset INTEGER (-8..15), powerControlOffsetSS ENUMERATED{db-3, db0, db3, db6} OPTIONAL, -- Need R scramblingID ScramblingId, periodicityAndOffset CSI-ResourcePeriodicityAndOffset OPTIONAL, -- Cond PeriodicOrSemiPersistent qcl-InfoPeriodicCSI-RS TCI-StateId OPTIONAL, -- Cond Periodic ..., [[ subcarrierSpacing-r18 SubcarrierSpacing OPTIONAL, -- Cond LTM absoluteFrequencyPointA-r18 ARFCN-ValueNR OPTIONAL, -- Cond LTM cyclicPrefix-r18 ENUMERATED {extended} OPTIONAL -- Cond LTM ]] } -- TAG-NZP-CSI-RS-RESOURCE-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
4,768 | 23.3.2.2 Relay Node Vendor-Specific OAM System | As part of the startup procedure, relay nodes (see 3GPP TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [91], clause 4.7) needs to discover its Operations and Maintainence (OAM) system. A relay node vendor-specific OAM system within an operator's network is identified using the relay node type allocation code from IMEI or IMEISV (IMEI-TAC), MNC and MCC from IMSI and in some cases also tracking area code information associated to the eNB serving the relay node. A subdomain name for use by EUTRAN OAM system nodes shall be derived from the MNC and MCC by adding the label "eutran" to the beginning of the OAM System Realm/Domain (see clause 23.2). The vendor-specific relay node OAM system FQDN shall be constructed as following: - tac-lb<TAC-low-byte>.tac-hb<TAC-high-byte>.imei-tac<IMEI-TAC>.eutran-rn.oam.mnc<MNC>.mcc<MCC>.3gppnetwork.org The IMEI-TAC is 8 decimal digits (see clause 6.2). NOTE: IMEI-TAC is used for the type allocation code from IMEI or IMEISV instead of TAC in this clause in order to separate it from the tracking area code (TAC). The TAC is a 16 bit integer. <TAC-high-byte> is the hexadecimal string of the most significant byte in the TAC and <TAC-low-byte > is the hexadecimal string of the least significant byte. If there are less than 2 significant digits in <TAC-high-byte> or <TAC-low-byte >, "0" digit(s) shall be inserted at the left side to fill the 2 digit coding. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 23.3.2.2 |
4,769 | – SemiStaticChannelAccessConfig | The IE SemiStaticChannelAccessConfig is used to configure channel access parameters when the network is operating in semi-static channel access mode (see clause 4.3 in TS 37.213[ Physical layer procedures for shared spectrum channel access ] [48]. SemiStaticChannelAccessConfig information element -- ASN1START -- TAG-SEMISTATICCHANNELACCESSCONFIG-START SemiStaticChannelAccessConfig-r16 ::= SEQUENCE { period-r16 ENUMERATED {ms1, ms2, ms2dot5, ms4, ms5, ms10} } -- TAG-SEMISTATICCHANNELACCESSCONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
4,770 | 4.2.11.2 Number of UEs per network slice availability check and update procedure | This clause applies to Non-Hierarchical and centralized NSAC architectures. The difference between the two architectures for the various steps, where applicable, is described at the end of the clause. The number of UEs per network slice availability check and update procedure is to update (i.e. increase or decrease) the number of UEs registered with an S-NSSAI which is subject to NSAC. The AMF is configured with the information indicating which network slice is subject to NSAC. Figure 4.2.11.2-1: Number of UEs per network slice availability check and update procedure 1. If the AMF is not aware of which NSACF to communicate, the AMF performs NSACF discovery as described in clause 6.3.22 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] and in clause 5.2.7.3.2. The AMF triggers the Number of UEs per network slice availability check and update procedure to update the number of UEs registered with a network slice when a network slice subject to NSAC is included in the Allowed NSSAI or Partially Allowed NSSAI (i.e. the AMF requests to register the UE with the S-NSSAI) or removed from the Allowed NSSAI or Partially Allowed NSSAI (i.e. the AMF requests to de-register the UE from the S-NSSAI) for a UE. The trigger event at the AMF also includes the change of Allowed NSSAI or Partially Allowed NSSAI in the case of inter-AMF mobility. The procedure is triggered in the following cases: - At UE Registration procedure, according to clause 4.2.2.2.2 (including Registration types of Initial Registration or Mobility Registration Update in inter-AMF mobility in CM-CONNECTED or CM-IDLE state): - before the Registration Accept in step 21 if the EAC mode is active; or - after the Registration Accept message if the EAC mode is not active; - At UE Deregistration procedure, as per clause 4.2.2.3, after the Deregistration procedure is completed; - At UE Configuration Update procedure (which may result from NSSAA procedure or subscribed S-NSSAI change): - before the UE Configuration Update message if the EAC mode is active and the update flag is to increase; or - after the UE Configuration Update message if the EAC mode is active and the update flag is to decrease; or - after the UE Configuration Update message if the EAC mode is not active. NOTE 1: Depending on the deployment, there may be different NSACF for different S-NSSAI subject to NSAC and hence, during the registration, AMF triggers the Number of UEs per network slice availability check and update procedure to multiple NSACFs. 2. The AMF sends Nnsacf_NSAC_NumOfUEsUpdate_Request message to the NSACF. The AMF includes in the message the UE ID, Access Type to which the Allowed NSSAI or Partially Allowed NSSAI is applied, the S-NSSAI(s), the NF ID and the update flag which indicates whether the number of UEs registered with the S-NSSAI(s) is to be increased when the UE has gained registration to network slice(s) subject to NSAC or the number of UEs registered with the S-NSSAI(s) is to be decreased when the UE has deregistered from S-NSSAI(s) or could not renew its registration to an S-NSSAI subject to NSAC. If this is the first time to perform NSAC procedure for the S-NSSAI towards the NSACF, the AMF includes notification endpoint for EAC Notification to implicitly subscribe the EAC notification for the S-NSSAI from the NSACF. 3. The NSACF determines whether the Access Type provided by the AMF is configured for the NSAC based on its configuration. If the Access Type is not configured for the NSAC, the NSACF always accepts the request from the AMF without increasing or decreasing the number of UEs. If the Access Type is configured for the NSAC, the NSACF updates the current number of UEs registered for the S-NSSAI, i.e. increases or decrease the number of UEs registered per network slice based on the information provided by the AMF in the update flag parameter. If the update flag parameter from the AMF indicates increase, the following applies: - If the UE ID is already in the list of UEs registered with the network slice, the current number of UEs is not increased as the UE has already been counted as registered with the network slice. The NSACF creates a new entry associated with this new update and shall also maintain the old entry associated with previous update. The multiple entries for the same UE ID in the NSACF are differentiated based on the NF ID of the NF sending the update request. The NSACF removes the entry associated with the NF ID upon reception of a request having update flag indicating decrease. NOTE 2: The use case of having two or more entries in the NSACF for the same UE can happen during (a) inter-AMF mobility when the new AMF request update to the NSACF before the old AMF sends request to deregister the UE; or (b) PDN connections establishment in the EPC when multiple SMF +PGW-Cs (i.e. used for different PDN Connections associated with the same S-NSSAI) send update requests for maximum number of UEs to the NSACF. NOTE 3: To handle AMF graceful removal, the NSACF can subscribe for unavailability notifications with the AMF (directly or via NRF) as described in clause 5.21.2.2 and act accordingly, e.g. update the NF ID with the target AMF ID. - If the UE ID is not in the list of UE IDs registered with the network slice and the maximum number of UEs registered with the network slice has not been reached yet, the NSACF adds the UE ID in the list of UEs registered with the network slice as a new entry associated with this new update and increases the current number of the UEs registered with the network slice. If the UE ID is not in the list of UEs registered with that S-NSSAI and the maximum number of UEs for that S-NSSAI has already been reached, then the NSACF returns a result parameter indicating that the maximum number of UEs registered with the network slice has been reached. If the update flag parameter from the AMF indicates decrease and if there is only one entry associated with the UE ID, the NSACF removes the UE ID from the list of UEs registered with the network slice for each of the S-NSSAI(s) indicated in the request from the AMF and also the NSACF decreases the number of UEs per network slice that is maintained by the NSACF for each of these network slices. If there are multiple entries associated with the UE ID, the NSACF removes the entry associated with the NF ID but the UE ID is kept in the list of UEs registered with the S-NSSAI. The NSACF takes access type into account for increasing and decreasing the number of UEs per network slice as described in clause 5.15.11.1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The NSACF stores the notification endpoint for EAC Notification associated with the S-NSSAI if it is received from the AMF. The NSACF can use this AMF notification endpoint to update the EAC mode as described in clause 4.2.11.3. NOTE 4: This enables the NSACF to maintain up-to-date information about the AMFs serving the S-NSSAIs. 4. The NSACF returns the Nnsacf_NSAC_NumOfUEsUpdate_Response message including Result indication per S-NSSAI. The Result indication includes either 'maximum number of UEs registered with the network slice reached' or 'maximum number of UEs registered with the network slice not reached'. At UE Registration procedure, if only some of the S-NSSAIs reached the maximum number of UEs per S-NSSAI, the AMF sends a Registration Accept message to the UE in which the AMF includes the rejected S-NSSAI(s) in the rejected NSSAI list for which the NSACF has indicated that the maximum number of UEs per network slice has been reached and for each rejected S-NSSAI the AMF includes a reject cause set to 'maximum number of UEs per network slice reached' and optionally a back-off timer. When for all the Requested S-NSSAI(s) provided in step 2 the NSACF returned the maximum number of UEs per network slice has been reached and if one or more subscribed S-NSSAIs are marked as default in the subscription data and not subject to NSAC, the AMF can decide to include these Default Subscribed S-NSSAIs in the Allowed NSSAI. Otherwise, the AMF rejects the UE request for registration. In the Registration Reject message, the AMF includes the rejected S-NSSAI(s) in the rejected NSSAI parameter and for each rejected S-NSSAI the AMF includes a reject cause to indicate that the maximum number of UEs per network slice has been reached and optionally a back-off timer. NOTE 5: If the use case requires the UE to remain reachable at all times with at least one slice, it is recommended that at least one of the Subscribed S-NSSAIs is marked as the default S-NSSAI which is not subject to NSAC. This will ensure the UE is able to access to services even when maximum number of UEs per network slice has been reached. For a centralized architecture the following differences apply: - In step 2, the AMF additionally includes the NSAC service area the AMF belongs to, if available, as an additional parameter in the Nnsacf_NSAC_NumOfUEsUpdate_Request. - In step 3, based on operator configuration, the NSACF performs the validation against the maximum number of Registered UEs registered per NSAC service area defined for the network slice if applicable and available, or the maximum number of Registered UEs in the entire PLMN for the network slice. Additionally the NSACF stores the NSAC service area of AMF if available. NOTE 6: When a centralized NSAC architecture is deployed, NSACF does not perform any readmission at inter-AMF mobility since the UE is already admitted if the validation of maximum number of Registered UEs against the entire PLMN. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.2.11.2 |
4,771 | 4.15.12 Event Exposure using Local NEF | This clause contains the description and the procedure for the exposure of QoS monitoring information via direct interaction between UPF (L-PSA UPF) and Local NEF/AF. Editor's note: It is FFS whether Local NEF is introduced or NEF is used instead. Figure 4.15.12-1: Event exposure using Local NEF 1. The UPF obtains QoS monitoring information as defined in clauses 5.8.2.18 and 5.45 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. 2. The UPF sends the notification related with QoS monitoring information over Nupf_EventExposure_Notify service operation according to the configuration from SMF as defined in clause 5.8.2.18 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The notification is sent to the Notification Target Address that may correspond (4a) to the AF or (4b) to the Local NEF. 3. If the Local NEF is used, it reports the QoS monitoring information to the AF by invoking Nnef_EventExposure_Notify service operation. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.15.12 |
4,772 | 5.30.2.10.2 Onboarding Network is an SNPN | 5.30.2.10.2.1 General A UE configured with Default UE credentials may register with an ON-SNPN for the provisioning of SO-SNPN credentials. 5.30.2.10.2.2 Architecture Figures 5.30.2.10.2.2-1, 5.30.2.10.2.2-2 and 5.30.2.10.2.2-3 depict the architecture for Onboarding of UEs in an ON-SNPN. Figure 5.30.2.10.2.2-1: Architecture for UE Onboarding in ON-SNPN when the DCS includes an AUSF and a UDM Figure 5.30.2.10.2.2-2: Architecture for UE Onboarding in ON-SNPN when the DCS includes a AAA Server used for primary authentication Figure 5.30.2.10.2.2-3: Architecture for UE Onboarding in ON-SNPN when the DCS is not involved during primary authentication NOTE 1: AUSF in the ON-SNPN interfaces with the DCS via NSSAAF as shown in Figure 5.30.2.10.2.2-2 owned by an entity that is internal or external to the ON-SNPN. NOTE 2: The functionality with respect to exchange information between PVS and SO-SNPN to provision SNPN credentials and other data from the SO-SNPN in the UE is out of 3GPP scope. NOTE 3: The dotted lines in Figure 5.30.2.10.2.2-1, Figure 5.30.2.10.2.2-2 and Figure 5.30.2.10.2.2-3 indicate that whether domains (e.g. DCS domain, PVS domain, and SO-SNPN) are separated depends on the deployment scenario. NOTE 4: See TS 33.501[ Security architecture and procedures for 5G System ] [29] for the functionality beyond AUSF, and other interfaces required for security. NOTE 5: When secondary authentication is used in the context of the UE onboarding architecture in Figure 5.30.2.10.2.2-3, the same S-NSSAI/DNN or different S-NSSAI/DNNs can be used for the onboarding PDU Sessions of different UEs even though the DN-AAA servers that authenticate the UEs can reside in different administrative domains. When the DCS is involved during mutual primary authentication during the Onboarding procedure (as in Figure 5.30.10.2.2-1 and Figure 5.30.10.2.2-2), the following applies: - When the DCS includes an AUSF and a UDM functionality, then the AMF selects AUSF in the DCS domain. The ON-SNPN and DCS domain are connected via N32 and SEPP which are not shown in the Figure 5.30.2.10.2.2-1. - When the DCS includes a AAA Server functionality, only NSI based SUPI is supported and the AMF selects AUSF in the ON-SNPN. Based on local configuration (e.g. using the realm part of the Onboarding SUCI), the AUSF skips the UDM selection and directly performs primary authentication towards DCS with AAA Server functionality using Default UE credentials for primary authentication. The AUSF uses an NSSAAF (and the NSSAAF may use a AAA-P which is not shown in the figure 5.30.2.10.2.2-2) to relay EAP messages towards the DCS including a AAA Server. The NSSAAF selects AAA Server based on the domain name corresponding to the realm part of the SUPI. NOTE 5: The AMF in ON-SNPN uses the Home Network Identifier of the Onboarding SUCI to select the DCS. It is assumed that the ON-SNPN is configured on per Home Network Identifier basis to determine whether to perform primary authentication with AUSF/UDM or AAA server. - Upon establishment of the PDU Session used for User Plane Remote Provisioning the ON-SNPN may trigger secondary authentication procedure, as described in clause 4.3.2.3 of TS 23.502[ Procedures for the 5G System (5GS) ] [3], with a DN-AAA using Default UE credentials for secondary authentication as described in clause I.9.2.4 of TS 33.501[ Security architecture and procedures for 5G System ] [29]. When the DCS is not involved during primary authentication (as in Figure 5.30.10.2.2-3), the following applies: - The AMF selects a local AUSF as described in clause 5.30.2.10.2.6 and performs primary authentication towards the local AUSF using Default UE credentials for primary authentication as described in TS 33.501[ Security architecture and procedures for 5G System ] [29]. - Upon establishment of the PDU Session used for User Plane Remote Provisioning the ON-SNPN may trigger secondary authentication procedure, as described in clause 4.3.2.3 of TS 23.502[ Procedures for the 5G System (5GS) ] [3], with the DCS or with a DN-AAA server using Default UE credentials for secondary authentication, as described in clause I.9.2.4 of TS 33.501[ Security architecture and procedures for 5G System ] [29]. When secondary authentication is used, the SMF identifies the DCS or the DN-AAA server as defined in clause 4.3.2.3 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. NOTE 6: If the secondary authentication fails, the SMF rejects the PDU Session used for User Plane Remote Provisioning. Based on local policy the AMF can deregister the UE as described in clause 5.30.2.10.2.7. NOTE 7: The DCS and PVS can be owned by an administrative entity that can be different from either the ON-SNPN or SO-SNPN. The ownership of DCS and PVS is outside the scope of 3GPP. 5.30.2.10.2.3 Broadcast system information When the SNPN supports Onboarding of UEs for SNPNs (i.e. the SNPN can be used as ON-SNPN), the NG-RAN node or the Trusted non-3GPP access network providing access to SNPN additionally broadcasts the following information: - An onboarding enabled indication that indicates whether onboarding is currently enabled for the SNPN. For access to SNPN via NG-RAN the onboarding enabled indication is broadcasted per cell e.g. to allow start of the onboarding procedure only in parts of the SNPN. NOTE: Onboarding enabled indication per cell does not affect mobility management functions, i.e. once the UE selects the ON-SNPN as described in clause 5.30.2.10.2.5 and successfully registers within ON-SNPN as described in clause 5.30.2.10.2.6, the UE can move to a cell of the ON-SNPN not indicating onboarding support and continue with the remote provisioning as described in clause 5.30.2.10.4. 5.30.2.10.2.4 UE Configuration Aspects A UE enabled to support UE Onboarding, shall be pre-configured with Default UE credentials, and the UE may be pre-configured with ON-SNPN selection information. The Default UE credentials consist of credentials for primary authentication and optionally credentials for secondary authentication, as described in clause I.9 of TS 33.501[ Security architecture and procedures for 5G System ] [29]. NOTE 1: The content of the ON-SNPN network selection information depends on UE implementation and can include SNPN network identifiers and/or GIN(s). The UE uses the ON-SNPN selection information for selection of ON-SNPN (see clause 5.30.2.10.2.5). The UE Configuration Data for UP Remote Provisioning is described in the clause 5.30.2.10.4.2. NOTE 2: It is assumed that the UE is not pre-configured with a S-NSSAI and DNN for the purpose of UE onboarding in the ON-SNPN. NOTE 3: The Default UE credentials for primary authentication are used to derive a SUPI. When the UE derives the SUPI from the Default UE credentials for primary authentication, the UE performs specific onboarding procedure as described in clauses 5.30.2.10.2.5, 5.30.2.10.2.6 and 5.30.2.10.2.7. 5.30.2.10.2.5 Network selection This clause applies only when the UE is in SNPN access mode. When the UE wants to perform UE onboarding via an SNPN, the UE shall perform ON-SNPN selection as described below. An ON-SNPN is an SNPN providing onboarding access and enabling remote provisioning for a UE registered for onboarding as specified in clause 4.2.2.2.4 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. NOTE: The trigger for the UE to initiate the UE Onboarding procedure is UE implementation dependent (e.g. the trigger can be a power-on event in the UE, or an input by the user). For automatic or manual selection, the UE may select and attempt to register to an ON-SNPN which broadcast the Onboarding enabled indication described in clause 5.30.2.10.2.3 and matches the pre-configured ON-SNPN selection information such as SNPN network identifier and/or GIN(s) (if available) described in clause 5.30.2.10.2.4 according to the UE implementation-specific logic. If the registration fails, the UE may select and attempt to register to a different ON-SNPN as defined in clause 4.9.3.1.3 or clause 4.9.3.1.4 of TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [17]. 5.30.2.10.2.6 Registration for UE onboarding When the user or UE has selected an ON-SNPN according to clause 5.30.2.10.2.5, the UE establishes an RRC connection towards the NG-RAN node of the ON-SNPN. The UE provides an indication in RRC Connection Establishment that the RRC connection is for onboarding as defined in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [28]. This indication allows the NG-RAN node to select an appropriate AMF that supports the UE onboarding procedures. The UE indicates the ON-SNPN as the selected network, and the NG-RAN node shall indicate the selected PLMN ID and NID of the ON-SNPN to the AMF. NOTE 1: As the configuration information in the UE does not include any S-NSSAI and DNN used for onboarding, the UE does not include S-NSSAI and DNN in RRC when it registers for UE onboarding purposes to the ONN. The UE shall initiate the NAS registration procedure by sending a NAS Registration Request message with the following characteristics: - The UE shall set the 5GS Registration Type to the value "SNPN Onboarding" indicating that the registration request is for onboarding. - The UE shall provide a SUCI derived from a SUPI as specified in TS 23.003[ Numbering, addressing and identification ] [19] and TS 33.501[ Security architecture and procedures for 5G System ] [29]. The SUPI shall uniquely identify the UE and shall be derived from the Default UE credentials for primary authentication. The SUPI used for onboarding may contain an IMSI or a network-specific identifier. The ON-SNPN may determine the corresponding DCS identity or address/domain, based on the SUCI (i.e. based on the Home Network Identifier of the SUCI). The UE does not include a Requested NSSAI in NAS signalling when it registers for UE onboarding purposes to the ON-SNPN. The AMF supporting UE onboarding is configured with AMF Onboarding Configuration Data that includes e.g.: - S-NSSAI and DNN to be used for onboarding or a configured SMF for the S-NSSAI and DNN used for onboarding. - Information to use a local AUSF(s) within the ON-SNPN for onboarding of UEs with a SUCI for a DCS with AAA Server or for onboarding of UEs in the case where the DCS is not involved during primary authentication. NOTE 2: The S-NSSAI used for onboarding is assumed to be configured in both the AMF (i.e. in the AMF Onboarding Configuration Data) and the NG-RAN nodes for the corresponding Tracking Areas where onboarding is enabled. When the AMF receives a NAS Registration Request with a 5GS Registration Type set to "SNPN Onboarding", the AMF: - starts an authentication procedure towards the AUSF, the authentication procedure is specified in TS 33.501[ Security architecture and procedures for 5G System ] [29]. The AMF may be provided with PVS IP address(es) or PVS FQDN(s) from the DCS during authentication procedure. The AMF selects an appropriate AUSF as described in clause 6.3.4 based on the Home Network Identifier of the SUCI used during onboarding or based on local configuration in the AMF. - applies the AMF Onboarding Configuration Data e.g. used to restrict UE network usage to only onboarding for User Plane Remote Provisioning of UE as described in clause 5.30.2.10.4.3. - stores in the UE context in AMF an indication that the UE is registered for SNPN onboarding. - shall handle the list of equivalent SNPNs as described in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [47]. Upon successful authentication from AUSF, the AMF informs the UE about the result of the registration. If the UE is not successfully authenticated, the AMF shall reject the registration procedure for onboarding, and the UE may select a different ON-SNPN to attempt to register. NOTE 3: The AMF does not interact with the UDM of the ON-SNPN or DCS (i.e. for registration or subscription management purposes) when it receives a NAS Registration Request with a 5GS Registration Type set to "SNPN Onboarding" (see clause 4.2.2.2.4 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]). 5.30.2.10.2.7 Deregistration from the ON-SNPN for onboarding registered UE Once remote provisioning of SO-SNPN credentials is completed, the UE should initiate deregistration from the ON-SNPN. Based on ON-SNPN policies, the AMF may start an implementation specific timer once the UE has registered to the ON-SNPN for the purpose of onboarding. Expiry of this timer triggers the AMF to deregister the onboarding registered UE from the ON-SNPN. The AMF may also deregister the UE when it determines that the PDU Session used for User Plane Remote Provisioning has been released by the SMF. When AMF re-allocation occurs for a UE registered for SNPN onboarding during mobility registration update procedure as described in TS 23.502[ Procedures for the 5G System (5GS) ] [3] in clause 4.2.2.2.4 or during N2 based handover as described in TS 23.502[ Procedures for the 5G System (5GS) ] [3] clause 4.9.1.3, the new AMF supporting SNPN Onboarding should be selected as described in clause 6.3.5. If the new AMF receives in UE context the indication that the UE is registered for SNPN onboarding, the new AMF may start an implementation specific timer for when to deregister the UE when the new AMF completes the Registration procedure (i.e. sends Registration Accept to the UE) or completes the N2 based handover procedure. NOTE: This specific timer is used to prevent onboarding registered UEs from staying at the ON-SNPN indefinitely. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.30.2.10.2 |
4,773 | 5.8.10.2.2 Sidelink measurement identity removal | The UE shall: 1> for each sl-MeasId included in the received sl-MeasIdToRemoveList that is part of the current UE configuration in VarMeasConfigSL: 2> remove the entry with the matching sl-MeasId from the sl-MeasIdList within the VarMeasConfigSL; 2> remove the NR sidelink measurement reporting entry for this sl-MeasId from the VarMeasReportListSL, if included; 2> stop the periodical reporting timer and reset the associated information (e.g. sl-TimeToTrigger) for this sl-MeasId. NOTE: The UE does not consider the message as erroneous if the sl-MeasIdToRemoveList includes any sl-MeasId value that is not part of the current UE configuration. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.8.10.2.2 |
4,774 | 5.2 Maintenance of Uplink Time Alignment | The MAC entity has a configurable timer timeAlignmentTimer per TAG. The timeAlignmentTimer is used to control how long the MAC entity considers the Serving Cells belonging to the associated TAG to be uplink time aligned, as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8]. The MAC entity shall: - when a Timing Advance Command MAC control element is received and if a NTA has been stored or maintained with the indicated TAG: - except when the received Timing Advance Command MAC control element is addressed with a PUR-RNTI: - apply the Timing Advance Command for the indicated TAG; - start or restart the timeAlignmentTimer associated with the indicated TAG. - when a Timing Advance Command is received in a Random Access Response message for a serving cell belonging to a TAG: - if the UE is configured with pur-Config (see TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8]) and if a NTA has been stored or maintained and no temporary NTA has been stored: - store current NTA as temporary NTA (see clause 5.4.7.2). - if the Random Access Preamble was not selected by the MAC entity: - apply the Timing Advance Command for this TAG; - start or restart the timeAlignmentTimer associated with this TAG. - else, if the timeAlignmentTimer associated with this TAG is not running: - apply the Timing Advance Command for this TAG; - start the timeAlignmentTimer associated with this TAG; - when the contention resolution is considered not successful as described in clause 5.1.5, stop timeAlignmentTimer associated with this TAG. - else: - ignore the received Timing Advance Command. - when the MAC entity is configured with rach-Skip or rach-SkipSCG: - apply timing advance value indicated by targetTA in rach-Skip or rach-SkipSCG for the pTAG; - start the timeAlignmentTimer associated with this TAG. - when a timeAlignmentTimer expires: - if the timeAlignmentTimer is associated with the pTAG: - flush all HARQ buffers for all serving cells; - notify RRC to release PUCCH/SPUCCH for all serving cells; - notify RRC to release SRS for all serving cells; - for NB-IoT, notify RRC to release all dedicated resources for SR; - clear any configured downlink assignments and uplink grants; - consider all running timeAlignmentTimers as expired; - else if the timeAlignmentTimer is associated with an sTAG, then for all Serving Cells belonging to this TAG: - flush all HARQ buffers; - notify RRC to release SRS; - notify RRC to release PUCCH/SPUCCH, if configured; - clear any configured downlink assignments and uplink grants. - upon indication from upper layers to start timeAlignmentTimer, if a NTA has been stored or maintained with the indicated TAG: - start or restart the timeAlignmentTimer associated with the indicated TAG. When the MAC entity stops uplink transmissions for an SCell due to the fact that the maximum uplink transmission timing difference (as described in clause 7.9.2 of TS 36.133[ Evolved Universal Terrestrial Radio Access (E-UTRA); Requirements for support of radio resource management ] [9]) or the maximum uplink transmission timing difference the UE can handle between TAGs of any MAC entity of the UE is exceeded, the MAC entity considers the timeAlignmentTimer associated with the SCell as expired. The MAC entity shall not perform any uplink transmission on a Serving Cell, except the Random Access Preamble transmission and transmissions corresponding to a PUR-RNTI, when the timeAlignmentTimer associated with the TAG to which this Serving Cell belongs is not running. Furthermore, when the timeAlignmentTimer associated with the pTAG is not running, the MAC entity shall not perform any uplink transmission on any Serving Cell except the Random Access Preamble transmission on the SpCell. The MAC entity shall not perform any sidelink transmission which is performed based on UL timing of the corresponding serving cell and any associated SCI transmissions when the corresponding timeAlignmentTimer is not running. NOTE: A MAC entity stores or maintains NTA upon expiry of associated timeAlignmentTimer, where NTA is defined in TS 36.211[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation ] [7]. The MAC entity applies a received Timing Advance Command MAC control element and starts associated timeAlignmentTimer also when the timeAlignmentTimer is not running. | 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.2 |
4,775 | 16.3.3a Slice-based cell reselection | Slice-based cell reselection information can be included in SIB16 and in RRCRelease messages. The slice-based cell reselection information may include reselection priorities per NSAG per frequency and corresponding list(s) of cells where the slices of the NSAG are supported or not supported. The UE determines the NSAG(s) and their priorities to be considered during cell reselection as specified in TS 23.501[ System architecture for the 5G System (5GS) ] [3], and in TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [10]. When a UE supports slice-based cell reselection, and when slice-based cell reselection information is provided to the UE, then the UE uses the slice-based cell reselection information. Valid cell reselection information provided in RRCRelease always has a priority over cell reselection information provided in SIB messages. When no slice-based cell reselection information is provided for any NSAG that was determined to be considered during cell reselection (as specified in TS 23.501[ System architecture for the 5G System (5GS) ] [3]), then the UE uses the general cell reselection information, i.e., without considering the NSAG(s) and their priorities. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.3.3a |
4,776 | 4.2.2.9 Number of Normally Released Calls (QCI1 E-RAB) initiated by MME in RLF Detected Conditions | a) This measurement provides the number of the normally released calls (QCI1 E-RAB) initiated by MME in RLF detected conditions. b) CC c)) The measurement is triggered on reception of E-RAB Release Command for QCI1 with “Cause” equal to “Normal Release” from MME in case RLF was detected (identified via running RLF timer) on eNB side for the QCI1 E-RAB within the last predefined time interval (e.g. 1 second). d)) Each measurement is an integer value. e)) The measurement name has the form QCI1ERAB.NormalCallRLF. 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.2.2.9 |
4,777 | 6.2.5 Configured transmitted power | The UE is allowed to set its configured maximum output power PCMAX,c for serving cell c. The configured maximum output power PCMAX,c is set within the following bounds: PCMAX_L,c ≤ PCMAX,c ≤ PCMAX_H,c with PCMAX_L,c = MIN {PEMAX,c – TC,c, (PPowerClass – ΔPPowerClass) – MAX(MPRc + A-MPRc + ΔTIB,c + TC,c + TProSe, P-MPRc)} PCMAX_H,c = MIN {PEMAX,c, PPowerClass – ΔPPowerClass} where - PEMAX,c is the value given by IE P-Max for serving cell c, defined in [7]; - PPowerClass is the maximum UE power specified in Table 6.2.2-1 without taking into account the tolerance specified in the Table 6.2.2-1; - ΔPPowerClass = 3 dB for a power class 2 capable UE operating in Band 41, when P-max of 23 dBm or lower is indicated or if the uplink/downlink configuration is 0 or 6 in the cell; otherwise, ΔPPowerClass = 0 dB - ΔPPowerClass = PPowerClass – PPowerClass_Default dB for UE operating in Band 14, when P-max of 23 dBm or lower is indicated in the cell; otherwise, ΔPPowerClass = 0 dB. - MPRc and A-MPRc for serving cell c are specified in subclause 6.2.3 and subclause 6.2.4, respectively; - TIB,c is the additional tolerance for serving cell c as specified in Table 6.2.5-2; TIB,c = 0 dB otherwise; - TC,c = 1.5 dB when NOTE 2 in Table 6.2.2-1 applies; - TC,c = 0 dB when NOTE 2 in Table 6.2.2-1 does not apply; - TProSe = 0.1 dB when the UE supports ProSe Direct Discovery and/or ProSe Direct Communication on the corresponding E-UTRA ProSe band; TProSe = 0 dB otherwise. - For a power class higher than default UE power class capable UE except for operating in Band 14 and Band 41, ΔPPowerClass = PPowerClass – PPowerClass_Default dB, when the band is a TDD band whose frame configuration is 0 or 6; or P-max is not indicated in the cell; or P-Max is provided and set to the maximum output power of the default power class or lower, otherwise, ΔPPowerClass = 0 dB. P-MPRc is the allowed maximum output power reduction for a) ensuring compliance with applicable electromagnetic energy absorption requirements and addressing unwanted emissions / self desense requirements in case of simultaneous transmissions on multiple RAT(s) for scenarios not in scope of 3GPP RAN specifications; b) ensuring compliance with applicable electromagnetic energy absorption requirements in case of proximity detection is used to address such requirements that require a lower maximum output power. The UE shall apply P-MPR c for serving cell c only for the above cases. For UE conducted conformance testing P-MPR shall be 0 dB NOTE 1: P-MPRc was introduced in the PCMAX,c equation such that the UE can report to the eNB the available maximum output transmit power. This information can be used by the eNB for scheduling decisions. NOTE 2: P-MPRc may impact the maximum uplink performance for the selected UL transmission path. TREF and Teval are specified in Table 6.2.5-0 for different TTI patterns. For each TREF, the PCMAX_L,c for serving cell c is evaluated perTeval and given by the minimum value taken over the transmission(s) within the Teval; the minimum PCMAX_ L,c over the one or more Teval is then applied for the entire TREF. PPowerClass shall not be exceeded by the UE during any period of time. Table 6.2.5-0: PCMAX evaluation window for different TTI patterns The measured configured maximum output power PUMAX,c shall be within the following bounds: PCMAX_L,c – MAX{TL,c, T(PCMAX_L,c)} ≤ PUMAX,c ≤ PCMAX_H,c + T(PCMAX_H,c). where the tolerance T(PCMAX,c) for applicable values of PCMAX,c is specified in Table 6.2.5-1, and Table 6.2.5-1A. The tolerance TL,c is the absolute value of the lower tolerance for the applicable operating band as specified in Table 6.2.2-1. Table 6.2.5-1: PCMAX tolerance Table 6.2.5-1A: PCMAX tolerance for power class 5 Table 6.2.5-1B: PCMAX tolerance for power class 6 for category M1 and M2 UE For the UE which supports inter-band carrier aggregation configurations with the uplink assigned to one or two E-UTRA bands the ΔTIB,c is defined for applicable bands in Table 6.2.5-2, Table 6.2.5-3 and Table 6.2.5-4 where unless otherwise stated, the same ΔTIB,c is applicable to E-UTRA band(s) part for CA configurations which have the same E-UTRA operating band combination. Table 6.2.5-2: ΔTIB,c (two bands) NOTE: The above additional tolerances do not apply to supported UTRA operating bands with frequency range below 1 GHz that correspond to the E-UTRA operating bands that belong to the supported inter-band carrier aggregation configurations when such bands are belonging only to band combination(s) where one band is <1GHz and another band is >1.7GHz and there is no harmonic relationship between the low band UL and high band DL. Otherwise the above additional tolerances also apply to supported UTRA operating bands that correspond to the E-UTRA operating bands that belong to the supported inter-band carrier aggregation configurations. NOTE: To meet the TIB,c requirements for CA_3A-7A with state-of-the-art technology, an increase in power consumption of the UE may be required. It is also expected that as the state-of-the-art technology evolves in the future, this possible power consumption increase can be reduced or eliminated. Table 6.2.5-3: ΔTIB,c (three bands) Table 6.2.5-4: ΔTIB,c (four bands) Table 6.2.5-5: ΔTIB,c (five bands) NOTE: The above additional tolerances do not apply to supported UTRA operating bands with frequency range below 1 GHz that correspond to the E-UTRA operating bands that belong to the supported inter-band carrier aggregation configurations when such bands are belonging only to band combination(s) where one band is <1GHz and other bands are >1.7GHz and there is no harmonic relationship between the low band UL and high band DL. Otherwise the above additional tolerances also apply to supported UTRA operating bands that correspond to the E-UTRA operating bands that belong to the supported inter-band carrier aggregation configurations. Table 6.2.5-6: ΔTIB,c (six bands) | 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.5 |
4,778 | 6.6.2.2A.1 Minimum requirement (network signalled value "CA_NS_04") | Additional spectrum emission requirements are signalled by the network to indicate that the UE shall meet an additional requirement for a specific deployment scenario as part of the cell handover/broadcast message. When "CA_NS_04" is indicated in the cell, the power of any UE emission shall not exceed the levels specified in Table 6.6.2.2A.1-1. Table 6.6.2.2A.1-1: Additional requirements NOTE: As a general rule, the resolution bandwidth of the measuring equipment should be equal to the measurement bandwidth. However, to improve measurement accuracy, sensitivity and efficiency, the resolution bandwidth may be smaller than the measurement bandwidth. When the resolution bandwidth is smaller than the measurement bandwidth, the result should be integrated over the measurement bandwidth in order to obtain the equivalent noise bandwidth of the measurement bandwidth. | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.6.2.2A.1 |
4,779 | 4.4.3.1 N4 Association Setup Procedure | The N4 Association Setup procedure is used to setup an N4 association between the SMF and the UPF, to enable the SMF to use the resources of the UPF subsequently to establish N4 Sessions. The SMF and UPF may exchange the supported functionalities on each side during these procedures. The setup of an N4 association is initiated by the SMF. SMF and UPF may additionally support an N4 association initiated by UPF. The SMF should only establish an N4 association with a UPF that supports F-TEID allocation at the UPF. The SMF initiates the N4 Association Setup procedure to request to setup an N4 association towards a UPF prior to establishing a first N4 session on this UPF. When receiving an N4 Association Setup Request, the UPF shall send an N4 Association Setup Response. N4 Association Setup procedure can be used to request the UPF to measure and report the clock drift between the external time and 5GS time for one or more external time domains by provisioning External Clock Drift Report and providing the corresponding Time Domain number(s) as specified in TS 29.244[ Interface between the Control Plane and the User Plane nodes ] [69]. The SMF may omit the Time domain number in the request; in this case the UPF shall report the clock drift for all Time domains the UPF is connected to. Figure 4.4.3.1-1: N4 association setup procedure initiated by SMF The UPF may initiate the N4 Association Setup procedure to request to setup an N4 association towards a SMF prior to establishing a first N4 session on this UPF. When receiving an N4 Association Setup Request, the SMF shall send an N4 Association Setup Response. Figure 4.4.3.1-2: N4 association setup procedure initiated by UPF | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.4.3.1 |
4,780 | 9.5 Interfaces based on DIAMETER or GTP | This clause applies to all DIAMETER or GTP-based interfaces between the 5G Core and other network entities that are not part of the 5G System. These includes the Rx interface between the PCF and the IMS System and the N26 interface between the AMF and the MME. The protection of these interfaces shall be supported according to NDS/IP as specified in TS 33.210[ Network Domain Security (NDS); IP network layer security ] [3], unless security is provided by other means, e.g. physical security. If (D)TLS is used, implementation and usage shall follow the profile given in clause 6.2 of TS 33.210[ Network Domain Security (NDS); IP network layer security ] [3] and clause 6.1.3a of TS 33.310[ Network Domain Security (NDS); Authentication Framework (AF) ] [5]. The cipher suites in RFC 6733 shall not be supported. A SEG may be used to terminate the NDS/IP IPsec tunnels. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 9.5 |
4,781 | 9.9.3.59 UE radio capability ID request | The purpose of the UE radio capability ID request information element is to indicate that the UE radio capability ID shall be included by the UE in the SECURITY MODE COMPLETE message. The UE radio capability ID request is a type 4 information element with a length of 3 octets. The UE radio capability ID request information element is coded as shown in figure 9.9.3.59.1 and table 9.9.3.59.1. Figure 9.9.3.59.1: UE radio capability ID request information element Table 9.9.3.59.1: UE radio capability ID request information element | 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.9.3.59 |
4,782 | 20.5 SGmb re-used AVPs | Table 20.5.1 lists the Diameter AVPs re-used by the SGmb reference point from the Gmb reference point and other existing Diameter Application, reference to their respective specifications and short description of their usage witin the SGmb reference point. When reused from Gmb reference point, the specific clause in the present specification is referred. Other AVPs from existing Diameter Applications, except for the AVPs from Diameter base protocol, do not need to be supported. The AVPs from Diameter base protocol are not included in table 20.5.1, but they are re-used for the SGmb reference point. Where RADIUS VSAs are re-used, they shall be translated to Diameter AVPs as described in RFC 7155 [120] with the exception that the ‘M’ flag shall be set and the ‘P’ flag may be set. Table 20.5.1 : SGmb re-used Diameter AVPs | 3GPP TS 29.061 | Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) | CT WG3 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 20.5 |
4,783 | – DMRS-DownlinkConfig | The IE DMRS-DownlinkConfig is used to configure downlink demodulation reference signals for PDSCH. DMRS-DownlinkConfig information element -- ASN1START -- TAG-DMRS-DOWNLINKCONFIG-START DMRS-DownlinkConfig ::= SEQUENCE { dmrs-Type ENUMERATED {type2} OPTIONAL, -- Need S dmrs-AdditionalPosition ENUMERATED {pos0, pos1, pos3} OPTIONAL, -- Need S maxLength ENUMERATED {len2} OPTIONAL, -- Need S scramblingID0 INTEGER (0..65535) OPTIONAL, -- Need S scramblingID1 INTEGER (0..65535) OPTIONAL, -- Need S phaseTrackingRS SetupRelease { PTRS-DownlinkConfig } OPTIONAL, -- Need M ..., [[ dmrs-Downlink-r16 ENUMERATED {enabled} OPTIONAL -- Need R ]], [[ dmrs-TypeEnh-r18 ENUMERATED {enabled} OPTIONAL -- Need R ]] } -- TAG-DMRS-DOWNLINKCONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
4,784 | 4.3.2.4 Ciphering key sequence number | The security parameters for authentication and ciphering are tied together in sets. In a GSM authentication challenge, from a challenge parameter RAND both the authentication response parameter SRES and the GSM ciphering key can be computed given the secret key associated to the IMSI. In a UMTS authentication challenge, from a challenge parameter RAND, the authentication response parameter RES and the UMTS ciphering key and the UMTS integrity key can be computed given the secret key associated to the IMSI. In addition, in the USIM a GSM ciphering key can be computed from the UMTS ciphering key and the UMTS integrity key by means of an unkeyed conversion function. Furthermore, in A/Gb mode if an A5 ciphering algorithm that requires a 128-bit ciphering key is taken into use, then a GSM Kc128 shall also be calculated as described in the subclause 4.3.2.3a. In order to allow start of ciphering on a RR connection without authentication, the ciphering key sequence numbers are introduced. The ciphering key sequence number is managed by the network in the way that the AUTHENTICATION REQUEST message contains the ciphering key sequence number allocated to the GSM ciphering key (in case of a GSM authentication challenge) or the UMTS ciphering key and the UMTS integrity key (in case of a UMTS authentication challenge) which may be computed from the RAND parameter carried in that message. If an authentication procedure has been completed successfully and a ciphering key sequence number is stored in the network, the network shall include a different ciphering key sequence number in the AUTHENTICATION REQUEST message when it intiates a new authentication procedure. The mobile station stores the ciphering key sequence number with the GSM ciphering key (in case of a GSM authentication challenge) and the UMTS ciphering key and the UMTS integrity key (in case of a UMTS authentication challenge) and indicates to the network in the first message (LOCATION UPDATING REQUEST, CM SERVICE REQUEST, PAGING RESPONSE, CM RE-ESTABLISHMENT REQUEST) which ciphering key sequence number the stored GSM ciphering key (in case of a GSM authentication challenge) or set of UMTS ciphering, UMTS integrity, derived GSM ciphering key, and potentially the derived GSM Kc128 (in case of a UMTS authentication challenge) has. When the deletion of the ciphering key sequence number is described this also means that the associated GSM ciphering key, the UMTS ciphering key and the UMTS integrity key shall be considered as invalid and also the GSM Kc128 shall be deleted if any (i.e. the established GSM security context or the UMTS security context is no longer valid). In A/Gb mode, the network may choose to start ciphering with the stored GSM ciphering key or GSM Kc128 (under the restrictions given in 3GPP TS 42.009[ Security aspects ] [5]) if the stored ciphering key sequence number and the one given from the mobile station are equal. NOTE 1: The decision of starting ciphering with the GSM ciphering key or the GSM Kc128 depends on whether the network indicates in the CIPHERING MODE COMMAND message an A5 ciphering algorithm which requires a 64 or 128-bit ciphering key as specified in 3GPP TS 33.102[ 3G security; Security architecture ] [5a]. In Iu mode, the network may choose to start ciphering and integrity with the stored UMTS ciphering key and UMTS integrity key (under the restrictions given in 3GPP TS 42.009[ Security aspects ] [5] and 3GPP TS 33.102[ 3G security; Security architecture ] [5a]) if the stored ciphering key sequence number and the one given from the mobile station are equal. NOTE 2: In some specifications the term KSI (Key Set Identifier) might be used instead of the term ciphering key sequence number. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.3.2.4 |
4,785 | 8.30 Charging Characteristics | The charging characteristics information element is defined in 3GPP TS 32.251[ Telecommunication management;Charging management;Packet Switched (PS) domain charging ] [8] and is a way of informing both the SGW and PGW of the rules for producing charging information or informing the PGW to inhibit the establishment of the Gx session based on operator configured triggers. For the encoding of this information element see 3GPP TS 32.298[ Telecommunication management; Charging management; Charging Data Record (CDR) parameter description ] [9]. Figure 8.30-1: Charging Characteristics | 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.30 |
4,786 | 9.11.2.11 Service-level device ID | The purpose of the Service-level device ID information element is to carry the necessary identity for authentication and authorization by the external DN. The Service-level device ID information element is coded as shown in figure 9.11.2.11.1 and table 9.11.2.11.1. The Service-level device ID information element is a type 4 information element with minimum length of 3 octets and maximum length of 257 octets. Figure 9.11.2.11.1: Service-level device ID information element Table 9.11.2.11.1: Service-level device ID 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.2.11 |
4,787 | A.7.0 Parameters for the input S to the KDF | When deriving a KAMF from KSEAF the following parameters shall be used to form the input S to the KDF. - FC = 0x6D - P0 = IMSI or NAI or GCI or GLI - L0 = P0 length - number of octets in P0 - P1 = ABBA parameter - L1 = P1 length - number of octets in P1 The input key KEY shall be the 256-bit KSEAF. For P0, when the SUPI type is IMSI, P0 shall be set to IMSI as defined in clause 2.2 of TS 23.003[ Numbering, addressing and identification ] [19]. For P0, when the SUPI type is network specific identifier, the P0 shall be set to Network Access Identifier (NAI) as defined in clause 28.7.2 of TS 23.003[ Numbering, addressing and identification ] [19]. When the SUPI type is GLI, P0 shall be set to GLI taking format of NAI as defined in clause 28.16.2 of TS 23.003[ Numbering, addressing and identification ] [19]. When the SUPI type is GCI, P0 shall be set to GCI taking format of NAI as defined in clause 28.15.2 of TS 23.003[ Numbering, addressing and identification ] [19]. P0 shall be represented as a character string as specified in B.2.1.2 of TS 33.220[ Generic Authentication Architecture (GAA); Generic Bootstrapping Architecture (GBA) ] [28], for both SUPI types. For ABBA parameter values please refer to clause A.7.1. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | A.7.0 |
4,788 | 11.2.1.3.5 IPv6 Prefix Delegation via DHCPv6 | Optionally, a single network prefix shorter than the default /64 prefix may be assigned to a PDN connection. In this case, the /64 default prefix used for IPv6 stateless autoconfiguration will be allocated from this network prefix; the remaining address space from the network prefix can be delegated to the PDN connection using prefix delegation after the PDP context activation/default bearer establishment and IPv6 prefix allocation via IPv6 stateless address autoconfiguration as defined in clause 11.2.1.3.2/11.2.1.3.2a. When PLMN based parameter configuration is used, the GGSN / PDN GW provides the requested IPv6 prefix from a locally provisioned pool. When external PDN based IPv6 prefix allocation is used, the GGSN / PDN GW may obtain the prefix from the external PDN as per subclauses 16.4 and 16a.4. For the detailed description of the UE uses DHCPv6 to request additional IPv6 prefixes refer to 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [3] and 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [77]. | 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 | 11.2.1.3.5 |
4,789 | 5.32.6 Support of Steering Functionalities 5.32.6.1 General | The functionality in an ATSSS-capable UE that can steer, switch and split the MA PDU Session traffic across 3GPP access and non-3GPP access, is called a "steering functionality". An ATSSS-capable UE may support one or more of the following types of steering functionalities: - High-layer steering functionalities, which operate above the IP layer: - In this release of the specification, two high-layer steering functionalities are vspecified: - The first applies the MPTCP protocol (IETF RFC 8684 [81]) and is called "MPTCP functionality" (see clause 5.32.6.2.1). This steering functionality can be applied to steer, switch and split the TCP traffic flows identified in the ATSSS/N4 rules. The MPTCP functionality in the UE may communicate with an associated MPTCP Proxy functionality in the UPF, by using the MPTCP protocol over the 3GPP and/or the non-3GPP user plane. - The second applies the QUIC protocol (RFC 9000 [166], RFC 9001 [167], RFC 9002 [168]) and its multipath extensions (draft-ietf-quic-multipath [174]), and it is called "MPQUIC functionality" (see clause 5.32.6.2.2). This steering functionality can be applied to steer, switch and split the UDP traffic flows identified in the ATSSS/N4 rules. The MPQUIC functionality in the UE may communicate with an associated MPQUIC Proxy functionality in the UPF, by using the QUIC protocol and its multipath extensions over the 3GPP and/or the non-3GPP user plane. - Low-layer steering functionalities, which operate below the IP layer: - One type of low-layer steering functionality defined in the present document is called "ATSSS Low-Layer functionality", or ATSSS-LL functionality (see clause 5.32.6.3.1). This steering functionality can be applied to steer, switch and split all types of traffic, including TCP traffic, UDP traffic, Ethernet traffic, etc. ATSSS-LL functionality is mandatory for MA PDU Session of type Ethernet. In the network, there shall be in the data path of the MA PDU session one UPF supporting ATSSS-LL. NOTE: Filters used in ATSSS rules related with a MA PDU Session of type Ethernet can refer to IP level parameters such as IP addresses and TCP/UDP ports. The UE indicates to the network its supported steering functionalities and steering modes by including in the UE ATSSS Capability one of the following: 1) ATSSS-LL functionality with any steering mode. In this case, the UE indicates that it is capable to steer, switch and split all traffic of the MA PDU Session by using the ATSSS-LL functionality with any steering mode allowed for ATSSS-LL, as specified in clause 5.32.8. 2) MPTCP functionality with any steering mode and ATSSS-LL functionality with only Active-Standby steering mode. In this case, the UE indicates that: a) it is capable to steer, switch and split the MPTCP traffic of the MA PDU Session by using the MPTCP functionality with any steering mode specified in clause 5.32.8; and b) it is capable to steer and switch all other traffic (i.e. the non-MPTCP traffic) of the MA PDU Session by using the ATSSS-LL functionality with the Active-Standby steering mode specified in clause 5.32.8. 3) MPTCP functionality with any steering mode and ATSSS-LL functionality with any steering mode. In this case, the UE indicates that: a) it is capable to steer, switch and split the MPTCP traffic of the MA PDU Session by using the MPTCP functionality with any steering mode specified in clause 5.32.8; and b) it is capable to steer, switch and split all other traffic (i.e. the non-MPTCP traffic) of the MA PDU Session by using the ATSSS-LL functionality with any steering mode, as specified in clause 5.32.8. 4) MPQUIC functionality with any steering mode and ATSSS-LL functionality with only Active-Standby steering mode. In this case, the UE indicates that: a) it is capable to steer, switch and split the MPQUIC traffic of the MA PDU Session by using the MPQUIC functionality with any steering mode specified in clause 5.32.8; and b) it is capable to steer and switch all other traffic (i.e. the non-MPQUIC traffic) of the MA PDU Session by using the ATSSS-LL functionality with the Active-Standby steering mode specified in clause 5.32.8. 5) MPQUIC functionality with any steering mode and ATSSS-LL functionality with any steering mode. In this case, the UE indicates that: a) it is capable to steer, switch and split the MPQUIC traffic of the MA PDU Session by using the MPQUIC functionality with any steering mode specified in clause 5.32.8; and b) it is capable to steer, switch and split all other traffic (i.e. the non-MPQUIC traffic) of the MA PDU Session by using the ATSSS-LL functionality with any steering mode that can be used with ATSSS-LL, as specified in clause 5.32.8. 6) MPTCP functionality with any steering mode, MPQUIC functionality with any steering mode, and ATSSS-LL functionality with only Active-Standby steering mode. In this case, the UE indicates that: a) it is capable to steer, switch and split the MPTCP traffic of the MA PDU Session by using the MPTCP functionality with any steering mode specified in clause 5.32.8; b) it is capable to steer, switch and split the MPQUIC traffic of the MA PDU Session by using the MPQUIC functionality with any steering mode specified in clause 5.32.8; and c) it is capable to steer and switch all other traffic (i.e. the non-MPTCP traffic and the non-MPQUIC traffic) of the MA PDU Session by using the ATSSS-LL functionality with the Active-Standby steering mode specified in clause 5.32.8. 7) MPTCP functionality with any steering mode, MPQUIC functionality with any steering mode, and ATSSS-LL functionality with any steering mode. In this case, the UE indicates that: a) it is capable to steer, switch and split the MPTCP traffic of the MA PDU Session by using the MPTCP functionality with any steering mode specified in clause 5.32.8; b) it is capable to steer, switch and split the MPQUIC traffic of the MA PDU Session by using the MPQUIC functionality with any steering mode specified in clause 5.32.8; and c) it is capable to steer, switch and split all other traffic (i.e. the non-MPTCP traffic and the non-MPQUIC traffic) of the MA PDU Session by using the ATSSS-LL functionality with any steering mode that can be used with ATSSS-LL, as specified in clause 5.32.8. The above steering functionalities are schematically illustrated in the Figure 5.32.6.1-1, which shows an example model for an ATSSS-capable UE supporting the MPTCP functionality, the MPQUIC functionality and the ATSSS-LL functionality. The MPTCP flows and the MPQUIC flows in this figure represent the traffic of the applications for which MPTCP can be applied and for which MPQUIC can be applied respectively. The five different IP addresses illustrated in the UE are further described in clause 5.32.6.2.1 and in clause 5.32.6.2.2. When the MPTCP functionality and the MPQUIC functionality are both applied, the addresses (IP@1, IP@2) used for MPTCP may be the same as the addresses (IP@4, IP@5) used for MPQUIC. The "Low-Layer" in this figure contains functionality that operates below the IP layer (e.g. different network interfaces in the UE), while the "High-Layer" contains functionality that operates above the IP layer. Figure 5.32.6.1-1: Steering functionalities in an example UE model Within the same MA PDU Session in the UE, it is possible to steer the MPTCP flows by using the MPTCP functionality, to steer the MPQUIC flows by using the MPQUIC functionality and, simultaneously, to steer all other flows by using the ATSSS-LL functionality. For the same packet flow, only one steering functionality shall be used. All steering functionalities in the UE shall take ATSSS decisions (i.e. decide how to steer, switch and split the traffic) by using the same set of ATSSS rules. Similarly, all ATSSS decisions in the UPF shall be taken by applying the same set of N4 rules, which support ATSSS. The ATSSS rules and the N4 rules supporting ATSSS are provisioned in the UE and in the UPF respectively, when the MA PDU Session is established. If the UE supports multiple steering functionalities, e.g. both the MPTCP functionality and the ATSSS-LL functionality, or the MPTCP functionality, the MPQUIC functionality and the ATSSS-LL functionality, it shall use the provisioned ATSSS rules (see TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]) to decide which steering functionality to apply for a specific packet flow. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.32.6 |
4,790 | 5.15.4.1.1 UE Network Slice configuration | The Network Slice configuration information contains one or more Configured NSSAI(s). A Configured NSSAI may either be configured by a Serving PLMN and apply to the Serving PLMN, or may be a Default Configured NSSAI configured by the HPLMN and that applies to any PLMNs for which no specific Configured NSSAI has been provided to the UE. There is at most one Configured NSSAI per PLMN. NOTE 1: The value(s) used in the Default Configured NSSAI are expected to be commonly decided by all roaming partners, e.g. by the use of values standardized by 3GPP or other bodies. The Default Configured NSSAI, if it is configured in the UE, is used by the UE in a Serving PLMN only if the UE has no Configured NSSAI for the Serving PLMN. The Configured NSSAI of a PLMN may include S-NSSAIs that have standard values or PLMN-specific values. The Configured NSSAI for the Serving PLMN includes the S-NSSAI values which can be used in the Serving PLMN and may be associated with mapping of each S-NSSAI of the Configured NSSAI to one or more corresponding HPLMN S-NSSAI values. In the non-roaming case, the network shall not provide any mapped S-NSSAI to the UE with the Configured NSSAI. In the roaming case, the AMF shall provide to the UE the mapping of each S-NSSAI of the Configured NSSAI for the Serving PLMN to the corresponding S-NSSAI values of the HPLMN when providing NSSAI information, as described in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [47]. A UE subscription may contain Network Slice Simultaneous Registration Group (NSSRG) information. If so, the UE configuration is performed as described in clause 5.15.12.2. The UE may be pre-configured with the Default Configured NSSAI. The UE may be provisioned/updated with the Default Configured NSSAI, determined by the UDM in the HPLMN, using the UE Parameters Update via UDM Control Plane procedure defined in clause 4.20 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. Each S-NSSAI in the Default Configured NSSAI may have a corresponding S-NSSAI as part of the Subscribed S-NSSAI(s). Consequently, if the Subscribed S-NSSAI(s) which are also present in the Default Configured NSSAI are updated the UDM should update the Default Configured NSSAI in the UE. In the HPLMN, the S-NSSAIs in the Configured NSSAI provided as described in clause 5.15.4.2, at the time when they are provided to the UE, shall match the Subscribed S-NSSAIs for the UE. When the Subscribed S-NSSAI(s) are updated (i.e. some existing S-NSSAIs are removed and/or some new S-NSSAIs are added) and one or more are applicable to the Serving PLMN the UE is registered in, as described in clause 5.15.3, or when the associated mapping is updated the AMF shall update the UE with the Configured NSSAI for the Serving PLMN and/or Allowed NSSAI and Partially Allowed NSSAI and/or the associated mapping to HPLMN S-NSSAIs (see clause 5.15.4.2). When there is the need to update the Allowed NSSAI or Partially Allowed NSSAI, the AMF shall provide the UE with the new Allowed NSSAI or Partially Allowed NSSAI and the associated mapping to HPLMN S-NSSAIs, unless the AMF cannot determine the new Allowed NSSAI (e.g. all S-NSSAIs in the old Allowed NSSAI have been removed from the Subscribed S-NSSAIs), in which case the AMF shall not send any Allowed NSSAI to the UE but indicate to the UE to perform a Registration procedure. If the UE is in a CM-IDLE state, the AMF may trigger Network Triggered Service Request or wait until the UE is in a CM-CONNECTED state as described in clause 4.2.4.2, TS 23.502[ Procedures for the 5G System (5GS) ] [3]. When providing a Requested NSSAI to the network upon registration, the UE in a given PLMN only includes and uses S-NSSAIs applying to this PLMN. The mapping of S-NSSAIs of the Requested NSSAI to HPLMN S-NSSAIs may also be provided (see clause 5.15.4.1.2 for when this is needed). The S-NSSAIs in the Requested NSSAI are part of the Configured and/or Allowed NSSAIs applicable for this PLMN, when they are available. If the UE has received NSSRG information together with the Configured NSSAI, it only includes in the Requested NSSAI S-NSSAIs that all share a common NSSRG. If the UE has stored Pending NSSAI and the UE is still interested in the Pending NSSAI then all the S-NSSAIs in the Requested NSSAI and the Pending S-NSSAI shall share a common NSSRG. If no Configured NSSAI and Allowed NSSAI for the PLMN are available, the S-NSSAIs in the Requested NSSAI correspond to the Default Configured NSSAI, if configured in the UE. Upon successful completion of a UE's Registration procedure over an Access Type, the UE obtains from the AMF an Allowed NSSAI or Partially Allowed NSSAI for this Access Type, which includes one or more S-NSSAIs and, if needed (see clause 5.15.4.1.2 for when this is needed), their mapping to the HPLMN S-NSSAIs. These S-NSSAIs are valid for the current Registration Area and Access Type provided by the AMF the UE has registered with and can be used simultaneously by the UE (up to the maximum number of simultaneous Network Slice instances or PDU Sessions). The UE might also obtain from the AMF, one or more rejected S-NSSAIs with cause and validity of rejection. An S-NSSAI may be rejected: - for the entire PLMN; - for the current Registration Area; or - partially in the current Registration Area. Such S-NSSAI rejected partially in the current Registration area is associated with a list of TAs where the S-NSSAI is not supported. The AMF may also reject the use of an S-NSSAI due to congestion as described in clause 5.19.7.4. While the UE remains RM-REGISTERED in the PLMN and regardless of the Access Type, the UE shall not re-attempt to register to an S-NSSAI rejected for the entire PLMN until this rejected S-NSSAI is deleted as specified below. While the UE remains RM-REGISTERED in the PLMN, the UE shall not re-attempt to register to an S-NSSAI rejected in the current Registration Area until it moves out of the current Registration Area. While the UE remains RM-REGISTERED in the PLMN, the UE shall not re-attempt to register to an S-NSSAI rejected partially in the RA until the UE moves into a TA which is not part of the list of TAs associated with the S-NSSAI. NOTE 2: The details and more cases of S-NSSAI rejection are described in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [47]. The S-NSSAIs that the UE provides in the Requested NSSAI which are neither in the Allowed NSSAI nor in the Partially Allowed NSSAI, nor provided as a rejected S-NSSAI, shall, by the UE, not be regarded as rejected, i.e. the UE may request to register these S-NSSAIs again next time the UE sends a Requested NSSAI. The UE stores (S-)NSSAIs as follows: - When provisioned with a Configured NSSAI for a PLMN and/or a mapping of Configured NSSAI to HPLMN S-NSSAIs and possibly NSSRG information for each S-NSSAI in the Configured NSSAI (if applicable and supported by the UE), or when requested to remove the configuration due to network slicing subscription change, the UE shall: - replace any stored (old) Configured NSSAI for this PLMN with the new Configured NSSAI for this PLMN (if applicable); and - delete any stored associated mapping of this old Configured NSSAI for this PLMN to HPLMN S-NSSAIs and, if present and applicable, store the mapping of Configured NSSAI to HPLMN S-NSSAIs; and - delete any stored associated NSSRG information for each S-NSSAI of the Configured NSSAI and, if present, store the associated NSSRG information for each S-NSSAI of the Configured NSSAI; and - delete any stored rejected S-NSSAI for this PLMN; - keep the received Configured NSSAI for a PLMN (if applicable) and associated mapping to HPLMN S-NSSAIs (if applicable) and associated NSSRG information for each S-NSSAI of the Configured NSSAI (if applicable and supported by the UE) stored in the UE, even when registering in another PLMN, until a new Configured NSSAI for this PLMN and/or associated mapping are provisioned in the UE, or until the network slicing subscription changes, as described in clause 5.15.4.2. The number of Configured NSSAIs and associated mapping to be kept stored in the UE for PLMNs other than the HPLMN is up to UE implementation. A UE shall at least be capable of storing a Configured NSSAI for the serving PLMN including any necessary mapping of the Configured NSSAI for the Serving PLMN to HPLMN S-NSSAIs and the Default Configured NSSAI. - The Allowed NSSAI received in a Registration Accept message or a UE Configuration Update Command applies to a PLMN when at least a TAI of this PLMN is included in the RA/TAI list included in this Registration Accept message or UE Configuration Update Command. If the UE Configuration Update Command contains an Allowed NSSAI but not a TAI List, then the last received RA/TAI list applies for the decision on which PLMN(s) the Allowed NSSAI is applicable. If received, the Allowed NSSAI for a PLMN and Access Type and any associated mapping of this Allowed NSSAI to HPLMN S-NSSAIs shall be stored in the UE. The UE should store this Allowed NSSAI and any associated mapping of this Allowed NSSAI to HPLMN S-NSSAIs also when the UE is turned off, or until the network slicing subscription changes, as described in clause 5.15.4.2: NOTE 3: Whether the UE stores the Allowed NSSAI and any associated mapping of the Allowed NSSAI to HPLMN S-NSSAIs also when the UE is turned off is left to UE implementation. - When a new Allowed NSSAI for a PLMN and any associated mapping of the Allowed NSSAI to HPLMN S-NSSAIs are received over an Access Type, the UE shall: - replace any stored (old) Allowed NSSAI and any associated mapping for these PLMN and Access Type with this new Allowed NSSAI; and - delete any stored associated mapping of this old Allowed NSSAI for this PLMN to HPLMN S-NSSAIs and, if present, store the associated mapping of this new Allowed NSSAI to HPLMN S-NSSAIs; - If received, a Partially Allowed NSSAI received in a Registration Accept message or a UE Configuration Update Command message applies to the current Registration Area. The UE stores the Partially Allowed NSSAI in the same way as described for the Allowed NSSAI (see also clause 5.15.17). - If received, an S-NSSAI rejected for the entire PLMN shall be stored in the UE while RM-REGISTERED in this PLMN regardless of the Access Type or until it is deleted. - If received, an S-NSSAI rejected for the current Registration Area shall be stored in the UE while RM-REGISTERED until the UE moves out of the current Registration Area or until the S-NSSAI is deleted. - If received, an S-NSSAI rejected partially in the RA shall be stored in the UE while RM-REGISTERED until the UE moves out of the current Registration Area or until the S-NSSAI is deleted (see also clause 5.15.17). NOTE 4: The storage aspects of rejected S-NSSAIs are described in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [47]. - If received, the Pending NSSAI shall be stored in the UE as described in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [47]. - If received, the S-NSSAI validity time information shall be stored in the UE in the UE as described in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [47]. - If received, the S-NSSAI location availability information shall be stored in the UE as described in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [47]. - If received, the mapping of old S-NSSAI to the Alternative S-NSSAI shall be stored in the UE as described in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [47]. UE configuration to guide UE selection of a N3IWF/TNGF that supports the S-NSSAIs needed by the UE is defined in clause 6.3.6 and clause 6.3.12 respectively. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.15.4.1.1 |
4,791 | – RRCReconfigurationFailureSidelink | The RRCReconfigurationFailureSidelink message is used to indicate the failure of a PC5 RRC AS reconfiguration. It is only applied to unicast of NR sidelink communication. Signalling radio bearer: SL-SRB3 RLC-SAP: AM Logical channel: SCCH Direction: UE to UE RRCReconfigurationFailureSidelink message -- ASN1START -- TAG-RRCRECONFIGURATIONFAILURESIDELINK-START RRCReconfigurationFailureSidelink ::= SEQUENCE { rrc-TransactionIdentifier-r16 RRC-TransactionIdentifier, criticalExtensions CHOICE { rrcReconfigurationFailureSidelink-r16 RRCReconfigurationFailureSidelink-r16-IEs, criticalExtensionsFuture SEQUENCE {} } } RRCReconfigurationFailureSidelink-r16-IEs ::= SEQUENCE { lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL } -- TAG-RRCRECONFIGURATIONFAILURESIDELINK-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
4,792 | 4.2.2.4 Service State, NO IMSI | When in state MM IDLE and service state NO IMSI the mobile station shall (see subclause 3.2, 3GPP TS 43.022[ None ] [82] and 3GPP TS 45.008[ None ] [34]): - not start any normal location updating attempt; - not perform periodic updating; - not perform IMSI detach if powered down; - reject any request from CM entities for MM connections except for emergency calls; - not respond to paging; - only perform default cell selection. In addition, mobile stations supporting VGCS listening or VBS listening shall: - not indicate notifications to the GCC or BCC layer. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.2.2.4 |
4,793 | 4.2.3 Service state when back to state MM IDLE from another state | When returning to MM IDLE, e.g., after a location updating procedure, the mobile station selects the cell as specified in 3GPP TS 43.022[ None ] [82] and 3GPP TS 25.304[ None ] [98]. With one exception, this is a normal cell selection. An eCall only mobile station (as determined by information configured in USIM), shall start timer T3242 if the return to MM IDLE state is the result of an emergency services call and shall start timer T3243 if the return to MM IDLE state is the result of a call to a non-emergency MSISDN for test and terminal reconfiguration services, as described in subclause 4.4.7. If this return to idle state is not subsequent to a location updating procedure terminated with reception of cause "Roaming not allowed in this location area", the service state depends on the result of the cell selection procedure, on the update status of the mobile station, on the location data stored in the mobile station and on the presence of the SIM/USIM: - if no cell has been found, the state is NO CELL AVAILABLE, until a cell is found; - if no SIM/USIM is present, or if the inserted SIM/USIM is considered invalid by the MS, the state is NO IMSI; - for an eCall only mobile station (as determined by information configured in USIM), if timer T3242 or timer T3243 has expired and service state PLMN SEARCH is not required, the state is eCALL INACTIVE and the eCall inactivity procedure is performed as described in subclause 4.4.7; - if the selected cell is in the location area where the MS is registered, then the state is NORMAL SERVICE; it shall be noted that this also includes an abnormal case described in subclause 4.4.4.9; - (Only applicable for mobile stations supporting VGCS listening or VBS listening.) if the mobile stations was in the service state RECEIVING GROUP CALL (NORMAL SERVICE) or RECEIVING GROUP CALL (LIMITED SERVICE) before the location updating procedure and the selected cell is in the location area where the mobile station is registered, then the state is RECEIVING GROUP CALL (NORMAL SERVICE); - if the selected cell is in a location area where the mobile station is not registered but in which the MS is allowed to attempt a location update, then the state is LOCATION UPDATE NEEDED; - if the selected cell is in a location area where the mobile station is not allowed to attempt a location update, then the state is LIMITED SERVICE; - if the selected cell is a CSG cell whose CSG ID and associated PLMN identity are not in the Allowed CSG list or in the Operator CSG list stored in the MS, then the state is LIMITED SERVICE; - (Only applicable for MSs supporting VGCS listening or VBS listening.) if the MSs was in the service state RECEIVING GROUP CALL (NORMAL SERVICE) or RECEIVING GROUP CALL (LIMITED SERVICE) before the location updating procedure and the selected cell is in the location area where the MS is not allowed to attempt a location update, then the state is RECEIVING GROUP CALL (LIMITED SERVICE); - after some abnormal cases occurring during an unsuccessful location updating procedure, as described in subclause 4.4.4.9, the state is ATTEMPTING TO UPDATE. In case of a return from a location updating procedure to which was answered "Roaming not allowed in this location area", the service state PLMN SEARCH is entered as specified in subclause 4.2.1.2. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.2.3 |
4,794 | 4.1.1.9 Equivalent PLMNs list | The mobile equipment shall store a list of "equivalent PLMNs". These PLMNs shall be regarded by the MS as equivalent to each other for PLMN selection and cell selection/re-selection. The same list is used by 5GMM, EMM, GMM and MM (see 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [167] and 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120]). The list of equivalent PLMNs is replaced or deleted at the end of each location updating procedure, routing area updating procedure and GPRS attach procedure. The stored list consists of a list of equivalent PLMNs as downloaded by the network plus the PLMN code of the registered PLMN that downloaded the list. The stored list shall not be deleted when the MS is switched off. The stored list shall be deleted if the SIM/USIM is removed or when an MS attached for emergency bearer services enters the state GMM-DEREGISTERED. The maximum number of possible entries in the stored list is 16. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.1.1.9 |
4,795 | 4.15.3.2.3c Specific NEF service operations information flow for group member list change | The procedure is used by the AF to subscribe to notifications and to explicitly cancel a previous subscription for group member list change. Step 1, step 2, step 4, step 5, step 6a and step 7 of Figure 4.15.3.2.3-1 are performed with the differences that the Event ID is set with "Group Member List Change". When a NF consumer subscribes to the group member list change event, if the request indicates immediate reporting, the group member list is provided in the Nudm/Nnef_EeventEExposure_Subscribe response, When the UDM detects the group member list change event occurs, it sends the event report including the identities of the UE(s) added/removed to/from the group to the NEF by means of Nudm_EventExposure_Notify message and NEF forwards the information to the AF by means of Nnef_EventExposure_Notify message. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.15.3.2.3c |
4,796 | – SIB20 | SIB20 contains the information required to acquire the MCCH/MTCH configuration for MBS broadcast. SIB20 information element -- ASN1START -- TAG-SIB20-START SIB20-r17 ::= SEQUENCE { mcch-Config-r17 MCCH-Config-r17, cfr-ConfigMCCH-MTCH-r17 CFR-ConfigMCCH-MTCH-r17 OPTIONAL, -- Need S lateNonCriticalExtension OCTET STRING OPTIONAL, ..., [[ cfr-ConfigMCCH-MTCH-RedCap-r18 CFR-ConfigMCCH-MTCH-r17 OPTIONAL, -- Need S mcch-ConfigRedCap-r18 MCCH-Config-r17 OPTIONAL -- Cond CFR-RedCap ]] } MCCH-Config-r17 ::= SEQUENCE { mcch-RepetitionPeriodAndOffset-r17 MCCH-RepetitionPeriodAndOffset-r17, mcch-WindowStartSlot-r17 INTEGER (0..79), mcch-WindowDuration-r17 ENUMERATED {sl2, sl4, sl8, sl10, sl20, sl40,sl80, sl160} OPTIONAL, -- Need S mcch-ModificationPeriod-r17 ENUMERATED {rf2, rf4, rf8, rf16, rf32, rf64, rf128, rf256, rf512, rf1024, rf2048, rf4096, rf8192, rf16384, rf32768, rf65536} } MCCH-RepetitionPeriodAndOffset-r17 ::= CHOICE { rf1-r17 INTEGER(0), rf2-r17 INTEGER(0..1), rf4-r17 INTEGER(0..3), rf8-r17 INTEGER(0..7), rf16-r17 INTEGER(0..15), rf32-r17 INTEGER(0..31), rf64-r17 INTEGER(0..63), rf128-r17 INTEGER(0..127), rf256-r17 INTEGER(0..255) } -- TAG-SIB20-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
4,797 | 5.7.1a.3 Actions related to reception of DLInformationTransferMRDC message | Upon receiving the DLInformationTransferMRDC, the UE shall: 1> if the RRCReconfiguration message is included in dl-DCCH-MessageNR: 2> perform the RRC reconfiguration procedure according to 5.3.5.3; 1> else if the RRCRelease message is included in dl-DCCH-MessageNR: 2> perform the RRC release procedure according to 5.3.8; 1> else if the MobilityFromNRCommand message is included in the dl-DCCH-MessageNR: 2> perform the mobility from NR procedure according to 5.4.3.3; 1> else if the E-UTRA RRCConnectionReconfiguration message is included in dl-DCCH-MessageEUTRA: 2> perform the RRC connection reconfiguration procedure as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10], clause 5.3.5.4; 1> else if the E-UTRA RRCConnectionRelease message is included in dl-DCCH-MessageEUTRA: 2> perform the RRC connection release as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10], clause 5.3.8; 1> else if the MobilityFromEUTRACommand message is included in the dl-DCCH-MessageEUTRA: 2> perform the mobility from E-UTRA procedure as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10], clause 5.4.3.3; | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.7.1a.3 |
4,798 | 6.4 Physical downlink shared channel | The physical downlink shared channel shall be processed and mapped to resource elements as described in clause 6.3 with the following additions and exceptions: - In resource blocks in which UE-specific reference signals are not transmitted, the PDSCH shall be transmitted on the same set of antenna ports as the PBCH, which is one of , , or . - In resource blocks in which UE-specific reference signals are transmitted, the PDSCH shall be transmitted on antenna port(s) ,,, , , , , or the antenna ports listed in Table 6.3.4.4-1, where is the number of layers used for transmission of the PDSCH. - If PDSCH is transmitted in MBSFN subframes as defined in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [4], the PDSCH shall be transmitted on one or several of antenna port(s) or on the antenna ports indicated in Table 6.3.4.4-1, where is the number of layers used for transmission of the PDSCH. - PDSCH is not mapped to resource elements used for UE-specific reference signals associated with PDSCH - In mapping to resource elements, the same positions of the cell-specifc reference shall be assumed for all antenna ports on which the PDSCH is transmitted and the positions of the cell-specific reference signals are given by clause 6.10.1.2 with the number of antenna ports and the frequency shift of the cell-specific reference signals derived as described in clause 6.10.1.2, unless indicated otherwise in clause 7.1.9 in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [4], - if one set of parameters for cell-specific reference signal positions are provided by clause 7.1.9 in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [4], the values of these parameters are used for all antenna ports whereon the PDSCH is transmitted in the resource blocks indicated by the relevant DCI. - if two sets of parameters for cell-specific reference signal positions are provided by clause 7.1.9 in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [4], the first set of parameters are used for the set of antenna ports associated with PDSCH codeword while the second set of parameters are used for the set of antenna ports associated with PDSCH codeword , according to codeword-to-layer mapping and layer-to-port mapping in Clause 6.3.3.2 and Clause 6.3.4.4, respectively. - If the DCI associated with the PDSCH uses the C-RNTI or semi-persistent C-RNTI, PDSCH modulation symbols on the indicated antenna ports are not mapped to resource elements assumed by the UE to be used for transmission of: - zero-power CSI reference signals, where the positions of the CSI reference signals assumed for each antenna port are given by clause 6.10.5.2. The configuration for zero power CSI reference signals is - obtained as described in clause 6.10.5.2 and used for all antenna ports whereon the PDSCH is transmitted, unless indicated otherwise in clause 7.1.9 in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [4] - if one set of parameters for zero power CSI reference signal configuration is provided by clause 7.1.9 in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [4], the values of these parameters are used for all antenna ports on which the PDSCH is transmitted in the resource blocks indicated by the corresponding DCI scheduling the PDSCH, and - if two sets of parameters for zero power CSI reference signal configuration are provided by clause 7.1.9 in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [4], the first set of parameters are used for the set of antenna ports associated with PDSCH codeword while the second set of parameters are used for the set of antenna ports associated with PDSCH codeword , according to codeword-to-layer mapping and layer-to-port mapping in Clause 6.3.3.2 and Clause 6.3.4.4, respectively. - obtained by higher-layer configuration of up to five reserved CSI-RS resources as part of the discovery signal configuration following the procedure for zero-power CSI-RS in clause 6.10.5.2. - non-zero-power CSI reference signals for CSI reporting, except for non-zero power CSI reference signals configured by csi-RS-ConfigNZP-ApList, where the positions of the non-zero-power CSI reference signals for CSI reporting are given by clause 6.10.5.2. The configuration for non-zero power CSI reference signals is obtained as described in clause 6.10.5.2. - PDSCH is not mapped to any physical resource-block pair(s) carrying an EPDCCH associated with the PDSCH. - PDSCH with subframe duration on antenna port 7, 8, 9, 10, 11, 12, 13 or 14 is not mapped to any physical resource-block pair(s) carrying PBCH or synchronization signals. - Frame structure type 1, PDSCH on antenna port 5 is not mapped to any physical resource-block pair(s) carrying PBCH or synchronization signals. - Frame structure type 2, PDSCH on antenna port 5 is not mapped to any physical resource-block pair(s) carrying PBCH. - For frame structure type 1 and 2, the index in the first slot in a subframe fulfils where is given by clause 7.1.6.4 of TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [4]. - For frame structure type 3, - if the higher layer parameter subframeStartPosition indicates 's07' and the downlink transmission starts in the second slot of a subframe - the index in the second slot in a subframe fulfils where is given by clause 7.1.6.4 of TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [4], - otherwise - the index in the first slot in a subframe fulfils where is given by clause 7.1.6.4 of TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [4], - In mapping to resource elements, if the DCI associated with the PDSCH uses the C-RNTI or semi-persistent C-RNTI, and transmit diversity according to clause 6.3.4.3 is used, and if the higher-layer parameter semiOpenLoop is not set and if the DCI associated with the PDSCH is not of format 7, resource elements in an OFDM symbol assumed by the UE to contain CSI-RS shall be used in the mapping if and only if all of the following criteria are fulfilled: - there is an even number of resource elements for the OFDM symbol in each resource block assigned for transmission, and - the complex-valued symbols and , where is an even number, can be mapped to resource elements and in the same OFDM symbol with . - In mapping to resource elements, if the DCI associated with the PDSCH uses C-RNTI or semi-persistent C-RNTI and if the higher-layer parameter semiOpenLoop is set for subframe PDSCH or the higher-layer parameter semiOpenLoop-STTI is set for slot/subslot PDSCH or if the DCI associated with the PDSCH is of format 7 and transmit diversity according to clause 6.3.4.3 is used, a pair of resource elements , shall be used in the mapping if and only if - the complex-valued symbols and can be mapped to resource elements and in the same OFDM symbol and the same PRB with , where is an even number and starts from 0 at the lowest subcarrier of the PRB. | 3GPP TS 36.211 | Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation | RAN1 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.4 |
4,799 | 13.1.1 TLS protection between NF and SEPP 13.1.1.0 General | To allow for TLS protection between the SEPP and Network Functions or SCPs within a PLMN, the SEPP shall support: - TLS wildcard certificate for its domain name and generation of telescopic FQDN based on an FQDN obtained from the received N32-f message as specified in clause 13.1.1.1. - using the custom HTTP header 3gpp-Sbi-Target-apiRoot, defined in clause 5.2.3.2.4 of TS 29.500[ 5G System; Technical Realization of Service Based Architecture; Stage 3 ] [74], in the HTTP request originated by the NF within the SEPP’s PLMN, to forward the protected HTTP Request message towards the remote PLMN as specified in clause 13.1.1.2. NOTE: Whether the SEPP and NFs within the SEPP’s PLMN use telescopic FQDN or the custom HTTP header is based on PLMN operator’s policy. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 13.1.1 |
4,800 | 13.4.1.1.2 Service Request Process | The complete service request is a two-step process including requesting an access token by NF Service Consumer (Step 1, i.e. 1a or 1b), and then verification of the access token by NF Service Producer (Step 2). NOTE: The service request process regarding the enabler for network automation is specified in Annex X. Step 1: Access token request Pre-requisite: - The NF Service consumer (OAuth2.0 client) is registered with the NRF (Authorization Server). - The NF Service Producer (OAuth2.0 resource server) is registered with the NRF (Authorization Server) with optionally "additional scope" information per NF type. - The NRF and NF Service Producer share the required credentials. - The NRF and NF have mutually authenticated each other – where the NF Service Consumer is identified by the NF Instance ID of the public key certificate of the NF Service Consumer.. 1a. Access token request for accessing services of NF Service Producers of a specific NF type The following procedure describes how the NF Service Consumer obtains an access token before service access to NF Service Producers of a specific NF type. Figure 13.4.1.1.2-1: NF Service Consumer obtaining access token before NF Service access 1. The NF Service Consumer shall request an access token from the NRF in the same PLMN using the Nnrf_AccessToken_Get request operation. The message shall include the NF Instance Id(s) of the NF Service Consumer, the requested "scope" including the expected NF Service name(s) and optionally "additional scope" information (i.e. requested resources and requested actions (service operations) on the resources), NF type of the expected NF Service Producer instance and NF Service Consumer. The NF Service Consumer may also include a list of NSSAIs or list of NSI IDs for the expected NF Service Producer instances. The message may include the NF Set ID and/or NF Service Set Id of the expected NF Service Producer instances. The message may include a list of S-NSSAIs of the NF Service Consumer. The message may also include the PLMN ID(s) of the NF Service Consumer. 2. The NRF shall verify that the input parameters NF Instance ID and NF type as well as PLMN ID(s), if available, in the access token request match with the corresponding ones in the public key certificate of the NF Service Consumer or those in the NF profile of the NF Service Consumer. If the verification of the parameters in the access token request fails, the access token request is not further processed. The NRF may additionally verify the S-NSSAIs of the NF Service Consumer. The NRF checks whether the NF Service Consumer is authorized to access the requested service(s). For example, the NRF may verify that the NF Service Consumer can serve a slice which is included in the allowed slices for the NF Service Producer. If the NF Service Consumer is authorized, the NRF shall then generate an access token with appropriate claims included. The NRF shall digitally sign the generated access token based on a shared secret or private key as described in RFC 7515 [45]. If the NF Service Consumer is not authorized, the NRF shall not issue an access token to the NF Service Consumer. The claims in the token shall include the NF Instance Id of NRF (issuer), NF Instance Id of the NF Service Consumer (subject), NF type of the NF Service Producer (audience), expected service name(s), (scope), expiration time (expiration) and optionally "additional scope" information (allowed resources and allowed actions (service operations) on the resources). The claims may include a list of NSSAIs or NSI IDs for the expected NF Service Producer instances. The claims may include the NF Set ID and/or NF Service Set Id of the expected NF Service Producer instances. 3. If the authorization is successful, the NRF shall send access token to the NF Service Consumer in the Nnrf_AccessToken_Get response operation, otherwise it shall reply based on Oauth 2.0 error response defined in RFC 6749 [43]. The other parameters (e.g., the expiration time, allowed scope) sent by NRF in addition to the access token are described in TS 29.510[ 5G System; Network function repository services; Stage 3 ] [68]. The NF Service Consumer may store the received token(s). Stored tokens may be re-used for accessing service(s) from NF Service Producer NF type listed in claims (scope, audience) during their validity time. 1b. Access token request for accessing services of a specific NF Service Producer instance / NF Service Producer service instance The following steps describes how the NF Service Consumer obtains an access token before service access to a specific NF Service Producer instance / NF Service Producer service instance. 1. The NF Service Consumer shall request an access token from the NRF for a specific NF Service Producer instance / NF Service Producer service instance. The request shall include the NF Instance Id(s) of the requested NF Service Producer, the expected NF Service name, optionally "additional scope" information (allowed resources and allowed actions (service operations) on the resources) and NF Instance Id of the NF Service Consumer. The request may also include the PLMN ID(s) of the NF Service Consumer. 2. The NRF shall verify that the input parameters in the access token request, i.e. NF Instance ID and, if available, PLMN ID(s) and NF type, match with the corresponding ones in the public key certificate of the NF Service Consumer or those in the NF profile of the NF Service Consumer. If the verification of the parameters in the access token request fails, the access token request is not further processed. The NRF checks whether the NF Service Consumer is authorized to access the requested services from the NF Service Producer instance/NF Service Producer service instance, and then proceeds to generate an access token with the appropriate claims included. If the NF Service Consumer is not authorized, the NRF shall not issue an access token to the NF Service Consumer. The claims in the token shall include the NF Instance Id of NRF (issuer), NF Instance Id of the NF Service Consumer (subject), NF Instance Id or several NF Instance Id(s) of the requested NF Service Producer (audience), expected service name(s) (scope), optionally "additional scope" information (allowed resources and allowed actions (service operations) on the resources), and expiration time (expiration). 3. The token shall be included in the Nnrf_AccessToken_Get response sent to the NF Service Consumer. The NF Service Consumer may store the received token(s). Stored tokens may be re-used for accessing service(s) from NF Instance Id or several NF Instance Id(s) of the requested NF Service Producer instance listed in claims (scope, audience) during their validity time. Step 2: Service access request based on token verification The following figure and procedure describe how authorization is performed during Service request of the NF Service Consumer. Prior to the request, the NF Service Consumer may perform Nnrf_NFDiscovery_Request operation with the requested additional scopes to select a suitable NF Service Producer (resource server) which is able to authorize the Service Access request. Figure 13.4.1.1.2-2: NF Service Consumer requesting service access with an access token Pre-requisite: The NF Service Consumer is in possession of a valid access token before requesting service access from the NF Service Producer. 1. The NF Service Consumer requests service from the NF Service Producer. The NF Service Consumer shall include the access token. The NF Service Consumer and NF Service Producer shall authenticate each other following clause 13.3. 2. The NF Service Producer shall verify the token as follows: - The NF Service Producer ensures the integrity of the token by verifying the signature using NRF’s public key or checking the MAC value using the shared secret. - If integrity check is successful, the NF Service Producer shall verify the claims in the token as follows: - In the direct communication case, it checks that the NF Instance ID in the subject claim within the access token matches the NF Instance ID in the subjectAltName in the NF Service Consumer's TLS client certificate. NOTE: Void. - It checks that the audience claim in the access token matches its own identity or the type of NF Service Producer. If a list of NSSAIs or list of NSI IDs is present, the NF Service Producer shall check that it serves the corresponding slice(s). If applicable (e.g., when the request is for information related to a specific UE), the NF Service Producer may check that the NF Service Consumer is allowed to access (as indicated by the NF Service Producer’s NSSAIs in the access token presented by the NF Service Consumer) at least one of the slice(s) that the UE is currently registered to, e.g., by verifying that the UE’s allowed NSSAI(s) intersect with the NF Service Producer's NSSAIs in the access token. - If an NF Set ID present, the NF Service Producer shall check the NF Set ID in the claim matches its own NF Set ID. If an NF Service Set ID present, the NF Service Producer shall check if the NF Service Consumer is authorized to access the requested service according to NF Service Producer Service Set ID in the access token claim. - If scope is present, it checks that the scope matches the requested service operation. - If the access token contains "additional scope" information (i.e. allowed resources and allowed actions (service operations) on the resources), it checks that the additional scope matches the requested service operation. - It checks that the access token has not expired by verifying the expiration time in the access token against the current data/time. - If the CCA is present in the service request, it may verify the CCA as specified in clause 13.3.8.3 and that the subject claim (i.e., the NF Instance Id of the NF Service Consumer) in the access token matches the subject claim in the CCA. 3. If the verification is successful, the NF Service Producer shall execute the requested service and responds back to the NF Service Consumer. Otherwise, it shall reply based on Oauth 2.0 error response defined in RFC 6749 [43]. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 13.4.1.1.2 |
Subsets and Splits
No saved queries yet
Save your SQL queries to embed, download, and access them later. Queries will appear here once saved.