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
β |
|---|---|---|---|---|---|---|---|
2,901 | β MeasGapSharingConfig | The IE MeasGapSharingConfig specifies the measurement gap sharing scheme and controls setup/ release of measurement gap sharing. MeasGapSharingConfig information element -- ASN1START -- TAG-MEASGAPSHARINGCONFIG-START MeasGapSharingConfig ::= SEQUENCE { gapSharingFR2 SetupRelease { MeasGapSharingScheme } OPTIONAL, -- Need M ..., [[ gapSharingFR1 SetupRelease { MeasGapSharingScheme } OPTIONAL, --Need M gapSharingUE SetupRelease { MeasGapSharingScheme } OPTIONAL --Need M ]] } MeasGapSharingScheme::= ENUMERATED {scheme00, scheme01, scheme10, scheme11} -- TAG-MEASGAPSHARINGCONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | β |
2,902 | 5.16.3 IMS support 5.16.3.1 General | IP-Connectivity Access Network specific concepts when using 5GS to access IMS can be found in TS 23.228[ IP Multimedia Subsystem (IMS); Stage 2 ] [15]. 5GS supports IMS with the following functionality: - Indication toward the UE if IMS voice over PS session is supported. - Capability to transport the P-CSCF address(es) to UE. - Paging Policy Differentiation for IMS as defined in TS 23.228[ IP Multimedia Subsystem (IMS); Stage 2 ] [15]. - IMS emergency service as defined in TS 23.167[ IP Multimedia Subsystem (IMS) emergency sessions ] [18]. - Domain selection for UE originating sessions. - Terminating domain selection for IMS voice. - Support of P-CSCF restoration procedure (clause 5.16.3.9). - NRF based P-CSCF discovery (clause 5.16.3.11). NOTE: The NRF based P-CSCF discovery has no impact on the UE, i.e. the UE does not need to know how P-CSCF IP address(es) is discovered in the network. - NRF based HSS discovery (clause 5.16.3.12). | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.16.3 |
2,903 | A.3 Causes related to PLMN specific network failures and congestion/authentication failures | Cause #16 β MSC temporarily not reachable This EMM cause is sent to the UE if it requests a combined EPS attach or tracking area updating in a PLMN where the MSC is temporarily not reachable via the EPS part of the network. Cause #17 β Network failure This EMM cause is sent to the UE if the MME cannot service an UE generated request because of PLMN failures. Cause #18 β CS domain not available This EMM cause is sent to the UE if the MME cannot service an UE generated request because CS domain is not available and SMS in MME is not supported. Cause #19 β ESM failure This EMM cause is sent to the UE when there is a failure in the ESM message contained in the EMM message. Cause #20 β MAC failure This EMM cause is sent to the network if the USIM detects that the MAC in the AUTHENTICATION REQUEST message is not fresh (see 3GPP TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [19]). Cause #21 β Synch failure This EMM cause is sent to the network if the USIM detects that the SQN in the AUTHENTICATION REQUEST message is out of range (see 3GPP TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [19]). Cause #22 β Congestion This EMM cause is sent to the UE because of congestion in the network (e.g. no channel, facility busy/congested etc.). Cause #23 β UE security capabilities mismatch This EMM cause is sent to the network if the UE detects that the UE security capability does not match the one sent back by the network. Cause #24 β Security mode rejected, unspecified This EMM cause is sent to the network if the security mode command is rejected by the UE if the UE detects that the nonceUE does not match the one sent back by the network or for unspecified reasons. Cause #26 β Non-EPS authentication unacceptable This EMM cause is sent to the network in S1 mode if the "separation bit" in the AMF field of AUTN is set to 0 in the AUTHENTICATION REQUEST message (see 3GPP TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [19]). Cause #39 β CS service temporarily not available This EMM cause is sent to the UE when the CS fallback or 1xCS fallback request cannot be served temporarily due to O&M reasons or a mobile terminating CS fallback call is aborted by the network during call establishment (see 3GPP TS 29.118[ Mobility Management Entity (MME) - Visitor Location Register (VLR) SGs interface specification ] []). Cause #42 β Severe network failure This EMM cause is sent to the UE when the network has determined that the requested procedure cannot be completed successfully due to network failure. The failure is not expected to be temporary and repeated request is not likely to succeed in near future. Cause #78 βPLMN not allowed to operate at the present UE location This EMM cause is sent to the UE to indicate that the PLMN is not allowed to operate at the present UE location. NOTE: This cause is only used by the network towards UE in NB-S1 mode or WB-S1 mode accessing the network through a satellite E-UTRA cell. | 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 | A.3 |
2,904 | β SIB18 | SIB18 contains Group IDs for Network selection (GINs) to support access using credentials from a Credentials Holder or to support UE onboarding. SIB18 information element -- ASN1START -- TAG-SIB18-START SIB18-r17 ::= SEQUENCE { gin-ElementList-r17 SEQUENCE (SIZE (1..maxGIN-r17)) OF GIN-Element-r17 OPTIONAL, -- Need R gins-PerSNPN-List-r17 SEQUENCE (SIZE (1..maxNPN-r16)) OF GINs-PerSNPN-r17 OPTIONAL, -- Need S lateNonCriticalExtension OCTET STRING OPTIONAL, ... } GIN-Element-r17 ::= SEQUENCE { plmn-Identity-r17 PLMN-Identity, nid-List-r17 SEQUENCE (SIZE (1..maxGIN-r17)) OF NID-r16 } GINs-PerSNPN-r17 ::= SEQUENCE { supportedGINs-r17 BIT STRING (SIZE (1..maxGIN-r17)) OPTIONAL -- Need R } -- TAG-SIB18-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | β |
2,905 | 5.15.1.2.2 Sidelink process | The Sidelink process is associated with a HARQ buffer. The Sidelink process shall maintain a state variable CURRENT_TX_NB, which indicates the number of transmissions that have taken place for the MAC PDU currently in the buffer. When the Sidelink process is established, CURRENT_TX_NB shall be initialized to 0. The sequence of redundancy versions is 0, 2, 3, 1. The variable CURRENT_IRV is an index into the sequence of redundancy versions. This variable is up-dated modulo 4. The Sidelink process is configured with a maximum number of HARQ retransmissions by RRC: numRetx. If the Sidelink HARQ Entity requests a new transmission, the Sidelink process shall: - set CURRENT_TX_NB to 0; - set CURRENT_IRV to 0; - store the MAC PDU in the associated HARQ buffer; - store the grant received from the Sidelink HARQ Entity; - generate a transmission as described below. If the Sidelink HARQ Entity requests a retransmission, the Sidelink process shall: - increment CURRENT_TX_NB by 1; - generate a transmission as described below. To generate a transmission, the Sidelink process shall: - if there is no uplink transmission, no transmission or reception on PSCCH, and no transmission or reception on PSSCH at the time of the transmission; or - if there is a Sidelink Discovery Gap for Transmission at the time of transmission and if there is a MAC PDU to be transmitted in this TTI in uplink, which is not obtained from the Msg3 buffer: - instruct the physical layer to generate a transmission according to the grant with the redundancy version corresponding to the CURRENT_IRV value. - increment CURRENT_IRV by 1. After performing above actions, the Sidelink process then shall: - if CURRENT_TX_NB = numRetx: - flush the HARQ buffer. | 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.15.1.2.2 |
2,906 | 5.5.3 eCall inactivity procedure | The eCall inactivity procedure is performed only in 3GPP access and applicable only to a UE configured for eCall only mode as specified in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [22]. The procedure shall be started when: a) the UE is in any 5GMM-REGISTERED substate except substates 5GMM-REGISTERED.PLMN-SEARCH or 5GMM-REGISTERED.NO-CELL-AVAILABLE; b) the UE is in 5GMM-IDLE mode or 5GMM-CONNECTED mode with RRC inactive indication; and c) one of the following conditions applies: 1) timer T3444 expires or is found to have already expired and timer T3445 is not running; 2) timer T3445 expires or is found to have already expired and timer T3444 is not running; or 3) timers T3444 and T3445 expire or are found to have already expired. The UE shall then perform the following actions: a) stop other running timers (e.g. T3511, T3512); b) if the UE is currently registered to the network for 5GS services, perform a de-registration procedure; c) delete any 5G-GUTI, TAI list, last visited registered TAI, list of equivalent PLMNs, and ngKSI; and d) enter 5GMM-DEREGISTERED.eCALL-INACTIVE state. | 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.3 |
2,907 | 4.7.1.9 Release of the PS signalling connection (Iu mode only) | In Iu mode, to allow the network to release the PS signalling connection (see 3GPP TS 25.331[ None ] [23c] and 3GPP TS 44.118[ None ] [111]) the MS: a) shall start the timer T3340 if the MS receives any of the reject cause values #11, #12, #13, #15 or #25; b) shall start the timer T3340 if the network indicates "no follow-on proceed" in the ROUTING AREA UPDATE ACCEPT or ATTACH ACCEPT message and user plane radio access bearers have not been setup; c) shall start the timer T3340 if the MS receives a DETACH ACCEPT message and the MS has set the detach type to "IMSI detach" in the DETACH REQUEST message and user plane radio access bearers have not been set up; or d) may start the timer T3340 if the MS receives any of the reject cause values #3, #6, #7 or #8 or if it receives an AUTHENTICATION AND CIPHERING REJECT message. Upon expiry of T3340, the MS shall release the established PS signalling connection (see 3GPP TS 25.331[ None ] [23c] and 3GPP TS 44.118[ None ] [111]). Upon release of the established PS signalling connection, if timer T3243 is not running, the MS shall start timer T3243 when: - the MS is an eCall only MS (as determined by information configured in USIM); - the MS is capable of eCall over IMS; and - the PS signalling connection that was released had been established for a call to an HPLMN designated non-emergency MSISDN or URI for test or terminal reconfiguration service which was handed over from S1 mode. In case b, if the MS has signalling pending, then it shall request a new PS signalling connection for further signalling. In case b and c, - upon an indication from the lower layers that radio accesss bearer(s) is set up, the MS shall stop timer T3340 and may send uplink signalling via the existing PS signalling connection or user data via radio access bearer(s). If the MS is establishing a PDN connection for emergency bearer services or the MS is initiating a service request procedure to send user data for emergency bearer services, the MS shall send the uplink signalling via the existing PS signalling connection; - upon receipt of a REQUEST PDP CONTEXT ACTIVATION message, MODIFY PDP CONTEXT REQUEST message, DEACTIVATE PDP CONTEXT REQUEST message, REQUEST SECONDARY PDP CONTEXT ACTIVATION message or REQUEST MBMS CONTEXT ACTIVATION message, the MS shall stop timer T3340 and may send uplink signalling via the existing PS signalling connection. If the MS is establishing a PDN connection for emergency bearer services or the MS is initiating a service request procedure to send user data for emergency bearer services, the MS shall send the uplink signalling via the existing PS signalling connection; or - upon receipt of a DETACH REQUEST message, the MS shall stop timer T3340 and respond to the network initiated GPRS detach as specified in subclause 4.7.4.2. If the MS receives the "Extended wait time" for PS domain from the lower layers when no attach, routing area updating or service request procedure is ongoing, the MS shall ignore the "Extended wait time". If the MS needs to perform PLMN selection, the MS may release the established PS signalling connection (see 3GPP TS 25.331[ None ] [23c] and 3GPP TS 44.118[ None ] [111]). | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.7.1.9 |
2,908 | 4.2.3.2 UE Triggered Service Request | The UE in CM-IDLE state initiates the Service Request procedure in order to send uplink signalling messages, user data, to request emergency services fallback, or as a response to a network paging request. The UE shall not initiate UE Triggered Service Request from CM-IDLE if there is a Service Gap timer running. After receiving the Service Request message, the AMF may perform authentication. After the establishment of the signalling connection to an AMF, the UE or network may send signalling messages, e.g. PDU Session establishment from UE to the SMF, via the AMF. The Service Request procedure is used by a UE in CM-CONNECTED to request activation of a User Plane connection for PDU Sessions and to respond to a NAS Notification message from the AMF. When a User Plane connection for a PDU Session is activated, the AS layer in the UE indicates it to the NAS layer. The Service Request procedure is used by the Multi-USIM UE over 3GPP access, in: a) CM-CONNECTED state to request release of the UE connection, stop data transmission, discard of any pending data and optionally, store Paging Restriction Information; or b) CM-IDLE state to request removal of Paging Restriction Information. The Multi-USIM UE shall not execute UE triggered Service Request procedure with Release Request indication if regulatory prioritized services (e.g. emergency service, emergency callback waiting) are ongoing. After an emergency call, the UE shall not execute a UE triggered Service Request procedure with Release Request indication for a duration which is sufficient for emergency call back. c) CM-IDLE state to respond to paging with a Reject Paging Indication that indicates that N1 connection shall be released and no user plane connection shall be established. The UE optionally provides the Paging Restriction Information. The UE may be unable to respond to paging with a Reject Paging Indication, e.g. due to UE implementation constraints. NOTE 1: A Multi-USIM UE in RRC_INACTIVE/CM-CONNECTED state that decides to reject the RAN paging, requests the release of the UE connection as in bullet a) above. The UE can discard, by implementation, any data or NAS PDUs that it receives before it is released. For any Service Request, the AMF responds with a Service Accept message to synchronize PDU Session status between UE and network, if necessary. The AMF responds with a Service Reject message to UE, if the Service Request cannot be accepted by network. The AMF may steer the UE from 5GC by rejecting the Service Request. The AMF should take into account the Preferred and Supported Network Behaviour (see clause 5.31.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]) and availability of EPC to the UE before steering the UE from 5GC. The Service Reject message may include an indication or cause code requesting the UE to perform Registration procedure. For this procedure, the impacted SMF and UPF, if any, are all under control of the PLMN serving the UE, e.g. in Home Routed roaming case the SMF and UPF in HPLMN are not involved if V-SMF relocation is not triggered. For Service Request due to user data, network may take further actions if User Plane connection activation is not successful. The procedure in this clause 4.2.3.2 is applicable to the scenarios with or without intermediate UPF and with or without intermediate UPF reselection. If the UE initiates Service Request procedures via non-3GPP Access, functions defined in clause 4.12.4.1 are applied. The User Plane of all PDU Sessions with redundant I-UPFs or with redundant N3/N9 tunnels for URLLC shall be activated during the Service Request procedure if the UE in CM-IDLE state initiates the Service Request procedure from 3GPP access. If the redundant I-UPFs are to be added/replaced/removed, the N4 Session procedure to manage the I-UPF is done for each I-UPF in steps 6c, 6d,7a, 7b, 8a, 8b, 9, 10, 17a,17b, 20a, 20b, 21a,21b, 22a and 22b of the figure 4.2.3.2-1. If the redundant N3/N9 tunnels are used for URLLC and the I-UPF is to be added/replaced/removed, the N4 Session procedure to update the tunnel is done for each N3/N9 tunnel in steps 6c, 6d, 7a, 7b, 8a, 8b, 9, 10, 17a, 17b. 20a, 20b, 21a and 21b of the figure 4.2.3.2-1. Figure 4.2.3.2-1: UE Triggered Service Request procedure 1. UE to (R)AN: AN message (AN parameters, Service Request (List Of PDU Sessions To Be Activated, List Of Allowed PDU Sessions, security parameters, PDU Session status, 5G-S-TMSI, [NAS message container], Exempt Indication, [Release Request indication], [Paging Restriction Information], [Reject Paging Indication])). The NAS message container shall be included if the UE is sending a Service Request message as an Initial NAS message and the UE needs to send non-cleartext IEs, see clause 4.4.6 of TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [25]. The Multi-USIM UE in CM-CONNECTED state may include the Release Request indication and optionally Paging Restriction Information in the Service Request message over 3GPP access, if the UE intends to leave CM-CONNECTED state. The Multi-USIM UE in CM-IDLE state may include the Release Request indication and not include Paging Restriction Information in the Service Request message over 3GPP access, if the UE intends to delete the Paging Restriction Information. If the Multi-USIM UE in CM-IDLE state decides not to accept the paging, it may send a Service Request message including a Reject Paging Indication and optionally Paging Restriction Information, unless it is not able to send this message e.g. due to UE implementation constraints. The List Of PDU Sessions To Be Activated is provided by UE when the UE wants to re-activate the PDU Session(s). The List Of Allowed PDU Sessions is provided by the UE when the Service Request is a response of a Paging or a NAS Notification for a PDU Session associated with non-3GPP access and identifies the PDU Sessions that can be transferred to 3GPP access. In the case of NG-RAN: - The AN parameters include 5G-S-TMSI, Selected PLMN ID (or PLMN ID and NID, see clause 5.30 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]), Establishment cause and may also include NSSAI information. The Establishment cause provides the reason for requesting the establishment of an RRC connection. Whether and how the UE includes the NSSAI information as part of the AN parameters is dependent on the value of the Access Stratum Connection Establishment NSSAI Inclusion Mode parameter, as specified in clause 5.15.9 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. - The UE sends Service Request message towards the AMF encapsulated in an RRC message to the NG-RAN. The RRC message(s) that can be used to carry the 5G-S-TMSI and this NAS message are described in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [12] and TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [16]. If the Service Request is triggered by the UE for user data, the UE identifies, using the List Of PDU Sessions To Be Activated, the PDU Session(s) for which the UP connections are to be activated in Service Request message. When the UE includes the List Of PDU Sessions To Be Activated, the UE shall indicate PDU Sessions only associated with the access the Service Request is related to. If the Service Request is triggered by the UE for signalling only, the UE doesn't identify any List Of PDU Sessions To Be Activated. If this procedure is triggered for paging response and the UE has at the same time some user data to be transferred, the UE identifies the PDU Session(s) whose UP connections are to be activated in Service Request message, by the List Of PDU Sessions To Be Activated. Otherwise the UE does not identify any PDU Session(s) in the Service Request message for paging response. As defined in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [25] the UE shall include always-on PDU Sessions which are accepted by the network in the List Of PDU Sessions To Be Activated even if there are no pending uplink data for those PDU Sessions or when the Service Request is triggered for signalling only or when the Service Request is triggered for paging response. If the Service Request over 3GPP access is triggered in response to the paging or NAS Notification indicating non-3GPP access, the Service Request message shall identify the list of PDU Sessions associated with the non-3GPP access that can be re-activated over 3GPP access in the List Of Allowed PDU Sessions, as described in clause 4.2.3.3 (step 6) of this specification and in clause 5.6.8 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. When the UE over 3GPP access is in NB-N1 mode and the resulting number of PDU Sessions with user plane resources activated for the UE does not exceed the maximum number of supported user plane resources (0, 1 or 2), based on whether the UE supports UP data transfer and the UE's 5GMM Core Network Capability as described in clause 5.31.19 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], the AMF shall notify the SMF that reactivation of the user-plane resources for the corresponding PDU session(s) associated with non-3GPP access can be performed as defined in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [25]. If the Service Request is triggered to report PS Data Off status change and the UE is in Non-Allowed Area, the UE shall send Service Request message with an indication that the message is exempted from restriction (e.g. Non-Allowed Area). In this case, if the UE is in Non-Allowed Area, the UE shall not include the List Of PDU Sessions To Be Activated and as a result the always-on PDU Session is not re-activated during the Service Request procedure. The PDU Session status indicates the PDU Sessions available in the UE. The UE shall not trigger a Service Request procedure for a PDU Session corresponding to a LADN when the UE is outside the area of availability of the LADN. NOTE 2: A PDU Session corresponding to a LADN is not included in the List Of PDU Sessions To Be Activated when the UE is outside the area of availability of the LADN. For UE in CM-CONNECTED state, only the List Of PDU Sessions To Be Activated and List Of Allowed PDU Sessions need to be included in the Service Request. The UE shall not trigger a Service Request procedure for a PDU Session associated to an S-NSSAI if the S-NSSAI is not valid as per the S-NSSAI location availability information. NOTE 3: A PDU Session associated to an S-NSSAI is not included in the List Of PDU Sessions To Be Activated when the S-NSSAI is not valid as per the S-NSSAI location availability information. 2. (R)AN to AMF: N2 Message (N2 parameters, Service Request). Details of this step are described in TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [10]. If the AMF can't handle the Service Request it will reject it. When NG-RAN is used, the N2 parameters include the 5G-S-TMSI, Selected PLMN ID (or PLMN ID and NID, see clause 5.30 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]), Location information and Establishment cause, UE Context Request. If the UE is in CM-IDLE state, the NG-RAN obtains the 5G-S-TMSI in RRC procedure. NG-RAN selects the AMF according to 5G-S-TMSI. The Location Information relates to the cell in which the UE is camping. Based on the PDU Session status, the AMF may initiate PDU Session Release procedure in the network for the PDU Sessions whose PDU Session ID(s) were indicated by the UE as not available. When the Establishment cause is associated with priority services (e.g. MPS, MCX), or when the AMF determines that the UE has priority subscription (e.g. MPS, MCX) in the UDM, the AMF includes a Message Priority header to indicate priority information. Other NFs relay the priority information by including the Message Priority header in service-based interfaces, as specified in TS 29.500[ 5G System; Technical Realization of Service Based Architecture; Stage 3 ] [17]. The AMF enforces the Mobility Restrictions as specified in clause 5.3.4.1.1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If there is a Service Gap timer running in AMF for the UE and the AMF is not waiting for a MT paging response from the UE and the Service Request is not for regulatory prioritized services like Emergency services or not for exception reporting, the AMF rejects the Service Request with an appropriate cause. In addition, AMF may also provide a UE with a Mobility Management Back-off timer set to the remaining value of the Service Gap timer. If the AMF supports RACS and the AMF detects that the selected PLMN is different from the currently registered PLMN for the UE, the AMF determines the UE Radio Capability ID of the newly selected PLMN to the gNB as described in clause 5.4.4.1a of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. For NR satellite access, the AMF may decide to verify the UE location and determine whether the PLMN is allowed to operate at the UE location, as described in clause 5.4.11.4 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If the UE receives a Service Reject message with cause value indicating that the PLMN is not allowed to operate in the present UE location, the UE shall attempt to select a PLMN, as specified in TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [22]. 3a) AMF to (R)AN: N2 Request (security context, Mobility Restriction List, list of recommended cells / TAs / NG-RAN node identifiers). If the 5G-AN had requested for UE Context or there is a requirement for AMF to provide this e.g. the AMF needs to initiate fallback procedure as in clause 4.13.4.2 for Emergency services, AMF initiates NGAP procedure as specified in TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [10]. For UE in CM-IDLE state, 5G-AN stores the Security Context in the UE AN context. Mobility Restriction List is described in clause 5.3.4.1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The 5G-AN uses the Security Context to protect the messages exchanged with the UE as described in TS 33.501[ Security architecture and procedures for 5G System ] [15]. If the NG-RAN node had provided the list of recommended cells / TAs / NG-RAN node identifiers during the AN Release procedure (see clause 4.2.6), the AMF shall include it in the N2 Request. The RAN may use this information to allocate the RAN Notification Area when the RAN decides to enable RRC_INACTIVE state for the UE. 3. If the Service Request was not sent integrity protected or integrity protection verification failed, the AMF shall reject the Service Request as stated in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [25]. If the UE in CM-IDLE state triggered the Service Request to establish a signalling connection only, after successful establishment of the signalling connection the UE and the network can exchange NAS signalling and steps 4 to 11 and 15 to 22 are skipped. If the UE in Non-Allowed Area triggered the Service Request with an indication that the message is exempted from restriction (e.g. Non-Allowed Area), the AMF should accept the Service Request. In this case, if the UE is in Non-Allowed Area, the AMF rejects user plane setup request from the SMF except for emergency services. If the procedure was triggered in response to paging or NAS notification indicating non-3GPP access and the AMF received N1 SM Container only from the SMF in step 3a of clause 4.2.3.3, the AMF sends the NAS signalling including the N1 SM Container to the UE in step 7 of clause 4.2.3.3 without updating the access associated to the PDU Session. If the Service Request message is received over 3GPP access without a Release Request indication or a Reject Paging Indication, the AMF shall delete any stored Paging Restriction Information for this UE and stop restricting paging accordingly. If the Service Request message over 3GPP access includes a Release Request indication or a Reject Paging Indication, then: - the AMF may accept or reject the received Paging Restriction Information requested by the UE based on operator policy. If the AMF rejects the Paging Restriction Information, the AMF removes any stored Paging Restriction Information from the UE context and discards the UE requested Paging Restriction Information. If the AMF accepts the Paging Restriction Information from the UE, the AMF stores the Paging Restriction Information from the UE in the UE context. - If no Paging Restriction Information is provided, no paging restrictions apply and the AMF removes any stored Paging Restriction Information from the UE context. - no User Plane resources are established and instead the AMF triggers the AN Release procedure as described in clause 4.2.6. NOTE 4: If AMF does not perform steps 5-7 before step 2 then some DL data might not be delivered to the UE. If the procedure was triggered in response to paging and the Service Request message includes a Reject Paging Indication, the AMF initiates the UCU procedure as described in step 7 of clause 4.2.3.3 before the triggering of the AN Release procedure. 4. [Conditional] AMF to SMF: Nsmf_PDUSession_UpdateSMContext Request (PDU Session ID(s), Operation Type, UE location information, Access Type, RAT Type, UE presence in LADN service area, Indication of Access Type can be changed, [MO Exception Data Counter], [Satellite backhaul category], [GEO Satellite ID]). The Nsmf_PDUSession_UpdateSMContext Request is invoked: - If the UE identifies List Of PDU Sessions To Be Activated in the Service Request message; - This procedure is triggered by the SMF but the PDU Session(s) identified by the UE correlates to other PDU Session ID(s) than the one triggering the procedure; or - If this procedure is triggered by the SMF in response to paging or NAS notification indicating 3GPP access or if this step onwards is invoked following step 4a of clause 4.2.3.3 and the current UE location is outside the "Area of validity for the N2 SM information" provided by the SMF in step 3a of clause 4.2.3.3 or the "Area of validity for the N2 SM information" was not provided by the SMF in step 3a of clause 4.2.3.3, the AMF shall not send the N2 information provided by the SMF in step 3a of clause 4.2.3.3. Otherwise, if the current UE location is in the "Area of validity for the N2 SM information", steps 4 to 11 are skipped; or - If this procedure is triggered by the SMF in response to paging or NAS notification indicating non-3GPP access and the AMF received N2 SM Information only, or both N1 SM Container and N2 SM Information in step 3a of clause 4.2.3.3. If the DNN corresponds to an LADN then the "UE presence in LADN service area" indicates if the UE is IN or OUT of the LADN service area. If the AMF does not provide the "UE presence in LADN service area" indication and the SMF determines that the DNN corresponds to a LADN, then the SMF considers that the UE is OUT of the LADN service area. The AMF determines the PDU Session(s) for which the UP connection(s) shall be activated and sends an Nsmf_PDUSession_UpdateSMContext Request to SMF(s) associated with the PDU Session(s) with Operation Type set to "UP activate" to indicate establishment of User Plane resources for the PDU Session(s). The AMF determines Access Type and RAT Type, see clause 4.2.2.2.1. If the RAT type is NB-IoT, the AMF shall ensure that the number of PDU session(s) for which UP connection(s) are active does not exceed this UE's maximum number of supported user plane resources (0, 1 or 2) based on whether the UE supports UP data transfer and the UE 5GMM Core Network Capability as described in clause 5.31.19 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If the procedure was triggered in response to paging or NAS Notification indicating non-3GPP access, the AMF received N2 SM Information in step 3a of clause 4.2.3.3 and the PDU Session for which the UE was paged or notified is not in the List Of Allowed PDU Sessions provided by the UE, the AMF notifies the SMF that the UE is not reachable. For other PDU Sessions in the List Of Allowed PDU Sessions the Service Request Procedure succeeds without re-activating the User Plane of any PDU Sessions, unless they have also been included by the UE in the List Of PDU Sessions To Be Activated. If the procedure was triggered in response to paging or NAS notification indicating non-3GPP access and the PDU Session for which the UE was paged or notified is in the List Of Allowed PDU Sessions provided by the UE and the AMF received N2 SM Information only or N1 SM Container and N2 SM Information from the SMF in step 3a of clause 4.2.3.3, the AMF notifies the SMF that the access type of the PDU session can be changed. The AMF discards any already received N1 SM Container and N2 SM Information. In Home Routed roaming case, the V-SMF triggers Nsmf_PDUSession_Update service operation towards the H-SMF to notify the access type of the PDU Session can be changed and the procedure continues as specified in clause 4.3.3.3 from step 1a to step 10. If the UE is accessing via the NB-IoT RAT, the AMF may inform all (H-)SMFs whether the RRC establishment cause is set to "MO exception data", as described in clause 5.31.14.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The AMF may immediately send the MO Exception Data Counter to the (H-)SMF. If the AMF, based on configuration, as described in clauses 5.43.4 and 5.43.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], is aware that satellite backhaul category and/or GEO Satellite ID has changed and needs to be updated to the SMF, the AMF includes the new satellite backhaul category or new GEO Satellite ID or both as described in clauses 5.43.4 and 5.43.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The AMF may receive a Service Request to establish another NAS signalling connection via a new NG-RAN while it has maintained an old NAS signalling connection for UE still via an old NG-RAN. The new NG-RAN and the old NG-RAN can be the same NG-RAN node. In this case, AMF shall trigger the AN release procedure toward the old NG-RAN to release the old NAS signalling connection as defined in clause 4.2.6 and: - For the PDU Sessions indicated by the UE in the List Of PDU Sessions To Be Activated, the AMF requests the SMF to activate the PDU Session(s) immediately by performing this step 4; and NOTE 5: This activates the UP of PDU Session(s) using resources of the new NG-RAN. - For the PDU Sessions indicated by the old NG-RAN in the "List of PDU Session ID(s) with active N3 user plane" but not in the List Of PDU Sessions To Be Activated sent by the UE, the AMF requests the SMF to deactivate the PDU Session(s). NOTE 6: This deactivates the UP of PDU Session(s) that are no more needed by the UE. 5a. Void. 5b. If the PDU Session ID corresponds to a LADN and the SMF determines that the UE is outside the area of availability of the LADN based on the "UE presence in LADN service area" from the AMF, the SMF decides to (based on local policies) either: - keep the PDU Session, but reject the activation of User Plane connection for the PDU Session and inform the AMF about it. If the procedure has been triggered by a Network Triggered Service Request as described in clause 4.3.2.3, the SMF may notify the UPF that originated the Data Notification to discard downlink data for the PDU Sessions and/or to not provide further Data Notification messages; or - to release the PDU Session: the SMF releases the PDU Session and informs the AMF that the PDU Session is released. In any case of the two cases above the SMF answers to the AMF (step10) with an appropriate reject cause and the User Plane Activation of PDU Session is stopped. Otherwise, based on the location info received from the AMF, the SMF checks the UPF Selection Criteria according to clause 6.3.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] and determines to perform one of the following: - accepts the activation of UP connection and continue using the current UPF(s); - accepts the activation of UP connection and selects a new intermediate UPF (or add/remove an intermediate UPF), if the UE has moved out of the service area of the UPF that was previously connecting to the AN, while maintaining the UPF(s) acting as PDU Session Anchor. The steps to perform I-UPF addition/change/removal are described as conditional steps in the following of the current procedure; or NOTE 7: If the old and/or new I-UPF implements an UL CL or BP functionality and a PDU Session Anchor for connectivity to the local access to the Data Network as described in clause 5.6.4.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], the signalling described in the current clause is intended as the signalling to add, remove or change the PDU Session Anchor and must be complemented by the signalling to add, release or change the UL CL or BP as described respectively in clauses 4.3.5.4, 4.3.5.5 and 4.3.5.7. - rejects the activation of UP connection of a PDU Session of SSC mode 2 and trigger re-establishment of the PDU Session after Service Request procedure to perform the allocation of a new UPF to act as PDU Session Anchor, e.g. the UE has moved out of the service area of the anchor UPF which is connecting to NG-RAN. In the case that the SMF fails to find suitable I-UPF, the SMF decides to (based on local policies) either: - trigger re-establishment of PDU Session. After Service Request procedure, SMF sends N1 SM message to the UE via the AMF by invoking Namf_Communication_N1N2MessageTransfer containing the cause indicating PDU Session re-establishment is required for the UE; or - keep the PDU Session, but reject the activation request of User Plane connection for the PDU Session and inform the AMF about it; or - release the PDU Session after Service Request procedure. If the SMF has determined that the UE is performing Inter-RAT mobility to or from the NB-IoT RAT then the SMF uses the "PDU Session continuity at inter RAT mobility" to determine how to handle the PDU Session. 6a. [Conditional] SMF to UPF (PSA): N4 Session Modification Request. Depending on the network deployment, the CN Tunnel Info of UPF (PSA) allocated for N3 or N9 interface may be changed during the Service Request procedure, e.g. UPF connected to different IP domains. If different CN Tunnel Info need be used, the SMF sends N4 Session Modification Request message to UPF (PSA) and requests CN Tunnel Info providing the target Network Instance. 6b. [Conditional] UPF (PSA) to SMF: N4 Session Modification Response. The UPF (PSA) sends an N4 Session Establishment Response message to the SMF. The UPF provides CN Tunnel Info to the SMF. The UPF (PSA) associate the CN Tunnel Info with UL Packet detection rules provided by the SMF. If the redundant I-UPFs are used for URLLC, each I-UPF provides UL CN Tunnel Info for N3 interface to the SMF in the N4 Session Establishment Response message. If the redundant N3 tunnels are used for URLLC, the UPF (PSA) provides redundant UL CN Tunnel Info for N3 interface to the SMF in N4 Session Establishment Response message. 6c. [Conditional] SMF to new UPF (intermediate): N4 Session Establishment Request. If the SMF selects a new UPF to act as intermediate UPF for the PDU Session, or if the SMF selects to insert an intermediate UPF for a PDU Session which did not have an intermediate UPF, an N4 Session Establishment Request message is sent to the new UPF, providing Packet detection, Data forwarding, enforcement and reporting rules to be installed on the intermediate UPF. The CN Tunnel Info (on N9) of PSA, i.e. which is used to establish the N9 tunnel, for this PDU Session is also provided to the intermediate UPF. If a new UPF is selected by the SMF to replace the old (intermediate) UPF, the SMF may also include a request for the new UPF to allocate a second tunnel endpoint for buffered DL data from the old I-UPF and to indicate via usage reporting end marker reception on this second tunnel. In this case, the UPF is instructed by the SMF to buffer the DL data it may receive at the same time from the UPF (PSA). 6d. New UPF (intermediate) to SMF: N4 Session Establishment Response. The new intermediate UPF sends an N4 Session Establishment Response message to the SMF. The UPF provides DL CN Tunnel Info as requested by SMF in step 6c. The SMF starts a timer, to be used in step 22a to release the resource in old intermediate UPF if there is one. 7a. [Conditional] SMF to UPF (PSA): N4 Session Modification Request. If the SMF selects a new UPF to act as intermediate UPF for the PDU Session, the SMF sends N4 Session Modification Request message to PDU Session Anchor UPF, providing DL Tunnel Info from new intermediate UPF. If the new intermediate UPF was added for the PDU Session, the UPF (PSA) begins to send the DL data to the new I-UPF as indicated in the DL CN Tunnel Info. The UPF (PSA) sends one or more "end marker" packets for each N9 tunnel to the old I-UPF immediately after switching the path to new I-UPF. If the Service Request is triggered by the network and the SMF removes the old I-UPF but does not replace it with a new I-UPF, the SMF may also include a request for the UPF to allocate a second tunnel endpoint for buffered DL data from the old I-UPF and to indicate end marker reception on this second tunnel via usage reporting. In this case, the UPF (PSA) begins to buffer the DL data it may receive at the same time from the N6 interface. The UPF (PSA) sends one or more "end marker" packets for each N9 tunnel to the old I-UPF immediately after switching the path to (R)AN. 7b. The UPF (PSA) sends N4 Session Modification Response message to SMF. If requested by SMF, the UPF (PSA) sends DL CN tunnel info for the old (intermediate) UPF to the SMF. The SMF starts a timer, to be used in step 22a to release the resource in old intermediate UPF if there is one. If the UPF that connects to RAN is the UPF (PSA) and if the SMF finds that the PDU Session is activated when receiving the Nsmf_PDUSession_UpdateSMContext Request in step 4 with Operation Type set to "UP activate" to indicate establishment of User Plane resources for the PDU Session(s), it deletes the AN Tunnel Info and initiates an N4 Session Modification procedure to remove Tunnel Info of AN in the UPF. 8a. [Conditional] SMF to old UPF (intermediate): N4 Session Modification Request (New UPF address, New UPF DL Tunnel ID) If the service request is triggered by the network and the SMF removes the old (intermediate) UPF, the SMF sends the N4 Session Modification Request message to the old (intermediate) UPF, providing the DL Tunnel Info for the buffered DL data. If the SMF allocated new I-UPF, the DL Tunnel Info is from the new (intermediate) UPF acting as N3 terminating point. If the SMF did not allocate a new I-UPF, the DL Tunnel Info is from the new UPF (PSA) acting as N3 terminating point. The SMF starts a timer to monitor the forwarding tunnel as step 6d or 7b. If the old I-UPF receives end marker packets and there is no associated tunnel to forward these packets, the old I-UPF discards the received end marker packets and does not send any Data Notification to SMF. If the SMF find the PDU Session is activated when receiving the Nsmf_PDUSession_UpdateSMContext Request in step 4 with Operation Type set to "UP activate" to indicate establishment of User Plane resources for the PDU Session(s), it deletes the AN Tunnel Info and initiates an N4 Session Modification procedure to remove Tunnel Info of AN in the UPF. 8b. old UPF (intermediate) to SMF: N4 Session Modification Response The old (intermediate) UPF sends N4 Session Modification Response message to SMF. 9. [Conditional] old UPF (intermediate) to new UPF (intermediate): buffered downlink data forwarding If the I-UPF is changed and forwarding tunnel was established to the new I-UPF, the old (intermediate) UPF forwards its buffered data to the new (intermediate) UPF acting as N3 terminating point. If indicated by SMF in step 6c, the new I-UPF reports to SMF when end marker packet is received. Then the SMF initiates N4 Session Modification procedure to indicate the new I-UPF to send the buffered downlink packet(s) received from the UPF (PSA). 10. [Conditional] old UPF (intermediate) to UPF (PSA): buffered downlink data forwarding If the old I-UPF is removed and no new I-UPF is assigned for the PDU Session and forwarding tunnel was established to the UPF (PSA), the old (intermediate) UPF forwards its buffered data to the UPF (PSA) acting as N3 Terminating Point. If indicated by SMF in step 7a, the UPF (PSA) reports to SMF when the end marker packet has been received. Then the SMF initiates N4 Session Modification procedure to request the UPF (PSA) to send the buffered DL data received from the N6 interface. 11. [Conditional] SMF to AMF: Nsmf_PDUSession_UpdateSMContext Response (N2 SM information (PDU Session ID, QFI(s), QoS profile(s), CN N3 Tunnel Info, S-NSSAI, User Plane Security Enforcement, UE Integrity Protection Maximum Data Rate, RSN, PDU Session Pair ID), N1 SM Container, Cause) to the AMF. If the UPF that connects to RAN is the UPF (PSA), the N3 CN Tunnel Info is the UL CN Tunnel Info of the UPF (PSA). If the UPF that connects to RAN is the new intermediate UPF, the CN N3 Tunnel Info is the UL Tunnel Info of the intermediate UPF. For the PDU Session with redundant I-UPFs or with redundant N3 tunnels for URLLC, the two UL N3 CN Tunnel Info are included, the SMF also indicates the NG-RAN that one of the CN Tunnel Info is used as the redundancy tunnel of the PDU session as described in clause 5.33.2.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The SMF shall send N1 SM Container and/or N2 SM Information to the AMF when applicable. (e.g. when the SMF was notified from the AMF that the access type of the PDU Session can be changed in step 4). For a PDU Session that the SMF has determined to accept the activation of UP connection in step 5a or 5b, the SMF generates only N2 SM information and sends Nsmf_PDUSession_UpdateSMContext Response to the AMF to establish the User Plane(s). The N2 SM information contains information that the AMF shall provide to the NG-RAN. The SMF may indicate for each QoS Flow whether redundant transmission shall be performed by a corresponding redundant transmission indicator. If the SMF decided to change the PSA UPF for the SSC mode 3 PDU Session, the SMF triggers the change of SSC mode 3 PDU Session anchor as an independent procedure described in clause 4.3.5.2 or clause 4.3.5.3 after accepting the activation of UP of the PDU Session. For each QoS Flow: - an ECN marking for L4S indicator to (R)AN in the case of ECN marking for L4S in RAN as described in clause 5.37.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]; or, - a QoS monitoring configuration for congestion information as described in clause 5.45.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], in the case of ECN marking for L4S by PSA UPF as described in clause 5.37.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] or QoS monitoring for congestion information as described in clause 5.45.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The SMF can reject the activation of UP of the PDU Session by including a cause in the Nsmf_PDUSession_UpdateSMContext Response. Following are some of the cases: - If the PDU Session corresponds to a LADN and the UE is outside the area of availability of the LADN as described in step 5b; - If the AMF notified the SMF that the UE is reachable only for regulatory prioritized service and the PDU Session to be activated is not for a regulatory prioritized service; or - If the SMF decided to change the PSA UPF for the requested PDU Session as described in step 5b. In this case, after sending Nsmf_PDUSession_UpdateSMContext Response, the SMF triggers another procedure to instruct UE to re-establish the PDU Session as described in clause 4.3.5.1 for SSC mode 2. - If the SMF received negative response in Step 6b due to UPF resource unavailability. If the PDU Session has been assigned any EPS bearer ID, the SMF also includes the mapping between EPS bearer ID(s) and QFI(s) into the N2 SM information to be sent to the NG-RAN. The User Plane Security Enforcement information is determined by the SMF upon PDU session establishment as described in clause 5.10.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If the User Plane Security Enforcement information indicates that Integrity Protection is "Preferred" or "Required", the SMF also includes the UE Integrity Protection Maximum Data Rate. The RSN and PDU Session Pair ID are included when applicable, as determined by the SMF during PDU Session establishment as described in clause 5.33.2.1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. 12. AMF to (R)AN: N2 Request (N2 SM information received from SMF, security context, Mobility Restriction List, UE-AMBR, List of UE-Slice-MBR(s) (optional and for 3GPP access type only), MM NAS Service Accept, list of recommended cells / TAs / NG-RAN node identifiers, UE Radio Capability, Core Network Assistance Information, Tracing Requirements, UE Radio Capability ID). The Allowed NSSAI for the Access Type for the UE and if available, Partially Allowed NSSAI (as described in clause 5.15.17 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]), are included in the N2 message. If the subscription information includes Tracing Requirements, the AMF includes Tracing Requirements in the N2 Request. If the UE triggered the Service Request while in CM-CONNECTED state, only N2 SM information received from SMF and MM NAS Service Accept are included in the N2 Request. If the Service Request procedure is triggered by the Network (as described in clause 4.2.3.3) while the UE is in CM-CONNECTED state, only N2 SM information received from SMF is included in the N2 Request. If the Service Request procedure is triggered by the Network (as described in clause 4.2.3.3) while the UE is in CM-IDLE state, only N2 SM information received from SMF and MM NAS Service Accept is included in the N2 Request. For a UE that was in CM-IDLE state when the Service Request was triggered, the NG-RAN stores the Security Context. If the Service Request is not triggered by UE for a signalling connection only, RAN also stores QoS Information for the QoS Flows of the PDU Sessions that are activated and N3 Tunnel IDs in the UE RAN context and Mobility Restriction List (as described in clause 5.3.4.1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]). MM NAS Service Accept includes PDU Session status in AMF. Any local PDU Session Release during the Session Request procedure is indicated to the UE via the Session Status. PDU Session Reactivation Result is provided in Service Accept for the PDU sessions in the List Of PDU Sessions To Be Activated and the PDU Session in the List of Allowed PDU Sessions which has caused paging or NAS notification. If the PDU Session Reactivation Result of a PDU Session is failure, the cause of the failure is also provided. If the AMF accepts the Paging Restriction Information sent from the UE, the AMF informs the UE about the acceptance/rejection of the requested Paging Restriction Information in the MM NAS Service Accept message. If AMF receives multiple TAIs from the NG-RAN in step 2 and determines that some, but not all of them are forbidden by subscription or by operator policy, the AMF shall include the forbidden TAI(s) in the MM NAS Service Accept message. If there are multiple PDU Sessions that involves multiple SMFs, AMF does not need to wait for responses from all SMFs in step 11 before it sends N2 SM information to the RAN. However, the AMF shall wait for all responses from the SMFs before it sends MM NAS Service Accept message to the UE. AMF shall include at least one N2 SM information from SMF if this step is triggered for PDU Session User Plane activation. AMF may send additional N2 SM information from SMFs in separate N2 message(s) (e.g. N2 tunnel setup request), if there is any. Alternatively, if multiple SMFs are involved, the AMF may send one N2 Request message to (R)AN after all the Nsmf_PDUSession_UpdateSMContext Response service operations from all the SMFs associated with the UE are received. If the NG-RAN node had provided the list of recommended cells / TAs / NG-RAN node identifiers during the AN Release procedure (see clause 4.2.6), the AMF shall include it in the N2 Request. The NG-RAN may use this information to allocate the RAN Notification Area when the NG-RAN decides to enable RRC_INACTIVE state for the UE. The AMF includes the UE's "RRC Inactive Assistance Information" as defined in clause 5.3.3.2.5 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If the NG-RAN node does not support RACS and the AMF have UE Radio Capability ID but not the UE Radio Capability information, then AMF will use Nucmf_UECapabilityManagement_Resolve to try to retrieve the corresponding UE Radio Capability information. If the NG-RAN node does not support RACS, or the AMF does not have UE Radio Capability ID in UE context, the AMF shall include the UE Radio Capability information, if available, to the NG-RAN node as described in TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If the RAT Type is NB-IoT then NB-IoT specific UE Radio Access Capability Information is included instead, if available. If AMF has UE Radio Capability ID in UE context valid for the PLMN the UE is currently in and the NG-RAN supports RACS, the AMF signals the UE Radio Capability ID. If the NG-RAN node does not have mapping between the UE Radio Capability ID and the corresponding UE radio capabilities, it shall use the non-UE associated procedure described in TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [10] to retrieve the mapping from the AMF. The AMF may include the Core Network Assistance Information which includes Core Network assisted RAN parameters tuning and Core Network assisted RAN paging information as defined in TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If the UE included support for restriction of use of Enhanced Coverage, the AMF sends Enhanced Coverage Restricted information to the (R)AN in the N2 message. If the UE and the AMF have negotiated to enable MICO mode and the AMF uses the Extended connected timer, then the AMF provides the Extended Connected time value to NG-RAN (see clause 5.31.7.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]) in this step. The Extended Connected Time value indicates the minimum time the RAN should keep the UE in RRC_CONNECTED state regardless of inactivity. If the AMF accepted MICO mode in the last registration procedure and knows there may be mobile terminated data or signalling pending, the AMF maintains the N2 connection for at least the Extended Connected Time as described in clause 5.31.7.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] and provides the Extended Connected Time value to the RAN in N2 message with Service Accept message. The RAN should keep the UE in RRC_CONNECTED state for an Extended Connected Time period in order to ensure the downlink data and/or signalling is delivered to the UE. If the RAN receives two CN Tunnel Info for a PDU session in step 11 for redundant transmission, RAN also allocates two AN Tunnel Info correspondingly and indicate to SMF one of the AN Tunnel Info is used as the redundancy tunnel of the PDU session as described in clause 5.33.2.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. 13. (R)AN to UE: The NG-RAN performs RRC Connection Reconfiguration with the UE depending on the QoS Information for all the QoS Flows of the PDU Sessions whose UP connections are activated and Data Radio Bearers. For a UE that was in CM-IDLE state, if the Service Request is not triggered by UE for a signalling connection only, the User Plane security is established at this step, which is described in detail in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [12] and TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [16]. For a UE that was in CM-IDLE state, if the Service Request is triggered by UE for a signalling connection only, AS security context may be established in this step, which is described in detail in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [12] and TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [16]. If the N2 Request includes a NAS message, the NG-RAN forwards the NAS message to the UE. The UE locally deletes context of PDU Sessions that are not available in 5GC. NOTE 8: The reception of the Service Accept message does not imply the successful activation of the User Plane radio resources. NOTE 9: If not all the requested User Plane AN resources are successfully activated, see TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [10]. After the User Plane radio resources are setup, the uplink data from the UE can now be forwarded to NG-RAN. The NG-RAN sends the uplink data to the UPF address and Tunnel ID provided in the step 11. If the NG-RAN can not establish redundant user plane for the PDU Session as indicated by the RSN parameter and PDU Session Pair ID, the NG-RAN takes the decision on how to proceed with the PDU Session as described in TS 23.501[ System architecture for the 5G System (5GS) ] [2]. 14. [Conditional] (R)AN to AMF: N2 Request Ack (List of PDU Sessions To Be Established with N2 SM information (AN Tunnel Info, List of accepted QoS Flows for the PDU Sessions whose UP connections are activated, List of rejected QoS Flows for the PDU Sessions whose UP connections are activated), established QoS Flows status (active/not active) for QoS monitoring configuration for congestion information, established QoS Flows status (active/not active) for ECN marking for L4S, List of PDU Sessions that failed to be established with the failure cause given in the N2 SM information element). The message may include N2 SM information(s), e.g. AN Tunnel Info. NG-RAN may respond N2 SM information with separate N2 message (e.g. N2 tunnel setup response) if AMF sends separate N2 message in step 11. If multiple N2 SM information are included in the N2 Request message in step 12, the N2 Request Ack includes multiple N2 SM information and information to enable the AMF to associate the responses to relevant SMF. 15. [Conditional] AMF to SMF: Nsmf_PDUSession_UpdateSMContext Request (N2 SM information, RAT Type, Access Type) per PDU Session to the SMF. The AMF determines Access Type and RAT Type, see clause 4.2.2.2.1. If the AMF received N2 SM information (one or multiple) in step 14, then the AMF shall forward the N2 SM information to the relevant SMF per PDU Session ID. If the UE Time Zone has changed compared to the last reported UE Time Zone then the AMF shall include the UE Time Zone IE in this message. If the PDU Session is moved from the non-3GPP access to 3GPP access (i.e. N3 tunnel for the PDU Session is established successfully), the SMF and AMF update associated access of the PDU Session. The UE updates associated access of the PDU Session when the user plane resource for the PDU Session is successfully established. Procedure for unpausing a charging pause initiated earlier is specified in clause 4.4.4. If a PDU Session is rejected by the serving NG-RAN with an indication that the PDU Session was rejected because User Plane Security Enforcement is not supported in the serving NG-RAN and the User Plane Enforcement Policy indicates "Required" as described in clause 5.10.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], the SMF shall trigger the release of this PDU Session. In all other cases of PDU Session rejection, the SMF can decide whether to release the PDU Session or to deactivate the UP connection of this PDU Session. If some of the QoS Flows of a PDU Session are not accepted by the serving NG-RAN, the SMF shall initiate the PDU Session Modification procedure to remove the non-accepted QoS Flows from the PDU Session after this procedure is completed. 16. [Optional] SMF to PCF: If dynamic PCC is deployed and if Policy Control Request Trigger condition(s) have been met (e.g. change of Access Type, change of UE location), performs SMF initiated SM Policy Modification procedure as defined in clause 4.16.5.1. The PCF may provide updated policies. 17a. [Conditional] SMF to new intermediate UPF: N4 Session Modification Request (AN Tunnel Info and List of accepted QFI(s)). If the SMF selected a new UPF to act as intermediate UPF for the PDU Session in step 5b, the SMF initiates a N4 Session Modification procedure to the new I-UPF and provides AN Tunnel Info. The Downlink Data from the new I-UPF can now be forwarded to NG-RAN and UE. 17b. [Conditional] UPF to SMF: N4 Session Modification Response. 18a. [Conditional] SMF to UPF (PSA): N4 Session Modification Request (AN Tunnel Info, List of rejected QoS Flows). If a User Plane is to be setup or modified and after the modification there is no I-UPF, the SMF initiates a N4 Session Modification procedure to UPF (PSA) and provides AN Tunnel Info. The Downlink Data from the UPF (PSA) can now be forwarded to NG-RAN and UE. For QoS Flows in the List of rejected QoS Flows, the SMF shall instruct the UPF to remove the rules (e.g. Packet Detection Rules etc.) which are associated with the QoS Flows. If SMF decides to perform redundant transmission for one or more QoS Flows of the PDU, the SMF also indicates the UPF (PSA) to perform packet duplication for the QoS Flow(s) in downlink direction by forwarding rules. If the PCC rule(s) are updated in step 16, the SMF may initiate a N4 Session Modification procedure to UPF (PSA) based on the updated PCC rule(s). 18b. [Conditional] UPF to SMF: N4 Session Modification Response. 19. [Conditional] SMF to AMF: Nsmf_PDUSession_UpdateSMContext Response. 20a. [Conditional] SMF to new UPF (intermediate): N4 Session Modification Request. If forwarding tunnel has been established to the new I-UPF and if the timer SMF set for forwarding tunnel at step 8a has expired, SMF sends N4 Session modification request to new (intermediate) UPF acting as N3 terminating point to release the forwarding tunnel. 20b. [Conditional] new UPF (intermediate) to SMF: N4 Session modification response. New (intermediate) UPF acting as N3 terminating point sends N4 Session Modification response to SMF. 21a. [Conditional] SMF to UPF (PSA): N4 Session Modification Request. If forwarding tunnel has been established to the UPF (PSA) and if the timer SMF set for forwarding tunnel at step 7b has expired, SMF sends N4 Session modification request to UPF (PSA) acting as N3 Terminating Point to release the forwarding tunnel. 21b. [Conditional] UPF (PSA) to SMF: N4 Session Modification Response. UPF (PSA) acting as N3 Terminating Point sends N4 Session Modification Response to SMF. 22a. [Conditional] SMF to old UPF: N4 Session Modification Request or N4 Session Release Request. If the SMF decided to continue using the old UPF in step 5b, the SMF sends an N4 Session Modification Request, providing AN Tunnel Info. If the SMF decided to select a new UPF to act as intermediate UPF in step 5b and the old UPF is not PSA UPF, the SMF initiates resource release, after timer in step 6b or 7b expires, by sending an N4 Session Release Request (Release Cause) to the old intermediate UPF. 22b. [Conditional] Old intermediate UPF to SMF: N4 Session Modification Response or N4 Session Release Response. The old UPF acknowledges with an N4 Session Modification Response or N4 Session Release Response message to confirm the modification or release of resources. For the mobility related events described in clause 4.15.4, the AMF invokes the Namf_EventExposure_Notify service operation after step 4. Upon reception of the Namf_EventExposure_Notify with an indication that the UE is reachable, if the SMF has pending DL data the SMF invokes the Namf_Communication_N1N2MessageTransfer service operation to the AMF to establish the User Plane(s) for the PDU Sessions, otherwise the SMF resumes sending DL data notifications to the AMF in the case of DL data. Upon reception of the Namf_EventExposure_Notify with an indication that UE is reachable only for regulatory prioritized service, the SMF deactivates the PDU Session if the service of the PDU Session is not regulatory prioritized. For home routed roaming case, the V-SMF triggers the deactivation of the PDU Session, in addition, the H-SMF refrains from sending downlink signalling if the signalling is not related to regulatory prioritized service upon receiving the notification. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.2.3.2 |
2,909 | 10.5.4.11b CLIR invocation | The CLIR invocation information element may be sent by the mobile station to the network in the SETUP message. The use is defined in 3GPP TS 24.081[ Line Identification supplementary services; Stage 3 ] [25]. The CLIR invocation information element is coded as shown in figure 10.5.97/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The CLIR invocation is a type 2 information element. Figure 10.5.97/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] CLIR invocation 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.4.11b |
2,910 | β SL-ScheduledConfig | The IE SL-ScheduledConfig specifies sidelink communication/positioning configurations used for network scheduled NR sidelink communication/positioning. SL-ScheduledConfig information element -- ASN1START -- TAG-SL-SCHEDULEDCONFIG-START SL-ScheduledConfig-r16 ::= SEQUENCE { sl-RNTI-r16 RNTI-Value, mac-MainConfigSL-r16 MAC-MainConfigSL-r16 OPTIONAL, -- Need M sl-CS-RNTI-r16 RNTI-Value OPTIONAL, -- Need M sl-PSFCH-ToPUCCH-r16 SEQUENCE (SIZE (1..8)) OF INTEGER (0..15) OPTIONAL, -- Need M sl-ConfiguredGrantConfigList-r16 SL-ConfiguredGrantConfigList-r16 OPTIONAL, -- Need M ..., [[ sl-DCI-ToSL-Trans-r16 SEQUENCE (SIZE (1..8)) OF INTEGER (1..32) OPTIONAL -- Need M ]], [[ sl-ConfiguredGrantConfigDedicated-SL-PRS-RP-List-r18 SL-ConfiguredGrantConfigDedicated-SL-PRS-RP-List-r18 OPTIONAL -- Need M ]] } MAC-MainConfigSL-r16 ::= SEQUENCE { sl-BSR-Config-r16 BSR-Config OPTIONAL, -- Need M ul-PrioritizationThres-r16 INTEGER (1..16) OPTIONAL, -- Need M sl-PrioritizationThres-r16 INTEGER (1..8) OPTIONAL, -- Need M ... } SL-ConfiguredGrantConfigList-r16 ::= SEQUENCE { sl-ConfiguredGrantConfigToReleaseList-r16 SEQUENCE (SIZE (1..maxNrofCG-SL-r16)) OF SL-ConfigIndexCG-r16 OPTIONAL, -- Need N sl-ConfiguredGrantConfigToAddModList-r16 SEQUENCE (SIZE (1..maxNrofCG-SL-r16)) OF SL-ConfiguredGrantConfig-r16 OPTIONAL -- Need N } SL-ConfiguredGrantConfigDedicated-SL-PRS-RP-List-r18 ::= SEQUENCE { sl-ConfiguredGrantConfigDedicated-SL-PRS-RPToReleaseList-r18 SEQUENCE (SIZE (1..maxNrofCG-SL-r16)) OF SL-ConfigIndexCG-r16 OPTIONAL, -- Need N sl-ConfiguredGrantConfigDedicated-SL-PRS-RPToAddModList-r18 SEQUENCE (SIZE (1..maxNrofCG-SL-r16)) OF SL-ConfiguredGrantConfigDedicatedSL-PRS-RP-r18 OPTIONAL -- Need N } -- TAG-SL-SCHEDULEDCONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | β |
2,911 | 7.7 Carrier Aggregation | When CA is configured, the UE only has one RRC connection with the network. At RRC connection establishment/re-establishment/handover, one serving cell provides the NAS mobility information, and at RRC connection re-establishment/handover, one serving cell provides the security input. This cell is referred to as the Primary Cell (PCell). Depending on UE capabilities, Secondary Cells (SCells) can be configured to form together with the PCell a set of serving cells. The configured set of serving cells for a UE therefore always consists of one PCell and one or more SCells. The reconfiguration, addition and removal of SCells can be performed by RRC. At intra-NR handover and during connection resume from RRC_INACTIVE, the network can also add, remove, keep, or reconfigure SCells for usage with the target PCell. When adding a new SCell, dedicated RRC signalling is used for sending all required system information of the SCell i.e. while in connected mode, UEs need not acquire broadcast system information directly from the SCells. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 7.7 |
2,912 | 6.2.13 Handling of Small data rate control | Small data rate control is applicable only to NB-N1 mode and WB-N1 mode. Small data rate control controls the maximum number of uplink user data messages including uplink exception data reporting sent by the UE in a time interval for the PDU session in accordance with 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8]. The UE shall limit the rate at which it generates uplink user data messages to comply with the small data rate control policy. The NAS shall provide the indicated rates to upper layers for enforcement. The indicated rates in a NAS procedure applies to the PDU session the NAS procedure corresponds to, and the indicated rates are valid until a new value is indicated or the PDU session is released. If the UE indicates support for CIoT 5GS optimizations, the network may provide the small data rate control parameters to the UE and may provide the small data rate control parameters for exception data to the UE if and only if the small data rate control parameters is provided to the UE. Small data rate control parameters and small data rate control parameters for exception data can also be provided to the UE in S1 mode as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15]. If an allowed indication of additional exception reports is provided with the small data rate control parameters and: - the additional small data rate control parameters for exception data is provided and the limit for additional rate for exception data reporting is not reached; or - the additional small data rate control parameters for exception data is not provided, the UE is allowed to send uplink exception reports even if the limit for the small data rate control has been reached. During a PDU session release procedure, if the small data rate control was applied to the PDU session that is being released, the network may store the small data rate control status for the released PDU session as specified in 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8]. If: a) the UE indicates support for CIoT 5GS optimizations; and b) the small data rate control status was stored for the PDU session and is still valid, the network may provide the remaining small data rate control status as initial small data rate control parameters to the UE and initial small data rate control parameters for exception data to the UE during a subsequent PDU session establishment procedure. If received during the establishment of a PDU session, the UE shall apply the initial small data rate control parameters and the initial small data rate control parameters for exception data for the duration of the validity period. When the validity period expires the small data rate control parameters and the small data rate control parameters for exception data shall be applied (see 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8]). NOTE 1: The HPLMN can discard or delay user data that exceeds the limit provided for small data rate control. Upon inter-system change from N1 mode to S1 mode, the UE shall store the current small data rate control status for PDU sessions to be transferred from N1 mode to S1 mode as specified in 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8]. NOTE 2: How long the UE stores the current small data rate control status is implementation specific. Upon inter-system change from S1 mode to N1 mode, the UE shall use the stored small data rate control status, if any, to comply with the small data rate control policy for PDU sessions transferred from S1 mode to N1 mode as specified in 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8], if the validity period of the stored small data rate control status has not expired. | 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.13 |
2,913 | 5.31.14.2 Serving PLMN Rate Control | The Serving PLMN Rate Control value is configured in the (V-)SMF. NOTE 1: Homogeneous support of Serving PLMN Rate Control in a network is assumed. At PDU Session establishment and PDU Session modification, the (V-)SMF may inform the UE and UPF/NEF of any per PDU Session local Serving PLMN Rate Control that the Serving PLMN intends to enforce for NAS Data PDUs. The (V-)SMF shall only indicate a Serving PLMN Rate Control command to the UPF if the PDU Session is using N4 and is set to Control Plane only. The (V-)SMF shall only indicate a Serving PLMN Rate Control command to the NEF if that PDN connection is using NEF. Serving PLMN rate control is operator configurable and expressed as "X NAS Data PDUs per deci hour" where X is an integer that shall not be less than 10. There are separate limits for uplink and downlink NAS Data PDUs: - The UE shall limit the rate at which it generates uplink NAS Data PDUs to comply with the Serving PLMN policy. In the UE the indicated rate control applies only on the PDU Session where it was received, and therefore the UE shall limit the rate of its uplink NAS Data PDUs to comply with the rate that is indicated for the PDU Session. The indicated rate is valid until the PDU Session is released. - The UPF/NEF shall limit the rate at which it generates downlink Data PDUs. In the UPF/NEF the indicated rate control applies only on the PDU Session where it was received, and therefore the UPF/NEF shall limit the rate of its downlink Data PDUs to comply with the rate that is indicated for the PDU Session. - The (V-)SMF may enforce these limits per PDU Session by discarding or delaying packets that exceed these limits. The Serving PLMN Rate does not include SMS using NAS Transport PDUs. The (V-)SMF starts the Serving PLMN Rate Control when the first NAS Data PDU is received. NOTE 2: If the UE/UPF/NEF start the Serving PLMN rate control at a different time than the (V-)SMF, PDUs sent within the limit enforced at the UE/UPF/NEF can still exceed the limit enforced by the (V-)SMF. NOTE 3 It is assumed that the Serving PLMN Rate is sufficiently high to not interfere with the Small Data Rate Control as the Small Data Rate Control, if used, is assumed to allow fewer messages. NAS PDUs related to exception reports are not subject to the Serving PLMN Rate Control. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.31.14.2 |
2,914 | 5.2.6.15.2 Nnef_SMContext_Create service operation | Service operation name: Nnef_SMContext_Create Description: This service operation is used by the consumer to request connection establishment between NF consumer and NEF to support NIDD via NEF. Inputs, Required: User Identity, PDU session ID, NIDD information, S-NSSAI, DNN. Inputs, Optional: RDS support indication, Serving PLMN Rate Control parameters, Small Data Rate Control parameters and Small Data Control Status. Outputs, Required: Cause. Outputs, Optional: Extended Buffering Support, NIDD Parameters, RDS support indication. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.6.15.2 |
2,915 | 8.9.4 Inter-gNB handover involving gNB-CU-UP change | Figure 8.9.4-1 shows the procedure used for inter-gNB handover involving gNB-CU-UP change. Overall inter-gNB handover procedure is specified in TS 37.340[ Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Overall Description; Stage-2 ] [12]. Figure 8.9.4-1: Inter-gNB handover involving gNB-CU-UP change 1. The source gNB-CU-CP sends HANDOVER REQUEST message to the target gNB-CU-CP. In case of Conditional Handover, the target gNB is regarded as a candidate gNB which is only accessed by the UE when the CHO condition(s) are fulfilled. 2-4. Bearer Context Setup procedure is performed as described in clause 8.9.2. 5. The target gNB-CU-CP responds the source gNB-CU-CP with an HANDOVER REQUEST ACKNOWLEDGE message. NOTE: In case of Conditional Handover, it is up to target gNB-CU-CP implementation to make sure that the EARLY STATUS TRANSFER information is forwarded to the right gNB-CU-UP (e.g. separate UE-associated signalling connection over Xn interface for each gNB-CU-UP). 6. The F1 UE Context Modification procedure is performed to send the handover command to the UE, and to indicate to stop the data transmission for the UE. NOTE: In case of DAPS Handover or Conditional Handover, the F1 UE Context Modification procedure in step 6 does not indicate to stop the data transmission for the UE. Instead, the F1 DL RRC Message Transfer procedure can be used which carries the handover command to the UE. 7-8. Bearer Context Modification procedure (gNB-CU-CP initiated) is performed to enable the gNB-CU-CP to retrieve the PDCP UL/DL status and to exchange data forwarding information for the bearer. 9. The source gNB-CU-CP sends an SN STATUS TRANSFER message to the target gNB-CU-CP. NOTE: In case of DAPS Handover, the EARLY STATUS TRANSFER message is sent for DRBs configured with DAPS instead of the SN STATUS TRANSFER message. NOTE: In case of Conditional Handover, the EARLY STATUS TRANSFER message is sent only if early data forwarding is applied. NOTE: The COUNT related info for the EARLY STATUS TRANSFER message is retrieved from the source gNB-CU-UP via the steps 7/8. 10-11. Bearer Context Modification procedure is performed as described in clause 8.9.2. The target gNB-CU-CP does not transfer the PDCP UL/DL status carried from the SN STATUS TRANSFER message to the target gNB-CU-UP if the PDCP status does not need to be preserved (e.g. full configuration). In case of DAPS Handover or Conditional Handover, the COUNT related info carried by the EARLY STATUS TRANSFER message is provided to the target gNB-CU-UP. 12. Data Forwarding may be performed from the source gNB-CU-UP to the target gNB-CU-UP. NOTE: In case of Conditional Handover, the UE performs RACH when the CHO condition(s) are fulfilled. Once successfully accessed, the target gNB-DU sends an ACCESS SUCCESS message to inform the target gNB-CU-CP of which cell the UE has accessed through. The target gNB-CU-CP may forward to the target gNB-CU-UP, necessary information for sending downlink packets (i.e. DL TNL address information for F1-U and UP security information corresponding to the accessed cell), via a Bearer context modification procedure. The target gNB-CU-CP may initiate Bearer context release procedure toward the other signalling connections or other candidate target gNB-CU-UPs, if any, to release the prepared conditional handover resources for the UE. 12a. In case of DAPS Handover or Conditional Handover, the target gNB-CU-CP sends the HANDOVER SUCCESS message to the source gNB-CU-CP to inform that the UE has successfully accessed the target cell. 12b In case of DAPS Handover or Conditional Handover, the F1 UE Context Modification procedure is performed to indicate to stop the data transmission for the UE. 12c-12d. In case of DAPS Handover or Conditional Handover, the Bearer context modification procedure (gNB-CU-CP initiated) is performed to indicate the source gNB-CU-UP to stop packet delivery and also to retrieve the PDCP UL/DL status. 12e. In case of DAPS Handover or Conditional Handover, the source gNB-CU-CP sends the SN STATUS TRANSFER message to the target gNB-CU-CP. 12f-12g. In case of DAPS Handover or Conditional Handover, the Bearer context modification procedure is performed to provide the PDCP UL/DL status to the target gNB-CU-UP only if the PDCP status needs to be preserved as described in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [2]. NOTE: In case of Conditional Handover, inactivity monitoring is performed after step 12g. 13-15. Path Switch procedure is performed to update the DL TNL address information for the NG-U towards the core network. 16. The target gNB-CU-CP sends an UE CONTEXT RELEASE message to the source gNB-CU-CP. 17. and 19. Bearer Context Release procedure is performed. 18. F1 UE Context Release procedure is performed to release the UE context in the source gNB-DU. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 8.9.4 |
2,916 | 9.9.4.3 EPS quality of service | The purpose of the EPS quality of service information element is to specify the QoS parameters for an EPS bearer context. The EPS quality of service information element is coded as shown in figure 9.9.4.3.1 and table 9.9.4.3.1. The EPS quality of service is a type 4 information element with a minimum length of 3 octets and a maximum length of 15 octets. Octets 4-15 are optional. If octet 4 is included, then octets 5-7 shall also be included, and octets 8-15 may be included. If octet 8 is included, then octets 4-11 shall also be included, and octets 12-15 may be included. If octet 12 is included, then octets 4-15 shall also be included. The length of the EPS QoS IE can be either 3 octets, 7 octets, 11 octets or 15 octets. Refer to 3GPP TS 23.203[ Policy and charging control architecture ] [7] for a detailed description of the QoS Class Identifier (QCI). Figure 9.9.4.3.1: EPS quality of service information element Table 9.9.4.3.1: EPS quality of service 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.3 |
2,917 | 5.6 SC-FDMA baseband signal generation | This clause applies to all uplink physical signals and uplink physical channels except the physical random access channel and PUSCH using sub-PRB allocations for BL/CE UEs. The time-continuous signal for antenna port in SC-FDMA symbol in an uplink slot is defined by for where , , and is the content of resource element on antenna port . For frame structure type 3, if the associated DCI indicates PUSCH starting position other than '00' or if 'autonomous PUSCH' is configured, is given by where and were is given by TS36.213 [4] if 'autonomous PUSCH' is configured. The quantity is given by clause 8.1. The UE behaviour if is undefined. The SC-FDMA symbols in a slot shall be transmitted in increasing order of , starting with , where SC-FDMA symbol starts at time within the slot. Table 5.6-1 lists the values of that shall be used. Table 5.6-1: SC-FDMA parameters | 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.6 |
2,918 | 4.7.5.1.3 Normal and periodic routing area updating procedure accepted by the network | If the routing area updating request has been accepted by the network, a ROUTING AREA UPDATE ACCEPT message shall be sent to the MS. The network may assign a new P-TMSI and/or a new P-TMSI signature for the MS. If a new P-TMSI and/or P-TMSI signature have been assigned to the MS, it/they shall be included in the ROUTING AREA UPDATE ACCEPT message together with the routing area identification. In a shared network, if the MS is a network sharing supporting MS, the network shall indicate the PLMN identity of the CN operator that has accepted the routing area updating request in the RAI contained in the ROUTING AREA UPDATE ACCEPT message; if the MS is a network sharing non-supporting MS, the network shall indicate the PLMN identity of the common PLMN (see 3GPP TS 23.251[ Network sharing; Architecture and functional description ] [109]). If the PLMN identity of the common PLMN included in the RAI does not identify the CN operator that has accepted the routing area updating request, the network may include the PLMN identity of the CN operator that has accepted the routing area updating request in the ROUTING AREA UPDATE ACCEPT message. In a multi-operator core network (MOCN) with common GERAN, the network shall indicate in the RAI the common PLMN identity (see 3GPP TS 23.251[ Network sharing; Architecture and functional description ] [109]). If the common PLMN identity included in the RAI does not identify the CN operator that has accepted the routing area updating request, the network may include the PLMN identity of the CN operator that has accepted the routing area updating request in the ROUTING AREA UPDATE ACCEPT message. In A/Gb mode, if the MS indicates support of integrity protection in the MS network capability IE in the ROUTING AREA UPDATE REQUEST message, and if the network supports integrity protection, then the network shall store all octets received from the MS in the MS network capability IE and in the MS Radio Access Capability IE, up to the maximum length defined for the respective information element. NOTE 1: The network needs to store the MS network capability and MS Radio Access Capability exactly as received from the MS and network is not allowed to ignore the "higher" octets sent by the MS even if the network does not support any features indicated in the higher octetst. Otherwise the replay check of the MS network capability and MS Radio Access Capability will fail in the MS. In A/Gb mode, if a UMTS security context is available in the network and if the MS indicates support of integrity protection in the ROUTING AREA UPDATE REQUEST message and the network supports integrity protection, and if integrity protection of the ROUTING AREA UPDATE REQUEST message is successfully verified in the LLC layer in the network, then if the network decides to re-authenticate the MS or select a new integrity algorithm or ciphering algorithm, the network shall initiate an authentication and ciphering procedure. In A/Gb mode, if a UMTS security context is available in the network and if the MS indicates support of integrity protection in the ROUTING AREA UPDATE REQUEST message and the network supports integrity protection if integrity protection of the ROUTING AREA UPDATE REQUEST message is successfully verified in the LLC layer in the network, the network may decide to continue using the stored GPRS GSM Kint integrity key, GPRS GSM Kc128 encryption key, GPRS GSM ciphering algorithm and GPRS GSM integrity algorithm in the LLC layer without initiating an authentication and ciphering procedure. If the MS and network continue to use the same ciphering mode, ciphering or no ciphering, the ciphering mode is re-established without the need to run an authentication and ciphering procedure. The network shall replay the MS network capability IE and the MS radio access capability IE received from the MS in the ROUTING AREA UPDATE REQUEST message, by including the MS network capability IE and the MS radio access capability IE in the ROUTING AREA UPDATE ACCEPT message to the MS. The GMM layer in the network shall assign the stored GPRS GSM Kint key, the GPRS GSM Kc128 key, the GPRS GSM integrity algorithm and the GPRS GSM ciphering algorithm to the LLC layer. The MS shall then indicate to the LLC layer that it shall start integrity protection and ciphering in the LLC layer before sending the ROUTING AREA UPDATE ACCEPT message to the MS. If the integrity protection of the ROUTING AREA UPDATE REQUEST message is not successfully verified in the LLC layer or if the ROUTING AREA UPDATE REQUEST message is received without integrity protection, then the network shall progress the routing area updating procedure and initiate an authentication and ciphering procedure to authenticate the MS and activate integrity protection and ciphering in the MS. In A/Gb mode, if a UMTS security context is available in the network and if the MS indicates support of integrity protection in the ROUTING AREA UPDATE REQUEST message and the network supports integrity protection, and if the network is not able to verify the message authentication code in the LLC layer protecting the ROUTING AREA UPDATE REQUEST message, due to the LLC layer at the network not having been configured yet with the integrity key and integrity algorithm for this MS, then the network shall progress the ROUTING AREA UPDATE REQUEST message at GMM layer anyway. If the CKSN included in the ROUTING AREA UPDATE REQUEST message belongs to an UMTS security context available in the network, then the network may re-establish integrity protection and ciphering of layer 3 signalling messages in the LLC layer without initiating an authentication and ciphering procedure. In A/Gb mode, if the MS indicates support of integrity protection of user plane data in the MS network capability IE in the ROUTING AREA UPDATE REQUEST message, and if the network supports and accepts integrity protection of user plane data, then the network shall indicate integrity protection of user plane data to the MS in the ROUTING AREA UPDATE ACCEPT message. The MS shall indicate to the LLC layer to start integrity protection of user plane data after the reception of the ROUTING AREA UPDATE ACCEPT message, if indicated. The same GPRS GSM Kint key and the same GPRS GSM integrity algorithm used for integrity protection of layer 3 signalling messages shall be used for integrity protection of user plane data in the LLC layer. The network shall indicate to the LLC layer to start integrity protection of user plane data after sending the ROUTING AREA UPDATE ACCEPT message to the MS. If the network does not indicate to the MS in the ROUTING AREA UPDATE ACCEPT message that it accepts the use of integrity protection of user plane data, and if the MS does not accept such a network, then the MS shall detach from the network. If a new DRX parameter was included in the ROUTING AREA UPDATE REQUEST message, the network shall store the new DRX parameter and use it for the downlink transfer of signalling and user data. The network shall include the extended DRX parameters IE in the ROUTING AREA UPDATE ACCEPT message only if the extended DRX parameters IE was included in the ROUTING AREA UPDATE REQUEST message, and the network supports and accepts the use of eDRX. If the MS has indicated in the ROUTING AREA UPDATE REQUEST message that it supports PS inter-RAT handover from GERAN to UTRAN Iu mode, the network may include in the ROUTING AREA UPDATE ACCEPT message a request to provide the Inter RAT information container. If the MS has included the MS network capability IE or the UE network capability IE or both in the ROUTING AREA UPDATE REQUEST message, the network shall store all octets received from the MS, up to the maximum length defined for the respective information element. In case the UE network capability IE indicated new information to the network, the MS shall set the TIN to "P-TMSI". NOTE 2: This information is forwarded to the new SGSN during inter-SGSN handover or to the new MME during intersystem handover to S1 mode. In A/Gb mode the Cell Notification information element shall be included in the ROUTING AREA UPDATE ACCEPT message in order to indicate the ability of the network to support the Cell Notification. The network shall change to state GMM-COMMON-PROCEDURE-INITIATED and shall start the supervision timer T3350 as described in subclause 4.7.6. If the LAI or PLMN identity contained in the ROUTING AREA UPDATE ACCEPT message is a member of any of the "forbidden" lists and the MS is not attached for emergency bearer services, then any such entry shall be deleted. In Iu mode, the network should prolong the PS signalling connection if the mobile station has indicated a follow-on request pending in ROUTING AREA UPDATE REQUEST. The network may also prolong the PS signalling connection without any indication from the mobile terminal (for example, if user plane radio access bearers have been established for the MS). If the PDP context status information element is included in ROUTING AREA UPDATE REQUEST message, then the network shall deactivate all those PDP contexts locally (without peer to peer signalling between the MS and the network), which are not in SM state PDP-INACTIVE on network side but are indicated by the MS as being in state PDP-INACTIVE. If the MBMS context status information element is included in the ROUTING AREA UPDATE REQUEST message, then the network shall deactivate all those MBMS contexts locally (without peer to peer signalling between the MS and network) which are not in SM state PDP-INACTIVE on the network side, but are indicated by the MS as being in state PDP-INACTIVE. If no MBMS context status information element is included, then the network shall deactivate all MBMS contexts locally which are not in SM state PDP-INACTIVE on the network side. If a ROUTING AREA UPDATE REQUEST message is received from an MS with a LIPA PDN connection, and if: - a L-GW Transport Layer Address is provided by the lower layer together with the ROUTING AREA UPDATE REQUEST message, and the GGSN address associated with the PDP context of the LIPA PDN connection is different from the provided L-GW Transport Layer Address (see 3GPP TS 25.413[ UTRAN Iu interface Radio Access Network Application Part (RANAP) signalling ] [19c]); or - no L-GW Transport Layer Address is provided together with the ROUTING AREA UPDATE REQUEST message by the lower layer, then the SGSN locally deactivates all PDP contexts associated with the LIPA PDN connection. If the ROUTING AREA UPDATE REQUEST request message is accepted, the SGSN informs the MS via the PDP context status IE in the ROUTING AREA UPDATE ACCEPT message that PDP contexts were locally deactivated. If a ROUTING AREA UPDATE REQUEST message is received from an MS with a SIPTO at the local network PDN connection, the following different cases can be distinguished: 1) If the PDN connection is a SIPTO at the local network PDN connection with collocated L-GW and if: - a SIPTO L-GW Transport Layer Address is provided by the lower layer together with the ROUTING AREA UPDATE REQUEST message, and the GGSN address associated with the PDP context of the SIPTO at the local network PDN connection is different from the provided SIPTO L-GW Transport Layer Address (see 3GPP TS 25.413[ UTRAN Iu interface Radio Access Network Application Part (RANAP) signalling ] [19c]); or - no SIPTO L-GW Transport Layer Address is provided together with the ROUTING AREA UPDATE REQUEST message by the lower layer, 2) If the PDN connection is a SIPTO at the local network PDN connection with stand-alone GW and if: - a LHN-ID value is provided by the lower layer together with the ROUTING AREA UPDATE REQUEST message, and the LHN-ID stored in the PDP context of the SIPTO at the local network PDN connection is different from the provided LHN-ID value (see 3GPP TS 25.413[ UTRAN Iu interface Radio Access Network Application Part (RANAP) signalling ] [19c]); or - no LHN-ID value is provided together with the ROUTING AREA UPDATE REQUEST message by the lower layer, then the SGSN locally deactivates all PDP contexts associated with the SIPTO at the local network PDN connection. If the ROUTING AREA UPDATE REQUEST request message is accepted, the SGSN informs the MS via the PDP context status IE in the ROUTING AREA UPDATE ACCEPT message that PDP contexts were locally deactivated. For a SIPTO at the local network PDN connection with stand-alone GW, the conditions to deactivate ISR are specified in 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [122], subclause 4.3.5.6. If due to regional subscription restrictions or access restrictions the MS is not allowed to access the routing area, but the MS has a PDN connection for emergency bearer services established, the network may accept the ROUTING AREA UPDATE REQUEST message and deactivate all non-emergency PDP contexts by initiating an PDP context deactivation procedure when the routing area updating procedure is initiated in PMM-CONNECTED mode. When the routing area updating procedure is initiated in PMM-IDLE mode, the network locally deactivates all non-emergency PDP contexts and informs the MS via the PDP context status IE in the ROUTING AREA UPDATE ACCEPT message. The network shall not deactivate the PDP contexts for emergency bearer services. The network shall consider the MS to be attached for emergency bearer services only. If the network supports delivery of SMS via GPRS (see 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [74]) and this delivery is enabled (see 3GPP TS 29.272[ Evolved Packet System (EPS); Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) related interfaces based on Diameter protocol ] [150]), then the network shall include the Additional network feature support IE in the ROUTING AREA UPDATE ACCEPT message and set the GPRS-SMS indicator. If the network supports the extended protocol configuration options IE and the MS indicated support of the extended protocol configuration options IE, then the network shall include the Additional network feature support IE in the ROUTING AREA UPDATE ACCEPT message and set the ePCO IE indicator to "extended protocol configuration options IE supported". The network shall indicate "combined RA/LA updated" or "combined RA/LA updated and ISR activated" in the update result IE in the ROUTING AREA UPDATE ACCEPT message, if the following conditions apply: - the update type IE included in the ROUTING AREA UPDATE REQUEST message indicates "periodic updating" and the MS was previously successfully attached for GPRS and non-GPRS services; and - location area updating for non-GPRS services as specified in 3GPP TS 29.018[ General Packet Radio Service (GPRS); Serving GPRS Support Node (SGSN) - Visitors Location Register (VLR); Gs interface layer 3 specification ] [149] is successful. The network shall include the T3324 value IE in the ROUTING AREA UPDATE ACCEPT message only if the T3324 value IE was included in the ROUTING AREA UPDATE REQUEST message, and the network supports and accepts the use of PSM. If the network supports and accepts the use of PSM, and the MS included the T3312 extended value IE in the ROUTING AREA UPDATE REQUEST message, then the network shall take into account the T3312 value requested when providing the Periodic RA update timer IE and the T3312 extended value IE in the ROUTING AREA UPDATE ACCEPT message. NOTE 3: Besides the value requested by the MS, the network can take local configuration into account when selecting a value for T3312 (see 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [74] subclause 5.3.13.54). In A/Gb mode, if the MS indicates support for restriction on use of enhanced coverage in the ROUTING AREA UPDATE REQUEST message, and the network restricts enhanced coverage for the MS, then the network shall set the RestrictEC bit to "Enhanced coverage restricted" in the Additional network feature support IE of the ROUTING AREA UPDATE ACCEPT message. If the network includes the T3324 value IE indicating a value other than deactivated in the ROUTING AREA UPDATE ACCEPT message, the network shall indicate in the Update result IE in the ROUTING AREA UPDATE ACCEPT message that ISR is not activated. Upon receipt of a ROUTING AREA UPDATE ACCEPT message, the MS shall store the received routing area identification, stops timer T3330, reset the routing area updating attempt counter, reset the service request attempt counter and set the GPRS update status to GU1 UPDATED. If the message contains a P-TMSI, the MS shall use this P-TMSI as new temporary identity for GPRS services and shall store the new P-TMSI. If no P-TMSI was included by the network in the ROUTING AREA UPDATE ACCEPT message, the old P-TMSI shall be kept. Furthermore, the MS shall store the P-TMSI signature if received in the ROUTING AREA UPDATE ACCEPT message. If no P-TMSI signature was included in the message, the old P-TMSI signature, if available, shall be deleted. Upon receipt of a ROUTING AREA UPDATE ACCEPT message with update result IE indicating "combined RA/LA updated" or "combined RA/LA updated and ISR activated" during the periodic routing area updating procedure, the MS shall behave as follows: - if the ROUTING AREA UPDATE ACCEPT message contains an IMSI, the MS is not allocated any TMSI. The MS shall delete any old TMSI accordingly; - if the ROUTING AREA UPDATE ACCEPT message contains a TMSI, the MS shall use this TMSI as new temporary identity. The MS shall delete its old TMSI and shall store the new TMSI. In this case, a ROUTING AREA UPDATE COMPLETE message is returned to the network to confirm the received TMSI; or - if neither a TMSI nor an IMSI has been included by the network in the ROUTING AREA UPDATE ACCEPT message, the old TMSI, if any is available, shall be kept. Upon receiving a ROUTING AREA UPDATE COMPLETE message, the SGSN shall stop timer T3350 and change to state GMM-REGISTERED. The P-TMSI, if sent in the ROUTING AREA UPDATE ACCEPT message, shall be considered as valid. NOTE 4: Upon receiving a ROUTING AREA UPDATE COMPLETE message, if a new TMSI is included in the ROUTING AREA UPDATE ACCEPT message, the SGSN sends a BSSAP+-TMSI-REALLOCATION-COMPLETE message as specified in 3GPP TS 29.018[ General Packet Radio Service (GPRS); Serving GPRS Support Node (SGSN) - Visitors Location Register (VLR); Gs interface layer 3 specification ] [149]. If the PDP context status information element is included in ROUTING AREA UPDATE ACCEPT message, then the MS shall deactivate all those PDP contexts locally (without peer to peer signalling between the MS and network), which are not in SM state PDP-INACTIVE in the MS but are indicated by the network as being in state PDP-INACTIVE. If there is a default PDP context among the PDP contexts to be deactivated, an MS supporting S1 mode shall locally deactivate all PDP contexts associated to the same PDP address and APN as the default PDP context without peer-to-peer SM signalling to the network; an MS not supporting S1 mode may apply the same behaviour. If only the PDN connection for emergency bearer services remains established, the MS shall consider itself attached for emergency bearer services only. If the MBMS context status information element is included in the ROUTING AREA UPDATE ACCEPT message, then the MS shall deactivate all those MBMS contexts locally (without peer to peer signalling between the MS and network) which are not in SM state PDP-INACTIVE in the MS, but are indicated by the network as being in state PDP-INACTIVE. If no MBMS context status information element is included, then the MS shall deactivate all those MBMS contexts locally which are not in SM state PDP-INACTIVE in the MS. If the ROUTING AREA UPDATE ACCEPT message contains the T3312 extended value IE, then the MS shall use the T3312 extended value IE as periodic routing area update timer (T3312). If the ROUTING AREA UPDATE ACCEPT message does not contain the T3312 extended value IE, then the MS shall use value in the Periodic RA update timer IE as periodic routing area update timer (T3312). If the MS receives the ROUTING AREA UPDATE ACCEPT message from a PLMN for which a PLMN-specific attempt counter or PLMN-specific PS-attempt counter is maintained (see subclause 4.1.1.6A), then the MS shall reset these counters. If the MS maintains a counter for "SIM/USIM considered invalid for GPRS services", then the MS shall reset this counter. If the ROUTING AREA UPDATE ACCEPT message contains the T3324 value IE, then the MS shall use the timer value for T3324 as specified in subclause 4.7.2.8. If the ROUTING AREA UPDATE ACCEPT message contains the DCN-ID IE, then the MS shall store the included DCN-ID value together with the PLMN code of the registered PLMN in a DCN-ID list in a non-volatile memory in the ME as described in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120], annex C. In a shared network or in a multi-operator core network (MOCN) with common GERAN, if the ROUTING AREA UPDATE ACCEPT message contains the DCN-ID IE and the PLMN identity of the CN operator IE, the MS shall store the included DCN-ID value with the PLMN identity indicated in the PLMN identity of the CN operator IE, and the included DCN-ID value with the PLMN identity indicated in the RAI in a DCN-ID list in a non-volatile memory in the ME as described in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120], annex C. In A/Gb mode, if the ROUTING AREA UPDATE ACCEPT message contains the Cell Notification information element, then the MS shall start to use the LLC NULL frame to perform cell updates. If the MS has initiated the routing area updating procedure due to manual CSG selection and receives a ROUTING AREA UPDATE ACCEPT message, and the MS sent the ROUTING AREA UPDATE REQUEST message in a CSG cell, the MS shall check if the CSG ID and associated PLMN identity of the cell are contained in the Allowed CSG list. If not, the MS shall add that CSG ID and associated PLMN identity to the Allowed CSG list and the MS may add the HNB Name (if provided by lower layers) to the Allowed CSG list if the HNB Name is present in neither the Operator CSG list nor the Allowed CSG list. The network may also send a list of "equivalent PLMNs" in the ROUTING AREA UPDATE ACCEPT message. Each entry of the list contains a PLMN code (MCC+MNC). If the routing area updating procedure is initiated during a CS fallback procedure and the network is configured to support the return to the last registered E-UTRAN PLMN after CS fallback as specified in 3GPP TS 23.272[ Circuit Switched (CS) fallback in Evolved Packet System (EPS); Stage 2 ] [133], and the PLMN identity which is provided as part of the RAI contained in the ROUTING AREA UPDATE ACCEPT message differs from the last registered E-UTRAN PLMN identity, the network shall include the last registered E-UTRAN PLMN identity in the list of "equivalent PLMNs" in the ROUTING AREA UPDATE ACCEPT message. NOTE 5: The network can determine a routing area updating procedure is initiated during a CS fallback procedure as specified in 3GPP TS 23.272[ Circuit Switched (CS) fallback in Evolved Packet System (EPS); Stage 2 ] [133]. NOTE 6: The last registered E-UTRAN PLMN identity can be derived by the network as specified in 3GPP TS 23.272[ Circuit Switched (CS) fallback in Evolved Packet System (EPS); Stage 2 ] [133]. The mobile station shall store the list, as provided by the network, and further handle the list as follows: - if there is no PDN connection for emergency bearers established, the mobile station shall remove from the list of "equivalent PLMNs" any PLMN code that is already in the "forbidden PLMN" list. If the mobile station is operating in MS operation mode C or the mobile station is supporting S1 mode, it shall also remove any PLMN code that is already in the list of "forbidden PLMNs for GPRS service"; - if the MS is not attached for emergency bearer services and there is a PDN connection for emergency bearer services established, the MS shall remove from the list of "equivalent PLMNs" any PLMN code present in the "forbidden PLMN" list when the PDN connection for emergency bearer services is released. If the mobile station is operating in MS operation mode C or the mobile station is supporting S1 mode, it shall also remove any PLMN code present in the list of "forbidden PLMNs for GPRS service" when the PDN connection for emergency bearer services is released; and - in addition, for all cases the mobile station shall add to the stored list the PLMN code of the registered PLMN that sent the list. All PLMNs in the stored list shall be regarded as equivalent to each other for PLMN selection, cell selection/re-selection and handover. The stored list in the mobile station shall be replaced on each occurrence of the ROUTING AREA UPDATE ACCEPT message. If no list is contained in the message, then the stored list in the mobile station shall be deleted. An MS attached for emergency bearer services only shall delete the stored list when the MS enters the state GMM-DEREGISTERED. The list shall be stored in the mobile station while switched off so that it can be used for PLMN selection after switch on. A ROUTING AREA UPDATE COMPLETE message shall be returned to the network if the ROUTING AREA UPDATE ACCEPT message contained any of: - a P-TMSI; - a TMSI; - receive N-PDU Numbers (see 3GPP TS 44.065[ Mobile Station (MS) - Serving GPRS Support Node (SGSN); Subnetwork Dependent Convergence Protocol (SNDCP) ] [78] and 3GPP TS 25.322[ None ] [19b]); or - a request for the provision of Inter RAT handover information. If Receive N-PDU Numbers were included, the Receive N-PDU Numbers values valid in the MS, shall be included in the ROUTING AREA UPDATE COMPLETE message. If the network has requested the provision of Inter RAT handover information, the MS shall return a ROUTING AREA UPDATE COMPLETE message including the Inter RAT handover information IE to the network. NOTE 7: In Iu mode, after a routing area updating procedure, the mobile station can initiate Service Request procedure to request the resource reservation for the active PDP contexts if the resources have been released by the network or send upper layer message (e.g. ACTIVATE PDP CONTEXT REQUEST) to the network via the existing PS signalling connection. In Iu mode, if the network wishes to prolong the PS signalling connection (for example, if the mobile station has indicated "follow-on request pending" in ROUTING AREA UPDATE REQUEST message or if user plane radio access bearers have been established for the MS) the network shall indicate the "follow-on proceed" in the ROUTING AREA UPDATE ACCEPT message. If the network wishes to release the PS signalling connection, the network shall indicate "no follow-on proceed" in the ROUTING AREA UPDATE ACCEPT message. After that in Iu mode, the mobile station shall act according to the follow-on proceed flag included in the Update result information element in the ROUTING AREA UPDATE ACCEPT message (see subclause 4.7.13). The network may also send a Local Emergency Numbers List with local emergency numbers in the ROUTING AREA UPDATE ACCEPT, by including the Emergency Number List IE. The mobile equipment shall store the Local Emergency Numbers List, as provided by the network. The Local Emergency Numbers List stored in the mobile equipment shall be replaced on each receipt of the Emergency Number List IE. The received Local Emergency Numbers List shall be provided to the upper layers. The emergency number(s) received in the Emergency Number List IE are valid only in networks in the same country as the cell on which this IE is received. If no list is contained in the ROUTING AREA UPDATE ACCEPT message, then the stored Local Emergency Numbers List in the mobile equipment shall be kept, except if the mobile equipment has successfully registered to a PLMN in a country different from that of the PLMN that sent the Local Emergency Numbers List. The mobile equipment shall use the stored Local Emergency Numbers List of emergency numbers received from the network in addition to the emergency numbers stored on the SIM/USIM or ME to detect that the number dialled is an emergency number. NOTE 8: The mobile equipment may use the Local Emergency Numbers List to assist the end user in determining whether the dialled number is intended for an emergency service or for another destination, e.g. a local directory service. The possible interactions with the end user are implementation specific. NOTE 9: An MS that supports procedures specified in 3GPP TS 24.302[ Access to the 3GPP Evolved Packet Core (EPC) via non-3GPP access networks; Stage 3 ] [156], can get additional local emergency numbers through those procedures, which can be used based on operator policy (see 3GPP TS 24.302[ Access to the 3GPP Evolved Packet Core (EPC) via non-3GPP access networks; Stage 3 ] [156]) to detect that the number dialled is an emergency number. The Local Emergency Numbers List shall be deleted at switch off and removal of the SIM/USIM. The mobile equipment shall be able to store up to ten local emergency numbers received from the network. In order to indicate to the MS that the GUTI and TAI list assigned to the MS remain registered with the network and are valid in the MS, the network shall indicate in the Update result IE in the ROUTING AREA UPDATE ACCEPT message that ISR is activated. If the MS is attached for emergency bearer services or if the network has deactivated all non-emergency PDP contexts, the network shall indicate in the update result IE in the ROUTING AREA UPDATE ACCEPT message that ISR is not activated. If the ROUTING AREA UPDATE ACCEPT message contains: i) no indication that ISR is activated, an MS supporting S1 mode shall set the TIN to "P-TMSI" and shall stop the periodic tracking area update timer T3412 or T3423, if running; or ii) an indication that ISR is activated, then: - if the MS is required to perform tracking area updating for IMS voice termination as specified in annex P.5, the MS shall set the TIN to "P-TMSI" and shall stop the periodic tracking area update timer T3412 or T3423, if running; - if the MS had initiated the routing area updating procedure due to a change in DRX parameters, the MS shall set the TIN to "P-TMSI" and shall stop the periodic tracking area update timer T3412 or T3423 if running; - if the MS had initiated the routing area updating procedure due to a change in the UE's usage setting or the voice domain preference for E-UTRAN, the MS shall set the TIN to "P-TMSI" and shall stop the periodic tracking area update timer T3412 or T3423, if running; or - the MS shall regard the available GUTI and TAI list as valid and registered with the network. If the TIN currently indicates "GUTI" and the periodic tracking area update timer T3412 is running or is deactivated, the MS shall set the TIN to "RAT-related TMSI". If the TIN currently indicates "GUTI" and the periodic tracking area update timer T3412 has already expired, the MS shall set the TIN to "P-TMSI". In A/Gb mode, if a UMTS security context is available, if the MS indicates support of integrity protection in the ROUTING AREA UPDATE REQUEST message and the network supports integrity protection, then if the MS receives replayed capability IEβs in ROUTING AREA UPDATE ACCEPT message, then the MS shall check if the replayed MS network capability IE and the replayed MS Radio Access Capability IE received in the ROUTING AREA UPDATE ACCEPT message has not been altered compared to the MS network capability IE and the MS Radio Access Capability IE that the MS sent to the network in ROUTING AREA UPDATE REQUEST message. If the replayed MS network capability IE and the replayed MS Radio Access Capability IE are not the same, then the MS shall ignore the ROUTING AREA UPDATE ACCEPT message. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.7.5.1.3 |
2,919 | 6.8.1.5 USIM | The USIM shall support UMTS AKA and may support backwards compatibility with the GSM system, which consists of: Feature 1: 64-bit GSM cipher key derivation (conversion function c3) to access GSM BSS attached to a R99+ VLR/SGSN using a dual-mode R99+ ME; Feature 2: GSM AKA to access the GSM BSS attached to a R98- VLR/SGSN or when using ME not capable of UMTS AKA; Feature 3: SIM-ME interface (GSM 11.11) to operate within ME not capable of UMTS AKA. When the ME provides the USIM with RAND and AUTN, UMTS AKA shall be executed. If the verification of AUTN is successful, the USIM shall respond to the ME with the UMTS user response RES and the UMTS cipher/integrity keys CK and IK. The ME shall store CK and IK as current security context data on the USIM. If the USIM supports access to 64-bit GSM cipher key derivation (feature 1), the USIM shall also derive the 64-bit GSM cipher key Kc from the UMTS cipher/integrity keys CK and IK using conversion function c3 and send the derived Kc to the ME. In case the verification of AUTN is not successful, the USIM shall respond with an appropriate error indication to the ME. When the ME provides the USIM with only , and the USIM supports GSM AKA (Feature 2), GSM AKA shall be executed. The USIM first computes the UMTS user response RES and the UMTS cipher/integrity keys CK and IK. The USIM then derives the GSM user response SRES and the 64-bit GSM cipher key Kc using the conversion functions c2 and c3 and send the GSM user response SRES and the 64-bit GSM cipher key Kc to the ME. The ME shall store the 64-bit GSM cipher key Kc as the current security context on the USIM. In case the USIM does not support 64-bit GSM cipher key derivation (Feature 1) or GSM AKA (Feature 2), the ME shall be informed. An ME with a USIM that does not support GSM cipher key derivation (Feature 1) shall not perform the GSM cipher key derivation (conversion function c3) in the ME and therefore cannot operate in any GSM BSS with 64-bit key ciphering enabled. An ME with a USIM that does not support GSM AKA (Feature 2) cannot operate under a R98- VLR/SGSN. A USIM that does not support GSM AKA (Feature 2) cannot work within a ME that is not capable of UMTS AKA. | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | 6.8.1.5 |
2,920 | 4.7.7.1 Authentication and ciphering initiation by the network | The network initiates the authentication and ciphering procedure by transferring an AUTHENTICATION_AND_CIPHERING REQUEST message across the radio interface and starts timer T3360. The AUTHENTICATION_AND_CIPHERING REQUEST message shall contain all parameters necessary to calculate the response parameters when authentication is performed (see 3GPP TS 43.020[ Security related network functions ] [13] and 3GPP TS 33.102[ 3G security; Security architecture ] [5a]). If authentication is requested, then the AUTHENTICATION_AND_CIPHERING REQUEST message shall contain either: - In a GSM authentication challenge, the GPRS ciphering key sequence number and the RAND, or - In a UMTS authentication challenge, the GPRS ciphering key sequence number, the RAND and the AUTN. In A/Gb mode, if authentication is not requested, then the AUTHENTICATION_AND_CIPHERING REQUEST message shall not contain neither the GPRS ciphering key sequence number, the RAND nor the AUTN. In A/Gb mode, if ciphering is requested, in a GSM authentication challenge or in a UMTS authentication challenge, then the AUTHENTICATION_AND_CIPHERING REQUEST message shall indicate the GPRS GSM ciphering algorithm. In A/Gb mode, an MS supporting integrity protection shall ignore a GSM authentication challenge from the network. In A/Gb mode, in a UMTS authentication challenge, if the MS has indicated support for integrity protection in MS network capability IE included in the ATTACH REQUEST or ROUTING AREA UPDATE REQUEST message to the network, then if the network supports integrity protection then the network shall activate integrity protection in the MS (see subclause 4.7.3.1.3 and subclause 4.7.5.1.3). If the network does not activate integrity protection in the MS, then the MS shall detach from the network. In A/Gb mode, if no UMTS security context is available in the network or if no common UMTS security context is available in the MS and the network, and if the MS has indicated support for integrity protection in MS network capability IE to the network, then an authentication and activation of integrity protection and setting of ciphering mode (enabled or disabled), shall take place in the same authentication and ciphering procedure. The network shall replay the MS network capability IE and the MS radio access capability IE received from the MS in the latest ATTACH REQUEST message or the latest ROUTING AREA UPDATE REQUEST message, by including the MS network capability IE and the MS radio access capability IE in the AUTHENTICATION AND CIPHERING REQUEST message to the MS. The network shall select one of the GPRS GSM integrity algorithms indicated in the MS network capability IE received from the MS in the latest ATTACH REQUEST message or ROUTING AREA UPDATE REQUEST message. The selected GPRS GSM integrity algorithm shall be included in the AUTHENTICATION AND CIPHERING REQUEST message. The network shall enable or disable ciphering and include the selected GPRS GSM ciphering algorithm if ciphering is enabled. If ciphering is enabled, then the network shall select one of the GPRS GSM ciphering algorithm indicated in the MS network capability IE received from the MS in the latest ATTACH REQUEST message or ROUTING AREA UPDATE REQUEST message.The network shall calculate a message authentication code for the AUTHENTICATION AND CIPHERING REQUEST message at the GMM layer with the new integrity key, GPRS GSM Kint key, indicated by the GPRS ciphering key sequence number included in the AUTHENTICATION AND CIPHERING REQUEST message. The new GPRS GSM Kint shall be calculated from the new UMTS security context established in the same procedure as described in the subclause 4.7.7.3b. The AUTHENTICATION AND CIPHERING REQUEST message shall include the calculated message authentication code for integrity protection. In A/Gb mode, if an established UMTS security context is available in the network and if the MS has indicated support for integrity protection in the MS network capability IE, when authentication takes place in the authentication and ciphering procedure (regardless whether a change of the integrity algorithm, ciphering algorithm or a change of ciphering mode takes place in the same procedure), then the network shall replay the MS network capability IE and the MS Radio Access Capability IE received from the MS in the latest ATTACH REQUEST message or the latest ROUTING AREA UPDATE REQUEST message, by including the MS network capability IE and the MS Radio Access Capability IE into the AUTHENTICATION AND CIPHERING REQUEST message to the MS. If a change of the GPRS GSM integrity algorithm takes place in the same procedure, then the network shall select one of the GPRS GSMintegrity algorithms indicated in the MS network capability IE received from the MS in the latest ATTACH REQUEST message or ROUTING AREA UPDATE REQUEST message. The selected GPRS GSM integrity algorithm shall be included into the AUTHENTICATION AND CIPHERING REQUEST message. If the network decides to change the ciphering mode or the ciphering algorithm or both, then if ciphering is enabled the network shall select one of the GPRS GSM ciphering algorithms indicated in the MS network capability IE received from the MS in the latest ATTACH REQUEST message or ROUTING AREA UPDATE REQUEST message. The network shall also include the ciphering mode or the selected GPRS GSM ciphering algorithm or both, if ciphering is enabled (Ciphering algorithm IE) in the AUTHENTICATION AND CIPHERING REQUEST message. The network calculates a message authentication code over the parameters included in the AUTHENTICATION AND CIPHERING REQUEST message at the GMM layer with the new integrity key GPRS GSM Kint indicated by the GPRS ciphering key sequence number included by the AUTHENTICATION AND CIPHERING REQUEST message. The new GPRS GSM Kint shall be calculated from the new UMTS security context established in the same procedure as described in the subclause 4.7.7.3b. The AUTHENTICATION AND CIPHERING REQUEST message shall include the calculated message authentication code for integrity protection. In A/Gb mode, if an established UMTS security context context is available in the network and if the MS has indicated support for integrity protection in the MS network capability IE to the network, and if integrity protection is in use, then if only a change of the integrity algorithm or ciphering algorithm or both, or a change of the ciphering mode, is requested in the authentication and ciphering procedure, then the AUTHENTICATION AND CIPHERING REQUEST message shall include the new GPRS GSM integrity algorithm or the new setting of the ciphering mode and the new GPRS GSM ciphering algorithm; that shall be taken into use. NOTE: The AUTHENTICATION AND CIPHERING REQUEST message is protected by a message authentication code in the LLC layer when no authentication takes place in the authentication and ciphering procedure.Therefore, no message authentication code shall be calculated and included by the GMM layer into this message when only an algorithm change takes place. In addition, there is no need to replay the MS network capability IE and the MS Radio Access Capability IE in the AUTHENTICATION AND CIPHERING REQUEST message when no authentication takes place as a valid UMTS security context is already established between the MS and network. The network includes the A&C reference number information element in the AUTHENTICATION AND CIPHERING REQUEST message. Its value is chosen in order to link an AUTHENTICATION AND CIPHERING REQUEST in a RA with its RESPONSE. The A&C reference number value might be based on the RA Colour Code value. Additionally, the network may request the MS to include its IMEISV in the AUTHENTICATION AND CIPHERING RESPONSE message. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.7.7.1 |
2,921 | 8.4.1.2.5 Enhanced Downlink Control Channel Performance Requirement Type A - 2 Tx Antenna Port under Asynchronous Network | The test purpose is to verify the Enhanced Downlink Control Channel Performance Requirement Type A for PDCCH/PCFICH with 2 transmit antennas for the case of dominant interferer with interference model defined in clause B.5.2. For the parameters specified in Table 8.4.1-1 and Table 8.4.1.2.5-1, the average probability of a missed downlink scheduling grant (Pm-dsg) shall be below the specified value in Table 8.4.1.2.5-2 for the Enhanced Downlink Control Channel Performance Requirement Type A. In Table 8.4.1.2.5-1, Cell 1 is the serving cell, and Cell 2 and Cell 3 are the agressor 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 not provided. Table 8.4.1.2.5-1: Test Parameters for PDCCH/PCFICH Table 8.4.1.2.5-2: Minimum Performance for PDCCH/PCFICH for Enhanced Downlink Control Channel Performance Requirement Type A | 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.4.1.2.5 |
2,922 | 5.42 Support of Non-seamless WLAN offload | Non-seamless WLAN offload is an optional capability of a UE supporting WLAN radio access. The architecture to support authentication for Non-seamless WLAN offload in 5GS is defined in clause 4.2.15. A UE supporting Non-seamless WLAN offload may, while connected to WLAN access, route specific data flows via the WLAN access without traversing the 5GC. These UE data flows are identified using URSP configuration for Non-Seamless Offload, or UE Local Configurations as defined in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]. For these data flows, the UE uses the local IP address allocated by the WLAN access network and no IP address preservation is provided between WLAN and NG-RAN. For performing the Non-seamless WLAN offload, the UE needs to acquire a local IP address from the WLAN access network and it is not required to connect to an N3IWF, ePDG or TNGF. If the WLAN access network is configured to require the 5GS based access authentication of the UE for connecting to the WLAN, the UE performs the authentication procedure for Non-seamless WLAN offload in 5GS defined in clause 4.2.15 and in Annex S of TS 33.501[ Security architecture and procedures for 5G System ] [29]. After successful authentication, the UE is not considered to be entered in 5GS Registered state. The UE can send and receive traffic not traversing the 5GC and which is not under the control of the 5GC. A non-3GPP access network may be connected via SWa' to multiple PLMNs for 5G NSWO. In a roaming scenario the HPLMN may be reached by the UE via a WLAN access connected to more than one VPLMN. Therefore, a UE when roaming shall be able to indicate a specific selected VPLMN (e.g. using decorated NAI for 5G NSWO) through which the NSWO request should be sent towards the HPLMN. A non-3GPP access network may be connected to multiple SNPNs different from the Credentials Holder for 5G NSWO. When using the credentials owned by CH, the UE shall be able to indicate a specific selected SNPN (e.g. using decorated NAI for 5G NSWO) through which the NSWO request should be sent towards the CH in the following scenarios: - The CH hosts AUSF/UDM and the CH is reached by the UE via a WLAN access connected to a SNPN different from the CH as defined in Figure 4.2.15-3a. - The CH hosts AAA server and the CH is reached by the UE via a WLAN access connected to the AAA proxy in specific SNPN as defined in Figure 4.2.15-3b. A UE connected to a WLAN access network using 5GS credentials (as shown in Figure 4.2.15-1), may also be connected to the 5GC, for example to establish a PDU session. For example, the UE may connect to the 5GC either via another access type (such as NG-RAN), or via the same WLAN access network by performing the 5GS registration via Untrusted non-3GPP access procedure (using N3IWF) or interworking between ePDG connected to EPC and 5GS (using ePDG) defined in TS 23.502[ Procedures for the 5G System (5GS) ] [3]. When a UE is connected to a WLAN access network (e.g. using 5GS credentials) and using an Untrusted non-3GPP access, the UE can perform Non-Seamless Offload of some or all data traffic to this WLAN access network sending the traffic outside the IPSec tunnel encapsulation as defined in URSP rules with Non-Seamless Offload indication. A UE may use the Registration procedure for Trusted non-3GPP access defined in clause 4.12a.2.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3] and then determine to send some traffic (to be subject to Non-seamless WLAN offload) outside of the IPSec tunnel established with the TNGF. NOTE: A UE cannot first connect to a WLAN access network using 5GS credentials and without performing 5GS registration, and then later, on this WLAN access network, perform 5GS registration using the Trusted non-3GPP access procedure without first having to release the WLAN and then to establish a new WLAN association per the Registration procedure for Trusted non-3GPP access as defined in clause 4.12a.2.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. When the UE decides to use 5G NSWO to connect to the WLAN access network using its 5GS credentials but without registration to 5GS, the NAI format for 5G NSWO is used whose realm is different than the realm defined for usage of Trusted non-3GPP access to the 5GC (defined in clauses 28.7.6 and 28.7.7 of TS 23.003[ Numbering, addressing and identification ] [19]). The NAI format for 5G NSWO is defined in TS 23.003[ Numbering, addressing and identification ] [19]. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.42 |
2,923 | 6.2.4E UE maximum output power with additional requirements for category M1 and M2 UE | Additional ACLR and spectrum emission requirements can be signalled by the network to indicate that the UE shall also meet additional requirements in a specific deployment scenario. To meet these additional requirements, Additional Maximum Power Reduction (A-MPR) is allowed for the output power as specified in Table 6.2.2E-1 and Table 6.2.4E-2. Unless stated otherwise, an A-MPR of 0 dB shall be used. For UE Power Class 3 and 5 the specific requirements and identified subclauses are specified in Table 6.2.4E-1 and Table 6.2.4E-2 along with the allowed A-MPR values that may be used to meet these requirements. The allowed A-MPR values specified below in Table 6.2.4E-1 and Table 6.2.4E-2 and from 6.2.4-2 to 6.2.4-15 are in addition to the allowed MPR requirements specified in subclause 6.2.3E. Table 6.2.4E-1: Additional Maximum Power Reduction (A-MPR) for category M1 UE Table 6.2.4E-2: Additional Maximum Power Reduction (A-MPR) for category M2 UE Table 6.2.4E-3: A-MPR for "NS_04" for Cat-M1 Table 6.2.4E-4: A-MPR for "NS_07" for Cat-M1 Table 6.2.4E-5: A-MPR for "NS_12" for Cat-M1 For subPRB allocation, the allowed A-MPR values specified below in Table 6.2.4E-6 and Table 6.2.4E-7 for category M1 UE and category M2 UE respectively in addition to the allowed MPR requirements specified in subclause 6.2.3E. Table 6.2.4E-6: Additional Maximum Power Reduction (A-MPR) for category M1 UE for subPRB allocation Table 6.2.4E-7: Additional Maximum Power Reduction (A-MPR) for category M2 UE for subPRB allocation Table 6.2.4E-8: A-MPR for "NS_03" for Cat-M1 with sub-PRB allocation Table 6.2.4E-9: A-MPR for "NS_04" for Cat-M1 with sub-PRB allocation Table 6.2.4E-10: A-MPR for "NS_03" for Cat-M2 with sub-PRB allocation Table 6.2.4E-11: A-MPR for "NS_04" for Cat-M2 with sub-PRB allocation Table 6.2.4E-12: A-MPR for "NS_07" for Cat-M2 with sub-PRB allocation Table 6.2.4E-13: A-MPR for "NS_06" for Cat-M1 with sub-PRB allocation Table 6.2.4E-14: A-MPR for "NS_12" for Cat-M1 with sub-PRB allocation Table 6.2.4E-15: A-MPR for "NS_35" for Cat-M1 with sub-PRB allocation Table 6.2.4E-16: A-MPR for "NS_38" for Cat-M1 with sub-PRB allocation for E-UTRA lowest channel edge > 1427 MHz and β€ 1447 MHz Table 6.2.4E-17: A-MPR for "NS_05" for Cat-M2 with sub-PRB allocation Table 6.2.4E-18: A-MPR for "NS_06" for Cat-M2 with sub-PRB allocation Table 6.2.4E-19: A-MPR for "NS_12" for Cat-M2 with sub-PRB allocation for E-UTRA lower channel edge >= 814.2 MHz and β€ 829.2 MHz Table 6.2.4E-20: A-MPR for "NS_13" for Cat-M2 with sub-PRB allocation for E-UTRA lower channel edge >= 819 MHz and β€ 824 MHz Table 6.2.4E-21: A-MPR for "NS_15" for Cat-M2 with sub-PRB allocation for E-UTRA highest channel edge > 834 MHz and β€ 849 MHz Table 6.2.4E-22: A-MPR for "NS_16" for Cat-M2 with sub-PRB allocation for E-UTRA lowest channel edge > 807 MHz and β€ 812 MHz Table 6.2.4E-23: A-MPR for βNS_07β for Cat-M1 with sub-PRB allocation Table 6.2.4E-24: A-MPR for βNS_38β for Cat-M2 with sub-PRB allocation for E-UTRA lowest channel edge > 1427 MHz and β€ 1447 MHz Table 6.2.4E-25: A-MPR for βNS_56β for Cat-M1 allocation Table 6.2.4E-26: A-MPR for βNS_56β for Cat-M1 allocation with subPRB Table 6.2.4E-27: A-MPR for βNS_56β for Cat-M2 allocation with subPRB Table 6.2.4E-28: A-MPR for βNS_27β for Cat-M1 allocation with subPRB allocation No other A-MPR requirement than those specified in table 6.2.4E-1, table 6.2.4E-2, table 6.2.4E-6 and table 6.2.4E-7 applies to category M1 and M2 UE. | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.2.4E |
2,924 | 5.5.3.7 Charging Principles for Roaming Architecture for Voice over IMS with Local Breakout | The Roaming Architecture for Voice over IMS with Local Breakout is described in the TS 23.228[ IP Multimedia Subsystem (IMS); Stage 2 ] [209]. The roaming charging procedures for Roaming Architecture for Voice over IMS with Local Breakout shall be based on the existing principles described in clauses 5.5.3.1, 5.5.3.2 and 5.5.3.4. Additionally, roaming charging data for Roaming Architecture for Voice over IMS with Local Breakout shall provide the following information: - Indicator whether loopback or home routing has been applied - Final destination for the session when loopback is applied - Indicator whether OMR (Optimal Media Routing) has been applied - Charging data created by VPLMN after the loopback must be assigned to a user identified by the P-Asserted-Identity. NOTE: this is different from charging data collected for interconnection accounting, where identity of served user is optional and not relevant for post-processing. Details are described in the TS 32.260[ Telecommunication management;Charging management;IP Multimedia Subsystem (IMS) charging ] [20] | 3GPP TS 32.240 | Telecommunication management; Charging management; Charging architecture and principles | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 5.5.3.7 |
2,925 | B.4 Example implementation of Non-Terrestrial Networks | The following figure illustrates an example implementation of a Non-Terrestrial Network for transparent NTN payload: Figure B.4-1: NTN based NG-RAN The gNB depicted in Figure B.4-1 may be subdivided into non-NTN infrastructure gNB functions and the NTN Service Link provisioning system. The NTN infrastructure may be thought of being subdivided into the NTN Service Link provisioning system and the NTN Control function. The NTN Service Link provisioning system may consist of one or more NTN payloads and NTN Gateways. The NTN payload is embarked on a spaceborne (or airborne) vehicle, providing a structure, power, commanding, telemetry, attitude control for the satellite (resp. HAPS) and possibly an appropriate thermal environment, radiation shielding. The NTN Service Link provisioning system maps the NR-Uu radio protocol over radio resources of the NTN infrastructure (e.g. beams, channels, Tx power). The NTN control function controls the spaceborne (or airborne) vehicles as well as the radio resources of the NTN infrastructure (NTN payload(s) & NTN Gateway(s)). It provides control data, e.g. Ephemeris, to the non-NTN infrastructure gNB functions of the gNB. Provision of NTN control data to the gNB is out of 3GPP scope. NOTE: The transport of NR-Uu protocol between the NTN Service Link provisioning system and the non-NTN infrastructure gNB functions is out of 3GPP scope. At least the following NTN related parameters are expected to be provided by O&M to the gNB for its operation: a) Earth-fixed beams: for each beam provided by a given NTN-payload: - The Cell identifier (NG and Uu) mapped to the beam; - The Cell's reference location (e.g. cell's center and range). b) Quasi-Earth-fixed: for each beam provided by a given NTN payload: - The Cell identifier (NG and Uu) and time window mapped to a beam; - The Cell's/beam's reference location (e.g. cell's center and range); - The time window of the successive switch overs (feeder link, service link); - The identifier and time window of all serving satellites (resp. HAPS) and NTN Gateways. c) Earth moving beams: for each beam provided by a given NTN payload: - The Uu Cell identifier mapped to a beam and mapping information to fixed geographical areas reported on NG, including information about the beams direction and motion of the beam's foot print on Earth; - Its elevation wrt NTN payload; - Schedule of successive serving NTN Gateways/gNBs; - Schedule of successive switch overs (feeder link, service link). | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | B.4 |
2,926 | 6.8.5.2 GSM security context | Handover from GSM BSS to UTRAN with a GSM security context is possible for a GSM subscriber with a R99+ ME or for a UMTS subscriber with a R99+ ME when the initial MSC/VLR is R98-. At the network side, two cases are distinguished: a) In case of a handover to a UTRAN controlled by the same MSC/VLR, UMTS cipher/integrity keys CK and IK are derived from the 64-bit GSM cipher key Kc used before the intersystem handover (using the conversion functions c4 and c5) and sent to the target RNC. In case of subsequent handover in a non-anchor R99+ MSC/VLR, a 64-bit GSM cipher key Kc is received for a UMTS subscriber if the anchor MSC/VLR is R98-. b) In case of a handover to a UTRAN controlled by another MSC/VLR, the initial MSC/VLR (R99+ or R98-) sends the 64-bit GSM cipher key Kc used before the intersystem handover to the new MSC/VLR controlling the target RNC. That MSC/VLR derives UMTS cipher/integrity keys CK and IK which are then forwarded to the target RNC. The initial MSC/VLR remains the anchor point for throughout the service. At the user side, in either case, the ME derives the UMTS cipher/integrity keys CK and IK from the 64-bit GSM cipher key Kc (using the conversion functions c4 and c5) which was used before the intersystem handover and applies them. | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | 6.8.5.2 |
2,927 | 8.11 MSISDN | MSISDN is transferred via GTP tunnels. The sending entity copies the value part of the MSISDN into the Value field of the MSISDN IE. MSISDN is defined in 3GPP TS 23.003[ Numbering, addressing and identification ] [2]. Figure 8.11-1: MSISDN Octets 5 to (n+4) represent the MSISDN value is in international number format as described in ITU-T Rec E.164 [25] and 3GPP TS 29.002[ Mobile Application Part (MAP) specification ] [41]. MSISDN value contains only the actual MSISDN number (does not contain the "nature of address indicator" octet, which indicates "international number" as in 3GPP TS 29.002[ Mobile Application Part (MAP) specification ] [41]) and is encoded as TBCD digits, i.e. digits from 0 through 9 are encoded "0000" to "1001". When there is an odd number of digits, bits 8 to 5 of the last octet are encoded with the filler "1111". | 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.11 |
2,928 | 20.3.4 Public User Identity | The Public User Identity shall take the form of a SIP URI (see IETF RFC 3261 [26]), and shall have the form "sip:username@domain". The MSC Server enhanced for ICS shall derive the Public User Identity from the subscriber's IMSI. The Public User Identity shall consist of the string "sip:" appended with a username and domain portion equal to the IMSI derived Private User Identity described in clause 20.3.3. An example using the same example IMSI from clause 20.3.3 can be found below: EXAMPLE: "sip:[email protected]". | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 20.3.4 |
2,929 | 8.137 Monitoring Event Extension Information | The Monitoring Event Information contains the monitoring event parameters that are necessary to transfer over the S3/S16/S10 interface. The Monitoring Event Extension Information is coded as depicted in Figure 8.137-1. Figure 8.137-1: Monitoring Event Extension Information The SCEF Reference ID, the SCEF ID and the SCEF Reference ID Ext shall be encoded as specified in clause 8.4.4, 8.4.5 and 8.4.82 of 3GPP TS 29.336[ Home Subscriber Server (HSS) diameter interfaces for interworking with packet data networks and applications ] [69]. The SCEF ID Length indicates the length of the SCEF ID in octets. The following bits within Octet 5 indicate: - Bit 1 β LRTP (Remaining Minimum Periodic Location Reporting Time Present): This flag is used to indicate that Remaining Minimum Periodic Location Reporting Time shall be present. - Bit 2 β SRIE (SCEF Reference Id Extension): if this flag is set to "1", the SCEF Reference ID Ext field shall be present to contain the 64-bit SCEF Reference ID Ext for the event. In this case, the receiver shall ignore the SCEF Reference ID received in octets 5 to 8. NOTE: The sender can set any value for SCEF Reference ID if the SCEF Reference ID Ext is included. - Bit 3-8 Spare. Remaining Minimum Periodic Location Reporting Time indicates the current value of the timer for minimum periodic location reporting. It shall be encoded as specified in clause 8.4.29 of 3GPP TS 29.336[ Home Subscriber Server (HSS) diameter interfaces for interworking with packet data networks and applications ] [69]. The target MME/SGSN shall start the timer with the Remaining Minimum Periodic Location Reporting Time to continue detecting the location change. If the timer expires, the target MME/SGSN shall restart the timer with the value of the Periodic-Time AVP within the Monitoring-Event-Configuration AVP provided by the HSS. | 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.137 |
2,930 | 5.3.3.1a Conditions for establishing RRC Connection for NR sidelink communication/discovery/V2X sidelink communication | For NR sidelink communication/discovery, an RRC connection establishment is initiated only in the following cases: 1> if configured by upper layers to transmit NR sidelink communication and related data is available for transmission: 2> if the frequency on which the UE is configured to transmit NR sidelink communication is included in sl-FreqInfoList/sl-FreqInfoListSizeExt within SIB12 provided by the cell on which the UE camps; and if the valid version of SIB12 does not include sl-TxPoolSelectedNormal for the concerned frequency; 1> if configured by upper layers to transmit NR sidelink discovery and related data is available for transmission: 2> if the UE is configured by upper layers to transmit NR sidelink L2 U2N relay discovery messages and sl-L2U2N-Relay is included in SIB12; or 2> if the UE is configured by upper layers to transmit NR sidelink L3 U2N relay discovery messages and sl-L3U2N-RelayDiscovery is included in SIB12; or 2> if the UE is configured by upper layers to transmit NR sidelink non-relay discovery messages and sl-NonRelayDiscovery is included in SIB12: 3> if the frequency on which the UE is configured to transmit NR sidelink discovery is included in sl-FreqInfoList/sl-FreqInfoListSizeExt within SIB12 provided by the cell on which the UE camps; and if the valid version of SIB12 includes neither sl-DiscTxPoolSelected nor sl-TxPoolSelectedNormal for the concerned frequency; For L2 U2N Relay UE in RRC_IDLE, an RRC connection establishment is initiated in the following cases: 1> if any message is received from a L2 U2N Remote UE via SL-RLC0 as specified in 9.1.1.4 or SL-RLC1 as specified in 9.2.4; or 1> if RemoteUEInformationSidelink containing the connectionForMP is received from a L2 U2N Remote UE as specified in 5.8.9.8.3; For V2X sidelink communication, an RRC connection is initiated only when the conditions specified for V2X sidelink communication in clause 5.3.3.1a of TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10] are met. NOTE: Upper layers initiate an RRC connection (except if the RRC connection is initiated at the L2 U2N Relay UE upon reception of a message from a L2 U2N Remote UE via SL-RLC0 or SL-RLC1). The interaction with NAS is left to UE implementation. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.3.1a |
2,931 | 4.22.3.3 Home-routed, the UE registered to the same VPLMN over both access | In the case of home-routed roaming, when the UE is registered to the same VPLMN over 3GPP access and non-3GPP access, the procedure for establishing a MA PDU Session when the VPLMN is ATSSS capable and the UE requests a single-access PDU Session but no policy in the UE and no local restrictions mandate a single access, is the same with the procedure specified in clause 4.22.2.2.1, with the following clarifications and modifications: - In step 1, the UE sets Request Type to initial request and it may include an "MA PDU Network-Upgrade Allowed" indication in UL NAS Transport message and its ATSSS Capabilities as defined in clause 5.32.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] in PDU Session Establishment Request message. - In step 2, if the AMF receives the "MA PDU Network-Upgrade Allowed" indication, the AMF may select a V-SMF and a H-SMF that support MA PDU sessions. If the AMF determines that the requested S-NSSAI is not allowed on both accesses, the AMF shall not forward "MA PDU Network-Upgrade Allowed" indication to the V-SMF. - In step 3, the AMF sends the "MA PDU Network-Upgrade Allowed" indication, if received from the UE. If the AMF sends the "MA PDU Network-Upgrade Allowed" indication to V-SMF, it shall also indicate to V-SMF whether the UE is registered over both accesses. - In step 5, two DL N9 tunnel CN info and two UL N3 tunnel CN info are allocated by the V-SMF or by the V-UPF. Additionally, the V-SMF indicates to H-SMF the relationship between the DL N9 tunnel CN info and the access type. If the single CN Tunnel is established by the H-SMF, the DL N9 tunnel CN info binding to the access over which the NAS message is received is to be used. - In step 6, the V-SMF provides the "MA PDU Network-Upgrade Allowed" indication, if received from AMF, together with an indication whether the UE is registered over both accesses. - After step 6, if the H-SMF receives the "MA PDU Network-Upgrade Allowed" indication, the H-SMF may decide to convert the single-access PDU Session requested by the UE into a MA PDU Session, if dynamic PCC is not to be used. The H-SMF may take this decision based on local operator policy, subscription data indicating whether the MA PDU session is allowed or not and/or other conditions, which are not specified in the present document. If the H-SMF receives ATSSS Capabilities from the UE but does not receive "MA PDU Network-Upgrade Allowed" indication from the AMF, the H-SMF shall not convert the single-access PDU Session requested by the UE into a MA PDU Session. - In step 9, if dynamic PCC is to be used for the MA PDU Session, the H-SMF sends an "MA PDU Network-Upgrade Allowed" indication instead of "MA PDU Request" indication to H-PCF in the SM Policy Control Create message if the MA PDU session is allowed based on the subscription data. The H-SMF also provides the ATSSS Capabilities of the MA PDU session. The H-PCF decides whether the single-access PDU Session can be converted into an MA PDU session or not based on operator policy and subscription data. - In step 13, the H-SMF sends "MA PDU session Accepted" indication to V-SMF in the Nsmf_PDUSession_Create Response message. - In step 14, the V-SMF includes the "MA PDU session Accepted" indication in the Namf_Communication_N1N2MessageTransfer message to the AMF. The AMF mark this PDU session as MA PDU session based on the received "MA PDU session Accepted" indication. - In step 16, the UE receives a PDU Session Establishment Accept message, which includes ATSSS rules and indicates to UE that the requested single-access PDU session was established as a MA PDU Session. - After step 18, two N9 tunnels between the H-UPF and the V-UPF as well as two N3 tunnels between the V-UPF and 5G-AN are established, or, if the H-UPF is connected to two different V-UPFs, the H-UPF has one N9 tunnel with each V-UPF. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.22.3.3 |
2,932 | 6.8.3 Distribution and use of authentication data between VLRs/SGSNs | The distribution of authentication data (unused authentication vectors and/or current security context data) between R99+ VLRs/SGSNs of the same service network domain is performed according to chapter 6.3.4. The following four cases are distinguished related to the distribution of authentication data between VLRs/SGSNs (of the same or different releases). Conditions for the distribution of such data and for its use when received at VLRn/SGSNn are indicated for each case: a) R99+ VLR/SGSN to R99+ VLR/SGSN UMTS and GSM authentication vectors can be distributed between R99+ VLRs/SGSNs. Note that originally all authentication vectors (quintets for UMTS subscribers and triplets for GSM subscribers) are provided by the HLR/AuC. Current security context data can be distributed between R99+ VLRs/SGSNs. VLRn/SGSNn shall not use current security context data received from VLRo/SGSNo to authenticate the subscriber using local authentication in the following cases: i) Security context to be established at VLRn/SGSNn requires a different set of keys than the one currently in use at VLRo/SGSNo. This change of security context is caused by a change of ME release (Rβ99 ME Rβ98 ME) when the user registers at VLRn/SGSNn. ii) Authentication data from VLRo includes 64-bit Kc+CKSN but no unused AVs and the subscriber has a Rβ99 ME (under GSM BSS or UTRAN). In this situation, VLRn have no indication of whether the subscriber is GSM or UMTS and it is not able to decide whether the 64-bit Kc received can be used (in case the subscriber were a GSM subscriber). In these two cases, received current security context data shall be discarded and a new AKA procedure shall be performed. b) R98- VLR/SGSN to R98- VLR/SGSN Only triplets can be distributed between R98- VLRs/SGSNs. Note that originally for GSM subscribers, triplets are generated by HLR/AuC and for UMTS subscribers, they are derived from UMTS authentication vectors by R99+ HLR/AuC. UMTS AKA is not supported and only GSM security context can be established by a R98- VLR/SGSN. R98- VLRs are not prepared to distribute current security context data. Since only GSM security context can be established under R98- SGSNs, security context data can be distributed and used between R98- SGSNs. c) R99+ VLR/SGSN to R98- VLR/SGSN R99+ VLR/SGSN can distribute to a new R98- VLR/SGSN triplets originally provided by HLR/AuC for GSM subscribers or can derive triplets from stored quintets originally provided by R99+ HLR/AuC for UMTS subscribers. Note that R98- VLR/SGSN can only establish GSM security context. R99+ VLRs shall not distribute current security context data to R98- VLRs. Since R98- SGSNs are only prepared to handle GSM security context data, R99+ SGSNs shall only distribute GSM security context data (64-bit Kc, CKSN) to R98- SGSNs. d) R98- VLR/SGSN to R99+ VLR/SGSN. In order to not establish a GSM security context for a UMTS subscriber, triplets provided by a R98- VLR/SGSN can only be used by a R99+ VLR/SGSN to establish a GSM security context under GSM-BSS with a R98- ME. In all other cases, R99+ VLR/SGSN shall request fresh AVs (either triplets or quintets) to HE. In the event, the R99+ VLR/SGSN receives quintets, it shall discard the triplets provided by the R98- VLR/SGSN. R98- VLRs are not prepared to distribute current security context data. R98- SGSNs can distribute GSM security context data only. The use of this information at R99+ SGSNn shall be performed according to the conditions stated in a). | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | 6.8.3 |
2,933 | 6.9.2.3.4 UE handling | The UE behaviour is the same regardless if the handover is intra-gNB-CU, intra ng-eNB, Xn, or N2 with the exception that during intra-gNB-CU handover, the UE may retain the same key based on an indication from the gNB. The UE behaviour is also same in case of conditional handover, as specified in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [52], i.e., the UE shall use the parameters of the selected target cell in KNG-RAN* derivations. If the UE also receives a NASC (NAS Container) in the HO Command message, the UE shall update its NAS security context as follows: NOTE 1: The purpose of this NASC could be compared to a NAS SMC message. - The UE shall verify the freshness of the downlink NAS COUNT in the NASC. - If the NASC indicates a new KAMF has been calculated (i.e., K_AMF_change_flag is one), - The UE shall compute the horizontally derived KAMF using the KAMF from the current 5G NAS security context identified by the ngKSI included in the NASC and the downlink NAS COUNT in the NASC, as specified in Annex A.13. - The UE shall assign the ngKSI included in the NASC to the ngKSI of the new derived KAMF. The UE shall further configure NAS security based on the horizontally derived KAMF and the selected NAS security algorithms in the NASC. - The UE shall further verify the NAS MAC in the NASC as described in Clause 6.9.2.3.3 and if the verification is successful, the UE shall further set the NAS COUNTs to zero. - If KAMF change is not indicated, - If the verification is successful, the UE shall configure the NAS security based on the parameters included in the NASC but shall not set the NAS COUNTs to zero. - The UE shall verify the NAS MAC in the NASC. - The UE shall further set the downlink NAS COUNT value of the currently active NAS security context to the received downlink NAS COUNT value in the NASC. If verification of the NASC fails, the UE shall abort the handover procedure. Furthermore, the UE shall discard the new NAS security context if it was derived and continue to use the existing NAS and AS security contexts. If keySetChangeIndicator in the HO command is true - If the HO Command message contained a NASC parameter with the K_AMF_change_flag set to one: - The UE shall use the horizontally derived KAMF and the NAS COUNT value of 232-1 in the derivation of the temporary KgNB. The UE shall further process this temporary key as described in subclause 6.9.4.4. - Else: - The UE handling related to key derivation shall be done as defined in clause 6.9.4.4. Else - If the NCC value the UE received in the HO Command message from target ng-eNB/gNB via source ng-eNB/gNB is equal to the NCC value associated with the currently active KgNB/KeNB, the UE shall derive the KNG-RAN* from the currently active KgNB/KeNB and the target PCI and its frequency ARFCN-DL/EARFCN-DL using the function defined in Annex A.11 and A.12. - If the UE received an NCC value that was different from the NCC associated with the currently active KgNB/KeNB, the UE shall first synchronize the locally kept NH parameter by computing the function defined in Annex A.10 iteratively (and increasing the NCC value until it matches the NCC value received from the source ng-eNB/gNB via the HO command message. When the NCC values match, the UE shall compute the KNG-RAN* from the synchronized NH parameter and the target PCI and its frequency ARFCN-DL/EARFCN-DL using the function defined in Annex A.11 and A.12. The UE shall use the KNG-RAN* as the KgNB when communicating with the target gNB and as the KeNB when communicating with the target ng-eNB. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.9.2.3.4 |
2,934 | 6.3 5G Edge computing services charging | Edge Computing support in 5GS is defined in TS 23.501[ System architecture for the 5G System (5GS) ] [215], TS 23.502[ Procedures for the 5G System (5GS) ] [214] and TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [217]. The architecture for enabling Edge Applications is specified in TS 23.558[ Architecture for enabling Edge Applications ] [218]. The charging principles for the Edge Computing domain are specified in TS 32.257[ Telecommunication management; Charging management; Edge computing domain charging ] [17] and TS 32.255[ Telecommunication management; Charging management; 5G data connectivity domain charging; Stage 2 ] [15]. The architecture of Edge Computing in Local Breakout roaming scenario and charging for Edge Computing in local breakout follows the principles in clause 5.5.3.9 are specified in TS.23.501[ System architecture for the 5G System (5GS) ] [215]. | 3GPP TS 32.240 | Telecommunication management; Charging management; Charging architecture and principles | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 6.3 |
2,935 | 5.6.1.3 Reception of the UECapabilityEnquiry by the UE | The UE shall set the contents of UECapabilityInformation message as follows: 1> if the ue-CapabilityRAT-RequestList contains a UE-CapabilityRAT-Request with rat-Type set to nr: 2> include in the ue-CapabilityRAT-ContainerList a UE-CapabilityRAT-Container of the type UE-NR-Capability and with the rat-Type set to nr; 2> include the supportedBandCombinationList, featureSets and featureSetCombinations as specified in clause 5.6.1.4; 1> if the ue-CapabilityRAT-RequestList contains a UE-CapabilityRAT-Request with rat-Type set to eutra-nr: 2> if the UE supports (NG)EN-DC or NE-DC: 3> include in the ue-CapabilityRAT-ContainerList a UE-CapabilityRAT-Container of the type UE-MRDC-Capability and with the rat-Type set to eutra-nr; 3> include the supportedBandCombinationList and featureSetCombinations as specified in clause 5.6.1.4; 1> if the ue-CapabilityRAT-RequestList contains a UE-CapabilityRAT-Request with rat-Type set to eutra: 2> if the UE supports E-UTRA: 3> include in the ue-CapabilityRAT-ContainerList a ue-CapabilityRAT-Container of the type UE-EUTRA-Capability associated with the terrestrial network and with the rat-Type set to eutra as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10], clause 5.6.3.3, according to the capabilityRequestFilter, if received; 1> if the ue-CapabilityRAT-RequestList contains a UE-CapabilityRAT-Request with rat-Type set to utra-fdd: 2> if the UE supports UTRA-FDD: 3> include the UE radio access capabilities for UTRA-FDD within a ue-CapabilityRAT-Container and with the rat-Type set to utra-fdd; 1> if the RRC message segmentation is enabled based on the field rrc-SegAllowed received, and the encoded RRC message is larger than the maximum supported size of a PDCP SDU specified in TS 38.323[ NR; Packet Data Convergence Protocol (PDCP) specification ] [5]: 2> initiate the UL message segment transfer procedure as specified in clause 5.7.7; 1> else: 2> submit the UECapabilityInformation message to lower layers for transmission, upon which the procedure ends. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.6.1.3 |
2,936 | 6.45.1 Overview | In the roaming ecosystem, a roaming services provider provides the technical and commercial means to facilitate the deployment and operation of roaming services between a client operator and a set of selected connected operators. The roaming services provider handles the technical implementation of the roaming relations in a scalable and operationally efficient way. With a roaming services provider present in the roaming ecosystem, operators can choose not to establish a bilateral direct agreement with specific operators. A trusted relation exists between the involved operator and the roaming services provider. Roaming services providers, according to their role and responsibilities, assume financial and technical liability to apply all necessary controls and access to all communications. Among other functionalities, a roaming services provider needs to: β’ Process identifiers and potentially other information transmitted in signalling messages between PLMNs in a secure manner. β’ Be able to modify, add or delete information that is relevant to their role, respecting what is contractually agreed in service level agreements (SLAs) and enforced technically. β’ Isolate the individual operator signalling flows from each other β’ Report on the detection of and mitigation of security breaches. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.45.1 |
2,937 | 4.3.1.6.2 Attempted executions of outgoing handover to the cells outside the RN per handover cause | This measurement provides the number of attempted executions of outgoing handovers to the cells outside the RN per handover cause. CC. Transmission of the RRC ConnectionReconfiguration message by the RN to UE triggering the handover from the RN to the cell outside the RN, indicatingthe attempt of an outgoing handover to the cell outside the RN(see TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8]). The sum of all supported per cause measurements shall equal the total number of attempted executions of outgoing handovers to the cell outside the RN. Each RRCConnectionReconfiguration message transimtted is added to the relevant per handover cause measurement, the possible causes are included in TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [9]. In case only a subset of per cause measurements is supported, a sum subcounter will be provided first. Each measurement is an integer value. The number of measurements is equal to the number of causes supported plus a possible sum value identified by the .sum suffix. HO.OutRNOutAtt.Cause where Cause identifies the cause for handover EUtranCellFDD EUtranCellTDD Valid for packet switched traffic EPS | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.3.1.6.2 |
2,938 | 5.4.13 Support of discontinuous network coverage for satellite access 5.4.13.0 General | The present clause 5.4.13 provides optional enhancements to support discontinuous coverage: - Mobility management and power saving optimization, see clause 5.4.13.1; and - Coverage availability information provisioning to the UE, see clause 5.4.13.2; and - Coverage availability information provisioning to the AMF, see clause 5.4.13.3; and - Paging, see clause 5.4.13.4; and - Overload control, see clause 5.4.13.5. NOTE: In this Release, there is no specified support for discontinuous coverage over NR in RAN specifications. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.4.13 |
2,939 | 4.2.7 Reference points | The 5G System Architecture contains the following reference points: N1: Reference point between the UE and the AMF. N2: Reference point between the (R)AN and the AMF. N3: Reference point between the (R)AN and the UPF. N4: Reference point between the SMF and the UPF. N6: Reference point between the UPF and a Data Network. N9: Reference point between two UPFs. The following reference points show the interactions that exist between the NF services in the NFs. These reference points are realized by corresponding NF service-based interfaces and by specifying the identified consumer and producer NF service as well as their interaction in order to realize a particular system procedure. N5: Reference point between the PCF and an AF or TSN AF. N7: Reference point between the SMF and the PCF. N8: Reference point between the UDM and the AMF. N10: Reference point between the UDM and the SMF. N11: Reference point between the AMF and the SMF. N12: Reference point between AMF and AUSF. N13: Reference point between the UDM and Authentication Server function the AUSF. N14: Reference point between two AMFs. N15: Reference point between the PCF and the AMF in the case of non-roaming scenario, PCF in the visited network and AMF in the case of roaming scenario. N16: Reference point between two SMFs, (in roaming case between SMF in the visited network and the SMF in the home network). N16a: Reference point between SMF and I-SMF. N17: Reference point between AMF and 5G-EIR. N18: Reference point between any NF and UDSF. N19: Reference point between two PSA UPFs for 5G LAN-type service. N22: Reference point between AMF and NSSF. N23: Reference point between PCF and NWDAF. N24: Reference point between the PCF in the visited network and the PCF in the home network. N27: Reference point between NRF in the visited network and the NRF in the home network. N28: Reference point between PCF and CHF. N29: Reference point between NEF and SMF. N30: Reference point between PCF and NEF. NOTE 1: The functionality of N28 and N29 and N30 reference points are defined in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]. N31: Reference point between the NSSF in the visited network and the NSSF in the home network. NOTE 2: In some cases, a couple of NFs may need to be associated with each other to serve a UE. N32: Reference point between a SEPP in one PLMN or SNPN and a SEPP in another PLMN or SNPN; or between a SEPP in a SNPN and a SEPP in a CH/DCS, where the CH/DCS contains a UDM/AUSF. NOTE 3: The functionality of N32 reference point is defined in TS 33.501[ Security architecture and procedures for 5G System ] [29]. N33: Reference point between NEF and AF. N34: Reference point between NSSF and NWDAF. N35: Reference point between UDM and UDR. N36: Reference point between PCF and UDR. N37: Reference point between NEF and UDR. N38: Reference point between I-SMFs and between V-SMFs. N40: Reference point between SMF and the CHF. N41: Reference point between AMF and CHF in HPLMN. N42: Reference point between AMF and CHF in VPLMN. NOTE 4: The functionality of N40, N41 and N42 reference points are defined in TS 32.240[ Telecommunication management; Charging management; Charging architecture and principles ] [41]. N43: Reference point between PCFs. NOTE 5: The functionality of N43 reference point is defined in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]. NOTE 6: The reference points from N44 up to and including N49 are reserved for allocation and definition in TS 32.240[ Telecommunication management; Charging management; Charging architecture and principles ] [41]. N50: Reference point between AMF and the CBCF. N51: Reference point between AMF and NEF. N52: Reference point between NEF and UDM. N55: Reference point between AMF and the UCMF. N56: Reference point between NEF and the UCMF. N57: Reference point between AF and the UCMF. NOTE 7: The Public Warning System functionality of N50 reference point is defined in TS 23.041[ Technical realization of Cell Broadcast Service (CBS) ] [46]. N58: Reference point between AMF and the NSSAAF. N59: Reference point between UDM and the NSSAAF. N60: Reference point between AUSF and NSWOF. NOTE 8: The functionality of N60 reference point is defined in TS 33.501[ Security architecture and procedures for 5G System ] [29]. N80: Reference point between AMF and NSACF. N81: Reference point between SMF and NSACF. N82: Reference point between NSACF and NEF. N83: Reference point between AUSF and NSSAAF. N84: Reference point between TSCTSF and PCF. N85: Reference point between TSCTSF and NEF. N86: Reference point between TSCTSF and AF. N87: Reference point between TSCTSF and UDM. N88: Reference point between SMF and EASDF. N89: Reference point between TSCTSF and AMF. N96: Reference point between TSCTSF and NRF. N97: Reference point between two NSACFs in different PLMNs. N99: Reference point between two NSACFs within the same PLMN. NOTE 9: The reference points from N90 up to and including N95 are reserved for allocation and definition in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]. NOTE 10: The reference points from N100 up to and including N109 are reserved for allocation and definition in TS 32.240[ Telecommunication management; Charging management; Charging architecture and principles ] [41]. The reference points to support SMS over NAS are listed in clause 4.4.2.2. The reference points to support Location Services are listed in TS 23.273[ 5G System (5GS) Location Services (LCS); Stage 2 ] [87]. The reference points to support SBA in IMS (N5, N70 and N71) are described in TS 23.228[ IP Multimedia Subsystem (IMS); Stage 2 ] [15]. The reference points to support AKMA (N61, N62 and N63) are described in TS 33.535[ Authentication and Key Management for Applications (AKMA) based on 3GPP credentials in the 5G System (5GS) ] [124]. The reference points to support 5G ProSe are described in TS 23.304[ Proximity based Services (ProSe) in the 5G System (5GS) ] [128]. The reference points to support 5G multicast-broadcast services are described in TS 23.247[ Architectural enhancements for 5G multicast-broadcast services ] [129]. The reference points to Support Uncrewed Aerial Systems (UAS) connectivity, identification and tracking are described in TS 23.256[ Support of Uncrewed Aerial Systems (UAS) connectivity, identification and tracking; Stage 2 ] [136]. The reference points to support SBA in GBA and GBA push (N65, N66, N67 and N68) are described in TS 33.220[ Generic Authentication Architecture (GAA); Generic Bootstrapping Architecture (GBA) ] [140] and TS 33.223[ Generic Authentication Architecture (GAA); Generic Bootstrapping Architecture (GBA) Push function ] [141]. The reference points to support SMS delivery using SBA are described in TS 23.540[ 5G System: Technical realization of Service Based Short Message Service; Stage 2 ] [142]. The reference points to support Ranging based services and Sidelink Positioning are described in TS 23.586[ Architectural Enhancements to support Ranging based services and Sidelink Positioning ] [180]. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.2.7 |
2,940 | 8.3.1.1C Enhanced Performance Requirement Type B β Single-layer Spatial Multiplexing with TM9 interference model | The requirements are specified in Table 8.3.1.1C-2, with the addition of the parameters in Table 8.3.1.1C-1 and the downlink physical channel setup according to Annex C.3.2. The purpose of these tests is to verify closed loop rank one performance on one of the antenna ports 7, 8 without a simultaneous transmission on the other antenna port in the serving cell when the PDSCH transmission in the serving cell is interfered by PDSCH of two interfering cells applying transmission mode 9 interference model defined in clause B.6.4. In 8.3.1.1C-1, Cell 1 is the serving cell, and Cell 2, 3 are interfering cells. The downlink physical channel setup is according to Annex C.3.2 for each of Cell 1, Cell 2 and Cell 3, respectively. Table 8.3.1.1C-1: Test Parameters for Testing CDM-multiplexed DM RS (Single-layer) with TM9 interference model Table 8.3.1.1C-2: Minimum Performance for Enhanced Performance Requirement Type B, CDM-multiplexed DM RS with TM9 interference model | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.3.1.1C |
2,941 | 5.44.3.3 Non-3GPP QoS Assistance Information | QoS experienced by PINEs connected behind a PEGC depends on the end-to-end path between a PINE and the application server, i.e. depends on the QoS differentiation in both the 3GPP network and the non-3GPP network attached to the PEGC. Non-3GPP QoS Assistance Information (N3QAI) enables the PEGC to perform QoS differentiation for the PINEs in the non-3GPP network behind the PEGC. During PDU session establishment and PDU session modification, if the SMF provides the PEGC with QoS flow descriptions, the SMF may additionally signal N3QAI for each QoS flow to the PEGC based on the (DNN, S-NSSAI) combination of the PDU Session. Based on the N3QAI together with QoS rule information, the PEGC may reserve resources in the non-3GPP network. N3QAI consists of the following QoS information: QoS characteristics, GFBR/MFBR, Maximum Packet Loss Rate, Notification Control. How to enforce QoS based on the N3QAI in the non-3GPP network is considered outside the scope of 3GPP. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.44.3.3 |
2,942 | 5.2.1.11 Speech Codec Selection | For speech calls, a mobile station implementing this version of the protocol shall indicate all codecs that it supports for UTRAN in the Supported Codec List information element. Codecs for GERAN shall be indicated in the Bearer Capability information element, if this information element is included. Additionally, if the mobile station supports codecs for GERAN and UTRAN, it shall indicate the codecs for GERAN also in the Supported Codec List information element. If the network does not receive a Supported Codec List information element then for speech calls in UTRAN it shall select the default UMTS speech codec. For speech calls in GERAN, if the network does not receive a Supported Codec List information element nor a Bearer Capability information element, the network shall select GSM full rate speech version 1. The network shall determine the default UMTS speech codec by the following: i) If no GSM Speech Version codepoints are received in the Supported Codec List IE or in octet 3a etc. of the Bearer Capabilities IE then a "UMTS only" terminal is assumed and the default UMTS speech codec shall be UMTS_AMR. ii) If at least one GSM Speech Version codepoint is received in the Supported Codec List IE or in octet 3a etc. of the Bearer Capabilities IE then the ME supports GSM and UMTS and the default UMTS speech codec shall be UMTS_AMR_2. NOTE 1: In case (ii), if the call is set up in A/Gb or GERAN Iu mode by a R99 ME, call control in the core network may treat the ME as a "GSM only" ME. The default UMTS speech codec will only become relevant when an intersystem handover to UTRAN Iu mode is initiated by the radio access network, and can be determined when this procedure is started. If the Supported Codec List IE is received, then the network shall use this list to select the codec for Iu mode and indicate the selected codec to the ME via RANAP and RRC protocol in the NAS Synchronisation Indicator IE. See 3GPP TS 25.413[ UTRAN Iu interface Radio Access Network Application Part (RANAP) signalling ] [19c], 3GPP TS 25.331[ None ] [23c] and 3GPP TS 44.118[ None ] [111]. The NAS Synchronisation Indicator IE shall be coded as the 4 least significant bits of the selected codec type (CoID) defined in 3GPP TS 26.103[ Speech codec list for GSM and UMTS ] [83], subclause 6.3. The network shall determine the preference for the selected codec type; codec type prioritisation is not provided by the ME. The ME shall activate the codec type received in the NAS Synchronisation Indicator IE. If the mobile station does not receive the NAS Synchronisation Indicator IE (RRC protocol) - during setup of a speech call; - during inter-system handover of a speech call from A/Gb or GERAN Iu mode to UTRAN Iu mode; - during an in-call modification from data to speech; - during a SRVCC handover to UTRAN Iu mode; or - during a 5G-SRVCC handover from NG-RAN to UTRAN Iu mode, then it shall select the UMTS_AMR_2 speech codec. NOTE 2: If the network does not support UMTS_AMR_2, it may activate the UMTS_AMR codec and indicate to the mobile station that it shall select UMTS_AMR_2. According to 3GPP TS 26.103[ Speech codec list for GSM and UMTS ] [83], subclause 5.4, no interworking problem will occur in this case. If the mobile station has selected a speech codec for UTRAN Iu mode, it shall keep this codec until - a new codec is requested by the network by sending a NAS Synchronisation Indicator IE (RRC protocol); - a new codec is requested by the network during inter-system handover from UTRAN Iu mode to A/Gb or GERAN Iu mode; or - an in-call modification from speech to data is performed. For adaptive multirate codec types no indication of subsets of modes is supported in this protocol, from the mobile station or to the mobile station. It is a pre-condition that the support of such codec types by the mobile station implicitly includes all modes defined for that codec type. | 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.11 |
2,943 | 10.5.4.7 Called party BCD number | The purpose of the called party BCD number information element is to identify the called party. The called party BCD number information element is coded as shown in figure 10.5.91/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.118/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The called party BCD number is a type 4 information element with a minimum length of 3 octets and a maximum length of 43 octets. For PCS 1900 the maximum length is 19 octets. Figure 10.5.91/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Called party BCD number information element NOTE 1: The number digit(s) in octet 4 precedes the digit(s) in octet 5 etc. The number digit which would be entered first is located in octet 4, bits 1 to 4. NOTE 2: If the called party BCD number contains an odd number of digits, bits 5 to 8 of the last octet shall be filled with an end mark coded as "1111". Since the information element must contain the complete called party BCD number there is no need for an additional complete indication. Table 10.5.118/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Called party BCD number NOTE 1: For the definition of "number" see ITU-T Recommendation I.330 [48] and 3GPP TS 23.003[ Numbering, addressing and identification ] [10]. NOTE 2: The type of number "unknown" is used when the user or the network has no knowledge of the type of number, e.g. international number, national number, etc. In this case the number digits field is organized according to the network dialling plan, e.g. prefix or escape digits might be present. NOTE 3: Prefix or escape digits shall not be included. NOTE 4: The type of number "network specific number" is used to indicate administration/service number specific to the serving network, e.g. used to access an operator. NOTE 5: The international format shall be accepted by the MSC when the call is destined to a destination in the same country as the MSC. Table 10.5.118/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Called party BCD number (continued) - When an MS is the recipient of number information from the network, any incompatibility between the number digits and the number plan identification shall be ignored and a STATUS message shall not be sent to the network. - In the case of numbering plan "unknown", the number digits field is organized according to the network dialling plan; e.g. prefix or escape digits might be present. Table 10.5.118/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Called party BCD number (continued) | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 10.5.4.7 |
2,944 | 5.9.4 5G Globally Unique Temporary Identifier | The AMF shall allocate a 5G Globally Unique Temporary Identifier (5G-GUTI) to the UE that is common to both 3GPP and non-3GPP access. It shall be possible to use the same 5G-GUTI for accessing 3GPP access and non-3GPP access security context within the AMF for the given UE. An AMF may re-assign a new 5G-GUTI to the UE at any time. The AMF provides a new 5G-GUTI to the UE under the conditions specified in clause 6.12.3 of TS 33.501[ Security architecture and procedures for 5G System ] [29]. When the UE is in CM-IDLE, the AMF may delay providing the UE with a new 5G-GUTI until the next NAS transaction. The 5G-GUTI shall be structured as: <5G-GUTI> := <GUAMI> <5G-TMSI> where GUAMI identifies one or more AMF(s). When the GUAMI identifies only one AMF, the 5G-TMSI identifies the UE uniquely within the AMF. However, when AMF assigns a 5G-GUTI to the UE with a GUAMI value used by more than one AMF, the AMF shall ensure that the 5G-TMSI value used within the assigned 5G-GUTI is not already in use by the other AMF(s) sharing that GUAMI value. The Globally Unique AMF ID (GUAMI) shall be structured as: <GUAMI> := <MCC> <MNC> <AMF Region ID> <AMF Set ID> <AMF Pointer> where AMF Region ID identifies the region, AMF Set ID uniquely identifies the AMF Set within the AMF Region and AMF Pointer identifies one or more AMFs within the AMF Set. NOTE 1: The AMF Region ID addresses the case that there are more AMFs in the network than the number of AMFs that can be supported by AMF Set ID and AMF Pointer by enabling operators to re-use the same AMF Set IDs and AMF Pointers in different regions. NOTE 2: In the case of SNPNs, the PLMN IDs may be shared among SNPNs such that the constructed GUAMIs are not globally unique. However, PLMN ID and NID are provided together, separate from the GUAMI, to uniquely identify selected or supported SNPN in RRC and N2. NOTE 3: See TS 23.003[ Numbering, addressing and identification ] [19] for details on the structure of the fields of GUAMI. The 5G-S-TMSI is the shortened form of the GUTI to enable more efficient radio signalling procedures (e.g. during Paging and Service Request) and is defined as: <5G-S-TMSI> := <AMF Set ID> <AMF Pointer> <5G-TMSI> As specified in TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [50] and TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [52] for 3GPP access, the NG-RAN uses the 10 Least Significant Bits of the 5G-TMSI in the determination of the time at which different UEs are paged. Hence, the AMF shall ensure that the 10 Least Significant Bits of the 5G-TMSI are evenly distributed. As specified in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [28] and TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [51] for 3GPP access, the NG-RAN's RRC Connection Establishment's contention resolution process assumes that there is a low probability of the same 5G-TMSI being allocated by different AMFs to different UEs. The AMFs' process for allocating the 5G-TMSI should take this account. NOTE 4: To achieve this, the AMF could, for example, use a random seed number for any process it uses when choosing the UE's 5G-TMSI. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.9.4 |
2,945 | 5.9.4.4 MBS services of interest determination | The UE shall: 1> consider an MBS service to be part of the MBS services of interest if the following conditions are met: 2> the UE is receiving or interested to receive this service via a broadcast MRB; and 2> the session of this service is ongoing or about to start; and 2> one or more MBS FSAIs in the USD for this service is included in SIB21 acquired from the PCell for a frequency belonging to the set of MBS frequencies of interest, determined according to 5.9.4.3 or SIB21 acquired from the PCell does not provide the frequency mapping for the concerned service but that frequency is included in the USD of this service. NOTE: The UE may determine whether the session is ongoing from the start and stop time indicated in the User Service Description (USD), see TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [2] or TS 23.247[ Architectural enhancements for 5G multicast-broadcast services ] [67]. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.9.4.4 |
2,946 | 8.11.1.1.3 Transmit diversity performance (Cell-Specific Reference Symbols) | 8.11.1.1.3.1 Minimum Requirement 2 Tx Antenna Port supporting narrowband transmission The requirements are specified in Table 8.11.1.1.3.1-2, with the addition of the parameters in Table 8.11.1.1.3.1-1 and Table 8.11.1.1.3.1-1a, and the downlink physical channel setup according to Annex C.3.2. The purpose is to verify the performance of transmit diversity (SFBC) with 2 transmitter antennas. Table 8.11.1.1.3.1-1: Test Parameters for Transmit diversity performance (FRC) Table 8.11.1.1.3.1-1a: Test Parameters for Transmit diversity performance (FRC) Table 8.11.1.1.3.1-2: Minimum performance Transmit Diversity (FRC) 8.11.1.1.3.2 Minimum Requirement 2 Tx Antenna Port supporting wideband transmission The requirements are specified in Table 8.11.1.1.3.2-2, with the addition of the parameters in Table 8.11.1.1.3.2-1 and the downlink physical channel setup according to Annex C.3.2. The purpose is to verify the performance of transmit diversity (SFBC) with 2 transmitter antennas. Table 8.11.1.1.3.2-1: Test Parameters for Transmit diversity performance (FRC) Table 8.11.1.1.3.2-2: Minimum performance Transmit Diversity (FRC) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.11.1.1.3 |
2,947 | 5.3.8 RRC connection release 5.3.8.1 General | Figure 5.3.8.1-1: RRC connection release, successful The purpose of this procedure is: - to release the RRC connection, which includes the release of the established radio bearers (except for broadcast MRBs), BH RLC channels, Uu Relay RLC channels, PC5 Relay RLC channels as well as all radio resources; or - to suspend the RRC connection only if SRB2 and at least one DRB or multicast MRB or, for IAB and NCR, SRB2, are setup, which includes the suspension of the established radio bearers (except for broadcast MRBs). | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.8 |
2,948 | 5.2.3.2.1 Nudm_UECM_Registration service operation | Service operation name: Nudm_UECM_Registration Description: Register UE's serving NF (if NF Type is AMF, SMSF, or NWDAF) or Session's serving NF (if NF Type is SMF) on the UDM. This operation implies the following: - The authorization, if applicable, to register the NF service consumer in UDM for the UE (e.g. based on UE roaming/RAT restrictions applicable when NF type is AMF). If this is successful, the NF service consumer is set as a serving NF for the corresponding UE/Session context. - When the consumer is AMF or SMF, it is implicitly subscribed to be notified when it is deregistered in UDM. This notification is done by means of Nudm_UECM_DeregistrationNotification operation. - When the consumer is AMF or SMF, it may optionally use this operation to subscribe to be notified of the need for P-CSCF Restoration. This notification is done by means of Nudm_UECM_PCscfRestoration operation. For more information regarding P-CSCF restoration procedures see TS 23.380[ IMS Restoration Procedures ] [38]. Inputs, Required: NF ID, SUPI, NF Type, Access Type (if NF Type is AMF, SMSF), RAT Type and GUAMI (if NF Type is AMF), PDU Session ID (if NF Type is SMF), Analytics ID(s) (if NF Type is NWDAF). If NF Type is SMF: DNN or Indication of Emergency Services, S-NSSAI, SMF+PGW-C FQDN for S5/S8 if the PDU Session supports EPS interworking, Serving Node PLMN ID. If NF type is AMF and Access Type is 3GPP access: Registration type. If NF type is SMSF: SMSF MAP address and/or Diameter address, Serving PLMN ID. NOTE: The GUAMI includes the MNC+MCC of the serving PLMN. In home routed roaming, the H-SMF provides the PLMN ID of the HPLMN as Serving Node PLMN ID. In LBO roaming, the SMF in the VPLMN provides the PLMN ID of the serving PLMN in the VPLMN as Serving Node PLMN ID. Inputs, Optional: PEI (conditional, condition stated below), P-CSCF Restoration notification information, NID (e.g. if NF Type is AMF; see clause 5.18 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]), backup AMF(s) (if NF Type is AMF), "Homogeneous Support of IMS Voice over PS Sessions" indication (if NF Type is AMF), UE SRVCC capability (if NF Type is AMF), indication that access is from ePDG (shall be sent if NF Type is SMF and PDU Session is setup via S2b), VGMLC ID (if NF type is AMF and information is available in AMF). Backup AMF(s) sent only once by the AMF to the UDM in its first interaction with the UDM, indication of no event exposure subscription information available (if NF Type is AMF). PCF ID selected for the PDN connection/PDU Session (If NF type is SMF), UE MINT support indicator, Disaster Roaming indicator indicating that Disaster Roaming service is applied. Outputs, Required: Result indication. Outputs, Optional: None. If the PEI was retrieved by the AMF (either from the UE or another AMF), AMF shall provide it to the UDM using Nudm_UECM_Registration in order to ensure that the UDM always has the latest PEI available e.g. for reporting event Change of SUPI-PEI association. See step 14a of clause 4.2.2.2.2 for an example usage of this service operation. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.3.2.1 |
2,949 | 5.2.6.28.2 Nnef_ASTI_Create operation | Service operation name: Nnef_ASTI_Create Description: The consumer requests to activate the 5G access stratum time distribution, for which the NEF authorizes the request and invokes the corresponding service operation with TSCTSF (clause 5.2.27.4.2). Inputs, Required: As specified in clause 5.2.27.4.2. Inputs, Optional: As specified in clause 5.2.27.4.2. Outputs, Required: Operation execution result indication and in the case of successful operation, any outputs as specified in clause 5.2.27.4.2. Outputs, Optional: As specified in clause 5.2.27.4.2. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.6.28.2 |
2,950 | 8.13.3.1.2 Minimum Requirement for TDD PCell | The purpose of these tests is to verify the closed loop rank-two performance with wideband and frequency selective precoding. For TDD FDD CA with TDD PCell and 2DL CCs, the requirements are specified in Table 8.13.3.1.2-4 based on single carrier requirement specified in Table 8.13.3.1.2-2 and Table 8.13.3.1.2-3, with the addition of the parameters in Table 8.13.3.1.2-1 and the downlink physical channel setup according to Annex C.3.2. For TDD FDD CA with TDD PCell and 3DL CCs, the requirements are specified in Table 8.13.3.1.2-5 based on single carrier requirement specified in Table 8.13.3.1.2-2 and Table 8.13.3.1.2-3, with the addition of the parameters in Table 8.13.3.1.2-1 and the downlink physical channel setup according to Annex C.3.2. For TDD FDD CA with TDD PCell and 4DL CCs, the requirements are specified in Table 8.13.3.1.2-6 based on single carrier requirement specified in Table 8.13.3.1.2-2 and Table 8.13.3.1.2-3, with the addition of the parameters in Table 8.13.3.1.2-1 and the downlink physical channel setup according to Annex C.3.2. For TDD FDD CA with TDD PCell and 5DL CCs, the requirements are specified in Table 8.13.3.1.2-7 based on single carrier requirement specified in Table 8.13.3.1.2-2 and Table 8.13.3.1.2-3, with the addition of the parameters in Table 8.13.3.1.2-1 and the downlink physical channel setup according to Annex C.3.2. The test coverage for different number of component carriers is defined in 8.1.2.4. Table 8.13.3.1.2-1: Test Parameters for Multi-Layer Spatial Multiplexing (FRC) for CA Table 8.13.3.1.2-2: Single carrier performance with different bandwidths for multiple CA configurations for FDD SCell (FRC) Table 8.13.3.1.2-3: Single carrier performance with different bandwidths for multiple CA configurations for TDD PCell and SCell (FRC) Table 8.13.3.1.2-4: Minimum performance for multiple CA configurations with 2DL CCs (FRC) Table 8.13.3.1.2-5: Minimum performance for multiple CA configurations with 3DL CCs (FRC) Table 8.13.3.1.2-6: Minimum performance for multiple CA configurations with 4DL CCs (FRC) Table 8.13.3.1.2-7: Minimum performance for multiple CA configurations with 5DL CCs (FRC) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.13.3.1.2 |
2,951 | 4.23.7.2.3 Execution phase | Compared to the procedure for execution phase in 4.9.1.3.3, the SMF interacting with the S-UPF, T-UPF, S-AMF and T-AMF is the I-SMF. The difference is as following: - Step 10a: If I-SMF is available for a PDU Session and the existing intermediate S-UPF is re-allocated, i.e. a new T-UPF is selected, the I-SMF invokes an Nsmf_PDUSession_Update Request (DL CN Tunnel Info of the T-UPF) service operation toward the SMF. The SMF sends N4 Session Modification Request message to PDU Session Anchor UPF, providing DL CN Tunnel Info to the PDU Session Anchor UPF. The PDU Session Anchor sends one or more "end marker" packets for each N3/N9 tunnel on the old path immediately after switching the path, the source NG-RAN shall forward the "end marker" packets to the target NG-RAN. - Step 10b: The SMF responds with the Nsmf_PDUSession_Update Response service operation to I-SMF once the PDU Session Anchor UPF is updated with the DL Tunnel Info of the T-UPF. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.23.7.2.3 |
2,952 | 4.13.8.3 Coverage availability information provisioning to the UE | A UE may use satellite coverage availability information for satellite access to support discontinuous coverage operations. Satellite coverage availability information can be provided to a UE by an external server via a PDN Connection or SMS. The protocol and format of satellite coverage availability information via PDU Connection or SMS is not defined in this release of the specification, but some examples on the information that constitutes the satellite coverage availability information is defined in Annex N. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.13.8.3 |
2,953 | 6.1.3.1.4 Unsuccessful PDP context activation requested by the network | Upon receipt of the REQUEST PDP CONTEXT ACTIVATION message, the MS may reject the network requested PDP context activation by sending the REQUEST PDP CONTEXT ACTIVATION REJECT message to the network. The message contains the same TI as included in the REQUEST PDP CONTEXT ACTIVATION and an additional cause code that typically indicates one of the following causes: # 26: insufficient resources; # 31: activation rejected, unspecified; # 40: feature not supported; or # 95 - 111: protocol errors. The network shall stop timer T3385 and enter state PDP-INACTIVE. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.1.3.1.4 |
2,954 | 5.2.6.32.2 Nnef_MemberUESelectionAssistance_Subscribe service operation | Service operation name: Nnef_MemberUESelectionAssistance_Subscribe Description: The NF consumer subscribes to receive the Member UE selection assistance information, or the subscription is updated if the same subscription is already existing in NEF. Inputs, Required: At least one Member UE filtering criterion shown in Table 4.15.13.2-1. Inputs, Conditional Required: If no Subscription Correlation ID is provided in the subscription, AF Identifier, Notification Target Address (+ Notification Correlation ID), a list of target member UEs in the form of a list of GPSIs or a list of UE IP addresses) is required. Inputs, Optional: Application ID, Subscription Correlation ID (in the case of update of the existing subscription), Expiry time, time window(s) for selecting the candidate UEs, specific parameters depending on the Member UE filtering criteria as shown in Table 4.15.13.2-1, Periodicity (the periodicity of member update), maximum number of candidate UEs. Outputs, Required: When the subscription is accepted: Subscription Correlation ID, Expiry time (required if the subscription can be expired based on the operator's policy). | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.6.32.2 |
2,955 | 6.8.2 Authentication and key agreement for GSM subscribers 6.8.2.1 General | For GSM subscribers, GSM AKA shall always be used. The execution of the GSM AKA results in the establishment of a GSM security context between the user and the serving network domain to which the VLR/SGSN belongs. The user needs to separately establish a security context with each serving network domain. When in a UTRAN, the UMTS cipher/integrity keys CK and IK are derived from the GSM cipher key Kc by the ME and the VLR/SGSN, both R99+ entities. Figure 19 shows the different scenarios that can occur with GSM subscribers using either R98- or R99+ ME in a mixed network architecture. Figure 19: Authentication and key agreement for GSM subscribers Note that the GSM parameters RAND and RES are sent transparently through the UTRAN or GSM BSS. In case of a GSM BSS, ciphering is applied in the GSM BSS for services delivered via the MSC/VLR, and by the SGSN for services delivered via the SGSN. In the latter case the GSM cipher key Kc is not sent to the GSM BSS. In case of a UTRAN, ciphering is always applied in the RNC, and the UMTS cipher/integrity keys CK an IK are always sent to the RNC. | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | 6.8.2 |
2,956 | 4.5.2 UL PRB Usage for traffic | This measurement provides the usage (in percentage) of physical resource blocks (PRBs) on the uplink for DTCH traffic. The measurement is split into subcounters per E-RAB QoS level (QCI). If there is one or more RNs served in a cell, for that cell the eNodeB performs PRB usage measurements separately for all traffic (including transmissions to/from RNs and UEs directly connected to the eNodeB) and for RN traffic. The measurement is also applicable to RNs. SI This measurement is obtained according to the definition in 3GPP TS 36.314[ Evolved Universal Terrestrial Radio Access (E-UTRA); Layer 2 - Measurements ] [11]. Separate counters are maintained for each QCI. The sum of all supported per QCI measurements shall equal the total PRB usage for DTCH. In case only a subset of per QCI measurements is supported, a sum subcounter will be provided first. Each measurement is an integer value from 0 to 100. The number of measurements is equal to the number of QCIs plus a possible sum value identified by the .sum suffix. The measurement name has the form RRU.PrbUl.QCI, which indicats the UL PRB Usage for all traffic RRU.PrbUlRN.QCI, which indicates the UL PRB Usage for the RN traffic where QCI identifies the E-RAB level quality of service class. EUtranCellFDD EUtranCellTDD Valid for packet switched traffic EPS | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.5.2 |
2,957 | 9.2.3.5 L1/L2-Triggered Mobility 9.2.3.5.1 General | LTM is a procedure in which a gNB receives L1 measurement report(s) from a UE, and on their basis the gNB changes UE serving cell by a cell switch command signalled via a MAC CE. The cell switch command indicates an LTM candidate configuration that the gNB previously prepared and provided to the UE through RRC signalling. Then the UE switches to the target configuration according to the cell switch command. The LTM procedure can be used to reduce the mobility latency as described in Annex G. When configured by the network, it is possible to activate TCI states of one or multiple cells that are different from the current serving cell. For instance, the TCI states of the LTM candidate cells can be activated in advance before any of those cells become the serving cell. This allows the UE to be DL synchronized with those cells, thereby facilitating a faster cell switch to one of those cells when cell switch is triggered. When configured by the network, it is possible to initiate UL TA acquisition (called early TA) procedure of one or multiple cells that are different from the current serving cells. If the cell has the same NTA as the current serving cells or NTA=0, early TA acquisition procedure is not required. The network may request the UE to perform early TA acquisition of a candidate cell before a cell switch. The early TA acquisition procedure is triggered by PDCCH order as specified in clause 9.2.6 or realized through UE-based TA measurement as configured by RRC. In the former case, the gNB to which the candidate cell belongs calculates the TA value and sends it to the gNB to which the serving cell belongs. The serving cell sends the TA value in the LTM cell switch command MAC CE when triggering LTM cell switch. In the latter case, the UE performs TA measurement for the candidate cells after being configured by RRC but the exact time the UE performs TA measurement is up to UE implementation. The UE applies the TA value measured by itself and performs RACH-less LTM upon receiving the cell switch command. The network may also send a TA value in the LTM cell switch command MAC CE without early TA acquisition. Depending on the availability of a valid TA value, the UE performs either a RACH-less LTM or RACH-based LTM cell switch. If the TA value is provided in the cell switch command, the UE applies the TA value as instructed by the network. In the case where UE-based TA measurement is configured, but no TA value is provided in the cell switch command, the UE applies the TA value by itself if available. Meanwhile, the UE performs RACH-less LTM cell switch upon receiving the cell switch command. If no valid TA value is available, the UE performs RACH-based LTM cell switch. Regardless of whether the UE is configured for UE-based TA measurement for a certain candidate cell, it will still follow the PDCCH order, which includes requesting a random access procedure towards the candidate cells. This also applies to the candidate cells for which the UE is capable of deriving TA values by itself. Additionally, regardless of whether the UE has already performed a random access procedure towards the candidate cells, it will still follow the UE-based measurement configuration if configured by the network. For RACH-less LTM, the UE accesses the target cell using either a configured grant or a dynamic grant. The configured grant is provided in the LTM candidate configuration, and the UE selects the configured grant occasion associated with the beam indicated in the cell switch command. Upon initiation of LTM cell switch to the target cell, the UE starts to monitor PDCCH on the target cell for dynamic scheduling. Before RACH-less LTM procedure completion, the UE shall not trigger random access procedure if it does not have a valid PUCCH resource for triggered SRs. The following principles apply to LTM: - Security key is maintained upon an LTM cell switch; - Subsequent LTM is supported. LTM supports both intra-gNB-DU and intra-gNB-CU inter-gNB-DU mobility. LTM supports both intra-frequency and inter-frequency mobility, including mobility to inter-frequency cell that is not a current serving cell. LTM is supported only for licensed spectrum. The following scenarios are supported: - PCell change in non-CA scenario and non-DC scenario; - PCell and SCell(s) change in CA scenario; - Dual connectivity scenario, PCell and MCG SCell(s) change and intra-SN PSCell and SCG SCell(s) change without MN involvement. LTM for simultaneous PCell and PSCell change is not supported. While the UE has stored LTM candidate configurations the UE can also execute any L3 handover command sent by the network. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 9.2.3.5 |
2,958 | 7.9 UE Assistance Information | When configured to do so, the UE can signal the network through UEAssistanceInformation: - If it prefers an adjustment in the connected mode DRX cycle length, for the purpose of delay budget reporting; - If it is experiencing internal overheating; - If it prefers certain DRX parameter values, and/or a reduced maximum number of secondary component carriers, and/or a reduced maximum aggregated bandwidth and/or a reduced maximum number of MIMO layers and/or minimum scheduling offsets K0 and K2 for power saving purpose; - If it expects not to send or receive any more data in the near future, and in this case, it can provide its preference to transition out of RRC_CONNECTED where this indication may express its preferred RRC state, or alternately, it may cancel an earlier indicated preference to transition out of RRC_CONNECTED; - If it prefers (not) to be provisioned with reference time information; - If it prefers to transition out of RRC_CONNECTED state for MUSIM operation and its preferred RRC state after transition; - If it wants to include assistance information for setup or release of gaps for MUSIM operation; - When affected by IDC problems that it cannot solve by itself: - The list of frequencies affected by IDC problems (see clause 23.4 of TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [2]); - The list of frequency ranges/frequency range combinations affected by the IDC problems; - DRX based TDM assistance information (see clause 23.4.2 of TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [2]); - Its RRM measurement relaxation status indicating whether RRM measurement relaxation criteria are met or not; - Its RLM measurement relaxation status indicating whether the UE is applying RLM measurements relaxation; - Its BFD measurement relaxation status indicating whether the UE is applying BFD measurements relaxation; - If it prefers not operating on multi-Rx (i.e. not supporting simultaneous reception with different QCL-typeD) for FR2. NOTE: The requirements on RRM/RLM/CSI measurements in different phases of IDC interference 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 ] [2] are applicable except that for NR serving cell, the requirements in TS 38.133[ NR; Requirements for support of radio resource management ] [13] and TS 38.101[ None ] -1 [18], TS 38.101[ None ] -2 [35], TS 38.101[ None ] -3 [36] apply. In the second case, the UE can express a preference for temporarily reducing the number of maximum secondary component carriers, the maximum aggregated bandwidth and the number of maximum MIMO layers. In all cases, it is up to the gNB whether to accommodate the request. For sidelink, the UE can report SL traffic pattern(s) to NG-RAN, for periodic traffic. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 7.9 |
2,959 | 28.6 5GS Tracking Area Identity (TAI) | The 5GS Tracking Area Identity (TAI) consists of a Mobile Country Code (MCC), Mobile Network Code (MNC), and Tracking Area Code (TAC). It is composed as shown in figure 28.6-1. Figure 28.6-1: Structure of the 5GS Tracking Area Identity (TAI) The TAI is composed of the following elements: - Mobile Country Code (MCC) identifies the country in which the PLMN is located. The value of the MCC is the same as the 3-digit MCC contained in the IMSI; - Mobile Network Code (MNC) is a code identifying the PLMN in that country. The value of the MNC is the same as the 2-digit or 3-digit MNC contained in the IMSI; - 5GS Tracking Area Code (TAC) is a fixed length code (of 3 octets) identifying a Tracking Area within a PLMN. This part of the tracking area identification shall be coded using a full hexadecimal representation. The following are reserved hexadecimal values of the TAC: - 000000, and - FFFFFE. NOTE 1: The above reserved values are used in some special cases when no valid TAI exists in the UE (see 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [125] for more information). NOTE 2: In the 5G Core Network protocols, when the TAI needs to be identified in the context of Standalone Non-Public Networks (SNPN), the Network Identifier (NID) of the SNPN is included as part of the TAI Information Element (see 3GPP TS 29.571[ 5G System; Common Data Types for Service Based Interfaces; Stage 3 ] [129]); this is a protocol aspect that does not imply any change on the system-wide definition of the TAI. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 28.6 |
2,960 | 9.11.3.37 NSSAI | The purpose of the NSSAI information element is to identify a collection of S-NSSAIs The NSSAI information element is coded as shown in figure 9.11.3.37.1 and table 9.11.3.37.1. The NSSAI is a type 4 information element with a minimum length of 4 octets and a maximum length of 146 octets. NOTE: More than one S-NSSAIs in an NSSAI can have the same SST values, and optionally same SD values, which are associated with different mapped HPLMN SST values and optionally mapped HPLMN SD values. Figure 9.11.3.37.1: NSSAI information element Table 9.11.3.37.1: NSSAI information element | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.11.3.37 |
2,961 | 2.8.2.2.2 Mapping in the UE | When the UE moves from the GERAN/UTRAN to the E-UTRAN, the UE needs to map the RAI and P-TMSI to a GUTI to be sent to the MME. The P-TMSI signature is sent intact to the MME. The mapping of P-TMSI (TLLI) and RAI in GERAN/UTRAN to GUTI in E-UTRAN shall be performed as follows: GERAN/UTRAN <MCC> maps to E-UTRAN <MCC> GERAN/UTRAN <MNC> maps to E-UTRAN <MNC> GERAN/UTRAN <LAC> maps to E-UTRAN <MME Group ID> GERAN/UTRAN <RAC> maps into bit 23 and down to bit 16 of the M-TMSI The 8 most significant bits of GERAN/UTRAN <NRI> map to the MME code. GERAN/UTRAN <P-TMSI> maps as follows: - 6 bits of the GERAN/UTRAN <P-TMSI> starting at bit 29 and down to bit 24 are mapped into bit 29 and down to bit 24 of the E-UTRAN <M-TMSI>; - 16 bits of the GERAN/UTRAN <P-TMSI> starting at bit 15 and down to bit 0 are mapped into bit 15 and down to bit 0 of the E-UTRAN <M-TMSI>. The values of <LAC> and <MME group id> shall be disjoint, so that they can be differentiated. The most significant bit of the <LAC> shall be set to zero; and the most significant bit of <MME group id> shall be set to one. Based on this definition, the most significant bit of the <MME group id> can be used to distinguish the node type, i.e. whether it is an MME or SGSN. The UE copies the received old SGSN's <LAC> into the <MME Group ID> when sending a message to an MME, regardless of the value of the most significant bit of the <LAC>. In networks where this definition is not applied (e.g. in networks already configured with LAC with the most significant bit set to 1 before LTE deployment), the information in the TAU/RAU request indicating whether the provided GUTI/P-TMSI is "native" (i.e. no system change) or "mapped" (i.e. system change) can be used to distinguish the node type for UEs implemented according to this release of the specification (see 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [90] and 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [5]). Specific network implementations still satisfying 3GPP standard interfaces can be used for pre-Rel-10 UEs to distinguish the node type. NOTE 1: As an example, at NAS level, the MME/SGSN can retrieve the old SGSN/MME by using additional GUTI/additional RAI/P-TMSI with double DNS query to solve the first time the UE moves between E-UTRAN and GERAN/UTRAN. As another example, the MME/SGSN can retrieve the old SGSN/MME by using double DNS query. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 2.8.2.2.2 |
2,962 | O.5.3 Repeated IEs | If an information element, for which repetition is not specified in subclause O.2, is repeated in the user-user protocol contents, only the contents of the information element appearing first shall be handled and all subsequent repetitions of the information element shall be ignored. When repetition of information elements is specified, only the contents of specified repeated information elements shall be handled. If the limit on repetition of information elements is exceeded, the contents of information elements appearing first up to the limit of repetitions shall be handled and all subsequent repetitions of the information element shall be ignored. | 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 | O.5.3 |
2,963 | 5.2.1 Resource grid | The transmitted signal in each slot is described by one or several resource grids of subcarriers and SC-FDMA symbols. The resource grid is illustrated in Figure 5.2.1-1. The quantity depends on the uplink transmission bandwidth configured in the cell and shall fulfil where and are the smallest and largest uplink bandwidths, respectively, supported by the current version of this specification. The set of allowed values for is given by TS 36.101[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception ] [7]. The number of SC-FDMA symbols in a slot depends on the cyclic prefix length configured by the higher layer parameter UL-CyclicPrefixLength and is given in Table 5.2.3-1. An antenna port is defined such that the channel over which a symbol on the antenna port is conveyed can be inferred from the channel over which another symbol on the same antenna port is conveyed. There is one resource grid per antenna port. The antenna ports used for transmission of a physical channel or signal depends on the number of antenna ports configured for the physical channel or signal as shown in Table 5.2.1-1. The index is used throughout clause 5 when a sequential numbering of the antenna ports is necessary. Figure 5.2.1-1: Uplink resource grid Table 5.2.1-1: Antenna ports used for different physical channels and signals | 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.2.1 |
2,964 | 4.11.0a.2a.3 PCF initiated SM Policy Association Modification | For the purpose of URSP delivery in EPS, PCF initiated SM Policy Association Modification procedure is triggered by an interaction from the PCF for the UE. The following enhancements are applicable to clause 4.16.5.2 (PCF initiated SM Policy Association Modification procedure): - Step 4: The PCF for the PDU Session may receive a UE Policy Container from the PCF for the UE and/or an update in the Policy Control Request Triggers applicable to the UE as described in clause 4.11.0a.2a.6: - If a UE Policy Container is received from the PCF for the UE, the PCF for the PDU Session selects one of the ongoing PDU Sessions for this UE that supports URSP Rule delivery in EPS and includes that UE Policy Container in Npcf_SMPolicyControl_UpdateNotify request. If an update in the Policy Control Request Triggers applicable to the UE is received, the PCF for the PDU Session determines whether an update on the current Policy Control Request Triggers needs to be sent to the SMF+PGW-C in Npcf_SMPolicyControl_UpdateNotify request. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.11.0a.2a.3 |
2,965 | 6.1.3 Overall Architecture of IAB | Figure 6.1.3-1: Overall architecture of IAB The NG-RAN supports IAB by the IAB-node wirelessly connecting to the gNB capable of serving the IAB-nodes, named IAB-donor. The IAB-donor consists of an IAB-donor-CU and one or more IAB-donor-DU(s). In case of separation of gNB-CU-CP and gNB-CU-UP, the IAB-donor may consist of an IAB-donor-CU-CP, multiple IAB-donor-CU-UPs and multiple IAB-donor-DUs. The IAB-node connects to an upstream IAB-node or an IAB-donor-DU via a subset of the UE functionalities of the NR Uu interface (named IAB-MT function of IAB-node). The IAB-node provides wireless backhaul to the downstream IAB-nodes and UEs via the network functionalities of the NR Uu interface (named IAB-DU function of IAB-node). The F1-C traffic between an IAB-node and IAB-donor-CU is backhauled via the IAB-donor-DU and the optional intermediate hop IAB-node(s). The F1-U traffic between an IAB-node and IAB-donor-CU is backhauled via the IAB-donor-DU and the optional intermediate hop IAB-node(s). All functions specified for a gNB-DU are equally applicable for an IAB-DU and IAB-donor-DU, unless otherwise stated, and all functions specified for a gNB-CU are equally applicable for an IAB-donor-CU, unless otherwise stated. All functions specified for the UE context are equally applicable for managing the context of IAB-MT, unless otherwise stated. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 6.1.3 |
2,966 | 9.14.1.1 Half-duplex FDD | The following requirements apply to UE Category NB2 capable of npdsch-16QAM-r17. For the parameters specified in Table 9.14.1.1-1, and using the downlink physical channels specified in C.3.6, the reported candidateRep value according to RC.33 FDD in Table A.4-1 shall be in the range of Β±1 of the reported median more than 90% of the time. If the NPDSCH BLER using the transport format indicated by median candidateRep value is less than or equal to 0.1, the BLER using the transport format indicated by the (median candidateRep value + 1) shall be greater than 0.1. If the NPDSCH BLER using the transport format indicated by the median candidateRep value is greater than 0.1, the BLER using transport format indicated by (median candidateRep value - 1) shall be less than or equal to 0.1. Table 9.14.1.1-1: Half-duplex 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.14.1.1 |
2,967 | 6.5.3.4.2 Handling of network rejection due to ESM cause #26 | If the ESM cause value is #26 "insufficient resources" and the Back-off timer value IE is included, the UE shall ignore the Re-attempt indicator IE provided by the network, if any, and take different actions depending on the timer value received for timer T3396 in the Back-off timer value IE (if the UE is configured for dual priority, exceptions are specified in clause 6.5.5; if the UE is a UE configured to use AC11 β 15 in selected PLMN, exceptions are specified in clause 6.3.5): i) if the timer value indicates neither zero nor deactivated, the UE shall stop timer T3396 associated with the corresponding APN, if it is running. The UE shall then start T3396 with the value provided in the Back-off timer value IE and not send another PDN CONNECTIVITY REQUEST, BEARER RESOURCE MODIFICATION REQUEST with exception of those identified in clause 6.5.4.1, or BEARER RESOURCE ALLOCATION REQUEST message for the same APN until timer T3396 expires or timer T3396 is stopped. If the UE did not provide an APN for the establishment of the PDN connection and the request type was different from "emergency" and from "handover of emergency bearer services", the UE shall stop the timer T3396 associated with no APN if it is running. The UE shall start timer T3396 with the received value and not send another PDN CONNECTIVITY REQUEST message without an APN and with request type different from "emergency" and from "handover of emergency bearer services", or another BEARER RESOURCE MODIFICATION REQUEST with exception of those identified in clause 6.5.4.1, or BEARER RESOURCE ALLOCATION REQUEST message for a non-emergency PDN connection established without an APN provided by the UE, until timer T3396 expires or timer T3396 is stopped. The UE shall not stop timer T3396 upon a PLMN change or inter-system change; ii) if the timer value indicates that this timer is deactivated, the UE shall not send another PDN CONNECTIVITY REQUEST, BEARER RESOURCE MODIFICATION REQUEST with exception of those identified in clause 6.5.4.1, or BEARER RESOURCE ALLOCATION REQUEST message for the same APN until the UE is switched off or the USIM is removed or the UE receives an ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST, ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST or MODIFY EPS BEARER CONTEXT REQUEST message for the same APN from the network or a DEACTIVATE EPS BEARER CONTEXT REQUEST message including ESM cause #39 "reactivation requested" for a default EPS bearer context for the same APN from the network. If the UE did not provide an APN for the establishment of the PDN connection and the request type was different from "emergency" and from "handover of emergency bearer services", the UE shall not send another PDN CONNECTIVITY REQUEST message without an APN and with request type different from "emergency" and from "handover of emergency bearer services", or another BEARER RESOURCE MODIFICATION REQUEST with exception of those identified in clause 6.5.4.1, or BEARER RESOURCE ALLOCATION REQUEST message for a non-emergency PDN connection established without APN provided by the UE, until the UE is switched off or the USIM is removed, or the UE receives an ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST, ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST or MODIFY EPS BEARER CONTEXT REQUEST message for a non-emergency PDN connection established without an APN provided by the UE, or a DEACTIVATE EPS BEARER CONTEXT REQUEST message including ESM cause #39 "reactivation requested" for a default EPS bearer context of a non-emergency PDN connection established without an APN provided by the UE. The timer T3396 remains deactivated upon a PLMN change or inter-system change; or iii) if the timer value indicates zero, the UE: - shall stop timer T3396 associated with the corresponding APN, if running, and may send another PDN CONNECTIVITY REQUEST, BEARER RESOURCE MODIFICATION REQUEST or BEARER RESOURCE ALLOCATION REQUEST message for the same APN; and - if the UE did not provide an APN for the establishment of the PDN connection and the request type was different from "emergency" and from "handover of emergency bearer services", the UE shall stop timer T3396 associated with no APN, if running, and may send another PDN CONNECTIVITY REQUEST message without an APN, or another BEARER RESOURCE MODIFICATION REQUEST or BEARER RESOURCE ALLOCATION REQUEST message for a non-emergency PDN connection established without an APN provided by the UE. If the Back-off timer value IE is not included, the UE may send a PDN CONNECTIVITY REQUEST, BEARER RESOURCE MODIFICATION REQUEST or BEARER RESOURCE ALLOCATION REQUEST messages for the same APN. The further actions to be performed by the UE are implementation dependent as part of upper layers responsibility. If the timer T3396 is running when the UE enters state EMM-DEREGISTERED, the UE remains switched on, and the USIM in the UE remains the same, then timer T3396 is kept running until it expires or it is stopped. If the UE is switched off when the timer T3396 is running, and if the USIM in the UE remains the same when the UE is switched on, the UE behaves as follows: - let t1 be the time remaining for T3396 timeout at switch off and let t be the time elapsed between switch off and switch on. If t1 is greater than t, then the timer shall be restarted with the value t1 β t. If t1 is equal to or less than t, then the timer need not be restarted. If the UE is not capable of determining t, then the UE shall restart the timer with the value t1; - if prior to switch off, timer T3396 was running for a specific APN, because a PDN CONNECTIVITY REQUEST, BEARER RESOURCE MODIFICATION REQUEST or BEARER RESOURCE ALLOCATION REQUEST message containing the low priority indicator set to "MS is configured for NAS signalling low priority" was rejected with a timer value for timer T3396, and if timer T3396 is restarted at switch on, then the UE configured for dual priority shall handle session management requests as indicated in clause 6.5.5; and - if prior to switch off timer T3396 was running because a PDN CONNECTIVITY REQUEST without APN sent together with an ATTACH REQUEST message containing the low priority indicator set to "MS is configured for NAS signalling low priority" was rejected with a timer value for timer T3396, and if timer T3396 is restarted at switch on, then the UE configured for dual priority shall handle session management requests as indicated in clause 6.5.5. | 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.5.3.4.2 |
2,968 | 5.20b.1 Group attribute provisioning | A group may be a 5G VN group managed as defined in clause 5.29.2, as well as a group configured by OA&M. An AF may provision DNN and S-NSSAI specific attributes for a group of UEs: - LADN Service area, which consists of Tracking Area identities or geographical information, it is applicable to each UE member within the group and for a specific DNN and S-NSSAI. - Default QoS, the QoS refers to 5QI, ARP and 5QI Priority Level as defined in clause 5.7.2.7 and it is applicable to each UE member within the group and for a specific DNN and S-NSSAI. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.20b.1 |
2,969 | β BandCombinationListSidelinkEUTRA-NR | The IE BandCombinationListSidelinkEUTRA-NR contains a list of V2X sidelink and NR sidelink band combinations. BandCombinationListSidelinkEUTRA-NR information element -- ASN1START -- TAG-BANDCOMBINATIONLISTSIDELINKEUTRANR-START BandCombinationListSidelinkEUTRA-NR-r16 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombinationParametersSidelinkEUTRA-NR-r16 BandCombinationListSidelinkEUTRA-NR-v1630 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombinationParametersSidelinkEUTRA-NR-v1630 BandCombinationListSidelinkEUTRA-NR-v1710 ::= SEQUENCE (SIZE (1..maxBandComb)) OF BandCombinationParametersSidelinkEUTRA-NR-v1710 BandCombinationParametersSidelinkEUTRA-NR-r16 ::= SEQUENCE (SIZE (1..maxSimultaneousBands)) OF BandParametersSidelinkEUTRA-NR-r16 BandCombinationParametersSidelinkEUTRA-NR-v1630 ::= SEQUENCE (SIZE (1..maxSimultaneousBands)) OF BandParametersSidelinkEUTRA-NR-v1630 BandCombinationParametersSidelinkEUTRA-NR-v1710 ::= SEQUENCE (SIZE (1..maxSimultaneousBands)) OF BandParametersSidelinkEUTRA-NR-v1710 BandParametersSidelinkEUTRA-NR-r16 ::= CHOICE { eutra SEQUENCE { bandParametersSidelinkEUTRA1-r16 OCTET STRING OPTIONAL, bandParametersSidelinkEUTRA2-r16 OCTET STRING OPTIONAL }, nr SEQUENCE { bandParametersSidelinkNR-r16 BandParametersSidelink-r16 } } BandParametersSidelinkEUTRA-NR-v1630 ::= CHOICE { eutra NULL, nr SEQUENCE { tx-Sidelink-r16 ENUMERATED {supported} OPTIONAL, rx-Sidelink-r16 ENUMERATED {supported} OPTIONAL, sl-CrossCarrierScheduling-r16 ENUMERATED {supported} OPTIONAL } } BandParametersSidelinkEUTRA-NR-v1710 ::= CHOICE { eutra NULL, nr SEQUENCE { --32-4 sl-TransmissionMode2-PartialSensing-r17 SEQUENCE { harq-TxProcessModeTwoSidelink-r17 ENUMERATED {n8, n16}, scs-CP-PatternTxSidelinkModeTwo-r17 CHOICE { fr1-r17 SEQUENCE { scs-15kHz-r17 BIT STRING (SIZE (16)) OPTIONAL, scs-30kHz-r17 BIT STRING (SIZE (16)) OPTIONAL, scs-60kHz-r17 BIT STRING (SIZE (16)) OPTIONAL }, fr2-r17 SEQUENCE { scs-60kHz-r17 BIT STRING (SIZE (16)) OPTIONAL, scs-120kHz-r17 BIT STRING (SIZE (16)) OPTIONAL } } OPTIONAL, extendedCP-Mode2PartialSensing-r17 ENUMERATED {supported} OPTIONAL, dl-openLoopPC-Sidelink-r17 ENUMERATED {supported} OPTIONAL } OPTIONAL, --32-2a: Receiving NR sidelink of PSFCH rx-sidelinkPSFCH-r17 ENUMERATED {n5, n15, n25, n32, n35, n45, n50, n64} OPTIONAL, --32-5a-1 tx-IUC-Scheme1-Mode2Sidelink-r17 ENUMERATED {supported} OPTIONAL, --32-5b-1 tx-IUC-Scheme2-Mode2Sidelink-r17 ENUMERATED {n4, n8, n16} OPTIONAL } } BandParametersSidelink-r16 ::= SEQUENCE { freqBandSidelink-r16 FreqBandIndicatorNR } -- TAG-BANDCOMBINATIONLISTSIDELINKEUTRANR-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | β |
2,970 | 12.2.5.1 Definition 12.2.5.1.1 General description | Within a message, one or multiple instances of the Load Control Information (LCI) IE may be included by the same GTP-C entity. When providing load control information in a message for the first time or subsequently, the GTP-C entity shall always include the full set of load control information, i.e. all the node level and APN Level applicable instances of the Load Control Information, even if only a subset of the load control information has changed. All the instances of the LCI IE provided by a given GTP-C entity in a message shall contain the same Load-Control-Sequence-Number. The Load Control Sequence Number shall be incremented whenever the load control information is changed (see clause 12.2.5.1.2.1). The receiver shall overwrite any stored load control information of a peer with the newly received load control information (via one or multiple instances) from the same peer node if the new load control information is more recent than the old information as indicated by the Load Control Sequence Number, e.g. if the receiver has stored 'X' instances of the load control information for a peer node, it overwrites those 'X' instances with the new set of 'Y' instances received in a message from the same peer node, where X, Y are any integer number. The receiver shall consider all the parameters received in the same instance of the LCI IE in conjunction while using this information for node selection. When more than one instance of the LCI IE is received, the receiver shall consider the parameters included in each instance independently, when using this information for node selection. The parameters are further defined in clauses 12.2.5.1.2 and 12.2.5.1.3. Load control information may be extended with new parameters in future versions of the specification. Any new parameter will have to be categorized as: - Non-critical optional parameters: the support of these parameters is not critical for the receiver. The receiver can successfully and correctly comprehend the load control information instance, containing one or more of these parameters, by using the other parameters and ignoring the non-critical optional parameter. - Critical optional parameters: the support of these parameters is critical for the receiver to correctly comprehend the instance of the load control information containing one or more of these parameters. The sender may include one or more non-critical optional parameters within any instance of the LCI IE without having the knowledge of the receiver's capability to support the same. However, the sender shall only include one or more critical optional parameter in any instance of the LCI IE towards a receiver if the corresponding receiver is known to support those parameters. The sender may be aware of this either via signalling methods or by configuration; (this will have to be defined when introducing any such new parameter in future). Each instance of the LCI IE shall be associated to the node identity (FQDN or IP address of the GW node received from the HSS or the DNS) of the serving SGW or PGW, i.e. the identity determined during the SGW or PGW selection. NOTE: The Node type is derived based on the instance number of the LCI IE. | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 12.2.5.1 |
2,971 | Y.2 Authentication and authorization between MSGin5G client and MSGin5G Server | The Authentication and authorization between MSGin5G Client and MSGin5G Server shall be based on AKMA, which is specified in TS 33.535[ Authentication and Key Management for Applications (AKMA) based on 3GPP credentials in the 5G System (5GS) ] [91]. Before initiating communication with MSGin5G Server, the UE needs to have performed primary authentication and registered with the 5GC, resulting in the successful generation of KAKMA and A-KID at both MSGin5G Client and the 5GC as specified in clause 6.1, TS 33.535[ Authentication and Key Management for Applications (AKMA) based on 3GPP credentials in the 5G System (5GS) ] [91]. Once the UE is registered in 5GC, the MSGin5G Client in the UE and the MSGin5G Server may use TLS for authentication as specified in Annex B of TS 33.535[ Authentication and Key Management for Applications (AKMA) based on 3GPP credentials in the 5G System (5GS) ] [91] with the MSGin5G Server taking the role of AKMA AF. Methods other than TLS with AKMA may be used for authentication between the MSGin5G Client and MSGin5G Server, depending on the Ua* protocols. When MSGin5G service is used with SEAL, the application architecture described in TS 23.554[ Application architecture for MSGin5G Service; Stage 2 ] [106] is followed. In this case, authorization of the MSGin5G UE by the MSGin5G server is performed by validating the association between the UE service ID and UE ID (SUPI/GPSI). The UE service ID is acquired via the MSGin5G registration request, as specified in TS 23.554[ Application architecture for MSGin5G Service; Stage 2 ] [106]. The Configuration Management server or MSGin5G Configuration Function maintains association of the assigned UE service ID with the UE ID. The MSGin5G server retrieves the association from the Configuration Management server or MSGin5G Configuration Function using the UE ID received from the AAnF and verifies whether the UE service ID received in the registration request message is associated with the UE ID in the retrieved association information. For constrained UE, the Gateway/Proxy UE shall perform authentication and authorization on behalf of the constrained UE with MSgin5G Server based on AKMA as specified above. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | Y.2 |
2,972 | 5.5.3.2.5A Tracking area updating procedure for initiating a PDN connection for emergency bearer services not accepted by the network | If the tracking area updating request for initiating a PDN connection for emergency bearer services cannot be accepted by the network, the UE shall perform the procedures as described in clause 5.5.3.2.5. If the tracking area updating request for initiating a PDN connection for emergency bearer services fails due to receiving the AUTHENTICATION REJECT message, the UE shall perform the procedures as described in clause 5.4.2.5. Then if the UE is in the same selected PLMN where the last tracking area updating request was attempted, the UE shall: a) inform the upper layers of the failure of the procedure; or NOTE 1: This can result in the upper layers establishment of a CS emergency call (if not already attempted in the CS domain) or other implementation specific mechanisms, e.g. procedures specified in 3GPP TS 24.229[ IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 ] [13D] can result in the emergency call being attempted to another IP-CAN. b) detach locally, if not detached already, attempt EPS attach for emergency bearer services. If the tracking area updating request for initiating a PDN connection for emergency bearer services fails due to abnormal case a) in clause 5.5.3.2.6, the UE shall perform the actions as described in clause 5.5.3.2.6 and inform the upper layers of the failure to access the network. NOTE 2: This can result in the upper layers establishment of a CS emergency call (if not already attempted in the CS domain) or other implementation specific mechanisms, e.g. procedures specified in 3GPP TS 24.229[ IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 ] [13D] can result in the emergency call being attempted to another IP-CAN. If the tracking area updating request for initiating a PDN connection for emergency bearer services fails due to abnormal cases b), c), d) or f) as well as k) when the "Extended wait time" is ignored, and ka) when the "Extended wait time CP data" is ignored in clause .2.6, the UE shall perform the procedures as described in clause 5.5.3.2.6. Then if the UE is in the same selected PLMN where the last tracking area updating request was attempted, the UE shall: a) inform the upper layers of the failure of the procedure; or NOTE 3: This can result in the upper layers establishment of a CS emergency call (if not already attempted in the CS domain) or other implementation specific mechanisms, e.g. procedures specified in 3GPP TS 24.229[ IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 ] [13D] can result in the emergency call being attempted to another IP-CAN. b) detach locally, if not detached already, attempt EPS attach for emergency bearer services. | 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.2.5A |
2,973 | A.28 Monitor of the number of active UEs | The number of the active UEs in each cell is a valuable measurment for operators to know how many UEs are with buffered data per cell basis. This kind of information can help operators to tune the admission control parameters for the cell and to do load balancing between cells to ensure that the target percentage or number of the UEs admitted achieve the target QoS. However, the number of single uplink or downlink UEs can not effectively reflect the actual number of active UEs either on the downlink or on the uplink in the network. As the active UEs reflect UEs have data to transmit or receive , the ratio of the number of active UEs to the number of the RRC connected UEs can be established, which can be used to monitor the the cell. In addition, compared with the number of RRC connected users, the number of active UEs is a more effective measurement to reflect the control plane capacity of wireless network. | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | A.28 |
2,974 | 8.1.2.3C Applicability and test rules for SDR tests for 4Rx capable UEs | For FDD single carrier or CA, UE is required to fulfill SDR tests specified in section 8.7.9. For TDD single carrier or CA, UE is required to fulfill SDR tests specified in section 8.7.10. For TDD-FDD CA, UE is required to fulfill SDR test in section 8.7.11. For FDD DC, UE is required to fulfill SDR tests specified in section 8.7.13. For TDD DC, UE is required to fulfill SDR tests specified in section 8.7.14. For TDD-FDD DC, UE is required to fulfill SDR test in section 8.7.15. For single carrier or CA SDR tests, CA configuration, bandwidth combination and MIMO layer on each CC is determined by following procedure. - Select one CA bandwidth combination among all supported CA configurations with bandwidth combination and MIMO layer on each CC that leads to largest equivalent aggregated bandwidth among all CA bandwidth combinations supported by UE. Equivalent aggregated bandwidth is defined as where is number of CCs, and is MIMO layer and bandwidth of CC . - When there are multiple sets of {CA configuration, bandwidth combination, MIMO layer} with same largest aggregated bandwidth, select one among sets with largest number of 4 layer CCs. - The procedure applies also for single carrier using operating band instead of CA configuration, and bandwidth instead of bandwidth combination. For DC SDR tests, DC configuration, bandwidth combination and MIMO layer on each CC is determined by following procedure. - Select one DC bandwidth combination among all supported DC configurations with bandwidth combination and MIMO layer on each CC that leads to largest equivalent aggregated bandwidth among all DC bandwidth combinations supported by UE. Equivalent aggregated bandwidth is defined as where is number of CCs, and is MIMO layer and bandwidth of CC . - When there are multiple sets of {DC configuration, bandwidth combination, MIMO layer} with same largest aggregated bandwidth, select one among sets with largest number of 4 layer CCs. For UEs with no supported 4Rx RF bands the applicability rule in 8.1.2.3C is not applied for SDR tests. | 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.3C |
2,975 | 5.11.3 UE Core Network Capability | The UE Core Network Capability is split into the UE Network Capability IE (mostly for E-UTRAN access related core network parameters) and the MS Network Capability IE (mostly for UTRAN/GERAN access related core network parameters) and contains capabilities, e.g. for CIoT, NAS/AS security algorithms (that also indicate support for EPS-UPIP), etc. Both the UE Network Capability and the MS Network Capability are transferred between CN nodes at MME to MME, MME to SGSN, SGSN to SGSN, and SGSN to MME changes. In order to ensure that the UE Core Network Capability information stored in the MME is up to date (e.g. to handle the situation when the USIM is moved into a different device while out of coverage, and the old device did not send the Detach message; and the cases of inter-RAT Tracking Area Update), the UE shall send the UE Core Network Capability information to the MME during the Attach and non-periodic Tracking Area Update procedure within the NAS message. The MME shall store always the latest UE Core Network Capability received from the UE. Any UE Core Network Capability that an MME receives from an old MME/SGSN is replaced when the UE provides the UE Core Network Capability with Attach and the Tracking Area Update signalling. The MME shall remove the stored MS Network Capability, if MS Network Capability is not included in Attach or non-periodic Tracking Area Update signalling e.g. UE is only capable of E-UTRAN. If the UE's UE Core Network Capability information changes (in either ECM-CONNECTED or in ECM-IDLE state (including cases of being in GERAN/UTRAN coverage and having ISR activated)), the UE shall perform a Tracking Area Update ('type' different to 'periodic') when it next returns to E-UTRAN coverage - see clause 5.3.3.0. If the UE supports multiple user plane radio bearers on the NB-IoT RAT (see TS 36.306[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio access capabilities ] [82], TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [37]), then the UE shall indicate this in the UE Network Capability IE. If the UE supports, the RACS feature defined in clause 5.11.3a, and in this specification for the impact on the EPS procedures, then the UE shall indicate this in the UE Network Capability IE. If the UE supports dual connectivity with NR (see clause 4.3.2a), then the UE shall indicate its support in a NAS indicator. If the UE supports Service Gap Control (see clause 4.3.17.9), then the UE shall indicate this in the UE Network Capability IE. If a UE operating two or more USIMs, supports and intends to use one or more Multi-USIM features (see clause 4.3.33) in a PLMN, it shall indicate in the UE Core Network Capability for this USIM in this PLMN that it supports these one or more Multi-USIM features, i.e. by means of one or more of the Connection Release Supported, Paging Cause Indication for Voice Service Supported, Reject Paging Request Supported, Paging Timing Collision Control Supported, and Paging Restriction Supported. Otherwise, the UE with the capabilities of Multi-USIM features shall indicate these one or more Multi-USIM features are not supported. A UE not operating two or more USIMs shall indicate the Multi-USIM features are not supported. NOTE: It is not necessary for a UE operating two or more USIMs to use Multi-USIM features with all USIMs. If the UE supports Enhanced support of discontinuous network coverage for satellite access (see clause 4.3.18.1), then the UE shall indicate this in the UE Network Capability IE. To allow for the addition of future features, the MME shall store the UE Network Capability and the MS Network Capability even if either or both is larger than specified in TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [47]/TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [46], up to a maximum size of 32 octets for each IE. | 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.3 |
2,976 | 4.7.7c Change of the ciphering algorithm at PS Handover | For PS handover to A/Gb mode (see subclause 10.5.1.14 and 3GPP TS 44.060[ None ] [76]) the network shall either assign a GSM ciphering algorithm to be used in the target cell or deactivate ciphering in the target cell. The MS shall start to use the new GSM ciphering algorithm or deactivate ciphering upon an indication from the lower layers that the PS handover procedure has been successfully completed (see 3GPP TS 44.060[ None ] [76]) After PS handover to Iu mode (see 3GPP TS 25.331[ None ] [23c] and 3GPP TS 44.118[ None ] [111]) the network shall activate integrity protection and shall either assign a ciphering algorithm to be used in the target cell or deactivate ciphering in the target cell, using the security mode control procedure (3GPP TS 25.331[ None ] [23c] and 3GPP TS 44.118[ None ] [111]). If the GSM ciphering algorithm is changed at PS handover and the routing area updating procedure triggered by the PS handover procedure is not accepted by the network, the MS shall delete any GPRS ciphering key sequence number and proceed as specified in subclauses 4.7.5.1.4 and 4.7.5.2.4. If the routing area updating procedure fails, because the radio resources assigned in the new cell are released before the MS receives a ROUTING AREA UPDATE ACCEPT message, the MS shall delete any GPRS ciphering key sequence number and proceed as specified in subclauses 4.7.5.1.5 item b and 4.7.5.2.5, respectively. | 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.7c |
2,977 | D.6.3 UE policy section management result | The purpose of the UE policy section management result information element is to transfer from the UE to the PCF information about instructions for UE policy section management which the UE could not execute successfully. The UE policy section management result information element is coded as shown in figure D.6.3.1, figure D.6.3.2, figure D.6.3.3, figure D.6.3.4, figure D.6.3.5 and table D.6.3.1. The UE policy section management result information element has a minimum length of 12 octets and a maximum length of 65534 octets. Figure D.6.3.1: UE policy section management result information element Figure D.6.3.2: UE policy section management result contents Figure D.6.3.3: UE policy section management subresult Figure D.6.3.4: UE policy section management subresult contents Figure D.6.3.5: Result Table D.6.3.1: UE policy section management result information element | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | D.6.3 |
2,978 | 4.18.3.1 PFD Retrieval by the SMF | This procedure enables the SMF to retrieve PFDs for an Application Identifier from the NEF (PFDF) when a PCC rule with this Application Identifier is provided/activated and PFDs provided by the NEF (PFDF) are not available at the SMF. In addition, this procedure enables the SMF to retrieve PFDs from the NEF (PFDF)when the caching timer for an Application Identifier elapses and a PCC Rule for this Application Identifier is still active. The NEF (PFDF) retrieves the PFDs from UDR unless already available in NEF (PFDF). The SMF may retrieve PFDs for one or more Application Identifiers in the same Request. All PFDs related to an Application Identifier are provided in the response from the UDR to NEF (PFDF). Figure 4.18.3.1-1 PFD Retrieval by the SMF 1. SMF invokes the Nnef_PFDManagement_Fetch (Application Identifier (s)) to the NEF (PFDF). 2. NEF (PFDF) checks if the PFDs for the Application Identifier (s) are available in the NEF (PFDF), if available, the NEF (PFDF) skips to step 4. If not, the NEF (PFDF) invokes Nudr_DM_Query (Application Identifier (s)) to retrieve the PFD(s) from UDR. 3. The UDR provides a Nudr_DM_Query response (Application Identifier(s), PFD(s)) to the NEF (PFDF). 4. The NEF (PFDF) replies to the SMF with Nnef_PFDManagement_Fetch (Application Identifier(s), PFD(s)). | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.18.3.1 |
2,979 | 5.22.3 Invocation-related Priority Mechanisms | The generic mechanisms used based on invocation-related Priority Mechanisms for prioritised services are based an interaction with an Application Function and between the Application Function and the PCF over Rx/N5 interface. These mechanisms apply to mobile originated as well as mobile terminated SIP call/sessions (clause 5.21 of TS 23.228[ IP Multimedia Subsystem (IMS); Stage 2 ] [15]) and Priority PDU connectivity services including MPS for Data Transport Service. NOTE 1: Clause 5.21 of TS 23.228[ IP Multimedia Subsystem (IMS); Stage 2 ] [15] is applicable to 5GS, with the understanding that the term PCRF corresponds to PCF in the 5GS. Invocation-related mechanisms for Mobile Originations e.g. via SIP/IMS: - PCF: When an indication for a session arrives over the Rx/N5 Interface and the UE does not have priority for the signalling QoS Flow, the PCF derives the ARP and 5QI parameters, plus associated QoS characteristics as appropriate, of the QoS Flow for Signalling as per Service Provider policy as specified in clause 6.1.3.11 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]. - PCF: For sessions such as MPS, when establishing or modifying a QoS Flow for media as part of the session origination procedure, the PCF selects the ARP and 5QI parameters, plus associated QoS characteristics as appropriate, to provide priority treatment to the QoS Flow(s). - PCF: When all active sessions to a particular DN are released, and the UE is not configured for priority treatment to that particular PDU Session for a DN, the PCF will downgrade the IMS Signalling QoS Flows from appropriate settings of the ARP and 5QI parameters, plus associated QoS characteristics as appropriate, to those entitled by the UE based on subscription. Invocation-related mechanisms for Mobile Terminations e.g. via SIP/IMS: - PCF: When an indication for a session arrives over the Rx/N5 Interface, mechanisms as described above for Mobile Originations are applied. - UPF: If an IP packet arrives at the UPF for a UE that is CM-IDLE, the UPF sends a "Data Notification" including the information to identify the QoS Flow for the DL data packet to the SMF, as specified in clause 4.2.3.3 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. - SMF: If a " Data Notification" message arrives at the SMF for a QoS Flow associated with an ARP priority level value that is entitled for priority use, delivery of priority indication during the Paging procedure is provided by inclusion of the ARP in the N11 interface "N1N2MessageTransfer" message, as specified in clause 4.2.3.3 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. - AMF: If an "N1N2MessageTransfer" message arrives at the AMF containing an ARP priority level value that is entitled for priority use, the AMF handles the request with priority and includes the "Paging Priority" IE in the N2 "Paging" message set to a value assigned to indicate that there is an IP packet at the UPF entitled to priority treatment, as specified in clause 4.2.3.3 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. - SMF: For a UE that is not configured for priority treatment, upon receiving the "N7 Session Management Policy Modification" message from the PCF with an ARP priority level that is entitled for priority use, the SMF sends an "N1N2MessageTransfer" to update the ARP for the Signalling QoS Flows, as specified in clause 4.3.3.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. - AMF: Upon receiving the "N1N2MessageTransfer" message from the SMF with an ARP priority level that is entitled for priority use, the AMF updates the ARP for the Signalling QoS Flows, as specified in clause 4.3.3.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. - (R)AN: Inclusion of the "Paging Priority" in the N2 "Paging" message triggers priority handling of paging in times of congestion at the (R)AN as specified in clause 4.2.3.3 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. Invocation-related mechanisms for the Priority PDU connectivity services: - PCF: If the state of the Priority PDU connectivity services is modified from disabled to enabled, the QoS Flow(s) controlled by the Priority PDU connectivity services are established/modified to have the service appropriate settings of the ARP and 5QI parameters, plus associated QoS characteristics as appropriate, using the PDU Session Modification procedure as specified in clause 4.3.3 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. - PCF: If the state of Priority PDU connectivity services is modified from enabled to disabled, the QoS Flow(s) controlled by the Priority PDU connectivity services are modified from Priority PDU connectivity service appropriate settings of the ARP and 5QI parameters, plus associated QoS characteristics as appropriate, to those entitled by the UE as per subscription, using the PDU Session Modification procedure as specified in clause 4.3.3 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. Invocation-related mechanisms for MPS for Data Transport Service: - MPS for Data Transport Service follows the same steps as those for Priority PDU connectivity services. The QoS Flows that will be subject to MPS for Data Transport Service are based on operator policy and regulations by means of local PCF configuration. NOTE 2: If no configuration is provided, MPS for Data Transport Service applies to the QoS Flow associated with the default QoS rule. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.22.3 |
2,980 | 6.16.1 Security handling in Control Plane CIoT 5GS Optimization 6.16.2.1 General | The purpose of this procedure is to allow the ng-eNB to suspend an RRC connection to be resumed by the UE using User Plane CIoT 5GS Optimisation at a later time. The UE may resume the RRC connection in the same or different ng-eNB where the suspend took place. The UE and ng-eNB store the AS security context at suspend and reactivate the AS security context at resume. The UE and the ng-eNB may also use EDT (Early Data Transmission) or PUR (Preconfigured Uplink Resource) feature in this procedure, as defined in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [88] and TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [69]. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.16.1 |
2,981 | 20.5a.7 MBMS-Data-Transfer-Start AVP | The MBMS-Data-Transfer-Start AVP (AVP code 929) is of type Unsigned64. This value indicates the time in seconds for the radio resources set up relative to 00:00:00 on 1 January 1900 (calculated as continuous time without leap seconds and traceable to a common time reference) where binary encoding of the integer part is in the first 32 bits and binary encoding of the fraction part in the last 32 bits. The fraction part is expressed with a granularity of 1 /2**32 second. This AVP is only valid for E-UTRAN access type. | 3GPP TS 29.061 | Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) | CT WG3 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 20.5a.7 |
2,982 | 6.1.3.3.1 Synchronization failure or MAC failure in USIM | This clause describes synchronisation failure or MAC failure in USIM. In step 7 in Figure 6.1.3.2-1 when 5G AKA is used; or in step 5 in Figure 6.1.3.1-1 when EAP-AKAβ is used, at the receipt of the RAND and AUTN, if the verification of the AUTN fails, then the USIM indicates to the ME the reason for failure and in the case of a synchronisation failure passes the AUTS parameter (see TS 33.102[ 3G security; Security architecture ] [9]) to the ME. If 5G AKA is used: The ME shall respond with NAS message Authentication Failure with a CAUSE value indicating the reason for failure. In case of a synchronisation failure of AUTN (as described in TS 33.102[ 3G security; Security architecture ] [9]), the UE also includes AUTS that was provided by the USIM. Upon receipt of an authentication failure message, the AMF/SEAF may initiate new authentication towards the UE. (see TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [35]). If EAP-AKAβ is used: The ME shall proceed as described in RFC 4187 [21] and RFC 5448 [12] for EAP-AKAβ. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.1.3.3.1 |
2,983 | 4.25.3 NIDD Configuration | Figure 4.25.3-1 illustrates the procedure for configuring necessary information for data delivery via the NIDD API. The NIDD Configuration procedure can be NEF initiated or AF triggered: in the former case the procedure starts at step 1, in the latter case it starts at step 2. Figure 4.25.3-1: NIDD Configuration procedure 1. [Optional] If the NEF requires a NIDD configuration with a given AF, then the NEF sends a Nnef_NIDDConfiguration_TriggerNotify (GPSI, AF Identifier, NEF ID) message to the AF for asking the Nnef_NIDDConfiguration_Create Request for the UE identified by the GPSI. 2. The AF sends a Nnef_NIDDConfiguration_Create Request message (GPSI or External Group Identifier, AF Identifier, NIDD Duration, T8 Destination Address, Requested Action, TLTRI, Reliable Data Service Configuration, MTC Provider Information) to the NEF. Reliable Data Service Configuration is an optional parameter that is used to configure the Reliable Data Service (as defined in clause 5.31.6 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]) including port numbers for originator application(s) and receiver application(s). TLTRI is included in the request if the Requested Action is set to "Update" or "Cancel", otherwise TLTRI is not included in the request and the NEF assigns a TLTRI to the NIDD Configuration. If Reliable Data Service Configuration is present, the Reliable Data Service Configuration may include the mobile terminated and mobile originated serialization format(s) that are supported by the AF for each port number. NOTE 1: It is up to the AF to determine whether and if NIDD Duration can be set to never expire. NOTE 2: The AF is expected to be configured to use the same NEF as the one selected by the SMF during the UE's establishment of the PDU Session used for NEF based NIDD. NOTE 3: When more than one AF is associated with a PDU Session, the parameters that are provided in step 2 can be provisioned in the NEF based on operator policy or configuration. In which case, any parameters that are provided in step 2 that conflict with the provisioned values are ignored. NOTE 4: If the AF does not indicate a serialization format, it is assumed that the UE application is provisioned to know what serialization format will be used for MT traffic or that the AF will use the same format that is used by the associated MO traffic. 3. If the Requested Action is set to "Cancel" it indicates that the purpose of the request is to cancel the transaction identified by TLTRI and the flow proceeds to step 7. If the Requested Action is set to "Update", the purpose of the transaction is to update the parameters associated with the configuration (i.e. Reliable Data Service). Otherwise, the request is for a new NIDD configuration and the NEF stores the received GPSI or External Group Identifier, AF Identifier, T8 Destination Address and NIDD Duration. If either the AF is not authorised to perform this request (e.g. based on policies, if the SLA does not allow for it) or the Nnef_NIDDConfiguration_Create Request is malformed, the NEF performs step 7 and provides a Cause value appropriately indicating the error. Depending on the configuration, the NEF may change the NIDD Duration. 4. The NEF sends an Nudm_NIDDAuthorisation_Get Request (GPSI or External Group Identifier, S-NSSAI, DNN, AF Identifier, MTC Provider Information, NIDD Duration, Update Notification Address) message to the UDM to authorise the NIDD configuration request for the received External Group Identifier or GPSI. NOTE 5: The NEF uses the AF Identifier, External Group Identifier or GPSI that was obtained in step 2 to determine what DNN will be used to enable transfer of unstructured data between the UE and the AF. This determination is based on local policies. NOTE 6: The MTC Provider Information in step 2 is an optional parameter. The NEF should validate the provided MTC Provider Information and may override it to a NEF selected MTC Provider Information based on configuration. How the NEF determines the MTC Provider Information, if not present in step 2, is left to implementation (e.g. based on the requesting AF). 5. The UDM examines the Nudm_NIDDAuthorisation_Get Request message. If the authorisation is successful and if an External Group Identifier was included in step 4, the UDM maps the External Group Identifier to an Internal-Group Identifier and a list of GPSIs and maps GPSIs to SUPIs. NOTE 7: If External Group Identifier was included in step 4, how the UDM selects a GPSI when multiple GPSIs are associated with the same SUPI is left to implementation, e.g. based on the MTC Provider Information (if received) or the default GPSI (if not received). 6. The UDM sends an Nudm_NIDDAuthorisation_Get Response (single value or list of (SUPI and GPSI), Result) message to the NEF to acknowledge acceptance of the Nudm_NIDDAuthorisation_Get Request. If the UDM determines that the list size exceeds the message capacity, the UDM shall segment the list and send it in multiple messages (for details on segmentation, see TS 29.503[ 5G System; Unified Data Management Services; Stage 3 ] [52]). The SUPI(s) and if available, the GPSI(s) (when Nnef_NIDDConfiguration_Create Request contains an GPSI) are returned by the UDM in this response. This allows the NEF to correlate the AF request received in step 2 of this procedure with the SMF-NEF Connection to be established for each UE or each group member UE. Depending on the configuration (e.g. based on DNN), the UDM may change the NIDD Duration and include the updated value of the NIDD Duration in the response to the NEF. 7. The NEF sends a Nnef_NIDDConfiguration_Create Response (TLTRI, Maximum Packet Size, Reliable Data Service Indication and Cause) message to the AF to acknowledge acceptance of the Nnef_NIDDConfiguration_Create Request. If the NIDD Configuration was accepted, the NEF assigns a TLTRI to the NIDD Configuration and sends it to the AF. The NEF creates an association between the TLTRI, GPSI or External Group Identifier, SUPI and PDU session ID which is received from the SMF in step 2 of the SMF-NEF Connection procedure in clause 4.25.1. In the MT NIDD procedure, the NEF will use TLTRI and either GPSI or External Group Identifier to determine the SUPI(s) and PDU session ID(s) of PDU Session(s) for delivering unstructured data. In the MO NIDD procedure, the NEF will use the SUPI(s) and PDU session ID(s) to obtain the TLTRI, GPSI. The Reliable Data Service Indication indicates if the Reliable Data Service is enabled in the NIDD configuration. The Maximum Packet Size is the maximum NIDD packet size. The response may include an updated value of the NIDD Duration. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.25.3 |
2,984 | 10.5.6.3A Extended protocol configuration options | The purpose of the extended protocol configuration options information element is to: - transfer external network protocol options associated with a PDP context activation, and - transfer additional (protocol) data (e.g. configuration parameters, error codes or messages/events) associated with an external protocol or an application. The extended protocol configuration options is a type 6 information element with a minimum length of 4 octets and a maximum length of 65538 octets. The extended protocol configuration options information element is coded as shown in figure 10.5.6.3A.1 and table 10.5.6.3A.1. Figure 10.5.6.3A.1: Extended protocol configuration options information element Table 10.5.6.3A.1: Extended protocol configuration options information element | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 10.5.6.3A |
2,985 | 4.22.2.4.2 PDN Connections and Multi Access PDU Sessions | When the UE wants to request a new PDN Connection in EPC and wants to use this PDN Connection as user-plane resource associated with a MA PDU Session: - The UE requests establishment of a new PDN Connection when the UE is registered via non-3GPP access in EPS using PDN Connection Establishment procedure. The UE provides the following ATSSS information to ePDG via IKE signalling: - An indication that the PDN Connection is requested to be associated with a MA PDU Session - The UE's ATSSS capabilities as described in clause 5.32.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] (i.e. whether the UE is capable of supporting any combination of the ATSSS-LL functionality, the MPTCP functionality and the MPQUIC functionality). - The ePDG may select a PGW-C+SMF as described in TS 23.402[ Architecture enhancements for non-3GPP accesses ] [26]. The ePDG forwards the ATSSS information to the selected PGW-C+SMF via APCO in Create Session Request message. NOTE: The selection of PGW-C+SMF in the correct 5GC slice requires the same mapping between EPC and 5GC slices as required for single-access PDU sessions. In order to select an ATSSS capable PGW-C+SMF it is assumed that the operator deployment ensures that all PGW-C+SMF(s) configured to support the specific APN in this network slice are also capable to support ATSSS. There is however no assumption that all PGW-U+UPFs need to support ATSSS, since PGW-C+SMF can make a selection of PGW-U+UPF taking the multi-access properties into account. - The PGW-C+SMF determines based its capabilities whether the request can be accepted. The PCF decides whether the multi-access connectivity is allowed or not based on operator policy and subscription data, as described in clause 4.22.2. The PGW-C+SMF provides the following information via the APCO in the Create Session Response message to the ePDG: - An indication whether the request for using the PDN Connection for MA-PDU Session is accepted or not. - If the UE has indicated that it is capable of supporting the MPTCP functionality and the PGW-C+SMF accepts to activate the MPTCP functionality, then the network provides MPTCP proxy information to the UE, as described in clause 5.32.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. - If the UE has indicated that it is capable of supporting the MPQUIC functionality and the PGW-C+SMF accepts to activate the MPQUIC functionality, then the network provides MPQUIC proxy information to the UE, as described in clause 5.32.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. - UE Measurement Assistance Information (as described in clause 5.32.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]). - ATSSS rules - The ePDG forwards the received above information to the UE via IKE signalling. After the PDN Connection establishment: - If the UE registers to 5GC and wants to add 3GPP user-plane resources, then the UE shall send a PDU Session Establishment Request over this access containing a "MA PDU Request" indication as described in clause 5.32.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. When the UE wants to request a new MA PDU Session in 5GC/3GPP access, the description in clause 5.32.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], applies. After the MA PDU Session establishment in 5GC/3GPP access, the description in clause 5.32.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], applies with the following additions: - If the UE is registered to EPC and wants to add user-plane resources on non-3GPP access over EPC, then the UE shall send a PDN Connection Establishment Request over this access containing the IP address of the MA PDU Session in CFG_REQUEST Configuration Payload and include a "MA PDU Request" indication and UE's ATSSS capabilities and the PDU Session ID of the existing MA PDU Session on 3GPP access over 5GC. The ePDG forwards the ATSSS information via the APCO in the Create Session Request message to the PGW-C/SMF. - When the UE deregisters from the EPC/non-3GPP access (but remains registered on the 5GC/3GPP access), the ePDG will notify the PGW-C+SMF that the PDN Connection is released, as described in TS 23.402[ Architecture enhancements for non-3GPP accesses ] [26]. The SMF can then notify the UPF that the access type has become unavailable. A UE that has an established MA-PDU session over 3GPP access in 5GC and non-3GPP access in EPS, may be able to use Dual Connectivity for the 3GPP access leg. Depending on the RAT types supported by the UE, the PDU Session may also be handed over to 3GPP access in EPC. For a UE supporting both E-UTRAN/EPC access and NG-RAN/5GC access, the user plane resources for 3GPP access may be moved between E-UTRAN/EPC access and NG-RAN/5GC access as described in clause 5.17.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. For the MA PDU session over 3GPP access in 5GC and non-3GPP access in EPS, when a UE moves from NG-RAN/5GC to E-UTRAN/EPC, the SMF+PGW-C may release the user plane resources either over 3GPP access or non-3GPP access based on operator policy. In this case, while the UE remains in EPC in both 3GPP access and non-3GPP access, the UE shall not trigger PDN Connection establishment to add an additional EPC access leg to the MA PDU Session. If the SMF+PGW-C does not release the user plane resources over one of accesses, the UE sends traffic over both accesses based on ATSSS rules. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.22.2.4.2 |
2,986 | 6.41.2.6 Hosting Network Localized Services and Home Operator Services | The 5G system shall enable the home network operator to indicate to the UE what services are preferred to be used from the home network when the UE connects to a hosting network and the requested services are available from both the hosting and the home network. Based on localized service agreements, the hosting network shall be able to provide required connectivity and QoS for a UE simultaneously connected to the hosting network for localized services and its home network for home network services. A UE shall be able to connect to its home network via the hosting network, if supported by the hosting network and the home network based on localized service agreements. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.41.2.6 |
2,987 | 4.3.1.2.3 Successful outgoing inter-eNB handover executions per handover cause | This measurement provides the number of successful outgoing inter-eNB handovers per handover cause, the forwarded handovers for RN in DeNB are exclusive. CC. Receipt at the source eNB of UE CONTEXT RELEASE [10] over the X2 from the target eNB following a successful handover, or if handover is performed via S1, receipt of UE CONTEXT RELEASE COMMAND [9] at the source eNB following a successful handover, the forwarded X2AP UE CONTEXT RELEASE message and S1AP UE CONTEXT RELEASE COMMAND message for RN in DeNB are exclusive. Each X2AP UE CONTEXT RELEASE message or S1AP UE CONTEXT RELEASE COMMAND message received and counted is added to the relevant per handover cause measurement, the possible causes are included in TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [9]. The sum of all supported per cause measurements shall equal the total number of outgoing inter-eNB handover events. In case only a subset of per cause measurements is supported, a sum subcounter will be provided first. Each measurement is an integer value. The number of measurements is equal to the number of causes supported plus a possible sum value identified by the .sum suffix. HO.InterEnbOutSucc.Cause where Cause identifies the cause for handover. EUtranCellFDD EUtranCellTDD Valid for packet switched traffic EPS | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.3.1.2.3 |
2,988 | D.2.2.2 UE-initiated UE state indication procedure initiation | In order to initiate the UE-initiated UE state indication procedure, the UE shall create a UE STATE INDICATION message. The UE: a) shall allocate a PTI value currently not used and set the PTI IE to the allocated PTI value; b) if not operating in SNPN access operation mode, shall include the UPSI(s) of the UE policy section(s) which are identified by a UPSI with the PLMN ID part indicating the HPLMN or the selected PLMN available in the UE in the UPSI list IE, if any; NOTE 1: If the UE does not have any UE policy section which is identified by a UPSI with the PLMN ID part indicating the HPLMN or the selected PLMN, the UE sets the Length of UPSI list contents field in the UPSI list IE to zero. c) if operating in SNPN access operation mode, shall include UPSI(s) of the UE policy section(s) which are identified by a UPSI: - with the PLMN ID part indicating the MCC and MNC of the selected SNPN; and - associated with the NID of the selected SNPN; available in the UE in the UPSI list IE, if any; NOTE 2: If the UE does not have any UE policy section which is identified by a UPSI with the PLMN ID part indicating the MCC and MNC of the selected SNPN and associated with the NID of the selected SNPN, the UE sets the Length of UPSI list contents field in the UPSI list IE to zero. d) shall specify whether the UE supports ANDSP in the UE policy classmark IE; e) shall specify whether the UE supports URSP provisioning in EPS in the UE policy classmark IE; e1) if the UE supports VPS URSP, shall set the SVPSU bit to "VPS URSP supported by the UE" in the UE policy classmark IE; f) if the UE supports reporting URSP rule enforcement, shall set the SupportRURE bit to "Reporting URSP rule enforcement supported by the UE"; and g) may include the UE's one or more OS IDs in the UE OS Id IE. The UE shall send the UE STATE INDICATION message (see example in figure D.2.2.2.1). The UE shall transport the created UE STATE INDICATION message using the registration procedure (see subclause 5.5.1). Figure D.2.2.2.1: UE-initiated UE state indication procedure | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | D.2.2.2 |
2,989 | 8.1.2.12.3 Applicability rule and antenna connection for CA and DC tests | 8.1.2.12.3.1 Applicability rule and antenna connection for CA and DC tests with 2Rx All tests specified in 8.2 to 8.8 with 2Rx with CA, TDD-FDD CA and DC are tested with 8 Rx capable UEs. Within the CA/DC configuration if any of the PCell and/or the SCells and/or PSCells is a 2Rx supported RF band, the antenna connection should follow the same method as defined in 8.1.2.12.1 and 8.1.2.12.2 for single carrier tests on any of the 2Rx supported RF bands, with the same requirements specified with 2Rx applied. Within the CA configuration if any of the PCell and/or the SCells and/or PSCells is a 4Rx supported RF band, the antenna connection should follow the same as illustrated in Figure 8.1.2.12.1-1 and Figure 8.1.2.12.1-2 for single carrier tests on any of the 4 Rx supported RF bands, with the SNR requirements applied with 1.5dB less than the number specified with 2Rx. Within the CA configuration if any of the PCell and/or the SCells and/or PSCells is an 8Rx supported RF band, the antenna connection should follow the same as illustrated in Figure 8.1.2.12.1-1 and Figure 8.1.2.12.1-2 for single carrier tests on any of the 8Rx supported RF bands, with the SNR requirements applied with 3.0dB less than the number specified with 2Rx for PDSCH tests and 1.5dB less than the number specified with 2Rx for control channel tests. Same applicability rules defined in 8.1.2.3, 8.1.2.3A, and 8.1.2.3B for CA, TDD-FDD CA and DC applied for different CA and DC configurations and bandwidth combination sets should be applied for 8 Rx capable UEs. 8.1.2.12.3.2 Applicability rule and antenna connection for CA tests with 4Rx All tests specified in 8.13 with 4Rx with FDD CA/DC, TDD CA/DC and TDD-FDD CA/DC are tested with 8 Rx capable UEs. Within the CA/DC configuration if any of the PCell and/or the SCells and/or PSCells is a 4Rx supported RF band, the antenna connection should follow the same method as defined in 8.1.2.12.1 and 8.1.2.12.2 for single carrier tests on any of the 4Rx supported RF bands, with the same requirements specified with 4Rx applied. Within the CA configuration if any of the PCell and/or the SCells and/or PSCells is an 8Rx supported RF band, the antenna connection should follow the same as illustrated in Figure 8.1.2.12.1-3 and Figure 8.1.2.12.1-4 for single carrier PDSCH tests on any of the 8Rx supported RF bands, with the SNR requirements applied with 1.5dB less than the number specified with 4Rx for PDSCH tests, and with the same SNR requirements as specified with 4Rx applied for control channel test. Same applicability rules defined in 8.1.2.6.5 for CA, TDD-FDD CA and DC applied for different CA and DC configurations and bandwidth combination sets should be applied for 8 Rx capable UEs. 8.1.2.12.3.3 Applicability rule and antenna connection for CA tests with 8Rx All tests specified in 8.14.2 with 8Rx with TDD CA are tested with 8 Rx capable UEs. Within the CA configuration if any of the PCell and/or the SCells and/or PSCells is an 8Rx supported RF band, the antenna connection should follow the same method as defined in 8.1.2.12.1 for single carrier PDSCH tests on any of the 8Rx supported RF bands, with the same requirements specified with 8Rx applied. For 8Rx capable UEs supporting different CA configurations and bandwidth combination sets, the applicability and test rules are defined in Table 8.1.2.12.3-1 for TDD CA. For simplicity, CA configuration below refers to combination of CA configuration and bandwidth combination set. Table 8.1.2.12.3-1: Applicability and test rules for CA UE demodulation tests | 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.3 |
2,990 | 4.12a.4.2 Procedure for the UE context release in the TNGF | This procedure for releasing the N2 signalling connection and the N3 user plane connection for a UE connected to 5GC via trusted non-3GPP access, shall be the same as the procedure specified in clause 4.12.4.2 for the untrusted non-3GPP access with the following modifications: - The untrusted non-3GPP access is substituted by a trusted non-3GPP access point (TNAP). - The N3IWF is substituted by the TNGF. - If the UE has reserved any non-3GPP specific QoS resources, the UE releases these resources when the IKEv2 Child SA is released. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.12a.4.2 |
2,991 | 5.4.3 Security mode control procedure 5.4.3.1 General | The purpose of the NAS security mode control procedure is to take an EPS security context into use, and initialise and start NAS signalling security between the UE and the MME with the corresponding EPS NAS keys and EPS security algorithms. Furthermore, the network may also initiate the security mode control procedure in the following cases: - in order to change the NAS security algorithms for a current EPS security context already in use; - in order to change the value of uplink NAS COUNT used in the latest SECURITY MODE COMPLETE message as described in 3GPP TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [19], clause 7.2.9.2; and - in order to request the UE radio capability ID from the UE. For restrictions concerning the concurrent running of a security mode control procedure with other security related procedures in the AS or inside the core network see 3GPP TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [19], clause . | 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.3 |
2,992 | 10.2.3 Allocation principles | The default Individual CTSMSI contains the least significant portion of the IMSI. This is the default CTS-MS identity. Assigned CTSMSIs are allocated by the CTS-FP during enrolment, registration and other access procedures. Significant Part of the assigned CTSMSI shall be allocated in the range 00001-FFFFE. CTS-FP shall not allocate Significant Part equal to 00000 or to FFFFF and shall not allocate Assigned CTSMSI using Reserved Type value. Such assignments shall be ignored by the CTS-MS. Assigned CTSMSIs are allocated in ciphered mode. NOTE: The assigned individual CTSMSI should be updated whenever it is sent in clear text on the CTS radio interface during RR connection establishment. The value FFFFF from the set of Assigned Connectionless Group CTSMSI shall be considered in all CTS-MS as the value of the Connectionless Broadcast Identifier. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 10.2.3 |
2,993 | 5.2.19.2.4 Naf_EventExposure_Notify service operation | Service operation name: Naf_EventExposure_Notify Description: The AF provides the previously subscribed event information to the consumer NF which has subscribed to that event before. Input, Required: Notification Correlation Information, Event ID, corresponding UE ID(s) (either external UE ID(s), or Internal/External Group Identifier, or UE IP v4 address(es) or UE IP v6 prefix(es), time stamp. NOTE: UE ID includes GPSI or SUPI. Input, Optional: Event specific parameter list. Output, Required: None. Output, Optional: None. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.19.2.4 |
2,994 | 5.2.1.2 Transfer of CDRs via Ga | Upon receiving a charging event, the CDF uses the event to create/open a CDR (both event and session based charging), or to add information to an existing open CDR. As there is a 1:1 mapping between charging events and CDRs in event based charging, CDRs are created promptly after receiving and processing the event, and are then ready for transfer on to the CGF via the Ga reference point. In session based charging, a CDR is opened when the initial charging event, specifying the start of a user session, is received. Information is added to the CDR upon receiving interim charging events. The CDR may be closed due to a number of reasons configured on the CDF or dependent on implementation, including but not limited to: - time limit; - volume limit; - limit of change of charging conditions; - end of user session, e.g. reception of the final charging event describing the session termination; - limits (e.g. memory size) imposed by implementation. The CDR generation could be suppressed to limit the number of CDRs based on operator configuration. When a CDR is closed and the session is still active, a subsequent CDR is opened. Hence multiple "partial CDRs" may be needed to completely describe the session. This implies that opening and closure of CDRs may occur completely asynchronously to the reception of the charging events. The size of partial CDRs could be optionally reduced by allowing a reduced format for partial CDRs, implying that some information can be eliminated rather than repeated in all the partial CDRs. This means that only changes from one CDR to the next, in addition to mandatory information, is reported. All the missing information can be reconstructed from fields in previous partial CDRs. For example, if location information is captured in CDRs but the user did not change location, the corresponding partial CDR would not include any location information. Therefore, two formats are considered for Partial CDRs: - a Fully Qualified Partial CDR that contains the complete set of CDR Fields, and - a Reduced Partial CDR that contains all the Mandatory fields (M) and ONLY the changes that occurred in any other field relative to the previous partial CDR. The first CDR generated when a session is opened shall be a Fully Qualified Partial CDR. Subsequent partial CDRs may be Reduced Partial CDRs. Thus, the convention is that when any non-mandatory field is missing from a Reduced Partial CDR, it should be interpreted that the same field as in the previous partial CDR could be used. Refer to clause 5.4 for the definition of "mandatory" and other CDR field categories. All CDFs and CGFs from all vendors shall be able to generate or receive Fully Qualified Partial CDRs. Generation and reception of Reduced Partial CDRs on the Ga interface is optional. However, if Reduced Partial CDRs are transmitted on the Ga interface they must comply with the rules specified in this clause. If the CDFs are generating Reduced Partial CDRs on the Ga interface, the CGF must be able to convert the CDRs into Fully Qualified Partial CDRs. However, if according to operator choice, the BD can support Reduced Partial CDRs, no conversion to the Fully Qualified Partial CDR format is required. The possible charging configurations that can be supported on both the Ga and the Bx interfaces are illustrated in figure 5.2.1.2.1. Configuration a) is the default arrangement that MUST be supported by all systems. The other configurations are optional and may be supported IN ADDITION to configuration a). Configuration b) illustrates the case where the CGF is converting Reduced to Fully Qualified Partial CDRs. Configuration c) depicts the case were Reduced Partial CDRs can be received in the BD and no conversion is needed. Figure 5.2.1.2.1: Possible Configurations of Ga and Bx CDR Formats When a CDR is closed, it is immediately transferred to the CGF. The exact timing may be determined by configuration parameters of the protocol used on The CDF shall be capable of receiving and processing charging events and generating and forwarding the resulting CDRs in near real-time. Details on the protocol application for the open Ga interface can be found in TS 32.295[ Telecommunication management; Charging management; Charging Data Record (CDR) transfer ] [54]. The semantics and formal description of the CDR parameters are specified in TS 32.298[ Telecommunication management; Charging management; Charging Data Record (CDR) parameter description ] [51]. | 3GPP TS 32.240 | Telecommunication management; Charging management; Charging architecture and principles | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 5.2.1.2 |
2,995 | 9.7.2.3 FDD (Category 1bis UE) | The following requirements apply to UE DL Category 1bis. For the parameters specified in Table 9.7.2.3-1, and using the downlink physical channels specified in Annex C.3.2, the minimum requirements are specified in Table 9.7.2.3-2 and by the following a) a sub-band differential CQI offset level of 0 shall be reported at least ο‘ % of the time but less than ο’ο % for each sub-band; 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 β₯ ο§; c) when transmitting on a randomly selected sub-band among the sub-bands with the highest differential CQI offset level the corresponding TBS, the average BLER for the indicated transport formats shall be greater or equal to 0.05. 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. Table 9.7.2.3-1 Sub-band test for single antenna transmission (FDD) Table 9.7.2.3-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.7.2.3 |
2,996 | 4.15.6.3g Network Slice Usage Control parameters for dedicated S-NSSAI to a single AF | An AF having a S-NSSAI dedicated to it may be authorized, to control the parameters to remove the S-NSSAI from the Allowed NSSAI or release a PDU Session associated with the S-NSSAI. In this case, these parameters may be provided by an authorized AF via the NEF and be stored as part of the subscriber data. The provision procedure of the Network Slice Usage Control Parameters is realized by external parameter provision procedure as described in clause 4.15.6.2. The AMF and SMF use the Network Slice Usage Control parameter as described in clause 5.15.15 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. Table 4.15.6.3g-1: Description of Network Slice Usage Control parameters According to the received network slice usage control parameter, the UDM updates all related UE subscription data which includes the indicated S-NSSAI. Only in this case and for subscribers having such an S-NSSAI a subscribed S-NSSAI, the slice deregistration inactivity timer value and/or PDU Session inactivity timer value is obtained by the AMF or SMF as part of the subscription data respectively as specified in clauses 4.2.2.2.2 and 4.3.2.2.1. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.15.6.3g |
2,997 | 9.6.1.1 FDD | The following requirements apply to UE Category β₯3. For CA with 2 DL CC, for the parameters specified in Table 9.6.1.1-1 and Table 9.6.1.1-2, and using the downlink physical channels specified in tables C.3.2-1 and C.3.2-2 on each cell, the difference between the wideband CQI indices of Pcell and Scell reported shall be such that wideband CQIPcell β wideband CQIScell β₯ 2 for more than 90% of the time. Table 9.6.1.1-1: Parameters for PUCCH 1-0 static test on multiple cells (FDD, 2 DL CA) Table 9.6.1.1-2: PUCCH 1-0 static test (FDD, 2 DL CA) The following requirements for 3DL CA apply to UE Category β₯5. For CA with 3 DL CC, for the parameters specified in Table 9.6.1.1-3 and Table 9.6.1.1-4, and using the downlink physical channels specified in tables C.3.2-1 and C.3.2-2 on each cell, the difference between the wideband CQI indices of PCell and SCell1 reported, and the difference between the wideband CQI indices of SCell 1 and SCell2 reported shall be such that wideband CQIPCell β wideband CQISCell1 β₯ 2 wideband CQISCell1 β wideband CQISCell2 β₯ 2 for more than 90% of the time. The following requirements for 4DL CA apply to UE Category β₯8. For CA with 4 DL CC, for the parameters specified in Table 9.6.1.1-3 and Table 9.6.1.1-5, and using the downlink physical channels specified in tables C.3.2-1 and C.3.2-2 on each cell, the difference between the wideband CQI indices of PCell and SCell1 reported, and the difference between the wideband CQI indices of SCell 1 and SCell2, and SCell 1 and SCell 3 reported shall be such that wideband CQIPCell β wideband CQISCell1 β₯ 2 wideband CQISCell1 β wideband CQISCell2 β₯ 2 wideband CQISCell1 β wideband CQISCell3 β₯ 2 for more than 90% of the time. Table 9.6.1.1-3: Parameters for PUCCH 1-0 static test on multiple cells (FDD, 3 and 4 DL CA) Table 9.6.1.1-4: PUCCH 1-0 static test (FDD, 3 DL CA) Table 9.6.1.1-5: PUCCH 1-0 static test (FDD, 4 DL CA) The following requirements for 5DL CA apply to UE Category 8 and β₯11. For CA with 5 DL CC, for the parameters specified in Table 9.6.1.1-6 and Table 9.6.1.1-7, and using the downlink physical channels specified in tables C.3.2-1 and C.3.2-2 on each cell, the difference between the wideband CQI indices of PCell and SCell1 reported, and the difference between the wideband CQI indices of SCell 1 and SCell2, SCell 1 and SCell 3, and SCell 1 and SCell 4 reported shall be such that wideband CQIPCell β wideband CQISCell1 β₯ 2 wideband CQISCell1 β wideband CQISCell2 β₯ 2 wideband CQISCell1 β wideband CQISCell3 β₯ 2 wideband CQISCell1 β wideband CQISCell4 β₯ 2 for more than 90% of the time. Table 9.6.1.1-6: Parameters for PUCCH 1-0 static test on multiple cells (FDD, 5 DL CA) Table 9.6.1.1-7: PUCCH 1-0 static test (FDD, 5 DL CA) The following requirements for 6DL CA apply to UE Category 8 and β₯11. For CA with 6 DL CC, for the parameters specified in Table 9.6.1.1-8 and Table 9.6.1.1-9, and using the downlink physical channels specified in tables C.3.2-1 and C.3.2-2 on each cell, the difference between the wideband CQI indices of PCell and SCell1 reported, and the difference between the wideband CQI indices of SCell 1 and SCell2, SCell 1 and SCell 3, SCell 1 and SCell 4, and SCell 1 and SCell 5 reported shall be such that wideband CQIPCell β wideband CQISCell1 β₯ 2 wideband CQISCell1 β wideband CQISCell2 β₯ 2 wideband CQISCell1 β wideband CQISCell3 β₯ 2 wideband CQISCell1 β wideband CQISCell4 β₯ 2 wideband CQISCell1 β wideband CQISCell5 β₯ 2 for more than 90% of the time. Table 9.6.1.1-8: Parameters for PUCCH 1-0 static test on multiple cells (FDD, 6 DL CA) Table 9.6.1.1-9: PUCCH 1-0 static test (FDD, 6 DL CA) The following requirements for 7DL CA apply to UE Category 8 and β₯11. For CA with 7 DL CC, for the parameters specified in Table 9.6.1.1-10 and Table 9.6.1.1-11, and using the downlink physical channels specified in tables C.3.2-1 and C.3.2-2 on each cell, the difference between the wideband CQI indices of PCell and SCell1 reported, and the difference between the wideband CQI indices of SCell 1 and SCell2, SCell 1 and SCell 3, SCell 1 and SCell 4, SCell 1 and SCell 5, and SCell 1 and SCell 6 reported shall be such that wideband CQIPCell β wideband CQISCell1 β₯ 2 wideband CQISCell1 β wideband CQISCell2 β₯ 2 wideband CQISCell1 β wideband CQISCell3 β₯ 2 wideband CQISCell1 β wideband CQISCell4 β₯ 2 wideband CQISCell1 β wideband CQISCell5 β₯ 2 wideband CQISCell1 β wideband CQISCell6 β₯ 2 for more than 90% of the time. Table 9.6.1.1-10: Parameters for PUCCH 1-0 static test on multiple cells (FDD, 7 DL CA) Table 9.6.1.1-11: PUCCH 1-0 static test (FDD, 7 DL CA) | 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.6.1.1 |
2,998 | 9.11.4.8 Mapped EPS bearer contexts | The purpose of the mapped EPS bearer contexts information element is to indicate a set of EPS bearer contexts for a PDU session, as described in subclause 6.1.4.1. The mapped EPS bearer contexts information element is a type 6 information element with a minimum length of 7 octet and a maximum length of 65538 octets. The mapped EPS bearer contexts information element is coded as shown in figure 9.11.4.8.1, figure 9.11.4.8.2, figure 9.11.4.8.3 and table 9.11.4.8.1. Figure 9.11.4.8.1: Mapped EPS bearer contexts Figure 9.11.4.8.2: Mapped EPS bearer context Figure 9.11.4.8.3: EPS parameters list Table 9.11.4.8.1: Mapped EPS bearer contexts information element | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.11.4.8 |
2,999 | 28.7.6 NAI used for 5G registration via trusted non-3GPP access | While performing the EAP-authentication procedure when a UE attempts to register to 5GCN via a trusted non-3GPP access network in a selected PLMN (see clause 4.12a in 3GPP TS 23.502[ Procedures for the 5G System (5GS) ] [120]), the UE shall derive a NAI from the identity of the selected PLMN in the following format: "<any_non_null_string>@nai.5gc.mnc<MNC>.mcc<MCC>.3gppnetwork.org" where: a) the username part <any_non_null_string> is any non null string; and b) the <MNC> and <MCC> identify the PLMN (either HPLMN or VPLMN) to which the UE attempts to connect via the trusted non-3GPP access network as described in clause 6.3.12 in 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [119]. While performing the EAP-authentication procedure when a UE attempts to register to 5GCN via a trusted non-3GPP access network in a selected SNPN (see clause 5.30.2.13 in 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [119]), the UE shall derive a NAI from the identity of the selected SNPN in the following format: "<any_non_null_string>@nai.5gc.nid<NID>.mnc<MNC>.mcc<MCC>.3gppnetwork.org"; where: a) the username part <any_non_null_string> is any non null string; and b) the <MNC>, <MCC> and <NID> identify the SNPN to which the UE attempts to connect via the trusted non-3GPP access network. While performing the EAP authentication procedure when a UE attempts to register to 5GCN via a trusted non-3GPP access network in a selected TNGF, the UE shall derive NAI from the identity of the selected TNGF in the following format: "<any_non_mull_string>@tngfid<TNGF ID>.nai.5gc.mnc<MNC>.mcc<MCC>.3gppnetwork.org"; where: a) The username part <any_non_mull_string> is any non null string; and b) The <MNC> and <MCC> identify the PLMN (either HPLMN or VPLMN) to which the UE attempts to connect via the trusted non-3GPP access network; and c) <TNGF ID> identifies the TNGF. The TNGF ID value shall comply with the syntax specified in clause 2.2 of IETF RFC 7542 [126] for a label in the realm part of a NAI. While performing the EAP-authentication procedure when a UE attempts to register to 5GCN via a trusted non-3GPP access network in a selected SNPN and TNGF, the UE shall derive a NAI from the identity of the selected SNPN and TNGF in the following format: "<any_non_null_string>@tngfid<TNGF ID>.nai.5gc.nid<NID>.mnc<MNC>.mcc<MCC>.3gppnetwork.org"; where: a) the username part <any_non_null_string> is any non null string; and b) the <MNC>, <MCC> and <NID> identify the SNPN to which the UE attempts to connect via the trusted non-3GPP access network; and c) <TNGF ID> identifies the TNGF. The TNGF ID value shall comply with the syntax specified in clause 2.2 of IETF RFC 7542 [126] for a label in the realm part of a NAI. NOTE 1: The username part of the NAI is not used to identify the UE since the UE is identified by its NAS registration to the 5GCN independent of using the NAI. The realm part of the NAI is however used by the trusted non-3GPP access for TNGF selection. NOTE 2: In case of 5GCN, there is no need for a decorated NAI as in EPC (see clause 19.3.3), since the UE sends a NAS registration request to the PLMN including a SUCI or 5G-GUTI. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 28.7.6 |
3,000 | 5.3.4.3.2 Successful completion of in-call modification | If the destination network/mobile station receives a MODIFY message with a new mode which is already the actual one of the call the network/mobile station shall remain in the "active" state; send a MODIFY COMPLETE message with the actual mode; and shall not initiate anything else. If the requested mode is speech and if during call establishment the network received a Supported Codec List IE, the network shall use this list to select the codec for UTRAN. If no Supported Codec List information element is received, then for UTRAN the network shall select the default UMTS speech codec according to subclause 5.2.1.11. Codecs for GERAN shall be selected from the codecs indicated in the Supported Codec List information element or in the Bearer Capability information element. If neither a Supported Codec List information element nor a Bearer Capability information element is received, then for GERAN the network shall select GSM full rate speech version 1. If the Supported Codec List IE is received, then the network shall indicate the codec selected for Iu mode to the mobile station via RANAP and RRC protocol in the NAS Synchronisation Indicator IE (see subclause 5.2.1.11). If the in-call modification was originated by the mobile station, the mobile station and the network shall proceed as follows: If the requested mode is not the actual one and can be supported by the network it shall change the channel configuration, if required, and step on to any internal resources necessary to support the next call mode. If the requested mode is a data or facsimile mode, it shall also perform the appropriate means to take the direction of the data call into account. After successful change of the channel configuration it shall start sending user information according to the next call mode and start interpreting received user channel information according to the next call mode; send a MODIFY COMPLETE message with the new call mode included and enter the "active" state (network side). If the MODIFY message had contained a reverse call setup direction IE, the same IE shall be included in the MODIFY COMPLETE message. Upon receipt of the MODIFY COMPLETE message the mobile station shall: initiate the alternation to those resources necessary to support the next call mode; stop timer T323; and enter the "active" state (mobile station side). If the in-call modification was originated by the network, the mobile station and the network shall proceed as follows: If the requested mode is not the actual one and can be supported by the mobile station it shall reserve any internal resources necessary to support the next call mode. NOTE: For a change from speech to a different call mode, user interaction may be required, before the mobile decides that the requested mode can be supported. If the requested mode is a data or facsimile mode, it shall also perform the appropriate means to take the direction of the data call into account. The mobile station shall send a MODIFY COMPLETE message with the new call mode included, stop timer T324 and enter the "active" state (mobile station side). If the MODIFY message had contained a reverse call setup direction IE, the same IE shall be included in the MODIFY COMPLETE message. If the old call mode is speech, the mobile station shall continue sending Bm-channel information and interpreting received Bm-channel information for speech until the network modifies its channel configuration. After receipt of the MODIFY COMPLETE message the network shall: reserve any internal resources necessary to support the next call mode, stop sending Bm-channel information, and stop interpreting received Bm-channel information according to the old call mode, unless these actions were already performed earlier. Furthermore, the network shall change the channel configuration, if required; after successful change of the channel configuration initiate the alternation to those resources necessary to support the next call mode; stop timer T323; and enter the "active" state (network side). The mobile station shall start sending user information according to the next call mode and start interpreting received user channel information according to the next call mode as soon as a suitable channel for the new mode is available. In both cases: For an alternate speech/facsimile group 3 service (refer to subclause 5.3.4) the old resources may still be kept reserved. The reaction of the originating side if it had included a reverse call setup direction IE in the MODIFY message, but the destination side did not include the IE in the MODIFY COMPLETE message is implementation dependent. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.3.4.3.2 |
Subsets and Splits
No saved queries yet
Save your SQL queries to embed, download, and access them later. Queries will appear here once saved.