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,101 | 5.7.1.3 Control of QoS Flows | The following options are supported to control QoS Flows: 1) For Non-GBR QoS Flows, and when standardized 5QIs or pre-configured 5QIs are used and when the 5QI is within the range of the QFI (i.e. a value less than 64), the 5QI value may be used as the QFI of the QoS Flow. (a) A default ARP shall be pre-configured in the AN; or (b) The ARP and the QFI shall be sent to RAN over N2 at PDU Session Establishment or at PDU Session Modification and when NG-RAN is used every time the User Plane of the PDU Session is activated; and 2) For all other cases (including GBR and Non-GBR QoS Flows), a dynamically assigned QFI shall be used. The 5QI value may be a standardized, pre-configured or dynamically assigned. The QoS profile and the QFI of a QoS Flow shall be provided to the (R)AN over N2 at PDU Session Establishment/Modification and when NG-RAN is used every time the User Plane of the PDU Session is activated. Only options 1b and 2 may apply to 3GPP ANs. Options 1a, 1b and 2 may apply to Non-3GPP access. NOTE: Pre-configured 5QI values cannot be used when the UE is roaming. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.7.1.3 |
6,102 | A.7.1 ABBA parameter values | ABBA parameter is provided to the UE from SEAF and shall be used as an input parameter for KAMF derivation. To support flexible set of security features ABBA parameter is defined when security features change. To ensure forward compatibility, the ABBA parameter is a variable length parameter. The SEAF shall set the ABBA parameter to 0x0000. The UE shall use the ABBA parameter provided by the SEAF in the calculation of KAMF. The following values have been defined for this parameter. Table A.7.1-1: ABBA parameter definitions | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | A.7.1 |
6,103 | – InterRAT-Parameters | The IE InterRAT-Parameters is used convey UE capabilities related to the other RATs. InterRAT-Parameters information element -- ASN1START -- TAG-INTERRAT-PARAMETERS-START InterRAT-Parameters ::= SEQUENCE { eutra EUTRA-Parameters OPTIONAL, ..., [[ utra-FDD-r16 UTRA-FDD-Parameters-r16 OPTIONAL ]] } EUTRA-Parameters ::= SEQUENCE { supportedBandListEUTRA SEQUENCE (SIZE (1..maxBandsEUTRA)) OF FreqBandIndicatorEUTRA, eutra-ParametersCommon EUTRA-ParametersCommon OPTIONAL, eutra-ParametersXDD-Diff EUTRA-ParametersXDD-Diff OPTIONAL, ... } EUTRA-ParametersCommon ::= SEQUENCE { mfbi-EUTRA ENUMERATED {supported} OPTIONAL, modifiedMPR-BehaviorEUTRA BIT STRING (SIZE (32)) OPTIONAL, multiNS-Pmax-EUTRA ENUMERATED {supported} OPTIONAL, rs-SINR-MeasEUTRA ENUMERATED {supported} OPTIONAL, ..., [[ ne-DC ENUMERATED {supported} OPTIONAL ]], [[ nr-HO-ToEN-DC-r16 ENUMERATED {supported} OPTIONAL ]] } EUTRA-ParametersXDD-Diff ::= SEQUENCE { rsrqMeasWidebandEUTRA ENUMERATED {supported} OPTIONAL, ... } UTRA-FDD-Parameters-r16 ::= SEQUENCE { supportedBandListUTRA-FDD-r16 SEQUENCE (SIZE (1..maxBandsUTRA-FDD-r16)) OF SupportedBandUTRA-FDD-r16, ... } SupportedBandUTRA-FDD-r16 ::= ENUMERATED { bandI, bandII, bandIII, bandIV, bandV, bandVI, bandVII, bandVIII, bandIX, bandX, bandXI, bandXII, bandXIII, bandXIV, bandXV, bandXVI, bandXVII, bandXVIII, bandXIX, bandXX, bandXXI, bandXXII, bandXXIII, bandXXIV, bandXXV, bandXXVI, bandXXVII, bandXXVIII, bandXXIX, bandXXX, bandXXXI, bandXXXII} -- TAG-INTERRAT-PARAMETERS-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
6,104 | 6.5.4.4.3 Handling of network rejection due to ESM cause other than ESM cause #26 | If the ESM cause value is not #26 "insufficient resources", and the Back-off timer value IE is included, the UE shall behave as follows 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): - 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 bearer resource modification procedure and PLMN and combination and not send another BEARER RESOURCE MODIFICATION REQUEST message with exception of those identified in clause 6.5.4.1, in the PLMN for the same until the back-off timer expires, the UE is switched off or the USIM is removed; - if the timer value indicates that this timer is deactivated, the UE shall not send another BEARER RESOURCE MODIFICATION REQUEST message with exception of those identified in clause 6.5.4.1, in the PLMN for the same until the UE is switched off or the USIM is removed; and - if the timer value indicates zero, the UE may send another BEARER RESOURCE MODIFICATION REQUEST message in the PLMN for the same . If the Back-off timer value IE is not included, then the UE shall ignore the Re-attempt indicator IE provided by the network, if any. 1) Additionally, if the ESM cause value is #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 a PLMN that is within the EHPLMN list (if the EHPLMN list is present) or 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 #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 bearer resource modification 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 BEARER RESOURCE MODIFICATION REQUEST message with exception of those identified in clause 6.5.4.1, in the PLMN for the same APN. If the back-off timer is started upon receipt of BEARER RESOURCE MODIFICATION 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 BEARER RESOURCE MODIFICATION REQUEST message for the same APN in the new PLMN, if the back-off timer is not running and is not deactivated for the bearer resource modification procedure and the combination of new PLMN and APN. Furthermore as an implementation option, for the ESM cause values #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 BEARER RESOURCE MODIFICATION REQUEST message for the same APN that was sent by the UE, 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 modification procedure for the same PLMN and APN combination in A/Gb or Iu mode or a PDU session modification 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 modification procedure for the same PLMN and APN combination in A/Gb or Iu mode and a PDU session modification 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 bearer resource modification 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 upon receipt of an MODIFY 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 BEARER RESOURCE MODIFICATION 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 BEARER RESOURCE MODIFICATION 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 timers 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 MODIFICATION 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 BEARER RESOURCE MODIFICATION 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 BEARER RESOURCE MODIFICATION 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 timer 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 BEARER RESOURCE MODIFICATION 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 BEARER RESOURCE MODIFICATION 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. The further actions to be performed by the UE are implementation dependent as part of upper layers responsibility. | 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.4.4.3 |
6,105 | 8.112 Load Control Information | Load Control Information is a grouped IE containing a number of other IEs. Which of those IEs are mandatory, optional or conditional and the conditions that apply are GTP message specific, and described in the corresponding clause under clause 7. Load Control Information may be repeated within a message with exactly the same Type and Instance values to represent a list of Load Control Information. Load Control Information is coded as depicted in Table 8.112-1. Table 8.112-1: Load Control Information Grouped Type | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 8.112 |
6,106 | 8.2.2.3.6 Minimum Requirement 2 Tx Antenna Port (network-based CRS interference mitigation) | The requirements are specified in Table 8.2.2.3.6-2, with the addition of parameters in Table 8.2.2.3.6-1 and the downlink physical channel setup according to Annex C.3.2. The purpose is to verify the performance of open-loop spatial multiplexing performence with 2 transmit antennas when the PDSCH transmission in the serving cell is interfered by CRS of one dominant interfering cell with network-based CRS interference mitigation. In Table 8.2.2.3.6-1, Cell 1 is the serving cell, and Cell 2 is interfering cell. The downlink physical channel setup is according to Annex C.3.2 for each of Cell 1 and Cell 2 respectively. Table 8.2.2.3.6-1: Test parameters for Larger Delay CDD (FRC) with network-based CRS interference mitigation Table 8.2.2.3.6-2: Minimum performance Large Delay CDD (FRC) with network-based CRS interference mitigation | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.2.2.3.6 |
6,107 | 16.10.5.3.3 Handover between Multicast-supporting cell and Multicast non-supporting cell | During an MBS multicast session, at mobility from an MBS-supporting cell to an MBS non-supporting cell, the target gNB sets up PDU Session Resources mapped to the MBS multicast session. The 5GC infers from the absence of an "MBS-support" indication from gNB in the Path Switch Request message (Xn handover) or Handover Request Acknowledge message (NG handover) that MBS multicast data packets delivery has to be switched to 5GC individual MBS traffic delivery as specified in TS 23.247[ Architectural enhancements for 5G multicast-broadcast services ] [45]. If data forwarding is applied, the source gNB infers from the handover preparation response message that the target gNB does not support MBS and changes the QFI(s) in the forwarded packets to the associated PDU Session QFI(s) if respective mapping information is available. The source gNB may be aware that the target gNB is non-MBS supporting already before Handover Preparation. For mobility from MBS non-supporting cell to MBS-supporting cell, the existing Xn/NG handover procedures apply. The 5GC infers from the presence of the "MBS-support" indicator from gNB in the Path Switch Request message (Xn handover) or in the Handover Request Acknowledge message (NG handover) that MBS multicast data packets delivery can be switched from 5GC Individual MBS traffic delivery to 5GC Shared MBS traffic delivery. After Xn handover, the SMF triggers switching MBS multicast data packets delivery from 5GC Individual to 5GC Shared MBS traffic delivery by providing MBS Session IDs joined by the UE to the target gNB by means of the PDU Session Resource Modification procedure. For NG handover, the SMF provides the MBS Session IDs joined by the UE to the target gNB by means of NGAP Handover Request. Minimization of data loss and duplication avoidance may be applied by means of identical MBS QFI SNs received over the shared NG-U tunnel against those received over unicast NG-U tunnels or forwarding tunnels. Mobility from a multicast-supporting cell to a multicast non-supporting cell can be achieved by switching the MRB to a DRB in the source gNB before a handover. NOTE: A UE may be handed over to a target gNB not supporting MBS without prior reconfiguration from MRB to the DRB in the source gNB. In this case, the AS configuration may not be comprehended by the target gNB causing full configuration. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.10.5.3.3 |
6,108 | 4.4.1 Location updating procedure | The location updating procedure is a general procedure which is used for the following purposes: - normal location updating (described in this subclause); - periodic updating (see subclause 4.4.2); or - IMSI attach (see subclause 4.4.3). The normal location updating procedure is used to update the registration of the actual Location Area of a mobile station in the network. The location updating type information element in the LOCATION UPDATING REQUEST message shall indicate normal location updating. The conditions under which the normal location updating procedure is used by a mobile station in the MM IDLE state are defined for each service state in subclause 4.2.2. Only applicable for mobile stations supporting VGCS listening or VBS listening: A mobile station in RR group receive mode is in the MM IDLE state, substate RECEIVING GROUP CALL (NORMAL SERVICE) or RECEIVING GROUP CALL (LIMITED SERVICE). To perform a location updating, the MS in RR group receive mode shall leave the group receive mode, establish an independent dedicated RR connection to perform the location updating as described above and return to the RR group receive mode afterwards. The MS shall also start the normal location updating procedure: a) if the network indicates that the mobile station is unknown in the VLR as a response to MM connection establishment request; b) void c) when the MS, configured to use CS fallback and SMS over SGs, or SMS over SGs only, enters a GERAN or UTRAN cell in network operation mode II and timer T3423 has expired or is in the GERAN or UTRAN cell in network operation mode II when timer T3423 expires; NOTE 1: Timer T3423 is specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120]. d) when the MS, configured to use CS fallback and SMS over SGs, or SMS over SGs only, enters a GERAN or UTRAN cell after intersystem change from S1 mode to Iu or A/Gb mode, if timer T3346 is running, and the location area of the current cell is the same as the stored location area; NOTE 2: If inter-system change is due to a mobile originating CS call, the location updating procedure can be performed after the RR connection is released unless the MS moves back to E-UTRAN. e) when the MS is both IMSI attached for GPRS and non-GPRS services and enters a new routing area where the network operates in network operation mode I and timer T3346 is running. f) when the network is operating in network operation mode I, timer T3346 is running, timer T3246 is not running, and due to manual CSG selection the MS has selected a CSG cell whose CSG identity and associated PLMN identity are not included in the Allowed CSG list or in the Operator CSG list of the MS; g) when due to a manual CSG selection the MS has selected a CSG cell whose CSG identity and associated PLMN identity are not included in the MS's Allowed CSG list or in the MS's Operator CSG list; h) when the network is operating in network operation mode I, T3346 is running, update status is not U1 UPDATED and the user manually selects the current PLMN; or i) when the MS is configured to use CS fallback and SMS over SGs, or SMS over SGs only, and the TIN indicates "GUTI", enters a GERAN or UTRAN cell after intersystem change from S1 mode to Iu or A/Gb mode in NMO II and timer T3412 is not running. If the MS, configured to use CS fallback and SMS over SGs, enters a GERAN or UTRAN cell, after intersystem change from S1 mode to Iu or A/Gb mode due to CS fallback, and the location area of the current cell is not available, the MS may initiate the location updating procedure. When the MS supporting N1 mode in MS operation modes A or B moves from NG-RAN coverage to GERAN coverage, or from NG-RAN coverage to UTRAN coverage, and the network operates in network operation mode II, the MS may intiate the normal location updating procedure. To limit the number of consecutive unsuccessful location updating attempts made, an attempt counter is used. The detailed handling of the attempt counter is described in subclauses 4.4.4.5 to 4.4.4.9. The mobile equipment shall contain a list of "forbidden location areas for roaming", as well as a list of "forbidden location areas for regional provision of service". These lists shall be erased when the MS is switched off or when the SIM/USIM is removed, and periodically (with period in the range 12 to 24 hours). When the lists are erased, the MS performs a cell selection according to 3GPP TS 43.022[ None ] [82] and 3GPP TS 25.304[ None ] [98]. The location area identification received on the BCCH that triggered the location updating request shall be added to the suitable list whenever a LOCATION AREA UPDATING REJECT message is received with the cause "Roaming not allowed in this location area", "Location Area not allowed", or "No suitable cells in Location Area". The lists shall accommodate each 10 or more location area identifications. When the list is full and a new entry has to be inserted, the oldest entry shall be deleted. In a shared network, the MS shall choose one of the PLMN identities as specified in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [14]. The MS shall construct the Location Area Identification of the cell from this chosen PLMN identity and the LAC received on the BCCH. If the constructed LAI is different from the stored LAI, the MS shall initiate the location updating procedure. For: - a shared GERAN, in A/Gb mode, the chosen PLMN identity shall be indicated to the GERAN in the LOCATION UPDATING REQUEST message using the Skip Indicator IE as specified in subclause 10.3.1. - a shared UTRAN, the chosen PLMN identity shall be indicated to the UTRAN in the RRC INITIAL DIRECT TRANSFER message (see 3GPP TS 25.331[ None ] [23c]). For GERAN Iu mode, network sharing is not supported. Whenever a LOCATION UPDATING REJECT message with the cause "PLMN not allowed" is received by the MS, the PLMN identity used to construct the LAI which triggered the location updating procedure shall be stored in the "forbidden PLMN list" and if the MS is configured to use timer T3245 (see 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [135] or 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [112]) then the MS shall start timer T3245 and proceed as described in subclause 4.1.1.6. Whenever a LOCATION UPDATING REJECT message is received by the MS with the cause "Roaming not allowed in this location area", "Location Area not allowed", or "No suitable cells in Location Area", the constructed LAI which triggered the location updating procedure shall be stored in the suitable list. The cell selection processes in the different states are described in 3GPP TS 43.022[ None ] [82] and 3GPP TS 45.008[ None ] [34]. The location updating procedure is always initiated by the mobile station. In the case that the mobile station is initiating an emergency call but, due to cell re-selection or redirection by the network, it moves to a different LAI then the mobile station may delay the location updating procedure in the new LA until after the emergency call is completed. | 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.1 |
6,109 | 5.1.2 Random Access Resource selection | The Random Access Resource selection procedure shall be performed as follows: - for BL UEs or UEs in enhanced coverage or NB-IoT UEs, if EDT is initiated by the upper layers: - if the message size (UL data available for transmission plus MAC header and, where required, MAC control elements) is larger than the TB size signalled in edt-TBS for the selected enhanced coverage level for EDT; or - if the PRACH resource associated with EDT for the selected enhanced coverage level is not available: - indicate to upper layers that EDT is cancelled; - for BL UEs or UEs in enhanced coverage, select the PRACH resource set corresponding to the selected enhanced coverage level. For EDT, the PRACH resource set shall correspond to the set associated with EDT for the selected enhanced coverage level. - if, except for NB-IoT, ra-PreambleIndex (Random Access Preamble) and ra-PRACH-MaskIndex (PRACH Mask Index) have been explicitly signalled and ra-PreambleIndex is not 000000: - the Random Access Preamble and the PRACH Mask Index are those explicitly signalled; - else if, for NB-IoT, ra-PreambleIndex (Random Access Preamble) and PRACH resource have been explicitly signalled: - the PRACH resource is that explicitly signalled; - if the ra-PreambleIndex signalled is not 000000: - if ra-CFRA-Config is configured: - the Random Access Preamble is set to nprach-SubcarrierOffset + nprach-NumCBRA-StartSubcarriers + (ra-PreambleIndex modulo (nprach-NumSubcarriers - nprach-NumCBRA-StartSubcarriers)), where nprach-SubcarrierOffset, nprach-NumCBRA-StartSubcarriers and nprach-NumSubcarriers are parameters in the currently used PRACH resource. - else: - the Random Access Preamble is set to nprach-SubcarrierOffset + (ra-PreambleIndex modulo nprach-NumSubcarriers), where nprach-SubcarrierOffset and nprach-NumSubcarriers are parameters in the currently used PRACH resource. - else: - select the Random Access Preamble group according to the PRACH resource and the support for multi-tone Msg3 transmission. A UE supporting multi-tone Msg3 shall only select the single-tone Msg3 Random Access Preambles group if there is no multi-tone Msg3 Random Access Preambles group. - randomly select a Random Access Preamble within the selected group. - else the Random Access Preamble shall be selected by the MAC entity as follows: - if the UE is a BL UE or UE in enhanced coverage and EDT is initiated: - select the Random Access Preambles group corresponding to PRACH resource for EDT for the selected enhanced coverage level. - else if the UE is a BL UE or UE in enhanced coverage and Random Access Preamble group B does not exist: - select the Random Access Preambles group corresponding to the selected enhanced coverage level. - else if the UE is an NB-IoT UE: - if the UE supports carrier specific NRSRP thresholds for NPRACH resource selection and rsrp-ThresholdsPrachInfoList-r16 is signalled for a carrier in ul-ConfigList: - if the measured RSRP is lower than the RSRP threshold corresponding to the selected enhanced coverage level in rsrp-ThresholdsPrachInfoList-r16: - do not consider the PRACH resource on this non-anchor carrier for PRACH resource selection. - randomly select one of the PRACH resources corresponding to the selected enhanced coverage level according to the configured probability distribution, and select the Random Access Preambles group corresponding to the PRACH resource and the support for multi-tone Msg3 transmission. A UE supporting multi-tone Msg3 shall only select the single-tone Msg3 Random Access Preambles group if there is no multi-tone Msg3 Random Access Preambles group. For EDT, the PRACH resource shall correspond to resource associated with EDT for the selected enhanced coverage level. - else if Msg3 has not yet been transmitted, the MAC entity shall: - if Random Access Preambles group B exists and any of the following events occur: - the potential message size (UL data available for transmission plus MAC header and, where required, MAC control elements) is greater than messageSizeGroupA and the pathloss is less than PCMAX,c (of the Serving Cell performing the Random Access Procedure) – preambleInitialReceivedTargetPower – deltaPreambleMsg3 – messagePowerOffsetGroupB; - the Random Access procedure was initiated for the CCCH logical channel and the CCCH SDU size plus MAC header is greater than messageSizeGroupA; - select the Random Access Preambles group B; - else: - select the Random Access Preambles group A. - else, if Msg3 is being retransmitted, the MAC entity shall: - select the same group of Random Access Preambles as was used for the preamble transmission attempt corresponding to the first transmission of Msg3. - randomly select a Random Access Preamble within the selected group. The random function shall be such that each of the allowed selections can be chosen with equal probability; - except for NB-IoT, set PRACH Mask Index to 0. - determine the next available subframe containing PRACH permitted by the restrictions given by the prach-ConfigIndex (except for NB-IoT), the PRACH Mask Index (except for NB-IoT, see clause 7.3), physical layer timing requirements, as specified in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [2], and in case of NB-IoT, the subframes occupied by PRACH resources related to a higher enhanced coverage level (a MAC entity may take into account the possible occurrence of measurement gaps when determining the next available PRACH subframe); - except for NB-IoT: - if the transmission mode is TDD and the PRACH Mask Index is equal to zero: - if ra-PreambleIndex was explicitly signalled and it was not 000000 (i.e., not selected by MAC): - randomly select, with equal probability, one PRACH from the PRACHs available in the determined subframe. - else: - randomly select, with equal probability, one PRACH from the PRACHs available in the determined subframe and the next two consecutive subframes. - else: - determine a PRACH within the determined subframe in accordance with the requirements of the PRACH Mask Index, if any. - for NB-IoT UEs, BL UEs or UEs in enhanced coverage, select the ra-ResponseWindowSize and mac-ContentionResolutionTimer corresponding to the selected enhanced coverage level and PRACH. - proceed to the transmission of the Random Access Preamble (see clause 5.1.3). | 3GPP TS 36.321 | Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification | RAN2 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 5.1.2 |
6,110 | 16.18 Support for Aerial UE Communication 16.18.1 General | NR connectivity for UEs capable of Aerial communication is supported via the following functionalities: - subscription-based Aerial UE identification and authorization, as specified in TS 23.502[ Procedures for the 5G System (5GS) ] [22], clause 5.2.3.3.1; - height reporting based on the measurement event(s) where the UE's altitude has crossed a network-configured reference altitude threshold; - height-dependent configurations which apply only to specific height regions; - interference detection based on a measurement reporting that is triggered when a configured number of cells (i.e. larger than one) fulfils the triggering criteria simultaneously; - signalling of flight path information from UE to NG-RAN and from the source gNB to target gNB during handover; - location information reporting, including UE's horizontal and vertical velocity; - broadcasting of BRID and DAA messages via PC5 interface. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.18 |
6,111 | 4.13.8.5 Paging | In the case of satellite access that provides discontinuous network coverage, the MME may utilize sub-area paging (e.g. first page in the last known ECGI or TA and retransmission in all registered TAs). The MME may utilize the location information as received at or before the S1 release due to the discontinuous coverage for paging optimisation. The MME may e.g. receive UE location from eNodeB during the Attach or TAU procedure e.g. triggered for Mobility Management and Power Saving Optimization for discontinuous network coverage as described in clause 4.13.8.2, or the MME may request the Location Reporting Procedure when the UE is in ECM_CONNECTED state as described in clause 5.9.1. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.13.8.5 |
6,112 | 5.2.4 Secure storage and processing of subscription credentials | The following requirements apply for the storage and processing of the subscription credentials used to access the 5G network: The subscription credential(s) shall be integrity protected within the UE using a tamper resistant secure hardware component. The long-term key(s) of the subscription credential(s) (i.e. K) shall be confidentiality protected within the UE using a tamper resistant secure hardware component. The long-term key(s) of the subscription credential(s) shall never be available in the clear outside of the tamper resistant secure hardware component. The authentication algorithm(s) that make use of the subscription credentials shall always be executed within the tamper resistant secure hardware component. It shall be possible to perform a security evaluation / assessment according to the respective security requirements of the tamper resistant secure hardware component. NOTE: The security assessment scheme used for the security evaluation of the tamper resistant secure hardware component is outside the scope of 3GPP specifications. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 5.2.4 |
6,113 | 5.4.3.2 Receipt of a DISCONNECT message from the mobile station. | The call control entity in the network in any state except the "null" state and the "release request" state shall, upon receipt of a DISCONNECT message: - Stop all running call control timers; - initiate procedures to clear the network connection and the call to the remote user; - send a RELEASE message to its peer entity; - start timer T308; and - enter the "release request" state. NOTE: The RELEASE message has only local significance and does not imply an acknowledgement of clearing from the remote user. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.4.3.2 |
6,114 | 9.3.1.2.2 TDD | For the parameters specified in Table 9.3.1.2.2-1, and using the downlink physical channels specified in Annex C.3.2, the minimum requirements are specified in Table 9.3.1.2.2-2 and by the following a) a sub-band differential CQI offset level of 0 shall be reported at least % of the time but less than % for each sub-band; b) the ratio of the throughput obtained when transmitting on a randomly selected sub-band among the sub-bands with the highest differential CQI offset level the corresponding TBS and that obtained when transmitting the TBS indicated by the reported wideband CQI median on a randomly selected sub-band in set S shall be ≥ ; c) when transmitting on a randomly selected sub-band among the sub-bands with the highest differential CQI offset level the corresponding TBS, the average BLER for the indicated transport formats shall be greater or equal to 0.05. The requirements only apply for sub-bands of full size and the random scheduling across the sub-bands is done by selecting a new sub-band in each TTI for FDD, each available downlink transmission instance for TDD. Sub-bands of a size smaller than full size are excluded from the test. Table 9.3.1.2.2-1 Sub-band test for TDD Table 9.3.1.2.2-2 Minimum requirement (TDD) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 9.3.1.2.2 |
6,115 | 20.4 Temporary UE capability restriction and removal of restriction | For MUSIM operation, a MUSIM device in RRC_CONNECTED state in Network A may indicate its preference on temporary UE capability restriction or removal of restriction with Network A when the MUSIM device needs transmission or reception in Network B (e.g., including start/stop connection to Network B). Network A is NR and Network B can either be E-UTRA or NR. The MUSIM device may request a temporary capability restriction only after the Network signals via RRC that this is allowed. When configured to do so, a MUSIM device can indicate one or more of the following temporary capability restriction or removal of restriction to the Network A: - A MUSIM device can explicitly request SCell(s) or SCG to be released; - A MUSIM device can indicate its preference on temporary maximum MIMO layers and/or supported channel bandwidth for specific serving cells for both UL/DL; - A MUSIM device can indicate its preference on the temporary maximum number of CCs per UL/DL; - A MUSIM device can indicate its preference on the concerned band(s) or band combination(s) (e.g. forbidden and/or affected band(s) or band combination(s)) based on a band-filter list configured by network. For affected band(s) and band combination(s), this preference can include temporary maximum MIMO layers and/or supported channel bandwidth for both UL/DL; - A MUSIM device can indicate the measurement gap requirement changes. When it is allowed by Network A in SIB1, a MUSIM device can indicate to the Network A that its capabilities are temporarily restricted in RRCSetupComplete/RRCResumeComplete message while the MUSIM device is already in RRC_CONNECTED state in Network B. When a MUSIM device is in RRC_CONNECTED state in both Network A and Network B, if Network B is NR, it is up to UE implementation to select which network to request temporary UE capability restriction; if Network B is E-UTRA, the request for temporary UE capability restriction can only be performed on Network A. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 20.4 |
6,116 | 5.5.2 Signalling data integrity | The AMF shall support integrity protection and replay protection of NAS-signalling. The AMF shall support the following integrity protection algorithms: - NIA-0, 128-NIA1, 128-NIA2 as defined in Annex D of the present document. The AMF may support the following integrity protection algorithm: - 128-NIA3 as defined in Annex D of the present document. NIA0 shall be disabled in AMF in the deployments where support of unauthenticated emergency session is not a regulatory requirement. All NAS signalling messages except those explicitly listed in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [35] as exceptions shall be integrity-protected with an algorithm different to NIA-0 except for emergency calls. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 5.5.2 |
6,117 | 5.31.4.2 Establishment of N3 data transfer during Data Transport in Control Plane CIoT 5GS Optimisation | If UE and AMF have successfully negotiated N3 data transfer in addition to Control Plane CIoT 5GS Optimisation based on the Preferred and Supported Network Behaviour as defined in clause 5.31.2, then the SMF may decide to establish N3 data transfer for any PDU session for which Control Plane Only Indicator was not included based on local SMF decision e.g. based on the amount of data transferred in UL or DL using Control Plane CIoT 5GS Optimisation. In that case, the SMF initiates the SMF-triggered N3 data transfer establishment procedure as described in clause 4.2.10.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. If UE and AMF successfully negotiate N3 data transfer in addition to Control Plane CIoT 5GS Optimisation based on the Preferred and Supported Network Behaviour as defined in clause 5.31.2, then the UE may decide to establish N3 data transfer for any PDU session for which Control Plane Only Indicator was not included based on local decision, e.g. based on the amount of data to be transferred. In that case, the UE performs the UE triggered N3 data transfer establishment procedure as described in clause 4.2.10.1 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.31.4.2 |
6,118 | – ServingCellConfigCommon | The IE ServingCellConfigCommon is used to configure cell specific parameters of a UE's serving cell. The IE contains parameters which a UE would typically acquire from SSB, MIB or SIBs when accessing the cell from IDLE. With this IE, the network provides this information in dedicated signalling when configuring a UE with a SCells or with an additional cell group (SCG). It also provides it for SpCells (MCG and SCG) upon reconfiguration with sync. ServingCellConfigCommon information element -- ASN1START -- TAG-SERVINGCELLCONFIGCOMMON-START ServingCellConfigCommon ::= SEQUENCE { physCellId PhysCellId OPTIONAL, -- Cond HOAndServCellAdd, downlinkConfigCommon DownlinkConfigCommon OPTIONAL, -- Cond HOAndServCellAdd uplinkConfigCommon UplinkConfigCommon OPTIONAL, -- Need M supplementaryUplinkConfig UplinkConfigCommon OPTIONAL, -- Need S n-TimingAdvanceOffset ENUMERATED { n0, n25600, n39936 } OPTIONAL, -- Need S ssb-PositionsInBurst CHOICE { shortBitmap BIT STRING (SIZE (4)), mediumBitmap BIT STRING (SIZE (8)), longBitmap BIT STRING (SIZE (64)) } OPTIONAL, -- Cond AbsFreqSSB ssb-periodicityServingCell ENUMERATED { ms5, ms10, ms20, ms40, ms80, ms160, spare2, spare1 } OPTIONAL, -- Need S dmrs-TypeA-Position ENUMERATED {pos2, pos3}, lte-CRS-ToMatchAround SetupRelease { RateMatchPatternLTE-CRS } OPTIONAL, -- Need M rateMatchPatternToAddModList SEQUENCE (SIZE (1..maxNrofRateMatchPatterns)) OF RateMatchPattern OPTIONAL, -- Need N rateMatchPatternToReleaseList SEQUENCE (SIZE (1..maxNrofRateMatchPatterns)) OF RateMatchPatternId OPTIONAL, -- Need N ssbSubcarrierSpacing SubcarrierSpacing OPTIONAL, -- Cond HOAndServCellWithSSB tdd-UL-DL-ConfigurationCommon TDD-UL-DL-ConfigCommon OPTIONAL, -- Cond TDD ss-PBCH-BlockPower INTEGER (-60..50), ..., [[ channelAccessMode-r16 CHOICE { dynamic NULL, semiStatic SemiStaticChannelAccessConfig-r16 } OPTIONAL, -- Cond SharedSpectrum discoveryBurstWindowLength-r16 ENUMERATED {ms0dot5, ms1, ms2, ms3, ms4, ms5} OPTIONAL, -- Need R ssb-PositionQCL-r16 SSB-PositionQCL-Relation-r16 OPTIONAL, -- Cond SharedSpectrum highSpeedConfig-r16 HighSpeedConfig-r16 OPTIONAL -- Need R ]], [[ highSpeedConfig-v1700 HighSpeedConfig-v1700 OPTIONAL, -- Need R channelAccessMode2-r17 ENUMERATED {enabled} OPTIONAL, -- Cond SharedSpectrum2 discoveryBurstWindowLength-r17 ENUMERATED {ms0dot125, ms0dot25, ms0dot5, ms0dot75, ms1, ms1dot25} OPTIONAL, -- Need R ssb-PositionQCL-r17 SSB-PositionQCL-Relation-r17 OPTIONAL, -- Cond SharedSpectrum2 highSpeedConfigFR2-r17 HighSpeedConfigFR2-r17 OPTIONAL, -- Need R uplinkConfigCommon-v1700 UplinkConfigCommon-v1700 OPTIONAL, -- Need R ntn-Config-r17 NTN-Config-r17 OPTIONAL -- Need R ]], [[ featurePriorities-r17 SEQUENCE { redCapPriority-r17 FeaturePriority-r17 OPTIONAL, -- Need R slicingPriority-r17 FeaturePriority-r17 OPTIONAL, -- Need R msg3-Repetitions-Priority-r17 FeaturePriority-r17 OPTIONAL, -- Need R sdt-Priority-r17 FeaturePriority-r17 OPTIONAL -- Need R } OPTIONAL -- Need R ]], [[ ra-ChannelAccess-r17 ENUMERATED {enabled} OPTIONAL -- Cond SharedSpectrum2 ]], [[ featurePriorities-v1800 SEQUENCE { msg1-Repetitions-Priority-r18 FeaturePriority-r17 OPTIONAL, eRedCapPriority-r18 FeaturePriority-r17 OPTIONAL -- Need R } OPTIONAL, -- Need R atg-Config-r18 ATG-Config-r18 OPTIONAL -- Need R ]] } -- TAG-SERVINGCELLCONFIGCOMMON-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
6,119 | 10.5.3.5a Network Name | The purpose of this information element is to pass a text string to the mobile station. The Network Name information element is coded as shown in figure 10.5.80/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.94/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . If the coding scheme UCS2 is used and Chinese-Japanese-Korean-Vietnamese (CJKV) ideographs as defined in ISO/IEC 10646 [72] are received in the text string, the MS shall use the MCC of the PLMN from which it received the network name information element to determine the language for those CJKV ideographs as specified in table 10.5.93a/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Table 10.5.93a/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : MCC to CJKV ideograph language mapping table NOTE: This is due to CJKV ideograph language ambiguity in UCS2, in the sense that the same hexadecimal code can be mapped to different character displays dependent on the used language. The coding of CJKV ideographs itself does not allow to discriminate the CJKV ideograph language. The Network Name is a type 4 information element with a minimum length of 3 octets. No upper length limit is specified except for that given by the maximum number of octets in a L3 message (see 3GPP TS 44.006[ None ] [19]). Figure 10.5.80/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Network Name information element Table 10.5.94/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Network Name information element | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 10.5.3.5a |
6,120 | 11.2.1.3.1a IPv6 EPC based Bearer Activation | In this case, the P-GW provides the UE with an IPv6 Prefix belonging to the Intranet/ISP addressing space. A dynamic IPv6 address is given using stateless address autoconfiguration. This IPv6 address is used for packet forwarding within the packet domain and for packet forwarding on the Intranet/ISP. When a P-GW receives an initial access request (e.g. Create Session Request or Proxy Binding Update) message, the P-GW deduces from local configuration data associated with the APN: - The source of IPv6 Prefixes (P-GW internal prefix pool, or external address allocation server); - Any server(s) to be used for address allocation, authentication and/or protocol configuration options retrieval (e.g. IMS related configuration, see 3GPP TS 24.229[ IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 ] [47]); - The protocol, i.e. RADIUS, Diameter or DHCPv6, to be used with the server(s); - The communication and security feature needed to communicate with the server(s); As an example the P-GW may use one of the following options: - P-GW internal Prefix pool for IPv6 prefixes allocation and no authentication; - P-GW internal Prefix pool for IPv6 prefixes allocation and RADIUS for authentication. The AAA server responds with either an Access-Accept or an Access-Reject to the RADIUS client in the P-GW; - RADIUS for authentication and IPv6 prefix allocation. The AAA server responds with either an Access-Accept or an Access-Reject to the RADIUS client in the P-GW; The P-GW includes the PDP Address IE in the the initial access response (e.g. Create Session Response or Proxy Binding Acknowledgement) and return an IPv6 address composed of a Prefix and an Interface-Identifier. The Interface-Identifier may have any value and it does not need to be unique within or across APNs. It shall however not conflict with the Interface-Identifier that the P-GW has selected for its own side of the UE-P-GW link. The Prefix assigned by the P-GW or the external AAA server shall be globally or site-local unique (see the Note in subclause 11.3 of this document regarding the usage of site-local addresses). Table 0.a summarizes the IPv6 prefix allocation and parameter configuration use cases between the UE and the P-GW that may lead the P-GW to interwork with the external RADIUS AAA, Diameter AAA and DHCPv6 servers over Sgi reference point. For detailed description of the signalling flows between the UE and the P-GW, see the references in the table. The detailed description of the signalling use cases that may be triggered between the P-GW and the external servers are specified in this document, as referenced in the table. Table 0.a : IPv6 prefix allocation and parameter configuration use cases | 3GPP TS 29.061 | Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) | CT WG3 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 11.2.1.3.1a |
6,121 | 7.3.16 Relocation Cancel Request | A Relocation Cancel Request message shall be sent from the source MME/SGSN/AMF to the target MME/SGSN/AMF/MME_SRVCC on S3/S10/S16/N26 interface as part of the Inter-RAT handover Cancel procedure, S1 Based handover Cancel procedure, SRNS Relocation Cancel Procedure, EPS to 5GS handover cancel procedure, 5GS to EPS handover cancel procedure and 5G-SRVCC from NG-RAN to UTRAN handover cancel procedure. See Table 7.3.16-1 specifics the presence of the IEs in the message. Table 7.3.16-1: Information Elements in Relocation Cancel 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.16 |
6,122 | 5.2.12.2.8 Nudr_DM_Notify service operation | Service operation name: Nudr_DM_Notify. Description: UDR notifies NF service consumer(s) about modification of data, when data in the UDR is added, modified or deleted and an NF needs to be informed about this, due to a previous subscription to notifications procedure or due to a local configuration policy in the UDR. Inputs, Required: Notification Correlation Information, Data Set Identifier as defined in clause 5.2.12.2.1, Target of Event Reporting as defined in clause 5.2.12.2, Updated Data. Inputs, Optional: Data Subset Identifier as defined in clause 5.2.12.2.1. Outputs, Required: Result. Outputs, Optional: None. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.12.2.8 |
6,123 | 28.7.3 NAI format for SUCI | When the SUPI is defined as a Network Specific Identifier, the SUCI shall take the form of a Network Access Identifier (NAI). In this case, the NAI format of the SUCI shall have the form username@realm as specified in clause 2.2 of IETF RFC 7542 [126], where the realm part shall be identical to the realm part of the Network Specific Identifier. In SNPN scenarios, the realm part of the NAI may include MCC, MNC and the NID of the SNPN (see 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] clauses 5.30.2.3, 5.30.2.9, 6.3.4, and 6.3.8; for the realm part format see Home Network Domain for an SNPN in clause 28.2). When the SUPI is defined as an IMSI, the SUCI in NAI format shall have the form username@realm, where the realm part shall be constructed by converting the leading digits of the IMSI, i.e. MNC and MCC, into a domain name, as described in clause 28.2. In SNPN scenarios, the realm part shall additionally include the NID of the SNPN, if available. The resulting realm part of the NAI shall be in the form: "5gc.mnc<MNC>.mcc<MCC>.3gppnetwork.org", or "5gc.nid<NID>.mnc<MNC>.mcc<MCC>.3gppnetwork.org" (for SNPN scenarios where the NID is available). NOTE: The NID might not be available for the UE if an operator chooses the SUCI calculation to be the done inside the USIM, since the NID is configured within the ME part of the UE. The username part of the NAI shall take one of the following forms: a) for the null-scheme: type<supi type>.rid<routing indicator>.schid<protection scheme id>.userid<MSIN or Network Specific Identifier SUPI username> b) for the Scheme Output for Elliptic Curve Integrated Encryption Scheme Profile A and Profile B: type<supi type>.rid<routing indicator>.schid<protection scheme id>.hnkey<home network public key id>.ecckey<ECC ephemeral public key value>.cip<ciphertext value>.mac<MAC tag value> c) for HPLMN proprietary protection schemes: type<supi type>.rid<routing indicator>.schid<protection scheme id>.hnkey<home network public key id>. out<HPLMN defined scheme output> See clause 2.2B for the definition and format of the different fields of the SUCI. EXAMPLES: Assuming the IMSI 234150999999999, where MCC=234, MNC=15 and MSISN=0999999999, the Routing Indicator 678, and a Home Network Public Key Identifier of 27, the NAI format for the SUCI takes the form: - for the null-scheme: type0.rid678.schid0.userid0999999999@5gc.mnc015.mcc234.3gppnetwork.org - for the Profile <A> protection scheme: type0.rid678.schid1.hnkey27.ecckey<ECC ephemeral public key>.cip< encryption of 0999999999>.mac<MAC tag value>@5gc.mnc015.mcc234.3gppnetwork.org Assuming the Network Specific Identifier [email protected], the Routing Indicator 678, and a Home Network Public Key Identifier of 27, the NAI format for the SUCI takes the form: - for the null-scheme: [email protected] - for an anonymous SUCI: [email protected] (with username corresponding to "anonymous"), or [email protected] (with username corresponding to an empty string) - for the Profile <A> protection scheme: type1.rid678.schid1.hnkey27.ecckey<ECC ephemeral public key>.cip< encryption of user17>.mac<MAC tag value>@example.com See clauses 28.15.5 and 28.16.5 for the NAI format for a SUCI containing a GCI or a GLI. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 28.7.3 |
6,124 | 4.4.3.5 NAS COUNT wrap around | If, when increasing the NAS COUNT as specified above, the MME detects that either its downlink NAS COUNT or the UE's uplink NAS COUNT is "close" to wrap around, (close to 224), the MME shall take the following actions: - If there is no non-current native EPS security context with sufficiently low NAS COUNT values, the MME shall initiate a new AKA procedure with the UE, leading to a new established EPS security context and the NAS COUNT being reset to 0 in both the UE and the MME when the new EPS security context is activated; - Otherwise, the MME can activate a non-current native EPS security context with sufficiently low NAS COUNT values or initiate a new AKA procedure as specified above. If for some reason a new KASME has not been established using AKA before the NAS COUNT wraps around, the node (MME or UE) in need of sending a NAS message shall instead release the NAS signalling connection. Prior to sending the next uplink NAS message, the UE shall delete the eKSI indicating the current EPS security context. When the EIA0 is used as the NAS integrity algorithm, the UE and the MME shall allow NAS COUNT wrap around. If NAS COUNT wrap around occurs, the following requirements apply: - the UE and the MME shall continue to use the current security context; - the MME shall not initiate the EPS AKA procedure; - the MME shall not release the NAS signalling connection; and - the UE shall not perform a local release of the NAS signalling connection. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.4.3.5 |
6,125 | 6.2A IP header compression | The UE and the MME may support robust header compression (ROHC) framework (see IETF RFC 5795 [37]) for IP header compression if control plane CIoT EPS optimization is supported for PDN connections of IP PDN type. If IP header compression for control plane CIoT EPS optimization is supported, the ROHC profiles defined in 3GPP TS 36.323[ Evolved Universal Terrestrial Radio Access (E-UTRA); Packet Data Convergence Protocol (PDCP) specification ] [38] may be supported. The ROHC configuration is negotiated and established during the UE requested PDN connectivity procedure as specified in clause 6.5.1. Both the UE and the MME indicate whether IP header compression for control plane CIoT EPS optimization is supported during attach and tracking area updating procedures (see clauses 5.5.1 and 5.5.3). The ROHC configuration can be re-negotiated by using the UE requested bearer resource modification procedure or the EPS bearer context modification procedure as specified in clauses 6.4.3 and 6.5.4. | 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.2A |
6,126 | 5.8.14 NR sidelink U2N Relay UE operation 5.8.14.1 General | This procedure is used by a UE supporting NR sidelink U2N Relay UE operation configured by upper layers to transmit NR sidelink discovery messages to evaluate AS layer conditions. 5.8.14.2 NR sidelink U2N Relay UE threshold conditions A UE capable of NR sidelink U2N Relay UE operation shall: 1> if the threshold conditions specified in this clause were previously not met: 2> if threshHighRelay is not configured; or the RSRP measurement of the PCell, or the cell on which the UE camps, is below threshHighRelay by hystMaxRelay if configured; and 2> if threshLowRelay is not configured; or the RSRP measurement of the PCell, or the cell on which the UE camps, is above threshLowRelay by hystMinRelay if configured: 3> consider the threshold conditions to be met (entry); 1> else: 2> if the RSRP measurement of the PCell, or the cell on which the UE camps, is above threshHighRelay if configured; or 2> if the RSRP measurement of the PCell, or the cell on which the UE camps, is below threshLowRelay if configured; 3> consider the threshold conditions not to be met (leave); | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.8.14 |
6,127 | 4.22.10.2 UE or network requested MA PDU Session Release (non-roaming and roaming with local breakout) | The signalling flow for a MA PDU Session Release when the UE is not roaming, or when the UE is roaming and the PDU Session Anchor (PSA) is located in the VPLMN, is based on the signalling flow in Figure 4.3.4.2-1 with the following differences and clarifications: - In step 1, if the AMF needs to release the MA PDU Session over a single access, the AMF invokes the Nsmf_PDUSession_UpdateSMContext service operation to request the release of the MA PDU Session over a single access. In this case, the AMF includes in which access the MA PDU Session should be released. NOTE: When the SMF received the release request from the AMF, the SMF decides whether the MA PDU Session is completely released or released over a single access based on its local policy. - In step 1, if the AMF needs to release the MA PDU Session (e.g. locally released when the UE is CM-IDLE), the AMF invokes the Nsmf_PDUSession_ReleaseSMContext service operation to request the release of the MA PDU Session. - In step 2a, if the SMF releases the MA PDU Session over a single access, the SMF sends an N4 Session Modification Request (N4 Session ID) message instead of N4 Session Release message to the UPF(s) of the MA PDU session. - In step 2b, the UPF acknowledges the N4 Session Modification Request by the transmission of an N4 Session Modification Response (N4 Session ID) message to the SMF. - In step 3, the SMF sends the PDU Session Release Command message to release the MA PDU session over a single access (either 3GPP access or non-3GPP access) or both accesses. - In step 3, if the SMF releases the MA PDU Session over a single access, the SMF shall not include "skip indicator" in the Namf_Communication_N1N2MessageTransfer service. - In step 3, if the SMF releases the MA PDU Session over both accesses and user plane resources are established in both accesses, the SMF includes both N1 SM container (PDU Session Release Command) and N2 SM Resource Release request together in the Nsmf_PDUSession_UpdateSMContext or Namf_Communication_N1N2MessageTransfer service so that the UE does not request to activate user plane resources. The SMF releases user plane resources of the other access by including N2 SM Resource Release only in Namf_Communication_N1N2MessageTransfer service. - In step 3, when the SMF provides N1 SM container and/or N2 SM information, the SMF includes access type in the Namf_Communication_N1N2MessageTransfer to provide routing information to the AMF. - In step 11, the SMF triggers Nsmf_PDUSession_SMContextStatusNotify service only when the MA PDU Session is released in both accesses. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.22.10.2 |
6,128 | 6.8.9.1 UMTS security context | A UMTS security context is only established for UMTS subscribers. At the network side, two cases are distinguished: a) In case of a PS intra SGSN Handover, the UMTS cipher/integrity keys CK and IK agreed during the latest UMTS AKA procedure are sent to the target RNC or BSC. b) In case of a PS inter SGSN Handover, the initial SGSN sends the UMTS cipher/integrity keys CK and IK agreed during the latest UMTS AKA procedure to the new SGSN controlling the target RNC or BSC. The new SGSN becomes the new anchor point for the service. The new SGSN then stores the UMTS cipher/integrity keys CK and IK and sends them to the target RNC or BSC. At the user side, in both cases, the ME applies the UMTS cipher/integrity keys CK and IK received from the USIM during the latest UMTS AKA procedure. | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | 6.8.9.1 |
6,129 | 11.2.1.3.2a IPv6 Stateless Address Autoconfiguration for EPC | This subclause describes the signalling flows for the IPv6 Stateless Address Autoconfiguration procedures for EPC, in the case of using GTP-based S5/S8/S2a, and PMIP-based S5/S8/S2a. The procedures are based on the descriptions in TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [77] and TS 23.402[ Architecture enhancements for non-3GPP accesses ] [78]. Subclause 11.2.3.1a lists the use cases between the UE to the P-GW that may trigger the P-GW to interwork with the external PDNs for IPv6 Prefix allocation. IPv6 prefix is delivered to UE in Router Advertisement message from the access router, in the process of IPv6 Stateless Address Autoconfiguration. In the procedure in the cases of using GTP-based S5/S8, P-GW acts as an access router, and allocates to a UE a globally unique /64 IPv6 prefix if the PLMN allocates the prefix, or P-GW retrieves IPv6 prefix from an external PDN if one is allocated by the external PDN and advertises it to the UE. In the latter procedure, P-GW uses RADIUS, Diameter or DHCPv6 protocol for the retrieval of an IPv6 prefix. Following is the flow for IPv6 Stateless Address Autoconfiguration for EPC using GTP-based S5/S8. 1. UE initiates the Attach procedure, indicating ‘IPv6’ or ‘IPv4v6’ for PDN type in PDP type information element. 2. MME requests for Default Bearer creation by sending Create Session Request to the S-GW. 2x. The S-GW sends Create Session Request to the P-GW. 3. P-GW retrieves IPv6 prefix using RADIUS, Diameter, or DHCPv6 mechanism. This procedure is performed when an external PDN allocates an IPv6 prefix. 4. The P-GW sends Create Session Response. It includes the IPv6 interface identifier I IPv6 prefix. 5. S-GW sends Create Session Response message to the MME. It includes the IPv6 interface identifier I IPv6 prefix. 5x. The MME sends Attach Accept message to the UE without the IPv6 prefix. The UE shall ignore the IPv6 prefix if it receives one in the message. 6. After receiving the Attach Accept message, the UE may send a Router Solicitation to the P-GW to solicit a Router Advertisement message. 7. The P-GW sends a Router Advertisement message to the UE, solicited or unsolicited. It shall include an IPv6 prefix in Prefix Information option field of the message. The prefix is the same as the one in the Attach Accept message, if it is provided during the default bearer establishment. For the handling of M, O, L and A flags, and the lifetime of the prefix in the Router Advertisement message, follow the description in subclause 11.2.1.3.2. Figure 11bc: IPv6 Stateless Address Autoconfiguration for GTP-based S5/S8 If PMIP-based S5/S8 is used, S-GW acts as an access router. Therefore, it is responsible for receiving Router Solicitation from and sending Router Advertisement message to the UE. Other than this, procedure is the same as the case of using GTP-based S5/S8; P-GW allocates, or retrieves an IPv6 prefix from the external PDN. The prefix is delivered from the P-GW to the S-GW in the IPv6 Home Network Prefix Option IE of a Proxy Binding Ackowledgement message. In addition, the S-GW shall initiate sending the IPv6 Router Advertisement message (either solicited or unsolicited) to the UE once the PDN connection with PDN type IPv4v6 or IPv6 is setup after the procedure of E-UTRAN initial Attach, UE requested PDN connectivity, intra-3GPP access handover with Serving GW relocation, or handover from non-3GPP IP Access with S2a/S2b to 3GPP Access. Following diagram shows the case where PMIP-based S5/S8 is used. Figure 11bd: IPv6 Stateless Address Autoconfiguration for PMIP-based S5/S8 For trusted non-3GPP accesses, the non-3GPP network supports prefix advertisement for IPv6 prefix received from the P-GW in PMIPv6 Proxy Binding Acknowledgement. If the trusted non-3GPP access network is a WLAN network, for GTP/PMIP –based S2a, TWAN acts as an access router. Therefore, TWAN is responsible for receiving Router Solicitation from and sending Router Advertisement message to the UE. Other than this, procedure is the same as the case of using GTP/PMIP-based S5/S8; P-GW allocates, or retrieves an IPv6 prefix from the external PDN. The prefix is delivered from the P-GW to the TWAN in the IPv6 Home Network Prefix Option IE of a Proxy Binding Ackowledgement message or in the PDN Address Allocation IE of Create Session Response message. Following diagram shows the case for trusted non-3GPP access network for WLAN access where GTP/PMIP-based S2a is used. Figure 11be: IPv6 Stateless Address Autoconfiguration for trusted WLAN access for GTP/PMIP-based S2a The P-GW ensures that the advertised IPv6 prefix is globally unique. Regarding the handling of Duplicate Address Detection, follow subclause 11.2.1.3.2. The UE constructs its full IPv6 address in accordance with RFC 4862[83]. For the handling of IPv6 interface identifier, refer to subclause 11.2.1.3.2. If the P-GW, S-GW and TWAN receive Neighbor Solicitation message from the UE, it shall answer with Neighbor Advertisement message. To renew the allocated IPv6 prefix, the P-GW (GTP based S5/S8), S-GW (PMIPv6 based S5/S8) or TWAN (GTP/PMIP based S2a) shall send an IPv6 Router Advertisement (solicited or unsolicited) to the UE with the same assigned IPv6 prefix and and new non-zero values in preferred and valid lifetime fields for the PDN connection (PDN type IPv4v6 or IPv6), before the Router Advertisement lifetime and prefix lifetime expiry, as specified in IETF RFC 4861 [89]. When sending the IPv6 Router Advertisement message, the S-GW may trigger the paging (e.g. by sending a Downlink Data Notification message to the MME) if the UE is in idle state. In order to reduce paging an idle UE to deliver RA, the Router Advertisement lifetime and IPv6 prefix lifetime shall be configured accordingly. If a UE supports multiple PDN connections functionality, it can connect to multiple P-GWs simultaneously, or it can access multiple PDNs through a single P-GW. In the former case, the IPv6 prefix allocated for its default bearer is used for the UE’s dedicated bearers toward the same PDN. In the latter case, IPv6 Stateless Address Autoconfiguration procedure is applied for each PDN connection. | 3GPP TS 29.061 | Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) | CT WG3 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 11.2.1.3.2a |
6,130 | 6.10.2.2.3 SN initiated | When uplink and/or downlink PDCP COUNTs are about to wrap around for any of the SCG DRBs or SCG SRB, the SN shall request the MN to update the KSN over the Xn-C using the SN Modification procedure with MN involvement. The SN shall send the SN Modification Required message including KSN key update an indication to the MN as shown in Figure 6.10.2.2.3-1. When the MN receives KSN Key update indication, the MN shall derive a fresh KSN and send the derived KSN to the SN in the SN Modification Request message as in clause 6.10.2.1. Rest of the flows are like the call flow in Clause 6.10.2.1. Figure 6.10.2.2.3-1. SN Key update procedure using SN Modification procedure (SN initiated with MN involvement) | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.10.2.2.3 |
6,131 | 4.5.3 Operator-defined access categories | Operator-defined access category definitions can be signalled to the UE using NAS signalling. Each operator-defined access category definition consists of the following parameters: a) a precedence value which indicates in which order the UE shall evaluate the operator-defined category definition for a match; b) an operator-defined access category number, i.e. access category number in the 32-63 range that uniquely identifies the access category in the PLMN or SNPN in which the access categories are being sent to the UE; c) criteria consisting of one or more access category criteria type and associated access category criteria type values. The access category criteria type can be set to one of the following: 1) DNN; 2) Void; 3) OS Id + OS App Id of application triggering the access attempt; or 4) S-NSSAI; and NOTE 1: An access category criteria type can be associated with more than one access category criteria values. d) optionally, a standardized access category. This standardized access category is used in combination with the access identities of the UE to determine the RRC establishment cause as specified in subclause 4.5.6. If the access attempt is to establish a new PDU session i.e. it is triggered by: - a request from upper layers to send an UL NAS TRANSPORT message for the purpose of PDU session establishment unless the request triggered a service request procedure (or a registration procedure if the UE is in state 5GMM-REGISTERED.ATTEMPTING-REGISTRATION-UPDATE) to transition the UE from 5GMM-IDLE mode or 5GMM-IDLE mode with suspend indication to 5GMM-CONNECTED mode; or - a service request procedure (or a registration procedure if the UE is in state 5GMM-REGISTERED.ATTEMPTING-REGISTRATION-UPDATE) to transition the UE from 5GMM-IDLE mode or 5GMM-IDLE mode with suspend indication to 5GMM-CONNECTED mode triggered by a request from upper layers to send an UL NAS TRANSPORT message for the purpose of PDU session establishment, then: - the access attempt matches access category criteria type DNN if the DNN requested by the UE during the PDU session establishment procedure matches any of the access criteria type values associated with the access criteria type DNN; and - the access attempt matches access category criteria type S-NSSAI if the S-NSSAI requested by the UE during the PDU session establishment procedure matches any of the access criteria type values associated with the access criteria type S-NSSAI. If the access attempt is for an existing PDU session i.e. it is triggered by: - a request from upper layers to send an UL NAS TRANSPORT message for the purpose of PDU session modification unless the request triggered a service request procedure (or a registration procedure if the UE is in state 5GMM-REGISTERED.ATTEMPTING-REGISTRATION-UPDATE) to transition the UE from 5GMM-IDLE mode or 5GMM-IDLE mode with suspend indication to 5GMM-CONNECTED mode; - a service request procedure (or a registration procedure if the UE is in state 5GMM-REGISTERED.ATTEMPTING-REGISTRATION-UPDATE) to transition the UE from 5GMM-IDLE mode or 5GMM-IDLE mode with suspend indication to 5GMM-CONNECTED mode triggered by a request from upper layers to send an UL NAS TRANSPORT message for the purpose of PDU session modification; - a service request procedure (or a registration procedure if the UE is in state 5GMM-REGISTERED.ATTEMPTING-REGISTRATION-UPDATE) to transition the UE from 5GMM-IDLE mode or 5GMM-IDLE mode with suspend indication to 5GMM-CONNECTED mode triggered by a request from upper layers to send an UL NAS TRANSPORT message for the purpose of PDU session release; - a service request procedure (or a registration procedure if the UE is in state 5GMM-REGISTERED.ATTEMPTING-REGISTRATION-UPDATE) requesting user-plane resources for a PDU session; or - an uplink user data packet is to be sent for a PDU session with suspended user-plane resources, then: - the access attempt matches access category criteria type DNN if the DNN provided by the network in the PDU SESSION ESTABLISHMENT ACCEPT message matches any of the access criteria type values associated with the access criteria type DNN; and - the access attempt matches access category criteria type S-NSSAI if the S-NSSAI associated with the PDU session matches any of the access criteria type values associated with the access criteria type S-NSSAI. NOTE 2: In order to avoid having access attempts for non-always-on PDU sessions blocked due to access barring of always-on PDU sessions, it is recommended that the network assigns the highest precedence values to operator-defined access category definition which can be matched by always-on PDU sessions. An access attempt matches the criteria of an operator-defined access category definition, if the access attempt matches all access category criteria types included in the criteria with any of the associated access criteria type values. Each operator-defined access category definition has a different precedence value. Several operator-defined access category definitions can have the same operator-defined access category number. If: - an access category in bullet d) is not provided; - an access category in bullet d) is provided and is not a standardized access category; or - an access category in bullet d) is provided, is a standardized access category and is not recognized by the UE; the UE shall use instead access category 7 (MO_data) in combination with the access identities of the UE to determine the RRC establishment cause as specified in subclause 4.5.6. The operator-defined access category definitions are valid in the PLMN which provided them and in a PLMN equivalent to the PLMN which provided them, or in the SNPN which provided them and in an SNPN equivalent to the SNPN which provided them, as specified in annex C. If the UE stores operator-defined access category definitions valid in the selected PLMN or the RPLMN, or valid in the selected SNPN or RSNPN, then access control in 5GMM-IDLE mode or 5GMM-IDLE mode with suspend indication will only be performed for the event a) defined in subclause 4.5.1. If the transition from 5GMM-IDLE mode or 5GMM-IDLE mode with suspend indication over 3GPP access to 5GMM-CONNECTED mode is due to a UE NAS initiated 5GMM specific procedure, then this access attempt shall be mapped to one of the standardized access categories in the range < 32, see subclause 4.5.2. I.e. for this case the UE shall skip the checking of operator-defined access category definitions. If the UE stores operator-defined access category definitions valid in the selected PLMN or the RPLMN, or valid in the selected SNPN or RSNPN, then access control in 5GMM-CONNECTED mode and in 5GMM-CONNECTED mode with RRC inactive indication will only be performed for the events 1) to 8) defined in subclause 4.5.1. The UE shall handle the operator-defined access category definitions stored for the RPLMN or RSNPN as specified in subclause 5.4.4.3, subclause 5.5.1.2.4, and subclause 5.5.1.3.4. When the UE is switched off, the UE shall keep the operator-defined access category definitions so that the operator-defined access category definitions can be used after switch on. When the UE selects a new PLMN which is not equivalent to the previously selected PLMN, or selects a new SNPN which is not equivalent to the previously selected SNPN, the UE shall stop using the operator-defined access category definitions stored for the previously selected PLMN or SNPN and should keep the operator-defined access category definitions stored for the previously selected PLMN or SNPN. NOTE 3: When the UE selects a new PLMN which is not equivalent to the previously selected PLMN, or selects a new SNPN which is not equivalent to the previously selected SNPN, the UE can delete the operator-defined access category definitions stored for the previously selected PLMN or SNPN e.g. if there is no storage space in the UE. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.5.3 |
6,132 | 6.2.1 Resource grid | The transmitted signal in each slot is described by one or several resource grids of subcarriers and OFDM symbols. The resource grid structure is illustrated in Figure 6.2.2-1. The quantity depends on the downlink transmission bandwidth configured in the cell and shall fulfil where and are the smallest and largest downlink bandwidths, respectively, supported by the current version of this specification. The set of allowed values for is given by TS 36.104[ Evolved Universal Terrestrial Radio Access (E-UTRA); Base Station (BS) radio transmission and reception ] [6]. The number of OFDM symbols in a slot depends on the cyclic prefix length and subcarrier spacing configured and is given in Table 6.2.3-1. An antenna port is defined such that the channel over which a symbol on the antenna port is conveyed can be inferred from the channel over which another symbol on the same antenna port is conveyed. For MBSFN reference signals, positioning reference signals, UE-specific reference signals associated with PDSCH, demodulation reference signals associated with SPDCCH, and demodulation reference signals associated with EPDCCH, there are limits given below within which the channel can be inferred from one symbol to another symbol on the same antenna port. There is one resource grid per antenna port. The set of antenna ports supported depends on the reference signal configuration in the cell: - Cell-specific reference signals support a configuration of one, two, or four antenna ports and are transmitted on antenna ports ,, and , respectively. - MBSFN reference signals are transmitted on antenna port. The channel over which a symbol on antenna portis conveyed can be inferred from the channel over which another symbol on the same antenna port is conveyed only if the two symbols correspond to subframes (slots in case of 0.37 kHz subcarrier spacing) of the same MBSFN area. - UE-specific reference signals associated with PDSCH intended for non-BL/CE UE are transmitted on antenna port(s) , , , or one or several of . The channel over which a symbol on one of these antenna ports is conveyed can be inferred from the channel over which another symbol on the same antenna port is conveyed only if the two symbols are within the same subframe and in the same PRG when PRB bundling is used or in the same PRB pair when PRB bundling is not used. - UE-specific reference signals associated with PDSCH intended for BL/CE UE are transmitted on one or several of antenna port(s) . The channel over which a symbol on one of these antenna ports is conveyed can be inferred from the channel over which another symbol on the same antenna port is conveyed only if the two symbols are in the same set of consecutive subframes and have the same PRB index. - Demodulation reference signals associated with EPDCCH are transmitted on one or several of . The channel over which a symbol on one of these antenna ports is conveyed can be inferred from the channel over which another symbol on the same antenna port is conveyed only if the two symbols are in the same PRB pair. - Demodulation reference signals associated with MPDCCH are transmitted on one or several of . The channel over which a symbol on one of these antenna ports is conveyed can be inferred from the channel over which another symbol on the same antenna port is conveyed only if the two symbols are in the same set of consecutive subframes and have the same PRB index. - Demodulation reference signals associated with SPDCCH are transmitted on . - Positioning reference signals are transmitted on antenna port. The channel over which a symbol on antenna port is conveyed can be inferred from the channel over which another symbol on the same antenna port is conveyed only within one positioning reference signal occasion consisting of consecutive downlink subframes, where is configured by higher layers. - CSI reference signals support a configuration of 1, 2, 4, 8, 12, 16, 20, 24, 28, or 32 antenna ports and are transmitted on antenna ports , , , , , , , , and, respectively. Two antenna ports are said to be quasi co-located if the large-scale properties of the channel over which a symbol on one antenna port is conveyed can be inferred from the channel over which a symbol on the other antenna port is conveyed. The large-scale properties include one or more of delay spread, Doppler spread, Doppler shift, average gain, and average delay. | 3GPP TS 36.211 | Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation | RAN1 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.2.1 |
6,133 | 6.3.26 NRF discovery and selection | The following mechanisms may be used for discovery of NRF service instances and their endpoint addresses: - NF consumers or SCP may have all the NRF services instances and their endpoint addresses locally configured. - NF consumers or SCP may have the endpoint address of a NRF discovery service locally configured and utilize it to discover the NRF(s) and get the NF profile(s) of the NRF(s). - NF consumers (e.g. v-NRF) or SCP may have endpoint addresses of the NRF bootstrapping service and utilize it to discover the NRF service instances and their endpoint addresses. The NRF bootstrapping service is a version independent API, which may be especially useful over roaming interfaces. - The NF consumer, e.g. AMF, may use the Nnssf_NSSelection service to get the endpoint address of a NRF discovery service for a certain slice. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 6.3.26 |
6,134 | 10.1.4.1.3 Group hopping | For the reference signal for NPUSCH format 1, sequence-group hopping can be enabled where the sequence-group number in slot of a radio frame is defined by a group hopping pattern and a sequence-shift pattern according to where the number of reference signal sequences available for each resource unit size, is given by Table 10.1.4.1.3-1. Table 10.1.4.1.3-1: Definition of Sequence-group hopping can be enabled or disabled by means of the cell-specific parameter groupHoppingEnabled provided by higher layers. Sequence-group hopping for NPUSCH can be disabled for a certain UE through the higher-layer parameter groupHoppingDisabled despite being enabled on a cell basis unless the NPUSCH transmission corresponds to a Random Access Response Grant or a retransmission of the same transport block as part of the contention based random access procedure. The group-hopping pattern is given by where for . When , for frame structure type 1, is the slot number of the first slot of the resource unit and for frame structure type 2, is the frame number of the first slot of the resource unit. The pseudo-random sequence is defined by clause 7.2. The pseudo-random sequence generator shall be initialized with at the beginning of the resource unit for and in every even slot for . The sequence-shift pattern is given by where is given by higher-layer parameter groupAssignmentNPUSCH. If no value is signalled, . | 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.1.4.1.3 |
6,135 | 5.3.7.3 Actions following cell selection while T311 is running | Upon selecting a suitable NR cell, the UE shall: 1> ensure having valid and up to date essential system information as specified in clause 5.2.2.2; 1> stop timer T311; 1> if T390 is running: 2> stop timer T390 for all access categories; 2> perform the actions as specified in 5.3.14.4; 1> stop the relay (re)selection procedure, if ongoing; 1> if the cell selection is triggered by detecting radio link failure of the MCG or re-configuration with sync failure of the MCG or mobility from NR failure, and 1> if attemptCondReconfig is configured; and 1> if the selected cell is not configured with CondEventT1, or the selected cell is configured with CondEventT1 and leaving condition has not been fulfilled; and 1> if the selected cell is one of the candidate cells for which the reconfigurationWithSync is included in the masterCellGroup in the MCG VarConditionalReconfig and the condExecutionCondPSCell is not configured for the corresponding condReconfigId in the MCG VarConditionalReconfig: 2> if the UE supports RLF-Report for conditional handover, set the choCellId in the VarRLF-Report to the global cell identity, if available, otherwise to the physical cell identity and carrier frequency of the selected cell; 2> apply the stored condRRCReconfig associated to the selected cell and perform actions as specified in 5.3.5.3; NOTE 1: It is left to network implementation to how to avoid keystream reuse in case of CHO based recovery after a failed handover without key change. 1> if the cell selection is triggered by detecting radio link failure of the MCG or re-configuration with sync failure of the MCG or mobility from NR failure; and 1> if attemptLTM-Switch is configured; and 1> if the selected cell is one of the LTM candidate cells in the LTM-Candidate IE within VarLTM-Config associated with the MCG: 2> perform the LTM cell switch procedure for the selected LTM candidate cell according to the actions specified in 5.3.5.18.6; 1> else: 2> if UE is configured with attemptCondReconfig; or 2> if UE is configured with attemptLTM-Switch: 3> reset MAC; 3> release spCellConfig, if configured; 3> release the MCG SCell(s), if configured; 3> release delayBudgetReportingConfig, if configured and stop timer T342, if running; 3> release overheatingAssistanceConfig , if configured and stop timer T345, if running; 3> if MR-DC is configured: 4> perform MR-DC release, as specified in clause 5.3.5.10; 3> release idc-AssistanceConfig, if configured; 3> release btNameList, if configured; 3> release wlanNameList, if configured; 3> release sensorNameList, if configured; 3> release drx-PreferenceConfig for the MCG, if configured and stop timer T346a associated with the MCG, if running; 3> release maxBW-PreferenceConfig for the MCG, if configured and stop timer T346b associated with the MCG, if running; 3> release maxCC-PreferenceConfig for the MCG, if configured and stop timer T346c associated with the MCG, if running; 3> release maxMIMO-LayerPreferenceConfig for the MCG, if configured and stop timer T346d associated with the MCG, if running; 3> release minSchedulingOffsetPreferenceConfig for the MCG, if configured and stop timer T346e associated with the MCG, if running; 3> release rlm-RelaxationReportingConfig for the MCG, if configured and stop timer T346j associated with the MCG, if running; 3> release bfd-RelaxationReportingConfig for the MCG, if configured and stop timer T346k associated with the MCG, if running; 3> release releasePreferenceConfig, if configured and stop timer T346f, if running; 3> release onDemandSIB-Request if configured, and stop timer T350, if running; 3> release referenceTimePreferenceReporting, if configured; 3> release sl-AssistanceConfigNR, if configured; 3> release obtainCommonLocation, if configured; 3> release scg-DeactivationPreferenceConfig, if configured, and stop timer T346i, if running; 3> release musim-GapAssistanceConfig, if configured and stop timer T346h, if running; 3> release musim-GapPriorityAssistanceConfig, if configured; 3> release musim-LeaveAssistanceConfig, if configured; 3> release musim-CapabilityRestrictionConfig, if configured and stop timer T346n, if running; 3> release propDelayDiffReportConfig, if configured; 3> release ul-GapFR2-PreferenceConfig, if configured; 3> release rrm-MeasRelaxationReportingConfig, if configured; 3> release maxBW-PreferenceConfigFR2-2, if configured; 3> release maxMIMO-LayerPreferenceConfigFR2-2, if configured; 3> release minSchedulingOffsetPreferenceConfigExt, if configured; 3> release uav-FlightPathAvailabilityConfig, if configured; 3> release ul-TrafficInfoReportingConfig, if configured, and stop all instances of timer T346x, if running; 3> suspend all RBs, and BH RLC channels for the IAB-MT, except SRB0 and broadcast MRBs; 2> remove all the entries within the MCG VarConditionalReconfig, if any; 2> perform the LTM configuration release procedure for the MCG and the SCG as specified in clause 5.3.5.18.7; 2> for each measId, if the associated reportConfig has a reportType set to condTriggerConfig: 3> for the associated reportConfigId: 4> remove the entry with the matching reportConfigId from the reportConfigList within the VarMeasConfig; 3> if the associated measObjectId is only associated to a reportConfig with reportType set to condTriggerConfig: 4> remove the entry with the matching measObjectId from the measObjectList within the VarMeasConfig; 3> remove the entry with the matching measId from the measIdList within the VarMeasConfig; 2> remove the servingSecurityCellSetId within the VarServingSecurityCellSetID, if any; 2> release the PC5 RLC entity for SL-RLC0, if any; 2> start timer T301; 2> apply the default L1 parameter values as specified in corresponding physical layer specifications except for the parameters for which values are provided in SIB1; 2> apply the default MAC Cell Group configuration as specified in 9.2.2; 2> apply the CCCH configuration as specified in 9.1.1.2; 2> apply the timeAlignmentTimerCommon included in SIB1; 2> initiate transmission of the RRCReestablishmentRequest message in accordance with 5.3.7.4; NOTE 2: This procedure applies also if the UE returns to the source PCell. NOTE 3: A L2 U2N Relay UE may re-establish (e.g. via release and establish) the SL-RLC0 and SL-RLC1 of the connected L2 Remote UE(s). Upon selecting an inter-RAT cell, the UE shall: 1> perform the actions upon going to RRC_IDLE as specified in 5.3.11, with release cause 'RRC connection failure'. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.7.3 |
6,136 | 8.9.6.2 RRC Inactive to other states | The procedure for changing the UE state from RRC-inactive to RRC-connected is shown in Figure 8.9.6.2-1. Figure 8.9.6.2-1: RRC Inactive to RRC Connected state transition. 0. The gNB-CU-UP receives DL data on NG-U interface. 1. The gNB-CU-UP sends DL DATA NOTIFICATION message to the gNB-CU-CP. 2. The gNB-CU-CP sends PAGING message to the gNB-DU. 3. The gNB-DU sends the Paging message to the UE. NOTE: steps 0-3 are needed only in case of DL data. 4. The UE sends RRCResumeRequest message either upon RAN paging or UL data arrival. 5. The gNB-DU sends the INITIAL UL RRC MESSAGE TRANSFER message to the gNB-CU-CP. 6. The gNB-CU-CP sends UE CONTEXT SETUP REQUEST message including the stored F1 UL TEIDs to create the UE context in the gNB-DU. 7. The gNB-DU responds with the UE CONTEXT SETUP RESPONSE message including the F1 DL TEIDs allocated for the DRBs. 8. The gNB-CU-CP and the UE perform the RRC-Resume procedure via the gNB-DU. 9. The gNB-CU-CP sends BEARER CONTEXT MODIFICATION REQUEST message with a RRC Resume indication, which indicates that the UE is resuming from RRC-inactive state. The gNB-CU-CP also includes the F1 DL TEIDs received from the gNB-DU in step 7. 10. The gNB-CU-UP responds with theBEARER CONTEXT MODIFICATION RESPONSE message. NOTE steps 8 and 9 can be performed in parallel. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 8.9.6.2 |
6,137 | 17.7.6 MBMS-Service-Area AVP | The MBMS-Service-Area AVP (AVP code 903) is of type OctetString, and indicates the area over which the MBMS bearer service has to be distributed. The AVP consists of the following parts: The MBMS service area code represents the coding for the MBMS Service Area Identity. The MBMS Service Area Identity and its semantics are defined in subclause 15.3 of 3GPP TS 23.003[ Numbering, addressing and identification ] [40]. The length of an MBMS service area code is 2 octets. Each MBMS service area code shall only be present once in the list. | 3GPP TS 29.061 | Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) | CT WG3 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 17.7.6 |
6,138 | 6.1.3.6 Power Headroom Report MAC Control Element | The Power Headroom Report (PHR) MAC control element is identified by a MAC PDU subheader with LCID as specified in table 6.2.1-2. It has a fixed size and consists of a single octet defined as follows (figure 6.1.3.6-1): - R: reserved bit, set to "0"; - Power Headroom (PH): this field indicates the power headroom level. The length of the field is 6 bits. The reported PH and the corresponding power headroom levels are shown in Table 6.1.3.6-1 below (the corresponding measured values in dB can be found in clause 9.1.8.4 of TS 36.133[ Evolved Universal Terrestrial Radio Access (E-UTRA); Requirements for support of radio resource management ] [9]). Figure 6.1.3.6-1: PHR MAC control element Table 6.1.3.6-1: Power Headroom levels for PHR | 3GPP TS 36.321 | Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification | RAN2 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.1.3.6 |
6,139 | 8.3.1.1B Single-layer Spatial Multiplexing (demodulation subframe overlaps with aggressor cell ABS and CRS assistance information are configured) | The requirements are specified in Table 8.3.1.1B-2, with the addition of parameters in Table 8.3.1.1B-1. The purpose is to verify the performance of the antenna ports 7 or 8 without a simultaneous transmission on the other antenna port in the serving cell if the PDSCH transmission in the serving cell takes place in subframes that overlap with ABS [9] of the aggressor cell with CRS assistance information. In Table 8.3.1.1B-1, Cell 1 is the serving cell, and Cell 2 and Cell 3 are the aggressor cells. The downlink physical channel setup for Cell 1 is according to Annex C.3.2 and for Cell 2 and Cell 3 is according to Annex C.3.3, respectively. The CRS assistance information [7] includes Cell 2 and Cell 3. Table 8.3.1.1B-1: Test parameters of TM9-Single-Layer (2 CSI-RS ports) – Non-MBSFN ABS Table 8.3.1.1B-2: Minimum Performance of TM9-Single-Layer (2 CSI-RS ports) – Non-MBSFN ABS | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.3.1.1B |
6,140 | 4.2 Protocol stack 4.2.0 General | The protocol stack for GTPv2 shall be as depicted in Figure 4.2.0-1. Figure 4.2.0-1: GTPv2 stack The GTPv2 headers are specified in the respective clauses of this specification. The source and destination IP addresses and UDP ports used for each GTP-C message depend on the role that the message plays in a message exchange. A message can be an Initial message, or a Triggered message, or a Triggered Reply message to Triggered message. An Initial message is sent to a peer GTP entity with a sequence number chosen by the sending entity (see clause 7.6). A Triggered message is sent in response to an Initial message. Triggered Reply message may be sent in response to a Triggered message. See clause 7.6 for the sequence number usage. Typically, a Request message is an Initial message, but a Request message may be a Triggered messages in certain procedures where they are triggered by an Initial Command message. See clause 4.2.5 for classification of the Initial messages and their possible Triggered messages, as well as cases where there are Triggered Reply messages to the Triggered messages. Piggybacking is an optional feature, which is described in Annex F of 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [3]. If the feature is supported, then the piggybacking of the initial messages on triggered response messages for EUTRAN Initial Attach, a Handover from Trusted or Untrusted Non-3GPP IP Access to E-UTRAN (see clauses 8.6 and 16.11 of 3GPP TS 23.402[ Architecture enhancements for non-3GPP accesses ] [45]) and UE-requested PDN Connectivity procedures shall be implemented as per requirements in clauses 4.2.0 and 5.5.1 of this specification .When piggybacking is used, a common IP header and a common UDP header shall be used for the triggered response message and the piggybacked initial message as depicted in Figure 4.2.0-2. Immediately following the triggered response message is the piggybacked initial message, following which no additional information shall be present. The clause 5.5 specifies the usage of piggybacking-specific fields in the GTP-C header. Figure 4.2.0-2: Packet Format for the Piggybacking of messages | 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 | 4.2 |
6,141 | Annex F (informative): Redundant user plane paths based on multiple UEs per device | This clause describes an approach to realize multiple user plane paths in the system based on a device having multiple UEs and specific network deployments. The approach assumes a RAN deployment where redundant coverage by multiple gNBs (in the case of NR) is generally available. Upper layer protocols, such as the IEEE 802.1 TSN (Time Sensitive Networking), can make use of the multiple user plane paths. The UEs belonging to the same terminal device request the establishment of PDU Sessions that use independent RAN and CN network resources using the mechanisms outlined below. This deployment option has a number of preconditions: - The redundancy framework uses separate gNBs to achieve user plane redundancy over the 3GPP system. It is however up to operator deployment and configuration whether separate gNBs are available and used. If separate gNBs are not available for a device, the redundancy framework may still be applied to provide user plane redundancy in the rest of the network as well as between the device and the gNB using multiple UEs. - Terminal devices integrate multiple UEs which can connect to different gNBs independently. - RAN coverage is redundant in the target area: it is possible to connect to multiple gNBs from the same location. To ensure that the two UEs connect to different gNBs, the gNBs need to operate such that the selection of gNBs can be distinct from each other (e.g. gNB frequency allocation allows the UE to connect to multiple gNBs). - The core network UPF deployment is aligned with RAN deployment and supports redundant user plane paths. - The underlying transport topology is aligned with the RAN and UPF deployment and supports redundant user plane paths. - The physical network topology and geographical distribution of functions also supports the redundant user plane paths to the extent deemed necessary by the operator. - The operation of the redundant user plane paths is made sufficiently independent, to the extent deemed necessary by the operator, e.g. independent power supplies. Figure F-1 illustrates the architecture view. UE1 and UE2 are connected to gNB1 and gNB2, respectively and UE1 sets up a PDU Session via gNB1 to UPF1, while UE2 sets up a PDU Session via gNB2 to UPF2. UPF1 and UPF2 connect to the same Data Network (DN), but the traffic via UPF1 and UPF2 might be routed via different user plane nodes within the DN. UPF1 and UPF2 are controlled by SMF1 and SMF2, respectively. Figure F-1: Architecture with redundancy based on multiple UEs in the device The approach comprises the following main components shown as example using NR in figure F-2. - gNB selection: The selection of different gNBs for the UEs in the same device is realized by the concept of UE Reliability Groups for the UEs and also for the cells of gNBs. By grouping the UEs in the device and cells of gNBs in the network into more than one reliability group and preferably selecting cells in the same reliability group as the UE, it is ensured that UEs in the same device can be assigned different gNBs for redundancy as illustrated in Figure F-2, where UE1 and the cells of gNB1 belong to reliability group A, and UE2 and the cells of gNB2 belong to reliability group B. Figure F-2: Reliability group-based redundancy concept in RAN For determining the reliability grouping of a UE, one of the following methods or a combination of them can be used: - It could be configured explicitly to the UE and sent in a Registration Request message to the network using an existing parameter (such as an S-NSSAI in the Requested NSSAI where the SST is URLLC; the Reliability Group can be decided by the SD part). - It could also be derived from existing system parameters (e.g. SUPI, PEI, S-NSSAI, RFSP) based on operator configuration. The Reliability Group of each UE is represented via existing parameters and sent from the AMF to the RAN when the RAN context is established, so each gNB has knowledge about the reliability group of the connected UEs. NOTE: An example realisation can be as follows: the UE's Allowed NSSAI can be used as input to select the RFSP index value for the UE. The RAN node uses the RFSP for RRM purposes and can based on local configuration determine the UE's Reliability Group based on the S-NSSAI in Allowed NSSAI and/or S-NSSAI for the PDU Session(s). The reliability group of the RAN (cells of gNBs) entities are pre-configured by the O&M system in RAN. It is possible for gNBs to learn the reliability group neighbouring cells as the Xn connectivity is set up, or the reliability group of neighbouring cells are also configured into the gNBs. In the case of connected mode mobility, the serving gNB prioritizes candidate target cells that belong to different reliability group than the UE. It follows that normally the UE is handed over only to cells in the same reliability group. If cells in the same reliability group are not available (UE is out of the coverage of cells of its own reliability group or link quality is below a given threshold) the UE may be handed over to a cell in another reliability group as well. If the UE connects to a cell whose reliability group is different from the UE's reliability group, the gNB initiates a handover to a cell in the appropriate reliability group whenever such a suitable cell is available. In the case of an Idle UE, it is possible to use the existing cell (re-)selection priority mechanism, with a priori UE config using dedicated signalling (in the RRCConnectionRelease message during transition from connected to idle mode) to configure the UE to reselect the cells of the appropriate reliability group for camping in deployments where the cell reliability groups use different sets of frequencies. - UPF selection. UPF selection mechanisms as described in clause 6.3.3 can be used to select different UPFs for the UEs within the device. The selection may be based either on UE configuration or network configuration of different DNNs leading to the same DN, or different slices for the two UEs. It is possible to use the UE's Reliability Group, described above for gNB selection, as an input to the UPF selection. The proper operator configuration of the UPF selection can ensure that the path of the PDU Sessions of UE1 and UE2 are independent. - Control plane. The approach can optionally apply different control plane entities for the individual UEs within the device. This may be achieved by using: - different DNNs for the individual UEs within the device to select different SMFs, - or applying different slices for the individual UEs within the device either based on UE configuration or network subscription, to select different AMFs and/or SMFs. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | Annex |
6,142 | 5.15.2.2 Standardised SST values | Standardized SST values provide a way for establishing global interoperability for slicing so that PLMNs can support the roaming use case more efficiently for the most commonly used Slice/Service Types. The SSTs which are standardised are in the following Table 5.15.2.2-1. Table 5.15.2.2-1: Standardised SST values NOTE 1: The support of all standardised SST values is not required in a PLMN. Services indicated in this table for each SST value can also be supported by means of other SSTs. NOTE 2: A mapping of GSMA defined Network Slice Types (NEST) to standard SST values is defined in GSMA NG.116 [137]. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.15.2.2 |
6,143 | 4.4.5.1 IP Latency in DL, E-RAB level | This measurement provides IP Latency in DL on E-RAB level. CC This measurement is obtained by the following formula for E-RABs LatTime is obtained by accumulating the time T for E-RABs The sample of “T” is made for the new arrived IP data block (PDCP SDU) when there is no other prior data to be transmitted to the same UE in the eNodeB/RN . LatSample is obtained by accumulating the number of Latency samples taken on the E-RAB level The measurement is split into subcounters per E-RAB QoS level (QCI). Each measurement is an integer value representing the time in ms. The number of measurements is equal to the number of QCIs. The measurement name has the form DRB.IpLateDl.QCI where QCI identifies the E-RAB level quality of service class. EUtranCellFDD EUtranCellTDD Valid for packet switched traffic EPS This measurement is to support the Integrity KPI “E-UTRAN IP Latency” defined in [13] | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.4.5.1 |
6,144 | 4.3.17.9 Service Gap Control | Service Gap Control is an optional feature intended for MTC/CIoT UEs to control the frequency at which these UEs can access the network. That is, to ensure a minimum time gap between consecutive Mobile Originated data communications initiated by the UE. This helps reducing peak load situations when there are a large number of these UEs in an operator network. Service Gap Control is intended to be used for "small data allowance plans" for MTC/CIoT UEs where the applications are tolerant to service latency. NOTE 1: Time critical applications, such as emergency services and regulatory prioritised services can suffer from the latency caused by the Service Gap Control feature. Therefore Service Gap Control feature is not recommended for subscriptions with such applications and services. Service Gap Time is a subscription parameter used to set the Service Gap timer and is enforced in the UE and in the MME on a per UE level (i.e. the same Service Gap Timer applies for all PDN connections that the UE has). The UE indicates its capability of support for Service Gap Control in the Attach Request message and TAU Request message to the MME. The MME passes the Service Gap Time to the UE in the Attach Accept message and/or Tracking Area Update Accept message for UE that has indicated its supports of the Service Gap Control. The Service Gap Control shall be applied in a UE when a Service Gap Time is stored in the UE context and applied in the MME when the Service Gap Time is stored in the MM context. Service Gap Control requires the UE to stay in ECM-IDLE mode for at least the whole duration of the Service Gap timer before triggering Mobile Originated user data transmission, except for procedures that are exempted (see TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [46]). The Service Gap timer shall be started each time a UE moves from ECM-CONNECTED to ECM-IDLE, unless the connection request was initiated by the paging of a Mobile Terminated event, or after a TAU procedure without active flag or signalling active flag, which shall not trigger a new or extended Service Gap interval. When a Service Gap timer expires, the UE is allowed to send a connection request again. If the UE does so, the Service Gap timer will be restarted at the next ECM-CONNECTED to ECM-IDLE transition. The Service Gap control is applied in ECM-IDLE state only and does not impact UE Mobile Originated user data transmission or Mobile Originated signalling in ECM-CONNECTED state. The Service Gap timer is not stopped upon ECM-IDLE state to ECM-CONNECTED state transition. The UE shall not initiate connection requests for MO user plane data, MO control plane data, or MO SMS when a Service Gap timer is running. The UE shall also not initiate Attach Requests when a Service Gap timer is running, unless it is Attach Request without PDN connectivity or Emergency Attach which are allowed. NOTE 2: As a consequence of allowing Attach without PDN connectivity procedure, the UE with a running Service Gap timer does not initiate further MO signalling, except for tracking area updating procedure, until the UE receives MT signalling or after the UE has moved to ECM-IDLE state and the Service Gap Timer is not running. NOTE 3: Implementations need to make sure that latest and up-to-date data are always sent when a Service Gap timer expires. The MME may enforce the Service Gap timer by rejecting connection request for MO user plane data, MO control plane data, or MO SMS when a Service Gap timer is running. The MME may enforce the Service Gap timer by not allowing Attach Requests when a Service Gap timer is running, unless it is Attach Request without PDN connectivity or Emergency Attach which are allowed. When rejecting the connection requests and the Attach Requests while the Service Gap timer is running, the MME may include a Mobility Management back-off timer corresponding to the time left of the current Service Gap timer. For the UEs that does not support Service Gap Control (e.g. pre-release-15 UEs), Service Gap Control may be enforced using "General NAS level Mobility Management control" as defined in clause 4.3.7.4.2.1. When the MME starts the Service Gap timer, the MME should invoke the Service Gap timer with a value that is slightly shorter than the Service Gap Time value provided to the UE in the subscription information received from the HSS. NOTE 4: This ensures that the MME doesn't reject any UE requests just before the Service Gap timer expires e.g. because of slightly unsynchronized timers between UE and MME. A UE which transitions from a PSM or eDRX power saving state shall apply Service Gap Control when it wakes up if the Service Gap timer is still running. Additional aspects of Service Gap Control: - Service Gap Control applies in all PLMNs. - When the Service Gap timer is running and the UE receives paging, the UE shall respond as normal. - Service Gap Control applies to low priority (delayTolerant) and normal traffic. - Service Gap Control does not apply to exception reporting for NB-IoT. - Emergency Attach and Attach without PDN Connectivity are allowed when a Service Gap timer is running. - Service Gap Control shall be effective also for UEs performing detach and reattach unless it is Attach Request without PDN connectivity or Emergency Attach. - Tracking Area Update with active flag or signalling active flag is not allowed when a Service Gap timer is running except for emergency bearer services or if the UE is accessing with high priority access class in the range AC 11-15. - If the Service Gap timer is running, the Service Gap is applied at PLMN selection as follows: a) Re-attach to the registered PLMN: The remaining Service Gap timer value survives and controls the re-attach. b) Attach or Tracking Area Update to a different PLMN: The remaining Service Gap timer value survives and controls the Attach/Tracking Area Update to the new PLMN. c) USIM swap: The Service Gap timer is no longer running and the Service Gap feature does not apply, unless re-instatiated by the serving PLMN. - Multiple uplink packets and downlink packets are allowed during one RRC connection for UE operating within its APN Rate Control limits. The following procedures are impacted by Service Gap Control: - E-UTRAN Initial Attach, see clause 5.3.2.1; - Tracking Area Update procedures, see clause 5.3.3; - UE Triggered Service Request, see clause 5.3.4.1; - Connection Resume Request, see clause 5.3.5A. NOTE 5: Since UE triggered Service Request and Connection Resume Request are prevented by Service Gap timer, this implicitly prevents the UE from initiating MO data in Control Plane EPS Optimisations (see clause 5.3.4B.2), MO NIDD procedure (see TS 23.682[ Architecture enhancements to facilitate communications with packet data networks and applications ] [74]) and MO SMS (see TS 23.272[ Circuit Switched (CS) fallback in Evolved Packet System (EPS); Stage 2 ] [58]). | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.3.17.9 |
6,145 | – MIMO-ParametersPerBand | The IE MIMO-ParametersPerBand is used to convey MIMO related parameters specific for a certain band (not per feature set or band combination). MIMO-ParametersPerBand information element -- ASN1START -- TAG-MIMO-PARAMETERSPERBAND-START MIMO-ParametersPerBand ::= SEQUENCE { tci-StatePDSCH SEQUENCE { maxNumberConfiguredTCI-StatesPerCC ENUMERATED {n4, n8, n16, n32, n64, n128} OPTIONAL, maxNumberActiveTCI-PerBWP ENUMERATED {n1, n2, n4, n8} OPTIONAL } OPTIONAL, additionalActiveTCI-StatePDCCH ENUMERATED {supported} OPTIONAL, pusch-TransCoherence ENUMERATED {nonCoherent, partialCoherent, fullCoherent} OPTIONAL, beamCorrespondenceWithoutUL-BeamSweeping ENUMERATED {supported} OPTIONAL, periodicBeamReport ENUMERATED {supported} OPTIONAL, aperiodicBeamReport ENUMERATED {supported} OPTIONAL, sp-BeamReportPUCCH ENUMERATED {supported} OPTIONAL, sp-BeamReportPUSCH ENUMERATED {supported} OPTIONAL, dummy1 DummyG OPTIONAL, maxNumberRxBeam INTEGER (2..8) OPTIONAL, maxNumberRxTxBeamSwitchDL SEQUENCE { scs-15kHz ENUMERATED {n4, n7, n14} OPTIONAL, scs-30kHz ENUMERATED {n4, n7, n14} OPTIONAL, scs-60kHz ENUMERATED {n4, n7, n14} OPTIONAL, scs-120kHz ENUMERATED {n4, n7, n14} OPTIONAL, scs-240kHz ENUMERATED {n4, n7, n14} OPTIONAL } OPTIONAL, maxNumberNonGroupBeamReporting ENUMERATED {n1, n2, n4} OPTIONAL, groupBeamReporting ENUMERATED {supported} OPTIONAL, uplinkBeamManagement SEQUENCE { maxNumberSRS-ResourcePerSet-BM ENUMERATED {n2, n4, n8, n16}, maxNumberSRS-ResourceSet INTEGER (1..8) } OPTIONAL, maxNumberCSI-RS-BFD INTEGER (1..64) OPTIONAL, maxNumberSSB-BFD INTEGER (1..64) OPTIONAL, maxNumberCSI-RS-SSB-CBD INTEGER (1..256) OPTIONAL, dummy2 ENUMERATED {supported} OPTIONAL, twoPortsPTRS-UL ENUMERATED {supported} OPTIONAL, dummy5 SRS-Resources OPTIONAL, dummy3 INTEGER (1..4) OPTIONAL, beamReportTiming SEQUENCE { scs-15kHz ENUMERATED {sym2, sym4, sym8} OPTIONAL, scs-30kHz ENUMERATED {sym4, sym8, sym14, sym28} OPTIONAL, scs-60kHz ENUMERATED {sym8, sym14, sym28} OPTIONAL, scs-120kHz ENUMERATED {sym14, sym28, sym56} OPTIONAL } OPTIONAL, ptrs-DensityRecommendationSetDL SEQUENCE { scs-15kHz PTRS-DensityRecommendationDL OPTIONAL, scs-30kHz PTRS-DensityRecommendationDL OPTIONAL, scs-60kHz PTRS-DensityRecommendationDL OPTIONAL, scs-120kHz PTRS-DensityRecommendationDL OPTIONAL } OPTIONAL, ptrs-DensityRecommendationSetUL SEQUENCE { scs-15kHz PTRS-DensityRecommendationUL OPTIONAL, scs-30kHz PTRS-DensityRecommendationUL OPTIONAL, scs-60kHz PTRS-DensityRecommendationUL OPTIONAL, scs-120kHz PTRS-DensityRecommendationUL OPTIONAL } OPTIONAL, dummy4 DummyH OPTIONAL, aperiodicTRS ENUMERATED {supported} OPTIONAL, ..., [[ dummy6 ENUMERATED {true} OPTIONAL, beamManagementSSB-CSI-RS BeamManagementSSB-CSI-RS OPTIONAL, beamSwitchTiming SEQUENCE { scs-60kHz ENUMERATED {sym14, sym28, sym48, sym224, sym336} OPTIONAL, scs-120kHz ENUMERATED {sym14, sym28, sym48, sym224, sym336} OPTIONAL } OPTIONAL, codebookParameters CodebookParameters OPTIONAL, csi-RS-IM-ReceptionForFeedback CSI-RS-IM-ReceptionForFeedback OPTIONAL, csi-RS-ProcFrameworkForSRS CSI-RS-ProcFrameworkForSRS OPTIONAL, csi-ReportFramework CSI-ReportFramework OPTIONAL, csi-RS-ForTracking CSI-RS-ForTracking OPTIONAL, srs-AssocCSI-RS SEQUENCE (SIZE (1.. maxNrofCSI-RS-Resources)) OF SupportedCSI-RS-Resource OPTIONAL, spatialRelations SpatialRelations OPTIONAL ]], [[ -- R1 16-2b-0: Support of default QCL assumption with two TCI states defaultQCL-TwoTCI-r16 ENUMERATED {supported} OPTIONAL, codebookParametersPerBand-r16 CodebookParameters-v1610 OPTIONAL, -- R1 16-1b-3: Support of PUCCH resource groups per BWP for simultaneous spatial relation update simul-SpatialRelationUpdatePUCCHResGroup-r16 ENUMERATED {supported} OPTIONAL, -- R1 16-1f: Maximum number of SCells configured for SCell beam failure recovery simultaneously maxNumberSCellBFR-r16 ENUMERATED {n1,n2,n4,n8} OPTIONAL, -- R1 16-2c: Supports simultaneous reception with different Type-D for FR2 only simultaneousReceptionDiffTypeD-r16 ENUMERATED {supported} OPTIONAL, -- R1 16-1a-1: SSB/CSI-RS for L1-SINR measurement ssb-csirs-SINR-measurement-r16 SEQUENCE { maxNumberSSB-CSIRS-OneTx-CMR-r16 ENUMERATED {n8, n16, n32, n64}, maxNumberCSI-IM-NZP-IMR-res-r16 ENUMERATED {n8, n16, n32, n64}, maxNumberCSIRS-2Tx-res-r16 ENUMERATED {n0, n4, n8, n16, n32, n64}, maxNumberSSB-CSIRS-res-r16 ENUMERATED {n8, n16, n32, n64, n128}, maxNumberCSI-IM-NZP-IMR-res-mem-r16 ENUMERATED {n8, n16, n32, n64, n128}, supportedCSI-RS-Density-CMR-r16 ENUMERATED {one, three, oneAndThree}, maxNumberAperiodicCSI-RS-Res-r16 ENUMERATED {n2, n4, n8, n16, n32, n64}, supportedSINR-meas-r16 ENUMERATED {ssbWithCSI-IM, ssbWithNZP-IMR, csirsWithNZP-IMR, csi-RSWithoutIMR} OPTIONAL } OPTIONAL, -- R1 16-1a-2: Non-group based L1-SINR reporting nonGroupSINR-reporting-r16 ENUMERATED {n1, n2, n4} OPTIONAL, -- R1 16-1a-3: Non-group based L1-SINR reporting groupSINR-reporting-r16 ENUMERATED {supported} OPTIONAL, multiDCI-multiTRP-Parameters-r16 SEQUENCE { -- R1 16-2a-0: Overlapping PDSCHs in time and fully overlapping in frequency and time overlapPDSCHsFullyFreqTime-r16 INTEGER (1..2) OPTIONAL, -- R1 16-2a-1: Overlapping PDSCHs in time and partially overlapping in frequency and time overlapPDSCHsInTimePartiallyFreq-r16 ENUMERATED {supported} OPTIONAL, -- R1 16-2a-2: Out of order operation for DL outOfOrderOperationDL-r16 SEQUENCE { supportPDCCH-ToPDSCH-r16 ENUMERATED {supported} OPTIONAL, supportPDSCH-ToHARQ-ACK-r16 ENUMERATED {supported} OPTIONAL } OPTIONAL, -- R1 16-2a-3: Out of order operation for UL outOfOrderOperationUL-r16 ENUMERATED {supported} OPTIONAL, -- R1 16-2a-5: Separate CRS rate matching separateCRS-RateMatching-r16 ENUMERATED {supported} OPTIONAL, -- R1 16-2a-6: Default QCL enhancement for multi-DCI based multi-TRP defaultQCL-PerCORESETPoolIndex-r16 ENUMERATED {supported} OPTIONAL, -- R1 16-2a-7: Maximum number of activated TCI states maxNumberActivatedTCI-States-r16 SEQUENCE { maxNumberPerCORESET-Pool-r16 ENUMERATED {n1, n2, n4, n8}, maxTotalNumberAcrossCORESET-Pool-r16 ENUMERATED {n2, n4, n8, n16} } OPTIONAL } OPTIONAL, singleDCI-SDM-scheme-Parameters-r16 SEQUENCE { -- R1 16-2b-1b: Single-DCI based SDM scheme - Support of new DMRS port entry supportNewDMRS-Port-r16 ENUMERATED {supported1, supported2, supported3} OPTIONAL, -- R1 16-2b-1a: Support of s-port DL PTRS supportTwoPortDL-PTRS-r16 ENUMERATED {supported} OPTIONAL } OPTIONAL, -- R1 16-2b-2: Support of single-DCI based FDMSchemeA supportFDM-SchemeA-r16 ENUMERATED {supported} OPTIONAL, -- R1 16-2b-3a: Single-DCI based FDMSchemeB CW soft combining supportCodeWordSoftCombining-r16 ENUMERATED {supported} OPTIONAL, -- R1 16-2b-4: Single-DCI based TDMSchemeA supportTDM-SchemeA-r16 ENUMERATED {kb3, kb5, kb10, kb20, noRestriction} OPTIONAL, -- R1 16-2b-5: Single-DCI based inter-slot TDM supportInter-slotTDM-r16 SEQUENCE { supportRepNumPDSCH-TDRA-r16 ENUMERATED {n2, n3, n4, n5, n6, n7, n8, n16}, maxTBS-Size-r16 ENUMERATED {kb3, kb5, kb10, kb20, noRestriction}, maxNumberTCI-states-r16 INTEGER (1..2) } OPTIONAL, -- R1 16-4: Low PAPR DMRS for PDSCH lowPAPR-DMRS-PDSCH-r16 ENUMERATED {supported} OPTIONAL, -- R1 16-6a: Low PAPR DMRS for PUSCH without transform precoding lowPAPR-DMRS-PUSCHwithoutPrecoding-r16 ENUMERATED {supported} OPTIONAL, -- R1 16-6b: Low PAPR DMRS for PUCCH lowPAPR-DMRS-PUCCH-r16 ENUMERATED {supported} OPTIONAL, -- R1 16-6c: Low PAPR DMRS for PUSCH with transform precoding & pi/2 BPSK lowPAPR-DMRS-PUSCHwithPrecoding-r16 ENUMERATED {supported} OPTIONAL, -- R1 16-7: Extension of the maximum number of configured aperiodic CSI report settings csi-ReportFrameworkExt-r16 CSI-ReportFrameworkExt-r16 OPTIONAL, -- R1 16-3a, 16-3a-1, 16-3b, 16-3b-1, 16-8: Individual new codebook types codebookParametersAddition-r16 CodebookParametersAddition-r16 OPTIONAL, -- R1 16-8: Mixed codebook types codebookComboParametersAddition-r16 CodebookComboParametersAddition-r16 OPTIONAL, -- R4 8-2: SSB based beam correspondence beamCorrespondenceSSB-based-r16 ENUMERATED {supported} OPTIONAL, -- R4 8-3: CSI-RS based beam correspondence beamCorrespondenceCSI-RS-based-r16 ENUMERATED {supported} OPTIONAL, beamSwitchTiming-r16 SEQUENCE { scs-60kHz-r16 ENUMERATED {sym224, sym336} OPTIONAL, scs-120kHz-r16 ENUMERATED {sym224, sym336} OPTIONAL } OPTIONAL ]], [[ -- R1 16-1a-4: Semi-persistent L1-SINR report on PUCCH semi-PersistentL1-SINR-Report-PUCCH-r16 SEQUENCE { supportReportFormat1-2OFDM-syms-r16 ENUMERATED {supported} OPTIONAL, supportReportFormat4-14OFDM-syms-r16 ENUMERATED {supported} OPTIONAL } OPTIONAL, -- R1 16-1a-5: Semi-persistent L1-SINR report on PUSCH semi-PersistentL1-SINR-Report-PUSCH-r16 ENUMERATED {supported} OPTIONAL ]], [[ -- R1 16-1h: Support of 64 configured PUCCH spatial relations spatialRelations-v1640 SEQUENCE { maxNumberConfiguredSpatialRelations-v1640 ENUMERATED {n96, n128, n160, n192, n224, n256, n288, n320} } OPTIONAL, -- R1 16-1i: Support of 64 configured candidate beam RSs for BFR support64CandidateBeamRS-BFR-r16 ENUMERATED {supported} OPTIONAL ]], [[ -- R1 16-2a-9: Interpretation of maxNumberMIMO-LayersPDSCH for multi-DCI based mTRP maxMIMO-LayersForMulti-DCI-mTRP-r16 ENUMERATED {supported} OPTIONAL ]], [[ supportedSINR-meas-v1670 BIT STRING (SIZE (4)) OPTIONAL ]], [[ -- R1 23-8-5 Increased repetition for SRS srs-increasedRepetition-r17 ENUMERATED {supported} OPTIONAL, -- R1 23-8-6 Partial frequency sounding of SRS srs-partialFrequencySounding-r17 ENUMERATED {supported} OPTIONAL, -- R1 23-8-7 Start RB location hopping for partial frequency SRS srs-startRB-locationHoppingPartial-r17 ENUMERATED {supported} OPTIONAL, -- R1 23-8-8 Comb-8 SRS srs-combEight-r17 ENUMERATED {supported} OPTIONAL, -- R1 23-9-1 Basic Features of Further Enhanced Port-Selection Type II Codebook (FeType-II) per band information codebookParametersfetype2-r17 CodebookParametersfetype2-r17 OPTIONAL, -- R1 23-3-1-2a Two associated CSI-RS resources mTRP-PUSCH-twoCSI-RS-r17 ENUMERATED {supported} OPTIONAL, -- R1 23-3-2 Multi-TRP PUCCH repetition scheme 1 (inter-slot) mTRP-PUCCH-InterSlot-r17 ENUMERATED {pf0-2, pf1-3-4, pf0-4} OPTIONAL, -- R1 23-3-2b Cyclic mapping for multi-TRP PUCCH repetition mTRP-PUCCH-CyclicMapping-r17 ENUMERATED {supported} OPTIONAL, -- R1 23-3-2c Second TPC field for multi-TRP PUCCH repetition mTRP-PUCCH-SecondTPC-r17 ENUMERATED {supported} OPTIONAL, -- R1 23-5-2 MTRP BFR based on two BFD-RS set mTRP-BFR-twoBFD-RS-Set-r17 SEQUENCE { maxBFD-RS-resourcesPerSetPerBWP-r17 ENUMERATED {n1, n2}, maxBFR-r17 INTEGER (1..9), maxBFD-RS-resourcesAcrossSetsPerBWP-r17 ENUMERATED {n2, n3, n4} } OPTIONAL, -- R1 23-5-2a PUCCH-SR resources for MTRP BFRQ - Max number of PUCCH-SR resources for MTRP BFRQ per cell group mTRP-BFR-PUCCH-SR-perCG-r17 ENUMERATED{n1, n2} OPTIONAL, -- R1 23-5-2b Association between a BFD-RS resource set on SpCell and a PUCCH SR resource mTRP-BFR-association-PUCCH-SR-r17 ENUMERATED {supported} OPTIONAL, -- R1 23-6-3 Simultaneous activation of two TCI states for PDCCH across multiple CCs (HST/URLLC) sfn-SimulTwoTCI-AcrossMultiCC-r17 ENUMERATED {supported} OPTIONAL, -- R1 23-6-4 Default DL beam setup for SFN sfn-DefaultDL-BeamSetup-r17 ENUMERATED {supported} OPTIONAL, -- R1 23-6-4a Default UL beam setup for SFN PDCCH(FR2 only) sfn-DefaultUL-BeamSetup-r17 ENUMERATED {supported} OPTIONAL, -- R1 23-8-1 SRS triggering offset enhancement srs-TriggeringOffset-r17 ENUMERATED {n1, n2, n4} OPTIONAL, -- R1 23-8-2 Triggering SRS only in DCI 0_1/0_2 srs-TriggeringDCI-r17 ENUMERATED {supported} OPTIONAL, -- R1 23-9-5 Active CSI-RS resources and ports for mixed codebook types in any slot per band information codebookComboParameterMixedType-r17 CodebookComboParameterMixedType-r17 OPTIONAL, -- R1 23-1-1 Unified TCI [with joint DL/UL TCI update] for intra-cell beam management unifiedJointTCI-r17 SEQUENCE{ maxConfiguredJointTCI-r17 ENUMERATED {n8, n12, n16, n24, n32, n48, n64, n128}, maxActivatedTCIAcrossCC-r17 ENUMERATED {n1, n2, n4, n8, n16} } OPTIONAL, -- R1 23-1-1b Unified TCI with joint DL/UL TCI update for intra- and inter-cell beam management with more than one MAC-CE unifiedJointTCI-multiMAC-CE-r17 SEQUENCE{ minBeamApplicationTime-r17 ENUMERATED {n1, n2, n4, n7, n14, n28, n42, n56, n70, n84, n98, n112, n224, n336} OPTIONAL, maxNumMAC-CE-PerCC ENUMERATED {n2, n3, n4, n5, n6, n7, n8} } OPTIONAL, -- R1 23-1-1d Per BWP TCI state pool configuration for CA mode unifiedJointTCI-perBWP-CA-r17 ENUMERATED {supported} OPTIONAL, -- R1 23-1-1e TCI state pool configuration with TCI pool sharing for CA mode unifiedJointTCI-ListSharingCA-r17 ENUMERATED {n1,n2,n4,n8} OPTIONAL, -- R1 23-1-1f Common multi-CC TCI state ID update and activation unifiedJointTCI-commonMultiCC-r17 ENUMERATED {supported} OPTIONAL, -- R1 23-1-1g Beam misalignment between the DL source RS in the TCI state unifiedJointTCI-BeamAlignDLRS-r17 ENUMERATED {supported} OPTIONAL, -- R1 23-1-1h Association between TCI state and UL PC settings for PUCCH, PUSCH, and SRS unifiedJointTCI-PC-association-r17 ENUMERATED {supported} OPTIONAL, -- R1 23-1-1i Indication/configuration of R17 TCI states for aperiodic CSI-RS, PDCCH, PDSCH unifiedJointTCI-Legacy-r17 ENUMERATED {supported} OPTIONAL, -- 23-1-1m Indication/configuration of R17 TCI states for SRS unifiedJointTCI-Legacy-SRS-r17 ENUMERATED {supported} OPTIONAL, -- R1 23-1-1j Indication/configuration of R17 TCI states for CORESET #0 unifiedJointTCI-Legacy-CORESET0-r17 ENUMERATED {supported} OPTIONAL, -- R1 23-1-1c SCell BFR with unified TCI framework (NOTE; pre-requisite is empty) unifiedJointTCI-SCellBFR-r17 ENUMERATED {supported} OPTIONAL, -- R1 23-1-1a Unified TCI with joint DL/UL TCI update for inter-cell beam management unifiedJointTCI-InterCell-r17 SEQUENCE{ additionalMAC-CE-PerCC-r17 ENUMERATED {n0, n1, n2, n4}, additionalMAC-CE-AcrossCC-r17 ENUMERATED {n0, n1, n2, n4} } OPTIONAL, -- R1 23-10-1 Unified TCI with separate DL/UL TCI update for intra-cell beam management unifiedSeparateTCI-r17 SEQUENCE{ maxConfiguredDL-TCI-r17 ENUMERATED {n4, n8, n12, n16, n24, n32, n48, n64, n128}, maxConfiguredUL-TCI-r17 ENUMERATED {n4, n8, n12, n16, n24, n32, n48, n64}, maxActivatedDL-TCIAcrossCC-r17 ENUMERATED {n1, n2, n4, n8, n16}, maxActivatedUL-TCIAcrossCC-r17 ENUMERATED {n1, n2, n4, n8, n16} } OPTIONAL, -- R1 23-10-1b Unified TCI with separate DL/UL TCI update for intra-cell beam management with more than one MAC-CE unifiedSeparateTCI-multiMAC-CE-r17 SEQUENCE{ minBeamApplicationTime-r17 ENUMERATED {n1, n2, n4, n7, n14, n28, n42, n56, n70, n84, n98, n112, n224, n336}, maxActivatedDL-TCIPerCC-r17 INTEGER (2..8), maxActivatedUL-TCIPerCC-r17 INTEGER (2..8) } OPTIONAL, -- R1 23-10-1d Per BWP DL/UL-TCI state pool configuration for CA mode unifiedSeparateTCI-perBWP-CA-r17 ENUMERATED {supported} OPTIONAL, -- R1 23-10-1e TCI state pool configuration with DL/UL-TCI pool sharing for CA mode unifiedSeparateTCI-ListSharingCA-r17 SEQUENCE { maxNumListDL-TCI-r17 ENUMERATED {n1,n2,n4,n8} OPTIONAL, maxNumListUL-TCI-r17 ENUMERATED {n1,n2,n4,n8} OPTIONAL } OPTIONAL, -- R1 23-10-1f Common multi-CC DL/UL-TCI state ID update and activation with separate DL/UL TCI update unifiedSeparateTCI-commonMultiCC-r17 ENUMERATED {supported} OPTIONAL, -- 23-10-1m Unified TCI with separate DL/UL TCI update for inter-cell beam management with more than one MAC-CE unifiedSeparateTCI-InterCell-r17 SEQUENCE { k-DL-PerCC-r17 ENUMERATED {n0, n1, n2, n4}, k-UL-PerCC-r17 ENUMERATED {n0, n1, n2, n4}, k-DL-AcrossCC-r17 ENUMERATED {n0, n1, n2, n4}, k-UL-AcrossCC-r17 ENUMERATED {n0, n1, n2, n4} } OPTIONAL, -- R1 23-1-2 Inter-cell beam measurement and reporting (for inter-cell BM and mTRP) unifiedJointTCI-mTRP-InterCell-BM-r17 SEQUENCE { maxNumAdditionalPCI-L1-RSRP-r17 INTEGER (1..7), maxNumSSB-ResourceL1-RSRP-AcrossCC-r17 ENUMERATED {n1,n2,n4,n8} } OPTIONAL, -- R1 23-1-3 MPE mitigation mpe-Mitigation-r17 SEQUENCE { maxNumP-MPR-RI-pairs-r17 INTEGER (1..4), maxNumConfRS-r17 ENUMERATED {n1, n2, n4, n8, n12, n16, n28, n32, n48, n64} } OPTIONAL, -- R1 23-1-4 UE capability value reporting srs-PortReport-r17 SEQUENCE { capVal1-r17 ENUMERATED {n1, n2, n4} OPTIONAL, capVal2-r17 ENUMERATED {n1, n2, n4} OPTIONAL, capVal3-r17 ENUMERATED {n1, n2, n4} OPTIONAL, capVal4-r17 ENUMERATED {n1, n2, n4} OPTIONAL } OPTIONAL, -- R1 23-2-1a Monitoring of individual candidates mTRP-PDCCH-individual-r17 ENUMERATED {supported} OPTIONAL, -- R1 23-2-1b PDCCH repetition with PDCCH monitoring on any span of up to 3 consecutive OFDM symbols of a slot mTRP-PDCCH-anySpan-3Symbols-r17 ENUMERATED {supported} OPTIONAL, -- R1 23-2-2 Two QCL TypeD for CORESET monitoring in PDCCH repetition mTRP-PDCCH-TwoQCL-TypeD-r17 ENUMERATED {supported} OPTIONAL, -- R1 23-3-1-2b CSI-RS processing framework for SRS with two associated CSI-RS resources mTRP-PUSCH-CSI-RS-r17 SEQUENCE { maxNumPeriodicSRS-r17 INTEGER (1..8), maxNumAperiodicSRS-r17 INTEGER (1..8), maxNumSP-SRS-r17 INTEGER (0..8), numSRS-ResourcePerCC-r17 INTEGER (1..16), numSRS-ResourceNonCodebook-r17 INTEGER (1..2) } OPTIONAL, -- R1 23-3-1a Cyclic mapping for Multi-TRP PUSCH repetition mTRP-PUSCH-cyclicMapping-r17 ENUMERATED {typeA,typeB,both} OPTIONAL, -- R1 23-3-1b Second TPC field for Multi-TRP PUSCH repetition mTRP-PUSCH-secondTPC-r17 ENUMERATED {supported} OPTIONAL, -- R1 23-3-1c Two PHR reporting mTRP-PUSCH-twoPHR-Reporting-r17 ENUMERATED {supported} OPTIONAL, -- R1 23-3-1e A-CSI report mTRP-PUSCH-A-CSI-r17 ENUMERATED {supported} OPTIONAL, -- R1 23-3-1f SP-CSI report mTRP-PUSCH-SP-CSI-r17 ENUMERATED {supported} OPTIONAL, -- R1 23-3-1g CG PUSCH transmission mTRP-PUSCH-CG-r17 ENUMERATED {supported} OPTIONAL, -- R1 23-3-2d Updating two Spatial relation or two sets of power control parameters for PUCCH group mTRP-PUCCH-MAC-CE-r17 ENUMERATED {supported} OPTIONAL, -- R1 23-3-2e Maximum number of power control parameter sets configured for multi-TRP PUCCH repetition in FR1 mTRP-PUCCH-maxNum-PC-FR1-r17 INTEGER (3..8) OPTIONAL, -- R1 23-4 IntCell-mTRP mTRP-inter-Cell-r17 SEQUENCE { maxNumAdditionalPCI-Case1-r17 INTEGER (1..7), maxNumAdditionalPCI-Case2-r17 INTEGER (0..7) } OPTIONAL, -- R1 23-5-1 Group based L1-RSRP reporting enhancements mTRP-GroupBasedL1-RSRP-r17 SEQUENCE { maxNumBeamGroups-r17 INTEGER (1..4), maxNumRS-WithinSlot-r17 ENUMERATED {n2,n3,n4,n8,n16,n32,n64}, maxNumRS-AcrossSlot-r17 ENUMERATED {n8, n16, n32, n64, n128} } OPTIONAL, -- R1 23-5-2c MAC-CE based update of explicit BFD-RS mTRP-PUCCH-IntraSlot-r17 => per band mTRP-BFD-RS-MAC-CE-r17 ENUMERATED {n4, n8, n12, n16, n32, n48, n64 } OPTIONAL, -- R1 23-7-1 Basic Features of CSI Enhancement for Multi-TRP mTRP-CSI-EnhancementPerBand-r17 SEQUENCE { maxNumNZP-CSI-RS-r17 INTEGER (2..8), cSI-Report-mode-r17 ENUMERATED {mode1, mode2, both}, supportedComboAcrossCCs-r17 SEQUENCE (SIZE (1..16)) OF CSI-MultiTRP-SupportedCombinations-r17, codebookModeNCJT-r17 ENUMERATED{mode1,mode1And2} } OPTIONAL, -- R1 23-7-1b Active CSI-RS resources and ports in the presence of multi-TRP CSI codebookComboParameterMultiTRP-r17 CodebookComboParameterMultiTRP-r17 OPTIONAL, -- R1 23-7-1a Additional CSI report mode 1 mTRP-CSI-additionalCSI-r17 ENUMERATED{x1,x2} OPTIONAL, -- R1 23-7-4 Support of Nmax=2 for Multi-TRP CSI mTRP-CSI-N-Max2-r17 ENUMERATED {supported} OPTIONAL, -- R1 23-7-5 CMR sharing mTRP-CSI-CMR-r17 ENUMERATED {supported} OPTIONAL, -- R1 23-8-11 Partial frequency sounding of SRS for non-frequency hopping case srs-partialFreqSounding-r17 ENUMERATED {supported} OPTIONAL, -- R1-24 feature: Extend beamSwitchTiming for FR2-2 beamSwitchTiming-v1710 SEQUENCE { scs-480kHz ENUMERATED {sym56, sym112, sym192, sym896, sym1344} OPTIONAL, scs-960kHz ENUMERATED {sym112, sym224, sym384, sym1792, sym2688} OPTIONAL } OPTIONAL, -- R1-24 feature: Extend beamSwitchTiming-r16 for FR2-2 beamSwitchTiming-r17 SEQUENCE { scs-480kHz-r17 ENUMERATED {sym896, sym1344} OPTIONAL, scs-960kHz-r17 ENUMERATED {sym1792, sym2688} OPTIONAL } OPTIONAL, -- R1-24 feature: Extend beamReportTiming for FR2-2 beamReportTiming-v1710 SEQUENCE { scs-480kHz-r17 ENUMERATED {sym56, sym112, sym224} OPTIONAL, scs-960kHz-r17 ENUMERATED {sym112, sym224, sym448} OPTIONAL } OPTIONAL, -- R1-24 feature: Extend maximum number of RX/TX beam switch DL for FR2-2 maxNumberRxTxBeamSwitchDL-v1710 SEQUENCE { scs-480kHz-r17 ENUMERATED {n2, n4, n7} OPTIONAL, scs-960kHz-r17 ENUMERATED {n1, n2, n4, n7} OPTIONAL } OPTIONAL ]], [[ -- R1-23-1-4a: Semi-persistent/aperiodic capability value report srs-PortReportSP-AP-r17 ENUMERATED {supported} OPTIONAL, maxNumberRxBeam-v1720 INTEGER (9..12) OPTIONAL, -- R1-23-6-5 Support implicit configuration of RS(s) with two TCI states for beam failure detection sfn-ImplicitRS-twoTCI-r17 ENUMERATED {supported} OPTIONAL, -- R1-23-6-6 QCL-TypeD collision handling with CORESET with 2 TCI states sfn-QCL-TypeD-Collision-twoTCI-r17 ENUMERATED {supported} OPTIONAL, -- R1-23-7-1c Basic Features of CSI Enhancement for Multi-TRP - number of CPUs mTRP-CSI-numCPU-r17 ENUMERATED {n2, n3, n4} OPTIONAL ]], [[ supportRepNumPDSCH-TDRA-DCI-1-2-r17 ENUMERATED {n2, n3, n4, n5, n6, n7, n8, n16} OPTIONAL ]], [[ codebookParametersetype2DopplerCSI-r18 CodebookParametersetype2DopplerCSI-r18 OPTIONAL, codebookParametersfetype2DopplerCSI-r18 CodebookParametersfetype2DopplerCSI-r18 OPTIONAL, -- R1 40-1-1a: Unified TCI with joint DL/UL TCI update for single-DCI based intra-cell multi-TRP with multiple activated TCI -- codepoints per CC tci-JointTCI-UpdateMultiActiveTCI-PerCC-r18 SEQUENCE { tci-StateInd-r18 ENUMERATED {withAssignment, withoutAssignment}, maxNumberActiveJointTCI-PerCC-r18 INTEGER (2..8) } OPTIONAL, -- R1 40-1-1c: DCI format 1_1 and if supported 1_2 configured with TCI selection field tci-SelectionDCI-r18 ENUMERATED {supported} OPTIONAL, -- R1 40-1-2: Unified TCI with separate DL/UL TCI update for single-DCI based intra-cell multi-TRP with single activated TCI -- codepoint per CC tci-SeperateTCI-UpdateSingleActiveTCI-PerCC-r18 SEQUENCE { maxNumConfigDL-TCI-PerCC-PerBWP-r18 ENUMERATED {n4, n8, n12, n16, n24, n32, n48, n64, n128}, maxNumConfigUL-TCI-PerCC-PerBWP-r18 ENUMERATED {n4, n8, n12, n16, n24, n32, n48, n64}, maxNumActiveDL-TCI-AcrossCC-r18 ENUMERATED {n2, n4, n8, n16}, maxNumActiveUL-TCI-AcrossCC-r18 ENUMERATED {n2, n4, n8, n16} } OPTIONAL, -- R1 40-1-3: Per aperiodic CSI-RS resource/resource set configuration for TCI selection in S-DCI based MTRP tci-SelectionAperiodicCSI-RS-r18 ENUMERATED {perResource, perResourceSet, both} OPTIONAL, -- R1 40-1-4: Two TCI states for CJT Tx scheme for PDSCH twoTCI-StatePDSCH-CJT-TxScheme-r18 ENUMERATED {cjtSchemeA, cjtSchemeB, both} OPTIONAL, -- R1 40-2-3: TAG ID indication via absolute TA command MAC CE spCell-TAG-Ind-r18 ENUMERATED {supported} OPTIONAL, -- R1 40-2-4: PDCCH order sent by one TRP triggers RACH procedure (specifically PRACH) towards a different TRP based on CFRA for -- inter-cell interCellCrossTRP-PDCCH-OrderCFRA-r18 ENUMERATED {supported} OPTIONAL, -- R1 40-2-4a: PDCCH order sent by one TRP triggers RACH procedure (specifically PRACH) towards a different TRP based on CFRA for -- intra-cell intraCellCrossTRP-PDCCH-OrderCFRA-r18 ENUMERATED {supported} OPTIONAL, -- R1 40-2-9: Overlapping UL transmission reduction overlapUL-TransReduction-r18 ENUMERATED {supported} OPTIONAL, -- R1 40-4-11: Joint configuration of Rel.18 DMRS ports and Rel.18 dynamic switching between DFT-S-OFDM and CP-OFDM for PUSCH jointConfigDMRSPortDynamicSwitching-r18 ENUMERATED {supported} OPTIONAL, -- R1 40-5-1a: Comb offset hopping time-domain behavior when repetition factor R>1 srs-combOffsetInTime-r18 ENUMERATED {srs, rsrs, both} OPTIONAL, -- R1 40-5-1b: SRS comb offset hopping combined with legacy group/sequence hopping srs-combOffsetCombinedGroupSequence-r18 ENUMERATED {supported} OPTIONAL, -- R1 40-5-1c: Comb offset hopping within a subset srs-combOffsetHoppingWithinSubset-r18 ENUMERATED {supported} OPTIONAL, -- R1 40-5-2a: Smaller cyclic shift granularity for cyclic shift hopping srs-cyclicShiftHoppingSmallGranularity-r18 ENUMERATED {supported} OPTIONAL, -- R1 40-5-2b: SRS cyclic shift hopping combined with legacy group/sequence hopping srs-cyclicShiftCombinedGroupSequence-r18 ENUMERATED {supported} OPTIONAL, -- R1 40-5-2c: Cyclic shift hopping within a subset cyclicShiftHoppingWithinSubset-r18 ENUMERATED {supported} OPTIONAL, -- R1 40-5-3: SRS cyclic shift hopping combined with SRS comb offset hopping srs-cyclicShiftCombinedCombOffset-r18 ENUMERATED {supported} OPTIONAL, -- R1 40-6-1-1: 2 PTRS ports for single-DCI based STx2P SDM scheme for PUSCH—codebook pusch-CB-2PTRS-SingleDCI-STx2P-SDM-r18 ENUMERATED {supported} OPTIONAL, -- R1 40-6-1a-1: 2 PTRS ports for single-DCI based STx2P SDM scheme for PUSCH—noncodebook pusch-NonCB-2PTRS-SingleDCI-STx2P-SDM-r18 ENUMERATED {supported} OPTIONAL, -- R1 40-6-1b: Association between CSI-RS and SRS for noncodebook single-DCI based STx2P SDM scheme for PUSCH pusch-NonCB-SingleDCI-STx2P-SDM-CSI-RS-SRS-r18 SEQUENCE { maxNumberPeriodicSRS-Resource-PerBWP-r18 INTEGER (1..8), maxNumberAperiodicSRS-Resource-PerBWP-r18 INTEGER (1..8), maxNumberSemiPersistentSRS-ResourcePerBWP-r18 INTEGER (0..8), valueY-SRS-ResourceAssociate-r18 INTEGER (1..16), valueX-CSI-RS-ResourceAssociate-r18 INTEGER (1..2) } OPTIONAL, -- R1 40-6-1-2: New DMRS port entry for single-DCI based SDM scheme dmrs-PortEntrySingleDCI-SDM-r18 ENUMERATED {supported} OPTIONAL, -- R1 40-6-2-1: 2 PTRS ports for single-DCI based STx2P SFN scheme for PUSCH—codebook pusch-CB-2PTRS-SingleDCI-STx2P-SFN-r18 ENUMERATED {supported} OPTIONAL, -- R1 40-6-2a-1: 2 PTRS ports for single-DCI based STx2P SFN scheme for PUSCH—codebook pusch-NonCB-2PTRS-SingleDCI-STx2P-SFN-r18 ENUMERATED {supported} OPTIONAL, -- R1 40-6-2b: Association between CSI-RS and SRS for noncodebook single-DCI based STx2P SFN scheme for PUSCH pusch-NonCB-SingleDCI-STx2P-SFN-CSI-RS-SRS-r18 SEQUENCE { maxNumberPeriodicSRS-Resource-PerBWP-r18 INTEGER (1..8), maxNumberAperiodicSRS-Resource-PerBWP-r18 INTEGER (1..8), maxNumberSemiPersistentSRS-ResourcePerBWP-r18 INTEGER (0..8), valueY-SRS-ResourceAssociate-r18 INTEGER (1..16), valueX-CSI-RS-ResourceAssociate-r18 INTEGER (1..2) } OPTIONAL, -- R1 40-6-3c: Codebook multi-DCI based STx2P PUSCH+PUSCH –Fully overlapping PUSCHs in time and fully overlapping in frequency twoPUSCH-CB-MultiDCI-STx2P-FullTimeFullFreqOverlap-r18 ENUMERATED {supported} OPTIONAL, -- R1 40-6-3d: Codebook multi-DCI based STx2P PUSCH+PUSCH – Fully overlapping PUSCHs in time and partially overlapping in frequency twoPUSCH-CB-MultiDCI-STx2P-FullTimePartialFreqOverlap-r18 ENUMERATED {supported} OPTIONAL, -- R1 40-6-3e: Codebook multi-DCI based STx2P PUSCH+PUSCH – Partially overlapping PUSCHs in time and fully overlapping in frequency twoPUSCH-CB-MultiDCI-STx2P-PartialTimeFullFreqOverlap-r18 ENUMERATED {supported} OPTIONAL, -- R1 40-6-3f: Codebook multi-DCI based STx2P PUSCH+PUSCH – Partially overlapping PUSCHs in time, partially overlapping in frequency twoPUSCH-CB-MultiDCI-STx2P-PartialTimePartialFreqOverlap-r18 ENUMERATED {supported} OPTIONAL, -- R1 40-6-3g: Codebook multi-DCI based STx2P PUSCH+PUSCH – Partially overlapping PUSCHs in time, partially or non-overlapping -- in frequency twoPUSCH-CB-MultiDCI-STx2P-PartialTimeNonFreqOverlap-r18 ENUMERATED {supported} OPTIONAL, -- R1 40-6-4a: Dynamic indication of repetition number for SFN scheme for PUCCH pucch-RepetitionDynamicIndicationSFN-r18 ENUMERATED {supported} OPTIONAL ]] } DummyG ::= SEQUENCE { maxNumberSSB-CSI-RS-ResourceOneTx ENUMERATED {n8, n16, n32, n64}, maxNumberSSB-CSI-RS-ResourceTwoTx ENUMERATED {n0, n4, n8, n16, n32, n64}, supportedCSI-RS-Density ENUMERATED {one, three, oneAndThree} } BeamManagementSSB-CSI-RS ::= SEQUENCE { maxNumberSSB-CSI-RS-ResourceOneTx ENUMERATED {n0, n8, n16, n32, n64}, maxNumberCSI-RS-Resource ENUMERATED {n0, n4, n8, n16, n32, n64}, maxNumberCSI-RS-ResourceTwoTx ENUMERATED {n0, n4, n8, n16, n32, n64}, supportedCSI-RS-Density ENUMERATED {one, three, oneAndThree} OPTIONAL, maxNumberAperiodicCSI-RS-Resource ENUMERATED {n0, n1, n4, n8, n16, n32, n64} } DummyH ::= SEQUENCE { burstLength INTEGER (1..2), maxSimultaneousResourceSetsPerCC INTEGER (1..8), maxConfiguredResourceSetsPerCC INTEGER (1..64), maxConfiguredResourceSetsAllCC INTEGER (1..128) } CSI-RS-ForTracking ::= SEQUENCE { maxBurstLength INTEGER (1..2), maxSimultaneousResourceSetsPerCC INTEGER (1..8), maxConfiguredResourceSetsPerCC INTEGER (1..64), maxConfiguredResourceSetsAllCC INTEGER (1..256) } CSI-RS-IM-ReceptionForFeedback ::= SEQUENCE { maxConfigNumberNZP-CSI-RS-PerCC INTEGER (1..64), maxConfigNumberPortsAcrossNZP-CSI-RS-PerCC INTEGER (2..256), maxConfigNumberCSI-IM-PerCC ENUMERATED {n1, n2, n4, n8, n16, n32}, maxNumberSimultaneousNZP-CSI-RS-PerCC INTEGER (1..64), totalNumberPortsSimultaneousNZP-CSI-RS-PerCC INTEGER (2..256) } CSI-RS-ProcFrameworkForSRS ::= SEQUENCE { maxNumberPeriodicSRS-AssocCSI-RS-PerBWP INTEGER (1..4), maxNumberAperiodicSRS-AssocCSI-RS-PerBWP INTEGER (1..4), maxNumberSP-SRS-AssocCSI-RS-PerBWP INTEGER (0..4), simultaneousSRS-AssocCSI-RS-PerCC INTEGER (1..8) } CSI-ReportFramework ::= SEQUENCE { maxNumberPeriodicCSI-PerBWP-ForCSI-Report INTEGER (1..4), maxNumberAperiodicCSI-PerBWP-ForCSI-Report INTEGER (1..4), maxNumberSemiPersistentCSI-PerBWP-ForCSI-Report INTEGER (0..4), maxNumberPeriodicCSI-PerBWP-ForBeamReport INTEGER (1..4), maxNumberAperiodicCSI-PerBWP-ForBeamReport INTEGER (1..4), maxNumberAperiodicCSI-triggeringStatePerCC ENUMERATED {n3, n7, n15, n31, n63, n128}, maxNumberSemiPersistentCSI-PerBWP-ForBeamReport INTEGER (0..4), simultaneousCSI-ReportsPerCC INTEGER (1..8) } CSI-ReportFrameworkExt-r16 ::= SEQUENCE { maxNumberAperiodicCSI-PerBWP-ForCSI-ReportExt-r16 INTEGER (5..8) } PTRS-DensityRecommendationDL ::= SEQUENCE { frequencyDensity1 INTEGER (1..276), frequencyDensity2 INTEGER (1..276), timeDensity1 INTEGER (0..29), timeDensity2 INTEGER (0..29), timeDensity3 INTEGER (0..29) } PTRS-DensityRecommendationUL ::= SEQUENCE { frequencyDensity1 INTEGER (1..276), frequencyDensity2 INTEGER (1..276), timeDensity1 INTEGER (0..29), timeDensity2 INTEGER (0..29), timeDensity3 INTEGER (0..29), sampleDensity1 INTEGER (1..276), sampleDensity2 INTEGER (1..276), sampleDensity3 INTEGER (1..276), sampleDensity4 INTEGER (1..276), sampleDensity5 INTEGER (1..276) } SpatialRelations ::= SEQUENCE { maxNumberConfiguredSpatialRelations ENUMERATED {n4, n8, n16, n32, n64, n96}, maxNumberActiveSpatialRelations ENUMERATED {n1, n2, n4, n8, n14}, additionalActiveSpatialRelationPUCCH ENUMERATED {supported} OPTIONAL, maxNumberDL-RS-QCL-TypeD ENUMERATED {n1, n2, n4, n8, n14} } DummyI ::= SEQUENCE { supportedSRS-TxPortSwitch ENUMERATED {t1r2, t1r4, t2r4, t1r4-t2r4, tr-equal}, txSwitchImpactToRx ENUMERATED {true} OPTIONAL } CSI-MultiTRP-SupportedCombinations-r17 ::= SEQUENCE { maxNumTx-Ports-r17 ENUMERATED {n2, n4, n8, n12, n16, n24, n32}, maxTotalNumCMR-r17 INTEGER (2..64), maxTotalNumTx-PortsNZP-CSI-RS-r17 INTEGER (2..256) } -- TAG-MIMO-PARAMETERSPERBAND-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
6,146 | 28.3.2.4.2 Format of NSSF FQDN | The NSSF FQDN for an NSSF in an operator's PLMN shall be constructed by prefixing its Home Network Domain Name (see clause 28.2) with the label "nssf." as described below: - nssf.5gc.mnc<MNC>.mcc<MCC>.3gppnetwork.org The NSSF FQDN for an NSSF in an operator's SNPN, if not pre-configured in the NF, shall be constructed by prefixing the Home Network Domain Name (see clause 28.2) of the SNPN in which the NSSF is located with the label "nssf." as described below: - nssf.5gc.nid<NID>.mnc<MNC>.mcc<MCC>.3gppnetwork.org | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 28.3.2.4.2 |
6,147 | 4.7.7.5.1 Authentication not accepted by the MS | In a UMTS authentication challenge, the authentication procedure is extended to allow the MS to check the authenticity of the core network. Thus allowing, for instance, detection of false base station. Following a UMTS authentication challenge, the MS may reject the core network, on the grounds of an incorrect AUTN parameter (see 3GPP TS 33.102[ 3G security; Security architecture ] [5a]). This parameter contains two possible causes for authentication failure: a) MAC code failure If the MS considers the MAC code (supplied by the core network in the AUTN parameter) to be invalid, it shall send a AUTHENTICATION AND CIPHERING FAILURE message to the network, with the GMM cause 'MAC failure'. The MS shall then follow the procedure described in subclause 4.7.7.6 (f). b) SQN failure If the MS considers the SQN (supplied by the core network in the AUTN parameter) to be out of range, it shall send a AUTHENTICATION AND CIPHERING FAILURE message to the network, with the GMM cause 'Synch failure' and the re-synchronization token AUTS provided by the USIM (see 3GPP TS 33.102[ 3G security; Security architecture ] [5a]). The MS shall then follow the procedure described in subclause 4.7.7.6 (g). In Iu mode, an MSwith a USIM inserted shall reject the authentication challenge if no Authentication Parameter AUTN IE was present in the AUTHENTICATION REQUEST message (i.e. a GSM authentication challenge has been received when the MS expects a UMTS authentication challenge). In such a case, the MS shall send the AUTHENTICATION AND CIPHERING FAILURE message to the network, with the GMM cause 'GSM authentication unacceptable’. The MS shall then follow the procedure described in subclause 4.7.7.6 (f). If the MS returns an AUTHENTICATION_AND_CIPHERING_FAILURE message to the network, the MS shall delete any previously stored RAND and RES and shall stop timer T3316, if running. If the MS has a PDN connection for emergency bearer services established or is establishing such a PDN connection, additional MS requirements are specified in subclause 4.7.7.6, under "for items f and g". | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.7.7.5.1 |
6,148 | 5.5.4.4 UE-initiated authentication and key agreement procedure accepted by the network | Upon receiving the RELAY KEY REQUEST message, the AMF processes the message and interacts with the AUSF of the 5G ProSe remote UE or the 5G ProSe end UE as specified in 3GPP TS 33.503[ Security Aspects of Proximity based Services (ProSe) in the 5G System (5GS) ] [56]. If EAP-AKA' authentication for the 5G ProSe remote UE or the 5G ProSe end UE is initiated by the network, the AMF shall: a) create a RELAY AUTHENTICATION REQUEST message; b) set the PRTI IE of the RELAY AUTHENTICATION REQUEST message to the PRTI value of the received RELAY KEY REQUEST message; c) set the EAP message IE of the RELAY AUTHENTICATION REQUEST message to EAP request message received from the AUSF; and d) send the RELAY AUTHENTICATION REQUEST message to the UE. Upon receiving the RELAY AUTHENTICATION REQUEST message, the UE stops the timer T3527 and forwards the EAP message to the 5G ProSe remote UE or the 5G ProSe end UE as specified in 3GPP TS 24.554[ Proximity-services (ProSe) in 5G System (5GS) protocol aspects; Stage 3 ] [19E]. Upon receiving the EAP response message from the 5G ProSe remote UE or the 5G ProSe end UE as specified in 3GPP TS 24.554[ Proximity-services (ProSe) in 5G System (5GS) protocol aspects; Stage 3 ] [19E], the UE shall: a) create a RELAY AUTHENTICATION RESPONSE message; b) set the PRTI IE of the RELAY AUTHENTICATION RESPONSE message to the PRTI value of the received RELAY AUTHENTICATION REQUEST message; c) set the EAP message IE of the RELAY AUTHENTICATION RESPONSE message to EAP response message received from the 5G ProSe remote UE or the 5G ProSe end UE; and d) start a timer T3527 upon sending the RELAY AUTHENTICATION RESPONSE message to the AMF. After receiving the RELAY AUTHENTICATION RESPONSE message, the AMF may send a new RELAY AUTHENTICATION REQUEST message carrying EAP request message according to further handling of EAP-AKA' authentication from the AUSF as specified in 3GPP TS 33.503[ Security Aspects of Proximity based Services (ProSe) in the 5G System (5GS) ] [56]. The UE repeats the handling of the RELAY AUTHENTICATION REQUEST message as described above. Upon receiving the message from the AUSF that the authentication is successful, the AMF shall: a) create a RELAY KEY ACCEPT message; b) set the PRTI IE of the RELAY KEY ACCEPT message to the PRTI value of the RELAY KEY REQUEST message; c) include the EAP message IE of the RELAY KEY ACCEPT message set to EAP-success message received from the AUSF, if any; d) include the relay key response parameters IE of the RELAY KEY ACCEPT message set to KNR_ProSe and nonce_2 received from AUSF; and e) include the CP-PRUK ID in the relay key response parameters IE of the RELAY KEY ACCEPT message. Upon receiving the RELAY KEY ACCEPT message, the UE shall forward the EAP-success message, if any, and nonce_2 to the 5G ProSe remote UE or the 5G ProSe end UE as specified in 3GPP TS 24.554[ Proximity-services (ProSe) in 5G System (5GS) protocol aspects; Stage 3 ] [19E], and consider the authentication as completed successfully. The UE shall store the CP-PRUK ID to be used in the remote UE report procedure as specified in subclause 6.6.2.2. | 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.4.4 |
6,149 | – RepetitionSchemeConfig | The IE RepetitionSchemeConfig is used to configure the UE with repetition schemes as specified in TS 38.214[ NR; Physical layer procedures for data ] [19] clause 5.1. RepetitionSchemeConfig information element -- ASN1START -- TAG-REPETITIONSCHEMECONFIG-START RepetitionSchemeConfig-r16 ::= CHOICE { fdm-TDM-r16 SetupRelease { FDM-TDM-r16 }, slotBased-r16 SetupRelease { SlotBased-r16 } } RepetitionSchemeConfig-v1630 ::= SEQUENCE { slotBased-v1630 SetupRelease { SlotBased-v1630 } } FDM-TDM-r16 ::= SEQUENCE { repetitionScheme-r16 ENUMERATED {fdmSchemeA, fdmSchemeB,tdmSchemeA }, startingSymbolOffsetK-r16 INTEGER (0..7) OPTIONAL -- Need R } SlotBased-r16 ::= SEQUENCE { tciMapping-r16 ENUMERATED {cyclicMapping, sequentialMapping}, sequenceOffsetForRV-r16 INTEGER (1..3) } SlotBased-v1630 ::= SEQUENCE { tciMapping-r16 ENUMERATED {cyclicMapping, sequentialMapping}, sequenceOffsetForRV-r16 INTEGER (0) } -- TAG-REPETITIONSCHEMECONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
6,150 | 6.18.2 Requirements | The 5G system shall enable users to obtain services from more than one network simultaneously on an on-demand basis. For a user with a single operator subscription, the use of multiple serving networks operated by different operators shall be under the control of the home operator. When a service is offered by multiple operators, the 5G system shall be able to maintain service continuity with minimum service interruption when the serving network is changed to a different serving network operated by a different operator. NOTE 1: A business agreement is required between the network operators. In the event of the same service being offered by multiple operators, unless directed by the home operator's network, the UE shall be prioritized to receive subscribed services from the home operator's network. NOTE 2: If the service is unavailable (e.g. due to lack of network coverage) from the home operator's network, the UE may be able to receive the service from another operator's network. NOTE 3: QoS provided by the partner operator's network for the same service will be based on the agreement between the two operators and could be different than that provided by the home operator's network. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.18.2 |
6,151 | 8.38 MM Context | The MM Context information element contains the Mobility Management, UE security parameters that are necessary to transfer over S3/S16/S10/N26 interface. All Spare bits are set to zeros by the sender and ignored by the receiver. Spare bits in MM Context IE shall be set to 1's before sending MM Context IE to Gn/Gp SGSN. NOTE 1: The encoding of Spare bits in MM Context IE is different between GTPv1 and GTPv2. Spare bits in GTPv1 in MM Context IE there are set to 1s. Security Mode indicates the type of security keys (GSM/UMTS/EPS) and Authentication Vectors (quadruplets /quintuplets/triplets) that are passed to the new MME/SGSN/AMF. The DRX parameter coding is specified in clause 10.5.5.6 of 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [5]. If DRXI (DRX Indicator), bit 4 of octet 5, is set to "1", then the DRX parameter field is present, otherwise its octets are not present. During 5GS to EPS mobility procedure, the source AMF shall not send 5G DRX parameter to the target MME; and during EPS to 5GS mobility procedure, the target AMF shall discard the DRX parameter if received. The encoding of 5G DRX as specified in clause 9.11.3.2A of 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [87] is different from the one as specified in clause 10.5.5.6 of 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [5]. Uplink/downlink Subscribed UE AMBR (Aggregate Maximum Bit Rate) is coded as Unsigned32 integer values in kbps (1000 bps) for all non-GBR bearers according to the subscription of the user. The uplink/downlink Subscribed UE AMBR requires converting values in bits per second to kilobits per second when it is received from the HSS. If such conversions result in fractions, then the uplink/downlink Subscribed UE AMBR values shall be rounded upwards. If SAMBRI (Subscribed UE AMBR Indicator), bit 1 of octet 6, is set to "1", then the Uplink/downlink Subscribed UE AMBR parameter field is present, otherwise these parameters are not present. If no Subscribed UE AMBR is received from the HSS, the SAMBRI shall be set to "0".Uplink/downlink Used UE AMBR (Aggregate Maximum Bit Rate) is coded as Unsigned32 integer values in kbps (1000 bps) for all non-GBR bearers currently being used by the UE. If UAMBRI (Used UE AMBR Indicator), bit 2 of octet 6, is set to "1", then the Uplink/downlink Used UE AMBR parameter field is present, otherwise these parameters are not present. The encoding of Mobile Equipment Identity (MEI) field shall be same as specified in clause 8.10 of this specification. If Length of Mobile Equipment Identity is zero, then the Mobile Equipment Identity parameter shall not be present. If the UE is emergency or RLOS attached and the UE is UICCless or the IMSI is unauthenticated, Mobile Equipment Identity (MEI) shall be used as the UE identity. The UE Network Capability coding is specified in clause 9.9.3.34 of 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [23]. If Length of UE Network Capability is zero, then the UE Network Capability parameter shall not be present. The MS Network Capability coding is specified in clause 10.5.5.12 of 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [5]. If Length of MS Network Caapability is zero, then the MS Network Capability parameter shall not be present. The Voice Domain Preference and UE's Usage Setting coding is specified in clause 10.5.5.28 of 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [5]. If Length of Voice Domain Preference and UE's Usage Setting is zero, then the Voice Domain Preference and UE's Usage Setting parameter shall not be present. Used Cipher indicates the GSM ciphering algorithm that is in use. Used NAS Cipher indicates the EPS ciphering algorithm that is in use. The Access restriction data is composed of UNA(UTRAN Not Allowed), GENA(GERAN Not Allowed), GANA(GAN Not Allowed), INA(I-HSPA-Evolution Not Allowed), ENA(WB-E-UTRAN Not Allowed), NBNA( NB-IoT Not Allowed), ECNA (Enhanced Coverage Not Allowed) and HNNA(HO-To-Non-3GPP-Access Not Allowed). If the SGSN support the Higher bitrates than 16 Mbps flag, the Higher bitrates than 16 Mbps flag shall be included in the MM Context if: - the source S4-SGSN has received "Higher bitrates than 16 Mbps flag" in the RANAP Initial UE Message or in RANAP Relocation Complete as defined in TS 25.413[ UTRAN Iu interface Radio Access Network Application Part (RANAP) signalling ] [33] from the RNC, or - the source S4-SGSN has stored the "Higher bitrates than 16 Mbps flag" (received from an SGSN via the Identification Response, Context Response or Forward Relocation Request during earlier procedures). The S4-SGSN shall set the "Higher bitrates than 16 Mbps flag" to "1" if "Higher bitrates than 16 Mbps flag" is "allowed" and to "0" if it is "not allowed". The Length of Higher bitrates than 16 Mbps flag shall be set to zero if the S4-SGSN has not received the "Higher bitrates than 16 Mbps flag". As depicted in Figure 8.38-1, the GSM Key, Used Cipher and Authentication Triplets that are unused in the old SGSN shall be transmitted to the new SGSN for the GSM subscribers. An array of at most 5 Authentication Triplets may be included. The field 'Number of Triplet' shall be set to the value '0' if no Authentication Triplet is included (i.e. octets '16 to h' are absent). The Authentication Triplet coding is specified in Figure 8.38-7. Figure 8.38-1: GSM Key and Triplets As depicted in Figure 8.38-2, the UMTS Key, Used Cipher and Authentication Quintuplets that are unused in the old SGSN shall be transmitted to the new SGSN when the UMTS subscriber is attached to a GSM BSS in the old system, in case the user has a ME capable of UMTS AKA. An array of at most 5 Authentication Quintuplets may be included. The field 'Number of Quintuplets' shall be set to the value '0' if no Authentication Quintuplet is included (i.e. octets '40 to h' are absent). If the UGIPAI (Used GPRS integrity protection algorithm Indicator), bit 3 of octet 6, is set to 1, then bits 4 to 6 of octet 7 shall contain the Used GPRS integrity protection algorithm field, otherwise these bits shall be set to 0 and ignored by the receiver. The GUPII (GPRS User Plane Integrity Indicator), bit 4 of octet 6, shall be set to 1 if the subscriber profile indicated that user plane integrity protection is required and set to 0 otherwise. NOTE 2: The encoding of the bits is not identical with GTPv1 as the spare bits are encoded differently. The source S4-SGSN shall include the IOV_updates counter if it is supported and available. The IOV_updates counter is encoded as an integer with a length of 1 octet. The use of the IOV_updates counter is specified in 3GPP TS 43.020[ Security related network functions ] [78]. If IOVI (IOV_updates Indicator), bit 5 of octet 6, is set to "1", then the IOV_updates counter parameter field shall be present, otherwise it shall not be present. The Authentication Quintuplet coding is specified in Figure 8.38-8. Figure 8.38-2: UMTS Key, Used Cipher and Quintuplets As depicted in Figure 8.38-3, the GSM Key, Used Cipher and Authentication Quintuplets that are unused in the old SGSN shall be transmitted to the new SGSN when the UMTS subscriber is attached to a GSM BSS in the old system, in case the user has a ME no capable of UMTS AKA. An array of at most 5 Authentication Quintuplets may be included. The field 'Number of Quintuplets' shall be set to the value '0' if no Authentication Quintuplet is included (i.e. octets '16 to h' are absent). The Authentication Quintuplet coding is specified in Figure 8.38-8. Figure 8.38-3: GSM Key, Used Cipher and Quintuplets As depicted in Figure 8.38-4, the UMTS Key, KSI and unused Authentication Quintuplets in the old SGSN may be transmitted to the new SGSN/MME when the UMTS subscriber is attached to UTRAN/GERAN in the old system, but it is not allowed to send quintuplets to an MME in a different serving network domain (see 3GPP TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [12] clause 6.1.6). The MME may forward the UMTS Key, KSI and unused Authentication Quintuplets which were previously stored back to the same SGSN, for further details, refer to 3GPP TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [12]. An array of at most 5 Authentication Quintuplets may be included. The field 'Number of Quintuplets' shall be set to the value '0' if no Authentication Quintuplet is included (i.e. octets '40 to h' are absent). If the UGIPAI (Used GPRS integrity protection algorithm Indicator), bit 3 of octet 6, is set to 1, then bits 1 to 3 of octet 7 shall contain the Used GPRS integrity protection algorithm field, otherwise these bits shall be set to 0 and ignored by the receiver. The GUPII (GPRS User Plane Integrity Indicator), bit 4 of octet 6, shall be set to 1 if the subscriber profile indicated that user plane integrity protection is required and set to 0 otherwise. NOTE 3: The encoding of the bits is not identical with GTPv1 as the spare bits are encoded differently. The source S4-SGSN shall include the IOV_updates counter if it is supported and available. The IOV_updates counter is encoded as an integer with a length of 1 octet. The use of the IOV_updates counter is specified in 3GPP TS 43.020[ Security related network functions ] [78]. If IOVI (IOV_updates Indicator), bit 5 of octet 6, is set to "1", then the IOV_updates counter parameter field shall be present, otherwise it shall not be present. The Extended Access Restriction Data is to store the extra access restriction data received from the HSS (other than ECNA, NBNA, HNNA, ENA, INA, GANA, GENA and UNA). If Length of Extended Access Restriction Data is zero, then the field of Extended Access Restriction Data shall not be present. The Extended Access Restriction Data is composed of NRSRNA (NR as Secondary RAT Not Allowed). The presence of the Extended Access Restriction Data for the case in UMTS Key as depicted in Figure 8.38-4 is optional. NOTE 4: In Figure 8.38-4, including the Extended Access Restriction Data allows optimized selection of SGW in case of handover from GSM/UTRAN to E-UTRAN. The Authentication Quintuplet coding is specified in Figure 8.38-8. Figure 8.38-4: UMTS Key and Quintuplets As depicted in Figure 8.38-5, the current EPS Security Context, a non-current EPS Security Context (if available), and unused Authentication Quadruplets in the old MME may be transmitted to the new MME/AMF. If the new MME/AMF is not in the same serving network domain, then only the current EPS Security Context may be transmitted. The mapping of an EPS security context to a 5G security context in the new AMF is specified in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [86]. An array of at most 5 Authentication Quadruplets may be included. The field 'Number of Quadruplets' shall be set to the value '0' if no Authentication Quadruplet is included (i.e. octets '46 to g' are absent). Authentication Quintuplets shall not be transmitted to the new MME/AMF (i.e. octets 'g+1 to h' shall be absent) even if the old MME has the Authentication Quintuplets for this UE. The field 'Number of Quintuplets' shall be set to the value '0'. The reasons for not sending Quintuplets are specified in3GPP TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [12] clause 6.1.6. The current EPS Security Context may be transmitted by the old AMF to the new MME, where the mapping of a 5G security context to an EPS security context is specified in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [86]. The field 'Number of Quadruplets' and 'Number of Quintuplets' shall be set to the value '0'. The AMF shall not transmit un-used authentication vectors to an MME and shall discard any un-used authentication vectors received from an MME, regardless of whether the MME and AMF pertain to the same or different serving network domains. The Authentication Quintuplet and Authentication Quadruplet codings are specified in Figure 8.38-8 and Figure 8.38-9 respectively. The value of the NAS Downlink Count shall be set to the value that shall be used to send the next NAS message. The value of the NAS Uplink Count shall be set to the largest NAS Uplink Count that was in a successfully integrity verified NAS message. In Figure 8.38-5, the fields for the Old EPS Security Context (i.e. octets from s to s+64) may be present only in S10 Forward Relocation Request message according to the Rules on Concurrent Running of Security Procedures, which are specified in 3GPP TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [12]. The octets for Old EPS Security Context shall be present if the OSCI (Old Security Context Indicator), bit 1 of octet 6) is set to "1"; otherwise they shall not be present. If NHI_old (Next Hop Indicator for old EPS Security Context), bit 8 of octet s, is set to "1", then the parameters old NH (Next Hop) and old NCC (Next Hop Chaining Count) shall be present; otherwise the octets for old NH parameter shall not be present and the value of old NCC parameter shall be ignored by the receiver. . Multiple APN Rate Control Statuses (including the number of packets still allowed in the given time unit, the number of additional exception reports still allowed in the given time unit and the termination time of the current APN Rate Control validity period) may be included by the MME. The MM context shall contain the APN Rate Control Status(s) for PDN connection which are released and currentlty not re-established. Once a PDN connection is re-established, the related APN Rate Control Status shall be deleted. The UAMBRI shall be set to "0" by the old AMF, and then the Uplink/downlink Used UE AMBR parameter field are not present.The SAMBRI shall be set to "1" by the old AMF, if the AMF has the Uplink/downlink Subscribed UE AMBR received from the MME, or the Uplink/downlink Subscribed UE AMBR in 5G. The RLOS indication flag (bit 7 of octet s) shall be set to 1 if the UE is RLOS attached. Figure 8.38-5: EPS Security Context and Quadruplets If NHI (Next Hop Indicator), bit 5 of octet 5, is set to "1", then the optional parameters NH (Next Hop) and NCC (Next Hop Chaining Count) are both present, otherwise their octets are not present. The UE Radio Capability for Paging information is specified in the clause 9.2.1.98 of 3GPP TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [10]. If Length of UE Radio Capability for Paging information is zero, then the UE Radio Capability for Paging information shall not be present. The old MME shall, when available, include UE Radio Capability for Paging information to the new MME in the Context Response or Forward Relocation Request message as specified in the clause 5.11.4 of 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [4]. If the RAT type is indicated by the new MME in the Context Request message, then the old MME shall include the UE Radio Capability for Paging for the corresponding RAT type, if available. The Extended Access Restriction Data is composed of NRSRNA (NR as Secondary RAT Not Allowed), USSRNA (Unlicensed Spectrum in the form of LAA or LWA/LWIP as Secondary RAT Not Allowed), NRNA (NR in 5GS Not Allowed), NRUSRNA (New Radio Unlicensed as Secondary RAT Not Allowed), and of NRUNA (NR-U in 5GS Not Allowed). NOTE 5: As specified in clause 4.11.1.2.1 of 3GPP TS 23.502[ Procedures for the 5G System (5GS) ] [83], NRSRNA can be provided via N26 during handover from 5GC to EPC in order to allow the MME to make appropriate handling, e.g. SGW selection based on access restriction, or whether or not to allocate resources for secondary RAT during inter RAT handover. The UE additional security capability coding is specified in clause 9.9.3.53 of 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [23]. If Length of UE additional security capability is zero, then the field UE additional security capability in octets "(v+2) to x" shall not be present. The UE NR security capability coding is specified in clause 9.11.3.54 of 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [87]. If Length of UE NR security capability is zero, then the field UE NR security capability in octets "(x+2) to y" shall not be present. The Core Network Restrictions coding is specified in clause 7.2.230 of 3GPP TS 29.272[ Evolved Packet System (EPS); Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) related interfaces based on Diameter protocol ] [70]. If Length of Core Network Restrictions is zero, then the field of Core Network Restrictions in octets "(l+2) to (l+5)" shall not be present. The UE Radio Capability ID is specified in the clause 9.9.3.60 of 3GPP TS24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [23]. If Length of UE Radio Capability ID is zero, then the UE Radio Capability ID shall not be present. When supporting the RACS feature, the old MME shall include the PLMN-assigned UE Radio Capability ID if available, otherwise it shall include the Manufacturer-assigned UE Radio Capability ID, to the new MME as specified in the clause 5.11.3a of 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [4]. NOTE 6: If the MME supports RACS and the MME detects that the selected PLMN during a service request procedure is different from the currently registered PLMN for the UE, the MME stores the UE Radio Capability ID of the newly selected PLMN in the MM context as described in clause 5.11.3a of 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [4], and provides this UE Radio Capability ID to the target MME during any subsequent inter-MME mobility. The EPS NAS Security Context Type (ENSCT) shall be encoded in bits 1 and 2 of octet 'a'. ENSCT indicates the type of the Key Set Identifier, see Table 8.38-6. For EPS NAS Security Context usage see e.g. clause 6.4 in 3GPP TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [12]. Bits 3 to 8 of octet 'a' are spare and shall be set to '0' by the sender and ignored by the receiver. As depicted in Figure 8.38-6, the old MME will derive CK' and IK' from KASME and transmit the CK' and IK' to the new SGSN. Authentication Quintuplets, if available, shall be transmitted to the SGSN if, and only if the MME received them from this SGSN earlier, according to 3GPP TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [12] clause 6.1.5. An array of at most 5 Authentication Quintuplets may be included. The field 'Number of Quintuplets' shall be set to the value '0' if no Authentication Quintuplet is included (i.e. octets 'g+1 to h' are absent). An array of at most 5 Authentication Quadruplets may be included. The field 'Number of Quadruplets' shall be set to the value '0' if no Authentication Quadruplet is included (i.e. octets '40 to g' are absent). A key KASME shall never be transmitted to an SGSN according to 3GPP TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [12] clause 6.4. The Authentication Quintuplet and Authentication Quadruplet codings are specified in Figure 8.38-8 and Figure 8.38-9 respectively. The old SGSN/MME may deliver both Authentication Quadruplets and Authentication Quintuplets it holds to the peer combo node to optimize the procedure. NOTE 7: 3GPP TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [12] states that "EPS authentication data shall not be forwarded from an MME towards an SGSN". The statement above assumes that the old MME can determine by local configuration that the peer node is a combo SGSN/MME (as opposed to a single SGSN). Figure 8.38-6: UMTS Key, Quadruplets and Quintuplets Figure 8.38-7: Authentication Triplet Figure 8.38-8: Authentication Quintuplet Figure 8.38-9: Authentication Quadruplet Figure 8.38-10: APN Rate Control Status For the encoding of APN field see clause 8.6. Octets (k+13) to (k+20) (APN Rate Control Status validity Time) are coded as the time in seconds relative to 00:00:00 on 1 January 1900 (calculated as continuous time without leap seconds and traceable to a common time reference) where binary encoding of the integer part is in the 32 most significant bits and binary encoding of the fraction part in the 32 least significant bits. The fraction part is expressed with a granularity of 1 /2**32 second. Table 8.38-1: Security Mode Values Table 8.38-2: Used NAS Cipher Values Table 8.38-3: Used Cipher Values Table 8.38-4: Used NAS integrity protection algorithm Values Table 8.38-5: Used GPRS integrity protection algorithm Values Table 8.38-6: EPS NAS Security Context Type (ENSCT) in bits 1 and 2 of octet 'a' | 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.38 |
6,152 | – CSI-AperiodicTriggerStateList | The CSI-AperiodicTriggerStateList IE is used to configure the UE with a list of aperiodic trigger states. Each codepoint of the DCI field "CSI request" is associated with one trigger state (see TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3], clause 6.1.3.13). Upon reception of the value associated with a trigger state, the UE will perform measurement of CSI-RS, CSI-IM and/or SSB (reference signals) and aperiodic reporting on L1 according to all entries in the associatedReportConfigInfoList for that trigger state. CSI-AperiodicTriggerStateList information element -- ASN1START -- TAG-CSI-APERIODICTRIGGERSTATELIST-START CSI-AperiodicTriggerStateList ::= SEQUENCE (SIZE (1..maxNrOfCSI-AperiodicTriggers)) OF CSI-AperiodicTriggerState CSI-AperiodicTriggerState ::= SEQUENCE { associatedReportConfigInfoList SEQUENCE (SIZE(1..maxNrofReportConfigPerAperiodicTrigger)) OF CSI-AssociatedReportConfigInfo, ..., [[ ap-CSI-MultiplexingMode-r17 ENUMERATED {enabled} OPTIONAL -- Need R ]], [[ ltm-AssociatedReportConfigInfo-r18 LTM-CSI-ReportConfigId-r18 OPTIONAL -- Need R ]] } CSI-AssociatedReportConfigInfo ::= SEQUENCE { reportConfigId CSI-ReportConfigId, resourcesForChannel CHOICE { nzp-CSI-RS SEQUENCE { resourceSet INTEGER (1..maxNrofNZP-CSI-RS-ResourceSetsPerConfig), qcl-info SEQUENCE (SIZE(1..maxNrofAP-CSI-RS-ResourcesPerSet)) OF TCI-StateId OPTIONAL -- Cond Aperiodic }, csi-SSB-ResourceSet INTEGER (1..maxNrofCSI-SSB-ResourceSetsPerConfig) }, csi-IM-ResourcesForInterference INTEGER(1..maxNrofCSI-IM-ResourceSetsPerConfig) OPTIONAL, -- Cond CSI-IM-ForInterference nzp-CSI-RS-ResourcesForInterference INTEGER (1..maxNrofNZP-CSI-RS-ResourceSetsPerConfig) OPTIONAL, -- Cond NZP-CSI-RS-ForInterference ..., [[ resourcesForChannel2-r17 CHOICE { nzp-CSI-RS2-r17 SEQUENCE { resourceSet2-r17 INTEGER (1..maxNrofNZP-CSI-RS-ResourceSetsPerConfig), qcl-info2-r17 SEQUENCE (SIZE(1..maxNrofAP-CSI-RS-ResourcesPerSet)) OF TCI-StateId OPTIONAL -- Cond Aperiodic }, csi-SSB-ResourceSet2-r17 INTEGER (1..maxNrofCSI-SSB-ResourceSetsPerConfigExt) } OPTIONAL, -- Cond NoUnifiedTCI csi-SSB-ResourceSetExt INTEGER (1..maxNrofCSI-SSB-ResourceSetsPerConfigExt) OPTIONAL -- Need R ]], [[ resourcesForChannelTDCP-r18 SEQUENCE { resourceSet2TDCP-r18 INTEGER (1..maxNrofNZP-CSI-RS-ResourceSetsPerConfig), resourceSet3TDCP-r18 INTEGER (1..maxNrofNZP-CSI-RS-ResourceSetsPerConfig) OPTIONAL -- Need R } OPTIONAL, -- Cond TDCP applyIndicatedTCI-State-r18 CHOICE { perSet-r18 ENUMERATED {first, second}, perResource-r18 SEQUENCE (SIZE(1..maxNrofAP-CSI-RS-ResourcesPerSet)) OF ENUMERATED {first, second} } OPTIONAL, -- Need R applyIndicatedTCI-State2-r18 CHOICE { perSet-r18 ENUMERATED {first, second}, perResource-r18 SEQUENCE (SIZE(1..maxNrofAP-CSI-RS-ResourcesPerSet)) OF ENUMERATED {first, second} } OPTIONAL, -- Cond SecondCSICMR csi-ReportSubConfigTriggerList-r18 CSI-ReportSubConfigTriggerList-r18 OPTIONAL -- Need R ]] } -- TAG-CSI-APERIODICTRIGGERSTATELIST-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
6,153 | 9.9.3.15 ESM message container | The purpose of the ESM message container information element is to enable piggybacked transfer of a single ESM message within an EMM message. The ESM message included in this IE shall be coded as specified in clause 8.3, i.e. without NAS security header. The ESM message container information element is coded as shown in figure 9.9.3.15.1 and table 9.9.3.15.1. The ESM message container is a type 6 information element. Figure 9.9.3.15.1: ESM message container information element Table 9.9.3.15.1: ESM message container 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.3.15 |
6,154 | 8.3.3.2 Back-off timer value | The network may include this IE if the 5GSM cause is not #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", or #68 "not supported SSC mode", to request a minimum time interval before procedure retry is allowed. | 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 | 8.3.3.2 |
6,155 | 13.3.2.1 Direct communication | In direct communication, authentication between network functions within one PLMN shall use one of the following methods: - If the PLMN uses protection at the transport layer as described in clause 13.1, authentication provided by the transport layer protection solution shall be used for authentication between NFs. - If the PLMN does not use protection at the transport layer, authentication between NFs within one PLMN may be implicit by NDS/IP or physical security (see clause 13.1). If the PLMN uses token-based authorization, the network shall use protection at the transport layer as described in clause 13.1. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 13.3.2.1 |
6,156 | 5.4.1.2.4.3 EAP message reliable transport procedure accepted by the UE | The UE shall create an AUTHENTICATION RESPONSE message. If the received EAP message is an EAP-request message, the UE shall set the EAP message IE of the AUTHENTICATION RESPONSE message to the EAP-response message responding to the received EAP-request message. The UE shall send the AUTHENTICATION RESPONSE message to the AMF. Upon receipt of an AUTHENTICATION RESPONSE message, the AMF shall stop timer T3560. If the EAP message IE is included in the AUTHENTICATION RESPONSE message, the AMF handles the EAP message received in the EAP message IE of the AUTHENTICATION RESPONSE message. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.4.1.2.4.3 |
6,157 | 4.3.1.1 Charging Trigger Function | The Charging Trigger Function (CTF) generates charging events based on the observation of network resource usage as described in clause 4.1.1. In every network element and service element that provides charging information, the CTF is the focal point for collecting the information pertaining to chargeable events within the network element, assembling this information into matching charging events, and sending these charging events towards the CDF. The CTF is therefore a mandatory, integrated component in all network elements that provide offline charging functionality, as depicted in figure 4.2.1. It is made up of two functional blocks: - Accounting Metrics Collection The process that monitors signalling functions for calls, service events or sessions established by the network users, or the handling of user traffic for these calls, service events or sessions, or service delivery to the user via these calls, service events or sessions. It is required to provide metrics that identify the user and the user's consumption of network resources and/or services in real-time. The exact behaviour and functionality of this process e.g.: - trigger conditions for collection of charging information, - information elements to collect, - which service events, signalling or user traffic to monitor, - relationship to services / bearers / sessions, depends on functions / services that the NE provides. The Account Metrics Collection can therefore be considered as the network element dependent part of the CTF. Depending on implementation choice, NE functions (e.g. the handling of service events or signalling / user traffic) may be distributed among multiple physical "devices" within the NE. In order to be able to capture the required charging information from the service events or signalling / user traffic, the design of the Accounting Metrics Collection has to match the physical design / distribution of these functions within the NE. This implies that in case of such distributed NE functionality, the Accounting Metrics Collection becomes a distributed functionality itself. - Accounting Data Forwarding This process receives the collected accounting metrics and determines the occurrence of chargeable events from a set of one or more of these metrics. It then assembles charging events that match the detected chargeable events, and forwards the charging events towards the CDF via the Rf reference point. The charging events provide information pertinent to the chargeable event, i.e. characterising the network resource usage together with an identification of the involved user(s). There is no assumption of any synchronisation between the reception of individual accounting metrics, however, it must be possible for the Accounting Data Forwarding to complete its overall functionality per charging event in real-time. While the exact information received by the Account Data Forwarding from the Account Metrics Collection, and the relevant chargeable events, are specific to each type of network element, the overall functionality of receiving, assembling and forwarding the charging information can be considered generic. Hence the Accounting Data Forwarding is considered the NE independent part of the CTF. Even when distributed within the network element or service element, the CTF is considered to be part of the network element or service element. In service-specific cases, the CTF functional components of Accounting Metrics Collection and Accounting Data Forwarding are divided between the UE and the network element or service element. This architecture extension, conditionally required for specific services, is specified in Annex D. The behaviour of the CTF with respect to the definition of the chargeable events, the matching charging events and the information elements to collect is specified per domain, subsystem and service in the respective middle tier TS 32.25[ None ] x, TS 32.26[ None ] x and TS 32.27[ None ] x ([10] – [49]). | 3GPP TS 32.240 | Telecommunication management; Charging management; Charging architecture and principles | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.3.1.1 |
6,158 | – RACH-ConfigDedicated | The IE RACH-ConfigDedicated is used to specify the dedicated random access parameters. RACH-ConfigDedicated information element -- ASN1START -- TAG-RACH-CONFIGDEDICATED-START RACH-ConfigDedicated ::= SEQUENCE { cfra CFRA OPTIONAL, -- Need S ra-Prioritization RA-Prioritization OPTIONAL, -- Need N ..., [[ ra-PrioritizationTwoStep-r16 RA-Prioritization OPTIONAL, -- Need N cfra-TwoStep-r16 CFRA-TwoStep-r16 OPTIONAL -- Need S ]] } CFRA ::= SEQUENCE { occasions SEQUENCE { rach-ConfigGeneric RACH-ConfigGeneric, ssb-perRACH-Occasion ENUMERATED {oneEighth, oneFourth, oneHalf, one, two, four, eight, sixteen} OPTIONAL -- Cond Mandatory } OPTIONAL, -- Need S resources CHOICE { ssb SEQUENCE { ssb-ResourceList SEQUENCE (SIZE(1..maxRA-SSB-Resources)) OF CFRA-SSB-Resource, ra-ssb-OccasionMaskIndex INTEGER (0..15) }, csirs SEQUENCE { csirs-ResourceList SEQUENCE (SIZE(1..maxRA-CSIRS-Resources)) OF CFRA-CSIRS-Resource, rsrp-ThresholdCSI-RS RSRP-Range } }, ..., [[ totalNumberOfRA-Preambles INTEGER (1..63) OPTIONAL -- Cond Occasions ]], [[ msg1-RepetitionNum-r18 ENUMERATED {n2, n4, n8} OPTIONAL -- Cond 4StepCFRArep ]] } CFRA-TwoStep-r16 ::= SEQUENCE { occasionsTwoStepRA-r16 SEQUENCE { rach-ConfigGenericTwoStepRA-r16 RACH-ConfigGenericTwoStepRA-r16, ssb-PerRACH-OccasionTwoStepRA-r16 ENUMERATED {oneEighth, oneFourth, oneHalf, one, two, four, eight, sixteen} } OPTIONAL, -- Need S msgA-CFRA-PUSCH-r16 MsgA-PUSCH-Resource-r16, msgA-TransMax-r16 ENUMERATED {n1, n2, n4, n6, n8, n10, n20, n50, n100, n200} OPTIONAL, -- Need S resourcesTwoStep-r16 SEQUENCE { ssb-ResourceList SEQUENCE (SIZE(1..maxRA-SSB-Resources)) OF CFRA-SSB-Resource, ra-ssb-OccasionMaskIndex INTEGER (0..15) }, ... } CFRA-SSB-Resource ::= SEQUENCE { ssb SSB-Index, ra-PreambleIndex INTEGER (0..63), ..., [[ msgA-PUSCH-Resource-Index-r16 INTEGER (0..3071) OPTIONAL -- Cond 2StepCFRA ]] } CFRA-CSIRS-Resource ::= SEQUENCE { csi-RS CSI-RS-Index, ra-OccasionList SEQUENCE (SIZE(1..maxRA-OccasionsPerCSIRS)) OF INTEGER (0..maxRA-Occasions-1), ra-PreambleIndex INTEGER (0..63), ... } -- TAG-RACH-CONFIGDEDICATED-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
6,159 | 6.2.17 SEPP | The Security Edge Protection Proxy (SEPP) is a non-transparent proxy and supports the following functionality: - Message filtering and policing on inter-PLMN control plane interfaces. NOTE: The SEPP protects the connection between Service Consumers and Service Producers from a security perspective, i.e. the SEPP does not duplicate the Service Authorization applied by the Service Producers as specified in clause 7.1.4. - Topology hiding. Detailed functionality of SEPP, related flows and the N32 reference point, are specified in TS 33.501[ Security architecture and procedures for 5G System ] [29]. The SEPP applies the above functionality to every Control Plane message in inter-PLMN signalling, acting as a service relay between the actual Service Producer and the actual Service Consumer. For both Service Producer and Consumer, the result of the service relaying is equivalent to a direct service interaction. Every Control Plane message in inter-PLMN signalling between the SEPPs may pass via IPX entities. More details on SEPPs and the IPX entities are described in TS 29.500[ 5G System; Technical Realization of Service Based Architecture; Stage 3 ] [49] and TS 33.501[ Security architecture and procedures for 5G System ] [29]. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 6.2.17 |
6,160 | 5.3.24 WUS assistance | A UE supporting reception of WUS assistance information indicates its capability for reception of WUS assistance information during registration procedure (see 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8]). The UE supporting WUS assistance information may include its UE paging probability information in the Requested WUS assistance information IE in the REGISTRATION REQUEST message (see 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8]). The UE shall not include its UE paging probability information during: a) a registration procedure for initial registration for emergency services (see subclause 5.5.1.2); b) a registration procedure for initial registration for initiating an emergency PDU session (see subclause 5.5.1.2); c) a registration procedure for mobility and periodic registration update (see subclause 5.5.1.3) for initiating an emergency PDU session if the UE is in the state 5GMM-REGISTERED.ATTEMPTING-REGISTRATION-UPDATE; or d) a registration procedure for mobility and periodic registration update (see subclause 5.5.1.3) when the UE has an emergency PDU session established. The UE and the network may negotiate the UE paging probability information during a registration procedure when the UE does not have an emergency PDU session. The UE paging probability information is an assistance information used to determine the WUS group for paging UE (see 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8], 3GPP TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [25B]). NOTE 1: The determination of UE paging probability information is up to UE implementation. If a UE supporting WUS assistance information did not receive the Negotiated WUS assistance information IE during the last registration procedure due to an active emergency PDU session over 3GPP access, the UE shall initiate a registration procedure for mobility and periodic registration update to request WUS assistance information after the emergency PDU session is released over 3GPP access. If the UE does not have an emergency PDU session and the network accepts the use of the WUS assistance information for the UE, the network determines the negotiated UE paging probability information for the UE based on the requested UE paging probability information, if any, local configuration or previous statistical information for the UE, and then indicates the negotiated UE paging probability information in the Negotiated WUS assistance information IE to the UE in the REGISTRATION ACCEPT message. The network shall store the negotiated UE paging probability information in the 5GMM context of the UE for paging. The UE shall use WUS assistance information only if the UE received the Negotiated WUS assistance information IE during the last registration procedure. If the UE did not receive the Negotiated WUS assistance information IE during the last registration procedure, the UE shall delete any existing WUS assistance information received from the network. If the network did not accept the request to use WUS assistance information, the network shall delete the stored negotiated UE paging probability information for the UE, if available. When an emergency PDU session is successfully established after the UE received the Negotiated WUS assistance information IE during the last registration procedure, the UE and the AMF shall not use WUS assistance information until: - the successful completion of the PDU session release procedure of the emergency PDU session; - the UE receives WUS assistance information during a registration procedure with PDU session status IE or upon successful completion of a service request procedure, if the UE or the network locally releases the emergency PDU session; or - the successful completion of the handover of the emergency PDU session to non-3GPP access. NOTE 2: WUS assistance is not supported by NR connected to 5GCN. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.3.24 |
6,161 | 6.1.4 Location update | In case a user identifies itself using a TMSIo/LAIo pair that was assigned by the visited VLRn the IMSI can normally be retrieved from the database. If this is not the case, the visited VLRn should request the user to identify itself by means of its permanent user identity. This mechanism is described in 6.2. In case a user identifies itself using a TMSIo/LAIo pair that was not assigned by the visited VLRn and the visited VLRn and the previously visited VLRo exchange authentication data, the visited VLRn should request the previously visited VLRo to send the permanent user identity. This mechanism is described in 6.3.4, it is integrated in the mechanism for distribution of authentication data between VLRs. If the previously visited VLRo cannot be contacted or cannot retrieve the user identity, the visited VLRn should request the user to identify itself by means of its permanent user identity. This mechanism is described in 6.2. | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | 6.1.4 |
6,162 | 4 Architecture model and concepts 4.1 General concepts | The 5G System architecture is defined to support data connectivity and services enabling deployments to use techniques such as e.g. Network Function Virtualization and Software Defined Networking. The 5G System architecture shall leverage service-based interactions between Control Plane (CP) Network Functions where identified. Some key principles and concept are to: - Separate the User Plane (UP) functions from the Control Plane (CP) functions, allowing independent scalability, evolution and flexible deployments e.g. centralized location or distributed (remote) location. - Modularize the function design, e.g. to enable flexible and efficient network slicing. - Wherever applicable, define procedures (i.e. the set of interactions between network functions) as services, so that their re-use is possible. - Enable each Network Function and its Network Function Services to interact with other NF and its Network Function Services directly or indirectly via a Service Communication Proxy if required. The architecture does not preclude the use of another intermediate function to help route Control Plane messages (e.g. like a DRA). - Minimize dependencies between the Access Network (AN) and the Core Network (CN). The architecture is defined with a converged core network with a common AN - CN interface which integrates different Access Types e.g. 3GPP access and non-3GPP access. - Support a unified authentication framework. - Support "stateless" NFs, where the "compute" resource is decoupled from the "storage" resource. - Support capability exposure. - Support concurrent access to local and centralized services. To support low latency services and local access to data networks, UP functions can be deployed close to the Access Network. - Support roaming with both Home routed traffic as well as Local breakout traffic in the visited PLMN. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4 |
6,163 | 5.5.6 Progress | At any time during the establishment or release of a call and during an active call the network may send a PROGRESS message to the mobile station. On receipt of a PROGRESS message during the establishment or release of a call the mobile station shall stop all call control timers related to that call. NOTE: If the PROGRESS has been received before the receipt of a CALL PROCEEDING message, the mobile station will not start timer T310 on receipt of a CALL PROCEEDING message, see subclause 5.2.1.1.3. Figure 5.11/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Progress | 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.5.6 |
6,164 | 5.3.10.4 RLF cause determination | The UE shall set the rlf-Cause in the VarRLF-Report as follows: 1> if the UE declares radio link failure due to T310 expiry: 2> set the rlf-Cause as t310-Expiry; 1> else if the UE declares radio link failure due to the random access problem indication from MCG MAC: 2> if the random access procedure was initiated for beam failure recovery: 3> set the rlf-Cause as beamFailureRecoveryFailure; 2> else: 3> set the rlf-Cause as randomAccessProblem; 1> else if the UE declares radio link failure due to the reaching of maximum number of retransmissions from the MCG RLC: 2> set the rlf-Cause as rlc-MaxNumRetx; 1> else if the UE declares radio link failure due to consistent uplink LBT failures: 2> set the rlf-Cause as lbtFailure; 1> else if the IAB-MT declares radio link failure due to the reception of a BH RLF indication on BAP entity: 2> set the rlf-Cause as bh-rlfRecoveryFailure. 1> else if the UE declares radio link failure due to T312 expiry: 2> set the rlf-Cause as t312-Expiry; | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.10.4 |
6,165 | 5.2.6.4.3 Nnef_ParameterProvision_Create service operation | Service operation name: Nnef_ParameterProvision_Create Description: The consumer creates a 5G VN group, or Multicast MBS related information group. Inputs, Required: AF Identifier, Transaction Reference ID. Inputs, Optional: GPSI or UE addressing information, one or multiple Expected UE Behaviour parameters (optionally with associated confidence and/or accuracy levels) or one or multiple Application-Specific Expected UE Behaviour parameters (optionally with associated confidence and/or accuracy levels), External Group ID for 5G VN group creation or for multicast MBS group creation, External Group ID, 5G VN group related information (e.g. 5G VN group data, 5G VN membership management), MTC Provider Information, Multicast MBS related information, DNN and S-NSSAI specific Group Parameters, DNN, S-NSSAI, PLMN IDs, ECS Address Configuration Information. Outputs, Required: Operation execution result indication. Outputs, Optional: Transaction specific parameters, if available. External Identifier (representing an AF specific UE Identifier). For Multicast MBS related information, refer to TS 23.247[ Architectural enhancements for 5G multicast-broadcast services ] [78]. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.6.4.3 |
6,166 | – UAC-BarringInfoSetList | The IE UAC-BarringInfoSetList provides a list of access control parameter sets. An access category can be configured with access parameters according to one of the sets. UAC-BarringInfoSetList information element -- ASN1START -- TAG-UAC-BARRINGINFOSETLIST-START UAC-BarringInfoSetList ::= SEQUENCE (SIZE(1..maxBarringInfoSet)) OF UAC-BarringInfoSet UAC-BarringInfoSetList-v1700 ::= SEQUENCE (SIZE(1..maxBarringInfoSet)) OF UAC-BarringInfoSet-v1700 UAC-BarringInfoSet ::= SEQUENCE { uac-BarringFactor ENUMERATED {p00, p05, p10, p15, p20, p25, p30, p40, p50, p60, p70, p75, p80, p85, p90, p95}, uac-BarringTime ENUMERATED {s4, s8, s16, s32, s64, s128, s256, s512}, uac-BarringForAccessIdentity BIT STRING (SIZE(7)) } UAC-BarringInfoSet-v1700 ::= SEQUENCE { uac-BarringFactorForAI3-r17 ENUMERATED {p00, p05, p10, p15, p20, p25, p30, p40, p50, p60, p70, p75, p80, p85, p90, p95} OPTIONAL -- Need S } -- TAG-UAC-BARRINGINFOSETLIST-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
6,167 | 4.7.4.4 Backhaul RLF Recovery | When the IAB-node using SA-mode declares RLF on the backhaul link, it can perform RLF recovery at another parent node underneath the same or underneath a different IAB-donor-CU. In the latter case, the collocated IAB-DU and the IAB-DU(s) of its descendant node(s) may retain the F1 connectivity with the initial IAB-donor-CU, while the IAB-MT(s) of the descendant node(s) and all the served UEs retain the RRC connectivity with the initial IAB-donor-CU, in the same manner as for inter-donor partial migration. The BH RLF recovery procedure for the IAB-node is captured in TS 38.401[ NG-RAN; Architecture description ] [4]. BH RLF declaration for IAB-node and the aspects of RLF recovery by the IAB-MT are handled in clause 9.2.7 of the present document. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 4.7.4.4 |
6,168 | 10.5.4.33 Service category | The purpose of the Service category information element is to provide the network with information about services invoked by the user equipment. The Service category information element is coded as shown in figure 10.5.118d/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.135d/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] The Service category is a type 4 information element with a minimum length of 3 octets. Figure 10.5.118d/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Service Category information element Table 10.5.135d/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Service Category information element Emergency Service Category Value (octet 3) The meaning of the Emergency Category Value is derived from the following settings (see 3GPP TS 22.101[ Service aspects; Service principles ] [8] clause 10): Bit 1 Police Bit 2 Ambulance Bit 3 Fire Brigade Bit 4 Marine Guard Bit 5 Mountain Rescue Bit 6 manually initiated eCall Bit 7 automatically initiated eCall Bit 8 is spare and set to "0" A mobile station not initiating an eCall shall set bit 6 and bit 7 to "0" and may set one or more of bit 1, bit 2, bit 3, bit 4 or bit 5 to "1". If more than one of these bits is set to "1", routing to a combined emergency centre (e.g. ambulance and fire brigade in Japan) is required. A mobile station initiating an eCall shall set either bit 6 or bit 7 to "1" and shall set all other bits to "0". A MSC supporting eCall shall use the information indicated in bit 6 and bit 7 to route the manually or automatically initiated eCall to an operator defined emergency call centre. If the MSC can not match the received service category to any of the emergency centres, or if no bit is set to "1", the MSC shall route the emergency call to an operator defined default emergency centre. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 10.5.4.33 |
6,169 | 16a.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 an Inter-SGSN RA update occurs). Upon reception of an UpdatePDPContextRequest from the SGSN, the GGSN may send an Accounting Request (Interim) to the Diameter server to update the necessary information related to this PDP context (see figure 25c). 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 or the GTP-U TEID have changed, then the GGSN should not send the Accounting Request (Interim) message to the Diameter server. In such cases, the GGSN need not wait for the Diameter Accounting Answer from the Diameter server message before sending the UpdatePDPContextResponse to the SGSN. The GGSN may delete the PDP context if the Accounting Answer is not received from the Diameter server. NOTE: As shown the GGSN need not wait for the Diameter Accounting Answer message from the Diameter server to send the UpdatePDPContextResponse to the SGSN. The GGSN may delete the PDP context if the Accounting Answer is not received from the Diameter server. Figure 25c: Diameter 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 | 16a.3.3 |
6,170 | – RACH-ConfigCommonTwoStepRA | The IE RACH-ConfigCommonTwoStepRA is used to specify cell specific 2-step random-access type parameters. RACH-ConfigCommonTwoStepRA information element -- ASN1START -- TAG-RACH-CONFIGCOMMONTWOSTEPRA-START RACH-ConfigCommonTwoStepRA-r16 ::= SEQUENCE { rach-ConfigGenericTwoStepRA-r16 RACH-ConfigGenericTwoStepRA-r16, msgA-TotalNumberOfRA-Preambles-r16 INTEGER (1..63) OPTIONAL, -- Need S msgA-SSB-PerRACH-OccasionAndCB-PreamblesPerSSB-r16 CHOICE { oneEighth ENUMERATED {n4,n8,n12,n16,n20,n24,n28,n32,n36,n40,n44,n48,n52,n56,n60,n64}, oneFourth ENUMERATED {n4,n8,n12,n16,n20,n24,n28,n32,n36,n40,n44,n48,n52,n56,n60,n64}, oneHalf ENUMERATED {n4,n8,n12,n16,n20,n24,n28,n32,n36,n40,n44,n48,n52,n56,n60,n64}, one ENUMERATED {n4,n8,n12,n16,n20,n24,n28,n32,n36,n40,n44,n48,n52,n56,n60,n64}, two ENUMERATED {n4,n8,n12,n16,n20,n24,n28,n32}, four INTEGER (1..16), eight INTEGER (1..8), sixteen INTEGER (1..4) } OPTIONAL, -- Cond 2StepOnly msgA-CB-PreamblesPerSSB-PerSharedRO-r16 INTEGER (1..60) OPTIONAL, -- Cond SharedRO msgA-SSB-SharedRO-MaskIndex-r16 INTEGER (1..15) OPTIONAL, -- Need S groupB-ConfiguredTwoStepRA-r16 GroupB-ConfiguredTwoStepRA-r16 OPTIONAL, -- Need S msgA-PRACH-RootSequenceIndex-r16 CHOICE { l839 INTEGER (0..837), l139 INTEGER (0..137), l571 INTEGER (0..569), l1151 INTEGER (0..1149) } OPTIONAL, -- Cond 2StepOnly msgA-TransMax-r16 ENUMERATED {n1, n2, n4, n6, n8, n10, n20, n50, n100, n200} OPTIONAL, -- Need R msgA-RSRP-Threshold-r16 RSRP-Range OPTIONAL, -- Cond 2Step4Step msgA-RSRP-ThresholdSSB-r16 RSRP-Range OPTIONAL, -- Need R msgA-SubcarrierSpacing-r16 SubcarrierSpacing OPTIONAL, -- Cond 2StepOnlyL139 msgA-RestrictedSetConfig-r16 ENUMERATED {unrestrictedSet, restrictedSetTypeA, restrictedSetTypeB} OPTIONAL, -- Cond 2StepOnly ra-PrioritizationForAccessIdentityTwoStep-r16 SEQUENCE { ra-Prioritization-r16 RA-Prioritization, ra-PrioritizationForAI-r16 BIT STRING (SIZE (2)) } OPTIONAL, -- Cond InitialBWP-Only ra-ContentionResolutionTimer-r16 ENUMERATED {sf8, sf16, sf24, sf32, sf40, sf48, sf56, sf64} OPTIONAL, -- Cond 2StepOnly ..., [[ ra-PrioritizationForSlicingTwoStep-r17 RA-PrioritizationForSlicing-r17 OPTIONAL, -- Cond InitialBWP-Only featureCombinationPreamblesList-r17 SEQUENCE (SIZE(1..maxFeatureCombPreamblesPerRACHResource-r17)) OF FeatureCombinationPreambles-r17 OPTIONAL -- Cond AdditionalRACH ]] } GroupB-ConfiguredTwoStepRA-r16 ::= SEQUENCE { ra-MsgA-SizeGroupA-r16 ENUMERATED {b56, b144, b208, b256, b282, b480, b640, b800, b1000, b72, spare6, spare5, spare4, spare3, spare2, spare1}, messagePowerOffsetGroupB-r16 ENUMERATED {minusinfinity, dB0, dB5, dB8, dB10, dB12, dB15, dB18}, numberOfRA-PreamblesGroupA-r16 INTEGER (1..64) } -- TAG-RACH-CONFIGCOMMONTWOSTEPRA-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
6,171 | 7.3.7 Context Acknowledge | A Context Acknowledge message shall be sent as a response to a previous Context Response message, only if the previous Context Response message is received with the acceptance cause. Possible cause values are specified in Table 8.4-1. Message specific cause values are: - "User authentication failed". - "Relocation failure due to NAS message redirection". - "Denied in RAT". Upon receiving cause value other than the request was accepted, the old MME/S4-SGSN shall continue as if the Context Request was never received. Table 7.3.7-1 specifies the presence requirements and conditions of the IEs in the message. Table 7.3.7-1: Information Elements in a Context Acknowledge Table 7.3.7-2: Bearer Context within Context Acknowledge | 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.7 |
6,172 | 5.3.21 Wake-up signal assistance | A UE supporting wake-up signal (WUS) assistance can indicate its WUS assistance capability during attach or tracking area updating procedure (see 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [10]). The UE supporting WUS assistance may include its UE paging probability information in the Requested WUS assistance information IE during an attach or tracking area updating procedure (see 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [10]). The UE shall not include its UE paging probability information during: - an attach for emergency bearer services procedure; - an attach procedure for initiating a PDN connection for emergency bearer services with attach type not set to "EPS emergency attach"; - a tracking area updating procedure for initiating a PDN connection for emergency bearer services; or. - a tracking area updating procedure when the UE has a PDN connection established for emergency bearer services. The UE and the network may negotiate the UE paging probability information during an attach or tracking area updating procedure when the UE is not attached for emergency bearer services. The UE paging probability information is an assistance information used to determine the WUS group for paging UE (see 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [10], 3GPP TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [20]). NOTE: The determination of UE paging probability information is up to UE implementation. If the UE is not attached for emergency bearer services and the network accepts the use of the WUS assistance for the UE, the network determines the negotiated UE paging probability information for the UE based on the requested UE paging probability information, if any, local configuration or previous statistical information for the UE, and then indicates the negotiated UE paging probability information in the Negotiated WUS assistance information IE to the UE when accepting the attach or the tracking area updating procedure. The network shall store the negotiated UE paging probability information in the EMM context of the UE for paging. The UE shall use WUS assistance only if it received the Negotiated WUS assistance information IE during the last attach or tracking area updating procedure. If the UE did not receive the Negotiated WUS assistance information IE during the last attach or tracking area updating procedure, the UE shall delete any existing WUS assistance information received from the network. If the network did not accept the request to use WUS assistance, the network shall delete the stored negotiated UE paging probability information for the UE, if available. When a PDN connection for emergency bearer service is successfully established after the UE received the Negotiated WUS assistance information IE during the last attach or tracking area updating procedure, the UE and the network shall not use WUS assistance information until: - the successful completion of the PDN disconnect procedure of the PDN connection for emergency bearer services or EPS bearer context deactivation procedure of the EPS bearer context for emergency, or - the UE receives WUS assistance information during a tracking area updating procedure with EPS bearer context synchronization or upon successful completion of a service request procedure, if the UE or the network locally releases the PDN connection for emergency bearer service. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.3.21 |
6,173 | 4.13.6.3 Transfer of PDU session used for IMS voice from non-3GPP access to 5GS | Figure 4.13.6.3-1: Transfer of PDU session used for IMS voice from non-3GPP access to 5GS When the UE has an ongoing IMS voice session via non-3GPP access using ePDG or N3IWF and the session is transferred to NG-RAN, depending on the selected RAT in 5GS (NR or E-UTRA) and the support of EPS/inter-RAT fallback in NG-RAN, either the IMS voice session continues over NG-RAN (E-UTRA) or EPS/inter-RAT fallback is triggered. Steps 1, 2 and 3 apply to either of the above two cases. 1. UE has ongoing IMS voice session via non-3GPP access using ePDG or N3IWF. UE is triggered to move to 3GPP access and camps in NG-RAN. 2. If the UE is not registered via 3GPP access, the UE shall initiate Registration procedure as defined in clause 4.2.2.2.2. 3. UE initiates PDU session establishment for the PDU session used for IMS voice service in order to initiate handover from EPC/ePDG to 5GS as defined in clause 4.11.4.1 step 2 or to initiate handover from N3IWF to 3GPP access in 5GC in step 2 of clauses 4.9.2.1 and 4.9.2.3. The SMF accepts the PDU session transfer from the UE. NOTE 1: If the UE is aware (e.g. implementation-dependent mechanisms) that voice over NR may not be natively supported in the current Registration area, the UE can attempt to move to E-UTRA to initiate a handover of the IMS PDU Session to EPC or 5GC to continue the IMS voice session. The remaining steps are not executed. 4. NG-RAN may decide to trigger EPS or inter-RAT fallback, taking into account UE capabilities, indication from AMF that "Redirection for EPS fallback for voice is possible" (received as part of initial context setup as defined in TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [10]), network configuration (e.g. N26 availability configuration) and radio conditions. NG-RAN may initiate measurement report solicitation from the UE including E-UTRA as target. If NG-RAN does not trigger EPS or inter-RAT fallback, then the procedure stops here and following steps are not executed. NOTE 2: If the AMF has indicated that "Redirection for EPS fallback for voice is not possible", then EPS fallback for IMS voice is not performed. If NG-RAN has not received indication "Redirection for EPS fallback for voice", the decision to execute EPS fallback for IMS voice or not is based on network configuration (e.g. based on N26 availability and other criteria). 5. NG-RAN responds indicating rejection either to set up the QoS flow for IMS voice or the entire PDU session used for IMS voice service as received in step 3 towards the SMF+PGW-C (or H-SMF+P-GW-C via V-SMF, in the case of roaming scenario) via AMF with an indication that mobility due to fallback for IMS voice is ongoing. The SMF+PGW-C reports the EPS Fallback event to the PCF if the PCF has subscribed to this event. If NG-RAN responds indicating rejection to set up the QoS flow for IMS voice, steps 5-7 from clause 4.13.6.1 are executed if EPS fallback is triggered, or steps 5-6 from clause 4.13.6.2 are executed if inter-RAT Fallback for IMS voice is triggered. The SMF+PGW-C executes the release of resources in non-3GPP AN as specified in step 3 of clauses 4.11.4.1, 4.9.2.1 and 4.9.2.3. NOTE 3: The timing of executing the release of resources in non-3GPP AN will depend on whether NG-RAN decides to trigger EPS or inter-RAT fallback but will take place at least after step 5. If NG-RAN rejects entire PDU session used for IMS voice service, the SMF should stop the ongoing procedure and keep the PDN connection / PDU Session at non-3GPP side. The NG-RAN performs AN release with redirection or handover procedure. In both cases, after receiving the AN release with redirection or completion of the handover procedure the UE initiates TAU procedure. In the case of inter-system redirection to EPS, if the UE decides to re-initiate handover of an IMS voice session over non-3GPP access to EPS after inter-system change from 5GS to EPS is completed, the UE includes active flag in the request. NOTE 4: Depending on UE implementation, the UE can re-initiate handover of an IMS voice session over non-3GPP access to EPS if the inter-system change from 5GS to EPS is triggered by the NG-RAN and the UE does not receive a response to the PDU session establishment request i.e. when the establishment of the entire PDU session used for voice is rejected by NG-RAN. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.13.6.3 |
6,174 | 5.4.4.2.4 Receipt of a RELEASE message from the mobile station | 5.4.4.2.4.1 Release, CCBS not requested For a network that does not support the "CCBS activation" option: The call control entity of the network in any state except the "null" state and the "release request" state, shall, upon receipt of a RELEASE message: stop all running call control timers; send a RELEASE COMPLETE message; release the MM connection; and return to the "null" state. For a network that does support the "CCBS activation" option: The call control entity of the network in any state except the "null" state and the "release request" state, shall, upon receipt of a RELEASE message without a Facility IE including an Invoke=CCBSRequest: stop all running call control timers; send a RELEASE COMPLETE message; release the MM connection; and return to the "null" state. 5.4.4.2.4.2 Release, CCBS Requested For a network that does not support the "CCBS activation" option: The call control entity of the network in any state except the "null" state and the "release request" state, shall, upon receipt of a RELEASE message: stop all running call control timers; send a RELEASE COMPLETE message; release the MM connection; and return to the "null" state. For a network that does support the "CCBS activation" option: The call control entity of the network in any state except the "null" state and the "release request" state, shall, upon receipt of a RELEASE message containing a Facility IE including an Invoke=CCBSRequest: stop all running call control timers; then attempt to activate the recall; then send a RELEASE COMPLETE message indicating the success or failure of the recall activation attempt; release the MM connection; and return to the "null" state. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.4.4.2.4 |
6,175 | 6.3.2 Network-requested PDU session modification procedure 6.3.2.1 General | The purpose of the network-requested PDU session modification procedure is to enable the network to modify a PDU session, re-negotiate header compression configuration associated to a PDU session, convey a port management information container, to trigger EAS rediscovery, provide updated DNS server address(es) due to the newly selected local DNS server or the newly selected EASDF, provide updated ECS configuration information, remove joined UE from one or more multicast MBS sessions associated with a PDU session, update ATSSS parameters (e.g. ATSSS rules), update the MBS service area or the security information of multicast MBS session that the UE has joined or to inform about the result of service-level AA procedure or C2 authorization for UAS services. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.3.2 |
6,176 | 5.3.11.3 UE Activity Notification procedure | The UE Activity Notification procedure is illustrated in Figure 5.3.11.3-1. Figure 5.3.11.3-1: UE Activity Procedure 1) The MME receives an indication regarding UE reachability, e.g. an Attach Request message from the UE or MME receive an indication from S-GW that UE has handed over to non-3GPP coverage. 2) If the MME contains an MM context of the UE and if URRP-MME for that UE is configured to report once that the UE is reachable, the MME shall send a UE-Activity-Notification (IMSI, UE-Reachable) message to the HSS and clears the corresponding URRP-MME for that UE. 3) When the HSS receives the UE-Activity-Notification (IMSI, UE-Reachable) message or the Update Location message for an UE that has URRP-MME set, it triggers appropriate notifications to the entities that have subscribed to the HSS for this notification and clears the URRP-MME for that UE. | 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.11.3 |
6,177 | 8.7.19 TDD (8 Rx) | The parameters specified in Table 8.7.19-1 are valid for all TDD tests for 8Rx capable UEs unless otherwise stated. For 2/4 layer carrier configurations, please refer to Table 8.7.10-1. 8 layer carier configuration is specified in Table 8.7.19-1. Table 8.7.19-1: Common Test Parameters for 8 Layer (TDD) For UE not supporting 256QAM, the TB success rate shall be higher than 85% when PDSCH are scheduled with FRC in Table 8.7.19-2 with the downlink physical channel setup according to Annex C.3.2. For UE supporting 256QAM, the TB success rate shall be higher than 85% when PDSCH are scheduled with FRC in Table 8.7.19-3 with the downlink physical channel setup according to Annex C.3.2. For UE supporting 256QAM, the requirement with 64QAM is not applicable. The TB success rate is defined as 100%*NDL_correct_rx/ (NDL_newtx + NDL_retx), where NDL_newtx is the number of newly transmitted DL transport blocks, NDL_retx is the number of retransmitted DL transport blocks, and NDL_correct_rx is the number of correctly received DL transport blocks. The TB success rate shall be sustained during at least 300 frames. Table 8.7.19-2: Per-CC FRC for SDR test (TDD 64QAM) Table 8.7.19-3: Per-CC FRC for SDR test (TDD 256QAM) CA configuration, bandwidth combination and MIMO layer on each CC is determined by following procedure. Select the set(s) of {CA configuration, bandwidth combination, MIMO layer} among all the supported CA configurations that leads to the largest equivalent aggregated bandwidth which does not cause the transport block bits within a TTI to exceed the capability of the category of UE under test when the defined reference channel applies on each CC. The equivalent aggregated bandwidth is defined as Where is the number of CCs, and are MIMO layer and bandwidth of CC . And for and for - The procedure applies also for single carrier using operating band instead of CA configuration, and bandwidth instead of bandwidth combination. | 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.7.19 |
6,178 | 4.9.1.2.2 Xn based inter NG-RAN handover without User Plane function re-allocation | This procedure is used to hand over a UE from a source NG-RAN to Target NG-RAN using Xn when the AMF is unchanged and the SMF decides to keep the existing UPF. The UPF referred in this clause 4.9.1.2.2 is the UPF which terminates N3 interface in the 5GC for non-roaming or local breakout roaming scenario, V-UPF which terminates N3 interface in 5GC for home routed roaming scenario. The SMF referred in this clause 4.9.1.2.2 is the V-SMF for home routed roaming scenario. The presence of IP connectivity between the Source UPF and Target NG-RAN is assumed. The call flow is shown in figure 4.9.1.2.2-1. Figure 4.9.1.2.2-1: Xn based inter NG-RAN handover without UPF re-allocation 1a. If the PLMN has configured secondary RAT usage reporting, the source NG-RAN node during the handover execution phase may provide RAN usage data Report (N2 SM Information (Secondary RAT usage data), Handover Flag, Source to Target transparent container) to the AMF. The source NG-RAN node shall provide this only when the Target NG-RAN has confirmed handover over Xn interface. The Handover Flag indicates to the AMF that it should buffer the N2 SM Information containing the usage data report before forwarding it. If the source NG RAN and Target NG RAN support RACS as defined in TS 23.501[ System architecture for the 5G System (5GS) ] [2], the source NG-RAN provides the UE's UE Radio Capability ID to the Target NG-RAN. If the source NG-RAN has knowledge that the Target NG-RAN might not have a local copy of the Radio Capability corresponding to the UE Radio Capability ID (i.e. because the source NG-RAN had itself to retrieve the UE's Radio Capability from the AMF) then the source NG-RAN may also send some or all of the UE's Radio Capability to the Target NG-RAN (the size limit based on local configuration) in Xn signalling as defined in TS 38.423[ NG-RAN; Xn Application Protocol (XnAP) ] [72] . In the case of inter-PLMN handover, when the source and Target NG-RAN support RACS as defined in TS 23.501[ System architecture for the 5G System (5GS) ] [2] and the source NG-RAN determines based on local configuration that the Target PLMN does not support the UE Radio Capability ID assigned by the source PLMN, then the source NG-RAN shall provide the UE radio access capabilities to the Target NG-RAN and shall not send the UE Radio Capability ID. If, as permitted in TS 38.423[ NG-RAN; Xn Application Protocol (XnAP) ] [72], the Target NG-RAN during the handover preparation received the UE radio access capabilities but did not receive the UE Radio Capability ID, NG-RAN shall proceed with handover using the received UE radio access capabilities. If the Target NG-RAN received both the UE radio access capabilities and the UE Radio Capability ID, then the Target NG-RAN shall use any locally stored UE radio access capability information corresponding to the UE Radio Capability ID. If none are stored locally, the Target NG-RAN may request the full UE radio access capability information from the core network. If the full UE radio access capability information is not promptly received from the core network, or the Target NG-RAN chooses not to request them, then the Target NG-RAN shall proceed with the UE radio access capabilities sent by the source NG-RAN. The Target NG-RAN shall not use the UE radio access capability information received from the source NG-RAN for any other UE with the same the UE Radio Capability ID. 1b. Target NG-RAN to AMF: N2 Path Switch Request (List of PDU Sessions To Be Switched with N2 SM Information, List of PDU Sessions that failed to be established with the failure cause given in the N2 SM information element, UE Location Information, established QoS Flows status (active/not active) for QoS monitoring configuration for congestion information, established QoS Flows status (active/not active) for ECN marking for L4S, PDU Set Based Handling Support Indication included in the N2 SM information). The Target NG-RAN sends an N2 Path Switch Request message to an AMF to inform that the UE has moved to a new Target cell and provides a List Of PDU Sessions To Be Switched. AN Tunnel Info for each PDU Session to be switched is included in the N2 SM Information. If redundant transmission is performed for one or more QoS Flows in the PDU Session, two AN Tunnel Info are provided by the Target NG-RAN and the Target NG-RAN indicates to the SMF one of the AN Tunnel Info is used as the redundancy tunnel of the PDU Session as described in clause 5.33.2.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If only one AN Tunnel Info is provided by the Target NG-RAN for the PDU session, the SMF may release these QoS Flows by triggering PDU Session Modification procedure as specified in clause 4.3.3 after the handover procedure. The serving PLMN ID is included in the message. The Target NG-RAN shall include the PDU Session in the PDU Sessions Rejected list: - If none of the QoS Flows of a PDU Session are accepted by the Target NG-RAN; or - If the corresponding network slice is not supported in the Target NG-RAN; or - When the NG-RAN cannot set up user plane resources fulfilling the User Plane Security Enforcement with a value Required, the NG-RAN rejects the establishment of user plane resources for the PDU Session. If the NG-RAN cannot set up user plane resources fulfilling the User Plane Security Enforcement with a value Preferred, the NG-RAN establishes the user plane resources for the PDU session and shall include the PDU Session in the PDU Sessions Modified list. PDU Sessions Rejected contains an indication of whether the PDU session was rejected because User Plane Security Enforcement is not supported in the Target NG-RAN. Depending on the type of target cell, the Target NG-RAN includes appropriate information in this message. For the PDU Sessions to be switched to the Target NG-RAN, the N2 Path Switch Request message shall include the list of accepted QoS Flows. For each QoS Flow accepted with an Alternative QoS Profile as specified in TS 23.501[ System architecture for the 5G System (5GS) ] [2], the N2 SM Information shall include a reference to the fulfilled Alternative QoS Profile. The NG-RAN includes the PDU Set Based Handling Support Indication in N2 SM information as defined in clause 5.37.5.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. 2. AMF to SMF: Nsmf_PDUSession_UpdateSMContext Request (N2 SM information received from T-RAN in step 1b and N2 SM Information from source NG-RAN (Secondary RAT usage data), UE Location Information, UE presence in LADN service area). The N2 SM Information here from source NG-RAN is the one buffered at step 1a when applicable. The AMF sends N2 SM information by invoking the Nsmf_PDUSession_UpdateSMContext request service operation for each PDU Session in the lists of PDU Sessions received in the N2 Path Switch Request. The Nsmf_PDUSession_UpdateSMContext Request contains either an indication that the PDU Session Is To Be Switched (together with information on the N3 addressing to use and on the transferred QoS flows) or an indication that the PDU Session is to be Rejected (together with a rejection cause). If the AMF, based on configuration, as described in clause 5.43.4 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], is aware that satellite backhaul category has changed due to the handover and needs to be updated to the SMF, the AMF includes the new satellite backhaul category and indicates the satellite backhaul category change as described in clause 5.43.4 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If the AMF, based on configuration, as described in clause 5.43.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], is aware that the UE is accessing over a gNB using GEO satellite backhaul and GEO Satellite ID needs to be updated to the SMF, the AMF may include the latest GEO Satellite ID as described in clause 5.43.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. For a PDU Sessions to be switched to the Target NG-RAN, upon receipt of the Nsmf_PDUSession_UpdateSMContext request, the SMF determines whether the existing UPF can continue to serve the UE. If the existing UPF cannot continue to serve the UE, steps 3-11 of clause 4.9.1.2.3 or 4.9.1.2.4 are performed depending on whether the existing UPF is a PDU Session Anchor. Otherwise, the following steps 3 to 6 are performed if the existing UPFs can continue to serve the PDU Session. In the case that the AMF determines that the PDU Session is related to a LADN, then the AMF provides the "UE presence in LADN service area" to the SMF. If the AMF does not provide the "UE presence in LADN service area" indication and the SMF determines that the DNN corresponds to a LADN, then the SMF considers that the UE is OUT of the LADN service area. The SMF takes actions for the LADN PDU Session as defined in clause 5.6.5 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] based on the "UE presence in LADN service area" indication. If a PDU Session is rejected by the Target NG-RAN with an indication that the PDU session was rejected because User Plane Security Enforcement is not supported in the Target NG-RAN and the User Plane Enforcement Policy indicates "Required" as described in clause 5.10.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], the SMF triggers the release of this PDU Session. In all other cases of PDU Session rejection, the SMF can decide whether to release the PDU Session or to deactivate the UP connection of this PDU Session. If some of the QoS Flows of a PDU Session are not accepted by the Target NG-RAN, the SMF shall initiate the PDU Session Modification procedure to remove the non-accepted QoS Flows from the PDU Session(s) after the handover procedure is completed. For the PDU Session(s) that do not have active N3 UP connections before handover procedure, the SMF(s) keep the inactive status after handover procedure. If the UE moves into a non-Allowed Area, the AMF also notifies via Namf_EventExposure_Notify to each NF Consumer (e.g. SMFs of the established PDU Sessions) which has subscribed for UE reachability event, that the UE is only reachable for regulatory prioritized services. The SMF then deactivates the PDU session if this PDU Session is not for emergency service. 3. SMF to UPF: N4 Session Modification Request (AN Tunnel Info) For PDU Sessions that are modified by the Target NG-RAN, the SMF sends an N4 Session Modification Request message to the UPF. The SMF may notify the UPF that originated the Data Notification to discard downlink data for the PDU Sessions and/or to not provide further Data Notification messages. Depending on the network deployment, the CN Tunnel Info of UPF used for connection to Target NG-RAN and connection to Source NG-RAN may be different, e.g. due to Source and Target NG-RAN are in different IP domains. In this case the SMF may ask the UPF to allocate new CN Tunnel Info, providing the target Network Instance. 4. UPF to SMF: N4 Session Modification Response (CN Tunnel Info) For the PDU Sessions that are switched, the UPF returns an N4 Session Modification Response message to the SMF after requested PDU Sessions are switched. Tunnel identifiers for UL traffic are included only for PDU Sessions whose user plane resources are not being released and was requested by the SMF. If redundant transmission is performed for one or more QoS Flows of a PDU Session and different CN Tunnel Info were requested by the SMF, the UPF allocates two different CN Tunnel Info and indicates the SMF that one CN Tunnel Info is used as the redundancy tunnel of the PDU session as described in clause 5.33.2.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. For the PDU Sessions that are deactivated, the UPF returns an N4 Session Modification Response message to the SMF after the N3 (R)AN tunnel information is released. 5. In order to assist the reordering function in the Target NG-RAN, the UPF (as specified in clause 5.8.2.9 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]) sends one or more "end marker" packets for each N3 tunnel on the old path immediately after switching the path. The UPF starts sending downlink packets to the Target NG-RAN. 6. SMF to AMF: Nsmf_PDUSession_UpdateSMContext Response (N2 SM information) The SMF sends an Nsmf_PDUSession_UpdateSMContext response (N2 SM Information (CN Tunnel Info, updated CN PDB for the accepted QoS Flows, Updated TSCAIs for the accepted QoS Flows)) to the AMF for PDU Sessions which have been switched successfully. The CN Tunnel Info of UPF send to AMF is used to setup N3 tunnel. If redundant transmission is performed for one or more QoS Flows of a PDU Session, two CN Tunnel Info are sent and the SMF indicates to the Target NG-RAN one of the CN Tunnel Info is used as the redundancy tunnel of the PDU Session as described in clause 5.33.2.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The SMF sends an Nsmf_PDUSession_UpdateSMContext response without including the CN Tunnel Info to the AMF for the PDU Sessions for which user plane resources are deactivated or released and then the SMF releases the PDU Session(s) which is to be released using a separate procedure as defined in clause 4.3.4. For each accepted GBR QoS Flow of Delay-critical resource type, the dynamic CN PDB and TSCAI may be updated and sent to the Target NG-RAN by the SMF. The SMF may update the CN PDB and TSCAI in the response or using a separate PDU Session Modification procedure, based on local configuration. If the Source NG-RAN does not support Alternative QoS Profiles (see TS 23.501[ System architecture for the 5G System (5GS) ] [2]) and the Target NG-RAN supports them, the SMF sends the Alternative QoS Profiles (see TS 23.501[ System architecture for the 5G System (5GS) ] [2]) to the Target NG-RAN on a per QoS Flow basis, if available. NOTE: Step 6 can occur any time after receipt of N4 Session Modification Response at the SMF. 7. AMF to NG-RAN: N2 Path Switch Request Ack (N2 SM Information, Failed PDU Sessions, UE Radio Capability ID). Once the Nsmf_PDUSession_UpdateSMContext response is received from all the SMFs, the AMF aggregates received CN Tunnel Info and sends this aggregated information as a part of N2 SM Information along with the Failed PDU Sessions in N2 Path Switch Request Ack to the Target NG-RAN. If none of the requested PDU Sessions have been switched successfully, the AMF shall send an N2 Path Switch Request Failure message to the Target NG-RAN. If the UE Radio Capability ID is included in the N2 Path Switch Request Ack message, when there is no corresponding UE radio capabilities set for UE Radio Capability ID at the Target NR-RAN, the Target NG-RAN shall request the AMF to provide the UE radio capabilities set corresponding to UE Radio Capability ID to the Target NG-RAN. 8. By sending a Release Resources message to the Source NG-RAN, the Target NG-RAN confirms success of the handover. It then triggers the release of resources with the Source NG-RAN. 9. [Conditional] The UE may initiate Mobility Registration Update procedure if one of the triggers of registration procedure applies as described in clause 4.2.2.2.2. In this case, only steps 1, 2, 3, 17 and 21 in clause 4.2.2.2.2 are performed. For the mobility related events as described in clause 4.15.4, the AMF invokes the Namf_EventExposure_Notify service operation. Upon reception of the Namf_EventExposure_Notify with an indication that UE is reachable only for regulatory prioritized service, the SMF deactivates the PDU Session if the service of the PDU Session is not regulatory prioritized. For home routed roaming case, the V-SMF triggers the deactivation of the PDU Session, in addition, the H-SMF refrains from sending downlink signalling if the signalling is not related to regulatory prioritized service upon receiving the notification. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.9.1.2.2 |
6,179 | 4.16.2.2 AM Policy Association Modification initiated by the PCF | The AM Policy Association modification procedure may be initiated by an internal PCF event or by PCF obtaining pertinent analytics information from an NWDAF. The following procedure is applicable to AM Policy Association modification due to Case B. Figure 4.16.2.2-1: AM Policy Association Modification initiated by the PCF The procedure driven by a PCF internal event applies to both roaming and non-roaming scenarios and when driven by NWDAF or CHF, applies only to non-roaming scenarios. An AM Policy Association is established, with the V-PCF in case of roaming or with the PCF in a non-roaming case as described in clause 4.16.1.2 before this procedure is triggered. In the non-roaming case the role of the V-PCF is performed by the PCF. For the roaming scenarios, the V-PCF interacts with the AMF. NOTE: The V-PCF/PCF stores the access and mobility related policy information provided to the AMF. 1. [Conditional] The PCF determines internally that the new status of the UE context requires new policies, potentially triggered by an AF as described in clause 4.15.6.9 or by a notification from the UDR or optionally, the CHF provides a Spending Limit Report to the PCF as described in clause 4.16.8. This may be triggered by obtaining pertinent analytics information from an NWDAF as described in clause 6.1.1.3 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. 2. The (V-)PCF in case of roaming and PCF in a non-roaming case makes a policy decision. The PCF may also decide to subscribe to a new Analytics ID from NWDAF as described in clause 6.1.1.3 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. 3. The (V-)PCF in the roaming case and the PCF in a non-roaming case sends Npcf_AMPolicyControl_UpdateNotify including AM Policy Association ID associated with the SUPI defined in TS 29.507[ 5G System; Access and Mobility Policy Control Service; Stage 3 ] [32]. The policy update may include Service Area Restrictions, UE-AMBR, RFSP index value and RFSP in Use Validity Time, access stratum time distribution indication, Uu time synchronization error budget, clock quality detail level and optionally clock quality acceptance criteria. If an AF has previously subscribed to event request for allocation of service area coverage outcome in step 1, the (V-)PCF checks if the allocated service area coverage was changed and sends a respective notification to the AF using Npcf_AMPolicyAuthorization_Notify as defined in clause 6.1.3.18 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. 4. The AMF deploys and stores the updated access and mobility related policy information, which includes storing the Service Area Restrictions and Policy Control Request Trigger of AM Policy Association, provisioning of the Service Area Restrictions to the UE, provisioning the RFSP index, UE-AMBR, Service Area Restrictions to the NG-RAN, optionally the access stratum time distribution indication, Uu time synchronization error budget, clock quality detail level and optionally clock quality acceptance criteria to the NG-RAN and request for notification of SM Policy association establishment and termination to a list of (DNN, S-NSSAI)(s) together with PCF for the UE binding information. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.16.2.2 |
6,180 | Create Indirect Data Forwarding Tunnel Response | A Create Indirect Data Forwarding Tunnel Response message shall be sent by the SGW to the MME/SGSN as a response to a Create Indirect Data Forwarding Tunnel Request message. Table -1 specifies the presence requirements and the conditions of the IEs in the message. The Cause value indicates if the Indirect Data Forwarding Tunnels has been created in the SGW or not. No Indirect Data Forwarding Tunnels have been created in the SGW if the Cause differs from "Request accepted" or "Request accepted partially". Possible Cause values are specified in Table 8.4-1. Message specific cause values are: - "Request accepted". - "Request accepted partially". - "Data forwarding not supported". - "Context not found". Table -1: Information Elements in a Create Indirect Data Forwarding Tunnel Response Table -2: Bearer Context within Create Indirect Data Forwarding Tunnel Response | 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 | Create |
6,181 | 4.4.6.3 Scheduled IP Throughput in DL | a) This measurement provides the volume of a data burst during IP throughput measurement, excluding the data transmitted in the TTI when the buffer is emptied in downlink. For an eNodeB serving one or more RNs, packets transmitted between the E-UTRAN and RNs are excluded, i.e., only packets transmitted between the eNodeB (or RN) and UEs are counted. The measurement is also applicable to RN. b) DER(n=1) c) This measurement is obtained according to the definition in 3GPP TS 36.314[ Evolved Universal Terrestrial Radio Access (E-UTRA); Layer 2 - Measurements ] [11] clause 4.1.6 as sum of ThpVolDl. Separate counters are maintained for each QCI. d) Each measurement is a real value representing volume of a data burst in kbit. The number of measurements is equal to the number of QCIs. e) The measurement name has the form DRB.IPVolDl.QCI where QCI identifies the E-RAB level quality of service class. f) EUtranCellFDD EUtranCellTDD g) Valid for packet switched traffic h) EPS i) This measurement is to support the Integrity KPI "E-UTRAN IP Throughput" defined in [13]. | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.4.6.3 |
6,182 | 14.4.2.2 Nnssaaf_AIW_Authenticate service operation | Service operation name: Nnssaaf_AIW_Authenticate Description: The NSSAAF provides Authentication and Authorization service to the consumer NF by relaying EAP or EAP-TTLS inner method messages towards a AAA Server and performing related protocol conversion as needed. Input, Required: 1) In EAP Authentication: a) In the initial authentication request: SUPI. b) In subsequent authentication requests: EAP message. 2) In case EAP-TTLS mechanisms are implemented: inner method container. Input, Optional: None Output, Required: 1) In EAP authentication: EAP message, authentication result and if success MSK and SUPI. 2) In case EAP-TTLS mechanisms are implemented: inner method container. Output, Optional: None | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 14.4.2.2 |
6,183 | 17.2 Cross-Link Interference Management | When different TDD DL/UL patterns are used between neighbouring cells, UL transmission in one cell may interfere with DL reception in another cell: this is referred to as Cross Link Interference (CLI). To mitigate CLI, gNBs can exchange and coordinate their intended TDD DL-UL configurations over Xn and F1 interfaces; and the victim UEs can be configured to perform CLI measurements. There are two types of CLI measurements: - SRS-RSRP measurement in which the UE measures SRS-RSRP over SRS resources of aggressor UE(s); - CLI-RSSI measurement in which the UE measures the total received power observed over RSSI resources. Layer 3 filtering applies to CLI measurement results and both event triggered and periodic reporting are supported. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 17.2 |
6,184 | 5.26.1 Architecture Principles for Configuration Transfer | Configuration Transfer between two RAN node provides a generic mechanism for the exchange of information between applications belonging to the RAN nodes. In order to make the information transparent for the Core Network, the information is included in a transparent container that includes source and target RAN node addresses, which allows the Core Network nodes to route the messages. The mechanism is depicted in figure 5.26 1. Figure 5.26-1: inter NG-RAN Configuration Transfer basic network architecture The NG-RAN transparent containers are transferred from the source NG-RAN node to the destination NG-RAN node by use of Configuration Transfer messages. A Configuration Transfer message is used from the NG-RAN node to the AMF over N2 interface, a AMF Configuration Transfer message is used from the AMF to the NG-RAN over N2 interface, and a Configuration Transfer Tunnel message is used to tunnel the transparent container from a source AMF to a target AMF over the N14 interface. Each Configuration Transfer message carrying the transparent container is routed and relayed independently by the core network node(s). | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.26.1 |
6,185 | 4.9.2.4.1 The selected N3IWF is in the registered PLMN | Figure 4.9.2.4.1-1: Handover of a PDU Session procedure from 3GPP access to untrusted non-3GPP access (home routed roaming) 1. If the UE is not registered via untrusted non-3GPP access, the UE shall initiate Registration procedure as defined in clause 4.12.2. The N3IWF selects the same AMF as the one used via 3GPP access. 2. The UE performs PDU Session Establishment procedure with the PDU Session ID of the PDU Session to be moved as specified in clause 4.12.5. The AMF selects the same V-SMF as the one used via 3GPP access. In the Nsmf_PDUSession_Update Response the H-SMF shall include all QoS information for the QoS Flow(s) applicable to the PDU Session for the target access so that when sending the PDU Session Establishment Accept, within the N1 SM container and in the N2 SM information, the V-SMF can include all QoS information (e.g. QoS Rule(s) in N1 SM container, QFI(s) and QoS Profile(s) in N2 SM information) for the QoS Flow(s) acceptable according to VPLMN policies. 3. If the User Plane of the PDU Session is activated in 3GPP access, the V-SMF executes the release of resources in 3GPP access by performing step 5c to 10 specified in clause 4.3.4.3 (UE or network requested PDU Session Release for Home Routed Roaming) in order to release the resources over the source 3GPP access. Because the PDU Session shall not be released, the SMF shall not send the PDU Session Release Command to the UE. Hence, in steps 5c, 6, 8 and 9 of clause 4.3.4.3, the messages do not include the N1 SM container but only the N2 Resource Release Request (resp. Ack). Since the PDU Session is not to be released, the SMF shall not execute step 11 of clause 4.3.4.2 and the SM context between the AMF and the SMF is maintained. If the User Plane of the PDU Session is deactivated in 3GPP access, this step is skipped. The steps 2 and 3 shall be repeated for all PDU Sessions to be moved from 3GPP access to untrusted non-3GPP access. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.9.2.4.1 |
6,186 | 5.8.2.13 Support for 5G VN group communication 5.8.2.13.0 General | The SMF may configure the UPF(s) to apply different traffic forwarding methods to route traffic between PDU Sessions for a single 5G VN group. For example, depending on the destination address, some packet flows may be forwarded locally, while other packet flows are forwarded via N19 and other packet flows are forwarded to N6. If a single SMF serves the DNN/S-NSSAI of the 5G VN group, the UPF local switching, N6-based forwarding and N19-based forwarding methods described in clause 5.29.4 are coordinated by the SMF. If an SMF set serves the DNN/S-NSSAI of the 5G VN group, implementation based mechanisms can be used between SMF(s) that are part of the SMF set for controlling the connectivity between the PSA UPFs of the UE members of the 5G VN group. When a 5G VN group communication is extended in a wide area, bigger than the service area of any SMF set serving the DNN/S-NSSAI of the 5G VN group, multiple SMF sets might control the PDU Sessions of the UE members of the 5G VN group. In this case, N6/N19 connectivity between PSA UPFs of the UE members of the 5G VN group controlled by different SMF sets, is achieved via OAM configuration. As a deployment option, a subset of the UPFs controlled by an SMF Set may be configured with the N6/N19 connectivity to enable 5G VN group communication across SMF Sets. N6 connectivity between PSA UPFs via a DN may also exist. 5G VN group communication includes one to one communication and one to many communication. One to one communication supports forwarding of unicast traffic between two UEs within a 5G VN, or between a UE and a device on the DN. One to many communication supports forwarding of multicast traffic and broadcast traffic from one UE (or device on the DN) to many/all UEs within a 5G VN and devices on the DN. Traffic forwarding within the 5G VN group is realized by using a UPF internal interface ("5G VN internal") and a two-step detection and forwarding process. In the first step, the packets received from any 5G VN group member (via it's PDU Session, via N6 or via N19) are forwarded to the UPF internal interface (i.e. Destination Interface set to "5G VN internal"). In the second step, PDRs installed at the UPF internal interface (i.e. Source Interface set to "5G VN internal") detect the packet and forward it to the respective 5G VN group member (via it's PDU Session, via N6 or via N19). The details of the PDR and FAR configuration are described in the following clauses. For UEs belonging to the same 5G VN group and having PDU Sessions that correspond to N4 Sessions in the same PSA UPF, the following applies for traffic that is sent from one of these UEs to another one of these UEs using local switching: The incoming traffic for one PDU Session will match the corresponding N4 Session's PDR(s) of the source PDU Session (based on GTP-U header information). The traffic is then sent back to classification in that UPF (via the internal interface) and will match another N4 Session corresponding to the destination PDU Session (based on destination address in the PDU). The PDU is then forwarded to the target UE. If 5G VN group members' PDU Sessions are served by different PSA UPFs and N19-based forwarding is applied, the SMF creates a group-level N4 Session with each involved UPF to enable N19-based forwarding and N6-based forwarding. When the traffic is then sent back to classification in that UPF (via the internal interface) it may match group-level N4 Session corresponding to the 5G VN group (based on destination address in the PDU or a default PDR rule with match-all packet filter). The PDU is then forwarded to N6 or to the UPF indicated in the group-level N4 Session via corresponding N19 tunnel. This enables the PDU to be sent to the target group member in the other UPF or to the device in the DN. In the case of N19-based forwarding is not applied for a 5G VN group, group level N4 session is not required. If more than one 5G VN group has to be supported in the PLMN, the N4 rule attribute Network Instance is used in addition to the UPF internal interface and set to a value representing the 5G VN group. This keeps the traffic of different 5G VN groups separate from each other and thus enables isolation of the 5G VN group communication during the packet detection and forwarding process. The SMF shall provide the PDRs and FARs related to the UPF internal interface as follows whenever more than one 5G VN group has to be supported in the PLMN: - The FAR with Destination Interface set to "5G VN internal" shall also contain the Network Instance set to the value representing the 5G VN group. - The PDR with Source Interface set to "5G VN internal" shall also contain the Network Instance set to the value representing the 5G VN group. Forwarding Ethernet unicast traffic towards the PDU Session corresponding to the Destination MAC address of an Ethernet frame may correspond: - either to the SMF explicitly configuring DL PDR(s) with the MAC addresses detected by the UPF on PDU Sessions and reported to the SMF; this is further described in clause 5.8.2.13.1; - or to the SMF relying on MAC address learning in UPF as defined in clause 5.8.2.5.3. To request this UPF behaviour the SMF sets the Ethernet PDU Session Information indication in the DL PDR of the "5G VN internal" interface related with a 5G VN group. This may apply in the case that all PDU Sessions related with this 5G VN group are served by the same PSA or by multiple PSAs not inter-connected via N19. For Ethernet traffic on 5G-VN, in the former case above where SMF explicitly configures DL PDR with the MAC addresses detected on PDU Sessions supporting a 5G VN group, the SMF acts as a central controller which is responsible for setting up the forwarding rules in the UPFs so that it avoids forwarding loops. The SMF becomes aware of the MAC addresses in use within a 5G VN group by the UPF's reporting of the MAC addresses. The SMF is responsible to react to topology changes in the Ethernet network. Local switching without SMF involvement is not specified for a 5G-VN when different PDU Sessions related with this 5G VN group may be served by different PSA(s) connected over N19. NOTE: The mechanisms described above implies signalling on N4 Sessions related with a VN group each time a new MAC address is detected as used (or no more used) within a PDU Session related with this 5G VN group. Hence the usage of the solution with SMF explicitly configuring DL PDR with the MAC addresses defined in this release can raise signalling scalability issues for large VN groups with lots of devices (MAC addresses) served by PDU sessions related with this VN group. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.8.2.13 |
6,187 | 9.11.3.2A 5GS DRX parameters | The purpose of the 5GS DRX parameters information element is to indicate that the UE wants to use DRX and for the network to indicate the DRX cycle value to be used at paging. The 5GS DRX parameters is a type 4 information element with a length of 3 octets. The 5GS DRX parameters information element is coded as shown in figure 9.11.3.2A.1 and table 9.11.3.2A.1. The value part of a DRX parameter information element is coded as shown in table 9.11.3.2A.1. Figure 9.11.3.2A.1: 5GS DRX parameters information element Table 9.11.3.2A.1: 5GS DRX parameters information element | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.11.3.2A |
6,188 | Annex X (normative): Security aspects of enablers for Network Automation (eNA) for the 5G system (5GS) X.1 General | This Annex provides security requirements and procedures for the Network Automation features. The feature for enablers for Network Automation by 5GS is described in 3GPP TS23.501[2] and 3GPP TS23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [105]. X.2 Authorization of NF Service Consumers for data access via DCCF The detailed procedure for NF Service Consumer to receive data from Service Producers via DCCF is depicted in Figure X.2-1: Figure X.2-1: NF Service Consumer Authorization to receive data from NF Service Producers via DCCF 1-3. NF Service Consumer shall send a request to the NRF to receive an access token to request services of DCCF, to be used for data collection request. NRF after verifying shall generate access token and sends it to the NF Service Consumer. 4. The NF Service Consumer initiates a NF service request to the DCCF which includes the access_token_nwdaf. The NF Service Consumer shall also generate a Client Credentials Assertion (CCA) token (CCA_NWDAF) as described in the clause 13.3.8 and includes it in the request message in order to authenticate itself towards the NF Service Producers. NOTE 0: The procedure of NF Service Consumer (e.g. NWDAF) requesting the services provided by NF Service Producer via DCCF is defined in Clause 6.2.6.3 of TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [105]. 5. The DCCF shall verify if the access_token_nwdaf is valid and executes the service. If the NRF does not support authorization of the source NF (e.g. NWDAF) for data access via the DCCF (e.g. if the NRF is Rel-16), the DCCF authorizes the data access of the NF Service Consumer. 6. The DCCF determines the NF Service Producer(s) from where the data is to be collected (as specified in Clause 6.2.6.3.2 in TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [105]). NOTE 1: If the NF Service Consumer sends the NF Service Producer information (i.e. NF Service Producer type and Instance ID) along with the service request in Step 4, then DCCF does not determine the NF Service Producer, but requests an access token from the NRF using the NF Service Producer details sent by the NF Service Consumer (as described in Step 7). 7. The DCCF sends a Nnrf_AccessToken_Get request to NRF including the information to identify the target NF (NF Service Producer), the source NF (NF Service Consumer e.g. NWDAF), the NF Instance ID of DCCF and the CCA_NWDAF provided by the NF Service Consumer. The nfInstanceId IE attribute in the access token request (Nnrf_AccessToken_Get) indicates the NF instance ID of the DCCF as intermediate NF Service Consumer, whereas the sourceNfInstanceId IE attribute indicates the source NF instance ID (NF Service Consumer e.g., NWDAF). NOTE 1a: Void 8. The NRF shall check whether the DCCF and the NF Service Consumer (e.g. NWDAF) are allowed to access the service provided by the identified NF Service Producers, and the DCCF as the proxy is allowed to request the service from the identified NF Service Producers on behalf the NF Service Consumer. NRF authenticates both DCCF and NWDAF based on one of the SBA methods described in clause 13.3.1.2. NOTE 2: A Rel-16 NRF only authenticates and authorizes the DCCF, i.e., after the NRF receives Nnrf_AccessToken_Get request, the NRF validates whether the intermediate NF Service Consumer (e.g., DCCF) is authorized to receive the requested service from the NF Service Producer. The NRF from Rel-16 or earlier does not validate whether the source NF Service Consumer (e.g., NWDAF) is authorized to receive the requested service. NOTE 3: Void 9. The NRF after successful verification then generates and provides an access token to the DCCF as described in the clause 13.4.1.1.2, with NF Instance ID of the DCCF (subject), and an additional access token claim containing the identity ofthe source NF Service Consumer, in order to authorize both DCCF and NF Service Consumer (e.g.. NWDAF) to consume the services of NF Service Producer. NOTE 4: In the case the NRF is from Rel-16 or earlier, the NRF generates an OAuth2.0 access token with “subject” claim mapped to the intermediate NF Service Consumer, i.e., in this case DCCF, and no additional claim for the source NF Service Consumer (e.g., NWDAF) identity is added. 10. The DCCF requests service from the NF Service Producer. The request also contains the content of the CCA_NWDAF, so that the NF Service Producer(s) authenticates the NF Service Consumer (e.g. NWDAF) , i.e.,the NF Service Producer shall check the subject claim of CCA_NWDAF with the access token claim conveying the source NF Instance ID, when this claim is present in the access token. Editor's note: The additional information about the NF Service Consumer (source NF, e.g., NWDAF) conveyed in the CCCCCA_NWDAF, and the way to be conveyed (e.g., in a new header) is to be specified in stage 3 (TS 29.510[ 5G System; Network function repository services; Stage 3 ] ). 11. The NF Service Producer(s) authenticates the NF Service Consumer and ensures that the source NF Service Consumer identity is included as an access token additional claim. The NF Service Producer authenticates and authorizes the DCCF following clauses 13.3.2 and 13.4.1. After authentication and authorization is successful, the NF Service Producer(s) executes the service. NOTE 5: Rel-16 NF Service Producer only authenticates and authorizes the DCCF. 12. The NF Service Producer(s) shall provide requested data to the DCCF. 13. The DCCF forwards the received data to the NF Service Consumer(s). NOTE 6: In the case a new NF Service Consumer comes at a later stage to request the data, which is already being collected by DCCF, steps 1-10 apply. When the request is received by the NF Service Producer (i.e. the data producer), it authenticates the NF Service Consumer and verifies the access token provided along with the service request and sends to DCCF the access token verification response. DCCF based upon the response received, either updates the subscription info to include the new NF Service Consumer as well and sends the data to both the consumers (as specified in Clause 6.2.6.3.2 in TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [105]), or in the case of access token verification failure, the DCCF rejects the request received by the NF Service Consumer. NOTE 7: Void X.3 Authorization of NF Service Consumers for data access via DCCF when notification sent via MFAF The detailed procedure for NF Service Consumer to receive data from Service Producers via DCCF when notification is sent via MFAF is depicted in Figure X.3-1: Figure X.3-1: Service Consumer Authorization to receive data from Service Producers via MFAF Steps 1-9 are same as Steps 1 – 9 of Annex X.2. 10-11. The DCCF sends an access token request to the NRF to request service from MFAF. NRF after verifying sends access_token_dccf to DCCF to consume the services of MFAF. 12. DCCF shall then send the Nmfaf_3daDataManagement_Configure request to MFAF (as specified in the Clause 6.2.6.3.2 in TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [105]) along with the access_token_dccf. Steps 13 – 14 are same as Steps 10 – 11 of Annex X.2 15. The NF Service Producer(s) shall provide requested data to the MFAF. 16. The MFAF forwards the received data to the data consumer(s). NOTE 1: In the case a new data consumer comes at a later stage to request the data, which is already being collected by DCCF, steps 1-9 and 13 apply. When the request is received by the NF Service Producer (i.e. the data producer), it authenticates the NF Service Consumer and verifies the access token provided along with the service request and sends to DCCF the access token verification response. DCCF based upon the response received, either updates the subscription info at the MFAF to include the new data consumer as well and MFAF sends the data to both the consumers (as specified in Clause 6.2.6.3.2 in TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [105]), or in the case of access token verification failure, the DCCF rejects the request received by the data consumer and does not update the subscription at the MFAF. NOTE 2: Void X.4 Security protection of data via messaging framework The transfer of the data between the data source and data consumer via the messaging framework shall be confidentiality, integrity, and replay protected. Confidentiality protection, integrity protection, and replay-protection shall be supported on the new interfaces between 3GPP entities and MFAF by reusing the existing security mechanism defined for SBA in Clause 13. X.5 Protection of data transferred between AF and NWDAF As specified in TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [105], the NWDAF may interact with an AF to collect data from UE Application(s) as an input for analytics generation. The AF can be in the MNO domain or an AF external to MNO domain. To enhance the 5GS to support collection and utilisation of UE related data for providing the inputs to generate analytics information (to be consumed by other NFs), the communication between AF and NWDAF needs to be secured. The NWDAF interacts with the 5GC NFs and the AF using Service-based Interfaces. The existing 5G security mechanism can be reused for the transfer of UE data over the SBA interface between AF and NWDAF. When the AF is located in the operator’s network, the NWDAF uses Service-Based Interface as depicted in clause 13 to communicate with the AF directly. When the AF is located outside the operator’s network, the NEF is used to exchange the messages between the AF and the NWDAF. The security aspects of NEF is specified in clause 12. X.6 Protection of UE data in transit between NFs According to clause 13.1.0, all network functions shall support mutually authenticated TLS and HTTPS. TLS shall be used for transport protection within a PLMN unless network security is provided by other means. Thus, communication between NFs is integrity, confidentiality and replay protected. NFs shall obtain an access token from NRF for requesting analytics from an analytics function or providing analytics data to the analytics function. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | Annex |
6,189 | 8.10.1.2.14 HST-SFN performance | 8.10.1.2.14.1 Minimum Requirement for Rel-16 further enhanced HST The requirements are specified in Table 8.10.1.2.14-2, with the addition of the parameters in Table 8.10.1.2.14-1 and the downlink physical channel setup according to Annex C.3.2. The purpose of this test is to verify UE performance in the HST-SFN-500 scenario. The test for HST-SFN-500 scenario defined in B.3B is applied when highSpeedEnhDemodFlag2-r16 [7] is received. Table 8.10.1.2.14-1: Void Table 8.10.1.2.14-2: Void NOTE: Table 8.10.1.2.14-1 and Table 8.10.1.2.14-2 are moved to subclause 8.10.1.2.14.1 as Table 8.10.1.2.14.1-1 and Table 8.10.1.2.14.1-2. Table 8.10.1.2.14.1-1: Test Parameters for UE performance in HST-SFN-500 scenario (FRC) Table 8.10.1.2.14.1-2: Minimum performance UE in HST-SFN-500 scenario (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.10.1.2.14 |
6,190 | 6.3.7.1 PCF discovery and selection for a UE or a PDU Session | PCF discovery and selection functionality is implemented in AMF, SMF, SCP and PCF and follows the principles in clause 6.3.1. The AMF uses the PCF services for a UE and the SMF uses the PCF services for a PDU Session. PCF for a PDU Session uses the PCF services for a UE. When the NF service consumer performs discovery and selection for a UE, the following applies: - The AMF may utilize the NRF to discover the candidate PCF instance(s) for a UE. In addition, PCF information may also be locally configured in the AMF. The AMF selects a PCF instance based on the available PCF instances obtained from the NRF or locally configured information in the AMF, depending on operator's policies. In the non roaming case, the AMF selects a PCF instance for AM policy association and selects the same PCF instance for UE policy association. In the roaming case, the AMF selects a V-PCF instance for AM policy association and selects the same V-PCF instance for UE policy association. The PCF for a PDU Session selects a (V-)PCF instance for UE policy association. The following factors may be considered at PCF discovery and selection for Access and Mobility policies and UE policies: - SUPI; the AMF selects a PCF instance based on the SUPI range the UE's SUPI belongs to or based on the results of a discovery procedure with NRF using the UE's SUPI as input for PCF discovery. - S-NSSAI(s). In the roaming case, the AMF selects the V-PCF instance based on the S-NSSAI(s) of the VPLMN and selects the H-PCF instance based on the S-NSSAI(s) of the HPLMN. - PCF Set ID. - PCF Group ID of the UE's SUPI. NOTE 1: The AMF can infer the PCF Group ID the UE's SUPI belongs to, based on the results of PCF discovery procedures with NRF. The AMF provides the PCF Group ID the SUPI belongs to to other PCF NF consumers as described in TS 23.502[ Procedures for the 5G System (5GS) ] [3]. - DNN replacement capability of the PCF. - Slice replacement capability of the PCF. - PCF Selection Assistance Info and PCF ID(s) serving the established PDU Sessions/PDN Connections received from UDM. In case PCF Selection Assistance Info and PCF ID(s) are received from the UDM, the AMF selects the same PCF instance serving the combination of DNN and S-NSSAI as indicated by the PCF Selection Assistance Info, if multiple DNN, S-NSSAI combinations are provided, the AMF selects the DNN,S-NSSAI using local configuration. In case PCF ID(s) are not received, e.g. EPS interworking is not supported, the AMF selects the PCF instance by considering other above factors. - URSP delivery in EPS capability of the PCF. When the NF service consumer performs discovery and selection for a PDU Session, the following applies: - The SMF may utilize the NRF to discover the candidate PCF instance(s) for a PDU Session. In addition, PCF information may also be locally configured in the SMF. The SMF selects a PCF instance based on the available PCF instances obtained from the NRF or locally configured information in the SMF, depending on operator's policies. The following factors may be considered at PCF discovery and selection for a PDU session: a) Local operator policies. b) Selected Data Network Name (DNN). c) S-NSSAI of the PDU Session. In the LBO roaming case, the SMF selects the PCF instance based on the S-NSSAI of the VPLMN. In the home routed roaming case, the H-SMF selects the H-PCF instance based on the S-NSSAI of the HPLMN. d) SUPI; the SMF selects a PCF instance based on the SUPI range the UE's SUPI belongs to or based on the results of a discovery procedure with NRF using the UE's SUPI as input for PCF discovery. e) PCF selected by the AMF for the UE. f) MA PDU Session capability of the PCF, for an MA PDU session. g) The PCF Group ID provided by the AMF to the SMF. h) PCF Set ID. i) Same PCF Selection Indication. j) URSP delivery in EPS capability of the PCF. In the case of delegated discovery and selection in SCP, the SMF includes the factors b) - h), j), if available, in the first request. The selected PCF instance for serving the UE and the selected PCF instance for serving a PDU session of this UE may be the same or may be different. In the following scenarios, information about the PCF instance that has been selected (i.e. the PCF ID, PCF Set Id and, if PCF Set Id is not available, the PCF Group ID (if available)) may be forwarded to another NF. If the NF service consumer performs discovery and selection, this NF may use this PCF instance. If the NF service consumer performs delegated discovery and selection, this NF may include PCF ID, PCF Set Id and, if PCF Set Id is not available, the PCF Group ID (if available) in the request and the SCP may use this information to select the PCF instance (discovery may still be needed depending on what level of information is sent by the AMF, e.g. the address of the PCF instance may not be present): When NF service consumer performs discovery and selection, the following applies: - During AMF relocation, the target AMF may receive a PCF ID, PCF Set Id and, if PCF Set Id is not available, the PCF Group ID (if available) from the source AMF to enable the usage of the same PCF by the target AMF, and the target AMF may decide based on operator policy either to use the same PCF or select a new PCF. - The AMF may, based on operator policies, forward the selected PCF to SMF instance(s) during the PDU Session Establishment procedure(s) to enable the usage of the same PCF for the AMF and the SMF instance(s). The SMF may decide based on operator policy either to use the same PCF or select a new PCF. If combination of the DNN and S-NSSAI of the PDU session matches one of the combination of the DNN and S-NSSAI included in the PCF Selection Assistance info received from UDM, the AMF shall forward Same PCF Selection Indication together with the selected PCF to SMF instance during the PDU Session Establishment procedure. In case that the Same PCF Selection Indication is received together with the PCF ID, the SMF shall select the same PCF instance for SM Policy Control. - In the roaming case, the AMF may, based on operator policies, e.g. roaming agreement, select the H-PCF in addition to the V-PCF for a UE by performing the PCF discovery and selection as described above. The AMF sends the H-PCF ID of the selected H-PCF instance to the V-PCF during the policy association establishment procedure. When the SMF receives a a redirection indication with PCF ID from the PCF for the PDU session, the SMF shall terminate the current SM Policy Control association and reselects a PCF based on the received PCF ID. The SMF shall then establish an SM Policy Control association with the reselected PCF. In the case of delegated discovery and selection in the SCP, the following applies: - The selected PCF instance may include the PCF Id, PCF Set Id and, if PCF Set Id is not available, the PCF Group ID (if available) in the response to the AMF. NOTE 2: The selected (V-)PCF instance can include the binding indication, including the (V-)PCF ID and possibly PCF Set ID in the response to the AMF as described in clause 6.3.1.0. - The AMF first establishes an AM policy association; when forwarding the related request message the SCP discovers and selects a PCF instance. Unless binding information is provided in the response to that request the SCP adds the NF function producer ID it selected, i.e. PCF ID, into the response and the AMF uses the received PCF ID and available binding information as discovery and selection parameters for the request to establish the UE policy association towards the SCP. The SCP selects the (V-)PCF instance for UE policy association based on the received discovery and selection parameters. - During AMF relocation, the AMF may receive a PCF ID, PCF Set Id and, if PCF Set Id is not available, the PCF Group ID (if available) from the source AMF to enable the usage of the same PCF instance by the AMF. The AMF may decide based on operator policy either to use the old PCF instance or select another PCF instance. If the AMF decides to use the old PCF, the AMF includes the PCF ID PCF Set Id, and if PCF Set Id is not available, the PCF Group ID (if available) as received from the source AMF in the AM policy update request to the SCP. - The AMF may, based on operator policies, forward the selected PCF ID, PCF Set Id and, if PCF Set Id is not available, the PCF Group ID (if available) to the SMF during the PDU Session Establishment procedure to enable the usage of the same PCF for the AMF and the SMF. The SMF may include that information in the request in discovery and selection parameters to the SCP. The SCP may decide based on operator policy either to use the indicated PCF instance or select another PCF instance. - In the roaming case, the AMF performs discovery and selection of the H-PCF from NRF as described in this clause. The AMF may indicate the maximum number of H-PCF instances to be returned from NRF, i.e. H-PCF selection at NRF. The AMF uses the received V-PCF ID and available binding information received during the AM policy association procedure to send the UE policy association establishment request, which also includes the H-PCF ID, to the SCP. The SCP discovers and selects the V-PCF. The V-PCF sends an UE policy association establishment request towards the HPLMN, which includes the H-PCF ID as a discovery and selection parameter to SCP. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 6.3.7.1 |
6,191 | 5.5.4.11 Event C1 (The NR sidelink channel busy ratio is above a threshold) | The UE shall: 1> consider the entering condition for this event to be satisfied when condition C1-1, as specified below, is fulfilled; 1> consider the leaving condition for this event to be satisfied when condition C1-2, as specified below, is fulfilled; Inequality C1-1 (Entering condition) Inequality C1-2 (Leaving condition) The variables in the formula are defined as follows: Ms is the measurement result of channel busy ratio of the transmission resource pool, not taking into account any offsets. Hys is the hysteresis parameter for this event (i.e. hysteresis as defined within reportConfigNR-SL for this event). Thresh is the threshold parameter for this event (i.e. c1-Threshold as defined within reportConfigNR-SL for this event). Ms is expressed in decimal from 0 to 1 in steps of 0.01. Hys is expressed is in the same unit as Ms. Thresh is expressed in the same unit as Ms. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.5.4.11 |
6,192 | 7.8 Messages with semantically incorrect contents | When a message with semantically incorrect contents is received, the UE shall perform the foreseen reactions of the procedural part of the present document (i.e. of clauses 5, 6). If, however no such reactions are specified, the UE shall ignore the message except that it shall return a status message (5GMM STATUS or 5GSM STATUS depending on the EPD) with cause #95 "semantically incorrect message". The network should follow the same procedure except that a status message is not normally transmitted. | 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.8 |
6,193 | 5.6.3 Transport of NAS messages procedure 5.6.3.1 General | The purpose of the transport of NAS messages procedure is to carry SMS messages in an encapsulated form between the MME and the UE. The procedure may be initiated by the UE or the network and can only be used when the UE is attached for EPS services and non-EPS services or for EPS services and "SMS only", and the UE is in EMM-CONNECTED mode. NOTE 1: If the UE is in EMM-IDLE mode and is using EPS services with control plane CIoT EPS optimization, the UE transports the first SMS message by encapsulating it in the NAS message container IE in the Control Plane Service Request message. NOTE 2: When the UE is using EPS services with control plane CIoT EPS optimization, the network can initiate downlink transport of NAS messages procedure even if the UE does not have any PDN connections established. | 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.6.3 |
6,194 | 10.5.4.4 Auxiliary states | The purpose of the auxiliary states information element is to describe the current status of the auxiliary states of a call in the call control states "active" and "mobile originating modify" (see 3GPP TS 24.083[ Call Waiting (CW) and Call Hold (HOLD) supplementary services; Stage 3 ] [27] and 3GPP TS 24.084[ Multi Party (MPTY) supplementary service; Stage 3 ] [28]). The auxiliary states information element is coded as shown in figure 10.5.87/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] , table 10.5.100/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.101/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The auxiliary states is a type 4 information element with 3 octets length. Figure 10.5.87/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Auxiliary states information element Table 10.5.100/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Auxiliary states information element Table 10.5.101/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Auxiliary states information element | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 10.5.4.4 |
6,195 | 23.2 OAM System Realm/Domain | The OAM System Realm/Domain shall be in the form of an Internet domain name, e.g. operator.com, as specified in IETF RFC 1035 [19] and IETF RFC 1123 [20]. The OAM System Realm/Domain consists of one or more labels. Each label shall consist of the alphabetic characters (A-Z and a-z), digits (0-9) and the hyphen (-) in accordance with IETF RFC 1035 [19]. Each label shall begin and end with either an alphabetic character or a digit in accordance with IETF RFC 1123 [20]. The case of alphabetic characters is not significant. The OAM System Realm/Domain shall be in the form of "oam.mnc<MNC>.mcc<MCC>.3gppnetwork.org", where "<MNC>" and "<MCC>" fields correspond to the MNC and MCC of the operator's PLMN. Both the "<MNC>" and "<MCC>" fields are 3 digits long. If the MNC of the PLMN is 2 digits, then a zero shall be added at the beginning. For example, the OAM System Realm/Domain of an IMSI shall be derived as described in the following steps: 1. take the first 5 or 6 digits, depending on whether a 2 or 3 digit MNC is used (see 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [27]) and separate them into MCC and MNC; if the MNC is 2 digits then a zero shall be added at the beginning; 2. use the MCC and MNC derived in step 1 to create the "mnc<MNC>.mcc<MCC>.3gppnetwork.org" domain name; 3. add the label "oam" to the beginning of the domain name. An example of an OAM System Realm/Domain is: IMSI in use: 234150999999999; Where: MCC = 234; MNC = 15; MSIN = 0999999999; Which gives the OAM System Realm/Domain name: oam.mnc015.mcc234.3gppnetwork.org. NOTE: If it is not possible for a Relay Node to identify whether a 2 or 3 digit MNC is used (e.g. USIM is inserted and the length of MNC in the IMSI is not available in the "Administrative data" data file), it is implementation dependent how the Relay Node determines the length of the MNC (2 or 3 digits). | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 23.2 |
6,196 | N.4 Enabling the UE access to Localized Services | The access to a Localized Service is made available in a specific area and/or a specific period of time. After the UE has successfully registered to a PNI-NPN/SNPN providing access to the Localized Service, the UE can be configured with URSP rules using existing principles (see clause 6.6.2.2 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]). The URSP rules can include an association between the UE application and the DNN/S-NSSAI which is meant for a particular Localized Service. The URSP rules can also include "Route Selection Validation Criteria" as described in Table 6.6.2.1-3 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45], with the time/location defined for the particular Localized Service. The existing LADN feature described in clause 5.6.5 can also be used for enabling the UE access to Localized Service which is defined by a LADN DNN. The S-NSSAI used for a Localized Service can be restricted to a specific area and time as described in clause 5.15. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | N.4 |
6,197 | 16.15.2 Awareness | XR-Awareness relies on QoS flows, PDU Sets, Data Bursts and traffic assistance information (see TS 23.501[ System architecture for the 5G System (5GS) ] [3]). The following PDU Set QoS Parameters may be provided by the SMF to the gNB as part of the QoS profile of the QoS flow, and to enable PDU Set based QoS handling at least one of them shall be provided: - PDU Set Delay Budget (PSDB): as defined in TS 23.501[ System architecture for the 5G System (5GS) ] [3], upper bound for the duration between the reception time of the first PDU (at the UPF for DL, at the UE for UL) and the time when all PDUs of a PDU Set have been successfully received (at the UE in DL, at the UPF in UL). A QoS Flow is associated with only one PSDB, and when available, it applies to both DL and UL and supersedes the PDB of the QoS flow. - PDU Set Error Rate (PSER): as defined in TS 23.501[ System architecture for the 5G System (5GS) ] [3], upper bound for a rate of non-congestion related PDU Set losses between RAN and the UE. A QoS Flow is associated with only one PSER, and when available, it applies to both DL and UL and supersedes the PER of the QoS flow. NOTE 1: In this release, a PDU set is considered as successfully delivered only when all PDUs of a PDU Set are delivered successfully. - PDU Set Integrated Handling Information (PSIHI): indicates whether all PDUs of the PDU Set are needed for the usage of PDU Set by application layer, as defined in TS 23.501[ System architecture for the 5G System (5GS) ] [3]. NOTE 2: The PDU Set QoS parameters are common for all PDU Sets within a QoS flow. During the Xn-handover preparation procedure, the source gNB sends the stored PDU Set QoS Parameters as part of the QoS profile to the target NG-RAN node. In addition, the UPF can identify PDUs that belong to PDU Sets, and may indicate to the gNB the following PDU Set Information in the GTP-U header: - PDU Set Sequence Number; - Indication of End PDU of the PDU Set; - PDU Sequence Number within a PDU Set; - PDU Set Size in bytes; - PDU Set Importance (PSI), which identifies the relative importance of a PDU Set compared to other PDU Sets within the same QoS Flow. 5GC may provide XR traffic assistance information to gNB through NG AP TSC Assistance Information (TSCAI) as specified in clause 5.37.8 of TS 23.501[ System architecture for the 5G System (5GS) ] [3] (for both GBR and non-GBR QoS flows): - UL and/or DL Periodicity; - N6 Jitter Information (i.e. between UPF and Data Network) associated with the DL Periodicity. This assistance information can be used by the gNB to configure DRX to enable better UE power saving. In addition, 5GC may provide the following information through NG-U as specified in clause 5.37.5.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [3]: - Indication of End of Data Burst in the GTP-U header of the last PDU in downlink. This information can be used by the gNB to push the UE back to sleep when possible. In the uplink, the UE needs to be able to identify PDU Sets and Data Bursts dynamically, including PSI. How this is done is left up to UE implementation but when possible for a QoS flow, this is indicated to the gNB via UE Assistance Information. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.15.2 |
6,198 | 5.4.5.4 Abnormal cases on the network side | The following abnormal case can be identified: a) Lower layers indication of non-delivered NAS PDU due to handover If the EMM INFORMATION message could not be delivered due to an intra MME handover and the target TA is included in the TAI list, then upon successful completion of the intra MME handover the MME shall retransmit the EMM INFORMATION message. If a failure of the handover procedure is reported by the lower layer and the S1 signalling connection exists, the MME shall retransmit the EMM INFORMATION 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 | 5.4.5.4 |
6,199 | 4.6.2.11 Mobility management for partial network slice | A serving PLMN or SNPN can indicate the S-NSSAI(s) is allowed or rejected in some TA(s) but not all TAs of the registration area to the UE during the registration procedure as specified in subclause 5.5.1 and the generic UE configuration update procedure as specified in subclause 5.4.4. The support for the partial network slice by a UE or an AMF is optional. If the UE supports the partial network slice and includes the S-NSSAI(s) in the requested NSSAI and: a) if the S-NSSAI(s) is allowed in the current TA but not all TAs of the registration area, and 1) if the S-NSSAI(s) is subject to NSAC for the maximum number of UEs, the AMF should include the S-NSSAI(s) in the allowed NSSAI to the UE and limit the registration area so that the S-NSSAI(s) is allowed in all the TAs of the registration area; 2) if the S-NSSAI(s) is subject to NSSAA, the AMF shall include the S-NSSAI(s) in: i) the pending NSSAI to the UE when the AMF is going to perform the network slice-specific authentication and authorization for the S-NSSAI(s); or ii) the partially allowed NSSAI to the UE after the network slice-specific authentication and authorization for the S-NSSAI(s) has been successfully performed; and 3) otherwise, the AMF shall include the S-NSSAI(s) in the partially allowed NSSAI to the UE; or b) if the S-NSSAI(s) is rejected in the current TA but not all TAs of the registration area; and 1) if the S-NSSAI is subject to NSAC for the maximum number of UEs, the AMF should include the S-NSSAI(s) in the partially rejected NSSAI to the UE; 2) if the S-NSSAI(s) is subject to NSSAA, the AMF shall include the S-NSSAI(s) in: i) the partially rejected NSSAI to the UE when the AMF determines not to perform the network slice-specific authentication and authorization for the S-NSSAI(s); ii) the pending NSSAI to the UE when the AMF is going to perform the network slice-specific authentication and authorization for the S-NSSAI(s); or iii) either the partially allowed NSSAI or the partially rejected NSSAI to the UE after the network slice-specific authentication and authorization for the S-NSSAI(s) has been successfully performed; NOTE 1: The AMF determines whether to perform the network slice-specific authentication and authorization procedure for the partial network slice based on its own local policy. 3) if the S-NSSAI(s) is associated with a slice deregistration inactivity timer on the AMF side as specified in subclause 4.6.2.9, the AMF shall include the S-NSSAI(s) in the partially rejected NSSAI to the UE; and 4) otherwise, the AMF shall include the S-NSSAI(s) in either the partially allowed NSSAI or the partially rejected NSSAI to the UE; or c) if the partially allowed NSSAI, the partially rejected NSSAI, or both are changed, the AMF shall provide the new partially allowed NSSAI, the new partially rejected NSSAI, or both to the UE. Upon receiving the partially allowed NSSAI, the UE shall regard the S-NSSAI(s) included in partially allowed NSSAI as the allowed S-NSSAI(s) for the current registration area and store the received partially allowed NSSAI as specified in subclause 4.6.2.2. Upon receiving the partially rejected NSSAI, the UE shall store the received partially rejected NSSAI as specified in subclause 4.6.2.2. The UE shall not attempt to include the S-NSSAI in the requested NSSAI if the current TAI is in the list of TAs for which S-NSSAI is rejected. The mobility management for partial network slice is only applicable to 3GPP access. The mobility management for partial network slice is not applicable to a UE that is registering or registered for onboarding services in 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 | 4.6.2.11 |
6,200 | 6.4.2.4.3 Handling of network rejection not due to congestion control | If the 5GSM cause value is different from #26 "insufficient resources", #37 "5GS QoS not accepted", #44 "Semantic errors in packet filter(s)", #45 "Syntactical error in packet filter(s)", #46 "out of LADN service area", #59 "unsupported 5QI value", #67 "insufficient resources for specific slice and DNN", #69 "insufficient resources for specific slice", #83 "Semantic error in the QoS operation", and #84 "Syntactical error in the QoS operation", 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 DNN and S-NSSAI to the network during the PDU session establishment, the UE shall start the back-off timer with the value provided in the Back-off timer value IE for the PDU session modification procedure and: i) in a PLMN, [PLMN, DNN, (mapped) HPLMN S-NSSAI of the PDU session] combination. The UE shall not send another PDU SESSION MODIFICATION REQUEST message with exception of those identified in subclause 6.4.2.1, for the same DNN and the (mapped) HPLMN S-NSSAI of the PDU session 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 MODIFICATION REQUEST message with exception of those identified in subclause 6.4.2.1, for the same DNN and (mapped) subscribed SNPN S-NSSAI of the PDU session 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 did not provide a DNN or S-NSSAI or any of the two parameters to the network during the PDU session establishment, it shall start the back-off timer accordingly for the PDU session modification procedure and: i) in a PLMN, [PLMN, DNN, no S-NSSAI], [PLMN, no DNN, (mapped) HPLMN S-NSSAI of the PDU session] or [PLMN, no DNN, no S-NSSAI] combination. Dependent on the combination, the UE shall not send another PDU SESSION MODIFICATION REQUEST message with exception of those identified in subclause 6.4.2.1, for the same [PLMN, DNN, no S-NSSAI], [PLMN, no DNN, (mapped) HPLMN S-NSSAI of the PDU session] 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 of the PDU session] 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 MODIFICATION REQUEST message with exception of those identified in subclause 6.4.2.1, 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 of the PDU session] or [SNPN, selected entry of the "list of subscriber data" or selected PLMN subscription, no DNN, no S-NSSAI] combination in the current SNPN, until the back-off timer expires, the UE is switched off, the USIM is removed, or the selected entry in the "list of subscriber data" is updated; b) if the timer value indicates that this timer is deactivated and: 1) if the UE provided DNN and S-NSSAI to the network during the PDU session establishment, the UE shall not send another PDU SESSION MODIFICATION REQUEST message with exception of those identified in subclause 6.4.2.1, for: i) in a PLMN, the same DNN and the (mapped) HPLMN S-NSSAI of the PDU session in the current PLMN, until the UE is switched off, or the USIM is removed; or ii) in an SNPN, the same DNN and the (mapped) subscribed SNPN S-NSSAI of the PDU session in the current SNPN using the selected entry of the "list of subscriber data" or selected PLMN subscription, until the UE is switched off, or the USIM is removed, or the selected entry in the "list of subscriber data"; 2) 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, the UE shall not send another PDU SESSION MODIFICATION REQUEST message with exception of those identified in subclause 6.4.2.1, for: i) in a PLMN; the same [PLMN, DNN, no S-NSSAI], [PLMN, no DNN, (mapped) HPLMN S-NSSAI of the PDU session] 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 of the PDU session] 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 in the "list of subscriber data" is updated; and c) if the timer value indicates zero, the UE may send another PDU SESSION MODIFICATION REQUEST message for: 1) in a PLMN, the same combination of [PLMN, DNN, (mapped) HPLMN S-NSSAI of the PDU session], [PLMN, DNN, no S-NSSAI], [PLMN, no DNN, (mapped) HPLMN S-NSSAI of the PDU session], or [PLMN, no 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, (mapped) subscribed SNPN S-NSSAI of the PDU session], [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 of the PDU session], or [SNPN, the selected entry of the "list of subscriber data" or selected PLMN subscription, no DNN, no S-NSSAI] in the current SNPN. 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 MODIFICATION REJECT message, if any. a) Additionally, if the 5GSM cause value is #32 "service option not supported", or #33 "requested service option not subscribed", 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 the 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 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 and the UE used the USIM for registration to the current SNPN; 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 values different from #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: 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 modification 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 3: 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 MODIFICATION REQUEST message for the combination of [PLMN, DNN, (mapped) HPLMN S-NSSAI of the PDU session], [PLMN, DNN, no S-NSSAI], [PLMN, no DNN, (mapped) HPLMN S-NSSAI of the PDU session], or [PLMN, no DNN, no S-NSSAI] 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], or [SNPN, the selected entry of the "list of subscriber data" or selected PLMN subscription, no DNN, no S-NSSAI] in the SNPN. If the back-off timer is started upon receipt of a PDU SESSION MODIFICATION 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 the UE may send a PDU SESSION MODIFICATION REQUEST message for: 1) in a PLMN, the combination of [new PLMN, DNN, (mapped) HPLMN S-NSSAI of the PDU session], [new PLMN, DNN, no S-NSSAI], [new PLMN, no DNN, (mapped) HPLMN S-NSSAI of the PDU session], 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 modification procedure and the combination of [new PLMN, DNN, (mapped) HPLMN S-NSSAI of the PDU session], [new PLMN, DNN, no S-NSSAI], [new PLMN, no DNN, (mapped) HPLMN S-NSSAI of the PDU session], or [new PLMN, no DNN, no S-NSSAI]; or 2) 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 of the PDU session], [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 of the PDU session], 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 modification 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 of the PDU session], [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 of the PDU session], or [new SNPN, the selected entry of the "list of subscriber data" or selected PLMN subscription, no DNN, no S-NSSAI]; Furthermore, as an implementation option, for the 5GSM cause value #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 PDU SESSION MODIFICATION REQUEST message: 1) in a PLMN, the same combination of [PLMN, DNN, (mapped) HPLMN S-NSSAI of the PDU session], [PLMN, DNN, no S-NSSAI], [PLMN, no DNN, (mapped) HPLMN S-NSSAI of the PDU session], or [PLMN, no DNN, no S-NSSAI], if the UE is registered to a new PLMN which is in the list of equivalent PLMNs; or 2) 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 of the PDU session], [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 of the PDU session], or [SNPN, the selected entry of the "list of subscriber data" or selected PLMN subscription, no DNN, no S-NSSAI], if the UE is registered to a new SNPN which is in the list of equivalent SNPNs. 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 of the PDU session] 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 an EPS bearer resource allocation procedure or an EPS bearer resource modification procedure for the same [PLMN, DNN] combination in S1 mode; and NOTE 4: 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 an EPS bearer resource allocation procedure or an EPS bearer resource modification procedure for the same [PLMN, 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 equivalent 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 of the PDU session], [DNN, no S-NSSAI], [no DNN, (mapped) HPLMN S-NSSAI of the PDU session], or [no DNN, no S-NSSAI] combination, the UE shall start a back-off timer for the PDU session modification 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 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 of the PDU session], [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 of the PDU session], 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 modification procedure with the value provided by the network, or deactivate the respective back-off timer, for N1 mode in an SNPN. If the back-off timer for a [PLMN, DNN] or [PLMN, no DNN] combination was started or deactivated in S1 mode upon receipt of BEARER RESOURCE ALLOCATION REJECT message or BEARER RESOURCE MODIFICATION 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 MODIFICATION REQUEST message in this PLMN for the same 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 MODIFICATION REQUEST message with exception of those identified in subclause 6.4.2.1, in this PLMN for the same 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 5: 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 6: 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. 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 MODIFICATION REQUEST message except for indicating a change of 3GPP PS data off UE status or another PDU SESSION ESTABLISHMENT REQUEST message 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 provided by network as described in subclause 5.4.4 and subclause 5.5.1. NOTE 7: 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 7A: 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 #37 "5GS QoS not accepted", #44 "Semantic errors in packet filter(s)", #45 "Syntactical error in packet filter(s)", #59 "unsupported 5QI value", #83 "Semantic error in the QoS operation" or #84 "Syntactical error in the QoS operation", the UE shall ignore the Back-off timer value IE and Re-attempt indicator IE provided by the network, if any. The UE should pass the corresponding error cause to the upper layers. NOTE 8: How to solve the issues of not accepted 5GS QoS and unsupported 5QI value in the upper layers is UE implementation specific. | 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.2.4.3 |
Subsets and Splits
No saved queries yet
Save your SQL queries to embed, download, and access them later. Queries will appear here once saved.