Search is not available for this dataset
doc_id
int64 1
6.72k
β | Section
stringlengths 5
247
β | Content
stringlengths 501
147k
β | Source
stringclasses 456
values | Document Title
stringclasses 22
values | Working Group
stringclasses 21
values | Series Subject
stringclasses 9
values | Subclause
stringlengths 1
13
β |
|---|---|---|---|---|---|---|---|
6,501 | 4.2 Architecture reference model 4.2.1 General | This specification describes the architecture for the 5G System. The 5G architecture is defined as service-based and the interaction between network functions is represented in two ways. - A service-based representation, where network functions (e.g. AMF) within the Control Plane enables other authorized network functions to access their services. This representation also includes point-to-point reference points where necessary. - A reference point representation, shows the interaction exist between the NF services in the network functions described by point-to-point reference point (e.g. N11) between any two network functions (e.g. AMF and SMF). Service-based interfaces are listed in clause 4.2.6. Reference points are listed in clause 4.2.7. Network functions within the 5GC Control Plane shall only use service-based interfaces for their interactions. NOTE 1: The interactions between NF services within one NF are not specified in this Release of the specification. NFs and NF services can communicate directly, referred to as Direct Communication, or indirectly via the SCP, referred to as Indirect Communication. For more information on communication options, see Annex E and clauses under 6.3.1 and 7.1.2. In addition to the architecture descriptions in clause 4, the following areas are further described in other specifications: - NG-RAN architecture is described in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [27] and TS 38.401[ NG-RAN; Architecture description ] [42]. - Security architecture is described in TS 33.501[ Security architecture and procedures for 5G System ] [29] and TS 33.535[ Authentication and Key Management for Applications (AKMA) based on 3GPP credentials in the 5G System (5GS) ] [124]. - Charging architecture is described in TS 32.240[ Telecommunication management; Charging management; Charging architecture and principles ] [41]. - 5G Media streaming architecture is described in TS 26.501[ 5G Media Streaming (5GMS); General description and architecture ] [135]. NOTE 3: The NFs listed in clause 4.2.2 are described in the following clauses or in the specifications above. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.2 |
6,502 | 5.8.11 Zone identity calculation | The UE shall determine an identity of the zone (i.e. Zone_id) in which it is located using the following formulae, if sl-ZoneConfig is configured: x1= Floor (x / L) Mod 64; y1= Floor (y / L) Mod 64; Zone_id = y1 * 64 + x1. The parameters in the formulae are defined as follows: L is the value of sl-ZoneLength included in sl-ZoneConfig; x is the geodesic distance in longitude between UE's current location and geographical coordinates (0, 0) according to WGS84 model [58] and it is expressed in meters; y is the geodesic distance in latitude between UE's current location and geographical coordinates (0, 0) according to WGS84 model [58] and it is expressed in meters. NOTE: How the calculated zone_id is used is specified in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3]. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.8.11 |
6,503 | 9.2.2.6 Resume request responded with Release with Redirect, with UE context relocation | The following figure describes a UE triggered NAS procedure responded by the network with a release with redirect, with UE context relocation. Figure 9.2.2.6-1: Resume request responded with Release with Redirect, with UE Context relocation 1. The UE resumes from RRC_INACTIVE, providing the I-RNTI allocated by the last serving gNB. 2. The gNB, if able to resolve the gNB identity contained in the I-RNTI, requests the last serving gNB to provide UE Context data. 3. The last serving gNB provides the UE context. 4. The gNB may move the UE to RRC_CONNECTED (and the procedure follows step 4 of Figure 9.2.2.4.1-1), or send the UE back to RRC_IDLE (in which case an RRCRelease message is sent by the gNB), or send the UE back to RRC_INACTIVE, including a release with redirect indication (as assumed in the following). 5. If loss of DL user data buffered in the last serving gNB shall be prevented, the gNB provides forwarding addresses. 6./7. The gNB performs path switch. 8. The gNB keeps the UE in RRC_INACTIVE state by sending RRCRelease with suspend indication, including redirection information (frequency layer the UE performs cell selection upon entering RRC_INACTIVE). 9. The gNB triggers the release of the UE resources at the last serving gNB. NOTE1: Upon receiving the release with redirect, the higher layers trigger a pending procedure so the UE tries to resume again after cell selection. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 9.2.2.6 |
6,504 | 5.5.4.24 Event A3H2 (Neighbour becomes offset better than SpCell and the Aerial UE altitude becomes lower than a threshold) | The UE shall: 1> consider the entering condition for this event to be satisfied when both condition A3H2-1 and condition A3H2-2, as specified below, are fulfilled; 1> consider the leaving condition for this event to be satisfied when condition A3H2-3 or condition A3H2-4, i.e. at least one of the two, as specified below, is fulfilled; 1> use the SpCell for Mp, Ofp and Ocp. NOTE: The cell(s) that triggers the event has reference signals indicated in the measObjectNR associated to this event which may be different from the NR SpCell measObjectNR. Inequality A3H2-1 (Entering condition 1) Mn + Ofn + Ocn β Hys1 > Mp + Ofp + Ocp + Off Inequality A3H2-2 (Entering condition 2) Ms + Hys2 < Thresh Inequality A3H2-3 (Leaving condition 1) Mn + Ofn + Ocn + Hys1 < Mp + Ofp + Ocp + Off Inequality A3H1-4 (Leaving condition 2) Ms β Hys > Thresh The variables in the formula are defined as follows: Mn is the measurement result of the neighbouring cell, not taking into account any offsets. Ofn is the measurement object specific offset of the reference signal of the neighbour cell (i.e. offsetMO as defined within measObjectNR corresponding to the neighbour cell). Ocn is the cell specific offset of the neighbour cell (i.e. cellIndividualOffset as defined within measObjectNR corresponding to the frequency of the neighbour cell), and set to zero if not configured for the neighbour cell. Mp is the measurement result of the SpCell, not taking into account any offsets. Ofp is the measurement object specific offset of the SpCell (i.e. offsetMO as defined within measObjectNR corresponding to the SpCell). Ocp is the cell specific offset of the SpCell (i.e. cellIndividualOffset as defined within measObjectNR corresponding to the SpCell), and is set to zero if not configured for the SpCell. Hys1 is the hysteresis parameter for this event (i.e. a3-Hysteresis as defined within reportConfigNR for this event). Off is the offset parameter for this event (i.e. a3-Offset as defined within reportConfigNR for this event). Ms is the Aerial UE altitude relative to the sea level. Hys2 is the hysteresis parameter for this event (i.e. h2-Hysteresis as defined within reportConfigNR for this event). Thresh is the threshold parameter for this event (i.e. h2-Threshold as defined within reportConfigNR for this event). Mn, Mp are expressed in dBm in case of RSRP, or in dB in case of RSRQ and RS-SINR. Ofn, Ocn, Hys1, Ofp, Ocp, Off are expressed in dB. Ms, Hys2, Thresh are expressed in meters. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.5.4.24 |
6,505 | 9.1.1.3 Test coverage for different number of componenet carriers | For FDD CA tests specified in 9.6.1.1, among all supported CA capabilities, if corresponding CA tests with the largest number of CCs supported by the UE are tested, the test coverage can be considered fulfilled without executing the CA tests with less than the largest number of CCs supported by the UE. For TDD CA tests specified in 9.6.1.2, among all supported CA capabilities, if corresponding CA tests with the largest number of CCs supported by the UE are tested, the test coverage can be considered fulfilled without executing the CA tests with less than the largest number of CCs supported by the UE. For TDD FDD CA tests specified in 9.6.1.3 and 9.6.1.4, among all supported CA capabilities, if corresponding CA tests with the largest number of CCs supported by the UE are tested, the test coverage can be considered fulfilled without executing the TDD FDD CA tests with less than the largest number of CCs supported by the 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 | 9.1.1.3 |
6,506 | 4.23.17 Additional considerations for Home-routed roaming | As described in clause 4.23.1, the procedures in clause 4.23 apply for home-routed roaming scenarios with V-SMF insertion/removal/change (i.e. by replacing the I-SMF with V-SMF and SMF with H-SMF). Differences compared to the procedures for I-SMF are described below: - The Registration procedure as defined in clause 4.23.3 with the following additions: - Step 8a of clause 4.23.4.3 (for cases d and e): the new V-SMF provides the QoS constraints of the VPLMN to H-SMF. - Step 8c of clause 4.23.4.3 (for cases d and e): the new V-SMF may apply VPLMN QoS policies as described in TS 23.501[ System architecture for the 5G System (5GS) ] [2], clause 5.7.1.11. - Inter NG-RAN node N2 based handover with V-SMF insertion/change as defined in clause 4.23.7.3 (i.e. by replacing the I-SMF with V-SMF) with the following additions: - Preparation phase, step 4b (for case V-SMF change): the target V-SMF may apply VPLMN QoS policies as described in TS 23.501[ System architecture for the 5G System (5GS) ] [2], clause 5.7.1.11. - Preparation phase, step 5d (for case V-SMF insertion): the target V-SMF may apply VPLMN QoS policies as described in TS 23.501[ System architecture for the 5G System (5GS) ] [2], clause 5.7.1.11. - Execution phase, step 6 (for case V-SMF change/insertion): the target V-SMF provides the QoS constraints of the VPLMN to H-SMF. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.23.17 |
6,507 | 6.5.1.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 behave as follows: 1) if the PDN CONNECTIVITY REQUEST message was sent standalone, the UE shall 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 and an APN was included in the PDN CONNECTIVITY REQUEST message, the UE shall stop timer T3396 associated with the corresponding APN, if it is running. If the timer value indicates neither zero nor deactivated, no APN was included in the PDN CONNECTIVITY REQUEST message 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 it is running. The UE shall then start timer T3396 with the value provided in the Back-off timer value IE and: - 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 that was sent by the UE, until timer T3396 expires or timer T3396 is stopped; and - 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 for a non-emergency PDN connection established without an APN provided by the UE, if no APN was included in the PDN CONNECTIVITY REQUEST message and the request type was different from "emergency" and from "handover of emergency bearer services", 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; and - 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 an APN provided by the UE, if no APN was included in the PDN CONNECTIVITY REQUEST message and the request type was different from "emergency" and from "handover of emergency bearer services", 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; and 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 no APN was included in the PDN CONNECTIVITY REQUEST message 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; and 2) if the PDN CONNECTIVITY REQUEST message was sent together with an ATTACH REQUEST, the UE shall take different actions depending on the timer value received for timer T3396 in the Back-off timer value IE and on the integrity protection of the ATTACH REJECT message (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 ATTACH REJECT message is not integrity protected and an APN was sent by the UE during the attach procedure, the UE shall stop timer T3396 associated with the corresponding APN if it is running. If the ATTACH REJECT message is not integrity protected, the request type was different from "emergency" and from "handover of emergency bearer services", and an APN was not sent by the UE, the UE shall stop timer T3396 associated with no APN if it is running. The UE shall then start timer T3396 with a random value from a default range specified in table 11.2.3 defined in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13], and: a) shall not initiate a new attach procedure with the same APN or send another PDN CONNECTIVITY REQUEST with the same APN that was sent by the UE, until timer T3396 expires or timer T3396 is stopped; and b) shall not initiate a new attach procedure without an APN and with request type different from "emergency" and from "handover of emergency bearer services" or send another PDN CONNECTIVITY REQUEST without an APN and with request type different from "emergency" and from "handover of emergency bearer services", if the UE did not provide any APN during the attach procedure and the request type was different from "emergency" and from "handover of emergency bearer services", until timer T3396 expires. The UE shall not stop timer T3396 upon a PLMN change or inter-system change; ii) if the ATTACH REJECT message is integrity protected, the UE shall proceed as follows: a) if the timer value indicates neither zero nor deactivated and an APN was sent by the UE during the attach procedure, the UE shall stop timer T3396 associated with the corresponding APN if it is running. If the timer value indicates neither zero nor deactivated, the request type was different from "emergency" and from "handover of emergency bearer services", and an APN was not sent by the UE during the attach procedure, the UE shall stop timer T3396 associated with no APN if it is running. The UE shall then start timer T3396 with the value provided in the Back-off timer value IE and: - shall not initiate a new attach procedure with the same APN or send another PDN CONNECTIVITY REQUEST with the same APN that was sent by the UE, until timer T3396 expires or timer T3396 is stopped; and - shall not initiate a new attach procedure without an APN and with request type different from "emergency" and from "handover of emergency bearer services" or send another PDN CONNECTIVITY REQUEST without an APN and with request type different from "emergency" and from "handover of emergency bearer services", if the UE did not provide any APN during the attach procedure and the request type was different from "emergency" and from "handover of emergency bearer services", until timer T3396 expires. The UE shall not stop timer T3396 upon a PLMN change or inter-system change; b) if the timer value indicates that this timer is deactivated, the UE: - shall not initiate a new attach procedure with the same APN or send another PDN CONNECTIVITY REQUEST with the same APN that was sent 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 message for the same APN from the network; and - shall not initiate a new attach procedure without an APN and with request type different from "emergency" and from "handover of emergency bearer services" or send another PDN CONNECTIVITY REQUEST without an APN and with request type different from "emergency" and from "handover of emergency bearer services", if the UE did not provide any APN during the attach procedure and the request type was different from "emergency" and from "handover of emergency bearer services", until the UE is switched off or the USIM is removed, or the UE receives an ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message for 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; and c) if the timer value indicates that this timer is zero, the UE shall proceed as specified in clause 5.5.1.2.6 item d. If the Back-off timer value IE is not included and the PDN CONNECTIVITY REQUEST was sent standalone, then the UE may send another PDN CONNECTIVITY REQUEST, BEARER RESOURCE MODIFICATION REQUEST or BEARER RESOURCE ALLOCATION REQUEST message for the same APN. When the timer T3396 is running or the timer is deactivated, the UE is allowed to initiate an attach procedure or PDN connectivity procedure if the procedure is for emergency bearer services. 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 shall behave 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.1.4.2 |
6,508 | 5.2.2 UE behaviour in state EMM-DEREGISTERED 5.2.2.1 General | The state EMM-DEREGISTERED is entered in the UE, when: - the detach or combined detach is performed either by the UE or by the MME (see clause 5.5.2); - the attach request is rejected by the MME (see clause 5.5.1); - the tracking area update request is rejected by the MME (see clause 5.5.3); - the service request procedure is rejected by the MME (see clause 5.6.1); - the UE deactivates all EPS bearer contexts locally (see clause 6.4.4.6); - the UE is switched on; - an inter-system change from S1 mode to non-3GPP access is completed and the non-3GPP access network provides PDN connectivity to the same EPC; or - the UE attached for emergency bearer services is in EMM-IDLE mode and its periodic tracking area update timer expires (see clause ). In state EMM-DEREGISTERED, the UE shall behave according to the substate as explained in clause 5.2.2.3. | 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.2.2 |
6,509 | 5.32.5.5 UE Assistance Operation | When UE-assistance operation is authorized by the PCF in the PCC Rule, the SMF provides an indication for UE-assistance in the ATSSS Rule to the UE, as described in clause 5.32.8, and in the MAR to the UPF, as described in clause 5.8.5.8. If the UE receives the UE-assistance indicator in an ATSSS rule (as specified in clause 5.32.8) and the UE decides to apply a different UL traffic distribution for an SDF than the default UL traffic distribution indicated in the Steering Mode component of the ATSSS rule (e.g. because the UE is running out of battery), then the following applies: - The UE may apply any split percentages for the UL traffic distribution of an SDF, based on implementation specific criteria. - The UE may send a PMF-UAD (UE Assistance Data) message to UPF that contains the split percentages that may be used by UPF for all DL traffic that the UE-assistance operation applies. The UPF acknowledges the reception of the PMF-UAD message by sending a PMF-UAD complete message to the UE. NOTE: If the UE has multiple ATSSS rules that allow UE-assistance operation, and the UE decides to use different UL split percentages for their respective SDFs, then the split percentages included in the PMF-UAD message are selected by the UE based on implementation specific criteria. - The UPF may apply the information in a received PMF-UAD message to align the DL traffic distribution for traffic that is allowed to use UE-assistance operation, i.e. traffic where the MAR contains a Steering Mode Indicator set to UE-assistance operation. - If the UE decides to terminate the UE assistance operation, the UE may send a PMF-UAT (UE Assistance Termination) message to the UPF indicating that the UE assistance operation is terminated and the UE performs the UL traffic distribution according to the split percentages in the ATSSS rule received from the network. If the UPF receives the PMF-UAT message, the UPF acknowledges the reception by sending a PMF-UAT complete message and performs DL traffic distribution by applying the split percentages included in the MAR. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.32.5.5 |
6,510 | 6.1 Overview | The layer 2 of NR is split into the following sublayers: Medium Access Control (MAC), Radio Link Control (RLC), Packet Data Convergence Protocol (PDCP) and Service Data Adaptation Protocol (SDAP). The two figures below depict the Layer 2 architecture for downlink and uplink, where: - The physical layer offers to the MAC sublayer transport channels; - The MAC sublayer offers to the RLC sublayer logical channels; - The RLC sublayer offers to the PDCP sublayer RLC channels; - The PDCP sublayer offers to the SDAP sublayer radio bearers; - The SDAP sublayer offers to 5GC QoS flows; - Comp. refers to header compression or uplink data compression; - Segm. refers to segmentation; - Control channels (BCCH, PCCH are not depicted for clarity). NOTE: The gNB may not be able to guarantee that a L2 buffer overflow will never occur. If such overflow occurs, the UE may discard packets in the L2 buffer. Figure 6.1-1: Downlink Layer 2 Structure Figure 6.1-2: Uplink Layer 2 Structure Radio bearers are categorized into two groups: data radio bearers (DRB) for user plane data and signalling radio bearers (SRB) for control plane data. For IAB, the Layer 2 of NR includes: MAC, RLC, Backhaul Adaptation Protocol (BAP), PDCP and optionally SDAP. The BAP sublayer supports routing across the IAB topology and traffic mapping to BH RLC channels for enforcement of traffic prioritization and QoS. Figures 6.1-3 below depicts the Layer-2 architecture for downlink on the IAB-donor. Figures 6.1-4 and 6.1-5 depict the Layer-2 architecture for downlink and uplink on the IAB-node, where the BAP sublayer offers routing functionality and mapping to BH RLC channels. Figure 6.1-3: DL L2-structure for user plane at IAB-donor Figure 6.1-4: DL L2-structure at IAB-node Figure 6.1-5: UL L2-structure at IAB-node | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 6.1 |
6,511 | 7.3.8 Identification Request | If the UE identifies itself with temporary identity and it has changed SGSN/MME since detach in Attach procedure, the new MME/SGSN shall send an Identification Request message to the old SGSN/MME/AMF over S3, S16, S10 or N26 interface to request IMSI. A new AMF may also send an Identification Request message to the old MME over the N26 interface, during a registration procedure (see clause 4.11.5.2 of 3GPP TS 23.502[ Procedures for the 5G System (5GS) ] [83]). Table -1 specifies the presence requirements and conditions of the IEs in the message. If the sending/new node is an MME, it shall include in the Identification Request message: - the GUTI IE and Complete Attach Request Message IE, if the GUTI or the indication of mapped or native GUTI received from UE indicates the old node is a MME, as specified in clause 2.8.2.2.2 of 3GPP TS 23.003[ Numbering, addressing and identification ] [2]. - the RAI P-TMSI, which was derived from the GUTI received from UE, and the P-TMSI Signature that was received intact from the UE, if the GUTI or the indication of mapped or native GUTI indicates the old node is an SGSN as specified in clause 2.8.2.2.2 of 3GPP TS 23.003[ Numbering, addressing and identification ] [2]. If the sending/new node is an SGSN, it shall include RAI IE, P-TMSI IE and P-TMSI Signature IE in the Identification Request message. If the receiving/old node is an MME, it shall construct GUTI according to the RAI IE, P-TMSI IE and P-TMSI Signature IE (see the mapping relationship between RAI, P-TMSI, P-TMSI signature and GUTI defined in 3GPP TS23.003[ Numbering, addressing and identification ] [2]), and find UE context via this GUTI. If the sending/new node is an AMF, it shall include the GUTI IE and Complete Attach Request Message IE in the Identification Request message. The AMF shall construct the GUTI IE from the old 5G-GUTI received from the UE (mapped from the EPS GUTI by the UE), as specified in clause 2.10.2.2.3 of 3GPP TS 23.003[ Numbering, addressing and identification ] [2]. The new MME differentiates the type of the old node as specified in clause 2.8.2.2.2 of 3GPP TS 23.003[ Numbering, addressing and identification ] [2]. If the old node is an SGSN, the GUTI shall be mapped to RAI and P-TMSI by the new MME; if the old node is a MME, the new MME include GUTI IE and Complete Attach Request Message IE in the Identification Request message. The Mapping between temporary and area identities is defined in 3GPP TS 23.003[ Numbering, addressing and identification ] [2]. The GUTI IE shall not coexist with any of the RAI IE, P-TMSI IE and P-TMSI Signature IE in an Identification Request message. If this occurs, the receiving node shall return a corresponding cause value in the response message. The Target PLMN ID IE shall be used in old SGSN/MME in order to decide whether un-used authentication vectors to be distributed to new SGSN/MME or not. Distribution and use of authentication vectors between different serving network domains are specified in 3GPP TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [12]. If the receiving/old node is an AMF, it shall construct the 5G-GUTI from the GUTI IE (see the mapping relationship between GUTI and 5G-GUTI defined in clause 2.10 of 3GPP TS 23.003[ Numbering, addressing and identification ] [2]), and find UE context via this 5G-GUTI. Table -1: Information Elements in an Identification Request | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 7.3.8 |
6,512 | D.7.1 Network initiated QoS | When UE is accessing an overlay network via an underlay network as described in clause D.3, in order to ensure the underlay network to support the QoS required by the overlay network User Plane IPsec Child SA, the QoS differentiation mechanism based on network-initiated QoS modification as described in clause 5.30.2.7 and clause 5.30.2.8 can be used with the following considerations: - An overlay network service can have specific QoS requirement that needs to be fulfilled by the underlay network, based on SLA between the two networks. - The SLA covers selective services of the overlay network which require QoS support in underlay network. The rest of the overlay network traffic could be handled in best efforts basis by underlay network. - The SLA between the overlay network and the underlay network includes a mapping between DSCP values of the User Plane IPsec Child SAs and the QoS requirement of the overlay network services. The QoS requirement includes the QoS parameters described in clause 5.7.2 that are necessary (e.g. 5QI, ARP, etc.) during the network-initiated QoS modification in underlay network. In order to facilitate the SLA, a guidance for details of the mapping between DSCP values of the User Plane IPSec Child SAs and QoS requirement of the overlay network services is described of TS 29.513[ 5G System; Policy and Charging Control signalling flows and QoS parameter mapping; Stage 3 ] [133]. The SLA also includes the N3IWF IP address of the overlay network. - The mapping agreed in SLA is configured at N3IWF of the overlay network and at the SMF/PCF of the underlay network. If a dedicated DNN/S-NSSAI is used in the underlay network for providing access to the N3IWF in the overlay network, the SMF/PCF in the underlay network can be configured to enable packet detection (based on N3IWF IP address and DSCP value) for PDU sessions associated with the dedicated DNN/S-NSSAI. - When UE establishes a PDU Session in underlay network, the PCF in the underlay network determines PCC rules based on UE subscription information and local configuration which takes into account the SLA described above and installs the PCC rules on the SMF which generates and installs PDR/URR on UPF. The PCC rules indicate N3IWF IP address and the DSCP values of the User Plane IPsec Child SAs of the overlay network which require QoS differentiation by the underlay network. So, the UPF in the underlay network can detect packets of the User Plane IPsec Child SAs corresponding to the overlay network services which require QoS support by the underlay network. - UE registers and establishes PDU Session in the overlay network via the User Plane connectivity established in the underlay network. When UE is accessing a specific service of overlay network, a QoS Flow can be created by the overlay network, then N3IWF creates dedicated User Plane IPsec Child SA for each overlay network QoS Flow that requires underlay network QoS support. - N3IWF uses the QoS profile and the Session-AMBR it receives from SMF in overlay network along with the mapping agreed in the SLA to derive a specific DSCP value for the User Plane IPsec Child SA. N3IWF assigns a specific DSCP value only to one User Plane IPsec Child SA for a UE at the same time. UE (for UL) and N3IWF (for DL) will set the DSCP marking in the outer IP header of the User Plane IPsec Child SA accordingly. - The overlay network traffic between UE and N3IWF using the specific DSCP marking will be detected by the UPF in the underlay network, based on previous installed PDR/URR. The SMF/PCF in underlay network will be informed when the overlay network traffic is detected. Then the PCF installs new PCC rules on the SMF including the QoS parameters for handling of packets corresponding to the specific User Plane IPsec Child SA based on the N3IWF IP address and the DSCP value of the User Plane IPsec Child SA, and the SMF generates a QoS profile that triggers the PDU Session Modification procedure as described in clause 4.3.3 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. The QoS parameters are derived from the mapping agreed in SLA based on the detected DSCP value. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | D.7.1 |
6,513 | 16.6 Stand-Alone NPN 16.6.1 General | An SNPN is a network deployed for non-public use which does not rely on network functions provided by a PLMN (see clause 4.8). An SNPN is identified by a PLMN ID and NID (see clause 8.2) broadcast in SIB1. An SNPN-capable UE supports the SNPN access mode. When the UE is set to operate in SNPN access mode, the UE only selects and registers with SNPNs. When the UE is not set to operate in SNPN access mode, the UE performs normal PLMN selection procedures. Emergency services and ETWS /CMAS can be supported by SNPNs. An IMS Emergency call support indication is provided per SNPN to inform the UE which SNPN(s) support emergency bearer. In normal service state the indication is provided in the same way as in case of PLMNs (see clause 16.5.2). In limited service state and for emergency services other than eCall over IMS, a UE is informed whether an SNPN of the cell supports emergency services over NG-RAN from a per SNPN broadcast indication (imsEmergencySupportForSNPN). The broadcast indicator for an SNPN may be set to "support" if any AMF of the SNPN supports IMS emergency bearer services. NR-NR Dual Connectivity within a single SNPN or across SNPNs as indicated in the mobility restriction list is supported. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.6 |
6,514 | 5.2.5.6 Npcf_UEPolicyControl Service 5.2.5.6.1 General | Service description: NF Service Consumer, e.g. AMF, or the PCF serving the PDU Session when a UE attaches in EPS, may create and manage a UE Policy Association in the PCF through which the NF Service Consumer receives Policy Control Request Trigger of UE Policy Association. The association allows (V-)PCF to provide UE policy information to the UE transparently through the NF Service Consumer using NAS TRANSPORT message to carry: - UE policy information as defined in clause 6.6 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. In the case of roaming, the URSP rules are provided by H-PCF and the ANDSP rules may be provided by V-PCF or H-PCF or both. As part of this service, the PCF may provide the NF Service Consumer, e.g. AMF, with policy information about the UE that may contain: - Policy Control Request Trigger of UE Policy Association. When such a Policy Control Request Trigger condition is met, the NF Service Consumer, e.g. AMF, shall contact PCF and provide information on the Policy Request Trigger condition that has been met. In the case of roaming, the V-PCF may subscribe to AMF or the H-PCF may subscribe to AMF via V-PCF. At Npcf_UEPolicyControl_Create, the NF Service Consumer, e.g. AMF, requests the creation of a corresponding "UE Policy Association" with the PCF (Npcf_UEPolicyControl_Create) and provides relevant parameters about the UE context to the PCF. When the PCF has created the UE Policy Association, the PCF may provide policy information as defined above. When a Policy Control Request Trigger condition is met, the NF Service Consumer, e.g. AMF, requests the update (Npcf_UEPolicyControl_Update) of the UE Policy Association by providing information on the condition(s) that have been met. The PCF may provide updated policy information to the NF Service Consumer. During the AMF relocation, if the target AMF receives the PCF ID from source AMF and the target AMF decides to contact with the PCF identified by the PCF ID based on the local policies, the target AMF requests the update (Npcf_UEPolicyControl_Update) of the UE Policy Association. If a Policy Control Request Trigger condition is met, the information matching the trigger condition may also be provided by the target AMF. The PCF may provide updated policy information to the target AMF. The PCF may at any time provide updated policy information (Npcf_UEPolicyControl_UpdateNotify). At UE deregistration the NF Service Consumer, e.g. AMF, or the PCF serving the PDU Session when a UE detaches from EPS, requests the deletion of the corresponding UE Policy Association. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.5.6 |
6,515 | 16.9 Sidelink 16.9.1 General | In this clause, an overview of NR sidelink communication and how NG-RAN supports NR sidelink communication, V2X sidelink communication and Ranging/Sidelink positioning is given. V2X sidelink communication is specified in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [2]. Ranging/Sidelink positioning is specified in TS 38.305[ NG Radio Access Network (NG-RAN); Stage 2 functional specification of User Equipment (UE) positioning in NG-RAN ] [42]. The NG-RAN architecture supports the PC5 interface as illustrated in Figure 16.9.1-1. Sidelink transmission and reception over the PC5 interface are supported when the UE is inside NG-RAN coverage, irrespective of which RRC state the UE is in, and when the UE is outside NG-RAN coverage. Figure 16.9.1-1: NG-RAN Architecture supporting the PC5 interface Support of V2X services via the PC5 interface can be provided by NR sidelink communication and/or V2X sidelink communication. NR sidelink communication may be used to support other services than V2X services. NR sidelink communication can support one of three types of transmission modes for a pair of a Source Layer-2 ID and a Destination Layer-2 ID in the AS: - Unicast transmission, characterized by: - Support of one PC5-RRC connection between peer UEs for the pair; - Transmission and reception of control information and user traffic between peer UEs in sidelink; - Support of sidelink HARQ feedback; - Support of sidelink transmit power control; - Support of RLC AM; - Detection of radio link failure for the PC5-RRC connection. - Groupcast transmission, characterized by: - Transmission and reception of user traffic among UEs belonging to a group in sidelink; - Support of sidelink HARQ feedback. - Broadcast transmission, characterized by: - Transmission and reception of user traffic among UEs in sidelink. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.9 |
6,516 | 5.4.5.3.3 Network-initiated NAS transport of messages | Upon reception of a DL NAS TRANSPORT message, the UE shall stop the timer T3346 if running. Upon reception of a DL NAS TRANSPORT message, if the Payload container type IE is set to: a) "N1 SM information" and the 5GMM cause IE is not included in the DL NAS TRANSPORT message, the 5GSM message in the Payload container IE and the PDU session ID are handled in the 5GSM procedures specified in clause 6; b) "SMS", the UE shall forward the content of the Payload container IE to the SMS stack entity; c) "LTE Positioning Protocol (LPP) message container", the UE shall forward the payload container type, the content of the Payload container IE and the routing information included in the Additional information IE to the upper layer location services application; c1) "SLPP message container", the UE shall forward the payload container type, the content of the Payload container IE and the routing information included in the Additional information IE to the upper layer location services application; d) "SOR transparent container" and if the Payload container IE: 1) successfully passes the integrity check (see 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]), the ME shall store the received SOR counter as specified in annex C and proceed as follows: i) If the Payload container IE indicates a list of preferred PLMN/access technology combinations is provided and the list type indicates "PLMN ID and access technology list", then the ME shall replace the highest priority entries in the "Operator Controlled PLMN Selector with Access Technology" list stored in the ME; ii) If the list type indicates "secured packet", then the ME shall behave as if a SMS is received with protocol identifier set to SIM data download, data coding scheme set to class 2 message and SMS payload as secured packet contents of SOR transparent container IE. The SMS payload is forwarded to UICC as specified in 3GPP TS 23.040[ Technical realization of the Short Message Service (SMS) ] [4A]; iii) If the Payload container IE includes SOR-SNPN-SI, the ME shall replace SOR-SNPN-SI of the selected entry of the "list of subscriber data" or associated with the selected PLMN subscription, as specified in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5] with the received SOR-SNPN-SI; iv) If the SOR-CMCI is present, in plain text, and the Store SOR-CMCI in ME indicator is set to "Store SOR-CMCI in ME" then the UE shall store or delete the SOR-CMCI in the non-volatile memory of the ME as described in annex C.1;and v) If the Payload container IE includes SOR-SNPN-SI-LS, the ME shall replace SOR-SNPN-SI-LS of the selected entry of the "list of subscriber data" or associated with the selected PLMN subscription, as specified in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5] with the received SOR-SNPN-SI-LS; If the ACK bit of the SOR header for SOR data type in the SOR transparent container is set to "acknowledgement requested" and the list type indicates: A) "PLMN ID and access technology list"; or B) "secured packet" and the ME receives status bytes from the UICC indicating that the UICC has received the secured packet successfully; then the ME shall send an acknowledgement in the Payload container IE of an UL NAS TRANSPORT message with Payload type IE set to "SOR transparent container" as specified in subclause 5.4.5.2.2. In the Payload container IE carrying the acknowledgement, the UE shall set the ME support of SOR-CMCI indicator to "SOR-CMCI supported by the ME". Additionally, if the UE supports access to an SNPN using credentials from a credentials holder and the UE is not operating in SNPN access operation mode, the UE may set the ME support of SOR-SNPN-SI indicator to "SOR-SNPN-SI supported by the ME".Additionally, if the UE supports access to an SNPN providing access for localized services in SNPN, the UE shall set the ME support of SOR-SNPN-SI-LS indicator to "SOR-SNPN-SI-LS supported by the ME". The UE shall proceed with the behaviour as specified in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5] annex C; or 2) does not successfully pass the integrity check (see 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]) then the UE shall discard the content of the payload container IE and proceed with the behaviour as specified in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5] annex C. e) Void; f) Void; g) "N1 SM information" and: 1) the 5GMM cause IE is set to the 5GMM cause #22 "Congestion", the UE passes to the 5GSM sublayer an indication that the 5GSM message was not forwarded due to DNN based congestion control along with the 5GSM message from the Payload container IE of the DL NAS TRANSPORT message, and the time value from the Back-off timer value IE; 2) the 5GMM cause IE is set to the 5GMM cause #28 "Restricted service area", the UE passes to the 5GSM sublayer an indication that the 5GSM message was not forwarded due to service area restrictions along with the 5GSM message from the Payload container IE of the DL NAS TRANSPORT message, enters the state 5GMM-REGISTERED.NON-ALLOWED-SERVICE and, if the DL NAS TRANSPORT message is received over 3GPP access, performs the registration procedure for mobility and periodic registration update without waiting for the release of the N1 NAS signalling connection (see subclauses 5.3.5 and 5.5.1.3); 3) the 5GMM cause IE is set to the 5GMM cause #65 "maximum number of PDU sessions reached", the UE passes to the 5GSM sublayer an indication that the 5GSM message was not forwarded because the PLMN's maximum number of PDU sessions has been reached, along with the 5GSM message from the Payload container IE of the DL NAS TRANSPORT message; 4) the 5GMM cause IE is set to the 5GMM cause #67 "insufficient resources for specific slice and DNN", the UE passes to the 5GSM sublayer an indication that the 5GSM message was not forwarded due to S-NSSAI and DNN based congestion control along with the 5GSM message from the Payload container IE of the DL NAS TRANSPORT message, and the time value from the Back-off timer value IE; 5) the 5GMM cause IE is set to the 5GMM cause #69 "insufficient resources for specific slice", the UE passes to the 5GSM sublayer an indication that the 5GSM message was not forwarded due to S-NSSAI only based congestion control along with the 5GSM message from the Payload container IE of the DL NAS TRANSPORT message, and the time value from the Back-off timer value IE; 5a) the 5GMM cause IE is set to the 5GMM cause #78 "PLMN not allowed to operate at the present UE location", the UE passes to the 5GSM sublayer an indication that the 5GSM message was not forwarded because the UE is registered to a PLMN via a satellite NG-RAN cell that is not allowed to operate at the present UE location along with the 5GSM message from the Payload container IE of the DL NAS TRANSPORT message. Additionally, if the cause is received from a statellite NG-RAN cell, the UE shall not send the UL NAS TRANSPORT message to transport any of the data types listed in subclause 5.4.5.2.1. The UE shall store the PLMN identity and, if it is known, the current geographical location in the list of "PLMNs not allowed to operate at the present UE location" and shall start a corresponding timer instance (see subclause 4.23.2). The UE shall enter state 5GMM-DEREGISTERED.PLMN-SEARCH and perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]; 6) the 5GMM cause IE is set to the 5GMM cause #90 "payload was not forwarded", the UE passes to the 5GSM sublayer an indication that the 5GSM message was not forwarded due to routing failure along with the 5GSM message from the Payload container IE of the DL NAS TRANSPORT message. The UE shall ignore the Back-off timer value IE, if any; 7) the 5GMM cause IE is set to the 5GMM cause #91 "DNN not supported or not subscribed in the slice", the UE passes to the 5GSM sublayer an indication that the 5GSM message was not forwarded because the DNN is not supported or not subscribed in a slice along with the 5GSM message from the Payload container IE of the DL NAS TRANSPORT message, and the time value from the Back-off timer value IE, if any; 8) the 5GMM cause IE is set to the 5GMM cause #92 "insufficient user-plane resources for the PDU session", the UE passes to the 5GSM sublayer an indication that the 5GSM message was not forwarded due to insufficient user-plane resources along with the 5GSM message from the Payload container IE of the DL NAS TRANSPORT message. 9) the 5GMM cause IE is set to the 5GMM cause #79 "UAS services not allowed", the UE passes to the 5GSM sublayer an indication that the 5GSM message was not forwarded because the UE is marked in the UE's 5GMM context that it is not allowed to request UAS services along with the 5GSM message from the Payload container IE of the DL NAS TRANSPORT message. h) "UE policy container", the UE policy container in the Payload container IE is handled in the UE policy delivery procedures specified in Annex D; i) "UE parameters update transparent container" and if the Payload container IE 1) successfully passes the integrity check (see 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]), the ME shall store the received UE parameter update counter as specified in annex C and proceed as follows: i) if the UE parameters update list includes a UE parameters update data set with UE parameters update data set type indicating "Routing indicator update data", A) the ME shall behave as if an SMS is received with protocol identifier set to SIM data download, data coding scheme set to class 2 message and SMS payload as secured packet contents of UE parameters update transparent container IE. The SMS payload is forwarded to UICC as specified in 3GPP TS 23.040[ Technical realization of the Short Message Service (SMS) ] [4A]; and B) if the ACK bit of the UE parameters update header in the UE parameters update transparent container is set to "acknowledgment requested" and if the ME receives status bytes from the UICC indicating that the UICC has received the secured packet successfully, the ME shall send an acknowledgement in the Payload container IE of an UL NAS TRANSPORT message with Payload type IE set to "UE parameters update transparent container" as specified in subclause 5.4.5.2.2; and C) if the ME receives a REFRESH command from the UICC as specified in 3GPP TS 31.111[ Universal Subscriber Identity Module (USIM) Application Toolkit (USAT) ] [22A] and if the REG bit of the UE parameters update header in the UE parameters update transparent container IE is set to "re-registration requested", and: C1) the UE is registered over 3GPP access, then the UE shall wait until the emergency services over 3GPP access, if any, are completed, enter 5GMM-IDLE mode over 3GPP access or 5GMM-CONNECTED mode with RRC inactive indication, perform a de-registration procedure, and then delete its 5G-GUTI if the UE is registered to different PLMN or SNPN on non-3GPP access or the UE is not registered over non-3GPP access, or wait until the de-registration procedure over non-3GPP access specified in case C2) or C3) is completed before deleting its 5G-GUTI if the UE is registered to same PLMN or SNPN on non-3GPP access, and then initiate a registration procedure for initial registration as specified in subclause 5.5.1.2; C2) the UE is registered over non-3GPP access and does not have emergency services ongoing over non-3GPP access, then the UE shall locally release the N1 NAS signalling connection and enter 5GMM-IDLE mode over non-3GPP access, perform a de-registration procedure, and then delete its 5G-GUTI if the UE is registered to different PLMN or SNPN on 3GPP access or the UE is not registered over 3GPP access, or wait until the de-registration procedure over 3GPP access specified in case C1) is completed before deleting its 5G-GUTI if the UE is registered to same PLMN or SNPN on 3GPP access, and then initiate a registration procedure for initial registration as specified in subclause 5.5.1.2; and C3) the UE is registered over non-3GPP access and has an emergency services ongoing over non-3GPP access, then the UE shall wait until the emergency services are completed before locally releasing the N1 NAS signalling connection and enter 5GMM-IDLE mode over non-3GPP access, perform a de-registration procedure, and then delete its 5G-GUTI if the UE is registered to different PLMN or SNPN on 3GPP access or if the UE is not registered over 3GPP access, or wait until the de-registration procedure over 3GPP access specified in case C1) is completed before deleting its 5G-GUTI if the UE is registered to same PLMN or SNPN on 3GPP access, and then initiate a registration procedure for initial registration as specified in subclause 5.5.1.2. ii) if the UE parameters update list includes a UE parameters update data set with UE parameters update data set type indicating "Default configured NSSAI update data", A) if the ACK bit of the UE parameters update header in the UE parameters update transparent container is set to "acknowledgment requested" and if the UE parameters update list does not include a UE parameters update data set with UE parameters update data set type indicating "Routing indicator update data", the ME shall send an acknowledgement in the Payload container IE of an UL NAS TRANSPORT message with Payload type IE set to "UE parameters update transparent container" as specified in subclause 5.4.5.2.2 B) the ME shall replace the stored default configured NSSAI with the default configured NSSAI included in the default configured NSSAI update data. In case of SNPN, the ME shall replace the stored default configured NSSAI associated with the selected entry of the "list of subscriber data" or the PLMN subscription with the default configured NSSAI included in the default configured NSSAI update data; and C) if the REG bit of the UE parameters update header in the UE parameters update transparent container is set to "re-registration requested" and the UE parameters update list does not include a UE parameters update data set with UE parameters update data set type indicating "Routing indicator update data", the UE shall wait until it enters 5GMM-IDLE mode and then the UE shall initiate a registration procedure for mobility registration update as specified in subclause 5.5.1.3. if the UE parameters update list does not include a UE parameters update data set with UE parameters update data set type indicating "Routing indicator update data", the UE used the old default configured NSSAI to create the requested NSSAI in a REGISTRATION REQUEST message, because the UE does not have a configured NSSAI for the current PLMN or SNPN, and the UE has an stored allowed NSSAI for the current PLMN or SNPN which contains one or more S-NSSAIs that are not included in the new default configured NSSAI, the UE shall wait until it enters 5GMM-IDLE mode and then the UE shall initiate a registration procedure for mobility and periodic registration update as specified in subclause 5.5.1.3; and iii) if the UE parameters update list includes a UE parameters update data set with UE parameters update data set type indicating "Disaster roaming information update data", A) if the ACK bit of the UE parameters update header in the UE parameters update transparent container is set to "acknowledgment requested" and if the UE parameters update list does not include a UE parameters update data set with UE parameters update data set type indicating "Routing indicator update data" or a UE parameters update data set with UE parameters update data set type indicating "Default configured NSSAI update data", the ME shall send an acknowledgement in the Payload container IE of an UL NAS TRANSPORT message with Payload type IE set to "UE parameters update transparent container" as specified in subclause 5.4.5.2.2; B) the UE shall delete the indication of whether disaster roaming is enabled in the UE stored in the ME, if any, and store the indication of whether disaster roaming is enabled in the UE included in the disaster roaming information update data in the ME; C) the UE shall delete the indication of applicability of "lists of PLMN(s) to be used in disaster condition" provided by a VPLMN' stored in the ME, if any, and store the indication of 'applicability of "lists of PLMN(s) to be used in disaster condition" provided by a VPLMN' included in the disaster roaming information update data in the ME; and D) if the REG bit of the UE parameters update header in the UE parameters update transparent container is set to "re-registration requested" and the UE parameters update list does not include a UE parameters update data set with UE parameters update data set type indicating "Routing indicator update data", the UE shall wait until it enters 5GMM-IDLE mode and then the UE shall initiate a registration procedure for mobility registration update as specified in subclause 5.5.1.3. iv) if the UE parameters update list includes a UE parameters update data set with UE parameters update data set type indicating "ME routing indicator update data": A) if the ACK bit of the UE parameters update header in the UE parameters update transparent container is set to "acknowledgment requested" and the UE parameters update list does not include a UE parameters update data set with UE parameters update data set type indicating "Default configured NSSAI update data", the ME shall send an acknowledgement in the Payload container IE of an UL NAS TRANSPORT message with Payload type IE set to "UE parameters update transparent container" as specified in subclause 5.4.5.2.2; B) the UE shall set or replace the routing indicator of the selected entry of the "list of subscriber data" with the routing indicator included in the ME routing indicator update data; and C) if the REG bit of the UE parameters update header in the UE parameters update transparent container IE is set to "re-registration requested", and: C1) the UE is registered over 3GPP access and is not registered over non-3GPP access, then the UE shall wait until the emergency services over 3GPP access, if any, are completed, enter 5GMM-IDLE mode over 3GPP access or 5GMM-CONNECTED mode with RRC inactive indication, perform a de-registration procedure, delete its 5G-GUTI, and then initiate a registration procedure for initial registration as specified in subclause 5.5.1.2; C2) the UE is registered over non-3GPP access and is not registered over 3GPP access, then the UE shall locally release the N1 NAS signalling connection and enter 5GMM-IDLE mode over non-3GPP access, perform a de-registration procedure, delete its 5G-GUTI, and then initiate a registration procedure for initial registration as specified in subclause 5.5.1.2; or C3) the UE is registered over 3GPP access and non-3GPP access to same SNPN, then the UE shall wait until the emergency services over 3GPP access, if any, are completed, enter 5GMM-IDLE mode over 3GPP access or 5GMM-CONNECTED mode with RRC inactive indication over 3GPP access, perform a de-registration procedure over 3GPP access, locally release the N1 NAS signalling connection and enter 5GMM-IDLE mode over non-3GPP access, perform a de-registration procedure over non-3GPP access, delete its 5G-GUTI and then initiate a registration procedure for initial registration as specified in subclause 5.5.1.2. 2) does not successfully pass the integrity check (see 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]) then the UE shall discard the content of the payload container IE; j) "Location services message container" and the 5GMM cause IE is not included in the DL NAS TRANSPORT message, the UE shall forward the payload container type, the content of the Payload container IE and the routing information in the Additional information IE if included to the upper layer location services application; k) "CIoT user data container" and the 5GMM cause IE is not included in the DL NAS TRANSPORT message, the UE shall forward the content of the Payload container IE and the PDU session ID to the 5GSM sublayer; l) "CIoT user data container" and: 1) the 5GMM cause IE is set to the 5GMM cause #22 "Congestion", the UE passes to the 5GSM sublayer an indication that the CIoT user data was not forwarded due to DNN based congestion control along with the CIoT user data from the Payload container IE of the DL NAS TRANSPORT message, and the time value from the Back-off timer value IE; 2) the 5GMM cause IE is set to the 5GMM cause #67 "insufficient resources for specific slice and DNN", the UE passes to the 5GSM sublayer an indication that the CIoT user data was not forwarded due to S-NSSAI and DNN based congestion control along with the CIoT user data from the Payload container IE of the DL NAS TRANSPORT message, and the time value from the Back-off timer value IE; 3) the 5GMM cause IE is set to the 5GMM cause #69 "insufficient resources for specific slice", the UE passes to the 5GSM sublayer an indication that the CIoT user data was not forwarded due to S-NSSAI only based congestion control along with the CIoT user data from the Payload container IE of the DL NAS TRANSPORT message, and the time value from the Back-off timer value IE; or 4) the 5GMM cause IE is set to the 5GMM cause #90 "payload was not forwarded", the UE passes to the 5GSM sublayer an indication that the user data container was not forwarded due to routing failure along with the user data container from the Payload container IE and the PDU session ID from the PDU session ID IE of the DL NAS TRANSPORT message; m) "service-level-AA container", the UE shall forward the content of the Payload container IE to the upper layers; m1) "Event notification", the UE shall forward the received event notification indicator(s) to the upper layers (see 3GPP TS 23.216[ Single Radio Voice Call Continuity (SRVCC); Stage 2 ] [6A] and 3GPP TS 24.237[ IP Multimedia (IM) Core Network (CN) subsystem IP Multimedia Subsystem (IMS) service continuity; Stage 3 ] [14AA] for the "SRVCC handover cancelled, IMS session re-establishment required" indicator); m2) "UPP-CMI container" and the 5GMM cause IE is not included in the DL NAS TRANSPORT message, the UE shall forward the payload container type, the content of the Payload container IE and the routing information included in the Additional information IE to the upper layer location services application for user plane connection management for user plane positioning; NOTE 2: The user plane connection establishment for user plane positioning connection management is specified in 3GPP TS 24.572[ 5G System (5GS); User plane Location Services (LCS) protocols and procedures; Stage 3 ] [64]. m3) "UPP-CMI container" and the 5GMM cause IE is set to the 5GMM cause #94 "User plane positioning not authorized", the UE passes to the upper layer location services application an indication that user plane positioning is not authorized by the network; or n) "Multiple payloads", the UE shall first decode the content of the Payload container IE (see subclause 9.11.3.39) to obtain the number of payload container entries and for each payload container entry, the UE shall: 1) decode the payload container type field; 2) decode the optional IE fields and the payload container contents field in the payload container entry; and 3) handle the content of each payload container entry the same as the content of the Payload container IE and the associated optional IEs as specified in bullets a) to m3) above according to the payload container type field. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.4.5.3.3 |
6,517 | 6.3.3 Authentication and key agreement | The purpose of this procedure is to authenticate the user and establish a new pair of cipher and integrity keys between the VLR/SGSN and the USIM. During the authentication, the USIM verifies the freshness of the authentication vector that is used. Figure 8: Successful UMTS Authentication and Key Agreement The VLR/SGSN invokes the procedure by selecting the next unused authentication vector from the ordered array of authentication vectors in the VLR/SGSN database. Authentication vectors in a particular node are used on a first-in / first-out basis. The VLR/SGSN sends to the USIM the random challenge and an authentication token for network authentication AUTN from the selected authentication vector. Upon receipt the user proceeds as shown in Figure 9. Figure 9: User authentication function in the USIM Upon receipt of RAND and AUTN the USIM first computes the anonymity key AK = f5K (RAND) and retrieves the sequence number SQN = () Γ
AK. Next the USIM computes XMAC = f1K (SQN || || AMF) and compares this with MAC which is included in AUTN. If they are different, the user sends an authentication failure message back to the VLR/SGSN with an indication of the cause and the user abandons the procedure. In this case, VLR/SGSN shall initiate an Authentication Failure Report procedure towards the HLR as specified in section 6.3.6. VLR/SGSN may also decide to initiate a new identification and authentication procedure towards the user, cf. TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [35]. Next the USIM verifies that the received sequence number SQN is in the correct range. If the USIM considers the sequence number to be not in the correct range, it sends synchronisation failure back to the VLR/SGSN including an appropriate parameter, and abandons the procedure. The synchronisation failure message contains the parameter AUTS. It is AUTS = Conc(SQNMS ) || MAC-S. Conc(SQNMS) = SQNMS f5*K(RAND) is the concealed value of the counter SQNMS in the MS, and MAC-S = f1*K(SQNMS || RAND || AMF) where is the random value received in the current user authentication request. f1* is a message authentication code (MAC) function with the property that no valuable information can be inferred from the function values of f1* about those of f1, ... , f5, f5* and vice versa. f5* is the key generating function used to compute AK in re-synchronisation procedures with the property that no valuable information can be inferred from the function values of f5* about those of f1, f1*, f2, ... , f5 and vice versa. The AMF used to calculate MAC-S assumes a dummy value of all zeros so that it does not need to be transmitted in the clear in the re-synch message. The construction of the parameter AUTS in shown in the following Figure 10: Figure 10: Construction of the parameter AUTS If the sequence number is considered to be in the correct range however, the USIM computes RES = f2K () and includes this parameter in a user authentication response back to the VLR/SGSN. Finally the USIM computes the cipher key CK = f3K (RAND) and the integrity key IK = f4K (). Note that if this is more efficient, RES, CK and IK could also be computed earlier at any time after receiving . If the USIM also supports conversion function c3, it shall derive the 64-bit GSM cipher key Kc from the UMTS cipher/integrity keys CK and IK. UMTS keys are sent to the MS along with the derived 64-bit GSM key for UMTS-GSM interoperability purposes. USIM shall store original CK, IK until the next successful execution of AKA. Upon receipt of user authentication response the VLR/SGSN compares RES with the expected response XRES from the selected authentication vector. If XRES equals RES then the authentication of the user has passed. The SGSN shall compute the 128-bit GSM ciphering key Kc128 according to annex B.5 if it is to use a 128-bit GSM ciphering algorithm. The VLR/MSC shall compute the 128-bit GSM ciphering key Kc128 according to annex B.5 if it signals a 128-bit GSM ciphering algorithm as a permitted GSM ciphering algorithm to the BSS. The VLR/SGSN also selects the appropriate cipher key CK and integrity key IK from the selected authentication vector. If XRES and RES are different, VLR/SGSN shall initiate an Authentication Failure Report procedure towards the HLR as specified in section 6.3.6. VLR/SGSN may also decide to initiate a new identification and authentication procedure towards the user, cf. TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [35]. Re-use and re-transmission of (RAND, AUTN) The verification of the SQN by the USIM will cause the MS to reject an attempt by the VLR/SGSN to re-use a quintet to establish a particular UMTS security context more than once. In general therefore the VLR/SGSN shall use a quintet only once. There is one exception however: in the event that the VLR/SGSN has sent out an authentication request using a particular quintet and does not receive a response message (authentication response or authentication failure) from the MS, it may re-transmit the authentication request using the same quintet. However, as soon as a response message arrives no further re-transmissions are allowed. If after the initial transmission or after a series of re-transmissions no response arrives, retransmissions may be abandoned. If retransmissions are abandoned then the VLR/SGSN shall delete the quintet. At the MS side, in order to allow this re-transmission without causing additional re-synchronisation procedures, the ME shall store for the PS domain (and optionally the CS domain) the last received RAND as well as the corresponding RES, CK and IK. If the USIM returned SRES and Kc (for GSM access), the ME shall store these values. When the ME receives an authentication request and discovers that a is repeated, it shall re-transmit the response. The ME shall delete the stored values , RES and SRES (if they exist) as soon as the 3G security mode command or the GSM cipher mode command is received by the ME or the connection is aborted. If the ME can handle the retransmission mechanism for CS domain then it shall be able to handle the retransmission for both PS and CS domain simultaneously. | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | 6.3.3 |
6,518 | 5.4.5.3.2 Network-initiated NAS transport procedure initiation | In 5GMM-CONNECTED mode, the AMF initiates the NAS transport procedure by sending the DL NAS TRANSPORT message, as shown in figure 5.4.5.3.2.1. In case a) in subclause 5.4.5.3.1, i.e. upon reception from an SMF of a 5GSM message without an N1 SM delivery skip allowed indication for a UE or a 5GSM message with an N1 SM delivery skip allowed indication for a UE in the 5GMM-CONNECTED mode, the AMF shall: a) include the PDU session information (PDU session ID) in the PDU session ID IE; b) set the Payload container type IE to "N1 SM information"; and c) set the Payload container IE to the 5GSM message. In case b) in subclause 5.4.5.3.1, i.e. upon reception from an SMSF of an SMS payload, the AMF shall: a) set the Payload container type IE to "SMS"; b) set the Payload container IE to the SMS payload; and c) select the access type to deliver the DL NAS TRANSPORT message as follows in case the access type selection is required: 1) if the UE to receive the DL NAS TRANSPORT message is registered to the network via both 3GPP access and non-3GPP access, the 5GMM context of the UE indicates that SMS over NAS is allowed, the UE is in MICO mode, and the UE is in 5GMM-IDLE mode for 3GPP access and in 5GMM-CONNECTED mode for non-3GPP access, then the AMF selects non-3GPP access. Otherwise, the AMF selects either 3GPP access or non-3GPP access. If the delivery of the DL NAS TRANSPORT message over 3GPP access has failed, the AMF may re-send the DL NAS TRANSPORT message over the non-3GPP access. If the delivery of the DL NAS TRANSPORT message over non-3GPP access has failed, the AMF may re-send the DL NAS TRANSPORT message over the 3GPP access; and 2) otherwise, the AMF selects 3GPP access. NOTE 1: The AMF selects an access type between 3GPP access and non-3GPP access based on operator policy. In case c) in subclause 5.4.5.3.1 i.e. upon reception from an LMF of an LPP message payload, the AMF shall: a) set the Payload container type IE to "LTE Positioning Protocol (LPP) message container"; b) set the Payload container IE to the LPP message payload received from the LMF; c) set the Additional information IE to an LCS correlation identifier received from the LMF from which the LPP message was received. NOTE 2: The LCS Correlation Identifier is assigned originally by the AMF except for LPP message transfer associated with event reporting for periodic or triggered location as described in subclause 6.3.1 of 3GPP TS 23.273[ 5G System (5GS) Location Services (LCS); Stage 2 ] [6B], where the LMF assigns the correlation identifier. AMF and LMF assigned correlation identifiers can be distinguished by an implementation specific convention (e.g. use of a different number of octets) to enable an AMF to distinguish one from the other when received in the Additional Information IE in an UL NAS Transport message. In case c1) in subclause 5.4.5.3.1 i.e. upon reception from an LMF of an SLPP message payload, the AMF shall: a) set the Payload container type IE to "SLPP message container"; b) set the Payload container IE to the SLPP message payload received from the LMF; and c) set the Additional information IE to an LCS correlation identifier received from the LMF from which the SLPP message was received. In case d) in subclause 5.4.5.3.1 i.e. upon reception of a steering of roaming information (see 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]) from the UDM to be forwarded to the UE, the AMF shall: a) set the Payload container type IE to "SOR transparent container"; and b) set the Payload container IE to the steering of roaming information received from the UDM (see 3GPP TS 29.503[ 5G System; Unified Data Management Services; Stage 3 ] [20AB]). In case e) in subclause 5.4.5.3.1, i.e. upon sending a single uplink 5GSM message which was not forwarded due to routing failure, the AMF shall: a) include the PDU session ID in the PDU session ID IE; b) set the Payload container type IE to "N1 SM information"; c) set the Payload container IE to the 5GSM message which was not forwarded; d) set the 5GMM cause IE to the 5GMM cause #90 "payload was not forwarded" or 5GMM cause #91 "DNN not supported or not subscribed in the slice". The AMF sets the 5GMM cause IE to the 5GMM cause #91 "DNN not supported or not subscribed in the slice", if the 5GSM message could not be forwarded since SMF selection fails because: 1) the DNN is not supported in the slice identified by the S-NSSAI used by the AMF; or 2) neither the DNN provided by the UE nor the wildcard DNN are in the subscribed DNN list of the UE for the S-NSSAI used by the AMF. Otherwise, the AMF sets the 5GMM cause IE to the 5GMM cause #90 "payload was not forwarded"; and e) optionally include the Back-off timer value IE if the 5GMM cause IE is set to 5GMM cause #91 "DNN not supported or not subscribed in the slice" due to the DNN is not supported in the slice. In case f) in subclause 5.4.5.3.1, i.e. upon sending a single uplink 5GSM message which was not forwarded due to congestion control, the AMF shall: a) include the PDU session ID in the PDU session ID IE; b) set the Payload container type IE to "N1 SM information"; c) set the Payload container IE to the 5GSM message which was not forwarded; d) set the 5GMM cause IE to the 5GMM cause #22 "Congestion", the 5GMM cause #67 "insufficient resources for specific slice and DNN" or the 5GMM cause #69 "insufficient resources for specific slice"; and e) include the Back-off timer value IE. In case g) in subclause 5.4.5.3.1, i.e. upon reception of a UE policy container from the PCF to be forwarded to the UE, the AMF shall: a) set the Payload container type IE to "UE policy container"; and b) set the Payload container IE to the UE policy container received from the PCF. In case h) in subclause 5.4.5.3.1, i.e. upon sending a single uplink 5GSM message which was not forwarded, because the PLMN's maximum number of PDU sessions has been reached, the AMF shall: a) include the PDU session ID in the PDU session ID IE; b) set the Payload container type IE to "N1 SM information"; c) set the Payload container IE to the 5GSM message which was not forwarded; and d) set the 5GMM cause IE to the 5GMM cause #65 "maximum number of PDU sessions reached". In case h1) in subclause 5.4.5.3.1, i.e. upon sending a single uplink 5GSM message which was not forwarded, because the maximum number of PDU sessions with active user-plane resources has been reached, the AMF shall: a) include the PDU session ID in the PDU session ID IE; b) set the Payload container type IE to "N1 SM information"; c) set the Payload container IE to the 5GSM message which was not forwarded; and d) set the 5GMM cause IE to the 5GMM cause #92 "insufficient user-plane resources for the PDU session". In case h2) in subclause 5.4.5.3.1, i.e. upon sending a single uplink 5GSM message which was not forwarded because the UE requested to establish a PDU session associated with an S-NSSAI or to modify a PDU session associated with an S-NSSAI for which: a) the AMF is performing network slice-specific authentication and authorization and determined to reject the request based on local policy; or b) the network slice-specific authentication and authorization has failed or the authorization has been revoked; the AMF shall: a) include the PDU session ID in the PDU session ID IE; b) set the Payload container type IE to "N1 SM information"; c) set the Payload container IE to the 5GSM message which was not forwarded; and d) set the 5GMM cause IE to the 5GMM cause #90 "payload was not forwarded". In case h3) in subclause 5.4.5.3.1, i.e. upon sending a single uplink 5GSM message which was not forwarded because the UE requested to establish an MA PDU session for LADN DNN, the AMF shall: a) include the PDU session ID in the PDU session ID IE; b) set the Payload container type IE to "N1 SM information"; c) set the Payload container IE to the 5GSM message which was not forwarded; and d) set the 5GMM cause IE to the 5GMM cause #90 "payload was not forwarded". In case h4) in subclause 5.4.5.3.1, i.e. upon sending a single uplink 5GSM message which was not forwarded, because the maximum number of UEs for a network slice has been reached, the AMF shall: a) include the PDU session ID in the PDU session ID IE; b) set the Payload container type IE to "N1 SM information"; c) set the Payload container IE to the 5GSM message which was not forwarded; d) set the 5GMM cause IE to the 5GMM cause #69 "insufficient resources for specific slice"; and e) include the Back-off timer value IE. For case h5) in subclause 5.4.5.3.1, i.e. upon sending a single uplink 5GSM message which was not forwarded because the UE is marked in the UE's 5GMM context that it is not allowed to request UAS services, the AMF shall: a) include the PDU session ID in the PDU session ID IE; b) set the Payload container type IE to "N1 SM information"; c) set the Payload container IE to the 5GSM message which was not forwarded; and d) set the 5GMM cause IE to the 5GMM cause #79 "UAS services not allowed". For case h6) in subclause 5.4.5.3.1, i.e. upon sending a single uplink 5GSM message which was not forwarded because because the UE not supporting S-NSSAI location validity information requested forwarding of an 5GSM message with Request type IE is set to "initial request" when not in the NS-AoS of the related S-NSSAI, the AMF shall: a) include the PDU session ID in the PDU session ID IE; b) set the Payload container type IE to "N1 SM information"; c) set the Payload container IE to the 5GSM message which was not forwarded; d) set the 5GMM cause IE to the 5GMM cause #69 "insufficient resources for specific slice"; and e) include the Back-off timer value IE. In case i) in subclause 5.4.5.3.1, i.e. upon sending a single uplink 5GSM message which was not forwarded due to service area restrictions, the AMF shall: a) include the PDU session ID in the PDU session ID IE; b) set the Payload container type IE to "N1 SM information"; c) set the Payload container IE to the 5GSM message which was not forwarded; and d) set the 5GMM cause IE to the 5GMM cause #28 "Restricted service area". In case i1) in subclause 5.4.5.3.1, i.e. upon sending a single uplink 5GSM message which was not forwarded because the UE is registered to a PLMN via a satellite NG-RAN cell that is not allowed to operate at the present UE location, the AMF shall: a) include the PDU session ID in the PDU session ID IE; b) set the Payload container type IE to "N1 SM information"; c) set the Payload container IE to the 5GSM message which was not forwarded; and d) set the 5GMM cause IE to the 5GMM cause #78 "PLMN not allowed to operate at the present UE location". In case j) in subclause 5.4.5.3.1 i.e. upon reception of UE parameters update data (see 3GPP TS 23.502[ Procedures for the 5G System (5GS) ] [9]) from the UDM to be forwarded to the UE, the AMF shall: a) set the Payload container type IE to "UE parameters update transparent container"; and b) set the contents of the Payload container IE to the UE parameters update data (see 3GPP TS 23.502[ Procedures for the 5G System (5GS) ] [9]) received from the UDM. For case k) in subclause 5.4.5.3.1 upon reception from a location services application of a Location services message payload, the AMF shall: a) set the Payload container type IE to "Location services message container"; and b) set the Payload container IE to the Location services message payload. For case k) in subclause 5.4.5.3.1 upon reception from an LMF of a Location services message payload, the AMF shall: a) set the Payload container type IE to "Location services message container"; b) set the Payload container IE to the Location services message payload; and c) set the Additional information IE to routing information associated with the LMF from which the Location services message payload was received. NOTE 3: Case k) in subclause 5.4.5.3.1 supports transport of a Location services message container between a UE and an AMF and between a UE and an LMF. For transport between a UE and an LMF, the Additional information IE is included and provides routing information for the LMF. For transport between a UE and an AMF, the Additional information IE is not included. In case l) in subclause 5.4.5.3.1, i.e. upon reception from an SMF of a user data container payload, the AMF shall: a) include the PDU session ID in the PDU session ID IE; b) set the Payload container type IE to "CIoT user data container"; and c) set the Payload container IE to the user data container. For case l1) in subclause 5.4.5.3.1, i.e. upon sending a single uplink CIoT user data container or control plane user data which was not forwarded due to routing failure, the AMF shall: a) include the PDU session ID in the PDU session ID IE; b) set the Payload container type IE to "CIoT user data container"; c) set the Payload container IE to the CIoT user data container or control plane user data which was not forwarded; and d) set the 5GMM cause IE to the 5GMM cause #90 "payload was not forwarded". NOTE 4: For case l1) in subclause 5.4.5.3.1, this is also applied for a single uplink CIoT user data container or control plane user data in the CONTROL PLANE SERVICE REQUEST message which was not forwarded due to routing failure. For case l2) in subclause 5.4.5.3.1, i.e. upon sending a single uplink CIoT user data container which was not forwarded due to congestion control, the AMF shall: a) include the PDU session ID in the PDU session ID IE; b) set the Payload container type IE to " CIoT user data container"; c) set the Payload container IE to the CIoT user data container which was not forwarded; d) set the 5GMM cause IE to the 5GMM cause #22 "Congestion", the 5GMM cause #67 "insufficient resources for specific slice and DNN" or the 5GMM cause #69 "insufficient resources for specific slice", and include the Back-off timer value IE. In case m) in subclause 5.4.5.3.1, during UUAA-MM procedure, if the AMF receives the UUAA payload from the UAS-NF, the AMF shall: a) include the service-level-AA payload with the value set to the payload; and b) if a payload type associated with the payload is received, include the service-level-AA payload type with the value set to the payload type In case m1) in subclause 5.4.5.3.1, i.e. if the AMF needs to send an event notification indicator for upper layers to the UE which set the "EventNotification" bit of the 5GMM capability IE in the last REGISTRATION REQUEST message to "Event notification supported", the AMF shall: a) set the Payload container type IE to "Event notification"; and b) set the Payload container IE to the event notification indicator. In case m2) in subclause 5.4.5.3.1, i.e. upon reception from an LMF of a UPP-CMI container, the AMF shall: a) set the Payload container type IE to "UPP-CMI container"; b) set the Payload container IE to the UPP-CMI container received from the LMF; and c) set the Additional information IE to routing information associated with the LMF from which the Location services message payload was received. For case m3) in subclause 5.4.5.3.1, i.e. upon sending a single UPP-CMI container which was not forwarded due to user plane positioning not authorized, the AMF shall: a) set the Payload container type IE to "UPP-CMI container"; b) set the Payload container IE to the UPP-CMI container which was not forwarded; and c) set the 5GMM cause IE to the 5GMM cause #94 "User plane positioning not authorized". In case n) in subclause 5.4.5.3.1, the AMF shall: a) set the Payload container type IE to "Multiple payloads"; b) set each payload container entry of the Payload container IE (see subclause 9.11.3.39) as follows: i) set the payload container type field of the payload container entry to a payload container type value set in the Payload container type IE as specified for cases a) to m3) above; ii) set the payload container entry contents field of the payload container entry to the payload container contents set in the Payload container IE as specified for cases a) to m3) above; iii) set the optional IE fields, if any, to the optional associated information as specified for cases a) to m3) above. Figure 5.4.5.3.2.1: Network-initiated NAS transport 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 | 5.4.5.3.2 |
6,519 | 5.15 RAN Information Management (RIM) procedures 5.15.1 General | The RAN Information Management (RIM) procedures provide a generic mechanism for the exchange of arbitrary information between applications belonging to the RAN nodes. The RAN information is transferred via the MME and SGSN core network node(s). In order to make the RAN information transparent for the Core Network, the RAN information is included in a RIM container that shall not be interpreted by the Core Network nodes. The RIM procedures are optional both in the RAN and the CN nodes. For the Gb interface the use of RIM procedures is negotiated at start/restart of the Gb link. For the Iu interface there is no negotiation of using RIM procedures or not at Iu link start/restart. The RAN information is transferred in RIM containers from the source RAN node to the destination RAN node by use of messages. Source and destination RAN nodes can be E-UTRAN, UTRAN or GERAN. Each message carrying the RIM container is routed and relayed independently by the core network node(s). Any relation between messages is transparent for the MME/SGSN, i.e. a request/response exchange between RIM applications, for example, is routed and relayed as two independent messages by the MME/SGSN. The interfaces which will be used are the Gb, the Iu, the S1, Gn and the S3 interfaces. The RAN information in the RIM container shall be transparent for the Core Network. An MME or SGSN supporting the RIM procedures provides addressing, routing and relaying functions. | 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.15 |
6,520 | 7.2 Protocol States | RRC supports the following states which can be characterised as follows: - RRC_IDLE: - PLMN selection; - Broadcast of system information; - Cell re-selection mobility; - Paging for mobile terminated data is initiated by 5GC; - Transfer of MBS broadcast data to the UE over MRB(s); - DRX for CN paging configured by NAS. - RRC_INACTIVE: - PLMN selection; - Broadcast of system information; - Cell re-selection mobility; - Paging is initiated by NG-RAN (RAN paging); - RAN-based notification area (RNA) is managed by NG- RAN; - DRX for RAN paging configured by NG-RAN; - 5GC - NG-RAN connection (both C/U-planes) is established for UE; - The UE Inactive AS context is stored in NG-RAN and the UE; - NG-RAN knows the RNA which the UE belongs to; - Transfer of MBS broadcast data to the UE over MRB(s); - Transfer of unicast data and/or signalling to/from the UE over radio bearers configured for SDT. - RRC_CONNECTED: - 5GC - NG-RAN connection (both C/U-planes) is established for UE; - The UE AS context is stored in NG-RAN and the UE; - NG-RAN knows the cell which the UE belongs to; - Transfer of unicast data to/from the UE; - Transfer of MBS multicast/broadcast data to the UE over MRB(s); - Network controlled mobility including measurements. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 7.2 |
6,521 | 30.3 Structure of Area Session ID | The concept of Area Session ID is defined in 3GPP TS 23.247[ Architectural enhancements for 5G multicast-broadcast services ] [140]. Area Session IDs are used for MBS sessions with location dependent content. An Area Session ID together with an MBS Session ID (i.e. TMGI or Source Specific IP Multicast address) shall uniquely identify an MBS session in a specific MBS Service Area. NOTE: For a location-dependent MBS session, the same MBS Session ID but a different Area Session ID are used for each MBS Service Area. Different MB-SMFs and/or MB-UPFs can be assigned for different MBS service areas in an MBS session. An Area Session Identity shall be a decimal number between 0 and 65535 (inclusive). | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 30.3 |
6,522 | 6.4.1.4.3 Handling of network rejection not due to congestion control | If the 5GSM cause value is different from #26 "insufficient resources", #28 "unknown PDU session type", #39 "reactivation requested", #46 "out of LADN service area", #50 "PDU session type IPv4 only allowed", #51 "PDU session type IPv6 only allowed", #54 "PDU session does not exist", #57 "PDU session type IPv4v6 only allowed", #58 "PDU session type Unstructured only allowed", #61 "PDU session type Ethernet only allowed", #67 "insufficient resources for specific slice and DNN", #68 "not supported SSC mode", and #69 "insufficient resources for specific slice", #86 "UAS services not allowed", and #33 "requested service option not subscribed" upon sending PDU SESSION ESTABLISHMENT REQUEST to establish an MA PDU session, and the Back-off timer value IE is included, the UE shall behave as follows: (if the UE is a UE configured for high priority access in selected PLMN or SNPN, exceptions are specified in subclause 6.2.12): a) if the timer value indicates neither zero nor deactivated and: 1) if the UE provided a DNN and S-NSSAI to the network during the PDU session establishment and the 5GSM cause value is different from #27 "missing or unknown DNN", the UE shall start the back-off timer with the value provided in the Back-off timer value IE for the PDU session establishment procedure and: i) in a PLMN, [PLMN, DNN, (mapped) HPLMN S-NSSAI] combination. The UE shall not send another PDU SESSION ESTABLISHMENT REQUEST message for the same DNN and (mapped) HPLMN S-NSSAI in the current PLMN, until the back-off timer expires, the UE is switched off, or the USIM is removed; or ii) in an SNPN, [SNPN, selected entry of the "list of subscriber data" or selected PLMN subscription, DNN, (mapped) subscribed SNPN S-NSSAI] combination. The UE shall not send another PDU SESSION ESTABLISHMENT REQUEST message for the same DNN and (mapped) subscribed SNPN S-NSSAI in the current SNPN using the selected entry of the "list of subscriber data" or selected PLMN subscription, until the back-off timer expires, the UE is switched off, the USIM is removed, or the selected entry of the "list of subscriber data" is updated; 2) if the UE provided a DNN to the network during the PDU session establishment and the 5GSM cause value is #27 "missing or unknown DNN", the UE shall start the back-off timer with the value provided in the Back-off timer value IE for the PDU session establishment procedure and: i) in a PLMN, [PLMN, DNN] combination. The UE shall not send another PDU SESSION ESTABLISHMENT REQUEST message for the same DNN in the current PLMN, until the back-off timer expires, the UE is switched off, or the USIM is removed; or ii) in an SNPN, [SNPN, selected entry of the "list of subscriber data" or selected PLMN subscription, DNN] combination. The UE shall not send another PDU SESSION ESTABLISHMENT REQUEST message for the same DNN in the current SNPN using the selected entry of the "list of subscriber data" or selected PLMN subscription, until the back-off timer expires, the UE is switched off, the USIM is removed, or the selected entry of the "list of subscriber data" is updated; 3) if the UE did not provide a DNN or S-NSSAI or any of the two parameters to the network during the PDU session establishment and the 5GSM cause value is different from #27 "missing or unknown DNN", it shall start the back-off timer accordingly for the PDU session establishment procedure and: i) in a PLMN, [PLMN, DNN, no S-NSSAI], [PLMN, no DNN, (mapped) HPLMN S-NSSAI] or [PLMN, no DNN, no S-NSSAI] combination. Dependent on the combination, the UE shall not send another PDU SESSION ESTABLISHMENT REQUEST message for the same [PLMN, DNN, no S-NSSAI], [PLMN, no DNN, (mapped) HPLMN S-NSSAI] or [PLMN, no DNN, no S-NSSAI] combination in the current PLMN, until the back-off timer expires, the UE is switched off, or the USIM is removed; or ii) in an SNPN, [SNPN, selected entry of the "list of subscriber data" or selected PLMN subscription, DNN, no S-NSSAI], [SNPN, selected entry of the "list of subscriber data" or selected PLMN subscription, no DNN, (mapped) subscribed SNPN S-NSSAI] or [SNPN, selected entry of the "list of subscriber data" or selected PLMN subscription, no DNN, no S-NSSAI] combination. Dependent on the combination, the UE shall not send another PDU SESSION ESTABLISHMENT REQUEST message for the same [SNPN, selected entry of the "list of subscriber data" or selected PLMN subscription, DNN, no S-NSSAI], [SNPN, selected entry of the "list of subscriber data" or selected PLMN subscription, no DNN, (mapped) subscribed SNPN S-NSSAI] or [SNPN, selected entry of the "list of subscriber data" or selected PLMN subscription, no DNN, no S-NSSAI] combination in the current PLMN using the selected entry of the "list of subscriber data" or selected PLMN subscription, until the back-off timer expires, the UE is switched off, the USIM is removed or the selected entry of the "list of subscriber data" is updated; or 4) if the UE did not provide a DNN to the network during the PDU session establishment and the 5GSM cause value is #27 "missing or unknown DNN", it shall start the back-off timer accordingly for the PDU session establishment procedure and: i) in a PLMN, [PLMN, no DNN] combination. The UE shall not send another PDU SESSION ESTABLISHMENT REQUEST message for the same [PLMN, no DNN] in the current PLMN, until the back-off timer expires, the UE is switched off, or the USIM is removed; or ii) in an SNPN, [SNPN, selected entry of the "list of subscriber data" or selected PLMN subscription, no DNN] combination. The UE shall not send another PDU SESSION ESTABLISHMENT REQUEST message for the same [SNPN, selected entry of the "list of subscriber data" or selected PLMN subscription, no DNN] in the current PLMN, using the selected entry of the "list of subscriber data" or selected PLMN subscription, until the back-off timer expires, the UE is switched off, the USIM is removed or the selected entry of the "list of subscriber data" is updated; b) if the timer value indicates that this timer is deactivated and: 1) if the UE provided a DNN and S-NSSAI to the network during the PDU session establishment and the 5GSM cause value is different from #27 "missing or unknown DNN", the UE shall not send another PDU SESSION ESTABLISHMENT REQUEST message for: i) in a PLMN, the same DNN and (mapped) HPLMN S-NSSAI in the current PLMN, until the UE is switched off, or the USIM is removed; or ii) in an SNPN, the same DNN and (mapped) subscribed SNPN S-NSSAI in the current SNPN using the selected entry of the "list of subscriber data" or selected PLMN subscription, until the UE is switched off, the USIM is removed, or the selected entry of the "list of subscriber data" is updated; 2) if the UE provided a DNN to the network during the PDU session establishment and the 5GSM cause value is #27 "missing or unknown DNN", the UE shall not send another PDU SESSION ESTABLISHMENT REQUEST message for: i) in a PLMN, the same DNN in the current PLMN, until the UE is switched off, or the USIM is removed; or ii) in an SNPN, the same DNN in the current SNPN using the selected entry of the "list of subscriber data" or selected PLMN subscription, until the UE is switched off, the USIM is removed, or the selected entry of the "list of subscriber data" is updated; 3) if the UE did not provide a DNN or S-NSSAI or any of the two parameters to the network during the PDU session establishment and the 5GSM cause value is different from #27 "missing or unknown DNN", the UE shall not send another PDU SESSION ESTABLISHMENT REQUEST message for: i) in a PLMN, the same [PLMN, DNN, no S-NSSAI], [PLMN, no DNN, (mapped) HPLMN S-NSSAI] or [PLMN, no DNN, no S-NSSAI] combination in the current PLMN, until the UE is switched off, or the USIM is removed; or ii) in an SNPN, the same [SNPN, the selected entry of the "list of subscriber data" or selected PLMN subscription, DNN, no S-NSSAI], [SNPN, the selected entry of the "list of subscriber data" or selected PLMN subscription, no DNN, (mapped) subscribed SNPN S-NSSAI] or [SNPN, the selected entry of the "list of subscriber data" or selected PLMN subscription, no DNN, no S-NSSAI] combination in the current SNPN using the selected entry of the "list of subscriber data" or selected PLMN subscription, until the UE is switched off, the USIM is removed, or the selected entry of the "list of subscriber data" is updated; or 4) if the UE did not provide a DNN to the network during the PDU session establishment and the 5GSM cause value is #27 "missing or unknown DNN", the UE shall not send another PDU SESSION ESTABLISHMENT REQUEST message for: i) in a PLMN, the same [PLMN, no DNN] in the current PLMN, until the UE is switched off, or the USIM is removed; or ii) in an SNPN, the same [SNPN, the selected entry of the "list of subscriber data" or selected PLMN subscription, no DNN] in the current SNPN using the selected entry of the "list of subscriber data" or selected PLMN subscription, until the UE is switched off, the USIM is removed, or the selected entry of the "list of subscriber data" is updated; and c) if the timer value indicates zero and the 5GSM cause value is different from #27 "missing or unknown DNN", the UE may send another PDU SESSION ESTABLISHMENT REQUEST message for: 1) in a PLMN, the same combination of [PLMN, DNN, (mapped) HPLMN S-NSSAI], [PLMN, DNN, no S-NSSAI], [PLMN, no DNN, (mapped) HPLMN S-NSSAI], or [PLMN, no DNN, no S-NSSAI] in the current PLMN. If the timer value indicates zero and the 5GSM cause value is #27 "missing or unknown DNN", the UE may send another PDU SESSION ESTABLISHMENT REQUEST message for the same combination of [PLMN, DNN], or [PLMN, no DNN] in the current PLMN; or 2) in an SNPN, the same combination of [SNPN, the selected entry of the "list of subscriber data" or selected PLMN subscription, DNN, (mapped) subscribed SNPN S-NSSAI], [SNPN, the selected entry of the "list of subscriber data" or selected PLMN subscription, DNN, no S-NSSAI], [SNPN, the selected entry of the "list of subscriber data" or selected PLMN subscription, no DNN, (mapped) subscribed S-NSSAI], or [SNPN, the selected entry of the "list of subscriber data" or selected PLMN subscription, no DNN, no S-NSSAI] in the current SNPN using the selected entry of the "list of subscriber data" or selected PLMN subscription. If the timer value indicates zero and the 5GSM cause value is #27 "missing or unknown DNN", the UE may send another PDU SESSION ESTABLISHMENT REQUEST message for the same combination of [SNPN, the selected entry of the "list of subscriber data" or selected PLMN subscription, DNN], or [SNPN, the selected entry of the "list of subscriber data" or selected PLMN subscription, no DNN] in the current SNPN using the selected entry of the "list of subscriber data" or selected PLMN subscription. If the Back-off timer value IE is not included, then the UE shall ignore the Re-attempt indicator IE provided by the network in the PDU SESSION ESTABLISHMENT REJECT message, if any. a) Additionally, if the 5GSM cause value is #8 "operator determined barring", #32 "service option not supported", #33 "requested service option not subscribed" upon sending PDU SESSION ESTABLISHMENT REQUEST not to establish an MA PDU session, or #70 "missing or unknown DNN in a slice", then: 1) the UE not operating in SNPN access operation mode shall proceed as follows: i) if the UE is registered in the HPLMN or in a PLMN that is within the EHPLMN list, the UE shall behave as described above in the present subclause using the configured SM Retry Timer value as specified in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [17] or in USIM file NASCONFIG as specified in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [22], if available, as back-off timer value; and NOTE 1: The way to choose one of the configured SM Retry Timer values for back-off timer value is up to UE implementation if the UE is configured with: - an SM Retry Timer value in ME as specified in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [17]; and - an SM Retry Timer value in USIM file NASCONFIG as specified in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [22]. ii) otherwise, if the UE is not registered in its HPLMN or in a PLMN that is within the EHPLMN list, or if the SM Retry Timer value is not configured, the UE shall behave as described above in the present subclause, using the default value of 12 minutes for the back-off timer; or 2) the UE operating in SNPN access operation mode shall proceed as follows: i) if: A) the SM Retry Timer value for the current SNPN as specified in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [17] is available; or B) the UE used the USIM for registration to the current SNPN and the SM Retry Timer value in USIM file NASCONFIG as specified in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [22] is available; then the UE shall behave as described above in the present subclause using the configured SM Retry Timer value as back-off timer value; or NOTE 2: The way to choose one of the configured SM Retry Timer values for back-off timer value is up to UE implementation if both conditions in bullets A) and B) above are satisfied. ii) otherwise, the UE shall behave as described above in the present subclause, using the default value of 12 minutes for the back-off timer. b) For 5GSM cause value #27 "missing or unknown DNN", then: 1) the UE not operating in SNPN access operation mode shall proceed as follows: i) if the UE is registered in the HPLMN or in a PLMN that is within the EHPLMN list, the UE shall start the back-off timer with the configured SM Retry Timer value as specified in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [17] or in USIM file NASCONFIG as specified in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [22], if available, as back-off timer value for the PDU session establishment procedure and the [PLMN, DNN] or [PLMN, no DNN] combination. The UE shall not send another PDU SESSION ESTABLISHMENT REQUEST message for the same DNN in the current PLMN, until the back-off timer expires, the UE is switched off or the USIM is removed; and NOTE 3: The way to choose one of the configured SM Retry Timer values for back-off timer value is up to UE implementation if the UE is configured with: - an SM Retry Timer value in ME as specified in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [17]; and - an SM Retry Timer value in USIM file NASCONFIG as specified in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [22]. ii) otherwise, if the UE is not registered in its HPLMN or in a PLMN that is within the EHPLMN list, or if the SM Retry Timer value is not configured, the UE shall start the back-off timer with the default value of 12 minutes as back-off timer value for the PDU session establishment procedure and the [PLMN, DNN] or [PLMN, no DNN] combination. The UE shall not send another PDU SESSION ESTABLISHMENT REQUEST message for the same DNN in the current PLMN, until the back-off timer expires, the UE is switched off or the USIM is removed; or 2) the UE operating in SNPN access operation mode shall proceed as follows: i) if: A) the SM Retry Timer value for the current SNPN as specified in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [17] is available; or B) the UE used the USIM for registration to the current SNPN and the SM Retry Timer value in USIM file NASCONFIG as specified in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [22] is available; then: the UE shall start the back-off timer with the configured SM Retry Timer value as back-off timer value for the PDU session establishment procedure and the [SNPN, selected entry of the "list of subscriber data" or selected PLMN subscription, DNN] or [SNPN, selected entry of the "list of subscriber data" or selected PLMN subscription, no DNN] combination. The UE shall not send another PDU SESSION ESTABLISHMENT REQUEST message for the same DNN in the current SNPN using the selected entry in the "list of subscriber data" or selected PLMN subscription, until the back-off timer expires, the UE is switched off, the UICC containing the USIM is removed or the selected entry of the "list of subscriber data" is updated; or NOTE 4: The way to choose one of the configured SM Retry Timer values for back-off timer value is up to UE implementation if both conditions in bullets A) and B) above are satisfied. ii) otherwise: - the UE shall start the back-off timer with the default value of 12 min as back-off timer value for the PDU session establishment procedure and the [SNPN, selected entry of the "list of subscriber data" or selected PLMN subscription, DNN] or [SNPN, selected entry in the "list of subscriber data" or selected PLMN subscription, no DNN] combination. The UE shall not send another PDU SESSION ESTABLISHMENT REQUEST message for the same DNN in the current SNPN using the selected entry of the "list of subscriber data", until the back-off timer expires, the UE is switched off, the UICC containing the USIM is removed or the selected entry of the "list of subscriber data" is updated; and c) For 5GSM cause values different from #8 "operator determined barring", #27 "missing or unknown DNN", #32 "service option not supported", #33 "requested service option not subscribed" and #70 "missing or unknown DNN in a slice", the UE behaviour regarding the start of a back-off timer is unspecified. The UE shall not stop any back-off timer: a) upon a PLMN or SNPN change; b) upon an inter-system change; or c) upon registration over another access type. If the network indicates that a back-off timer for the PDU session establishment procedure is deactivated, then it remains deactivated; a) upon a PLMN or SNPN change; b) upon an inter-system change; or c) upon registration over another access type. NOTE 5: This means the back-off timer can still be running or be deactivated for the given 5GSM procedure when the UE returns to the PLMN or SNPN or when it performs inter-system change back from S1 mode to N1 mode. Thus, the UE can still be prevented from sending another PDU SESSION ESTABLISHMENT REQUEST message for the combination of [PLMN, DNN, (mapped) HPLMN S-NSSAI], [PLMN, DNN, no S-NSSAI], [PLMN, no DNN, (mapped) HPLMN S-NSSAI], [PLMN, no DNN, no S-NSSAI], [PLMN, DNN], or [PLMN, no DNN] in the PLMN, or for the combination of [SNPN, the selected entry of the "list of subscriber data" or selected PLMN subscription, DNN, (mapped) subscribed S-NSSAI], [SNPN, the selected entry of the "list of subscriber data" or selected PLMN subscription, DNN, no S-NSSAI], [SNPN, the selected entry of the "list of subscriber data" or selected PLMN subscription, no DNN, (mapped) subscribed S-NSSAI], [SNPN, the selected entry of the "list of subscriber data" or selected PLMN subscription, no DNN, no S-NSSAI], [SNPN, the selected entry of the "list of subscriber data" or selected PLMN subscription, DNN], or [SNPN, the selected entry of the "list of subscriber data" or selected PLMN subscription, no DNN] in the SNPN. If the back-off timer is started upon receipt of a PDU SESSION ESTABLISHMENT REJECT (i.e. the timer value was provided by the network, a configured value is available or the default value is used as explained above) or the back-off timer is deactivated, the UE behaves as follows: a) after a PLMN or SNPN change: 1) the UE may send a PDU SESSION ESTABLISHMENT REQUEST message for: i) in a PLMN, the combination of [new PLMN, DNN, (mapped) HPLMN S-NSSAI], [new PLMN, DNN, no S-NSSAI], [new PLMN, no DNN, (mapped) HPLMN S-NSSAI], or [new PLMN, no DNN, no S-NSSAI] in the new PLMN, if the back-off timer is not running and is not deactivated for the PDU session establishment procedure and the combination of [new PLMN, DNN, (mapped) HPLMN S-NSSAI], [new PLMN, DNN, no S-NSSAI], [new PLMN, no DNN, (mapped) HPLMN S-NSSAI], or [new PLMN, no DNN, no S-NSSAI]; or ii) in an SNPN, the combination of [new SNPN, the selected entry of the "list of subscriber data" or selected PLMN subscription, DNN, (mapped) subscribed SNPN S-NSSAI], [new SNPN, the selected entry of the "list of subscriber data" or selected PLMN subscription, DNN, no S-NSSAI], [new PLMN, the selected entry of the "list of subscriber data" or selected PLMN subscription, no DNN, (mapped) subscribed SNPN S-NSSAI], or [new SNPN, the selected entry of the "list of subscriber data" or selected PLMN subscription, no DNN, no S-NSSAI] in the new SNPN, if the back-off timer is not running and is not deactivated for the PDU session establishment procedure and the combination of [new SNPN, the selected entry of the "list of subscriber data" or selected PLMN subscription, DNN, (mapped) subscribed SNPN S-NSSAI], [new SNPN, the selected entry of the "list of subscriber data" or selected PLMN subscription, DNN, no S-NSSAI], [new SNPN, the selected entry of the "list of subscriber data" or selected PLMN subscription, no DNN, (mapped) subscribed SNPN S-NSSAI], or [new SNPN, the selected entry of the "list of subscriber data" or selected PLMN subscription, no DNN, no S-NSSAI]; 2) as an implementation option, for the 5GSM cause value #8 "operator determined barring", #32 "service option not supported", #33 "requested service option not subscribed" and #70 "missing or unknown DNN in a slice", if the network does not include a Re-attempt indicator IE, the UE may decide not to automatically send another PDU SESSION ESTABLISHMENT REQUEST message for: i) in a PLMN, the same combination of [PLMN, DNN, (mapped) HPLMN S-NSSAI], [PLMN, DNN, no S-NSSAI], [PLMN, no DNN, (mapped) HPLMN S-NSSAI], or [PLMN, no DNN, no S-NSSAI] using the same PDU session type if the UE is registered to a new PLMN which is in the list of equivalent PLMNs; or ii) in an SNPN, if the UE supports equivalent SNPNs, the same combination of [SNPN, the selected entry of the "list of subscriber data" or selected PLMN subscription, DNN, (mapped) subscribed SNPN S-NSSAI], [SNPN, the selected entry of the "list of subscriber data" or selected PLMN subscription, DNN, no S-NSSAI], [SNPN, the selected entry of the "list of subscriber data" or selected PLMN subscription, no DNN, (mapped) subscribed SNPN S-NSSAI], or [SNPN, the selected entry of the "list of subscriber data" or selected PLMN subscription, no DNN, no S-NSSAI] using the same PDU session type and using the selected entry of the "list of subscriber data" or selected PLMN subscription, if the UE is registered to a new SNPN which is in the list of equivalent SNPNs; and 3) as an implementation option, for the 5GSM cause value #27 "missing or unknown DNN", if the network does not include a Re-attempt indicator IE, the UE may decide not to automatically send another PDU SESSION ESTABLISHMENT REQUEST message for: i) in a PLMN, the same combination of [PLMN, DNN] or [PLMN, no DNN] using the same PDU session type if the UE is registered to a new PLMN which is in the list of equivalent PLMNs; or ii) in an SNPN, if the UE supports equivalent SNPNs, the same combination of [SNPN, the selected entry of the "list of subscriber data" or selected PLMN subscription, DNN] or [SNPN, the selected entry of the "list of subscriber data" or selected PLMN subscription, no DNN] using the same PDU session type if the UE is registered to a new SNPN which is in the list of equivalent SNPNs; or b) if the network does not include the Re-attempt indicator IE to indicate whether re-attempt in S1 mode is allowed, or the UE ignores the Re-attempt indicator IE, e.g. because the Back-off timer value IE is not included, then: 1) if the UE is registered in its HPLMN or in a PLMN that is within the EHPLMN list and the back-off timer is running for the combination of [PLMN, DNN, (mapped) HPLMN S-NSSAI] or [PLMN, DNN, no S-NSSAI], the UE shall apply the configured SM_RetryAtRATChange value as specified in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [17] or in USIM file NASCONFIG as specified in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [22], if available, to determine whether the UE may attempt a PDN connectivity procedure for the same [PLMN, DNN] combination in S1 mode. If the back-off timer is running for the combination of [PLMN, no DNN, (mapped) HPLMN S-NSSAI] or [PLMN, no DNN, no S-NSSAI], the same applies for the PDN connectivity procedure for the [PLMN, no DNN] combination in S1 mode accordingly; and NOTE 6: The way to choose one of the configured SM_RetryAtRATChange values for back-off timer value is up to UE implementation if the UE is configured with: - an SM_RetryAtRATChange value in ME as specified in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [17]; and - an SM_RetryAtRATChange value in USIM file NASCONFIG as specified in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [22]. 2) if the UE is not registered in its HPLMN or in a PLMN that is within the EHPLMN list, or if the NAS configuration MO as specified in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [17] is not available and the value for inter-system change is not configured in the USIM file NASCONFIG, then the UE behaviour regarding a PDN connectivity procedure for the same [PLMN, DNN] or [PLMN, no DNN] combination in S1 mode is unspecified; and c) if the network includes the Re-attempt indicator IE indicating that re-attempt in an equivalent PLMN or SNPN is not allowed, then depending on the timer value received in the Back-off timer value IE, for: 1) in a PLMN, each combination of a PLMN from the equivalent PLMN list and the respective [DNN, (mapped) HPLMN S-NSSAI], [DNN, no S-NSSAI], [no DNN, (mapped) HPLMN S-NSSAI], or [no DNN, no S-NSSAI] combination, the UE shall start a back-off timer for the PDU session establishment procedure with the value provided by the network, or deactivate the respective back-off timer as follows: i) if the Re-attempt indicator IE additionally indicates that re-attempt in S1 mode is allowed, the UE shall start or deactivate the back-off timer for N1 mode only; and ii) otherwise, the UE shall start or deactivate the back-off timer for S1 and N1 mode; or 2) in a SNPN, if the UE supports equivalent SNPNs, each combination of a SNPN from the equivalent SNPN list and the respective [the selected entry of the "list of subscriber data" or selected PLMN subscription, DNN, (mapped) subscribed SNPN S-NSSAI], [the selected entry of the "list of subscriber data" or selected PLMN subscription, DNN, no S-NSSAI], [the selected entry of the "list of subscriber data" or selected PLMN subscription, no DNN, (mapped) subscribed SNPN S-NSSAI], or [the selected entry of the "list of subscriber data" or selected PLMN subscription, no DNN, no S-NSSAI] combination, the UE shall start a back-off timer for the PDU session establishment procedure with the value provided by the network, or deactivate the respective back-off timer, for N1 mode. If the back-off timer for a [PLMN, DNN] or [PLMN, no DNN] combination, was started or deactivated in S1 mode upon receipt of PDN CONNECTIVITY REJECT message (see 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15]) and the network indicated that re-attempt in N1 mode is allowed, then this back-off timer does not prevent the UE from sending a PDU SESSION ESTABLISHMENT REQUEST message in this PLMN for the same DNN, or without DNN, after inter-system change to N1 mode. If the network indicated that re-attempt in N1 mode is not allowed, the UE shall not send any PDU SESSION ESTABLISHMENT REQUEST message in this PLMN for the same DNN in combination with any S-NSSAI or without S-NSSAI, or in this PLMN without DNN in combination with any S-NSSAI or without S-NSSAI, after inter-system change to N1 mode until the timer expires, the UE is switched off or the USIM is removed. NOTE 7: The back-off timer is used to describe a logical model of the required UE behaviour. This model does not imply any specific implementation, e.g. as a timer or timestamp. NOTE 8: Reference to back-off timer in this section can either refer to use of timer T3396 or to use of a different packet system specific timer within the UE. Whether the UE uses T3396 as a back-off timer or it uses different packet system specific timers as back-off timers is left up to UE implementation. When the back-off timer is running or the timer is deactivated, the UE is allowed to initiate a PDU session establishment procedure if the procedure is for emergency services. If the 5GSM cause value is #28 "unknown PDU session type" and the PDU SESSION ESTABLISHMENT REQUEST message contained a PDU session type IE indicating a PDU session type, the UE shall ignore the Back-off timer value IE and Re-attempt indicator IE provided by the network, if any. The UE may send another PDU SESSION ESTABLISHMENT REQUEST message to establish a new PDU session with the PDU session type IE indicating another PDU session type, e.g. using another value which can be used for the rejected component in the same route selection descriptor as specified in 3GPP TS 24.526[ User Equipment (UE) policies for 5G System (5GS); Stage 3 ] [19]. The behaviour of the UE for 5GSM cause value #28 also applies if the PDU session is a MA PDU Session. If the 5GSM cause value is #39 "reactivation requested", the UE shall ignore the Back-off timer value IE and Re-attempt indicator IE provided by the network, if any. NOTE 9: Further UE behaviour upon receipt of 5GSM cause value #39 is up to the UE implementation. If the 5GSM cause value is #46 "out of LADN service area", the UE shall ignore the Back-off timer value IE and Re-attempt indicator IE provided by the network, if any. If the UE is not located inside the LADN service area, the UE shall not send another PDU SESSION ESTABLISHMENT REQUEST message or another PDU SESSION MODIFICATION REQUEST message except for indicating a change of 3GPP PS data off UE status for the LADN DNN provided by the UE during the PDU session establishment procedure until the LADN information for the specific LADN DNN or the extended LADN information for the specific LADN DNN and S-NSSAI is updated as described in subclause 5.4.4 and subclause 5.5.1. If the UE is not located inside the LADN service area, the UE shall not indicate the PDU session(s) for the LADN DNN provided by the UE during the PDU session establishment procedure in the Uplink data status IE included in the SERVICE REQUEST message until the LADN information for the specific LADN DNN or the extended LADN information for the specific LADN DNN and S-NSSAI is updated as described in subclause 5.4.4 and subclause 5.5.1. NOTE 10: Based on UE implementation, the UE locating inside the LADN service area can send another PDU SESSION ESTABLISHMENT REQUEST message or PDU SESSION MODIFICATION REQUEST message for the LADN DNN which was rejected with the 5GSM cause value #46 "out of LADN service area". NOTE 10A: If the UE does not receive a CONFIGURATION UPDATE COMMAND message with new LADN information within an implementation dependent time, the UE can request this information by initiating a registration procedure for mobility or periodic registration update (see subclause 5.5.1.3.2, item q). If the 5GSM cause value is #50 "PDU session type IPv4 only allowed", #51 "PDU session type IPv6 only allowed", #57 "PDU session type IPv4v6 only allowed", #58 "PDU session type Unstructured only allowed", or #61 "PDU session type Ethernet only allowed", the UE shall ignore the Back-off timer value IE provided by the network, if any. The UE shall evaluate the URSP rules if available as specified in 3GPP TS 24.526[ User Equipment (UE) policies for 5G System (5GS); Stage 3 ] [19]. The UE shall not subsequently send another PDU SESSION ESTABLISHMENT REQUEST message for: a) in a PLMN, the same DNN (or no DNN, if no DNN was indicated by the UE) and the same (mapped) HPLMN S-NSSAI (or no S-NSSAI, if no S-NSSAI was indicated by the UE) to obtain a PDU session type different from the one allowed by the network until any of the following conditions is fulfilled: 1) the UE is registered to a new PLMN which was not in the list of equivalent PLMNs at the time when the PDU SESSION ESTABLISHMENT REJECT message was received; 2) the UE is registered to a new PLMN which was in the list of equivalent PLMNs at the time when the PDU SESSION ESTABLISHMENT REJECT message was received, and either the network did not include a Re-attempt indicator IE in the PDU SESSION ESTABLISHMENT REJECT message or the Re-attempt indicator IE included in the message indicated that re-attempt in an equivalent PLMN is allowed; 3) the UE is switched off; or 4) the USIM is removed; or b) in an SNPN, the same DNN (or no DNN, if no DNN was indicated by the UE) and the same (mapped) subscribed SNPN S-NSSAI (or no S-NSSAI, if no S-NSSAI was indicated by the UE), using the selected entry of the "list of subscriber data" or selected PLMN subscription until any of the following conditions is fulfilled: 1) the UE is registered to a new SNPN which was not in the list of equivalent SNPNs at the time when the PDU SESSION ESTABLISHMENT REJECT message was received; 2) the UE is registered to a new SNPN which was in the list of equivalent SNPNs at the time when the PDU SESSION ESTABLISHMENT REJECT message was received, and either the network did not include a Re-attempt indicator IE in the PDU SESSION ESTABLISHMENT REJECT message or the Re-attempt indicator IE included in the message indicated that re-attempt in an equivalent SNPN is allowed; 3) the UE is switched off; 4) the USIM is removed; or 5) the selected entry of the "list of subscriber data" is updated. For the 5GSM cause values #50 "PDU session type IPv4 only allowed", #51 "PDU session type IPv6 only allowed", #57 "PDU session type IPv4v6 only allowed", #58 "PDU session type Unstructured only allowed", and #61 "PDU session type Ethernet only allowed", the UE shall ignore the value of the RATC bit in the Re-attempt indicator IE provided by the network, if any. NOTE 11: For the 5GSM cause values #50 "PDU session type IPv4 only allowed", #51 "PDU session type IPv6 only allowed", #57 "PDU session type IPv4v6 only allowed", #58 "PDU session type Unstructured only allowed", and #61 "PDU session type Ethernet only allowed", re-attempt in S1 mode for the same DNN (or no DNN, if no DNN was indicated by the UE) is only allowed using the PDU session type(s) indicated by the network. If the 5GSM cause value is #54 "PDU session does not exist", the UE shall ignore the Back-off timer value IE and Re-attempt indicator IE provided by the network, if any. If the PDU session establishment procedure is to perform handover of an existing PDU session between 3GPP access and non-3GPP access, the UE shall release locally the existing PDU session with the PDU session ID included in the PDU SESSION ESTABLISHMENT REJECT message. The UE may initiate another UE-requested PDU session establishment procedure with the request type set to "initial request" in the subsequent PDU SESSION ESTABLISHMENT REQUEST message to establish a PDU session with: a) in a PLMN, the same DNN (or no DNN, if no DNN was indicated by the UE) and the same (mapped) HPLMN S-NSSAI (or no S-NSSAI, if no S-NSSAI was indicated by the UE); or b) in an SNPN, the same DNN (or no DNN, if no DNN was indicated by the UE) and the same (mapped) subscribed SNPN S-NSSAI (or no S-NSSAI, if no S-NSSAI was indicated by the UE) using the selected entry of the "list of subscriber data" or selected PLMN subscription. NOTE 12: User interaction is necessary in some cases when the UE cannot re-establish the PDU session(s) automatically. If the 5GSM cause value is #68 "not supported SSC mode", the UE shall ignore the Back-off timer value IE and Re-attempt indicator IE provided by the network, if any. The UE shall evaluate the URSP rules if available as specified in 3GPP TS 24.526[ User Equipment (UE) policies for 5G System (5GS); Stage 3 ] [19]. The UE shall not subsequently send another PDU SESSION ESTABLISHMENT REQUEST message for: a) in a PLMN, the same DNN (or no DNN, if no DNN was indicated by the UE) and the same (mapped) HPLMN S-NSSAI (or no S-NSSAI, if no S-NSSAI was indicated by the UE) using the same SSC mode or an SSC mode which was not included in the Allowed SSC mode IE until any of the following conditions is fulfilled: 1) the UE is registered to a new PLMN which was not in the list of equivalent PLMNs at the time when the PDU SESSION ESTABLISHMENT REJECT message was received; 2) the SSC mode which is used to access to the DNN (or no DNN, if no DNN was indicated by the UE) and the (mapped) HPLMN S-NSSAI (or no S-NSSAI, if no S-NSSAI was indicated by the UE) is changed by the UE which subsequently requests a new SSC mode in the Allowed SSC mode IE or no SSC mode; 3) the UE is switched off; or 4) the USIM is removed; or b) in an SNPN, the same DNN (or no DNN, if no DNN was indicated by the UE) and the same subscribed SNPN S-NSSAI (or no S-NSSAI, if no S-NSSAI was indicated by the UE) using the same SSC mode or an SSC mode which was not included in the Allowed SSC mode IE, using the selected entry of the "list of subscriber data" or selected PLMN subscription until any of the following conditions is fulfilled: 1) the UE is registered to a new SNPN which was not in the list of equivalent SNPNs at the time when the PDU SESSION ESTABLISHMENT REJECT message was received; 2) the SSC mode which is used to access to the DNN (or no DNN, if no DNN was indicated by the UE) and the (mapped) subscribed SNPN S-NSSAI (or no S-NSSAI, if no S-NSSAI was indicated by the UE) is changed by the UE which subsequently requests a new SSC mode in the Allowed SSC mode IE or no SSC mode; 3) the UE is switched off; 4) the USIM is removed, or 5) the selected entry of the "list of subscriber data" is updated. If the UE receives the 5GSM cause value is #33 "requested service option not subscribed" upon sending PDU SESSION ESTABLISHMENT REQUEST to establish an MA PDU session, the UE shall ignore the Back-off timer value IE and Re-attempt indicator IE provided by the network, if any. The UE shall evaluate URSP rules, if available, as specified in 3GPP TS 24.526[ User Equipment (UE) policies for 5G System (5GS); Stage 3 ] [19] and the UE may send PDU SESSION ESTABLISHMENT REQUEST after evaluating those URSP rules. If the 5GSM cause value is #86 "UAS services not allowed", the UE shall ignore the Back-off timer value IE and Re-attempt indicator IE provided by the network, if any, and shall behave as specified in subcluase 6.4.1.4.1. Upon receipt of an indication from 5GMM sublayer that the 5GSM message was not forwarded because the DNN is not supported or not subscribed in a slice along with a PDU SESSION ESTABLISHMENT REQUEST message with the PDU session ID IE set to the PDU session ID of the PDU session, the UE shall stop timer T3580, shall abort the procedure and shall behave as follows: a) if the timer value indicates neither zero nor deactivated, the UE shall start the back-off timer with the value received from the 5GMM sublayer for the PDU session establishment procedure and: 1) in a PLMN, the [PLMN, DNN, S-NSSAI] combination or the [PLMN, DNN, no S-NSSAI] combination, if no S-NSSAI was provided during the PDU session establishment. The UE shall not send another PDU SESSION ESTABLISHMENT REQUEST message in the PLMN for the same DNN and the same S-NSSAI that were sent by the UE, or for the same DNN and no S-NSSAI if S-NSSAI that was not sent by the UE, until: i) the back-off timer expires; ii) the UE is switched off; iii) the USIM is removed; or iv) the DNN is included in the LADN information or extended LADN information and the network provides the LADN information or extended LADN information during the registration procedure or the generic UE configuration update procedure; or 2) in an SNPN, the [SNPN, the selected entry of the "list of subscriber data" or selected PLMN subscription, DNN, S-NSSAI] combination or the [SNPN, the selected entry of the "list of subscriber data" or selected PLMN subscription, DNN, no S-NSSAI] combination, if no S-NSSAI was provided during the PDU session establishment. The UE shall not send another PDU SESSION ESTABLISHMENT REQUEST message in the SNPN for the same DNN and the same S-NSSAI that were sent by the UE, or for the same DNN and no S-NSSAI if S-NSSAI that was not sent by the UE, using the selected entry of the "list of subscriber data" or selected PLMN subscription, until: i) the back-off timer expires; ii) the UE is switched off; iii) the USIM is removed; or iv) the selected entry of the "list of subscriber data" is updated; or v) the DNN is included in the LADN information or extended LADN information and the network provides the LADN information or extended LADN information during the registration procedure or the generic UE configuration update procedure; b) if the timer value is not received from the 5GMM sublayer or the timer value indicates that this timer is deactivated, the UE shall not send another PDU SESSION ESTABLISHMENT REQUEST message 1) in the PLMN for the same DNN and the same S-NSSAI that were sent by the UE, or for the same DNN and no S-NSSAI if S-NSSAI that was not sent by the UE, until: i) the UE is switched off; ii) the USIM is removed; or iii) the DNN is included in the LADN information or extended LADN information and the network provides the LADN information or extended LADN information during the registration procedure or the generic UE configuration update procedure; and 2) in the SNPN, for the same DNN and the same S-NSSAI that were sent by the UE, or for the same DNN and no S-NSSAI if S-NSSAI that was not sent by the UE, using the selected entry of the "list of subscriber data" or selected PLMN subscription, until: i) the UE is switched off; ii) the USIM is removed; iii) the selected entry of the "list of subscriber data" is updated; or iii) the DNN is included in the LADN information or extended LADN information and the network provides the LADN information or extended LADN information during the registration procedure or the generic UE configuration update procedure; and c) if the timer value indicates zero, the UE may send another PDU SESSION ESTABLISHMENT REQUEST message for: 1) in a PLMN, the same combination of [PLMN, DNN, S-NSSAI], [PLMN, DNN, no S-NSSAI] in the current PLMN; or 2) in an SNPN, the same combination of [SNPN, the selected entry of the "list of subscriber data" or selected PLMN subscription, DNN, S-NSSAI], [SNPN, the selected entry of the "list of subscriber data" or selected PLMN subscription, DNN, no S-NSSAI] in the current SNPN. | 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.4.1.4.3 |
6,523 | 8.3.2.1F Enhanced Performance Requirement Type B β Single-layer Spatial Multiplexing with TM3 interference | The requirements are specified in Table 8.3.2.1F-2, with the addition of the parameters in Table 8.3.2.1F-1 and the downlink physical channel setup according to Annex C.3.2. The purpose of these tests is to verify closed loop rank one performance on one of the antenna ports 7 or 8 without a simultaneous transmission on the other antenna port in the serving cell when the PDSCH transmission in the serving cell is interfered by PDSCH of two interfering cells applying transmission mode 3 interference model defined in clause B.6.2. In 8.3.2.1F-1, Cell 1 is the serving cell, and Cell 2, 3 are interfering cells. The downlink physical channel setup is according to Annex C.3.2 for each of Cell 1, Cell 2 and Cell 3, respectively. Table 8.3.2.1F-1: Test Parameters for Testing CDM-multiplexed DM RS (Single-layer) with TM3 interference model Table 8.3.2.1F-2: Minimum Performance for Enhanced Performance Requirement Type B, CDM-multiplexed DM RS with TM3 interference model | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.3.2.1F |
6,524 | 7.6.1.1G Minimum requirements for V2X | The V2X UE throughput shall be β₯ 95% of the maximum throughput of the reference measurement channels as specified in Annex A.8.2 with paramteters defined in Table 7.6.1.1G-1 and Table 7.6.1.1G-2. Table 7.6.1.1G-1: In band blocking parameters Table 7.6.1.1G-2: In-band blocking When UE is configured for simultaneous E-UTRA V2X sidelink and E-UTRA downlink reception for inter-band E-UTRA V2X / E-UTRA bands specified in Table 5.5G-2, the requirements in subclause 7.6.1.1G apply for the E-UTRA V2X sidelink reception and the requirements in subclause 7.6.1.1 apply for the E-UTRA downlink reception while all downlink carriers are active. For intra-band contiguous multi-carrier operation, the V2X UE throughput shall be β₯ 95% of the maximum throughput of the reference measurement channels as specified in Annex A.8.2 with paramteters defined in Table 7.6.1.1G-3 and Table 7.6.1.1G-4. Table 7.6.1.1G-3: In band blocking parameters for intra-band contiguous multi-carrier for V2X UE Table 7.6.1.1G-4: In-band blocking for intra-band contiguous multi-carrier for V2X UE | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 7.6.1.1G |
6,525 | 5.7.3 Potential service requirements | The 3GPP system shall provide the capability for an MNO to receive the UAS information regarding its 3GPP communication capabilities. The 3GPP system shall support the UAS identification data which can differentiate the UAS with UAS-capable UE and the UAS with non-UAS-capable UE. NOTE: UAS-capable UE refers to the UE which support interaction capability with UTM and certain 3GPP communication features which 3GPP provides for UAS. The 3GPP system shall support identification and reporting unauthorized UAVs to a UTM. | 3GPP TS 22.825 | Study on Remote Identification of Unmanned Aerial Systems (UAS) | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 5.7.3 |
6,526 | 10.19.2 MR-DC with 5GC | The Conditional Handover with Secondary Node procedure is used for configuration and execution of CHO with SN or CHO with candidate SCG(s). This procedure includes the cases where the SN is kept, changed or added. If the SN is kept, the UE context at the SN is kept. If the SN is changed, the UE context at the source SN is moved to the target SN. CHO with candidate SCG(s) is not supported for NE-DC and NGEN-DC. Figure 10.19.2-1: Conditional Handover with Secondary Node procedure Figure 10.19.2-1 shows an example signaling flow for Conditional Handover with Secondary Node. NOTE 1: For a CHO without SN change, the source SN and the target SN shown in Figure 10.19.2-1 are the same node. NOTE 2: For a CHO with SN addition, the source SN and steps involving the source SN in Figure 10.19.2-1 are ignored. 1. The source MN starts the conditional handover procedure by initiating the Xn Handover Preparation procedure including MCG configuration and, if the UE is configured with an SCG, SCG configuration. The source MN includes the (source) SN UE XnAP ID, SN ID, the UE context in the (source) SN and the Conditional Handover Information Request IE in the Handover Request message. In case of CHO with candidate SCG(s), the source MN also provides the maximum number of conditional reconfigurations that the candidate MN can prepare for the UE in the Handover Request message. NOTE 3: In case of the CHO with/without SN change or CHO with candidate SCG(s), the source MN may trigger the MN-initiated SN Modification procedure (to the source SN) to retrieve the current SCG configuration, if configured, before step 1. 2. If the candidate MN decides to keep the UE context in the SN, the candidate MN sends the SN Addition Request message to the SN including the SN UE XnAP ID as a reference to the UE context in the SN that was established by the source MN. If the candidate MN decides to change the SN allowing delta configuration, the candidate MN sends the SN Addition Request message to the candidate SN including the UE context in the source SN that was established by the source MN. Otherwise, the candidate MN may send the SN Addition Request message to the candidate SN including neither the SN UE XnAP ID nor the UE context in the source SN that was established by the source MN. Within the SN Addition Request message, the candidate MN also includes the CHO related information, i.e., the source MN ID and the MN UE XnAP ID in the source MN, in order to indicate that the SN Addition Preparation procedure is triggered in relation to a CHO and to enable the SN to identify requests related to the same UE. In case of CHO with candidate SCG(s), the candidate MN also provides the candidate PSCells recommended by the candidate MN via the latest measurement results for the candidate SN(s) to choose and configure the candidate SCG cell(s), and provides the maximum number of PSCells that the candidate SN can prepare for the UE in the SN Addition Request message. NOTE 3a: The target MN and other potential target MNs may trigger the SN Addition Preparation procedure to the same (target) SN. NOTE 3b: The source MN may initiate additional Xn Handover Preparation procedures towards the same or other target MNs. Based on each Xn Handover Preparation procedure, each target MN may decide to trigger SN Addition Preparation procedure. 3. The (candidate) SN replies with the SN Addition Request Acknowledge message. The (candidate) SN may include the indication of the full or delta RRC configuration. In case of CHO with candidate SCG(s), within the list of cells as indicated within the measurement results indicated by the candidate MN, the candidate SN decides the list of PSCell(s) to prepare (considering the maximum number indicated by the candidate MN) and, for each prepared PSCell, the candidate SN decides other SCG SCells and provides the new corresponding SCG radio resource configuration to the candidate MN in an NR RRC reconfiguration** message contained in the SN Addition Request Acknowledge message with the prepared PSCell ID(s). NOTE 4: In CHO with SCG configuration, it is up to the candidate MN implementation to make sure that the CG-Config provided from the (candidate) SN can be used in all CHO preparations. NOTE 4A1: In case of CHO with candidate SCG(s), the (candidate) SN assigns the same data forwarding addresses for multiple data forwarding requests from different candidate MNs and the (candidate) SN indicates to the candidate MN direct data forwarding path availability with the source SN and/or source MN, if applicable. 3a. For the SN terminated bearers using MCG resources, the candidate MN provides Xn-U DL TNL address information in the Xn-U Address Indication message. 4. The candidate MN includes within the Handover Request Acknowledge message the MN RRC reconfiguration message to be sent to the UE in order to perform the conditional handover, and may also provide forwarding addresses to the source MN. If PDU session split is performed in the target side during handover procedure, more than one data forwarding addresses corresponding to each node are included in the Handover Request Acknowledge message. The candidate MN indicates to the source MN that the UE context in the SN is kept if the candidate MN and the SN decided to keep the UE context in the SN in step 2 and step 3. In case of CHO with candidate SCG(s), the candidate MN includes a list of one or more (candidate) SNs in Handover Request Acknowledge message with the PDU Session admission results, data forwarding addresses and list of prepared PSCells for each prepared (candidate) SN. The candidate MN also indicates to the source MN the parameters of the execution condition of each prepared candidate PSCell. NOTE 4A2: In case of CHO with candidate SCG(s), the candidate MN indicates direct data forwarding path availability between the target node and the source SN in per PDU session granularity in the Handover Request Acknowledge message, if applicable. NOTE 4a0: Steps 1-4 may be produced in several instances, each instance initiated with a separate Handover Preparation procedure (step 1). The order of messages belonging to separate instances is not defined. 4a. The source MN sends the Xn-U Address Indication message to the (source) SN. This Xn-U Address Indication message notifies conditional handover to the (source) SN, which may decide to perform, if applicable, early data forwarding for SN-terminated bearers, together with the sending of an Early Status Transfer message to the source MN. NOTE 4a: Separate Xn-U Address Indication procedures may be initiated to provide different forwarding addresses of the prepared conditional handovers. In this case, it is up to the source MN and SN implementations to make sure that the Early Status Transfer message(s) from the source SN, if any, is forwarded to the right target MN. The Xn-U Address Indication procedure may further be initiated to indicate to the (source) SN to stop already initiated early data forwarding for some SN-terminated bearers, if they are no longer subject to data forwarding due to the modification or cancellation of the prepared conditional handovers. 5. The source MN sends an RRC reconfiguration message to the UE, including the CHO configuration, i.e. a list of RRC reconfiguration* messages and associated execution conditions, in which each RRC reconfiguration* message contains an MCG configuration and possibly an SCG configuration in the RRC reconfiguration** message received from the candidate SN in step 3. For each configuration of CHO with candidate SCG(s), the source MN provides an execution condition for the candidate PCell and an execution condition for the candidate PSCell. Besides, each RRC reconfiguration* message contains an MCG configuration and an SCG configuration in the RRC reconfiguration** message received from the candidate SN in step 3. NOTE 4b: In case of CHO with candidate SCG(s), the source MN can provide multiple CHO configurations for the same candidate PCell (i.e. without the SCG configuration or with the SCG configuration of different candidate PSCell). 6. The UE applies the RRC reconfiguration message received in step 5, stores the CHO configuration and replies to the MN with an RRC reconfiguration complete message. 7/8. The UE maintains connection with the source MN and, if the UE is configured with a PSCell, with the source PSCell, after receiving CHO configuration, and starts evaluating the execution condition for the candidate PCell(s) and if any, the execution condition for the candidate PSCell(s): - If at least one candidate PCell satisfies the corresponding execution condition and the associated candidate PSCell satisfies the corresponding execution condition, the UE detaches from the source MN, applies the stored corresponding configuration for that selected candidate PCell and the associated candidate PSCell, synchronises to that candidate PCell, and completes the RRC handover procedure by sending RRC reconfiguration complete* message to the target MN. The UE includes an embedded SN RRCReconfigurationComplete** message for the target SN, and information enabling the target MN to identify the target SN of the selected candidate PSCell. - Else if at least one candidate PCell satisfies the corresponding execution condition and there is no associated execution condition for a candidate PSCell, the UE detaches from the source MN, applies the stored corresponding configuration for that selected candidate PCell and, if included, the associated PSCell, synchronises to that candidate PCell and completes the RRC handover procedure by sending RRC reconfiguration complete* message to the target MN. If the stored configuration for the selected candidate PCell includes an SCG configuration, the UE includes an embedded SN RRCReconfigurationComplete** message for the target SN. - The UE releases the stored CHO configurations after successful completion of the RRC handover procedure. NOTE 5: In case the target SN includes the indication of the full RRC configuration, the MN performs release of the SN terminated radio bearer configuration and release and add of the NR SCG configuration part towards the UE. 9. If configured with bearers requiring SCG radio resources, the UE synchronizes to the (target) SN. NOTE 6: The order the UE performs Random Access towards the MN (step 7) and performs the Random Access procedure towards the (target) SN (step 9) is not defined. 10. If the RRC connection reconfiguration procedure was successful, the target MN informs the (target) SN via SN Reconfiguration Complete message. 11. The target MN sends the Handover Success message to the source MN to inform that the UE has successfully accessed the target cell. In case of CHO with candidate SCG(s), the target PSCell ID may also be included in the Handover Success message. 12a/b. The source MN sends SN Release Request message to the (source) SN including a Cause indicating MCG mobility. The source MN indicates to the (source) SN that the UE context in SN is kept, if it receives the indication from the target MN. The (source) SN acknowledges the release request. 12c. The source MN sends XN-U Address Indication message to the (source) SN to transfer data forwarding information. More than one data forwarding addresses may be provided if the PDU session is split in the target side. 12d. The source MN sends the Handover Cancel message toward the other signalling connections or other candidate MNs, if any, to cancel CHO for the UE. 12e/f. If the target MN is configured with other candidate PCell(s) associated with other candidate SN(s) than the target SN, the target MN sends the SN Release Request message(s) to the corresponding candidate SN(s). Other candidate MN(s) send(s) the SN Release Request message(s) to other candidate SN(s), if configured. The other candidate SN(s) acknowledges the release request. 13a. The (source) SN sends the Secondary RAT Data Usage Report message to the source MN and includes the data volumes delivered to and received from the UE over the NR/E-UTRA radio as described in clause 10.11.2. NOTE 7: The order the source SN sends the Secondary RAT Data Usage Report message and performs data forwarding with MN/target SN is not defined. The SN may send the report when the transmission of the related QoS is stopped. 13b. The source MN sends the Secondary RAT Data Usage Report message to AMF to provide information on the used NR/E-UTRA resource. 14. For bearers using RLC AM, the source MN sends the SN Status Transfer message to the target MN, including, if needed, SN Status received from the source SN. The target MN forwards the SN Status to the target SN, if needed. 15. If applicable, data forwarding takes place from the source side (i.e. source MN or source SN). If the SN is kept, data forwarding may be omitted for the SN terminated bearers or QoS flows kept in the SN. 16-19. The target MN initiates the Path Switch procedure. If the target MN includes multiple DL TEIDs for one PDU session in the Path Switch Request message, multiple UL TEID of the UPF for the PDU session should be included in the Path Switch Ack message in case there is TEID update in UPF. NOTE 8: If new UL TEIDs of the UPF for SN are included, the target MN performs MN initiated SN Modification procedure to provide them to the SN. 20. The target MN initiates the UE Context Release procedure towards the source MN. 21. Upon reception of the UE Context Release message from source MN, the (source) SN releases C-plane related resources associated to the UE context towards the source MN. Any ongoing data forwarding may continue. The SN shall not release the UE context associated with the target MN if the UE contest kept indication was included in the SN Release Request message in step 12a. | 3GPP TS 37.340 | Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Overall Description; Stage-2 | RAN2 | 3GPP Series : 37 , Multiple radio access technology aspects | 10.19.2 |
6,527 | 4.7.13.5 Abnormal cases in the MS | The following abnormal cases can be identified: a) Access barred because of access class control, EAB or ACDC If the service request procedure is started in response to a paging request from the network, access class barring, EAB or ACDC is not applicable. The service request procedure shall not be started. The MS stays in the current serving cell and applies normal cell reselection process. The service request procedure may be started by CM layer if it is still necessary, i.e. when access is granted or because of a cell change. If access is barred because of access class control, the service request is initiated due to a request from upper layers for PS signalling connection, ACDC is applicable to the request and the MS supports ACDC, then the service request procedure shall be started. If access is barred for a certain ACDC category, and if the service request is initiated due to a request from upper layers for PS signalling connection for a higher ACDC category and the MS supports ACDC, then the service request procedure shall be started. If an access request for an uncategorized application is barred due to ACDC , and if the service request is initiated due to a request from upper layers for PS signalling connection for a certain ACDC category and the MS supports ACDC, then the service request procedure shall be started. b) Lower layer failure without "Extended Wait Time" received from lower layers before the security mode control procedure is completed, SERVICE ACCEPT or SERVICE REJECT message is received The procedure shall be aborted except in the following implementation option cases b.1, b.2 and b.3. b.1) Release of PS signalling connection in Iu mode (i.e. RRC connection release) before the completion of the service request procedure The service request procedure shall be initiated again, if the following conditions apply: i) The original service request procedure was initiated over an existing PS signalling connection; and ii) No SECURITY MODE COMMAND message and no Non-Access Stratum (NAS) messages relating to the PS signalling connection were received after the SERVICE REQUEST message was transmitted. b.2) RR release in Iu mode (i.e. RRC connection release) with cause different than "Directed signalling connection re-establishment", for example, "Normal", or "User inactivity" (see 3GPP TS 25.331[ None ] [23c] and 3GPP TS 44.118[ None ] [111]) The service request procedure shall be initiated again, if the following conditions apply: i) The original service request procedure was initiated over an existing RRC connection and, ii) No SECURITY MODE COMMAND message and no Non-Access Stratum (NAS) messages relating to the PS signalling connection were received after the SERVICE REQUEST messge was transmitted. NOTE: The RRC connection release cause different than "Directed signalling connection re-establishment" that triggers the re-initiation of the service request procedure is implementation specific. b.3) RR release in Iu mode (i.e. RRC connection release) with cause "Directed signalling connection re-establishment" (see 3GPP TS 25.331[ None ] [23c] and 3GPP TS 44.118[ None ] [111]) The routing area updating procedure shall be initiated followed by a rerun of the service request procedure if the following condition applies: i) The service request procedure was not due to a rerun of the procedure due to "Directed signalling connection re-establishment". c) T3317 expired The MS shall enter GMM-REGISTERED state. If the MS is in PMM-IDLE mode then the MS shall increment the service request attempt counter, abort the procedure and release locally any resources allocated for the service request procedure. If the service request procedure is initiated to establish a PDN connection for emergency bearer services or the MS has a PDN connection for emergency bearer services established or the MS is an MS configured to use AC11 β 15 in selected PLMN, the service request counter shall not be incremented. If the service request attempt counter is greater than or equal to 5, the MS shall start timer T3325. The MS shall not attempt service request until expiry of timer T3325 unless: - the service request is in response to paging from the network; - the MS is an MS configured to use AC11 β 15 in selected PLMN; - the service request is initiated to establish a PDN connection for emergency bearer services; - the MS has a PDN connection for emergency bearer services established; or - the MS is registered in a new PLMN. If the MS is in PMM-CONNECTED mode, then the procedure shall be aborted. d) SERVICE REJECT received, other causes than those treated in subclause 4.7.13.4, and cases of GMM cause values #22 and #25, if considered as abnormal cases according to subclause 4.7.13.4 The procedure shall be aborted. e) Routing area update procedure is triggered If a cell change into a new routing area occurs and the necessity of routing area update procedure is determined before the security mode control procedure is completed, a SERVICE ACCEPT or SERVICE REJECT message has been received, the Service request procedure shall be aborted and the routing area updating procedure is started immediately. Follow-on request pending may be indicated in the ROUTING AREA UPDATE REQUEST for the service, which was the trigger of the aborted Service request procedure, to restart the pending service itself or the Service request procedure after the completion of the routing area updating procedure. If the Service type of the aborted SERVICE REQUEST was indicating "data", then the routing area update procedure may be followed by a re-initiated Service request procedure indicating "data", if it is still necessary. If the Service type was indicating "MBMS multicast service reception", or "MBMS broadcast service reception" the Service request procedure shall be aborted. f) Power off If the MS is in state GMM-SERVICE-REQUEST-INITIATED at power off, the GPRS detach procedure shall be performed. g) Detach procedure collision GPRS detach containing detach type "re-attach required" or "re-attach not required": If the MS receives a DETACH REQUEST message from the network in state GMM-SERVICE-REQUEST-INITIATED, the GPRS detach procedure shall be progressed and the Service request procedure shall be aborted. If the GMM cause IE, in the DETACH REQUEST message, indicated a "re-attach required", the GPRS attach procedure shall be performed. If the DETACH REQUEST message contains detach type "re-attach not required" and GMM cause #2 "IMSI unknown in HLR", the MS will follow the procedure as described below for the detach type "IMSI detach". GPRS detach containing detach type "IMSI detach": If the MS receives a DETACH REQUEST message from the network in state GMM-SERVICE-REQUEST-INITIATED, the network and the MS shall progress both procedures. h) "Extended wait time" for PS domain from the lower layers The MS shall abort the service request procedure, enter state GMM-REGISTERED, and stop timer T3317 if still running. If the SERVICE REQUEST message contained the low priority indicator set to "MS is configured for NAS signalling low priority", the MS shall start timer T3346 with the "Extended wait time" value. In other cases the MS shall ignore the "Extended wait time". The MS stays in the current serving cell and applies normal cell reselection process. The service request procedure is started, if still necessary, when timer T3346 expires or is stopped. m) Timer T3346 is running The MS shall not start the service request procedure unless: - the MS receives a paging; or - the MS is an MS configured to use AC11 β 15 in selected PLMN; or - the MS has a PDN connection for emergency bearer services established; or - the MS is establishing a PDN connection for emergency bearer services; or - the MS has a PDN connection established without the NAS signalling low priority indication or is establishing a PDN connection without the NAS signalling low priority indication, the timer T3302 and the timer T3311 are not running and the timer T3346 was started due to rejection of a NAS request message (e.g. ATTACH REQUEST, ROUTING AREA UPDATE REQUEST or SERVICE REQUEST) which contained the low priority indicator set to "MS is configured for NAS signalling low priority". The MS stays in the current serving cell and applies normal cell reselection process. The service request procedure is started, if still necessary, when timer T3346 expires or is stopped. | 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.13.5 |
6,528 | 9.9 Security mechanisms for non-SBA interfaces internal to the 5GC and between PLMNs | Non-SBA interfaces internal to the 5G Core such as N4 and N9 can be used to transport signalling data as well as privacy sensitive material, such as user and subscription data, or other parameters, such as security keys. Therefore, these interfaces shall be confidentiality, integrity, and replay protected. Roaming interfaces between PLMNs except for N32, shall be confidentiality, integrity, and replay protected. Protection for the N32 interface is specified in clauses 13.1 and 13.2.. For the protection of the above mentioned non-SBA internal and roaming interfaces except N32, IPsec ESP and IKEv2 certificate-based authentication shall be supported as specified in sub-clauses 9.1.2 of the present document with confidentiality, integrity and replay protection. This security mechanism shall be used,, unless security is provided by other means, e.g. physical security. A SEG may be used to terminate the IPsec tunnels. QoS related aspects are further described in sub-clause 9.1.3 of the present document. NOTE: It is up to the operator choice to use cryptographic solutions or other mechanisms to protect internal non-SBA interfaces such as N4 and N9. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 9.9 |
6,529 | 4.2.8.2.3 Home-routed Roaming Architecture | Figure 4.2.8.2.3-1: Home-routed Roaming architecture for 5G Core Network with untrusted non-3GPP access - N3IWF in the same VPLMN as 3GPP access Figure 4.2.8.2.3-2: Home-routed Roaming architecture for 5G Core Network with untrusted non-3GPP access - N3IWF in a different VPLMN than 3GPP access Figure 4.2.8.2.3-3: Home-routed Roaming architecture for 5G Core Network with untrusted non-3GPP access - N3IWF in HPLMN Figure 4.2.8.2.3-4: Home-routed Roaming architecture for 5G Core Network with trusted non-3GPP access using the same VPLMN as 3GPP access NOTE 1: The reference architecture in all above figures only shows the architecture and the network functions directly connected to support non-3GPP access, and other parts of the architecture are the same as defined in clause 4.2. NOTE 2: The two N2 instances in Figure 4.2.8.2.3-1 and in Figure 4.2.8.2.3-4 terminate to a single AMF for a UE which is connected to the same 5G Core Network over 3GPP access and non-3GPP access simultaneously. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.2.8.2.3 |
6,530 | 5.30.2.3 UE configuration and subscription aspects | An SNPN-enabled UE is configured with the following information for each subscribed SNPN: - PLMN ID and NID of the subscribed SNPN; - Subscription identifier (SUPI) and credentials for the subscribed SNPN; - Optionally, an N3IWF FQDN and the MCC of the country where the configured N3IWF is located; - Optionally, if the UE supports access to an SNPN using credentials from a Credentials Holder: - User controlled prioritized list of preferred SNPNs; - Credentials Holder controlled prioritized list of preferred SNPNs; - Credentials Holder controlled prioritized list of GINs; - Optionally, if the UE supports access to an SNPN using credentials from a Credentials Holder and access to an SNPN providing access for Localized Services: - User controlled prioritized list of preferred SNPNs; - Credentials Holder controlled prioritized list of preferred SNPNs for accessing Localized Services, each entry of the list includes: - an SNPN identifier; - validity information; and - optionally, location assistance information; - Credentials Holder controlled prioritized list of GINs for accessing Localized Services, each entry of the list includes: - a GIN; - validity information; and - optionally, location assistance information; - Protection scheme for concealing the SUPI as defined in TS 33.501[ Security architecture and procedures for 5G System ] [29]. NOTE 1: Additionally the UE can be configured with indication to use anonymous SUCI as defined in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [47]. Validity information consists of: - Time validity information, i.e. time periods (defined by start and end times) when access to the SNPN for accessing Localized Services is allowed; and/or Location assistance information consisting of: - Geolocation information, and/or, - Tracking Area information of serving networks, i.e. lists of TACs per PLMN ID or per PLMN ID and NID. The UE may use the location assistance information to determine where to search for the SNPNs in the Credentials Holder controlled prioritized list of SNPNs and GINs for accessing Localized Services, i.e. the location assistance information is not used for any area restriction enforcement. For an SNPN-enabled UE with SNPN subscription, the Credentials Holder controlled prioritized lists of preferred SNPNs and GINs, or Credentials Holder controlled prioritized lists of preferred SNPNs and GINs for accessing Localized Services may be updated by the Credentials Holder using the Steering of Roaming (SoR) procedure as defined in Annex C of TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [17]. Updating Credentials Holder controlled prioritized lists of preferred SNPNs and GINs, or Credentials Holder controlled prioritized lists of preferred SNPNs and GINs for accessing Localized Services via the Steering of Roaming (SoR) procedure is not applicable for Credentials Holder with AAA Server. A subscription of an SNPN is either: - identified by a SUPI containing a network-specific identifier that takes the form of a Network Access Identifier (NAI) using the NAI RFC 7542 [20] based user identification as defined in clause 28.7.2 of TS 23.003[ Numbering, addressing and identification ] [19]. The realm part of the NAI may include the NID of the SNPN; or - identified by a SUPI containing an IMSI. NOTE 2: As to route network signalling to AUSF and UDM instances serving the SNPN-enabled UE, the UE can be configured with Routing Indicator locally or updated with Routing Indicator using the UE Parameters Update via UDM Control Plane procedure defined in clause 4.20 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. When the SNPN credential is stored in the USIM, the Routing Indicator is provisioned in the USIM, when the SNPN credential is stored in the ME, the Routing Indicator is provisioned in the ME. In the case of access to an SNPN using credentials owned by a Credentials Holder as specified in clause 5.30.2.9.2 and clause 5.30.2.9.3, the SUPI shall also contain identification for the Credentials Holder (i.e. the realm in the case of Network Specific Identifier based SUPI or the MCC and MNC in the case of an IMSI based SUPI). In the case of access to an SNPN using credentials owned by a Credentials Holder using AAA-S as specified in clause 5.30.2.9.2, only Network Specific Identifier based SUPI is supported. NOTE 3: When Credentials Holder is an SNPN, and the MCC and MNC of the SNPN is not unique (e.g. MCC =999 is used and MNC is not coordinated amongst the SNPNs), then IMSI based SUPI is not supported as the MCC and MNC need not be globally unique always; instead USIM credentials are supported using Network Specific Identifier based SUPI. NOTE 4: Network Specific Identifier are not supported for the case the Credentials Holder is provided by a PLMN. NOTE 5: It is assumed that normally the SNPN and the Credentials Holder use different PLMN ID. If the SNPN and CHs (where CH can be another SNPN or a PLMN) share PLMN ID, and IMSI based SUPI is used, then the Routing Indicator can be used for AUSF/UDM discovery and selection as long as the Routing Indicator values are coordinated among the involved SNPN and CHs. When the PLMN ID is not shared between SNPNs and CHs (where CH can be another SNPN or a PLMN) and IMSI based SUPI is used, then PLMN ID is sufficient to be used for AUSF/UDM discovery & selection unless the CHs deploys multiple AUSF/UDM in which case also the Routing Indicator can be used as long as the Routing Indicator values are coordinated within the CH. An SNPN-enabled UE that supports access to an SNPN using credentials from a Credentials Holder and that is equipped with a PLMN subscription may additionally be configured with the following information for SNPN selection and registration using the PLMN subscription in SNPN access mode: - User controlled prioritized list of preferred SNPNs; - Credentials Holder controlled prioritized list of preferred SNPNs; - Credentials Holder controlled prioritized list of preferred GINs. - Optionally if the UE supports access to an SNPN providing access for Localized Services: - Credentials Holder controlled prioritized list of preferred SNPNs for accessing Localized Services, each entry of the list includes: - an SNPN identifier; - validity information; and - optionally, location assistance information; - Credentials Holder controlled prioritized list of preferred GINs for accessing Localized Services, each entry of the list includes: - a GIN; - validity information; and - optionally, location assistance information. Validity information consists of: - Time validity information, i.e. time periods (defined by start and end times) when access to the SNPN for accessing Localized Services is allowed; and/or, Location assistance information consisting of: - Geolocation information, and/or, - Tracking Area information of serving networks, i.e. lists of TACs per PLMN ID or per PLMN ID and NID. The UE may use the location assistance information to determine where to search for the SNPNs in the Credentials Holder controlled prioritized list of SNPNs and GINs for accessing Localized Services, i.e. the location assistance information is not used for any area restriction enforcement. For an SNPN-enabled UE with PLMN subscription, the Credentials Holder controlled prioritized lists of preferred SNPNs and GINs, or the Credentials Holder controlled prioritized lists of preferred SNPNs and GINs for accessing Localized Services may be updated by the Credentials Holder using the Steering of Roaming (SoR) procedure as defined in Annex C of TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [17]. When the Credentials Holder updates a UE with the Credentials Holder controlled prioritized lists of preferred SNPNs and GINs, and/or the Credentials Holder controlled prioritized lists of preferred SNPNs and GINs for accessing Localized Services, the UE may perform SNPN selection again, e.g. to potentially select a higher prioritized SNPN or to potentially select an SNPN that provides access for Localized Services. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.30.2.3 |
6,531 | β PDCCH-Config | The IE PDCCH-Config is used to configure UE specific PDCCH parameters or MBS multicast PDCCH parameters such as control resource sets (CORESET), search spaces and additional parameters for acquiring the PDCCH. If this IE is used for the scheduled SCell in case of cross carrier scheduling, the fields other than searchSpacesToAddModList and searchSpacesToReleaseList are absent. If the IE is used for a dormant BWP, the fields other than controlResourceSetToAddModList and controlResourceSetToReleaseList are absent. If this IE is used for MBS CFR, the field downlinkPreemptiom,tpc-PUSCH, tpc-SRS, uplinkCancellation, monitoringCapabilityConfig, and searchSpaceSwitchConfig are absent. PDCCH-Config information element -- ASN1START -- TAG-PDCCH-CONFIG-START PDCCH-Config ::= SEQUENCE { controlResourceSetToAddModList SEQUENCE(SIZE (1..3)) OF ControlResourceSet OPTIONAL, -- Need N controlResourceSetToReleaseList SEQUENCE(SIZE (1..3)) OF ControlResourceSetId OPTIONAL, -- Need N searchSpacesToAddModList SEQUENCE(SIZE (1..10)) OF SearchSpace OPTIONAL, -- Need N searchSpacesToReleaseList SEQUENCE(SIZE (1..10)) OF SearchSpaceId OPTIONAL, -- Need N downlinkPreemption SetupRelease { DownlinkPreemption } OPTIONAL, -- Need M tpc-PUSCH SetupRelease { PUSCH-TPC-CommandConfig } OPTIONAL, -- Need M tpc-PUCCH SetupRelease { PUCCH-TPC-CommandConfig } OPTIONAL, -- Need M tpc-SRS SetupRelease { SRS-TPC-CommandConfig} OPTIONAL, -- Need M ..., [[ controlResourceSetToAddModListSizeExt-v1610 SEQUENCE (SIZE (1..2)) OF ControlResourceSet OPTIONAL, -- Need N controlResourceSetToReleaseListSizeExt-r16 SEQUENCE (SIZE (1..5)) OF ControlResourceSetId-r16 OPTIONAL, -- Need N searchSpacesToAddModListExt-r16 SEQUENCE(SIZE (1..10)) OF SearchSpaceExt-r16 OPTIONAL, -- Need N uplinkCancellation-r16 SetupRelease { UplinkCancellation-r16 } OPTIONAL, -- Need M monitoringCapabilityConfig-r16 ENUMERATED { r15monitoringcapability,r16monitoringcapability } OPTIONAL, -- Need M searchSpaceSwitchConfig-r16 SearchSpaceSwitchConfig-r16 OPTIONAL -- Need R ]], [[ searchSpacesToAddModListExt-v1700 SEQUENCE(SIZE (1..10)) OF SearchSpaceExt-v1700 OPTIONAL, -- Need N monitoringCapabilityConfig-v1710 ENUMERATED { r17monitoringcapability } OPTIONAL, -- Need M searchSpaceSwitchConfig-r17 SearchSpaceSwitchConfig-r17 OPTIONAL, -- Need R pdcch-SkippingDurationList-r17 SEQUENCE(SIZE (1..3)) OF SCS-SpecificDuration-r17 OPTIONAL -- Need R ]], [[ pdcch-MonitoringResumptionAfterNack-r18 ENUMERATED {true} OPTIONAL, -- Need R searchSpacesToAddModListExt-v1800 SEQUENCE(SIZE (1..10)) OF SearchSpaceExt-v1800 OPTIONAL -- Need N ]] } SearchSpaceSwitchConfig-r16 ::= SEQUENCE { cellGroupsForSwitchList-r16 SEQUENCE(SIZE (1..4)) OF CellGroupForSwitch-r16 OPTIONAL, -- Need R searchSpaceSwitchDelay-r16 INTEGER (10..52) OPTIONAL -- Need R } SearchSpaceSwitchConfig-r17 ::= SEQUENCE { searchSpaceSwitchTimer-r17 SCS-SpecificDuration-r17 OPTIONAL, -- Need R searchSpaceSwitchDelay-r17 INTEGER (10..52) OPTIONAL -- Need R } CellGroupForSwitch-r16 ::= SEQUENCE(SIZE (1..16)) OF ServCellIndex SCS-SpecificDuration-r17 ::= INTEGER (1..166) -- TAG-PDCCH-CONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | β |
6,532 | 6.2.4F UE maximum output power with additional requirements for category NB1 and NB2 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 are specified. For the agreed E-UTRA bands for category NB1 and NB2 UE an A-MPR of 0 dB shall be allowed unless specified otherwise. For UE Power Class 3 and 5 the specific requirements and identified subclauses are specified in Table 6.2.4F-1 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.4F-1 are in addition to the allowed MPR requirements specified in subclause 6.2.3F-1. Table 6.2.4F-1: Additional Maximum Power Reduction (A-MPR) for category NB1 and NB2 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.4F |
6,533 | D.6 Support for session/service continuity between SNPN and PLMN when using N3IWF | Depending on the UE's radio capability and implementation, the following existing mechanisms can be used to allow session/service continuity between SNPN and PLMN: - For Single Radio UE which includes single Rx/Tx and dual Rx/single Tx UE, seamless service continuity is not supported in this release when the UE is moving between the 3GPP access networks of SNPN and PLMN because of the single radio limitation. But the PDU session continuity between SNPN and PLMN can be realized by utilizing the existing handover procedure between non-3GPP access and 3GPP access as defined in clause 4.9.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3], where one network is acting as non-3GPP access of the other network. - For Dual Radio (Dual Rx/Dual Tx) UE, the service continuity can be achieved by utilizing the existing handover procedure between non-3GPP access and 3GPP access for PDU session on a single access and the existing user plane resource addition procedure for MA PDU session, where one network is acting as non-3GPP access of the other network - For PDU session on a single access, UE can register to the same 5GC via both Uu and NWu interfaces from two networks when it is possible, by following the procedure defined in clause 4.2.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3] if the registration is via Uu, or in clause 4.12.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3] if the registration is via NWu. The registration via NWu utilizes the user plane which is established in another 5GC using another network's Uu interface. For example, if UE is moving out of its SNPN 3GPP access coverage and would like to continue its SNPN service in PLMN, UE can register to its SNPN 5GC via PLMN's 3GPP access network using NWu interface with SNPN's 5GC before moving out SNPN NG-RAN coverage. Upon mobility, the existing handover procedure between non-3GPP access and 3GPP access defined in clause 4.9.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3] can be utilized. - For MA PDU session, if supported by UE and network, UE can register to the same 5GC via Uu and NWu interfaces and establish MA PDU session with ATSSS support to be anchored in the 5GC as defined in clause 4.22.2.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3], where one network is acting as non-3GPP access of the other network (Figure D.6-1 shows the example of UE with MA PDU session anchored in SNPN UPF when connected to SNPN via Uu and NWu interfaces). Upon mobility, UE can add/activate the user plane resource to the corresponding access type basing on the procedures defined in clause 4.22.7 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. Figure D.6-1: MA PDU session with ATSSS support for dual radio UE accessing to Stand-alone Non-Public Network services via Uu and NWu interfaces | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | D.6 |
6,534 | 2.2 Composition of IMSI | IMSI is composed as shown in figure 1. Figure 1: Structure of IMSI IMSI is composed of three parts: 1) Mobile Country Code (MCC) consisting of three digits. The MCC identifies uniquely the country of domicile of the mobile subscription; 2) Mobile Network Code (MNC) consisting of two or three digits for 3GPP network applications. The MNC identifies the home PLMN of the mobile subscription within its country of domicile, or it identifies together with MCC and NID the mobile subscription's SNPN. The length of the MNC (two or three digits) depends on the value of the MCC. A mixture of two and three digit MNC codes within a single MCC area is not recommended and is outside the scope of this specification. 3) Mobile Subscriber Identification Number (MSIN) identifying the mobile subscription within a PLMN or SNPN. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 2.2 |
6,535 | 5.5.1.2.5 Initial registration not accepted by the network | If the initial registration request cannot be accepted by the network, the AMF shall send a REGISTRATION REJECT message to the UE including an appropriate 5GMM cause value. If the initial registration request is rejected due to general NAS level mobility management congestion control, the network shall set the 5GMM cause value to #22 "congestion" and assign a value for back-off timer T3346. In NB-N1 mode, if the registration request is rejected due to operator determined barring (see 3GPP TS 29.503[ 5G System; Unified Data Management Services; Stage 3 ] [20AB]), the network shall set the 5GMM cause value to #22 "congestion" and assign a value for back-off timer T3346. If the REGISTRATION REJECT message with 5GMM cause #76 or #78 was received without integrity protection, then the UE shall discard the message. If the REGISTRATION REJECT message with 5GMM cause #62 was received without integrity protected, the behaviour of the UE is specified in subclause 5.3.20.2. Based on operator policy, if the initial registration request is rejected due to core network redirection for CIoT optimizations, the network shall set the 5GMM cause value to #31 "Redirection to EPC required". NOTE 1: The network can take into account the UE's S1 mode capability, the EPS CIoT network behaviour supported by the UE or the EPS CIoT network behaviour supported by the EPC to determine the rejection with the 5GMM cause value #31 "Redirection to EPC required". If the initial registration request is rejected because: a) all the S-NSSAI(s) included in the requested NSSAI are rejected; and b) the UE set the NSSAA bit in the 5GMM capability IE to: 1) "Network slice-specific authentication and authorization supported" and: i) void; ii) all default S-NSSAIs are not allowed; or iii) network slice-specific authentication and authorization has failed or been revoked for all default S-NSSAIs and based on network local policy, the network decides not to initiate the network slice-specific re-authentication and re-authorization procedures for any default S-NSSAI requested by the UE; or 2) "Network slice-specific authentication and authorization not supported" and all default S-NSSAIs are either not allowed or are subject to network slice-specific authentication and authorization; i) void ii) void the network shall set the 5GMM cause value of the REGISTRATION REJECT message to #62 "No network slices available". If the 5GMM cause value is set to #62 "No network slices available", the network shall include, in the rejected NSSAI of the REGISTRATION REJECT message, all the S-NSSAI(s) which were included in the requested NSSAI. If the UE has set the ER-NSSAI bit to "Extended rejected NSSAI supported" in the 5GMM capability IE of the REGISTRATION REQUEST message, the rejected S-NSSAI(s) shall be included in the Extended rejected NSSAI IE of the REGISTRATION REJECT message. Otherwise, the rejected S-NSSAI(s) shall be included in the Rejected NSSAI IE of the REGISTRATION REJECT message. In roaming scenarios, if the Extended rejected NSSAI IE is included in the REGISTRATION REJECT message, the AMF shall provide mapped S-NSSAI(s) for the rejected NSSAI. If the UE supports extended rejected NSSAI and the AMF determines that maximum number of UEs reached for one or more S-NSSAIs in the requested NSSAI as specified in subclause 4.6.2.5, the AMF shall include the rejected NSSAI containing one or more S-NSSAIs with the rejection cause "S-NSSAI not available due to maximum number of UEs reached" in the Extended rejected NSSAI IE in the REGISTRATION REJECT message. In addition, the AMF may include a back-off timer value for each S-NSSAI with the rejection cause "S-NSSAI not available due to maximum number of UEs reached" in the Extended rejected NSSAI IE of the REGISTRATION REJECT message. If the AMF receives the initial registration request along with the authenticated indication over N2 reference point on non-3GPP access and does not receive the indication that authentication by the home network is not required over N12 reference point, the network shall set the 5GMM cause value to #72 "Non-3GPP access to 5GCN not allowed". If the initial registration request from a UE supporting CAG is rejected due to CAG restrictions, the network shall set the 5GMM cause value to #76 "Not authorized for this CAG or authorized for CAG cells only" and should include the "CAG information list" in the CAG information list IE or the Extended CAG information list IE in the REGISTRATION REJECT message. NOTE 2: The network cannot be certain that "CAG information list" stored in the UE is updated as result of sending of the REGISTRATION REJECT message with the CAG information list IE or the Extended CAG information list IE, as the REGISTRATION REJECT message is not necessarily delivered to the UE (e.g. due to abnormal radio conditions). NOTE 3: The "CAG information list" can be provided by the AMF and include no entry if no "CAG information list" exists in the subscription. NOTE 4: If the UE supports extended CAG information list, the CAG information list can be included either in the CAG information list IE or Extended CAG information list IE. NOTE 4A: It is unexpected for network to send REGISTRATION REJECT message to the UE with 5GMM cause value #76 in non-CAG cell and not indicate "Indication that the UE is only allowed to access 5GS via CAG cells" for the serving PLMN in the Extended CAG information list or the CAG information list. If the UE does not support extended CAG information list, the CAG information list shall not be included in the Extended CAG information list IE. If the initial registration request from a UE not supporting CAG is rejected due to CAG restrictions, the network shall operate as described in bullet j) of subclause 5.5.1.2.8. If the UE's initial registration request is via a satellite NG-RAN cell and the network using the User Location Information provided by the NG-RAN, see 3GPP TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [31], is able to determine that the UE is in a location where the network is not allowed to operate, the network shall set the 5GMM cause value in the REGISTRATION REJECT message to #78 "PLMN not allowed to operate at the present UE location". NOTE 5: When the UE is accessing network for emergency services, it is up to operator and regulatory policies whether the network needs to determine if the UE is in a location where network is not allowed to operate. If the AMF receives the initial registration request including the service-level device ID set to the CAA-level UAV ID in the Service-level-AA container IE and the AMF determines that the UE is not allowed to use UAS services via 5GS based on the user's subscription data and the operator policy, the AMF shall return a REGISTRATION REJECT message with 5GMM cause #79 βUAS services not allowedβ. If the UE initiates the registration procedure for disaster roaming services and the AMF determines that it does not support providing disaster roaming services for the determined PLMN with disaster condition to the UE, then the AMF shall send a REGISTRATION REJECT message with 5GMM cause #80 βDisaster roaming for the determined PLMN with disaster condition not allowedβ. If the AMF receives the initial registration request over non-3GPP access and detects that the N3IWF used by the UE is not compatible with the allowed NSSAI and the UE has indicated its support for slice-based N3IWF selection in the REGISTRATION REQUEST message, the AMF may send a REGISTRATION REJECT message with 5GMM cause #81 βSelected N3IWF is not compatible with the allowed NSSAIβ and may provide information for a suitable N3IWF in the REGISTRATION REJECT message indicating the suitable N3IWF that is compatible with the requested NSSAI. If the AMF receives the initial registration request over non-3GPP access and detects that the TNGF used by the UE is not compatible with the allowed NSSAI and the UE has indicated its support for slice-based TNGF selection in the REGISTRATION REQUEST message, the AMF may send a REGISTRATION REJECT message with 5GMM cause #82 βSelected TNGF is not compatible with the allowed NSSAIβ and may provide information for a suitable TNAN in the TNAN information IE in the REGISTRATION REJECT message indicating the suitable TNGF that is compatible with the requested NSSAI. If the AMF received multiple TAIs from the satellite NG-RAN as described in 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8], and determines that, by UE subscription and operator's preferences, all of the received TAIs are forbidden for roaming or for regional provision of service, the AMF shall include the TAI(s) in: a) the Forbidden TAI(s) for the list of "5GS forbidden tracking areas for roaming" IE; or b) the Forbidden TAI(s) for the list of "5GS forbidden tracking areas for regional provision of service" IE; or c) both; in the REGISTRATION REJECT message. Regardless of the 5GMM cause value received in the REGISTRATION REJECT message via satellite NG-RAN, - if the UE receives the Forbidden TAI(s) for the list of "5GS forbidden tracking areas for roaming" IE in the REGISTRATION REJECT message, the UE shall store the TAI(s) belonging to the serving PLMN or equivalent PLMN(s) and ignore the TAI(s) which do not belong to the serving PLMN or equivalent PLMN(s) included in the IE, if not already stored, into the list of "5GS forbidden tracking areas for roaming"; and - if the UE receives the Forbidden TAI(s) for the list of "5GS forbidden tracking areas for regional provision of service" IE in the REGISTRATION REJECT message, the UE shall store the TAI(s) belonging to the serving PLMN or equivalent PLMN(s) and ignore the TAI(s) which do not belong to the serving PLMN or equivalent PLMN(s) included in the IE, if not already stored, into the list of "5GS forbidden tracking areas for regional provision of service". Furthermore, the UE shall take the following actions depending on the 5GMM cause value received in the REGISTRATION REJECT message. #3 (Illegal UE); or #6 (Illegal ME). The UE shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2) and shall delete any 5G-GUTI, last visited registered TAI, TAI list and ngKSI. In case of PLMN, the UE shall consider the USIM as invalid for 5GS services until switching off, the UICC containing the USIM is removed or the timer T3245 expires as described in subclause 5.3.19A.1; In case of SNPN, if the UE is not performing initial registration for onboarding services in SNPN and the UE does not support access to an SNPN using credentials from a credentials holder and does not support equivalent SNPNs, the UE shall consider the selected entry of the "list of subscriber data" with the SNPN identity of the current SNPN as invalid until the UE is switched off, the entry is updated or the timer T3245 expires as described in subclause 5.3.19A.2. In case of SNPN, if the UE is not performing initial registration for onboarding services in SNPN and the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs, or both, the UE shall consider the selected entry of the "list of subscriber data" as invalid for 3GPP access until the UE is switched off, the entry is updated or the timer T3245 expires as described in subclause 5.3.19A.2. Additionally, if EAP based primary authentication and key agreement procedure using EAP-AKA' or 5G AKA based primary authentication and key agreement procedure was performed in the current SNPN, the UE shall consider the USIM as invalid for the current SNPN until switching off, the UICC containing the USIM is removed or the timer T3245 expires as described in subclause 5.3.19A.2. If the UE is not performing initial registration for onboarding services in SNPN, the UE shall delete the list of equivalent PLMNs (if any) or the list of equivalent SNPNs (if any), and enter the state 5GMM-DEREGISTERED.NO-SUPI. If the message has been successfully integrity checked by the NAS, then the UE shall: 1) set the counter for "SIM/USIM considered invalid for GPRS services" events and the counter for "USIM considered invalid for 5GS services over non-3GPP access" events in case of PLMN if the UE maintains these counters; or 2) set the counter for "the entry for the current SNPN considered invalid for 3GPP access" events and the counter for "the entry for the current SNPN considered invalid for non-3GPP access" events in case of SNPN if the UE maintains these counters; to a UE implementation-specific maximum value. If the message was received via 3GPP access and the UE is operating in single-registration mode, the UE shall handle the EMM parameters EMM state, EPS update status, 4G-GUTI, last visited registered TAI, TAI list and eKSI as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15] for the case when the EPS attach request procedure is rejected with the EMM cause with the same value. The USIM shall be considered as invalid also for non-EPS services until switching off, the UICC containing the USIM is removed or the timer T3245 expires as described in subclause 5.3.7a in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15]. If the message has been successfully integrity checked by the NAS and the UE maintains a counter for "SIM/USIM considered invalid for non-GPRS services", then the UE shall set this counter to a UE implementation-specific maximum value. If the UE is performing initial registration for onboarding services in SNPN, the UE shall reset the registration attempt counter, store the SNPN identity in the "permanently forbidden SNPNs" list for onboarding services, enter state 5GMM-DEREGISTERED.PLMN-SEARCH, and perform an SNPN selection or an SNPN selection for onboarding services according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]. If the message has been successfully integrity checked by the NAS, the UE shall set the SNPN-specific attempt counter for the current SNPN to the UE implementation-specific maximum value. If the message has been successfully integrity checked by the NAS and the UE also supports the registration procedure over the other access, the UE shall in addition handle 5GMM parameters and 5GMM state for this access, as described for this 5GMM cause value. #7 (5GS services not allowed). The UE shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2) and shall delete any 5G-GUTI, last visited registered TAI, TAI list and ngKSI. In case of PLMN, the UE shall consider the USIM as invalid for 5GS services until switching off, the UICC containing the USIM is removed or the timer T3245 expires as described in subclause 5.3.19A.1; In case of SNPN, if the UE is not performing initial registration for onboarding services in SNPN and the UE does not support access to an SNPN using credentials from a credentials holder and does not support equivalent SNPNs, the UE shall consider the selected entry of the "list of subscriber data" with the SNPN identity of the current SNPN as invalid for 5GS services until the UE is switched off, the entry is updated or the timer T3245 expires as described in subclause 5.3.19A.2. In case of SNPN, if the UE is not performing initial registration for onboarding services in SNPN and the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs, or both, the UE shall consider the selected entry of the "list of subscriber data" as invalid for 3GPP access until the UE is switched off, the entry is updated or the timer T3245 expires as described in subclause 5.3.19A.2. Additionally, if EAP based primary authentication and key agreement procedure using EAP-AKA' or 5G AKA based primary authentication and key agreement procedure was performed in the current SNPN, the UE shall consider the USIM as invalid for the current SNPN until switching off, the UICC containing the USIM is removed or the timer T3245 expires as described in subclause 5.3.19A.2. If the UE is not performing initial registration for onboarding services in SNPN, the UE shall enter the state 5GMM-DEREGISTERED.NO-SUPI. If the message has been successfully integrity checked by the NAS, then the UE shall: 1) set the counter for "SIM/USIM considered invalid for GPRS services" events and the counter for "USIM considered invalid for 5GS services over non-3GPP access" events in case of PLMN if the UE maintains these counters; or 2) set the counter for "the entry for the current SNPN considered invalid for 3GPP access" events and the counter for "the entry for the current SNPN considered invalid for non-3GPP access" events in case of SNPN if the UE maintains these counters; to a UE implementation-specific maximum value. If the message was received via 3GPP access and the UE is operating in single-registration mode, the UE shall handle the EMM parameters EMM state, EPS update status, 4G-GUTI, last visited registered TAI, TAI list and eKSI as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15] for the case when the EPS attach request procedure is rejected with the EMM cause with the same value. If the UE is performing initial registration for onboarding services in SNPN, the UE shall reset the registration attempt counter, store the SNPN identity in the "permanently forbidden SNPNs" list for onboarding services, enter state 5GMM-DEREGISTERED.PLMN-SEARCH, and perform an SNPN selection or an SNPN selection for onboarding services according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]. If the message has been successfully integrity checked by the NAS, the UE shall set the SNPN-specific attempt counter for the current SNPN to the UE implementation-specific maximum value. If the message has been successfully integrity checked by the NAS and the UE also supports the registration procedure over the other access, the UE shall in addition handle 5GMM parameters and 5GMM state for this access, as described for this 5GMM cause value. #10 (Implicitly de-registered). 5GMM cause #10 is only applicable when received from a wireline access network by the 5G-RG acting on behalf of the AUN3 device and indicates that there is no 5G-RG connected to the same wireline. 5GMM cause #10 received when the 5G-RG is not acting on behalf of the AUN3 or received from a 5G access network other than a wireline access network is considered as abnormal cases and the behaviour of the UE is specified in subclause 5.5.1.2.7. When received over wireline access network, the 5G-RG acting on behalf of the AUN3 device shall abort the initial registration procedure that was initiated on behalf of the AUN3 device. The 5G-RG shall set its 5GS update status to 5U2 NOT UPDATED (and shall store it according to subclause 5.1.3.2.2), shall delete its 5G-GUTI, last visited registered TAI, TAI list, ngKSI, and shall reset its registration attempt counter, and shall enter the state 5GMM-DEREGISTERED. #11 (PLMN not allowed). This cause value received from a cell belonging to an SNPN is considered as an abnormal case and the behaviour of the UE is specified in subclause 5.5.1.2.7. The UE shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2) and shall delete any 5G-GUTI, last visited registered TAI, TAI list and ngKSI. The UE shall delete the list of equivalent PLMNs and reset the registration attempt counter and store the PLMN identity in the forbidden PLMN list as specified in subclause 5.3.13A and if the UE is configured to use timer T3245 then the UE shall start timer T3245 and proceed as described in subclause 5.3.19A.1. For 3GPP access the UE shall enter state 5GMM-DEREGISTERED.PLMN-SEARCH and perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5], and for non-3GPP access the UE shall enter state 5GMM-DEREGISTERED.LIMITED-SERVICE and perform network selection as defined in 3GPP TS 24.502[ Access to the 3GPP 5G Core Network (5GCN) via non-3GPP access networks ] [18]. If the message has been successfully integrity checked by the NAS and the UE maintains the PLMN-specific attempt counter and the PLMN-specific attempt counter for non-3GPP access for that PLMN, the UE shall set the PLMN-specific attempt counter and the PLMN-specific attempt counter for non-3GPP access for that PLMN to the UE implementation-specific maximum value. If the message was received via 3GPP access and the UE is operating in single-registration mode, the UE shall in addition handle the EMM parameters EMM state, EPS update status, 4G-GUTI, last visited registered TAI, TAI list, eKSI and attach attempt counter as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15] for the case when the EPS attach request procedure is rejected with the EMM cause with the same value. If the message has been successfully integrity checked by the NAS and the UE also supports the registration procedure over the other access to the same PLMN, the UE shall in addition handle 5GMM parameters and 5GMM state for this access, as described for this 5GMM cause value. #12 (Tracking area not allowed). The UE shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2) and shall delete last visited registered TAI and TAI list. If the UE is not registering or has not registered to the same PLMN over both 3GPP access and non-3GPP access, the UE shall additionally delete 5G-GUTI and ngKSI. Additionally, the UE shall reset the registration attempt counter. If: 1) the UE is not operating in SNPN access operation mode and the Forbidden TAI(s) for the list of "5GS forbidden tracking areas for regional provision of service" IE is not included in the REGISTRATION REJECT message, the UE shall store the current TAI in the list of "5GS forbidden tracking areas for regional provision of service" and enter the state 5GMM-DEREGISTERED.LIMITED-SERVICE. If the REGISTRATION REJECT message is not integrity protected, the UE shall memorize the current TAI was stored in the list of "5GS forbidden tracking areas for regional provision of service" for non-integrity protected NAS reject message; or 2) the UE is operating in SNPN access operation mode, the UE shall store the current TAI in the list of "5GS forbidden tracking areas for regional provision of service" for the current SNPN and the selected entry of the "list of subscriber data" or the selected PLMN subscription, and enter the state 5GMM-DEREGISTERED.LIMITED-SERVICE. If the REGISTRATION REJECT is not integrity protected, the UE shall memorize the current TAI was stored in the list of "5GS forbidden tracking areas for regional provision of service" for the current SNPN and the selected entry of the "list of subscriber data" or the selected PLMN subscription, for non-integrity protected NAS reject message. If the message was received via 3GPP access and the UE is operating in single-registration mode, the UE shall handle the EMM parameters EMM state, EPS update status, 4G-GUTI, last visited registered TAI, TAI list, eKSI and attach attempt counter as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15] for the case when the EPS attach request procedure is rejected with the EMM cause with the same value. #13 (Roaming not allowed in this tracking area). The UE shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2) and shall delete last visited registered TAI and TAI list. If the UE is not registering or has not registered to the same PLMN over both 3GPP access and non-3GPP access, the UE shall additionally delete 5G-GUTI, ngKSI and the list of equivalent PLMNs (if available) or the list of equivalent SNPNs (if available). Additionally, the UE shall reset the registration attempt counter. If: 1) the UE is not operating in SNPN access operation mode and the Forbidden TAI(s) for the list of "5GS forbidden tracking areas for roaming" IE is not included in the REGISTRATION REJECT message, the UE shall store the current TAI in the list of "5GS forbidden tracking areas for roaming" and enter the state 5GMM-DEREGISTERED.LIMITED-SERVICE or optionally 5GMM-DEREGISTERED.PLMN-SEARCH. If the REGISTRATION REJECT message is not integrity protected, the UE shall memorize the current TAI was stored in the list of "5GS forbidden tracking areas for roaming" for non-integrity protected NAS reject message; or 2) the UE is operating in SNPN access operation mode, the UE shall store the current TAI in the list of "5GS forbidden tracking areas for roaming" for the current SNPN and the selected entry of the "list of subscriber data" or the selected PLMN subscription, and enter the state 5GMM-DEREGISTERED.LIMITED-SERVICE or optionally 5GMM-DEREGISTERED.PLMN-SEARCH. If the REGISTRATION REJECT message is not integrity protected, the UE shall memorize the current TAI was stored in the list of "5GS forbidden tracking areas for roaming" for the current SNPN and the selected entry of the "list of subscriber data" or the selected PLMN subscription, for non-integrity protected NAS reject message. For 3GPP access, if the UE is registered in S1 mode and operating in dual-registration mode, the PLMN that the UE chooses to register in is specified in subclause 4.8.3. Otherwise the UE shall perform a PLMN selection or SNPN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]. For non-3GPP access, the UE shall perform network selection as defined in 3GPP TS 24.502[ Access to the 3GPP 5G Core Network (5GCN) via non-3GPP access networks ] [18]. If the message was received via 3GPP access and the UE is operating in single-registration mode, the UE shall handle the EMM parameters EMM state, EPS update status, 4G-GUTI, last visited registered TAI, TAI list, eKSI and attach attempt counter as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15] for the case when the EPS attach request procedure is rejected with the EMM cause with the same value. #15 (No suitable cells in tracking area). The UE shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2) and shall delete any last visited registered TAI and TAI list. If the UE is not registering or has not registered to the same PLMN over both 3GPP access and non-3GPP access, the UE shall additionally delete 5G-GUTI and ngKSI. Additionally, the UE shall reset the registration attempt counter. If: 1) the UE is not operating in SNPN access operation mode and the Forbidden TAI(s) for the list of "5GS forbidden tracking areas for roaming" IE is not included in the REGISTRATION REJECT message, the UE shall store the current TAI in the list of "5GS forbidden tracking areas for roaming" and enter the state 5GMM-DEREGISTERED.LIMITED-SERVICE. If the REGISTRATION REJECT message is not integrity protected, the UE shall memorize the current TAI was stored in the list of "5GS forbidden tracking areas for roaming" for non-integrity protected NAS reject message; or 2) the UE is operating in SNPN access operation mode, the UE shall store the current TAI in the list of "5GS forbidden tracking areas for roaming" for the current SNPN and the selected entry of the "list of subscriber data" or the selected PLMN subscription, and enter the state 5GMM-DEREGISTERED.LIMITED-SERVICE. If the REGISTRATION REJECT message is not integrity protected, the UE shall memorize the current TAI was stored in the list of "5GS forbidden tracking areas for roaming" for the current SNPN and the selected entry of the "list of subscriber data" or the selected PLMN subscription, for non-integrity protected NAS reject message. The UE shall search for a suitable cell in another tracking area according to 3GPP TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [28] or 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [25C]. If the message was received via 3GPP access and the UE is operating in single-registration mode, the UE shall handle the EMM parameters EMM state, EPS update status, 4G-GUTI, last visited registered TAI, TAI list, eKSI and attach attempt counter as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15] for the case when the EPS attach request procedure is rejected with the EMM cause with the same value. If received over non-3GPP access the cause shall be considered as an abnormal case and the behaviour of the UE for this case is specified in subclause 5.5.1.2.7. #22 (Congestion). If the T3346 value IE is present in the REGISTRATION REJECT message and the value indicates that this timer is neither zero nor deactivated, the UE shall proceed as described below; otherwise it shall be considered as an abnormal case and the behaviour of the UE for this case is specified in subclause 5.5.1.2.7. The UE shall abort the initial registration procedure, set the 5GS update status to 5U2 NOT UPDATED, reset the registration attempt counter and enter state 5GMM-DEREGISTERED.ATTEMPTING-REGISTRATION. The UE shall stop timer T3346 if it is running. If the REGISTRATION REJECT message is integrity protected, the UE shall start timer T3346 with the value provided in the T3346 value IE. If the REGISTRATION REJECT message is not integrity protected, the UE shall start timer T3346 with a random value from the default range specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [12]. The UE stays in the current serving cell and applies the normal cell reselection process. The initial registration procedure is started if still needed when timer T3346 expires or is stopped. If the message was received via 3GPP access and the UE is operating in single-registration mode, the UE shall handle the EMM parameters EMM state, EPS update status, and attach attempt counter as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15] for the case when the EPS attach request procedure is rejected with the EMM cause with the same value. If the UE is registering for onboarding services in SNPN, the UE may enter the state 5GMM-DEREGISTERED.PLMN-SEARCH and perform an SNPN selection or an SNPN selection for onboarding services according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]. #27 (N1 mode not allowed). The UE shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2) and shall delete any 5G-GUTI, last visited registered TAI, TAI list and ngKSI. Additionally, the UE shall reset the registration attempt counter and shall enter the state 5GMM-DEREGISTERED.LIMITED-SERVICE. If the message has been successfully integrity checked by the NAS, the UE shall set: 1) the PLMN-specific N1 mode attempt counter for 3GPP access and the PLMN-specific N1 mode attempt counter for non-3GPP access for that PLMN in case of PLMN; or 2) the SNPN-specific attempt counter for 3GPP access for the current SNPN in case of SNPN and the SNPN-specific attempt counter for non-3GPP access for the current SNPN; to the UE implementation-specific maximum value. The UE shall disable the N1 mode capability for the specific access type for which the message was received (see subclause 4.9). If the message has been successfully integrity checked by the NAS, the UE shall disable the N1 mode capability also for the other access type (see subclause 4.9). If the message was received via 3GPP access and the UE is operating in single-registration mode, the UE shall in addition set the EPS update status to EU3 ROAMING NOT ALLOWED and shall delete any 4G-GUTI, last visited registered TAI, TAI list and eKSI. Additionally, the UE shall reset the attach attempt counter and enter the state EMM-DEREGISTERED. #31 (Redirection to EPC required). 5GMM cause #31 received by a UE that has not indicated support for CIoT optimizations or not indicated support for S1 mode or received by a UE over non-3GPP access is considered as an abnormal case and the behaviour of the UE is specified in subclause 5.5.1.2.7. This cause value received from a cell belonging to an SNPN is considered as an abnormal case and the behaviour of the UE is specified in subclause 5.5.1.2.7. The UE shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2) and shall delete any 5G-GUTI, last visited registered TAI, TAI list and ngKSI. Additionally, the UE shall reset the registration attempt counter. The UE shall enable the E-UTRA capability if it was disabled, disable the N1 mode capability for 3GPP access (see subclause 4.9.2) and enter the 5GMM-DEREGISTERED.NO-CELL-AVAILABLE. If the message was received via 3GPP access and the UE is operating in single-registration mode, the UE shall handle the EMM parameters EMM state, EPS update status, 4G-GUTI, TAI list, eKSI and attach attempt counter as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15] for the case when the EPS attach procedure is rejected with the EMM cause with the same value. #36 (IAB-node operation not authorized). This cause value is only applicable when received over 3GPP access by a UE operating as an IAB-node. This cause value received from a 5G access network other than 3GPP access or received by a UE not operating as an IAB-node is considered as an abnormal case and the behaviour of the UE is specified in subclause 5.5.1.2.7. The UE shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2) and shall delete any 5G-GUTI, last visited registered TAI, TAI list and ngKSI. If: 1) the UE is not operating in SNPN access operation mode, i) the UE shall delete the list of equivalent PLMNs and reset the registration attempt counter and store the PLMN identity in the forbidden PLMN list as specified in subclause 5.3.13A and if the UE is configured to use timer T3245 then the UE shall start timer T3245 and proceed as described in subclause 5.3.19a.1. The UE shall enter state 5GMM-DEREGISTERED.PLMN-SEARCH and perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]. If the message has been successfully integrity checked by the NAS and the UE maintains the PLMN-specific attempt counter for 3GPP access for that PLMN, the UE shall set the PLMN-specific attempt counter for 3GPP access for that PLMN to the UE implementation-specific maximum value; and ii) If the UE is operating in single-registration mode, the UE shall in addition handle the EMM parameters EMM state, EPS update status, 4G-GUTI, last visited registered TAI, TAI list, eKSI and attach attempt counter as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15] for the case when the EPS attach request procedure is rejected with the EMM cause with the same value; or 2) the UE is operating in SNPN access operation mode, i) the UE shall delete the list of equivalent SNPNs (if available). The UE shall reset the registration attempt counter and store the SNPN identity in the "temporarily forbidden SNPNs" list for 3GPP access and, if the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, the selected entry of the "list of subscriber data" or the selected PLMN subscription. The UE shall enter state 5GMM-DEREGISTERED.PLMN-SEARCH and perform an SNPN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]. If the message has been successfully integrity checked by the NAS, the UE shall set the SNPN attempt counter for 3GPP access for the current SNPN to the UE implementation-specific maximum value.#62 (No network slices available). The UE shall abort the initial registration procedure, set the 5GS update status to 5U2 NOT UPDATED and enter state 5GMM-DEREGISTERED. ATTEMPTING-REGISTRATION or 5GMM-DEREGISTERED.PLMN-SEARCH. Additionally, the UE shall reset the registration attempt counter. The UE receiving the rejected NSSAI in the REGISTRATION REJECT message takes the following actions based on the rejection cause in the rejected S-NSSAI(s): "S-NSSAI not available in the current PLMN or SNPN" The UE shall store the rejected S-NSSAI(s) in the rejected NSSAI for the current PLMN or SNPN as specified in subclause 4.6.2.2 and shall not attempt to use this S-NSSAI(s) in the current PLMN or SNPN over any access until switching off the UE, the UICC containing the USIM is removed, an entry of the "list of subscriber data" with the SNPN identity of the current SNPN is updated, or the rejected S-NSSAI(s) are removed as described in subclause 4.6.2.2. "S-NSSAI not available in the current registration area" The UE shall store the rejected S-NSSAI(s) in the rejected NSSAI for the current registration area as described in subclause 4.6.2.2 and shall not attempt to use this S-NSSAI(s) in the current registration area over the current access until switching off the UE, the UE moving out of the current registration area, the UICC containing the USIM is removed, the entry of the "list of subscriber data" with the SNPN identity of the current SNPN is updated, or the rejected S-NSSAI(s) are removed as described in subclause 4.6.2.2. "S-NSSAI not available due to the failed or revoked network slice-specific authentication and authorization" The UE shall store the rejected S-NSSAI(s) in the rejected NSSAI for the failed or revoked NSSAA as specified in subclause 4.6.2.2 and shall not attempt to use this S-NSSAI in the current PLMN or SNPN over any access until switching off the UE, the UICC containing the USIM is removed, the entry of the "list of subscriber data" with the SNPN identity of the current SNPN is updated, or the rejected S-NSSAI(s) are removed as described in subclause 4.6.1 and 4.6.2.2. "S-NSSAI not available due to maximum number of UEs reached" Unless the back-off timer value received along with the S-NSSAI is zero, the UE shall add the rejected S-NSSAI(s) in the rejected NSSAI for the maximum number of UEs reached as specified in subclause 4.6.2.2 and shall not attempt to use this S-NSSAI in the current PLMN or SNPN over the current access until switching off the UE, the UICC containing the USIM is removed, the entry of the "list of subscriber data" with the SNPN identity of the current SNPN is updated, or the rejected S-NSSAI(s) are removed as described in subclauses 4.6.1 and 4.6.2.2. NOTE 6: If the back-off timer value received along with the S-NSSAI in the rejected NSSAI for the maximum number of UEs reached is zero as specified in subclause 10.5.7.4a of 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [12], the UE does not consider the S-NSSAI as the rejected S-NSSAI. If there is one or more S-NSSAIs in the rejected NSSAI with the rejection cause "S-NSSAI not available due to maximum number of UEs reached", then for each S-NSSAI, the UE shall behave as follows: a) stop the timer T3526 associated with the S-NSSAI, if running; b) start the timer T3526 with: 1) the back-off timer value received along with the S-NSSAI, if a back-off timer value is received along with the S-NSSAI that is neither zero nor deactivated; or 2) an implementation specific back-off timer value, if no back-off timer value is received along with the S-NSSAI; and c) remove the S-NSSAI from the rejected NSSAI for the maximum number of UEs reached when the timer T3526 associated with the S-NSSAI expires. If the UE has an allowed NSSAI or configured NSSAI and: 1) at least one S-NSSAI of the allowed NSSAI or configured NSSAI is not included in the rejected NSSAI the UE may stay in the current serving cell, apply the normal cell reselection process and start an initial registration with a requested NSSAI that includes any S-NSSAI from the allowed NSSAI or the configured NSSAI that is not in the rejected NSSAI. 2) all the S-NSSAI(s) in the allowed NSSAI and configured NSSAI are rejected and at least one S-NSSAI is rejected due to "S-NSSAI not available in the current registration area" and: i) the REGISTRATION REJECT message is integrity protected, the UE is not operating in SNPN access operation mode and the Forbidden TAI(s) for the list of "5GS forbidden tracking areas for roaming" IE is not included in the REGISTRATION REJECT message, then the UE shall store the current TAI in the list of "5GS forbidden tracking areas for roaming", memorize the current TAI was stored in the list of "5GS forbidden tracking areas for roaming" for S-NSSAI is rejected due to "S-NSSAI not available in the current registration area" and enter the state 5GMM-DEREGISTERED.LIMITED-SERVICE. The UE shall search for a suitable cell in another tracking area according to 3GPP TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [28] or 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [25C]; or ii) the REGISTRATION REJECT message is integrity protected and the UE is operating in SNPN access operation mode, then the UE shall store the current TAI in the list of "5GS forbidden tracking areas for roaming", memorize the current TAI was stored in the list of "5GS forbidden tracking areas for roaming" for S-NSSAI is rejected due to "S-NSSAI not available in the current registration area" for the current SNPN and, if the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, the selected entry of the "list of subscriber data" or the selected PLMN subscription, and enter the state 5GMM-DEREGISTERED.LIMITED-SERVICE. The UE shall search for a suitable cell in another tracking area according to 3GPP TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [28] or 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [25C]. 3) otherwise,the UE may perform a PLMN selection or SNPN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5] and additionally, the UE may disable the N1 mode capability for the current PLMN or SNPN if the UE does not have an allowed NSSAI and each S-NSSAI in configured NSSAI, if available, was rejected with cause "S-NSSAI not available in the current PLMN or SNPN" or "S-NSSAI not available due to the failed or revoked network slice-specific authentication and authorization" as described in subclause 4.9. If the UE has neither allowed NSSAI for the current PLMN or SNPN nor configured NSSAI for the current PLMN or SNPN and, 1) if at least one S-NSSAI in the default configured NSSAI is not rejected, the UE may stay in the current serving cell, apply the normal cell reselection process, and start an initial registration with a requested NSSAI with that default configured NSSAI; or 2) if all the S-NSSAI(s) in the default configured NSSAI are rejected and at least one S-NSSAI is rejected due to "S-NSSAI not available in the current registration area", i) if the REGISTRATION REJECT message is integrity protected and the UE is not operating in SNPN access operation mode, the UE shall store the current TAI in the list of "5GS forbidden tracking areas for roaming" and enter the state 5GMM-DEREGISTERED.LIMITED-SERVICE. The UE shall search for a suitable cell in another tracking area according to 3GPP TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [28] or 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [25C]; or ii) if the REGISTRATION REJECT message is integrity protected and the UE is operating in SNPN access operation mode, the UE shall store the current TAI in the list of "5GS forbidden tracking areas for roaming" for the current SNPN and, if the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, the selected entry of the "list of subscriber data" or the selected PLMN subscription, and enter the state 5GMM-DEREGISTERED.LIMITED-SERVICE. The UE shall search for a suitable cell in another tracking area according to 3GPP TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [28] or 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [25C]. 3) otherwise, the UE may perform a PLMN selection or SNPN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5] and additionally, the UE may disable the N1 mode capability for the current PLMN or SNPN if each S-NSSAI in the default configured NSSAI was rejected with cause "S-NSSAI not available in the current PLMN or SNPN" or "S-NSSAI not available due to the failed or revoked network slice-specific authentication and authorization" as described in subclause 4.9. If 1) the UE has allowed NSSAI for the current PLMN or SNPN or configured NSSAI for the current PLMN or SNPN or both and all the S-NSSAIs included in the allowed NSSAI or the configured NSSAI or both are rejected; or 2) the UE has neither allowed NSSAI for the current PLMN or SNPN nor configured NSSAI for the current PLMN or SNPN and all the S-NSSAIs included in the default configured NSSAI are rejected, and the UE has rejected NSSAI for the maximum number of UEs reached, and the UE wants to obtain services in the current serving cell without performing a PLMN selection or SNPN selection, the UE may stay in the current serving cell and attempt to use the rejected S-NSSAI(s) for the maximum number of UEs reached in the current serving cell after the rejected S-NSSAI(s) are removed as described in subclause 4.6.2.2. If the message was received via 3GPP access and the UE is operating in single-registration mode, the UE shall in addition set the EPS update status to EU2 NOT UPDATED, reset the attach attempt counter and enter the state EMM-DEREGISTERED. #72 (Non-3GPP access to 5GCN not allowed). When received over non-3GPP access the UE shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2) and shall delete last visited registered TAI and TAI list. If the UE is not registering or has not registered to the same PLMN over 3GPP access, the UE shall additionally delete 5G-GUTI and ngKSI. Additionally, the UE shall reset the registration attempt counter and enter the state 5GMM-DEREGISTERED. If the message has been successfully integrity checked by the NAS, the UE shall set: 1) the PLMN-specific N1 mode attempt counter for non-3GPP access for that PLMN in case of PLMN: or 2) the SNPN-specific attempt counter for non-3GPP access for that SNPN in case of SNPN; to the UE implementation-specific maximum value. NOTE 7: The 5GMM sublayer states, the 5GMM parameters and the registration status are managed per access type independently, i.e. 3GPP access or non-3GPP access (see subclauses 4.7.2 and 5.1.3). The UE shall disable the N1 mode capability for non-3GPP access (see subclause 4.9.3). As an implementation option, the UE may enter the state 5GMM-DEREGISTERED.PLMN-SEARCH in order to perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]. If received over 3GPP access the cause shall be considered as an abnormal case and the behaviour of the UE for this case is specified in subclause 5.5.1.2.7. #73 (Serving network not authorized). This cause value received from a cell belonging to an SNPN is considered as an abnormal case and the behaviour of the UE is specified in subclause 5.5.1.2.7. The UE shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2) and shall delete any 5G-GUTI, last visited registered TAI, TAI list and ngKSI. The UE shall delete the list of equivalent PLMNs, reset the registration attempt counter, store the PLMN identity in the forbidden PLMN list as specified in subclause 5.3.13A. For 3GPP access the UE shall enter state 5GMM-DEREGISTERED.PLMN-SEARCH in order to perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5], and for non-3GPP access the UE shall enter state 5GMM-DEREGISTERED.LIMITED-SERVICE and perform network selection as defined in 3GPP TS 24.502[ Access to the 3GPP 5G Core Network (5GCN) via non-3GPP access networks ] [18]. If the message has been successfully integrity checked by the NAS, the UE shall set the PLMN-specific attempt counter and the PLMN-specific attempt counter for non-3GPP access for that PLMN to the UE implementation-specific maximum value. If the message was received via 3GPP access and the UE is operating in single-registration mode, the UE shall in addition set the EPS update status to EU3 ROAMING NOT ALLOWED and shall delete any 4G-GUTI, last visited registered TAI, TAI list and eKSI. Additionally, the UE shall reset the attach attempt counter and enter the state EMM-DEREGISTERED. #74 (Temporarily not authorized for this SNPN). 5GMM cause #74 is only applicable when received from a cell belonging to an SNPN. 5GMM cause #74 received from a cell not belonging to an SNPN is considered as an abnormal case and the behaviour of the UE is specified in subclause 5.5.1.2.7. The UE shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2) and shall delete any 5G-GUTI, last visited registered TAI, TAI list, ngKSI and the list of equivalent SNPNs (if available). The UE shall reset the registration attempt counter and store the SNPN identity in the "temporarily forbidden SNPNs" list or "temporarily forbidden SNPNs for access for localized services in SNPN" list if the SNPN is an SNPN selected for localized services in SNPN as specified in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5] for the specific access type for which the message was received and the selected entry of the "list of subscriber data" or the selected PLMN subscription. If the UE supports access to an SNPN using credentials from a credentials holder, the UE shall store the SNPN identity in the "temporarily forbidden SNPNs" list along with the GIN(s) broadcasted by the SNPN if any, for the selected entry of the "list of subscriber data" or the selected PLMN subscription. If the UE supports access to an SNPN providing access for localized services in SNPN and the access for localized services in SNPN has been enabled, the UE shall store the SNPN identity in the list of "temporarily forbidden SNPNs for access for localized services in SNPN" (if the SNPN was selected according to subclause 4.9.3.1.1 bullet a0) of 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]) along with the GIN(s) broadcasted by the SNPN if any, for the selected entry of the "list of subscriber data" or the selected PLMN subscription. If the registration request is not for onboarding services in SNPN, for 3GPP access the UE shall enter state 5GMM-DEREGISTERED.PLMN-SEARCH and perform an SNPN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5] and for non-3GPP access the UE shall enter state 5GMM-DEREGISTERED.LIMITED-SERVICE and perform network selection as defined in 3GPP TS 24.502[ Access to the 3GPP 5G Core Network (5GCN) via non-3GPP access networks ] [18]. If the registration request is for onboarding services in SNPN, the UE shall enter state 5GMM-DEREGISTERED.PLMN-SEARCH and perform an SNPN selection or an SNPN selection for onboarding services according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]. If the message has been successfully integrity checked by the NAS, the UE shall set the SNPN-specific attempt counter for 3GPP access and the SNPN-specific attempt counter for non-3GPP access for the current SNPN to the UE implementation-specific maximum value. If the message has been successfully integrity checked by the NAS and the UE also supports the registration procedure over the other access to the same SNPN, the UE shall in addition handle 5GMM parameters and 5GMM state for this access, as described for this 5GMM cause value. #75 (Permanently not authorized for this SNPN). 5GMM cause #75 is only applicable when received from a cell belonging to an SNPN with a globally-unique SNPN identity. 5GMM cause #75 received from a cell not belonging to an SNPN or a cell belonging to an SNPN with a non-globally-unique SNPN identity is considered as an abnormal case and the behaviour of the UE is specified in subclause 5.5.1.2.7. The UE shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2) and shall delete any 5G-GUTI, last visited registered TAI, TAI list ngKSI and the list of equivalent SNPNs (if available). The UE shall reset the registration attempt counter and store the SNPN identity in the "permanently forbidden SNPNs" list or "permanently forbidden SNPNs for access for localized services in SNPN" list if the SNPN is an SNPN selected for localized services in SNPN as specified in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5] for the specific access type for which the message was received and the selected entry of the "list of subscriber data" or the selected PLMN subscription. If the UE supports access to an SNPN using credentials from a credentials holder, the UE shall store the SNPN identity in the "permanently forbidden SNPNs" list along with the GIN(s) broadcasted by the SNPN if any, for the selected entry of the "list of subscriber data" or the selected PLMN subscription. If the UE supports access to an SNPN providing access for localized services in SNPN and the access for localized services in SNPN has been enabled, the UE shall store the SNPN identity in the list of "permanently forbidden SNPNs for access for localized services in SNPN" (if the SNPN was selected according to subclause 4.9.3.1.1 bullet a0) of 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]) along with the GIN(s) broadcasted by the SNPN if any, for the selected entry of the "list of subscriber data" or the selected PLMN subscription. If the registration request is not for onboarding services in SNPN, for 3GPP access the UE shall enter state 5GMM-DEREGISTERED.PLMN-SEARCH and perform an SNPN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5] and for non-3GPP access the UE shall enter state 5GMM-DEREGISTERED.LIMITED-SERVICE and perform network selection as defined in 3GPP TS 24.502[ Access to the 3GPP 5G Core Network (5GCN) via non-3GPP access networks ] [18]. If the registration request is for onboarding services in SNPN, the UE shall enter state 5GMM-DEREGISTERED.PLMN-SEARCH and perform an SNPN selection or an SNPN selection for onboarding services according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]. If the message has been successfully integrity checked by the NAS, the UE shall set the SNPN-specific attempt counter for 3GPP access and the SNPN-specific attempt counter for non-3GPP access for the current SNPN to the UE implementation-specific maximum val If the message has been successfully integrity checked by the NAS and the UE also supports the registration procedure over the other access to the same SNPN, the UE shall in addition handle 5GMM parameters and 5GMM state for this access, as described for this 5GMM cause value. #76 (Not authorized for this CAG or authorized for CAG cells only). This cause value received via non-3GPP access or from a cell belonging to an SNPN is considered as an abnormal case and the behaviour of the UE is specified in subclause 5.5.1.2.7. The UE shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED, store the 5GS update status according to subclause 5.1.3.2.2, and reset the registration attempt counter. If 5GMM cause #76 is received from: 1) a CAG cell, and if the UE receives a "CAG information list" in the CAG information list IE or the Extended CAG information list IE included in the REGISTRATION REJECT message, the UE shall: i) replace the "CAG information list" stored in the UE with the received CAG information list IE or the Extended CAG information list IE when received in the HPLMN or EHPLMN; ii) replace the serving VPLMN's entry of the "CAG information list" stored in the UE with the serving VPLMN's entry of the received CAG information list IE or the Extended CAG information list IE when the UE receives the CAG information list IE or the Extended CAG information list IE in a serving PLMN other than the HPLMN or EHPLMN; or NOTE 8: When the UE receives the CAG information list IE or the Extended CAG information list IE in a serving PLMN other than the HPLMN or EHPLMN, entries of a PLMN other than the serving VPLMN, if any, in the received CAG information list IE or the Extended CAG information list IE are ignored. iii) remove the serving VPLMN's entry of the "CAG information list" stored in the UE when the UE receives the CAG information list IE or the Extended CAG information list IE in a serving PLMN other than the HPLMN or EHPLMN and the CAG information list IE or the Extended CAG information list IE does not contain the serving VPLMN's entry. Otherwise, then the UE shall delete the CAG-ID(s) of the cell from the "allowed CAG list" for the current PLMN, if the CAG-ID(s) are authorized based on the "allowed CAG list". In the case the "allowed CAG list" for the current PLMN only contains a range of CAG-IDs, how the UE deletes the CAG-ID(s) of the cell from the "allowed CAG list" for the current PLMN is up to UE implementation. In addition: i) if the entry in the "CAG information list" for the current PLMN does not include an "indication that the UE is only allowed to access 5GS via CAG cells" or if the entry in the "CAG information list" for the current PLMN includes an "indication that the UE is only allowed to access 5GS via CAG cells" and one or more CAG-ID(s) are authorized based on the updated "allowed CAG list" for the current PLMN, then the UE shall enter the state 5GMM-DEREGISTERED.LIMITED-SERVICE and shall search for a suitable cell according to 3GPP TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [28] or 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [25C] with the updated "CAG information list"; ii) if the entry in the "CAG information list" for the current PLMN includes an "indication that the UE is only allowed to access 5GS via CAG cells" and no CAG-ID is authorized based on the updated "allowed CAG list" for the current PLMN, then the UE shall enter the state 5GMM-DEREGISTERED.PLMN-SEARCH and shall apply the PLMN selection process defined in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5] with the updated "CAG information list"; or iii) if the "CAG information list" does not include an entry for the current PLMN, then the UE shall enter the state 5GMM-DEREGISTERED.LIMITED-SERVICE and shall search for a suitable cell according to 3GPP TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [28] or 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [25C] with the updated "CAG information list". 2) a non-CAG cell, and if the UE receives a "CAG information list" in the CAG information list IE or the Extended CAG information list IE included in the REGISTRATION REJECT message, the UE shall: i) replace the "CAG information list" stored in the UE with the received CAG information list IE or the Extended CAG information list IE when received in the HPLMN or EHPLMN; ii) replace the serving VPLMN's entry of the "CAG information list" stored in the UE with the serving VPLMN's entry of the received CAG information list IE or the Extended CAG information list IE when the UE receives the CAG information list IE or the Extended CAG information list IE in a serving PLMN other than the HPLMN or EHPLMN; or NOTE 9: When the UE receives the CAG information list IE or the Extended CAG information list IE in a serving PLMN other than the HPLMN or EHPLMN, entries of a PLMN other than the serving VPLMN, if any, in the received CAG information list IE or the Extended CAG information list IE are ignored. iii) remove the serving VPLMN's entry of the "CAG information list" stored in the UE when the UE receives the CAG information list IE or the Extended CAG information list IE in a serving PLMN other than the HPLMN or EHPLMN and the CAG information list IE or the Extended CAG information list IE does not contain the serving VPLMN's entry. Otherwise, the UE shall store an "indication that the UE is only allowed to access 5GS via CAG cells" in the entry of the "CAG information list" for the current PLMN, if any. If the "CAG information list" stored in the UE does not include the current PLMN's entry, the UE shall add an entry for the current PLMN to the "CAG information list" and store an "indication that the UE is only allowed to access 5GS via CAG cells" in the entry of the "CAG information list" for the current PLMN. If the UE does not have a stored "CAG information list", the UE shall create a new "CAG information list" and add an entry with an "indication that the UE is only allowed to access 5GS via CAG cells" for the current PLMN. In addition: i) if one or more CAG-ID(s) are authorized based on the "allowed CAG list" for the current PLMN, then the UE shall enter the state 5GMM-DEREGISTERED.LIMITED-SERVICE and shall search for a suitable cell according to 3GPP TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [28] with the updated CAG information; or ii) if no CAG-ID is authorized based on the "allowed CAG list" for the current PLMN, then the UE shall enter the state 5GMM-DEREGISTERED.PLMN-SEARCH and shall apply the PLMN selection process defined in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5] with the updated "CAG information list". If the message was received via 3GPP access and the UE is operating in single-registration mode, the UE shall in addition set the EPS update status to EU3 ROAMING NOT ALLOWED, reset the attach attempt counter and enter the state EMM-DEREGISTERED. #77 (Wireline access area not allowed). 5GMM cause #77 is only applicable when received from a wireline access network by the 5G-RG or the W-AGF acting on behalf of the FN-CRG. 5GMM cause #77 received from a 5G access network other than a wireline access network and 5GMM cause #77 received by the W-AGF acting on behalf of the FN-BRG are considered as abnormal cases and the behaviour of the UE is specified in subclause 5.5.1.2.7. When received over wireline access network, the 5G-RG and the W-AGF acting on behalf of the FN-CRG shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2), shall delete 5G-GUTI, last visited registered TAI, TAI list and ngKSI, shall reset the registration attempt counter, shall enter the state 5GMM-DEREGISTERED and shall act as specified in subclause 5.3.23. NOTE 10: The 5GMM sublayer states, the 5GMM parameters and the registration status are managed per access type independently, i.e. 3GPP access or non-3GPP access (see subclauses 4.7.2 and 5.1.3). #78 (PLMN not allowed to operate at the present UE location). This cause value received from a non-satellite NG-RAN cell is considered as an abnormal case and the behaviour of the UE is specified in subclause 5.5.1.2.7. The UE shall set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2) and shall delete last visited registered TAI and TAI list. If the UE is not registering or has not registered to the same PLMN over non-3GPP access, the UE shall additionally delete 5G-GUTI and ngKSI. Additionally, the UE shall reset the registration attempt counter. The UE shall store the PLMN identity and, if it is known, the current geographical location in the list of "PLMNs not allowed to operate at the present UE location" and shall start a corresponding timer instance (see subclause 4.23.2). The UE shall enter state 5GMM-DEREGISTERED.PLMN-SEARCH and perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]. If the message was received via 3GPP access and the UE is operating in single-registration mode, the UE shall handle the EMM parameters EMM state, EPS update status, 4G-GUTI, TAI list, eKSI and attach attempt counter as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15] for the case when the EPS attach procedure is rejected with the EMM cause with the same value. #79 (UAS services not allowed). The UE shall abort the initial registration procedure, set the 5GS update status to 5U2 NOT UPDATED and enter state 5GMM-DEREGISTERED. ATTEMPTING-REGISTRATION or 5GMM-DEREGISTERED.PLMN-SEARCH. Additionally, the UE shall reset the registration attempt counter. If the UE re-attempt the registration procedure to the current PLMN, the UE shall not include the service-level device ID set to the CAA-level UAV ID in the Service-level-AA container IE of REGISTRATION REQUEST message unless the UE receives a CONFIGURATION UPDATE COMMAND message including the service-level-AA service status indication in the Service-level-AA container IE with the UAS field set to "UAS services enabled". If the message was received via 3GPP access and the UE is operating in single-registration mode, the UE shall in addition set the EPS update status to EU2 NOT UPDATED, reset the attach attempt counter and enter the state EMM-DEREGISTERED. #80 (Disaster roaming for the determined PLMN with disaster condition not allowed). The UE shall abort the initial registration procedure, set the 5GS update status to 5U2 NOT UPDATED, enter state 5GMM-DEREGISTERED.ATTEMPTING-REGISTRATION and shall delete any 5G-GUTI, last visited registered TAI, TAI list and ngKSI. Additionally, the UE shall reset the registration attempt counter. The UE shall not attempt to register for disaster roaming services on this PLMN for the determined PLMN with disaster condition for a period in the range of 12 to 24 hours. The UE shall not attempt to register for disaster roaming services on this PLMN for a period in the range of 3 to 10 minutes. The UE shall perform PLMN selection as described in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6]. If the message has been successfully integrity checked by the NAS and the UE maintains the PLMN-specific attempt counter of the PLMN which sent the reject message for the determined PLMN with disaster condition, the UE shall set the PLMN-specific attempt counter of the PLMN which sent the reject message for the determined PLMN with disaster condition to the UE implementation-specific maximum value. If the message was received via 3GPP access and the UE is operating in single-registration mode, the UE shall in addition set the EPS update status to EU2 NOT UPDATED, reset the attach attempt counter and enter the state EMM-DEREGISTERED. #81 (Selected N3IWF is not compatible with the allowed NSSAI). The UE shall abort the initial registration procedure, set the 5GS update status to 5U2 NOT UPDATED and enter state 5GMM-DEREGISTERED. ATTEMPTING-REGISTRATION or 5GMM-DEREGISTERED.PLMN-SEARCH. Additionally, the UE shall reset the registration attempt counter. If the N3IWF identifier IE is included in the REGISTRATION REJECT message and the UE supports slice-based N3IWF selection, the UE may use the provided N3IWF identifier IE in N3IWF selection as specified in 3GPP TS 24.502[ Access to the 3GPP 5G Core Network (5GCN) via non-3GPP access networks ] [18] prior to an immediate consecutive initial registration attempt to the network, otherwise the UE shall ignore the N3IWF identifier IE. #82 (Selected TNGF is not compatible with the allowed NSSAI). The UE shall abort the initial registration procedure, set the 5GS update status to 5U2 NOT UPDATED and enter state 5GMM-DEREGISTERED. ATTEMPTING-REGISTRATION or 5GMM-DEREGISTERED.PLMN-SEARCH. Additionally, the UE shall reset the registration attempt counter. If the TNAN information IE is included in the REGISTRATION REJECT message and the UE supports slice-based TNGF selection, the UE may use the provided TNAN information IE in TNAN selection as specified in 3GPP TS 24.502[ Access to the 3GPP 5G Core Network (5GCN) via non-3GPP access networks ] [18] prior to an immediate consecutive registration attempt to the network, otherwise the UE shall ignore the TNAN information IE. Other values are considered as abnormal cases. The behaviour of the UE in those cases is specified in subclause 5.5.1.2.7. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.5.1.2.5 |
6,536 | 10.3.1 Skip indicator | Bits 5 to 8 of the first octet of every Mobility Management message and GPRS MobilityManagement message contains the skip indicator. With the exception of the following cases for a shared GERAN network in A/Gb mode, - when the MS is sending a LOCATION UPDATING REQUEST, CM SERVICE REQUEST, IMSI DETACH INDICATION or CM RE-ESTABLISHMENT REQUEST message; or - when the network is receiving a LOCATION UPDATING REQUEST, PAGING RESPONSE, CM SERVICE REQUEST, IMSI DETACH INDICATION or CM RE-ESTABLISHMENT REQUEST message, the skip indicator field shall be handled as follows: a) A message received with skip indicator different from 0000 shall be ignored. A message received with skip indicator encoded as 0000 shall not be considered an error that causes the message to be ignored. b) A protocol entity sending a Mobility Management message or a GPRS Mobility Management message shall encode the skip indicator as 0000. In a shared GERAN network in A/Gb mode: a) When the MS is sending a LOCATION UPDATING REQUEST, CM SERVICE REQUEST, IMSI DETACH INDICATION or CM RE-ESTABLISHMENT REQUEST message, - if the MS is a GERAN network sharing supporting MS, the MS shall encode the skip indicator IE to indicate the chosen PLMN identity from the PLMN identities in the broadcast system information (see 3GPP TS 44.018[ None ] [84]) according to table 10.3.1; - otherwise, the MS shall encode the skip indicator as 0000. b) When the network is receiving a LOCATION UPDATING REQUEST, PAGING RESPONSE, CM SERVICE REQUEST, IMSI DETACH INDICATION or CM RE-ESTABLISHMENT REQUEST message, - if the skip indicator is encoded as 0000, the message shall not be considered an error that causes the message to be ignored; - if the skip indicator is different from 0000, the message shall not be considered an error and shall be processed by the receiving MM entity. The MS shall be considered as GERAN network sharing supporting MS. NOTE: The skip indicator handling of PAGING RESPONSE message on the MS and the BSS is specified in 3GPP TS 44.018[ None ] [84]. Figure 10.3.1: Skip indicator Table 10.3.1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Skip indicator | 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.3.1 |
6,537 | 4.2.2.2.3 Registration with AMF re-allocation | When an AMF receives a Registration request, the AMF may need to reroute the Registration request to another AMF, e.g. when the initial AMF is not the appropriate AMF to serve the UE. The Registration with AMF re-allocation procedure, described in figure 4.2.2.2.3-1, is used to reroute the NAS message of the UE to the target AMF during a Registration procedure. Figure 4.2.2.2.3-1: Registration with AMF re-allocation procedure The initial AMF and the target AMF register their capability at the NRF. 1. If the UE is in CM-IDLE State, steps 1 and 2 of figure 4.2.2.2.2-1 have occurred and the (R)AN sends the Registration request message within an Initial UE message to the initial AMF. If the UE is in CM-CONNECTED state and triggers registration procedure, the NG-RAN sends Registration request message in the Uplink NAS Transport message to the serving AMF which is initial AMF. The AMF may skip step 2-3. 2. If the AMF needs the SUPI and/or UE's subscription information to decide whether to reroute the Registration Request or if the Registration Request was not sent integrity protected or integrity protection is indicated as failed, then AMF performs steps 4 to 9a or to 9b of figure 4.2.2.2.2-1. 3a. [Conditional] If the initial AMF needs UE's subscription information to decide whether to reroute the Registration Request and UE's slice selection subscription information was not provided by old AMF, the AMF selects a UDM as described in clause 6.3.8 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. 3b. Initial AMF to UDM: Nudm_SDM_Get (SUPI, Slice Selection Subscription data). The initial AMF request UE's Slice Selection Subscription data from UDM by invoking the Nudm_SDM_Get (see clause 5.2.3.3.1) service operation. UDM may get this information from UDR by Nudr_DM_Query(SUPI, Slice Selection Subscription data). For a Disaster Roaming Registration, the AMF may provide the indication of Disaster Roaming service to the UDM. 3c. UDM to initial AMF: Response to Nudm_SDM_Get. The AMF gets the Slice Selection Subscription data including Subscribed S-NSSAIs. UDM responds with slice selection subscription data to initial AMF. For a Disaster Roaming Registration, the UDM responds with the slice selection subscription data for a Disaster Roaming service to initial AMF based on the local policy and/or the local configuration as specified in clause 5.40.4 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. 4a. [Conditional] Initial AMF to NSSF: Nnssf_NSSelection_Get (Requested NSSAI, [Mapping Of Requested NSSAI], Subscribed S-NSSAI(s) with the default S-NSSAI indication, [NSSRG Information], TAI, Allowed NSSAI for the other access type (if any), [Mapping of Allowed NSSAI], PLMN ID of the SUPI). If there is a need for slice selection, (see clause 5.15.5.2.1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]), e.g. the initial AMF cannot serve all the S-NSSAI(s) from the Requested NSSAI permitted by the subscription information, the initial AMF invokes the Nnssf_NSSelection_Get service operation from the NSSF by including Requested NSSAI, optionally Mapping Of Requested NSSAI, Subscribed S-NSSAIs with the default S-NSSAI indication, [NSSRG Information], Allowed NSSAI for the other access type (if any), Mapping of Allowed NSSAI, PLMN ID of the SUPI and the TAI of the UE. If the AMF needs to indicate the NSSF to return the Configured NSSAI to obtain network slice configuration when it receives from the UDM an indication that subscription has changed for the UE (see step 14b of clause 4.2.2.2.2) to ensure that the information returned by the NSSF includes the new Configured NSSAI for the UE which can be used to update UE network slicing configuration (see step 21 of clause 4.2.2.2.2), the AMF indicates to the NSSF that the AMF needs a Configured NSSAI by providing the Default Configured NSSAI Indication as described in clause 5.15.5.2.1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The AMF includes, if available, the NSSRG Information for the S-NSSAIs of the HPLMN, defined in clause 5.15.12 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], including information whether the UE has indicated support of the subscription-based restrictions to simultaneous registration of network slices and whether the UDM has indicated to provide all subscribed S-NSSAIs for non-supporting UEs. If the UE context includes Partially Allowed NSSAI, then the AMF includes the S-NSSAIs of the Partially Allowed NSSAI in the Allowed NSSAI and includes the corresponding HPLMN S-NSSAI in the Mapping Of Allowed NSSAI. 4b. [Conditional] NSSF to Initial AMF: Response to Nnssf_NSSelection_Get (AMF Set or list of AMF addresses, Allowed NSSAI for the first access type, [Mapping Of Allowed NSSAI], [Allowed NSSAI for the second access type], [Mapping of Allowed NSSAI], [NSI ID(s)], [NRF(s)], [List of rejected (S-NSSAI(s), cause value(s))], [Configured NSSAI for the Serving PLMN], [Mapping Of Configured NSSAI]). The NSSF performs the steps specified in point (B) in clause 5.15.5.2.1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The NSSF returns to initial AMF the Allowed NSSAI for the first access type, optionally the Mapping Of Allowed NSSAI, the Allowed NSSAI for the second access type (if any), optionally the Mapping of Allowed NSSAI and the target AMF Set or, based on configuration, the list of candidate AMF(s). The NSSF may return NSI ID(s) associated to the Network Slice instance(s) corresponding to certain S-NSSAI(s). The NSSF may return the NRF(s) to be used to select NFs/services within the selected Network Slice instance(s). It may return also information regarding rejection causes for S-NSSAI(s) not included in the Allowed NSSAI. The NSSF may return Configured NSSAI for the Serving PLMN and possibly the associated mapping of the Configured NSSAI. If the NSSRG information was included in the request, the NSSF provides the Configured NSSAI as described in clause 5.15.12 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. NOTE 1: The NRF(s) returned by the NSSF, if any, belong to any level of NRF (see clause 6.2.6 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]) according to the deployment decision of the operator. 5. [Conditional] Initial AMF to old AMF: Namf_Communication_RegistrationStatusUpdate (failure cause ). If the UE was in CM-IDLE and another AMF is selected, the initial AMF sends a reject indication to the old AMF telling that the UE Registration procedure did not fully complete at the initial AMF. The old AMF continues as if the Namf_Communication_UEContextTransfer had never been received. 6a. [Conditional] Initial AMF to NRF: Nnrf_NFDiscovery_Request (NF type, AMF Set). If the initial AMF does not locally store the target AMF address and if the initial AMF intends to use direct reroute to target AMF or the reroute via (NG-R)AN message needs to include AMF address, then the initial AMF invokes the Nnrf_NFDiscovery_Request service operation from the NRF to find a proper target AMF which has required NF capabilities to serve the UE. The NF type is set to AMF. The AMF Set is included in the Nnrf_NFDiscovery_Request. 6b. [Conditional] NRF to AMF: Response to Nnrf_NFDiscovery_Request (list of (AMF pointer, AMF address, plus additional selection rules and NF capabilities)). The NRF replies with the list of potential target AMF(s). The NRF may also provide the details of the services offered by the candidate AMF(s) along with the notification end-point for each type of notification service that the selected AMF had registered with the NRF, if available. As an alternative, it provides a list of potential target AMFs and their capabilities and optionally, additional selection rules. Based on the information about registered NFs and required capabilities, a target AMF is selected by the initial AMF. If the security association has been established between the UE and initial AMF, to avoid a registration failure, the initial AMF shall forward the NAS message to the target AMF by executing step 7(A). NOTE 2: The security context in the initial AMF is not transferred to the target AMF if initial AMF forward the NAS message to the target AMF via (R)AN. In this case the UE rejects the NAS message sent from target AMF as the security context in the UE and target AMF are not synchronized. NOTE 3: Network slice isolation cannot be completely maintained in case the AMF reallocation is executed by step 7(A). If the initial AMF is not part of the target AMF Set and is not able to get a list of candidate AMF(s) by querying the NRF with the target AMF Set (e.g. the NRF locally pre-configured on AMF does not provide the requested information, the query to the appropriate NRF provided by the NSSF is not successful, or the initial AMF has knowledge that the initial AMF is not authorized as serving AMF etc.) then the initial AMF shall forward the NAS message to the target AMF via (R)AN executing step 7(B) unless the security association has been established between the UE and initial AMF; the Allowed NSSAI, optionally the Partially Allowed NSSAI and the AMF Set are included to enable the (R)AN to select the target AMF as described in clause 6.3.5 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. 7(A). If the initial AMF, based on local policy and subscription information, decides to forward the NAS message to the target AMF directly, the initial AMF invokes the Namf_Communication_N1MessageNotify to the target AMF, carrying the rerouted NAS message. The Namf_Communication_N1MessageNotify service operation includes AN access information (e.g. the information enabling (R)AN to identify the N2 terminating point, CAG Identifier(s) of the CAG cell) and the complete Registration Request message in clear text as specified in TS 33.501[ Security architecture and procedures for 5G System ] [15] and the UE's SUPI and MM Context if available. If the initial AMF has obtained the information from the NSSF as described at step 4b, that information except the AMF Set or list of AMF addresses is included. The target AMF then updates the (R)AN with a new updated N2 termination point for the UE in the first message from target AMF to RAN in step 8. 7(B). [Conditional] if the UE was in CM-IDLE, if the initial AMF, based on local policy and subscription information, decides to forward the NAS message to the target AMF via (R)AN unless the target AMF(s) are returned from the NSSF and identified by a list of candidate AMF(s), the initial AMF sends a NGAP Reroute NAS Request message to the (R)AN (step 7a). The NGAP Reroute Request NAS message includes the information about the target AMF and the complete Registration Request message. If the initial AMF has obtained the information as described at step 4b, that information is included. The (R)AN sends the Initial UE message to the target AMF (step 7b) indicating reroute due to slicing including the information from step 4b that the NSSF provided. NOTE 4: Step 7B is not supported if the UE was in CM-CONNECTED i.e. the NGAP Uplink NAS Transport message was received at step 1. 8. After receiving the Registration Request message transmitted at step 7(A)a or step 7(B)b, the target AMF continues with the Registration procedure from step 4 until 22 of figure 4.2.2.2.2-1 (with the target AMF corresponding to the new AMF), which includes the UE context retrieved from old AMF. If the 5G security context is received from the initial AMF, the target AMF continue using that one instead of the 5G security context the target AMF may have retrieved from the old AMF. If the initial AMF decides to forward the NAS message to the target AMF (step 7(A), the first message from the target AMF to (R)AN (either Initial Context Setup Request, or Downlink NAS Transport) contain the AMF name of the initial AMF and target AMF UE NGAP ID. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.2.2.2.3 |
6,538 | 5.2.3.3.4 Nudm_SDM_Subscribe service operation | Service operation name: Nudm_SDM_Subscribe Description: The NF consumer subscribes for updates to Subscription Data indicated by the 'subscription data type' input. The UDM shall check the requested consumer is authorized to subscribe to requested updates. Inputs, Required: Subscription data type(s), Key for each Subscription data type(s). Inputs, Optional: Data Sub Key(s), Immediate Report Indication, Disaster Roaming Indicator indicating that Disaster Roaming service is applied. Outputs, Required: None. Outputs, Optional: Subscription Data. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.3.3.4 |
6,539 | 10.5.5.15 Routing area identification | The purpose of the routing area identification information element is to provide an unambiguous identification of routing areas within the GPRS coverage area. The routing area identification is a type 3 information element with 7 octets length. The routing area identification information element is coded as shown in figure 10.5.130/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.148/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Figure 10.5.130/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Routing area identification information element Table 10.5.148/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Routing area identification information element | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 10.5.5.15 |
6,540 | 8 Security 8.2 General | The 5G system shall support a secure mechanism to store cached data. The 5G system shall support a secure mechanism to access a content caching application. The 5G system shall support a secure mechanism to access a service or an application in an operator's Service Hosting Environment. The 5G system shall enable support of an access-independent security framework. The 5G system shall support a mechanism for the operator to authorize subscribers of other PLMNs to receive temporary service (e.g. mission critical services). The 5G system shall be able to provide temporary service for authorized users without access to their home network (e.g. IOPS, mission critical services). The 5G system shall allow the operator to authorize a third-party to create, modify and delete network slices, subject to an agreement between the third-party and the network operator. Based on operator policy, a 5G network shall provide suitable means to allow a trusted and authorized third-party to create and modify network slices used for the third-party with appropriate security policies (e.g. user data privacy handling, slices isolation, enhanced logging). The 5G system shall support a secure mechanism to protect relayed data from being intercepted by a relay UE. Subject to HPLMN policy as well as its service and operational needs, any USIM able to access EPS instead of a 5G USIM may be used to authenticate a user in a 5G system to access supported services according to the user subscription. The 5G system shall provide integrity protection and confidentiality for communications between authorized UEs using a 5G LAN-type service. The 5G LAN-VN shall be able to verify the identity of a UE requesting to join a specific private communication. The 5G system shall provide suitable means to allow the use of a trusted third-party provided encryption between any UE served by a private slice and a core network entity in that private slice. The 5G system shall provide suitable means to allow use of a trusted and authorized third-party provided integrity protection mechanism for data exchanged between an authorized UE served by a private slice and a core network entity in that private slice. The 5G system shall provide suitable means to allow use of a trusted and authorized third-party provided integrity protection mechanism for data exchanged between an authorized UE served by a non-public network and a core network entity in that non-public network. The 5G system shall enable a PLMN to host an NPN without compromising the security of that PLMN. NOTE: Dedicated network entities of NPN can be deployed in customer premises that are outside the control of the PLMN operator. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 8 |
6,541 | 7.6.1.1 Minimum requirements | The throughput shall be β₯ 95% of the maximum throughput of the reference measurement channels as specified in Annexes A.2.2, A.2.3 and A.3.2 (with one sided dynamic OCNG Pattern OP.1 FDD/TDD for the DL-signal as described in Annex A.5.1.1/A.5.2.1) with parameters specified in Tables 7.6.1.1-1 and 7.6.1.1-2. For operating bands with an unpaired DL part (as noted in Table 5.5-1), the requirements only apply for carriers assigned in the paired part. Table 7.6.1.1-1: In band blocking parameters Table 7.6.1.1-2: In-band blocking For the UE which supports inter band CA configuration in Table 7.3.1-1A, PInterferer power defined in Table 7.6.1.1-2 is increased by the amount given by ΞRIB,c in Table 7.3.1-1A. | 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 | 7.6.1.1 |
6,542 | 4.12b.2 Initial Registration & PDU Session Establishment | Figure 4.12b.2-1 illustrates how the N5CW device can connect to a trusted WLAN Access Network and simultaneously register to a 5G core network. A single EAP-based authentication procedure is executed for connecting the N5CW device to the trusted WLAN Access Network and for registering the N5CW device to the 5G core network. Figure 4.12b.2-1: Initial registration and PDU session establishment 0. The N5CW device selects a PLMN (or SNPN) and a trusted WLAN that supports "5G connectivity-without-NAS" to this PLMN (or SNPN) by using the procedure specified in clause 6.3.12a and clause 5.30.2.15 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] for access to PLMN and SNPN, respectively. Steps 1-10: Initial registration to 5GC. 1. The N5CW device associates with the selected trusted WLAN and the EAP authentication procedure is initiated. 2. The N5CW device provides its Network Access Identity (NAI). The Trusted WLAN Access Point (TWAP) selects a Trusted WLAN Interworking Function (TWIF), e.g. based on the received realm and sends an AAA request to the selected TWIF. If the N5CW device has not registered over 3GPP access to 5GC of the selected PLMN or SNPN when the above procedure is initiated, then the NAI includes the SUCI as specified in clause 28.7.7 of TS 23.003[ Numbering, addressing and identification ] [33]. For example, when accessing a PLMN the NAI can have the following format: [email protected]<MNC>.mcc<MCC>.3gppnetwork.org. If the selected PLMN is VPLMN, the N5CW device should use the decorated NAI format as specified in clause 28.7.9 of TS 23.003[ Numbering, addressing and identification ] [33] to indicate to TWAN which is the selected VPLMN, for example, NAI=nai.5gc-nn.mnc<MNC_Home>.mcc<MCC_Home>[email protected]<MNC_visited>.mcc<MCC_visited>.3gppnetwork.org. If the N5CW device has registered to 5GC over 3GPP access to 5GC of the selected PLMN or SNPN (i.e. it is also a 5G UE) when the above procedure is initiated, then the NAI includes the 5G-GUTI assigned to N5CW device over 3GPP access. This enables the TWIF in step 4a below to select the same AMF as the one serving the N5CW device over 3GPP access. If the N5CW device accesses to SNPN with the credentials owned by Credentials Holder, the decorated NAI as specified in clause 28.7.9 of TS 23.003[ Numbering, addressing and identification ] [33] should be provided. For example, NAI=nai.5gc-nn.nid<NID_Home>.mnc<MNC_Home>.mcc<MCC_Home>[email protected]<NID_visited>.mnc<MNC_visited>.mcc<MCC_visited>.3gppnetwork.org. The NAI provided by the N5CW device in step 2b indicates that the N5CW device wants "5G connectivity-without-NAS" towards a specific PLMN or SNPN (i.e. the PLMN or SNPN selected in step 0). For example, when accessing a PLMN, the NAI can have the following format: NAI=<5G-GUTI>@nai.5gc-nn.mnc<MNC>.mcc<MCC>.3gppnetwork.org or NAI=nai.5gc-nn.mnc<MNC_Home>.mcc<MCC_Home>[email protected]<MNC_visited>.mcc<MCC_visited>.3gppnetwork.org, the N5CW device indicating that it wants "5G connectivity-without-NAS" (5gc-nn) to the PLMN with MCC=<MCC> and MNC=<MNC> and to the PLMN with MCC=<MCC_visited> and MNC=<MNC_visited>. 3. The TWIF creates a 5GC Registration Request message on behalf of the N5CW device. The TWIF uses default values to populate the parameters in the Registration Request message, which are the same for all N5CW devices. The Registration type indicates "Initial Registration". If the TWIF receives a Decorated NAI, in Registration Request message the TWIF send the NAI which corresponds to the HPLMN by removing the decoration, for example NAI=type1.rid678.schid0.useriduser17@ nai.5gc-nn.mnc<MNC_Home>.mcc<MCC_Home>.3gppnetwork.org. 4. The TWIF selects an AMF by using the 5G-GUTI in the NAI, or selects the AMF of the VPLMN indicates by the realm of the decoration in the Decorated NAI, for example "mnc<MNC_visited>.mcc<MCC_visited>.3gppnetwork.org" or selects the AMF by using the local configuration. TWIF sends an N2 message to the AMF including the Registration Request, the User Location and an AN Type. If the N5CW device provides a Decorated NAI to the TWIF, the TWIF shall select the AMF in the visited PLMN/SNPN as per decoration part and remove the decoration part from the Decorated NAI (i.e. change the format to NAI format of SUCI as defined in clause 28.7.7 of TS 23.003[ Numbering, addressing and identification ] [33]) and provides it to AMF in the Registration Request. For example, if the NAI is "nai.5gc-nn.nid<NID_Home>.mnc<MNC_Home>.mcc<MCC_Home>[email protected]<NID_visited>.mnc<MNC_visited>.mcc<MCC_visited>.3gppnetwork.org.", the TWIF selects the AMF in the SNPN corresponding to "nai.5gc-nn.nid<NID_visited>.mnc<MNC_visited>.mcc<MCC_visited>.3gppnetwork.org." and provides the AMF in the Registration Request with the NAI of "type1.rid678.schid0.useriduser17@ nai.5gc-nn.nid<NID_Home>.mnc<MNC_Home>.mcc<MCC_Home>.3gppnetwork.org". 5. The AMF triggers an authentication procedure by sending a request to AUSF indicating the AN type. 6. An EAP authentication procedure takes place between the N5CW device and AUSF. Over the N2 interface, the EAP messages are encapsulated within NAS Authentication messages. The type of EAP authentication procedure is specified in TS 33.501[ Security architecture and procedures for 5G System ] [15]. NOTE: The SUPI used for authentication does not take the format of Decorated NAI. 7. After a successful authentication, the AUSF sends to AMF the EAP-Success message and the created SEAF key. The AMF derives an AN key from the received SEAF key. 8. The NAS Security Mode Command (SMC) is sent from the AMF to the TWIF. The selected NAS security algorithms of integrity protection and ciphering are set to NULL. 9. The AMF sends an N2 Initial Context Setup Request and provides the AN key to TWIF. In turn, the TWIF derives a Pairwise Master Key (PMK) from the AN key and sends the PMK key and the EAP-Success message to the Trusted WLAN Access Point, which forwards the EAP-Success to the N5CW device. The PMK is the key used to secure the WLAN air-interface communication according to IEEE Std 802.11 [48]. A layer-2 or layer-3 connection is established between the Trusted WLAN Access Point and the TWIF for transporting all user-plane traffic of the N5CW device to TWIF. This connection is later bound to an N3 connection that is created for this N5CW device. 10. Finally, the AMF sends a Registration Accept message to TWIF. At this point, the N5CW device is connected to the WLAN Access Network and is registered to 5GC. Steps 20-21: PDU Session Establishment. 20. The TWIF creates a PDU Session Establishment Request message on behalf of the N5CW device and sends this message to AMF. This may be triggered by receiving an IP configuration request (e.g. DHCP Offer/Request) from the N5CW device. The TWIF may use default values to populate the parameters in the PDU Session Establishment Request message, but may also skip some PDU session parameters and let the AMF or the SMF determine these parameters based on the N5CW device subscription information received during the registration procedure. This way, default PDU session parameters can be used per N5CW device. The value of the PDU Session id provided by TWIF in step 20c shall always be the same. It will be a value reserved for the PDU sessions requested by the TWIF and it will be different from the values that can be used by the N5CW device when requesting a PDU session over 3GPP access. This way, the PDU session id provided by the TWIF cannot be the same with the PDU Session Id of any PDU session established by the N5CW device over 3GPP access. 21. The AMF sends upon request of the SMF an N2 PDU Session Request message to TWIF in order to reserve the appropriate Access Network resources. This N2 message includes the PDU Session Establishment Accept message. In step 21b, the TWIF may reserve WLAN access resources for the user-plane communication between the N5CW device and TWIF. If and how this resource reservation is performed is outside the scope of 3GPP. After the establishment of the PDU session, the TWIF assigns IP configuration data to N5CW device (e.g. with DHCP). The IP address assigned to N5CW device is the IP address allocated to the PDU session. Step 25: User plane communication. The TWIF binds the N5CW device-specific L2/L3 connection created in step 9g with the N3 connection created in step 21. All user-plane traffic sent by the N5CW device is forwarded to TWIF via the L2/L3 connection and then to UPF via the N3 connection. The TWIF operates as a Layer-2 relay. The TWIF may receive URSP rules (see TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]), which indicate the traffic that should be offloaded locally by TWIF (sent outside the PDU session) and the traffic that should be sent inside the PDU session. The above procedure supports only one PDU session per N5CW device whose parameters are either configured for all N5CW devices in the TWIF or are derived from default values in the N5CW device subscription. If the TWIF is co-located with one or more local UPFs then: - In step 20c (N2 Uplink NAS Transport), the TWIF may send a TWIF Identities parameter to AMF. The TWIF Identities parameter contains a list of identifiers (i.e. FQDNs or IP addresses) of N3 terminations supported by the TWIF. - If received by the AMF, it shall forward it to the SMF when invoking Nsmf_PDUSessionCreateSMContext i.e. at the establishment of the PDU Session. The SMF may use this information to select a local UPF for the PDU Session. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.12b.2 |
6,543 | 6.46.8.2 Requirements | Subject to operatorβs policies, a 5G system with satellite access shall be able to support S&F Satellite operation for authorized UEs e.g. store data on the satellite when the feeder link is unavailable; and forward the data once the feeder link between the satellite and the ground segment becomes available. A 5G system with satellite access shall be able to inform a UE whether S&F Satellite operation is applied. Subject to operatorβs policies, a 5G system with satellite access supporting S&F Satellite operation shall be able to allow the operator or a trusted 3rd party to apply, on a per UE and/or satellite basis, an S&F data retention period. Subject to operatorβs policies, a 5G system with satellite access supporting S&F Satellite operation shall be able to allow the operator or a trusted 3rd party to apply, on a per UE and/or satellite basis, an S&F data storage quota. Subject to regulatory requirements and operatorβs policy, a 5G system with satellite access supporting S&F Satellite operation shall be able to support a mechanism to configure and provision specific store and forward QoS and policies for a UE (e.g. forwarding priority, acknowledgment policy). A 5G system with satellite access supporting S&F Satellite operation shall be able to provide related information (e.g. estimated delivery time to the authorised 3rd party) to an authorized UE. A 5G system with satellite access shall be able to inform an authorised 3rd party whether S&F Satellite operation is applied for communication with a UE and to provide related information (e.g. estimated delivery time to the authorised UE). Subject to operatorβs policies, a 5G system with satellite access supporting S&F Satellite operation shall be able to support forwarding of the stored data from one satellite to another satellite (e.g., which has an available feeder link to the ground network), through ISLs. NOTE: It is assumed that the satellite constellation knows which satellite has a feeder link available. However, this is outside the scope of 3GPP. Subject to operatorβs policies, a 5G system with satellite access supporting the S&F Satellite operation shall be able to support suitable means to resume communication between the satellite and the ground station once the feeder link becomes available. A 5G system with satellite access supporting S&F Satellite operation shall support mechanisms for a UE to register with the network when the network is in S&F Satellite operation. A 5G system with satellite access supporting S&F Satellite operation shall support mechanisms to authorize subscribers for receiving services when the network is in S&F Satellite operation. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.46.8.2 |
6,544 | 4.22.2.2.1 Home-routed Roaming - UE registered to the same PLMN | When the UE is registered to the same VPLMN over 3GPP access and non-3GPP access, the MA PDU Session is established as specified in Figure 4.3.2.2.2-1 ("UE-requested PDU Session Establishment for home-routed roaming scenarios") with the differences and clarifications: - The PDU Session Establishment Request message may be sent over the 3GPP access or over the non-3GPP access. - In step 1, the UE provides Request Type as "MA PDU Request" 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. The UE indicates to AMF whether it supports non-3GPP access path switching. - In step 2, if the AMF supports MA PDU sessions, then the AMF selects a V-SMF and an H-SMF, which supports MA PDU sessions. The V-SMF serves the UE over both accesses. If the AMF supports non-3GPP access path switching and the UE indicated in step 1 that the UE supports non-3GPP access path switching, the AMF selects a V-SMF and H-SMF supporting non-3GPP access path switching, if such a V-SMF and H-SMF are available. - In step 3, the AMF informs the SMF that the request is for a MA PDU Session by including an "MA PDU Request" indication and in addition, the AMF indicates to V-SMF that the UE is registered over both accesses. If the AMF supports non-3GPP access path switching while maintaining two N2 connections for non-3GPP access, the selected SMFs supports non-3GPP path switching and UE indicated in step 1 that the UE supports non-3GPP access path switching, the AMF indicates whether the UE supports non-3GPP path switching to the V-SMF. - 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. - In step 6, the V-SMF informs the H-SMF that the request is for a MA PDU Session by including an "MA PDU Request" indication and indicates to H-SMF that the UE is registered over both accesses. 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 info binding to the access over which the NAS message is received is to be used. - In step 7, the H-SMF retrieves, via Session Management subscription data, the information whether the MA PDU session is allowed or not. - In step 9, if dynamic PCC is to be used for the MA PDU Session, the H-SMF sends an "MA PDU Request" indication to H-PCF in the SM Policy Control Create message and the ATSSS Capabilities of the MA PDU session. The H-SMF provides the currently used list of Access Type(s) and RAT Type(s) for the MA-PDU session to the H-PCF. The H-PCF decides whether the MA PDU session is allowed or not based on operator policy and subscription data. The H-PCF provides the PCC rules containing MA PDU session control information and the H-SMF derives the ATSSS rules for the UE and the N4 rules for the H-UPF. - In step 12, two UL N9 tunnel CN info are allocated by the H-SMF or by the H-UPF. After this step, the two N9 tunnels between the H-UPF and V-UPF are established. - In step 13, the H-SMF sends "MA PDU session Accepted" indication to V-SMF in the Nsmf_PDUSession_Create Response message. The H-SMF indicates to V-SMF the relationship between the UL N9 tunnel CN info and the access type. - In step 14, the V-SMF sends the "MA PDU session Accepted" indication in the Namf_Communication_N1N2MessageTransfer message to the AMF and indicates the AMF to send the N2 SM Information included in this message over the access that the UE sent the PDU Session Establishment Request. The AMF marks this PDU session as MA PDU session based on the received "MA PDU session Accepted" indication. The V-SMF indicates support of non-3GPP path switching in the PDU Session Establishment Accept message. If the V-SMF received two UL N9 tunnel CN info from the H-SMF, the V-SMF also initiates the establishment of user-plane resources over the other access. The V-SMF sends an N1N2 Message Transfer to AMF including N2 SM Information and the other access type to indicate to AMF that the N2 SM Information should be sent over the other access. The N1N2 Message Transfer does not include an N1 SM Container for the UE which was sent to UE over the access that the UE sent the PDU Session Establishment Request. - In step 16, the UE receives a PDU Session Establishment Accept message, which indicates to UE that the requested MA PDU session was successfully established. This message includes the ATSSS rules for the MA PDU session, which were derived by H-SMF and may include Measurement Assistance Information. - After step 20, if the V-SMF was informed in step 3 that the UE is registered over both accesses, then the V-SMF initiates the establishment of user-plane resources over the other access too. The V-SMF sends an N1N2 Message Transfer to the AMF including N2 SM Information and indicates to the AMF over which access the N2 SM Information should be sent. The N1N2 Message Transfer does not include an N1 SM Container for the UE because this was sent to the UE in step 14. After this step, two N9 tunnels between the H-UPF and the V-UPF as well as two N3 tunnels between the V-UPF and RAN/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.2.2.1 |
6,545 | A.9 KgNB, KWAGF, KTNGF, KTWIF and KN3IWF derivation function | When deriving the keys KgNB, KWAGF, KTNGF, KTWIF and KN3IWF from KAMF and the uplink NAS COUNT in the UE and the AMF the following parameters shall be used to form the input S to the KDF. - FC = 0x6E - P0 = Uplink NAS COUNT - L0 = length of uplink NAS COUNT (i.e. 0x00 0x04) - P1 = Access type distinguisher - L1 = length of Access type distinguisher (i.e. 0x00 0x01) The values for the access type distinguisher are defined in table A.9-1. The values 0x00 and 0x03 to 0xf0 are reserved for future use, and the values 0xf1 to 0xff are reserved for private use. The access type distinguisher shall be set to the value for 3GPP (0x01) when deriving KgNB. The access type distinguisher shall be set to the value for non-3GPP (0x02) when deriving KN3IWF, KWAGF, KTWIF or KTNGF.. Table A.9-1: Access type distinguishers The input key KEY shall be the 256-bit KAMF. This function is applied when cryptographically protected 5G radio bearers are established and when a key change on-the-fly is performed. As N5CW devices do not support NAS over non-3GPP access, the Uplink NAS COUNT shall be set to 0 for KTWIF key generation, see clause 7A.2.4. Similarly, the AUN3 devices do not support NAS over non-3GPP access, the Uplink NAS COUNT shall be set to 0 for KWAGF key generation, see clause 7B.7.3. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | A.9 |
6,546 | Annex I (informative): Indirect Network Sharing of NG-RAN Sharing | This annex clarifies scenarios applicable for Indirect Network Sharing between a Shared NG-RAN and the corresponding participating operator's core network as alternatives for operators who intend to deploy a NG Radio Access Network. Examples of such scenarios include wide-range coverage of rural areas, long-distance road coverage, compatibility with existing networks, service consistency, cooperation with diverse networks, considering different operators' strategies, commercial agreements, and specific rules/legislation in different countries. Two or more operators have deployed or plan to deploy 5G access networks and core networks with MOCN. The challenge for the network operators is the maintenance generated by the interconnection (e.g., number of network interfaces) between the shared RAN and two or more core networks, especially for a large number of shared base stations. For these reasons, it is valuable to introduce a newly supported network sharing scenario as the operators' agreement. In case of Indirect Network Sharing, the communication between the Shared NG-RAN and the Participating Operatorβs core network happens via a number of inter-operator interfaces that are independent of the actual number of base stations at the Hosting NG-RAN Operator. There is an agreement between all the operators to work together and build a shared network together cover the entire country, utilizing the different operatorβs allocated spectrum appropriately in different parts of the coverage area (for example, Low Traffic Areas and High Traffic Areas). Multiple operators share one NG-RAN, but their 5GCs are independent. UEs access their subscribed PLMN services and/or subscribed services, including Hosted Services, provided by their participating operators respectively, when entering the Shared NG-RAN. The following figures illustrate the example in which Indirect Network Sharing is realized via routing through the Hosting Operatorβs core network. - The Hosting NG-RAN Operator 1, as illustrated below, can share its NG-RAN with the participating operators with or without direct connections between the shared access and the core networks of the participating operators. - The Participating NG-RAN Operators 2 and 3, using shared NG-RAN resources provided by the Hosting NG-RAN Operator, e.g., within a specific 5G frequency band or within a specific area, when the Shared NG-RAN does not have direct connections between the shared access and the core networks of the Participating NG-RAN Operators 2 and 3. - The Participating NG-RAN Operator 4, using shared NG-RAN resources provided by the Hosting NG-RAN Operator, with direct connections between the shared NG-RAN and the core networks of the participating operator, is in a MOCN arrangement. Figure I-1: Different options both direct and indirect connections between the Shared NG-RAN and the core networks of the participating operators. Figure I-2: Indirect Network Sharing scenario involving core network of Hosting NG-RAN Operator between the Shared NG-RAN and the core networks of the participating operators. The network sharing partners can set a specific sharing allocation model for the network sharing method they are using. The collection of charging information associated with the sharing method that the UE accesses with can be possible. It is also necessary to understand the charging information between the networks of both parties, e.g., the number of the users, and how long users using a certain shared network method will take. This information is also needed when users use the participating operator's hosted services they have subscribed to and their flexible charging via Shared NG-RAN. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | Annex |
6,547 | 6.5.1.4.3 Handling of network rejection due to ESM cause other than ESM cause #26 | If the ESM cause value is different from #26 "insufficient resources", #28 "unknown PDN type", #50 "PDN type IPv4 only allowed", #51 "PDN type IPv6 only allowed", #54 "PDN connection does not exist", #57 "PDN type IPv4v6 only allowed", #58 "PDN type non IP only allowed", #61 "PDN type Ethernet only allowed", #65 "maximum number of EPS bearers reached", and #66 "requested APN not supported in current RAT and PLMN combination", and the Back-off timer value IE is included, the UE shall behave as follows: 1) if the PDN CONNECTIVITY REQUEST message was sent standalone, the UE shall take different actions depending on the timer value received in the Back-off timer value IE (if the UE is a UE configured to use AC11 β 15 in selected PLMN, exceptions are specified in clause 6.3.6): i) if the timer value indicates neither zero nor deactivated, the UE shall start the back-off timer with the value provided in the Back-off timer value IE for the PDN connectivity procedure and PLMN and combination, and the UE: - shall not send another PDN CONNECTIVITY REQUEST message in the PLMN for the same APN that was sent by the UE, until the back-off timer expires, the UE is switched off or the USIM is removed; and - shall not send another PDN CONNECTIVITY REQUEST message in the PLMN without an APN and with request type different from "emergency" and from "handover of emergency bearer services" if no APN was included in the PDN CONNECTIVITY REQUEST message, until the back-off timer expires, the UE is switched off or the USIM is removed; ii) if the timer value indicates that this timer is deactivated, the UE: - shall not send another PDN CONNECTIVITY REQUEST message in the PLMN for the same APN until the UE is switched off or the USIM is removed; and - shall not send another PDN CONNECTIVITY REQUEST message in the PLMN without an APN and with request type different from "emergency" and from "handover of emergency bearer services" if no APN was included in the PDN CONNECTIVITY REQUEST message, until the UE is switched off or the USIM is removed; and iii) if the timer value indicates zero, the UE: - may send another PDN CONNECTIVITY REQUEST message in the PLMN for the same APN; and - may send another PDN CONNECTIVITY REQUEST message in the PLMN without an APN; and 2) if the PDN CONNECTIVITY REQUEST message was sent together with an ATTACH REQUEST, the UE shall take different actions depending on the timer value received in the Back-off timer value IE and on the integrity protection of the ATTACH REJECT message (if the UE is a UE configured to use AC11 β 15 in selected PLMN, exceptions are specified in clause 6.3.6): i) if the ATTACH REJECT message is not integrity protected, the UE shall start the back-off timer with a random value from a default range specified in table 11.2.3(see 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13]), and the UE: a) shall not initiate a new attach procedure or send another PDN CONNECTIVITY REQUEST message in the PLMN with the same APN that was sent by the UE, until the back-off timer expires, the UE is switched off or the USIM is removed; and b) shall not initiate a new attach procedure or send another PDN CONNECTIVITY REQUEST message in the PLMN without an APN and with request type different from "emergency" and from "handover of emergency bearer services", if the UE did not provide any APN during the attach procedure and the request type was different from "emergency", until the back-off timer expires, the UE is switched off or the USIM is removed; and ii) if the ATTACH REJECT message is integrity protected, the UE shall proceed as follows: a) if the timer value indicates neither zero nor deactivated, the UE shall start the back-off timer with the value provided in the Back-off timer value IE for the PDN connectivity procedure and PLMN and combination, and the UE: - shall not initiate a new attach procedure or send another PDN CONNECTIVITY REQUEST message in the PLMN with the same APN that was sent by the UE, until the back-off timer expires, the UE is switched off or the USIM is removed; and - shall not initiate a new attach procedure or send another PDN CONNECTIVITY REQUEST message in the PLMN without an APN and with request type different from "emergency" and from "handover of emergency bearer services", if the UE did not provide any APN during the attach procedure and the request type was different from "emergency" and from "handover of emergency bearer services", until the back-off timer expires, the UE is switched off or the USIM is removed; b) if the timer value indicates that this timer is deactivated, the UE: - shall not initiate a new attach procedure or send another PDN CONNECTIVITY REQUEST message in the PLMN with the same APN that was sent by the UE, until the UE is switched off or the USIM is removed; and - shall not initiate a new attach procedure or send another PDN CONNECTIVITY REQUEST message in the PLMN without an APN and with request type different from "emergency" and from "handover of emergency bearer services", if the UE did not provide any APN during the attach procedure and the request type was different from "emergency" and from "handover of emergency bearer services", until the UE is switched off or the USIM is removed; and c) if the timer value indicates that this timer is zero, the UE shall proceed as specified in clause 5.5.1.2.6 item d. If the Back-off timer value IE is not included and the PDN CONNECTIVITY REQUEST was sent standalone, then the UE shall ignore the Re-attempt indicator IE provided by the network in PDN CONNECTIVITY REJECT, if any. 1) Additionally, if the ESM cause value is #8 "operator determined barring", #27 "missing or unknown APN", #32 "service option not supported", or #33 "requested service option not subscribed", the UE shall proceed as follows: - if the UE is registered in the HPLMN or in a PLMN that is within the EHPLMN list (if the EHPLMN list is present), the UE shall behave as described above in the present clause, using the configured SM_RetryWaitTime value as specified in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [15A] or in USIM file NASCONFIG as specified in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [17], if available, as back-off timer value; and NOTE 0: The way to choose one of the configured SM_RetryWaitTime values for back-off timer value is up to UE implementation if the UE is configured with: - an SM_RetryWaitTime value in ME as specified in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [15A]; and - an SM_RetryWaitTime value in USIM file NASCONFIG as specified in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [17]. - otherwise, if the UE is not registered in its HPLMN or in a PLMN that is within the EHPLMN list (if the EHPLMN list is present), or if the SM_RetryWaitTime value is not configured, the UE shall behave as described above in the present clause, using the default value of 12 minutes for the back-off timer. 2) For ESM cause values different from #8 "operator determined barring", #27 "missing or unknown APN", #32 "service option not supported", or #33 "requested service option not subscribed", the UE behaviour regarding the start of a back-off timer is unspecified. The UE shall not stop any back-off timer upon a PLMN change or inter-system change. If the network indicates that a back-off timer for the PDN connectivity procedure and PLMN and APN combination is deactivated, then it remains deactivated upon a PLMN change or inter-system change. NOTE 1: This means the back-off timer can still be running or be deactivated for the given ESM procedure and PLMN and APN combination when the UE returns to the PLMN or when it performs inter-system change back from A/Gb or Iu mode or N1 mode to S1 mode. Thus the UE can still be prevented from sending another PDN CONNECTIVITY REQUEST message in the PLMN for the same APN. If the Back-off timer value IE is not included and the PDN CONNECTIVITY REQUEST was sent together with an ATTACH REQUEST, the UE shall ignore the Re-attempt indicator IE provided by the network in PDN CONNECTIVITY REJECT, if any, and proceed as specified in clause 5.5.1.2.6, item d. If the back-off timer is started upon receipt of a PDN CONNECTIVITY REJECT (i.e. the timer value was provided by the network, a configured value is available or the default value is used as explained above) or the back-off timer is deactivated, the UE behaves as follows: 1) after a PLMN change the UE may send a PDN CONNECTIVITY REQUEST message for the same APN in the new PLMN, if the back-off timer is not running and is not deactivated for the PDN connectivity procedure and the combination of new PLMN and APN. Furthermore as an implementation option, for the ESM cause values #8 "operator determined barring", #27 "missing or unknown APN", #32 "service option not supported" or #33 "requested service option not subscribed", if the network does not include a Re-attempt indicator IE, the UE may decide not to automatically send another PDN CONNECTIVITY REQUEST message for the same APN that was sent by the UE using the same PDN type, or the UE may decide not to automatically send another PDN CONNECTIVITY REQUEST message included in an ATTACH REQUEST message without an APN using the same PDN type if the UE did not provide any APN in the PDN connectivity procedure, if the UE is registered to a new PLMN which is in the list of equivalent PLMNs; 2) if the network does not include the Re-attempt indicator IE to indicate whether re-attempt in A/Gb or Iu mode or N1 mode is allowed, or the UE ignores the Re-attempt indicator IE, e.g. because the Back-off timer value IE is not included, then: - if the UE is registered in its HPLMN or in a PLMN that is within the EHPLMN list (if the EHPLMN list is present), the UE shall apply the configured SM_RetryAtRATChange value as specified in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [15A] or in USIM file NASCONFIG as specified in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [17], if available, to determine whether the UE may attempt a PDP context activation procedure for the same PLMN and APN combination in A/Gb or Iu mode or a PDU session establishment procedure for the same PLMN and APN combination in N1 mode; and NOTE 2: The way to choose one of the configured SM_RetryAtRATChange values for back-off timer value is up to UE implementation if the UE is configured with: - an SM_RetryAtRATChange value in ME as specified in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [15A]; and - an SM_RetryAtRATChange value in USIM file NASCONFIG as specified in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [17]. - if the UE is not registered in its HPLMN or in a PLMN that is within the EHPLMN list (if the EHPLMN list is present), or if the NAS configuration MO as specified in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [15A] is not available and the value for inter-system change is not configured in the USIM file NASCONFIG, then the UE behaviour regarding a PDP context activation procedure for the same PLMN and APN combination in A/Gb or Iu mode and a PDU session establishment procedure for the same PLMN and APN combination in N1 mode are unspecified; and 3) if the network includes the Re-attempt indicator IE indicating that re-attempt in an equivalent PLMN is not allowed, then depending on the timer value received in the Back-off timer value IE, for each combination of a PLMN from the equivalent PLMN list and the APN the UE shall start a back-off timer for the PDN connectivity procedure with the value provided by the network, or deactivate the respective back-off timer as follows: - if the Re-attempt indicator IE additionally indicates that re-attempt in A/Gb or Iu mode or N1 mode is allowed, the UE shall start or deactivate the back-off timer for S1 mode only; and - otherwise the UE shall start or deactivate the back-off timer for A/Gb, Iu, S1 and N1 mode. If the back-off timer for a PLMN and APN combination was started or deactivated in A/Gb or Iu mode upon receipt of an ACTIVATE PDP CONTEXT REJECT message (see 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13]) and the network indicated that re-attempt in S1 mode is allowed, then this back-off timer does not prevent the UE from sending a PDN CONNECTIVITY REQUEST message in this PLMN for the same APN after inter-system change to S1 mode. If the network indicated that re-attempt in S1 mode is not allowed, the UE shall not send any PDN CONNECTIVITY REQUEST message in this PLMN for the same APN after inter-system change to S1 mode until the timer expires, the UE is switched off or the USIM is removed. If a back-off timer for a PLMN and APN combination, in combination with any S-NSSAI or without S-NSSAI (see 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54]) was started or deactivated in N1 mode upon receipt of a PDU SESSION ESTABLISHMENT REJECT message (see 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54]) and the network indicated that re-attempt in S1 mode is allowed, then this back-off timer does not prevent the UE from sending a PDN CONNECTIVITY REQUEST message in this PLMN for the same APN after inter-system change to S1 mode. If the network indicated that re-attempt in S1 mode is not allowed, the UE shall not send any PDN CONNECTIVITY REQUEST message in this PLMN for the same APN after inter-system change to S1 mode until the timer expires, the UE is switched off or the USIM is removed. If more than one back-off timers for the same PLMN and APN combination was started in N1 mode with an indication from the network that re-attempt in S1 mode is not allowed and no back-off timer for the same PLMN and APN combination was deactivated in N1 mode, the UE shall not send any PDN CONNECTIVITY REQUEST message in this PLMN for the same APN after inter-system change to S1 mode until all timers have expired. If at least one back-off timer for the same PLMN and APN combination was deactivated in N1 mode, the UE shall not send any PDN CONNECTIVITY REQUEST message in this PLMN for the same APN until the UE is switched off or the USIM is removed. NOTE 3: The back-off timer is used to describe a logical model of the required UE behaviour. This model does not imply any specific implementation, e.g. as a timer or timestamp. NOTE 4: Reference to back-off timer in this section can either refer to use of timer T3396 or to use of a different packet system specific timer within the UE. Whether the UE uses T3396 as a back-off timer or it uses different packet system specific timers as back-off timers is left up to UE implementation. This back-off timer is stopped when the UE is switched off or the USIM is removed. When the back-off timer is running or the timer is deactivated, the UE is allowed to initiate an attach procedure or PDN connectivity procedure if the procedure is for emergency bearer services. If the ESM cause value is #28 "unknown PDN type" and the PDN CONNECTIVITY REQUEST message contained a PDN type IE indicating a PDN connection type, the UE shall ignore the Back-off timer value IE and Re-attempt indicator IE provided by the network, if any. The UE may send another PDN CONNECTIVITY REQUEST message with the PDN type IE indicating another PDN connection type. If the ESM cause value is #50 "PDN type IPv4 only allowed", #51 "PDN type IPv6 only allowed", #57 "PDN type IPv4v6 only allowed", #58 "PDN type non IP only allowed" or #61 "PDN type Ethernet only allowed", the UE shall ignore the Back-off timer value IE provided by the network, if any. The UE shall not automatically send another PDN CONNECTIVITY REQUEST message for the same APN that was sent by the UE to obtain a PDN type different from the one allowed by the network until any of the following conditions is fulfilled: - the UE is registered to a new PLMN, and either the network did not include a Re-attempt indicator IE in the PDN CONNECTIVITY REJECT message or the Re-attempt indicator IE included in the message indicated that re-attempt in an equivalent PLMN is allowed; - the UE is registered to a new PLMN which was not in the list of equivalent PLMNs at the time when the PDN CONNECTIVITY REJECT message was received; - the UE is switched off; or - the USIM is removed. For the ESM cause values #50 "PDN type IPv4 only allowed", #51 "PDN type IPv6 only allowed", #57 "PDN type IPv4v6 only allowed", #58 "PDN type non IP only allowed" and #61 "PDN type Ethernet only allowed", the UE shall ignore the value of the RATC bit in the Re-attempt indicator IE provided by the network, if any. NOTE 5: For the ESM cause values #50 "PDN type IPv4 only allowed", #51 "PDN type IPv6 only allowed", #57 "PDN type IPv4v6 only allowed", #58 "PDN type non IP only allowed" and #61 "PDN type Ethernet only allowed", re-attempt in A/Gb, Iu, or N1 mode for the same APN (or no APN, if no APN was indicated by the UE) is only allowed using the PDN type(s) indicated by the network. Furthermore as an implementation option, for the SM cause values #50 "PDN type IPv4 only allowed", #51 "PDN type IPv6 only allowed", #57 "PDN type IPv4v6 only allowed", #58 "PDN type non IP only allowed" and #61 "PDN type Ethernet only allowed", if the network does not include a Re-attempt indicator IE the UE may decide not to automatically send another PDN CONNECTIVITY REQUEST message for the same APN that was sent by the UE using the same PDN type, if the UE is registered to a new PLMN which is in the list of equivalent PLMNs. NOTE 6: Request to send another PDN CONNECTIVITY REQUEST message with a specific PDN type has to come from upper layers. If the ESM cause value is #65 "maximum number of EPS bearers reached", the UE shall determine the PLMN's maximum number of EPS bearer contexts in S1 mode (see clause 6.5.0) as the number of active EPS bearer contexts it has. The UE shall ignore the Back-off timer value IE and Re-attempt indicator IE provided by the network, if any. NOTE 7: In some situations, when attempting to establish multiple EPS bearer contexts, the number of active EPS bearer contexts that the UE has when ESM cause #65 is received is not equal to the maximum number of EPS bearer contexts reached in the network. NOTE 8: When the network supports emergency bearer services, it is not expected that ESM cause #65 is returned by the network when the UE requests a PDN connection for emergency bearer services. The PLMN's maximum number of EPS bearer contexts in S1 mode applies to the PLMN in which the ESM cause #65 "maximum number of EPS bearers reached" is received. When the UE is switched off, when the USIM is removed, or when there is a change in the value indicated by the network in the 15 bearers bit of the EPS network feature support IE, the UE shall clear all previous determinations representing PLMNs maximum number of EPS bearer contexts in S1 mode. Upon successful registration with a new PLMN, the UE may clear previous determinations representing any PLMN's maximum number(s) of EPS bearer contexts in S1 mode. If the ESM cause value is #66 "requested APN not supported in current RAT and PLMN combination", the UE shall take different actions depending on the Back-off timer value IE and the Re-attempt indicator IE optionally included: 1) If the PDN CONNECTIVITY REQUEST message was sent standalone, the Back-off timer value IE is not included, and either the Re-attempt indicator IE is not included or the Re-attempt indicator IE is included indicating that re-attempt in an equivalent PLMN is allowed, the UE shall not send another PDN CONNECTIVITY REQUEST message for the same APN in the current PLMN in S1 mode until the UE is switched off or the USIM is removed; 2) if the PDN CONNECTIVITY REQUEST message was sent standalone, the Back-off timer value IE is not included, and the Re-attempt indicator IE is included and indicates that re-attempt in an equivalent PLMN is not allowed, the UE shall not send a PDN CONNECTIVITY REQUEST message for the same APN in any PLMN in the list of equivalent PLMNs in S1 mode until the UE is switched off or the USIM is removed; 3) if the PDN CONNECTIVITY REQUEST message was sent standalone and the Back-off timer value IE is included, the UE shall take different actions depending on the timer value received in the Back-off timer value IE (if the UE is a UE configured to use AC11 β 15 in selected PLMN, exceptions are specified in clause 6.3.6): i) if the timer value indicates neither zero nor deactivated, the UE shall start the back-off timer with the value provided in the Back-off timer value IE for the PLMN and APN combination and shall not send another PDN CONNECTIVITY REQUEST for the same in the current PLMN in S1 mode until the back-off timer expires, the UE is switched off or the USIM is removed; ii) if the timer value indicates that this timer is deactivated, the UE shall not send another PDN CONNECTIVITY REQUEST message for the same APN in the current PLMN in S1 mode until the UE is switched off or the USIM is removed; and iii) if the timer value indicates that this timer is zero, the UE may send a PDN CONNECTIVITY REQUEST message for the same APN in the current PLMN; and 4) if the PDN CONNECTIVITY REQUEST message was sent together with an ATTACH REQUEST, the UE shall take different actions depending on the integrity protection of the ATTACH REJECT message (if the UE is a UE configured to use AC11 β 15 in selected PLMN, exceptions are specified in clause 6.3.6): i) if the ATTACH REJECT message is not integrity protected, regardless whether the Back-off timer IE is included, the UE shall start the back-off timer with a random value from a default range specified in table 11.2.3(see 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13]), and shall not initiate a new attach procedure or send another PDN CONNECTIVITY REQUEST message in the current PLMN in S1 mode with the same APN that was sent by the UE, until the back-off timer expires, the UE is switched off or the USIM is removed; and ii) if the ATTACH REJECT message is integrity protected, the UE shall proceed as follows: a) if the Back-off timer value IE is included and the timer value indicates neither zero nor deactivated, the UE shall start the back-off timer with the value provided in the Back-off timer value IE for the PDN connectivity procedure and PLMN and APN combination and shall not initiate a new attach procedure or send another PDN CONNECTIVITY REQUEST message in the current PLMN in S1 mode with the same APN that was sent by the UE, until the back-off timer expires, the UE is switched off or the USIM is removed; b) if the Back-off timer value IE is included and the timer value indicates that this timer is deactivated, the UE shall not initiate a new attach procedure or send another PDN CONNECTIVITY REQUEST message in the current PLMN in S1 mode with the same APN that was sent by the UE, until the UE is switched off or the USIM is removed; c) if the Back-off timer value IE is included and the timer value indicates that this timer is zero, the UE shall proceed as specified in clause 5.5.1.2.6 item d; d) if the Back-off timer value IE is not included, and either the Re-attempt indicator IE is not included or the Re-attempt indicator IE is included indicating that re-attempt in an equivalent PLMN is allowed, the UE shall not initiate a new attach procedure or send another PDN CONNECTIVITY REQUEST message for the same APN in the current PLMN in S1 mode until the UE is switched off or the USIM is removed; and e) if the Back-off timer value IE is not included, and the Re-attempt indicator IE is included and indicates that re-attempt in an equivalent PLMN is not allowed, the UE shall not initiate a new attach procedure or send a PDN CONNECTIVITY REQUEST message for the same APN in any PLMN in the list of equivalent PLMNs in S1 mode until the UE is switched off or the USIM is removed. NOTE 9: Receiving ESM cause value #66 during an attach procedure without APN is not expected and the UE behaviour is implementation specific. If the network includes the Re-attempt indicator IE indicating that re-attempt in an equivalent PLMN is not allowed, then: - for cases 3.i, 4.i and 4.ii.a the UE shall additionally start a back-off timer with the value provided in the Back-off timer value IE for the PDN connectivity procedure for each combination of a PLMN from the equivalent PLMN list and the APN; and - for cases 3.ii and 4.ii.b the UE shall deactivate the respective back-off timers for the PDN connectivity procedure for each combination of a PLMN from the equivalent PLMN list and the APN. For the ESM cause value #66 "requested APN not supported in current RAT and PLMN combination" the UE shall ignore the value of the RATC bit in the Re-attempt indicator IE provided by the network, if any. As an implementation option, for cases 1, 3.i, 3.ii, 4.iv, 4.v.a and 4.v.b, if the Re-attempt indicator IE is not included, the UE may decide not to automatically send another PDN CONNECTIVITY REQUEST message for the same APN in a PLMN which is in the list of equivalent PLMNs. If the ESM cause value is #54 "PDN connection does not exist", the UE shall ignore the Back-off timer value IE and Re-attempt indicator IE provided by the network, if any, and take different actions as follows: - if the PDN CONNECTIVITY REQUEST message was sent standalone, the UE shall set the request type to "initial request" in the subsequent PDN CONNECTIVITY REQUEST message to establish a PDN connectivity to the same APN; - if the PDN CONNECTIVITY REQUEST message was sent together with an ATTACH REQUEST message, the UE shall set the request type to "initial request" in the PDN CONNECTIVITY REQUEST message which is included in the subsequent ATTACH REQUEST message to establish a PDN connectivity to the same APN. NOTE 10: User interaction is necessary in some cases when the UE cannot re-activate the EPS bearer context(s) automatically. If the PDN connection is for UAS services, and the PDN CONNECTIVITY REJECT message includes the Extended protocol configuration options IE containing the service-level-AA container with the length of two octets , and the service-level-AA container with the length of two octets contains the service-level-AA response parameter with the SLAR field set to "Service level authentication and authorization was not successful or service level authorization is revoked", then the UE supporting UAS services shall consider the UUAA procedure as failed and not attempt to establish a PDN connection for UAS 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 | 6.5.1.4.3 |
6,548 | 5.1.4 Coordination between 5GMM and EMM 5.1.4.1 General | If both 5GMM and EMM are enabled, a UE, operating in single-registration mode, shall maintain one common registration for 5GMM for 3GPP access and EMM. Coordination between 5GMM for 3GPP access and EMM for a UE, which is capable of N1 mode and S1 mode and operates in dual-registration mode, is not needed, except as specified in subclause 4.8.3. The coordination between 5GMM for 3GPP access and EMM in subclauses 5.1.4.2 and 5.1.4.3 only applies to the UEs operating in single-registration mode. Regarding the coordination of "SIM/USIM considered invalid" and "USIM considered invalid for 5GS services" between the various mobility management entities see subclause 5.1.5. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.1.4 |
6,549 | β ReportConfigNR-SL | The IE ReportConfigNR-SL specifies criteria for triggering of a CBR measurement reporting event for NR sidelink communication/discovery. Measurement reporting events are based on CBR measurement results on the corresponding transmission resource pools. These events are labelled CN with N equal to 1 and 2. Event C1: CBR of NR sidelink communication/discovery is above a threshold; Event C2: CBR of NR sidelink communication/discovery is below a threshold; ReportConfigNR-SL information element -- ASN1START -- TAG-REPORTCONFIGNR-SL-START ReportConfigNR-SL-r16 ::= SEQUENCE { reportType-r16 CHOICE { periodical-r16 PeriodicalReportConfigNR-SL-r16, eventTriggered-r16 EventTriggerConfigNR-SL-r16 } } EventTriggerConfigNR-SL-r16::= SEQUENCE { eventId-r16 CHOICE { eventC1 SEQUENCE { c1-Threshold-r16 SL-CBR-r16, hysteresis-r16 Hysteresis, timeToTrigger-r16 TimeToTrigger }, eventC2-r16 SEQUENCE { c2-Threshold-r16 SL-CBR-r16, hysteresis-r16 Hysteresis, timeToTrigger-r16 TimeToTrigger }, ... }, reportInterval-r16 ReportInterval, reportAmount-r16 ENUMERATED {r1, r2, r4, r8, r16, r32, r64, infinity}, reportQuantity-r16 MeasReportQuantity-r16, ... } PeriodicalReportConfigNR-SL-r16 ::= SEQUENCE { reportInterval-r16 ReportInterval, reportAmount-r16 ENUMERATED {r1, r2, r4, r8, r16, r32, r64, infinity}, reportQuantity-r16 MeasReportQuantity-r16, ... } MeasReportQuantity-r16 ::= SEQUENCE { cbr-r16 BOOLEAN, ... } -- TAG-REPORTCONFIGNR-SL-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | β |
6,550 | 9.1.1.2A Applicability and test rules for different TDD-FDD CA configurations and bandwidth combination sets | The performance requirement for TDD-FDD CA CQI tests in Clause 9 are defined independent of CA configurations and bandwidth combination sets specified in Clause 5.6A.1. For UEs supporting different CA configurations and bandwidth combination sets, the applicability and test rules are defined for the tests for 2 DL TDD-FDD CA in Table 9.1.1.2A-1 and for 3 or more DL TDD-FDD CA in Table 9.1.1.2A-2. For simplicity, CA configuration below refers to combination of CA configuration and bandwidth combination set. Table 9.1.1.2A-1: Applicability and test rules for CA UE CQI tests for TDD-FDD CA with 2 DL CCs Table 9.1.1.2A-2: Applicability and test rules for CA UE CQI tests for TDD-FDD CA with 3 or more DL CCs | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 9.1.1.2A |
6,551 | 5.5.2.5 Measurement object addition/modification | The UE shall: 1> for each measObjectId included in the received measObjectToAddModList: 2> if an entry with the matching measObjectId exists in the measObjectList within the VarMeasConfig, for this entry: 3> reconfigure the entry with the value received for this measObject, except for the fields cellsToAddModList, excludedCellsToAddModList, allowedCellsToAddModList, cellsToRemoveList, excludedCellsToRemoveList, allowedCellsToRemoveList, tx-PoolMeasToRemoveList, tx-PoolMeasToAddModList, ssb-PositionQCL-CellsToRemoveList, ssb-PositionQCL-CellsToAddModList, cca-CellsToRemoveList, and cca-CellsToAddModList; 3> if the received measObject includes the cellsToRemoveList: 4> for each physCellId included in the cellsToRemoveList: 5> remove the entry with the matching physCellId from the cellsToAddModList; 3> if the received measObject includes the cellsToAddModList: 4> for each physCellId value included in the cellsToAddModList: 5> if an entry with the matching physCellId exists in the cellsToAddModList: 6> replace the entry with the value received for this physCellId; 5> else: 6> add a new entry for the received physCellId to the cellsToAddModList; 3> if the received measObject includes the excludedCellsToRemoveList: 4> for each pci-RangeIndex included in the excludedCellsToRemoveList: 5> remove the entry with the matching pci-RangeIndex from the excludedCellsToAddModList; NOTE 1: For each pci-RangeIndex included in the excludedCellsToRemoveList that concerns overlapping ranges of cells, a cell is removed from the exclude-list of cells only if all PCI ranges containing it are removed. 3> if the received measObject includes the excludedCellsToAddModList: 4> for each pci-RangeIndex included in the excludedCellsToAddModList: 5> if an entry with the matching pci-RangeIndex is included in the excludedCellsToAddModList: 6> replace the entry with the value received for this pci-RangeIndex; 5> else: 6> add a new entry for the received pci-RangeIndex to the excludedCellsToAddModList; 3> if the received measObject includes the allowedCellsToRemoveList: 4> for each pci-RangeIndex included in the allowedCellsToRemoveList: 5> remove the entry with the matching pci-RangeIndex from the allowedCellsToAddModList; NOTE2: For each pci-RangeIndex included in the allowedCellsToRemoveList that concerns overlapping ranges of cells, a cell is removed from the allow-list of cells only if all PCI ranges containing it are removed. 3> if the received measObject includes the allowedCellsToAddModList: 4> for each pci-RangeIndex included in the allowedCellsToAddModList: 5> if an entry with the matching pci-RangeIndex is included in the allowedCellsToAddModList: 6> replace the entry with the value received for this pci-RangeIndex; 5> else: 6> add a new entry for the received pci-RangeIndex to the allowedCellsToAddModList 3> for each measId associated with this measObjectId in the measIdList within the VarMeasConfig, if any: 4> if the UE does not support Uplink PDCP delay measurements upon MO update; or 4> if the UE supports Uplink PDCP delay measurements upon MO update and if ul-DelayValueConfig or ul-ExcessDelayConfig is not configured for the associated reportConfig: 5> remove the measurement reporting entry for this measId from the VarMeasReportList, if included; 5> stop the periodical reporting timer or timer T321 or timer T322, whichever one is running, and reset the associated information (e.g. timeToTrigger) for this measId; 3> if the received measObject includes the tx-PoolMeasToRemoveList: 4> for each transmission resource pool indicated in tx-PoolMeasToRemoveList: 5> remove the entry with the matching identity of the transmission resource pool from the tx-PoolMeasToAddModList; 3> if the received measObject includes the tx-PoolMeasToAddModList: 4> for each transmission resource pool indicated in tx-PoolMeasToAddModList: 5> if an entry with the matching identity of the transmission resource pool exists in the tx-PoolMeasToAddModList: 6> replace the entry with the value received for this transmission resource pool; 5> else: 6> add a new entry for the received identity of the transmission resource pool to the tx-PoolMeasToAddModList; 3> if the received measObject includes the ssb-PositionQCL-CellsToRemoveList: 4> for each physCellId included in the ssb-PositionQCL-CellsToRemoveList: 5> remove the entry with the matching physCellId from the ssb-PositionQCL-CellsToAddModList; 3> if the received measObject includes the ssb-PositionQCL-CellsToAddModList: 4> for each physCellId included in the ssb-PositionQCL-CellsToAddModList: 5> if an entry with the matching physCellId exists in the ssb-PositionQCL-CellsToAddModList: 6> replace the entry with the value received for this physCellId; 5> else: 6> add a new entry for the received physCellId to the ssb-PositionQCL-CellsToAddModList; 3> if the received measObject includes the cca-CellsToRemoveList: 4> for each physCellId included in the cca-CellsToRemoveList: 5> remove the entry with the matching physCellId from the cca-CellsToAddModList; 3> if the received measObject includes the cca-CellsToAddModList: 4> for each physCellId included in the cca-CellsToAddModList: 5> if an entry with the matching physCellId exists in the cca-CellsToAddModList: 6> replace the entry with the value received for this physCellId; 5> else: 6> add a new entry for the received physCellId to the cca-CellsToAddModList; 2> else: 3> add a new entry for the received measObject to the measObjectList within VarMeasConfig. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.5.2.5 |
6,552 | 5.33.2.2 Support of redundant transmission on N3/N9 interfaces | If the reliability of NG-RAN node, UPF and CP NFs are high enough to fulfil the reliability requirement of URLLC services served by these NFs, but the reliability of single N3 tunnel is considered not high enough, e.g. due to the deployment environment of backhaul network, the redundant transmission may be deployed between PSA UPF and NG-RAN via two independent N3 tunnels, which are associated with a single PDU Session, over different transport layer path to enhance the reliability. SMF may make use of Redundant Transmission Experience analytics provided by NWDAF, as described in clause 6.13 of TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [86], to determine whether redundant transmission for the PDU session of the URLLC shall be performed or (if activated) shall be stopped. To ensure the two N3 tunnels are transferred via disjointed transport layer paths, the SMF or PSA UPF should provide different routing information in the tunnel information (e.g. different IP addresses or different Network Instances), and these routing information should be mapped to disjoint transport layer paths according to network deployment configuration. The SMF indicates NG-RAN and PSA UPF that one of the two CN/AN Tunnel Info is used as the redundancy tunnel of the PDU Session accordingly. The redundant transmission using the two N3/N9 tunnels are performed at QoS Flow granularity and are sharing the same QoS Flow ID. During or after a URLLC QoS Flow establishment, if the SMF decided that redundant transmission shall be performed based on authorized 5QI, NG-RAN node capability, operator configuration and/or Redundant Transmission Experience analytics, the SMF informs the PSA UPF and NG-RAN to perform redundant transmission via N4 interface and N2 information accordingly. In this case, NG-RAN should also provide different routing information in the tunnel information (e.g. different IP addresses), and these routing information should be mapped to disjoint transport layer paths according to network deployment configuration. NOTE 1: The NG-RAN node capability to support the redundant transmission on N3/N9 can be configured in the SMF per network slice or per SMF service area. If duplication transmission is performed on N3/N9 interface, for each downlink packet of the QoS Flow the PSA UPF received from DN, the PSA UPF replicates the packet and assigns the same GTP-U sequence number to them for the redundant transmission. The NG-RAN eliminates the duplicated packets based on the GTP-U sequence number and then forwards the PDU to the UE. For each uplink packet of the QoS Flow the NG-RAN received from UE, the NG-RAN replicates the packet and assigns the same GTP-U sequence number to them for redundant transmission. These packets are transmitted to the PSA UPF via two N3 Tunnels separately. The PSA UPF eliminates the duplicated packet based on the GTP-U sequence number accordingly. NOTE 2: How to realize the sequence number for support of GTP-U duplication over N3/N9 is up to stage 3. NOTE 3: For redundant transmission on N3/N9 interfaces, reordering is not required on the receiver side. The PSA UPF and NG-RAN may transmit packets via one or both of the tunnels per QoS Flow based on SMF instruction. NOTE 4: The AMF selects an SMF supporting redundant transmission based on the requested S-NSSAI and/or DNN. During UE mobility, when the UE moves from NG-RAN supporting redundant transmission to NG-RAN not supporting redundant transmission, the SMF may release the QoS Flow which are subject to redundant transmission. Figure 5.33.2.2-1 illustrates the case that the redundant transmission is performed only on N3 interface. These packets are transmitted to the NG-RAN via two N3 Tunnels separately. The RAN node and PSA UPF shall support the packet replication and elimination function as described above. Figure 5.33.2.2-1: Redundant transmission with two N3 tunnels between the PSA UPF and a single NG-RAN node Two Intermediate UPFs (I-UPFs) between the PSA UPF and the NG-RAN may be used to support the redundant transmission based on two N3 and N9 tunnels between a single NG-RAN node and the PSA UPF. The NG-RAN node and PSA UPF shall support the packet replication and elimination function as described above. Figure 5.33.2.2-2: Two N3 and N9 tunnels between NG-RAN and PSA UPF for redundant transmission In figure 5.33.2.2-2, there are two N3 and N9 tunnels between NG-RAN and PSA UPF for the URLLC QoS Flow(s) of the same PDU Session for redundant transmission established during or after a URLLC QoS Flow establishment. In the case of downlink traffic, the PSA UPF duplicates the downlink packet of the QoS Flow from the DN and assigns the same GTP-U sequence number to them. These duplicated packets are transmitted to I-UPF1 and I-UPF2 via N9 Tunnel 1 and N9 Tunnel 2 separately. Each I-UPF forwards the packet with the same GTP-U sequence number which receives from the PSA UPF to NG-RAN via N3 Tunnel 1 and N3 Tunnel 2 respectively. The NG-RAN eliminates the duplicated packet based on the GTP-U sequence number. In the case of uplink traffic, the NG-RAN duplicates the packet of the QoS Flow from the UE and assigns the same GTP-U sequence number to them. These duplicated packets are transmitted to I-UPF1 and I-UPF2 via N3 Tunnel 1 and N3 Tunnel 2 separately. Each I-UPF forwards the packet with the same GTP-U sequence number which receives from the NG-RAN to PSA UPF via N9 Tunnel 1 and N9 Tunnel 2 respectively. The PSA UPF eliminates the duplicated packets based on the GTP-U sequence number. The I-UPFs inserted on one leg of the redundant paths shall not behave in an UL CL or Branching Point role. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.33.2.2 |
6,553 | 7.3 Decentralised UAV traffic management | The 3GPP system shall enable a UAV to broadcast the following identity data in a short-range area for collision avoidance: [UAV type, current location and time, route data, operating status]. The 3GPP system shall enable UAV to broadcast the identity information which preserves the privacy of the owner of the UAV and the UAV operator. The 3GPP system shall enable a UAV to receive local broadcast communication transport service from other UAV in short range. A UAV shall be able to use a direct UAV to UAV local broadcast communication transport service when served or not served by a 3GPP network. A UAV shall be able to use a direct UAV to UAV local broadcast communication transport service when served or not served by the same 3GPP network. The 3GPP system shall support a direct UAV to UAV local broadcast communication transport service at relative speeds of up to 320kmph. The 3GPP system shall support a direct UAV to UAV local broadcast communication transport service at absolute speeds of up to 160kmph. The 3GPP system shall support a direct UAV to UAV local broadcast communication transport service with variable message payloads of 50-1500 bytes, not including security-related message component(s). The 3GPP system shall support a direct UAV to UAV local broadcast communication transport service which can maintain a separation distance between two UAVs of greater than 50m. The 3GPP system shall support a direct UAV to UAV local broadcast communication transport service which supports a range of up to 600m The 3GPP system shall support a direct UAV to UAV local broadcast communication transport service which supports a range sufficient to give the UAVs ample time to perform manoeuvres to maintain a separation distance of 50m (e.g. 6.5 seconds). The 3GPP system shall support a direct UAV to UAV local broadcast communication transport service which can transmit messages at a frequency of at least 10 messages per second. The 3GPP system shall support a direct UAV to UAV local broadcast communication transport service which can transmit messages with an end-to-end latency of at most 100ms. The 3GPP system shall be able to support direct device connection between UAVs to transmit messages to identity the UAVs. Editorβs note: It is FFS up to which distance the direct device connection needs to support The 3GPP system shall be able to support a UAV to transmit a message to identity the UAV via direct device connection in addition to network connection. The UAS shall be able to locally broadcast its identity and location. NOTE: the locally broadcast information should not expose personally identifiable information to general users. The UAS shall be able to locally broadcast its identity via local broadcast with a rate of at least once per 1s. The UAS shall be able to locally broadcast its identity up to a range of 500m. | 3GPP TS 22.825 | Study on Remote Identification of Unmanned Aerial Systems (UAS) | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 7.3 |
6,554 | 4.3.3.3 UE or network requested PDU Session Modification (home-routed roaming) | The UE or network requested PDU Session Modification procedure (home-routed roaming scenario) is depicted in figure 4.3.3.3-1. Figure 4.3.3.3-1: UE or network requested PDU Session Modification (for home-routed roaming scenario) 1. The procedure is triggered by one of the following events: 1a. (UE or serving network requested) As in step 1a of clause 4.3.3.2 with the addition that: - The V-SMF checks whether it can accept the request from the UE; - The V-SMF invokes an Nsmf_PDUSession_Update Request (SM Context ID, UE request for PDU Session Modification or the QoS modification request from the VPLMN, UE location information, Time Zone, the current Access Type, PCO, [Always-on PDU Session Requested]) service operation to inform the H-SMF to update the PDU Session. The H-SMF responds to the request immediately. If the AMF notified the V-SMF that the access type of the PDU session can be changed, as described in the UE Triggered Service Request procedure in clause 4.2.3.2, the V-SMF shall also indicate that the access type can be changed. The PS Data Off status, if changed, shall be included in PCO (Protocol Configuration Option) in the PDU Session Modification Request message. When PCF is deployed, the SMF shall further report the PS Data Off status to PCF if the PS Data Off event trigger is provisioned, the additional behaviour of SMF and PCF for 3GPP PS Data Off is defined in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. 1b. (HPLMN requested) This step is the same as step 1b in clause 4.3.3.2. If the H-SMF received the indication that the access type of the PDU session can be changed, the H-SMF shall indicate the target access type to the PCF in the Access Type information of the Npcf_SMPolicyControl_Update Request. 1c. (HPLMN requested) This step is the same as step 1c in clause 4.3.3.2. 1d. (HPLMN requested) This step is the same as step 1d in clause 4.3.3.2. 1e. As in step 1e of clause 4.3.3.2 with addition that: - The AMF invokes Nsmf_PDUSession_UpdateSMContext (SM context ID, N2 SM information) and sends it to the V-SMF; - The V-SMF invokes an Nsmf_PDUSession_Update Request (SM context ID, ULI, AN type, QoS Flow to be released) service operation to inform the H-SMF to update the PDU Session. The H-SMF responds to the request immediately. For AN initiated notification control in step 1e of clause 4.3.3.2, the V-SMF includes also QoS Flow notification information as specified in clause 5.7 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. NOTE 1: SM Context ID between AMF and V-SMF and between V-SMF and H-SMF are different. SM Context ID has local significance per SMF instance. 1f. (Slice Replacement) As in step 1h of clause 4.3.3.2 with addition: - When the AMF determines as described in clause 5.15.19 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] that VPLMN S-NSSAI is to be replaced by an Alternative VPLMN S-NSSAI, and/or HPLMN S-NSSAI is to be replaced by an Alternative HPLMN S-NSSAI, the AMF invokes Nsmf_PDUSession_UpdateSMContext (SM context ID, VPLMN S-NSSAI, Alternative VPLMN S-NSSAI, HPLMN S-NSSAI, Alternative HPLMN S-NSSAI) and sends it to the V-SMF. If the AMF determines that the current PDU Session cannot be retained (e.g. the current V-SMF cannot support the Alternative VPLMN S-NSSAI), the AMF includes a release indication. - If Alternative HPLMN S-NSSAI is received from the AMF, the V-SMF invokes an Nsmf_PDUSession_Update Request (SM context ID, HPLMN S-NSSAI, Alternative HPLMN S-NSSAI) service operation to inform the H-SMF. The H-SMF responds to the request immediately. The V-SMF forwards the release indication if it is received from the AMF. 2. This step is the same as steps 2 in clause 4.3.3.2 with the SMF is H-SMF. 3. (UE or serving network requested or HPLMN requested) The H-SMF invokes the Nsmf_PDUSession_Update Request (SM Context ID, QoS profiles, [Alternative QoS profile(s)], Session-AMBR, information needed to build the SM PDU Session Modification Command message towards the UE including the QoS rule(s) and QoS Flow level QoS parameters if needed for the QoS Flow(s) associated with the QoS rule(s) and QoS rule operation and the QoS Flow level QoS parameters operation) service operation to the V-SMF. Based on operator policies and roaming agreements, the V-SMF may decide to fully accept or reject the QoS information provided by the H-SMF. The V-SMF shall also be able to accept a subset of the QoS flows requested to be created or modified within a single H-SMF request i.e. V-SMF can accept some QoS flows and reject other QoS flows in same response to H-SMF. If an Always-on PDU Session Granted indication was provided by the H-SMF to indicate that the PDU Session is to be changed to an always-on PDU Session, the V-SMF decides whether to accept or reject the request from the H-SMF based on local policies. For network slice replacement, based on the information received from the V-SMF, the H-SMF determines whether to retain the PDU Session as described in clause 5.15.19 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If the H-SMF decides to retain the PDU Session, the H-SMF includes the Alternative HPLMN S-NSSAI and a cause value indicating that the PDU Session is to be retained in the Nsmf_PDUSession_Update Request message. For SSC mode 3 PDU Session if the H-SMF decides to establish a new PDU Session on the Alternative HPLMN S-NSSAI, the H-SMF includes Alternative HPLMN S-NSSAI and a cause value indicating that a new PDU Session re-establishment on the Alternative HPLMN S-NSSAI is required in the Nsmf_PDUSession_Update Request message. For SSC mode 1 and SSC mode 2 PDU session if the H-SMF decides to establish a new PDU Session on the HPLMN Alternative S-NSSAI, the H-SMF initiates release of the PDU Session as described in clause 4.3.4.3. 3a-3b (HPLMN requested) These steps are executed if new QoS Flow(s) are to be created. The SMF updates the UPF with UL Packet Detection Rules of the new QoS Flow. These steps are executed if the HPLMN S-NSSAI is replaced by an Alternative HPLMN S-NSSAI and the PDU Session is retained. The SMF updates the UPF with Alternative S-NSSAI. NOTE 2: This allows the UL packets with the QFI of the new QoS Flow to be transferred. 4a-4b. These steps are the same as step 3a-3b in clause 4.3.3.2 but controlled from the V-SMF. The V-SMF uses the information received in step 3 to generate any N1 and/or N2 signalling to be sent towards the UE and/or the (R)AN. For network slice replacement in step 1f, the following applies: - If the PDU Session is to be retained and only the VPLMN S-NSSAI is to be replaced by an Alternative VPLMN S-NSSAI, the V-SMF includes Alternative VPLMN S-NSSAI in the N1 PDU Session Modification Command message and a cause value to notify the UE that the VPLMN S-NSSAI of the PDU Session is replaced with the Alternative VPLMN S-NSSAI. The V-SMF also set the S-NSSAI in N2 SM information to Alternative VPLMN S-NSSAI. - If the PDU Session is to be retained and only the HPLMN S-NSSAI is to be replaced by an Alternative HPLMN S-NSSAI, the V-SMF includes Alternative HPLMN S-NSSAI in the N1 PDU Session Modification Command message and a cause value to notify the UE that the HPLMN S-NSSAI is replaced with the Alternative HPLMN S-NSSAI - If the PDU Session is to be retained and both VPLMN S-NSSAI and HPLMN S-NSSAI are to be replaced, the V-SMF includes Alternative HPLMN S-NSSAI and VPLMN Alternative S-NSSAI in the N1 PDU Session Modification Command message and a cause value to notify the UE that the HPLMN S-NSSAI is replaced with the Alternative HPLMN S-NSSAI and the VPLMN S-NSSAI of the PDU Session is replaced with Alternative VPLMN S-NSSAI. The V-SMF sets the S-NSSAI in N2 SM information to Alternative VPLMN S-NSSAI. - If a new PDU Session establishment is required, the V-SMF includes Alternative HPLMN S-NSSAI and/or Alternative VPLMN S-NSSAI in the N1 PDU Session Modification Command message and a cause value to notify the UE that a new PDU Session establishment on the HPLMN Alternative S-NSSAI and/or Alternative VPLMN S-NSSAI is required. 5-7. These steps are the same as step 4-6 in clause 4.3.3.2. 8. This step is the same as step 7a in clause 4.3.3.2 with the difference that the SMF is V-SMF. If the N2 SM information indicates modification failure and the V-SMF rejected the PDU session modification as described in step 7 in clause 4.3.3.2, step 9 is skipped. 9a-9b are the same as step 8a-8b in clause 4.3.3.2 but executed in Visited PLMN 10. This step is the same as step 7b in clause 4.3.3.2 with the difference that the SMF is V-SMF. 11-12. These steps are the same as steps 8-9 in 4.3.3.2. 13-14. These steps are the same as step 11a-11b in clause 4.3.3.2 but executed in Visited PLMN. 15. V-SMF responds to the H-SMF with an Nsmf_PDUSession_Update response carrying the information like PCO provided by the UE in the SM PDU Session Modification Command Ack message from the UE to the V-SMF, Secondary RAT usage data. The H-SMF shall modify the PDU Session context. If the V-SMF has rejected QFI(s) (step3) or the (R)AN has rejected QFI(s) in step 6 of Figure 4.3.3.2-1, the H-SMF is responsible of later updating the QoS rules and QoS Flow level QoS parameters if needed for the QoS Flow(s) associated with the QoS rule(s) in the UE. 16-17. These steps are the same as steps 12-13 in clause 4.3.3.2 with the difference that the SMF is H-SMF. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.3.3.3 |
6,555 | 4.4.7 eCall inactivity procedure | The eCall inactivity procedure is applicable only to an eCall only mobile station (as determined by information configured in USIM). The procedure shall be started when: - the mobile station is in any MM Idle state except NO IMSI, NO CELL AVAILABLE or PLMN SEARCH; - the mobile station is in GMM-NULL or GMM-DEREGISTERED state; and - one of the following conditions applies: - timer T3242 expires or is found to have already expired and T3243 is not running; - timer T3243 expires or is found to have already expired and T3242 is not running; or - timer T3242 and timer T3243 expire or are found to have already expired. The mobile station shall then stop other running timers (e.g. T3211, T3212, T3213) and shall perform the IMSI detach procedure if required by the serving network and if the update state is U1. The mobile station then enters MM Idle eCALL INACTIVE state and the mobile station shall delete any LAI, TMSI, ciphering key sequence number stored in the SIM/USIM and set the update state to U4 Updating Disabled. While in eCALL INACTIVE state, the mobile station maintains awareness of a potential serving cell in a potential serving network but initiates no MM signalling with the network and ignores any paging requests. The mobile station shall leave eCALL INACTIVE state only when one of the following events occur: - if the SIM or USIM is removed, the mobile station enters the NO IMSI state; - if coverage is lost, the mobile station enters PLMN SEARCH state; - if the mobile station is deactivated (e.g. powered off) by the user: the mobile station enters the NULL state; - if there is a CM request for an emergency services call: the mobile station should follow the procedure for return to state MM-IDLE in subclause 4.2.3 and attempt a location update. The MS then uses the MM and CM procedures to establish the emergency call at the earliest opportunity; or NOTE 1: If an eCall only device has not successfully completed a location update procedure, PSAP callback will not be possible due to its calling line identity being unavailable at the PSAP. NOTE 2: An eCall only device uses the CS domain to originate an emergency services call when in A/Gb or Iu mode, even if the device is capable of eCall over IMS. - if there is a CM request for a call to an HPLMN designated non-emergency MSISDN for the purpose of accessing test and terminal reconfiguration services: the mobile station follows the procedure for return to state MM-IDLE in subclause 4.2.3 and attempts a normal location update. Once this is complete, further MM and CM procedures are used to establish the non-emergency call. NOTE 3: An eCall only device uses the CS domain to originate a call to an HPLMN designated non-emergency MSISDN for the purpose of accessing test and terminal reconfiguration services when in A/Gb or Iu mode, even if the device is capable of eCall over IMS. | 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.4.7 |
6,556 | 10.19.1 EN-DC | The Conditional Handover with Secondary Node procedure is used for configuration and execution of CHO with SN. This procedure includes the cases where the SN is kept, changed or added. If the SN is kept, the UE context at the SN is kept. If the SN is changed, the UE context at the source SN is moved to the target SN. Figure 10.19.1-1: Conditional Handover with Secondary Node procedure Figure 10.19.1-1 shows an example signaling flow for Conditional Handover with Secondary Node. NOTE 1: For a CHO without SN change, the source SN and the target SN shown in Figure 10.19.1-1 are the same node. NOTE 2: For a CHO with SN addition, the source SN and steps involving the source SN in Figure 10.19.1-1 are ignored. 1. The source MN starts the conditional handover procedure by initiating the X2 Handover Preparation procedure including MCG configuration and, if the UE is configured with an SCG, SCG configuration. The source MN may include the (source) SN UE X2AP ID, SN ID, the UE context in the (source) SN and the Conditional Handover Information Request IE in the Handover Request message. NOTE 3: In case of the CHO with/without SN change, the source MN may trigger the MN-initiated SN Modification procedure (to the source SN) to retrieve the current SCG configuration, if configured, before step 1. 2. If the candidate MN decides to keep the UE context in the SN, the candidate MN sends the SgNB Addition Request message to the SN including the SN UE X2AP ID as a reference to the UE context in the SN that was established by the source MN. If the candidate MN decides to change the SN allowing delta configuration, the candidate MN sends the SgNB Addition Request message to the candidate SN including the UE context in the source SN that was established by the source MN. Otherwise, the candidate MN may send the SgNB Addition Request message to the candidate SN including neither the SN UE X2AP ID nor the UE context in the source SN that was established by the source MN. Within the SgNB Addition Request message, the candidate MN also includes the CHO related information, i.e., the source MN ID and the MN UE X2AP ID in the source MN, in order to indicate that the SgNB Addition Preparation procedure is triggered in relation to a CHO and to enable the SN to identify requests related to the same UE. NOTE 3a: The target MN and other potential target MNs may trigger the SgNB Addition Preparation procedure to the same (target) SN. NOTE 3b: The source MN may initiate additional X2 Handover Preparation procedures towards the same or other target MNs. Based on each X2 Handover Preparation procedure, each target MN may decide to trigger SgNB Addition Preparation procedure. 3. The (candidate) SN replies with the SgNB Addition Request Acknowledge message. The (candidate) SN may include the indication of full or delta RRC configuration. NOTE 4: In CHO with SCG configuration, it is up to the candidate MN implementation to make sure that the CG-Config provided from the (candidate) SN can be used in all CHO preparations. 4. The candidate MN includes within the Handover Request Acknowledge message a transparent container to be sent to the UE as an RRC message to perform the conditional handover, and may also provide forwarding addresses to the source MN. The candidate MN indicates to the source MN that the UE context in the SN is kept if the candidate MN and the SN decided to keep the UE context in the SN in step 2 and step 3. NOTE 4a0: Steps 1-4 may be produced in several instances, each instance initiated with a separate Handover Preparation procedure (step 1). The order of messages belonging to separate instances is not defined. 4a. The source MN sends the Data Forwarding Address Indication message to the (source) SN. This Data Forwarding Address Indication message notifies conditional handover to the (source) SN, which may decide to perform, if applicable, early data forwarding for SN-terminated bearers, together with the sending of an Early Status Transfer message to the source MN. NOTE 4a: Separate Data Forwarding Address Indication procedures may be initiated to provide different forwarding addresses of the prepared conditional handovers. In this case, it is up to the source MN and SN implementations to make sure that the Early Status Transfer message(s) from the source SN, if any, is forwarded to the right target MN. The Data Forwarding Address Indication procedure may further be initiated to indicate to the (source) SN to stop already initiated early data forwarding for some SN-terminated bearers, if they are no longer subject to data forwarding due to the modification or cancellation of the prepared conditional handovers. 5. The source MN sends an RRCConnectionReconfiguration message to the UE, including the CHO configuration, i.e. a list of RRCConnectionReconfiguration* messages and associated execution conditions, in which each RRCConnectionReconfiguration* message contains an MCG configuration and possibly an SCG configuration in the RRCReconfiguration** message received from the candidate SN in step 3. 6. The UE applies the RRCConnectionReconfiguration message received in step 5, stores the CHO configuration and replies to the MN with an RRCConnectionReconfigurationComplete message. 7/8. The UE maintains connection with the source MN and, if the UE is configured with a PSCell, with the source PSCell, after receiving CHO configuration, and starts evaluating the CHO execution condition for the candidate cell(s). If at least one CHO candidate cell satisfies the corresponding CHO execution condition, the UE detaches from the source MN, applies the stored corresponding configuration for that selected candidate cell, synchronises to that candidate cell and completes the RRC handover procedure by sending RRCConnectionReconfigurationComplete* message to the target MN. If the stored configuration for the selected candidate cell includes an SCG configuration, the UE includes an embedded SN RRCReconfigurationComplete** message for the target SN. The UE releases stored CHO configurations after successful completion of RRC handover procedure. NOTE 5: In case the target SN includes the indication of full RRC configuration, the MN performs release of the SN terminated radio bearer configuration and release and add of the NR SCG configuration part towards the UE. 9. If configured with bearers requiring SCG radio resources, the UE synchronizes to the (target) SN. NOTE 6: The order the UE performs Random Access towards the MN (step 7) and performs the Random Access procedure towards the (target) SN (step 9) is not defined. 10. If the RRC connection reconfiguration procedure was successful, the target MN informs the (target) SN via SgNB Reconfiguration Complete message. 11. The target MN sends the Handover Success message to the source MN to inform that the UE has successfully accessed the target cell. 12a/b. The source MN sends SgNB Release Request message to the (source) SN including a Cause indicating MCG mobility and, if applicable, data forwarding information. The source MN indicates to the (source) SN that the UE context in SN is kept, if it receives the indication from the target MN. The (source) SN acknowledges the release request. 12c. The source MN sends the Handover Cancel message toward the other signalling connections or other candidate MNs, if any, to cancel CHO for the UE. 12d/e. If the target MN is configured with other candidate PCell(s) associated with other candidate SN(s) than the target SN, the target MN sends the SgNB Release Request message(s) to the corresponding candidate SN(s). Other candidate MN(s) send(s) the SgNB Release Request message(s) to other candidate SN(s), if configured. The other candidate SN(s) acknowledges the release request. 13a. The (source) SN sends the Secondary RAT Data Usage Report message to the source MN and includes the data volumes delivered to and received from the UE over the NR radio for the related E-RABs. NOTE 7: The order the source SN sends the Secondary RAT Data Usage Report message and performs data forwarding with MN/target SN is not defined. The SgNB may send the report when the transmission of the related bearer is stopped. 13b. The source MN sends the Secondary RAT Data Usage Report message to MME to provide information on the used NR resource. 14. For bearers using RLC AM, the source MN sends the SN Status Transfer message, including, if needed, SN Status received from the source SN to the target MN. The target MN forwards the SN Status to the target SN, if needed. 15. If applicable, data forwarding takes place from the source side (i.e. source MN or source SN). If the SN is kept, data forwarding may be omitted for SN-terminated bearers kept in the SN. 16-19. The target MN initiates the S1 Path Switch procedure. NOTE 8: If new UL TEIDs of the S-GW are included, the target MN performs the MN initiated SN Modification procedure to provide them to the SN. 20. The target MN initiates the UE Context Release procedure towards the source MN. 21. Upon reception of the UE Context Release message, the (source) SN releases C-plane related resources associated to the UE context towards the source MN. Any ongoing data forwarding may continue. The SN shall not release the UE context associated with the target MN if the UE context kept indication was included in the SgNB Release Request message in step 12a. | 3GPP TS 37.340 | Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Overall Description; Stage-2 | RAN2 | 3GPP Series : 37 , Multiple radio access technology aspects | 10.19.1 |
6,557 | 5.3.6.2.2.1 Fallback to speech | If modem handshaking fails (in a modem call), the call mode will be modified to speech if a speech bearer capability IE was included. The modem signalling is inband, so the call must have reached the active state, when these conclusions about the presence of modems can be done. The call modifications are realized through the in-call modification procedure, by which the network requests the MS to modify the call mode (see subclause 5.3.4.3). NOTE: Fallback from digital (UDI) H.324-call to speech after call setup is not a valid case at the terminating side. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.3.6.2.2.1 |
6,558 | 5.2.26.2 Nupf_EventExposure Service 5.2.26.2.1 General | Service description: This service can expose UPF related information to other NFs. There are several operations for this service: - Notifying events on the PDU Session to the NFs. - Allow consumer NFs to subscribe and unsubscribe for an Event ID on UPF. The following events can be notified to a NF consumer: - QoS Monitoring. This event provides QoS Flow level performance information and can be used for direct event notification of QoS Monitoring reports to a different NF than the SMF as defined in clause 5.8.2.18 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], or it may be for UPF Data collection by NWDAF for analytics (see TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [50]) as described in clause 4.15.4.5. Subscription to this event is always indirect via SMF. The subscription specifies the type of measurement that is being requested. A combination of the information listed below can be requested. UPF and SMF interact using Session Reporting Rules as defined in clause 5.8.5.11 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The event notification may contain following information: - QoS monitoring result for the QoS parameter(s) to be measured defined in clause 5.45 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], e.g. UL packet delay, DL packet delay, or round trip packet delay. - Indication of QoS Flow associated with the default QoS Rule (if requested by SMF, see clause 4.15.4.5.1). - UserDataUsageMeasures. This event provides information of user data usage of the User PDU Session. It can be used for UPF Data Collection by NWDAF for analytics (see TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [50]) as described in clause 4.15.4.5. SMF and other allowed direct consumers shall use Service Based Interface subscription service operation to subscribe this UPF event. The subscription request specifies type of measurement that is being requested and for which target traffic, which is either the whole PDU Session or traffic identified by either Application Id or traffic filter information and the required granularity for the information reported. A combination of the information listed below can be requested. The event notification may contain following information: - Volume Measurement: measures of data volume exchanged (UL, DL and/or overall) and/or number of packets exchanged (UL, DL and/or overall) with or without application granularity. - Throughput Measurement: measures of data throughput (UL and DL) measures aggregated for the PDU Session or per application. - Application related Information: URL/s and/or Domain information (domain name and protocol) detected for the target traffic. When the subscription requests that information is provided per data flow, the notification includes the packet filter set and the Applications Identifier if available. - UserDataUsageTrends. This event provides statistical measurements. It can be used for UPF Data Collection by NWDAF for analytics (see TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [50]) as described in clause 4.15.4.5. SMF and other allowed direct consumers shall use SBI subscription operation to subscribe this UPF event. The subscription specifies for which target traffic the information is requested, which is either the whole PDU Session or traffic identified by either Application Id or traffic filter information and the required granularity for the information reported. The event notification may contain following information: - Throughput Statistic Measurement (average and/or peak throughput) over the measurement period for the PDU Session or per application. When the subscription requests that information is provided per data flow, the notification includes the packet filter set and the Applications Identifier if available. - TSC management information (UMIC, PMIC, NW-TT port number) as defined in clause 5.8.5.14 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. TSC management information event can be the result of an implicit subscription of the PCF on behalf of the TSNAF/TSCTSF via the Npcf_SMPolicyControl service as described in clause 5.28 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If the consumer of UPF service is NWDAF and the target of UE is any UE, according to the Analytic ID from consumer, the NWDAF can decide which kind of information should be collect from UPF and event ID to use. Subscription may be performed directly towards UPF or via SMF as described in clause 4.15.4.5. The UPF collects the data according to the event ID and exposes the related information directly regardless of whether the subscription has been relayed by the SMF. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.26.2 |
6,559 | 4.16.12.1.1 UE Policy Association Modification initiated by the AMF without AMF relocation | This procedure addresses the scenario where a Policy Control Request Trigger condition is met. Figure 4.16.12.1.1-1: UE Policy Association Modification initiated by the AMF This procedure concerns both roaming and non-roaming scenarios. In the non-roaming case the V-PCF is not involved. In the roaming case, the AMF interacts with the V-PCF and the H-PCF interacts with the V-PCF. 1. When a Policy Control Request Trigger condition is met the AMF updates UE Policy Control Association and provides information on the conditions that have changed to the PCF. The AMF sends a Npcf_UEPolicyControl Update Request with the following information: UE Policy Association ID associated with the SUPI defined in TS 29.525[ 5G System; UE Policy Control Service; Stage 3 ] [58] and the Policy Control Request Trigger met. In roaming scenario, based on operator policies, the AMF may provide to the V-PCF the PCF ID of the selected H-PCF. The V-PCF contacts the H-PCF. See clause 6.1.2.5 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20] and clause 4.2.3.2 of TS 29.525[ 5G System; UE Policy Control Service; Stage 3 ] [58] for more details on Policy Control Request Trigger. In the roaming case, steps 2 and 3 are executed, otherwise step 4 follows. 2. The V-PCF forwards the information received from AMF in step 1 to the (H-)PCF. 3. The H-PCF replies to the V-PCF. In the non-roaming case, the PCF may subscribe to Analytics from NWDAF as defined in clause 6.1.1.3 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. 4. The (V-) PCF sends a Npcf_UEPolicyControl Update Response to the AMF. 5. The (H-)PCF may create the UE policy container including UE policy information as defined in clause 6.6 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. In the case of roaming the H-PCF may include the UE policy container in the Npcf_UEPolicyControl UpdateNotify Request. 6. The (V-)PCF sends a response to H-PCF using Npcf_UEPolicyControl UpdateNotify Response. Steps 7, 8 and 9 are the same as steps 8, 9 and 10 of procedure UE Policy Association Establishment in clause 4.16.11. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.16.12.1.1 |
6,560 | 4.7.3.1.2 GMM common procedure initiation | If the network receives an ATTACH REQUEST message containing the P-TMSI type IE and the Mobile identity IE with type of identity indicating "TMSI/P-TMSI/M-TMSI", and the network does not follow the use of the most significant bit of the LAC as specified in 3GPP TS 23.003[ Numbering, addressing and identification ] [10] subclause 2.8.2.2.2, the network shall use the P-TMSI type IE to determine whether the mobile identity included in the Mobile identity IE is a native P-TMSI or a mapped P-TMSI. The network may initiate GMM common procedures, e.g. the GMM identification and GMM authentication and ciphering procedure, depending on the received information such as IMSI, CKSN, old RAI, P-TMSI and P-TMSI signature. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.7.3.1.2 |
6,561 | 5.2.21.2.2 Nnsacf_NSAC_NumOfUEsUpdate service operation | Service Operation name: Nnsacf_NSAC_NumOfUEsUpdate Description: Updates the number of UEs registered with a network slice (e.g. increase or decrease) when the UE registration status for a network slice subject to NSAC has changed. Also, if the number of the UEs registered with the network slice is to be increased and the Early Admission Control (EAC) mode in the NSACF is activated for that network slice (see Nnsacf_NSAC_EACNotify service operation), the NSACF first checks whether the number of UEs registered with the network slice has reached the maximum number of UEs per network slice threshold. If the maximum number of UEs registered with the network slice has already been reached, the UE registration for that network slice via the same Access Type configured in the NSACF is rejected. If the EAC is not activated, the NSACF increases or decreases the number of UEs per network slice as per the input parameters below. Inputs, Required: S-NSSAI(s), UE ID (SUPI), NF ID, Access Type, update flag. Inputs, Optional: None. Inputs, Conditional: Notification endpoint for EAC Notification for the S-NSSAI, NSAC admission mode, PLMN ID, UE already registered indication, AMF NSAC service area. The S-NSSAI(s) parameter is a list of one or more network slices for which the number of UEs registered with a network slice is to be updated and checked if the maximum number of UEs per network slice threshold has already been reached. In the roaming case, the corresponding mapped S-NSSAI(s) of the HPLMN is also included. The UE ID parameter is used by the NSACF to maintain a list of UE IDs registered with the network slice. The NSACF also takes Access Type into account for increasing and decreasing the number of UEs per network slice as described in clause 5.15.11.1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The NF ID parameter is the NF instance ID of the NF (e.g. AMF or SMF + PGW-C) sending the request to the NSACF. The update flag input parameter indicates whether the number of UEs registered with a network slice is to be: - increased when the UE registers to a new network slice subject to NSAC. If the UE ID is already in the list of UEs registered with the network slice, the number of UEs registered with the network slice is not increased as the UE has already been counted as registered with the network slice. If the UE ID is not in the list of UE IDs registered with the network slice and the maximum number of UEs registered with the network slice has not been reached yet, the NSACF adds the UE ID in the list of UEs registered with the network slice and increases the number of the UEs registered with the network slice. If the UE_ID is not in the list of UEs registered with that S-NSSAI and the maximum number of UEs per network slice for that S-NSSAI has already been reached, then the NSACF returns maximum number of UEs per network slice reached result; - decreased when the UE deregisters for a network slice that is subject to NSAC. The NSACF decreases the number of the UEs registered with the network slice and removes the UE ID from the list of UEs registered with the network slice; - updated when the UE moves the PDU sessions across Access Types as described in the clause 4.11.5.9a. NSAC admission mode applies to inbound roamers. It is included by NF consumer to indicate applicable NSAC admission mode in VPLMN. Its values can be VPLMN NSAC admission mode, or VPLMN with HPLMN assistance NSAC admission mode. The PLMN ID is the serving PLMN of the UE. The UE already registered parameter indicates that the UE has already been registered in another NSACF service area. The AMF NSAC service area is included in a centralized NSAC architecture, if available. The NSACF may optionally return the current status of the network slice availability (e.g. a percentage out of the maximum number of UEs registered with a network slice) in the availability status parameter. This information may be used for NSACF signalling and load balancing in case multiple NSACFs are serving the same network slice. Outputs, Required: Result indication. The Result indication parameter contains the outcome of the update and check operation in the NSACF and may indicate one of the values 'maximum number of UEs for the S-NSSAI not reached' or 'maximum number of UEs for the S-NSSAI reached'. Outputs, Optional: Updated local maximum number of registered UEs, or Updated UE admission threshold. These parameters can only be returned by a primary NSACF. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.21.2.2 |
6,562 | 8.12.2 NSA IAB Integration procedure | The IAB integration procedure for NSA is shown in Figure 8.12.2-1. Figure 8.12.2-1: Signalling flow for IAB integration procedure in NSA Phase 1-1. IAB-MT part setup with E-UTRAN. In this phase, the IAB-MT part connects to the LTE network as a UE, by performing RRC connection setup procedure with an eNB, authentication with the EPC, IAB-nodeβs access traffic-related radio bearer configuration at the E-UTRAN side, and optionally, OAM connectivity establishment by using the IAB-MTβs PDN connection. The IAB-node can select the IAB-supporting eNB based on an over-the-air indication from eNB (transmitted in SIB1). To indicate its IAB capability, the IAB-MT includes the IAB-node indication in RRCConnectionSetupComplete message, to assist the eNB to select an MME supporting IAB. The eNB then configures the IAB-MT part with an NR measurement configuration in order to perform discovery, measurement and measurement reporting of candidate gNBs. To enable the eNB choose an en-gNB which supports IAB function, the IAB capability of neighbour gNBs can be pre-configured in the eNB (e.g. by OAM). NOTE: Other ways to enable the eNB know the IAB capability of neighbour gNBs are not precluded. Phase 1-2. SgNB addition. In this phase, the IAB-MT part connects to the parent node IAB-DU and IAB-donor-CU via the EN-DC SgNB Addition procedure. The procedure defined in clause 8.4.1 is reused. The eNB includes βIAB Node Indicationβ in SGNB ADDITION REQUEST message to inform the IAB-donor-CU that the request is for an IAB-node. In addition, SRB3 can be set up for the IAB-MT, to transmit RRC message between the IAB-MT and the IAB-donor-CU via the NR links directly. Phase 2-1: BH RLC channel establishment. This phase is the same as Phase 2-1 in the standalone IAB integration procedure (refer to the Phase 2-1 in clause 8.12.1). This step may occur in Phase 1-2. Phase 2-2: Routing update. This phase is the same as Phase 2-2 in the standalone IAB integration procedure (refer to the Phase 2-2 in clause 8.12.1), except that the IP traffic on the F1-C interface may be transmitted via the MeNB. Phase 3. IAB-DU part setup. This phase is the same as Phase 3 in the standalone IAB integration procedure (refer to the Phase 3 in clause 8.12.1), except that the IP traffic on the F1-C interface may be transmitted via the MeNB. The IAB-donor-CU decides to only configure LTE leg, or only to configure NR leg, or to configure both LTE leg and NR leg, to be used for F1-C traffic transfer. The configuration may be performed before IAB-DU part setup. IAB-donor-CU may also change the configuration after IAB-DU part setup. In case the configuration is not performed before IAB-DU part setup, the IAB node uses the NR leg as the default one. When both LTE leg and NR leg are configured, it is up to the implementation to select the leg for F1-C traffic transfer. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 8.12.2 |
6,563 | 5.3.5 S1 release procedure | This procedure is used to release the logical S1-AP signalling connection (over S1-MME) and all S1 bearers (in S1-U) for a UE. This Procedure releases the S11-U bearer in Control Plane CIoT EPS Optimisation (except in the case of buffering in MME), instead of the S1-U bearer. The procedure will move the UE from ECM-CONNECTED to ECM-IDLE in both the UE and MME, and all UE related context information is deleted in the eNodeB. When the S1-AP signalling connection is lost, e.g. due to loss of the signalling transport or because of an eNodeB or MME failure, the S1 release procedure is performed locally by the eNodeB and by the MME. When the S1 release procedure is performed locally by the eNodeB or by the MME each node performs locally its actions as described in the procedure flow below without using or relying on any of the signalling shown directly between eNodeB and MME. If Service Gap Control shall be applied for the UE (see clause 4.3.17.9) and the Service Gap timer is not already running, the Service Gap timer shall be started in MME and UE when entering ECM-IDLE, unless the connection was initiated after a paging of an MT event, or after a TAU procedure without any active flag set or signalling active flag set. The initiation of S1 Release procedure is either: - eNodeB-initiated with cause e.g. O&M Intervention, Unspecified Failure, User Inactivity, Repeated RRC signalling Integrity Check Failure, Release due to UE generated signalling connection release, CS Fallback triggered, Inter-RAT Redirection, UE using satellite access moved out of PLMN serving area, etc. as defined in TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [36]; or - MME-initiated with cause e.g. authentication failure, detach, not allowed CSG cell (e.g. the CSG ID of the currently used CSG cell expires or is removed from the CSG subscription data), etc. Both eNodeB-initiated and MME-initiated S1 release procedures are shown in Figure 5.3.5-1. Figure 5.3.5-1: S1 Release Procedure 1a. In certain cases the eNodeB may release the UE's signalling connection before or in parallel to requesting the MME to release the S1 context, e.g. the eNodeB initiates an RRC Connection Release for CS Fallback by redirection. If the reason for the release is that the eNodeB received Release Assistance Indicator in Access Stratum as defined in TS 36.321[ Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification ] [87], the eNodeB should not immediately release the RRC connection, instead send S1 UE context Release Request with appropriate cause value e.g. user inactivity. 1b. If the eNodeB detects a need to release the UE's signalling connection and all radio bearers for the UE, the eNodeB sends an S1 UE Context Release Request (Cause) message to the MME. Cause indicates the reason for the release (e.g. O&M intervention, unspecified failure, user inactivity, repeated integrity checking failure, or release due to UE generated signalling connection release). If the PLMN has configured secondary RAT reporting and the eNodeB has Secondary RAT usage data to report, the Secondary RAT usage data is included in S1 UE Context Release Request. NOTE 1: Step 1 is only performed when the eNodeB-initiated S1 release procedure is considered. Step 1 is not performed and the procedure starts with Step 2 when the MME-initiated S1 release procedure is considered. The MME upon receiving S1 UE Context Release Request with Cause=user inactivity continues with the S1 release procedure unless the MME is aware of pending MT traffic or signalling and/or NAS Release Assistance Information that may have been received in NAS PDU when Control Plane CIoT EPS Optimisation is used, which indicates that downlink data is expected. The MME upon receiving S1 UE Context Release Request with Cause indicating the release is requested due to a UE using satellite access moved out of PLMN serving area, may detach the UE as described in clause 5.3.8.3 before continuing with the S1 Release procedure. For Control Plane CIoT EPS Optimisation with data buffering in the MME, step 2 and step 3 are skipped. 2. The MME sends a Release Access Bearers Request (Abnormal Release of Radio Link Indication, Secondary RAT usage data) message to the S-GW that requests the release of all S1-U bearers for the UE, or the S11-U in Control Plane CIoT EPS Optimisation if buffering is in the S-GW. This message is triggered either by an S1 Release Request message from the eNodeB, or by another MME event. The Abnormal Release of Radio Link Indication is included if the S1 release procedure is due to an abnormal release of the radio link. If secondary RAT usage data was received in Step 1b, the MME includes Secondary RAT usage data in this message. 3. If the S-GW has received a Release Access Bearers Request, the S-GW releases all eNodeB related information (address and TEIDs), or the MME TEIDs related information in Control Plane CIoT EPS Optimisation (address and TEIDs), for the UE and responds with a Release Access Bearers Response message to the MME. Other elements of the UE's S-GW context are not affected. The S-GW retains the S1-U configuration that the S-GW allocated for the UE's bearers. The S-GW starts buffering downlink packets received for the UE and initiating the "Network Triggered Service Request" procedure, described in clause 5.3.4.3, if downlink packets arrive for the UE. In Control Plane CIoT EPS Optimisation Downlink data triggers Mobile Terminated Data transport in NAS signalling defined in clause 5.3.4B.3. NOTE 2: Based on operator policy any received Indication of "Abnormal Release of Radio Link" may be used by Serving GW in subsequent decisions to trigger PDN charging pause if the feature has been enabled on that PDN. 4. The MME releases S1 by sending the S1 UE Context Release Command (Cause) message to the eNodeB. 5. If the RRC connection is not already released, the eNodeB sends a RRC Connection Release message to the UE in Acknowledged Mode. Once the message is acknowledged by the UE, the eNodeB deletes the UE's context. 6. The eNodeB confirms the S1 Release by returning an S1 UE Context Release Complete (ECGI, TAI, Secondary RAT usage data) message to the MME. With this, the signalling connection between the MME and the eNodeB for that UE is released. This step shall be performed promptly after step 4, e.g. it shall not be delayed in situations where the UE does not acknowledge the RRC Connection Release. If Dual Connectivity was activated by that eNodeB at the time of the release or earlier by that eNodeB, the eNodeB shall include the last known PSCell ID and the time elapsed since the Dual Connectivity was released. If the eNodeB supports WUS, the eNodeB should include the Information On Recommended Cells And eNodeBs For Paging in the S1 UE Context Release Complete message; otherwise, the eNodeB may include the Information On Recommended Cells And eNodeBs For Paging in the S1 UE Context Release Complete message. If available, the MME shall store this information to be used when paging the UE. The eNodeB includes Information for Enhanced Coverage, if available, in the S1 UE Context Release Complete message. If the PLMN has configured secondary RAT usage data reporting, the eNodeB has not included Secondary RAT usage data at step 1b, and the eNodeB has Secondary RAT usage data to report, the Secondary RAT usage data is included in this message. If Secondary RAT usage data was included at step 1b then MME ignores Secondary RAT usage data at step 6. The MME deletes any eNodeB related information ("eNodeB Address in Use for S1-MME", "MME UE S1 AP ID" and "eNodeB UE S1AP ID") from the UE's MME context, but, retains the rest of the UE's MME context including the S-GW's S1-U configuration information (address and TEIDs). All non-GBR EPS bearers established for the UE are preserved in the MME and in the Serving GW. If the cause of S1 release is because of User I inactivity, Inter-RAT Redirection, the MME shall preserve the GBR bearers. If the cause of S1 release is because of CS Fallback triggered, further details about bearer handling are described in TS 23.272[ Circuit Switched (CS) fallback in Evolved Packet System (EPS); Stage 2 ] [58]. Otherwise, e.g. Radio Connection With UE Lost, S1 signalling connection lost, eNodeB failure the MME shall trigger the MME Initiated Dedicated Bearer Deactivation procedure (clause 5.4.4.2) for the GBR bearer(s) of the UE after the S1 Release procedure is completed. NOTE 3: EPC does not support the GPRS preservation feature with setting the MBR for GBR bearers to zero. NOTE 4: The MME can defer the deactivation of GBR bearers for a short period (in the order of seconds) upon receipt of an S1AP UE Context Release Request due to radio reasons, so as to allow the UE to re-establish the corresponding radio and S1-U bearers and thus avoid deactivation of the GBR bearers. If LIPA is active for a PDN connection, the HeNB informs the collocated L-GW by internal signalling to releases the direct user plane path to the HeNB. After the direct user plane path is released, if downlink packets arrive for the UE, the L-GW forwards the first packet on the S5 tunnel to the S-GW to initiate the "Network Triggered Service Request" procedure, as described in clause 5.3.4.3. 7. If the eNodeB provided and MME accepted Secondary RAT usage data in step 6 (i.e. MME initiated S1 release), the MME initiates the Secondary RAT usage data reporting procedure in clause 5.7A.3 as illustrated in figure 5.7A.3-2 (steps 7a - 7d). If PGW secondary RAT usage reporting is active, steps 7b and 7c are performed, otherwise only steps 7a and 7d are performed. If the eNodeB provided Secondary RAT usage data in step 1b (i.e. eNodeB initiated S1 release) and PGW secondary RAT usage data reporting is active, the MME initiates the Secondary RAT usage data reporting procedure in clause 5.7A.3 as illustrated in figure 5.7A.3-2. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.3.5 |
6,564 | 5.1.3.4.1 EMM-DEREGISTERED | In the state EMM-DEREGISTERED, the MME has no EMM context or the EMM Context is marked as detached. The UE is detached. The MME may answer to an attach or a combined attach procedure initiated by the UE (see clause 5.5.1). The MME may also answer to a tracking area updating procedure or combined tracking area updating procedure initiated by a UE if the EMM context is marked as detached. The MME may also answer to a detach procedure initiated by the UE (see clause 5.5.1.2.7). If ISR is not activated or ISR is deactivated during a routing area updating or combined routing area updating procedure or an inter-system handover to A/Gb mode or Iu mode, the MME enters the state EMM-DEREGISTERED after the successful completion of the procedure. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.1.3.4.1 |
6,565 | 8.10.1.2.5 Enhanced Performance Requirement Type A β Single-layer Spatial Multiplexing with TM9 interference model (User-Specific Reference Symbols) | The requirements are specified in Table 8.10.1.2.5-2, with the addition of the parameters in Table 8.10.1.2.5-1 and the downlink physical channel setup according to Annex C.3.2. The purpose of these tests is to verify closed-loop rank one performance on one of the antenna ports 7 or 8 without a simultaneous transmission on the other antenna port in the serving cell when the PDSCH transmission in the serving cell is interfered by PDSCH of one dominant interfering cell applying transmission mode 9 interference model defined in clause B.5.4. In 8.10.1.2.5-1, Cell 1 is the serving cell, and Cell 2 is the interfering cell. The downlink physical channel setup is according to Annex C.3.2 for each of Cell 1and Cell 2, respectively. Table 8.10.1.2.5-1: Test Parameters for Testing CDM-multiplexed DM RS (single layer) with TM9 interference model and 4Rx Antenna Ports Table 8.10.1.2.5-2: Enhanced Performance Requirement Type A, CDM-multiplexed DM RS with TM9 interference model and 4Rx Antenna Ports | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.10.1.2.5 |
6,566 | 4.11.0a.2a.5 UE Policy Association establishment | To support the delivery of URSP rule in EPS as described in clause 6.1.2.2.3 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20], the PCF for the PDU Session may establish a UE Policy Association towards the PCF for the UE. This procedure may be triggered by the following procedures: 1. UE requested bearer resource modification. 2. 5GS to EPS handover or 5GS to EPS Idle Mode mobility. Figure 4.11.0a.2a.5-1: UE Policy Association establishment procedure In the non-roaming case, the V-PCF for the UE is not involved, and the PCF for the PDU Session interacts with the PCF for the UE. For the Home Routed roaming scenario, the V-PCF for the UE is not involved and the H-PCF for the PDU Session interacts with the H-PCF for the UE. For the LBO roaming scenario, the V-PCF for the PDU Session interacts with the V-PCF for the UE and the V-PCF for the UE interacts with the H-PCF for the UE. The procedure is based on clause 4.16.11.1 for a UE in 5GC with the following differences: 1. The PCF for the PDU Session determines the need of establishment of a UE Policy Association when: - A UE Policy Container is received from the UE during SM Policy Association Update at UE requested bearer resource modification as described in clause 4.11.0a.2a.2.1; or - During 5GS to EPS mobility as described in clause 4.11.0a.2a.2.2. 2. Same as step 2 in clause 4.16.11, with the following exceptions: The PCF for the PDU Session includes the UE Policy Container in case of SM Policy Association update at UE requested bearer resource modification or 5GS to EPS Mobility indication in case of SM Policy Association update at 5GS to EPS mobility. For LBO roaming the V-PCF for the PDU Session discovers and selects an instance of the V-PCF for the UE based on the available PCF instances obtained from the NRF or locally configured information in the V-PCF, depending on operator's policies, as described in clause 6.3.7.1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The V-PCF for the PDU Session contacts the V-PCF for the UE and steps 3 and 4 are executed. For non-roaming or Home Routed roaming the (H-)PCF for the PDU Session contacts the (H-)PCF for the UE and step5 follows. 3. Same as step 3 in clause 4.16.11.1, with the following exceptions: The UE Policy Container is received at SM Policy Association instead of initial registration. When the UE Policy Association is being established due to 5GS to EPS mobility as described in clause 4.11.0a.2a.2.2, the V-PCF for a UE in the VPLMN needs to discover and select the same H-PCF for a UE that is serving the UE in the H-PLMN for 5GS by querying the BSF in the HPLMN. This is to be able to recover the information about the list of PSIs in the UE and the subscribed PCRTs from former UE Policy Association for the UE in 5GS as described in step 6. Therefore, the V-PCF for a UE in the VPLMN needs first to discover the BSF in the HPLMN. NOTE 1: For Home Routed roaming, the V-PCF for a UE is not involved, therefore in this roaming scenario it is not possible to retrieve the Application guidance on URSP Rule for inbound roamers of the PLMN and provide it to the H-PCF for the UE to be used as input for the generation of the URSP rules for the UE as described in clause 6.6.2.2.3 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. 4. Same as in clause 4.16.11.1. 5. Same as in clause 4.16.11.1 step 5, with the following exceptions: The subscription to notification of N1 message delivery of policy information to the UE using Namf_Communication_N1N2MessageSubscribe service is not applicable. 6. The Same as step 6 in clause 4.16.11.1, with the following difference: If "5GS to EPS Mobility" indication was received in Npcf_UEPolicyControl_Create in step 2 instead, the (H-)PCF recovers the information about the list of PSIs for the UE, the subscribed PCRTs in 5GS from former UE Policy Association for the UE and the indication about the support of provisioning of URSP rules in EPS. If the UE does not support the provisioning of URSPs in EPS, the H-PCF rejects the establishment of the UE Policy Association. NOTE 2: In LBO roaming the V-PCF for a UE may trigger the establishment of the UE Policy Association for a UE that does not support the provisioning of URSP in EPS, as described in step 4a in clause 4.11.0a.2a.2.2. The (H-)PCF provides the UE Policy Container in the Npcf_UEPolicyControl_UpdateNotify Request. 7. Same as in clause 4.16.11. NOTE 3: Steps 8 and 9 are executed only in LBO roaming scenario. 8. The V-PCF for the UE forwards the UE Policy Container to the V-PCF for the PDU Session by invoking Npcf_UEPolicyControl UpdateNotify Request. The V-PCF for the UE checks the size limit as described in clause 6.1.2.2.2 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. 9. The V-PCF for the PDU Session sends a response to the V-PCF for the UE. 10. If the UE provides a UE Policy Container with the result of the URSP update to the PCF for the PDU Session as described in clause 4.11.0a.2a.2.3 the PCF for the PDU Session forwards the UE Policy Container to the (V-) PCF for the UE invoking Npcf_UEPolicyControl_Update Request. 11. The (V-) PCF for the UE sends a response to the (V-) PCF for the PDU Session. NOTE 4: Steps 12 and 13 are executed only in LBO roaming. 12. The V-PCF for the UE forwards the notification response to the H-PCF by invoking Npcf_UEPolicyControl_Update Request. 13. The H-PCF sends a response to the V-PCF for the UE. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.11.0a.2a.5 |
6,567 | 6.4.1.2 Default EPS bearer context activation initiated by the network | The MME shall initiate the default bearer context activation procedure by sending an ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message and enter the state BEARER CONTEXT ACTIVE PENDING (see example in figure 6.4.1.2.1). When the default bearer is activated as part of the attach procedure, the MME shall send the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message together with ATTACH ACCEPT and shall not start the timer T3485. When the default bearer is activated as the response to a stand-alone PDN CONNECTIVITY REQUEST message apart from the attach procedure, the MME shall send the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message alone, and start the timer T3485. The MME shall assign and include an EPS bearer identity in the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message selecting a value as specified by clause 9.3.2. The MME shall retrieve the PTI from the PDN CONNECTIVITY REQUEST message and include it in the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message. Both the network identifier part and the operator identifier part shall be included in the Access Point Name IE. Figure 6.4.1.2.1: Default EPS bearer context activation procedure | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.4.1.2 |
6,568 | 5.7.2.6 Aggregate Bit Rates | Each PDU Session of a UE is associated with the following aggregate rate limit QoS parameter: - per Session Aggregate Maximum Bit Rate (Session-AMBR). The Session-AMBR is signalled to the appropriate UPF entity/ies to the UE and to the (R)AN (to enable the calculation of the UE-AMBR). The Session-AMBR limits the aggregate bit rate that can be expected to be provided across all Non-GBR QoS Flows for a specific PDU Session. The Session-AMBR is measured over an AMBR averaging window which is a standardized value. The Session-AMBR is not applicable to GBR QoS Flows. Each UE is associated with the following aggregate rate limit QoS parameter: - per UE Aggregate Maximum Bit Rate (UE-AMBR). The UE-AMBR limits the aggregate bit rate that can be expected to be provided across all Non-GBR QoS Flows of a UE. Each (R)AN shall set its UE-AMBR to the sum of the Session-AMBR of all PDU Sessions with active user plane to this (R)AN up to the value of the UE-AMBR received from AMF. The UE-AMBR is a parameter provided to the (R)AN by the AMF based on the value of the subscribed UE-AMBR retrieved from UDM or the dynamic serving network UE-AMBR retrieved from PCF (e.g. for roaming subscriber). The AMF provides the UE-AMBR provided by PCF to (R)AN if available. The UE-AMBR is measured over an AMBR averaging window which is a standardized value. The UE-AMBR is not applicable to GBR QoS Flows. Each group of PDU Sessions of the UE for the same slice (S-NSSAI) may be associated with the following aggregate rate limit QoS parameter: - per UE per Slice-Maximum Bit Rate (UE-Slice-MBR). The UE-Slice-MBR limits the aggregate bit rate that can be expected to be provided across all GBR and Non-GBR QoS Flows corresponding to PDU Sessions of the UE for the same slice (S-NSSAI) which have an active user plane. Each supporting NG-RAN shall set its UE-Slice-MBR to the sum of the Session-AMBR and MFBR for GBR QoS Flows of all PDU Sessions corresponding to the slice (S-NSSAI) with active user plane to this NG-RAN up to the value of the UE-Slice-MBR corresponding to the slice (S-NSSAI) received from AMF. The UE-Slice-MBR is measured over an AMBR averaging window which is a standardized value. The UE-Slice-MBR is an optional parameter provided to the NG-RAN by the AMF as described in clause 5.15.13. NOTE: The AMBR averaging window is only applied to Session-AMBR, UE-AMBR and UE-Slice-MBR measurement and the AMBR averaging windows for Session-AMBR and UE-AMBR are standardised to the same value. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.7.2.6 |
6,569 | β SL-BWP-PRS-PoolConfigCommon | The IE SL-BWP-PRSPoolConfigCommon is used to configure the cell-specific NR sidelink PRS dedicated resource pool. SL-BWP-PRS-PoolConfigCommon information element -- ASN1START -- TAG-SL-BWP-PRS-POOLCONFIGCOMMON-START SL-BWP-PRS-PoolConfigCommon-r18 ::= SEQUENCE { sl-PRS-RxPool-r18 SEQUENCE (SIZE (1..maxNrofRXPool-r16)) OF SL-PRS-ResourcePool-r18 OPTIONAL, -- Need R sl-PRS-TxPoolSelectedNormal-r18 SEQUENCE (SIZE (1..maxNrofSL-PRS-TxPool-r18)) OF SL-PRS-ResourcePoolConfig-r18 OPTIONAL, -- Need R sl-PRS-TxPoolExceptional-r18 SL-PRS-ResourcePoolConfig-r18 OPTIONAL, -- Need R ... } -- TAG-SL-BWP-PRSPOOLCONFIGCOMMON-STOP -- ASN1STOP Editor's Note: FFS If sl-PRS-TxPoolExceptional is used for SL positioning. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | β |
6,570 | 7.10 Support of RAN visible QoE measurement | The RAN visible QoE measurement function is specified in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [2]. In split gNB architecture, upon the reception of the RAN visible QoE measurement report from the UE, the gNB-CU may forward the corresponding QoE information to the gNB-DU. The QoE information transferred to the gNB-DU may include the RAN visible QoE measurement results received from the UE, along with the corresponding DRB ID(s). The gNB-DU may deactivate the transfer of RAN visible QoE measurement results from the gNB-CU, by initiating QoE Information Transfer Control procedure towards the gNB-CU. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 7.10 |
6,571 | β BH-RLC-ChannelConfig | The IE BH-RLC-ChannelConfig is used to configure an RLC entity, a corresponding logical channel in MAC for BH RLC channel between IAB-node and its parent node. BH-RLC-ChannelConfig information element -- ASN1START -- TAG-BHRLCCHANNELCONFIG-START BH-RLC-ChannelConfig-r16::= SEQUENCE { bh-LogicalChannelIdentity-r16 BH-LogicalChannelIdentity-r16 OPTIONAL, -- Cond LCH-SetupOnly bh-RLC-ChannelID-r16 BH-RLC-ChannelID-r16, reestablishRLC-r16 ENUMERATED {true} OPTIONAL, -- Need N rlc-Config-r16 RLC-Config OPTIONAL, -- Cond LCH-Setup mac-LogicalChannelConfig-r16 LogicalChannelConfig OPTIONAL, -- Cond LCH-Setup ... } -- TAG-BHRLCCHANNELCONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | β |
6,572 | D.3.2 Process and asset monitoring | The monitoring of states, e.g. the level of the liquid of process reactors, is a paramount task in process automation. Due to the ever-changing states, measurement data is either pulled or pushed from the sensors in a cyclic manner. Some sensors are more conveniently accessed via wireless links, and monitoring of these sensors via handheld terminals, e.g. during maintenance, is also on the rise. This kind of application entails rather modest user experienced data rates (~ 1 Mbit/s), and since this kind of data is "only" an indicator for, e.g., what process should be stopped in order to avoid an overflow, and not for automated control loops, the requirement on communication service availability is comparably low (99,9%). Note that emergency valves and such are typically operated locally and do not rely on communication networks. However, many sensors are deployed in chemical plants etc., so that connection density can readily reach 10 000 km-2. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | D.3.2 |
6,573 | 8.48 Fully Qualified Container (F-Container) | Fully Qualified Container (F-Container) is coded as depicted in Figure 8.48-1. All Spare bits are set to zeros by the sender and ignored by the receiver. Figure 8.48-1: Full Qualified Container (F-Container) The F-Container field shall contain one of the following information, depending of the contents of the container transported by the specific GTP Information Element: - transparent copy of the corresponding IEs (see clause 8.2.2): - the "Source to Target Transparent Container" or the "Target to Source Transparent Container" as specified in 3GPP TS 25.413[ UTRAN Iu interface Radio Access Network Application Part (RANAP) signalling ] [33]; or - the "SON Configuration Transfer" as specified in 3GPP TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [10] or "EN-DC SON Configuration Transfer" as specified in 3GPP TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [10]; or - the "Inter-system SON Configuration Transfer" as specified in 3GPP TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [10] and 3GPP TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [84]; or - the "eNB Status Transfer Transparent Container" or eNB Early Status Transfer Transparent Container as specified in 3GPP TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [10]; or - "Source BSS to Target BSS Transparent Container" or "Target BSS to Source BSS Transparent Container" as specified in 3GPP TS 48.018[ None ] [34] or 3GPP TS 25.413[ UTRAN Iu interface Radio Access Network Application Part (RANAP) signalling ] [33], which contains the value part of the "Source BSS to Target BSS Transparent Container" IE or the value part of the "Target BSS to Source BSS Transparent Container" IE defined in 3GPP TS 48.018[ None ] [34], i.e. octets 3 to n, excluding octet 1 (Element ID) and octet 2, 2a (Length); or - transparent copy of the value part of the "NBIFOM Container" as specified in 3GPP TS 24.161[ Network-Based IP Flow Mobility (NBIFOM); Stage 3 ] 73]. - transparent copy of the octets of the encoded OCTET STRING of the "Source to Target Transparent Container" or the "Target to Source Transparent Container" specified in 3GPP TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [10] and 3GPP TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [84]; or - transparent copy of the BSSGP RIM PDU as specified in 3GPP TS 48.018[ None ] [34]; or - the Packet Flow ID, Radio Priority, SAPI, PS Handover XID parameters as specified in figure 8.42-2. NOTE 1: Annex B.2 provides further details on the encoding of Generic Transparent Containers over RANAP, S1-AP and GTP. See also Annex C of 3GPP TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [10] for further details on how the MME constructs the F-Container field from the Source to Target Transparent Container or Target to Source Transparent Container IEs received from S1-AP. Container Type values are specified in Table 8.48-2. Table 8. 48-2: Container Type values NOTE 2: For any other new future F-Container content types, new Container Type values may be needed, although use of RAT agnostic containers should be used whenever possible. The BSS Container IE in the Bearer Context IE in Forward Relocation Request and Context Response messages is coded as depicted in Figure 8.48-3. Figure 8.48-3: BSS Container The flags PFI, RP, SAPI and PHX in octet 6 indicate the corresponding type of parameter (Packet FlowID, Radio Priority, SAPI and PS handover XID parameters) shall be present in a respective field or not. If one of these flags is set to "0", the corresponding field shall not be present at all. The Spare bit shall be set to zero by the sender and ignored by the receiver. If PFI flag is set, Packet Flow ID shall be present in Octet a. If RP flag is set, Radio Priority shall be present in Octet b. If SAPI flag is set, SAPI shall be present in Octet b. If PHX flag is set: - XiD parameters length is present in Octet c. - XiD parameters are present in Octet d to n. | 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.48 |
6,574 | 6.2.1 Services and Functions | The main services and functions of the MAC sublayer include: - Mapping between logical channels and transport channels; - Multiplexing/demultiplexing of MAC SDUs belonging to one or different logical channels into/from transport blocks (TB) delivered to/from the physical layer on transport channels; - Scheduling information reporting; - Error correction through HARQ (one HARQ entity per cell in case of CA); - Priority handling between UEs by means of dynamic scheduling; - Priority handling between logical channels of one UE by means of logical channel prioritisation; - Priority handling between overlapping resources of one UE; - Padding. A single MAC entity can support multiple numerologies, transmission timings and cells. Mapping restrictions in logical channel prioritisation control which numerology(ies), cell(s), and transmission timing(s) a logical channel can use (see clause 16.1.2). | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 6.2.1 |
6,575 | 5.3.4.2 Mobility Pattern | The Mobility Pattern is a concept that may be used by the AMF to characterise and optimise the UE mobility. The AMF determines and updates Mobility Pattern of the UE based on subscription of the UE, statistics of the UE mobility, network local policy, and the UE assisted information, or any combination of them. The statistics of the UE mobility can be historical or expected UE moving trajectory. If NWDAF is deployed, the statistics of the UE mobility can also be analytics (i.e. statistics or predictions) provided by the NWDAF (see TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [86]). The Mobility Pattern can be used by the AMF to optimize mobility support provided to the UE, for example, Registration area allocation. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.3.4.2 |
6,576 | 5.32.7.3 Interworking without N26 Interface | Interworking without N26 interface is based on clause 5.17.2.3, with the following differences and clarifications: - After UE moves from 5GS to EPS, UE may send a PDN Connectivity Request with "handover" indication to transfer the MA PDU Session to EPS. Then, if the UE or the network does not support MA PDU Session with 3GPP access connected to EPC, the SMF+PGW-C triggers to release MA PDU in 5GS. If UE does not transfer the MA PDU Session to EPS, UE keeps the MA PDU Session in 5GS. If the UE and the network support MA PDU Session with 3GPP access connected to EPC, the UE includes a "handover" indication and a "MA PDU Request" indication as well as the PDU Session ID in the PCO and the SMF+PGW-C keeps the user-plane resources over non-3GPP access in 5GC as described in clause 4.22.6.2.5 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. In this case, UE may report to UPF that 3GPP access is unavailable, all MA PDU Session traffic is transported over N3GPP access. Later, if UE returns to 5GS, UE may report the 3GPP access availability to UPF. - After UE moves from EPS to 5GS, UE may trigger PDU Session Establishment procedure to transfer the PDN Connection to 5GS. During the PDU Session Establishment procedure, if the PDN Connection was not used as the 3GPP access leg of the MA PDU Session, the UE may request to establish a MA PDU Session by including "MA PDU Request" or, if no policy in the UE (e.g. no URSP rule) and no local restrictions mandate a single access for the PDU Session, the UE may include the "MA PDU Network-Upgrade Allowed" indication. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.32.7.3 |
6,577 | 6.2.17 Handling of edge computing enhancements | EAS discovery, EAS rediscovery and ECS address provisioning provide enhanced edge computing support in 5GS (see 3GPP TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [10A]). If the network supports the session breakout connectivity model or distributed anchor connectivity model to enable edge computing enhancements and the UE generated DNS message is to be handled by an edge application server discovery function (EASDF) for EAS discovery as specified in 3GPP TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [10A], the SMF selects the EASDF and it provides its IP address to the UE as the DNS server to be used for the PDU session in the Extended protocol configuration options IE during the UE-requested PDU session establishment procedure as described in subclause 6.4.1.3. NOTE 1: EASDF selection is outside the scope of the present document. If the network supports the session breakout connectivity model to enable edge computing enhancements and the UE generated DNS message is to be handled by a local DNS server for EAS discovery as specified in 3GPP TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [10A], the SMF selects the local DNS server, obtains its IP address and can provide the IP address of the local DNS server to the UE as the DNS server to be used for the PDU session in the Extended protocol configuration options IE during the UE-requested PDU session establishment procedure or the network-requested PDU session modification procedure as described in subclauses 6.4.1.3 and 6.3.2.2, respectively. NOTE 2: Local DNS server selection and the acquisition of its IP address is outside the scope of the present document. If the UE supports EAS rediscovery and the SMF decides to trigger the EAS rediscovery as specified in 3GPP TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [10A], the SMF initiates a network-requested PDU session modification procedure to provide the EAS rediscovery information to the UE as described in subclauses 6.3.2.2. Upon receipt of the EAS rediscovery information, the UE provides the received information to the upper layers. NOTE 3: The upper layers of the UE uses the EAS rediscovery information to trigger the EAS discovery procedure to get the new EAS information as specified in 3GPP TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [10A]. If the UE supports ECS address provisioning over NAS as specified in 3GPP TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [10A], the UE indicates its support of ECS configuration information provisioning over NAS in the Extended protocol configuration options IE either during the UE-requested PDU session establishment procedure as described in subclause 6.4.1.2 or while in S1 mode as described in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15], respectively. If the UE indicated support of ECS configuration information address provisioning over NAS, the SMF can provide the ECS configuration information in the Extended protocol configuration options IE during the network-requested PDU session modification procedure, UE-requested PDU session establishment procedure or the UE-requested PDU session modification procedure as described in subclauses 6.3.2.2, 6.4.1.3 and 6.4.2.3, respectively. NOTE 4: The SMF can obtain the ECS configuration information based on the local configuration, the UE's location, the UE's subscription information, or any combination of them. If the UE supports the edge DNS client (EDC) as specified in 3GPP TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [10A], the UE indicates its support of EDC in the Extended protocol configuration options IE during the UE-requested PDU session establishment procedure as described in subclause 6.4.1.2 or the UE-requested PDU session modification procedure as described in subclause 6.4.2.2. If the UE indicates support of EDC, the SMF can indicate in the Extended protocol configuration options IE during the UE-requested PDU session establishment procedure as described in subclause 6.4.1.3 or the network-requested PDU session modification procedure as described in subclause 6.3.2.2, that the network allows the use of EDC for the applications which are mapped onto the PDU session and explicitly requested the use of EDC, or that the network requires the use of EDC for all applications mapped onto the PDU session. | 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.17 |
6,578 | 6.1 RSRP related measurements | a) This measurement provides a bin distribution (histogram) of the periodical E-UTRAN RSRP measurements received from all of UEs in the measured E-UTRAN cell. To collect this measurement, the eNodeB needs to trigger the periodical UE measurement reports towards all of the UEs in the measured E-UTRAN cell. b) CC c) Receipt by the eNodeB from the UE of MeasurementReport message indicating a periodical UE measurement report where IE MeasResults field includes rsrpResult. The event triggered MeasurementReport messages are excluded.This measurement shall be increased for each reported value RSRP_LEV (See in 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [18]). For every one or two or 17 or 20 RSRP_LEV(s) a separate measurement is defined. (See in 3GPP TS 36.133[ Evolved Universal Terrestrial Radio Access (E-UTRA); Requirements for support of radio resource management ] [19]) d) Each measurement is an integer value. e) MR.Rsrp.y . y is an integer from 00 to 47. Note: 00 of y indicates from RSRP _LEV _00 to RSRP _LEV _LEV _20, namely RSRP < -120dBm, 01 of y indicates RSRP _LEV _21 and RSRP _LEV _25, namely -120 RSRP < -115dBm, 02 of y indicates RSRP _LEV _26, namely -115 RSRP < -114dBm, 03 of y indicates RSRP _LEV _27, namely -114 RSRP < -113dBm β¦ 36 of y indicates RSRP _LEV _60, namely -81 RSRP < -80dBm, 37 of y indicates RSRP _LEV _61, RSRP _LEV _62, namely -80 RSRP < -78dBm, 38 of y indicates RSRP _LEV _63, RSRP _LEV _64, namely -78 RSRP < -76dBm, β¦ 46 of y indicates from RSRP _LEV _79 to RSRP _LEV _80, namely -62 RSRP < -60dBm, 47 of y indicates from RSRP _LEV _81 to RSRP _LEV _97, namely -60dBm RSRP. (See in 3GPP TS36.133[ Evolved Universal Terrestrial Radio Access (E-UTRA); Requirements for support of radio resource management ] [19]) f) EUtranCellTDD EUtranCellFDD g) Valid for packet switched traffic. h) EPS | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 6.1 |
6,579 | 7.3.1 Procedure transaction identity | The following network procedures shall apply for handling an unknown, erroneous, or unforeseen PTI received in a 5GSM message: a) In case the network receives a PDU SESSION MODIFICATION COMPLETE, a PDU SESSION RELEASE COMPLETE message or a PDU SESSION MODIFICATION COMMAND REJECT message in which the PTI value is an assigned or unassigned value that does not match any PTI in use, the network shall respond with a 5GSM STATUS message including 5GSM cause #47 "PTI mismatch". b) In case the network receives a PDU SESSION AUTHENTICATION COMPLETE message or a SERVICE-LEVEL AUTHENTICATION COMPLETE message in which the PTI value is an assigned value, the network shall respond with a 5GSM STATUS message including 5GSM cause #81 "invalid PTI value". c) In case the network receives a PDU SESSION ESTABLISHMENT REQUEST message, a PDU SESSION MODIFICATION REQUEST message or a PDU SESSION RELEASE REQUEST message in which the PTI value is an unassigned value, the network shall respond with a 5GSM STATUS message including 5GSM cause #81 "invalid PTI value". d) In case the network receives a 5GSM message in which the PTI value is a reserved value, the network shall ignore the message. The following UE procedures shall apply for handling an unknown, erroneous, or unforeseen PTI received in a 5GSM message: a) In case the UE receives a PDU SESSION MODIFICATION COMMAND message or a PDU SESSION MODIFICATION REJECT message in which the PTI value is an assigned value that does not match any PTI in use: 1) if the UE detects that this PDU SESSION MODIFICATION COMMAND message is a network retransmission of an already accepted request (see subclause 6.3.2.3), the UE shall respond with a PDU SESSION MODIFICATION COMPLETE message; 2) if the UE detects that this PDU SESSION MODIFICATION COMMAND message is a network retransmission of an already rejected request (see subclause 6.3.2.4), the UE shall respond with a PDU SESSION MODIFICATION COMAND REJECT message; or 3) otherwise, the UE shall respond with a 5GSM STATUS message including 5GSM cause #47 "PTI mismatch". b) In case the UE receives a PDU SESSION RELEASE COMMAND message or a PDU SESSION RELEASE REJECT message in which the PTI value is an assigned value that does not match any PTI in use: 1) if the UE detects that this PDU SESSION RELEASE COMMAND message is a network retransmission of an already accepted request (see subclause 6.3.3.3), the UE shall respond with a PDU SESSION RELEASE COMPLETE message; or 2) otherwise, the UE shall respond with a 5GSM STATUS message including 5GSM cause #47 "PTI mismatch". c) In case the UE receives a PDU SESSION ESTABLISHMENT ACCEPT message or a PDU SESSION ESTABLISHMENT REJECT message in which the PTI value is an assigned value that does not match any PTI in use: 1) the UE shall respond with a 5GSM STATUS message including 5GSM cause #47 "PTI mismatch". d) In case the UE receives a PDU SESSION AUTHENTICATION COMMAND message, a PDU SESSION AUTHENTICATION RESULT message or a SERVICE-LEVEL AUTHENTICATION COMMAND message in which the PTI value is an assigned value, the UE shall respond with a 5GSM STATUS message including 5GSM cause #81 "invalid PTI value". e) In case the UE receives a PDU SESSION ESTABLISHMENT ACCEPT message, a PDU SESSION ESTABLISHMENT REJECT message, a PDU SESSION MODIFICATION REJECT message or a PDU SESSION RELEASE REJECT message in which the PTI value is an unassigned value, the UE shall ignore the message. f) In case the UE receives a 5GSM message in which the PTI value is a reserved value, the UE shall ignore the message. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 7.3.1 |
6,580 | 4.3.3.2 Identification response by the mobile station | The mobile station shall be ready to respond to an IDENTITY REQUEST message at any time whilst a RR connection exists. Upon receipt of the IDENTITY REQUEST message the mobile station shall send an IDENTITY RESPONSE message. The IDENTITY RESPONSE message shall contain the identification parameters as requested by the network. Upon receipt of the IDENTITY REQUEST message with the Identity type IE indicating that P-TMSI, RAI and P-TMSI signature are being requested, an MS that supports S1 mode shall handle the IDENTITY RESPONSE message as follows: - If the TIN indicates "GUTI" and the MS holds a valid GUTI allocated by an MME, the MS shall map the GUTI into a P-TMSI, P-TMSI signature and RAI as specified in 3GPP TS 23.003[ Numbering, addressing and identification ] [10]. The MS shall indicate the P-TMSI in the Mobile identity IE. In addition, the MS shall include the mapped RAI in the Routing area identification IE and the mapped P-TMSI signature in the P-TMSI signature IE. In addition, the MS shall include the P-TMSI type IE with P-TMSI type set to "mapped P-TMSI". - If the TIN indicates "P-TMSI" or "RAT-related TMSI" and the MS holds a valid P-TMSI and RAI, the MS shall indicate the P-TMSI in the Mobile identity IE and shall indicate the RAI in the Routing area identification IE. In addition, the MS shall include the P-TMSI type IE with P-TMSI type set to "native P-TMSI". If the MS holds a valid P-TMSI signature, it shall include it in the P-TMSI signature IE. If the MS does not support S1 mode, it shall handle the IDENTITY RESPONSE message as follows: - If the MS holds a valid P-TMSI and RAI, the MS shall indicate the P-TMSI in the Mobile identity IE and shall indicate the RAI in the Routing area identification IE. In addition, the MS shall include the P-TMSI type IE with P-TMSI type set to "native P-TMSI". If the MS holds a valid P-TMSI signature, it shall include it in the P-TMSI signature IE. Upon receipt of the IDENTITY RESPONSE message, the network shall stop timer T3270. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.3.3.2 |
6,581 | 9.4.16 Routing area update complete | This message shall be sent by the MS to the network in response to a routing area update accept message if at least one of the following conditions is fulfilled: - a P-TMSI and/or a TMSI has been assigned; - there are established LLC connections; or - the network has requested the MS to provide feature-related information. See table 9.4.16/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Message type: routing area update complete Significance: dual Direction: MS to network Table 9.4.16/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : ROUTING AREA UPDATE COMPLETE message content | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.4.16 |
6,582 | 5.5.1.2.3 S1-based handover, Reject | The Target eNodeB rejects the use of the Handover procedure if none of the requested bearers in the Handover Request message could be established. In this case no UE context is established in the target MME/eNodeB and no resources are allocated. Further, the Target MME rejects the handover request and clears all resource in Target eNodeB and Target MME if the Target eNodeB accepts the handover request but none of the default EPS bearers gets resources allocated. In both cases, the UE remains in the Source eNodeB/MME. Figure 5.5.1.2.3-1: S1-based handover, Reject NOTE 1: Steps 3, 4, 7 and 8 are performed if the MME is relocated. NOTE 2: If the MME is not relocated Steps 5 and 6 are performed by the source MME and, in the description below, the source MME acts as the target MME. 1-5. Steps 1 to 5 in the flow are identical to steps 1-5 in clause 5.5.1.2.2. 6a. If the Target eNodeB fails to allocate any resources for any of the requested EPS bearers it sends a Handover Failure (Cause) message to the Target MME. The Target MME clears any reserved resources for this UE in the target MME. 6b. If the Target MME receives a Handover Request Acknowledge message from the Target eNodeB but none of the default EPS bearers are in the EPS Bearer Setup list IE, the Target MME clears any reserved resources for this UE in both the Target MME and the Target eNodeB. 7. This step is only performed for Serving GW relocation, i.e. if steps 4/4a have been performed. The Target MME deletes the EPS bearer resources by sending Delete Session Request (Cause) messages to the Target Serving GW. The Target Serving GW acknowledges with Delete Session Response (Cause) messages. 8. The Target MME sends the Forward Relocation Response (Cause) message to the Source MME. 9. When the Source MME receives the Forward Relocation Response message, it sends a Handover Preparation Failure (Cause) message to the Source eNodeB. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.5.1.2.3 |
6,583 | β FailureInformation | The FailureInformation message is used to inform the network about a failure detected by the UE. Signalling radio bearer: SRB1 or SRB3 RLC-SAP: AM Logical channel: DCCH Direction: UE to network FailureInformation message -- ASN1START -- TAG-FAILUREINFORMATION-START FailureInformation ::= SEQUENCE { criticalExtensions CHOICE { failureInformation FailureInformation-IEs, criticalExtensionsFuture SEQUENCE {} } } FailureInformation-IEs ::= SEQUENCE { failureInfoRLC-Bearer FailureInfoRLC-Bearer OPTIONAL, lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension FailureInformation-v1610-IEs OPTIONAL } FailureInfoRLC-Bearer ::= SEQUENCE { cellGroupId CellGroupId, logicalChannelIdentity LogicalChannelIdentity, failureType ENUMERATED {rlc-failure, spare3, spare2, spare1} } FailureInformation-v1610-IEs ::= SEQUENCE { failureInfoDAPS-r16 FailureInfoDAPS-r16 OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL } FailureInfoDAPS-r16 ::= SEQUENCE { failureType-r16 ENUMERATED {daps-failure, spare3, spare2, spare1} } -- TAG-FAILUREINFORMATION-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | β |
6,584 | 9.9.4.30 Extended quality of service | The purpose of the Extended quality of service information element is to indicate for an EPS bearer context the maximum bit rates for uplink and downlink and the guaranteed bit rates for uplink and downlink, if at least one of the bit rates has a value higher than 10 Gbps. The Extended quality of service information element is coded as shown in figure 9.9.4.30.1 and table 9.9.4.30.1. For uplink and downlink, if the sending entity only has to indicate one bit rate (i.e. with a value higher than 10 Gbps), it shall encode the other bit rate (i.e., with a value smaller or equal to 10 Gbps) as "00000000". The receiving entity shall ignore a bit rate which is included in the extended quality of service information element and has a value smaller or equal to 10 Gbps. The Extended quality of service is a type 4 information element with a length of 12 octets. Figure 9.9.4.30.1: Extended quality of service information element Table 9.9.4.30.1: Extended 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.30 |
6,585 | 6.5.1.4 UE requested PDN connectivity procedure not accepted by the network 6.5.1.4.1 General | If connectivity with the requested PDN cannot be accepted by the network, the MME shall send a PDN CONNECTIVITY REJECT message to the UE. The message shall contain the PTI and an ESM cause value indicating the reason for rejecting the UE requested PDN connectivity. The ESM cause IE typically indicates one of the following ESM cause values: #8: operator determined barring; #26: insufficient resources; #27: missing or unknown APN; #28: unknown PDN type; #29: user authentication or authorization failed; #30: request rejected by Serving GW or PDN GW; #31: request rejected, unspecified; #32: service option not supported; #33: requested service option not subscribed; #34: service option temporarily out of order; #35: PTI already in use; #38: network failure; #50: PDN type IPv4 only allowed; #51: PDN type IPv6 only allowed; #53: ESM information not received; #54: PDN connection does not exist; #55: multiple PDN connections for a given APN not allowed; #57: PDN type IPv4v6 only allowed; #58: PDN type non IP only allowed; #61: PDN type Ethernet only allowed; #65: maximum number of EPS bearers reached; #66: requested APN not supported in current RAT and PLMN combination; #95 β 111: protocol errors; #112: APN restriction value incompatible with active EPS bearer context; #113: Multiple accesses to a PDN connection not allowed. The network may include a Back-off timer value IE in the PDN CONNECTIVITY REJECT message. If the ESM cause value is #26 "insufficient resources" and the PDN CONNECTIVITY REQUEST message was received via a NAS signalling connection established with RRC establishment cause "High priority access AC 11 β 15" or the request type in the PDN CONNECTIVITY REQUEST message was set to "emergency" or "handover of emergency bearer services", the network shall not include a Back-off timer value IE. If the ESM cause value is different from #26 "insufficient resources", #28 "unknown PDN type", #50 "PDN type IPv4 only allowed", #51 "PDN type IPv6 only allowed", #54 "PDN connection does not exist", #57 "PDN type IPv4v6 only allowed", #58 "PDN type non IP only allowed", #61 "PDN type Ethernet only allowed", #65 "maximum number of EPS bearers reached", and #66 "requested APN not supported in current RAT and PLMN combination", and the PDN CONNECTIVITY REQUEST message was received via a NAS signalling connection established with RRC establishment cause "High priority access AC 11 β 15", the network shall not include a Back-off timer value IE. If the Back-off timer value IE is included and the ESM cause value is different from #26 "insufficient resources", #50 "PDN type IPv4 only allowed", #51 "PDN type IPv6 only allowed", #57 "PDN type IPv4v6 only allowed", #58 "PDN type non IP only allowed", #61 "PDN type Ethernet only allowed", and #65 "maximum number of EPS bearers reached", the network may include the Re-attempt indicator IE to indicate: - whether the UE is allowed to attempt a PDP context activation procedure in the PLMN for the same in A/Gb or Iu mode or a PDU session establishment procedure in the PLMN for the same APN in N1 mode; and - whether another attempt in A/Gb and Iu mode, in S1 mode or in N1 mode is allowed in an equivalent PLMN. If the ESM cause value is #50 "PDN type IPv4 only allowed", #51 "PDN type IPv6 only allowed", #57 "PDN type IPv4v6 only allowed", #58 "PDN type non IP only allowed" or #61 "PDN type Ethernet only allowed", the network may include the Re-attempt indicator IE without Back-off timer value IE to indicate whether the UE is allowed to attempt a PDN connectivity procedure in an equivalent PLMN for the same APN in S1 mode using the same PDN type. If the ESM cause value is #66 "requested APN not supported in current RAT and PLMN combination", the network may include the Re-attempt indicator IE without Back-off timer value IE to indicate whether the UE is allowed to attempt a PDN connectivity procedure in an equivalent PLMN for the same APN in S1 mode. Upon receipt of the PDN CONNECTIVITY REJECT message, the UE shall stop timer T3482 and enter the state PROCEDURE TRANSACTION INACTIVE. If the PDN CONNECTIVITY REJECT message is due to an ESM failure notified by EMM layer (i.e., EMM cause #19 "ESM failure" included in an ATTACH REJECT message), the UE may include a different APN in the PDN CONNECTIVITY REQUEST message. NOTE 1: When receiving EMM cause #19 "ESM failure", coordination is required between the EMM and ESM sublayers in the UE to notify the ESM failure. If the PDN CONNECTIVITY REQUEST message was sent with request type set to "emergency" or "handover of emergency bearer services" in a stand-alone PDN connectivity procedure and the UE receives a PDN CONNECTIVITY REJECT message, then the UE may: a) inform the upper layers of the failure to establish the emergency bearer; or NOTE 2: This can result in the upper layers requesting 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 PDN CONNECTIVITY REQUEST message was sent with PDN type set to "Ethernet" and the UE receives a PDN CONNECTIVITY REJECT message with ESM cause #58 "PDN type non IP only allowed", then the UE may attempt a PDN connectivity procedure with the non-IP PDN type. If the PDN CONNECTIVITY REJECT message contains the UAS services not allowed indication in the Extended protocol configuration options IE and the UE has not provided its CAA-level UAV ID to the network, the UE shall not send another PDN CONNECTIVITY REQUEST message for UAS services without providing its CAA-level UAV ID to the network. NOTE 3: If the PDN CONNECTIVITY REJECT message contains the UAS services not allowed indication in the Extended protocol configuration options IE, the ESM cause value #29 "user authentication or authorization failed" is included in the PDN CONNECTIVITY REJECT message. NOTE 4: The PDN CONNECTIVITY REJECT message contains the UAS services not allowed indication included in the Extended protocol configuration options IE, if the PDN connection is identified to be for UAS services based on the APN, and the CAA-level UAV ID is not provided by the UE in the request, or if the network is informed by the UAS NF that the UAS service is not allowed. NOTE 5: If the PDN CONNECTIVITY REQUEST message does not contain the SDNAEPC support indicator in the Protocol configuration options IE or the Extended protocol configuration options IE and the secondary DN authentication and authorization over EPC is mandatory due to local policies, the ESM cause value #29 "user authentication or authorization failed" can be included in the PDN CONNECTIVITY REJECT message". | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.5.1.4 |
6,586 | β CSI-ReportSubConfig | The IE CSI-ReportSubConfig is used to configure parameters in one sub-configuration within a CSI report configuration. CSI-ReportSubConfig information element -- ASN1START -- TAG-CSI-REPORTSUBCONFIG-START CSI-ReportSubConfig-r18 ::= SEQUENCE { reportSubConfigId-r18 CSI-ReportSubConfigId-r18, portSubsetIndicator-r18 CHOICE { p2 BIT STRING (SIZE (2)), p4 BIT STRING (SIZE (4)), p8 BIT STRING (SIZE (8)), p12 BIT STRING (SIZE (12)), p16 BIT STRING (SIZE (16)), p24 BIT STRING (SIZE (24)), p32 BIT STRING (SIZE (32)) } OPTIONAL, -- Need R nzp-CSI-RS-ResourceList-r18 SEQUENCE (SIZE (1..maxNrofNZP-CSI-RS-ResourcesPerSet)) OF NZP-CSI-RS-ResourceIndex OPTIONAL, -- Need R powerOffset-r18 INTEGER(0..23) OPTIONAL -- Need R } NZP-CSI-RS-ResourceIndex ::= INTEGER (0..maxNrofNZP-CSI-RS-ResourcesPerSet-1-r18) -- TAG-CSI-REPORTSUBCONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | β |
6,587 | 4.3.15a.3 SIPTO at the Local Network with L-GW function collocated with the (H)eNB | SIPTO at the Local Network is achieved using a Local GW (L-GW) function collocated with the (H)eNB and using the same procedures as described in clause 4.3.15, with the following additions: - The (H)eNB supporting the SIPTO at the Local Network function includes the Local GW address to the MME in every INITIAL UE MESSAGE and every UPLINK NAS TRANSPORT control message specified in TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [36]. - The PDN GW selection function uses the L-GW address proposed by (H)eNB in the S1-AP message, instead of DNS interrogation. - Specific to the HeNB subsystem, the Local GW information for SIPTO at the Local Network is signalled on S1 separately from the Local GW information for LIPA. The L-GW shall be able to discriminate between PDN connection for SIPTO at the Local Network and for LIPA. NOTE 1: The protocol option (i.e. GTP or PMIP) supported on the S5 interface between Local GW and S-GW is configured on the MME. The direct user plane path between the (H)eNB and the collocated L-GW is enabled with a SIPTO Correlation ID parameter that is associated with the default EPS bearer on the PDN connection used for SIPTO at the Local Network. Upon establishment of the default EPS bearer the MME sets the SIPTO Correlation ID equal to the PDN GW TEID (GTP-based S5) or the PDN GW GRE key (PMIP-based S5). The SIPTO Correlation ID is then signalled by the MME to the (H)eNB as part of E-RAB establishment and is stored in the E-RAB context in the (H)eNB. The SIPTO Correlation ID is used in the (H)eNB for matching the radio bearers with the direct user plane path connections from the collocated L-GW for SIPTO at local network PDN connection. As IP data session continuity for the SIPTO at the Local Network PDN connection is not supported in this release of the specification, the SIPTO at the Local Network PDN connection shall be re-established when the UE moves away from (H)eNB. During the handover procedure, when the source (H)eNB releases its resources related to the UE, the (H)eNB shall request using intra-node signalling the collocated L-GW to re-establish the SIPTO at the Local Network PDN connection. The L-GW starts a timer. When the timer expires, the L-GW shall initiate the release of the SIPTO at the Local Network PDN connection using the PDN GW initiated bearer deactivation procedure according to clause 5.4.4.1 with the "reactivation requested" cause value. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.3.15a.3 |
6,588 | 5.2.1.1 Transfer of charging events via Rf | In event based charging, a network / user event (e.g. MM submission) corresponds to a single chargeable event. In session based charging, at least two chargeable events are needed, one each to describe the start and the end of the session, respectively. Multiple interim events are possible in order to describe changes to session characteristics (generally termed "change of charging condition", e.g. tariff time switch, change of PDP context QoS or change of IMS session media types), or when certain limits, e.g. time or volume, are exceeded. The CTF transforms each chargeable event into a charging event and forwards these charging events to the CDF in real-time. The relation between chargeable events and charging events is 1:1. For event based charging, the relation between charging events and CDRs is 1:1. For session based charging, the relation between charging events and CDRs is m:n with m >=n. The middle tier TSs specify the chargeable events per domain / service / subsystem even if Rf does not exist as an open interface in the respective domain / service / subsystem, as it is always required to identify the connection between chargeable events and triggers for CDR generation and information addition. If charging events are generated for unsuccessful resource usage attempts, the charging event must describe the reason and the circumstances of the failure. Details, including if and when those events are generated, are specified in the middle tier TSs. Details on the protocol application for the open Rf interface, including the message types and the domain / subsystem /service independent contents of the messages, can be found in TS 32.299[ Telecommunication management; Charging management; Diameter charging applications ] [50]. | 3GPP TS 32.240 | Telecommunication management; Charging management; Charging architecture and principles | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 5.2.1.1 |
6,589 | 4.2.3.3 Number of E-RABs failed to modify the QoS parameter | a) This measurement provides the number of E-RABs failed to be modified the QoS parameter. The measurement is split into subcounters per failure cause. b) CC c) On transmission by the eNodeB/RN of an E-RAB MODIFY RESPONSE message, each E-RAB failed to modify the QoS parameter is added to the relevant measurement per cause, the possible causes are included in TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [9]. The sum of all supported per cause measurements shall equal the total number of E-RABs failed to modify the QoS parameter. In case only a subset of per cause measurements is supported, a sum subcounter will be provided first. d) Each measurement is an integer value. The number of measurements is equal to the number of causes plus a possible sum value identified by the .sum suffix. e) The measurement name has the form ERAB.ModQoSFailNbr.Cause where Cause identifies the cause resulting in the E-RAB Modify failure. f) EUtranCellFDD EUtranCellTDD g) Valid for packet switched traffic h) EPS | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.2.3.3 |
6,590 | 5.2.2.2.1 Selection of the substate after power on | For a UE configured for eCall only mode as specified in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [22], timers T3444 and T3445 are considered to have expired at power on. When the UE is switched on, the substate shall be PLMN-SEARCH if the USIM is available and valid or there are valid entries in the "list of subscriber data". See 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5] for further details. The substate chosen after PLMN-SEARCH, following power on is: a) if no cell can be selected, the substate shall be NO-CELL-AVAILABLE; b) if the UE is not operating in SNPN access operation mode, and no USIM is present, or the USIM is considered invalid by the UE, the substate shall be NO-SUPI; c) if the UE is operating in SNPN access operation mode, and: 1) the selected entry in the "list of subscriber data" does not contain subscription identifier, and no USIM is present, or the USIM is considered invalid by the UE; or 2) no valid entry in the "list of subscriber data" exists; the substate shall be NO-SUPI; d) if a suitable cell has been found: 1) the PLMN identity of the cell is not in one of the forbidden PLMN lists; 2) if the SNPN is not an SNPN selected for localized services in SNPN (see 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]), the SNPN identity of the cell is not in one of the "permanently forbidden SNPNs" list or the "temporarily forbidden SNPNs" list which are, if the MS supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription ; or 3) if the SNPN is an SNPN selected for localized services in SNPN (see 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]), the SNPN identity of the cell is not in one of the "permanently forbidden SNPNs for access for localized services in SNPN" list or "temporarily forbidden SNPNs for access for localized services in SNPN" list, associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription; and the tracking area is not in one of the lists of 5GS forbidden tracking areas, then the substate shall be NORMAL-SERVICE; e) if the selected cell is known not to be able to provide normal service, then the UE shall enter the substate LIMITED-SERVICE; f) if the UE is in manual network selection mode and no cell of the selected PLMN or SNPN has been found, the UE shall enter the substate NO-CELL-AVAILABLE; and g) if the UE is configured for eCall only mode as specified in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [22], the substate shall be eCALL-INACTIVE. | 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.2.2.2.1 |
6,591 | 8.1.1 Receiver antenna capability | The performance requirements are based on UE(s) that utilize one or more antenna receivers. For all test cases, the SNR is defined as where NRX denotes the number of receiver antenna connectors and the superscript receiver antenna connector j. The above SNR definition assumes that the REs are not precoded. The SNR definition does not account for any gain which can be associated to the precoding operation. The relative power of physical channels transmitted is defined in Table C.3.2-1. The SNR requirement applies for the UE categories and CA capabilities given for each test. For enhanced performance requirements type A, the SINR is defined as where NRX denotes the number of reciver antenna connectors and the superscript receiver antenna connector j. The above SINR definition assumes that the REs are not precoded. The SINR definition does not account for any gain which can be associated to the precoding operation. The relative power of physical channels transmitted is defined in Table C.3.2-1. The SINR requirement applies for the UE categories given for each test. For the performance requirements specified in this clause, it is assumed that NRX=2 unless otherwise stated. Table 8.1.1-1: Void | 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.1 |
6,592 | 10.2.8 OFDM baseband signal generation | For an NB-IoT carrier - for which the higher layer parameter operationModeInfo indicates 'inband-DifferentPCI ' and for all NB-IoT downlink physical channels and signals except NPRS, - for which the higher layer parameter operationModeInfo indicates 'Guardband ' or 'Standalone ', - for an NB-IoT carrier for which the higher layer parameter CarrierConfigDedicated-NB or DL-CarrierConfigCommon-NB is present and no inbandCarrierInfo is present, or - for an NB-IoT carrier for which the higher layer parameters CarrierConfigDedicated-NB or DL-CarrierConfigCommon-NB is present and inbandCarrierInfo is present and the higher layers do not indicate is the same as and for all NB-IoT downlink physical channels and signals except NPRS, the time-continuous signal on antenna port in OFDM symbol in a downlink slot is defined by for where , , and is the content of resource element on antenna port . Otherwise, the time-continuous signal on antenna port in OFDM symbol , where is the OFDM symbol index from the start of the last even-numbered subframe, is defined by for where and, if resource element is used for Narrowband IoT except for NPRS, and 0 otherwise including NPRS. The quantity is the frequency location of the center of the Narrowband IoT PRB minus the frequency location of the center of the LTE signal. Only normal CP is supported for Narrowband IoT downlink in this release of the specification. | 3GPP TS 36.211 | Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation | RAN1 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 10.2.8 |
6,593 | A.2.2 More detailed aspects | The following more detailed conventions should be used: - Bullets: - Capitals should be used in the same manner as in other parts of the procedural text i.e. in most cases no capital applies since the bullets are part of the sentence starting with 'The UE shall:' - All bullets, including the last one in a clause, should end with a semi-colon i.e. an ';. - Conditions: - Whenever multiple conditions apply, a semi-colon should be used at the end of each conditions with the exception of the last one, i.e. as in 'if cond1, or cond2. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | A.2.2 |
6,594 | 5.19 Control Plane Load Control, Congestion and Overload Control 5.19.1 General | In order to ensure that the network functions within 5G System are operating under nominal capacity for providing connectivity and necessary services to the UE. Thus, it supports various measures to guard itself under various operating conditions (e.g. peak operating hour, extreme situations). It includes support for load (re-)balancing, overload control and NAS level congestion control. A 5GC NF is considered to be in overload when it is operating over its nominal capacity resulting in diminished performance (including impacts to handling of incoming and outgoing traffic). | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.19 |
6,595 | 6.6.2.5 Abnormal cases on the network side | The following abnormal cases have been identified: a) Collision of network-requested PDU session release procedure and remote UE report procedure: If the SMF receives a REMOTE UE REPORT message during a network-requested PDU session release procedure, and the PDU session indicated in the PDU SESSION RELEASE COMMAND message is the PDU session ID that is in the REMOTE UE REPORT message, the SMF shall abort the remote UE report procedure and proceed with the network-requested PDU session release procedure. b) PDU session inactive for the received PDU session identity: If the PDU session ID in the REMOTE UE REPORT message belongs to any PDU session in state PDU SESSION INACTIVE in the SMF, the SMF shall send the 5GSM STATUS message to the UE with the 5GSM cause #43 "Invalid PDU session identity". | 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.6.2.5 |
6,596 | 16.3.3 Accounting Update | During the life of a PDP context some information related to this PDP context may change (i.e. SGSN address if a Inter-SGSN RA update occurs). Upon reception of an UpdatePDPContextRequest from the SGSN, the GGSN may send an Accounting Request Interim-Update to the AAA server to update the necessary information related to this PDP context (see figure 24). Interim updates are also used when the IPv4 address is allocated/released/re-allocated for deferred IPv4 addressing for the PDP type IPv4v6. If the GGSN receives an UpdatePDPContextRequest from the SGSN that specifically indicates a direct tunnel establishment or a direct tunnel teardown (switching the user plane tunnel end back to the SGSN), and only the GTP user plane address and/or the GTP-U TEID have changed, then the GGSN should not send the Accounting Request Interim-Update to the AAA server. In such cases, the GGSN need not wait for the RADIUS AccountingResponse from the AAA server message before sending the UpdatePDPContextResponse to the SGSN. The GGSN may delete the PDP context if the AccountingResponse is not received from the AAA. NOTE: As shown the GGSN need not wait for the RADIUS AccountingResponse from the AAA server message to send the UpdatePDPContextResponse to the SGSN. The GGSN may delete the PDP context if the AccountingResponse is not received from the AAA. Figure 24: RADIUS for PDP context Update | 3GPP TS 29.061 | Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) | CT WG3 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 16.3.3 |
6,597 | β PUCCH-PowerControl | The IE PUCCH-PowerControl is used to configure UE-specific parameters for the power control of PUCCH. PUCCH-PowerControl information element -- ASN1START -- TAG-PUCCH-POWERCONTROL-START PUCCH-PowerControl ::= SEQUENCE { deltaF-PUCCH-f0 INTEGER (-16..15) OPTIONAL, -- Need R deltaF-PUCCH-f1 INTEGER (-16..15) OPTIONAL, -- Need R deltaF-PUCCH-f2 INTEGER (-16..15) OPTIONAL, -- Need R deltaF-PUCCH-f3 INTEGER (-16..15) OPTIONAL, -- Need R deltaF-PUCCH-f4 INTEGER (-16..15) OPTIONAL, -- Need R p0-Set SEQUENCE (SIZE (1..maxNrofPUCCH-P0-PerSet)) OF P0-PUCCH OPTIONAL, -- Need M pathlossReferenceRSs SEQUENCE (SIZE (1..maxNrofPUCCH-PathlossReferenceRSs)) OF PUCCH-PathlossReferenceRS OPTIONAL, -- Need M twoPUCCH-PC-AdjustmentStates ENUMERATED {twoStates} OPTIONAL, -- Need S ..., [[ pathlossReferenceRSs-v1610 SetupRelease { PathlossReferenceRSs-v1610 } OPTIONAL -- Need M ]] } P0-PUCCH ::= SEQUENCE { p0-PUCCH-Id P0-PUCCH-Id, p0-PUCCH-Value INTEGER (-16..15) } P0-PUCCH-Id ::= INTEGER (1..8) PathlossReferenceRSs-v1610 ::= SEQUENCE (SIZE (1..maxNrofPUCCH-PathlossReferenceRSsDiff-r16)) OF PUCCH-PathlossReferenceRS-r16 PUCCH-PathlossReferenceRS ::= SEQUENCE { pucch-PathlossReferenceRS-Id PUCCH-PathlossReferenceRS-Id, referenceSignal CHOICE { ssb-Index SSB-Index, csi-RS-Index NZP-CSI-RS-ResourceId } } PUCCH-PathlossReferenceRS-r16 ::= SEQUENCE { pucch-PathlossReferenceRS-Id-r16 PUCCH-PathlossReferenceRS-Id-v1610, referenceSignal-r16 CHOICE { ssb-Index-r16 SSB-Index, csi-RS-Index-r16 NZP-CSI-RS-ResourceId } } PUCCH-PowerControlSetInfo-r17 ::= SEQUENCE { pucch-PowerControlSetInfoId-r17 PUCCH-PowerControlSetInfoId-r17, p0-PUCCH-Id-r17 P0-PUCCH-Id, pucch-ClosedLoopIndex-r17 ENUMERATED { i0, i1 }, pucch-PathlossReferenceRS-Id-r17 PUCCH-PathlossReferenceRS-Id-r17 } PUCCH-PowerControlSetInfoId-r17 ::= INTEGER (1.. maxNrofPowerControlSetInfos-r17) -- TAG-PUCCH-POWERCONTROL-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | β |
6,598 | 8.2.1.3.5 Minimum Requirement 2 Tx Antenna Port (Superposed transmission) | The requirements are specified in Table 8.2.1.3.5-2, with the addition of the parameters in Table 8.2.1.3.5-1 and the downlink physical channel setup according to Annex C.3.2. The purpose is to verify the minimun performance of open-loop spatial multiplexing with 2 transmitter antennas superposed with simultaneous PDSCH interference. Table 8.2.1.3.5-1: Test Parameters for Minimum Requirement 2 Tx Antenna Port - Superposed transmission (FRC) Table 8.2.1.3.5-2: Minimum Performance for Minimum Requirement 2 Tx Antenna Port - Superposed transmission (FRC) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.2.1.3.5 |
6,599 | 5.5.4.10 Event I1 (Interference becomes higher than threshold) | The UE shall: 1> consider the entering condition for this event to be satisfied when condition I1-1, as specified below, is fulfilled; 1> consider the leaving condition for this event to be satisfied when condition I1-2, as specified below, is fulfilled. Inequality I1-1 (Entering condition) Mi β Hys > Thresh Inequality I1-2 (Leaving condition) Mi+ Hys < Thresh The variables in the formula are defined as follows: Mi is the measurement result of the interference, not taking into account any offsets. Hys is the hysteresis parameter for this event (i.e. hysteresis as defined within reportConfigNR for this event). Thresh is the threshold parameter for this event (i.e. i1-Threshold as defined within reportConfigNR for this event). Mi, Thresh are expressed in dBm. Hys is expressed in dB. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.5.4.10 |
6,600 | 9.2.7.2 Frame structure type 3 wth TDD Pcell | The following requirements apply to UE Category β₯1. For the parameters specified in Table 9.2.7.2-1, Table 9.2.7.2-2and using the downlink physical channels specified in tables C.3.2-1 and C.3.2-2, two sets of CQI reports are obtained for LAA Scell, The first one is obtained by reports whose reference resource is in the downlink subframes with 6 dB transmission power boost, i.e., high power subframes. The second one is obtained by reports whose reference resource is in the downlink subframe with 0 dB transmission power boost, i.e., low power subframe. In the test, PDSCH transport format in high power subframe is determined by first set of CQI reports and PDSCH transport format in low power subframe is determined by second set of CQI reports. The reported CQI value in the first set of reports shall be in the range of Β±1 of the reported median more than 90% of the first set of reports. The reported CQI value in the second set of reports shall be in the range of Β±1 of the reported median more than 90% of the second set of reports. If the PDSCH BLER in the high power subframes using the transport format indicated by wideband CQI median is less than or equal to 0.1, the BLER in high power subframes using the transport format indicated by the (wideband CQI median + 1) shall be greater than 0.1. If the PDSCH BLER in high power subframes using the transport format indicated by the wideband CQI median is greater than 0.1, the BLER in high power subframes using transport format indicated by (wideband CQI median β 1) shall be less than or equal to 0.1. If the PDSCH BLER in the low power subframes using the transport format indicated by wideband CQI median is less than or equal to 0.1, the BLER in low power subframes using the transport format indicated by the (wideband CQI median + 1) shall be greater than 0.1. If the PDSCH BLER in the low power subframes using the transport format indicated by the wideband CQI median is greater than 0.1, the BLER in low power subframes using transport format indicated by (wideband CQI median β 1) shall be less than or equal to 0.1. The value of the wideband CQI for the first set of CQI report minus the wideband CQI median for second set of CQI shall be larger than or equal to 2 in Test 1 and Test 2. Table 9.2.7.2-1: Parameters for PUSCH 3-1 static test on TDD Pcell Table 9.2.7.2-2: PUSCH 3-1 static test on LAA Scell | 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.2.7.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.