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
⌀ |
|---|---|---|---|---|---|---|---|
3,401 | 5.2.3.8.3 Nudm_ServiceSpecificAuthorisation_UpdateNotify service operation | Service operation name: Nudm_ServiceSpecificAuthorisation_UpdateNotify Description: This service operation is used by the UDM to notify a Service Specific Authorisation Update to NF consumer. Inputs, Required: GPSI or External Group Id, SUPI or Internal Group Id, Status, Cause (e.g. subscription withdrawal, DNN associated to the authorization is removed from UE subscription). Inputs, Optional: DNN, S-NSSAI, Service Type (e.g. AF guidance for URSP), MTC Provider Information, AF ID. Outputs, Required: None. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.3.8.3 |
3,402 | 10.19.3 CHO with candidate SCG(s) | A CHO with candidate SCG(s) is defined as a PCell change with PSCell addition/change that is executed by the UE when the execution conditions for both candidate PCell and the associated candidate PSCell are met. The UE starts evaluating the execution conditions for candidate PCell(s) and candidate PSCell(s) simultaneously upon receiving the CHO with candidate SCG(s) configuration, and stops evaluating the execution conditions once a PCell change or a PSCell change is triggered. The UE does not execute CHO with candidate SCG(s) until the execution conditions for both the candidate PCell and the associated candidate PSCell are met. | 3GPP TS 37.340 | Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Overall Description; Stage-2 | RAN2 | 3GPP Series : 37 , Multiple radio access technology aspects | 10.19.3 |
3,403 | 8.4.2.2.6 Enhanced Downlink Control Channel Performance Requirement Type A - 2 Tx Antenna Port with Non-Colliding CRS Dominant Interferer | The purpose of this test is to verify the Enhanced Downlink Control Channel Performance Requirement Type A for PDCCH/PCFICH with 2 transmit antennas for the case of dominant interferer with the non-colliding CRS pattern and applying interference model defined in clause B.7.1. For the parameters specified in Table 8.4.2-1 and Table 8.4.2.2.6-1, the average probability of a missed downlink scheduling grant (Pm-dsg) shall be below the specified value in Table 8.4.2.2.6-2. In Table 8.4.2.2.6-1, 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 and includes Cell 2 and Cell 3. Table 8.4.2.2.6-1: Test Parameters for PDCCH/PCFICH Table 8.4.2.2.6-2: Minimum Performance for PDCCH/PCFICH for Enhanced Downlink Control Channel Performance Requirement Type A | 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.4.2.2.6 |
3,404 | 4.15.9.3.2 Time synchronization service activation | Figure 4.15.9.3.2-1: Time synchronization service activation 1. The AF creates a time synchronization service configuration for a PTP instance by invoking Nnef_TimeSynchronization_ConfigCreate service operation. The request includes the parameters as described in Table 4.15.9.3-1. The request contains a Subscription Correlation ID and user-plane node ID as a reference to the target of the UEs and AF-sessions. The create request creates also a subscription for the changes in the time synchronization service configuration. The AF may subscribe to receiving network time synchronization status report(s) as specified in clause 4.15.9.5.1. 2. The NEF authorizes the request. After successful authorization, the NEF invokes the Ntsctsf_TimeSynchronization_ConfigCreate service operation with the corresponding TSCTSF, with the parameters as received from the AF. If the request includes a spatial validity condition and if the AF uses a geographical area as a spatial validity condition, the NEF transforms this information into 3GPP identifiers (e.g. TAI(s)) based on pre-configuration. The AF that is part of operator's trust domain may invoke the services directly with TSCTSF. If the request includes a spatial validity condition and if the AF is within the operator's domain, the spatial validity condition shall comprise of a list of TA(s). NOTE 1: It is assumed that AFs within the operator's domain is aware of TAs that can be used to formulate a spatial validity condition for Time Synchronization Coverage Area (see clause 5.27.1.10 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]). 3. TSCTSF checks whether the AF requested parameters comply with the stored Time Synchronization Subscription data as defined in clause 5.27.1.11 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], for that, the TSCTSF retrieves the Time Synchronization Subscription data from the UDM as defined in clause 4.15.9.2). The TSCTSF determines the Time Synchronization Coverage Area and responds with the Ntsctsf_TimeSynchronization_ConfigCreate response as specified in clause 5.27.1.11 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The Ntsctsf_TimeSynchronization_ConfigCreate response includes a PTP instance reference. 4. The NEF responds with the Nnef_TimeSynchronization_ConfigCreate response, including a reference to the time synchronization service configuration (PTP instance reference). 5-6. The TSCTSF uses the Subscription Correlation ID and user-plane node ID in Ntsctsf_TimeSynchronization_ConfigCreate to determine the target UEs and corresponding AF-sessions. The TSCTSF uses the parameters (e.g. requested PTP instance type, transport protocol and PTP profile) in the Ntsctsf_TimeSynchronization_ConfigCreate request to determine suitable DS-TT(s) and corresponding AF-sessions among all AF-sessions that are associated with the Subscription Correlation ID and user-plane node ID in the request. The TSCTSF maintains association between list of suitable AF-sessions, corresponding time synchronization configuration, the PTP instance reference in 5GS, PTP instance references in each involved DS-TT and NW-TT and Subscription Correlation ID and user-plane node ID as given in step 1. NOTE 2: The AF-sessions that are not associated with a time synchronization configuration, are available to be selected as suitable AF-sessions in another Ntsctsf_TimeSynchronization_ConfigCreate request. The TSCTSF uses the procedures described in clause K.2.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] to configure and initialize the PTP instance in the DS-TT(s) and NW-TT. The TSCTSF constructs a PMIC to each DS-TT/UE to activate the time synchronization service in DS-TT in respect to the service parameters in the request in step 2. The TSCTSF constructs PMIC(s) and UMIC to NW-TT to activate the time synchronization service in NW-TT in respect to the service parameters in the request in step 2. Upon reception of responses from each DS-TT and NW-TT, the TSCTSF determines the state of the time synchronization configuration. The TSCTSF constructs a PMIC to each DS-TT/UE to subscribe for the port management information changes in the DS-TT. The TSCTSF constructs PMIC(s) and UMIC to NW-TT to subscribe for the port management and user-plane management information changes in NW-TT. The TSCTSF retrieves the PMIC(s) and UMIC via means of Npcf_PolicyAuthorization service operations. The create request creates also a subscription for notifications for the changes in the time synchronization service configuration. If the AF provided clock quality acceptance criteria in step 1, the TSCTSF subscribes for notifications for changes in the NG-RAN and UPF/NW-TT timing synchronization status, as described in clause 4.15.9.5.1: - To determine the impacted UEs due to a timing synchronization status update reported by the NG-RAN, the TSCTSF follows the operation described in clause 5.27.1.12 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. - To determine the impacted UEs due to a timing synchronization status update reported by the UPF/NW-TT, the TSCTSF verifies if the UPF/NW-TT is configured to send (g)PTP messages to the UEs/DS-TTs. If the Ntsctsf_TimeSynchronization_ConfigCreate request contains a temporal validity condition with a start-time and/or the stop-time that is in the future, the TSCTSF maintains the start-time and stop-time for the time synchronization service for the corresponding time synchronization configuration. If the start-time is in the past, the TSCTSF treats the request as if the time synchronization service was activated immediately. When the start-time is reached, the TSCTSF proceeds as described in this step above. When the stop-time is reached for active time synchronization service configuration, the TSCTSF proceeds as Ntsctsf_TimeSynchronization_ConfigDelete was received as described in clause 4.15.9.3.4. If the Ntsctsf_TimeSynchronization_ConfigCreate request contains a spatial validity condition, then the TSCTSF performs the following operations: - TSCTSF determines whether the TSCTSF has subscribed for the UE presence in Area of Interest composed by the TA(s) in the Time Synchronization Coverage Area. If not, the TSCTSF may either discover the AMF(s) serving the TA(s) comprising the Time Synchronization Coverage Area or discover the serving AMF(s) for each UE identified by a GPSI/SUPI as described in clause 5.27.1.10 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. Then the TSCTSF subscribes to the AMF(s) to receive notifications about the UE presence in Area of Interest using Namf_EventExposure operation with the corresponding event filters as described in clause 5.2.2.3 and in clause 5.3.4.4. of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The subscribed area of interest may be the same as the Time Synchronization Coverage Area or may be a subset of the Time Synchronization Coverage Area (e.g. a list of TAs) based on the latest known UE location. - In order to ensure that a TAI list specifying the AoI for the AMF is aligned with UE's Registration Area (RA), the following steps shall be performed: - When invoking the subscription with the AMF(s), the TSCTSF may provide an indication, a new Parameter Type = "Adjust AoI based on RA", that the AMF may adjust the received AoI depending on UE's RA. - After receiving the Namf_EventExposure_Subscribe request from the TSCTSF with the Parameter Type = "Adjust AoI based on RA" and specified AoI, the AMF compares TAs from the AoI with the UE's Registration Area (RA). If the AoI includes one or more TA(s) that are part of UE's current RA, the AMF reports the UE is inside the Area Of Interest, otherwise the AMF reports the UE is outside the Area Of Interest, as described in Annex D. - The AMF notifies the TSCTSF about the UE's presence in the AoI using the Namf_EventExposure_Notify service operation. - Based on the notification from the AMF and the Time Synchronization Coverage Area determined in step 3, the TSCTSF determines whether to activate time synchronization service for this UE: - If the UE location is within the Time Synchronization Coverage Area, the TSCTSF determines to activate time synchronization service for the UE/DS-TT creating the PTP port in DS-TT and adding it to the PTP instance. The TSCTSF uses the procedures described in clause K.2.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] to configure and initialize the PTP instance in the DS-TT(s) and NW-TT. - If the UE location is outside the Time Synchronization Coverage Area, the TSCTSF determines not to activate time synchronization service and not to create a PTP port in a DS-TT. The TSCTSF uses the procedure in clause 4.15.9.4 to activate or modify the 5G access stratum time distribution for the UEs that are part of the impacted PTP instance. 7. The TSCTSF notifies the NEF (or AF) with the Ntsctsf_TimeSynchronization_ConfigUpdateNotify service operation, containing the PTP instance reference and the current state of the time synchronization service configuration. If TSCTSF received spatial validity condition as part of the Ntsctsf_TimeSynchronization_ConfigCreate request, the TSCTSF notifies the NEF (or AF) with the Ntsctsf_TimeSynchronization_ConfigUpdateNotify service operation, whenever the UE moves in or out of the Area of Interest. The notification contains the PTP instance reference and the current state of the time synchronization service configuration. 8. The NEF notifies the AF with the Nnef_TimeSynchronization_ConfigUpdateNotify service operation, containing the PTP instance reference and the current state of the time synchronization service configuration. 9. Upon a change in the PTP instance in the DS-TT or NW-TT, the DS-TT or NW-TT report the change via PMIC or UMIC to the TSCTSF as described in clause K.2.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. Upon PDU Session release indication from a PCF, the TSCTSF removes the corresponding AF-session from the list of AF-sessions associated with the time synchronization configuration. The TSCTSF uses the procedure in clause 4.15.9.4 to remove the 5G access stratum time distribution parameters for the UE that is removed from the impacted PTP instance. Upon PDU Session Establishment as defined clause 4.3.2.2.1, steps 10-13 in Figure 4.15.9.2-1 are repeated for the new PDU Session and the TSCTSF may notify the NEF (or AF) for the Time Synchronization capability event, optionally with the updated time synchronization capabilities, as described in step 12 in Figure 4.15.9.2-1. NOTE 3: Upon receiving the notification, the NEF (or AF) can use the Ntsctsf_TimeSynchronization_ConfigUpdate service operation to add the DS-TT/UE to the existing PTP instance and corresponding time synchronization service configuration. If TSCTSF received spatial validity condition as part of the Ntsctsf_TimeSynchronization_ConfigCreate request, upon a change in the UE presence in Area of Interest, the TSCTSF determines if the spatial validity condition shall trigger an activation or deactivation of the time synchronization service: - If the UE has moved outside the Time Synchronization Coverage Area, then the TSCTSF temporarily removes the UE/DS-TT port from the PTP instance: - If the DS-TT is configured to send Sync, Follow_Up and Announce messages for the related PTP instance, then TSCTSF deactivates the Grandmaster functionality in the DS-TT using PMIC (see also clause K.2.2.4 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]). - If NW-TT is configured to send Sync, Follow_Up and Announce messages on behalf of the DS-TT, then TSCTSF deactivates the Grandmaster functionality on behalf of the DS-TT in NW-TT using UMIC (see also clause K.2.2.4 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]). - If the UE has moved inside the Time Synchronization Coverage Area, then the TSCTSF adds the DS-TT PTP port to the PTP instance and also (re-)activates the Grandmaster functionality (described in clause K.2.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]). Upon a NG-RAN timing synchronization status update, the NG-RAN report the change via AMF or provisioned via OAM to the TSCTSF as described in clause 4.15.9.5.1. Upon a UPF/NW-TT timing synchronization status update, the UPF/NW-TT timing synchronization status update is reported via UMIC or provisioned via OAM to the TSCTSF as described in clause 4.15.9.5.1. If TSCTSF received a NG-RAN or UPF/NW-TT timing synchronization status update and the time synchronization service has a configured clock quality acceptance criteria for the UE, the TSCTSF determines whether the clock quality acceptance criteria can still be met: - If the clock quality acceptance criteria can still be met, then TSCTSF may update the clockQuality information sent in Announce messages for the PTP instance using PMIC/UMIC reporting. The handling of Announce messages follows existing procedures as described in TS 23.501[ System architecture for the 5G System (5GS) ] [2]. - If the clock quality acceptance criteria cannot be met or can be met again, then TSCTSF informs the AF about the acceptance criteria result (e.g., acceptable/not acceptable). 10. The TSCTSF updates the state of the time synchronization configuration and may notify the NEF (or AF) with the Ntsctsf_TimeSynchronization_ConfigUpdateNotify service operation, containing the PTP instance reference and the updated state of the time synchronization service configuration, including whether there was a change in the UE's presence in the Time Synchronization Coverage Area (in cases when the AF has requested the service for a specific spatial validity condition), or the clock quality acceptance criteria result (in cases when the AF has requested the service with a clock quality acceptance criteria condition). 11. The NEF notifies the AF with the Nnef_TimeSynchronization_ConfigUpdateNotify service operation, containing the reference to the time synchronization service configuration (PTP instance reference) and the updated state of the time synchronization service configuration. If the AF receives a clock quality acceptance criteria result, the AF may update the configuration of the PTP instance by updating the PTP instance sending a Nnef/Ntsctsf_TimeSynchronization_ConfigUpdate or Nnef/Ntsctsf_TimeSynchronization_ConfigDelete request, as described in clauses 4.15.9.3.3 and 4.15.9.3.4. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.15.9.3.2 |
3,405 | – SecurityModeComplete | The SecurityModeComplete message is used to confirm the successful completion of a security mode command. Signalling radio bearer: SRB1 RLC-SAP: AM Logical channel: DCCH Direction: UE to Network SecurityModeComplete message -- ASN1START -- TAG-SECURITYMODECOMPLETE-START SecurityModeComplete ::= SEQUENCE { rrc-TransactionIdentifier RRC-TransactionIdentifier, criticalExtensions CHOICE { securityModeComplete SecurityModeComplete-IEs, criticalExtensionsFuture SEQUENCE {} } } SecurityModeComplete-IEs ::= SEQUENCE { lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension SEQUENCE{} OPTIONAL } -- TAG-SECURITYMODECOMPLETE-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
3,406 | – DedicatedSIBRequest | The DedicatedSIBRequest message is used to request SIB(s) required by the UE in RRC_CONNECTED as specified in clause 5.2.2.3.5. Signalling radio bearer: SRB1 RLC-SAP: AM Logical channel: DCCH Direction: UE to Network DedicatedSIBRequest message -- ASN1START -- TAG-DEDICATEDSIBREQUEST-START DedicatedSIBRequest-r16 ::= SEQUENCE { criticalExtensions CHOICE { dedicatedSIBRequest-r16 DedicatedSIBRequest-r16-IEs, criticalExtensionsFuture SEQUENCE {} } } DedicatedSIBRequest-r16-IEs ::= SEQUENCE { onDemandSIB-RequestList-r16 SEQUENCE { requestedSIB-List-r16 SEQUENCE (SIZE (1..maxOnDemandSIB-r16)) OF SIB-ReqInfo-r16 OPTIONAL, requestedPosSIB-List-r16 SEQUENCE (SIZE (1..maxOnDemandPosSIB-r16)) OF PosSIB-ReqInfo-r16 OPTIONAL } OPTIONAL, lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL } SIB-ReqInfo-r16 ::= ENUMERATED { sib12, sib13, sib14, sib20-v1700, sib21-v1700, spare3, spare2, spare1 } PosSIB-ReqInfo-r16 ::= SEQUENCE { gnss-id-r16 GNSS-ID-r16 OPTIONAL, sbas-id-r16 SBAS-ID-r16 OPTIONAL, posSibType-r16 ENUMERATED { posSibType1-1, posSibType1-2, posSibType1-3, posSibType1-4, posSibType1-5, posSibType1-6, posSibType1-7, posSibType1-8, posSibType2-1, posSibType2-2, posSibType2-3, posSibType2-4, posSibType2-5, posSibType2-6, posSibType2-7, posSibType2-8, posSibType2-9, posSibType2-10, posSibType2-11, posSibType2-12, posSibType2-13, posSibType2-14, posSibType2-15, posSibType2-16, posSibType2-17, posSibType2-18, posSibType2-19, posSibType2-20, posSibType2-21, posSibType2-22, posSibType2-23, posSibType3-1, posSibType4-1, posSibType5-1, posSibType6-1, posSibType6-2, posSibType6-3,..., posSibType1-9-v1710, posSibType1-10-v1710, posSibType2-24-v1710, posSibType2-25-v1710, posSibType6-4-v1710, posSibType6-5-v1710, posSibType6-6-v1710, posSibType2-17a-v1770, posSibType2-18a-v1770, posSibType2-20a-v1770, posSibType1-11-v1800, posSibType1-12-v1800, posSibType2-26-v1800, posSibType2-27-v1800 } } -- TAG-DEDICATEDSIBREQUEST-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
3,407 | 5.2.3 Charging data transfer in converged charging | In converged charging, charging events mirroring the resource usage request of the user are transferred from the CTF or CEF to the CHF via the Nchf service-based interface. - The CTF determines whether to use Event based charging (IEC and PEC) or Session based charging (SCUR and ECUR). - The CEF determines the type of Event based charging (IEC and PEC) to use. The charging data transfer for the converged online and offline charging is the converged operation of the online and offline charging specified in the clause 5.2.1 and 5.2.2. Details on the protocol application for the Nchf interface, including the message types and the domain / subsystem /service content of the messages, can be found in TS 32.290[ Telecommunication management; Charging management; 5G system; Services, operations and procedures of charging using Service Based Interface (SBI) ] [57] and TS 32.291[ Telecommunication management; Charging management; 5G system, charging service; Stage 3 ] [58]. | 3GPP TS 32.240 | Telecommunication management; Charging management; Charging architecture and principles | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 5.2.3 |
3,408 | 13.3.1.1 IPv4 Address allocation and IPv4 parameter configuration via DHCPv4 | The UE may obtain the IPv4 address and/or its configuration parameters at or after the initial access signalling (e.g. default bearer establishment) to the packet domain. The request for IPv4 address and/or configuration parameters from the UE may trigger the P-GW acting as DHCPv4 client to request the IPv4 address and/or configuration parameters from an external DHCPv4 server and deliver them to the UE. See subclause 11.2.1.2.2 for details. The DHCPv4 functions in the P-GW, the UE and the external DHCPv4 server shall be compliant to RFC 2131 [26], RFC 1542 [27] and RFC 4039 [79]. The following bullet items describe the successful IPv4 address allocation and parameter configuration signalling flow between the P-GW and the external DHCPv4 server as depicted Figure 16h. For a detailed description of the DHCPv4 messages, refer to RFC 2131 [26], RFC 1542 [27] and RFC 4039 [79]. Figure 16h is an example signalling flow for IPv4 address allocation and parameter configuration at the default bearer setup using DHCPv4 as specified in RFC 2131 [26]. If the optimized signalling (Rapid Commit Option) is used as per RFC 4039 [79], the messages 2-3 can be eliminated. 1) The DHCPv4 client function in the P-GW sends a DHCPDISCOVER as an IP limited broadcast message, i.e. the destination address 255.255.255.255, towards the external PDN. If the P-GW has the DHCPv4 server IP addresses configured for the APN, the DHCPDISCOVER shall be send as unicast (or even multicast) to the external DHCPv4 servers. 2) Upon receiving the DHCPDISCOVER request message, the external DHCPv4 servers reply by sending a DHCPOFFER message including an offered IP address. Several DHCPOFFER messages may be received by the P-GW if multiple DHCPv4 servers respond to the DHCPDISCOVER. 3) The DHCPv4 client function in the P-GW processes the messages and sends a DHCPREQUEST towards the selected external DHCPv4 server. 4) Upon receiving the DHCPREQUEST message, the selected external DHCPv4 server acknowledges the address allocation by sending a DHCPACK containing the lease period (T1), the time-out time (T2) and the configuration information requested in DHCPREQUEST. The P-GW stores the allocated IPv4 address, the lease timers and the configuration parameters. The IPv4 address and the configuration parameters shall be delivered to the UE through P-GW to UE messages. Figure 16h: The signalling flow for IPv4 address allocation and parameter configuration using DHCPv4 Figure 16i is an example signalling flow for IPv4 address lease renew by using DHCPv4 protocol as specified in RFC 2131 [26]. 1) The DHCPv4 client function in the P-GW sends a unicast DHCPREQUEST towards the external DHCPv4 server to extend the lease period of the allocated IPv4 address. 2) The external DHCPv4 server replies with a DHCPACK message confirming the renewed lease and the T1 and T2 timers are restarted. Figure 16i: The signalling flow for IPv4 address lease renew using DHCPv4 | 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 | 13.3.1.1 |
3,409 | D.2.2 Non-roaming interoperation scenario | In the non-roaming scenario the PLMN operates Gn/Gp 2G and/or 3G SGSNs as well as MME and S-GW for E-UTRAN access. Intra PLMN roaming and inter access mobility between Gn/Gp 2G and/or 3G SGSNs and an MME/S-GW are enabled by: - Gn functionality as specified between two Gn/Gp SGSNs, which is provided by the MME, and - Gn functionality as specified between Gn/Gp SGSN and Gn/Gp GGSN that is provided by the P-GW. All this Gn functionality is based on GTP version 1 only. The architecture for interoperation with Gn/Gp SGSNs in the non-roaming case is illustrated in Figure D.2.2-1. Figure D.2.2-1: Non-roaming Architecture for interoperation with Gn/Gp SGSNs NOTE: If the Rel-7 SGSN applies Direct Tunnel there is a user plane connection between P-GW and UTRAN. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | D.2.2 |
3,410 | 4.16.14 Management of access and mobility related policy information depending on the application in use 4.16.14.1 General | The procedure for management of access and mobility related policy information depending on the application in use enables modification of the access and mobility related policy information on detection of the start and stop of an application. The content of this clause applies to non-roaming and LBO roaming scenario (for any inbound roaming UEs), i.e. to cases where the involved entities (e.g. PCF, SMF and UPF) belong to the serving PLMN. The PCF shall not apply a change of access and mobility related policy information for application traffic detected in PDU Sessions established in Home Routed mode. If PCF for the UE and PCF for the PDU Session are the same PCF, then steps 3, 5, 6, 9 and 12 in Figure 4.16.14.2-1 are not performed. If the PCF for the UE and the PCF for the PDU Session are different PCFs, then the PCF for the UE is informed when a SM Policy Association is established or released by either: - Subscription to the BSF: = see steps 2, 3, 4, 5a, 11 and 12a in Figure 4.16.14.2.1-1. The BSF notifies when a PCF is registered or deregistered for the PDU Session to a DNN, S-NSSAI. - see steps 2, 3, 5 and 8 in Figure 4.16.14.2.2-1. The BSF reports the registration of a PCF for the PDU Session when the first SM Policy Association is established and the deregistration of the PCF for the PDU Session when the last SM Policy Association is terminated for a (DNN, S-NSSAI). - Request to the PCF for the PDU Session to a DNN, S-NSSAI via AMF and SMF. See steps 1, 4, 5b, 11 and 12b in Figure 4.16.14.2-1. The PCF for the PDU Session reports that the SM Policy Association is established as described in clause 4.16.4 and provides the UE address(es). The SM Policy Association Termination notifies the PCF for the UE as described in clause 4.16.6. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.16.14 |
3,411 | 5.3.9 Requirements for the gNB F1 interfaces | Requirements given below apply to gNBs with split DU-CU implementations using F1 interface defined in TS 38.470[ NG-RAN; F1 general aspects and principles ] [31]. Signalling traffic (i.e. both F1-C interface management traffic defined in TS 38.470[ NG-RAN; F1 general aspects and principles ] [31] and F1-C signalling bearer defined in TS 38.472[ NG-RAN; F1 signalling transport ] [32]) and user plane data can be sent on the F1 interface between a given DU and its CU. - F1-C interface shall support confidentiality, integrity and replay protection. - All management traffic carried over the CU-DU link shall be integrity, confidentiality and replay protected. - The gNB shall support confidentiality, integrity and replay protection on the gNB DU-CU F1-U interface [33] for user plane. - F1-C and management traffic carried over the CU-DU link shall be protected independently from F1-U traffic. NOTE: The above requirements allow to have F1-U protected differently (including turning integrity and/or encryption off or on for F1-U) from all other traffic on the CU-DU (e.g. the traffic over F1-C). | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 5.3.9 |
3,412 | 5.23 Supporting for Asynchronous Type Communication | Asynchronous type communication (ATC) enables 5GC to delay synchronizing UE context with the UE, so as to achieve an efficient signalling overhead and increase system capacity. The support of ATC is optional for the AMF. 5GC supports asynchronous type communication with the following functionality: - Capability to store the UE context based on the received message, and synchronize the UE context with the involved network functions or UE later; For network function (e.g. PCF, UDM, etc.) triggered signalling procedure (e.g. network triggered Service Request procedure, network triggered PDU Session Modification procedure, etc.), if the UE CM state in the AMF is CM-IDLE state and the requesting network function indicates to the AMF the ATC is allowed for the signalling, if the AMF supports the ATC feature, the AMF may update and store the UE context based on the received message without paging UE immediately. When the UE CM state in the AMF enters CM-CONNECTED state, the AMF forwards N1 and N2 message to synchronize the UE context with the (R)AN and/or the UE. If the originating NF does not require immediate delivery, it may indicate that the AMF is allowed to use ATC. NOTE: Pre-Rel-17 AMF implementation cannot decode the indication that ATC is allowed. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.23 |
3,413 | 5.1.2 Entity authentication | The following security features related to entity authentication are provided: - user authentication: the property that the serving network corroborates the user identity of the user; - network authentication: the property that the user corroborates that he is connected to a serving network that is authorised by the user's HE to provide him services; this includes the guarantee that this authorisation is recent. To achieve these objectives, it is assumed that entity authentication should occur at each connection set-up between the user and the network. Two mechanisms have been included: an authentication mechanism using an authentication vector delivered by the user's HE to the serving network, and a local authentication mechanism using the integrity key established between the user and serving network during the previous execution of the authentication and key establishment procedure. Clause 6.3 describes an authentication and key establishment mechanism that achieves the security features listed above and in addition establishes a secret cipher key (see 5.1.3) and integrity key (see 5.1.4) between the user and the serving network. This mechanism should be invoked by the serving network after a first registration of a user in a serving network and after a service request, location update request, attach request, detach request or connection re-establishment request, when the maximum number of local authentications using the derived integrity key have been conducted. Clause 6.5 describes the local authentication mechanism. The local authentication mechanism achieves the security features user authentication and network authentication and uses an integrity key established between user and serving network during the previous execution of the authentication and key establishment procedure. This mechanism should be invoked by the serving network after a service request, location update request, attach request, detach request or connection re-establishment request, provided that the maximum number of local authentications using the same derived integrity key has not been reached yet. | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | 5.1.2 |
3,414 | A.3.1.2 ASN.1 identifier naming conventions | The naming of identifiers (i.e., the ASN.1 field and type identifiers) should be based on the following guidelines: - Message (PDU) identifiers should be ordinary mixed case without hyphenation. These identifiers, e.g., the RRCConnectionModificationCommand, should be used for reference in the procedure text. Abbreviations should be avoided in these identifiers and abbreviated forms of these identifiers should not be used. - Type identifiers other than PDU identifiers should be ordinary mixed case, with hyphenation used to set off acronyms only where an adjacent letter is a capital, e.g., EstablishmentCause, SelectedPLMN (not Selected-PLMN, since the "d" in "Selected" is lowercase), InitialUE-Identity and MeasSFN-SFN-TimeDifference. - Field identifiers shall start with a lowercase letter and use mixed case thereafter, e.g., establishmentCause. If a field identifier begins with an acronym (which would normally be in upper case), the entire acronym is lowercase (plmn-Identity, not pLMN-Identity). The acronym is set off with a hyphen (ue-Identity, not ueIdentity), in order to facilitate a consistent search pattern with corresponding type identifiers. - Identifiers should convey the meaning of the identifier and should avoid adding unnecessary postfixes (e.g. abstractions like 'Info') for the name. - Identifiers that are likely to be keywords of some language, especially widely used languages, such as C++ or Java, should be avoided to the extent possible. - Identifiers, other than PDU identifiers, longer than 25 characters should be avoided where possible. It is recommended to use abbreviations, which should be done in a consistent manner i.e. use 'Meas' instead of 'Measurement' for all occurrences. Examples of typical abbreviations are given in table A.3.1.2.1-1 below. - For future extension: When an extension is introduced a suffix is added to the identifier of the concerned ASN.1 field and/or type. A suffix of the form "-rX" is used, with X indicating the release, for ASN.1 fields or types introduced in a later release (i.e. a release later than the original/first release of the protocol) as well as for ASN.1 fields or types for which a revision is introduced in a later release replacing a previous version, e.g., Foo-r9 for the Rel-9 version of the ASN.1 type Foo. A suffix of the form "-rXb" is used for the first revision of a field that it appears in the same release (X) as the original version of the field, "-rXc" for a second intra-release revision and so on. A suffix of the form "-vXYZ" is used for ASN.1 fields or types that only are an extension of a corresponding earlier field or type (see clause A.4), e.g., AnElement-v10b0 for the extension of the ASN.1 type AnElement introduced in version 10.11.0 of the specification. A number 0...9, 10, 11, etc. is used to represent the first part of the version number, indicating the release of the protocol. Lower case letters a, b, c, etc. are used to represent the second (and third) part of the version number if they are greater than 9. In the procedural specification, in field descriptions as well as in headings suffices are not used, unless there is a clear need to distinguish the extension from the original field. - More generally, in case there is a need to distinguish different variants of an ASN.1 field or IE, a suffix should be added at the end of the identifiers e.g. MeasObjectUTRA, ConfigCommon. When there is no particular need to distinguish the fields (e.g. because the field is included in different IEs), a common field identifier name may be used. This may be attractive e.g. in case the procedural specification is the same for the different variants. - It should be avoided to use field identifiers with the same name within the elements of a CHOICE, including using a CHOICE inside a SEQUENCE (to avoid certain compiler errors). Table A.3.1.2-1: Examples of typical abbreviations used in ASN.1 identifiers NOTE: The table A.3.1.2.1-1 is not exhaustive. Additional abbreviations may be used in ASN.1 identifiers when needed. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | A.3.1.2 |
3,415 | 6.5.2.4.1 Minimum requirements | The peak-to-peak variation of the EVM equalizer coefficients contained within the frequency range of the uplink allocation shall not exceed the maximum ripple specified in Table 6.5.2.4.1-1 for normal conditions. For uplink allocations contained within both Range 1 and Range 2, the coefficients evaluated within each of these frequency ranges shall meet the corresponding ripple requirement and the following additional requirement: the relative difference between the maximum coefficient in Range 1 and the minimum coefficient in Range 2 must not be larger than 5 dB, and the relative difference between the maximum coefficient in Range 2 and the minimum coefficient in Range 1 must not be larger than 7 dB (see Figure 6.5.2.4.1-1). The EVM equalizer spectral flatness shall not exceed the values specified in Table 6.5.2.4.1-2 for extreme conditions. For uplink allocations contained within both Range 1 and Range 2, the coefficients evaluated within each of these frequency ranges shall meet the corresponding ripple requirement and the following additional requirement: the relative difference between the maximum coefficient in Range 1 and the minimum coefficient in Range 2 must not be larger than 6 dB, and the relative difference between the maximum coefficient in Range 2 and the minimum coefficient in Range 1 must not be larger than 10 dB (see Figure 6.5.2.4.1-1). Table 6.5.2.4.1-1: Minimum requirements for EVM equalizer spectrum flatness (normal conditions) Table 6.5.2.4.1-2: Minimum requirements for EVM equalizer spectrum flatness (extreme conditions) Figure 6.5.2.4.1-1: The limits for EVM equalizer spectral flatness with the maximum allowed variation of the coefficients indicated (the ETC minimum requirement within brackets). | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.5.2.4.1 |
3,416 | 10.5.1.12.3 PS domain specific system information | The purpose of the CN domain specific GSM-MAP NAS system information element, when used for the PS domain, is to provide the MS with actual parameter settings of parameters relevant only for GMM functionality. The coding of the information element identifier and length information is defined in the 3GPP TS 25.331[ None ] [23c]. Only the coding of the content is in the scope of the present document. For PS domain, the content of the CN domain specific GSM-MAP NAS system information element is coded as shown in figure 10.5.1.12.3/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.1.12.3/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The length of this element content is two octets. The MS shall ignore any additional octets received. Figure 10.5.1.12.3/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] PS domain specific system information element Table 10.5.1.12.3/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : PS domain specific system 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.1.12.3 |
3,417 | 7.6.3.1D Minimum requirements for ProSe | The relative throughput shall be ≥ 95% of the maximum throughput of the reference measurement channels as specified in Annex A.6.2 with parameters specified in Table 7.6.3.1D-1 and Table 7.6.3.1D-2. Table 7.6.3.1D-1: Narrow-band blocking for ProSe Direct Discovery Table 7.6.3.1D-2: Narrow-band blocking for ProSe Direct Communication For the UE which supports inter-band CA configuration in Table 7.3.1-1A, PUW power defined in Table 7.6.3.1D-1 and Table 7.6.3.1D-2 is increased by the amount given by ΔRIB,c in Table 7.3.1-1A. | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 7.6.3.1D |
3,418 | 4.12.2.2 Registration procedure for untrusted non-3GPP access | The signalling flow in Figure 4.12.2.2-1 does not show all the details of a registration procedure via untrusted non-3GPP access. It shows primarily the steps executed between the UE and N3IWF. All the details of a registration procedure, including interactions with PCF, UDM, etc. are specified in clause 4.2.2.2.2. Figure 4.12.2.2-1: Registration via untrusted non-3GPP access 1. The UE connects to an untrusted non-3GPP Access Network with any appropriate authentication procedure and it is assigned an IP address. For example, a non-3GPP authentication method can be used, e.g. no authentication (in the case of a free WLAN), EAP with pre-shared key, username/password, etc. When the UE decides to attach to 5GC network, the UE not operating in SNPN access mode for NWu interface selects an N3IWF in a 5G PLMN, as described in clause 6.3.6 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. When the UE decides to attach to 5GC network, the UE operating in SNPN access mode for NWu interface selects an N3IWF in an SNPN, as described in clause 6.3.6.2a of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. NOTE 1: The UE Selection of a N3IWF that supports the S-NSSAIs needed by the UE is enabled based on ANDSP configuration defined in TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The N3IWF selection based on this information is documented in TS 23.501[ System architecture for the 5G System (5GS) ] [2]. 2. The UE proceeds with the establishment of an IPsec Security Association (SA) with the selected N3IWF by initiating an IKE initial exchange according to RFC 7296 [3]. After step 2, all subsequent IKE messages are encrypted and integrity protected by using the IKE SA established in this step. 3. The UE shall initiate an IKE_AUTH exchange by sending an IKE_AUTH request message. The AUTH payload is not included in the IKE_AUTH request message, which indicates that the IKE_AUTH exchange shall use EAP signalling (in this case EAP-5G signalling). If the UE supports MOBIKE, it shall include a Notify payload in the IKE_AUTH request, as specified in RFC 4555 [40], indicating that MOBIKE is supported. In addition, as specified in TS 33.501[ Security architecture and procedures for 5G System ] [15], if the UE is provisioned with the N3IWF root certificate, it shall include the CERTREQ payload within the IKE_AUTH request message to request the N3IWF's certificate. In the case of WLAN access, if the UE has an MPS subscription, the UE shall include a Notify payload in the IKE_AUTH request indicating its MPS subscription. NOTE 2: Based on operator policy, the N3IWF can use the MPS subscription indication at this time to handle this UE with priority. 4. The N3IWF responds with an IKE_AUTH response message, which includes an EAP-Request/5G-Start packet. The EAP-Request/5G-Start packet informs the UE to initiate an EAP-5G session, i.e. to start sending NAS messages encapsulated within EAP-5G packets. If the N3IWF has received a CERTREQ payload from the UE, the N3IWF shall include the CERT payload in the IKE_AUTH response message containing the N3IWF's certificate. How the UE uses the N3IWF's certificate is specified in TS 33.501[ Security architecture and procedures for 5G System ] [15]. 5. The UE shall send an IKE_AUTH request, which includes an EAP-Response/5G-NAS packet that contains the Access Network parameters (AN parameters) and a Registration Request message. The AN parameters contain information that is used by the N3IWF for selecting an AMF in the 5G core network. This information includes e.g. the GUAMI, the Selected PLMN ID (or PLMN ID and NID, see clause 5.30 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]), the Requested NSSAI and the Establishment cause. The Establishment cause provides the reason for requesting a signalling connection with 5GC and the N3IWF may use the Establishment cause to determine the DSCP value on N2.. Whether and how the UE includes the Requested NSSAI as part of the AN parameters is dependent on the value of the Access Stratum Connection Establishment NSSAI Inclusion Mode parameter, as specified in clause 5.15.9 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The registration request may contain an indication that the UE supports N3IWF selection based on the slices the UE wishes to use over untrusted non-3GPP access (i.e. that the UE supports Extended Home N3IWF identifier configuration and Slice-specific N3IWF prefix configuration). If at step 1 the UE selects the N3IWF based on Tracking/Location Area of same PLMN as described in clause 6.3.6 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], the UE may include this TA in the last visited TAI in registration request in order to help the AMF to determine the target N3IWF as described in step 17. If the UE in SNPN access mode for NWu interface performs the Registration procedure for UE onboarding, the UE shall include an indication in the AN parameters that the connection request is for onboarding. The Registration Type "SNPN Onboarding" indicates that the UE wants to perform SNPN Onboarding Registration. NOTE 3: The N3IWF does not send an EAP-Identity request because the UE includes its identity in the first IKE_AUTH. This is in line with RFC 7296 [3] clause 3.16. 6. The N3IWF shall select an AMF based on the received AN parameters and local policy, as specified in clause 6.3.5 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The N3IWF shall then forward the Registration Request received from the UE to the selected AMF within an N2 message. This message contains N2 parameters that include the Selected PLMN ID and optionally the Selected NID and the Establishment cause. NOTE 4: The Selected NID is present when the UE connects to an SNPN via Untrusted non-3GPP access. 7. The selected AMF may decide to request the SUCI by sending a NAS Identity Request message to UE. This NAS message and all subsequent NAS messages are sent to UE encapsulated within EAP/5G-NAS packets. The AMF may use the Establishment cause to determine the Message Priority header and then the DSCP value for subsequent signalling according to TS 29.500[ 5G System; Technical Realization of Service Based Architecture; Stage 3 ] [17]. 8. The AMF may decide to authenticate the UE by invoking an AUSF. In this case, the AMF shall select an AUSF as specified in clause 6.3.4 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] based on SUPI or SUCI. The AUSF executes the authentication of the UE as specified in TS 33.501[ Security architecture and procedures for 5G System ] [15]. The AUSF selects a UDM as described in clause 6.3.8 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] and gets the authentication data from UDM. The authentication packets are encapsulated within NAS authentication messages and the NAS authentication messages are encapsulated within EAP/5G-NAS packets. After the successful authentication: - In step 8h, the AUSF shall send the anchor key (SEAF key) to AMF which is used by AMF to derive NAS security keys and a security key for N3IWF (N3IWF key). The UE also derives the anchor key (SEAF key) and from that key it derives the NAS security keys and the security key for N3IWF (N3IWF key). The N3IWF key is used by the UE and N3IWF for establishing the IPsec Security Association (in step 11). - In step 8h, the AUSF shall also include the SUPI, if in step 8a the AMF provided to AUSF a SUCI. NOTE 5: EAP-AKA' or 5G-AKA are allowed for the authentication of UE via non-3GPP access, as specified in TS 33.501[ Security architecture and procedures for 5G System ] [15]. Figure 4.12.2.2-1 only shows authentication flow using EAP-AKA'. Authentication methods other than EAP-AKA' or 5G-AKA are also allowed for UE accessing SNPN services via a PLMN, as specified in TS 33.501[ Security architecture and procedures for 5G System ] [15], Annex I, as well as for UE accessing SNPN services directly via Untrusted non-3GPP access. If the UE in SNPN access mode for NWu interface performs the Registration procedure for UE onboarding, the interaction between AMF and AUSF (step 8a, 8b, 8g and 8h in Figure 4.12.2.2-1) is replaced with step 9-1 or step 9-2 or step 9-3 in Figure 4.2.2.2.4-1, depending on the 5GC architecture that is used for UE onboarding. 9a. The AMF shall send a NAS Security Mode Command to UE in order to activate NAS security. If an EAP-AKA' authentication was successfully executed in step 8, the AMF shall encapsulate the EAP-Success received from AUSF within the NAS Security Mode Command message. 9b. The N3IWF shall forward the NAS Security Mode Command message to UE within an EAP/5G-NAS packet. 9c. The UE completes the EAP-AKA' authentication (if initiated in step 8), creates a NAS security context and an N3IWF key and sends the NAS Security Mode Complete message within an EAP/5G-NAS packet. 9d. The N3IWF relays the NAS Security Mode Complete message to the AMF. 10a. Upon receiving NAS Security Mode Complete, the AMF shall send an NGAP Initial Context Setup Request message that includes the N3IWF key. 10b. This triggers the N3IWF to send an EAP-Success to UE, which completes the EAP-5G session. No further EAP-5G packets are exchanged. 11. The IPsec SA is established between the UE and N3IWF by using the common N3IWF key that was created in the UE in step 9c and received by the N3IWF in step 10a. This IPsec SA is referred to as the "signalling IPsec SA". After the establishment of the signalling IPsec SA, the N3IWF notifies the AMF that the UE context (including AN security) was created by sending a NGAP Initial Context Setup Response. The signalling IPsec SA shall be configured to operate in tunnel mode and the N3IWF shall assign to UE: a) an "inner" IP address; and b) a NAS_IP_ADDRESS and a TCP port number. The N3IWF may apply a DSCP value to this signalling IPsec SA, in which case all IP packets exchanged between the UE and N3IWF via the "signalling IPsec SA" shall be marked with this DSCP value. If the N3IWF has received an indication that the UE supports MOBIKE (see step 3), then the N3IWF shall include a Notify payload in the IKE_AUTH response message sent in step 11a, indicating that MOBIKE shall be supported, as specified in RFC 4555 [40]. NOTE 6: The DSCP value is determined by operator policy, and may e.g., be based on the DSCP value on N2. All subsequent NAS messages exchanged between the UE and N3IWF shall be sent via the signalling IPsec SA and shall be carried over TCP/IP. The UE shall send NAS messages within TCP/IP packets with source address the "inner" IP address of the UE and destination address the NAS_IP_ADDRESS that is received in step 11a. The N3IWF shall send NAS messages within TCP/IP packets with source address the NAS_IP_ADDRESS and destination address the "inner" IP address of the UE. The TCP connection used for reliable NAS transport between the UE and N3IWF shall be initiated by the UE right after the signalling IPsec SA is established in step 11a. The UE shall send the TCP connection request to the NAS_IP_ADDRESS and to the TCP port number specified in TS 24.502[ Access to the 3GPP 5G Core Network (5GCN) via non-3GPP access networks ] [41]. 12. The AMF determines the allowed subset of the Requested NSSAI that is allowed by the Subscribed S-NSSAI(s); the AMF may detect that the N3IWF used by the UE is not compatible with this allowed subset and based on operator's policy configured in the AMF, the AMF determines whether a different N3IWF should be used. If the UE supports slice-based N3IWF selection and the AMF determines to use a different N3IWF, then the AMF proceeds with steps 15-19. Otherwise, i.e. if the AMF determines to use the selected N3IWF that supports part of the allowed subset, the AMF proceeds with steps 13 and 14. In this case, steps 15-19 are skipped. NOTE 7: The AMF considers the subscribed S-NSSAI(s) before determining to trigger the UE PCF to avoid triggering the UE PCF to update the UE policies for Requested S-NSSAIs that the UE is not subscribed for. 13. The AMF sends the NAS Registration Accept message in an N2 message sent to the N3IWF. The N2 Message includes the Allowed NSSAI for the access type for the UE. The Allowed NSSAI is a subset of the slices supported by the selected N3IWF. 14. The N3IWF forwards the NAS Registration Accept message to UE via the established signalling IPsec SA. If the NAS Registration Accept message is received by the N3IWF before the IPsec SA is established, the N3IWF shall store it and forward it to the UE only after the establishment of the signalling IPsec SA. Steps 15 to 19 correspond to the case where the AMF has detected that the N3IWF used by the UE is not compatible with the subset of the requested NSSAI that is allowed by the subscribed S-NSSAI(s). 15. If the UE Registration Request contains an indication that the UE supports N3IWF selection based on the slices the UE wishes to use over untrusted non-3GPP access and the AMF is able to select a UE PCF that supports UE policies for slice specific N3IWF selection, the AMF may trigger UE policy association establishment if a suitable UE policy association does not exist yet. Then the AMF triggers the UE PCF to update the UE policies for slice specific N3IWF selection by either indicating the request in Npcf_UEPolicyControl_Create or, if a UE policy already exists, by issuing a Npcf_UEPolicyControl_Update. The AMF requests the PCF to receive a notification when the PCF has completed the update of these UE policies. NOTE 8: The UE is assumed to inform PCF whether the UE supports Extended Home N3IWF identifier configuration and Slice-specific N3IWF prefix configuration as part of the UE policy update procedure. Details will be specified in Stage 3 specifications. 16. The PCF updates the UE policies for slice specific N3IWF selection per the procedure defined in figure 4.2.4.3-1. When the update of these UE policies is completed, the PCF notifies the AMF by invoking Npcf_UEPolicyControl_UpdateNotify. 17. The AMF sends via the N3IWF a UE Registration Reject indicating that the UE selected N3IWF was not appropriate for the requested slices that the UE is allowed to access to. The AMF optionally may provide target N3IWF information (FQDN and/or IP address) to the UE within the Registration Reject message. NOTE 9: The AMF may determine a target N3IWF that supports the subset of the requested NSSAI that is allowed by the subscribed S-NSSAI(s) based on the list of supported TAs and the corresponding list of supported slices for each TA obtained in N2 interface management procedures as specified in TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [10]. To determine the target N3IWF, the AMF may take into account UE location corresponding to last visited TAI included in Registration Request as described at step 5 when the UE selects N3IWF based on Tracking/Location Area of same PLMN. 18. If supported by the UE and if the UE received target N3IWF information in step 17, the UE connects to the target N3IWF, otherwise the UE may perform N3IWF selection again using the updated N3IWF selection information received in step 16. The UE uses the target N3IWF information in the Registration Reject only for the N3IWF selection directly following the rejected registration and UE shall not store for future use. The AMF provides the Access Type set to "Non-3GPP access" to the UDM when it registers with the UDM and the RAT type determined as specified in clause 5.3.2.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. NOTE 10: The Access Type and the RAT type are is set to "Untrusted Non-3GPP access" even when the UE accesses SNPN services via PLMN over 3GPP access. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.12.2.2 |
3,419 | 5.31.4.3 Control Plane Relocation Indication procedure | For intra-NB-IoT mobility when UE and AMF are using Control Plane CIoT 5GS Optimisation, the CP Relocation Indication procedures may be used. The purpose of the CP Relocation Indication procedure is to request the AMF to authenticate the UE's re-establishment request (see TS 33.501[ Security architecture and procedures for 5G System ] [29]), and initiate the establishment of the UE's N2 connection after the UE has initiated an RRC Re-Establishment procedure in a new NG-RAN node (see TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [27]). The RRC Re-Establishment procedure uses the Truncated 5G-S-TMSI as the UE identifier. The NG-RAN is configured with the sizes of the components of the Truncated 5G-S-TMSI and it is configured with how to recreate the AMF Set ID, the AMF Pointer and 5G-TMSI from the equivalent truncated parameters (see TS 23.003[ Numbering, addressing and identification ] [19]). The AMF configures the UE with the Truncated 5G-S-TMSI Configuration that provides the sizes of the components of the Truncated 5G-S-TMSI as described in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [47] during the Registration. The configuration of these parameters are specific to each PLMN. NOTE: Network sharing default configuration of the sizes of the truncated components is described in TS 23.003[ Numbering, addressing and identification ] [19]. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.31.4.3 |
3,420 | 9.9.4.2.2 TDD | The minimum performance requirement in Table 9.9.4.2.2-2 is defined as a) The ratio of the throughput obtained when transmitting based on UE reported RI and that obtained when transmitting with fixed rank 1 shall be ≥ ; b) The ratio of the throughput obtained when transmitting based on UE reported RI and that obtained when transmitting with fixed rank 2 shall be ≥ ; For the parameters specified in Table 9.9.4.2.2-1, and using the downlink physical channels specified in Annex C.3.2, the minimum requirements are specified in Table 9.9.4.2.2-2. Table 9.9.4.2.2-1: RI Test (TDD) Table 9.9.4.2.2-2: Minimum requirement (TDD) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 9.9.4.2.2 |
3,421 | Annex B (normative): Mapping between temporary identities | When interworking procedures with N26 are used and the UE performs idle mode mobility from 5GC to EPC the following mapping from 5G GUTI to EPS GUTI applies: - 5G <MCC> maps to EPS <MCC> - 5G <MNC> maps to EPS <MNC> - 5G <AMF Region ID> and 5G <AMF Set ID> maps to EPS <MMEGI> and part of EPS <MMEC> - 5G <AMF Pointer> map to part of EPS <MMEC> - 5G <5G-TMSI> maps to EPS <M-TMSI> NOTE 1: The mapping described above does not necessarily imply the same size for the 5G GUTI and EPS GUTI fields that are mapped. The size of 5G GUTI fields and other mapping details will be defined in TS 23.003[ Numbering, addressing and identification ] [19]. NOTE 2: To support interworking with the legacy EPC core network entity (i.e. when MME is not updated to support interworking with 5GS), it is assumed that the 5G <AMF Region ID> and EPS <MMEGI> is partitioned to avoid overlapping values in order to enable discovery of source node (i.e. MME or AMF) without ambiguity. Once the EPS in the PLMN has been updated to support interworking with 5GS, the full address space of the AMF Region ID can be used for 5GS. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | Annex |
3,422 | 5.2.2.5.4 Namf_Location_ProvideLocationInfo service operation | Service operation name: Namf_Location_ProvideLocationInfo Description: Provides Network Provided Location Information (NPLI) of a target UE to the consumer NF. Input, Required: UE Identification (SUPI). Input, Optional: 5GS Location Information Request, Current Location Request, RAT type Requested, Local Time Zone Request. Output, Required: Success/Failure indication. Output, Optional: 5GS Location Information (Cell Identity, Tracking Area Identity, Geographical/Geodetic Information, Current Location Retrieved, Age of Location Information, Current RAT Type), Local Time Zone, Failure Cause. In the case of non-3GPP access: a UE local IP address (used to reach the N3IWF/TNGF) and optionally UDP source port number (if NAT is detected). | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.2.5.4 |
3,423 | 7.2.21 Release Access Bearers Request | The Release Access Bearers Request message shall be sent on the S11 interface by the MME to the SGW as part of the S1 release procedure and eNodeB initiated Connection Suspend procedure. It may also be sent on the S11 interface by the MME to the SGW as part of the Establishment of S1-U bearer during Data Transport in Control Plane CIoT EPS optimisation procedure (see clause 5.3.4B.4 of 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [3]). NOTE: The S1 release procedure is also used to release the S11-U bearers for the Control Plane CIoT EPS optimisation, except in the case of data buffering in the MME. The message shall also be sent on the S4 interface by the SGSN to the SGW as part of the procedures: - RAB release using S4 - Iu Release using S4 - READY to STANDBY transition within the network Table 7.2.21-1: Information Element in Release Access Bearers 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.21 |
3,424 | 5.34.3 I-SMF selection, V-SMF reselection | The AMF is responsible of detecting when to add or to remove an I-SMF or a V-SMF for a PDU Session. For this purpose, the AMF gets from NRF information about the Service Area and supported DNAI(s) of SMF(s). During mobility events such as Hand-Over or AMF change, if the service area of the SMF does not include the new UE location, then the AMF selects and inserts an I-SMF which can serve the UE location and the S-NSSAI. Conversely if the AMF detects that an I-SMF is no more needed (as the service area of the SMF includes the new UE location) it removes the I-SMF and interfaces directly with the SMF of the PDU Session. If the AMF detects that the SMF cannot serve the UE location (e.g. due to mobility), then the AMF selects a new I-SMF serving the UE location. If the existing I-SMF (or V-SMF) cannot serve the UE location (e.g. due to mobility) and the service area of the SMF does not include the new UE location (or the PDU Session is Home Routed), then the AMF initiates an I-SMF (or V-SMF) change. A V-SMF change may take place either at intra-PLMN or inter-PLMN mobility. According to the PCC rules related with AF influence traffic mechanism regarding DNAI(s), the SMF determines the target DNAI which is applicable to the current UE location and which can be based on the common DNAI (if applicable) as described in TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [130]. If current (I-)SMF cannot serve the target DNAI or if the SMF can server the target DNAI and existing I-SMF is not needed, the SMF may send the target DNAI information to the AMF for triggering I-SMF (re)selection or removal, e.g. the AMF performs I-SMF (re)selection or removal based on the target DNAI and supported DNAI(s) of (I-)SMF. If the SMF determines that target DNAI currently served by I-SMF should not be used for the PDU Session hence the existing I-SMF is not needed (e.g. due to the updated PCC rules removes DNAI(s) that was provided in the previous PCC rules), the SMF sends the target DNAI information without including target DNAI to AMF, which may trigger the I-SMF removal. At PDU Session Establishment in non-roaming and roaming with LBO scenarios, if the AMF or SCP cannot select an SMF with a Service Area supporting the current UE location for the selected (DNN, S-NSSAI) and required SMF capabilities, the AMF selects an SMF for the selected (DNN, S-NSSAI) and required capabilities and in addition selects an I-SMF serving the UE location and the S-NSSAI. Compared to the SMF selection function defined in clause 6.3.2, the following parameters are not applicable for I-SMF/V-SMF selection: - Data Network Name (DNN). - Subscription information from UDM. NOTE 1: All SMF(s) and I-SMF are assumed to be able to control the UPF mapping between EPC bearers and 5GC QoS Flows. If HR-SBO roaming is allowed for a PDU Session, the DNN is also considered for V-SMF selection. If delegated SMF discovery is used at PDU Session establishment: 1. The AMF sends Nsmf_PDUSession_CreateSMContext Request to SCP and includes the parameters as defined in clause 6.3.2 (e.g. the DNN, required SMF capabilities, UE location) as discovery and selection parameters. If the SCP successfully selects an SMF matching all discovery and selection parameters, the SCP forwards the Nsmf_PDUSessionCreateSMContext Request to the selected SMF. 2. If the SCP cannot select an SMF matching all discovery and selection parameters, the SCP returns a dedicated error to AMF. In this case the I-SMF also need be discovered. 3. Upon reception of the error from the SCP that an SMF matching all discovery and selection parameters cannot be found, the AMF performs the discovery and selection of the SMF from NRF (thus not providing the UE location as a discovery parameter). The AMF may indicate the maximum number of SMF instances to be returned from NRF, i.e. SMF selection at NRF. 4. The AMF sends Nsmf_PDUSession_CreateSMContext Request to SCP, which includes the endpoint (e.g. URI) of the selected SMF and the discovery and selection parameters as defined in clause 6.3.2 except the DNN and the required SMF capabilities, i.e. parameter for I-SMF selection. The SCP performs discovery and selection of the I-SMF and forwards the Nsmf_PDUSession_CreateSMContext Request to the selected I-SMF. 5. The I-SMF sends the Nsmf_PDUSession_Create Request towards the SMF via the SCP; the I-SMF uses the received endpoint (e.g. URI) of the selected SMF to construct the target destination to be addressed. The SCP forwards the Nsmf_PDUSession_Create Request to the SMF. 6. The SMF answers to the I-SMF that answers to the AMF; in this answer the AMF receives the I-SMF ID. 7. Upon reception of a response from I-SMF, based on the received I-SMF ID, the AMF may obtain the SMF Service Area of the I-SMF from NRF. The AMF uses the SMF Service Area of the I-SMF to determine the need for I-SMF relocation upon subsequent UE mobility. If delegated I-SMF discovery is used once the PDU Session establishment has been established, the procedure starts at step 4 above and is further detailed in the messages flows in clause 23 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. If delegated V-SMF discovery is used for V-SMF reselection, clause 6.3.2 applies, but there is no need for discovery and selection of the H-SMF. This is further detailed in the messages flows in clause 23 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.34.3 |
3,425 | 4.2.3 Common architecture – service based interface | The following figures provide an overview of the logical ubiquitous charging architecture and the information flows for converged offline and online charging in service based interface variant for 5G systems and Edge Computing enabling sub-systems. Figure 4.2.3.1 provides the overview in service based representation: Figure 4.2.3.1: Logical ubiquitous charging architecture and information flows for 5G systems – service based representation Figure 4.2.3.2 provides the overview in reference point representation: Figure 4.2.3.2: Logical ubiquitous charging architecture and information flows for 5G systems – reference point representation The reference points are defined in clause 4.4.3. For the sake of simplicity, the SMF+PGW-C is not explicitly added in Figure 4.2.3.1 and Figure 4.2.3.2, and is represented by the SMF. The SMF+PGW-C uses Nchf for 5GS and EPC interworking as well as when enhanced to support GERAN/UTRAN. The Nchf_SpendingLimitControl service exposed by CHF and consumed by the PCF is specified in TS 23.502[ Procedures for the 5G System (5GS) ] [214]. | 3GPP TS 32.240 | Telecommunication management; Charging management; Charging architecture and principles | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.2.3 |
3,426 | 6.3.2.1 Multiple registrations in different PLMNs | The UE shall independently maintain and use two different 5G security contexts, one per PLMN's serving network. Each security context shall be established separately via a successful primary authentication procedure with the Home PLMN. The ME shall store the two different 5G security contexts on the USIM if the USIM supports the 5G parameters storage. If the USIM does not support the 5G parameters storage, then the ME shall store the two different 5G security contexts in the ME non-volatile memory. Both of the two different 5G security contexts are current 5G security context. The latest KAUSF result of the successful completion of the latest primary authentication shall be used by the UE and the HN regardless over which access network type (3GPP or non-3GPP) it was generated. The HN shall keep the latest KAUSF generated during successful authentication over a given access even if the UE is deregistered from that access, but the UE is registered via another access. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.3.2.1 |
3,427 | 16.12.6.1 Switching from indirect to direct path | For service continuity of L2 U2N Relay, the following procedure is used, in case of L2 U2N Remote UE switching from indirect to direct path under the same gNB: Figure 16.12.6.1-1: Procedure for L2 U2N Remote UE intra-gNB switching from indirect to direct path 1. The Uu measurement configuration and measurement report signalling procedures are performed to evaluate both relay link measurement and Uu link measurement. The measurement results from L2 U2N Remote UE are reported when configured measurement reporting criteria are met. The sidelink relay measurement report shall include at least L2 U2N Relay UE's source L2 ID, serving cell ID (i.e., NCGI/NCI), and sidelink measurement quantity result. The sidelink measurement quantity can be SL-RSRP of the serving L2 U2N Relay UE, and if SL-RSRP is not available, SD-RSRP is used. 2. The gNB decides to switch the L2 U2N Remote UE onto direct Uu path. 3. The gNB sends the RRCReconfiguration message to the L2 U2N Remote UE. The L2 U2N Remote UE stops User Plane and Control Plane transmission via the L2 U2N Relay UE after reception of the RRCReconfiguration message with the path switch configuration. 4. The L2 U2N Remote UE synchronizes with the gNB and performs Random Access. 5. The UE (i.e., L2 U2N Remote UE in previous steps) sends the RRCReconfigurationComplete message to the gNB via the direct path, using the configuration provided in the RRCReconfiguration message. From this step, the UE (i.e., L2 U2N Remote UE in previous steps) uses the RRC connection via the direct path to the gNB. 6. The gNB sends the RRCReconfiguration message to the L2 U2N Relay UE to reconfigure the connection between the L2 U2N Relay UE and the gNB. The RRCReconfiguration message to the L2 U2N Relay UE can be sent any time after step 3 based on gNB implementation (e.g., to release Uu Relay RLC Channel and PC5 Relay RLC channel configuration for relaying, and bearer mapping configuration related to the L2 U2N Remote UE). 7. Either L2 U2N Relay UE or L2 U2N Remote UE's AS layer indicates upper layers to release PC5 unicast link after receiving the RRCReconfiguration message from the gNB. The timing to execute link release is up to UE implementation. 8. The data path is switched from indirect path to direct path between the UE (i.e., previous L2 U2N Remote UE) and the gNB. The PDCP re-establishment or PDCP data recovery in uplink is performed by the UE (i.e., previous L2 U2N Remote UE) for lossless delivery during path switch if gNB configures it. NOTE 1: Step 8 can be executed any time after step 4. Step 8 is independent of step 6 and step 7. For service continuity of L2 U2N Relay, the following procedure is used, in case of L2 U2N Remote UE switching from indirect to direct path under another gNB: Figure 16.12.6.1-2: Procedure for L2 U2N Remote UE inter-gNB switching from indirect to direct path 1. The Uu measurement configuration is configured by the source gNB, and measurement report signalling procedures are performed by the L2 U2N Remote UE to evaluate both relay link measurement and Uu link measurement. The measurement results from L2 U2N Remote UE are reported when configured measurement reporting criteria are met. The sidelink relay measurement report shall include at least L2 U2N Relay UE's source L2 ID, serving cell ID (i.e., NCGI/NCI), and sidelink measurement quantity result. The sidelink measurement quantity can be SL-RSRP of the serving L2 U2N Relay UE, and if SL-RSRP is not available, SD-RSRP is used. 2. The source gNB decides to trigger path switch for the L2 U2N Remote UE, onto direct path. 3. The source gNB sends the HANDOVER REQUEST message to the target gNB with necessary information to prepare the handover at the target side. NOTE 2: In order to support the DL lossless handover for the L2 U2N Remote UE, the source gNB may not discard the DL data even though the delivery of the data has been acknowledged by the L2 U2N Relay UE based on the gNB implementation. Then, the source gNB forwards the buffered DL data to the target gNB during the data forwarding procedure. 4. Admission Control may be performed by the target gNB. 5. The target gNB sends the HANDOVER REQUEST ACKNOWLEDGE message to the source gNB, which contains new RRC configuration for the L2 U2N Remote UE. 6. The source gNB triggers the path switch by sending an RRCReconfiguration message to the L2 U2N Remote UE, containing at least cell ID and the information required to access the target cell. The L2 U2N Remote UE stops User Plane and Control Plane transmission via the L2 U2N Relay UE after reception of the RRCReconfiguration message. 7. The source gNB sends the SN STATUS TRANSFER message to the target gNB to convey the uplink PDCP SN receiver status and the downlink PDCP SN transmitter status of the L2 U2N Remote UE's DRBs for which PDCP status preservation applies (i.e. for RLC AM). 8. The L2 U2N Remote UE synchronizes with the target gNB and performs Random Access. 9. The L2 U2N Remote UE sends RRCReconfigurationComplete message to target gNB via the direct path. 10. The target gNB sends the UE CONTEXT RELEASE message to inform the source gNB about the success of the path switch. 11. The source gNB sends RRCReconfiguration message to the L2 U2N Relay UE to reconfigure the connection between the L2 U2N Relay UE and the source gNB. The RRCReconfiguration message to the L2 U2N Relay UE can be sent any time after step 6 based on source gNB implementation (e.g., to release Uu Relay RLC channel and PC5 Relay RLC channel configuration for relaying, and bearer mapping configuration related to the L2 U2N Remote UE). 12. Either L2 U2N Relay UE or L2 U2N Remote UE's AS layer indicates upper layer to release PC5 unicast link after receiving the RRCReconfiguration message from the source gNB. The timing to execute link release is up to UE implementation. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.12.6.1 |
3,428 | I.8.1 Credentials holder using AUSF and UDM for primary authentication | For SNPNs with Credentials Holder using AUSF and UDM for primary authentication, clause 5.30.2.9.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] states that the UE is not considered to be roaming, however SNPN and Credentials Holder communicate via SEPPs. The following requirements and procedures related to SEPPs and interconnect security apply for SNPNs with Credentials Holder using AUSF and UDM for primary authentication: - Requirements for Security Edge Protection Proxy (SEPP), clause 5.9.3.2 - Protection between SEPPs, clause 13.1.2. NOTE: IPX providers are not expected to be used between SNPN and Credentials holder using AUSF and UDM for primary authentication. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | I.8.1 |
3,429 | 9.2.2.1 Overview | RRC_INACTIVE is a state where a UE remains in CM-CONNECTED and can move within an area configured by NG-RAN (the RNA) without notifying NG-RAN. In RRC_INACTIVE, the last serving gNB node keeps the UE context and the UE-associated NG connection with the serving AMF and UPF. For a UE in RRC_INACTIVE with eDRX cycle longer than 10.24 seconds, the NG-RAN node may, based on implementation, send a request to the AMF to perform MT Communication Handling as described in TS 23.501[ System architecture for the 5G System (5GS) ] [3]. If the last serving gNB receives DL data from the UPF or DL UE-associated signalling from the AMF (except the UE Context Release Command message) while the UE is in RRC_INACTIVE, it pages in the cells corresponding to the RNA and may send XnAP RAN Paging to neighbour gNB(s) if the RNA includes cells of neighbour gNB(s). Upon receiving the RAN Paging Request message from the AMF while the UE is in RRC_INACTIVE with eDRX beyond 10.24 seconds, the last serving gNB may page in its cells comprised in the RNA and may send XnAP RAN Paging to neighbour gNB(s) if the RNA includes cells of neighbour gNB(s), in order for the gNB to trigger the UE to resume connection in RRC_CONNECTED state or RRC_INACTIVE state. Upon receiving the UE Context Release Command message while the UE is in RRC_INACTIVE, the last serving gNB may page in the cells corresponding to the RNA and may send XnAP RAN Paging to neighbour gNB(s) if the RNA includes cells of neighbour gNB(s), in order to release UE explicitly. Upon receiving the NG RESET message while the UE is in RRC_INACTIVE, the last serving gNB may page involved UEs in the cells corresponding to the RNA and may send XnAP RAN Paging to neighbour gNB(s) if the RNA includes cells of neighbour gNB(s) in order to explicitly release involved UEs. Upon RAN paging failure, the gNB behaves according to TS 23.501[ System architecture for the 5G System (5GS) ] [3]. The AMF provides to the NG-RAN node the Core Network Assistance Information to assist the NG-RAN node's decision whether the UE can be sent to RRC_INACTIVE, and to assist UE configuration and paging in RRC_INACTIVE. The Core Network Assistance Information includes the registration area configured for the UE, the Periodic Registration Update timer, and the UE Identity Index value, and may include the UE specific DRX, an indication if the UE is configured with Mobile Initiated Connection Only (MICO) mode by the AMF, the Expected UE Behaviour, the UE Radio Capability for Paging, the PEI with Paging Subgrouping assistance information, the NR Paging eDRX Information, the Paging Cause Indication for Voice Service, the Hashed UE Identity Index Value and the CN support indication for MT Communication Handling. The UE registration area is taken into account by the NG-RAN node when configuring the RNA. The UE specific DRX and UE Identity Index value are used by the NG-RAN node for RAN paging. The Periodic Registration Update timer is taken into account by the NG-RAN node to configure Periodic RNA Update timer. The NG-RAN node takes into account the Expected UE Behaviour to assist the UE RRC state transition decision. The NG-RAN node may use the UE Radio Capability for Paging during RAN Paging. The NG-RAN node takes into account the PEI with Paging Subgrouping assistance information for subgroup paging in RRC_INACTIVE except when the UE context contains an emergency PDU session in which case the PEI with Paging Subgrouping assistance information shall not be used according to TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [28]. When sending the XnAP RAN Paging to neighbour NG-RAN node(s), the PEI with Paging Subgrouping assistance information may be included. The NG-RAN node takes into account the NR Paging eDRX Information to configure the RAN Paging when the NR UE is in RRC_INACTIVE. When sending XnAP RAN Paging to neighbour NG-RAN node(s), the NR Paging eDRX Information for RRC_IDLE and for RRC_INACTIVE may be included. The NG-RAN node takes into consideration the Paging Cause Indication for Voice Service to include the Paging Cause in RAN Paging for a UE in RRC_INACTIVE state. When sending XnAP RAN Paging to neighbour NG-RAN node(s), the Paging Cause may be included. When sending XnAP RAN Paging to neighbour NG-RAN node(s), the Hashed UE Identity Index Value may be included to determine the start point of PTW. The NG-RAN takes into account the CN support indication for MT Communication Handling when deciding to request the AMF for MT Communication Handling for a UE in RRC_INACTIVE state with long eDRX beyond 10.24 seconds as described in TS 23.501[ System architecture for the 5G System (5GS) ] [3]. At transition to RRC_INACTIVE the NG-RAN node may configure the UE with a periodic RNA Update timer value. At periodic RNA Update timer expiry without notification from the UE, the gNB behaves as specified in TS 23.501[ System architecture for the 5G System (5GS) ] [3]. If the UE accesses a gNB other than the last serving gNB, the receiving gNB triggers the XnAP Retrieve UE Context procedure to get the UE context from the last serving gNB and may also trigger an Xn-U Address Indication procedure including tunnel information for potential recovery of data from the last serving gNB. Upon successful UE context retrieval, the receiving gNB shall perform the slice-aware admission control in case of receiving slice information and becomes the serving gNB and it further triggers the NGAP Path Switch Request and applicable RRC procedures. After the path switch procedure, the serving gNB triggers release of the UE context at the last serving gNB by means of the XnAP UE Context Release procedure. In case the UE is not reachable at the last serving gNB, the gNB shall fail any AMF initiated UE-associated class 1 procedure which allows the signalling of unsuccessful operation in the respective response message. It may trigger the NAS Non Delivery Indication procedure to report the non-delivery of any non PDU Session related NAS PDU received from the AMF as specified in TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [26]. If the UE accesses a gNB other than the last serving gNB and the receiving gNB does not find a valid UE Context, the receiving gNB can perform establishment of a new RRC connection instead of resumption of the previous RRC connection. UE context retrieval will also fail and hence a new RRC connection needs to be established if the serving AMF changes. A UE in the RRC_INACTIVE state is required to initiate RNA update procedure when it moves out of the configured RNA. When receiving RNA update request from the UE, the receiving gNB triggers the XnAP Retrieve UE Context procedure to get the UE context from the last serving gNB and may decide to send the UE back to RRC_INACTIVE state, move the UE into RRC_CONNECTED state, or send the UE to RRC_IDLE. In case of periodic RNA update, if the last serving gNB decides not to relocate the UE context, it fails the Retrieve UE Context procedure and sends the UE back to RRC_INACTIVE, or to RRC_IDLE directly by an encapsulated RRCRelease message. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 9.2.2.1 |
3,430 | 8.3 International Mobile Subscriber Identity (IMSI) | International Mobile Subscriber Identity (IMSI) is transferred via GTP tunnels. The sending entity copies the value part of the IMSI into the Value field of the IMSI IE. IMSI is defined in 3GPP TS 23.003[ Numbering, addressing and identification ] [2]. Figure 8.3-1: IMSI Octets 5 to (n+4) represent the IMSI value in international number format as described in ITU-T Rec E.212 [64], encoded as TBCD digits, i.e. digits from 0 through 9 are encoded "0000" to "1001". When there is an odd number of digits, bits 8 to 5 of the last octet are encoded with the filler "1111". The maximum number of digits is 15. | 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.3 |
3,431 | – Paging | The Paging message is used for the notification of one or more UEs. Signalling radio bearer: N/A RLC-SAP: TM Logical channel: PCCH Direction: Network to UE Paging message -- ASN1START -- TAG-PAGING-START Paging ::= SEQUENCE { pagingRecordList PagingRecordList OPTIONAL, -- Need N lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension Paging-v1700-IEs OPTIONAL } Paging-v1700-IEs ::= SEQUENCE { pagingRecordList-v1700 PagingRecordList-v1700 OPTIONAL, -- Need N pagingGroupList-r17 PagingGroupList-r17 OPTIONAL, -- Need N nonCriticalExtension Paging-v1800-IEs OPTIONAL } Paging-v1800-IEs ::= SEQUENCE { pagingRecordList-v1800 PagingRecordList-v1800 OPTIONAL, -- Need N pagingGroupList-v1800 PagingGroupList-v1800 OPTIONAL, -- Need N nonCriticalExtension SEQUENCE {} OPTIONAL } PagingRecordList ::= SEQUENCE (SIZE(1..maxNrofPageRec)) OF PagingRecord PagingRecordList-v1700 ::= SEQUENCE (SIZE(1..maxNrofPageRec)) OF PagingRecord-v1700 PagingGroupList-r17 ::= SEQUENCE (SIZE(1..maxNrofPageGroup-r17)) OF TMGI-r17 PagingRecordList-v1800 ::= SEQUENCE (SIZE(1..maxNrofPageRec)) OF PagingRecord-v1800 PagingGroupList-v1800 ::= SEQUENCE (SIZE(1..maxNrofPageGroup-r17)) OF GroupPaging-r18 PagingRecord ::= SEQUENCE { ue-Identity PagingUE-Identity, accessType ENUMERATED {non3GPP} OPTIONAL, -- Need N ... } PagingRecord-v1700 ::= SEQUENCE { pagingCause-r17 ENUMERATED {voice} OPTIONAL -- Need N } PagingRecord-v1800 ::= SEQUENCE { mt-SDT ENUMERATED {true} OPTIONAL -- Need N } PagingUE-Identity ::= CHOICE { ng-5G-S-TMSI NG-5G-S-TMSI, fullI-RNTI I-RNTI-Value, ... } GroupPaging-r18 ::= SEQUENCE { inactiveReceptionAllowed-r18 ENUMERATED {true} OPTIONAL -- Need N } -- TAG-PAGING-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
3,432 | 5.5.4.8 Event B1 (Inter RAT neighbour becomes better than threshold) | The UE shall: 1> consider the entering condition for this event to be satisfied when condition B1-1, as specified below, is fulfilled; 1> consider the leaving condition for this event to be satisfied when condition B1-2, as specified below, is fulfilled. Inequality B1-1 (Entering condition) Mn + Ofn + Ocn – Hys > Thresh Inequality B1-2 (Leaving condition) Mn + Ofn + Ocn + Hys < Thresh The variables in the formula are defined as follows: Mn is the measurement result of the inter-RAT neighbour cell, not taking into account any offsets. Ofn is the measurement object specific offset of the frequency of the inter-RAT neighbour cell (i.e. eutra-Q-OffsetRange as defined within the measObjectEUTRA corresponding to the frequency of the neighbour inter-RAT cell, utra-FDD-Q-OffsetRange as defined within the measObjectUTRA-FDD corresponding to the frequency of the neighbour inter-RAT cell). Ocn is the cell specific offset of the inter-RAT neighbour cell (i.e. cellIndividualOffset as defined within the measObjectEUTRA corresponding to the neighbour inter-RAT cell, or cellIndividualOffset as defined within reportConfigInterRAT), and set to zero if not configured for the neighbour cell. Hys is the hysteresis parameter for this event (i.e. hysteresis as defined within reportConfigInterRAT for this event). Thresh is the threshold parameter for this event (i.e. b1-ThresholdEUTRA as defined within reportConfigInterRAT for this event, b1-ThresholdUTRA-FDD as defined for UTRA-FDD within reportConfigInterRAT for this event). Mn is expressed in dBm or in dB, depending on the measurement quantity of the inter-RAT neighbour cell. Ofn, Ocn, Hys are expressed in dB. Thresh is expressed in the same unit as Mn. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.5.4.8 |
3,433 | 5.8.9.1a.5.2 Additional Sidelink RLC Bearer release operation | The UE shall: 1> for groupcast and broadcast; or 1> for unicast, after receiving the RRCReconfigurationCompleteSidelink message, if the additional sidelink RLC bearer release was triggered due to the configuration received within the sl-ConfigDedicatedNR: 2> for each sl-RLC-BearerConfigIndex included in the received sl-RLC-BearerToReleaseListSizeExt in sl-ConfigDedicatedNR that is part of the current UE sidelink configuration: 3> release the RLC entity and the corresponding logical channel of the additional sidelink RLC bearer for NR sidelink communication, associated with the sl-RLC-BearerConfigIndex. 1> for unicast, if the additional sidelink RLC bearer release was triggered due to the reception of the RRCReconfigurationSidelink message: 2> for each SL-RLC-BearerConfigIndex included in received sl-RLC-BearerToReleaseList in RRCReconfigurationSidelink that is part of the current UE sidelink configuration: 3> release the RLC entity and the corresponding logical channel of the additional sidelink RLC bearer for NR sidelink communication associated with the SL-RLC-BearerConfigIndex; 1> for unicast, after receiving the RRCReconfigurationCompleteSidelink message, if the additional sidelink RLC bearer release was triggered due to the configuration received within the SIB12, SidelinkPreconfigNR or indicated by upper layers: 2> for each SL-RLC-BearerConfigIndex included in transmitted sl-RLC-BearerToReleaseList in RRCReconfigurationSidelink that is part of the current UE sidelink configuration: 3> release the RLC entity and the corresponding logical channel of the additional sidelink RLC bearer for NR sidelink communication associated with the SL-RLC-BearerConfigIndex; | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.8.9.1a.5.2 |
3,434 | 4.3.2.7a Use of established security contexts | In A/Gb mode, in the case of an established GSM security context, the GSM ciphering key shall be loaded from the SIM/USIM and taken into use by the ME when any valid CIPHERING MODE COMMAND is received during an RR connection (the definition of a valid CIPHERING MODE COMMAND message is given in 3GPP TS 44.018[ None ] [84] subclause 3.4.7.2). In A/Gb mode, in the case of an established UMTS security context, the GSM ciphering key shall be loaded from the USIM and taken into use by the MS when a valid CIPHERING MODE COMMAND is received during an RR connection (the definition of a valid CIPHERING MODE COMMAND message is given in 3GPP TS 44.018[ None ] [84] subclause 3.4.7.2) which indicates an A5 ciphering algorithm that requires a 64-bit ciphering key. The network shall derive a GSM ciphering key from the UMTS ciphering key and the UMTS integrity key by using the conversion function named "c3" defined in 3GPP TS 33.102[ 3G security; Security architecture ] [5a]. In A/Gb mode, in the case of an established UMTS security context, the UMTS ciphering key and the UMTS integrity key shall be loaded from the USIM in order for the ME to derive the GSM Kc128 (see 3GPP TS 33.102[ 3G security; Security architecture ] [5a]) and shall be taken into use by the ME when a valid CIPHERING MODE COMMAND is received during an RR connection (the definition of a valid CIPHERING MODE COMMAND message is given in 3GPP TS 44.018[ None ] [84] subclause 3.4.7.2) which indicates an A5 ciphering algorithm that requires a 128-bit ciphering key. The network shall derive a GSM Kc128 from the UMTS ciphering key and the UMTS integrity as defined in 3GPP TS 33.102[ 3G security; Security architecture ] [5a]. In Iu mode, in the case of an established GSM security context, the ME shall derive a UMTS ciphering key and a UMTS integrity key from the GSM ciphering key by using the conversion functions named "c4" and "c5" defined in 3GPP TS 33.102[ 3G security; Security architecture ] [5a]. The GSM ciphering key shall be loaded from the SIM/USIM and the derived UMTS ciphering key and UMTS integrity key shall be taken into use by the MS when a valid SECURITY MODE COMMAND indicating CS domain is received during an RR connection (the definition of a valid SECURITY MODE COMMAND message is given in 3GPP TS 25.331[ None ] [23c] and 3GPP TS 44.118[ None ] [111]). The network shall derive a UMTS ciphering key and a UMTS integrity key from the GSM ciphering key by using the conversion functions named "c4" and "c5" defined in 3GPP TS 33.102[ 3G security; Security architecture ] [5a]. In Iu mode, in the case of an established UMTS security context, the UMTS ciphering key and UMTS integrity key shall be loaded from the USIM and taken into use by the MS when a valid SECURITY MODE COMMAND indicating CS domain is received during a RR connection (the definition of a valid SECURITY MODE COMMAND message is given in 3GPP TS 25.331[ None ] [23c] and 3GPP TS 44.118[ None ] [111]). In Iu mode and A/Gb mode, if the MS received a valid SECURITY MODE COMMAND indicating CS domain in Iu mode or a valid CIPHERING MODE COMMAND in A/Gb mode before the network initiates a new Authentication procedure and establishes a new GSM/UMTS security context, the new keys are taken into use in the MS when a new valid SECURITY MODE COMMAND indicating CS domain in Iu mode, or a new valid CIPHERING MODE COMMAND in A/Gb mode, is received during the RR connection. In case of Iu mode to Iu mode handover, A/Gb mode to A/Gb mode handover, or inter-system change to A/Gb mode, the MS and the network shall continue to use the key from the old key set until a new valid SECURITY MODE COMMAND indicating CS domain in Iu mode, or a new valid CIPHERING MODE COMMAND in A/Gb mode, is received during the RR connection. In case of inter-system change to Iu mode, the MS and the network shall continue to use the keys from the old key set until the second valid SECURITY MODE COMMAND indicating CS domain is received during the RR connection. NOTE 1: If the MS received a valid SECURITY MODE COMMAND indicating CS domain in Iu mode or a valid CIPHERING MODE COMMAND in A/Gb mode before the inter-system change to Iu mode occurs, the first SECURITY MODE COMMAND message after the inter-system change, which indicates CS domain and includes only an Integrity protection mode IE, is initiated by the UTRAN without receipt of a corresponding RANAP security mode control procedure from the MSC/VLR. The only purpose of this SECURITY MODE COMMAND message is to activate the integrity protection, but not to load a new key set from the SIM/USIM (see 3GPP TS 25.331[ None ] [23c] and 3GPP TS 44.118[ None ] [111]). NOTE 2: If the MS did not receive any valid SECURITY MODE COMMAND indicating CS domain in Iu mode or any valid CIPHERING MODE COMMAND in A/Gb mode before the inter-system change to Iu mode occurs, the first SECURITY MODE COMMAND message after the inter-system change, which indicates CS domain, is initiated by the UTRAN on receipt of a RANAP security mode control procedure from the MSC/VLR. The purpose of this SECURITY MODE COMMAND message is to load a key set from the SIM/USIM and to activate either integrity protection or ciphering and integrity protection (see 3GPP TS 25.331[ None ] [23c] and 3GPP TS 44.118[ None ] [111]). | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.3.2.7a |
3,435 | 7.3.1E Minimum requirements (QPSK) for UE category 0, M1, M2 and 1bis | The throughput shall be ≥ 95% of the maximum throughput of the reference measurement channels as specified in Annexes A.2.2, A.2.3 and A.3.2 (with one sided dynamic OCNG Pattern OP.1 FDD/TDD for the DL-signal as described in Annex A.5.1.1/A.5.2.1) with parameters specified in Table 7.3.1E-1A/Table 7.3.1E-1B and Table 7.3.1E-2 for category 0, Table 7.3.1E-3/Table 7.3.1E-4 for category M1, and Table 7.3.1E-6/Table 7.3.1E-7 for category 1bis, and Table 7.3.1E-8/Table 7.3.1E-9 for category M2. Table 7.3.1E-1A: Reference sensitivity for FDD and TDD UE category 0 QPSK PREFSENS Table 7.3.1E-1B: Reference sensitivity for HD-FDD UE category 0 QPSK PREFSENS The reference receive sensitivity (REFSENS) requirement specified in Table 7.3.1E-1A/Table 7.3.1E-1B shall be met for an uplink transmission bandwidth less than or equal to that specified in Table 7.3.1E-2. Unless given by Table 7.3.1-3, the minimum requirements specified in Table 7.3.1E-1A/Table 7.3.1E-1B shall be verified with the network signalling value NS_01 (Table 6.2.4E-1) configured. NOTE: Table 7.3.1E-2 is intended for conformance tests and does not necessarily reflect the operational conditions of the network, where the number of uplink and downlink allocated resource blocks will be practically constrained by other factors. Typical receiver sensitivity performance with HARQ retransmission enabled and using a residual BLER metric relevant for e.g. Speech Services is given in the Annex G (informative). Table 7.3.1E-2: FDD and TDD UE category 0 Uplink configuration for reference sensitivity Table 7.3.1E-3: Reference sensitivity for FDD and TDD UE category M1 QPSK PREFSENS Table 7.3.1E-4: Reference sensitivity for HD-FDD UE category M1 QPSK PREFSENS The reference receive sensitivity (REFSENS) requirement specified in Table 7.3.1E-3/Table 7.3.1E-4 shall be met for an uplink transmission bandwidth less than or equal to that specified in Table 7.3.1E-5. NOTE: Table 7.3.1E-5 is intended for conformance tests and does not necessarily reflect the operational conditions of the network, where the number of uplink and downlink allocated resource blocks will be practically constrained by other factors. Typical receiver sensitivity performance with HARQ retransmission enabled and using a residual BLER metric relevant for e.g. Speech Services is given in the Annex G (informative). Table 7.3.1E-5: FDD and TDD UE category M1 Uplink configuration for reference sensitivity Table 7.3.1E-6: Reference sensitivity for FDD and TDD UE category 1bis QPSK PREFSENS Table 7.3.1E-7: FDD and TDD UE category 1bis Uplink configuration for reference sensitivity Table 7.3.1E-8: Reference sensitivity for FDD /TDD UE category M2 QPSK PREFSENS Table 7.3.1E-9: Reference sensitivity for HD-FDD category M2 QPSK PREFSENS Table 7.3.1E-10: FDD/HD-FDD and TDD UE category M2 Uplink configuration for reference sensitivity | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 7.3.1E |
3,436 | 9.9.4.1.2 TDD | The minimum performance requirement in Table 9.9.4.1.2-2 is defined as a) The ratio of the throughput obtained when transmitting based on UE reported RI and that obtained when transmitting with fixed rank 1 shall be ≥ ; b) The ratio of the throughput obtained when transmitting based on UE reported RI and that obtained when transmitting with fixed rank 2 shall be ≥ ; For the parameters specified in Table 9.9.4.1.2-1, and using the downlink physical channels specified in Annex C.3.2, the minimum requirements are specified in Table 9.9.4.1.2-2. Table 9.9.4.1.2-1: RI Test (TDD) Table 9.9.4.1.2-2: Minimum requirement (TDD) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 9.9.4.1.2 |
3,437 | 5.5.1.3 Group hopping | The sequence-group number in slot is defined by a group hopping pattern and a sequence-shift pattern according to There are 17 different hopping patterns and 30 different sequence-shift patterns. Sequence-group hopping can be enabled or disabled by means of the cell-specific parameter Group-hopping-enabled provided by higher layers. Sequence-group hopping for PUSCH can be disabled for a certain UE through the higher-layer parameter Disable-sequence-group-hopping despite being enabled on a cell basis unless the PUSCH transmission corresponds to a Random Access Response Grant or a retransmission of the same transport block as part of the contention based random access procedure. The group-hopping pattern may be different for PUSCH, (S)PUCCH and SRS and is given by where the pseudo-random sequence is defined by clause 7.2. The pseudo-random sequence generator shall be initialized with at the beginning of each radio frame where is given by clause 5.5.1.5. The sequence-shift pattern definition differs between PUCCH, PUSCH and SRS. For SPUCCH/PUCCH, the sequence-shift pattern is given by where is given by clause 5.5.1.5. For PUSCH, the sequence-shift pattern is given by , where is configured by higher layers, if no value for is provided by higher layers or if the PUSCH transmission corresponds to a Random Access Response Grant or a retransmission of the same transport block as part of the contention based random access procedure, otherwise it is given by with given by clause 5.5.1.5. For SRS, the sequence-shift pattern is given by where is given by clause 5.5.1.5. | 3GPP TS 36.211 | Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation | RAN1 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 5.5.1.3 |
3,438 | 4.7.1.7a Intersystem change from S1 mode to A/Gb mode or S1 mode to Iu mode with ISR activated | If ISR is activated and the MS returns from S1 mode to a cell belonging to a RA which is different from the RA where the MS is registered, the MS initiates a normal or combined routing area updating procedure depending on the network operation mode in the current RA. If ISR is activated and the MS returns from S1 mode to a cell belonging to the RA where the MS is registered, the following cases can be distinguished: a) Inter-system change due to PS handover: If the PS handover is to A/Gb mode, the MS initiates a normal or combined routing area updating procedure depending on the network operation mode in the current RA. b) Inter-system change not due to PS handover: 1) If the READY timer is running in the MS after the inters-ystem change occurs, then the MS shall perform a normal or combined routing area updating procedure depending on the network mode of operation in the current RA. 2) If the READY timer is not running in the MS in A/Gb mode or the MS is in PMM-IDLE mode in Iu mode after the intersystem change occurs, unless a routing area updating procedure is required according to subclause 4.7.5.1 and 4.7.5.2.1, the MS shall not perform a routing area updating procedure until uplink user data or signalling information needs to be sent from the MS to the network. - If the MS is in the same access network, (i.e. A/Gb mode or Iu mode), as when it last sent user data or signalling messages in a cell belonging to the RA where the MS is registered, the procedures defined for that access system shall be followed. This shall be sending of an LLC PDU in a A/Gb mode cell or initiating the SERVICE REQUEST procedure in an Iu mode cell. - If the MS is in a different access network (i.e. A/Gb mode or Iu mode), as when it last sent user data or signalling messages in a cell belonging to the RA where the MS is registered, the normal or combined RA update procedure shall be performed depending on the network operation mode in the current RA, before the sending of user data or signalling messages. If the signalling message is a DETACH REQUEST indicating "power off", the routing area updating procedure need not be performed. - If the periodic routing area update timer expires the MS shall initiate the periodic RA update procedure. 3) If the READY timer is not running in the network in A/Gb mode or the network is in PMM-IDLE mode in Iu mode, then the network shall page the MS if downlink user data or signalling information needs to be sent from the network to the MS. This shall include both A/Gb mode and Iu mode cells. - If the MS receives the paging indication in the same access network (i.e. A/Gb mode or Iu mode), as when it last sent user data or signalling information in a cell belonging to the RA where the MS is registered, the MS shall send any LLC PDU in a A/Gb mode cell or shall initiate the service request procedure indicating service type "paging response" in an Iu mode cell. - If the MS receives the paging indication in a different access network (i.e. A/Gb mode or Iu mode), as when it last sent user data or signalling information in a cell belonging to the RA where the MS is registered, the MS shall perform normal or combined routing area updating procedure shall be performed depending on the network operation mode in the current RA. | 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.1.7a |
3,439 | 5.2.5.8.3 Npcf_AMPolicyAuthorization_Update service operation | Service operation name: Npcf_AMPolicyAuthorization_Update Description: Provides updated information to the PCF. Inputs, Required: Identification of the application context. Inputs, Optional: Throughput requirements, service coverage requirements, policy duration, 5G access stratum time distribution indication (enable, disable), Uu time synchronization error budget, clock quality detail level, clock quality acceptance criteria. Outputs, Required: Success or Failure. Outputs, Optional: The inputs that can be accepted by the PCF. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.5.8.3 |
3,440 | 11.2.1.6 Support for CUPS across SGi | Control plane and user plane separation of PGW as PGW-C and PGW-U, has been introduced as described in 3GPP TS 23.214[ Architecture enhancements for control and user plane separation of EPC nodes ] [117]. For UE IP address from the DN AAA server in the external PDN: If the AAA server in the external PDN is reachable only via the PGW-U, the PGW-U forward all the Diameter or RADIUS messages between the DN AAA server in the external PDN and the PGW-C, according to 3GPP TS 29.244[ Interface between the Control Plane and the User Plane nodes ] [114]. For UE IP address from DHCPv4/v6 server in the external PDN: If the DHCPv4/v6 server in the external PDN is reachable only via the PGW-U, the PGW-U forward all the DHCPv4/v6 messages between the DHCPv4/v6 server in the external PDN and the PGW-C. according to 3GPP TS 29.244[ Interface between the Control Plane and the User Plane nodes ] [114]. NOTE: If the DN AAA server or the DHCPv4/v6 server in the external PDN is reachable directly, then the PGW-C communicates with it directly, without involving the PGW-U. | 3GPP TS 29.061 | Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) | CT WG3 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 11.2.1.6 |
3,441 | 8.11.1.2.1 Closed-loop spatial multiplexing performance (Cell-Specific Reference Symbols) | 8.11.1.2.1.1 Minimum Requirement Single-Layer Spatial Multiplexing 2 Tx Antenna Port The requirements are specified in Table 8.11.1.2.1.1-2, with the addition of the parameters in Table 8.11.1.2.1.1-1 and the downlink physical channel setup according to Annex C.3.2. The purpose of these tests is to verify the closed loop rank-one performance with frequency selective precoding. Table 8.11.1.2.1.1-1: Test Parameters for Single-Layer Spatial Multiplexing (FRC) Table 8.11.1.2.1.1-2: Minimum performance Single-Layer Spatial Multiplexing (FRC) 8.11.1.2.1.2 Minimum Requirement Single-Layer Spatial Multiplexing 2 Tx Antenna Port with CRS assistance information The requirements are specified in Table 8.11.1.2.1.2-2, with the addition of parameters in Table 8.11.1.2.1.2-1. In Table 8.11.1.2.1.2-1, 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 closed loop single-layer spatial multiplexing TM6 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.1.2.1.2-1: Test Parameters Table 8.11.1.2.1.2-2: Minimum performance for PDSCH 8.11.1.2.1.3 Minimum Requirement Single-Layer Spatial Multiplexing 4 Tx Antenna Port with CRS assistance information The requirements are specified in Table 8.11.1.2.1.3-2, with the addition of parameters in Table 8.11.1.2.1.3-1. In Table 8.11.1.2.1.3-1, 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 closed loop single-layer spatial multiplexing TM6 performance under assumption that UE applies CRS interference mitigation in the scenario with 4 CRS antenna ports in the serving and aggressor cells. Table 8.11.1.2.1.3-1: Test Parameters Table 8.11.1.2.1.3-2: Minimum performance for PDSCH | 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.1.2.1 |
3,442 | 5.7.3 Physical sidelink channels and signals | Physical Sidelink Control Channel (PSCCH) indicates resource and other transmission parameters used by a UE for PSSCH. PSCCH transmission is associated with a DM-RS. Physical Sidelink Shared Channel (PSSCH) transmits the TBs of data themselves, and control information for HARQ procedures and CSI feedback triggers, etc. At least 6 OFDM symbols within a slot are used for PSSCH transmission. PSSCH transmission is associated with a DM-RS and may be associated with a PT-RS. Physical Sidelink Feedback Channel (PSFCH) carries HARQ feedback over the sidelink from a UE which is an intended recipient of a PSSCH transmission to the UE which performed the transmission. PSFCH sequence is transmitted in one PRB repeated over two OFDM symbols near the end of the sidelink resource in a slot. The Sidelink synchronization signal consists of sidelink primary and sidelink secondary synchronization signals (S-PSS, S-SSS), each occupying 2 symbols and 127 subcarriers. Physical Sidelink Broadcast Channel (PSBCH) occupies 9 and 7 symbols for normal and extended CP cases respectively, including the associated DM-RS. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.7.3 |
3,443 | 5.3.5.5.2 Reconfiguration with sync | The UE shall perform the following actions to execute a reconfiguration with sync. 1> if the AS security is not activated, perform the actions upon going to RRC_IDLE as specified in 5.3.11 with the release cause 'other' upon which the procedure ends; 1> stop timer T430 if running; 1> if no DAPS bearer is configured: 2> stop timer T310 for the corresponding SpCell, if running; 1> if this procedure is executed for the MCG: 2> if timer T316 is running; 3> stop timer T316; 3> if the UE supports RLF-Report for fast MCG recovery procedure: 4> set the elapsedTimeT316 in the VarRLF-Report to the value of the elapsed time of the timer T316; 4> set the pSCellId to the global cell identity of the PSCell, if available, otherwise to the physical cell identity and carrier frequency of the PSCell; 3> else: 4> clear the information included in VarRLF-Report, if any; 2> resume MCG transmission, if suspended. 1> stop timer T312 for the corresponding SpCell, if running; 1> if sl-PathSwitchConfig is included: 2> consider the target L2 U2N Relay UE to be the one indicated by the targetRelayUE-Identity in the sl-PathSwitchConfig; 2> start timer T420 for the corresponding target L2 U2N Relay UE with the timer value set to t420, as included in the sl-PathSwitchConfig; 2> apply the value of the newUE-Identity as the C-RNTI; 2> indicate to upper layer (to trigger the PC5 unicast link establishment) with the target L2 U2N Relay UE indicated by the targetRelayUE-Identity; 2> apply the default configuration of SL-RLC1 as defined in 9.2.4 for SRB1; 1> else (sl-PathSwitchConfig is not included): 2> if this procedure is executed for the MCG or if this procedure is executed for an SCG not indicated as deactivated in the E-UTRA or NR RRC message in which the RRCReconfiguration message is embedded: 3> start timer T304 for the corresponding SpCell with the timer value set to t304, as included in the reconfigurationWithSync; 2> if the frequencyInfoDL is included: 3> consider the target SpCell to be one on the SSB frequency indicated by the frequencyInfoDL with a physical cell identity indicated by the physCellId; 2> else: 3> consider the target SpCell to be one on the SSB frequency of the source SpCell with a physical cell identity indicated by the physCellId; 2> start synchronising to the DL of the target SpCell; 2> apply the specified BCCH configuration defined in 9.1.1.1 for the target SpCell; 2> acquire the MIB of the target SpCell, which is scheduled as specified in TS 38.213[ NR; Physical layer procedures for control ] [13]; 2> if NTN-Config is configured for the target cell: 3> start timer T430 with the timer value set to ntn-UlSyncValidityDuration from the subframe indicated by epochTime, according to the target cell NTN-Config; NOTE 1: The UE should perform the reconfiguration with sync as soon as possible following the reception of the RRC message triggering the reconfiguration with sync, which could be before confirming successful reception (HARQ and ARQ) of this message. NOTE 2: The UE may omit reading the MIB if the UE already has the required timing information, or the timing information is not needed for random access. NOTE 2a: A UE with DAPS bearer does not monitor for system information updates in the source PCell. 2> If any DAPS bearer is configured: 3> create a MAC entity for the target cell group with the same configuration as the MAC entity for the source cell group; 3> for each DAPS bearer: 4> establish an RLC entity or entities for the target cell group, with the same configurations as for the source cell group; 4> establish the logical channel for the target cell group, with the same configurations as for the source cell group; NOTE 2b: In order to understand if a DAPS bearer is configured, the UE needs to check the presence of the field daps-Config within the RadioBearerConfig IE received in radioBearerConfig or radioBearerConfig2. 3> for each SRB: 4> establish an RLC entity for the target cell group, with the same configurations as for the source cell group; 4> establish the logical channel for the target cell group, with the same configurations as for the source cell group; 3> suspend SRBs for the source cell group; NOTE 3: Void 3> apply the value of the newUE-Identity as the C-RNTI in the target cell group; 3> configure lower layers for the target SpCell in accordance with the received spCellConfigCommon; 3> configure lower layers for the target SpCell in accordance with any additional fields, not covered in the previous, if included in the received reconfigurationWithSync. 2> else: 3> reset the MAC entity of this cell group; 3> consider the SCell(s) of this cell group, if configured, that are not included in the SCellToAddModList in the RRCReconfiguration message, to be in deactivated state; 3> apply the value of the newUE-Identity as the C-RNTI for this cell group; 3> configure lower layers in accordance with the received spCellConfigCommon; 3> if rach-LessHO is included: 4> configure lower layers in accordance with rach-LessHO for the target SpCell; 3> configure lower layers in accordance with any additional fields, not covered in the previous, if included in the received reconfigurationWithSync. 2> if the UE is acting as L2 U2N Remote UE at the source side: 3> indicate upper layer to trigger PC5 unicast link release. Upon L2 U2N Relay UE receiving reconfigurationWithSync, it either indicates to upper layers (to trigger PC5 unicast link release) or sends NotificationMessageSidelink message to the connected L2 U2N Remote UE(s) in accordance with 5.8.9.10. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.5.5.2 |
3,444 | 20.4.5 Abort-Session-Request Command | The Abort-Session-Request (ASR) command, defined in IETF RFC 6733 (DIAMETER BASE) [111], is indicated by the Command-Code set to 274 and the message flags’ ‘R’ bit set, is sent by the BM-SC to the MBMS GW to request that the session identified by the Session-Id be stopped. The relevant AVPs that are of use for the SGmb interface are detailed in the ABNF description below. Other valid AVPs for this command are not used for SGmb purposes and should be ignored by the receiver or processed according to the relevant specifications. Message Format <ASR> ::= < Diameter Header: 274, REQ, PXY > < Session-Id > { Origin-Host } { Origin-Realm } { Destination-Realm } { Destination-Host } { Auth-Application-Id } [ Origin-State-Id ] * [ Proxy-Info ] * [ Route-Record ] [ Restart-Counter ] | 3GPP TS 29.061 | Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) | CT WG3 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 20.4.5 |
3,445 | 16.10.5.2 Configuration | A UE can be configured to receive data of MBS multicast session only in RRC_CONNECTED state or RRC_INACTIVE state. To receive the multicast service, the UE needs to perform MBS Session Join procedure as specified in TS 23.247[ Architectural enhancements for 5G multicast-broadcast services ] [45]. It is up to gNB to decide whether the UE receives data of MBS multicast session in RRC_CONNECTED state or RRC_ INACTIVE state. The gNB moves the UE from RRC_CONNECTED state to RRC_INACTIVE state via RRCRelease message, and moves the UE from RRC_INACTIVE state to RRC_CONNECTED state via group notification or UE-specific paging. If the UE which joined a multicast session is in RRC_CONNECTED state and when the multicast session is activated, the gNB may send RRCReconfiguration message with relevant MBS configuration for the multicast session to the UE. If the gNB configures the UE to receive the MBS multicast session in RRC_INACTIVE state, the gNB may provide the PTM configuration via RRCRelease message for the MBS multicast session as well as information which multicast service(s) can be continued to be received in RRC_INACTIVE state. The UE does not suspend MRBs of the multicast session indicated to be continued to be received in RRC_INACTIVE state. Multicast MCCH is used in case a cell supports updating PTM configuration or providing PTM configuration to UEs in RRC_INACTIVE state moved from other cells. Otherwise, multicast MCCH can be optionally present. A notification mechanism is used to announce the change of the multicast MCCH contents due to multicast session modification or session deactivation or due to neighbouring cell information modification. The scheduling information for multicast MCCH reception is provided via SIB24 and optionally via RRCRelease message. When there is temporarily no data to be sent to the UEs for a multicast session that is active, the gNB may move the UE to RRC_INACTIVE state. When an MBS multicast session is deactivated, the gNB may move the UE in RRC_CONNECTED state to RRC_IDLE or RRC_INACTIVE state. For UEs receiving data of MBS multicast session in RRC_INACTIVE state, the gNB notifies the UE to stop monitoring PDCCH addressed by corresponding G-RNTI via RRCRelease message or multicast MCCH when there is temporarily no data to be sent or when the session is deactivated. gNBs supporting MBS use a group notification mechanism to notify the UEs in RRC_IDLE or RRC_INACTIVE state when a multicast session has been activated by the CN. gNBs supporting MBS use a group notification mechanism to notify the UEs in RRC_INACTIVE state when the session is already activated and the gNB has multicast session data to deliver. If the UE receiving data of MBS multicast session in RRC_INACTIVE state in a cell is notified to stop monitoring PDCCH addressed by G-RNTI for all the joined multicast sessions, the UE does not monitor PDCCH addressed by multicast-MCCH-RNTI until the group notification is received. Upon reception of the group notification, the UEs reconnect to the network or resume the connection and transition to RRC_CONNECTED state from either RRC_IDLE state or RRC_INACTIVE state. Upon reception of the group notification that indicates to allow the multicast reception in RRC_INACTIVE state, the UE stays in RRC_INACTIVE state and behaves as specified in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [12]. If the UE is notified by both group notification and the UE-specific paging, the UE follows the UE-specific paging and goes to RRC_CONNECTED state. The group notification is addressed with P-RNTI on PDCCH, and the paging channels are monitored by the UE as described in clause 9.2.5. Paging message for group notification contains MBS session ID which is utilized to page all UEs in RRC_IDLE and RRC_INACTIVE states that joined the associated MBS multicast session, i.e., UEs are not paged individually. The UE stops monitoring for group notifications related to a specific multicast session, i.e., stops checking for the MBS session ID in the Paging message, when the UE enters RRC_CONNECTED state. The UE does not monitor for group notifications for these cases, i.e., once this UE leaves this multicast session or the network requests the UE to leave, or the network releases the multicast session. NOTE: The gNB's decision to keep a UE in RRC_CONNECTED (e.g., to meet latency requirements for mission critical service) or move the UE to RRC_INACTIVE or RRC_IDLE (e.g., when there is temporarily no data to be sent to the UE or to address congestion in the cell) may consider 5QI value(s) or other QoS parameters for mission critical and non-mission critical UEs. If the UE in RRC_IDLE state that joined an MBS multicast session is camping on the gNB not supporting MBS, the UE may be notified by CN-initiated paging where CN pages each UE individually due to session activation or data availability, as described in clause 9.2.5. If the UE in RRC_INACTIVE state that joined MBS multicast session is camping on the gNB not supporting MBS, the UE may be notified individually by RAN-initiated paging due to session activation or data availability, as described in clause 9.2.5. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.10.5.2 |
3,446 | 5.5.2.3 Measurement identity addition/modification | The network applies the procedure as follows: - configure a measId only if the corresponding measurement object, the corresponding reporting configuration and the corresponding quantity configuration, are configured. The UE shall: 1> for each measId included in the received measIdToAddModList: 2> if an entry with the matching measId exists in the measIdList within the VarMeasConfig: 3> replace the entry with the value received for this measId; 2> else: 3> add a new entry for this measId to 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; NOTE 1: If the measId associated with reportConfig for conditional reconfiguration is modified, the conditions are considered to be not fulfilled as specified in 5.3.5.13.4. 2> if the reportType is set to reportCGI in the reportConfig associated with this measId: 3> if the measObject associated with this measId concerns E-UTRA: 4> if the useAutonomousGaps is included in the reportConfig associated with this measId: 5> start timer T321 with the timer value set to 200 ms for this measId; 4> else: 5> start timer T321 with the timer value set to 1 second for this measId; 3> if the measObject associated with this measId concerns NR: 4> if the measObject associated with this measId concerns FR1: 5> if the useAutonomousGaps is included in the reportConfig associated with this measId: 6> if the UE is an (e)RedCap UE with 1 Rx branch 7> start timer T321 with the timer value set to 3 seconds for this measId; 6> else 7> start timer T321 with the timer value set to 2 seconds for this measId; 5> else: 6> start timer T321 with the timer value set to 2 seconds for this measId; 4> if the measObject associated with this measId concerns FR2: 5> if the useAutonomousGaps is included in the reportConfig associated with this measId: 6> if the UE is a RedCap UE with 1 Rx branch 7> start timer T321 with the timer value set to 6 seconds for this measId; 6> else 7> start timer T321 with the timer value set to 5 seconds for this measId; 5> else: 6> start timer T321 with the timer value set to 16 seconds for this measId. 2> if the reportType is set to reportSFTD in the reportConfigNR associated with this measId and the drx-SFTD-NeighMeas is included: 3> if the measObject associated with this measId concerns FR1: 4> start timer T322 with the timer value set to 3 seconds for this measId; 3> if the measObject associated with this measId concerns FR2: 4> start timer T322 with the timer value set to 24 seconds for this measId. 2> if the reportType is set to reportOnActivation in the reportConfig associated with this measId: 3> indicate to lower layer to enable the measurement reporting for fast unknown SCell activation. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.5.2.3 |
3,447 | 9.10 Timing | Transmission of a sidelink radio frame number from the UE shall start seconds before the start of the corresponding timing reference frame at the UE. The UE is not required to receive sidelink or downlink transmissions earlier than after the end of a sidelink transmission. For PSDCH transmission and sidelink synchronization signal transmission for PSDCH: if the UE has a serving cell fulfilling the S criterion according to [10, clause 5.2.3.2] - the timing of reference radio frame equals that of downlink radio frame of the cell c as given in Clause 14.3.1 of [4] and - is given by clause 8.1, otherwise - the timing of reference radio frame is implicitly obtained from [4] and - . For all other sidelink transmissions: if the UE has a serving cell fulfilling the S criterion according to [10, clause 5.2.3.2] - the timing of reference radio frame equals that of downlink radio frame in the cell with the same uplink carrier frequency as the sidelink and - is given by clause 8.1, otherwise - the timing of reference radio frame is implicitly obtained from [4] and - . Figure 9.9-1: Sidelink timing relation. The quantity differs between channels and signals according to | 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 | 9.10 |
3,448 | 5.32.5.6 Suspend and Resume Traffic Duplication | As part of the Redundant Steering Mode, a UPF can decide to suspend traffic duplication for a UE by sending PMF- Suspend Duplication Request message to the UE. How the UPF determines to suspend traffic duplication is implementation specific. NOTE 1: The Suspension of traffic duplication can be caused by e.g. the locally detected UPF congestion. In that way the UPF can stop receiving duplicated traffic via 3GPP and non-3GPP access network simultaneously. The UPF may indicate in the PMF-Suspend Duplication Request message the type of traffic (i.e. GBR or non-GBR) for which traffic duplication is being suspended. The PMF-Suspend Duplication Request message is sent over the user plane of any available access network of the MA PDU Session. Once the UE receives the PMF-Suspend Duplication Request message from the UPF, the UE shall stop duplicating the type of traffic for which traffic duplication is suspended. If the UPF does not provide the type of traffic (GBR or non-GBR) in the PMF-Suspend Duplication Request message, traffic duplication is suspended for all traffic for which traffic duplication is being performed. Once UPF suspended traffic duplication and if no Primary Access is configured, both the UE and the UPF decide, based on their own implementation, which access network to use for sending UL and DL traffic. If the Primary Access is configured, both the UE and the UPF use the Primary Access for sending UL and DL traffic. The UPF may decide to resume traffic duplication for a UE by sending the PMF-Resume Duplication Request message. How the UPF determines to resume traffic duplication is implementation specific. NOTE 2: Traffic duplication can be resumed e.g. when the UPF has detected that local congestion has diminished. Once the UE receives the PMF-Resume Duplication Request message from the UPF, the UE may restart to duplicate the type of traffic for which traffic duplication is resumed based on the provided Redundant steering mode policies and UE implementation. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.32.5.6 |
3,449 | 5.7.4 UE Assistance Information 5.7.4.1 General | Figure 5.7.4.1-1: UE Assistance Information The purpose of this procedure is for the UE to inform the network of: - its delay budget report carrying desired increment/decrement in the connected mode DRX cycle length, or; - its overheating assistance information, or; - its IDC assistance information, or; - its preference on DRX parameters for power saving, or; - its preference on the maximum aggregated bandwidth for power saving, or; - its preference on the maximum number of secondary component carriers for power saving, or; - its preference on the maximum number of MIMO layers for power saving, or; - its preference on the minimum scheduling offset for cross-slot scheduling for power saving, or; - its preference on the RRC state, or; - configured grant assistance information for NR sidelink communication, or; - its preference in being provisioned with reference time information, or; - its preference for FR2 UL gap, or; - its preference to transition out of RRC_CONNECTED state for MUSIM operation, or; - its preference on the MUSIM gaps, or; - its preference on the MUSIM gap priority, or; - its preference on the MUSIM temporary capability restriction, or; - its relaxation state for RLM measurements, or; - its relaxation state for BFD measurements, or; - availability of data and/or signalling mapped to radio bearers which are not configured for SDT, or; - its preference for the SCG to be deactivated, or; - availability of uplink data to transmit for a DRB for which there is no MCG RLC bearer while the SCG is deactivated, or; - change of its fulfilment status for RRM measurement relaxation criterion, or; - service link (specified in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [2]) propagation delay difference between serving cell and neighbour cell(s); or - its preference on multi-Rx operation for FR2; or - availability of flight path information for Aerial UE operation; or - UL traffic information, or; - the information of the relay UE(s) with which it connects via a non-3GPP connection for MP, or; - configured grant assistance information for NR sidelink positioning. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.7.4 |
3,450 | 5.5.2.1 E-UTRAN to UTRAN Iu mode Inter RAT handover 5.5.2.1.1 General | Pre-conditions: - The UE is in ECM-CONNECTED state (E-UTRAN mode). If emergency bearer services are ongoing for an UE, handover to the target RNC is performed independent of the Handover Restriction List. The SGSN checks, as part of the Routing Area Update in the execution phase, if the handover is to a restricted area and if so SGSN deactivate the non-emergency PDP context as specified in TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [7], clause 9.2.4.2. If emergency bearer services are ongoing for the UE, the source MME evaluates the handover to the target CSG cell independent of the UE's CSG subscription. If the handover is to a CSG cell that the UE is not subscribed, the target RNC will only accept the emergency bearers and the target SGSN deactivates the non-emergency PDP contexts that were not accepted by the target RNC as specified in TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [7], clause 9.2.4.2. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.5.2.1 |
3,451 | 4.13.7 Tracking Area handling | For Cellular IoT over satellite access with moving cells, in order to ensure that each TA is Earth-stationary, even if the radio cells are moving across the Earth's surface, the E-UTRAN may change the TAC values that are broadcast in a cell's system information as the cell moves, as described in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [37]. E-UTRAN may broadcast in a cell a single TAC per PLMN and change this TAC value as the cell moves. Alternatively, the E-UTRAN may broadcast in a cell more than one TAC for a PLMN and add or remove TAC values as the cell moves. The eNodeB provides either the single broadcast TAI or all broadcast TAIs corresponding to the Selected PLMN as described in TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [36] to the MME as part of the ULI, whenever the TAI is included in the S1-AP message as described in TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [36]. The eNodeB indicates, if known, also the TAI where the UE is geographically located. NOTE: The MME can take into account the TAI where the UE is geographically located, and the last visited TAI to generate a suitable Tracking Area List for the UE. The MME considers the UE to be in a forbidden area if the only TAI or all TAIs received from the eNodeB are forbidden based on subscription data. The UE considers it is in a cell within a forbidden area if the only TAI or all TAIs broadcast in this cell for the selected PLMN are forbidden. In a PLMN, the UE considers it is not in a cell within a forbidden area if at least one broadcast TAI for this PLMN in this cell is not forbidden. If the MME receives multiple TAIs from E-UTRAN and determines that some, but not all, TAIs in the received list of TAIs are forbidden by subscription or by operator policy, the MME shall send the forbidden TAI(s) to UE as described in clause 5.3.2, 5.3.3 and 5.3.4. The UE stores the TAI(s) in the appropriate Forbidden Area list and removes the TAI(s) from the TAI list. | 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.7 |
3,452 | 5.29.3 PDU Session management | Session management as defined for 5GS in clause 5.6 is applicable to 5G-VN-type services with the following clarification and enhancement: - A UE gets access to 5G LAN-type services via a PDU Session of IP PDU Session type or Ethernet PDU Session type. - A PDU Session provides access to one and only one 5G VN group. The PDU Sessions accessing to a certain 5G VN group should all anchor at the same network, i.e. the common home network of 5G VN group members. - A DNN and S-NSSAI is associated with a 5G VN group. - A dedicated SMF, a dedicated SMF Set or multiple SMF (Sets) can be responsible for all the PDU Sessions for communication of a certain 5G VN group. Multiple SMF (Sets) may apply for a 5G VN group extended over a large area, bigger than the service area of any SMF Set serving the DNN/S-NSSAI of the 5G VN group. SMF selection is described in clause 6.3.2. NOTE 1: If a dedicated SMF (Set) is used to serve a 5G VN, the network is configured so that the same SMF (Set) is always selected for a certain 5G VN group, e.g. only one SMF, or SMFs in one SMF Set, registers on the NRF with the DNN/S-NSSAI used for a given 5G VN group. NOTE 2: Having a dedicated SMF serving a 5G VN does not contradict that redundancy solutions can be used to achieve high availability. If SMF Set(s) serve the 5G VN group, high availability is achieved by the set functionality. - In the case that more than one SMF sets or SMF instances in a SMF Set are responsible for all the PDU Sessions for communication of a certain 5G VN group to enable SMF redundancy for reliability of the 5G VN group communication: - The associations between one or more SMF Sets and the DNN, S-NSSAI of the associated 5G VN group is registered and discovered in NRF. - The SMFs that registered to associate with the DNN, S-NSSAI of the 5G VN group should be available in the LADN service area of the 5G VN group. - The UE provides the DNN and S-NSSAI associated with the 5G VN group to access the 5G LAN-type services for that 5G VN, using the PDU Session Establishment procedure described in clause 4.3.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. - During establishment of the PDU Session, secondary authentication as described in clause 5.6.6 and in clause 4.3.2.3 of TS 23.502[ Procedures for the 5G System (5GS) ] [3], may be performed in order to authenticate and authorize the UE for accessing the DNN and S-NSSAI associated with the 5G VN group. Authentication and authorization for a DNN and S-NSSAI using secondary authentication implies authentication and authorization for the associated 5G VN group. There is no 5G VN group specific authentication or authorization defined. - The SM level subscription data for a DNN and S-NSSAI available in UDM, as described in clause 5.6.1, applies to the DNN and S-NSSAI associated to a 5G VN group. - Session management related policy control for a DNN and S-NSSAI as described in TS 23.502[ Procedures for the 5G System (5GS) ] [3], is applicable to the DNN and S-NSSAI associated to a 5G VN group. This includes also usage of URSP, for the UE to determine how to route outgoing traffic to a PDU Session for the DNN and S-NSSAI associated to a 5G VN group. - Session and service continuity SSC mode 1, SSC mode 2, and SSC mode 3 as described in clause 5.6.9 are applicable to N6-based traffic forwarding of 5G VN communication within the associated 5G VN group. - A PDU Session provides unicast, broadcast and multicast communication for the DNN and S-NSSAI associated to a 5G VN group. The PSA UPF determines whether the communication is for unicast, broadcast or multicast based on the destination address of the received data, and performs unicast, broadcast or multicast communication handling. - During the PDU Session Establishment procedure, the SMF retrieves SM subscription data related to 5G-VN type service from the UDM as part of the UE subscription data for the DNN and S-NSSAI. - In order to realize N19 traffic routing in the case that a single SMF (or single SMF Set) is serving the 5G VN, the SMF (or SMF Set) correlates PDU sessions established to the same 5G VN group and uses this to configure the UPF with the group level N4-session including packet detection and forwarding rules for N19 tunnelling forwarding. NOTE 3: In the case of a SMF Set serving a 5G VN, implementation dependent mechanism can be used between SMF(s) that are part of a SMF Set to control the N19 configuration. - In order to realize N6/N19 traffic routing between PSA UPFs in case multiple SMF Sets are serving the 5G VN, traffic forwarding between UPFs belonging to different SMF (Set)s can be realized via User Plane tunnels that are configured using OAM between UPFs served by different SMF (Set)s. How to implement the user plane tunnels and traffic forwarding configured between these UPFs is up to network implementation and deployment and is out of scope of this specification. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.29.3 |
3,453 | 7.2 Diversity characteristics | The requirements in Section 7 assume that the receiver is equipped with two Rx port as a baseline. These requirements apply to all UE categories unless stated otherwise. Additional requirements apply for UE(s) equipped with four Rx ports. These additional requirements also apply for supported band combinations for which the UE can operate using up to four Rx ports while configured with carrier aggregation. With the exception of subclause 7.9 all requirements shall be verified by using both (all) antenna ports simultaneously. NOTE: for an operating band in which the UE can operate using up to four Rx ports, it suffices to verify for conformance the additional requirements applicable for four Rx ports [except for REFSENS]. NOTE: Implementation of 4 antenna ports for all operating bands supported by the UE is not mandated. For a category 0, a category [M 1] , category 1bis, category NB1 and NB2 UE the requirements in Section 7 assume that the receiver is equipped with single Rx port. | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 7.2 |
3,454 | 4.13.2.3 Number of attempted WLAN releases from the LWA WLAN mobility set | a) This measurement provides the number of attempted WLAN releases from the LWA WLAN mobility set. b) CC c) On transmission of RRCConnectionReconfiguration message which includes the wlan-ToReleaseList in the lwa-MobilityConfig of lwa-Configuration information element (see TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [18]) by the eNB. d) An integer value e) LWI.LwaWlanRelAtt f) WLANMobilitySet g) Valid for packet switched traffic h) EPS | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.13.2.3 |
3,455 | 4.3.4.1 IMSI detach initiation by the mobile station | The IMSI detach procedure consists only of the IMSI DETACH INDICATION message sent from the mobile station to the network. The mobile station then starts timer T3220 and enters the MM sublayer state IMSI DETACH INITIATED. If no RR connection exists, the MM sublayer within the mobile station will request the RR sublayer to establish a RR connection. If establishment of the RR connection is not possible because a suitable cell is not (or not yet) available then, the mobile station shall try for a period of at least 5 seconds and for not more than a period of 20 seconds to find a suitable cell. If a suitable cell is found during this time then, the mobile station shall request the RR sublayer to establish an RR connection, otherwise the IMSI detach is aborted. For: - a shared GERAN in A/Gb mode, if the MS is a GERAN network sharing supporting MS, the chosen PLMN identity shall be indicated to the GERAN in the IMSI DETACH INDICATION message using the Skip Indicator IE as specified in subclause 10.3.1 and; - a shared UTRAN, the chosen PLMN identity shall be indicated to the UTRAN in the RRC INITIAL DIRECT TRANSFER message (see 3GPP TS 25.331[ None ] [23c]). If a RR connection exists, the MM sublayer will release locally any ongoing MM connections before the IMSI DETACH INDICATION message is sent. The IMSI detach procedure may not be started if a MM specific procedure is active. If possible, the IMSI detach procedure is then delayed until the MM specific procedure is finished, else the IMSI detach is omitted. | 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.1 |
3,456 | – BWP | The IE BWP is used to configure generic parameters of a bandwidth part as defined in TS 38.211[ NR; Physical channels and modulation ] [16], clause 4.5, and TS 38.213[ NR; Physical layer procedures for control ] [13], clause 12. For each serving cell the network configures at least an initial downlink bandwidth part and one (if the serving cell is configured with an uplink) or two (if using supplementary uplink (SUL)) initial uplink bandwidth parts. Furthermore, the network may configure additional uplink and downlink bandwidth parts for a serving cell. The uplink and downlink bandwidth part configurations are divided into common and dedicated parameters. BWP information element -- ASN1START -- TAG-BWP-START BWP ::= SEQUENCE { locationAndBandwidth INTEGER (0..37949), subcarrierSpacing SubcarrierSpacing, cyclicPrefix ENUMERATED { extended } OPTIONAL -- Need R } -- TAG-BWP-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
3,457 | 8.3.2.5 Performance Requirements for semiOpenLoop transmission | The requirements are specified in Table 8.3.2.5-2, with the addition of the parameters in Table 8.3.2.5-1 and the downlink physical channel setup according to Annex C.3.2. The purpose of these tests is to verify rank one and rank two performances for full RB allocation upon antenna ports 7 and 8 with higher layer parameter semiOpenLoop is configured. Table 8.3.2.5-1: Test Parameters for Testing CDM-multiplexed DM RS (dual layer) when high layer parameter semiOpenLoop is configured Table 8.3.2.5-2: Minimum Performance Requirements for CDM-multiplexed DM RS (FRC) when high layer parameter semiOpenLoop is configured | 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.5 |
3,458 | 4.8.2 Connection Resume procedure 4.8.2.1 General | The Connection Resume procedure is used by a UE to request the establishment of a secure connection between a UE and the network when the UE is in CM-CONNECTED with RRC_INACTIVE state, or in CM-IDLE with Suspend indicator for the UE supporting User Plane CIoT 5GS Optimisation. The UE initiates the procedure when upper layers or the AS (when responding to RAN paging or upon triggering RNA updates) requests the resumption of a suspended RRC connection. NG-RAN details are specified in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [9] and TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [12] for NR and in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [46] and TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [16] for E-UTRA. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.8.2 |
3,459 | 6.2.2G UE maximum output power for V2X Communication | When UE is configured for E-UTRA V2X sidelink transmissions non-concurrent with E-UTRA uplink transmissions for E-UTRA V2X operating bands specified in Table 5.5G-1, the allowed V2X UE maximum output power for shall be as applied in Table 6.2.2-1 in subclause 6.2.2. For V2X UE is configured for simultaneous E-UTRA V2X sidelink and E-UTRA uplink transmissions for inter-band E-UTRA V2X / E-UTRA bands specified in Table 5.5G-2, the UE maximum output power shall be as specified in Table 6.2.2G-1 in subclause 6.2.2G for the corresponding inter-band con-current operation with uplink assigned to two bands. Table 6.2.2G-1: Inter-band con-current V2X UE Power Class (two bands) For intra-band contiguous multi-carrier operation, the maximum output power is defined in Table 6.2.2G-2. Table 6.2.2G-2: V2X UE Power Class for intra-band contiguous multi-carrier operation When a UE is configured for E-UTRA V2X sidelink transmissions in Band 47, the UE shall meet the following additional requirements for transmission within the frequency ranges 5855-5925 MHz: - The maximum mean power spectral density shall be restricted to 23 dBm/MHz EIRP when the network signaling value NS_33 or NS_34 is indicated. where the network signaling values are specified in clause 6.2.4G. NOTE: The PSD limit in EIRP shall be converted to conducted requirement depend on the supported post antenna connector gain Gpost connector declared by the UE following the principle described in annex I. For V2X UE supporting Transmit Diversity, if the UE transmits on two connectors at the same time, the maximum output power for any transmission bandwidth within the channel bandwidth is specified in Table 6.2.2G-3. The maximum output power is measured as the sum of the maximum output power at each UE antenna connector. The period of measurement shall be at least one sub frame (1ms). Table 6.2.2G-3: V2X UE Power Class for Transmit Diversity scheme If the UE transmits on one antenna connector at a time, the requirements in Table 6.2.2-1 shall apply to the active antenna connector. | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.2.2G |
3,460 | 19.2.1.1 Service Provided by the BM-SC in Home PLMN | A visited PLMN may offer to roaming users MBMS user services from their home PLMN. For this case, the PDP connection, which will be used for the JOIN step, may be from the UE to the visited GGSN due to operator policy or routing optimization. Then the authorization is done in the BM-SC in visited PLMN with the authorization information retrieved from the BM-SC in home PLMN. Whether GGSN of home or visited PLMN would be used is based on the operator policy, or agreement between PLMNs. The MBMS user traffic is provided by the BM-SC in home PLMN and proxyed. Figure 28: Activation of an MBMS multicast service in roaming scenario with service provided in the home PLMN 1. The GGSN sends an AAR to the BM-SC in visited PLMN seeking authorizationt for the activating roaming UE to receive data from a particular service. 2. The BM-SC in visited PLMN finds the BM-SC in home PLMN which will serve the roaming UE based on the multicast IP address, and identity of the user, and sends the AAR to it for the roaming UE to receive data from a particular service. 3. The authorization decision is provided from BM-SC in home PLMN in the AAA to BM-SC in visited PLMN. An APN may be included in the signalling between BM-SCs, which indicates a GGSN in home PLMN which will serve the UE for the specific MBMS service. The BM-SC in the visit network may modify the APN based on the operator policy or agreement between PLMNs. 4. The authorization decision, as received from BM-SC in home PLMN, is provided in the AAA to GGSN together with the APN to be used for creation of the MBMS UE Context If the AAA indicates that the roaming UE is not authorized to receive the MBMS data the process terminates with no additional message exchange. Whether GGSN of home or visited PLMN would be used is based on the operator policy, or agreement between PLMNs, for example, the visited BM-SC may modify the APN from the home BM-SC according to configuration of operator policy. 5. The GGSN sends an AAR seeking authorization for the activating UE to BM-SC in home PLMN. This GGSN may be different from the GGSN that receives IGMP join message. 6. The authorization decision is provided in the AAA to GGSN. | 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 | 19.2.1.1 |
3,461 | 4.3.2a Support for Dual Connectivity | Dual Connectivity involves two RAN nodes, i.e. Master and Secondary RAN nodes (see TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [5] for the definitions), in providing radio resources to a given UE (with active radio bearers), while a single S1-MME termination point exists for an UE between a MME and the E-UTRAN. The E-UTRAN architecture and related functions to support Dual Connectivity with E-UTRAN is further described in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [5]. Dual Connectivity with E-UTRAN as Master RAN node and NR as Secondary RAN node is further described in TS 37.340[ Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Overall Description; Stage-2 ] [85]. Dual connectivity defines "Master Cell Group (MCG) bearer" and "Secondary Cell Group (SCG) bearer" alternatives (see TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [5]). For E-RABs configured as "MCG bearers" the U-plane termination points are maintained, whereas for E-RABs configured as "SCG bearers" it enables changing the U-plane termination point in the E-UTRAN by means of S1-MME signalling without changing the S1-MME termination point. Dual Connectivity also defines a "split bearer" alternative TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [5]. The "split bearer" in the E-UTRAN is transparent to the core network entities (e.g. MME, S-GW etc.) with the exception of the CSG membership verification by the MME when the Secondary eNodeB is a hybrid access eNodeB. The E-UTRAN uses the per-UE information supplied by the MME and local E-UTRAN configuration data to determine whether or not to use Dual Connectivity for that UE, and, on a per EPS bearer basis the E-UTRAN decides whether to use an MCG bearer or SCG bearer, and, whether or not that bearer is a "split bearer". NOTE 1: Typically, the MME and SGW cannot determine whether the RAN termination point(s) for the S1-U interface are located on a Master RAN node that has multiple IP addresses, or, on a Secondary RAN node. If the UE has indicated support for Dual Connectivity with NR and MME has an Access Restriction for NR for a UE (either signalled from the HSS, or, locally generated by VPLMN policy in the MME) then the MME shall signal this to the E-UTRAN as part of Handover Restriction List and to the UE in Attach and TAU Accept as defined in clauses 5.5.2.2.3, 5.5.2.4.3, 5.3.2.1, 5.3.3.1, 5.3.3.2 and D.3.6 respectively. An eNodeB supporting Dual Connectivity with NR checks whether the UE is allowed to use NR. If the UE is not allowed to use NR, the eNodeB shall not establish Dual Connectivity with NR as a secondary RAT. The MME uses "UE support for dual connectivity with NR" for SGW and PGW selection when the UE indicates support for NR and there is no Access Restriction for NR for the UE. An E-UTRAN cell, based on operator configuration, broadcasts whether it is capable of supporting dual connectivity with locally available NR secondary cell(s). At inter-RAT handover from NR or GERAN/UTRAN, the Access Restriction for NR is either already in the MME's UE context, or, is obtained from the HSS during the subsequent Tracking Area Update procedure (i.e. not from the source AMF/SGSN or source RAN). In both inter-RAT handover cases, any NR Access Restriction is then signalled to the E-UTRAN. NOTE 2: This signalling of the Access Restriction during the TAU after the inter-RAT handover procedure means that there is a small risk that NR resources are transiently allocated. The eNodeB, at which the S1-MME terminates, performs all necessary S1-MME related functions (as specified for any serving eNodeB) such as mobility management, relaying of NAS signalling, E-RAB handling, etc. and manages the handling of user plane connection of S1-U. Additional functional characteristics are: - User location information reporting is based on the identity of the cell that is serving the UE and supported by the eNodeB terminating S1-MME. The cell identity of the Primary cell in the secondary RAN node may also be included, if available. - Path update signalling for E-RABs configured as "SCG bearers" and Serving GW relocation cannot occur at the same time. - During handover with dual connectivity, the requirement of forwarding "end marker" packets to target node is also applicable to secondary RAN node if it is the source node for S1-U bearer. - After handover with data forwarding, the E-UTRAN initiated E-RAB modification procedure of clause 5.4.7 should not be initiated by the target eNodeB before "end marker" packet is received at the target RAN node or a timer in target eNodeB expires. - Relaying function is not supported. - CSG function may be supported if the Secondary eNodeB is a hybrid access eNodeB (see more details in clause 5.4.7 and in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [5]). NOTE 3: A HeNB cannot be the Master eNodeB, i.e. a HeNB cannot initiate the Secondary eNodeB Addition procedure. NOTE 4: A HeNB is not allowed to be the Secondary eNodeB if the HeNB is a closed access eNodeB. - When the Secondary eNodeB is a hybrid access eNodeB, the Master eNodeB may ask CSG membership verification to the MME using E-RAB Modification Indication message (for SCG bearers) or UE Context Modification Indication (for split bearers) message. The MME shall determine the CSG membership based on the CSG Membership Information as specified in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [5] and shall respond to the Master eNodeB using respectively a E-RAB Modification Confirm or a UE Context Modification Confirm, but shall not update the User CSG Information in the Core Network. - The LIPA function may be supported for the SCG bearer alternative, in the case that the Secondary eNodeB is a HeNB with a collocated L-GW (see more details in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [5]). - "SIPTO at the Local Network with L-GW function collocated with the (H)eNB" function may be supported (see more details in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [5]): - For the MCG and split bearer alternatives, if the Master eNodeB is collocated with a L-GW; and/or - For the SCG bearer alternative, if the Secondary eNodeB is a (H)eNB with a collocated L-GW. NOTE 5: LIPA or SIPTO at the Local Network PDN connection can be established if the SeNodeB has already been added before the UE requests establishment of the LIPA or SIPTO at the Local Network PDN connection. NOTE 6: LIPA or SIPTO at the Local Network PDN connection can be established if the UE is in the coverage of the candidate SeNodeB when the UE requests establishment of the LIPA or SIPTO at the Local Network PDN connection, but the SeNodeB has not yet been added. In this case, there is a time gap between the moment when the PDN connection establishment is completed and the moment when the SeNodeB Addition procedure is completed. - "SIPTO at the Local Network with stand-alone GW" function may be supported for the MCG, SCG, and split bearer alternatives if the Master and Secondary eNodeBs belong to the same LHN (see more detail in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [5]). | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.3.2a |
3,462 | 4.6.2.4 Network slice-specific authentication and authorization | The UE and network may support network slice-specific authentication and authorization. A serving PLMN or SNPN shall perform network slice-specific authentication and authorization for the S-NSSAI(s) of the HPLMN or the subscribed SNPN which are subject to it based on subscription information. The UE shall indicate whether it supports network slice-specific authentication and authorization in the 5GMM Capability IE in the REGISTRATION REQUEST message as specified in subclauses 5.5.1.2.2 and 5.5.1.3.2. The upper layer stores an association between each S-NSSAI and its corresponding credentials for the network slice-specific authentication and authorization. NOTE 1: The credentials for network slice-specific authentication and authorization and how to provision them in the upper layer are out of the scope of 3GPP. The network slice-specific authentication and authorization procedure shall not be performed unless the primary authentication and key agreement procedure as specified in the subclause 5.4.1 has successfully been completed. The AMF informs the UE about S-NSSAI(s) for which network slice-specific authentication and authorization (except for re-NSSAA) will be performed or is ongoing in the pending NSSAI. The AMF informs the UE about S-NSSAI(s) for which NSSAA procedure is completed as success in the allowed NSSAI or in the partially allowed NSSAI. The AMF informs the UE about S-NSSAI(s) for which NSSAA procedure is completed as failure in the rejected NSSAI for the failed or revoked NSSAA. The AMF stores and handles allowed NSSAI, partially allowed NSSAI, pending NSSAI, rejected NSSAI, and 5GS registration result in the REGISTRATION ACCEPT message according to subclauses 5.5.1.2.4 and 5.5.1.3.4. NOTE 2: The AMF maintains the NSSAA procedure status for each S-NSSAI, as specified in 3GPP TS 29.518[ 5G System; Access and Mobility Management Services; Stage 3 ] [20B] and the NSSAA procedure status for each S-NSSAI is not impacted by NSAC as specified in subclauses 4.6.2.5 and 4.6.3.1. NOTE 3: Upon completion of NSSAA procedures, it can happen that the total number of S-NSSAIs which need to be included in the allowed NSSAI exceeds eight. In this case, it is up to the AMF implementation on how to pick up the S-NSSAIs included in the allowed NSSAI. NOTE 4: It can happen that one or more S-NSSAIs included in the received allowed NSSAI, are not the S-NSSAIs that the UE intends to register to. In this case, it is up to the UE implementation on how to use these S-NSSAIs. To perform network slice-specific authentication and authorization for an S-NSSAI, the AMF invokes an EAP-based network slice-specific authentication and authorization procedure for the S-NSSAI, see subclause 5.4.7 and 3GPP TS 23.502[ Procedures for the 5G System (5GS) ] [9] using the EAP framework as described in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]. The AMF updates the allowed NSSAI, the partially allowed NSSAI and the rejected NSSAI using the generic UE configuration update procedure as specified in the subclause 5.4.4 after the network slice-specific authentication and authorization procedure is completed. The AMF shall send the pending NSSAI containing all S-NSSAIs for which the network slice-specific authentication and authorization procedure (except for re-NSSAA) will be performed or is ongoing in the REGISTRATION ACCEPT message. The AMF shall also include in the REGISTRATION ACCEPT message the allowed NSSAI containing one or more S-NSSAIs from the requested NSSAI which are allowed by the AMF and for which network slice-specific authentication and authorization is not required, if any. The AMF shall also include in the REGISTRATION ACCEPT message the partially allowed NSSAI containing one or more S-NSSAIs from the requested NSSAI which are allowed by the AMF in a list of TAs within the current registration area and for which network slice-specific authentication and authorization is not required, if any. The network slice-specific re-authentication and re-authorization procedure or the network slice-specific authorization revocation procedure can be invoked by the network for a UE supporting NSSAA at any time. After the network performs the network slice-specific re-authentication and re-authorization procedure or network slice-specific authorization revocation procedure: a) if network slice-specific re-authentication and re-authorization fails or network slice-specific authorization is revoked for some but not all S-NSSAIs in the allowed NSSAI or the partially allowed NSSAI,, the AMF updates the allowed NSSAI or the partially allowed NSSAI and the rejected NSSAI accordingly using the generic UE configuration update procedure as specified in the subclause 5.4.4 and inform the SMF to release all PDU sessions associated with the S-NSSAI for which network slice-specific re-authentication and re-authorization fails or network slice-specific authorization is revoked; b) if network slice-specific re-authentication and re-authorization fails or network slice-specific authorization is revoked for all S-NSSAIs in the allowed NSSAI or the partially allowed NSSAI but there are one or more default S-NSSAIs which are not subject to network slice-specific authentication and authorization or for which the network slice-specific authentication and authorization has been successfully performed, the AMF updates the allowed NSSAI or the partially allowed NSSAI containing these default S-NSSAIs and the rejected NSSAI accordingly using the generic UE configuration update procedure as specified in the subclause 5.4.4. The AMF shall also inform the SMF to release all PDU sessions associated with the S-NSSAI for which network slice-specific re-authentication and re-authorization fails or network slice-specific authorization is revoked; or c) if network slice-specific re-authentication and re-authorization fails or network slice-specific authorization is revoked for all S-NSSAIs in the allowed NSSAI or the partially allowed NSSAI and all default S-NSSAIs are subject to network slice-specific authentication and authorization, and the network slice-specific authentication and authorization has not been successfully performed for any of these default S-NSSAIs, then AMF performs the network-initiated de-registration procedure and includes the rejected NSSAI in the DEREGISTRATION REQUEST message as specified in the subclause 5.5.2.3 except when the UE has an emergency PDU session established or the UE is establishing an emergency PDU session. In this case the AMF shall send the CONFIGURATION UPDATE COMMAND message containing rejected NSSAI and inform the SMF to release all PDU sessions associated with the S-NSSAI for which network slice-specific re-authentication and re-authorization fails or network slice-specific authorization is revoked. After the emergency PDU session is released, the AMF performs the network-initiated de-registration procedure as specified in the subclause 5.5.2.3. The UE does not include in the requested NSSAI any of the S-NSSAIs from the pending NSSAI that the UE stores, regardless of the access type. When the UE storing a pending NSSAI intends to register to one or more additional S-NSSAIs not included in the pending NSSAI, the UE initiates the registration procedure with a requested NSSAI containing these S-NSSAIs as described in subclause 5.5.1.3.2. In this case, the requested NSSAI shall also include one or more S-NSSAIs from the allowed NSSAI or the partially allowed NSSAI, if the UE still wants to use the S-NSSAI(s) from the allowed NSSAI or the partially allowed NSSAI. During the registration procedure, when the AMF receives a requested NSSAI from a UE over an access type, for which there is a pending NSSAI including one or more S-NSSAIs that were previously requested over the same access type, the AMF considers S-NSSAIs included in the requested NSSAI and S-NSSAIs in the pending NSSAI that were previously requested over the same access type as requested S-NSSAIs by the UE. The AMF handles the requested S-NSSAIs as described in subclause 5.5.1.3.4. When performing the network slice-specific re-authentication and re-authorization procedure if the S-NSSAI is included in the allowed NSSAI for both 3GPP and non-3GPP accesses, and the UE is registered to both 3GPP and non-3GPP accesses in the same PLMN, then the AMF selects an access type to perform network slice-specific re-authentication and re-authorization based upon operator policy. If network slice-specific authorization is revoked for an S-NSSAI that is in the current allowed NSSAI for an access type or for an S-NSSAI that is in the current partially allowed NSSAI for 3GPP access type, the AMF shall: a) provide a new allowed NSSAI or a new partially allowed NSSAI, excluding the S-NSSAI for which the network slice-specific authorization is revoked; and b) provide a new rejected NSSAI for the failed or revoked NSSAA, including the S-NSSAI for which the network slice-specific authorization is revoked, with the rejection cause "S-NSSAI not available due to the failed or revoked network slice-specific authentication and authorization", to the UE using the generic UE configuration update procedure as specified in the subclause 5.4.4 and inform the SMF to release all PDU sessions associated with the S-NSSAI for which the network slice-specific authorization is revoked for this access type. If the UE requests the establishment of a new PDU session or the modification of a PDU session for an S-NSSAI for which the AMF is performing network slice-specific re-authentication and re-authorization procedure, the AMF may determine to not forward the 5GSM message to the SMF as described in subclause 5.4.5.2.4. NOTE 5: If the AMF receives the HTTP code set to "4xx" or "5xx" as specified in 3GPP TS 29.500[ 5G System; Technical Realization of Service Based Architecture; Stage 3 ] [20AA] or the AMF detects that the NSSAAF failure as specified in 3GPP TS 29.526[ 5G System; Network Slice-Specific and SNPN Authentication and Authorization services; Stage 3 ] [21A] during the NSSAA procedure for an S-NSSAI, then the AMF considers the NSSAA procedure has failed for this S-NSSAI. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.6.2.4 |
3,463 | 4.7.2.12 Extended coverage for GSM | The MS can support and use the extended coverage in GSM for IoT (EC-GSM-IoT) feature (see 3GPP TS 43.064[ None ] [159]). A GPRS MS using EC-GSM-IoT may operate in MS operation mode C only. If the MS uses one of the four coverage classes of EC-GSM-IoT as defined in 3GPP TS 43.064[ None ] [159], the MS shall calculate the value of the applicable NAS timers as indicated in tables 11.3, 11.3A and 11.2c using a multiplier of 3, unless the timer is deactivated. The NAS timer value obtained is used as described in the appropriate procedure subclause of this specification. The NAS timer value shall be calculated at start of a NAS procedure and shall not be re-calculated until the NAS procedure is completed, restarted or aborted. The usage of one of the four coverage classes of EC-GSM-IoT by an MS is indicated to the SGSN by lower layers. When a SGSN that supports EC-GSM-IoT performs NAS signaling with an MS that is using EC-GSM-IoT, the SGSN shall calculate the value of the applicable NAS timers as indicated in tables 11.4, 11.4a and 11.2d using a multiplier of 3. The NAS timer value shall be calculated at start of a NAS procedure and shall not be re-calculated until the NAS procedure is completed, restarted or aborted. In order to deal with use of extensive resources from the network, the operator may prevent specific subscribers from using enhanced coverage (see 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [74]). When in A/Gb mode, the MS supporting EC-GSM-IoT shall indicate support for restriction on use of enhanced coverage. The MS supporting restriction on use of enhanced coverage indicates "Mobile station supports restriction on use of enhanced coverage" in the MS network capability information element in the ATTACH REQUEST and ROUTING AREA UPDATE REQUEST message. If the MS supports restriction on use of enhanced coverage, the SGSN indicates whether the use of enhanced coverage is restricted or not in the ATTACH ACCEPT message and ROUTING AREA UPDATE ACCEPT message (see subclause 4.7.3.1 and subclause 4.7.5.1). If the use of enhanced coverage is restricted the MS shall not use enhanced coverage in the registered PLMN and in any PLMN which is in the list of equivalent PLMNs. | 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.12 |
3,464 | 8.136 Extended Trace Information | Extended Trace Information is coded as depicted in Figure 8.136-1. See 3GPP TS 32.422[ Telecommunication management; Subscriber and equipment trace; Trace control and configuration management ] [18] for details on trace related information. Figure 8.136-1: Extended Trace Information Octets 5 to 10 represent the Trace Reference parameter as defined in clause 5.6 of 3GPP TS 32.422[ Telecommunication management; Subscriber and equipment trace; Trace control and configuration management ] [18]. Triggering Events, List of NE Types, Session Trace Depth, List of Interfaces and IP Address of Trace Collection Entity are specified in 3GPP TS 32.422[ Telecommunication management; Subscriber and equipment trace; Trace control and configuration management ] [18]. NOTE: The List of Triggering Events, List of NE Types and List of Interfaces include the events, NE types and List of interfaces to be traced in the target system during an EPS to 5GS or 5GS to EPS mobility, see clause 4.1.2.15.2 of 3GPP TS 32.422[ Telecommunication management; Subscriber and equipment trace; Trace control and configuration management ] [18]. See 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [5], clause 10.5.1.4, Mobile Identity, for the coding of MCC and MNC, whose values are obtained from the serving PLMN that the EM/NM is managing. If MNC is 2 digits long, bits 5 to 8 of octet 6 are coded as "1111". | 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.136 |
3,465 | 10.5.6.14 MBMS bearer capabilities | The purpose of the MBMS bearer capabilities information element is to indicate the maximum bit rate for downlink supported by the MS for an MBMS context. NOTE: The information element indicates the static physical capabilities of the MS, independent of the radio access (UTRAN or GERAN), the radio conditions, or other CS or PS services possibly activated by the MS. The MBMS bearer capabilities is a type 4 information element with a maximum length of 4 octets. The MBMS bearer capabilities information element is coded as shown in figure 10.5.155/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.169/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Figure 10.5.155/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : MBMS bearer capabilities information element Table 10.5.169/3GPP TR 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : MBMS bearer capabilities information element Maximum bit rate for downlink, octet 3 (see 3GPP TS 23.107[ Quality of Service (QoS) concept and architecture ] [81]) The coding is identical to that of the maximum bit rate for downlink, octet 9, in the Quality of service information element (see subclause 10.5.6.5). If the sending entity wants to indicate a maximum bit rate for downlink higher than 8640 kbps, it shall set octet 3 to "11111110", i.e. 8640 kbps, and shall encode the value for the maximum bit rate in octet 4. Maximum bit rate for downlink (extended), octet 4 The coding is identical to that of the maximum bit rate for downlink (extended), octet 15, in the Quality of service information element (see subclause 10.5.6.5). | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 10.5.6.14 |
3,466 | 4.2.4 UE Configuration Update 4.2.4.1 General | UE configuration may be updated by the network at any time using UE Configuration Update procedure. UE configuration includes: - Access and Mobility Management related parameters decided and provided by the AMF. This includes the Configured NSSAI and its mapping to the Subscribed S-NSSAIs, the Allowed NSSAI and its mapping to Subscribed S-NSSAIs, the Partially Allowed NSSAI and its mapping to Subscribed S-NSSAIs, the list of S-NSSAI(s) rejected partially in the RA, the Service Gap time, the list of Rejected NSSAIs if the UE Configuration Update procedure is triggered by the AMF after Network Slice-Specific Authentication and Authorization of S-NSSAIs, the Truncated 5G-S-TMSI Configuration and a priority subscription indication (e.g. MPS). If the UE and the AMF support RACS, this may also include a PLMN-assigned UE Radio Capability ID or alternatively a PLMN-assigned UE Radio Capability ID deletion indication. If the UE and AMF supports Disaster Roaming service, this may also include the "list of PLMN(s) to be used in Disaster Condition", Disaster Roaming wait range information, Disaster Return wait range information and notifying UE that the disaster condition is no longer applicable, as specified in TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The AMF may also update MBSR (IAB-UE) with MBSR authorization information as specified in clause 5.35A.4 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], S-NSSAI location availability information. The AMF may determine a Maximum Time Offset controlling when UEs are allowed to initiate NAS signalling with the network as specified in clause 5.4.13.5 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. - UE Policy provided by the PCF. When AMF wants to change the UE configuration for access and mobility management related parameters the AMF initiates the procedure defined in clause 4.2.4.2. When the PCF wants to change or provide new UE Policies in the UE, the PCF initiates the procedure defined in clause 4.2.4.3. If the UE Configuration Update procedure requires the UE to initiate a Registration procedure, the AMF indicates this to the UE explicitly. The procedure in clause 4.2.4.2 may be triggered also when the AAA Server that performed Network Slice-Specific Authentication and Authorization for an S-NSSAI revokes the authorization. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.2.4 |
3,467 | 9.9.3.62 WUS assistance information | The purpose of the WUS assistance information information element is to transfer the required assistance information to determine the WUS group used when paging the UE. The coding of the information element allows combining different types of WUS assistance information. The WUS assistance information information element is coded as shown in figure 9.9.3.62.1, figure 9.9.3.62.2 and table 9.9.3.62.1. The WUS assistance information is a type 4 information element, with a minimum length of 3 octets. Figure 9.9.3.62.1: WUS assistance information information element Figure 9.9.3.62.2: WUS assistance information type –type of information= "000" Table 9.9.3.62.1: WUS assistance information information element | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.9.3.62 |
3,468 | 5.2.18.2.1 Nucmf_Provisioning_Create service operation | Service operation name: Nucmf_Provisioning_Create Description: The consumer creates a UCMF dictionary entry (or more entries) for a Manufacturer-assigned UE Radio Capability ID(s). For each UE Radio Capability ID the following inputs are provided: a) a UE radio access capability set with respective coding format or the UE radio access capability set in both TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [16] and TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [12] coding formats and each RATs' UE Radio Capability for Paging; and b) the related UE model(s) IMEI/TAC value(s) the UE radio capability ID applies to. Inputs, Required: (list of) [UE Radio Capability ID(s), set(s) of UE radio access capability set and UE Radio Capability for Paging and respective Coding format(s), (list of) IMEI/TAC value(s)]. Inputs, Optional: None. Outputs, Required: None. Outputs, Optional: None. The Coding format(s) indicates the format of the respective UE radio access capabilities as defined in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [16] or TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [12]. The UCMF dictionary entry shall not contain UTRAN radio capabilities. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.18.2.1 |
3,469 | 7B.2 Authentication for 5G-RG | The 5G-RG can be connected to 5GC via W-5GAN, NG RAN or via both accesses. The registration procedure for the 5G-RG connecting to 5GC via NG-RAN is specified in TS 23.316[ Wireless and wireline convergence access support for the 5G System (5GS) ] [79] clause 4.11. The registration procedure for the 5G-RG connecting to 5GC via W-5GAN is specified in TS 23.316[ Wireless and wireline convergence access support for the 5G System (5GS) ] [79] clause 7.2.1. The Untrusted non-3GPP access procedure defined in clause 7.2.1 is used as the basis for registration of the 5G-RG. The 5G-RG shall support both 5G-AKA and EAP-AKA’ and it shall be authenticated by the 3GPP home network. The 5G-RG is equivalent to a normal UE. As 5G-RG is a UE from 5GC point of view, the authentication framework defined in clause 6.1.3 shall be used to authenticate the 5G-RG. In case of 5G-RG connects to 5GC via 5G-RAN, comparing to clause 6.1, the difference is: - UE is replaced by 5G-RG. In case of 5G-RG connects to 5GC via W-5GAN, a W-CP protocol stack message shall be used between the 5G-RG and the W-5GAN for encapsulating NAS message. The authentication method is executed between the 5G-RG and AUSF as shown below. Figure 7B.2-1 5G-RG authentication procedure 1. 5G-RG establishes a W-CP connection with a W-5GAN. The detail of connection is out of the scope of 3GPP. 2. (void) 3. The 5G-RG shall send a message using W-CP protocol stack that contains a Registration message containing UE security capabilities and the SUCI. If there is an available security context, the 5G-RG shall integrity protect the Registration Request message and shall send the 5G-GUTI instead of SUCI. If the 5G-RG has registered to the same AMF through NG RAN, and if this is the first time that the 5G-RG connects to the 5GC throughW-5GAN, the value of corresponding UL NAS COUNT used for integrity protection is 0; else it can use the existing non-3GPP specific UL NAS COUNT for integrity protection. NOTE: Since the 5G-RG will not use non-3GPP access, and to avoid to create new category of security context, so the non-3GPP specific security context is used to refer to the security context that 5G-RG is used through wireline access. 4. The W-AGF shall select an AMF as specified in TS 23.316[ Wireless and wireline convergence access support for the 5G System (5GS) ] [79]. The W-AGF shall then forward the Registration Request received from the UE to the selected AMF within an N2 initial UE message 5. If the AMF receives a 5G-GUTI and the Registration is integrity protected, it may use the security context to verify the integrity protection as describe in clause 6.4.6. If the 5G-RG has registered to the same AMF through NG RAN, and if this is the first time that the AMF receives UE’s NAS signalling through wireline access, the value of corresponding UL NAS COUNT used for integrity verification is 0; else it can use the existing non-3GPP specific UL NAS COUNT for integrity verification. If integrity is verified successfully, it indicates that 5G-RG is authenticated by AMF. If integrity is verified successfully and no newer security context has been activated over the NG RAN, then step 8 to step 11 may be skipped. If integrity is verified successfully and a newer security context has been activated over the NG RAN then authentication may be skipped but the AMF shall activate the newer context with a NAS SMC procedure as described in step 8 and onwards. Otherwise, the AMF shall authenticate the 5G-RG. If the AMF decides to authenticate the 5G-RG, it shall use one of the methods from clause 6.1.3. In this case, the AMF shall send a key request to the AUSF. The AUSF may initiate an authentication procedure as specified in clause 6.1.3. Between AMF and UE (5G-RG), the authentication packets are encapsulated within NAS authentication messages and the NAS authentication messages are carried in N2 signalling between the AMF and W-AGF, and then are encapsulated using W-CP protocol stack message between the W-AGF and the UE (5G-RG). In the final authentication message from the home network, the AUSF shall send the anchor key KSEAF derived from KAUSF to the SEAF. The SEAF shall derive the KAMF from KSEAF and send it to the AMF which is used by the AMF to derive NAS security keys. If EAP-AKA' is used for authentication as described in clause 6.1.3.1, then the AUSF shall include the EAP-Success. The 5G-RG also derives the anchor key KSEAF and from that key it derives the KAMF followed by NAS security keys. The NAS COUNTs associated with NAS connection identifier "0x02" are set at the 5G-RG and AMF. 6. The AMF shall send a Security Mode Command (SMC) to the UE (5G-RG) in order to activate NAS security associated with NAS connection identifier "0x02". This message is first sent to W-AGF (within an N2 message). If EAP-AKA' is used for authentication, the AMF shall encapsulate the EAP-Success received from AUSF within the SMC message. 7. The W-AGF shall forward the NAS SMC to 5G-RG. 8. The W-AGF shall forward the NAS packet containing NAS SMC Complete to the AMF over the N2 interface. 9. The AMF upon reception of the NAS SMC Complete from the UE (5G-RG) or upon success of integrity protection verification, initiates the NGAP procedure to set up the AN context. AMF shall compute the W-AGF key, KWAGF that is an equivalent to key KN3IWF, using the uplink NAS COUNT associated with NAS connection identifier "0x02" as defined in Annex A.9. 10. Upon receiving NAS Security Mode Complete, the AMF shall send an N2 Initial Context Setup Request message to the W-AGF. The message contains the KWAGF. NOTE: Whether the key KWAGF is used by the 5G-RG and W-AGF is out of the scope of 3GPP. 11. (void) 12. Upon receiving the NAS Registration Accept message from the AMF, the W-AGF shall forward it to the 5G-RG over the established W-CP. All further NAS messages between the UE and the W-AGF shall be sent over the established W-CP. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 7B.2 |
3,470 | 4.3.1.5 Abnormal cases on the network side | The following abnormal cases can be identified: a) RR connection failure: If the RR connection is lost before the TMSI REALLOCATION COMPLETE message is received, the network shall release all MM connections, if any. Furthermore, the network should consider both the old and the new TMSI as occupied for a certain recovery time. During this period the network: - may use the IMSI for paging or network originated transactions on the CM layer. Upon response from the mobile station the TMSI reallocation procedure shall be restarted; - may consider the new TMSI as valid if it is used by the mobile station; or - may use the identification procedure followed by a new TMSI reallocation procedure, if the mobile station uses the old TMSI (see subclause 4.3.3). Other implementations are possible, e.g. the network may page with the old TMSI. b) Expiry of timer T3250: The TMSI reallocation procedure is supervised by the timer T3250 (see example in figure 4.1). At expiry of timer T3250 the network may release the RR connection. In this case, the network shall abort the reallocation procedure release all MM connections if any, and follow the rules for the case a as described above. Figure 4.1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : TMSI reallocation 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.1.5 |
3,471 | 12.3.10.2.3 Self-protection by the overloaded GTP-C entity | A source GTP-C entity enforcing the overload control cannot ensure that the overloaded peer will not receive more messages than what it can handle during the overload condition, e.g. the "loss" algorithm does not guarantee that the future traffic reaches perfectly that requested by the overloaded GTP-C entity. Hence, the overloaded target GTP-C entity shall protect itself from the risk of meltdown even in a network where all the sending GTP-C entities support the overload control mechanism. As a part of this self-protection, the overloaded target GTP-C entity may reject the messages which it cannot handle during an overloaded state. A GTP-C entity which decides to not process an incoming request message due to overload should still send a reject response message, if possible, indicating the temporary unavailability of the resources; otherwise the request message may be dropped. NOTE: Without a response message, the source GTP-C entity cannot determine whether the request did not reach the target GTP-C entity due to a network error or whether the target GTP-C entity was in overload and not able to process the request and send a response message. This will cause the source GTP-C entity to retransmit the request message and hence will increase further the overload at the target node. The GTP-C entity may apply message prioritization as described in clause 12.3.9.3 when selecting the incoming request messages to be throttled. While rejecting the message due to overload, the GTP-C entity shall set the cause to "GTP-C Entity Congestion" or "APN congestion" (for node level or APN level overload respectively) and may include the Overload Control Information in the rejection response as specified in clauses 12.3.5.1.1 and 12.3.11. | 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 | 12.3.10.2.3 |
3,472 | 6.2.4A.8 A-MPR for CA_NS_08 | If the UE is configured to CA_42C and it receives IE CA_NS_08 the allowed maximum output power reduction applied to transmission on the PCC and the SCC for contiguously aggregated signals is specified in Table 6.2.4A.8-1. Table 6.2.4A.8-1: Contiguous Allocation A-MPR for CA_NS_08 If the UE is configured to CA_42C and it receives IE CA_NS_08 the allowed maximum output power reduction applied to transmissions on the PCell and the SCell with non-contiguous resource allocation is defined as follows A-MPR = CEIL {MA, 0.5} Where MA is defined as follows MA = 20 ; 0 ≤ A < 0.025 23 – 120A ; 0.025 ≤ A < 0.05 17.53 – 10.59A ; 0.05 ≤ A ≤ 0.9 8 ; 0.9 ≤ A ≤ 1 Where A = NRB_alloc / NRB_agg. | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.2.4A.8 |
3,473 | 4.15.4.5.3 Information flow for UPF event exposure service for any UE | Figure 4.15.4.5.3-1: UPF Information Exposure to the UPF event consumer (e.g. NWDAF) of any UE scenario 1. (For the case when the UPF event consumer is NWDAF) The analytics consumer sends a request to the NWDAF for analytics on any UE. The analytics consumer provides the value "any UE" in the Target of Analytics Reporting. Analytics Filter Information optionally contains DNN, S-NSSAI, Area of Interest, Application server IP address/FQDN, APP ID, DNAI, etc. 2. (Optional and only when the UPF event consumer is NWDAF) If the Analytic Filter Information does not contain DNN/S-NSSAI, but only includes application server IP address/FQDN, the NWDAF should first obtain the DNAI from NEF. The NWDAF invokes Nnef_DNAIMapping_Subscribe service to request the DNAI information. The request includes EAS IP/IP range and/or FQDN. 3. (Conditional, if step 2 took place) The NEF determines the suitable DNAI(s) and provides them to NWDAF. 4. The UPF event consumer triggers the SMF(s)/UPF(s) discovery to NRF by Nnrf_NFDiscovery_Request providing the DNN, S-NSSAI, DNAI etc. This procedure is to discover the related SMF(s)/UPF(s) associated with any UE and support the indicated DNAI. Either SMF(s) or UPF(s) are discovered depending on whether the subscription request to UPF events meets the criteria for direct subscription to UPF as defined in clause 5.8.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]). 5. The NRF provides Nnrf_NFDiscovery_Response that may refer to several SMFs/UPFs. 6. (Option 1) If the subscribed UPF events needs the SMF(s) to do a third-party subscription onto UPF (as defined in clause 5.8.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]), the same procedure as Indirect subscription via several SMFs (steps 3 - 5 in Figure 4.15.4.5.2-1(for single UE)) takes place via each discovered SMF. 7. (Option 2) If the subscribed UPF events allows to directly subscribe to UPF (as defined in clause 5.8.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]), the UPF event consumer (e.g. NWDAF) triggers the Nupf_EventExposure_Subscribe to all discovered UPFs. The information included in the subscription is as described in step 3 in clause 4.15.4.5.2. 8. Each of the UPFs invokes Nupf_EventExposure_Notify service operation directly to the UPF event consumer (e.g. NWDAF). | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.15.4.5.3 |
3,474 | 7A Security for trusted non-3GPP access to the 5G core network 7A.1 General | Security for trusted non-3GPP access to the 5G Core network is achieved when the UE registers to the 5GC via the TNAN. The UE registers to 5GC and, at the same time, it authenticates with the TNAN by using the EAP-5G procedure, similar to the one used with the registration procedure for untrusted non-3GPP access. The link between the UE and the TNAN can be any data link (L2) that supports EAP encapsulation. The requirement on the Ta interface between the TNAP and TNGF can be found in clause 4.2.8.3.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The TNGF terminates the EAP-5G signalling andfowards the NAS message to the 5GC when the UE attempts to register to 5GC via the TNAN. The security relies on Layer-2 security between UE and TNAP, which is a trusted entity so that no IPSec encryption would be necessary between UE and TNGF, i.e. NULL encryption is sufficient for the user plane and signalling. NOTE: The encryption protection over Layer-2 between UE and TNAP is assumed to be enabled. Separate IPSec SAs may be used for NAS transport and PDU Sessions. At the end of the UE’s registration to 5GC, an IPSec SA (NWt) is established between the UE and TNGF. This is used to protect NAS messages between the UE and TNGF. Later when the UE initiates a PDU session establishment, the TNGF initiates establishment of one or more IPSec child SAs per PDU session. This results in additional IPSec SA’s (NWt) to be setup between the UE and TNGF-UP which are then for user plane transport between the two. Clause 7A.2.4 describes how WLAN UEs that do not support 5GC NAS (N5CW) register via trusted non-3GPP access. Those N5CW devices are able to authenticate to the network with 3GPP credentials and register with the help of an interworking function (TWIF) that provides the 5GC NAS protocol stack towards the AMF. As defined in clause 7.1, it is the home operator policy decision if a non-3GPP access network is treated as trusted non-3GPP access network. When all of the security domains in clause 4.1 of the present specification related to the non-3GPP access network are considered sufficiently secure by the home operator, the non-3GPP access may be identified as a trusted non-3GPP access for that operator. However, this policy decision may additionally be based on reasons not related to security feature groups. NOTE: It is specified in clause 7.1a of the current document how the UE gets the operator policy and how it will behave accordingly. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 7A |
3,475 | 5.2.5.3.3 Npcf_PolicyAuthorization_Update service operation | Service operation name: Npcf_PolicyAuthorization_Update Description: Provides updated information to the PCF. Inputs, Required: Identification of the application session context. Inputs, Optional: Media type, Media format, bandwidth requirements, sponsored data connectivity information if applicable, flow description information as described in clause 6.1.3.6 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20], AF Application Identifier, AF Communication Service Identifier, AF Record Identifier, Flow status, Priority indicator, resource allocation outcome, AF Application Event Identifier, a list of DNAI(s) and corresponding routing profile ID(s) or N6 traffic routing information, AF Transaction Id, Early and/or late notifications about UP path management events, temporal validity condition, spatial validity condition, Information for EAS IP Replacement in 5GC, Indication for EAS Relocation, AF indication for simultaneous connectivity over source and target PSA at edge relocation as described in clause 5.6.7 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], Background Data Transfer Reference ID, priority sharing indicator as described in clause 6.1.3.15 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20], pre-emption control information as described in clause 6.1.3.15 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20], Port Management Information Container and related port number, User plane node Management Information Container, TSN AF parameters provided by the TSN AF to the PCF as described in clause 6.1.3.23 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20], TSCTSF parameters provided by the TSCTSF to the PCF as described in clause 6.1.3.23a and clause 6.1.3.23b of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20], QoS Reference or individual QoS parameters as described in clause 6.1.3.22 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20], Alternative Service Requirements (containing one or more QoS Reference parameters or Requested Alternative QoS Parameter Sets in a prioritized order), TSC Assistance Container, QoS Monitoring parameter(s) as defined in clause 5.45 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], Reporting frequency, Target of reporting and optional an indication of local event notification as described in clause 6.1.3.21 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20], MPS for Data Transport Service indicator as described in clause 6.1.3.11 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20], Packet Delay Variation requirements as described in clause 6.1.3.26 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20], SFC Identifier(s), Metadata, Periodicity as described clauses 6.1.3.22 and 6.3.1 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20], PDU Set QoS Parameters as described in clause 5.7.7 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], Protocol Description as described in clause 5.37.5 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], Notification Target Address for PMIC/UMIC UPF event, Correlation ID for PMIC/UMIC UPF event, updated information for Multi-modal Service Requirements as described in clause 6.1.3.27.3 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. NOTE: When only one DNAI and corresponding routing profile ID(s) and the Indication for EAS Relocation are available, the presented DNAI is the target DNAI as defined in clause 6.3.7 of TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [74]. Outputs, Required: Success or Failure (reason for failure, e.g. as defined in clause 6.1.3.16 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]). Outputs, Optional: The service information that can be accepted by the PCF. Provides updated application level information and communicates with Npcf_SMPolicyControl service to determine and install the policy according to the information provided by the NF Consumer. Updates an application context in the PCF. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.5.3.3 |
3,476 | 9.4.14 Routing area update request | This message is sent by the MS to the network either to request an update of its location file or to request an IMSI attach for non-GPRS services. See table 9.4.14/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Message type: ROUTING AREA UPDATE REQUEST Significance: dual Direction: MS to network Table 9.4.14/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : ROUTING AREA UPDATE REQUEST message content | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.4.14 |
3,477 | – NR-DL-PRS-PDC-Info | The IE NR-DL-PRS-PDC-Info defines downlink PRS configuration for PDC. NR-DL-PRS-PDC-Info information element -- ASN1START -- TAG-NR-DL-PRS-PDC-INFO-START NR-DL-PRS-PDC-Info-r17 ::= SEQUENCE { nr-DL-PRS-PDC-ResourceSet-r17 NR-DL-PRS-PDC-ResourceSet-r17 OPTIONAL, -- Need R ... } NR-DL-PRS-PDC-ResourceSet-r17 ::= SEQUENCE { periodicityAndOffset-r17 NR-DL-PRS-Periodicity-and-ResourceSetSlotOffset-r17, numSymbols-r17 ENUMERATED {n2, n4, n6, n12, n1-v1800, spare3, spare2, spare1}, dl-PRS-ResourceBandwidth-r17 INTEGER (1..63), dl-PRS-StartPRB-r17 INTEGER (0..2176), resourceList-r17 SEQUENCE (SIZE (1..maxNrofPRS-ResourcesPerSet-r17)) OF NR-DL-PRS-Resource-r17, repFactorAndTimeGap-r17 RepFactorAndTimeGap-r17 OPTIONAL, -- Need S ... } NR-DL-PRS-Periodicity-and-ResourceSetSlotOffset-r17 ::= CHOICE { scs15-r17 CHOICE { n4-r17 INTEGER (0..3), n5-r17 INTEGER (0..4), n8-r17 INTEGER (0..7), n10-r17 INTEGER (0..9), n16-r17 INTEGER (0..15), n20-r17 INTEGER (0..19), n32-r17 INTEGER (0..31), n40-r17 INTEGER (0..39), n64-r17 INTEGER (0..63), n80-r17 INTEGER (0..79), n160-r17 INTEGER (0..159), n320-r17 INTEGER (0..319), n640-r17 INTEGER (0..639), n1280-r17 INTEGER (0..1279), n2560-r17 INTEGER (0..2559), n5120-r17 INTEGER (0..5119), n10240-r17 INTEGER (0..10239), ... }, scs30-r17 CHOICE { n8-r17 INTEGER (0..7), n10-r17 INTEGER (0..9), n16-r17 INTEGER (0..15), n20-r17 INTEGER (0..19), n32-r17 INTEGER (0..31), n40-r17 INTEGER (0..39), n64-r17 INTEGER (0..63), n80-r17 INTEGER (0..79), n128-r17 INTEGER (0..127), n160-r17 INTEGER (0..159), n320-r17 INTEGER (0..319), n640-r17 INTEGER (0..639), n1280-r17 INTEGER (0..1279), n2560-r17 INTEGER (0..2559), n5120-r17 INTEGER (0..5119), n10240-r17 INTEGER (0..10239), n20480-r17 INTEGER (0..20479), ... }, scs60-r17 CHOICE { n16-r17 INTEGER (0..15), n20-r17 INTEGER (0..19), n32-r17 INTEGER (0..31), n40-r17 INTEGER (0..39), n64-r17 INTEGER (0..63), n80-r17 INTEGER (0..79), n128-r17 INTEGER (0..127), n160-r17 INTEGER (0..159), n256-r17 INTEGER (0..255), n320-r17 INTEGER (0..319), n640-r17 INTEGER (0..639), n1280-r17 INTEGER (0..1279), n2560-r17 INTEGER (0..2559), n5120-r17 INTEGER (0..5119), n10240-r17 INTEGER (0..10239), n20480-r17 INTEGER (0..20479), n40960-r17 INTEGER (0..40959), ... }, scs120-r17 CHOICE { n32-r17 INTEGER (0..31), n40-r17 INTEGER (0..39), n64-r17 INTEGER (0..63), n80-r17 INTEGER (0..79), n128-r17 INTEGER (0..127), n160-r17 INTEGER (0..159), n256-r17 INTEGER (0..255), n320-r17 INTEGER (0..319), n512-r17 INTEGER (0..511), n640-r17 INTEGER (0..639), n1280-r17 INTEGER (0..1279), n2560-r17 INTEGER (0..2559), n5120-r17 INTEGER (0..5119), n10240-r17 INTEGER (0..10239), n20480-r17 INTEGER (0..20479), n40960-r17 INTEGER (0..40959), n81920-r17 INTEGER (0..81919), ... }, ... } NR-DL-PRS-Resource-r17 ::= SEQUENCE { nr-DL-PRS-ResourceID-r17 NR-DL-PRS-ResourceID-r17, dl-PRS-SequenceID-r17 INTEGER (0..4095), dl-PRS-CombSizeN-AndReOffset-r17 CHOICE { n2-r17 INTEGER (0..1), n4-r17 INTEGER (0..3), n6-r17 INTEGER (0..5), n12-r17 INTEGER (0..11), ... }, dl-PRS-ResourceSlotOffset-r17 INTEGER (0..maxNrofPRS-ResourceOffsetValue-1-r17), dl-PRS-ResourceSymbolOffset-r17 INTEGER (0..12), dl-PRS-QCL-Info-r17 DL-PRS-QCL-Info-r17 OPTIONAL, -- Need N ..., [[ dl-PRS-ResourceSymbolOffset-v1800 INTEGER (13) OPTIONAL -- Need R ]] } DL-PRS-QCL-Info-r17 ::= CHOICE { ssb-r17 SEQUENCE { ssb-Index-r17 INTEGER (0..63), rs-Type-r17 ENUMERATED {typeC, typeD, typeC-plus-typeD}, ... }, dl-PRS-r17 SEQUENCE { qcl-DL-PRS-ResourceID-r17 NR-DL-PRS-ResourceID-r17, ... }, ... } NR-DL-PRS-ResourceID-r17 ::= INTEGER (0..maxNrofPRS-ResourcesPerSet-1-r17) RepFactorAndTimeGap-r17 ::= SEQUENCE { repetitionFactor-r17 ENUMERATED {n2, n4, n6, n8, n16, n32, spare2, spare1}, timeGap-r17 ENUMERATED {s1, s2, s4, s8, s16, s32, spare2, spare1} } -- TAG-NR-DL-PRS-PDC-INFO-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
3,478 | 9.9.3.33 Tracking area identity list | The purpose of the Tracking area identity list information element is to transfer a list of tracking areas from the network to the UE. The coding of the information element allows combining different types of lists. The lists of type "00" and "01" allow a more compact encoding, when the different TAIs are sharing the PLMN identity. The Tracking area identity list information element is coded as shown in figure 9.9.3.33.1, figure 9.9.3.33.2, figure 9.9.3.33.3, figure 9.9.3.33.4 and table 9.9.3.33.1. The Tracking area identity list is a type 4 information element, with a minimum length of 8 octets and a maximum length of 98 octets. The list can contain a maximum of 16 different tracking area identities. Figure 9.9.3.33.1: Tracking area identity list information element Figure 9.9.3.33.2: Partial tracking area identity list – type of list = "00" Figure 9.9.3.33.3: Partial tracking area identity list – type of list = "01" Figure 9.9.3.33.4: Partial tracking area identity list – type of list = "10" Table 9.9.3.33.1: Tracking area identity list information element | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.9.3.33 |
3,479 | 28.3.2.2.3 Tracking Area Identity based N3IWF FQDN | The Tracking Area Identity based N3IWF FQDN is used to support location based N3IWF selection within a PLMN. There are two N3IWF FQDNs defined one based on a TAI with a 2 octet TAC and a 5GS one based on a 3 octet TAC. 1) The Tracking Area Identity based N3IWF FQDN using a 2 octet TAC shall be constructed respectively as: "tac-lb<TAC-low-byte>.tac-hb<TAC-high-byte>.tac.n3iwf.5gc.mnc<MNC>.mcc<MCC>.pub.3gppnetwork.org" where - the <MNC> and <MCC> shall identify the PLMN where the N3IWF is located and shall be encoded as - <MNC> = 3 digits - <MCC> = 3 digits If there are only 2 significant digits in the MNC, one "0" digit shall be inserted at the left side to fill the 3 digits coding of MNC in the N3IWF FQDN. - the <TAC>, together with the <MCC> and <MNC> shall identify the Tracking Area Identity the UE is located in. The TAC is a 16-bit integer. The <TAC-high-byte> is the hexadecimal string of the most significant byte in the TAC and the <TAC-low-byte > is the hexadecimal string of the least significant byte. If there are less than 2 significant digits in <TAC-high-byte> or <TAC-low-byte >, "0" digit(s) shall be inserted at the left side to fill the 2 digit coding; As examples, - the Tracking Area Identity based N3IWF FQDN for the TAC H'0B21, MCC 345 and MNC 12 is coded in the DNS as: "tac-lb21.tac-hb0b.tac.n3iwf.5gc.mnc012.mcc345.pub.3gppnetwork.org" 2) The 5GS Tracking Area Identity based N3IWF FQDN using a 3 octet TAC shall be constructed respectively as: "tac-lb<TAC-low-byte>.tac-mb<TAC-middle-byte>.tac-hb<TAC-high-byte>.5gstac.n3iwf.5gc.mnc<MNC>.mcc<MCC>.pub.3gppnetwork.org" where - the <MNC> and <MCC> shall identify the PLMN where the N3IWF is located and shall be encoded as - <MNC> = 3 digits - <MCC> = 3 digits If there are only 2 significant digits in the MNC, one "0" digit shall be inserted at the left side to fill the 3 digits coding of MNC in the N3IWF FQDN. - the <TAC>, together with the <MCC> and <MNC> shall identify the 5GSTracking Area Identity the UE is located in. The 5GS TAC is a 24-bit integer. The <TAC-high-byte> is the hexadecimal string of the most significant byte in the TAC and the <TAC-low-byte > is the hexadecimal string of the least significant byte. If there are less than 2 significant digits in <TAC-low-byte>, <TAC-middle-byte> or <TAC-high-byte >, "0" digit(s) shall be inserted at the left side to fill the 2 digit coding; As examples, - the 5GS Tracking Area Identity based N3IWF FQDN for the 5GS TAC H'0B1A21, MCC 345 and MNC 12 is coded in the DNS as: "tac-lb21.tac-mb1a.tac-hb0b.5gstac.n3iwf.5gc.mnc012.mcc345.pub.3gppnetwork.org" | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 28.3.2.2.3 |
3,480 | D.1 GTP-C interfaces not supporting Load Control | Load Control has been designed as a generic mechanism possibly applicable to any GTP-C node. However, for the reasons clarified below, in the current release, Load Control is not supported for the following GTP-C based interfaces: - S3, S10, S16 (limited GTP-C signalling traffic, to minimize impact to the MME/S4-SGSN); - Sm, Sn (limited GTP-C signalling traffic, to avoid impact to the MBMS GW); - Sv (limited GTP-C signalling traffic, to avoid impact to the legacy CS products); - S101, S121 (to avoid impacts to the legacy HRPD products); - Gn/Gp (to avoid impact to the legacy Gn-SGSN/GGSN products and GTPv1-C protocol). | 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 | D.1 |
3,481 | 10.5.7.7 Uplink data status | The purpose of the Uplink data status information element is to indicate to the network which preserved PDP contexts have uplink data pending. The Uplink data status information element is a type 4 information element with 4 octets length. The Uplink data status information element is coded as shown in figure 10.5.149/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.166/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Figure 10.5.149A/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Uplink data status information element Table 10.5.166/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Uplink data status information element NSAPI uplink status (octet 3 and 4) Octet 3, bits 1 to 5 are all spare and shall be encoded as 0 NSAPI(5) – NSAPI(15) (octets 3 – 4): 0 no uplink data are pending for the preserved PDP context or the PDP context is PDP-INACTIVE or is PDP-ACTIVE with a RAB already established. 1 uplink data are pending for the preserved PDP context. | 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.7.7 |
3,482 | 5.3.2.2 HARQ process | For each TTI where a transmission takes place for the HARQ process, one or two (in case of downlink spatial multiplexing) TBs and the associated HARQ information are received from the HARQ entity. For each received TB and associated HARQ information, the HARQ process shall: - if the NDI, when provided, has been toggled compared to the value of the previous received transmission corresponding to this TB; or - if the HARQ process is equal to the broadcast process and if this is the first received transmission for the TB according to the system information schedule indicated by RRC; or - if this is the very first received transmission for this TB (i.e. there is no previous NDI for this TB): - consider this transmission to be a new transmission. - else: - consider this transmission to be a retransmission. The MAC entity then shall: - if this is a new transmission: - attempt to decode the received data. - else if this is a retransmission: - if the data for this TB has not yet been successfully decoded: - combine the received data with the data currently in the soft buffer for this TB and attempt to decode the combined data. - if the data which the MAC entity attempted to decode was successfully decoded for this TB; or - if the data for this TB was successfully decoded before: - if the HARQ process is equal to the broadcast process: - deliver the decoded MAC PDU to upper layers. - else if this is the first successful decoding of the data for this TB: - deliver the decoded MAC PDU to the disassembly and demultiplexing entity. - generate a positive acknowledgement (ACK) of the data in this TB. - else: - replace the data in the soft buffer for this TB with the data which the MAC entity attempted to decode. - generate a negative acknowledgement (NACK) of the data in this TB. - if the HARQ process is associated with a transmission indicated with a Temporary C-RNTI and the Contention Resolution is not yet successful (see clause 5.1.5); or - if the HARQ process is equal to the broadcast process; or - if the HARQ process is not associated with a transmission indicated with a PUR-RNTI and the timeAlignmentTimer, associated with the TAG containing the serving cell on which the HARQ feedback is to be transmitted, is stopped or expired; or - if the HARQ feedback is disabled for the corresponding HARQ process: - if harq-FeedbackEnablingforSPSactive is configured and the transmission is the first SPS PDSCH transmission after SPS activation: - indicate the generated positive or negative acknowledgement for this TB to the physical layer. - else: - do not indicate the generated positive or negative acknowledgement to the physical layer. - else: - indicate the generated positive or negative acknowledgement for this TB to the physical layer. The MAC entity shall ignore NDI received in all downlink assignments on PDCCH for its Temporary C-RNTI when determining if NDI on PDCCH for its C-RNTI has been toggled compared to the value in the previous transmission. NOTE 1: When the MAC entity is configured with more than one serving cell, UE behaviors for storing data to the soft buffer is specified in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [2]. NOTE 2: If the MAC entity receives a retransmission with a TB size different from the last valid TB size signalled for this TB, the UE behavior is left up to UE implementation. | 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.2 |
3,483 | 5.2.27.2.3 Ntsctsf_TimeSynchronization_ConfigUpdate operation | Service operation name: Ntsctsf_TimeSynchronization_ConfigUpdate Description: Authorize the request and forward the request to update the time synchronization configuration. Inputs, Required: PTP instance reference. Inputs, Optional: List of UE identities (SUPIs) to be added to the time synchronization configuration. List of UE identities (SUPIs) to be removed from the time synchronization configuration. (g)PTP grandmaster enabled, grandmaster priority, Time Domain, Temporary Validity Condition, clock quality detail level, clock quality acceptance criteria as described in Table 4.15.9.3-1. Outputs, Required: Operation execution result indication. Outputs, Optional: None. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.27.2.3 |
3,484 | 4.3.2.1 Xn User Plane | The Xn User plane (Xn-U) interface is defined between two NG-RAN nodes. The user plane protocol stack on the Xn interface is shown in Figure 4.3.2.1-1. The transport network layer is built on IP transport and GTP-U is used on top of UDP/IP to carry the user plane PDUs. Figure 4.3.2.1-1: Xn-U Protocol Stack Xn-U provides non-guaranteed delivery of user plane PDUs and supports the following functions: - Data forwarding; - Flow control. Further details of Xn-U can be found in TS 38.420[ NG-RAN; Xn general aspects and principles ] [17]. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 4.3.2.1 |
3,485 | 5.8.15.3 Selection and reselection of NR sidelink U2N Relay UE | A UE capable of NR sidelink U2N Remote UE operation that is configured by upper layers to search for a NR sidelink U2N Relay UE shall: 1> if the UE has no serving cell; or 1> if the RSRP measurement of the cell on which the UE camps (for L2 and L3 U2N Remote UE in RRC_IDLE or RRC_INACTIVE)/ the PCell (for L3 U2N Remote UE in RRC_CONNECTED) is below threshHighRemote within sl-RemoteUE-Config: 2> if the UE does not have a selected NR sidelink U2N Relay UE; or 2> if the UE has a selected NR sidelink U2N Relay UE, and SL-RSRP of the currently selected NR sidelink U2N Relay UE is available and is below sl-RSRP-Thresh; or 2> if the UE has a selected NR sidelink U2N Relay UE, and SL-RSRP of the currently selected NR sidelink U2N Relay UE is not available, and SD-RSRP of the currently selected U2N Relay UE is below sl-RSRP-Thresh; or NOTE 1: U2N Remote UE uses SL-RSRP measurements for relay reselection trigger evaluation when there is data transmission from U2N Relay UE to U2N Remote UE, and it is left to UE implementation whether to use SL-RSRP or SD-RSRP for relay reselection trigger evaluation in case of no data transmission from U2N Relay UE to U2N Remote UE. If SD-RSRP is used, the discovery procedure will be performed between the U2N Remote UE and the selected U2N Relay UE. 2> if the UE has a selected NR sidelink U2N Relay UE, and upper layers indicate not to use the currently selected NR sidelink U2N Relay UE; or 2> if the UE has a selected NR sidelink U2N Relay UE, and upper layers request the release of the PC5-RRC connection; or 2> if the UE has a selected NR sidelink U2N Relay UE, and sidelink radio link failure is detected on the PC5-RRC connection with the current U2N Relay UE as specified in clause 5.8.9.3: 3> perform NR sidelink discovery procedure as specified in clause 5.8.13 in order to search for candidate NR sidelink U2N Relay UEs; 4> when evaluating the one or more detected NR sidelink U2N Relay UEs, apply layer 3 filtering as specified in 5.5.3.2 across measurements that concern the same U2N Relay UE ID and using the sl-FilterCoefficientRSRP in SIB12 (if in RRC_IDLE/INACTIVE), the sl-FilterCoefficientRSRP in sl-ConfigDedicatedNR (if in RRC_CONNECTED) or the preconfigured sl-FilterCoefficientRSRP as defined in 9.3 (out of coverage), before using the SD-RSRP measurement results; 4> consider a candidate NR sidelink U2N Relay UE for which SD-RSRP exceeds sl-RSRP-Thresh by sl-HystMin has met the AS criteria; 3> if the UE detects any suitable NR sidelink U2N Relay UE(s): 4> consider one of the available suitable NR sidelink U2N relay UE(s) can be selected; NOTE 2: A candidate NR sidelink U2N Relay UE which meets all AS layer criteria defined in 5.8.15.3 and higher layer criteria defined in TS 23.304[ Proximity based Services (ProSe) in the 5G System (5GS) ] [65] can be regarded as suitable NR sidelink U2N Relay UE by the NR sidelink U2N Remote UE. If multiple suitable NR sidelink U2N Relay UEs are available, it is up to Remote UE implementation to choose one NR sidelink U2N Relay UE. The details of the interaction with upper layers are up to UE implementation. NOTE 3: For L2 U2N Remote UEs in RRC_IDLE/INACTIVE and L3 U2N Remote UEs, the cell (re)selection procedure and relay (re)selection procedure run independently. If both suitable cells and suitable NR sidelink U2N Relay UEs are available, it is up to NR sidelink U2N Remote UE implementation to select either a cell or a NR sidelink U2N Relay UE. Furthermore, L3 U2N Remote UE's selection on both cell and NR sidelink U2N Relay UE is also based on UE implementation. 3> else: 4> consider no NR sidelink U2N Relay UE to be selected. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.8.15.3 |
3,486 | 4.4.2.2 Average number of active UEs on the UL per QCI | a) This measurement provides the average number of UEs that have DTCH data queued on the uplink. The measurement is split into subcounters per E-RAB QoS level (QCI). For an eNodeB serving one or more RNs, the measurement refers to the number of active UEs connected directly to the eNodeB, excluding RNs. The measurement is also applicable to RNs. b) SI c) This measurement is obtained according to the definition in 3GPP TS 36.314[ Evolved Universal Terrestrial Radio Access (E-UTRA); Layer 2 - Measurements ] [11]. Separate counters are maintained for each QCI. d) Each measurement is an integer value. The number of measurements is equal to the number of QCIs plus a possible sum value identified by the .sum suffix. e) The measurement name has the form DRB.UEActiveUl.QCI where QCI identifies the E-RAB level quality of service class. f) EUtranCellFDD EUtranCellTDD g) Valid for packet switched traffic h) EPS | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.4.2.2 |
3,487 | 6.5.1.6 Abnormal cases on the network side | The following abnormal cases can be identified: a) UE initiated PDN connectivity request for an already existing PDN connection: If the network receives a PDN CONNECTIVITY REQUEST message with the same combination of APN and PDN type as an already existing PDN connection and: - the information elements in the PDN CONNECTIVITY REQUEST message do not differ from the ones received within the previous PDN CONNECTIVITY REQUEST message, and the MME has not received the ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT message from UE, the network shall resend the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message and continue the previous procedure. - one or more information elements in the PDN CONNECTIVITY REQUEST message differ from the ones received within the previous PDN CONNECTIVITY REQUEST message, and multiple PDN connections for a given APN are not allowed, the network may deactivate the existing EPS bearer contexts for the PDN connection locally without notification to the UE and proceed with the requested PDN connectivity procedure or may reject this PDN connectivity procedure including the ESM cause #55 "multiple PDN connections for a given APN not allowed", in the PDN CONNECTIVITY REJECT message. If the network receives a PDN CONNECTIVITY REQUEST message with request type "emergency" and the MME has not received the ACTIVATE DEFAULT EPS BEARER CONTEXT ACCEPT message from UE for the previous PDN connectivity request for emergency bearer services, the network shall resend the ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message and continue the previous procedure. If there is already a PDN connection for emergency bearer services existing, the MME shall reject the request with ESM cause #55 "multiple PDN connections for a given APN not allowed" or deactivate the existing EPS bearer contexts for the PDN connection locally without notification to the UE and proceed with the requested PDN connectivity procedure. b) UE initiated PDN connectivity request with request type "handover" for a PDN connection that does not exist: If the network receives a PDN CONNECTIVITY REQUEST message for either a default APN or a specific APN with request type set to "handover" and the MME does not have any information about that PDN connection, then MME shall reject the PDN connectivity request procedure including the ESM cause #54 "PDN connection does not exist", in the PDN CONNECTIVITY REJECT message. c) ESM information not received: If the ESM information transfer flag in the PDN CONNECTIVITY REQUEST message has been set and the ESM information is not received before the final expiry of timer T3489 as described in clause 6.6.1.2.6, the MME shall reject the PDN connectivity request procedure including the ESM cause #53 "ESM information not received", in the PDN CONNECTIVITY REJECT message. d) Additional UE initiated PDN connectivity request received from a UE that is attached for emergency bearer services: The MME shall reject the request with ESM cause #31 "request rejected, unspecified". e) A PDN CONNECTIVITY REQUEST message with request type "handover of emergency bearer services" received from a UE and the MME does not have any information about a P-GW currently providing emergency bearer services for the UE or the MME is not configured with an address of a P-GW in the MME emergency configuration data: MME shall reject the PDN connectivity request procedure including the ESM cause #54 "PDN connection does not exist", in the PDN CONNECTIVITY REJECT message. f) Additional UE initiated PDN connectivity request received from a UE that is attached for access to RLOS: The MME shall reject the request with ESM cause #31 "request rejected, unspecified". g) PDN CONNECTIVITY REQUEST message received from a UE which is in a location where the PLMN is not allowed to operate If the MME determines that the UE is in a location where the PLMN is not allowed to operate, the MME discards the message. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.5.1.6 |
3,488 | C.2.2 Verification of sequence number freshness in the USIM | The USIM shall maintain an array of a previously accepted sequence number components: SEQMS (0), SEQMS (1),… SEQMS (a-1). The initial sequence number value in each array element shall be zero. To verify that the received sequence number SQN is fresh, the USIM shall compare the received SQN with the sequence number in the array element indexed using the index value contained in SQN, i.e. with the array entry SEQMS (i) where i = is the index value. (a) If SEQ > SEQMS (i) the USIM shall consider the sequence number to be guaranteed fresh and subsequently shall set SEQMS (i) to SEQ. (b) If SEQ ≤ SEQMS (i) the USIM shall generate a synchronisation failure message using the highest previously accepted sequence number anywhere in the array, i.e. SQNMS. The USIM shall also be able to put a limit L on the difference between SEQMS and a received sequence number component SEQ. If such a limit L is applied then, before verifying the above conditions (a) and (b), the sequence number shall only be accepted by the USIM if SEQMS - SEQ < L. If SQN can not be accepted then the USIM shall generate a synchronisation failure message using SQNMS. | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | C.2.2 |
3,489 | 7.8.1.1 Minimum requirements | The throughput shall be ≥ 95% of the maximum throughput of the reference measurement channels as specified in Annexes A.2.2, A.2.3 and A.3.2 (with one sided dynamic OCNG Pattern OP.1 FDD/TDD for the DL-signal as described in Annex A.5.1.1/A.5.2.1) with parameters specified in Table 7.8.1.1 for the specified wanted signal mean power in the presence of two interfering signals. For operating bands with an unpaired DL part (as noted in Table 5.5-1), the requirements only apply for carriers assigned in the paired part. Table 7.8.1.1-1: Wide band intermodulation For the UE which supports inter band CA configuration in Table 7.3.1-1A, Pinterferer1 and Pinterferer2 powers defined in Table 7.8.1.1-1 are increased by the amount given by ΔRIB,c in Table 7.3.1-1A. | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 7.8.1.1 |
3,490 | 8.5.3 Call control | a) If the message is a SETUP message, a RELEASE COMPLETE message with cause # 96 "invalid mandatory information" shall be returned. b) If the message is a DISCONNECT message, a RELEASE message shall be returned with cause value # 96 "invalid mandatory information" and subclause 5.4. "call clearing" applies as normal. c) If the message is a RELEASE message, a RELEASE COMPLETE message shall be returned with cause value # 96 "invalid mandatory information". d) If the message is a RELEASE COMPLETE message, it shall be treated as a normal RELEASE COMPLETE message. e) If the message is a HOLD REJECT or RETRIEVE REJECT message, it shall be treated as a normal HOLD REJECT or RETRIEVE REJECT message. f) If the message is a STATUS message and received by the network, a RELEASE COMPLETE message may be returned with cause value # 96 "invalid mandatory information". | 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 | 8.5.3 |
3,491 | 20.5a.8 MBMS-Data-Transfer-Stop AVP | The MBMS-Data-Transfer-Stop AVP (AVP code 930) is of type Unsigned64. This value indicates the time in seconds for the release of resources relative to 00:00:00 on 1 January 1900 (calculated as continuous time without leap seconds and traceable to a common time reference) where binary encoding of the integer part is in the first 32 bits and binary encoding of the fraction part in the last 32 bits. The fraction part is expressed with a granularity of 1 /2**32 second. This AVP is only valid for E-UTRAN access type. | 3GPP TS 29.061 | Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) | CT WG3 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 20.5a.8 |
3,492 | 5.2.2 Network selection | In order to determine to which PLMN to attempt registration, the UE performs network selection. The network selection procedure comprises two main parts, PLMN selection and access network selection. The requirements for the PLMN selection are specified in TS 22.011[ Service accessibility ] [25] and the procedures are in TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [17]. The access network selection part for the 3GPP access networks is specified in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [30] for E-UTRAN and in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [27] for the NR. The network selection for the Disaster Roaming is described in TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [17] and TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [47]. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.2 |
3,493 | 5.43 Support for 5G Satellite Backhaul 5.43.1 General | Satellite may be used as part of the backhaul between (R)AN and 5GC. The 5G System supports to report of usage of satellite backhaul as described in clause 5.43.2. For some deployments, UPF may be deployed on the satellite. In these cases, edge computing or local switch via UPF deployed on the satellite may be performed as described in clauses 5.43.2 and 5.43.3. Deployments with satellite backhaul and edge computing with UPF on the ground is supported as described in clause 5.13, i.e. without satellite backhaul specific requirements. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.43 |
3,494 | 5.2.6.11.2 Nnef_ServiceParameter_Create operation | Service operation name: Nnef_ServiceParameter_Create Description: The consumer stores service specific parameters in the UDR via the NEF. Inputs, Required: Service Descriptor (e.g. the combination of DNN and S-NSSAI, an AF-Service-Identifier or an External Application Identifier) Inputs, Optional: Service Parameters and Target UE identifiers (e.g. the address (IP or Ethernet) of the UE if available, GPSI if available, External Group Identifier if available), "PLMN ID(s) of inbound roamers", subscribedEvents, notificationDestination. If identifiers of target UE(s) or a group of UEs or "PLMN ID(s) of inbound roamers" are not provided, then the Service Parameters shall correspond to any UEs of the PLMN of the NEF using the service identified by the Service Description. Outputs, Required: Transaction Reference ID, operation execution result indication. Outputs, Optional: None. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.6.11.2 |
3,495 | 4.7.5.2.5 Abnormal cases in the MS | The MS shall proceed as follows: 1) If the combined routing area update was successful for GPRS services only and the ROUTING AREA UPDATE ACCEPT message contained a cause value not treated in subclause 4.7.5.2.3.2 or the GMM Cause IE is not included in the message, the MS shall proceed as follows: a) The MS shall stop timer T3330 if still running, and shall enter state MM IDLE. The routing area updating attempt counter shall be incremented; b) If the routing area updating attempt counter is less than 5, and the stored RAI is equal to the RAI of the current serving cell and the GMM update status is equal to GU1 UPDATED: - the MS shall keep the GMM update status GU1 UPDATED and changes state to GMM-REGISTERED.ATTEMPTING-TO-UPDATE-MM. The MS shall start timer T3311. When timer T3311 expires the combined routing area update procedure indicating "combined RA/LA updating with IMSI attach" is triggered again; and c) If the routing area updating attempt counter is greater than or equal to 5: - the MS shall start timer T3302 and shall change to state GMM-REGISTERED.ATTEMPTING-TO-UPDATE-MM; and - a GPRS MS operating in MS operation mode A shall then proceed with appropriate MM specific procedure; a GPRS MS operating in MS operation mode B may then proceed with appropriate MM specific procedures. The MM sublayer shall act as in network operation mode II or as long as the combined GMM procedures are not successful and no new RA is entered; 2) Combined routing area updating and paging for non-GPRS services procedure collision If the MS receives a paging for non-GPRS services before the routing area updating procedure has been completed, the MS shall progress the routing area updating procedure and respond to the paging for non-GPRS services when the MS has completed the routing area updating procedure or aborted the procedure for other reasons. The MS shall return to MM state MM IDLE and proceed with the appropriate MM specific procedures to respond to the paging for non-GPRS services; and 3) otherwise, the abnormal cases specified in subclause 4.7.5.1.5 apply with the following modification. If the GPRS routing area updating attempt counter is incremented according to subclause 4.7.5.1.5 the next actions depend on the Location Area Identities (stored on SIM/USIM and the one of the current serving cell) and the value of the routing area updating attempt counter. - if the update status is U1 UPDATED, and the stored LAI is equal to the one of the current serving cell and the routing area updating attempt counter is smaller than 5, then the mobile station shall keep the update status to U1 UPDATED, the new MM state is MM IDLE substate NORMAL SERVICE; - if the routing area updating attempt counter is smaller than 5 and, additionally, the update status is different from U1 UPDATED or the stored LAI is different from the one of the current serving cell, the mobile station shall delete any LAI, TMSI, ciphering key sequence number stored in the SIM/USIM and list of equivalent PLMNs and set the update status to U2 NOT UPDATED. The MM state remains MM LOCATION UPDATING PENDING; or - if the routing area updating attempt counter is greater or equal to 5, the mobile station shall delete any LAI, TMSI, ciphering key sequence number stored in the SIM/USIM and the list of equivalent PLMNs, and shall set the update status to U2 NOT UPDATED. A GPRS MS operating in MS operation mode A shall then proceed with appropriate MM specific procedure; a GPRS MS operating in MS operation mode B may then proceed with appropriate MM specific procedures. The MM sublayer shall act as in network operation mode II as long as the combined GMM procedures are not successful and no new RA is entered. The new MM state is MM IDLE substate ATTEMPTING TO UPDATE or optionally MM IDLE substate PLMN SEARCH in order to perform a PLMN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [14]. | 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.2.5 |
3,496 | 5.30.2.9 SNPN connectivity for UEs with credentials owned by Credentials Holder 5.30.2.9.1 General | SNPNs may support UE access using credentials owned by a Credentials Holder separate from the SNPN. In this case the Session Management procedures (i.e. PDU Sessions) terminate in an SMF in the SNPN. When an SNPN supports UE access using credentials assigned by a Credentials Holder separate from the SNPN, it is assumed that is supported homogeneously within the whole SNPN. Credentials Holder using AAA Server for primary authentication and authorization is described in clause 5.30.2.9.2 and Credentials Holder using AUSF and UDM for primary authentication and authorization is described in clause 5.30.2.9.3. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.30.2.9 |
3,497 | 5.3.3 RRC connection establishment 5.3.3.1 General | Figure 5.3.3.1-1: RRC connection establishment, successful Figure 5.3.3.1-2: RRC connection establishment, network reject The purpose of this procedure is to establish an RRC connection. RRC connection establishment involves SRB1 establishment. The procedure is also used to transfer the initial NAS dedicated information/ message from the UE to the network. The network applies the procedure e.g.as follows: - When establishing an RRC connection; - When UE is resuming or re-establishing an RRC connection, and the network is not able to retrieve or verify the UE context. In this case, UE receives RRCSetup and responds with RRCSetupComplete. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.3 |
3,498 | 28.16.5 NAI format for SUCI containing a GLI | The SUCI containing a GLI shall take the form of a Network Access Identifier (NAI). The NAI format of the SUCI shall have the form username@realm as specified in clause 2.2 of IETF RFC 7542 [126], where the realm part shall be identical to the realm part of the SUPI (see clause 28.16.2). The username part of the NAI shall be encoded as specified for the null-scheme in clause 28.7.3, i.e. it shall take the following form: type2.rid0.schid0.userid<username> where the username shall be encoded as the username part of the SUPI (see clause 28.16.2). | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 28.16.5 |
3,499 | 5.5.4.16 CondEvent T1 (Time measured at UE is within a duration from threshold) | The UE shall: 1> consider the entering condition for this event to be satisfied when condition T1-1, as specified below, is fulfilled; 1> consider the leaving condition for this event to be satisfied when condition T1-2, as specified below, is fulfilled; Inequality T1-1 (Entering condition) Inequality T1-2 (Leaving condition) The variables in the formula are defined as follows: Mt is the time measured at UE. Thresh1 is the threshold parameter for this event (i.e. t1-Threshold as defined within reportConfigNR for this event). Duration is the duration parameter for this event (i.e. duration as defined within reportConfigNR for this event). Mt is expressed in ms. Thresh1 is expressed in the same unit as Mt. Duration is expressed in the same unit as Mt. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.5.4.16 |
3,500 | – MeasResults | The IE MeasResults covers measured results for intra-frequency, inter-frequency, inter-RAT mobility and measured results for NR sidelink communication/discovery. MeasResults information element -- ASN1START -- TAG-MEASRESULTS-START MeasResults ::= SEQUENCE { measId MeasId, measResultServingMOList MeasResultServMOList, measResultNeighCells CHOICE { measResultListNR MeasResultListNR, ..., measResultListEUTRA MeasResultListEUTRA, measResultListUTRA-FDD-r16 MeasResultListUTRA-FDD-r16, sl-MeasResultsCandRelay-r17 OCTET STRING -- Contains PC5 SL-MeasResultListRelay-r17 } OPTIONAL, ..., [[ measResultServFreqListEUTRA-SCG MeasResultServFreqListEUTRA-SCG OPTIONAL, measResultServFreqListNR-SCG MeasResultServFreqListNR-SCG OPTIONAL, measResultSFTD-EUTRA MeasResultSFTD-EUTRA OPTIONAL, measResultSFTD-NR MeasResultCellSFTD-NR OPTIONAL ]], [[ measResultCellListSFTD-NR MeasResultCellListSFTD-NR OPTIONAL ]], [[ measResultForRSSI-r16 MeasResultForRSSI-r16 OPTIONAL, locationInfo-r16 LocationInfo-r16 OPTIONAL, ul-PDCP-DelayValueResultList-r16 UL-PDCP-DelayValueResultList-r16 OPTIONAL, measResultsSL-r16 MeasResultsSL-r16 OPTIONAL, measResultCLI-r16 MeasResultCLI-r16 OPTIONAL ]], [[ measResultRxTxTimeDiff-r17 MeasResultRxTxTimeDiff-r17 OPTIONAL, sl-MeasResultServingRelay-r17 OCTET STRING OPTIONAL, -- Contains PC5 SL-MeasResultRelay-r17 ul-PDCP-ExcessDelayResultList-r17 UL-PDCP-ExcessDelayResultList-r17 OPTIONAL, coarseLocationInfo-r17 OCTET STRING OPTIONAL ]], [[ altitudeUE-r18 Altitude-r18 OPTIONAL ]] } MeasResultServMOList ::= SEQUENCE (SIZE (1..maxNrofServingCells)) OF MeasResultServMO MeasResultServMO ::= SEQUENCE { servCellId ServCellIndex, measResultServingCell MeasResultNR, measResultBestNeighCell MeasResultNR OPTIONAL, ... } MeasResultListNR ::= SEQUENCE (SIZE (1..maxCellReport)) OF MeasResultNR MeasResultNR ::= SEQUENCE { physCellId PhysCellId OPTIONAL, measResult SEQUENCE { cellResults SEQUENCE{ resultsSSB-Cell MeasQuantityResults OPTIONAL, resultsCSI-RS-Cell MeasQuantityResults OPTIONAL }, rsIndexResults SEQUENCE{ resultsSSB-Indexes ResultsPerSSB-IndexList OPTIONAL, resultsCSI-RS-Indexes ResultsPerCSI-RS-IndexList OPTIONAL } OPTIONAL }, ..., [[ cgi-Info CGI-InfoNR OPTIONAL ]] , [[ choCandidate-r17 ENUMERATED {true} OPTIONAL, choConfig-r17 SEQUENCE (SIZE (1..2)) OF CondTriggerConfig-r16 OPTIONAL, triggeredEvent-r17 SEQUENCE { timeBetweenEvents-r17 TimeBetweenEvent-r17 OPTIONAL, firstTriggeredEvent ENUMERATED {condFirstEvent, condSecondEvent} OPTIONAL } OPTIONAL ]] } MeasResultListEUTRA ::= SEQUENCE (SIZE (1..maxCellReport)) OF MeasResultEUTRA MeasResultEUTRA ::= SEQUENCE { eutra-PhysCellId PhysCellId, measResult MeasQuantityResultsEUTRA, cgi-Info CGI-InfoEUTRA OPTIONAL, ... } MultiBandInfoListEUTRA ::= SEQUENCE (SIZE (1..maxMultiBands)) OF FreqBandIndicatorEUTRA MeasQuantityResults ::= SEQUENCE { rsrp RSRP-Range OPTIONAL, rsrq RSRQ-Range OPTIONAL, sinr SINR-Range OPTIONAL } MeasQuantityResultsEUTRA ::= SEQUENCE { rsrp RSRP-RangeEUTRA OPTIONAL, rsrq RSRQ-RangeEUTRA OPTIONAL, sinr SINR-RangeEUTRA OPTIONAL } ResultsPerSSB-IndexList::= SEQUENCE (SIZE (1..maxNrofIndexesToReport2)) OF ResultsPerSSB-Index ResultsPerSSB-Index ::= SEQUENCE { ssb-Index SSB-Index, ssb-Results MeasQuantityResults OPTIONAL } ResultsPerCSI-RS-IndexList::= SEQUENCE (SIZE (1..maxNrofIndexesToReport2)) OF ResultsPerCSI-RS-Index ResultsPerCSI-RS-Index ::= SEQUENCE { csi-RS-Index CSI-RS-Index, csi-RS-Results MeasQuantityResults OPTIONAL } MeasResultServFreqListEUTRA-SCG ::= SEQUENCE (SIZE (1..maxNrofServingCellsEUTRA)) OF MeasResult2EUTRA MeasResultServFreqListNR-SCG ::= SEQUENCE (SIZE (1..maxNrofServingCells)) OF MeasResult2NR MeasResultListUTRA-FDD-r16 ::= SEQUENCE (SIZE (1..maxCellReport)) OF MeasResultUTRA-FDD-r16 MeasResultUTRA-FDD-r16 ::= SEQUENCE { physCellId-r16 PhysCellIdUTRA-FDD-r16, measResult-r16 SEQUENCE { utra-FDD-RSCP-r16 INTEGER (-5..91) OPTIONAL, utra-FDD-EcN0-r16 INTEGER (0..49) OPTIONAL } } MeasResultForRSSI-r16 ::= SEQUENCE { rssi-Result-r16 RSSI-Range-r16, channelOccupancy-r16 INTEGER (0..100) } MeasResultCLI-r16 ::= SEQUENCE { measResultListSRS-RSRP-r16 MeasResultListSRS-RSRP-r16 OPTIONAL, measResultListCLI-RSSI-r16 MeasResultListCLI-RSSI-r16 OPTIONAL } MeasResultListSRS-RSRP-r16 ::= SEQUENCE (SIZE (1.. maxCLI-Report-r16)) OF MeasResultSRS-RSRP-r16 MeasResultSRS-RSRP-r16 ::= SEQUENCE { srs-ResourceId-r16 SRS-ResourceId, srs-RSRP-Result-r16 SRS-RSRP-Range-r16 } MeasResultListCLI-RSSI-r16 ::= SEQUENCE (SIZE (1.. maxCLI-Report-r16)) OF MeasResultCLI-RSSI-r16 MeasResultCLI-RSSI-r16 ::= SEQUENCE { rssi-ResourceId-r16 RSSI-ResourceId-r16, cli-RSSI-Result-r16 CLI-RSSI-Range-r16 } UL-PDCP-DelayValueResultList-r16 ::= SEQUENCE (SIZE (1..maxDRB)) OF UL-PDCP-DelayValueResult-r16 UL-PDCP-DelayValueResult-r16 ::= SEQUENCE { drb-Id-r16 DRB-Identity, averageDelay-r16 INTEGER (0..10000), ... } UL-PDCP-ExcessDelayResultList-r17 ::= SEQUENCE (SIZE (1..maxDRB)) OF UL-PDCP-ExcessDelayResult-r17 UL-PDCP-ExcessDelayResult-r17 ::= SEQUENCE { drb-Id-r17 DRB-Identity, excessDelay-r17 INTEGER (0..31), ... } TimeBetweenEvent-r17 ::= INTEGER (0..1023) -- TAG-MEASRESULTS-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
Subsets and Splits
No saved queries yet
Save your SQL queries to embed, download, and access them later. Queries will appear here once saved.