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,201 | 4.2 Linkage between the protocols for EPS mobility management and EPS session management | During the EPS attach procedure, the network can activate a default EPS bearer context (i.e. if the UE requests PDN connectivity in the attach request). Additionally, the network can activate one or several dedicated EPS bearer contexts in parallel for PDN connections of IP or Ethernet PDN type. To this purpose the EPS session management messages for the default EPS bearer context activation can be transmitted in an information element in the EPS mobility management messages. In this case, the UE and the network execute the attach procedure, the default EPS bearer context activation procedure, and the dedicated EPS bearer context activation procedure in parallel. The UE and network shall complete the combined default EPS bearer context activation procedure and the attach procedure before the dedicated EPS bearer context activation procedure is completed. If EMM-REGISTERED without PDN connection is not supported by the UE or the MME, then the success of the attach procedure is dependent on the success of the default EPS bearer context activation procedure. If the attach procedure fails, then the ESM procedures also fail. A UE using EPS services with control plane CIoT EPS optimization can initiate transport of user data via the control plane. For this purpose a UE in EMM-IDLE mode can initiate the service request procedure and transmit the ESM DATA TRANSPORT message in an information element in the CONTROL PLANE SERVICE REQUEST message. Except for the attach procedure and the service request procedure, during EMM procedures the MME shall suspend the transmission of ESM messages. During the service request procedure the MME may suspend the transmission of ESM messages. Except for the attach procedure and the service request procedure for UE initiated transport of user data via the control plane, during EMM procedures the UE shall suspend the transmission of ESM messages. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.2 |
4,202 | 5.15.3 Subscription aspects | The Subscription Information shall contain one or more S-NSSAIs i.e. Subscribed S-NSSAIs. The subscription information shall include at least one default S-NSSAI. The UDM sends at the most 16 Subscribed S-NSSAIs to AMF, i.e. the number that can fit in a Configured NSSAI. The subscription information the UDM sends to the AMF shall include at least one default S-NSSAI. If an S-NSSAI is marked as default, then the network is expected to serve the UE with a related applicable Network Slice instance when the UE does not send any permitted S-NSSAI to the network in a Registration Request message as part of the Requested NSSAI. The Subscription Information for each S-NSSAI may contain: - a Subscribed DNN list and one default DNN; and - the indication whether the S-NSSAI is marked as default Subscribed S-NSSAI; and - the indication whether the S-NSSAI is subject to Network Slice-Specific Authentication and Authorization; and - Network Slice Simultaneous Usage Group (NSSRG) information (see clause 5.15.12). The network verifies the Requested NSSAI the UE provides in the Registration Request against the Subscription Information. For the S-NSSAIs subject to Network Slice-Specific Authentication and Authorization the clause 5.15.10 applies. NOTE 1: It is recommended that at least one of the Subscribed S-NSSAIs marked as default S-NSSAI is not subject to Network Slice-specific Authentication and Authorization, in order to ensure access to services even when Network Slice-specific Authentication and Authorization fails. NOTE 2: It is recommended to minimize the number of Subscribed S-NSSAIs in subscriptions for NB-IoT or NR RedCap capable UEs to minimize overhead for signalling a large number of S-NSSAIs in Requested NSSAI in RRC and NAS via NB-IoT or NR RedCap. In roaming case, the UDM shall provide to the VPLMN only the S-NSSAIs from the Subscribed S-NSSAIs the HPLMN allows for the UE in the VPLMN. If the UE is subject to restrictions of simultaneous registration of network slices (i.e. if the Subscription Information for the S-NSSAIs contains NSSRG information), the UDM provides to the VPLMN a subscribed S-NSSAIs and, if applicable, NSSRG information, as described in clause 5.15.12. NOTE 3: Network slice instances supporting an S-NSSAI subject to Network Slice-Specific Authentication and Authorization need to be deployed with AMFs supporting Network Slice-Specific Authentication and Authorization, otherwise S-NSSAIs requiring Network Slice-Specific Authentication and Authorization would be incorrectly allowed without execution of Network Slice-Specific Authentication and Authorization. NOTE 4: Network slice instances supporting an S-NSSAI subject to Network Slice Admission Control (NSAC) for number of registered UE per network slice need to be deployed with AMFs supporting NSAC, otherwise S-NSSAIs requiring NSAC would be incorrectly allowed without execution of NSAC. When the UDM updates the Subscribed S-NSSAI(s) to the serving AMF, based on configuration in this AMF, the AMF itself or the NSSF determines the mapping of the Configured NSSAI for the Serving PLMN and/or Allowed NSSAI to the Subscribed S-NSSAI(s). The serving AMF then updates the UE with the above information as described in clause 5.15.4. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.15.3 |
4,203 | 5.7.9.2 Initiation | If the UE supports storage of mobility history information, the UE shall: 1> If the UE supports PSCell mobility history information and upon addition of a PSCell: 2> include an entry in visitedPSCellInfoList in variable VarMobilityHistoryReport possibly after performing the following, if necessary: 3> if visitedPSCellInfoListReport is available in the visitedCellInfoList in variable VarMobilityHistoryReport: 4> for the oldest PCell entry in visitedCellInfoList including visitedPSCellInfoListReport; 5> remove the oldest entry in the visitedPSCellInfoListReport; 3> else: 4> remove the oldest entry in visitedPSCellInfoList in variable VarMobilityHistoryReport; 2> for the included entry: 3> set the field timeSpent of the entry according to following: 4> if this is the first PSCell entry for the current PCell since entering the current PCell in RRC_CONNECTED: 5> include the entry as the time spent with no PSCell since entering the current PCell in RRC_CONNECTED; 4> else: 5> include the time spent with no PSCell since last PSCell release since entering the current PCell in RRC_CONNECTED; 1> If the UE supports PSCell mobility history information and upon change, or release of a PSCell while being connected to the current PCell: 2> include an entry in visitedPSCellInfoList of the variable VarMobilityHistoryReport possibly after performing the following, if necessary: 3> if visitedPSCellInfoListReport is available in the visitedCellInfoList in variable VarMobilityHistoryReport: 4> for the oldest PCell entry in visitedCellInfoList including visitedPSCellInfoListReport; 5> remove the oldest entry in the visitedPSCellInfoListReport; 3> else: 4> remove the oldest entry in visitedPSCellInfoList in variable VarMobilityHistoryReport; 2> for the included entry: 3> if the global cell identity of the previous PSCell is available: 4> include the global cell identity of that cell in the field visitedCellId of the entry; 3> else: 4> include the physical cell identity and carrier frequency of that cell in the field visitedCellId of the entry; 3> set the field timeSpent of the entry as the time spent in the previous PSCell while being connected to the current PCell; 1> Upon change of suitable cell, consisting of PCell in RRC_CONNECTED (for NR or E-UTRA cell) or serving cell in RRC_INACTIVE (for NR cell) or in RRC_IDLE (for NR or E-UTRA cell), to another NR or E-UTRA cell, or when entering any cell selection' state from 'camped normally' state in NR or LTE or when entering 'any cell selection' state from a suitable cell in RRC_CONNECTED state in NR or LTE: 2> include an entry in visitedCellInfoList of the variable VarMobilityHistoryReport possibly after removing the oldest entry, if necessary, according to following: 3> if the global cell identity of the previous PCell/serving cell is available: 4> include the global cell identity of that cell in the field visitedCellId of the entry; 3> else: 4> include the physical cell identity and carrier frequency of that cell in the field visitedCellId of the entry; 3> set the field timeSpent of the entry as the time spent in the previous PCell/serving cell; 3> if the UE supports PSCell mobility history information and if the UE continues to be connected to the same PSCell during the change of the PCell in RRC_CONNECTED; or 3> if the UE supports PSCell mobility history information and if the UE changes PSCell at the same time as the change of the PCell in RRC_CONNECTED; or 3> if the UE supports PSCell mobility history information and if the PSCell is released at the same time as the change of the PCell in RRC_CONNECTED: 4> include an entry in visitedPSCellInfoList of the variable VarMobilityHistoryReport possibly after performing the following, if necessary: 5> if visitedPSCellInfoListReport is available in the visitedCellInfoList in variable VarMobilityHistoryReport: 6> for the oldest PCell entry in visitedCellInfoList including visitedPSCellInfoListReport; 7> remove the oldest entry in the visitedPSCellInfoListReport; 5> else: 6> remove the oldest entry in visitedPSCellInfoList in variable VarMobilityHistoryReport; 4> for the included entry: 5> if the global cell identity of the PSCell (in case the UE continues to be connected to the same PSCell) or the previous PSCell (in case the UE changes PSCell, or in case PSCell is released) is available: 6> include the global cell identity of that cell in the field visitedCellId of the entry; 5> else: 6> include the physical cell identity and carrier frequency of that cell in the field visitedCellId of the entry; 5> set the field timeSpent of the entry as the time spent in the PSCell, while being connected to previous PCell; 3> if the UE supports PSCell mobility history information and if the UE was not configured with a PSCell at the time of change of PCell in RRC_CONNECTED: 4> include an entry in visitedPSCellInfoList after performing the following, if necessary; 5> if visitedPSCellInfoListReport is available in the visitedCellInfoList in variable VarMobilityHistoryReport: 6> for the oldest PCell entry in visitedCellInfoList including visitedPSCellInfoListReport; 7> remove the oldest entry in the visitedPSCellInfoListReport; 5> else: 6> remove the oldest entry in visitedPSCellInfoList in variable VarMobilityHistoryReport; 4> for the included entry: 5> set the field timeSpent of the entry as the time without PSCell according to the following: 6> if the UE experienced a PSCell release since entering the previous PCell in RRC_CONNECTED: 7> include the time spent with no PSCell since last PSCell release since entering the previous PCell in RRC_CONNECTED; 6> else: 7> include the time spent with no PSCell since entering the previous PCell in RRC_CONNECTED; 3> if the UE supports PSCell mobility history information and if visitedPSCellInfoList exists in VarMobilityHistoryReport: 4> include visitedPSCellInfoList in VarMobilityHistoryReport in the visitedPSCellInfoListReport within the entry of the visitedCellInfoList associated to the latest PCell entry; 4> remove visitedPSCellInfoList from the variable VarMobilityHistoryReport; 1> if the UE supports PSCell mobility history information and upon entering 'camped normally' state in NR (in RRC_IDLE or RRC_INACTIVE) or E-UTRA (in RRC_IDLE) while previously in RRC_CONNECTED state NR or LTE while not connected to a PSCell: 2> include an entry in visitedPSCellInfoList after performing the following, if necessary; 3> if visitedPSCellInfoListReport is available in the visitedCellInfoList in variable VarMobilityHistoryReport: 4> for the oldest PCell entry in visitedCellInfoList including visitedPSCellInfoListReport; 5> remove the oldest entry in the visitedPSCellInfoListReport; 3> else: 4> remove the oldest entry in visitedPSCellInfoList in variable VarMobilityHistoryReport; 2> for the included entry: 3> set the field timeSpent of the entry as the time without PSCell according to the following: 4> if the UE experienced a PSCell release since entering the current PCell in RRC_CONNECTED: 5> include the time spent with no PSCell since last PSCell release after entering the current PCell in RRC_CONNECTED; 4> else: 5> include the time spent with no PSCell since entering the current PCell in RRC_CONNECTED; 1> upon entering 'camped normally' state in NR (in RRC_IDLE or RRC_INACTIVE) or E-UTRA (in RRC_IDLE) while previously in 'any cell selection' state or 'camped on any cell' state in NR or LTE: 2> include an entry in variable VarMobilityHistoryReport possibly after removing the oldest entry, if necessary, according to following: 3> set the field timeSpent of the entry as the time spent in 'any cell selection' state and/or 'camped on any cell' state in NR or LTE. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.7.9.2 |
4,204 | – DownlinkPreemption | The IE DownlinkPreemption is used to configure the UE to monitor PDCCH for the INT-RNTI (interruption). DownlinkPreemption information element -- ASN1START -- TAG-DOWNLINKPREEMPTION-START DownlinkPreemption ::= SEQUENCE { int-RNTI RNTI-Value, timeFrequencySet ENUMERATED {set0, set1}, dci-PayloadSize INTEGER (0..maxINT-DCI-PayloadSize), int-ConfigurationPerServingCell SEQUENCE (SIZE (1..maxNrofServingCells)) OF INT-ConfigurationPerServingCell, ... } INT-ConfigurationPerServingCell ::= SEQUENCE { servingCellId ServCellIndex, positionInDCI INTEGER (0..maxINT-DCI-PayloadSize-1) } -- TAG-DOWNLINKPREEMPTION-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
4,205 | 5.8.2.6.3 Reporting of Usage Information towards SMF | The UPF shall support reporting of usage information to the SMF. The UPF shall be capable to support reporting based on different triggers, including: - Periodic reporting with period defined by the SMF. - Usage thresholds provided by the SMF. - Report on demand received from the SMF. The SMF shall make sure that the multiple granularity levels required by the reporting keys in the Usage Reporting rules satisfy the following aggregation levels without requiring a knowledge of the granularity levels by the UPF: - PDU Session level reporting; - Traffic flow (for both charging and usage monitoring) level reporting as defined by the reporting keys in the Usage Reporting Rule (see the description above). Based on the mapping between Monitoring key and PCC rule stored at the SMF, the SMF shall combine the reported information with session and subscriber related information which is available at the SMF, for Usage Monitoring reporting over the corresponding Npcf interface (N7 reference point). Based on the mapping between Charging key and Sponsor Identity (if applicable) and PCC rule stored at the SMF, the SMF shall combine the reported information with session and subscriber related information which is available at the SMF, for offline and online charging reporting over the corresponding charging interfaces. This functionality is specified in TS 32.255[ Telecommunication management; Charging management; 5G data connectivity domain charging; Stage 2 ] [68]. The usage information shall be collected in the UPF and reported to the SMF as defined in 5.8.2.6, based on Monitoring Keys and triggers which are specified in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.8.2.6.3 |
4,206 | 4.3.5.6 Change of additional PDU Session Anchor for IPv6 multi-homing or UL CL | The following procedure is triggered by an SMF when the SMF needs to modify IPv6 multi-homing or UL CL rule (i.e. traffic filter in the Branching Point or the UL CL) in order to move the some or whole traffic flows of the existing additional PDU Session Anchor which was established by the IPv6 multi-homing or the UL CL operations (i.e. PSA1 in figure 4.3.5.6-1) to a new additional PDU Session Anchor (i.e. PSA2 in figure 4.3.5.6-1) which is established under the same Branching Point or UL CL for a UE where the UE already has a PDU Session Anchor which was established before the event of Branching Point or UL CL insertion (i.e. PSA0 in figure 4.3.5.6-1). This procedure establishes a new additional PDU Session Anchor (i.e. PSA2) and conditionally releases the existing additional PDU Session Anchor (i.e. PSA1), while modifying IPv6 multi-homing or UL CL rule in the same Branching Point or UL CL under controlled by the same SMF. Figure 4.3.5.6-1: Change of additional PSA for a PDU Session in IPv6 multi-homing or UL CL case 1. The SMF decides to change one additional PSA of a PDU Session with IPv6 multi-homing or UL CL, due to events that may benefit from such change or upon request from an Application Function. 2. 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 PSA2 is selected and waits for a notification response from the AF before configuring the PSA2. If the SMF receives a negative notification response from the AF, the SMF may stop the procedure. This is defined in Figure 4.3.6.3-1. The SMF sends an N4 Session Establishment Request to PSA2 and provides the tunnel ID of Branching Point or UL CL, Packet detection, enforcement and reporting rules to be installed on the PSA2 for this PDU Session. The SMF may also indicate local PSA2 to buffer the uplink data. The PSA2 acknowledges by sending an N4 Session Establishment Response. The tunnel ID of PSA2 is provided to the SMF in this step. In the case of IPv6 multi-homing PDU Session, a new IPv6 prefix corresponding to PSA2 is allocated (by the SMF or by the UPF depending on the deployment) and if the PCF has subscribed to the IP allocation/release event, the SMF performs the Session Management Policy Modification Procedure as defined in clause 4.16.5 to provide the new allocated IPv6 prefix to the PCF. 3a. In the case of PDU session with UL CL, 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 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 sends an N4 Session Modification Request to the Branching Point or UL CL to update the UL traffic filter according to new allocated IPv6 prefix allocated to PSA 2 or the UL CL rules regarding to the traffic flows that the SMF tries to move from PSA1 to PSA2. The N4 Session Modification Request message contains the identifications of traffic filter that needs to be updated and the tunnel ID of PSA2. NOTE: The identification of a traffic filter can be either the index of the traffic filter, or a single value of the information field in traffic filter (e.g. the tunnel ID of next hop), or a combination value of some information field in the traffic filter (e.g. the tunnel ID of next hop with source port number). 3b. The Branching Point or the UL CL acknowledges by N4 Session Modification Response the Branching Point or when the UL CL successfully updates all the traffic filters that the SMF requests to modify. 3c. The SMF may also indicate PSA2 to stop buffering and start forwarding uplink data. 4. In the case of IPv6 multi-homing PDU Session, 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 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. In the case of IPv6 multi-homing PDU Session, The SMF notifies the UE of the availability of the new IP prefix @ PSA2. This is performed using an IPv6 Router Advertisement message (RFC 4861 [6]). Also, the SMF sends IPv6 multi-homed routing rule along with the IPv6 prefix to the UE using an IPv6 Router Advertisement message (RFC 4191 [21]) as described in clause 5.8.2.2.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The SMF may also indicate PSA2 to stop buffering and start forwarding uplink data. 5. In the case of IPv6 multi-homing PDU Session, The SMF may re-configure the UE for the original IP prefix @ PSA0,i.e. SMF sends IPv6 multi-homed routing rule along with the IPv6 prefix to the UE using an IPv6 Router Advertisement message (RFC 4191 [21]) as described in clause 5.8.2.2.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. 6. Step 6 occurs only if the Branching Point or UL CL does not have any traffic filter on the PDU Session which forwards a traffic flow to PSA1. 6a. The SMF sends an N4 Session Release Request with N4 session ID to PSA1. The PSA1 shall release all tunnel resources and contexts associated with the N4 session. 6b. PSA1 sends an N4 Session Release Response with N4 session ID to the SMF at the same moment that PSA1 successfully releases all tunnel resources and contexts associated with the N4 session. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.3.5.6 |
4,207 | 10.5.1.11 Priority Level | The purpose of the Priority Level is to provide information defining the priority level requested or applied. The Priority Level IE may be included in CM_SERVICE_REQUEST, CALL_PROCEEDING and SETUP messages. The Priority Level information element is coded as shown in figure 10.5.11/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.11/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The Priority Level is a type 1 information element with 1 octet length. Figure 10.5.11/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Priority Level Table 10.5.11/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Priority Level | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 10.5.1.11 |
4,208 | 13.3.2 Principles | The following principles shall apply if this procedure is supported, enabled by operator policy and if the PGW pertains to the same PLMN as the originating entity or if the PGW pertains to a different PLMN and operator policy in the originating entity allows to use this procedure towards this PLMN. A GTP-C entity originating a Create Session Request (i.e. MME, SGSN, TWAN or ePDG) shall include in the message the Origination Time Stamp indicating the absolute time at which the request is initiated, as specified in clause 13.2.2, and the Maximum Wait Time indicating the maximum time period to complete the processing of the request. The Maximum Wait Time, together with the Origination Time Stamp, indicates the absolute time at which the request times out at the originating entity. The MME/SGSN shall set the Maximum Wait Time to a value smaller or equal to (N3+1) x T3 set in the SGW, to avoid upstream entities continuing to process requests which would have ceased to be processed by the SGW, which could result in hanging contexts in upstream entities. NOTE 1: If the Maximum Wait Time is set to a value smaller than N3 x T3 set in the SGW, the SGW actually stops retransmitting a given GTP-C Create Session Request as soon as it receives a rejection response from the PGW due to the expiry of the Maximum Wait Time. I.e. the Maximum Wait Time actually leads to shorten the duration during which the SGW retransmits the GTP-C request. The SGW shall forward the Origination Time Stamp over the S5/S8 interface as specified in clause 13.2.2. The SGW shall also forward the Maximum Wait Time over the S5/S8 interface, if received from the MME/SGSN. Upon receipt of a request which contains the Origination Time Stamp and the Maximum Wait Time parameters, the receiving entity should check that the request has not already timed out at the originating entity. The receiving entity may perform additional similar checks during the processing of the request, e.g. upon receipt of a response from the next upstream entity. The receiving entity should reject a request that is known to have timed out with the cause 'Timed Out Request'; it may alternatively drop the request. Besides, the receiving entity should initiate the release of any session it may have successfully created towards an upstream entity, to avoid hanging sessions in the network. NOTE 2: Sending a rejection response over the last hop towards the originating node, i.e. over S11/S4 or S2a/S2b, is not useful as the request has timed out at the originated entity. In the context of this specification, the receiving entity refers to an SGW or PGW. 3GPP TS 29.212[ Policy and Charging Control (PCC); Reference points ] [29] and 3GPP TS 29.273[ Evolved Packet System (EPS); 3GPP EPS AAA interfaces ] [68] further specify: - the PGW requirements regarding the forwarding of the Maximum Wait Time parameter over the Gx and/or S6b interfaces, when received from the SGW or TWAN/ePDG; - the handling of the Maximum Wait Time parameter by the PCRF and 3GPP AAA Server. An originating entity which detects a NTP failure shall not insert the Origination Time Stamp and the Maximum Wait Time parameters towards other entities. A receiving entity which detects a NTP failure shall ignore the the Maximum Wait Time parameter. | 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 | 13.3.2 |
4,209 | 5.30.3.2 Identifiers | The following is required for identification: - A CAG is identified by a CAG Identifier which is unique within the scope of a PLMN ID; - A CAG cell broadcasts one or multiple CAG Identifiers per PLMN; NOTE 1: It is assumed that a cell supports broadcasting a total of twelve CAG Identifiers. Further details are defined in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [28]. - A CAG cell may in addition broadcast a human-readable network name per CAG Identifier: NOTE 2: The human-readable network name per CAG Identifier is only used for presentation to user when user requests a manual CAG selection. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.30.3.2 |
4,210 | 6.35.3 Service Function Management | - The service function management shall allow the operator to create, modify, and delete a service function based on operator’s service function chaining policies. - The service function management shall allow the operator to create, configure, and control a chain of service functions per application and its users on per UE basis based on operator’s policy or request from third parties. - The service function management shall be able to manage service function chaining for deployments where the Hosted Services are provided by the operator and for deployments where the Hosted Services are provided by a third party. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.35.3 |
4,211 | 5.5.1.1 X2-based handover 5.5.1.1.1 General | These procedures are used to hand over a UE from a source eNodeB to a target eNodeB using the X2 reference point. In these procedures the MME is unchanged. Two procedures are defined depending on whether the Serving GW is unchanged or is relocated. In addition to the X2 reference point between the source and target eNodeB, the procedures rely on the presence of S1-MME reference point between the MME and the source eNodeB as well as between the MME and the target eNodeB. The handover preparation and execution phases are performed as specified in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [5]. If emergency bearer services are ongoing for the UE handover to the target eNodeB is performed independent of the Handover Restriction List. The MME checks, as part of the Tracking Area Update in the execution phase, if the handover is to a restricted area and if so MME releases the non-emergency bearers as specified in clause 5.10.3. If the serving PLMN changes during X2-based handover, the source eNodeB shall indicate to the target eNodeB (in the Handover Restriction List) the PLMN selected to be the new Serving PLMN. When the UE receives the handover command it will remove any EPS bearers for which it did not receive the corresponding EPS radio bearers in the target cell. As part of handover execution, downlink and optionally also uplink packets are forwarded from the source eNodeB to the target eNodeB. When the UE has arrived to the target eNodeB, downlink data forwarded from the source eNodeB can be sent to it. Uplink data from the UE can be delivered via the (source) Serving GW to the PDN GW or optionally forwarded from the source eNodeB to the target eNodeB. Only the handover completion phase is affected by a potential change of the Serving GW, the handover preparation and execution phases are identical. If the MME receives a rejection to a NAS procedure (e.g. dedicated bearer establishment/modification/release; location reporting control; NAS message transfer; etc.) from the eNodeB with an indication that an X2 handover is in progress (see TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [5]), the MME shall reattempt the same NAS procedure either when the handover is complete or the handover is deemed to have failed, except in the case of Serving GW relocation. The failure is known by expiry of the timer guarding the NAS procedure. If the X2 handover includes the Serving GW relocation, and if the MME receives a rejection to a NAS message transfer for a Downlink NAS Transport or Downlink Generic NAS Transport message from the eNodeB with an indication that an X2 handover is in progress, the MME should resend the corresponding message to the target eNodeB when either the handover is complete or to the source eNodeB when the handover is deemed to have failed if the MME is still the serving MME. If the MME receives a rejection to a NAS message transfer for a CS Service Notification or to a UE Context Modification Request message with a CS Fallback indicator from the eNodeB with an indication that an X2 handover is in progress, the MME shall resend the corresponding message to the target eNodeB when the handover is complete or to the source eNodeB when the handover is deemed to have failed. If during the handover procedure the MME detects that the Serving GW needs be relocated, the MME shall reject any PDN GW initiated EPS bearer(s) request received since handover procedure started and shall include an indication that the request has been temporarily rejected due to handover procedure in progress. The rejection is forwarded by the Serving GW to the PDN GW, with the indication that the request has been temporarily rejected. Upon reception of a rejection for an EPS bearer(s) PDN GW initiated procedure with an indication that the request has been temporarily rejected due to handover procedure in progress, the PDN GW start a locally configured guard timer. The PDN GW shall re-attempt, up to a pre-configured number of times, when either it detects that the handover is completed or has failed using message reception or at expiry of the guard timer. For handover the following applies related to handling of radio capabilities: - If the source eNodeB and target eNodeB support RACS as defined in clause 5.11.3a, the source eNodeB provides the UE's UE Radio Capability ID to the target eNodeB. - If the source eNodeB has knowledge that the target eNodeB might not have a local copy of the Radio Capability corresponding to the UE Radio Capability ID (i.e. because the source eNodeB had itself to retrieve the UE's Radio Capability from the MME) then the source eNodeB may also send some (or all) of the UE's Radio Capability to the target eNodeB (the size limit based on local configuration) in X2 signalling as defined in TS 36.423[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 Application Protocol (X2AP) ] [76]. In the case of inter-PLMN handover, when the source and target eNodeB support RACS as defined in clause 5.11.3a and the source eNodeB determines based on local configuration that the target PLMN does not support the UE Radio Capability ID assigned by the source PLMN, then the source eNodeB shall provide the UE radio capabilities to the target eNodeB and shall not send the UE Radio Capability ID. - If the target eNodeB does not have mapping between the specific UE Radio Capability ID and the UE radio capabilities and no UE radio capabilities are provided by source eNodeB, it shall use the procedure described in TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [36] to retrieve the mapping from the Core Network. - If, as permitted in TS 36.423[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 Application Protocol (X2AP) ] [76], the target eNodeB during the handover preparation received the UE radio capabilities but did not receive the UE Radio Capability ID the target eNodeB shall proceed with handover using the received UE radio capabilities. - If the target eNodeB received both the UE radio capabilities and the UE Radio Capability ID, then the target eNodeB shall use any locally stored UE radio capability information corresponding to the UE Radio Capability ID. - If none are stored locally, the target eNodeB may request the full UE radio capability information from the core network. - If the full UE radio capability information is not promptly received from the core network, or the target eNodeB chooses not to request it, then the target eNodeB shall proceed with the UE radio capabilities sent by the source RAN node. The target eNodeB shall not use the UE radio capability information received from the source eNodeB for any other UE with the same UE Radio Capability ID. - If the target eNodeB knows (e.g. by configuration) that the UE's E-UTRA radio capabilities applicable to the target eNB may be different to the E-UTRA radio capabilities stored in the source eNodeB (e.g. for handover to/from an E-UTRA eNodeB that supports the NTN enhancements as defined in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [5]), then the target eNodeB shall trigger retrieval of the radio capability information again from the UE. NOTE: In order to support handover from an E-UTRA eNodeB that supports the NTN enhancements as defined in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [5] the target eNodeB needs to be upgraded to support the above 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") | 5.5.1.1 |
4,212 | 7 Handling of unknown, unforeseen, and erroneous protocol data 7.1 General | The procedures specified in the present document apply to those messages which pass the checks described in this clause. This clause also specifies procedures for the handling of unknown, unforeseen, and erroneous protocol data by the receiving entity. These procedures are called "error handling procedures", but in addition to providing recovery mechanisms for error situations they define a compatibility mechanism for future extensions of the protocols. Clauses 7.1 to 7.8 shall be applied in order of precedence. Most error handling procedures are mandatory for the UE. Detailed error handling procedures in the network are implementation dependent and may vary from PLMN to PLMN. However, when extensions of this protocol are developed, networks will be assumed to have the error handling that is indicated in this clause as mandatory ("shall") and that is indicated as strongly recommended ("should"). Also, the error handling of the network is only considered as mandatory or strongly recommended when certain thresholds for errors are not reached during a dedicated connection. For definition of semantical and syntactical errors see 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [12], clause 11.4.2. | 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 | 7 |
4,213 | 6.6 SINR related measurements | a) This measurement provides the distribution of RS-SINR received by eNodeB from UEs in the cell. The periodical UE measurement reports towards all of the UEs need to be triggered by eNodeB in the measured cell (See in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [18]). b) CC. c) This measurement is obtained by incrementing the appropriate measurement bin using measured quantity value (See Table 9.1.17.1-1 in TS 36.133[ Evolved Universal Terrestrial Radio Access (E-UTRA); Requirements for support of radio resource management ] [19]) when a RS-SINR value is reported by a UE when rs-sinr-Result is used for MeasResults IE as configured by MeasurementReport configurations as defined in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [18]. d) A set of integer. e) MR.RSSINR.BinX where X represents the range of Measured quantity SS-SINR value (-23 to 40 dB with 0.5 dB resolution) NOTE: Number of bins and the range for each bin is left to implementation. f) EUtranCellTDD EUtranCellFDD 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 | 6.6 |
4,214 | 6.7.4 AS security mode command procedure | The AS SMC procedure is for RRC and UP security algorithms negotiation and RRC security activation. for the gNB/ng-eNB. AS SMC procedure can be triggered to establish a secure RRC signalling-only connection during UE registration or PDU session establishment as specified in TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [34] and TS 23.502[ Procedures for the 5G System (5GS) ] [8]. The activation of UP security is as described in clause 6.6.2. AS SMC procedure consists of a roundtrip of messages between gNB/ng-eNB and UE. The gNB/ng-eNB sends the AS security mode command to the UE and the UE replies with the AS security mode complete message. See Figure 6.7.4-1. The AS security mode command message sent from gNB/ng-eNB to UE shall contain the selected RRC and UP encryption and integrity algorithms. This AS security mode command message shall be integrity protected with RRC integrity key based on the current KgNB. The AS security mode complete message from UE to gNB/ng-eNB shall be integrity protected with the selected RRC algorithm indicated in the AS security mode command message and RRC integrity key based on the current KgNB. RRC downlink ciphering (encryption) at the gNB/ng-eNB shall start after sending the AS security mode command message. RRC uplink deciphering (decryption) at the gNB/ng-eNB shall start after receiving and successful verification of the AS security mode complete message. RRC uplink ciphering (encryption) at the UE shall start after sending the AS security mode complete message. RRC downlink deciphering (decryption) at the UE shall start after receiving and successful verification of the AS security mode command message. If any control of the AS security mode command is not successful in the UE, the UE shall reply with an unprotected security mode failure message (see TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [22]). Ciphering and integrity protection of UP downlink and uplink, at the UE and the gNB/ng-eNB, shall start as defined by clause 6.6.2. AS SMC shall be used only during an initial context setup between the UE and the gNB/ng-eNB (i.e., to activate an initial KgNB at RRC_IDLE to RRC_CONNECTED state transition). NOTE: Derivation of a KgNB at RRC_IDLE to RRC_CONNECTED state ensures that AS SMC establishes a fresh KgNB. Consequently, the PDCP COUNTs can be reset. Figure 6.7.4-1: AS Security Mode Command Procedure | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.7.4 |
4,215 | 5.3.1.2 AS Security | AS security comprises of the integrity protection and ciphering of RRC signalling (SRBs) and user data (DRBs). RRC handles the configuration of the AS security parameters which are part of the AS configuration: the integrity protection algorithm, the ciphering algorithm, if integrity protection and/or ciphering is enabled for a DRB and two parameters, namely the keySetChangeIndicator and the nextHopChainingCount, which are used by the UE to determine the AS security keys upon reconfiguration with sync (with key change), connection re-establishment and/or connection resume. The integrity protection algorithm is common for SRB1, SRB2, SRB3 (if configured), SRB4 (if configured), SRB5 (if configured) and DRBs configured with integrity protection, with the same keyToUse value. The ciphering algorithm is common for SRB1, SRB2, SRB3 (if configured), SRB4 (if configured), SRB5 (if configured) and DRBs configured with the same keyToUse value. Neither integrity protection nor ciphering applies for SRB0. NOTE 0: All DRBs related to the same PDU session have the same enable/disable setting for ciphering and the same enable/disable setting for integrity protection, as specified in TS 33.501[ Security architecture and procedures for 5G System ] [11]. RRC integrity protection and ciphering are always activated together, i.e. in one message/procedure. RRC integrity protection and ciphering for SRBs are never de-activated. However, it is possible to switch to a 'NULL' ciphering algorithm (nea0). The 'NULL' integrity protection algorithm (nia0) is used only for SRBs and for the UE in limited service mode, see TS 33.501[ Security architecture and procedures for 5G System ] [11] and when used for SRBs, integrity protection is disabled for DRBs. In case the ′NULL' integrity protection algorithm is used, 'NULL' ciphering algorithm is also used. NOTE 1: Lower layers discard RRC messages for which the integrity protection check has failed and indicate the integrity protection verification check failure to RRC. The AS applies four different security keys: one for the integrity protection of RRC signalling (KRRCint), one for the ciphering of RRC signalling (KRRCenc), one for integrity protection of user data (KUPint) and one for the ciphering of user data (KUPenc). All four AS keys are derived from the KgNB key. The KgNB key is based on the KAMF key (as specified in TS 33.501[ Security architecture and procedures for 5G System ] [11]), which is handled by upper layers. The integrity protection and ciphering algorithms can only be changed with reconfiguration with sync. The AS keys (KgNB, KRRCint, KRRCenc, KUPint and KUPenc) change upon reconfiguration with sync (if masterKeyUpdate is included), and upon connection re-establishment and connection resume. For each radio bearer an independent counter (COUNT, as specified in TS 38.323[ NR; Packet Data Convergence Protocol (PDCP) specification ] [5]) is maintained for each direction. For each radio bearer, the COUNT is used as input for ciphering and integrity protection. It is not allowed to use the same COUNT value more than once for a given security key. As specified in TS 33.501[ Security architecture and procedures for 5G System ] clause 6.9.4.1 [11], the network is responsible for avoiding reuse of the COUNT with the same RB identity and with the same key, e.g. due to the transfer of large volumes of data, release and establishment of new RBs, and multiple termination point changes for RLC-UM bearers and multiple termination point changes for RLC-AM bearer with SN terminated PDCP re-establishment (COUNT reset) due to SN only full configuration whilst the key stream inputs (i.e. bearer ID, security key) at MN have not been updated. In order to avoid such re-use, the network may e.g. use different RB identities for RB establishments, change the AS security key, or an RRC_CONNECTED to RRC_IDLE/RRC_INACTIVE and then to RRC_CONNECTED transition. In order to limit the signalling overhead, individual messages/ packets include a short sequence number (PDCP SN, as specified in TS 38.323[ NR; Packet Data Convergence Protocol (PDCP) specification ] [5]). In addition, an overflow counter mechanism is used: the hyper frame number (HFN, as specified in TS 38.323[ NR; Packet Data Convergence Protocol (PDCP) specification ] [5]). The HFN needs to be synchronized between the UE and the network. For each SRB, the value provided by RRC to lower layers to derive the 5-bit BEARER parameter used as input for ciphering and for integrity protection is the value of the corresponding srb-Identity with the MSBs padded with zeroes. For a UE provided with an sk-counter, keyToUse indicates whether the UE uses the master key (KgNB) or the secondary key (S-KeNB or S-KgNB) for a particular DRB. The secondary key is derived from the master key and sk-Counter, as defined in TS 33.501[ Security architecture and procedures for 5G System ] [11]. Whenever there is a need to refresh the secondary key, e.g. upon change of MN with KgNB change or to avoid COUNT reuse, the security key update is used (see 5.3.5.7). When the UE is in NR-DC, the network may provide a UE configured with an SCG with an sk-Counter even when no DRB is setup using the secondary key (S-KgNB) in order to allow the configuration of SRB3. The network can also provide the UE with an sk-Counter, even if no SCG is configured, when using SN terminated MCG bearers. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.1.2 |
4,216 | 7.7.10 Repeated Information Elements | An Information Element is repeated if there is more than one IE with the same IE Type and Instance in the scope of the GTP message (scope of the grouped IE). Such an IE is a member in a list. If an information element is repeated in a GTP signalling message in which repetition of the information element is not specified, only the contents of the information element appearing first shall be handled and all subsequent repetitions of the information element shall be ignored. When repetition of information elements is specified, only the contents of specified repeated information elements shall be handled and all subsequent repetitions of the information element shall be ignored. | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 7.7.10 |
4,217 | 9.3.1 Scrambling | The block of bits , where is the number of bits transmitted on the physical sidelink shared channel in one subframe shall be scrambled according to clause 5.3.1. The scrambling sequence generator shall be initialised with at the start of every PSSCH subframe where - for sidelink transmission modes 1 and 2, is destination identity obtained from the sidelink control channel, and - for sidelink transmission modes 3 and 4, with and given by clause 5.1.1 in [3] equals the decimal representation of CRC on the PSCCH transmitted in the same subframe as the PSSCH. | 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 | 9.3.1 |
4,218 | 15.5 Addressing and identification for Bootstrapping MBMS Service Announcement | The UE needs a Service Announcement Fully Qualified Domain Name (FQDN) to bootstrap MBMS Service Announcement as specified in 3GPP TS 26.346[ Multimedia Broadcast/Multicast Service (MBMS); Protocols and codecs ] [105]. The Service Announcement FQDN is composed of six labels. The last three labels shall be "pub.3gppnetwork.org". The second and third labels together shall uniquely identify the PLMN. The first label shall be "mbmsbs". The Service Announcement FQDN is derived from the IMSI or Visited PLMN Identity as follows: "mbmsbs.mnc<MNC>.mcc<MCC>.pub.3gppnetwork.org" where: "mnc" and "mcc" serve as invariable identifiers for the following digits. - When using the Service Announcement FQDN in a visited network, the <MNC> and <MCC> shall be derived from the visited PLMN Identity as defined in clause 12.1. - When using the Service Announcement FQDN in the home network, the <MNC> and <MCC> shall be derived from the components of the IMSI as defined in clause 2.2. In order to guarantee inter-PLMN DNS translation, the <MNC> and <MCC> coding used in the "mbmsbs.mnc<MNC>.mcc<MCC>.pub.3gppnetwork.org" format of the Service Announcement 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 Service Announcement FQDN. As an example, the Service Announcement FQDN for MCC 345 and MNC 12 is coded in the DNS as: "mbmsbs.mnc012.mcc345.pub.3gppnetwork.org". | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 15.5 |
4,219 | 6.3.23 EASDF discovery and selection | Multiple instances of EASDF may be deployed in a network. NF consumers mentioned in this clause are SMF(s). The NF consumers shall utilize the NRF to discover EASDF instance(s) unless EASDF information is available by other means, e.g. locally configured on the NF consumer. The EASDF selection function in NF consumers or SCP selects an EASDF instance based on the available EASDF instances. The following factors may be considered by the NF consumer or SCP for EASDF selection: - S-NSSAI. - DNN. - the N6 IP address of the EASDF. NOTE: The IP address of the EASDF is not used for EASDF discovery. It can be used is to select an EASDF that is "IP near" to the PSA of the PDU Session. - The N6 IP address of the PSA UPF. - Location as per NF profile. - DNAI (if exist). | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 6.3.23 |
4,220 | 6.26.2 Requirements 6.26.2.1 General | The 5G system shall support 5G LAN-type service in a shared RAN configuration. The 5G system shall support 5G LAN-type service over a wide area mobile network. The 5G network shall support service continuity for 5G LAN-type service, i.e. the private communication between UEs shall not be interrupted when one or more UEs of the private communication move within the same network that provides the 5G LAN-type service. The 5G system shall support use of unlicensed as well as licensed spectrum for 5G LAN-type services. The 5G system shall enable the network operator to provide the same 5G LAN-type service to any 5G UE, regardless of whether it is connected via public base stations, indoor small base stations connected via fixed access, or via relay UEs connected to either of these two types of base stations. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.26.2 |
4,221 | – MBSMulticastConfiguration | The MBSMulticastConfiguration message contains the control information applicable for MBS multicast services transmitted via multicast MRBs for RRC_INACTIVE UEs. Signalling radio bearer: N/A RLC-SAP: UM Logical channel: multicast MCCH Direction: Network to UE MBSMulticastConfiguration message -- ASN1START -- TAG-MBSMULTICASTCONFIGURATION-START MBSMulticastConfiguration-r18 ::= SEQUENCE { criticalExtensions CHOICE { mbsMulticastConfiguration-r18 MBSMulticastConfiguration-r18-IEs, criticalExtensionsFuture SEQUENCE {} } } MBSMulticastConfiguration-r18-IEs ::= SEQUENCE { mbs-SessionInfoList-r18 MBS-SessionInfoListMulticast-r18 OPTIONAL, -- Need R mbs-NeighbourCellList-r18 MBS-NeighbourCellList-r17 OPTIONAL, -- Need S drx-ConfigPTM-List-r18 SEQUENCE (SIZE (1..maxNrofDRX-ConfigPTM-r17)) OF DRX-ConfigPTM-r17 OPTIONAL, -- Need R pdsch-ConfigMTCH-r18 PDSCH-ConfigBroadcast-r17 OPTIONAL, -- Need S mtch-SSB-MappingWindowList-r18 MTCH-SSB-MappingWindowList-r17 OPTIONAL, -- Need R thresholdMBS-List-r18 SEQUENCE (SIZE (1..maxNrofThresholdMBS-r18)) OF ThresholdMBS-r18 OPTIONAL, -- Need R lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL } ThresholdMBS-r18 ::= CHOICE { rsrp-r18 RSRP-Range, rsrq-r18 RSRQ-Range } -- TAG-MBSMULTICASTCONFIGURATION-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
4,222 | 12.2.5.2 Frequency of inclusion | How often the sender includes the load control information is implementation specific. The sender shall ensure that new/updated load control information is propagated to the target receivers within an acceptable delay, such that the purpose of the information (i.e. effective load balancing) is achieved. The sender may include the LCI IE e.g. as follows: - the sender may include Load Control Information towards a peer only when the new/changed value has not already been provided to that peer; - the sender may include the Load Control Information in each and every message (extended with LCI IE) towards the peer; - the sender may include Load Control Information periodically, i.e. include the information during a first period then cease to do so during a second period. The sender may also implement a combination of one or more of the above approaches. Besides, the sender may also decide to include the Load Control Information only in a subset of the applicable GTP-C messages. The receiver shall be prepared to receive the load control information in any of the GTP-C messages extended with an LCI IE and upon such reception, shall be able act upon the received load control information. | 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.2.5.2 |
4,223 | 5.8.2.13.1 Support for unicast traffic forwarding of a 5G VN | To enable unicast traffic forwarding in a UPF, the following applies: - The SMF provides for each 5G VN group member's N4 Session (i.e. N4 Session corresponding to PDU Session) the following N4 rules that enable the processing of packets received from this UE. - in order to detect the traffic, a PDR containing Source Interface set to "access side", and CN Tunnel Information set to PDU Session tunnel header (i.e. N3 or N9 GTP-U F-TEID); and - in order to forward the traffic, a FAR containing Destination Interface set to "5G VN internal". - The SMF provides for each 5G VN group member's N4 Session (i.e. N4 session corresponding to PDU Session) the following N4 rules that enable the processing of packets towards this UE. - in order to detect the traffic, a PDR containing Source Interface set to "5G VN internal", and Destination Address set to the IP/MAC address (es) of this 5G VN group member; and - in order to forward the traffic, a FAR containing Outer Header Creation indicating the N3/N9 tunnel information, and Destination Interface set "access side". - If N19-based forwarding is applied, the SMF configures the group-level N4 Session for processing packets received from a N19 tunnel with the following N4 rules for each N19 tunnel. - in order to detect the traffic, a PDR containing Source Interface set to "core side", and CN Tunnel Information set to N19 tunnel header (i.e. N19 GTP-U F-TEID); and - in order to forward the traffic, a FAR containing Destination Interface set to "5G VN internal". - If N19-based forwarding is applied, the SMF configures the group-level N4 Session for processing packets towards 5G VN group members anchored at other UPFs with the following N4 rules for each N19 tunnel. - in order to detect the traffic, a PDR containing Source Interface set to "5G VN internal", and Destination Address set to the IP/MAC address (es) of UEs anchored at the peer UPF of this N19 tunnel (e.g. based on the IP address range supported by the peer UPF); and - in order to forward the traffic to a 5G VN group member anchored at another UPF via the N19 tunnel, a FAR containing Outer Header Creation indicating the N19 tunnel information, Destination Interface set to "core side". - The SMF configures the group-level N4 Session for processing packets received from a 5G VN group member connected via N6 with the following N4 rules. - in order to detect the traffic, a PDR containing Source Interface set to "core side", and Source Address set to the IP/MAC address (es) of this 5G VN group member; and - in order to forward the traffic, a FAR containing Destination Interface set to "5G VN internal". - The SMF configures the group-level N4 Session for processing packets towards a 5G VN group member connected via N6 or packets towards a device residing in DN with the following N4 rules. - in order to detect the traffic, a PDR containing Source Interface set to "5G VN internal", and Destination Address set to the IP/MAC address (es) of this 5G VN group member; and - in order to forward the traffic to the 5G VN group member or device via N6, a FAR containing Destination Interface set to "core side". - The SMF shall update N4 rules for group-level N4 Session to enable correct forwarding of packets towards UE who's PSA UPF has been reallocated and address is unchanged. - The SMF may also configure the following N4 rules for the group-level N4 Session to process packets with an unknown destination address: - in order to detect the traffic, a PDR containing Source Interface set to "5G VN internal", a match-all Packet Filter, and a Precedence set to the lowest precedence value; and - in order to process the traffic, a FAR containing Destination Interface set to "core side" to route the traffic via N6 by default, or in the case of local SMF configuration that N6-based forwarding is not applied a FAR instructing the UPF to drop the traffic. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.8.2.13.1 |
4,224 | 5.5.4 eCall inactivity procedure | The eCall inactivity procedure is applicable only to a UE configured for eCall only mode as specified in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [17]. The procedure shall be started when: - the UE is in any EMM-REGISTERED substate except substates EMM-REGISTERED.PLMN-SEARCH or EMM-REGISTERED.NO-CELL-AVAILABLE; - the UE is in EMM-IDLE mode; and - one of the following conditions applies: 1) timer T3444 expires or is found to have already expired and timer T3445 is not running; 2) timer T3445 expires or is found to have already expired and timer T3444 is not running; or 3) timers T3444 and T3445 expire or are found to have already expired. The UE shall then perform the following actions: - stop other running timers (e.g. T3411, T3412); - if the UE is currently registered to EPS services only, perform a detach procedure for EPS services only; - if the UE is currently registered for both EPS services and non-EPS services, perform a combined detach procedure for EPS services and non-EPS services; - delete any GUTI, TAI list, last visited registered TAI, list of equivalent PLMNs, and eKSI; and - enter EMM-DEREGISTERED.eCALL-INACTIVE state. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.5.4 |
4,225 | 19.2.1.2 Service Provided by the BM-SC in visited PLMN | When visited and home PLMN support the same classes of MBMS user services, a visited PLMN may offer its own MBMS user services to roaming users. In this case, the authorization is done in the BM-SC in visited PLMN with the authorization information retrieved from the BM-SC in home PLMN. Then the MBMS user traffic is provided by the BM-SC in visited PLMN. Figure 29a: Activation of an MBMS multicast service in roaming scenario with service provided in the visited PLMN 1. The GGSN sends an AAR to the BM-SC in visited PLMN seeking authorizationt information for the activating roaming UE to receive data from a particular service. 2. The BM-SC in visited PLMN finds the BM-SC in home PLMN which have the authorization information for the roaming UE based on the multicast IP address, and identity of the user, and sends the AAR to it for the roaming UE to receive authorization from a particular service. 3. The authorization decision is provided from BM-SC in home PLMN in the AAA to BM-SC in visited PLMN. 4. The authorization decision, as received from BM-SC in home PLMN, is provided in the AAA to GGSN together with the APN to be used for creation of the MBMS UE Context If the AAA indicates that the roaming UE is not authorized to receive the MBMS data the process terminates with no additional message exchange. 5. The GGSN sends an AAR seeking authorization for the activating UE to BM-SC in visited PLMN. This GGSN may be different from the GGSN that receives IGMP join message. 6. The authorization decision is provided in the AAA to GGSN. | 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 | 19.2.1.2 |
4,226 | 6.6.2.3.1 Minimum requirement E-UTRA | E-UTRA Adjacent Channel Leakage power Ratio (E-UTRAACLR) is the ratio of the filtered mean power centred on the assigned channel frequency to the filtered mean power centred on an adjacent channel frequency at nominal channel spacing. The assigned E-UTRA channel power and adjacent E-UTRA channel power are measured with rectangular filters with measurement bandwidths specified in Table 6.6.2.3.1-1, Table 6.6.2.3.1-2, and Table 6.6.2.3.1-3. If the measured adjacent channel power is greater than –50dBm then the E-UTRAACLR shall be higher than the value specified in Table 6.6.2.3.1-1, Table 6.6.2.3.1-2, and Table 6.6.2.3.1-3. For a power class 2 capable UE operating on Band 41, when an IE P-max as defined in [7] of 23 dBm or lower is indicated in the cell or if the uplink/downlink configuration is 0 or 6, the requirements for power class 2 are not applicable, and the corresponding requirements for a power class 3 UE shall apply. For each supported frequency band other than Band 14 and Band 41, the UE shall: - if the UE supports a different power class than the default UE power class for the band and the supported power class enables the higher maximum output power than that of the default power class: - if the band is a TDD band whose frame configuration is 0 or 6; or - if the IE P-Max as defined in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [7] is not provided; or - if the IE P-Max as defined in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [7] is provided and set to the maximum output power of the default power class or lower; - meet all requirements for the default power class of the operating band in which the UE is operating and set its configured transmitted power as specified in sub-clause 6.2.5; - else (i.e the IE P-Max as defined in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [7] is provided and set to the higher value than the maximum output power of the default power class): - meet all requirements for the supported power class and set its configured transmitted power class as specified in sub-clause 6.2.5. Table 6.6.2.3.1-1: General requirements for E-UTRAACLR Table 6.6.2.3.1-2: Additional E-UTRAACLR requirements for Power Class 1 Table 6.6.2.3.1-3: Additional E-UTRAACLR requirements for Power Class 2 | 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.3.1 |
4,227 | 5.8.5.2 N4 Session Context | N4 Session Context is identified by an N4 Session ID. An N4 Session Context is generated by SMF and UPF respectively to store the parameters related to an N4 session, including the N4 session ID and following information (see TS 29.244[ Interface between the Control Plane and the User Plane nodes ] [65] for an exhaustive list): 1) general session related parameters such as S-NSSAI, PDU Session Type, Trace Information, APN/DNN, ATSSS Control Information; 2) the PDRs, URRs, QERs, BAR(s), FARs, MARs used for this N4 session; 3) parameters sent to support UPF statistics. The UPF may use parameters listed above in bullets 1) (e.g. S-NSSAI) and 2) (e.g. Network Instance in PDR/FAR(s)) for determining internal UPF resources. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.8.5.2 |
4,228 | 4.4.7.1 DL cell PDCP SDU Data Volume | This measurement provides the Data Volume (amount of PDCP SDU bits) in the downlink delivered from PDCP layer to RLC layer. The measurement is calculated per PLMN ID and per E-RAB QoS profile (QCI, ARP and GBR). The unit is Mbit. b) CC c) This measurement is obtained by counting the number of bits entering the eNodeB/RN. The measurement is performed at the PDCP SDU level. The measurement is performed per configured PLMN ID per configured DL QoS profile criteria. (See 3GPP TS 36.314[ Evolved Universal Terrestrial Radio Access (E-UTRA); Layer 2 - Measurements ] , clause 4.1.9). d) Each measurement is an integer value representing the number of bits measured in Mbits. The number of measurements is equal to the number of PLMNs multiplied by the number of QoS profiles. [Total no. of measurement instances] x [no. of filter values for all measurements] (DL and UL) ≤ 200. e) The measurement name has the form DRB.PdcpSduVolumeDl_Filter. Filter = PLMNID (1-6), QCImax (1-255), QCImin (1-255), ARPmax (1-15), ARPmin (1-15), GBR (n), where n ( ≥ 1) corresponds to an operator defined bitrate range. Example: A measurement with filter PLMN=2, QCImax=4, QCImin=2, ARPmax=10, ARPmin=1 and GBR=3 results in the measurement name: DRB.PdcpSduVolumeDl_Plmn2Qci2-4Arp1-10Gbr3. f) EUtranCellFDD EUtranCellTDD g) Valid for packet switched traffic h) EPS i) Can be used by MOP (see TS 32.130[ Telecommunication management; Network sharing; Concepts and requirements ] [22]) for cross-operator accounting in shared networks. | 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.4.7.1 |
4,229 | 6.7.1A Minimum requirement for CA | User Equipment(s) transmitting in close vicinity of each other can produce intermodulation products, which can fall into the UE, or eNode B receive band as an unwanted interfering signal. The UE intermodulation attenuation is defined by the ratio of the mean power of the wanted signal to the mean power of the intermodulation product on both component carriers when an interfering CW signal is added at a level below the wanted signal at each of the transmitter antenna port with the other antenna port(s) if any is terminated. Both the wanted signal power and the intermodulation product power are measured through rectangular filter with measurement bandwidth shown in Table 6.7.1A-1. For inter-band carrier aggregation with one component carrier per operating band and the uplink active in two E-UTRA bands, the requirement is specified in Table 6.7.1-1 which shall apply on each component carrier with both component carriers active. For intra-band contiguous carrier aggregation the requirement of transmitting intermodulation is specified in Table 6.7.1A-1. Table 6.7.1A-1: Transmit Intermodulation For combinations of intra-band and inter-band carrier aggregation with three uplink component carriers (up to two contiguously aggregated carriers per band) transmit intermodulations is defined as follows. For the E-UTRA band supporting one component carrier the requirement specified in Table 6.7.1-1 apply. For the E-UTRA band supporting two contiguous component carriers the requirements specified in Table 6.7.1A-1 apply. | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.7.1A |
4,230 | 16.4.7.1 Presence of the 3GPP Vendor-Specific attribute in RADIUS messages. | Table 7: List of the 3GPP Vendor-Specific sub-attributes The information represented by some of the Sgi sub-attributes may not be available to the P-GW depending on the UE’s radio access and the S5/S8 protocol type (GTP or PMIP). For example, the P-GW will be aware of the User Location Info (e.g. TAI) if the user is in LTE access and GTP based S5/S8 is used. However, such information is not passed to the P-GW when PMIP based S5/S8 is utilised. In such scenarios, if a sub-attribute is configured in the P-GW to be transferred to the RADIUS AAA server, but the information in the P-GW is not up to date or not available; the P-GW shall not send the corresponding sub-attribute, unless otherwise stated in the following subclause where the encoding of each sub-attribute is specified. | 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 | 16.4.7.1 |
4,231 | 4.3.22 UE Power Saving Mode | A UE may adopt a PSM that is described in TS 23.682[ Architecture enhancements to facilitate communications with packet data networks and applications ] [74]. If a UE is capable of adopting a PSM and it wants to use the PSM it shall request an Active Time value and may request a Periodic TAU/RAU Timer value during every Attach and TAU procedures, which are handled as described in TS 23.682[ Architecture enhancements to facilitate communications with packet data networks and applications ] [74]. The UE shall not request a Periodic TAU/RAU Timer value if it is not requesting an Active Time value. The network shall not allocate an Active Time value if the UE has not requested it. PSM has no support in the CS domain on the network side. NOTE 1: When the PSM is activated the UE might not be available for paging of Mobile Terminated CS services even though the UE is registered in the CS domain. NOTE 2: The Attach and TAU procedures of this specification are not showing the details of the Periodic TAU Time and Active Time negotiation, i.e. are not showing the related IEs. If the network allocates an Active Time value, the UE and the MME starts the Active timer (see clause 4.3.5.2) with the Active Time value allocated by the network when transitioning from ECM_CONNECTED to ECM_IDLE. The UE shall stop the Active timer, if running, when a transition to ECM_CONNECTED mode is made. When the Active timer expires, the UE deactivates its Access Stratrum functions and enters PSM. In PSM, due to deactivation of Access Stratum functions, the UE stops all idle mode procedures, but continues to run any NAS timers that may apply, e.g. the periodic TAU timer. The UE shall resume Access Stratum functions and idle mode procedures before the periodic TAU timer expires for performing the periodic TAU procedure as applicable. The UE may resume idle mode procedures and Access Stratum functions any time while in PSM, e.g. for mobile originated communications. Any timers and conditions that remain valid during power-off, e.g. for NAS-level back-off, apply in the same way during PSM. When the Active timer expires for the UE, the MME knows that the UE entered PSM and is not available for paging. The MME handles availability for paging as detailed in clause 4.3.5.2. On UE side the PSM complies with some substates of EMM_REGISTERED, as specified in TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [46]. The MME considers the UE to be EMM_REGISTERED, but not reachable. The UE's Access Stratum functions are considered as deactivated during PSM. For mobile terminated data while a UE is in PSM, the functions for High latency communication may be used as described in clause 4.3.17.7. When the UE has bearers for emergency services, the UE shall not apply PSM. When the UE is attached for RLOS services, the UE shall not apply PSM. | 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.22 |
4,232 | 6.25.1 Description | Non-public networks are intended for the sole use of a private entity such as an enterprise, and can be deployed in a variety of configurations, utilising both virtual and physical elements. Specifically, they can be deployed as completely standalone networks, they can be hosted by a PLMN, or they can be offered as a slice of a PLMN. In any of these deployment options, it is expected that unauthorized UEs, those that are not associated with the enterprise, will not attempt to access the non-public network, which could result in resources being used to reject that UE and thereby not be available for the UEs of the enterprise. It is also expected that UEs of the enterprise will not attempt to access a network they are not authorized to access. For example, some enterprise UEs can be restricted to only access the non-public network of the enterprise, even if PLMN coverage is available in the same geographic area. Other enterprise UEs can access both a non-public network and a PLMN where specifically allowed. In addition to the requirements in this section, all requirements and KPIs in other sections of TS 22.261[ Service requirements for the 5G system ] , that are not exclusively for PLMNs (i.e. explicitly using the term PLMN) also apply to (i.e. are in scope of) non-public networks, except the requirements in sections 5.1, 6.2.4 and 6.3.2.2. However, hereby it is important to realize that requirements and features are optional to be supported by a non-public network, since non-public network deployments can include different subsets of 5G system requirements and services described in the sections of TS 22.261[ Service requirements for the 5G system ] . The deployment choices are dependent on verticals needs and regulation. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.25.1 |
4,233 | 14.1 Services provided by AUSF 14.1.1 General | The AUSF provides UE authentication service to the requester NF by Nausf_UEAuthentication. For AKA based authentication, this operation can be also used to recover from synchronization failure situations. Clause 14.1.2 describes the Nausf_UEAuthentication service. The service operations listed here are used in procedures that are described in clause 6 of the present document and in TS 33.503[ Security Aspects of Proximity based Services (ProSe) in the 5G System (5GS) ] [109]. Clause 14.1.3 describes the Nausf_SoRProtection service used in procedures that are described in clause 6.14 of the present document. Clause 14.1.4 describes the Nausf_UPUProtection service used in procedures that are described in clause 6.15 of the present document. Since AUSF is completely security-related, all service operations are described in the present document. TS 23.501[ System architecture for the 5G System (5GS) ] [2], clause 7.2.7, only lists the services and TS 23.502[ Procedures for the 5G System (5GS) ] [8], clause 5.2.10, provides the reference to the present document. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 14.1 |
4,234 | 6.3.4.10 Consecutive subframe and subslot TTI or consecutive slot and subslot TTI time mask | The consecutive subframe and subslot boundary time mask or consecutive slot and subslot boundary time mask defines the observation period between the slot or subframe and the subslot. There are no additional requirements on UE transmit power beyond that which is required in subclause 6.2.2 and subclause 6.6.2.3 Figure 6.3.4.10-1: Subframe TTI and subslot TTI boundary with SRS in last subframe TTI symbol and Reference Symbol in first subslot TTI symbol Figure 6.3.4.10-2: Subframe TTI and subslot TTI boundary with SRS in last subframe TTI symbol and data Symbol in first subslot TTI symbol When the last symbol of the Subframe or slot is not SRS then the transient period is placed in the Subframe or Slot. Figure 6.3.4.10-3: subframe TTI and subslot TTI boundary | 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.3.4.10 |
4,235 | 10.5.6.21 NBIFOM container | The purpose of the NBIFOM container information element is to transfer parameters associated with the network-based IP flow mobility (NBIFOM). The NBIFOM container is a type 4 information element with a minimum length of 3 octets and a maximum length of 257 octets. The NBIFOM container information element is coded as shown in figure 10.5.6.21-1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.6.21-1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Figure 10.5.6.21-1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : NBIFOM container information element Table 10.5.6.21-1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : NBIFOM container information element | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 10.5.6.21 |
4,236 | 4.7.1.2a.2 Integrity checking of GMM signalling messages in the MS | Except the messages listed below, no GMM signalling messages shall be processed by the receiving GMM entity in the MS or forwarded to the SM entity, unless the use of integrity protection has been successfully negotiated: - GMM messages: - IDENTITY REQUEST (only if the requested identification parameter is IMSI) - ATTACH REJECT (if the cause is not #25) - AUTHENTICATION AND CIPHERING REJECT - ROUTING AREA UPDATE REJECT (if the cause is not #25) - DETACH ACCEPT (for non power-off) NOTE: These messages are accepted by the MS without integrity protection, as in certain situations they are sent by the network before integrity protection can be activated. All SM messages shall be integrity protected. Once the integrity protection has been successfully negotiated, the receiving GMM or SM entity in the MS shall not process any GMM signalling messages unless they have been successfully integrity checked by the LLC layer. If GMM signalling messages, having not successfully passed the integrity check, are received, then the LLC layer in the MS discards that message. The processing of the AUTHENTICATION AND CIPHERING REQUEST message, at authentication, that has not successfully passed the integrity check at GMM layer is specified in subclause 4.7.7.2. If any GMM or SM signalling message is received without integrity protection even though integrity protection has been successfully negotiated, then the GMM layer shall discard this 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.1.2a.2 |
4,237 | 6.8.7.2 GSM security context | A GSM security context in GSM BSS can be either: - Established for a UMTS subscriber A GSM security context for a UMTS subscriber is established in case the user has a ME not capable of UMTS AKA, where intersystem change to UTRAN is not possible, or in case the user has a R99+ ME but the SGSN is R98-, where intersystem change to UTRAN implies a change to a R99+ SGSN. As result, in case of intersystem change to a UTRAN controlled by another R99+ SGSN, the initial R98- SGSN sends the 64-bit GSM cipher key Kc agreed during the latest GSM AKA procedure to the new SGSN controlling the target RNC. Since the new R99+ SGSN has no indication of whether the subscriber is GSM or UMTS, a R99+ SGSN shall perform a new UMTS AKA when receiving the 64-bit Kc from a R98- SGSN. A UMTS security context using fresh quintets is then established between the R99+ SGSN and the USIM. The new SGSN becomes the new anchor point for the service. At the user side, new keys shall be agreed during the new UMTS AKA initiated by the R99+ SGSN. - Established for a GSM subscriber Handover from GSM BSS to UTRAN for GSM subscriber is only possible with R99+ ME. At the network side, three cases are distinguished: a) In case of an intersystem change to a UTRAN controlled by the same SGSN, the SGSN derives UMTS cipher/integrity keys CK and IK from the 64-bit GSM cipher key Kc (using the conversion functions c4 and c5) agreed during the latest GSM AKA procedure and sends them to the target RNC. b) In case of an intersystem change from a R99+ SGSN to a UTRAN controlled by another SGSN, the initial SGSN sends the 64-bit GSM cipher key Kc agreed during the latest GSM AKA procedure to the (new) SGSN controlling the target RNC. The new SGSN becomes the new anchor point for the service. The new SGSN stores the 64-bit GSM cipher key Kc and derives the UMTS cipher/integrity keys CK and IK which are then forwarded to the target RNC. c) In case of an intersystem change from an R98-SGSN to a UTRAN controlled by another SGSN, the initial SGSN sends the 64-bit GSM cipher key Kc agreed during the latest GSM AKA procedure to the (new) SGSN controlling the target RNC. The new SGSN becomes the new anchor point for the service. To ensure use of UMTS keys for a possible UMTS subscriber (superfluous in this case), a R99+ SGSN will perform a new AKA when a R99+ ME is coming from a R98-SGSN. At the user side, in all cases, the ME derives the UMTS cipher/integrity keys CK and IK from the GSM cipher key Kc (using the conversion functions c4 and c5) received from the SIM during the latest GSM AKA procedure and applies them. In case c) these keys will be over-written with a new CK, IK pair due to the new AKA. | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | 6.8.7.2 |
4,238 | 5.4.5.2.4 UE-initiated NAS transport of messages not accepted by the network | Upon reception of an UL NAS TRANSPORT message, if the Payload container type IE is set to "N1 SM information" and the UE is not configured for high priority access in selected PLMN or SNPN, and: a) if the Request type IE is set to "initial request", "existing PDU session" or "MA PDU request"; 1) DNN based congestion control is activated for the DNN included in the UL NAS TRANSPORT message, or DNN based congestion control is activated for the selected DNN in case of no DNN included in the UL NAS TRANSPORT message, e.g. configured by operation and maintenance, the AMF shall send back to the UE the 5GSM message which was not forwarded, a back-off timer value and 5GMM cause #22 "congestion" as specified in subclause 5.4.5.3.1 case f); 2) S-NSSAI and DNN based congestion control is activated for the S-NSSAI and DNN included in the UL NAS TRANSPORT message, or S-NSSAI and DNN based congestion control is activated for the S-NSSAI included in the UL NAS TRANSPORT message and the selected DNN in case of no DNN included in the UL NAS TRANSPORT message, or S-NSSAI and DNN based congestion control is activated for the selected S-NSSAI in case of no S-NSSAI included in the UL NAS TRANSPORT message and the DNN included in the UL NAS TRANSPORT message, or S-NSSAI and DNN based congestion control is activated for the selected S-NSSAI and the selected DNN in case of no S-NSSAI and no DNN included in the UL NAS TRANSPORT message, e.g. configured by operation and maintenance, the AMF shall send back to the UE the 5GSM message which was not forwarded, a back-off timer value and 5GMM cause #67 "insufficient resources for specific slice and DNN" as specified in subclause 5.4.5.3.1 case f); 3) S-NSSAI only based congestion control is activated for the S-NSSAI included in the UL NAS TRANSPORT message, or S-NSSAI based congestion control is activated for the selected S-NSSAI in case of no S-NSSAI included in the UL NAS TRANSPORT message, e.g. configured by operation and maintenance, the AMF shall send back to the UE the 5GSM message which was not forwarded, a back-off timer value and 5GMM cause #69 "insufficient resources for specific slice" as specified in subclause 5.4.5.3.1 case f); b) void; c) if the Request type IE is set to "modification request" and the PDU session is not an emergency PDU session; 1) DNN based congestion control is activated for the stored DNN, e.g. configured by operation and maintenance, the AMF shall send back to the UE the 5GSM message which was not forwarded, a back-off timer value and 5GMM cause #22 "congestion" as specified in subclause 5.4.5.3.1 case f); 2) S-NSSAI and DNN based congestion control is activated for the stored S-NSSAI and DNN, e.g. configured by operation and maintenance, the AMF shall send back to the UE the 5GSM message which was not forwarded, a back-off timer value and 5GMM cause #67 "insufficient resources for specific slice and DNN" as specified in subclause 5.4.5.3.1 case f); 3) S-NSSAI only based congestion control is activated for the stored S-NSSAI, e.g. configured by operation and maintenance, the AMF shall send back to the UE the 5GSM message which was not forwarded, a back-off timer value and 5GMM cause #69 "insufficient resources for specific slice" as specified in subclause 5.4.5.3.1 case f); or d) the timer T3447 is running and the UE does not support service gap control: 1) the Request type IE: i) is set to "initial request"; ii) is set to "existing PDU session"; or iii) is set to "modification request" and the PDU session being modified is a non-emergency PDU session; 2) the current NAS signalling connection was not triggered by paging; and 3) mobile terminated signalling has not been sent or no user-plane resources have been established for any PDU session after the establishment of the current NAS signalling connection, the AMF shall send back to the UE the message which was not forwarded, send the 5GMM cause #22 "Congestion", and may include a back-off timer set to the remaining time of the timer T3447 as specified in subclause 5.4.5.3.1 case f). Upon reception of a UL NAS TRANSPORT message, if the Payload container type IE is set to "N1 SM information", the Request type IE is set to "initial request", "existing PDU session" or "MA PDU request", and the AMF determines that the PLMN's maximum number of PDU sessions has already been reached for the UE, the AMF shall send back to the UE the 5GSM message which was not forwarded and 5GMM cause #65 "maximum number of PDU sessions reached" as specified in subclause 5.4.5.3.1 case h). Upon reception of a UL NAS TRANSPORT message, if the Payload container type IE is set to "N1 SM information", the Request type IE is set to "initial request", and a) the UE is in NB-N1 mode; b) the UE has indicated preference for user plane CIoT 5GS optimization; c) the network accepted the use of user plane CIoT 5GS optimization; and d) the AMF determines that there are user-plane resources established for a number of PDU sessions that is equal to the UE' s maximum number of supported user-plane resources (see 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8]), the AMF shall either: a) send back to the UE the message which was not forwarded as specified in in subclause 5.4.5.3.1 case h1); or b) proceed with the PDU session establishment and include the Control Plane CIoT 5GS Optimisation indication or Control Plane Only indicator to the SMF. Upon reception of a UL NAS TRANSPORT message, if the Payload container type IE is set to "N1 SM information", the Request type IE is set to "initial request", and a) the UE does not support S-NSSAI location validity information; b) the S-NSSAI is subject to NS-AoS; and c) the AMF determines that the UE is not in the NS-AoS, the AMF may send back to the UE the message which was not forwarded as specified in subclause 5.4.5.3.1 case h6), include the 5GMM cause #69 "insufficient resources for specific slice", and include a back-off timer. Upon reception of an UL NAS TRANSPORT message, if the Payload container type IE is set to "CIoT user data container", the UE is not configured for high priority access in selected PLMN, and: a) the timer T3447 is running and the UE does not support service gap control; b) the current NAS signalling connection was not triggered by paging; and c) mobile terminated signalling has not been sent or no user-plane resources have been established for any PDU session after the establishment of the current NAS signalling connection; the AMF shall send back to the UE the CIoT user data which was not forwarded, send the 5GMM cause #22 "Congestion", and include a back-off timer set to the remaining time of the timer T3447 as specified in subclause 5.4.5.3.1 case l2). Upon reception of a UL NAS TRANSPORT message, if the Payload container type IE is set to "N1 SM information", the Request type IE is set to "existing PDU session", and a) the UE is in NB-N1 mode; b) the UE has indicated preference for user plane CIoT 5GS optimization; c) the network accepted the use of user plane CIoT 5GS optimization; and d) the AMF determines that there are user-plane resources established for a number of PDU sessions that equals to the UE's maximum number of supported user-plane resources (see 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8]), the AMF shall send back to the UE the message which was not forwarded as specified in in subclause 5.4.5.3.1 case h1). Upon reception of an UL NAS TRANSPORT message, if the Payload container type IE is set to "N1 SM information", the Request type IE is set to "initial request" or "modification request", the associated S-NSSAI that the AMF determined through the S-NSSAI IE or the PDU session ID IE is an S-NSSAI for which the AMF is performing NSSAA, and the AMF determines to not forward the 5GSM message to the SMF based on local policy, the AMF shall send back to the UE the 5GSM message which was not forwarded as specified in subclause 5.4.5.3.1 case h2). Upon reception of an UL NAS TRANSPORT message, if the Payload container type IE is set to "SMS", "LTE Positioning Protocol (LPP) message container" or "UPP-CMI container" or "SLPP message container", the UE is not configured for high priority access in selected PLMN, and: a) the timer T3447 is running and the UE does not support service gap control; b) the current NAS signalling connection was not triggered by paging; and c) mobile terminated signalling has not been sent or no user-plane resources have been established for any PDU session after the establishment of the current NAS signalling connection; the AMF shall abort the procedure. NOTE 1: In this state the NAS signalling connection can be released by the network. Upon reception of an UL NAS TRANSPORT message, if the Payload container type IE is set to "N1 SM information", the Request type IE is set to "initial request", and: a) the determined DNN, S-NSSAI or both DNN and S-NSSAI are identified for UAS services; and b) the UE is marked in the UE's 5GMM context that it is not allowed to request UAS services; the AMF shall send back to the UE the 5GSM message which was not forwarded as specified in subclause 5.4.5.3.1 case h4). NOTE 2: The UE marked in the UE's 5GMM context as not allowed to request UAS services happens in the case that the UUAA-MM procedure needs to be performed during the registration procedure according to operator policy. | 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.4 |
4,239 | 5.37.2 Policy control enhancements to support multi-modal services | A multi-modal service is a communication service that consists of several data flows that relate to each other and that are subject to application coordination. The data flows can transfer different types of data (for example audio, video, positioning, haptic data) and may come from different sources(e.g. a single UE, a single device or multiple devices connected to the single UE, or multiple UEs). For the single UE case, it is expected that those data flows are closely related and require strong application coordination for the proper execution of the multi-modal application and therefore, all those data flows are transmitted in a single PDU session. The Nnef_AFsessionWithQoS service allows the AF to provide, at the same time, for each data flow that belongs to the multi-modal service, a Multi-modal Service ID, the service requirements and the QoS monitoring requirements: - The Multi-modal Service ID is an explicit indication that data flows are related to a multi-modal service. The PCF may use this information to derive the correct PCC rules and to apply appropriate QoS policies for the data flows that are part of a specific multi-modal application. - The AF may provide QoS monitoring requirements for data flows associated to a multi-modal service to the PCF . The PCF generates the authorized QoS Monitoring policy for each data flow. NOTE: In order to start the QoS monitoring for the data flows associated to a multi-modal service within a certain period of time, the PCF needs to receive the QoS monitoring requirements for those data flows from AF within a single request or, in case of multiple requests, within a short period of time. In addition to the features that are provided for the case that the data flows are associated with a single UE, the following features are provided for the case where the data flows are associated with more than one UE: - The same DNN/S-NSSAI combination for the multi-modal service should be selected by each of the involved UEs. The URSP Rule evaluation framework is used to ensure that the same DNN/S-NSSAI is selected. - The AF should use the same Multi-modal Service ID in the interactions with the PCF(s) for all the involved UEs that relate to a multi-modal service. The PCF may take this information into account (e.g. to apply a specific QoS policy) when processing each AF request independently. The data flows contribute to the service experience, but are still valid stand-alone, as they are transmitted over separate PDU Sessions to/from the involved UEs. - If multiple PCFs are involved, the PCFs take policy decisions according to the input provided by the AF. There is no support for policy coordination among the multiple PCFs in this Release of the specification. Policy decisions are taken by each PCF separately on a per PDU Session basis. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.37.2 |
4,240 | 5.5.1.2.4 Initial registration accepted by the network | During a registration procedure with 5GS registration type IE set to "emergency registration", the AMF shall not check for mobility and access restrictions, regional restrictions or subscription restrictions, or CAG restrictions when processing the REGISTRATION REQUEST message. If the initial registration request is accepted by the network, the AMF shall send a REGISTRATION ACCEPT message to the UE. NOTE 0: If the AMF receives the initial registration request over non-3GPP access and detects that the N3IWF used by the UE is compatible with only part of the allowed NSSAI and the UE has not indicated its support for slice-based N3IWF selection in the REGISTRATION REQUEST message, the AMF accepts the initial registration request. NOTE 0A: If the AMF receives the initial registration request over non-3GPP access and detects that the TNGF used by the UE is compatible with only part of the allowed NSSAI and the UE has not indicated its support for slice-based TNGF selection in the REGISTRATION REQUEST message, the AMF accepts the initial registration request. For each of the information elements: 5GMM capability, S1 UE network capability, and UE security capability, the AMF shall store all octets received from the UE in the REGISTRATION REQUEST message, up to the maximum length defined for the respective information element. NOTE 1: This information is forwarded to the new AMF during inter-AMF handover or to the new MME during inter-system handover to S1 mode. The AMF shall assign and include a TAI list as a registration area the UE is registered to in the REGISTRATION ACCEPT message. The AMF shall not assign a TAI list containing both tracking areas in NB-N1 mode and tracking areas not in NB-N1 mode. The UE, upon receiving a REGISTRATION ACCEPT message, shall delete its old TAI list and store the received TAI list. If the REGISTRATION REQUEST message was received over non-3GPP access, the AMF shall include a single TAI in the TAI list. NOTE 2: For non-3GPP access, the operator can allocate a TAI per N3IWF, TNGF, TWIF or W-AGF. Each N3IWF, TNGF, TWIF or W-AGF is locally configured with a TAI. Each N3IWF, TNGF, TWIF or W-AGF can be configured with its own TAI value, or with the same TAI value as other N3IWFs, TNGFs, TWIFs or W-AGFs. NOTE 3: When assigning the TAI list, the AMF can take into account the eNodeB's capability of support of CIoT 5GS optimization. The AMF may include service area restrictions in the Service area list IE in the REGISTRATION ACCEPT message. The UE, upon receiving a REGISTRATION ACCEPT message with the service area restrictions shall act as described in subclause 5.3.5. The AMF may also include a list of equivalent PLMNs in the REGISTRATION ACCEPT message. Each entry in the list contains a PLMN code (MCC+MNC). The UE shall store the list as provided by the network, and if the initial registration procedure is not for emergency services, the UE shall remove from the list any PLMN code that is already in the forbidden PLMN list as specified in subclause 5.3.13A. In addition, the UE shall add to the stored list the PLMN code of the registered PLMN that sent the list. The UE shall replace the stored list on each receipt of the REGISTRATION ACCEPT message. If the REGISTRATION ACCEPT message does not contain a list, then the UE shall delete the stored list. The AMF of a PLMN shall not include a list of equivalent SNPNs. If the ESI bit of the 5GMM capability IE of the REGISTRATION REQUEST message is set to "equivalent SNPNs supported", the AMF of a SNPN may include a list of equivalent SNPNs in the REGISTRATION ACCEPT message. If the initial registration request is for onboarding services in SNPN, the AMF shall not include a list of equivalent SNPNs in the REGISTRATION ACCEPT message. Each entry in the list contains an SNPN identity. The UE shall store the list as provided by the network. If the initial registration procedure is not for emergency services and is not the initial registration for onboarding services in SNPN, the UE shall remove from the list any SNPN identity that is already in: - the "permanently forbidden SNPNs" list or the "temporarily forbidden SNPNs" list, if the SNPN was not selected according to subclause 4.9.3.1.1 bullet a0) and subclause 4.9.3.2.1 bullet a0) of 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]; or - the "permanently forbidden SNPNs for access for localized services in SNPN" list or the "temporarily forbidden SNPNs for access for localized services in SNPN" list, if the SNPN was selected according to subclause 4.9.3.1.1 bullet a0) or subclause 4.9.3.2.1 bullet a0) of 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]. The UE shall add to the stored list the SNPN identity of the registered SNPN that sent the list. The UE shall replace the stored list on each receipt of the REGISTRATION ACCEPT message. If the REGISTRATION ACCEPT message does not contain a list, then the UE shall delete the stored list. The AMF of an SNPN shall not include a list of equivalent PLMNs. NOTE 3A: If N1 mode was disabled for an SNPN due to reception of 5GMM cause #27 or #62, the UE implementation ensures that it does not register to this SNPN due to being part of the list of "equivalent SNPNs" received while registered in another SNPN. If the initial registration procedure is not for emergency services, the UE is not registered for disaster roaming services, and if the PLMN identity of the registered PLMN is a member of the forbidden PLMN list as specified in subclause 5.3.13A, any such PLMN identity shall be deleted from the corresponding list(s). If the Service area list IE is not included in the REGISTRATION ACCEPT message, any tracking area in the registered PLMN and its equivalent PLMN(s) in the registration area, or in the registered SNPN, is considered as an allowed tracking area as described in subclause 5.3.5. If the REGISTRATION REQUEST message contains the LADN indication IE, based on the LADN indication IE, UE subscription information, UE location and local configuration about LADN and: - if the LADN indication IE includes requested LADN DNNs, the UE subscribed DNN list includes the requested LADN DNNs or the wildcard DNN, and the LADN service area of the requested LADN DNN has an intersection with the current registration area, the AMF shall determine the requested LADN DNNs included in the LADN indication IE as LADN DNNs for the UE; - if no requested LADN DNNs included in the LADN indication IE and the wildcard DNN is included in the UE subscribed DNN list, the AMF shall determine the LADN DNN(s) configured in the AMF whose LADN service area has an intersection with the current registration area as LADN DNNs for the UE; or - if no requested LADN DNNs included in the LADN indication IE and the wildcard DNN is not included in the UE subscribed DNN list, or if the UE subscribed DNN list does not include any of the DNN's in the LADN indication IE, the AMF shall determine the LADN DNN(s) included in the UE subscribed DNN list whose LADN service area has an intersection with the current registration area as LADN DNNs for the UE. If the LADN indication IE is not included in the REGISTRATION REQUEST message, the AMF shall determine the LADN DNN(s) included in the UE subscribed DNN list whose service area has an intersection with the current registration area as LADN DNNs for the UE, except for the wildcard DNN included in the UE subscribed DNN list. If the UE supports WUS assistance information and the AMF supports and accepts the use of WUS assistance information for the UE, then the AMF shall determine the negotiated UE paging probability information for the UE, store it in the 5GMM context of the UE, and if the UE is not performing the initial registration for emergency services, the AMF shall include it in the Negotiated WUS assistance information IE in the REGISTRATION ACCEPT message. The AMF may consider the UE paging probability information received in the Requested WUS assistance information IE when determining the negotiated UE paging probability information for the UE. NOTE 4: Besides the UE paging probability information requested by the UE, the AMF can take local configuration or previous statistical information for the UE into account when determining the negotiated UE paging probability information for the UE. If the UE sets the NR-PSSI bit to "NR paging subgrouping supported" in the 5GMM capability IE in the REGISTRATION REQUEST message and the AMF supports and accepts the use of PEIPS assistance information for the UE, then the AMF shall determine the Paging subgroup ID for the UE, store it in the 5GMM context of the UE, and shall include it in the Negotiated PEIPS assistance information IE in the REGISTRATION ACCEPT message or in the Updated PEIPS assistance information IE in the CONFIGURATION UPDATE COMMAND message as part of the registration procedure. The AMF may consider the UE paging probability information received in the Requested PEIPS assistance information IE when determining the Paging subgroup ID for the UE. NOTE 5: Besides the UE paging probability information when provided by the UE, the AMF can also take local configuration, whether the UE is likely to receive IMS voice over PS session calls, UE mobility pattern or previous statistical information for the UE or information provided by the NG-RAN into account when determining the Paging subgroup ID for the UE. If the UE set the UN-PER bit to "unavailability period supported" in the 5GMM capability IE in the REGISTRATION REQUEST message and the AMF supports and accepts the use of unavailability period for the UE, then the AMF shall set the UN-PER bit to "unavailability period supported" in the 5GS network feature support IE in the REGISTRATION ACCEPT message. The AMF shall include the LADN information which consists of the determined LADN DNNs for the UE and LADN service area(s) available in the current registration area in the LADN information IE of the REGISTRATION ACCEPT message. If the UE has set the LADN-DS bit to "LADN per DNN and S-NSSAI supported" in the 5GMM capability IE of the REGISTRATION REQUEST message and the extended LADN information is available for the UE, the AMF shall include the extended LADN information which consists of the determined LADN DNNs for the UE, the S-NSSAIs associated with the determined LADN DNNs for the UE and in the allowed NSSAI, and LADN service area(s) available in the current registration area in the Extended LADN information IE in the Registration accept type 6 IE container IE of the REGISTRATION ACCEPT message. If: - the UE does not support LADN per DNN and S-NSSAI; - the UE is subscribed to the LADN DNN for a single S-NSSAI only; and - the AMF only has the extended LADN information; the AMF may decide to provide the LADN service area for that LADN DNN of the extended LADN information as the LADN information and include the LADN information in the LADN information IE of the CONFIGURATION UPDATE COMMAND message. NOTE 5A: If the LADN service area is configured per DNN and S-NSSAI, in order to serve the UEs that do not support LADN per DNN and S-NSSAI, it is recommended that the LADN DNN is only served by a single S-NSSAI. NOTE 5B: In case of the UE is subscribed to the LADN DNN for multiple S-NSSAIs, the AMF can treat this as no extended LADN information is available. If the UE does not support LADN per DNN and S-NSSAI and the AMF has neither the LADN information nor the extended LADN information, the AMF shall not provide any LADN information to the UE. The UE, upon receiving the REGISTRATION ACCEPT message with the LADN information, shall store the received LADN information. The UE, upon receiving the REGISTRATION ACCEPT message with the Extended LADN information, shall store the received extended LADN information. If there exists one or more LADN DNNs which are included in the LADN indication IE of the REGISTRATION REQUEST message and are not included in the LADN information IE and Extended LADN information IE in the Registration accept type 6 IE container IE of the REGISTRATION ACCEPT message, the UE considers such LADN DNNs as not available in the current registration area. The 5G-GUTI reallocation shall be part of the initial registration procedure. During the initial registration procedure, if the AMF has not allocated a new 5G-GUTI by the generic UE configuration update procedure, the AMF shall include in the REGISTRATION ACCEPT message the new assigned 5G-GUTI together with the assigned TAI list. If the UE has set the CAG bit to "CAG supported" in the 5GMM capability IE of the REGISTRATION REQUEST message and the AMF needs to update the "CAG information list" stored in the UE, the AMF shall include the CAG information list IE or the Extended CAG information list IE in the REGISTRATION ACCEPT message. NOTE 6: The "CAG information list" can be provided by the AMF and include no entry if no "CAG information list" exists in the subscription. NOTE 7: If the UE supports extended CAG information list, the CAG information list can be included either in the CAG information list IE or Extended CAG information list IE. If the UE does not support extended CAG information list, the CAG information list shall not be included in the Extended CAG information list IE. If a 5G-GUTI or the SOR transparent container IE is included in the REGISTRATION ACCEPT message, the AMF shall start timer T3550 and enter state 5GMM-COMMON-PROCEDURE-INITIATED as described in subclause 5.1.3.2.3.3. If the Operator-defined access category definitions IE, the Extended emergency number list IE, the CAG information list IE or the Extended CAG information list IE are included in the REGISTRATION ACCEPT message, the AMF shall start timer T3550 and enter state 5GMM-COMMON-PROCEDURE-INITIATED as described in subclause 5.1.3.2.3.3. If the UE has set the RCMAP bit to "Sending of REGISTRATION COMPLETE message for negotiated PEIPS assistance information supported" in the 5GMM capability IE of the REGISTRATION REQUEST message and if the Negotiated PEIPS assistance information IE is included in the REGISTRATION ACCEPT message, the AMF shall start timer T3550 and enter state 5GMM-COMMON-PROCEDURE-INITIATED as described in subclause 5.1.3.2.3.3. If the UE is not in NB-N1 mode and the UE has set the RACS bit to "RACS supported" in the 5GMM Capability IE of the REGISTRATION REQUEST message, the AMF may include either a UE radio capability ID IE or a UE radio capability ID deletion indication IE in the REGISTRATION ACCEPT message. If the UE radio capability ID IE or the UE radio capability ID deletion indication IE is included in the REGISTRATION ACCEPT message, the AMF shall start timer T3550 and enter state 5GMM-COMMON-PROCEDURE-INITIATED as described in subclause 5.1.3.2.3.3. The AMF shall include the MICO indication IE in the REGISTRATION ACCEPT message only if the MICO indication IE was included in the REGISTRATION REQUEST message, the AMF supports and accepts the use of MICO mode. If the AMF supports and accepts the use of MICO mode, the AMF may indicate "all PLMN registration area allocated" in the MICO indication IE in the REGISTRATION ACCEPT message. If "all PLMN registration area allocated" is indicated in the MICO indication IE, the AMF shall not assign and include the TAI list in the REGISTRATION ACCEPT message. If the REGISTRATION ACCEPT message included an MICO indication IE indicating "all PLMN registration area allocated", the UE shall treat all TAIs in the current PLMN as a registration area and delete its old TAI list. If "strictly periodic registration timer supported" is indicated in the MICO indication IE in the REGISTRATION REQUEST message, the AMF may indicate "strictly periodic registration timer supported" in the MICO indication IE in the REGISTRATION ACCEPT message. The AMF shall include an active time value in the T3324 IE in the REGISTRATION ACCEPT message if the UE requested an active time value in the REGISTRATION REQUEST message and the AMF accepts the use of MICO mode and the use of active time. If the AMF supports and accepts the use of MICO, and the UE included the Requested T3512 value IE in the REGISTRATION REQUEST message, then the AMF shall take into account the T3512 value requested when providing the T3512 value IE in the REGISTRATION ACCEPT message. NOTE 7A: The T3512 value assigned to the UE by AMF can be different from the T3512 value requested by the UE. AMF can take several factors into account when assigning the T3512 value, e.g. local configuration, expected UE behaviour, UE requested T3512 value, UE subscription data, network policies. The AMF shall include the T3512 value IE in the REGISTRATION ACCEPT message only if the REGISTRATION REQUEST message was sent over the 3GPP access. The AMF shall include the non-3GPP de-registration timer value IE in the REGISTRATION ACCEPT message only if the REGISTRATION REQUEST message was sent over the non-3GPP access. If the UE requests "control plane CIoT 5GS optimization" in the 5GS update type IE, indicates support of control plane CIoT 5GS optimization in the 5GMM capability IE and the AMF decides to accept the requested CIoT 5GS optimization and the registration request, the AMF shall indicate "control plane CIoT 5GS optimization supported" in the 5GS network feature support IE of the REGISTRATION ACCEPT message. The AMF may include the T3447 value IE set to the service gap time value in the REGISTRATION ACCEPT message if: - the UE has indicated support for service gap control in the REGISTRATION REQUEST message; and - a service gap time value is available in the 5GMM context. If there is a running T3447 timer in the AMF and the Follow-on request indicator is set to "Follow-on request pending" in the REGISTRATION REQUEST message, the AMF shall ignore the flag and proceed as if the flag was not received except for the following cases: a) the UE is configured for high priority access in the selected PLMN; or b) the 5GS registration type IE in the REGISTRATION REQUEST message is set to "emergency registration". If the UE has indicated support for the control plane CIoT 5GS optimizations, and the AMF decides to activate the congestion control for transport of user data via the control plane, then the AMF shall include the T3448 value IE in the REGISTRATION ACCEPT message. If: - the UE in NB-N1 mode is using control plane CIoT 5GS optimization; and - the network is configured to provide the truncated 5G-S-TMSI configuration for control plane CIoT 5GS optimizations; the AMF shall include the Truncated 5G-S-TMSI configuration IE in the REGISTRATION ACCEPT message and set the "Truncated AMF Set ID value" and the "Truncated AMF Pointer value" in the Truncated 5G-S-TMSI configuration IE based on network policies. The AMF shall start timer T3550 and enter state 5GMM-COMMON-PROCEDURE-INITIATED as described in subclause 5.1.3.2.3.3. If the UE has included the service-level device ID set to the CAA-level UAV ID in the Service-level-AA container IE of the REGISTRATION REQUEST message, and if: - the UE has a valid aerial UE subscription information; - the UUAA procedure is to be performed during the registration procedure according to operator policy; - there is no valid successful UUAA result for the UE in the UE 5GMM context; and - the REGISTRATION REQUEST message was not received over non-3GPP access, then the AMF shall initiate the UUAA-MM procedure with the UAS-NF as specified in 3GPP TS 23.256[ Support of Uncrewed Aerial Systems (UAS) connectivity, identification and tracking; Stage 2 ] [6AB] and shall include a service-level-AA pending indication in the Service-level-AA container IE of the REGISTRATION ACCEPT message. The AMF shall store in the UE 5GMM context that a UUAA procedure is pending. The AMF shall start timer T3550 and enter state 5GMM-COMMON-PROCEDURE-INITIATED as described in subclause 5.1.3.2.3.3. If the REGISTRATION REQUEST message was received over non-3GPP access, the AMF shall not initiate UUAA-MM procedure. If the UE has included the service-level device ID set to the CAA-level UAV ID in the Service-level-AA container IE of the REGISTRATION REQUEST message, and if: - the UE has a valid aerial UE subscription information; - the UUAA procedure is to be performed during the registration procedure according to operator policy; and - there is a valid successful UUAA result for the UE in the UE 5GMM context, then the AMF shall include a service-level-AA response in the Service-level-AA container IE of the REGISTRATION ACCEPT message and set the SLAR field in the service-level-AA response to "Service level authentication and authorization was successful". If the AMF determines that the UUAA-MM procedure needs to be performed for a UE, the AMF has not received the service-level device ID set to the CAA-level UAV ID in the Service-level-AA container IE of the REGISTRATION REQUEST message from the UE and the AMF decides to accept the UE to be registered for other services than UAS services based on the user's subscription data and the operator policy, the AMF shall accept the initial registration request and shall mark in the UE's 5GMM context that the UE is not allowed to request UAS services. If the UE supports MINT, the AMF may include the List of PLMNs to be used in disaster condition IE in the REGISTRATION ACCEPT message. If the UE supports MINT, the AMF may include the Disaster roaming wait range IE in the REGISTRATION ACCEPT message. If the UE supports MINT, the AMF may include the Disaster return wait range IE in the REGISTRATION ACCEPT message. NOTE 8: The AMF can determine the contents of the "list of PLMN(s) to be used in disaster condition", the value of the disaster roaming wait range and the value of the disaster return wait range based on the network local configuration. If the AMF received the list of TAIs from the satellite NG-RAN as described in 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8], and determines that, by UE subscription and operator's preferences, any but not all TAIs in the received list of TAIs is forbidden for roaming or for regional provision of service, the AMF shall include the TAI(s) in: a) the Forbidden TAI(s) for the list of "5GS forbidden tracking areas for roaming" IE; or b) the Forbidden TAI(s) for the list of "5GS forbidden tracking areas for regional provision of service" IE; or c) both; in the REGISTRATION ACCEPT message. NOTE 9: Void. If the UE has set the Reconnection to the network due to RAN timing synchronization status change (RANtiming) bit to "Reconnection to the network due to RAN timing synchronization status change supported" in the 5GMM capability IE of the REGISTRATION REQUEST message, the AMF may include the RAN timing synchronization IE with the RecReq bit set to "Reconnection requested" in the REGISTRATION ACCEPT message. If the AMF receives the initial registration request along with the mobile IAB-indication over N2 reference point (see TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [31]) from UE and the UE is authorized to operate as an MBSR based on the subscription information and local policy (see 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8]), the AMF shall include the Feature authorization indication IE in the REGISTRATION ACCEPT message and shall set the MBSRAI field to "authorized to operate as MBSR". If the AMF receives the initial registration request along with the mobile IAB-indication over N2 reference point (see TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [31]) from UE and the UE is not authorized to operate as an MBSR based on the subscription information and local policy but can operate as a UE, the AMF shall include the Feature authorization indication IE in the REGISTRATION ACCEPT message and shall set the MBSRAI field to "not authorized to operate as MBSR but allowed to operate as a UE". If the UE supports user plane positioning using LCS-UPP, SUPL or both, the AMF shall set the LCS-UPP bit and the SUPL bit in the 5GS network feature support IE of the REGISTRATION ACCEPT message as specified in 3GPP TS 24.572[ 5G System (5GS); User plane Location Services (LCS) protocols and procedures; Stage 3 ] [64]. Upon receipt of the REGISTRATION ACCEPT message, the UE shall reset the registration attempt counter, enter state 5GMM-REGISTERED and set the 5GS update status to 5U1 UPDATED. If the UE receives the REGISTRATION ACCEPT message from a PLMN, then the UE shall reset the PLMN-specific attempt counter for that PLMN for the specific access type for which the message was received. The UE shall also reset the PLMN-specific N1 mode attempt counter for that PLMN for the specific access type for which the message was received. If the message was received via 3GPP access, the UE shall reset the counter for "SIM/USIM considered invalid for GPRS services" events and the counter for "SIM/USIM considered invalid for non-GPRS services" events, if any. If the message was received via non-3GPP access, the UE shall reset the counter for "USIM considered invalid for 5GS services over non-3GPP" events. If the UE receives the REGISTRATION ACCEPT message from an SNPN, then the UE shall reset the SNPN-specific attempt counter for the current SNPN for the specific access type for which the message was received. If the message was received via 3GPP access, the UE shall reset the counter for "the entry for the current SNPN considered invalid for 3GPP access" events. If the message was received via non-3GPP access, the UE shall reset the counter for "the entry for the current SNPN considered invalid for non-3GPP access" events. If the REGISTRATION ACCEPT message included a T3512 value IE, the UE shall use the value in the T3512 value IE as periodic registration update timer (T3512). If the REGISTRATION ACCEPT message include a T3324 value IE, the UE shall use the value in the T3324 value IE as active timer (T3324). If the REGISTRATION ACCEPT message included a non-3GPP de-registration timer value IE, the UE shall use the value in non-3GPP de-registration timer value IE as non-3GPP de-registration timer. If the REGISTRATION ACCEPT message contains a) the Network slicing indication IE with the Network slicing subscription change indication set to "Network slicing subscription changed"; b) a Configured NSSAI IE with a new configured NSSAI for the current PLMN or SNPN and optionally the mapped S-NSSAI(s) for the configured NSSAI for the current PLMN or SNPN; c) an NSSRG information IE with a new NSSRG information; d) an Alternative NSSAI IE with a new alternative NSSAI; e) an S-NSSAI location validity information in the Registration accept type 6 IE container IE with a new S-NSSAI location validity information; or f) an S-NSSAI time validity information IE with a new S-NSSAI time validity information, the UE shall return a REGISTRATION COMPLETE message to the AMF to acknowledge the successful update of the network slicing information. If the UE has set the RCMAN bit to "Sending of REGISTRATION COMPLETE message for NSAG information supported" in the 5GMM capability IE of the REGISTRATION REQUEST message and if REGISTRATION ACCEPT message contains the NSAG information IE, the UE shall return REGISTRATION COMPLETE message to the AMF to acknowledge the reception of the NSAG information IE. NOTE 9A: When the UE receives the NSSRG information IE, the UE may provide the NSSRG information to lower layers for the purpose of NSAG-aware cell reselection. If the REGISTRATION ACCEPT message contains the CAG information list IE or the Extended CAG information list IE and the UE had set the CAG bit to "CAG supported" in the 5GMM capability IE of the REGISTRATION REQUEST message, the UE shall: a) replace the "CAG information list" stored in the UE with the received CAG information list IE or the Extended CAG information list IE when received in the HPLMN or EHPLMN; NOTE 10: When the UE receives the CAG information list IE or the Extended CAG information list IE in the HPLMN derived from the IMSI, the EHPLMN list is present and is not empty and the HPLMN is not present in the EHPLMN list, the UE behaves as if it receives the CAG information list IE or the Extended CAG information list IE in a VPLMN. b) replace the serving VPLMN's entry of the "CAG information list" stored in the UE with the serving VPLMN's entry of the received CAG information list IE or the Extended CAG information list IE when the UE receives the CAG information list IE or the Extended CAG information list IE in a serving PLMN other than the HPLMN or EHPLMN; or NOTE 11: When the UE receives the CAG information list IE or the Extended CAG information list IE in a serving PLMN other than the HPLMN or EHPLMN, entries of a PLMN other than the serving VPLMN, if any, in the received CAG information list IE or the Extended CAG information list IE are ignored. c) remove the serving VPLMN's entry of the "CAG information list" stored in the UE when the UE receives the CAG information list IE or the Extended CAG information list IE in a serving PLMN other than the HPLMN or EHPLMN and the CAG information list IE or the Extended CAG information list IE does not contain the serving VPLMN's entry. The UE shall store the "CAG information list" received in the CAG information list IE or the Extended CAG information list IE as specified in annex C. If the received "CAG information list" includes an entry containing the identity of the registered PLMN, the UE shall operate as follows: a) if the UE receives the REGISTRATION ACCEPT message via a CAG cell, none of the CAG-ID(s) supported by the current CAG cell is authorized based on the "Allowed CAG list" of the entry for the registered PLMN in the received "CAG information list", and: 1) the entry for the registered PLMN in the received "CAG information list" does not include an "indication that the UE is only allowed to access 5GS via CAG cells", then the UE shall enter the state 5GMM-REGISTERED.LIMITED-SERVICE and shall search for a suitable cell according to 3GPP TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [28] or 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [25C] with the updated "CAG information list"; or 2) the entry for the registered PLMN in the received "CAG information list" includes an "indication that the UE is only allowed to access 5GS via CAG cells" and: i) if one or more CAG-ID(s) are authorized based on the "Allowed CAG list" of the entry for the registered PLMN in the received "CAG information list", the UE shall enter the state 5GMM-REGISTERED.LIMITED-SERVICE and shall search for a suitable cell according to 3GPP TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [28] with the updated "CAG information list"; or ii) if no CAG-ID is authorized based on the "Allowed CAG list" of the entry for the registered PLMN in the received "CAG information list", the UE has not set the 5GS registration type IE in the REGISTRATION REQUEST message to "emergency registration", and the initial registration was not initiated to perform handover of an existing emergency PDU session from the non-current access to the current access, then the UE shall enter the state 5GMM-REGISTERED.PLMN-SEARCH and shall apply the PLMN selection process defined in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5] with the updated "CAG information list"; or b) if the UE receives the REGISTRATION ACCEPT message via a non-CAG cell and the entry for the registered PLMN in the received "CAG information list" includes an "indication that the UE is only allowed to access 5GS via CAG cells" and: 1) if one or more CAG-ID(s) are authorized based on the "allowed CAG list" for the registered PLMN in the received "CAG information list", the UE shall enter the state 5GMM-REGISTERED.LIMITED-SERVICE and shall search for a suitable cell according to 3GPP TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [28] with the updated "CAG information list"; or 2) if no CAG-ID is authorized based on the "Allowed CAG list" of the entry for the registered PLMN in the received "CAG information list", the UE has not set the 5GS registration type IE in the REGISTRATION REQUEST message to "emergency registration", and the initial registration was not initiated to perform handover of an existing emergency PDU session from the non-current access to the current access, then the UE shall enter the state 5GMM-REGISTERED.PLMN-SEARCH and shall apply the PLMN selection process defined in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5] with the updated "CAG information list". If the received "CAG information list" does not include an entry containing the identity of the registered PLMN and the UE receives the REGISTRATION ACCEPT message via a CAG cell, the UE shall enter the state 5GMM-REGISTERED.LIMITED-SERVICE and shall search for a suitable cell according to 3GPP TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [28] or 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [25C] with the updated "CAG information list". If the REGISTRATION ACCEPT message contains the Operator-defined access category definitions IE, the Extended emergency number list IE ,the CAG information list IE or the Extended CAG information list IE, the UE shall return a REGISTRATION COMPLETE message to the AMF to acknowledge reception of the operator-defined access category definitions, the extended local emergency numbers list or the "CAG information list". If the UE has set the RCMAP bit to "Sending of REGISTRATION COMPLETE message for negotiated PEIPS parameters supported" in the 5GMM capability IE of the REGISTRATION REQUEST message and if REGISTRATION ACCEPT message contains the Negotiated PEIPS assistance information IE, the UE shall return REGISTRATION COMPLETE message to the AMF to acknowledge the reception of the Negotiated PEIPS assistance information IE. If the REGISTRATION ACCEPT message contains the UE radio capability ID IE or the UE radio capability ID deletion indication IE, the UE shall return a REGISTRATION COMPLETE message to the AMF to acknowledge reception of the UE radio capability ID IE or the UE radio capability ID deletion indication IE. Upon receiving a REGISTRATION COMPLETE message, the AMF shall stop timer T3550 and change to state 5GMM-REGISTERED. The 5G-GUTI, if sent in the REGISTRATION ACCEPT message, shall be considered as valid, the PEIPS assistance information, if sent in the REGISTRATION ACCEPT message, shall be considered as valid, and the UE radio capability ID, if sent in the REGISTRATION ACCEPT, shall be considered as valid. If the 5GS update type IE was included in the REGISTRATION REQUEST message with the SMS requested bit set to "SMS over NAS supported", and SMSF selection is successful, then the AMF shall send the REGISTRATION ACCEPT message after the SMSF has confirmed that the activation of the SMS service was successful. When sending the REGISTRATION ACCEPT message, the AMF shall: a) set the SMS allowed bit of the 5GS registration result IE to "SMS over NAS allowed" in the REGISTRATION ACCEPT message, if the UE has set the SMS requested bit of the 5GS update type IE to "SMS over NAS supported" in the REGISTRATION REQUEST message and the network allows the use of SMS over NAS for the UE; and b) store the SMSF address and the value of the SMS allowed bit of the 5GS registration result IE in the UE 5GMM context and consider the UE available for SMS over NAS. If: a) the SMSF selection in the AMF is not successful; b) the SMS activation via the SMSF is not successful; c) the AMF does not allow the use of SMS over NAS; d) the SMS requested bit of the 5GS update type IE was set to "SMS over NAS not supported" in the REGISTRATION REQUEST message; or e) the 5GS update type IE was not included in the REGISTRATION REQUEST message; then the AMF shall set the SMS allowed bit of the 5GS registration result IE to "SMS over NAS not allowed" in the REGISTRATION ACCEPT message. When the UE receives the REGISTRATION ACCEPT message, if the UE is also registered over another access to the same PLMN, the UE considers the value indicated by the SMS allowed bit of the 5GS registration result IE as applicable for both accesses over which the UE is registered. The AMF shall include the 5GS registration result IE in the REGISTRATION ACCEPT message. If the 5GS registration result value in the 5GS registration result IE indicates: a) "3GPP access", the UE: - shall consider itself as being registered to 3GPP access; and - if in 5GMM-REGISTERED state over non-3GPP access and on the same PLMN or SNPN as 3GPP access, shall enter state 5GMM-DEREGISTERED.ATTEMPTING-REGISTRATION over non-3GPP access and set the 5GS update status to 5U2 NOT UPDATED over non-3GPP access; or b) "Non-3GPP access", the UE: - shall consider itself as being registered to non-3GPP access; and - if in the 5GMM-REGISTERED state over 3GPP access and is on the same PLMN or SNPN as non-3GPP access, shall enter the state 5GMM-DEREGISTERED.ATTEMPTING-REGISTRATION over 3GPP access and set the 5GS update status to 5U2 NOT UPDATED over 3GPP access; or c) "3GPP access and non-3GPP access", the UE shall consider itself as being registered to both 3GPP access and non-3GPP access. In roaming scenarios, the AMF shall provide mapped S-NSSAI(s) for the configured NSSAI, the allowed NSSAI, the partially allowed NSSAI, the rejected NSSAI (if Extended rejected NSSAI IE is used) , the partially rejected NSSAI, the pending NSSAI or NSSRG information when included in the REGISTRATION ACCEPT message. The AMF shall include the allowed NSSAI for the current PLMN or SNPN and shall include the mapped S-NSSAI(s) for the allowed NSSAI contained in the requested NSSAI from the UE if available, in the REGISTRATION ACCEPT message if the UE included the requested NSSAI in the REGISTRATION REQUEST message and the AMF allows one or more S-NSSAIs in the requested NSSAI. Additionally, if the AMF allows one or more subscribed S-NSSAIs for the UE, the AMF may include the allowed subscribed S-NSSAI(s) in the allowed NSSAI in the REGISTRATION ACCEPT message. The AMF may also include rejected NSSAI in the REGISTRATION ACCEPT message if the initial registration request is not for onboarding services in SNPN. If the UE has set the ER-NSSAI bit to "Extended rejected NSSAI supported" in the 5GMM capability IE of the REGISTRATION REQUEST message, the rejected NSSAI shall be included in the Extended rejected NSSAI IE in the REGISTRATION ACCEPT message; otherwise the rejected NSSAI shall be included in the Rejected NSSAI IE in the REGISTRATION ACCEPT message. If the initial registration request is for onboarding services in SNPN, the AMF shall not include rejected NSSAI in the REGISTRATION ACCEPT message. If the UE has indicated the support for partial network slice and the AMF determines one or more S-NSSAI(s) in the requested NSSAI are to be included in the partially rejected NSSAI as specified in subclause 4.6.2.11, the AMF shall include the Partially rejected NSSAI IE in the Registration accept type 6 IE container IE of the REGISTRATION ACCEPT message. If the UE receives the Partially rejected NSSAI IE in the Registration accept type 6 IE container IE of the REGISTRATION ACCEPT message, the UE shall store the partially rejected NSSAI as specified in subclause 4.6.2.2. If the UE has set the ER-NSSAI bit to "Extended rejected NSSAI supported" in the 5GMM capability IE of the REGISTRATION REQUEST message, the rejected NSSAI contains S-NSSAI(s) which was included in the requested NSSAI but rejected by the network associated with rejection cause(s); otherwise the rejected NSSAI contains S-NSSAI(s) which was included in the requested NSSAI but rejected by the network associated with rejection cause(s) with the following restrictions: a) rejected NSSAI for the current PLMN or SNPN shall not include an S-NSSAI for the current PLMN or SNPN which is associated to multiple mapped S-NSSAIs and some of these but not all mapped S-NSSAIs are not allowed; and b) rejected NSSAI for the current registration area shall not include an S-NSSAI for the current PLMN or SNPN which is associated to multiple mapped S-NSSAIs and some of these but not all mapped S-NSSAIs are not allowed. NOTE 12: The UE that does not support extended rejected NSSAI can avoid requesting an S-NSSAI associated with a mapped S-NSSAI, which was included in the previous requested NSSAI but neither in the allowed NSSAI nor in the rejected NSSAI in the consequent registration procedures. If the UE indicated the support for network slice-specific authentication and authorization, and if the Requested NSSAI IE includes one or more S-NSSAIs subject to network slice-specific authentication and authorization, the AMF shall in the REGISTRATION ACCEPT message include: a) the allowed NSSAI containing the S-NSSAI(s) or the mapped S-NSSAI(s), if any: 1) which are not subject to network slice-specific authentication and authorization and are allowed by the AMF; or 2) for which the network slice-specific authentication and authorization has been successfully performed; aa) the partially allowed NSSAI containing the S-NSSAI(s) or the mapped S-NSSAI(s), if any: 1) which are not subject to network slice-specific authentication and authorization and are allowed by the AMF; or 2) for which the network slice-specific authentication and authorization has been successfully performed; b) optionally, the rejected NSSAI; ba) optionally, the partially rejected NSSAI; c) pending NSSAI containing one or more S-NSSAIs for which network slice-specific authentication and authorization (except for re-NSSAA) will be performed or is ongoing, and one or more S-NSSAIs from the pending NSSAI which the AMF provided to the UE during the previous registration procedure for which network slice-specific authentication and authorization will be performed or is ongoing, if any; and d) the "NSSAA to be performed" indicator in the 5GS registration result IE set to indicate that the network slice-specific authentication and authorization procedure will be performed by the network, if the allowed NSSAI is not included in the REGISTRATION ACCEPT message. If the initial registration request is not for onboarding services in SNPN, the UE indicated the support for network slice-specific authentication and authorization, and: a) the UE did not include the requested NSSAI in the REGISTRATION REQUEST message or none of the S-NSSAIs in the requested NSSAI in the REGISTRATION REQUEST message are allowed; b) all default S-NSSAIs are subject to network slice-specific authentication and authorization; and c) the network slice-specific authentication and authorization procedure has not been successfully performed for any of the default S-NSSAIs, the AMF shall in the REGISTRATION ACCEPT message include: a) the "NSSAA to be performed" indicator in the 5GS registration result IE to indicate that the network slice-specific authentication and authorization procedure will be performed by the network; b) pending NSSAI containing one or more default S-NSSAIs for which network slice-specific authentication and authorization will be performed or is ongoing and one or more S-NSSAIs from the pending NSSAI which the AMF provided to the UE during the previous registration procedure for which network slice-specific authentication and authorization will be performed or is ongoing (if any); c) optionally, the rejected NSSAI; and e) optionally, the partially rejected NSSAI. If the initial registration request is not for onboarding services in SNPN, the UE indicated the support for network slice-specific authentication and authorization, and: a) the UE did not include the requested NSSAI in the REGISTRATION REQUEST message or none of the S-NSSAIs in the requested NSSAI in the REGISTRATION REQUEST message are allowed; and b) one or more default S-NSSAIs are not subject to network slice-specific authentication and authorization or the network slice-specific authentication and authorization procedure has been successfully performed for one or more default S-NSSAIs; the AMF shall in the REGISTRATION ACCEPT message include: a) pending NSSAI containing one or more default S-NSSAIs for which network slice-specific authentication and authorization will be performed or is ongoing (if any) and one or more S-NSSAIs from the pending NSSAI which the AMF provided to the UE during the previous registration procedure for which network slice-specific authentication and authorization will be performed or is ongoing (if any); b) allowed NSSAI containing S-NSSAI(s) for the current PLMN each of which corresponds to a default S-NSSAI which are not subject to network slice-specific authentication and authorization or for which the network slice-specific authentication and authorization has been successfully performed; c) allowed NSSAI containing one or more default S-NSSAIs, as the mapped S-NSSAI(s) for the allowed NSSAI in roaming scenarios, which are not subject to network slice-specific authentication and authorization or for which the network slice-specific authentication and authorization has been successfully performed; and d) optionally, the rejected NSSAI. If the UE did not include the requested NSSAI in the REGISTRATION REQUEST message or none of the S-NSSAIs in the requested NSSAI in the REGISTRATION REQUEST message are allowed, the allowed NSSAI shall not contain default S-NSSAI(s) that are subject to NSAC. If the subscription information includes the NSSRG information, the S-NSSAIs of the allowed NSSAI shall be associated with at least one common NSSRG value. When the REGISTRATION ACCEPT message includes a pending NSSAI, the pending NSSAI shall contain all S-NSSAIs for which network slice-specific authentication and authorization (except for re-NSSAA) will be performed or is ongoing from the requested NSSAI of the REGISTRATION REQUEST message that was received over the 3GPP access, non-3GPP access, or both the 3GPP access and non-3GPP access. If the UE supports extended rejected NSSAI and the AMF determines that maximum number of UEs reached for one or more S-NSSAI(s) in the requested NSSAI as specified in subclause 4.6.2.5, the AMF shall include the rejected NSSAI containing one or more S-NSSAIs with the rejection cause "S-NSSAI not available due to maximum number of UEs reached" in the Extended rejected NSSAI IE in the REGISTRATION ACCEPT message. In addition, the AMF may include a back-off timer value for each S-NSSAI with the rejection cause "S-NSSAI not available due to maximum number of UEs reached" included in the Extended rejected NSSAI IE of the REGISTRATION ACCEPT message. To avoid that large numbers of UEs simultaneously initiate deferred requests, the network should select the value for the backoff timer for each S-NSSAI for the informed UEs so that timeouts are not synchronised. If the UE does not indicate support for extended rejected NSSAI and the maximum number of UEs has been reached, the AMF should include the rejected NSSAI containing one or more S-NSSAIs with the rejection cause "S-NSSAI not available in the current registration area" in the Rejected NSSAI IE and should not include these S-NSSAIs in the allowed NSSAI in the REGISTRATION ACCEPT message. NOTE 13: Based on network policies, the AMF can include the S-NSSAI(s) for which the maximum number of UEs has been reached in the rejected NSSAI with rejection causes other than "S-NSSAI not available in the current registration area". If the UE indicates the support for the network slice usage control and the AMF determines to provide on-demand NSSAI, the AMF shall include the On-demand NSSAI IE in the REGISTRATION ACCEPT message. If the UE supports network slice usage control and the AMF determines to provide on-demand NSSAI, the AMF shall include the On-demand NSSAI IE in the REGISTRATION ACCEPT message. If the UE receives the On-demand NSSAI IE in the REGISTRATION ACCEPT message, the UE shall store the on-demand NSSAI as specified in subclause 4.6.2.2. If the AMF has a new configured NSSAI for the current PLMN or SNPN, the AMF shall include the configured NSSAI for the current PLMN or SNPN in the REGISTRATION ACCEPT message. NOTE 13A: A new configured NSSAI can be available at the AMF following an indication that the subscription data for network slicing has changed. The AMF may include a new configured NSSAI for the current PLMN or SNPN in the REGISTRATION ACCEPT message if: a) the REGISTRATION REQUEST message did not include the requested NSSAI and the initial registration request is not for onboarding services in SNPN; b) the REGISTRATION REQUEST message included the requested NSSAI containing an S-NSSAI that is not valid in the serving PLMN or SNPN; c) the REGISTRATION REQUEST message included the requested NSSAI containing S-NSSAI(s) with incorrect mapped S-NSSAI(s); d) the REGISTRATION REQUEST message included the Network slicing indication IE with the Default configured NSSAI indication bit set to "Requested NSSAI created from default configured NSSAI"; e) the S-NSSAIs of the requested NSSAI in the REGISTRATION REQUEST message are not associated with any common NSSRG value, except for the case that the AMF, based on the indication received from the UDM as specified in 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8], has provided all subscribed S-NSSAIs in the configured NSSAI to a UE who does not support NSSRG; or NOTE 14: If the S-NSSAIs of the requested NSSAI in the REGISTRATION REQUEST message are not associated with any common NSSRG value, it is possible that at least one of the S-NSSAIs is not included in any of new allowed NSSAI, new (extended) rejected NSSAI (if applicable), and new pending NSSAI (if applicable). f) the UE is in 5GMM-REGISTERED state over the other access and the S-NSSAIs of the requested NSSAI in the REGISTRATION REQUEST message over the current access and the allowed NSSAI over the other access are not associated with any common NSSRG value. The AMF may include a new configured NSSAI for the current PLMN or SNPN in the REGISTRATION ACCEPT message if the REGISTRATION REQUEST message includes a requested NSSAI containing an S-NSSAI and the S-NSSAI time validity information, if available, indicates that the S-NSSAI is not available (see 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8]). In this case, if the TempNS bit of the 5GMM capability IE in the REGISTRATION REQUEST message is set to: a) "S-NSSAI time validity information supported" and the S-NSSAI time validity information indicates that the S-NSSAI will: 1) become available again, then the AMF shall also send S-NSSAI time validity information; or 2) not become available again, then the AMF shall not include the S-NSSAI in the new configured NSSAI; or b) "S-NSSAI time validity information not supported" and the AMF sends a new configured NSSAI, then the AMF shall not include the S-NSSAI in the new configured NSSAI. If a new configured NSSAI for the current PLMN is included in the REGISTRATION ACCEPT message, the subscription information includes the NSSRG information, and the NSSRG bit in the 5GMM capability IE of the REGISTRATION REQUEST message is set to: a) "NSSRG supported", then the AMF shall include the NSSRG information in the REGISTRATION ACCEPT message; or b) "NSSRG not supported", then the configured NSSAI shall include one or more S-NSSAIs each of which is associated with all the NSSRG value(s) of the default S-NSSAI(s), or the configured NSSAI shall include, based on the indication received from the UDM as specified in 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8], all subscribed S-NSSAIs even if these S-NSSAIs do not share any common NSSRG value. If the AMF needs to update the NSSRG information and the UE has set the NSSRG bit to "NSSRG supported" in the 5GMM capability IE of the REGISTRATION REQUEST message, then the AMF shall include the new NSSRG information in the REGISTRATION ACCEPT message. In addition, the AMF shall start timer T3550 and enter state 5GMM-COMMON-PROCEDURE-INITIATED as described in subclause 5.1.3.2.3.3. If the UE supports S-NSSAI time validity information and the AMF needs to update the S-NSSAI time validity information, then the AMF shall include the S-NSSAI time validity information IE in the REGISTRATION ACCEPT message. In addition, the AMF shall start timer T3550 and enter state 5GMM-COMMON-PROCEDURE-INITIATED as described in subclause 5.1.3.2.3.3. If the UE supports S-NSSAI location validity information and the AMF needs to update the S-NSSAI location validity information, then the AMF shall include the new S-NSSAI location validity information in the Registration accept type 6 IE container IE of the REGISTRATION ACCEPT message. In addition, the AMF shall start timer T3550 and enter state 5GMM-COMMON-PROCEDURE-INITIATED as described in subclause 5.1.3.2.3.3. If the UE has set the NSAG bit to "NSAG supported" in the 5GMM capability IE of the REGISTRATION REQUEST message over 3GPP access, the AMF may include the NSAG information IE in the REGISTRATION ACCEPT message. Up to 4 NSAG entries are allowed to be associated with a TAI list in the NSAG information IE. If the UE has set the RCMAN bit to "Sending of REGISTRATION COMPLETE message for NSAG information supported" in the 5GMM capability IE of the REGISTRATION REQUEST message and if the NSAG information IE is included in the REGISTRATION ACCEPT message, the AMF shall start timer T3550 and enter state 5GMM-COMMON-PROCEDURE-INITIATED as described in subclause 5.1.3.2.3.3. NOTE 14a: How the AMF selects NSAG entries to be included in the NSAG information IE is implementation specific, e.g. take the NSAG priority and the current registration area into account. NOTE 14b: If the NSAG for the PLMN and its equivalent PLMN(s) have different associations with S-NSSAIs, then the AMF includes a TAI list for the NSAG entry in the NSAG information IE. If the UE receives the NSAG information IE in the REGISTRATION ACCEPT message, the UE shall store the NSAG information as specified in subclause 4.6.2.2. If the UE supports network slice replacement and the AMF determines to provide the mapping information between the S-NSSAI to be replaced and the alternative S-NSSAI to the UE, then the AMF shall include the Alternative NSSAI IE, the Allowed NSSAI IE including the alternative S-NSSAI, if not included in the current allowed NSSAI, and the Configured NSSAI IE including the alternative S-NSSAI, if not included in the current configured NSSAI, in the REGISTRATION ACCEPT message. If the AMF determines that the S-NSSAI which has been replaced is available, then the AMF shall provide the updated alternative NSSAI excluding the S-NSSAI which has been replaced and the corresponding alternative S-NSSAI in the Alternative NSSAI IE in the REGISTRATION ACCEPT message. If the AMF determines that all the S-NSSAI(s) which have been replaced are available, then the AMF shall provide the Alternative NSSAI IE with Length of Alternative NSSAI contents set to 0 in the REGISTRATION ACCEPT message. In addition, the AMF shall start timer T3550 and enter state 5GMM-COMMON-PROCEDURE-INITIATED as described in subclause 5.1.3.2.3.3. If the UE receives the Alternative NSSAI IE in the REGISTRATION ACCEPT message, the UE shall store the alternative NSSAI as specified in subclause 4.6.2.2. If the UE has indicated the support for partial network slice and the AMF determines one or more S-NSSAI(s) in the requested NSSAI are to be included in the partially allowed NSSAI as specified in subclause 4.6.2.11, the AMF shall include the Partially allowed NSSAI IE in the Registration accept type 6 IE container IE of the REGISTRATION ACCEPT message. If the UE receives the Partially allowed NSSAI IE in the Registration accept type 6 IE container IE of the REGISTRATION ACCEPT message, the UE shall store the partially allowed NSSAI as specified in subclause 4.6.2.2. If the UE requests ciphering keys for ciphered broadcast assistance data in the REGISTRATION REQUEST message and the AMF has valid ciphering key data applicable to the UE's subscription and current tracking area, then the AMF shall include the ciphering key data in the Ciphering key data IE of the REGISTRATION ACCEPT message. The AMF shall include the Network slicing indication IE with the Network slicing subscription change indication set to "Network slicing subscription changed" in the REGISTRATION ACCEPT message if the UDM has indicated that the subscription data for network slicing has changed. In this case the AMF shall start timer T3550 and enter state 5GMM-COMMON-PROCEDURE-INITIATED as described in subclause 5.1.3.2.3.3. The UE that has indicated the support for network slice-specific authentication and authorization receiving the pending NSSAI in the REGISTRATION ACCEPT message shall store the S-NSSAI(s) in the pending NSSAI as specified in subclause 4.6.2.2. If the registration area contains TAIs belonging to different PLMNs, which are equivalent PLMNs, the UE shall store the received pending NSSAI for each of the equivalent PLMNs as specified in subclause 4.6.2.2. If the pending NSSAI is not included in the REGISTRATION ACCEPT message and the "NSSAA to be performed" indicator is not set to "Network slice-specific authentication and authorization is to be performed" in the 5GS registration result IE of the REGISTRATION ACCEPT message, then the UE shall delete the pending NSSAI for the current PLMN and its equivalent PLMN(s) or SNPN, if existing, as specified in subclause 4.6.2.2. The UE receiving the rejected NSSAI in the REGISTRATION ACCEPT message takes the following actions based on the rejection cause in the rejected S-NSSAI(s): "S-NSSAI not available in the current PLMN or SNPN" The UE shall add the rejected S-NSSAI(s) in the rejected NSSAI for the current PLMN or SNPN as specified in subclause 4.6.2.2 and shall not attempt to use this S-NSSAI(s) in the current PLMN or SNPN over any access until switching off the UE, the UICC containing the USIM is removed, the entry of the "list of subscriber data" with the SNPN identity of the current SNPN is updated, or the rejected S-NSSAI(s) are removed as described in subclause 4.6.2.2. "S-NSSAI not available in the current registration area" The UE shall add the rejected S-NSSAI(s) in the rejected NSSAI for the current registration area as specified in subclause 4.6.2.2 and shall not attempt to use this S-NSSAI(s) in the current registration area over the current until switching off the UE, the UE moving out of the current registration area, the UICC containing the USIM is removed, the entry of the "list of subscriber data" with the SNPN identity of the current SNPN is updated, or the rejected S-NSSAI(s) are removed as described in subclause 4.6.2.2. "S-NSSAI not available due to the failed or revoked network slice-specific authentication and authorization" The UE shall store the rejected S-NSSAI(s) in the rejected NSSAI for the failed or revoked NSSAA as specified in subclause 4.6.2.2 and shall not attempt to use this S-NSSAI in the current PLMN or SNPN over any access until switching off the UE, the UICC containing the USIM is removed, the entry of the "list of subscriber data" with the SNPN identity of the current SNPN is updated, or the rejected S-NSSAI(s) are removed as described in subclause 4.6.1 and 4.6.2.2. "S-NSSAI not available due to maximum number of UEs reached" Unless the back-off timer value received along with the S-NSSAI is zero, the UE shall add the rejected S-NSSAI(s) in the rejected NSSAI for the maximum number of UEs reached as specified in subclause 4.6.2.2 and shall not attempt to use this S-NSSAI in the current PLMN or SNPN over the current access until switching off the UE, the UICC containing the USIM is removed, the entry of the "list of subscriber data" with the SNPN identity of the current SNPN is updated, or the rejected S-NSSAI(s) are removed as described in subclauses 4.6.1 and 4.6.2.2. NOTE 15: If the back-off timer value received along with the S-NSSAI in the rejected NSSAI for the maximum number of UEs reached is zero as specified in subclause 10.5.7.4a of 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [12], the UE does not consider the S-NSSAI as the rejected S-NSSAI. If there is one or more S-NSSAIs in the rejected NSSAI with the rejection cause "S-NSSAI not available due to maximum number of UEs reached", then for each S-NSSAI, the UE shall behave as follows: a) stop the timer T3526 associated with the S-NSSAI, if running; b) start the timer T3526 with: 1) the back-off timer value received along with the S-NSSAI, if a back-off timer value is received along with the S-NSSAI that is neither zero nor deactivated; or 2) an implementation specific back-off timer value, if no back-off timer value is received along with the S-NSSAI; and c) remove the S-NSSAI from the rejected NSSAI for the maximum number of UEs reached when the timer T3526 associated with the S-NSSAI expires. If the UE sets the NSSAA bit in the 5GMM capability IE to "Network slice-specific authentication and authorization not supported", and: a) if the Requested NSSAI IE only includes the S-NSSAI(s) subject to network slice-specific authentication and authorization and one or more default S-NSSAIs (containing one or more S-NSSAIs each of which may be associated with a new S-NSSAI) which are not subject to network slice-specific authentication and authorization are available, the AMF shall in the REGISTRATION ACCEPT message include: 1) the allowed NSSAI or the partially allowed NSSAI containing S-NSSAI(s) for the current PLMN or SNPN each of which corresponds to a default S-NSSAI which are not subject to network slice-specific authentication and authorization; 2) the allowed NSSAI or the partially allowed NSSAI containing the default S-NSSAIs, as the mapped S-NSSAI(s) for the allowed NSSAI in roaming scenarios, which are not subject to network slice-specific authentication and authorization; and 3) the rejected NSSAI containing the S-NSSAI(s) subject to network slice specific authentication and authorization with the rejection cause indicating "S-NSSAI not available in the current PLMN or SNPN", except if the UE has not set the ER-NSSAI bit to "Extended rejected NSSAI supported" in the 5GMM capability IE of the REGISTRATION REQUEST message and the S-NSSAI(s) is associated to multiple mapped S-NSSAIs and some of these but not all mapped S-NSSAIs are subject to NSSAA; or b) if the Requested NSSAI IE includes one or more S-NSSAIs subject to network slice-specific authentication and authorization, the AMF shall in the REGISTRATION ACCEPT message include: 1) the allowed NSSAI or the partially allowed NSSAI containing the S-NSSAI(s) or the mapped S-NSSAI(s) which are not subject to network slice-specific authentication and authorization; and 2) the rejected NSSAI containing: i) the S-NSSAI(s) subject to network slice specific authentication and authorization with the rejection cause indicating "S-NSSAI not available in the current PLMN or SNPN", except if the UE has not set the ER-NSSAI bit to "Extended rejected NSSAI supported" in the 5GMM capability IE of the REGISTRATION REQUEST message and the S-NSSAI is associated to multiple mapped S-NSSAIs and some of these but not all mapped S-NSSAIs are subject to NSSAA; and ii) the S-NSSAI(s) which was included in the requested NSSAI but rejected by the network associated with the rejection cause indicating "S-NSSAI not available in the current PLMN or SNPN" or the rejection cause indicating "S-NSSAI not available in the current registration area", if any. If the UE does not indicate support for network slice-specific authentication and authorization, the initial registration request is not for onboarding services in SNPN, and if: a) the UE did not include the requested NSSAI in the REGISTRATION REQUEST message; or b) none of the S-NSSAIs in the requested NSSAI in the REGISTRATION REQUEST message are allowed; and one or more default S-NSSAIs (containing one or more S-NSSAIs each of which may be associated with a new S-NSSAI) which are not subject to network slice-specific authentication and authorization are available, the AMF shall: a) put the allowed S-NSSAI(s) for the current PLMN or SNPN each of which corresponds to a default S-NSSAI and not subject to network slice-specific authentication and authorization in the allowed NSSAI of the REGISTRATION ACCEPT message; b) put the default S-NSSAIs and not subject to network slice-specific authentication and authorization, as the mapped S-NSSAI(s) for the allowed NSSAI in roaming scenarios, in the allowed NSSAI of the REGISTRATION ACCEPT message; and c) determine a registration area such that all S-NSSAIs of the allowed NSSAI are available in the registration area. If the REGISTRATION ACCEPT message contains the Network slicing indication IE with the Network slicing subscription change indication set to "Network slicing subscription changed", the UE shall delete the network slicing information for each and every PLMN or SNPN except for the current PLMN or SNPN as specified in subclause 4.6.2.2 and remove all tracking areas from the list of "5GS forbidden tracking areas for roaming" which were added due to rejection of S-NSSAI due to "S-NSSAI not available in the current registration area". If the REGISTRATION ACCEPT message contains the allowed NSSAI, then the UE shall store the included allowed NSSAI together with the PLMN identity of the registered PLMN or the SNPN identity of the registered SNPN and the registration area as specified in subclause 4.6.2.2. If the registration area contains TAIs belonging to different PLMNs, which are equivalent PLMNs, the UE shall store the received allowed NSSAI in each of allowed NSSAIs which are associated with each of the PLMNs. If the REGISTRATION ACCEPT message contains a configured NSSAI IE with a new configured NSSAI for the current PLMN or SNPN and optionally the mapped S-NSSAI(s) for the configured NSSAI for the current PLMN or SNPN, the UE shall store the contents of the configured NSSAI IE as specified in subclause 4.6.2.2. In addition, if the REGISTRATION ACCEPT message contains: a) an NSSRG information IE, the UE shall store the contents of the NSSRG information IE as specified in subclause 4.6.2.2. If the UE receives a new configured NSSAI in the REGISTRATION ACCEPT message and no NSSRG information IE, the UE shall delete any stored NSSRG information, if any, as specified in subclause 4.6.2.2; b) an S-NSSAI location validity information in the Registration accept type 6 IE container IE, the UE shall store the contents of the S-NSSAI location validity information as specified in subclause 4.6.2.2. If the UE receives a Configured NSSAI IE in the REGISTRATION ACCEPT message and no S-NSSAI location validity information, the UE shall delete any stored S-NSSAI location validity information as specified in subclause 4.6.2.2; c) an S-NSSAI time validity information IE, the UE shall store the contents of the S-NSSAI time validity information IE as specified in subclause 4.6.2.2. If the UE receives a Configured NSSAI IE in the REGISTRATION ACCEPT message and no S-NSSAI time validity information IE, the UE shall delete any stored S-NSSAI time validity information as specified in subclause 4.6.2.2; or d) an On-demand NSSAI IE, the UE shall store the contents of the On-demand NSSAI IE as specified in subclause 4.6.2.2. If the UE receives a Configured NSSAI IE in the REGISTRATION ACCEPT message and no On-demand NSSAI IE, the UE shall delete any stored on-demand NSSAI as specified in subclause 4.6.2.2. The UE shall stop slice deregistration inactivity timer, if running for the S-NSSAI which is deleted from the on-demand NSSAI. If the REGISTRATION ACCEPT message: a) includes the 5GS registration result IE with the "NSSAA to be performed" indicator set to "Network slice-specific authentication and authorization is to be performed"; b) includes a pending NSSAI; c) does not include an allowed NSSAI; and d) does not include an partially allowed NSSAI, the UE shall delete the stored allowed NSSAI, if any, as specified in subclause 4.6.2.2, and the UE: a) shall not initiate a 5GSM procedure except for emergency services ; and b) shall not initiate a service request procedure except for cases f), i), m) and o) in subclause 5.6.1.1; c) shall not initiate an NAS transport procedure except for sending SMS, an LPP message, a UPP-CMI container, an SLPP message, a location service message, an SOR transparent container, a UE policy container, a UE parameters update transparent container or a CIoT user data container; until the UE receives an allowed NSSAI, a partially allowed NSSAI, or both. If the UE included S1 mode supported indication in the REGISTRATION REQUEST message, the AMF supporting interworking with EPS shall set the IWK N26 bit to either: a) "interworking without N26 interface not supported" if the AMF supports N26 interface; or b) "interworking without N26 interface supported" if the AMF does not support N26 interface in the 5GS network feature support IE in the REGISTRATION ACCEPT message. The UE supporting S1 mode shall operate in the mode for interworking with EPS as follows: a) if the IWK N26 bit in the 5GS network feature support IE is set to "interworking without N26 interface not supported", the UE shall operate in single-registration mode; b) if the IWK N26 bit in the 5GS network feature support IE is set to "interworking without N26 interface supported" and the UE supports dual-registration mode, the UE may operate in dual-registration mode; or NOTE 16: The registration mode used by the UE is implementation dependent. c) if the IWK N26 bit in the 5GS network feature support IE is set to "interworking without N26 interface supported" and the UE only supports single-registration mode, the UE shall operate in single-registration mode. The UE shall store the received interworking without N26 interface indicator for interworking with EPS as specified in annex C.1 and treat it as valid in the entire PLMN and its equivalent PLMN(s). The network informs the UE about the support of specific features, such as IMS voice over PS session, location services (5G-LCS), emergency services, emergency services fallback, ATSSS and non-3GPP access path switching, in the 5GS network feature support information element. In a UE with IMS voice over PS session capability, the IMS voice over PS session indicator, the Emergency services support indicator, and the Emergency services fallback indicator shall be provided to the upper layers. The upper layers take the IMS voice over PS session indicator into account when selecting the access domain for voice sessions or calls. In a UE with LCS capability, location services indicator (5G-LCS) shall be provided to the upper layers. When initiating an emergency call, the upper layers also take the IMS voice over PS session indicator, the Emergency services support indicator, and the Emergency services fallback indicator into account for the access domain selection. In a UE with the capability for ATSSS, the network support for ATSSS shall be provided to the upper layers. If the UE receives the 5GS network feature support IE with the ATSSS support indicator set to "ATSSS not supported", the UE shall perform a local release of the MA PDU session, if any. In a UE that supports non-3GPP access path switching, the network support for non-3GPP access path switching shall be provided to the upper layers. If the UE receives the 5GS network feature support IE with the non-3GPP access path switching bit set to "non-3GPP access path switching not supported", the UE shall not perform the registration procedure for mobility registration update for non-3GPP access path switching. NOTE 17: If the UE is registered to different PLMNs over 3GPP and non-3GPP accesses, the UE uses the capability received over non-3GPP access to determine whether to initiate the registration procedure for mobility registration update for non-3GPP path switching. The AMF shall set the EMF bit in the 5GS network feature support IE to: a) "Emergency services fallback supported in NR connected to 5GCN and E-UTRA connected to 5GCN" if the network supports the emergency services fallback procedure when the UE is in an NR cell connected to 5GCN or an E-UTRA cell connected to 5GCN; b) "Emergency services fallback supported in NR connected to 5GCN only" if the network supports the emergency services fallback procedure when the UE is in an NR cell connected to 5GCN and does not support the emergency services fallback procedure when the UE is in an E-UTRA cell connected to 5GCN; c) "Emergency services fallback supported in E-UTRA connected to 5GCN only" if the network supports the emergency services fallback procedure when the UE is in an E-UTRA cell connected to 5GCN and does not support the emergency services fallback procedure when the UE is in an NR cell connected to 5GCN; or d) "Emergency services fallback not supported" if network does not support the emergency services fallback procedure when the UE is in any cell connected to 5GCN. NOTE 18: If the emergency services are supported in neither the EPS nor the 5GS homogeneously, based on operator policy, the AMF will set the EMF bit in the 5GS network feature support IE to "Emergency services fallback not supported". NOTE 19: Even though the AMF's support of emergency services fallback is indicated per RAT, the UE's support of emergency services fallback is not per RAT, i.e. the UE's support of emergency services fallback is the same for both NR connected to 5GCN and E-UTRA connected to 5GCN. Access identity 1 is only applicable while the UE is in N1 mode. Access identity 2 is only applicable while the UE is in N1 mode. When the UE is registered to the same PLMN or SNPN over 3GPP and non-3GPP access, the UE and the AMF maintain one MPS indicator and one MCS indicator that are common to both 3GPP and non-3GPP access. When the UE is registered to different PLMNs or SNPNs over 3GPP access and non-3GPP access, the UE maintains two MPS indicators and two MCS indicators separately for different accesses i.e., an MPS indicator and an MCS indicator for the 3GPP access and another MPS indicator and an MCS indicator for the non-3GPP access. For both 3GPP and non-3GPP access, the access identity is determined according to subclause 4.5.2: - if the UE is not operating in SNPN access operation mode: a) the network informs the UE that the use of access identity 1 is valid in the RPLMN or equivalent PLMN by setting the MPS indicator bit of the 5GS network feature support IE to "Access identity 1 valid", in the REGISTRATION ACCEPT message. Based on operator policy, the AMF sets the MPS indicator bit in the REGISTRATION ACCEPT message based on the MPS priority information in the user's subscription context obtained from the UDM; b) upon receiving a REGISTRATION ACCEPT message with the MPS indicator bit set to "Access identity 1 valid": - via 3GPP access; or - via non-3GPP access if the UE is registered to the same PLMN over 3GPP access and non-3GPP access; the UE shall act as a UE with access identity 1 configured for MPS, as described in subclause 4.5.2, in all NG-RAN of the registered PLMN and its equivalent PLMNs. The MPS indicator bit in the 5GS network feature support IE provided in the REGISTRATION ACCEPT message is valid in all NG-RAN of the registered PLMN and its equivalent PLMNs until the UE receives a REGISTRATION ACCEPT message or a CONFIGURATION UPDATE COMMAND message with the MPS indicator bit set to "Access identity 1 not valid": - via 3GPP access; or - via non-3GPP access if the UE is registered to the same PLMN over 3GPP access and non-3GPP access; or until the UE selects a non-equivalent PLMN over 3GPP access; b1) upon receiving a REGISTRATION ACCEPT message with the MPS indicator bit set to "Access identity 1 valid": - via non-3GPP access; or - via 3GPP access if the UE is registered to the same PLMN over 3GPP access and non-3GPP access; the UE shall act as a UE with access identity 1 configured for MPS, as described in subclause 4.5.2, in non-3GPP access of the registered PLMN and its equivalent PLMNs. The MPS indicator bit in the 5GS network feature support IE provided in the REGISTRATION ACCEPT message is valid in non-3GPP access of the registered PLMN and its equivalent PLMNs until the UE receives a REGISTRATION ACCEPT message or a CONFIGURATION UPDATE COMMAND message with the MPS indicator bit set to "Access identity 1 not valid": - via non-3GPP access; or - via 3GPP access if the UE is registered to the same PLMN over 3GPP access and non-3GPP access; or until the UE selects a non-equivalent PLMN over non-3GPP access; c) the network informs the UE that the use of access identity 2 is valid in the RPLMN or equivalent PLMN by setting the MCS indicator bit of the 5GS network feature support IE to "Access identity 2 valid", in the REGISTRATION ACCEPT message. Based on operator policy, the AMF sets the MCS indicator bit in the REGISTRATION ACCEPT message based on the MCS priority information in the user's subscription context obtained from the UDM; d) upon receiving a REGISTRATION ACCEPT message with the MCS indicator bit set to "Access identity 2 valid": - via 3GPP access; or - via non-3GPP access if the UE is registered to the same PLMN over 3GPP access and non-3GPP access; the UE shall act as a UE with access identity 2 configured for MCS, as described in subclause 4.5.2, in all NG-RAN of the registered PLMN and its equivalent PLMNs. The MCS indicator bit in the 5GS network feature support IE provided in the REGISTRATION ACCEPT message is valid in all NG-RAN of the registered PLMN and its equivalent PLMNs until the UE receives a REGISTRATION ACCEPT message or a CONFIGURATION UPDATE COMMAND message with the MCS indicator bit set to "Access identity 2 not valid": - via 3GPP access; or - via non-3GPP access if the UE is registered to the same PLMN over 3GPP access and non-3GPP access; or until the UE selects a non-equivalent PLMN over 3GPP access; and d1) upon receiving a REGISTRATION ACCEPT message with the MCS indicator bit set to "Access identity 2 valid": - via non-3GPP access; or - via 3GPP access if the UE is registered to the same PLMN over 3GPP access and non-3GPP access; the UE shall act as a UE with access identity 2 configured for MCS, as described in subclause 4.5.2, in non-3GPP access of the registered PLMN and its equivalent PLMNs. The MCS indicator bit in the 5GS network feature support IE provided in the REGISTRATION ACCEPT message is valid in non-3GPP access of the registered PLMN and its equivalent PLMNs until the UE receives a REGISTRATION ACCEPT message or a CONFIGURATION UPDATE COMMAND message with the MCS indicator bit set to "Access identity 2 not valid": - via non-3GPP access; or - via 3GPP access if the UE is registered to the same PLMN over 3GPP access and non-3GPP access; or until the UE selects a non-equivalent PLMN over non-3GPP access; or - if the UE is operating in SNPN access operation mode: a) the network informs the UE that the use of access identity 1 is valid in the RSNPN or equivalent SNPN by setting the MPS indicator bit of the 5GS network feature support IE to "Access identity 1 valid", in the REGISTRATION ACCEPT message. Based on operator policy, the AMF sets the MPS indicator bit in the REGISTRATION ACCEPT message based on the MPS priority information in the user's subscription context obtained from the UDM; b) upon receiving a REGISTRATION ACCEPT message with the MPS indicator bit set to "Access identity 1 valid": - via 3GPP access; or - via non-3GPP access if the UE is registered to the same SNPN over 3GPP access and non-3GPP access; the UE shall act as a UE with access identity 1 configured for MPS, as described in subclause 4.5.2A, in all NG-RAN of the registered SNPN and its equivalent SNPNs. The MPS indicator bit in the 5GS network feature support IE provided in the REGISTRATION ACCEPT message is valid in all NG-RAN of the registered SNPN and its equivalent SNPNs until the UE receives a REGISTRATION ACCEPT message or a CONFIGURATION UPDATE COMMAND message with the MPS indicator bit set to "Access identity 1 not valid": - via 3GPP access; or - via non-3GPP access if the UE is registered to the same SNPN over 3GPP access and non-3GPP access; or until the UE selects a non-equivalent SNPN over 3GPP access; b1) upon receiving a REGISTRATION ACCEPT message with the MPS indicator bit set to "Access identity 1 valid": - via non-3GPP access; or - via 3GPP access if the UE is registered to the same SNPN over 3GPP access and non-3GPP access; the UE shall act as a UE with access identity 1 configured for MPS, as described in subclause 4.5.2A, in non-3GPP access of the registered SNPN and its equivalent SNPNs. The MPS indicator bit in the 5GS network feature support IE provided in the REGISTRATION ACCEPT message is valid in non-3GPP access of the registered SNPN and its equivalent SNPNs until the UE receives a REGISTRATION ACCEPT message or a CONFIGURATION UPDATE COMMAND message with the MPS indicator bit set to "Access identity 1 not valid"; - via non-3GPP access; or - via 3GPP access if the UE is registered to the same SNPN over 3GPP access and non-3GPP access; or until the UE selects a non-equivalent SNPN over non-3GPP access; c) the network informs the UE that the use of access identity 2 is valid in the RSNPN or equivalent SNPN by setting the MCS indicator bit of the 5GS network feature support IE to "Access identity 2 valid", in the REGISTRATION ACCEPT message. Based on operator policy, the AMF sets the MCS indicator bit in the REGISTRATION ACCEPT message based on the MCS priority information in the user's subscription context obtained from the UDM; d) upon receiving a REGISTRATION ACCEPT message with the MCS indicator bit set to "Access identity 2 valid": - via 3GPP access; or - via non-3GPP access if the UE is registered to the same SNPN over 3GPP access and non-3GPP access; the UE shall act as a UE with access identity 2 configured for MCS, as described in subclause 4.5.2A, in all NG-RAN of the registered SNPN and its equivalent SNPNs. The MCS indicator bit in the 5GS network feature support IE provided in the REGISTRATION ACCEPT message is valid in all NG-RAN of the registered SNPN and its equivalent SNPNs until the UE receives a REGISTRATION ACCEPT message or a CONFIGURATION UPDATE COMMAND message with the MCS indicator bit set to "Access identity 2 not valid": - via 3GPP access; or - via non-3GPP access if the UE is registered to the same SNPN over 3GPP access and non-3GPP access; or until the UE selects a non-equivalent SNPN over 3GPP access; and d1) upon receiving a REGISTRATION ACCEPT message with the MCS indicator bit set to "Access identity 2 valid": - via non-3GPP access; or - via 3GPP access if the UE is registered to the same SNPN over 3GPP access and non-3GPP access; the UE shall act as a UE with access identity 2 configured for MCS, as described in subclause 4.5.2A, in non-3GPP access of the registered SNPN and its equivalent SNPNs. The MCS indicator bit in the 5GS network feature support IE provided in the REGISTRATION ACCEPT message is valid in non-3GPP access of the registered SNPN and its equivalent SNPNs until the UE receives a REGISTRATION ACCEPT message or a CONFIGURATION UPDATE COMMAND message with the MCS indicator bit set to "Access identity 2 not valid": - via non-3GPP access; or - via 3GPP access if the UE is registered to the same SNPN over 3GPP access and non-3GPP access; or until the UE selects a non-equivalent SNPN over non-3GPP access. If the UE indicates support for restriction on use of enhanced coverage in the REGISTRATION REQUEST message and: a) in WB-N1 mode, the AMF decides to restrict the use of CE mode B for the UE, then the AMF shall set the RestrictEC bit to "CE mode B is restricted"; b) in WB-N1 mode, the AMF decides to restrict the use of both CE mode A and CE mode B for the UE, then the AMF shall set the RestrictEC bit to " Both CE mode A and CE mode B are restricted"; or c) in NB-N1 mode, the AMF decides to restrict the use of enhanced coverage for the UE, then the AMF shall set the RestrictEC bit to "Use of enhanced coverage is restricted", in the 5GS network feature support IE in the REGISTRATION ACCEPT message. If the UE indicates support of the N1 NAS signalling connection release in the REGISTRATION REQUEST message and the network decides to accept the N1 NAS signalling connection release, then the AMF shall set the N1 NAS signalling connection release bit to "N1 NAS signalling connection release supported" in the 5GS network feature support IE of the REGISTRATION ACCEPT message. If the UE indicates support of the paging indication for voice services in the REGISTRATION REQUEST message and the network decides to accept the paging indication for voice services, then the AMF shall set the paging indication for voice services bit to "paging indication for voice services supported" in the 5GS network feature support IE of the REGISTRATION ACCEPT message. Upon receipt of REGISTRATION ACCEPT message with the paging indication for voice services bit set to "paging indication for voice services supported", the UE NAS layer informs the lower layers that paging indication for voice services is supported. Otherwise, the UE NAS layer informs the lower layers that paging indication for voice services is not supported. If the UE indicates support of the reject paging request in the REGISTRATION REQUEST message and the network decides to accept the reject paging request, then the AMF shall set the reject paging request bit to "reject paging request supported" in the 5GS network feature support IE of the REGISTRATION ACCEPT message. If the UE indicates support of the paging restriction in the REGISTRATION REQUEST message, and the AMF sets: - the reject paging request bit to "reject paging request supported"; - the N1 NAS signalling connection release bit to "N1 NAS signalling connection release supported"; or - both of them; in the 5GS network feature support IE of the REGISTRATION ACCEPT message, and the network decides to accept the paging restriction, then the AMF shall set the paging restriction bit to "paging restriction supported" in the 5GS network feature support IE of the REGISTRATION ACCEPT message. If the UE indicates support of ranging and sidelink positioning in the REGISTRATION REQUEST message and the network supports ranging and sidelink positioning, the AMF shall set the ranging and sidelink positioning supported bit to "Ranging and sidelink positioning supported" in the 5GS network feature support IE of the REGISTRATION ACCEPT message. If the UE has set the Follow-on request indicator to "Follow-on request pending" in the REGISTRATION REQUEST message, or the network has downlink signalling pending, the AMF shall not immediately release the NAS signalling connection after the completion of the registration procedure. If the UE is authorized to use V2X communication over PC5 reference point based on: a) at least one of the following bits in the 5GMM capability IE of the REGISTRATION REQUEST message set by the UE, or already stored in the 5GMM context in the AMF during the previous registration procedure as follows: 1) the V2XCEPC5 bit to "V2X communication over E-UTRA-PC5 supported"; or 2) the V2XCNPC5 bit to "V2X communication over NR-PC5 supported"; and b) the user's subscription context obtained from the UDM as defined in 3GPP TS 23.287[ Architecture enhancements for 5G System (5GS) to support Vehicle-to-Everything (V2X) services ] [6C]; the AMF should not immediately release the NAS signalling connection after the completion of the registration procedure. If the UE is authorized to use A2X communication over PC5 reference point based on: a) at least one of the following bits in the 5GMM capability IE of the REGISTRATION REQUEST message set by the UE, or already stored in the 5GMM context in the AMF during the previous registration procedure as follows: 1) the A2XEPC5 bit to "A2X over E-UTRA-PC5 supported"; or 2) the A2XNPC5 bit to "A2X over NR-PC5 supported"; and b) the user's subscription context obtained from the UDM as defined in 3GPP TS 23.256[ Support of Uncrewed Aerial Systems (UAS) connectivity, identification and tracking; Stage 2 ] [6C]; the AMF should not immediately release the NAS signalling connection after the completion of the registration procedure. If the UE is authorized to use 5G ProSe services based on: a) at least one of the following bits in the 5GMM capability IE of the REGISTRATION REQUEST message set by the UE, or already stored in the 5GMM context in the AMF during the previous registration procedure as follows: 1) the 5G ProSe direct discovery bit to "5G ProSe direct discovery supported"; or 2) the 5G ProSe direct communication bit to "5G ProSe direct communication supported"; and b) the user's subscription context obtained from the UDM as defined in 3GPP TS 23.304[ Proximity based Services (ProSe) in the 5G System (5GS) ] [6E]; the AMF should not immediately release the NAS signalling connection after the completion of the registration procedure. If the Requested DRX parameters IE was included in the REGISTRATION REQUEST message, the AMF shall include the Negotiated DRX parameters IE in the REGISTRATION ACCEPT message and replace any stored Negotiated DRX parameter and use it for the downlink transfer of signalling and user data. The AMF may set the Negotiated DRX parameters IE based on the received Requested DRX parameters IE and operator policy if available. If the Requested NB-N1 mode DRX parameters IE was included in the REGISTRATION REQUEST message, the AMF shall include the Negotiated NB-N1 mode DRX parameters IE in the REGISTRATION ACCEPT message and replace any stored Negotiated NB-N1 mode DRX parameters and use it for the downlink transfer of signalling and user data in NB-N1 mode. The AMF may set the Negotiated NB-N1 mode DRX parameters IE based on the received Requested NB-N1 mode DRX parameters IE and operator policy if available. The AMF shall include the Negotiated extended DRX parameters IE in the REGISTRATION ACCEPT message only if the Requested extended DRX parameters IE was included in the REGISTRATION REQUEST message, and the AMF supports and accepts the use of eDRX. The AMF may set the Negotiated extended DRX parameters IE based on the received Requested extended DRX parameters IE, operator policy, information from NG-RAN and the user's subscription context obtained from the UDM if available. If: a) the UE's USIM is configured with indication that the UE is to receive the SOR transparent container IE, the SOR transparent container IE included in the REGISTRATION ACCEPT message does not successfully pass the integrity check (see 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]); and b) if the UE attempts obtaining service on another PLMNs as specified in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5] annex C; then the UE shall locally release the established N1 NAS signalling connection after sending a REGISTRATION COMPLETE message. If: a) the UE's USIM is configured with indication that the UE is to receive the SOR transparent container IE, the SOR transparent container IE is not included in the REGISTRATION ACCEPT message; and b) the UE attempts obtaining service on another PLMNs as specified in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5] annex C; then the UE shall locally release the established N1 NAS signalling connection. If: a) the UE operates in SNPN access operation mode; b) the ME is configured to indicate that the UE shall expect to receive the steering of roaming information during initial registration procedure for the selected entry of the "list of subscriber data" or the selected PLMN subscription; c) the SOR transparent container IE included in the REGISTRATION ACCEPT message does not successfully pass the integrity check (see 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]); and d) the UE attempts obtaining service on another SNPN as specified in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5] annex C; then the UE shall locally release the established N1 NAS signalling connection after sending a REGISTRATION COMPLETE message. If: a) the UE operates in SNPN access operation mode; b) the ME is configured to indicate that the UE shall expect to receive the steering of roaming information during initial registration procedure for the selected entry of the "list of subscriber data" or the selected PLMN subscription; c) the SOR transparent container IE is not included in the REGISTRATION ACCEPT message; and d) the UE attempts obtaining service on another SNPN as specified in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5] annex C; then the UE shall locally release the established N1 NAS signalling connection. If the REGISTRATION ACCEPT message includes the SOR transparent container IE and the SOR transparent container IE successfully passes the integrity check (see 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]), the ME shall store the received SOR counter as specified in annex C and proceed as follows: a) the UE shall proceed with the behaviour as specified in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5] annex C; and b) if the registration procedure is performed over 3GPP access and the UE attempts obtaining service on another PLMNs or SNPNs as specified in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5] annex C, then the UE may locally release the established N1 NAS signalling connection after sending a REGISTRATION COMPLETE message. Otherwise the UE shall send a REGISTRATION COMPLETE message and not release the current N1 NAS signalling connection locally. If an acknowledgement is requested in the SOR transparent container IE of the REGISTRATION ACCEPT message, the UE acknowledgement is included in the SOR transparent container IE of the REGISTRATION COMPLETE message. In the SOR transparent container IE carrying the acknowledgement, the UE shall set the ME support of SOR-CMCI indicator to "SOR-CMCI supported by the ME". Additionally, if the UE supports access to an SNPN using credentials from a credentials holder and the UE is not operating in SNPN access operation mode, the UE may set the ME support of SOR-SNPN-SI indicator to "SOR-SNPN-SI supported by the ME". Additionally, if the UE supports access to an SNPN providing access for localized services in SNPN, the UE shall set the ME support of SOR-SNPN-SI-LS indicator to "SOR-SNPN-SI-LS supported by the ME" If the SOR transparent container IE successfully passes the integrity check (see 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]) and: a) the list type indicates: 1) "PLMN ID and access technology list", and the SOR transparent container IE indicates a list of preferred PLMN/access technology combinations is provided, then the ME shall replace the highest priority entries in the "Operator Controlled PLMN Selector with Access Technology" list stored in the ME and shall proceed with the behaviour as specified in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5] annex C; or 2) "secured packet", then the ME shall behave as if a SMS is received with protocol identifier set to SIM data download, data coding scheme set to class 2 message and SMS payload as secured packet contents of SOR transparent container IE. The SMS payload is forwarded to UICC as specified in 3GPP TS 23.040[ Technical realization of the Short Message Service (SMS) ] [4A] and the ME shall proceed with the behaviour as specified in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5] annex C; or b) the list type indicates "PLMN ID and access technology list" and the SOR transparent container IE indicates "HPLMN indication that 'no change of the "Operator Controlled PLMN Selector with Access Technology" list stored in the UE is needed and thus no list of preferred PLMN/access technology combinations is provided'", the UE operates in SNPN access operation mode and the SOR transparent container IE includes SOR-SNPN-SI, the ME shall replace SOR-SNPN-SI of the selected entry of the "list of subscriber data" or associated with the selected PLMN subscription, as specified in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5] with the received SOR-SNPN-SI. If the SOR-CMCI is present and the Store SOR-CMCI in ME indicator is set to "Store SOR-CMCI in ME" then the UE shall store or delete the SOR-CMCI in the non-volatile memory of the ME as described in annex C.1. The UE shall proceed with the behaviour as specified in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5] annex C. If the SOR transparent container IE does not pass the integrity check successfully, then the UE shall discard the content of the SOR transparent container IE. If required by operator policy, the AMF shall include the NSSAI inclusion mode IE in the REGISTRATION ACCEPT message (see table 4.6.2.3.1 of subclause 4.6.2.3). Upon receipt of the REGISTRATION ACCEPT message: a) if the message includes the NSSAI inclusion mode IE, the UE shall operate in the NSSAI inclusion mode indicated in the NSSAI inclusion mode IE over the current access within the current PLMN and its equivalent PLMN(s), if any, or the current SNPN ,in the current registration area; or b) otherwise: 1) if the UE has NSSAI inclusion mode for the current PLMN or SNPN and access type stored in the UE, the UE shall operate in the stored NSSAI inclusion mode; 2) if the UE does not have NSSAI inclusion mode for the current PLMN or SNPN and the access type stored in the UE and if the UE is performing the registration procedure over: i) 3GPP access, the UE shall operate in NSSAI inclusion mode D in the current PLMN or SNPN and the current access type; ii) untrusted non-3GPP access, the UE shall operate in NSSAI inclusion mode B in the current PLMN and the current access type; or iii) trusted non-3GPP access, the UE shall operate in NSSAI inclusion mode D in the current PLMN and the current access type; or 3) if the 5G-RG does not have NSSAI inclusion mode for the current PLMN and wireline access stored in the 5G-RG, and the 5G-RG is performing the registration procedure over wireline access, the 5G-RG shall operate in NSSAI inclusion mode B in the current PLMN and the current access type. The AMF may include operator-defined access category definitions in the REGISTRATION ACCEPT message. If the UE receives Operator-defined access category definitions IE in the REGISTRATION ACCEPT message and the Operator-defined access category definitions IE contains one or more operator-defined access category definitions, the UE shall delete any operator-defined access category definitions stored for the RPLMN and shall store the received operator-defined access category definitions for the RPLMN. If the UE receives the Operator-defined access category definitions IE in the REGISTRATION ACCEPT message and the Operator-defined access category definitions IE contains no operator-defined access category definitions, the UE shall delete any operator-defined access category definitions stored for the RPLMN. If the REGISTRATION ACCEPT message does not contain the Operator-defined access category definitions IE, the UE shall not delete the operator-defined access category definitions stored for the RPLMN. If the UE has indicated support for service gap control in the REGISTRATION REQUEST message and: - the REGISTRATION ACCEPT message contains the T3447 value IE, then the UE shall store the new T3447 value, erase any previous stored T3447 value if exists and use the new T3447 value with the timer T3447 next time it is started; or - the REGISTRATION ACCEPT message does not contain the T3447 value IE, then the UE shall erase any previous stored T3447 value if exists and stop the timer T3447 if running. If the T3448 value IE is present in the received REGISTRATION ACCEPT message and the value indicates that this timer is neither zero nor deactivated, the UE shall: a) stop timer T3448 if it is running; and b) start timer T3448 with the value provided in the T3448 value IE. If the UE is using 5GS services with control plane CIoT 5GS optimization, the T3448 value IE is present in the REGISTRATION ACCEPT message and the value indicates that this timer is either zero or deactivated, the UE shall ignore the T3448 value IE and proceed as if the T3448 value IE was not present. If the REGISTRATION ACCEPT message contains the Truncated 5G-S-TMSI configuration IE, then the UE shall store the included truncated 5G-S-TMSI configuration and return a REGISTRATION COMPLETE message to the AMF to acknowledge reception of the truncated 5G-S-TMSI configuration. NOTE 20: The UE provides the truncated 5G-S-TMSI configuration to the lower layers. If the UE is not in NB-N1 mode, the UE has set the RACS bit to "RACS supported" in the 5GMM Capability IE of the REGISTRATION REQUEST message and the REGISTRATION ACCEPT message includes: a) a UE radio capability ID deletion indication IE set to "Network-assigned UE radio capability IDs deletion requested", the UE shall delete any network-assigned UE radio capability IDs associated with the RPLMN or RSNPN and, if the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, the selected entry of the "list of subscriber data" or the selected PLMN subscription stored at the UE, then the UE shall, after the completion of the ongoing registration procedure, initiate a registration procedure for mobility and periodic registration update as specified in subclause 5.5.1.3.2 over the existing N1 NAS signalling connection; or b) a UE radio capability ID IE, the UE shall store the UE radio capability ID as specified in annex C. If the UE has included the service-level device ID set to the CAA-level UAV ID in the Service-level-AA container IE of the REGISTRATION REQUEST message and the REGISTRATION ACCEPT message contains the service-level-AA pending indication in the Service-level-AA container IE, the UE shall return a REGISTRATION COMPLETE message to the AMF to acknowledge reception of the service-level-AA pending indication, and the UE shall not attempt to perform another registration procedure for UAS services until the UUAA-MM procedure is completed, or to establish a PDU session for USS communication or a PDU session for C2 communication until the UUAA-MM procedure is completed successfully. If the UE has included the service-level device ID set to the CAA-level UAV ID in the Service-level-AA container IE of the REGISTRATION REQUEST message and the REGISTRATION ACCEPT message does not contain the service-level-AA pending indication in the Service-level-AA container IE, the UE shall consider the UUAA-MM procedure is not triggered. If the REGISTRATION REQUEST message includes the 5GS registration type IE set to "SNPN onboarding registration" or the network determines that the UE's subscription only allows for configuration of SNPN subscription parameters in PLMN via the user plane, the AMF may start an implementation specific timer for onboarding services when the network considers that the UE is in 5GMM-REGISTERED (i.e. the network receives the REGISTRATION COMPLETE message from UE). NOTE 21: If the AMF considers that the UE is in 5GMM-IDLE, when the implementation specific timer for onboarding services expires and the network considers that the UE is still in state 5GMM-REGISTERED, the AMF can locally de-register the UE; or if the UE is in 5GMM-CONNECTED, the AMF can initiate the network-initiated de-registration procedure (see subclause 5.5.2.3). NOTE 22: The value of the implementation specific timer for onboarding services needs to be large enough to allow a UE to complete the configuration of one or more entries of the "list of subscriber data" taking into consideration that configuration of SNPN subscription parameters in PLMN via the user plane or onboarding services in SNPN involves third party entities outside of the operator's network. If the UE receives the List of PLMNs to be used in disaster condition IE in the REGISTRATION ACCEPT message and the UE supports MINT, the UE shall delete the "list of PLMN(s) to be used in disaster condition" stored in the ME together with the PLMN ID of the RPLMN, if any, and may store the "list of PLMN(s) to be used in disaster condition" included in the List of PLMNs to be used in disaster condition IE in the ME together with the PLMN ID of the RPLMN. If the UE receives the Disaster roaming wait range IE in the REGISTRATION ACCEPT message and the UE supports MINT, the UE shall delete the disaster roaming wait range stored in the ME, if any, and store the disaster roaming wait range included in the Disaster roaming wait range IE in the ME. If the UE receives the Disaster return wait range IE in the REGISTRATION ACCEPT message and the UE supports MINT, the UE shall delete the disaster return wait range stored in the ME, if any, and store the disaster return wait range included in the Disaster return wait range IE in the ME. If the 5GS registration type IE in the REGISTRATION REQUEST message is set to "disaster roaming initial registration" and: a) the MS determined PLMN with disaster condition IE is included in the REGISTRATION REQUEST message, the AMF shall determine the PLMN with disaster condition in the MS determined PLMN with disaster condition IE; b) the MS determined PLMN with disaster condition IE is not included in the REGISTRATION REQUEST message and the Additional GUTI IE is included in the REGISTRATION REQUEST message and contains 5G-GUTI of a PLMN of the country of the PLMN providing disaster roaming services, the AMF shall determine the PLMN with disaster condition in the PLMN identity of the 5G-GUTI; c) the MS determined PLMN with disaster condition IE and the Additional GUTI IE are not included in the REGISTRATION REQUEST message and: 1) the 5GS mobile identity IE contains 5G-GUTI of a PLMN of the country of the PLMN providing disaster roaming services, the AMF shall determine the PLMN with disaster condition in the PLMN identity of the 5G-GUTI; or 2) the 5GS mobile identity IE contains SUCI of a PLMN of the country of the PLMN providing disaster roaming services, the AMF shall determine the PLMN with disaster condition in the PLMN identity of the SUCI; or d) the MS determined PLMN with disaster condition IE is not included in the REGISTRATION REQUEST message, NG-RAN of the PLMN providing disaster roaming services broadcasts disaster roaming indication and: - the Additional GUTI IE is included in the REGISTRATION REQUEST message and contains 5G-GUTI of a PLMN of a country other than the country of the PLMN providing disaster roaming services; or - the Additional GUTI IE is not included and the 5GS mobile identity IE contains 5G-GUTI or SUCI of a PLMN of a country other than the country of the PLMN providing disaster roaming services; the AMF shall determine the PLMN with disaster condition based on the disaster roaming agreement arrangement between mobile network operators. NOTE 23: The disaster roaming agreement arrangement between mobile network operators is out scope of 3GPP. If the AMF determines that a disaster condition applies to the PLMN with disaster condition, and the UE is allowed to be registered for disaster roaming services, the AMF shall set the Disaster roaming registration result value bit in the 5GS registration result IE to "no additional information" in the REGISTRATION ACCEPT message. If the AMF determines that the UE can be registered to the PLMN for normal service, the AMF shall set the Disaster roaming registration result value bit in the 5GS registration result IE to "request for registration for disaster roaming services accepted as registration not for disaster roaming services" in the REGISTRATION ACCEPT message. If the UE indicates "disaster roaming initial registration" in the 5GS registration type IE in the REGISTRATION REQUEST message and the 5GS registration result IE value in the REGISTRATION ACCEPT message is set to: - "request for registration for disaster roaming service accepted as registration not for disaster roaming services", the UE shall consider itself registered for normal service. If the PLMN identity of the registered PLMN is a member of the forbidden PLMN list as specified in subclause 5.3.13A, any such PLMN identity shall be deleted from the corresponding list(s). If UE supports S1 mode, the UE shall initiate the registration procedure for mobility and periodic registration update and indicate that S1 mode is supported as described in subclause 5.5.1.3.2; or - "no additional information", the UE shall consider itself registered for disaster roaming services. If the UE receives the forbidden TAI(s) for the list of "5GS forbidden tracking areas for roaming" IE in the REGISTRATION ACCEPT message, the UE shall store the TAI(s) belonging to the serving PLMN or equivalent PLMN(s) and ignore the TAI(s) which do not belong to the serving PLMN or equivalent PLMN(s) included in the IE, if not already stored, into the list of "5GS forbidden tracking areas for roaming". If the UE receives the forbidden TAI(s) for the list of "5GS forbidden tracking areas for regional provision of service" IE in the REGISTRATION ACCEPT message, the UE shall store the TAI(s) belonging to the serving PLMN or equivalent PLMN(s) and ignore the TAI(s) which do not belong to the serving PLMN or equivalent PLMN(s) included in the IE, if not already stored, into the list of "5GS forbidden tracking areas for regional provision of service". If the UE supporting the reconnection to the network due to RAN timing synchronization status change receives the RAN timing synchronization IE with the RecReq bit set to "Reconnection requested" in the REGISTRATION ACCEPT message, the UE shall operate as specified in subclauses 5.3.1.4, 5.5.1.3.2 and 5.6.1.1. If the UE supports discontinuous coverage, the AMF may include the Discontinuous coverage maximum time offset IE in the REGISTRATION ACCEPT message. If the UE receives, the Discontinuous coverage maximum time offset IE in the REGISTRATION ACCEPT message, the UE shall replace any previously received discontinuous coverage maximum time offset value on the same satellite NG-RAN RAT type and PLMN with the latest received timer value. If for discontinuous coverage the AMF includes Unavailability configuration IE in the REGISTRATION ACCEPT message and sets the End of unavailability report bit to “UE does not need to report end of unavailability”, the UE is not required to initiate the registration procedure for mobility registration update when the unavailability period duration has ended. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.5.1.2.4 |
4,241 | 8.9.3.1 gNB-CU-CP initiated bearer context release | Figure 8.9.3.1-1 shows the procedure used to release the bearer context in the gNB-CU-UP initiated by the gNB-CU-CP. Figure 8.9.3.1-1: Bearer context release over F1-U – gNB-CU-CP initiated 0. Bearer context release (e.g., following an SGNB RELEASE REQUEST message from the MeNB) is triggered in gNB-CU-CP. 1. The gNB-CU-CP sends a BEARER CONTEXT MODIFICATION REQUEST message to the gNB-CU-UP. 2. The gNB-CU-UP responds with a BEARER CONTEXT MODIFICATION RESPONSE carrying the PDCP UL/DL status. 3. F1 UE context modification procedure is performed to stop the data transmission for the UE. It is up to gNB-DU implementation when to stop the UE scheduling. NOTE: step 1-3 are performed only if the PDCP status of the bearer(s) needs to be preserved e.g., for bearer type change. 4. The gNB-CU-CP may receive the UE CONTEXT RELEASE message from the MeNB in EN-DC operation as described in clause 8.4.2.1. 5. and 7. Bearer context release procedure is performed. 6. F1 UE context release procedure is performed to release the UE context in the gNB-DU. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 8.9.3.1 |
4,242 | 5.35.3 Data handling and QoS support with IAB | Control plane and user plane protocol stacks for IAB operation are defined in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [27]. QoS management for IAB can remain transparent to the 5GC. If NG-RAN cannot meet a QoS requirement for a QoS Flow to IAB-related resource constraints, the NG-RAN can reject the request using procedures defined in TS 23.502[ Procedures for the 5G System (5GS) ] [3]. The IAB-UE function can establish a PDU session or PDN connection, e.g. for OAM purpose (protocol stack not shown here). In that case, the IAB-UE obtains an IP address/prefix from the core network using normal UE procedures. The IAB-UE's IP address is different from that of the IAB-node's gNB DU IP address. NOTE: For OAM traffic, based on their specific requirements, operators can select QoS characteristics and reference them by operator specific 5QI(s) or using signalled QoS characteristics within the operator's network. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.35.3 |
4,243 | 4.11.6.3 Configuration of monitoring events for common network exposure | Figure 4.11.6.3-1 represent the information flow to configure monitoring events applicable to both EPC and 5GC using 5GC procedures towards UDM in scenarios where interworking between 5GS and EPC is possible. Figure 4.11.6.3-1: Configuration of monitoring events for common network exposure 1. The AF configures a monitoring event via the SCEF+NEF using the Nnef_EventExposure_Subscribe service operation. 2. SCEF+NEF configures the monitoring event in the UDM+HSS using the Nudm_EventExposure_Subscribe service operation. The combined SCEF+NEF indicates that the monitoring event is also applicable to EPC (i.e. the event must be reported both by 5GC and EPC). Depending on the type of event, the SCEF+NEF may include a SCEF address (i.e. if the event needs to be configured in the MME and the corresponding notification needs to be sent directly to the SCEF). 3. The HSS+UDM configures the monitoring event. For events that need to be reported from a serving node (e.g. location change) the HSS+UDM requests the configuration of the monitoring event to the corresponding serving node in the 5GC and EPC. The HSS+UDM uses the corresponding Event Exposure Subscribe service operation to configure monitoring events in 5GC serving NFs (e.g. Namf_EventExposure_Subscribe or Nsmf_EventExposure_Subscribe). The HSS+UDM uses the procedures defined in TS 23.682[ Architecture enhancements to facilitate communications with packet data networks and applications ] [23] to configure monitoring events in MME. The HSS+UDM provides the MME with the SCEF address during the configuration of the monitoring event in EPC. If the HSS and UDM are deployed as separate network entities, UDM shall use HSS services to configure the monitoring event in EPC as defined in TS 23.632[ User data interworking, coexistence and migration; Stage 2 ] [68]. 4. The HSS+UDM replies the SCEF+NEF with the indication that the monitoring event was successfully configured in 5GC and EPC by sending the Nudm_EventExposure_Subscribe Response. 5. The SCEF+NEF responds to AF by sending Nnef_EventExposure_Subscribe Response. 6. The SCEF+NEF is notified when HSS+UDM or the serving node at the 5GC or EPC detects the corresponding event. The HSS+UDM notifies the SCEF+NEF using the Nudm_EventExposure_Notify service operation. A serving NF in the 5GC notifies the SCEF+NEF using the corresponding Event Exposure Notify service operation (e.g. Namf_EventExposure_Notify or Nsmf_EventExposure_Notify). The MME notifies the SCEF+NEF using the procedures defined in TS 23.682[ Architecture enhancements to facilitate communications with packet data networks and applications ] [23] using the SCEF address provided by the HSS+UDM in step 3. 7. The SCEF+NEF notifies the AF using the 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.11.6.3 |
4,244 | 8.2 Network Identities | The following identities are used in NG-RAN for identifying a specific network entity: - AMF Name: used to identify an AMF. - NR Cell Global Identifier (NCGI): used to identify NR cells globally. The NCGI is constructed from the PLMN identity the cell belongs to and the NR Cell Identity (NCI) of the cell. The PLMN ID included in the NCGI should be the first PLMN ID within the set of PLMN IDs associated to the NR Cell Identity in SIB1, following the order of broadcast. NOTE 1: How to manage the scenario where a different PLMN ID has been allocated by the operator for an NCGI is left to OAM and/or implementation. - gNB Identifier (gNB ID): used to identify gNBs within a PLMN. The gNB ID is contained within the NCI of its cells. - Global gNB ID: used to identify gNBs globally. The Global gNB ID is constructed from the PLMN identity the gNB belongs to and the gNB ID. The MCC and MNC are the same as included in the NCGI. NOTE 2: It is not precluded that a cell served by a gNB does not broadcast the PLMN ID included in the Global gNB ID. - Tracking Area identity (TAI): used to identify tracking areas. The TAI is constructed from the PLMN identity the tracking area belongs to and the TAC (Tracking Area Code) of the Tracking Area. - Single Network Slice Selection Assistance information (S-NSSAI): identifies a network slice. - Network Slice AS Group (NSAG): identifies an association to a slice or a set of slices. An NSAG is defined within a TA, used for slice-based cell reselection and/or slice-based RACH configuration. Values of NSAG IDs associated with different slice or set of slices shall be unique within a TA, also when slice-based cell reselection and slice-based RACH configuration are both supported in the TA. - Network Identifier (NID): identifies an SNPN in combination with a PLMN ID. - Closed Access Group Identifier: identifies a CAG within a PLMN. - Local NG-RAN Node Identifier: used as reference to the NG-RAN node in the I-RNTI. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 8.2 |
4,245 | 5.31.5 Non-IP Data Delivery (NIDD) | Functions for NIDD may be used to handle Mobile Originated (MO) and Mobile Terminated (MT) communication for unstructured data (also referred to as Non-IP). Such delivery to the AF is accomplished by one of the following two mechanisms: - Delivery using the NIDD API; - Delivery using UPF via a Point-to-Point (PtP) N6 tunnel. NIDD is handled using an Unstructured PDU session to the NEF. The UE may obtain an Unstructured PDU session to the NEF during the PDU Session Establishment procedure. Whether or not the NIDD API shall be invoked for a PDU session is determined by the presence of a "NEF Identity for NIDD" for the DNN/S-NSSAI combination in the subscription. If the subscription includes a "NEF Identity for NIDD" corresponding with the DNN and S-NSSAI information, then the SMF selects that NEF and uses the NIDD API for that PDU session. The NEF exposes the NIDD APIs described in TS 23.502[ Procedures for the 5G System (5GS) ] [3] on the N33/Nnef reference point. The NEF uses the provisioned policies to map an AF Identifier and UE Identity to a DNN/S-NSSAI combination if the Reliable Data Service (RDS) is not enabled. If RDS is enabled, the NEF determines the association based on RDS port numbers and the provisioned policies that may be used to map AF Identifier and User identity to a DNN. The NEF also supports distribution of Mobile Terminated messages to a group of UEs based on the NIDD API. If an External Group Identifier is included in the MT NIDD request, the NEF uses the UDM to resolve the External Group Identifier to a list of SUPIs and sends the message to each UE in the group with an established PDU Session. The Protocol Configuration Options (PCO) may be used to transfer NIDD parameters to and from the UE (e.g. maximum packet size). The PCO is sent in the 5GSM signalling between UE and SMF. NIDD parameters are sent to and from the NEF via the N29 interface. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.31.5 |
4,246 | 5.5.1.3.2 Mobility and periodic registration update initiation | The UE in state 5GMM-REGISTERED shall initiate the registration procedure for mobility and periodic registration update by sending a REGISTRATION REQUEST message to the AMF, a) when the UE detects that the current TAI is not in the list of tracking areas that the UE previously registered in the AMF; b) when the periodic registration updating timer T3512 expires in 5GMM-IDLE mode and the UE is not registered for emergency services (see subclause 5.3.7); c) when the UE receives a CONFIGURATION UPDATE COMMAND message indicating "registration requested" in the Registration requested bit of the Configuration update indication IE as specified in subclauses 5.4.4.3; d) when the UE in state 5GMM-REGISTERED.ATTEMPTING-REGISTRATION-UPDATE either receives a paging or the UE receives a NOTIFICATION message with access type indicating 3GPP access over the non-3GPP access for PDU sessions associated with 3GPP access; NOTE 1: As an implementation option, MUSIM UE is allowed to not respond to paging based on the information available in the paging message, e.g. voice service indication. e) upon inter-system change from S1 mode to N1 mode and if the UE previously had initiated an attach procedure or a tracking area updating procedure when in S1 mode; f) when the UE receives an indication of "RRC Connection failure" from the lower layers and does not have signalling pending (i.e. when the lower layer requests NAS signalling connection recovery) except for the case specified in subclause 5.3.1.4; g) when the UE changes the 5GMM capability or the S1 UE network capability or both; h) when the UE's usage setting changes; i) when the UE needs to change the slice(s) it is currently registered to; j) when the UE changes the UE specific DRX parameters; k) when the UE in state 5GMM-REGISTERED.ATTEMPTING-REGISTRATION-UPDATE receives a request from the upper layers to establish an emergency PDU session or perform emergency services fallback; l) when the UE needs to register for SMS over NAS, indicate a change in the requirements to use SMS over NAS, or de-register from SMS over NAS; m) when the UE needs to indicate PDU session status to the network after performing a local release of PDU session(s) as specified in subclauses 6.4.1.5 and 6.4.3.5; n) when the UE in 5GMM-IDLE mode changes the radio capability for NG-RAN or E-UTRAN; o) when the UE receives a fallback indication from the lower layers and does not have signalling pending, see subclauses 5.3.1.4 and 5.3.1.2); p) void; q) when the UE needs to request new LADN information; r) when the UE needs to request the use of MICO mode or needs to stop the use of MICO mode or to request the use of new T3324 value or new T3512 value; s) when the UE in 5GMM-CONNECTED mode with RRC inactive indication enters a cell in the current registration area belonging to an equivalent PLMN of the registered PLMN and not belonging to the registered PLMN; t) when the UE receives over 3GPP access a SERVICE REJECT message or a DL NAS TRANSPORT message, with the 5GMM cause value set to #28 "Restricted service area"; u) when the UE needs to request the use of eDRX, when a change in the eDRX usage conditions at the UE requires different extended DRX parameters, or needs to stop the use of eDRX; NOTE 2: A change in the eDRX usage conditions at the UE can include e.g. a change in the UE configuration, a change in requirements from upper layers or the battery running low at the UE. v) when the UE supporting 5G-SRVCC from NG-RAN to UTRAN changes the mobile station classmark 2 or the supported codecs; w) when the UE in state 5GMM-REGISTERED.ATTEMPTING-REGISTRATION-UPDATE decides to request new network slices after being rejected due to no allowed network slices requested, or request S-NSSAI(s) which have been removed from the rejected NSSAI for the maximum number of UEs reached; x) when the UE is not in NB-N1 mode and the UE has received a UE radio capability ID deletion indication IE set to "Network-assigned UE radio capability IDs deletion requested”; y) when the UE receives a REGISTRATION REJECT message with 5GMM cause values #3, #6 or #7 without integrity protection over another access; z) when the UE needs to request new ciphering keys for ciphered broadcast assistance data; za) when due to manual CAG selection the UE has selected a CAG-ID which is not a CAG-ID authorized based on the "allowed CAG list" for the selected PLMN or a CAG-ID in a PLMN for which the entry in the "CAG information list" does not exist or when the UE has selected, without selecting a CAG-ID, a PLMN for which the entry in the "CAG information list" includes an "indication that the UE is only allowed to access 5GS via CAG cells"; zb) when the UE needs to start, stop or change the conditions for using the WUS assistance information or PEIPS assistance information; zc) when the UE changes the UE specific DRX parameters in NB-N1 mode; zd) when the UE in 5GMM-CONNECTED mode with RRC inactive indication enters a new cell with different RAT in current TAI list or not in current TAI list; ze) when the UE enters state 5GMM-REGISTERED.NORMAL-SERVICE or 5GMM-REGISTERED.NON-ALLOWED-SERVICE (as described in subclause 5.3.5.2) over 3GPP access after the UE has sent a NOTIFICATION RESPONSE message over non-3GPP access in response to reception of a NOTIFICATION message over non-3GPP access as specified in subclause 5.6.3.1; zf) when the UE supporting UAS services is not registered for UAS services and needs to register to the 5GS for UAS services; zg) when the UE supporting MINT needs to perform the registration procedure for mobility and periodic registration update to register to the PLMN offering disaster roaming; zh) when the MUSIM UE supporting the paging timing collision control needs to request a new 5G-GUTI assignment and the UE is not registered for emergency services; NOTE 3: Based on implementation, the MUSIM UE can request a new 5G-GUTI assignment (e.g. when the lower layers request to modify the timing of the paging occasions). zi) when the network supports the paging restriction and the MUSIM UE in state 5GMM-REGISTERED.NON-ALLOWED-SERVICE needs to requests the network to remove the paging restriction; zj) when the UE changes the 5GS Preferred CIoT network behaviour or the EPS Preferred CIoT network behaviour; zk) when the UE that has entered 5GMM-REGISTERED.NO-CELL-AVAILABLE and it has one or more S-NSSAI(s) in pending NSSAI, finds a suitable cell according to 3GPP TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [28]; zl) when the UE is registered for disaster roaming services and receives a request from the upper layers to establish an emergency PDU session or perform emergency services fallback; zm1) when the UE needs to provide the unavailability information; zm2) void; NOTE 3A: How UE determines that it is about to lose satellite coverage is an implementation option. zn) when the UE needs to come out of unavailability period and resume normal services; zo) when the UE in state 5GMM-REGISTERED.ATTEMPTING-REGISTRATION-UPDATE, the UE supports the reconnection to the network due to RAN timing synchronization status change has been requested to reconnect to the network upon receiving an indication of a change in the RAN timing synchronization status (see subclauses 5.4.4.2, 5.5.1.2.4, and 5.5.1.3.4), and the UE receives an indication of a change in the RAN timing synchronization status; or zp) when the UE that supports non-3GPP access path switching needs to trigger non-3GPP access path switching from the old non-3GPP access to the new non-3GPP access that is in the same PLMN. NOTE 4: Non-3GPP access path switching from a non-3GPP access to a wireline access, or from a wireline access to a non-3GPP access, is not specified in this release of the specification. zq) if the UE moves from a tracking area for which the TAI is configured for partially rejected NSSAI to another tracking area within the registration area with aTAI for which the S-NSSAI(s) is supported and the UE still needs to request that S-NSSAI(s). NOTE 4A: The UEs that do not initiate the registration procedure for mobility and periodic registration update in the case above will not receive service for the S-NSSAI(s) that are configured to support the S-NSSAI(s) in the tracking areas supporting the S-NSSAI(s). Operators are recomended to consider the impact of such a configuration, of having partially rejected NSSAI applicable in some tracking areas within a registration area, as it requires the UE to perform mobility and periodic registration update procedure upon mobility within the same registration area. If case b) is the only reason for initiating the registration procedure for mobility and periodic registration update, the UE shall indicate "periodic registration updating" in the 5GS registration type IE; otherwise, if the UE initiates the registration procedure for mobility and periodic registration update due to case Zg), the UE shall indicate "disaster roaming mobility registration updating" in the 5GS registration type IE; otherwise the UE shall indicate "mobility registration updating". If case zl) is the reason for initiating the registration procedure for mobility and periodic registration update and if the UE supports S1 mode and the UE has not disabled its E-UTRA capability, the UE shall: - set the S1 mode bit to "S1 mode supported" in the 5GMM capability IE of the REGISTRATION REQUEST message; and - include the S1 UE network capability IE in the REGISTRATION REQUEST message; If the UE which is not registered for disaster roaming services indicates "mobility registration updating" in the 5GS registration type IE and the UE supports S1 mode and the UE has not disabled its E-UTRA capability, the UE shall: - set the S1 mode bit to "S1 mode supported" in the 5GMM capability IE of the REGISTRATION REQUEST message; - include the S1 UE network capability IE in the REGISTRATION REQUEST message additionally, if the UE supports EPS-UPIP, the UE shall set the EPS-UPIP bit to "EPS-UPIP supported" in the S1 UE network capability IE in the REGISTRATION REQUEST message; and - if the UE supports sending an ATTACH REQUEST message containing a PDN CONNECTIVITY REQUEST message with request type set to "handover" to transfer a PDU session from N1 mode to S1 mode, set the HO attach bit to "attach request message containing PDN connectivity request with request type set to handover to transfer PDU session from N1 mode to S1 mode supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports the LTE positioning protocol (LPP) in N1 mode as specified in 3GPP TS 37.355[ LTE Positioning Protocol (LPP) ] [26], the UE shall set the LPP bit to "LPP in N1 mode supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports the Location Services (LCS) notification mechanisms in N1 mode as specified in 3GPP TS 23.273[ 5G System (5GS) Location Services (LCS); Stage 2 ] [6B], the UE shall set the 5G-LCS bit to "LCS notification mechanisms supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports the user plane positioning using LCS-UPP as specified in 3GPP TS 23.273[ 5G System (5GS) Location Services (LCS); Stage 2 ] [6B], the UE shall set the LCS-UPP bit to "LCS-UPP user plane positioning supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports the user plane positioning using SUPL as specified in 3GPP TS 38.305[ NG Radio Access Network (NG-RAN); Stage 2 functional specification of User Equipment (UE) positioning in NG-RAN ] [67] and 3GPP TS 23.271[ Functional stage 2 description of Location Services (LCS) ] [68], the UE shall set the SUPL bit to "SUPL user plane positioning supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. For all cases except case b), when the UE is not in NB-N1 mode and the UE supports RACS, the UE shall set the RACS bit to "RACS supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports 5G-SRVCC from NG-RAN to UTRAN as specified in 3GPP TS 23.216[ Single Radio Voice Call Continuity (SRVCC); Stage 2 ] [6A], the UE shall set: - the 5G-SRVCC from NG-RAN to UTRAN capability bit to "5G-SRVCC from NG-RAN to UTRAN supported" in the 5GMM capability IE of the REGISTRATION REQUEST message for all cases except case b; and - include the Mobile station classmark 2 IE and the Supported codecs IE in the REGISTRATION REQUEST message for all cases except case b. If the UE supports the restriction on use of enhanced coverage, the UE shall set the RestrictEC bit to "Restriction on use of enhanced coverage supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports network slice-specific authentication and authorization, the UE shall set the NSSAA bit to "network slice-specific authentication and authorization supported" in the 5GMM capability IE of the REGISTRATION REQUEST message for all cases except case b. If the UE supports CAG feature, the UE shall set the CAG bit to "CAG Supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports extended CAG information list, the UE shall set the Ex-CAG bit to "Extended CAG information list supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports enhanced CAG information, the UE shall set the ECI bit to "enhanced CAG information supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports sending of REGISTRATION COMPLETE message for acknowledging the reception of Negotiated PEIPS assistance inforation IE, the UE shall set the RCMAP bit to "Sending of REGISTRATION COMPLETE message for negotiated PEIPS assistance information supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE operating in the single-registration mode performs inter-system change from S1 mode to N1 mode and: a) has one or more stored UE policy sections identified by a UPSI with the PLMN ID part indicating the HPLMN or the selected PLMN, the UE shall set the Payload container type IE to "UE policy container" and include the UE STATE INDICATION message (see annex D) in the Payload container IE of the REGISTRATION REQUEST message; or b) does not have any stored UE policy section identified by a UPSI with the PLMN ID part indicating the HPLMN or the selected PLMN, and the UE needs to send a UE policy container to the network, the UE shall set the Payload container type IE to "UE policy container" and include the UE STATE INDICATION message (see annex D) in the Payload container IE of the REGISTRATION REQUEST message. NOTE 5: In this version of the protocol, the UE can only include the Payload container IE in the REGISTRATION REQUEST message to carry a payload of type "UE policy container". The UE in state 5GMM-REGISTERED shall initiate the registration procedure for mobility and periodic registration update by sending a REGISTRATION REQUEST message to the AMF when the UE needs to request the use of SMS over NAS transport or the current requirements to use SMS over NAS transport change in the UE. The UE shall set the SMS requested bit of the 5GS update type IE in the REGISTRATION REQUEST message as specified in subclause 5.5.1.2.2. When initiating a registration procedure for mobility and periodic registration update and the UE needs to send the 5GS update type IE for a reason different than indicating a change in requirement to use SMS over NAS, the UE shall set the SMS requested bit of the 5GS update type IE in the REGISTRATION REQUEST message to the same value as indicated by the UE in the last REGISTRATION REQUEST message. If the UE no longer requires the use of SMS over NAS, then the UE shall include the 5GS update type IE in the REGISTRATION REQUEST message with the SMS requested bit set to "SMS over NAS not supported". After sending the REGISTRATION REQUEST message to the AMF the UE shall start timer T3510. If timer T3502 is currently running, the UE shall stop timer T3502. If timer T3511 is currently running, the UE shall stop timer T3511. If the last visited registered TAI is available, the UE shall include the last visited registered TAI in the REGISTRATION REQUEST message. The UE shall handle the 5GS mobile identity IE in the REGISTRATION REQUEST message as follows: a) if the UE is operating in the single-registration mode, performs inter-system change from S1 mode to N1 mode, and the UE holds a valid native 4G-GUTI, the UE shall create a 5G-GUTI mapped from the valid native 4G-GUTI as specified in 3GPP TS 23.003[ Numbering, addressing and identification ] [4] and indicate the mapped 5G-GUTI in the 5GS mobile identity IE. Additionally, if the UE holds a valid 5G-GUTI, the UE shall include the 5G-GUTI in the Additional GUTI IE in the REGISTRATION REQUEST message in the following order: 1) a valid 5G-GUTI that was previously assigned by the same PLMN with which the UE is performing the registration, if available; 2) a valid 5G-GUTI that was previously assigned by an equivalent PLMN, if available; and 3) a valid 5G-GUTI that was previously assigned by any other PLMN, if available; and NOTE 6: The 5G-GUTI included in the Additional GUTI IE is a native 5G-GUTI. b) for all other cases, if the UE holds a valid 5G-GUTI, the UE shall indicate the 5G-GUTI in the 5GS mobile identity IE. If the UE is registering with an SNPN and the valid 5G-GUTI was previously assigned by another SNPN, the UE shall additionally include the NID of the other SNPN in the NID IE. If the UE does not operate in SNPN access operation mode, holds two valid native 5G-GUTIs assigned by PLMNs and: 1) one of the valid native 5G-GUTI was assigned by the PLMN with which the UE is performing the registration, then the UE shall indicate the valid native 5G-GUTI assigned by the PLMN with which the UE is performing the registration. In addition, the UE shall include the other valid native 5G-GUTI in the Additional GUTI IE; or 2) none of the valid native 5G-GUTI was assigned by the PLMN with which the UE is performing the registration, then the UE shall indicate the valid native 5G-GUTI assigned over the same access via which the UE is performing the registration. If the UE supports MICO mode and requests the use of MICO mode, then the UE shall include the MICO indication IE in the REGISTRATION REQUEST message. If the UE requests to use an active time value, it shall include the active time value in the T3324 IE in the REGISTRATION REQUEST message. If the UE includes the T3324 IE, it may also request a particular T3512 value by including the Requested T3512 IE in the REGISTRATION REQUEST message. Additionally, if the UE supports strictly periodic registration timer, the UE shall set the Strictly Periodic Registration Timer Indication bit of the MICO indication IE in the REGISTRATION REQUEST message to "strictly periodic registration timer supported". If the UE needs to stop the use of MICO mode, then the UE shall not include the MICO indication IE in the REGISTRATION REQUEST message. If the UE needs to use or change the UE specific DRX parameters, the UE shall include the Requested DRX parameters IE in the REGISTRATION REQUEST message for all cases except case b). If the UE is in NB-N1 mode and if the UE needs to use or change the UE specific DRX parameters for NB-N1 mode, the UE shall include the Requested NB-N1 mode DRX parameters IE in the REGISTRATION REQUEST message for all cases except case b). If the UE supports eDRX and requests the use of eDRX, the UE shall include the Requested extended DRX parameters IE in the REGISTRATION REQUEST message. If the UE needs to request LADN information for specific LADN DNN(s) or indicates a request for LADN information as specified in 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8], the UE shall include the LADN indication IE in the REGISTRATION REQUEST message and: - request specific LADN DNNs by including a LADN DNN value in the LADN indication IE for each LADN DNN for which the UE requests LADN information; or - to indicate a request for LADN information by not including any LADN DNN value in the LADN indication IE. If the UE is initiating the registration procedure for mobility and periodic registration update, the UE may include the Uplink data status IE to indicate which PDU session(s) is: - not associated with control plane only indication; - associated with the access type the REGISTRATION REQUEST message is sent over; and - have pending user data to be sent over user plane or are associated with active multicast MBS session(s). If the UE has one or more active always-on PDU sessions associated with the access type over which the REGISTRATION REQUEST message is sent and the user-plane resources for these PDU sessions are not established, and for cases triggering the REGISTRATION REQUEST message except b), the UE shall include the Uplink data status IE and indicate that the UE has pending user data to be sent for those PDU sessions. If the UE is located outside the LADN service area and inside the registration area assigned by the network, the UE shall not include the PDU session for LADN in the Uplink data status IE. If the UE is in a non-allowed area or is not in an allowed area as specified in subclause 5.3.5, and the UE is in the registration area assigned by the network, the UE shall not include the Uplink data status IE except for emergency services or for high priority access. If the MUSIM UE requests the network to release the NAS signalling connection, the UE shall not include the Uplink data status IE in the REGISTRATION REQUEST message. If the UE has one or more active PDU sessions which are not accepted by the network as always-on PDU sessions and no uplink user data pending to be sent for those PDU sessions, the UE shall not include those PDU sessions in the Uplink data status IE in the REGISTRATION REQUEST message. When the registration procedure for mobility and periodic registration update is initiated in 5GMM-IDLE mode, the UE may include a PDU session status IE in the REGISTRATION REQUEST message, indicating: - which single access PDU sessions associated with the access type the REGISTRATION REQUEST message is sent over are not inactive in the UE; and - which MA PDU sessions are not inactive and having the corresponding user plane resources being established or established in the UE on the access the REGISTRATION REQUEST message is sent over. If the UE received a paging message with the access type indicating non-3GPP access, the UE shall include the Allowed PDU session status IE in the REGISTRATION REQUEST message. If the UE has PDU session(s) associated with non-3GPP access for which the associated S-NSSAI(s) are included in the allowed NSSAI for 3GPP access or the S-NSSAI associated with the PDU session is included in the partially allowed NSSAI for 3GPP access and the TAI where the UE is currently camped is in list of TAs for which the S-NSSAI is allowed, the UE shall indicate the PDU session(s) for which the UE allows to re-establish the user-plane resources over 3GPP access in the Allowed PDU session status IE. Otherwise, the UE shall not indicate any PDU session(s) in the Allowed PDU session status IE. If the UE is in a non-allowed area or the UE is not in an allowed area, the UE shall set the Allowed PDU session status IE as specified in subclause 5.3.5.2. When the Allowed PDU session status IE is included in the REGISTRATION REQUEST message, the UE shall indicate that a PDU session is not allowed to be transferred to the 3GPP access if the 3GPP PS data off UE status is "activated" for the corresponding PDU session and the UE is not using the PDU session to send uplink IP packets for any of the 3GPP PS data off exempt services (see subclause 6.2.10). If the UE operating in the single-registration mode performs inter-system change from S1 mode to N1 mode, the UE: a) shall include the UE status IE with the EMM registration status set to "UE is in EMM-REGISTERED state" in the REGISTRATION REQUEST message; NOTE 7: Inclusion of the UE status IE with this setting corresponds to the indication that the UE is "moving from EPC" as specified in 3GPP TS 23.502[ Procedures for the 5G System (5GS) ] [9], subclause 4.11.1.3.3 and 4.11.2.3. NOTE 8: The value of the 5GMM registration status included by the UE in the UE status IE is not used by the AMF. b) may include the PDU session status IE in the REGISTRATION REQUEST message indicating the status of the PDU session(s) mapped during the inter-system change from S1 mode to N1 mode from the PDN connection(s) for which the EPS indicated that interworking to 5GS is supported, if any (see subclause 6.1.4.1); c) shall include a TRACKING AREA UPDATE REQUEST message as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15] in the EPS NAS message container IE in the REGISTRATION REQUEST message if the registration procedure is initiated in 5GMM-IDLE mode and the UE has received an "interworking without N26 interface not supported" indication from the network; c1) may include a TRACKING AREA UPDATE REQUEST message as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15] in the EPS NAS message container IE in the REGISTRATION REQUEST message if the registration procedure is initiated in 5GMM-IDLE mode and the UE has received an "interworking without N26 interface supported" indication from the network; and d) shall include an EPS bearer context status IE in the REGISTRATION REQUEST message indicating which EPS bearer contexts are active in the UE, if the UE has locally deactivated EPS bearer context(s) for which interworking to 5GS is supported while the UE was in S1 mode without notifying the network. For a REGISTRATION REQUEST message with a 5GS registration type IE indicating "mobility registration updating", if the UE: a) is in NB-N1 mode and: 1) the UE needs to change the slice(s) it is currently registered to within the same registration area; or 2) the UE has entered a new registration area; or b) is not in NB-N1 mode and is not registered for onboarding services in SNPN; the UE shall include the Requested NSSAI IE containing the S-NSSAI(s) corresponding to the network slices to which the UE intends to register and associated mapped S-NSSAI(s), if available, in the REGISTRATION REQUEST message as described in this subclause. When the UE is entering a visited PLMN and intends to register to the slices for which the UE has only HPLMN S-NSSAI(s) available, the UE shall include these HPLMN S-NSSAI(s) in the Requested mapped NSSAI IE This is also applicable when the UE is entering an EHPLMN whose PLMN code is not derived from the IMSI. NOTE 9: The REGISTRATION REQUEST message can include both the Requested NSSAI IE and the Requested mapped NSSAI IE as described below. If the UE is registered for onboarding services in SNPN, the UE shall not include the Requested NSSAI IE in the REGISTRATION REQUEST message. If the UE has allowed NSSAI or configured NSSAI or both for the current PLMN, the Requested NSSAI IE shall include either: a) the configured NSSAI for the current PLMN or SNPN, or a subset thereof as described below; b) the allowed NSSAI for the current PLMN or SNPN, or a subset thereof as described below; or c) the allowed NSSAI for the current PLMN or SNPN, or a subset thereof as described below, plus the configured NSSAI for the current PLMN or SNPN, or a subset thereof as described below; In addition, the Requested NSSAI IE shall include S-NSSAI(s) applicable in the current PLMN or SNPN, and if available the associated mapped S-NSSAI(s) for: a) each PDN connection that is established in S1 mode when the UE is operating in the single-registration mode and the UE is performing an inter-system change from S1 mode to N1 mode; or b) each active PDU session. If the UE does not have S-NSSAI(s) applicable in the current PLMN or SNPN, then the Requested mapped NSSAI IE shall include HPLMN S-NSSAI(s) (e.g. mapped S-NSSAI(s), if available) for: a) each PDN connection established in S1 mode when the UE is operating in the single-registration mode and the UE is performing an inter-system change from S1 mode to N1 mode to a visited PLMN; or b) each active PDU session when the UE is performing mobility from N1 mode to N1 mode to a visited PLMN. NOTE 10: The Requested NSSAI IE is used instead of Requested mapped NSSAI IE in REGISTRATION REQUEST message when the UE enters HPLMN and the EHPLMN list is not present or is empty; or when the UE enters a PLMN whose PLMN code is derived from the IMSI and the EHPLMN list is not empty. The Requested mapped NSSAI IE is used when the UE enters an EHPLMN whose PLMN code is not derived from the IMSI. For a REGISTRATION REQUEST message with a 5GS registration type IE indicating "mobility registration updating", if the UE is in NB-N1 mode and the procedure is initiated for all cases except case a), c), e), i), s), t), w), and x), the REGISTRATION REQUEST message shall not include the Requested NSSAI IE. If the UE has: - no allowed NSSAI for the current PLMN or SNPN; - no configured NSSAI for the current PLMN or SNPN; - neither active PDU session(s) nor PDN connection(s) to transfer associated with an S-NSSAI applicable in the current PLMN or SNPN; and - neither active PDU session(s) nor PDN connection(s) to transfer associated with mapped S-NSSAI(s); and has a default configured NSSAI, then the UE shall: a) include the S-NSSAI(s) in the Requested NSSAI IE of the REGISTRATION REQUEST message using the default configured NSSAI; and b) include the Network slicing indication IE with the Default configured NSSAI indication bit set to "Requested NSSAI created from default configured NSSAI" in the REGISTRATION REQUEST message. If the UE has: - no allowed NSSAI for the current PLMN or SNPN; - no configured NSSAI for the current PLMN or SNPN; - neither active PDU session(s) nor PDN connection(s) to transfer associated with an S-NSSAI applicable in the current PLMN or SNPN - neither active PDU session(s) nor PDN connection(s) to transfer associated with mapped S-NSSAI(s); and - no default configured NSSAI, the UE shall include neither Requested NSSAI IE nor Requested mapped NSSAI IE in the REGISTRATION REQUEST message. If all the S-NSSAI(s) corresponding to the slice(s) to which the UE intends to register are included in the pending NSSAI, the UE shall not include a requested NSSAI in the REGISTRATION REQUEST message. When the UE storing a pending NSSAI intends to register to additional S-NSSAI(s) over the same access type, the UE shall send the requested NSSAI containing the additional S-NSSAI(s) that the UE intends to register to in the REGISTRATION REQUEST message. The requested NSSAI shall not include any S-NSSAI from the pending NSSAI. The subset of configured NSSAI provided in the requested NSSAI consists of one or more S-NSSAIs in the configured NSSAI applicable to the current PLMN or SNPN, where any included S-NSSAI is neither in the rejected NSSAI nor associated to an S-NSSAI in the rejected NSSAI. If the UE is inside the NS-AoS of an S-NSSAI in the rejected NSSAI with a rejection cause value set to "S-NSSAI not available in the current registration area", the S-NSSAI may be included in the requested NSSAI. For case zq, the subset of configured NSSAI provided in the requested NSSAI consists of one or more S-NSSAIs in the configured NSSAI applicable to the current PLMN or SNPN, where any included S-NSSAI is in the partially rejected NSSAI and the current TAI is in the list of TAs for which the S-NSSAI is not rejected. If the UE is inside the NS-AoS of an S-NSSAI in the partially rejected NSSAI and the current TAI is in the list of TAs for which the S-NSSAI is rejected, the S-NSSAI may be included in the requested NSSAI. In addition, if the NSSRG information is available, the subset of configured NSSAI provided in the requested NSSAI shall be associated with at least one common NSSRG value. The UE may also include in the requested NSSAI included in the Requested NSSAI IE or the Requested mapped NSSAI IE or both, the S-NSSAI(s) which were added to configured NSSAI in S1 mode and for which the associated NSSRG information is not available. If the UE is in 5GMM-REGISTERED state over the other access and has already an allowed NSSAI for the other access in the same PLMN or in different PLMNs, all the S-NSSAI(s) in the requested NSSAI included in the Requested NSSAI IE or the Requested mapped NSSAI IE or both for the current access shall share at least an NSSRG value common to all the S-NSSAI(s) of the allowed NSSAI for the other access. If the UE is simultaneously performing the registration procedure on the other access in different PLMNs, the UE shall include S-NSSAIs that share at least a common NSSRG value across all access types. The S-NSSAIs in the pending NSSAI and requested NSSAI shall be associated with at least one common NSSRG value. NOTE 11: If the UE has stored mapped S-NSSAI(s) for the rejected NSSAI, and one or more S-NSSAIs in the stored mapped S-NSSAI(s) for the configured NSSAI are not included in the stored mapped S-NSSAI(s) for the rejected NSSAI, then a S-NSSAI in the configured NSSAI associated to one or more of these mapped S-NSSAI(s) for the configured NSSAI are available to be included in the requested NSSAI together with their mapped S-NSSAI. NOTE 12: If one or more mapped S-NSSAIs in the stored mapped S-NSSAI(s) for the configured NSSAI are not included in the stored rejected NSSAI for the failed or revoked NSSAA, a S-NSSAI in the configured NSSAI associated to one or more of these mapped S-NSSAI(s) for the configured NSSAI are available to be included in the registration request together with their mapped S-NSSAI. NOTE 13: There is no need to consider the case that the UE is simultaneously performing the registration procedure on the other access in the same PLMN, due to that the UE is not allowed to initiate the registration procedure over one access when the registration over the other access to the same PLMN is going on. If: a) the UE is registered to current PLMN over the other access and has NSSRG information available; b) the UE is attempting mobility registration to the same current PLMN from other PLMN in the current access; and c) the UE has PDU session(s) or PDN connection(s) associated with NSSAI not sharing part of NSSRG available of the current PLMN; then the UE locally releases these PDU session(s) or PDN connection(s), as the NSSAI for these PDU session(s) or PDN connection(s) will not be included in the requested or the requested mapped NSSAI in the current PLMN due to its lack of association to the common NSSRG of the current PLMN. The subset of allowed NSSAI provided in the requested NSSAI consists of one or more S-NSSAIs in the allowed NSSAI for this PLMN. If the UE supports the S-NSSAI time validity information, S-NSSAI time validity information is available for an S-NSSAI, and the S-NSSAI time validity information indicates that the S-NSSAI is not available, the UE shall not include the S-NSSAI in the Requested NSSAI IE of the REGISTRATION REQUEST message. If the UE has S-NSSAI time validity information over the other access in the same PLMN and the S-NSSAI time validity information indicates that the S-NSSAI is not available, the UE shall not include the S-NSSAI in the Requested NSSAI IE of the REGISTRATION REQUEST message for the current access type. NOTE 14: How the UE selects the subset of configured NSSAI or allowed NSSAI to be provided in the requested NSSAI is implementation specific. The UE can take preferences indicated by the upper layers (e.g. policies like URSP, applications) and UE local configuration into account. NOTE 15: The number of S-NSSAI(s) included in the requested NSSAI cannot exceed eight. If the UE supports NSAG, the UE shall set the NSAG bit to "NSAG supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports sending of REGISTRATION COMPLETE message for acknowledging the reception of NSAG information IE in the REGISTRATION ACCEPT message, the UE shall set the RCMAN bit to "Sending of REGISTRATION COMPLETE message for NSAG information supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports the unavailability period, the UE shall set the UN-PER bit to "unavailability period supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports network slice replacement, the UE shall set the NSR bit to "network slice replacement supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. For case zm1), if the network indicated support for the unavailability period in the last registration procedure and the UE is able to store its 5GMM and 5GSM contexts, the UE shall include the Unavailability information IE, set the Follow-on request indicator to "No follow-on request pending" in the REGISTRATION REQUEST message. In addition, the UE shall not include the Uplink data status IE or the Allowed PDU session status IE in the REGISTRATION REQUEST message even if the UE has one or more active always-on PDU sessions associated with the 3GPP access. If the UE includes the Unavailability information IE to indicate the type of the unavailability period and the UE will be unavailable due to NR satellite access discontinuous coverage, the UE shall set the Unavailability type bit to "unavailability due to discontinuous coverage" in the Unavailability information IE. For case zm1, the UE should initiate the registration procedure for mobility and periodic registration update only if the UE can determine, based on its implementation, that there is enough time to complete the procedure before the start of the unavailability period. NOTE 15A: If the UE is unable to store its 5GMM and 5GSM contexts, the UE triggers the de-registration procedure. Ability to store the 5GMM information for UEs not operating in SNPN access operation mode as described in Annex C.1 does not imply the ability to store the 5GMM and 5GSM contexts. NOTE 15B: If the UE is able to store its 5GMM and 5GSM contexts, the UE can store the 5GMM and 5GSM contexts even if the registration procedure for mobility and periodic registration update is not completed successfully. The UE shall set the Follow-on request indicator to "Follow-on request pending", if the UE: a) initiates the registration procedure for mobility and periodic registration update upon request of the upper layers to establish an emergency PDU session; b) initiates the registration procedure for mobility and periodic registration update upon receiving a request from the upper layers to perform emergency services fallback; or c) needs to prolong the established NAS signalling connection after the completion of the registration procedure for mobility and periodic registration update (e.g. due to uplink signalling pending but no user data pending). NOTE 16: The UE does not have to set the Follow-on request indicator to 1 even if the UE has to request resources for V2X communication over PC5 reference point, 5G ProSe direct discovery over PC5, 5G ProSe direct communication over PC5 or ranging and sidelink positioning over PC5 or A2X communication over PC5 reference point. For case n), the UE shall include the 5GS update type IE in the REGISTRATION REQUEST message with the NG-RAN-RCU bit set to "UE radio capability update needed". Additionally, if the UE is not in NB-N1 mode, the UE supports RACS and the UE has an applicable UE radio capability ID for the new UE radio configuration in the serving PLMN or SNPN, the UE shall include the applicable UE radio capability ID in the UE radio capability ID of the REGISTRATION REQUEST message. NOTE 16A: For cases n, if the UE supports RACS irrespective whether the UE has an applicable UE radio capability ID for the new UE radio configuration in the selected PLMN the 5GS update type IE in the REGISTRATION REQUEST message with the NG-RAN-RCU bit is set to "UE radio capability update needed". If the UE is in the 5GMM-CONNECTED mode and the UE changes the radio capability for NG-RAN or E-UTRAN, the UE may locally release the established N1 NAS signalling connection and enter the 5GMM-IDLE mode. Then, the UE shall initiate the registration procedure for mobility and periodic registration update including the 5GS update type IE in the REGISTRATION REQUEST message with the NG-RAN-RCU bit set to " UE radio capability update needed". For case o), the UE shall include the Uplink data status IE in the REGISTRATION REQUEST message indicating the PDU session(s) without active user-plane resources for which the UE has pending user data to be sent, if any, and the PDU session(s) for which user-plane resources were active prior to receiving the fallback indication, if any. If the UE has joined one or more multicast MBS session and was in 5GMM-CONNECTED mode with RRC inactive indication before receiving the fallback indication from the lower layers, the UE shall include the Uplink data status IE in the REGISTRATION REQUEST message indicating the PDU session(s) that are associated to the one or more multicast MBS session. If the UE is in a non-allowed area or if the UE is not in allowed area, the UE shall not include the Uplink data status IE in REGISTRATION REQUEST message, except if the PDU session for which user-plane resources were active prior to receiving the fallback indication is an emergency PDU session, or if the UE is configured for high priority access in the selected PLMN or SNPN as specified in subclause 5.3.5. For case f), the UE shall include the Uplink data status IE in the REGISTRATION REQUEST message indicating the PDU session(s) for which the UE has uplink user data pending and the PDU session(s) for which user-plane resources were active prior to receiving "RRC Connection failure" indication from the lower layers, if any. If the UE has joined one or more multicast MBS session and was in 5GMM-CONNECTED mode with RRC inactive indication before receiving the indication of "RRC Connection failure" from the lower layers or before receiving the indication that the resumption of the RRC connection has failed from the lower layers, the UE shall include the Uplink data status IE in the REGISTRATION REQUEST message indicating the PDU session(s) that are associated to the one or more multicast MBS session. If the UE is in non-allowed area or not in allowed area, the UE shall not include the Uplink data status IE in REGISTRATION REQUEST message, except that the PDU session for which user-plane resources were active prior to receiving the "RRC Connection failure"indication is emergency PDU session, or that the UE is configured for high priority access in selected PLMN or SNPN, as specified in subclause 5.3.5. If the UE supports service gap control, then the UE shall set the SGC bit to "service gap control supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. For case a), x) or if the UE operating in the single-registration mode performs inter-system change from S1 mode to N1 mode, the UE shall: a) if the UE has an applicable network-assigned UE radio capability ID for the current UE radio configuration in the selected PLMN or SNPN, include the applicable network-assigned UE radio capability ID in the UE radio capability ID IE of the REGISTRATION REQUEST message; and b) if the UE: 1) does not have an applicable network-assigned UE radio capability ID for the current UE radio configuration in the selected PLMN or SNPN; and 2) has an applicable manufacturer-assigned UE radio capability ID for the current UE radio configuration, include the applicable manufacturer-assigned UE radio capability ID in the UE radio capability ID IE of the REGISTRATION REQUEST message. For all cases except cases b) and z), if the UE supports ciphered broadcast assistance data and the UE needs to obtain new ciphering keys, the UE shall include the Additional information requested IE with the CipherKey bit set to "ciphering keys for ciphered broadcast assistance data requested" in the REGISTRATION REQUEST message. For case z), the UE shall include the Additional information requested IE with the CipherKey bit set to "ciphering keys for ciphered broadcast assistance data requested" in the REGISTRATION REQUEST message. For case a), if the UE supports ciphered broadcast assistance data and the UE detects that one or more ciphering keys stored at the UE is not applicable in the current TAI, the UE should include the Additional information requested IE with the CipherKey bit set to "ciphering keys for ciphered broadcast assistance data requested" in the REGISTRATION REQUEST message. For case b), if the UE supports ciphered broadcast assistance data and the remaining validity time for one or more ciphering keys stored at the UE is less than timer T3512, the UE should include the Additional information requested IE with the CipherKey bit set to "ciphering keys for ciphered broadcast assistance data requested" in the REGISTRATION REQUEST message. The UE shall set the WUSA bit to "WUS assistance information reception supported" in the 5GMM capability IE if the UE supports WUS assistance information. The UE may include its UE paging probability information in the Requested WUS assistance information IE if the UE has set the WUSA bit to "WUS assistance information reception supported" in the 5GMM capability IE and does not have an active emergency PDU session. The UE shall set the NR-PSSI bit to "NR paging subgrouping supported" in the 5GMM capability IE if the UE supports PEIPS assistance information, is not registered for emergency services and does not have an active emergency PDU session. The UE may include its UE paging probability information in the Requested PEIPS assistance information IE if the UE has set the NR-PSSI bit to "NR paging subgrouping supported" in the 5GMM capability IE. If the network supports the N1 NAS signalling connection release, and the MUSIM UE requests the network to release the NAS signalling connection, the UE shall set Request type to "NAS signalling connection release" in the UE request type IE, set the Follow-on request indicator to "No follow-on request pending" and, if the network supports the paging restriction, may set the paging restriction preference in the Paging restriction IE in the REGISTRATION REQUEST message. In addition, the UE shall not include the Uplink data status IE or the Allowed PDU session status IE in the REGISTRATION REQUEST message even if the UE has one or more active always-on PDU sessions associated with the 3GPP access. NOTE 17: If the network has already indicated support for N1 NAS signalling connection release in the current stored registration area and the UE doesn't have an emergency PDU session established, the MUSIM UE is allowed to request the network to release the NAS signalling connection during registration procedure for mobility and periodic registration update that is due to mobility outside the registration area even before detecting whether the network supports the N1 NAS signalling connection release in the current TAI. NOTE 18: If the network has already indicated support for paging restriction in the current stored registration area and the UE doesn't have an emergency PDU session established, the MUSIM UE is allowed to include paging restriction together with the request to the network to release the NAS signalling connection during registration procedure for mobility and periodic registration update that is due to mobility outside the registration area even before detecting whether the network supports the paging restriction in the current TAI. For case zi), the UE shall not include the Paging restriction IE in the REGISTRATION REQUEST message. If the UE is in 5GMM-IDLE mode and the network supports the N1 NAS signalling connection release, the UE may include the UE request type IE and set Request type to "NAS signalling connection release" to remove the paging restriction and request the release of the NAS signalling connection at the same time. In addition, the UE shall not include the Uplink data status IE in the REGISTRATION REQUEST message. If the UE does not have a valid 5G NAS security context and the UE is sending the REGISTRATION REQUEST message after an inter-system change from S1 mode to N1 mode in 5GMM-IDLE mode, the UE shall send the REGISTRATION REQUEST message without including the NAS message container IE. The UE shall include the entire REGISTRATION REQUEST message (i.e. containing cleartext IEs and non-cleartext IEs, if any) in the NAS message container IE that is sent as part of the SECURITY MODE COMPLETE message as described in subclauses 4.4.6 and 5.4.2.3. If the UE indicates "mobility registration updating" in the 5GS registration type IE and supports V2X as specified in 3GPP TS 24.587[ Vehicle-to-Everything (V2X) services in 5G System (5GS); Stage 3 ] [19B], the UE shall set the V2X bit to "V2X supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE indicates "mobility registration updating" in the 5GS registration type IE and supports V2X communication over E-UTRA-PC5 as specified in 3GPP TS 24.587[ Vehicle-to-Everything (V2X) services in 5G System (5GS); Stage 3 ] [19B], the UE shall set the V2XCEPC5 bit to "V2X communication over E-UTRA-PC5 supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE indicates "mobility registration updating" in the 5GS registration type IE and supports V2X communication over NR-PC5 as specified in 3GPP TS 24.587[ Vehicle-to-Everything (V2X) services in 5G System (5GS); Stage 3 ] [19B], the UE shall set the V2XCNPC5 bit to "V2X communication over NR-PC5 supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. The UE shall send the REGISTRATION REQUEST message including the NAS message container IE as described in subclause 4.4.6: a) when the UE is sending the message from 5GMM-IDLE mode, the UE has a valid 5G NAS security context, and needs to send non-cleartext IEs; or b) when the UE is sending the message after an inter-system change from S1 mode to N1 mode in 5GMM-IDLE mode and the UE has a valid 5G NAS security context and needs to send non-cleartext IEs. The UE with a valid 5G NAS security context shall send the REGISTRATION REQUEST message without including the NAS message container IE when the UE does not need to send non-cleartext IEs and the UE is sending the message: a) from 5GMM-IDLE mode; or b) after an inter-system change from S1 mode to N1 mode in 5GMM-IDLE mode. If the UE is sending the REGISTRATION REQUEST message after an inter-system change from S1 mode to N1 mode in 5GMM-CONNECTED mode and the UE needs to send non-cleartext IEs, the UE shall cipher the NAS message container IE using the mapped 5G NAS security context and send the REGISTRATION REQUEST message including the NAS message container IE as described in subclause 4.4.6. If the UE does not need to send non-cleartext IEs, the UE shall send the REGISTRATION REQUEST message without including the NAS message container IE. If the REGISTRATION REQUEST message includes a NAS message container IE, the AMF shall process the REGISTRATION REQUEST message that is obtained from the NAS message container IE as described in subclause 4.4.6. If the UE is in NB-N1 mode, then the UE shall set the Control plane CIoT 5GS optimization bit to "Control plane CIoT 5GS optimization supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. For all cases except case b, if the UE is capable of NB-S1 mode, then the UE shall set the Control plane CIoT EPS optimization bit to "Control plane CIoT EPS optimization supported" in the S1 UE network capability IE of the REGISTRATION REQUEST message. If the registration procedure for mobility and periodic registration update is initiated and there is request from the upper layers to perform "emergency services fallback" pending, the UE shall send a REGISTRATION REQUEST message without an Uplink data status IE. If the UE supports N3 data transfer and multiple user-plane resources in NB-N1 mode (see 3GPP TS 36.306[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio access capabilities ] [25D], 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [25A]), then the UE shall set the Multiple user-plane resources support bit to "Multiple user-plane resources supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. The UE shall set the ER-NSSAI bit to "Extended rejected NSSAI supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports the NSSRG, then the UE shall set the NSSRG bit to "NSSRG supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. For case zf), the UE shall include the service-level device ID in the Service-level-AA container IE of the REGISTRATION REQUEST message and set the value to the CAA-level UAV ID. The UE shall include the service-level-AA server address in the Service-level-AA container IE of the REGISTRATION REQUEST message and set the value to the USS address, if it is provided by the upper layers. The UE shall include the service-level-AA payload in the Service-level-AA container IE of the REGISTRATION REQUEST message and shall set the service-level-AA payload type, if the service-level-AA payload is provided by upper layers. NOTE 18: The service-level-AA payload can be of type "C2 authorization payload". The C2 authorization payload can include one or both of an indication of the request for direct C2 communication and pairing information for direct C2 communication. If the UE supports 5G ProSe direct discovery as specified in 3GPP TS 24.554[ Proximity-services (ProSe) in 5G System (5GS) protocol aspects; Stage 3 ] [19E], the UE shall set the 5G ProSe-dd bit to "5G ProSe direct discovery supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports 5G ProSe direct communication as specified in 3GPP TS 24.554[ Proximity-services (ProSe) in 5G System (5GS) protocol aspects; Stage 3 ] [19E], the UE shall set the 5G ProSe-dc bit to "5G ProSe discovery communication supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports acting as 5G ProSe layer-2 UE-to-network relay UE as specified in 3GPP TS 24.554[ Proximity-services (ProSe) in 5G System (5GS) protocol aspects; Stage 3 ] [19E], the UE shall set the 5G ProSe-l2relay bit to "Acting as a 5G ProSe layer-2 UE-to-network relay UE supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports acting as 5G ProSe layer-3 UE-to-network relay UE as specified in 3GPP TS 24.554[ Proximity-services (ProSe) in 5G System (5GS) protocol aspects; Stage 3 ] [19E], the UE shall set the 5G ProSe-l3relay bit to "Acting as a 5G ProSe layer-3 UE-to-network relay UE supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports acting as 5G ProSe layer-2 UE-to-network remote UE as specified in 3GPP TS 24.554[ Proximity-services (ProSe) in 5G System (5GS) protocol aspects; Stage 3 ] [19E], the UE shall set the 5G ProSe-l2rmt bit to "Acting as a 5G ProSe layer-2 UE-to-network remote UE supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports acting as 5G ProSe layer-3 UE-to-network remote UE as specified in 3GPP TS 24.554[ Proximity-services (ProSe) in 5G System (5GS) protocol aspects; Stage 3 ] [19E], the UE shall set the 5G ProSe-l3rmt bit to "Acting as a 5G ProSe layer-3 UE-to-network remote UE supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports acting as 5G ProSe layer-2 UE-to-UE relay UE as specified in 3GPP TS 24.554[ Proximity-services (ProSe) in 5G System (5GS) protocol aspects; Stage 3 ] [19E], the UE shall set the 5G ProSe-l2U2U relay bit to "Acting as a 5G ProSe layer-2 UE-to-UE relay UE supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports acting as 5G ProSe layer-3 UE-to-UE relay UE as specified in 3GPP TS 24.554[ Proximity-services (ProSe) in 5G System (5GS) protocol aspects; Stage 3 ] [19E], the UE shall set the 5G ProSe-l3U2U relay bit to "Acting as a 5G ProSe layer-3 UE-to-UE relay UE supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports acting as 5G ProSe layer-2 end UE as specified in 3GPP TS 24.554[ Proximity-services (ProSe) in 5G System (5GS) protocol aspects; Stage 3 ] [19E], the UE shall set the 5G ProSe-l2end bit to "Acting as a 5G ProSe layer-2 end UE supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports acting as 5G ProSe layer-3 end UE as specified in 3GPP TS 24.554[ Proximity-services (ProSe) in 5G System (5GS) protocol aspects; Stage 3 ] [19E], the UE shall set the 5G ProSe-l3end bit to "Acting as a 5G ProSe layer-3 end UE supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. For all cases except case b, if the MUSIM UE supports the N1 NAS signalling connection release, then the UE shall set the N1 NAS signalling connection release bit to "N1 NAS signalling connection release supported" in the 5GMM capability IE of the REGISTRATION REQUEST message otherwise the UE shall not set the N1 NAS signalling connection release bit to "N1 NAS signalling connection release supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. For all cases except case b, if the MUSIM UE supports the paging indication for voice services, then the UE shall set the paging indication for voice services bit to "paging indication for voice services supported" in the 5GMM capability IE of the REGISTRATION REQUEST message otherwise the UE shall not set the paging indication for voice services bit to "paging indication for voice services supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. For all cases except case b, if the MUSIM UE supports the reject paging request, then the UE shall set the reject paging request bit to "reject paging request supported" in the 5GMM capability IE of the REGISTRATION REQUEST message otherwise the UE shall not set the reject paging request bit to "reject paging request supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. For all cases except case b, if the MUSIM UE sets: - the reject paging request bit to "reject paging request supported"; - the N1 NAS signalling connection release bit to "N1 NAS signalling connection release supported"; or - both of them; and supports the paging restriction, then the UE shall set the paging restriction bit to "paging restriction supported" in the 5GMM capability IE of the REGISTRATION REQUEST message otherwise the UE shall not set the paging restriction bit to "paging restriction supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports MINT, the UE shall set the MINT bit to "MINT supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports slice-based N3IWF selection, the UE shall set the SBNS bit to "Slice-based N3IWF selection supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports slice-based TNGF selection, the UE shall set the SBTS bit to "Slice-based TNGF selection supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports UAS services, the UE shall set the UAS bit to "UAS services supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports A2X over E-UTRA-PC5 as specified in 3GPP TS 24.577[ Aircraft-to-Everything (A2X) services in 5G System (5GS) protocol aspects; Stage 3 ] [60], the UE shall set the A2XEPC5 bit to "A2X over E-UTRA-PC5 supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports A2X over NR-PC5 as specified in 3GPP TS 24.577[ Aircraft-to-Everything (A2X) services in 5G System (5GS) protocol aspects; Stage 3 ] [60], the UE shall set the A2XNPC5 bit to "A2X over NR-PC5 supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports A2X over Uu as specified in 3GPP TS 24.577[ Aircraft-to-Everything (A2X) services in 5G System (5GS) protocol aspects; Stage 3 ] [60], the UE shall set the A2X-Uu bit to "A2X over Uu supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports SL positioning server UE as specified in 3GPP TS 23.586[ Architectural Enhancements to support Ranging based services and Sidelink Positioning ] [63] over PC5, the UE shall set the SLPSPC5 bit to "SL positioning server UE over PC5 supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. For case zg), if the UE has determined the MS determined PLMN with disaster condition as specified in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5], and: a) the MS determined PLMN with disaster condition is the HPLMN and: 1) the Additional GUTI IE is included in the REGISTRATION REQUEST message and does not contain a valid 5G-GUTI that was previously assigned by the HPLMN; or 2) the Additional GUTI IE is not included in the REGISTRATION REQUEST message and the 5GS mobile identity IE contains neither the SUCI nor a valid 5G-GUTI that was previously assigned by the HPLMN; or b) the MS determined PLMN with disaster condition is not the HPLMN and: 1) the Additional GUTI IE is included in the REGISTRATION REQUEST message and does not contain a valid 5G-GUTI that was previously assigned by the MS determined PLMN with disaster condition; or 2) the Additional GUTI IE is not included in the REGISTRATION REQUEST message and the 5GS mobile identity IE does not contain a valid 5G-GUTI that was previously assigned by the MS determined PLMN with disaster condition; the UE shall include in the REGISTRATION REQUEST message the MS determined PLMN with disaster condition IE indicating the MS determined PLMN with disaster condition. NOTE 19: If the UE initiates the registration procedure for disaster roaming services, and the MS determined PLMN with disaster condition cannot be determined when an NG-RAN cell of the PLMN broadcasts the disaster related indication as specified in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5], the UE does not include in the REGISTRATION REQUEST message the MS determined PLMN with disaster condition IE but includes the Additional GUTI IE or the 5GS mobile identity IE or both as specified in subclauses 5.5.1.2.2. For case zh) the UE shall indicate "mobility registration updating" in the 5GS registration type IE of the REGISTRATION REQUEST message. For case zp), the UE shall send the REGISTRATION REQUEST message over the new non-3GPP access. The UE shall include the Uplink data status IE in the REGISTRATION REQUEST message indicating the MA PDU session ID(s) or the single access PDU session ID(s) whose user plan resources are to be switched from the old non-3GPP access to the new non-3GPP access or to be established over the new non-3GPP access, if any. If the UE requests the network to keep using the user plane resources of the old non-3GPP access during path switching to the new non-3GPP access, the UE shall include the Non-3GPP path switching information IE in the REGISTRATION REQUEST message and set the NSONR bit to "non-3GPP path switching while using old non-3GPP resources requested". If the UE supports event notification, the UE shall set the EventNotification bit to "Event notification supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports access to an SNPN using credentials from a credentials holder and the UE is in its HPLMN or EHPLMN or a subscribed SNPN, the UE shall set the SSNPNSI bit to "SOR-SNPN-SI supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports equivalent SNPNs, the UE shall set the ESI bit to "equivalent SNPNs supported" in the 5GMM capability IE of the REGISTRATION REQUEST message.If the UE supports LADN per DNN and S-NSSAI, the UE shall set the LADN-DS bit to "LADN per DNN and S-NSSAI supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports the reconnection to the network due to RAN timing synchronization status change, the UE shall set the Reconnection to the network due to RAN timing synchronization status change (RANtiming) bit to "Reconnection to the network due to RAN timing synchronization status change supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports MPS indicator update via the UE configuration update procedure, the UE shall set the MPSIU bit to "MPS indicator update supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports MCS indicator update via the UE configuration update procedure, the UE shall set the MCSIU bit to "MCS indicator update supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports ranging and sidelink positioning over PC5 as specified in 3GPP TS 24.514[ Ranging based services and sidelink positioning in 5G system(5GS); Stage 3 ] [62] and supports: a) V2X communication over PC5 as specified in 3GPP TS 24.587[ Vehicle-to-Everything (V2X) services in 5G System (5GS); Stage 3 ] [19B]; b) 5G ProSe direct discovery and 5G ProSe direct communication as specified in 3GPP TS 24.554[ Proximity-services (ProSe) in 5G System (5GS) protocol aspects; Stage 3 ] [19E]; or c) both a) and b), the UE shall set the RSPPC5 bit to "Ranging and sidelink positioning over PC5 supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports the partial network slice, the UE shall set the PNS bit to "Partial network slice supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports network slice usage control, the UE shall set the NSUC bit to "Network slice usage control supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports the S-NSSAI time validity information, the UE shall set the TempNS bit to "S-NSSAI time validity information supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports the S-NSSAI location validity information, the UE shall set the SLVI bit to "S-NSSAI location validity information supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. Figure 5.5.1.3.2.1: Registration procedure for mobility and periodic registration update | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.5.1.3.2 |
4,247 | 5.3.2 Physical-layer processing for physical uplink shared channel | The uplink physical-layer processing of transport channels consists of the following steps: - Transport Block CRC attachment; - Code block segmentation and Code Block CRC attachment; - Channel coding: LDPC coding; - Physical-layer hybrid-ARQ processing; - Rate matching; - Scrambling; - Modulation: π/2 BPSK (with transform precoding only), QPSK, 16QAM, 64QAM and 256QAM; - Layer mapping, transform precoding (enabled/disabled by configuration), and pre-coding; - Mapping to assigned resources and antenna ports. The UE transmits at least one symbol with demodulation reference signal on each layer on each frequency hop in which the PUSCH is transmitted, and up to 3 additional DMRS can be configured by higher layers. Phase Tracking RS may be transmitted on additional symbols to aid receiver phase tracking. The UL-SCH physical layer model is described in TS 38.202[ NR; Services provided by the physical layer ] [20]. For configured grants operation with shared spectrum channel access, described in clause 10.3, a CG-UCI (Configured Grant Uplink Control Information) can be transmitted in PUSCH scheduled by configured uplink grant. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.2 |
4,248 | Annex A (informative): Relationship between Service-Based Interfaces and Reference Points | Service-Based Interfaces and Reference Points are two different ways to model interactions between architectural entities. A Reference Point is a conceptual point at the conjunction of two non-overlapping functional groups (see TR 21.905 [1]). In figure A-1 the functional groups are equivalent to Network Functions. A reference point can be replaced by one or more service-based interfaces which provide equivalent functionality. Figure A-1: Example show a Reference Point replaced by two Service based Interfaces Figure A-2: Example showing a Reference Point replaced by a single Service based Interface Reference points exist between two specific Network Functions. Even if the functionality is equal on two reference points between different Network Functions there has to be a different reference point name. Using the service-based interface representation it is immediately visible that it is the same service-based interface and that the functionality is equal on each interface. Figure A-3: Reference Points vs. Service-based Interfaces representation of equal functionality on the interfaces A NF may expose one or more services through Service based interfaces. Figure A-4: One or more Services exposed by one Network Function | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | Annex |
4,249 | 5.2.8.3 Nsmf_EventExposure Service 5.2.8.3.1 General | Service description: This service provides events related to PDU Sessions towards consumer NF. The service operations exposed by this service allow other NFs to subscribe and get notified of events happening on PDU Sessions. The following are the key functionalities of this NF service. - Allow consumer NFs to Subscribe and unsubscribe for an Event ID on PDU Session(s); - Allow the NWDAF to collect data for network data analytics from SMF as specified in TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [50] and from UPF as specified in clause 4.15.4.5; - Notifying events on the PDU Session to the subscribed NFs; and - Allow consumer NFs to acknowledge or respond to an event notification. The following events can be subscribed by a NF consumer (Event ID is defined in clause 4.15.1): - UE IP address / Prefix allocation/change: The event notification may contain a new UE IP address / Prefix or an indication of which UE IP address / Prefix has been released. - PDU Session Establishment and/or PDU Session Release. The event notification may contain following information: - PDU Session Type. - DNN. - UE IP address/Prefix. - UP path change: a notification corresponding to this event is sent when the UE IP address / Prefix and / or DNAI and /or the N6 traffic routing information has changed. The event notification may contain following information: - the type of notification ("EARLY" or "LATE"). - for both the source and target UP path between the UE and the DN, the corresponding information is provided when it has changed: - DNAI. - UE IP address / Prefix. - N6 traffic routing information. - Candidate DNAI(s) for the PDU Session. - Change of common EAS. NOTE 1: UP path change notification, DNAI and N6 traffic routing information are further described in clause 5.6.7 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. - QoS Monitoring: the event notification may contain the QoS Monitoring report for the QoS parameter(s) to be measured defined in clause 5.45 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. Implicit subscription of the PCF on behalf of the NEF/AF as part of setting PCC rule(s) may trigger SMF to send this event notification. - Change of Access Type; The event notification contains the new Access Type for the PDU Session. For MA PDU Session the Change of Access Type may include two Access Type information that the user is currently using. - Change of RAT Type; the event notification contains the new RAT Type for the PDU Session. - PLMN change; The event notification contains the new PLMN Identifier for the PDU Session. - Change of satellite backhaul category; The event notification contains the new satellite backhaul category for the PDU session. - Downlink data delivery status. The event notification contains the status of downlink data buffering in the core network including: - First downlink packet per source of the downlink IP traffic in extended buffering and Estimated maximum wait time. - First downlink packet per source of the downlink IP traffic discarded. - First downlink packet per source of the downlink IP traffic transmitted after previous buffering and/or discarding of corresponding packet(s). - QFI allocation: The event notification is sent when a new QoS flow is established within a PDU session and contains: - If the Target of Event Reporting is a PDU session, both the allocated QFI and either one of the following (Application Identifier or IP Packet Filter Set or Ethernet Packet Filter Set). The 5QI corresponding to the QoS flow and the DNN, S-NSSAI corresponding to the PDU session are also sent. - If the Target of Event Reporting is a SUPI, both the allocated QFI and either one of the following (Application Identifier or IP Packet Filter Set or Ethernet Packet Filter Set) for each PDU session ID established for this SUPI. The 5QI corresponding to the QoS flow and the DNN, S-NSSAI corresponding to each PDU session are also sent. - If the Target of Event Reporting is an Internal-Group-Id or any UE, multiple instances of the tuple (allocated QFI and either one of the following (Application Identifier or IP Packet Filter Set or Ethernet Packet Filter Set). PDU session ID, SUPI). The 5QI corresponding to the QoS flow and the DNN, S-NSSAI corresponding to each PDU session are also sent. - Total number of Session Management transactions: - The total number of Session Management transaction is used to collect the number of SM transactions of a SUPI or Internal Group ID, for example Dispersion Analytics as specified in TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [50]. The transaction count is incremented when the NAS transactions from PDU Session Establishment, PDU Session Authentication, PDU Session Modification and PDU Session Release procedures is concluded. Only the periodic reporting mode applies. - Information on PDU Session for WLAN (i.e. Access Type is Non-3GPP and RAT Type is TRUSTED_WLAN). NOTE 2: When the consumer NF is the NWDAF, the event QFI allocation is used to collect data for Observed Service Experience analytics, UE communication analytics, QoS Sustainability analytics and end-to-end data volume transfer time analytics as specified in TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [50]. - User plane status information: The event notification contains: - PDU Session ID. - User Plane Inactivity Timer (as specified in TS 29.244[ Interface between the Control Plane and the User Plane nodes ] [69]). - PDU Session status (activated, deactivated). NOTE 3: When the consumer NF is the NWDAF, the event user plane status information is used to collect data for UE Communication analytics as specified in TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [50]. - Session Management Congestion Control Experience for PDU Session: The event notification contains the data related to Session Management Congestion Control experience per PDU Session as described in TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [50]. - UE session behaviour trends (see clause 4.15.4.3); - UE communications trends (see clause 4.15.4.3); - UP with redundant transmission: the event notification indicates if redundant transmission (see clause 5.33.2.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]) has been activated or not for the PDU session; - User Data Usage Measures (see clause 4.15.4.5): SMF conveys the subscription to UPF on behalf of the consumer. Consumer receives the events directly from UPF; and - User Data Usage Trends (see clause 4.15.4.5): SMF conveys the subscription to UPF on behalf of the consumer. Consumer receives the events directly from UPF. When the consumer NF is the NWDAF, the event Information on PDU Session for WLAN is used to collect data for WLAN performance analytics as specified in TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [50]. When the consumer NF is the NWDAF, the event Session Management Congestion Control Experience for PDU Session is used to collect data for Session Management Congestion Control Experience analytics as specified in TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [50]. When the consumer NF is the NWDAF, the events QoS Monitoring, User Data Usage Measures and User Data Usage Trends are used to collect data from UPF for analytics as specified in clause 4.15.4.5 and in TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [50]. SMF conveys the subscription to UPF on behalf of the NWDAF. The consumer NF may request to subscribe the UPF exposure events (including event ID of exposed UPF event of QoS monitoring, User Data Usage Measures and User Data Usage Trends) via SMF indirectly by Nsmf_EventExposure. After receiving this subscription request, the SMF does a third-party subscription onto UPF on behalf of this consumer. The consumer should also provide the subscribed UPF event to SMF. Event Filters are used to specify the conditions to match for notifying the events (i.e. "List of Parameter values to match"). If there are no conditions to match for a specific Event ID, then the Event Filter is not provided. The following table provides as an example how the conditions to match for event reporting can be specified for various Event IDs for SMF exposure. Table 5.2.8.3.1-1: Example of Event Filters for SMF exposure events The target of SMF event reporting may correspond to a PDU Session ID, an UE ID (SUPI), an Internal Group Identifier, an indication that any UE is targeted (e.g. on a specific DNN), or an indication that any PDU session is the target. When acknowledgment is expected the SMF also provides Notification Correlation Information to the consumer NF in the event notification. The consumer NF may provide the following event-specific information when acknowledging an event notification: - For UP path change event: - N6 traffic routing information related to the target DNAI. NOTE 4: Acknowledgement to a UP path change event notification is further described in clause 5.6.7 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.8.3 |
4,250 | 8.150 Alternative IMSI | Alternative IMSI is transferred via GTP tunnels. The sending entity copies the value part of the Alternative IMSI into the Value field of the Alternative IMSI IE. Alternative IMSI is in the form of an IMSI as defined in 3GPP TS 23.003[ Numbering, addressing and identification ] [2]. Figure 8.150-1: Alternative IMSI Octets 5 to (n+4) represent the Alternative IMSI value in international number format as described in ITU-T Rec E.212 [64], encoded as TBCD digits, i.e. digits from 0 through 9 are encoded "0000" to "1001". When there is an odd number of digits, bits 8 to 5 of the last octet are encoded with the filler "1111". The maximum number of digits is 15. | 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.150 |
4,251 | 5.31.4 Control Plane CIoT 5GS Optimisation 5.31.4.1 General | The Control Plane CIoT 5GS Optimisation is used to exchange user data between the UE and the SMF as payload of a NAS message in both uplink and downlink directions, avoiding the establishment of a user plane connection for the PDU Session. The UE and the AMF perform integrity protection and ciphering for the user data by using NAS PDU integrity protection and ciphering. For IP and Ethernet data, the UE and the SMF may negotiate and perform header compression. NOTE: In the context of Control Plane CIoT 5GS Optimisation, established or activated user plane resources/connection refers to radio user plane resources/connection i.e Data Radio Bearer and N3 tunnel. UE and AMF negotiate support and use of Control Plane CIoT 5GS Optimisation as defined in clause 5.31.2. When the Control Plane CIoT 5GS Optimisation feature is used and the PDU Session Type is unstructured, the SMF selects either NEF or UPF based on information in the UE's subscription. If UE and network have negotiated support and use of Control Plane CIoT 5GS Optimisation then the following paragraphs of this clause apply. During the PDU Session Establishment procedure the AMF indicates to the SMF that Control Plane CIoT 5GS Optimisation is available for data transmission. During the PDU Session Establishment procedure the AMF also determines based on Preferred and Supported Network Behaviour (see clause 5.31.2), subscription data, other already established PDU Sessions and local policy whether a new PDU Session shall only use the Control Plane CIoT 5GS Optimisation (i.e. that a user-plane connection shall never be established for the new PDU Session). If a PDU Session shall only use Control Plane CIoT 5GS Optimisation, the AMF provides a Control Plane Only Indicator to the SMF during the PDU Session Establishment. The SMF provides the Control Plane Only Indicator in the Session Management Request to the UE. A UE and SMF receiving the Control Plane Only Indicator for a PDU Session shall always use the Control Plane CIoT 5GS Optimisation for this PDU Session. The following rules apply for the use of the Control Plane Only Indicator during PDU Session Establishment: - If N3 data transfer was not successfully negotiated, all PDU Sessions shall include Control Plane Only Indicator. - If N3 data transfer was successfully negotiated then: - For a new PDU Session for a DNN/S-NSSAI for which the subscription data for SMF Selection includes an Invoke NEF indication (i.e. for a PDU Session which will be anchored in NEF), the AMF shall always include the Control Plane Only Indicator. - For a new PDU Session for a DNN/S-NSSAI for which the subscription data for SMF Selection does not include an Invoke NEF indication (i.e. for a PDU Session which will be anchored in UPF) and that supports interworking with EPS based on the subscription data defined in TS 23.502[ Procedures for the 5G System (5GS) ] [3]: - for the first PDU Session the AMF determines based on local policy whether to include the Control Plane Only Indicator or not; - if the AMF previously included a Control Plane Only Indicator for PDU Sessions that support interworking with EPS based on the subscription data defined in TS 23.502[ Procedures for the 5G System (5GS) ] [3] and that are anchored in UPF, the AMF shall include it also for the new PDU Session; - if the AMF previously did not include a Control Plane Only Indicator for any of the PDU Sessions that support interworking with EPS based on the subscription data defined in TS 23.502[ Procedures for the 5G System (5GS) ] [3] and that are anchored in UPF, the AMF shall not include it for the new PDU Session. - For a new PDU Session for a DNN/S-NSSAI for which the subscription data for SMF Selection does not include an Invoke NEF indication (i.e. for a PDU Session which will be anchored in UPF) and that does not support interworking with EPS based on the subscription data defined in TS 23.502[ Procedures for the 5G System (5GS) ] [3], AMF determines individually per PDU Session whether to include the Control Plane Only Indicator or not. As described in clause 5.31.4.2, if UE and AMF successfully negotiate N3 data transfer in addition to Control Plane CIoT 5GS Optimisation, the UE or SMF may request to establish N3 data transfer for one or more PDU Sessions for which Control Plane Only Indicator was not received. In CM-CONNECTED, the UE and the network use N3 delivery for PDU Sessions for which user plane resources are established, and uses NAS for data transmission for PDU Sessions for which user plane resources are not established. If the AMF determines that Control Plane Only indication associated with PDU Session is not applicable any longer due to e.g. change of Preferred and Supported Network Behaviour, subscription data, and local policy, the AMF should request the SMF to release the PDU Session as specified in clause 4.3.4.2 or clause 4.3.4.3 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. Early Data Transmission may be initiated by the UE for mobile originated Control Plane CIoT 5GS Optimisation when the RAT Type is E-UTRA. The QoS model as defined in clause 5.7 is not supported for PDU Sessions using Control Plane CIoT 5GS Optimisation as user plane resources are not established for those PDU Sessions. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.31.4 |
4,252 | 5.2.3.3 CC-Establishment confirmation | The call control entity of the network in the "CC-establishment present" state, shall, upon receipt of a CC-ESTABLISHMENT CONFIRMED message, stop timer T333 and enter the "CC-establishment confirmed" state. For speech calls, if the ESTABLISHMENT CONFIRMED message contains a Supported Codec List information element, the network shall use this list to select the codec for UMTS. If no Supported Codec List information element is received, then for UMTS the network shall select the default UMTS speech codec according to subclause 5.2.1.11. Codecs for GERAN shall be selected from the codecs indicated in the Supported Codec List information element or in the Bearer Capability information element. If neither a Supported Codec List information element nor a Bearer Capability information element is received, then for GERAN the network shall select GSM full rate speech version 1. Codec information that does not apply to the currently serving radio access shall be used by the network if an inter-system change occurs. In the "CC-establishment confirmed" state, the network sends a RECALL message. This message initiates user alerting and also shall include the Facility IE (providing additional information to be presented to the user for notification). The network starts timer T334 and enters the 'recall present' state. Upon reception of the RECALL message the Mobile station stops T335 and enters the "recall present" state. Figure 5.7b/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Recall | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.2.3.3 |
4,253 | 6.4.2.1 Multiple active NAS connections with different PLMNs | TS 23.501[ System architecture for the 5G System (5GS) ] [2] has a scenario when the UE is registered to a VPLMN's serving network via 3GPP access and to another VPLMN's or HPLMN's serving network via non-3GPP access at the same time. When the UE is registered in one PLMN's serving network over a certain type of access (e.g. 3GPP) and is registered to another PLMN's serving network over another type of access (e.g. non-3GPP), then the UE has two active NAS connections with different AMF's in different PLMNs. As described in clause 6.3.2.1, the UE shall independently maintain and use two different 5G security contexts, one per PLMN serving network. The 5G security context maintained by the UE shall contain the full set of 5G parameters, including NAS context parameters for 3GPP and non-3GPP access types per PLMN. In case of connection to two different PLMNs, it is necessary to maintain a complete 5G NAS security context for each PLMN independently, each with all associated parameters (such as two pairs of NAS COUNTs, i.e. one pair for 3GPP access and one pair for non-3GPP access). Each security context shall be established separately via a successful primary authentication procedure with the Home PLMN. All the NAS and AS security mechanisms defined for single registration mode are applicable independently on each access using the corresponding 5G security context. NOTE: The UE belongs to a single HPLMN. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.4.2.1 |
4,254 | 5.2.2.2.6 Namf_Communication_N1N2MessageUnSubscribe service operation | Service operation name: Namf_Communication_N1N2MessageUnSubscribe. Description: An NF can unsubscribe with the AMF to stop notifying a particular N1 message type or a specific N2 information type about the UE. Input, Required: CN NF ID, N1 Message Type Input, Optional: None. Output, Required: None. Output, Optional: None. The consumer NF invokes the Namf_Communication_N1MessageUnSubscribe service operation (NF ID, N1 message type or N2 information type to subscribe) on the AMF. The AMF deletes the binding for the consumer NF for the requested N1 message type. NOTE: Whether UnSubscribe Ack need a separate message or be realized in the transport layer will be determined in TS 29.518[ 5G System; Access and Mobility Management Services; Stage 3 ] [18]. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.2.2.6 |
4,255 | 8.2.1.3.1C Enhanced Performance Requirement Type C - 2 Tx Antenna Ports with TM1 interference | The requirements are specified in Table 8.2.1.3.1C-2, with the addition of parameters in Table 8.2.1.3.1C-1 and the downlink physical channel setup according to Annex C.3.2. The purpose is to verify the performance of open-loop spatial multiplexing performence with 2 transmit antennas when the PDSCH transmission in the serving cell is interfered by PDSCH of one dominant interfering cell with transmission mode 1. In Table 8.2.1.3.1C-1, Cell 1 is the serving cell, and Cell 2 is interfering cells. The downlink physical channel setup is according to Annex C.3.2 for each of Cell 1 and Cell 2 respectively. Table 8.2.1.3.1C-1 Test parameters for Larger Delay CDD (FRC) with TM1 interference Table 8.2.1.3.1C-2 Enhanced Performance Requirement Type C, Larger Delay CDD (FRC) with TM1 interference | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.2.1.3.1C |
4,256 | 5.2.7.2.7 Nnrf_NFManagement_NFStatusUnsubscribe service operation | Service Operation name: Nnrf_NFManagement_NFStatusUnsubscribe Description: Consumer can unsubscribe from being notified of newly registered NF along with its NF services and other events types described in the Nnrf_NFManagement_NFStatusSubscribe service operation (see clause 5.2.7.2.5). Inputs, Required: Subscription Correlation ID. Inputs, Optional: None. Outputs, Required: Operation execution result indication. Outputs, Optional: None. NOTE: Alternatively, other means such as OA&M can also be used to unsubscribe for NF status. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.7.2.7 |
4,257 | 19.11 Dedicated Core Networks Identifier | A Dedicated Core Network ID (DCN-ID) identifies a Dedicated Core Network (DCN) within a PLMN. The allowed values of DCN-ID shall be in the range of 0 to 65535. Values in the range of 0 to 127 are standardized and defined as follows: 0: Spare, for future use … 127: Spare, for future use Values in the range of 128 to 65535 are operator-specific. The use of the standardized DCN-ID is specified in 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [72]. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 19.11 |
4,258 | 8.3 Bearer type change | In MR-DC, all the possible bearer type change options are supported: - MCG bearer to/from split bearer; - MCG bearer to/from SCG bearer; - SCG bearer to/from split bearer. Bearer termination point change is supported for all bearer types, and can be performed with or without bearer type change: - MN terminated bearer to/from SN terminated bearer. For MR-DC: - when the security key is changed for a bearer due to a termination point change, the associated PDCP and RLC entities are re-established, while MAC behavior might depend on the solution selected by the network, e.g. MAC reset, change of LCID, etc. (see Annex A); - for MCG bearer, split bearer and SCG bearer, during MN security key change the MCG/SCG PDCP and RLC are re-established and MCG/SCG MAC is reset; - if a bearer type change happens together with MN security key change then for MCG bearer, split bearer and SCG bearer, the MCG/SCG PDCP and RLC are re-established and MCG/SCG MAC is reset; - if a bearer type change happens through SN change procedure, then SN terminated PDCP and SCG RLC are re-established and SCG MAC is reset. MCG RLC/MAC behavior depends on the solution selected by the network, see Annex A; - one step (direct) bearer type change between MN terminated bearer types without using the handover procedure is supported; - one step (direct) bearer type change between SN terminated bearer types without using the handover or SN change procedure is supported; - one step (direct) bearer type change from/to MN terminated bearer to/from SN terminated bearer without using the handover procedure is supported; - PDCP SN length change for an AM DRB or RLC mode change for DRB is performed using a release and add of the DRBs (in a single message) or full configuration; - One step (direct) bearer type change with PDCP version change (only applicable for EN-DC) is supported. For MR-DC with 5GC: - in a bearer termination point change of a DRB from a source NG-RAN node to a target NG-RAN node, for each DRB for which the source NG-RAN node provides QoS flow to DRB mapping information to the target NG-RAN node, the source NG-RAN node also offers the indicated DRB ID for usage at the target NG-RAN node. The target NG-RAN node informs the source NG-RAN node if it accepts the DRB offloading and takes the DRB ID into use. NOTE 1: In this clause the term "handover" refers to an E-UTRA handover or to an NR synchronous reconfiguration not necessarily implying a P(S)Cell change with or without security key change. NOTE 2: L2 handling for bearer type change in MR-DC is also summarized in Annex A (the table does not consider the cases that PDCP SN length is changed and avoiding reuse of COUNT). | 3GPP TS 37.340 | Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Overall Description; Stage-2 | RAN2 | 3GPP Series : 37 , Multiple radio access technology aspects | 8.3 |
4,259 | G.3.2 B2B charging information utilisation | In the business CHF only interaction, the NF (CTF) collect and report the charging information per business subscriber to B-CHF. In the business CHF via consumer CHF interaction, the NF (CTF) collect and report the charging information to C-CHF. C-CHF report the charging information per business subscriber to B-CHF. The identification for the business subscriber is specified in the respective middle tier TS, e.g. - Tenant Identifier in TS 28.201[ Charging management; Network slice performance and analytics charging in the 5G System (5GS); Stage 2 ] [70]. - EAS Provider Identifier in TS 32.257[ Telecommunication management; Charging management; Edge computing domain charging ] [17]. | 3GPP TS 32.240 | Telecommunication management; Charging management; Charging architecture and principles | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | G.3.2 |
4,260 | 8.3.2.1B Enhanced Performance Requirement Type A – Single-layer Spatial Multiplexing with TM9 interference model | The requirements are specified in Table 8.3.2.1B-2, with the addition of the parameters in Table 8.3.2.1B-1 and the downlink physical channel setup according to Annex C.3.2. The purpose of these tests is to verify closed-loop rank one performance on one of the antenna ports 7 or 8 without a simultaneous transmission on the other antenna port in the serving cell when the PDSCH transmission in the serving cell is interfered by PDSCH of one dominant interfering cell applying transmission mode 9 interference model defined in clause B.5.4. In 8.3.2.1B-1, Cell 1 is the serving cell, and Cell 2 is the interfering cell. The downlink physical channel setup is according to Annex C.3.2 for each of Cell 1and Cell 2, respectively. Table 8.3.2.1B-1: Test Parameters for Testing CDM-multiplexed DM RS (single layer) with TM9 interference model Table 8.3.2.1B-2: Enhanced Performance Requirement Type A, CDM-multiplexed DM RS with TM9 interference model | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.3.2.1B |
4,261 | – CFR-ConfigMulticast | The IE CFR-ConfigMulticast indicates UE specific common frequency resource configuration for multicast for one dedicated BWP. CFR-ConfigMulticast information element -- ASN1START -- TAG-CFR-CONFIGMULTICAST-START CFR-ConfigMulticast-r17::= SEQUENCE { locationAndBandwidthMulticast-r17 INTEGER (0..37949) OPTIONAL, -- Need S pdcch-ConfigMulticast-r17 PDCCH-Config OPTIONAL, -- Need M pdsch-ConfigMulticast-r17 PDSCH-Config OPTIONAL, -- Need M sps-ConfigMulticastToAddModList-r17 SPS-ConfigMulticastToAddModList-r17 OPTIONAL, -- Need N sps-ConfigMulticastToReleaseList-r17 SPS-ConfigMulticastToReleaseList-r17 OPTIONAL -- Need N } SPS-ConfigMulticastToAddModList-r17 ::= SEQUENCE (SIZE (1..8)) OF SPS-Config SPS-ConfigMulticastToReleaseList-r17 ::= SEQUENCE (SIZE (1..8)) OF SPS-ConfigIndex-r16 -- TAG-CFR-CONFIGMULTICAST-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
4,262 | – LTE-NeighCellsCRS-AssistInfoList | The IE LTE-NeighCellsCRS-AssistInfoList-r17 is used to provide configuration information of neighbour LTE cells to assist the UE to perform CRS interference mitigation (CRS-IM) in scenarios with overlapping spectrum for LTE and NR. LTE-NeighCellsCRS-AssistInfoList information element -- ASN1START -- TAG-LTE-NEIGHCELLSCRS-ASSISTINFOLIST-START LTE-NeighCellsCRS-AssistInfoList-r17 ::= SEQUENCE (SIZE (1..maxNrofCRS-IM-InterfCell-r17)) OF LTE-NeighCellsCRS-AssistInfo-r17 LTE-NeighCellsCRS-AssistInfo-r17 ::= SEQUENCE { neighCarrierBandwidthDL-r17 ENUMERATED {n6, n15, n25, n50, n75, n100, spare2, spare1} OPTIONAL, -- Cond CRS-IM neighCarrierFreqDL-r17 INTEGER (0..16383) OPTIONAL, -- Need S neighCellId-r17 EUTRA-PhysCellId OPTIONAL, -- Need S neighCRS-muting-r17 ENUMERATED {enabled} OPTIONAL, -- Need R neighMBSFN-SubframeConfigList-r17 EUTRA-MBSFN-SubframeConfigList OPTIONAL, -- Need S neighNrofCRS-Ports-r17 ENUMERATED {n1, n2, n4} OPTIONAL, -- Need S neighV-Shift-r17 ENUMERATED {n0, n1, n2, n3, n4, n5} OPTIONAL -- Cond NotCellID } -- TAG-LTE-NEIGHCELLSCRS-ASSISTINFOLIST-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
4,263 | 10.5.7.1 PDP context status | The purpose of the PDP context status information element is to indicate the state of each PDP context which can be identified by NSAPI. The PDP context status information element is a type 4 information element with 4 octets length. The PDP context status information element is coded as shown in figure 10.5.148/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.164/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Figure 10.5.148/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] PDP context status information element Table 10.5.164/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : PDP context status 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.7.1 |
4,264 | 5.7.3b.3 Failure type determination | The UE shall set the MCG failure type as follows: 1> if the UE initiates transmission of the MCGFailureInformation message due to T310 expiry: 2> set the failureType as t310-Expiry; 1> else if the UE initiates transmission of the MCGFailureInformation message due to T312 expiry: 2> set the failureType as t312-Expiry; 1> else if the UE initiates transmission of the MCGFailureInformation message to provide random access problem indication from MCG MAC: 2> if the random access procedure was initiated for beam failure recovery: 3> set the failureType as beamFailureRecoveryFailure; 2> else: 3> set the failureType as randomAccessProblem; 1> else if the UE initiates transmission of the MCGFailureInformation message to provide indication from MCG RLC that the maximum number of retransmissions has been reached: 2> set the failureType as rlc-MaxNumRetx: 1> else if the UE initiates transmission of the MCGFailureInformation message due to consistent uplink LBT failures on the MCG: 2> set the failureType as lbt-Failure; 1> else if connected as an IAB-node and the MCGFailureInformation message is initiated due to the reception of a BH RLF indication on BAP entity from the MCG: 2> set the failureType as bh-RLF. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.7.3b.3 |
4,265 | – SRS-PosTx-Hopping | The IE SRS-PosTx-Hopping specifies the frequency hopping configuration for SRS for Positioning transmission. SRS-PosTx-Hopping information element -- ASN1START -- TAG- SRS-PosTx-Hopping-START SRS-PosTx-Hopping-r18 ::= SEQUENCE { srs-PosConfig-r18 SRS-PosConfig-r17, bwp-r18 BWP, srs-PosUplinkTransmissionWindowConfig-r18 SetupRelease { SRS-PosUplinkTransmissionWindowConfig-r18 } OPTIONAL -- Need M } SRS-PosUplinkTransmissionWindowConfig-r18 ::= SEQUENCE { windowPeriodicityAndOffset-r18 CHOICE { periodicityAndOffset-r18 SRS-PeriodicityAndOffset-r16, periodicityAndOffset-Ext-r18 SRS-PeriodicityAndOffsetExt-r16 }, duration-r18 ENUMERATED {s1,s2,s4,s6}, ... } -- TAG-SRS-PosTx-Hopping-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
4,266 | 6.37.2 Requirements | The 5G system shall be able to support for a UE to discover other UEs supporting ranging. The 5G system shall be able to authorize ranging for a UE or a group of UE when using licensed spectrum. The 5G system shall be able to protect privacy of a UE and its user, ensuring that no identifiable information can be tracked by undesired entities during ranging. The 5G system shall be able to enable or disable ranging. The 5G system shall support mutual ranging, i.e. two UEs shall be able to initiate ranging to each other. The 5G system shall be able to ensure that the use of Ranging, if in licensed spectrum, is only permitted in network coverage under the full control of the operator who provides the coverage. NOTE 1: The above requirement does not apply for public safety networks with dedicated spectrum, where ranging might be allowed out of coverage or in partial coverage as well. The 5G system shall support energy efficient UE ranging operation. The 5G system shall be able to start ranging and stop ranging according to the application layer’s demand. The 5G system shall be able to provide mechanisms for a MNO, or authorized 3rd party, to provision and manage ranging operation and configurations. The 5G system shall be able to support mechanisms for a UE to assist another UE to perform ranging of a third UE (if the requesting UE is LOS with the assisting UE and the assisting UE is LOS with the third UE). NOTE 2: It cannot be assumed that all ranging UEs support the same application for exchange of information. The 5G system shall be able to support ranging enabled UEs to determine the ranging capabilities (e.g. capabilities to perform distance and/or angle measurement) of other ranging enabled UEs. The 5G system shall be able to allow a ranging enabled UE to determine if another ranging enabled UE is stationary or mobile, before and/or during ranging. NOTE 3: This may require assistance from other ranging enabled UEs. The 5G system shall allow ranging between 2 UEs triggered by and exposed to a third UE. The 5G system shall allow ranging service between 2 UEs triggered by and exposed to the application server. The 5G system shall be able to support one UE initiating ranging to the other UE. The 5G system shall be able to support ranging between UEs which subscribe to different operators. The 5G system shall be able to allow roaming UEs to perform ranging. The 5G system shall be able to ensure the integrity and confidentiality of ranging information used by ranging-enabled UEs. The 5G system shall be able to ensure that user privacy is not violated during ranging, e.g., subject to regional or national regulatory requirements. The 5G system shall be able to ensure security protection (e.g., interworking security) when the ranging concerns UEs subscribed with different operators. The level of security provided by the existing 5G system shall not be adversely affected when ranging is enabled. The 5G system shall support means to securely identify other ranging capable UEs, with which a certain UE can perform ranging. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.37.2 |
4,267 | 5.3.6.4 Multimedia CAT during the alerting phase of a mobile originated call | A mobile station supporting multimedia CAT during the alerting phase of a mobile originated multimedia call establishment shall indicate support of this capability to the network in the Call Control Capabilities information element in the SETUP message. The network may generate a multimedia CAT to such a mobile station before it has reached the "active" state of a call. To do so, the network shall through connect the traffic channel towards the source of the multimedia CAT and send a progress indicator IE indicating user attachment with progress description #9 "In-band multimedia CAT available" in either an ALERTING message or a PROGRESS message that is sent to the mobile station during call establishment. On reception of an ALERTING or a PROGRESS message the mobile station shall proceed as specified elsewhere in clause 5; if the progress indicator IE indicated user attachment with progress description #9 "In-band multimedia CAT available", the mobile station shall: - attach the user connection for multimedia as soon as an appropriate channel in multimedia mode is available; and - set up an H.324 call. It is up to the network to ensure that no undesired end-to-end through connection with the called party takes place during the establishment of a mobile terminated call. The mobile station shall not abort the call if an error or H.324 call clearing occurs during the setup or the lifetime of the H.324 call during the alerting phase; the call control entity of the calling mobile station shall remain in its current state. Upon reception of a new request from the network to attach the user connection with progress description #9 "In-band multimedia CAT available", the mobile station shall release any on-going H.324 call, and set up a new H.324 call. NOTE: The network can request the mobile station to restart a new H.324 call during the alerting phase of the call e.g. during call forwarding scenarios to transmit to the calling party the multimedia CAT of the forwarded-to party. The network may initiate the in-call modification procedure (see subclause 5.3.4.3) towards the MS in the "call delivered" state to modify the call mode to speech, if service change has been agreed at call setup. Upon receiving an indication that the call has been accepted, the call control entity of the network shall send a CONNECT message to its peer entity at the calling mobile station; start timer T313 and enter the "connect indication" state. This message indicates to the call control entity of the calling mobile station that a connection has been established through the network. On reception of a CONNECT message, the mobile station shall proceed as specified elsewhere in clause 5; the mobile station shall release any on-going H.324 call and set up a new H.324 call towards the called party. Mobile stations supporting multimedia CAT during the alerting phase of a mobile originated multimedia call establishment should also support the Media Oriented Negotiation Acceleration procedures specified in ITU-T Recommendation H.324 Amendment 1 [117] and ITU-T Recommendation H.324 Amendment 2 [118]. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.3.6.4 |
4,268 | 9.3.8.1.1 FDD | For the parameters specified in Table 9.3.8.1.1-1, and using the downlink physical channels specified in Annex C, the minimum requirements are specified in Table 9.3.8.1.1-2 and by the following a) the ratio of the throughput obtained when transmitting the transport format indicated by each reported wideband CQI index subject to interference sources with NeighCellsInfo-r12 configured and that obtained when transmitting the transport format indicated by each reported wideband CQI index subject to interference sources without NeighCellsInfo-r12 configured shall be ≥ ; Table 9.3.8.1.1-1 Fading test for FDD Table 9.3.8.1.1-2 Minimum requirement (FDD) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 9.3.8.1.1 |
4,269 | A.3.5 Fields with optional presence | A field with optional presence may be declared with the keyword DEFAULT. It identifies a default value to be assumed, if the sender does not include a value for that field in the encoding: -- /example/ ASN1START PreambleInfo ::= SEQUENCE { numberOfRA-Preambles INTEGER (1..64) DEFAULT 1, ... } -- ASN1STOP Alternatively, a field with optional presence may be declared with the keyword OPTIONAL. It identifies a field for which a value can be omitted. The omission carries semantics, which is different from any normal value of the field: -- /example/ ASN1START PRACH-Config ::= SEQUENCE { rootSequenceIndex INTEGER (0..1023), prach-ConfigInfo PRACH-ConfigInfo OPTIONAL -- Need N } -- ASN1STOP The semantics of an optionally present field, in the case it is omitted, should be indicated at the end of the paragraph including the keyword OPTIONAL, using a short comment text with a need code. The need code includes the keyword "Need", followed by one of the predefined semantics tags (S, M, N or R) defined in clause 6.1. If the semantics tag S is used, the semantics of the absent field are further specified either in the field description table following the ASN.1 clause, or in procedure text. The addition of OPTIONAL keywords for capability groups is based on the following guideline. If there is more than one field in the lower level IE, then OPTIONAL keyword is added at the group level. If there is only one field in the lower level IE, OPTIONAL keyword is not added at the group level. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | A.3.5 |
4,270 | 10.5.5.8 P-TMSI signature | The purpose of the P-TMSI signature information element is to identify a GMM context of an MS. The P-TMSI signature is a type 3 information element with 4 octets length. The P-TMSI signature information element is coded as shown in figure 10.5.124/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.141/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Figure 10.5.124/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : P-TMSI signature information element Table 10.5.141/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : P-TMSI signature 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.5.8 |
4,271 | – CSI-ResourceConfig | The IE CSI-ResourceConfig defines a group of one or more NZP-CSI-RS-ResourceSet, CSI-IM-ResourceSet and/or CSI-SSB-ResourceSet. CSI-ResourceConfig information element -- ASN1START -- TAG-CSI-RESOURCECONFIG-START CSI-ResourceConfig ::= SEQUENCE { csi-ResourceConfigId CSI-ResourceConfigId, csi-RS-ResourceSetList CHOICE { nzp-CSI-RS-SSB SEQUENCE { nzp-CSI-RS-ResourceSetList SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-ResourceSetsPerConfig)) OF NZP-CSI-RS-ResourceSetId OPTIONAL, -- Need R csi-SSB-ResourceSetList SEQUENCE (SIZE (1..maxNrofCSI-SSB-ResourceSetsPerConfig)) OF CSI-SSB-ResourceSetId OPTIONAL -- Need R }, csi-IM-ResourceSetList SEQUENCE (SIZE (1..maxNrofCSI-IM-ResourceSetsPerConfig)) OF CSI-IM-ResourceSetId }, bwp-Id BWP-Id, resourceType ENUMERATED { aperiodic, semiPersistent, periodic }, ..., [[ csi-SSB-ResourceSetListExt-r17 CSI-SSB-ResourceSetId OPTIONAL -- Need R ]] } -- TAG-CSI-RESOURCECONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
4,272 | – UplinkTxDirectCurrentMoreCarrierList | The IE UplinkTxDirectCurrentMoreCarrierList indicates the Tx Direct Current locations for intra-band CA including one, two or more uplink carriers. The UE does not report the uplink Direct Current location information for SUL carrier(s). UplinkTxDirectCurrentMoreCarrierList information element -- ASN1START -- TAG-UPLINKTXDIRECTCURRENTMORECARRIERLIST-START UplinkTxDirectCurrentMoreCarrierList-r17 ::= SEQUENCE (SIZE (1..maxNrofCC-Group-r17)) OF CC-Group-r17 CC-Group-r17 ::= SEQUENCE { servCellIndexLower-r17 ServCellIndex, servCellIndexHigher-r17 ServCellIndex OPTIONAL, defaultDC-Location-r17 DefaultDC-Location-r17, offsetToDefault-r17 CHOICE{ offsetValue OffsetValue-r17, offsetlist SEQUENCE (SIZE(1..maxNrofReqComDC-Location-r17)) OF OffsetValue-r17 } OPTIONAL } OffsetValue-r17::= SEQUENCE { offsetValue-r17 INTEGER (-20000.. 20000), shift7dot5kHz-r17 BOOLEAN } DefaultDC-Location-r17 ::= CHOICE { ul FrequencyComponent-r17, dl FrequencyComponent-r17, ulAndDL FrequencyComponent-r17 } FrequencyComponent-r17 ::= ENUMERATED {activeCarrier,configuredCarrier,activeBWP,configuredBWP} -- TAG-UPLINKTXDIRECTCURRENTMORECARRIERLIST-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
4,273 | 11.3 Numbering and Addressing | In the case of interworking with public IP networks (such as the Internet), the PLMN operator shall use public network addresses. These public addresses can be reserved from the responsible IP numbering body, or from an ISP with which the PLMN operator has an agreement. In case of IPv6, a global IPv6 prefix can be obtained from the same sources. In the case of interworking with private IP networks, two scenarios can be identified: 1. the PLMN operator manages internally the subnetwork IPv4 addresses and/ or IPv6 prefixes as applicable. Each private network is assigned a unique subnetwork IPv4 addresses and/ or IPv6 prefixes. Normal routing functions are used to route packets to the appropriate private network; 2. each private network manages its own addressing. In general this will result in different private networks having overlapping address ranges. A logically separate connection (e.g. an IP in IP tunnel or layer 2 virtual circuit) is used between the GGSN/P-GW and each private network. In this case the IP address alone is not necessarily unique. The pair of values, Access Point Name (APN) and IPv4 address and/or IPv6 prefixes, is unique. NOTE 1: In IPv6, "site-local addresses"were originally designed to be used for addressing inside of a site that is similar to the usage of "private addresses" in IPv4. The usage of "site-local-addresses" is deprecated as specified in RFC 4291 [82]. Existing implementations and deployments may continue using site-local addresses. However, in new implementations the prefix that was allocated for "site local addresses" shall be treated as for "global unicast addresses", see RFC 4291 [82]. The PLMN operator allocates the IP addresses for the subscribers in either of the following ways. - The PLMN operator allocates a static IPv4 address and/or a static IPv6 prefix when the subscription record is built. The IPv4 address and/or IPv6 prefix are respectively reserved from a pool of free IPv4 addresses and/or IPv6 prefixes. Each external network has its own pool of IPv4 addresses and/or IPv6 prefixes. - The PLMN operator allocates (either on its own or in conjunction with the external network) a dynamic IPv4 address and/or a dynamic IPv6 prefix as described in 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [3], 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [77] and 3GPP TS 23.402[ Architecture enhancements for non-3GPP accesses ] [78]. For UEs used for Machine-Type Communications (MTC) as described in 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [77] and 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [3] and Cellular Internet of Things (CIoT) as described in 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [77] and 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [3], IPv6 address allocation should be the primary mechanism for IP address allocation. IPv4 based address allocation is considered a transition solution and is deprecated for MTC used over 3GPP accesses. NOTE 2: For implementation guidelines related to transition and other aspects of IPv4 address usage see 3GPP TS 23.221[ Architectural requirements ] [99] Annex B. In case of transferring Non-IP data over SGi PtP tunnelling based on UDP/IP (see subclause 11.8) the PLMN operator uses private network addresses for the establishment of the tunnel. | 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.3 |
4,274 | 4.5.4.1 Access control and checking in 5GMM-IDLE mode and in 5GMM-IDLE mode with suspend indication | When the UE is in 5GMM-IDLE mode or 5GMM-IDLE mode with suspend indication, upon receiving a request from the upper layers for an access attempt, the NAS shall categorize the access attempt into access identities and an access category following: a) subclause 4.5.2, table 4.5.2.1 and table 4.5.2.2, and subclause 4.5.3, if the UE is not operating in SNPN access operation mode over 3GPP access ; or b) subclause 4.5.2A, table 4.5.2A.1 and table 4.5.2A.2, and subclause 4.5.3, if the UE is operating in SNPN access operation mode over 3GPP access , and provide the applicable access identities and the access category to the lower layers for the purpose of access control checking. In this request to the lower layer the NAS can also provide to the lower layer the RRC establishment cause determined as specified in subclause 4.5.6 of this specification. NOTE 1: The access barring check is performed by the lower layers. NOTE 2: As an implementation option, the NAS can provide the RRC establishment cause to the lower layers after being informed by the lower layers that the access attempt is allowed. If the UE has uplink user data pending for one or more PDU sessions when it builds a REGISTRATION REQUEST or SERVICE REQUEST message as initial NAS message, the UE shall indicate the respective PDU sessions in the Uplink data status IE as specified in subclause 5.5.1.3.2 and 5.6.1.2.1, regardless of the access category for which the access barring check is performed. If the UE is registered for 5GS services with control plane CIoT 5GS optimization has uplink user data pending for one or more PDU sessions when it builds a CONTROL PLANE SERVICE REQUEST message as initial NAS message, the UE shall indicate the respective PDU sessions as specified in subclause 5.6.1.2.2, regardless of the access category for which the access barring check is performed. NOTE 3: The UE indicates pending user data for all the respective PDU sessions, even if barring timers are running for some of the corresponding access categories. If the lower layers indicate that the access attempt is allowed, the NAS shall initiate the procedure to send the initial NAS message for the access attempt. If the lower layers indicate that the access attempt is barred, the NAS shall not initiate the procedure to send the initial NAS message for the access attempt. Additionally: a) if the event which triggered the access attempt was an MO-MMTEL-voice-call-started indication or an MO-MMTEL-video-call-started indication: 1) if the UE is operating in the single-registration mode, the UE's usage setting is "voice centric" and the UE has not disabled its E-UTRA capability as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15], the UE may attempt to select an E-UTRA cell connected to EPC. If the UE finds a suitable E-UTRA cell connected to EPC, it then proceeds with the appropriate EMM specific procedures and, if necessary, ESM procedures to make a PDN connection providing access to IMS available; see subclause 4.8.2 and 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15]; 2) if the UE is operating in the dual-registration mode, the UE may proceed in S1 mode with the appropriate EMM specific procedures and ESM procedures to make a PDN connection providing access to IMS available; see subclause 4.8.3 and 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15]; or 3) otherwise, the NAS shall notify the upper layers that the access attempt is barred. In this case, upon receiving an indication from the lower layers that the barring is alleviated for the access category with which the access attempt was associated, the NAS shall notify the upper layers that the barring is alleviated for the access category and may initiate the procedure to send the initial NAS message, if still needed; b) if the event which triggered the access attempt was an MO-SMSoIP-attempt-started indication or an MO-IMS-registration-related-signalling-started indication: 1) if the UE is operating in the single-registration mode, the UE may attempt to select an E-UTRA cell connected to EPC. If the UE finds a suitable E-UTRA cell connected to EPC, it then proceeds with the appropriate EMM specific procedures and, if necessary, ESM procedures to make a PDN connection providing access to IMS available; see subclause 4.8.2 and 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15]; 2) if the UE is operating in the dual-registration mode, the UE may proceed in S1 mode with the appropriate EMM specific procedures and ESM procedures to make a PDN connection providing access to IMS available; see subclause 4.8.3 and 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15]; or 3) otherwise, the NAS shall notify the upper layers that the access attempt is barred. In this case, upon receiving an indication from the lower layers that the barring is alleviated for the access category with which the access attempt was associated, the NAS shall notify the upper layers that the barring is alleviated for the access category and may initiate the procedure to send the initial NAS message, if still needed; and c) if the access attempt is for emergency: 1) the NAS shall notify the upper layers that the access attempt is barred. In this case, upon receiving an indication from the lower layers that the barring is alleviated for the access category with which the access attempt was associated, the NAS shall notify the upper layers of that the barring is alleviated for the access category and may initiate the procedure to send the initial NAS message, if still needed. NOTE 4: This can result in the upper layers requesting another emergency call attempt using domain selection as specified in 3GPP TS 23.167[ IP Multimedia Subsystem (IMS) emergency sessions ] [6] and 3GPP TS 24.229[ IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 ] [14]. NOTE 5: Barring timers, on a per access category basis, are run by the lower layers. At expiry of barring timers, the indication of alleviation of access barring is indicated to the NAS on a per access category basis. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.5.4.1 |
4,275 | 16.10.5.7 Physical Layer | A CFR configured by RRCReconfiguration message is defined for multicast scheduling as an 'MBS frequency region' with a number of contiguous PRBs confined within and with the same numerology as the DL BWP, and multicast scheduling may have specific characteristics (e.g., PDCCH, PDSCH and SPS configurations). The CFR for the multicast reception in RRC_INACTIVE state and the CFR for broadcast can be configured differently. If one CFR is not completely contained within the other CFR, the UE in RRC_INACTIVE state is not required to receive both broadcast and multicast simultaneously. Two HARQ-ACK reporting modes are defined for MBS: - For the first HARQ-ACK reporting mode, the UE generates HARQ-ACK information with ACK value when a UE correctly decodes a transport block or detects a DCI format indicating an SPS PDSCH release; otherwise, the UE generates HARQ-ACK information with NACK value. - For the second HARQ-ACK reporting mode, the UE does not transmit a PUCCH that would include only HARQ-ACK information with ACK values. HARQ-ACK feedback for multicast can be enabled or disabled by higher layer configuration per G-RNTI or per G-CS-RNTI and/or indication in the DCI scheduling multicast transmission. HARQ feedback is not supported for MBS multicast session data reception for UEs in RRC_INACTIVE state. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.10.5.7 |
4,276 | 16.10.5.1 Session Management | There are two delivery modes as specified in TS 23.247[ Architectural enhancements for 5G multicast-broadcast services ] [45]: - 5GC Shared MBS traffic delivery; - 5GC Individual MBS traffic delivery. As specified in TS 23.247[ Architectural enhancements for 5G multicast-broadcast services ] [45], if the gNB supports MBS, the network shall use the 5GC Shared MBS traffic delivery in which case an MBS Session Resource context for a multicast session is setup in the gNB when the first UE joins the multicast session. For 5GC Shared MBS traffic delivery mode, shared NG-U resources are used to provide MBS user data to the gNB. The gNB initiates the Multicast Distribution Setup procedure towards the 5GC, to allocate shared NG-U resources for a multicast session. In case multiple MBS session areas as specified in TS 23.247[ Architectural enhancements for 5G multicast-broadcast services ] [45] are associated with the same multicast session for location dependent MBS services, multiple NG-U shared resources are established for the same multicast session per MBS Area Session ID served by the gNB. A shared NG-U resource applies one of the following transport options: - unicast transport; - multicast transport. For 5GC Shared MBS traffic delivery an MBS Session Resource comprises one or several MRBs. If minimisation of data loss is applied for a given MRB, synchronisation of allocation of PDCP COUNT values is applied by either or a combination of the following methods: - derivation of the PDCP COUNT values by means of a DL MBS QFI Sequence Number provided on NG-U. Synchronisation in terms of MBS QoS flow to MRB mapping and PDCP SN size of the corresponding MRB among gNBs are achieved by means of network implementation. - deployment of a Shared NG-U Termination at NG-RAN, shared among gNBs, which comprises a common entity for assignment of PDCP COUNT values. Synchronisation in terms of MBS QoS flow to MRB mapping and PDCP SN size of the corresponding MRB among gNBs may be achieved by means of network implementation. If PDCP COUNT values are derived from a DL MBS QFI Sequence Number provided on NG-U and only one QoS Flow is mapped to an MRB, the gNB shall set the PDCP COUNT value of PDCP PDU to the value of the DL MBS QFI Sequence Number provided with the received packet over NG-U. If PDCP COUNT values are derived from a DL MBS QFI Sequence Number provided on NG-U and multiple QoS Flows are mapped to an MRB, the gNB may derive the PDCP COUNT value of the PDCP PDU from the sum of the DL MBS QFI Sequence Numbers of the QoS Flows mapped to this MRB. NOTE: Synchronisation of PDCP COUNT values in case user data for MBS QoS flows mapped to the same MRB arrive over NG-U at different gNBs in different order or in case of loss of data over NG-U, and related handling of minimisation of data loss is left to implementation. As specified in TS 23.247[ Architectural enhancements for 5G multicast-broadcast services ] [45], the gNB may receive from the 5GC MBS Assistance Information associated with a multicast MBS session for a UE, which assists the gNB in configuring the UE properly. The MBS Assistance Information indicates that the UE is expected to require dedicated resources very frequently. Based on this information, the gNB may decide the RRC state of the UE. The QoS requirements of the multicast session apply regardless of the RRC state within which the UE receives multicast session data. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.10.5.1 |
4,277 | 5.9.3 Broadcast MRB configuration 5.9.3.1 General | The broadcast MRB configuration procedure is used by the UE to configure PDCP, RLC, MAC and the physical layer upon starting and/or stopping to receive a broadcast MRB transmitted on MTCH, or upon modification of a configuration of a broadcast MRB received by the UE. The procedure applies to MBS capable UEs that are interested to receive or that are receiving an MBS broadcast service that are in RRC_IDLE, RRC_INACTIVE or RRC_CONNECTED with an active BWP with common search space configured by searchSpaceMTCH or searchSpaceMCCH. NOTE: How to perform a modification of a broadcast MRB which is already configured in the UE is left to UE implementation. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.9.3 |
4,278 | 4.3.1.2 NG Control Plane | The NG control plane interface (NG-C) is defined between the NG-RAN node and the AMF. The control plane protocol stack of the NG interface is shown on Figure 4.3.1.2-1. The transport network layer is built on IP transport. For the reliable transport of signalling messages, SCTP is added on top of IP. The application layer signalling protocol is referred to as NGAP (NG Application Protocol). The SCTP layer provides guaranteed delivery of application layer messages. In the transport, IP layer point-to-point transmission is used to deliver the signalling PDUs. Figure 4.3.1.2-1: NG-C Protocol Stack NG-C provides the following functions: - NG interface management; - UE context management; - UE mobility management; - Transport of NAS messages; - Paging; - PDU Session Management; - Configuration Transfer; - Warning Message Transmission. Further details of NG-C can be found in TS 38.410[ NG-RAN; NG general aspects and principles ] [16]. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 4.3.1.2 |
4,279 | I.10.5.1 NSWO support in SNPN using CH with AAA server | The reference architecture to support authentication for Non-seamless WLAN offload using SNPN credentials from Credentials Holder using AAA Server is specified in Figure 4.2.15-3b of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. This clause applies to UEs that support NSWO in SNPN with any key generating EAP method by using the SNPN credentials with CH AAA server (i.e., the MSK indication described in step 0 of clause I.2.2.2.2 is configured on the UE). The UE shall reuse 5G NSWO procedures defined in Annex S.3.2 with WLAN access network for NSWO authentication with the same key generating EAP method that is used by the SNPN over 3GPP access with the following exception: - The EAP authentication is performed between the UE and the CH AAA with no involvement of NSWOF/AUSF/UDM. - The construction of SUCI described in this document is not applicable. NOTE: The requirement to use the same key generating EAP method includes the EAP identity privacy mechanism used by the SNPN over 3GPP access. This implies that for NSWO support in SNPN using CH with AAA server the identity privacy is achieved at the EAP layer via EAP method specific means. I.10.5.2 NSWO support in SNPN without CH 5G NSWO procedures are defined in Annex S.3.2. For SNPN the procedures are extended to usage of any key-generating EAP-method as follows: Steps 1-2 are performed as described in Annex S.3.2. In step 3, the SUCI can be of type anonymous SUCI if the construction of SUCI as described in clause 6.12 cannot be used and if the employed EAP method supports SUPI privacy. Steps 4-6 are performed as described in Annex S.3.2. 7. Upon reception of the Nudm_UEAuthentication_Get Request, the UDM invokes SIDF to de-conceal SUCI to gain SUPI if the received SUCI is not an anonymous SUCI. For selection of authentication methods, the statements in Annex I.2.2.1 apply. In case of SNPN, the UDM selects authentication method based on the NSWO indicator, subscription data and/or local configuration. The authentication method may include EAP-AKA’ or any other key-generating EAP authentication method. The UDM returns the selected authentication method to the AUSF. 8. Authentication is performed between the AUSF and UE using the selected EAP method. After a successful authentication the AUSF derives the MSK key and does not generate the KAUSF, as indicated by the NSWO indicator and as described for the PLMN case in Annex S.3.2. Steps 9-11 are performed as described in steps 16-18 of Annex S.3.2. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | I.10.5.1 |
4,280 | 4 Overview of the security architecture | Figure 1 gives an overview of the complete 3G security architecture. Figure 1: Overview of the security architecture Five security feature groups are defined. Each of these feature groups meets certain threats and accomplishes certain security objectives: - Network access security (I): the set of security features that provide users with secure access to 3G services, and which in particular protect against attacks on the (radio) access link; - Network domain security (II): the set of security features that enable nodes in the provider domain to securely exchange signalling data, and protect against attacks on the wireline network; - User domain security (III): the set of security features that secure access to mobile stations; - Application domain security (IV): the set of security features that enable applications in the user and in the provider domain to securely exchange messages; - Visibility and configurability of security (V): the set of features that enables the user to inform himself whether a security feature is in operation or not and whether the use and provision of services should depend on the security feature. Figure 2 gives an overview of the ME registration and connection principles within UMTS with a CS service domain and a PS service domain. As in GSM/GPRS, user (temporary) identification, authentication and key agreement will take place independently in each service domain. User plane traffic will be ciphered using the cipher key agreed for the corresponding service domain while control plane data will be ciphered and integrity protected using the cipher and integrity keys from either one of the service domains. In clause 6 the detailed procedures are defined and when not otherwise stated they are used in both service domains. Figure 2: Overview of the ME registration and connection principles within UMTS for the separate CN architecture case when the CN consists of both a CS service domain with evolved MSC/VLR, 3G_MSC/VLR, as the main serving node and an PS service domain with evolved SGSN/GGSN, 3G_SGSN and 3G GGSN, as the main serving nodes (Extract from TS 23.121[ Architectural requirements for Release 1999 ] [4] – Figure 4-8) | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | 4 |
4,281 | 5.5.1.2.6 Abnormal cases in the UE | The following abnormal cases can be identified: a) Access barred because of access class barring, EAB, ACDC or NAS signalling connection establishment rejected by the network without "Extended wait time" received from lower layers In WB-S1 mode, if access is barred for "originating signalling" (see 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [22]), the attach procedure shall not be started. The UE stays in the current serving cell and applies the normal cell reselection process. The attach procedure is started as soon as possible, i.e. when access for "originating signalling" is granted on the current cell or when the UE moves to a cell where access for "originating signalling" is granted. In NB-S1 mode, if access is barred for "originating signalling" (see 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [22]), the attach procedure shall not be started. The UE stays in the current serving cell and applies the normal cell reselection process. Further UE behaviour is implementation specific, e.g. the attach procedure is started again after an implementation dependent time. In NB-S1 mode, if access is barred for "originating signalling" (see 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [22]), a request for an exceptional event is received from the upper layers, then the attach procedure shall be started. NOTE 1: In NB-S1 mode, the EMM layer cannot receive the access barring alleviation indication from the lower layers (see 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [22]). If access is barred because of access class barring for "originating signalling" (see 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [22]), ACDC is applicable to the request from the upper layers and the UE supports ACDC, then the attach procedure shall be started. If access is barred for a certain ACDC category (see 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [22]), a request with a higher ACDC category is received from the upper layers and the UE supports ACDC, then the attach procedure shall be started. If an access request for an uncategorized application is barred due to ACDC (see 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [22]), a request with a certain ACDC category is received from the upper layers and the UE supports ACDC, then the attach procedure shall be started. aa) Lower layer failure to establish the RRC connection and: - the UE is in its HPLMN or in an EHPLMN (if the EHPLMN list is present); - the attach request is neither for emergency bearer services nor for initiating a PDN connection for emergency bearer services with attach type not set to "EPS emergency attach"; - the UE supports being configured with CustomLLFailureRetry as specified in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [15A]); and - CustomLLFailureRetry leaf is present as specified in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [15A]); The UE shall increment the UE implementation specific attempt counter. If the UE implementation specific attempt counter is less than the value of MaxMinRetry consecutive attempts, the UE shall start T3411 with the duration of MinRetryTimer. If the UE implementation specific attempt counter is equal to the value of MaxMinRetry, the UE shall start T3402 with the duration of MaxRetryTimer and set the attach attempt counter to 5. The attach procedure shall be aborted, and the UE shall proceed as described below. b) Lower layer failure not covered in case aa) or release of the NAS signalling connection without "Extended wait time" and without "Extended wait time CP data" received from lower layers before the ATTACH ACCEPT or ATTACH REJECT message is received The attach procedure shall be aborted, and the UE shall proceed as described below. c) T3410 timeout The UE shall abort the attach procedure. The NAS signalling connection, if any, shall be released locally. NOTE 2: The NAS signalling connection can also be released if the UE deems that the network has failed the authentication check as specified in clause 5.4.2.7. The UE shall proceed as described below. d) ATTACH REJECT, other EMM cause values than those treated in clause 5.5.1.2.5, and cases of EMM cause values #22, #25, #31 and #78, if considered as abnormal cases according to clause 5.5.1.2.5 Upon reception of the EMM cause #19 "ESM failure", if the UE is not configured for NAS signalling low priority and the ESM cause value received in the PDN CONNECTIVITY REJECT message is not #54 "PDN connection does not exist", the UE may set the attach attempt counter to 5. Subsequently, if the UE needs to retransmit the ATTACH REQUEST message to request PDN connectivity towards a different APN, the UE may stop T3411 or T3402, if running, and send the ATTACH REQUEST message. If the UE needs to attempt EPS attach to request transfer of a PDN connection for emergency bearer services by including a PDN CONNECTIVITY REQUEST message with request type set to "handover of emergency bearer services", the UE shall stop T3411 or T3402, if running, and send the ATTACH REQUEST message. NOTE 3: When receiving EMM cause #19 "ESM failure", coordination is required between the EMM and ESM sublayers in the UE to determine whether to set the attach attempt counter to 5. If the attach request is neither for emergency bearer services nor for initiating a PDN connection for emergency bearer services with attach type not set to "EPS emergency attach", upon reception of the EMM causes #95, #96, #97, #99 and #111 the UE should set the attach attempt counter to 5. The UE shall proceed as described below. e) Change of cell into a new tracking area If a cell change into a new tracking area occurs before the attach procedure is completed, the attach procedure shall be aborted and re-initiated immediately. If a tracking area border is crossed when the ATTACH ACCEPT message has been received but before an ATTACH COMPLETE message is sent, the attach procedure shall be re-initiated. If a GUTI was allocated during the attach procedure, this GUTI shall be used in the attach procedure. f) Mobile originated detach required The attach procedure shall be aborted, and the UE initiated detach procedure shall be performed. g) Detach procedure collision If the UE receives a DETACH REQUEST message from the network in state EMM-REGISTERED-INITIATED and the detach type indicates "re-attach not required" and no EMM cause IE, or "re-attach not required" and the EMM cause value is not #2 "IMSI unknown in HSS", the detach procedure shall be progressed and the attach procedure shall be aborted. If the UE receives a DETACH REQUEST message from the network in state EMM-REGISTERED-INITIATED and the detach type indicates "re-attach required", the detach procedure shall be progressed and the UE shall locally release the NAS signalling connection, before re-initiating the attach procedure. Otherwise the attach procedure shall be progressed and the DETACH REQUEST message shall be ignored. h) Transmission failure of ATTACH REQUEST message indication from lower layers The UE shall restart the attach procedure immediately. i) Transmission failure of ATTACH COMPLETE message indication from lower layers If the current TAI is not in the TAI list, the UE shall restart the attach procedure. If the current TAI is still in the TAI list, it is up to the UE implementation how to re-run the ongoing procedure. The EMM sublayer notifies the ESM sublayer that the ESM message in the ESM message container IE of the ATTACH COMPLETE has failed to be transmitted. j) If EMM-REGISTERED without PDN connection is not supported by the UE or the MME, and the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message combined with the ATTACH ACCEPT is not accepted by the UE due to failure in the UE ESM sublayer, then the UE shall initiate the detach procedure by sending a DETACH REQUEST message to the network. Further UE behaviour is implementation specific. If EMM-REGISTERED without PDN connection is supported by the UE and the MME, and the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message combined with the ATTACH ACCEPT is not accepted by the UE due to failure in the UE ESM sublayer, then the UE shall either send an ATTACH COMPLETE message together with an ACTIVATE DEFAULT EPS BEARER CONTEXT REJECT contained in the ESM message container information element to the network or initiate the detach procedure by sending a DETACH REQUEST message. Further UE behaviour is implementation specific. k) Indication from the lower layers that an S101 mode to S1 mode handover has been cancelled (S101 mode only) The UE shall abort the attach procedure and enter state EMM-DEREGISTERED.NO-CELL-AVAILABLE. l) "Extended wait time" from the lower layers If the ATTACH REQUEST message contained the low priority indicator set to "MS is configured for NAS signalling low priority", the UE shall start timer T3346 with the "Extended wait time" value and reset the attach attempt counter. If the ATTACH REQUEST message did not contain the low priority indicator set to "MS is configured for NAS signalling low priority", the UE is operating in NB-S1 mode and the UE is not a UE configured to use AC11 – 15 in selected PLMN, then the UE shall start timer T3346 with the "Extended wait time" value and reset the attach attempt counter. In other cases the UE shall ignore the "Extended wait time". The UE shall abort the attach procedure, stay in the current serving cell, change the state to EMM-DEREGISTERED.ATTEMPTING-TO-ATTACH and apply the normal cell reselection process. The UE shall proceed as described below. la) "Extended wait time CP data" from the lower layers If the UE is operating in NB-S1 mode, the UE shall start the timer T3346 with the "Extended wait time CP data" value and reset the attach attempt counter. In other cases the UE shall ignore the "Extended wait time CP data". The UE shall abort the attach procedure, stay in the current serving cell, change the state to EMM-DEREGISTERED.ATTEMPTING-TO-ATTACH and apply the normal cell reselection process. The UE shall proceed as described below. m) Timer T3346 is running The UE shall not start the attach procedure unless: - the UE is a UE configured to use AC11 – 15 in selected PLMN; - the UE needs to attach for emergency bearer services; - the UE in NB-S1 mode is requested by the upper layer to transmit user data related to an exceptional event and i) the UE is allowed to use exception data reporting (see the ExceptionDataReportingAllowed leaf of the NAS configuration MO in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [15A] or the USIM file EFNASCONFIG in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [17]); and ii) timer T3346 was not started when NAS signalling connection was established with RRC establishment cause set to "MO exception data"; or - the UE needs to attach without the NAS signalling low priority indication and if the timer T3346 was started due to rejection of a NAS request message (e.g. ATTACH REQUEST, TRACKING AREA UPDATE REQUEST or EXTENDED SERVICE REQUEST) which contained the low priority indicator set to "MS is configured for NAS signalling low priority". The UE stays in the current serving cell and applies the normal cell reselection process. NOTE 4: It is considered an abnormal case if the UE needs to initiate an attach procedure while timer T3346 is running independent on whether timer T3346 was started due to an abnormal case or a non successful case. The UE shall proceed as described below. n) If EMM-REGISTERED without PDN connection is supported by the UE and the MME, an ESM DUMMY MESSAGE is included in the ESM message container information element of the ATTACH REQUEST message and the UE receives the ATTACH ACCEPT message combined with a PDN CONNECTIVITY REJECT message, the UE shall send an ATTACH COMPLETE message together with an ESM DUMMY MESSAGE contained in the ESM message container information element to the network. Further UE behaviour is implementation specific. o) Timer T3447 is running The UE shall not start the attach procedure unless: - the UE is a UE configured to use AC11 – 15 in selected PLMN; - the UE attempts to attach for emergency bearer services; or - the UE attempts to attach without PDN connection request. The UE stays in the current serving cell and applies the normal cell reselection process. The attach request procedure is started, if still necessary, when timer T3447 expires. For the cases aa, b, c, d, l, la and m: - Timer T3410 shall be stopped if still running. - For the cases aa, b, c, d, l when the "Extended wait time" is ignored, and la when the "Extended wait time CP data" is ignored, if the attach request is neither for emergency bearer services nor for initiating a PDN connection for emergency bearer services with attach type not set to "EPS emergency attach", the attach attempt counter shall be incremented, unless it was already set to 5. - If the attach attempt counter is less than 5: - for the cases l, la and m, the attach procedure is started, if still necessary, when timer T3346 expires or is stopped; - for the cases aa, b, c, d, l when the "Extended wait time" is ignored, and la when the "Extended wait time CP data" is ignore, if the attach request is neither for emergency bearer services nor for initiating a PDN connection for emergency bearer services with attach type not set to "EPS emergency attach", timer T3411 is started and the state is changed to EMM-DEREGISTERED.ATTEMPTING-TO-ATTACH. When timer T3411 expires the attach procedure shall be restarted, if still required by ESM sublayer. - If the attach attempt counter is equal to 5: - the UE shall delete any GUTI, TAI list, last visited registered TAI, list of equivalent PLMNs and KSI, shall set the update status to EU2 NOT UPDATED, and shall start timer T3402 if he value of the timer as indicated by the network is not zero. The state is changed to EMM-DEREGISTERED.ATTEMPTING-TO-ATTACH or optionally to EMM-DEREGISTERED.PLMN-SEARCH in order to perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6]; and - if A/Gb mode, Iu mode or N1 mode is supported by the UE: - if A/Gb mode or Iu mode is supported by the UE, the UE shall in addition handle the GMM parameters GMM state, GPRS update status, P-TMSI, P-TMSI signature, RAI and GPRS ciphering key sequence number as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] for the abnormal case when a normal attach procedure fails and the attach attempt counter is equal to 5; - if the UE is operating in single-registration mode, the UE shall in addition handle the 5GMM parameters 5GMM state, 5GS update status, 5G-GUTI, last visited registered TAI, TAI list and ngKSI as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] for the abnormal case when an initial registration procedure performed over 3GPP access fails and the registration attempt counter is equal to 5; and - except for case aa the UE shall attempt to select GERAN, UTRAN or NG-RAN radio access technology and proceed with appropriate GMM or 5GMM specific procedures. For case aa the UE may attempt to select GERAN, UTRAN or NG-RAN radio access technology and proceed with appropriate GMM or 5GMM specific procedures. Additionally, if the UE selects GERAN or UTRAN radio access technology, the UE may disable the E-UTRA capability as specified in clause 4.5. If No E-UTRA Disabling In 5GS is enabled at the UE (see 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [50] or 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [17]) and the UE selects NG-RAN radio access technology, it shall not disable the E-UTRA capability; otherwise, the UE may disable the E-UTRA capability as specified in clause 4.5. - if the value of T3402 as indicated by the network is zero, the UE shall perform the actions defined for the expiry of the timer T3402. NOTE 5: Whether the UE requests RRC to treat the active E-UTRA cell as barred (see 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [21]) is left to the UE implementation. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.5.1.2.6 |
4,282 | 13.4.1.3.1.1 With mutual authentication between NF Service Consumer and NRF at the transport layer | This clause covers the scenario where the NF Service Consumer and the NRF are connected over a mutually authenticated TLS connection. Figure 13.4.1.3.1.1-1: Authorization and service invocation procedure, for indirect communication without delegated discovery, with mutual authentication between NF and NRF at the transport layer Discovery of the NF Service Producer: 0. Optionally, the NF Service Consumer may discover the NF Service Producer before requesting authorization to invoke the services of the NF Service Producer. E.g. if the NF Service Consumer has not yet discovered the NF Service Producer, then it may run the discovery procedure. NF Service Consumer authorization: 1-2. After mutual authentication between NF Service Consumer and NRF at the transport layer, the NF Service Consumer and NRF perform the "Access token request before service access" procedure as described in clause 13.4.1.1. If the NF Service Consumer has already discovered the NF Service Producer, it can also perform the "Access token request for a specific NF Service Producer/NF Service Producer instance" procedure as described in clause 13.4.1.1. Service request: The NF Service Consumer, SCP, NRF and NF Service Producer perform the procedure "Indirect Communication without delegated discovery Procedure" described in clause 4.17.11 of TS 23.502[ Procedures for the 5G System (5GS) ] [8]. The following steps describe how the access token received from steps 1 and 2 is used in this procedure. 3. If no cached data is available, the NF Service Consumer discovers the NF Service Producer via the SCP. 4. The NF Service Consumer sends a service request for the specific service to the SCP. The service request includes the access token as received in step 2, and may include the NF Service Consumer CCA as defined in clause 13.3.8. If the CCA is included, the NF type of the expected audience in the CCA shall contain the NF type of the NF Service Producer . If the NF Service Consumer allows reselection of a target NF Service Producer by the SCP, the expected audience in the CCA shall also contain NF type "NRF". NOTE: In the same deployment, the NF Service Consumer can delegate the reselection of the target NF Service Producer to the SCP for some requests, and not for other requests. 5. The SCP selects a NF Service Producer instance, performs the API root modifications and forwards the received request to the selected NF Service Producer instance. The request contains the access token and may contain the NF Service Consumer CCA if received in step 4. 6. To authorize the access, the NF Service Producer authenticates the service consumer NF using one of the methods described in clause 13.3.2.2 and if successful, it validates the access token as described in clause 13.4.1.1 by verifying the signature and checking if the requested service is part of the token's scope. 7. If the checks in step 6 are successful, the NF Service Producer processes the service request and provides a service response. 8. The SCP performs reverse API root modifications and forwards the service response. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 13.4.1.3.1.1 |
4,283 | M.3.3.2 Security mechanisms for the F1 interface | The F1 interface connects the IAB-node (gNB-DU) to the IAB-donor-CU. It consists of the F1-C for control plane and the F1-U for the user plane. F1 security for IAB is established using the security mechanisms for the F1 interface as specified in clause 9.8.2 of the present document, with IAB node taking the role of gNB-DU and IAB-donor-CU taking the role of gNB-CU. In addition to the security mechanisms specified in clause 9.8.2 of the present document for the F1 interface, the IKEv2 Pre-shared Secret Key (PSK) authentication shall be supported. When IKEv2 performs a PSK authentication, in the IKE_AUTH request message, the IAB node shall set the ID type to ID_KEY-ID and set its value to PSK ID. NOTE 1: The PSK and PSK ID (for IKEv2 PSK authentication) can be preconfigured at the IAB node and IAB donor. Pre-configuration of the PSK(s) is out of the scope of the present document. Additionally, to support a flexible plug and play of IAB-node and IAB-donor without a pre-configuration of the PSK(s), dynamic PSK computation for IKEv2 PSK authentication may also be supported. When dynamic PSK is used, the IAB-node and the IAB-donor shall calculate the PSK (KIAB) as specified in the Annex A.23 of this document. The IAB-donor shall uniquely identify the IAB-node’s security context (KgNB) using the IAB-node DU IP address. The IAB-donor shall use KIAB as PSK for IKEv2 between IAB-node and the IAB-donor. KIAB is stored in the IAB-node and in the IAB-donor. This key KIAB and the IPsec SA cryptographic keys are taken into use with the establishment of IPsec Security Association (SA) between the IAB-node and the IAB-donor. KIAB remains valid as long as the IAB-node is connected to the IAB-donor or until the IAB-node is re-authenticated. In case of CP-UP separation of IAB-donor-CU (IAB-donor-CU contains IAB-donor-CU-CP and IAB-donor-CU-UP that use different IP address) then, IAB-donor-CU-CP and IAB-node DU shall generate KIAB-CU-CP and KIAB-CU-UP as specified in the Annex A.23 of this document. The key KIAB-CU-CP shall be used for establishment of secure F1 interface between the IAB-node DU and IAB-donor-CU-CP. The IAB-donor-CU-CP shall provide KIAB-CU-UP to the IAB-donor-CU-UP via E1 interface and KIAB-CU-UP shall be used for establishment of secure F1 interface between the IAB-node DU and IAB-donor-CU-UP. NOTE 2: KIAB is used as the PSK for IKEv2 authentication, the interface between the IAB-donor-CU and the SEG to provision the key KIAB in the SEG is implementation specific and out of the scope of the present document. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | M.3.3.2 |
4,284 | 4.1.5.1 Number of UE CONTEXT Release Request initiated by eNodeB/RN | This measurement provides the number of UE CONTEXT Release initiated by eNB/RN for each release cause. CC. Transmission of an UE CONTEXT RELEASE REQUEST message initiated by eNodeB/RN. Each release request is to be added to the relevant cause measurement. The possible causes are defined in 36.413 [9]. The sum of all supported per causes measurements shall equal the total number of UE CONTEXT Release initiated by eNodeB/RN. In case only a subset of per cause measurements is supported, a sum subcounter will be provided first. Each measurement is an integer value. The number of measurements is equal to the number of causes plus a possible sum value identified by the .sum suffix. The measurement name has the form UECNTX.RelReq.Cause where Cause identifies the release cause. EUtranCellFDD EUtranCellTDD Valid for packet switching. EPS By differenciate the causes, this measurement is used to count “The number of abnormal RRC connection release related to load”, which can be used for LBO target calculation.. | 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.1.5.1 |
4,285 | 5.13 Activation/Deactivation of SCells | If the MAC entity is configured with one or more SCells, the network may activate and deactivate the configured SCells. The SpCell is always activated. The network activates and deactivates the SCell(s) by sending Activation/Deactivation and/or Hibernation MAC control element(s) described in clause 6.1.3.8 and 6.1.3.15 respectively. Furthermore, the MAC entity maintains a sCellDeactivationTimer timer per configured SCell (except the SCell configured with PUCCH/SPUCCH, if any) and deactivates the associated SCell upon its expiry. In case the sCellHibernationTimer is configured, it takes priority over sCellDeactivationTimer. The same initial timer value applies to each instance of the sCellDeactivationTimer and it is configured by RRC. The configured SCells are initially deactivated upon addition and after a handover unless the parameter sCellState is set to activated or dormant for the SCell within RRC configuration. The configured SCG SCells are initially deactivated after a SCG change unless the parameter sCellState is set to activated or dormant for the SCell within RRC configuration. The MAC entity shall for each TTI and for each configured SCell: - if the MAC entity is configured with an activated SCell upon SCell configuration or receives MAC control element(s) in this TTI activating the SCell, the MAC entity shall in the TTI according to the timing defined in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [2]: - activate the SCell; i.e. apply normal SCell operation including: - SRS transmissions on the SCell; - if cqi-ShortConfigSCell is configured: - CQI/PMI/RI/PTI/CRI reporting for the SCell using the short period of the CSI (CQI/PMI/RI/PTI/CRI) reporting resource configured by cqi-ShortConfigSCell according to the timing defined in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [2]. - else: - CQI/PMI/RI/PTI/CRI reporting for the SCell using the configuration in cqi-ReportConfigSCell. - PDCCH monitoring on the SCell; - PDCCH monitoring for the SCell; - PUCCH/SPUCCH transmissions on the SCell, if configured. - start or restart the sCellDeactivationTimer associated with the SCell; - if sCellHibernationTimer associated with the SCell is configured; - start or restart the sCellHibernationTimer associated with the SCell. - trigger PHR according to clause 5.4.6. - else, if the MAC entity receives MAC control element(s) in this TTI deactivating the SCell; or - if the sCellDeactivationTimer associated with the activated SCell expires in this TTI and sCellHibernationTimer is not configured: - in the TTI according to the timing defined in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [2]: - deactivate the SCell; - stop the sCellDeactivationTimer associated with the SCell; - clear any configured downlink assignments and uplink grants associated with the SCell; - flush all HARQ buffers associated with the SCell. - if PDCCH on the activated SCell indicates an uplink grant or downlink assignment; or - if PDCCH on the Serving Cell scheduling the activated SCell indicates an uplink grant or a downlink assignment for the activated SCell; or - if a MAC PDU is transmitted in a configured uplink grant or received in a configured downlink assignment: - restart the sCellDeactivationTimer associated with the SCell; - if sCellHibernationTimer associated with the SCell is configured; - restart the sCellHibernationTimer associated with the SCell; - if the SCell is activated and the cqi-ShortConfigSCell expires in this TTI, according to the timing defined in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [2]: - apply SCell CQI/PMI/RI/PTI/CRI reporting for the SCell using the configuration in cqi-ReportConfigSCell; - if the SCell is deactivated: - not transmit SRS on the SCell; - not report CQI/PMI/RI/PTI/CRI for the SCell; - not transmit on UL-SCH on the SCell; - not transmit on RACH on the SCell; - not monitor the PDCCH on the SCell; - not monitor the PDCCH for the SCell; - not transmit PUCCH/SPUCCH on the SCell. HARQ feedback for the MAC PDU containing Activation/Deactivation MAC control element shall not be impacted by PCell, PSCell and PUCCH SCell interruptions due to SCell activation/deactivation, as specified in TS 36.133[ Evolved Universal Terrestrial Radio Access (E-UTRA); Requirements for support of radio resource management ] [9]. NOTE: When SCell is deactivated, the ongoing Random Access procedure on the SCell, if any, is aborted. | 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.13 |
4,286 | C.1.1.3 Time-based sequence number generation | In its binary representation, the sequence number consists of two concatenated parts SQN = SEQ || IND. The part SEQ is not divided into two parts. The global counter GLC is thus as long as SEQ. Instead of storing the individual counter SEQHE in the HE there is a value DIF stored in the HE which is individual for each user. The DIF value represents the current difference between generated SEQ values for that user and the GLC. When the HE needs new sequence numbers SQN to create new authentication vectors, HE retrieves the (user-specific) value of DIF from the data base and calculates SEQ values as SEQ = GLC +DIF. The DIF value may have to be updated in the HE only during the re-synchronization procedure. In this case the DIF value is set as DIF = SEQMS - GLC where SQNMS = SEQMS || INDMS is the value sent by USIM in the re-synchronization procedure. | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | C.1.1.3 |
4,287 | 17.1 MBMS user authorisation | Upon reception of an IGMP (IPv4) or MLD (IPv6) Join message for an IP multicast address allocated to MBMS services, the GGSN shall request authorisation of the user for this multicast MBMS bearer service (identified by the PDP context over which the IGMP join is received). The GGSN shall support pre-configuration of a BM-SC or Gmb proxy server for authorisation purposes to which the request shall be sent. The GGSN may support a list of pre-configured BM-SC servers based on the MBMS bearer service requested, for authorisation purposes. Upon receipt of an MBMS UE Context Establishment Request for a user who has not already been authorised for the MBMS bearer service, the GGSN shall request authorisation of the user for this service. | 3GPP TS 29.061 | Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) | CT WG3 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 17.1 |
4,288 | 4.3.2.2.1 Online Charging Function | The OCF consists of two distinct modules, namely the Session Based Charging Function (SBCF) and the Event Based Charging Function (EBCF). The Session Based Charging Function is responsible for online charging of network / user sessions, e.g. voice calls, IP CAN bearers, IP CAN session or IMS sessions. The Event Based Charging Function performs event-based online charging (also referred to as "content charging") in conjunction with any application server or service NE, including SIP application servers. Online charging in the CS and PS domains may be performed using the CAP reference point from the MSC and SGSN, respectively, to the OCF (refer to TS 23.078[ Customised Applications for Mobile network Enhanced Logic (CAMEL) Phase 4; Stage 2 ] [207] for details on CAP). Online charging communication between the S-CSCF and the SBCF is described in clause 4.3.2.2.2. All other network elements employ the Ro reference point for online charging (refer to TS 32.299[ Telecommunication management; Charging management; Diameter charging applications ] [50]). Refer to TS 32.296[ Telecommunication management; Charging management; Online Charging System (OCS): Applications and interfaces ] [53] for details on the relation between the network elements (i.e. the embedded online enhanced CTF) and the SBCF or EBCF, respectively. | 3GPP TS 32.240 | Telecommunication management; Charging management; Charging architecture and principles | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.3.2.2.1 |
4,289 | 4.23.6.2 Policy Update Procedures with I-SMF | Figure 4.23.6-1 shows procedures related to provisioning of PCC rules containing traffic steering information related to an I-SMF. Figure 4.23.6-1: Policy Update procedure In cases where step 1a in figure 4.23.6-1 is triggered in response to PCF receiving AF request, below steps 3 and 4 are applicable, in addition to those steps as explained in clause 4.3.6.1. Step 3: SMF provides to I-SMF with DNAI(s) of interest for this PDU Session for local traffic steering. If PCC rule changes for traffic offloaded via ULCL/BP due to the AF request, the SMF provides the updated N4 information to the I-SMF. Step 4: The procedure described in clauses 4.23.9.1, 4.23.9.2 and 4.23.9.3, from step 2 is executed. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.23.6.2 |
4,290 | 5.6.3 Potential service requirements | Editor’s note: These potential requirements require cross-checking with regulators and UAS OEMs before inclusion into normative work. The UAS shall be able to locally broadcast its identity and location. NOTE: the locally broadcast information should not expose personally identifiable information to general users. The UAS shall be able to locally broadcast its identity via local broadcast with a rate of at least once per 1s. The UAS shall be able to locally broadcast its identity up to a range of 500m. | 3GPP TS 22.825 | Study on Remote Identification of Unmanned Aerial Systems (UAS) | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 5.6.3 |
4,291 | 4.3.17.8 Support for Non-IP Data Delivery (NIDD) 4.3.17.8.1 General | The support of Non-IP data is part of the CIoT EPS Optimisations. A PDN Type "Non-IP" is used for Non-IP data. The Non-IP data delivery to SCS/AS is accomplished by one of two mechanisms: - Delivery using SCEF as defined in clause 4.3.17.8.3.2. - Delivery using a Point-to-Point (PtP) SGi tunnel as defined in clause 4.3.17.8.3.3. When the Reliable Data Service is not used, Non-IP data in-sequence delivery cannot be guaranteed and data PDUs may be lost requiring higher protocol layers to ensure guaranteed delivery when needed. The Reliable Data Service is defined in TS 23.682[ Architecture enhancements to facilitate communications with packet data networks and applications ] [74]. NOTE: If UEs use protocols that require broadcast/multicast mechanisms (e.g. use "IP stacks" on top of PDN connections of type "Non-IP"), this may cause increased traffic and power consumption to the UE and the network. The SMS service may also be used to deliver data without use of the IP protocol. The SMS service is always supported for CIoT EPS Optimisations, i.e. can be used simultaneously with Non-IP and IP data. When only the SMS service is needed, an attach without PDN connection establishment can be used, see clause 5.3.2. Dedicated bearers are not supported for the Non-IP data. | 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.17.8 |
4,292 | 5.10 MBS multicast reception in RRC_INACTIVE 5.10.1.1 General | UE configured to receive MBS multicast service(s) in RRC_INACTIVE that the UE has joined applies MBS multicast procedures described in this clause. MBS multicast configuration information is provided in RRCRelease and on multicast MCCH logical channel. When there is temporarily no data for an active multicast session or when the multicast session is deactivated, the network notifies the UE to stop monitoring the corresponding G-RNTI via MBS multicast configuration information. If the UE is notified to stop monitoring the G-RNTI(s) for all the joined multicast sessions, it stops monitoring the Multicast MCCH-RNTI for the cell where it received the notification. Multicast MCCH carries the MBSMulticastConfiguration message which indicates the MBS multicast sessions that are provided in the cell as well as the corresponding scheduling related information for these sessions. Optionally, the MBSMulticastConfiguration message may also contain a list of neighbour cells providing the same MBS multicast service(s) for RRC_INACTIVE as provided in the current cell. The configuration information required by the UE to receive multicast MCCH is provided in SIB24. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.10 |
4,293 | 5.7.13 RLM/BFD relaxation | In case both low mobility criterion and good serving cell criterion are configured for RLM/BFD relaxation, the UE is allowed to perform RLM and/or BFD relaxation according to requirements specified in TS 38.133[ NR; Requirements for support of radio resource management ] [14] when both relaxed measurement criterion for low mobility and relaxed measurement criterion for good serving cell quality are met. In case only the good serving cell quality criterion is configured for RLM/BFD relaxation, the UE is allowed to perform RLM and/or BFD relaxation according to requirements specified in TS 38.133[ NR; Requirements for support of radio resource management ] [14] when the relaxed measurement criterion for good serving cell quality is met. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.7.13 |
4,294 | – PCI-Range | The IE PCI-Range is used to encode either a single or a range of physical cell identities. The range is encoded by using a start value and by indicating the number of consecutive physical cell identities (including start) in the range. For fields comprising multiple occurrences of PCI-Range, the Network may configure overlapping ranges of physical cell identities. PCI-Range information element -- ASN1START -- TAG-PCI-RANGE-START PCI-Range ::= SEQUENCE { start PhysCellId, range ENUMERATED {n4, n8, n12, n16, n24, n32, n48, n64, n84, n96, n128, n168, n252, n504, n1008,spare1} OPTIONAL -- Need S } -- TAG-PCI-RANGE-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
4,295 | 4.16.1.3 Failed Secondary Node Additions without SN terminated bearers | a) This measurement provides the number of failures when Secondary Node Addition without SN terminated bearers. The measurement is split into subcounters per failure cause. b) CC c) On MN failed receipt of SGNB ADDITION REQUEST ACKNOWLEGE Message or on transmission by MN of an SgNB Release Message after receipt of SGNB ADDITION REQUEST ACKNOWLEGE Message when Secondary Node Additions without SN terminated bearers. Each Secondary Node failed to add is added to the relevant measurement per cause, the possible causes are included in TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [9]. The sum of all supported per cause measurements shall equal the total number of Additions failed to setup at Secondary Node Additions without SN terminated bearers case. In case only a subset of per cause measurements is supported, a sum subcounter will be provided first. SGNB Addition Trigger Indication (TS 36.423[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 Application Protocol (X2AP) ] [10]) excludes SN change, inter-eNB HO, intra-eNB HO. d) Each measurement is an integer value. The number of measurements is equal to the number of causes plus a possible sum value identified by the .sum suffix. e) The measurement name has the form ENDC.SNAdditionFailWoSnErab.Cause where Cause identifies the cause resulting in the Secondary Node Addition failure for without SN terminated bearers case. f) EUtranCellFDD EUtranCellTDD g) Valid for packet switched traffic h) EPS | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.16.1.3 |
4,296 | 5.4.2 Authentication procedure 5.4.2.1 General | The purpose of the EPS authentication and key agreement (AKA) procedure is to provide mutual authentication between the user and the network and to agree on a key KASME (see 3GPP TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [19]). The cases when the EPS AKA procedure should be used are defined in 3GPP TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [19]. The EPS AKA procedure is always initiated and controlled by the network. However, the UE can reject the EPS authentication challenge sent by the network. The UE shall proceed with an EPS authentication challenge only if a USIM is present. A partial native EPS security context is established in the UE and the network when an EPS authentication is successfully performed. During a successful EPS authentication procedure, the CK and IK are computed by the USIM. CK and IK are then used by the ME as key material to compute a new key, KASME. KASME is stored in the EPS security contexts (see 3GPP TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [19]) of both the network and in the volatile memory of the ME while attached to the network, and is the root for the EPS integrity protection and ciphering key hierarchy. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.4.2 |
4,297 | 4.12a.4.3 CN-initiated selective deactivation of UP connection of an existing PDU Session associated with Trusted non-3GPP Access | The procedure described in clause 4.3.7 (CN-initiated selective deactivation of UP connection of an existing PDU Session) is used for CN-initiated selective deactivation of UP connection for an established PDU Session associated with trusted non-3GPP Access for a UE in CM-CONNECTED state, with the following exceptions: - The NG-RAN corresponds to a TNAN including a TNGF. - The user plane between the UE and TNGF, i.e. Child SA(s) for the PDU Session, is released not with RRC signalling but with IKEv2 signalling, as specified in clause 4.12a.7. - If the UE has reserved any non-3GPP specific QoS resources, the UE releases these resources when the IKEv2 Child SA is released. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.12a.4.3 |
4,298 | 4.16.15.2.2 Procedure for PDTQ warning notification | Figure 4.16.15.2.2-1: The procedure for PDTQ warning notification 1. The negotiation for PDTQ policy as described in clause 4.16.15.2.1 is completed. In addition, the PCF has subscribed to analytics on "Network Performance" or "DN Performance" from NWDAF for the area of interest and time window of a PDTQ policy following the procedures and services described in TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [50], including a Reporting Threshold in the Analytics Reporting information. The value for Reporting Threshold is set by the PCF based on operator configuration. 2. The PCF is notified with the Network Performance analytics or DN Performance analytics in the area of interest from the NWDAF when the NWDAF determines that the Network Performance or DN Performance reaches the Reporting Threshold as described for the Network Performance analytics or DN Performance analytics in TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [50]. 3. The H-PCF requests from the UDR the stored PDTQ policies using Nudr_DM_Query (Policy Data, Planned Data Transfer with QoS requirements) service operation. 4. The UDR provides all the PDTQ Policies together with the relevant information received from the AFs (as defined in clause 6.1.2.7 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]) to the H-PCF. 5. The H-PCF identifies the PDTQ Policies affected based on the notification received from NWDAF. For each of them, the H-PCF determines the ASP of which the PDTQ traffic will be influenced by the degradation of network Performance or DN Performance and which requested the H-PCF to send the notification. The PCF then performs the following steps for each of the determined ASPs, i.e. Steps 6 - 11 can occur multiple times (i.e. once per ASP). 6. The PCF decides based on operator policies, whether a new list of candidate PDTQ policies can be calculated for the ASP. If the PCF does not find any new candidate PDTQ policy, the previously negotiated PDTQ policy shall be kept, no interaction with that ASP shall occur and the procedure stops for that PDTQ policy. NOTE: The PDTQ policies of an ASP which did not request to be notified are kept and no interaction with this ASP occurs. 7. The PCF sends the notification to the NEF by invoking Npcf_PDTQPolicyControl_Notify (PDTQ Reference ID, list of candidate PDTQ policies) service operation. 8. The NEF sends the PDTQ warning notification to the AF by invoking Nnef_PDTQPolicyNegotiation_Notify (PDTQ Reference ID, list of candidate PDTQ policies) service operation. 9. The AF checks the new PDTQ policies included in the candidate list in the PDTQ warning notification. 10. If the AF selects any of the new PDTQ policies, the steps 9-14 from clause 4.16.15.2.1 are executed with the difference that the AF has to respond as well when only one PDTQ policy was provided by the PCF and the PCF removes the no longer valid PDTQ policy from the UDR for the corresponding PDTQ Reference ID. 11. If the AF doesn't select any of the new PDTQ policies, the steps 9-12 from clause 4.16.15.2.1 are executed, with the AF indicating that none of the candidate PDTQ policies is acceptable. In this case, the AF response only includes PDTQ reference ID, but no PDTQ policy and the previously negotiated PDTQ policy shall be kept. The AF can send a Stop notification by invoking Nnef_PDTQPolicyNegotiation_Update service, when the AF requests not to receive the PDTQ warning notification anymore. Then, the NEF invokes Npcf_PDTQPolicyControl_Update service in order to provide this information for the H-PCF. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.16.15.2.2 |
4,299 | 10.5.3.1.1 Authentication Parameter AUTN (UMTS and EPS authentication challenge) | The purpose of the Authentication Parameter AUTN information element is to provide the MS with a means of authenticating the network. The Authentication Parameter AUTN information element is coded as shown in figure 10.5.75.1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.89.1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The Authentication Parameter AUTN is a type 4 information element with a length of 18 octets. Figure 10.5.75.1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Authentication Parameter AUTN information element (UMTS and EPS authentication challenge) Table 10.5.89.1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Authentication Parameter AUTN information element (UMTS and EPS authentication challenge) | 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.1.1 |
4,300 | 8.13.2.2.1 Minimum Requirement Dual-Layer Spatial Multiplexing 2 Tx Antenna Port | For CA with 2 DL CCs, for dual-layer transmission on antenna ports 7 and 8 upon detection of a PDCCH with DCI format 2C, the requirements are specified in Table 8.13.2.2.1-2A, based on single carrier requirement specified in Table 8.13.2.2.1-2, with the addition of the parameters in Table 8.13.2.2.1-1 and the downlink physical channel setup according to Annex C.3.2. For CA with 3 DL CCs, for dual-layer transmission on antenna ports 7 and 8 upon detection of a PDCCH with DCI format 2C, the requirements are specified in Table 8.13.2.2.1-3, based on single carrier requirement specified in Table 8.13.2.2.1-2, with the addition of the parameters in Table 8.13.2.2.1-1 and the downlink physical channel setup according to Annex C.3.2. For CA with 4 DL CCs, for dual-layer transmission on antenna ports 7 and 8 upon detection of a PDCCH with DCI format 2C, the requirements are specified in Table 8.13.2.2.1-4, based on single carrier requirement specified in Table 8.13.2.2.1-2, with the addition of the parameters in Table 8.13.2.2.1-1 and the downlink physical channel setup according to Annex C.3.2. For CA with 5 DL CCs, for dual-layer transmission on antenna ports 7 and 8 upon detection of a PDCCH with DCI format 2C, the requirements are specified in Table 8.13.2.2.1-5, based on single carrier requirement specified in Table 8.13.2.2.1-2, with the addition of the parameters in Table 8.13.2.2.1-1 and the downlink physical channel setup according to Annex C.3.2. The test coverage for different number of component carriers is defined in 8.1.2.4. Table 8.13.2.2.1-1: Test Parameters for Multi-Layer Spatial Multiplexing (FRC) for CA Table 8.13.2.2.1-2: Single carrier performance for multiple CA configurations Table 8.13.2.2.1-2A: Minimum performance (FRC) based on single carrier performance for CA with 2 DL CCs Table 8.13.2.2.1-3: Minimum performance (FRC) based on single carrier performance for CA with 3 DL CCs Table 8.13.2.2.1-4: Minimum performance (FRC) based on single carrier performance for CA with 4 DL CCs Table 8.13.2.1.1-5: Minimum performance (FRC) based on single carrier performance for CA with 5 DL CCs 8.13.2.3 Enhanced Performance Requirements Type A Closed-loop spatial multiplexing 8.13.2.3.1 Minimum Requirement Single-Layer Spatial Multiplexing 2 Tx Antenna Port with TM4 interference model (Cell-Specific Reference Symbols) The purpose of these tests is to verify the closed loop rank-one performance with wideband precoding with two transmit antennas when the PDSCH transmission in the serving cell is interfered by PDSCH of one dominant interfering cell applying transmission mode 4 interference model defined in clause B.5.3. In Table 8.13.2.3.1-1, Cell 1 is the serving cell, and Cell 2 is the interfering cell. The downlink physical channel setup is according to Annex C.3.2 for each of Cell 1 and Cell 2, respectively. For CA with 2 DL CCs, the requirements are specified in Table 8.13.2.3.1-3, based on single carrier requirement specified in Table 8.13.2.3.1-2, with the addition of the parameters in Table 8.13.2.3.1-1 and the downlink physical channel setup according to Annex C.3.2. Table 8.13.2.3.1-1: Test Parameters for Single-Layer Spatial Multiplexing (FRC) with TM4 interference model for CA Table 8.13.2.3.1-2: Single carrier performance for multiple CA configurations Enhanced Performance Requirement Type A Table 8.13.2.3.1-3: Minimum performance (FRC) based on single carrier performance for CA with 2 DL CCs | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.13.2.2.1 |
Subsets and Splits
No saved queries yet
Save your SQL queries to embed, download, and access them later. Queries will appear here once saved.