Search is not available for this dataset
doc_id
int64 1
6.72k
⌀ | Section
stringlengths 5
247
⌀ | Content
stringlengths 501
147k
⌀ | Source
stringclasses 456
values | Document Title
stringclasses 22
values | Working Group
stringclasses 21
values | Series Subject
stringclasses 9
values | Subclause
stringlengths 1
13
⌀ |
|---|---|---|---|---|---|---|---|
2,801 | 4.11.1.4.3 EPS bearer ID revocation | Following procedures are updated to revoke the EPS bearer ID(s) assigned to the QoS flow(s): - UE or network requested PDU Session Release for Non-roaming and Roaming with Local Breakout (clause 4.3.4.2). - UE or network requested PDU Session Release for Home-routed Roaming (clause 4.3.4.3). - UE or network requested PDU Session Modification (non-roaming and roaming with local breakout) (clause 4.3.3.2). - UE or network requested PDU Session Modification (home-routed roaming) (clause 4.3.3.3). - Handover of a PDU Session procedure from 3GPP to untrusted non-3GPP access (non-roaming and roaming with local breakout) (clause 4.9.2.2) - Handover of a PDU Session procedure from 3GPP to untrusted non-3GPP access (home routed roaming) (clause 4.9.2.4 When the PDU Session is released as described in clauses 4.3.4.2 or 4.3.4.3, 4.9.2.2, or 4.9.2.4 and the SMF invokes Nsmf_PDUSession_StatusNotify to notify AMF that the SM context for this PDU Session is released, the AMF releases the association between the SMF ID and the PDU Session ID and releases the EBIs assigned for this PDU Session. When all the PDU sessions which are allocated with EBIs are released in the same SMF, the AMF may revoke DNN and SMF+PGW-C FQDN for S5/S8 interface in the UDM using Nudm_UECM_Update service operation. NOTE 1: If the SMF+PGW-C in which the PDU sessions support EPS interworking is changed for the same DNN, the AMF can update the DNN and new SMF+PGW-C FQDN for S5/S8 interface in the UDM using Nudm_UECM_Update service operation. When the UE initiates a PDU Session Modification as described in clauses 4.3.3.2 or 4.3.3.3 and the SMF needs to release the assigned EBI from a QoS flow (e.g. when the QoS flow is released), the SMF can indicate the Released EBI list in the Nsmf_PDUSession_UpdateSMContext Response to the AMF. The AMF releases the corresponding EBI allocation for this PDU Session. When the AMF decides to revoke some EBI(s), e.g. when the AMF receives a new EBI allocation request but there is no EBI available, the AMF may decide to revoke EBI(s) for another PDU Session, the AMF initiates a PDU Session Modification as described in clauses 4.3.3.2 or 4.3.3.3 and includes EBI list to be revoked in the Nsmf_PDUSession_UpdateSMContext Request. The SMF releases the indicated EBI(s) for the PDU Session. When the AMF initiates a PDU Session Modification as described in clauses 4.3.3.2 or 4.3.3.3 to change the status of EPS interworking with N26 to "not supported", the AMF releases the EBIs assigned for this PDU Session and SMF release the assigned EBIs from the QoS Flows belonging to this PDU Session. When the SMF initiates a PDU Session Modification as described in clauses 4.3.3.2 or 4.3.3.3 and the SMF needs to release the assigned EBI from a QoS flow (e.g. when the QoS flow is released), the SMF invokes Namf_Communication_EBIAssignment and indicates the Released EBI list to the AMF. The AMF releases the corresponding EBI allocation for this PDU Session. When the handover of a PDU Session procedure from 3GPP to untrusted non-3GPP access is performed in clause 4.9.2.2 or clause 4.9.2.4.1, the AMF, the SMF and the UE releases locally the EBI(s) allocated for this PDU Session. When the handover of a PDU Session procedure from 3GPP to untrusted non-3GPP access is performed in clause 4.9.2.4.2, the H-SMF invokes Nsmf_PDUSession_StatusNotify to notify V-AMF to release the association between the SMF ID and the PDU Session ID and as a result, the EBI(s) assigned for this PDU Session are released. The UE releases locally the EBI(s) allocated for this PDU Session. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.11.1.4.3 |
2,802 | – EarlyUL-SyncConfig | The IE EarlyUL-SyncConfig is used to configure random access resources for the early UL synchronization procedure. EarlyUL-SyncConfig information element -- ASN1START -- TAG-EARLYUL-SYNCCONFIG-START EarlyUL-SyncConfig-r18 ::= SEQUENCE { frequencyInfoUL-r18 FrequencyInfoUL, rach-ConfigGeneric-r18 RACH-ConfigGeneric, bwp-GenericParameters-r18 BWP, ssb-PerRACH-Occasion-r18 ENUMERATED {oneEighth, oneFourth, oneHalf, one, two, four, eight, sixteen} OPTIONAL, -- Need M prach-RootSequenceIndex-r18 CHOICE { l839 INTEGER (0..837), l139 INTEGER (0..137) }, ltm-prach-SubcarrierSpacing-r18 SubcarrierSpacing, n-TimingAdvanceOffset-r18 ENUMERATED { n0, n25600, n39936 } OPTIONAL, -- Need R ... } -- TAG-EARLYUL-SYNCCONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
2,803 | 10.5.5.10 IMEISV request | The purpose of the IMEISV request information element is to indicate that the IMEISV shall be included by the MS in the authentication and ciphering response message. The IMEISV request is a type 1 information element. The IMEISV request information element is coded as shown in figure 10.5.126/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.143/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Figure 10.5.126/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : IMEISV request information element Table 10.5.143/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : IMEISV request information element | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 10.5.5.10 |
2,804 | 5.5.1.2.2 Initial registration initiation | The UE in state 5GMM-DEREGISTERED shall initiate the registration procedure for initial registration by sending a REGISTRATION REQUEST message to the AMF, a) when the UE performs initial registration for 5GS services; b) when the UE performs initial registration for emergency services; c) when the UE performs initial registration for SMS over NAS; d) when the UE moves from GERAN to NG-RAN coverage or the UE moves from a UTRAN to NG-RAN coverage and the following applies: 1) the UE initiated a GPRS attach or routing area updating procedure while in A/Gb mode or Iu mode; or 2) the UE has performed 5G-SRVCC from NG-RAN to UTRAN as specified in 3GPP TS 23.216[ Single Radio Voice Call Continuity (SRVCC); Stage 2 ] [6A], and since then the UE did not perform a successful EPS attach or tracking area updating procedure in S1 mode or registration procedure in N1 mode; e) when the UE performs initial registration for onboarding services in SNPN; f) when the UE performs initial registration for disaster roaming services; and g) when the UE performs initial registration to come out of unavailability period and resume normal services; with the following clarifications to initial registration for emergency services: a) the UE shall not initiate an initial registration for emergency services over the current access, if the UE is already registered for emergency services over the non-current access, unless the initial registration has to be initiated to perform handover of an existing emergency PDU session from the non-current access to the current access; and NOTE 1: Transfer of an existing emergency PDU session between 3GPP access and non-3GPP access is needed e.g. if the UE determines that the current access is no longer available. b) the UE can only initiate an initial registration for emergency services over non-3GPP access if it cannot register for emergency services over 3GPP access. The UE initiates the registration procedure for initial registration by sending a REGISTRATION REQUEST message to the AMF, starting timer T3510. If timer T3502 is currently running, the UE shall stop timer T3502. If timer T3511 is currently running, the UE shall stop timer T3511. During initial registration the UE handles the 5GS mobile identity IE in the following order: a) if: 1) the UE: i) was previously registered in S1 mode before entering state EMM-DEREGISTERED; and ii) has received an "interworking without N26 interface not supported" indication from the network; and 2) EPS security context and a valid native 4G-GUTI are available; then the UE shall create a 5G-GUTI mapped from the valid native 4G-GUTI as specified in 3GPP TS 23.003[ Numbering, addressing and identification ] [4] and indicate the mapped 5G-GUTI in the 5GS mobile identity IE. The UE shall include the UE status IE with the EMM registration status set to "UE is not in EMM-REGISTERED state" and shall include an ATTACH REQUEST message as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15] in the EPS NAS message container IE. Additionally, if the UE holds a valid 5G-GUTI, the UE shall include the 5G-GUTI in the Additional GUTI IE in the REGISTRATION REQUEST message in the following order: 1) a valid 5G-GUTI that was previously assigned by the same PLMN with which the UE is performing the registration, if available; 2) a valid 5G-GUTI that was previously assigned by an equivalent PLMN, if available; and 3) a valid 5G-GUTI that was previously assigned by any other PLMN, if available; b) if: 1) the UE is registering with a PLMN and the UE holds a valid 5G-GUTI that was previously assigned, over 3GPP access or non-3GPP access, by the same PLMN with which the UE is performing the registration, the UE shall indicate the 5G-GUTI in the 5GS mobile identity IE; or 2) the UE is registering with a SNPN, the UE holds a valid 5G-GUTI that was previously assigned, over 3GPP access or non-3GPP access, by the same SNPN with which the UE is performing the registration, and the UE is not initiating the initial registration for onboarding services in SNPN, the UE shall indicate the 5G-GUTI in the 5GS mobile identity IE; c) if: 1) the UE is registering with a PLMN and the UE holds a valid 5G-GUTI that was previously assigned, over 3GPP access or non-3GPP access, by an equivalent PLMN, the UE shall indicate the 5G-GUTI in the 5GS mobile identity IE; or 2) the UE is registering with an SNPN, the UE holds a valid 5G-GUTI that was previously assigned, over 3GPP access or non-3GPP access, by an equivalent SNPN identified by a globally unique SNPN identity, and the UE is not initiating the initial registration for onboarding services in SNPN, the UE shall indicate the 5G-GUTI in the 5GS mobile identity IE and shall additionally include the NID of the equivalent SNPN in the NID IE; d) if: 1) the UE is registering with a PLMN and the UE holds a valid 5G-GUTI that was previously assigned, over 3GPP access or non-3GPP access, by any other PLMN, the UE shall indicate the 5G-GUTI in the 5GS mobile identity IE; or 2) the UE is registering with an SNPN, the UE holds a valid 5G-GUTI that was previously assigned, over 3GPP access or non-3GPP access, by any other SNPN identified by a globally unique SNPN identity, and the UE is not initiating the initial registration for onboarding services in SNPN, the UE shall indicate the 5G-GUTI in the 5GS mobile identity IE and shall additionally include the NID of the other SNPN in the NID IE; e) if a SUCI other than an onboarding SUCI is available, and the UE is not initiating the initial registration for onboarding services in SNPN, the UE shall include the SUCI other than an onboarding SUCI in the 5GS mobile identity IE; f) if the UE does not hold a valid 5G-GUTI or SUCI other than an onboarding SUCI, and is initiating the initial registration for emergency services, the PEI shall be included in the 5GS mobile identity IE; and g) if the UE is initiating the initial registration for onboarding services in SNPN, an onboarding SUCI shall be included in the 5GS mobile identity IE. NOTE 2: The AMF in ON-SNPN uses the onboarding SUCI as specified in 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8]. If the SUCI is included in the 5GS mobile identity IE and the timer T3519 is not running, the UE shall start timer T3519 and store the value of the SUCI sent in the REGISTRATION REQUEST message. The UE shall include the stored SUCI in the REGISTRATION REQUEST message while timer T3519 is running. If the UE is operating in the dual-registration mode and it is in EMM state EMM-REGISTERED, the UE shall include the UE status IE with the EMM registration status set to "UE is in EMM-REGISTERED state". NOTE 3: Inclusion of the UE status IE with this setting corresponds to the indication that the UE is "moving from EPC" as specified in 3GPP TS 23.502[ Procedures for the 5G System (5GS) ] [9]. NOTE 4: The value of the 5GMM registration status included by the UE in the UE status IE is not used by the AMF. If the last visited registered TAI is available, the UE shall include the last visited registered TAI in the REGISTRATION REQUEST message. NOTE 5: The AMF can use the last visited registered TAI included in the REGISTRATION REQUEST message, if available, in the procedure of slice-based N3IWF selection as specified in 3GPP TS 23.502[ Procedures for the 5G System (5GS) ] [9] when the registration procedure is performed over non-3gpp access. If the UE requests the use of SMS over NAS, the UE shall include the 5GS update type IE in the REGISTRATION REQUEST message with the SMS requested bit set to "SMS over NAS supported". When the 5GS update type IE is included in the REGISTRATION REQUEST for reasons other than requesting the use of SMS over NAS, and the UE does not need to register for SMS over NAS, the UE shall set the SMS requested bit of the 5GS update type IE to "SMS over NAS not supported" in the REGISTRATION REQUEST message. If the UE supports MICO mode and requests the use of MICO mode, then the UE shall include the MICO indication IE in the REGISTRATION REQUEST message. If the UE requests to use an active time value, it shall include the active time value in the T3324 IE in the REGISTRATION REQUEST message. If the UE includes the T3324 IE, it may also request a particular T3512 value by including the Requested T3512 IE in the REGISTRATION REQUEST message. Additionally, if the UE supports strictly periodic registration timer, the UE shall set the Strictly Periodic Registration Timer Indication bit of the MICO indication IE in the REGISTRATION REQUEST message to "strictly periodic registration timer supported". If the UE needs to use the UE specific DRX parameters, the UE shall include the Requested DRX parameters IE in the REGISTRATION REQUEST message. If the UE is in NB-N1 mode and if the UE needs to use the UE specific DRX parameters for NB-N1 mode, the UE shall include the Requested NB-N1 mode DRX parameters IE in the REGISTRATION REQUEST message. If the UE supports eDRX and requests the use of eDRX, the UE shall include the Requested extended DRX parameters IE in the REGISTRATION REQUEST message. If the UE needs to request LADN information for specific LADN DNN(s) or indicates a request for LADN information as specified in 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8], the UE shall include the LADN indication IE in the REGISTRATION REQUEST message and: - request specific LADN DNNs by including a LADN DNN value in the LADN indication IE for each LADN DNN for which the UE requests LADN information; or - to indicate a request for LADN information by not including any LADN DNN value in the LADN indication IE. The UE shall include the requested NSSAI containing the S-NSSAI(s) corresponding to the slice(s) to which the UE intends to register with and shall include the mapped S-NSSAI(s) for the requested NSSAI, if available, in the REGISTRATION REQUEST message. If the UE has allowed NSSAI or configured NSSAI or both for the current PLMN or SNPN, the requested NSSAI shall be either: a) the configured NSSAI for the current PLMN or SNPN, or a subset thereof as described below; b) the allowed NSSAI for the current PLMN or SNPN, or a subset thereof as described below; or c) the allowed NSSAI for the current PLMN or SNPN, or a subset thereof as described below, plus the configured NSSAI for the current PLMN or SNPN, or a subset thereof as described below. If the UE supports the S-NSSAI time validity information, S-NSSAI time validity information is available for an S-NSSAI, and the S-NSSAI time validity information indicates that the S-NSSAI is not available, the UE shall not include the S-NSSAI in the Requested NSSAI IE of the REGISTRATION REQUEST message. If the UE has S-NSSAI time validity information over the other access in the same PLMN and the S-NSSAI time validity information indicates that the S-NSSAI is not available, the UE shall not include the S-NSSAI in the Requested NSSAI IE of the REGISTRATION REQUEST message for the current access type. If the UE has neither allowed NSSAI for the current PLMN or SNPN nor configured NSSAI for the current PLMN or SNPN and has a default configured NSSAI, the UE shall: a) include the S-NSSAI(s) in the Requested NSSAI IE of the REGISTRATION REQUEST message using the default configured NSSAI; and b) include the Network slicing indication IE with the Default configured NSSAI indication bit set to "Requested NSSAI created from default configured NSSAI" in the REGISTRATION REQUEST message. If the UE has no allowed NSSAI for the current PLMN or SNPN, no configured NSSAI for the current PLMN or SNPN, and no default configured NSSAI, the UE shall not include a requested NSSAI in the REGISTRATION REQUEST message. If all the S-NSSAI(s) corresponding to the slice(s) to which the UE intends to register are included in the pending NSSAI, the UE shall not include a requested NSSAI in the REGISTRATION REQUEST message. The subset of configured NSSAI provided in the requested NSSAI consists of one or more S-NSSAIs in the configured NSSAI applicable to the current PLMN or SNPN, where any included S-NSSAI is: a) neither in the rejected NSSAI nor associated to an S-NSSAI in the rejected NSSAI. If the UE is inside the NS-AoS of an S-NSSAI in the rejected NSSAI with a rejection cause value set to "S-NSSAI not available in the current registration area", the S-NSSAI may be included in the requested NSSAI; or b) in the partially rejected NSSAI and the current TAI is not in the list of TAs for which the S-NSSAI is rejected. If the UE is inside the NS-AoS of an S-NSSAI in the partially rejected NSSAI and the current TAI is in the list of TAs for which the S-NSSAI is rejected, the S-NSSAI may be included in the requested NSSAI. In addition, if the NSSRG information is available, the subset of configured NSSAI provided in the requested NSSAI shall be associated with at least one common NSSRG value. The UE may also include in the requested NSSAI, the S-NSSAI(s) which were added to configured NSSAI in S1 mode and for which the associated NSSRG information is not available. If the UE is in 5GMM-REGISTERED state over the other access and has already an allowed NSSAI for the other access in the same PLMN or in different PLMNs, all the S-NSSAI(s) in the requested NSSAI for the current access shall share at least an NSSRG value common to all the S-NSSAI(s) of the allowed NSSAI for the other access. If the UE is simultaneously performing the registration procedure on the other access in different PLMNs, the UE shall include S-NSSAIs that share at least a common NSSRG value across all access types. The S-NSSAIs in the pending NSSAI and requested NSSAI shall be associated with at least one common NSSRG value. NOTE 6: If the UE has stored mapped S-NSSAI(s) for the rejected NSSAI, and one or more S-NSSAIs in the stored mapped S-NSSAI(s) for the configured NSSAI are not included in the stored mapped S-NSSAI(s) for the rejected NSSAI, then a S-NSSAI in the configured NSSAI associated to one or more of these mapped S-NSSAI(s) for the configured NSSAI are available to be included in the requested NSSAI together with their mapped S-NSSAI. NOTE 7: If one or more mapped S-NSSAIs in the stored mapped S-NSSAI(s) for the configured NSSAI are not included in the stored rejected NSSAI for the failed or revoked NSSAA, a S-NSSAI in the configured NSSAI associated to one or more of these mapped S-NSSAI(s) for the configured NSSAI are available to be included in the registration request together with their mapped S-NSSAI. NOTE 8: There is no need to consider the case that the UE is simultaneously performing the registration procedure on the other access in the same PLMN, due to that the UE is not allowed to initiate the registration procedure over one access when the registration over the other access to the same PLMN is going on. The subset of allowed NSSAI provided in the requested NSSAI consists of one or more S-NSSAIs in the allowed NSSAI for the current PLMN. NOTE 9: How the UE selects the subset of configured NSSAI or allowed NSSAI to be provided in the requested NSSAI is implementation specific. The UE can take preferences indicated by the upper layers (e.g. policies like URSP, applications) and UE local configuration into account. NOTE 10: The number of S-NSSAI(s) included in the requested NSSAI cannot exceed eight. If the UE initiates an initial registration for onboarding services in SNPN, the UE shall not include the Requested NSSAI IE in the REGISTRATION REQUEST message. If the UE supports NSAG, the UE shall set the NSAG bit to "NSAG supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports sending of REGISTRATION COMPLETE message for acknowledging the reception of NSAG information IE in the REGISTRATION ACCEPT message, the UE shall set the RCMAN bit to "Sending of REGISTRATION COMPLETE message for NSAG information supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE initiates an initial registration for emergency services or needs to prolong the established NAS signalling connection after the completion of the initial registration procedure (e.g. due to uplink signalling pending), the UE shall set the Follow-on request indicator to "Follow-on request pending". NOTE 11: The UE does not have to set the Follow-on request indicator to 1, even if the UE has to request resources for V2X communication over PC5 reference point, 5G ProSe direct discovery over PC5, 5G ProSe direct communication over PC5 or A2X communication over PC5 reference point. If the UE supports S1 mode and the UE has not disabled its E-UTRA capability and the 5GS registration type IE in the REGISTRATION REQUEST message is not set to "disaster roaming initial registration", the UE shall: - set the S1 mode bit to "S1 mode supported" in the 5GMM capability IE of the REGISTRATION REQUEST message; - include the S1 UE network capability IE in the REGISTRATION REQUEST message; additionally, if the UE supports EPS-UPIP, the UE shall set the EPS-UPIP bit to "EPS-UPIP supported" in the S1 UE network capability IE in the REGISTRATION REQUEST message; and - if the UE supports sending an ATTACH REQUEST message containing a PDN CONNECTIVITY REQUEST message with request type set to "handover" to transfer a PDU session from N1 mode to S1 mode, set the HO attach bit to "attach request message containing PDN connectivity request with request type set to handover to transfer PDU session from N1 mode to S1 mode supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports the LTE positioning protocol (LPP) in N1 mode as specified in 3GPP TS 37.355[ LTE Positioning Protocol (LPP) ] [26], the UE shall set the LPP bit to "LPP in N1 mode supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports the Location Services (LCS) notification mechanisms in N1 mode as specified in 3GPP TS 23.273[ 5G System (5GS) Location Services (LCS); Stage 2 ] [6B], the UE shall set the 5G-LCS bit to "LCS notification mechanisms supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports the user plane positioning using LCS-UPP as specified in 3GPP TS 23.273[ 5G System (5GS) Location Services (LCS); Stage 2 ] [6B], the UE shall set the LCS-UPP bit to "LCS-UPP user plane positioning supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports the user plane positioning using SUPL as described in 3GPP TS 38.305[ NG Radio Access Network (NG-RAN); Stage 2 functional specification of User Equipment (UE) positioning in NG-RAN ] [67] and 3GPP TS 23.271[ Functional stage 2 description of Location Services (LCS) ] [68], the UE shall set the SUPL bit to "SUPL user plane positioning supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE is in NB-N1 mode, then the UE shall set the Control plane CIoT 5GS optimization bit to "Control plane CIoT 5GS optimization supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE is capable of NB-S1 mode, then the UE shall set the Control plane CIoT EPS optimization bit to "Control plane CIoT EPS optimization supported" in the S1 UE network capability IE of the REGISTRATION REQUEST message. If the UE supports N3 data transfer and multiple user-plane resources in NB-N1 mode (see 3GPP TS 36.306[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio access capabilities ] [25D], 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [25A]), then the UE shall set the Multiple user-plane resources support bit to "Multiple user-plane resources supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports 5G-SRVCC from NG-RAN to UTRAN as specified in 3GPP TS 23.216[ Single Radio Voice Call Continuity (SRVCC); Stage 2 ] [6A], the UE shall: - set the 5G-SRVCC from NG-RAN to UTRAN capability bit to "5G-SRVCC from NG-RAN to UTRAN supported" in the 5GMM capability IE of the REGISTRATION REQUEST message; and - include the Mobile station classmark 2 IE and the Supported codecs IE in the REGISTRATION REQUEST message. If the UE supports service gap control, then the UE shall set the SGC bit to "service gap control supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports the restriction on use of enhanced coverage, the UE shall set the RestrictEC bit to "Restriction on use of enhanced coverage supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports network slice-specific authentication and authorization, the UE shall set the NSSAA bit to "network slice-specific authentication and authorization supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports CAG feature, the UE shall set the CAG bit to "CAG Supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports extended CAG information list, the UE shall set the Ex-CAG bit to "Extended CAG information list supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports enhanced CAG information, the UE shall set the ECI bit to "enhanced CAG information supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports network slice replacement, the UE shall set the NSR bit to "network slice replacement supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports sending of REGISTRATION COMPLETE message for acknowledging the reception of Negotiated PEIPS assistance information IE in the REGISTRATION ACCEPT message, the UE shall set the RCMP bit to "Sending of REGISTRATION COMPLETE message for negotiated PEIPS assistance information supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. When the UE is not in NB-N1 mode, if the UE supports RACS, the UE shall: a) set the RACS bit to "RACS supported" in the 5GMM capability IE of the REGISTRATION REQUEST message; b) if the UE has an applicable network-assigned UE radio capability ID for the current UE radio configuration in the selected PLMN or SNPN, include the applicable network-assigned UE radio capability ID in the UE radio capability ID IE of the REGISTRATION REQUEST message; and c) if the UE: 1) does not have an applicable network-assigned UE radio capability ID for the current UE radio configuration in the selected PLMN or SNPN; and 2) has an applicable manufacturer-assigned UE radio capability ID for the current UE radio configuration, include the applicable manufacturer-assigned UE radio capability ID in the UE radio capability ID IE of the REGISTRATION REQUEST message. If the UE has one or more stored UE policy sections: - identified by a UPSI with the PLMN ID part indicating the HPLMN or the selected PLMN; or - identified by a UPSI with the PLMN ID part indicating the PLMN ID part of the SNPN identity of the selected SNPN and associated with the NID of the selected SNPN; then the UE shall set the Payload container type IE to "UE policy container" and include the UE STATE INDICATION message (see annex D) in the Payload container IE of the REGISTRATION REQUEST message. If the UE does not have any stored UE policy section: - identified by a UPSI with the PLMN ID part indicating the HPLMN or the selected PLMN; or - identified by a UPSI with the PLMN ID part indicating the PLMN ID part of the SNPN identity of the selected SNPN and associated with the NID of the selected SNPN; and the UE needs to send a UE policy container to the network, then the UE shall set the Payload container type IE to "UE policy container" and include the UE STATE INDICATION message (see annex D) in the Payload container IE of the REGISTRATION REQUEST message. NOTE 12: In this version of the protocol, the UE can only include the Payload container IE in the REGISTRATION REQUEST message to carry a payload of type "UE policy container". If the UE does not have a valid 5G NAS security context, the UE shall send the REGISTRATION REQUEST message without including the NAS message container IE. The UE shall include the entire REGISTRATION REQUEST message (i.e. containing cleartext IEs and non-cleartext IEs, if any) in the NAS message container IE that is sent as part of the SECURITY MODE COMPLETE message as described in subclauses 4.4.6 and 5.4.2.3. If the UE has a valid 5G NAS security context and the UE needs to send non-cleartext IEs, the UE shall send a REGISTRATION REQUEST message including the NAS message container IE as described in subclause 4.4.6. If the UE does not need to send non-cleartext IEs, the UE shall send a REGISTRATION REQUEST message without including the NAS message container IE. If the UE supports ciphered broadcast assistance data and needs to obtain new ciphering keys, the UE shall include the Additional information requested IE with the CipherKey bit set to "ciphering keys for ciphered broadcast assistance data requested" in the REGISTRATION REQUEST message. The UE shall set the WUSA bit to "WUS assistance information reception supported" in the 5GMM capability IE if the UE supports WUS assistance information. The UE may include its UE paging probability information in the Requested WUS assistance information IE if the UE has set the WUSA bit to "WUS assistance information reception supported" in the 5GMM capability IE and the UE is not performing the initial registration for emergency services. The UE shall set the NR-PSSI bit to "NR paging subgrouping supported" in the 5GMM capability IE if the UE supports PEIPS assistance information and the 5GS registration type IE in the REGISTRATION REQUEST message is not set to "emergency registration". The UE may include its UE paging probability information in the Requested PEIPS assistance information IE if the UE has set the NR-PSSI bit to "NR paging subgrouping supported" in the 5GMM capability IE. If the REGISTRATION REQUEST message includes a NAS message container IE, the AMF shall process the REGISTRATION REQUEST message that is obtained from the NAS message container IE as described in subclause 4.4.6. If the UE supports V2X as specified in 3GPP TS 24.587[ Vehicle-to-Everything (V2X) services in 5G System (5GS); Stage 3 ] [19B], the UE shall set the V2X bit to "V2X supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports V2X communication over E-UTRA-PC5 as specified in 3GPP TS 24.587[ Vehicle-to-Everything (V2X) services in 5G System (5GS); Stage 3 ] [19B], the UE shall set the V2XCEPC5 bit to "V2X communication over E-UTRA-PC5 supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports V2X communication over NR-PC5 as specified in 3GPP TS 24.587[ Vehicle-to-Everything (V2X) services in 5G System (5GS); Stage 3 ] [19B], the UE shall set the V2XCNPC5 bit to "V2X communication over NR-PC5 supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. The UE shall set the ER-NSSAI bit to "Extended rejected NSSAI supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports the NSSRG, then the UE shall set the NSSRG bit to "NSSRG supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the W-AGF acting on behalf of an N5GC device initiates an initial registration as specified in 3GPP TS 23.316[ Wireless and wireline convergence access support for the 5G System (5GS) ] [6D], the W-AGF acting on behalf of the N5GC device shall include the N5GC indication IE with the N5GC device indication bit set to "N5GC device registration is requested" in the REGISTRATION REQUEST message. If the 5G-RG acting on behalf of an AUN3 device initiates an initial registration as specified in 3GPP TS 23.316[ Wireless and wireline convergence access support for the 5G System (5GS) ] [6D], the 5G-RG acting on behalf of an AUN3 device shall include the AUN3 indication IE with the AUN3 device indication bit set to "AUN3 device registration is requested" in the REGISTRATION REQUEST message. If the UE supports UAS services, the UE shall set the UAS bit to "UAS services supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports A2X over E-UTRA-PC5 as specified in 3GPP TS 24.577[ Aircraft-to-Everything (A2X) services in 5G System (5GS) protocol aspects; Stage 3 ] [60], the UE shall set the A2XEPC5 bit to "A2X over E-UTRA-PC5 supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports A2X over NR-PC5 as specified in 3GPP TS 24.577[ Aircraft-to-Everything (A2X) services in 5G System (5GS) protocol aspects; Stage 3 ] [60], the UE shall set the A2XNPC5 bit to "A2X over NR-PC5 supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports A2X over Uu as specified in 3GPP TS 24.577[ Aircraft-to-Everything (A2X) services in 5G System (5GS) protocol aspects; Stage 3 ] [60], the UE shall set the A2X-Uu bit to "A2X over Uu supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports SL positioning server UE as specified in 3GPP TS 23.586[ Architectural Enhancements to support Ranging based services and Sidelink Positioning ] [63] over PC5, the UE shall set the SLPSPC5 bit to "SL positioning server UE over PC5 supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. When the UE supporting UAS services initiates an initial registration for UAS services, the UE shall include the service-level device ID in the Service-level-AA container IE of the REGISTRATION REQUEST message and set the value to the CAA-level UAV ID. The UE shall include the service-level-AA server address in the Service-level-AA container IE of the REGISTRATION REQUEST message and set the value to the USS address, if it is provided by the upper layers. The UE shall include the service-level-AA payload in the Service-level-AA container IE of the REGISTRATION REQUEST message and shall set the service-level-AA payload type, if the service-level-AA payload is provided by upper layers. NOTE 13: The service-level-AA payload can be of type "C2 authorization payload". The C2 authorization payload can include one or both of an indication of the request for direct C2 communication and pairing information for direct C2 communication. If the UE supports 5G ProSe direct discovery as specified in 3GPP TS 24.554[ Proximity-services (ProSe) in 5G System (5GS) protocol aspects; Stage 3 ] [19E], the UE shall set the 5G ProSe-dd bit to "5G ProSe direct discovery supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports 5G ProSe direct communication as specified in 3GPP TS 24.554[ Proximity-services (ProSe) in 5G System (5GS) protocol aspects; Stage 3 ] [19E], the UE shall set the 5G ProSe-dc bit to "5G ProSe direct communication supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports acting as 5G ProSe layer-2 UE-to-network relay UE as specified in 3GPP TS 24.554[ Proximity-services (ProSe) in 5G System (5GS) protocol aspects; Stage 3 ] [19E], the UE shall set the 5G ProSe-l2relay bit to "Acting as a 5G ProSe layer-2 UE-to-network relay UE supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports acting as 5G ProSe layer-3 UE-to-network relay UE as specified in 3GPP TS 24.554[ Proximity-services (ProSe) in 5G System (5GS) protocol aspects; Stage 3 ] [19E], the UE shall set the 5G ProSe-l3relay bit to "Acting as a 5G ProSe layer-3 UE-to-network relay UE supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports acting as 5G ProSe layer-2 UE-to-network remote UE as specified in 3GPP TS 24.554[ Proximity-services (ProSe) in 5G System (5GS) protocol aspects; Stage 3 ] [19E], the UE shall set the 5G ProSe-l2rmt bit to "Acting as a 5G ProSe layer-2 UE-to-network remote UE supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports acting as 5G ProSe layer-3 UE-to-network remote UE as specified in 3GPP TS 24.554[ Proximity-services (ProSe) in 5G System (5GS) protocol aspects; Stage 3 ] [19E], the UE shall set the 5G ProSe-l3rmt bit to "Acting as a 5G ProSe layer-3 UE-to-network remote UE supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports acting as 5G ProSe layer-2 UE-to-UE relay UE as specified in 3GPP TS 24.554[ Proximity-services (ProSe) in 5G System (5GS) protocol aspects; Stage 3 ] [19E], the UE shall set the 5G ProSe-l2U2U relay bit to "Acting as a 5G ProSe layer-2 UE-to-UE relay UE supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports acting as 5G ProSe layer-3 UE-to-UE relay UE as specified in 3GPP TS 24.554[ Proximity-services (ProSe) in 5G System (5GS) protocol aspects; Stage 3 ] [19E], the UE shall set the 5G ProSe-l3U2U relay bit to "Acting as a 5G ProSe layer-3 UE-to-UE relay UE supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports acting as 5G ProSe layer-2 end UE as specified in 3GPP TS 24.554[ Proximity-services (ProSe) in 5G System (5GS) protocol aspects; Stage 3 ] [19E], the UE shall set the 5G ProSe-l2end bit to "Acting as a 5G ProSe layer-2 end UE supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports acting as 5G ProSe layer-3 end UE as specified in 3GPP TS 24.554[ Proximity-services (ProSe) in 5G System (5GS) protocol aspects; Stage 3 ] [19E], the UE shall set the 5G ProSe-l3end bit to "Acting as a 5G ProSe layer-3 end UE supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the MUSIM UE supports the N1 NAS signalling connection release, then the UE shall set the N1 NAS signalling connection release bit to "N1 NAS signalling connection release supported" in the 5GMM capability IE of the REGISTRATION REQUEST message otherwise the UE shall not set the N1 NAS signalling connection release bit to "N1 NAS signalling connection release supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the MUSIM UE supports the paging indication for voice services, then the UE shall set the paging indication for voice services bit to "paging indication for voice services supported" in the 5GMM capability IE of the REGISTRATION REQUEST message otherwise the UE shall not set the paging indication for voice services bit to "paging indication for voice services supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the MUSIM UE supports the reject paging request, then the UE shall set the reject paging request bit to "reject paging request supported" in the 5GMM capability IE of the REGISTRATION REQUEST message otherwise the UE shall not set the reject paging request bit to "reject paging request supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the MUSIM UE sets: - the reject paging request bit to "reject paging request supported"; - the N1 NAS signalling connection release bit to "N1 NAS signalling connection release supported"; or - both of them; and supports the paging restriction, then the UE shall set the paging restriction bit to "paging restriction supported" in the 5GMM capability IE of the REGISTRATION REQUEST message otherwise the UE shall not set the paging restriction bit to "paging restriction supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports MINT, the UE shall set the MINT bit to "MINT supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports slice-based N3IWF selection, the UE shall set the SBNS bit to "Slice-based N3IWF selection supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports slice-based TNGF selection, the UE shall set the SBTS bit to "Slice-based TNGF selection supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE initiates the registration procedure for disaster roaming services, the UE has determined the MS determined PLMN with disaster condition as specified in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5] and: a) the MS determined PLMN with disaster condition is the HPLMN and: 1) the Additional GUTI IE is included in the REGISTRATION REQUEST message and does not contain a valid 5G-GUTI that was previously assigned by the HPLMN; or 2) the Additional GUTI IE is not included in the REGISTRATION REQUEST message and the 5GS mobile identity IE contains neither the SUCI nor a valid 5G-GUTI that was previously assigned by the HPLMN; or b) the MS determined PLMN with disaster condition is not the HPLMN and: 1) the Additional GUTI IE is included in the REGISTRATION REQUEST message and does not contain a valid 5G-GUTI that was previously assigned by the MS determined PLMN with disaster condition; or 2) the Additional GUTI IE is not included in the REGISTRATION REQUEST message and the 5GS mobile identity IE does not contain a valid 5G-GUTI that was previously assigned by the MS determined PLMN with disaster condition; the UE shall include in the REGISTRATION REQUEST message the MS determined PLMN with disaster condition IE indicating the MS determined PLMN with disaster condition. NOTE 14: If the UE initiates the registration procedure for disaster roaming services, and the MS determined PLMN with disaster condition cannot be determined when an NG-RAN cell of the PLMN broadcasts the disaster related indication as specified in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5], the UE does not include in the REGISTRATION REQUEST message the MS determined PLMN with disaster condition IE but includes the Additional GUTI IE or the 5GS mobile identity IE or both as specified in subclauses 5.5.1.2.2. If the UE supports event notification, the UE shall set the EventNotification bit to "Event notification supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports access to an SNPN using credentials from a credentials holder and the UE is in its HPLMN or EHPLMN or a subscribed SNPN, the UE shall set the SSNPNSI bit to "SOR-SNPN-SI supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports equivalent SNPNs, the UE shall set the ESI bit to "equivalent SNPNs supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports the unavailability period, the UE shall set the UN-PER bit to "unavailability period supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports the reconnection to the network due to RAN timing synchronization status change, the UE shall set the Reconnection to the network due to RAN timing synchronization status change (RANtiming) bit to "Reconnection to the network due to RAN timing synchronization status change supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports LADN per DNN and S-NSSAI, the UE shall set the LADN-DS bit to "LADN per DNN and S-NSSAI supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports MPS indicator update via the UE configuration update procedure, the UE shall set the MPSIU bit to "MPS indicator update supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports MCS indicator update via the UE configuration update procedure, the UE shall set the MCSIU bit to "MCS indicator update supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports ranging and sidelink positioning over PC5 as specified in 3GPP TS 24.514[ Ranging based services and sidelink positioning in 5G system(5GS); Stage 3 ] [62] and supports: a) V2X communication over PC5 as specified in 3GPP TS 24.587[ Vehicle-to-Everything (V2X) services in 5G System (5GS); Stage 3 ] [19B]; b) 5G ProSe direct discovery and 5G ProSe direct communication as specified in 3GPP TS 24.554[ Proximity-services (ProSe) in 5G System (5GS) protocol aspects; Stage 3 ] [19E]; or c) both a) and b), the UE shall set the RSPPC5 bit to "Ranging and sidelink positioning over PC5 supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports the partial network slice, the UE shall set the PNS bit to "Partial network slice supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports network slice usage control, the UE shall set the NSUC bit to "Network slice usage control supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports the S-NSSAI time validity information, the UE shall set the TempNS bit to "S-NSSAI time validity information supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. If the UE supports the S-NSSAI location validity information, the UE shall set the SLVI bit to "S-NSSAI location validity information supported" in the 5GMM capability IE of the REGISTRATION REQUEST message. Figure 5.5.1.2.2.1: Registration procedure for initial registration | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.5.1.2.2 |
2,805 | 4.7.7.6 Abnormal cases | The following abnormal cases can be identified: a) Lower layer failure Upon detection of a lower layer failure before the AUTHENTICATION AND CIPHERING RESPONSE message is received, the network shall abort the procedure. b) Expiry of timer T3360 The network shall, on the first expiry of the timer T3360, retransmit the AUTHENTICATION AND CIPHERING REQUEST message and shall reset and start timer T3360. This retransmission is repeated four times, i.e. on the fifth expiry of timer T3360, the procedure shall be aborted. c) Collision of an authentication and ciphering procedure with a GPRS attach procedure If the network receives an ATTACH REQUEST message before the ongoing authentication procedure has been completed and no GPRS attach procedure is pending on the network (i.e. no ATTACH ACCEPT/REJECT message has to be sent as an answer to an ATTACH REQUEST message), the network shall abort the authentication and ciphering procedure and proceed with the new GPRS attach procedure. d) Collision of an authentication and ciphering procedure with a GPRS attach procedure when the authentication and ciphering procedure has been caused by a previous GPRS attach procedure If the network receives an ATTACH REQUEST message before the ongoing authentication procedure has been completed and a GPRS attach procedure is pending (i.e. an ATTACH ACCEPT/REJECT message has still to be sent as an answer to an earlier ATTACH REQUEST message), then: - If one or more of the information elements in the ATTACH REQUEST message differs from the ones received within the previous ATTACH REQUEST message, the network shall not treat the authentication any further and proceed with the GPRS attach procedure; or - If the information elements do not differ, then the network shall not treat any further this new ATTACH REQUEST message. d1) Collision of an authentication and ciphering procedure with a GPRS detach procedure GPRS detach containing cause "power off": If the network receives a DETACH REQUEST message before the ongoing authentication and ciphering procedure has been completed, the network shall abort the authentication and ciphering procedure and shall progress the GPRS detach procedure. GPRS detach containing other causes than "power off": If the network receives a DETACH REQUEST message before the ongoing authentication and ciphering procedure has been completed, the network shall complete the authentication and ciphering procedure and shall respond to the GPRS detach procedure as described in subclause 4.7.4. e) Collision of an authentication and ciphering procedure with a routing area updating procedure If the network receives a ROUTING AREA UPDATE REQUEST message before the ongoing authentication procedure has been completed, the network shall progress both procedures. Figure 4.7.7/1 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Authentication and ciphering procedure (f) Authentication failure (GMM cause #18 "MAC failure" or #21 "GSM authentication unacceptable") The MS shall send an AUTHENTICATION AND CIPHERING FAILURE message, with GMM cause 'MAC failure’ or 'GSM authentication unacceptable’ according to subclause 4.7.7.5.1, to the network and start timer T3318. Furthermore, the MS shall stop any of the retransmission timers that are running (e.g. T3310, T3321, T3330 or T3317). Upon the first receipt of an AUTHENTICATION AND CIPHERING FAILURE message from the MS with GMM cause 'MAC failure’ or 'GSM authentication unacceptable’ the network may initiate the identification procedure described in subclause 4.7.8. This is to allow the network to obtain the IMSI from the MS. The network may then check that the P-TMSI originally used in the authentication challenge corresponded to the correct IMSI. Upon receipt of the IDENTITY REQUEST message from the network, the MS shall send the IDENTITY RESPONSE message. NOTE: Upon receipt of an AUTHENTICATION AND CIPHERING FAILURE message from the MS with reject cause "MAC failure" or "GSM authentication unacceptable", the network may also terminate the authentication procedure (see subclause 4.7.7.5). If the P-TMSI/IMSI mapping in the network was incorrect, the network should respond by sending a new AUTHENTICATION AND CIPHERING REQUEST message to the MS. Upon receiving the new AUTHENTICATION AND CIPHERING REQUEST message from the network, the MS shall stop timer T3318, if running, and then process the challenge information as normal. If the P-TMSI/IMSI mapping in the network was correct, the network should terminate the authentication and ciphering procedure by sending an AUTHENTICATION AND CIPHERING REJECT message. If the network is validated successfully (an AUTHENTICATION AND CIPHERING REQUEST message that contains a valid SQN and MAC is received), the MS shall send the AUTHENTICATION AND CIPHERING RESPONSE message to the network and shall start any retransmission timers (e.g. T3310, T3321, T3330 or T3317), if they were running and stopped when the MS received the first failed AUTHENTICATION AND CIPHERING REQUEST message. If the MS receives the second AUTHENTICATION AND CIPHERING REQUEST message while T3318 is running and - the MAC value cannot be resolved; or - the message was received in UMTS and contains a GSM authentication challenge, the MS shall follow the procedure specified in this subclause (f), starting again from the beginning. If the SQN is invalid, the MS shall proceed as specified in (g). It can be assumed that the source of the authentication challenge is not genuine (authentication not accepted by the MS) if any of the following occurs: - the timer T3318 expires; - the MS detects any combination of the authentication failures: "MAC failure", "invalid SQN", and "GSM authentication unacceptable", during three consecutive authentication challenges. The authentication challenges shall be considered as consecutive only, if the authentication challenges causing the second and third authentication failure are received by the MS, while the timer T3318 or T3320 started after the previous authentication failure is running. The MS shall stop timer T3318, if the timer is running and the MS detects a lower layer failure, the network releases the PS signalling connection, the MS performs inter-system change to S1 mode, or the MS initiates a GPRS suspension procedure (see 3GPP TS 44.018[ None ] [84]). When it has been deemed by the MS that the source of the authentication challenge is not genuine (authentication not accepted by the MS), the MS shall behave as described in subclause 4.7.7.6.1. Figure 4.7.7a/1 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Authentication failure cause "MAC failure" or "GSM authentication unacceptable" (g) Authentication failure (GMM cause #19 "Synch failure"): The MS shall send an AUTHENTICATION AND CIPHERING FAILURE message, with the GMM cause "Synch failure", to the network and start the timer T3320. Furthermore, the MS shall stop any of the retransmission timers that are running (e.g. T3310, T3321, T3330 or T3317). Upon the first receipt of an AUTHENTICATION AND CIPHERING message from the MS with the GMM cause "synch failure", the network shall use the returned AUTS parameter from the authentication & ciphering failure parameter IE in the AUTHENTICATION AND CIPHERING FAILURE message, to re-synchronise. The re-synchronisation procedure requires the SGSN to delete all unused authentication vectors for that IMSI and obtain new vectors from the HLR. When re-synchronisation is complete, the network shall initiate the authentication & ciphering procedure. Upon receipt of the AUTHENTICATION AND CIPHERING REQUEST message, the MS shall stop timer T3320, if running. NOTE: Upon receipt of two consecutive AUTHENTICATION AND CIPHERING FAILURE messages from the MS with reject cause "synch failure", the network may terminate the authentication procedure by sending an AUTHENTICATION AND CIPHERING REJECT message. If the network is validated successfully (a new AUTHENTICATION AND CIPHERING REQUEST message is received which contains a valid SQN and MAC) while T3320 is running, the MS shall send the AUTHENTICATION AND CIPHERING RESPONSE message to the network and shall start any retransmission timers (i.e. T3310, T3321, T3330 or T3317), if they were running and stopped when the MS received the first failed AUTHENTICATION AND CIPHERING REQUEST message. If the MS receives the second AUTHENTICATION AND CIPHERING REQUEST message while T3320 is running and - the MAC value cannot be resolved; or - the message was received in Iu mode and contains a GSM authentication challenge, the MS shall proceed as specified in (f). If the SQN is invalid, the MS shall follow the procedure specified in this subclause (g), starting again from the beginning. The MS shall deem that the network has failed the authentication check and behave as described in subclause 4.7.7.6.1, if any of the following occurs: - the timer T3320 expires; - the MS detects any combination of the authentication failures: "MAC failure", "invalid SQN", and "GSM authentication unacceptable", during three consecutive authentication challenges. The authentication challenges shall be considered as consecutive only, if the authentication challenges causing the second and third authentication failure are received by the MS, while the timer T3318 or T3320 started after the previous authentication failure is running. The MS shall stop timer T3320, if the timer is running and the MS detects a lower layer failure, the network releases the PS signalling connection, the MS performs inter-system change to S1 mode, or the MS initiates a GPRS suspension procedure (see 3GPP TS 44.018[ None ] [84]). When it has been deemed by the MS that the source of the authentication challenge is not genuine (authentication not accepted by the MS), the MS shall behave as described in subclause 4.7.7.6.1. Figure 4.7.7b/1 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Authentication failure cause 'Synch failure’ Upon receipt of an AUTHENTICATION AND CIPHERING REJECT message, the UE shall perform the actions as specified in subclause 4.7.7.5. For items f and g: Depending on local requirements or operator preference for emergency bearer services, if the MS has a PDN connection for emergency bearer services established or is establishing such a PDN connection, the SGSN need not follow the procedures specified for the authentication failure specified in the present subclause and shall continue using the current security context, if any. The SGSN shall deactivate all non-emergency PDP contexts, if any, by initiating a PDP context deactivation procedure. If there is an ongoing session management procedure, the SGSN shall deactivate all non-emergency PDP contexts upon completion of the session management procedure. The network shall consider the MS to be attached for emergency bearer services only. If an MS has a PDN connection for emergency bearer services established or is establishing such a PDN connection when timer T3318 or T3320 expires, the MS shall not deem that the network has failed the authentication check and not behave as described in subclause 4.7.7.6.1. Instead the MS shall continue using the current security context, if any. The MS shall deactivate all non-emergency PDP contexts, if any, by initiating a PDP context deactivation procedure. If there is an ongoing session management procedure, the MS shall deactivate all non-emergency PDP contexts upon completion of the session management procedure. The MS shall start any retransmission timers (e.g. T3310, T3317, T3321 or T3330) if: - they were running and stopped when the MS received the AUTHENTICATION AND CIPHERING REJECT message and detected an authentication failure; and - the procedures associated with these timers have not yet been completed. The MS shall consider itself to be attached for emergency bearer services only. | 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.6 |
2,806 | 4.16.8.3 Intermediate Spending Limit Report Retrieval | This clause describes the signalling flow for the PCF to retrieve the status of additional policy counters available at the CHF or to unsubscribe from spending limit reporting. If the PCF provides the list of policy counter identifier(s), the CHF returns the policy counter status per policy counter identifier provided by the PCF. NOTE: If the CHF returns the status of all available policy counters some of these might not be relevant for a policy decision, (e.g. those used in a policy decision only when roaming). Figure 4.16.8.3.1: Intermediate Spending Limit Report Retrieval 1. The PCF determines that policy decisions depend on the status of additional policy counter(s) held at the CHF or that notifications of policy counter status changes for some policy counters are no longer required. 2. The PCF sends Nchf_SpendingLimitControl_Subscribe to the CHF, including the Subscription Correlation Id, the EventId "policy counter status change" and an updated list of policy counter identifier(s) as EventFilters, that overrides the previously stored list of policy counter identifier(s). The CHF responds to the Nchf_SpendingLimitControl_Subscribe service operation and provides as Event Information the policy counter status and optionally pending policy counter statuses and their activation times, per required policy counter identifier and stores or removes the PCF's subscription to spending limit reporting by comparing the updated list with the existing PCF subscriptions. If no policy counter identifier(s) was provided, the CHF returns the policy counter status, optionally including pending policy counter statuses and their activation times, for all policy counter(s), which are available for this subscriber and stores the PCF's subscription to spending limit reports of all policy counters provided to the PCF. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.16.8.3 |
2,807 | 5.3.3 List of forbidden PLMNs for attach in S101 mode | A UE supporting S101 mode shall store a list of "forbidden PLMNs for attach in S101 mode". The UE shall erase this list when the UE is switched off or when the USIM is removed. In S101 mode, the UE shall add to the "forbidden PLMNs for attach in S101 mode" list the PLMN identity provided with the indication from the lower layers to prepare for an S101 mode to S1 mode handover whenever an ATTACH REJECT message is received with the EMM cause #11 "PLMN not allowed", #12 "tracking area not allowed", #13 "roaming not allowed in this tracking area", #14 "EPS services not allowed in this PLMN", #15 "no suitable cells in tracking area", or #35 "Requested service option not authorized in this PLMN" as specified in clause 5.5.1.2.5. The maximum number of possible entries in the "forbidden PLMNs for attach in S101 mode" list is implementation dependent, but the list shall accommodate at least one PLMN identity. When the list is full and a new PLMN identity has to be inserted, the UE shall delete the oldest PLMN identity. | 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.3 |
2,808 | 7.1 High data rates and traffic densities | Several scenarios require the support of very high data rates or traffic densities of the 5G system. The scenarios address different service areas: urban and rural areas, office and home, and special deployments (e.g. massive gatherings, broadcast, residential, and high-speed vehicles). The scenarios and their performance requirements can be found in table 7.1-1. - Urban macro – The general wide-area scenario in urban area - Rural macro – The general wide-area scenario in rural area - Indoor hotspot – The scenario for offices and homes, and residential deployments. - Broadband access in a crowd – The scenario for very dense crowds, for example, at stadiums or concerts. In addition to a very high connection density the users want to share what they see and hear, putting a higher requirement on the uplink than the downlink. - Dense urban – The scenario for pedestrian users, and users in urban vehicles, for example, in offices, city centres, shopping centres, and residential areas. The users in vehicles can be connected either directly or via an onboard base station to the network. - Broadcast-like services – The scenario for stationary users, pedestrian users, and users in vehicles, for example, in offices, city centres, shopping centres, residential areas, rural areas and in high speed trains. The passengers in vehicles can be connected either directly or via an onboard base station to the network. - High-speed train – The scenario for users in trains. The users can be connected either directly or via an onboard base station to the network. - High-speed vehicle – The scenario for users in road vehicles. The users can be connected either directly or via an onboard base station to the network. - Airplanes connectivity – The scenario for users in airplanes. The users can be connected either directly or via an onboard base station to the network. Table 7.1-1 Performance requirements for high data rate and traffic density scenarios. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 7.1 |
2,809 | D.1 Determination of UE presence in Area of Interest by AMF | If the AMF has requested NG-RAN location reporting as specified in clause 4.10 for the Area Of Interest and UE is in CM-CONNECTED state, including RRC_CONNECTED and RRC_INACTIVE state, the AMF determines the UE presence in the Area of Interest as the reported value from the NG-RAN, as specified in clause D.2. In the case the UE is served by a MBSR, the AMF may consider the additional ULI provided by the NG-RAN node (as defined in clause 5.35A.6 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]) when determining the UE presence in Area of Interest. If the AMF has requested N2 Notification as specified in clause 4.8.3, the AMF determines the UE presence in Area Of Interest as follows, taking N2 Notification from NG-RAN into consideration: - IN: - if the UE is in CM-CONNECTED with RRC_CONNECTED state and if the last received User Location Information for the UE is inside the Area Of Interest service area; or NOTE 1: The above is valid e.g. under the condition that Area Of Interest border coincides with NG-RAN node service area border(s). - if the UE is in CM-CONNECTED and if the UE is inside a Registration Area which is completely contained within the Area Of Interest. - OUT: - if the UE is in CM-CONNECTED with RRC_CONNECTED state and if the last received User Location Information for the UE is outside the Area Of Interest; or NOTE 2: The above is valid e.g. under the condition that Area Of Interest border coincides with NG-RAN node service area border(s). - if the UE is in CM-CONNECTED and if UE is inside a Registration Area which does not contain any part of Area Of Interest. - UNKNOWN: if none of above conditions for IN or OUT is met. Otherwise, AMF determines the UE presence of Area Of Interest as follows: - IN: - if the UE is inside the Area Of Interest service area and if the UE is in CM-CONNECTED state; or - if the Area Of Interest service area is indicated as a RAN node identity and the Parameter Type with value "RAN timing synchronization status change event" is included and the UE has indicated a support for registration update procedure due to RAN timing synchronization status as described in clause 5.3.4.4 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] and the most recent N2 connection for the UE is via a RAN Node that is included in the Area Of Interest service area; or - if the Parameter Type with value "Adjust AoI based on RA" is included and the UE is inside a Registration Area which contains at least one Tracking Area that is contained within the Area Of Interest; or - if the UE is inside a Registration Area which is contained within the Area Of Interest. - OUT: - if the UE is outside the Area Of Interest in CM-CONNECTED and the Parameter Type with value "Adjust AoI based on RA" is not included; or - if the Area Of Interest service area is indicated as a RAN node identity and the Parameter Type with value "RAN timing synchronization status change event" is included and the UE has indicated a support for registration update procedure due to RAN timing synchronization status as described in clause 5.3.4.4 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] and the most recent N2 connection for the UE is via a RAN Node that is not included in the Area Of Interest service area; or - if UE is inside a Registration Area which does not contain any part of Area Of Interest. - UNKNOWN: if none of above conditions for IN or OUT is met. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | D.1 |
2,810 | 5.3.4.4.2 Tracking of IMS NEs generating charging information | Based on operator policy, each IMS NE for which the CTF is generating charging events, shall include its own address or specific NE identifier into the initial SIP request to be sent out within the trust domain. The final SIP response sent back by the last element of the trust domain shall contain the list of addresses and identifiers received within the initial SIP request. The list of addresses or identifiers received in the final response shall be included in the charging event generated by the CTF. | 3GPP TS 32.240 | Telecommunication management; Charging management; Charging architecture and principles | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 5.3.4.4.2 |
2,811 | 8.7.18 TDD FDD CA (1024QAM and up to 4 Rx supported) | The common parameters are specified in Table 8.7.18-1 for UE which is capable of supporting 1024QAM. Table 8.7.18-1: Common Test Parameters (TDD FDD CA) The UE capability for 1024QAM is signalled per band or per band combination, hence the SDR tests with the mixed modulation orders and the mixed receiver antenna numbers across CC-s are specified. For UE not supporting CA and supporting 1024QAM, the TB success rate shall be higher than 85% when PDSCH is scheduled with FRC in Table 8.7.18-4 according the UE capability. The maximum supported channel bandwidth and MIMO layer are configured during the test. For UE supporting CA and supporting 1024QAM at least on one CC for a supported CA configuration, the SDR requirements are specified as follows: - If UE is capable of supporting 256QAM, the TB success rate shall be higher than 85% on each CC when PDSCH-s are scheduled with FRC-s in Table 8.7.18-3 for the transmission with 256QAM and Table 8.7.18-4 for the transmission with 1024QAM according to the reported capability of supported modulation order for the determined CA configuration. - If UE is not capable of supporting 256QAM, the TB success rate shall be higher than 85% on each CC when PDSCH-s are scheduled with FRC-s in Table 8.7.18-2 for the transmission with 64QAM and Table 8.7.18-4 for the transmission with 1024QAM according to the reported capability of supported modulation order for the determined CA configuration. For UE supporting 1024 QAM, the SDR requirement with 64QAM and 256QAM only is not applicable. The CA configuration or band for single carrier, bandwidth combination or bandwidth for single carrier, modulation order on each CC and MIMO layer on each CC are determined by the following procedure. - Among all the supported CA configurations which support 1024QAM at least on one CC, select one set of {CA configuration or a band, bandwidth combination or bandwidth, modulation order on each CC, MIMO layer on each CC}, which leads to the largest equivalent aggregated bandwidth. The equivalent aggregated bandwidth is defined as Where N is the number of CCs, represents the MIMO layer, represents the bandwidths on each FDD CC and represents the bandwidths on each FDD CC, [ is the scaling factor according to the supported modulation order on each CC, where Mi = 0.75 is used if the maximum modulation order of CC i is 64QAM, Mi = 1 is used if the maximum modulation order of CC i is 256QAM, and Mi = 1.25 is used if the maximum modulation order of CC i is 1024QAM.] - When there are multiple sets of {CA configuration or a band, bandwidth combination or bandwidth, modulation order on each CC, MIMO layer on each CC} which can reach the same equivalent aggregated bandwidth, select one among the sets with the largest number of CCs supporting 1024QAM. - When there are multiple sets of {CA configuration or a band, bandwidth combination or bandwidth, modulation order on each CC, MIMO layer on each CC} which can reach the same equivalent aggregated bandwidth with the same number of CCs supporting 1024QAM, select one among the sets with the largest number of CCs supporting 4 layer. - The procedure applies also for the single carrier operating band instead of CA configuration, and bandwidth instead of bandwidth combination. The TB success rate for single carrier or on each CC for CA 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.18-2: Per-CC FRC for SDR test (TDD-FDD 64QAM) Table 8.7.18-3: Per-CC FRC for SDR test (TDD-FDD 256QAM) Table 8.7.18-4: Per-CC FRC for SDR test (TDD-FDD 1024QAM) | 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.18 |
2,812 | 5.1 General 5.1.2 General requirements | The UE shall: 1> process the received messages in order of reception by RRC, i.e. the processing of a message shall be completed before starting the processing of a subsequent message; NOTE: Network may initiate a subsequent procedure prior to receiving the UE's response of a previously initiated procedure. 1> within a clause execute the steps according to the order specified in the procedural description; 1> consider the term 'radio bearer' (RB) to cover SRBs, DRBs and MRBs unless explicitly stated otherwise; 1> set the rrc-TransactionIdentifier in the response message, if included, to the same value as included in the message received from the network that triggered the response message; 1> upon receiving a choice value set to setup: 2> apply the corresponding received configuration and start using the associated resources, unless explicitly specified otherwise; 1> upon receiving a choice value set to release: 2> clear the corresponding configuration and stop using the associated resources; 1> in case the size of a list is extended, upon receiving an extension field comprising the entries in addition to the ones carried by the original field (regardless of whether the network signals more entries in total); apply the following generic behaviour unless explicitly stated otherwise: 2> create a combined list by concatenating the additional entries included in the extension field to the original field while maintaining the order among both the original and the additional entries; 2> for the combined list, created according to the previous, apply the same behaviour as defined for the original field. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.1 |
2,813 | 10.2.6A.3 NPRS subframe configuration | On a NB-IoT DL carrier configured for NPRS transmission, an NB-IoT UE can assume NPRSs are transmitted in DL subframes configured by all higher layer parameters nprsBitmap, the NB-IoT carrier-specific subframe configuration period the NB-IoT-carrier-specific starting subframe offset and the number of consecutive downlink subframes where NPRS shall be transmitted. If frame structure type 2 is used, the UE shall not assume NPRSs are transmitted in special subframes. - If , and are not configured for an NB-IoT downlink carrier configured for NPRS transmission, an NB-IoT UE shall assume NPRSs are transmitted in downlink subframes configured by higher layer parameter nprsBitmap. - If nprsBitmap is not configured for an NB-IoT downlink carrier configured for NPRS transmission, an NB-IoT UE shall assume NPRSs are transmitted in downlink subframes configured by the higher layer parameters , and . - If the higher layer parameter operationModeInfoNPRS for the configured NB-IoT carrier is set to in-band, the higher layer parameters nprsBitmap shall be configured. - If , and are configured, the NPRS instances in the first subframe of the downlink subframes, shall satisfy . The NPRSs shall not be mapped to resource elements allocated to resource blocks of NPBCH, NPSS, NSSS, or SystemInformationBlock-Type1-NB regardless of their antenna port . | 3GPP TS 36.211 | Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation | RAN1 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 10.2.6A.3 |
2,814 | 5.38.4 Reject Paging Request | A Multi-USIM UE may set up a connection to respond to a page with a Reject Paging Indication to the network indicating that the UE does not accept the paging and requests to return to CM-IDLE state after sending this response, if both UE and network indicate the Reject Paging Request feature is supported to each other. Upon being paged by the network, the Multi-USIM UE in CM-IDLE state attempts to send a Service Request message to the paging network including the Reject Paging Indication as the response to the paging, unless it is unable to do so, e.g. due to UE implementation constraints. In addition to the Reject Paging Indication, the UE may include Paging Restriction Information as specified in clause 5.38.5 in the Service Request message, if supported by UE and network. NOTE: A Multi-USIM UE in RRC_INACTIVE state can decide to not initiate the RRC connection resumption procedure, e.g. when it decides not to respond to the paging message due to UE implementation constraints as specified in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [47] and TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [28]. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.38.4 |
2,815 | 6.3.7 Length of authentication parameters | The authentication key (K) shall have a length of 128 bits or 256 bits. NOTE: Examples of algorithm set for 3GPP authentication and key agreement functions allow either an authentication key K with only a length of 128 bits, or an authentication key K with a length of 128 bits or 256 bits. Depending on the chosen algorithm set, the operator may have the choice of the length of the authentication key K (128 bits or 256 bits). The random challenge () shall have a length of 128 bits. Sequence numbers (SQN) shall have a length of 48 bits. The anonymity key (AK) shall have a length of 48 bits. The authentication management field (AMF) shall have a length of 16 bits. The message authentication codes MAC in AUTN and MAC-S in AUTS shall have a length of 64 bits. The cipher key (CK) shall have a length of 128 bits. The integrity key (IK) shall have a length of 128 bits. The authentication response (RES) shall have a variable length of 4-16 octets. | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | 6.3.7 |
2,816 | 4.9.1 Number of incoming IRAT mobility events per LA | a) This measurement provides the number of incoming IRAT mobility events per E-UTRAN cell. This measurement is split into subcounters per LA. b) CC. c) On receipt by the eNB from UE of an RRCConnectionSetupComplete message in which the most significant bit of the “mmegi” in “RegisteredMME” IE is “0” (see TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8]). Each RRCConnectionSetupComplete message received is added to the relevant per LAI measurement. This definition is only applicable to the EUTRAN cells of which the adjacent (including overlaid) RAT is set the most significant bit of the <LAC> with zero. d) Each measurement is an integer value. e) RRC.IratIncMobility.LAI where LAI identifies the LAI of the RAT’s coverage the UE comes from. f) EUtranCellFDD EUtranCellTDD g) Valid for packet switched traffic h) EPS | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.9.1 |
2,817 | 8.18.1 RACH based SDT | The procedure for RACH based small data transmission in RRC Inactive is shown in Figure 8.18.1-1. Figure 8.18.1-1: RACH based Small Data Transmission in RRC Inactive state. 1. The UE in RRC Inactive sends the RRCResumeRequest message together with UL SDT data and/or UL SDT signalling. 2. The gNB-DU buffers the UL SDT data and/or UL SDT signalling. 3. The step 3 is as defined in step 4 in clause 8.6.2, including an indication of SDT access. The gNB-DU may also provide SDT assistance information. 4-5. If UE context is successfully retrieved as specified in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [2], the steps 4-5 are as defined in steps 6-7 in clause 8.9.6.2. The UL SDT data, if any, is forwarded to the gNB-CU-UP, and the UL signalling, if any, is forwarded to the gNB-CU-CP via the UL RRC MESSAGE TRANSFER message, in which any UL NAS PDU is delivered to AMF. NOTE 1: In case that full UE context is retrieved from another gNB-CU-CP as specified in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [2], the gNB-CU-CP first establishes the UE context in the gNB-CU-UP via the Bearer Context Setup procedure and F1-U UL TEIDs are retrieved before step 4. The BEARER CONTEXT SETUP REQUSET message may include an indication to suspend non-SDT bearers, and in this case, the BEARER CONTEXT MODIFICATION REQUEST message in step 6 does not include resume indication for SDT DRBs. NOTE 2: In case that only partial UE context for SDT including F1-U UL TEIDs is retrieved from another gNB-CU-CP as specified in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [2], the gNB-CU-CP uses those F1-U UL TEIDs for steps 4-5, and the subsequent steps 6-7 are not executed. The F1-U DL TEIDs received from the gNB-DU in step 5 should be forwarded to the other gNB-CU-CP, to be used for transferring of the DL SDT data. In addition, the UL SDT data, if any, is forwarded from the gNB-DU to the gNB-CU-UP of the other gNB-CU-CP for which the partial context is retrieved, and the UL signalling, if any, is forwarded from the gNB-CU-CP to the other gNB-CU-CP (the last serving gNB-CU-CP) via the XnAP RRC TRANSFER message. NOTE 3: The other gNB-CU-UP may need to buffer the UL SDT data if received before the SDT bearer(s) are resumed. 6. The gNB-CU-CP sends the BEARER CONTEXT MODIFICATION REQUEST message including an resume indication for SDT DRBs. The gNB-CU-CP also includes the F1-U DL TEIDs received from the gNB-DU in step 5. 7. The gNB-CU-UP responds with the BEARER CONTEXT MODIFICATION RESPONSE message. NOTE 4: void. Upon receiving the UE INACTIVITY NOTIFICATION message without SDT volume threshold crossed indication from the gNB-DU, the gNB-CU, if serving the UE and deciding to terminate the ongoing SDT procedure, shall transmit the UE CONTEXT RELEASE COMMAND message to the gNB-DU. If CG-SDT is (re-)configured, the gNB-CU may request the gNB-DU to keep CG-SDT configuration and resources in the UE CONTEXT RELEASE COMMAND message. NOTE 5: Upon receiving BSR from the UE, in case that UL SDT data size in the BSR is larger than the threshold configured from the gNB-CU-CP, the gNB-DU sends the UE INACTIVITY NOTIFICATION message with the SDT volume threshold crossed indication to the gNB-CU-CP. Upon receiving such indication, the gNB-CU-CP may terminate the ongoing SDT procedure, by sending the RRCResume message to move the UE to RRC_CONNECTED, or by sending the RRCRelease message to move the UE to RRC_INACTIVE. Upon receiving non-SDT data, the gNB-CU-UP shall send the DL DATA NOTIFICATION message to the gNB-CU-CP. The gNB-CU-CP shall terminate the ongoing SDT procedure as specified in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [2]. If the amount of the received DL SDT data is above the data size threshold configured by the gNB-CU-CP, the gNB-CU-UP shall send the DL DATA NOTIFICATION message with the SDT data size threshold crossed indication. The gNB-CU-CP may terminate the ongoing SDT procedure. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 8.18.1 |
2,818 | 7.3.9 Identification Response | The old SGSN/MME/AMF shall send an Identification Response message to the new MME/SGSN/AMF as a response to a previous Identification Request message over S3/S10/S16/N26 interface. Table 7.3.9-1 specifies the presence requirements and conditions of the IEs in the message. For Intra Domain Connection of RAN Nodes to Multiple CN Nodes, if an old SGSN within an SGSN pool receives an Identification Request message that contains the optional parameter Address for Control Plane, the old SGSN shall use this address as destination IP address of the Identification Response message. Possible Cause values are specified in Table 8.4-1. Message specific cause values are: "P-TMSI Signature mismatch" "User authentication failed" Only the Cause information element shall be included in the response if the Cause contains another value than "Request accepted". Table 7.3.9-1: Information Elements in an Identification 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 | 7.3.9 |
2,819 | 4.3.6.2 Processing AF requests to influence traffic routing and/or Service Function Chaining for Sessions not identified by an UE address | Figure 4.3.6.2-1: Processing AF requests to influence traffic routing and/or Service Function Chaining for Sessions not identified by an UE address NOTE 1: The 5GC functions used in this scenario are assumed to all belong to the same PLMN (HPLMN in non-roaming case or VPLMN in the case of a PDU Session in LBO mode). 0. The PCF(s) subscribe to modifications of AF requests (Data Set = Application Data; Data Subset = AF traffic influence request information, Data Key = S-NSSAI and/or DNN and/or Internal Group Identifier or SUPI) from the UDR. 1. To create a new request, the AF invokes a Nnef_TrafficInfluence_Create service operation. The content of this service operation (AF request) is defined in clause 5.2.6.7. The request contains also an AF Transaction Id. If it subscribes to events related with PDU Sessions the AF indicates also where it desires to receive the corresponding notifications (AF notification reporting information). To update or remove an existing request, the AF invokes a Nnef_TrafficInfluence_Update or Nnef_TrafficInfluence_Delete service operation providing the corresponding AF Transaction Id. The Nnef_TrafficInfluence_Create (initiated by target AF) or Nnef_TrafficInfluence_Update (initiated by source AF or target AF) service operation may be used for the case of AF instance change. If Nnef_TrafficInfluence_Update service operation is invoked, the NEF is required to update the subscription resource. The Nnef_TrafficInfluence_Update service operation may include an updated notification target address. The updated subscription resource is used by the target AF. NOTE 2: If the source AF transfers the application context to the target AF, then target AF may create new subscription via Nnef_TrafficInfluence_Create operation or update existing subscription via Nnef_TrafficInfluence_Update. However, whether and how the application context transfer is done is out of this specification. 2. The AF sends its request to the NEF. If the request is sent directly from the AF to the PCF, the AF reaches the PCF selected for the existing PDU Session by configuration or by invoking Nbsf_management_Discovery service. The NEF ensures the necessary authorization control, including throttling of AF requests and as described in clause 4.3.6.1, mapping from the information provided by the AF into information needed by the 5GC. 3. (in the case of Nnef_TrafficInfluence_Create or Update): The NEF stores the AF request information in the UDR (Data Set = Application Data; Data Subset, Data Key = AF Transaction Internal ID, S-NSSAI and DNN and/or Internal Group Identifier(s) and/or Subscriber Category(s) or SUPI). The Data Subset identifies whether the information relates to AF traffic influence request information for traffic routing or AF traffic influence request information for service function chaining, as described in Table 5.2.12.2.1-1. NOTE 3: Both the AF Transaction Internal ID and S-NSSAI and DNN and/or Internal Group Identifier(s) and/or Subscriber Category(s) or SUPI are regarded as Data Key when the AF request information are stored into the UDR, see Table 5.2.12.2.1-1. The Subscriber Category(s) is determined by NEF as described in clause 4.3.6.1. (in the case of Nnef_TrafficInfluence_delete): The NEF deletes the AF requirements in the UDR (Data Set = Application Data; Data Subset, Data Key = AF Transaction Internal ID). The Data Subset identifies whether the information relates to AF traffic influence request information for traffic routing or AF traffic influence request information for service function chaining. The NEF responds to the AF. 4. The PCF(s) that have subscribed to modifications of AF requests receive(s) a Nudr_DM_Notify notification of data change from the UDR. The Data Subset identifies whether the information relates to AF traffic influence request information for traffic routing or AF traffic influence request information for service function chaining. 5. The PCF determines if existing PDU Sessions are potentially impacted by the AF request. For each of these PDU Sessions, the PCF updates the SMF with corresponding new policy information about the PDU Session by invoking Npcf_SMPolicyControl_UpdateNotify service operation as described in steps 5 and 6 in clause 4.16.5. The PCF validates whether the SFC identifier (if available) corresponds to an authorized SFC for the AF based on local configuration. If the validation has succeeded the PCF maps the SFC identifier to the corresponding Traffic Steering Policy identifier (i.e. TSP ID). The PCF includes the Traffic Steering Policy ID(s) in the AF influence on traffic routing Enforcement Control information and/or N6-LAN Traffic Steering Enforcement Control information of the relevant PCC rule as defined in clause 6.3.1 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. The PCF also includes the Metadata in the N6-LAN Traffic Steering Enforcement Control information of the PCC rule when Metadata was provided by the AF. If the AF request includes a notification reporting request for UP path change, the PCF includes in the PCC rule(s) the information required for reporting the event, including the Notification Target Address pointing to the NEF or AF and the Notification Correlation ID containing the AF Transaction Internal ID. If the AF request includes an EAS Correlation indication or indication of traffic correlation, PCF includes in the PCC rule(s) an EAS Correlation indication or indication of traffic correlation and a Traffic Correlation ID corresponding to a set of UEs that AF request aims at, also if AF request includes a common EAS IP address or common DNAI for a set of UEs, PCC rule includes the common EAS IP address or common DNAI. In the case of AF influence on traffic routing, the PCF may, optionally, use service experience analytics per UP path, as defined in clause 6.4.3 of TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [50], to provide an updated list of DNAI(s) to the SMF. The PCF may use the "Subscriber categories" as defined in "PDU Session policy control subscription information" in table 6.2-2 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20] to determine whether the PDU Session is impacted by the AF request. 6. When the updated policy information about the PDU Session is received from the PCF, the SMF may take appropriate actions to reconfigure the User plane of the PDU Session. In the case of AF influence on traffic routing, examples of actions are: - The SMF may consider service experience analytics and/or DN Performance analytics per UP path (i.e. including UPF and/or DNAI and/or AS instance) as defined in clauses 6.4.3 and 6.14.3, respectively, of TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [50] before taking any actions. - Determining a target DNAI. - Determining if a common DNAI needs to be used as a target DNAI. - Adding, replacing or removing a UPF in the data path to e.g. act as an UL CL or a Branching Point e.g. as described in clause 4.3.5. - Allocate a new Prefix to the UE (when IPv6 multi-Homing applies). - Updating the UPF in the target DNAI with AF influence on traffic routing control parameters as described in clause 5.6.7.1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. - Subscribe to notifications from the AMF for an Area of Interest via Namf_EventExposure_Subscribe service operation. - Determining whether to relocate PSA UPF considering the user plane latency requirements provided by the AF (see clause 6.3.6 of TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [74]). When the updated policy information about the PDU Session is received from the PCF, the SMF may take appropriate actions to assist the EAS discovery and re-discovery for PDU Session with Session Breakout connectivity model such as: - Retrieve the EAS deployment information as defined in clause 6.2.3.4.1 of TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [74]. - Providing DNS message handling rule to forward DNS messages of the UE and/or report when detecting DNS messages as defined in clause 6.2.3.2.2 of TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [74]. In the case of AF influence on Service Function Chaining, the SMF may take appropriate actions to enforce the N6-LAN traffic steering control: - Provide N6-LAN traffic steering control parameters to UPF as described in clause 5.6.16 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. 7. The SMF may decide whether it is required to send the target DNAI to the AMF for triggering SMF/I-SMF (re)selection and then inform the target DNAI information for the current PDU session or for the next PDU session to AMF via Nsmf_PDUSession_SMContextStatusNotify service operation. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.3.6.2 |
2,820 | 4.13.4.2 Emergency Services Fallback | The call flow in Figure 4.13.4.2-1 describes the procedure for emergency services fallback. Figure 4.13.4.2-1: Emergency Services Fallback 1. UE camps on E-UTRA or NR cell in the 5GS (in either CM-IDLE or CM-CONNECTED state). 2. UE has a pending IMS emergency session request (e.g. voice) from the upper layers. 3. If the AMF has indicated support for emergency services using fallback via the Registration Accept message for the current RAT, the UE sends a Service Request message indicating that it requires emergency services fallback. The UE is not required to include the PDU Sessions that are not relevant for the emergency service in the List Of PDU Sessions to be Activated in the Service Request for the emergency service. NOTE 1: If the UE includes PDU Sessions to be Activated in the Service Request for the emergency service, it will delay the Emergency Services Fallback procedure. 4. 5GC triggers a request for Emergency Services Fallback by executing an NG-AP procedure in which it indicates to NG-RAN that this is a fallback for emergency services. The AMF based on the support of Emergency Services in EPC or 5GC may indicate the target CN for the RAN node to know whether inter-RAT fallback or inter-system fallback is to be performed. When AMF initiates Redirection for UE(s) that have been successfully authenticated, AMF includes the security context in the request to trigger fallback towards NG-RAN. 5. Based on the target CN if indicated in message 4 or otherwise based on the RAN configuration, one of the following procedures is executed by NG-RAN: 5a. NG-RAN initiates handover (see clause 4.9.1.3) or redirection to a 5GC-connected E-UTRAN cell, if UE is currently camped on NR. 5b. NG-RAN initiates handover (see clause 4.11.1.2.1) or redirection to E-UTRAN connected to EPS. NG-RAN uses the security context provided by the AMF to secure the redirection procedure. If the redirection procedure is used either in 5a or 5b the target CN type (EPC or 5GC) is also conveyed to the UE in order to be able to perform the appropriate NAS procedures (S1 or N1 Mode). The UE uses the emergency indication in the RRC message as specified in clause 6.2.2 of TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [16] and E-UTRAN provides the emergency indication to AMF (during Registration triggered by step 5a) and MME (during Tracking Area Update triggered by step 5b). Both the Registration and the Tracking Area Update requests should contain Follow-on request and active flag respectively to indicate that the UE has "user data pending". For the handover procedure used in step 5b see clause 4.11.1.2.1, step 1. In step 5b, if the MME does not support emergency services for that UE, the MME should act such that the call for emergency service is likely to succeed promptly, e.g. if the UE successfully completed a combined TA/LA Update with the network, by using the CSFB procedures specified in TS 23.272[ Circuit Switched (CS) fallback in Evolved Packet System (EPS); Stage 2 ] [61]. NOTE 2: If such a combined TA/LA Update is not successful, or the UE did not request a combined update, then, as specified in TS 23.167[ IP Multimedia Subsystem (IMS) emergency sessions ] [28], the UE autonomously selects a RAT that may (but which might not) support the CS domain. 6. After handover or redirection to the target cell the UE establishes a PDU Session / PDN connection for IMS emergency services and performs the IMS procedures for establishment of an IMS emergency session (e.g. voice) as defined in TS 23.167[ IP Multimedia Subsystem (IMS) emergency sessions ] [28]. At least for the duration of the emergency voice call, the E-UTRAN connected to EPC is configured to not trigger any handover to 5GS and the target NG-RAN is configured to not trigger inter NG-RAN handover back to source NG-RAN. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.13.4.2 |
2,821 | 4.2.8.5.4 Reference Points | The Yt' and Yw reference points are both outside the scope of the 3GPP specifications. The Yt' reference point transports WLAN messages (e.g. IEEE 802.11 messages), while the Yw reference point: - Shall be able to transport authentication messages between the TNAP and the TWIF for enabling authentication of a N5CW device; - Shall allow the N5CW device to request and receive IP configuration from the TWIF, including an IP address, e.g. with DHCP. - Shall support the transport of user-plane traffic for the N5CW device. The N1, N2 and N3 reference points are the same reference points defined in clause 4.2.7. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.2.8.5.4 |
2,822 | – SL-BWP-Config | The IE SL-BWP-Config is used to configure the UE specific NR sidelink communication/discovery/positioning on one particular sidelink bandwidth part. SL-BWP-Config information element -- ASN1START -- TAG-SL-BWP-CONFIG-START SL-BWP-Config-r16 ::= SEQUENCE { sl-BWP-Id BWP-Id, sl-BWP-Generic-r16 SL-BWP-Generic-r16 OPTIONAL, -- Need M sl-BWP-PoolConfig-r16 SL-BWP-PoolConfig-r16 OPTIONAL, -- Need M ..., [[ sl-BWP-PoolConfigPS-r17 SetupRelease {SL-BWP-PoolConfig-r16} OPTIONAL, -- Need M sl-BWP-DiscPoolConfig-r17 SetupRelease {SL-BWP-DiscPoolConfig-r17} OPTIONAL -- Need M ]], [[ sl-LBT-FailureRecoveryConfig-r18 SetupRelease { SL-LBT-FailureRecoveryConfig-r18 } OPTIONAL, -- Need M sl-StartingSymbolFirst-r18 ENUMERATED {sym0, sym1, sym2, sym3, sym4, sym5, sym6} OPTIONAL, -- Need M sl-StartingSymbolSecond-r18 ENUMERATED {sym3, sym4, sym5, sym6, sym7} OPTIONAL, -- Need M sl-TransmissionStructureForPSCCHandPSSCH-r18 ENUMERATED {contigousRB, interlaceRB} OPTIONAL, -- Need M sl-GapOfAdditionalSSSB-Occasion-r18 INTEGER (0..639) OPTIONAL, -- Need M sl-AbsoluteFrequencySSB-NonAnchorList-r18 SEQUENCE (SIZE (1.. maxSL-NonAnchorRBsets)) OF ARFCN-ValueNR OPTIONAL, -- Need M sl-NumOfSSS-Brepetition-r18 SEQUENCE (SIZE (1..5)) OF INTEGER (2..9) OPTIONAL, -- Need M sl-CPE-StartingPositionS-SSB-r18 INTEGER (1..9) OPTIONAL, -- Need M sl-CWS-ForPsschWithoutHarqAck-r18 ENUMERATED {t1, t8, t16, t32, infinity} OPTIONAL, -- Need M sl-NumOfAdditionalSSSBOccasion-r18 INTEGER (0..4) OPTIONAL, -- Need M sl-SSSBPowerOffsetOfAnchorRBSet-r18 ENUMERATED {value1, value2} OPTIONAL, -- Need M sl-RBSetConfigList-r18 SEQUENCE (SIZE (1..5)) OF SL-RBSetConfig-r18 OPTIONAL, -- Need M sl-BWP-PoolConfigA2X-r18 SetupRelease {SL-BWP-PoolConfig-r16} OPTIONAL, -- Need M sl-BWP-PRS-PoolConfig-r18 SetupRelease {SL-BWP-PRS-PoolConfig-r18} OPTIONAL -- Need M ]] } SL-BWP-Generic-r16 ::= SEQUENCE { sl-BWP-r16 BWP OPTIONAL, -- Need M sl-LengthSymbols-r16 ENUMERATED {sym7, sym8, sym9, sym10, sym11, sym12, sym13, sym14} OPTIONAL, -- Need M sl-StartSymbol-r16 ENUMERATED {sym0, sym1, sym2, sym3, sym4, sym5, sym6, sym7} OPTIONAL, -- Need M sl-PSBCH-Config-r16 SetupRelease {SL-PSBCH-Config-r16} OPTIONAL, -- Need M sl-TxDirectCurrentLocation-r16 INTEGER (0..3301) OPTIONAL, -- Need M ... } -- TAG-SL-BWP-CONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
2,823 | D.3.7.3 Execution phase | Figure D.3.7.3-1: E-UTRAN to GERAN A/Gb mode Inter RAT HO, execution phase The source eNodeB continues to receive downlink and uplink user plane PDUs. 1. The Source MME completes the preparation phase towards Source eNodeB by sending the message Handover Command (Target BSS to Source BSS Transparent Container (PS Handover Command with RN part and EPC part), Bearers Subject to Data Forwarding List). The "Bearers Subject to Data forwarding list" may be included in the message and it shall be a list of 'Address(es) and TEID(s) for user traffic data forwarding' received from target side in the preparation phase (Forward Relocation Response message (Step 8)). Source eNodeB initiate data forwarding for the bearers specified in the "Bearers Subject to Data Forwarding List". The data forwarding goes directly to target SGSN decided in the preparation phase. 2. The Source eNodeB will give a command to the UE to handover to the Target Access System via the message HO from E-UTRAN Command. This message includes a transparent container including radio aspect parameters that the Target BSS has set-up in the preparation phase (RN part). This message also includes the XID and IOV-UI parameters received from the Target SGSN (EPC part). Upon the reception of the HO from E-UTRAN Command message containing the Handover Command message, the UE shall associate its bearer IDs to the respective PFIs based on the relation with the NSAPI and shall suspend the uplink transmission of the user plane data. NOTE 1: This step is unmodified compared to clause 5.5.2.3.3. The target SGSN acts as the new SGSN. 3. If the PLMN has configured Secondary RAT usage data reporting and the source eNodeB has Secondary RAT usage data to report, the eNodeB sends the RAN Usage data report message (Secondary RAT usage data) to the MME. Since the handover is an inter-RAT handover, the MME continues with the Secondary RAT usage data reporting procedure as in clause 5.7A.3. The reporting procedure in clause 5.7A.3 is only performed if PGW secondary RAT usage reporting is active. NOTE 2: The source eNodeB does not send any RAN context towards the target BSS. 4. The MS executes the handover according to the parameters provided in the message delivered in step 2. The procedure is the same as in step 6 in clause 5.1.4.2 in TS 43.129[ None ] [8] with the additional function of association of the received PFI and existing RAB Id related to the particular NSAPI as described in clause 4.4.1 in TS 43.129[ None ] [8]. The UE locally deactivates ISR by setting its TIN from "RAT-related TMSI" to "GUTI", if any EPS bearer context activated after the ISR was activated in the UE exists. 5/7. After accessing the cell using access bursts and receiving timing advance information from the BSS in step 2, the MS processes the NAS container and then sends one XID Response message to the new SGSN. The MS sends this message immediately after receiving the Packet Physical Information message containing the timing advance or, in the synchronised network case, immediately if the PS Handover Access message is not required to be sent (see clause 6.2 in TS 43.129[ None ] [8]). Upon sending the XID Response message, the MS shall resume the user data transfer only for those NSAPIs for which there are radio resources allocated in the target cell. For NSAPIs using LLC ADM for which radio resources were not allocated in the target cell the MS may request for radio resources using the legacy procedures. NOTE 3: If the new SGSN indicated Reset (i.e. reset to default parameters) in the NAS container for PS HO included in the Handover from UTRAN Command message (UTRAN) or the Handover from GERAN Iu Command message, in order to avoid collision cases the mobile station may avoid triggering XID negotiation for any LLC SAPI used in LLC ADM, but wait for the SGSN to do so (see step 12). In any case the mobile station may avoid triggering XID negotiation for any LLC SAPI used in LLC ABM, but wait for the SGSN to do so (see step 12a). NOTE 4: This step is unmodified compared to pre-Rel-8. The message "HO from E-UTRAN Command" acts as the "Handover from UTRAN Command" message (UTRAN) or the "Handover from GERAN Iu Command" message. 6. Upon reception of the first correct RLC/MAC block (sent in normal burst format) from the MS the target BSS sends a PS Handover Complete (Local TLLI, Handover Complete Status) message to inform the new SGSN that the MS has arrived in the target cell. Each uplink N-PDU received by the new SGSN via the target BSS is then forwarded directly to the GGSN. A timer in source MME is started to supervise when resources in Source eNodeB and Source Serving GW shall be released. NOTE 5: This step is unmodified compared to pre-Rel-8. The PDN GW acts as the GGSN. 8. Upon receiving the PS Handover Complete message, the new SGSN send a Forward Relocation Complete message to the old SGSN to indicate completion of the PS handover procedures. The old SGSN responds with a Forward Relocation Complete Acknowledge message. For all bearers that were not included in the Forward Relocation Request message sent in step 3, the old SGSN now releases them by sending a Delete Bearer Command to the SGW, or, the appropriate message to the SCEF. NOTE 6: This step is unmodified compared to pre-Rel-8. The Source MME acts as the old SGSN. 9/11. The new SGSN sends an Update PDP Context Request (new SGSN Address, TEID, QoS Negotiated) message to the GGSN concerned. The GGSN updates the PDP context fields and returns an Update PDP Context Response (TEID) message. From now on the GGSN sends new incoming downlink IP packets to the new SGSN instead of to the old SGSN. The PDN GW shall include a Charging Id to be used at the SGSN as the Charging ID for reporting usage for this PDP context. The PDN GW shall include the Charging Id in the offline charging data. NOTE 7: This step is unmodified compared to pre-Rel-8. The Source MME acts as the old SGSN, and the PDN GW acts as the GGSN. 12. If the new SGSN indicated Reset (i.e. reset to default parameters) in the NAS container for PS HO included in the Handover from UTRAN Command message (UTRAN) or the Handover from GERAN Iu Command message, then on receipt of the PS Handover Complete the new SGSN initiates an LLC/SNDCP XID negotiation for each LLC SAPI used in LLC ADM. In this case if the SGSN wants to use the default parameters, it shall send an empty XID Command. If the new SGSN indicated 'Reset to the old XID parameters' in the NAS container for PS HO, no further XID negotiation is required for LLC SAPIs used in LLC ADM only. NOTE 8: This step is unmodified compared to pre-Rel-8. The message "HO from E-UTRAN Command" acts as the "Handover from UTRAN Command" message (UTRAN) or the "Handover from GERAN Iu Command" message. 12a. The new SGSN (re-)establishes LLC ABM for the PDP contexts which use acknowledged information transfer. During the exchange of SABM and UA the SGSN shall perform LLC/SNDCP XID negotiation. 13. The MS sends a Routing Area Update Request (Old P-TMSI, Old RAI, Old P-TMSI signature, Update Type) message to the new SGSN informing it that the source cell belongs to a new routing area. The MS shall send this message immediately after message 5, see TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [7]. The new SGSN knows that a handover has been performed for this MS and can therefore exclude the SGSN context procedures which normally are used within the RA Update procedure. For a MS supporting CIoT EPS Optimisations, the MS uses the PDP context status information in the RAU Accept to identify any non-transferred bearers that it shall locally release. For further descriptions of the Routing Area Update procedure see TS 43.129[ None ] [8], clauses 5.5.2.3 and 5.6.1.1.1. NOTE 9: The RAU procedure is performed regardless if the routing area is changed or not, as specified by TS 43.129[ None ] [8]. 14. When the timer started at step 8 expires, the source MME sends a Release Resources message to the source eNodeB. The Source eNodeB releases its resources related to the UE. Additionally, the source MME deletes the EPS bearer resources by sending Delete Session Request (Cause, Operation Indication, Secondary RAT usage data) messages to the Serving GW. The operation Indication flag is not set, that indicates to the Serving GW that it shall not initiate a delete procedure towards the PDN GW. Secondary RAT usage data was included if it was received in step 3a. The Serving GW acknowledges with Delete Session Response (Cause) messages. If ISR is activated then the cause indicates to the old Serving GW that the old Serving GW shall delete the bearer resources on the other old CN node by sending Delete Bearer Request message(s) to that CN node. 15. When the timer started in step 8 expires and if resources for indirect forwarding have been allocated then they are released. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | D.3.7.3 |
2,824 | 5.4.3.2 NAS security mode control initiation by the network | The MME initiates the NAS security mode control procedure by sending a SECURITY MODE COMMAND message to the UE and starting timer T3460 (see example in figure 5.4.3.2.1). The MME shall reset the downlink NAS COUNT counter and use it to integrity protect the initial SECURITY MODE COMMAND message if the security mode control procedure is initiated: - to take into use the EPS security context created after a successful execution of the EPS authentication procedure; - upon receipt of TRACKING AREA UPDATE REQUEST message including a GPRS ciphering key sequence number IE, if the MME wishes to create a mapped EPS security context (i.e. the type of security context flag is set to "mapped security context" in the NAS key set identifier IE included in the SECURITY MODE COMMAND message). The MME shall send the SECURITY MODE COMMAND message unciphered, but shall integrity protect the message with the NAS integrity key based on KASME or mapped K'ASME indicated by the eKSI included in the message. The MME shall set the security header type of the message to "integrity protected with new EPS security context". The MME shall create a locally generated KASME and send the SECURITY MODE COMMAND message including a KSI value in the NAS key set identifier IE set to "000" and EIA0 and EEA0 as the selected NAS security algorithms only when the security mode control procedure is initiated: - during an attach procedure for emergency bearer services if no shared EPS security context is available; - during an attach procedure for access to RLOS if no valid EPS security context is available; - during a tracking area updating procedure for a UE that has a PDN connection for emergency bearer services if no shared EPS security context is available; - during a tracking area updating procedure for a UE that has a PDN connection for access to RLOS if no valid EPS security context is available; - during a service request procedure for a UE that has a PDN connection for emergency bearer services if no shared EPS security context is available; - during a service request procedure for a UE that has a PDN connection for access to RLOS if no valid EPS security context is available; - after a failed authentication procedure for a UE that has a PDN connection for emergency bearer services or that is establishing a PDN connection for emergency bearer services, if continued usage of a shared security context is not possible; or - after a failed authentication procedure for a UE that has a PDN connection for access to RLOS or that is establishing a PDN connection for access to RLOS, if continued usage of a valid security context is not possible. The UE shall process a SECURITY MODE COMMAND message including a KSI value in the NAS key set identifier IE set to "000" and EIA0 and EEA0 as the selected NAS security algorithms and, if accepted, create a locally generated KASME when the security mode control procedure is initiated: - during an attach procedure for emergency bearer services; - during an attach procedure for access to RLOS; - during a tracking area updating procedure when the UE has a PDN connection for emergency bearer services; - during a tracking area updating procedure when the UE has a PDN connection for access to RLOS; - during a service request procedure when the UE has a PDN connection for emergency bearer services; - during a service request procedure when the UE has a PDN connection for access to RLOS; - after an authentication procedure when the UE has a PDN connection for emergency bearer services or is establishing a PDN connection for emergency bearer services; or - after an authentication procedure when the UE has a PDN connection for access to RLOS or is establishing a PDN connection for access to RLOS. NOTE 1: The process for creation of the locally generated KASME by the MME and the UE is implementation dependent. Upon receipt of a TRACKING AREA UPDATE REQUEST message including a GPRS ciphering key sequence number IE, if the MME does not have the valid current EPS security context indicated by the UE, the MME shall either: - indicate the use of the new mapped EPS security context to the UE by setting the type of security context flag in the NAS key set identifier IE to "mapped security context" and the KSI value related to the security context of the source system; or - set the KSI value "000" in the NAS key set identifier IE if the MME sets EIA0 and EEA0 as the selected NAS security algorithms for a UE that has a PDN connection for emergency bearer services. While having a current mapped EPS security context with the UE, if the MME wants to take the native EPS security context into use, the MME shall include the eKSI that indicates the native EPS security context in the SECURITY MODE COMMAND message. The MME shall include the replayed security capabilities of the UE (including the security capabilities with regard to NAS, RRC and UP (user plane) ciphering as well as NAS and RRC integrity, and other possible target network security capabilities, i.e. UTRAN/GERAN if the UE included them in the message to network), the replayed nonceUE when creating a mapped EPS security context and if the UE included it in the message to the network, the selected NAS ciphering and integrity algorithms and the Key Set Identifier (eKSI). If the MME supports handling of UE additional security capabilities and the UE included a UE additional security capability IE in the message to the network, the MME shall include the replayed additional security capabilities of the UE. The MME shall include both the nonceMME and the nonceUE when creating a mapped EPS security context during inter-system change from A/Gb mode to S1 mode or Iu mode to S1 mode in EMM-IDLE mode. The MME may initiate a SECURITY MODE COMMAND in order to change the NAS security algorithms for a current EPS security context already in use. The MME re-derives the NAS keys from KASME with the new NAS algorithm identities as input and provides the new NAS algorithm identities within the SECURITY MODE COMMAND message. The MME shall set the security header type of the message to "integrity protected with new EPS security context". If, during an ongoing attach or tracking area updating procedure, the MME is initiating a SECURITY MODE COMMAND (i.e. after receiving the ATTACH REQUEST or TRACKING AREA UPDATE REQUEST message, but before sending a response to that message) and the ATTACH REQUEST or TRACKING AREA UPDATE REQUEST message is received without integrity protection or does not successfully pass the integrity check at the MME, the MME shall calculate the HASHMME of the entire plain ATTACH REQUEST or TRACKING AREA UPDATE REQUEST message as described in 3GPP TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [19] and shall include the HASHMME in the SECURITY MODE COMMAND message. Additionally, the MME may request the UE to include its IMEISV in the SECURITY MODE COMPLETE message. NOTE 2: The AS and NAS security capabilities will be the same, i.e. if the UE supports one algorithm for NAS, the same algorithm is also supported for AS. If: - the NAS security mode control procedure is initiated during an ongoing attach procedure in WB-S1 mode; - the network supports RACS; - the UE has set the RACS bit to "RACS supported" in the UE network capability IE of the ATTACH REQUEST message; and - the UE has set the URCIDA bit to "UE radio capability ID available" in the UE radio capability ID availability IE of the ATTACH REQUEST message, then the MME shall request the UE to include its UE radio capability ID in the SECURITY MODE COMPLETE message. If: - the NAS security mode control procedure is initiated during an ongoing tracking area updating procedure in WB-S1 mode; - the network supports RACS; - the UE has set the RACS bit to "RACS supported" in the UE network capability IE of the TRACKING AREA UPDATE REQUEST message; and - the UE has set the URCIDA bit to "UE radio capability ID available" in the UE radio capability ID availability IE of the TRACKING AREA UPDATE REQUEST message, then the MME may request the UE to include its UE radio capability ID in the SECURITY MODE COMPLETE message. If: - the NAS security mode control procedure is initiated during an ongoing tracking area updating procedure in WB-S1 mode; - the network supports RACS; - the UE has set the RACS bit to "RACS supported" in the UE network capability IE of the TRACKING AREA UPDATE REQUEST message; - the UE has set the URCIDA bit to "UE radio capability ID available" in the UE radio capability ID availability IE of the TRACKING AREA UPDATE REQUEST message; and - no UE radio capability ID is available in the UE context in the MME, then the MME shall request the UE to include its UE radio capability ID in the SECURITY MODE COMPLETE message. Figure 5.4.3.2.1: Security mode control procedure | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.4.3.2 |
2,825 | 5.10.1.3 Multicast MCCH information validity and notification of changes | Change of multicast MCCH information only occurs at specific radio frames, i.e. the concept of a modification period is used. Within a modification period, the same multicast MCCH information may be transmitted a number of times, as defined by its scheduling (which is based on a repetition period). When the network changes (some of) the multicast MCCH information, it notifies the UEs about the change starting from the beginning of the multicast MCCH modification period via PDCCH which schedules the multicast MCCH in every repetition in that modification period. Upon receiving a change notification, a UE receiving MBS multicast service(s) in RRC_INACTIVE acquires the new multicast MCCH information starting from the same slot. The UE applies the previously acquired multicast MCCH information until the UE acquires the new multicast MCCH information. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.10.1.3 |
2,826 | C.4.3.2 Network specific identifier-based SUPI | The following test data set corresponds to SUCI computation in the UE for network specific identifier-based SUPI and ECIES Profile A. SUPI is: [email protected] ECIES test data The ECIES Scheme Output is computed in the UE as defined in Figure C.3.2-1 of clause C.3.2 with the following data Home Network Private Key: 'C53C22208B61860B06C62E5406A7B330C2B577AA5558981510D128247D38BD1D' Home Network Public Key: '5A8D38864820197C3394B92613B20B91633CBD897119273BF8e4A6f4EEC0A650' Eph. Private Key: 'BE9EFF3E9F22A4B42A3D236E7A6C500B3F2E7E0C7449988BA800D664BF4FCD97' Eph. Public Key: '977D8B2FDAA7B64AA700D04227D5B440630EA4EC50F9082273A26BB678C92222' Eph. Shared Key: '511C1DF473BB88317F923501F8BA944FD3B667D25699DCB552DBCEF60BBDC56D' Eph. Enc. Key: 'FE77B87D87F40428EDD71BCA69D79059' Plaintext block: '766572796C6F6E67757365726E616D6531' Cipher-text vaue: '8E358A1582ADB15322C10E515141D2039A' Eph. mac key: 'D87B69F4FE8CD6B211264EA5E69F682F151A82252684CDB15A047E6EF0595028' MAC-tag value: '12E1D7783A97F1AC' Scheme Output: ecckey977D8B2FDAA7B64AA700D04227D5B440630EA4EC50F9082273A26BB678C92222.cip8E358A1582ADB15322C10E515141D2039A.mac12E1D7783A97F1AC | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | C.4.3.2 |
2,827 | 10.18.3 Conditional PSCell addition or change failure | One of the functions of self-optimization for CPAC is to detect CPAC failures that occur due to Too late CPC execution or Too early CPC/CPA execution, or CPC/CPA execution to wrong PSCell. These problems are defined as follows: - Too Late CPC Execution: UE receives CPC configuration, while a SCG failure occurs before CPC execution condition is satisfied; a suitable PSCell different from source PSCell is found based on the measurements reported from the UE. - Too Early CPC/CPA Execution: CPC/CPA execution is not successful or an SCG failure occurs shortly after a successful CPC/CPA execution; in case of CPC, the source PSCell is still the suitable PSCell based on the measurements reported from the UE; in case of CPA, no suitable PSCell is found based on the measurements reported from the UE. - CPC/CPA Execution to wrong PSCell: CPC/CPA execution is not successful or an SCG failure occurs shortly after a successful CPC/CPA execution; a suitable PSCell different from the source PSCell or the target PSCell is found based on the measurements reported from the UE. There are two sub-cases: - if the suitable PSCell is one of the candidate target PSCells provided by the node initiating the CPC or by the MN initiating the CPA, but not one of the candidate PSCells selected by the candidate or target SN, it is wrong target PSCell selection at the candidate or target SN; - else, it is wrong candidate PSCell list selection at the node initiating the CPC or at the MN initiating the CPA. In the definition above, the "successful CPC/CPA execution" refers to the UE state, namely the successful completion of the RA procedure. The MN performs the initial analysis when SCGFailureInformation is received from the UE. In the first step, MN verifies whether intra-SN PSCell change has been triggered in the last serving SN. In case the intra-SN PSCell change has been triggered in the last serving SN, the MN forwards the SCG Failure Information Report message to this last serving SN, which performs the final root cause analysis. In case of no intra-SN PSCell change, the MN determines the type of PSCell addition/change, e.g., whether it is CPA or CPC in case of conditional mobility, if CPC whether it is MN initiated or SN initiated. For CPA or MN initiated CPC, if the suitable PSCell is one of the candidate PSCells provided by the MN at CPAC preparation, but not one of the candidate PSCells selected by the candidate or target SN, MN sends the SCG Failure Information Report messageto the candidate or target SN, which perform the final MRO related optimisation. Otherwise, the MN performs the final MRO related optimisation. For SN initiated CPC, the MN sends the SCG Failure Information Report messageto source SN, and source SN performs root cause analysis. If the suitable PSCell is one of the candidate PSCells provided by the source SN, but not one of the candidate PSCells selected by the candidate or target SN, the source SN indicates to MN that the root cause of the SCG failure may have occurred in the other nodes. MN then sends the SCG Failure Information Report messageto the candidate or target SN. Otherwise, the source SN performs the final MRO related optimisation. | 3GPP TS 37.340 | Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Overall Description; Stage-2 | RAN2 | 3GPP Series : 37 , Multiple radio access technology aspects | 10.18.3 |
2,828 | 28.15.5 NAI format for SUCI containing a GCI | The SUCI containing a GCI shall take the form of a Network Access Identifier (NAI). 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 SUPI (see clause 28.15.2). The username part of the NAI shall be encoded as specified for the null-scheme in clause 28.7.3, i.e. it shall take the following form: type3.rid0.schid0.userid<username> where the username shall be encoded as the username part of the SUPI (see clause 28.15.2). EXAMPLE 1: type3.rid0.schid0.userid00-00-5E-00-53-00@5gc.mnc012.mcc345.3gppnetwork.org EXAMPLE 2: [email protected] | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 28.15.5 |
2,829 | 7.5.1 Common procedures | When on receipt of a message, a) an "imperative message part" error; or b) a "missing mandatory IE" error is diagnosed or when a message containing: a) a syntactically incorrect mandatory IE; b) an IE with an IEI unknown in the message, but encoded as "comprehension required" (see 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [11]); or c) an out of sequence IE encoded as "comprehension required" (see 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [11]) is received, the UE shall proceed as follows: If the message is not one of the messages listed in the UE procedures in subclause 7.5.3, item a), b) or c), the UE shall return a status message (5GMM STATUS or 5GSM STATUS depending on the EPD) with cause #96 "invalid mandatory information"; the network shall proceed as follows: If the message is not one of the messages listed in the network procedures in subclause 7.5.3, item a), b) or c), the network shall either: 1) try to treat the message (the exact further actions are implementation dependent); or 2) ignore the message except that it should return a status message (5GMM STATUS or 5GSM STATUS depending on the EPD) with cause #96 "invalid mandatory information". | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 7.5.1 |
2,830 | 4.11 System interworking procedures with EPC 4.11.0 General | Clause 4.11 includes the following: - Procedures for interworking with EPS based on N26 interface (clause 4.11.1) and interworking without N26 interface (clause 4.11.2); - Handover procedures between EPS and 5GC-N3IWF (clause 4.11.3), handover procedures between EPS and 5GC-TNGF (clause 4.11.3a) and handover procedures between EPC/ePDG and 5GS (clause 4.11.4); - Impact to 5GC procedure due to interworking with EPC (clause 4.11.5); - Interworking for common network exposure (clause 4.11.6). In clause 4.11, UEs are assumed to support both 5GC NAS and EPC NAS unless explicitly stated otherwise. The procedures in clause 4.11 are not applicable for Disaster Roaming service (see clause 5.40 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]). | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.11 |
2,831 | 6.3.4.2.2 Precoding for large delay CDD | For large-delay CDD, precoding for spatial multiplexing is defined by where the precoding matrixis of size and , . The diagonal size-matrix supporting cyclic delay diversity and the size- matrix are both given by Table 6.3.4.2.2-1 for different numbers of layers . The values of the precoding matrix shall be selected among the precoder elements in the codebook configured in the eNodeB and the UE. The eNodeB can further confine the precoder selection in the UE to a subset of the elements in the codebook using codebook subset restriction. The configured codebook shall be selected from Table 6.3.4.2.3-1 or 6.3.4.2.3-2. For 2 antenna ports, the precoder is selected according to where denotes the precoding matrix corresponding to precoder index 0 in Table 6.3.4.2.3-1. For 4 antenna ports, the UE may assume that the eNodeB cyclically assigns different precoders to different vectors on the physical downlink shared channel as follows. A different precoder is used every vectors, where denotes the number of transmission layers in the case of spatial multiplexing. In particular, the precoder is selected according to , where is the precoder index given by and denote precoder matrices corresponding to precoder indices 12,13,14 and 15, respectively, in Table 6.3.4.2.3-2. Table 6.3.4.2.2-1: Large-delay cyclic delay diversity | 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.3.4.2.2 |
2,832 | 10.5.5.22 PS LCS Capability | The purpose of the PS LCS Capability element is to indicate the positioning methods and additional positioning capabilities supported by the MS for the provision of location services (LCS) via the PS domain in Gb-mode. The PS LCS Capability is a type 4 information element with a length of 4 octets. The PS LCS Capability element is coded as shown in figure 10.5.135b/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.153b/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Figure 10.5.135b/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : PS LCS Capability information element Table 10.5.153b/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] PS LCS Capability information element | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 10.5.5.22 |
2,833 | 4.15.3.2.10 Number of UEs and PDU Sessions per network slice notification procedure | 4.15.3.2.10.1 Reported value(s) aggregated at NEF This procedure depicts the case of an AF subscribing to receive the registered number of UEs, or the number of PDU sessions in a specific S-NSSAI. The procedure handles the case when there is a single NSACF in the PLMN responsible for the S-NSSAI (single Service Area) or when there are multiple NSACFs responsible for the S-NSSAI in the PLMN (multiple Service Areas). Figure 4.15.3.2.10.1-1: Reported value(s) aggregated at NEF per network slice notification procedure 1. To subscribe or unsubscribe for the number of UEs or the number of PDU Sessions per network slice notification with the NEF, the AF sends Nnef_EventExposure Subscribe/Unsubscribe Request (Event ID, Event Filter, Event Reporting information, S-NSSAI) message to the NEF. The Event ID parameter defines the subscribed event ID, i.e. Number of Registered UEs or Number of Established PDU Sessions. The Event Filter parameter defines the S-NSSAI, in case of a trusted AF or AF-Service-Identifier as defined in TS 29.522[ 5G System; Network Exposure Function Northbound APIs; Stage 3 ] [87] for an untrusted AF, for which reporting is required. The Event Reporting information parameter defines the mode of reporting, which includes threshold reporting with a threshold value or periodic reporting with included periodicity time interval. The S-NSSAI is the slice for which the subscription is requested The AF may request one-time reporting or immediate reporting. NOTE 1: When immediate reporting but not for one-time reporting is requested, the subscription is maintained after returning the report to the AF. When one-time reporting is requested, the subscription is terminated right after returning the report to the AF. Notifications related to the threshold based subscriptions behave as follows: - A single notification is sent only when the number of registered UEs or the number of established PDU Sessions reaches the threshold. A single notification is sent every time there is a change from being below the threshold to reach the threshold. - A single notification is sent only once when the number of registered UEs or the number of established PDU Sessions go below the threshold after reaching it. A single notification is sent every time there is a change from reaching the threshold to coming down below the threshold. 2. The NEF confirms with Nnef_EventExposure_Subscribe/Unsubscribe Response message to the AF. This message may include the event reporting, if available in the NEF and immediate reporting or one-time reporting was requested by the AF. In the case of Untrusted AF, the NEF includes the AF-Service-Identifier corresponding to the S-NSSAI in the returned notification. If immediate reporting or one-time reporting is requested, step 2 occurs after step 5 and the subscription response contains the immediate or one-time report. For the case of one-time reporting, no subscription is created at the NEF/NSACF. 3. The NEF may query the NRF to find the NSACF(s) responsible for the requested S-NSSAI. If needed, the NEF translates the AF-Service-Identifier to the corresponding S-NSSAI prior to performing the query. 4. If the NEF has not already subscribed to the event from the NSACF for the requested S-NSSAI, the NEF initiates the request Nnsacf_SliceEventExposure_Subscribe/Unsubscribe Request (Event ID, Event Filter, Event Reporting information, immediate reporting, S-NSSAI) to all the NSACFs supporting the requested S-NSSAI. The NEF stores the AF requested Event Reporting Information. If multiple NSACFs are selected for the requested S-NSSAI, the NEF may set the Event Reporting Information to periodic in its request to the NSACFs. If single NSACF is selected, the NEF sets the Event Reporting Information identical to the received request from the AF. The NEF also sets the Event ID and Event Filter identical to the received request from the AF NOTE 2: The period chosen is selected by the NEF based on its internal logic. 5. The NSACF(s) confirms with Nnsacf_SliceEventExposure_Subscribe/Unsubscribe Response message to the NEF. This message may include the event reporting if available at NSACF and immediate reporting or one-time reporting was requested by the NEF. 6. When the reporting condition for a subscribed event is fulfilled, the NSACF triggers a notification towards the NEF. 7. The NSACF sends the Nnsacf_SliceEvent Exposure_Notify (Event ID, Event Reporting information) message to the NEF. If the subscription is for event based notification (e.g. based on the monitored event reaching a threshold value), the Event Reporting information parameter contains confirmation for the event fulfilment. If the subscription is for periodic notification or for immediate reporting, the Event Reporting information parameter provides information for the current number of UEs registered with a network slice (e.g. represented in percentage of the maximum number of the UEs registered with the network slice) or information for the current number of PDU Sessions on a network slice (e.g. represented in percentage of the maximum number of the UEs established on the network slice). 8. When a single NSACF is returned from the discovery procedure, the NEF sends the Nnef_EventExposure_Notify (Event ID, Event Reporting information) message since the reporting condition is fulfilled. In the case of Untrusted AF, the NEF includes the AF-Service-Identifier corresponding to the S-NSSAI in the returned notification. 9. When multiple NSACFs are selected for the requested NSSAI the NEF performs the aggregation from reporting NSACF(s) and maintain the overall usage of the S-NSSAI for the selected NSACFs as long as the subscription is active. NOTE 3: If multiple NSACFs are selected for the requested S-NSSAI, the NEF continuously updates the aggregated information to be able to fulfil the incoming subscription request from the AF. 10. When multiple NSACFs are selected for the requested S-NSSAI and when the reporting condition for a subscribed event by the AF is fulfilled, the NEF sends Nnef_EventExposure_Notify (Event ID, Event Reporting information) message towards the AF. In case of untrusted AF; the NEF includes the AF-Service-Identifier corresponding to the S-NSSAI in the returned notification. If the hierarchical NSAC architecture is deployed in the PLMN for the NSAC of an S-NSSAI and the number of UEs, number of UE with at least one PDU session/PDN connection, or number of PDU Sessions are aggregated at NEF, the same procedure as above can be reused. In this case Primary NSACF behaves as a normal NSACF. 4.15.3.2.10.2 Reported value(s) aggregated at Primary NSACF If the hierarchical NSAC architecture is deployed in the PLMN for the NSAC of an S-NSSAI, the Primary NSACF needs to be aware of the current status of registered UEs, UE with at least one PDU session/PDN connection, or established PDU sessions at all NSACFs with whom it is interacting, so it can dynamically adapt and adjust the local Maximum number of UEs, local Maximum number of UE with at least one PDU session/PDN connection, or PDU sessions configured at the NSACFs. In this case, it is possible to leverage this capability and provide subscribing AFs to receive the registered number of UEs, number of UE with at least one PDU session/PDN connection, or the number of PDU sessions for the requested S-NSSAI without NEF aggregation. Such a procedure is depicted below. Figure 4.15.3.2.10.2-1: Reported value(s) aggregated at Primary NSACF per network slice notification procedure 1. The AF subscribes (or unsubscribe) to the number of UEs, or the number of PDU Sessions per network slice notification to the NEF. The NEF finds the primary NSACF responsible for the requested S-NSSAI. Based on the network configuration, the NEF does not to do the aggregation. The procedure is same as steps 1-5 of clause 4.15.3.2.10.1 with the following differences: - Based on the network configuration the NEF is aware that one NSACF can serve entire PLMN for the requested S-NSSAI, i.e. existence of the Primary NSACF. The NEF queries the NRF to find the corresponding primary NSACF responsible for the requested S-NSSAI. Besides the requested S-NSSAI, the Serving Area information of "Entire PLMN" is included as querying parameter. In the case of Trusted AF, the AF can discover and subscribe (or unsubscribe) directly with the Primary NSACF. - The NEF sets the Event Reporting Information identical to the received request from the AF. The NEF also sets the Event ID and Event Filter identical to the received request from the AF. The Primary NSACF responsible for the requested S-NSSAI performs the aggregation per network configuration. 2-6. The Primary NSACF subscribes (or unsubscribes) to the number of UEs, or the number of PDU Sessions per network slice notification to all the NSACFs supporting the requested S-NSSAI(s). The procedure is same as steps 4-7 of clause 4.15.3.2.10.1 for multiple NSACFs case with the Primary NSACF replacing the NEF and the following differences: - Step 2, based on the received event subscription from NEF, the Primary NSACF triggers the slice event subscription to NSACF(s) if it does not exist before. - Step 6, the Primary NSACF performs the aggregated values from reporting NSACF(s) including itself (if available) and maintain the overall usage of the S-NSSAI(s) for the indicated Event ID parameter, i.e. the number of UEs registered with a network slice, number of UE with at least one PDU session/PDN connection, or the number of PDU Sessions established on a network slice, from the selected NSACFs as long as the subscription is active. When the reporting condition for a subscribed event is fulfilled, the Primary NSACF triggers a notification for the event towards the NEF. As values from the NSACF(s) has been aggregated at the Primary NSACF, there is no aggregation to be performed further at the NEF. NEF forwards the received values to AF. NOTE: For the number of registered UEs per network slice or number of UE with at least one PDU session/PDN connection, the aggregated value includes both the number of registered UE at NSACF(s) and the number of registered UE at Primary NASCF as described in the clause 5.15.11.1.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. For the number of established PDU sessions per network slice, the aggregated value only includes the number of established PDU Sessions at the NSACF(s). | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.15.3.2.10 |
2,834 | 6.2.13 SMSF | The SMSF supports the following functionality to support SMS over NAS: - SMS management subscription data checking and conducting SMS delivery accordingly. - SM-RP/SM-CP with the UE (see TS 24.011[ Point-to-Point (PP) Short Message Service (SMS) support on mobile radio interface ] [6]). - Relay the SM from UE toward SMS-GMSC/IWMSC/SMS-Router. - Relay the SM from SMS-GMSC/IWMSC/SMS-Router toward the UE. - SMS charging. - Lawful Interception. - Interaction with AMF and SMS-GMSC for notification procedure that the UE is unavailable for SMS transfer (i.e, notifies SMS-GMSC to inform UDM when UE is unavailable for SMS). | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 6.2.13 |
2,835 | 6.9.2.3.2 Xn-handover | In Xn handovers the source gNB/ng-eNB shall perform a vertical key derivation in case it has an unused {NH, NCC} pair. The source gNB/ng-eNB shall first compute KNG-RAN* from target PCI, its frequency ARFCN-DL/EARFCN-DL, and either from currently active KgNB in case of horizontal key derivation or from the NH in case of vertical key derivation as described in Annex A.11/A.12. Next, the source gNB/ng-eNB shall forward the { KNG-RAN*, NCC} pair to the target gNB/ng-eNB. The target gNB/ng-eNB shall use the received KNG-RAN* directly as KgNB to be used with the UE. The target gNB/ng-eNB shall associate the NCC value received from source gNB/ng-eNB with the KgNB. The target gNB/ng-eNB shall include the received NCC into the prepared HO Command message, which is sent back to the source gNB/ng-eNB in a transparent container and forwarded to the UE by source gNB/ng-eNB. When the target gNB/ng-eNB has completed the handover signalling with the UE, it shall send a NGAP PATH SWITCH REQUEST message to the AMF. Upon reception of the NGAP PATH SWITCH REQUEST, the AMF shall increase its locally kept NCC value by one and compute a new fresh NH from its stored data using the function defined in Annex A.10. The AMF shall use the KAMF from the currently active 5G NAS security context for the computation of the new fresh NH. The AMF shall then send the newly computed {NH, NCC} pair to the target gNB/ng-eNB in the NGAP PATH SWITCH REQUEST ACKNOWLEDGE message. The target gNB/ng-eNB shall store the received {NH, NCC} pair for further handovers and remove other existing unused stored {NH, NCC} pairs if any. If the AMF had activated a new 5G NAS security context with a new KAMF, different from the 5G NAS security context on which the currently active 5G AS security context is based, but has not yet successfully performed a UE Context Modification procedure, the sent NGAP PATH SWITCH REQUEST ACKNOWLEDGE message shall in addition contain a NSCI (New Security Context Indicator). The AMF shall in this case derive a new initial KgNB from the new KAMF and the uplink NAS COUNT in the most recent NAS Security Mode Complete message as specified in Annex A.9. The AMF shall associate the derived new initial KgNB with a new NCC value equal to zero. Then, the AMF shall use {the derived new initial KgNB, the new NCC value initialized to zero} pair as the newly computed {NH, NCC} pair to be sent in the NGAP PATH SWITCH REQUEST ACKNOWLEDGE message. The gNB/ng-eNB shall in this case set the value of keySetChangeIndicator field to true in further handovers. The gNB/ng-eNB should in this case perform an intra-gNB-CU/intra-ng-eNB handover immediately . NOTE 1: Because the NGAP PATH SWITCH REQUEST message is transmitted after the radio link handover, it can only be used to provide keying material for the next handover procedure. Thus, for Xn-handovers key separation happens only after two hops because the source gNB/ng-eNB knows the target gNB/ng-eNB keys. The target gNB/ng-eNB can immediately initiate an intra-gNB-CU/intra-ng-eNB handover to take the new NH into use once the new NH has arrived in the PATH SWITCH REQUEST ACKNOWLEDGE message. NOTE 2: The key derivation mechanism described in this clause is also applicable to CHO defined in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [52]. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.9.2.3.2 |
2,836 | 8.2.2.9.1 Minimum Requirement | The purpose of this test is to verify UE performance in the HST-SFN scenario defined in B.3A when highSpeedEnhancedDemodulationFlag [7] is received. For single carrier, the requirements are specified in Table 8.2.2.9.1-2, with the addition of the parameters in Table 8.2.2.9.1-1 and the downlink physical channel setup according to Annex C.3.2. For CA with 2 DL CCs, the requirements are specified in Table 8.2.2.9.1-5, based on single carrier requirement specified in Table 8.2.2.9.1-4, with the addition of the parameters in Table 8.2.2.9.1-3 and the downlink physical channel setup according to Annex C.3.2. For CA with 3 DL CCs, the requirements are specified in Table 8.2.2.9.1-6, based on single carrier requirement specified in Table 8.2.2.9.1-4, with the addition of the parameters in Table 8.2.2.9.1-3 and the downlink physical channel setup according to Annex C.3.2. For CA with 4 DL CCs, the requirements are specified in Table 8.2.2.9.1-7, based on single carrier requirement specified in Table 8.2.2.9.1-4, with the addition of the parameters in Table 8.2.2.9.1-3 and the downlink physical channel setup according to Annex C.3.2. For CA with 5 DL CCs, the requirements are specified in Table 8.2.2.9.1-8, based on single carrier requirement specified in Table 8.2.2.9.1-4, with the addition of the parameters in Table 8.2.2.9.1-3 and the downlink physical channel setup according to Annex C.3.2. The test coverage for different number of component carriers is defined in 8.1.2.4. Table 8.2.2.9.1-1: Test Parameters for UE performance in HST-SFN scenario (FRC) Table 8.2.2.9.1-2: Minimum performance UE in HST-SFN scenario (FRC) Table 8.2.2.9.1-3: Test Parameters for Large Delay CDD (FRC) for CA Table 8.2.2.9.1-4: Single carrier performance for multiple CA configurations Table 8.2.2.9.1-5: Minimum performance (FRC) based on single carrier performance for CA with 2 DL CCs Table 8.2.2.9.1-6: Minimum performance (FRC) based on single carrier performance for CA with 3 DL CCs Table 8.2.2.9.1-7: Minimum performance (FRC) based on single carrier performance for CA with 4 DL CCs Table 8.2.2.9.1-8: Minimum performance (FRC) based on single carrier performance for CA with 5 DL CCs | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.2.2.9.1 |
2,837 | 8.10.1.2.6 Dual-Layer Spatial Multiplexing (User-Specific Reference Symbols) | For dual-layer transmission on antenna ports 7 and 8 upon detection of a PDCCH with DCI format 2C, the requirements are specified in Table 8.10.1.2.6-2, with the addition of the parameters in Table 8.10.1.2.6-1 where Cell 1 is the serving cell and Cell 2 is the interfering cell. The downlink physical channel setup is set according to Annex C.3.2. The purpose of these tests is to verify the rank-2 performance for full RB allocation, to verify rate matching with multiple CSI reference symbol configurations with non-zero and zero transmission power, and to verify that the UE correctly estimate SNR. Table 8.10.1.2.6-1: Test Parameters for Testing CDM-multiplexed DM RS (dual layer) with multiple CSI-RS configurations and 4Rx Antenna Ports Table 8.10.1.2.6-2: Minimum performance for CDM-multiplexed DM RS (FRC) with multiple CSI-RS configurations | 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.6 |
2,838 | 9.3.17b CC-Establishment confirmed $(CCBS)$ | A Network that does not support the "Network initiated MO call" option shall treat this message as a message with message type not defined for the PD. This message is sent by the mobile station to the network to indicate the requested channel characteristics for the call which may be initiated by the mobile station. See Table 9.67b/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Message type: CC-ESTABLISHMENT CONFIRMED Significance: local Direction: mobile station to network Table 9.67b/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : CC-ESTABLISHMENT CONFIRMED message content | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.3.17b |
2,839 | 5.9.1 Description | Considering beyond visual line-of-sight remote controlled UAV using cellular technologies can expose some public safety and security concerns in some countries, therefore there is a need to consider the case which needs to apply restriction on the fly range of a remote controlled UAV, such as to prevent out-of-sight flying, restriction on the distance range between the UAV and the UAV controller, or the geographic range of UAV can fly. In addition, because of the roaming consideration, preventing controlled UAV crossing different PLMNs may also be required. Therefore, to address those public security and charging issues, we should define and limit the fly range of the UAV, such as controlling range between UAV and UAV controller. | 3GPP TS 22.825 | Study on Remote Identification of Unmanned Aerial Systems (UAS) | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 5.9.1 |
2,840 | 5.3.3.1A Tracking Area Update procedure with Serving GW change and data forwarding | Figure 5.3.3.1A-1: Tracking Area Update procedure with Serving GW change and data forwarding NOTE 1: The procedure steps (A) and (B) are defined in clause 5.3.3.1. Step 5 in the figure above has compared to clause 5.3.3.1 one additional parameter which is described below. 4. The timer setting by the old S4 SGSN or MME in step 4 (as in clause 5.3.3.1) shall ensure that the buffered data in the old Serving GW can be forwarded before the old Serving GW resource is released. 5. DL data is being buffered in the old Serving GW and the DL Data Expiration Time has not expired, therefore the old MME/old S4-SGSN indicates Buffered DL Data Waiting in the Context Response. This triggers the new MME to setup the user plane and invoke data forwarding. For Control Plane CIoT EPS Optimisation, if the DL data is buffered in the old Serving GW, and when the Buffered DL Data Waiting is indicated, the new MME shall setup the S11 user plane with the new Serving GW and invoke data forwarding. If the DL data is buffered in the old MME and the DL Data Expiration Time has not expired, the old MME shall discard the buffered DL data. 11-12. The user plane is setup. These procedure steps are defined in clause 5.3.4.1, steps 4-7 and steps 8-12 respectively in the UE Triggered Service Request procedure. NOTE 2: It is assumed that Pause of PGW Charging is not invoked by SGW that is performing extended data buffering. For Control Plane CIoT EPS Optimisation, steps 11 and 12 are skipped. 13. Since it was indicated in step 5 that buffered DL data is waiting, the new MME sets up forwarding parameters by sending Create Indirect Data Forwarding Tunnel Request (target eNodeB addresses and TEIDs for forwarding) to the Serving GW. The Serving GW sends a Create Indirect Data Forwarding Tunnel Response (target Serving GW addresses and TEIDs for forwarding) to the target MME. For Control Plane CIoT EPS Optimisation, the new MME sets up forwarding parameters by sending Create Indirect Data Forwarding Tunnel Request (target MME address and TEID for forwarding) to the Serving GW. Upon receipt of the Create Indirect Data Forwarding Tunnel Response message the new MME starts a timer for release of resources if resources for indirect forwarding were allocated in the new S-GW. Indirect forwarding may be performed via a Serving GW which is different from the Serving GW used as the anchor point for the UE. 14. This procedure step is defined in clause 5.3.3.1, step 7. In addition the new MME includes the F-TEID where buffered DL data should be forwarded and a Forwarding indication in the Context Acknowledge message. The F-TEID is the F-TEID for the indirect forwarding received from step 13 or it may be the F-TEID of the eNodeB (when eNodeB supports forwarding). 15. A Modify Bearer Request( F-TEID ) is sent to the old Serving GW. The F-TEID is the Forwarding F-TEID where the buffered DL data shall be forwarded. 16. The old Serving GW forwards its buffered data towards the received F-TEID in step 15. The buffered DL data is sent to the UE over the radio bearers established in step 11. For Control Plane CIoT EPS Optimisation, the buffered DL data is sent to the new MME from the new Serving GW and is sent to the UE as described in steps 12-14 of clause 5.3.4B.3. 17-18. As steps 15-16, 18-19 in clause 5.3.3.1. 19. If indirect forwarding was used, then the expiry of the timer at the new MME started at step 13 triggers the new MME to send a Delete Indirect Data Forwarding Tunnel Request message to the new S-GW to release temporary resources used for indirect forwarding that were allocated at step 13. | 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.3.1A |
2,841 | 17.3.2 Provisioning GANC-SEGW identifier | The Provisioning GANC-SEGW identifier shall take the form of a fully qualified domain name (FQDN) as specified in IETF RFC 1035 [19] and IETF RFC 1123 [20]. The Provisioning GANC-SEGW identifier 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. If the (U)SIM is not provisioned with the FQDN or IP address of the Provisioning GANC-SEGW, the UE derives an FQDN from the IMSI to identify the Provisioning GANC-SEGW. The UE shall derive such an FQDN as follows: 1. create a domain name as specified in 17.3.1; 2. add the label "psegw." to the beginning of the domain name. An example of an FQDN for a Provisioning GANC-SEGW is: IMSI in use: 234150999999999; Where: MCC = 234; MNC = 15; MSIN = 0999999999, Which gives the FQDN: psegw.gan.mnc015.mcc234.pub.3gppnetwork.org. NOTE: If it is not possible for the UE to identify whether a 2 or 3 digit MNC is used (e.g. SIM is inserted and the length of MNC in the IMSI is not available in the "Administrative data" data file), it is implementation dependent how the UE determines the length of the MNC (2 or 3 digits). | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 17.3.2 |
2,842 | 5.4.2.4 NAS security mode control completion by the network | The AMF shall, upon receipt of the SECURITY MODE COMPLETE message, stop timer T3560. From this time onward the AMF shall integrity protect and encipher all signalling messages with the selected 5GS integrity and ciphering algorithms. If the SECURITY MODE COMPLETE message contains a NAS message container IE with a REGISTRATION REQUEST message, the AMF shall complete the ongoing registration procedure by considering the REGISTRATION REQUEST message contained in the NAS message container IE as the message that triggered the procedure. If the SECURITY MODE COMPLETE message contains a NAS message container IE with a DEREGISTRATION REQUEST message, the AMF shall complete the ongoing deregistration procedure by considering the DEREGISTRATION REQUEST message contained in the NAS message container IE as the message that triggered the procedure. If the SECURITY MODE COMPLETE message contains a NAS message container IE with a REGISTRATION REQUEST message, the 5GMM capability IE included in the REGISTRATION REQUEST message indicates "S1 mode supported" and the AMF supports N26 interface, the AMF shall initiate another NAS security mode control procedure in order to provide the selected EPS NAS security algorithms to the UE as described in subclause 5.4.2.2. This second NAS security mode control procedure should be initiated as part of 5GMM common procedures of the ongoing registration procedure. If the SECURITY MODE COMPLETE message contains a NAS message container IE with a SERVICE REQUEST message, the AMF shall complete the ongoing service request procedure by considering the SERVICE REQUEST message contained in the NAS message container IE as the message that triggered the procedure. If the SECURITY MODE COMPLETE message contains a NAS message container IE with a CONTROL PLANE SERVICE REQUEST message, the AMF shall complete the ongoing service request procedure by considering the CONTROL PLANE SERVICE REQUEST message contained in the NAS message container IE as the message that triggered the procedure. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.4.2.4 |
2,843 | 4.3.25.3 Considerations for Network Sharing | If the network supports the MOCN configuration for network sharing (see TS 23.251[ Network sharing; Architecture and functional description ] [24]), each network sharing operator has separate CN(s). Mechanisms for selection of serving operator for supporting and non-supporting UEs are defined in TS 23.251[ Network sharing; Architecture and functional description ] [24]. Each of the sharing operators may deploy one or more DCNs. If Selected PLMN information is provided by the UE, the RAN selects the CN operator based on this provided information and then DECOR rerouting may, if needed, be initiated within the CN of the selected operator. If the UE assisted DCN selection feature is supported and both the Selected PLMN information and DCN-ID is provided by the UE, the RAN first selects the CN operator followed by selection of a DCN supported by the selected CN operator. If Selected PLMN information is not provided by the UE (may only happen in GERAN and UTRAN), the network initiates MOCN redirection, including CS/PS coordination, to select a CN operator that can serve the UE. After this, DECOR rerouting is initiated if needed. The serving node in the selected DCN ends the MOCN redirection. If the UE assisted DCN selection feature is supported and Selected PLMN information is not provided by the UE, the network initiates CN operator selection and after the CN operator selection is concluded the DCN is selected based on the UE provided DCN-ID. As the PLMN information included in the RAI is the Common PLMN (refer to TS 23.251[ Network sharing; Architecture and functional description ] [24]), which does not reflect the selected CN operator, the network may also return the PLMN ID of the selected CN operator. When the UE receives the NAS Accept message, the UE associates the DCN-ID with both the PLMN ID of the selected CN operator and the Common PLMN IDs. The functions for redirecting or maintaining UEs in specific DCNs are configured to work within the CNs of the same operator. | 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.25.3 |
2,844 | 10.5.1.10 Group Cipher Key Number | The purpose of the Group Cipher Key Number is to provide information on the group cipher key to be used for ciphering and deciphering by the mobile station. The Group Cipher Key Number information element is coded as shown in figure 10.5.9/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and Table10.5.9/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] The Group Cipher Key Number is a type 1 information element with 1 octet length. Figure 10.5.9/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Group Cipher Key Number Table 10.5.9/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Group Cipher Key Number | 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.1.10 |
2,845 | 6.34.1 Description | The 5G system is expected to meet the service requirements for critical medical applications where critical medical applications denote medical devices and applications involved in the delivery of care for patient’s survival. Additionally, as the medical industry undergoes a shift to value-based healthcare, where companies and healthcare providers have to move to business models based on providing clinical value with cost efficiency, the 5G system can help to adopt new and more efficient care delivery models in order to reduce administrative and supply costs. On this matter, 5G technology can especially have an important impact by: - enabling superior monitoring capability means thus improving the effectiveness of preventive care, - enabling shifting care location from hospitals to homes and other lower cost facilities, - improving operating room planning, enabling streamlining equipment usage and simplifying operating theater implementation, - Enhancing cooperation in critical situations between ambulance and hospital staff. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.34.1 |
2,846 | – PRS-ProcessingCapabilityOutsideMGinPPWperType | The IE PRS-ProcessingCapabilityOutsideMGinPPWperType is used to indicate DL PRS Processing Capability outside MG capabilities supported by the UE. PRS-ProcessingCapabilityOutsideMGinPPWperType information element -- ASN1START -- TAG-PRS-PROCESSINGCAPABILITYOUTSIDEMGINPPWPERType-START PRS-ProcessingCapabilityOutsideMGinPPWperType-r17 ::= SEQUENCE { prsProcessingType-r17 ENUMERATED {type1A, type1B, type2}, ppw-dl-PRS-BufferType-r17 ENUMERATED {type1, type2, ...}, ppw-durationOfPRS-Processing-r17 CHOICE { ppw-durationOfPRS-Processing1-r17 SEQUENCE { ppw-durationOfPRS-ProcessingSymbolsN-r17 ENUMERATED {msDot125, msDot25, msDot5, ms1, ms2, ms4, ms6, ms8, ms12, ms16, ms20, ms25, ms30, ms32, ms35, ms40, ms45, ms50}, ppw-durationOfPRS-ProcessingSymbolsT-r17 ENUMERATED {ms1, ms2, ms4, ms8, ms16, ms20, ms30, ms40, ms80, ms160, ms320, ms640, ms1280} }, ppw-durationOfPRS-Processing2-r17 SEQUENCE { ppw-durationOfPRS-ProcessingSymbolsN2-r17 ENUMERATED {msDot125, msDot25, msDot5, ms1, ms2, ms3, ms4, ms5, ms6, ms8, ms12}, ppw-durationOfPRS-ProcessingSymbolsT2-r17 ENUMERATED {ms4, ms5, ms6, ms8} } } OPTIONAL, ppw-maxNumOfDL-PRS-ResProcessedPerSlot-r17 SEQUENCE { scs15-r17 ENUMERATED {n1, n2, n4, n6, n8, n12, n16, n24, n32, n48, n64} OPTIONAL, scs30-r17 ENUMERATED {n1, n2, n4, n6, n8, n12, n16, n24, n32, n48, n64} OPTIONAL, scs60-r17 ENUMERATED {n1, n2, n4, n6, n8, n12, n16, n24, n32, n48, n64} OPTIONAL, scs120-r17 ENUMERATED {n1, n2, n4, n6, n8, n12, n16, n24, n32, n48, n64} OPTIONAL, ... }, ppw-maxNumOfDL-Bandwidth-r17 CHOICE { fr1-r17 ENUMERATED {mhz5, mhz10, mhz20, mhz40, mhz50, mhz80, mhz100}, fr2-r17 ENUMERATED {mhz50, mhz100, mhz200, mhz400} } OPTIONAL } -- TAG-PRS-PROCESSINGCAPABILITYOUTSIDEMGINPPWPERType-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
2,847 | 5.3.10 Security Function 5.3.10.1 General | The security functions include: - Guards against unauthorised EPS service usage (authentication of the UE by the network and service request validation). - Provision of user identity confidentiality (temporary identification and ciphering). - Provision of user data and signalling confidentiality (ciphering). - Provision of origin authentication of signalling and user data (integrity protection). - Authentication of the network by the UE. Security-related network functions for EPS are described in TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [41]. The aspects of user plane data integrity protection that involve interactions with the 5G Core are specified in TS 23.501[ System architecture for the 5G System (5GS) ] [83] and TS 23.502[ Procedures for the 5G System (5GS) ] [84]. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.3.10 |
2,848 | I.10.2.2 Untrusted non-3GPP access support in SNPN with CH | UE may use the credentials from a Credentials Holder AAA server to access SNPN services via Untrusted non-3GPP access. Figure I.10.2.2-1: Procedure for Untrusted non-3GPP Access using Credentials Holder AAA Server 0 prior conditions and assumptions are described in step 0 in clause I.2.2.2.2. 1a-6b as specified in clause 7.2.1. In addition, if the construction of SUCI as described in clause 6.12 cannot be used and if the employed EAP method supports SUPI privacy, the UE may send an anonymous SUPI based on configuration. 7 authentication and key agreement procedure between the UE and the AAA server, as specified in steps 2-15 in clause I.2.2.2.2. 8-17 as specified in clause I.10.2.1 . | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | I.10.2.2 |
2,849 | 4.3.2.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 an AUTHENTICATION FAILURE message to the network, with the reject cause 'MAC failure'. The MS shall then follow the procedure described in subclause 4.3.2.6 (c). 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 FAILURE message to the network, with the reject cause 'Synch failure' and a 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.3.2.6 (d). In UMTS, an MS with 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 FAILURE message to the network, with the reject cause "GSM authentication unacceptable". The MS shall then follow the procedure described in subclause 4.3.2.6 (c). If the MS returns an AUTHENTICATION_FAILURE message to the network, the MS shall delete any previously stored RAND and RES and shall stop timer T3218, if running. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.3.2.5.1 |
2,850 | – CSI-SSB-ResourceSet | The IE CSI-SSB-ResourceSet is used to configure one SS/PBCH block resource set which refers to SS/PBCH as indicated in ServingCellConfigCommon and ServingCellConfig. CSI-SSB-ResourceSet information element -- ASN1START -- TAG-CSI-SSB-RESOURCESET-START CSI-SSB-ResourceSet ::= SEQUENCE { csi-SSB-ResourceSetId CSI-SSB-ResourceSetId, csi-SSB-ResourceList SEQUENCE (SIZE(1..maxNrofCSI-SSB-ResourcePerSet)) OF SSB-Index, ..., [[ servingAdditionalPCIList-r17 SEQUENCE (SIZE(1..maxNrofCSI-SSB-ResourcePerSet)) OF ServingAdditionalPCIIndex-r17 OPTIONAL -- Need R ]] } ServingAdditionalPCIIndex-r17 ::= INTEGER(0..maxNrofAdditionalPCI-r17) -- TAG-CSI-SSB-RESOURCESET-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
2,851 | 5.3.10 Handling of DNN based congestion control | The AMF may detect and start performing DNN based congestion control when one or more DNN congestion criteria as specified in 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8] are met. If the UE does not provide a DNN for a non-emergency PDU session, then the AMF uses the selected DNN or the DNN associated with the PDU session corresponding to the 5GSM procedure. When DNN based congestion control is activated at the AMF, the AMF performs the congestion control as specified in subclause 5.4.5 and the UE performs the congestion control as specified in subclause 5.4.5 and subclause 6.2.7. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.3.10 |
2,852 | 20.5a.1 MBMS-Access-Indicator AVP | The MBMS-Access-Indicator AVP (AVP code 923) is of type Enumerated. It indicates whether the MBMS bearer service will be delivered in UTRAN-only, E-UTRAN-only or both coverage areas. The following values are supported: UTRAN (0) The MBMS bearer service shall only be delivered in UTRAN only coverage areas. E-UTRAN (1) The MBMS bearer service shall only be delivered in E-UTRAN only coverage areas. UTRAN-AND-E-UTRAN (2) The MBMS bearer service shall be delivered both in UTRAN and E-UTRAN coverage areas. | 3GPP TS 29.061 | Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) | CT WG3 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 20.5a.1 |
2,853 | 5.4.1.3.4 Authentication completion by the network | Upon receipt of an AUTHENTICATION RESPONSE message, the network stops the timer T3560 and checks the correctness of RES* (see 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]). If the 5G AKA based primary authentication and key agreement procedure has been completed successfully and the related ngKSI is stored in the 5G NAS security context of the network, the network shall include a different ngKSI value in the AUTHENTICATION REQUEST message when it initiates a new 5G AKA based primary authentication and key agreement procedure. Upon receipt of an AUTHENTICATION FAILURE message, the network stops the timer T3560. In the case where the 5GMM cause #21 "synch failure" is received, the core network may renegotiate with the UDM/AUSF and provide the UE with new authentication parameters. | 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.3.4 |
2,854 | 4.11.1.3 Idle Mode Mobility procedures 4.11.1.3.1 General | When a UE moves from EPC to 5GC, the UE always performs Registration procedure. When a UE moves from 5GC to EPC, the UE performs either Tracking Area Update or Initial Attach. The UE performs Tracking Area Update procedure if - Both the UE and the EPC support "attach without PDN connectivity", or - The UE has at least one PDU Session for which Session Continuity is supported during interworking, i.e. the UE has EPS Bearer ID and mapped EPS QoS parameters received as described in clause 4.11.1.1. The UE performs an initial attach procedure if - The UE is registered without PDU Session in 5GC or the UE is registered only with PDU Session for which Session Continuity is not supported during interworking to EPC; and - Either the UE or the EPC does not support attach without PDN connectivity. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.11.1.3 |
2,855 | 4.7.2 The EPS bearer 4.7.2.1 The EPS bearer in general | For E-UTRAN access to the EPC the PDN connectivity service is provided by an EPS bearer for GTP-based S5/S8, and if IP is in use, by an EPS bearer concatenated with IP connectivity between Serving GW and PDN GW for PMIP-based S5/S8. In this release of the specifications, dedicated bearers are only supported for the IP and Ethernet PDN Connectivity Service. When User Plane (S1-U) is used for data traffic, then an EPS bearer uniquely identifies traffic flows that receive a common QoS treatment between a UE and a PDN GW for GTP-based S5/S8, and between UE and Serving GW for PMIP-based S5/S8. The packet filters signalled in the NAS procedures are associated with a unique packet filter identifier on per-PDN connection basis. NOTE 1: The EPS Bearer Identity together with the packet filter identifier is used to reference which packet filter the UE intends to modify or delete, i.e. it is used to implement the unique packet filter identifier. An EPS bearer is the level of granularity for bearer level QoS control in the EPC/E-UTRAN. That is, all traffic mapped to the same EPS bearer receive the same bearer level packet forwarding treatment (e.g. scheduling policy, queue management policy, rate shaping policy, RLC configuration, etc.). Providing different bearer level packet forwarding treatment requires separate EPS bearers. NOTE 2: In addition but independent to bearer level QoS control, the PCC framework allows an optional enforcement of service level QoS control on the granularity of SDFs independent of the mapping of SDFs to EPS bearers. One EPS bearer is established when the UE connects to a PDN, and that remains established throughout the lifetime of the PDN connection to provide the UE with always-on connectivity to that PDN. That bearer is referred to as the default bearer. Any additional EPS bearer that is established for the same PDN connection is referred to as a dedicated bearer. The EPS bearer traffic flow template (TFT) is the set of all packet filters associated with that EPS bearer. An UpLink Traffic Flow Template (UL TFT) is the set of uplink packet filters in a TFT. A DownLink Traffic Flow Template (DL TFT) is the set of downlink packet filters in a TFT. Every dedicated EPS bearer is associated with a TFT. A TFT may be also assigned to the default EPS bearer. The UE uses the UL TFT for mapping traffic to an EPS bearer in the uplink direction. The PCEF (for GTP-based S5/S8) or the BBERF (for PMIP-based S5/S8) uses the DL TFT for mapping traffic to an EPS bearer in the downlink direction. The UE may use the UL TFT and DL TFT to associate EPS Bearer Activation or Modification procedures to an application and to traffic flow aggregates of the application. Therefore the PDN GW shall, in the Create Dedicated Bearer Request and the Update Bearer Request messages, provide all available traffic flow description information (e.g. source and destination IP address and port numbers and the protocol information). For the UE, the evaluation precedence order of the packet filters making up the UL TFTs is signalled from the P-GW to the UE as part of any appropriate TFT operations. NOTE 3: The evaluation precedence index of the packet filters associated with the default bearer, in relation to those associated with the dedicated bearers, is up to operator configuration. It is possible to "force" certain traffic onto the default bearer by setting the evaluation precedence index of the corresponding filters to a value that is lower than the values used for filters associated with the dedicated bearers. Further details about the TFT and the TFT operations are described in clause 15.3 of TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [7]. The details about the TFT packet filter(s) are described in clause 15.3.2 of TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [7] for PDN connections of IP type and in clause 5.7.6.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [83] for PDN connections of Ethernet type. A TFT of an uplink unidirectional EPS bearer is only associated with UL packet filter(s) that matches the uplink unidirectional traffic flow(s) A TFT of a downlink unidirectional EPS bearer is associated with DL packet filter(s) that matches the unidirectional traffic flow(s) and a UL packet filter that effectively disallows any useful packet flows (see clause 15.3.3.4 in TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [7] for an example of such packet filter. The UE routes uplink packets to the different EPS bearers based on uplink packet filters in the TFTs assigned to these EPS bearers. The UE evaluates for a match, first the uplink packet filter amongst all TFTs that has the lowest evaluation precedence index and, if no match is found, proceeds with the evaluation of uplink packet filters in increasing order of their evaluation precedence index. This procedure shall be executed until a match is found or all uplink packet filters have been evaluated. If a match is found, the uplink data packet is transmitted on the EPS bearer that is associated with the TFT of the matching uplink packet filter. If no match is found, the uplink data packet shall be sent via the EPS bearer that has not been assigned any uplink packet filter. If all EPS bearers (including the default EPS bearer for that PDN) have been assigned one or more uplink packet filters, the UE shall discard the uplink data packet. NOTE 4: The above algorithm implies that there is at most one EPS bearer without any uplink packet filter. Therefore, some UEs may expect that during the lifetime of a PDN connection (where only network has provided TFT packet filters) at most one EPS bearer exists without any uplink packet filter. To ensure that at most one EPS bearer exists without any uplink packet filter, the PCEF (for GTP-based S5/S8) or the BBERF (for PMIP-based S5/S8) maintains a valid state for the TFT settings of the PDN connection as defined in clause 15.3.0 of TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [7] and if necessary, adds a packet filter which effectively disallows any useful packet flows in uplink direction (see clause 15.3.3.4 in TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [7] for an example of such a packet filter) to the TFT of a dedicated bearer. NOTE 5: The default bearer is the only bearer that may be without any uplink packet filter and thus, a packet filter which effectively disallows any useful packet flows in uplink direction will not be added by the PCEF/BBERF. The initial bearer level QoS parameter values of the default bearer are assigned by the network, based on subscription data (in E-UTRAN the MME sets those initial values based on subscription data retrieved from HSS). In a non-roaming scenario, the PCEF may change the QoS parameter value received from the MME based on interaction with the PCRF or based on local configuration. When the PCEF changes those values, the MME shall use the bearer level QoS parameter values received on the S11 reference point during establishment or modification of the default bearer. In a roaming scenario, based on local configuration, the MME may downgrade the ARP or APN-AMBR and/or remap QCI parameter values received from HSS to the value locally configured in MME (e.g. when the values received from HSS do not comply with services provided by the visited PLMN). The PCEF may change the QoS parameter values received from the MME based on interaction with the PCRF or based on local configuration. Alternatively, the PCEF may reject the bearer establishment. NOTE 6: For certain APNs (e.g. the IMS APN defined by the GSMA) the QCI value is strictly defined and therefore remapping of QCI is not permitted. NOTE 7: In roaming scenarios, the ARP/APN-AMBR/QCI values provided by the MME for a default bearer may deviate from the subscribed values depending on the roaming agreement. If the PCC/PCEF rejects the establishment of the default bearer, this implies that Attach via E-UTRAN will fail. Similarly, if the PCEF (based on interaction with the PCRF or based on local configuration) upgrades the ARP/APN-AMBR/QCI parameter values received from the MME, the default bearer establishment and attach may be rejected by the MME. NOTE 8: Subscription data related to bearer level QoS parameter values retrieved from the HSS are not applicable for dedicated bearers. For WB-E-UTRA, the decision to establish or modify a dedicated bearer can only be taken by the EPC, and the bearer level QoS parameter values are always assigned by the EPC. Dedicated bearers are not supported over NB-IoT. The PDN GW uses the RAT Type to ensure that no dedicated bearers are active when the UE is accessing over NB-IoT. In the case of inter-RAT mobility from WB-EUTRA to NB-IoT, the UE and MME indicate local deactivation of non-default EPS bearers at TAU as specified in TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [46]. The MME shall not modify the bearer level QoS parameter values received on the S11 reference point during establishment or modification of a default or dedicated bearer (except when the conditions described in NOTE 9 or NOTE 10 apply). Consequently, "QoS negotiation" between the E-UTRAN and the EPC during default or dedicated bearer establishment / modification is not supported. Based on local configuration, the MME may reject the establishment or modification of a default or dedicated bearer if the bearer level QoS parameter values sent by the PCEF over a GTP based S8 roaming interface do not comply with a roaming agreement. NOTE 9: If the EPS QoS parameters are not compliant with the roaming agreement, the MME, based on local policies, can downgrade the ARP priority level, ARP pre-emption capability, ARP pre-emption vulnerability, APN-AMBR or MBR (for GBR bearers) parameters received over S8 and allow the bearer establishment or modification of a default or dedicated bearer. The HPLMN is expected to set EPS QoS parameters compliant with roaming agreements, therefore the HPLMN is not informed about any downgrade of EPS bearer QoS parameters. The consequences of such a downgrading APN-AMBR and MBR are that APN-AMBR and MBR enforcement at the HPLMN and at the UE will not be aligned. The consequence of downgrading the ARP is that the EPS bearer ARP at the HPLMN and at the eNodeB will not be aligned, and multiple EPS bearers created can possibly have the same EPS bearer ARP in the eNodeB. NOTE 10: In roaming scenarios, for IMS voice service (e.g. the IMS APN defined by the GSMA), the MME, based on local policy, can override the ARP (i.e. ARP priority level, ARP pre-emption capability, ARP pre-emption vulnerability) received over S8 if the ARP indicates lower priority than the local policy. The purpose of ARP override in the serving PLMN is to apply the same allocation and retention priority for IMS voice service for all users (i.e. roamers and non-roamers) and to apply the same allocation and retention priority for all MPS service users (clause 4.3.18) when roaming agreements are in place and where regulatory requirements apply. At inter-RAT mobility, based on local configuration, the MME may perform a mapping of QCI values for which there is no mapping defined in Table E.3 or which are not supported in the target RAT. NOTE 11: The PCRF ensures that the EPS bearer QCI values are aligned with the QCI values mapped by the MME for the current RAT as described in clause A.4.1.2 of TS 23.203[ Policy and charging control architecture ] [6]. The distinction between default and dedicated bearers should be transparent to the access network (e.g. E-UTRAN). An EPS bearer is referred to as a GBR bearer if dedicated network resources related to a Guaranteed Bit Rate (GBR) value that is associated with the EPS bearer are permanently allocated (e.g. by an admission control function in the eNodeB) at bearer establishment/modification. Otherwise, an EPS bearer is referred to as a Non-GBR bearer. NOTE 12: Admission control can be performed at establishment / modification of a Non-GBR bearer even though a Non-GBR bearer is not associated with a GBR value. A dedicated bearer can either be a GBR or a Non-GBR bearer. A default bearer shall be a Non-GBR bearer. NOTE 13: A default bearer provides the UE with connectivity throughout the lifetime of the PDN connection. That motivates the restriction of a default bearer to bearer type Non-GBR. | 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.7.2 |
2,856 | 10 Generic error handling 10.1 General | The generic error handling defined in the subsequent clauses applies unless explicitly specified otherwise e.g. within the procedure specific error handling. The UE shall consider a value as not comprehended when it is set: - to an extended value that is not defined in the version of the transfer syntax supported by the UE; - to a spare or reserved value unless the specification defines specific behaviour that the UE shall apply upon receiving the concerned spare/reserved value. The UE shall consider a field as not comprehended when it is defined: - as spare or reserved unless the specification defines specific behaviour that the UE shall apply upon receiving the concerned spare/reserved field. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 10 |
2,857 | 9.12.1.2 TDD | For the parameters specified in Table 9.12.1.2-1 and Table 9.12.1.2-2 using the downlink physical channels specified in Annex C.3.2, the minimum requirements are specified in Table 9.12.1.2-3 by the following a) a CQI index not in the set {median CQI -1, median CQI, median CQI +1} shall be reported at least % of the time; b) the ratio of the throughput obtained when transmitting the transport format indicated by each reported wideband CQI index and that obtained when transmitting a fixed transport format configured according to the wideband CQI median shall be ≥ ; c) when transmitting the transport format indicated by each reported wideband CQI index, the average BLER for the indicated transport formats shall be greater or equal to 0.02. Table 9.12.1.2-1: Fading test for slot-PDSCH (TDD) Table 9.12.1.2-2: SPDCCH parameters (FDD) Table 9.12.1.2-3: Minimum requirement for slot-PDSCH (FDD) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 9.12.1.2 |
2,858 | 9.8.1.1 FDD and half-duplex FDD | The following requirements apply to UE supporting coverage enhancement. For the parameters specified in Table 9.8.1.1-1, and using the downlink physical channels specified in tables C.3.2-1 and C.3.2-2, the reported CQI value according to RC.23 FDD in Table A.4-1 shall be in the range of ±1 of the reported median more than 90% of the time. If the PDSCH BLER using the transport format indicated by median CQI is less than or equal to 0.1, the BLER using the transport format indicated by the (median CQI + 1) shall be greater than 0.1. If the PDSCH BLER using the transport format indicated by the median CQI is greater than 0.1, the BLER using transport format indicated by (median CQI – 1) shall be less than or equal to 0.1. Table 9.8.1.1-1: PUCCH 1-0 static test (FDD and half-duplex FDD) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 9.8.1.1 |
2,859 | – UECapabilityEnquiry | The UECapabilityEnquiry message is used to request UE radio access capabilities for NR as well as for other RATs. Signalling radio bearer: SRB1 RLC-SAP: AM Logical channel: DCCH Direction: Network to UE UECapabilityEnquiry message -- ASN1START -- TAG-UECAPABILITYENQUIRY-START UECapabilityEnquiry ::= SEQUENCE { rrc-TransactionIdentifier RRC-TransactionIdentifier, criticalExtensions CHOICE { ueCapabilityEnquiry UECapabilityEnquiry-IEs, criticalExtensionsFuture SEQUENCE {} } } UECapabilityEnquiry-IEs ::= SEQUENCE { ue-CapabilityRAT-RequestList UE-CapabilityRAT-RequestList, lateNonCriticalExtension OCTET STRING OPTIONAL, ue-CapabilityEnquiryExt OCTET STRING (CONTAINING UECapabilityEnquiry-v1560-IEs) OPTIONAL -- Need N } UECapabilityEnquiry-v1560-IEs ::= SEQUENCE { capabilityRequestFilterCommon UE-CapabilityRequestFilterCommon OPTIONAL, -- Need N nonCriticalExtension UECapabilityEnquiry-v1610-IEs OPTIONAL } UECapabilityEnquiry-v1610-IEs ::= SEQUENCE { rrc-SegAllowed-r16 ENUMERATED {enabled} OPTIONAL, -- Need N nonCriticalExtension SEQUENCE {} OPTIONAL } -- TAG-UECAPABILITYENQUIRY-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
2,860 | 5.3.10 Access class control | The network can restrict the access for certain groups of UEs by means of barring their access class. The UE shall evaluate the access control information as specified in 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [22] for: - Access Class Barring; - Access Control for CSFB and Extended Access Barring (EAB); - Access Control for Application specific Congestion control for Data Communication (ACDC), if the UE supports ACDC; and - Access Barring. | 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.10 |
2,861 | 5.9.3 Potential service requirements | The 3GPP system shall enable a UAS to update a UTM with the live location information of a UAV and its UAV controller. The 3GPP system shall be able to supplement location information of UAV and its UAV controller. The 3GPP system shall support a UTM to consume Location Service provided by the network. The 3GPP system shall be able to enforce the authorisation for an in-flight UAS to operate basing on UAS subscription information or under the instructions from UTM (e.g. by enabling dedicated control channel between UAS and UTM, or enabling or disabling communication between the UAV and UAV controller). | 3GPP TS 22.825 | Study on Remote Identification of Unmanned Aerial Systems (UAS) | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 5.9.3 |
2,862 | – SRS-AllPosResourcesRRC-Inactive | The IE SRS-AllPosResourcesRRC-Inactive is used to convey SRS positioning related parameters specific for a certain band. SRS-AllPosResourcesRRC-Inactive information element -- ASN1START -- TAG-SRS-ALLPOSRESOURCESRRC-INACTIVE-START SRS-AllPosResourcesRRC-Inactive-r17 ::= SEQUENCE { srs-PosResourcesRRC-Inactive-r17 SEQUENCE { -- R1 27-15: Positioning SRS transmission in RRC_INACTIVE state for initial UL BWP maxNumberSRS-PosResourceSetPerBWP-r17 ENUMERATED {n1, n2, n4, n8, n12, n16}, maxNumberSRS-PosResourcesPerBWP-r17 ENUMERATED {n1, n2, n4, n8, n16, n32, n64}, maxNumberSRS-ResourcesPerBWP-PerSlot-r17 ENUMERATED {n1, n2, n3, n4, n5, n6, n8, n10, n12, n14}, maxNumberPeriodicSRS-PosResourcesPerBWP-r17 ENUMERATED {n1, n2, n4, n8, n16, n32, n64}, maxNumberPeriodicSRS-PosResourcesPerBWP-PerSlot-r17 ENUMERATED {n1, n2, n3, n4, n5, n6, n8, n10, n12, n14}, dummy1 ENUMERATED {n1, n2, n4, n8, n16, n32, n64 }, dummy2 ENUMERATED {n1, n2, n3, n4, n5, n6, n8, n10, n12, n14} } } -- TAG-SRS-ALLPOSRESOURCESRRC-INACTIVE-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
2,863 | 5.5.5 Tracking area update request message (for N1 mode only) | The tracking area updating procedure is used to construct a TRACKING AREA UPDATE REQUEST message for the inter-system change from S1 mode to N1 mode for further security verification by the MME. The TRACKING AREA UPDATE REQUEST message is created by EMM by request of 5GMM which further includes the message in the REGISTRATION REQUEST message as described in 3GPP TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [54]. The TRACKING AREA UPDATE REQUEST message shall contain only mandatory information elements. The UE shall set the EPS update type IE in the TRACKING AREA UPDATE REQUEST message to "TA updating". The UE shall include the eKSI (either KSIASME or KSISGSN) in the NAS Key Set Identifier IE in the TRACKING AREA UPDATE REQUEST message. The UE shall integrity protect the TRACKING AREA UPDATE REQUEST message with the current EPS security context and increase the uplink NAS COUNT by one. The UE shall set associated GUTI in the Old GUTI IE. When the UE is in EMM-REGISTERED.NO-CELL-AVAILABLE substate and needs to construct the TRACKING AREA UPDATE REQUEST message for inter-system change from S1 mode to N1 mode, the UE shall consider that the tracking area updating procedure is not initiated and the UE shall remain in EMM-REGISTERED.NO-CELL-AVAILABLE state. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.5.5 |
2,864 | D.3.8.2 Preparation phase | Figure D.3.8.2-1: GERAN A/Gb mode to E-UTRAN inter RAT HO, preparation phase 1. The source BSS decides to initiate a PS handover. At this point both uplink and downlink user data is transmitted via the following: TBFs between MS and source BSS, BSSGP PFCs tunnel(s) between source BSS and old SGSN, GTP tunnel(s) between old SGSN and GGSN. NOTE 1: The UE acts as MS, and the PDN GW acts as the GGSN. 2. The source BSS sends the message PS handover Required (TLLI, Cause, Source Cell Identifier, Target eNodeB Identifier, Source to Target Transparent Container (RN part), and active PFCs list) to Source SGSN to request the CN to establish resources in the Target eNodeB, Target MME and the Serving GW. NOTE 2: The Source SGSN acts as the Old SGSN. NOTE 3: As an implementations option for supporting introduction scenarios with pre-Rel8 SGSNs the source BSS may be configured to use RNC IDs instead of eNodeB IDs to identify a target eNodeB. The Cause is relayed transparently by the SGSN to the MME and the MME maps the BSSGP cause code to an S1AP cause code. Source to Target Transparent Container carries information for the target eNodeB. This container is relayed transparently by the SGSN. 3. The Source SGSN determines from the 'Target eNodeB Identifier' IE that the type of handover is IRAT PS Handover to E-UTRAN. The Source SGSN initiates the Handover resource allocation procedure by sending message Forward Relocation Request (IMSI, Target Identification, MM Context, PDP Context, SGSN Tunnel Endpoint Identifier for Control Plane, SGSN Address for Control plane, Source to Target Transparent Container (RN part), Packet Flow ID, SNDCP XID parameters, LLC XID parameters) to the target MME. This message includes all PDP contexts that are established in the source system indicating the PFIs and the XID parameters related to those PDP Contexts, and the uplink Tunnel endpoint parameters of the Serving GW. The PDP Contexts shall be sent in a prioritized order, i.e. the most important PDP Context first. The prioritization method is implementation dependent, but should be based on the current activity. NOTE 3: Assigning the highest priority to the PDP context without TFT could be done to get service continuity for all ongoing services regardless of the number of supported EPS bearers in the UE and network. The target MME maps the PDP contexts to the EPS bearers 1-to-1 and maps the Release 99 QoS parameter values of a PDP context to the EPS Bearer QoS parameter values of an EPS bearer as defined in Annex E. The MME establishes the EPS bearer(s) in the indicated order. The MME deactivates the EPS bearers which cannot be established. The MM context contains security related information, e.g. supported ciphering algorithms as described in TS 29.060[ General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp interface ] [14]. For the PDP Context with traffic class equals 'Background', the source SGSN shall indicate via the Activity Status Indicator IE that EPS bearers shall be established on the target side. NOTE 4: The Source SGSN acts as the old SGSN. 4. The target MME selects the Serving GW as described under clause 4.3.8.2 on "Serving GW selection function". The target MME sends a Create Session Request message (IMSI, MME Tunnel Endpoint Identifier for Control Plane, MME Address for Control plane, PDN GW address(es) for user plane, PDN GW UL TEID(s) for user plane, PDN GW address for control plane, and PDN GW TEID(s) for control plane, the Protocol Type over S5/S8, APN-AMBR, Serving Network) per PDN connection to the Serving GW. The Protocol Type over S5/S8 is provided to Serving GW which protocol should be used over S5/S8 interface. For relocation from Gn/Gp SGSN, the target MME provides the APN-AMBR if not received explicitly from the Gn/Gp SGSN based on the mapping from MBR (as specified in Annex E) to the Serving GW 4a. The Serving GW allocates its local resources and returns them in a Create Session Response (Serving GW address(es) for user plane, Serving GW UL TEID(s) for user plane, Serving GW Address for control plane, Serving GW TEID for control plane) message to the target MME. 5. The Target MME will request the Target eNodeB to establish the Bearer(s) by sending the message Handover Request (UE Identifier, S1AP Cause, Integrity protection information (i.e. IK and allowed Integrity Protection algorithms), Encryption information (i.e. CK and allowed Ciphering algorithms), EPS Bearers to be setup list, Source to Target Transparent Container). The Target MME shall not request resources for which the Activity Status Indicator within a PDP Context indicates that no active bearer exists on the source side for that PDP Context. For each EPS bearer requested to be established, 'EPS Bearers To Be Setup' IE shall contain information such as ID, bearer parameters, Transport Layer Address, "Data forwarding not possible" indication and S1 Transport Association. The Transport Layer Address is the Serving GW Address for user data, and the S1 Transport Association corresponds to the uplink Tunnel Endpoint Identifier Data. "Data forwarding not possible" indication shall be included if the target MME decides the corresponding bearer will not be subject to data forwarding. The target MME shall not request the target eNodeB to establish EPS GBR bearers with maximum bitrate set to 0 and those EPS bearers should not be included in the EPS Bearers to be setup list and should be deactivated by the MME. For the remaining EPS Bearer Contexts the MME ignores any Activity Status Indicator within an EPS Bearer Context and requests the target eNodeB to allocate resources for all the remaining EPS Bearer Contexts. The ciphering and integrity protection keys will be sent transparently from the target eNodeB to the UE in the Target to Source Transparent Container, and in the message PS Handover Command from source BSS to the UE. This will then allow data transfer to continue in the new RAT/mode target cell without requiring a new AKA (Authentication and Key Agreement) procedure. The MME shall compute the UE-AMBR, as per clause 4.7.3, based on explicit APN-AMBR values received from the Gn/Gp SGSN. If explicit APN-AMBR values are not received by the MME, a local UE-AMBR shall be included in the 'EPS Bearers be setup list ' IE. The local UE-AMBR is described in Annex E. 5a. The Target eNodeB allocates the request resources and returns the applicable parameters to the Target MME in the message Handover Request Acknowledge (Target to Source Transparent Container, EPS Bearers setup list, EPS Bearers failed to setup list). Upon sending the Handover Request Acknowledge message the target eNodeB shall be prepared to receive downlink GTP PDUs from the Serving GW for the accepted EPS bearers. The target eNodeB shall ignore it if the number of radio bearers in the Source to Target Transparent container does not comply with the number of bearers requested by the MME and allocate bearers as requested by the MME. 6. If 'Indirect Forwarding' applies, the target MME sends a Create Indirect Data Forwarding Tunnel Request message (Cause, Target eNodeB Address(es), TEID(s) for DL user plane) to the Serving GW. Cause indicates that the bearer(s) are subject to data forwarding. 6a. The Serving GW returns a Create Indirect Data Forwarding Tunnel Response (Cause, Serving GW Address(es) and TEID(s) for Data Forwarding) message to the target MME. If the Serving GW doesn't support data forwarding, an appropriate cause value shall be returned and the Serving GW Address(es) and TEID(s) will not be included in the message. 7. The Target MME sends the message Forward Relocation Response (Cause, List of Set Up PFCs, MME Tunnel Endpoint Identifier for Control Plane, BSSGP cause, MME Address for control plane, Target to Source Transparent Container, Address(es) and TEID(s) for Data Forwarding) to the Source SGSN. If 'Direct Forwarding' is applicable, then the IEs 'Address(es) and TEID(s) for Data Forwarding' contains the DL GTP-U tunnel endpoint parameters to the eNodeB. If 'Indirect Forwarding' applies the IEs 'Address(es) and TEID(s) for Data Forwarding' contain the DL GTP-U tunnel endpoint parameters to the Serving GW. NOTE 5: The Source SGSN acts as the old SGSN. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | D.3.8.2 |
2,865 | 6.2 Identification by a permanent identity | The mechanism described in here allows the identification of a user on the radio path by means of the permanent subscriber identity (IMSI). The mechanism should be invoked by the serving network whenever the user cannot be identified by means of a temporary identity. In particular, it should be used when the user registers for the first time in a serving network, or when the serving network cannot retrieve the IMSI from the TMSI by which the user identifies itself on the radio path. The mechanism is illustrated in Figure 4. Figure 4: Identification by the permanent identity The mechanism is initiated by the visited VLR/SGSN that requests the user to send its permanent identity. The user's response contains the IMSI in cleartext. This represents a breach in the provision of user identity confidentiality. | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | 6.2 |
2,866 | 5.3.4.3.2 Preferred band(s) per data radio bearer(s) | The NG-RAN may prefer to use specific radio resources per data radio bearer(s), e.g. depending on the Network Slices associated to the data radio bearer used by the UE. The UE idle mode mobility control and priority-based reselection mechanism operates as described in clause 5.3.4.3.1, and when UP resources are activated e.g. for a specific S-NSSAI the NG-RAN can use local policies to decide on what specific radio resources to use for the associated data radio bearer(s). A UE may be served by a set of data radio bearers which may be served by cells in different bands, selected based on RRM policies. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.3.4.3.2 |
2,867 | 4.4.1 E-UTRAN | E-UTRAN is described in more detail in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [5]. In addition to the E-UTRAN functions described in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [5], E-UTRAN functions include: - Header compression and user plane ciphering and integrity protection (for user plane data sent across S1-U); - MME selection when no routing to an MME can be determined from the information provided by the UE; - UL bearer level rate enforcement based on UE-AMBR and MBR via means of uplink scheduling (e.g. by limiting the amount of UL resources granted per UE over time); - DL bearer level rate enforcement based on UE-AMBR; - UL and DL bearer level admission control; - Transport level packet marking in the uplink, e.g. setting the DiffServ Code Point, based on the QCI, and optionally the ARP priority level, of the associated EPS bearer; - ECN-based congestion control. | 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.4.1 |
2,868 | 9.11.3.55 UE's usage setting | The purpose of the UE's usage setting information element is to provide the network with the UE's usage setting as defined in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15]. The network uses the UE's usage setting to select the RFSP index. The UE's usage setting information element is coded as shown in figure 9.11.3.55.1 and table 9.11.3.55.1. The UE's usage setting is a type 4 information element with a length of 3 octets. Figure 9.11.3.55.1: UE's usage setting information element Table 9.11.3.55.1: UE's usage setting 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.55 |
2,869 | 5.10.3.2 Multicast MRB establishment | Upon establishment of a multicast MRB, the UE shall: 1> establish a PDCP entity and an RLC entity i n accordance with MRB-InfoBroadcast for this multicast MRB included in the MBSMulticastConfiguration message and the configuration specified in 9.1.1.7; 1> configure the MAC layer in accordance with the mtch-SchedulingInfo (if included); 1> configure the physical layer in accordance with the mbs-SessionInfoList, searchSpaceMulticastMTCH, and pdsch-ConfigMTCH, applicable for the multicast MRB; 1> if an SDAP entity with the received mbs-SessionId does not exist: 2> establish an SDAP entity as specified in TS 37.324[ Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Service Data Adaptation Protocol (SDAP) specification ] [24] clause 5.1.1; 2> indicate the establishment of the user plane resources for the mbs-SessionId to upper layers; 1> receive DL-SCH on the cell where the MBSMulticastConfiguration message was received for the established multicast MRB using g-RNTI and mtch-SchedulingInfo (if included) in this message for this MBS multicast service. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.10.3.2 |
2,870 | 8.2.3.2.2 Minimum Requirement for TDD PCell | For TDD FDD CA with TDD PCell and 2DL CCs, the requirements are specified in Table 8.2.3.2.2-4 based on single carrier requirement specified in Table 8.2.3.2.2-2 and Table 8.2.3.2.2-3, with the addition of the parameters in Table 8.2.3.2.2-1 and the downlink physical channel setup according to Annex C.3.2. The purpose is to verify the performance of large delay CDD with 2 transmitter antennas. For TDD FDD CA with TDD PCell and 3DL CCs, the requirements are specified in Table 8.2.3.2.2-5 based on single carrier requirement specified in Table 8.2.3.2.2-2 and Table 8.2.3.2.2-3, with the addition of the parameters in Table 8.2.3.2.2-1 and the downlink physical channel setup according to Annex C.3.2. The purpose is to verify the performance of large delay CDD with 2 transmitter antennas. For TDD FDD CA with TDD PCell and 4DL CCs, the requirements are specified in Table 8.2.3.2.2-6 based on single carrier requirement specified in Table 8.2.3.2.2-2 and Table 8.2.3.2.2-3, with the addition of the parameters in Table 8.2.3.2.2-1 and the downlink physical channel setup according to Annex C.3.2. The purpose is to verify the performance of large delay CDD with 2 transmitter antennas. For TDD FDD CA with TDD PCell and 5DL CCs, the requirements are specified in Table 8.2.3.2.2-7 based on single carrier requirement specified in Table 8.2.3.2.2-2 and Table 8.2.3.2.2-3, with the addition of the parameters in Table 8.2.3.2.2-1 and the downlink physical channel setup according to Annex C.3.2. The purpose is to verify the performance of large delay CDD with 2 transmitter antennas. For TDD FDD CA with TDD PCell and 6DL CCs, the requirements are specified in Table 8.2.3.2.2-8 based on single carrier requirement specified in Table 8.2.3.2.2-2 and Table 8.2.3.2.2-3, with the addition of the parameters in Table 8.2.3.2.2-1 and the downlink physical channel setup according to Annex C.3.2. The purpose is to verify the performance of large delay CDD with 2 transmitter antennas. For TDD FDD CA with TDD PCell and 7DL CCs, the requirements are specified in Table 8.2.3.2.2-9 based on single carrier requirement specified in Table 8.2.3.2.2-2 and Table 8.2.3.2.2-3, with the addition of the parameters in Table 8.2.3.2.2-1 and the downlink physical channel setup according to Annex C.3.2. The purpose is to verify the performance of large delay CDD with 2 transmitter antennas. The test coverage for different number of component carriers is defined in 8.1.2.4. Table 8.2.3.2.2-1: Test Parameters for Large Delay CDD (FRC) for CA Table 8.2.3.2.2-2: Single carrier performance with different bandwidths for multiple CA configurations for FDD SCell (FRC) Table 8.2.3.2.2-3: Single carrier performance with different bandwidths for multiple CA configurations for TDD PCell and SCell (FRC) Table 8.2.3.2.2-4: Minimum performance for multiple CA configurations with 2DL CCs (FRC) Table 8.2.3.2.2-5: Minimum performance for multiple CA configurations with 3DL CCs (FRC) Table 8.2.3.2.2-6: Minimum performance for multiple CA configurations with 4DL CCs (FRC) Table 8.2.3.2.2-7: Minimum performance for multiple CA configurations with 5DL CCs (FRC) Table 8.2.3.2.2-8: Minimum performance for multiple CA configurations with 6DL CCs (FRC) Table 8.2.3.2.2-9: Minimum performance for multiple CA configurations with 7DL CCs (FRC) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.2.3.2.2 |
2,871 | 5.8.5.14 TSC Management Information | The following table describes the TSC Management Information Container (TSC MIC) that includes UMIC, PMIC and the associated NW-TT port number. The SMF may include the notification target address for PMIC/UMIC UPF event provided by the PCF in the TSC Management Information sent to UPF if the UPF supports the related redirect reporting via Nupf. If the notification target address for PMIC/UMIC UPF event is provided by the SMF, the UPF may directly report TSC management information to the TSNAF or TSCTSF using Nupf_EventExposure_Notify service operation described in clause 7.2.29. Table 5.8.5.14-1: TSC Management Information Container | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.8.5.14 |
2,872 | 9.3.6 Minimum requirement (With multiple CSI processes) | The purpose of the test is to verify the reporting accuracy of the CQI and the UE processing capability for multiple CSI processes. Each CSI process is associated with a CSI-RS resource and a CSI-IM resource as shown in Table -1. For UE supports one CSI process, CSI process 2 is configured and the corresponding requirements shall be fulfilled. For UE supports three CSI processes, CSI processes 0, 1 and 2 are configured and the corresponding requirements shall be fulfilled. For UE supports four CSI processes, CSI processes 0, 1, 2 and 3 are configured and the corresponding requirements shall be fulfilled. Table -1: Configuration of CSI processes | 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.6 |
2,873 | 6.1.3.3.4 Abnormal cases | a) Expiry of timers On the network side: On the first expiry of timer T3386, the network shall resend the MODIFY PDP CONTEXT REQUEST message reset and restart timer T3386. This retransmission is repeated four times, i.e. on the fifth expiry of timer T3386, the network may continue to use the previously negotiated QoS and TFT, or it may initiate the PDP context deactivation procedure. In the MS: On the first expiry of timer T3381, the MS shall resend the MODIFY PDP CONTEXT REQUEST message reset and restart timer T3381. This retransmission is repeated four times, i.e. on the fifth expiry of timer T3381, the MS may continue to use the previously negotiated QoS and TFT, or it may initiate the PDP context deactivation procedure. b) Collision of MS and Network initiated PDP Context Modification Procedures A collision of a MS and network initiated PDP context modification procedures is identified by the MS if a MODIFY PDP CONTEXT REQUEST message is received from the network after the MS has sent a MODIFY PDP CONTEXT REQUEST message itself, and both messages contain the same TI and the MS has not yet received a MODIFY PDP CONTEXT ACCEPT message from the network. A collision is detected by the network in case a MODIFY PDP CONTEXT REQUEST message is received from the MS with the same TI as the MODIFY PDP CONTEXT REQUEST message sent to the MS. In the case of such a collision, the network initiated PDP context modification shall take precedence over the MS initiated PDP context modification. The MS shall terminate internally the MS initiated PDP context modification procedure, enter the state PDP-Active and proceed with the network initiated PDP context modification procedure by sending a MODIFY PDP CONTEXT ACCEPT message. The network shall ignore the MODIFY PDP CONTEXT REQUEST message received in the state PDP-MODIFY-PENDING. The network shall proceed with the network initiated PDP context modification procedure as if no MODIFY PDP CONTEXT REQUEST message was received from the MS. c) Collision of MS initiated PDP Context Modification Procedures and Network initiated Deactivate PDP Context Request Procedures A collision of a MS initiated PDP context modification procedures and a network initiated PDP context deactivation procedures is identified by the MS if a DEACTIVATE PDP CONTEXT REQUEST message is received from the network after the MS has sent a MODIFY PDP CONTEXT REQUEST message, and the MS has not yet received a MODIFY PDP CONTEXT ACCEPT message from the network. In the case of such a collision, the network initiated PDP context deactivation shall take precedence over the MS initiated PDP context modification. The MS shall terminate internally the MS initiated PDP context modification procedure, and proceed with the network initiated PDP context deactivation procedure by sending a DEACTIVATE PDP CONTEXT ACCEPT, enter the state PDP-INACTIVE. The network shall ignore the MODIFY PDP CONTEXT REQUEST message received in the state PDP-INACTIVE-PENDING. The network shall proceed with the network initiated PDP context deactivation procedure as if no MODIFY PDP CONTEXT REQUEST message was received from the MS. d) MS initiated PDP context modification procedure for a PDN connection established for emergency bearer services. The network shall reply with a MODIFY PDP CONTEXT REJECT message with a cause code indicating "activation rejected by GGSN, Serving GW or PDN GW". The TFT in the MODIFY PDP CONTEXT REQUEST message is checked for different types of TFT IE errors as follows: a) Semantic errors in TFT operations: 1) When the TFT operation is "Create a new TFT" and there is already an existing TFT for the PDP context. 2) When the TFT operation is an operation other than "Create a new TFT" and there is no TFT for the PDP context. 3) When the TFT operation is "Delete existing TFT" and the TFT includes packet filters created by the receiver of the request. 4) When the TFT operation is "Delete existing TFT" and there is already another PDP context with the same PDP address and APN without a TFT. 5) When the TFT operation is "Delete existing TFT" and the PDP context is not the default PDP context. 6) When the TFT operation is "Delete packet filters from existing TFT" or "Replace packet filters in existing TFT" and at least one of the packet filters to be deleted or replaced was created by the receiver of the request. 7) When the TFT operation is "Delete packet filters from existing TFT" and this operation would render the TFT empty. In the above cases the network shall perform the following actions: In case 1) the network shall further process the new activation request and, if it was processed successfully, delete the old TFT. In case 2) the network shall: - further process the new request and, if no error according to list items b), c), and d) was detected, consider the TFT as successfully deleted, if the TFT operation is "Delete existing TFT" or "Delete packet filters from existing TFT"; and - process the new request as an activation request, if the TFT operation is "Add packet filters in existing TFT" or "Replace packet filters in existing TFT". In case 3) the network shall reject the modification request with cause "semantic error in the TFT operation". In case 4) the network shall either: - reject the modification request with cause "semantic error in the TFT operation"; or - optionally, if the BCM is "MS only" and the packet filters in the TFT do not have any explicit direction information, i.e. the packet filter direction parameter is set to "00", process the new deletion request and, after successful deletion of the TFT, deactivate the old PDP context with the same PDP address and APN without a TFT by explicit peer-to-peer signalling between the MS and the network. - In case 5) the network shall either: - reject the modification request with cause "semantic error in the TFT operation"; or - optionally, if the BCM is "MS only" and the packet filters in the TFT do not have any explicit direction information, i.e. the packet filter direction parameter is set to "00", process the new deletion request. In case 6) the network shall reject the modification request with cause "semantic error in the TFT operation". In case 7) the network shall: i) if the PDP context is the default PDP context, further process the new request and, if no error according to list items b), c), and d) was detected, delete the existing TFT. After successful deletion of the TFT, if there was already another PDP context with the same PDP address and APN without a TFT, the network shall deactivate this old PDP context without a TFT by explicit peer-to-peer signalling between the MS and the network; and ii) if the PDP context is not the default PDP context, further process the new request and, if no error according to list items b), c), and d) was detected, delete the existing TFT. After successful deletion of the TFT, the network shall deactivate the modified PDP context by explicit peer-to-peer signalling between the MS and the network. The network need not respond with a Modify PDP Context Accept message. In the above cases the MS shall perform the following actions: In case 1) the MS shall further process the new activation request and, if it was processed successfully, delete the old TFT. In case 2) the MS shall: - further process the new request and, if no error according to list items b), c), and d) was detected, consider the TFT as successfully deleted, if the TFT operation is "Delete existing TFT" or "Delete packet filters from existing TFT"; and - process the new request as an activation request, if the TFT operation is "Add packet filters in existing TFT" or "Replace packet filters in existing TFT". In case 3) the MS shall reject the modification request with cause "semantic error in the TFT operation". In case 4) the MS shall either: A) reject the modification request with cause "semantic error in the TFT operation"; or B) optionally, to support networks compliant with earlier versions of the protocol, process the new deletion request and, after successful deletion of the TFT, deactivate the old PDP context with the same PDP address and APN without a TFT by explicit peer-to-peer signalling between the MS and the network. NOTE 1: This case is not expected to occur for a network implementing this version of the protocol, because at least one of the two PDP contexts without TFT will be a non-default PDP context. But for Bearer Control Mode 'MS/NW' such a network does not support an initial configuration where the old PDP context without TFT is a non-default PDP context, and the network will not attempt to delete the TFT of a non-default PDP context. If during a previous inter-system change from S1 mode to A/Gb or Iu mode the default PDP context linked to the PDP context to be modified was mapped from an EPS bearer context, the MS shall follow option A. In case 5) the MS shall either: A) reject the modification request with cause "semantic error in the TFT operation"; or B) optionally, to support networks compliant with earlier versions of the protocol, process the new deletion request. NOTE 2: A network implementing this version of the protocol will not attempt to delete the TFT of a non-default PDP context. If during a previous inter-system change from S1 mode to A/Gb or Iu mode the default PDP context linked to the PDP context to be modified was mapped from an EPS bearer context, the MS shall follow option A. In case 6) the MS shall reject the modification request with cause "semantic error in the TFT operation". In case 7) the MS shall: i) if the PDP context is the default PDP context, further process the new request and, if no error according to list items b), c), and d) was detected, delete the existing TFT. After successful deletion of the TFT, if there was already another PDP context with the same PDP address and APN without a TFT, the MS shall deactivate this old PDP context without a TFT by explicit peer-to-peer signalling between the MS and the network; and ii) if the PDP context is not the default PDP context, either - further process the new request and, if no error according to list items b), c), and d) was detected, delete the existing TFT. After successful deletion of the TFT, the MS shall deactivate the modified PDP context by explicit peer-to-peer signalling between the MS and the network. The MS need not send a Modify PDP Context Accept message; or - reject the modification request with cause "semantic error in the TFT operation". b) Syntactical errors in TFT operations: 1) When the TFT operation is an operation other than "Delete existing TFT" or "No TFT operation" and the packet filter list in the TFT IE is empty. 2) When the TFT operation is "Delete existing TFT" or "No TFT operation" with a non-empty packet filter list in the TFT IE. 3) When the TFT operation is "Replace packet filters in existing TFT" and the packet filter to be replaced does not exist in the original TFT. 4) When the TFT operation is "Delete packet filters from existing TFT" and the packet filter to be deleted does not exist in the original TFT. 5) Void. 6) When there are other types of syntactical errors in the coding of the TFT IE, such as a mismatch between the number of packet filters subfield, and the number of packet filters in the packet filter list. 7) When the TFT operation is "No TFT operation" with an empty parameters list. In case 3) the network shall not diagnose an error, further process the replace request and, if no error according to list items c) and d) was detected, include the packet filters received to the existing TFT. In case 4) the network shall not diagnose an error, further process the deletion request and, if no error according to list items c) and d) was detected, consider the respective packet filter as successfully deleted. Otherwise the network shall reject the modification request with cause "syntactical error in the TFT operation". In case 3) the MS shall not diagnose an error, further process the replace request and, if no error according to list items c) and d) was detected, include the packet filters received to the existing TFT. In case 4) the MS shall not diagnose an error, further process the deletion request and, if no error according to list items c) and d) was detected, consider the respective packet filter as successfully deleted. Otherwise the MS shall reject the modification request with cause "syntactical error in the TFT operation". NOTE 2a: An implementation that strictly follows packet filter list as defined in subclause 10.5.6.12 might not detect case 2). c) Semantic errors in packet filters: 1) When a packet filter consists of conflicting packet filter components which would render the packet filter ineffective, i.e. no IP packet will ever fit this packet filter. How the receiver determines a semantic error in a packet filter is outside the scope of the present document. 2) When the resulting TFT, which is not assigned to the default PDP context, does not contain any packet filter applicable for the uplink direction. NOTE 3: When BCM is 'MS only', the MS is allowed to include a TFT with packet filters without any explicit direction information, i.e. with value "00", and such packet filters are applicable for both uplink and downlink directions. The network shall reject the modification request with cause "semantic errors in packet filter(s)". The MS shall reject the modification request with cause "semantic errors in packet filter(s)". d) Syntactical errors in packet filters: 1) When the TFT operation is "Create a new TFT" or "Add packet filters to existing TFT" and two or more packet filters in the resultant TFT would have identical packet filter identifiers. 2) When the TFT operation is "Create a new TFT" or "Add packet filters to existing TFT" or "Replace packet filters in existing TFT" and two or more packet filters in all TFTs associated with this PDP address and APN would have identical packet filter precedence values. 3) When there are other types of syntactical errors in the coding of packet filters, such as the use of a reserved value for a packet filter component identifier. In case 1), if two or more packet filters with identical packet filter identifiers are contained in the new request, the network shall reject the modification request with cause "syntactical errors in packet filter(s)". Otherwise, the network shall not diagnose an error, further process the new request and, if it was processed successfully, delete the old packet filters which have the identical packet filter identifiers. In case 2) the network shall not diagnose an error, further process the new request and, if it was processed successfully, delete the old packet filters which have identical filter precedence values. Furthermore, by means of explicit peer-to-peer signalling between the MS and the network, the network shall deactivate the PDP context(s) for which it has deleted the packet filters. Otherwise the network shall reject the modification request with cause "syntactical errors in packet filter(s)". In case 1), if two or more packet filters with identical packet filter identifiers are contained in the new request, the MS shall reject the modification request with cause "syntactical errors in packet filter(s)". Otherwise, the MS shall not diagnose an error, further process the new request and, if it was processed successfully, delete the old packet filters which have the identical packet filter identifiers. In case 2) the MS shall not diagnose an error, further process the new request and, if it was processed successfully, delete the old packet filters which have identical filter precedence values. Furthermore, the MS shall deactivate the PDP context(s) for which it has deleted the packet filters by means of explicit peer-to-peer signalling between the MS and the network,. Otherwise, the MS shall reject the modification request with cause "syntactical errors in packet filter(s)". Figure 6.6/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Network initiated PDP context modification procedure Figure 6.7/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : MS initiated PDP context modification procedure | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.1.3.3.4 |
2,874 | 4 Frame structure | Throughout this specification, unless otherwise noted, the size of various fields in the time domain is expressed as a number of time units seconds. Downlink, uplink and sidelink transmissions are organized into radio frames with duration. Three radio frame structures are supported: - Type 1, applicable to FDD only, - Type 2, applicable to TDD only, - Type 3, applicable to LAA secondary cell operation only. NOTE: LAA secondary cell operation only applies to frame structure type 3. Transmissions in multiple cells can be aggregated where up to 31 secondary cells can be used in addition to the primary cell. Unless otherwise noted, the description in this specification applies to each of the up to 32 serving cells. In case of multi-cell aggregation, different frame structures can be used in the different serving cells. | 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 | 4 |
2,875 | B.1 Causes related to nature of request | Cause #8 – Operator Determined Barring This ESM cause is used by the network to indicate that the requested service was rejected by the MME due to Operator Determined Barring. Cause #26 – Insufficient resources This ESM cause is used by the UE or by the network to indicate that the requested service cannot be provided due to insufficient resources. If EPS counting is required for a network slice, this ESM cause is used by the network to indicate that the requested service cannot be provided due to maximum number of UEs registered to a specific network slice reached or maximum number of PDU sessions on a specific network slice reached. Cause #27 – Missing or unknown APN This ESM cause is used by the network to indicate that the requested service was rejected by the external packet data network because the access point name was not included although required or if the access point name could not be resolved. Cause #28 – Unknown PDN type This ESM cause is used by the network to indicate that the requested service was rejected by the external packet data network because the PDN type could not be recognised. Cause #29 – User authentication or authorization failed This ESM cause is used by the network to indicate that the requested service was rejected by the external packet data network due to a failed user authentication, revoked by the external packet data network, or the required user authentication cannot be performed. Cause #30 – Request rejected by Serving GW or PDN GW This ESM cause is used by the network to indicate that the requested service or operation or the request for a resource was rejected by the Serving GW or PDN GW. Cause #31 – Request rejected, unspecified This ESM cause is used by the network or by the UE to indicate that the requested service or operation or the request for a resource was rejected due to unspecified reasons. Cause #32 – Service option not supported This ESM cause is used by the network when the UE requests a service which is not supported by the PLMN. Cause #33 – Requested service option not subscribed This ESM cause is sent when the UE requests a service option for which it has no subscription. Cause #34 – Service option temporarily out of order This ESM cause is sent when the network cannot service the request because of temporary outage of one or more functions required for supporting the service. Cause #35 – PTI already in use This ESM cause is used by the network to indicate that the PTI included by the UE is already in use by another active UE requested procedure for this UE. Cause #36 – Regular deactivation This ESM cause is used to indicate a regular UE or network initiated release of EPS bearer resources. Cause #37 – EPS QoS not accepted This ESM cause is used by the network if the new EPS QoS cannot be accepted that was indicated in the UE request. Cause #38 – Network failure This ESM cause is used by the network to indicate that the requested service was rejected due to an error situation in the network. Cause #39 – Reactivation requested This ESM cause is used by the network to request a PDN connection reactivation. Cause #41 – Semantic error in the TFT operation. This ESM cause is used by the network or the UE to indicate that the requested service was rejected due to a semantic error in the TFT operation included in the request. Cause #42 – Syntactical error in the TFT operation. This ESM cause is used by the network or the UE to indicate that the requested service was rejected due to a syntactical error in the TFT operation included in the request. Cause #43 – Invalid EPS bearer identity This ESM cause is used by the network or the UE to indicate that the EPS bearer identity value provided to it is not a valid value for the received message or the EPS bearer context identified by the linked EPS bearer identity IE in the request is not active. Cause #44 – Semantic errors in packet filter(s) This ESM cause is used by the network or the UE to indicate that the requested service was rejected due to one or more semantic errors in packet filter(s) of the TFT included in the request. Cause #45 – Syntactical error in packet filter(s) This ESM cause is used by the network or the UE to indicate that the requested service was rejected due to one or more syntactical errors in packet filter(s) of the TFT included in the request. Cause #47 – PTI mismatch This ESM cause is used by the UE to indicate that the PTI value which is included in the ESM message that the UE receives does not match a PTI in use. Cause #49 – Last PDN disconnection not allowed This ESM cause is used by the network, in case of EMM-REGISTERED without PDN connection is not supported by the UE or the MME, to indicate that the UE requested PDN disconnection procedure on the last remaining PDN connection is not allowed. Cause #50 – PDN type IPv4 only allowed This ESM cause is used by the network to indicate that only PDN type IPv4 is allowed for the requested PDN connectivity. Cause #51 – PDN type IPv6 only allowed This ESM cause is used by the network to indicate that only PDN type IPv6 is allowed for the requested PDN connectivity. Cause #52 – single address bearers only allowed This ESM cause is used by the network to indicate that the requested PDN connectivity is accepted with the restriction that only single IP version bearers are allowed. Cause #53 – ESM information not received This ESM cause is used by the network to indicate that the PDN connectivity procedure was rejected due to the ESM information was not received. Cause #54 – PDN connection does not exist This ESM cause is used by the network at handover of a PDN connection from a non-3GPP access network connected to EPC, or at interworking of a PDU session from non-3GPP access network connected to 5GCN or from NG-RAN connected to 5GCN to a PDN connection, to indicate that the MME does not have any information about the requested PDN connection. Cause #55 – Multiple PDN connections for a given APN not allowed This ESM cause is used by the network to indicate that the PDN connectivity procedure was rejected due to multiple PDN connections for a given APN are not allowed. Cause #56 – Collision with network initiated request This ESM cause is used by the network to indicate that the network has already initiated the activation, modification or deactivation of bearer resources which was requested by the UE. Cause #57 – PDN type IPv4v6 only allowed This ESM cause is used by the network to indicate that only PDN types IPv4, IPv6 or IPv4v6 are allowed for the requested PDN connectivity. Cause #58 – PDN type non IP only allowed This ESM cause is used by the network to indicate that only PDN type non IP is allowed for the requested PDN connectivity. Cause #59 – Unsupported QCI value This ESM cause is used by the network if the QCI indicated in the UE request cannot be supported. Cause #60 – Bearer handling not supported This ESM cause is used by the network to indicate that the procedure requested by the UE was rejected because the bearer handling is not supported. Cause #61 – PDN type Ethernet only allowed This ESM cause is used by the network to indicate that only PDN type Ethernet is allowed for the requested PDN connectivity. Cause #65 – Maximum number of EPS bearers reached This ESM cause is used by the network to indicate that the procedure requested by the UE was rejected as the network has reached the maximum number of simultaneously active EPS bearer contexts for the UE. Cause #66 – Requested APN not supported in current RAT and PLMN combination This ESM cause is used by the network to indicate that the procedure requested by the UE was rejected as the requested APN is not supported in the current RAT and PLMN. Cause #81 – Invalid PTI value This ESM cause is used by the network or UE to indicate that the PTI provided to it is unassigned or reserved. Cause #112 – APN restriction value incompatible with active EPS bearer context. This ESM cause is used by the network to indicate that the EPS bearer context(s) have an APN restriction value that is not allowed in combination with a currently active EPS bearer context. Restriction values are defined in 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [4]. Cause #113 – Multiple accesses to a PDN connection not allowed This ESM cause is used by the network to indicate that multiple accesses to a PDN connection for NBIFOM is not allowed. | 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 | B.1 |
2,876 | 5.3 GTP-C header for Echo and Version Not Supported Indication messages | The GTPv2-C message header for the Echo Request, Echo Response and Version Not Supported Indication messages shall not contain the TEID field, but shall contain the Sequence Number fields, followed by one spare octet as depicted in figure 5.3-1. The spare bits shall be set to zero by the sender and ignored by the receiver. For the Version Not Supported Indication message header, the Sequence Number may be set to any number and shall be ignored by the receiver. Figure 5.3-1: The format of Echo and Version Not Supported Indication messages Header | 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 | 5.3 |
2,877 | 10.5.5.28 Voice domain preference and UE's usage setting | The purpose of the Voice domain preference and UE's usage setting information element is to provide the network with the UE's usage setting and the voice domain preference for WB-S1 mode. The network uses the UE's usage setting and the voice domain preference for E-UTRAN (see 3GPP TS 24.167[ 3GPP IMS Management Object (MO); Stage 3 ] [13B]) to select the RFSP index. The UE's usage setting bit indicates the value configured on the ME as defined in 3GPP TS 23.221[ Architectural requirements ] [131]. The voice domain preference for E-UTRAN bit indicates the value configured on the ME of the Voice domain preference for E-UTRAN as defined in 3GPP TS 24.167[ 3GPP IMS Management Object (MO); Stage 3 ] [134]. The Voice domain preference and UE's usage setting information element is coded as shown in figure 10.5.151A/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.166A/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Figure 10.5.151A/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Voice domain preference and UE's usage setting information element Table 10.5.166A/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Voice domain preference and UE's usage setting information element | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 10.5.5.28 |
2,878 | 6.1.3.8 Activation/Deactivation MAC Control Elements | The Activation/Deactivation MAC control element of one octet is identified by a MAC PDU subheader with LCID as specified in table 6.2.1-1. It has a fixed size and consists of a single octet containing seven C-fields and one R-field. The Activation/Deactivation MAC control element with one octet is defined as follows (figure 6.1.3.8-1). The Activation/Deactivation MAC control element of four octets is identified by a MAC PDU subheader with LCID as specified in table 6.2.1-1. It has a fixed size and consists of a four octets containing 31 C-fields and one R-field. The Activation/Deactivation MAC control element of four octets is defined as follows (figure 6.1.3.8-2). For the case with no serving cell with a ServCellIndex, as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8] larger than 7, Activation/Deactivation MAC control element of one octet is applied, otherwise Activation/Deactivation MAC control element of four octets is applied. For the case that Activation/Deactivation MAC control element is received and Hibernation MAC control element is not received: - Ci: if there is an SCell configured with SCellIndex i as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8], this field indicates the activation/deactivation status of the SCell with SCellIndex i, else the MAC entity shall ignore the Ci field. When the Ci field is set to "1", SCell with SCellIndex i shall be activated if it is in already activated state or deactivated state, otherwise the Ci field set to "1" shall be ignored. The Ci field is set to "0" to indicate that the SCell with SCellIndex i shall be deactivated; - R: Reserved bit, set to "0". For the case that both Activation/Deactivation MAC control element and Hibernation MAC control element are received, see clause 6.1.3.15. Figure 6.1.3.8-1: Activation/Deactivation MAC control element of one octet Figure 6.1.3.8-2: Activation/Deactivation MAC control element of four octets | 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.8 |
2,879 | 6.2.2F UE maximum output power for category NB1 and NB2 | Category NB1 and NB2 UE Power Classes are specified in Table 6.2.2F-1 and define the maximum output power for any transmission bandwidth within the category NB1 and NB2 channel bandwidth. For 3.75 kHz sub-carrier spacing the maximum output power is defined as mean power of measurement which period is atleast one slot (2ms) excluding the 2304Ts gap when UE is not transmitting. For 15kHz sub-carrier spacing the maximum output power is defined as mean power of measurement which period is atleast one sub-frame (1ms). Table 6.2.2F-1: UE Power Class | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.2.2F |
2,880 | 4.7.1 PDN connectivity service | The Evolved Packet System provides connectivity between a UE and a PLMN external packet data network. This is referred to as PDN Connectivity Service. The IP PDN Connectivity Service s the transport of traffic flow aggregate(s), consisting of one or more Service Data Flows (SDFs). NOTE: The concept of SDF is defined in the context of PCC, TS 23.203[ Policy and charging control architecture ] [6], and is not explicitly visible in the NAS signalling. A PDN connection to an SCEF has the following characteristics: - It is only supported for WB-EUTRA, LTE-M and NB-IoT RAT types; - It applies only when Control Plane CIoT EPS Optimisation are applicable; - It does not support the transport of traffic flow aggregate(s); - It does not support Emergency Services. | 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.7.1 |
2,881 | 8.13.3.1.1 Minimum Requirement for FDD PCell | The purpose of these tests is to verify the closed loop rank-two performance with wideband and frequency selective precoding. For TDD FDD CA with FDD PCell and 2DL CCs, the requirements are specified in Table 8.13.3.1.1-4 based on single carrier requirement specified in Table 8.13.3.1.1-2 and Table 8.13.3.1.1-3, with the addition of the parameters in Table 8.13.3.1.1-1 and the downlink physical channel setup according to Annex C.3.2. For TDD FDD CA with FDD PCell and 3DL CCs, the requirements are specified in Table 8.13.3.1.1-5 based on single carrier requirement specified in Table 8.13.3.1.1-2 and Table 8.13.3.1.1-3, with the addition of the parameters in Table 8.13.3.1.1-1 and the downlink physical channel setup according to Annex C.3.2. For TDD FDD CA with FDD PCell and 4DL CCs, the requirements are specified in Table 8.13.3.1.1-6 based on single carrier requirement specified in Table 8.13.3.1.1-2 and Table 8.13.3.1.1-3, with the addition of the parameters in Table 8.13.3.1.1-1 and the downlink physical channel setup according to Annex C.3.2. For TDD FDD CA with FDD PCell and 5DL CCs, the requirements are specified in Table 8.13.3.1.1-7 based on single carrier requirement specified in Table 8.13.3.1.1-2 and Table 8.13.3.1.1-3, with the addition of the parameters in Table 8.13.3.1.1-1 and the downlink physical channel setup according to Annex C.3.2. The test coverage for different number of component carriers is defined in 8.1.2.4. Table 8.13.3.1.1-1: Test Parameters for Multi-Layer Spatial Multiplexing (FRC) for CA Table 8.13.3.1.1-2: Single carrier performance with different bandwidths for multiple CA configurations for FDD PCell and SCell (FRC) Table 8.13.3.1.1-3: Single carrier performance with different bandwidths for multiple CA configurations for TDD SCell (FRC) Table 8.13.3.1.1-4: Minimum performance for multiple CA configurations with 2DL CCs (FRC) Table 8.13.3.1.1-5: Minimum performance for multiple CA configurations with 3DL CCs (FRC) Table 8.13.3.1.1-6: Minimum performance for multiple CA configurations with 4DL CCs (FRC) Table 8.13.3.1.1-7: Minimum performance for multiple CA configurations with 5DL CCs (FRC) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.13.3.1.1 |
2,882 | 13.2.4.6 Protecting IPX modifications using JSON Web Signature (JWS) | The IPX providers shall use JSON Web Signature (JWS) as specified in RFC 7515 [45] for the protection of IPX provider modified attributes. The mechanism described in this clause uses signatures, i.e. asymmetric methods, with private/public key pairs. More specifically, when an IPX node modifies one or more attributes of the original HTTP message and creates a modifiedDataToIntegrityProtect object to record its modifications, it shall use JWS to integrity protect the modifiedDataToIntegrityProtect object. The IPX provider shall use its private key as input to JWS for generating the signature representing the contents of the modifiedDataToIntegrityProtect object. The "alg" parameter in the JOSE header indicates the chosen signature algorithm. The 3GPP profile for supported algorithms is described in clause 13.2.4.9. The Flattened JWS JSON Serialization syntax shall be used to represent JWS as a JSON object. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 13.2.4.6 |
2,883 | 5.4.3 PDN GW initiated bearer modification without bearer QoS update | The bearer modification procedure without bearer QoS update is used to update the TFT for an active default or dedicated bearer, to modify the APN-AMBR, to retrieve User Location from the MME, to inform PCO to UE or to instruct the MME (e.g. to activate/deactivate the location reporting). The procedure for a GTP based S5/S8 is depicted in figure 5.4.3-1. In this procedure there is no need to update the underlying radio bearer(s). This procedure may be triggered if the APN-AMBR is changed by the PCRF/PDN GW. Figure 5.4.3-1: Bearer Modification Procedure without Bearer QoS Update NOTE 1: Steps 3-8 are common for architecture variants with GTP based S5/S8 and PMIP-based S5/S8. For an PMIP-based S5/S8, procedure steps (A) and (B) are defined in TS 23.402[ Architecture enhancements for non-3GPP accesses ] [2]. Steps 1, 2, 9 and 10 concern GTP based S5/S8. Steps 3-8 may also be used within the HSS Initiated Subscribed QoS Modification. 1. If dynamic PCC is deployed, the PCRF sends a PCC decision provision (QoS policy) message to the PDN GW. This corresponds to the beginning of the PCRF-initiated IP-CAN Session Modification procedure or to the PCRF response in the PCEF initiated IP-CAN Session Modification procedure as defined in TS 23.203[ Policy and charging control architecture ] [6], up to the point that the PDN GW requests IP-CAN Bearer Signalling. The PCC decision provision message may indicate that User Location Information and/or UE Time Zone Information is to be provided to the PCRF as defined in TS 23.203[ Policy and charging control architecture ] [6]. If dynamic PCC is not deployed, the PDN GW may apply local QoS policy. 2. The PDN GW uses this QoS policy to determine that a service data flow shall be aggregated to or removed from an active bearer. The PDN GW generates the TFT and determines that no update of the EPS Bearer QoS is needed. The PDN GW then sends the Update Bearer Request (PTI, EPS Bearer Identity, APN-AMBR, TFT, Retrieve Location) message to the Serving GW. The Procedure Transaction Id (PTI) parameter is used when the procedure was initiated by a UE Requested Bearer Resource Modification procedure - see clause 5.4.5. "Retrieve Location" is indicated if requested by the PCRF. If the PDN GW initiated bearer modification procedure was triggered by a UE requested bearer resource modification procedure and if 3GPP PS Data Off UE Status was present in the Bearer Resource Command PCO, the PDN GW shall include the 3GPP PS Data Off Support Indication in the Update Bearer Request PCO. 3. The Serving GW sends the Update Bearer Request (PTI, EPS Bearer Identity, APN-AMBR, TFT, Retrieve Location) message to the MME. If the UE is in ECM-IDLE state (and extended idle mode DRX is not enabled) the MME will trigger the Network Triggered Service Request from step 3 (which is specified in clause 5.3.4.3). In that case the following steps 4-7 may be combined into Network Triggered Service Request procedure or be performed stand-alone. If both the PCO and the TFT are absent and the APN-AMBR has not been modified, the MME shall skip the following steps 4-7. If the UE is in ECM-IDLE state and extended idle mode DRX is enabled for the UE, the MME will trigger Network Triggered Service Request from step 3 (which is specified in clause 5.3.4.3) and start a timer which is configured to a value smaller than the GTP re-transmission timer. If the MME receives no response from the UE before the timer expires, the MME sends an Update Bearer Response with a rejection cause indicating that UE is temporarily not reachable due to power saving and then sets the internal flag Pending Network Initiated PDN Connection Signalling. The rejection is forwarded by the Serving GW to the PDN GW. In this case, the steps 4-9 are skipped. NOTE 2: If ISR is activated and the Serving GW does not have a downlink S1-U and the SGSN has notified the Serving GW that the UE has moved to PMM-IDLE or STANDBY state, the Serving GW sends Downlink Data Notification to trigger MME and SGSN to page the UE (as specified in clause 5.3.4.3) before sending the Update Bearer Request message. NOTE 3: The PCO can be set by the PDN GW in accordance with the TS 23.380[ IMS Restoration Procedures ] [75]. 4. The MME builds a Session Management Request message including the TFT, APN-AMBR, EPS Bearer Identity and a WLAN offloadability indication. The MME then sends a Downlink NAS Transport (Session Management Configuration) message to the eNodeB. If the APN AMBR has changed, the MME may also update the UE AMBR. And if the UE-AMBR is updated, the MME signal a modified UE-AMBR value to the eNodeB by using S1-AP UE Context Modification Procedure. The MME may include an indication whether the traffic of this PDN Connection is allowed to be offloaded to WLAN as described in clause 4.3.23. 5. The eNodeB sends the Direct Transfer (Session Management Request) message to the UE. The UE uses the uplink packet filter (UL TFT) to determine the mapping of traffic flows to the radio bearer. The UE stores the modified APN-AMBR value and sets the MBR parameter of the corresponding non-GBR PDP contexts (of this PDN connection) to the new value. The UE shall set its TIN to "GUTI" if the modified EPS bearer was established before ISR activation. 6. The UE NAS layer builds a Session Management Response including EPS Bearer Identity. The UE then sends a Direct Transfer (Session Management Response) message to the eNodeB. 7. The eNodeB sends an Uplink NAS Transport (Session Management Response) message to the MME. 8. If the procedure is performed without steps 4-7 and location retrieval is requested and the UE is ECM_CONNECTED and unless the MME is configured not to retrieve ECGI from the eNodeB under this condition, the MME uses the Location Reporting Procedure described in clause 5.9.1 to retrieve the ECGI from the eNodeB. The MME acknowledges the bearer modification to the Serving GW by sending an Update Bearer Response (EPS Bearer Identity, User Location Information (ECGI)) message. The MME includes the last known User Location information. NOTE 4: Based on operator policy and local regulation the MME may, instead of using the Location Reporting Procedure described in clause 5.9.1 to retrieve the ECGI from the eNodeB, use the last known User Location information obtained from e.g. attach procedure, tracking area update procedure, etc. 9. The Serving GW acknowledges the bearer modification to the PDN GW by sending an Update Bearer Response (EPS Bearer Identity, User Location Information (ECGI)) message. 10. If the bearer modification procedure was triggered by a PCC Decision Provision message from the PCRF, the PDN GW indicates to the PCRF whether the requested PCC decision (QoS policy) could be enforced or not by sending a Provision Ack message. This then allows the PCRF-Initiated IP-CAN Session Modification procedure or the PCEF initiated IP-CAN Session Modification procedure as defined in TS 23.203[ Policy and charging control architecture ] [6] to continue and eventually conclude, proceeding after the completion of IP-CAN bearer signalling. If requested by the PCRF the PDN GW indicates User Location Information and/or UE Time Zone Information to the PCRF as defined in TS 23.203[ Policy and charging control architecture ] [6]. If the bearer modification is rejected with a cause indicating that the UE is temporarily not reachable due to power saving, then the PDN GW re-attempts the same procedure after it receives the indication that the is UE available for end to end signalling in the subsequent Modify Bearer Request message. NOTE 5: The exact signalling of step 1 and 10 (e.g. for local break-out) is outside the scope of this specification. This signalling and its interaction with the bearer activation procedure are to be specified in TS 23.203[ Policy and charging control architecture ] [6]. Steps 1 and 10 are included here only for completeness. | 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.4.3 |
2,884 | 4.8.4A.1 Core network selection | A UE that supports CIoT optimizations performs core network selection (i.e. it selects EPC or 5GCN) if the lower layers have provided an indication that the current E-UTRA cell is connected to both EPC and 5GCN as specified in 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8]. When selecting a PLMN as described in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5], the UE shall select a core network type (EPC or 5GCN) based on: a) indication from the lower layers about the CIoT EPS optimizations supported in EPC; b) indication from the lower layers about the CIoT 5GS optimizations supported in 5GCN; c) the CIoT EPS optimizations supported by the UE; d) the CIoT 5GS optimizations supported by the UE; e) the UE's preferred CIoT network behaviour for EPC; and f) the UE's preferred CIoT network behaviour for 5GCN. The UE shall provide the selected core network type information to the lower layer during the initial registration procedure. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.8.4A.1 |
2,885 | 15.4 Support for Energy Saving 15.4.1 General | The aim of this function is to reduce operational expenses through energy savings. The function allows, for example in a deployment where capacity boosters can be distinguished from cells providing basic coverage, to optimize energy consumption enabling the possibility for an E-UTRA or NR cell providing additional capacity via single or dual connectivity, to be switched off when its capacity is no longer needed and to be re-activated on a need basis, or to support various adaptation techniques in time, frequency, spatial and power domains. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 15.4 |
2,886 | 6.7.3.4 Transitions from RRC_INACTIVE to RRC_CONNECTED states | At state transition from RRC_INACTIVE to RRC_CONNECTED, the source gNB/ng-eNB shall include the UE 5G security capabilities and the ciphering and integrity algorithms the UE was using with the source cell in the Xn-AP Retrieve UE Context Response message. The target gNB/ng-eNB shall check if it supports the received algorithms, if the target gNB/ng-eNB supports the received ciphering and integrity algorithms, the target gNB/ng-eNB shall check the received algorithms to its locally configured list of algorithms (this applies for both integrity and ciphering algorithms). If the target gNB/ng-eNB selects the same security algorithms, the target gNB/ng-eNB shall use the selected algorithms to derive RRC integrity and RRC encryption keys to protect the RRCResume message and send to the UE on SRB1. If the target gNB/ng-eNB does not support the received algorithms or if the target gNB/ng-eNB prefers to use different algorithms, the target gNB/ng-eNB shall send an RRCSetup message on SRB0 in order to proceed with RRC connection establishment as if the UE was in RRC_IDLE (fallback procedure) to the UE. Then the UE performs NAS based RRC recovery and negotiates a suitable algorithm with target gNB/ng-eNB via AS SMC procedure. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.7.3.4 |
2,887 | 6.3.2 Multiple registrations in same or different serving networks 6.3.2.0 General | There are two cases where the UE can be multiple registered in different PLMN's serving networks or in the same PLMN's serving networks. The first case is when the UE is registered in one PLMN serving network over a certain type of access (e.g. 3GPP) and is registered to another PLMN serving network over the other type of access (e.g. non-3GPP). The second case is where the UE is registered in the same AMF in the same PLMN serving network over both 3GPP and non-3GPP accesses. The UE will establish two NAS connections with the network in both cases. NOTE: The UE uses the same subscription credential(s) for multiple registrations in the same or different serving networks. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.3.2 |
2,888 | 5.2.3.2.5 UPDATE-NEEDED | The UE: - shall not send any user data; - shall not send signalling information, unless it is a service request a tracking area updating or combined tracking area updating procedure which is triggered: a) as a response to paging; NOTE: As an implementation option, the MUSIM UE is allowed to not respond to paging based on the information available in the paging message, e.g. voice service indication. b) upon request by the upper layers to establish a PDN connection for emergency bearer services; or c) upon a request from the upper layers for an MMTEL voice call, MMTEL video call, SMSoIP, SMS over NAS or SMS over S102; - shall perform cell selection/reselection according to 3GPP TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [21]; - shall enter the appropriate new substate as soon as the access is allowed in the selected cell for one of the access classes of the UE; and - if configured for eCall only mode as specified in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [17], shall perform the eCall inactivity procedure at expiry of timer T3444 or T3445 (see clause 5.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 | 5.2.3.2.5 |
2,889 | 4.3.2 Roaming architecture | Figure 4.3.2-1 represents the Roaming architecture with local breakout and Figure 4.3.2-2 represents the Roaming architecture with home-routed traffic for interworking between 5GS and EPC/E-UTRAN. Figure 4.3.2-1: Local breakout roaming architecture for interworking between 5GS and EPC/E-UTRAN NOTE 1: There can be another UPF (not shown in the figure above) between the NG-RAN and the UPF + PGW-U, i.e. the UPF + PGW-U can support N9 towards the additional UPF, if needed. NOTE 2: S9 interface from EPC is not required since no known deployment exists. Figure 4.3.2-2: Home-routed roaming architecture for interworking between 5GS and EPC/E-UTRAN | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.3.2 |
2,890 | 5.4.2.2 HSS Initiated Subscribed QoS Modification | The HSS Initiated Subscribed QoS Modification for a GTP-based S5/S8 is depicted in figure 5.4.2.2-1. Figure 5.4.2.2-1: HSS Initiated Subscribed QoS Modification NOTE 1: For a PMIP-based S5/S8, procedure steps (A) and steps (B) are defined in TS 23.402[ Architecture enhancements for non-3GPP accesses ] [2]. Steps 3, 4, 5, 7 and 8 concern GTP based S5/S8. 1. The HSS sends an Insert Subscriber Data (IMSI, Subscription Data) message to the MME. The Subscription Data includes EPS subscribed QoS (QCI, ARP) and the subscribed UE-AMBR and APN-AMBR. 1a. The MME updates the stored Subscription Data and acknowledges the Insert Subscriber Data message by returning an Insert Subscriber Data Ack (IMSI) message to the HSS (see clause 5.3.9.2). 2a If only the subscribed UE-AMBR has been modified, the MME calculates a new UE-AMBR value as described in clause 4.7.3 and may then signal a modified UE-AMBR value to the eNodeB by using S1-AP UE Context Modification Procedure. The HSS Initiated Subscribed QoS Modification Procedure ends after completion of the UE Context Modification Procedure. 2b. If the QCI and/or ARP and/or subscribed APN-AMBR has been modified and there is related active PDN connection with the modified QoS Profile the MME sends the Modify Bearer Command (EPS Bearer Identity, EPS Bearer QoS, APN-AMBR) message to the Serving GW. The EPS Bearer Identity identifies the default bearer of the affected PDN connection. The EPS Bearer QoS contains the EPS subscribed QoS profile to be updated. 3. The Serving GW sends the Modify Bearer Command (EPS Bearer Identity, EPS Bearer QoS, APN-AMBR) message to the PDN GW. 4. If PCC infrastructure is deployed, the PDN GW informs the PCRF about the updated EPS Bearer QoS and APN-AMBR. The PCRF sends new updated PCC decision to the PDN GW. This corresponds to the PCEF-initiated IP-CAN Session Modification procedure as defined in TS 23.203[ Policy and charging control architecture ] [6]. The PCRF may modify the APN-AMBR and the QoS parameters (QCI and ARP) associated with the default bearer in the response to the PDN GW as defined in TS 23.203[ Policy and charging control architecture ] [6]. 5. The PDN GW modifies the default bearer of each PDN connection corresponding to the APN for which subscribed QoS has been modified. If the subscribed ARP parameter has been changed, the PDN GW shall also modify all dedicated EPS bearers having the previously subscribed ARP value unless superseded by PCRF decision. The PDN GW then sends the Update Bearer Request (EPS Bearer Identity, EPS Bearer QoS, TFT, APN-AMBR) message to the Serving GW. NOTE 2: As no PTI is included the MME use protocol specific details, as described in TS 29.274[ 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 ] [43], to determine if the Update Bearer Request was triggered by this procedure or not. 6. If the QCI and/or ARP parameter(s) have been modified, steps 3 to 10, as described in clause 5.4.2.1, Figure 5.4.2.1-1, are invoked. If neither the QCI nor the ARP have been modified, but instead only the APN-AMBR was updated, steps 3 to 8, as described in clause 5.4.3, Figure 5.4.3-1, are invoked. 7. The Serving GW acknowledges the bearer modification to the PDN GW by sending an Update Bearer Response (EPS Bearer Identity, User Location Information (ECGI)) message. If the bearer modification fails the PDN GW deletes the concerned EPS Bearer. 8. The PDN GW indicates to the PCRF whether the requested PCC decision was enforced or not by sending a Provision Ack message. | 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.4.2.2 |
2,891 | 8.18.3 RA-SDT or non-SDT with CG-SDT configuration | The procedure for the case where the UE has CG-SDT resource configurations but decides to perform RACH based small data transmission in RRC Inactive or to perform RACH procedure to transit to RRC Connected (see TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [30] clause 5.27) is shown in Figure 8.18.3-1. Figure 8.18.3-1: RA-SDT or non-SDT with CG-SDT configuration. 1. The UE in RRC Inactive sends RRCResumeRequest message. If the UE decides to perform RACH based SDT procedure, it also sends UL SDT data and/or UL SDT signalling. 2. The gNB-DU buffers the UL SDT data and/or UL SDT signalling. 3. The gNB-DU sends the INITIAL UL RRC MESSAGE TRANSFER message to the gNB-CU-CP, including a new gNB-DU UE F1AP ID, and in case of RACH based SDT access, the gNB-DU provides an indication of SDT access and may also the SDT assistance information. 4. If UE context is successfully retrieved as specified in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [2], the gNB-CU-CP sends the UE CONTEXT SETUP REQUEST message with the stored (or retrieved from the last serving gNB) F1 UL TEIDs and the new gNB-DU UE F1AP ID received in step 3. In case that the gNB-DU is the one that sent the RRCRelease message with CG-SDT resource configurations to the UE, the gNB-CU-CP also includes the old gNB-DU UE F1AP ID and the old gNB-CU F1AP UE ID within the Old CG-SDT Session Info IE of the UE CONTEXT SETUP REQUEST message. In case that the gNB-CU-CP is the one that generated the RRCRelease message with CG-SDT resource configurations but the gNB-DU is not the old gNB-DU that sent the RRCRelease message to the UE, the gNB-CU-CP initiates the UE Context Release procedure by sending the UE CONTEXT RELEASE COMMAND message to the old gNB-DU. In case that the UE accesses a gNB other than the last serving gNB, upon receiving the RETRIEVE UE CONTEXT REQUEST message from the receiving gNB-CU-CP, the last serving gNB-CU-CP initiates the UE Context Release procedure by sending the UE CONTEXT RELEASE COMMAND message to the last serving gNB-DU. 5. The gNB-DU sends the UE CONTEXT SETUP RESPONSE message with the new gNB-DU UE F1AP ID. In case the old gNB-DU UE F1AP ID is received within the Old CG-SDT Session Info IE in step 4, the gNB-DU retrieves the stored CG-SDT resource configurations and UE context based on the Old CG-SDT Session Info IE, if any, and associates them with the new gNB-DU F1AP UE ID. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 8.18.3 |
2,892 | 5.6.2.2 Paging for 5GS services 5.6.2.2.1 General | The network shall initiate the paging procedure for 5GS services when NAS signalling messages or user data is pending to be sent to the UE in 5GMM-IDLE mode over 3GPP access (see example in figure 5.6.2.2.1.1) and there is no paging restriction applied in the network for that paging. Figure 5.6.2.2.1.1: Paging procedure To initiate the procedure the 5GMM entity in the AMF requests the lower layer to start paging and shall start timer T3513. If downlink signalling or user data is pending to be sent over non-3GPP access, the 5GMM entity in the AMF shall indicate to the lower layer that the paging is associated to non-3GPP access. The network shall not page the UE to re-establish user-plane resources of PDU session(s) associated with non-3GPP access over 3GPP access if all the PDU sessions of the UE that are established over the 3GPP access are associated with control plane only indication or S-NSSAI(s) associated with PDU session(s) are not in the UE’s allowed NSSAI for a PLMN on 3GPP access. If the network has downlink user data pending for a UE, the AMF has stored paging restriction of the UE and the Paging restriction type in the stored paging restriction is set to: a) "All paging is restricted", the network should not page the UE; b) "All paging is restricted except for voice service", the network should page the UE only when: 1) the pending downlink user data for the UE is considered as voice service related by the network; c) "All paging is restricted except for specified PDU session(s)", the network should page the UE only when: 1) for PDU session(s) that paging is not restricted based on the stored paging restriction, the network has downlink user data pending; or d) "All paging is restricted except for voice service and specified PDU session(s)", the network should page the UE only when: 1) the pending downlink user data for the UE is considered as voice service related by the network; or 2) for PDU session(s) that paging is not restricted based on the stored paging restriction, the network has downlink user data pending. If the network has downlink signalling pending for a UE and the AMF has stored paging restriction of the UE and the Paging restriction type in the stored paging restriction is set to: a) "All paging is restricted", the network should not page the UE; b) "All paging is restricted except for voice service", the network should page the UE only when: 1) the pending downlink signalling for the UE is 5GMM signalling or 5GSM signalling of the PDU session of voice service; c) "All paging is restricted except for specified PDU session(s)", the network should page the UE only when: 1) the pending downlink signalling for the UE is 5GMM signalling; or 2) for PDU session(s) that paging is not restricted based on the stored paging restriction, the network has downlink 5GSM signalling pending; or d) "All paging is restricted except for voice service and specified PDU session(s)", the network should page the UE only when: 1) the pending downlink signalling for the UE is 5GMM signalling or 5GSM signalling of the PDU session of voice service; or 2) for PDU session(s) that paging is not restricted based on the stored paging restriction, the network has downlink 5GSM signalling pending. NOTE 1: If the network pages the UE due to downlink signalling pending, the network initiates the release of the N1 NAS signalling connection after network-requested procedure is completed. The 5GMM entity in the AMF may provide the lower layer with the "allowed CAG list" and an "indication that the UE is only allowed to access 5GS via CAG cells" for the current PLMN, if available, and with the "allowed CAG list" and an "indication that the UE is only allowed to access 5GS via CAG cells" per equivalent PLMN, if available. If there is an active emergency PDU session, the 5GMM entity in the AMF shall not provide the lower layer with the "allowed CAG list" and an "indication that the UE is only allowed to access 5GS via CAG cells" for the current PLMN, even if available, or with the "allowed CAG list" and an "indication that the UE is only allowed to access 5GS via CAG cells" per equivalent PLMN, even if available. Upon reception of a paging indication, the UE shall stop the timer T3346, if running, and: a) if control plane CIoT 5GS optimization is not used by the UE, the UE shall: 1) initiate a service request procedure over 3GPP access to respond to the paging as specified in subclauses 5.6.1.2.1 if the UE is in 5GMM-REGISTERED.NORMAL-SERVICE or 5GMM-REGISTERED.NON-ALLOWED-SERVICE (as described in subclause 5.3.5.2) state and the UE is in the 5GMM-IDLE mode without suspend indication; 2) initiate a service request procedure over non-3GPP access to respond to the paging as specified in subclauses 5.6.1; 3) initiate a registration procedure for mobility and periodic registration update over 3GPP access to respond to the paging as specified in subclauses 5.5.1.3.2; or 4) proceed as specified in subclause 5.3.1.5 if the UE is in the 5GMM-IDLE mode with suspend indication; or b) if control plane CIoT 5GS optimization is used by the UE, the UE shall: 1) initiate a service request procedure as specified in subclause 5.6.1.2.2 if the UE is in the 5GMM-IDLE mode without suspend indication; 2) initiate a registration procedure for mobility and periodic registration update over 3GPP access as specified in subclauses 5.5.1.3.2; or 3) proceed as specified in subclause 5.3.1.5 if the UE is in the 5GMM-IDLE mode with suspend indication. NOTE 2: If the UE is in the 5GMM-IDLE mode without suspend indication and has an uplink user data to be sent to the network using control plane CIoT 5GS optimization when receiving the paging indication, the UE can piggyback the uplink user data during the service request procedure initiated to respond to the paging, as specified in subclause 5.6.1.2.2. The MUSIM UE based on implementation may use the paging cause indicated by lower layers (see 3GPP TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [30]), if any, to accept the paging, reject the paging or ignore the paging indication. Upon reception of a paging indication, if the network supports the rejection of paging request and if a MUSIM UE decides not to accept the paging, the UE may initiate a service request procedure to reject the paging as specified in subclause 5.6.1.1. NOTE 3: As an implementation option, MUSIM UE is allowed to not respond to paging based on the information available in the paging message, e.g. voice service indication. If TMGI is used as paging identity and the TMGI matches with multicast MBS session which the has UE joined, the UE shall respond to the paging. Otherwise, the UE shall not respond to the paging. The network shall stop timer T3513 for the paging procedure when an integrity-protected response is received from the UE and successfully integrity checked by the network or when the 5GMM entity in the AMF receives an indication from the lower layer that it has received the NGAP UE context resume request message as specified in 3GPP TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [31]. If the response received is not integrity protected, or the integrity check is unsuccessful, timer T3513 for the paging procedure shall be kept running unless: a) the UE is registered for emergency services; b) the UE has an emergency PDU session; or c) the response received is a REGISTRATION REQUEST message for mobility and periodic registration update and the security mode control procedure or authentication procedure performed during mobility and periodic registration update has completed successfully. Upon expiry of timer T3513, the network may reinitiate paging. If the network, while waiting for a response to the paging sent without paging priority, receives downlink signalling or downlink data associated with priority user-plane resources for PDU sessions, the network shall stop timer T3513, and then initiate the paging procedure with paging priority. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.6.2.2 |
2,893 | 9.2.10 Extended DRX for RRC_IDLE and RRC_INACTIVE | When extended DRX (eDRX) is used, the following applies: - For RRC_INACTIVE, eDRX configuration for RAN paging is decided and configured by NG-RAN. In RRC_INACTIVE the UE monitors both RAN and CN paging; - For RRC_IDLE, eDRX for CN paging is configured by upper layers. In RRC_IDLE the UE monitors only CN paging; - Information on whether eDRX for CN paging and RAN paging is allowed on the cell is provided separately in system information; - The maximum value of the eDRX cycle is 10485.76 seconds (2.91 hours) while the minimum value of the eDRX cycle is 2.56 seconds; - The hyper SFN (H-SFN) is broadcast by the cell and increments by one when the SFN wraps around; - Paging Hyperframe (PH) refers to the H-SFN in which the UE starts monitoring paging according to DRX during a Paging Time Window (PTW). The PH and PTW are determined based on a formula (see TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [10]) that is known by the AMF, UE and NG-RAN; - H-SFN, PH and PTW are used if the eDRX cycle is greater than 10.24 seconds; - When the RRC_IDLE eDRX cycle is longer than the system information modification period, the UE verifies that stored system information remains valid before resuming/establishing an RRC connection. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 9.2.10 |
2,894 | 5.2.2.4.1 Actions upon reception of the MIB | Upon receiving the MIB the UE shall: 1> store the acquired MIB; 1> if the UE is in RRC_IDLE or in RRC_INACTIVE, or if the UE is in RRC_CONNECTED while T311 is running: 2> if the access is not for NTN or the UE is not capable of NTN or the UE is not capable of NES cell DTX/DRX; and 2> if the access is not for ATG or the UE is not capable of ATG; and 2> if the cellBarred in the acquired MIB is set to barred: 3> if the UE is an (e)RedCap UE and ssb-SubcarrierOffset indicates SIB1 is transmitted in the cell (TS 38.213[ NR; Physical layer procedures for control ] [13]): 4> acquire the SIB1, which is scheduled as specified in TS 38.213[ NR; Physical layer procedures for control ] [13]; 3> consider the cell as barred in accordance with TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [20]; 3> perform cell re-selection to other cells on the same frequency as the barred cell as specified in TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [20]; 2> else: 3> apply the received systemFrameNumber, pdcch-ConfigSIB1, subCarrierSpacingCommon, ssb-SubcarrierOffset and dmrs-TypeA-Position. NOTE 1: A UE capable of NTN access should acquire SIB1 to determine whether the cell is an NTN cell. NOTE 2: A UE capable of ATG access should acquire SIB1 to determine whether the cell is an ATG cell. NOTE 3: A UE capable of NES cell DTX/DRX should acquire SIB1 to determine the cell barring status when the cellBarred in MIB is set to barred. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.2.2.4.1 |
2,895 | 10.5.6.6 SM cause | The purpose of the SM cause information element is to indicate the reason why a session management request is rejected. The SM cause is a type 3 information element with 2 octets length. The SM cause information element is coded as shown in figure 10.5.139/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.157/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Figure 10.5.139/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : SM cause information element Table 10.5.157/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : SM cause information element | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 10.5.6.6 |
2,896 | 5.3.4.3.4 Failure of in-call modification | 5.3.4.3.4.1 Network rejection of in-call modification If the network cannot support the change to the requested call mode or if the change of the channel configuration fails the network shall: release the resources which had been reserved for the alternation: send a MODIFY REJECT message with the old bearer capability and with cause # 58 "bearer capability not presently available" to the initiating mobile station; and enter the "active" state. If the change of the channel configuration fails, the network shall return to the internal resources required for the old call mode. Upon receipt of the MODIFY REJECT message with the old bearer capability the initiating mobile station shall: stop timer T323; release any resources which had been reserved for the alternation; resume sending user channel information according to the present call mode; resume interpreting received user channel information according to the present call mode; and enter the "active" state. 5.3.4.3.4.2 Mobile station rejection of in-call modification If the mobile station cannot support the change to the requested call mode, the mobile station shall: stop timer T324; release any resources which had been reserved for the alternation; send a MODIFY REJECT message with the old bearer capability and cause # 58 "bearer capability not presently available", and enter the "active" state. Upon receipt of the MODIFY REJECT message the network shall: stop timer T323, release any resources which had been reserved for the alternation. 5.3.4.3.4.3 Time-out recovery Upon expiration of T323 in either the mobile station or the network the procedures for call clearing shall be initiated (see subclause 5.4) with cause # 102 "recovery on timer expiry". Upon expiration of T324 the mobile station shall: release any resources which had been reserved for the alternation; send a MODIFY REJECT message with the old bearer capability and cause #58 "bearer capability not presently available"; and enter the "active" state. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.3.4.3.4 |
2,897 | 4.6.3.1 ECM-IDLE | A UE is in ECM-IDLE state when no NAS signalling connection between UE and network exists. In ECM-IDLE state, a UE performs cell selection/reselection according to TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [34] and PLMN selection according to TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [10]. Except for UEs that have had their RRC connection suspended, as described in clause 5.3.4A, there exists no UE context in E-UTRAN for the UE in the ECM-IDLE state. There is no S1_MME and no S1_U connection for the UE in the ECM-IDLE state. In the EMM-REGISTERED and ECM-IDLE state, the UE shall: - perform a tracking area update if the current TA is not in the list of TAs that the UE has received from the network in order to maintain the registration and enable the MME to page the UE; - perform the periodic tracking area updating procedure to notify the EPC that the UE is available; - perform a tracking area update if the RRC connection was released with release cause "load balancing TAU required"; - perform a tracking area update when the UE reselects an E-UTRAN cell and the UE's TIN indicates "P-TMSI"; - perform a tracking area update for a change of the UE's Core Network Capability information or the UE specific DRX parameter; - perform a tracking area update when a change in conditions in the UE require a change in the extended idle mode DRX parameters previously provided by the MME. - perform a tracking area update when the UE manually selects a CSG cell, and the CSG ID and associated PLMN of that cell is absent from both the UE's Allowed CSG list and the UE's Operator CSG list; - answer to paging from the MME by performing a service request procedure or, if the UE has had its RRC connection suspended, the UE initiates the Connection Resume procedure (clause 5.3.5A); - perform the service request procedure in order to establish the radio bearers when uplink user data is to be sent, or uplink NAS signalling is to be sent for UE requested bearer modification procedure (clause 5.4.5), UE requested PDN connectivity (clause 5.10.2), UE requested PDN disconnection (clause 5.10.3), or if the UE has had its RRC connection suspended the UE initiates the Connection Resume procedure (clause 5.3.5A). The UE and the MME shall enter the ECM-CONNECTED state when the signalling connection is established between the UE and the MME. Initial NAS messages that initiate a transition from ECM-IDLE to ECM-CONNECTED state are Attach Request, Tracking Area Update Request, Service Request or Detach Request. A successful completion of the Connection Resume procedure, described in clause 5.3.5.A, initiates at UE and MME a state transition from ECM-IDLE to ECM-CONNECTED. When the UE is in ECM-IDLE state, the UE and the network may be unsynchronized, i.e. the UE and the network may have different sets of established EPS bearers. When the UE and the MME enter the ECM-CONNECTED state, the set of EPS Bearers is synchronized between the UE and network. | 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.6.3.1 |
2,898 | 10.7.1 EN-DC | Inter-Master Node handover with/without MN initiated Secondary Node change is used to transfer context data from a source MN to a target MN while the context at the SN is kept or moved to another SN. During an Inter-Master Node handover, the target MN decides whether to keep or change the SN (or release the SN, as described in clause 10.8). NOTE 1: Void. Figure 10.7.1-1: Inter-MN handover with/without MN initiated SN change Figure 10.7.1-1 shows an example signaling flow for inter-Master Node handover with or without MN initiated Secondary Node change: NOTE 2: For an inter-Master Node handover without Secondary Node change, the source SN and the target SN shown in Figure 10.7.1-1 are the same node. 1. The source MN starts the handover procedure by initiating the X2 Handover Preparation procedure including both MCG and SCG configuration. The source MN includes the (source) SN UE X2AP ID, SN ID and the UE context in the (source) SN in the Handover Request message. NOTE 3: The source MN may trigger the MN-initiated SN Modification procedure (to the source SN) to retrieve the current SCG configuration before step 1. 2. If the target MN decides to keep the UE context in SN, the target MN sends SgNB Addition Request to the SN including the SN UE X2AP ID as a reference to the UE context in the SN that was established by the source MN. If the target MN decides to change the SN allowing delta configuration, the target MN sends the SgNB Addition Request to the target SN including the UE context in the source SN that was established by the source MN. Otherwise, the target MN may send the SgNB Addition Request to the target SN including neither the SN UE X2AP ID nor the UE context in the source SN that was established by the source MN. 3. The (target) SN replies with SgNB Addition Request Acknowledge. The (target) SN may include the indication of the full or delta RRC configuration. NOTE 3a: In case the target SN includes the indication of the full RRC configuration, the MN performs release of the SN terminated radio bearer configuration and release and add of the NR SCG configuration part towards the UE. NOTE 3b: Void. 4. The target MN includes within the Handover Request Acknowledge message a transparent container to be sent to the UE as an RRC message to perform the handover, and may also provide forwarding addresses to the source MN. The target MN indicates to the source MN that the UE context in the SN is kept if the target MN and the SN decided to keep the UE context in the SN in step 2 and step 3. 5. The source MN sends SgNB Release Request to the (source) SN including a Cause indicating MCG mobility. The (source) SN acknowledges the release request. The source MN indicates to the (source) SN that the UE context in SN is kept, if it receives the indication from the target MN. If the indication as the UE context kept in SN is included, the SN keeps the UE context. 6. The source MN triggers the UE to apply the new configuration. 7/8. The UE synchronizes to the target MN and replies with RRCConnectionReconfigurationComplete message. 9. If configured with bearers requiring SCG radio resources, the UE synchronizes to the (target) SN. NOTE 3b1: The order the UE performs Random Access towards the MN (step 7) and performs the Random Access procedure towards the SN (step 9) is not defined. 10. If the RRC connection reconfiguration procedure was successful, the target MN informs the (target) SN via SgNB Reconfiguration Complete message. 11a. The SN sends the Secondary RAT Data Usage Report message to the source MN and includes the data volumes delivered to and received from the UE over the NR radio for the related E-RABs. NOTE 4: The order the source SN sends the Secondary RAT Data Usage Report message and performs data forwarding with MN/target SN is not defined. The SgNB may send the report when the transmission of the related bearer is stopped. 11b. The source MN sends the Secondary RAT Report message to MME to provide information on the used NR resource. 12. For bearers using RLC AM, the source MN sends the SN Status Transfer message, including, if needed, SN Status received from the source SN to the target MN. The target forwards the SN Status to the target SN, if needed. 13. If applicable, data forwarding takes place from the source side. If the SN is kept, data forwarding may be omitted for SN-terminated bearers kept in the SN. 14-17. The target MN initiates the S1 Path Switch procedure. NOTE 5: If new UL TEIDs of the S-GW are included, the target MN performs the MN initiated SN Modification procedure to provide them to the SN. 18. The target MN initiates the UE Context Release procedure towards the source MN. 19. Upon reception of the UE Context Release message, the (source) SN releases C-plane related resources associated to the UE context towards the source MN. Any ongoing data forwarding may continue. The SN shall not release the UE context associated with the target MN if the UE context kept indication was included in the SgNB Release Request message in step 5. | 3GPP TS 37.340 | Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Overall Description; Stage-2 | RAN2 | 3GPP Series : 37 , Multiple radio access technology aspects | 10.7.1 |
2,899 | 8.6.1 Mapping of a 5G security context to an EPS security context | The derivation of a mapped EPS security context from a 5G security context is done as described below: - The KASME' key, taken as the KASME, shall be derived from the KAMF using the 5G NAS Uplink COUNT value derived from the TAU Request message or Attach Request message in idle mode mobility or the 5G NAS Downlink COUNT value in handovers as described in Annex A.14. - The eKSI for the newly derived KASME key shall be defined such as the value field is taken from the ngKSI and the type field is set to indicate a mapped security context. - The EPS uplink and downlink NAS COUNT values in the mapped context shall be set to the uplink and downlink NAS COUNT values of the current 5G security context respectively. - The selected EPS NAS algorithms shall be set to the EPS algorithms signalled to the UE by the AMF during an early authentication procedure followed by a NAS SMC as described in clause 6.7.2. NOTE: Whenever an algorithm change is required, the target MME initiates an NAS SMC to select other algorithms as described in TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [10]. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 8.6.1 |
2,900 | 5.7.13.1 Relaxed measurement criterion for low mobility | The relaxed measurement criterion for UE with low mobility in RRC_CONNECTED is fulfilled when: - (SS-RSRPRef – SS-RSRP) < SSearchDeltaP-Connected, Where: - SS-RSRP = current L3 RSRP measurement of the SpCell based on SSB (dB). - SS-RSRPRef = reference L3 RSRP measurement of the SpCell based on SSB (dB), set as follows: - After receiving low mobility criterion configuration, or - After MAC of the CG successfully completes a Random Access procedure after applying a reconfigurationWithSync in spCellConfig of the CG while low mobility criterion is configured, or - If (SS-RSRP - SS-RSRPRef) > 0, or - If the relaxed measurement criterion has not been met for TSearchDeltaP-Connected: - The UE shall set the value of SS-RSRPRef to the current SS-RSRP value of the SpCell. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.7.13.1 |
Subsets and Splits
No saved queries yet
Save your SQL queries to embed, download, and access them later. Queries will appear here once saved.