Search is not available for this dataset
doc_id
int64 1
6.72k
⌀ | Section
stringlengths 5
247
⌀ | Content
stringlengths 501
147k
⌀ | Source
stringclasses 456
values | Document Title
stringclasses 22
values | Working Group
stringclasses 21
values | Series Subject
stringclasses 9
values | Subclause
stringlengths 1
13
⌀ |
|---|---|---|---|---|---|---|---|
5,801 | 6.8.2.2 Key handling during mobility in RRC_INACTIVE state 6.8.2.2.1 General | The purpose of this procedure is to allow the UE to notify the network if it moves out of the configured RNA (RAN-based Notification Area) or if UE initiates a periodic RAN-based notification area update procedure. The UE and gNB store the AS security context in RRC_INACTIVE state and reactivate the AS security context when the UE initiates the RAN-based Notification Area Update (RNAU) procedure. The ng-eNB connected to 5GC shall also support the same key handling during mobility in RRC_INACTIVE. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.8.2.2 |
5,802 | 16.12.4 Relay Selection/Reselection | The U2N Remote UE performs radio measurements at PC5 interface and uses them for U2N Relay selection and reselection along with higher layer criteria, as specified in TS 23.304[ Proximity based Services (ProSe) in the 5G System (5GS) ] [48]. When there is no unicast PC5 connection between the U2N Relay UE and the U2N Remote UE, the U2N Remote UE uses SD-RSRP measurements to evaluate whether PC5 link quality towards a U2N Relay UE satisfies relay selection criterion. For relay reselection, U2N Remote UE uses SL-RSRP measurements towards the serving U2N Relay UE for relay reselection trigger evaluation when there is data transmission from U2N Relay UE to U2N Remote UE, and it is left to UE implementation whether to use SL-RSRP or SD-RSRP for relay reselection trigger evaluation in case of no data transmission from U2N Relay UE to U2N Remote UE. A U2N Relay UE is considered suitable by a U2N Remote UE in terms of radio criteria if the PC5 link quality measured by U2N Remote UE towards the U2N Relay UE exceeds configured threshold (pre-configured or provided by gNB). The U2N Remote UE searches for suitable U2N Relay UE candidates that meet all AS layer and higher layer criteria (see TS 23.304[ Proximity based Services (ProSe) in the 5G System (5GS) ] [48]). If there are multiple such suitable U2N Relay UEs, it is up to U2N Remote UE implementation to choose one U2N Relay UE among them. For L2 U2N Relay (re)selection, the PLMN ID and cell ID can be used as additional AS criteria. The U2N Remote UE triggers U2N Relay selection in following cases: - Direct Uu signal strength of current serving cell of the U2N Remote UE is below a configured signal strength threshold; - Indicated by upper layer of the U2N Remote UE. The U2N Remote UE may trigger U2N Relay reselection in following cases: - PC5 signal strength of current U2N Relay UE is below a (pre)configured signal strength threshold; - Cell reselection, handover, Uu RLF, or Uu RRC connection establishment/resume failure has been indicated by U2N Relay UE via PC5-RRC signalling; - When U2N Remote UE receives a PC5-S link release message from U2N Relay UE; - When U2N Remote UE detects PC5 RLF; - Indicated by upper layer. For L2 U2N Remote UEs in RRC_IDLE or RRC_INACTIVE and L3 U2N Remote UEs, the cell (re)selection procedure and relay (re)selection procedure run independently. If both suitable cells and suitable U2N Relay UEs are available, it is up to the U2N Remote UE implementation to select either a cell or a U2N Relay UE. A L3 U2N Remote UE may select a cell and a L3 U2N Relay UE simultaneously and this is up to implementation of L3 U2N Remote UE. For both L2 and L3 U2N Relay UEs in RRC_IDLE or RRC_INACTIVE, the PC5-RRC message(s) are used to inform their connected U2N Remote UE(s) when U2N Relay UEs select a new cell. The PC5-RRC message(s) are also used to inform their connected L2 or L3 U2N Remote UE(s) when L2 or L3 U2N Relay UE performs handover, detects Uu RLF, or its Uu RRC connection establishment/resume fails. Upon reception of the PC5 RRC message for notification, it is up to U2N Remote UE implementation whether to release or keep the unicast PC5 link. If U2N Remote UE decides to release the unicast PC5 link, it triggers the PC5 release procedure and may perform cell or relay reselection. The U2U Remote UE performs radio measurements (i.e., SD-RSRP and/or SL-RSRP) at PC5 interface and uses them for U2U Relay selection and reselection along with higher layer criteria, as specified in TS 23.304[ Proximity based Services (ProSe) in the 5G System (5GS) ] [48]. For relay selection, U2U Remote UE uses SL-RSRP measurements towards the peer U2U Remote UE for relay selection trigger evaluation when valid SL-RSRP measurements are available. For relay reselection, U2U Remote UE uses SL-RSRP measurement towards the U2U Relay UE for relay reselection trigger evaluation when there is data transmission from U2U Relay UE to U2U Remote UE. It is left to U2U Remote UE implementation whether to use SL-RSRP or SD-RSRP for relay selection or reselection trigger evaluation in case of no data transmission. The thresholds for SD-RSRP and SL-RSRP can be configured separately for the trigger evaluation of U2U relay selection or reselection. The same threshold value(s) are applied for all the discovery models including DCR with integrated discovery. The same threshold value(s) are applied for relay selection and relay reselection. The U2U Remote UE may trigger U2U Relay selection in the following cases: - When the SL-RSRP or SD-RSRP between U2U Remote UEs is below a (pre)configured signal strength threshold; - When U2U Remote UE receives an indication to trigger U2U relay selection from the upper layer of the UE. The U2U Remote UE may trigger U2U Relay reselection in the following cases: - When the SL-RSRP or SD-RSRP of the current U2U Relay UE is below a (pre)configured signal strength threshold; - When U2U Remote UE receives an indication from the upper layer due to detecting PC5 RLF; - When L2 U2U Remote UE receives an indication from the upper layer due to receiving the PC5 RLF indication from the L2 U2U Relay UE; - When U2U Remote UE receives a PC5-S link release message from U2U Relay UE; - When U2U Remote UE receives an indication to trigger U2U relay reselection from the upper layer of the UE. For the discovery model A, the U2U Relay UE should announce via discovery announcement message only the neighbour U2U Remote UE(s) for which the SD-RSRP/SL-RSRP between the U2U Relay and the neighbour U2U Remote UE(s) is above a configured threshold. Upon discovery message reception, U2U Remote UE considers a U2U Relay UE as a candidate U2U Relay UE if the SD-RSRP towards the U2U Relay UE is above a configured threshold and the upper layer criteria are met. For the discovery model B, when the U2U Relay UE receives the discovery solicitation message from U2U Remote UE, the U2U Relay UE forwards the discovery solicitation message only if the SD-RSRP between the U2U Relay UE and the U2U Remote UE is above a threshold. After the peer U2U remote UE receives a discovery solicitation message from the U2U Relay UE, the peer U2U Remote UE transmits the discovery response message only if the SD-RSRP between the peer U2U Remote UE and the U2U Relay UE is above a configured threshold. Upon discovery response message reception forwarded by the U2U Relay UE, the U2U Remote UE considers a U2U Relay UE as a candidate U2U Relay UE if the SD-RSRP towards the U2U Relay UE is above a configured threshold and the upper layer criteria are met. For the DCR message with integrated discovery, when the U2U Relay UE receives the DCR message with integrated discovery from U2U Remote UE, the U2U Relay UE forwards the DCR message with integrated discovery only if the SL-RSRP between the U2U Relay UE and the U2U Remote UE is above a threshold. Upon receiving DCR message with integrated discovery from one or multiple U2U Relay UEs, the peer U2U Remote UE should consider candidate U2U Relay UEs towards which the SL-RSRP is above a configured SD-RSRP threshold (not the SL-RSRP, as broadcast is used) to respond and that satisfy upper-layer criteria, and select a U2U Relay UE among them. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.12.4 |
5,803 | 9.3.18a Recall $(CCBS)$ | A mobile station 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 from the network to the mobile station to initiate the sending of the SETUP message. In addition it provides information for user notification. See Table 9.68b/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Message type: RECALL Significance: local Direction: network to mobile station Table 9.68b/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Recall 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.18a |
5,804 | 5.15.7.3 Connected mode aspects | In addition to the interworking principles documented in clause 5.17.2 the following applies for interworking with N26: - When a UE is CM-CONNECTED in 5GC and a handover to EPS occur, the AMF selects the target MME based on the source AMF Region ID, AMF Set ID and target location information. The AMF forwards the UE context to the selected MME over the N26 Interface. In the UE context, the AMF also includes the UE Usage type, if it is received as part of subscription data. The Handover procedure is executed as documented in TS 23.502[ Procedures for the 5G System (5GS) ] [3]. When the Handover procedure completes successfully the UE performs a Tracking Area Update. This completes the UE registration in the target EPS. As part of this the UE obtains a DCN-ID if the target EPS uses it. - When a UE is ECM-CONNECTED in EPC, and performs a handover to 5GS, the MME selects the target AMF based on target location information, e.g. TAI and any other available local information (including the UE Usage Type if one is available for the UE in the subscription data) and forwards the UE context to the selected AMF over the N26 interface. In the home-routed roaming case, the AMF selects default V-SMFs. The Handover procedure is executed as documented in TS 23.502[ Procedures for the 5G System (5GS) ] [3]. The SMF+PGW-C sends PDU Session IDs and related S-NSSAIs to AMF. Based on the received S-NSSAIs values the target AMF derives the S-NSSAI values for the Serving PLMN, the target AMF reselects a final target AMF if necessary as described in clause 5.15.5.2.1, the AMF reallocation procedure is triggered. For each PDU Session based on the associated derived S-NSSAI values if the V-SMF need be reallocated, the final target AMF triggers the V-SMF reallocation as described in clause 4.23.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. When the Handover procedure completes successfully the UE performs a Registration procedure. This completes the UE registration in the target 5GS and as part of this the UE obtains an Allowed NSSAI. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.15.7.3 |
5,805 | 5.2.16.3.2 Nnssf_NSSAIAvailability_Update service operation | Service operation name: Nnssf_NSSAIAvailability_Update Description: This service operation enables the AMF to update the NSSF with the S-NSSAIs the AMF supports per TA and get the availability of the S-NSSAIs and optionally NSI IDs per TA for the S-NSSAIs the AMF supports. Inputs, Required: Supported S-NSSAIs per TAI. The supported S-NSSAIs per TAI, is a list of TAIs and for each TAI the S-NSSAIs supported by the AMF. Inputs, Optional: Supported NSAGs per TAI.. The supported NSAGs per TAI, is a list of TAIs and for each TAI the NSAGs and the associated S-NSSAIs supported by the AMF. Outputs, Required: A list of TAIs and for each TAI, the S-NSSAIs and optionally NSI IDs supported by the AMF and 5G-AN and authorized by the NSSF for the TAI. Outputs, Conditional Required: A list of TAIs and for each TAI, the NSAGs authorized by the NSSF for the TAI. The authorized NSAGs per TAI, is a list of TAIs and for each TAI the NSAGs and the associated S-NSSAIs. Outputs, Optional: For each TAI, a list of S-NSSAIs restricted per PLMN for the TAI. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.16.3.2 |
5,806 | 5.4.4 Clearing initiated by the network | Apart from the exception conditions identified in subclause 5.4.2, the call control entity of the network shall initiate clearing by: sending a DISCONNECT message; and entering the "disconnect indication" state. The DISCONNECT message is a local invitation to clear the call. NOTE: When the network initiates clearing by sending a RELEASE message, the procedures described in subclauses 5.4.3., 5.4.3.4 and 5.4.3.5 are followed. A mobile station that does not support the "Prolonged Clearing Procedure" shall comply with the requirements of subclause 5.4.4.1 and shall ignore subclause 5.4.4.2. A mobile station that supports the "Prolonged Clearing Procedure" shall comply with the requirements of subclauses 5.4.4.2 and shall ignore subclause 5.4.4.1. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.4.4 |
5,807 | – SCCH-Message | The SCCH-Message class is the set of PC5-RRC messages that may be sent from the UE to the UE for unicast of NR sidelink communication on SCCH logical channel. -- ASN1START -- TAG-SCCH-MESSAGE-START SCCH-Message ::= SEQUENCE { message SCCH-MessageType } SCCH-MessageType ::= CHOICE { c1 CHOICE { measurementReportSidelink MeasurementReportSidelink, rrcReconfigurationSidelink RRCReconfigurationSidelink, rrcReconfigurationCompleteSidelink RRCReconfigurationCompleteSidelink, rrcReconfigurationFailureSidelink RRCReconfigurationFailureSidelink, ueCapabilityEnquirySidelink UECapabilityEnquirySidelink, ueCapabilityInformationSidelink UECapabilityInformationSidelink, uuMessageTransferSidelink-r17 UuMessageTransferSidelink-r17, remoteUEInformationSidelink-r17 RemoteUEInformationSidelink-r17 }, messageClassExtension CHOICE { c2 CHOICE { notificationMessageSidelink-r17 NotificationMessageSidelink-r17, ueAssistanceInformationSidelink-r17 UEAssistanceInformationSidelink-r17, ueInformationRequestSidelink-r18 UEInformationRequestSidelink-r18, ueInformationResponseSidelink-r18 UEInformationResponseSidelink-r18, spare4 NULL, spare3 NULL, spare2 NULL, spare1 NULL }, messageClassExtensionFuture-r17 SEQUENCE {} } } -- TAG-SCCH-MESSAGE-STOP -- ASN1STOP 6.6.2 Message definitions | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
5,808 | K.2.3 IOPS network configuration | An IOPS network can comprise either: - a Local EPC and a single isolated IOPS-capable eNodeB, which may be co-located or have connectivity to the Local EPC; or - a Local EPC and two or more IOPS-capable eNodeBs, which have connectivity to a single Local EPC. Existing procedures 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] can be used to achieve dynamic configuration of the S1-MME interface. An IOPS-capable eNodeB can be pre-provisioned with IP endpoint information, relating to the MMEs of one or more candidate Local EPC instances. For each local MME in turn the eNodeB can try to initialize a SCTP association. Once SCTP connectivity has been established, the eNodeB and local MME exchange application level configuration data over the S1-MME application protocol with the S1 Setup Procedure (see TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [36]). In line with local operator policies the eNodeB can be provisioned with the IP endpoint of a preferred Local EPC MME instance and the IP endpoints of one or more alternative Local EPC MME instances. The alternative Local EPC instances will be used if an S1-MME path cannot be established with the local MME of the preferred Local EPC instance. All Local EPCs deployed by a public safety authority / operator assume the same PLMN-Id. In order to achieve the broadcast of different TAIs on separate IOPS networks the TACs broadcast by the cells of eNodeBs connected to different Local EPCs are distinct to ensure the required UE mobility behaviour (see clause K.2.5). Therefore, the TAC broadcast by the cells of an eNodeB operating in IOPS mode will be dependent upon the Local EPC to which the eNodeB has established an S1-MME connection. If the scope of service of a Local EPC is a single eNodeB, then all cells served by the eNodeB share the same TAC (assigned for use in IOPS mode) and neighbouring eNodeBs that are also operating in IOPS mode with the same dedicated PLMN-Id are assigned different TACs (resulting in different TAIs) so a TAU attempt is triggered upon mobility. If multiple eNodeBs are configured to be served by a single Local EPC, configuration of TAIs for IOPS can be done according to local operator policies in such a way that a reselection to a cell operating a PLMN in normal mode always triggers an attach request. If sharing the same PLMN-Id, it is assumed the TAC assigned to cells in a Nomadic EPS would be different from the TACs assigned to infrastructure eNodeBs operating in IOPS mode, so as to trigger a TAU between these systems. The support by IOPS network entities of S1-flex and/or eMBMS is up to local operator policy and configuration. | 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") | K.2.3 |
5,809 | 5.1.4 Data integrity | The following security features are provided with respect to integrity of data on the network access link: - integrity algorithm agreement: the property that the MS and the SN can securely negotiate the integrity algorithm that they shall use subsequently; - integrity key agreement: the property that the MS and the SN agree on an integrity key that they may use subsequently; - data integrity and origin authentication of signalling data: the property that the receiving entity (MS or SN) is able to verify that signalling data has not been modified in an unauthorised way since it was sent by the sending entity (SN or MS) and that the data origin of the signalling data received is indeed the one claimed; Integrity key agreement is realised in the course of the execution of the mechanism for authentication and key agreement (see 6.3). Integrity algorithm agreement is realised by means of a mechanism for security mode negotiation between the user and the network (see 6.4.5). This mechanism also enables the selected integrity algorithm and the agreed integrity key to be applied in the way described in 6.5. | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | 5.1.4 |
5,810 | – SL-BWP-ConfigCommon | The IE SL-BWP-ConfigCommon is used to configure the cell-specific configuration information on one particular sidelink bandwidth part. SL-BWP-ConfigCommon information element -- ASN1START -- TAG-SL-BWP-CONFIGCOMMON-START SL-BWP-ConfigCommon-r16 ::= SEQUENCE { sl-BWP-Generic-r16 SL-BWP-Generic-r16 OPTIONAL, -- Need R sl-BWP-PoolConfigCommon-r16 SL-BWP-PoolConfigCommon-r16 OPTIONAL, -- Need R ..., [[ sl-BWP-PoolConfigCommonPS-r17 SL-BWP-PoolConfigCommon-r16 OPTIONAL, -- Need R sl-BWP-DiscPoolConfigCommon-r17 SL-BWP-DiscPoolConfigCommon-r17 OPTIONAL -- Need R ]], [[ sl-LBT-FailureRecoveryConfig-r18 SetupRelease { SL-LBT-FailureRecoveryConfig-r18 } OPTIONAL, -- Need R sl-StartingSymbolFirst-r18 ENUMERATED {sym0, sym1, sym2, sym3, sym4, sym5, sym6} OPTIONAL, -- Need R sl-StartingSymbolSecond-r18 ENUMERATED {sym3, sym4, sym5, sym6, sym7} OPTIONAL, -- Need R sl-TransmissionStructureForPSCCHandPSSCH-r18 ENUMERATED {contigousRB, interlaceRB} OPTIONAL, -- Need R sl-GapOfAdditionalSSSB-Occasion-r18 INTEGER (0..639) OPTIONAL, -- Need R sl-AbsoluteFrequencySSB-NonAnchorList-r18 SEQUENCE (SIZE (1.. maxSL-NonAnchorRBsets)) OF ARFCN-ValueNR OPTIONAL, -- Need R sl-NumOfSSS-Brepetition-r18 SEQUENCE (SIZE (1..5)) OF INTEGER (2..9) OPTIONAL, -- Need R sl-CPE-StartingPositionS-SSB-r18 INTEGER (1..9) OPTIONAL, -- Need R sl-CWS-ForPsschWithoutHarqAck-r18 ENUMERATED {t1, t8, t16, t32, infinity} OPTIONAL, -- Need R sl-NumOfAdditionalSSSBOccasion-r18 INTEGER (0..4) OPTIONAL, -- Need R sl-SSSBPowerOffsetOfAnchorRBSet-r18 ENUMERATED {value1, value2} OPTIONAL, -- Need R sl-PSFCHPowerOffset-r18 INTEGER (0..10) OPTIONAL, -- Need R sl-RBSetConfigList-r18 SEQUENCE (SIZE (1..5)) OF SL-RBSetConfig-r18 OPTIONAL, -- Need R sl-BWP-PoolConfigCommonA2X-r18 SL-BWP-PoolConfigCommon-r16 OPTIONAL, -- Need R sl-BWP-PRS-PoolConfigCommon-r18 SL-BWP-PRS-PoolConfigCommon-r18 OPTIONAL -- Need R ]] } -- TAG-SL-BWP-CONFIGCOMMON-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
5,811 | 6.2.4 PCF | The Policy Control Function (PCF) includes the following functionality: - Supports unified policy framework to govern network behaviour. - Provides policy rules to Control Plane function(s) to enforce them. - Accesses subscription information relevant for policy decisions in a Unified Data Repository (UDR). - Support PDU Set Handling as defined in clause 5.37.5. NOTE: The PCF accesses the UDR located in the same PLMN as the PCF. The details of the PCF functionality are defined in clause 6.2.1 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 6.2.4 |
5,812 | 8.3.1.1F Enhanced Performance Requirement Type B – Single-layer Spatial Multiplexing with TM10 serving cell configuration and TM9 interference model | The requirements are specified in Table 8.3.1.1F-2, with the addition of the parameters in Table 8.3.1.1F-1 and the downlink physical channel setup according to Annex C.3.2. The purpose of these tests is to verify closed loop rank one performance on one of the antenna ports 7 or 8 without a simultaneous transmission on the other antenna port in the serving cell when the PDSCH transmission configured with TM10 in the serving cell is interfered by PDSCH of one dominant interfering cell applying transmission mode 9 interference model defined in clause B.6.3. The NAICS network assistance is provided when the serving cell TM10 is configured with QCL-type A and PCID based DM-RS scrambling. The neighbouring cell has transmission mode TM9 and NeighCellsInfo-r12 for interfering cell indicates presence of TM9. In 8.3.1.1F-1, Cell 1 is the serving cell, and Cell 2, 3 are interfering cells. The downlink physical channel setup is according to Annex C.3.2 for each of Cell 1, Cell 2 and Cell 3, respectively. Table 8.3.1.1F-1: Test Parameters for Testing CDM-multiplexed DM RS (single layer) with TM10 serving cell configuration and TM9 interference model Table 8.3.1.1F-2: Minimum Performance for Enhanced Performance Requirement Type B, CDM-multiplexed DM RS with TM10 serving cell configuration and TM9 interference model | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.3.1.1F |
5,813 | 4.12.6 UE or Network Requested PDU Session Modification via Untrusted non-3GPP access | The UE or network requested PDU Session Modification procedure via untrusted non-3GPP access is depicted in figure 4.12.6-1. The procedure applies in non-roaming, roaming with LBO as well as in home-routed roaming scenarios. For non-roaming and LBO scenarios, the functional entities in the following procedures are located in the PLMN of the N3IWF. The procedure below is based on the PDU Session Modification procedure specified in clause 4.3.3.2 (for non-roaming and roaming with LBO) and on the PDU Session Modification procedure specified in clause 4.3.3.3 (for home-routed roaming). Figure 4.12.6-1: UE or Network Requested PDU Session Modification via untrusted non-3GPP access 1. If the PDU Session Modification procedure is initiated by the UE, the UE shall send a PDU Session Modification Request message to AMF as specified in step 1 of clause 4.3.2.2. The message shall be sent to N3IWF via the established IPsec SA for NAS signalling. The N3IWF shall transparently forward the PDU Session Modification Request to AMF/SMF. 2. In the case of non-roaming or LBO, the steps 1a (from AMF) to 1e and steps 2-3 as per the PDU Session Modification procedure in clause 4.3.3.2 are executed. In the case of home-routed, the steps 1a (from AMF) to 1d and steps 2-3 as per the PDU Session Modification procedure in clause 4.3.3.3 are executed. 3. The AMF sends N2 PDU Session Resource Modify Request (N2 SM information received from SMF, NAS message) message to the N3IWF. This step is the same as step 4 in clause 4.3.3.2 (for non-roaming and roaming with Local Breakout) and step 5 in clause 4.3.3.3 (for home-routed roaming). 4. The N3IWF may issue IKEv2 signalling exchange with the UE that is related with the information received from SMF according to the IKEv2 specification in RFC 7296 [3]. Based on the N2 SM information received from the SMF, the N3IWF may perform one of the following: 4a. The N3IWF may decide to create a new Child SA for the new QoS Flow(s). In this case, the N3IWF establishes a new Child SA by sending an IKE_CREATE_CHILD_SA request message, which includes the SA, the PDU Session ID, the QFI(s), optionally a DSCP value and optionally the Additional QoS Information specified in clause 4.12a.5. If the Additional QoS Information is received, the UE may reserve non-3GPP Access Network resources according to the Additional QoS Information. 4b. The N3IWF may decide to add or remove QoS Flow(s) to/from an existing Child SA. In this case, the N3WIF updates the QoS Flow and Child SA mapping information by sending an INFORMATIONAL request message, which includes the QFI(s) associated with the Child SA and optionally the Additional QoS Information specified in clause 4.12a.6, which contains the new QoS information that should be associated with the existing Child SA. If the Additional QoS Information is received, the UE may update the reserved non-3GPP Access Network resources for the existing Child SA according to the Additional QoS Information. 4c. The N3IWF may decide to delete an existing Child SA, e.g. when there is no QoS Flow mapped to this Child SA. In this case, the N3IWF deletes the existing Child SA by sending INFORMATIONAL request message, which includes a Delete payload. NOTE: If the N3IWF has included the Default Child SA indication during the establishment of one of the Child SAs of the PDU Session, the N3IWF may not update the mapping between QoS Flows Child SAs. 5. The N3IWF acknowledges N2 PDU Session Request by sending a N2 PDU Session Response Message to the AMF to acknowledge the success or failure of the request. 6. In the case of non-roaming or LBO, step 7 as per the PDU Session Modification procedure in clause 4.3.3.2 is executed. In the case of home-routed, the steps 8-10 as per the PDU Session Modification procedure in clause 4.3.3.3 are executed. 7. The N3IWF sends the PDU Session Modification Command to UE (if received in step 3) and receives the response message from UE. Steps 4a/4c and step 7 may happen consecutively. Steps 7b map happen before step 4b/4d. 8. The N3IWF forwards the NAS message to the AMF. 9. For non-roaming and roaming with LBO, all the steps after step 10 in clause 4.3.3.2 are executed according to the general PDU Session Modification procedure. For home-routed roaming, all steps after step 13 in clause 4.3.3.3 are executed according to the general PDU Session Modification procedure. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.12.6 |
5,814 | Annex M (informative): Functions and procedures over NB-IoT RAT | In the case of conflict between the information in this Annex and other information in the main body of the present document, the information in the main body takes precedence. The following tables list the functions and procedures that are: - Supported or not supported over NB-IoT RAT, including whether for CP CIoT EPS Optimisation only, UP CIoT EPS Optimisation only or both. - Optional for the UE and/or network when using NB-IoT RAT. NOTE: The tables M-1 to M-5 are ordered by clause number according to the present specification. The table M-6 is ordered by clause number according to TS 23.682[ Architecture enhancements to facilitate communications with packet data networks and applications ] [74]. The notation "CP/UP/Both" indicates whether a particular item is supported for CP CIoT EPS Optimisation only, UP CIoT EPS Optimisation only or both. Table M-1: Clause 4 Concepts Table M-2: Clause 5.3 Authentication, security and location management Table M-3: Clause 5.4 Session management, QoS and interaction with PCC Table M-4: Clauses 5.5 and 5.6 Handover and NACC Table M-5: Misc. Table M-6:MTC/CIoT-related items in TS 23.682[ Architecture enhancements to facilitate communications with packet data networks and applications ] [74] | 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") | Annex |
5,815 | 8.7.8 TDD FDD (DC) | The parameters specified in Table 8.7.8-1 are valid for all TDD FDD DC tests unless otherwise stated. Table 8.7.8-1: Common Test Parameters (TDD FDD DC) For UE not supporting 256QAM, the requirements are specified in Table 8.7.8-2, with the addition of the parameters in Table 8.7.8-1 and the downlink physical channel setup according to Annex C.3.2. The test points are applied to UE category and bandwidth combination with maximum aggregated bandwidth as specified inTable 8.7.8-3. The TB success rate shall be sustained during at least 300 frames. For UE supporting 256QAM, the requirements are specified in Table 8.7.8-4, with the addition of the parameters in Table 8.7.7-1 and the downlink physical channel setup according to Annex C.3.2. The test points are applied to UE category and bandwidth combination with maximum aggregated bandwidth as specified inTable 8.7.8-5. The TB success rate shall be sustained during at least 300 frames. For UE supporting 256QAM, the requirements in Table 8.7.8-2 are not applicable. The applicability of ther requirements are specified in Clause 8.1.2.3A. Table 8.7.8-2: Minimum requirement (TDD FDD DC 64QAM) Table 8.7.8-3: Test points for sustained data rate (FRC TDD FDD DC 64QAM) Table 8.7.8-4: Minimum requirement (TDD FDD DC 256QAM) Table 8.7.8-5: Test points for sustained data rate (FRC TDD FDD DC 256QAM) | 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.8 |
5,816 | 5.7.1A Channel spacing for CA | For intra-band contiguous carrier aggregation with two or more component carriers, the nominal channel spacing between two adjacent E-UTRA component carriers is defined as the following unless stated otherwise: where BWChannel(1) and BWChannel(2) are the channel bandwidths of the two respective E-UTRA component carriers according to Table 5.6-1 with values in MHz. The channel spacing for intra-band contiguous carrier aggregation can be adjusted to any multiple of 300 kHz less than the nominal channel spacing to optimize performance in a particular deployment scenario. For intra-band contiguous carrier aggregation with two or more component carriers in Band 46, the requirements apply for both 19.8 MHz and 20.1 MHz nominal carrier spacing between two 20 MHz component carriers, and for 15.0 MHz nominal carrier spacing between 10 MHz and 20 MHz component carriers. For intra-band non-contiguous carrier aggregation the channel spacing between two or more E-UTRA component carriers in different sub-blocks shall be larger than the nominal channel spacing defined in this subclause. | 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 | 5.7.1A |
5,817 | 6.6.1 Exchange of protocol configuration options 6.6.1.1 General | The UE and the PDN GW can exchange protocol configuration options via the dedicated ESM information request procedure or via other ESM procedures. If supported by the network and UE end-to-end for a PDN connection, protocol configuration options shall be exchanged via the Extended protocol configuration options IE. Otherwise the Protocol configuration options IE is used. NOTE 1: In this version of the protocol inter-system mobility to and from NB-S1 mode is supported. During inter-system-mobility from NB-S1 mode to WB-S1 mode the end-to-end support of the Extended protocol configuration options IE can be lost, e.g. if the new MME does not support the Extended protocol configuration options IE. For the UE, the extended protocol configuration options is supported by the network and the UE end-to-end for a PDN connection if - the UE is in NB-S1 mode; - the APN requested for the PDN connection is for UAS services; - the PDN Type requested for the PDN connection is non-IP or Ethernet; - the network has indicated support of the Extended protocol configuration options IE in the last ATTACH ACCEPT or TRACKING AREA UPDATING ACCEPT message and the network has included the Extended protocol configuration options IE in at least one EPS session management message received by the UE for this PDN connection; or - a corresponding PDU session was transferred after inter-system change from N1 mode to S1 mode. For the MME, the extended protocol configuration options is supported by the network and the UE end-to-end for a PDN connection if - the UE is in NB-S1 mode; - the APN requested for the PDN connection is for UAS services; - the PDN Type requested for the PDN connection is non-IP or Ethernet; - the UE has indicated support of the Extended protocol configuration options IE in the last ATTACH REQUEST or TRACKING AREA UPDATING REQUEST message, and the MME has received the Extended protocol configuration options IE in at least one message sent by the PDN GW towards the UE for this PDN connection (for details see 3GPP TS 29.274[ 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 ] [16D]); or - a corresponding PDU session was transferred after inter-system change from N1 mode to S1 mode. NOTE 2: For the PDN GW, the extended protocol configuration options is supported by the network and the UE end-to-end for a PDN connection if the last support indication received from the MME or S-GW indicates that extended protocol configuration options is supported for this PDN connection (for details see 3GPP TS 29.274[ 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 ] [16D]). | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.6.1 |
5,818 | 6.6.2.3.2A Minimum requirement UTRA for CA | For inter-band carrier aggregation with one component carrier per operating band and the uplink active in two E-UTRA bands, the UTRA Adjacent Channel Leakage power Ratio (UTRAACLR) is the ratio of the filtered mean power centred on the assigned channel bandwidth on the component carrier to the filtered mean power centred on an adjacent channel frequency. The UTRA Adjacent Channel Leakage power Ratio is defined per carrier and the requirement is specified in subclause 6.6.2.3.2. For intra-band contiguous carrier aggregation the UTRA Adjacent Channel Leakage power Ratio (UTRAACLR) is the ratio of the filtered mean power centred on the aggregated channel bandwidth to the filtered mean power centred on an adjacent(s) UTRA channel frequency. For intra-band non-contiguous carrier aggregation when all sub-blocks consist of one component carrier the UTRA Adjacent Channel Leakage power Ratio (UTRAACLR) is the ratio of the sum of the filtered mean powers centered on the assigned sub-block frequencies to the filtered mean power centred on an adjacent(s) UTRA channel frequency. UTRAACLR1/2 requirements are applicaple for all sub-blocks and are specified in Table 6.6.2.3.2A-2. UTRAACLR1 is required to be met in the sub-block gap when the gap bandwidth Wgap is 5MHz≤Wgap <15MHz. Both UTRAACLR1 and UTRAACLR2 are required to be met in the sub-block gap when the gap bandwidth Wgap is 15MHz≤Wgap. For combinations of intra-band and inter-band carrier aggregation with three uplink component carriers (up to two contiguously aggregated carriers per band), the UTRA Adjacent Channel Leakage power Ratio (UTRAACLR) is defined as follows. For the E-UTRA band supporting one component carrier, the UTRA Adjacent Channel Leakage power Ratio (UTRAACLR) is the ratio of the filtered mean power centred on the assigned channel bandwidth of the component carrier to the filtered mean power centred on an adjacent(s) UTRA channel frequency and the requirements specified in subclause 6.6.2.3.2 apply. For the E-UTRA band supporting two contiguous component carriers the UTRA Adjacent Channel Leakage power Ratio (UTRAACLR) is the ratio of the filtered mean power centred on the aggregated channel bandwidth to the filtered mean power centred on an adjacent(s) UTRA channel frequency and the requirements specified in subclause 6.6.2.3.2A apply. UTRA Adjacent Channel Leakage power Ratio is specified for both the first UTRA adjacent channel (UTRAACLR1) and the 2nd UTRA adjacent channel (UTRAACLR2). The UTRA channel power is measured with a RRC bandwidth filter with roll-off factor =0.22. The assigned aggregated channel bandwidth power is measured with a rectangular filter with measurement bandwidth specified in Table 6.6.2.3.2A-1 for intraband contiguous carrier aggregation or 6.6.2.3.2A-2 for intraband non-contiguous carrier aggregation. If the measured UTRA channel power is greater than –50dBm then the UTRAACLR shall be higher than the value specified in Table 6.6.2.3.2A-1 for intraband contiguous carrier aggregation or 6.6.2.3.2A-2 for intraband non-contiguous carrier aggregation. For carrier aggregation with one or two uplink component carriers, the UTRAACLR requirements for the PC3 UE are not applicable to the uplink component carrier(s) assigned to one of the E-UTRA band in Band 7, 12, 13, 17, 20, 24, 27, 30, 33, 35, 36, 37, 38, 40, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 68, 70, 71 or 85. Table 6.6.2.3.2A-1: Requirements for UTRAACLR1/2 Table 6.6.2.3.2A-2: Requirements for intraband non-contiguous CA UTRAACLR1/2 | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.6.2.3.2A |
5,819 | 6.10.4 Positioning reference signals | Positioning reference signals shall only be transmitted in resource blocks in downlink subframes configured for positioning reference signal transmission. If both normal and MBSFN subframes are configured as positioning subframes within a cell, the OFDM symbols in a MBSFN subframe configured for positioning reference signal transmission shall use the same cyclic prefix as used for subframe #0. If only MBSFN subframes are configured as positioning subframes within a cell, the OFDM symbols configured for positioning reference signals in the MBSFN region of these subframes shall use extended cyclic prefix length. In a subframe configured for positioning reference signal transmission, the starting positions of the OFDM symbols configured for positioning reference signal transmission shall be identical to those in a subframe in which all OFDM symbols have the same cyclic prefix length as the OFDM symbols configured for positioning reference signal transmission. Positioning reference signals are transmitted on antenna port 6. The positioning reference signals shall not be mapped to resource elements allocated to the core part of the PBCH, PSS or SSS regardless of their antenna port . Positioning reference signals are defined for only. | 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.10.4 |
5,820 | 6.5.3.6 Abnormal cases on the network side | The following abnormal case can be identified: a) No PDN connection with the linked EPS bearer identity activated: If the linked EPS bearer identity included in the BEARER RESOURCE ALLOCATION REQUEST message does not belong to the default EPS bearer context of an established PDN connection, the MME shall reply with a BEARER RESOURCE ALLOCATION REJECT message with ESM cause #43 "invalid EPS bearer identity". b) BEARER RESOURCE ALLOCATION REQUEST message received for a PDN connection established for emergency bearer services: The MME shall reply with a BEARER RESOURCE ALLOCATION REJECT message with ESM cause #31 "request rejected, unspecified". c) BEARER RESOURCE ALLOCATION REQUEST message received from a UE which is in a location where the PLMN is not allowed to operate If the MME determines that the UE is in a location where the PLMN is not allowed to operate, the MME discards the message. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.5.3.6 |
5,821 | 5.16.3.6 Terminating domain selection for IMS voice | When requested by IMS, the UDM/HSS shall be able to query the serving AMF for T-ADS related information. T-ADS is a functionality located in the IMS and is performed as specified in TS 23.221[ Architectural requirements ] [23]. The AMF shall respond to the query with the following information unless the UE is detached: - whether or not IMS voice over PS Session is supported in the registration area (s) where the UE is currently registered; - whether or not IMS voice over PS Session Supported Indication over non-3GPP access is supported in the WLAN where the UE is currently registered; - the time of the last radio contact with the UE; and - the current Access Type and RAT type. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.16.3.6 |
5,822 | 5.3.5.4 Secondary cell group release | The UE shall: 1> as a result of SCG release triggered by E-UTRA (i.e. (NG)EN-DC case) or NR (i.e. NR-DC case): 2> reset SCG MAC, if configured; 2> for each RLC bearer that is part of the SCG configuration: 3> perform RLC bearer release procedure as specified in 5.3.5.5.3; 2> for each BH RLC channel that is part of the SCG configuration: 3> perform BH RLC channel release procedure as specified in 5.3.5.5.10; 2> release the SCG configuration; 2> for all application layer measurement configurations that are part of the SCG configuration: 3> inform upper layers about the release of the application layer measurement configurations; 3> discard any application layer measurement reports which were not yet submitted to lower layers for transmission; 2> remove all the entries within the SCG VarConditionalReconfig, if any; 2> if SCG release was triggered by NR (i.e. NR-DC case): 3> remove all the entries in the condReconfigList within the MCG VarConditionalReconfig for which the RRCReconfiguration within condRRCReconfig does not include the masterCellGroup with reconfigurationWithSync and for which subsequentCondReconfig is not present, if any; 2> else (i.e. EN-DC case): 3> perform VarConditionalReconfiguration CPC removal as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10] clause 5.3.5.9.7; 2> stop timer T310 for the corresponding SpCell, if running; 2> stop timer T312 for the corresponding SpCell, if running; 2> stop timer T304 for the corresponding SpCell, if running. NOTE: Release of cell group means only release of the lower layer configuration of the cell group but the RadioBearerConfig may not be released. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.5.4 |
5,823 | 4.3.5.8 IMS voice over PS Session Supported Indication | The serving PLMN shall send an indication toward the UE during the Attach procedure and Tracking Area Update procedures if an IMS voice over PS session is supported. The serving PLMN uses this indicator to indicate to the UE whether it can expect a successful IMS voice over PS session according to TS 22.173[ IP Multimedia Core Network Subsystem (IMS) Multimedia Telephony Service and supplementary services; Stage 1 ] [73] with a bearer that supports Conversational Voice as specified in TS 23.203[ Policy and charging control architecture ] [6]. A UE with "IMS voice over PS" voice capability should take this indication into account when establishing voice over PS sessions (as specified in TS 23.221[ Architectural requirements ] [27]) as well as when determining whether to deactivate the special handling of ISR locally (as detailed in clause 4.3.5.6). The serving PLMN provides this indication based e.g. on local policy, HPLMN, Voice Support Match Indicator, the SRVCC capability of the network and UE and/or extends of E-UTRAN/UTRAN coverage. The serving PLMN shall indicate to the UE that the UE can expect a successful IMS voice over PS session only if the MME is configured to know that the serving PLMN has a roaming agreement for IMS voice with the HPLMN of the UE. This indication is per TAI list. On request by the HSS, the MME shall indicate the following: - whether or not an IMS voice over PS Session is supported in the TA(s) that are registered for the UE ("IMS voice over PS Session Supported Indication"), together with the time of the last radio contact with the UE; and - the current RAT type. NOTE: In order to support routing of incoming IMS voice calls to the correct domain (PS or CS), the network-based T-ADS (see TS 23.292[ IP Multimedia Subsystem (IMS) centralized services; Stage 2 ] [60] and TS 23.221[ Architectural requirements ] [27]) requires that there is homogeneous support/non-support of IMS voice over PS session for all registered TAs of the UE. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.3.5.8 |
5,824 | 5.30.2.13 Access to SNPN services via Trusted non-3GPP access | Access to SNPN services via Trusted non-3GPP access network follows the specification in the previous (sub)clauses of clause 5.30.2 with the differences as specified in this clause. To access SNPN services via a Trusted non-3GPP access network, the UE follows the procedure for accessing a PLMN via a Trusted non-3GPP access network defined in clause 6.3.12.2 with the following clarifications and additions: - A non-3GPP access network may advertise (e.g. with ANQP), not only the PLMNs with which 5G connectivity is supported (as specified in clause 6.3.12.2), but also the SNPNs with which 5G connectivity is supported and the related parameters and indications defined in clause 5.30.2.2 (i.e. human-readable network name(s), GIN(s), indication whether access using credentials from a Credentials Holder is supported, indication whether SNPN allows registration attempts from UEs that are not explicitly configured to select the SNPN, etc.). - The UE initiates the access network selection procedure specified in clause 6.3.12.2 and constructs a list of available SNPNs. This list contains the SNPNs advertised by all discovered non-3GPP access networks. - The UE selects an SNPN that is included in the list of available SNPNs following the procedure in clause 5.30.2.4. - The UE selects a non-3GPP access network that supports 5G connectivity to the selected SNPN and initiates the registration procedure via Trusted non-3GPP access specified in clause 4.12a.2.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3] in order to register with the selected SNPN via the selected non-3GPP access network. During the EAP authentication procedure the NAI provided by the UE indicates that 5G connectivity to a specific SNPN is required (e.g. NAI = "<username>@nai.5gc.nid<NID>.mnc<MNC>.mcc<MCC>.3gppnetwork.org"). NOTE: In the case of SNPN ID with self-assigned NID, if the UE, when trying to register with an SNPN ID via TNAN X, is rejected by the AMF with a cause code that temporarily prevents the UE from registering with this SNPN ID, the UE does temporarily not attempt to register with the same SNPN ID, even if the same SNPN ID is advertised via another TNAN. - If there are multiple non-3GPP access networks that support 5G connectivity to the selected SNPN, then the UE places these non-3GPP access networks in a prioritized list and selects the highest priority non-3GPP access network from this list. To determine the priority of a non-3GPP access network, the UE shall apply the WLANSP rules (if provided), and the procedure specified in clause 6.6.1.3 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45], "UE procedure for selecting a WLAN access based on WLANSP rules". If the UE is not provided with WLANSP rules, the UE determines the priority of a non-3GPP access network by using implementation means. UE onboarding via Trusted non-3GPP access is supported as follows: - The non-3GPP access network advertises (e.g. via ANQP) an Onboarding enabled indication, as specified in clause 5.30.2.10.2.3. - The UE selects an SNPN advertising the Onboarding enabled indication following the network selection procedure specified in clause 5.30.2.10.2.5. - As part of UE registration via Trusted non-3GPP access, in Figure 4.12a.2.2-1, step 5 of TS 23.502[ Procedures for the 5G System (5GS) ] [3] the UE provides an onboarding indication inside the AN-Parameters. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.30.2.13 |
5,825 | 5.17.2.2 Interworking Procedures with N26 interface 5.17.2.2.1 General | NOTE 1: Additional network slicing and Interworking with EPS with N26 aspects are specified in clause 5.15.7. Interworking procedures using the N26 interface, enables the exchange of MM and SM states between the source and target network. The N26 interface may be either intra-PLMN or inter-PLMN (e.g. to enable inter-PLMN mobility). When interworking procedures with N26 is used, the UE operates in single-registration mode. For the 3GPP access, the network keeps only one valid MM state for the UE, either in the AMF or MME. For the 3GPP access, either the AMF or the MME is registered in the HSS+UDM. The support for N26 interface between AMF in 5GC and MME in EPC is required to enable seamless session continuity (e.g. for voice services) for inter-system change. The UE's subscription may include restriction for Core Network Type (EPC) and RAT restriction for E-UTRA. If so, the UDM provides these restrictions to the AMF. The AMF includes RAT and Core Network type restrictions in the Handover Restriction List to the NR. The AMF and NR use these restrictions to determine if mobility of the UE to EPS or E-UTRA connected to EPS should be permitted. When the UE moves from 5GS to EPS, the SMF determines which PDU Sessions can be relocated to the target EPS, e.g. based on capability of the deployed EPS, operator policies for which PDU Session, seamless session continuity should be supported etc. The SMF can release the PDU Sessions that cannot be transferred as part of the handover or Idle mode mobility. However, whether the PDU Session is successfully moved to the target network is determined by target EPS. Similarly, the UE's subscription may include restriction for Core Network Type (5GC) and RAT restriction for NR. If so, the HSS provides these restrictions to the MME. The MME includes RAT and Core Network type restrictions in the Handover Restriction List to the E-UTRAN. The MME and E-UTRAN use these restrictions to determine if mobility of the UE to 5GS or NR connected to 5GS should be permitted. If the SMF+PGW-C receives the PDU session ID from UE via PCO and know 5GC is not restricted for the PDN connection by user subscription, the SMF+PGW-C sends the mapped QoS parameters to UE. When the UE moves from EPS to 5GS, for the case when the MME has selected SMF+PGW-C even for PDN connections that cannot be relocated to the target 5GS, the SMF+PGW-C determines which PDN Connections can be relocated to the target 5GS, e.g. based on capability of the deployed 5GS, subscription and operator policies for which PDN Connection, seamless session continuity should be supported etc. The SMF+PGW-C and NG-RAN can reject the PDN Connections that cannot be transferred as part of the handover or Idle mode mobility. For the case when the MME has selected standalone P-GW for a PDN connection for which session continuity is not supported and the AMF cannot retrieve the address of the corresponding SMF during EPS to 5GS mobility, the AMF does not move the PDN connection to 5GS. NOTE 2: When applying the AMF planned removal procedure or the procedure to handle AMF failures (see clause 5.21.2) implementations are expected to update the DNS configuration to enable MMEs to discover alternative AMFs if the MME tries to retrieve a UE context from an AMF that has been taken out of service or has failed. This addresses the scenario of UEs performing 5GS to EPS Idle mode mobility and presenting a mapped GUTI pointing to an AMF that has been taken out of service or has failed. In the case of mobility from 5GS to EPS, if the MME lacks certain capability, e.g. MME not supporting 15 EPS bearers, the 5GC shall not transfer the UE EPS bearers and/or EPS PDN connections that are not supported by the EPC network. If the MME does not support 15 EPS bearers, the AMF determines which EBIs cannot be transferred to EPS, and retrieves the EPS bearer contexts from the SMF+PGW-C for the EBIs that can be transferred to EPS. NOTE 3: How the AMF determines which EBIs can be transferred to EPS is according to local configuration, e.g. according to DNN, S-NSSAI, ARP associated with an EBI. In the case of mobility from 5GS to EPS, if the mobility is a result of the PCF modifying the RFSP Index value for the UE to indicate that EPC/E-UTRAN access is prioritized over the 5GS access, the AMF may be sent with a RFSP in Use Validity Time by the PCF as specified in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]. If the AMF receives RFSP in Use Validity Time and selects the RFSP Index in use identical to the authorized RFSP Index as specified in clause 5.3.4.3, then the AMF provides the MME with the RFSP Index in use and the RFSP in Use Validity Time, which indicates the time by which the RFSP Index in use will be used in the MME as specified in clause 4.11.1.5.8 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. NOTE 4: The RFSP in Use Validity Time is to allow the UE to stay in EPS for a period of time to avoid the potential ping-pong issue (i.e. 5GS keeps sending the UE to EPS based on authorized RFSP Index from PCF, and the EPS keeps sending the UE back to 5GS immediately based on the subscribed RFSP Index. NOTE 5: The RFSP in Use Validity Time applies only to EPS but not to 5GS, therefore in the case of mobility from EPS to 5GS, the RFSP in Use Validity Time if received from MME is ignored by the AMF. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.17.2.2 |
5,826 | 9.11.3.18B CIoT small data container | This information element is used to encapsulate the CIoT user data, SMS, or location services message with a size that is not more than 254 octets between the UE and the AMF when the UE is using control plane CIoT 5GS optimization. The CIoT small data container information element is coded as shown in figure 9.11.3.18B.1, figure 9.11.3.18B.2, figure 9.11.3.18B.3, figure 9.11.3.18B.4 and table 9.11.3.18B.1. The CIoT small data container is a type 4 information element with a minimum length of 4 octets and a maximum length of 257 octets. Figure 9.11.3.18B.1: CIoT small data container information element Figure 9.11.3.18B.2: CIoT small data container contents for Data type "Control plane user data" Figure 9.11.3.18B.3: CIoT small data container contents for Data type "Location services message container" Figure 9.11.3.18B.4: CIoT small data container contents for Data type "SMS" Table 9.11.3.18B.1: CIoT small data container 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.18B |
5,827 | 8.3.1.1G Single-layer Spatial Multiplexing (CRS assistance information is configured) | The requirements are specified in Table 8.3.1.1G-2, with the addition of parameters in Table 8.3.1.1G-1. The purpose is to verify the performance of the antenna ports 7 or 8 without a simultaneous transmission on the other antenna port in the serving cell with CRS assistance information. In Table 8.3.1.1G-1, Cell 1 is the serving cell, and Cell 2 and Cell 3 are the aggressor cells. The downlink physical channel setup for Cell 1, Cell2 and Cell 3 is according to Annex C.3.2. The CRS assistance information [7] includes Cell 2 and Cell 3. Table 8.3.1.1G-1: Test parameters of TM9-Single-Layer (2 CSI-RS ports) Table 8.3.1.1G-2: Minimum Performance of TM9-Single-Layer (2 CSI-RS ports) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.3.1.1G |
5,828 | 5.2.8.2.7 Nsmf_PDUSession_ReleaseSMContext service operation | Service operation name: Nsmf_PDUSession_ReleaseSMContext. Description: It allows to release the AMF-SMF association for a certain PDU Session because the PDU Session has been released. Input, Required: SM Context ID. Input, Optional: UE location information, AN type, UE Time Zone, N2 SM Info (Secondary RAT Usage Data), V-SMF only, I-SMF only. Output, Required: Result Indication. Output, Optional: Cause, Small Data Rate Control Status, APN Rate Control Status. See clause 4.3.4.2 and clause 4.3.4.3 for an example usage of this service. If the consumer NF is AMF and the PDU Session indicated by the PDU Session ID had been assigned some EBIs, the AMF locally determines that the corresponding EBI(s) are released. For the use of the "V-SMF only" indication, see clause 4.11.1.2. For the use of the "I-SMF only" indication, see clause 4.23.7.3. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.8.2.7 |
5,829 | 13.10 Default Conference Factory URI for MMTel | The Default Conference Factory URI for MMTel shall take the form of a SIP URI (see IETF RFC 3261 [26]) with a host portion set to the home network domain name as described in clause 13.2 prefixed with "conf-factory.". The user portion shall be set to "mmtel". Examples of the Default Conference Factory URI for MMTel can be found below: EXAMPLE 1: "sip:[email protected]" when the UE has a home network domain name of operator.com. EXAMPLE 2: "sip:[email protected]" for 3GPP systems, when the UE with no ISIM application has a home network domain name of ims.mnc015.mcc234.3gppnetwork.org derived from the same example IMSI as described in clause 13.2. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 13.10 |
5,830 | 5.6.1.6 Service request procedure for initiating an emergency PDU session not accepted by the network | If the service request for initiating an emergency PDU session cannot be accepted by the network, the UE shall perform the procedures as described in subclause 5.6.1.5. If the service request for initiating an emergency PDU session fails due to receiving the AUTHENTICATION REJECT message, the UE shall perform the procedures as described in subclauses 5.4.1.2.2.11, 5.4.1.2.3.1, 5.4.1.2.3A.1 or 5.4.1.3.5. Then if the UE is in the same selected PLMN where the last service request was attempted, the UE shall: a) inform the upper layers of the failure of the procedure; or NOTE 1: This can result in the upper layers requesting another emergency call attempt using domain selection as specified in 3GPP TS 23.167[ IP Multimedia Subsystem (IMS) emergency sessions ] [6]. b) de-register locally, if not de-registered already, attempt initial registration for emergency services. If the service request for initiating an emergency PDU session fails due to abnormal cases a), f) or l) in subclause .7, the UE shall perform the procedures as described in subclause 5.6.1.7. Then if the UE is in the same selected PLMN where the last SERVICE REQUEST message was attempted, the UE shall: a) inform the upper layers of the failure of the procedure; or NOTE 2: This can result in the upper layers requesting another emergency call attempt using domain selection as specified in 3GPP TS 23.167[ IP Multimedia Subsystem (IMS) emergency sessions ] [6] and 3GPP TS 24.229[ IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 ] [14]. b) de-register locally, if not de-registered already, attempt initial registration for emergency services. If the service request for initiating a PDU session for emergency services fails due to abnormal case b) in subclause 5.6.1.7, the UE shall perform the actions as described in subclause 5.6.1.7 and inform the upper layers of the failure to access the network. NOTE 3: This can result in the upper layers requesting another emergency call attempt using domain selection as specified in 3GPP TS 23.167[ IP Multimedia Subsystem (IMS) emergency sessions ] [6]. | 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.1.6 |
5,831 | A.5 Service and service operation description template | The description of a service or service operation in this specification shall be done according to the following template. NOTE: The heading level should follow that of the actual clause where the service is specified. X.x <Nnfname_ServiceName<_OperationName>> X.x.1 Description Service or service operation name: <Nnfname_ServiceName<_OperationName>>. Description: <short descriptive text>. Known NF Consumers: <list of NFs>. Inputs, Required: <list of parameters> -- Parameters required from NF Consumer for successful completion of the service or service operation. Parameters required for the operation of the underlying protocol shall not be listed. Inputs, Optional: <list of parameters> -- Additional parameters that may be provided by NF Consumer for execution of the service or service operation. Parameters required for the operation of the underlying protocol shall not be listed. Outputs, Required: <list of parameters>, < Nnfname_ServiceNameX<_OperationNameY >>, <Other> -- Parameters provided to NF Consumer and/or service triggered upon successful completion of the service and/or other (e.g. procedure triggered). Parameters required for the operation of the underlying protocol shall not be listed. Outputs, Optional: <list of parameters> -- Additional parameters provided to NF Consumer upon successful completion of the service or service operation. Parameters required for the operation of the underlying protocol shall not be listed. X.x.2 Service/service operation information flow <Information flow of the service or service operation offered by NF Producer to NF Consumer over the NF Producer service-based interface>. NOTE: This information flow can require invoking other services. In this case, the invoked services are represented as described in clause A.3. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | A.5 |
5,832 | 4.15.13.4 Specific procedure for the 5GC assistance to member UE selection based on the UE's current location, historical location and direction and UE separation distance | Figure 4.15.13.4-1: 5GC assistance to Member UE selection based on the UE's current and historical location, direction and separation distance 1. AF requests 5GS assistance to support the Member UE selection by considering the UE's historical location, UE's current location, direction and UE separation distance. AF includes the UE lists and the following criteria as part of the member UE selection request: - UE historical location: The Target AoI where the UEs have been roving over the historical nomadic period before moving into the FL coverage area. - UE current location: The current AoI which is the coverage area of the FL training server where the selected UEs located in to participate in the FL operation. - UE Direction: Select the UE with the different direction in the FL coverage Area. - UE separation distance: Select UEs that are geographically separated, fulfilling the separation distance no smaller than the certain predefined separation distance. When providing a target area for e.g. FL operation, the AF may provide sub-areas, and provide a maximum number of UEs that should take part in FL from each sub-area. 2. NEF translates the GPSIs to SUPIs and maps the filtering criteria into the corresponding UE filtering information. 3-4. The NEF invokes Namf_EventExposure_Subscribe service operation with the UE list, the current AoI and event ID = Location report. AMF will provide a list of UEs that are within the current AoI to the NEF using the Namf_EventExposure_Notify service operation. The NEF obtains the list of possible member UEs from AMF within the current AoI. 5. In order to identify the appropriate NWDAF which can provide analytics output to derive the visited AOI info and get the UE direction for the possible target member UEs above, the NEF initiates NWDAF discovery request (Analytics ID = UE mobility/Relative Proximity, AOI = Target AOI) with UE list received from step 4. 6-7. The NEF invokes NWDAF Analytics Info request (UE list received from step 4, Analytics ID = UE mobility, Relative Proximity, Filters include "Visited AoI = Target AOI", "target period = historical nomadic period" and "proximity attributes"). In a response, NWDAF provides a list of UEs that were ever roving within the target AOI, at the minimum, over the historical nomadic period. Additionally, NWDAF provides a list of UEs location in the order of which the UE passes through. Thus, the NEF gets the corresponding statistics of UE mobility, the UE's direction and distance between UEs in the group/list. 8-9. Based on the information provided by the AMF and NWDAF, the NEF can determine the FL candidate UEs which are now within the FL coverage area but were roving within the target AOI over the historical nomadic period and UE with the different direction and separated from each other fulfilling the minimum distance threshold as requested by AF. The NEF notifies AF for such UE candidate list. 10. The NEF also needs to consider the list of UEs which are now within the FL coverage area, but may move out of the FL coverage area. Therefore, for each UE in the candidate list in steps 8-9, the NEF invokes the Namf_EventExposure_Notify service with UE ID = SUPI, Event ID=UE moving in/out of AOI in order to keep tracking the movement of the UE(s). 11-12. If step 10 identifies any UE which is moving out of the FL coverage area, the NEF may further notify the AF of the given UE which is moving out the coverage. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.15.13.4 |
5,833 | 20.4.1 Re-Auth-Request Command | The Re-Auth-Request (RAR) command, defined in IETF RFC 6733 (DIAMETER BASE) [111], is indicated by the Command-Code set to 258 and the message flags’ ‘R’ bit set. The relevant AVPs that are of use for the SGmb interface are detailed in the ABNF description below. Other valid AVPs for this command are not used for SGmb purposes and should be ignored by the receiver or processed according to the relevant specifications. The bold marked AVPs in the message format indicate new optional AVPs for SGmb, or modified existing AVPs. Message Format: <RAR> ::= < Diameter Header: 258, REQ, PXY > < Session-Id > { Origin-Host } { Origin-Realm } { Destination-Realm } { Destination-Host } { Auth-Application-Id } { Re-Auth-Request-Type } [ Called-Station-Id ] [ Framed-IP-Address] [ Framed-IPv6-Prefix ] [ Framed-Interface-Id ] [ MBMS-Access-Indicator ] [ MBMS-StartStop-Indication ] [ MBMS-Service-Area ] [ QoS-Information ] [ MBMS-Session-Duration ] [ MBMS-Session-Identity ] [ MBMS-Session-Repetition-number ] [ TMGI ] * [ 3GPP-SGSN-Address ] * [ 3GPP-SGSN-IPv6-Address ] [ MBMS-Time-To-Data-Transfer ] [ MBMS-Data-Transfer-Start ] [ MBMS-Data-Transfer-Stop ] [ MBMS-Flags ] [ MBMS-User-Data-Mode-Indication ] [ MBMS-BMSC-SSM-IP-Address ] [ MBMS-BMSC-SSM-IPv6-Address ] [ MBMS-Flow-Identifier ] [ CN-IP-Multicast-Distribution ] [ MBMS-HC-Indicator ] [ MBMS-GW-UDP-Port-Indicator] ; for IP unicast encapsulated user data [ MBMS-GW-SSM-IP-Address ] ; for IP multicast encapsulated user data [ MBMS-GW-SSM-IPv6-Address ] ; for IP multicast encapsulated user data [ MBMS-BMSC-SSM-UDP-Port ] ; for IP multicast encapsulated user data [ MBMS-Cell-List ] [ Local-M1-Information ] [ Origin-State-Id ] * [ Proxy-Info ] * [ Route-Record ] * [ Supported-Features ] [ Restart-Counter ] For the MBMS Session Start procedure, RAR is sent by the BM-SC to the MBMS GW(s) that will deliver the MBMS service when it is ready to send data. This is a request to activate all necessary bearer resources in the network for the transfer of MBMS data. The RAR message contains either an IPv4 address included in 3GPP-SGSN-Address AVP or an IPv6 address included in 3GPP-SGSN-IPv6-Address AVP for each participating MBMS control plane nodes (MMEs, SGSNs). The MBMS-Time-to-Data-Transfer AVP shall be included to indicate the expected time between the reception of the MBMS Session Start and the transmission of MBMS data flows. For E-UTRAN access, the RAR message may also contain the MBMS-Data-Transfer-Start AVP containing the absolute time stamp of the data delivery start. The RAR message shall also contain the MBMS-Service-Area AVP. If the MBMS Cell List feature is supported, or if the BM-SC does not yet know whether the MBMS-GW supports this feature, the RAR may contain the MBMS-Cell-List AVP. For the distributed MCE architectures, i.e. when the MCE is part of eNB as described in clause 15.1.1 in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [98], the MBMS-Data-Transfer-Start AVP should be used at MBSFN operation mode to ensure synchronized session control and to facilitate a graceful reallocation of resources for the MBSFN when needed. The RAR message shall also contain the Local-M1-Information AVP if the BM-SC determines to use the local MBMS information as specified in 3GPP TS 23.285[ Architecture enhancements for V2X services ] [112]. The MBMS-Flags AVP may provide specific control indications in relation to MBMS, e.g. whether the MBMS Session Start procedure is used to re-establish an MBMS session. For the MBMS Session Update procedure, RAR is sent by the BM-SC in order for the MBMS GW(s) to update their session attributes. If the MBMS service area or the MBMS cell list needs to be changed, the MBMS-Service-Area AVP shall be included in the RAR. If the MBMS Cell List feature is supported and the MBMS cell list needs to be changed, the MBMS-Cell-List AVP shall also be included. If the MBMS-Service-Area AVP but no MBMS-Cell-List AVP is included, this shall indicate that any MBMS Cell List included in a previous RAR does no longer apply. If the Access indicator needs to be updated, it shall be included in the MBMS-Access-Indicator AVP. For E-UTRAN access, the RAR message may also contain the MBMS-Data-Transfer-Start AVP containing the absolute time stamp of the data delivery start. For the distributed MCE architectures, i.e. when the MCE is part of eNB as described in clause 15.1.1 in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [98], the MBMS-Data-Transfer-Start AVP should be used at MBSFN operation mode to ensure synchronized session control and to facilitate a graceful reallocation of resources for the MBSFN when needed. The MBMS-StartStop-Indication AVP with the value UPDATE shall be included. The MBMS-Time-To-Data-Transfer with AVP the value set to 0 shall be included. The MBMS-Session-Duration AVP shall be included to indicate the duration of the remaining part of the MBMS session. The 3GPP-SGSN-Address AVP and the 3GPP-SGSN-IPv6-Address AVP shall be included if the related lists of MBMS control plane nodes (MMEs, SGSNs) in the MBMS GW(s) have changed. If the ARP needs to be changed, the QoS-Information AVP shall be included. The other bold marked AVPs shall be included as given by the previous, corresponding MBMS Session Start procedure. For the MBMS Session Stop procedure, RAR is sent by the BM-SC to the MBMS GW(s) when it considers the MBMS session to be terminated. The session is typically terminated when there is no more MBMS data expected to be transmitted for a sufficiently long period of time to justify a release of bearer plane resources in the network. For E-UTRAN access, the RAR message may also contain the MBMS-Data-Transfer-Stop AVP containing the absolute time stamp of the data delivery stop. The MBMS-Flags AVP may provide specific control indications, e.g. whether the MBMS Session Stop procedure is used to release the MBMS bearer context locally. For the MBMS Session Start procedure, the Qos-Information AVP indicates the QoS that is required for the MBMS bearer service for the actual MBMS session. Only the QoS-Class-Identifier AVP, Max-Requested-Bandwidth-DL AVP, Guaranteed-Bitrate-DL AVP and Allocation-Retention-Priority AVP within the QoS-Information AVP are applicable for the MBMS bearer service. The MBMS-Service-Area AVP is passed from BM-SC transparently through MBMS GW to the MMEs/SGSN(s) that are relevant for the actual MBMS bearer service. The MBMS-Cell-List AVP is also passed transparently through MBMS GW to the MMEs. The MBMS-Access-Indicator AVP indicates in which radio access types the MBMS bearer service shall be broadcasted, i.e UTRAN, or E-UTRAN, or both. The usage of MBMS-StartStop-Indication AVP, Session-Id AVP, Framed-IP-Address AVP, Framed-IPv6-Prefix AVP, Framed-Interface-Id AVP, Called-Station-Id AVP and MBMS-Flow-Identifier AVP can refer to Gmb interface as described in clause 17.6.5. If unicast mode is used, the MBMS GW shall select an IP unicast address and a destination UDP port that is unique within the MBMS GW or that IP unicast address. If IP multicast encapsulation of application IP multicast datagram is used over Sgi-mb, the BM-SC shall select a source UDP port that is unique within the BM-SC for that IP multicast address. For the MBMS Heartbeat procedure, RAR is sent by the BM-SC to the MBMS GW, or vice-versa. The RAR message shall contain the following AVPs: - the MBMS-StartStop-Indication AVP set to the value "heartbeat"; - the Restart-Counter AVP set to the local restart counter of the sender. | 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.4.1 |
5,834 | 6.9.1 Modulation | The block of bits transmitted on one PHICH in one subframe shall be modulated as described in clause 7.1, resulting in a block of complex-valued modulation symbols, where . Table 6.9.1-1 specifies the modulation mappings applicable for the physical hybrid ARQ indicator channel. Table 6.9.1-1: PHICH modulation schemes. The block of modulation symbols shall be symbol-wise multiplied with an orthogonal sequence and scrambled, resulting in a sequence of modulation symbols according to where and is a cell-specific scrambling sequence generated according to clause 7.2. The scrambling sequence generator shall be initialised with at the start of each subframe. The sequence is given by Table 6.9.1-2 where the sequence index corresponds to the PHICH number within the PHICH group. Table 6.9.1-2: Orthogonal sequences for PHICH | 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.9.1 |
5,835 | 6.5.2 Requirements | Based on operator policy, application needs, or both, the 5G system shall support an efficient user plane path between UEs attached to the same network, modifying the path as needed when the UE moves during an active communication. The 5G network shall enable a Service Hosting Environment provided by operator. Based on operator policy, the 5G network shall be able to support routing of data traffic between a UE attached to the network and an application in a Service Hosting Environment for specific services, modifying the path as needed when the UE moves during an active communication. Based on operator policy, application needs, or both, the 5G system shall support an efficient user plane path, modifying the path as needed when the UE moves or application changes location, between a UE in an active communication and: - an application in a Service Hosting Environment; or - an application server located outside the operator’s network; or - an application server located in a customer premises network or personal IoT network. The 5G network shall maintain user experience (e.g. QoS, QoE) when a UE in an active communication moves from a location served by a Service Hosting Environment to: - another location served by a different Service Hosting Environment; or - another location served by an application server located outside the operator’s network; or - another location served by an application server located in a customer premises network or personal IoT network, and vice versa. The 5G network shall maintain user experience (e.g. QoS, QoE) when an application for a UE moves as follows: - within a Service Hosting Environment; or - from a Service Hosting Environment to another Service Hosting Environment; or - from a Service Hosting Environment to an application server located place outside the operator’s network; or - from a Service Hosting Environment to an application server located in a customer premises network or personal IoT network, and vice versa. The 5G network shall be able to interact with applications in a Service Hosting Environment for efficient network resource utilization and offloading data traffic to the most suitable Service Hosting Environment, e.g. close to the UE's point of attachment to the access network or based on usage information. NOTE: To accomplish offloading data traffic, usage information might be exposed to the Service Hosting Environment. The 5G network shall support configurations of the Service Hosting Environment in the network (e.g. access network, core network), that provide application access close to the UE's point of attachment to the access network. The 5G system shall support mechanisms to enable a UE to access the closest Service Hosting Environment for a specific hosted application or service. The 5G network shall enable instantiation of applications for a UE in a Service Hosting Environment close to the UE's point of attachment to the access network. The 5G system shall be able to suspend or stop application instances in a Service Hosting Environment. NOTE: Not all applications will always be available in all Service Hosting Environments. Therefore, it may be needed to instantiate an application at a Service Hosting Environment nearby for serving a particular UE. Based on operator policy, the 5G system shall provide a mechanism such that one type of traffic (from a specific application or service) to/from a UE can be offloaded close to the UE's point of attachment to the access network, while not impacting other traffic type to/from that same UE. Satellite access related efficient user plane requirements are covered in clause 6.46.6. The 5G System shall enable the discovery of a suitable Hosted Service. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.5.2 |
5,836 | 12.8 Sustained downlink data rate with active Sidelink | The purpose of this test is to verify the downlink data rate is not impacted when Sidelink resource are also configured. The test parameters are in Table 12.8.1-1. Cell 1 is the serving cell and UE 1 and UE 2 are transmitters of Prose Direct Communication. The test UE is expected to receive all PDSCH transmissions, and prioritize the transmission of ACK/NACK over the reception of UE 2’s PSSCH. The test cases apply to UE categories and bandwidth combinations with maximum aggregated bandwidth as specified in Table 12.8.1-2. The minimum requirements are specified in Table 12.8.1-3. The TB success rate in the cellular link shall be sustained during at least 300 frames. Table 12.8.1-1: Test parameters for sustained downlink data rate (FDD 64QAM) with active Sidelink Table 12.8.1-2: Test cases for sustained data rate Table 12.8.1-3: Minimum requirements (FDD 64QAM) with active Sidelink | 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 | 12.8 |
5,837 | 4.2.1.2 Number of initial E-RABs successfully established | a) This measurement provides the number of initial E-RABs successfully established. The measurement is split into subcounters per E-RAB QoS level (QCI). b) CC c) On transmission by the eNodeB/RN of an INITIAL CONTEXT SETUP RESPONSE message, each E-RAB successfully established is added to the relevant measurement per QCI, the possible QCIs are included in TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [9]. The sum of all supported per QCI measurements shall equal the total number of E-RABs successfully setup. In case only a subset of per QCI measurements is supported, a sum subcounter will be provided first. d) Each measurement is an integer value. The number of measurements is equal to the number of QCIs plus a possible sum value identified by the .sum suffix. e) The measurement name has the form ERAB.EstabInitSuccNbr.QCI where QCI identifies the E-RAB level quality of service class. f) EUtranCellFDD EUtranCellTDD g) Valid for packet switched traffic h) EPS | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.2.1.2 |
5,838 | 10.5.4.17 Keypad facility | The purpose of the keypad facility information element is to convey IA5 characters, e.g. entered by means of a terminal keypad (see note). The keypad facility information element is coded as shown in figure 10.5.103/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The keypad facility is a type 3 information element with 2 octets length. Figure 10.5.103/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Keypad facility information element NOTE: In the 3GPP system this information element is only used to transfer one DTMF digit (0, 1, ... , 9, A, B, C, D, *, #) as one IA5 character. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 10.5.4.17 |
5,839 | 21.2 Home Agent – Access Point Name (HA-APN) 21.2.1 General | The HA-APN is composed of two parts as follows: - The HA-APN Network Identifier; this defines to which external network the HA is connected. - The HA-APN Operator Identifier; this defines in which PLMN the HA serving the HA-APN is located. The HA-APN Operator Identifier is placed after the HA-APN Network Identifier. The HA-APN consisting of both the Network Identifier and Operator Identifier corresponds to a FQDN of a HA; the HA-APN has, after encoding as defined in the paragraph below, a maximum length of 100 octets. The encoding of the HA-APN shall follow the Name Syntax defined in IETF RFC 2181 [18], IETF RFC 1035 [19] and IETF RFC 1123 [20]. The HA-APN consists of one or more labels. Each label is coded as a one octet length field followed by that number of octets coded as 8 bit ASCII characters. Following IETF RFC 1035 [19] the labels shall consist only of the alphabetic characters (A-Z and a-z), digits (0-9) and the hyphen (-). Following IETF RFC 1123 [20], the label shall begin and end with either an alphabetic character or a digit. The case of alphabetic characters is not significant. The HA-APN is not terminated by a length byte of zero. For the purpose of presentation, a HA-APN is usually displayed as a string in which the labels are separated by dots (e.g. "Label1.Label2.Label3"). | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 21.2 |
5,840 | 4.3.30 Unlicensed spectrum aggregation (LAA/LWA/LWIP/NR-U) | Unlicensed spectrum aggregation in EPS can use either LTE Licensed-Assisted Access (LAA) that is using the Carrier Aggregation (CA) RAN configuration defined in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [5], or LWA/LWIP aggregation using WLAN or NR-U as secondary RAT that is using the Dual Connectivity architecture defined in clause 4.3.2a and TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [5]. If the UE has Access Restriction for Unlicensed Spectrum in the form of LAA, LWA/LWIP, or NR-U (either signalled from the HSS, or, locally generated by VPLMN policy in the MME) the MME signals this to the E-UTRAN as part of Handover Restriction List. An eNodeB supporting aggregation with unlicensed spectrum in the form of LAA, LWA/LWIP, or NR-U checks whether the UE is allowed to use unlicensed spectrum. If the UE is not allowed to use Unlicensed Spectrum, the eNodeB shall not establish dual connectivity or carrier aggregation (CA) with LTE in unlicensed spectrum in the form of LAA, WLAN as a secondary RAT in the form of LWA/LWIP, or NR-U as a secondary RAT. At inter-RAT handover from GERAN/UTRAN, the Access Restriction for Unlicensed Spectrum is either already in the MME's UE context, or is obtained from the HSS during the subsequent Tracking Area Update procedure (i.e. not from the source SGSN or source RAN). In both inter-RAT handover cases, any Access Restriction for use of Unlicensed Spectrum is then signalled to the E-UTRAN. NOTE: This signalling of the Access Restriction during the TAU after the inter-RAT handover procedure means that there is a small risk that unlicensed spectrum resources are transiently allocated. | 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.30 |
5,841 | 4.7.6.3 P-TMSI reallocation completion by the network | Upon receipt of the P-TMSI REALLOCATION COMPLETE message, the network shall stop the timer T3350 and shall consider both the old and the new P-TMSI and the corresponding P-TMSI signatures as valid until the old P-TMSI can be considered as invalid by the network (see subclause 4.7.1.5). In A/Gb mode, the GMM layer shall notify the LLC layer that the P-TMSI has been changed (see 3GPP TS 44.064[ Mobile Station - Serving GPRS Support Node (MS-SGSN); Logical Link Control (LLC) Layer Specification ] [78a]). | 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.6.3 |
5,842 | 5.2.1.12 Cellular Text telephone Modem (CTM) selection | The mobile station can send a CTM support indication in the Bearer Capability IE in call establishment messages to inform the network of the use of CTM text in the call. When the mobile station indicates speech and support of CTM text telephony, the network shall select a speech codec and additionally CTM text telephony detection/conversion functions as specified in 3GPP TS 23.226[ Global text telephony (GTT); Stage 2 ] [92] and 3GPP TS 26.226[ Cellular text telephone modem; General description ] [93], if such functions are available. NOTE: If CTM support is indicated by the mobile station, then it supports CTM text telephony together with any supported speech codec and for any supported radio access. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.2.1.12 |
5,843 | – SL-MeasObjectList | The IE SL-MeasObjectList concerns a list of SL measurement objects to add or modify for a destination. SL-MeasObjectList information element -- ASN1START -- TAG-SL-MEASOBJECTLIST-START SL-MeasObjectList-r16 ::= SEQUENCE (SIZE (1..maxNrofSL-ObjectId-r16)) OF SL-MeasObjectInfo-r16 SL-MeasObjectInfo-r16 ::= SEQUENCE { sl-MeasObjectId-r16 SL-MeasObjectId-r16, sl-MeasObject-r16 SL-MeasObject-r16, ... } SL-MeasObjectId-r16 ::= INTEGER (1..maxNrofSL-ObjectId-r16) SL-MeasObject-r16 ::= SEQUENCE { frequencyInfoSL-r16 ARFCN-ValueNR, ... } -- TAG-SL-MEASOBJECTLIST-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
5,844 | 6.16.2.2 Connection Suspend | When the ng-eNB initiates the Connection Suspend procedure, it sends N2 Suspend Request message to the AMF. Upon reception of the N2 Suspend Request message, the AMF shall check its local policy. If the local policy indicates that a new NH derivation is needed, the AMF shall increase its locally kept NCC value by one and compute a fresh NH from its stored data using the function defined in Annex A.10. The AMF shall store that fresh {NH, NCC} pair and send it to the ng-eNB in the N2 Suspend Response message. Upon receipt of the N2 Suspend Response message from the AMF and if the message includes a {NH, NCC} pair, the ng-eNB shall store the fresh {NH, NCC} pair in the N2 Suspend Response message and remove any existing unused stored {NH, NCC} pairs. The ng-eNB shall send to the UE an RRC Release with releaseCause set to rrc-suspend message that is ciphered and integrity protected in PDCP layer using current AS security context. The ng-eNB shall include a fresh I-RNTI, and an NCC in that RRC Release message. The I-RNTI is used for context identification, and the UE ID part of the I-RNTI assigned by the ng-eNB shall be different in consecutive suspends of the same UE. This is to avoid tracking of UEs based on the I-RNTI. If the ng-eNB has a fresh and unused pair of {NCC, NH}, the ng-eNB shall include the NCC in the RRC Release message. Otherwise, the ng-eNB shall include the same NCC associated with the current KgNB in the RRC Release message. The NCC is used for AS security. The ng-eNB shall delete the current AS keys KRRCenc, KUPenc (if available), and KUPint (if available) after sending the RRC Release message to the UE, but shall keep the current AS key KRRCint. If the sent NCC value is fresh and belongs to an unused pair of {NCC, NH}, the ng-eNB shall save the pair of {NCC, NH} in the current UE AS security context and shall delete the current AS key KgNB. If the sent NCC value is equal to the NCC value associated with the current KgNB, the ng-eNB shall keep the current AS key KgNB and NCC. The ng-eNB shall store the sent I-RNTI together with the current UE context including the remainder of the AS security context. Upon receiving the RRC Release with releaseCause set to rrc-suspend message from the ng-eNB, the UE shall decrypt the RRC Release message using the KRRCenc key and verify that the integrity of the received the RRC Release message is correct by checking the PDCP MAC-I. If this verification is successful, then the UE shall take the received NCC value and save it as stored NCC with the current UE context. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.16.2.2 |
5,845 | – NCR-AperiodicFwdConfig | The IE NCR-AperiodicFwdConfig is used to configure a list of aperiodic forwarding time resources for NCR-Fwd access link. NCR-AperiodicFwdConfig information element -- ASN1START -- TAG-NCR-APERIODICFWDCONFIG-START NCR-AperiodicFwdConfig-r18 ::= SEQUENCE { aperiodicFwdTimeRsrcToAddModList-r18 SEQUENCE (SIZE (1..maxNrofAperiodicFwdTimeResource-r18)) OF NCR-AperiodicFwdTimeResource-r18 OPTIONAL, -- Need N aperiodicFwdTimeRsrcToReleaseList-r18 SEQUENCE (SIZE (1..maxNrofAperiodicFwdTimeResource-r18)) OF NCR-AperiodicFwdTimeResourceId-r18 OPTIONAL, -- Need N referenceSCS-r18 SubcarrierSpacing OPTIONAL, -- Need M aperiodicBeamFieldWidth-r18 INTEGER (1..6) OPTIONAL, -- Need M numberOfFields-r18 INTEGER (1..32) OPTIONAL, -- Need M ... } NCR-AperiodicFwdTimeResource-r18 ::= SEQUENCE { aperiodicFwdTimeRsrcId-r18 NCR-AperiodicFwdTimeResourceId-r18, slotOffsetAperiodic-r18 INTEGER (0..14), symbolOffset-r18 INTEGER (0..maxNrofSymbols-1), durationInSymbols-r18 INTEGER (1..28) } NCR-AperiodicFwdTimeResourceId-r18 ::= INTEGER (0..maxNrofAperiodicFwdTimeResource-1-r18) -- TAG-NCR-APERIODICFWDCONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
5,846 | 4.3.5.6 Idle mode signalling reduction function | The Idle mode Signalling Reduction (ISR) function provides a mechanism to limit signalling during inter-RAT cell-reselection in idle mode (ECM-IDLE, PMM-IDLE, GPRS STANDBY states). NOTE 1: The Idle mode Signalling Reduction function is mandatory for E-UTRAN UEs that support GERAN and/or UTRAN and optional for core network. The UE's ISR capability in the UE Core Network Capability element is for test purpose. The MME/SGSN activates ISR only if the Serving GW supports the ISR. How MME/SGSN determines a Serving GW supports ISR is implementation dependent. ISR shall be activated by decision of the CN nodes and shall be explicitly signalled to the UE as "ISR activated" in the RAU and TAU Accept messages. The UE may have valid MM parameters both from MME and from SGSN. The "Temporary Identity used in Next update" (TIN) is a parameter of the UE's MM context, which identifies the UE identity that the UE shall indicate in the next RAU Request, TAU Request or Attach Request message. The TIN also identifies the status of ISR activation in the UE. The TIN can take one of the three values, "P-TMSI", "GUTI" or "RAT-related TMSI". The UE shall set the TIN when receiving an Attach Accept, a TAU Accept or RAU Accept message according to the rules in table 4.3.5.6-1. Table 4.3.5.6-1: Setting of the TIN When "ISR Activated" is indicated by the RAU/TAU Accept message but the UE shall not set the TIN to "RAT-related TMSI" is a special situation. Here the UE has deactivated ISR due to special situation handling. By maintaining the old TIN value the UE remembers to use the RAT specific TMSI indicated by the TIN when updating with the CN node of the other RAT. Only if the TIN is set to "RAT-related TMSI" ISR behaviour is enabled for the UE, i.e. the UE can change between all registered areas and RATs without any update signalling and it listens for paging on the RAT it is camped on. If the TIN is set to "RAT-related TMSI", the UE's P-TMSI and RAI as well as its GUTI and TAI(s) shall remain registered with the network and shall remain valid in the UE. Table 4.3.5.6-2: Temporary UE Identity that the UE shall indicate in Attach Request and TAU/RAU Request (as "old GUTI" or as "old P-TMSI/RAI" information element) Table 4.3.5.6-2 shows which temporary identity the UE shall indicate in a Tracking or Routing Area Update Request or in an Attach Request message, when the UE stores these as valid parameters. Situations may occur that cause unsynchronized state information in the UE, MME and SGSN. Such special situations trigger a deactivation of ISR locally in the UE. The UE shall deactivate ISR locally by setting its TIN to the temporary identity of the currently used RAT in following special situations: - Modification of any EPS bearer context or PDP context which was activated before the ISR is activated in the UE; - At the time when the UE moves from E-UTRAN to GERAN/UTRAN or moves from GERAN/UTRAN to E-UTRAN by means other than PSHO, if any EPS bearer context or PDP context activated after the ISR was activated in the UE exists; - At the time when the UE moves from GERAN/UTRAN to E-UTRAN by means other than PSHO and CS to PS SRVCC, if the PDP contexts were suspended in GERAN and not successfully resumed before returning to E-UTRAN; - After updating either MME or SGSN about the change of the UE specific DRX parameters to guarantee that the other CN node is also updated; - After updating either MME or SGSN about the change of the UE Core Network Capabilities to guarantee that the other CN node is also updated; - E-UTRAN selection by a UTRAN-connected UE (e.g. when in URA_PCH to release Iu on UTRAN side); - E-UTRAN selection from GERAN READY state; - GERAN selection by an E-UTRAN-connected UE via Cell Change Order that is not for CS fallback; - After a LAU procedure if the UE has CS fallback and/or SMS over SGs activated. - For a UE that is IMS registered for voice, then after that UE moves from a Tracking Area List that supports IMS voice over PS sessions (see 4.3.5.8 for more information) to one that does not, and vice versa. It shall be possible, e.g. using Device Management or initial provisioning, to configure the UE to apply/not apply this particular exception. NOTE 2: A UE moving between Tracking Area Lists that both support IMS voice over PS sessions, or that both do not support IMS voice over PS sessions, is unaffected by the above. The UE shall deactivate ISR locally by setting its TIN to the temporary identity of the RAT that is still available to the UE in following special situations: - After the RAT-specific Deactivate ISR timer expires, e.g. because the coverage of that RAT is lost or the RAT is no more selected by the UE (this may result also in implicit detach by SGSN or MME). ISR shall be deactivated in the UE by the CN node using normal update signalling, i.e. by omitting the signalling of "ISR Activated", in following special situations: - CN node change resulting in context transfer between the same type of CN nodes (SGSN to SGSN or MME to MME); - Serving GW change; - When the UE only has bearers related to emergency bearer service; - When the UE is registered for RLOS service; - TAU or RAU when UE moves over the border between local and macro network where SIPTO at local network with stand-alone GW and Serving GW relocation without mobility are supported in the core network. - TAU or RAU when the network confirms to use PSM for the UE. If tracking area list or routing area covers both local network and macro network, the ISR shall not be activated if the UE is allowed to use SIPTO at local network and Serving GW relocation without mobility are supported in the core 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.3.5.6 |
5,847 | 6.3 Principles for Network Function and Network Function Service discovery and selection 6.3.1 General | The NF discovery and NF service discovery enable Core Network entities (NFs or Service Communication Proxy (SCP)) to discover a set of NF instance(s) and NF service instance(s) for a specific NF service or an NF type. NF service discovery is enabled via the NF discovery procedure, as specified in clauses 4.17.4, 4.17.5, 4.17.9 and 4.17.10 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. Unless the expected NF and NF service information is locally configured on the requester NF, e.g. when the expected NF service or NF is in the same PLMN as the requester NF, the NF and NF service discovery is implemented via the Network Repository Function (NRF). NRF is the logical function that is used to support the functionality of NF and NF service discovery and status notification as specified in clause 6.2.6. NOTE 1: NRF can be colocated together with SCP e.g. for communication option D, depicted in Annex E. In order for the requested NF type or NF service to be discovered via the NRF, the NF instance need to be registered in the NRF. This is done by sending a Nnrf_NFManagement_NFRegister containing the NF profile. The NF profile contains information related to the NF instance, such as NF instance ID, supported NF service instances (see clause 6.2.6 for more details regarding the NF profile). The registration may take place e.g. when the producer NF instance and its NF service instance(s) become operative for the first time. The NF service registration procedure is specified in clause 4.17.1 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. In order for the requester NF or SCP to obtain information about the NF and/or NF service(s) registered or configured in a PLMN/slice, based on local configuration the requester NF or SCP may initiate a discovery procedure with the NRF by providing the type of the NF and optionally a list of the specific service(s) it is attempting to discover. The requester NF or SCP may also provide other service parameters e.g. slicing related information. For the detailed service parameter(s) used for specific NF and NF service discovery refer to clause 5.2.7.3.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. The requester NF may also provide NF Set related information to enable reselection of NF instances within the NF set. The requester NF may also provide the required supported features of the NF. For some Network Functions which have access to the subscription data (e.g. HSS, UDM) the NRF may need to resolve the NF Group ID corresponding to a subscriber identifier. If the NRF has no stored configuration mapping identity sets/ranges to NF Group ID locally, the NRF may retrieve the NF Group ID corresponding to a specific subscriber identifier from the UDR using the Nudr_GroupIDmap_Query service operation. In the case of Indirect Communication, a NF Service Consumer employs an SCP which routes the request to the intended target of the request. If the requester NF is configured to delegate discovery, the requester NF may omit the discovery procedure with the NRF and instead delegate the discovery to the SCP; the SCP will then act on behalf of the requester NF. In this case, the requester NF adds any necessary discovery and selection parameters to the request in order for the SCP to be able to do discovery and associated selection. The SCP may interact with the NRF to perform discovery and obtain discovery result and it may interact with the NRF or UDR to obtain NF Group ID corresponding to subscriber identifier. NOTE 2: For delegated discovery of the HSS or the UDM, the SCP can rely on the NRF to discover the group of HSS/UDM instance(s) serving the provided user identity, or in some deployments the SCP can first query the UDR for the HSS/UDM Group ID for the provided user identity. It is expected that the stage 3 defines a single encoding for the user identity provided by the service consumer that can be used for both variants of delegated discovery to avoid that the service consumer needs to be aware of the SCP behaviour. The NRF provides a list of NF instances and NF service instances relevant for the discovery criteria. The NRF may provide the IP address or the FQDN of NF instance(s) and/or the Endpoint Address(es) of relevant NF service instance(s) to the NF Consumer or SCP. The NRF may also provide NF Set ID and/or NF Service Set ID to the NF Consumer or SCP. The response contains a validity period during which the discovery result is considered valid and can be cached. The result of the NF and NF service discovery procedure is applicable to any subscriber that fulfils the same discovery criteria. The entity that does the discovery may cache the NF profile(s) received from the NF/NF service discovery procedure. During the validity period, the cached NF profile(s) may be used for NF selection for any subscriber matching the discovery criteria. NOTE 3: Refer to TS 29.510[ 5G System; Network function repository services; Stage 3 ] [58] for details on using the validity period. In the case of Direct Communication, the requester NF uses the discovery result to select NF instance and a NF service instance that is able to provide a requested NF Service (e.g. a service instance of the PCF that can provide Policy Authorization). In the case of Indirect Communication without Delegated Discovery, the requester NF uses the discovery result to select a NF instance while the associated NF service instance selection may be done by the requester NF and/or an SCP on behalf of the requester NF. In both the cases above, the requester NF may use the information from a valid cached discovery result for subsequent selections (i.e. the requester NF does not need to trigger a new NF discovery procedure to perform the selection). In the case of Indirect Communication with Delegated Discovery, the SCP will discover and select a suitable NF instance and NF service instance based on discovery and selection parameters provided by the requester NF and optional interaction with the NRF. The NRF to be used may be provided by the NF consumer as part of the discovery parameters, e.g. as a result of a NSSF query. The SCP may use the information from a valid cached discovery result for subsequent selections (i.e. the SCP does not need to trigger a new NF discovery procedure to perform the selection). NOTE 4: In a given PLMN, Direct Communication, Indirect Communication, or both may apply. The requester NF or SCP may subscribe to receive notifications from the NRF of a newly updated NF profile of an NF (e.g. NF service instances taken in or out of service), or newly registered de-registered NF instances. The NF/NF service status subscribe/notify procedure is defined in clauses 4.17.7 and 4.17.8 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. For NF and NF service discovery across PLMNs, the NRF in the local PLMN interacts with the NRF in the remote PLMN to retrieve the NF profile(s) of the NF instance(s) in the remote PLMN that matches the discovery criteria. The NRF in the local PLMN reaches the NRF in the remote PLMN by forming a target PLMN specific query using the PLMN ID provided by the requester NF. The NF/NF service discovery procedure across PLMNs is specified in clause 4.17.5 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. NOTE 5: See TS 29.510[ 5G System; Network function repository services; Stage 3 ] [58] for details on using the target PLMN ID specific query to reach the NRF in the remote PLMN. For topology hiding, see clause 6.2.17. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 6.3 |
5,848 | 10.2 IP Fragmentation | It is specified here how the fragmentation mechanism shall work with GTP-C. Fragmentation should be avoided if possible. Examples of fragmentation drawbacks are: - Fragmentation is inefficient, since the complete IP header is duplicated in each fragment. - If one fragment is lost, the complete packet has to be discarded. The reason is that no selective retransmission of fragments is possible. Path MTU discovery should be used, especially if GTPv2-C message is encapsulated with IPv6 header. The application should find out the path MTU, and thereby utilise more efficient fragmentation mechanisms. | 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 | 10.2 |
5,849 | 5.3.2 Scenario | Police respond to a nuisance complaint about a UAV. Before entering the area where the report was made, they query the UTM to see if any have a live UAV in the area. For example, the police might supply a civic address, geographic polygon, a list of identities of known persistent offenders, etc. The UTM would return the subscription, equipment identity, route data, live location, and all data for the flight of any devices operating as a UAS in the submitted area or matching the submitted identity. This could lead to a further request for more data to attempt to make visual contact with (a) the UAV, and (b) the UAV operator. | 3GPP TS 22.825 | Study on Remote Identification of Unmanned Aerial Systems (UAS) | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 5.3.2 |
5,850 | 6.2.4A Enhanced Resource-Element Groups (EREGs) | EREGs are used for defining the mapping of enhanced control channels to resource elements. There are 16 EREGs, numbered from 0 to 15, per physical resource block pair. Number all resource elements, except resource elements carrying DM-RS for antenna ports for normal cyclic prefix or for extended cyclic prefix, in a physical resource-block pair cyclically from 0 to 15 in an increasing order of first frequency, then time. All resource elements with number in that physical resource-block pair constitutes EREG number . For frame structure type 3, if the higher layer parameter subframeStartPosition indicates 's07' and the downlink transmission starts in the second slot of a subframe, the above definition applies to the second slot of that subframe instead of the first slot. | 3GPP TS 36.211 | Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation | RAN1 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.2.4A |
5,851 | 1.5 Use of logical channels in A/Gb mode | The logical control channels are defined in 3GPP TS 45.002[ None ] [32]. In the following those control channels are considered which carry signalling information or specific types of user packet information: i) Broadcast Control CHannel (BCCH): downlink only, used to broadcast Cell specific information; ii) Synchronization CHannel (SCH): downlink only, used to broadcast synchronization and BSS identification information; iii) Paging CHannel (PCH): downlink only, used to send page requests to Mobile Stations (MSs); iv) Random Access CHannel (RACH): uplink only, used to request a Dedicated Control CHannel; v) Access Grant CHannel (AGCH): downlink only, used to allocate a Dedicated Control CHannel; vi) Standalone Dedicated Control CHannel (SDCCH): bi-directional; vii) Fast Associated Control CHannel (FACCH): bi-directional, associated with a Traffic CHannel; viii) Slow Associated Control CHannel (SACCH): bi-directional, associated with a SDCCH or a Traffic CHannel; ix) Cell Broadcast CHannel (CBCH): downlink only used for general (not point to point) short message information; x) Notification CHannel (NCH): downlink only, used to notify mobile stations of VBS (Voice Broadcast Service) calls or VGCS (Voice Group Call Service) calls. Two service access points are defined on signalling layer 2 which are discriminated by their Service Access Point Identifiers (SAPI) (see 3GPP TS 44.006[ None ] [19]): i) SAPI 0: supports the transfer of signalling information including user-user information; ii) SAPI 3: supports the transfer of user short messages. Layer 3 selects the service access point, the logical control channel and the mode of operation of layer 2 (acknowledged, unacknowledged or random access, see 3GPP TS 44.005[ None ] [18] and 3GPP TS 44.006[ None ] [19]) as required for each individual message. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 1.5 |
5,852 | – MeasIdleConfig | The IE MeasIdleConfig is used to convey information to UE about measurements requested to be done while in RRC_IDLE or RRC_INACTIVE. MeasIdleConfig information element -- ASN1START -- TAG-MEASIDLECONFIG-START MeasIdleConfigSIB-r16 ::= SEQUENCE { measIdleCarrierListNR-r16 SEQUENCE (SIZE (1..maxFreqIdle-r16)) OF MeasIdleCarrierNR-r16 OPTIONAL, -- Need S measIdleCarrierListEUTRA-r16 SEQUENCE (SIZE (1..maxFreqIdle-r16)) OF MeasIdleCarrierEUTRA-r16 OPTIONAL, -- Need S ... } MeasIdleConfigDedicated-r16 ::= SEQUENCE { measIdleCarrierListNR-r16 SEQUENCE (SIZE (1..maxFreqIdle-r16)) OF MeasIdleCarrierNR-r16 OPTIONAL, -- Need N measIdleCarrierListEUTRA-r16 SEQUENCE (SIZE (1..maxFreqIdle-r16)) OF MeasIdleCarrierEUTRA-r16 OPTIONAL, -- Need N measIdleDuration-r16 ENUMERATED{sec10, sec30, sec60, sec120, sec180, sec240, sec300, spare}, validityAreaList-r16 ValidityAreaList-r16 OPTIONAL, -- Need N ... } ValidityAreaList-r16 ::= SEQUENCE (SIZE (1..maxFreqIdle-r16)) OF ValidityArea-r16 ValidityArea-r16 ::= SEQUENCE { carrierFreq-r16 ARFCN-ValueNR, validityCellList-r16 ValidityCellList OPTIONAL -- Need N } ValidityCellList ::= SEQUENCE (SIZE (1.. maxCellMeasIdle-r16)) OF PCI-Range MeasIdleCarrierNR-r16 ::= SEQUENCE { carrierFreq-r16 ARFCN-ValueNR, ssbSubcarrierSpacing-r16 SubcarrierSpacing, frequencyBandList MultiFrequencyBandListNR OPTIONAL, -- Need R measCellListNR-r16 CellListNR-r16 OPTIONAL, -- Need R reportQuantities-r16 ENUMERATED {rsrp, rsrq, both}, qualityThreshold-r16 SEQUENCE { idleRSRP-Threshold-NR-r16 RSRP-Range OPTIONAL, -- Need R idleRSRQ-Threshold-NR-r16 RSRQ-Range OPTIONAL -- Need R } OPTIONAL, -- Need R ssb-MeasConfig-r16 SEQUENCE { nrofSS-BlocksToAverage-r16 INTEGER (2..maxNrofSS-BlocksToAverage) OPTIONAL, -- Need S absThreshSS-BlocksConsolidation-r16 ThresholdNR OPTIONAL, -- Need S smtc-r16 SSB-MTC OPTIONAL, -- Need S ssb-ToMeasure-r16 SSB-ToMeasure OPTIONAL, -- Need S deriveSSB-IndexFromCell-r16 BOOLEAN, ss-RSSI-Measurement-r16 SS-RSSI-Measurement OPTIONAL -- Need S } OPTIONAL, -- Need S beamMeasConfigIdle-r16 BeamMeasConfigIdle-NR-r16 OPTIONAL, -- Need R ... } MeasIdleCarrierEUTRA-r16 ::= SEQUENCE { carrierFreqEUTRA-r16 ARFCN-ValueEUTRA, allowedMeasBandwidth-r16 EUTRA-AllowedMeasBandwidth, measCellListEUTRA-r16 CellListEUTRA-r16 OPTIONAL, -- Need R reportQuantitiesEUTRA-r16 ENUMERATED {rsrp, rsrq, both}, qualityThresholdEUTRA-r16 SEQUENCE { idleRSRP-Threshold-EUTRA-r16 RSRP-RangeEUTRA OPTIONAL, -- Need R idleRSRQ-Threshold-EUTRA-r16 RSRQ-RangeEUTRA-r16 OPTIONAL -- Need R } OPTIONAL, -- Need S ... } CellListNR-r16 ::= SEQUENCE (SIZE (1..maxCellMeasIdle-r16)) OF PCI-Range CellListEUTRA-r16 ::= SEQUENCE (SIZE (1..maxCellMeasIdle-r16)) OF EUTRA-PhysCellIdRange BeamMeasConfigIdle-NR-r16 ::= SEQUENCE { reportQuantityRS-Indexes-r16 ENUMERATED {rsrp, rsrq, both}, maxNrofRS-IndexesToReport-r16 INTEGER (1.. maxNrofIndexesToReport), includeBeamMeasurements-r16 BOOLEAN } RSRQ-RangeEUTRA-r16 ::= INTEGER (-30..46) -- TAG-MEASIDLECONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
5,853 | 16.12.5.5 System Information | The in-coverage L2 U2N Remote UE is allowed to acquire any necessary SIB(s) over Uu interface irrespective of its PC5 connection to L2 U2N Relay UE. The L2 U2N Remote UE can also receive the system information from the L2 U2N Relay UE after PC5 connection establishment with L2 U2N Relay UE. The L2 U2N Remote UE in RRC_CONNECTED can use the on-demand SIB framework as specified in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [12] to request the SIB(s) via L2 U2N Relay UE. The L2 U2N Remote UE in RRC_IDLE or RRC_INACTIVE can inform L2 U2N Relay UE of its requested SIB type(s) via PC5-RRC message. Then, L2 U2N Relay UE triggers on-demand SI/SIB acquisition procedure as specified in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [12] according to its own RRC state (if needed) and sends the acquired SI(s)/SIB(s) to L2 U2N Remote UE via PC5-RRC message. Any SIB that the RRC_IDLE or RRC_INACTIVE L2 U2N Remote UE has a requirement to use (e.g., for relay purpose) can be requested by the L2 U2N Remote UE (from the L2 U2N Relay UE or the network). For SIBs that have been requested by the L2 U2N Remote UE from the L2 U2N Relay UE, the L2 U2N Relay UE forwards them again in case of any update for requested SIB(s). In case of RRC_CONNECTED L2 U2N Remote UE(s), it is the responsibility of the network to send updated SIB(s) to L2 U2N Remote UE(s) when they are updated. The L2 U2N Remote UE de-configures SI request with L2 U2N Relay UE when entering into RRC_CONNECTED state. For SIB1 forwarding, for L2 U2N Remote UE, both request-based delivery (i.e., SIB1 request by the U2N Remote UE) and unsolicited forwarding are supported by L2 U2N Relay UE, of which the usage is left to L2 U2N Relay UE implementation. If SIB1 changes, for L2 U2N Remote UE in RRC_IDLE or RRC_INACTIVE, the L2 U2N Relay UE always forwards SIB1. For the L2 U2N Remote UE in RRC_IDLE or RRC_INACTIVE, the short message over Uu interface is not forwarded by the L2 U2N Relay UE to the L2 U2N Remote UE. The L2 U2N Relay UE can forward PWS SIBs to its connected L2 U2N Remote UE(s). RAN sharing is supported for L2 U2N Relay UE. In particular, the L2 U2N Relay UE may forward, via discovery message, cell access related information before the establishment of a PC5-RRC connection. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.12.5.5 |
5,854 | 5.4.3.3 Reception of the MobilityFromNRCommand by the UE | The UE shall: 1> stop timer T310, if running; 1> stop timer T312, if running; 1> if T316 is running: 2> stop timer T316; 2> if the UE supports RLF-Report for fast MCG recovery procedure: 3> set the elapsedTimeT316 in the VarRLF-Report to the value of the elapsed time of the timer T316; 3> set the pSCellId to the global cell identity of the PSCell, if available, otherwise to the physical cell identity and carrier frequency of the PSCell; 2> else: 3> clear the information included in VarRLF-Report, if any; 1> if T390 is running: 2> stop timer T390 for all access categories; 2> perform the actions as specified in 5.3.14.4; 1> inform upper layers about the release of all application layer measurement configurations; 1> discard any application layer measurement reports which were not yet submitted to lower layers for transmission; 1> if the targetRAT-Type is set to eutra: 2> consider inter-RAT mobility as initiated towards E-UTRA; 2> forward the nas-SecurityParamFromNR to the upper layers, if included; 1> else if the targetRAT-Type is set to utra-fdd: 2> consider inter-RAT mobility as initiated towards UTRA-FDD; 2> forward the nas-SecurityParamFromNR to the upper layers, if included; 1> if successHO-Config is configured: 2> consider itself to be configured to provide the successful handover information for inter-RAT handover in accordance with 5.7.10.6; 1> else: 2> consider itself not to be configured to provide the successful handover information for inter-RAT handover. 1> access the target cell indicated in the inter-RAT message in accordance with the specifications of the target RAT. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.4.3.3 |
5,855 | 5.3.5.13b SCG deactivation | Upon initiating the procedure, the UE shall: 1> consider the SCG to be deactivated; 1> indicate to lower layers that the SCG is deactivated; 1> if bfd-and-RLM is configured to true: 2> perform radio link monitoring on the SCG; 2> indicate to lower layers to perform beam failure detection on the PSCell; 1> else: 2> stop radio link monitoring on the SCG; 2> indicate to lower layers to stop beam failure detection on the PSCell; 2> stop timer T310 for this cell group, if running; 2> stop timer T312 for this cell group, if running; 2> reset the counters N310 and N311; 1> if the UE was in RRC_CONNECTED and the SCG was activated before receiving the message for which this procedure is initiated: 2> if SRB3 was configured before the reception of the RRCReconfiguration or of the RRCConnectionReconfiguration and SRB3 is not to be released according to any RadioBearerConfig included in the RRCReconfiguration or in the RRCConnectionReconfiguration as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10]: 3> trigger the PDCP entity of SRB3 to perform SDU discard as specified in TS 38.323[ NR; Packet Data Convergence Protocol (PDCP) specification ] [5]; 3> re-establish the RLC entity of SRB3 as specified in TS 38.322[ NR; Radio Link Control (RLC) protocol specification ] [4]. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.5.13b |
5,856 | 5.3.9.2 Insert Subscriber Data procedure | The Insert Subscriber Data procedure is illustrated in Figure 5.3.9.2-1. Figure 5.3.9.2-1: Insert Subscriber Data procedure 1. The HSS sends an Insert Subscriber Data (IMSI, Subscription Data) message to the MME. 2. 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. The update result should be contained in the Ack message. The MME initiates appropriate action according to the changed subscriber data (e.g. MME initiates detach if the UE is not allowed to roam in this network). For received PDN subscription contexts that have no related active PDN connection in the MME, no further action is required except storage in the MME. Otherwise if the subscribed QoS Profile has been modified and the UE is in ECM-CONNECTED state or in ECM-IDLE state when ISR is not activated but the UE is reachable by the MME, the HSS Initiated Subscribed QoS Modification procedure, as described in Figure 5.4.2.2-1, is invoked from step 2a. When ISR is not activated and the UE is in ECM IDLE state and is not reachable by the MME, e.g. when the UE is suspended, when the UE has entered into power saving mode or when the PPF is cleared in the MME, the HSS Initiated Subscribed QoS Modification procedure, as described in Figure 5.4.2.2-1, is invoked from step 2a at the next ECM IDLE to ECM CONNECTED transition. If the UE is in ECM-IDLE state and the ISR is activated, this procedure is invoked at the next ECM-IDLE to ECM-CONNECTED transition. If the UE is in ECM-IDLE state and the ISR is not activated and if the subscription change no longer allows the PDN connection, the MME initiated PDN disconnection procedure in clause 5.10.3 is used to delete the concerned PDN connection. If the MME receives RAT specific Subscribed Paging Time Window that is different from the one stored in the MME MM context, the MME updates RAT specific Subscribed Paging Time Window parameter in the MME MM context to the value received from the HSS. If the UE is in ECM-CONNECTED state and connected via a CSG or hybrid cell, the MME shall check the received CSG subscription data. If the MME detects that the CSG membership to that cell has changed or expired, the MME initiates the procedure in clause 5.16. If the MME received a changed Service Gap Time parameter in the updated subscription data, the MME shall provide the new Service Gap Time value to the UE in the next Tracking Area Update Accept message, or, if the UE does not send any Tracking Area Update Request within a certain time period that shall be longer than any PSM or eDRX interval used by the UE, the MME may initiate a detach with reattach required of the UE or an RRC connection release with release cause load balancing TAU required of the UE. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.3.9.2 |
5,857 | O.3 Authentication procedure | Figure O.3-1 shows the details of the authentication procedure as part of the initial registration procedure specified in clause 4.10a of TS 23.316[ Wireless and wireline convergence access support for the 5G System (5GS) ] [79] following the principles listed in clause O.2. It uses EAP-TLS as an example, but other EAP methods can also be supported. The W-AGF acts on behalf of the N5GC device during the registration process. The link between the N5GC device and the RG, and between the RG and the W-AGF can be any data link (L2) that supports EAP encapsulation. Figure O.3-1: Registration and authentication of a non-5G capable device to the 5GC In the following, the procedure for registration and authentication of an N5GC device to the 5GC is described: 1. The N5GC device connects to the W-AGF via a RG which is configured as a layer 2 bridge. The W-AGF is associated with a 5GC and acts on behalf of the N5GC device during its registration process. 2a. The W-AGF initiates the EAP authentication procedure by sending an EAP request/Identity to the N5GC device via the RG, which acts as an L2 bridge device and forwards the ethernet frame to the N5GC device. The EAP message is encapsualted inside an L2 frame (e.g., EAPOL). 2b. In response, the N5GC device sends back an EAP response/Identity including its Network Access Identifier (NAI) in the form of username@realm. NOTE 1: If TLS subscription identifier privacy protection is supported , as in "Section 2.1.4. Privacy" of RFC 5216 [38] for TLS 1.2 or in RFC 8446 [60] for TLS 1.3, the "username" part must be is either omitted or "anonymous". 3. The W-AGF creates a registration request on behalf of the N5GC device with an indication that the registration is on behalf of an N5GC device. The SUPI of the N5GC device is the NAI as received from the device, and the W-AGF constructs the SUCI from this SUPI using the NULL scheme. 4a. The W-AGF selects the AMF/SEAF. 4b. The W-AGF sends to the AMF/SEAF a registration request on behalf of the N5GC device. The registration request includes the NAI SUCI, wireline network name if available, and a device capability indicator (e.g., the device is non-5G capable). 4c. The AMF/SEAF selects the AUSF based on the SUCI in the received registration request and sends a Nausf_UEAuthentication_Authenticate Request message to the AUSF. It contains the SUCI of the N5GC device, and an indicator that the request is on behalf of the N5GC device. 5a. The AUSF sends a Nudm_UEAuthentication_Get Request to the UDM. It contains the SUCI of the N5GC device and the N5GC device indicator. 5b. The UDM invokes the SIDF to map the SUCI to the SUPI and selects an authentication method, e.g., EAP-TLS, based on the SUPI. When the "username" part of the SUPI is "anonymous" or omitted, the UDM may select an authentication method based on the “realm” part of the SUPI, the N5GC device indicator, a combination of the "realm" part and the N5GC device indicator, or the UDM local policy. 5c. The UDM sends a Nudm_UEAuthentication_Get Response to the AUSF, which contains the SUPI of the N5GC device and an indicator of the selected authentication method, e.g., EAP-TLS. NOTE 2: Steps 6a-14c describe the exchange of EAP-TLS between the AUSF and the N5GC device, based on TLS 1.2 without subscription identifier privacy protection. If the operator determines to provide subscription identifier privacy for the N5GC in TLS layer, the EAP TLS server needs to support privacy either inherently (e.g., in TLS 1.3) or via separate privacy option (e.g., in TLS 1.2). When TLS 1.2 is used, the N5GC device would need to behave as described in "Section 2.1.4. Privacy" of RFC 5216 [38] where instead of sending the client certificate in cleartext over the air, the N5GC device sends TLS certificate (no cert) during the first TLS handshake and sends TLS certificate (client certificate) during the second TLS handshake within the TLS session negotiated form the first TLS handshake. 6a. The AUSF starts EAP-TLS by sending to the AMF/SEAF a Nausf_UEAuthentication_Authenticate Response message containing an EAP-Request message of EAP-type=EAP-TLS with the Start (S) bit set, denoted as EAP-Request/EAP-TLS [TLS start]. 6b. The AMF/SEAF forwards the EAP-Request/EAP-TLS [TLS start] in the Authentication Request message to the W-AGF. 6c. After receiving the EAP-Request/EAP-TLS [TLS start] message from AMF/SEAF, the W-AGF forwards the EAP-Request/EAP-TLS [TLS start] message to the N5GC device in an L2 message, leaving out the ABBA and ngKSI parameters. 7a. After receiving the EAP-Request/EAP-TLS [TLS start] message from the W-AGF, the N5GC device replies to the W-AGF with an EAP-Response/EAP-TLS message whose data field encapsulates a TLS client_hello message. Such EAP-Response message, denoted as EAP-Response/EAP-TLS [client_hello], is encapsulated in an L2 message. 7b. The W-AGF forwards the EAP-Response/EAP-TLS [client_hello] to the AMF/SEAF in an Authentication Response message. 7c. The AMF/SEAF forwards the EAP-Response/EAP-TLS [client_hello] message to the AUSF in a Nausf_UEAuthentication_Authenticate Request message. 8a. The AUSF replies to the AMF/SEAF with EAP-Request/EAP-TLS message whose data field encapsulates a TLS server_hello message, a TLS server certificate message, a TLS server_key_exchange message, a TLS client certificate_request message, and a TLS server_hello_done message. Such EAP-Request message, denoted as EAP-Request/EAP-TLS [server_hello], is encapsulated in a Nausf_UEAuthentication_Authenticate Response message. 8b. The AMF/SEAF forwards the EAP-Request/EAP-TLS [server_hello] message to the W-AGF in an Authentication Request message. 8c. The W-AGF forwards the EAP-Request/EAP-TLS [server_hello] to the N5GC device in an L2 message. 9. The N5GC device authenticates the AUSF by validating the server certificate included in the EAP-Request/EAP-TLS [server_hello] message received in step 8c. The N5GC device needs to be provisioned with certificates of a trust anchor to validate the AUSF server certificate. In addition, the N5GC device also needs to be provisioned with its own client certificate. 10a. If the TLS server authentication is successful, then the N5GC device replies to the W-AGF with EAP-Response/EAP-TLS in an L2 message. The data field of the EAP-Response/EAP-TLS message contains a TLS client certificate message, a TLS client_key_exchange message, a TLS certificate_verify message, a TLS change_cipher_spec message, and TLS finished message. This EAP-Response message is denoted as EAP-Response/EAP-TLS [client_certificate]. 10b. The W-AGF forwards to the AMF/SEAF the EAP-Response/EAP-TLS [client_certificate] in an Authentication Response message. 10c. The AMF/SEAF forwards the EAP-Response/EAP-TLS [client_certificate] message to the AUSF in a Nausf_UEAuthentication_Authenticate Request message. 11. The AUSF authenticates the N5GC device by verifying the client certificate received in the EAP-Response/EAP-TLS [client_certificate] message. Among other validations, the AUSF verifies that the client certificate is issued by a certificate authority trusted by the AUSF. If the client certificate is verified successfully, the AUSF continues to step 12a. Otherwise the AUSF returns an EAP-failure message. The AUSF needs to be provisioned with certificates of trust anchor to verify client certificates. 12a. The AUSF sends to the AMF/SEAF an EAP-Request/EAP-TLS message with its data field encapsulating a TLS change_cipher_spec message and a TLS server finished. This EAP-Request message, denoted as EAP-Request/EAP-TLS [server_finished], is encapsulated in a Nausf_UEAuthentication_Authenticate Response message. 12b. The AMF/SEAF forwards EAP-Request/EAP-TLS [server_finished] message to the W-AGF in an Authentication Request message. 12c. The W-AGF forwards EAP-Request/EAP-TLS [server_finished] message to the N5GC device in an L2 message. 13a. The N5GC sends to the W-AGF an EAP-Response/EAP-TLS message with its data field set to empty, denoted as EAP-Response/EAP-TLS [empty], in an L2 message 13b. The W-AGF forwards to the AMF/SEAF the EAP-Response/EAP-TLS [empty] message in an Authentication Response message. 13c. The AMF/SEAF forwards the EAP-Response/EAP-TLS [empty] message to the AUSF in a Nausf_UEAuthentication_Authenticate Request message. 14a. The AUSF sends to the AMF/SEAF an EAP-Success message along with the SUPI in a Nausf_UEAuthentication_Authenticate Response message. If the SUPI received from the UDM in step 5c is anonymous, the AUSF derives the SUPI from the client identifier in the TLS client certificate. AUSF does not perform the derivation of KAUSF nor KSEAF based on the indicator of an N5GC device received in step 4c, nor sends KSEAF to AMF/SEAF. NOTE 2a: It is left to implementation if the AUSF verifies that the SUPI derived from the client certificate belongs to a valid susbcription in the network and returns an EAP-failure message if there is a miss-match. 14b. The AMF/SEAF forwards to the W-AGF the EAP-Success message in an Authentication Result message or a Security Mode Command message. 14c. The W-AGF forwards to the N5GC device the EAP-Success message in an L2 message, and the authentication procedure is finished. NOTE 3: Neither the AUSF nor the N5GC device performs further 5G related key derivation from EMSK, since neither 5G AS nor 5G NAS security is used in this setting. 15. The AUSF sends a UDM_Nudm_UEAuthentication_ResultConfirmation Request message to the UDM, including the SUPI obtained from the TLS client certificate, SN-name, the authentication method (i.e., EAP-TLS), the authentication result, and a timestamp. 16. The UDM stores the authentication result accordingly. 17. The UDM sends a UDM_Nudm_UEAuthentication_ResultConfirmation Response message to the AUSF. 18. The AMF sends a Nudm_UEContextManagement_Registration Request message to the UDM. 19. The UDM authorizes the registration request based on authentication result stored in step 16 and other information (e.g., UE subscription profile). 20. The UDM sends a Nudm_UEContextManagement_Registration Response message to the AMF. 21. The AMF sends Registration Accept message to the W-AGF | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | O.3 |
5,858 | 5.4.4.5 Abnormal cases in the UE | The following abnormal cases can be identified: a) Requested identity is not available If the UE cannot encode the requested identity in the IDENTITY RESPONSE message, e.g. because no valid USIM is available, then it shall encode the identity type as "no identity". b) Transmission failure of IDENTITY RESPONSE message indication from lower layers (if the identification procedure is triggered by a tracking area updating procedure or an attach procedure) The UE shall abort the identification procedure and re-initiate the tracking area updating procedure if the identification procedure is triggered by a tracking area updating procedure. The UE shall abort the identification procedure and re-initiate the attach procedure if the identification procedure is triggered by an attach procedure. c) Transmission failure of IDENTITY RESPONSE message indication with TAI change from lower layers (if the identification procedure is triggered by a service request procedure) If the current TAI is not in the TAI list, the identification procedure shall be aborted and a tracking area updating procedure shall be initiated. If the current TAI is still part of the TAI list, the identification procedure shall be aborted and it is up to the UE implementation how to re-run the ongoing procedure that triggered the identification procedure. d) Transmission failure of IDENTITY RESPONSE message indication without TAI change from lower layers (if the identification procedure is triggered by a service request procedure) The identification procedure shall be aborted and it is up to the UE implementation how to re-run the ongoing procedure that triggered the identification 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.4.5 |
5,859 | 10.2.2 Composition of the CTSMSI | bit No 22 1 +-------------------------------------------+ | | | +----------------------+ Type|<-----------Significant Part---------->| CTSMSI 22 bits <-------------------------------------------> Figure 13: Structure of CTSMSI The CTSMSI is composed of the following elements: - CTSMSI Type. Its length is 2 bits; - Significant Part. Its length is 20 bits. The following CTSMSI Type values have been allocated for use by CTS: 00 Default Individual CTSMSI; 01 Reserved; 10 Assigned Individual CTSMSI; 11 Assigned Connectionless Group CTSMSI. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 10.2.2 |
5,860 | 6.11.1 Services and Functions | The main service and functions of the BAP sublayer include: - Transfer of data; - Routing of packets to next hop; - Determination of BAP destination and BAP path for packets from upper layers; - Determination of egress BH RLC channels for packets routed to next hop; - Differentiating traffic to be delivered to upper layers from traffic to be delivered to egress link; - Flow control feedback and polling signalling; - BH RLF detection indication, BH RLF recovery indication, and BH RLF indication; - BAP header rewriting. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 6.11.1 |
5,861 | 18 Small Data Transmission 18.0 General | Small Data Transmission (SDT) is a procedure allowing data and/or signalling transmission while remaining in RRC_INACTIVE state (i.e. without transitioning to RRC_CONNECTED state). SDT is enabled on a radio bearer basis and can be initiated either by the UE in case of MO-SDT (Mobile Originated SDT) or by the network in case of MT-SDT (Mobile Terminated SDT). MO-SDT is initiated by the UE only if less than or equal to a configured amount of UL data awaits transmission across all radio bearers for which SDT is enabled, the DL RSRP is above a configured threshold, and a valid SDT resource is available as specified in clause 5.27.1 of TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [6]. MT-SDT is initiated by the network with an indication to the UE in a paging message when DL data awaits transmission for radio bearers configured for SDT; based on the indication, the UE initiates the MT-SDT only if the DL RSRP is above a configured threshold as specified in clause 5.27.1 of TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [6]. When MT-SDT is initiated by the UE, a resume cause indicating MT-SDT is included in the RRCResumeRequest/RRCResumeRequest1. Maximum duration the SDT procedure can last is dictated by a SDT failure detection timer that is configured by the network (see clause 6.2.2 of TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [12]). Network can enable MO-SDT, MT-SDT, or both in a cell. SDT procedure is initiated with either a transmission over RACH (configured via system information) or over Type 1 CG resources (configured via dedicated signalling in RRCRelease). The SDT resources can be configured on initial BWP for both RACH and CG. RACH and CG resources for SDT can be configured on either or both of NUL and SUL carriers. The CG resources for SDT are valid only within the PCell of the UE when the RRCRelease with suspend indication is received. CG resources are associated with one or multiple SSB(s). For RACH, the network can configure 2-step and/or 4-step RA resources for MO-SDT. When both 2-step and 4-step RA resources for MO-SDT are configured, the UE selects the RA type according to clause 9.2.6. If MT-SDT procedure is initiated over RACH, only the RACH resources not configured for SDT can be used by the UE. CFRA is not supported for SDT over RACH. Once initiated, the SDT procedure is either: - successfully completed after the UE is directed to RRC_IDLE (via RRCRelease) or to continue in RRC_INACTIVE (via RRCRelease or RRCReject) or to RRC_CONNECTED (via RRCResume or RRCSetup); or - unsuccessfully completed upon cell re-selection, expiry of the SDT failure detection timer, a MAC entity reaching a configured maximum PRACH preamble transmission threshold, an RLC entity reaching a configured maximum retransmission threshold, or integrity check failure while SDT procedure is ongoing, or expiry of SDT-specific timing alignment timer or configuredGrantTimer while SDT procedure is ongoing over CG and the UE has not received a response from the network after the initial PUSCH transmission. Upon unsuccessful completion of the SDT procedure, the UE transitions to RRC_IDLE. For SDT, network should not send RRCReject in response to RRCResumeRequest/RRCResumeRequest1 if DL data over any radio bearer configured for SDT is transmitted. The initial PUSCH transmission during the SDT procedure includes at least the CCCH message. When using CG resources for initial SDT transmission, the UE can perform autonomous retransmission of the initial transmission if the UE does not receive confirmation from the network (dynamic UL grant or DL assignment) before a configured timer expires as specified in clause 5.4.1 of TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [6]. After the initial PUSCH transmission, subsequent transmissions are handled differently depending on the type of resource used to initiate the SDT procedure: - When using CG resources, the network can schedule subsequent UL transmissions using dynamic grants or they can take place on the following CG resource occasions. The DL transmissions are scheduled using dynamic assignments. The UE can initiate subsequent UL transmission only after reception of confirmation (dynamic UL grant or DL assignment) for the initial PUSCH transmission from the network. For subsequent UL transmission, the UE cannot initiate re-transmission over a CG resource. - When using RACH resources, the network can schedule subsequent UL and DL transmissions using dynamic UL grants and DL assignments, respectively, after the completion of the RA procedure. When SDT procedure is initiated, AS security is applied for all the radio bearers enabled for SDT as specified in clause 5.3.13.3 of TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [12]. While the SDT procedure is ongoing, if data appears in a buffer of any radio bearer not enabled for SDT, the UE initiates a transmission of a non-SDT data arrival indication using UEAssistanceInformation message to the network and, if available, includes the resume cause. SDT procedure over CG resources can only be initiated with valid UL timing alignment. The UL timing alignment is maintained by the UE based on a SDT-specific timing alignment timer configured by the network via dedicated signalling and, for initial CG-SDT transmission, also by DL RSRP of configured number of highest ranked SSBs which are above a configured RSRP threshold. Upon expiry of the SDT-specific timing alignment timer, the CG resources are released while maintaining the CG resource configuration. Logical channel restrictions configured by the network while in RRC_CONNECTED state and/or in RRCRelease message for radio bearers enabled for SDT, if any, are applied by the UE during SDT procedure. The network may configure UE to apply ROHC continuity for SDT either when the UE initiates SDT in the PCell of the UE when the RRCRelease with suspend indication was received or when the UE initiates SDT in a cell of its RNA. For SDT procedure over CG resources, the network may configure maximum time duration until the next valid CG occasion for initial CG-SDT transmission based on which the UE decides whether SDT procedure over CG resources can be initiated. The maximum time duration is configured per logical channel for MO-SDT and per UE for MT-SDT. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 18 |
5,862 | 5.3.1.2.6 IPv6 Prefix Delegation via DHCPv6 | Optionally a single network prefix shorter than the default /64 prefix may be assigned to a PDN connection. In this case, the /64 default prefix used for IPv6 stateless autoconfiguration will be allocated from this network prefix; the remaining address space from the network prefix can be delegated to the PDN connection using prefix delegation after the default bearer establishment and IPv6 prefix allocation via IPv6 stateless address autoconfiguration as defined in clause 5.3.1.2.2. When PLMN based parameter configuration is used, the PDN GW provides the requested IPv6 prefix from a locally provisioned pool. When external PDN based IPv6 prefix allocation is used, the PDN GW obtains the prefix from the external PDN. NOTE: Allocation of IPv6 prefixes with flexible prefix length can leverage e.g. local configuration on the PDN GW or interaction with the AAA server. The address space provided is maintained as an IPv6 address space pool available to the PDN connection for DHCPv6 IPv6 prefix requests with the exclusion of the IPv6 prefix that is allocated to the PDN connection during default bearer establishment as defined in clause 5.3.1.2.2. The total IPv6 address space available for the PDN connection (UE default bearer prefix and UE PDN connection IPv6 address space pool) shall be possible to aggregate into one IPv6 prefix that will represent all IPv6 addresses that the UE may use. If the UE had indicated that it supports prefix exclusion and the prefix to be delegated to the UE includes the /64 prefix that was allocated to the PDN Connection, the PDN GW shall utilise the prefix exclusion feature as specified for DHCPv6 Prefix Delegation in IETF RFC 6603 [70]. The UE uses DHCPv6 to request additional IPv6 prefixes (i.e. prefixes in addition to the default prefix) from the PDN GW after completing stateless IPv6 address autoconfiguration procedures. The UE acts as a "Requesting Router" as described in RFC 8415 [94] and inserts one or more IA_PD option(s) into a DHCPv6 Solicit message sent from the UE to the PDN GW. The PDN GW acts as the DHCP server and fulfils the role of a "Delegating Router" according to RFC 8415 [94]. The UE optionally includes the RAPID_COMMIT option in the DHCPv6 Solicit message to trigger two-message DHCPv6 procedure instead of the four-message DHCPv6 procedure. The UE shall include OPTION_PD_EXCLUDE option code in an OPTION_ORO option to indicate support for prefix exclusion. In response to the DHCPv6 Solicit message, the UE receives a DHCPv6 Reply message with one or more IA_PD prefix(es) for every IA_PD option that it sent in the DHCPv6 Solicit message. The PDN GW delegates a prefix excluding the default prefix with help of OPTION_PD_EXCLUDE. Prefix exclusion procedures shall follow IETF RFC 6603 [70]. | 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.1.2.6 |
5,863 | – PUCCH-ConfigCommon | The IE PUCCH-ConfigCommon is used to configure the cell specific PUCCH parameters. PUCCH-ConfigCommon information element -- ASN1START -- TAG-PUCCH-CONFIGCOMMON-START PUCCH-ConfigCommon ::= SEQUENCE { pucch-ResourceCommon INTEGER (0..15) OPTIONAL, -- Cond InitialBWP-Only pucch-GroupHopping ENUMERATED { neither, enable, disable }, hoppingId INTEGER (0..1023) OPTIONAL, -- Need R p0-nominal INTEGER (-202..24) OPTIONAL, -- Need R ..., [[ nrofPRBs INTEGER (1..16) OPTIONAL, -- Need R intra-SlotFH-r17 ENUMERATED {fromLowerEdge, fromUpperEdge} OPTIONAL, -- Cond InitialBWP-RedCapOnly pucch-ResourceCommonRedCap-r17 INTEGER (0..15) OPTIONAL, -- Cond InitialBWP-RedCap additionalPRBOffset-r17 ENUMERATED {n2, n3, n4, n6, n8, n9, n10, n12} OPTIONAL -- Cond InitialBWP-RedCapOnly ]] } -- TAG-PUCCH-CONFIGCOMMON-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
5,864 | 4.16.7.2 Procedures for future background data transfer | Figure 4.16.7.2-1: Negotiation for future background data transfer 1. The AF invokes the Nnef_BDTPNegotiation_Create (ASP Identifier, Number of UEs, Volume per UE, Desired time window and optionally External Group Identifier, Network Area Information, Request for notification, MAC address or IP 3-tuple of Application server). The Request for notification is an indication that BDT warning notification should be sent to the AF. 2a. Based on an AF request, the NEF requests to translate the External Group Identifier into the Internal Group Identifier using Nudm_SDM_Get (Group Identifier Translation, External Group Identifier). 2b. The NEF invokes the Npcf_BDTPolicyControl_Create (ASP Identifier, Number of UEs, Volume per UE, Desired time window and optionally Internal Group Identifier, the Network Area Information, Request for notification, MAC address or IP 3-tuple of Application server) with the H-PCF to authorize the creation of the policy regarding the background data transfer. If the PCF was provided with Request for notification, then PCF may send BDT warning notification to the AF as described in clause 4.16.7.3. 3 The H-PCF may request from the UDR the stored Background Data Transfer policies for all the ASPs using Nudr_DM_Query (Policy Data, Background Data Transfer) service operation. NOTE 1: If only one PCF is deployed in the PLMN, the Background Data Transfer policy can be locally stored and no interaction with UDR is required. 4. The UDR provides all the stored Background Data Transfer policies and corresponding related information (i.e. volume of data to be transferred per UE, the expected amount of UEs) to the H-PCF. 5. The H-PCF determines, based on information provided by the AF and other available information one or more Background Data Transfer policies. The PCF may interact with the NWDAF and request the Network Performance analytics information for the Desired time window and the Network Area Information as defined in TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [50]. NOTE 2: When the External Group Identifier was provided and the Network Area Information was not provided by the AF at step 1, the NWDAF derives the Network Area Information from the Internal Group ID as defined in clause 6.6 of TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [50]. NOTE 3: The maximum aggregated bitrate is not enforced in the network. 6. The H-PCF send the acknowledge message to the NEF with the acceptable Background Data T Transfer policies and a Background Data Transfer Reference ID. 7. The NEF sends a Nnef_BDTPNegotiation_Create response to the AF to provide one or more background data transfer policies and the Background Data Transfer Reference ID to the AF. The AF stores the Background Data Transfer Reference ID for the future interaction with the PCF. If the NEF received only one background data transfer policy from the PCF, steps 8-11 are not executed and the flow proceeds to step 12. Otherwise, the flow proceeds to step 8. NOTE 4: If the NEF receives only one Background Data T Transfer policy, the AF is not required to confirm. 8. The AF invokes the Nnef_BDTPNegotiation_Update service to provide the NEF with Background Data Transfer Reference ID and the selected background data transfer policy. 9. The NEF invokes the Npcf_BDTPolicyControl_Update service to provide the H-PCF with the selected background data transfer policy and the associated Background Data Transfer Reference ID. 10. The H-PCF sends the acknowledge message to the NEF. 11. The NEF sends the acknowledge message to the AF. 12. The H-PCF stores the Background Data Transfer Reference ID together with the new Background Data T Transfer policy, the corresponding related information (i.e. volume of data to be transferred per UE, the expected amount of UEs), optionally MAC address or IP 3-tuple of Application server the information of request for notification, together with the relevant information received from the AF (as defined in clause 6.1.2.4 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]) in the UDR by invoking Nudr_DM_Update (BDT Reference id, Policy Data, Background Data Transfer). This step is not executed, when the PCF decides to locally store the Background Data Transfer policy. 13. The UDR sends a response to the H-PCF as its acknowledgement. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.16.7.2 |
5,865 | 7.9.1 Delete PDN Connection Set Request | This message may be sent on the S2a, S2b, S5, S8, or S11 interfaces as specified in 3GPP TS 23.007[ Restoration procedures ] [17]. Table 7.9.1-1: Information Elements in a Delete PDN Connection Set Request TEID of 0 shall be used for the Delete PDN Connection Set Request. Only one type of FQ-CSID shall be included in each Delete PDN Connection Set Request, A mix of different types, such as SGW-FQ-CSID and PGW-FQ-CSID shall not be used. A combined node, such as a collocated PGW/SGW, shall send separate Delete PDN Connection Set Request for the PGW role and one for the SGW role if a partial fault impacts more than one role. | 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.9.1 |
5,866 | 6.2.4A UE maximum output power with additional requirements for CA | Additional ACLR, spectrum emission and spurious emission requirements for carrier aggregation can be signalled by the network to indicate that the UE shall also meet additional requirements in a specific deployment scenario. To meet these additional requirements, Additional Maximum Power Reduction (A-MPR) is allowed for the CA Power Class as specified in Table 6.2.2A-1. If for intra-band carrier aggregation the UE is configured for transmissions on a single serving cell, then subclauses 6.2.3 and 6.2 4 apply with the Network Signaling value indicated by the field additionalSpectrumEmission. For intra-band contiguous aggregation with the UE configured for transmissions on two serving cells, the maximum output power reduction specified in Table 6.2.4A-1 is allowed for all serving cells of the applicable uplink CA configurations according to the CA network signalling value indicated by the field additionalSpectrumEmissionSCell-r10. Then clause 6.2.3A does not apply, i.e. the carrier aggregation MPR = 0dB, unless the value indicated is CA_NS_09 or CA_NS_31. For uplink 64 QAM and 256 QAM, the applied maximum output power reduction is obtained by taking the maximum value of MPR requirements specified in Table 6.2.3A-1 and A-MPR requirements specified in Table 6.2.4A-1. Table 6.2.4A-1: Additional Maximum Power Reduction (A-MPR) for intra-band contiguous CA If for intra-band non-contigous carrier aggregation the UE is configured for transmissions on a single serving cell, then subclauses 6.2.3 and 6.2 4 apply with the Network Signaling value indicated by the field additionalSpectrumEmission. For intra-band non-contiguous carrier aggregation with the UE configured for transmissions on two serving cells, the maximum output power reduction specified in Table 6.2.4A-2 is allowed for all serving cells of the applicable uplink CA configurations according to the CA network signalling value indicated by the field additionalSpectrumEmissionSCell-r10. MPR as specified in subclause 6.2.3A is not allowed in addition, unless A-MPR is N/A. Table 6.2.4A-2: Additional Maximum Power Reduction (A-MPR) for intra-band non-contiguous CA If for inter-band carrier aggregation the UE is configured for transmissions on a single serving cell, then subclauses 6.2.3 and 6.2 4 apply with the Network Signaling value indicated by the field additionalSpectrumEmission. For inter-band carrier aggregation with the UE configured for transmissions on two serving cells the maximum output power reduction specified in Table 6.2.4-1 is allowed for each serving cell of the applicable uplink CA configuration according to the Network Signaling value indicated by the field additionalSprectrumEmission for the PCC and the CA network signalling value indicated by the field additionalSpectrumEmissionSCell-r10 for the SCC. The value of additionalSpectrumEmissionSCell-r10 is equal to that of additionalSprectrumEmission configured on the SCC. MPR as specified in subclause 6.2.3A is allowed in addition. For PUCCH and SRS transmissions, the allowed A-MPR is according to that specified for PUSCH QPSK modulation for the corresponding transmission bandwidth. For intra-band carrier aggregation, the A-MPR shall be evaluated per Teval period as specified in table 6.2.4A-3 and given by the maximum value taken over the transmission(s) on all component carriers within that period; the maximum A-MPR over TREF is then applied for the entire TREF. Table 6.2.4A-3: A-MPR evaluation Teval period For combinations of intra-band and inter-band carrier aggregation with the UE configured for transmission on three serving cells (up to two contiguously aggregated carriers per band), the maximum output power reduction is specified as follows. For the band supporting one serving cell the maximum output power reduction specified in Table 6.2.4-1 is allowed according to the Network Signaling value indicated by the field additionalSprectrumEmission for the PCC and the CA network signalling value indicated by the field additionalSpectrumEmissionSCell-r10 for the SCC. The value of additionalSpectrumEmissionSCell-r10 is equal to that of additionalSprectrumEmission configured on the SCC. MPR as specified in subclause 6.2.3A is allowed in addition. For the band supporting intra-band contiguous aggregation with the UE configured for transmissions on two serving cells, the maximum output power reduction specified in Table 6.2.4A-1 is allowed for all serving cells of the applicable uplink CA configurations according to the CA network signalling value indicated by the field additionalSpectrumEmissionSCell-r10. Then clause 6.2.3A does not apply, i.e. the carrier aggregation MPR = 0dB, unless the value indicated is CA_NS_31. For uplink 64 QAM and 256 QAM, the applied maximum output power reduction is obtained by taking the maximum value of MPR requirements specified in Table 6.2.3A-1 and A-MPR requirements specified in Table 6.2.4A-1. For the UE maximum output power modified by A-MPR specified in table 6.2.4A-1, the power limits specified in subclause 6.2.5A apply. | 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.4A |
5,867 | 8.21.8 Extended Macro eNodeB ID field | The coding of Extended Macro eNodeB ID is depicted in Figure 8.21.8-1. Only zero or one Extended Macro eNodeB ID or Macro eNodeB ID field shall be present in ULI IE. Figure 8.21.8-1: Extended Macro eNodeB ID field The Extended Macro eNodeB ID consists of 21 bits. The coding of the Extended Macro eNodeB ID is the responsibility of each administration. Coding using full hexadecimal representation (binary, not ASCII encoding) shall be used. If the SMeNB flag is not set the Extended Macro eNodeB ID field contains a Long Macro eNodeB ID with a length of 21 Bits. Bit 5 of Octet g+3 is the most significant bit and bit 1 of g+5 is the least significant bit. If the SMeNB flag is set the Extended Macro eNodeB ID field contains a Short Macro eNodeB ID with a length of 18 Bits. Bits 3 to 5 of Octet g+3 shall be set to 0 by the sender and shall be ignored by the receiver. Bit 2 of Octet g+3 is the most significant bit and bit 1 of Octet g+5 is the least significant bit. NOTE: Homogenous support of the Extended Macro eNodeB ID IE is expected in a PLMN. | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 8.21.8 |
5,868 | 4.4.2.1.1 Establishment of 5G NAS security context | The security parameters for authentication, integrity protection and ciphering are tied together in a 5G NAS security context and identified by a key set identifier (ngKSI). The relationship between the security parameters is defined in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]. Before security can be activated, the AMF and the UE need to establish a 5G NAS security context. Usually, the 5G NAS security context is created as the result of a primary authentication and key agreement procedure between the AMF and the UE. A new 5G NAS security context may also be created during an N1 mode to N1 mode handover. Alternatively, during inter-system change from S1 mode to N1 mode, the AMF not supporting interworking without N26 and the UE operating in single-registration mode may derive a mapped 5G NAS security context from an EPS security context that has been established while the UE was in S1 mode. The 5G NAS security context is taken into use by the UE and the AMF, when the AMF initiates a security mode control procedure, during an N1 mode to N1 mode handover, or during the inter-system change procedure from S1 mode to N1 mode. The 5G NAS security context which has been taken into use by the network most recently is called current 5G NAS security context. This current 5G NAS security context can be of type native or mapped, i.e. originating from a native 5G NAS security context or mapped 5G NAS security context. The key set identifier ngKSI is assigned by the AMF either during the primary authentication and key agreement procedure or, for the mapped 5G NAS security context, during the inter-system change. The ngKSI consists of a value and a type of security context parameter indicating whether a 5G NAS security context is a native 5G NAS security context or a mapped 5G NAS security context. When the 5G NAS security context is a native 5G NAS security context, the ngKSI has the value of KSIAMF, and when the current 5G NAS security context is of type mapped, the ngKSI has the value of KSIASME. The 5G NAS security context which is indicated by an ngKSI can be taken into use to establish the secure exchange of NAS messages when a new N1 NAS signalling connection is established without executing a new primary authentication and key agreement procedure (see subclause 5.4.1) or when the AMF initiates a security mode control procedure. For this purpose, the initial NAS messages (i.e. REGISTRATION REQUEST, DEREGISTRATION REQUEST, SERVICE REQUEST and CONTROL PLANE SERVICE REQUEST) and the SECURITY MODE COMMAND message contain an ngKSI in the ngKSI IE indicating the current 5G NAS security context used to integrity protect the NAS message. In the present document, when the UE is required to delete an ngKSI, the UE shall set the ngKSI to the value "no key is available" and consider also the associated keys KAMF or K'AMF, 5G NAS ciphering key and 5G NAS integrity key invalid (i.e. the 5G NAS security context associated with the ngKSI as no longer valid). In the initial registration procedure, when the key KAUSF, is invalid, the UE shall delete the ngKSI. NOTE: In some specifications the term ciphering key sequence number might be used instead of the term key set identifier (KSI). As described in subclause 4.8 in order to interwork with E-UTRAN connected to EPC, the UE supporting both S1 mode and N1 mode can operate in either single-registration mode or dual-registration mode. A UE operating in dual-registration mode shall independently maintain and use both EPS security context (see 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15]) and 5G NAS security context. When the UE operating in dual-registration mode performs an EPS attach procedure, it shall take into use an EPS security context and follow the handling of this security context as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15]. However, when the UE operating in dual-registration mode performs an initial registration procedure, it shall take into use a 5G NAS security context and follow the handling of this security context as described in the present specification. The UE and the AMF need to be able to maintain two 5G NAS security contexts simultaneously, i.e. a current 5G NAS security context and a non-current 5G NAS security context, since: a) after a 5G re-authentication, the UE and the AMF can have both a current 5G NAS security context and a non-current 5G NAS security context which has not yet been taken into use (i.e. a partial native 5G NAS security context); and b) after an inter-system change from S1 mode to N1 mode, the UE and the AMF can have both a mapped 5G NAS security context, which is the current 5G NAS security context, and a non-current native 5G NAS security context that was created during a previous access in N1 mode. The number of 5G NAS security contexts that need to be maintained simultaneously by the UE and the AMF is limited by the following requirements: a) after a successful 5G (re-)authentication, which creates a new partial native 5G NAS security context, the AMF and the UE shall delete the non-current 5G NAS security context, if any; b) when a partial native 5G NAS security context is taken into use through a security mode control procedure, the AMF shall delete the previously current 5G NAS security context. If the UE does not support multiple records of NAS security context storage for multiple registration (see 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [22]), the UE shall delete the previously current 5G NAS security context. If the UE supports multiple records of NAS security context storage for multiple registration, the UE shall: 1) replace the previously current 5G NAS security context stored in the first 5G security context of that access (see 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [22]) with the new 5G security context (taken into use through a security mode control procedure), when the UE activates the new 5G security context for the same PLMN and access; or 2) store the previously current 5G NAS security context in the second 5G security context of that access (see 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [22]) and store the new 5G security context (taken into use through a security mode control procedure) in the first 5G security context, when the UE activates the new 5G security context for a different PLMN over that access but the previously current 5G NAS security context is associated with the 5G-GUTI of the other access; c) when the AMF and the UE create a 5G NAS security context using "null integrity protection algorithm" and "null ciphering algorithm" during an initial registration procedure for emergency services, or a registration procedure for mobility and periodic registration update for a UE that has an emergency PDU session (see subclause 5.4.2.2), the AMF and the UE shall delete the previous current 5G NAS security context. The UE shall not update the USIM and non-volatile ME memory with the current 5G NAS security context and shall delete the current 5G NAS security context when the UE is deregistered from emergency services (e.g. before registering for normal service); d) when a new mapped 5G NAS security context or 5G NAS security context created using "null integrity protection algorithm" and "null ciphering algorithm" is taken into use during the inter-system change from S1 mode to N1 mode, the AMF and the UE shall not delete the previously current native 5G NAS security context, if any. Instead, the previously current native 5G NAS security context shall become a non-current native 5G NAS security context, and the AMF and the UE shall delete any partial native 5G NAS security context; If no previously current native 5G NAS security context exists, the AMF and the UE shall not delete the partial native 5G NAS security context, if any; e) when the AMF and the UE derive a new mapped 5G NAS security context during inter-system change from S1 mode to N1 mode, the AMF and the UE shall delete any existing current mapped 5G NAS security context; f) when a non-current full native 5G NAS security context is taken into use by a security mode control procedure, then the AMF and the UE shall delete the previously current mapped 5G NAS security context; g) when the UE or the AMF moves from 5GMM-REGISTERED to 5GMM-DEREGISTERED state, if the current 5G NAS security context is a mapped 5G NAS security context and a non-current full native 5G NAS security context exists, then the non-current 5G NAS security context shall become the current 5G NAS security context. Furthermore, the UE and the AMF shall delete any mapped 5G NAS security context or partial native 5G NAS security context. h) when the UE operating in single-registration mode in a network supporting N26 interface performs an inter-system change from N1 mode to S1 mode: 1) if the UE has a mapped 5G NAS security context and the inter-system change is performed in: i) 5GMM-IDLE mode, the UE shall delete the mapped 5G NAS security context after the successful completion of the tracking area update procedure or attach procedure (see 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15]); or ii) 5GMM-CONNECTED mode, the UE shall delete the mapped 5G NAS security context after the completion of the inter-system change. After deletion of the mapped 5G NAS security context, if the UE has a non-current full native 5G NAS security context, then the non-current full native 5G NAS security context shall become the current full native 5G NAS security context; and i) when the UE operating in single-registration mode in a network supporting N26 interface performs an inter-system change from S1 mode to N1 mode in 5GMM-IDLE mode, if the UE has a non-current full native 5G NAS security context, then the UE shall make the non-current full native 5G NAS security context as the current native 5G NAS security context. The UE shall delete the mapped 5G NAS security context, if any. | 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.4.2.1.1 |
5,869 | 6.4.1.2 UE-requested PDU session establishment procedure initiation | In order to initiate the UE-requested PDU session establishment procedure, the UE shall create a PDU SESSION ESTABLISHMENT REQUEST message. NOTE 0: When IMS voice is available over either 3GPP access or non-3GPP access, the "voice centric" UE in 5GMM-REGISTERED state will receive a request from upper layers to establish the PDU session for IMS signalling, if the conditions for performing an initial registration with IMS indicated in 3GPP TS 24.229[ IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 ] [14] subclause U.3.1.2 are satisfied. If the UE requests to establish a new PDU session, the UE shall allocate a PDU session ID which is not currently being used by another PDU session over either 3GPP access or non-3GPP access. If the N5CW device supporting 3GPP access requests to establish a new PDU session via 3GPP access, the N5CW device supporting 3GPP access shall refrain from allocating "PDU session identity value 15". If the TWIF acting on behalf of the N5CW device requests to establish a new PDU session, the TWIF acting on behalf of the N5CW device shall allocate the "PDU session identity value 15". The UE shall allocate a PTI value currently not used and shall set the PTI IE of the PDU SESSION ESTABLISHMENT REQUEST message to the allocated PTI value. If the UE is registered for emergency services over the current access, the UE shall not request establishing a non-emergency PDU session over the current access. If the UE is registered for emergency services over the current access it shall not request establishing an emergency PDU session over the non-current access except if the request is for transferring the emergency PDU session to the non-current access. Before transferring an emergency PDU session from non-3GPP access to 3GPP access, or before transferring a PDN connection for emergency bearer services from untrusted non-3GPP access connected to EPC to 3GPP access, the UE shall check whether emergency services are supported in the NG-RAN cell (either an NR cell or an E-UTRA cell) on which the UE is camping. NOTE 1: Transfer of an existing emergency PDU session or PDN connection for emergency bearer services between 3GPP access and non-3GPP access is needed e.g. if the UE determines that the current access is no longer available. If the UE requests to establish a new emergency PDU session, the UE shall include the PDU session type IE in the PDU SESSION ESTABLISHMENT REQUEST message and shall set the IE to the IP version capability as specified in subclause 6.2.4.2. If the UE requests to establish a new non-emergency PDU session with a DN, the UE shall include the PDU session type IE in the PDU SESSION ESTABLISHMENT REQUEST message and shall set the IE to one of the following values: "IPv4", "IPv6", "IPv4v6", "Ethernet" or "Unstructured" based on the URSP rules or based on UE local configuration (see 3GPP TS 24.526[ User Equipment (UE) policies for 5G System (5GS); Stage 3 ] [19]) and based on the IP version capability as specified in subclause 6.2.4.2. NOTE 2: When the UE initiates the UE-requested PDU session establishment procedure to transfer an existing non-IP PDN connection in the EPS to the 5GS, the UE can use locally available information associated with the PDN connection to select the PDU session type between "Ethernet" and "Unstructured". If the UE requests to establish a new non-emergency PDU session with a DN and the UE requests an SSC mode, the UE shall set the SSC mode IE of the PDU SESSION ESTABLISHMENT REQUEST message to the SSC mode. If the UE requests to establish a PDU session of "IPv4", "IPv6" or "IPv4v6" PDU session type, the UE shall either omit the SSC mode IE or set the SSC mode IE to "SSC mode 1", "SSC mode 2", or "SSC mode 3". If the UE requests to establish a PDU session of "Ethernet" or "Unstructured" PDU session type, the UE shall either omit the SSC mode IE or set the SSC mode IE to "SSC mode 1" or "SSC mode 2". If the UE requests transfer of an existing PDN connection in the EPS to the 5GS or the UE requests transfer of an existing PDN connection in an untrusted non-3GPP access connected to the EPC to the 5GS, the UE shall set the SSC mode IE to "SSC mode 1". If the UE requests to establish a new emergency PDU session, the UE shall set the SSC mode IE of the PDU SESSION ESTABLISHMENT REQUEST message to "SSC mode 1". A UE supporting PDU connectivity service shall support SSC mode 1 and may support SSC mode 2 and SSC mode 3 as specified in 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8]. If the UE requests to establish a new non-emergency PDU session with a DN, the UE may include the SM PDU DN request container IE with a DN-specific identity of the UE complying with network access identifier (NAI) format as specified in IETF RFC 7542 [37]. NOTE 3: The UE can avoid including both the SM PDU DN request container IE and the Extended protocol configuration options IE with PAP/CHAP protocol identifiers in the PDU SESSION ESTABLISHMENT REQUEST message. The way to achieve this is implementation dependent. If the UE requests to: a) establish a new PDU session; b) perform handover of an existing PDU session from non-3GPP access to 3GPP access; c) transfer an existing PDN connection in the EPS to the 5GS according to subclause 4.8.2.3.1; d) transfer an existing PDN connection in untrusted non-3GPP access connected to the EPC to the 5GS; or e) establish user plane resources over 3GPP access of an MA PDU session established over non-3GPP access only; and the UE at the same time intends to join one or more multicast MBS sessions that is associated to the PDU session, the UE should include the Requested MBS container IE in the PDU SESSION ESTABLISHMENT REQUEST message. In that case, the UE shall set the MBS operation to "Join multicast MBS session" and include the multicast MBS session information(s) and shall set the Type of multicast MBS session ID for each of the multicast MBS session information to either "Temporary Mobile Group Identity (TMGI)" or "Source specific IP multicast address" depending on the type of the multicast MBS session ID available in the UE. Then the remaining values of each of the multicast MBS session information shall be set as following: a) if the Type of multicast MBS session ID is set to "Temporary Mobile Group Identity (TMGI)", the UE shall set the multicast MBS session ID to the TMGI; or b) if the Type of multicast MBS session ID is set to "Source specific IP multicast address for IPv4" or " Source specific IP multicast address for IPv6", the UE shall set the Source IP address information and the Destination IP address information to the corresponding values. The UE should not request to join a multicast MBS session for local MBS service if neither current TAI nor CGI of the current cell is part of the MBS service area(s) of the multicast MBS session, if the UE has valid information of the MBS service area(s) of the multicast MBS session. NOTE 4: The UE obtains the details of the MBS session ID(s) e.g., TMGI, Source IP address information and Destination IP address information as a pre-configuration in the UE or during the MBS service announcement, which is out of scope of this specification. Pre-configuration can be provided in one or more of the following ways: a) in a UE implementation-specific way (e.g. factory configuration); b) in the USIM (see EF5MBSUECONFIG file in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [22]); or c) in the UE pre-configuration MO for MBS (see 3GPP TS 24.575[ 5G System; Multicast/Broadcast UE pre-configuration Management Object (MO) ] [65). The UE should set the RQoS bit to "Reflective QoS supported" in the 5GSM capability IE of the PDU SESSION ESTABLISHMENT REQUEST message if the UE supports reflective QoS and: a) the UE requests to establish a new PDU session of "IPv4", "IPv6", "IPv4v6" or "Ethernet" PDU session type; b) the UE requests to transfer an existing PDN connection in the EPS of "IPv4", "IPv6", "IPv4v6" or "Ethernet" PDN type or of "Non-IP" PDN type mapping to "Ethernet" PDU session type, to the 5GS; or c) the UE requests to transfer an existing PDN connection in an untrusted non-3GPP access connected to the EPC of "IPv4", "IPv6" or "IPv4v6" PDN type to the 5GS. NOTE 5: The determination to not request the usage of reflective QoS by the UE for a PDU session is implementation dependent. The UE shall indicate the maximum number of packet filters that can be supported for the PDU session in the Maximum number of supported packet filters IE of the PDU SESSION ESTABLISHMENT REQUEST message if: a) the UE requests to establish a new PDU session of "IPv4", "IPv6", "IPv4v6", or "Ethernet" PDU session type, and the UE can support more than 16 packet filters for this PDU session; b) the UE requests to transfer an existing PDN connection in the EPS of "IPv4", "IPv6", "IPv4v6", or "Ethernet" PDN type or of "Non-IP" PDN type mapping to "Ethernet" PDU session type, to the 5GS and the UE can support more than 16 packet filters for this PDU session; or c) the UE requests to transfer an existing PDN connection in an untrusted non-3GPP access connected to the EPC of "IPv4", "IPv6" or "IPv4v6" PDN type to the 5GS and the UE can support more than 16 packet filters for this PDU session. The UE shall include the Integrity protection maximum data rate IE in the PDU SESSION ESTABLISHMENT REQUEST message to indicate the maximum data rate per UE for user-plane integrity protection supported by the UE for uplink and the maximum data rate per UE for user-plane integrity protection supported by the UE for downlink. The UE shall set the MH6-PDU bit to "Multi-homed IPv6 PDU session supported" in the 5GSM capability IE of the PDU SESSION ESTABLISHMENT REQUEST message if the UE supports multi-homed IPv6 PDU session and: a) the UE requests to establish a new PDU session of "IPv6" or "IPv4v6" PDU session type; or. b) the UE requests to transfer an existing PDN connection of "IPv6" or "IPv4v6" PDN type in the EPS or in an untrusted non-3GPP access connected to the EPC to the 5GS. The UE shall set the EPT-S1 bit to "Ethernet PDN type in S1 mode supported" in the 5GSM capability IE of the PDU SESSION ESTABLISHMENT REQUEST message if the UE supports Ethernet PDN type in S1 mode and requests "Ethernet" PDU session type. If the UE requests to establish a new PDU session as an always-on PDU session (e.g. because the PDU session is for time synchronization or TSC), the UE shall include the Always-on PDU session requested IE and set the value of the IE to "Always-on PDU session requested" in the PDU SESSION ESTABLISHMENT REQUEST message. NOTE 6: Determining whether a PDU session is for time synchronization or TSC is UE implementation dependent. If the UE has an emergency PDU session, the UE shall not perform the UE-requested PDU session establishment procedure to establish another emergency PDU session. The UE may perform the UE-requested PDU session establishment procedure to transfer an existing emergency PDU session or an existing PDN connection for emergency services. If: a) the UE requests to perform handover of an existing PDU session between 3GPP access and non-3GPP access; b) the UE requests to perform transfer an existing PDN connection in the EPS to the 5GS; or c) the UE requests to perform transfer an existing PDN connection in an untrusted non-3GPP access connected to the EPC to the 5GS; the UE shall: a) set the PDU session ID in the PDU SESSION ESTABLISHMENT REQUEST message and in the UL NAS TRANSPORT message to the stored PDU session ID corresponding to the PDN connection; and b) set the S-NSSAI in the UL NAS TRANSPORT message to the stored S-NSSAI associated with the PDU session ID of a non-emergency PDU session. The UE shall not request to perform handover of an existing non-emergency PDU session: 1) between 3GPP access and non-3GPP access if the S-NSSAI is not included in the allowed NSSAI for the target access; or 2) from non-3GPP access to 3GPP access: i) if the S-NSSAI is not in the partially allowed NSSAI for 3GPP access; or ii) if the S-NSSAI is in the partially allowed NSSAI for 3GPP access but the TAI where the UE is currently camped on is not in the list of TAs for which the S-NSSAI is supported. If the N5CW device supporting 3GPP access requests to perform handover of an existing PDU session from non-3GPP access to 3GPP access, the N5CW device supporting 3GPP access shall set the PDU session ID in the PDU SESSION ESTABLISHMENT REQUEST message and in the UL NAS TRANSPORT message to "PDU session identity value 15". If the UE is registered to a network which supports ATSSS and the UE requests to establish a new PDU session the UE may allow the network to upgrade the requested PDU session to an MA PDU session. In order to allow the network to upgrade the requested PDU session to an MA PDU session, the UE shall set "MA PDU session network upgrade is allowed" in the MA PDU session information IE and shall set the request type to "initial request" in the UL NAS TRANSPORT message. If the UE is registered to a network which does not support ATSSS, the UE shall not perform the procedure to allow the network to upgrade the requested PDU session to an MA PDU session. If the UE is registered to a network which supports ATSSS, the UE may request to establish an MA PDU session. If the UE requests to establish an MA PDU session, the UE shall set the request type to "MA PDU request" in the UL NAS TRANSPORT message. If the UE is registered to a network which does not support ATSSS, the UE shall not request to establish an MA PDU session. When the UE is registered over both 3GPP access and non-3GPP access in the same PLMN and the UE requests to establish a new MA PDU session, the UE may provide an S-NSSAI in the UL NAS TRANSPORT message only if the S-NSSAI is included in the allowed NSSAIs of both accesses. NOTE 7: If the UE requested DNN corresponds to an LADN DNN, the AMF does not forward the MA PDU session information IE to the SMF but sends the message back to the UE to inform of the unhandled request (see subclause 5.4.5.2.5). If the UE is registered to a network which supports ATSSS and the UE has already an MA PDU session established over one access, the UE may perform the UE-requested PDU session establishment procedure to establish user-plane resources over the other access for the MA PDU session as specified in subclause 4.22 of 3GPP TS 23.502[ Procedures for the 5G System (5GS) ] [9] and the S-NSSAI associated with the MA PDU session is included in the allowed NSSAI of the other access. If the UE establishes user-plane resources over the other access for the MA PDU session, the UE shall: a) set the request type to "MA PDU request" in the UL NAS TRANSPORT message; b) set the PDU session ID to the stored PDU session ID corresponding to the established MA PDU session in the PDU SESSION ESTABLISHMENT REQUEST message and in the UL NAS TRANSPORT message; and c) set the S-NSSAI in the UL NAS TRANSPORT message to the stored S-NSSAI associated with the PDU session ID. If the UE requests to establish a new MA PDU session or if the UE requests to establish a new PDU session and the UE allows the network to upgrade the requested PDU session to an MA PDU session: a) if the UE supports ATSSS Low-Layer functionality with any steering mode (i.e., any steering mode allowed for ATSSS Low-Layer functionality) as specified in subclause 5.32.6 of 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8], the UE shall set the ATSSS-ST bits to "ATSSS Low-Layer functionality with any steering mode allowed for ATSSS-LL supported" in the 5GSM capability IE of the PDU SESSION ESTABLISHMENT REQUEST message; NOTE 8: The ATSSS Low-Layer functionality cannot be used together with the redundant steering mode. When the UE indicates that it is capable of supporting the ATSSS Low-Layer functionality with any steering mode, it implies that the UE supports the ATSSS Low-Layer functionality with any steering mode except the redundant steering mode. b) if the UE supports MPTCP functionality with any steering mode and ATSSS-LL functionality with only active-standby steering mode as specified in subclause 5.32.6 of 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8], the UE shall set the ATSSS-ST bits to "MPTCP functionality with any steering mode and ATSSS-LL functionality with only active-standby steering mode supported" in the 5GSM capability IE of the PDU SESSION ESTABLISHMENT REQUEST message; c) if the UE supports MPTCP functionality with any steering mode and ATSSS-LL functionality with any steering mode (i.e., any steering mode allowed for ATSSS-LL functionality) as specified in subclause 5.32.6 of 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8], the UE shall set the ATSSS-ST bits to "MPTCP functionality with any steering mode and ATSSS-LL functionality with any steering mode allowed for ATSSS-LL supported" in the 5GSM capability IE of the PDU SESSION ESTABLISHMENT REQUEST message; d) if a performance measurement function in the UE can perform access performance measurements using the QoS flow of the non-default QoS rule as specified in subclause 5.32.5 of 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8], the UE shall set the APMQF bit to "Access performance measurements per QoS flow supported" in the 5GSM capability IE of the PDU SESSION ESTABLISHMENT REQUEST message; e) if the UE supports MPQUIC functionality with any steering mode and ATSSS-LL functionality with only active-standby steering mode as specified in subclause 5.32.6 of 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8], the UE shall set the ATSSS-ST bits to "MPQUIC functionality with any steering mode and ATSSS-LL functionality with only active-standby steering mode supported" in the 5GSM capability IE of the PDU SESSION ESTABLISHMENT REQUEST message; f) if the UE supports MPQUIC functionality with any steering mode and ATSSS-LL functionality with any steering mode (i.e., any steering mode allowed for ATSSS-LL functionality) as specified in subclause 5.32.6 of 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8], the UE shall set the ATSSS-ST bits to "MPQUIC functionality with any steering mode and ATSSS-LL functionality with any steering mode allowed for ATSSS-LL supported" in the 5GSM capability IE of the PDU SESSION ESTABLISHMENT REQUEST message; g) if the UE supports MPTCP functionality with any steering mode, MPQUIC functionality with any steering mode and ATSSS-LL functionality with only active-standby steering mode as specified in subclause 5.32.6 of 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8], the UE shall set the ATSSS-ST bits to "MPTCP functionality with any steering mode, MPQUIC functionality with any steering mode and ATSSS-LL functionality with only active-standby steering mode supported" in the 5GSM capability IE of the PDU SESSION ESTABLISHMENT REQUEST message; and h) if the UE supports MPTCP functionality with any steering mode, MPQUIC functionality with any steering mode and ATSSS-LL functionality with any steering mode (i.e., any steering mode allowed for ATSSS-LL functionality) as specified in subclause 5.32.6 of 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8], the UE shall set the ATSSS-ST bits to "MPTCP functionality with any steering mode, MPQUIC functionality with any steering mode and ATSSS-LL functionality with any steering mode allowed for ATSSS-LL supported" in the 5GSM capability IE of the PDU SESSION ESTABLISHMENT REQUEST message. Upon receipt of a PDU SESSION ESTABLISHMENT REQUEST message for MA PDU session establishment, the SMF shall check if the 5GSM capability IE in the PDU SESSION ESTABLISHMENT REQUEST message, includes: a) the ATSSS-ST bits set to "MPTCP functionality with any steering mode and ATSSS-LL functionality with only active-standby steering mode supported" and: i) if the DNN configuration allows for the MPTCP functionality with any steering mode and ATSSS-LL functionality with any steering mode (i.e., any steering mode allowed for ATSSS-LL functionality), the SMF shall ensure that the established PDU session has the capability of MPTCP with any steering mode and ATSSS-LL with any steering mode in the downlink and MPTCP with any steering mode and ATSSS-LL with only active-standby steering mode in the uplink; or ii) if the DNN configuration allows for the MPTCP functionality with any steering mode and ATSSS-LL functionality with only active-standby steering mode, the SMF shall ensure that the established PDU session has the capability of MPTCP with any steering mode and ATSSS-LL with only active-standby steering mode in the downlink and the uplink; b) the ATSSS-ST bits set to "MPQUIC functionality with any steering mode and ATSSS-LL functionality with only active-standby steering mode supported" and: i) if the DNN configuration allows for the MPQUIC functionality with any steering mode and ATSSS-LL functionality with any steering mode (i.e., any steering mode allowed for ATSSS-LL functionality), the SMF shall ensure that the established PDU session has the capability of MPQUIC with any steering mode and ATSSS-LL with any steering mode in the downlink and MPQUIC with any steering mode and ATSSS-LL with only active-standby steering mode in the uplink; or ii) if the DNN configuration allows for the MPQUIC functionality with any steering mode and ATSSS-LL functionality with only active-standby steering mode, the SMF shall ensure that the established PDU session has the capability of MPQUIC with any steering mode and ATSSS-LL with only active-standby steering mode in the downlink and the uplink; c) the ATSSS-ST bits set to "MPQUIC functionality with any steering mode and ATSSS-LL functionality with any steering mode allowed for ATSSS-LL supported" and if the DNN configuration allows for the MPQUIC functionality with any steering mode and ATSSS-LL functionality with any steering mode (i.e., any steering mode allowed for ATSSS-LL functionality), the SMF shall ensure that the established PDU session has the capability of MPQUIC with any steering mode and ATSSS-LL with any steering mode in the downlink and the uplink; d) the ATSSS-ST bits set to "ATSSS Low-Layer functionality with any steering mode allowed for ATSSS-LL supported" and if the DNN configuration allows for the ATSSS-LL functionality with any steering mode (i.e., any steering mode allowed for ATSSS-LL functionality), the SMF shall ensure that the established PDU session has the capability of ATSSS-LL with any steering mode in the downlink and the uplink; e) the ATSSS-ST bits set to "MPTCP functionality with any steering mode and ATSSS-LL functionality with any steering mode allowed for ATSSS-LL supported" and if the DNN configuration allows for the MPTCP functionality with any steering mode and ATSSS-LL functionality with any steering mode (i.e., any steering mode allowed for ATSSS-LL functionality), the SMF shall ensure that the established PDU session has the capability of MPTCP with any steering mode and ATSSS-LL with any steering mode in the downlink and the uplink; f) the ATSSS-ST bits set to "MPTCP functionality with any steering mode, MPQUIC functionality with any steering mode and ATSSS-LL functionality with any steering mode allowed for ATSSS-LL supported" and if the DNN configuration allows for the MPTCP functionality with any steering mode, the MPQUIC functionality with any steering mode and ATSSS-LL functionality with any steering mode (i.e., any steering mode allowed for ATSSS-LL functionality), the SMF shall ensure that the established PDU session has the capability of MPTCP with any steering mode, the MPQUIC with any steering mode and ATSSS-LL with any steering mode in the downlink and the uplink; or g) the ATSSS-ST bits set to "MPTCP functionality with any steering mode, MPQUIC functionality with any steering mode and ATSSS-LL functionality with only active-standby mode supported" and i) if the DNN configuration allows for the MPTCP functionality with any steering mode, the MPQUIC functionality with any steering mode and ATSSS-LL functionality with any steering mode (i.e., any steering mode allowed for ATSSS-LL functionality), the SMF shall ensure that the established PDU session has the capability of MPTCP with any steering mode, MPQUIC with any steering mode and ATSSS-LL with any steering mode in the downlink and MPTCP with any steering mode, MPQUIC with steering mode and ATSSS-LL with only active-standby steering mode in the uplink; or ii) if the DNN configuration allows for the MPTCP functionality with any steering mode, the MPQUIC functionality with any steering mode and ATSSS-LL functionality with only active-standby steering mode, the SMF shall ensure that the established PDU session has the capability of MPTCP with any steering mode, MPQUIC with any steering mode and ATSSS-LL with only active-standby steering mode in the downlink and the uplink. If the UE requests to establish a new MA PDU session and the UE supports to establish a PDN connection as the user plane resource of an MA PDU session, the UE shall include the ATSSS request parameter in the Extended protocol configuration options IE of the PDU SESSION ESTABLISHMENT REQUEST message. If the UE is registered to a network which does not support ATSSS and the UE has already an MA PDU session established over one access, the UE shall not attempt to establish user-plane resources for the MA PDU session over the network which does not support ATSSS as specified in subclause 4.22 of 3GPP TS 23.502[ Procedures for the 5G System (5GS) ] [9]. If the UE supports 3GPP PS data off, except for the transfer of a PDU session from non-3GPP access to 3GPP access and except for the establishment of user plane resources on the other access for the MA PDU session, the UE shall include the Extended protocol configuration options IE in the PDU SESSION ESTABLISHMENT REQUEST message and include the 3GPP PS data off UE status. The UE behaves as described in subclause 6.2.10. If the UE supports Reliable Data Service, the UE shall include the Extended protocol configuration options IE in the PDU SESSION ESTABLISHMENT REQUEST message and include the Reliable Data Service request indicator. The UE behaves as described in subclause 6.2.15. If the UE supports DNS over (D)TLS (see 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]), the UE shall include the Extended protocol configuration options IE in the PDU SESSION ESTABLISHMENT REQUEST message and include DNS server security information indicator and optionally, if the UE wishes to indicate which security protocol type(s) are supported by the UE, it may include the DNS server security protocol support. NOTE 9: Support of DNS over (D)TLS is based on the informative requirements as specified in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]. If: a) the PDU session type value of the PDU session type IE is set to "IPv4", "IPv6" or "IPv4v6"; b) the UE indicates "Control plane CIoT 5GS optimization supported" and "IP header compression for control plane CIoT 5GS optimization supported" in the 5GMM capability IE of the REGISTRATION REQUEST message; and c) the network indicates "Control plane CIoT 5GS optimization supported" and "IP header compression for control plane CIoT 5GS optimization supported" in the 5GS network support feature IE of the REGISTRATION ACCEPT message; the UE shall include the IP header compression configuration IE in the PDU SESSION ESTABLISHMENT REQUEST message. If: a) the PDU session type value of the PDU session type IE is set to "Ethernet"; b) the UE indicates "Control plane CIoT 5GS optimization supported" and "Ethernet header compression for control plane CIoT 5GS optimization supported" in the 5GMM capability IE of the REGISTRATION REQUEST message; and c) the network indicates "Control plane CIoT 5GS optimization supported" and "Ethernet header compression for control plane CIoT 5GS optimization supported" in the 5GS network support feature IE of the REGISTRATION ACCEPT message; the UE shall include the Ethernet header compression configuration IE in the PDU SESSION ESTABLISHMENT REQUEST message. If the UE supports transfer of port management information containers, the UE shall: a) set the TPMIC bit to "Transfer of port management information containers supported" in the 5GSM capability IE of the PDU SESSION ESTABLISHMENT REQUEST message; b) if the UE requests to establish a PDU session of "Ethernet" PDU session type, include the DS-TT Ethernet port MAC address IE in the PDU SESSION ESTABLISHMENT REQUEST message and set its contents to the MAC address of the DS-TT Ethernet port used for the PDU session; c) if the UE-DS-TT residence time is available at the UE, include the UE-DS-TT residence time IE and set its contents to the UE-DS-TT residence time; and d) if a Port management information container is provided by the DS-TT, include the Port management information container IE in the PDU SESSION ESTABLISHMENT REQUEST message. NOTE 10: Only SSC mode 1 is supported for a PDU session which is for time synchronization or TSC. If the UE supports secondary DN authentication and authorization over EPC, the UE shall set the SDNAEPC bit to "Secondary DN authentication and authorization over EPC supported" in the 5GSM capability IE of the PDU SESSION ESTABLISHMENT REQUEST message. If the UE supporting S1 mode supports receiving QoS rules with the length of two octets or QoS flow descriptions with the length of two octets via the Extended protocol configuration options IE, the UE shall include the QoS rules with the length of two octets support indicator or the QoS flow descriptions with the length of two octets support indicator, respectively, in the Extended protocol configuration options IE in the PDU SESSION ESTABLISHMENT REQUEST message. If: - the UE is operating in single-registration mode; - the UE supports local IP address in traffic flow aggregate description and TFT filter in S1 mode; and - the PDU session Type requested is different from "Unstructured". the UE shall indicate the support of local address in TFT in S1 mode in the Extended protocol configuration options IE in the PDU SESSION ESTABLISHMENT REQUEST message. If the W-AGF acting on behalf of the FN-RG requests to establish a PDU session of "IPv6" or "IPv4v6" PDU session type, the W-AGF acting on behalf of the FN-RG may include in the PDU SESSION ESTABLISHMENT REQUEST message the Suggested interface identifier IE with the PDU session type value field set to "IPv6" and containing the interface identifier for the IPv6 link local address associated with the PDU session suggested to be allocated to the FN-RG. If the UE supports provisioning of ECS configuration information to the EEC in the UE, then the UE shall include the Extended protocol configuration options IE in the PDU SESSION ESTABLISHMENT REQUEST message and shall include the ECS configuration information provisioning support indicator. If the UE supports receiving DNS server addresses in protocol configuration options, the UE shall include the Extended protocol configuration options IE in the PDU SESSION ESTABLISHMENT REQUEST message and in the Extended protocol configuration options IE: a) if the UE requests to establish a PDU session of "IPv4" or "IPv4v6" PDU session type, the UE shall include the DNS server IPv4 address request; and b) if the UE requests to establish a PDU session of "IPv6" or "IPv4v6" PDU session type, the UE shall include the DNS server IPv6 address request. If the UE supporting UAS services requests to establish a PDU session for C2 communication, the UE shall include the Service-level-AA container IE in the PDU SESSION ESTABLISHMENT REQUEST message. In the Service-level-AA container IE, the UE shall include: a) the service-level device ID with the value set to the CAA-level UAV ID of the UE; and b) if available, the service-level-AA payload with the value set to the C2 authorization payload and the service-level-AA payload type with the value set to "C2 authorization payload". NOTE 11: The C2 authorization payload in the service-level-AA payload can include one, some or all of the pairing information for C2 communication, an indication of the request for direct C2 communication, pairing information for direct C2 communication, and the UAV flight authorization information. If the UE supports the EAS rediscovery, the UE shall include the Extended protocol configuration options IE in the PDU SESSION ESTABLISHMENT REQUEST message and shall include the EAS rediscovery support indication in the Extended protocol configuration options IE. If the UE needs to include a PDU session pair ID based on the matching URSP rule or UE local configuration, the UE shall include the PDU session pair ID IE in the PDU SESSION ESTABLISHMENT REQUEST message. If the UE needs to include an RSN based on the matching URSP rule or UE local configuration, the UE shall include the RSN IE in the PDU SESSION ESTABLISHMENT REQUEST message. If the UE is not registered for onboarding services in SNPN and needs PVS information, the UE shall include the Extended protocol configuration options IE in the PDU SESSION ESTABLISHMENT REQUEST message and include the PVS information request in the Extended protocol configuration options IE. If the UE supports the EDC, the UE shall include the Extended protocol configuration options IE in the PDU SESSION ESTABLISHMENT REQUEST message and shall include the EDC support indicator in the Extended protocol configuration options IE. If the UE supports a "destination MAC address range type" packet filter component and a "source MAC address range type" packet filter component, the UE shall include the Extended protocol configuration options IE in the PDU SESSION ESTABLISHMENT REQUEST message and shall include the MS support of MAC address range in 5GS indicator in the Extended protocol configuration options IE. If the UE supports reporting of URSP rule enforcement and is indicated to send URSP rule enforcement report to network based on the matching URSP rule which contains the URSP rule enforcement report indication set to "URSP rule enforcement report is required", the UE shall include connection capabilities in the PDU SESSION ESTABLISHMENT REQUEST message. Editor’s note [CR#5362, eUEPO]: How to include connection capabilities in the the PDU SESSION ESTABLISHMENT REQUEST message is FFS. The UE shall transport: a) the PDU SESSION ESTABLISHMENT REQUEST message; b) the PDU session ID of the PDU session being established, being handed over, being transferred, or been established as an MA PDU session; c) if the request type is set to: 1) "initial request" or "MA PDU request" and the UE determined to establish a new PDU session or an MA PDU session based on either a URSP rule including one or more S-NSSAIs in the URSP (see subclause 6.2.9) or UE local configuration, according to subclause 4.2.2 of 3GPP TS 24.526[ User Equipment (UE) policies for 5G System (5GS); Stage 3 ] [19]: i) if the UE is in the HPLMN or the subscribed SNPN, an S-NSSAI in the allowed NSSAI which corresponds to one of the S-NSSAI(s) in the matching URSP rule, if any, or else to the S-NSSAI(s) in the UE local configuration or in the default URSP rule, if any, according to the conditions given in subclause 4.2.2 of 3GPP TS 24.526[ User Equipment (UE) policies for 5G System (5GS); Stage 3 ] [19]; ii) if the UE is in a non-subscribed SNPN, the UE determined according to the conditions given in subclause 4.2.2 of 3GPP TS 24.526[ User Equipment (UE) policies for 5G System (5GS); Stage 3 ] [19] to establish a new PDU session or an MA PDU session based on a URSP rule including one or more S-NSSAIs, and the URSP rule is a part of a non-subscribed SNPN signalled URSP (see 3GPP TS 24.526[ User Equipment (UE) policies for 5G System (5GS); Stage 3 ] [19]): A) an S-NSSAI in the allowed NSSAI, which is one of the S-NSSAI(s) in the URSP rule; and B) a mapped S-NSSAI associated with the S-NSSAI in A); or iii) otherwise: A) one of the mapped S-NSSAI(s) which is equal to one of the S-NSSAI(s) in the matching URSP rule, if any, or else to the S-NSSAI(s) in the UE local configuration or in the default URSP rule, if any, according to the conditions given in subclause 4.2.2 of 3GPP TS 24.526[ User Equipment (UE) policies for 5G System (5GS); Stage 3 ] [19]; and B) the S-NSSAI in the allowed NSSAI associated with the S-NSSAI in A); or 1a) "initial request" and the UE determined to establish a new PDU session based on the PDU session parameters for 5G ProSe layer-3 UE-to-network relay UE including an S-NSSAI in the UE policies for 5G ProSe UE-to-network relay UE as defined in 3GPP TS 24.555[ Proximity-services (ProSe) in 5G System (5GS); User Equipment (UE) policies; Stage 3 ] [19F]: i) in case of a non-roaming scenario, an S-NSSAI in the allowed NSSAI which corresponds to the S-NSSAI in the selected PDU session parameters for 5G ProSe layer-3 UE-to-network relay UE, if any; or ii) in case of a roaming scenario: A) one of the mapped S-NSSAI(s) which corresponds to the S-NSSAI in the selected PDU session parameters for 5G ProSe layer-3 UE-to-network relay UE, if any; and B) the S-NSSAI in the allowed NSSAI associated with the S-NSSAI in A); NOTE 12: When the UE is roaming, an AMF compliant with earlier versions of the specification can omit providing to the UE a mapped S-NSSAI for one or more S-NSSAIs in the allowed NSSAI and the UE then locally sets the mapped S-NSSAI as described in subclause 4.6.2.1. 1b) "initial request" and the UE has the partially allowed NSSAI and determined to establish a new PDU session based on either a URSP rule including one or more S-NSSAIs in the URSP (see subclause 6.2.9) or UE local configuration, according to subclause 4.2.2 of 3GPP TS 24.526[ User Equipment (UE) policies for 5G System (5GS); Stage 3 ] [19]: i) if the UE is in the HPLMN or the subscribed SNPN and the current TA is in the list of TAs for which the S-NSSAI is allowed, an S-NSSAI in the partially allowed NSSAI which corresponds to one of the S-NSSAI(s) in the matching URSP rule, if any, or else to the S-NSSAI(s) in the UE local configuration or in the default URSP rule, if any, according to the conditions given in subclause 4.2.2 of 3GPP TS 24.526[ User Equipment (UE) policies for 5G System (5GS); Stage 3 ] [19]; ii) if the UE is in the VPLMN or a non-subscribed SNPN, the UE determined according to the conditions given in subclause 4.2.2 of 3GPP TS 24.526[ User Equipment (UE) policies for 5G System (5GS); Stage 3 ] [19] to establish a new PDU session based on a URSP rule including one or more S-NSSAIs, the URSP rule is a part of a non-subscribed SNPN signalled URSP (see 3GPP TS 24.526[ User Equipment (UE) policies for 5G System (5GS); Stage 3 ] [19]) and the current TA is in the list of TAs for which the S-NSSAI is allowed: A) an S-NSSAI in the partially allowed NSSAI, which is one of the S-NSSAI(s) in the URSP rule; and B) a mapped S-NSSAI associated with the S-NSSAI in A); or 2) "existing PDU session", an S-NSSAI, which is an S-NSSAI in the allowed NSSAI associated with the PDU session and (in roaming scenarios) a mapped S-NSSAI, with exception when S-NSSAI is not provided by the network in subclause 6.1.4.2; c1) the alternative S-NSSAI associated with the S-NSSAI to be replaced, if an alternative S-NSSAI for the S-NSSAI or the mapped S-NSSAI exists; d) if the request type is set to: 1) "initial request" or "MA PDU request" and the UE determined to establish a new PDU session or an MA PDU session based on either a URSP rule including one or more DNNs in the URSP (see subclause 6.2.9) or UE local configuration, according to subclause 4.2.2 of 3GPP TS 24.526[ User Equipment (UE) policies for 5G System (5GS); Stage 3 ] [19], a DNN which corresponds to one of the DNN(s) in the matching URSP rule, if any, or else to the DNN(s) in the UE local configuration or in the default URSP rule, if any, according to the conditions given in subclause 4.2.2 of 3GPP TS 24.526[ User Equipment (UE) policies for 5G System (5GS); Stage 3 ] [19]; 1a) "initial request" and the UE determined to establish a new PDU session based on the PDU session parameters for 5G ProSe layer-3 UE-to-network relay UE including a DNN in the UE policies for 5G ProSe UE-to-network relay UE as defined in 3GPP TS 24.555[ Proximity-services (ProSe) in 5G System (5GS); User Equipment (UE) policies; Stage 3 ] [19F], a DNN which corresponds to the DNN in the selected PDU session parameters for 5G ProSe layer-3 UE-to-network relay UE, if any; or 2) "existing PDU session", a DNN which is a DNN associated with the PDU session; e) the request type which is set to: 1) "initial request", if the UE is not registered for emergency services and the UE requests to establish a new non-emergency PDU session; 2) "existing PDU session", if the UE is not registered for emergency services and the UE requests: i) handover of an existing non-emergency PDU session between 3GPP access and non-3GPP access; ii) transfer of an existing PDN connection for non-emergency bearer services in the EPS to the 5GS; or iii) transfer of an existing PDN connection for non-emergency bearer services in an untrusted non-3GPP access connected to the EPC to the 5GS; 3) "initial emergency request", if the UE requests to establish a new emergency PDU session; 4) "existing emergency PDU session", if the UE requests: i) handover of an existing emergency PDU session between 3GPP access and non-3GPP access; ii) transfer of an existing PDN connection for emergency bearer services in the EPS to the 5GS; or iii) transfer of an existing PDN connection for emergency bearer services in an untrusted non-3GPP access connected to the EPC to the 5GS; or 5) "MA PDU request", if: i) the UE requests to establish an MA PDU session; ii) the UE requests to establish user plane resources over other access of an MA PDU session established over one access only; or iii) the UE performs inter-system change from S1 mode to N1 mode according to subclause 4.8.2.3.1 and requests transfer of a PDN connection which is a user plane resource of an MA PDU session; and f) the old PDU session ID which is the PDU session ID of the existing PDU session, if the UE initiates the UE-requested PDU session establishment procedure upon receiving the PDU SESSION MODIFICATION COMMAND messages with the 5GSM cause IE set to #39 "reactivation requested"; NOTE 13: If the PDU SESSION MODIFICATION COMMAND message included alternative S-NSSAI, the UE includes alternative S-NSSAI in the PDU SESSION ESTABLISHMENT REQUEST message for PDU session re-establishment. using the NAS transport procedure as specified in subclause 5.4.5, and the UE shall start timer T3580 (see example in figure 6.4.1.2.1). For bullet c) 1), if the matching URSP rule does not have an associated S-NSSAI, or if the UE does not have any matching URSP rule and there is no S-NSSAI in the UE local configuration or in the default URSP rule, the UE shall not provide any S-NSSAI in a PDU session establishment procedure. For bullet c) 1a), if the selected PDU session parameters for 5G ProSe layer-3 UE-to-network relay UE do not have an associated S-NSSAI, the UE shall not provide any S-NSSAI in a PDU session establishment procedure. For bullet d) 1), - If the matching non-default URSP rule does not have an associated DNN, then the UE shall not provide any DNN in a PDU session establishment procedure; - If the UE does not have any matching non-default URSP rule, the UE requests a connectivity that requires PAP/CHAP and the UE is configured with the default DNN for the S-NSSAI in the UE local configuration corresponding to the request, then the UE should provide such DNN in a PDU session establishment procedure; - If the UE does not have any matching non-default URSP rule, the UE requests a connectivity that requires PAP/CHAP, the UE is not configured with the default DNN for the S-NSSAI in the UE local configuration corresponding to the request, and the application provides the DNN, then the UE shall use such DNN in a PDU session establishment procedure; - If the UE does not have any matching non-default URSP rule, the UE requests a connectivity that does not require PAP/CHAP, the UE is not configured with the DNN for the S-NSSAI in the UE local configuration corresponding to the request, and the application provides the DNN, then the UE shall use such DNN in a PDU session establishment procedure; - If the UE does not have any matching non-default URSP rule, the UE requests a connectivity that requires PAP/CHAP, the UE is not configured with the default DNN for the S-NSSAI in the UE local configuration corresponding to the request, the application does not provide the DNN and there is no DNN in the default URSP rule, then the UE shall not provide any DNN in a PDU session establishment procedure; or - If the UE does not have any matching non-default URSP rule, the UE requests a connectivity that does not require PAP/CHAP, the UE is not configured with the DNN for the S-NSSAI in the UE local configuration corresponding to the request, the application does not provide the DNN and there is no DNN in the default URSP rule, then the UE shall not provide any DNN in a PDU session establishment procedure. For bullet d) 1a), if the selected the PDU session parameters for 5G ProSe layer-3 UE-to-network relay UE do not have an associated DNN, the UE shall not provide any DNN in a PDU session establishment procedure. If the request type is set to "initial emergency request" or "existing emergency PDU session" or the UE is registered for onboarding services in SNPN, neither DNN nor S-NSSAI is transported by the UE using the NAS transport procedure as specified in subclause 5.4.5. Figure 6.4.1.2.1: UE-requested PDU session establishment procedure Upon receipt of a PDU SESSION ESTABLISHMENT REQUEST message, a PDU session ID, optionally an S-NSSAI associated with (in roaming scenarios) a mapped S-NSSAI, optionally a DNN determined by the AMF, optionally a DNN selected by the network (if different from the DNN determined by the AMF), the request type, and optionally an old PDU session ID, the SMF checks whether connectivity with the requested DN can be established. If the requested DNN is not included, the SMF shall use the default DNN. If the PDU session being established is a non-emergency PDU session, the request type is not set to "existing PDU session" and the PDU session authentication and authorization by the external DN is required due to local policy, the SMF shall check whether the PDU SESSION ESTABLISHMENT REQUEST message includes the SM PDU DN request container IE or the Service-level-AA container IE. If the PDU session being established is a non-emergency PDU session, the request type is not set to "existing PDU session", the SM PDU DN request container IE is included in the PDU SESSION ESTABLISHMENT REQUEST message, the PDU session authentication and authorization by the external DN is required due to local policy and user's subscription data, and: a) the information for the PDU session authentication and authorization by the external DN in the SM PDU DN request container IE is compliant with the local policy and user's subscription data, the SMF shall proceed with the EAP Authentication procedure specified in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24] and refrain from accepting or rejecting the PDU SESSION ESTABLISHMENT REQUEST message until the EAP Authentication procedure finalizes; or b) the information for the PDU session authentication and authorization by the external DN in the SM PDU DN request container IE is not compliant with the local policy and user's subscription data, the SMF shall consider it as an abnormal case and proceed as specified in subclause 6.4.1.7. If the PDU session being established is a non-emergency PDU session, the request type is not set to "existing PDU session", the SM PDU DN request container IE is not included in the PDU SESSION ESTABLISHMENT REQUEST message and the PDU session authentication and authorization by the external DN is required due to local policy and user's subscription data, the SMF shall proceed with the EAP Authentication procedure specified in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24] and refrain from accepting or rejecting the PDU SESSION ESTABLISHMENT REQUEST message until the EAP Authentication procedure finalizes. If the SMF receives the old PDU session ID from the AMF and a PDU session exists for the old PDU session ID, the SMF shall consider that the request for the relocation of SSC mode 3 PDU session anchor with multiple PDU sessions as specified in 3GPP TS 23.502[ Procedures for the 5G System (5GS) ] [9] is accepted by the UE. If the SMF receives the onboarding indication from the AMF, the SMF shall consider that the PDU session is established for onboarding services in SNPN. If the UE has set the TPMIC bit to "Transfer of port management information containers supported" in the 5GSM capability IE of the PDU SESSION ESTABLISHMENT REQUEST message and has included a DS-TT Ethernet port MAC address IE (if the PDU session type is "Ethernet"), the Port management information container IE, and, optionally, the UE-DS-TT residence time IE in the PDU SESSION ESTABLISHMENT REQUEST message, the SMF shall operate as specified in 3GPP TS 23.502[ Procedures for the 5G System (5GS) ] [9] subclause 4.3.2.2.1. If requested by the upper layers, the UE supporting UAS services shall initiate a request to establish a PDU session for UAS services, where the UE: a) shall include the service-level device ID with the value set to the CAA-level UAV ID; b) if provided by the upper layers, shall include the service-level-AA server address, with the value set to the USS address; and c) if provided by the upper layers, shall include: i) the service-level-AA payload type, with the value set to "UUAA payload"; and ii) the service-level-AA payload, with the value set to UUAA payload, in the Service-level-AA container IE of the PDU SESSION ESTABLISHMENT REQUEST message. If the PDU session being established is a non-emergency PDU session, the request type is not set to "existing PDU session", the Service-level-AA container IE is included in the PDU SESSION ESTABLISHMENT REQUEST message, and a) the service-level authentication and authorization by the external DN is required due to local policy; b) there is a valid user's subscription information for the requested DNN or for the requested DNN and S-NSSAI; and c) the information for the service-level authentication and authorization by the external DN in the Service-level-AA container IE includes CAA-level UAV ID, then the SMF shall proceed with the UUAA-SM procedure as specified in 3GPP TS 23.256[ Support of Uncrewed Aerial Systems (UAS) connectivity, identification and tracking; Stage 2 ] [6AB] and refrain from accepting or rejecting the PDU SESSION ESTABLISHMENT REQUEST message until the service-level authentication and authorization procedure is completed. The UE supporting UAS services shall not request a PDU session establishment procedure to the same DNN (or no DNN, if no DNN was indicated by the UE) and the same S-NSSAI (or no S-NSSAI, if no S-NSSAI was indicated by the UE) for which the UE has requested a service level authentication and authorization procedure which is ongoing. If the PDU SESSION ESTABLISHMENT REQUEST message includes the PDU session pair ID IE, the RSN IE, or both, the SMF shall operate as specified in subclause 5.33.2 of 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8]. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.4.1.2 |
5,870 | 9.4.10a Authentication and Ciphering Failure | This message is sent by the mobile station to the network to indicate that authentication of the network has failed. See table 9.4.10a/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Message type: AUTHENTICATION AND CIPHERING FAILURE Significance: dual Direction: mobile station to network Table 9.4.10a/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : AUTHENTICATION AND CIPHERING FAILURE message content | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.4.10a |
5,871 | 6.6.1 Description | Video-based services (e.g. live streaming, VR) and personal data storage applications have been instrumental for the massive growth in mobile broadband traffic. Subject to service agreement between the operator and the content provider, the information of content and content itself can be aware by operator. In-network content caching provided by the operator, a third-party or both, can improve user experience, reduce backhaul resource usage and utilize radio resource efficiently. The operation of in-network caching includes flexible management of the location of the content cache within the network and efficient delivery of content to and from the appropriate content caching application. Examples of services are the delivery of popular video content from a content caching application via broadcast, and secure storage of a user's personal data or files using a distributed caching application. Such a service could also provide a student with a wireless backpack, where students can resume their work through the same or a different UE at any time, with very fast response times from the network. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.6.1 |
5,872 | 9.8.3.2 TDD | The following requirements apply to UE supporting supporting ce-ModeA-r13 and ce-PDSCH-64QAM-r15. For the parameters specified in Table 9.8.3.2-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.31 TDD 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.3.2-1: PUCCH 1-0 static test (TDD) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 9.8.3.2 |
5,873 | – BWP-DownlinkCommon | The IE BWP-DownlinkCommon is used to configure the common parameters of a downlink BWP. They are "cell specific" and the network ensures the necessary alignment with corresponding parameters of other UEs. The common parameters of the initial bandwidth part of the PCell are also provided via system information. For all other serving cells, the network provides the common parameters via dedicated signalling. BWP-DownlinkCommon information element -- ASN1START -- TAG-BWP-DOWNLINKCOMMON-START BWP-DownlinkCommon ::= SEQUENCE { genericParameters BWP, pdcch-ConfigCommon SetupRelease { PDCCH-ConfigCommon } OPTIONAL, -- Need M pdsch-ConfigCommon SetupRelease { PDSCH-ConfigCommon } OPTIONAL, -- Need M ... } -- TAG-BWP-DOWNLINKCOMMON-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
5,874 | 9.4.4.1 T3302 value | This IE may be included to indicate a value for the T3302 timer. In Iu mode, if the MS is not attaching for emergency services, the network shall not include this IE if this message is to be sent non-integrity protected. If the MS is attaching for emergency bearer services, the network may include this IE if this message is to be sent non-integrity protected. In Iu mode, if the MS is not attaching for emergency services, the MS shall ignore the contents of this IE if this message is received without integrity protection. If the MS is attaching for emergency bearer services, the MS shall use the received contents of this IE if this message is received without integrity protection. If this IE is not included or if in Iu mode the message is not integrity protected, the MS shall use the default value. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.4.4.1 |
5,875 | 5.5.2.5 Inter RAT handover Cancel 5.5.2.5.1 General | Instead of completing the handover procedure, the source RAN node (eNodeB, RNC or BSS) may at any time during the handover procedure, up to the time when a handover command message is sent to the UE cancel the handover. The reason for cancelling may be e.g. due to a timer expiration or due to other events within the source RAN node and is initiated by sending a handover cancel PDU to the source EPC node (MME or SGSN). A handover cancel PDU shall also be sent by the source RAN node after a handover command message is sent to the UE for the case where the handover fails and the UE returns to the old cell or radio contact with the UE is lost. This is done in order to release the resources reserved for the Handover in the target system. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.5.2.5 |
5,876 | 4.2.2.2.4 Registration with Onboarding SNPN | This clause specifies how a UE can register to an ON-SNPN for provisioning the UE with SO-SNPN credentials and other information to enable SNPN access as defined in clause 5.30.2.10 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The Registration procedure for Onboarding SNPN over 3GPP access shall be supported as specified in clause 4.2.2.2.2 with the following changes compared to the steps in the call flow represented in Figure 4.2.2.2.2-1, covering three cases, i.e. when DCS is hosting AAA Server and when DCS is hosting AUSF/UDM and when DCS is not involved, as shown in Figure 4.2.2.2.4-1. The Registration procedure for Onboarding SNPN over untrusted non-3GPP access shall be supported as specified in clause 4.12.2.2. The Registration procedure for Onboarding SNPN over trusted non-3GPP access shall be supported as specified in clause 4.12a.2.2. Figure 4.2.2.2.4-1: UE Registration with ON-SNPN 1. UE to NG-RAN: AN parameters shall include Onboarding indication if the UE is accessing 5GS for Onboarding. The Registration Type "SNPN Onboarding" indicates that the UE wants to perform SNPN Onboarding Registration (i.e. allows the UE to access an ON-SNPN for the purpose of provisioning the UE with SO-SNPN credentials). For SNPN Onboarding Registration, a SUCI generated from a SUPI derived from Default UE Credentials shall be included as described in clause 5.30.2.10.2.6 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If the UE has registered in the ON-SNPN for onboarding, the UE can perform a Mobility Registration Update, or a Periodic Registration Update as specified in clause 4.2.2.2.2. If the onboarding registered UE wants to perform a Mobility Registration Update the AN parameters shall also include an Onboarding indication that the UE is registered for onboarding. NOTE: When the UE is performing Registration for Onboarding to an ON-SNPN, the UE does not include a Requested NSSAI as the UE is not pre-configured with a S-NSSAI for the purpose of UE onboarding in the ON-SNPN. 2. Based on the Onboarding indication in step 1, the NG-RAN selects an AMF as described in clause 6.3.5 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. 3. NG-RAN to AMF: The N2 message contains the Registration Request as described in step 1. 4. [Conditional] new AMF to old AMF: Namf_Communication_UEContextTransfer (complete Registration Request). 5. [Conditional] old AMF to new AMF: Response to Namf_Communication_UEContextTransfer (SUPI, UE Context in AMF (as per Table 5.2.2.2.2-1)). Once the registration is completed successfully, the new AMF may start an implementation specific deregistration timer for when to deregister the onboarding registered UE if the UE context contains the indication that the UE is registered for onboarding. 6-7. Skipped. 8. When the AMF receives a NAS Registration Request with the 5GS Registration Type set to "SNPN Onboarding", the AMF applies locally configured AMF Configuration Data for Onboarding in order to restrict UE network usage to only onboarding and stores in the UE Context in AMF an indication that the UE is registered for onboarding. The AMF selects an AUSF as described in clause 5.30.2.10.2.6 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. Based on ON-SNPN policies, the AMF may start an implementation specific deregistration timer configured for UE Onboarding as described in TS 23.501[ System architecture for the 5G System (5GS) ] [2]. 9. The authentication is performed as described in TS 33.501[ Security architecture and procedures for 5G System ] [15]. For DCS hosting AAA Server as shown in step 9-1, based on local configuration (e.g. using the realm part of the SUCI), the AUSF sends the SUPI towards the AAA Server in the DCS domain via the NSSAAF, then the AAA Server in the DCS domain authenticates the UE based on received data from AUSF. During authentication procedure the AAA Server in the DCS domain may provide PVS FQDN(s) and/or PVS IP address(es) for the UE to the AUSF via the NSSAAF, the AUSF then provides PVS FQDN(s) and/or PVS IP address(es) to the AMF. For DCS hosting AUSF/UDM as shown in step 9-2, the AUSF in DCS domain performs UDM selection. The AMF sends the SUCI and Default UE credentials received from the UE towards the AUSF in DCS domain, which authenticates the UE based on received data from AMF and subscription data from the UDM in DCS domain. During authentication procedure, the AUSF in the DCS domain provides PVS FQDN(s) and/or PVS IP address(es) to the AMF. When DCS is not involved during primary authentication as shown in step 9-3, the AMF selects a local AUSF as defined in clause 6.3.4 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] and performs primary authentication towards the local AUSF using Default UE credentials as described in TS 33.501[ Security architecture and procedures for 5G System ] [15]. 10. [Conditional] new AMF to old AMF: Namf_Communication_RegistrationStatusUpdate. 11. [Conditional] AMF to UE: Identity Request/Response (PEI). If the PEI was not provided by the UE, the Identity Request procedure is initiated by AMF sending an Identity Request message to the UE to retrieve the PEI. 12. Optionally the new AMF initiates ME identity check by invoking the N5g-eir_EquipmentIdentityCheck_Get service operation (see clause 5.2.4.2.2). The PEI check is performed as described in clause 4.7. 13-20. Skipped. 21. AMF to UE: The AMF sends a Registration Accept message to the UE indicating that the Registration Request for Onboarding SNPN has been accepted. The Allowed NSSAI containing the S-NSSAI from the AMF Onboarding Configuration Data is included in the N2 message to NG-RAN. 21b. Skipped. 22. UE to AMF: The UE sends a Registration Complete message to the AMF. 23-25. Skipped. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.2.2.2.4 |
5,877 | 5.5.2.4.4 GERAN A/Gb mode to E-UTRAN Inter RAT handover reject | The Target eNodeB may reject the use of the Handover procedure if none of the requested EPS bearers in the Handover Request message could be established. In this case no UE context is established in the target MME/eNodeB and no resources are allocated. The UE remains in the Source BSS/SGSN. Figure 5.5.2.4.4-1: GERAN A/Gb mode to E-UTRAN inter RAT HO reject 1. Steps 1 to 5 in the flow are identical to the ones in clause 5.5.2.4.2. 6. If the Target eNodeB fails to allocate any resources for any of the requested EPS Bearers it sends a Handover Failure (Cause) message to the Target MME. When the Target MME receives the Handover Failure message from Target eNodeB the Target MME clears any reserved resources for this UE. 7. This step is only performed for Serving GW relocation, i.e. if Steps 4/4a have been performed. The Target MME deletes the EPS bearer resources by sending Delete Session Request (Cause) messages to the Target Serving GW. The Target Serving GW acknowledges with Delete Session Response (Cause) messages. 8. The Target MME sends the Forward Relocation Response (Cause) message to the Source SGSN. 9. When the Source SGSN receives the Forward Relocation Response message it send a PS Handover Required Negative Acknowledge (Cause) message to the Source BSS. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.5.2.4.4 |
5,878 | 5.31.18 User Plane CIoT 5GS Optimisation | User Plane CIoT 5GS Optimisation enables transfer of user plane data from CM-IDLE without the need for using the Service Request procedure to establish Access Stratum (AS) context in NG-RAN and UE. If the following preconditions are met: - UE and AMF negotiated support User Plane CIoT 5GS Optimisation (see clause 5.31.2) over NAS, - the UE has indicated support of User Plane CIoT 5GS Optimisation in the UE radio capabilities as defined in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [51], - AMF has indicated User Plane CIoT 5GS Optimisation support for the UE to NG-RAN, - the UE has established at least one PDU session with active UP connection, i.e. AS context is established in NG-RAN and the UE, then the RRC connection can be suspended by means of the Connection Suspend Procedure (see clause 4.8.1.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]). Based on a trigger from the NAS layer when a UE is in CM-IDLE with Suspend, the UE should attempt the Connection Resume in CM-IDLE with Suspend procedure (clause 4.8.2.3 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]). If the Connection Resume in CM-IDLE with Suspend procedure fails, the UE initiates the pending NAS procedure. To maintain support for User Plane CIoT 5GS Optimisation for UE mobility across different NG-RAN nodes, the AS Context should be transferred between the NG-RAN nodes, see TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [27] and TS 38.423[ NG-RAN; Xn Application Protocol (XnAP) ] [99]. For MT data or signalling when the UE is in CM-IDLE with Suspend, Network Triggered Service Request procedure (clause 4.2.3.3 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]) applies. By using the Connection Suspend Procedure: - the UE at transition into CM-IDLE stores the AS information; - NG-RAN stores the AS information, the NGAP UE association and the PDU session context for that UE; - AMF stores the NGAP UE association and other information necessary to later resume the UE, interacts with the SMF(s) to deactivate the user plane resources for the UE's PDU Sessions and enters CM-IDLE. NG-RAN may decide based on implementation to delete the stored UE context and NGAP association. In that case, the RAN shall initiate the AN Release procedure as described in clause 4.2.6 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. NG-RAN does not initiate any RRC procedure to notify the UE of the UE context release. By using the Connection Resume in CM-IDLE with Suspend procedure: - the UE resumes the connection from CM-IDLE with the network using the AS information stored during the Connection Suspend procedure; - NG-RAN notifies the AMF that the connection with the UE has been resumed; - AMF enters CM-CONNECTED and interacts with the SMF to activate the user plane resources for the UE's PDU Sessions. Early Data Transmission may be initiated by the UE for mobile originated User Plane CIoT 5GS Optimisation during Connection Resume. If the AMF establishes an NGAP UE association with a new NG-RAN node different from the stored NGAP UE association, e.g. the UE initiates service request or registration procedure from a different NG-RAN node, the AMF initiates UE N2 release command towards the old NG-RAN node. NG-RAN maintains the N3 tunnel endpoint information while a UE is in CM-IDLE with Suspend. UPF is instructed to remove DL N3 Tunnel Info of AN during Connection Suspend procedure, while UPF keeps UL N3 Tunnel Info (i.e. UPF accepts and forwards UL data). If a UE sends MO data with resume procedure, the NG-RAN can send the MO data to the UPF which is addressed by the N3 tunnel endpoint information. In the case of change of serving NG-RAN node due to UE mobility, if NG-RAN determines that it is not able to connect to the UPF which is addressed by the N3 tunnel endpoint information, NG-RAN performs Path Switch procedure before sending the MO data received from the UE. Early Data Transmission may be initiated by the UE for mobile originated User Plane CIoT 5GS Optimisation when the RAT Type is E-UTRA. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.31.18 |
5,879 | 5.4.2 Exception conditions | Under normal conditions, the call control entity of the mobile station or of the network initiates call clearing by sending a DISCONNECT message to its peer entity; then both entities follow the procedures defined in subclauses 5.4.3 and 5.4.4 respectively. As an exception to the above rule, the call control entity of the mobile station or of the network, in response to a SETUP or START CC or CC-ESTABLISHMENT CC-ESTABLISHMENT CONFIRMED or RECALL message, can reject a call by stopping all running call control timers, responding with a RELEASE COMPLETE message, releasing the MM connection, and returning to the "null" state, provided no other response has previously been sent. As a further exception, the call control entity of the network may initiate call clearing by stopping all running call control timers, sending a RELEASE message, starting timer T308, and entering the "release request" state. NOTE: This way to initiate call clearing by sending a RELEASE message should not be used by the network: - if in-band tones/announcements are provided and the network decides to use the procedure described in subclause 5.4.4.1.1.1 or 5.4.4.2.1; - if the network wants to have the opportunity to respond to information sent by the mobile station during call clearing, e.g. when the network indicates that "CCBS activation is possible". A call control entity shall accept an incoming RELEASE COMPLETE message used to initiate the call clearing even though the cause information element is not included. A control entity shall accept an incoming RELEASE message used to initiate the call clearing even though the cause information element is not included. Furthermore, a call control entity shall regard an incoming RELEASE COMPLETE message as consistent with any of its states; a call control entity shall regard an incoming RELEASE message as consistent with any of its states except the null state: a call control entity of the mobile station shall regard an incoming DISCONNECT message as consistent with any of its call control states except the "null" state, the "release request" state, and the "disconnect indication" state; a call control entity of the network shall regard an incoming DISCONNECT message as consistent with any of its call control states except the "null" state and the "release request" state. NOTE: This allows the introduction of shorter call clearing procedures in the future. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.4.2 |
5,880 | 6.3.2 Distribution of authentication data from HE to SN | The purpose of this procedure is to provide the VLR/SGSN with an array of fresh authentication vectors from the user's HE to perform a number of user authentications. Figure 6: Distribution of authentication data from HE to VLR/SGSN The VLR/SGSN invokes the procedures by requesting authentication vectors to the HE/AuC. The authentication data request shall include the IMSI and the requesting node type (PS or CS). Upon the receipt of the authentication data request from the VLR/SGSN, the HE may have pre-computed the required number of authentication vectors and retrieve them from the HLR database or may compute them on demand. The HE/AuC sends an authentication response back to the VLR/SGSN that contains an ordered array of n authentication vectors AV(1..n). The authentication vectors are ordered based on sequence number. Figure 7 shows the generation of an authentication vector AV by the HE/AuC. Figure 7: Generation of authentication vectors The HE/AuC starts with generating a fresh sequence number SQN and an unpredictable challenge . For each user the HE/AuC keeps track of a counter: SQNHE The HE has some flexibility in the management of sequence numbers, but some requirements need to be fulfilled by the mechanism used: a) The generation mechanism shall allow a re-synchronisation procedure in the HE described in section 6.3.5. b) In case the SQN exposes the identity and location of the user, the AK may be used as an anonymity key to conceal it. c) The generation mechanism shall allow protection against wrap around of the counter SQN in the USIM. A method how to achieve this is given in informative Annex C.2. NOTE: A wrap around of the counter SQN could lead to a repeated use of a key pair (CK, IK). This repeated key use could potentially be exploited by an attacker to compromise encryption or forge message authentication codes applied to data sent over the 3GPP-defined air interfaces. The mechanisms for verifying the freshness of sequence numbers in the USIM shall to some extent allow the out-of-order use of sequence numbers. This is to ensure that the authentication failure rate due to synchronisation failures is sufficiently low. This requires the capability of the USIM to store information on past successful authentication events (e.g. sequence numbers or relevant parts thereof). The mechanism shall ensure that a sequence number can still be accepted if it is among the last x = 32 sequence numbers generated. This shall not preclude that a sequence number is rejected for other reasons such as a limit on the age for time-based sequence numbers. The same minimum number x needs to be used across the systems to guarantee that the synchronisation failure rate is sufficiently low under various usage scenarios, in particular simultaneous registration in the CS- and the PS-service domains, user movement between VLRs/SGSNs which do not exchange authentication information, super-charged networks. The use of SQNHE is specific to the method of generation sequence numbers. A method is specified in Annex C.1 how to generate a fresh sequence number. A method is specified in Annex C.2 how to verify the freshness of a sequence number. An authentication and key management field AMF is included in the authentication token of each authentication vector. Annex H defines the usage of the AMF. Example uses of the proprietary part of the AMF are included in Annex F. Subsequently the following values are computed: - a message authentication code MAC = f1K(SQN || || AMF) where f1 is a message authentication function; - an expected response XRES = f2K () where f2 is a (possibly truncated) message authentication function; - a cipher key CK = f3K () where f3 is a key generating function; - an integrity key IK = f4K () where f4 is a key generating function; - an anonymity key AK = f5K () where f5 is a key generating function or f5 0. Finally the authentication token AUTN = || AMF || MAC is constructed. Here, AK is an anonymity key used to conceal the sequence number as the latter may expose the identity and location of the user. The concealment of the sequence number is to protect against passive attacks only. If no concealment is needed then f5 0 (AK = 0). | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | 6.3.2 |
5,881 | 9.7.2.4 TDD (Category 1bis UE) | The following requirements apply to UE DL Category 1bis. For the parameters specified in Table 9.7.2.4-1, and using the downlink physical channels specified in Annex C.3.2, the minimum requirements are specified in Table 9.7.2.4-2 and by the following a) a sub-band differential CQI offset level of 0 shall be reported at least % of the time but less than % for each sub-band; b) the ratio of the throughput obtained when transmitting on a randomly selected sub-band among the sub-bands with the highest differential CQI offset level the corresponding TBS and that obtained when transmitting the TBS indicated by the reported wideband CQI median on a randomly selected sub-band in set S shall be ≥ ; c) when transmitting on a randomly selected sub-band among the sub-bands with the highest differential CQI offset level the corresponding TBS, the average BLER for the indicated transport formats shall be greater or equal to 0.05. The requirements only apply for sub-bands of full size and the random scheduling across the sub-bands is done by selecting a new sub-band in each available downlink transmission instance for TDD. Table 9.7.2.4-1 Sub-band test for single antenna transmission (TDD) Table 9.7.2.4-2 Minimum requirement (TDD) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 9.7.2.4 |
5,882 | 4.7.2.7 Handling of timer T3302 | The value of timer T3302 can be sent by the network to the MS in the ATTACH ACCEPT message, ROUTING AREA UPDATE ACCEPT message, ATTACH REJECT message, and ROUTING AREA UPDATE REJECT message. The MS shall apply this value, if the value is different from "deactivated" in the routing area registered by the MS, until a new value is received. The default value of this timer is used in the following cases: - ATTACH ACCEPT message, ATTACH REJECT message, or ROUTING AREA UPDATE REJECT message is received without a value specified; - ROUTING AREA UPDATE ACCEPT message is received without a value specified, and the update type in the ROUTING AREA UPDATE REQUEST message is not set to "periodic updating"; - In Iu mode, if the network provides a value in a non-integrity protected Iu mode GMM message and the MS is not attaching for emergency services or not attached for emergency services; - In A/Gb mode and if the MS supports integrity protection, if the network provides a value in a non-integrity protected GMM message; - the network indicates that the timer is "deactivated"; - the MS does not have a stored value for this timer; - a new PLMN which is not in the list of equivalent PLMNs has been entered, the routing area updating fails and the routing area updating attempt counter is equal to 5; or - a new PLMN which is not in the list of equivalent PLMNs has been entered, the attach procedure fails, and the attach attempt counter is equal to 5. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.7.2.7 |
5,883 | 4.9.1.2 Xn based inter NG-RAN handover 4.9.1.2.1 General | Clause 4.9.1.2 includes details regarding the Xn based inter NG-RAN handover with and without UPF re-allocation. Xn handovers are only supported for intra-AMF mobility. New AMF can be selected by the target NG-RAN node as specified in clause 5.21.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The handover preparation and execution phases are performed as specified in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [9], in the case of handover to a shared network, source NG-RAN determines a PLMN or an SNPN to be used in the target network as specified by TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If the serving PLMN or SNPN changes during Xn-based handover, the source NG-RAN node shall indicate to the target NG-RAN node (in the Mobility Restriction List) the selected PLMN ID or SNPN ID to be used in the target network. During Xn based handover into a shared NG-RAN node the source NG RAN node shall include the serving NID (if available) in the Mobility Restriction List to be used by the target NG-RAN node. If the AMF generates the N2 downlink signalling during the ongoing handover and receives a rejection to a N2 interface procedure (e.g. Location Reporting Control; DL NAS message transfer; etc.) from the NG-RAN with an indication that a Xn based handover procedure is in progress, the AMF may reattempt the same N2 interface procedure either when the handover is complete or the handover is deemed to have failed, when possible. The failure is known by expiry of the timer guarding the N2 interface procedure. Upon reception for an SMF initiated N1 and/or N2 request(s) with an indication that the request has been temporarily rejected due to handover procedure in progress, the SMF starts a locally configured guard timer. Any NF (e.g. the SMF) should hold any signalling messages targeted towards AMF for a given UE during the handover preparation phase unless it detects that the handover execution is completed or handover has failed/cancelled. The NF (e.g. the SMF) may re-attempt, up to a pre-configured number of times, when either it detects that the handover is completed or has failed using message reception or at expiry of the guard timer. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.9.1.2 |
5,884 | 10.5.3.3 CM service type | The purpose of the CM Service Type information element is to specify which service is requested from the network. The CM Service Type information element is coded as shown in figure 10.5.77/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.91/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The CM Service Type is a type 1 information element. Figure 10.5.77/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] CM Service Type information element Table 10.5.91/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : CM Service Type information element | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 10.5.3.3 |
5,885 | 19.9 IMSI-Group Identifier | IMSI-Group Identifier is a network internal globally unique ID which identifies a set of IMSIs (e.g. MTC devices) from a given network that are grouped together for one specific group related services. It is used e.g. for group specifc NAS level congestion control (see 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [72]). An IMSI-Group Identifier shall be composed as shown in figure 19.9-1. Figure 19.9-1: Structure of IMSI-Group Identifier IMSI-Group Identifier is composed of four parts: 1) Group Service Identifier, identifies the service (4 Octets) for which the IMSI-Group Identifier is valid. 2) Mobile Country Code (MCC) consisting of three digits. The MCC identifies uniquely the country of domicile of the mobile subscriber; 3) Mobile Network Code (MNC) consisting of two or three digits. The MNC identifies the home PLMN of the mobile subscriber. The length of the MNC (two or three digits) depends on the value of the MCC. A mixture of two and three digit MNC codes within a single MCC area is not recommended and is outside the scope of this specification. 4) the Local Group Id is assigned by the network operator and may have a length of up to 10 octets. Two different IMSI-Group Identifier values, with the same Group Service Identifier and with MCC/MNC values that point to the same PLMN, shall have two different Local Group Ids. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 19.9 |
5,886 | 5.4.1.6 Abnormal cases on the network side | The following abnormal cases can be identified: a) Lower layer failure If a lower layer failure is detected before the GUTI REALLOCATION COMPLETE message is received, the old and the new GUTI shall be considered as valid until the old GUTI can be considered as invalid by the network. If a new TAI list was provided in the GUTI REALLOCATION COMMAND message, the old and new TAI list shall also be considered as valid until the old TAI list can be considered as invalid by the network. During this period the network: - may first use the old S-TMSI from the old GUTI for paging within the area defined by the old TAI list for an implementation dependent number of paging attempts for network originated transactions. If a new TAI list was provided with old GUTI in the GUTI REALLOCATION COMMAND message, the new TAI list should also be used for paging. Upon response from the UE, the network may re-initiate the GUTI reallocation. If the response is received from a tracking area within the old and new TAI list, the network shall re-initiate the GUTI reallocation. If no response is received to the paging attempts, the network may use the new S-TMSI from the new GUTI for paging for an implementation dependent number of paging attempts. In this case, if a new TAI list was provided with new GUTI in the GUTI REALLOCATION COMMAND message, the new TAI list shall be used instead of the old TAI list. Upon response from the UE the network shall consider the new GUTI as valid and the old GUTI as invalid. If no response is received to the paging attempts, the network may use the IMSI for paging for an implementation dependent number of paging attempts; NOTE 1: Paging with IMSI causes the UE to re-attach as described in clause .2.2. - shall consider the new GUTI as valid if it is used by the UE and, additionally, the new TAI list as valid if it was provided with this GUTI in the GUTI REALLOCATION COMMAND message; - may use the identification procedure followed by a new GUTI reallocation if the UE uses the old GUTI; and - if the network accepted to use eDRX for the UE, may determine the next paging window from both old GUTI and new GUTI, and may first use the S-TMSI from the GUTI which led the first eDRX for paging. If no response is received to the paging attempts for the first eDRX, the network may use the other S-TMSI from the other GUTI which led the second eDRX for paging. For this paging procedure, the network shall start timer T3415 long enough to care the paging attempts for both eDRXs. NOTE 2: If the second eDRX comes during the first eDRX ongoing, the paging attempts for the second eDRX can be initiated with stopping further paging attempts for the first eDRX. b) Expiry of timer T3450 The GUTI reallocation procedure is supervised by the timer T3450. The network shall, on the first expiry of timer T3450, reset and restart timer T3450 and shall retransmit the GUTI REALLOCATION COMMAND. This retransmission is repeated four times, i.e. on the fifth expiry of timer T3450, the network shall abort the reallocation procedure and shall follow the rules described for case a above. c) GUTI reallocation and attach procedure collision If the network receives an ATTACH REQUEST message before the ongoing GUTI reallocation procedure has been completed the network shall proceed with the attach procedure after deletion of the EMM context. d) GUTI reallocation and UE initiated detach procedure collision If the network receives a DETACH REQUEST message before the ongoing GUTI reallocation procedure has been completed, the network shall abort the GUTI reallocation procedure and shall progress the detach procedure. e) GUTI reallocation and tracking area updating procedure collision If the network receives a TRACKING AREA UPDATE REQUEST message before the ongoing GUTI reallocation procedure has been completed, the network shall abort the GUTI reallocation procedure and shall progress the tracking area updating procedure. The network may then perform a new GUTI reallocation. f) GUTI reallocation and service request procedure collision If the network receives an EXTENDED SERVICE REQUEST message for CS fallback or 1xCS fallback before the ongoing GUTI reallocation procedure has been completed, the network shall progress both procedures. g) Lower layer indication of non-delivered NAS PDU due to handover If the GUTI REALLOCATION COMMAND message could not be delivered due to an intra MME handover and the target TA is included in the TAI list, then upon successful completion of the intra MME handover the MME shall retransmit the GUTI REALLOCATION COMMAND message. If a failure of the handover procedure is reported by the lower layer and the S1 signalling connection exists, the MME shall retransmit the GUTI REALLOCATION COMMAND message. If there is a different new GUTI and optionally a new TAI list included in a subsequent GUTI REALLOCATION COMMAND message, the UE always regards the newest GUTI and the newest TAI list as valid for the recovery time. | 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.1.6 |
5,887 | 5.6.10.2 Support of Ethernet PDU Session type | For a PDU Session set up with the Ethernet PDU Session type, the SMF and the UPF acting as PDU Session Anchor (PSA) can support specific behaviours related with the fact the PDU Session carries Ethernet frames. Depending on operator configuration related with the DNN, different configurations for how Ethernet traffic is handled on N6 may apply, for example: - Configurations with a 1-1 relationship between a PDU Session and a N6 interface possibly corresponding to a dedicated tunnel established over N6. In this case the UPF acting as PSA transparently forwards Ethernet frames between the PDU Session and its corresponding N6 interface, and it does not need to be aware of MAC addresses used by the UE in order to route down-link traffic. - Configurations, where more than one PDU Session to the same DNN (e.g. for more than one UE) corresponds to the same N6 interface. In this case the UPF acting as PSA needs to be aware of MAC addresses used by the UE in the PDU Session in order to map down-link Ethernet frames received over N6 to the appropriate PDU Session. Forwarding behaviour of the UPF acting as PSA is managed by SMF as specified in clause 5.8.2.5. NOTE 1: The "MAC addresses used by the UE" correspond to any MAC address used by the UE or any device locally connected to the UE and using the PDU Session to communicate with the DN. Based on operator configuration, the SMF may request the UPF acting as the PDU Session Anchor to respond to ARP/IPv6 Neighbour Solicitation requests based on local cache information, i.e. the mapping between the UE MAC address to the UE IP address, and the DN where the PDU Session is connected to, or to redirect the ARP traffic from the UPF to the SMF. Responding to ARP/IPv6 ND based on local cache information applies to ARP/IPv6 ND received in both UL and DL directions. NOTE 2: Responding to ARP/ND from a local cache assumes the UE or the devices behind the UE acquire their IP address via in-band mechanisms that the SMF/UPF can detect and by this link the IP address to the MAC address. NOTE 3: This mechanism is intended to avoid broadcasting or multicasting the ARP/IPv6 ND to every UE. Ethernet Preamble and Start of Frame delimiter are not sent over 5GS: - For UL traffic the UE strips the preamble and frame check sequence (FCS) from the Ethernet frame. - For DL traffic the PDU Session Anchor strips the preamble and frame check sequence (FCS) from the Ethernet frame. Neither a MAC nor an IP address is allocated by the 5GC to the UE for a PDU Session. The PSA shall store the MAC addresses received from the UE, and associate those with the appropriate PDU Session. The SMF may receive a list of allowed VLAN tags from DN-AAA (for a maximum of 16 VLAN tags) or may be locally configured with allowed VLAN tags values. The SMF may also be configured with instructions on VLAN handling (e.g. the VLAN tag to be inserted or removed, S-TAG to be inserted or removed). Taking this into account, the SMF determines the VLAN handling for the PDU Session, and instructs the UPF to accept or discard the UE traffic based on the allowed VLAN tags, as well as to handle VLAN tags (addition/removal) via PDR (Outer header removal) and FAR (UPF applying Outer header creation of a Forwarding policy). For example: - The UPF may insert (for uplink traffic) and remove (for downlink traffic) a S-TAG on N6 or N19 or internal interface ("5G VN internal") for the traffic from and to the UE. - The UPF may insert (for uplink traffic) and remove (for downlink traffic) a VLAN tag on the N6 interface while there is no VLAN in the traffic to and from the UE. - The UPF may discard any UE traffic that does not contain any allowed VLAN tag when the UPF handles the UE uplink or downlink traffic. NOTE 4: This can be used for traffic steering to N6-LAN but also for N6-based traffic forwarding related with 5G-VN service described in clause 5.29.4 Apart from specific conditions related to the support of PDU sessions over W-5GAN defined in TS 23.316[ Wireless and wireline convergence access support for the 5G System (5GS) ] [84], the UPF shall not remove VLAN tags sent by the UE and the UPF shall not insert VLAN tags for the traffic sent to the UE. PDU(s) containing a VLAN tag shall be switched only within the same VLAN by a PDU Session Anchor. The UE may acquire from the SMF, at PDU Session Establishment, the MTU of the Ethernet frames' payload that the UE shall consider, see clause 5.6.10.4. NOTE 5: The UE may operate in bridge mode with regard to a LAN it is connecting to the 5GS, thus different MAC addresses may be used as source address of different frames sent UL over a single PDU Session (and destination MAC address of different frames sent DL over the same PDU Session). NOTE 6: Entities on the LAN connected to the 5GS by the UE may have an IP address allocated by the DN but the IP layer is considered as an application layer which is not part of the Ethernet PDU Session. NOTE 7: In this Release of the specification, only the UE connected to the 5GS is authenticated, not the devices behind such UE. NOTE 8: 5GS does not support the scenario where a MAC address or if VLAN applies a (MAC address, VLAN) combination is used on more than one PDU Session for the same DNN and S-NSSAI. NOTE 9: This Release of the specification does not guarantee that the Ethernet network remains loop-free. Deployments need to be verified on an individual basis that loops in the Ethernet network are avoided. NOTE 10: This Release of the specification does not guarantee that the Ethernet network properly and quickly reacts to topology changes. Deployments need to be verified on an individual basis how they react to topology changes. Different Frames exchanged on a PDU Session of Ethernet type may be served with different QoS over the 5GS. Thus, the SMF may provide to the UPF Ethernet Packet Filter Set and forwarding rule(s) based on the Ethernet frame structure and UE MAC address(es). The UPF detects and forwards Ethernet frames based on the Ethernet Packet Filter Set and forwarding rule(s) received from the SMF. This is further defined in clauses 5.7 and 5.8.2. When a PDU Session of Ethernet PDU type is authorized by a DN as described in clause 5.6.6, the DN-AAA server may, as part of authorization data, provide the SMF with a list of allowed MAC addresses for this PDU Session; the list is limited to a maximum of 16 MAC addresses. When the list has been provided for a PDU Session, the SMF sets corresponding filtering rules in the UPF(s) acting as PDU Session Anchor for the PDU Session. The UPF discards any UL traffic that does not contain one of these MAC addresses as a source address if the list of allowed MAC addresses is provided. In this Release of specification, the PDU Session of Ethernet PDU Session type is restricted to SSC mode 1 and SSC mode 2. For a PDU Session established with the Ethernet PDU Session type, the SMF may, upon PCF request, need to ensure reporting to the PCF of all Ethernet MAC addresses used as UE address in a PDU Session. In this case, as defined in clause 5.8.2.12, the SMF controls the UPF to report the different MAC addresses used as source address of frames sent UL by the UE in the PDU Session. NOTE 11: This relates to whether AF control on a per MAC address is allowed on the PDU Session as defined in clause 6.1.1.2 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]. The PCF may activate or deactivate the reporting of the UE MAC address using the "UE MAC address change" Policy Control Request Trigger as defined in Table 6.1.3.5-1 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]. The SMF may relocate the UPF acting as the PDU Session Anchor for an Ethernet PDU Session as defined in clause 4.3.5.8 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. The relocation may be triggered by a mobility event such as a handover, or may be triggered independent of UE mobility, e.g. due to load balancing reasons. In order to relocate the PSA UPF, the reporting of the UE MAC addresses needs to be activated by the SMF. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.6.10.2 |
5,888 | 4.3.2b Authentication Procedure used for a GSM authentication challenge | The purpose of the authentication procedure is twofold (see 3GPP TS 43.020[ Security related network functions ] [13]): First to permit the network to check whether the identity provided by the mobile station is acceptable or not; Second to provide parameters enabling the mobile station to calculate a new GSM ciphering key. The cases where the authentication procedure should be used are defined in 3GPP TS 42.009[ Security aspects ] [5]. The authentication procedure is always initiated and controlled by the network. GSM authentication challenge shall be supported by a ME supporting GERAN or UTRAN. A GSM security context is established in the MS and the network when a GSM authentication challenge is performed in A/Gb mode or in Iu mode. However, in Iu mode the MS shall not accept a GSM authentication challenge, if a USIM is inserted. After a successful GSM authentication, the GSM ciphering key and the ciphering key sequence number, are stored both in the network and the MS. | 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.2b |
5,889 | 10.1.3.6 Mapping to physical resources | Each NPUSCH codeword can be mapped to one or more than one resource units, , as given by clause 16.5.1.2 of TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [4], each of which shall be transmitted times. The block of complex-valued symbols shall be multiplied with the amplitude scaling factor in order to conform to the transmit power specified in [4], and mapped in sequence starting with to subcarriers assigned for transmission of NPUSCH. The mapping to resource elements corresponding to the subcarriers assigned for transmission and not used for transmission of reference signals, shall be in increasing order of first the index , then the index, starting with the first slot in the assigned resource unit. After mapping to slots, the slots shall be repeated additional times, before continuing the mapping of to the following slot, where For NPUSCH Format 1 and 2 on frame structure type 2 with , - the NPUSCH transmission is carried out in the first set of slots spanning over two contiguous uplink subframes not overlapping with any uplink subframe configured as invalid; - for TDD configuration 1 and 4, if the starting position for the NPUSCH is indicated as the second of the two contiguous uplink subframes, the NPUSCH transmission is postponed until the start of two consecutive uplink subframes. If a mapping to slots or a repetition of the mapping contains a resource element which overlaps with - any configured NPRACH resource according to nprach-ParametersList in SystemInformationBlockType2-NB, or - any configured NPRACH resource according to nprach-ParametersList given by ul-ConfigList in SystemInformationBlockType22-NB and if the UE indicates multiCarrier-NPRACH as supported, or - any configured NPRACH resource according to nprach-ParametersList given by ul-ConfigListMixed in SystemInformationBlockType22-NB and if the UE indicates multiCarrier-NPRACH and mixedOperationMode as supported, or - any configured NPRACH resource according to nprach-ParametersListFmt2 in SystemInformationBlockType2-NB and if the UE indicates nprach-Format2 as supported, or - any configured NPRACH resource according to nprach-ParametersListFmt2 given by ul-ConfigList in SystemInformationBlockType23-NB and if the UE indicates multiCarrier-NPRACH and nprach-Format2 as supported, or - any configured NPRACH resource according to nprach-ParametersListFmt2 given by ul-ConfigListMixed in SystemInformationBlockType23-NB and if the UE indicates multiCarrier-NPRACH, mixedOperationMode and nprach-Format2 as supported, or - any configured NPRACH resource according to nprach-ParametersListTDD in SystemInformationBlockType2-NB, or - any configured NPRACH resource according to nprach-ParametersListTDD in SystemInformationBlockType22-NB and if the UE indicates multiCarrier-NPRACH as supported, or - any configured NPRACH resource configured for Early Data Transmission and if the NPUSCH transmission is during an Early Data Transmission procedure [12, Clause 7.3b], then, - for the NPUSCH transmission in overlapped slots is postponed until the next slots not overlapping with any configured NPRACH resource. - for the NPUSCH transmission in overlapped slots is postponed until the next slots starting with the first slot satisfying and not overlapping with any configured NPRACH resource. NPRACH gaps as defined in clause 10.1.6.1 are not part of the NPRACH resource. For frame structure type 2, the valid uplink subframes which are not used for NPRACH transmission when it is not possible to map G symbol groups back-to-back are not part of the NPRACH resource. The mapping of is then repeated until slots have been transmitted. After transmissions and/or postponements due to NPRACH of time units, for frame structure type 1, a gap of time units shall be inserted where the NPUSCH transmission is postponed. The portion of a postponement due to NPRACH which coincides with a gap is counted as part of the gap. When higher layer parameter npusch-AllSymbols is set to false, resource elements in SC-FDMA symbols overlapping with a symbol configured with SRS according to srs-SubframeConfig shall be counted in the NPUSCH mapping but not used for transmission of the NPUSCH. When higher layer parameter npusch-AllSymbols is set to true, all symbols are transmitted. If higher layer parameter resourceReservationConfigUL is configured, then in case of NPUSCH format 1 transmission associated with C-RNTI or SPS C-RNTI using UE-specific NPDCCH search space with the Resource reservation field in the DCI set to 1 including NPUSCH format 1 transmission without a corresponding NPDCCH, or in case of NPUSCH format 2 transmission associated with C-RNTI using UE-specific NPDCCH search space, - In a subframe for or a slot for that is overlapping with any fully reserved uplink subframe as defined in clause 16.5 in [4], - for , the NPUSCH transmission is postponed until the next NB-IoT uplink subframe that is not fully reserved. - for , the NPUSCH transmission in the slot is postponed until the next slot spanning over two contiguous uplink subframes not overlapping with any uplink subframe that is fully reserved. - In a subframe for or a slot for that is not overlapping with any fully reserved uplink subframe, any SC-FDMA symbols overlapping with reserved symbols shall be counted in the NPUSCH mapping but not used for transmission of the NPUSCH. For a UE communicating over NTN, after transmissions (and/or postponements due to NPRACH) of time units, for frame structure type 1, a transmission gap of time units shall be counted for the NPUSCH resource mapping but not used for transmission of the NPUSCH according to the UE capability ntn-SegmentedPrecompensationGaps-r17 as specified in 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [9]. The quantity is provided by higher layers, and the quantity of is configured by higher layers based on the UE capability if signalled. | 3GPP TS 36.211 | Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation | RAN1 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 10.1.3.6 |
5,890 | 5.6.4 Single PDU Session with multiple PDU Session Anchors 5.6.4.1 General | In order to support selective traffic routing to the DN or to support SSC mode 3 as defined in clause 5.6.9.2.3, the SMF may control the data path of a PDU Session so that the PDU Session may simultaneously correspond to multiple N6 interfaces. The UPF that terminates each of these interfaces is said to support PDU Session Anchor functionality. Each PDU Session Anchor supporting a PDU Session provides a different access to the same DN. Further, the PDU Session Anchor assigned at PDU Session Establishment is associated with the SSC mode of the PDU Session and the additional PDU Session Anchor(s) assigned within the same PDU Session e.g. for selective traffic routing to the DN are independent of the SSC mode of the PDU Session. When a PCC rule including the Application Function influence on traffic routing Enforcement Control information defined in clause 6.3.1 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45] is provided to the SMF, the SMF can decide whether to apply traffic routing (by using UL Classifier functionality or IPv6 multi-homing) based on DNAI(s) included in the PCC rule. NOTE 1: Application Function influence on traffic routing Enforcement Control information can be either determined by the PCF when requested by AF via NEF as described in clause 5.6.7.1 or statically pre-configured in the PCF. NOTE 2: Selective traffic routing to the DN supports, for example, deployments where some selected traffic is forwarded on an N6 interface to the DN that is "close" to the AN serving the UE. This may correspond to - The Usage of UL Classifier functionality for a PDU Session defined in clause 5.6.4.2. - The Usage of an IPv6 multi-homing for a PDU Session defined in clause 5.6.4.3. SMF may also take decision to apply traffic routing (by using UL Classifier functionality or IPv6 multi-homing) in EAS Discovery with EASDF procedure described in TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [130]. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.6.4 |
5,891 | 9.11.2.9 S1 mode to N1 mode NAS transparent container | The purpose of the S1 mode to N1 mode NAS transparent container information element is to provide the UE with parameters that enable the UE to create a mapped 5G NAS security context and take this context into use after inter-system change to N1 mode in 5GMM-CONNECTED mode. The S1 mode to N1 mode NAS transparent container information element is coded as shown in figure 9.11.2.9.1 and table 9.11.2.9.1. The S1 mode to N1 mode NAS transparent container is a type 4 information element with a length of 10 octets. The value part of the S1 mode to N1 mode NAS transparent container information element is included in specific information elements within some RRC messages sent to the UE. NOTE: For these cases the coding of the information element identifier and length information of RRC is defined in 3GPP TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [30]. Figure 9.11.2.9.1: S1 mode to N1 mode NAS transparent container information element Table 9.11.2.9.1: S1 mode to N1 mode NAS transparent container 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.2.9 |
5,892 | 5.3.5 RRC reconfiguration 5.3.5.1 General | Figure 5.3.5.1-1: RRC reconfiguration, successful Figure 5.3.5.1-2: RRC reconfiguration, failure The purpose of this procedure is to modify an RRC connection, e.g. to establish/modify/release RBs/BH RLC channels/Uu Relay RLC channels/PC5 Relay RLC channels, to perform reconfiguration with sync, to setup/modify/release measurements, to add/modify/release SCells and cell groups, to add/modify/release conditional handover configuration, to add/modify/release conditional PSCell change or conditional PSCell addition configuration, to add/modify/release LTM configuration. As part of the procedure, NAS dedicated information may be transferred from the Network to the UE. RRC reconfiguration to perform reconfiguration with sync includes, but is not limited to, the following cases: - reconfiguration with sync and security key refresh, involving RA to the PCell/PSCell, MAC reset, refresh of security and re-establishment of RLC and PDCP triggered by explicit indicators; - reconfiguration with sync but without security key refresh, involving RA to the PCell/PSCell, MAC reset and RLC re-establishment and PDCP data recovery (for AM DRB or AM MRB) triggered by explicit indicators. - reconfiguration with sync for DAPS and security key refresh, involving RA to the target PCell, establishment of target MAC, and - for non-DAPS bearer: refresh of security and re-establishment of RLC and PDCP triggered by explicit indicators; - for DAPS bearer: establishment of RLC for the target PCell, refresh of security and reconfiguration of PDCP to add the ciphering function, the integrity protection function and ROHC function of the target PCell; - for SRB: refresh of security and establishment of RLC and PDCP for the target PCell; - reconfiguration with sync for DAPS but without security key refresh, involving RA to the target PCell, establishment of target MAC, and - for non-DAPS bearer: RLC re-establishment and PDCP data recovery (for AM DRB or AM MRB) triggered by explicit indicators. - for DAPS bearer: establishment of RLC for target PCell, reconfiguration of PDCP to add the ciphering function, the integrity protection function and ROHC function of the target PCell; - for SRB: establishment of RLC and PDCP for the target PCell. - reconfiguration with sync for direct-to-indirect path switch, not involving RA at target side, involving re-establishment of PDCP /PDCP data recovery (for AM DRB) triggered by explicit indicators, and - reconfiguration with sync for LTM cell switch (without security key refresh), and - involving or not involving RA to the target LTM candidate SpCell according to a network indication; - MAC reset; - depending on a network indication, re-establishment of RLC and PDCP data recovery (for AM DRB). - reconfiguration with sync for LTM cell switch (without security key refresh), and - involving or not involving RA to the target LTM candidate SpCell according to a network indication; - MAC reset; - depending on a network indication, no re-establishment of RLC. In (NG)EN-DC and NR-DC, SRB3 can be used for measurement configuration and reporting, for UE assistance (re-)configuration and reporting for power savings, for IP address (re-)configuration and reporting for IAB-nodes, to (re-)configure MAC, RLC, BAP, physical layer and RLF timers and constants of the SCG configuration, to reconfigure PDCP for DRBs associated with the S-KgNB or SRB3, to reconfigure SDAP for DRBs associated with S-KgNB in NGEN-DC and NR-DC, to add/modify/release conditional PSCell change configuration, and (re-)configure the LTM configuration associated with the SCG (only in NR-DC), provided that the (re-)configuration does not require any MN involvement, and to transmit RRC messages between the MN and the UE during fast MCG link recovery. In (NG)EN-DC and NR-DC, only measConfig, radioBearerConfig, conditionalReconfiguration, ltm-Config (only in NR-DC), bap-Config, iab-IP-AddressConfigurationList, otherConfig, appLayerMeasConfig and/or secondaryCellGroup are included in RRCReconfiguration received via SRB3, except when RRCReconfiguration is received within DLInformationTransferMRDC. When a clause of 5.3.5 is executed due to an LTM cell switch execution (i.e., as specified in 5.3.5.18.6) or due to a conditional reconfiguration execution for subsequent CPAC (i.e., as specified in 5.3.5.13.8), every appearance of "the received" before RRCReconfiguration, before a field name, or before an IE name, refers to the RRCReconfiguration, to the field name or to the IE, respectively, that was generated and stored by the UE as specified in 5.3.5.18.6 or 5.3.5.13.8. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.5 |
5,893 | 6.5.2.1 Error Vector Magnitude | The Error Vector Magnitude is a measure of the difference between the reference waveform and the measured waveform. This difference is called the error vector. Before calculating the EVM the measured waveform is corrected by the sample timing offset and RF frequency offset. Then the carrier leakage shall be removed from the measured waveform before calculating the EVM. The measured waveform is further modified by selecting the absolute phase and absolute amplitude of the Tx chain. The EVM result is defined after the front-end IDFT as the square root of the ratio of the mean error vector power to the mean reference power expressed as a %. The basic EVM measurement interval in the time domain is one preamble sequence for the PRACH, and as specified in Table 6.5.2.1-1 for the PUCCH and PUSCH in the time domain. When the PUSCH or PUCCH transmission slot or subslot is shortened due to multiplexing with SRS, the EVM measurement interval is reduced by one symbol, accordingly. Likewise, when the PUSCH starting position is modified or when second last symbol is the ending symbol of the PUSCH subframe for Frame Structure Type 3, the EVM measurement interval is reduced accordingly. The PUSCH or PUCCH EVM measurement interval is also reduced when the mean power, modulation or allocation between slots or subslots is expected to change. In the case of PUSCH transmission, the measurement interval is reduced by a time interval equal to the sum of 5 μs and the applicable exclusion period defined in subclause 6.3.4, adjacent to the boundary where the power change is expected to occur. The PUSCH exclusion period is applied to the signal obtained after the front-end IDFT. In the case of PUCCH transmission with power change, the PUCCH EVM measurement interval is reduced by one symbol adjacent to the boundary where the power change is expected to occur. Table 6.5.2.1-1: Measurement interval for EVM | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.5.2.1 |
5,894 | 9.3.3.1.2 TDD | For the parameters specified in Table 9.3.3.1.2-1, and using the downlink physical channels specified in Annex C.3.2, the minimum requirements are specified in Table 9.3.3.1.2-2 and by the following a) a sub-band differential CQI offset level of +2 shall be reported at least % for at least one of the sub-bands of full size at the channel edges; b) the ratio of the throughput obtained when transmitting on a randomly selected sub-band among the sub-bands with the highest differential CQI offset level the corresponding TBS and that obtained when transmitting the TBS indicated by the reported wideband CQI median on a randomly selected sub-band in set S shall be ≥ ; The requirements only apply for sub-bands of full size and the random scheduling across the sub-bands is done by selecting a new sub-band in each TTI for FDD, each available downlink transmission instance for TDD. Sub-bands of a size smaller than full size are excluded from the test. Table 9.3.3.1.2-1 Sub-band test for single antenna transmission (TDD) Table 9.3.3.1.2-2 Minimum requirement (TDD) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 9.3.3.1.2 |
5,895 | 5.2.5.4 Npcf_SMPolicyControl service 5.2.5.4.1 General | Service description: NF Service Consumer, e.g. SMF, can create and manage a SM Policy Association in the PCF through which the NF Service Consumer receives policy information for a PDU Session. As part of this service, the PCF may provide the NF Service Consumer, e.g. SMF, with policy information for the PDU Session that may contain: - PDU Session related policy information as defined in clause 6.4 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. - PCC rule information as defined in clause 6.3 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. - Policy Control Request Trigger information i.e. a set of Policy Control Request Trigger(s) as defined in clause 6.1.3.5 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. At PDU Session establishment the NF Service Consumer, e.g. SMF, requests the creation of a corresponding SM Policy Association with the PCF (Npcf_SMPolicyControl_Create) and provides relevant parameters about the PDU Session to the PCF. When the PCF has created the SM Policy Association, the PCF may provide policy information for the PDU Session in the response. When a Policy Control Request Trigger condition is met the NF Service Consumer, e.g. SMF requests the update(Npcf_SMPolicyControl_Update) of the SM Policy Association by providing information on the condition(s) that have been met as defined in clause 6.1.3.5 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. The PCF may provide updated policy information for the PDU Session to the NF Service Consumer in the response. The PCF may at any time provide updated policy information for the (Npcf_SMPolicyControl_UpdateNotify). At PDU Session Release the NF Service Consumer, e.g. SMF requests the deletion of the corresponding SM Policy Association (Npcf_SMPolicyControl_Delete). | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.5.4 |
5,896 | 4.15.6.7.2 Service specific parameter provisioning by AF to HPLMN | Figure 4.15.6.7.2-1 shows procedure for service specific parameter provisioning. The AF uses Nnef_ServiceParameter service to provide the service specific parameters to the HPLMN and the UE. In the roaming case, PCF is replaced by H-PCF, the AMF interacts with the V-PCF which interacts with H-PCF. Figure 4.15.6.7.2-1: Service specific information provisioning by AF to HPLMN 0a. The AMF establishes UE Policy Association as specified in clause 4.16.11. 0b. PCF requests notifications from the UDR on changes in UE policy information. 1. To create a new request, the AF invokes an Nnef_ServiceParameter_Create service operation. The request may include subscription information to the report of the outcome of UE Policy delivery. To update or remove an existing request, the AF invokes an Nnef_ServiceParameter_Update or Nnef_ServiceParameter_Delete service operation together with the corresponding Transaction Reference ID which was provided to the AF in Nnef_ServiceParameter_Create response message. The content of this service operation (AF request) includes the information described in clause 5.2.6.11. 2. The AF sends its request to the NEF. The NEF authorizes the AF request. The NEF performs the following mappings: - Map the AF-Service-Identifier into DNN and S-NSSAI combination, determined by local configuration. - Map the External Application Identifier into the corresponding Application Identifier known in the core network. 2a. The NEF may invoke Nudm_SDM_Get service operation to perform the following mappings: - Map the GPSI in Target UE Identifier into SUPI, according to information received from UDM. - Map the External Group Identifier in Target UE Identifier into Internal Group Identifier, according to information received from UDM. If the AF subscribed to the outcome of UE Policy delivery, the AF indicates where the AF receives the corresponding notifications. (in the case of Nnef_ServiceParameter_Create): The NEF assigns a Transaction Reference ID to the Nnef_ServiceParameter_Create request. 2b. (in the case of Nnef_ServiceParameter_Create or Update): The NEF may need to authorize the service specific parameter provisioning request with the UDM by sending a Nudm_ServiceSpecificAuthorisation_Create service operation as defined in clause 4.15.6.7a. NOTE 2: The NEF skips the mapping of GPSI or External Group Identifier in step 2a if it needs to authorize the service specific parameter provisioning request with the UDM as the response of the authorization request from UDM includes the SUPI or Internal Group Identifier. (in the case of Nnef_ServiceParameter_delete): The NEF requests the UDM to remove the authorization of the service specific parameters provisioned by sending a Nudm_ServiceSpecificAuthorisation_Remove service operation. 3. (in the case of Nnef_ServiceParameter_Create or Update): The NEF stores the AF request information in the UDR as the "Application Data" (Data Subset setting to "Service specific information") together with the assigned Transaction Reference ID. (in the case of Nnef_ServiceParameter_delete): The NEF deletes the AF request information from the UDR. 4. The NEF responds to the AF. In the case of Nnef_ServiceParameter_Create response message, the response message includes the assigned Transaction Reference ID. If the UE is registered to the network and the PCF performs the subscription to notification to the data modified in the UDR by invoking Nudr_DM_Subscribe (AF service parameter provisioning information, SUPI, Data Set setting to "Application Data", Data Subset setting to "Service specific information") at step 0, the following steps are performed: 5. The PCF(s) receive(s) a Nudr_DM_Notify notification of data change from the UDR. NOTE 3: PCF does not have to subscribe for each UE the application specific information, e.g. if PCF has already received the application specific information for a group of UE or for a DNN by a subscription of other UE. The same application specific information is delivered to every UE in a group or a DNN. For PIN service, PCF generates the URSP rules with PIN ID in the Traffic Descriptor as specified in Table 6.6.2.1-2 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. 6. The PCF initiates UE Policy delivery as specified in clause 4.2.4.3. 7. If the AF subscribed to notifications about the outcome of UE Policies delivery due to Service specific parameter provisioning and the PCF is notified of UE Policy Container from the AMF, the PCF notifies the UE Policy delivery result contained in the UE Policy container as the outcome of the procedure to NEF by sending Npcf_EventExposure_Notify including the SUPI, the list of GPSI(s) if available, and if provided in the step 2a, the Internal-Group-Id. If the PCF is notified about UE Policy delivery failure from the AMF due to UE not reachable, the PCF may determine to retry step 6 of this procedure when the UE becomes reachable. In such a case, the PCF may report the interim status i.e. UE is temporarily unreachable as the outcome of the procedure to NEF by sending Npcf_EventExposoure_Notify. If the PCF determines the failure of the UE Policies delivery procedure, the PCF notifies the failure with an appropriate cause such as UE is unreachable as the outcome of the procedure to NEF by sending Npcf_EventExposure_Notify. If the PCF determines that it cannot yet deliver URSP Rules that are based on the service parameters from the AF, then the PCF may report in the interim status that URSP Rules have not yet been delivered by the PCF as the outcome of the procedure to NEF by sending Npcf_EventExposure_Notify. The content of event reporting in this step is described in clause 6.1.3.18 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. 8. When the NEF receives Npcf_EventExposure_Notify, the NEF performs information mapping (e.g. AF Transaction Internal ID provided in Notification Correlation ID to AF Transaction ID, SUPI to GPSI, Internal-Group-Id to External-Group-Id, etc.) and triggers the appropriate Nnef_ServiceParameter_Notify message. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.15.6.7.2 |
5,897 | 4.2.7.4 Additional User Location Information with Mobile Base Station Relay (MBSR) | As described in clause 5.35A of TS 23.501[ System architecture for the 5G System (5GS) ] [2], when a UE is being served by an MBSR, for any N2 messages sent by NG-RAN to AMF, if the User Location Information is included, the N2 parameters shall also include the additional ULI of this MBSR. When the AMF provides user location information to other NFs (e.g. LMF as specified in clause 5.9 of TS 23.273[ 5G System (5GS) Location Services (LCS); Stage 2 ] [51]) for a UE connected via MBSR, the AMF may also send the Additional ULI received via N2 messages. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.2.7.4 |
5,898 | 5.6.2.4 Paging for SMS | The network shall initiate the paging procedure when it receives an incoming mobile terminating SMS to the UE if the UE is: 1) IMSI attached for non-EPS services or for "SMS only"; or 2) attached for EPS services with CIoT EPS optimization and the UE has requested "SMS only" and the UE is in NB-S1 mode, - no NAS signalling connection exists. - there is no paging restriction applied in the network. For the UE using eDRX, the network initiates the paging procedure when an incoming mobile terminating SMS is received within the paging time window. If an incoming mobile terminating SMS is received outside the paging time window and the eDRX value that the network provides to the UE in the Extended DRX parameters IE during the last attach procedure or the last tracking area updating procedure is not all zeros (i.e. the E-UTRAN eDRX cycle length duration is higher than 5.12 seconds), the network initiates the paging procedure at T time ahead of the beginning of the next paging time window. NOTE: T time is a short time period based on implementation. The operator can take possible imperfections in the synchronization between the CN and the UE into account when choosing T time. To initiate the procedure for SMS when no NAS signalling connection exists, the EMM entity in the network requests the lower layer to start paging (see 3GPP TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [23]). The paging message shall include a CN domain indicator set to "PS". If the paging message includes a UE Paging Identity set to the UE's S-TMSI, the paging procedure is performed according to clause 5.6.2.2.1. If the paging message includes a UE Paging Identity set to the UE's IMSI, the paging procedure is performed according to clause 5.6.2.2.2. The MME shall not start timers T3413 and T3415 for this procedure. If the negotiated UE paging probability information is available in the EMM context of the UE, the EMM entity shall provide the lower layer with the negotiated UE paging probability information (see 3GPP TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [20], 3GPP TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [23]). | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.6.2.4 |
5,899 | 5.3 Physical uplink shared channel | The baseband signal representing the physical uplink shared channel is defined in terms of the following steps: - scrambling - modulation of scrambled bits to generate complex-valued symbols - mapping of the complex-valued modulation symbols onto one or several transmission layers - transform precoding to generate complex-valued symbols - precoding of the complex-valued symbols - mapping of precoded complex-valued symbols to resource elements - generation of complex-valued time-domain SC-FDMA signal for each antenna port Figure 5.3-1: Overview of uplink physical channel processing | 3GPP TS 36.211 | Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation | RAN1 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 5.3 |
5,900 | 5.6.9.2.1 SSC Mode 1 | For a PDU Session of SSC mode 1, the UPF acting as PDU Session Anchor at the establishment of the PDU Session is maintained regardless of the access technology (e.g. Access Type and cells) a UE is successively using to access the network. In the case of a PDU Session of IPv4 or IPv6 or IPv4v6 type, IP continuity is supported regardless of UE mobility events. In this Release of the specification, when IPv6 multihoming or UL CL applies to a PDU Session of in SSC mode 1, and the network allocates (based on local policies) additional PDU Session Anchors to such a PDU Session, these additional PDU Session Anchors may be released or allocated, and the UE does not expect that the additional IPv6 prefix is maintained during the lifetime of PDU Session. SSC mode 1 may apply to any PDU Session type and to any access type. A UE supporting PDU Connectivity shall support SSC mode 1. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.6.9.2.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.