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
⌀ |
|---|---|---|---|---|---|---|---|
5,001 | 5.31.2 Preferred and Supported Network Behaviour | At registration, a UE includes its 5G Preferred Network Behaviour indicating the network behaviour the UE can support and what it would prefer to use. NOTE: If the UE supports S1-mode then the UE will indicate the supported EPS Network Behaviour Information in the S1 UE network capability IE. The 5G Preferred Network Behaviour signalled by the UE includes the following information in the 5GMM Capability IE: - Whether Control Plane CIoT 5GS Optimisation is supported. - Whether User Plane CIoT 5GS Optimisation is supported. - Whether N3 data transfer is supported. - Whether header compression for Control Plane CIoT 5GS Optimisation is supported. And the following 5G Preferred Network Behaviour in other IEs: - Whether Control Plane CIoT 5GS Optimisation or User Plane CIoT 5GS Optimisation is preferred. If N3 data transfer is supported is indicated by the UE, the UE supports data transfer that is not subject to CIoT 5GS Optimisations. If the UE indicates support of User Plane CIoT 5GS Optimisation then it shall also indicate support of N3 data transfer. The AMF indicates the network behaviour the network accepts in the 5G Supported Network Behaviour information. This indication is per Registered Area. The AMF may indicate one or more of the following: - Whether Control Plane CIoT 5GS Optimisation is supported. - Whether User Plane CIoT 5GS Optimisation is supported. - Whether N3 data transfer is supported. - Whether header compression for Control Plane CIoT 5GS Optimisation is supported. If the AMF indicates support of User Plane CIoT 5GS Optimisation then it shall also indicate support of N3 data transfer. If the UE and AMF indicate support for User Plane CIoT 5GS Optimisation, the AMF indicates support of User Plane CIoT 5GS Optimisation support for the UE to NG-RAN. For NB-IoT UEs that only support Control Plane CIoT 5GS Optimisation, the AMF shall include support for Control Plane CIoT 5GS Optimisation in the Registration Accept message. A UE that supports the NB-IoT shall always indicate support for Control Plane CIoT 5GS Optimisation. A UE that supports WB-E-UTRA shall always indicate support for N3 data transfer. The 5G Preferred Network Behaviour indication from the UE may be used to influence policy decisions that can cause rerouting of the Registration Request from an AMF to another AMF. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.31.2 |
5,002 | 8.111 Overload Control Information | Overload Control Information is a grouped IE containing a number of other IEs. Which of those IEs are mandatory, optional or conditional and the conditions that apply are GTP message specific, and described in the corresponding clause under clause 7. Overload Control Information may be repeated within a message with exactly the same Type and Instance values to represent a list of Overload Control Information. Overload Control Information is coded as depicted in Table 8.111-1. Table 8.111-1: Overload Control Information Grouped Type | 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.111 |
5,003 | 6.41.2.7 Returning to Home Network | The 5G system shall provide mechanisms to mitigate user plane and control plane overload caused by a high number of UEs returning from a temporary local access of a hosting network to their home network in a very short period of time. The 5G system shall provide mechanisms to minimize the impact on the UEs communication e.g., to prevent user plane and control plane outages when returning to a home network together with other high number of UEs in a very short period of time, after terminating their temporary local access to a hosting network. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.41.2.7 |
5,004 | 10.9.1 EN-DC | The eNB to Master Node change procedure is used to transfer context data from a source eNB to a target MN that adds an SN during the handover. Figure 10.9.1-1: eNB to Master Node change Figure 10.9.1-1 shows an example signaling flow for eNB to Master Node change: 1. The source eNB starts the handover procedure by initiating the X2 Handover Preparation procedure. 2. The target MN sends SgNB Addition Request to the target SN. 3. The target SN replies with SgNB Addition Request Acknowledge. If data forwarding is needed, the target SN provides forwarding addresses to the target MN. NOTE 0: Void. 4. The target MN includes within the Handover Request Acknowledge message a transparent container to be sent to the UE as an E-UTRA RRC message, including a NR RRC configuration message which also includes the SCG configuration, to perform the handover, and may also provide forwarding addresses to the source eNB. 5. The source eNB triggers the UE to apply the new configuration. 6/7. The UE synchronizes to the target MN and replies with RRCConnectionReconfigurationComplete message. 8. If configured with bearers requiring SCG radio resources, the UE synchronizes to the target SN. NOTE 0: The order the UE performs Random Access towards the target MN (step 6) and performs the Random Access procedure towards the target SN (step 8) is not defined. 9. If the RRC connection reconfiguration procedure was successful, the target MN informs the target SN. 10. For bearers using RLC AM, the source eNB sends the SN Status Transfer message, which the target MN forwards then to the target SN, if needed. 11. Data forwarding from the source eNB takes place. 12-15. The target MN initiates the S1 Path Switch procedure. NOTE 1: If new UL TEIDs of the S-GW are included, the target MN performs MN initiated SN Modification procedure to provide them to the target SN. 16. The target MN initiates the UE Context Release procedure towards the source eNB. NOTE 2: Void. NOTE 3: Void. | 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.9.1 |
5,005 | 4.15.6.3f Application-Specific Expected UE Behaviour parameters | The Application-Specific Expected UE Behaviour parameters characterise the foreseen behaviour of a UE for a specific application. When AF provisions the Application-Specific Expected UE Behaviour parameters, the AF shall provide application traffic descriptors (i.e. the corresponding Packet Filters or Application ID). Each parameter within the Application-Specific Expected UE Behaviour shall have an associated validity time and may have a confidence and/or accuracy level associated with it as defined in the clause 4.15.6.2 and clause 4.15.6.3. Table 4.15.6.3f-1: Description of Application-Specific Expected UE Behaviour parameters | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.15.6.3f |
5,006 | 4.12.2 Registration via Untrusted non-3GPP Access 4.12.2.1 General | Clause 4.12.2 specifies how a UE can register to 5GC via an untrusted non-3GPP Access Network. It is based on the Registration procedure specified in clause 4.2.2.2.2 and it uses a vendor-specific EAP method called "EAP-5G". The EAP-5G packets utilize the "Expanded" EAP type and the existing 3GPP Vendor-Id registered with IANA under the SMI Private Enterprise Code registry. The "EAP-5G" method is used between the UE and the N3IWF and is utilized only for encapsulating NAS messages (not for authentication). If the UE needs to be authenticated, mutual authentication is executed between the UE and AUSF. The details of the authentication procedure are specified in TS 33.501[ Security architecture and procedures for 5G System ] [15]. In Registration and subsequent Registration procedures via untrusted non-3GPP access, the NAS messages are always exchanged between the UE and the AMF. When possible, the UE can be authenticated by reusing the existing UE security context in AMF. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.12.2 |
5,007 | 9 Message Screening | Screening functions reside within the Packet Domain as described in 3GPP TS 22.060[ General Packet Radio Service (GPRS); Service description; Stage 1 ] [2], 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [3], 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [77] and 3GPP TS 23.402[ Architecture enhancements for non-3GPP accesses ] [78]. Screening may be applicable for only certain protocols. Screening is outside the scope of the present document. | 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 | 9 |
5,008 | C.2.4 Location of types II and III information | Type II information is included in the bearer capability information element. Type III information is also included in the bearer capability information element. The network may use and modify type III information (e.g. to provide interworking). In any case a modification of the bearer capability information element has to be performed when interworking to the fixed network (e.g. ISDN) is required, where the signalling of the radio interface has to be mapped to fixed network signalling (e.g. mapping of GSM BCIE to ISDN BCIE, see 3GPP TS 29.007[ General requirements on interworking between the Public Land Mobile Network (PLMN) and the Integrated Services Digital Network (ISDN) or Public Switched Telephone Network (PSTN) ] [38]). | 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 | C.2.4 |
5,009 | 12.3.9 Message throttling 12.3.9.1 General | As part of the overload mitigation, a GTP-C entity shall reduce the total number of messages, which would have been sent otherwise, towards the overloaded peer based on the information received within the Overload Control Information. This shall be achieved by discarding a fraction of the messages in proportion to the overload level of the target peer. This is called message throttling. Message throttling shall only apply to initial messages. Triggered request or response messages should not be throttled since that would result in the retransmission of the corresponding request message by the sender. Before piggybacking the initial message over a response message, the initial message should be subject to the message throttling in the similar manner as any other non-piggybacked initial message. If the node decides to throttle this initial message then the response message should be sent without any piggyback message. A GTP-C entity supporting GTP-C overload control shall support and use the "Loss" algorithm as specified in this clause, for message throttling. | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 12.3.9 |
5,010 | 19.3.8 Keyname NAI | The keyname NAI shall take the form of an NAI, and shall have the form username@realm as specified in clause 2.1 of IETF RFC 4282 [53]. The username part is the EMSK name as defined in IETF RFC 6696 [113]. For ERP exchange with an ER server located in the 3GPP AAA Server, the realm part of the keyname NAI shall be the realm part of the Root NAI of the UE as described in clause 19.3.2, i.e. the realm part of the keyName-NAI will be in the form: "@nai.epc.mnc<MNC>.mcc<MCC>.3gppnetwork.org" For ERP exchange with an ER server located in the TWAP or in the 3GPP AAA Proxy, the realm part of the keyname NAI shall be the realm discovered by the UE in the non-3GPP access network (received at the lower layer or through an ERP exchange as described in IETF RFC 6696 [113]). | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 19.3.8 |
5,011 | 16.13.5 BWP operation | An (e)RedCap UE in RRC_IDLE or RRC_INACTIVE monitors paging only in an initial BWP (default or RedCap specific) associated with CD-SSB and performs cell (re-)selection and related measurements on the CD-SSB. If a RedCap-specific initial UL BWP is configured and NUL is selected, (e)RedCap UEs shall use only the RedCap-specific initial UL BWP to perform RACH procedure in RRC_IDLE and RRC_INACTIVE or to perform CG-SDT procedure (as described in clause 18.0) in RRC_INACTIVE. An (e)RedCap UE may be configured with multiple NCD-SSBs provided that each BWP is configured with at most one SSB. NCD-SSB may be configured for an (e)RedCap UE in RRC_CONNECTED to perform RLM, BFD, and RRM measurements and RA resource selection when the active BWP does not contain CD-SSB. An (e)RedCap UE may be configured with NCD-SSB for a RedCap-specific initial DL BWP to perform SDT procedure in RRC_INACTIVE (as described in clause 18.0) in case the RedCap-specific initial DL BWP does not contain CD-SSB. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.13.5 |
5,012 | 6.5.4.2 IK | The integrity key IK is 128 bits long. There may be one IK for CS connections (IKCS), established between the CS service domain and the user and one IK for PS connections (IKPS) established between the PS service domain and the user. Which integrity key to use for a particular connection is described in 6.5.5. For UMTS subscribers IK is established during UMTS AKA as the output of the integrity key derivation function f4, that is available in the USIM and in the HLR/AuC. For GSM subscribers, that access the UTRAN, IK is established following GSM AKA and is derived from the GSM cipher key Kc, as described in 6.8.2. IK is stored in the USIM and a copy is stored in the ME. IK is sent from the USIM to the ME upon request of the ME. The USIM shall send IK under the condition that a valid IK is available. The ME shall trigger a new authentication procedure if the current value of STARTCS or STARTPS in the USIM are not up-to-date or STARTCS or STARTPS have reached THRESHOLD. The ME shall delete IK from memory after power-off as well as after removal of the USIM. IK is sent from the HLR/AuC to the VLR/SGSN and stored in the VLR/SGSNas part of a quintet. It is sent from the VLR/SGSN to the RNC in the (RANAP) security mode command. At handover, the IK is transmitted within the network infrastructure from the old RNC to the new RNC, to enable the communication to proceed, and the synchronisation procedure is resumed. The IK remains unchanged at handover, with the exception of SRVCC handover and reverse SRVCC handover. | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | 6.5.4.2 |
5,013 | 13.3.1.3 Authorization of discovery request and error handling | When NRF receives message from unauthenticated NF, NRF shall support error handling, and may send back an error message. The same procedure shall be applied vice versa. After successful authentication between NRF and NF, the NRF shall decide whether the NF is authorized to perform discovery and registration. In the non-roaming scenario, the NRF authorizes the Nnrf_NFDiscovery_Request based on the profile of the expected NF/NF service and the type of the NF Service Consumer, as described in clause 4.17.4 of TS23.502[ Procedures for the 5G System (5GS) ] [8]. In the roaming scenario, the NRF of the NF Service Producer shall authorize the Nnrf_NFDiscovery_Request based on the profile of the expected NF/NF Service, the type of the NF Service Consumer and the serving network ID. If the NRF finds NF Service Consumer is not allowed to discover the expected NF instances(s) as described in clause 4.17.4 of TS 23.502[ Procedures for the 5G System (5GS) ] [8], NRF shall support error handling, and may send back an error message. NOTE 1: Void. When a NF consumes the Nnrf_NFManagement or the Nnrf_NFDiscovery services provided by the NRF, the usage of the OAuth 2.0 access token for authorization between the NF and the NRF is optional. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 13.3.1.3 |
5,014 | 4.3.10 Functionality for Connection of eNodeBs to Multiple MMEs | An eNodeB may connect to several MMEs. This implies that an eNodeB must be able to determine which of the MMEs, covering the area where an UE is located, should receive the signalling sent from a UE. To avoid unnecessary signalling in the core network, a UE that has attached to one MME should generally continue to be served by this MME as long as the UE is in the radio coverage of the pool area to which the MME is associated. The concept of pool area is a RAN based definition that comprises one or more TA(s) that, from a RAN perspective, are served by a certain group of MMEs. This does not exclude that one or more of the MMEs in this group serve TAs outside the pool area. This group of MMEs is also referred to as an MME pool. To enable the eNodeB to determine which MME to select when forwarding messages from an UE, this functionality defines a routing mechanism (and other related mechanism). A routing mechanism (and other related mechanism) is defined for the MMEs. The routing mechanism is required to find the correct old MME (from the multiple MMEs that are associated with a pool area). When a UE roams out of the pool area and into the area of one or more MMEs that do not know about the internal structure of the pool area where the UE roamed from, the new MME will send the Identification Request message or the Context Request message to the old MME using the GUTI. The routing mechanism in both the MMEs and the eNodeB utilises the fact that every MME that serves a pool area must have its own unique value range of the GUTI parameter within the pool area. | 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.10 |
5,015 | – BeamFailureRecoveryRSConfig | The IE BeamFailureRecoveryRSConfig is used to configure the UE with candidate beams for beam failure recovery in case of beam failure detection. See also TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3], clause 5.17. BeamFailureRecoveryRSConfig information element -- ASN1START -- TAG-BEAMFAILURERECOVERYRSCONFIG-START BeamFailureRecoveryRSConfig-r16 ::= SEQUENCE { rsrp-ThresholdBFR-r16 RSRP-Range OPTIONAL, -- Need M candidateBeamRS-List-r16 SEQUENCE (SIZE(1..maxNrofCandidateBeams-r16)) OF CandidateBeamRS-r16 OPTIONAL, -- Need M ..., [[ candidateBeamRS-List2-r17 SEQUENCE (SIZE(1..maxNrofCandidateBeams-r16)) OF CandidateBeamRS-r16 OPTIONAL -- Need R ]] } -- TAG-BEAMFAILURERECOVERYRSCONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
5,016 | 11.2.1.7 Support L2TP for CUPS across SGi | L2TP (described in IETF RFC 2661 [118]) is a standard method for tunneling encapsulated Point-to-Point Protocol (PPP) frames over an IP network. L2TP operates between two L2TP endpoints (LAC and LNS), and tunnels PPP-encapsulated IP traffic between these endpoints. L2TP runs over UDP/IP and was originally defined for systems where PPP is used by an end-device to connect to a network (e.g. via DSL connections, or 2G/3G PPP PDP context). In these cases, a LAC could be deployed in the network (e.g. in a BNG or GGSN/PGW) to tunnel the PPP traffic to a server (LNS) over an IP network. For CUPS with the UE using IP PDN connection, the PPP functionality that is required to use L2TP is instead supported by the PGW-U, as illustrated in below figure. Upon receiving a PDN connection session establishment request from the UE via MME and SGW-C, PGW-C may depend on local L2TP configuration per APN or the received L2TP information from a DN AAA server in Access-Accept message, request the PGW-U to setup L2TP tunnel towards an L2TP network server (LNS) in the external DN and tunnel the PDN Connection user plane traffic in this L2TP tunnel. In this case the PGW-U acts as a L2TP access concentrator (LAC). To enable this, the PGW-C may provide L2TP tunnel information to the PGW-U as LAC, such as LNS IP address as described in 3GPP TS 29.244[ Interface between the Control Plane and the User Plane nodes ] [114]. This L2TP tunnel information may be configured on the PGW-C as part of the APN configuration or received from the DN-AAA server. Alternatively, the L2TP tunnel parameters may be configured in the PGW-U. The L2TP tunnel parameters include necessary parameters for setting up L2TP tunnel towards the LNS (e.g. LNS address, tunnel password). In addition, the PGW-C may provide PAP/CHAP authentication information to the PGW-U, for use in L2TP session establishment, in case it was received from the UE in the PCO or ePCO IE of the PDN Connection establishment request message. When L2TP is to be used for a PDN Connection, the PGW-C may select a PGW-U and requests the UE IP address to be allocated by LNS according to 3GPP TS 29.244[ Interface between the Control Plane and the User Plane nodes ] [114], the PGW-U (LAC) may retrieve this IP address from the LNS. Figure 11f: L2TP Tunnel between CUPS and external DN Below figure describes the L2TP connection procedures between CUPS and external DN, upon the UE is accessed in EPS and the PGW-C and PGW-U has been negotiated supporting L2TP feature. Figure 11g: L2TP connection procedures between CUPS and external DN 0. The PGW-C and the PGW-U negotiated supporting L2TP feature as specified in 3GPP TS 29.244[ Interface between the Control Plane and the User Plane nodes ] [114]. 1. The PGW-C receives a PDN Connection session establishment request from the UE via MME and SGW-C. The UE may include the authentication information for PAP and/or CHAP in PCO or ePCO IE. The PGW-C may locally configure the UE authentication information for a given APN. The PGW-C may determine that an L2TP session is required for the PDN Connection session based on local configured L2TP parameters per APN. 2. The PGW-C may receive the L2TP Tunnel parameters (e.g. LNS IP address or FQDN, tunnel password) from the DN-AAA server in Access-Accept message or Diameter AAA message, or local configured. 3. If L2TP protocol is determined to support the PDN connection, the PGW-C selects a PGW-U supporting L2TP and be configured with the LAC name/addresses and then requests the PGW-U to setup an L2TP tunnel if needed and/or L2TP session towards the L2TP network server (LNS). The PGW-C sends PFCP Session Establishment Request to the PGW-U, which may include L2TP Tunnel Information for setting up a L2TP tunnel and L2TP session information to setup a L2TP session, together with the information for authentication used during L2TP Tunnel setup, as well as for L2TP session. The L2TP Tunnel Information includes LNS IPv4 address or IPv6 address of LNS, Tunnel Password. The L2TP Session Information includes specific information related to the PDN Connection, e.g. a Calling Number which may be set to UE's MSISDN, an indication to instruct that the PGW-U shall request the LNS to allocate an IP address for the PDN session, indications to instruct that the PGW-U shall request the LNS to provide DNS server addresses or NBNS server addresses etc. as specified in 3GPP TS 29.244[ Interface between the Control Plane and the User Plane nodes ] [114]. 4. The PGW-U checks if any existing L2TP tunnel can be used to serve the PDN Connection according to the information provided in the L2TP Tunnel Information. If the PGW-U decides to setup a new L2TP tunnel, it initiates L2TP Tunnel establishment by sending an SCCRQ (Start-Control-Connection-Request) message towards the LNS, the PGW-U will allocate a Tunnel ID, and it may include a CHAP Challenge to authenticate the LNS. The Challenge and Challenge Response (to be included in SCCCN) is produced by the PGW-U using the Tunnel Password received from the PGW-C. The LNS responds with an SCCRP (Start-Control-Connection-Reply) message, containing its allocated Tunnel ID and a CHAP Challenge Response to the Challenge in SCCRQ. The PGW-U then responds with a Challenge response for tunnel authentication in the SCCCN (Start-Control-Connection-Connected) message. An L2TP tunnel is established after the tunnel authentication is successful, with the reception of the SCCCN message sent by the PGW-U to the LNS. If the PGW-U decides to use an already existing L2TP tunnel for the requested PDN Connection from the PGW-C, it proceeds with step 5 below directly without current step. 5. Once the L2TP Tunnel is established (or already present) between the PGW-U and the LNS for the PDN Connection requested by the UE, the PGW-U proceeds with L2TP session setup towards the LNS. The PGW-U sends an ICRQ (Incoming-Call-Request) message towards the LNS, which contains the Tunnel ID assigned by the LNS, its assigned Session ID, and optionally, the Calling Number and Called Number. The LNS responds with an ICRP (Incoming-Call-Reply) message and provides the Session ID assigned by it to the LAC. The PGW-U then sends an ICCN (Incoming-Call-Connected) message. If proxy LCP and authentication are employed, the ICCN message includes the link control parameters (e.g. MRU) and UE authentication information sent from the PGW-C which was received via PCO or ePCO IE in step 1. In addition, the PGW-U (LAC) will act as a PPP endpoint to use IPCP to request UE IP Address, DNS server address and/or NBNS server address(es). The LCP renegotiation may by triggered by the LNS after receiving the ICCN message. If so, the LAC and LNS will use PPP LCP to communicate link specific control parameter (e.g. MRU), and indicate authentication type, then either PPP PAP/CHAP takes place. The PPP IPCP transactions takes places to retrieve UE IP Address, DNS server address and/or NBNS server address. 6. The status of the L2TP session setup is sent by the PGW-U to the PGW-C in a PFCP Session Establishment Response. 7. The PGW-C sends a PDU Session Establishment Response to the UE and the user data session is initiated, which may contain the DNS and NBNS Server information. | 3GPP TS 29.061 | Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) | CT WG3 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 11.2.1.7 |
5,017 | Annex B (informative): Supported MR-DC Handover Scenarios | Table B-1 summarizes the supported handover scenarios involving MR-DC configurations. Table B-1: Supported MR-DC handover scenarios. NOTE 1: Only SRVCC handover of IMS voice bearer to UTRAN is supported. NOTE 2: All handover scenarios according to Table B-1 that have a DC option in the column "from" are supported during fast MCG failure recovery. NOTE 3: Only intra-RAT conditional handover is supported except for E-UTRA with 5GC scenario. NOTE 4: DAPS handover is only supported from E-UTRA with EPC to E-UTRA with EPC and from NR to NR. | 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 | Annex |
5,018 | 13.3.8 Client credentials assertion based authentication 13.3.8.1 General | The Client credentials assertion (CCA) is a token signed by the NF Service Consumer. It enables the NF Service Consumer to authenticate towards the receiving end point (NRF, NF Service Producer) by including the signed token in a service request. It includes the NF Service Consumer’s NF Instance ID that can be checked against the certificate by the NF Service Producer. The CCA includes a timestamp as basis for restriction of its lifetime. CCAs are expected to be more short-lived than NRF generated access tokens. So, they can be used in deployments with requirements for tokens with shorter lifetime for NF-NF communication. There is a trade-off that when the lifetime of the CCA is too short, it requires the NF Service Consumer to generate a new CCA for every new service request. The CCA cannot be used in the roaming case, as the NF Service Producer in the home PLMN will not be able to verify the signature of the NF Service Consumer in the visited PLMN unless cross-certification process is established between the two PLMNs through one of the mechanisms specified in TS 33.310[ Network Domain Security (NDS); Authentication Framework (AF) ] . CCA does not provide integrity protection on the full service request. Neither does it provide a mechanism for the NF Service Consumer to authenticate the NF Service Producer. In this clause, CCAs are described generally for both NF-NRF communication and NF-NF communication. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 13.3.8 |
5,019 | 4.11 User Plane CIoT EPS Optimisation | The User Plane CIoT EPS Optimisation functionality enables support for transfer of user plane data without the need for using the Service Request procedure to establish Access Stratum (AS) context in the serving eNodeB and UE. If the following preconditions are met: - UE and MME support User Plane CIOT EPS Optimisation as defined in clause 4.3.5.10, - MME indicates "UE User Plane CIoT Support Indicator" IE to "supported" as defined in TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [36], - and the UE performs an initial connection establishment that establishes the AS bearers and the AS security context in the network and UE, then the RRC connection can be suspended by means of a Connection Suspend Procedure (see clause 5.3.4A). Based on trigger from the NAS layer when UE is in ECM-IDLE including if it attempts to send data using Control Plane CIoT EPS Optimisation as defined in clause 5.3.4B, the UE shall attempt the Connection Resume procedure, see clause 5.3.5A and TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [46]. If the Connection Resume procedure fails, the UE initiates the pending NAS procedure, see TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [46]. To maintain support for User Plane CIoT EPS Optimisation at UE mobility between cells configured on different eNodeBs, the AS Context should be transferred between the eNodeBs, see TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [5] and TS 36.423[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 Application Protocol (X2AP) ] [76]. Early Data Transfer (EDT) for User Plane CIOT EPS Optimisation is defined in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [5] and clause 5.3.5A. If the UE is in ECM-IDLE state with AS information stored, and the UE attempts to send data using Control Plane CIoT EPS Optimisation as defined in clause 5.3.4B, the UE shall attempt the Connection Resume procedure without Early Data Transfer. By using the Connection Suspend procedure, see clause 5.3.5A and TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [5]: - the UE at transition into ECM-IDLE stores the AS information; - the eNodeB stores the AS information, the S1AP association and the bearer context for that UE; - MME stores the S1AP association and the bearer context for that UE and enters ECM-IDLE. In the context of this functionality, the UE and the eNodeB store the relevant AS information at transition into ECM-IDLE. By using the Connection Resume procedure, see clause 5.3.5A and TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [5]: - the UE resumes the connection with the network using the AS information stored during the Connection Suspend procedure; - the, potentially new, eNodeB notifies the MME that the connection with the UE has been securely resumed and the MME enters ECM-CONNECTED. If a MME has a S1AP association stored for a UE and the MME receives for that UE a EMM procedure over another UE-associated logical S1-connection or at Tracking Area Update procedure with MME change, or SGSN Context Request, when the UE has re-attached, or when the UE has been Detached, the MME and the previously involved eNodeB shall delete that stored S1AP association using the S1 Release procedure, see clause 5.3.5 and TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [36]. | 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.11 |
5,020 | 5.5.2.2.3 UE-initiated de-registration procedure completion for 5GS services over 3GPP access | If the access type in the DEREGISTRATION REQUEST message indicates that the de-registration procedure is for 3GPP access, the AMF shall trigger the SMF to perform a local release of the PDU session(s) established over 3GPP access, if any, for this UE. The UE shall perform a local release of the PDU session(s) established over 3GPP access, if any. If a PDU session is associated with one or more multicast MBS sessions, the UE shall locally leave the associated multicast MBS sessions and the SMF shall consider the UE as removed from the associated multicast MBS sessions. If there is an MA PDU session with user plane resources established on both 3GPP access and non-3GPP access in the same PLMN or in different PLMNs, the AMF shall trigger SMF to perform release of user plane resources on 3GPP access, and the UE shall consider the user plane resources on 3GPP access as released. If there is an MA PDU session with user plane resources established on 3GPP access only, the AMF shall trigger the SMF to perform a local release of the MA PDU session, and the UE shall perform a local release of the MA PDU session. If the MA PDU session is associated with one or more MBS multicast sessions, the UE shall locally leave the associated MBS multicast sessions. The UE is marked as inactive in the AMF for 5GS services for 3GPP access. The AMF shall enter the state 5GMM-DEREGISTERED for 3GPP access. If the UE supports N1 mode only and the de-registration request is not due to switch off, then: a) if the de-registration procedure was performed due to disabling of 5GS services, then the UE shall enter the 5GMM-NULL state for 3GPP access; b) otherwise, the UE shall enter the 5GMM-DEREGISTERED state for 3GPP access. NOTE: Case b) is applicable when the UE is also registered over non-3GPP access. If the access type indicates that the de-registration procedure is for 3GPP access or for 3GPP access and non-3GPP access, and the UE is operating in single-registration mode, it shall additionally proceed as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15], subclause 5.5.2.2.2, for the case when the UE receives an EMM message DETACH ACCEPT. Furthermore, if the UE supports A/Gb or Iu mode, it shall disable the N1 mode capability for 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 | 5.5.2.2.3 |
5,021 | 5.1.2 Types of EMM procedures | Depending on how they can be initiated, three types of EMM procedures can be distinguished: 1) EMM common procedures: An EMM common procedure can always be initiated whilst a NAS signalling connection exists. The procedures belonging to this type are: Initiated by the network: - GUTI reallocation; - authentication; - security mode control; - identification; - EMM information. 2) EMM specific procedures: At any time only one UE initiated EMM specific procedure can be running. The procedures belonging to this type are: Initiated by the UE and used to attach the IMSI in the network for EPS services and/or non-EPS services, and to establish an EMM context and if requested by the UE, a default bearer: - attach and combined attach. Initiated by the UE and used to attach the IMSI or IMEI for emergency bearer services, and to establish an EMM context and a default bearer to a PDN that provides emergency bearer services: - attach. Initiated by the UE and used to attach the IMSI or IMEI for access to RLOS, and to establish an EMM context and a default bearer to a PDN connection for RLOS: - attach. Initiated by the UE or the network and used to detach the IMSI in the network for EPS services and/or non-EPS services and to release an EMM context and all bearers, if any: - detach and combined detach. Initiated by the UE and used to detach the IMSI in the network for EPS services or non-EPS services and to release an EMM context and all bearers, if any: - eCall inactivity procedure. Initiated by the UE when an EMM context has been established: - normal tracking area updating and combined tracking area updating (S1 mode only); - periodic tracking area updating (S1 mode only). The tracking area updating procedure can be used to request also the resource reservation for sending data. 3) EMM connection management procedures (S1 mode only): Initiated by the UE and used to establish a secure connection to the network or to request the resource reservation for sending data, or both: - service request. The service request procedure can only be initiated if no UE initiated EMM specific procedure is ongoing. Initiated by the network and used to request the establishment of a NAS signalling connection or to prompt the UE to re-attach if necessary as a result of a network failure: - paging procedure. Initiated by the UE or the network and used to transport NAS messages: - transport of NAS messages; - generic transport of NAS messages. The transport of NAS messages procedure and the generic transport of NAS messages procedure cannot be initiated while an EMM specific procedure or a service request procedure is ongoing. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.1.2 |
5,022 | 13.2.4.5.1 modifiedDataToIntegrityProtect | Figure 13.2.4.5.1-1 Example of JSON representation of IPX provider modifications This is a temporary JSON object generated by an IPX provider as it modifies the original message. It shall contain the following: a) Operations – This is a JSON patch document that captures IPX modifications based on RFC 6902 [64]. If no patch is required, the operations element shall be set to null. b) Identity – This is the identity of the IPX performing the modification. c) Tag – A JSON string element to capture the “tag” value (JWE Authentication tag) in the JWE object generated by the sending SEPP. This is required for replay protection. NOTE: Since there is no central registry that can ensure unique IPX Identities, it is expected that an IPX will include its Fully Quantified Domain Name (FQDN) in the JSON modification object. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 13.2.4.5.1 |
5,023 | 6.16.1.1 Security procedures for Small Data Transfer in Control Plane CIoT 5GS Optimisation | The Control Plane Optimisation for 5GS CIoT is used to exchange small user data or SMS as payload of a NAS message in both uplink and downlink directions. The UE and the AMF perform integrity protection and ciphering for the small user data or SMS using NAS security context specific to the NAS connection. If UE uses Control Plane optimisation for 5GS CIoT for Mobile Originated data transport, the UE sends a Control Plane Service Request message including a container for small user data or SMS transport. The Control Plane Service Request message shall be partially ciphered (i.e. the container including uplink user data or SMS is ciphered, and non-cleartext remains unciphered) and integrity protected by the current 5G NAS security context specific to the NAS connection if such exists as depicted in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [35]. Upon reception of the Control Plane Service Request message with the ciphered container for small user data or SMS transport, the AMF shall verify integrity of the whole Control Plane Service Request message and decipher the ciphered container to obtain the small user data or SMS. When applying NAS ciphering/deciphering mechanism for the container, the LENGTH value shall be set to the length of the container contents. Additionally, if UE uses Control Plane optimisation for 5GS CIoT for Mobile Originated data transport, the UE in CM-CONNECTED mode sends small user data or SMS in UL NAS transport message to the AMF. The UL NAS transport message shall be ciphered and integrity protected with the current 5G NAS security context specific to the NAS connection. Upon reception of the UL NAS transport message for small user data or SMS transport, the AMF shall verify integrity and decipher the UL NAS transport message to obtain the small user data or SMS. If UE uses Control Plane optimisation for 5GS CIoT for Mobile Terminated data transport, the UE obtains small user data or SMS in DL NAS transport message from the AMF. The DL NAS transport message shall be ciphered and integrity protected with the current 5G NAS security context specific to the NAS connection. Upon reception of the DL NAS transport message for small user data or SMS transport, the UE shall verify integrity and decipher the DL NAS transport message to obtain the small user data or SMS. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.16.1.1 |
5,024 | 5.4.8 Access Stratum Release Assistance Indication | Access Stratum Release Assistance Indication is used to provide the serving eNB with information whether subsequent DL or UL transmission is expected. AS RAI uses the DCQR and AS RAI MAC Control Element. Upper layers trigger AS RAI. For EDT and transmission using PUR, if AS RAI is triggered by upper layers but is not included in the resulting MAC PDU with the MAC SDU as a result of logical channel prioritization, AS RAI is cancelled, for other transmissions if AS RAI is not included in the resulting MAC PDU as a result of logical channel prioritization, AS RAI may be cancelled. If rai-Activation is configured and a buffer size of zero bytes has been triggered for the BSR and no subsequent DL and UL data transmission is expected, and if rai-ActivationEnh is enabled and applicable as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8], it is up to UE to send BSR MAC control element or DCQR and AS RAI 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.4.8 |
5,025 | 5.5.3.3.4 Combined tracking area updating procedure accepted by the network 5.5.3.3.4.1 General | Depending on the value of the EPS update result IE received in the TRACKING AREA UPDATE ACCEPT message, the following different cases can be distinguished: 1) The EPS update result IE value indicates "combined TA/LA updated": Tracking and location area updating is successful for EPS and non-EPS services, or for EPS services and "SMS only"; 2) The EPS update result IE value indicates "TA updated": Tracking area updating is successful, but location area updating for non-EPS services or "SMS only" is not successful. A TRACKING AREA UPDATE COMPLETE message shall be returned to the network if the TRACKING AREA UPDATE ACCEPT message contains a GUTI or a TMSI or both. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.5.3.3.4 |
5,026 | 8.72 MBMS Flow Identifier | The MBMS Flow Identifier is defined in 3GPP TS 23.246[ Multimedia Broadcast/Multicast Service (MBMS); Architecture and functional description ] [37]. In broadcast mode, the MBMS Flow Identifier information element is included in MBMS Session Management messages to differentiate the different sub-sessions of an MBMS user service (identified by the TMGI) providing location-dependent content. The payload shall be encoded as per the MBMS-Flow-Identifier AVP defined in 3GPP TS 29.061[ Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) ] [38], excluding the AVP Header fields (as defined in IETF RFC 3588 [39], clause 4.1). Figure 8.72-1: MBMS Flow Identifier | 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.72 |
5,027 | 7.7.8 Semantically incorrect Information Element | Apart from Echo Request message, the receiver of a GTP signalling message Request including a mandatory or a verifiable conditional information element with a semantically invalid Value shall discard the request, should log the error, and shall send a response with Cause set to "Mandatory IE incorrect" together with a type and instance of the offending IE. The receiver of a GTP signalling message Response including a mandatory or a verifiable conditional information element with a semantically invalid Value shall notify the upper layer that a message with this sequence number has been received and should log the error. If a GTP entity receives an information element with a value which is shown as reserved, it shall treat that information element as invalid and should log the error. If the invalid IE is received in a Request, and it is a mandatory IE or a verifiable conditional IE, the GTP entity shall send a response with Cause set to "Mandatory IE incorrect " together with a type and instance of the offending IE. The principle is: the use of reserved values invokes error handling; the use of spare values can be silently discarded and so in the case of IEs with spare values used, processing shall be continued ignoring the spare values. The receiver of a GTP signalling message including an optional information element with a Value that is not in the range defined for this information element value shall discard this IE, but shall treat the rest of the message as if this IE was absent and continue processing. The receiver shall not check the content of an information element field that is defined as 'spare". All semantically incorrect optional information elements in a GTP signalling message shall be treated as not present in the message. | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 7.7.8 |
5,028 | – MBSBroadcastConfiguration | The MBSBroadcastConfiguration message contains the control information applicable for MBS broadcast services transmitted via broadcast MRB. Signalling radio bearer: N/A RLC-SAP: UM Logical channel: MCCH Direction: Network to UE MBSBroadcastConfiguration message -- ASN1START -- TAG-MBSBROADCASTCONFIGURATION-START MBSBroadcastConfiguration-r17 ::= SEQUENCE { criticalExtensions CHOICE { mbsBroadcastConfiguration-r17 MBSBroadcastConfiguration-r17-IEs, criticalExtensionsFuture SEQUENCE {} } } MBSBroadcastConfiguration-r17-IEs ::= SEQUENCE { mbs-SessionInfoList-r17 MBS-SessionInfoList-r17 OPTIONAL, -- Need R mbs-NeighbourCellList-r17 MBS-NeighbourCellList-r17 OPTIONAL, -- Need S drx-ConfigPTM-List-r17 SEQUENCE (SIZE (1..maxNrofDRX-ConfigPTM-r17)) OF DRX-ConfigPTM-r17 OPTIONAL, -- Need R pdsch-ConfigMTCH-r17 PDSCH-ConfigBroadcast-r17 OPTIONAL, -- Need S mtch-SSB-MappingWindowList-r17 MTCH-SSB-MappingWindowList-r17 OPTIONAL, -- Need R lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL } -- TAG-MBSBROADCASTCONFIGURATION-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
5,029 | 13.3.1.1 Direct communication | NRF and NF shall authenticate each other during discovery, registration, and access token request. In direct communication, NF and NRF shall use one of the following methods for authentication: - If the PLMN uses protection at the transport layer as described in clause 13.1, authentication provided by the transport layer protection solution shall be used for mutual authentication of the NRF and NF. - If the PLMN does not use protection at the transport layer, mutual authentication of NRF and NF may be implicit by NDS/IP or physical security (see clause 13.1). | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 13.3.1.1 |
5,030 | 8.3.1.3.1 Minimum requirement with Same Cell ID (with single NZP CSI-RS resource) | The requirements are specified in Table 8.3.1.3.1-3, with the additional parameters in Table 8.3.1.3.1-1 and Table 8.3.1.3.1-2. The purpose of this test is to verify the UE capability of supporting non quasi-colocated antenna ports when the UE receives DCI format 2D in a scenario where the two transmission point share the same Cell ID. In particular the test verifies that the UE, configured with quasi co-location type B, performs correct tracking and compensation of the timing difference between two transmission points, channel parameters estimation and rate matching according to the ‘PDSCH RE Mapping and Quasi-Co-Location Indicator’ (PQI) signalling defined in [6], configured according to Table 8.3.1.3.1-2. In Tables 8.3.1.3.1-1 and 8.3.1.3.1-2, transmission point 1 (TP 1) is the serving cell and transmission point 2 (TP 2) transmits PDSCH. The downlink physical channel setup for TP 1 is according to Table C.3.4-1 and for TP 2 according to Table C.3.4-2. Table 8.3.1.3.1-1: Test Parameters for quasi co-location type B: same Cell ID Table 8.3.1.3.1-2: Configurations of PQI and DL transmission hypothesis for each PQI set Table 8.3.1.3.1-3: Minimum performance for quasi co-location type B: same Cell ID | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.3.1.3.1 |
5,031 | 5.2.1.4.1 Notification of interworking in connection with mobile originated call establishment | During call establishment, the call may leave a PLMN/ISDN environment; e.g., because of interworking with another network, with a non-PLMN/ISDN user, or with non-PLMN/ISDN equipment within the called user's premises; the call may also return to a PLMN/ISDN environment. When such situations occur, the network may send a progress indicator information element to the calling mobile station either: a) in an appropriate call control message, if a state change is required (e.g. ALERTING or CONNECT); or, b) in the PROGRESS message, if no state change is appropriate. This progress indicator information element shall contain one of the following progress description values: a) #1 "call is not end-to-end PLMN/ISDN; further call progress information may be available in-band". b) #2 "destination address is non-PLMN/ISDN". c) #4 "call has returned to PLMN/ISDN. See also subclauses 5.5.1 and 5.5.6 for further reactions of the mobile station. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.2.1.4.1 |
5,032 | 5.3.13.4 Reception of the RRCResume by the UE | The UE shall: 1> stop timer T319, if running; 1> stop timer T319a, if running and consider SDT procedure is not ongoing; 1> stop timer T380, if running; 1> if T331 is running: 2> stop timer T331; 2> perform the actions as specified in 5.7.8.3; 1> if the RRCResume includes the fullConfig: 2> perform the full configuration procedure as specified in 5.3.5.11; 1> else: 2> if the RRCResume does not include the restoreMCG-SCells: 3> release the MCG SCell(s) from the UE Inactive AS context, if stored; 2> if the RRCResume does not include the restoreSCG: 3> release the MR-DC related configurations (i.e., as specified in 5.3.5.10) from the UE Inactive AS context, if stored; 2> restore the masterCellGroup, mrdc-SecondaryCellGroup, if stored, and pdcp-Config from the UE Inactive AS context; 2> configure lower layers to consider the restored MCG and SCG SCell(s) (if any) to be in deactivated state; 1> discard the UE Inactive AS context; 1> store the used nextHopChainingCount value associated to the current KgNB; 1> if sdt-MAC-PHY-CG-Config is configured: 2> instruct the MAC entity to stop the cg-SDT-TimeAlignmentTimer, if it is running; 2> instruct the MAC entity to start the timeAlignmentTimer associated with the PTAG, if it is not running; 1> if srs-PosRRC-Inactive is configured: 2> instruct the MAC entity to stop inactivePosSRS-TimeAlignmentTimer, if it is running; 1> if srs-PosRRC-InactiveValidityAreaConfig is configured: 2> instruct the MAC entity to stop inactivePosSRS-ValidityAreaTAT, if it is running; 1> release the suspendConfig except the ran-NotificationAreaInfo; 1> if the RRCResume includes the masterCellGroup: 2> perform the cell group configuration for the received masterCellGroup according to 5.3.5.5; 1> if the RRCResume includes the mrdc-SecondaryCellGroup: 2> if the received mrdc-SecondaryCellGroup is set to nr-SCG: 3> perform the RRC reconfiguration according to 5.3.5.3 for the RRCReconfiguration message included in nr-SCG; 2> if the received mrdc-SecondaryCellGroup is set to eutra-SCG: 3> perform the RRC connection reconfiguration as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10], clause 5.3.5.3 for the RRCConnectionReconfiguration message included in eutra-SCG; 1> if the RRCResume includes the radioBearerConfig: 2> perform the radio bearer configuration according to 5.3.5.6; 1> if the RRCResume message includes the sk-Counter: 2> perform security key update procedure as specified in 5.3.5.7; 1> if the RRCResume message includes the radioBearerConfig2: 2> perform the radio bearer configuration according to 5.3.5.6; 1> if the RRCResume message includes the needForGapsConfigNR: 2> if needForGapsConfigNR is set to setup: 3> consider itself to be configured to provide the measurement gap requirement information of NR target bands; 2> else: 3> consider itself not to be configured to provide the measurement gap requirement information of NR target bands; 1> if the RRCResume message includes the needForGapNCSG-ConfigNR: 2> if needForGapNCSG-ConfigNR is set to setup: 3> consider itself to be configured to provide the measurement gap and NCSG requirement information of NR target bands; 2> else: 3> consider itself not to be configured to provide the measurement gap and NCSG requirement information of NR target bands; 1> if the RRCResume message includes the needForGapNCSG-ConfigEUTRA: 2> if needForGapNCSG-ConfigEUTRA is set to setup: 3> consider itself to be configured to provide the measurement gap and NCSG requirement information of E-UTRA target bands; 2> else: 3> consider itself not to be configured to provide the measurement gap and NCSG requirement information of E-UTRA target bands; 1> if idleInactiveReportAllowed is not included in the RRCResume message: 2> for each application layer measurement configuration with configforRRC-IdleInactive set to true: 3> forward the measConfigAppLayerId and inform upper layers about the release of the application layer measurement configuration; 3> discard any application layer measurement reports which were not yet submitted to lower layers for transmission; 3> release the application layer measurement configuration in UE variables VarAppLayerIdleConfig and VarAppLayerPLMN-ListConfig; 3> consider itself not to be configured to send application layer measurement report for the measConfigAppLayerId; 1> if the RRCResume message includes the appLayerMeasConfig: 2> perform the application layer measurement configuration procedure as specified in 5.3.5.13d; 1> if the RRCResume message includes the sl-L2RemoteUE-Config (i.e. the UE is a L2 U2N Remote UE): 2> perform the L2 U2N Remote UE configuration procedure as specified in 5.3.5.16; 1> if the RRCResume message includes the sl-ConfigDedicatedNR: 2> perform the sidelink dedicated configuration procedure as specified in 5.3.5.14; 1> resume SRB2 (if suspended), SRB3 (if configured), SRB4 (if configured), all DRBs (that are suspended) and multicast MRBs (that are suspended); NOTE 1: If the SCG is deactivated, resuming SRB3 and all DRBs does not imply that PDCP or RRC PDUs can be transmitted or received on SCG RLC bearers. 1> if stored, discard the cell reselection priority information provided by the cellReselectionPriorities or inherited from another RAT; 1> stop timer T320, if running; 1> if the RRCResume message includes the measConfig: 2> perform the measurement configuration procedure as specified in 5.5.2; 1> resume measurements if suspended; 1> if T390 is running: 2> stop timer T390 for all access categories; 2> perform the actions as specified in 5.3.14.4; 1> if T302 is running: 2> stop timer T302; 2> perform the actions as specified in 5.3.14.4; 1> enter RRC_CONNECTED; 1> indicate to upper layers that the suspended RRC connection has been resumed; 1> stop the cell re-selection procedure; 1> stop relay reselection procedure if any for L2 U2N Remote UE; 1> consider the current cell to be the PCell; 1> set the content of the of RRCResumeComplete message as follows: 2> if the upper layer provides NAS PDU, set the dedicatedNAS-Message to include the information received from upper layers; 2> if upper layers provides a PLMN: 3> if the UE is either allowed or instructed to access the PLMN via a cell for which at least one CAG ID is broadcast: 4> set the selectedPLMN-Identity from the npn-IdentityInfoList; 3> else: 4> set the selectedPLMN-Identity to the PLMN selected by upper layers from the plmn-IdentityInfoList; 2> if the masterCellGroup contains the reportUplinkTxDirectCurrent: 3> include the uplinkTxDirectCurrentList for each MCG serving cell with UL; 3> include uplinkDirectCurrentBWP-SUL for each MCG serving cell configured with SUL carrier, if any, within the uplinkTxDirectCurrentList; 2> if the masterCellGroup contains the reportUplinkTxDirectCurrentTwoCarrier: 3> include in the uplinkTxDirectCurrentTwoCarrierList the list of uplink Tx DC locations for the configured uplink carrier aggregation in the MCG; 2> if the masterCellGroup contains the reportUplinkTxDirectCurrentMoreCarrier: 3> include in the uplinkTxDirectCurrentMoreCarrierList the list of uplink Tx DC locations for the configured uplink carrier aggregation in the MCG; 2> if the UE has idle/inactive measurement information concerning cells other than the PCell available in VarMeasIdleReport: 3> if the idleModeMeasurementReq is included in the RRCResume message: 4> set the measResultIdleEUTRA in the RRCResumeComplete message to the value of measReportIdleEUTRA in the VarMeasIdleReport, if available; 4> set the measResultIdleNR in the RRCResumeComplete message to the value of measReportIdleNR in the VarMeasIdleReport, if available; 4> discard the VarMeasIdleReport upon successful delivery of the RRCResumeComplete message is confirmed by lower layers; 3> else: 4> if the SIB1 contains idleModeMeasurementsNR and the UE has NR idle/inactive measurement information concerning cells other than the PCell available in VarMeasIdleReport; or 4> if the SIB1 contains idleModeMeasurementsEUTRA and the UE has E-UTRA idle/inactive measurement information available in VarMeasIdleReport: 5> include the idleMeasAvailable; 2> if the RRCResume message includes mrdc-SecondaryCellGroup set to eutra-SCG: 3> include in the eutra-SCG-Response the E-UTRA RRCConnectionReconfigurationComplete message in accordance with TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10] clause 5.3.5.3; 2> if the RRCResume message includes mrdc-SecondaryCellGroup set to nr-SCG: 3> include in the nr-SCG-Response the SCG RRCReconfigurationComplete message; 2> if the UE has logged measurements available for NR and if the RPLMN is included in plmn-IdentityList stored in VarLogMeasReport; or 2> if the UE has logged measurements available for NR and if the current registered SNPN is included in snpn-ConfigIDList stored in VarLogMeasReport: 3> include the logMeasAvailable in the RRCResumeComplete message; 3> if Bluetooth measurement results are included in the logged measurements the UE has available for NR: 4> include the logMeasAvailableBT in the RRCResumeComplete message; 3> if WLAN measurement results are included in the logged measurements the UE has available for NR: 4> include the logMeasAvailableWLAN in the RRCResumeComplete message; 2> if the sigLoggedMeasType in VarLogMeasReport is included; or 2> if the UE is capable of reporting availability of signalling based logged MDT for inter-RAT (i.e. LTE to NR), and if the sigLoggedMeasType in VarLogMeasReport of TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10] is included: 3> if T330 timer is running (associated to the logged measurement configuration for NR or for LTE): 4> set sigLogMeasConfigAvailable to true in the RRCResumeComplete message; 3> else: 4> if the UE has logged measurements: 5> set sigLogMeasConfigAvailable to false in the RRCResumeComplete message; 2> if the UE has connection establishment failure or connection resume failure information available in VarConnEstFailReport or VarConnEstFailReportList and if the RPLMN is equal to plmn-Identity stored in VarConnEstFailReport or in at least one of the entries of VarConnEstFailReportList; or 2> if the UE has connection establishment failure information or connection resume failure information available in VarConnEstFailReport or VarConnEstFailReportList and if the registered SNPN identity is equal to snpn-identity stored in VarConnEstFailReport or any entry of VarConnEstFailReportList: 3> include connEstFailInfoAvailable in the RRCResumeComplete message; 2> if the UE has radio link failure or handover failure information available in VarRLF-Report and if the RPLMN is included in plmn-IdentityList stored in VarRLF-Report; or 2> if the UE has radio link failure or handover failure information available in VarRLF-Report of TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10] and if the UE is capable of cross-RAT RLF reporting and if the RPLMN is included in plmn-IdentityList stored in VarRLF-Report of TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10]; or 2> if the UE has radio link failure or handover failure information available in VarRLF-Report and if the current registered SNPN are included in snpn-IdentityList stored in VarRLF-Report; or 3> include rlf-InfoAvailable in the RRCResumeComplete message; 2> if the UE has successful PSCell change or addition related information available in VarSuccessPSCell-Report and if the RPLMN is included in plmn-IdentityList stored in VarSuccessPSCell-Report; or 2> if the UE has successful PSCell change or addition information available in VarSuccessPSCell-Report and if the current registered SNPN is included in snpn-IdentityList stored in the VarSuccessPSCell-Report: 3> include successPSCell-InfoAvailable in the RRCResumeComplete message; 2> if the UE has successful handover information available in VarSuccessHO-Report and if the RPLMN is included in plmn-IdentityList stored in VarSuccessHO-Report; or 2> if the UE has successful handover information available in VarSuccessHO-Report and if the current registered SNPN is included in snpn-IdentityList stored in the VarSuccessHO-Report: 3> include successHO-InfoAvailable in the RRCResumeComplete message; 2> if the UE supports storage of mobility history information and the UE has mobility history information available in VarMobilityHistoryReport: 3> include the mobilityHistoryAvail in the RRCResumeComplete message; 2> if speedStateReselectionPars is configured in the SIB2: 3> include the mobilityState in the RRCResumeComplete message and set it to the mobility state (as specified in TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [20]) of the UE just prior to entering RRC_CONNECTED state; 2> if the UE is configured with at least one application layer measurement with configForRRC-IdleInactive set to true: 3> for each application layer measurement configuration with configForRRC-IdleInactive set to true: 4> if the RPLMN is not included in plmn-IdentityList in VarAppLayerPLMN-ListConfig: 5> forward the measConfigAppLayerId and inform upper layers about the release of the application layer measurement configuration; 5> discard any application layer measurement reports which were not yet submitted to lower layers for transmission; 5> release the application layer measurement configuration in UE variables VarAppLayerIdleConfig and VarAppLayerPLMN-ListConfig; 5> consider itself not to be configured to send application layer measurement report for the measConfigAppLayerId; 3> if at least one stored application layer measurement configuration or application layer measurement report container has not been released: 4> include measConfigReportAppLayerAvailable in the RRCResumeComplete message; 2> if the UE is configured to provide the measurement gap requirement information of NR target bands: 3> include the NeedForGapsInfoNR and set the contents as follows: 4> include intraFreq-needForGap and set the gap requirement information of intra-frequency measurement for each NR serving cell; 4> if requestedTargetBandFilterNR is configured, for each supported NR band that is also included in requestedTargetBandFilterNR, include an entry in interFreq-needForGap and set the gap requirement information for that band; otherwise, include an entry in interFreq-needForGap and set the corresponding gap requirement information for each supported NR band; 3> if the needForInterruptionConfigNR is enabled: 4> include the needForInterruptionInfoNR and set the contents as follows: 5> include intraFreq-needForInterruption with the same number of entries, and listed in the same order, as in intraFreq-needForGap; 5> for each entry in intraFreq-needForInterruption, include interruptionIndication and set the interruption requirement information if the corresponding entry in intraFreq-needForGap is set to no-gap; 5> include interFreq-needForInterruption with the same number of entries, and listed in the same order, as in interFreq-needForGap; 5> for each entry in interFreq-needForInterruption, include interruptionIndication and set the interruption requirement information if the corresponding entry in interFreq-needForGap is set to no-gap; 2> if the UE is configured to provide the measurement gap and NCSG requirement information of NR target bands: 3> include the NeedForGapNCSG-InfoNR and set the contents as follows: 4> include intraFreq-needForNCSG and set the gap and NCSG requirement information of intra-frequency measurement for each NR serving cell; 4> if requestedTargetBandFilterNCSG-NR is configured: 5> for each supported NR band included in requestedTargetBandFilterNCSG-NR, include an entry in interFreq-needForNCSG and set the NCSG requirement information for that band; 4> else: 5> include an entry for each supported NR band in interFreq-needForNCSG and set the corresponding NCSG requirement information; 2> if the UE is configured to provide the measurement gap and NCSG requirement information of E-UTRA target bands: 3> include the NeedForGapNCSG-InfoEUTRA and set the contents as follows: 4> if requestedTargetBandFilterNCSG-EUTRA is configured: 5> for each supported E-UTRA band included in requestedTargetBandFilterNCSG-EUTRA, include an entry in needForNCSG-EUTRA and set the NCSG requirement information for that band; 4> else: 5> include an entry for each supported E-UTRA band in needForNCSG-EUTRA and set the corresponding NCSG requirement information; 2> if the SIB1 contains musim-CapRestrictionAllowed and the UE capability is restricted for MUSIM operation: 3> if supported, include the musim-CapRestrictionInd in the RRCResumeComplete message upon determining it has temporary capability restriction; 2> if the UE has flight path information available: 3> include flightPathInfoAvailable; 1> submit the RRCResumeComplete message to lower layers for transmission; 1> the procedure ends. NOTE 2: Network only configures at most one of reportUplinkTxDirectCurrent, reportUplinkTxDirectCurrentTwoCarrier or reportUplinkTxDirectCurrentMoreCarrier in one RRC message. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.13.4 |
5,033 | – MIB | The MIB includes the system information transmitted on BCH. Signalling radio bearer: N/A RLC-SAP: TM Logical channel: BCCH Direction: Network to UE MIB -- ASN1START -- TAG-MIB-START MIB ::= SEQUENCE { systemFrameNumber BIT STRING (SIZE (6)), subCarrierSpacingCommon ENUMERATED {scs15or60, scs30or120}, ssb-SubcarrierOffset INTEGER (0..15), dmrs-TypeA-Position ENUMERATED {pos2, pos3}, pdcch-ConfigSIB1 PDCCH-ConfigSIB1, cellBarred ENUMERATED {barred, notBarred}, intraFreqReselection ENUMERATED {allowed, notAllowed}, spare BIT STRING (SIZE (1)) } -- TAG-MIB-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
5,034 | 4.2 Composition of the Routing Area Identification (RAI) | The Routing Area Identification shall be composed as shown in figure 4: Figure 4: Structure of Routing Area Identification The RAI is composed of the following elements: - A valid Location Area Identity (LAI) as defined in clause 4.1. Invalid LAI values are used in some special cases when no valid RAI exists in the mobile station (see 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [5], 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [27] and 3GPP TS 51.011[ Specification of the Subscriber Identity Module - Mobile Equipment (SIM-ME) interface ] [9]). - Routeing Area Code (RAC) which is a fixed length code (of 1 octet) identifying a routeing area within a location area. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.2 |
5,035 | 17.6.7 Abort-Session-Request Command | The Abort-Session-Request (ASR) command, defined in IETF RFC 6733 (DIAMETER BASE) [111], is indicated by the Command-Code set to 274 and the message flags’ ‘R’ bit set, is sent by the BM-SC to the GGSN to request that the session identified by the Session-Id be stopped. The relevant AVPs that are of use for the Gmb interface are detailed in the ABNF description below. Other valid AVPs for this command are not used for Gmb purposes and should be ignored by the receiver or processed according to the relevant specifications. Message Format <ASR> ::= < Diameter Header: 274, REQ, PXY > < Session-Id > { Origin-Host } { Origin-Realm } { Destination-Realm } { Destination-Host } { Auth-Application-Id } [ Origin-State-Id ] * [ Proxy-Info ] * [ Route-Record ] | 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.6.7 |
5,036 | 8.8.2.1 FDD | The parameters specified in Table 8.8.2.1-1 are valid for all FDD TM9 localized ePDCCH tests unless otherwise stated. Table 8.8.2.1-1: Test Parameters for Localized EPDCCH with TM9 For the parameters specified in Table 8.8.2.1-1 the average probability of a missed downlink scheduling grant (Pm-dsg) shall be below the specified value in Table 8.8.2.1-2. EPDCCH subframe monitoring is configured and the subframe monitoring requirement in EPDCCH restricted subframes is statDTX of 99.9%. The downlink physical setup is in accordance with Annex C.3.2. Table 8.8.2.1-2: Minimum performance Localized EPDCCH with TM9 | 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.8.2.1 |
5,037 | 16.14.7 O&M Requirements | The following NTN related parameters shall be provided by O&M to the gNB providing NTN access: - Ephemeris information describing the orbital trajectory information or coordinates for the NTN payload. This information is provided on a regular basis or upon demand to the gNB; - Two different sets of ephemeris format shall be supported: - Set 1: NTN payload position and velocity state vectors: - Position; - Velocity. - Set 2: At least the following parameters in orbital parameter ephemeris format, as specified in NIMA TR 8350.2 [51]: - Semi-major axis; - Eccentricity; - Argument of periapsis; - Longitude of ascending node; - Inclination; - Mean anomaly at epoch time. - The explicit epoch time associated to ephemeris data; - The location of the NTN Gateways; NOTE 1: The ephemeris of the NTN payloads and the location of the NTN Gateways, are used at least for the Uplink timing and frequency synchronization. It may also be used for the random access and the mobility management purposes. - Additional information to enable gNB operation for feeder/service link switch overs. NOTE 2: The NTN related parameters provided by O&M to the gNB may depend on the type of supported service links, i.e., Earth-fixed, quasi-Earth-fixed, or Earth-moving. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.14.7 |
5,038 | 8.13.2.1.4 Minimum Requirement Four-Layer Spatial Multiplexing 4 Tx Antenna Port | The purpose of these tests is to verify the closed loop rank-four performance with wideband precoding with 4Tx and 4Rx under CA. For CA with 2 DL CCs, the requirements are specified in Table 8.13.2.1.4-3, based on single carrier requirement specified in Table 8.13.2.1.4-2, with the addition of the parameters in Table 8.13.2.1.4-1 and the downlink physical channel setup according to Annex C.3.2. The test coverage for different number of component carriers is defined in 8.1.2.4. Table 8.13.2.1.4-1: Test Parameters for Multi-Layer Spatial Multiplexing (FRC) for CA Table 8.13.2.1.4-2: Single carrier performance for multiple CA configurations Table 8.13.2.1.4-3: Minimum performance (FRC) based on single carrier performance for CA with 2 DL CCs | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.13.2.1.4 |
5,039 | 8.11.2.1.4 CE Mode A with CRS interference model | The requirements are specified in Table 8.11.2.1.4-2, with the addition of parameters in Table 8.11.2.1.4-1. In Table 8.11.2.1.4-2, Cell 1 is the serving cell, and Cell 2 and Cell 3 are the aggressor cells. The downlink physical channel setup is according to Annex C.3.2 for each of Cell 1, Cell 2 and Cell 3, respectively. The CRS assistance information [7] is provided to the UE and includes information on Cell 2 and Cell 3. The purpose of the test is to verify the MPDCCH performance under assumption that UE applies CRS interference mitigation in the scenario with 2 CRS antenna ports in the serving and aggressor cells. Table 8.11.2.1.4-1: Test Parameters for MPDCCH Table 8.11.2.1.4-2: Minimum performance CE Mode A MPDCCH | 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.11.2.1.4 |
5,040 | 5.3.4.3 Network Triggered Service Request | Figure 5.3.4.3-1: Network triggered Service Request procedure If the MME needs to signal with the UE that is in ECM-IDLE state, e.g. to perform the MME/HSS-initiated detach procedure for the ECM-IDLE mode UE or the S-GW receives control signalling (e.g. Create Bearer Request or Update Bearer Request), the MME starts network triggered service request procedure from step 3a in the Network Triggered Service request procedure. If the MME wishes to use the Control Plane CIoT EPS Optimisation for mobile terminating services, then the procedure of clause 5.3.4B.3 is used to replace the procedure of this clause. If ISR is activated, when the Serving GW receives a Create Bearer Request or Update Bearer Request for a UE, and the S-GW does not have a downlink S1-U and the SGSN has notified the Serving GW that the UE has moved to PMM-IDLE or STANDBY state, the Serving GW buffers signalling messages and sends a Downlink Data Notification to trigger the MME and SGSN to page the UE. If the Serving GW, while waiting for the user plane to be established, is triggered to send a second Downlink Data Notification with higher priority (i.e. ARP priority level) than the first Downlink Data Notification was sent with, the Serving GW sends a new Downlink Data Notification message indicating the higher priority to the MME. If the Serving GW receives additional downlink signalling messages for a bearer with same or lower priority than the first Downlink Data Notification was sent for or if the Serving GW has sent the second Downlink Data Notification message indicating the higher priority and receives additional downlink signalling messages for this UE, the Serving GW buffers these downlink signalling messages and does not send a new Downlink Data Notification. The S-GW will be notified about the current RAT type based on the UE triggered service request procedure. The S-GW will go on executing the dedicated bearer activation or dedicated bearer modification procedure, i.e. send the corresponding buffered signalling to MME or SGSN which UE resides in now and inform the current RAT type to the PDN GW if the RAT type has been changed compared to the last reported RAT Type. If dynamic PCC is deployed, the current RAT type information shall also be conveyed from the PDN GW to the PCRF. If the PCRF response leads to an EPS bearer modification the PDN GW should initiate a bearer update procedure as specified in clause 5.4.2.1 below. When the Serving GW sends a Downlink Data Notification, it shall include both EPS Bearer ID and ARP. If the Downlink Data Notification is triggered by the arrival of downlink data packets at the Serving GW, the Serving GW shall include the EPS Bearer ID and ARP associated with the bearer on which the downlink data packet was received. If the Downlink Data Notification is triggered by the arrival of control signalling, the Serving GW shall include the EPS Bearer ID and ARP if present in the control signalling. If the ARP is not present in the control signalling, the Serving GW shall include the ARP in the stored EPS bearer context. If a LIPA PDN connection exists, when the L-GW receives the downlink data for a UE that is in ECM-IDLE state, the L-GW sends the first downlink user packet to Serving GW and buffers all other downlink user packets. The Serving GW will trigger the MME to page the UE. 1. When the Serving GW receives a downlink data packet/control signalling for a UE known as not user plane connected (i.e. the S-GW context data indicates no downlink user plane TEID), it buffers the downlink data packet and identifies which MME or SGSN is serving that UE. If that MME has requested the Serving GW to throttle downlink low priority traffic and if the downlink data packet is received on a low priority bearer to be throttled (see clause 4.3.7.4.1a), the SGW drops the downlink data. The steps below are not executed. If that MME has requested the S-GW to delay sending the Downlink Data Notification (see clause 5.3.4.2 on "Handling of abnormal conditions in UE triggered Service Request"), the Serving GW buffers the downlink data and waits until the timer expires before continuing with step 2. If the DL-TEID and eNodeB address for that UE is received before the expiry of the timer, the timer shall be cancelled and the Network triggered Service Request procedure is finished without executing the steps below, i.e. DL data are sent to the UE. If the Serving GW receives additional downlink data packets/control signalling for this UE before the expiry of the timer, the Serving GW does not restart this timer. 2. The Serving GW sends a Downlink Data Notification message (ARP, EPS Bearer ID, Paging Policy Indication) to the MME and SGSN nodes for which it has control plane connectivity for the given UE. The ARP and EPS Bearer ID are always set in Downlink Data Notification. The MME and SGSN respond to the S-GW with a Downlink Data Notification Ack message. When supporting Paging Policy Differentiation, the Serving GW indicates in the message the Paging Policy Indication related to the downlink data that triggered the Downlink Data Notification message, as described in clause 4.9. NOTE 1: The ARP, the EPS Bearer ID and optionally the Paging Policy Indication are sent to the SGSN as well as MME, but the usage of these parameters at SGSN is not specified in this release of the specification. An MME and an SGSN that detects that the UE is in a power saving state (e.g. Power Saving Mode or extended idle mode DRX) or is only in coverage intermittently (e.g. the UE is using satellite access with a known maximum interval between coverage occasions) and cannot be reached by paging at the moment, shall invoke extended buffering depending on operator configuration, except for cases described in next paragraphs. MME/SGSN derives the expected time before radio bearers can be established to the UE. The MME/SGSN then indicates DL Buffering Requested to the Serving GW in the Downlink Data Notification Ack message and includes a DL Buffering Duration time and optionally a DL Buffering Suggested Packet Count. The MME/SGSN stores a new value for the DL Data Buffer Expiration Time in the MM context for the UE based on the DL Buffering Duration time and skips the remaining steps of this procedure. The DL Data Buffer Expiration Time is used for UEs using power saving state or if the UE is only in coverage intermittently (e.g. the UE is using satellite access with a known maximum interval between coverage occasions) and indicates that there are buffered data in the Serving GW and that the user plane setup procedure is needed when the UE makes signalling with the network. When the DL Data Buffer Expiration Time has expired, the MME/SGSN considers no DL data to be buffered and no indications of Buffered DL Data Waiting are sent during context transfers at TAU procedures. If there is a "Availability after DDN Failure" monitoring event configured for the UE in the MME/SGSN, the MME/SGSN does not invoke extended buffering. Instead, the MME/SGSN sets the Notify-on-available-after-DDN-failure flag to remember to send an "Availability after DDN Failure" notification when the UE becomes available. If there is a "UE Reachability" monitoring event configured for the UE in the MME/SGSN, the MME/SGSN should not need to invoke extended buffering. NOTE 2: When "Availability after DDN failure" and "UE reachability" monitoring events are used for a UE, the application server is assumed to send data when the UE is reachable or about to become reachable, hence no extended buffering is needed. If there are multiple application servers, the event notifications and extended buffering may be needed simultaneously. It is assumed this is handled through additional information based on SLA as described in the next paragraph. The MME/SGSN may use additional information based on a SLA with the MTC user for when to invoke extended buffering, e.g. only invoke it for a certain APN, do not invoke it for certain subscribers, invoke extended buffering in conjunction with "Availability after DDN failure" and "UE reachability" monitoring events, etc. A Serving GW that receives a DL Buffering Requested indication in a Downlink Data Notification Ack message stores a new value for the DL Data Buffer Expiration Time based on the DL Buffering Duration time and does not send any additional Downlink Data Notification if subsequent downlink data packets are received in the Serving GW before the buffer time DL Data Buffer Expiration Time has expired for the UE. If the Serving GW, while waiting for the user plane to be established, is triggered to send a second Downlink Data Notification for a bearer with higher priority (i.e. ARP priority level) than the first Downlink Data Notification was sent for, the SGW sends a new Downlink Data Notification message indicating the higher priority to the MME. If the Serving GW receives additional downlink data packets for a bearer with same or lower priority than the first Downlink Data Notification was sent for or if the Serving GW has sent the second Downlink Data Notification message indicating the higher priority and receives additional downlink data packets for this UE, the Serving GW buffers these downlink data packets and does not send a new Downlink Data Notification. If the Serving GW, while waiting for the user plane to be established, receives a Modify Bearer Request message from MME or SGSN other than the one it sent a Downlink Data Notification message to, the Serving GW re-sends the Downlink Data Notification message only to the new MME or SGSN from which it received the Modify Bearer Request message even if ISR is active. If the Tracking Area Update procedure with MME change or the Routing Area Update procedure is in progress when the old MME receives a Downlink Data Notification message, the old MME may reject a Downlink Data Notification message with an indication that the Downlink Data Notification message has been temporarily rejected. Similarly, if the Routing Area Update procedure with SGSN change or the Tracking Area Update procedure is in progress when the old SGSN receives a Downlink Data Notification message, the old SGSN may reject a Downlink Data Notification message with an indication that the Downlink Data Notification message has been temporarily rejected. If the MME holds stored Paging Restriction Information (see clause 4.3.33.6) for the UE that restricts the Downlink Data from causing paging, the MME sends Downlink Data Notification Ack message with an indication that the Downlink Data Notification message has been temporarily rejected. Upon reception of a Downlink Data Notification Ack message with an indication that the Downlink Data Notification message has been temporarily rejected and if the Downlink Data Notification is triggered by the arrival of downlink data packets at the Serving GW, the Serving GW may start a locally configured guard timer and buffers all downlink user packets received to the given UE and waits for a Modify Bearer Request message to come. Upon reception of a Modify Bearer Request message, the Serving GW re-sends the Downlink Data Notification message only to the new MME or SGSN from which it received the Modify Bearer Request message even if ISR is active. Otherwise the Serving GW releases buffered downlink user packets at expiry of the guard timer or receiving the Delete Session Request message from MME/SGSN. Upon reception of a Downlink Data Notification Ack message with an indication that the Downlink Data Notification message has been temporarily rejected and if the Downlink Data Notification is triggered by the arrival of signalling messages at the Serving GW, the Serving GW may reject the PDN GW initiated EPS bearer(s) request with the same indication that the request has been temporarily rejected. Upon reception of a rejection for an EPS bearer(s) PDN GW initiated procedure with an indication that the request has been temporarily rejected, the PDN GW may start a locally configured guard timer. The PDN GW may re-attempt, up to a pre-configured number of times, when either it detects the UE accesses via a new SGW or at expiry of the guard timer. 3a. If the UE is registered in the MME and considered reachable for paging, the MME sends a Paging message (NAS ID for paging, TAI(s), UE identity based DRX index, Paging DRX length, list of CSG IDs for paging, Paging Priority indication, Enhanced Coverage Restricted, CE mode B Restricted, Assistance Data for Recommended Cells, WUS Assistance Information, Voice Service Indication) to each eNodeB belonging to the tracking area(s) in which the UE is registered. The step is described in detail in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [5] and TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [36]. Steps 3-4 are omitted if the MME already has a signalling connection over S1-MME towards the UE but the S1-U tunnel has not yet been established. If the MME holds stored Paging Restriction Information for the UE, the MME may block the paging for this UE, based on local policy and the stored Paging Restriction Information (see clause 4.3.33.6). If extended idle mode DRX is enabled for the UE, the MME pages the UE just before the occurrence of the UE's next paging occasion, which is determined as described in TS 23.682[ Architecture enhancements to facilitate communications with packet data networks and applications ] [74]. NOTE 3: Steps 3a and 4a are performed also when the UE and the network support User Plane CIoT EPS Optimisation and the previous RRC connection has been suspended. Paging priority indication is included only: - if the MME receives a Downlink Data Notification or Create/Update Bearer Request with an ARP priority level associated with MPS or other priority services, as configured by the operator. - One Paging Priority level can be used for multiple ARP priority level values. The mapping of ARP priority level values to Paging Priority level (or levels) is configured by operator policy. During a congestion situation the eNodeB may prioritise the paging of UEs according to the Paging Priority indications. If the MME, while waiting for a UE response to the Paging Request message sent without Paging Priority indication, receives an Update Bearer Request, Create Bearer Request or Downlink Data Notification, any of which indicates an ARP priority level associated with MPS or other priority services, as configured by the operator, the MME shall send another paging message with the suitable Paging Priority. When the MME is configured to support CSG paging optimisation in the CN, the MME should avoid sending Paging messages to those eNodeB(s) with CSG cells for which the UE does not have a CSG subscription. When the MME is configured to support CSG paging optimisation in the HeNB Subsystem, the list of CSG IDs for paging is included in the Paging message. For CSG paging optimisation, the CSG IDs of expired CSG subscriptions and valid CSG subscriptions are both included in the list. If the UE has emergency bearer service the MME shall not perform the CSG paging optimisation. NOTE 4: An expired CSG subscription indicates that the UE is not allowed service in the CSG. However, since the removal of the CSG from the UE is pending, it is possible the UE will camp on that CSG and therefore the UE is still paged for the CSG. NOTE 5: The eNodeB reports to the MME the CSG ID supported. For More detail of this procedure refer to TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [36]. When the MME supports SIPTO at Local Network and LIPA paging for traffic arriving on the PDN connection with L-GW function collocated with the (H)eNB the MME should only page this (H)eNB to avoid sending Paging messages to eNodeB(s) that are not handling this specific PDN connection. Paging strategies may be configured in the MME for different combinations of APN, Paging Policy Indication from SGW when available (see clause 4.9) and other EPS bearer context information e.g. QCI. APN and any EPS bearer context information are identified by EPS bearer ID received in Downlink Data Notification. Paging strategies may include: - paging retransmission scheme (e.g. how frequently the paging is repeated or with what time interval); - determining whether to send the Paging message to the eNodeBs during certain MME high load conditions; - whether to apply sub-area based paging (e.g. first page in the last known ECGI or TA and retransmission in all registered TAs). If extended idle mode DRX was enabled in the UE, the MME may additionally take into account the Paging Time Window length for paging retransmission schemes. NOTE 6: The Paging priority in the Paging message is set based on priority level of the ARP IE received in Downlink Data Notification or Create/Update Bearer Request message and is independent from any paging strategy. The MME and the E-UTRAN may support further paging optimisations in order to reduce the signalling load and the network resources used to successfully page a UE by one or several following means: - by the MME implementing specific paging strategies (e.g. the S1 Paging message is sent to the eNodeB that served the UE last); - by the MME considering Information On Recommended Cells And eNodeBs provided by the E-UTRAN at transition to ECM IDLE. The MME takes the eNodeB related part of this information into account to determine the eNodeBs to be paged, and provides the information on recommended cells within the S1 Paging message to each of these eNodeBs; - by the E-UTRAN considering the Paging Attempt Count Information provided by the MME at paging. When implementing such optimisations/strategies, the MME shall take into account any PSM active timer and the DRX interval for the UE. The MME shall ensure that the correct Paging DRX Length is provided based on the accepted UE Specific DRX of the current RAT. If the UE Radio Capability for Paging Information is available in the MME for the RAT corresponding to the TAI(s) in the S1 Paging message, the MME shall add the UE Radio Capability for Paging Information for that RAT in the S1 Paging message to the eNodeB. If the Information On Recommended Cells And eNodeBs For Paging is available in the MME, the MME shall take that information into account to determine the eNodeBs for paging and, when paging an eNodeB, the MME may transparently convey the information on recommended cells to the eNodeB. The MME may include in the S1AP Paging message(s) the paging attempt count information. The paging attempt count information shall be the same for all eNodeBs selected by the MME for paging. The MME may include in the S1AP Paging message(s) the WUS Assistance Information, if available. If the MME has Information for Enhanced Coverage stored and Enhanced Coverage is not restricted then the MME shall include Information for Enhanced Coverage in the Paging message for all eNodeBs selected by the MME for paging. For including the Enhanced Coverage Restricted parameter in the paging message, see clause 4.3.28. For including the CE mode B Restricted parameter in the Paging message, see clause 4.3.27a. If the network supports the Paging Cause Indication for Voice Service feature if the UE context in the MME indicates that the UE supports the Paging Cause for Voice Service feature, the MME should provide the Voice Service Indication in the S1AP Paging message only when the MME detects that the downlink data which triggers the Paging message is related to voice service, as specified in clause 4.3. 3b. If the UE is registered in the SGSN, the SGSN sends paging messages to RNC/BSS, which is described in detail in TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [7]. 4a. If eNodeBs receive paging messages from the MME, the UE is paged by the eNodeBs. The step is described in detail in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [5] and TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [34]. If the WUS Assistance Information is included in Step 3a, the eNodeB takes it into account when paging the UE (see TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [5]). If the UE and eNodeB support WUS, then: - if the S1-AP Paging message contains the Assistance Data for Recommended Cells IE (see TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [36]), the eNodeB shall only broadcast the UE's Wake Up Signal in the last used cell; - else (i.e. the Assistance Data for Recommended Cells IE is not included in the S1-AP Paging message) the eNodeB should not broadcast the UE's Wake Up Signal. If the Voice Service Indication is included in step 3a, the eNodeB supporting the Paging Cause Indication for Voice Service feature should include the Voice Service Indication in the paging message to the UE, see TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [5]. 4b. If RNC/BSS nodes receive paging messages from the SGSN the UE is paged by the RNSC/BSS, which is described in detail in TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [7]. 5. When UE is in the ECM-IDLE state, upon reception of paging indication in E-UTRAN access, the UE initiates the UE triggered Service Request procedure (clause 5.3.4.1) or, if the UE is enabled to use User Plane CIoT EPS Optimisation and there is suspended access stratum context stored in the UE, the UE initiates the Connection Resume procedure (clause 5.3.5A). If the MME already has a signalling connection over S1-MME towards the UE but the S1-U tunnel has not yet been established, then the messages sequence performed start from the step when MME establishes the bearer(s). If the Multi-USIM UE is in ECM-IDLE state, upon reception of paging indication in E-UTRAN access and if the UE decides not to accept the paging, the UE attempts to send a Reject Paging Indication via the UE Triggered Service Request procedure (clause 5.3.4.1) unless it is unable to do so, e.g. due to UE implementation constraints. Upon reception of paging indication in UTRAN or GERAN access, the MS shall respond in respective access as specified TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [47] and the SGSN shall notify the S-GW. The MME and/or SGSN supervises the paging procedure with a timer. If the MME and/or SGSN receives no response from the UE to the Paging Request message, it may repeat the paging according to any applicable paging strategy described in step 2. If the MME and/or SGSN receives no response from the UE after this paging repetition procedure, it shall use the Downlink Data Notification Reject message to notify the Serving GW about the paging failure, if paging was triggered by a Downlink Data Notification message, unless the MME or SGSN is aware of an ongoing MM procedure that prevents the UE from responding, i.e. the MME or SGSN received a Context Request message indicating that the UE performs TAU or RAU procedure with another MME or SGSN. If paging was triggered by control signalling from the Serving GW and if the MME or SGSN receives no response from the UE after this paging repetition procedure, the MME or SGSN shall reject that control signalling. When a Downlink Data Notification Reject message is received, if ISR is not activated, the Serving GW deletes the buffered packet(s). If ISR is activated and the Serving GW receives Downlink Data Notification Reject message from both SGSN and MME, the Serving GW deletes the buffered packet(s) or rejects the control signalling which triggers the Service Request procedure. The Serving GW may invoke the procedure PDN GW Pause of Charging (clause 5.3.6A) if UE is in ECM IDLE and the PDN GW has enabled "PDN charging pause" feature. NOTE 7: The Serving GW may initiate the procedure PDN GW Pause of Charging at any time before step 5 if the UE is in ECM IDLE and the PDN GW has indicated that the feature is enabled for this PDN. See clause 5.3.6A. 5a. After receiving the Reject Paging Indication, the MME uses the Downlink Data Notification Failure Indication message to notify the Serving GW that the UE rejected the page and no user plane radio bearers will be established. The UE remains reachable for future paging attempts based on stored (if any) Paging Restriction Information. 6a. If ISR is activated and paging response is received in E-UTRAN access the Serving GW sends a "Stop Paging" message to the SGSN. 6b. If ISR is activated and paging response is received in UTRAN or GERAN access the Serving GW sends a "Stop Paging" message to the MME. The Serving GW transmits downlink data towards the UE via the RAT which performed the Service Request procedure. For a LIPA PDN connection, after the UE enters connected mode, the packets buffered in the L-GW are forwarded to the HeNB on the direct path. If the UE enters connected mode at a different cell than the one where the L-GW is collocated, the MME shall deactivate the LIPA PDN connection as defined in clause 5.3.4.1 step 2. If the network triggered service request fails due to no response from the UE, then MME and/or SGSN may be based on operator policy initiate the Dedicated Bearer Deactivation procedure for preserved GBR bearers. For details, see clause 5.4.4.2 for MME and TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [7] for SGSN. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.3.4.3 |
5,041 | 5.8.3 Sidelink UE information for NR sidelink communication/discovery/positioning 5.8.3.1 General | Figure 5.8.3.1-1: Sidelink UE information for NR sidelink communication/discovery The purpose of this procedure is to inform the network that the UE: - is interested or no longer interested to receive or transmit NR sidelink communication/discovery/positioning, - is requesting assignment or release of transmission resource for NR sidelink communication/discovery/positioning, - is reporting QoS parameters and QoS profile(s) related to NR sidelink communication, - is reporting mapped frequency(ies) for each QoS flow related to NR sidelink communication, - is reporting associated Tx Profile for each QoS flow related to NR sidelink communication, - is reporting that a sidelink radio link failure, sidelink RRC reconfiguration failure or a sidelink carrier failure has been detected, - is reporting the sidelink UE capability information of the associated peer UE for unicast communication, - is reporting the RLC mode information of the sidelink data radio bearer(s) received from the associated peer UE for unicast communication, - is reporting the accepted sidelink DRX configuration received from the associated peer UE for NR sidelink unicast reception, - is reporting the sidelink DRX assistance information received from the associated peer UE for NR sidelink unicast transmission, when the UE is configured with sl-ScheduledConfig, - is reporting, for NR sidelink groupcast transmission, the sidelink DRX on/off indication for the associated Destination Layer-2 ID, when the UE is configured with sl-ScheduledConfig, - is reporting, for NR sidelink groupcast or broadcast reception, the Destination Layer-2 ID and QoS profile(s) associated with its interested services to which sidelink DRX is applied, - is reporting DRX configuration reject information from its associated peer UE for NR sidelink unicast transmission, when the UE is configured with sl-ScheduledConfig, - is reporting parameters related to U2N relay operation, - is reporting parameters related to U2U relay operation. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.8.3 |
5,042 | 6.3.9 UDR discovery and selection | Multiple instances of UDR may be deployed, each one storing specific data or providing service to a specific set of NF consumers as described in clause 4.2.5. In segmented UDR deployment, different instances of UDR store the data for different Data Sets and Data Subsets or for different users. A UDR instance can also store application data that applies on any UE, i.e. all subscribers of the PLMN. If the NF service consumer performs discovery and selection, the NF consumer shall utilize the NRF to discover the appropriate UDR instance(s) unless UDR instance information is available by other means, e.g. locally configured on NF consumer. The UDR selection function in NF consumers is applicable to both 3GPP access and non-3GPP access. The NF consumer or the SCP shall select a UDR instance that contains relevant information for the NF consumer, e.g. UDM/SCP selects a UDR instance that contains subscription data, while NEF/SCP (when used to access data for exposure) selects a UDR that contains data for exposure; or PCF/SCP selects a UDR that contains Policy Data and/or Application Data. The UDR selection function in UDR NF consumers considers the Data Set Identifier of the data to be managed in UDR (see UDR service definition in clause 5.2.12 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]). Additionally, the UDR selection function in UDR NF consumers should consider one of the following factors when available to the UDR NF consumer when selecting a UDR that stores the required Data Set(s) and Data Subset(s): 1. UDR Group ID the UE's SUPI belongs to. 2. SUPI; e.g. the UDR NF consumer selects a UDR instance based on the SUPI range the UE's SUPI belongs to or based on the results of a discovery procedure with NRF using the UE's SUPI as input for UDR discovery. 3. GPSI or External Group ID; e.g. UDR NF consumers select a UDR instance based on the GPSI or External Group ID range the UE's GPSI or External Group ID belongs to or based on the results of a discovery procedure with NRF using the UE's GPSI or External Group ID as input for UDR discovery. 4. UDR capability to store application data that is applicable on any UE (i.e. all subscribers of the PLMN). In the case of delegated discovery and selection, the NF consumer shall include the available factors in the request towards SCP. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 6.3.9 |
5,043 | 7.10 Fallback to GTPv1 mechanism | An EPC entity shall assume that each GTP processing node that it is about to communicate with is GTPv2 capable. Before the first GTP tunnel is setup for a given UE/node, the EPC node shall always send a version 2 (GTPv2) message to a peer node. As an exception, during an inter-SGSN handover, even if the target SGSN is GTPv2 capable, the source SGSN shall send a GTPv1 message "Forward Relocation Request" to the target SGSN if the PDP Context(s) for this UE were established to GGSN(s), or if there is no active PDP context and the source or target SGSN does not support SRNS relocation w/o PDN connection over GTPv2 (see clause 7.3.1). A GTPv2 entity shall fallback to GTPv1 only if either a "Version Not Supported" message in GTPv1 format as specified in 3GPP TS 29.060[ General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp interface ] [4] is received from the peer node (this indicates that the peer GTP entity does not support GTPv2), or if a GTPv2 message is received with Cause value "Fallback to GTPv1". If a GTPv1 "Version Not Supported" message in received, a GTPv2 entity may fallback to GTPv1. 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [3] (see annex D) and 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [35] specify GTP version usage during the mobility between a UTRAN/GERAN and an E-UTRAN. A GTPv2 entity may receive a GTPv2 message with a Cause value "Fallback to GTPv1" in the following cases: - an S4 SGSN receives the Cause code "Fallback to GTPv1" in a GTPv2 Context Response message over S16 interface. When an UE has activated a PDP context via S4 SGSN to GGSN and inter-SGSN RAU is underway, the old S4 SGSN shall include the Cause value "Fallback to GTPv1" in a GTPv2 Context Response message over S16 interface. In this case, the new S4 SGSN shall abort the ongoing GTPv2 procedure and send a GTPv1 "SGSN Context Request" message to the old S4 SGSN. The fallback to GTPv1 is performed only for this UE in the current procedure. - an MME receives the Cause code "Fallback to GTPv1" in a GTPv2 Context Response message over the S3 interface. When an UE has active PDP context(s) via an S4 SGSN and a TAU is underway, the old S4 SGSN may include the Cause value "Fallback to GTPv1" in a GTPv2 Context Response message over the S3 interface. In this case, the MME shall abort the ongoing GTPv2 procedure and should send a GTPv1 "SGSN Context Request" message to the old S4 SGSN. The fallback to GTPv1 is performed only for this UE. Fallback to GTPv1 shall not occur on already established GTP tunnels without change of the peer nodes of the communication bearer. | 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.10 |
5,044 | 4.16.6 SM Policy Association Termination | Figure 4.16.6-1: SM Policy Association Termination This procedure concerns both roaming and non-roaming scenarios. In the non-roaming case the V-PCF is not involved. In the local breakout roaming case, the H-PCF is not involved. In the home routed roaming case, the V-PCF is not involved and the H-PCF interacts only with the H-SMF. The procedure for Session Management Policy Termination may be initiated by: - (Case A) the PCF. - (Case B) the SMF. For local breakout roaming, the interaction with HPLMN (e.g. step 6) is not used. In local breakout roaming, the V-PCF interacts with the UDR of the VPLMN. 1. (Case A) The PCF may invoke the Npcf_SMPolicyControl_UpdateNotify service operation to request the release of a PDU Session. The SMF acknowledges the request. The rest of the procedure corresponds to both Case A &B. 2. The SMF may invoke the Npcf_SMPolicyControl_Delete service operation to request the deletion of the SM Policy Association with the PCF. The SMF provides relevant information to the PCF. 3. When receiving the request from step2, the PCF finds the PCC Rules that require an AF to be notified and removes PCC Rules for the PDU Session. If the SMF reported accumulated usage for the PDU session in step 1 the PCF deducts the value from the remaining allowed usage for the subscriber, DNN and S-NSSAI in the UDR by invoking Nudr_DM_Update (SUPI, DNN, S-NSSAI, Policy Data, Remaining allowed Usage data, updated data) service operation. If the SMF reported accumulated usage for a MK(s) in step 1 the PCF deducts the value from the remaining allowed usage for the MK in the UDR by invoking Nudr_DM_Update (SUPI, DNN, S-NSSAI, Policy Data, Remaining allowed Usage data, updated data (including MK(s))) service operation. NOTE: For local breakout roaming, PDU Session policy control subscription information and Remaining allowed usage subscription information for monitoring control as defined in clause 6.2.1.3 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20] are not available in V-UDR and V-PCF uses locally configured information according to the roaming agreement with the HPLMN operator. 4. The SMF removes all policy information about the PDU Session associated with the PDU Session. 5. The PCF notifies the AF as explained in clause 7.3.1 steps 6-7 of TS 23.203[ Policy and charging control architecture ] [24]. The PCF may invoke Nbsf_Management_Deregister service operation to delete the binding created in BSF. The PCF may report that a SM Policy Association is terminated as described in clause 4.16.14.2. In the non-roaming case, the PCF may unsubscribe to analytics from NWDAF. 6. The PCF may invoke the procedure defined in clause 4.16.8 to unsubscribe to policy counter status reporting (If this is the last PDU Session for this subscriber requiring policy counter status reporting) or to modify the subscription to policy counter status reporting, (if any remaining existing PDU Sessions for this subscriber requires policy counter status reporting). 7. The PCF removes the information related to the terminated PDU Session and acknowledges to the SMF that the PCF handling of the PDU Session has terminated. This interaction is the response to the SMF request in step 2. 8. The PCF may (e.g. if it is the last PDU Session on the (DNN, S-NSSAI) couple) unsubscribe to the notification of the PDU Session related data modification from the UDR by invoking Nudr_DM_Unsubscribe (Subscription Correlation Id) if it had subscribed such notification. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.16.6 |
5,045 | 6.5.2G Transmit modulation quality for V2X Communication | The requirements in this clause apply to V2X sidelink transmissions. 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.5.2G apply for V2X sidelink transmission and the requirements in subclause 6.5.2 apply for the E-UTRA uplink transmission. For V2X UE supporting Transmit Diversity, if the UE transmits on two antenna-connectors at the same time, the transmit modulation quality requirements for single carrier shall apply to each transmit antenna connector. If V2X UE transmits on one-antenna connector at a time, the requirements specified for single carrier apply to the active antenna connector. | 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.5.2G |
5,046 | 9.9.4.13A Re-attempt indicator | The purpose of the Re-attempt indicator information element is to indicate a condition under which the UE is allowed, in the current PLMN for the same APN, to re-attempt a session management procedure (see 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13]) corresponding to the EPS session management procedure which was rejected by the network. The Re-attempt indicator information element is coded as shown in figure 9.9.4.13A/3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] and table 9.9.4.13A/3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] . The Re-attempt indicator is a type 4 information element with a length of 3 octets. Figure 9.9.4.13A: Re-attempt indicator information element Table 9.9.4.13A: Re-attempt indicator information element | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.9.4.13A |
5,047 | 4.6.3.3 Session management based network slice data rate limitation control | A serving PLMN or the HPLMN can perform network slice data rate limitation control for the S-NSSAI(s) subject to network slice data rate limitation control to monitor and control the total data rate of established PDU sessions per network slice as specified in 3GPP TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [10]. If the maximum data rate of PDU sessions on a network slice associated with an S-NSSAI has been exceeded during the PDU session establishment procedure, the SMF may reject the PDU session establishment request using S-NSSAI based congestion control as specified in subclause 6.2.8 and 6.4.1.4.2. A serving PLMN or the HPLMN can perform management of Slice-Maximum Bit Rate per UE (UE-Slice-MBR) as specified in 3GPP TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [10]. When the UE-Slice-MBR for the UE and S-NSSAI to which the PDU session is allocated is exceeded during the PDU session establishment procedure, the SMF may reject the PDU session establishment request using S-NSSAI based congestion control as specified in subclause 6.2.8 and 6.4.1.4.2. NOTE 1: Based on operator policy, the network slice data rate limitation control can be not applicable for the S-NSSAI(s) used for emergency services or priority services. NOTE 2: The network slice data rate limitation control and UE-Slice-MBR management are performed by the PCF. | 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.3.3 |
5,048 | 19.3.2 Root NAI | The Root NAI shall take the form of an NAI, and shall have the form username@realm as specified in clause 2.1 of IETF RFC 4282 [53]. When the username part is the IMSI, the realm part of Root NAI shall be built according to the following steps: 1. Convert the leading digits of the IMSI, i.e. MNC and MCC, into a domain name, as described in clause 19.2. 2. Prefix domain name with the label of "nai". The resulting realm part of the Root NAI will be in the form: "@nai.epc.mnc<MNC>.mcc<MCC>.3gppnetwork.org" When including the IMSI, the Root NAI is prepended with a specific leading digit when used for EAP authentication (see 3GPP TS 29.273[ Evolved Packet System (EPS); 3GPP EPS AAA interfaces ] [78]) in order to differentiate between EAP authentication method. The leading digit is: - "0" when used in EAP-AKA, as specified in IETF RFC 4187 [50] - "6" when used in EAP-AKA', as specified in IETF RFC 5448 [82]. The resulting Root NAI will be in the form: "0<IMSI>@nai.epc.mnc<MNC>.mcc<MCC>.3gppnetwork.org" when used for EAP AKA authentication "6<IMSI>@nai.epc.mnc<MNC>.mcc<MCC>.3gppnetwork.org" when used for EAP AKA' authentication For example, if the IMSI is 234150999999999 (MCC = 234, MNC = 15), the Root NAI takes the form [email protected] for EAP AKA authentication and the Root NAI takes the form [email protected] for EAP AKA' authentication. The NAI sent in the Mobile Node Identifier field in PMIPv6 shall not include the digit prepended in front of the IMSI based username that is described above. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 19.3.2 |
5,049 | 5.2.2.2.21 Namf_Communication_RelocateUEContext service operation | Service operation name: Namf_Communication_RelocateUEContext Description: This service operation is used by an initial AMF to relocate the UE context in a target AMF during EPS to 5GS handover (per N26) procedures. Input, Required: UE context of the identified UE, Source to Target RAN Transparent Container and the identification of target RAN, PDU Session ID and its associated S-NSSAI of the VPLMN value for each PDU Session, the corresponding S-NSSAI of HPLMN value for home routed PDU Session(s), content for EPS to 5GS handover (information to reach the MME about this UE (MME Control Plane F-TEID, MME addressing information), PDU Session ID and the S-NSSAI associated with corresponding N2 SM Information received from SMF). As described in Table 5.2.2.2.2-1, the UE context may include the SUPI, DRX parameters, AM policy information, UE Radio Capability ID, PCF ID, UE network capability, used N1 security context information, event subscriptions by other consumer NF, Allowed NSSAI received from NSSF and the list of SM PDU Session IDs with the corresponding SMF handling the PDU Session, the S-NSSAI of the VPLMN and the S-NSSAI of HPLMN for home routed PDU Session(s). Input, Optional: This may contain following optional information within the UE context: allocated EBI information, MS Classmark 2, STN-SR, C MSISDN and the Supported Codec IE. Output, Required: Cause, handle for the UE context created. Output, Optional: None. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.2.2.21 |
5,050 | 8.2.1.5 Inter-gNB-DU LTM | This procedure is used for the case when the UE moves from one gNB-DU to another gNB-DU within the same gNB-CU during NR operation for LTM. Figure 8.2.1.5-1 shows the inter-gNB-DU LTM procedure for intra-NR. Figure 8.2.1.5-1: Inter-gNB-DU LTM 1. The UE sends a MeasurementReport message (L3 measurement result) to the source gNB-DU containing measurements of neighbouring cells. The source gNB-DU sends an UL RRC MESSAGE TRANSFER message conveying the received MeasurementReport message to the gNB-CU. 2. The gNB-CU determines to initiate LTM configuration. 3. The gNB-CU sends a UE CONTEXT SETUP REQUEST message to the candidate gNB-DU(s), containing one target candidate cell ID, the LTM configuration ID of the candidate cell, LTM configuration ID mapping list, and the CSI resource configuration. The gNB-CU indicates the source gNB-DU ID, and requests PRACH resources from the candidate gNB-DU. The gNB-CU may request the candidate gNB-DU to provide the lower layer configuration for the purpose of generating the reference configuration. 4. If the candidate gNB-DU accepts the request of LTM configuration, it responds with a UE CONTEXT SETUP RESPONSE message including the generated lower layer RRC configurations (e.g., TCI state configuration, RACH configuration, and the CSI report configuration) for the accepted target candidate cell. NOTE 1: The CU-initiated UE Context Modification procedure may be initiated for preparing candidate cells in the source gNB-DU as specified in step 3 and 4 in 8.2.1.4 Intra-gNB-DU LTM. 5. The gNB-CU sends a UE CONTEXT MODIFICATION REQUEST message to the source gNB-DU including the collected CSI report configuration, RACH configuration and the TCI state configuration for the accepted target candidate cell(s) in other gNB-DU(s). 6. The source gNB-DU responds with a UE CONTEXT MODIFICATION RESPONSE message which includes an updated lower layer configuration, e.g., containing the CSI report configuration. 7. The gNB-CU sends a UE CONTEXT MODIFICATION REQUEST message to the candidate gNB-DU(s) containing the CSI report configuration, TCI state information, RACH Configuration, and the LTM configuration IDs of the candidate cells in other candidate gNB-DU(s). The gNB-CU may also provide the lower layer part of the reference configuration to the candidate gNB-DU(s). The gNB-CU may also provide an updated CSI resource configuration to the candidate gNB-DU(s). NOTE 2: The candidate cell may be the same cell as source cell. 8. The candidate gNB-DU responds with a UE CONTEXT MODIFICATION RESPONSE message including the updated lower layer configuration. The candidate gNB-DU may also respond the updated CSI report configuration. 9. The gNB-CU sends a DL RRC MESSAGE TRANSFER message to the source gNB-DU, which includes the generated RRCReconfiguration message with the LTM configuration. 10. The source gNB-DU forwards the received RRCReconfiguration message to the UE. 11. The UE responds to the source gNB-DU with an RRCReconfigurationComplete message. 12. The source gNB-DU forwards the RRCReconfigurationComplete message to the gNB-CU via an UL RRC MESSAGE TRANSFER message. 13. Early synchronization may be performed as specified in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [2]. 14 - 15. The candidate gNB-DU sends the TA value, the associated CFRA resource information, the candidate cell ID and the source gNB-DU ID to the source gNB-DU via the DU-CU TA INFORMATION TRANSFER and CU-DU TA INFORMATION TRANSFER messages, for which the source gNB-DU ID is omitted in the CU-DU TA INFORMATION TRANSFER message. 16. The UE sends the L1 measurement result to the source gNB-DU. 17. The source gNB-DU decides to execute LTM to a candidate target cell. 18. The source gNB-DU sends the Cell Switch command to the UE. 19. The source gNB-DU sends the DU-CU CELL SWITCH NOTIFICATION message to the gNB-CU to indicate the initiation of the Cell Switch command to the UE, for which the message includes the target cell ID and the TCI state ID. 20. The gNB-CU forwards the target cell ID and the TCI state ID to the target gNB-DU in the CU-DU CELL SWITCH NOTIFICATION message. 21. The target gNB-DU detects the UE access as specified in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [2]. 22. The target gNB-DU sends the ACCESS SUCCESS message to the gNB-CU with the target cell ID. 23. The UE sends an RRCReconfigurationComplete message to the target gNB-DU. 24. The target gNB-DU forwards the RRCReconfigurationComplete message to the gNB-CU via an UL RRC MESSAGE TRANSFER message. 25. The gNB-CU may send the UE CONTEXT RELEASE COMMAND message to the source gNB-DU to release the resources of prepared cells. 26. The source gNB-DU responds with a UE CONTEXT RELEASE COMPLETE message. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 8.2.1.5 |
5,051 | 6.3.12a.2 Access Network Selection Procedure | The steps executed by a N5CW device for access network selection are specified below and are very similar with the corresponding steps executed by a UE that supports NAS; see clause 6.3.12.2. Step 1: The N5CW device constructs a list of available PLMNs. This list contains the PLMNs included in the PLMN List-4 advertised by all discovered WLAN access networks. a. The N5CW device discovers the PLMN List-4 advertised by all discovered WLAN access networks by sending an ANQP query to each discovered WLAN access network. The ANQP query shall request "3GPP Cellular Network" information. If a WLAN access network supports interworking with one or more PLMNs, the ANQP response received by the N5CW device includes a "3GPP Cellular Network" information element containing one or more of the following lists: PLMN List-1, PLMN List-2, PLMN List-3 and PLMN List-4. The PLMN List-1, PLMN List-2 and PLMN List-3 are defined in clause 6.3.12. The PLMN List-4 includes the PLMNs with which "5G connectivity-without-NAS" is supported. Step 2: The N5CW device selects a PLMN that is included in the list of available PLMNs as follows. a. If the N5CW device is connected to a PLMN via 3GPP access and this PLMN is included in the list of available PLMNs, then the N5CW device selects this PLMN. b. Otherwise (the N5CW device is not connected to a PLMN via 3GPP access, or the N5CW device is connected to a PLMN via 3GPP access but this PLMN is not in the list of available PLMNs): i) If the N5CW device determines to be located in its home country, then: - The N5CW device selects the HPLMN if the N5CW device has a USIM or is pre-configured with an HPLMN, if the HPLMN is included in the list of available PLMNs. Otherwise, the N5CW device selects an E-HPLMN (Equivalent HPLMN), if an E-HPLMN is included in the list of available PLMNs. If the list of available PLMNs does not include the HPLMN and does not include an E-HPLMN, the N5CW device stops the access network selection procedure. ii) If the N5CW device determines to be located in its visited country, then: - The N5CW device determines if it is mandatory to select a PLMN in the visited country, as follows: - If the N5CW device has IP connectivity (e.g. it is connected via 3GPP access), the N5CW device sends a DNS query and receives a DNS response that indicates if a PLMN must be selected in the visited country. The DNS response includes a lifetime that denotes how long the DNS response can be cached. - If the N5CW device has no IP connectivity (e.g. it is not connected via 3GPP access), then the N5CW device may use a cached DNS response that was received in the past, or may use local configuration that indicates which visited countries mandate a PLMN selection in the visited country. - If the N5CW device determines that it is not mandatory to select a PLMN in the visited country, and the HPLMN or an E-HPLMN is included in the list of available PLMNs, then the N5CW device selects the HPLMN or an E-HPLMN, whichever is included in the list of available PLMNs. - Otherwise, the N5CW device selects a PLMN in the visited country as follows: - If the N5CW device has a USIM, the UE selects a PLMN in the visited country by considering, in priority order, the PLMNs, first, in the User Controlled PLMN Selector list and, next, in the Operator Controlled PLMN Selector list (see TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [17]). - If the N5CW device does not have a USIM, the N5CW device selects the highest priority PLMN in a pre-configured list, which is also included in the list of available PLMNs. - If the list of available PLMNs does not include a PLMN that is also included in the pre-configured list(s), the N5CW device either stops the access network selection procedure, or may select a PLMN based on its own implementation. Step 3: Finally, the N5CW device selects a WLAN access network (e.g. an SSID) to connect to, following the procedure specified in clause 6.6.1.3 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45], "UE procedure for selecting a WLAN access based on WLANSP rules", or any other implementation specific means. After the N5CW device completes the above access network selection procedure, the N5CW device initiates the "Initial Registration and PDU Session Establishment" procedure specified in clause 4.12b.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 6.3.12a.2 |
5,052 | 5.3.5.17.3.2 N3C remote UE configuration | The N3C remote UE shall: 1> if n3c-IndirectPathAddChange is set to setup: 2> consider the non-3GPP connection with the relay UE indicated by the n3c-RelayIdentification to be used for the N3C indirect path; 2> consider the source non-3GPP connection is not to be used in case of N3C indirect path change (i.e. a new relay UE is indicated by the n3c-RelayIdentification); 1> else if n3c-IndirectPathAddChange is set to release: 2> consider the indirect path is not to be used and release the corresponding configuration. Editor's Note: whether T421 is applicable to scenario 2. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.5.17.3.2 |
5,053 | 6.6.2G Out of band emission for V2X Communication | 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 requirements in subclause 6.6.2 apply except for the ACLR requirements for power class 2 V2X UE. 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.6.2 apply per V2X sidelink transmission and E-UTRA uplink transmission as specified for the corresponding inter-band con-current operation with uplink assigned to two bands. For intra-band contiguous multi-carrier operation, the general CA spectrum emission mask for CA Bandwidth Class B specified in subclause 6.6.2.1A shall apply for V2X Bandwdith Class B, the general CA spectrum emission mask for CA Bandwidth Class C specified in subclause 6.6.2.1A shall apply for V2X Bandwdith Class C and C1. For intra-band contiguous multi-carrier operation, the E-UTRA ACLR requirment for CA Bandwidth Class B specified in subclause 6.6.2.3.3A shall apply for V2X Bandwdith Class B, the general CA spectrum emission mask for CA Bandwidth Class C specified in subclause 6.6.2.3.3A shall apply for V2X Bandwdith Class C and C1. For power class 2 V2X UE, the assigned channel power and adjacent channel power are measured with rectangular filters with measurement bandwidths specified in Table 6.6.2G-1. If the measured adjacent channel power is greater than –50dBm then ACLR shall be higher than the value specified in Table 6.6.2G-1. Table 6.6.2G-1: ACLR requirements for power class 2 V2X Communication For V2X UE supporting Transmit Diversity, if the UE transmits on two antenna connectors at the same time, the requirements specified for single carrier apply to each transmit antenna connector. If V2X UE transmits on one antenna connector at a time, the requirements specified for single carrier shall apply to the active antenna connector. | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.6.2G |
5,054 | – ControlResourceSetId | The ControlResourceSetId IE concerns a short identity, used to identify a control resource set within a serving cell. The ControlResourceSetId = 0 identifies the ControlResourceSet#0 configured via PBCH (MIB) and in controlResourceSetZero (ServingCellConfigCommon). The ID space is used across the BWPs and MBS CFRs of a Serving Cell. ControlResourceSetId information element -- ASN1START -- TAG-CONTROLRESOURCESETID-START ControlResourceSetId ::= INTEGER (0..maxNrofControlResourceSets-1) ControlResourceSetId-r16 ::= INTEGER (0..maxNrofControlResourceSets-1-r16) ControlResourceSetId-v1610 ::= INTEGER (maxNrofControlResourceSets..maxNrofControlResourceSets-1-r16) -- TAG-CONTROLRESOURCESETID-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
5,055 | 10.5.3.16 MM Timer | The purpose of the MM timer information element is to specify MM specific timer values, e.g. for the timer T3246. The MM timer is a type 4 information element with 3 octets length. The MM timer information element is coded as shown in figure 10.5.3.16-1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.3.16-1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Figure 10.5.3.16-1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : MM Timer information element Table 10.5.3.16-1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : MM Timer 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.16 |
5,056 | 4.4.2.5 Derivation of keys at CS to PS SRVCC handover from A/Gb mode to S1 mode or from Iu mode to S1 mode | At change from A/Gb mode to S1 mode or from Iu mode to S1 mode due to CS to PS SRVCC handover (see 3GPP TS 23.216[ Single Radio Voice Call Continuity (SRVCC); Stage 2 ] [8]), the UE shall derive a mapped EPS security context for the PS domain from the UMTS security context for the CS domain. At change from A/Gb mode to S1 mode due to CS to PS SRVCC handover, ciphering may be started and integrity protection shall be started (see 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [22]) without any new authentication procedure. NOTE 1: CS to PS SRVCC handover from A/Gb mode to S1 mode or from Iu mode to S1 mode is not supported if the current CS security context is a GSM security context. NOTE 2: For emergency calls, CS to PS SRVCC handover from A/Gb mode to S1 mode or from Iu mode to S1 mode is not supported. In order to derive a mapped EPS security context for a CS to PS SRVCC handover from A/Gb mode or Iu mode to S1 mode, the MSC creates a NONCEMSC and generates the CK'PS and IK'PS using the CS UMTS integrity key, the CS UMTS ciphering key and the created NONCEMSC as specified in annex B.6 in 3GPP TS 33.102[ 3G security; Security architecture ] [18]. The MSC associates the CK'PS and IK'PS with a KSI'PS. The KSI'PS is set to the value of the KSICS associated with the CS UMTS integrity key and the CS UMTS ciphering key. The MSC transfers the CK'PS, IK'PS and the KSI'PS to the MME. The MME shall create a mapped EPS security context by setting the K'ASME to the concatenation of the CK'PS and IK'PS received from the MSC (i.e. CK'PS || IK'PS). The MME shall associate the K'ASME with a KSISGSN. The MME shall set KSISGSN to the value of the KSI'PS received from the MSC. The MME shall include the selected NAS algorithms, NONCEMME and generated KSISGSN (associated with the K'ASME) in the NAS security transparent container for the handover to E-UTRAN. The MME shall derive the EPS NAS keys from K'ASME. When the UE receives the command to perform CS to PS SRVCC handover to S1 mode, the ME shall generate the CK'PS and IK'PS using the CS UMTS integrity key, the CS UMTS ciphering key and the received NONCEMSC value in the transparent container in the CS to PS SRVCC handover command as specified in annex B.6 in 3GPP TS 33.102[ 3G security; Security architecture ] [18]. The ME shall ignore the NONCEMME value received in the NAS Security Transparent Container in the CS to PS SRVCC handover command. NOTE 3: The NONCEMME value received in the NAS Security Transparent Container for the handover to E-UTRAN is not used by the ME or MME in any key derivation in this handover. The ME shall create the key K'ASME by concatenating the derived CK'PS and IK'PS (i.e. CK'PS || IK'PS.). The ME shall associate the derived key K'ASME with a KSISGSN. The ME shall set the KSISGSN associated to K'ASME to the KSISGSN value received in the NAS Security Transparent Container from the network. NOTE 4: Although this case is related to the MSC server enhanced for SRVCC, the name KSISGSN is kept to avoid introducing a new name for the same domain. The ME shall derive the EPS NAS keys (CK' and IK') from the K'ASME as specified in 3GPP TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [19]. The ME shall apply these derived EPS NAS security keys (CK' and IK'), reset the uplink and downlink NAS COUNT values for the mapped EPS security context (i.e. to the value 0), and replace an already established mapped EPS security context for the PS domain, if any, in the ME, when the CS to PS SRVCC handover from A/Gb mode or Iu mode has been completed successfully. If the already established current EPS security context is of type native, then it shall become the non-current native EPS security context and overwrite any existing non-current native EPS security context in the ME. The network shall replace an already established mapped EPS security context for the PS domain, if any, when the CS to PS SRVCC handover from A/Gb mode or Iu mode has been completed successfully. If the already established current EPS security context is of type native, then it shall become the non-current native EPS security context and overwrite any existing non-current native EPS security context in the MME. If the CS to PS SRVCC handover from A/Gb mode or Iu mode has not been completed successfully, the UE and the network shall delete the new derived mapped EPS security context for the PS domain. Additionally, the network shall delete an already established mapped EPS security context for the PS domain, if any, if the eKSI of the already established EPS security context is equal to the KSISGSN of the new derived EPS security context for the PS domain. | 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.5 |
5,057 | 5.5.2.1A.2 Reference signal sequence using π/2-BPSK modulation scheme | For using π/2-BPSK modulation scheme, is used to determine which 2 of 3 subcarriers will be used: - 0 indicates that the two subcarriers having the lowest indices among the three allocated are utilized. - 1 indicates that the two subcarriers having the highest indices among the three allocated are utilized. The reference signal sequences and for using 2 out of 3 subcarriers are defined by where the binary sequence is defined by clause 7.2 and shall be initialised with at the start of the PUSCH transmission using sub-PRB allocations for BL/CE UEs. The quantity is given by Table 5.5.2.1A.2-1 where if group hopping is not enabled, and by clause 5.5.2.1A.3 if group hopping is enabled for PUSCH using sub-PRB allocations for BL/CE UEs. Table 5.5.2.1A.2-1: Definition of The reference signal sequences for PUSCH using sub-PRB allocations for BL/CE UEs is given by clause 5.3.3, where and correspond to the complex-valued symbols at the input of the transform precoding. The resulting complex-valued symbols at the output of the transform precoding correspond to the sequence which is mapped to physical resources as described in clause 5.5.2.1A.4. | 3GPP TS 36.211 | Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation | RAN1 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 5.5.2.1A.2 |
5,058 | 28.7.7.2 Decorated NAI used for N5CW devices via trusted non-3GPP access for SNPN | If the credentials holder is constructed based on SNPN, the Decorated NAI used for N5CW devices via trusted non-3GPP access for SNPN scenarios shall take the form: "nai.5gc-nn.nid<NID_Home>.mnc<homeMNC>.mcc<homeMCC>.3gppnetwork.org!<5G_device_unique_identity>@nai.5gc-nn.nid<NID_visited>.mnc<visitedMNC>.mcc<visitedMCC>.3gppnetwork.org"where the <5G_device_unique_identity> is to identify the N5CW device as defined in clause 28.7.7.0, the <NID_Home> or <NID_visited> shall be encoded as hexadecimal digits as specified in clause 12.7, and the <NID_Home>, <homeMNC>, and <homeMCC> are used to identify the SNPN based credentials holder. If the credentials holder is constructed based on PLMN, the Decorated NAI used for N5CW devices via trusted non-3GPP access for SNPN shall take the form: "nai.5gc-nn.mnc<homeMNC>.mcc<homeMCC>.3gppnetwork.org!<5G_device_unique_identity>@nai.5gc-nn.nid<NID_visited>.mnc<visitedMNC>.mcc<visitedMCC>.3gppnetwork.org" where the <5G_device_unique_identity> is to identify the N5CW device as defined in clause 28.7.7.0, the <NID_visited> shall be encoded as hexadecimal digits as specified in clause 12.7, and the <homeMNC> and <homeMCC> are used to identify the PLMN based credentials holder. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 28.7.7.2 |
5,059 | 6.6.1.2.2 ESM information request initiated by the network | The network initiates the ESM information request procedure by sending an ESM INFORMATION REQUEST message to the UE, starting timer T3489 and entering the state PROCEDURE TRANSACTION PENDING (see example in figure 6.6.1.2.2.1). This message shall be sent only after the security context has been setup, and if the ESM information transfer flag has been set in the PDN CONNECTIVITY REQUEST message. The MME shall set the EPS bearer identity of the ESM INFORMATION REQUEST message to the value "no EPS bearer identity assigned" and include the PTI from the associated PDN CONNECTIVITY REQUEST message. Figure 6.6.1.2.2.1: ESM information request procedure | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.6.1.2.2 |
5,060 | 6.2.18 Support of redundant PDU sessions | The 5GSM sublayer may support establishment of redundant PDU sessions (see subclause 5.33.2 of 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8]). In order to establish a set of two redundant PDU sessions, a UE can include a PDU session pair ID, an RSN, or both in a PDU SESSION ESTABLISHMENT REQUEST message for each of the two redundant PDU sessions (see subclause 6.4.1.2). The UE can set the PDU session pair ID, the RSN, or both according to URSP or UE local configuration (see 3GPP TS 24.526[ User Equipment (UE) policies for 5G System (5GS); Stage 3 ] [19]). An SMF receiving a PDU session pair ID, an RSN, or both via a PDU SESSION ESTABLISHMENT REQUEST message operates as specified in subclause 5.33.2 of 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8]. In addition, an SMF can handle two PDU sessions as redundant even if the UE provides neither a PDU session pair ID nor an RSN in a PDU SESSION ESTABLISHMENT REQUEST message for each of the PDU sessions (see subclause 5.33.2 of 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8]). | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.2.18 |
5,061 | 18.3 SDT without UE context relocation | The overall procedure for SDT procedure over RACH without UE context relocation is illustrated in the figure 18.3-1. Figure 18.3-1. RA-based SDT without UE context relocation 1/2. The steps 1/2 are as defined in steps 1/2 in Figure 18.2-1. 3. The last serving gNB decides not to relocate the full UE context for SDT. 4. The last serving gNB transfers a partial UE context including the SDT related RLC context. 5. The receiving gNB acknowledges receiving the partial UE context and provides associated DL TNL address. The UE context is kept at the last serving gNB and the SDT related RLC context is established at the receiving gNB. Then UL/DL GTP-U tunnels are established for DRBs configured for SDT, if any, and the UL SDT data and/or signalling, if any, are forwarded to the last serving gNB, and then delivered to the core network. NOTE 1: The DL signalling from the last serving gNB, if any, is forwarded to the receiving gNB via the RRC TRANSFER message, for which the receiving gNB delivers it to the UE. NOTE 1a: In case DL non-SDT data or DL non-SDT signalling arrives, or UE assistance information (i.e. UL non-SDT data arrival indication) is received from the UE, the last serving gNB terminates the SDT procedure and directs the UE to continue in RRC_INACTIVE state by sending the RRCRelease message. NOTE 1b: The last serving gNB may terminate the SDT procedure and direct the UE to continue in RRC_INACTIVE state by sending the RRCRelease message based on (e.g. large size of) DL SDT data or DL SDT signalling. 6. The receiving gNB detects the end of SDT session and sends the RETRIEVE UE CONTEXT CONFIRM message including whether this is a "normal" end of SDT transaction or a radio link problem, or large SDT volume from BSR. 7. Upon receiving the RETRIEVE UE CONTEXT CONFIRM message and deciding to terminate the SDT, the last serving gNB responds to the receiving gNB with the RETRIEVE UE CONTEXT FAILURE message including an encapsulated RRCRelease message. The receiving gNB shall release the established partial UE context. NOTE 2: Void. NOTE 3: Void. 8. The receiving gNB sends the RRCRelease message to the UE. NOTE 4: Void. NOTE 5: The last serving gNB may terminate the SDT procedure and direct the UE to continue in RRC_INACTIVE state by sending the RRCRelease message upon receiving the indication about large uplink SDT data from the BSR from the receiving gNB in step 6. 9. The UE moves to RRC_INACTIVE state if the suspend indication is included in the RRCRelease message. Or else, the UE moves to RRC_IDLE state. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 18.3 |
5,062 | 5.9.3.3 Protection of attributes | Integrity protection shall be applied to all attributes transferred over the N32-f interface. Confidentiality protection shall be applied to all attributes specified in SEPP's Data-type Encryption Policy (clause 13.2.3.2). The following attributes shall be confidentiality protected when being sent over the N32-f interface, irrespective of the Data-type Encryption Policy: - Authentication Vectors. - Cryptographic material. - Location data, e.g. Cell ID and Physical Cell ID. - Content of SMS in case of SMS over SBI over N32. - Authorization token. The following attributes should additionally be confidentiality protected when being sent over the N32-f interface: - SUPI. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 5.9.3.3 |
5,063 | 5.2.8.2.8 Nsmf_PDUSession_SMContextStatusNotify service operation | Service operation name: Nsmf_PDUSession_SMContextStatusNotify. Description: This service operation is used by the SMF to notify its consumers about the status of an SM context related to a PDU Session (e.g. PDU Session Release due to local reasons within the SMF, PDU Session handover to a different system or access type, SMF context transfer, triggering I-SMF selection for the PDU Session). The SMF may use this service operation to update the SMF derived CN assisted RAN parameters tuning in the AMF. The SMF may report the DDN Failure with NEF Correlation ID to the AMF. Input, Required: Status information. Input, Optional: Cause, SMF derived CN assisted RAN parameters tuning, New SMF ID for SM Context Transfer (see clause 4.26.5.3) or SMF set ID, Small Data Rate Control Status, APN Rate Control Status, DDN Failure detected in (I-/V-)SMF, target DNAI information, list of NWDAF IDs and corresponding Analytics ID(s). Output, Required: Result Indication. Output, Optional: None. The target DNAI information indicates the target DNAI for the current PDU session or target DNAI for next PDU session. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.8.2.8 |
5,064 | 3 Numbering plan for mobile stations 3.1 General | The structure of the following numbers is defined below: - the telephone number used by a subscriber of a fixed (or mobile) network to call a mobile station of a PLMN; - the network addresses used for packet data communication between a mobile station and a fixed (or mobile) station; - mobile station roaming numbers. One or more numbers of the E.164 numbering plan shall be assigned to a mobile station to be used for all calls to that station, i.e. the assignment of at least one MSISDN (i.e. E.164 number) to a mobile station is mandatory. As an exception, GPRS and EPS allow for operation whereby a MSISDN is not allocated as part of the subscription data (see 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [3] clause 5.3.17 and 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [72]). NOTE: For card operated stations the E.164 number should be assigned to the holder of the card (personal number). | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 3 |
5,065 | 4.24.2 UPF anchored Mobile Terminated Data Transport in Control Plane CIoT 5GS Optimisation | This clause describes the procedures for Mobile Terminated Data Transport in Control Plane CIoT 5GS Optimisation where the PDU Session is terminated at a UPF. Figure 4.24.2-1: Mobile Terminated Data Transport in Control Plane CIoT 5GS Optimisation 1. Downlink data is received by the UPF. If buffering is configured in the UPF, then the flow continues in step 2a, otherwise the flow continues in step 2f. 2a. [conditional] If this is the first downlink packet to be buffered and SMF has instructed the UPF to report the arrival of first downlink packet to be buffered, then the UPF sends a Data Notification to the SMF. 2b. [conditional] The SMF sends a Data Notification ACK to the UPF. 2c. [conditional] The SMF sends a Namf_MT_EnableUEReachability request to the AMF. The SMF determines whether Extended Buffering applies based on local policy and the capability of the UPF. If Extended Buffering applies, the SMF includes "Extended Buffering support" indication in Namf_MT_EnableUEReachability request. 2d. [conditional] If the UE is considered reachable, step 3 is executed immediately. If the AMF determines the UE is unreachable (e.g. if the UE is in MICO mode or the UE is configured for extended idle mode DRX), then the AMF rejects the request from the SMF with an indication that the UE is not reachable. If the SMF included Extended Buffering support indication, the AMF indicates the Estimated Maximum Wait time in the response message. Based on the rejection message from the AMF, the SMF should subscribe with the AMF for UE reachability using the Namf_EventExposure service. If the UE is in MICO mode, the AMF determines the Estimated Maximum Wait time based on the next expected periodic registration timer update expiration or by implementation. The procedure continues in step 8ab when the UE becomes reachable. If the UE is configured for extended idle mode DRX, the AMF determines the Estimated Maximum Wait time based on the start of next PagingTime Window. The procedure continues in step 3 when the UE becomes reachable. If the AMF detects that the UE context contains Paging Restriction Information, the AMF may block the paging for this UE based on the stored Paging Restriction Information (see clause 5.38.1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]). If the AMF blocks paging, the AMF sends MT_EnableUEReachability response to the SMF with an indication that its request has been rejected due to restricted paging. 2e. [conditional] If the SMF receives an "Estimated Maximum Wait time" from the AMF and Extended buffering applies, the SMF sends a failure indication to the UPF with an Extended Buffering time and optionally a DL Buffering Suggested Packet Count. The Extended Buffering time is determined by the SMF and should be larger or equal to the Estimated Maximum Wait time received from the AMF. The DL Buffering Suggested Packet Count parameter is determined by the SMF and if available, the Suggested Number of Downlink Packets parameter may be considered. The procedure stops after this step. 2f. [conditional] If buffering is not configured in the UPF, then the UPF forwards the downlink data to the (V-)SMF in non-roaming and LBO cases. In the home-routed roaming case, the H-UPF forwards the data to the V-UPF and then to the V-SMF. 2g. [conditional] The SMF determines whether Extended Buffering applies based on local policy and the capability of the SMF. If user data is received in step 2f and Extended buffering is not configured for the SMF, then (V-)SMF compresses the header if header compression applies to the PDU session and creates the downlink user data PDU that is intended as payload in a NAS message. The (V-)SMF forwards the downlink user data PDU and the PDU session ID to the AMF using the Namf_Communication_N1N2MessageTransfer service operation. If Extended Buffering applies, then (V-)SMF keeps a copy of the downlink data. If user data is received in step 2f and Extended Buffering applies, the SMF includes "Extended Buffering support" indication in Namf_Communication_N1N2Message Transfer. 2h. [conditional] AMF responds to SMF. If AMF determines that the UE is reachable for the SMF, then the AMF informs the SMF. Based on this, the SMF deletes the copy of the downlink data. If the AMF determines the UE is unreachable for the SMF (e.g. if the UE is in MICO mode or the UE is configured for extended idle mode DRX), then the AMF rejects the request from the SMF. If the SMF included Extended Buffering support indication, the AMF indicates the Estimated Maximum Wait time, in the reject message, for the SMF to determine the Extended Buffering time. Based on the rejection message from the AMF, the SMF should subscribe with the AMF for UE reachability using the Namf_EventExposure service. If the UE is in MICO mode, the AMF determines the Estimated Maximum Wait time based on the next expected periodic registration timer update expiration or by implementation. The procedure continues in step 8ab when the UE becomes reachable. If the UE is configured for extended idle mode DRX, the AMF determines the Estimated Maximum Wait time based on the start of next PagingTime Window. The procedure continues in step 3 when the UE becomes reachable. If the AMF detects that the UE context contains Paging Restriction Information, the AMF may block the paging for this UE, based on the stored Paging Restriction Information (see clause 5.38.1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]). If the AMF blocks paging, the AMF sends Namf_Communication_N1N2MessageTransfer response to the SMF with an indication that its request has been rejected due to restricted paging. If the SMF receives an "Estimated Maximum Wait time" from the AMF and Extended Buffering in SMF applies, the SMF store the DL Data for the Extended Buffering time. The Extended Buffering time is determined by the SMF and should be larger or equal to the Estimated Maximum Wait time received from the AMF. The SMF does not send any additional Namf_Communication_N1N2MessageTransfer message if subsequent downlink data packets are received. 3. [Conditional] If the UE is in CM-IDLE, when the AMF determines that the UE is reachable, the AMF sends a paging message to NG-RAN. If available, the AMF may include the WUS Assistance Information in the N2 Paging message(s). 4. [Conditional] If NG-RAN received a paging message from AMF and UE and NG-RAN support WUS, then: - if the NGAP Paging message contains the Assistance Data for Recommended Cells IE (see TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [10]), then NG-RAN shall only broadcast the UE's Wake Up Signal in the last used cell; - else (i.e. the Assistance Data for Recommended Cells IE is not included in the NGAP Paging message) NG-RAN should not broadcast the UE's Wake Up Signal. NG-RAN performs paging. If the WUS Assistance Information is included in the N2 Paging message, the NG-eNB takes it into account when paging the UE (see TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [46]). 5. [Conditional] If the UE receives paging message, it responds with a NAS message sent over RRC Connection Establishment. If the UE is in CM-IDLE state in 3GPP access and is using the Multi-USIM Paging Rejection feature (see clause 5.38 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]), upon reception of paging request and if the UE determines not to accept the paging, the UE attempts to send a Reject Paging Indication via the UE Triggered Service Request procedure (clause 4.2.3.2) unless it is unable to do so, e.g. due to UE implementation constraints. 5a. [Conditional] In the NB-IoT case, during Step 5, the NG-RAN, based on configuration, may retrieve the NB-IoT UE Priority and the Expected UE Behaviour Parameters from the AMF, if not previously retrieved. Based on such parameters, the NG-RAN may apply prioritisation between requests from different UEs before triggering step 6 and throughout the RRC connection. The NG-RAN may retrieve additional parameters (e.g. UE Radio Capabilities). 6. [Conditional] The NAS message is forwarded to the AMF. If the AMF receives any Paging Restrictions information in the Control Plane Service Request, the AMF updates the UE context with the received Paging Restrictions information. If no Paging Restriction information is provided, no paging restrictions apply. 7a. [Conditional] AMF to SMF: Namf_MT-EnableUEReachability Response. If the SMF used the MT_EnableUEReachability request in step 2c and the UE has not responded to paging then the AMF sends a response to the SMF indicating that the request failed. If the SMF used the MT_EnableUEReachability service operation in step 2c and the UE has responded with a Control Plane Service Request NAS message including Reject Paging Indication in step 5, the AMF notifies the SMF using the MT_EnableUEReachability response that the UE rejected the page and no user plane connection will be established. The UE remains reachable for future paging attempts. 7b. [Conditional] SMF to UPF: If the SMF has received a Namf_MT-EnableUEReachability response from the AMF indicating that the request failed or the UE rejected the paging, the SMF indicates to the UPF to discard the buffered data. . If the AMF indicated that the UE rejected the paging, steps 7c-12 are skipped. Otherwise the procedure stops after this step. 7c. [Conditional] AMF to SMF: Namf_Communication_N1N2Transfer Failure Notification. If the SMF used the Namf_Communication_N1N2MessageTransfer service operation in step 2g and the UE has not responded to paging, the AMF sends a failure notification to the SMF based on which the SMF discards the buffered data. The procedure stops after this step. If the SMF used the Namf_Communication_N1N2MessageTransfer service operation in step 2g and the UE has responded with a Control Plane Service Request NAS message including Reject Paging Indication in step 5, the AMF notifies the SMF using the Namf_Communication_N1N2MessageTransfer Failure Notification that the UE rejected the page and no user plane connection will be established. The UE remains reachable for future paging attempts. Steps 9-12 are skipped. 8aa. [Conditional] AMF to SMF: Namf_MT-EnableUEReachability Response. If the SMF used the MT_EnableUEReachability request in step 2c and steps 2d-2e were skipped, then the AMF indicates to the SMF that the UE is reachable. 8ab. [Conditional] AMF to SMF: If in step 2d or 2h the SMF has subscribed with the AMF for UE reachability event, the AMF uses the Namf_EventExposure Notify service operation indicating to the SMF that the UE is reachable. 8b. [Conditional] SMF to UPF: N4 Session Modification Request. If the SMF received an indication from the AMF that the UE is reachable, then the SMF indicates to the UPF to deliver buffered data to the SMF. 8c. [Conditional] UPF to SMF: N4 Session Modification Response. 8d. [Conditional] Buffered data is delivered to the SMF. 8e. [Conditional] (V-)SMF compresses the header if header compression applies to the PDU session and creates the downlink user data PDU that is intended as payload in a NAS message. The (V-)SMF forwards the downlink user data PDU and the PDU session ID to the AMF using the Namf_Communication_N1N2MessageTransfer service operation. When buffering is not configured in the UPF, this step is executed only if in step 2h the SMF has subscribed with the AMF for UE reachability event. 9. The AMF creates a DL NAS transport message with the PDU session ID and the downlink user data PDU received from the SMF. The AMF ciphers and integrity protects the NAS transport message. 10. The AMF sends the DL NAS transport message to NG-RAN. 11. NG-RAN delivers the NAS payload over RRC to the UE. 12. While the RRC connection is established further uplink and downlink data can be exchanged. In order to send uplink data, the procedure continues as per steps 1-10 of the UPF anchored Mobile Originated Data Transport in Control Plane CIoT 5GS Optimisation procedure (clause 4.24.1). 13. If the AMF has paged the UE to trigger the NAS procedure as in step 3-6, the AMF shall initiate the UE configuration update procedure as defined in clause 4.2.4.2 to assign a new 5G-GUTI. If the UE response in the Control Plane Service Request NAS message includes a Reject Paging Indication, the AMF triggers the release of the UE as specified in clause 4.2.3.2. 14. [Conditional] If no further activity is detected by NG-RAN, then NG-RAN triggers the AN release procedure. 15. [Conditional] The UE's logical NG-AP signalling connection and RRC signalling connection are released according to clause 4.2.6. NOTE: The details of the NGAP messages to be used for this procedure are specified in TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [10]. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.24.2 |
5,066 | 8.1.2.12 Applicability of performance requirements for 8Rx capable UEs | For 8Rx capable UEs, the 2Rx supported RF bands, 4Rx supported RF bands and 8Rx supported RF bands are up to UE’s declaration. For any demodulation tests and CSI tests conducted in the 8Rx supported RF band, four receive antenna ports that UE may use for control channel demodulation are clarified via UE declaration. When testing an N-Rx (N = 2,4) demodulation or CSI test on the 8Rx supported band, the fading duplication and antenna mapping should guarantee that the four receive antennas UE declares for the control channel demodulation collectively receives at least 4/N duplicated version of the fading channel seen at each receive antenna of the N-Rx test, i.e., the connection diagrams in Figure 8.1.2.12.1-1 to Figure 8.1.2.12.1-4 are valid under the condition that Rx1, Rx3, Rx5 and Rx7 are the four receive antennas declared by UE for the control channel demodulation. | 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.12 |
5,067 | 5.4 Physical uplink control channel | The physical uplink control channel, PUCCH, carries uplink control information. Simultaneous transmission of PUCCH and PUSCH from the same UE is supported if enabled by higher layers. For frame structure type 2, the PUCCH is not transmitted in the UpPTS field. The physical uplink control channel supports multiple formats as shown in Table 5.4-1 with different number of bits per subframe, where represents the bandwidth of the PUCCH format 4 as defined by clause 5.4.2B, and and are defined in Table 5.4.2C-1. Formats 2a and 2b are supported for normal cyclic prefix only. Table 5.4-1: Supported PUCCH formats All PUCCH formats use a cyclic shift, , which varies with the symbol number and the slot number according to where the pseudo-random sequence is defined by clause 7.2. The pseudo-random sequence generator shall be initialized with , where is given by clause 5.5.1.5 with corresponding to the primary cell, at the beginning of each radio frame. The physical resources used for PUCCH format 1/1a/1b and PUCCH format 2/2a/2b depends on two parameters, and , given by higher layers. The variable denotes the bandwidth in terms of resource blocks that are available for use by PUCCH formats 2/2a/2b transmission in each slot. The variable denotes the number of cyclic shift used for PUCCH formats 1/1a/1b in a resource block used for a mix of formats 1/1a/1b and 2/2a/2b. The value of is an integer multiple of within the range of {0, 1, …, 7}, where is provided by higher layers. No mixed resource block is present if . At most one resource block in each slot supports a mix of formats 1/1a/1b and 2/2a/2b. Resources used for transmission of PUCCH formats 1/1a/1b, 2/2a/2b, 3, 4, and 5 are represented by the non-negative indices , , , and , respectively. | 3GPP TS 36.211 | Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation | RAN1 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 5.4 |
5,068 | 5.4.9 Wake Up Signal Assistance 5.4.9.1 General | The RAN and UE may use a Wake Up Signal (WUS) to reduce the UE's idle mode power consumption. The RAN sends the WUS shortly before the UE's paging occasion. The WUS feature enables UEs to determine that in the paging occasions immediately following their WUS occasion they will not be paged if their WUS is not transmitted, or that they might be paged if their WUS is transmitted (see TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [52]). To avoid waking up UEs due to an AMF paging other UEs across multiple cells (e.g. due to frequent UE mobility and/or for low paging latency services such as VoLTE), the use of WUS by the ng-eNB and the UE is restricted to the last used cell, i.e. the cell in which the UE's RRC connection was last released. To support this: a) ng-eNBs should provide the Recommended Cells for Paging IE in the Information on Recommended Cells and RAN Nodes for Paging IE (see TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [34]) to the AMF in the NGAP UE Context Release Complete, UE Context Suspend Request and UE Context Resume Request messages; b) if received during the last NGAP UE Context Release Complete or UE Context Suspend Request message, the AMF provides (without modification) the Recommended Cells for Paging as Assistance Data for Recommended Cells IE in the Assistance Data for Paging IE within the NGAP Paging message to the RAN (see also TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [34]); and c) the AMF shall delete (or mark as invalid) the Information On Recommended Cells And RAND nodes For Paging when a new NGAP association is established for the UE. In the NGAP Paging message, the last used cell ID is sent in the Assistance Data for Recommended Cells IE in the Assistance Data for Paging IE (see TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [34]). When receiving an NGAP Paging message for a WUS-capable UE that also includes the Assistance Data for Recommended Cells IE then a WUS-capable ng-eNB shall only broadcast the WUS on the cell that matches the last used cell ID. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.4.9 |
5,069 | 6.9.2.4 Relay UE Selection | The 3GPP system shall support selection and reselection of relay UEs based on a combination of different criteria e.g. - the characteristics of the traffic that is intended to be relayed (e.g. expected message frequency and required QoS), - the subscriptions of relay UEs and remote UE, - the capabilities/capacity/coverage when using the relay UE, - the QoS that is achievable by selecting the relay UE, - the power consumption required by relay UE and remote UE, - the pre-paired relay UE, - the 3GPP or non-3GPP access the relay UE uses to connect to the network, - the 3GPP network the relay UE connects to (either directly or indirectly), - the overall optimization of the power consumption/performance of the 3GPP system, or - battery capabilities and battery lifetime of the relay UE and the remote UE. NOTE: Reselection may be triggered by any dynamic change in the selection criteria, e.g. by the battery of a relay UE getting depleted, a new relay capable UE getting in range, a remote UEs requesting additional resources or higher QoS, etc. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.9.2.4 |
5,070 | 7.7.2.3 Support of resource efficiency for RAN Sharing with multiple cell-ID broadcast | gNB-DUs sharing the same physical cell resources receive via F1-C information enabling identifying broadcast MBS sessions providing identical content. The identification is based on Associated Session ID, for location dependent MBS services, the MBS Service Area is also taken into account. Applying resource efficiency for RAN Sharing with multiple cell-ID broadcast - resolve different QoS requirements received from the participating 5GCs in an implementation specific way. - F1-U resources are established towards either all involved gNB-CUs or only some of them which is decided by the entity controlling the involved gNB-DUs sharing the same physical cell resources. The gNB-DU is able to trigger the gNB-CU to establish F1-U resources. - the gNB-CU-CP takes into account the decision F1-U resources have been established or not to decide whether to establish NG-U resources. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 7.7.2.3 |
5,071 | 5.11.3a UE Radio Capability Signalling optimization | With the increase of the size of UE radio capabilities driven e.g. by additional frequency bands and combinations thereof for E-UTRA and NR, an efficient approach to signal UE Radio Access Capability information over the radio interface and other network interfaces is defined with RACS. In this Release of the specification, RACS does not apply to NB-IOT (terrestrial or satellite). RACS works by assigning an identifier to represent a set of UE radio capabilities. This identifier is called UE Radio Capability ID. A UE Radio Capability ID can be either UE manufacturer-assigned or PLMN-assigned, as specified in clause 5.2.7. The UE Radio Capability ID is an alternative to the signalling of the UE Radio Capability information over the radio interface, within E-UTRAN, from E-UTRAN to NG-RAN, from MME to E-UTRAN and between CN nodes supporting RACS. The UCMF (UE radio Capability Management Function) stores all UE Radio Capability ID mappings in a PLMN and is responsible for assigning every PLMN-assigned UE Radio Capability ID in this PLMN, see clause 4.4.13. The UCMF shall be configured with a Version ID for PLMN assigned UE Radio Capability IDs, defined in clause 4.4.13. The UCMF stores the UE Radio Capability IDs alongside the UE Radio Capability information and the UE Radio Capability for Paging they map to. Each UE Radio Capability ID stored in the UCMF can be associated to one or both UE radio capabilities formats specified in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [89] and TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [37]. The two UE radio capabilities formats shall be identifiable by the MME and UCMF and the MME shall store the TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [37] format only. An E-UTRAN which supports RACS can be configured to operate with one of two modes of operation when providing the UE radio capabilities to the MME when the E-UTRAN executes a UE Radio Capability Enquiry procedure (see TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [37]) to retrieve UE radio capabilities from the UE. - Mode of operation A): The E-UTRAN provides to the MME both UE Radio Capability formats (i.e. the TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [37] format and TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [89] format). The E-UTRAN derives one of the formats using local transcoding of the other format it receives from the UE and extracts the E-UTRAN UE Radio Capability for Paging and NR UE Radio Capability for Paging from the UE Radio capabilities. - Mode of operation B): The E-UTRAN provides to the MME the TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [37] format only. In a PLMN supporting RACS only in EPS, Mode of Operation B shall be configured. If the PLMN supports RACS in both EPS and 5GS: - If RAN nodes in the EPS and 5GS are configured in Mode of operation B, then the UCMF shall be capable to transcode between TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [89] and TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [37] formats. The UCMF shall be able to generate the RAT-specific UE Radio Capability for Paging information from the UE Radio capabilities. - If E-UTRAN is configured to operate according to Mode A, then also the NG-RAN shall be configured to operate according to mode A and the UMCF is not required to transcode between TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [89] and TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [37] formats. The MME shall provide the UCMF with the UE Radio Capability for Paging information. When the E-UTRAN updates the MME with new UE radio capabilities information, the MME provides the information obtained from the E-UTRAN to the UCMF even if the MME already stores a UE Radio Capability ID for the UE. The UCMF then returns a value of UE Radio Capability ID. If the value is different from the one stored in the MME, the MME updates the UE Radio Capability ID it stores and provides this new value to the E-UTRAN (if applicable) and to the UE. PLMN-assigned UE Radio Capability ID is assigned to the UE using the GUTI Reallocation procedure, Attach Accept or TAU Accept as defined in present specification. In order to be able to interpret the UE Radio Capability ID a network entity or node may store a local copy of the mapping between the UE Radio Capability ID and its corresponding UE Radio Capability information i.e. a dictionary entry. When no mapping is available between a UE Radio Capability ID and the corresponding UE Radio Capability information in a network entity or node, this network entity or node shall be able to retrieve it and store it. - An MME which supports RACS shall store such UE Radio Capability ID mapping at least for all the UEs that it serves that have a UE Radio Capability ID assigned. - The E-UTRAN performs local caching of the UE Radio Capability information for the UE Radio Capability IDs for the UEs it is serving, and potentially for other UE Radio Capability IDs according to suitable local policies. - When the E-UTRAN needs to retrieve the mapping of a UE Radio Capability ID to the corresponding UE Radio Capability information, it queries the MME using S1 signalling defined in TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [36]. - When the MME needs to get the UE Radio Capability Information and the UE Radio Capability for Paging associated to a UE Radio Capability ID it provides the UE Radio capability ID to the UCMF with an indication that it is requesting the TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [37] format, and the UCMF returns a mapping of the UE Radio Capability ID to the corresponding UE Radio Capability information in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [37] format to the MME along with the E-UTRAN UE Radio Capability for Paging. - When the MME needs to obtain a PLMN assigned UE Radio Capability ID for a UE from the UCMF, it provides the UE Capability information it has for the current radio configuration of the UE and the IMEI/TAC for the UE. The MME shall provide to the UCMF the UE Radio Capability information (and at least in Mode A, the UE Radio Capability for Paging) obtained from the E-UTRAN in one or both the TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [89] and TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [37] formats depending on how the RAN is configured. The UCMF stores the association of IMEI/TAC with this UE Radio Capability ID and the UE Radio Capability information and the UE Radio Capability for Paging in all the formats it receives. The UE Radio Capability information formats the MME provides shall be identifiable at the UCMF. - UEs, MMEs and RAN nodes which support RACS learn the current value of the Version ID when a new PLMN assigned UE Radio Capability ID is received from the UCMF and the Version ID it contains is different from the ones in their PLMN assigned UE Radio Capability ID cache. For a PLMN, PLMN assigned UE Radio Capability IDs related to old values (i.e. not current value) of the Version ID can be removed from cache but, if so, prior to removing any cached PLMN-assigned UE radio Capability IDs with the current value of the Version ID. The MME, RAN and UE may still continue to use the stored PLMN assigned UE Radio Capability IDs with old values of the Version ID, until these are purged from cache. If an out of date PLMN assigned UE Radio Capability ID is removed from an MME cache, the MME shall proceed to assign a new PLMN assigned UE Radio Capability ID to all the UEs for which the UE context includes the removed PLMN-assigned UE Radio Capability ID, using the GUTI Reallocation procedure, or when these UEs perform a Tracking Area Update. If the MME attempts to resolve a PLMN assigned UE Radio capability ID with an old Version ID, the UCMF shall return an error code indicating that this Version ID is no longer current. - If at any time the MME has neither a valid UE Radio Capability ID nor any stored UE radio capabilities for the UE, the MME may trigger the RAN to provide the UE Radio Capability information and subsequently request the UCMF to allocate a UE Radio Capability ID. - The RAN, in order to support MOCN network sharing scenarios, shall be capable to cache PLMN assigned UE Radio Capability IDs per PLMN ID. A network may utilise the PLMN-assigned UE Radio Capability ID, without involving the UE, e.g. for use with legacy UEs. Mutual detection of the support of the RACS feature happens between directly connected E-UTRAN nodes and between E-UTRAN and MME using protocol means as defined in TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [36] and TS 36.423[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 Application Protocol (X2AP) ] [76]. To allow for a mix of RACS-supporting and non-RACS-supporting RAN nodes over the X2 interfaces, the UE Radio Capability ID should be included in the Path Switch signalling during X2 based handover and Handover Request during S1 based handover between MME and E-UTRAN. In addition, RACS-supporting RAN nodes can be discovered across inter-CN node boundaries during S1 handover using the "RACS Indication" in "Target eNB to Source eNB Transparent Container" within the HANDOVER REQUEST ACKNOWLEDGE message to indicate that that target eNodeB is able to acquire the UE radio capabilities through reception of the UE Radio Capability ID in future mobility actions, as defined in TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [36]. The support of RACS by peer MMEs or AMFs is based on configuration in a PLMN or across PLMNs. A UE that supports WB-EUTRA and/or NR indicates its support for RACS to MME using UE Core Network Capability as defined in clause 5.11.3. A UE that supports RACS and is already assigned with an applicable UE Radio Capability ID in the PLMN, shall signal the UE Radio Capability ID in Attach procedure, as defined in clause 5.3.2, and Tracking Area Update procedure, as defined in clause 5.3.3 and based on triggers defined in TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [46]. If both PLMN-assigned and UE manufacturer-assigned UE Radio Capability IDs are available in the UE and applicable in the PLMN, the UE shall signal the PLMN-assigned UE Radio Capability ID. The UE shall delete the PLMN-assigned UE Radio Capability ID(s) for the related PLMN upon receiving an indication from this PLMN. When a PLMN decides to request a particular type of UE to use UE manufacturer-assigned UE Radio Capability ID(s): - The UCMF sends either a Nucmf_UECapabilityManagement_Notify or URCMP Event Notification Request message defined in TS 29.674[ Interface between the UE radio Capability Management Function (UCMF) and the Mobility Management Entity (MME); Stage 3 ] [91] to the MME including either a list of UE Radio Capability IDs (if the UE was previously using any PLMN assigned IDs) or the IMEI/TAC values corresponding to UE types that are requested to use UE manufacturer-assigned UE Radio Capability ID. These values are stored in a "UE Manufacturer Assigned operation requested list" in the MME. - The MME uses the GUTI reallocation command message, Attach Accept message or Tracking Area Update Accept message to request the UE to delete all the PLMN-assigned UE Radio Capability ID(s) for this PLMN if the UE is, respectively, registering or is registered with PLMN assigned UE Radio Capability ID or IMEI/TAC values matching one value in the UE manufacturer-assigned operation requested list. NOTE 1: It is expected that in a given PLMN the UCMF and MMEs will be configured to either use a UE manufacturer-assigned operation requested list based on a list of PLMN assigned UE Radio Capability IDs or a list of TACs, but not both. NOTE 2: The strategy for triggering of the deletion of PLMN-assigned UE Radio Capability ID(s) in the UE by the MME is implementation-specific (e.g. can be used only towards UEs in ECM-Connected state). - a UE that receives indication to delete the all the PLMN-assigned UE Radio Capability IDs in the Attach Accept message, Tracking Area Update Accept message or GUTI reallocation command message, deletes any PLMN-assigned UE Radio Capability IDs for this PLMN. The UE proceeds to register with a UE manufacturer-assigned UE Radio Capability ID that is applicable to the current UE Radio configuration. - When the "UE Manufacturer Assigned operation requested list" contains PLMN assigned UE Radio Capability IDs, the UCMF shall avoid re-assigning PLMN assigned UE Radio Capability IDs that were added to the "UE Manufacturer Assigned operation requested list" in the MMEs to any UE. - The MME stores a PLMN assigned ID in the UE manufacturer-assigned operation requested list for a time duration that is implementation specific, but TACs are stored until the UCMF require to remove certain TACs from the list (i.e. the list of TACs which are requested to use UE manufacturer-assigned UE Radio Capability IDs in the MME and UCMF is synchronised at all times). - The UCMF can request at any time the MME to remove PLMN assigned ID(s) or TAC(s) values form the UE manufacturer-assigned operation requested list. NOTE 3: The MME can decide to remove a UE Radio Capability ID related to selected PLMN from the "UE Manufacturer Assigned operation requested list" list e.g. because no UE with that UE Radio Capability ID has connected to the network for long time. If later a UE with such UE Radio Capability ID connects to the network, the MME contacts the UCMF to resolve the UE Radio Capability ID, and at this point the UCMF can trigger again the deletion of the UE Radio Capability ID by including this in the UE manufacturer-assigned operation requested list of the MME. The serving MME stores the UE Radio Capability ID for a UE in the UE context and provides this UE Radio Capability ID to E-UTRAN as part of the UE context information using S1 signalling. During inter PLMN mobility, the new MME shall delete the UE Radio Capability ID received from the old MME, unless the operator policy indicates that all UE Radio Capability IDs used in the old PLMN are also valid in the new PLMN. NOTE 4: If MME decides to allocate TAIs of multiple PLMN IDs as part of Tracking Area to the UE then MME provides the UE Radio Capability ID of the new selected PLMN to the eNodeB during UE mobility, whether the UE Radio Capability ID is taken from stored UE context previously assigned by the same new selected PLMN or generated freshly each time a new PLMN is selected is up to MME implementation. The UE stores the PLMN-assigned UE Radio Capability ID in non-volatile memory when in EMM-DEREGISTERED state and can use it again when it registers in the same PLMN. NOTE 5: It is assumed that UE does not need to store the access stratum information (i.e. UE-EUTRA-Capability and UE-NR-Capability specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [37] and TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [89], respectively) that was indicated by the UE to the network when the PLMN-assigned UE Radio Capability ID was assigned by the network. However, it is assumed that the UE does store the related UE configuration (e.g. whether or not GERAN or UTRAN or MBMS is enabled/disabled). At any given time at most one UE Radio Capability ID is stored in the UE context in CN and RAN. The number of PLMN-specific UE Radio Capability IDs that the UE stores in non-volatile memory is left up to UE implementation. However, to minimise the load (e.g. from radio signalling) on the Uu interface and to provide smoother inter-PLMN mobility (e.g. at land borders) the UE shall be able to store at least the latest 16 PLMN-assigned UE Radio Capability IDs (along with the PLMN that assigned them). This number is independent of the UE manufacturer-assigned UE Radio Capability ID(s) the UE may store. It shall be possible for a UE to change, e.g. upon change in its usage settings, the set of UE radio capabilities in time and signal the associated UE Radio Capability ID, if available. The UE stores the mapping between the UE Radio Capability ID and the corresponding UE Radio Capability information for every UE Radio Capability ID it stores. If the UE's Radio Capability information changes and there is no associated UE Radio Capability ID for the updated UE Radio Capability information, the UE shall perform the Tracking Area Update procedure for "UE radio capability update" as defined in clause 5.11.2. The UE shall perform a Tracking Area Update procedure at every change between a cell that does not broadcast SystemInformationBlockType31(-NB) and an E-UTRA cell that broadcasts SystemInformationBlockType31(-NB). This Tracking Area Update shall either include the UE Radio Capability ID applicable to the new area, or, shall indicate that the Tracking Area Update is for a "UE radio capability update". The E-UTRAN may apply RRC filtering of UE radio capabilities when it retrieves the UE Radio Capability information from the UE as defined in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [37]. NOTE 6: In a RACS supporting PLMN, the filter of UE radio capabilities configured in E-UTRAN is preferably as wide in scope as possible (e.g PLMN-wide). In this case, it corresponds e.g. to the super-set of bands, band-combinations and RATs the PLMN deploys and not only to the specific E-UTRAN node or region. NOTE 7: If the filter, included in the UE Radio Capability information, of UE radio capabilities configured in two E-UTRAN nodes is different, during handover between these two nodes, it is possible that the target E-UTRAN node might need to enquire the UE for its UE Radio Capability information again and trigger re-allocation of a PLMN-assigned UE Radio Capability ID leading to extra signalling. Additionally, a narrow filter might reduce the list of candidate target nodes. If a UE supports both NB-IoT and possibly other RATs the UE handles the RACS procedures as follows: - Since there is no support for RACS in NB-IoT, if the UE supports RACS in non-NB-IoT RATs (i.e. for WB-EUTRA and/or NR): - NB-IoT specific UE Radio Capability information is handled in UE, RAN and MME according to clause 5.11.2. - when the UE is not camping on NB-IoT, the UE provides UE radio capabilities for other RATs but not NB-IoT UE radio capabilities, according to TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [37]. As a result the UE Radio Capability ID that is assigned by the network corresponds only to the UE radio capabilities of the non-NB-IoT RATs. The UE uses the UE Radio Capability IDs assigned only in Attach and TAU procedures performed over non-NB-IoT RATs. Support for RACS in 5GS is defined in TS 23.501[ System architecture for the 5G System (5GS) ] [83] and TS 23.502[ Procedures for the 5G System (5GS) ] [84]. | 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.11.3a |
5,072 | 8.5.2.2.4 Minimum Requirement 2 Tx Antenna Port (demodulation subframe overlaps with aggressor cell ABS and CRS assistance information are configured) | For the parameters specified in Table 8.5.2-1 and Table 8.5.2.2.4-1, the average probability of a miss-detecting ACK for NACK (Pm-an) shall be below the specified value in Table 8.5.2.2.4-2. In Table 8.5.2.2.4-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] including Cell 2 and Cell 3 is provided. Table 8.5.2.2.4-1: Test Parameters for PHICH Table 8.5.2.2.4-2: Minimum performance PHICH | 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.5.2.2.4 |
5,073 | 4.7.2.1.1 READY timer behaviour (A/Gb mode only) | The READY timer, T3314 is used in the MS and in the network per each assigned P-TMSI to control the cell updating procedure. When the READY timer is running or has been deactivated the MS shall perform cell update each time a new cell is selected (see 3GPP TS 43.022[ None ] [82]). If a routing area border is crossed, a routing area updating procedure shall be performed instead of a cell update. When the READY timer has expired: - the MS shall perform the routing area updating procedure when a routing area border is crossed; - the MS shall not perform a cell update when a new cell is selected. - the network shall page the MS if down-link user data or signalling information needs to be sent to the MS. All other GMM procedures are not affected by the READY timer. The READY timer is started: - in the MS when the GMM entity receives an indication from lower layers that an LLC frame other than LLC NULL frame has been transmitted on the radio interface; and - in the network when the GMM entity receives an indication from lower layers that an LLC frame other than LLC NULL frame has been successfully received by the network. Within GMM signalling procedures the network includes a "force to standby" information element, in order to indicate whether or not the READY timer shall be stopped when returning to the GMM-REGISTERED state. If the "force to standby" information element is received within more than one message during a ongoing GMM specific procedure, the last one received shall apply. If the READY timer is deactivated and the network indicates "force to standby" with the "force to standby" information element, this shall not cause a modification of the READY timer. The READY timer is not affected by state transitions to and from the GMM-REGISTERED.SUSPENDED sub-state. The value of the READY timer may be negotiated between the MS and the network using the GPRS attach or GPRS routing area updating procedure. - If the MS wishes to indicate its preference for a READY timer value it shall include the preferred values into the ATTACH REQUEST and/or ROUTING AREA UPDATE REQUEST messages. The preferred values may be smaller, equal to or greater than the default values or may be equal to the value requesting the READY Timer function to be deactivated. - Regardless of whether or not a timer value has been received by the network in the ATTACH REQUEST or ROUTING AREA UPDATE REQUEST messages, the network may include a timer value for the READY timer (different or not from the default value) into the ATTACH ACCEPT or ROUTING AREA UPDATE ACCEPT messages, respectively. If the READY Timer value was included, it shall be applied for the GMM context by the network and by the MS. - When the MS proposes a READY Timer value and the Network does not include any READY Timer Value in its answer, then the value proposed by the MS shall be applied for the GMM context by the Network and by the MS. - When neither the MS nor the Network proposes a READY Timer value into the ATTACH REQUEST/ATTACH ACCEPT or ROUTING AREA UPDATE REQUEST/ROUTING AREA UPDATE ACCEPT message, then the default value shall be used. If the negotiated READY timer value indicates that the ready timer function is deactivated, the READY timer shall always run without expiry. If the negotiated READY timer value indicates that the ready timer function is deactivated, and within the same procedure the network indicates "force to standby" with the "force to standby" information element, the READY timer shall always run without expiry. If the negotiated READY timer value is set to zero, the READY timer shall be stopped immediately. To account for the LLC frame uplink transmission delay, the READY timer value should be slightly shorter in the network than in the MS. This is a network implementation issue. If a new READY timer value is negotiated, the MS shall upon the reception of the ATTACH ACCEPT or ROUTING AREA UPDATE ACCEPT message perform an initial cell update (either by transmitting a LLC frame or, if required, a ATTACH COMPLETE or ROUTING AREA UPDATE COMPLETE message), in order to apply the new READY timer value immediately. If both the network and the MS support the Cell Notification, the initial cell update shall use any LLC frame except the LLC NULL frame. If the new READY timer value is set to zero or if the network indicates "force to standby" with the "force to standby" IE, the initial cell update should not be done. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.7.2.1.1 |
5,074 | 4.3.2.3 CDR generation for online charged subscribers | In offline charging, CDRs are generated in the network and forwarded to the BD for further processing, e.g. generating subscriber bills. In online charging, network resource usage is granted by the OCS based on a subscriber account on the OCS. If required by the operator, CDRs may additionally be generated for online charged subscribers. One way of achieving this is by performing online charging and offline charging simultaneously for these subscribers. Alternatively, the OCS can accomplish this by the use of the appropriate offline charging functions as follows: - A CDF, as specified in clause 4.3.1.2, is employed by each of the OCFs that are required to generate CDRs from the charging events they receive from the CTF; - A CGF, as specified in clause 4.3.1.3, is employed by the OCS in order to generate / manage CDR files and provide these files to the BD. | 3GPP TS 32.240 | Telecommunication management; Charging management; Charging architecture and principles | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.3.2.3 |
5,075 | 5.3.4.3 Inter-network correlation | To enable the different operators involved in IMS sessions to identify each other, the Inter Operator Identification concept (IOI) is introduced. IOI allows operators involved with session signalling to identify each other by exchanging operator identification information within the SIP signalling. The IOI is composed of one pair of originating IOI and terminating IOI. Additionally, one or more transit IOI values may occur. The IOI concept may help to support inter operator charging. The following requirements relate to the IOI concept: a) The IOI concept shall allow operators to uniquely identify each other for the SIP based requests; for example between A's Home PLMN and B's Home PLMN or between an A's Home PLMN and a A's Visited PLMN. b) The IOI concept can be used for inter operator accounting identification purposes. c) It shall be possible to prevent the information used for IOI from being passed to the UE. d) It shall be possible to apply the IOI concept on a peer to peer basis between operators. It shall be possible to use different identity values for operator identification between operators involved in IMS session related procedures and session unrelated procedures. e) IOI identities shall be included within SIP signalling: 1) When a SIP request is passed out of an IMS network the IOI identity of that IMS network (referred as originating IOI) shall be included in the SIP signalling. 2) When a SIP response is returned the IOI identity of that responding IMS network (referred as terminating IOI) shall be included in the SIP signalling. 3) For interconnection scenarios where one or more transit operators are between the originating and terminating operator, the identities of involved transit operators (referred as transit IOI) may be included in the SIP signalling. It should be noted that transit operators can be selected independently for each SIP method and direction of request. Due to operator policy, a transit operator may also hide his identity by adding a void value. Addition and deletion of transit IOI values are operator configurable. Details are described in the TS 24.229[ IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 ] [211]. 3a) The transit operator may provide IMS application servers to an operator network. The set of transit IOI values received in any SIP request or SIP response may be delivered to the IMS application server as per operator policy. 4) The set of originating IOI, transit IOI(s), and terminating IOI is applicable to a single inter IMS network signaling exchange (e.g., A’s Visited PLMN and A’s Home PLMN or A’s Home PLMN to B’s Home PLMN). When the SIP signaling progresses to another PLMN a new set of originating IOI, transit IOI(s), and terminating IOI is generated. The set of IOI values generated for one inter-operator signaling exchange should not be passed to the operators involved in a subsequent inter-operator signaling exchange. For example, the set of IOIs for the path from A’s Visited PLMN to A’s Home PLMN is different than for the path from A’s Home PLMN to B’s Home PLMN and the set of IOI values for one should not be transmitted across the other. 5) The path between an S-CSCF and an application server is an independent signaling exchange from those signaling exchanges between PLMNs. As such, the set of originating and terminating IOIs exchanged on those paths should not be transmitted on the path toward the application server. In addition, any set of originating and terminating IOIs for the path from the S-CSCF to an application server should not be transmitted on any other path from the S-CSCF. The set of transit IOI values received in any SIP request or SIP response may be delivered to the IMS application server as per operator policy. This set of transit IOI values delivered to the IMS application server do not reflect inter operator path between the S-CSCF and the application server, but rather the path either inbound to the S-CSCF or outbound from the S-CSCF and may be useful for operator-specific application processing in the application server. NOTE 0: No transit networks are expected between the S-CSCF and a 3rd party application server. f) Each IMS network is responsible for including its own unique IOI Identity into the SIP signalling. The IOI Identity shall be unique for each IMS operator (for example the IOI Identity of Home Operator A is different from Home Operator B). g) Three types of IOI shall be defined: 1) Type 1 IOI: between the Home PLMN and a Visited PLMN for an end user in roaming situation (case when the P-CSCF is located in a visited network); 2) Type 2 IOI: between the IMS network operator which holds the subscription of the originating end user and the IMS network operator which holds the subscription of the terminating end user. In case of redirection, Type 2 IOI can be used between IMS network operators which hold a subscription of the terminating end user, i.e. between the terminating party's IMS network operator from which the session is redirected to the terminating party's IMS network operator to which the session is redirected. In case Visited PLMN loopback is applied for Roaming Architecture for Voice over IMS with Local Breakout, Type 2 IOI can be used between A’s Visited PLMN and B’s Home PLMN. 3) Type 3 IOI: between the home IMS network operator and a service provider; h) For Type 1 IOI, the P-CSCF is responsible for generating the originating IOI and the S-CSCF in the Home PLMN is responsible for generating the terminating IOI; For Type 1 IOI, the "enhanced MSC for ISC" is responsible for generating the originating IOI. In case Visited PLMN loopback is applied for Roaming Architecture for Voice over IMS with Local Breakout, Type 1 IOI is also used between A’s Home PLMN and Visited PLMN on the loopback path in which the S-CSCF is responsible for generating the originating IOI and the TRF is responsible for generating the terminating IOI. i) For Type 2 IOI, the S-CSCF in the originating party's home IMS network or the E-CSCF in the originating party's local network or the originating MGCF is responsible for generating the originating IOI and the S-CSCF in the terminating party's IMS home network or the terminating MGCF is responsible for generating the terminating IOI. In case of redirection by the S-CSCF, the S-CSCF-in the terminating party's IMS network operator from which the session is redirected- is responsible for generating the originating IOI and the S-CSCF in the terminating party's IMS network operator or the terminating MGCF- to which the session is redirected- is responsible for generating the terminating IOI. In case of Visited PLMN loopback is applied for Roaming Architecture for Voice over IMS with Local Breakout, the TRF in A’s Visited PLMN is responsible for generating the originating IOI, and the S-CSCF in the B’s Home PLMN is responsible for generating the terminating IOI. NOTE 1: The originating IOI generated by the MGCF may not be reliable depending on Operators’ network configuration. j) For Type 3 IOI, when forwarding a request to an AS, the S-CSCF in the Home PLMN is responsible for generating the originating IOI and the AS contacted by this S-CSCF is responsible for generating the terminating IOI. For a Type 3 IOI, when an AS initiates a request, the AS is responsible for generating the originating IOI and the S-CSCF or I-CSCF contacted by this AS is responsible for generating the terminating IOI. For Type 3 IOI, when the E-CSCF forwards a request to the EATF or to the LRF, the E-CSCF is responsible for generating the originating IOI, and the EATF and LRF are responsible for generating the terminating IOI. For Type 3 IOI, when the LRF initiates a request to the E-CSCF, the LRF is responsible for generating the originating IOI, and the E-CSCF is responsible for generating the terminating IOI. k) IOI Identities received in the session signalling shall be incorporated into the CDRs produced by the IMS network elements. The operator identification information may be used for inter operator accounting purposes. l) The allocation of the IOI values for the operators is outside the scope of 3GPP standardization. NOTE 2: The relationship of the IOI concept with security aspects between operators is not specified in this document. | 3GPP TS 32.240 | Telecommunication management; Charging management; Charging architecture and principles | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 5.3.4.3 |
5,076 | 4.15.13.6 Specific procedure for end-to-end data volume transfer time related member UE filtering criteria 4.15.13.6.1 General | An AF may invoke Nnef_MemberUESelectionAssistance_Subscribe service operation with end-to-end data volume transfer time related filtering criteria for receiving a list of UEs that fulfil the filtering criteria. In addition to the mandatory parameters, the AF may also include in the request: - End-to-end data volume transfer time filtering criteria: this may include the average end-to-end data volume transfer time for a specific data volume between UE and AF and/or the variance of the end-to-end data volume transfer time. - An Area of Interest: location area of the candidate UEs. - Time windows for selecting the candidate UEs: start time and stop time. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.15.13.6 |
5,077 | 5.3.13A Forbidden PLMN lists | In N1 mode, two lists of forbidden PLMN are managed independently per access type, i.e., 3GPP access or non-3GPP access: - the list of "forbidden PLMNs" as defined in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5] is applicable for 3GPP access in N1 mode. The same list is used by 5GMM for 3GPP access, EMM, GMM and MM (see 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15] and 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [12]), regardless whether the UE is operating in single-registration mode or dual-registration mode. - the list of "forbidden PLMNs for non-3GPP access to 5GCN" as defined in 3GPP TS 24.502[ Access to the 3GPP 5G Core Network (5GCN) via non-3GPP access networks ] [18] is applicable for 5GMM for non-3GPP access. The list of "forbidden PLMNs for GPRS service" as defined in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5] and 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [12] is applicable for 3GPP access in N1 mode. The same list is used by 5GMM for 3GPP access, EMM and GMM (see 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15] and 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [12]), regardless whether the UE is operating in single-registration mode or dual-registration mode. The forbidden PLMN lists shall be maintained across activation and deactivation of SNPN access operation mode. NOTE: On timer T3245 expiry when the UE supports access to an SNPN using credentials from a credentials holder using PLMN subscription, and the UE is operating in SNPN access operation mode, as an implementation option the UE can delete the list of "forbidden PLMNs", "forbidden PLMNs for non-3GPP access to 5GCN" and "forbidden PLMNs for GPRS service". | 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.13A |
5,078 | 5.6.9.2.2 SSC Mode 2 | If a PDU Session of SSC mode 2 has a single PDU Session Anchor, the network may trigger the release of the PDU Session and instruct the UE to establish a new PDU Session to the same data network immediately. The trigger condition depends on operator policy e.g. request from Application Function, based on load status, etc. At establishment of the new PDU Session, a new UPF acting as PDU Session Anchor can be selected. Otherwise, if a PDU Session of SSC mode 2 has multiple PDU Session Anchors (i.e. in the case of multi-homed PDU Sessions or in the case that UL CL applies to a PDU Session of SSC mode 2), the additional PDU Session Anchors may be released or allocated. SSC mode 2 may apply to any PDU Session type and to any access type. SSC mode 2 is optional to be supported in the UE. NOTE 1: Features depending on SSC mode 2 will not work with the lack of support for SSC mode 2 in the UE. NOTE 2: In UL CL mode, the UE is not involved in PDU Session Anchor re-allocation, so that the existence of multiple PDU Session Anchors is not visible to the UE. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.6.9.2.2 |
5,079 | – SL-RLC-Config | The IE SL-RLC-Config is used to specify the RLC configuration of sidelink DRB. RLC AM configuration is only applicable to the unicast NR sidelink communication. SL-RLC-Config information element -- ASN1START -- TAG-SL-RLC-CONFIG-START SL-RLC-Config-r16 ::= CHOICE { sl-AM-RLC-r16 SEQUENCE { sl-SN-FieldLengthAM-r16 SN-FieldLengthAM OPTIONAL, -- Cond SLRBSetup sl-T-PollRetransmit-r16 T-PollRetransmit, sl-PollPDU-r16 PollPDU, sl-PollByte-r16 PollByte, sl-MaxRetxThreshold-r16 ENUMERATED { t1, t2, t3, t4, t6, t8, t16, t32 }, ... }, sl-UM-RLC-r16 SEQUENCE { sl-SN-FieldLengthUM-r16 SN-FieldLengthUM OPTIONAL, -- Cond SLRBSetup ... }, ... } -- TAG-SL-RLC-CONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
5,080 | 4.2.4.3 UE Configuration Update procedure for transparent UE Policy delivery | This procedure is initiated when the PCF wants to update UE policy information (i.e. UE policy) in the UE configuration. In the non-roaming case, the V-PCF is not involved and the role of the H-PCF is performed by the PCF. For the roaming scenarios, the V-PCF interacts with the AMF and the H-PCF interacts with the V-PCF. For the purpose of URSP delivery via EPS, the delivery procedure of UE Policy Containers from the SMF+PGW-C to the UE is specified in clause 4.11.0a.2a.10. Figure 4.2.4.3-1: UE Configuration Update procedure for transparent UE Policy delivery 0. PCF decides to update UE policy based on triggering conditions such as an initial registration, registration with 5GS when the UE moves from EPS to 5GS, or need for updating UE policy as follows: - For the case of initial registration and registration with 5GS when the UE moves from EPS to 5GS, the PCF compares the list of PSIs included in the UE policy information in Npcf_UEPolicyControl_Create request and determines, as described in clause 6.1.2.2.2 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20], whether UE policy information have to be updated and be provided to the UE via the AMF using DL NAS TRANSPORT message; and - For the network triggered UE policy update case (e.g. the change of UE location, the change of Subscribed S-NSSAIs as described in clause 6.1.2.2.2 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]), the PCF checks the latest list of PSIs to decide which UE policies have to be sent to the UE. The PCF checks if the size of the resulting UE policy information exceeds a predefined limit: - If the size is under the limit, then UE policy information are included in a single Namf_Communication_N1N2MessageTransfer service operation as described below. - If the size exceeds the predefined limit, the PCF splits the UE policy information in smaller, logically independent UE policy information ensuring the size of each is under the predefined limit. Each UE policy information will be then sent in separated Namf_Communication_N1N2MessageTransfer service operations as described below. NOTE 1: NAS messages from AMF to UE do not exceed the maximum size limit allowed in NG-RAN (PDCP layer), so the predefined size limit in PCF is related to that limitation. NOTE 2: The mechanism used to split the UE policy information is described in TS 29.507[ 5G System; Access and Mobility Policy Control Service; Stage 3 ] [32]. 0a. If the PCF has not subscribed to be notified by the AMF about the UE response to an update of UE policy information, the PCF subscribes to the AMF to be notified about the UE response to an update of UE policy information. 1. PCF invokes Namf_Communication_N1N2MessageTransfer service operation provided by the AMF. The message includes SUPI, UE Policy Container. 2. If the UE is registered and reachable by AMF in either 3GPP access or non-3GPP access, AMF shall transfers transparently the UE Policy container to the UE via the registered and reachable access. If the UE is registered in both 3GPP and non-3GPP accesses and reachable on both access and served by the same AMF, the AMF transfers transparently the UE Policy container to the UE via one of the accesses based on the AMF local policy. If the UE is not reachable by AMF over both 3GPP access and non-3GPP access, the AMF reports to the PCF that the UE Policy container could not be delivered to the UE using Namf_Communication_N1N2TransferFailureNotification as in the step 5 in clause 4.2.3.3. If AMF decides to transfer transparently the UE Policy container to the UE via 3GPP access, e.g. the UE is registered and reachable by AMF in 3GPP access only, or if the UE is registered and reachable by AMF in both 3GPP and non-3GPP accesses served by the same AMF and the AMF decides to transfer transparently the UE Policy container to the UE via 3GPP access based on local policy and the UE is in CM-IDLE and reachable by AMF in 3GPP access, the AMF starts the paging procedure by sending a Paging message described in the step 4b of Network Triggered Service Request (in clause 4.2.3.3). Upon reception of paging request, the UE shall initiate the UE Triggered Service Request procedure (clause 4.2.3.2). 3. If the UE is in CM-CONNECTED over 3GPP access or non-3GPP access, the AMF transfers transparently the UE Policy container (UE policy information) received from the PCF to the UE. The UE Policy container includes the list of Policy Sections as described in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. 4. The UE updates the UE policy provided by the PCF and sends the result to the AMF. 5. The AMF forwards the response of the UE to the PCF using Namf_Communication_N1MessageNotify. The PCF maintains the latest list of PSIs delivered to the UE and updates the latest list of PSIs in the UDR by invoking Nudr_DM_Update (SUPI, Policy Data, Policy Set Entry, updated PSI data) service operation. If the PCF is notified about UE Policy delivery failure from the AMF, the PCF may initiate UE Policy Association Modification procedure to provide a new trigger "Connectivity state changes" in Policy Control Request Trigger of UE Policy Association to AMF as defined in clause 4.16.12.2. The PCF may re-initiate the UE Configuration Update procedure for transparent UE Policy delivery as in step 1 when the PCF is notified of the UE connectivity state changed to CONNECTED. NOTE 3: For backward compatibility the PCF may subscribe the "Connectivity state changes (IDLE or CONNECTED)" event in Rel-15 AMF as defined in clause 5.2.2.3. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.2.4.3 |
5,081 | 5.8.9.1a.5.1 Additional Sidelink RLC Bearer release conditions | For NR sidelink communication, additional sidelink RLC bearer release is initiated in the following cases: 1> for sidelink DRB, the release conditions are met as in clause 5.8.9.1a.1.1 for the associated sidelink DRB; or 1> for sidelink SRB, the release conditions are met as in clause 5.8.9.1a.3 for the associated sidelink SRB; or 1> for sidelink DRB, if SL-RLC-BearerConfigIndex (if any) of the sidelink DRB or SRB is included in sl-RLC-BearerToReleaseList in RRCReconfigurationSidelink; 1> for sidelink DRB, if SL-RLC-BearerConfigIndex (if any) of the additional Sidelink RLC Bearer is included in sl-RLC-BearerToReleaseListSizeExt in sl-ConfigDedicatedNR and if the SL-TxProfile of the associated QoS flow(s) for the sl-ServedRadioBearer indicates backwardsIncompatible; or 1> for sidelink DRB, if SL-RLC-BearerConfig is received in sl-RLC-BearerToAddModListSizeExt in sl-ConfigDedicatedNR for a sl-ServedRadioBearer, and if the SL-TxProfile of the associated QoS flow(s) for the sl-ServedRadioBearer indicates backwardsCompatible and UE decides not to use PDCP duplication; or 1> for sidelink DRB, if SL-RLC-BearerConfig is received in sl-RLC-BearerConfigListSizeExt in SIB12 or in SidelinkPreconfigNR for a sl-ServedRadioBearer, and if the SL-TxProfile of the associated QoS flow(s) for the sl-ServedRadioBearer indicates backwardsCompatible and UE decides not to use PDCP duplication; 1> for sidelink SRB, if UE decides not to use PDCP duplication; | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.8.9.1a.5.1 |
5,082 | C.2.5 Relationship between bearer capability and low layer compatibility information elements | There shall be no contradiction of information between the low layer compatibility and the bearer capability at the originating side. However, as some bearer capability code points may be modified during the transport of the call (e.g. by the interworking function), this principle implies that there should be minimal duplication of information between the bearer capability information element and the low layer compatibility information element. NOTE: If as a result of duplication, a contradiction occurs at the terminating side between the bearer capability information element and the low layer compatibility information element at the terminating side, the receiving entity shall ignore the conflicting information in the low layer compatibility 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 | C.2.5 |
5,083 | 19.2 Home Network Realm/Domain | The home Network Realm/Domain shall be in the form of an Internet domain name, e.g. operator.com, as specified in IETF RFC 1035 [19] and IETF RFC 1123 [20]. The home Network Realm/Domain consists of one or more labels. Each label shall consist of the alphabetic characters (A-Z and a-z), digits (0-9) and the hyphen (-) in accordance with IETF RFC 1035 [19]. Each label shall begin and end with either an alphabetic character or a digit in accordance with IETF RFC 1123 [20]. The case of alphabetic characters is not significant. The Home Network Realm/Domain shall be in the form of "epc.mnc<MNC>.mcc<MCC>.3gppnetwork.org", where "<MNC>" and "<MCC>" fields correspond to the MNC and MCC of the operator's PLMN. Both the "<MNC>" and "<MCC>" fields are 3 digits long. If the MNC of the PLMN is 2 digits, then a zero shall be added at the beginning. For example, the Home Network Realm/Domain of an IMSI shall be derived as described in the following steps: 1. take the first 5 or 6 digits, depending on whether a 2 or 3 digit MNC is used (see 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [27]) and separate them into MCC and MNC; if the MNC is 2 digits then a zero shall be added at the beginning; 2. use the MCC and MNC derived in step 1 to create the "mnc<MNC>.mcc<MCC>.3gppnetwork.org" domain name; 3. add the label "epc" to the beginning of the domain name. An example of a Home Network Realm/Domain is: IMSI in use: 234150999999999; Where: MCC = 234; MNC = 15; MSIN = 0999999999; Which gives the Home Network Realm/Domain name: epc.mnc015.mcc234.3gppnetwork.org. NOTE: If it is not possible for a UE to identify whether a 2 or 3 digit MNC is used (e.g. USIM is inserted and the length of MNC in the IMSI is not available in the "Administrative data" data file), it is implementation dependent how the UE determines the length of the MNC (2 or 3 digits). | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 19.2 |
5,084 | 5.6.2 Paging procedure 5.6.2.1 General | The paging procedure is performed only in 3GPP access and used by the network to request the establishment of a NAS signalling connection to the UE. The paging procedure is also used by the network to request the UE to re-establish the user-plane resources of PDU sessions for downlink user data transport. Another purpose of the paging procedure is to request the UE to re-establish the user-plane resources of PDU session(s) associated with non-3GPP access over 3GPP access. Additionally, the network can use the paging procedure to initiate the mobile terminating SMS. For the UE using eDRX, the network initiates the paging procedure when NAS signalling messages or user data is pending to be sent to the UE within the paging time window and requests the lower layers to include the eDRX cycle length and paging time window length in the paging message. If NAS signalling messages or user data is pending to be sent to the UE outside the paging time window and the eDRX value that the network provides to the UE in the Negotiated extended DRX parameters IE during the last registration procedure indicates: a) the eDRX cycle length duration of the E-UTRA cell connected to 5GCN, is higher than 5.12 seconds; or b) the eDRX cycle length duration of the NR cell connected to 5GCN, is higher than 10.24 seconds, the network initiates the paging procedure at T time ahead of the beginning of the next paging time window. NOTE: T time is a short time period based on implementation. The operator can take possible imperfections in the synchronization between the 5GCN and the UE into account when choosing T time. If the network detects that the pending user data to be sent to the UE is related to the voice service as specified in 3GPP TS 23.502[ Procedures for the 5G System (5GS) ] [9] and the network decides to initiate the paging procedure based on the stored paging restriction information, if any, the AMF should request the lower layer to include the Voice Service Indication in the paging message when the UE and the network support the paging indication for voice services. | 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.2 |
5,085 | Annex N (informative): Support for access to Localized Services N.1 General | A Localized Service is a service, which is provided at specific/limited area and/or can be bounded in time. The service can be realized via applications (e.g. live or on-demand audio/video stream, electric game, IMS, etc.), or connectivity (e.g. UE to UE, UE to Data Network, etc.). A Localized Service provider is an application provider or network operator who make their services localized and that are offered to the end user via a network. A network providing Localized Services can be an SNPN or a PNI-NPN. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | Annex |
5,086 | 7.5.3 5GS session management | The following UE procedures shall apply for handling an error encountered with a mandatory information element in a 5GSM message: a) If the message is a PDU SESSION ESTABLISHMENT ACCEPT, the UE shall initiate PDU session release procedure by sending a PDU SESSION RELEASE REQUEST message with 5GSM cause #96 "invalid mandatory information". b) Void. c) If the message is a PDU SESSION RELEASE COMMAND, a PDU SESSION RELEASE COMPLETE message with 5GSM cause #96 "invalid mandatory information" shall be returned. The following network procedures shall apply for handling an error encountered with a mandatory information element in a 5GSM message: a) If the message is a PDU SESSION ESTABLISHMENT REQUEST, a PDU SESSION ESTABLISHMENT REJECT message with 5GSM cause #96 "invalid mandatory information" shall be returned. b) If the message is a PDU SESSION MODIFICATION REQUEST, a PDU SESSION MODIFICATION REJECT message with 5GSM cause #96 "invalid mandatory information" shall be returned. c) If the message is a PDU SESSION RELEASE REQUEST, a PDU SESSION RELEASE REJECT message with 5GSM cause #96 "invalid mandatory information" shall be returned. | 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 | 7.5.3 |
5,087 | 6.5.2A Transmit modulation quality for CA | For inter-band carrier aggregation with uplink assigned to two E-UTRA bands, the requirements shall apply on each component carrier as defined in clause 6.5.2 with all component carriers active. If two contiguous component carriers are assigned to one E-UTRA band, the requirements in subclauses 6.5.2A.1, 6.5.2A.2, and 6.5.2A.3 apply for those component carriers. The requirements in this clause apply with PCC and SCC in the UL configured and activated: PCC with PRB allocation and SCC without PRB allocation and without CSI reporting and SRS configured. | 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.5.2A |
5,088 | 9.3.3.1.1 FDD | For the parameters specified in Table 9.3.3.1.1-1, and using the downlink physical channels specified in Annex C.3.2, the minimum requirements are specified in Table 9.3.3.1.1-2 and by the following a) a sub-band differential CQI offset level of +2 shall be reported at least % for at least one of the sub-bands of full size at the channel edges; b) the ratio of the throughput obtained when transmitting on a randomly selected sub-band among the sub-bands with the highest differential CQI offset level the corresponding TBS and that obtained when transmitting the TBS indicated by the reported wideband CQI median on a randomly selected sub-band in set S shall be ≥ ; The requirements only apply for sub-bands of full size and the random scheduling across the sub-bands is done by selecting a new sub-band in each TTI for FDD, each available downlink transmission instance for TDD. Sub-bands of a size smaller than full size are excluded from the test. Table 9.3.3.1.1-1 Sub-band test for single antenna transmission (FDD) Table 9.3.3.1.1-2 Minimum requirement (FDD) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 9.3.3.1.1 |
5,089 | I.2.2.2.2 Procedure | Figure: I.2.2.2.2-1: Primary authentication with external domain 0. The UE shall be configured with credentials from the Credentials holder e.g. SUPI containing a network-specific identifier and credentials for the key-generating EAP-method used. As part of configuration of the credentials, the UE shall also be configured with an indication that the UE shall use MSK for the derivation of KAUSF after the success of the primary authentication. The exact procedures used to configure the UE are not specified in the present document. It is further assumed that there exists a trust relation between the SNPN and the Credentials holder AAA Server. These entities need to be mutually authenticated, and the information transferred on the interface need to be confidentiality, integrity and replay protected. When the procedures of this clause are used for onboarding purposes, the onboarding specific adaptations includes: the 'credentials' used is 'Default credentials', the 'SUPI' used is 'onboarding SUPI', the 'SUCI' used is 'onboarding SUCI' respectively. 1. The UE shall select the SNPN and initiate UE registration in the SNPN. For construction of the SUCI, existing methods in clause 6.12 can be used. Otherwise, if the EAP method supports SUPI privacy, the UE may send an anonymous value SUCI based on configuration. 2. The AMF within the SNPN shall initiate a primary authentication for the UE using a Nausf_UEAuthentication_Authenticate service operation with the AUSF. The AMF shall discover and select an AUSF based on criterions specified in TS 23.501[ System architecture for the 5G System (5GS) ] [2] clause 5.30.2.9.2. 3. In the case of onboarding, steps 3-5 are omitted. If steps 3-5 are not omitted, the AUSF shall initiate a Nudm_UEAuthentication_Get service operation. The AUSF shall discover and select a UDM based on criterions specified in TS 23.501[ System architecture for the 5G System (5GS) ] [2] clause 5.30.2.9. NOTE 1: SUPI will be used instead of SUCI in the case of a re-authentication. 4. In case the UDM receives a SUCI, the UDM shall resolve the SUCI to the SUPI before checking the authentication method applicable for the SUPI. The UDM decides to run primary authentication with an external entity based on subscription data. In case the UDM receives an anonymous SUCI, the UDM decides to run primary authentication with an external entity based the realm part of the SUPI in NAI format. NOTE 1a: The UDM needs to be configured with a list of realms and the intended authentication server In case the UDM receives an anonymous SUCI that does not contain the realm part, the UDM shall abort the procedure. Otherwise, the UDM authorizes the UE based on realm part of SUCI and send the anonymous SUPI and the indicator to the AUSF as described in step5. The anonymous SUPI shall be a NAI format. 5. In case the UDM received a SUCI in previous steps, the UDM shall provide the AUSF with the SUPI or anonymous SUPI and shall indicate to the AUSF to run primary authentication with a AAA Server in an external Credentials holder. When a Credentials Holder using AAA Server is used for primary authentication, the AUSF uses the MSK to derive KAUSF. It is strongly recommended that the same credentials that are used for authentication between UE and the 5G SNPN are not used for the authentication between the UE and a non-5G network, assuming that 5G SNPN and non-5G network are in different security domains. NOTE 2: MSKs obtained from the non-5G network could be used to impersonate the 5G SNPN towards the UE. 6. Based on the indication from the UDM, the AUSF shall select an NSSAAF as defined in TS 23.501[ System architecture for the 5G System (5GS) ] [2] and initiate a Nnssaaf_AIWF_Authenticate service operation towards that NSSAAF as defined in clause 14.4.2. 7. The NSSAAF shall select AAA Server based on the domain name corresponding to the realm part of the SUPI. The NSSAAF shall perform related protocol conversion and relay EAP messages to the AAA Server. NOTE 3: The interface and protocol between NSSAAF and AAA is out of scope of the present document and existing AAA protocols such as RADIUS or Diameter can be used. 8. The UE and AAA Server shall perform mutual authentication. The AAA Server shall act as the EAP Server for the purpose of primary authentication. The EAP Identity received by the AAA Server in the EAP-Response/Identity message in step 7 may contain anonymised SUPI. In such cases, AAA Server uses the EAP-method specific EAP Identity request/response messages to obtain the UE identifier as part of the EAP authentication between the UE and the AAA Server. 9. After successful authentication, the MSK and the SUPI (i.e., the UE identifier that is used for the successful EAP authentication) shall be provided from the AAA Server to the NSSAAF. 10. The NSSAAF returns the MSK and the SUPI to the AUSF using the Nnssaaf_AIWF_Authenticate service operation response message. The SUPI received from the AAA shall be used when deriving 5G keys (e.g., KAMF) that requires SUPI as an input for the key derivation. 11-13. In case of onboarding or SUCI received in step 2 is not anonymous, steps 11-13 are omitted. Otherwise, the AUSF verifies that the SUPI corresponds to a valid subscription in the SNPN by informing the UDM about the authentication result for the received SUPI using a Nudm_UEAuthentication_ResultConfirmation service operation. The UDM stores the authentication state for the SUPI and if there is not a subscription corresponding to the SUPI, the UDM shall return an error. If the verification of the SUPI is not successful, then the AUSF rejects the UE access to the SNPN. NOTE 4: If the above failure happens, the error is no failed authentication but lacking subscription in the SNPN. 14. The AUSF shall use the most significant 256 bits of MSK as the KAUSF. The AUSF shall also derive KSEAF from the KAUSF as defined in Annex A.6. 15. The AUSF shall send the successful indication together with the SUPI of the UE to the AMF/SEAF together with the resulting KSEAF. 16. The AMF shall send the EAP success in a NAS message. 17. The UE shall derive the KAUSF from MSK as described in step 11 according to the pre-configured indication as described in step 0. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | I.2.2.2.2 |
5,090 | 4.7.5 NAS signalling using trusted WLAN access network | A trusted WLAN interworking function (TWIF) provides functionalities for a non-5G capable over WLAN (N5CW) device to access 5GCN, including: a) NAS signalling over N1 NAS signalling connection with AMF; and b) PDU session establishment, modification and release on behalf of the N5CW device, over N2 connection with the AMF. The TWIF registers on behalf of the N5CW device to an AMF according to subclause 5.5.1 by populating the parameters for the registration by using implementation specific default values which are the same for N5CW devices. The TWIF may request to establish a PDU session as specified in subclause 6.4.1.2 on behalf of the N5CW device upon receipt of an IP configuration request from the N5CW device by populating either all the required parameters or part of the required parameters for the PDU session establishment by using implementation specific default values from the TWIF's configuration. Only one PDU session is supported when N5CW device accessing 5GC via the TWIF. NOTE 1: If part of the required parameters for the PDU session establishment is provided by the TWIF, the remaining of the required parameters are determined by the AMF or the SMF based on the N5CW device's subscription information. Upon loss of the IP address of the N5CW device, the TWIF acting on behalf of the N5CW device shall initiate the UE-requested PDU session release procedure as defined in subclause 6.4.3. NOTE 2: The established PDU session on behalf of the N5CW device can be modified by the TWIF or the network. | 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.7.5 |
5,091 | 8.1 Uplink-downlink frame timing | Transmission of the uplink radio frame number from the UE shall start seconds before the start of the corresponding downlink radio frame at the UE. Figure 8.1-1: Uplink-downlink timing relation Except for the cases mentioned in Table 8.1-1, Table 8.1-2 and Table 8.1-3, the range of is: . For frame structure type 1 and for frame structure type 2 unless stated otherwise in [4]. Note that not all slots in a radio frame may be transmitted. One example hereof is TDD, where only a subset of the slots in a radio frame is transmitted. is defined in different ranges depending on the UE configuration according to Table 8.1-1, Table 8.1-2 and Table 8.1-3. In case of subslot based transmission (Table 8.1-2 and Table 8.1-3), the UE is configured by higher layer signalling a processing timeline and an associated range of timing advance. The quantity is derived from the higher-layer parameters TACommon, TACommonDrift, and TACommonDriftVariation if configured (see Clause 4.2.3 in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [4]), otherwise . The quantity is computed by the UE based on UE position and serving satellite-ephemeris-related higher-layers parameters if configured, otherwise . Table 8.1-1: Ranges of for a UE configured with SCG, short processing time or slot-based transmission in both DL and UL Table 8.1-2: Ranges of for a UE configured with subslot-based transmission in both DL and UL (dl-STTI-Length and ul-STTI-Length, see TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [9]. set to 'subslot') Table 8.1-3: Ranges of for a UE configured with subslot-based transmission in DL and slot-based transmission in UL (dl-STTI-Length and ul-STTI-Length, see TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [9], set to 'subslot' and 'slot', respectively) In all other cases the range of is: . | 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 | 8.1 |
5,092 | 6.11.3 Routing, BAP Header Rewriting and BH-RLC-channel Mapping on BAP sublayer | Figure 6.11.3-1: Routing and BH RLC channel selection on BAP sublayer Routing on BAP sublayer uses the BAP routing ID, which is configured by the IAB-donor-CU. The BAP routing ID consists of BAP address and BAP path ID. The BAP address is used for the following purposes: 1. Determination if a packet has reached the destination node, i.e. IAB-node or IAB-donor-DU, on BAP sublayer. This is the case if the BAP address in the packet's BAP header matches the BAP address configured via RRC on the IAB-node, or via F1AP on the IAB-donor-DU. For a dual-connected boundary IAB-node that is configured with two BAP addresses, the BAP address in the packet's BAP header is matched with the BAP address configured by the CU of the IAB topology, where the packet has been received. 2. Determination of the next-hop node for packets that have not reached their destination. This applies to packets arriving from a prior hop on BAP sublayer or that have been received from IP layer. For packets arriving from a prior hop or from upper layers, the determination of the next-hop node is based on a routing configuration provided by the IAB-donor-CU via F1AP signalling or a default configuration provided by the IAB-donor-CU via RRC signalling. This F1AP configuration contains the mapping between the BAP routing ID carried in the packet's BAP header and the next-hop node's BAP address. Table 6.11.3-1: Routing configuration The IAB-node resolves the next-hop BAP address to a physical backhaul link. For this purpose, the IAB-donor-CU provides the IAB-node/IAB-donor-DU with its child-node's BAP address via F1AP, and it provides the IAB-node with its parent-node's BAP address via RRC. For a boundary IAB-node, the routing configuration also indicates the IAB topology it applies to. The BH link to the next-hop node and the next-hop BAP address belong to the IAB topology of the CU that provided the RRC configuration of the BH link to that next-hop node. The IAB-node can receive multiple routing configurations with the same destination BAP address but different BAP path IDs. These routing configurations may resolve to the same or different egress BH links. In case the BH link resolved from the routing entry is considered unavailable for this packet, the IAB-node may perform local rerouting as defined in TS 38.340[ NR; Backhaul Adaptation Protocol (BAP) specification ] [31], i.e., select another BH link by considering only the packet's BAP address or, in some cases, by header rewriting. In this manner, the packet can be delivered via an alternative path as defined in TS 38.340[ NR; Backhaul Adaptation Protocol (BAP) specification ] [31]. A BH link may be considered unavailable in case the BH link has RLF. A parent link may be considered unavailable after a BH RLF detection indication has been received on this parent link and before a subsequent BH RLF recovery indication has been received on the same parent link. For DL traffic, a BH link may be considered unavailable for BAP PDUs carrying a certain BAP routing ID due to congestion derived from flow-control feedback information related to this BAP routing ID, as defined in TS 38.340[ NR; Backhaul Adaptation Protocol (BAP) specification ] [31]. For a boundary IAB-node, the routing configuration may carry information on the IAB topology the configuration applies to. The IAB-node may rewrite the BAP routing ID in the packet's BAP header under the following circumstances: - A packet is routed between two IAB topologies via a boundary IAB-node as defined in TS 38.401[ NG-RAN; Architecture description ] [31]. In this case, the BAP routing ID carried by the received BAP PDU is allocated by the IAB-donor-CU of the ingress IAB topology, while the BAP routing ID carried by the BAP PDU after header rewriting is allocated by the IAB-donor-CU of the egress IAB topology. - An upstream packet is locally re-routed to a different IAB-donor-DU than indicated by the BAP address in the BAP header of the received packet. The rewritten BAP header carries the BAP address of the alternative IAB-donor-DU and the BAP path ID for a path to this alternative IAB-donor-DU. BAP header rewriting for upstream inter-IAB-donor-DU local rerouting is only applied if neither routing nor local re-routing without header rewriting resolve to an available egress BH link. For packets that are routed between two IAB topologies via a boundary node, the BAP header rewriting configuration is provided via F1AP, and it includes the ingress BAP routing ID, the egress BAP routing ID, and it indicates the egress IAB topology: Table 6.11.3-2a: BAP header rewriting configuration For upstream packets that are locally re-routed to a different IAB-donor-DU, the BAP header is rewritten with a BAP routing ID contained in the routing entry that was selected for re-routing. Details of BAP header rewriting are defined in TS 38.340[ NR; Backhaul Adaptation Protocol (BAP) specification ] [31]. When routing a packet from an ingress to an egress BH link, the IAB-node derives the egress BH RLC channel on the egress BH link through an F1AP-configured mapping from the BH RLC channel used on the ingress BH link. The BH RLC channel IDs used for ingress and egress BH RLC channels are generated by the IAB-donor-CU. Since the BH RLC channel ID only has link-local scope, the mapping configurations also include the BAP addresses of prior and next hop: Table 6.11.3-2: BH RLC channel mapping configuration For a boundary IAB-node, the BH RLC channel mapping configuration may also include indicators for the IAB topology of the ingress and of the egress BH link. The IAB-node resolves the BH RLC channel IDs from logical channel IDs based on the configuration by the IAB-donor-CU. The IAB-MT obtains the BH RLC channel ID in the RRC configuration of the corresponding logical channel. The IAB-DU obtains the BH RLC channel ID in the F1AP configuration of the BH RLC channel. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 6.11.3 |
5,093 | 13.2.4.3.2 dataToIntegrityProtectAndCipher | The dataToIntegrityProtectAndCipher is a JSON patch document as per RFC 6902 [64] that contains all the attribute values that require both encryption and integrity protection. Attribute values may come from any part of the original HTTP message – Pseudo_Headers, HTTP_Headers and Payload. The JSON array shall contain one array entry per attribute value that needs encryption. Each array entry represents the value of the attribute to be protected, and the index in the array is used to reference the protected value within the dataToIntegrityProtect block. This associates each attribute in the dataToIntegrityProtectAndCipher block with the original attribute in the dataToIntegrityProtect block. This is needed to reassemble the original message at the receiving SEPP. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 13.2.4.3.2 |
5,094 | – AdvancedReceiver-MU-MIMO | The IE AdvancedReceiver-MU-MIMO is used to provide a set of assistance information for R-ML (reduced complexity ML) receivers with enhanced inter-user interference suppression for MU-MIMO transmissions. AdvancedReceiver-MU-MIMO information element -- ASN1START -- TAG-ADVANCEDRECEIVER-MU-MIMO-START AdvancedReceiver-MU-MIMO-r18 ::= SEQUENCE { precodingAndResourceAllocation-r18 BOOLEAN OPTIONAL, -- Need M dmrsPowerBoosting-r18 BOOLEAN OPTIONAL, -- Need M pdsch-TimeDomainAllocation-r18 BOOLEAN OPTIONAL, -- Need M mcs-Table-r18 ENUMERATED {qam1024, qam256, qam64} OPTIONAL, -- Need R advReceiver-MU-MIMO-DCI-1-1-r18 ENUMERATED {enabled} OPTIONAL -- Need R } -- TAG-ADVANCEDRECEIVER-MU-MIMO-STOP -- ASN1STOP Editor's note: whether the IE type BOOLEAN within AdvancedReceiver-MU-MIMO-r18 needs to be changed to ENUMERATED {true} depends on further RAN4 clarification. Editor's note: whether dmrsPowerBoosting-r18 needs to be removed depends on further RAN4 clarification. NOTE: the same DMRS sequence represents the same root DMRS sequence r(n), see TS 38.211[ NR; Physical channels and modulation ] [16], clause 7.4.1.1.1. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
5,095 | 5.2.7.3 Nnrf_NFDiscovery service 5.2.7.3.1 General | Service description: This service enables one NF or SCP to discover a set of NF instances with specific NF service or a target NF type or one or more SCPs. The service also enables one NF service or SCP to discover a specific NF service. The service operations defined below allow the NF/NF services or SCP to communicate with NRF. This service also enables an SCP to discover SCPs. NOTE: For the purpose of the Nnrf_NFDiscovery service, the SCP is treated in the same way as NFs. It is designated with a specific NF type. However, the SCP does not support services. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.7.3 |
5,096 | 5.3.3 Potential service requirements | The 3GPP system shall enable an authorised official to query a UTM for information and identities of an active UAS when an authorised official provides a subset of UAS data (e.g. an IMSI, general location, or IMEI). The 3GPP system shall enable an authorised official to query a UTM for the current location(s) of an active UAS when an authorised official provides a subset of UAS data (e.g. an IMSI, general location, or IMEI). The 3GPP system shall enable a UTM to authenticate the identity and authority of the official making a request for UAS identity and information. | 3GPP TS 22.825 | Study on Remote Identification of Unmanned Aerial Systems (UAS) | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 5.3.3 |
5,097 | 5.2.2.3.2 Namf_EventExposure_Subscribe service operation | Service operation name: Namf_EventExposure_Subscribe. Description: The consumer NF uses this service operation to subscribe to or modify event reporting for one UE, a group of UE(s) or any UE. Input, Required: NF ID, Target of Event Reporting: UE(s) ID (SUPI or Internal Group Identifier or indication that any UE is targeted), ((set of) Event ID(s) defined in clause 5.2.2.3.1, Notification Target Address (+ Notification Correlation ID))s, Event Reporting Information defined in Table 4.15.1-1. Input, Optional: (Event Filter (s) associated with each Event ID; Event Filter (s) are defined in clause 5.2.2.3.1, Subscription Correlation ID (in the case of modification of the event subscription), Expiry time, list of group member UE(s) whose subscription to event notification(s) are removed or added for a group-based event notification subscription, operation indication (cancellation or addition), Idle Status Indication request (if UE reachability or Availability after DDN failure reporting is requested). Output, Required: When the subscription is accepted: Subscription Correlation ID (required for management of this subscription), Expiry time (required if the subscription can be expired based on the operator's policy). Output, Optional: First corresponding event report is included, if available (see clause 4.15.1). The NF consumer subscribes to the event notification by invoking Namf_EventExposure to the AMF. The AMF allocates an Subscription Correlation ID for the subscription and responds to the consumer NF with the Subscription Correlation ID. UE ID identifies the UE, SUPI and/or GPSI. Event ID (see clause 4.15.1) identifies the events that the NF consumer is interested in. The Subscription Correlation ID is unique within the AMF Set. The ((set of) Event ID(s), Notification Target Address (+ Notification Correlation ID)) helps the Event Receiving NF to co-relate a notification against a corresponding event subscription for the indicated Event ID. In the case that the NF consumer subscribes to the AMF on behalf of other NF, the NF consumer include the Notification Target Address(+Notification Correlation ID) of other NF for the Event ID which is to be notified to other NF directly and the Notification Target Address(+Notification Correlation ID) of itself for the Subscription Correlation ID change event. Each Notification Target Address(+ Notification Correlation ID) is associated with the related (set of) Event ID(s).When the Subscription Correlation ID change due to the AMF reallocation, the notification is sent to NF consumer which triggers this subscription. Event filter may include "AN type(s)" as part of the list of parameter values to match and it indicates to subscribe the event per Access Type. Event receiving NF ID identifies the NF that shall receive the event reporting. When the consumer NF needs to modify an existing subscription previously created by itself in the AMF, it invokes Namf_EventExposure_Subscribe service operation which contains the Subscription Correlation ID and the new Event Filters with Event ID to the AMF. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.2.3.2 |
5,098 | 8.19.4.2 Intra-gNB-DU switch from direct to indirect path | The signalling flow for U2N Remote UE switch from direct to indirect path without gNB-DU change is shown in Figure 8.19.4.2-1. Figure 8.19.4.2-1: U2N Remote UE Direct-to-indirect Path Switch without gNB-DU change procedure 1. The Uu measurement configuration and measurement report signalling is performed between U2N Remote UE and gNB-CU to evaluate both relay link measurement and Uu link measurement. The U2N Remote UE may report one or multiple candidate U2N Relay UE(s) and Uu measurement results after it measures/discovers the candidate U2N Relay UE(s). 2. The gNB-CU decides to switch the U2N Remote UE to a target U2N Relay UE under the same gNB-DU. 3. The reconfiguration to target U2N Relay UE is performed among U2N Relay UE, gNB-DU and gNB-CU if U2N Relay UE is in RRC_CONNECTED state. The gNB-CU sends an RRCReconfiguration message to the target U2N Relay UE. If the target Relay UE is in RRC_IDLE/INACTIVE state, this step is skipped and the configuration to the target U2N Relay UE is performed in Step 9. 4. gNB-CU sends the UE CONTEXT MODIFICATION REQUEST message for the U2N Remote UE to gNB-DU, which contains the path switch configuration at least. The F1-U packets of the U2N Remote UE can be continuously transmitted via previous tunnels if there is no tunnel update in this step. 5. gNB-DU responds with the UE CONTEXT MODIFICATION RESPONSE message to gNB-CU. 6. gNB-CU sends the DL RRC MESSAGE TRANSFER message by including the RRCReconfiguration message to gNB-DU. The contents in the RRCReconfiguration message may include at least path switch configuration, PC5 Relay RLC channel configuration for relaying traffic, bearer mapping configuration and the associated radio bearer(s). 7. gNB-DU sends the RRCReconfiguration message to the U2N Remote UE. The U2N Remote UE stops UP and CP transmission over Uu after reception of RRCReconfiguration message from the gNB. 8. The U2N Remote UE establishes PC5 connection with target U2N Relay UE. 9. The U2N Remote UE completes the path switch procedure by sending the RRCReconfigurationComplete message to the gNB-DU via the target U2N Relay UE. In case the U2N Relay UE is in RRC_IDLE/INACTIVE state when receiving the RRCReconfigurationComplete message, the reception of the RRCReconfigurationComplete message will first trigger RRC setup/resume procedure for the U2N relay UE to enter RRC_CONNECTED state. 10. The gNB-DU sends the UL RRC MESSAGE TRANSFER message to gNB-CU by including the RRCReconfigurationComplete message. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 8.19.4.2 |
5,099 | 5.4.2.3 Authentication response by the UE | The UE shall respond to an AUTHENTICATION REQUEST message. With the exception of the cases described in clauses 5.4.2.6 and 5.4.2.7 case k, the UE shall process the authentication challenge data and respond with an AUTHENTICATION RESPONSE message to the network. Upon a successful EPS authentication challenge, the UE shall determine the PLMN identity to be used for the calculation of the new KASME from the authentication challenge data according to the following rules: a) When the UE moves from EMM-IDLE mode to EMM-CONNECTED mode, until the first handover, the UE shall use the PLMN identity of the selected PLMN; and b) After handover or inter-system handover to S1 mode, - if the target cell is not a shared network cell, the UE shall use the PLMN identity received as part of the broadcast system information; - if the target cell is a shared network cell and the UE has a valid GUTI, the UE shall use the PLMN identity that is part of the GUTI; and - if the target cell is a shared network cell, the UE does not have a valid GUTI and, - the EPS authentication challenge is performed after inter-system handover from A/Gb mode to S1 mode or from Iu mode to S1 mode and the UE has a valid P-TMSI and RAI, the UE shall use the PLMN identity that is part of the RAI; or - the EPS authentication challenge is performed after inter-system handover from N1 mode to S1 mode and the UE has a valid 5G-GUTI, the UE shall use the PLMN identity that is part of the 5G-GUTI. Upon a successful EPS authentication challenge, the new KASME calculated from the authentication challenge data shall be stored in a new EPS security context in the volatile memory of the ME. The USIM will compute the authentication response (RES) using the authentication challenge data received from the ME, and pass RES to the ME. In order to avoid a synchronisation failure, when the UE receives an AUTHENTICATION REQUEST message, the UE shall store the received RAND together with the RES returned from the USIM in the volatile memory of the ME. When the UE receives a subsequent AUTHENTICATION REQUEST message, if the stored RAND value is equal to the new received value in the AUTHENTICATION REQUEST message, then the ME shall not pass the RAND to the USIM, but shall send the AUTHENTICATION RESPONSE message with the stored RES. If there is no valid stored RAND in the ME or the stored RAND is different from the new received value in the AUTHENTICATION REQUEST message, the ME shall pass the RAND to the USIM, shall override any previously stored RAND and RES with the new ones and start, or reset and restart timer T3416. The RAND and RES values stored in the ME shall be deleted and timer T3416, if running, shall be stopped: - upon receipt of a - SECURITY MODE COMMAND, - SERVICE REJECT, - SERVICE ACCEPT, - TRACKING AREA UPDATE REJECT, - TRACKING AREA UPDATE ACCEPT, or - AUTHENTICATION REJECT message; - upon expiry of timer T3416; - if the UE enters the EMM state EMM-DEREGISTERED or EMM-NULL; or - if the UE enters EMM-IDLE mode. | 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.3 |
5,100 | 5.1.3.2.1.3.8 5GMM-DEREGISTERED.eCALL-INACTIVE | The substate 5GMM-DEREGISTERED.eCALL-INACTIVE is chosen in the UE when: a) the UE is configured for eCall only mode as specified in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [22]; b) timer T3444 and timer T3445 have expired or are not running; c) a PLMN has been selected as specified in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]; d) the UE does not need to perform an eCall over IMS; and e) the UE does not need to perform a call to a non-emergency MSISDN or URI for test or terminal reconfiguration service. In this substate, the UE shall not initiate any signalling towards the network, except to originate an eCall over IMS, or a call to a non-emergency MSISDN or URI for test or terminal reconfiguration service. This substate is not applicable to non-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 | 5.1.3.2.1.3.8 |
Subsets and Splits
No saved queries yet
Save your SQL queries to embed, download, and access them later. Queries will appear here once saved.