Search is not available for this dataset
doc_id
int64 1
6.72k
⌀ | Section
stringlengths 5
247
⌀ | Content
stringlengths 501
147k
⌀ | Source
stringclasses 456
values | Document Title
stringclasses 22
values | Working Group
stringclasses 21
values | Series Subject
stringclasses 9
values | Subclause
stringlengths 1
13
⌀ |
|---|---|---|---|---|---|---|---|
6,001 | 5.2.18.2.2 Nucmf_Provisioning_Delete service operation | Service operation name: Nucmf_Provisioning_Delete Description: The consumer deletes a UCMF dictionary entry(s) for a Manufacturer-assigned UE Radio Capability ID(s). The consumer provides a (list of) UE radio capability ID value(s) to be deleted or it may provide the IMEI/TAC values for which the associated UE radio capability ID entries shall be no longer used. Inputs, Required: UE Radio Capability ID(s) of the UCMF dictionary entry(s) to be deleted or IMEI/TAC that no longer use associated UE radio Capability ID(s). Inputs, Optional: None. Outputs, Required: None. Outputs, Optional: None. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.18.2.2 |
6,002 | 5.7.3c.2 Initiation | In case of MP, a MP remote UE initiates the procedure to report indirect path failures when neither MCG nor indirect path transmission is suspended and when one of the following conditions is met: 1> upon detecting a SL indirect path failure resulting from sidelink radio link failure on the PC5 unicast link or receiption of NotificationMessageSidelink from the L2 U2N Relay UE indicating Uu failure, or indirect path addition/change failure in accordance with 5.3.5.17.2.3; or 1> upon detecting a N3C indirect path failure, including N3C connection failure or Uu failure of the relay UE with N3C indirect path; Upon initiating the procedure, the UE shall: 1> if the procedure was initiated to report SL indirect path failure: 2> reset the sidelink specific MAC of this destination; 2> stop T421 if running; 1> suspend indirect path transmission for all SRBs and DRBs; 1> initiate transmission of the IndirectPathFailureInformation message in accordance with 5.7.3c.4; | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.7.3c.2 |
6,003 | 8.2.2.2.3A Minimum Requirement 2 Tx Antenna Ports (demodulation subframe overlaps with aggressor cell ABS and CRS assistance information are configured) | The requirements are specified in Table 8.2.2.2.3A-2, with the addition of parameters in Table 8.2.2.2.3A-1. The purpose is to verify the performance of transmit diversity (SFBC) with 2 transmit antennas if the PDSCH transmission in the serving cell takes place in subframes that overlap with ABS [9] of the aggressor cell with CRS assistance information. In Table 8.2.2.2.3A-1, Cell 1 is the serving cell, and Cell 2 and Cell 3 are the aggressor cells. The downlink physical channel setup for Cell 1 is according to Annex C.3.2 and for Cell 2 and Cell 3 is according to Annex C.3.3, respectively. The CRS assistance information [7] includes Cell 2 and Cell 3. Table 8.2.2.2.3A-1: Test Parameters for Transmit diversity Performance (FRC) Table 8.2.2.2.3A-2: Minimum Performance Transmit Diversity (FRC) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.2.2.2.3A |
6,004 | 5.4.2.6 Authentication not accepted by the UE | In an EPS authentication challenge, the UE shall check the authenticity of the core network by means of the AUTN parameter received in the AUTHENTICATION REQUEST message. This enables the UE to detect a false network. During an EPS authentication procedure, the UE may reject the core network due to an incorrect AUTN parameter (see 3GPP TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [19]). This parameter contains three possible causes for authentication failure: a) MAC code failure: If the UE finds the MAC code (supplied by the core network in the AUTN parameter) to be invalid, the UE shall send an AUTHENTICATION FAILURE message to the network, with the EMM cause #20 "MAC failure". The UE shall then follow the procedure described in clause 5.4.2.7, item c. b) Non-EPS authentication unacceptable: If the UE finds that the "separation bit" in the AMF field of AUTN supplied by the core network is 0, the UE shall send an AUTHENTICATION FAILURE message to the network, with the EMM cause #26 "non-EPS authentication unacceptable" (see clause 6.1.1 in 3GPP TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [19]). The UE shall then follow the procedure described in clause 5.4.2.7, item d. c) SQN failure: If the UE finds the SQN (supplied by the core network in the AUTN parameter) to be out of range, the UE shall send an AUTHENTICATION FAILURE message to the network, with the EMM cause #21 "synch failure" and a re-synchronization token AUTS provided by the USIM (see 3GPP TS 33.102[ 3G security; Security architecture ] [18]). The UE shall then follow the procedure described in clause 5.4.2.7, item e. If the UE returns an AUTHENTICATION FAILURE message to the network, the UE shall delete any previously stored RAND and RES and shall stop timer T3416, if running. If the UE has a PDN connection for emergency bearer services established or is establishing such a PDN connection, additional UE requirements are specified in clause 5.4.2.7, under "for items c, d, e". If the UE is attached for access to RLOS and has a PDN connection for RLOS established or is establishing such a PDN connection, additional UE requirements are specified in clause 5.4.2.7, under "for items c, d, e". | 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.6 |
6,005 | 5.17.2.3.4 Redirection for UEs in connected state | When the UE supports single-registration mode or dual-registration mode without N26 interface: - If the UE is in CM-CONNECTED state in 5GC, the NG-RAN may perform RRC Connection Release with Redirection to E-UTRAN based on certain criteria (e.g. based on local configuration in NG-RAN, or triggered by the AMF upon receiving Handover Request message from NG-RAN). - If the UE is in ECM-CONNECTED state in EPC, the E-UTRAN may perform RRC Connection release with redirection to NG-RAN based on certain criteria (e.g. based on local configuration in E-UTRAN, or triggered by the MME upon receiving handover request from E-UTRAN). | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.17.2.3.4 |
6,006 | A.2.2 Service operation naming | If a service contains multiple independent operations, each operation shall be named and referred to according to the following nomenclature: - Nnfname_ServiceName_ServiceOperation[Method], where the ServiceName represents the actual NF service. The ServiceOperation itself defines the available service functionality which can be addressed by a specific operation. The Method(s) is/are the action(s), how the ServiceOperation can be used. It can be created, read, updated or deleted. Example (illustrative): Namf_Session_Registration[Create], Namf_Session_Registration[Delete] In general, this operation naming structure for the given example is depicted in a tree-structure diagram: Figure A.2.2-1: Service Operation Naming and its Methods | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | A.2.2 |
6,007 | 9.3.17a CC-Establishment $(CCBS)$ | A mobile station that does not support the "Network initiated MO call" option shall treat this message as a message with message type not defined for the PD. This message is sent from the network to the mobile station to provide information on the call that the mobile station should attempt to establish. See Table 9.67a/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Message type: CC-ESTABLISHMENT Significance: local Direction: network to mobile station Table 9.67a/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : CC-Establishment message content | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.3.17a |
6,008 | 4.15.9.5.1 Network timing synchronization status | Figure 4.15.9.5.1-1: Procedure for TSCTSF subscription to RAN and/or UPF/NW-TT timing synchronization status 0. The AF requests creation or modification of ASTI or PTP based time synchronization service as described in clauses 4.15.9.4 and 4.15.9.3 including clock quality detail level and clock quality acceptance criteria (if applicable) in the request. If the request is received at the NEF, it checks whether the AF is authorized to send the request and forwards the request to the TSCTSF. If network timing synchronization status reports are provisioned using node-level signalling via control plane, the TSCTSF determines the serving AMF(s) and the UPF/NW-TT nodes (if applicable) for the UE(s) that needs to initiate network timing synchronization status monitoring. Otherwise, if network timing synchronizations status reports are provisioned via OAM, steps 1-3 and 5-7 are skipped. 1-2. (When the procedure is triggered by the AF request to influence the 5G access stratum time distribution or by PTP instance activation, modification): Upon the reception of the clock quality detail level and clock quality acceptance criteria (if applicable) in the AF request in step 0, the TSCTSF needs to be subscribed to NG-RAN timing synchronization status updates at the NG-RAN nodes that may provision access stratum time distribution information to the target UE. NG-RAN timing synchronization status updates provisioning may be configured via AMF (with node level signalling as illustrated in steps 1-2). The TSCTSF sends Namf_Communication_NonUeN2InfoSubscribe to initiate the subscription for the NG-RAN timing synchronization status updates from the AMF. As part of this subscription, the TSCTSF may specify TA(s) and/or NG-RAN node(s) in the subscription for the timing synchronization status reporting. Based on local configuration and/or TA or NG-RAN node information as received from the TSCTSF, the AMF may subscribe to some or all NG-RAN nodes in the TA(s) for the timing synchronizations status reporting. 3. (When the procedure is triggered by the AF request for PTP instance activation, modification and if the UPF/NW-TT is involved in providing time information to DS-TT): Upon the reception of the clock quality acceptance criteria in the AF request in step 0, the TSCTSF needs to be subscribed to UPF/NW-TT timing synchronization status updates at the UPF/NW-TT that may provision time information via PTP to the target UE. UPF/NW-TT timing synchronization status updates provisioning may be configured via OAM or via UMIC. 4. The RAN node is pre-configured for the thresholds for each timing synchronization status attribute as described in clause 5.27.1.12 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. When the network timing synchronization status exceeds or meets again any of the pre-configured thresholds, the NG-RAN node detects a change on its timing synchronization status (e.g., degradation, failure, improvement). 5-6. If the NG-RAN node detects a change on its timing synchronization status as described in clause 5.27.1.12 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] and the timing synchronization status reporting is configured via the AMF in step 1, the NG-RAN node notifies the AMF providing a NG-RAN timing synchronization status update. The update can contain the information elements listed in Table 5.27.1.12-1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], and the scope of the timing synchronization status (as described in clause 5.27.1.12 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]). The AMF forwards the update to the subscribed TSCTSF. 7. If the UPF/NW-TT detects a change on its timing synchronization status and timing synchronization status reporting is configured via UMIC in step 3, the UPF/NW-TT notifies the TSCTSF providing a UPF/NW-TT timing synchronization status update via UMIC. The update can contain the information elements listed in Table K.1-2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. 8. Upon the reception of a change in the NG-RAN and/or NW-TT timing synchronization status update, the TSCTSF shall determine if the UE is impacted and whether the clock quality acceptance criteria can still be met. For each scope of the timing synchronization status received from the RAN in step 6, if the status indicates degradation or failure, TSCTSF may set the Area of Interest to gNB node ID(s) or Cell IDs in the scope of the timing synchronization status. The TSCTSF uses the resulted Area of Interest to subscribe for the UE presence in Area of Interest from the AMF that is serving the gNB node ID as described in clause 5.27.1.12 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If the status indicates recovery, the TSCTSF may remove the corresponding scope from the subscription. Upon reception of notification for the UE presence in the Area of Interest, if the TSCTSF determines that the UE is impacted for ASTI service, the TSCTSF performs steps 15-16 in clause 4.15.9.4 to notify the AF the acceptance criteria result. Upon reception of notification for the UE presence in the Area of Interest, if the TSCTSF determines that the UE is impacted for PTP service, the TSCTSF performs steps 9-11 in clause 4.15.9.3.2 to notify the AF the acceptance criteria result. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.15.9.5.1 |
6,009 | 5.3.21 CIoT 5GS optimizations | CIoT 5GS optimizations provide improved support of small data and SMS transfer. A UE supporting CIoT 5GS optimizations can indicate the 5GS CIoT network behaviour the UE can support and prefers to use during the registration procedure (see 3GPP TS 23.502[ Procedures for the 5G System (5GS) ] [9]). The UE may indicate the support for control plane CIoT 5GS optimization, user plane CIoT 5GS optimization, N3 data transfer and header compression (see subclause 9.11.3.1). Furthermore, the UE may, separately from the indication of support, indicate preference for control plane CIoT 5GS optimization or user plane CIoT 5GS optimization (see subclause 9.11.3.9A). The indication of preference is also considered as the request to use. A UE supporting CIoT EPS optimizations can also indicate the EPS CIoT network behaviour the UE can support during the registration procedure. Furthermore, the UE may, separately from the indication of support, indicate preference for control plane CIoT EPS optimization or user plane CIoT EPS optimization. NOTE 1: CIoT 5GS optimizations are not supported by NR connected to 5GCN. NOTE 2: If the UE does not support user plane CIoT 5GS optimization, it does not indicate preference for user plane CIoT 5GS optimization. The UE can be in NB-N1 mode or WB-N1 mode when requesting the use of CIoT 5GS optimizations during the registration procedure. A UE in NB-N1 mode always indicates support for control plane CIoT 5GS optimization. In NB-N1 mode, the UE, when requesting the use of CIoT 5GS optimizations, does not: - request an initial registration for emergency services; - request a PDU session establishment for emergency PDU session; or - indicate UE's usage setting during the registration procedure. The network does not indicate to the UE support of emergency services when the UE is in NB-N1 mode (see subclause 5.5.1.2.4 and 5.5.1.3.4). The control plane CIoT 5GS optimization enables support of efficient transport of user data (IP, Ethernet and Unstructured) or SMS messages over control plane via the AMF without triggering user-plane resources establishment. The support of control plane CIoT 5GS optimization is mandatory for the network in NB-N1 mode and optional in WB-N1 mode. Optional header compression of IP data and Ethernet data can be applied to PDU sessions with IP PDU session type and Ethernet PDU session type that are configured to support header compression. For IP header compression, Robust Header Compression (ROHC) protocol specified in IETF RFC 5795 [39B] is used. For Ethernet header compression, Ethernet Header Compression (EHC) protocol specified in 3GPP TS 38.323[ NR; Packet Data Convergence Protocol (PDCP) specification ] [29] is used. For a UE that supports Location Services (LCS) notification mechanisms in N1 mode, the control plane CIoT 5GS optimization also enables the transport of location services messages from 5GMM-IDLE mode using the CONTROL PLANE SERVICE REQUEST message when location services are requested (see subclause 6.7.1 in 3GPP TS 23.273[ 5G System (5GS) Location Services (LCS); Stage 2 ] [6B]). The user plane CIoT 5GS optimization enables support for change from 5GMM-IDLE mode over 3GPP access to 5GMM-CONNECTED mode over 3GPP access without the need for using the service request procedure (see subclause 5.3.1.5). If the UE supports user plane CIoT 5GS optimization, it shall also support N3 data transfer. If the UE indicates support of one or more CIoT 5GS optimizations and the network supports one or more CIoT 5GS optimizations and decides to accept the registration request, the network indicates the supported CIoT 5GS optimizations to the UE per registration area when accepting the UE request. Network indication of support is interpreted by the UE as the acceptance to use the respective feature. After completion of the registration procedure, the UE and the network can then use the accepted CIoT 5GS optimizations for the transfer of user data (IP, Ethernet, Unstructured and SMS). A UE in NB-N1 mode or WB-N1 mode can request the use of SMS over NAS by setting the SMS requested bit of the 5GS update type IE in the REGISTRATION REQUEST message as specified in subclauses 5.5.1.2.2 and 5.5.1.3.2. The AMF indicates whether it allows the use of SMS over NAS for a UE in NB-N1 mode or WB-N1 mode by setting the SMS allowed bit of the 5GS registration result IE in the REGISTRATION ACCEPT message as specified in subclauses 5.5.1.2.4 and 5.5.1.3.4. If the UE and the network support both the control plane CIoT 5GS optimization and N3 data transfer, then when receiving the UE's request for a PDU session establishment, the AMF decides whether the PDU session should be NEF PDU session or N6 PDU session as specified in 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8] and then: a) if NEF PDU session is to be established for unstructured data type, the AMF includes control plane only indication for the requested PDU session to the SMF; b) if N6 PDU session is to be established and the DNN or S-NSSAI of the newly requested N6 PDU session supports interworking with EPS as specified in 3GPP TS 23.502[ Procedures for the 5G System (5GS) ] [9]: 1) if there are existing N6 PDU sessions supporting interworking with EPS for this UE that were established with the control plane only indication, the AMF includes the control plane only indication for the newly requested N6 PDU session to the SMF; or 2) if there are existing N6 PDU sessions supporting interworking with EPS for this UE that were established without the control plane only indication, the AMF does not include the control plane only indication for the newly requested N6 PDU session to the SMF; 3) if there is no existing N6 PDU session supporting interworking with EPS for this UE, the AMF determines whether to include the control plane only indication for the newly requested N6 PDU session to the SMF based on local policies, the UE's preferred CIoT network behaviour and the supported CIoT network behaviour; and c) if N6 PDU session is to be established and the DNN or S-NSSAI of the N6 PDU session does not support interworking with EPS as specified in 3GPP TS 23.502[ Procedures for the 5G System (5GS) ] [9], the AMF determines whether to include the control plane only indication for the newly requested N6 PDU session to the SMF based on local policies, the UE's preferred CIoT network behaviour and the supported CIoT network behaviour. In NB-N1 mode, if the UE or the network does not support N3 data transfer, then when receiving the UE's request for a PDU session establishment, the AMF decides whether the PDU session should be NEF PDU session or N6 PDU session as specified in 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8] and then includes the control plane only indication for the requested PDU session to the SMF. If the network supports user plane CIoT 5GS optimization, it shall also support N3 data transfer. Broadcast system information may provide information about support of CIoT 5GS optimizations (see 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [25A]). At reception of new broadcast system information, the lower layers deliver it to the 5GMM layer in the UE. The information provided by lower layers is per PLMN and used by the UE to determine whether certain CIoT 5GS optimizations are supported in the cell. The UE shall not attempt to use CIoT 5GS optimizations which are indicated as not supported. In NB-N1 mode, at any given time, there cannot be user-plane resources established for a number of PDU sessions that exceeds the UE' s maximum number of supported user-plane resources. The UE in NB-N1 mode shall not: a) request the establishment of user-plane resources for a number of PDU sessions that exceeds the UE' s maximum number of supported user-plane resources; or b) initiate the establishment of a new PDU session, or request the transfer of a PDU session from the non-3GPP access to the 3GPP access, if: 1) the UE has indicated preference for user plane CIoT 5GS optimization; 2) the network accepted the use of user plane CIoT 5GS optimization; and 3) the UE currently has user-plane resources established fora number of PDU sessions that is equal to the UE' s maximum number of supported user-plane resources. The AMF enforces a limit on the number of PDU sessions with active user-plane resources for a UE in NB-N1 mode based on the UE's maximum number of supported user-plane resources as follows: a) there can be a maximum of one PDU session with active user-plane resources when the Multiple user-plane resources support bit is set to "Multiple user-plane resources not supported", or b) there can be a maximum of two PDU sessions with active user-plane resources when the Multiple user-plane resources support bit is set to "Multiple user-plane resources supported". A PDU session for a UE in NB-N1 mode shall only have one QoS rule and that is the default QoS rule. Reflective QoS is not supported in NB-N1 mode. Reflective QoS is not applicable for a PDU session with control plane only indication. In NB-N1 mode, when the UE requests the lower layer to establish a RRC connection and the UE requests the use of user plane CIoT 5GS optimization, the UE shall pass an indication of the requested CIoT 5GS optimizations to the lower layers. If the UE requests the use of N3 data transfer without user plane CIoT 5GS optimization, then the UE shall also pass an indication of user plane CIoT 5GS optimization to lower layers. In WB-N1 mode, when the UE requests the lower layer to establish a RRC connection and the UE requests the use of control plane CIoT 5GS optimization or user plane CIoT 5GS optimization, the UE shall pass an indication of the requested CIoT 5GS optimizations to the lower layers. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.3.21 |
6,010 | 10.2.5.1 NPDCCH formats | The narrowband physical downlink control channel carries control information. A narrowband physical control channel is transmitted on an aggregation of one or two consecutive narrowband control channel elements (NCCEs), where a narrowband control channel element corresponds to 6 consecutive subcarriers in a subframe where NCCE 0 occupies subcarriers 0 through 5 and NCCE 1 occupies subcarriers 6 through 11. The NPDCCH supports multiple formats as listed in Table 10.2.5.1-1. For NPDCCH format 1, both NCCEs belong to the same subframe. One or two NPDCCHs can be transmitted in a subframe. Table 10.2.5.1-1: Supported NPDCCH formats | 3GPP TS 36.211 | Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation | RAN1 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 10.2.5.1 |
6,011 | 5.8.2.6.2 Activation of Usage Reporting in UPF | Triggered by the PCC rules received from the PCF or preconfigured information available at SMF, as well as from the CHF for online charging method via quota management mechanisms, the SMF shall provide Usage Reporting Rules to the UPF for controlling how usage reporting is performed. The SMF shall request the report of the relevant usage information for Usage Monitoring, 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]. Each Usage Reporting Rule requested for usage monitoring control is associated with the PDR(s) whose traffic is to be accounted under this rule. The SMF shall generate the Usage Reporting Rule for each Monitoring-key within the active PCC Rule(s), either preconfigured or received from the PCF and also shall keep the mapping between them. Multiple Usage Reporting Rules may be associated with the same PDR. The SMF shall request the report of the relevant usage information for offline and online charging, based on Charging keys and additional triggers which are specified in TS 32.255[ Telecommunication management; Charging management; 5G data connectivity domain charging; Stage 2 ] [68]. Each Usage Reporting Rule requested for offline or online charging is associated with the PDR(s) whose traffic is to be accounted under this rule. The SMF shall generate the Usage Reporting Rule for each Charging key and Sponsor Identity (if applicable) within the active PCC Rule(s), either preconfigured or received from the PCF, and also shall keep the mapping between them. Multiple Usage Reporting Rules may be associated with the same PDR. The SMF function shall also provide reporting trigger events to the UPF for when to report usage information. The reporting trigger events (e.g. triggers, threshold information etc.) shall be supported for the PDU Session level reporting as well as on Rule level basis as determined by the SMF. The triggers may be provided as a volume, time or event to cater for the different charging/usage monitoring models supported by the TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45] for usage monitoring and by TS 32.255[ Telecommunication management; Charging management; 5G data connectivity domain charging; Stage 2 ] [68] for converged offline and online charging. The SMF shall decide on the thresholds value(s) based on allowance received from PCF, CHF or based on local configuration. Other parameters for instructing the UPF to report usage information are defined in TS 29.244[ Interface between the Control Plane and the User Plane nodes ] [65]. When the PCC Rule attribute Service Data flow handling while requesting credit (specified in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]) indicates "non-blocking", the SMF shall request the report of the relevant usage information for the Charging key and Sponsor Identity (if applicable) and provide a default threshold value to the UPF while waiting for the quota from the CHF. In some cases, the same Usage Reporting Rule can be used for different purposes (for both usage monitoring and charging), e.g. in the case that the same set of PDR(s), measurement method, trigger event, threshold, etc. apply. Similarly a reported measurement can be used for different purposes by the SMF. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.8.2.6.2 |
6,012 | 9.3.4.2.1 FDD | For the parameters specified in Table 9.3.4.2.1-1, and using the downlink physical channels specified in Annex C.3.2, the minimum requirements are specified in Table 9.3.4.2.1-2 and by the following a) the ratio of the throughput obtained when transmitting on subbands reported by the UE the corresponding TBS and that obtained when transmitting the TBS indicated by the reported wideband CQI median on a randomly selected subband in set S shall be ≥ ; The requirements only apply for subbands of full size and the random scheduling across the subbands is done by selecting a new subband in each TTI for FDD. The transport block size TBS (wideband CQI median) is that resulting from the code rate which is closest to that indicated by the wideband CQI median and theentry in Table 7.1.7.2.1-1 of TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [6] that corresponds to the subband size. Table 9.3.4.2.1-1 Subband test for single antenna transmission (FDD) Table 9.3.4.2.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.4.2.1 |
6,013 | 16.13.4 RRM measurement relaxations | RRM measurement relaxation is enabled and disabled by the network. In RRC_IDLE and RRC_INACTIVE an (e)RedCap UE is allowed to relax neighbour cell RRM measurements when the stationary criterion is met or when both stationary criterion and not-at-cell-edge criterion are met. Network may configure stationary criterion for an (e)RedCap UE in RRC_CONNECTED and the UE reports its RRM measurement relaxation fulfilment status using UE Assistance Information when the stationarity criterion is met or no longer met. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.13.4 |
6,014 | 6.14.2.3 SoR Counter | The AUSF and the UE shall associate a 16-bit counter, CounterSoR, with the key KAUSF. The UE shall initialize the CounterSoR to 0x00 0x00 when the newly derived KAUSF is stored (see clause 6.2.2.2). The UE shall store the SoR counter. If the USIM supports both 5G parameters storage and 5G parameters extended storage, then CounterSoR shall be stored in the USIM. Otherwise, CounterSoR shall be stored in the non-volatile memory of the ME To generate the SoR-MAC-IAUSF, the AUSF shall use the CounterSoR. The CounterSoR shall be incremented by the AUSF for every new computation of the SoR-MAC-IAUSF. The CounterSoR is used as freshness input into SoR-MAC-IAUSF and SoR-MAC-IUE derivations as described in the Annex A.17 and Annex A.18 respectively, to mitigate the replay attack. The AUSF shall send the value of the CounterSoR (used to generate the SoR-MAC-IAUSF) along with the SoR-MAC-IAUSF to the UE. The UE shall only accept CounterSoR value that is greater than stored CounterSoR value. The UE shall store the received CounterSoR, only if the verification of the received SoR-MAC-IAUSF is successful. The UE shall use the stored CounterSoR received from the HPLMN, when deriving the SoR-MAC-IUE for the SoR acknowledgement. The AUSF and the UE shall maintain the CounterSoR for lifetime of the KAUSF. The AUSF that supports the control plane solution for steering of roaming shall initialize the CounterSoR to 0x00 0x01 when the newly derived KAUSF is stored (see clause 6.2.2.1). The AUSF shall set the CounterSoR to 0x00 0x02 after the first calculated SoR-MAC-IAUSF, and monotonically increment it for each additional calculated SoR-MAC-IAUSF. The SoR Counter value of 0x00 0x00 shall not be used to calculate the SoR-MAC-IAUSF and SoR-MAC-IUE. The AUSF shall suspend the SoR protection service for the UE, if the CounterSoR associated with the KAUSF of the UE, is about to wrap around. When a fresh KAUSF is generated for the UE, the CounterSoR at the AUSF is reset to 0x00 0x01 as defined above and the AUSF shall resume the SoR protection service for the UE. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.14.2.3 |
6,015 | 6.10.1.2 Mapping to resource elements | The reference signal sequence shall be mapped to complex-valued modulation symbols used as reference symbols for antenna port in slot according to where The variables and define the position in the frequency domain for the different reference signals where is given by The cell-specific frequency shift is given by . Resource elements used for transmission of cell-specific reference signals on any of the antenna ports in a slot shall not be used for any transmission on any other antenna port in the same slot and set to zero. In an MBSFN subframe, cell-specific reference signals shall only be transmitted in the non-MBSFN region of the MBSFN subframe. Figures 6.10.1.2-1 and 6.10.1.2-2 illustrate the resource elements used for reference signal transmission according to the above definition. The notation is used to denote a resource element used for reference signal transmission on antenna port. Figure 6.10.1.2-1. Mapping of downlink reference signals (normal cyclic prefix) Figure 6.10.1.2-2. Mapping of downlink reference signals (extended cyclic prefix) | 3GPP TS 36.211 | Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation | RAN1 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.10.1.2 |
6,016 | 9.14.1.2 TDD | The following requirements apply to UE Category NB2 capable of npdsch-16QAM-r17. For the parameters specified in Table 9.14.1.2-1, and using the downlink physical channels specified in C.3.6, the reported candidateRep value according to RC.33 TDD in Table A.4-1 shall be in the range of ±1 of the reported median more than 90% of the time. If the NPDSCH BLER using the transport format indicated by median candidateRep value is less than or equal to 0.1, the BLER using the transport format indicated by the (median candidateRep value + 1) shall be greater than 0.1. If the NPDSCH BLER using the transport format indicated by the median candidateRep value is greater than 0.1, the BLER using transport format indicated by (median candidateRep value - 1) shall be less than or equal to 0.1. Table 9.14.1.2-1: TDD | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 9.14.1.2 |
6,017 | 14.1.4 Nausf_UPUProtection service | The following table illustrates the security related services for UE Parameters Update that AUSF provides. Table 14.1.4-1: NF services for UE Parameters Update provided by AUSF Service operation name: Nausf_UPUProtection. Description: The AUSF calculates the UPU-MAC-IAUSF as specified in the Annex A.19 of this document using UE specific home key (KAUSF) along with the UE Parameters Update Data received from the requester NF (see clause A.19) and delivers the UPU-MAC-IAUSF and CounterUPU to the requester NF. If the ACK Indication input is present, then the AUSF shall compute the UPU-XMAC-IUE and return the computed UPU-XMAC-IUE as specified in Annex A.20 of the present document, in the response. The details of the UE Parameters Update Data is specified in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [35]. Input, Required: Requester ID, SUPI, service name, UE Parameters Update Data. Input, Optional: ACK Indication. Output, Required: UPU-MAC-IAUSF, CounterUPU or error (counter_wrap). Output, Optional: UPU-XMAC-IUE (if the ACK Indication input is present, then the UPU-XMAC-IUE shall be computed and returned). | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 14.1.4 |
6,018 | 13.2.2.2 Procedure for Key agreement and Parameter exchange | 1. The two SEPPs shall perform the following cipher suite negotiation to agree on a cipher suite to use for protecting NF service related signalling over N32-f. 1a. The SEPP which initiated the first N32-c connection shall send a Security Parameter Exchange Request message to the responding SEPP including the initiating SEPP’s supported cipher suites. The cipher suites shall be ordered in initiating SEPP’s priority order. The SEPP shall provide an initiating SEPP’s N32-f context ID for the responding SEPP. 1b. The responding SEPP shall compare the received cipher suites to its own supported cipher suites and shall select, based on its local policy, a cipher suite, which is supported by both initiating SEPP and responding SEPP. 1c. The responding SEPP shall send a Security Parameter Exchange Response message to the initiating SEPP including the selected cipher suite for protecting the NF service related signalling over N32. The responding SEPP shall provide a responding SEPP’s N32-f context ID for the initiating SEPP. 2. The two SEPPs may perform the following exchange of Data-type encryption policies and Modification policies. Both SEPPs shall store protection policies sent by the peer SEPP: 2a. The SEPP which initiated the first N32-c connection shall send a Security Parameter Exchange Request message to the responding SEPP including the initiating SEPP’s Data-type encryption policies, as described in clause 13.2.3.2, and Modification policies, as described in clause 13.2.3.4. 2b. The responding SEPP shall store the policies if sent by the initiating SEPP. 2c. The responding SEPP shall send a Security Parameter Negotiation Response message to the initiating SEPP with the responding SEPP’s suite of protection policies. 2d. The initiating SEPP shall store the protection policy information if sent by the responding SEPP. 3. The two SEPPs shall exchange IPX security information lists that contain information on IPX public keys or certificates that are needed to verify IPX modifications at the receiving SEPP. 4. The two SEPPs shall export keying material from the TLS session established between them using the TLS export function. For TLS 1.2, the exporter specified in RFC 5705 [61] shall be used. For TLS 1.3, the exporter described in section 7.5 of RFC 8446 [60] shall be used. The exported key shall be used as the master key to derive session keys and IVs for the N32-f context as specified in clause 13.2.4.4.1. 5. When the responding SEPP needs to initiate traffic, e.g., error reporting, in the reverse direction to the sending SEPP, the responding SEPP in the first N32-c connection shall now setup a second N32-c connection by establishing a mutually authenticated TLS connection with the peer SEPP. NOTE: The second N32-c connection setup by the responding SEPP does not perform the negotiation of steps 1-4. 6. The two SEPPs start exchanging NF to NF service related signalling over N32-f and tear down the N32-c connection. The SEPPs may initiate new N32-c TLS sessions for any further N32-c communication that may occur over time while application layer security is applied to N32-f. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 13.2.2.2 |
6,019 | 4.5.1.3.2 Mobile Originating CM Activity $(CCBS)$ | When a CM sublayer entity in the network requests the MM sublayer to establish a MM connection, the MM sublayer will request the establishment of an RR connection to the RR sublayer if no RR connection to the desired mobile station exists. The MM sublayer is informed when the paging procedure is finished (see 3GPP TS 44.018[ None ] [84] subclause 3.3.2 and 3GPP TS 25.331[ None ] [23c]) and the mobile station shall enter the MM state WAIT FOR NETWORK COMMAND. In A/Gb mode, when an RR connection is established (or if it already exists at the time the request is received), the MM sublayer may initiate any of the MM common procedures (except IMSI detach), it may request the RR sublayer to perform the RR classmark interrogation procedure and/or the security mode setting procedure. In Iu mode, when an RR connection is established (or if it already exists at the time the request is received), the MM sublayer may initiate any of the MM common procedures (except IMSI detach), it may request the RR sublayer to perform the security mode control procedure. The network should use the information contained in the Mobile Station Classmark Type 2 IE on the mobile station's support for "Network Initiated MO CM Connection Request" to determine whether to: not start this procedure (eg if an RR connection already exists), or, to continue this procedure, or, to release the newly established RR connection. In the case of a "Network Initiated MO CM Connection Request" the network shall use the established RR connection to send a CM SERVICE PROMPT message to the mobile station. If the mobile station supports "Network Initiated MO CM Connection Request", the MM sublayer of the MS gives an indication to the CM entity identified by the CM SERVICE PROMPT message and enters the MM sublayer state PROCESS CM SERVICE PROMPT. In the state PROCESS CM SERVICE PROMPT the MM sublayer waits for either the rejection or confirmation of the recall by the identified CM entity. Any other requests from the CM entities shall either be rejected or delayed until this state is left. When the identified CM entity informs the MM sublayer, that it has send the first CM message in order to start the CM recall procedure the MM sublayer enters the state MM CONNECTION ACTIVE. If the identified CM entity indicates that it will not perform the CM recall procedure and all MM connections are released by their CM entities the MS shall proceed according to subclause 4.5.3.1. If the CM SERVICE PROMPT message is received by the MS in MM sublayer states WAIT FOR OUTGOING MM CONNECTION or in WAIT FOR ADDITIONAL OUTGOING MM CONNECTION then the mobile station shall send an MM STATUS message with cause " Message not compatible with protocol state". A mobile that does not support "Network Initiated MO CM Connection Request" shall return an MM STATUS message with cause #97 "message type non-existent or not implemented" to the network. If the mobile station supports "Network Initiated MO CM Connection Request" but the identified CM entity in the mobile station does not provide the associated support, then the mobile station shall send an MM STATUS message with cause "Service option not supported". In the case of a temporary CM problem (eg lack of transaction identifiers) then the mobile station shall send an MM STATUS message with cause "Service option temporarily out of order". If an RR connection already exists and no MM specific procedure is running, the network may use it to send the CM SERVICE PROMPT message. In A/Gb mode, if the establishment of an RR connection is unsuccessful, or if any of the MM common procedures or the security mode setting fail, this is indicated to the CM layer in the network with an appropriate error cause. In Iu mode, if the establishment of an RR connection is unsuccessful, or if any of the MM common procedures or the security mode control fail, this is indicated to the CM layer in the network with an appropriate error cause. If an RR connection used for a MM specific procedure exists to the mobile station, the "Network Initiated MO CM Connection Request" may be rejected or delayed depending on implementation. When the MM specific procedure has been completed, the network may use the same RR connection for the delayed "Network Initiated MO CM Connection Request". | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.5.1.3.2 |
6,020 | 6.5.1 Description | 5G is designed to meet diverse services with different and enhanced performances (e.g. high throughput, low latency and massive connections) and data traffic model (e.g. IP data traffic, non-IP data traffic, short data bursts and high throughput data transmissions). User plane should be more efficient for 5G to support differentiated requirements. On one hand, a Service Hosting Environment located inside of operator's network can offer Hosted Services closer to the end user to meet localization requirement like low latency, low bandwidth pressure. These Hosted Services contain applications provided by operators and/or trusted 3rd parties. On the other hand, user plane paths can be selected or changed to improve the user experience or reduce the bandwidth pressure, when a UE or application changes location during an active communication, or due to operational needs in the service hosting environment (e.g. based on usage information). The 5G network can also support multiple wireless backhaul connections (e.g. satellites and/or terrestrial), and efficiently route and/or bundle traffic among them. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.5.1 |
6,021 | 6.2.4G UE maximum output power with additional requirements for V2X Communication | For QPSK the MPR requirements specified in subclause 6.2.3G does not apply, i.e. MPR = 0dB. For 16QAM and 64 QAM, the applied maximum output power reduction is obtained by taking the maximum value of MPR requirements specified in subclause 6.2.3G and A-MPR requirements specified in subclause 6.2.4G. When UE is configured for E-UTRA V2X sidelink transmissions non-concurrent with E-UTRA uplink transmissions for E-UTRA V2X operating bands specified in Table 5.5G-1, the maximum output power reduction specified as A-MPR = CEIL {MA, 0.5} Where MA is defined as follows MA = A-MPRBase + Gpost connector * A-MPRStep CEIL{MA, 0.5} means rounding upwards to closest 0.5dB. A-MPRBase and A-MPRStep are specified in Tables 6.2.4G-1, 6.2.4G-2, 6.2.4G-3 is allowed when network signalling value is provided. The supported post antenna connector gain Gpost connector is declared by the UE following the principle described in annex I. NOTE: the A-MPRstep is the increase in A-MPR allowance to allow UE to meet tighter conducted A-SE and A-SEM requirements with higher value of declared Gpost connector. A-MPRBase is the default A-MPR value when no Gpost connector is declared. A-MPRBase and A-MPRstep vary depending on channel frequency and RB allocation. For channel frequencies and RB allocations that are close to the frequency range 5815-5855MHz, those value are much higher due to stringent emission requirement in this range. Table 6.2.4G-1: Additional Maximum Power Reduction (A-MPR) for power class 3 V2X UE Table 6.2.4G-2: A-MPR for NS_33 The allowed A-MPR for the maximum output power for V2X physical signal PSBCH and PSSS/SSSS shall be as be as specified in subclause 6.2.4 for the corresponding modulation and transmission bandwidth. When UE is configured for simultaneous E-UTRA V2X sidelink and E-UTRA uplink transmissions for inter-band E-UTRA V2X / E-UTRA bands specified in Table 5.5G-2, the requirements in subclause 6.2.4G apply for V2X PSSCH and PSCCH transmission. The allowed A-MPR requirements in subclause 6.2.4D apply for other V2X sidelink transmission (PSBCH/PSSS/SSSS). The A-MPR requirements in subclause 6.2.4 apply for uplink transmission. When UE is configured for E-UTRA V2X sidelink transmissions non-concurrent with E-UTRA uplink transmissions for E-UTRA V2X operating bands specified in Table 5.5G-1, the allowed A-MPR for the maximum output power for V2X physical channels PSCCH and PSSCH shall be as specified in Table 6.2.4G-3 and 6.2.4G-4 for V2X UE power class 2. Table 6.2.4G-3: Additional Maximum Power Reduction (A-MPR) for power class 2 V2X UE | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.2.4G |
6,022 | 4.3.5.10 Preferred and Supported Network Behaviour | A UE includes in a Preferred Network Behaviour indication the Network Behaviour the UE can support and what it would prefer to use. The Preferred Network Behaviour includes this information: - Whether Control Plane CIoT EPS Optimisation is supported. - Whether User Plane CIoT EPS Optimisation is supported. - Whether Control Plane CIoT EPS Optimisation is preferred or whether User Plane Plane CIoT EPS Optimisation is preferred. - Whether S1-U data transfer is supported. - Whether SMS transfer without Combined Attach is requested. - Whether Attach without PDN Connectivity is supported. - Whether header compression for Control Plane CIoT EPS Optimisation is supported. If SMS transfer without Combined EPS Attach is requested by the UE, a supporting MME provides SMS transfer without the UE performing the combined EPS attach specified in TS 23.272[ Circuit Switched (CS) fallback in Evolved Packet System (EPS); Stage 2 ] [58]. An MME connected to NB-IoT should support SMS transfer without the UE being required to perform a Combined Attach.This feature is only available to UEs that only support NB-IoT. If S1-U data transfer is supported is indicated by the UE, the UE supports data transfer that is not subject to CIoT EPS Optimisations. If the UE indicates support of User Plane CIoT EPS Optimisation then it shall also indicate support of S1-U data transfer. If Attach without PDN connection is supported, the UE need not establish a PDN connection as part of the Attach procedure and the UE and MME may at any time release all the PDN connections and remain EPS attached. The MME indicates the network behaviour the network accepts in the Supported Network Behaviour information. This indication is per TAI List. The MME may indicate one or more of the following: - Whether Control Plane CIoT EPS Optimisation is supported. - Whether User Plane CIoT EPS Optimisation is supported. - Whether S1-U data transfer is supported. - Whether SMS transfer without Combined Attach is accepted. - Whether Attach without PDN Connectivity is supported. - Whether header compression for Control Plane CIoT EPS Optimisation is supported. If the MME indicates support of User Plane CIoT EPS Optimisation then it shall also indicate support of S1-U data transfer. If the UE and MME indicate support for User Plane CIoT EPS Optimisation, MME sets the UE User Plane CIoT Support Indicator to "supported" in S1-AP messages as defined in TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [36]. For NB-IoT UEs that only support Control Plane CIoT EPS Optimisation, the MME shall include support for Control Plane CIoT EPS Optimisation in NAS accept messages. A UE that supports the NB-IoT shall always indicate support for Control Plane CIoT EPS Optimisation. In a network that supports Dedicated Core Networks (see clause 5.19), the Preferred Network Behaviour indication from the UE may be used to influence policy decisions that can cause rerouting of the Attach or TAU from an MME to another MME. Other CIoT EPS Optimisations include "Attach without PDN connection establishment"; "PDN type = non-IP"; and "UE connection to SCEF". These features are requested by implicit and explicit signalling described within the relevant clauses of this TS. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.3.5.10 |
6,023 | 9.11.3.12A Additional information requested | The purpose of the Additional information requested information element is to enable the UE to request ciphering keys for deciphering of ciphered broadcast assistance data. The Additional information requested information element is coded as shown in figure 9.11.3.12A.1 and table 9.11.3.12A.1. The Additional information requested is a type 4 information element with a length of 3 octets. Figure 9.11.3.12A.1: Additional information requested information element Table 9.11.3.12A.1: Additional information requested information element | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.11.3.12A |
6,024 | 2.8.2.1.2 Mapping in the UE | When a UE moves from an E-UTRAN to a GERAN/UTRAN, the UE needs to map the GUTI to an RAI, a P-TMSI and a P-TMSI Signature, for them to be sent to the SGSN. For GERAN, the TLLI is derived from the P-TMSI by the UE and is a foreign TLLI (see clause 2.6). The mapping of the GUTI shall be done to the combination of RAI of GERAN / UTRAN and the P-TMSI: E-UTRAN <MCC> maps to GERAN/UTRAN <MCC> E-UTRAN <MNC> maps to GERAN/UTRAN <MNC> E-UTRAN <MME Group ID> maps to GERAN/UTRAN <LAC> E-UTRAN <MME Code> maps to GERAN/UTRAN <RAC> and is also copied into the 8 Most Significant Bits of the NRI field within the P-TMSI; E-UTRAN <M-TMSI> maps as follows: - 6 bits of the E-UTRAN <M-TMSI> starting at bit 29 and down to bit 24 are mapped into bit 29 and down to bit 24 of the GERAN/UTRAN <P-TMSI>; - 16 bits of the E-UTRAN <M-TMSI> starting at bit 15 and down to bit 0 are mapped into bit 15 and down to bit 0 of the GERAN/UTRAN <P-TMSI>; - and the remaining 8 bits of the E-UTRAN <M-TMSI> are mapped into the 8 Most Significant Bits of the <P-TMSI signature> field. The UE shall fill the remaining 2 octets of the <P-TMSI signature> according to clauses 9.1.1, 9.4.1, 10.2.1, or 10.5.1 of 3GPP TS.33.401 [89] , as appropriate, for RAU/Attach procedures. For UTRAN, the 10-bit long NRI bits are masked out from the P-TMSI and are also supplied by the UE to the RAN node as IDNNS (Intra Domain NAS Node Selector) (see 3GPP TS 23.236[ Intra-domain connection of Radio Access Network (RAN) nodes to multiple Core Network (CN) nodes ] [23]). However, the RAN configured NRI length should not exceed 8 bits. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 2.8.2.1.2 |
6,025 | 4.8.2.3.2 Interworking between TNGF or N3IWF connected to 5GCN and E-UTRAN | If: a) the UE has registered in neither N1 mode over 3GPP access nor S1 mode yet; and b) the UE has at least one active PDU session associated with non-3GPP access which the UE intends to transfer to EPS, the UE shall initiate an EPS attach procedure and include a PDN CONNECTIVITY REQUEST message with a request type in the ATTACH REQUEST message to activate a default EPS bearer context for one of the active PDU sessions which the UE intends to transfer to EPS (see 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15]). The request type is set as follows: - if the PDU session which the UE intends to transfer is a non-emergency PDU session, the request type is set to "handover"; and - if the PDU session which the UE intends to transfer is an emergency PDU session, the request type is set to "handover of emergency bearer services" and the default bearer to be activated is the default EPS bearer context for the emergency PDU session. NOTE 1: It is necessary for the UE to support sending an ATTACH REQUEST message containing a PDN CONNECTIVITY REQUEST message with request type set to "handover" or "handover of emergency bearer services" to transfer a PDU session from N1 mode to S1 mode for interworking between TNGF or N3IWF connected to 5GCN and E-UTRAN. NOTE 2: The order of PDU sessions to be tranferred to EPS is up to UE implementation. After successful completion of the EPS attach procedure where the activated default EPS bearer context is not for emergency service, the UE shall initiate a UE requested PDN connectivity procedure with request type set to "handover" for non-emergency PDU session or "handover of emergency bearer services" for emergency PDU session in the PDN CONNECTIVITY REQUEST message to transfer each of the other PDU sessions which the UE intends to transfer to EPS, if any. If: a) the UE has not registered in N1 mode over non-3GPP access yet; and b) the UE has at least one active PDN connection which the UE intends to transfer to TNGF or N3IWF connected to 5GCN, the UE shall initiate an initial registration procedure over non-3GPP access (see subclause 5.5.1.2). After successful completion of the 5GS initial registration in N1 mode over non-3GPP access, the UE shall initiate a UE-requested PDU session establishment procedure with a request type to transfer each of the PDN connections which the UE intends to transfer to TNGF or N3IWF connected to 5GCN, if any. The request type is set as follows: - if the PDN connection which the UE intends to transfer is a PDN connection for emergency bearer services, the request type is set to "existing emergency PDU session" to transfer the PDN connection for emergency bearer services; and - if the PDN connection which the UE intends to transfer is a non-emergency PDN connection, the request type is set to "existing PDU session" to transfer the non-emergency PDN connection. NOTE 3: If the UE has no active PDU session associated with non-3GPP access which the UE in N1 mode intends to transfer to EPS or no active PDN connection associated with 3GPP access which the UE in S1 mode intends to transfer to TNGF or N3IWF connected to 5GCN, the interworking between TNGF or N3IWF connected to 5GCN and E-UTRAN is not supported. See subclause 6.1.4.2 for coordination between 5GSM and ESM. | 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.8.2.3.2 |
6,026 | 4.9.3 Handover of a PDU Session procedure between 3GPP and trusted non-3GPP access 4.9.3.0 General | The handover of a PDU Session between 3GPP access and trusted non-3GPP access shall be supported as specified in clause 4.9.2 for all types of handover of a PDU Session between 3GPP access and untrusted non-3GPP access, with the following modifications and clarifications: - The untrusted non-3GPP access is substituted by a trusted non-3GPP access point (TNAP). - The N3IWF is substituted by the TNGF. - The registration via untrusted non-3GPP access is substituted by the registration via trusted non-3GPP access as specified in clause 4.12a.2.2. - A PDU Session is activated over trusted non-3GPP access as specified in clause 4.12a.5. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.9.3 |
6,027 | – CellDTXDRX-Config | The IE CellDTXDRX-Config is used to configure cell DTX/DRX related parameters. Cell DTX is configured only when C-DRX is configured. CellDTXDRX-Config information element -- ASN1START -- TAG-CELLDTXDRX-CONFIG-START CellDTXDRX-Config-r18 ::= SEQUENCE { cellDTXDRX-onDurationTimer-r18 CHOICE { subMilliSeconds INTEGER (1..31), milliSeconds ENUMERATED { ms1, ms2, ms3, ms4, ms5, ms6, ms8, ms10, ms20, ms30, ms40, ms50, ms60, ms80, ms100, ms200, ms300, ms400, ms500, ms600, ms800, ms1000, ms1200, ms1600, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1 } } OPTIONAL, -- Need M cellDTXDRX-CycleStartOffset-r18 CHOICE { ms10 INTEGER(0..9), ms20 INTEGER(0..19), ms32 INTEGER(0..31), ms40 INTEGER(0..39), ms60 INTEGER(0..59), ms64 INTEGER(0..63), ms70 INTEGER(0..69), ms80 INTEGER(0..79), ms128 INTEGER(0..127), ms160 INTEGER(0..159), ms256 INTEGER(0..255), ms320 INTEGER(0..319), ms512 INTEGER(0..511), ms640 INTEGER(0..639), ms1024 INTEGER(0..1023), ms1280 INTEGER(0..1279), ms2048 INTEGER(0..2047), ms2560 INTEGER(0..2559), ms5120 INTEGER(0..5119), ms10240 INTEGER(0..10239) } OPTIONAL, -- Need M cellDTXDRX-SlotOffset-r18 INTEGER (0..31) OPTIONAL, -- Need M cellDTXDRXconfigType-r18 ENUMERATED {dtx, drx, dtxdrx} OPTIONAL, -- Need M cellDTXDRXactivationStatus-r18 ENUMERATED {activated, deactivated} OPTIONAL -- Need N } -- TAG-CELLDTXDRX-CONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
6,028 | 5.3.5.15.3 L2 U2N or U2U Remote UE Addition/Modification | The L2 U2N Relay UE shall: 1> if no SRAP entity has been established: 2> establish a SRAP entity as specified in TS 38.351[ NR; Sidelink Relay Adaptation Protocol (SRAP) Specification ] [66]; 1> for each sl-L2IdentityRemote value included in the sl-RemoteUE-ToAddModList that is not part of the current UE configuration (L2 U2N Remote UE Addition): 2> configure the parameters to SRAP entity in accordance with the sl-SRAP-ConfigRelay; 2> if SRB1 is included in sl-MappingToAddModList, and sl-EgressRLC-ChannelPC5 is configured: 3> release SL-RLC1, if established; 3> associate the PC5 Relay RLC channel as indicated by sl-EgressRLC-ChannelPC5 with SRB1; 2> else: (i.e. SRB1 is not included in sl-MappingToAddModList, or SRB1 is included in sl-MappingToAddModList, but sl-EgressRLC-ChannelPC5 is not configured) 3> if SL-RLC1 is not established: 4> apply the default configuration of SL-RLC1 as specified in clause 9.2.4 and associate it with the SRB1; 1> for each sl-L2IdentityRemote value included in the sl-RemoteUE-ToAddModList that is part of the current UE configuration (L2 U2N Remote UE modification): 2> modify the configuration in accordance with the sl-SRAP-ConfigRelay; The L2 U2U Relay UE shall: 1> if no SRAP entity has been established: 2> establish a SRAP entity as specified in TS 38.351[ NR; Sidelink Relay Adaptation Protocol (SRAP) Specification ] [66]; 1> for each target L2 U2U Remote UE indicated in sl-L2IdentityRemote value included in the sl-U2U-RemoteUE-ToAddModList that is not part of the current UE configuration (target L2 U2U Remote UE Addition): 2> for each source L2 U2U Remote UE indicated in sl-SourceUE-Identity in accordance with one entry of the sl-SourceRemoteUE-ToAddModList, configure the parameters to SRAP entity in accordance with the sl-SRAP-ConfigU2U; 1> for each target L2 U2U Remote UE indicated in sl-L2IdentityRemote value included in the sl-U2U-RemoteUE-ToAddModList that is part of the current UE configuration (target L2 U2U Remote UE modification): 2> for each source L2 U2U Remote UE indicated in sl-SourceUE-Identity included in the sl-SourceRemoteUE-ToReleaseList (source L2 U2U Remote UE Release): 3> release the configuration associated with the source L2 U2U Remote UE; 2> for the source L2 U2U Remote UE indicated in sl-SourceUE-Identity included in the sl-SourceRemoteUE-ToAddModList that is not part of the current UE configuration (source L2 U2U Remote UE Addition): 3> configure the parameters to SRAP entity in accordance with the sl-SRAP-ConfigU2U; 2> for the source L2 U2U Remote UE indicated in sl-SourceUE-Identity included in the sl-SourceRemoteUE-ToAddModList that is part of the current UE configuration (source L2 U2U Remote UE modification): 3> modify the configuration in accordance with the sl-SRAP-ConfigU2U; | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.5.15.3 |
6,029 | 8.2.2.2.3 Minimum Requirement 2 Tx Antenna Port (demodulation subframe overlaps with aggressor cell ABS) | The requirements are specified in Table 8.2.2.2.3-2, with the addition of parameters in Table 8.2.2.2.3-1 and the downlink physical channel setup according to Annex C.3.2 and Annex C.3.3. The purpose is to verify the performance of transmit diversity (SFBC) with 2 transmit antennas if the PDSCH transmission in the serving cell takes place in subframes that overlap with ABS [9] of the aggressor cell. In Table 8.2.2.2.3-1, Cell 1 is the serving cell, and Cell 2 is the aggressor cell. The downlink physical channel setup for Cell 1 is according to Annex C.3.2 and for Cell 2 is according to Annex C.3.3, respectively. Table 8.2.2.2.3-1: Test Parameters for Transmit diversity Performance (FRC) Table 8.2.2.2.3-2: Minimum Performance Transmit Diversity (FRC) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.2.2.2.3 |
6,030 | 5.2.27.3.3 Ntsctsf_QoSandTSCAssistance_Update operation | Service operation name: Ntsctsf_QoSandTSCAssistance_Update Description: The consumer requests the network to update the QoS and/or additional Alternative QoS for an AF session or a UE or a group of UEs. Inputs, Required: Transaction Reference ID. Inputs, Optional: Flow description, QoS Reference or individual QoS parameters as described in clause 6.1.3.22 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20], sponsored data connectivity information if applicable, Alternative Service Requirements (containing one or more QoS Reference parameters or Requested Alternative QoS Parameter Set(s) in a prioritized order), QoS parameter(s) to be measured as defined in clause 5.45 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], Reporting frequency, Target of reporting as described in clause 6.1.3.21 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20], flow direction, Burst Arrival Time at UE (uplink) or UPF (downlink), Periodicity, Time domain, Survival Time, BAT Window or Capability for BAT adaptation, Periodicity Range. Outputs, Required: Result. Output (optional): None. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.27.3.3 |
6,031 | 8.45 Trace Reference | Trace Reference shall be coded as depicted in Figure 8.45-1. See 3GPP TS 32.422[ Telecommunication management; Subscriber and equipment trace; Trace control and configuration management ] [18], clause 5.6, for the definition of Trace Reference. See 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [5], clause 10.5.1.4, Mobile Identity, for the coding of MCC and MNC, whose values are obtained from the serving PLMN that the EM/NM is managing. If MNC is 2 digits long, bits 5 to 8 of octet 6 are coded as "1111". Figure 8.45-1: Trace Reference | 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.45 |
6,032 | 9.4.1.1 Old P-TMSI signature | The MS shall include this IE, if the MS holds a valid P-TMSI, P-TMSI signature and RAI, or if the TIN indicates "GUTI" and the MS holds a valid GUTI, or if the TIN is deleted and the MS holds a valid GUTI, but no valid P-TMSI and RAI. If the MS is configured for "AttachWithIMSI" as specified in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [135] or 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [112] and is attaching in a new PLMN which is neither the registered PLMN nor in the list of equivalent PLMNs, the MS shall not include this IE. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.4.1.1 |
6,033 | 6.3.1 Description | The 5G system will support 3GPP access technologies, including one or more NR and E-UTRA as well as non-3GPP access technologies. Interoperability among the various access technologies will be imperative. For optimization and resource efficiency, the 5G system will select the most appropriate 3GPP or non-3GPP access technology for a service, potentially allowing multiple access technologies to be used simultaneously for one or more services active on a UE. New technology such as satellite and wide area base stations will increase coverage and availability. This clause provides requirements for interworking with the various combinations of access technologies. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.3.1 |
6,034 | – SCS-SpecificCarrier | The IE SCS-SpecificCarrier provides parameters determining the location and width of the actual carrier or the carrier bandwidth. It is defined specifically for a numerology (subcarrier spacing (SCS)) and in relation (frequency offset) to Point A. SCS-SpecificCarrier information element -- ASN1START -- TAG-SCS-SPECIFICCARRIER-START SCS-SpecificCarrier ::= SEQUENCE { offsetToCarrier INTEGER (0..2199), subcarrierSpacing SubcarrierSpacing, carrierBandwidth INTEGER (1..maxNrofPhysicalResourceBlocks), ..., [[ txDirectCurrentLocation INTEGER (0..4095) OPTIONAL -- Need S ]] } -- TAG-SCS-SPECIFICCARRIER-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
6,035 | – RRCReconfigurationCompleteSidelink | The RRCReconfigurationCompleteSidelink message is used to confirm the successful completion of a PC5 RRC AS reconfiguration. It is only applied to unicast of NR sidelink communication. Signalling radio bearer: SL-SRB3 RLC-SAP: AM Logical channel: SCCH Direction: UE to UE RRCReconfigurationCompleteSidelink message -- ASN1START -- TAG-RRCRECONFIGURATIONCOMPLETESIDELINK-START RRCReconfigurationCompleteSidelink ::= SEQUENCE { rrc-TransactionIdentifier-r16 RRC-TransactionIdentifier, criticalExtensions CHOICE { rrcReconfigurationCompleteSidelink-r16 RRCReconfigurationCompleteSidelink-r16-IEs, criticalExtensionsFuture SEQUENCE {} } } RRCReconfigurationCompleteSidelink-r16-IEs ::= SEQUENCE { lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension RRCReconfigurationCompleteSidelink-v1710-IEs OPTIONAL } RRCReconfigurationCompleteSidelink-v1710-IEs ::= SEQUENCE { dummy ENUMERATED {true}, nonCriticalExtension RRCReconfigurationCompleteSidelink-v1720-IEs OPTIONAL } RRCReconfigurationCompleteSidelink-v1720-IEs ::= SEQUENCE { sl-DRX-ConfigReject-v1720 ENUMERATED {true} OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL } -- TAG-RRCRECONFIGURATIONCOMPLETESIDELINK-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
6,036 | 5.8.9.1a.2 Sidelink DRB addition/modification | 5.8.9.1a.2.1 Sidelink DRB addition/modification conditions For NR sidelink communication, a sidelink DRB addition is initiated only in the following cases: 1> if any sidelink QoS flow is (re)configured by sl-ConfigDedicatedNR, SIB12, SidelinkPreconfigNR and is to be mapped to one sidelink DRB, which is not established; or 1> if any sidelink QoS flow is (re)configured by RRCReconfigurationSidelink and is to be mapped to a sidelink DRB, which is not established; For NR sidelink communication, a sidelink DRB modification is initiated only in the following cases: 1> if any of the sidelink DRB related parameters is changed by sl-ConfigDedicatedNR, SIB12, SidelinkPreconfigNR or RRCReconfigurationSidelink for one sidelink DRB, which is established; 5.8.9.1a.2.2 Sidelink DRB addition/modification operations For the sidelink DRB, whose sidelink DRB addition conditions are met as in clause 5.8.9.1a.2.1, the UE capable of NR sidelink communication that is configured by upper layers to perform NR sidelink communication shall: 1> for groupcast and broadcast; or 1> for unicast, if the sidelink DRB addition was triggered due to the reception of the RRCReconfigurationSidelink message; or 1> for unicast, after receiving the RRCReconfigurationCompleteSidelink message, if the sidelink DRB addition was triggered due to the configuration received within the sl-ConfigDedicatedNR, SIB12, SidelinkPreconfigNR or indicated by upper layers: 2> if an SDAP entity for NR sidelink communication associated with the destination and the cast type of the sidelink DRB does not exist: 3> establish an SDAP entity for NR sidelink communication as specified in TS 37.324[ Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Service Data Adaptation Protocol (SDAP) specification ] [24] clause 5.1.1; 2> (re)configure the SDAP entity in accordance with the sl-SDAP-ConfigPC5 received in the RRCReconfigurationSidelink or sl-SDAP-Config received in sl-ConfigDedicatedNR, SIB12, SidelinkPreconfigNR, associated with the sidelink DRB; 2> establish a PDCP entity for NR sidelink communication and configure it in accordance with the sl-PDCP-ConfigPC5 received in the RRCReconfigurationSidelink or sl-PDCP-Config received in sl-ConfigDedicatedNR, SIB12, SidelinkPreconfigNR, associated with the sidelink DRB; 2> for a per-hop sidelink DRB (i.e. the UE is not acting as L2 U2U Remote UE): 3> establish a RLC entity for NR sidelink communication and configure it in accordance with the sl-RLC-ConfigPC5 received in the RRCReconfigurationSidelink or sl-RLC-Config received in sl-ConfigDedicatedNR, SIB12, SidelinkPreconfigNR, associated with sidelink DRB; 3> if this procedure was due to the reception of a RRCReconfigurationSidelink message: 4> configure the MAC entity with a logical channel in accordance with the sl-MAC-LogicalChannelConfigPC5 received in the RRCReconfigurationSidelink associated with the sidelink DRB, and perform the sidelink UE information procedure in clause 5.8.3 for unicast if need; 3> else if this procedure was due to the reception of a RRCReconfigurationCompleteSidelink message: 4> configure the MAC entity with a logical channel associated with the sidelink DRB, in accordance with the sl-MAC-LogicalChannelConfig received in the sl-ConfigDedicatedNR, SIB12, SidelinkPreconfigNR; 3> else (i.e. for groupcast/broadcast): 4> configure the MAC entity with a logical channel associated with the sidelink DRB, in accordance with the sl-MAC-LogicalChannelConfig received in the sl-ConfigDedicatedNR, SIB12, SidelinkPreconfigNR and assign a new LCID to this logical channel. 2> for an end-to-end sidelink DRB (i.e. the UE is acting as L2 U2U Remote UE): 3> if the UE is in RRC_CONNECTED: 4> associate this end-to-end sidelink DRB with the PC5 RLC channel indicated by sl-EgressRLC-ChannelPC5 included in sl-ConfigDedicatedNR, received from RRCReconfiguration; 3> else if the UE is in RRC_IDLE or RRC_INACTIVE: 4> associate this end-to-end sidelink DRB with the PC5 RLC channel derived by per-SLRB QoS profile of this end-to-end sidelink DRB based on the configuration in SIB12; 3> else if the UE is out of coverage: 4> associate this end-to-end sidelink DRB with the PC5 RLC channel derived by per-SLRB QoS profile of this end-to-end sidelink DRB based on the configuration in SidelinkPreconfigNR; NOTE 1: When a sidelink DRB addition is due to the configuration by RRCReconfigurationSidelink, it is up to UE implementation to select the sidelink DRB configuration as necessary transmitting parameters for the sidelink DRB, from the received sl-ConfigDedicatedNR (if in RRC_CONNECTED), SIB12 (if in RRC_IDLE/INACTIVE), SidelinkPreconfigNR (if out of coverage) with the same RLC mode as the one configured in RRCReconfigurationSidelink. For the sidelink DRB, whose sidelink DRB modification conditions are met as in clause 5.8.9.1a.2.1, the UE capable of NR sidelink communication that is configured by upper layers to perform NR sidelink communication shall: 1> for groupcast and broadcast; or 1> for unicast, if the sidelink DRB modification was triggered due to the reception of the RRCReconfigurationSidelink message; or 1> for unicast, after receiving the RRCReconfigurationCompleteSidelink message, if the sidelink DRB modification was triggered due to the configuration received within the sl-ConfigDedicatedNR, SIB12 or SidelinkPreconfigNR: 2> reconfigure the SDAP entity of the sidelink DRB, in accordance with the sl-SDAP-ConfigPC5 received in the RRCReconfigurationSidelink or sl-SDAP-Config received in sl-ConfigDedicatedNR, SIB12, SidelinkPreconfigNR, if included; 2> reconfigure the PDCP entity of the sidelink DRB, in accordance with the sl-PDCP-ConfigPC5 received in the RRCReconfigurationSidelink or sl-PDCP-Config received in sl-ConfigDedicatedNR, SIB12, SidelinkPreconfigNR, if included; 2> reconfigure the RLC entity of the sidelink DRB, in accordance with the sl-RLC-ConfigPC5 received in the RRCReconfigurationSidelink or sl-RLC-Config received in sl-ConfigDedicatedNR, SIB12, SidelinkPreconfigNR, if included; 2> reconfigure the logical channel of the sidelink DRB, in accordance with the sl-MAC-LogicalChannelConfigPC5 received in the RRCReconfigurationSidelink or sl-MAC-LogicalChannelConfig received in sl-ConfigDedicatedNR, SIB12, SidelinkPreconfigNR, if included. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.8.9.1a.2 |
6,037 | Annex E (informative): Comparison between call control procedures specified in 3GPP TS 24.008 and ITU-T Recommendation Q.931 | This annex summarizes a comparison of the procedures for call control as specified in ITU-T Recommendation Q.931 (blue book) and 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . If no comment is given, it means that the procedures specified in ITU-T Recommendation Q.931 and 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] are similar. However, it should be noted that even in such cases the procedures may be described in slightly different ways in the two documents. Table E.1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Circuit-switched call control procedures Table E.1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Circuit-switched call control procedures (continued) Table E.1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Circuit-switched call control procedures (continued) Table E.1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Circuit-switched call control procedures (continued) | 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 | Annex |
6,038 | – UEInformationResponseSidelink | The UEInformationResponseSidelink message is used to deliver UE information in sidelink, e.g. the split QoS information for L2 U2U Relay operation. Signalling radio bearer: SL-SRB3 RLC-SAP: AM Logical channel: SCCH Direction: L2 U2U Relay UE to L2 U2U Remote UE UEInformationResponseSidelink message -- ASN1START -- TAG-UEINFORMATIONRESPONSESIDELINK-START UEInformationResponseSidelink-r18 ::= SEQUENCE { rrc-TransactionIdentifier-r18 RRC-TransactionIdentifier, criticalExtensions CHOICE { ueInformationResponseSidelink-r18 UEInformationResponseSidelink-r18-IEs, criticalExtensionsFuture SEQUENCE {} } } UEInformationResponseSidelink-r18-IEs ::= SEQUENCE { sl-SplitQoS-ConnectionListPC5-r18 SEQUENCE (SIZE (1.. maxNrofSL-Dest-r16)) OF SL-SplitQoS-ConnectionPC5-r18 OPTIONAL, -- Need N lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL } SL-SplitQoS-ConnectionPC5-r18 ::= SEQUENCE { sl-DestinationIdentityRemoteUE-r18 SL-DestinationIdentity-r16, sl-SplitQoS-InfoList-r18 SEQUENCE (SIZE (1.. maxNrofSL-QFIsPerDest-r16)) OF SL-SplitQoS-Info-r18 } SL-SplitQoS-Info-r18 ::= SEQUENCE { sl-QoS-FlowIdentity-r18 SL-QoS-FlowIdentity-r16, sl-SplitPacketDelayBudget-r18 INTEGER (0..1023) OPTIONAL -- Need M } -- TAG-UEINFORMATIONRESPONSESIDELINK-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
6,039 | 4.7.3.1 Backhaul transport | The IAB-DU's IP traffic is routed over the wireless backhaul via the BAP sublayer. The BAP sublayer is specified in TS 38.340[ NR; Backhaul Adaptation Protocol (BAP) specification ] [31]. In downstream direction, upper layer packets are encapsulated by the BAP sublayer at the IAB-donor-DU and de-encapsulated at the destination IAB-node. In upstream direction, upper layer packets are encapsulated at the IAB-node and de-encapsulated at the IAB-donor-DU. IAB-specific transport between IAB-donor-CU and IAB-donor-DU is specified in TS 38.401[ NG-RAN; Architecture description ] [4]. On the BAP sublayer, packets are routed based on the BAP routing ID, which is carried in the BAP header. The BAP header is added to the packet when it arrives from upper layers, and the BAP header is stripped off when the packet has reached its destination node. The selection of the packet's BAP routing ID is configured by the IAB-donor-CU. The BAP routing ID consists of BAP address and BAP path ID, where the BAP address indicates the destination node of the packet on the BAP sublayer, and the BAP path ID indicates the routing path the packet should follow to this destination. For the purpose of routing, each IAB-node and IAB-donor-DU is further configured with a designated BAP address. On each hop of the packet's path, the IAB-node inspects the packet's BAP address in the BAP routing ID carried in the BAP header to determine if the packet has reached its destination, i.e., matches the IAB-node's BAP address. In case the packet has not reached the destination, the IAB-node determines the next hop backhaul link, referred to as egress link, based on the BAP routing ID carried in the BAP header and a routing configuration it received from the IAB-donor-CU. For each packet, the IAB-node further determines the egress BH RLC channel on the designated egress link. For packets arriving from upper layers, the designated egress BH RLC channel is configured by the IAB-donor-CU, and it is based on upper layer traffic specifiers. Since each BH RLC channel is configured with QoS information or priority level, BH-RLC-channel selection facilitates traffic-specific prioritization and QoS enforcement on the BH. For F1-U traffic, it is possible to map each GTP-U tunnel to a dedicated BH RLC channel or to aggregate multiple GTP-U tunnels into one common BH RLC channel. For traffic other than F1-U traffic, it is possible to map UE-associated F1AP messages, non-UE-associated F1AP messages and non-F1 traffic onto the same or separate BH RLC channels. When packets are routed from one BH link to another, the egress BH RLC channel on the egress BH link is determined based on the mapping configuration between ingress BH RLC channels and egress BH RLC channels provided by the IAB-donor-CU. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 4.7.3.1 |
6,040 | 5.2.6.28.6 Nnef_ASTI_UpdateNotify operation | Service operation name: Nnef_ASTI_UpdateNotify Description: Forward the notification for the 5G access stratum time distribution status change. When the NEF receives a notification of a change from the TSCTSF, it forwards the notification by invoking a Nnef_ASTI_UpdateNotify service operation to the NF consumer(s) that has subscribed for the event. Inputs, Required: As specified in clause 5.2.27.4.6. Inputs, Optional: As specified in clause 5.2.27.4.6. Outputs, Required: Operation execution result indication. Outputs, Optional: None. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.6.28.6 |
6,041 | 8.66 Fully Qualified Domain Name (FQDN) | Fully Qualified Domain Name (FQDN) is coded as depicted in Figure 8.66-1. Figure 8.66-1: Fully Qualified Domain Name (FQDN) The FQDN field encoding shall be identical to the encoding of a FQDN within a DNS message of clause 3.1 of IETF RFC 1035 [31] but excluding the trailing zero byte. NOTE 1: The FQDN field in the IE is not encoded as a dotted string as commonly used in DNS master zone files. A "PGW node name" IE in S3/S10/S16/S5/S8 GTP messages shall be a PGW host name as per clause 4.3.2 of 3GPP TS 29.303[ Domain Name System Procedures; Stage 3 ] [32] when the PGW FQDN IE is populated from 3GPP TS 29.303[ Domain Name System Procedures; Stage 3 ] [32] procedures. Specifically, the first DNS label is either "topon" or "topoff", and the canonical node name of the PGW starts at the third label. The same rules apply to "SGW node name" IE on S3/S10/S16 and "SGW-U node name" IE on S5. NOTE 2: The constraint of clause 4.3.2 of 3GPP TS 29.303[ Domain Name System Procedures; Stage 3 ] format is on populating the IE by 3GPP nodes for 3GPP nodes, the receiver shall not reject an IE that is otherwise correctly formatted since the IE might be populated for a non-3GPP node. An "MME node name" IE and an "SGSN node name" IE in S3 GTP messages indicate the associated ISR node when the ISR becomes active. | 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.66 |
6,042 | 10.7.2 MR-DC with 5GC | Inter-MN handover with/without MN initiated SN change is used to transfer UE context data from a source MN to a target MN while the UE context at the SN is kept or moved to another SN. During an Inter-Master Node handover, the target MN decides whether to keep or change the SN (or release the SN, as described in clause 10.8). Only intra-RAT Inter-Master node handover with/without SN change is supported (e.g. no transition from NGEN-DC to NR-DC). Figure 10.7.2-1: Inter-MN handover with/without MN initiated SN change procedure Figure 10.7.2-1 shows an example signalling flow for inter-MN handover with or without MN initiated SN change: NOTE 1: For an Inter-Master Node handover without Secondary Node change, the source SN and the target SN shown in Figure 10.7.2-1 are the same node. 1. The source MN starts the handover procedure by initiating the Xn Handover Preparation procedure including both MCG and SCG configuration. The source MN includes the source SN UE XnAP ID, SN ID and the UE context in the source SN in the Handover Request message. NOTE 2: The source MN may trigger the MN-initiated SN Modification procedure (to the source SN) to retrieve the current SCG configuration and SN-associated QMC configuration information and to allow provision of data forwarding related information before step 1. 2. If the target MN decides to keep the UE context in source SN, the target MN sends SN Addition Request to the SN including the SN UE XnAP ID as a reference to the UE context in the SN that was established by the source MN. If the target MN decides to change the SN allowing delta configuration, the target MN sends the SN Addition Request to the target SN including the UE context in the source SN that was established by the source MN. Otherwise, the target MN may send the SN Addition Request to the target SN including neither the SN UE XnAP ID nor the UE context in the source SN that was established by the source MN. 3. The (target) SN replies with SN Addition Request Acknowledge. The (target) SN may include the indication of the full or delta RRC configuration. NOTE 2a0: Void. 3a. For SN terminated bearers using MCG resources, the target MN provides Xn-U DL TNL address information in the Xn-U Address Indication message. 4. The target MN includes within the Handover Request Acknowledge message the MN RRC reconfiguration message to be sent to the UE in order to perform the handover, and may also provide forwarding addresses to the source MN. If PDU session split is performed in the target side during handover procedure, more than one data forwarding addresses corresponding to each node are included in the Handover Request Acknowledge message. The target MN indicates to the source MN that the UE context in the SN is kept if the target MN and the SN decided to keep the UE context in the SN in step 2 and step 3. 5a/5b. The source MN sends SN Release Request message to the (source) SN including a Cause indicating MCG mobility. The (source) SN acknowledges the release request. The source MN indicates to the (source) SN that the UE context in SN is kept, if it receives the indication from the target MN. If the indication as the UE context kept in SN is included, the SN keeps the UE context. 5c. The source MN sends XN-U Address Indication message to the (source) SN to transfer data forwarding information. More than one data forwarding addresses may be provided if the PDU session is split in the target side. 6. The source MN triggers the UE to perform handover and apply the new configuration. 7/8. The UE synchronizes to the target MN and replies with MN RRC reconfiguration complete message. 9. If configured with bearers requiring SCG radio resources, the UE synchronizes to the (target) SN. NOTE 2a1: The order the UE performs Random Access towards the MN (step 7) and performs the Random Access procedure towards the SN (step 9) is not defined. 10. If the RRC connection reconfiguration procedure was successful, the target MN informs the (target) SN via SN Reconfiguration Complete message. 11a. The source SN sends the Secondary RAT Data Usage Report message to the source MN and includes the data volumes delivered to and received from the UE over the NR/E-UTRA radio as described in clause 10.11.2. NOTE 2a2: The order the source SN sends the Secondary RAT Data Usage Report message and performs data forwarding with MN/target SN is not defined. The SN may send the report when the transmission of the related QoS is stopped. 11b. The source MN sends the Secondary RAT Report message to AMF to provide information on the used NR/E-UTRA resource. 12. For bearers using RLC AM, the source MN sends the SN Status Transfer message to the target MN, including, if needed, SN Status received from the source SN. The target forwards the SN Status to the target SN, if needed. 13. If applicable, data forwarding takes place from the source side. If the SN is kept, data forwarding may be omitted for SN terminated bearers or QoS flows kept in the SN. 14-17. The target MN initiates the Path Switch procedure. If the target MN includes multiple DL TEIDs for one PDU session in the Path Switch Request message, multiple UL TEID of the UPF for the PDU session should be included in the Path Switch Ack message in case there is TEID update in UPF. NOTE 3: If new UL TEIDs of the UPF for SN are included, the target MN performs MN initiated SN Modification procedure to provide them to the SN. 18. The target MN initiates the UE Context Release procedure towards the source MN. 19. Upon reception of the UE Context Release message from source MN, the (source) SN releases C-plane related resources associated to the UE context towards the source MN. Any ongoing data forwarding may continue. The SN shall not release the UE context associated with the target MN if the UE contest kept indication was included in the SN Release Request message in step 5. | 3GPP TS 37.340 | Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Overall Description; Stage-2 | RAN2 | 3GPP Series : 37 , Multiple radio access technology aspects | 10.7.2 |
6,043 | 8.10.1.2.3 Closed-loop spatial multiplexing Enhanced Performance Requirements Type A - Single-Layer Spatial Multiplexing 2 Tx Antenna Port with TM4 interference model (Cell-Specific Reference Symbols) | The requirements are specified in Table 8.10.1.2.3-2, with the addition of the parameters in Table 8.10.1.2.3-1 and the downlink physical channel setup according to Annex C.3.2. The purpose of these tests is to verify the closed loop rank-one performance with wideband precoding with two transmit antennas when the PDSCH transmission in the serving cell is interfered by PDSCH of one dominant interfering cell applying transmission mode 4 interference model defined in clause B.5.3. In Table 8.10.1.2.3-1, Cell 1 is the serving cell, and Cell 2 is the 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.10.1.2.3-1: Test Parameters for Single-Layer Spatial Multiplexing (FRC) with TM4 interference model and 4Rx Antenna Ports Table 8.10.1.2.3-2: Enhanced Performance Requirement Type A, Single-Layer Spatial Multiplexing (FRC) with TM4 interference model and 4Rx Antenna Ports | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.10.1.2.3 |
6,044 | 17.2.3 Fast Re-authentication NAI | The Fast Re-authentication NAI in both EAP-SIM and EAP-AKA shall take the form of an NAI as specified in clause 2.1 of IETF RFC 4282 [53]. The UE shall use the re-authentication identity received during the previous EAP-SIM or EAP-AKA authentication procedure. If such an NAI contains a realm part then the UE should not modify it, otherwise it shall use a home network realm as defined in clause 17.2.1. The result will therefore be an identity of the form: "<re-authentication_ID_username>@<re-authentication_ID_realm> for both EAP-SIM and EAP-AKA authentication when a realm is present in the re-authentication identity received during the previous EAP-SIM or EAP-AKA authentication procedure and "<re-authentication_ID_username>@gan.mnc<MNC>.mcc<MCC>.3gppnetwork.org", for both EAP-SIM and EAP-AKA authentication when a realm is not present in the re-authentication identity received during the previous EAP-SIM or EAP-AKA authentication procedure. EXAMPLE 1: If the re-authentication identity is "12345" and the IMSI is 234150999999999 (MCC = 234, MNC = 15), the Fast Re-authentication NAI takes the form [email protected] EXAMPLE 2: If the re-authentication identity is "[email protected]", the Fast Re-authentication NAI takes the form [email protected] | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 17.2.3 |
6,045 | 4.17.9 Delegated service discovery when NF service consumer and NF service producer are in same PLMN | Figure 4.17.9-1: Delegated NF service discovery when NF service consumer and NF service producer are in same PLMN 1. The NF service consumer intends to communicate with an NF service producer. The NF service consumer sends the service request to an SCP. The request may include discovery and selection parameters necessary to discover and select a NF service producer instance. The discovery and selection parameters are included in the request by the NF service consumer in a way that the SCP does not need to parse the request body. 2. The SCP may perform discovery upon the request either by interacting with an NRF using Nnrf_NFDiscovery service NRF or may use information collected during the previous interactions with an NRF (by the Nnrf_NFDiscovery service or Nnrf_NFManagement_NFStatusNotify service operation). The SCP together with the NRF authorizes the request. The SCP selects the target NF service producer. NOTE 1: If the discovery and selection parameters in the request include a UE identity, e.g. SUPI or IMPI/IMPU, the SCP can resolve the requested NF's Group ID corresponding to the UE identity and then invoke the Nnrf_NFDiscovery service, as defined in clause 6.3.1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. 3. If the NF service consumer is authorized to communicate with the NF service producer, the SCP forwards the request to the selected NF service producer according to the configuration of the Network Slice, e.g. the expected NF instances are only reachable by NFs in the same network slice. 4. The NF service producer sends a response to the SCP. If the request in step 3 creates a resource in the NF service producer, such as depicted in Figure 4.17.9-1, the NF service producer responds with resource information identifying the created resource. 5. The SCP routes the response to the NF service consumer. If the NF service consumer receives a resource address, it uses it for subsequent requests regarding the concerned resource. Otherwise, the procedure ends here. 6. On a subsequent operation on the created resource, the NF service consumer addresses the resource via the resource address returned by the NF service producer at step 4. 7. The SCP resolves the NF service producer address and selects a target NF service producer instance. The SCP then routes the request to the selected NF service producer instance. See the clause 6.3.1.0 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] for the details of selection of a target NF service producer instance by SCP. 8. The SCP delivers the request to the NF service producer. 9. The NF service producer sends a response to the SCP. The NF service producer may respond with an updated resource information different to the one received in the previous response. 10. The SCP sends a response to the NF service consumer. If the resource information was updated, the NF service consumer uses the received resource information for subsequent operations (requests) on the resource. NOTE 2: In the similar manner of handling the resource information, a binding indication may be also provided by the NF service producer and used for the subsequent requests of the NF service consumer. See more details in clause 4.17.12. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.17.9 |
6,046 | 4.6.2.3 Provision of NSSAI to lower layers in 5GMM-IDLE mode | The UE NAS layer may provide the lower layers with an NSSAI (either requested NSSAI or allowed NSSAI) when the UE in 5GMM-IDLE mode sends an initial NAS message. The AMF may indicate, via the NSSAI inclusion mode IE of a REGISTRATION ACCEPT message, an NSSAI inclusion mode in which the UE shall operate over the current access within the current PLMN or SNPN, if any (see subclauses 5.5.1.2.4 and 5.5.1.3.4), where the NSSAI inclusion mode is chosen among the following NSSAI inclusion modes described in table 4.6.2.3.1. Table 4.6.2.3.1: NSSAI inclusion modes and NSSAI which shall be provided to the lower layers The UE shall store the NSSAI inclusion mode: a) indicated by the AMF, if the AMF included the NSSAI inclusion mode IE in the REGISTRATION ACCEPT message; or b) if the AMF did not include the NSSAI inclusion mode IE in the REGISTRATION ACCEPT message: 1) if the UE is pre-configured by operator to operate by default to according to mode C in the HPLMN (see the DefaultNSSAIInclusionMode leaf of the NAS configuration MO in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [17] or the USIM file EFNASCONFIG in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [22]), then mode C; 2) otherwise: i) mode D for 3GPP access and trusted non-3GPP access; or ii) mode B for untrusted non-3GPP access and wireline access. together with the identity of the current PLMN or SNPN and access type in a non-volatile memory in the ME as specified in annex C. The UE shall apply the NSSAI inclusion mode received in the REGISTRATION ACCEPT message over the current access within the current PLMN and its equivalent PLMN(s), if any, or the current SNPN in the current registration area. When a UE performs a registration procedure to a PLMN which is not a PLMN in the current registration area or an SNPN, if the UE has no NSSAI inclusion mode for the PLMN or the SNPN stored in a non-volatile memory in the ME, the UE shall provide the lower layers with: a) no NSSAI if the UE is performing the registration procedure over 3GPP access; or b) requested NSSAI if the UE is performing the registration procedure over non-3GPP access. When a UE performs a registration procedure after an inter-system change from S1 mode to N1 mode, if the UE has no NSSAI inclusion mode for the PLMN stored in a non-volatile memory in the ME and the registration procedure is performed over 3GPP access, the UE shall not provide the lower layers with any NSSAI over the 3GPP access. | 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.6.2.3 |
6,047 | 16a.4.8 ASA Command | The Abort-Session-Answer (ASA) command, defined in IETF RFC 6733 (Diameter Base) [111], is indicated by the Command-Code set to 274 and the message flags’ ‘R’ bit clear, is sent in response to the ASR. The relevant AVPs that are of use for the Gi/Sgi interface are detailed in the ABNF description below. Other valid AVPs for this command are not used for Gi/Sgi purposes and should be ignored by the receiver or processed according to the relevant specifications. The bold marked AVPs in the message format indicate optional AVPs for Gi/Sgi or modified existing AVPs. Message Format: <ASA> ::= < Diameter Header: 274, PXY > < Session-Id > { Result-Code } { Origin-Host } { Origin-Realm } [ User-Name ] [ Origin-State-Id ] [ Experimental-Result ] [ Error-Message ] [ Error-Reporting-Host ] [ Failed-AVP ] * [ Redirected-Host ] [ Redirected-Host-Usage ] [ Redirect-Max-Cache-Time ] * [ Proxy-Info ] * [ AVP ] The Experimental-Result AVP contains an Experimental-Result-Code AVP and will signal to the Diameter server that the IP-CAN bearer (e.g. PDP context) has been succesfully terminated as requested. See subclause 16a.6 for the description of the Experimental-Result-Code AVP. | 3GPP TS 29.061 | Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) | CT WG3 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 16a.4.8 |
6,048 | 5.4.5.3 Network-initiated NAS transport procedure 5.4.5.3.1 General | The purpose of the network-initiated NAS transport procedure is to provide a transport of: a) a single 5GSM message; b) SMS; c) an LPP message; c1) an SLPP message; d) an SOR transparent container; e) a single uplink 5GSM message which was not forwarded due to routing failure; f) a single uplink 5GSM message which was not forwarded due to congestion control; g) a UE policy container; h) a single uplink 5GSM message which was not forwarded, because the PLMN's maximum number of PDU sessions has been reached; h1) a single uplink 5GSM message which was not forwarded, because the maximum number of PDU sessions with active user-plane resources has been reached; h2) a single uplink 5GSM message which was not forwarded, because of ongoing network slice-specific authentication and authorization procedure for the S-NSSAI that is requested; h3) a single uplink 5GSM message which was not forwarded, because the UE requested to establish an MA PDU session for LADN DNN; h4) a single uplink 5GSM message which was not forwarded, because the maximum number of UEs for a network slice has been reached; h5) a single uplink 5GSM message which was not forwarded because the UE is marked in the UE's 5GMM context that it is not allowed to request UAS services; h6) a single uplink 5GSM message was not forwarded, because the UE not supporting S-NSSAI location validity information requested forwarding of an 5GSM message with Request type IE is set to "initial request" when not in the NS-AoS of the related S-NSSAI; i) a single uplink 5GSM message which was not forwarded due to service area restrictions; i1) a single uplink 5GSM message which was not forwarded because the UE is registered to a PLMN via a satellite NG-RAN cell that is not allowed to operate at the present UE location; j) a UE parameters update transparent container; k) a location services message; l) a CIoT user data container; l1) a single uplink CIoT user data container or control plane user data which was not forwarded due to routing failure; l2) a single uplink CIoT user data container which was not forwarded due to congestion control; m) a service-level-AA container; m1) an event notification for upper layers; m2) a UPP-CMI container; m3) a single UPP-CMI container which was not forwarded due to user plane positioning not authorized; or n) multiple of the above types. from the AMF to the UE in a 5GMM message. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.4.5.3 |
6,049 | 9.3.23a Start CC $(CCBS)$ | A Network that does not support the "Network initiated MO call" option shall treat this message as a message with message type not defined for the PD. This message is sent by the mobile station to the network to open a Call Control transaction which the network has requested the mobile station to open. See Table 9.70b/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Message type: START CC Significance: local Direction: mobile station to network Table 9.70b/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : START CC message content | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.3.23a |
6,050 | 8.1.2.10 Applicability of performance requirements for Multi-user Superposed Transmission | For a UE which does not supports DMRS enhancement table (dmrs-Enhancements-r13 UE-EUTRA-Capability [7]), if corresponding tests specified in 8.3.1.1I Test 1, 8.3.2.1J Test 1 are tested, the test coverage can be considered fulfilled without executing other tests specified in 8.3.1.1I and 8.3.2.1J. For a UE which supports DMRS enhancement table (dmrs-Enhancements-r13 UE-EUTRA-Capability [7]) and enahcned performance Type D in TM8/9 or TM10 with assistance information for up to 1 interfering layer, if corresponding tests specified in 8.3.1.1I Test 2, 8.3.2.1J Test 2 are tested, the test coverage can be considered fulfilled without executing other tests specified in 8.3.1.1I and 8.3.2.1J. For a UE which supports DMRS enhancement table (dmrs-Enhancements-r13 UE-EUTRA-Capability [7]) and enahcned performance Type D in TM8/9 or TM10 with assistance information for up to 3 interfering layer, if corresponding tests specified in 8.3.1.1I Test 3, 8.3.2.1J Test 3 are tested, the test coverage can be considered fulfilled without executing other tests specified in 8.3.1.1I and 8.3.2.1J. | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.1.2.10 |
6,051 | 4.15.13 Assistance for Member UE selection 4.15.13.1 Member UE selection general information flow | This clause describes the procedures that are generally applicable independently of the Member UE filtering criteria sent by the AF. Figure 4.15.13.1-1: 5GC assistance to Member UE selection and update 1. AF subscribes the Member UE selection assistance information by sending a first Nnef_MemberUESelectionAssistance_subscribe request including a list of target member UEs, one or more member UE filtering criteria as listed in Table 4.15.13.2-1 and optionally, time window(s). Subsequently, the AF may only update the Member UE filtering criteria of the subscription as described in clause 4.15.13.0 by invoking Nnef_MemberUESelectionAssistance_subscribe and providing a Subscription Correlation ID, i.e. the AF does not provide the list of target member UEs again. NOTE: The time window(s) for selecting the candidate UE(s) is used by the NEF when subscribing/requesting to NWDAF. The NEF maps the time window(s) for selecting the candidate UE(s) to the Analytics target period, which should be included in the Nnwdaf_AnalyticsSubscription_Subscribe or Nnwdaf_AnalyticsInfo_Request service operations. 2a. [CONDITIONAL] If the AF request does not contain a Subscription Correlation ID, the NEF verifies the authorization of the AF Request and identifies which information needs to be collected for each UE in the list of target member UEs and executes the corresponding service operations based on the Member UE filtering criteria provided by the AF, e.g. events, analytics ID(s), notifications, etc. 2b. [CONDITIONAL] If the AF request contains a Subscription Correlation ID, the NEF correlates the Nnef_MemberUESelectionAssistance_Subscribe request to an existing subscription according to the Subscription Correlation ID. The NEF uses the list of target member UE(s) received in step 1 for the Member UE update using the updated filtering criteria. 3. NEF interacts with different 5GC network functions to collect the required information for each UE in the list of target member UEs. The set of interactions between the NEF and the 5GC NFs depend on the Member UE filtering criteria provided by the AF. See Table 4.15.13.2-1 for details. 4. Based on the collected information from other 5GC NFs, the NEF consolidates all the information to derive the list(s) of candidate UEs which fulfil the Member UE filtering criteria in the AF request. The NEF may derive recommended time window(s), considering the validity period(s) of the analytics used for Member UE selection criteria. The recommended time window(s) may be a subset of the time window(s) received from the AF. In different recommended time windows, the list of candidate UE(s) which fulfil the Member UE filtering criteria may be different. 5. NEF sends a Nnef_MemberUESelectionAssistance_Notify request to the AF including the list(s) of candidate UEs and possibly additional information. See clause 5.2.6.32.4 for details. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.15.13 |
6,052 | 5.4.3.5 Abnormal cases | The call control entity of the mobile station in the "disconnect request" state, shall upon expiry of timer T305: send a RELEASE message to the network with the cause number originally contained in the DISCONNECT message and optionally, a second cause information element with cause #102 "recovery on timer expiry", start timer T308, and enter the "release request" state. The call control entity of the network in the "release request" state, shall, at first expiry of timer T308, retransmit the RELEASE message, start timer T308, and stay in the "release request" state. At second expiry of timer T308, the call control entity of the network shall: release the MM connection; and return to the "null" state. | 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.4.3.5 |
6,053 | X.7 User consent requirements | The user consent requirements for enablers of network automation shall comply with Annex V of the present document and TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [105]. For scenarios where local regulations permit, for example vPLMN and hPLMN subject to the same regulatory requirements, the NWDAF shall be deemed to be the enforcement point and shall be subject to the requirement specified in Annex V. NOTE: Depending on the use case and the data source, the enforcement point could be the vNWDAF or the hNWDAF. This is however left to the involved PLMNs to determine. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | X.7 |
6,054 | 17.7.15 MBMS-Session-Repetition-Number AVP | The MBMS-Session-Repetition-Number AVP (AVP code 912) is of type OctetString with a length of one octet. It contains the session identity repetition number of the MBMS transmission session on the Gmb interface. The value 0 indicates the first transmission of a session. The values 1 to 255 represents the retransmission sequence number of a session. When the optional MBMS-Session-Identity AVP is included in the MBMS Session Start RAR (Start) command by the BM-SC, the BM-SC shall also provide the corresponding MBMS-Session-Repetition-Number AVP, and vice versa. | 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.7.15 |
6,055 | D.3.6 Gn/Gp SGSN to MME Tracking Area Update | The Gn/Gp SGSN to MME Tracking Area Update procedure is illustrated in Figure D.3.6-1. Any steps descriptions that are from TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [7] are shown as italic text and remain unmodified. In those step descriptions an MS stands for UE, new SGSN for new MME, old SGSN for old Gn/Gp SGSN, GGSN for P-GW, and HLR for HSS. The new MME behaves towards the old Gn/Gp SGSN always like a Gn/Gp 3G-SGSN, regardless of whether the old Gn/Gp SGSN is a 2G-SGSN or a 3G-SGSN. Figure D.3.6-1: Gn/Gp SGSN to MME Tracking Area Update procedure NOTE 1: For a PMIP-based S5/S8, procedure steps (A) are defined in TS 23.402[ Architecture enhancements for non-3GPP accesses ] [2]. Steps 13 and 15 concern GTP based S5/S8. 1. One of the triggers described in clause 5.3.3.0 for starting the TAU procedure occurs. 2. The UE sends to the eNodeB a Tracking Area Update Request (last visited TAI, P-TMSI Signature, old GUTI, UE Core Network Capability, Preferred Network behaviour, active flag, EPS bearer status, additional GUTI, eKSI, NAS sequence number, NAS-MAC, KSI) message together with RRC parameters indicating the Selected Network and the old GUMMEI. In the RRC connection establishment signalling associated with the TAU Request, the UE indicates its support of the CIoT EPS Optimisations relevant for MME selection. If the UE's TIN indicates "GUTI" or "RAT-related TMSI" and the UE holds a valid GUTI then the old GUTI indicates this valid GUTI. If the UE's TIN indicates "P-TMSI" and the UE holds a valid P-TMSI and related RAI then these two elements are indicated as the old GUTI. Mapping a P-TMSI and an RAI to a GUTI is specified in Annex H. If the UE holds a valid GUTI and the old GUTI indicates a GUTI mapped from a P-TMSI and RAI, then the UE indicates the native GUTI. If the old GUTI indicates a GUTI mapped from a P-TMSI and RAI, and the UE has a valid P-TMSI signature, the P-TMSI signature shall be included. The RRC parameter "old GUMMEI" takes its value from the identifier that is signalled as the old GUTI according to the rules above. For a combined MME/SGSN the eNodeB is configured to route the MME-code(s) of this combined node to the same combined node. This eNodeB is also configured to route MME-code(s) of GUTIs that are generated by the UE's mapping of the P-TMSIs allocated by the combined node. Such an eNodeB configuration may also be used for separate nodes to avoid changing nodes in the pool caused by inter RAT mobility. NOTE 2: In the scenario of this flow the UE's TIN indicates "P-TMSI" and therefore the UE indicates a P-TMSI as the old GUTI. The last visited TAI is included if the UE has any in order to help the MME to produce a good list of TAIs for any subsequent TAU Accept message. Selected Network indicates the network that is selected. Active flag is a request by UE to activate the radio and S1 bearers for all the active EPS Bearers by the TAU procedure. The EPS bearer status indicates each EPS bearer that is active within the UE. The UE's ISR capability is included in the UE Core Network Capability element. If the UE has valid EPS security parameters, the TAU Request message shall be integrity protected by the NAS-MAC in order to allow validation of the UE by the MME. eKSI, NAS sequence number and NAS-MAC are included if the UE has valid EPS security parameters. NAS sequence number indicates the sequential number of the NAS message. KSI is included if the UE indicates a GUTI mapped from a P-TMSI in the information element "old GUTI". If a UE includes a Preferred Network Behaviour, this defines the Network Behaviour the UE is expecting to be available in the network as defined in clause 4.3.5.10. 3. The eNodeB derives the MME address from the RRC parameters carrying the old GUMMEI, the indicated Selected Network and the RAT (NB-IoT or WB-E-UTRAN). If that GUMMEI is not associated with the eNodeB, or the GUMMEI is not available, the eNodeB selects the MME as described in clause 4.3.8.3 on "MME Selection Function". The eNodeB forwards the TAU Request message together with the TAI+ECGI and RAT type of the cell from where it received the message and with the Selected Network to the MME. The RAT type shall distinguish between NB-IoT and WB-E-UTRAN types. To assist Location Services, the eNodeB indicates the UE's Coverage Level to the MME. 4. The new MME sends SGSN Context Request (old RAI, P-TMSI, old P-TMSI Signature, New SGSN Address) to the old SGSN to get the MM and PDP contexts for the UE. The new MME shall support functionality for Intra Domain Connection of RAN Nodes to Multiple CN Nodes, i.e. the MME derives the old SGSN from the old RAI and the old P-TMSI (or TLLI). When the internal structure of the pool area where the MS roamed from is not known, the new MME derives the old SGSN from the old RAI as described at clause 5.8 in TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [7]. For this case, the new MME derives an SGSN that it believes is the old SGSN. This derived SGSN is itself the old SGSN, or it is associated with the same pool area as the actual old SGSN and it will determine the correct old SGSN from the P-TMSI (or TLLI) and relay the message to that actual old SGSN. 5. If the old SGSN is a 2G-SGSN: The old 2G-SGSN validates the old P-TMSI Signature and responds with an appropriate error cause if it does not match the value stored in the old 2G SGSN. This should initiate the security functions in the new SGSN. If the security functions authenticate the MS correctly, the new SGSN shall send an SGSN Context Request (old RAI, old PTMSI, MS Validated, New SGSN Address) message to the old SGSN. MS Validated indicates that the new SGSN has authenticated the MS. If the old P-TMSI Signature was valid or if the new SGSN indicates that it has authenticated the MS, the old SGSN stops assigning SNDCP N-PDU numbers to downlink N-PDUs received, and responds with SGSN Context Response (MM Context, PDP Contexts). If the MS is not known in the old SGSN, the old SGSN responds with an appropriate error cause. The old SGSN stores New SGSN Address, to allow the old SGSN to forward data packets to the new SGSN. Each PDP Context includes the SNDCP Send N-PDU Number for the next downlink N-PDU to be sent in acknowledged mode to the MS, the SNDCP Receive N-PDU Number for the next uplink N-PDU to be received in acknowledged mode from the MS, the GTP sequence number for the next downlink N-PDU to be sent to the MS and the GTP sequence number for the next uplink N-PDU to be tunnelled to the GGSN. The old SGSN starts a timer and stops the transmission of N-PDUs to the MS. The new SGSN shall ignore the MS Network Capability contained in MM Context of SGSN Context Response only when it has previously received an MS Network Capability in the Routing Area Request. If the old SGSN is a 3G-SGSN: The old 3G-SGSN validates the old P-TMSI Signature and responds with an appropriate error cause if it does not match the value stored in the old SGSN. This should initiate the security functions in the new SGSN. If the security functions authenticate the MS correctly, the new SGSN shall send an SGSN Context Request (IMSI, old RAI, MS Validated) message to the old 3G-SGSN. MS Validated indicates that the new SGSN has authenticated the MS. If the old P-TMSI Signature was valid or if the new SGSN indicates that it has authenticated the MS, the old SGSN starts a timer. If the MS is not known in the old SGSN, the old 3G-SGSN responds with an appropriate error cause. If the UE with emergency bearers is not authenticated in the old MME (in a network supporting unauthenticated UEs) the old MME continues the procedure with sending a Context Response and starting the timer also when it cannot validate the Context Request. The old 3G SGSN responds with an SGSN Context Response (MM Context, PDP Contexts) message. For each PDP context the old 3G SGSN shall include the GTP sequence number for the next uplink GTP PDU to be tunnelled to the GGSN and the next downlink GTP sequence number for the next PDU to be sent to the MS. Each PDP Context also includes the PDCP sequence numbers if PDCP sequence numbers are received from the old SRNS. The new 3G-SGSN shall ignore the MS Network Capability contained in MM Context of SGSN Context Response only when it has previously received an MS Network Capability in the Routing Area Request. The GTP sequence numbers received from the old 3G-SGSN are only relevant if delivery order is required for the PDP context (QoS profile). If the UE uses power saving functions and the DL Data Buffer Expiration Time for the UE has not expired, the old Gn/Gp-SGSN indicates Buffered DL Data Waiting. When this is indicated, the new MME invokes data forwarding and user plane setup corresponding to clause 5.3.3.1A. NOTE 3: In this step, the new "SGSN" shall be understood to be a new "MME" and the old SGSN stores new SGSN Address, to allow the old SGSN to forward data packets to the new "S-GW or eNodeB". This step describes both the 2G and 3G SGSN variants due to combining the 2G or 3G SGSN to MME TAU into a single procedure. NOTE 4: For the old SGSN, this step is unmodified compared to pre-Rel-8. The MME (called new SGSN in above description) must provide SGSN functionality which includes mapping PDP contexts to EPS bearer information. SNDCP, GTP and PDCP sequence numbers are not relevant for the MME as the network does not configure usage of "delivery order required", does not configure acknowledged mode NSAPIs (SNDCP) and does not configure loss less UTRAN PDCP as described in clause "compatibility issues". 6. Security functions may be executed. Procedures are defined in clause 5.3.10 on Security Function. If the SGSN Context Response message from the old SGSN did not include IMEISV, the MME shall retrieve the ME Identity (the IMEISV) from the UE. 7. If the new MME identifies that the RAT type has changed, the MME checks the subscription information to identify for each APN whether to maintain the PDN connection, disconnect the PDN connection with a reactivation request, or, disconnect the PDN connection without reactivation request. If the MME decides to deactivate a PDN connection it performs MME-initiated PDN Connection Deactivation procedure after the tracking area update procedure is completed but before the S1/RRC interface connection is released. Existing ESM cause values as specified in TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [46] (e.g. #39, "reactivation requested"; #66 "Requested APN not supported in current RAT and PLMN combination"; and for a dedicated bearer, possibly #37 "EPS QoS not accepted") are used to cause predictable UE behaviour. If all the PDN connections are disconnected and the UE does not support "attach without PDN connectivity", the MME shall request the UE to detach and reattach. The new MME sends an SGSN Context Acknowledge message to the old SGSN. This informs the old SGSN that the new SGSN is ready to receive data packets belonging to the activated PDP contexts. The old SGSN marks in its context that the MSC/VLR association and the information in the GGSNs and the HLR are invalid. This triggers the MSC/VLR, the GGSNs, and the HLR to be updated if the MS initiates a Routing area update procedure back to the old SGSN before completing the ongoing routing area update procedure. If the security functions do not authenticate the UE correctly, then the Tracking area update shall be rejected, and the new MME shall send a reject indication to the old SGSN. The old SGSN shall continue as if the SGSN Context Request was never received. NOTE 5: in the italic text of this step, new "SGSN" shall be understood as to be a new "MME". The MME needs to map PDP contexts received from Gn/Gp SGSN into EPS bearer information. The GGSN address(es) and TEIDs map to the PDN GW address(es) and TEIDs respectively. The MME maps PDP contexts to EPS bearers one-to-one and it translates the release 99 QoS parameters to the EPS bearer QoS parameters. NOTE 6: The SGSN operation is unmodified compared to pre-Rel-8. The MME indicates reserved TEID and IP address parameters from an S-GW to the old SGSN so that the old Gn/Gp SGSN can forward data packets when needed. The S-GW discards any packets received from old Gn/Gp SGSN. NOTE 7: The Gn signalling between the new MME and the old Gn/Gp SGSN has no capabilities to indicate ISR Supported or ISR Activated. If there is no PDP context at all and the CIoT EPS Optimisation without PDN connection is not applied, the MME rejects the TAU Request. For UE using CIoT EPS Optimisation without any activated PDN connection, the steps 9, 10, 11, 12 and 13 are skipped. 8. The old SGSN or the old RNC forward data to the S-GW and the S-GW discards these data. 9. The new MME adopts the bearer contexts received from the SGSN as the UE's EPS bearer contexts to be maintained by the new MME. The new MME maps the PDP contexts to the EPS bearers 1-to-1 and maps the Release 99 QoS parameter values of a PDP context to the EPS Bearer QoS parameter values of an EPS bearer as defined in Annex E. The MME establishes the EPS bearer(s) in the indicated order. The MME deactivates the EPS bearers which cannot be established. The MME verifies the EPS bearer status received from the UE with the bearer contexts received from the old SGSN and releases any network resources related to EPS bearers that are not active in the UE. If the UE has no PDP context, the MME rejects the TAU Request. The new MME selects a Serving GW and sends an Create Session Request (IMSI, MME Address and TEID, PDN GW address and TEID, EPS Bearer QoS, serving network identity, ME Identity, User Location Information IE, UE Time Zone IE, User CSG Information IE, RAT type, MS Info Change Reporting support indication, NRS (received from the SGSN)) message per PDN connection to the Serving GW. The MME shall send the serving network identity to the Serving GW. The new MME does not indicate ISR Activated. 10. The Serving GW creates contexts and informs the PDN GW(s) about the change of the RAT type. The Serving GW sends a Modify Bearer Request (Serving GW Address and TEID, RAT type, ME Identity, User Location Information IE, UE Time Zone IE, User CSG Information IE, MS Info Change Reporting support indication, PDN Charging Pause Support indication) message per PDN connection to the PDN GW(s) concerned. 11. If dynamic PCC is deployed, and RAT type information needs to be conveyed from the PDN GW to the PCRF, then the PDN GW shall send RAT type information to the PCRF by performing an IP-CAN Session Modification procedure as defined in TS 23.203[ Policy and charging control architecture ] [6]. NOTE 8: The PDN GW does not need to wait for the PCRF response, but continues in the next step. If the PCRF response leads to an EPS bearer modification the PDN GW should initiate a bearer update procedure. 12. The PDN GW updates its context field and returns a Modify Bearer Response (PDN GW address and TEID, MSISDN, Default bearer id, Charging Id, MS Info Change Reporting Action (Start) (if the PDN GW decides to receive UE's location information during the session), CSG Information Reporting Action (Start) (if the PDN GW decides to receive UE's User CSG information during the session), PDN Charging Pause Enabled indication (if PDN GW has chosen to enable the function), APN Restriction) message to the Serving GW. The MSISDN is included if the PDN GW has it stored in its UE context. When the UE moves from Gn/Gp SGSN to the MME, the PDN GW shall send the APN restriction of each bearer context to the Serving GW. 13. The Serving GW updates its context and returns an Create Session Response (Serving GW address and TEID for user plane, PDN GW address and TEID, Serving GW Address and TEID for the control plane, Default bearer id, APN restriction) message to the new MME. The message also includes MS Info Change Reporting Action (Start) and/or CSG Information Reporting Action (Start) if they are included in step 12. The Serving GW shall forward the received APN Restriction to the MME. When the MME receives the Create Session Response message, the MME checks if there is a "Availability after DDN Failure" monitoring event or a "UE Reachability" monitoring event configured for the UE in the MME and in such a case sends an event notification (see TS 23.682[ Architecture enhancements to facilitate communications with packet data networks and applications ] [74] for further information). 14. To ensure the release of all UE resources in the Gn/Gp SGSN the new MME informs the HSS of the change of the serving core network node by sending an Update Location Request (MME Address, IMSI, ME Identity, ULR-Flags, MME Capabilities, Homogenous Support of IMS Voice over PS Sessions) message to the HSS. The ME Identity is included if the SGSN Context Response did not contain the IMEISV. Because of interoperation with an Gn/Gp SGSN, which the new MME identifies from the GTPv1 Context Response signalling, the ULR-Flags indicates "Single-Registration-Indication". The MME capabilities indicate the MME's support for regional access restrictions functionality. For "Homogenous Support of IMS Voice over PS Sessions", see clause 4.3.5.8A. 15. If the MME changes, then the HSS cancels any old MME. The HSS sends a Cancel Location (IMSI, Cancellation type) message to the old MME, with a Cancellation Type set to Update Procedure. 16. The old MME removes the MM context. The old MME releases any local bearer resources and it deletes the EPS bearer resources by sending Delete Session Request (Cause, Operation Indication) messages to the Serving GW. The operation Indication flag is not set, that indicates that the S-GW shall not initiate a delete procedure towards the PDN GW. If ISR is activated then the cause indicates to the old S-GW that the old S-GW shall delete the bearer resources on the other old CN node by sending Delete Bearer Request message(s) to that CN node. The old MME acknowledges with a Cancel Location Ack (IMSI) message. 17. The HSS cancels any old SGSN node as the ULR-Flags indicates "Single-Registration-Indication". The HSS sends a Cancel Location (IMSI, Cancellation Type) message to the old SGSN. The old SGSN removes the contexts. If the timer started in step 5 is not running, the old SGSN removes the MM context. Otherwise, the contexts are removed when the timer expires. It also ensures that the MM context is kept in the old SGSN for the case the UE initiates another TAU procedure before completing the ongoing TAU procedure to the new MME. NOTE 9: In all other mobility scenarios a new CN node initiates only cancellation of an old CN node of the same type via HSS. In this scenario here (Gn/Gp SGSN to MME TAU) the new MME, by indicating single registration, initiates in addition the cancellation of the old Gn/Gp SGSN via HSS to make sure that any PDP contexts of the UE are properly released. MME and S4 SGSN release PDP/PDN contexts based on context transfer signalling. 18. On receipt of Cancel Location, if the MS is PMM CONNECTED in the old SGSN, the old SGSN sends an Iu Release Command message to the old SRNC. 19. When the data-forwarding timer has expired, the SRNS responds with an Iu Release Complete message. 20. The old SGSN acknowledges with a Cancel Location Ack (IMSI) message. 21. The new MME validates the UE's presence in the (new) TA. If all checks are successful, the MME constructs an MM context for the UE, the HLR acknowledges the Update Location by sending Update Location Ack (IMSI, Subscription Data) message to the new MME. If the Update Location is rejected by the HSS, the MME rejects the TAU Request from the UE with an appropriate cause sent in the TAU Reject message to the UE. 22. If due to regional subscription restrictions or access restrictions the UE is not allowed to access the TA: - For UEs with ongoing emergency bearer services, the new MME accepts the Tracking Area Update Request and releases the non-emergency bearers as specified in clause 5.10.3. - For all other cases, the new MME rejects Tracking Area Update Request with an appropriate cause to the UE and notifies the HSS of rejection (details of this notification is stage 3 detail). The new MME responds to the UE with a Tracking Area Update Accept (GUTI, TAI-list, EPS bearer status, NAS sequence number, NAS-MAC, ISR Activated, Supported Network Behaviour) message. Restriction list shall be sent to eNodeB as eNodeB handles the roaming restrictions and access restrictions in the Intra E-UTRAN case. If the "active flag" is set in the TAU Request message the user plane setup procedure can be activated in conjunction with the TAU Accept message. The procedure is described in detail in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [5]. The messages sequence should be the same as for the UE triggered Service Request procedure specified in clause 5.3.4.1 from the step when MME establishes the bearer(s). If the active flag is set the MME may provide the eNodeB with Handover Restriction List. Handover Restriction List is described in clause 4.3.5.7 "Mobility Restrictions". The EPS bearer status indicates the active bearers in the network. The UE removes any internal resources related to bearers not marked active in the received EPS bearer status. If the EPS bearer status information was in the TAU Request, the MME shall indicate the EPS bearer status to the UE. For UE using CIoT EPS Optimisation without any activated PDN connection, there is no EPS bearer status included in the TAU Accept message. The MME indicates the CIoT optimisations it supports and prefers in the Supported Network Behaviour information as defined in clause 4.3.5.10. When receiving the TAU Accept message and there is no ISR Activated indication the UE shall set its TIN to "GUTI". NOTE 10: In the case of interoperation with Gn/Gp SGSNs, ISR Activated is never indicated by the MME as the SGSN does not support ISR, which the new MME recognises from Gn interface signalling that does not support ISR indications. If the Subscription Data received from the HSS (during the TAU) contains information that is necessary for the E-UTRAN to be aware of (e.g. a restriction in the UE's permission to use NR as a secondary RAT, Unlicensed Spectrum in the form of LAA/LWA/LWIP/NR-U (as specified in clause 4.3.30) or a combination of them), or an existing UE context in the MME indicates that the UE is not permitted to use NR as a secondary RAT, Unlicensed Spectrum or a combination of them, then the MME sends an updated Handover Restriction List in the Downlink NAS Transport message that it sends to E-UTRAN. If the UE is not allowed to use NR as Secondary RAT, the MME indicates that to the UE in TAU Accept message. 23. If the GUTI was included in the TAU Accept message, the UE acknowledges the message by returning a Tracking Area Update Complete message to the MME. When the "Active flag" is not set in the TAU Request message and the Tracking Area Update was not initiated in ECM-CONNECTED state, the MME releases the signalling connection with UE, according to clause 5.3.5. NOTE 11: The new MME may initiate E-RAB establishment (see TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [36]) after execution of the security functions (step 5), or wait until completion of the TA update procedure. For the UE, E-RAB establishment may occur any time after the TA update request is sent (step 2). 24. The target MME calculates UE-AMBR as defined in clause 4.7.3. If the local UE-AMBR provided by the MME as defined in Annex E is different from the corresponding derived UE-AMBR, or the APN-AMBR mapped from the subscribed MBR is different from the subscribed APN-AMBR, or the mapped subscribed QoS profile (i.e. the subscribed QoS profile mapped according to Annex E) of the default bearer is different from the EPS Subscribed QoS profile received from the HSS, the new MME shall initiate Subscribed QoS Modification procedure as described in clause 5.4.2.2, Figure 5.4.2.2-1. In the case of a rejected tracking area update operation, due to regional subscription, roaming restrictions, or access restrictions (see TS 23.221[ Architectural requirements ] [27] and TS 23.008[ Organization of subscriber data ] [28]) the new MME should not construct a bearer context. In the case of receiving the subscriber data from HSS, the new MME may construct an MM context and store the subscriber data for the UE to optimise signalling between the MME and the HSS. A reject shall be returned to the UE with an appropriate cause and the S1 connection shall be released. Upon return to idle, the UE shall act according to TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [10]. If the new MME is unable to update the bearer context in one or more P-GWs, the new MME shall deactivate the corresponding bearer contexts as described in clause "MME Initiated Dedicated Bearer Deactivation Procedure". This shall not cause the MME to reject the tracking area update. The PDP Contexts shall be sent from old SGSN to new SGSN (MME) in a prioritized order, i.e. the most important PDP Context first in the SGSN Context Response message. (The prioritization method is implementation dependent, but should be based on the current activity). The new MME shall determine the Maximum APN restriction based on the received APN Restriction of each bearer context from the P-GW and then store the new Maximum APN restriction value. If there are active EPS GBR bearers with maximum bitrate set to 0, the MME should initiate MME Initiated Dedicated Bearer Deactivation (as specified in clause 5.4.4.2) to deactivate the related EPS bearer Context. If the new MME is unable to support the same number of active bearer contexts as received from old SGSN, the new MME should use the prioritisation sent by old SGSN as input when deciding which bearer contexts to maintain active and which ones to delete. In any case, the new MME shall first update all contexts in one or more P-GWs and then deactivate the context(s) that it cannot maintain as described in clause "MME Initiated Dedicated Bearer Deactivation Procedure". This shall not cause the MME to reject the tracking area update. NOTE 12: If MS (UE) was in PMM-CONNECTED state the PDP Contexts are sent already in the Forward Relocation Request message as described in clause "Serving RNS relocation procedures" of TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [7]. If the tracking area update procedure fails a maximum allowable number of times, or if the MME returns a Tracking Area Update Reject (Cause) message, the UE shall enter EMM DEREGISTERED state. If the Update Location Ack message indicates a reject, this should be indicated to the UE, and the UE shall not access non-PS services until a successful location update is performed. The CAMEL procedure calls shall be performed, see referenced procedures in TS 23.078[ Customised Applications for Mobile network Enhanced Logic (CAMEL) Phase 4; Stage 2 ] [29]: C1) CAMEL_GPRS_PDP_Context_Disconnection, CAMEL_GPRS_Detach and CAMEL_PS_Notification. They are called in the following order: - The CAMEL_GPRS_PDP_Context_Disconnection procedure is called several times: once per PDP context. The procedure returns as result "Continue". - Then the CAMEL_GPRS_Detach procedure is called once. The procedure returns as result "Continue". - Then the CAMEL_PS_Notification procedure is called once. The procedure returns as result "Continue". NOTE 13: This CAMEL handling is unmodified compared to pre-Rel-8. NOTE 14: CAMEL procedure calls C2 and C3 were omitted intentionally from this procedure since EPS does not support CAMEL procedure calls. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | D.3.6 |
6,056 | 5.6.1.5 Service request procedure not accepted by the network | If the service request cannot be accepted, the network shall return a SERVICE REJECT message to the UE including an appropriate 5GMM cause value. If the SERVICE REJECT message with 5GMM cause #76 or #78 was received without integrity protection, then the UE shall discard the message. If the AMF needs to initiate PDU session status synchronisation or a PDU session status IE was included in the SERVICE REQUEST message, the AMF shall include a PDU session status IE in the SERVICE REJECT message to indicate which PDU sessions associated with the access type the SERVICE REJECT message is sent over are active in the AMF. If the PDU session status IE is included in the SERVICE REJECT message and if the message is integrity protected, then: a) for single access PDU sessions, the UE shall perform a local release of all those PDU sessions which are not in 5GSM state PDU SESSION INACTIVE or PDU SESSION ACTIVE PENDING on the UE side associated with the access type the SERVICE REJECT message is sent over, but are indicated by the AMF as being in 5GSM state PDU SESSION INACTIVE. If a locally released PDU session is associated with one or more MBS sessions, the UE shall locally leave the associated MBS multicast sessions; and b) for MA PDU sessions, for all those PDU sessions which are not in 5GSM state PDU SESSION INACTIVE or PDU SESSION ACTIVE PENDING and have user plane resources established on the UE side associated with the access the SERVICE REJECT message is sent over, but are indicated by the AMF as no user plane resources established: 1) for MA PDU sessions having user plane resources established only on the access type the SERVICE REJECT message is sent over, the UE shall perform a local release of those MA PDU sessions. If a locally released PDU session is associated with one or more MBS sessions, the UE shall locally leave the associated MBS multicast sessions; and 2) for MA PDU sessions having user plane resources established on both accesses, the UE shall perform a local release on the user plane resources on the access type the SERVICE REJECT message is sent over. If a locally released PDU session is associated with one or more MBS sessions, the UE shall locally leave the associated MBS multicast sessions. If the service request for mobile originated services is rejected due to general NAS level mobility management congestion control, the network shall set the 5GMM cause value to #22 "congestion" and assign a value for back-off timer T3346. In NB-N1 mode, if the service request for mobile originated services is rejected due to operator determined barring (see 3GPP TS 29.503[ 5G System; Unified Data Management Services; Stage 3 ] [20AB]), the network shall set the 5GMM cause value to #22 "congestion" and assign a value for back-off timer T3346. If the service request from a UE supporting CAG is rejected due to CAG restrictions, the network shall set the 5GMM cause value to #76 "Not authorized for this CAG or authorized for CAG cells only" and should include the "CAG information list" in the CAG information list IE or the Extended CAG information list IE in the SERVICE REJECT message. NOTE 1: The network cannot be certain that "CAG information list" stored in the UE is updated as result of sending of the SERVICE REJECT message with the CAG information list IE or the Extended CAG information list IE, as the SERVICE REJECT message is not necessarily delivered to the UE (e.g., due to abnormal radio conditions). NOTE 2: The "CAG information list" can be provided by the AMF and include no entry if no "CAG information list" exists in the subscription. NOTE 2A: If the UE supports extended CAG information list, the CAG information list can be included either in the CAG information list IE or Extended CAG information list IE. NOTE 2B: It is unexpected for network to send REGISTRATION REJECT message to the UE with 5GMM cause value #76 in non-CAG cell and not indicate "Indication that the UE is only allowed to access 5GS via CAG cells" for the serving PLMN in the Extended CAG information list or the CAG information list. If the UE does not support extended CAG information list, the CAG information list shall not be included in the Extended CAG information list IE. If the service request from a UE not supporting CAG is rejected due to CAG restrictions, the network shall operate as described in bullet h) of subclause 5.6.1.8. Upon receipt of the CONTROL PLANE SERVICE REQUEST message with uplink data: - if the AMF decides to not forward the uplink data piggybacked in the CONTROL PLANE SERVICE REQUEST message; and - if the AMF decides to activate the congestion control for transport of user data via the control plane, then the AMF shall send a SERVICE REJECT message and set the 5GMM cause value to #22 "congestion" and assign a value for control plane data back-off timer T3448. If the AMF determines that the UE is in a non-allowed area or is not in an allowed area as specified in subclause 5.3.5, then: a) if the service type IE in the SERVICE REQUEST message is set to "signalling" or "data", the AMF shall send a SERVICE REJECT message with the 5GMM cause value set to #28 "Restricted service area"; b) otherwise, if the service type IE in the SERVICE REQUEST message is set to "mobile terminated services", "emergency services", "emergency services fallback", "high priority access" or "elevated signalling", the AMF shall continue the process as specified in subclause 5.6.1.4 unless for other reasons the service request cannot be accepted. If the service request for mobile originated services is rejected due to service gap control as specified in subclause 5.3.17, i.e. the T3447 timer is running in AMF, the network shall set the 5GMM cause value to #22 "Congestion" and may include T3346 value IE in the SERVICE REJECT message set to the remaining time of the running T3447 timer. Based on operator policy, if the service request procedure is rejected due to core network redirection for CIoT optimizations, the network shall set the 5GMM cause value to #31 "Redirection to EPC required". NOTE 3: The network can take into account the UE's S1 mode capability, the EPS CIoT network behaviour supported by the UE or the EPS CIoT network behaviour supported by the EPC to determine the rejection with the 5GMM cause value #31 "Redirection to EPC required". If the service request is via a satellite NG-RAN cell, and the network determines that the UE is in a location where the network is not allowed to operate, see 3GPP TS 23.502[ Procedures for the 5G System (5GS) ] [9], the network shall set the 5GMM cause value in the SERVICE REJECT message to #78 "PLMN not allowed to operate at the present UE location". If the service request from a UE supporting MINT is rejected due to a disaster condition no longer being applicable in the current location of the UE, the network shall set the 5GMM cause value to #11 "PLMN not allowed" or #13 "Roaming not allowed in this tracking area" and may include a disaster return wait range in the Disaster return wait range IE in the SERVICE REJECT message. On receipt of the SERVICE REJECT message, if the UE is in state 5GMM-SERVICE-REQUEST-INITIATED, the UE shall reset the service request attempt counter and stop timer T3517 if running. If the AMF received multiple 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, all of the received TAIs are forbidden, for roaming or for regional provision of service, the AMF shall include the TAI(s) in: a) the Forbidden TAI(s) for the list of "5GS forbidden tracking areas for roaming" IE; or b) the Forbidden TAI(s) for the list of "5GS forbidden tracking areas for regional provision of service" IE; or c) both; in the SERVICE REJECT message. Regardless of the 5GMM cause value received in the SERVICE REJECT message via satellite NG-RAN, - if the UE receives the Forbidden TAI(s) for the list of "5GS forbidden tracking areas for roaming" IE in the SERVICE REJECT 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"; and - if the UE receives the Forbidden TAI(s) for the list of "5GS forbidden tracking areas for regional provision of service" IE in the SERVICE REJECT 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". Furthermore, the UE shall take the following actions depending on the 5GMM cause value received in the SERVICE REJECT message. #3 (Illegal UE); #6 (Illegal ME); The UE shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2) and shall delete any 5G-GUTI, last visited registered TAI, TAI list and ngKSI. In case of PLMN, the UE shall consider the USIM as invalid for 5GS services until switching off, the UICC containing the USIM is removed or the timer T3245 expires as described in subclause 5.3.19A.1; In case of SNPN, if the UE is not registered for onboarding services in SNPN and the UE does not support access to an SNPN using credentials from a credentials holder and does not support equivalent SNPNs, the UE shall consider the selected entry of the "list of subscriber data" with the SNPN identity of the current SNPN as invalid until the UE is switched off, the entry is updated or the timer T3245 expires as described in subclause 5.3.19A.2. In case of SNPN, if the UE is not registered for onboarding services in SNPN and the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs, or both, the UE shall consider the selected entry of the "list of subscriber data" as invalid for 3GPP access until the UE is switched off, the entry is updated or the timer T3245 expires as described in subclause 5.3.19A.2. Additionally, if EAP based primary authentication and key agreement procedure using EAP-AKA' or 5G AKA based primary authentication and key agreement procedure was performed in the current SNPN, the UE shall consider the USIM as invalid for the current SNPN until switching off, the UICC containing the USIM is removed or the timer T3245 expires as described in subclause 5.3.19A.2. If the UE is not registered for onboarding services in SNPN, the UE shall delete the list of equivalent PLMNs (if any) or the list of equivalent SNPNs (if any), and shall enter the state 5GMM-DEREGISTERED.NO-SUPI. If the message has been successfully integrity checked by the NAS, then the UE shall: 1) set the counter for "SIM/USIM considered invalid for GPRS services" events and the counter for "USIM considered invalid for 5GS services over non-3GPP access" events to UE implementation-specific maximum value in case of PLMN if the UE maintains these counters; 2) set the counter for "the entry for the current SNPN considered invalid for 3GPP access" events and the counter for "the entry for the current SNPN considered invalid for non-3GPP access" events to UE implementation-specific maximum value in case of SNPN if the UE maintains these counters; and If the message was received via 3GPP access and the UE is operating in the single-registration mode, the UE shall handle the EMM parameters EMM state, EPS update status, 4G-GUTI, last visited registered TAI, TAI list and eKSI as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15] for the case when the service request procedure is rejected with the EMM cause with the same value. The USIM shall be considered as invalid also for non-EPS services until switching off, the UICC containing the USIM is removed or the timer T3245 expires as described in subclause 5.3.7a in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15]. If the message has been successfully integrity checked by the NAS and the UE maintains a counter for "SIM/USIM considered invalid for non-GPRS services", then the UE shall set this counter to UE implementation-specific maximum value. If the UE is registered for onboarding services in SNPN, the UE shall store the SNPN identity in the "permanently forbidden SNPNs" list for onboarding services, enter state 5GMM-DEREGISTERED.PLMN-SEARCH, and perform an SNPN selection or an SNPN selection for onboarding services according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]. If the message has been successfully integrity checked by the NAS, the UE shall set the SNPN-specific attempt counter to the UE implementation-specific maximum value. If the message has been successfully integrity checked by the NAS and the UE also supports the registration procedure over the other access, the UE shall in addition handle 5GMM parameters and 5GMM state for this access, as described for this 5GMM cause value. #7 (5GS services not allowed). The UE shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2) and shall delete any 5G-GUTI, last visited registered TAI, TAI list and ngKSI. In case of PLMN, the UE shall consider the USIM as invalid for 5GS services until switching off, the UICC containing the USIM is removed or the timer T3245 expires as described in subclause 5.3.19A.1; In case of SNPN, if the UE is not registered for onboarding services in SNPN and the UE does not support access to an SNPN using credentials from a credentials holder and does not support equivalent SNPNs, the UE shall consider the selected entry of the "list of subscriber data" with the SNPN identity of the current SNPN as invalid for 5GS services until the UE is switched off, the entry is updated or the timer T3245 expires as described in subclause 5.3.19A.2. In case of SNPN, if the UE is not registered for onboarding services in SNPN and the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs, or both, the UE shall consider the selected entry of the "list of subscriber data" as invalid for 3GPP access until the UE is switched off, the entry is updated or the timer T3245 expires as described in subclause 5.3.19A.2. Additionally, if EAP based primary authentication and key agreement procedure using EAP-AKA' or 5G AKA based primary authentication and key agreement procedure was performed in the current SNPN, the UE shall consider the USIM as invalid for the current SNPN until switching off, the UICC containing the USIM is removed or the timer T3245 expires as described in subclause 5.3.19A.2. If the UE is not registered for onboarding services in SNPN, the UE shall enter the state 5GMM-DEREGISTERED.NO-SUPI. If the message has been successfully integrity checked by the NAS, then the UE shall: 1) set the counter for "SIM/USIM considered invalid for GPRS services" events and the counter for "USIM considered invalid for 5GS services over non-3GPP access" events to UE implementation-specific maximum value in case of PLMN if the UE maintains these counters; or 2) set the counter for "the entry for the current SNPN considered invalid for 3GPP access" events and the counter for "the entry for the current SNPN considered invalid for non-3GPP access" events to UE implementation-specific maximum value in case of SNPN if the UE maintains these counters; and If the message was received via 3GPP access and the UE is operating in single-registration mode, the UE shall handle the EMM parameters EMM state, EPS update status, 4G-GUTI, last visited registered TAI, TAI list and eKSI as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15] for the case when the service request procedure is rejected with the EMM cause with the same value. If the UE is registered for onboarding services in SNPN, the UE shall store the SNPN identity in the "permanently forbidden SNPNs" list for onboarding services, enter state 5GMM-DEREGISTERED.PLMN-SEARCH, and perform an SNPN selection or an SNPN selection for onboarding services according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]. If the message has been successfully integrity checked by the NAS, the UE shall set the SNPN-specific attempt counter to the UE implementation-specific maximum value. If the message has been successfully integrity checked by the NAS and the UE also supports the registration procedure over the other access, the UE shall in addition handle 5GMM parameters and 5GMM state for this access, as described for this 5GMM cause value. NOTE 4: The possibility to configure a UE so that the radio transceiver for a specific radio access technology is not active, although it is implemented in the UE, is outside the scope of the present document. #9 (UE identity cannot be derived by the network). The UE shall set the 5GS update status to 5U2 NOT UPDATED (and shall store it according to subclause 5.1.3.2.2) and shall delete any 5G-GUTI, last visited registered TAI, TAI list and ngKSI. The UE shall enter the state 5GMM-DEREGISTERED. If the service request was initiated for emergency services fallback, the UE shall attempt to select an E-UTRA cell connected to EPC or 5GCN according to the domain priority and selection rules specified in 3GPP TS 23.167[ IP Multimedia Subsystem (IMS) emergency sessions ] [6]. If the UE finds a suitable E-UTRA cell, it then proceeds with the appropriate EMM or 5GMM procedures. If the UE operating in single-registration mode has changed to S1 mode, it shall disable the N1 mode capability for 3GPP access. If the service request was initiated for any reason other than emergency services fallback or initiating an emergency PDU session, the UE shall perform a new initial registration procedure. NOTE 5: User interaction is necessary in some cases when the UE cannot re-establish the PDU session(s) automatically. If the message was received via 3GPP access and the UE is operating in the single-registration mode, the UE shall handle the EMM parameters EMM state, EPS update status, 4G-GUTI, last visited registered TAI, TAI list and eKSI as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15] for the case when the service request procedure is rejected with the EMM cause with the same value. #10 (Implicitly de-registered). The UE shall enter the state 5GMM-DEREGISTERED.NORMAL-SERVICE. The UE shall delete any mapped 5G NAS security context or partial native 5G NAS security context. If the service request was initiated for emergency services fallback, the UE shall attempt to select an E-UTRA cell connected to EPC or 5GCN according to the domain priority and selection rules specified in 3GPP TS 23.167[ IP Multimedia Subsystem (IMS) emergency sessions ] [6]. If the UE finds a suitable E-UTRA cell, it then proceeds with the appropriate EMM or 5GMM procedures. If the UE operating in single-registration mode has changed to S1 mode, it shall disable the N1 mode capability for 3GPP access. If the rejected request was neither for initiating an emergency PDU session nor for emergency services fallback, the UE shall perform a new initial registration procedure. NOTE 6: User interaction is necessary in some cases when the UE cannot re-establish the PDU session(s) automatically. If the message was received via 3GPP access and the UE is operating in the single-registration mode, the UE shall handle the EMM state as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15] for the case when the service request procedure is rejected with the EMM cause with the same value. #11 (PLMN not allowed). This cause value received from a cell belonging to an SNPN is considered as an abnormal case and the behaviour of the UE is specified in subclause 5.6.1.7. The UE shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2) and shall delete any 5G-GUTI, last visited registered TAI, TAI list and ngKSI. The UE shall delete the list of equivalent PLMNs and store the PLMN identity in the forbidden PLMN list as specified in subclause 5.3.13A and if the UE is configured to use timer T3245 then the UE shall start timer T3245 and proceed as described in subclause 5.3.19A.1. For 3GPP access, the UE shall enter the state 5GMM-DEREGISTERED.PLMN-SEARCH and perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5], and for non-3GPP access the UE shall enter state 5GMM-DEREGISTERED.LIMITED-SERVICE and perform network selection as defined in 3GPP TS 24.502[ Access to the 3GPP 5G Core Network (5GCN) via non-3GPP access networks ] [18]. If the message has been successfully integrity checked by the NAS and the UE mantains the PLMN-specific attempt counter and the PLMN-specific attempt counter for non-3GPP access for that PLMN, the UE shall set the PLMN-specific attempt counter and the PLMN-specific attempt counter for non-3GPP access for that PLMN to the UE implementation-specific maximum value. If the message was received via 3GPP access and the UE is operating in single-registration mode, the UE shall in addition handle the EMM parameters EMM state, EPS update status, 4G-GUTI, last visited registered TAI, TAI list and eKSI as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15] for the case when the service request procedure is rejected with the EMM cause with the same value. If the message has been successfully integrity checked by the NAS and the UE also supports the registration procedure over the other access to the same PLMN, the UE shall in addition handle 5GMM parameters and 5GMM state for this access, as described for this 5GMM cause value. If the UE receives the Disaster return wait range IE in the SERVICE REJECT 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. #12 (Tracking area not allowed). The UE shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2) and shall delete last visited registered TAI and TAI list. If the UE is not registering or has not registered to the same PLMN over both 3GPP access and non-3GPP access, the UE shall additionally delete 5G-GUTI and ngKSI. If: 1) the UE is not operating in SNPN access operation mode, the UE shall store the current TAI in the list of "5GS forbidden tracking areas for regional provision of service" and enter the state 5GMM-DEREGISTERED.LIMITED-SERVICE. If the SERVICE REJECT message is not integrity protected, the UE shall memorize the current TAI was stored in the list of "5GS forbidden tracking areas for regional provision of service" for non-integrity protected NAS reject message; or 2) the UE is operating in SNPN access operation mode, the UE shall store the current TAI in the list of "5GS forbidden tracking areas for regional provision of service" for the current SNPN and the selected entry of the "list of subscriber data" or the selected PLMN subscription, and enter the state 5GMM-DEREGISTERED.LIMITED-SERVICE. If the SERVICE REJECT message is not integrity protected, the UE shall memorize the current TAI was stored in the list of "5GS forbidden tracking areas for regional provision of service" for the current SNPN and the selected entry of the "list of subscriber data" or the selected PLMN subscription, for non-integrity protected NAS reject message. If the message was received via 3GPP access and the UE is operating in single-registration mode, the UE shall handle the EMM parameters EMM state, EPS update status, 4G-GUTI, last visited registered TAI, TAI list and eKSI as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15] for the case when the service request procedure is rejected with the EMM cause with the same value. #13 (Roaming not allowed in this tracking area). The UE shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2). For 3GPP access the UE shall enter the state 5GMM-REGISTERED.PLMN-SEARCH, and for non-3GPP access the UE shall enter the state 5GMM-REGISTERED.LIMITED-SERVICE. If: 1) the UE is not operating in SNPN access operation mode, the UE shall store the current TAI in the list of "5GS forbidden tracking areas for roaming" and remove the current TAI from the stored TAI list if present. If the SERVICE REJECT message is not integrity protected, the UE shall memorize the current TAI was stored in the list of "5GS forbidden tracking areas for roaming" for non-integrity protected NAS reject message; or 2) the UE is operating in SNPN access operation mode, the UE shall store the current TAI in the list of "5GS forbidden tracking areas for roaming" for the current SNPN and the selected entry of the "list of subscriber data" or the selected PLMN subscription, and remove the current TAI from the stored TAI list if present. If the SERVICE REJECT message is not integrity protected, the UE shall memorize the current TAI was stored in the list of "5GS forbidden tracking areas for roaming" for the current SNPN and the selected entry of the "list of subscriber data" or the selected PLMN subscription, for non-integrity protected NAS reject message. For 3GPP access the UE shall perform a PLMN selection or SNPN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5], and for non-3GPP access the UE shall perform network selection as defined in 3GPP TS 24.502[ Access to the 3GPP 5G Core Network (5GCN) via non-3GPP access networks ] [18]. If the message was received via 3GPP access and the UE is operating in single-registration mode, the UE shall handle the EMM parameters EMM state and EPS update status as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15] for the case when the service request procedure is rejected with the EMM cause with the same value. If the UE receives the Disaster return wait range IE in the SERVICE REJECT 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. #15 (No suitable cells in tracking area). The UE shall enter the state 5GMM-REGISTERED.LIMITED-SERVICE. If: 1) the UE is not operating in SNPN access operation mode, the UE shall store the current TAI in the list of "5GS forbidden tracking areas for roaming" and remove the current TAI from the stored TAI list if present. If the SERVICE REJECT message is not integrity protected, the UE shall memorize the current TAI was stored in the list of "5GS forbidden tracking areas for roaming" for non-integrity protected NAS reject message; or 2) the UE is operating in SNPN access operation mode, the UE shall store the current TAI in the list of "5GS forbidden tracking areas for roaming" for the current SNPN and the selected entry of the "list of subscriber data" or the selected PLMN subscription, and remove the current TAI from the stored TAI list if present. If the SERVICE REJECT message is not integrity protected, the UE shall memorize the current TAI was stored in the list of "5GS forbidden tracking areas for roaming" for the current SNPN and the selected entry of the "list of subscriber data" or the selected PLMN subscription, for non-integrity protected NAS reject message. If the UE initiated service request for emergency services fallback, the UE shall attempt to select an E-UTRA cell connected to EPC or 5GC according to the emergency services support indicator (see 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [25A]). If the UE finds a suitable E-UTRA cell, it then proceeds with the appropriate EMM or 5GMM procedures. If the UE operating in single-registration mode has changed to S1 mode, it shall disable the N1 mode capability for 3GPP access. If the service request was not initiated for emergency services fallback, the UE shall search for a suitable cell in another tracking area 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]. If the message was received via 3GPP access and the UE is operating in the single-registration mode, the UE shall handle the EMM parameters EMM state and EPS update status as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15] for the case when the service request procedure is rejected with the EMM cause with the same value. If received over non-3GPP access the cause shall be considered as an abnormal case and the behaviour of the UE for this case is specified in subclause 5.6.1.7. #22 (Congestion). If the T3346 value IE is present in the SERVICE REJECT message and the value indicates that this timer is neither zero nor deactivated, the UE shall proceed as described below, otherwise it shall be considered as an abnormal case and the behaviour of the UE for this case is specified in subclause 5.6.1.7. If the rejected request was not for initiating an emergency PDU session, the UE shall abort the service request procedure and enter state 5GMM-REGISTERED and stop timer T3517 if still running. The UE shall stop timer T3346 if it is running. If the SERVICE REJECT message is integrity protected, the UE shall start timer T3346 with the value provided in the T3346 value IE. If the SERVICE REJECT message is not integrity protected, the UE shall start timer T3346 with a random value from the default range specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [12]. For all other cases the UE stays in the current serving cell and applies normal cell reselection process. The service request procedure is started, if still necessary, when timer T3346 expires or is stopped. If the message was received via 3GPP access and the UE is operating in the single-registration mode, the UE shall handle the EMM parameters EMM state and EPS update status as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15] for the case when the service request procedure is rejected with the EMM cause with the same value. If the service request procedure was initiated for an MO MMTEL voice call (i.e. access category 4), or for an MO MMTEL video call (i.e. access category 5) or for an MO IMS registration related signalling (i.e. access category 9), a notification that the service request was not accepted due to congestion shall be provided to the upper layers. If the UE is using 5GS services with control plane CIoT 5GS optimization and if the T3448 value IE is present in the SERVICE REJECT message and the value indicates that this timer is neither zero nor deactivated, the UE shall: a) stop timer T3448 if it is running; b) consider the transport of user data via the control plane as unsuccessful; and c) start timer T3448: 1) with the value provided in the T3448 value IE if the SERVICE REJECT message is integrity protected; or 2) with a random value from the default range specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15] table 10.2.1 if the SERVICE REJECT message is not integrity protected. If the UE is using 5GS services with control plane CIoT 5GS optimization, the T3448 value IE is present in the SERVICE REJECT message and the value indicates that this timer is either zero or deactivated, the UE shall ignore the T3448 value IE and: a) stop timer T3448 if it is running; and b) consider the transport of user data via the control plane as unsuccessful. If the UE is using 5GS services with control plane CIoT 5GS optimization and if the T3448 value IE is not present in the SERVICE REJECT message, it shall be considered as an abnormal case and the behaviour of UE for this case is specified in subclause 5.6.1.7. #27 (N1 mode not allowed). The UE shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2) and shall enter the state 5GMM-REGISTERED.LIMITED-SERVICE. If the message has been successfully integrity checked by the NAS, the UE shall set: 1) the PLMN-specific N1 mode attempt counter for 3GPP access and the PLMN-specific N1 mode attempt counter for non-3GPP access for that PLMN in case of PLMN; or 2) the SNPN-specific attempt counter for 3GPP access for the current SNPN and the SNPN-specific attempt counter for non-3GPP access for the current SNPN in case of SNPN to the UE implementation-specific maximum value. The UE shall disable the N1 mode capability for the specific access type for which the message was received (see subclause 4.9). If the message has been successfully integrity checked by the NAS, the UE shall disable the N1 mode capability also for the other access type (see subclause 4.9). If the message was received via 3GPP access and the UE is operating in single-registration mode, the UE shall in addition set the EPS update status to EU3 ROAMING NOT ALLOWED and enter the state EMM-REGISTERED. #28 (Restricted service area). The UE shall enter the state 5GMM-REGISTERED.NON-ALLOWED-SERVICE, wait for the release of the N1 NAS signalling connection and perform the registration procedure for mobility and periodic registration update if the service type IE in the SERVICE REQUEST message was not set to "elevated signalling" and the SERVICE REJECT message is received over 3GPP access (see subclause 5.3.5 and 5.5.1.3). If the service type IE in the SERVICE REQUEST message was set to "elevated signalling", the UE shall not re-initiate service request procedure until the UE enters an allowed area or leaves a non-allowed area, except for emergency services, high priority access or responding to paging or notification. #31 (Redirection to EPC required). 5GMM cause #31 received by a UE that has not indicated support for CIoT optimizations or received by a UE over non-3GPP access is considered an abnormal case and the behaviour of the UE is specified in subclause 5.6.1.7. This cause value received from a cell belonging to an SNPN is considered as an abnormal case and the behaviour of the UE is specified in subclause 5.6.1.7. The UE shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2). The UE shall reset the service request attempt counter and enter the state 5GMM-REGISTERED.LIMITED-SERVICE. The UE shall enable the E-UTRA capability if it was disabled and disable the N1 mode capability for 3GPP access (see subclause 4.9.2). If the message was received via 3GPP access and the UE is operating in single-registration mode, the UE shall handle the EMM parameters, EMM state, and EPS update status as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15] for the case when the service request procedure is rejected with the EMM cause with the same value. #36 (IAB-node operation not authorized). This cause value is only applicable when received over 3GPP access by a UE operating as an IAB-node. This cause value received from a 5G access network other than 3GPP access or received by a UE not operating as an IAB-node is considered as an abnormal case and the behaviour of the UE is specified in subclause 5.6.1.7. The UE shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2) and shall delete any 5G-GUTI, last visited registered TAI, TAI list and ngKSI. If: 1) the UE is not operating in SNPN access operation mode, i) the UE shall delete the list of equivalent PLMNs and store the PLMN identity in the forbidden PLMN list as specified in subclause 5.3.13A and if the UE is configured to use timer T3245 then the UE shall start timer T3245 and proceed as described in subclause 5.3.19a.1. The UE shall enter the state 5GMM-DEREGISTERED.PLMN-SEARCH and perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]. If the message has been successfully integrity checked by the NAS and the UE maintains the PLMN-specific attempt counter for 3GPP access for that PLMN, the UE shall set the PLMN-specific attempt counter for 3GPP access for that PLMN to the UE implementation-specific maximum value; and ii) If the UE is operating in single-registration mode, the UE shall in addition handle the EMM parameters EMM state, EPS update status, 4G-GUTI, last visited registered TAI, TAI list and eKSI as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15] for the case when the service request procedure is rejected with the EMM cause with the same value; or 2) the UE is operating in SNPN access operation mode, i) the UE shall delete the list of equivalent SNPNs (if available). The UE shall store the SNPN identity in the "temporarily forbidden SNPNs" list for 3GPP access 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. The UE shall enter state 5GMM-DEREGISTERED.PLMN-SEARCH and perform an SNPN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]. If the message has been successfully integrity checked by the NAS, the UE shall set the SNPN-specific attempt counter for 3GPP access for the current SNPN to the UE implementation-specific maximum value. #72 (Non-3GPP access to 5GCN not allowed). If the UE initiated the service request procedure over non-3GPP access, the UE shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2) and shall delete last visited registered TAI and TAI list. If the UE is not registering or has not registered to the same PLMN over both 3GPP access and non-3GPP access, the UE shall additionally delete 5G-GUTI and ngKSI. Additionally, the UE shall enter the state 5GMM-DEREGISTERED for non-3GPP access. If the message has been successfully integrity checked by the NAS, the UE shall set: 1) the PLMN-specific N1 mode attempt counter for non-3GPP access for that PLMN in case of PLMN; or 2) the SNPN-specific attempt counter for non-3GPP access for that SNPN in case of SNPN; to the UE implementation-specific maximum value. NOTE 7: The 5GMM sublayer states, the 5GMM parameters and the registration status are managed per access type independently, i.e. 3GPP access or non-3GPP access (see subclauses 4.7.2 and 5.1.3). The UE shall disable the N1 mode capability for non-3GPP access (see subclause 4.9.3). As an implementation option, if the UE is not currently registered over 3GPP access, the UE may enter the state 5GMM-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 ] [5]. If received over 3GPP access the cause shall be considered as an abnormal case and the behaviour of the UE for this case is specified in subclause 5.6.1.7. #73 (Serving network not authorized). This cause value received from a cell belonging to an SNPN is considered as an abnormal case and the behaviour of the UE is specified in subclause 5.6.1.7. The UE shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2) and shall delete any 5G-GUTI, last visited registered TAI, TAI list and ngKSI. The UE shall delete the list of equivalent PLMNs, store the PLMN identity in the forbidden PLMN list as specified in subclause 5.3.13A. For 3GPP access the UE shall enter state 5GMM-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 ] [5], and for non-3GPP access the UE shall enter state 5GMM-DEREGISTERED.LIMITED-SERVICE in order to perform network selection as defined in 3GPP TS 24.502[ Access to the 3GPP 5G Core Network (5GCN) via non-3GPP access networks ] [18]. If the message has been successfully integrity checked by the NAS, the UE shall set the PLMN-specific attempt counter and the PLMN-specific attempt counter for non-3GPP access for that PLMN to the UE implementation-specific maximum value. If the message was received via 3GPP access and the UE is operating in single-registration mode, the UE shall in addition set the EPS update status to EU3 ROAMING NOT ALLOWED, enter the state EMM-DEREGISTERED and shall delete any 4G-GUTI, last visited registered TAI, TAI list and eKSI. #74 (Temporarily not authorized for this SNPN). 5GMM cause #74 is only applicable when received from a cell belonging to an SNPN. 5GMM cause #74 received from a cell not belonging to an SNPN is considered as an abnormal case and the behaviour of the UE is specified in subclause 5.6.1.7. The UE shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2) and shall delete any 5G-GUTI, last visited registered TAI, TAI list, ngKSI and the list of equivalent SNPNs (if available). The UE shall store the SNPN identity in the "temporarily forbidden SNPNs" list for the specific access type for which the message was received and the selected entry of the "list of subscriber data" or the selected PLMN subscription. If the UE supports access to an SNPN using credentials from a credentials holder, the UE shall store the SNPN identity in the "temporarily forbidden SNPNs" list along with the GIN(s) broadcasted by the SNPN if any, for the selected entry of the "list of subscriber data" or the selected PLMN subscription. If the UE supports access to an SNPN providing access for localized services in SNPN and the access for localized services in SNPN has been enabled, the UE shall store the SNPN identity in the list of "temporarily forbidden SNPNs for access for localized services in SNPN" (if the SNPN was selected according to subclause 4.9.3.1.1 bullet a0) of 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]) along with the GIN(s) broadcasted by the SNPN if any, for the selected entry of the "list of subscriber data" or the selected PLMN subscription. If the UE is not registered for onboarding services in SNPN, the UE shall enter state 5GMM-DEREGISTERED.PLMN-SEARCH and perform an SNPN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]. If the UE is registered for onboarding services in SNPN, the UE shall enter state 5GMM-DEREGISTERED.PLMN-SEARCH and perform an SNPN selection or an SNPN selection for onboarding services according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]. If the message has been successfully integrity checked by the NAS, the UE shall set the SNPN-specific attempt counter for 3GPP access and the SNPN-specific attempt counter for non-3GPP access for the current SNPN to the UE implementation-specific maximum value. If the message has been successfully integrity checked by the NAS and the UE also supports the registration procedure over the other access to the same SNPN, the UE shall in addition handle 5GMM parameters and 5GMM state for this access, as described for this 5GMM cause value. #75 (Permanently not authorized for this SNPN). 5GMM cause #75 is only applicable when received from a cell belonging to an SNPN with a globally-unique SNPN identity. 5GMM cause #75 received from a cell not belonging to an SNPN or a cell belonging to an SNPN with a non-globally-unique SNPN identity is considered as an abnormal case and the behaviour of the UE is specified in subclause 5.6.1.7. The UE shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2) and shall delete any 5G-GUTI, last visited registered TAI, TAI list, ngKSI and the list of equivalent SNPNs (if available). The UE shall store the SNPN identity in the "permanently forbidden SNPNs" list for the specific access type for which the message was received and the selected entry of the "list of subscriber data" or the selected PLMN subscription. If the UE is not registered for onboarding services in SNPN, the UE shall enter state 5GMM-DEREGISTERED.PLMN-SEARCH and perform an SNPN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]. If the UE supports access to an SNPN using credentials from a credentials holder, the UE shall store the SNPN identity in the "permanently forbidden SNPNs" list along with the GIN(s) broadcasted by the SNPN if any, for the selected entry of the "list of subscriber data" or the selected PLMN subscription. If the UE supports access to an SNPN providing access for localized services in SNPN and the access for localized services in SNPN has been enabled, the UE shall store the SNPN identity in the list of "permanently forbidden SNPNs for access for localized services in SNPN" (if the SNPN was selected according to subclause 4.9.3.1.1 bullet a0) of 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]) along with the GIN(s) broadcasted by the SNPN if any, for the selected entry of the "list of subscriber data" or the selected PLMN subscription. If the UE is registered for onboarding services in SNPN, the UE shall enter state 5GMM-DEREGISTERED.PLMN-SEARCH and perform an SNPN selection or an SNPN selection for onboarding services according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]. If the message has been successfully integrity checked by the NAS, the UE shall set the SNPN-specific attempt counter for 3GPP access and the SNPN-specific attempt counter for non-3GPP access for the current SNPN to the UE implementation-specific maximum value. If the message has been successfully integrity checked by the NAS and the UE also supports the registration procedure over the other access to the same SNPN, the UE shall in addition handle 5GMM parameters and 5GMM state for this access, as described for this 5GMM cause value. #76 (Not authorized for this CAG or authorized for CAG cells only). This cause value received via non-3GPP access or from a cell belonging to an SNPN is considered as an abnormal case and the behaviour of the UE is specified in subclause 5.6.1.7. The UE shall set the 5GS update status to 5U3.ROAMING NOT ALLOWED, store the 5GS update status according to subclause 5.1.3.2.2. If 5GMM cause #76 is received from: 1) a CAG cell, and if the UE receives a "CAG information list" in the CAG information list IE or the Extended CAG information list IE included in the SERVICE REJECT message, the UE shall: i) replace the "CAG information list" stored in the UE with the received "CAG information list" when received in the HPLMN or EHPLMN; ii) 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 8: 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. iii) 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. Otherwise, the UE shall delete the CAG-ID(s) of the cell from the "allowed CAG list" for the current PLMN, if the CAG-ID(s) are authorized based on the "Allowed CAG list". In the case the "allowed CAG list" for the current PLMN only contains a range of CAG-IDs, how the UE deletes the CAG-ID(s) of the cell from the "allowed CAG list" for the current PLMN is up to UE implementation. In addition: i) if the entry in the "CAG information list" for the current PLMN does not include an "indication that the UE is only allowed to access 5GS via CAG cells" or if the entry in the "CAG information list" for the current PLMN includes an "indication that the UE is only allowed to access 5GS via CAG cells" and one or more CAG-ID(s) are authorized based on the updated "allowed CAG list" for the current PLMN, 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"; ii) if the entry in the "CAG information list" for the current PLMN includes an "indication that the UE is only allowed to access 5GS via CAG cells" and no CAG-ID is authorized based on the updated "allowed CAG list" for the current PLMN, 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 iii) if the "CAG information list" does not include an entry for the current PLMN, 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". 2) a non-CAG cell, and if the UE receives a "CAG information list" in the CAG information list IE or the Extended CAG information list IE included in the SERVICE REJECT message, the UE shall: i) replace the "CAG information list" stored in the UE with the received "CAG information list" when received in the HPLMN or EHPLMN; ii) 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 9: 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. iii) 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. Otherwise, the UE shall store an "indication that the UE is only allowed to access 5GS via CAG cells" in the entry of the "CAG information list" for the current PLMN, if any. If the "CAG information list" stored in the UE does not include the current PLMN's entry, the UE shall add an entry for the current PLMN to the "CAG information list" and store an "indication that the UE is only allowed to access 5GS via CAG cells" in the entry of the "CAG information list" for the current PLMN. If the UE does not have a stored "CAG information list", the UE shall create a new "CAG information list" and add an entry with an "indication that the UE is only allowed to access 5GS via CAG cells" for the current PLMN. In addition: i) if one or more CAG-ID(s) are authorized based on the "allowed CAG list" for the current PLMN, 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] with the updated CAG information; or ii) if no CAG-ID is authorized based on the "allowed CAG list" for the current PLMN, 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 message was received via 3GPP access and the UE is operating in single-registration mode, the UE shall in addition set the EPS update status to EU3 ROAMING NOT ALLOWED, reset the service request attempt counter and enter the state EMM-REGISTERED. #77 (Wireline access area not allowed). 5GMM cause #77 is only applicable when received from a wireline access network by the 5G-RG or the W-AGF acting on behalf of the FN-CRG (or on behalf of the N5GC device). 5GMM cause #77 received from a 5G access network other than a wireline access network and 5GMM cause #77 received by the W-AGF acting on behalf of the FN-BRG are considered as abnormal cases and the behaviour of the UE is specified in subclause 5.6.1.7. When received over wireline access network, the 5G-RG and the W-AGF acting on behalf of the FN-CRG (or on behalf of the N5GC device) shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2), shall delete 5G-GUTI, last visited registered TAI, TAI list and ngKSI, shall enter the state 5GMM-DEREGISTERED and shall act as specified in subclause 5.3.23. NOTE 10: The 5GMM sublayer states, the 5GMM parameters and the registration status are managed per access type independently, i.e. 3GPP access or non-3GPP access (see subclauses 4.7.2 and 5.1.3). #78 (PLMN not allowed to operate at the present UE location). This cause value received from a non-satellite NG-RAN cell is considered as an abnormal case and the behaviour of the UE is specified in subclause 5.6.1.7. The UE shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2) and shall delete last visited registered TAI and TAI list. If the UE is not registering or has not registered to the same PLMN over both 3GPP access and non-3GPP access, the UE shall additionally delete 5G-GUTI and ngKSI. Additionally, the UE shall reset the registration attempt counter. The UE shall store the PLMN identity and, if it is known, the current geographical location in the list of "PLMNs not allowed to operate at the present UE location" and shall start a corresponding timer instance (see subclause 4.23.2). The UE shall enter state 5GMM-DEREGISTERED.PLMN-SEARCH and perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]. If the message was received via 3GPP access and the UE is operating in single-registration mode, the UE shall handle the EMM parameters EMM state, EPS update status, 4G-GUTI, last visited registered TAI, TAI list and eKSI as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15] for the case when the service request procedure is rejected with the EMM cause with the same value. | 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.6.1.5 |
6,057 | 8.3.2.1G Enhanced Performance Requirement Type B – Single-layer Spatial Multiplexing with TM10 serving cell configuration and TM9 interference model | The requirements are specified in Table 8.3.2.1G-2, with the addition of the parameters in Table 8.3.2.1G-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 configured with TM10 in the serving cell is interfered by PDSCH of one dominant interfering cell applying transmission mode 9 interference model defined in clause B.6.3. The NAICS network assistance is provided when the serving cell TM10 is configured with QCL-type A and PCID based DM-RS scrambling. The neighbouring cell has transmission mode TM9 and NeighCellsInfo-r12 for interfering cell indicates presence of TM9. In 8.3.2.1G-1, Cell 1 is the serving cell, and Cell 2, 3 are interfering cells. The downlink physical channel setup is according to Annex C.3.2 for each of Cell 1, Cell 2 and Cell 3, respectively. Table 8.3.2.1G-1: Test Parameters for Testing CDM-multiplexed DM RS (single layer) Multiplexing with TM10 serving cell configuration and TM9 interference model Table 8.3.2.1G-2: Minimum Performance for Enhanced Performance Requirement Type B, CDM-multiplexed DM RS Multiplexing with TM10 serving cell configuration and 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.1G |
6,058 | 5.37.5.3 Non-homogenous support of PDU set based handling in NG-RAN | By sending at least one PDU Set QoS parameter to the NG-RAN, the SMF requests the NG-RAN to activate PDU Set QoS handling for a given QoS flow and the NG-RAN provides the SMF with an indication of whether the PDU Set based handling is supported. Based on this indication, SMF may activate the PDU Set identification and marking in the PSA UPF. For the mobility procedures that may result in the change of NG-RAN for PDU Set based handling support, the target NG-RAN provides to the SMF with an indication of whether the target NG-RAN node supports PDU Set based handling, as specified in TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [34]. Based on the target NG-RAN indication, the SMF may, upon completion of the mobility procedure, initiate the PDU Session modification procedure to provide PDU Set QoS parameters to NG-RAN and may configure the PSA UPF to activate/deactivate the PDU Set identification and marking. In the case where the PSA UPF identifies and marks PDUs with PDU Set information in GTP-U header, it shall start doing so from a complete PDU Set. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.37.5.3 |
6,059 | 12.2.5.3 Limit on maximum number of instances | A GTP-C entity may signal one or multiple instances of the LCI IE, with each providing load control information for a different scope. In order to limit the processing of the message on the receiver side and the size of the message on transport level, the number of load control information instances shall be limited: - at message level: there shall be at most one instance of node level LCI IE per node (i.e. per SGW or PGW) and at most 10 APN level instances. - at node level: the maximum number of instances of LCI IE which may be provided across multiple messages by a given node shall be the same as the maximum number of instances of LCI IE at message level. | 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.3 |
6,060 | 5.3.6 Handling of timer T3402 | The value of timer T3402 can be sent by the network to the UE in the ATTACH ACCEPT message and TRACKING AREA UPDATE ACCEPT message. If the value is different from "deactivated", the UE shall apply this value in all tracking areas of the list of tracking areas assigned to the UE, until a new value is received. The value of timer T3402 can be sent by the network to the UE in the ATTACH REJECT message. If an ATTACH REJECT message including timer T3402 value different from "deactivated", was received integrity protected, the UE shall apply this value until a new value is received with integrity protection or a new PLMN is selected. Otherwise, the default value of this timer is used. The default value of this timer is also used by the UE in the following cases: - ATTACH ACCEPT message or TRACKING AREA UPDATE ACCEPT message is received without a value specified, and the EPS update type in the TRACKING AREA UPDATE REQUEST message is not set to "periodic updating"; - the network indicates that the timer is "deactivated"; - the UE does not have a stored value for this timer; - a new PLMN which is not in the list of equivalent PLMNs has been entered, the tracking area updating fails and the tracking area updating attempt counter is equal to 5; or - a new PLMN which is not in the list of equivalent PLMNs has been entered, the attach procedure fails, the attach attempt counter is equal to 5 and no ATTACH REJECT message was received from the new PLMN. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.3.6 |
6,061 | 4.7.4.2 IAB-node Migration | The IAB-node can migrate to a different parent node underneath the same IAB-donor-CU. The IAB-node continues providing access and backhaul service when migrating to a different parent node. The IAB-MT can also migrate to a different parent node underneath another IAB-donor-CU. In this case, the collocated IAB-DU and the IAB-DU(s) of its descendant node(s) retain F1 connectivity with the initial IAB-donor-CU. The IAB-MT of each descendant node and all the served UEs retain the RRC connectivity with the initial IAB-donor-CU. This migration is referred to as inter-donor partial migration. The IAB-node, whose IAB-MT migrates to the new IAB-donor-CU, is referred to as a boundary IAB-node. After inter-donor partial migration, the F1 traffic of the IAB-DU and its descendant nodes is routed via the BAP layer of the IAB topology to which the IAB-MT has migrated. Inter-donor partial migration is only supported for SA-mode. The intra-donor IAB-node migration procedure and inter-donor partial migration procedures are captured in TS 38.401[ NG-RAN; Architecture description ] [4]. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 4.7.4.2 |
6,062 | A.23 KIAB generation function | This input string is used when the IAB-node and the IAB-donor derive KIAB (PSK) for establishment of secure F1 interface. The following parameters shall be used to form the input S to the KDF: - FC = 0x83, - P0 = IAB-donor-CU IP address, - L0 = length of IAB-donor-CU IP address, - P1 = IAB-node DU IP address, - L1 = length of IAB-node DU IP address. The input key KEY shall be KgNB, if the key KgNB is in possession of the IAB-UE functionality in the IAB-node and in the IAB-donor-CU (also when acts as MN for NR-DC scenario), after the IAB-UE setup procedure (Phase-1). The input key KEY shall be S-KgNB, if the key S-KgNB is in possession of the IAB-UE functionality in the IAB-node and in the IAB-donor-CU (acts as a SN for EN-DC scenario), after dual connectivity procedure. The input key KEY shall be KSN, if the key KSN is in possession of the IAB-UE functionality in the IAB-node and in the IAB-donor-CU (acts as a SN for NR-DC scenario), after dual connectivity procedure. For P0, in case of CP-UP separation of IAB-donor-CU, - P0 shall be set to IAB-donor-CU-CP IP address for deriving KIAB-CU-CP. - P0 shall be set to IAB-donor-CU-UP IP address for deriving KIAB-CU-UP. The entire output of the KDF (256 bits) is used as the KIAB or KIAB-CU-CP or KIAB-CU-UP.. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | A.23 |
6,063 | D.2.1.2 Network-requested UE policy management procedure initiation | In order to initiate the network-requested UE policy management procedure, the PCF shall: a) if the network-requested UE policy management procedure is triggered by the UE-requested V2X policy provisioning procedure as specified in 3GPP TS 24.587[ Vehicle-to-Everything (V2X) services in 5G System (5GS); Stage 3 ] [19B], the UE-requested ProSe policy provisioning procedure as specified in 3GPP TS 24.554[ Proximity-services (ProSe) in 5G System (5GS) protocol aspects; Stage 3 ] [19E] or the UE-requested A2X policy provisioning procedure as specified in 3GPP TS 24.577[ Aircraft-to-Everything (A2X) services in 5G System (5GS) protocol aspects; Stage 3 ] [60], then set the PTI IE to the PTI value of the received UE POLICY PROVISIONING REQUEST message of the UE-requested V2X policy provisioning procedure, the UE-requested ProSe policy provisioning procedure or the UE-requested A2X policy provisioning procedure, otherwise allocate a PTI value currently not used and set the PTI IE to the allocated PTI value; b) encode the information about the UE policy sections to be added, modified or deleted in a UE policy section management list IE as specified in subclause D.6.2 and include it in a MANAGE UE POLICY COMMAND message; c) if the PCF is a PCF of the HPLMN or the subscribed SNPN, optionally include the UE policy network classmark IE in a MANAGE UE POLICY COMMAND message and set the non-subscribed SNPN signalled URSP handling indication of the UE policy network classmark IE to "UE is not allowed to accept URSP signalled by non-subscribed SNPNs", or "UE is allowed to accept URSP signalled by non-subscribed SNPNs"; c1) if the UE supports VPS URSP, optionally encode the information about entries of VPS URSP configuration to be added, modified or deleted in the VPS URSP configuration IE as specified in subclause D.6.8 and include it in a MANAGE UE POLICY COMMAND message; d) send the MANAGE UE POLICY COMMAND message to the UE via the AMF as specified in 3GPP TS 23.502[ Procedures for the 5G System (5GS) ] [9]; and e) start timer T3501 (see example in figure D.2.1.2.1). NOTE: The PCF starts a different timer T3501 for each PTI value. Figure D.2.1.2.1: Network-requested UE policy management procedure Upon receipt of the MANAGE UE POLICY COMMAND message with a PTI value currently not used by a network-requested UE policy management procedure, for each instruction included in the UE policy section management list IE, the UE shall: a) store the received UE policy section of the instruction, if the UE has no stored UE policy section associated with the same UPSI as the UPSI associated with the instruction; b) replace the stored UE policy section with the received UE policy section of the instruction, if the UE has a stored UE policy section associated with the same UPSI as the UPSI associated with the instruction; or c) delete the stored UE policy section, if the UE has a stored UE policy section associated with the same UPSI as the UPSI associated with the instruction and the UE policy section of the instruction is empty; additionally, if the UE policy network classmark IE is included in the MANAGE UE POLICY COMMAND message, and a) the UE has an empty EHPLMN list or the EHPLMN list is not present, and the UE's RPLMN is the HPLMN; b) the UE has a non-empty EHPLMN list, and the UE's RPLMN is an EHPLMN; or c) the UE's RSNPN is the subscribed SNPN, the UE shall delete the non-subscribed SNPN signalled URSP handling indication stored for the selected entry of "list of subscriber data" or the selected PLMN subscription, if any, and store the non-subscribed SNPN signalled URSP handling indication received in the UE policy network classmark IE, for the selected entry of "list of subscriber data" or the selected PLMN subscription. If the UE supports the VPS URSP, and the VPS URSP configuration is included in the MANAGE UE POLICY COMMAND message: a) if the replacement type field of the received VPS URSP configuration indicates "full list of tuples", the UE shall delete the stored VPS URSP configuration, if any; and b) if the received VPS URSP configuration contains one or more tuples: 1) if the UE does not have the stored VPS URSP configuration, the UE shall store the received VPS URSP configuration except zero or more tuples with no UPSCs; or 2) otherwise: i) for each tuple with a tuple ID in the stored VPS URSP configuration: A) if a tuple with the tuple ID is in the received VPS URSP configuration and contains: - no UPSCs, the UE shall delete the tuple with the tuple ID from the stored VPS URSP configuration; or - one or more UPSCs, the UE shall replace the tuple with the tuple ID in the stored VPS URSP configuration with the tuple with the tuple ID from the received VPS URSP configuration; or B) if no tuple with the tuple ID is in the received VPS URSP configuration, the UE shall keep the tuple with the tuple ID in the stored VPS URSP configuration; and ii) for each tuple with a tuple ID in the received VPS URSP configuration, if no tuple with the tuple ID is in the stored VPS URSP configuration and: A) the tuple with the tuple ID in the received VPS URSP configuration contains no UPSCs, the UE shall ignore the tuple with the tuple ID in the received VPS URSP configuration; or B) the tuple with the tuple ID in the received VPS URSP configuration contains one or more UPSCs, the UE shall add the tuple with the tuple ID from the received VPS URSP configuration to the stored VPS URSP configuration. The UE may continue storing a received UE policy section for a PLMN or SNPN when the UE registers in another PLMN or SNPN. If necessary, the UE may delete UE policy sections stored for a PLMN other than the RPLMN and the HPLMN or for an SNPN other than the registered SNPN and the subscribed SNPN, before storing the new received UE policy sections. When storing a UE policy section received from an SNPN, the UE shall associate the NID of that SNPN with the UPSI of the stored UE policy section. NOTE: The maximum number of UE policy sections for PLMNs or SNPNs other than the HPLMN and the RPLMN or the registered SNPN and the subscribed SNPN that the UE can store and how the UE selects the UE policy sections to be deleted are up to the UE implementation. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | D.2.1.2 |
6,064 | 5.5.3.6 IMS Interconnection | IMS Interconnection may include the following scenarios - Interworking between several IMS-based networks - Interworking between IMS-based networks and N/ISDN - Interworking between IMS-based networks and TISPAN NGN supporting N/ISDN Emulation - Interworking between IMS-based networks and non-IMS-based networks - IMS transit scenarios in multi operator environments where one or more transit operators are between the originating and terminating operator. For IMS transit scenarios, all involved transit operators get captured in the signalling, as described in clause 5.3.4.3. Depending on the operator specific policy, IMS transit charging may be limited to the immediately adjacent transit operators only, or consider all involved transit carriers within the multi-operator environment. IMS Interconnection charging is described in TS 32.260[ Telecommunication management;Charging management;IP Multimedia Subsystem (IMS) charging ] [20]. | 3GPP TS 32.240 | Telecommunication management; Charging management; Charging architecture and principles | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 5.5.3.6 |
6,065 | 5.19 Activation/Deactivation of CSI-RS resources | The network may activate and deactivate the configured CSI-RS resources of a serving cell by sending the Activation/Deactivation of CSI-RS resources MAC control element described in clause 6.1.3.14. The configured CSI-RS resources are initially deactivated upon configuration and after a handover. The MAC entity shall for each TTI: - if the MAC entity receives an Activation/Deactivation of CSI-RS resources MAC control element in this TTI on a serving cell, the MAC entity shall indicate to lower layers the information regarding the Activation/Deactivation of CSI-RS resources MAC control element: | 3GPP TS 36.321 | Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification | RAN2 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 5.19 |
6,066 | 10.5.3.14 Additional update parameters | The purpose of the Additional update parameters information element is to provide additional information during the location updating procedure and during MM connection establishment. The Additional update parameters information element is coded as shown in figure 10.5.84d/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.97b/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The Additional update parameters information element is a type 1 information element. Figure 10.5.84d/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Additional update parameters information element Table 10.5.97b/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Additional update parameters information element | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 10.5.3.14 |
6,067 | N.2.2 Configuration of network to provide access to Localized Services | For configuring the PNI-NPN or SNPN (e.g. creation of network slice/DNN for carrying Localized Service traffic), existing OAM mechanisms can be re-used as per TS 28.557[ Management and orchestration; Management of Non-Public Networks (NPN); Stage 1 and stage 2 ] [148] clause 6.3.1, that provides a solution for NPN provisioning by a network slice of a PLMN and for exposure of management capability of PNI-NPN (clause 6.3.2). The attributes to support this management is further documented in TS 28.541[ Management and orchestration; 5G Network Resource Model (NRM); Stage 2 and stage 3 ] [149]. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | N.2.2 |
6,068 | 5.3.5.3 Rejection of service level up- and downgrading | If a change of bearer service is requested together with a change of the "maximum number of traffic channels" and/or the "wanted air interface user rate", or if the current used service is not a data service where up- and downgrading is applicable, or if the receiver chooses not to grant the request, the network shall: - send a MODIFY REJECT message with bearer capability negotiated at call setup and with cause #58 "bearer capability not presently available"; - enter the "active" state. Upon receipt of the MODIFY REJECT message with the bearer capability negotiated at call setup, the mobile station shall: stop timer T323 and enter the "active" state. | 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.5.3 |
6,069 | 8.2.1.6 LTM with gNB-CU-UP change | Figure 8.2.1.6-1 shows the procedure used for LTM with the change of gNB-CU-UP within a gNB. Figure 8.2.1.6-1 LTM with the change of gNB-CU-UP 0. The source gNB-DU forwards the Measurement Report to the gNB-CU-CP. 1. The gNB-CU-CP decides to initiate LTM configuration. 2. The gNB-CU-CP sends a BEARER CONTEXT SETUP REQUEST message containing UL TNL address information for NG-U to setup the bearer context in the target gNB-CU-UP. 3. The target gNB-CU-UP responds with a BEARER CONTEXT SETUP RESPONSE message containing the UL TNL address information for F1-U, DL TNL address information for NG-U, and the TNL address information for data forwarding to the target gNB-CU-UP. 4. LTM configuration procedures are performed between gNB-CU and candidate gNB-DUs, and between gNB-CU and source gNB-DU as specified from step 3 to step 8 in section 8.2.1.5. 5 - 6. The gNB-CU-CP sends the RRC Reconfiguration message to the UE. 7. The UE sends the lower layer measurement result to the source gNB-DU, and the source gNB-DU decides to execute LTM to a candidate target cell. 8. The source gNB-DU sends the DU-CU CELL SWITCH NOTIFICATION message to the gNB-CU-CP with the selected target cell ID. 9-10. The gNB-CU-CP performs the Bearer Context Modification procedure to retrieve the PDCP UL/DL status and to exchange the TNL address information for data forwarding for the bearers. 11-12. The gNB-CU-CP performs the Bearer Context Modification procedure to send the DL TNL address information for F1-U and the PDCP UP/DL status to the target gNB-CU-UP. 13. Data Forwarding may be performed from the source gNB-CU-UP to the target gNB-CU-UP. 14. The target gNB-DU detects the UE in the target cell. 15. The target gNB-DU sends an ACCESS SUCCESS message to the gNB-CU-CP. 16-18. Path Switch procedure is performed to update the DL TNL address information for the NG-U towards the core network. 19-20. Bearer Context Release procedure may be performed to release the UE context in the source gNB-DU. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 8.2.1.6 |
6,070 | 5.7A Charging 5.7A.1 General | Accounting functionality is provided by the Serving GW and the PDN GW. When a Secondary RAT may be used, the Serving GW and PDN GW can be assisted by the E-UTRAN (see clause 5.7A.4). The Serving GW shall be able to collect and report for each UE accounting information, i.e. the amount of data transmitted in uplink and downlink direction categorized with the QCI and ARP pair per UE per PDN connection. For GTP-based S5/S8 the accounting information is collected and reported per bearer. The Serving GW shall not collect UE accounting information for packets that are being processed for the sole purpose of indirect forwarding. The Serving GW for inter-operator charging, and the PDN GW shall be able to interface the OFCS according to charging principles and through reference points specified in TS 32.240[ Telecommunication management; Charging management; Charging architecture and principles ] [51]. The PDN GW shall be able to provide charging functionality for each UE according to TS 23.203[ Policy and charging control architecture ] [6]. The PDN GW data collection for charging and usage monitoring purposes can be temporarily paused as described in clause 5.3.6A. A PDN GW without a Gx interface shall be able to flow based online and offline charging based on local configuration and interaction with the Online and Offline Charging Systems. The Online Charging System may provide a PRA identifier(s) to the PDN GW to subscribe to notifications about changes of UE presence in Presence Reporting Area as defined in the TS 23.203[ Policy and charging control architecture ] [6]. For UE-dedicated Presence Reporting Areas the Online Charging System also provides the list(s) of the elements comprising each subscribed UE-dedicated Presence Reporting Area. The PDN GW shall be able to collect and report, for each UE, accounting information, i.e. the amount of data received and transmitted in uplink and downlink direction categorized with the QCI and ARP pair per UE per PDN connection. For GTP-based S5/S8 the accounting information is collected and reported per bearer. The PDN GW data collection can be temporarily paused as described in clause 5.3.6A based on operator configuration in the PDN GW. NOTE: A consequence of pausing the PDN GW data collection is that PDN GW accounting information may not correspond to the volume that traversed the PDN GW and it is therefore not possible to verify accounting information collected at the Serving GW for inter-operator charging. The Charging identifier(s) generated by the PDN GW per bearer for GTP-based S5/S8 and per PDN connection for PMIP-based S5/S8 and the PDN GW address for control signalling enables the correlation of the reporting from a Serving GW and a PDN GW. The Charging identifier is uniquely assigned within the PDN GW. The PDN GW receives Charging Characteristics from the Serving GW through GTP-S5/S8, or through PMIP for PMIP-based S5/S8. The handling of the Charging Characteristics in the P-GW is defined in TS 32.251[ Telecommunication management;Charging management;Packet Switched (PS) domain charging ] [44]. To enable CSG charging function for a subscriber consuming network services via a CSG cell or a hybrid cell, User CSG Information is transferred to the PDN GW as indicated by CSG Information Reporting Action. User CSG Information includes CSG ID, access mode and CSG membership indication. CSG membership indication of whether the UE is a member of the CSG is included if the access mode is hybrid. The valid CSG information shall be available in the serving GW and PDN GW in connected mode. The PCRF shall, if deployed, provide User CSG Information reporting rules to the PDN GW at Attach and PDN Connectivity Request. PDN GW sets the CSG Information Reporting Action IE according to the User CSG Information reporting rules and sends it to Serving GW and MME. To enable the MME to signal the correct RAT Type (NB-IoT or WB-E-UTRAN) to the SGW and PDN GW for accounting information generation purposes, the eNodeB informs the MME of the RAT Type and TAC associated with each cell in the S1 SETUP REQUEST and eNodeB CONFIGURATION UPDATE messages (TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [36]). If the eNodeB signals WB-EUTRAN and the UE is of Category M from the UE's radio capability, the MME reports RAT Type LTE-M to the SGW. See clause 5.11.5 for more details. | 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.7A |
6,071 | 5.3.5.16.2 L2 U2U Relay UE Addition/Modification | The L2 U2U Remote UE shall: 1> if no SRAP entity has been established: 2> establish a SRAP entity as specified in TS 38.351[ NR; Sidelink Relay Adaptation Protocol (SRAP) Specification ] [66]; 1> for each L2 U2U Relay UE indicated in sl-L2IdentityRelay value included in the sl-U2U-RelayUE-ToAddModList that is not part of the current UE configuration (L2 U2U Relay UE Addition): 2> for peer target L2 U2U Remote UE indicated in sl-TargetUE-Identity in accordance with one entry of the SL-PeerRemoteUE-ToAddModList, configure the parameters to SRAP entity in accordance with the sl-SRAP-ConfigU2U; 1> for each L2 U2U Relay UE indicated in sl-L2IdentityRelay value included in the sl-U2U-RelayUE-ToAddModList that is part of the current UE configuration (L2 U2U Relay UE modification): 2> for each peer target L2 U2U Remote UE included in the sl-PeerRemoteUE-ToReleaseList (peer target L2 U2U Remote UE Release): 3> release the configuration associated with the peer target L2 U2U Remote UE; 2> for the peer target L2 U2U Remote UE indicated in sl-TargetUE-Identity included in the sl-PeerTargetRemoteUE-ToAddModList that is not part of the current UE configuration (peer target L2 U2U Remote UE Addition): 3> configure the parameters to SRAP entity in accordance with the sl-SRAP-ConfigU2U; 2> for the peer target L2 U2U Remote UE indicated in sl-TargetUE-Identity included in the sl-PeerTargetRemoteUE-ToAddModList that is part of the current UE configuration (peer target L2 U2U Remote UE modification): 3> modify the configuration in accordance with the sl-SRAP-ConfigU2U; | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.5.16.2 |
6,072 | 7.10.1 KPI requirement for direct network connection | The 5G system shall support split AI/ML inference between UE and Network Server/Application function with performance requirements as given in Table 7.10.1-1. Table 7.10.1-1 KPI Table of split AI/ML inference between UE and Network Server/Application function The 5G system shall support AI/ML model downloading with performance requirements as given in Table 7.10.1-2. Table 7.10.1-2 KPI Table of AI/ML model downloading The 5G system shall support Federated Learning between UE and Network Server/Application function with performance requirements as given in Table 7.10.1-3. Table 7.10.1-3: KPI Table of Federated Learning between UE and Network Server/Application function | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 7.10.1 |
6,073 | 7.3.21 UE Registration Query Request | The direction of this message shall be from S4-SGSN to MME (see Table 6.1-1). This message shall be used to support CS/PS coordination for shared UTRAN and GERAN access. When an S4-SGSN receives a UE Registration Query from a RAN node, including an indication to also query MMEs, and if the UE (identified by IMSI) is not registered in the S4-SGSN, the S4-SGSN shall send a UE Registration Query Request message to all MMEs that may hold the UE's context, as specified in the clause 7.1.6 of 3GPP TS 23.251[ Network sharing; Architecture and functional description ] [55]. NOTE: How the S4-SGSN determines which MMEs it will query, is based on local configuration. Table 7.3.21-1 specifies the presence of IEs in this message. Table 7.3.21-1: Information Elements in UE Registration Query Request | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 7.3.21 |
6,074 | 6.2.5.0 NEF functionality | The Network Exposure Function (NEF) supports the following independent functionality: - Exposure of capabilities and events: NF capabilities and events may be securely exposed by NEF for e.g. 3rd party, Application Functions, Edge Computing as described in clause 5.13. NEF stores/retrieves information as structured data using a standardized interface (Nudr) to the Unified Data Repository (UDR). - Secure provision of information from external application to 3GPP network: It provides a means for the Application Functions to securely provide information to 3GPP network, e.g. Expected UE Behaviour, 5G-VN group information, time synchronization service information and PDU Set handling service specific information. In that case the NEF may authenticate and authorize and assist in throttling the Application Functions. - Translation of internal-external information: It translates between information exchanged with the AF and information exchanged with the internal network function. For example, it translates between an AF-Service-Identifier and internal 5G Core information such as DNN, S-NSSAI, as described in clause 5.6.7. In particular, NEF handles masking of network and user sensitive information to external AF's according to the network policy. - Redirecting the AF to a more suitable NEF/L-NEF e.g. when serving an AF request for local information exposure and detecting there is a more appropriate NEF instance to serve the AF's request. - The Network Exposure Function receives information from other network functions (based on exposed capabilities of other network functions). NEF stores the received information as structured data using a standardized interface to a Unified Data Repository (UDR). The stored information can be accessed and "re-exposed" by the NEF to other network functions and Application Functions, and used for other purposes such as analytics. - A NEF may also support a PFD Function: The PFD Function in the NEF may store and retrieve PFD(s) in the UDR and shall provide PFD(s) to the SMF on the request of SMF (pull mode) or on the request of PFD management from NEF (push mode), as described in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]. - A NEF may also support a 5G-VN Group Management Function: The 5G-VN Group Management Function in the NEF may store the 5G-VN group information in the UDR via UDM as described in TS 23.502[ Procedures for the 5G System (5GS) ] [3]. - Support management of ECS Address Information. - Support management of relationship between DNAI and EAS Address Information. - Exposure of analytics: NWDAF analytics may be securely exposed by NEF for external party, as specified in TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [86]. - Retrieval of data from external party by NWDAF: Data provided by the external party may be collected by NWDAF via NEF for analytics generation purpose. NEF handles and forwards requests and notifications between NWDAF and AF, as specified in TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [86]. - Support of Non-IP Data Delivery: NEF provides a means for management of NIDD configuration and delivery of MO/MT unstructured data by exposing the NIDD APIs as described in TS 23.502[ Procedures for the 5G System (5GS) ] [3] on the N33/Nnef reference point. See clause 5.31.5. - Charging data collection and support of charging interfaces. - Support of Member UE selection assistance functionality: - NEF may provide one or more list(s) of candidate UE(s) (among the list of target member UE(s) provided by the AF) and additional information to the AF based on the parameters contained in the request from the AF as described in clause 5.46.2. NEF supports the translation of the member UE selection filtering criteria parameters received from the AF to the corresponding event or analytics filters that can be understood by the 5GC NFs for events or analytics related data collection. NEF interacts with 5GC NFs using existing services in order to collect the corresponding data and then derive the list(s) of candidate UE(s) and other assistance information as described in clause 4.15.13 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. - Support of Multi-member AF session with required QoS for a set of UEs identified by a list of UE addresses: - Details are specified in clause 4.15.6.13 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. - Support of UAS NF functionality: Details are defined in TS 23.256[ Support of Uncrewed Aerial Systems (UAS) connectivity, identification and tracking; Stage 2 ] [136]. - Support of EAS deployment functionality: Details are defined in TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [130]. - Support of SBI-based MO SM transmit for MSISDN-less MO SMS: Details are defined in TS 23.540[ 5G System: Technical realization of Service Based Short Message Service; Stage 2 ] [142]. - Support PDU Set Handling as defined in clause 5.37.5. - Support management of common EAS and common DNAI: Details are defined in TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [130]. A specific NEF instance may support one or more of the functionalities described above and consequently an individual NEF may support a subset of the APIs specified for capability exposure. NOTE: The NEF can access the UDR located in the same PLMN as the NEF. The services provided by the NEF are specified in clause 7.2.8. For external exposure of services related to specific UE(s), the NEF resides in the HPLMN. Depending on operator agreements, the NEF in the HPLMN may have interface(s) with NF(s) in the VPLMN. When a UE is capable of switching between EPC and 5GC, an SCEF+NEF is used for service exposure. See clause 5.17.5 for a description of the SCEF+NEF. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 6.2.5.0 |
6,075 | 4.4.6 Protection of initial NAS signalling messages | The 5GS supports protection of initial NAS messages as specified in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]. The protection of initial NAS messages applies to the REGISTRATION REQUEST, DEREGISTRATION REQUEST, SERVICE REQUEST and CONTROL PLANE SERVICE REQUEST message, and is achieved as follows: a) If the UE does not have a valid 5G NAS security context, the UE sends a REGISTRATION REQUEST message including cleartext IEs only. After activating a 5G NAS security context resulting from a security mode control procedure: 1) if the UE needs to send non-cleartext IEs, the UE shall include the entire REGISTRATION REQUEST message (i.e. containing both cleartext IEs and non-cleartext IEs) in the NAS message container IE and shall include the NAS message container IE in the SECURITY MODE COMPLETE message; or 2) if the UE does not need to send non-cleartext IEs, the UE shall include the entire REGISTRATION REQUEST message (i.e. containing cleartext IEs only) in the NAS message container IE and shall include the NAS message container IE in the SECURITY MODE COMPLETE message. b) If the UE has a valid 5G NAS security context and: 1) the UE needs to send non-cleartext IEs in a REGISTRATION REQUEST, DEREGISTRATION REQUEST, or SERVICE REQUEST message, the UE includes the entire REGISTRATION REQUEST, DEREGISTRATION REQUEST or SERVICE REQUEST message (i.e. containing both cleartext IEs and non-cleartext IEs) in the NAS message container IE and shall cipher the value part of the NAS message container IE. The UE shall then send a REGISTRATION REQUEST, DEREGISTRATION REQUEST, or SERVICE REQUEST message containing the cleartext IEs and the NAS message container IE; 2) the UE needs to send non-cleartext IEs in a CONTROL PLANE SERVICE REQUEST message: i) if CIoT small data container IE is the only non-cleartext IE to be sent, the UE shall cipher the value part of the CIoT small data container IE. The UE shall then send a CONTROL PLANE SERVICE REQUEST message containing the cleartext IEs and the CIoT small data container IE; ii) otherwise, the UE includes non-cleartext IEs in the NAS message container IE and shall cipher the value part of the NAS message container IE. The UE shall then send a CONTROL PLANE SERVICE REQUEST message containing the cleartext IEs and the NAS message container IE; 3) the UE does not need to send non-cleartext IEs in a REGISTRATION REQUEST, DEREGISTRATION REQUEST, or SERVICE REQUEST message, the UE sends the REGISTRATION REQUEST, DEREGISTRATION REQUEST, or SERVICE REQUEST message without including the NAS message container IE; or 4) the UE does not need to send non-cleartext IEs in a CONTROL PLANE SERVICE REQUEST message, the UE sends the CONTROL PLANE SERVICE REQUEST message without including the NAS message container IE and the CIoT small data container IE. When the initial NAS message is a REGISTRATION REQUEST message, the cleartext IEs are: - Extended protocol discriminator; - Security header type; - Spare half octet; - Registration request message identity; - 5GS registration type; - ngKSI; - 5GS mobile identity; - UE security capability; - Additional GUTI; - UE status; - EPS NAS message container; - NID; and - PLMN with disaster condition. When the initial NAS message is a DEREGISTRATION REQUEST message, the cleartext IEs are: - Extended protocol discriminator; - Security header type; - Spare half octet; - De-registration request message identity; - De-registration type; - ngKSI; and - 5GS mobile identity. When the initial NAS message is a SERVICE REQUEST message, the cleartext IEs are: - Extended protocol discriminator; - Security header type; - Spare half octet; - ngKSI; - Service request message identity; - Service type; and - 5G-S-TMSI. When the initial NAS message is a CONTROL PLANE SERVICE REQUEST message, the cleartext IEs are: - Extended protocol discriminator; - Security header type; - Spare half octet; - ngKSI; - Control plane service request message identity; and - Control plane service type. When the UE sends a REGISTRATION REQUEST, DEREGISTRATION REQUEST, SERVICE REQUEST or CONTROL PLANE SERVICE REQUEST message that includes a NAS message container IE, the UE shall set the security header type of the initial NAS message to "integrity protected". When the AMF receives an integrity protected initial NAS message which includes a NAS message container IE, the AMF shall decipher the value part of the NAS message container IE. If the received initial NAS message is a REGISTRATION REQUEST, DEREGISTRATION REQUEST, or a SERVICE REQUEST message, the AMF shall consider the NAS message that is obtained from the NAS message container IE as the initial NAS message that triggered the procedure. When the AMF receives a CONTROL PLANE SERVICE REQUEST message which includes a CIoT small data container IE, the AMF shall decipher the value part of the CIoT small data container IE and handle the message as specified in subclause 5.6.1.4.2. If the UE: a) has 5G-EA0 as a selected 5G NAS security algorithm; and b) selects a PLMN other than Registered PLMN and EPLMN over one access; the UE shall send an initial NAS message including cleartext IEs only via the access type associated with the newly selected PLMN as described in this subclause for the case when the UE does not have a valid 5G NAS security context. If the UE: a) has 5G-EA0 as a selected 5G NAS security algorithm; and b) selects a PLMN other than Registered PLMN and EPLMN over one access, and the Registered PLMN or EPLMN is not registering or registered over other access; the UE shall delete the 5G NAS security context. NOTE: UE deletes the 5G NAS security context only if the UE is not in the connected mode. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.4.6 |
6,076 | 16.12.7 Control plane procedures for L2 U2U Relay | The L2 U2U Remote UE needs to establish end-to-end SL-SRB/DRBs with the peer L2 U2U Remote UE before user plane data transmission. The following high level connection establishment procedure in Figure 16.12.7-1 applies to a L2 U2U Relay UE and L2 U2U Remote UE: Figure 16.12.7-1: Procedure for L2 U2U Remote UE connection establishment 1. The L2 U2U Remote UE, L2 U2U Relay UE, and peer L2 U2U Remote UE perform discovery procedure or integrated discovery procedure. 2a. The L2 U2U Remote UE establishes/modifies a PC5-RRC connection with the selected L2 U2U Relay UE (i.e., as specified in TS 23.304[ Proximity based Services (ProSe) in the 5G System (5GS) ] [48]). 2b. The L2 U2U Relay UE establishes/modifies a PC5-RRC connection with the peer L2 U2U Remote UE (i.e., as specified in TS 23.304[ Proximity based Services (ProSe) in the 5G System (5GS) ] [48]). 3. The L2 U2U Relay UE allocates two local IDs and it is delivered via RRCReconfigurationSidelink message to each of the L2 U2U Remote UEs: one local ID to identify the L2 U2U Remote UE, the other local ID to identify the peer L2 U2U Remote UE. When the local ID is delivered, an L2 ID of the peer L2 U2U Remote UE is also delivered to the U2U Remote UE for making the association between the local ID and the L2 ID of the peer U2U Remote UE. 4. The L2 U2U Remote UE establishes end-to-end PC5-RRC connection with the peer L2 U2U Remote UE via the L2 U2U Relay UE. For the end-to-end connection establishment, fixed indexes (i.e., 0/1/2/3) are defined for end-to-end SL-SRB 0/1/2/3 respectively, and specified PC5 Relay RLC Channel configuration is used on each hop. The sidelink UE capability is exchanged between the L2 U2U Remote UEs via PC5-RRC (e.g., SL-SRB3) message. 5. The L2 U2U Remote UE sends to the L2 U2U Relay UE all the QoS profiles for the end-to-end QoS flows via PC5-RRC. 6. The L2 U2U Relay UE performs QoS split only for PDB. NOTE: It is up to L2 U2U Relay UE implementation on how to split PDB. 7. The L2 U2U Relay UE sends the split QoS value (i.e., PDB) via PC5-RRC message to the L2 U2U Remote UE.8. The L2 U2U Remote UE or the serving gNB of the L2 U2U Remote UE derives the PDCP and SDAP configuration for end-to-end SL-DRB and provides the portion of the configuration related to reception to the peer L2 U2U Remote UE using end-to-end RRCReconfigurationSidelink messages. The end-to-end bearer IDs for SL-SRB and SL-DRB are used as input for the L2 U2U Relay ciphering and deciphering at PDCP. 9a. The L2 U2U Remote UE or the serving gNB of the L2 U2U Remote UE derives the first hop configuration (e.g. PC5 Relay RLC Channel configuration) for SL-DRB and provides to the L2 U2U Relay UE of the configuration related to receiving on the first hop (i.e., Rx by the relay UE), using per-hop RRCReconfigurationSidelink message. 9b. The L2 U2U Relay UE or the serving gNB of the L2 U2U Relay UE derives the second hop configuration (e.g. PC5 Relay RLC Channel configuration) for each SL-DRB and provides to the peer L2 U2U Remote UE of the configuration related to receiving data packets on the second hop (i.e., RX by the peer remote UE), using per-hop RRCReconfigurationSidelink message. 10. The L2 U2U Remote UE and the peer L2 U2U Remote UE transmit or receive data via L2 U2U Relay UE. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.12.7 |
6,077 | 5.2.2.2.13 Namf_Communication_EBIAssignment service operation | Service operation name: Namf_Communication_EBIAssignment. Description: The consumer NF uses this service operation to request a bunch of EPS Bearer IDs for a PDU Session and optionally indicate to the AMF the list of EBI(s) to be released. Inputs, Required: SUPI, PDU Session ID, ARP list. Input, Optional: Released EBI list. Outputs, Required: None. Outputs, Optional: a list of <ARP, EBI> pair, <ARP, Cause> pair. The consumer NF invokes the Namf_Communication_EBIAssignment service operation when it determines that one or more EPS Bearer IDs are required for EPS QoS mapping for a PDU Session. The ARP list indicates the number of the requested EBIs and the corresponding ARP. The AMF uses the ARP list (including ARP priority level, the pre-emption capability and the pre-emption vulnerability) and the S-NSSAI to prioritize the EBI request, AMF can revoke the EBI from an ongoing lower priority PDU Session, if the maximum number of EBIs have been reached and a session with a higher priority requests an EBI. The AMF responds the consumer NF with a cause which indicates whether the assignment is successful or not. If the assignment is successful, the AMF provides a list of <ARP, EBI> pair to the consumer NF. If the consumer NF determines that some EBIs are not needed, the consumer NF indicates the EBI(s) that can be released in the Released EBI list. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.2.2.13 |
6,078 | 4.4.4 Integrity protection of NAS signalling messages 4.4.4.1 General | For the UE, integrity protected signalling is mandatory for the NAS messages once a valid EPS security context exists and has been taken into use. For the network, integrity protected signalling is mandatory for the NAS messages once a secure exchange of NAS messages has been established for the NAS signalling connection. Integrity protection of all NAS signalling messages is the responsibility of the NAS. It is the network which activates integrity protection. The use of "null integrity protection algorithm" EIA0 (see clause 9.9.3.23) in the current security context is only allowed for an unauthenticated UE for which establishment of emergency bearer services or access to RLOS is allowed. For setting the security header type in outbound NAS messages, the UE and the MME shall apply the same rules irrespective of whether the "null integrity protection algorithm" or any other integrity protection algorithm is indicated in the security context. If the "null integrity protection algorithm" EIA0 has been selected as an integrity protection algorithm, the receiver shall regard the NAS messages with the security header indicating integrity protection as integrity protected. Details of the integrity protection and verification of NAS signalling messages are specified in 3GPP TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [19]. When a NAS message needs to be sent both ciphered and integrity protected, the NAS message is first ciphered and then the ciphered NAS message and the NAS sequence number are integrity protected by calculating the MAC. The same applies when an initial NAS message needs to be sent partially ciphered and integrity protected. NOTE: NAS messages that are ciphered or partially ciphered with the "null ciphering algorithm" EEA0 are regarded as ciphered or partially ciphered, respectively (see clause 4.4.5). When a NAS message needs to be sent only integrity protected and unciphered, the unciphered NAS message and the NAS sequence number are integrity protected by calculating the MAC. When during the EPS attach procedure or service request procedure an ESM message is piggybacked in an EMM message, there is only one sequence number IE and one message authentication code IE, if any, for the combined NAS message. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.4.4 |
6,079 | 8.3.2.1D Enhanced Performance Requirement Type B – Single-layer Spatial Multiplexing with TM9 interference | The requirements are specified in Table 8.3.2.1D-2, with the addition of the parameters in Table 8.3.2.1D-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 7or 8 without a simultaneous transmission on the other antenna port in the serving cell when the PDSCH transmission in the serving cell is interfered by PDSCH of two interfering cells applying transmission mode 9 interference model defined in clause B.6.4. In 8.3.2.1D-1, Cell 1 is the serving cell, and Cell 2, 3 are interfering cells. The downlink physical channel setup is according to Annex C.3.2 for each of Cell 1, Cell 2 and Cell 3, respectively. Table 8.3.2.1D-1: Test Parameters for Testing CDM-multiplexed DM RS (Single-layer) with TM9 interference model Table 8.3.2.1D-2: Minimum Performance for Enhanced Performance Requirement Type B, 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.1D |
6,080 | 5.5.2.3.4 Abnormal cases in the UE | The following abnormal cases can be identified: a) Transmission failure of DEREGISTRATION ACCEPT message indication from lower layers. The de-registration procedure shall be progressed and the UE shall send the DEREGISTRATION ACCEPT message. b) DEREGISTRATION REQUEST, other 5GMM cause values than those treated in subclause 5.5.2.3.2, cases of 5GMM cause value#11, #15, #22, #72, #74, #75, #76, #77, #78, #79 and #93 that are considered as abnormal cases according to subclause 5.5.2.3.2 or no 5GMM cause IE is included, and the De-registration type IE indicates "re-registration not required". The UE shall delete TAI list, last visited registered TAI and list of equivalent PLMNs (if any) or list of equivalent SNPNs (if any), shall set the 5GS update status to 5U2 NOT UPDATED and shall start timer T3502. If the UE is not registering or has not registered to the same PLMN over both 3GPP access and non-3GPP access, the UE shall additionally delete 5G-GUTI and ngKSI. A UE not supporting S1 mode may enter the state 5GMM-DEREGISTERED.PLMN-SEARCH in order to perform a PLMN selection or SNPN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]; otherwise the UE shall enter the state 5GMM-DEREGISTERED.ATTEMPTING-REGISTRATION. If the de-registration request is for 3GPP access only or for both 3GPP access and non-3GPP access and the UE is operating in the single-registration mode, the UE shall: - enter the state 5GMM-DEREGISTERED and attempt to select E-UTRAN radio access technology and proceed with the appropriate EMM specific procedures. In this case, the UE may disable the N1 mode capability (see subclause 4.9); or - enter the state 5GMM-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 ] [5]. If the message was received via 3GPP access and the UE is operating in the single-registration mode, the UE shall set the EPS update status to EU2 NOT UPDATED, enter the state EMM-DEREGISTERED and shall delete the EMM parameters 4G-GUTI, last visited registered TAI, TAI list and eKSI. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.5.2.3.4 |
6,081 | 6.2.4 Resource-element groups (REGs) | Resource-element groups are used for defining the mapping of control channels to resource elements. A resource-element group is represented by the index pair of the resource element with the lowest index in the group with all resource elements in the group having the same value of . The set of resource elements in a resource-element group depends on the number of cell-specific reference signals configured as described below with , . - In the first OFDM symbol of the first slot in a subframe the two resource-element groups in physical resource block consist of resource elements with and , respectively. - In the second OFDM symbol of the first slot in a subframe in case of one or two cell-specific reference signals configured, the three resource-element groups in physical resource block consist of resource elements with , and , respectively. - In the second OFDM symbol of the first slot in a subframe in case of four cell-specific reference signals configured, the two resource-element groups in physical resource block consist of resource elements with and , respectively. - In the third OFDM symbol of the first slot in a subframe, the three resource-element groups in physical resource block consist of resource elements with , and , respectively. - In the fourth OFDM symbol of the first slot in a subframe in case of normal cyclic prefix, the three resource-element groups in physical resource block consist of resource elements with , and , respectively. - In the fourth OFDM symbol of the first slot in a subframe in case of extended cyclic prefix, the two resource-element groups in physical resource block consist of resource elements with and , respectively. Mapping of a symbol-quadruplet onto a resource-element group represented by resource-element is defined such that elements are mapped to resource elements of the resource-element group not used for cell-specific reference signals in increasing order of and . In case a single cell-specific reference signal is configured, cell-specific reference signals shall be assumed to be present on antenna ports 0 and 1 for the purpose of mapping a symbol-quadruplet to a resource-element group, otherwise the number of cell-specific reference signals shall be assumed equal to the actual number of antenna ports used for cell-specific reference signals. The UE shall not make any assumptions about resource elements assumed to be reserved for reference signals but not used for transmission of a reference signal. For frame structure type 3, if the higher layer parameter subframeStartPosition indicates 's07' and the downlink transmission starts in the second slot of a subframe, the above definition applies to the second slot of that subframe instead of the first slot. | 3GPP TS 36.211 | Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation | RAN1 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.2.4 |
6,082 | 15.3 Protection of management interactions between the management service consumer and the management service producer | TLS shall be used to provide mutual authentication, integrity protection, replay protection and confidentiality protection for the interface between the management service producer and the management service consumer residing outside the 3GPP operator’s trust domain. Security profiles for TLS implementation and usage shall follow the TLS profile given in clause 6.2 of TS 33.210[ Network Domain Security (NDS); IP network layer security ] [3] and the certificate profile given in clause 6.1.3a of TS 33.310[ Network Domain Security (NDS); Authentication Framework (AF) ] [5]. The identities in the end entity certificates shall be used for authentication and policy checks. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 15.3 |
6,083 | 5.32.5.2 Round Trip Time Measurements | RTT measurements can be conducted by the UE and UPF independently. There is no measurement reporting from one side to the other. RTT measurements are defined to support the "Smallest Delay", "Priority-based", "Load Balancing" or "Redundant" steering mode (i.e. when RTT threshold value is applied). The estimation of the RTT by the UE and by the UPF is based on the following mechanism: 1. The PMF in the UE sends over the user plane PMF-Echo Request messages to the PMF in the UPF, and the PMF in the UPF responds to each one with a PMF-Echo Response message. Similarly, the PMF in the UPF sends over the user plane PMF-Echo Request messages to the PMF in the UE, and the PMF in the UE responds to each one with a PMF-Echo Response message. 2. When the UP connection of the MA PDU session is deactivated on an access, no PMF-Echo Request messages are sent on this access. The PMF in the UPF shall not send PMF-Echo Request on this access if the UP connection is not available or after it receives notification from the (H-)SMF to stop sending the PMF-Echo Request on this access. 3. The UE and the UPF derive an estimation of the average RTT over an access type and QoS Flow by averaging the RTT measurements obtained over this access type and QoS Flow. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.32.5.2 |
6,084 | 9.5.2.2 TDD | The minimum performance requirement in Table 9.5.2.2-2 is defined as a) The ratio of the throughput obtained when transmitting based on UE reported RI and that obtained when transmitting with fixed rank 1 shall be ≥ ; b) The ratio of the throughput obtained when transmitting based on UE reported RI and that obtained when transmitting with fixed rank 2 shall be ≥ ; For the parameters specified in Table 9.5.2.2-1, and using the downlink physical channels specified in Annex C.3.2, the minimum requirements are specified in Table 9.5.2.2-2. Table 9.5.2.2-1: RI Test (TDD) Table 9.5.2.2-2: Minimum requirement (TDD) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 9.5.2.2 |
6,085 | 6.1.2 Types of ESM procedures | Two types of ESM procedures can be distinguished: 1) Procedures related to EPS bearer contexts: These procedures are initiated by the network and are used for the manipulation of EPS bearer contexts: - default EPS bearer context activation; - dedicated EPS bearer context activation; - EPS bearer context modification; - EPS bearer context deactivation. This procedure is initiated by the network or by the UE and is used for the transport of user data via the control plane: - transport of user data via the control plane procedure. 2) Transaction related procedures: These procedures are initiated by the UE to request for resources, i.e. a new PDN connection or dedicated bearer resources, or to release these resources: - PDN connectivity procedure; - PDN disconnect procedure; - bearer resource allocation procedure; - bearer resource modification procedure. This procedure is initiated by the ProSe UE-to-network relay and is used for the manipulation of EPS bearer contexts: - remote UE report. When combined with the attach procedure, the PDN connectivity procedure can trigger the network to execute the following transaction related procedure: - ESM information request procedure. When combined with the attach procedure, if EMM-REGISTERED without PDN connection is supported by the UE and the network and no PDN connectivity procedure is initiated during the attach procedure, the UE or the network executes the following transaction related procedure: - ESM dummy message procedure. A successful transaction related procedure initiated by the UE triggers the network to execute one of the procedures related to EPS bearer contexts. The UE treats the start of the procedure related to the EPS bearer context as completion of the transaction related procedure. During procedures related to EPS bearer contexts, the MME and the UE shall not initiate the transport of user data via the control plane procedure until the ongoing procedure is completed. NOTE 1: The UE determination of the completion of the transport of user data via the control plane procedure is left to the implementation. NOTE 2: NAS signalling prioritization with respect to the transport of user data via the control plane cannot be guaranteed in the downlink direction in this version of the specification. Except for the remote UE report procedure and ESM information request procedure, during transaction related procedures, the MME and the UE shall not initiate the transport of user data via the control plane procedure until the ongoing procedure is completed. The following ESM procedures can be related to an EPS bearer context or to a procedure transaction: - ESM status procedure; - notification procedure. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.1.2 |
6,086 | 4.2 Functional Split | The gNB and ng-eNB host the following functions: - Functions for Radio Resource Management: Radio Bearer Control, Radio Admission Control, Connection Mobility Control, Dynamic allocation of resources to UEs in uplink, downlink and sidelink (scheduling); - IP and Ethernet header compression, uplink data decompression, encryption and integrity protection of data; - Selection of an AMF at UE attachment when no routing to an AMF can be determined from the information provided by the UE; - Routing of User Plane data towards UPF(s); - Routing of Control Plane information towards AMF; - Connection setup and release; - Scheduling and transmission of paging messages; - Scheduling and transmission of system broadcast information (originated from the AMF or OAM); - Measurement and measurement reporting configuration for mobility and scheduling; - Transport level packet marking in the uplink; - Session Management; - Support of Network Slicing; - QoS Flow management and mapping to data radio bearers; - Support of UEs in RRC_INACTIVE state; - Distribution function for NAS messages; - Radio access network sharing; - Dual Connectivity; - Tight interworking between NR and E-UTRA; - Maintain security and radio configuration for User Plane CIoT 5GS Optimisation, as defined in TS 23.501[ System architecture for the 5G System (5GS) ] [3] (ng-eNB only). NOTE 1: BL UE or UE in enhanced coverage is only supported by ng-eNB, see TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [2]. NOTE 2: NB-IoT UE is only supported by ng-eNB, see TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [2]. The AMF hosts the following main functions (see TS 23.501[ System architecture for the 5G System (5GS) ] [3]): - NAS signalling termination; - NAS signalling security; - AS Security control; - Inter CN node signalling for mobility between 3GPP access networks; - Idle mode UE Reachability (including control and execution of paging retransmission); - Registration Area management; - Support of intra-system and inter-system mobility; - Access Authentication; - Access Authorization including check of roaming rights; - Mobility management control (subscription and policies); - Support of Network Slicing; - SMF selection. - Selection of CIoT 5GS optimisations; The UPF hosts the following main functions (see TS 23.501[ System architecture for the 5G System (5GS) ] [3]): - Anchor point for Intra-/Inter-RAT mobility (when applicable); - External PDU session point of interconnect to Data Network; - Packet routing & forwarding; - Packet inspection and User plane part of Policy rule enforcement; - Traffic usage reporting; - Uplink classifier to support routing traffic flows to a data network; - Branching point to support multi-homed PDU session; - QoS handling for user plane, e.g. packet filtering, gating, UL/DL rate enforcement; - Uplink Traffic verification (SDF to QoS flow mapping); - Downlink packet buffering and downlink data notification triggering. The Session Management function (SMF) hosts the following main functions (see TS 23.501[ System architecture for the 5G System (5GS) ] [3]): - Session Management; - UE IP address allocation and management; - Selection and control of UP function; - Configures traffic steering at UPF to route traffic to proper destination; - Control part of policy enforcement and QoS; - Downlink Data Notification. This is summarized on the figure below where yellow boxes depict the logical nodes and white boxes depict the main functions. Figure 4.2-1: Functional Split between NG-RAN and 5GC | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 4.2 |
6,087 | 6.7.3.2 N2-handover | At handover from a source gNB/ng-eNB to a target gNB/ng-eNB over N2 (possibly including an AMF change and hence a transfer of the UE's 5G security capabilities from the source AMF to the target AMF), the target AMF shall send the UE's 5G security capabilities to the target gNB/ng-eNB in the NGAP HANDOVER REQUEST message (see TS 33.413[ None ] [34]). The target gNB/ng-eNB shall select the algorithm with highest priority from the UE's 5G security capabilities according to the locally configured prioritized list of algorithms (this applies for both integrity and ciphering algorithms). The chosen algorithms shall be indicated to the UE in the Handover Command message if the target gNB/ng-eNB selects different algorithms compared to the source gNB/ng-eNB. If the UE does not receive any selection of integrity and ciphering algorithms, it continues to use the same algorithms as before the handover (see TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [22]). For N2-handover, the source gNB/ng-eNB shall include AS algorithms used in the source cell (ciphering and integrity algorithms) in the source to target transparent container that shall be sent to the target gNB/ng-eNB. The AS algorithms used by the source cell are provided to the target gNB/ng-eNB so that it can use them during the potential RRC Connection Re-establishment procedure use them as specified in clause 6.11 for gNB and TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [10] for ng-eNB. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.7.3.2 |
6,088 | – CSI-RS-ResourceConfigMobility | The IE CSI-RS-ResourceConfigMobility is used to configure CSI-RS based RRM measurements. CSI-RS-ResourceConfigMobility information element -- ASN1START -- TAG-CSI-RS-RESOURCECONFIGMOBILITY-START CSI-RS-ResourceConfigMobility ::= SEQUENCE { subcarrierSpacing SubcarrierSpacing, csi-RS-CellList-Mobility SEQUENCE (SIZE (1..maxNrofCSI-RS-CellsRRM)) OF CSI-RS-CellMobility, ..., [[ refServCellIndex ServCellIndex OPTIONAL -- Need S ]] } CSI-RS-CellMobility ::= SEQUENCE { cellId PhysCellId, csi-rs-MeasurementBW SEQUENCE { nrofPRBs ENUMERATED { size24, size48, size96, size192, size264}, startPRB INTEGER(0..2169) }, density ENUMERATED {d1,d3} OPTIONAL, -- Need R csi-rs-ResourceList-Mobility SEQUENCE (SIZE (1..maxNrofCSI-RS-ResourcesRRM)) OF CSI-RS-Resource-Mobility } CSI-RS-Resource-Mobility ::= SEQUENCE { csi-RS-Index CSI-RS-Index, slotConfig CHOICE { ms4 INTEGER (0..31), ms5 INTEGER (0..39), ms10 INTEGER (0..79), ms20 INTEGER (0..159), ms40 INTEGER (0..319) }, associatedSSB SEQUENCE { ssb-Index SSB-Index, isQuasiColocated BOOLEAN } OPTIONAL, -- Need R frequencyDomainAllocation CHOICE { row1 BIT STRING (SIZE (4)), row2 BIT STRING (SIZE (12)) }, firstOFDMSymbolInTimeDomain INTEGER (0..13), sequenceGenerationConfig INTEGER (0..1023), ..., [[ slotConfig-r17 CHOICE { ms4 INTEGER (0..255), ms5 INTEGER (0..319), ms10 INTEGER (0..639), ms20 INTEGER (0..1279), ms40 INTEGER (0..2559) } OPTIONAL -- Need R ]] } CSI-RS-Index ::= INTEGER (0..maxNrofCSI-RS-ResourcesRRM-1) -- TAG-CSI-RS-RESOURCECONFIGMOBILITY-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
6,089 | 13.2.4.5.2 Modifications by IPX | NOTE 1: It is assumed that operators act as a certification authority for IPX providers they have a direct business relationship with. In order to authorize N32-f message modifications, operators sign a digital certificate for each of these IPX providers and provide it to both the IPX provider itself as well as their roaming partners to enable them to validate any modifications by this IPX provider. Only cIPX and pIPX shall be able to modify messages between cSEPP and pSEPP. In cases of messages from cSEPP to pSEPP, the cIPX is the first intermediary, while the pIPX is the second intermediary. In cases of messages from pSEPP to cSEPP the pIPX is the first intermediary, while the cIPX is the second intermediary. The first intermediary shall parse the encapsulated request (i.e. the clearTextEncapsulationMsg in the dataToIntegrityProtect block) and determine which changes are required. The first intermediary creates an Operations JSON patch document to describe the differences between received and desired message, using the syntax and semantic from RFC 6902 [64], such that, when applying the JSON patch to the encapsulated request the result will be the desired request. If no patch is required, the operations element is null. NOTE 2: It is necessary to create a JWS object even if no patch is required to prevent deletion of modifications. The first intermediary shall create a modifiedDataToIntegrityProtect JSON object as described in clause 13.2.4.5.1. The JSON object shall include the intermediary’s identity and the JWE authentication tag, which associates this update by the intermediary with the JWE object created by the sending SEPP. The first intermediary shall use the modifiedDataToIntegrityProtect JSON object as input to JWS to create a JWS object. The first intermediary shall append the generated JWS object to the payload in the HTTP message and then send the messageto the next hop. The second intermediary shall parse the encapsulated request, apply the modifications described in the JSON patch appended by the first intermediary and determine further modifications required for obtaining the desired request. The second intermediary shall record these modifications in an additional JSON patch against the JSON object resulting from application of the first intermediary's JSON patch. If no patch is required, the operations element for the second JSON patch is null. The second intermediary shall create a modifiedDataToIntegrityProtect JSON object as described in clause 13.2.4.5.1. It shall include its identity and the JWE authentication tag, which associates this update by the second intermediary with the JWE object created by the sending SEPP. The second intermediary shall use the modifiedDataToIntegrityProtect JSON object as input to JWS to create a JWS object. The second intermediary shall append the generated JWS object to the payload in the HTTP message and then send the message to the receiving SEPP. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 13.2.4.5.2 |
6,090 | 6.2.4A.3 A-MPR for CA_NS_03 for CA_1C | If the UE is configured to CA_1C and it receives IE CA_NS_03 the allowed maximum output power reduction applied to transmission on the PCC and the SCC for contiguously aggregated signals is specified in Table 6.2.4A.3-1. Table 6.2.4A.3-1: Contiguous allocation A-MPR for CA_NS_03 If the UE is configured to CA_1C and it receives IE CA_NS_03 the allowed maximum output power reduction applied to transmissions on the PCell and the SCell with non-contiguous resource allocation is defined as follows: A-MPR = CEIL {MA, 0.5} Where MA is defined as follows MA = -23.33A + 17.5 ; 0 ≤ A < 0.15 -7.65A + 15.15 ; 0.15 ≤ A ≤ 1 Where A = NRB_alloc / NRB_agg. | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.2.4A.3 |
6,091 | 5.7 Discontinuous Reception (DRX) | The MAC entity may be configured by RRC with a DRX functionality that controls the UE's PDCCH monitoring activity for the MAC entity's C-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, Semi-Persistent Scheduling C-RNTI (if configured), UL Semi-Persistent Scheduling V-RNTI (if configured), eIMTA-RNTI (if configured), SL-RNTI (if configured), SL-V-RNTI (if configured), CC-RNTI (if configured), SRS-TPC-RNTI (if configured), and AUL C-RNTI (if configured). When in RRC_CONNECTED, if DRX is configured, the MAC entity is allowed to monitor the PDCCH discontinuously using the DRX operation specified in this clause; otherwise the MAC entity monitors the PDCCH continuously. When using DRX operation, the MAC entity shall also monitor PDCCH according to requirements found in other clauses of this specification. RRC controls DRX operation by configuring the timers onDurationTimer, drx-InactivityTimer, drx-RetransmissionTimer (for HARQ processes scheduled using 1ms TTI, one per DL HARQ process except for the broadcast process), drx-RetransmissionTimerShortTTI (for HARQ processes scheduled using short TTI, one per DL HARQ process), drx-ULRetransmissionTimer (for HARQ processes scheduled using 1ms TTI, one per asynchronous UL HARQ process), drx-ULRetransmissionTimerShortTTI (for HARQ processes scheduled using short TTI, one per asynchronous UL HARQ process), the longDRX-Cycle, the value of the drxStartOffset and optionally the drxShortCycleTimer and shortDRX-Cycle. A HARQ RTT timer per DL HARQ process (except for the broadcast process) and UL HARQ RTT Timer per asynchronous UL HARQ process is also defined (see clause 7.7). The HARQ mode per HARQ process can be configured in uplinkHARQ-Mode. When a DRX cycle is configured, the Active Time includes the time while: - onDurationTimer or drx-InactivityTimer or drx-RetransmissionTimer or drx-RetransmissionTimerShortTTI or drx-ULRetransmissionTimer or drx-ULRetransmissionTimerShortTTI or mac-ContentionResolutionTimer (as described in clause 5.1.5) is running; or - a Scheduling Request is sent on PUCCH/SPUCCH and is pending (as described in clause 5.4.4). If this Serving Cell is part of a non-terrestrial network, the Active Time is started after the Scheduling Request transmission that is performed when the SR_COUNTER is 0 for all the SR configurations with pending SR(s) plus the UE-eNB RTT; or - an uplink grant for a pending HARQ retransmission can occur and there is data in the corresponding HARQ buffer for synchronous HARQ process; or - a PDCCH indicating a new transmission addressed to the C-RNTI of the MAC entity has not been received after successful reception of a Random Access Response for the preamble not selected by the MAC entity (as described in clause 5.1.4) ; or - mpdcch-UL-HARQ-ACK-FeedbackConfig is configured and repetitions within a bundle are being transmitted according to UL_REPETITION_NUMBER. If this Serving Cell is part of a non-terrestrial network, the Active Time starts after the first repetition within the bundle plus the UE-eNB RTT when repetitions within the bundle are being transmitted. When DRX is configured, the MAC entity shall for each subframe: - if a HARQ RTT Timer expires in this subframe: - if the data of the corresponding HARQ process was not successfully decoded: - start the drx-RetransmissionTimer or drx-RetransmissionTimerShortTTI for the corresponding HARQ process; - if NB-IoT: - if lower layers had indicated multiple TBs were scheduled for the associated expired HARQ RTT Timer: - start or restart drx-InactivityTimer when all HARQ RTT Timers have expired; - else: - start or restart the drx-InactivityTimer. - if an UL HARQ RTT Timer expires in this subframe: - start the drx-ULRetransmissionTimer or drx-ULRetransmissionTimerShortTTI for the corresponding HARQ process. - if NB-IoT: - if lower layers had indicated multiple TBs were scheduled for the associated expired HARQ RTT Timer: - start or restart drx-InactivityTimer when all HARQ RTT Timers have expired; - else: - start or restart the drx-InactivityTimer. - if a DRX Command MAC control element or a Long DRX Command MAC control element is received: - stop onDurationTimer; - stop drx-InactivityTimer. - if drx-InactivityTimer expires or a DRX Command MAC control element is received in this subframe: - if the Short DRX cycle is configured: - start or restart drxShortCycleTimer; - use the Short DRX Cycle. - else: - use the Long DRX cycle. - if drxShortCycleTimer expires in this subframe: - use the Long DRX cycle. - if a Long DRX Command MAC control element is received: - stop drxShortCycleTimer; - use the Long DRX cycle. - If the Short DRX Cycle is used and [(SFN * 10) + subframe number] modulo (shortDRX-Cycle) = (drxStartOffset) modulo (shortDRX-Cycle); or - if the Long DRX Cycle is used and [(SFN * 10) + subframe number] modulo (longDRX-Cycle) = drxStartOffset: - if NB-IoT: - if there is at least one HARQ process for which neither HARQ RTT Timer nor UL HARQ RTT Timer is running, start onDurationTimer. - else: - start onDurationTimer. - during the Active Time, for a PDCCH-subframe, if the subframe is not required for uplink transmission for half-duplex FDD UE operation, and if the subframe is not a half-duplex guard subframe, as specified in TS 36.211[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation ] [7], and if the subframe is not part of a configured measurement gap and if the subframe is not part of a configured Sidelink Discovery Gap for Reception, and for NB-IoT if the subframe is not required for uplink transmission or downlink reception other than on PDCCH; or - during the Active Time, for a subframe other than a PDCCH-subframe and for a UE capable of simultaneous reception and transmission in the aggregated cells, if the subframe is a downlink subframe indicated by a valid eIMTA L1 signalling for at least one serving cell not configured with schedulingCellId, as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8] and if the subframe is not part of a configured measurement gap and if the subframe is not part of a configured Sidelink Discovery Gap for Reception; or - during the Active Time, for a subframe other than a PDCCH-subframe and for a UE not capable of simultaneous reception and transmission in the aggregated cells, if the subframe is a downlink subframe indicated by a valid eIMTA L1 signalling for the SpCell and if the subframe is not part of a configured measurement gap and if the subframe is not part of a configured Sidelink Discovery Gap for Reception: - monitor the PDCCH; - if the PDCCH indicates a DL transmission or if a DL assignment has been configured for this subframe: - if the UE is an NB-IoT UE, a BL UE or a UE in enhanced coverage: - if the HARQ feedback is disabled by lower layers when downlinkHARQ-FeedbackDisabled is not configured; or - if the HARQ feedback is disabled by downlinkHARQ-FeedbackDisabled for the corresponding HARQ process; or - if the HARQ feedback is enabled by downlinkHARQ-FeedbackDisabled for the corresponding HARQ process and further reversed to disabled by lower layers: - if NB-IoT: - if the UE is configured with a single DL and UL HARQ process; or - if lower layers have indicated scheduling of transmission of multiple TBs and both associated HARQ processes are with disabled HARQ feedback: - start or restart drx-InactivityTimer in the subframe containing the last repetition of the corresponding PDSCH reception + 12 subframes + deltaPDCCH, where deltaPDCCH is the interval starting from the subframe containing the last repetition of the corresponding PDSCH reception plus 12 subframes to the first subframe of the next PDCCH occasion. - else if the HARQ feedback is enabled for the corresponding HARQ process: - if lower layers have indicated scheduling of transmission of multiple TBs: - start the HARQ RTT Timers for all HARQ processes which the HARQ feedback are enabled corresponding to the scheduled TBs in the subframe containing the last repetition of the PDSCH corresponding to the last scheduled TB; - else: - start the HARQ RTT Timer for the corresponding HARQ process in the subframe containing the last repetition of the corresponding PDSCH reception; - else: - start the HARQ RTT Timer for the corresponding HARQ process; - stop the drx-RetransmissionTimer or drx-RetransmissionTimerShortTTI for the corresponding HARQ process. - if NB-IoT, stop drx-ULRetransmissionTimer for all UL HARQ processes. - if the PDCCH indicates an UL transmission for an asynchronous HARQ process or if an UL grant has been configured for an asynchronous HARQ process for this subframe, or if the PDCCH indicates an UL transmission for an autonomous HARQ process or; - if the uplink grant is a configured grant for the MAC entity's AUL C-RNTI and if the corresponding PUSCH transmission has been performed in this subframe: - if mpdcch-UL-HARQ-ACK-FeedbackConfig is not configured; and - if the corresponding HARQ process is not configured with HARQ mode B: - if lower layers have indicated scheduling of transmission of multiple TBs: - start the UL HARQ RTT Timers for all scheduled HARQ processes which are not configured with HARQ mode B in the subframe containing the last repetition of the PUSCH corresponding to the last scheduled TB; - else: - start the UL HARQ RTT Timer for the corresponding HARQ process in the subframe containing the last repetition of the corresponding PUSCH transmission; - stop the drx-ULRetransmissionTimer or drx-ULRetransmissionTimerShortTTI for the corresponding HARQ process; - if mpdcch-UL-HARQ-ACK-FeedbackConfig is configured and an UL HARQ-ACK feedback has not been received on PDCCH until the last repetition of the corresponding PUSCH transmission: - if the corresponding HARQ process is not configured with HARQ mode B: - start or restart the drx-ULRetransmissionTimer for the corresponding HARQ process in the subframe containing the last repetition of the corresponding PUSCH transmission; - if NB-IoT: - if the UE is configured with single UL and DL HARQ process and if the corresponding HARQ process is configured with HARQ mode B; or - if lower layers have indicated scheduling of transmission of multiple TBs and both associated HARQ processes are configured with HARQ mode B: - start or restart drx-InactivityTimer in the subframe containing the last repetition of the corresponding PUSCH transmission + 1 subframe + deltaPDCCH, where deltaPDCCH is the interval starting from the subframe containing the last repetition of the corresponding PUSCH transmission plus 1 subframes to the first subframe of the next PDCCH occasion. - if NB-IoT, stop drx-RetransmissionTimer for all DL HARQ processes. - if the PDCCH indicates a new transmission (DL, UL or SL): - if the UE is an NB-IoT UE: - if the UE is configured with more than one HARQ process and PDCCH indicate the transmission is for a single TB: - start or restart drx-InactivityTimer. - else: - start or restart drx-InactivityTimer. - if the PDCCH indicates a transmission (DL, UL) for an NB-IoT UE: - if the NB-IoT UE is configured with a single DL and UL HARQ process; or - if the PDCCH indicates the transmission is for multiple TBs: - stop drx-InactivityTimer. - stop onDurationTimer. - if the PDCCH indicates an UL HARQ-ACK feedback for an asynchronous UL HARQ process for a UE configured with mpdcch-UL-HARQ-ACK-FeedbackConfig: - if the lower layer had indicated scheduling of transmission of multiple TBs: - stop drx-ULRetransmissionTimer for the corresponding UL HARQ process(es). - else if the PUSCH transmission is completed: - stop drx-ULRetransmissionTimer for all UL HARQ processes. - if the PDCCH indicates HARQ feedback for one or more HARQ processes for which UL HARQ operation is autonomous: - stop the drx-ULRetransmissionTimer for the corresponding HARQ process(es). - in current subframe n, if the MAC entity would not be in Active Time considering grants/assignments/DRX Command MAC control elements/Long DRX Command MAC control elements received and Scheduling Request sent until and including subframe n-5 when evaluating all DRX Active Time conditions as specified in this clause, type-0-triggered SRS, as specified in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [2], shall not be reported. - if CQI masking (cqi-Mask) is setup by upper layers: - in current TTI n, if onDurationTimer would not be running considering grants/assignments/DRX Command MAC control elements/Long DRX Command MAC control elements received until and including TTI n-5 when evaluating all DRX Active Time conditions as specified in this clause, CQI/PMI/RI/PTI/CRI on PUCCH shall not be reported. - else: - in current TTI n, if the MAC entity would not be in Active Time considering grants/assignments/DRX Command MAC control elements/Long DRX Command MAC control elements received and Scheduling Request sent until and including TTI n-5 when evaluating all DRX Active Time conditions as specified in this clause, CQI/PMI/RI/PTI/CRI on PUCCH shall not be reported. For NB-IoT, onDurationTimer may start within a PDCCH period and end within a PDCCH period. The UE shall monitor NPDCCH during these partial PDCCH periods while onDurationTimer is running. Regardless of whether the MAC entity is monitoring PDCCH or not, the MAC entity receives and transmits HARQ feedback and transmits type-1-triggered SRS, as specified in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [2], when such is expected. The MAC entity monitors PDCCH addressed to CC-RNTI for a PUSCH trigger B, as specified in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [2], on the corresponding SCell even if the MAC entity is not in Active Time. when such is expected. When the BL UE or the UE in enhanced coverage or NB-IoT UE receives PDCCH, the UE executes the corresponding action specified in this clause in the subframe following the subframe containing the last repetition of the PDCCH reception where such subframe is determined by the starting subframe and the DCI subframe repetition number field in the PDCCH specified in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [2], unless explicitly stated otherwise. NOTE 1: The same Active Time applies to all activated serving cell(s). NOTE 2: In case of downlink spatial multiplexing, if a TB is received while the HARQ RTT Timer is running and the previous transmission of the same TB was received at least N subframes before the current subframe (where N corresponds to the HARQ RTT Timer), the MAC entity should process it and restart the HARQ RTT Timer. NOTE 3: The MAC entity does not consider PUSCH trigger B, as specified in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [2], to be an indication of a new transmission. NOTE 4: For NB-IoT, for operation in FDD mode, and for operation in TDD mode with a single HARQ process, DL and UL transmissions will not be scheduled in parallel, i.e. if a DL transmission has been scheduled an UL transmission will not be scheduled until HARQ RTT Timer of the DL HARQ process has expired (and vice versa). | 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.7 |
6,092 | 9.3.2.5 Data Forwarding for the User Plane | In case of indirect data forwarding, user plane handling for inter-System data forwarding from 5GS to EPS follows the following key principles: - For the QoS flows accepted for data forwarding, the NG-RAN node initiates data forwarding to the UPF by the corresponding PDU session data forwarding tunnel(s). - The UPF maps forwarded data received from the per PDU session data forwarding tunnel(s) to the mapped EPS bearer(s) removing the QFI. - Handling of end marker packets: - The source NG-RAN node receives one or several end marker packets per PDU session from the UPF. When there are no more data packets to be forwarded for QoS flows mapped to an E-RAB, the source NG-RAN node sends one or several end markers including one QFI (by means of the PDU Session User Plane protocol TS 38.415[ NG-RAN; PDU session user plane protocol ] [30]) of those QoS flows mapped to that E-RAB and sends the end marker packets to the UPF over the PDU session tunnel. From the included QFI in the end markers and its mapping to an EPS bearer ID, the UPF knows which EPS bearer tunnel it needs to forward the end-markers to the SGW. The QFI is removed in the end marker packets sent to the SGW. In case of direct data forwarding, user plane handling for inter-System data forwarding from 5GS to EPS follows the following key principles: - For the QoS flows accepted for data forwarding, the source NG-RAN node maps data received from the NG-U PDU session tunnel to the respective E-RAB data forwarding tunnel and forwards each user packet as PDCP SDU without PDCP SN and QFI information. - The source NG-RAN node receives one or several GTP-U end marker packets per PDU session from the UPF and replicates the end marker packets into each E-RAB data forwarding tunnel when no more user data packets are to be forwarded over that tunnel. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 9.3.2.5 |
6,093 | 4.4.2.3 Establishment of secure exchange of NAS messages | Secure exchange of NAS messages via a NAS signalling connection is usually established by the MME during the attach procedure by initiating a security mode control procedure. After successful completion of the security mode control procedure, all NAS messages exchanged between the UE and the MME are sent integrity protected using the current EPS security algorithms, and except for the messages specified in clause 4.4.5, all NAS messages exchanged between the UE and the MME are sent ciphered using the current EPS security algorithms. During inter-system handover from A/Gb mode to S1 mode or Iu mode to S1 mode, secure exchange of NAS messages is established between the MME and the UE by: - the transmission of NAS security related parameters encapsulated in the AS signalling from the MME to the UE triggering the inter-system handover (see 3GPP TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [19]). The UE uses these parameters to generate the mapped EPS security context; and, - after the handover, the transmission of a TRACKING AREA UPDATE REQUEST message from the UE to the MME. The UE shall send this message integrity protected using the mapped EPS security context, but unciphered. From this time onward, all NAS messages exchanged between the UE and the MME are sent integrity protected using the mapped EPS security context, and except for the messages specified in clause , all NAS messages exchanged between the UE and the MME are sent ciphered using the mapped EPS security context. During inter-system change from N1 mode to S1 mode in EMM-CONNECTED mode, secure exchange of NAS messages is established between the MME and the UE by: - the transmission of NAS security related parameters encapsulated in the AS signalling from the AMF to the UE triggering the inter-system handover (see 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [56]). The UE uses these parameters to generate the mapped EPS security context (see clause 8.6.1 of 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [56]); and - after the handover, the transmission of a TRACKING AREA UPDATE REQUEST message from the UE to the MME. The UE shall send this message integrity protected using the mapped EPS security context, but unciphered. From this time onward, all NAS messages exchanged between the UE and the MME are sent integrity protected using the mapped EPS security context, and except for the messages specified in clause 4.4.5, all NAS messages exchanged between the UE and the MME are sent ciphered using the mapped EPS security context. During inter-system change from N1 mode to S1 mode in EMM-IDLE mode, if the UE is operating in the single-registration mode and: 1) if the tracking area updating procedure is initiated as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54], the UE shall transmit a TRACKING AREA UPDATE REQUEST message integrity protected with the current 5G NAS security context and the UE shall derive a mapped EPS security context (see clause 8.6.1 of 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [56]). The UE shall set the uplink and downlink NAS COUNT counters to the uplink and downlink NAS COUNT counters of the current 5G NAS security context respectively. The UE shall include the eKSI indicating the 5G NAS security context value in the TRACKING AREA UPDATE REQUEST message. After receiving the TRACKING AREA UPDATE REQUEST message including the eKSI, the MME forwards the TRACKING AREA UPDATE REQUEST message to the source AMF, if possible, to obtain the mapped EPS security context from the AMF as specified in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [56]. The MME shall store the mapped EPS NAS security context with the uplink and downlink NAS COUNT counters associated with the derived K'ASME key set to the uplink and downlink NAS COUNT counters of the mapped EPS NAS security context respectively. The MME re-establishes the secure exchange of NAS messages by either: - replying with a TRACKING AREA UPDATE ACCEPT message that is integrity protected and ciphered using the mapped EPS security context. From this time onward, all NAS messages exchanged between the UE and the MME are sent integrity protected and except for the messages specified in clause 4.4.5, all NAS messages exchanged between the UE and the MME are sent ciphered; or - initiating a security mode control procedure. This can be used by the MME to take a non-current EPS security context into use or to modify the current EPS security context by selecting new NAS security algorithms; or 2) if the attach procedure is initiated as specified in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54] and: a) if the UE has received an "interworking without N26 interface not supported" indication from the network and the UE has a valid 5G NAS security context, the UE shall send an ATTACH REQUEST message integrity protected with the current 5G NAS security context and the UE shall derive a mapped EPS security context (see clause 8.6.1 of 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [56]). The UE shall set the uplink and downlink NAS COUNT counters to the uplink and downlink NAS COUNT counters of the current 5G NAS security context respectively. The UE shall include the eKSI indicating the 5G NAS security context value in the ATTACH REQUEST message. After receiving the ATTACH REQUEST message including the eKSI, the MME forwards the ATTACH REQUEST message to the source AMF, if possible, to obtain the mapped EPS security context from the AMF as specified in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [56]. The MME shall store the mapped EPS NAS security context with the uplink and downlink NAS COUNT counters associated with the derived K'ASME key set to the uplink and downlink NAS COUNT counters of the mapped EPS NAS security context respectively. The MME re-establishes the secure exchange of NAS messages by either: - replying with an ATTACH ACCEPT message that is integrity protected and ciphered using the mapped EPS NAS security context. From this time onward, all NAS messages exchanged between the UE and the MME are sent integrity protected and except for the messages specified in clause 4.4.5, all NAS messages exchanged between the UE and the MME are sent ciphered; or - initiating a security mode control procedure. This can be used by the MME to modify the current EPS security context by selecting new NAS security algorithms; or b) otherwise: i) if the UE has a valid native EPS security context, the UE shall send an ATTACH REQUEST message integrity protected with the native EPS security context. The UE shall include the eKSI indicating the native EPS security context value in the ATTACH REQUEST message. After receiving the ATTACH REQUEST message including the eKSI, the MME shall check whether the eKSI included in the initial NAS message belongs to an EPS security context available in the MME, and shall verify the MAC of the NAS message. If the verification is successful, the MME re-establishes the secure exchange of NAS messages by either: - replying with an ATTACH ACCEPT message that is integrity protected and ciphered using the current EPS security context. From this time onward, all NAS messages exchanged between the UE and the MME are sent integrity protected and except for the messages specified in clause , all NAS messages exchanged between the UE and the MME are sent ciphered; or - initiating a security mode control procedure. This can be used by the MME to modify the current EPS security context by selecting new NAS security algorithms; or ii) if the UE has no valid native EPS security context, the UE shall send an ATTACH REQUEST message without integrity protection and encryption. The secure exchange of NAS messages shall be continued after S1 mode to S1 mode handover. It is terminated after inter-system handover from S1 mode to A/Gb mode or Iu mode or when the NAS signalling connection is released. When a UE in EMM-IDLE mode establishes a new NAS signalling connection and has a valid current EPS security context, secure exchange of NAS messages can be re-established in the following ways: 1) Except for the cases described in items 3 and 4 below, the UE shall transmit the initial NAS message integrity protected with the current EPS security context, but unciphered. The UE shall include the eKSI indicating the current EPS security context value in the initial NAS message. The MME shall check whether the eKSI included in the initial NAS message belongs to an EPS security context available in the MME, and shall verify the MAC of the NAS message. If the verification is successful, the MME may re-establish the secure exchange of NAS messages: - by replying with a NAS message that is integrity protected and ciphered using the current EPS security context. From this time onward, all NAS messages exchanged between the UE and the MME are sent integrity protected and except for the messages specified in clause , all NAS messages exchanged between the UE and the MME are sent ciphered; or - by initiating a security mode control procedure. This can be used by the MME to take a non-current EPS security context into use or to modify the current EPS security context by selecting new NAS security algorithms; or 2) If the initial NAS message was a SERVICE REQUEST message or EXTENDED SERVICE REQUEST message, secure exchange of NAS messages is triggered by the indication from the lower layers that the user plane radio bearers are successfully set up. After successful completion of the procedure, all NAS messages exchanged between the UE and the MME are sent integrity protected and except for the messages specified in clause , all NAS messages exchanged between the UE and the MME are sent ciphered. 3) If the UE has no current EPS security context and performs a tracking area updating procedure after an inter-system change in idle mode from A/Gb mode to S1 mode or Iu mode to S1 mode, the UE shall send the TRACKING AREA UPDATE REQUEST message without integrity protection and encryption. The UE shall include a nonce and a GPRS ciphering key sequence number for creation of a mapped EPS security context. The MME creates a fresh mapped EPS security context and takes this context into use by initiating a security mode control procedure and this context becomes the current EPS security context in both the UE and the MME. This re-establishes the secure exchange of NAS messages. 4) If the initial NAS message is a CONTROL PLANE SERVICE REQUEST message, the UE shall send the message integrity protected. If an ESM message container information element or a NAS message container information element is included the message shall be sent partially ciphered (see clause 4.4.5), otherwise the message shall be sent unciphered. Secure exchange of NAS messages is re-established in the UE: - by the indication from the lower layers that the user plane radio bearers are successfully set up; - upon receipt of a NAS message (e.g. a SERVICE ACCEPT message or ESM DATA TRANSPORT message) that is integrity protected and ciphered using the current EPS security context; or - upon receipt of a SECURITY MODE COMMAND message that has successfully passed the integrity check. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.4.2.3 |
6,094 | 5.3.3.8 Abortion of RRC connection establishment | If upper layers abort the RRC connection establishment procedure, due to a NAS procedure being aborted as specified in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [23], while the UE has not yet entered RRC_CONNECTED, the UE shall: 1> stop timer T300, if running; 1> reset MAC, release the MAC configuration and re-establish RLC for all RBs that are established (except broadcast MRBs). The L2 U2N Relay UE either indicates to upper layers (to trigger PC5 unicast link release) or sends NotificationMessageSidelink message to the connected L2 U2N Remote UE(s) in accordance with 5.8.9.10. The L2 U2N Remote UE indicates to upper layers to trigger PC5 unicast link release with its connected L2 U2N Relay UE. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.3.8 |
6,095 | 4.3.1.6.1 Attempted preparations of outgoing handovers to the cells outside the RN | This measurement provides the number of attempted preparations of outgoing handovers to the cells outside the RN. CC. Transmission of the X2AP message HANDOVER REQUEST by the RN to the DeNB (see TS 36.423[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 Application Protocol (X2AP) ] [10]), indicating the attempt of an outgoing handover preparation to the cells outside the RN. A single integer value. HO.OutRNOutPrepAtt EUtranCellFDD EUtranCellTDD Valid for packet switched traffic EPS | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.3.1.6.1 |
6,096 | 7.3.1 Procedure transaction identity | The following network procedures shall apply for handling an unknown, erroneous, or unforeseen PTI received in an ESM message: a) If the network receives a PDN CONNECTIVITY REQUEST message with an unassigned or reserved PTI value, the network shall respond with a PDN CONNECTIVITY REJECT message including ESM cause #81 "invalid PTI value". b) If the network receives a PDN DISCONNECT REQUEST message with an unassigned or reserved PTI value, the network shall respond with a PDN DISCONNECT REJECT message including ESM cause #81 "invalid PTI value". c) If the network receives a BEARER RESOURCE ALLOCATION REQUEST message with an unassigned or reserved PTI value, the network shall respond with a BEARER RESOURCE ALLOCATION REJECT message including ESM cause #81 "invalid PTI value". d) If the network receives a BEARER RESOURCE MODIFICATION REQUEST message with an unassigned or reserved PTI value, the network shall respond with a BEARER RESOURCE MODIFICATION REJECT message including ESM cause #81 "invalid PTI value". e) If the network receives an ESM INFORMATION RESPONSE message which includes an unassigned or reserved PTI value, the network shall ignore the message. If the PTI is an assigned value that does not match the PTI in use for any ongoing transaction related procedure, the network shall respond with an ESM STATUS message including ESM cause #81 "invalid PTI value". f) If the network receives an ESM message other than those listed in items a through e above with a reserved PTI value, the network shall ignore the message. The following UE procedures shall apply for handling an unknown, erroneous, or unforeseen PTI received in an ESM message: a) If the UE receives a PDN CONNECTIVITY REJECT message in which the PTI value is an unassigned or reserved value, or an assigned value that does not match any PTI in use, the UE shall ignore the message. b) If the UE receives a PDN DISCONNECT REJECT message in which the PTI value is an unassigned or reserved value, or an assigned value that does not match any PTI in use, the UE shall ignore the message. c) If the UE receives a BEARER RESOURCE ALLOCATION REJECT message in which the PTI value is an unassigned or reserved value, or an assigned value that does not match any PTI in use, the UE shall ignore the message. d) If the UE receives a BEARER RESOURCE MODIFICATION REJECT message in which the PTI value is an unassigned or reserved value, or an assigned value that does not match any PTI in use, the UE shall ignore the message. e) If the UE receives an ESM INFORMATION REQUEST message in which the PTI value is an unassigned or reserved value, the UE shall ignore the message. If the PTI is an assigned value that does not match a PTI in use for a pending UE requested PDN connectivity procedure for which the ESM information transfer flag was set in the PDN CONNECTIVITY REQUEST message, the UE shall respond with an ESM STATUS message including ESM cause #47 "PTI mismatch". f) If the UE receives a NOTIFICATION message in which the PTI value is an unassigned value, the UE shall proceed as specified in clause 7.3.2. If the PTI is a reserved value, the UE shall respond with an ESM STATUS message including ESM cause #81 "invalid PTI value". If the PTI is an assigned value that does not match any PTI in use, the UE shall respond with an ESM STATUS message including ESM cause #47 "PTI mismatch". g) If the UE receives an ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message in which the PTI value is an assigned value that does not match any PTI in use, if the UE detects that this request is a network retransmission of an already accepted request (see clause 6.5.1.3) the UE shall respond with an ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT message. Otherwise, the UE shall respond with an ACTIVATE DEFAULT EPS BEARER CONTEXT REJECT message including ESM cause #47 "PTI mismatch". h) If the UE receives an ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message which contains a reserved or unassigned PTI value, the UE shall respond with an ACTIVATE DEFAULT EPS BEARER CONTEXT REJECT message including ESM cause #81 "invalid PTI value". i) If the UE receives an ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message in which the PTI value is an assigned value that does not match any PTI in use, if the UE detects that this request is a network retransmission of an already accepted request (see clauses 6.5.3.3 and 6.5.4.3) the UE shall respond with an ACTIVATE DEDICATED EPS BEARER CONTEXT ACCEPT message. Otherwise, the UE shall respond with an ACTIVATE DEDICATED EPS BEARER CONTEXT REJECT message including ESM cause #47 "PTI mismatch". j) If the UE receives an ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message which contains a reserved PTI value, the UE shall respond with an ACTIVATE DEDICATED EPS BEARER CONTEXT REJECT message including ESM cause #81 "invalid PTI value". k) If the UE receives a MODIFY EPS BEARER CONTEXT REQUEST message in which the PTI value is an assigned value that does not match any PTI in use, if the UE detects that this request is a network retransmission of an already accepted request (see clauses 6.5.3.3 and 6.5.4.3) the UE shall respond with a MODIFY EPS BEARER CONTEXT ACCEPT message. Otherwise, the UE shall respond with a MODIFY EPS BEARER CONTEXT REJECT message including ESM cause #47 "PTI mismatch". l) If the UE receives a MODIFY EPS BEARER CONTEXT REQUEST message which contains a reserved PTI value, the UE shall respond with a MODIFY EPS BEARER CONTEXT REJECT message including ESM cause #81 "invalid PTI value". m) If the UE receives a DEACTIVATE EPS BEARER CONTEXT REQUEST message in which the PTI value is a reserved value or an assigned value that does not match any PTI in use, the UE shall ignore the message. n) If the UE receives an ESM message other than those listed in items a through m with a reserved PTI value or an assigned value that does not match any PTI in use, the UE shall ignore the message. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 7.3.1 |
6,097 | – CommonLocationInfo | The IE CommonLocationInfo is used to transfer detailed location information available at the UE to correlate measurements and UE position information. CommonLocationInfo information element -- ASN1START -- TAG-COMMONLOCATIONINFO-START CommonLocationInfo-r16 ::= SEQUENCE { gnss-TOD-msec-r16 OCTET STRING OPTIONAL, locationTimestamp-r16 OCTET STRING OPTIONAL, locationCoordinate-r16 OCTET STRING OPTIONAL, locationError-r16 OCTET STRING OPTIONAL, locationSource-r16 OCTET STRING OPTIONAL, velocityEstimate-r16 OCTET STRING OPTIONAL } -- TAG-COMMONLOCATIONINFO-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
6,098 | 4.16.1.12 Number of SN terminated bearers Path Update at Secondary Node Additions | a) This measurement provides the number of SN terminated bearers Path Update at Secondary Node Additions. b) CC c) On transmission by the MN of an E-RAB modification indication message to MME at Secondary Node Additions with SN terminated bearers. Each SN terminated bearers to path update is added to the relevant measurement. SGNB Addition Trigger Indication (TS 36.423[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 Application Protocol (X2AP) ] [10]) excludes SN change, inter-eNB HO, intra-eNB HO. d) Each measurement is an integer value. e) The measurement name has the form ERAB.PathUpdateAttAtSNAddition. 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.12 |
6,099 | 4.2.11.4 Number of PDU Sessions per network slice availability check and update procedure | This clause applies to Non-Hierarchical NSAC and centralized NSAC architectures. The difference between the two architectures for the various steps, where applicable, is described at the end of the clause. The number of PDU Sessions per network slice availability check and update procedure is to update (i.e. increase or decrease) the number of PDU Sessions established on S-NSSAI which is subject to NSAC. The SMF is configured with the information indicating which network slice is subject to NSAC. NOTE 1: EAC mode is not applicable for Number of PDU Sessions per network slice availability check and update procedure. Figure 4.2.11.4-1: Number of PDU Sessions per network slice availability check and update procedure 1. If the SMF is not aware of which NSACF to communicate, the SMF performs NSACF discovery as described in clause 6.3.22 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] and in clause 5.2.7.3.2. The SMF anchoring the PDU session triggers the Number of PDU Sessions per network slice availability check and update procedure for the network slices that are subject to NSAC at the beginning of a PDU Session Establishment procedure (clause 4.3.2.2.1 and clause 4.3.2.2.2) only for new PDU Sessions to be established and as a last step of successful PDU Session Release procedure (clause 4.3.4.2 and clause 4.3.4.3). NOTE 2: SMFs handling PDU sessions associated with UE Request Type "Existing PDU Session" for intra access handover purposes do not interact with the NSACF. 2. The SMF anchoring the PDU session sends Nnsacf_NSAC_NumOfPDUsUpdate_Request message to the NSACF. The SMF includes in the message the UE-ID, the PDU session ID, S-NSSAI for which the number of PDU Sessions per network slice update is required, Access Type and the update flag. The update flag may include one of the following values: - 'increase' which indicates that the number of PDUs established on the S-NSSAI is to be increased when the procedure is triggered at the beginning of PDU Session Establishment procedure or when a new user plane leg is to be established for an MA PDU Session; - 'decrease' which indicates that the number of PDU Sessions on the S-NSSAI is to be decreased when the procedure is triggered at the end of PDU Sessions Release procedure or when an existing user plane leg is to be released for an MA PDU Session. In the case of a PDU Session Establishment failure, the anchor SMF triggers another request to the NSACF with the update flag parameter equal to decrease in order to re-adjust back the PDU Session counter in the NSACF; or - 'update' which indicates that for existing PDU Session the Access Type is to be replaced with a new Access Type during inter access mobility. NOTE 3: For SSC mode 3 PDU session, the SMF of the new PDU Session invokes the NSACF to increase the number of PDU Session and adds the new PDU session ID in the NSACF. When the old PDU session is released the SMF of the old PDU session invokes the NSACF to decrease the number of PDU Session and remove the old PDU session ID in the NSACF. NOTE 4: An SMF anchoring an IPv6 Multi-homed PDU session does not invoke NSACF for an S-NSSAI subject to NSAC when the PDU session replaces an existing anchor according to clause 4.3.5.3. 3. The NSACF updates the current number of PDU Sessions established on the S-NSSAI, i.e. increase or decrease the number of PDU Sessions per network slice based on the information provided by the anchor SMF in the update flag parameter. If the update flag parameter from the SMF anchoring the PDU session indicates increase value and the maximum number of PDU Sessions established on the S-NSSAI has already been reached, then the NSACF returns a result parameter indicating that the maximum number of PDU Sessions per network slice has been reached. If the maximum number of PDU Sessions established on the S-NSSAI has not been reached, the NSACF checks the UE ID. If the UE ID is located, the NSACF, stores the PDU Session ID and the Access Type and increases the number of PDU Sessions for that S-NSSAI. If the NSACF did not locate the UE ID, it creates an entry for the UE ID, stores the PDU Session ID and Access Type and increases the number of PDU Sessions for that S-NSSAI. If the update flag parameter from the SMF anchoring the PDU session indicates decrease value, the current number of PDU Sessions per S-NSSAI, the NSACF locates the UE ID and decreases the number of PDU Sessions for that S-NSSAI and removes the related PDU Session ID entry. If the UE ID has no more PDU sessions, after the decrease, the NSACF removes the UE ID entry. If the update flag parameter from the SMF anchoring the PDU session indicates update value, the NSACF locates the existing entry with UE ID and PDU Session ID and replaces the Access Type in the existing entry. The NSACF takes the Access Type parameter into account for increasing and decreasing the number of PDU Sessions per S-NSSAI as described in clause 5.15.11.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. For MA PDU Session, if the SMF received information that the UE is registered over both accesses, the SMF provides multiple Access Types to the NSACF. If the NSACF receives a request containing multiple Access Types, the NSACF provides a Result indication for each Access Type. 4. The NSACF acknowledges the update to the anchor SMF with Nnsacf_NSAC_NumOfPDUsUpdate_Response message including a Result indication. If the NSACF returns a Result indication including 'maximum number of PDU Sessions per S-NSSAI reached', the SMF rejects the PDU Session establishment request with reject cause set to 'maximum number of PDU Sessions per S-NSSAI reached' and optionally a back-off timer and the Access Type. For MA PDU Session Establishment, the NSACF may accept the MA PDU Session and may provide to the SMF a Result indicating 'maximum number of PDU Sessions per S-NSSAI reached' or 'maximum number of PDU Sessions per S-NSSAI not reached' associated with an Access Type. If the NSACF indicates a failure that is associated with the Access Type over which the UE sent the MA PDU Session Establishment Request, the SMF sends to the UE a PDU Session Establishment Reject with a Result indication including 'maximum number of PDU Sessions per S-NSSAI reached' ,optionally a back-off timer and the Access Type. When the SMF rejects the MA PDU Session, the SMF sets the Access Type parameter as follows: - If the UE is registered via both accesses and: - If the NSACF indicates failure for both accesses, the Access Type indicates both accesses; - If the NSACF indicates failure for the access over which the MA PDU Session Establishment Request is received, the Access Type indicates the access over which the MA PDU Session Request is received. NOTE 5: If the UE is registered in both accesses and the NSACF indicates failure for the access different from the access over which the MA PDU Session Establishment Request is received, the SMF accepts the MA PDU Session Request and does not provide back-off timer to the UE. - If the UE is registered via a single access, the Access Type indicates the access over which the MA PDU Session Request is received. - For MA PDU Session Release over single Access Type, the NSACF locates the existing entry with PDU Session ID and if founds the entry with both Access Type then it removes only the received Access Type entry while keeping the PDU Session ID. For a centralized architecture the following differences apply: - In step 2, the SMF additionally includes the NSAC service area the SMF belongs to, if available, as an additional parameter in the Nnsacf_NSAC_NumOfPDUsUpdate_Request. - In step 3, based on operator configuration, the NSACF performs the validation against the maximum number of PDU Sessions established on the S-NSSAI per NSAC service area, if applicable and available, or maximum number of PDU Sessions established on the S-NSSAI in the entire PLMN. Additionally the NSACF stores the NSAC service area of SMF if available. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.2.11.4 |
6,100 | 4.19 5GS mobility management in WB-N1 mode for IoT | In WB-N1 mode, a UE operating in category CE can operate in either CE mode A or CE mode B (see 3GPP TS 36.306[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio access capabilities ] [25D]). If a UE that supports CE mode B and operates in WB-N1 mode, the UE's usage setting is not set to "voice centric" (see 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8]), and: a) the use of enhanced coverage is not restricted by the network; or b) CE mode B is not restricted by the network (see 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8]); the UE shall apply the value of the applicable NAS timer indicated in table 10.2.1 for WB-N1/CE mode. A UE that supports CE mode B and operates in WB-N1 mode shall not apply the value of the applicable NAS timer indicated in table 10.2.1 for WB-N1/CE mode before receiving an indication from the network that the use of enhanced coverage is not restricted, or CE mode B is not restricted, as described in this subclause. The NAS timer value obtained is used as described in the appropriate procedure subclause of this specification. The NAS timer value shall be calculated at start of a NAS procedure, and shall not be re-calculated until the NAS procedure is completed, restarted or aborted. The support of CE mode B by a UE is indicated to the AMF by lower layers and shall be stored by the AMF. When an AMF that supports WB-N1 mode performs NAS signalling with a UE, which supports CE mode B and operates in WB-N1 mode, the UE's usage setting is not set to "voice centric" (see 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8]) and the AMF determines that: a) the use of enhanced coverage is not restricted for the UE; or b) CE mode B is not restricted for the UE (see 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8]); the AMF shall calculate the value of the applicable NAS timer indicated in table 10.2.2 for WB-N1/CE mode. The NAS timer value obtained is used as described in the appropriate procedure subclause of this specification. The NAS timer value shall be calculated at start of a NAS procedure and shall not be re-calculated until the NAS procedure is completed, restarted or aborted. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.19 |
Subsets and Splits
No saved queries yet
Save your SQL queries to embed, download, and access them later. Queries will appear here once saved.