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
⌀ |
|---|---|---|---|---|---|---|---|
1,801 | 6.41.2.5 UE Discovery, Selection and Access | Subject to operator’s policy and agreement between a 3rd party service provider and operator, the 5G system shall enable a UE to receive and use configuration provided by a 3rd party service provider to discover and access a hosting network and localized services, including the considerations of prior service agreement with a 3rd party service provider and no prior subscription to hosting network. If the UE is able to obtain services from two networks simultaneously, it may additionally select the hosting network. If the UE cannot maintain the connection to the home network while selecting the hosting network, the selection shall only be done on request by the user, i.e., using manual selection. The 5G system shall support secure means for a UE to select and access localized services which may be provided by a 3rd party service provider via a hosting network, independent of prior subscription to the hosting network or 3rd party service provider. The 5G system shall enable the home network to allow a UE to automatically select a hosting network for accessing localized services when specified conditions (e.g., predefined time, location) are fulfilled. The 5G system shall be able to prevent a UE to re-access the hosting network after the localized services were terminated if the authorization for the localized services is no longer valid (e.g., can be based on certain conditions such as time or location of the user). The 5G system may support means for a UE which may or may not have prior subscription to the hosting network to display human readable information on how to gain access to the hosting network and available 3rd party services. The 5G system shall support a mechanism to allow a user to manually select a specific local hosting network. NOTE: Additional information can be presented to the user to facilitate the manual network selection. The 5G system shall be able to limit access of specific UEs to a configurable area of a hosting network's coverage area. The 5G system shall be able to maintain privacy of a user against the hosting network while the UE does not make use of the hosting network, for example, to prevent tracking of UEs by hosting networks. The 5G system shall enable the home network to instruct a UE to select a hosting network with certain conditions (e.g., predefined time, location) based on the request from a service provider. The 5G system shall enable the home network to allow a UE to select a hosting network or change to another hosting network, without any additional user intervention as long as the delivered services, both localized services and home routed services, are unchanged. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.41.2.5 |
1,802 | 5.2.2.4 Namf_MT service 5.2.2.4.1 General | Service description: It provides a NF the service to request information related to capabilities that make sure UE is reachable to send MT signalling or data to a target UE or toward UEs in a multicast session. The following are the key functionalities of this NF service - paging UE if UE is in IDLE state and respond other NF after the UE enters CM-CONNECTED state. - response to the requester NF if UE is in CONNECTED state. - providing the terminating domain selection information for IMS voice to the consumer NF. - requesting paging towards a group of UEs as defined in TS 23.247[ Architectural enhancements for 5G multicast-broadcast services ] [78]. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.2.4 |
1,803 | 8.106 Node Number | Node Number shall be coded as depicted in Figure 8.106-1. Figure 8.106-1: Node Number The Node number shall carry an ISDN number. If the Node Number carries the SGSN Number, then the SGSN number shall be coded according to the contents of ISDN-AddressString data type defined in 3GPP TS 29.002[ Mobile Application Part (MAP) specification ] [41]. The SGSN Number shall be in international format and the "nature of address indicator" shall indicate "international number". The SGSN Number is defined in 3GPP TS 23.003[ Numbering, addressing and identification ] [2]. The Length of Node Number shall not be zero. If the Node Number carries the MME number for MT SMS, then it shall be coded according to the contents of ISDN-AddressString data type defined in 3GPP TS 29.002[ Mobile Application Part (MAP) specification ] [41]. The MME number for MT SMS shall be in international format and the "nature of address indicator" shall indicate "international number". The MME number for MT SMS is defined in 3GPP TS 23.003[ Numbering, addressing and identification ] [2]. The Length of Node Number shall not be zero. If the Node Number carries the MSC Number, then the MSC number shall be coded according to the contents of ISDN-AddressString data type defined in 3GPP TS 29.002[ Mobile Application Part (MAP) specification ] [41]. The MSC Number shall be in international format and the "nature of address indicator" shall indicate "international number". The MSC Number is defined in 3GPP TS 23.003[ Numbering, addressing and identification ] [2]. The Length of Node Number shall not be zero. | 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.106 |
1,804 | 7B.5 Subscriber privacy for wireline access | The requirements and procedures on the UE related to subscriber privacy in clauses 5.2.5, 6.12 and Annex C are applicable for the 5G-RG. NOTE 1: The requirements and procedures on the UE related to subscriber privacy in clauses 5.2.5, 6.12 and Annex C are not applicable for the FG-RG. NOTE 2: When the SUPI contains a GCI, the 5G-CRG can use the null scheme to construct the SUCI. For a W-AGF representing an FN-RG, the null scheme shall be used to construct the SUCI as described in clauses 4.7.3 and 4.7.4 in TS 23.316[ Wireless and wireline convergence access support for the 5G System (5GS) ] [79]. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 7B.5 |
1,805 | – BWP-UplinkDedicated | The IE BWP-UplinkDedicated is used to configure the dedicated (UE specific) parameters of an uplink BWP. BWP-UplinkDedicated information element -- ASN1START -- TAG-BWP-UPLINKDEDICATED-START BWP-UplinkDedicated ::= SEQUENCE { pucch-Config SetupRelease { PUCCH-Config } OPTIONAL, -- Need M pusch-Config SetupRelease { PUSCH-Config } OPTIONAL, -- Need M configuredGrantConfig SetupRelease { ConfiguredGrantConfig } OPTIONAL, -- Need M srs-Config SetupRelease { SRS-Config } OPTIONAL, -- Need M beamFailureRecoveryConfig SetupRelease { BeamFailureRecoveryConfig } OPTIONAL, -- Cond SpCellOnly ..., [[ sl-PUCCH-Config-r16 SetupRelease { PUCCH-Config } OPTIONAL, -- Need M cp-ExtensionC2-r16 INTEGER (1..28) OPTIONAL, -- Need R cp-ExtensionC3-r16 INTEGER (1..28) OPTIONAL, -- Need R useInterlacePUCCH-PUSCH-r16 ENUMERATED {enabled} OPTIONAL, -- Need R pucch-ConfigurationList-r16 SetupRelease { PUCCH-ConfigurationList-r16 } OPTIONAL, -- Need M lbt-FailureRecoveryConfig-r16 SetupRelease { LBT-FailureRecoveryConfig-r16 } OPTIONAL, -- Need M configuredGrantConfigToAddModList-r16 ConfiguredGrantConfigToAddModList-r16 OPTIONAL, -- Need N configuredGrantConfigToReleaseList-r16 ConfiguredGrantConfigToReleaseList-r16 OPTIONAL, -- Need N configuredGrantConfigType2DeactivationStateList-r16 ConfiguredGrantConfigType2DeactivationStateList-r16 OPTIONAL -- Need R ]], [[ ul-TCI-StateList-r17 CHOICE { explicitlist SEQUENCE { ul-TCI-ToAddModList-r17 SEQUENCE (SIZE (1..maxUL-TCI-r17)) OF TCI-UL-State-r17 OPTIONAL, -- Need N ul-TCI-ToReleaseList-r17 SEQUENCE (SIZE (1..maxUL-TCI-r17)) OF TCI-UL-StateId-r17 OPTIONAL -- Need N }, unifiedTCI-StateRef-r17 ServingCellAndBWP-Id-r17 } OPTIONAL, -- Need R ul-powerControl-r17 Uplink-powerControlId-r17 OPTIONAL, -- Cond NoTCI-PC pucch-ConfigurationListMulticast1-r17 SetupRelease { PUCCH-ConfigurationList-r16 } OPTIONAL, -- Need M pucch-ConfigurationListMulticast2-r17 SetupRelease { PUCCH-ConfigurationList-r16 } OPTIONAL -- Need M ]], [[ pucch-ConfigMulticast1-r17 SetupRelease { PUCCH-Config } OPTIONAL, -- Need M pucch-ConfigMulticast2-r17 SetupRelease { PUCCH-Config } OPTIONAL -- Need M ]], [[ pathlossReferenceRSToAddModList-r17 SEQUENCE (SIZE (1..maxNrofPathlossReferenceRSs-r17)) OF PathlossReferenceRS-r17 OPTIONAL, -- Need N pathlossReferenceRSToReleaseList-r17 SEQUENCE (SIZE (1..maxNrofPathlossReferenceRSs-r17)) OF PathlossReferenceRS-Id-r17 OPTIONAL -- Need N ]] } ConfiguredGrantConfigToAddModList-r16 ::= SEQUENCE (SIZE (1..maxNrofConfiguredGrantConfig-r16)) OF ConfiguredGrantConfig ConfiguredGrantConfigToReleaseList-r16 ::= SEQUENCE (SIZE (1..maxNrofConfiguredGrantConfig-r16)) OF ConfiguredGrantConfigIndex-r16 ConfiguredGrantConfigType2DeactivationState-r16 ::= SEQUENCE (SIZE (1..maxNrofConfiguredGrantConfig-r16)) OF ConfiguredGrantConfigIndex-r16 ConfiguredGrantConfigType2DeactivationStateList-r16 ::= SEQUENCE (SIZE (1..maxNrofCG-Type2DeactivationState)) OF ConfiguredGrantConfigType2DeactivationState-r16 -- TAG-BWP-UPLINKDEDICATED-STOP -- ASN1STOP NOTE 1: In case of RRCReconfiguration with reconfigurationWithSync, the UE performs a MAC reset, which involves releasing the PUCCH-CSI/SRS/SR configuration in accordance with clause 5.3.12 and TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3], clauses 5.12 and 5.2. Hence, for these parts of the dedicated radio resource configuration, delta signalling is not supported in the message when reconfigurationWithSync is included. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
1,806 | 5.21.3.4 Reliability of NF Services | When multiple NF Service instances within a NF Service Set are exposed to the NF Service consumer or SCP and the failure of NF Service instance is detected or notified by the NRF, i.e. it is not available anymore, the NF Service consumer or SCP selects another NF Service instance of the same NF Service Set within the NF instance, if available. Otherwise the NF Service consumer or SCP selects a different NF instance within the same NF Set. NOTE: The NF Producer instance can change the NF Service instance in the response to the service request. When multiple NF Service instances within a NF Service Set are exposed to the NF Service consumer or SCP as a single NF Service, the reliability, i.e. the selection of an alternative NF Service instance is handled within the NF instance. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.21.3.4 |
1,807 | 6.5.2A.3.1 Minimum requirement for CA | For intra-band contiguous carrier aggregation bandwidth class B, C and D, the requirements in Table 6.5.2A.3.1-1 and 6.5.2A.3.1-2 apply within the aggregated transmission bandwidth configuration with both component carrier (s) active and one single contiguous PRB allocation of bandwidth at the edge of the aggregated transmission bandwidth configuration. The inband emission is defined as the interference falling into the non allocated resource blocks for all component carriers. The measurement method for the inband emissions in the component carrier with PRB allocation is specified in annex F. For a non allocated component carrier a spectral measurement is specified. For intra-band non-contiguous carrier aggregation the requirements for in-band emissions should be defined for each component carrier. Requirements only apply with PRB allocation in one of the component carriers according to Table 6.5.2.3.1. Table 6.5.2A.3.1-1: Minimum requirements for in-band emissions (allocated component carrier) Table 6.5.2A.3.1-2: Minimum requirements for in-band emissions (not allocated component carrier) | 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.2A.3.1 |
1,808 | – LTM-CSI-ReportConfig | The IE LTM-CSI-ReportConfig is used to configure report on the cell in which the LTM-CSI-ReportConfig is included. LTM-CSI-ReportConfig information element -- ASN1START -- TAG-LTM-CSI-REPORTCONFIG-START LTM-CSI-ReportConfig-r18 ::= SEQUENCE { ltm-CSI-ReportConfigId-r18 LTM-CSI-ReportConfigId-r18, ltm-ResourcesForChannelMeasurement-r18 LTM-CSI-ResourceConfigId-r18, ltm-ReportConfigType-r18 CHOICE { periodic-r18 SEQUENCE { reportSlotConfig-r18 CSI-ReportPeriodicityAndOffset, pucch-CSI-ResourceList-r18 SEQUENCE (SIZE (1..maxNrofBWPs)) OF PUCCH-CSI-Resource }, semiPersistentOnPUCCH-r18 SEQUENCE { reportSlotConfig-r18 CSI-ReportPeriodicityAndOffset, pucch-CSI-ResourceList-r18 SEQUENCE (SIZE (1..maxNrofBWPs)) OF PUCCH-CSI-Resource }, semiPersistentOnPUSCH-r18 SEQUENCE { reportSlotConfig-r18 CSI-ReportPeriodicityAndOffset, reportSlotOffsetList-r18 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER (0..128), reportSlotOffsetListDCI-0-2-r18 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER (0..128), reportSlotOffsetListDCI-0-1-r18 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER (0..128), p0alpha P0-PUSCH-AlphaSetId }, aperiodic-r18 SEQUENCE { reportSlotOffsetList-r18 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER (0..128), reportSlotOffsetListDCI-0-2-r18 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER (0..128), reportSlotOffsetListDCI-0-1-r18 SEQUENCE (SIZE (1.. maxNrofUL-Allocations-r16)) OF INTEGER (0..128) } }, ltm-ReportContent-r18 LTM-ReportContent-r18, ... } LTM-ReportContent-r18 ::= SEQUENCE { nrOfReportedCells-r18 ENUMERATED {n1,n2,n3,n4}, nrOfReportedRS-PerCell-r18 ENUMERATED {n1,n2,n3,n4}, spCellInclusion-r18 ENUMERATED {true} OPTIONAL -- Need R } -- TAG-LTM-CSI-REPORTCONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
1,809 | 4.13.2 Support of RAT types defined in EPC for satellite access | In the case of satellite access with WB-E-UTRAN, NB-IoT or LTE-M, the RAT Types values "WB-E-UTRAN(LEO)", "WB-E-UTRAN(MEO)", " WB-E-UTRAN(GEO)", " WB-E-UTRAN(OTHERSAT)", "NB-IoT(LEO)", "NB-IoT(MEO)", "NB-IoT(GEO)", "NB-IoT(OTHERSAT)", "LTE-M(LEO)", "LTE-M(MEO)", "LTE-M(GEO)" and "LTE-M(OTHERSAT)" are used in EPC to distinguish the different WB-E-UTRAN, NB-IoT and LTE-M satellite access types. In order to enable efficient enforcement of mobility restrictions: - Cells of each NB-IoT satellite RAT type (NB-IoT(LEO), NB-IoT(MEO), NB-IoT(GEO) or NB-IoT(OTHERSAT)) need to be deployed in TAs that are: - different from TAs for other NB-IoT satellite RAT types; and - different from TAs supporting terrestrial NB-IoT RAT type; and - different from TAs for WB-E-UTRAN satellite RAT types; and - different from TAs for WB-E-UTRAN terrestrial RAT types. The MME may initiate Detach of the UE when an S1 UE Context Release Request is received with Cause indicating the release is requested due to a UE using satellite access moved out of PLMN serving area, as specified in TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [36]. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.13.2 |
1,810 | 5.3.12A Handling of local emergency numbers received via 3GPP access and non-3GPP access 5.3.12A.1 General | The requirements in subclause 5.3.12 with the clarifications and additional conditions in subclause 5.3.12A apply to a UE supporting: - attach procedures (see 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15]) or registration procedures via 3GPP access; and - registration procedures via non-3GPP access. The UE shall ignore the presence or absence of local emergency numbers list, extended local emergency numbers list or both, in a REGISTRATION ACCEPT message received via non-3GPP access and keep the stored local emergency numbers list and the extended local emergency numbers list, if available, unless conditions in subclause 5.3.12A.2 are met. For the purposes of subclause 5.3.12A, the UE is considered neither registered nor attached over 3GPP access if: 1) the UE supports 3GPP access to EPC, the UE does not support 3GPP access to 5GC, and: a) the EMM sublayer is in the EMM-NULL state, EMM-DEREGISTERED state or EMM-DEREGISTERED-INITIATED state; or 2) the UE supports 3GPP access to 5GC, the UE does not support 3GPP access to EPC, and: a) the 5GMM sublayer is in the 5GMM-NULL state, 5GMM-DEREGISTERED state or 5GMM-DEREGISTERED-INITIATED state; or 3) supports both 3GPP access to EPC and 3GPP access to 5GC, and: a) the EMM sublayer is in the EMM-NULL state, EMM-DEREGISTERED state or EMM-DEREGISTERED-INITIATED state; and a) the 5GMM sublayer is in the 5GMM-NULL state, 5GMM-DEREGISTERED state or 5GMM-DEREGISTERED-INITIATED state. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.3.12A |
1,811 | D.3.1 Remote control | Some of the interactions within a plant are conducted by automated control applications similar to those described in clause D.2. Here too, sensor output is requested in a cyclic fashion, and actuator commands are sent via the communication network between a controller and the actuator. Furthermore, there is an emerging need for the control of the plant by personnel on location. Typically, monitoring and managing of distributed control systems takes place in a dedicated control room. Staff deployment to the plant itself occurs, for instance, during construction and commissioning of a plant and in the start-up phase of the processes. In this scenario, the locally deployed staff taps into the same real-time data as provided to the control room. These remote applications require high data rates (~ 100 Mbit/s) since the staff on location needs to view inaccessible locations with high definition (e.g. emergency valves) and since their colleagues in the control room benefit from high-definition footage from body cameras (HD or even 4K). For both kinds of applications, a very high communication service availability is needed (99,9999%). Typically, only a few control loops are fully automated and only handful of control personnel is deployed on location, so that the connection density is rather modest (~ 1000 km-2). | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | D.3.1 |
1,812 | 9.11.4.24 IP header compression configuration | The purpose of the IP header compression configuration information element is to negotiate ROHC channel setup parameters specified in IETF RFC 5795 [39B] and, optionally, provide additional header compression context setup parameters. The IP header compression configuration information element is coded as shown in figure 9.11.4.24.1 and table 9.11.4.24.1. The IP header compression configuration is a type 4 information element with a minimum length of 5 octets and a maximum length of 257 octets. The optional Additional IP header compression parameters container field conveys the additional header compression context setup parameters as specified in 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8] in a generic container. This field corresponds to the profile-specific information in the header of the ROHC IR packet type in IETF RFC 5795 [39B]. Figure 9.11.4.24.1: IP header compression configuration information element Table 9.11.4.24.1: IP header compression configuration information element | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.11.4.24 |
1,813 | 16.10.6.5.1 Service Continuity in RRC_IDLE or RRC_INACTIVE | Mobility procedures for MBS reception allow the UE to start or continue receiving MBS service(s) when changing cells. The gNB may indicate in the MCCH the list of neighbour cells providing the same MBS broadcast service(s) as provided in the serving cell. This allows the UE, e.g., to request unicast reception of the service before moving to a cell not providing the MBS broadcast service(s) using PTM transmission. To avoid the need to read MBS broadcast related system information and potentially MCCH on neighbour frequencies, the UE is made aware of which frequency is providing which MBS broadcast services via PTM, through User Service Description (USD), as defined in TS 26.346[ Multimedia Broadcast/Multicast Service (MBMS); Protocols and codecs ] [46], or the combination of the following: - USD; - SIB21, as defined in clause 7.3.1. NOTE: UE can request unicast reception of the service after moving to a cell not providing the MBS broadcast service(s) using PTM transmission. In RRC_IDLE and RRC_INACTIVE, the UE applies the normal cell reselection rules with the following modifications: - the UE which is receiving or interested to receive MBS broadcast service(s) via PTM and can only receive these MBS broadcast service(s) via PTM while camping on the frequency providing these MBS broadcast service(s) is allowed to make this frequency highest priority when the conditions described in TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [10] are met; - when the MBS broadcast service(s) which the UE is interested in are no longer available (after the end of the session) or the UE is no longer interested in receiving the service(s), the UE no longer prioritises the frequency providing these MBS broadcast service(s). | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.10.6.5.1 |
1,814 | A.13 KAMF to KAMF' derivation in mobility | Derivation of KAMF' from KAMF during mobility shall use the following input parameters. - FC = 0x72 - P0 = DIRECTION - L0 = length of DIRECTION (i.e. 0x00 0x01) - P1 = COUNT, - L1 = length of COUNT (i.e. 0x00 0x04) The input key KEY shall be KAMF. When KAMF' is derived in handover, DIRECTION shall be 0x01 and COUNT shall be the downlink NAS COUNT of the 3GPP access. When KAMF' is derived in idle mode mobility (i.e., mobility registration update), DIRECTION shall be 0x00 and COUNT shall be the uplink NAS COUNT of the 3GPP access used in the Registration Request. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | A.13 |
1,815 | .2 Delete Bearer Response | The Delete Bearer Response shall be sent as a response of Delete Bearer Request. Possible Cause values are specified in Table 8.4-1. Message specific cause values are: - "Request accepted". - "Request accepted partially". - "Context not found". - "Temporarily rejected due to handover/TAU/RAU procedure in progress". Table .2-1: Information Elements in Delete Bearer Response Table .2-2: Bearer Context within Delete Bearer Response Table 7.2.10.2-3: Overload Control Information within Delete Bearer Response | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | .2 |
1,816 | – RRCReject | The RRCReject message is used to reject an RRC connection establishment or an RRC connection resumption. Signalling radio bearer: SRB0 RLC-SAP: TM Logical channel: CCCH Direction: Network to UE RRCReject message -- ASN1START -- TAG-RRCREJECT-START RRCReject ::= SEQUENCE { criticalExtensions CHOICE { rrcReject RRCReject-IEs, criticalExtensionsFuture SEQUENCE {} } } RRCReject-IEs ::= SEQUENCE { waitTime RejectWaitTime OPTIONAL, -- Need N lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension SEQUENCE{} OPTIONAL } -- TAG-RRCREJECT-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
1,817 | 4.3.4.4 Abnormal cases | The following abnormal cases can be identified: a) Lower layer failure If the establishment of an RR connection is unsuccessful, or the RR connection is lost, the IMSI detach is aborted by the mobile station. b) Access barred because of access class control or EAB The signalling procedure for IMSI detach shall not be started. The MS starts the signalling procedure as soon as possible and if still necessary, i.e. when the barred state is removed or because of a cell change, or performs a local detach immediately or after an implementation dependent time. Figure 4.4/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : IMSI detach sequence | 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.4.4 |
1,818 | 3.2 Symbols | For the purposes of the present document the following symbols apply: A Interface between an MSC and a BSC. Bea Reference point for the CDR file transfer from the Exposure function API CGF to the BD. Bc Reference point for the CDR file transfer from the Circuit Switched CGF to the BD. Bcp Reference point for the CDR file transfer from the CP data transfer CGF to the BD. Bi Reference point for the CDR file transfer from the IMS CGF to the BD. Bl Reference point for the CDR file transfer from the GMLC CGF to the BD. Bm Reference point for the CDR file transfer from the MMS CGF to the BD. Bmn Reference point for the CDR file transfer from the Monitoring Event CGF to the BD. Bo Reference point for the CDR file transfer from the OCF CGF to the BD. Bp Reference point for the CDR file transfer from the Packet Switched CGF to the BD. Bs Reference point for the CDR file transfer for CAMEL services to the BD, i.e. from the SCF CGF to the BD. Bsm Reference point for the CDR file transfer from SMS CGF to the BD, Bt Reference point for the CDR file transfer from the PoC CGF to the BD. Bw Reference point for the CDR file transfer from the WLAN CGF to the BD (discontinued in Release 12). Bx Reference point for CDR file transfer between any (generic) 3G domain, subsystem or service CGF and a BD. CAP Reference point for CAMEL between a network element with integrated SSF and the OCS. Ga Reference point for CDR transfer between a CDF and the CGF. Gb Interface between an SGSN and a BSC. Gc Interface between an GGSN and an HLR. Gd Interface between an SMS-GMSC and an SGSN, and between a SMS-IWMSC and an SGSN. Gf Interface between an SGSN and an EIR. Gi Interface between the Packet-Switched domain and an external packet data network. Gn Interface between two GSNs within the same PLMN. Gp Interface between two GSNs in different PLMNs. Gr Interface between an SGSN and an HLR. Gs Interface between an SGSN and an MSC/VLR. Gx Reference point between a PCRF and a PCEF. Gy Online charging reference point between a PCEF and an OCS. Gyn Online charging reference point between a TDF and an OCS. Gz Offline charging reference point between a PCEF and an OFCS. Gzn Offline charging reference point between a TDF and an OFCS. Iu Interface between the RNS and the core network. kbit/s Kilobits per second. 1 kbit/s = 210 bits per second. Lr Interface between Gateway MLCs. Mbit/s Megabits per second. 1 Mbit/s = 220 bits per second. Mc Interface between the MGW and (G)MSC server. Rf Offline charging reference point between a 3G network element and the CDF. Nchf Service-based interface exhibited by Charging Function. Nnwdaf Service based interface exhibited by NWDAF. N28 Reference point between the PCF and Converged Charging System. Ro Online charging reference point between a 3G network element and the OCS. Rx Reference point between the PCRF and an AF. S8 Interface between S-GW and P-GW in different PLMNs. Sd Reference point between the PCRF and a TDF. Sy Reference point for policy enforcement between OCS and the PCRF. T8 Reference points for interworking between SCEF and SCS/AS. Um Interface between the Mobile Station (MS) and the GSM fixed network part. Uu Interface between the User Equipment (UE) and the US fixed network part. Wf Offline charging reference point between a 3GPP WLAN CTF and the CDF (discontinued in Release 12). Wo Online charging reference point between a 3GPP WLAN CTF and the OCS (discontinued in Release 12). | 3GPP TS 32.240 | Telecommunication management; Charging management; Charging architecture and principles | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 3.2 |
1,819 | 5.7.7.3 Actions related to transmission of ULDedicatedMessageSegment message | The UE shall segment the encoded RRC PDU based on the maximum supported size of a PDCP SDU specified in TS 38.323[ NR; Packet Data Convergence Protocol (PDCP) specification ] [5]. UE shall minimize the number of segments and set the contents of the ULDedicatedMessageSegment messages as follows: 1> For each new UL DCCH message, set the segmentNumber to 0 for the first message segment and increment the segmentNumber for each subsequent RRC message segment; 1> set rrc-MessageSegmentContainer to include the segment of the UL DCCH message corresponding to the segmentNumber; 1> if the segment included in the rrc-MessageSegmentContainer is the last segment of the UL DCCH message: 2> set the rrc-MessageSegmentType to lastSegment; 1> else: 2> set the rrc-MessageSegmentType to notLastSegment; 1> submit all the ULDedicatedMessageSegment messages generated for the segmented RRC message to lower layers for transmission in ascending order based on the segmentNumber, upon which the procedure ends. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.7.7.3 |
1,820 | 4.4.4.3 Integrity checking of NAS signalling messages in the MME | Except the messages listed below, no NAS signalling messages shall be processed by the receiving EMM entity in the MME or forwarded to the ESM entity, unless the secure exchange of NAS messages has been established for the NAS signalling connection: - EMM messages: - ATTACH REQUEST; - IDENTITY RESPONSE (if requested identification parameter is IMSI); - AUTHENTICATION RESPONSE; - AUTHENTICATION FAILURE; - SECURITY MODE REJECT; - DETACH REQUEST; - DETACH ACCEPT; - TRACKING AREA UPDATE REQUEST. NOTE 1: The TRACKING AREA UPDATE REQUEST message is sent by the UE without integrity protection, if the tracking area updating procedure is initiated due to an inter-system change in idle mode and no current EPS security context is available in the UE. The other messages are accepted by the MME without integrity protection, as in certain situations they are sent by the UE before security can be activated. NOTE 2: The DETACH REQUEST message can be sent by the UE without integrity protection, e.g. if the UE is attached for emergency bearer services or access to RLOS and there is no shared EPS security context available, or if due to user interaction an attach procedure is cancelled before the secure exchange of NAS messages has been established. For these cases the network can attempt to use additional criteria (e.g. whether the UE is subsequently still performing periodic tracking area updating or still responding to paging) before marking the UE as EMM-DEREGISTERED. All ESM messages are integrity protected except a PDN CONNECTIVITY REQUEST message if it is sent piggybacked in ATTACH REQUEST message and NAS security is not activated. Once a current EPS security context exists, until the secure exchange of NAS messages has been established for the NAS signalling connection, the receiving EMM entity in the MME shall process the following NAS signalling messages, even if the MAC included in the message fails the integrity check or cannot be verified, as the EPS security context is not available in the network: - ATTACH REQUEST; - IDENTITY RESPONSE (if requested identification parameter is IMSI); - AUTHENTICATION RESPONSE; - AUTHENTICATION FAILURE; - SECURITY MODE REJECT; - DETACH REQUEST; - DETACH ACCEPT; - TRACKING AREA UPDATE REQUEST; - SERVICE REQUEST; - EXTENDED SERVICE REQUEST; - CONTROL PLANE SERVICE REQUEST. NOTE 3: These messages are processed by the MME even when the MAC that fails the integrity check or cannot be verified, as in certain situations they can be sent by the UE protected with an EPS security context that is no longer available in the network. If an ATTACH REQUEST message is received without integrity protection or fails the integrity check and it is not an attach request for emergency bearer services and it is not an attach request for access to RLOS, the MME shall authenticate the subscriber before processing the attach request any further. Additionally, if the MME initiates a security mode control procedure, the MME shall include a HASHMME IE in the SECURITY MODE COMMAND message as specified in clause 5.4.3.2. If authentication procedure is not successful the MME shall maintain, if any, the EMM-context and EPS security context unchanged. For the case when the attach procedure is for emergency bearer services see clause 5.5.1.2.3 and clause 5.4.2.5. If a DETACH REQUEST message fails the integrity check, the MME shall proceed as follows: - If it is not a detach request due to switch off, and the MME can initiate an authentication procedure, the MME should authenticate the subscriber before processing the detach request any further. - If it is a detach request due to switch off, or the MME does not initiate an authentication procedure for any other reason, the MME may ignore the detach request and remain in state EMM-REGISTERED. NOTE 4: The network can attempt to use additional criteria (e.g. whether the UE is subsequently still performing periodic tracking area updating or still responding to paging) before marking the UE as EMM-DEREGISTERED. If a TRACKING AREA UPDATE REQUEST message is received without integrity protection or fails the integrity check and the UE provided a nonceUE, GPRS ciphering key sequence number, P-TMSI and RAI in the TRACKING AREA UPDATE REQUEST message, the MME shall initiate a security mode control procedure to take a new mapped EPS security context into use; otherwise, if the UE has only a PDN connection for non-emergency bearer services established and the PDN connection is not for RLOS, the MME shall initiate an authentication procedure. Additionally, if the MME initiates a security mode control procedure, the MME shall include a HASHMME IE in the SECURITY MODE COMMAND message as specified in clause 5.4.3.2. If authentication procedure is not successful the MME shall maintain, if any, the EMM-context and EPS security context unchanged. For the case when the UE has a PDN connection for emergency bearer services or for RLOS see clause 5.5.3.2.3 and clause 5.4.2.5. If a SERVICE REQUEST, EXTENDED SERVICE REQUEST or CONTROL PLANE SERVICE REQUEST message fails the integrity check and the UE has only PDN connections for non-emergency bearer services established and the PDN connections are not for RLOS, the MME shall send the SERVICE REJECT message with EMM cause #9 "UE identity cannot be derived by the network" and keep the EMM-context and EPS security context unchanged. For the case when the UE has a PDN connection for emergency bearer services or RLOS and integrity check fails, the MME may skip the authentication procedure even if no EPS security context is available and proceed directly to the execution of the security mode control procedure as specified in clause . After successful completion of the service request procedure, the network shall deactivate all non-emergency EPS bearers locally which are not EPS bearers for RLOS. The emergency EPS bearers shall not be deactivated. The network may deactivate the EPS bearers for RLOS. Once the secure exchange of NAS messages has been established for the NAS signalling connection, the receiving EMM or ESM entity in the MME shall not process any NAS signalling messages unless they have been successfully integrity checked by the NAS. If any NAS signalling message, having not successfully passed the integrity check, is received, then the NAS in the MME shall discard that message. If any NAS signalling message is received, as not integrity protected even though the secure exchange of NAS messages has been established, then the NAS shall discard this 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 | 4.4.4.3 |
1,821 | 5.15.3 Applications using the RIM Procedures | The RAN node applications, which use the RIM procedures, are fully transparent for the MME and SGSN. These applications are described in RAN specifications. An example between E-UTRAN and GERAN is the Network Assisted Cell Change described in TS 48.018[ None ] [42], TS 25.413[ UTRAN Iu interface Radio Access Network Application Part (RANAP) signalling ] [22] and TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [36]. An example between E-UTRAN and UTRAN is the exchange of SON related information described in TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [36] | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.15.3 |
1,822 | 9.4 Reporting of Precoding Matrix Indicator (PMI) | The minimum performance requirements of PMI reporting are defined based on the precoding gain, expressed as the relative increase in throughput when the transmitter is configured according to the UE reports compared to the case when the transmitter is using random precoding, respectively. When the transmitter uses random precoding, for each PDSCH allocation a precoder is randomly generated and applied to the PDSCH. A fixed transport format (FRC) is configured for all requirements. The requirements for transmission mode 6, transmission mode 9 with 4 TX and transmission mode 9 with 8 TX alternativeCodebookEnabledCLASSB_K1=TRUE configured are specified in terms of the ratio . In the definition of γ, for PUSCH 3-1 single PMI and PUSCH 1-2 multiple PMI requirements, is 60% of the maximum throughput obtained at using random precoding, and the throughput measured at with precoders configured according to the UE reports; For the PUCCH 2-1 single PMI requirement, is 60% of the maximum throughput obtained at using random precoding on a randomly selected full-size subband in set S subbands, and the throughput measured at with both the precoder and the preferred full-size subband applied according to the UE reports; For PUSCH 2-2 multiple PMI requirements, is 60% of the maximum throughput obtained at using random precoding on a randomly selected full-size subband in set S subbands, and the throughput measured at with both the subband precoder and a randomly selected full-size subband (within the preferred subbands) applied according to the UE reports. For PUCCH 1-1 single PMI requirement under transmission mode 9 with 4Tx and 8 TX when alternativeCodebookEnabledCLASSB_K1=TRUE configured, is 70% of the maximum throughput obtained at using the precoders configured according to the UE reports, and is the throughput measured at with random precoding. The requirements for transmission mode 9 with 8 TX and transmission mode 9 with 4TX enhanced codebook are specified in terms of the ratio In the definition of γ, for PUSCH 3-1 single PMI, PUCCH 1-1 single PMI and PUSCH 1-2 multiple PMI requirements, is 70% of the maximum throughput obtained at using the precoders configured according to the UE reports, and is the throughput measured at with random precoding. The requirements for transmission mode 9 with 12 TX, 16 TX, 24TX and 32 TX Class A codebook are specified in terms of the ratio In the definition of γ, for PUSCH 3-1 single PMI and PUSCH 1-2 multiple PMI requirements, is 90% of the maximum throughput obtained at using the precoders configured according to the UE reports, and is the throughput measured at with random precoding. The requirements for transmission mode 9 with 16 TX Class A advancedCodebookEnabled=TRUE configured are specified in terms of the ratio In the definition of γ, is [70%] of the maximum throughput obtained at using the precoders configured according to both the PMI and relative power indicator (RPI) reported by the UE, and is the throughput measured at using the precoders configured according to the UE reports PMI and fixed RPI equal to 0. | 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.4 |
1,823 | 11.8 Non-IP data transfering over SGi 11.8.1 General | When support of Non-IP data is provided at the Gi/SGi interface, different Point-to-Point (PtP) tunneling techniques may be used. When using PtP tunneling by UDP/IP encapsulation subclause 11.8.2 below shall be followed. Other techniques as described in clause 11.8.3 below may be used. The Gi/SGi based Non-IP data delivery is applicable to the User Plane CIoT EPS Optimization and the Control Plane CIoT EPS Optimization (see 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [77] and 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [3]). | 3GPP TS 29.061 | Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) | CT WG3 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 11.8 |
1,824 | 4.7.13.3 Service request procedure accepted by the network | If the SERVICE REQUEST message was sent in PMM-IDLE mode, the indication from the lower layers that the security mode control procedure is completed shall be treated as a successful completion of the procedure. The service request attempt counter shall be reset, timer T3317 shall be stopped, and the MS enters GMM-REGISTERED state and PMM-CONNECTED mode. If the SERVICE REQUEST message was sent in PMM-CONNECTED mode, then the reception of the SERVICE ACCEPT message shall be treated as a successful completion of the procedure. The timer T3317 shall be stopped and the MS remains in PMM-CONNECTED mode. Upon reception of the SERVICE REQUEST message, if the EMM Combined UE Waiting Flag is 'true', the SGSN shall complete the procedure and perform a detach procedure for non-GPRS services only as described in subclause 4.7.4.2. If the SERVICE REQUEST message was sent in a CSG cell and the CSG subscription has expired or was removed for a MS, but the MS has a PDN connection for emergency bearer services established, the network shall accept the SERVICE REQUEST message and deactivate all non-emergency PDP contexts by initiating PDP context deactivation procedure. The PDP contexts for emergency services shall not be deactivated. At successful completion of a service request procedure with Service type "data", the MS shall start timer T3319. The timer T3319 shall be stopped when the MS returns to PMM-IDLE mode or when the network releases the radio access bearer of any active PDP context. The MS shall not issue another Service Request with service type "data" while timer T3319 is running unless the Service request is being generated from a PDP context for which the flag in the Uplink data status IE has not been set in the last Service Request. The network may indicate a value for timer T3319 in the ATTACH ACCEPT or ROUTING AREA UPDATE ACCEPT messages. The last provided value of T3319 shall be used by the MS. If the information element T3319 value is not included in the ATTACH ACCEPT or ROUTING AREA UPDATE ACCEPT messages, the default value shall be used. If the T3319 value received by the MS contains an indication that the timer is deactivated or the timer value is zero, then the MS shall use the default value. If the PDP context status information element is included in the Service Accept, then the MS shall deactivate locally (without peer to peer signalling between the MS and the network) all that PDP contexts which are not in SM state PDP-INACTIVE on MS side but are indicated by the Network as being in state PDP-INACTIVE. If there is a default PDP context among the PDP contexts to be deactivated, an MS supporting S1 mode shall locally deactivate all PDP contexts associated to the same PDP address and APN as the default PDP context without peer-to-peer SM signalling to the network; an MS not supporting S1 mode may apply the same behaviour. If the MBMS context status information element is included in the SERVICE ACCEPT message, then the MS shall deactivate all those MBMS contexts locally (without peer to peer signalling between the MS and network) which are not in SM state PDP-INACTIVE in the MS, but are indicated by the network as being in state PDP-INACTIVE. If no MBMS context status information element is included, then the MS shall deactivate all those MBMS contexts locally which are not in SM state PDP-INACTIVE in the MS. If a service request is received from an MS with a LIPA PDN connection, and if: - a L-GW Transport Layer Address is provided by the lower layer together with the service request, and the GGSN address associated with the PDP context of the LIPA PDN connection is different from the provided L-GW Transport Layer Address (see 3GPP TS 25.413[ UTRAN Iu interface Radio Access Network Application Part (RANAP) signalling ] [19c]); or - no L-GW Transport Layer Address is provided together with the service request by the lower layer, then the SGSN explicitly deactivates all PDP contexts associated with the LIPA PDN connection by initiating the PDP context deactivation procedure (see subclause 6.1.3.4.2). If a service request is received from an MS with a SIPTO at the local network PDN connection, the following different cases can be distinguished: 1) if the PDN connection is a SIPTO at the local network PDN connection with collocated L-GW and if: - a SIPTO L-GW Transport Layer Address is provided by the lower layer together with the service request, and the GGSN address associated with the PDP context of the SIPTO at the local network PDN connection is different from the provided SIPTO L-GW Transport Layer Address (see 3GPP TS 25.413[ UTRAN Iu interface Radio Access Network Application Part (RANAP) signalling ] [19c]); or - no SIPTO L-GW Transport Layer Address is provided together with the service request by the lower layer, 2) if the PDN connection is a SIPTO at the local network PDN connection with stand-alone GW and if: - a LHN-ID value is provided by the lower layer together with the service request, and the LHN-ID stored in the PDP context of the SIPTO at the local network PDN connection is different from the provided LHN-ID value (see 3GPP TS 25.413[ UTRAN Iu interface Radio Access Network Application Part (RANAP) signalling ] [19c]); or - no LHN-ID value is provided together with the service request by the lower layer, then the SGSN explicitly deactivates all PDP contexts associated with the SIPTO at the local network PDN connection by initiating the PDP context deactivation procedure (see subclause 6.1.3.4.2). | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.7.13.3 |
1,825 | 8.11.2.2.4 CE Mode A with CRS interference model | The requirements are specified in Table 8.11.2.2.4-2, with the addition of parameters in Table 8.11.2.2.4-1. In Table 8.11.2.2.4-2, Cell 1 is the serving cell, and Cell 2 and Cell 3 are the aggressor cells. The downlink physical channel setup is according to Annex C.3.2 for each of Cell 1, Cell 2 and Cell 3, respectively. The CRS assistance information [7] is provided to the UE and includes information on Cell 2 and Cell 3. The purpose of the test is to verify the MPDCCH performance under assumption that UE applies CRS interference mitigation in the scenario with 2 CRS antenna ports in the serving and aggressor cells. Table 8.11.2.2.4-1: Test Parameters for MPDCCH (CRS interference model) Table 8.11.2.2.4-2: Minimum performance CE Mode A MPDCCH | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.11.2.2.4 |
1,826 | 19 Support for NR coverage enhancements | To improve NR uplink coverage for both FR1 and FR2, the following enhancements on PUSCH, PUCCH, PRACH and MSG3 PUSCH are supported: - Enhanced aggregation of multiple slots with TB repetition is supported for both PUSCH transmission with dynamic and configured grant. In addition, counting based on available slots is supported. The maximum number of aggregated slots for counting based on available slots and counting based on physical slots are both 32. - TB processing over multiple slots with and without repetition is supported for both PUSCH transmission with dynamic grant and configured grant. For a single transmission of TB processing over multiple slots PUSCH, the TB size is determined based on multiple slots. - DMRS bundling where the UE maintains phase continuity and power consistency across PUSCH transmissions or PUCCH repetitions to enable improved channel estimation is supported. Inter-slot frequency hopping with DMRS bundling is supported. - Dynamic PUCCH repetition factor indication configured per PUCCH resource is introduced, applicable to all PUCCH formats. - Aggregation of multiple slots with TB repetition for MSG3 transmission is supported on both NUL and SUL, applicable to CBRA with 4-step RA type. If configured, the UE requests MSG3 repetition via separate RACH resources when the RSRP of DL path-loss reference is lower than a configured threshold. BWP configured with RACH resources solely for MSG3 repetition is also supported without the need to consider the RSRP of DL path-loss reference by the UE. - MSG1 repetition with same beam is supported on both NUL and SUL for 4-step RA type. For CBRA, network broadcasts separate RSRP thresholds for different repetition numbers. UE performs MSG1 repetition via RACH resources that are different from RACH resources without MSG1 repetition. CFRA for MSG1 repetition for ReconfigurationWithSync is supported and the network signals the MSG1 repetition number explicitly. Fallback from lower number to higher number of MSG1 repetition is supported among the set(s) of RACH resources associated with same feature(s). Fallback from lower number to higher number of MSG1 repetition is not supported for MSG1-based SI request or if UE has performed fallback from CFRA to CBRA. Fallback from CFRA with MSG1 repetition to 4-step CBRA with MSG1 repetition using the same MSG1 repetition number as the one used for CFRA is supported. - Dynamic switching between DFT-S-OFDM and CP-OFDM for PUSCH is supported. The indication for switching between DFT-S-OFDM and CP-OFDM for PUSCH is contained in DCI format 0_1/0_2, which is configured separately for each BWP. PHR can be reported for current transmission of PUSCH using one of the DFT-S-OFDM or CP-OFDM waveform and an assumed transmission of PUSCH using the other waveform than the current one. - Frequency domain spectrum shaping without frequency extension is supported for MPR/PAR reduction on the PUSCH transmission, and the change value of UE power class is reported in the PHR. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 19 |
1,827 | 5.4.5 UE requested bearer resource modification | The UE requested bearer resource modification procedure for an E-UTRAN is depicted in figure 5.4.5-1. The procedure allows the UE to request for a modification of bearer resources (e.g. allocation or release of resources) for one traffic flow aggregate with a specific QoS demand. Alternatively, the procedure allows the UE to request for the modification of the packet filters used for an active traffic flow aggregate, without changing QoS. If accepted by the network, the request invokes either the Dedicated Bearer Activation Procedure, the Bearer Modification Procedure or a dedicated bearer is deactivated using the PDN GW Initiated Bearer Deactivation Procedure. The procedure is used by the UE when the UE already has a PDN connection with the PDN GW. A UE can send a subsequent Request Bearer Resource Modification Message before the previous procedure is completed. The UE requested bearer resource modification procedure is used to indicate the change of 3GPP PS Data Off UE Status to the PDN GW via the PCO, only if the UE has been previously informed that the PDN GW supports the 3GPP PS Data Off feature. When a UE supports only Control Plane CIoT EPS Optimisation as defined in clause 5.3.4B the UE need not support the UE requested bearer resource modification procedure in order to modify the traffic flow aggregate, as the UE does not support any DRBs. The UE may need to support UE requested bearer resource modification procedure for other purposes, e.g. header compression negotiation, see TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [46]. The UE supporting 15 EPS bearers as defined in clause 4.12 shall not initiate a UE requested bearer resource modification procedure that would trigger the establishment of a new EPS bearer, if it has already 8 EPS bearers established and the UE has not received an Indication for support of 15 EPS bearers per UE or has received cause #65 "maximum number of EPS bearers reached". In this procedure the UE signals a Traffic Aggregate Description (TAD) which is a partial TFT, together with a Procedure Transaction Identifier (PTI), and an EPS Bearer Identity (when the TAD operation is modify, delete or add to an existing packet filter). When the TAD operation is modify or delete, the packet filter identifiers of the TAD are the same as the TFT packet filter identifiers of the referenced EPS Bearer (as the concatenation of the TFT packet filter identifier and the EPS Bearer identifier represents a unique packet filter identifier within the PDN connection), for which resources are being modified. The TAD is released by the UE after it has received a TFT related to the current PTI from the network. Figure 5.4.5-1: UE requested bearer resource modification NOTE 1: Steps 1, 2, and 5 are common for architecture variants with GTP-based S5/S8 and PMIP-based S5/S8. The procedure steps marked (A) differ in the case that PMIP-based S5/S8 is employed and is defined in TS 23.402[ Architecture enhancements for non-3GPP accesses ] [2]. If the bearer resource modification procedure is initiated for re-negotiation of header compression configuration for Control Plane CIoT EPS Optimisation, the MME shall not send Bearer Resource Command message to the Serving GW. In this case, the Bearer Modification Procedures (according to clause 5.4.3) is invoked and only the steps from 4 to 7 are performed. 1. The UE sends a Request Bearer Resource Modification (LBI, PTI, EPS Bearer Identity, QoS, TAD, Protocol Configuration Options) message to the MME. If the UE was in ECM-IDLE mode, this NAS message is preceded by the Service Request procedure. The TAD indicates one requested operation (add, modify, or delete packet filters). If traffic flows are added, the TAD includes the packet filter(s) (consisting of the packet filter information including packet filter precedence, but without a packet filter identifier) to be added. The UE also sends the QCI requested and GBR, if applicable, for the added traffic flows. If the UE wants to link the new packet filter(s) to an existing packet filter to enable the usage of existing bearer resources for the new packet filter(s), the UE shall provide an existing packet filter identifier together with the new packet filter(s). If the new packet filter(s) are not linked to an existing packet filter the UE shall provide at least one UL packet filter in the TAD. If a downlink only traffic flow(s) is to be added the UE shall provide an UL packet filter that effectively disallows any useful packet flows (see clause 15.3.3.4 of TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [7] for an example of such packet filter). NOTE 2: Receiving at least one UL packet filter from the UE ensures that a valid state for the TFT settings of the PDN connection as defined in clause 15.3.0 of TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [7] is maintained if the TAD add operation results in the establishment of a new dedicated EPS bearer. If the UE wants to change the GBR in addition, the UE includes the GBR requirement of the EPS Bearer. The TAD is released when the procedure is completed. When only requesting for a modification of GBR (i.e. decrease or increase), the TAD shall include the existing packet filter identifier(s) for which the GBR change request applies to. The UE includes the GBR requirement of the EPS Bearer. The TAD is released when the procedure is completed. When requesting for a modification of packet filter(s) (e.g. change of port number), the TAD shall include packet filter identifier(s) for which the change request applies to together with the changed packet filter information. If the UE requests for deletion of traffic flows, the TAD includes the packet filter identifier(s) to be deleted. If the packet filters to be deleted were mapped to a GBR Bearer, the UE includes the new GBR requirement of the EPS Bearer. The UE sends the Linked Bearer Id (LBI) only when the requested operation is add, to indicate to which PDN connection the additional bearer resource is linked to. The EPS Bearer Identity is only sent when the requested operation is modify or delete. The Procedure Transaction Id is dynamically allocated by the UE for this procedure. The UE should ensure as far as possible that previously used PTI values are not immediately reused. The PTI is released when the procedure is completed. Protocol Configuration Options may be used to transfer application level parameters between the UE and the PDN GW (see TS 23.228[ IP Multimedia Subsystem (IMS); Stage 2 ] [52]), and are sent transparently through the MME and the Serving GW. If the PDN GW indicated support for the 3GPP PS data off feature during PDN connection setup, the UE shall include in the PCO the 3GPP PS Data Off Support Indication, which indicates whether the user has activated or deactivated 3GPP PS Data Off. 2. The MME sends the Bearer Resource Command (IMSI, LBI, PTI, EPS Bearer Identity, QoS, TAD, Protocol Configuration Options) message to the selected Serving GW. The MME validates the request using the Linked Bearer Id. The same Serving GW address is used by the MME as for the EPS Bearer identified by the Linked Bearer Id received in the Request Bearer Resource Modification message. 3. The Serving GW sends the Bearer Resource Command (IMSI, LBI, PTI, EPS Bearer Identity, QoS, TAD, Protocol Configuration Options) message to the PDN GW. The Serving GW sends the message to the same PDN GW as for the EPS Bearer identified by the Linked Bearer Id. 4. The PDN GW may either apply a locally configured QoS policy, or it may interact with the PCRF to trigger the appropriate PCC decision, which may take into account subscription information. This corresponds to the beginning of a PCEF-initiated IP-CAN Session Modification procedure as defined in TS 23.203[ Policy and charging control architecture ] [6], up to the point that the PDN GW requests IP-CAN Bearer Signalling. When interacting with PCRF, the PDN GW provides to the PCRF the content of the TAD and, if applicable, the GBR change (increase or decrease) associated with the packet filter information contained in the TAD. The GBR change is either calculated from the current Bearer QoS and the requested Bearer QoS from the UE, or set to the requested GBR if the TAD indicates an add operation and no EPS Bearer Identity was received. If the TAD indicates an add operation, the requested QCI is also provided to the PCRF unless an existing packet filter identifier is provided together with the new packet filter. The PCC decision provision message may indicate that User Location Information and/or UE Time Zone information is to be provided to the PCRF as defined in TS 23.203[ Policy and charging control architecture ] [6]. If the TAD operation is modify, delete, a request for changing the GBR, or add with a link to existing packet filter(s), then the PDN GW provides to the PCRF the SDF filter identifier(s), previously assigned on Gx, that correspond to the received packet filter identifiers of the EPS bearer indicated by the received EPS bearer identity. NOTE 3: The ability of the PCRF to handle multiple PCC rules in the same request depends on operator policy. It is therefore recommended that the UE avoids providing references to multiple packet filters for different applications and services. If the PDN GW detects that the 3GPP PS Data Off UE Status has changed, the PDN GW shall indicate this event to the charging system for offline and online charging. If the 3GPP PS Data Off UE Status indicates that 3GPP PS Data Off is activated for the UE, the PDN GW shall enforce the PCC rules for downlink traffic to be applied when 3GPP PS Data Off is activated, as described in TS 23.203[ Policy and charging control architecture ] [6]. 5. If the request is accepted, either the Dedicated Bearer Activation Procedure (according to clause 5.4.1), the PDN GW Initiated Bearer Deactivation Procedure (according to clause 5.4.4.1) or one of the Bearer Modification Procedures (according to clause 5.4.2.1 or 5.4.3) is invoked. The PTI allocated by the UE is used as a parameter in the invoked Dedicated Bearer Activation Procedure, the PDN GW Initiated Bearer Deactivation Procedure or the Bearer Modification Procedure to correlate it to the UE Requested Bearer Resource Modification Procedure. This provides the UE with the necessary linkage to what EPS Bearer to be used for the new traffic flow aggregate. The PDN GW shall not modify the QoS parameters requested by the UE. The PDN GW inserts, modifies or removes packet filter(s) corresponding to the TAD into the TFT for the EPS bearer. If PCC is in use, the PDN GW uses the service data flow filters as specified in the resulting PCC rule(s). The PDN GW validates the state of the TFT settings of the PDN connection as defined in clause 15.3.0 of TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [7]. If after the execution of all TAD operations the TFT of the dedicated EPS bearer contains only packet filters for the downlink direction, the PDN GW shall add a packet filter which effectively disallows any useful packet flows in uplink direction (see clause 15.3.3.4 in TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [7] for an example of such a packet filter) to the TFT. NOTE 4: The PDN GW addition of an uplink packet filter allows the handling of pre-Release 11 UEs which may have provided only downlink packet filters in a TAD add operation without linking to an existing packet filter. When a new packet filter is inserted into a TFT, the PDN GW assigns a new packet filter identifier which is unique within the TFT. The PDN GW maintains the relation between the SDF filter identifier in the PCC rule received from the PCRF and the packet filter identifier of the TFT of this EPS bearer. If all of the packet filter(s) for a dedicated EPS bearer have been removed from the TFT, the PDN GW performs the PDN GW Initiated Bearer Deactivation Procedure. If the requested QoS is not granted (i.e. the requested QoS cannot be accepted or resources could not be allocated), or the resulting TFT settings of the PDN connection does not pass the validation, then the PDN GW sends a Bearer Resource Failure Indication (with a cause indicating the reason why the request failed or was rejected) message, which shall be delivered to the UE. 6. If the PDN GW interacted with the PCRF in step 4, the PDN GW indicates to the PCRF whether the PCC decision could be enforced or not. This corresponds to the completion of the PCEF-initiated IP-CAN session modification procedure as defined in TS 23.203[ Policy and charging control architecture ] [6], proceeding after the completion of IP-CAN bearer signalling. If requested by the PCRF the PDN GW indicates User Location Information and/or UE Time Zone Information to the PCRF as defined in TS 23.203[ Policy and charging control architecture ] [6]. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.4.5 |
1,828 | – PUCCH-TPC-CommandConfig | The IE PUCCH-TPC-CommandConfig is used to configure the UE for extracting TPC commands for PUCCH from a group-TPC messages on DCI. PUCCH-TPC-CommandConfig information element -- ASN1START -- TAG-PUCCH-TPC-COMMANDCONFIG-START PUCCH-TPC-CommandConfig ::= SEQUENCE { tpc-IndexPCell INTEGER (1..15) OPTIONAL, -- Cond PDCCH-OfSpcell tpc-IndexPUCCH-SCell INTEGER (1..15) OPTIONAL, -- Cond PDCCH-ofSpCellOrPUCCH-SCell ..., [[ tpc-IndexPUCCH-sSCell-r17 INTEGER (1..15) OPTIONAL, -- Need R tpc-IndexPUCCH-sScellSecondaryPUCCHgroup-r17 INTEGER (1..15) OPTIONAL -- Cond twoPUCCHgroup ]] } -- TAG-PUCCH-TPC-COMMANDCONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
1,829 | 5.8.9.9.2 Actions related to transmission of UuMessageTransferSidelink message | The L2 U2N Relay UE initiates the Uu message transfer procedure when at least one of the following conditions is met: 1> upon receiving Paging message related to the connected L2 U2N Remote UE from network (including Paging message within RRCReconfiguration message); 1> upon acquisition of the SIB(s) requested by the connected L2 U2N Remote UE (as indicated in sl-RequestedSIB-List in the RemoteUEInformationSidelink) or upon receiving the updated SIB(s) from network which has been requested by the connected L2 U2N Remote UE; 1> upon acquisition of the posSIB(s) requested by the connected L2 U2N Remote UE (as indicated in sl-RequestedPosSIB-List in the RemoteUEInformationSidelink) or upon receiving the updated posSIB(s) from network which have been requested by the connected L2 U2N Remote UE; 1> upon unsolicited SIB1 forwarding to the connected L2 U2N Remote UE or upon receiving the updated SIB1 from network; For each associated L2 U2N Remote UE, the L2 U2N Relay UE shall set the contents of UuMessageTransferSidelink message as follows: 1> include sl-PagingDelivery if the Paging message received from network containing the ue-Identity of the L2 U2N Remote UE; 1> include sl-SIB1-Delivery if any of the conditions for initiating Uu message transfer procedure related to SIB1 are met; 1> include sl-SystemInformationDelivery if any of the conditions for initiating Uu message transfer procedure related to System Information are met; 1> submit the UuMessageTransferSidelink message to lower layers for transmission. NOTE: The L2 U2N Relay UE may perform unsolicited forwarding of SIB1 to the L2 U2N Remote UE based on UE implementation. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.8.9.9.2 |
1,830 | 5.5.1.3.4.2 Combined attach successful | The description for attach for EPS services as specified in clause 5.5.1.2.4 shall be followed. In addition, the following description for attach for non-EPS services or "SMS only" applies. The TMSI reallocation may be part of the combined attach procedure. The TMSI allocated is then included in the ATTACH ACCEPT message, together with the location area identification (LAI). In this case the MME shall start timer T3450 as described in clause 5.4.1.4, and enter state EMM-COMMON-PROCEDURE-INITIATED. If the MME does not indicate "SMS only" in the ATTACH ACCEPT message, subject to operator policies the MME should allocate a TAI list that does not span more than one location area. For a shared network in CS domain, the MME indicates the selected PLMN for CS domain in the LAI to the UE as specified in 3GPP TS 23.272[ Circuit Switched (CS) fallback in Evolved Packet System (EPS); Stage 2 ] [9]. The UE, receiving an ATTACH ACCEPT message, stores the received location area identification, stops timer T3410, resets the location update attempt counter and sets the update status to U1 UPDATED. If the message contains an IMSI, the UE is not allocated any TMSI, and shall delete any TMSI accordingly. If the message contains a TMSI, the UE shall use this TMSI as the new temporary identity. The UE shall delete its old TMSI and shall store the new TMSI. If neither a TMSI nor an IMSI has been included by the network in the ATTACH ACCEPT message, the old TMSI, if any available, shall be kept. If the UE maintains a counter for "SIM/USIM considered invalid for non-GPRS services" events (see clause 5.3.7b), then the UE shall reset this counter. If the UE requested "SMS only" in the Additional update type IE, or if the UE requested a combined attach for EPS and non-EPS services, but the network decides to accept the attach request for EPS services and "SMS only", the network shall indicate "SMS only" in the Additional update result IE. In addition, if the SMS services are provided via SMS in MME, the network shall provide a non-broadcast LAI in the ATTACH ACCEPT message. If a TMSI has to be allocated, then the network shall also provide a TMSI value which cannot cause any ambiguity with assigned TMSI values. If the ATTACH ACCEPT message includes the Additional update result IE with value "SMS only", a UE operating in CS/PS mode 2 and a UE operating in CS/PS mode 1 with "IMS voice available" shall not attempt to use CS fallback for mobile originating services. As an implementation option, if the ATTACH ACCEPT message does not include the Additional update result IE with value "SMS only" and the UE is not configured for NAS signalling low priority then the UE may stop timer T3246 if running. If the ATTACH ACCEPT message includes the Additional update result IE with value "CS Fallback not preferred", this indicates to a UE operating in CS/PS mode 2 and a UE operating in CS/PS mode 1 with "IMS voice available" that it is attached for EPS and non-EPS services and that it can use CS fallback. If the LAI contained in the ATTACH ACCEPT message is a member of the list of "forbidden location areas for regional provision of service" or the list of "forbidden location areas for roaming" then such entry shall be deleted. If the PLMN identity for the CS domain which is provided as part of the LAI contained in the ATTACH ACCEPT message differs from the PLMN identity provided as part of the GUTI, the MME shall include the PLMN identity for the CS domain in the list of equivalent PLMNs in the ATTACH ACCEPT message. The UE, when having requested PDN connectivity as contained in the ATTACH REQUEST message and on receiving the ATTACH ACCEPT message combined with the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message, shall send an ATTACH COMPLETE message combined with an ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT message to the network. Upon transmission of the ATTACH COMPLETE message the UE shall enter state EMM-REGISTERED and MM state MM-IDLE and set the EPS update status to EU1 UPDATED. If the ATTACH ACCEPT message includes the Additional update result IE with value "SMS only" or "CS Fallback not preferred", a UE operating in CS/PS mode 1 with "IMS voice not available" shall attempt to select GERAN or UTRAN radio access technology and disable the E-UTRA capability (see clause 4.5). Upon receiving an ATTACH COMPLETE message, the MME shall stop timer T3450, enter state EMM-REGISTERED. NOTE: Upon receiving an ATTACH COMPLETE message, the MME sends an SGsAP-TMSI-REALLOCATION-COMPLETE message as specified in 3GPP TS 29.118[ Mobility Management Entity (MME) - Visitor Location Register (VLR) SGs interface specification ] [16A]. After the UE performs intersystem change from N1 mode to S1 mode, if: - the network supports SRVCC for IMS emergency sessions (see 3GPP TS 23.216[ Single Radio Voice Call Continuity (SRVCC); Stage 2 ] [8]); - the UE has an emergency PDN connection; - the UE has set the SRVCC to GERAN/UTRAN capability bit in the MS network capability IE to "SRVCC from UTRAN HSPA or E-UTRAN to GERAN/UTRAN supported; and - the MME has neither an IMEI nor an IMEISV for the UE; then the MME shall initiate the identification procedure (see clause 5.4.4) or the security mode control procedure (see clause 5.4.3) with the UE. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.5.1.3.4.2 |
1,831 | 6.4.1 UE-requested PDU session establishment procedure 6.4.1.1 General | The purpose of the UE-requested PDU session establishment procedure is to establish a new PDU session with a DN, to perform handover of an existing PDU session between 3GPP access and non-3GPP access, to transfer an existing PDN connection in the EPS to the 5GS, to transfer an existing PDN connection in an untrusted non-3GPP access connected to the EPC to the 5GS, or to establish an MA PDU session to support ATSSS (see 3GPP TS 24.193[ 5G System;Access Traffic Steering, Switching and Splitting (ATSSS); Stage 3 ] [13B]), or to relay the service associated with the RSC for 5G ProSe layer-3 UE-to-network relay (see 3GPP TS 24.554[ Proximity-services (ProSe) in 5G System (5GS) protocol aspects; Stage 3 ] [19E]). If accepted by the network, the PDU session enables exchange of PDUs between the UE and the DN. The UE shall not request a PDU session establishment: a) for an LADN, if the DNN used for that LADN is included in the LADN information IE and the UE is located outside the LADN service area indicated in the LADN information IE; a1) for an LADN, if the DNN used for that LADN is included in the Extended LADN information IE and there is no S-NSSAI used for PDU session establishment; a2) for an LADN, if the DNN used for that LADN is included in the Extended LADN information IE and the S-NSSAI used for PDU session establishment is not associated with that LADN; a3) for an LADN, if the DNN and the S-NSSAI used for that LADN are included in the Extended LADN information IE and the UE is located outside the LADN service area indicated in the Extended LADN information IE; b) to transfer a PDU session from non-3GPP access to 3GPP access when the 3GPP PS data off UE status is "activated" and the UE is not using the PDU session to send uplink IP packets for any of the 3GPP PS data off exempt services (see subclause 6.2.10); c) when the UE is in NB-N1 mode, the UE has indicated preference for user plane CIoT 5GS optimization, the network has accepted the use of user plane CIoT 5GS optimization for the UE, and the number of PDU sessions that currently has user-plane resources established equals to the UE's maximum number of supported user-plane resources; d) to transfer a PDU session from 3GPP access to non-3GPP access when the UE has indicated preference for control plane CIoT 5GS optimization, the network has accepted the use of control plane CIoT 5GS optimization for the UE, and the Control plane only indication IE was received in the PDU SESSION ESTABLISHMENT ACCEPT message; e) to transfer a PDU session from the non-3GPP access to the 3GPP access when the UE is in NB-N1 mode, the UE has indicated preference for user plane CIoT 5GS optimization, the network has accepted the use of user plane CIoT 5GS optimization for the UE, and the number of PDU sessions that currently has user-plane resources established equals to the UE's maximum number of supported user-plane resources; f) associated to an S-NSSAI when the UE is not in the NS-AoS of the S-NSSAI; or g) associated to an S-NSSAI included in the partially allowed NSSAI when the current TA is not in the list of TAs where the S-NSSAI is allowed. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.4.1 |
1,832 | 5.21.1.2 NGAP UE-TNLA-binding | While a UE is in CM-Connected state the 5G-AN node shall maintain the same NGAP UE-TNLA-binding (i.e. use the same TNL association and same NGAP association for the UE) unless explicitly changed or released by the AMF. An AMF shall be able to update the NGAP UE-TNLA-binding (i.e. change the TNL association for the UE) in CM-CONNECTED state at any time. The NGAP UE-TNLA-binding can also be updated when a UE-specific NGAP message initiated by AMF is received via a new TNL association. An AMF shall be able to update the NGAP UE-TNLA-binding (i.e. change the TNL association for the UE) in response to an N2 message received from the 5G-AN by triangular redirection (e.g. by responding to the 5G-AN node using a different TNL association). An AMF shall be able to command the 5G-AN node to release the NGAP UE-TNLA-binding for a UE in CM-CONNECTED state while maintaining N3 (user-plane connectivity) for the UE at any time. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.21.1.2 |
1,833 | B.1 Protection of RRC messages | The following list provides information which messages can be sent (unprotected) prior to AS security activation and which messages can be sent unprotected after AS security activation. Those messages indicated "-" in "P" column should never be sent unprotected by gNB or UE. Further requirements are defined in the procedural text. P…Messages that can be sent (unprotected) prior to AS security activation A – I…Messages that can be sent without integrity protection after AS security activation A – C…Messages that can be sent unciphered after AS security activation NA… Message can never be sent after AS security activation | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | B.1 |
1,834 | 6.3 Coordination between SM and GMM for supporting ISR | The MS with its TIN set as "RAT-related TMSI" for which ISR is activated shall change its TIN to "P-TMSI" to locally deactivate ISR and stop the periodic tracking area update timer T3412 or T3423, if running: - upon modification of any PDP context which was activated before the ISR is activated in the MS; - upon deactivation of the last remaining PDP context in the MS; - at the time when the MS performs intersystem change from A/Gb mode to S1 mode or from Iu mode to S1 mode if any PDP context activated after the ISR was activated in the MS exists, and the MS is in EMM-IDLE mode on completion of intersystem change; or - upon deactivation of last non-emergency PDP context in the MS, if the MS has only a PDN connection for emergency bearer services remaining. ISR remains activated on the network side in the above cases. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.3 |
1,835 | 8.4.4.1 SN Addition with SCG Activation or Deactivation | Figure 8.4.4.1-1: SCG Activation or Deactivation in SN Addition procedure 1. The MN sends the SN Addition Request message to the SN, indicates the request of SCG activation or deactivation. 2. The SN-CU-CP may send the BEARER CONTEXT SETUP REQUEST message to the SN-CU-UP to setup bearer context and notify the activation or deactivation of the SCG. 3. The SN-CU-UP sends the BEARER CONTEXT SETUP RESPONSE message to the SN-CU-CP. 4. The SN-CU sends the UE CONTEXT SETUP REQUEST message to the SN-DU to setup UE context and indicate the request of SCG activation or deactivation. 5. The SN-DU sends the UE CONTEXT SETUP RESPONSE message to the SN-CU, indicates the SCG status. In case SCG activation is requested, the SN-DU shall indicate SCG activated in the message. 6. The SN-CU-CP may send the BEARER CONTEXT MODIFICATION REQUEST message to the SN-CU-UP as described in clause 8.9.2 and may notify the SCG status if needed. 7. The SN-CU-UP sends the BEARER CONTEXT MODIFICATION RESPONSE message to the SN-CU-CP. 8. The SN sends the SN Addition Request Acknowledge message to the MN, indicates the SCG status. In case SCG activation is requested, the SN shall indicate SCG activated in the message. 9. The MN-CU-CP may send the BEARER CONTEXT MODIFICATION REQUEST message to the MN-CU-UP to notify the SCG status. 10. The MN-CU-UP sends the BEARER CONTEXT MODIFICATION RESPONSE message to the MN-CU-CP. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 8.4.4.1 |
1,836 | 13.2 Home network domain name | The home network domain name shall be in the form of an Internet domain name, e.g. operator.com, as specified in IETF RFC 1035 [19] and IETF RFC 1123 [20]. The home network domain name consists of one or more labels. Each label shall consist of the alphabetic characters (A-Z and a-z), digits (0-9) and the hyphen (-) in accordance with IETF RFC 1035 [19]. Each label shall begin and end with either an alphabetic character or a digit in accordance with IETF RFC 1123 [20]. The case of alphabetic characters is not significant. For 3GPP systems, if there is no ISIM application, the UE shall derive the home network domain name from the IMSI as described in the following steps: 1. Take the first 5 or 6 digits, depending on whether a 2 or 3 digit MNC is used (see 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [27]) and separate them into MCC and MNC; if the MNC is 2 digits then a zero shall be added at the beginning. 2. Use the MCC and MNC derived in step 1 to create the "mnc<MNC>.mcc<MCC>.3gppnetwork.org" domain name. 3. Add the label "ims." to the beginning of the domain. An example of a home network domain name is: IMSI in use: 234150999999999; where: - MCC = 234; - MNC = 15; and - MSIN = 0999999999, which gives the home network domain name: ims.mnc015.mcc234.3gppnetwork.org. The Home Network Domain for a Stand-alone Non-Public Network (SNPN) subscriber with an IMSI-based SUPI type, shall use the IMSI-based derivation described above, and append nid<NID> of the SNPN, between the "ims." and "mnc<MNC>" labels. NOTE: The UE takes the NID from "list of subscriber data" as specified in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [139], from the entry selected by the UE. An example of a home SNPN network domain name using the above IMSI and NID 000007ed9d5 is ims.nid000007ed9d5.mnc015.mcc234.3gppnetwork.org. The Home Network Domain for a Stand-alone Non-Public Network (SNPN) subscriber identified by a SUPI containing a network-specific identifier that takes the form of an NAI consists of the string "ims." appended with the realm part of the NAI. For 3GPP2 systems, if there is no IMC present, the UE shall derive the home network domain name as described in Annex C of 3GPP2 X.S0013-004 [67]. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 13.2 |
1,837 | J.1 Modified f5* function | This annex shows how the AUTS calculation could be modified in order to avoid keystream re-use during AKA re-synchronisations procedure. The f5* function given in clause 6.3.3 only has RAND as a non-key input and hence if an authentication challenge (RAND, AUTN) is replayed, then the same AK is calculated which is then used to protect different SQNMS values. This possibly leaks some bits of SQNMS as shown in Borgaonkar et al (2019) [43]. If this is a concern to an operator, then a modified f5* function using MAC-S as an additional input can be used as shown in figure J.1-1 with the dashed line showing the change from clause 6.3.3. NOTE: Including MAC-S as an input to f5* ensures that AK is unique for each SQNMS. It is home network decision to include or not MAC-S as input to f5*. Figure J.1-1: Construction of the parameter AUTS with a modified f5* function When using the modified f5* function, the re-synchronisation proceeds as described in clauses 6.3.3. and 6.3.5 with the following changes: - in clause 6.3.3, the USIM calculates AUTS = Conc(SQNMS ) || MAC-S where Conc(SQNMS) = SQNMS f5*K(RAND, MAC-S) and MAC-S is calculated as given in clause 6.3.3; and - in clause 6.3.5, the HE/AuC retrieves SQNMS from Conc(SQNMS) by computing Conc(SQNMS) f5*K(RAND, MAC-S). | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | J.1 |
1,838 | B.2.1.1 Security procedures | EAP-TLS is a mutual authentication EAP method that can be used by the EAP peer and the EAP server to authenticate each other. It is specified in RFC 5216 [38] and draft-ietf-emu-eap-tls13 [76]. The 3GPP TLS protocol profile related to supported TLS versions and supported TLS cipher suites in 3GPP networks is specified in clause 6.2 of TS 33.210[ Network Domain Security (NDS); IP network layer security ] [3]. The 3GPP profile of TLS certificates is specified in clause 6.1.3a of TS 33.310[ Network Domain Security (NDS); Authentication Framework (AF) ] [5]. EAP-TLS supports several TLS versions, and the negotiation of the TLS version is part of EAP-TLS. The main principle of negotiation goes as follows. The EAP server indicates the support for EAP-TLS in the EAP-Request. If the peer chooses EAP-TLS, it responds with an EAP-Response indicating in the ClientHello message which TLS versions the peer supports. The EAP server chooses the TLS version, and indicates the chosen version in the ServerHello message. The TLS procedure described in the RFC 5216 [38] is applicable to TLS 1.2 defined in RFC 5246 [40]. The TLS procedure described in the draft-ietf-emu-eap-tls13 [76] is applicable to TLS 1.3 defined in RFC 8446 [77]. The procedure below is based on the unified authentication framework from the present document, procedures from TS 23.502[ Procedures for the 5G System (5GS) ] [8] and RFC 5216 [38]. The procedure for EAP-TLS with TLS 1.2 is presented here as an example, and other potential procedures are possible, e.g. if TLS resumption is used. Figure B.2.1.1-1: Using EAP-TLS Authentication Procedures over 5G Networks for initial authentication 1. The UE sends the Registration Request message to the SEAF, containing SUCI. If the SUPI is in NAI format, only the username part of the NAI is encrypted using the selected protection scheme and included in the SUCI, together with the realm part in the NAI needed for UDM routing. Privacy considerations are described in Clause B.2.2. 2. The SEAF sends Nausf_UEAuthentication_Authenticate Request message to the AUSF. The SUCI and the serving network name (as described in clause 6.1.1.4) are included in the message. 3. AUSF sends the the Nudm_UEAuthentication_Get Request, containing SUCI and the serving network name, to UDM. The general rules for UDM selection apply. 4. The SIDF located within the UDM de-conceals the SUCI to SUPI if SUCI is received in the message. The UDM then selects the primary authentication method. 5. If the UDM chooses to use EAP-TLS, it sends the SUPI and an indicator to choose EAP-TLS to AUSF in the Nudm_UEAuthentication_Get Response. 6. With the received SUPI and the indicator, the AUSF chooses EAP-TLS as the authentication method. The AUSF sends thea Nausf_UEAuthentication_Authenticate Response message containing EAP-Request/EAP-TLS [TLS start] message to the SEAF. 7. The SEAF forwards the EAP-Request/EAP-TLS [TLS start] in the Authentication Request message to the UE. This message also includes the ngKSI and the ABBA parameter. In fact, the SEAF shall always include the ngKSI and ABBA parameter in all EAP-Authentication request message. ngKSI will be used by the UE and AMF to identify the partial native security context that is created if the authentication is successful. The SEAF shall set the ABBA parameter as defined in Annex A.7.1. During an EAP authentication, the value of the ngKSI and the ABBA parameter sent by the SEAF to the UE shall not be changed. 8. After receiving the EAP-TLS [TLS-start] message from SEAF, the UE replies with an EAP-Response/EAP-TLS [client_hello] to the SEAF in the Authentication Response message. The contents of TLS client_hello are defined in the TLS specification of the TLS version in use. NOTE1: The EAP framework supports negotiation of EAP methods. If the UE does not support EAP-TLS, it should follow the rule described in RFC 3748 [27] to negotiate another EAP method. In 5G system, UDM typically knows which EAP method and credentials are supported by the subscriber, and consequently EAP based negotiation may never be used. 9. The SEAF forwards the EAP-Response/EAP-TLS [client hello] message to AUSF in the Nausf_UEAuthentication_Authenticate Request. 10. The AUSF replies to the SEAF with EAP-Request/EAP-TLS in the Nausf_UEAuthentication_Authenticate Response, which further includes information elements such as server_hello, server_certificate, server_key_exchange, certificate_request, server_hello_done. These information elements are defined in the RFCs for the corresponding TLS version in use. 11. The SEAF forwards the EAP-Request/EAP-TLS message with server_hello and other information elements to the UE through Authentication Request message. This message also includes the ngKSI and the ABBA parameter. The SEAF shall set the ABBA parameter as defined in Annex A.7.1. 12. The UE authenticates the server with the received message from step 11. NOTE 2: The UE is required to be pre-configured with a UE certificate and also certificates that can be used to verify server certificates. 13. If the TLS server authentication is successful, then the UE replies with EAP-Response/EAP-TLS in Authentication Response message, which further contains information element such as client_certificate, client_key_exchange, client_certificate_verify, change_cipher_spec, client_finished etc. Privacy considerations are described in Clause B.2.1.2. 14. The SEAF forwards the message with EAP-Response/EAP-TLS message with client_certificate and other information elements to the AUSF in the Nausf_UEAuthentication_Authenticate Request. 15. The AUSF authenticates the UE based on the message received. The AUSF verifies that the client certificate provided by the UE belongs to the subscriber identified by the SUPI. If there is a miss-match in the subscriber identifiers in the SUPI, the AUSF does not accept the client certificate. If the AUSF has successfully verified this message, the AUSF continues to step 16, otherwise it returns an EAP-failure. NOTE 2: The AUSF is required to be pre-configured with the root or any intermediary CA certificates that can be used to verify UE certificates. Deployment of certificate revocation lists (CRLs) and online certificate status protocol (OCSP) are described in clause B.2.2. 16. The AUSF sends EAP-Request/EAP-TLS message with change_cipher_spec and server_finished to the SEAF in the Nausf_UEAuthentication_Authenticate Response. 17. The SEAF forwards EAP-Request/EAP-TLS message from step 16 to the UE with Authentication Request message. This message also includes the ngKSI and the ABBA parameter. The SEAF shall set the ABBA parameter as defined in Annex A.7.1. 18. The UE sends an empty EAP-TLS message to the SEAF in Authentication Response message. 19. The SEAF further forwards the EAP-Response/EAP-TLS message to the AUSF in the Nausf_UEAuthentication_Authenticate Request. 20. The AUSF uses the most significant 256 bits of EMSK as the KAUSF and then calculates KSEAF from KAUSF as described in Annex A.6. The AUSF sends an EAP-Success message to the SEAF together with the SUPI and the derived anchor key in the Nausf_UEAuthentication_Authenticate Response. 21. The SEAF forwards the EAP-Success message to the UE and the authentication procedure is finished. This message also includes the ngKSI and the ABBA parameter. The SEAF shall set the ABBA parameter as defined in Annex A.7.1. Then the SEAF derives the KAMF from the KSEAF, the ABBA parameter and the SUPI according to Annex A.7, and provides the ngKSI and the KAMF to the AMF. On receiving the EAP-Success message, the UE derives EMSK and uses the most significant 256 bits of the EMSK as the KAUSF and then calculates KSEAF in the same way as the AUSF. The UE derives the KAMF from the KSEAF, the ABBA parameter and the SUPI according to Annex A.7. NOTE 3: Step 21 could be NAS Security Mode Command or Authentication Result. NOTE 4: The ABBA parameter is included to enable the bidding down protection of security features that may be introduced later. NOTE 5: As an implementation option, the UE creates the temporary security context as described in step 21 after receiving the EAP message that allows EMSK to be calculated. The UE turns this temporary security context into a partial security context when it receives the EAP Success. The UE removes the temporary security context if the EAP authentication fails. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | B.2.1.1 |
1,839 | 10.5.5.20 Service type | The purpose of the service type information element is to specify the purpose of the Service request procedure. The service type is a type 1 information element. The service type information element is coded as shown in figure 10.5.135/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.153a/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Figure 10.5.135/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Service type information element Table 10.5.153a/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : 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.5.20 |
1,840 | 5.7.1.3 Reception of the DLInformationTransfer by the UE | Upon receiving DLInformationTransfer message, the UE shall: 1> if dedicatedNAS-Message is included: 2> forward dedicatedNAS-Message to upper layers. 1> if referenceTimeInfo is included: 2> calculate the reference time based on the time, referenceSFN and timeInfoType if it is included; 2> calculate the uncertainty of the reference time based on the uncertainty, if uncertainty is included; 2> inform upper layers of the reference time and, if uncertainty is included, of the uncertainty; 2> ignore all further referenceTimeInfo received in SIB9, if any. 1> if sib9Fallback is included: 2> apply referenceTimeInfo in SIB9. 1> if rxTxTimeDiff-gNB is included: 2> calculate the propagation delay based on the UE Rx-Tx time difference measurement and the received Rx-Tx time difference measurement at the gNB; 2> inform upper layers of the propagation delay. 1> if ta-PDC is set to activate: 2> inform upper layers of the propagation delay determined by the accumulated Timing Advance commands. 1> if clockQualityDetailsLevel is included: 2> if eventID-TSS is included: 3> if VarEventID has an entry with a storedEventID value: 4> replace the storedEventID value within VarEventID with the eventID-TSS value received with clockQualityDetailsLevel; 3> else: 4> add a new entry of storedEventID within the VarEventID with a value set as the one of eventID-TSS value received with clockQualityDetailsLevel; 2> if the VarGnbID has an entry with a storedGnbID value: 3> replace the storedGnbID value within VarGnbID with the gNB identity value received within SIB1; 2> else: 3> add a new entry of storedGnbID within the VarGnbID with the gNB identity value received within SIB1. 2> forward clockQualityDetailsLevel to upper layers. Upon receiving DLInformationTransfer message, the IAB-MT shall: 1> if dedicatedInfoF1c is included: 2> forward dedicatedInfoF1c to the collocated IAB-DU. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.7.1.3 |
1,841 | 8.1 UE Initial Access | The signalling flow for UE Initial access is shown in Figure 8.1-1. Figure 8.1-1: UE Initial Access procedure 1. The UE sends an RRCSetupRequest message to the gNB-DU. 2. The gNB-DU includes the RRC message and, if the UE is admitted, the corresponding low layer configuration for the UE in the INITIAL UL RRC MESSAGE TRANSFER message and transfers to the gNB-CU. The INITIAL UL RRC MESSAGE TRANSFER message includes the C-RNTI allocated by the gNB-DU. If the gNB-DU identifies the UE as a Reduced Capability UE during the random access procedure, a NR RedCap UE Indication is provided in the INITIAL UL RRC MESSAGE TRANSFER message. 3. The gNB-CU allocates a gNB-CU UE F1AP ID for the UE and generates a RRCSetup message towards UE. The RRC message is encapsulated in -the DL RRC MESSAGE TRANSFER message. 4. The gNB-DU sends the RRCSetup message to the UE. 5. The UE sends the RRC CONNECTION SETUP COMPLETE message to the gNB-DU. 6. The gNB-DU encapsulates the RRC message in the UL RRC MESSAGE TRANSFER message and sends it to the gNB-CU. 7. The gNB-CU sends the INITIAL UE MESSAGE message to the AMF. 8. The AMF sends the INITIAL CONTEXT SETUP REQUEST message to the gNB-CU. 9. The gNB-CU sends the UE CONTEXT SETUP REQUEST message to establish the UE context in the gNB-DU. In this message, it may also encapsulate the SecurityModeCommand message. In case of NG-RAN sharing, the gNB-CU includes the serving PLMN ID (for SNPNs the serving SNPN ID). 10. The gNB-DU sends the SecurityModeCommand message to the UE. 11. The gNB-DU sends the UE CONTEXT SETUP RESPONSE message to the gNB-CU. 12. The UE responds with the SecurityModeComplete message. 13. The gNB-DU encapsulates the RRC message in the UL RRC MESSAGE TRANSFER message and sends it to the gNB-CU. 14. The gNB-CU generates the RRCReconfiguration message and encapsulates it in the DL RRC MESSAGE TRANSFER message. 15. The gNB-DU sends RRCReconfiguration message to the UE. 16. The UE sends RRCReconfigurationComplete message to the gNB-DU. 17. The gNB-DU encapsulates the RRC message in the UL RRC MESSAGE TRANSFER message and send it to the gNB-CU. 18. The gNB-CU sends the INITIAL CONTEXT SETUP RESPONSE message to the AMF. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 8.1 |
1,842 | 6.1.3.7a Extended MCH Scheduling Information MAC Control Element | The Extended MCH Scheduling Information MAC control element illustrated in Figure 6.1.3.7-2 is identified by a MAC PDU subheader with LCID as specified in Table 6.2.1-4. This control element has a variable size. For each MTCH the fields below are included: - LCID: this field indicates the Logical Channel ID of the MTCH. The length of the field is 5 bits; - Stop MTCH: this field indicates the ordinal number of the subframe within the MCH scheduling period, counting only the subframes allocated to the MCH, where the corresponding MTCH stops. Value 0 corresponds to the first subframe. The length of the field is 11 bits. The special Stop MTCH value 2047 indicates that the corresponding MTCH is not scheduled. The value range 2043 to 2046 is reserved. For each MTCH the fields below may be included: - LCID: this field indicates the Logical Channel ID of the MTCH. The length of the field is 5 bits. LCIDs x…x+y shall be equal to or a subset of the LCIDs 1…n; - S: this field indicates that the transmission of the corresponding MTCH is to be suspended. The S field is set to 000. All other values are reserved. Figure 6.1.3.7a-1: Extended MCH Scheduling Information MAC control element | 3GPP TS 36.321 | Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification | RAN2 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.1.3.7a |
1,843 | 9.1.1.2 Applicability and test rules for different CA configurations and bandwidth combination sets | The performance requirement for CA CQI tests in Clause 9 are defined independent of CA configurations and bandwidth combination sets specified in Clause 5.6A.1. For UEs supporting different CA configurations and bandwidth combination sets, the applicability and test rules are defined for the tests for 2 DL CCs in Table 9.1.1.2-1 and 3 or more DL CCs in Table 9.1.1.2-2. For simplicity, CA configuration below refers to combination of CA configuration and bandwidth combination set. Table 9.1.1.2-1: Applicability and test rules for CA UE CQI tests with 2 DL CCs Table 9.1.1.2-2: Applicability and test rules for CA UE CQI tests with 3 or more DL CCs | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 9.1.1.2 |
1,844 | 5 GTP Header for Control Plane 5.1 General format | Control Plane GTP uses a variable length header. Control Plane GTP header length shall be a multiple of 4 octets. Figure 5.1-1 illustrates the format of the GTPv2-C Header. Figure 5.1-1: General format of GTPv2 Header for Control Plane Where: - if T = 0, TEID field is not present, k = 0, m = 0 and n = 5; - if T = 1, TEID field is present, k = 1, m = 5 and n = 9. The usage of GTPv2-C header across the EPC specific interfaces is defined in the clause 5.5 "Usage of the GTPv2-C Header". Octet 1 bits shall be coded as follows: - Bits 6-8 represent the Version field. - Bit 5 represents the Piggybacking flag (P). - Bit 4 represents the TEID flag (T). - Bits 3-1 are spare, the sender shall set them to "0" and the receiving entity shall ignore them. | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 5 |
1,845 | 5.3.3 Connection Management 5.3.3.1 General | Connection management comprises the functions of establishing and releasing a NAS signalling connection between a UE and the AMF over N1. This NAS signalling connection is used to enable NAS signalling exchange between the UE and the core network. It comprises both the AN signalling connection between the UE and the AN (RRC Connection over 3GPP access or UE-N3IWF connection over untrusted N3GPP access or UE-TNGF connection over trusted N3GPP access) and the N2 connection for this UE between the AN and the AMF. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.3.3 |
1,846 | 8.17.4 IAB Inter-CU Backhaul RLF recovery for single connected IAB-node | The inter-CU backhaul RLF recovery procedure for IAB-nodes in SA mode enables recovery of an IAB-node to another parent node underneath a different IAB-donor-CU, when the IAB-MT of the IAB-node detects backhaul RLF. Figure 8.17.4-1 shows an example of the backhaul RLF recovery procedure for an IAB-node in SA mode. In this example, the IAB-node changes from its initial parent node to a new parent node, where the new parent node is served by a different IAB-donor-CU than that serving its initial parent node. In this procedure, the recovering IAB-node becomes a boundary IAB-node since the IAB-DU retains F1AP with the initial IAB-donor-CU while its IAB-MT obtains RRC connectivity with the new IAB-donor-CU. Figure 8.17.4-1: IAB inter-CU backhaul RLF recovery procedure for an IAB-node in SA mode 1. The IAB-MT of the IAB-node detects backhaul RLF. 2. The IAB-MT attempts RLF recovery by performing Random Access towards a new parent IAB-DU. 3. The IAB-MT undergoing RLF recovery sends an RRCReestablishmentRequest message to the new parent IAB-DU. 4. The new parent IAB-DU sends an INITIAL UL RRC MESSAGE to the new IAB-donor-CU, to convey the received RRCReestablishmentRequest message. 5. The new IAB-donor-CU retrieves the UE Context for the IAB-MT undergoing recovery, through the XnAP Retrieve UE Context procedure. The initial IAB-donor-CU may include the TNL address information of the IAB-node undergoing recovery in the RRC container of the RETRIEVE UE CONTEXT RESPONSE message. 6. The new IAB-donor-CU sends a DL RRC MESSAGE TRANSFER message to the new parent IAB-DU, to convey the generated RRCReestablishment message. 7. The new parent IAB-DU sends an RRCReestablishment message to the IAB-MT undergoing recovery. 8. The IAB-MT undergoing recovery sends an RRCReestablishmentComplete message to the new parent IAB-DU. 9. The new parent IAB-DU sends an UL RRC MESSAGE TRANSFER message to the new IAB-donor-CU, to convey the received RRCReestablishmentComplete message. 10. The new IAB-donor-CU triggers the UE Context Setup procedure toward the new parent IAB-DU, to create the UE context for the IAB-MT undergoing recovery and to set up one or more bearers. These bearers can be used by the IAB-MT undergoing recovery for its own signalling, and, optionally, data traffic. 11. The new IAB-donor-CU triggers the path switch procedure for the IAB-MT undergoing recovery, if needed. 12. The new IAB-donor-CU sends UE CONTEXT RELEASE message to the initial IAB-donor-CU. NOTE: The XnAP UE IDs of the boundary IAB-MT are retained at initial IAB-donor-CU and new IAB-donor-CU as long as the recovery path is used for transport of traffic between the IAB-node undergoing recovery and the initial IAB-donor-CU. 13. The initial IAB-donor-CU may release the BH RLC channels and BAP-sublayer routing entries on the initial path between the initial parent IAB-node and the initial IAB-donor-DU. 14. The new IAB-donor-CU sends a DL RRC MESSAGE TRANSFER message to the new parent IAB-DU, which includes an RRCReconfiguration message for the IAB-MT undergoing recovery. The RRC configuration may include new TNL addresses anchored at the new IAB-donor-DU. The RRC configuration may further include a BAP address for the recovery IAB-node in the new IAB-donor-CU’s topology, default BH RLC channel and a default BAP routing ID configuration for UL F1-C/non-F1 traffic mapping on the recovery path. 15. The new parent IAB-DU forwards the received RRCReconfiguration message to the IAB-MT undergoing recovery. 16. The IAB-MT undergoing recovery responds to the new parent IAB-DU with an RRCReconfigurationComplete message. 17. The new parent IAB-DU sends an UL RRC MESSAGE TRANSFER message to the new IAB-donor-CU, to convey the received RRCReconfigurationComplete message. 18. The remaining part of the procedure follows the steps 14-20 of the inter-CU topology adaptation procedure defined in clause 8.17.3.1. Traffic offload for descendant nodes follows the same procedure as that of clause 8.17.3.2. The new IAB-donor-CU may request the modification of the L2 transport of the offloaded traffic in the new IAB-donor-CU’s topology. The new IAB-donor-CU may further reconfigure the TNL addresses of the boundary IAB-node via RRC. The traffic offload due to inter-CU RLF recovery procedure for the boundary IAB-node and its descendant IAB-nodes can be fully revoked. In this case, the boundary IAB-MT is handed over in reverse direction, i.e., from the new IAB-donor-CU to the initial IAB-donor-CU, and the traffic of the boundary IAB-DU and the descendant IAB-DUs is routed again along the initial path used prior to BH RLF recovery. The new IAB-donor-CU can initiate the full revoking of traffic offload by executing the XnAP Handover Preparation procedure for the boundary IAB-MT towards the initial IAB-donor-CU. The initial IAB-donor-CU can initiate the full revoking of traffic offload in the same manner as described in clause 8.17.3.1 for the revoking initiated by the F1-terminating IAB-donor-CU. The initial IAB-donor-CU may request full or partial release of the offloaded traffic from the new IAB-donor-CU via the IAB TRANSPORT MIGRATION MANAGEMENT REQUEST message. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 8.17.4 |
1,847 | 16.14.10 Verification of UE location | For UE location verification based on multi-RTT with single satellite in NTN, at least the following UE and gNB measurements specified in TS 38.215[ NR; Physical layer measurements ] [59] are reported: gNB receive-transmit time difference at the uplink time synchronization reference point, UE receive-transmit time difference, UE receive-transmit time difference subframe offset and DL timing drift. The assistance information provided to the CN may include ephemeris information including accurate satellite position and velocity at the time of multi-RTT measurement, and common TA parameters (ta-Common, ta-CommonDrift, ta-CommonDriftVariant), and Epoch time. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.14.10 |
1,848 | 4.7.5.1.4a Routing area updating procedure for initiating a PDN connection for emergency bearer services not accepted by the network (UTRAN Iu mode only) | If the routing area updating request for initiating a PDN connection for emergency bearer services cannot be accepted by the network, the MS shall perform the procedures as described in subclause 4.7.5.1.4. Then if the MS is in the same selected PLMN where the last routing area updating was attempted, the MS shall: a) inform the upper layers of the failure of the procedure; or NOTE 1: This can result in the upper layers requesting establishment of a CS emergency call (if not already attempted in the CS domain) or other implementation specific mechanisms, e.g. procedures specified in 3GPP TS 24.229[ IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 ] [95] that can result in the emergency call being attempted to another IP-CAN. b) detach locally, if not detached already, attempt GPRS attach for emergency bearer services. If the routing area updating request for initiating a PDN connection for emergency bearer services fails due to abnormal case a) in subclause 4.7.5.1.5, the MS shall perform the procedures as described in subclause 4.7.5.1.5 and inform the upper layers of the failure to access the network. NOTE 2: This can result in the upper layers requesting establishment of a CS emergency call (if not already attempted in the CS domain) or other implementation specific mechanisms, e.g. procedures specified in 3GPP TS 24.229[ IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 ] [95] that can result in the emergency call being attempted to another IP-CAN. If the routing area updating request for initiating a PDN connection for emergency bearer services fails due to abnormal cases b), c) or d) in subclause 4.7.5.1.5, the MS shall perform the procedures as described in subclause 4.7.5.1.5. Then if the MS is in the same selected PLMN where the last routing area updating was attempted, the MS shall: a) inform the upper layers of the failure of the procedure; or NOTE 3: This can result in the upper layers requesting establishment of a CS emergency call (if not already attempted in the CS domain) or other implementation specific mechanisms, e.g. procedures specified in 3GPP TS 24.229[ IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 ] [95] that can result in the emergency call being attempted to another IP-CAN. b) detach locally, if not detached already, attempt GPRS attach for emergency bearer services. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.7.5.1.4a |
1,849 | 8.13.2 Management based MDT activation 8.13.2.1 General | In Management Based Trace Activation towards a gNB-CU-CP, gNB-CU-UP or a gNB-DU can be fulfilled with the Cell Traffic trace functionality defined in TS 32.422[ Telecommunication management; Subscriber and equipment trace; Trace control and configuration management ] [20]. The configuration parameters of the Trace Session that are received by a node in split RAN architecture are defined in TS 32.422[ Telecommunication management; Subscriber and equipment trace; Trace control and configuration management ] [20]. The following description is valid for both an en-gNB and a gNB. If the MDT measurement is initiated by the EM towards the gNB-CU-CP, and if the activation involves measurements collected by multiple nodes under the same gNB-CU-CP control in a split RAN architecture, the EM sends MDT measurement activation to the gNB-CU-CP and the gNB-CU-CP may further decide which gNB-DU(s) or which gNB-CU-UP(s) to perform the MDT measurement. When gNB-CU-CP or a gNB-DU receive the Trace Session Activation message from the management system for a given cell or a list of cell(s) under its control, the gNB-CU-CP or gNB-DU shall start a Trace Session for the given cell or list of cell(s). For Management Based MDT sent directly to a gNB-CU-UP, no MDT Area Configuration (apart from PLMN IDs) is to be included in the MDT activation indication. The signalling flows for management based MDT activation in gNB-CU-CP, gNB-DU and gNB-CU-UP are shown in Figure 8.13.2.2-1, Figure 8.13.2.3-1 and in Figure 8.13.2.4-1 respectively. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 8.13.2 |
1,850 | 4.4.3 IMSI attach procedure | The IMSI attach procedure is the complement of the IMSI detach procedure (see subclause 4.3.4). It is used to indicate the IMSI as active in the network. In A/Gb mode and GERAN Iu mode, the network indicates whether the IMSI attach/detach procedures are required by using the ATT flag which is broadcast in the L3-RR SYSTEM INFORMATION TYPE 3 message (see 3GPP TS 44.018[ None ] [84] subclause 10.5.2.11). In UTRAN Iu mode, the network indicates whether the IMSI attach/detach procedures are required by using the ATT flag which is included in the CS domain specific system information element (see subclause 10.5.1.12.2). The IMSI attach procedure is invoked if the ATT flag indicates that the IMSI detach/attach procedures are required and an IMSI is activated in a mobile station (i.e. activation of a mobile station with plug-in SIM/USIM, insertion of a card in a card-operated mobile station etc.) within coverage area from the network or a mobile station with an IMSI activated outside the coverage area enters the coverage area. The IMSI attach procedure is used only if the update status is U1 UPDATED and if the stored location area identification is the same as the one which is actually broadcasted on the BCCH of the current serving cell. In a shared network, the MS shall choose one of the PLMN identities as specified in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [14]. The MS shall use the IMSI attach procedure only if the update status is U1 UPDATED and the stored location area identification is equal to the combination of the chosen PLMN identity and the LAC received on the BCCH. Otherwise a normal location updating procedure (see subclause 4.4.1) is invoked independently of the ATT flag indication. The IMSI attach procedure is performed by using the location updating procedure (see subclause 4.4.1). The location updating type information element in the LOCATION UPDATING REQUEST message shall in this case indicate IMSI attach. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.4.3 |
1,851 | 5.6.1.5A Service request procedure for initiating a PDN connection for emergency bearer services not accepted by the network | If the service request for initiating a PDN connection for emergency bearer services cannot be accepted by the network, the UE shall perform the procedures as described in clause 5.6.1.5. If the service request for initiating a PDN connection for emergency bearer services fails due to receiving the AUTHENTICATION REJECT message, the UE shall perform the procedures as described in clause 5.4.2.5. Then if the UE is in the same selected PLMN where the last 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 establishment of a CS emergency call (if not already attempted in the CS domain) or other implementation specific mechanisms, e.g. procedures specified in 3GPP TS 24.229[ IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 ] [13D] can result in the emergency call being attempted to another IP-CAN. b) detach locally, if not detached already, attempt EPS attach for emergency bearer services. If the service request for initiating a PDN connection for emergency bearer services fails due to abnormal case a) in clause 5.6.1.6, the UE shall perform the actions as described in clause 5.6.1.6 and inform the upper layers of the failure to access the network. NOTE 2: This can result in the upper layers requesting establishment of a CS emergency call (if not already attempted in the CS domain) or other implementation specific mechanisms, e.g. procedures specified in 3GPP TS 24.229[ IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 ] [13D] can result in the emergency call being attempted to another IP-CAN. If the service request for initiating a PDN connection for emergency bearer services fails due to abnormal cases b), c), e), h) as well as l) when the "Extended wait time" is ignored, and la) when the "Extended wait time CP data" is ignored in clause .6, the UE shall perform the procedures as described in clause 5.6.1.6. 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 3: This can result in the upper layers requesting establishment of a CS emergency call (if not already attempted in the CS domain) or other implementation specific mechanisms, e.g. procedures specified in 3GPP TS 24.229[ IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 ] [13D] can result in the emergency call being attempted to another IP-CAN. b) detach locally, if not detached already, attempt EPS attach for emergency bearer services. | 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.1.5A |
1,852 | 10.5.5.21 Cell Notification | The purpose of the Cell Notification information element is to indicate that the Cell Notification is supported by the network and shall be then used by MS. The Cell Notification information element is coded as shown in figure 10.5.135a/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The Cell Notification is a type 2 information element. Figure 10.5.135a/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Cell Notification information element | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 10.5.5.21 |
1,853 | 6.10.3.1 SN Counter maintenance | The MN shall maintain a 16-bit counter, SN Counter, in its AS security context. The SN Counter is used when computing the KSN. The MN maintains the value of the counter SN Counter for a duration of the current 5G AS security context between UE and MN. The UE does not need to maintain the SN Counter after it has computed the KSN since the MN provides the UE with the current SN Counter value when the UE needs to compute a new KSN. The SN Counter is a fresh input to KSN derivation. That is, the UE assumes that the MN provides a fresh SN Counter each time and does not need to verify the freshness of the SN Counter. NOTE: An attacker cannot, over the air modify the SN Counter and force re-use of the same SN Counter. The reason for this is that the SN Counter is delivered over the RRC connection between the MN and the UE, and this connection is both integrity protected and protected from replay. The MN shall set the SN Counter to ‘0’ when a new AS root key, KNG-RAN, in the associated 5G AS security context is established. The MN shall set the SN Counter to ‘1’ after the first calculated KSN, and monotonically increment it for each additional calculated KSN. The SN Counter value '0' is used to calculate the first KSN. If the MN decides to release the offloaded connections to the SN and later decides to re-start the offloading to the same SN, the SN Counter value shall keep increasing, thus keeping the computed KSN fresh. The MN shall refresh the root key of the 5G AS security context associated with the SN Counter before the SN Counter wraps around. Refreshing the root key is done using intra cell handover as described in subclause 6.7.3.3 of the present document. When the root key is refreshed, the SN Counter is reset to '0' as defined above. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.10.3.1 |
1,854 | 5.8.5.7 Usage Report generated by UPF | The UPF sends the Usage Report to inform the SMF about the measurement of an active URR or about the detection of application traffic of an active Packet Detection Rule. For each URR, the Usage Report may be generated repeatedly, i.e. as long as any one of the valid event triggers applies. A final Usage Report is sent for a URR when it is no longer active, i.e. either the URR is removed or all the references to this URR in any of the Packet Detection Rules belonging to the N4 session. The following attributes can be included: Table 5.8.5.7-1: Attributes within Usage Report | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.8.5.7 |
1,855 | 4.7.2.8 Handling of timer T3324 (A/Gb mode, Iu mode and S1 mode) | An MS supporting PSM may request the network to assign a value for T3324 by including a requested timer value in: - the ATTACH REQUEST or ROUTING AREA UPDATE REQUEST message (in A/Gb mode and Iu mode ); or - the ATTACH REQUEST or TRACKING AREA UPDATE REQUEST message (in S1 mode). The value of timer T3324 can be sent by the network to the MS in: - the ATTACH ACCEPT or ROUTING AREA UPDATE ACCEPT message (in A/Gb mode and Iu mode ); and - the ATTACH ACCEPT or TRACKING AREA UPDATE ACCEPT message (in S1 mode). NOTE: Besides the value requested by the MS, the network can take local configuration into account when selecting a value for T3324 (see 3GPP TS 23.682[ Architecture enhancements to facilitate communications with packet data networks and applications ] [133A], subclause 4.5.4). In A/Gb mode and Iu mode, the MS shall apply the received T3324 value in the RA identified by the RAI contained in the ATTACH ACCEPT or ROUTING AREA UPDATE ACCEPT message, until a new value is received, T3324 is deactivated or a new PLMN is selected. The timer T3324 is deactivated if: - the last attach or routing area updating attempt was not completed successfully; - the network does not include a value for timer T3324 in the last ATTACH ACCEPT or ROUTING AREA UPDATE ACCEPT message received by the MS; or - the indicated value of the timer is "deactivated". In A/Gb mode and Iu mode, timer T3324 is reset and started with its initial value, when the MS changes from PMM-CONNECTED mode to PMM-IDLE mode (in Iu mode) or when the READY timer is stopped or expires (in A/Gb mode). Timer T3324 is stopped when the MS enters PMM-CONNECTED mode or GMM-DEREGISTERED state or the READY timer is started. In S1 mode, the MS shall apply the received T3324 value in all tracking areas of the list of tracking areas assigned to the MS, until a new value is received, T3324 is deactivated or a new PLMN is selected. The timer T3324 is deactivated if: - the last attach or tracking area updating attempt was not completed successfully; - the network does not include a value for timer T3324 in the last ATTACH ACCEPT or TRACKING AREA UPDATE ACCEPT message received by the MS; or - the indicated value of the timer is "deactivated". In S1 mode, timer T3324 is reset and started with its initial value, when the MS changes from EMM-CONNECTED mode to EMM-IDLE mode. Timer T3324 is stopped when the MS enters EMM-CONNECTED mode or EMM-DEREGISTERED state.In A/Gb mode and Iu mode, when timer T3324 expires the MS may activate PSM as specified in subclause 4.7.2.9. In S1 mode, when timer T3324 expires the MS may activate PSM as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [120], subclause 5.3.11. In A/Gb mode and Iu mode, if timer T3324 expires during an ongoing CS connection, the MS shall take action on the expiry of timer T3324 as described in subclause 4.7.2.9 when the MM state MM-IDLE is entered. | 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.8 |
1,856 | 7.2.18 Create Indirect Data Forwarding Tunnel Request | The Create Indirect Data Forwarding Tunnel Request message shall be sent on the S11/S4 interface by the MME/SGSN to the SGW as part of the Handover procedures or TAU/RAU procedure with Serving GW change and data forwarding as specified in clause 5.3.3.1A of 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [3]. Table 7.2.18-1 specifies the presence requirements and the conditions of the IEs in the message. Table 7.2.18-1: Information Elements in a Create Indirect Data Forwarding Tunnel Request Table -2: Bearer Context within Create Indirect Data Forwarding Tunnel Request | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 7.2.18 |
1,857 | – AppLayerMeasParameters | The IE AppLayerMeasParameters is used to convey the capabilities supported by the UE for application layer measurements. AppLayerMeasParameters information element -- ASN1START -- TAG-APPLAYERMEASPARAMETERS-START AppLayerMeasParameters-r17 ::= SEQUENCE { qoe-Streaming-MeasReport-r17 ENUMERATED {supported} OPTIONAL, qoe-MTSI-MeasReport-r17 ENUMERATED {supported} OPTIONAL, qoe-VR-MeasReport-r17 ENUMERATED {supported} OPTIONAL, ran-VisibleQoE-Streaming-MeasReport-r17 ENUMERATED {supported} OPTIONAL, ran-VisibleQoE-VR-MeasReport-r17 ENUMERATED {supported} OPTIONAL, ul-MeasurementReportAppLayer-Seg-r17 ENUMERATED {supported} OPTIONAL, ..., [[ qoe-IdleInactiveMeasReport-r18 ENUMERATED {supported} OPTIONAL, qoe-NRDC-MeasReport-r18 ENUMERATED {supported} OPTIONAL, qoe-AdditionalMemoryMeasReport-r18 ENUMERATED {kB128, kB256, kB512, kB1024} OPTIONAL, qoe-PriorityBasedDiscarding-r18 ENUMERATED {supported} OPTIONAL, srb5-r18 ENUMERATED {supported} OPTIONAL ]] } -- TAG-APPLAYERMEASPARAMETERS-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
1,858 | 5.3.11 Power saving mode | The UE can request the use of power saving mode (PSM) during an attach or tracking area updating procedure (see 3GPP TS 23.682[ Architecture enhancements to facilitate communications with packet data networks and applications ] [11A] and 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [10]). The UE shall not request the use of PSM during: - an attach for emergency bearer services procedure; - an attach procedure for initiating a PDN connection for emergency bearer services with attach type not set to "EPS emergency attach"; - a tracking area updating procedure for initiating a PDN connection for emergency bearer services; - a tracking area updating procedure when the UE has a PDN connection established for emergency bearer services; or - an attach for access to RLOS. The network accepts the use of PSM by providing a specific value for timer T3324 when accepting the attach or tracking area updating procedure. The UE may use PSM only if the network has provided the T3324 value IE during the last attach or tracking area updating procedure with a value different from "deactivated". NOTE: Timer T3324 is specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13]. Upon expiry of the timer T3324 or if the T3324 value provided by the network is zero, the UE may deactivate the AS layer and activate PSM by entering the state EMM-REGISTERED.NO-CELL-AVAILABLE if: a) the UE is not attached for emergency bearer services; b) the UE has no PDN connection for emergency bearer services; c) the UE is in EMM-IDLE mode; d) in the EMM-REGISTERED.NORMAL-SERVICE state; and e) the UE is not attached for access to RLOS. If conditions a, b, c and e are fulfilled, but the UE is in a state other than EMM-REGISTERED.NORMAL-SERVICE when timer T3324 expires, the UE may activate PSM when the MS returns to state EMM-REGISTERED.NORMAL-SERVICE. A UE that has already been allocated timer T3324 with a value different from "deactivated" and the timer T3324 has expired, may activate PSM if it receives an "Extended wait time" from lower layers. When PSM is activated all NAS timers are stopped and associated procedures aborted except for T3412, T3346, T3396, T3447, any backoff timers, and the timer T controlling the periodic search for HPLMN or EHPLMN (if the EHPLMN list is present) or higher prioritized PLMNs (see 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6]). If the UE is attached for emergency bearer services or has a PDN connection for emergency bearer services, the UE shall not activate PSM. If the UE is attached for access to RLOS, the UE shall not activate PSM. The UE may deactivate PSM and activate the AS layer at any time. Upon deactivating PSM, the UE may initiate EMM procedures (e.g. for the transfer of mobile originated signalling or user data). | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.3.11 |
1,859 | 4.13.8 Enhanced support of discontinuous network coverage for satellite access 4.13.8.1 General | Basic support for discontinuous coverage is specified in clause 4.3.5.2 and clause 4.3.17.7. The present clause 4.13.8 provides additional optional enhancements to discontinuous coverage: - Mobility management and power saving optimization, see clause 4.13.8.2; and - Coverage availability information provisioning to the UE, see clause 4.13.8.3; and - Coverage availability information provisioning to the MME, see clause 4.13.8.4; and - Paging, see clause 4.13.8.5; and - Overload control, see clause 4.13.8.6. In the following, "Enhanced Discontinuous Coverage" functionality includes the following enhancements as listed above: Mobility management and power saving optimization described in clause 4.13.8.2, and Overload control described in clause 4.13.8.6. During Attach or TAU procedures, a UE supporting Enhanced Discontinuous Coverage provides "Enhanced Discontinuous Coverage Support" indication as part of UE Core Network Capability in the Attach Request or TAU Request message to the MME. The MME receiving an Attach Request or a TAU Request message from the UE including "Enhanced Discontinuous Coverage Support" indicates whether Enhanced Discontinuous Coverage is supported by providing the "Enhanced Discontinuous Coverage Support" indication to the UE in the Attach Accept or TAU Accept message. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.13.8 |
1,860 | 4.11.2 Handling list of "PLMNs not allowed to operate at the present UE location" | The UE may be rejected with EMM cause #78 in ATTACH REJECT message, TRACKING AREA UPDATE REJECT message or DETACH REQUEST message. The EMM cause #78 is applicable for the UE only when the UE is accessing a PLMN using a satellite E-UTRAN access. For the satellite E-UTRAN access the UE shall store a list of "PLMN not allowed to operate at the present UE location". Each entry in the list consists of: a) PLMN identity of the PLMN which sent a message including EMM cause value #78 "PLMN not allowed to operate at the present UE location" via the satellite E-UTRAN access technology; b) geographical location, if known by the UE, where the EMM cause value #78 was received over the satellite E-UTRAN access technology; and c) if the geographical location exists, a UE implementation specific distance value. Before storing a new entry in the list, the UE shall delete any existing entry with the same PLMN identity. Upon storing a new entry, the UE starts a timer instance associated with the entry with an implementation specific value that shall not be set to a value smaller than the timer value indicated by the network in the Lower bound timer value IE, if any. If the Lower bound timer value IE was not provided by the network, the value of the timer shall be set based on the UE implementation. An entry in the list is deleted if the timer associated to the entry expires or the UE successfully registers to the PLMN stored in the entry. The UE is allowed to attempt to access a PLMN via the satellite E-UTRAN access technology which is part of the list of "PLMNs not allowed to operate at the present UE location" if: a) the current UE location is known, a geographical location is stored for the entry of this PLMN, and the distance from location where EMM cause value #78 was received to the current UE location is larger than a UE implementation specific value; or b) the access is for emergency services (see 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5] for further details). NOTE: When the UE is accessing network for emergency services, it is up to operator and regulatory policies whether the network needs to determine if the UE is in a location where network is not allowed to operate. The list shall accommodate three or more entries. The maximum number of entries is an implementation decision. When the list is full and a new entry has to be inserted, the oldest entry shall be deleted. Each entry shall be removed if for the entry: a) the UE successfully registers via the satellite E-UTRAN access technology to the PLMN stored in the entry except when the UE is attached for emergency bearer services; or b) the timer instance associated with the entry expires. The UE may remove an entry in the list, if the UE's current location is known, a geographical is stored for the entry of this PLMN, and the distance from location where EMM cause value #78 was received to the current UE location is larger than the UE implementation specific value. If the UE is in EMM-DEREGISTERED.LIMITED-SERVICE state and an entry from the list of "PLMNs not allowed to operate at the present UE location" is removed, the UE shall perform PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6]. When the UE is switched off, the UE shall keep the list of "PLMNs not allowed to operate at the present UE location" in its non-volatile memory together with the SUPI from the USIM. The UE shall delete the list of "PLMNs not allowed to operate at the present UE location" if the USIM is removed. If the UE is switched off when the timer instance associated with the entry in the list is running, the UE shall behave as follows when the UE is switched on and the USIM in the UE remains the same: let t1 be the time remaining for timer instance associated with the entry in the list to timeout at switch off and let t be the time elapsed between switch off and switch on. If t1 is greater than t, then the timer shall be restarted with the value t1 – t. If t1 is equal to or less than t, then the timer need not be restarted and considered expired. If the UE is not capable of determining t, then the UE shall restart the timer with the value t1. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.11.2 |
1,861 | 5.5.4.27 Event A5H1 (SpCell becomes worse than threshold1 and neighbour becomes better than threshold2 and the Aerial UE altitude becomes higher than a threshold3) | The UE shall: 1> consider the entering condition for this event to be satisfied when all of condition A5H1-1 and condition A5H1-2 and condition A5H1-3, as specified below, are fulfilled; 1> consider the leaving condition for this event to be satisfied when condition A5H1-4 or condition A5H1-5 or condition A5H1-6, i.e. at least one of the three, as specified below, is fulfilled; 1> use the SpCell for Mp. NOTE: The parameters of the reference signal(s) of the cell(s) that triggers the event are indicated in the measObjectNR associated to the event which may be different from the measObjectNR of the NR SpCell. Inequality A5H1-1 (Entering condition 1) Mp + Hys1 < Thresh1 Inequality A5H1-2 (Entering condition 2) Mn + Ofn + Ocn – Hys1 > Thresh2 Inequality A5H1-3 (Entering condition 3) Ms – Hys2 > Thresh3 Inequality A5H1-4 (Leaving condition 1) Mp – Hys1 > Thresh1 Inequality A5H1-5 (Leaving condition 2) Mn + Ofn + Ocn + Hys1 < Thresh2 Inequality A5H1-6 (Leaving condition 3) Ms + Hys2 < Thresh3 The variables in the formula are defined as follows: Mp is the measurement result of the NR SpCell, not taking into account any offsets. Mn is the measurement result of the neighbouring cell, not taking into account any offsets. Ofn is the measurement object specific offset of the neighbour cell (i.e. offsetMO as defined within measObjectNR corresponding to the neighbour cell). Ocn is the cell specific offset of the neighbour cell (i.e. cellIndividualOffset as defined within measObjectNR corresponding to the neighbour cell), and set to zero if not configured for the neighbour cell. Hys1 is the hysteresis parameter for this event (i.e. a5-Hysteresis as defined within reportConfigNR for this event). Thresh1 is the threshold parameter for this event (i.e. a5-Threshold1 as defined within reportConfigNR for this event). Thresh2 is the threshold parameter for this event (i.e. a5-Threshold2 as defined within reportConfigNR for this event). Ms is the Aerial UE altitude relative to the sea level. Hys2 is the hysteresis parameter for this event (i.e. h1-Hysteresis as defined within reportConfigNR for this event). Thresh3 is the threshold parameter for this event (i.e. h1-Threshold as defined within reportConfigNR for this event). Mn, Mp are expressed in dBm in case of RSRP, or in dB in case of RSRQ and RS-SINR. Ofn, Ocn, Hys are expressed in dB. Thresh1 is expressed in the same unit as Mp. Thresh2 is expressed in the same unit as Mn. Ms, Hys2, Thresh3 are expressed in meters. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.5.4.27 |
1,862 | 6.3.22 NSACF discovery and selection | The NF consumers shall utilise the NRF to discover NSACF instance(s), including the NSACF acting as Primary NSACF role, unless NSACF information is available by other means, e.g. locally configured in NF consumers. The NSACF selection function in the NSACF NF consumer selects an NSACF instance based on the available NSACF instances, which are obtained from the NRF or locally configured in the NSACF NF consumer. The following factors may be considered by the NF consumer for NSACF discovery and selection: - S-NSSAI(s). - NSAC Service Area Identifier, or a reserved value "Entire PLMN" for discovering the NSACF acting as Primary NSACF or centralized NSAC role. The NSAC Service Area Identifier is configured at the consumer NF and NSACF (see clause 5.15.11.0). Each Service Area Identifier is a unique and unambiguous identifier and a NSACF registers with the NRF the NSAC Service Area Identifier(s) of the NSAC Service Area(s) it serves. "Entire PLMN" is indicated in roaming case to the NRF of HPLMN by the VPLMN NF consumer when the VPLMN NF consumer needs to discover the HPLMN NSACF, or in non roaming case to select a Primary NSACF. - NSACF service capabilities: - Support monitoring and controlling the number of registered UEs per network slice for the network slice that is subject to NSAC. - Support, for network slices that are subject to NSAC and configured to support EPS counting, monitoring and controlling the number of registered UEs with at least one PDU session per network slice, as defined in clause 5.15.11.5a. - Support monitoring and controlling the number of established PDU Sessions per network slice for the network slice that is subject to NSAC. - PLMN ID information in the case of roaming to contact the HPLMN NSACF for inbound roamers. In the case of delegated discovery and selection in SCP, the NSACF NF consumer shall send all available and applicable factors to the SCP. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 6.3.22 |
1,863 | 8.7.3 FDD (EPDCCH scheduling) | The parameters specified in Table 8.7.3-1 are valid for all FDD tests unless otherwise stated. Table 8.7.3-1: Common test parameters (FDD) The requirements are specified in Table 8.7.3-3, with the addition of the parameters in Table 8.7.3-2 and the downlink physical channel setup according to Annex C.3.2. The test points are applied to UE category, CA capability and bandwidth combination with maximum aggregated bandwidth as specified in Table 8.7.3-4. The TB success rate shall be sustained during at least 300 frames. Table 8.7.3-2: Test parameters for SDR test for PDSCH scheduled by EPDCCH (FDD) Table 8.7.3-3: Minimum requirement (FDD) Table 8.7.3-4: Test points for sustained data rate (FRC) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.7.3 |
1,864 | 6.26.2.2 5G LAN-virtual network (5G LAN-VN) | A UE shall be able to select a 5G LAN-VN, that the UE is a member of, for private communication. A 5G system shall support 5G LAN-VNs with member UEs numbering between a few to tens of thousands. The 5G system shall be able to support large numbers of small 5G LAN-VNs. NOTE: Targeting residential deployments translate into millions of 5GLAN-VN per operator per country. These residential 5G LAN-VNs typically contain between 10-50 devices. The 5G LAN-VN shall support member UEs that are subscribed to different PLMNs, e.g. a 5G LAN-VN may span multiple countries and have member UEs that have a subscription to a PLMN in their home country. The 5G system shall support on-demand establishment of UE to UE, multicast, and broadcast private communication between members UEs of the same 5G LAN-VN. Multiple types of data communication shall be supported, at least IP and Ethernet. The 5G network shall ensure that only member UEs of the same 5G LAN-VN are able to establish or maintain private communications among each other using 5G LAN-type service. The 5G system shall allow member UEs of a 5G LAN-VN to join an authorized multicast session over that 5G LAN-VN. The 5G system shall be able to restrict private communications within a 5G LAN-VN based on UE’s location (i.e. when the UE moves out of the area it can no longer communicate on the 5G LAN-VN). The 5G network shall enable member UEs of a 5G LAN-VN to use multicast/broadcast over a 5G LAN-type service to communicate with required latency (e.g. 180 ms). The 5G system shall support a mechanism to provide consistent QoE to all the member UEs of the same 5G LAN-VN. The 5G system shall support routing based on a private addressing scheme within the 5G LAN-VN. The 5G system shall support a communication path between a non-3GPP device in the CPN and a UE in the 5G-LAN VN via the eRG of the CPN, for an eRG that is part of the 5G LAN-VN. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.26.2.2 |
1,865 | 13.3.7 Authentication and authorization between SCPs | SCPs shall use one of the following methods as described in 13.1 to mutually authenticate each other before service layer messages can be exchanged on that interface: - If the PLMN uses protection at the transport layer, authentication provided by the transport layer protection solution shall be used for mutual authentication of the SCPs. - If the PLMN does not use protection at the transport layer, mutual authentication of the two SCPs may be implicit by NDS/IP or physical security. Authorization between SCPs is based on local authorization policy. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 13.3.7 |
1,866 | 9.3.4.1.1 FDD | For the parameters specified in Table 9.3.4.1.1-1, and using the downlink physical channels specified in Annex C.3.2, the minimum requirements are specified in Table 9.3.4.1.1-2 and by the following a) the ratio of the throughput obtained when transmitting on a randomly selected subband among the best M subbands reported by the UE the corresponding TBS and that obtained when transmitting the TBS indicated by the reported wideband CQI median on a randomly selected subband in set S shall be ≥ ; The requirements only apply for subbands of full size and the random scheduling across the subbands is done by selecting a new subband in each TTI for FDD. The transport block size TBS (wideband CQI median) is that resulting from the code rate which is closest to that indicated by the wideband CQI median and theentry in Table 7.1.7.2.1-1 of TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [6] that corresponds to the subband size. Table 9.3.4.1.1-1 Subband test for single antenna transmission (FDD) Table 9.3.4.1.1-2 Minimum requirement (FDD) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 9.3.4.1.1 |
1,867 | 5.3.2.1 HARQ Entity | There is one HARQ entity at the MAC entity for each Serving Cell which maintains a number of parallel HARQ processes. Each HARQ process is associated with a HARQ process identifier. The HARQ entity directs HARQ information and associated TBs received on the DL-SCH to the corresponding HARQ processes (see clause 5.3.2.2). The number of DL HARQ processes per HARQ entity is specified in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [2], clause 7. When the physical layer is configured for downlink spatial multiplexing, as specified in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [2], one or two TBs are expected per TTI and they are associated with the same HARQ process. Otherwise, one TB is expected per TTI. For NB-IoT UEs or BL UEs or UEs in enhanced coverage, the parameter DL_REPETITION_NUMBER provides the number of transmissions repeated in a bundle. For each bundle, DL_REPETITION_NUMBER is set to a value provided by lower layers. Within a bundle, after the initial (re)transmission, DL_REPETITION_NUMBER-1 HARQ retransmissions follow. The HARQ feedback is transmitted for the bundle and a downlink assignment corresponding to a new transmission or a retransmission of the bundle is received after the last repetition of the bundle. A retransmission of a bundle is also a bundle. HARQ feedback may be disabled per HARQ process by configuring downlinkHARQ-FeedbackDisabled and/or by indication from lower layers. If the MAC entity is configured with blindSlotSubslotPDSCH-Repetitions or blindSubframePDSCH-Repetitions on a serving cell (TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8]), the parameter DL_REPETITION_NUMBER provides the number of transmissions repeated in a bundle for a downlink assignment received on that serving cell. For each bundle, DL_REPETITION_NUMBER and the redundancy version for each transmission within a bundle are set to values provided by lower layers. Within a bundle, after the initial (re-)transmission, DL_REPETITION_NUMBER-1 HARQ retransmissions follow. The HARQ feedback is sent only one time for the bundle and after the last transmission of the bundle. In addition to the broadcast HARQ process, NB-IoT has one or two DL HARQ processes. The MAC entity shall: - If a downlink assignment has been indicated for this TTI; or - If this TTI is for a retransmission within a bundle: - allocate the TB(s) received from the physical layer and the associated HARQ information to the HARQ process indicated by the associated HARQ information. - If a downlink assignment has been indicated for the broadcast HARQ process: - allocate the received TB to the broadcast HARQ process. NOTE: In case of BCCH and BR-BCCH a dedicated broadcast HARQ process is used. | 3GPP TS 36.321 | Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification | RAN2 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 5.3.2.1 |
1,868 | 6.10.2 MBSFN reference signals | MBSFN reference signals shall be transmitted in the MBSFN region of MBSFN subframes/slots only when the PMCH is transmitted. MBSFN reference signals are transmitted on antenna port 4. For an MBMS-dedicated carrier configured with a single MBSFN area, and for a PMCH transmitted with 0.37 kHz subcarrier spacing in slot , which is indicated to contain MCCH by higher layer parameter MCCH-Config: - for MBSFN reference signal pattern type 1, the UE may assume that MBSFN reference signals associated with the same are present in the three preceding slots to slot . - for MBSFN reference signal pattern type 2, the UE may assume that MBSFN reference signals associated with the same are present in the preceding slot to slot . MBSFN reference signals are defined for extended cyclic prefix 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.2 |
1,869 | 4.15.6.7a Authorization of service specific parameter provisioning | Figure 4.15.6.7a-1 shows the procedure to authorize the service specific parameter provisioning requests (e.g. for Application guidance for URSP determination as defined in clause 4.15.6.10). Figure 4.15.6.7a-1: Service Specific Authorization for an individual UE or group of UEs 1. The AF initiates the procedure as specified in clause 4.15.6.7. 2. The NEF sends Nudm_ServiceSpecificAuthorisation_Create Request including the GPSI or External Group Id, S-NSSAI/DNN, service type, (optional) AF ID, (optional) MTC Provider Information and notification address to receive updates of the authorization from UDM. 3. The UDM maps the GPSI or External Group Id included in the request from the NEF to SUPI or Internal Group Id. If the request is for an individual UE, the UDM checks the list of subscribed/allowed S-NSSAI/DNNs for the UE and other service info (e.g. MTC provider is authorized for the UE). If the request is for a group of UEs, the UDM checks whether the group related data (e.g. DNN/S-NSSAI group related data, see table 4.15.6.3b-1) and other service info, e.g. MTC provider is authorized for the group. 4. The UDM responds to the NEF with the service authorization result. If authorization succeeds, the UDM includes the SUPI or Internal Group Id mapping the GPSI or External Group Id provided by the NEF. If authorization fails (e.g. DNN is not subscribed for the UE or it is different from the group related data, UE subscription or group related data does not allow to modify URSP rules dynamically by an AF or by such specific AF or MTC provider), UDM returns a negative response with an appropriate error code and the NEF rejects the request with the proper error code to inform the AF about the request not authorized. NOTE 1: The MTC Provider Information can be used by any type of Service Providers (MTC or non-MTC) or Corporate or External Parties for, e.g. to distinguish their different customers. 5. The procedure continues as specified in clause 4.15.6.7. Figure 4.15.6.7a-2 illustrates the procedure for updating or revoking an existing Service Specific Authorization. Figure 4.15.6.7a-2: Service Specific Authorization Update procedure 0. UDM provided a successful authorization for a request to provision service specific parameters as defined in Figure 4.15.6.7a-1. The authorization for the provisioning of the service specific parameters is modified in UDM (e.g. due to subscription withdrawal or to the DNN associated to the authorization being removed from UE subscription). 1. The UDM sends a Nudm_ServiceSpecificAuthorisation_UpdateNotify Request (GPSI or External Group Id, SUPI or Internal Group Id, S-NSSAI, DNN, Service Type, (optional) AF ID, (optional) MTC Provider Information, Status, Cause) message to the NEF to update a UE's or group of UEs' authorization. 2. The NEF sends Nudm_ServiceSpecificAuthorisation_UpdateNotify Response message to the UDM to acknowledge the authorization update. 3. If the authorization is revoked, the NEF removes the service specific parameters from the UDR. 4. The NEF informs the AF that the service parameters authorisation status has changed by sending Nnef_ServiceParameter_Notify Request (GPSI or External Group Id, TLTRI, Status, Cause) message to the AF to update the authorization. 5. The AF responds to the NEF with Nnef_ServiceParameter_Notify Response message. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.15.6.7a |
1,870 | 5.3.5.5 Cell Group configuration 5.3.5.5.1 General | The network configures the UE with Master Cell Group (MCG), and zero or one Secondary Cell Group (SCG). In (NG)EN-DC, the MCG is configured as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10], and for NE-DC, the SCG is configured as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10]. The network provides the configuration parameters for a cell group in the CellGroupConfig IE. The UE performs the following actions based on a received CellGroupConfig IE: 1> if the CellGroupConfig contains the spCellConfig with reconfigurationWithSync: 2> perform Reconfiguration with sync according to 5.3.5.5.2; 2> resume all suspended radio bearers except the SRBs for the source cell group, and resume SCG transmission for all radio bearers, and resume BH RLC channels and resume SCG transmission for BH RLC channels for IAB-MT, if suspended; NOTE 1: If the SCG is deactivated, resuming SCG transmission for all radio bearers does not imply that PDCP PDUs can be transmitted or received on SCG RLC bearers. 1> if the CellGroupConfig contains the rlc-BearerToReleaseList or rlc-BearerToReleaseListExt: 2> perform RLC bearer release as specified in 5.3.5.5.3; 1> if the CellGroupConfig contains the rlc-BearerToAddModList: 2> perform the RLC bearer addition/modification as specified in 5.3.5.5.4; 1> if the CellGroupConfig contains the mac-CellGroupConfig: 2> configure the MAC entity of this cell group as specified in 5.3.5.5.5; 1> if the CellGroupConfig contains the sCellToReleaseList: 2> perform SCell release as specified in 5.3.5.5.8; 1> if the CellGroupConfig contains the spCellConfig: 2> configure the SpCell as specified in 5.3.5.5.7; 1> if the CellGroupConfig contains the sCellToAddModList: 2> perform SCell addition/modification as specified in 5.3.5.5.9; 1> if the CellGroupConfig contains the bh-RLC-ChannelToReleaseList: 2> perform BH RLC channel release as specified in 5.3.5.5.10; 1> if the CellGroupConfig contains the bh-RLC-ChannelToAddModList: 2> perform the BH RLC channel addition/modification as specified in 5.3.5.5.11; 1> if the CellGroupConfig contains the uu-RelayRLC-ChannelToReleaseList: 2> perform Uu Relay RLC channel release as specified in 5.3.5.5.12; 1> if the CellGroupConfig contains the uu-RelayRLC-ChannelToAddModList: 2> perform the Uu Relay RLC channel addition/modification as specified in 5.3.5.5.13; 1> if the CellGroupConfig contains the ncr-FwdConfig: 2> perform the NCR-Fwd configuration as specified in 5.3.5.5.14; 1> if the CellGroupConfig contains the autonomousDenialParameters: 2> consider itself to be allowed to deny any transmission in a particular UL slot if during the number of slots indicated by autonomousDenialValidity, preceding and including this particular slot, it autonomously denied fewer UL slots than indicated by autonomousDenialSlots within the same cell group; NOTE 2: When counting the number of denied UL slots, the UE sums up the denied UL slots across all serving cells within the same cell group. When counting the number of slots indicated by autonomousDenialValidity, the UE sums up the UL slots across all serving cells within the same cell group. NOTE 3: When multiple denied UL slots across all serving cells partially or fully overlap in the time domain, the number of denied UL slots across all serving cells is counted as one denied UL slot, based on the longest slot. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.5.5 |
1,871 | – BWP-UplinkCommon | The IE BWP-UplinkCommon is used to configure the common parameters of an uplink 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-UplinkCommon information element -- ASN1START -- TAG-BWP-UPLINKCOMMON-START BWP-UplinkCommon ::= SEQUENCE { genericParameters BWP, rach-ConfigCommon SetupRelease { RACH-ConfigCommon } OPTIONAL, -- Need M pusch-ConfigCommon SetupRelease { PUSCH-ConfigCommon } OPTIONAL, -- Need M pucch-ConfigCommon SetupRelease { PUCCH-ConfigCommon } OPTIONAL, -- Need M ..., [[ rach-ConfigCommonIAB-r16 SetupRelease { RACH-ConfigCommon } OPTIONAL, -- Need M useInterlacePUCCH-PUSCH-r16 ENUMERATED {enabled} OPTIONAL, -- Need R msgA-ConfigCommon-r16 SetupRelease { MsgA-ConfigCommon-r16 } OPTIONAL -- Cond SpCellOnly2 ]], [[ enableRA-PrioritizationForSlicing-r17 BOOLEAN OPTIONAL, -- Cond RA-PrioSliceAI additionalRACH-ConfigList-r17 SetupRelease { AdditionalRACH-ConfigList-r17 } OPTIONAL, -- Cond SpCellOnly2 rsrp-ThresholdMsg3-r17 RSRP-Range OPTIONAL, -- Need R numberOfMsg3-RepetitionsList-r17 SEQUENCE (SIZE (4)) OF NumberOfMsg3-Repetitions-r17 OPTIONAL, -- Cond Msg3Rep mcs-Msg3-Repetitions-r17 SEQUENCE (SIZE (8)) OF INTEGER (0..31) OPTIONAL -- Cond Msg3Rep ]], [[ additionalRACH-perPCI-ToAddModList-r18 SEQUENCE (SIZE (1.. maxNrofAdditionalPRACHConfigs-r18)) OF RACH-ConfigTwoTA-r18 OPTIONAL, -- Cond 2TA-Only additionalRACH-perPCI-ToReleaseList-r18 SEQUENCE (SIZE (1.. maxNrofAdditionalPRACHConfigs-r18)) OF RACH-ConfigTwoTAIndex-r18 OPTIONAL, -- Need N rsrp-ThresholdMsg1-RepetitionNum2-r18 RSRP-Range OPTIONAL, -- Cond Msg1Rep1 rsrp-ThresholdMsg1-RepetitionNum4-r18 RSRP-Range OPTIONAL, -- Cond Msg1Rep1 rsrp-ThresholdMsg1-RepetitionNum8-r18 RSRP-Range OPTIONAL, -- Cond Msg1Rep1 preambleTransMax-Msg1-Repetition-r18 ENUMERATED {n1, n2, n4, n6, n8, n10, n20, n50, n100, n200} OPTIONAL -- Cond Msg1Rep1 ]] } AdditionalRACH-ConfigList-r17 ::= SEQUENCE (SIZE(1..maxAdditionalRACH-r17)) OF AdditionalRACH-Config-r17 AdditionalRACH-Config-r17 ::= SEQUENCE { rach-ConfigCommon-r17 RACH-ConfigCommon OPTIONAL, -- Need R msgA-ConfigCommon-r17 MsgA-ConfigCommon-r16 OPTIONAL, -- Need R ... } NumberOfMsg3-Repetitions-r17::= ENUMERATED {n1, n2, n3, n4, n7, n8, n12, n16} -- TAG-BWP-UPLINKCOMMON-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
1,872 | 10.8.1 EN-DC | The Master Node to eNB Change procedure is used to transfer context data from a source MN/SN to a target eNB. Figure 10.8.1-1: Master Node to eNB Change procedure Figure 10.8.1-1 shows an example signalling flow for the Master Node to eNB Change procedure: 1. The source MN starts the MN to eNB Change procedure by initiating the X2 Handover Preparation procedure, including both MCG and SCG configuration. NOTE 1: The source MN may trigger the MN-initiated SN Modification procedure (to the source SN) to retrieve the current SCG configuration before step 1. 2. The target eNB includes the field in HO command which releases SCG configuration, and may also provide forwarding addresses to the source MN. 3. If the allocation of target eNB resources was successful, the MN initiates the release of the source SN resources towards the source SN including a Cause indicating MCG mobility. The SN acknowledges the release request. If data forwarding is needed, the MN provides data forwarding addresses to the source SN. Reception of the SgNB Release Request message triggers the source SN to stop providing user data to the UE and, if applicable, to start data forwarding. NOTE 1a: In case the handover is a conditional handover, step 3a and step 3b are performed after the source MN receives an indication that the UE has successfully accessed one of the potential target eNB(s) as described in step 11a in Figure 10.1.2.1a-1in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [2], i.e,. after step 6 in Figure 10.8.1-1. NOTE 1b: In case the handover is a conditional handover, the Data Forwarding Address Indication procedure is executed right after step 2. This Data Forwarding Address Indication procedure notifies conditional handover to the source SN, for which it may decide to perform, if applicable, early data forwarding for SN-terminated bearers, together with the sending of an EARLY STATUS TRANSFER message to the source MN. Separate Data Forwarding Address Indication procedures may be invoked to provide different forwarding addresses of the prepared conditional handovers. In this case, it is up to the source MN and SN implementations to make sure that the EARLY STATUS TRANSFER message(s) from the source SN, if any, is forwarded to the right target destination. The Data Forwarding Address Indication procedure may further be invoked to indicate to the source SN to stop already initiated early data forwarding for some SN-terminated bearers if they are no longer subject to data forwarding due to the modification or cancellation of the prepared conditional handovers. If applicable, the normal data forwarding and SN STATUS TRANSFER message would follow from the source SN once it receives the SgNB Release Request message of the step 3a that is performed after step 6. 4. The MN triggers the UE to apply the new configuration. Upon receiving the new configuration, the UE releases the entire SCG configuration. 5/6. The UE synchronizes to the target eNB. 7. For SN terminated bearers using RLC AM, the SN sends the SN Status Transfer message, which the source MN sends then to the target eNB. 8. If applicable, data forwarding takes place from the source side. 9a. The source SN sends the Secondary RAT Data Usagee Report message to the source MN and includes the data volumes delivered to and received from the UE over the NR radio for the related E-RABs. NOTE 2: The order the SN sends the Secondary RAT Data Usage Report message and performs data forwarding with MN is not defined. The SN may send the report when the transmission of the related bearer is stopped. 9b. The source MN sends the Secondary RAT Report message to MME to provide information on the used NR resource. 10-14. The target eNB initiates the S1 Path Switch procedure. 15. The target eNB initiates the UE Context Release procedure towards the source MN. 16. Upon reception of the UE Context Release message, the SN releases radio and C-plane related resources associated to the UE context. Any ongoing data forwarding may continue. NOTE 3: Inter-system HO from E-UTRA with EN-DC configuration to NR or to E-UTRA connected to 5GC is also supported. | 3GPP TS 37.340 | Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Overall Description; Stage-2 | RAN2 | 3GPP Series : 37 , Multiple radio access technology aspects | 10.8.1 |
1,873 | 5.8.6.2 Selection and reselection of synchronisation reference | The UE shall for frequency(ies) which have been selected for NR sidelink communication/discovery as specified in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3]: 1> if one frequency is selected for NR sidelink communication/discovery: 2> if sl-SyncFreqList is not included in RRCReconfiguration nor in SIB12; or 2> if sl-SyncFreqList is included in RRCReconfiguration or in SIB12, and none of the frequency(ies) selected as specified in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3] is included in the syncFreqList: 3> if the frequency used for NR sidelink communication/discovery is included in sl-FreqInfoToAddModList in sl-ConfigDedicatedNR within RRCReconfiguration message or included in sl-ConfigCommonNR within SIB12, and sl-SyncPriority is configured for the concerned frequency and set to gnbEnb: 4> select a cell as the synchronization reference source as defined in 5.8.6.3: NOTE 1: When an out of coverage L2 U2N Remote UE receives SIB12 with sl-SyncPriority set to gnbEnb, the L2 U2N Remote UE continues using the current synchronization source until higher priority synchronization source is found or the current synchronization source becomes unreliable. 3> else if the frequency used for NR sidelink communication/discovery is included in sl-FreqInfoToAddModList in sl-ConfigDedicatedNR within RRCReconfiguration message or included in sl-ConfigCommonNR within SIB12, and sl-SyncPriority for the concerned frequency is not configured or is set to gnss, and GNSS is reliable in accordance with TS 38.101[ None ] -1 [15] and TS 38.133[ NR; Requirements for support of radio resource management ] [14]: 4> select GNSS as the synchronization reference source; 3> else if the frequency used for NR sidelink communication/discovery is included in SL-PreconfigurationNR, and sl-SyncPriority in SidelinkPreconfigNR is set to gnss and GNSS is reliable in accordance with TS 38.101[ None ] -1 [15] and TS 38.133[ NR; Requirements for support of radio resource management ] [14]: 4> select GNSS as the synchronization reference source; 3> else: 4> perform a full search (i.e. covering all subframes and all possible SLSSIDs) to detect candidate SLSS, in accordance with TS 38.133[ NR; Requirements for support of radio resource management ] [14] 4> when evaluating the one or more detected SLSSIDs, apply layer 3 filtering as specified in 5.5.3.2 using the preconfigured sl-filterCoefficient in SL-SyncConfig, before using the PSBCH-RSRP measurement results; 4> if the UE has selected a SyncRef UE: 5> if the PSBCH-RSRP of the strongest candidate SyncRef UE exceeds the minimum requirement TS 38.133[ NR; Requirements for support of radio resource management ] [14] by sl-SyncRefMinHyst and the strongest candidate SyncRef UE belongs to the same priority group as the current SyncRef UE and the PSBCH-RSRP of the strongest candidate SyncRef UE exceeds the PSBCH-RSRP of the current SyncRef UE by syncRefDiffHyst; or 5> if the PSBCH-RSRP of the candidate SyncRef UE exceeds the minimum requirement TS 38.133[ NR; Requirements for support of radio resource management ] [14] by sl-SyncRefMinHyst and the candidate SyncRef UE belongs to a higher priority group than the current SyncRef UE; or 5> if GNSS becomes reliable in accordance with TS 38.101[ None ] -1 [15] and TS 38.133[ NR; Requirements for support of radio resource management ] [14], and GNSS belongs to a higher priority group than the current SyncRef UE; or 5> if a cell is detected and gNB/eNB (if sl-NbAsSync is set to true) belongs to a higher priority group than the current SyncRef UE; or 5> if the PSBCH-RSRP of the current SyncRef UE is less than the minimum requirement defined in TS 38.133[ NR; Requirements for support of radio resource management ] [14]: 6> consider no SyncRef UE to be selected; 4> if the UE has selected GNSS as the synchronization reference for NR sidelink communication/discovery: 5> if the PSBCH-RSRP of the candidate SyncRef UE exceeds the minimum requirement defined in TS 38.133[ NR; Requirements for support of radio resource management ] [14] by sl-SyncRefMinHyst and the candidate SyncRef UE belongs to a higher priority group than GNSS; or 5> if GNSS becomes not reliable in accordance with TS 38.101[ None ] -1 [15] and TS 38.133[ NR; Requirements for support of radio resource management ] [14]: 6> consider GNSS not to be selected; 4> if the UE has selected cell as the synchronization reference for NR sidelink communication/discovery: 5> if the PSBCH-RSRP of the candidate SyncRef UE exceeds the minimum requirement defined in TS 38.133[ NR; Requirements for support of radio resource management ] [14] by sl-SyncRefMinHyst and the candidate SyncRef UE belongs to a higher priority group than gNB/eNB; or 5> if the selected cell is not detected: 6> consider the cell not to be selected; 4> if the UE has not selected any synchronization reference: 5> if the UE detects one or more SLSSIDs for which the PSBCH-RSRP exceeds the minimum requirement defined in TS 38.133[ NR; Requirements for support of radio resource management ] [14] by sl-SyncRefMinHyst and for which the UE received the corresponding MasterInformationBlockSidelink message (candidate SyncRef UEs), or if the UE detects GNSS that is reliable in accordance with TS 38.101[ None ] -1 [15] and TS 38.133[ NR; Requirements for support of radio resource management ] [14], or if the UE detects a cell, select a synchronization reference according to the following priority group order: 6> if sl-SyncPriority corresponding to the concerned frequency is set to gnbEnb: 7> UEs of which SLSSID is part of the set defined for in coverage, and inCoverage, included in the MasterInformationBlockSidelink message received from this UE, is set to true, starting with the UE with the highest PSBCH-RSRP result (priority group 1); 7> UE of which SLSSID is part of the set defined for in coverage, and inCoverage, included in the MasterInformationBlockSidelink message received from this UE, is set to false, starting with the UE with the highest PSBCH-RSRP result (priority group 2); 7> GNSS that is reliable in accordance with TS 38.101[ None ] -1 [15] and TS 38.133[ NR; Requirements for support of radio resource management ] [14] (priority group 3); 7> UEs of which SLSSID is 0, and inCoverage, included in the MasterInformationBlockSidelink message received from this UE, is set to true, or of which SLSSID is 0 and SLSS is transmitted on slot(s) indicated by sl-SSB-TimeAllocation3, starting with the UE with the highest PSBCH-RSRP result (priority group 4); 7> UEs of which SLSSID is 0 and SLSS is not transmitted on slot(s) indicated by sl-SSB-TimeAllocation3, and inCoverage, included in the MasterInformationBlockSidelink message received from this UE, is set to false, starting with the UE with the highest PSBCH-RSRP result (priority group 5); 7> UEs of which SLSSID is 337 and inCoverage, included in the MasterInformationBlockSidelink message received from this UE, is set to false, starting with the UE with the highest PSBCH-RSRP result (priority group 5); 7> Other UEs, starting with the UE with the highest PSBCH-RSRP result (priority group 6); 6> if sl-SyncPriority corresponding to the concerned frequency is set to gnss, and sl-NbAsSync is set to true: 7> UEs of which SLSSID is 0, and inCoverage, included in the MasterInformationBlockSidelink message received from this UE, is set to true, or of which SLSSID is 0 and SLSS is transmitted on slot(s) indicated by sl-SSB-TimeAllocation3, starting with the UE with the highest PSBCH-RSRP result (priority group 1); 7> UEs of which SLSSID is 0 and SLSS is not transmitted on slot(s) indicated by sl-SSB-TimeAllocation3, and inCoverage, included in the MasterInformationBlockSidelink message received from this UE, is set to false, starting with the UE with the highest PSBCHS-RSRP result (priority group 2); 7> UEs of which SLSSID is 337 and inCoverage, included in the MasterInformationBlockSidelink message received from this UE, is set to false, starting with the UE with the highest PSBCH-RSRP result (priority group 2); 7> the cell detected by the UE as defined in 5.8.6.3 (priority group 3); 7> UEs of which SLSSID is part of the set defined for in coverage, and inCoverage, included in the MasterInformationBlockSidelink message received from this UE, is set to true, starting with the UE with the highest PSBCH-RSRP result (priority group 4); 7> UE of which SLSSID is part of the set defined for in coverage, and inCoverage, included in the MasterInformationBlockSidelink message received from this UE, is set to false, starting with the UE with the highest PSBCH-RSRP result (priority group 5); 7> Other UEs, starting with the UE with the highest S-RSRP result (priority group 6); 6> if sl-SyncPriority corresponding to the concerned frequency is set to gnss, and sl-NbAsSync is set to false: 7> UEs of which SLSSID is 0, and inCoverage, included in the MasterInformationBlockSidelink message received from this UE, is set to true, or of which SLSSID is 0 and SLSS is transmitted on slot(s) indicated by sl-SSB-TimeAllocation3, starting with the UE with the highest PSBCH-RSRP result (priority group 1); 7> UEs of which SLSSID is 0 and SLSS is not transmitted on slot(s) indicated by sl-SSB-TimeAllocation3, and inCoverage, included in the MasterInformationBlockSidelink message received from this UE, is set to false, starting with the UE with the highest PSBCHS-RSRP result (priority group 2); 7> UEs of which SLSSID is 337 and inCoverage, included in the MasterInformationBlockSidelink message received from this UE, is set to false, starting with the UE with the highest PSBCH-RSRP result (priority group 2); 7> Other UEs, starting with the UE with the highest PSBCH-RSRP result (priority group 3); 1> else if more than one frequency is selected for NR sidelink communication: 2> if sl-SyncFreqList is included in RRCReconfiguration or in SIB12, and includes at least one of the concerned frequency(ies) 3> if the concerned frequency(ies) are included in sl-FreqInfoToAddModList/sl-FreqInfoToAddModListExt in sl-ConfigDedicatedNR within RRCReconfiguration message or included in sl-ConfigCommonNR within SIB12, and sl-SyncPriority is configured for the concerned frequency(ies) and set to gnbEnb: 4> select one frequency from the concerned frequency(ies) which are included in sl-SyncFreqList as the synchronisation carrier frequency; 4> select a cell in accordance with the synchronisation carrier frequency as the synchronization reference source as defined in 5.8.6.3: 3> else if the concerned frequency(ies) are included in sl-FreqInfoToAddModList/sl-FreqInfoToAddModListExt in sl-ConfigDedicatedNR within RRCReconfiguration message or included in sl-ConfigCommonNR within SIB12, and sl-SyncPriority for concerned frequency(ies) are not configured or are set to gnss, and GNSS is reliable in accordance with TS 38.101[ None ] -1 [15] and TS 38.133[ NR; Requirements for support of radio resource management ] [14]; or if the concerned frequency(ies) are included in SL-PreconfigurationNR, and sl-SyncPriority in SidelinkPreconfigNR is set to gnss and GNSS is reliable in accordance with TS 38.101[ None ] -1 [15] and TS 38.133[ NR; Requirements for support of radio resource management ] [14]: 4> select one frequency from the concerned frequency(ies) which are included in sl-SyncFreqList as the synchronisation carrier frequency; 4> select GNSS in accordance with the synchronisation carrier frequency as the synchronization reference source; 3> else: 4> perform a full search (i.e. covering all subframes and all possible SLSSIDs) to detect candidate SLSS, in accordance with TS 38.133[ NR; Requirements for support of radio resource management ] [14] 4> when evaluating the one or more detected SLSSIDs, apply layer 3 filtering as specified in 5.5.3.2 using the preconfigured sl-filterCoefficient, before using the PSBCH-RSRP measurement results; 4> if the UE has selected a SyncRef UE: 5> if the PSBCH-RSRP of the strongest candidate SyncRef UE exceeds the minimum requirement TS 38.133[ NR; Requirements for support of radio resource management ] [14] by sl-SyncRefMinHyst and the strongest candidate SyncRef UE belongs to the same priority group as the current SyncRef UE and the PSBCH-RSRP of the strongest candidate SyncRef UE exceeds the PSBCH-RSRP of the current SyncRef UE by syncRefDiffHyst; or 5> if the PSBCH-RSRP of the candidate SyncRef UE exceeds the minimum requirement TS 38.133[ NR; Requirements for support of radio resource management ] [14] by sl-SyncRefMinHyst and the candidate SyncRef UE belongs to a higher priority group than the current SyncRef UE; or 5> if GNSS becomes reliable in accordance with TS 38.101[ None ] -1 [15] and TS 38.133[ NR; Requirements for support of radio resource management ] [14], and GNSS belongs to a higher priority group than the current SyncRef UE; or 5> if a cell is detected and gNB/eNB (if sl-NbAsSync is set to true) belongs to a higher priority group than the current SyncRef UE; or 5> if the PSBCH-RSRP of the current SyncRef UE is less than the minimum requirement defined in TS 38.133[ NR; Requirements for support of radio resource management ] [14]: 6> consider no SyncRef UE to be selected; 4> if the UE has selected GNSS as the synchronization reference for NR sidelink communication/discovery: 5> if the PSBCH-RSRP of the candidate SyncRef UE exceeds the minimum requirement defined in TS 38.133[ NR; Requirements for support of radio resource management ] [14] by sl-SyncRefMinHyst and the candidate SyncRef UE belongs to a higher priority group than GNSS; or 5> if GNSS becomes not reliable in accordance with TS 38.101[ None ] -1 [15] and TS 38.133[ NR; Requirements for support of radio resource management ] [14]: 6> consider GNSS not to be selected; 4> if the UE has selected cell as the synchronization reference for NR sidelink communication/discovery: 5> if the PSBCH-RSRP of the candidate SyncRef UE exceeds the minimum requirement defined in TS 38.133[ NR; Requirements for support of radio resource management ] [14] by sl-SyncRefMinHyst and the candidate SyncRef UE belongs to a higher priority group than gNB/eNB; or 5> if the selected cell is not detected: 6> consider the cell not to be selected; 4> if the UE has not selected any synchronization reference: 5> if the UE detects one or more SLSSIDs for which the PSBCH-RSRP exceeds the minimum requirement defined in TS 38.133[ NR; Requirements for support of radio resource management ] [14] by sl-SyncRefMinHyst and for which the UE received the corresponding MasterInformationBlockSidelink message (candidate SyncRef UEs), or if the UE detects GNSS that is reliable in accordance with TS 38.101[ None ] -1 [15] and TS 38.133[ NR; Requirements for support of radio resource management ] [14], or if the UE detects a cell, 6> select the synchronisation reference source(s) on each concerned frequency which is included in sl-SyncFreqList according to the following priority group order; 6> select the frequency with the highest synchronisation reference source priority as the synchronisation carrier frequency, according to the following priority group order, and consider the synchornization reference source (i.e. eNB/gNB, GNSS or SyncRef UE) that selected on the synchronisation carrier frequency as the synchronization reference: 7> if sl-SyncPriority corresponding to the concerned frequency is set to gnbEnb: 8> UEs of which SLSSID is part of the set defined for in coverage, and inCoverage, included in the MasterInformationBlockSidelink message received from this UE, is set to true, starting with the UE with the highest PSBCH-RSRP result (priority group 1); 8> UE of which SLSSID is part of the set defined for in coverage, and inCoverage, included in the MasterInformationBlockSidelink message received from this UE, is set to false, starting with the UE with the highest PSBCH-RSRP result (priority group 2); 8> GNSS that is reliable in accordance with TS 38.101[ None ] -1 [15] and TS 38.133[ NR; Requirements for support of radio resource management ] [14] (priority group 3); 8> UEs of which SLSSID is 0, and inCoverage, included in the MasterInformationBlockSidelink message received from this UE, is set to true, or of which SLSSID is 0 and SLSS is transmitted on slot(s) indicated by sl-SSB-TimeAllocation3, starting with the UE with the highest PSBCH-RSRP result (priority group 4); 8> UEs of which SLSSID is 0 and SLSS is not transmitted on slot(s) indicated by sl-SSB-TimeAllocation3, and inCoverage, included in the MasterInformationBlockSidelink message received from this UE, is set to false, starting with the UE with the highest PSBCH-RSRP result (priority group 5); 8> UEs of which SLSSID is 337 and inCoverage, included in the MasterInformationBlockSidelink message received from this UE, is set to false, starting with the UE with the highest PSBCH-RSRP result (priority group 5); 8> Other UEs, starting with the UE with the highest PSBCH-RSRP result (priority group 6); 7> if sl-SyncPriority corresponding to the concerned frequency is set to gnss, and sl-NbAsSync is set to true: 8> UEs of which SLSSID is 0, and inCoverage, included in the MasterInformationBlockSidelink message received from this UE, is set to true, or of which SLSSID is 0 and SLSS is transmitted on slot(s) indicated by sl-SSB-TimeAllocation3, starting with the UE with the highest PSBCH-RSRP result (priority group 1); 8> UEs of which SLSSID is 0 and SLSS is not transmitted on slot(s) indicated by sl-SSB-TimeAllocation3, and inCoverage, included in the MasterInformationBlockSidelink message received from this UE, is set to false, starting with the UE with the highest PSBCHS-RSRP result (priority group 2); 8> UEs of which SLSSID is 337 and inCoverage, included in the MasterInformationBlockSidelink message received from this UE, is set to false, starting with the UE with the highest PSBCH-RSRP result (priority group 2); 8> the cell detected by the UE as defined in 5.8.6.3 (priority group 3); 8> UEs of which SLSSID is part of the set defined for in coverage, and inCoverage, included in the MasterInformationBlockSidelink message received from this UE, is set to true, starting with the UE with the highest PSBCH-RSRP result (priority group 4); 8> UE of which SLSSID is part of the set defined for in coverage, and inCoverage, included in the MasterInformationBlockSidelink message received from this UE, is set to false, starting with the UE with the highest PSBCH-RSRP result (priority group 5); 8> Other UEs, starting with the UE with the highest S-RSRP result (priority group 6); 7> if sl-SyncPriority corresponding to the concerned frequency is set to gnss, and sl-NbAsSync is set to false: 8> UEs of which SLSSID is 0, and inCoverage, included in the MasterInformationBlockSidelink message received from this UE, is set to true, or of which SLSSID is 0 and SLSS is transmitted on slot(s) indicated by sl-SSB-TimeAllocation3, starting with the UE with the highest PSBCH-RSRP result (priority group 1); 8> UEs of which SLSSID is 0 and SLSS is not transmitted on slot(s) indicated by sl-SSB-TimeAllocation3, and inCoverage, included in the MasterInformationBlockSidelink message received from this UE, is set to false, starting with the UE with the highest PSBCHS-RSRP result (priority group 2); 8> UEs of which SLSSID is 337 and inCoverage, included in the MasterInformationBlockSidelink message received from this UE, is set to false, starting with the UE with the highest PSBCH-RSRP result (priority group 2); 8> Other UEs, starting with the UE with the highest PSBCH-RSRP result (priority group 3); NOTE 2: How the UE achieves subframe boundary alignment between V2X sidelink communication and NR sidelink communication/discovery (if both are performed by the UE) is as specified in TS 38.213[ NR; Physical layer procedures for control ] , clause 16.7. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.8.6.2 |
1,874 | 4.23.6.3 Reporting UP path change to the AF | Figure 4.23.6.3-1 shows procedures related Reporting UP path change to the AF. Figure 4.23.6.3-1: Reporting UP path change to the AF 1a. I-SMF indicates that UP path change may occur for the PDU Session via Nsmf_PDUSession_Update Request as described in clause 4.23.9; the SMF responds to the I-SMF. 2. If early notification has been requested by a PCC rule on behalf of AF as described in clause 4.3.6.2, then the SMF notifies the AF accordingly by invoking Nsmf_EventExposure_Notify service operation as described in clause 4.3.6.3. In this case the SMF may wait for further instructions of the AF. 3. SMF initiates Nsmf_PDUSession_Update Request with N4 information to control the local PSA and ULCL/BP as described in clause 4.23.9. 4. I-SMF enforces the change of DNAI or addition, change, or removal of UPF as described in clause 4.23.9. 5 I-SMF answers back to the Nsmf_PDUSession_Update from the SMF. 6. If late notification has been requested by a PCC rule on behalf of AF as described in clause 4.3.6.2, then the SMF notifies the AF accordingly by invoking Nsmf_EventExposure_Notify service operation as described in clause 4.3.6.3. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.23.6.3 |
1,875 | 5.3.1.1 RRC connection control | RRC connection establishment involves the establishment of SRB1. The network completes RRC connection establishment prior to completing the establishment of the NG connection, i.e. prior to receiving the UE context information from the 5GC. Consequently, AS security is not activated during the initial phase of the RRC connection. During this initial phase of the RRC connection, the network may configure the UE to perform measurement reporting, but the UE only sends the corresponding measurement reports after successful AS security activation. However, the UE only accepts a re-configuration with sync message when AS security has been activated. Upon receiving the UE context from the 5GC, the RAN activates AS security (both ciphering and integrity protection) using the initial AS security activation procedure. The RRC messages to activate AS security (command and successful response) are integrity protected, while ciphering is started only after completion of the procedure. That is, the response to the message used to activate AS security is not ciphered, while the subsequent messages (e.g. used to establish SRB2, DRBs and multicast MRBs) are both integrity protected and ciphered. After having initiated the initial AS security activation procedure, the network may initiate the establishment of SRB2 and DRBs and/or multicast MRBs, i.e. the network may do this prior to receiving the confirmation of the initial AS security activation from the UE. In any case, the network will apply both ciphering and integrity protection for the RRC reconfiguration messages used to establish SRB2, DRBs and/or multicast MRBs. The network should release the RRC connection if the initial AS security activation and/ or the radio bearer establishment fails. A configuration with SRB2 without DRB or multicast MRB, or with DRB or multicast MRB without SRB2 is not supported (i.e., SRB2 and at least one DRB or multicast MRB must be configured in the same RRC Reconfiguration message, and it is not allowed to release all the DRBs and multicast MRBs without releasing the RRC Connection). For IAB-MT and NCR-MT, a configuration with SRB2 without any DRB/MRB is supported. The release of the RRC connection normally is initiated by the network. The procedure may be used to re-direct the UE to an NR frequency or an E-UTRA carrier frequency. The suspension of the RRC connection is initiated by the network. When the RRC connection is suspended, the UE stores the UE Inactive AS context and any configuration received from the network, and transits to RRC_INACTIVE state. The RRC message to suspend the RRC connection is integrity protected and ciphered. The resumption of a suspended RRC connection is initiated by upper layers when the UE needs to transit from RRC_INACTIVE state to RRC_CONNECTED state or by RRC layer to perform a RNA update or by RAN paging from NG-RAN or for SDT. When the RRC connection is resumed, network configures the UE according to the RRC connection resume procedure based on the stored UE Inactive AS context and any RRC configuration received from the network. The RRC connection resume procedure re-activates AS security and re-establishes SRB(s) and DRB(s) and/or multicast MRB(s), if configured. Upon initiating the resume procedure for SDT, AS security (both ciphering and integrity protection) is re-activated for SRB2 (if configured for SDT) and for SRB1. In addition, AS security is also re-activated (if security is configured) for all the DRBs configured for SDT. Further, the PDCP entities of SRB1 and PDCP entities of the radio bearers configured for SDT are re-established and resumed whilst the UE remains in RRC_INACTIVE state. Transmission and reception of data and/or signalling messages over radio bearers configured for SDT can happen whilst the UE is in RRC_INACTIVE state and SDT procedure is ongoing. In response to a request to resume the RRC connection or in response to a resume procedure initiated for SDT, the network may resume the suspended RRC connection and send UE to RRC_CONNECTED, or reject the request to resume and send UE to RRC_INACTIVE (with a wait timer), or directly re-suspend the RRC connection and send UE to RRC_INACTIVE, or directly release the RRC connection and send UE to RRC_IDLE, or instruct the UE to initiate NAS level recovery (in this case the network sends an RRC setup message). NOTE: In case the UE receives the configurations for NR sidelink communication via the E-UTRA, the configurations for NR sidelink communication in SIB12 and sl-ConfigDedicatedNR within RRCReconfiguration used in clause 5.3 are provided by the configurations in SystemInformationBlockType28 and sl-ConfigDedicatedForNR within RRCConnectionReconfiguration as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10], respectively. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.1.1 |
1,876 | 16.3a.1 Authentication, Authorization and Accounting procedures | When a P-GW receives an initial access request (e.g. Create Session Request or Proxy Binding Update) message for a given APN, the P-GW may (depending on the configuration for this APN) send a RADIUS Access-Request to an AAA server. The AAA server authenticates and authorizes the user. If the RADIUS server is also responsible for IPv4 address and/or IPv6 prefix allocation, the AAA server shall return the allocated IPv4 address and/or IPv6 prefix in the Access-Accept message. When PDN type is IPv4v6 and deferred IPv4 addressing via IPv4 address pool in the AAA server is used, the P-GW may intiate RADIUS re-authorization procedures after successful initial attach for the purpose of IPv4 address allocation or to renew the lease for a previously allocated IPv4 address. In this case, the P-GW shall set the Service-Type attribute to "Authorize Only" and the 3GPP-Allocate-IP-Type subattribute to the type of IP address to be allocated in the Access-Request message sent to the AAA server. See subclause 16.4.7.2 for the conditions to use 3GPP-Allocate-IP-Type sub-attribute in Access-Request messages. If the P-GW is using DHCPv4 signalling towards the UE and the RADIUS server includes the Session-Timeout attribute in the Access-Accept, the P-GW may use the Session-Timeout value as the DHCPv4 lease time. The P-GW shall not set the DHCPv4 lease time value higher than the Session-Timeout value. The P-GW may renew the DHCP lease to the UE without re-authorization towards the AAA server providing that the new lease expiry is no later than the Session-Timeout timer expiry. If the P-GW wishes to extend the lease time beyond the current Session-Timeout expiry, it shall initiate a new AAA re-authorization. Even if the P-GW was not involved in user authentication, it may send a RADIUS Accounting-Request (START) message to an AAA server. This message may contain parameters, e.g. the tuple which includes the user-id and IPv4 address and/or IPv6 prefix, to be used by application servers (e.g. WAP gateway) in order to identify the user. This message also indicates to the AAA server that the user session has started. The session is uniquely identified by the Acct-Session-Id that is composed of the Charging-Id and the PGW-Address. If some external applications require RADIUS Accounting-Request (START) information before they can process user packets, then the selected APN (P-GW) may be configured in such a way that the P-GW drops user data until the Accounting-Response (START) is received from the AAA server. The P-GW may wait for the Accounting-Response (START) before sending the initial access response (e.g. Create Session Response or Proxy Binding Acknowledgement). The P-GW may reject the initial access request if the Accounting-Response (START) is not received. The authentication and accounting servers may be separately configured for each APN. For PDN type IPv4, at IPv4 address allocation via DHCPv4 signalling between the UE and the PDN, no IPv4 address is available at initial access. In that case the P-GW may wait to send the Accounting-Request (START) message until the UE receives its IPv4 address in a DHCPACK. For PDN type IPv4v6 and deferred IPv4 addressing, when the IPv4 address is allocated or re-allocated, the accounting session that was established for the IPv6 prefix allocation shall be used to inform the accounting server about the allocated IPv4 address by sending RADIUS Accounting-Request Interim-Update with the Framed-IP-Address attribute and its value field containing the allocated IPv4 address. When the P-GW receives a message indicating a bearer deactivation request or PDN disconnection request or detach request (e.g. Delete Bearer Command or Proxy Binding Update with lifetime equal 0) and providing a RADIUS Accounting-Request (START) message was sent previously, the P-GW shall send a RADIUS Accounting-Request (STOP) message to the AAA server, which indicates the termination of this particular bearer or user session. The P-GW shall immediately send the corresponding response (e.g. Delete Bearer Request or Proxy Binding Ack with lifetime equal 0) to the peer node (e.g. S-GW) in the Packet Domain, without waiting for an Accounting-Response (STOP) message from the AAA server. The AAA server shall deallocate the IPv4 address and/or IPv6 prefix initially allocated to the subscriber, if there is no session for the subscriber. For PDN type IPv4v6 and deferred IPv4 addressing, when the P-GW receives a message from the UE or the network indicating the release of the IPv4 address (e.g. receiving DHCPRELEASE) or decides to release the IPv4 address on its own (e.g. due to DHCP lease timer expiry or P-GW assigned IPv4 address), the P-GW shall inform the accounting server about the deallocation of the IPv4 address by sending RADIUS Accounting-Request Interim-Update without the Framed-IP-Address attribute. Accounting-Request (ON) and Accounting-Request (OFF) messages may be sent from the P-GW to the AAA server to ensure the correct synchronization of the session information in the P-GW and the AAA server. The P-GW may send an Accounting-Request (ON) message to the AAA server to indicate that a restart has occurred. The AAA server may then release the associated resources. Prior to a scheduled restart, the P-GW may send Accounting-Request (OFF) message to the AAA server. The AAA server may then release the associated resources. If an Access-Challenge is sent to the P-GW when an Access-Request message is pending, the P-GW shall silently discard the Access-Challenge message and it shall treat an Access-Challenge as though it had received an Access-Reject instead RFC 2865 [38]. For example, figure 25a.1 represents the RADIUS message flows between a P-GW and an Authentication, Authorization and Accounting (AAA) server, which is applicable for GTP based S5/S8: NOTE 1: If some external applications require RADIUS Accounting request (Start) information before they can process user packets, then the selected APN (P-GW) may be configured in such a way that the P-GW drops user data until the Accounting Response (START) is received from the AAA server. The P-GW may wait for the Accounting Response (START) before sending the Create Session Response. The P-GW may reject the bearer if the Accounting Response (START) is not received. NOTE 2: Separate accounting and authentication servers may be used. Figure 25a.1: An example of RADIUS message flow on Sgi interface for GTP-based S5/S8 (successful user authentication case) | 3GPP TS 29.061 | Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) | CT WG3 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 16.3a.1 |
1,877 | 5.3.3.3 Actions related to transmission of RRCSetupRequest message | The UE shall set the contents of RRCSetupRequest message as follows: 1> set the ue-Identity as follows: 2> if upper layers provide a 5G-S-TMSI: 3> set the ue-Identity to ng-5G-S-TMSI-Part1; 2> else: 3> draw a 39-bit random value in the range 0..239-1 and set the ue-Identity to this value; NOTE 1: Upper layers provide the 5G-S-TMSI if the UE is registered in the TA of the current cell. 1> if the establishment of the RRC connection is the result of release with redirect with mpsPriorityIndication (either in NR or E-UTRAN): 2> set the establishmentCause to mps-PriorityAccess; 1> else: 2> set the establishmentCause in accordance with the information received from upper layers; NOTE 2: In case the L2 U2N Relay UE initiates RRC connection establishment triggered by reception of message from a L2 U2N Remote UE via SL-RLC0 or SL-RLC1 as specified in 5.3.3.1a, the L2 U2N Relay UE sets the establishmentCause by implementation, but it can only set the emergency, mps-PriorityAccess, or mcs-PriorityAccess as establishmentCause if the same cause value is in the message received from the L2 U2N Remote UE via SL-RLC0. 1> if ta-Report or ta-ReportATG is configured with value enabled and the UE supports TA reporting: 2> indicate TA report initiation to lower layers; The UE shall submit the RRCSetupRequest message to lower layers for transmission. If the UE is an (e)RedCap UE and the (e)RedCap-specific initial downlink BWP is not associated with CD-SSB, the UE may continue cell re-selection related measurements as well as cell re-selection evaluation, otherwise the UE shall continue cell re-selection related measurements as well as cell re-selection evaluation. If the conditions for cell re-selection are fulfilled, the UE shall perform cell re-selection as specified in 5.3.3.6. NOTE 3: For L2 U2N Remote UE in RRC_IDLE, the cell (re)selection procedure as specified in TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [20] and relay (re)selection procedure as specified in 5.8.15.3 are performed independently and up to UE implementation to select either a cell or a L2 U2N Relay UE. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.3.3 |
1,878 | 5.2.2.4 Notification of interworking in connection with mobile terminating call establishment | In this subclause, the term "interworking" is used only in the meaning of interworking with a network other than PLMN or ISDN, not as interworking between PLMN and ISDN since this is the normal case. In this sense, PLMN and ISDN are seen within the same environment, called the PLMN/ISDN environment. During call establishment the call may enter an PLMN/ISDN environment, e.g., because of interworking with another network, with a non-PLMN/ISDN user, or with non-PLMN/ISDN equipment within the calling or called user's premises. When this occurs, the network may include a progress indicator information element to be included in the SETUP message to be sent to the called mobile station specifying progress description value: a) #1 "call is not end-to-end PLMN/ISDN; further call progress information may be available in-band" or b) #3 "origination address is non-PLMN/ISDN". See also subclause 5.5.1 for further reactions of the mobile station. | 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.2.4 |
1,879 | 5.8.10.4.3 Event S2 (Serving becomes worse than threshold) | The UE shall: 1> consider the entering condition for this event to be satisfied when condition S2-1, as specified below, is fulfilled; 1> consider the leaving condition for this event to be satisfied when condition S2-2, as specified below, is fulfilled; 1> for this NR sidelink measurement, consider the NR sidelink frequency indicated by the sl-MeasObject associated to this event. Inequality S2-1 (Entering condition) Ms + Hys < Thresh Inequality S2-2 (Leaving condition) Ms – Hys > Thresh The variables in the formula are defined as follows: Ms is the NR sidelink measurement result of the NR sidelink frequency, not taking into account any offsets. Hys is the hysteresis parameter for this event (i.e. sl-Hysteresis as defined within sl-ReportConfig for this event). Thresh is the threshold parameter for this event (i.e. s2-Threshold as defined within sl-ReportConfig for this event). Ms is expressed in dBm in case of RSRP. Hys is expressed in dB. Thresh is expressed in the same unit as Ms. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.8.10.4.3 |
1,880 | 4.5.5.3 Distribution of RACH access delay | This measurement provides the distribution of number of the time before UEs in a cell achieve a successful attach. The RACH access delay is the time from when a UE sends its first Random Access Preamble until the UE receives the Random Access Response. CC This measurement is obtained by incrementing the measurement bin corresponding to the access delay experienced by the UE. The access delay is calculated based upon the value of IE numberOfPreamblesSent and IE contentionDetected reported by UE inside UEInformationResponse message ([8] clause 6.2.2). The measurement is incremented each time a UEInformationResponse message containing rach-Report-r9 IE is received. Each measurement is an integer value. RRU.RachAccessDelayDist.BinX where BinX represents the bin. Note: Number of bins and the range for each bin is left to implementation. EUtranCellFDD EUtranCellTDD Valid for packet switched traffic EPS | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.5.5.3 |
1,881 | 5.1.6 Completion of the Random Access procedure | At completion of the Random Access procedure, the MAC entity shall: - discard explicitly signalled ra-PreambleIndex and ra-PRACH-MaskIndex, if any; - flush the HARQ buffer used for transmission of the MAC PDU in the Msg3 buffer. Upon successful completion of the Random Access procedure initiated for DAPS handover, the target MAC entity shall: - indicate the successful completion of the Random Access Procedure to the upper layers. In addition, the RN shall resume the suspended RN subframe configuration, if any. | 3GPP TS 36.321 | Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification | RAN2 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 5.1.6 |
1,882 | 5.5.2.2 Measurement identity removal | The UE shall: 1> for each measId included in the received measIdToRemoveList that is part of the current UE configuration in VarMeasConfig: 2> remove the entry with the matching measId from the measIdList within the VarMeasConfig; 2> remove the measurement reporting entry for this measId from the VarMeasReportList, if included; 2> stop the periodical reporting timer or timer T321 or timer T322, whichever one is running, and reset the associated information (e.g. timeToTrigger) for this measId. 2> if the reportType is set to reportOnActivation in the reportConfig associated with this measId: 3> indicate to lower layer to disable the measurement reporting for fast unknown SCell activation. NOTE: The UE does not consider the message as erroneous if the measIdToRemoveList includes any measId value that is not part of the current UE configuration. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.5.2.2 |
1,883 | 5.15.4.1.2 Mapping of S-NSSAIs values in the Allowed NSSAI and in the Requested NSSAI to the S-NSSAIs values used in the HPLMN | For the roaming case, one or more S-NSSAIs in an Allowed NSSAI provided to the UE can have values which are not part of the UE's current Network Slice configuration information for the Serving PLMN. In this case, the network provides the Allowed NSSAI together with the mapping of each S-NSSAI of the Allowed NSSAI to the corresponding S-NSSAI of the HPLMN. This mapping information allows the UE to associate Applications to S-NSSAIs of the HPLMN as per NSSP of the URSP rules or as per the UE Local Configuration, as defined in clause 6.1.2.2.1 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45] and to the corresponding S-NSSAI from the Allowed NSSAI. In the non-roaming case, the network shall not provide any mapped S-NSSAI to the UE with the Allowed NSSAI. In roaming case, the UE shall provide in the Requested NSSAI the mapping of S-NSSAIs of the Serving PLMN values to the corresponding S-NSSAI values of the HPLMN, for each S-NSSAI in the Requested NSSAI for which a mapping is available. These values are found in the mapping previously received from the Serving PLMN of the S-NSSAIs of the Configured NSSAI for the Serving PLMN or of the S-NSSAIs of the Allowed NSSAI for the Serving PLMN and Access Type to the corresponding S-NSSAIs values used in the HPLMN. If the AMF provides Partially Allowed NSSAI to the UE, in roaming case the AMF may provide the mapping information of each S-NSSAI of the Partially Allowed NSSAI to the corresponding HPLMN S-NSSAI as described in clause 5.15.17. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.15.4.1.2 |
1,884 | 13.4.1.2.2 Service Request Process | The complete service request is two-step process including requesting an access token by NF Service Consumer (Step 1, i.e. 1a or 1b), and then verification of the access token by NF Service Producer (Step 2). Step 1: Access token request Pre-requisite: - The NF Service consumer (OAuth2.0 client) is registered with the vNRF (Authorization Server in the vPLMN). - The hNRF and NF Service Producer share the required credentials. Additionally, the NF Service Producer (OAuth2.0 resource server) is registered with the hNRF (Authorization Server in the hPLMN) with optionally "additional scope" information per NF type. - The two NRFs are implicitly authenticated via N32 mutual authentication of SEPPs. NOTE: vSEPP to hSEPP communication is secured via N32. Only transitive trust between vNRF and hNRF can be achieved: The vNRF and vSEPP mutually authenticate, the vSEPP and hSEPP mutually authenticate, and the hSEPP and hNRF mutually authenticate. Hence, vNRF and hNRF can only implicitly authenticate each other. - The NRF in the serving PLMN (vNRF) has authenticated the NF Service Consumer. – where the NF Service Consumer is identified by the NF Instance ID of the public key certificate of the NF Service Consumer. For SNPNs with Credentials Holder using AUSF and UDM for primary authentication, the NF Service Consumer and the vNRF are located in the SNPN while the hNRF is located in the Credentials Holder. 1a. Access token request for accessing services of NF Service Producers of a specific NF type The following procedure describes how the NF Service Consumer obtains an access token for NF Service Producers of a specific NF type for use in the roaming scenario. Figure 13.4.1.2.2-1: NF Service Consumer obtaining access token before NF Service access (roaming) 1. The NF Service Consumer shall invoke Nnrf_AccessToken_Get Request (NF Instance Id of the NF Service Consumer, the requested "scope" including the expected NF Service Name (s) and optionally "additional scope" information (i.e. requested resources and requested actions (service operations) on the resources), NF Type of the expected NF Service Producer instance, NF type of the NF Service Consumer, home and serving PLMN IDs, optionally list of NSSAIs or list of NSI IDs for the expected NF Service Producer instances, optionally NF Set ID and/or the NF Service Set ID of the expected NF Service Producer) from NRF in the same PLMN. For SNPNs with Credentials Holder using AUSF and UDM for primary authentication, the SNPN ID of the serving SNPN is included instead of the serving PLMN ID and the SNPN ID or the PLMN ID of the Credentials Holder is included instead of the home PLMN ID. 2. The NRF in serving PLMN shall identify the NRF in home PLMN (hNRF) based on the home PLMN ID, and request an access token from hNRF as described in clause 4.17.5 of TS 23.502[ Procedures for the 5G System (5GS) ] [8]. The vNRF shall forward the parameters it obtained from the NF Service Consumer, including NF Service Consumer type, to the hNRF. 3. The hNRF checks whether the NF Service Consumer is authorized to access the requested service(s). If the NF Service Consumer is authorized, the hNRF shall generate an access token with appropriate claims included as defined in clause 13.4.1.1. The hNRF shall digitally sign the generated access token based on a shared secret or private key as described in RFC 7515 [45]. If the NF service consumer is not authorized, the hNRF shall not issue an access token to the NF Service Consumer. The claims in the token shall include the NF Instance Id of NRF (issuer), NF Instance Id of the NF Service Consumer appended with its PLMN ID (subject), NF type of the NF Service Producer appended with its PLMN ID (audience), expected services name(s), (scope) and expiration time (expiration), and optionally "additional scope" information (allowed resources and allowed actions (service operations) on the resources). The claims may include a list of NSSAIs or NSI IDs for the expected NF Service Producer instances. The claims may include the NF Set ID and/or the NF Service Set ID of the expected NF Service Producer instances. For SNPNs with Credentials Holder using AUSF and UDM for primary authentication, the SNPN ID of the serving SNPN is included instead of the NF Service Consumer's PLMN ID and the SNPN ID or the PLMN ID of the Credentials Holder is included instead of the NF Service Producer's PLMN ID. 4. If the authorization is successful, the access token shall be included in Nnrf_AccessToken_Get Response message to the vNRF. Otherwise it shall reply based on Oauth 2.0 error response defined in RFC 6749 [43]. 5. The vNRF shall forward the Nnrf_AccessToken_Get Response or error message to the NF Service Consumer. The NF Service Consumer may store the received token(s). Stored tokens may be re-used for accessing service(s) from NF Service Producer NF type listed in claims (scope, audience) during their validity time. The other parameters (e.g., the expiration time, allowed scope) sent by NRF in addition to the access token are described in TS 29.510[ 5G System; Network function repository services; Stage 3 ] [68]. 1b. Obtain access token for accessing services of a specific NF Service Producer instance / NF Service Producer service instance The following steps describes how the NF Service Consumer obtains an access token before service access to a specific NF Service Producer instance / NF Service Producer service instance. 1. The NF Service Consumer shall request an access token from the NRF for a specific NF Service Producer instance / NF Service Producer service instance. The request shall include the NF Instance Id of the requested NF Service Producer, appended with its PLMN ID, the expected NF service name and NF Instance Id of the NF Service Consumer, appended with its PLMN ID. For SNPNs with Credentials Holder using AUSF and UDM for primary authentication, the SNPN ID of the serving SNPN is included instead of the NF Service Consumer's PLMN ID and the SNPN ID or the PLMN ID of the Credentials Holder is included instead of the NF Service Producer's PLMN ID. 2. The NRF in the visiting PLMN shall forward the request to the NRF in the home PLMN. 3. The NRF in the home PLMN checks whether the NF Service Consumer is authorized to access the requested services from the NF Service Producer instance/NF Service Producer service instance and shall then proceed to generate an access token with the appropriate claims included. If the NF Service Consumer is not authorized, the NRF in the home PLMN shall not issue an access token to the NF Service Consumer. The claims in the token shall include the NF Instance Id of NRF (issuer), NF Instance Id of the NF Service Consumer appended with its PLMN ID (subject), NF Instance Id of the requested NF Service Producer appended with its PLMN ID (audience), expected service name(s) (scope) and expiration time (expiration). For SNPNs with Credentials Holder using AUSF and UDM for primary authentication, the SNPN ID of the serving SNPN is included instead of the NF Service Consumer's PLMN ID and the SNPN ID or the PLMN ID of the Credentials Holder is included instead of the NF Service Producer's PLMN ID. 4. The token shall be included in the Nnrf_AccessToken_Get response sent to the NRF in the visiting PLMN. 5. The NRF in the visiting PLMN shall forward the Nnrf_AccessToken_Get response message to the NF Service Consumer. The NF Service Consumer may store the received token(s). Stored tokens may be re-used for accessing service(s) from NF Instance Id or several NF Instance Id(s) of the requested NF Service Producer listed in claims (scope, audience) during their validity time. Step 2: Service access request based on token verification In addition to the steps described in the non-roaming scenario in 13.4.1.1, the NF Service Producer shall verify that the PLMN-ID (or SNPN ID) contained in the API request is equal to the one inside the access token. Figure 13.4.1.2.2-2: NF Service Consumer requesting service access with an access token in roaming case The NF Service Producer shall check that the home PLMN ID of audience claim in the access token matches its own PLMN identity. For SNPNs with Credentials Holder using AUSF and UDM for primary authentication, the NF Service Producer verifies the SNPN ID of the serving SNPN contained in the API request instead of the PLMN-ID, and the SNPN ID or the PLMN ID of the Credentials Holder instead of the home PLMN ID. The pSEPP shall check that the serving PLMN ID of subject claim in the access token matches the remote PLMN ID. If PRINS is used, this can be achieved by the pSEPP checking the PLMN ID of the serving network in the access token against the PLMN ID(s) in the N32-f context. If the peer network is an SNPN, the pSEPP shall check that the SNPN ID of the NF Service Consumer in the access token matches the SNPN ID of the peer network. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 13.4.1.2.2 |
1,885 | 4.8.2.2a Network Triggered Connection Resume in RRC_INACTIVE procedure | The Network Triggered Connection Resume in RRC_INACTIVE procedure is used when the NG-RAN needs to send data (e.g. the N1 NAS PDU and/or downlink user plane PDU) to a UE in the RRC_INACTIVE state. During the procedure, the NG-RAN sends a RAN Paging to the UE in order to trigger the Connection Resume in RRC_INACTIVE procedure in clause 4.8.2.2. Figure 4.8.2.2a-1: Network Triggered Connection Resume for UE in RRC_INACTIVE 1. The NG-RAN receives downlink data (e.g. the N1 NAS PDU and/or the user plane PDU) for a UE in RRC_INACTIVE State, the NG-RAN buffers the downlink data and triggers RAN Paging message. If the NG RAN supports the Paging Cause Indication for Voice Service feature and if the UE context in NG-RAN indicates that the UE supports the Paging Cause Indication for Voice Service feature, the NG RAN shall provide the Voice Service Indication in the RAN Paging message for the UE when it detects that the downlink data which triggers the RAN Paging message is related to voice service, as specified in clause 5.38.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. 2. The NG-RAN sends the RAN Paging message to the UE. 3. If the UE is in RRC_INACTIVE State, based on the RAN paging and the UE decides to accept the paging, the UE initiates the UE Triggered Connection Resume in RRC_INACTIVE procedure (see clause 4.8.2.2). | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.8.2.2a |
1,886 | 8.2.6.18 Payload container | Within a PLMN, this IE shall be included if: a) the UE has one or more stored UE policy sections identified by a UPSI with the PLMN ID part indicating the HPLMN or the selected PLMN for the registration procedure for mobility and periodic registration update due to inter-system change from S1 mode to N1 mode of a UE operating in the single-registration mode or for the registration procedure for initial registration; or b) the UE does not have any stored UE policy section identified by a UPSI with the PLMN ID part indicating the HPLMN or the selected PLMN for the registration procedure for mobility and periodic registration update due to inter-system change from S1 mode to N1 mode of a UE operating in the single-registration mode or for the registration procedure for initial registration and the UE needs to send a UE policy container to the network. Within an SNPN, this IE shall be included if: a) the UE has one or more stored UE policy sections for the selected SNPN for the registration procedure for initial registration; or b) the UE does not have any UE policy section for the selected SNPN for the registration procedure for initial registration and the UE needs to send a UE policy container to the network. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 8.2.6.18 |
1,887 | 5.3.19 Handling of congestion control for transport of user data via the control plane | The network may activate congestion control for transport of user data via the control plane, as specified in 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8]. If the UE has indicated support for the control plane CIoT 5GS optimizations and the network decides to activate the congestion control for transport of user data via the control plane, the network may include a value for the control plane data back-off timer T3448 in REGISTRATION ACCEPT, SERVICE ACCEPT or SERVICE REJECT message, and shall store an control plane data back-off time on a per UE basis. The UE starts the timer T3448 with the value informed in the message. To avoid that large numbers of UEs simultaneously initiate deferred requests, the network should select the value for the timer T3448 for the informed UEs so that timeouts are not synchronised. The network sends REGISTRATION ACCEPT message or SERVICE ACCEPT message without T3448 value IE to stop the timer T3448 running in the UE as specified in subclause 5.5.1.3.4 and subclause 5.6.1.4. Based on the stored control plane data back-off time for the UE, the network may reject the transfer of user data via the control plane initiated by the UE. While the timer T3448 is running, the UE in 5GMM-IDLE mode does not initiate the transport of user data via the control plane procedure, except if the UE is allowed to use exception data reporting (see the ExceptionDataReportingAllowed leaf of the NAS configuration MO in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [17] or the USIM file EFNASCONFIG in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [22]) and the user data is related to an exceptional event. The UE is allowed: a) to respond to paging with CONTROL PLANE SERVICE REQUEST message without uplink data; or b) to send a CONTROL PLANE SERVICE REQUEST message for emergency services or for emergency services fallback; even if the timer T3448 is running. Upon entering the state 5GMM-DEREGISTERED or a new PLMN which is not equivalent to the PLMN where the UE started the timer T3448, or upon being switched off while the timer T3448 is running, the UE stops the timer T3448. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.3.19 |
1,888 | 4.15.6.9.2 Processing AF requests to influence access and mobility management policies targeting an individual UE | This procedure is used for individual UEs when the request shall be applied independently of conditions related to the application traffic. Depending on the AF deployment (see clause 6.2.10 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]), the AF may interact with NFs of the Core Network either directly or via the NEF. The procedure for the direct case is described in Figure 4.15.6.9.2-1, while the procedure for the NEF-mediated case is described in Figure 4.15.6.9.2-2. Figure 4.15.6.9.2-1: Handling an AF request targeting an individual UE without using NEF This procedure concerns only non-roaming scenarios, i.e. to cases where the involved entities serving the UE (AF, PCF, BSF, AMF) belong to the home PLMN. 1. An AM Policy Association is established for a UE as described in clause 4.16.1. 2a. The AF searches the PCF for the UE using Nbsf_Management_Subscribe with SUPI or GPSI as input, indicating that it is searching for the PCF that handles the AM Policy Association of the UE. 2b. The BSF provides to the AF the identity of the PCF for the UE for the requested SUPI or GPSI via an Nbsf_Management_Notify operation. If a matching entry already exists in the BSF when step 2a is performed, this shall be immediately reported to the AF. 2c. The AF sends to the PCF for the UE its request for influencing the access and mobility management policy of the UE (identified by SUPI or GPSI) using Npcf_AMPolicyAuthorization (optionally providing a timer on how long this policy shall last, in which case the system behaviour upon expiration of this timer is as specified in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]). As part of the Npcf_AMPolicyAuthorization request, the AF may subscribe (within the Create and Update operations) or unsubscribe (within the Delete operation) to relevant events specified in clause 6.1.3.18 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20], e.g. events related to change of service area coverage. 3. The PCF takes a policy decision and then an AM Policy Association Modification procedure initiated by the PCF for the UE may be performed as described in clause 4.16.2.2. If the AF has subscribed to access and mobility management related events (i.e. request for service area coverage outcome) in step 2, the PCF reports the event (i.e. outcome of the request for service area coverage) to the AF. Figure 4.15.6.9.2-2: Handling an AF request targeting an individual UE using NEF This procedure concerns only non-roaming scenarios, i.e. to cases where the involved entities serving the UE (AF, NEF, PCF, BSF, AMF) belong to the home PLMN, or the AF belongs to a third party with which the home PLMN has an agreement. 1. An AM Policy Association is established for a UE as described in clause 4.16.1. 2a. The AF sends to NEF its request for influencing the access and mobility management policy of the UE (identified by GPSI) using Nnef_AMPolicyAuthorization (optionally providing a timer on how long this policy shall last, in which case the system behaviour upon expiration of this timer is as specified in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]). As part of the Nnef_AMPolicyAuthorization request, the AF may request to subscribe (within the Create and Update operations) or unsubscribe (within the Delete operation) for relevant events specified in clause 6.1.3.18 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20], e.g. events for request for service area coverage outcome. The NEF stores the request and sends a response to the AF. 2b. The NEF searches the PCF for the UE using Nbsf_Management_Subscribe with SUPI as input parameter, indicating that it is searching for the PCF that handles the AM Policy Association of the UE. 2c. The BSF provides to the NEF the identity of the PCF for the UE for the requested SUPI via an Nbsf_Management_Notify operation. If a matching entry already exists in the BSF when step 2b is performed, this shall be immediately reported to the NEF. 2d. The NEF sends to PCF for the UE the request for influencing the access and mobility management policy of the UE (identified by SUPI) using Npcf_AMPolicyAuthorization (having potentially translated GPSI to SUPI via UDM). As part of the Npcf_AMPolicyAuthorization request, the NEF may subscribe or unsubscribe (according to what the AF requested in step 2a) for relevant events specified in clause 6.1.3.18 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20], e.g. events for change of service area coverage. 2e. The NEF informs the AF about events to which the AF has potentially subscribed (i.e. events for change of service area coverage) using Nnef_AMPolicyAuthorization_Notify. 3. The PCF takes a policy decision and then an AM Policy Association Modification procedure initiated by the PCF for the UE may be performed as described in clause 4.16.2.2. If the AF has subscribed to access and mobility management related events i.e. request for service area coverage outcome in step 2, then the PCF reports the event (i.e. outcome of the request for service area coverage) to the AF as described in clause 4.16.2.2. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.15.6.9.2 |
1,889 | 6.38.2.2 Gateways | The 5G system shall be able to support access to the 5G network and its services via at least one gateway (i.e. PIN Element with Gateway Capability or eRG) for authorised UEs and authorised non-3GPP devices in a PIN or a CPN. The 5G system shall be able to support IP traffic offload to data network for a CPN. NOTE 1: The priority of offload can be from default configuration, network or user. Under operator control, an eRG, shall be able to efficiently deliver 5G multicast/broadcast services to authorized UEs and non-3GPP devices in the CPN. NOTE 2: The multicast service(s) that each of the authorized UEs and/or non-3GPP devices is allowed to receive may be different. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.38.2.2 |
1,890 | 6.1.3.3.2 Synchronization failure recovery in Home Network | Upon receiving an authentication failure message with synchronisation failure (AUTS) from the UE, the SEAF sends an Nausf_UEAuthentication_Authenticate Request message with a "synchronisation failure indication" to the AUSF and the AUSF sends an Nudm_UEAuthentication_Get Request message to the UDM/ARPF, together with the following parameters: - RAND sent to the UE in the preceding Authentication Request, and - AUTS received by the SEAF in the response from the UE to that request, as described in subclause 6.1.3.2.0 and 6.1.3.3.1. An SEAF will not react to unsolicited "synchronisation failure indication" messages from the UE. The SEAF does not send new authentication requests to the UE before having received the response to its Nausf_UEAuthentication_Authenticate Request message with a "synchronisation failure indication" from the AUSF (or before it is timed out). When the UDM/ARPF receives an Nudm_UEAuthentication_Get Request message with a "synchronisation failure indication" it acts as described in TS 33.102[ 3G security; Security architecture ] [9], clause 6.3.5 where ARPF is mapped to HE/AuC. The UDM/ARPF sends an Nudm_UEAuthentication_Get Response message with a new authentication vector for either EAP-AKA’ or 5G-AKA depending on the authentication method applicable for the user to the AUSF. The AUSF runs a new authentication procedure with the UE according to clauses 6.1.3.1 or 6.1.3.2 depending on the authentication method applicable for the user. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.1.3.3.2 |
1,891 | 5.45 QoS Monitoring 5.45.1 General | QoS monitoring comprises of measurements of QoS monitoring parameters and reports of the measurement result for a QoS Flow and can be enabled based on 3rd party application requests and/or operator policies configured in the PCF. Event Reporting from PCF is specified in clause 6.1.3.18 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45] and User Plane QoS Flow related QoS monitoring and reporting in clause 5.8.2.18. The AF may request measurements for one or more of the following QoS monitoring parameters, which may trigger QoS monitoring for service data flow(s): - UL packet delay, DL packet delay, round trip packet delay for a service data flow, see clause 5.45.2. - Congestion, see clause 5.45.3. - Data Rate, see clause 5.45.4. - Packet Delay Variation, see clause 5.37.7. - Round trip packet delay considering UL on a service data flow and DL of another service data flow, see clause 5.37.4. The following AF requested QoS requirements may trigger QoS monitoring for service data flow(s): - Round-trip latency requirement, see clause 5.37.6. The PCF may generate the authorized QoS Monitoring policy for a service data flow based on the QoS Monitoring request received from the AF (as described in clause 6.1.3.21 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]) or based on PCF local policy or configuration reasons, such as PCF awareness of dynamic satellite backhaul connection. The PCF includes the authorized QoS Monitoring policy in the PCC rule and provides it to the SMF. The QoS monitoring parameter(s) that can be measured by means of QoS monitoring are listed below. The QoS monitoring policy in PCC rule (described in clause 6.3.1 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]) may include the following: - UL packet delay, DL packet delay, round trip packet delay, see clause 5.45.2. - Congestion, see clause 5.45.3. - Data Rate, see clause 5.45.4. The SMF configures the UPF to perform QoS monitoring for the QoS Flow and to report the monitoring results as described in clause 5.8.2.18 with parameters determined by the SMF based on the authorized QoS Monitoring policy received from the PCF or local configuration or both. The SMF may also configure RAN to measure the QoS monitoring parameters by sending QoS monitoring request based on the authorized QoS Monitoring policy received from the PCF and/or local configuration. The QoS monitoring request to the NG RAN for different parameters is as defined in clause 5.45.2 and 5.45.3. The following clauses describe the QoS monitoring parameters which can be measured and any specific actions or constraints for their measurement. NOTE: The QoS monitoring parameter which can be measured are parameters which describe the QoS experienced in the 5GS by the application, i.e. they are not restricted to the 5G QoS Parameters defined in clause 5.7.2. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.45 |
1,892 | 5.5.2.7 Reporting configuration addition/modification | The UE shall: 1> for each reportConfigId included in the received reportConfigToAddModList: 2> if an entry with the matching reportConfigId exists in the reportConfigList within the VarMeasConfig, for this entry: 3> reconfigure the entry with the value received for this reportConfig; 3> for each measId associated with this reportConfigId included in the measIdList within the VarMeasConfig, if any: 4> remove the measurement reporting entry for this measId from the VarMeasReportList, if included; 4> stop the periodical reporting timer or timer T321 or timer T322, whichever one is running, and reset the associated information (e.g. timeToTrigger) for this measId; 2> else: 3> add a new entry for the received reportConfig to the reportConfigList within the VarMeasConfig. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.5.2.7 |
1,893 | 9.5.10 Modify PDP context request (MS to network direction) | This message is sent by the MS to the network to request modification of an active PDP context. See table 9.5.10/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Message type: modify PDP context request (MS TO network direction) Significance: global Direction: MS to network Table 9.5.10/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : modify PDP context request (MS to network direction) 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.5.10 |
1,894 | 16.9.9.2 Channel Access Priority Classes for Sidelink (SL-CAPC) | The SL-CAPC of SL radio bearers and SL MAC CEs are either fixed or (pre)configurable as follows: - Fixed to the highest priority for all SL-SRBs and SL MAC CEs - (Pre)configurable per DRB for all SL-DRBs When choosing the SL-CAPC for a SL-DRB the network takes into account the PQIs of all QoS flows mapped to that SL DRB. Table 16.9.9-1 below shows which SL-CAPC should be used for which standardized PQI(s), i.e., which SL-CAPC to use for a given QoS flow. For a UE in RRC_IDLE/RRC_INACTIVE or OOC, the UE uses the SL-CAPC configured in SIB/Pre-configuration when the QoS flow can be mapped to a non-default SLRB, or when the default SLRB is used for the QoS flow and the SL-CAPC of the default SLRB is configured. When the default SLRB is used for the QoS flow and the SL-CAPC of the default SLRB is not configured: - if the QoS flow is associated with standardized PQI, the UE derives SL-CAPC for the flow directly from the table below - if the QoS flow is associated with non-standardized PQI, the UE may select the SL-CAPC of the standardized PQI having the closest PDB. The UE then selects the lowest SL-CAPC priority level (highest SL-CAPC value) among the QoS flows to determine the SL-CAPC for the default SLRB. Table 16.9.9-1: Mapping between Channel Access Priority Classes for SL-U and PQI When performing Type 1 LBT for the transmission of a sidelink TB, the SL UE shall select the SL-CAPC as follows: - If only SL MAC CE(s) are included in the SL TB, the highest priority SL-CAPC is used; or - If SCCH SDU(s) are included in the SL TB, the highest priority SL-CAPC is used; or - The lowest priority SL-CAPC of the SL logical channel(s) with MAC SDU(s) multiplexed in the TB is used otherwise. The highest priority SL-CAPC is used for SBCCH SDU transmissions and PSFCH transmissions. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.9.9.2 |
1,895 | 5.4.6 Power Headroom Reporting | The Power Headroom reporting procedure is used to provide the serving eNB with information about the difference between the nominal UE maximum transmit power and the estimated power for UL-SCH transmission or SRS transmission per activated Serving Cell and also with information about the difference between the nominal UE maximum power and the estimated power for UL-SCH and PUCCH/SPUCCH transmission on SpCell and PUCCH SCell. The reporting period, delay and mapping of Power Headroom are defined in TS 36.133[ Evolved Universal Terrestrial Radio Access (E-UTRA); Requirements for support of radio resource management ] [9] and TS 38.133[ NR; Requirements for support of radio resource management ] [19]. RRC controls Power Headroom reporting by configuring the two timers periodicPHR-Timer and prohibitPHR-Timer, and by signalling dl-PathlossChange which sets the change in measured downlink pathloss and the required power backoff due to power management (as allowed by P-MPRc, see TS 36.101[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception ] [10] and TS 38.101[ None ] -3 [21]) to trigger a PHR, as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8]. A Power Headroom Report (PHR) shall be triggered if any of the following events occur: - prohibitPHR-Timer expires or has expired and the path loss has changed more than dl-PathlossChange dB for at least one activated Serving Cell of any MAC entity which is used as a pathloss reference since the last transmission of a PHR in this MAC entity when the MAC entity has UL resources for new transmission; - periodicPHR-Timer expires; - upon configuration or reconfiguration of the power headroom reporting functionality by upper layers, as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8], which is not used to disable the function; - activation of an SCell of any MAC entity with configured uplink; - addition of the PSCell (i.e. PSCell is newly added or PSCell is changed); - prohibitPHR-Timer expires or has expired, when the MAC entity has UL resources for new transmission, and the following is true in this TTI for any of the activated Serving Cells of any MAC entity with configured uplink: - there are UL resources allocated for transmission or there is a PUCCH/SPUCCH transmission on this cell, and the required power backoff due to power management (as allowed by P-MPRc, see TS 36.101[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception ] [10] and TS 38.101[ None ] -3 [21]) for this cell has changed more than dl-PathlossChange dB since the last transmission of a PHR when the MAC entity had UL resources allocated for transmission or PUCCH/SPUCCH transmission on this cell. NOTE 1: The MAC entity should avoid triggering a PHR when the required power backoff due to power management decreases only temporarily (e.g. for up to a few tens of milliseconds) and it should avoid reflecting such temporary decrease in the values of PCMAX,c/PH when a PHR is triggered by other triggering conditions. NOTE 2: If UL HARQ operation is autonomous for the HARQ entity and if the PHR is already included in a MAC PDU for transmission by this HARQ entity, but not yet transmitted by lower layers, it is up to UE implementation how to handle the PHR content. If the MAC entity has UL resources allocated for new transmission for this TTI the MAC entity shall: - if it is the first UL resource allocated for a new transmission since the last MAC reset, start periodicPHR-Timer; - if the Power Headroom reporting procedure determines that at least one PHR has been triggered and not cancelled, and; - if the allocated UL resources can accommodate the MAC control element for PHR which the MAC entity is configured to transmit, plus its subheader, as a result of logical channel prioritization: - if extendedPHR is configured: - for each activated Serving Cell with configured uplink: - obtain the value of the Type 1 or Type 3 power headroom; - if the MAC entity has UL resources allocated for transmission on this Serving Cell for this TTI: - obtain the value for the corresponding PCMAX,c field from the physical layer; - if simultaneousPUCCH-PUSCH is configured or a serving cell operating according to Frame Structure Type 3 with uplink is configured and activated: - obtain the value of the Type 2 power headroom for the PCell; - obtain the value for the corresponding PCMAX,c field from the physical layer (see clause 5.1.1.2 of TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [2]); - instruct the Multiplexing and Assembly procedure to generate and transmit an Extended PHR MAC control element for extendedPHR as defined in clause 6.1.3.6a based on the values reported by the physical layer; - else if extendedPHR2 is configured: - for each activated Serving Cell with configured uplink: - obtain the value of the Type 1 or Type 3 power headroom; - if the MAC entity has UL resources allocated for transmission on this Serving Cell for this TTI: - obtain the value for the corresponding PCMAX,c field from the physical layer; - if a PUCCH SCell is configured and activated: - obtain the value of the Type 2 power headroom for the PCell and PUCCH SCell; - obtain the values for the corresponding PCMAX,c fields from the physical layer (see clause 5.1.1.2 ofTS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [2]); - else: - if simultaneousPUCCH-PUSCH is configured for the PCell or a serving cell operating according to Frame Structure Type 3 with uplink is configured and activated: - obtain the value of the Type 2 power headroom for the PCell; - obtain the value for the corresponding PCMAX,c field from the physical layer (see clause 5.1.1.2 of TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [2]); - instruct the Multiplexing and Assembly procedure to generate and transmit an Extended PHR MAC control element for extendedPHR2 according to configured ServCellIndex and the PUCCH(s) for the MAC entity as defined in clause 6.1.3.6a based on the values reported by the physical layer; - else if dualConnectivityPHR is configured: - for each activated Serving Cell with configured uplink associated with any MAC entity: - obtain the value of the Type 1 or Type 3 power headroom; - if this MAC entity has UL resources allocated for transmission on this Serving Cell for this TTI or if the other MAC entity has UL resources allocated for transmission on this Serving Cell for this TTI and phr-ModeOtherCG is set to real by upper layers: - obtain the value for the corresponding PCMAX,c field from the physical layer; - if simultaneousPUCCH-PUSCH is configured or a serving cell operating according to Frame Structure Type 3 with uplink is configured and activated: - obtain the value of the Type 2 power headroom for the SpCell; - obtain the value for the corresponding PCMAX,c field for the SpCell from the physical layer (see clause 5.1.1.2 of TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [2]); - if the other MAC entity is E-UTRA MAC entity: - obtain the value of the Type 2 power headroom for the SpCell of the other MAC entity. - if phr-ModeOtherCG is set to real by upper layers: - obtain the value for the corresponding PCMAX,c field for the SpCell of the other MAC entity from the physical layer (see clause 5.1.1.2 of TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [2]); - instruct the Multiplexing and Assembly procedure to generate and transmit a Dual Connectivity PHR MAC control element as defined in clause 6.1.3.6b based on the values reported by the physical layer; - else: - obtain the value of the Type 1 power headroom from the physical layer; - instruct the Multiplexing and Assembly procedure to generate and transmit a PHR MAC control element as defined in clause 6.1.3.6 based on the value reported by the physical layer; - start or restart periodicPHR-Timer; - start or restart prohibitPHR-Timer; - cancel all triggered PHR(s). | 3GPP TS 36.321 | Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification | RAN2 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 5.4.6 |
1,896 | 5.3.18 Restricted local operator services | Restricted local operator services (RLOS) is an optional feature that enables operators to offer access to restricted local operator services to the unauthenticated UEs in limited service state (see 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [10]). Authenticated UEs in limited service state may also be able to access restricted local operator services. The UE requests access to RLOS during the attach procedure by setting the attach type to "EPS RLOS attach" in the ATTACH REQUEST message. Subject to regulation and local operator policy, if the MME is configured to support access to RLOS, the MME accepts the UE's attach request regardless of the authentication result or skips the authentication procedure. When the UE requests the lower layer to establish an RRC connection for access to RLOS, the UE indicates in the RRC signalling that the RRC connection is for access to RLOS to the lower layers. The UE supporting access to RLOS shall perform PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [6]. Broadcast system information may provide information about support of access to RLOS (see 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [22]). At reception of new broadcast system information, the lower layers deliver it to the EMM layer in the UE. The information provided by lower layers is per PLMN and used by the UE to determine whether the PLMN is configured to support access to RLOS. The UE shall not attempt to request access to RLOS if the PLMN does not support access to RLOS. NOTE: Only authorized applications on the UE are allowed to trigger the initiation of RLOS connection (see 3GPP TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [19]). For UE attached for access to RLOS, only UE originated access to RLOS requests are supported. Mobile terminated access to RLOS request and network triggered service request are not allowed. The UE is not allowed to initiate UE requested PDN connectivity for any additional PDN connection. In addition, intersystem change to other RAT including GERAN and UTRAN and handover between 3GPP and non-3GPP accesses are not supported. Access to RLOS is applicable to the UEs in WB-S1 mode only. The UEs in NB-S1 mode shall not request access to RLOS. Location service does not apply to access to RLOS. If a UE attached for access to RLOS needs to initiate an emergency call, the UE shall first perform a local detach prior to initiating an attach procedure for emergency bearer services. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.3.18 |
1,897 | 9.11.3.108 On-demand NSSAI | The purpose of the On-demand NSSAI information element is to provide a list of one or more on-demand S-NSSAIs and the associated slice deregistration inactivity timer value per the on-demand S-NSSAI to the UE. The On-demand NSSAI information element is coded as shown in figure 9.11.3.108.1, figure 9.11.3.108.2, and table 9.11.3.108.1. The On-demand NSSAI is a type 4 information element with a minimum length of 4 octets and a maximum length of 194 octets. Figure 9.11.3.108.1: On-demand NSSAI information element Figure 9.11.3.108.2: Information of on-demand S-NSSAI Table 9.11.3.108.1: On-demand NSSAI information element | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.11.3.108 |
1,898 | 8.3.2.1I Single-layer Spatial Multiplexing (With Enhanced DMRS table configured) | For single-layer transmission on antenna port 7, 8, 11 or 13 upon detection of a PDCCH with DCI format 2C, the requirement is specified in Table 8.3.2.1I-2, with the addition of the parameters in Table 8.3.2.1I-1 and the downlink physical channel setup according to Annex C.3.2. The purpose of the test is to verify rank-1 performance on antenna port 11 with a simultaneous transmission on the antenna port 7, 8 or 13 with DMRS enhancement table and 4 orthogonal DMRS ports (dmrs-Enhancements-r13 UE-EUTRA-Capability [7]). Table 8.3.2.1I-1: Test Parameters for Testing CDM-multiplexed DM RS (single layer) with interfering simultaneous transmission (FRC) with multiple CSI-RS configurations with Enhanced DMRS table Table 8.3.2.1I-2: Minimum performance for CDM-multiplexed DM RS with interfering simultaneous transmission (FRC) with multiple CSI-RS configurations with Enhanced DMRS table | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.3.2.1I |
1,899 | Annex G (informative): Business to Business (B2B) charging architecture and principles G.2.1 General | In the B2B scenario, the charging architecture may involve two modes of interaction: - Business CHF interaction: the NF (CTF) collects and reports the charging information per business, alternatively it collects and reports the charging information per consumer but for business charging purposes, to the business CHF (i.e. B-CHF). - Business CHF via consumer CHF interaction: the NF (CTF) collects and reports the charging information per consumer to a consumer CHF (i.e. C-CHF), and the C-CHF reports the charging information per business to the business CHF (i.e. B-CHF). | 3GPP TS 32.240 | Telecommunication management; Charging management; Charging architecture and principles | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | Annex |
1,900 | – SL-PSSCH-TxConfigList | The IE SL-PSSCH-TxConfigList indicates PSSCH transmission parameters. When lower layers select parameters from the range indicated in IE SL-PSSCH-TxConfigList, the UE considers both configurations in IE SL-PSSCH-TxConfigList and the CBR-dependent configurations represented in IE SL-CBR-PriorityTxConfigList. Only one IE SL-PSSCH-TxConfig is provided per SL-TypeTxSync. SL-PSSCH-TxConfigList information element -- ASN1START -- TAG-SL-PSSCH-TXCONFIGLIST-START SL-PSSCH-TxConfigList-r16 ::= SEQUENCE (SIZE (1..maxPSSCH-TxConfig-r16)) OF SL-PSSCH-TxConfig-r16 SL-PSSCH-TxConfig-r16 ::= SEQUENCE { sl-TypeTxSync-r16 SL-TypeTxSync-r16 OPTIONAL, -- Need R sl-ThresUE-Speed-r16 ENUMERATED {kmph60, kmph80, kmph100, kmph120, kmph140, kmph160, kmph180, kmph200}, sl-ParametersAboveThres-r16 SL-PSSCH-TxParameters-r16, sl-ParametersBelowThres-r16 SL-PSSCH-TxParameters-r16, ..., [[ sl-ParametersAboveThres-v1650 SL-MinMaxMCS-List-r16 OPTIONAL, -- Need R sl-ParametersBelowThres-v1650 SL-MinMaxMCS-List-r16 OPTIONAL -- Need R ]] } SL-PSSCH-TxParameters-r16 ::= SEQUENCE { sl-MinMCS-PSSCH-r16 INTEGER (0..27), sl-MaxMCS-PSSCH-r16 INTEGER (0..31), sl-MinSubChannelNumPSSCH-r16 INTEGER (1..27), sl-MaxSubchannelNumPSSCH-r16 INTEGER (1..27), sl-MaxTxTransNumPSSCH-r16 INTEGER (1..32), sl-MaxTxPower-r16 SL-TxPower-r16 OPTIONAL -- Cond CBR } -- TAG-SL-PSSCH-TXCONFIGLIST-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
Subsets and Splits