Search is not available for this dataset
doc_id
int64 1
6.72k
⌀ | Section
stringlengths 5
247
⌀ | Content
stringlengths 501
147k
⌀ | Source
stringclasses 456
values | Document Title
stringclasses 22
values | Working Group
stringclasses 21
values | Series Subject
stringclasses 9
values | Subclause
stringlengths 1
13
⌀ |
|---|---|---|---|---|---|---|---|
1,601 | O.4.2 Radio environment capability | The purpose of the radio environment capability is to provide information about the current radio environment of the MS. The radio environment capability information element is coded as shown in figure O.3/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table O.3/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The radio environment capability is a type 1 information element with 1 octet length. Figure O.3/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Radio environment capability contents Table O.3/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Radio environment capability contents | 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 | O.4.2 |
1,602 | 4.15.4.5.2 Information flow for subscription to UPF event exposure service for certain UE(s) via SMF | Figure 4.15.4.5.2-1: Subscription to UPF event exposure service for certain UE(s) via SMF In the case of a group of UEs, the UPF event consumer (e.g. NWDAF) first issues an Nnrf_NFDiscovery_Request service operation to find the UDM providing the target Group ID and gets the NF profile of the UDM serves this group. Then, NWDAF obtains the list of SUPIs that correspond to the Group ID from UDM using Nudm_SDM_Get NOTE 1: It is assumed that all members of a Group ID belong to the same UDM. Then, for each SUPI: 1. The UPF event consumer (e.g. NWDAF) invokes Nudm_UECM_Get service operation to retrieve the appropriate SMF by providing UE ID, DNN, S-NSSAI and NF type = SMF. 2. The UDM provides a Nudm_UECM_Get response with the corresponding SMF. 3. The UPF event consumer sends the Nsmf_EventExposure Subscription request to the SMF to subscribe to UPF data, including the following information: - Notification Target Address (UPF event consumer address), Notification Correlation Information. - Indication of UPF Event Exposure Service and Target subscription UPF Event Id. - Event Filter Information: S-NSSAI, DNN, DNAI,UPF Id, Traffic Description for the target traffic (e.g. Application Id), Area of Interest, SSID/BSSID. - Target of Event Reporting: a UE. - Reporting suggestion information. - Target Subscription information: Type of Measurement and granularity of the information requested. If the consumer is NWDAF and the analytic filter information includes application server IP address/FQDN, the NWDAF may need to first obtain the DNAI from NEF as described in steps 2 and 3 in Figure 4.15.4.5.3-1. 4. The SMF selects the PDU session(s) and the UPFs it has to send the request to. The SMF sends the request to the UPF including the UPF event consumer address, Notification Correlation Information, Event Filter Information, Reporting suggestion information, Target of Event Reporting and Target Subscription Information as required. Target of Event Reporting is a certain UE. The interaction mechanism used between SMF and UPF depends on UPF exposure event and which mechanism applies for each event as described in clause 5.2.26.2.1. For some events, the SMF shall contact UPF (4a) with N4 Session Modification with PFCP (TS 29.244[ Interface between the Control Plane and the User Plane nodes ] [69]), for other events (4b) with Nupf_event exposure subscribe request (as defined in clause 5.2.26.2.3). NOTE 2: Some events can require SMF interacts with RAN at this stage. 5. Per Reporting suggestion information (if available), the UPF sends the locally collected UPF data by invoking Nupf_EventExposure_Notify service operation to the UPF event consumer. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.15.4.5.2 |
1,603 | 4.3.1 UE's usage setting | The UE's usage setting defined in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15] applies to voice capable UEs in 5GS and indicates whether the UE has preference for voice services over data services or vice-versa, where: a) voice services include IMS voice; and b) data services include any kind of user data transfer without a voice media component. The UE's usage setting can be set to: a) "voice centric"; or b) "data centric". If the UE is capable of S1 mode, there is a single UE's usage setting at the UE which applies to both 5GS and EPS. | 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.3.1 |
1,604 | 17.5.4 Registration procedure | The registration procedure occurs when the GGSN indicates the BM-SC that it would like to receive session attributes and data for a particular multicast MBMS bearer service, in order to be distributed further downstream. A corresponding MBMS Bearer Context is established as a result between the GGSN and the BM-SC. Figure 29: MBMS Registration procedure 1. When the GGSN has no MBMS Bearer Context for an MBMS bearer service and the GGSN receives an MBMS Registration from an SGSN for this MBMS bearer service, or when the first MBMS UE Context is created in the GGSN for an MBMS bearer service for which the GGSN has no MBMS Bearer Context, the GGSN sends a AAR message (containing the IP multicast address and the APN) to the BM-SC. 2. Upon reception of an AAR from a GGSN, the BM-SC adds the identifier of the GGSN to the "list of downstream nodes" parameter in its MBMS Bearer Context and responds with an AAA message (containing TMGI, and Required Bearer Capabilities). If the MBMS Bearer Context is in the ‘Active’ state, the BM-SC initiates the Session Start procedure with the GGSN, as described in clause 17.5.2 "Session Start Procedure". | 3GPP TS 29.061 | Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) | CT WG3 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 17.5.4 |
1,605 | 10.11.2 MR-DC with 5GC | The secondary RAT data volume reporting function is used to report the data volume of secondary RAT to the 5GC. In MR-DC with 5GC, if configured, the MN reports the uplink and downlink data volumes of used secondary RAT resources to the 5GC as specified in TS 23.501[ System architecture for the 5G System (5GS) ] [11]. Configuration for reporting of secondary RAT data volume may happen separately for NR and E-UTRA. Secondary RAT data volume reporting indicates the secondary RAT type. For each PDU session, it contains data volumes consumed for the whole PDU Session, or for selected QoS flow, or both. Periodic reporting is performed by periodically sending the Secondary RAT Data Usage Report messages to the 5GC. The data volume is counted by the node hosting PDCP. Downlink data volume is counted in bytes of SDAP SDUs successfully delivered to the UE (for RLC AM) or transmitted to the UE (for RLC UM). Uplink data volume is counted in bytes of SDAP SDUs received by the node hosting PDCP. Forwarded packets shall not be counted when PDCP entity is relocated. When PDCP duplication is activated, packets shall be counted only once. Figure 10.11.2-1: Secondary RAT data volume periodic reporting - MR-DC with 5GC Figure 10.11.2-1 shows an example signalling flow for secondary RAT data volume periodic reporting: 1. For SN terminated bearers, the SN sends the Secondary RAT Data Usage Report message to the MN and includes the data volumes of used secondary RAT resources for PDU Sessions or selected QoS flows or both mapped to SN-terminated bearers. If periodic reporting is configured, then the SN periodically sends the Secondary RAT Data Usage Report message to the MN and includes the data volumes of used radio resources. 2. The MN sends the Secondary RAT Data Usage Report message to the 5GC to provide information on the used radio resources. NOTE: The Secondary RAT Data Usage Report message sent by the MN may also include secondary RAT data volumes of used secondary RAT resources for MN terminated bearers. | 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.11.2 |
1,606 | 4.7.3.1.4b Attach for initiating a PDN connection for emergency bearer services not accepted by the network (UTRAN Iu mode only) | If the network cannot accept the attach request for initiating a PDN connection for emergency bearer services with attach type not set to "emergency attach", the MS shall perform the procedures as described in subclause 4.7.3.1.4. Then if the MS is in the same selected PLMN where the last attach request was attempted, the MS shall: a) inform the upper layers of the failure of the procedure; or NOTE 1: This can result in the upper layers requesting establishment of a CS emergency call (if not already attempted in the CS domain) or other implementation specific mechanisms, e.g. procedures specified in 3GPP TS 24.229[ IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 ] [95] that can result in the emergency call being attempted to another IP-CAN. b) attempt GPRS attach for emergency bearer services. If the attach request for initiating a PDN connection for emergency bearer services with attach type not set to "emergency attach" fails due to abnormal case a) in subclause 4.7.3.1.5, the MS shall perform the procedures as described in subclause 4.7.3.1.5 and inform the upper layers of the failure to access the network. NOTE 2: This can result in the MS attempting a CS emergency call (if not already attempted in the CS domain) or other implementation specific mechanisms, e.g. procedures specified in 3GPP TS 24.229[ IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 ] [95] that can result in the emergency call being attempted to another IP-CAN. If the attach request for initiating a PDN connection for emergency bearer services with attach type not set to "emergency attach" fails due to abnormal cases b), c) or d) in subclause 4.7.3.1.5, the MS shall perform the procedures as described in subclause 4.7.3.1.5. Then if the MS is in the same selected PLMN where the last attach request was attempted, the MS shall: a) inform the upper layers; or NOTE 3: This can result in the MS attempting a CS emergency call (if not already attempted in the CS domain) or other implementation specific mechanisms, e.g. procedures specified in 3GPP TS 24.229[ IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 ] [95] that can result in the emergency call being attempted to another IP-CAN. b) attempt GPRS attach for emergency bearer services. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.7.3.1.4b |
1,607 | 4.15.6.8 Set a policy for a future AF session | Figure 4.15.6.8-1: Set a policy for a future AF session 1. The AF previously negotiated policy for background data transfer using the Procedure for future background data transfer as described in clause 4.16.7.2. 2. The AF requests that the previously negotiated policy for background data transfer be applied to a group of UE(s) or any UE, by invoking the Nnef_ApplyPolicy_Create service operation (AF Identifier, External Identifier or External Group Identifier, Background Data Transfer Reference ID). The Background Data Transfer Reference ID parameter identifies a previously negotiated transfer policy for background data transfer as defined in clause 4.16.7. The NEF assigns a Transaction Reference ID to the Nnef_ApplyPolicy_Create request. The NEF authorizes the AF request and stores the AF Identifier and the Transaction Reference ID. 3. The NEF invokes Nudm_SDM_Get (Identifier Translation, GPSI) to resolve the GPSI (External Identifier) to a SUPI or the NEF requests to resolve the External Group Identifier into the Internal Group Identifier using Nudm_SDM_Get (Group Identifier Translation, External Group Identifier). 4a. The NEF stores the AF request information in the UDR (Data Set = Application Data; Data Subset = Background Data Transfer, Data Key = Internal Group Identifier or SUPI). 4b. The NEF responds to the Nnef_ApplyPolicy_Create Request (Transaction Reference ID). 5. The PCF(s) that have subscribed to modifications of AF requests (Data Set = Application Data; Data Subset = Background Data Transfer, Data Key = Internal Group Identifier or SUPI) receive(s) a Nudr_DM_Notify notification of data change from the UDR. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.15.6.8 |
1,608 | 8.115 APN and Relative Capacity | The APN and Relative Capacity IE is coded as shown in Figure 8.115-1. Figure 8.115-1: APN and Relative Capacity The Relative Capacity represents the resources configured for the given APN as compared to the total resources of the target PGW, in percentage. It shall take binary coded integer values from 1 up to 100. Other values shall be considered as 0. The APN Length in octet '6' indicates the length of the APN field. The APN field, from octet 7 to 'm' shall be encoded as octet 5 to '(n+4)' defined in clause 8.6. | 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.115 |
1,609 | 4.15.9.5.2 5G access stratum time distribution status reporting to the UE | Figure 4.15.9.5.2-1: Procedure for reporting RAN timing synchronization status to subscribed UE 1. Creation or update of ASTI or PTP based time synchronization service (AF requested ASTI or PTP based time synchronization service is described in clauses 4.15.9.4 and 4.15.9.3; subscription based ASTI is described in clause 4.28.2.1) including in the request clock quality detail level indication and optionally the clock quality acceptance criteria. The clock quality level indication and optionally the clock quality acceptance criteria are sent to the NG-RAN and the UE reconnect indication is sent to the UE as described in clause 4.15.9.4. 2. The RAN node is pre-configured for the thresholds for each timing synchronization status attribute as described in clause 5.27.1.12 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If there is a change on its primary source so that the thresholds are exceeded or met again, the NG-RAN node indicates the status via SIB information as described in clause 5.27.1.12 in TS 23.501[ System architecture for the 5G System (5GS) ] [2]. 3. (When the UE is in RRC_INACTIVE or RRC_IDLE state): If supported by the UE and If the UE determines, based on the reading of SIB9 information as described in clause 5.27.1.12 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], a clock quality information update is available, and the AMF has provided the UE reconnection indication in step 10 of clause 4.15.9.4, the UE reconnects to the network as described in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [25]. 4. (When the UE is in RRC_CONNECTED state): The NG-RAN node notifies the UE providing clock quality information as configured in step 0 (i.e. sending clock quality metrics or acceptable/not acceptable indication) using unicast RRC signalling whenever the UE enters RRC_CONNECTED state and while the UE remains in RRC_CONNECTED, when any of the clock quality metrics or the acceptable/not acceptable indication for the UE changes. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.15.9.5.2 |
1,610 | 4.11.1.3.4 EPS to 5GS Mobility Registration Procedure (Idle) using N26 interface with AMF reallocation | During Idle state mobility registration procedure from EPS to 5GS, the initial AMF may select a new AMF based on S-NSSAIs associated with the established PDU Session, received in NAS Registration Request. Figure 4.11.1.3.4-1: EPS to 5GS mobility with AMF re-allocation for single-registration mode and N26 interface configuration 1. Step 1 to 7 of clause 4.11.1.3.3 in EPS to 5GS mobility using N26 interface is performed. 2. Step 3 to 4 of clause 4.2.2.2.3 in Registration with AMF reallocation procedure is performed with the difference that before the Network Slice selection the AMF needs to derive the S-NSSAI for the serving PLMN as described in clause 5.15.5.2.1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. 3. [Conditional] Initial AMF to MME: Context Acknowledge (failure cause) to MME according to TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13]. The initial AMF decides a new AMF needs to be reselected. The initial AMF sends a Context Acknowledge message with cause code indicating that the procedure is not successful. The MME shall continue as if Context Request was never received. 4. Step 6 to 7 of clause 4.2.2.2.3 in Registration with AMF reallocation procedure are performed. 5. After receiving the Registration Request message, the new AMF continues the registration from step 5 until step 18 of figure 4.11.1.3.3 (EPS to 5GS mobility using N26 procedure), which includes the UE context retrieved from old AMF. If the 5G security context is received from the initial AMF, the new AMF continues using that one instead of the mapped 5G security context retrieved from MME. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.11.1.3.4 |
1,611 | 5.3.7.5 Reception of the RRCReestablishment by the UE | The UE shall: 1> stop timer T301; 1> consider the current cell to be the PCell; 1> update the KgNB key based on the current KgNB key or the NH, using the received nextHopChainingCount value, as specified in TS 33.501[ Security architecture and procedures for 5G System ] [11]; 1> store the nextHopChainingCount value indicated in the RRCReestablishment message; 1> derive the KRRCenc and KUPenc keys associated with the previously configured cipheringAlgorithm, as specified in TS 33.501[ Security architecture and procedures for 5G System ] [11]; 1> derive the KRRCint and KUPint keys associated with the previously configured integrityProtAlgorithm, as specified in TS 33.501[ Security architecture and procedures for 5G System ] [11]. 1> request lower layers to verify the integrity protection of the RRCReestablishment message, using the previously configured algorithm and the KRRCint key; 1> if the integrity protection check of the RRCReestablishment message fails: 2> perform the actions upon going to RRC_IDLE as specified in 5.3.11, with release cause 'RRC connection failure', upon which the procedure ends; 1> configure lower layers to resume integrity protection for SRB1 using the previously configured algorithm and the KRRCint key immediately, i.e., integrity protection shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure; 1> configure lower layers to resume ciphering for SRB1 using the previously configured algorithm and, the KRRCenc key immediately, i.e., ciphering shall be applied to all subsequent messages received and sent by the UE, including the message used to indicate the successful completion of the procedure; 1> release the measurement gap configuration indicated by the measGapConfig, if configured; 1> release the MUSIM gap configuration indicated by the musim-GapConfig, if configured; 1> release the FR2 UL gap configuration indicated by the ul-GapFR2-Config, if configured; 1> perform the L2 U2N Remote UE configuration procedure in accordance with the received sl-L2RemoteUE-Config as specified in 5.3.5.16; 1> set the content of RRCReestablishmentComplete message as follows: 2> if the UE has logged measurements available for NR and if the RPLMN is included in plmn-IdentityList stored in VarLogMeasReport; or 2> if the UE has logged measurements available for NR and if the current registered SNPN are included in snpn-ConfigIDList stored in VarLogMeasReport: 3> include the logMeasAvailable in the RRCReestablishmentComplete message; 3> if Bluetooth measurement results are included in the logged measurements the UE has available for NR: 4> include the logMeasAvailableBT in the RRCReestablishmentComplete message; 3> if WLAN measurement results are included in the logged measurements the UE has available for NR: 4> include the logMeasAvailableWLAN in the RRCReestablishmentComplete message; 2> if the sigLoggedMeasType in VarLogMeasReport is included; or 2> if the UE is capable of reporting availability of signalling based logged MDT for inter-RAT (i.e. LTE to NR), and if the sigLoggedMeasType in VarLogMeasReport of TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10] is included: 3> if T330 timer is running (associated to the logged measurement configuration for NR or for LTE): 4> set sigLogMeasConfigAvailable to true in the RRCReestablishmentComplete message; 3> else: 4> if the UE has logged measurements: 5> set sigLogMeasConfigAvailable to false in the RRCReestablishmentComplete message; 2> if the UE has connection establishment failure or connection resume failure information available in VarConnEstFailReport or VarConnEstFailReportList and if the RPLMN is equal to plmn-Identity stored in VarConnEstFailReport or in at least one of the entries of VarConnEstFailReportList; or 2> if the UE supports multiple CEF report and if the UE has connection establishment failure information or connection resume failure information available in VarConnEstFailReport or VarConnEstFailReportList and if the registered SNPN identity is equal to snpn-identity stored in VarConnEstFailReport or any entry of VarConnEstFailReportList: 3> include connEstFailInfoAvailable in the RRCReestablishmentComplete message; 2> if the UE has radio link failure or handover failure information available in VarRLF-Report and if the RPLMN is included in plmn-IdentityList stored in VarRLF-Report; or 2> if the UE has radio link failure or handover failure information available in VarRLF-Report of TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10] and if the UE is capable of cross-RAT RLF reporting and if the RPLMN is included in plmn-IdentityList stored in VarRLF-Report of TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10]; or 2> if the UE has radio link failure or handover failure information available in VarRLF-Report and if the current registered SNPN is included in snpn-IdentityList stored in VarRLF-Report: 3> include rlf-InfoAvailable in the RRCReestablishmentComplete message; 2> if the UE has successful handover information available in VarSuccessHO-Report and if the RPLMN is included in plmn-IdentityList stored in VarSuccessHO-Report; or 2> if the UE has successful handover information available in VarSuccessHO-Report and if the current registered SNPN is included in snpn-IdentityList stored in the VarSuccessHO-Report: 3> include successHO-InfoAvailable in the RRCReestablishmentComplete message; 2> if the UE has successful PSCell change or addition information available in VarSuccessPSCell-Report and if the RPLMN is included in plmn-IdentityList stored in VarSuccessPSCell-Report; or 2> if the UE has successful PSCell change or addition information available in VarSuccessPSCell-Report and if the current registered SNPN is included in snpn-IdentityList stored in the VarSuccessPSCell-Report: 3> include successPSCell-InfoAvailable in the RRCReestablishmentComplete message; 2> if the UE has flight path information available: 3> if the UE had not previously provided a flight path information since last entering RRC_CONNECTED state; or 3> if at least one waypoint was not previously provided; or 3> if at least one upcoming waypoint that was previously provided is being removed; or 3> if flightPathUpdateDistanceThr is configured and for at least one waypoint, the 3D distance between the previously provided location and the new location is more than or equal to the distance threshold configured by flightPathUpdateDistanceThr; or 3> if flightPathUpdateTimeThr is configured and for at least one waypoint, the timestamp was not previously provided but is now available, or the time between the previously provided timestamp and the new timestamp, if available, is more than or equal to the time threshold configured by flightPathUpdateTimeThr: 4> include flightPathInfoAvailable; NOTE: If neither flightPathUpdateDistanceThr nor flightPathUpdateTimeThr is configured, it is up to UE implementation whether to include flightPathInfoAvailable when updated flight path information is available. 1> submit the RRCReestablishmentComplete message to lower layers for transmission; 1> if SIB21 is provided by the PCell: 2> if the UE initiated transmission of an MBSInterestIndication message during the last 1 second preceding detection of radio link failure: 3> initiate transmission of an MBSInterestIndication message in accordance with 5.9.4; 1> the procedure ends. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.7.5 |
1,612 | 6.45.2 Requirements | The 5G system shall allow roaming services to be provided by a roaming services provider in charge of managing roaming agreements, by mediating between two or more PLMNs, while maintaining the privacy and 5G security of any information transmitted between the home and the serving PLMN. NOTE 1: A PLMN can support both bi-lateral direct relationships with other PLMNs and make use of roaming service provider services toward different roaming partners. The 5G system shall allow a roaming services provider to be a trusted entity for either a home PLMN, a visited PLMN or both. NOTE 2: The expected maximum number of roaming service providers is two, one for the home PLMN and another for the visited PLMN. The 5G system shall allow a roaming services provider to accept or reject registration attempts, on behalf of the involved PLMNs, based on the roaming agreements. NOTE 3: Rejecting user registrations using an appropriate release cause permits the UE to be able to reselect another roaming partner or technology. The 5G system shall allow a roaming services provider to identify the origin and destination PLMN, and to verify the authenticity, of every transmitted message. The 5G system shall allow the Roaming services provider to be able to originate and modify messages as per contractually agreed SLAs. The 5G system shall allow the involved PLMNs to be able to identify the origin of any message generated by the roaming services providers as well as to identify any modification made to the exchanged messages by the roaming services providers. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.45.2 |
1,613 | 18.2 Radius Profile for Pk Reference Point | The RADIUS interface on Gi reference point as defined in Clause 16 is used for the Pk Reference Point as clarified in the Profile in this Clause. Only the following messages are required for the Radius Profile for the Pk reference Point: - Accounting-Request START - Accounting-Response START - Accounting-Request STOP - Accounting-Response STOP For the Radius Profile for the Pk Reference Point, only the mandatory Parameters within the Accounting-Request START and Accounting-Request STOP messages according to Clauses 16.4.3 and 16.4.4, respectively, and the Parameter "Calling-Station-Id" need to be supported. The usage of other parameters is optional. They may be ignored by the Presence Network Agent. | 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 | 18.2 |
1,614 | 13.1 Protection at the network or transport layer 13.1.0 General | All network functions shall support mutually authenticated TLS and HTTPS as specified in RFC 7540 [47] and RFC 2818 [90]. The identities in the end entity certificates shall be used for authentication and policy checks. Network functions shall support both server-side and client-side certificates. TLS client and server certificates shall be compliant with the SBA certificate profile specified in clause 6.1.3c of TS 33.310[ Network Domain Security (NDS); Authentication Framework (AF) ] [5]. The TLS profile shall follow the profile given in clause 6.2 of TS 33.210[ Network Domain Security (NDS); IP network layer security ] [3] with the restriction that it shall be compliant with the profile given by HTTP/2 as defined in RFC 7540 [47]. TLS clients shall include the SNI extension as specified in RFC 7540 [47]. TLS shall be used for transport protection within a PLMN unless network security is provided by other means. NOTE 1: Regardless of whether TLS is used or not, NDS/IP as specified in TS 33.210[ Network Domain Security (NDS); IP network layer security ] [3] and TS 33.310[ Network Domain Security (NDS); Authentication Framework (AF) ] [5] can be used for network layer protection. NOTE 2: If interfaces are trusted (e.g. physically protected), it is for the PLMN-operator to decide whether to use cryptographic protection. NOTE 3: It is a vendor implementation decision how the SNI extension is being used in TLS servers. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 13.1 |
1,615 | G.5 Causes related to invalid messages | Cause value = 95 Semantically incorrect message. See annex H, subclause H.5.10. Cause value = 96 Invalid mandatory information. See annex H, subclause H.6.1. Cause value = 97 Message type non-existent or not implemented. See annex H, subclause H.6.2. Cause value = 98 Message type not compatible with protocol state. See annex H, subclause H.6.3. Cause value = 99 Information element non-existent or not implemented. See annex H, subclause H.6.4. Cause value = 100 Conditional IE error. See annex H, subclause H.6.5. Cause value = 101 Message not compatible with protocol state. See annex H, subclause H.6.6. Cause value = 111 Protocol error, unspecified. See annex H, subclause H.6.8. | 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 | G.5 |
1,616 | 4.16.1.11 Number of Successful reconfigured SN terminated bearers at Secondary Node Additions | a) This measurement provides the number of Successful reconfigured SN terminated bearers at Secondary Node Additions. b) CC c) On transmission by the MN of an SgNB reconfiguration complete message to SN (after MN receives RRCConnectionReconfigurationComplete message) from UE when Secondary Node Additions with SN terminated bearers. Each successful reconfigured ERAB (which based SGNB ADDITION REQUEST ACKNOWLEDGE successful ERAB) on added to the relevant measurement per bearer type. The sum of all supported per bearer type measurements shall equal the total number of E-RABs successfully setup. In case only a subset of per bearer type measurements is supported, a sum subcounter will be provided first. SGNB Addition Trigger Indication (TS 36.423[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 Application Protocol (X2AP) ] ) excludes SN change, inter-eNB HO, intra-eNB HO. d) Each measurement is an integer value. e) The measurement name has the form ERAB.SNAdditionSuccAtSnAddition, ERAB.SNAdditionSuccAtSnAddition.SCG, ERAB.SNAdditionSuccAtSnAddition.SCGSplit. 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.16.1.11 |
1,617 | 9.5.5.2 TDD | The minimum performance requirement in Table 9.5.5.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 ≥ ; c) For Test 2, the RI reported for CSI process 1 shall be the same as the most recent RI reported for CSI process 0 if UE is configured with multiple CSI processes. For the parameters specified in Table 9.5.5.2-1, and using the downlink physical channels specified in Annex C.3.2, the minimum requirements are specified in Table 9.5.5.2-2. Table 9.5.5.2-1: RI Test (TDD) Table 9.5.5.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.5.5.2 |
1,618 | 9.9.3.70 Unavailability configuration | The purpose of the Unavailability configuration information element is to provide the unavailability period duration and the end of unavailability report indication from network to the UE. The Unavailability configuration information element is coded as shown in figure 9.9.3.70.1 and table 9.9.3.70.1. The Unavailability configuration is a type 4 information element with a minimum length of 3 octets and maximum length of 6 octets. Figure 9.9.3.70.1: Unavailability configuration information element Table 9.9.3.70.1: Unavailability configuration 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.70 |
1,619 | 5.15.14 Network Slice AS Groups support | The NG-RAN may support Network Slice AS Groups (NSAGs) which are used as specified in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [27], TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [28], TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [143] and TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [50]. A Network Slice AS Group is an identifier of a group of network slices which are associated with it. A Network Slice AS Group association with a group of network slices may be valid in one or more Tracking Areas. An S-NSSAI can be associated with at most one NSAG values for Random Access and at most one NSAG value for Cell Reselection within a Tracking Area. An S-NSSAI can be associated with different NSAG values in different Tracking Areas. The NG-RAN provides (and updates) the AMF with the values of the NSAG(s) an S-NSSAI is associated with in a TA using the NG Set Up and RAN Configuration Update procedures (see TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [34]). The AMF in turn provides this information to the NSSF. In deployments where the total number of groups does not exceed the number of groups associated with the NSAG size limit defined in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [28]), all the NSAGs configured in the NG-RAN may be unique per PLMN or SNPN. If the UE has indicated that the UE supports NSAG in the 5GMM Core Network Capability (see clause 5.4.4a), the AMF may, with or without NSSF assistance, configure the UE with NSAG Information for one or more S-NSSAIs in the Configured NSSAI, by including this NSAG Information in the Registration Accept message or the UE Configuration Command message. The UE uses the NSAG Information as defined in clause 5.3.4.3.1. The AMF shall indicate in the NSAG Information in which TA a specific NSAG association to S-NSSAI(s) is valid if the AMF provides in the UE configuration a NSAG value which is used in different TAs with a different association with NSSAIs. The configuration the AMF provides includes at least the NSAGs for the UE for the TAs of the Registration Area. If the AMF does not include the list of TAIs in association with an NSAG in the NSAG Information, the NSAG is valid in the Registered PLMN and equivalent PLMNs, or SNPN. NOTE: If the NSAGs for the PLMN and equivalent PLMNs have different associations to S-NSSAIs, then the AMF includes the list of TAIs in the NSAG information. The UE shall store and consider the received NSAG Information, valid for the Registered PLMN and equivalent PLMNs, or SNPN until: - the UE receives new NSAG information in a Registration Accept message or UE Configuration Command message in this PLMN or SNPN; or - the UE receives a Configured NSSAI without any NSAG information in this PLMN or SNPN. The UE shall store the currently valid NSAG information received in the Registered PLMN or SNPN when registered in this PLMN or SNPN and: - The UE should be able to store the NSAG information for at least the Registered-PLMN and equivalent PLMNs, or the Registered-SNPN and equivalent SNPNs. - The Registered-PLMN can provide NSAG information to the UE for the PLMN and the equivalent PLMNs, and the Registered-SNPN can provide NSAG information to the UE for the SNPN. - There can be at most 32 NSAGs configured in the UE at a time for a PLMN or SNPN. - At most 4 NSAGs can have an optional TAI associated with it. The NSAG information is not required to be stored after power off or after the UE becomes Deregistered as it is not used for cell selection. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.15.14 |
1,620 | C.2.3 Notes | 1. Using the above array mechanism, it is not required that a previously visited VLR/SGSN deletes the unused authentication vectors when a user de-registers from the serving network (super-charger concept). Retaining the authentication vectors for use when the user returns later may be more efficient as regards signalling when a user abroad switches a lot between two serving networks. 2. The array mechanism may also be used to avoid unjustified rejection of user authentication requests when authentication vectors in two VLR/SGSNs from different mobility management domains (circuit and packet) are used in an interleaving fashion. 3. When a VLR/SGSN uses fresh authentication vectors obtained during a previous visit of the user, the USIM can reject them although they have not been used before (because the array size a and the age limit L are finite). Rejection of a sequence number can therefore occur in normal operation, i.e., it is not necessarily caused by (malicious) replay or a database failure. 4. The mechanism presented in this section may allow the USIM to exploit knowledge about which authentication vectors were sent to the same VLR/SGSN. It may be assumed that authentication vectors sent to the same VLR/SGSN are always used in the correct order. Consequently, only one sequence number among those sent to the same VLR/SGSN has to be stored. 5. With the exception of SQNMS , the entries of the array need not be stored in full length if a limit L (age limit) on the difference between SEQMS and a received sequence number component SEQ is applied. 6. Condition (2) of Annex C.2.1 on means that SQNMS can reach its maximum value only after a minimum of SEQmax / successful authentications have taken place. 7. There is a dependency of the choice of and the size n of global counter GLC in Annex C.1.1.1: shall be chosen larger than 2n. | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | C.2.3 |
1,621 | 8.4.2.2.3 Minimum Requirement 2 Tx Antenna Port (demodulation subframe overlaps with aggressor cell ABS) | For the parameters for non-MBSFN ABS specified in Table 8.4.2-1 and Table 8.4.2.2.3-1, the average probability of a missed downlink scheduling grant (Pm-dsg) shall be below the specified value in Table 8.4.2.2.3-2. The downlink physical setup is in accordance with Annex C.3.2 and Annex C.3.3.. In Table 8.4.2.2.3-1, Cell 1 is the serving cell, and Cell 2 is the aggressor cell. The downlink physical channel setup for Cell 1 is according to Annex C.3.2 and for Cell 2 is according to Annex C.3.3, respectively. For the parameters for MBSFN ABS specified in Table 8.4.2-1 and Table 8.4.2.2.3-3, the average probability of a missed downlink scheduling grant (Pm-dsg) shall be below the specified value in Table 8.4.2.2.3-4. The downlink physical channel setup for Cell 1 is according to Annex C3.2 and for Cell 2 is according to Annex C.3.3, respectively. Table 8.4.2.2.3-1: Test Parameters for PDCCH/PCFICH – Non-MBSFN ABS Table 8.4.2.2.3-2: Minimum performance PDCCH/PCFICH – Non-MBSFN ABS Table 8.4.2.2.3-3: Test Parameters for PDCCH/PCFICH – MBSFN ABS Table 8.4.2.2.3-4: Minimum performance PDCCH/PCFICH – MBSFN ABS | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.4.2.2.3 |
1,622 | 6.2.5 Guard period for half-duplex FDD operation | For type A half-duplex FDD operation, a guard period is created by the UE by - not receiving the last part of a downlink subframe immediately preceding an uplink subframe from the same UE. For type B half-duplex FDD operation, guard periods, each referred to as a half-duplex guard subframe, are created by the UE by - not receiving a downlink subframe immediately preceding an uplink subframe from the same UE, and - not receiving a downlink subframe immediately following an uplink subframe from the same UE. | 3GPP TS 36.211 | Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation | RAN1 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.2.5 |
1,623 | 6.2.2 UE maximum output power | The following UE Power Classes define the maximum output power for any transmission bandwidth within the channel bandwidth for non CA configuration unless otherwise stated. The period of measurement shall be at least as defined in Table 6.2.2-0. Table 6.2.2-0: Measurement period for UE maximum output power Table 6.2.2-1: UE Power Class The default power class PPowerClass_Default for an operating band is Power Class 3 unless otherwise stated. For a power class 2 capable UE operating on Band 41, when an IE P-max as defined in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [7] of 23 dBm or lower is indicated in the cell or if the uplink/downlink configuration is 0 or 6, the requirements for power class 2 are not applicable, and the corresponding requirements for a power class 3 UE shall apply. For each supported frequency band other than Band 14 and Band 41, the UE shall: - if the UE supports a different power class than the default UE power class for the band and the supported power class enables the higher maximum output power than that of the default power class: - if the band is a TDD band whose frame configuration is 0 or 6; or - if the IE P-Max as defined in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [7] is not provided; or - if the IE P-Max as defined in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [7] is provided and set to the maximum output power of the default power class or lower; - meet all requirements for the default power class of the operating band in which the UE is operating and set its configured transmitted power as specified in sub-clause 6.2.5; - else (i.e the IE P-Max as defined in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [7] is provided and set to the higher value than the maximum output power of the default power class): - meet all requirements for the supported power class and set its configured transmitted power class as specified in sub-clause 6.2.5; | 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.2 |
1,624 | D.2 Support of Non-Public Network as a network slice of a PLMN | The PLMN operator can provide access to an NPN by using network slicing mechanisms. NOTE: Access to PLMN services can be supported in addition to PNI-NPN services, e.g. based on different S-NSSAI/DNN for different services. The following are some considerations in such a PNI-NPN case: 1. The UE has subscription and credentials for the PLMN; 2. The PLMN and NPN service provider have an agreement of where the NPN Network Slice is to be deployed (i.e. in which TAs of the PLMN and optionally including support for roaming PLMNs); 3. The PLMN subscription includes support for Subscribed S-NSSAI to be used for the NPN (see clause 5.15.3); 4. The PLMN operator can offer possibilities for the NPN service provider to manage the NPN Network Slice according to TS 28.533[ Management and orchestration; Architecture framework ] [79]. 5. When the UE registers the first time to the PLMN, the PLMN can configure the UE with URSP including NSSP associating Applications to the NPN S-NSSAI (if the UE also is able to access other PLMN services); 6. The PLMN can configure the UE with Configured NSSAI for the Serving PLMN (see clause 5.15.4); 7. The PLMN and NPN can perform a Network Slice specific authentication and authorization using additional NPN credentials; 8. The UE follows the logic as defined for Network Slicing, see clause 5.15; 9. The network selection logic, access control etc are following the principles for PLMN selection; and 10. The PLMN may indicate to the UE that the NPN S-NSSAI is rejected for the RA when the UE moves out of the coverage of the NPN Network Slice. However, limiting the availability of the NPN S-NSSAI would imply that the NPN is not available outside of the area agreed for the NPN S-NSSAI, e.g. resulting in the NPN PDU Sessions being terminated when the UE moves out of the coverage of the NPN Network Slice. Similarly access to NPN DNNs would not be available via non-NPN cells. 11. In order to prevent access to NPNs for authorized UE(s) in the case of network congestion/overload and if a dedicated S-NSSAI has been allocated for an NPN, the Unified Access Control can be used using the operator-defined access categories with access category criteria type (as defined in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [47]) set to the S-NSSAI used for an NPN. 12. If NPN isolation is desired, it is assumed that a dedicated S-NSSAI is configured for the NPN and that the UE is configured to operate in Access Stratum Connection Establishment NSSAI Inclusion Mode a, b or c, see clause 5.15.9, such that NG-RAN receives Requested NSSAI from the UE and it can use the S-NSSAI for AMF selection. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | D.2 |
1,625 | 4.5 Location Number | A location number is a number which defines a specific location within a PLMN. The location number is formatted according to ITU-T Recommendation E.164, as shown in figure 8. The Country Code (CC) and National Destination Code (NDC) fields of the location number are those which define the PLMN of which the location is part. Figure 8: Location Number Structure The structure of the locally significant part (LSP) of the location number is a matter for agreement between the PLMN operator and the national numbering plan administrator in the PLMN's country. It is desirable that the location number can be interpreted without the need for detailed knowledge of the internal structure of the PLMN; the LSP should therefore include the national destination code in the national numbering plan for the fixed network which defines the geographic area in which the location lies. The set of location numbers for a PLMN shall be chosen so that a location number can be distinguished from the MSISDN of a subscriber of the PLMN. This will allow the PLMN to trap attempts by users to dial a location number. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.5 |
1,626 | 6.8 Dynamic policy control | The 5G system shall support the creation and enforcement of prioritisation policy for users and traffic, during connection setup and when connected. NOTE: Prioritisation, pre-emption, and precedence of critical traffic associated with certain priority services (e.g. MPS and Emergency) are subject to regional/national regulatory and operator policies. The 5G system shall support optimised signalling for prioritised users and traffic where such signalling is prioritized over other signalling traffic. Based on operator policy, the 5G system shall allow flexible means for authorized entities to create and enforce priority among the different service flows. Based on operator policy, the 5G system shall support a real-time, dynamic, secure and efficient means for authorized entities (e.g. users, context aware network functionality) to modify the QoS and policy framework. Such modifications may have a variable duration. Based on operator policy, the 5G system shall maintain a session when prioritization of that session changes in real time, provided that the new priority is above the threshold for maintaining the session. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.8 |
1,627 | 5.7.8.2a Performing measurements | When performing measurements on NR carriers according to this clause, the UE shall derive the cell quality as specified in 5.5.3.3 and consider the beam quality to be the value of the measurement results of the concerned beam, where each result is averaged as described in TS 38.215[ NR; Physical layer measurements ] [9]. While in RRC_IDLE or RRC_INACTIVE, and T331 is running and SDT procedure is not ongoing, the UE shall: 1> perform the measurements in accordance with the following: 2> if the VarMeasIdleConfig includes the measIdleCarrierListEUTRA and the SIB1 contains idleModeMeasurementsEUTRA: 3> for each entry in measIdleCarrierListEUTRA within VarMeasIdleConfig: 4> if UE supports NE-DC between the serving carrier and the carrier frequency indicated by carrierFreqEUTRA within the corresponding entry: 5> perform measurements in the carrier frequency and bandwidth indicated by carrierFreqEUTRA and allowedMeasBandwidth within the corresponding entry; 5> if the reportQuantitiesEUTRA is set to rsrq: 6> consider RSRQ as the sorting quantity; 5> else: 6> consider RSRP as the sorting quantity; 5> if the measCellListEUTRA is included: 6> consider cells identified by each entry within the measCellListEUTRA to be applicable for idle/inactive mode measurement reporting; 5> else: 6> consider up to maxCellMeasIdle strongest identified cells, according to the sorting quantity, to be applicable for idle/inactive measurement reporting; 5> for all cells applicable for idle/inactive measurement reporting, derive measurement results for the measurement quantities indicated by reportQuantitiesEUTRA; 5> store the derived measurement results as indicated by reportQuantitiesEUTRA within the measReportIdleEUTRA in VarMeasIdleReport in decreasing order of the sorting quantity, i.e. the best cell is included first, as follows: 6> if qualityThresholdEUTRA is configured: 7> include the measurement results from the cells applicable for idle/inactive measurement reporting whose RSRP/RSRQ measurement results are above the value(s) provided in qualityThresholdEUTRA; 6> else: 7> include the measurement results from all cells applicable for idle/inactive measurement reporting; 2> if the VarMeasIdleConfig includes the measIdleCarrierListNR and the SIB1 contains idleModeMeasurementsNR: 3> for each entry in measIdleCarrierListNR within VarMeasIdleConfig that contains ssb-MeasConfig: 4> if UE supports carrier aggregation or NR-DC between serving carrier and the carrier frequency and subcarrier spacing indicated by carrierFreq and ssbSubCarrierSpacing within the corresponding entry: 5> perform measurements in the carrier frequency and subcarrier spacing indicated by carrierFreq and ssbSubCarrierSpacing within the corresponding entry; 5> if the reportQuantities is set to rsrq: 6> consider RSRQ as the cell sorting quantity; 5> else: 6> consider RSRP as the cell sorting quantity; 5> if the measCellListNR is included: 6> consider cells identified by each entry within the measCellListNR to be applicable for idle/inactive measurement reporting; 5> else: 6> consider up to maxCellMeasIdle strongest identified cells, according to the sorting quantity, to be applicable for idle/inactive measurement reporting; 5> for all cells applicable for idle/inactive measurement reporting, derive cell measurement results for the measurement quantities indicated by reportQuantities; 5> store the derived cell measurement results as indicated by reportQuantities for cells applicable for idle/inactive measurement reporting within measResultsPerCarrierListIdleNR in the measReportIdleNR in VarMeasIdleReport in decreasing order of the cell sorting quantity, i.e. the best cell is included first, as follows: 6> if qualityThreshold is configured: 7> include the measurement results from the cells applicable for idle/inactive measurement reporting whose RSRP/RSRQ measurement results are above the value(s) provided in qualityThreshold; 6> else: 7> include the measurement results from all cells applicable for idle/inactive measurement reporting; 5> if beamMeasConfigIdle is included in the associated entry in measIdleCarrierListNR and if UE supports idleInactiveNR-MeasBeamReport for the FR of the carrier frequency indicated by carrierFreq within the associated entry, for each cell in the measurement results: 6> derive beam measurements based on SS/PBCH block for each measurement quantity indicated in reportQuantityRS-Indexes, as described in TS 38.215[ NR; Physical layer measurements ] [9]; 6> if the reportQuantityRS-Indexes is set to rsrq: 7> consider RSRQ as the beam sorting quantity; 6> else: 7> consider RSRP as the beam sorting quantity; 6> set resultsSSB-Indexes to include up to maxNrofRS-IndexesToReport SS/PBCH block indexes in order of decreasing beam sorting quantity as follows: 7> include the index associated to the best beam for the sorting quantity and if absThreshSS-BlocksConsolidation is included, the remaining beams whose sorting quantity is above absThreshSS-BlocksConsolidation; 6> if the includeBeamMeasurements is set to true: 7> include the beam measurement results as indicated by reportQuantityRS-Indexes; 2> if, as a result of the procedure in this clause, the UE performs measurements in one or more carrier frequency indicated by measIdleCarrierListNR or measIdleCarrierListEUTRA: 3> store the cell measurement results for RSRP and RSRQ for the serving cell within measResultServingCell in the measReportIdleNR in VarMeasIdleReport. 3> if the VarMeasIdleConfig includes the measIdleCarrierListNR and it contains an entry with carrierFreq set to the value of the serving frequency: 4> if beamMeasConfigIdle is included in that entry, and if the UE supports idleInactiveNR- MeasBeamReport for the FR of the serving cell: 5> derive beam measurements based on SS/PBCH block for each measurement quantity indicated in reportQuantityRS-Indexes, as described in TS 38.215[ NR; Physical layer measurements ] [9]; 5> if the reportQuantityRS-Indexes is set to rsrq: 6> consider RSRQ as the beam sorting quantity; 5> else: 6> consider RSRP as the beam sorting quantity; 5> set resultsSSB-Indexes to include up to maxNrofRS-IndexesToReport SS/PBCH block indexes in order of decreasing beam sorting quantity as follows: 6> include the index associated to the best beam for the sorting quantity and if absThreshSS-BlocksConsolidation is included in SIB2 of serving cell, the remaining beams whose sorting quantity is above absThreshSS-BlocksConsolidation; 5> if the includeBeamMeasurements is set to true: 6> include the beam measurement results as indicated by reportQuantityRS-Indexes; NOTE 1: How the UE performs idle/inactive measurements is up to UE implementation as long as the requirements in TS 38.133[ NR; Requirements for support of radio resource management ] [14] are met for measurement reporting. NOTE 2: The UE is not required to perform idle/inactive measurements on a given carrier if the SSB configuration of that carrier provided via dedicated signaling is different from the SSB configuration broadcasted in the serving cell, if any. NOTE 3: How the UE prioritizes which frequencies to measure or report (in case it is configured with more frequencies than it can measure or report) is left to UE implementation. NOTE 4: When idleModeMeasVoiceFallback is included in SIB5, UE may decide to measure and report idle/inactive measurements for EUTRA carrier frequencies included in SIB5 even if it does not support NE-DC between the serving carrier and the EUTRA carrier frequencies. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.7.8.2a |
1,628 | 5.7.2.7 Default values | For each PDU Session Setup, the SMF retrieves the subscribed Session-AMBR values as well as the subscribed default values for the 5QI and the ARP and optionally, the 5QI Priority Level, from the UDM. The subscribed default 5QI value shall be a Non-GBR 5QI from the standardized value range. NOTE 1: The 5QI Priority Level can be added to the subscription information to achieve an overwriting of the standardized or preconfigured 5QI Priority Level e.g. in scenarios where dynamic PCC is not deployed or the PCF is unavailable or unreachable. The SMF may change the subscribed values for the default 5QI and the ARP and if received, the 5QI Priority Level, based on interaction with the PCF as described in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45] or, if dynamic PCC is not deployed, based on local configuration, to set QoS parameters for the QoS Flow associated with the default QoS rule. For QoS Flow(s) of the PDU Session other than the QoS Flow associated with the default QoS rule, the SMF shall set the ARP priority level, the ARP pre-emption capability and the ARP pre-emption vulnerability to the respective values in the PCC rule(s) bound to that QoS Flow (as described in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]). If dynamic PCC is not deployed, the SMF shall set the ARP priority level, the ARP pre-emption capability and the ARP pre-emption vulnerability based on local configuration. NOTE 2: The local configuration in the SMF can e.g. make use of the subscribed value for the ARP priority level and apply locally configured values for the ARP pre-emption capability and ARP pre-emption vulnerability. If dynamic PCC is not deployed, the SMF can have a DNN based configuration to enable the establishment of a GBR QoS Flow as the QoS Flow that is associated with the default QoS rule. This configuration contains a standardized GBR 5QI as well as GFBR and MFBR for UL and DL. NOTE 3: Interworking with EPS is not possible for a PDU Session with a GBR QoS Flow as the QoS Flow that is associated with the default QoS rule. The SMF may change the subscribed Session-AMBR values (for UL and/or DL), based on interaction with the PCF as described in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45] or, if dynamic PCC is not deployed, based on local configuration, to set the Session-AMBR values for the PDU Session. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.7.2.7 |
1,629 | 13.1.1.1 TLS protection based on telescopic FQDN and wildcard certificate | A telescopic FQDN is an FQDN with a single label as the first element and the SEPP’s domain as the trailer component. The label uniquely represents the original FQDN. NOTE 3: The structure of telescopic FQDN is defined in 3GPP TS 23.003[ Numbering, addressing and identification ] [19], clause 28.5.2. The SEPP shall generate a telescopic FQDN for the following messages received over N32-f: a. Nnrf_NFDiscovery_Get response HTTP message with FQDNs of a set of the discovered NF or NF service instance(s) (see TS 29.510[ 5G System; Network function repository services; Stage 3 ] [68]). The cSEPP generates a telescopic FQDN for each target Network Function FQDN in the Discovery response, rewrites the original FQDN with the telescopic FQDN and forwards the modified Discovery response to the NRF. b. Subscription message with the Callback URI in the payload of the message (see TS 29.501[ 5G System; Principles and Guidelines for Services Definition; Stage 3 ] [94]). The pSEPP generates a telescopic FQDN from the Callback URI in the Subscription message, rewrites the original FQDN in the callback URI, and forwards the modified Subscription message to the producer Network Function. c. Nsmf_PDUSession_POST HTTP message from a V-SMF with PduSessionCreateData containing the URI representing the PDU session in the V-SMF (see TS 29.502[ 5G System; Session Management Services; Stage 3 ] [95]). The pSEPP generates a telescopic FQDN from the Callback URI in the message, rewrites the original FQDN in the callback URI, and forwards the modified message to the target H-SMF. The following procedure illustrates how SEPPs use telescopic FQDN and wildcard certificate to establish a TLS connection between a Network Function or a SCP and the SEPP: 1. When the SEPP receives one of the messages identified in a-c above, it shall rewrite the FQDN from the received message with a telescopic FQDN and it forwards the modified HTTP message to the target Network Function or SCP inside the PLMN. 2. When the Network Function or SCP that received the telescopic FQDN in step 1 is ready to communicate with the target Network Function or SCP in another PLMN, it uses the telescopic FQDN in the Request URI of the HTTP Request. When communication between the Network Function or SCP and the SEPP that generated the telescopic FQDN is based on using the 3gpp-Sbi-Target-apiRoot custom HTTP header as specified in TS 29.500[ 5G System; Technical Realization of Service Based Architecture; Stage 3 ] [74], clause 5.2.3.2.4, the Network Function or SCP uses the telescopic FQDN in the 3gpp-Sbi-Target-apiRoot custom HTTP header of the HTTP Request. During TLS setup between the Network Function and the SEPP, the SEPP shall authenticate towards the Network Function or SCP using the wildcard certificate. 3. When the SEPP receives a HTTP request from the Network Function or SCP, the SEPP shall rewrite the telescopic FQDN with the original FQDN by replacing the unique delimiter in the label with the period character and removing its own suffix part. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 13.1.1.1 |
1,630 | 7.4.2 Requirements | A 5G system providing service with satellite access shall be able to support GEO based satellite access with up to 285 ms end-to-end latency. NOTE 1: 5 ms network latency is assumed and added to satellite one-way delay. A 5G system providing service with satellite access shall be able to support MEO based satellite access with up to 95 ms end-to-end latency. NOTE 2: 5 ms network latency is assumed and added to satellite one-way delay. A 5G system providing service with satellite access shall be able to support LEO based satellite access with up to 35 ms end-to-end latency. NOTE 3: 5 ms network latency is assumed and added to satellite one-way delay. A 5G system shall support negotiation on quality of service taking into account latency penalty to optimise the QoE for UE. The 5G system with satellite access shall support high uplink data rates for 5G satellite UEs. The 5G system with satellite access shall support high downlink data rates for 5G satellite UEs. The 5G system with satellite access shall support communication service availabilities of at least 99,99%. Table 7.4.2-1: Performance requirements for satellite access | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 7.4.2 |
1,631 | 6.2 Slot structure and physical resource elements 6.3 General structure for downlink physical channels | This clause describes a general structure, applicable to more than one physical channel. The baseband signal representing a downlink physical channel is defined in terms of the following steps: - scrambling of coded bits in each of the codewords to be transmitted on a physical channel - modulation of scrambled bits to generate complex-valued modulation symbols - mapping of the complex-valued modulation symbols onto one or several transmission layers - precoding of the complex-valued modulation symbols on each layer for transmission on the antenna ports - mapping of complex-valued modulation symbols for each antenna port to resource elements - generation of complex-valued time-domain OFDM signal for each antenna port Figure 6.3-1: Overview of physical channel processing | 3GPP TS 36.211 | Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation | RAN1 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.2 |
1,632 | 4.7.1.4.1 Radio resource sublayer address handling (A/Gb mode only) | This subclause describes how the RR addressing is managed by GMM. For the detailed coding of the different TLLI types and how a TLLI can be derived from a P-TMSI, see 3GPP TS 23.003[ Numbering, addressing and identification ] [10]. If the MS is configured for "AttachWithIMSI" as specified in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [135] or 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [112] and is entering a new PLMN which is neither the registered PLMN nor in the list of equivalent PLMNs, the MS should proceed as specified for case ii) below and use a randomly selected random TLLI for the transmission of the ATTACH REQUEST message. For all other cases, the MS shall determine the TLLI as follows: For an MS not supporting S1 mode, two cases can be distinguished: - a valid P-TMSI is available in the MS; or - no valid P-TMSI is available in the MS. i) valid P-TMSI available If the MS has stored a valid P-TMSI, the MS shall derive a foreign TLLI from that P-TMSI and shall use it for transmission of the: - ATTACH REQUEST message of any GPRS combined/non-combined attach procedure; other GMM messages sent during this procedure shall be transmitted using the same foreign TLLI until the ATTACH ACCEPT message or the ATTACH REJECT message is received; and - ROUTING AREA UPDATE REQUEST message of a combined/non-combined RAU procedure if the MS has entered a new routing area, or if the GPRS update status is not equal to GU1 UPDATED. Other GMM messages sent during this procedure shall be transmitted using the same foreign TLLI, until the ROUTING AREA UPDATE ACCEPT message or the ROUTING AREA UPDATE REJECT message is received. After a successful GPRS attach or routing area update procedure, independent of whether a new P-TMSI is assigned, if the MS has stored a valid P-TMSI then the MS shall derive a local TLLI from the stored P-TMSI and shall use it for addressing at lower layers. NOTE 1: Although the MS derives a local TLLI for addressing at lower layers, the network should not assume that it will receive only LLC frames using a local TLLI. Immediately after the successful GPRS attach or routing area update procedure, the network must be prepared to continue accepting LLC frames from the MS still using the foreign TLLI. ii) no valid P-TMSI available When the MS has not stored a valid P-TMSI, i.e. the MS is not attached to GPRS, the MS shall use a randomly selected random TLLI for transmission of the: - ATTACH REQUEST message of any combined/non-combined GPRS attach procedure. The same randomly selected random TLLI value shall be used for all message retransmission attempts and for the cell updates within one attach attempt. Upon receipt of an ATTACH REQUEST message, the network shall assign a P-TMSI to the MS. The network derives a local TLLI from the assigned P-TMSI, and transmits the assigned P-TMSI to the MS. Upon receipt of the assigned P-TMSI, the MS shall derive the local TLLI from this P-TMSI and shall use it for addressing at lower layers. NOTE 2: Although the MS derives a local TLLI for addressing at lower layers, the network should not assume that it will receive only LLC frames using a local TLLI. Immediately after the successful GPRS attach, the network must be prepared to continue accepting LLC frames from the MS still using the random TLLI. In both cases the MS shall acknowledge the reception of the assigned P-TMSI to the network. After receipt of the acknowledgement, the network shall use the local TLLI for addressing at lower layers. For an MS supporting S1 mode, the following five cases can be distinguished: a) the TIN indicates "P-TMSI" or "RAT-related TMSI" and the MS holds a valid P-TMSI and a RAI; b) the TIN indicates "GUTI" and the MS holds a valid GUTI allocated by an MME; c) the TIN is deleted and the MS holds a valid P-TMSI and RAI; d) the TIN is deleted and the MS holds a valid GUTI allocated by an MME, but no valid P-TMSI and RAI; or e) none of the previous cases is fulfilled. In case a) the MS shall derive a foreign TLLI from the P-TMSI and proceed as specified for case i) above. In case b), the MS shall derive a P-TMSI from the GUTI and then a foreign TLLI from this P-TMSI and proceed as specified for case i) above. NOTE 3: The mapping of the GUTI to the P-TMSI is specified in 3GPP TS 23.003[ Numbering, addressing and identification ] [10]. In case c) the MS shall derive a foreign TLLI from the P-TMSI and proceed as specified for case i) above. In case d) the MS shall derive a P-TMSI from the GUTI and then a foreign TLLI from this P-TMSI and proceed as specified for case i) above. In case e) the MS shall proceed as as specified for case ii) above. For transmission of an ATTACH REQUEST message, or a ROUTING AREA UPDATE REQUEST message after a routing area change, the MS also provides the lower layers with the DCN-ID according to the following rules: a) if a DCN-ID for the PLMN code of the selected PLMN is available in the MS, the MS shall provide this DCN-ID to the lower layers; or b) if no DCN-ID for the PLMN code of the selected PLMN is available but a Default_DCN_ID value is available in the MS, as specified in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [135] or in USIM file NASCONFIG as specified in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [112], the MS shall provide the Default_DCN_ID value to the lower layers. | 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.4.1 |
1,633 | 5.5.2.1.4 E-UTRAN to UTRAN Iu mode Inter RAT handover Reject | The Target RNC may reject the use of the Handover procedure if none of the requested RABs in the Relocation Request message could be established. In this case no UE context is established in the target SGSN/RNC and no resources are allocated. The UE remains in the Source eNodeB/MME. Figure 5.5.2.1.4-1: E-UTRAN to UTRAN Iu mode Inter RAT HO reject 1. The Step 1 to 5 in the flow are identical to the ones in clause 5.5.2.1.2. 6. If the Target RNC fails to allocate any resources for any of the requested RABs it sends a Relocation Failure (Cause) message to the Target SGSN. When the Target SGSN receives the Relocation Failure message from Target RNC the Target SGSN clears any reserved resources for this UE. 7. This step is only performed for Serving GW relocation, i.e. if Steps 4/4a have been performed. The Target SGSN deletes the EPS bearer resources by sending Delete Session Request (Cause) messages to the Target Serving GW. The Target Serving GW acknowledges with Delete Session Response (Cause) messages. 8. The Target SGSN sends the Forward Relocation Response (Cause) message to the Source MME. 9. When the Source MME receives the Forward Relocation Response message it send a Handover Preparation Failure (Cause) message to the Source eNodeB. | 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.4 |
1,634 | 5.4.3.7 Abnormal cases on the network side | The following abnormal cases can be identified: a) Lower layer failure before the SECURITY MODE COMPLETE or SECURITY MODE REJECT message is received The network shall abort the security mode control procedure. b) Expiry of timer T3460 The network shall, on the first expiry of the timer T3460, retransmit the SECURITY MODE COMMAND message and shall reset and start timer T3460. This retransmission is repeated four times, i.e. on the fifth expiry of timer T3460, the procedure shall be aborted. NOTE: If the SECURITY MODE COMMAND message was sent to create a mapped EPS security context during inter-system change from A/Gb mode to S1 mode or Iu mode to S1 mode, then the network does not generate new values for the nonceMME and the nonceUE, but includes the same values in the SECURITY MODE COMMAND message (see the clause 7.2.4.4 in 3GPP TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [19]). c) Collision between security mode control procedure and attach, service request, tracking area updating procedure or detach procedure not indicating switch off The network shall abort the security mode control procedure and proceed with the UE initiated procedure. d) Collision between security mode control procedure and other EMM procedures than in item c The network shall progress both procedures. e) Lower layers indication of non-delivered NAS PDU due to handover If the SECURITY MODE COMMAND message could not be delivered due to an intra MME handover and the target TA is included in the TAI list, then upon successful completion of the intra MME handover the MME shall retransmit the SECURITY MODE COMMAND message. If a failure of the handover procedure is reported by the lower layer and the S1 signalling connection exists, the MME shall retransmit the SECURITY MODE COMMAND message. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.4.3.7 |
1,635 | 6.4.4.5 Abnormal cases on the network side | The following abnormal cases can be identified: a) Expiry of timer T3495: On the first expiry of the timer T3495, the MME shall resend the DEACTIVATE EPS BEARER CONTEXT REQUEST and shall reset and restart timer T3495. This retransmission is repeated four times, i.e. on the fifth expiry of timer T3495, the MME shall abort the procedure and deactivate the EPS bearer context locally without any peer-to-peer ESM signalling between the MME and the UE. b) Collision of UE requested PDN disconnect procedure and EPS bearer context deactivation: When the MME receives a PDN DISCONNECT REQUEST message during the EPS bearer context deactivation procedure, and the EPS bearer indicated in the DEACTIVATE EPS BEARER CONTEXT REQUEST message is a dedicated EPS bearer belonging to the PDN connection the UE wants to disconnect, the MME shall proceed with both procedures. If the EPS bearer indicated in the DEACTIVATE EPS BEARER CONTEXT REQUEST message is the default EPS bearer, the MME shall proceed with the EPS bearer context deactivation procedure. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.4.4.5 |
1,636 | 5.6.1 Overview | NR Radio Access operating with shared spectrum channel access can operate in different modes where either PCell, PSCell, or SCells can be in shared spectrum and an SCell may or may not be configured with uplink. The applicable deployment scenarios are described in Annex B.3. The gNB performs channel access mode procedures as described in TS 37.213[ Physical layer procedures for shared spectrum channel access ] [37]. The gNB and the UE may apply Listen-Before-Talk (LBT) before performing a transmission on a cell configured with shared spectrum channel access. When LBT is applied, the transmitter listens to/senses the channel to determine whether the channel is free or busy and performs transmission only if the channel is sensed free. When the UE detects consistent uplink LBT failures, it takes actions as specified in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [6]. The detection is per Bandwidth Part (BWP) and based on all uplink transmissions within this BWP. When consistent uplink LBT failures are detected on SCell(s), the UE reports this to the corresponding gNB (MN for MCG, SN for SCG) via MAC CE on a different serving cell than the SCell(s) where the failures were detected. If no resources are available to transmit the MAC CE, a Scheduling Request (SR) can be transmitted by the UE. When consistent uplink LBT failures are detected on SpCell, the UE switches to another UL BWP with configured RACH resources on that cell, initiates RACH, and reports the failure via MAC CE. When multiple UL BWPs are available for switching, it is up to the UE implementation which one to select. For PSCell, if consistent uplink LBT failures are detected on all the UL BWPs with configured RACH resources, the UE declares SCG RLF and reports the failure to the MN via SCGFailureInformation. For PCell, if the uplink LBT failures are detected on all the UL BWP(s) with configured RACH resources, the UE declares RLF. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.6.1 |
1,637 | 9.9.3.53 UE additional security capability | The UE additional security capability information element is used by the UE to indicate which additional security algorithms are supported by the UE for S1 mode in dual connectivity with NR or for N1 mode or both. The UE additional security capability information element is coded as shown in figure 9.9.3.53.1 and table 9.9.3.53.1. The UE additional security capability is a type 4 information element with a length of 6 octets. Figure 9.9.3.53.1: UE additional security capability information element Table 9.9.3.53.1: UE additional security capability 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.53 |
1,638 | 4.17.12.2 Binding created as part of service response | When the NF service consumer communicates with the NF service producer, the producer may return a binding indication to the consumer. The consumer stores the received binding indication and uses it for the subsequent requests concerning the data context. Figure 4.17.12.2-1: Binding created as part of service response 1. If Direct Communication is used, the NF service consumer selects the NF service producer and sends the request to the selected NF service producer. If Indirect Communication without delegated discovery is used, the NF service consumer selects the NF service producer set or instance and sends the request to the selected NF service producer via the SCP; if the NF serviver consumer only selects the NF service producer set, it provides the necessary selection parameters and the SCP selects the NF service producer instance. If Indirect Communication with delegated discovery is used, the NF service consumer sends the request to the SCP and provides within the service request to the SCP the discovery and selection parameters necessary to discover and select a NF service producer. 2. The NF service producer sends a response to the NF service consumer. In the response the NF service producer may include a binding indication. If the NF service consumer receives a resource information and binding indication as specified in Table 6.3.1.0-1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], it uses them for subsequent requests regarding the concerned resource. Otherwise, the procedure ends here. 3. The NF service consumer uses the binding indication and resource information received in the previous step for subsequent requests regarding the concerned resource. If indirect communication with delegated discovery is used, the NF service consumer includes a Routing Binding Indication with the same contents as the received Binding Indication. If indirect communication without delegated discovery is used, the NF service consumer also includes the Routing Binding Indication with the same contents as the received Binding Indication unless the NF service consumer performs a reselection. The SCP shall route the service request using the Routing Binding Indication and resource information sent from the NF service consumer. 4. The NF service producer sends a response to the consumer. The NF service producer may respond with an updated binding indication, different to the one received in the previous response. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.17.12.2 |
1,639 | 8.2.1.1 Inter-gNB-DU Mobility | This procedure is used for the case when the UE moves from one gNB-DU to another gNB-DU within the same gNB-CU during NR operation. Figure 8.2.1.1-1 shows the inter-gNB-DU mobility procedure for intra-NR. Figure 8.2.1.1-1: Inter-gNB-DU Mobility for intra-NR 1. The UE sends a MeasurementReport message to the source gNB-DU. 2. The source gNB-DU sends an UL RRC MESSAGE TRANSFER message to the gNB-CU to convey the received MeasurementReport message. 2a. The gNB-CU may send an UE CONTEXT MODIFICATION REQUEST message to the source gNB-DU to query the latest configuration. 2b. The source gNB-DU responds with an UE CONTEXT MODIFICATION RESPONSE message that includes full configuration information. 3. The gNB-CU sends an UE CONTEXT SETUP REQUEST message to the target gNB-DU to create an UE context and setup one or more data bearers. The UE CONTEXT SETUP REQUEST message includes a HandoverPreparationInformation. In case of NG-RAN sharing, the gNB-CU includes the serving PLMN ID (for SNPNs the serving SNPN ID). 4. The target gNB-DU responds to the gNB-CU with an UE CONTEXT SETUP RESPONSE message. 5. The gNB-CU sends a UE CONTEXT MODIFICATION REQUEST message to the source gNB-DU, which includes a generated RRCReconfiguration message and indicates to stop the data transmission for the UE. The source gNB-DU also sends a Downlink Data Delivery Status frame to inform the gNB-CU about the unsuccessfully transmitted downlink data to the UE. NOTE: In case of DAPS Handover, the UE CONTEXT MODIFICATION REQUEST message in step 5 may indicate to stop the data transmission only for the DRB(s) not subject to DAPS Handover or may not indicate to stop the data transmission at all. Instead, the DL RRC Message Transfer procedure can be used to carry the handover command to the UE. The UE CONTEXT MODIFICATION REQUEST message that indicates to stop the data transmission for the UE is sent to the source gNB-DU once the gNB-CU knows that the UE has successfully accessed the target gNB-DU, for which the source gNB-DU sends a DDDS frame about the unsuccessfully transmitted downlink data to the gNB-CU. 6. The source gNB-DU forwards the received RRCReconfiguration message to the UE. 7. The source gNB-DU responds to the gNB-CU with the UE CONTEXT MODIFICATION RESPONSE message. 8. A Random Access procedure is performed at the target gNB-DU. The target gNB-DU sends a Downlink Data Delivery Status frame to inform the gNB-CU. Downlink packets, which may include PDCP PDUs not successfully transmitted in the source gNB-DU, are sent from the gNB-CU to the target gNB-DU. NOTE: It is up to gNB-CU implementation whether to start sending DL User Data to gNB-DU before or after reception of the Downlink Data Delivery Status. 9. The UE responds to the target gNB-DU with an RRCReconfigurationComplete message. 10. The target gNB-DU sends an UL RRC MESSAGE TRANSFER message to the gNB-CU to convey the received RRCReconfigurationComplete message. Downlink packets are sent to the UE. Also, uplink packets are sent from the UE, which are forwarded to the gNB-CU through the target gNB-DU. 11. The gNB-CU sends an UE CONTEXT RELEASE COMMAND message to the source gNB-DU. 12. The source gNB-DU releases the UE context and responds the gNB-CU with an UE CONTEXT RELEASE COMPLETE message. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 8.2.1.1 |
1,640 | 5.8.9.4 Sidelink common control information 5.8.9.4.1 General | The sidelink common control information is carried by MasterInformationBlockSidelink. The sidelink common control information may change at any transmission, i.e. neither a modification period nor a change notification mechanism is used. This procedure also applies to NR sidelink discovery. A UE configured to receive or transmit NR sidelink communication/discovery/positioning shall: 1> if the UE has a selected SyncRef UE, as specified in 5.8.6: 2> ensure having a valid version of the MasterInformationBlockSidelink message of that SyncRef UE; | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.8.9.4 |
1,641 | I.2.2.2 Credentials holder using AAA server for primary authentication I.2.2.2.1 General | The procedures described in this clause enables UEs to access an SNPN which makes use of a credential management system managed by a credential provider external to the SNPN. In this scenario the authentication server role is taken by the AAA Server. The AUSF acts as EAP authenticator and interacts with the AAA Server to execute the primary authentication procedure. The architecture for SNPN access using credentials from a Credentials Holder using AAA Server is described in clause 5.30.2.9.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | I.2.2.2 |
1,642 | 4.23.12.8.2 UE Triggered Service Request with I-SMF insertion/change/removal | The following impact is applicable for UE triggered Service Request with I-SMF insertion in clause 4.23.4.3: - In step 8a, when an I-SMF is inserted, if EBI(s) have been allocated before but the SMF+PGW-C has not prepared the CN Tunnel Info for each EPS bearer, the SMF+PGW-C requests the PGW-U+UPF to allocate the CN Tunnel for each EPS bearer for PDU Session(s). PGW-U+UPF allocates the PGW-U tunnel info for the EPS bearer and sends it to the SMF+PGW-C. - In step 8c, the SMF+PGW-C provides also CN Tunnel Info for each EPS bearer to the I-SMF. NOTE: The CN Tunnel Info for each EPS bearer provided to the I-SMF is to prepare for UE mobility to EPC network so that the I-SMF does not need interact with the SMF+PGW-C to get the EPS bearer context(s) at mobility to EPC. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.23.12.8.2 |
1,643 | Create Bearer Response | The Create Bearer Response message shall be sent on the S5/S8 interface by the SGW to the PGW, and on the S11 interface by the MME to the SGW as part of the Dedicated Bearer Activation procedure. The message shall also be sent on the S5/S8 interface by the SGW to the PGW and on the S4 interface by the SGSN to the SGW as part of Secondary PDP Context Activation procedure or the Network Requested Secondary PDP Context Activation procedure. The message shall also be sent on the S2a interface by the TWAN to the PGW as part of the Dedicated bearer activation in WLAN on GTP S2a and on the S2b interface by the ePDG to the PGW as part of the Dedicated S2b bearer activation with GTP on S2b. The message shall also be sent on the S5/S8 or S2a/S2b interface by the SGW or the TWAN/ePDG to the PGW and on the S11/S4 interface by the MME/S4-SGSN to the SGW as part of the Network-initiated IP flow mobility procedure or UE-initiated IP flow mobility procedure, as specified by 3GPP TS 23.161[ Network-Based IP Flow Mobility (NBIFOM); Stage 2 ] [71]. Possible Cause values are specified in Table 8.4-1. Message specific cause values are: - "Request accepted". - "Request accepted partially". - "Context not found". - "Semantic error in the TFT operation". - "Syntactic error in the TFT operation". - "Semantic errors in packet filter(s)". - "Syntactic errors in packet filter(s)". "Unable to page UE". "UE not responding". "Unable to page UE due to Suspension". "UE refuses". - "Denied in RAT". - "Temporarily rejected due to handover/TAU/RAU procedure in progress". - "MME/SGSN refuses due to VPLMN Policy". - "UE is temporarily not reachable due to power saving". - " Request rejected due to UE capability". Table -1: Information Elements in a Create Bearer Response Table -2: Bearer Context within Create Bearer Response Table 7.2.4-3: Overload Control Information within Create Bearer Response | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | Create |
1,644 | 6.2.19 Handling of maximum group data rate limitation control | The network can perform maximum group data rate limitation control to 5G VN groups as specified in 3GPP TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [10]. If the maximum data rate of PDU sessions associated within a 5G VN group has been exceeded the maximum group data rate of the 5G VN group, the SMF may reject the PDU SESSION ESTABLISHMENT REQUEST message against the 5G VN group using S-NSSAI based congestion control as specified in subclause 6.2.8 and 6.4.1.4.2. NOTE 1: The maximum group data rate limitation control does not apply for emergency services or for a UE configured for high priority access in selected PLMN or SNPN. NOTE 2: The maximum group data rate limitation control is performed by the PCF. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.2.19 |
1,645 | 8.7 RRC connection reestablishment | This procedure is used for the case that UE tries to reestablish the RRC connection, as shown in Figure 8.7-1. Figure 8.7-1: RRC connection reestablishment procedure 1. The UE sends a preamble to the gNB-DU. 2. The gNB-DU allocates new C-RNTI and responds with RAR. 3. The UE sends an RRCReestablishmentRequest message to the gNB-DU, which contains old C-RNTI and old PCI. 4. The gNB-DU includes the RRC message and, if the UE is admitted, the corresponding low layer configuration for the UE in the INITIAL UL RRC MESSAGE TRANSFER message and transfers to the gNB-CU. The INITIAL UL RRC MESSAGE TRANSFER message includes the new C-RNTI. If the gNB-DU identifies the UE as a Reduced Capability UE during the random access procedure, a NR RedCap UE Indication is provided in the INITIAL UL RRC MESSAGE TRANSFER message. 5. The gNB-CU includes an RRCReestablishment message and transfers to the gNB-DU. If the UE requests to re-establish RRC connection in the last serving gNB-DU, the DL RRC MESSAGE TRANSFER message shall include old gNB-DU UE F1AP ID. 6. The gNB-DU retrieves the UE context based on the old gNB-DU UE F1AP ID, and replaces old C-RNTI/PCI with new C-RNTI/PCI. It sends the RRCReestablishment message to UE. 7-8. The UE sends an RRCReestablishmentComplete message to the gNB-DU. The gNB-DU encapsulates the RRC message in the UL RRC MESSAGE TRANSFER message and sends to the gNB-CU. 9-10. The gNB-CU triggers an UE Context Modification procedure by sending UE CONTEXT MODIFICATION REQUEST message, which may include DRBs to be modified and released list. The gNB-DU responses with the UE CONTEXT MODIFICATION RESPONSE message. 9'-10'. The gNB-DU triggers an UE Context Modification procedure by sending UE CONTEXT MODIFICIATION REQUIRED message, which may include DRBs to be modified and released list. The gNB-CU responses with UE CONTEXT MODIFICATION CONFIRM message. NOTE: Here it is assumed that the UE accessed the original gNB-DU where the UE context is available for that UE, and either steps 9-10 or steps 9’-10’ may be executed or both could be skipped. NOTE: If the UE accessed from a gNB-DU other than the original one, the gNB-CU should trigger the UE Context Setup procedure toward this new gNB-DU. 11-12. The gNB-CU includes an RRCReconfiguration message into the DL RRC MESSAGE TRANSFER message and transfers to the gNB-DU. The gNB-DU forwards it to the UE. 13-14. The UE sends an RRCReconfigurationComplete message to the gNB-DU, and the gNB-DU forwards it to the gNB-CU. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 8.7 |
1,646 | 5.4.4.2.1 Clearing when tones/announcements provided and the network does not indicate that "CCBS activation is possible" | When in-band tones/announcements are provided (see subclause 5.5.1) and CCBS is not applicable, the call control entity of the network may initiate clearing by sending a DISCONNECT message containing progress indicator #8 "in-band information or appropriate pattern now available", either not containing an Allowed Actions IE or containing an Allowed Actions IE indicating "CCBS activation is not possible", starting timer T306, and entering the "disconnect indication" state. 5.4.4.2.1.1 Receipt of a DISCONNECT message The call control entity of the MS in any state except the "null" state, the "disconnect indication" state, and the "release request" state, shall, upon receipt of a DISCONNECT message with progress indicator #8 and, either not containing an Allowed Actions IE or containing an Allowed Actions IE indicating "CCBS activation is not possible": i) if an appropriate speech traffic channel is not connected, - stop all running call control timers; - send a RELEASE message; - start timer T308; - enter the "release request" state; and - not connect to the in-band tone/announcement. ii) if an appropriate speech traffic channel is connected, attach the user connection for speech if it is not yet attached and enter the "disconnect indication" state. In that state, if upper layers request the clearing of the call, the call control entity of the MS shall: - stop all running call control timers; - send a RELEASE message; - start timer T308; and - enter the "release request" state. 5.4.4.2.1.2 Expiry of timer T306 The call control entity of the network, having entered the "disconnect indication, shall, upon expiry of timer T306, continue clearing by sending a RELEASE message with the cause number originally contained in the DISCONNECT message; starting timer T308; and entering the "release request" state. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.4.4.2.1 |
1,647 | 5.2.3.2.5 Nudm_UECM_Update service operation | Service operation name: Nudm_UECM_Update. Description: Consumer updates some UE related information (e.g. UE capabilities, Intersystem continuity context, SMF+PGW-C FQDN for S5/S8 interface, Analytics ID(s) in the case of NWDAF). Inputs, Required: NF ID, SUPI, NF type, UE context information. Inputs, Optional: "Homogeneous Support of IMS Voice over PS Sessions" indication (if NF Type is AMF), UE MINT support indicator (if NF Type is AMF), SMF+PGW-C FQDN for S5/S8 interface (if NF Type is SMF), UE memory available for SMS indication (if NF Type is SMSF). Outputs, Required: 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.3.2.5 |
1,648 | 4.15 Network Exposure 4.15.1 General | The network capability exposure comprises - Exposure of network events externally as well as internally towards core network NFs; - Exposure of provisioning capability towards external functions; - Exposure of policy and charging capabilities towards external functions; - Exposure of core network internal capabilities for analytics. - Exposure of analytics to external party. - Retrieval of data from external party by NWDAF. - Exposure of number of registered UEs and/or established PDU Sessions for a network slice that is subject to Network Slice Admission Control towards core network NFs or external party. - Exposure of Member UE selection assistance information including list(s) of candidate UEs based on the UE list provided by the AF and possibly additional information that fulfil some Member UE filtering criteria provided by the AF. When subscribing to event reporting the NF consumer(s) provide: - One or multiple Event ID(s). An Event ID identifies the type of event being subscribed to (e.g. PDU Session Release, UE mobility out of an Area of Interest, etc.). - Event Filter Information: Provides Event Parameter Types and Event Parameter Value(s) to be matched against, in order to meet the condition for notifying the subscribed Event ID e.g. the Event Parameter Type could be "Area of interest" and Event Parameter Value list could be list of TAs; The Event Filter depends on the Event ID. The Event Filter Information is provided per Event ID(s) being subscribed to: within a subscription different Event ID(s) may be associated with different Event Filter Information. - Event Reporting Information described in the Table 4.15.1-1 below. Within a subscription all Event ID(s) are associated with a unique Event Reporting Information. - Target of Event Reporting: this may indicate a specific UE or PDU Session, a group of UE(s) or any UE (i.e. all UEs), Within a subscription all Event ID (s) are associated with the same Target of Event Reporting (possibly corresponding to multiple UE or multiple PDU Sessions). - A Notification Target Address (+ Notification Correlation ID) allowing the Event Receiving NF to correlate notifications received from the Event provider with this subscription. A subscription is associated with an unique Notification Target Address (+ Notification Correlation ID). In the case that the NF consumer subscribes to the NF producer on behalf of other NF, the NF consumer includes the Notification Target Address(+Notification Correlation ID) of other NF for the Event ID which is to be notified to other NF directly and the Notification Target Address(+Notification Correlation ID) of itself for the Subscription change related event notification. Each Notification Target Address(+ Notification Correlation ID) is associated with related (set of) Event ID(s). - An Expiry time represents the time upto which the subscription is desired to be kept as active. The NF service consumer may suggest an Expiry time and provide to the NF service producer. Based on the operator's policy, the NF service producer decides whether the subscription can be expired. If the subscription can be expired, the NF service producer determines the Expiry time and provide it in the response to the NF service consumer. If the event subscription is about to expire based on the received Expiry time and the NF service consumer wants to keep receiving notifications, the NF service consumer update the subscription with the NF service producer in order to extend the Expiry time. Once the Expiry time associated with the subscription is reached, the subscription becomes invalid at the NF service producer. If the NF service consumer wants to keep receiving notifications, it shall create a new subscription with the NF service producer. When the subscription is accepted by the Event provider NF, the consumer NF receives from the event provider NF an identifier (Subscription Correlation ID) allowing to further manage (modify, delete) this subscription. NOTE 1: The Notification Correlation ID is allocated by the consumer NF that subscribes to event reporting and the Subscription Correlation ID is allocated by the NF that notifies when the event is met. Both correlation identifiers can be assigned the same value, although in principle they are supposed to be different, as they are optimized for finding the subscription related context within each NF. The consumer NF may use an operation dedicated to subscription modification to add or remove Event ID(s) to this subscription or to modify Event Filter Information. Events are subscribed by the consumer NF(s) by providing Event Filters. The contents of the Event Reporting Information along with the presence requirement of each information element is described in Table 4.15.1-1. Table 4.15.1-1: Event Reporting Information NOTE 2: Explicit unsubscribe by the NF consumer is still possible. Maximum number of reports is applicable to the subscription to one UE or a group of UE(s). When the subscription is applied to a group of UE(s), the initial value of the parameter is applied to each individual member UE. The count of number of reports is per UE and per Event Type granularity also for group member UE. Maximum duration of reporting is applicable to the subscription to one UE, a group of UE(s) or any UE. When the subscription is applied to a group of UE(s), this parameter applies to each group member UE. When the subscription is applied to any UE, this parameter applies to all the impacted UEs. If for a given subscription Maximum duration of reporting is included then the subscription is cancelled locally in the NF as soon as Maximum duration of reporting is reached. If the Maximum number of reports is reached for a given subscription, the NEF cancels the subscription in the affected NFs. If both Maximum Number of reports and Maximum duration of reporting are included then the subscription expires or is cancelled as soon as one of the conditions is met. Sampling ratio is applicable to subscription targeting a group of UEs or any UE. When a sampling ratio is provided, a random subset is selected among the target UEs according to the sampling ratio and only the events related to this subset are reported. A UE remains selected until it is no longer managed by the event provider NF. A UE newly managed by the NF may be selected. Partitioning criteria are applicable to subscription targeting a group of UEs or any UE and may be used when sampling ratio is used. These criteria are used to instruct the NF on how to group the UEs before applying the sampling ratio. When partitioning criteria are provided, the NF groups the targeted UEs (i.e. creates sub-populations/strata) based on the partition criteria parameter. Then, from each sub-population/stratum, the NF selects a subset of UEs by sampling randomly from each sub-population according to the sampling ratio. For a given type of partitioning criteria, the UE belongs to a single sub-population/stratum as long as it is served by the NF. The types of Partitioning Criteria are described in Table 4.15.1-2: Table 4.15.1-2: Types of Partitioning Criteria Group Reporting Guard Time is an optional parameter for group-based monitoring configuration to indicate the time for which the Monitoring Event Reporting(s) related with the UEs in a group can be aggregated before sending them to the consumer NF. The value of the Group Reporting Guard time should be set less than the Maximum duration of reporting. For the continuous monitoring reporting, unless the Maximum duration of reporting has been reached, the Group Reporting Guard timer is restarted when it expires. If the time left until the Maximum duration of reporting is less than the Group Reporting Guard Time, then the Group Reporting Guard timer shall be set to expire when the Maximum duration of reporting expires. If the Maximum duration of reporting is expired, the Group Reporting Guard Time, if running, shall be considered to expire and aggregated Monitoring Event Reporting(s) is sent to destination immediately. Deactivation notification flag and retrieval notification flag enable the mute storage of events for a limited size of events at the Event provider NF, thus reducing the number of notifications and the overall signalling between the Event provider NF and the Event consumer NF. Usage of these parameters is further specified in clause 6.2.7 of TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [50]. Muting Exception Instructions specify actions to be taken by the Event provider NF if the Deactivation notification flag is set and an exception occurs at the Event Producer NF (e.g. the Event provider can no longer buffer notifications because storage space is no longer available). The actions are specified in clause 6.2.7 of TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [50]. Granularity of dynamics indicates negligible changes in the target event of the subscription for which notification is not required. The changes in the Granularity of dynamics are depicted as the range of scalar value (x, y) where it means [the previously notified scalar value - x, the previously notified scalar value + y), the list of event identification(s) (e.g. list of SUPI(s)), or the previous notification. If the Granularity of dynamics is provided, the provider NF shall send the notification only when the changes in the target event are not described in the Granularity of dynamics, except for the first notification. Reporting type is a parameter to reduce the data volume of notification. If the Reporting type is provided, the provider NF shall notify the events that have been newly appeared, disappeared and changed compared to the previous notification, except for the first notification. Table 4.15.1-1 indicates the presence requirements for the Event Reporting Information. Corresponding notifications contain at least the Notification Correlation ID together with the Event ID and the individual target (e.g. UE or PDU Session ID) associated with the notification. If the NF service consumer decides to terminate the event subscription, it unsubscribes the event subscription by sending unsubscription request to the event provider NF. After receiving unsubscription request from the NF service consumer, the event provider NF terminates the event subscription. If the NF service consumer has subscribed to group-based monitoring, then the NF service consumer may subsequently unsubscribe to the whole group or one or more identified group member UEs. Such partial cancellation of group-based monitoring does not affect the other group member UEs, but it only cancels the monitoring event subscription for the identified group member UEs. Partial cancellation of group-based monitoring can be caused by the following reasons: - UE's subscription is discontinued in the UDM; - UE's authorisation to the subscribed event type is revoked; - The subscribing NF explicitly unsubscribes to monitoring of selected UE(s); or - UE is removed from the monitoring target group that was identified in monitoring subscription. If the NF service consumer has subscribed to group-based monitoring and later new group member UEs are added to the group, then the NF service consumer may also subsequently add monitoring event subscription for the new group member UEs. The following clauses describe the external exposure of network capabilities and core network internal event and capability exposure. When the immediate reporting flag is set, the first corresponding event report is included in the subscription response message, if corresponding information is available at the reception of the subscription request of the event. During Monitoring Event Subscription as in clause 4.15.3, Parameter Provisioning as in clause 4.15.6, NIDD configuration as in clause 4.25.3 and Enhanced Coverage Restriction Control as in clause 4.27.1, the optional parameter MTC Provider Information is a reference parameter that may be provided by AF or determined by NEF based on which AF it communicates with. The MTC Provider Information identifies the MTC Service Provider and/or MTC Application. NOTE 3: The MTC Provider Information can be used by Service Providers for, e.g. to distinguish their different customers. NOTE 4: The MTC Provider Information is an optional parameter. The NEF can validate the provided MTC Provider Information and override it to a NEF selected MTC Provider Information based on configuration. How the NEF determines the MTC Provider Information, if not present, is left to implementation (e.g. based on the requesting AF). | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.15 |
1,649 | 6.6.2.2A.4 Minimum requirement CA_48B and CA_48C (network signalled value "CA_NS_10") | Additional spectrum emission requirements are signalled by the network to indicate that the UE shall meet an additional requirement for a specific deployment scenario as part of the cell handover/broadcast message. When "CA_NS_10" is indicated in the cell, the power of any UE emission shall not exceed the levels specified in Table 6.6.2.2A.4-1. Table 6.6.2.2A.4-1: Additional requirements for “CA_NS_10” NOTE: As a general rule, the resolution bandwidth of the measuring equipment should be equal to the measurement bandwidth. However, to improve measurement accuracy, sensitivity and efficiency, the resolution bandwidth may be smaller than the measurement bandwidth. When the resolution bandwidth is smaller than the measurement bandwidth, the result should be integrated over the measurement bandwidth in order to obtain the equivalent noise bandwidth of the measurement bandwidth. | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.6.2.2A.4 |
1,650 | 4.15.6.13.3 Procedure for updating a Multi-member AF session with required QoS | Figure 4.15.6.13.3-1: Procedure for updating a Multi-member AF session with required QoS 1. The AF which controls the Multi-member AF Session with required QoS invokes the Nnef_AFSessionWithQoS_Update Request to update the list of UE addresses and/or to update the QoS and/or to update the QoS monitoring and/or to update the Consolidated Data Rate monitoring. The Nnef_AFSessionWithQoS_Update request includes the Transaction Reference ID and one or more of the parameters that are listed in step 1 of the procedure for creating a Multi-member AF session with required QoS in clause 4.15.6.13.2 which the AF needs to update (or provide for the first time). NOTE 1: For example, the AF can subscribe to QoS monitoring or Consolidated Data Rate monitoring for the Multi-member AF session with required QoS if this has not been done during the procedure for creating a Multi-member AF session with required QoS, as described in clause 4.15.6.13.2. NOTE 2: If AF needs to terminate the Consolidated Data Rate monitoring for the Multi-member AF session with required QoS, the AF does not include the Consolidate Data Rate threshold in the AF request. 2. The NEF authorizes the AF request and may apply policies to control the overall amount of QoS authorized for the AF. If the authorisation is not granted, all following steps are skipped and the NEF replies to the AF with a Result value indicating that the authorisation failed. The NEF performs Consolidated Data Rate monitoring only when both the Consolidated Data Rate threshold and a request to do QoS Monitoring of data rate are provided by the AF. 3-5. When the AF provides an Nnef_AFSessionWithQoS_Update Request in order to add/update/remove the Consolidated Data Rate threshold or the list of UE addresses subject to Consolidated Data Rate monitoring, the NEF updates its local context and does not interact with the PCF(s) (unless required for reasons described in the following). When the AF provides an Nnef_AFSessionWithQoS_Update Request in order to update the list of UE addresses, to update the QoS and/or to update the QoS monitoring, the NEF refers to the locally stored information (i.e. the list of UE addresses, the QoS and the QoS monitoring information) and determines which new UE address is to be added to the list, which of the existing UE address is to be removed from the list and/or for which of the existing UE address(es) the QoS or the QoS monitoring (or both) is to be updated. Then, the NEF continues by invoking one of the following Npcf_PolicyAuthorization procedures for every affected UE address: a) If the NEF determines that a new UE is to be added to the list, the NEF performs steps 2a to 7 of clause 4.15.6.13.2 for the corresponding UE. The NEF uses the latest information on QoS and QoS monitoring for the interaction with the PCF. The NEF adds the address of the new UE to the locally stored list of UE addresses if the authorization was successful. b) If the NEF determines that an existing UE is to be removed from the list, the NEF initiates the Npcf_PolicyAuthorization_Delete as described in clause 5.2.5.3.4 excluding TSCTSF related info towards the PCF for the corresponding UE. The NEF removes the UE address from the locally stored list of UE addresses. c) If the NEF determines that an update of the QoS or the QoS monitoring or both for existing UE addresses is necessary, the NEF initiates the Npcf_PolicyAuthorization_Update to the respective UE's serving PCF(s) on a per AF session basis and step 4 in Figure 4.15.6.6a-1 applies. The NEF removes any UE addresses for which the authorization of the update request has failed from the list of UE addresses. The NEF stores any change to the QoS or the QoS monitoring information. 6. When an interaction with PCF(s) has occurred during step 5, the NEF aggregates the authorization responses from the PCF(s) and sends the Nnef_AFSessionWithQoS Update response (Transaction Reference ID, Result for list of UE addresses) with the aggregated authorization results to the AF. Result for list of UE addresses includes whether the request is granted or not for every UE address in the list. When no interaction with PCF(s) has occurred during step 4 and 5, the NEF sends the Nnef_AFSessionWithQoS Update response (Transaction Reference ID, Result) with the result of the Consolidated Data Rate monitoring related change to the AF. 7. For every UE address that has been added to the locally stored list of UE addresses, the NEF shall send a Npcf_PolicyAuthorization_Subscribe message to the respective PCF(s) to subscribe to notifications of Resource allocation status and may subscribe to other events described in clause 6.1.3.18 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. If an update of event subscription is requested by the AF, the NEF updates the event subscription with the respective PCF(s) for every UE address in the locally stored list of UE addresses. 8. Step 7 in Figure 4.15.6.6-1 applies, at least for those UE addresses for which the establishment or update of transmission resources was requested by the PCF(s). 9. When the establishment or update of transmission resources occurs, the NEF receives Npcf_PolicyAuthorization_Notify messages from the UE's serving PCF(s) about the Resource allocation status. The NEF aggregates the notifications from the respective UEs' serving PCFs before notifying the AF with a Nnef_AFSessionWithQoS_Notify message (Transaction Reference ID, Result for list of UE addresses). Result for list of UE addresses includes, for every UE address in the list, the information whether resources are allocated, resources are not allocated or resources are allocated while the currently fulfilled QoS matches an Alternative Service Requirement. The NEF updates the locally stored list of UE addresses by removing any UEs for which resources could not be allocated. NOTE 3: For those UE address(es) that did not get any resources, the AF may request resource reservation again, by adding them to the list of UE address(es) as described in clause 4.15.6.13.3. 10. As direct event notification is requested, the UPF(s) provide the QoS Monitoring events to the NEF using Nupf_EventExposure service as described in clause 5.2.26.2. 11. When the NEF receives QoS Monitoring events, the NEF sends Nnef_AFsessionWithQoS_Notify message with the individual or aggregated QoS Monitoring events to the AF as described for the QoS Monitoring and the Consolidated Data Rate monitoring in clause 4.15.6.13.1. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.15.6.13.3 |
1,651 | 8.10.1.1.11 Closed loop spatial multiplexing performance - Single-Layer Spatial Multiplexing 4 Tx Antenna Port with CRS assistance information (Cell-Specific Reference Symbols) | The requirements are specified in Table 8.10.1.1.11-2, with the addition of parameters in Table 8.10.1.1.11-1. In Table 8.10.1.1.11-1, Cell 1 is the serving cell, and Cell 2 is the aggressor cell. The downlink physical channel setup is according to Annex C.3.2 for each of Cell 1 and Cell 2, respectively. The CRS assistance information [7] is provided to the UE and includes information on Cell 2. The purpose of the test is to verify the closed loop single layer TM4 performance under assumption that UE applies CRS interference mitigation in the scenario with 4 CRS antenna ports in the serving and aggressor cell. Table 8.10.1.1.11-1: Test Parameters Table 8.10.1.1.11-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.10.1.1.11 |
1,652 | 4.3.7.3 Load re-balancing between MMEs | The MME Load Re-balancing functionality permits UEs that are registered on an MME (within an MME Pool Area) to be moved to another MME. NOTE 1: An example use for the MME Load Re-balancing function is for the O+M related removal of one MME from an MME Pool Area. NOTE 2: Typically, this procedure should not be used when the MME becomes overloaded because the Load Balancing function should have ensured that the other MMEs in the pool area are similarly overloaded. The eNodeBs may have their Load Balancing parameters adjusted beforehand (e.g. the Weight Factor is set to zero if all subscribers are to be removed from the MME, which will route new entrants to the pool area into other MMEs). In addition the MME may off-load a cross-section of its subscribers with minimal impacts on the network and users (e.g. the MME should avoid offloading only the low activity users while retaining the high activity subscribers. Gradual rather than sudden off-loading should be performed as a sudden re-balance of large number of subscribers could overload other MMEs in the pool. With minimal impact on network and the user's experience, the subscribers should be off-loaded as soon as possible). The load re-balancing can off-load part of or all the subscribers. To off-load ECM-CONNECTED mode UEs, the MME initiates the S1 Release procedure with release cause "load balancing TAU required" (clause 5.3.5). The S1 and RRC connections are released and the UE initiates a TAU but provides neither the S-TMSI nor the GUMMEI to eNodeB in the RRC establishment. NOTE 3: Special care needs to be taken when offloading Relay Nodes. This is because there may be UEs connected to the RN and some of these UEs may be registered on other MMEs. The MME should not release all S1 connections which are selected to be released immediately when offloading is initiated. The MME may wait until the S1 Release is performed due to inactivity. When the MME is to be offloaded completely the MME can enforce an S1 Release for all remaining UEs that were not offloaded by normal TAU procedures or by S1 releases caused by inactivity. To off-load UEs which perform TA Updates or Attaches initiated in ECM-IDLE mode, the MME completes that procedure and the procedure ends with the MME releasing S1 with release cause "load balancing TAU required". The S1 and RRC connections are released and the UE initiates a TAU but provides neither the S-TMSI nor the GUMMEI to eNodeB in the RRC establishment. When the UE provides neither the S-TMSI nor the GUMMEI in the RRC establishment, the eNodeB should select an MME based on the Weight Factors of the MMEs in the pool. To off-load UEs in ECM-IDLE state without waiting for the UE to perform a TAU or perform Service request and become ECM-CONNECTED, the MME first pages UE to bring it to ECM-CONNECTED state. If paging the UE fails and ISR is activated, the MME should adjust its paging retransmission strategy (e.g. limit the number of short spaced retransmissions) to take into account the fact that the UE might be in GERAN/UTRAN coverage. Hardware and/or software failures within an MME may reduce the MME's load handling capability. Typically such failures should result in alarms which alert the operator/O+M system. Only if the operator/O+M system is sure that there is spare capacity in the rest of the pool, the operator/O+M system might use the load re-balancing procedure to move some load off this MME. However, extreme care is needed to ensure that this load re-balancing does not overload other MMEs within the pool area (or neighbouring SGSNs) as this might lead to a much wider system failure. When the Dedicated Core Network (DCN) feature is used, the DCN load re-balancing functionality permits UEs that are registered on an MME in the DCN (within a pool area) to be moved to another MME in the same DCN in a manner that achieves load balancing between the CN nodes of the DCN and pool area. The DCN load re-balancing is triggered by the source MME (within a DCN). The details are as follows: - If the UE is in ECM-IDLE state, the NAS Message Redirection procedure (see clause 5.19.1) is triggered at the next intra-MME Tracking Area Update Request enabling eNodeB to load balance between MMEs of the same DCN. To off-load UEs in ECM-IDLE state without waiting for the UE to perform a TAU or perform Service request, the MME first pages the UE to bring it to ECM-CONNECTED state and proceeds as described for the ECM-CONNECTED case below. - If the UE is in ECM-CONNECTED state, the MME performs the GUTI reallocation procedure, includes the unchanged GUTI of the UE and a non-broadcast TAI to induce the UE to perform a TAU procedure, and forces the UE to go to ECM-IDLE state. During the subsequent TAU procedure the MME uses the NAS Message Redirection procedure (see clause 5.19.1) to redirect the UE to another MME within the same DCN. | 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.7.3 |
1,653 | 5.5G Operating bands for V2X Communication | E-UTRA V2X Communication is designed to operate in the the operating bands defined in Table 5.5G-1. Table 5.5G-1 V2X operating band E-UTRA V2X communication is designed to operate concurrent with E-UTRA uplink/downlink on the operating bands combinations listed in Table 5.5G-2. Table 5.5G-2 Inter-band con-current V2X operating bands E-UTRA V2X communication is also designed to operate for intra-band multi-carrier operation in the operating bands defined in Table 5.5G-3. Table 5.5G-3: V2X intra-band multi-carrier operation | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 5.5G |
1,654 | 4.10 NG-RAN Location reporting procedures | This procedure is used by an AMF to request the NG-RAN to report where the UE is currently located when the target UE is in CM-CONNECTED state. The need for the NG-RAN to continue reporting ceases when the UE transitions to CM-IDLE or the AMF sends cancel indication to NG-RAN. This procedure may be used for services that require accurate cell identification (e.g. emergency services, lawful intercept, charging), or for subscription to the service by other NFs. When Dual Connectivity is activated, PSCell information is only reported if requested by the AMF. Figure 4.10-1: NG-RAN Location Reporting Procedure 1. AMF to NG-RAN: Location Reporting Control (Reporting Type, Location Reporting Level, (Area Of Interest, Request Reference ID)). The AMF sends a Location Reporting Control message to the NG-RAN. The Location Reporting Control message shall identify the UE for which reports are requested and shall include Reporting Type and Location Reporting Level. The Location Reporting Control message may also include Area Of Interest and Request Reference ID. Location Reporting Level could be TAI+ Cell Identity. Reporting Type indicates whether the message is intended to trigger a single standalone report about the current Cell Identity serving the UE or start the NG-RAN to report whenever the UE changes cell, or ask the NG-RAN to report whenever the UE moves out or into the Area Of Interest. If the Reporting Type indicates to report whenever the UE changes cell and if PScell reporting is requested and Dual Connectivity is in use, the Master RAN node shall also report to the AMF whenever the PSCell changes. If the Reporting Type indicates to start the NG-RAN to report when UE moves out of or into the Area Of Interest, the AMF also provides the requested Area Of Interest information in the Location Reporting Control message. The AMF may include a Request Reference ID in the Location Report Control message to identify the request of reporting for an Area Of Interest. If multiple Areas Of Interest are included in the message, the Request Reference ID identifies each Area of Interest. NOTE 1: Requesting reports whenever the UE changes cell can increase signalling load on multiple interfaces. Requesting reports for all changes in PSCell ID can further increase signalling load. Hence it is recommended that any such reporting is only applied for a limited number of subscribers. 2. NG-RAN to AMF: Location Report (UE Location, UE Presence in Area Of Interest, Request Reference ID, Timestamp). The NG-RAN sends a Location Report message informing the AMF about the location of the UE which shall be represented as the requested Location Reporting Level. If PSCell reporting is requested and Dual Connectivity is activated, then the Master NG-RAN node shall also include the PSCell ID. With NR satellite access, cell and TAI reporting by NG-RAN refer to a fixed cell and fixed TA in which a UE is geographically located. As part of the User Location Information, NG_RAN also reports one or more TACs for the Selected PLMN as described in TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [10], but it is not guaranteed that the UE is always located in one of these TACs. When UE is in CM-CONNECTED with RRC_INACTIVE state, if NG-RAN has received Location Reporting Control message from AMF with the Reporting Type indicating single stand-alone report, the NG-RAN shall perform NG-RAN paging before reporting the location to the AMF. The NG-RAN should send the Location Report promptly and shall not wait to attempt to create a Dual Connectivity configuration. However, if PSCell reporting is requested and the PSCell ID is known to the Master RAN node, then it shall be included in the Location Report. In the case of RAN paging failure, the RAN reports UE's last known location with time stamp. When UE is in CM-CONNECTED with RRC_INACTIVE state, if NG-RAN has received Location Reporting Control message from AMF with the Reporting Type indicating continuous reporting whenever the UE changes cell, the NG-RAN shall send a Location Report message to the AMF including the UE's last known location with time stamp. If the UE was using Dual Connectivity immediately before entering CM-CONNECTED with RRC_INACTIVE state and PSCell reporting is requested, then the Location Report shall also include the PSCell ID. When UE is in CM-CONNECTED, if NG-RAN has received Location Reporting Control message from AMF with the Reporting Type of Area Of Interest based reporting, the NG-RAN shall track the UE presence in Area Of Interest and send a Location Report message to AMF including the UE Presence in the Area Of Interest (i.e. IN, OUT, or UNKNOWN) as described in clause D.2 and the UE's current location (including the PSCell ID if PSCell reporting is requested and Dual Connectivity is activated) when the UE is in RRC_CONNECTED state, or, when the UE is in RRC_INACTIVE state, the UE's last known location (including the PSCell ID if PSCell reporting is requested and the UE was using Dual Connectivity immediately before entering CM-CONNECTED with RRC_INACTIVE state) with time stamp if the NG-RAN perceives that the UE presence in the Area Of Interest is different from the last one reported. When the NG-RAN detects that the UE has moved out of or into multiple areas of interest, it sends multiple pairs of UE Presence in the Area Of Interest and the Request Reference ID in one Location Report message to AMF. If UE transitions from RRC_INACTIVE state to RRC_CONNECTED state, NG-RAN shall check the latest location (including the PSCell ID if PSCell reporting is requested and Dual Connectivity is activated) of UE and follow the rules when UE is in RRC_CONNECTED. The AMF may receive Location Report even if the UE presence in Area Of Interest is not changed. The AMF stores the latest received PSCell ID with its associated timestamp. The AMF stores the latest received PSCell ID with its associated timestamp, when available. In addition to the above, if the UE is served by an authorized MSBR and the AMF serving this UE receives the Location Report including the TAI/NR CGI for the MBSR that UE is accessing, the AMF shall, if supported, update the corresponding Warning Area List NG-RAN specified in TS 23.041[ Technical realization of Cell Broadcast Service (CBS) ] [86] 3. AMF to NG-RAN: Cancel Location Report (Reporting Type, Request Reference ID). The AMF can send a Cancel Location Reporting message to inform the NG-RAN that it should terminate the location reporting for a given UE corresponding to the Reporting Type or the location reporting for Area Of Interest indicated by Request Reference ID. This message is needed when the reporting type was requested for continuously reporting or for the Area Of Interest. The AMF may include the Request Reference ID which indicates the requested Location Reporting Control for the Area Of Interest, so that the NG-RAN should terminate the location reporting for the Area Of Interest. NOTE 2: Location reporting related information of the source NG-RAN node is transferred to the target NG-RAN node during Xn handover. In this release the location reporting procedure is applicable only to 3GPP access. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.10 |
1,655 | 10.5.5.18 Update type | The purpose of the update type information element is to specify the area the updating procedure is associated with. The update type is a type 1 information element. The update type information element is coded as shown in figure 10.5.132/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.150/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Figure 10.5.132/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Update type information element Table 10.5.150/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Update type information element | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 10.5.5.18 |
1,656 | – UEInformationRequest | The UEInformationRequest message is used by the network to retrieve information from the UE. Signalling radio bearer: SRB1 RLC-SAP: AM Logical channel: DCCH Direction: Network to UE UEInformationRequest message -- ASN1START -- TAG-UEINFORMATIONREQUEST-START UEInformationRequest-r16 ::= SEQUENCE { rrc-TransactionIdentifier RRC-TransactionIdentifier, criticalExtensions CHOICE { ueInformationRequest-r16 UEInformationRequest-r16-IEs, criticalExtensionsFuture SEQUENCE {} } } UEInformationRequest-r16-IEs ::= SEQUENCE { idleModeMeasurementReq-r16 ENUMERATED{true} OPTIONAL, -- Need N logMeasReportReq-r16 ENUMERATED {true} OPTIONAL, -- Need N connEstFailReportReq-r16 ENUMERATED {true} OPTIONAL, -- Need N ra-ReportReq-r16 ENUMERATED {true} OPTIONAL, -- Need N rlf-ReportReq-r16 ENUMERATED {true} OPTIONAL, -- Need N mobilityHistoryReportReq-r16 ENUMERATED {true} OPTIONAL, -- Need N lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension UEInformationRequest-v1700-IEs OPTIONAL } UEInformationRequest-v1700-IEs ::= SEQUENCE { successHO-ReportReq-r17 ENUMERATED {true} OPTIONAL, -- Need N coarseLocationRequest-r17 ENUMERATED {true} OPTIONAL, -- Need N nonCriticalExtension UEInformationRequest-v1800-IEs OPTIONAL } UEInformationRequest-v1800-IEs ::= SEQUENCE { flightPathInfoReq-r18 FlightPathInfoReportConfig-r18 OPTIONAL, -- Need N successPSCell-ReportReq-r18 ENUMERATED {true} OPTIONAL, -- Need N nonCriticalExtension SEQUENCE {} OPTIONAL } FlightPathInfoReportConfig-r18 ::= SEQUENCE { maxWayPointNumber-r18 INTEGER (1..maxWayPoint-r18), includeTimeStamp-r18 ENUMERATED {true} OPTIONAL } -- TAG-UEINFORMATIONREQUEST-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
1,657 | 19.4.2.9A.6 Country based Emergency Numbers FQDN | The Country based Emergency Numbers FQDN shall be constructed as specified for the Visited Country Emergency FQDN in clause 19.4.2.9A.4, but with replacing the label "epdg" by the label "en". The Country based Emergency Numbers FQDN shall be constructed as follows: "sos.en.epc.mcc<MCC>.visited-country.pub.3gppnetwork.org" NOTE: Even though a label named "visited-country" is present, operators in the home country can use the same mechanism to provide emergency numbers and associated type(s). As an example, the Country based Emergency Numbers FQDN for MCC 345 is coded in the DNS as: "sos.en.epc. mcc345.visited-country.pub.3gppnetwork.org". | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 19.4.2.9A.6 |
1,658 | 5.38 Support for Multi-USIM UE 5.38.1 General | A network and a Multi-USIM UE may support one or more of the following features for Multi-USIM UE operation: - Connection Release as described in clause 5.38.2; - Paging Cause Indication for Voice Service, as described in clause 5.38.3; - Reject Paging Request, as described in clause 5.38.4; - Paging Restriction, as described in clause 5.38.5; - Paging Timing Collision Control, as described in clause 5.38.6. In the Registration procedure (as specified in clause 4.2.2.2.2), when a Multi-USIM UE has more than one USIM active, supports and intends to use one or more Multi-USIM specific features, it indicates to the AMF the corresponding Multi-USIM feature(s) are supported (except for the Paging Timing Collision Control feature). Based on the received indication of the supported Multi-USIM features from the UE, the AMF shall indicate to the UE the support of the Multi-USIM features based on the Multi-USIM features supported by network and any preference policy by the network, if available. When a UE returns to having only one USIM active from a Multi-USIM UE that previously indicated to the network it supported Multi-USIM feature(s), the UE shall indicate all the Multi-USIM features are not supported to the network for that USIM. The AMF shall only indicate the support of Paging Restriction feature together with the support of either Connection Release feature or Reject Paging Request feature. The Multi-USIM UE includes the support of individual features for Connection Release, Paging Cause Indication for Voice Service, Reject Paging Request and Paging Restriction as specified in clause 5.4.4a. NOTE: The Paging Timing Collision Control feature being based on the Mobility Registration Update, and it doesn't require capability exchange between the UE and network. The network shall not indicate support for any Multi-USIM feature to the UE as part of the Emergency Registration procedure. A Multi-USIM UE shall use a separate PEI for each USIM when it registers with the network. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.38 |
1,659 | 30.2 Structure of TMGI | Temporary Mobile Group Identity (TMGI) is used within MBS to uniquely identify a broadcast MBS session or a multicast MBS session. TMGI is composed as shown in figure 30.2.1. Figure 30.2.1: Structure of TMGI The TMGI is composed of three parts: 1) MBS Service ID consisting of three octets. MBS Service ID consists of a 6-digit fixed-length hexadecimal number between 000000 and FFFFFF. MBS Service ID uniquely identifies an MBS service within a PLMN. 2) Mobile Country Code (MCC) consisting of three digits. The MCC identifies uniquely the country of domicile of the MB-SMF, except for the MCC value of 901, which does not identify any country and is assigned globally by ITU; 3) Mobile Network Code (MNC) consisting of two or three digits (depending on the assignment to the PLMN by its national numbering plan administrator). The MNC identifies the PLMN which the MB-SMF belongs to, except for the MNC value of 56 when the MCC value is 901, which does not identify any PLMN. For more information on the use of the TMGI, see 3GPP TS 23.247[ Architectural enhancements for 5G multicast-broadcast services ] [140]. NOTE: The structure of TMGI for MBS in 5GS is similar to the structure of TMGI for MBMS in EPS defined in clause 15.2. In a SNPN (Stand-alone Non-Public Network), TMGI is used together with NID (Network Identifier) to identify an MBS Session. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 30.2 |
1,660 | 5.19.7 NAS level congestion control 5.19.7.2 General NAS level congestion control | This clause only applies to NAS Mobility Management congestion control. Under general overload conditions the AMF may reject NAS messages from UEs using any 5G-AN. When a NAS request is rejected, a Mobility Management back-off time may be sent by the AMF to the UE. While the Mobility Management back-off timer is running, the UE shall not initiate any NAS request except for Deregistration procedure and procedures not subject to congestion control (e.g. high priority access, emergency services) and mobile terminated services. After any such Deregistration procedure, the back-off timer continues to run. While the Mobility Management back-off timer is running, the UE is allowed to perform Mobility Registration Update if the UE is already in CM-CONNECTED state. If the UE receives a paging request or a NAS notification message from the AMF while the Mobility Management back off timer is running, the UE shall stop the Mobility Management back-off timer and initiate the Service Request procedure or the Mobility Registration Update procedure over 3GPP access and/or non-3GPP access as applicable. Over non-3GPP access, if the UE is in CM-IDLE state when the back-off timer is stopped, it shall initiate the UE-triggered Service Request procedure as soon as it switches back to CM-CONNECTED state. In order to allow the UE to report the PS Data Off status change in PDU Session Modification Request message, the UE behaves as follows while keeping the NAS MM back-off timer running in the UE: - When the UE is in CM-IDLE state and has not moved out of the Registration Area, the UE is allowed to send a Service Request message with an indication that the message is exempted from NAS congestion control. When the UE is in CM-IDLE mode and has moved out of the Registration Area, the UE is allowed to send a Mobility Registration Update request message, with a Follow-on request, and with an indication that the message is exempted from NAS congestion control. - When the UE is in CM-CONNECTED state, the UE sends a PDU Session Modification Request with PS Data Off status change carried in UL NAS Transport message with an indication that the message is exempted from NAS congestion control. When the NAS MM congestion control is activated at AMF, if the UE indicates that the NAS MM message is exempted from NAS congestion control, the AMF shall not reject the NAS MM message and shall forward the NAS SM message to the corresponding SMF with an indication that the NAS SM message was indicated to be exempted from NAS congestion control. The SMF ensures that the NAS SM message is not subject to congestion control otherwise the SMF rejects the message, e.g. the SMF shall reject PDU Session Modification received if it is not for Data Off status reporting. The Mobility Management back-off timer shall not impact Cell/RAT/Access Type and PLMN change. Cell/RAT/TA/Access Type change does not stop the Mobility Management back-off timer. The Mobility Management back-off timer shall not be a trigger for PLMN reselection or SNPN reselection. The back-off timer is stopped as defined in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [47] when a new PLMN or SNPN, that is not an equivalent PLMN or is not an equivalent SNPN, is accessed. To avoid that large amounts of UEs initiate deferred requests (almost) simultaneously, the AMF should select the Mobility Management back-off timer value so that the deferred requests are not synchronized. If the UE required to report 5GSM Core Network Capability change, or the Always-on PDU Session Requested indication while the NAS MM congestion control timer was running and was unable to initiate MM signalling, the UE defers the related MM signalling until the MM congestion control timer expires and initiates after the expiry of the timer. In the case of a UE with scheduled communication pattern, the AMF may consider the UE's communication pattern while selecting a value for the Mobility Management back-off timer so that the UE does not miss its only scheduled communication window. The AMF should not reject Registration Request message for Mobility Registration Update that are performed when the UE is already in CM-CONNECTED state. The AMF may reject the Service Request message and a UL NAS Transfer with a Mobility Management back-off time when the UE is already in CM-CONNECTED state. If UE receives a DL NAS Transfer message from the AMF while the Mobility Management back off timer is running, the UE shall stop the Mobility Management back-off timer. For CM-IDLE state mobility, the AMF may reject Registration Request messages for Mobility Registration Update by including a Mobility Management back off time value in the Registration Reject message. If UE registered in the same PLMN for 3GPP access and non-3GPP access and receives a Mobility Management back-off time from the AMF, the back-off time (and corresponding start and stop) is applied equally to both 3GPP access and non-3GPP access. If UE registered in different PLMNs for 3GPP access and non-3GPP access respectively and receives a Mobility Management back-off time, the back-off time is only applied to the PLMN that provides the time to the UE. If the AMF rejects Registration Request messages or Service Request with a Mobility Management back-off time which is larger than the sum of the UE's Periodic Registration Update timer and the Implicit Deregistration timer, the AMF should adjust the mobile reachable timer and/or Implicit Deregistration timer such that the AMF does not implicitly deregister the UE while the Mobility Management back-off timer is running. NOTE: This is to minimize signalling after the Mobility Management back-off timer expires. If the AMF deregisters the UE with an indication of re-registration required, the UE behaviour for handling the back-off timer(s) is as specified in 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.19.7 |
1,661 | 4.3.3.4 Abnormal cases on the network side | The following abnormal cases can be identified: a) RR connection failure: Upon detection of a RR connection failure before the IDENTITY RESPONSE message is received, the network shall release all MM connections (if any) and abort any ongoing MM specific procedure. b) Expiry of timer T3270: The identification procedure is supervised by the network by the timer T3270. At expiry of the timer T3270 the network may release the RR connection. In this case, the network shall abort the identification procedure and any ongoing MM specific procedure, release all MM connections if any, and initiate the RR connection release procedure as described in 3GPP TS 44.018[ None ] [84] subclause 3.5, 3GPP TS 25.331[ None ] [23c] (UTRAN Iu mode only), or in 3GPP TS 44.118[ None ] [111] (GERAN Iu mode only). Figure 4.3/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Identification 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.3.4 |
1,662 | 9.9.3.63 NB-S1 DRX parameter | The purpose of the NB-S1 DRX parameter information element is to indicate that the UE intends to use the UE specific DRX parameter in NB-S1 mode and for the network to indicate the negotiated UE specific DRX parameter to be used at paging in NB-S1 mode. The NB-S1 DRX parameters information element is coded as shown in figure 9.9.3.63.1 and table 9.9.3.63.1. The NB-S1 DRX parameters is a type 4 information element with a length of 3 octets. Figure 9.9.3.63.1: NB-S1 DRX parameter information element Table 9.9.3.63.1: NB-S1 DRX parameter 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.63 |
1,663 | 5.3.13.2 Insert CSG Subscriber Data procedure | The Insert CSG Subscriber Data procedure is illustrated in Figure 5.3.13.2-1. Figure 5.3.13.2-1: Insert CSG Subscriber Data procedure 1. The CSS sends an Insert CSG Subscriber Data (IMSI, CSG Subscription Data) message to the MME. 2. The MME updates the stored CSG Subscription Data and acknowledges the Insert CSG Subscriber Data message by returning an Insert CSG Subscriber Data Ack (IMSI) message to the CSS. The update result should be contained in the Ack message. The MME initiates appropriate action according to the changed CSG subscriber data. If the UE is in ECM-CONNECTED state and connected via a CSG or hybrid cell, the MME shall check the received CSG subscriber data. If the MME detects that the CSG membership to that cell has changed or expired, the MME initiates the procedure in clause 5.16. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.3.13.2 |
1,664 | 6.2 Diverse mobility management 6.2.2 General requirements | The 5G network shall allow operators to optimize network behaviour (e.g. mobility management support) based on the mobility patterns (e.g. stationary, nomadic, spatially restricted mobility, full mobility) of a UE or group of UEs. The 5G system shall enable operators to specify and modify the types of mobility support provided for a UE or group of UEs. The 5G system shall optimize mobility management support for a UE or group of UEs that use only mobile originated communications. The 5G system shall support inter- and/or intra- access technology mobility procedures within 5GS with minimum impact to the user experience (e.g. QoS, QoE). | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.2 |
1,665 | 6.43.1 Description | The tactile and multi-modal communication service can be applied in multiple fields, e.g. industry, robotics and telepresence, virtual reality, augmented reality, healthcare, road traffic, serious gaming, education, culture and smart grid [38]. These services support applications enabling input from more than one sources and/or output to more than one destinations to convey information more effectively. As figure 6.43.1-1 illustrates, the input and output can be different modalities including: Video/Audio media; Information received by sensors about the environment, e.g. brightness, temperature, humidity, etc.; Haptic data: can be feelings when touching a surface (e.g., pressure, texture, vibration, temperature), or kinaesthetic senses (e.g. gravity, pull forces, sense of position awareness). Figure 6.43.1-1. Multi-modal interactive system For immersive multi-modal VR applications, synchronization between different media components is critical in order to avoid having a negative impact on the user experience (i.e. viewers detecting lack of synchronization), particularly when the synchronization threshold between two or more modalities is less than the latency KPI for the application. Example synchronization thresholds [41] [42] [43] [44] are summarised in table 6.43.1-1. Table 6.43.1-1: Typical synchronization thresholds for immersive multi-modality VR applications | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.43.1 |
1,666 | 19.2.2.2 Service Provided by the BM-SC in visited PLMN | Figure 31a: Deactivation of an MBMS multicast service in roaming scenario with service provided in the visited PLMN 1. Upon receiving the leave indication, the GGSN sends an STR to the BM-SC in visited PLMN, indicating that the roaming UE is requesting to leave the multicast service. The session to be terminate is uniquely identified by the Diameter session-id. 2. Upon reception of the STR, the BM-SC in visited PLMN verifies that the IP multicast address corresponds to a valid MBMS bearer service and sends an STR to the BM-SC in home PLMN. 3. The BM-SC in home PLMN responds the BM-SC in visited PLMN with an ST-Answer. 4. Upon reception of the STA, the BM-SC in visited PLMN sends an STA to the GGSN that orignated the Leave Indication. The APN shall be the same that was provided during service activation. 5. The GGSN deletes the MBMS UE Context and sends an STR to the BM-SC in visited PLMN to confirm the successful deactivation of the MBMS UE Context. 6. The BM-SC in visited PLMN, then, delets the MBMS UE Context and sends a confirmation to the GGSN in an STA message. | 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.2.2 |
1,667 | 9.1.1.5 Applicability of requirements for UEs supporting coverage enhancement | For 2Rx capable UEs supporting coverage enhancement mode A (ce-ModeA in UE-EUTRA-Capability [7]), all the tests for CE Mode A specified in 9.8.1 and 9.8.2 are tested on any of the 2Rx supported RF bands by connecting all 2Rx with data source from system simulator. The SNR requirements should be applied with 3dB less than the number specified with UE DL Category M1. For 4Rx capable UEs supporting coverage enhancement mode A (ce-ModeA in UE-EUTRA-Capability [7]), all the tests for CE Mode A specified in 9.8.1 and 9.8.2 are tested on any of the 4Rx supported RF bands by connecting all 4Rx with data source from system simulator. The SNR requirements should be applied with 6dB less than the number specified with UE DL Category M1. | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 9.1.1.5 |
1,668 | 8.21.2 SAI field | The coding of SAI (Service Area Identifier) is depicted in Figure 8.21.2-1. Only zero or one SAI field shall be present in ULI IE. Figure 8.21.2-1: SAI field The Location Area Code (LAC) consists of 2 octets. Bit 8 of Octet b+3 is the most significant bit and bit 1 of Octet b+4 the least significant bit. The coding of the location area code is the responsibility of each administration. Coding using full hexadecimal representation (binary, not ASCII encoding) shall be used. The Service Area Code (SAC) consists of 2 octets. Bit 8 of Octet b+5 is the most significant bit and bit 1 of Octet b+6 the least significant bit. The SAC is defined by the operator. See 3GPP TS 23.003[ Numbering, addressing and identification ] [2] clause 12.5 for more information. | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 8.21.2 |
1,669 | 5.4.4.6 Abnormal cases on the network side | The following abnormal cases can be identified: a) Lower layer failure Upon detection of a lower layer failure before the IDENTITY RESPONSE is received, the network shall abort any ongoing EMM procedure. b) Expiry of timer T3470 The identification procedure is supervised by the network by the timer T3470. The network shall, on the first expiry of the timer T3470, retransmit the IDENTITY REQUEST message and reset and restart the timer T3470. This retransmission is repeated four times, i.e. on the fifth expiry of timer T3470, the network shall abort the identification procedure and any ongoing EMM procedure. c) Collision of an identification procedure with an attach procedure If the network receives an ATTACH REQUEST message before the ongoing identification procedure has been completed and no attach procedure is pending on the network (i.e. no ATTACH ACCEPT/REJECT message has still to be sent as an answer to an ATTACH REQUEST message), the network shall proceed with the attach procedure. d) Collision of an identification procedure with an attach procedure when the identification procedure has been caused by an attach procedure If the network receives an ATTACH REQUEST message before the ongoing identification procedure has been completed and an attach procedure is pending (i.e. an ATTACH ACCEPT/REJECT message has to be sent as an answer to an earlier ATTACH REQUEST message), then: - If one or more of the information elements in the ATTACH REQUEST message differ from the ones received within the previous ATTACH REQUEST message, the network shall proceed with the new attach procedure; or - If the information elements do not differ, then the network shall not treat any further this new ATTACH REQUEST. e) Collision of an identification procedure with a UE initiated detach procedure Detach containing cause "switch off" within the Detach type IE: If the network receives a DETACH REQUEST message before the ongoing identification procedure has been completed, the network shall abort the identification procedure and shall progress the detach procedure. Detach containing other causes than "switch off" within the Detach type IE: If the network receives a DETACH REQUEST message before the ongoing identification procedure has been completed, the network shall complete the identification procedure and shall respond to the detach procedure as described in clause 5.5.2. f) Collision of an identification procedure with a tracking area updating procedure If the network receives a TRACKING AREA UPDATE REQUEST message before the ongoing identification procedure has been completed, the network shall progress both procedures. g) Collision of an identification procedure with a service request procedure If the network receives an EXTENDED SERVICE REQUEST message for CS fallback or 1xCS fallback before the ongoing identification procedure has been completed, the network shall progress both procedures. h) Lower layers indication of non-delivered NAS PDU due to handover If the IDENTITY REQUEST message could not be delivered due to an intra MME handover and the target TA is included in the TAI list, then upon successful completion of the intra MME handover the MME shall retransmit the IDENTITY REQUEST message. If a failure of the handover procedure is reported by the lower layer and the S1 signalling connection exists, the MME shall retransmit the IDENTITY REQUEST message. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.4.4.6 |
1,670 | 8.2.2.4.5 Minimum Requirement Multi-Layer Spatial Multiplexing 2 Tx Antenna Port (Superposed transmission) | The requirements are specified in Table 8.2.2.4.5-2, with the addition of the parameters in Table 8.2.2.4.5-1 and the downlink physical channel setup according to Annex C.3.2. The purpose is to verify the minimun performance of closed-loop spatial multiplexing with 2 transmitter antennas superposed with simultaneous PDSCH interference. Table 8.2.2.4.5-1: Test Parameters for Minimum Requirement Multi-Layer Spatial Multiplexing 2 Tx Antenna Port - Superposed transmission (FRC) Table 8.2.2.4.5-2: Minimum Performance for Minimum Requirement Multi-Layer Spatial Multiplexing 2 Tx Antenna Port - Superposed transmission (FRC) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.2.2.4.5 |
1,671 | 5.5.2.4 Measurement object removal | The UE shall: 1> for each measObjectId included in the received measObjectToRemoveList that is part of measObjectList in VarMeasConfig: 2> remove the entry with the matching measObjectId from the measObjectList within the VarMeasConfig; 2> remove all measId associated with this measObjectId from the measIdList within the VarMeasConfig, if any; 2> if a measId is removed from the measIdList: 3> remove the measurement reporting entry for this measId from the VarMeasReportList, if included; 3> stop the periodical reporting timer or timer T321 or timer T322, whichever is running, and reset the associated information (e.g. timeToTrigger) for this measId. NOTE: The UE does not consider the message as erroneous if the measObjectToRemoveList includes any measObjectId value that is not part of the current UE configuration. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.5.2.4 |
1,672 | 8.3.2.2 Dual-Layer Spatial Multiplexing | For dual-layer transmission on antenna ports 7 and 8 upon detection of a PDCCH with DCI format 2B, the requirements are specified in Table 8.3.2.2-2, with the addition of the parameters in Table 8.3.2.2-1 and the downlink physical channel setup according to Annex C.3.2. The purpose of these tests is to verify the rank-2 performance for full RB allocation. Table 8.3.2.2-1: Test Parameters for Testing CDM-multiplexed DM RS (dual layer) Table 8.3.2.2-2: Minimum performance for CDM-multiplexed DM RS (FRC) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.3.2.2 |
1,673 | 6.5.2.1.1 Minimum requirement | The RMS average of the basic EVM measurements for 10 subframes excluding any transient period for the average EVM case, and 60 subframes excluding any transient period for the reference signal EVM case, for the different modulations schemes shall not exceed the values specified in Table 6.5.2.1.1-1 for the parameters defined in Table 6.5.2.1.1-2. For EVM evaluation purposes, [all PRACH preamble formats 0-4 and] all PUCCH formats 1, 1a, 1b, 2, 2a and 2b are considered to have the same EVM requirement as QPSK modulated. Table 6.5.2.1.1-1: Minimum requirements for Error Vector Magnitude Table 6.5.2.1.1-2: Parameters for Error Vector Magnitude | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.5.2.1.1 |
1,674 | 5.2.27.3.7 Ntsctsf_QoSandTSCAssistance_Unsubscribe operation | Service operation name: Ntsctsf_QoSandTSCAssistance_unsubscribe Description: The consumer requests the network to unsubscribe to receive an event about the AF session with requested QoS or the AF session with requested QoS including Alternative Service Requirements. Inputs, Required: Subscription Correlation Id, (Set of) Event ID(s) as specified in clause 6.1.3.18 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. Inputs, Optional: None. Outputs, Required: Result. Output (optional): None. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.27.3.7 |
1,675 | 4.4.3.4 Ciphering and deciphering | The sender shall use its locally stored NAS COUNT as input to the ciphering algorithm. The receiver shall use the NAS sequence number included in the received message and an estimate for the NAS overflow counter as defined in subclause 4.4.3.1 to form the NAS COUNT input to the deciphering algorithm. The input parameters to the NAS ciphering algorithm are the BEARER ID, DIRECTION bit, NAS COUNT, NAS encryption key and the length of the key stream to be generated by the encryption algorithm. When applying initial NAS message protection to the REGISTRATION REQUEST, DEREGISTRATION REQUEST or SERVICE REQUEST message as described in subclause 4.4.6, the length of the key stream is set to the length of the entire plain NAS message that is included in the NAS message container IE, i.e. the value part of the NAS message container IE, that is to be ciphered. When applying initial NAS message protection to the CONTROL PLANE SERVICE REQUEST message as described in subclause 4.4.6, the length of the key stream is set to the length of: a) the value part of the CIoT small data container IE that is to be ciphered; or b) the value part of the NAS message container IE that is to be ciphered. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.4.3.4 |
1,676 | 5.2.6.7.5 Nnef_TrafficInfluence_Notify operation | Service operation name: Nnef_TrafficInfluence_Notify Description: Forward the notification of UP path management event report to AF. Known NF Service Consumers: AF. Inputs, Required: AF Transaction Id, Event ID. The AF Transaction Id identifies the AF request for traffic influence that the event report is related to. The event may be the UP path management event defined in clause 5.6.7 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. Inputs, Optional: Event information (defined on a per Event ID basis), capability of supporting EAS IP replacement in 5GC. 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.6.7.5 |
1,677 | 8.1.2.3A Applicability and test rules for different dual connectivity configuration and bandwidth combination set | The performance requirement for dual connectivity UE demodulation tests in Clause 8 are defined independent of dual connectivity configurations and bandwidth combination sets specified in Clause 5.6C.1. For UEs supporting difrerent dual connectivity configurations and bandwidth combination sets, the applicability and test rules are defined for the tests for the configurations with 2CCs in Table 8.1.2.3A-1 and 3 DL CCs in Table 8.1.2.3A-2. For simplicity, dual connectivity configuration below refers to combination of dual connectivity configuration and bandwidth set. Both CA performance requirements and dual connectivity performance requirements are applied for dual connectivity capable UE. Table 8.1.2.3A-1: Applicability and test rules for dual connectivity UE demodulation tests with 2DL CCs Table 8.1.2.3A-2: Applicability and test rules for dual connectivity UE demodulation tests with 3DL CCs | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.1.2.3A |
1,678 | 28.2 Home Network Domain | The Home Network Domain for 5GC shall be in the format specified in IETF RFC 1035 [19] and IETF RFC 1123 [20] and shall be structured as: "5gc.mnc<MNC>.mcc<MCC>.3gppnetwork.org", where "<MNC>" and "<MCC>" fields correspond to the MNC and MCC of the operator's PLMN. Both the "<MNC>" and "<MCC>" fields are 3 digits long. If 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 NF service endpoint format for inter PLMN routing. As an example, the Home Network Domain for MCC 345 and MNC 12 is coded as: "5gc.mnc012.mcc345.3gppnetwork.org". The Home Network Domain for a Stand-alone Non-Public Network (SNPN) shall be in the format specified in IETF RFC 1035 [19] and IETF RFC 1123 [20] and, if not pre-configured in the NF, shall be structured as: "5gc.nid<NID>.mnc<MNC>.mcc<MCC>.3gppnetwork.org", where <MNC> and <MCC> shall be encoded as specified above, and the NID shall be encoded as hexadecimal digits as specified in clause 12.7. As an example, the Home Network Domain for MCC 345, MNC 12 and NID 000007ed9d5 (hexadecimal: assignment mode = 0, PEN = 00007ed9, NID code = d5) is coded as: "5gc.nid000007ed9d5.mnc012.mcc345.3gppnetwork.org". NOTE: For interworking with an SNPN (e.g. discovery of AMFs from an SNPN by a shared NG RAN), the above sub-domain can be used when the MCC, MNC and NID uniquely identifies the SNPN. For signalling within an SNPN, the above sub-domain can be used regardless of whether the MCC, MNC and NID uniquely identifies the SNPN or not. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 28.2 |
1,679 | – NR-Sidelink-Preconf | -- ASN1START -- TAG-NR-SIDELINK-PRECONF-DEFINITIONS-START NR-Sidelink-Preconf DEFINITIONS AUTOMATIC TAGS ::= BEGIN IMPORTS SL-RelayUE-ConfigU2U-r18, SL-RemoteUE-ConfigU2U-r18, SL-RemoteUE-Config-r17, SL-DRX-ConfigGC-BC-r17, SL-Freq-Id-r16, maxNrofFreqSL-1-r18, SL-FreqConfigCommon-r16, SL-RadioBearerConfig-r16, SL-RLC-BearerConfig-r16, SL-EUTRA-AnchorCarrierFreqList-r16, SL-NR-AnchorCarrierFreqList-r16, SL-MeasConfigCommon-r16, SL-UE-SelectedConfig-r16, TDD-UL-DL-ConfigCommon, maxNrofFreqSL-r16, maxNrofSLRB-r16, maxSL-LCID-r16 FROM NR-RRC-Definitions; -- TAG-NR-SIDELINK-PRECONF-DEFINITIONS-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
1,680 | 6.3.11 CHF discovery and selection | The CHF discovery and selection function is supported by the SMF, the AMF, the SMSF and the PCF. It is used by the SMF to select a CHF that manages the online charging or offline charging for a PDU Session of a subscriber. It is used by the AMF to select a CHF that manages the online charging or offline charging for 5G connection and mobility of a subscriber. It is used by the SMSF to select a CHF that manages the online charging or offline charging for the SMS over NAS transactions of a subscriber. It is used by the PCF to select a CHF that manages the spending limits for a subscriber and/or a PDU Session of a subscriber. For the PCF to select the CHF, the address(es) of the CHF, including the Primary CHF address and the Secondary CHF address, may be: - stored in the UDR as part of the PDU Session policy control subscription information as defined in clause 6.2.1.3 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]. - stored in the UDR as part of the UE context policy control subscription information as defined in clause 6.2.1.3 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]. - stored in the UDR as part of the Access and Mobility policy control subscription information as defined in clause 6.2.1.3 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]. - locally configured in the PCF based on operator policies. - discovered using NRF as described in in clause 6.1 of TS 32.290[ Telecommunication management; Charging management; 5G system; Services, operations and procedures of charging using Service Based Interface (SBI) ] [67]. NOTE 1: The operator can perform the above UDR provisioning or local configuration in a consistent manner such that the same CHF address is used for SM policy, AM policy and UE policy. If NRF discovery is used, it is up to the PCF logic (or SCP logic when working in Delegated Discovery mode) and operator configuration to guarantee the CHF address consistency. The address(es) of the CHF shall be applicable for all services provided by the CHF. The CHF address(es) that a stored in the UDR or configured in the PCF may be complemented by the associated CHF instance ID(s) and CHF set ID(s) (see clause 6.3.1.0) stored or configured in the same location. The CHF address(es) retrieved from the UDR and possible associated CHF instance ID(s) and CHF set ID(s) take precendence over the locally configured CHF address(es) and possible associated CHF instance ID(s) and CHF set ID(s), and over the CHF address(es) discoverred by the NRF. If no CHF address(es) is received from the UDR, the PCF selects, based on operator policies, either the CHF addresse(es) provided by NRF, or the locally configured CHF address(es) and possible associated CHF instance ID(s) and CHF set ID(s). If the PCF has a CHF set ID but no CHF instance ID associated to the CHF address(es) in the same location, the CHF instance within the CHF set may change. If the PCF is not able to reach the CHF address(es), it should query the NRF for other CHF instances within the CHF set. If the PCF received a CHF set ID and a CHF instance ID associated to the CHF address(es) in the same location, the CHF service instance within the CHF may change. If an PCF is not able to reach the CHF address(es), it should query the NRF for other CHF service instances within the CHF. To enable the SMF to select the same CHF that is selected by the PCF for a PDU Session, the PCF provides the selected CHF address(es) and, if available, the associated CHF instance ID(s) and/or CHF set ID(s) in the PDU Session related policy information to the SMF as described in Table 6.4-1 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45] and the SMF applies the CHF address and if available, the associated CHF instance ID(s) and/or CHF set ID(s) passed from the PCF as defined in clause 5.1.8 of TS 32.255[ Telecommunication management; Charging management; 5G data connectivity domain charging; Stage 2 ] [68]. Otherwise, the SMF selection of the CHF as defined in clause 5.1.8 of TS 32.255[ Telecommunication management; Charging management; 5G data connectivity domain charging; Stage 2 ] [68] applies. If operator policies indicates the AMF should select the same CHF that is selected by the PCF for a UE, the PCF provides the selected CHF address(es) and, if available, the associated CHF instance ID(s) and/or CHF set ID(s) in the Access and mobility related policy information to the AMF as described in Table 6.5-1 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45] and the AMF may apply the CHF address and, if available, the associated CHF instance ID(s) and/or CHF set ID(s) passed from the PCF as defined in clause 5.1.3 of TS 32.256[ Charging management; 5G connection and mobility domain charging; Stage 2 ] [114]. Otherwise, the AMF selection of the CHF as defined in clause 5.1.3 of TS 32.256[ Charging management; 5G connection and mobility domain charging; Stage 2 ] [114] applies. How the CHF is selected by the SMSF is defined in clause 5.4 of TS 32.274[ Telecommunication management; Charging management; Short Message Service (SMS) charging ] [118]. If the NF consumer performs discovery and selection via NRF, the CHF selection function in NF consumers selects a CHF instance based on the available CHF instances obtained from the NRF. The CHF selection functionality in NF consumer or in SCP should consider one of the following factors: 1. CHF Group ID of the UE's SUPI. NOTE 2: The NF Consumer can infer the CHF Group ID the UE's SUPI belongs to, based on the results of CHF discovery procedures with NRF. 2. SUPI; the NF consumer selects a CHF instance based on the SUPI range the UE's SUPI belongs to or based on the results of a discovery procedure with NRF using the UE's SUPI as input for CHF discovery. In the case of delegated discovery and selection in SCP, the NF consumer shall include all available factors in the request towards SCP. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 6.3.11 |
1,681 | 8.24.2 RAN TSS reporting towards the UE | The signaling flow for RAN TSS reporting towards the UE in RRC_CONNECTED state is shown in Figure 8.24.2-1. Figure 8.24.2-1: RAN TSS reporting towards the UE in RRC_CONNECTED state NOTE 1: In this signalling flow, it is assumed that RAN TSS reporting is already enabled at the gNB-DU. 1. The AMF sends the INITIAL CONTEXT SETUP REQUEST message to the gNB-CU, containing the Clock Quality Reporting Control Information IE within the Time Synchronization Assistance Information IE. The clock quality reporting control information indicates the clock quality detail level to provide to the UE, i.e. “metrics” or “acceptable/not acceptable indication”. If clock quality detail level equals “acceptable/not acceptable indication”, the clock quality reporting control information also contains the clock quality acceptance criteria. NOTE 2: The clock quality reporting control information can also be provided in the UE CONTEXT MODIFICATION REQUEST, HANDOVER REQUEST, or PATH SWITCH REQUEST ACKNOWLEDGE messages. 2. The gNB-CU replies to the AMF by sending the INITIAL CONTEXT SETUP RESPONSE message. 3. The gNB-CU sends the latest clock quality information to the UE by sending the DLInformationTransfer message. The clock quality information provided to the UE depends on the clock quality detail level received in step 1 (i.e., “metrics” or “acceptable/not acceptable indication”). 4. Later, the gNB-DU detects a primary source event: a) a RAN TSS attribute cannot meet a pre-configured threshold (i.e. status is degraded); b) a RAN TSS attribute meets the pre-configured threshold again (i.e. status is no longer degraded); c) event a) occurred and b) has not yet been reached, the gNB-DU performs periodic reporting or a previously reported RAN TSS attribute value can no longer be met. NOTE 3: Additional primary source events, if any, are up to gNB-DU implementation. 5. Upon detecting the primary source event, the gNB-DU provides an updated RAN TSS report to the gNB-CU by sending a TIMING SYNCHRONISATION STATUS REPORT message. 6. Same as step 3. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 8.24.2 |
1,682 | 7.5.1G Minimum requirements for V2X | The V2X UE shall fulfil the minimum requirement specified in Table 7.5.1G-1 for all values of an adjacent channel interferer up to -22 dBm. However it is not possible to directly measure the ACS, instead the lower and upper range of test parameters are chosen in Table 7.5.1G-2 and Table 7.5.1G-3 where the throughput shall be ≥ 95% of the maximum throughput of the reference measurement channels as specified in Annex A.8.2. Table 7.5.1G-1: Adjacent channel selectivity for V2X Table 7.5.1G-2: Test parameters for Adjacent channel selectivity for V2X, Case 1 Table 7.5.1G-3: Test parameters for Adjacent channel selectivity for V2X, Case 2 When UE is configured for simultaneous E-UTRA V2X sidelink and E-UTRA downlink reception for inter-band E-UTRA V2X / E-UTRA bands specified in Table 5.5G-2, the requirements in subclause 7.5.1G apply for the E-UTRA V2X sidelink reception and the requirements in subclause 7.5.1 apply for the E-UTRA downlink reception while all downlink carriers are active. For intra-band contiguous multi-carrier operation, the V2X UE shall fulfil the minimum requirement specified in Table 7.5.1G-4 to Table 7.5.1G-6 where the throughput shall be ≥ 95% of the maximum throughput of the reference measurement channels as specified in Annex A.8.2. Table 7.5.1G-4: Adjacent channel selectivity for intra-band contiguous multi-carrier for V2X UE Table 7.5.1G-5: Test parameters for Adjacent channel selectivity, Case 1 Table 7.5.1G-6: Test parameters for Adjacent channel selectivity, Case 2 | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 7.5.1G |
1,683 | 12.3.5.1.2 Parameters | 12.3.5.1.2.1 Overload Control Sequence Number The GTP-C protocol requires retransmitted messages to have the same contents as the original message (see clause 7.6). Due to GTP-C retransmissions, the overload control information received by a GTP-C entity at a given time may be less recent than the overload control information already received from the same GTP-C entity. The Overload Control Sequence Number aids in sequencing the overload control information received from an overloaded GTP-C entity. The Overload Control Sequence Number contains a value that indicates the sequence number associated with the Overload Control Information IE. This sequence number shall be used to differentiate between two OCI IEs generated at two different instants, by the same GTP-C entity. The Overload Control Sequence Number parameter shall be supported (when supporting the overload control feature) and shall always be present in the Overload Control Information IE. The GTP-C entity generating this information shall increment the Overload Control Sequence Number whenever modifying some information in the OCI IE. The Overload Control Sequence Number shall not be incremented otherwise. The GTP-C entity may use the time, represented in an unsigned integer format, of the generation of the overload control information, to populate the Overload Control Sequence Number. When multiple instances of the OCI IE are provided in the same message by a given GTP-C entity, each of the Overload Control Sequence Numbers shall have the same value. This parameter shall be used by the receiver of the OCI IE to properly collate out-of-order OCI IEs, e.g. due to GTP-C retransmissions. This parameter shall also be used by the receiver of the OCI IE to determine whether the newly received overload control information has changed compared to the overload control information previously received from the same GTP-C entity. If the newly received overload control information has the same Overload Control Sequence Number as the previously received overload control information from the same GTP-C peer, then the receiver may simply discard the newly received overload control information whilst continuing to apply the overload abatement procedures, as per the previous value. NOTE 1: The timer corresponding to the Period of Validity (see 12.3.5.1.2.2) is not restarted if the newly received overload control information has the same Overload Control Sequence Number as the previously received overload control information. If the overload condition persists and the overloaded GTP-C entity needs to extend the duration during which the overload information applies, the sender needs to provide a new overload control information with an incremented Overload Control Sequence Number (even if the parameters within the overload control information have not changed). NOTE 2: The GTP-C Sequence Number cannot be used for collating out-of-order overload information as e.g. overload control information may be sent in both GTP-C requests and responses, using independent GTP-C sequence numbering. If the receiving GTP-C entity already received and stored overload control information, which is still valid, from the overloaded GTP-C entity, the receiving entity shall update its overload control information, only if the Overload-Sequence-Number received in the new overload control information is larger than the value of the Overload Control Sequence Number associated with the stored information. However due to roll-over of the Overload Control Sequence Number or restart of the GTP-C entity, the Overload Control Sequence Number may be reset to an appropriate base value by the peer GTP-C entity, hence the receiving entity shall be prepared to receive (and process) an Overload Control Sequence Number parameter whose value is less than the previous value. 12.3.5.1.2.2 Period of Validity The Period of Validity indicates the length of time during which the overload condition specified by the OCI IE is to be considered as valid (unless overridden by subsequent new overload control information). An overload condition shall be considered as valid from the time the OCI IE is received until the period of validity expires or until another OCI IE with a new set of information (identified using the Overload Control Sequence Number) is received from the same GTP-C entity (at which point the newly received overload control information shall prevail). The timer corresponding to the period of validity shall be restarted each time an OCI IE with a new set of information (identified using the Overload Control Sequence Number) is received. When this timer expires, the last received overload control information shall be considered outdated and obsolete, i.e. any associated overload condition shall be considered to have ceased. The Period of Validity parameter shall be supported (when supporting overload control). The Period of Validity parameter achieves the following: - it avoids the need for the overloaded GTP-C entity to include the Overload Control Information IE in every GTP-C messages it signals to its GTP-C peers when the overload state does not change; thus it minimizes the processing required at the overloaded GTP-C entity and its GTP-C peers upon sending/receiving GTP-C signalling; - it allows to reset the overload condition after some time in the GTP-C peers having received an overload indication from the overloaded GTP-C entity, e.g. if no signalling traffic takes place between these GTP-C entities for some time due to overload mitigation actions. This also removes the need for the overloaded GTP-C entity to remember the list of GTP-C entities to which it has sent a non-null overload reduction metric and to which it would subsequently need to signal when the overload condition ceases, if the Period of Validity parameter was not defined. 12.3.5.1.2.3 Overload Reduction Metric The Overload Reduction Metric shall have a value in the range of 0 to 100 (inclusive) which indicates the percentage of traffic reduction the sender of the overload control information requests the receiver to apply. An Overload Reduction Metric of "0" always indicates that the GTP-C entity is not in overload (that is, no overload abatement procedures need to be applied) for the indicated scope. Considering the processing requirement of the receiver of the Overload Control Information, e.g. to perform overload control based on the updated Overload Reduction Metric, the sender should refrain from advertising every small variation, e.g. with the granularity of 1 or 2, in the Overload Reduction Metric which does not result in useful improvement for mitigating the overload situation. During the typical operating condition of the sender, a larger variation in the Overload Reduction Metric, e.g. 5 or more units, should be considered as reasonable enough for advertising a new Overload Reduction Metric Information and thus justifying the processing requirement (to handle the new information) of the receiver. NOTE: The range of Overload Reduction Metric, i.e. 0 to 100, does not mandate the sender to collect its own overload information at every increment/decrement and hence to advertise the change of Overload Reduction Metric with a granularity of 1%. Based on various implementation specific criteria, such as the architecture, session and signalling capacity, the current load/overload situation and so on, the sender is free to define its own logic and periodicity with which its own overload control information is collected. The computation of the exact value for this parameter is left as an implementation choice at the sending GTP-C entity. The Overload Reduction Metric shall be supported (when supporting overload control) and shall always be present in the OCI IE. The inclusion of the OCI IE signals an overload situation is occuring, unless the Overload Reduction Metric is set to 0, which signals that the overload condition has ceased. Conversely, the absence of the OCI IE in a message does not mean that the overload has abated. 12.3.5.1.2.4 List of APNs The List of APNs IE indicates one or more APNs for which the Overload Control Information is applicable. When present in the OCI IE, the scope of the overload control information shall be the list of the indicated APNs for the PGW that sends the overload control information. At most one instance of the List of APNs IE shall be included within one Overload Control Information instance. NOTE 1: The maximum number of APNs in the List of APNs is set to 10. More than 10 occurrences of APN within one single instance of the List of APNs IE is treated as a protocol error by the receiver. If the List of APNs IE has not been included, the scope of the Overload Control Information shall be the entire GTP-C entity (unless restricted by other parameters in the Overload Control Information IE). The List of APNs parameter shall be supported (when supporting overload control). The List of APNs may be present or absent in the Overload Control Information IE (depending on the scope of the reported overload control information). NOTE 2: The instance number of both the node-level and APN-level overload control information is "0" and the instance number is therefore not used to indicate if the scope of the overload control information is on PGW node level or APN level. This parameter may be provided by the PGW only and it shall be used by the MME/S4-SGSN and the TWAN/ePDG only. The maximum number of APNs, for which the PGW may advertise the Overload Control Information, shall be limited to 10, i.e. the maximum number of occurrences of APNs within and across various instances of the Overload Control Information IE shall be limited to 10 for a given PGW. Hence, if the PGW supports more than 10 APNs, it shall advertise the overload control for at most 10 of the most important APNs. In future, if needed, this limit may be increased to allow the PGW to advertise the overload information for more APNs. In that case, the receiver that does not support the higher limit shall only handle the first 10 APNs and ignore the overload information for the remaining APNs to enable future compatibility. NOTE 3: Considering various aspects such as: the processing and storage requirements at the overloaded GTP-C entity and the receiver, the number of important APNs for which overload control advertisement could be necessary, interoperability between the nodes of various vendors, etc. it was decided to define a limit on maximum number of APNs for advertising the overload control information. It was decided to fix this limit to 10 whilst also ensuring that the mechanism exists to extend this limit in future releases, if required. | 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.5.1.2 |
1,684 | 5.5.1.2.6A Abnormal cases in the UE, SMS services not accepted | The UE shall proceed as follows: 1) if the attach was successful for EPS services only and the ATTACH ACCEPT message contained a value included in the SMS services status IE not treated in clause 5.5.1.2.4A, the UE shall proceed as follows: a) The UE shall stop timer T3410 if still running. The tracking area updating attempt counter shall be incremented, unless it was already set to 5; b) If the tracking area updating attempt counter is less than 5: - the UE shall start timer T3411, shall set the EPS update status to EU1 UPDATED and shall enter state EMM-REGISTERED.NORMAL-SERVICE. When timer T3411 expires the normal tracking area updating procedure for EPS services and "SMS only" or the combined tracking area updating procedure for EPS services and "SMS only" is triggered; c) If the tracking area updating attempt counter is equal to 5: - the UE shall start timer T3402, shall set the EPS update status to EU1 UPDATED and shall enter state EMM-REGISTERED.NORMAL-SERVICE. When timer T3402 expires the normal tracking area updating procedure for EPS services and "SMS only" or the combined tracking area updating procedure for EPS services and "SMS only" is triggered; and 2) otherwise, the abnormal cases specified in clause 5.5.1.2.6 apply. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.5.1.2.6A |
1,685 | 8.3.2.1A Single-layer Spatial Multiplexing (with multiple CSI-RS configurations) | For single-layer transmission on antenna ports 7 or 8 upon detection of a PDCCH with DCI format 2C, the requirements are specified in Table 8.3.2.1A-2 and 8.3.2.1A-3, with the addition of the parameters in Table 8.3.2.1A-1 and the downlink physical channel setup according to Annex C.3.2. The purpose of these tests is to verify rank-1 performance on one of the antenna ports 7 or 8 with and without a simultaneous transmission on the other antenna port, and to verify rate matching with multiple CSI reference symbol configurations with non-zero and zero transmission power. Table 8.3.2.1A-1: Test Parameters for Testing CDM-multiplexed DM RS (single layer) with multiple CSI-RS configurations Table 8.3.2.1A-2: Minimum performance for CDM-multiplexed DM RS without simultaneous transmission (FRC) with multiple CSI-RS configurations Table 8.3.2.1A-3: Minimum performance for CDM-multiplexed DM RS with interfering simultaneous transmission (FRC) with multiple CSI-RS configurations | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.3.2.1A |
1,686 | 6.36.3 Monitoring and Reporting | The 5G system shall be able to support mechanisms to monitor for timing source failure (e.g., GNSS). The 5G system shall be able to detect when reference timing signals (e.g., from GNSS or other timing source) are no longer viable for network time synchronization. The 5G system shall support a mechanism to determine if there is degradation of the 5G time synchronization. The 5G system shall be able to support mechanisms to indicate to devices (e.g., UEs, applications) that there is an alternate time source available for use (e.g., 5G system internal holdover capability, atomic clock, Sync over Fiber, TBS, GNSS), taking into account the holdover capability of the devices. The 5G system shall be able to detect when a timing source fails or is restored for network time synchronization. The 5G system shall support mechanisms to monitor different time sources and adopt the most appropriate. The 5G system shall support a mechanism to report timing errors such as divergence from UTC and time sync degradation to UEs and 3rd party applications. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.36.3 |
1,687 | 7.2 Network Function Services 7.2.1 General | In the context of this specification, an NF service is offering a capability to authorised consumers. Network Functions may offer different capabilities and thus, different NF services to distinct consumers. Each of the NF services offered by a Network Function shall be self-contained, reusable and use management schemes independently of other NF services offered by the same Network Function (e.g. for scaling, healing, etc). The discovery of the NF instance and NF service instance is specified in clause 6.3.1. NOTE 1: There can be dependencies between NF services within the same Network Function due to sharing some common resources, e.g. context data. This does not preclude that NF services offered by a single Network Function are managed independently of each other. Figure 7.2.1-1: Network Function and NF Service Each NF service shall be accessible by means of an interface. An interface may consist of one or several operations. Figure 7.2.1-2: Network Function, NF Service and NF Service Operation System procedures, as specified in TS 23.502[ Procedures for the 5G System (5GS) ] [3] can be built by invocation of a number of NF services. The following figure shows an illustrative example on how a procedure can be built; it is not expected that system procedures depict the details of the NF Services within each Network Function. Figure 7.2.1-3: System Procedures and NF Services NOTE 2: The SCP can be used for indirect communication between NF/NF service instances. For simplicity the SCP is not shown in the procedure. The following clauses provide for each NF the NF services it exposes through its service based interfaces. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 7.2 |
1,688 | 30.4 Structure of MBS Frequency Selection Area ID | The concept of MBS Frequency Selection Area ID is defined in clause 6.5.4 of 3GPP TS 23.247[ Architectural enhancements for 5G multicast-broadcast services ] [140]. The MBS Frequency Selection Area (FSA) ID is used for broadcast MBS session to guide the frequency selection of the UE. The MBS FSA ID identifies a preconfigured area within, and in proximity to, which the cell(s) announces the MBS FSA ID and the associating frequency (for details see 3GPP TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [141]). MBS FSA ID and their mapping to frequencies are provided to RAN nodes via OAM. An MBS FSA ID shall be a string of 6 hexadecimal digits. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 30.4 |
1,689 | 5.8.15.2 NR Sidelink U2N Remote UE threshold conditions | A UE capable of NR sidelink U2N Remote UE operation shall: 1> if the threshold conditions specified in this clause were previously not met: 2> if threshHighRemote is not configured; or the RSRP measurement of the PCell, or the cell on which the UE camps, is below threshHighRemote by hystMaxRemote if configured, or 2> if the UE has no serving cell: 3> consider the threshold conditions to be met (entry); 1> else: 2> if the RSRP measurement of the PCell, or the cell on which the UE camps, is above threshHighRemote if configured: 3> consider the threshold conditions not to be met (leave); The L2 U2N Remote UE not configured with MP considers the cell indicated by sl-ServingCellInfo in the SL-AccessInfo-L2U2N-r17 received from the connected L2 U2N Relay UE as the PCell/camping cell. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.8.15.2 |
1,690 | A.11 KNG-RAN* derivation function for target gNB | When deriving a KNG-RAN* from current KgNB or from fresh NH and the target physical cell ID in the UE and NG-RAN for handover purposes and transition from RRC_INACTIVE to RRC_CONNECTED states the following parameters shall be used to form the input S to the KDF. - FC = 0x70 - P0 = PCI (target physical cell id) - L0 = length of PCI (i.e. 0x00 0x02) - P1 = ARFCN-DL (the absolute frequency of SSB of the target PCell as specified in clause 13.3 of TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [52]) - L1 = length of ARFCN-DL (i.e. 0x00 0x03) The input key KEY shall be the 256-bit NH when the index NCC in the handover increases, otherwise the current 256-bit KgNB(when source is gNB) or KeNB (when source is ng-eNB). | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | A.11 |
1,691 | 6.23.2 Requirements | The 5G system shall provide a mechanism for supporting real-time E2E QoS monitoring within a system. NOTE 1: The end points in E2E are the termination points of the communication service within the boundary of the 5G system. The 5G system shall support combined QoS monitoring for a group of UEs. NOTE 1A: Combined monitoring stands for the monitoring of several UEs for which the monitoring results are reported together. An example for combined QoS monitoring is that the 5G networks monitors the service bit rates of all connections associated with the group of UEs. The 5G network shall provide an interface to an application for QoS monitoring (e.g. to initiate QoS monitoring, request QoS parameters, events, logging information). The 5G system shall be able to provide real time QoS parameters and events information to an authorized application/network entity. NOTE 2: The QoS parameters to be monitored and reported can include latency (e.g. UL/DL or round trip), jitter, and packet loss rate. The 5G system shall be able to log the history of the communication events. NOTE 3: The communication history may include timestamps of communication events and position-related information. Examples of such information are the positions of UEs and of radio base stations associated with communication events. Communication events include instances when the required QoS is not met. The 5G system shall support different levels of granularity for QoS monitoring (e.g. per flow or set of flows). The 5G system shall be able to provide event notification upon detecting an error that the negotiated QoS level cannot be met/guaranteed. The 5G system shall be able to provide information that identifies the type and the location of a communication error (e.g. cell ID). The 5G system shall be able to provide notification of communication events to authorized entities per pre-defined patterns. NOTE 4: An example for a communication event is that the service bit rate drops below a pre-defined threshold for QoS parameters. When such an event occurs, the authorized entity is notified, and the event is logged. The 5G system shall support event-based QoS monitoring. NOTE 5: An example for a triggering event is a position change of the pertinent UE. A position change can, for instance, be inferred from a 5G position service that tracks the UE. The 5G system shall be able to respond to a request from an authorized entity to provide real-time QoS monitoring information within a specified time after receiving the request (e.g., within 5 s). NOTE 6: The response time can be specified by the user. The 5G system shall support real time QoS monitoring with a specified update/refresh rate. NOTE 6a: The update/refresh rate can be specified by the user. NOTE 6b: The update/refresh rates for QoS monitoring measurements and reporting can be different. The 5G system shall be able to provide statistical information of service parameters and error types while a communication service is in operation. NOTE 7: The time span for collection and evaluation of statistical values can be specified by the user. The 5G system shall provide information on the current availability of a specific communication service in a particular area (e.g. cell ID) upon request of an authorized entity. The 5G system shall provide a means by which an MNO informs a third party of network events (failure of network infrastructure affecting UEs in a particular area, etc.). Based on MNO policy, the 5G system shall provide a mechanism to automatically report service degradations, communications loss, and sustained connection loss in a specific geographic area (e.g., a cell sector, a cell or a group of cells) to a third party. NOTE 8: These reports use a standard format. The specific values, thresholds, and conditions upon which alarms occur can include the measured values for end-to-end latency, service bit rate, communication service availability, end-to-end latency jitter, etc. for a UE, the UE’s location, and the time(s) during which the degradation occurred. The 5G system shall provide a mechanism for an authorised third party to report to an MNO service degradations, communication loss, and sustained connection loss. NOTE 9: These reports use a standard format. The specific values, thresholds, and conditions upon which alarms occur can include the measured values for end-to-end latency, service bit rate, communication service availability, end-to-end latency jitter, etc. for a UE, the UE’s location, and the time(s) during which the degradation occurred. NOTE 10: What the MNO does with such reports is out of scope of 3GPP. Based on operator request, for direct network connection scenarios in non-public networks, the 5G system shall be able to activate/deactivate efficient QoS monitoring with a finer granularity (e.g. per data packet) in a specific QoS flow (e.g. supporting URLLC services) to report on data packets not meeting the required QoS level. NOTE 11: The QoS parameters to be monitored and reported can include latency (e.g. UL or DL). NOTE 12: The above requirement does not assume UE impacts. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.23.2 |
1,692 | 4.15.3.2.2 UDM service operations information flow | The procedure is used by the NEF to subscribe to event notifications, to modify group-based subscriptions to event notifications, including removal or addition of certain UEs in a UE group and to explicitly cancel a previous subscription (see clause 4.15.1). Cancelling is done by sending Nudm_EventExposure_Unsubscribe request identifying the subscription to cancel. The notification steps 4 and 5 are not applicable in cancellation case. Figure 4.15.3.2.2-1: Nudm_EventExposure_Subscribe, Unsubscribe and Notify operations 1. The NEF subscribes to one or several monitoring events by sending Nudm_EventExposure_Subscribe request. The NEF subscribes to one or several Event(s) (identified by Event ID) and provides the associated notification endpoint of the NEF. Event Reporting Information defines the type of reporting requested. If the reporting event subscription is authorized by the UDM, the UDM records the association of the event trigger and the requester identity. The subscription may include Maximum number of reports and/or Maximum duration of reporting IE and optionally MTC Provider Information. If subscription to group-based event notifications are removed for certain UEs in a group of UEs for which there is an event notification subscription, the NEF provides impacted UE information (e.g. SUPI, MSISDN or External Identity) and operation indication (cancellation) to UDM via Nudm_EventExposure_Subscribe without cancelling the entire group-based event notification subscription. If the Maximum Number of Reports applies to the event subscription, the NEF sets the stored number of reports of the indicated UE(s) to Maximum Number of Reports. If subscription to group-based event notifications are added for certain UEs in a group of UEs for which there is an event notification subscription, the NEF provides impacted UE information (e.g. SUPI, MSISDN or External Identity) and operation indication (addition) to UDM via Nudm_EventExposure_Subscribe. 2a. [Conditional] Some events, require that UDM sends Namf_EventExposure_Subscribe request to the AMF serving that UE. As the UDM itself is not the Event Receiving NF, the UDM shall additionally provide the notification endpoint of itself besides the notification endpoint of NEF. Each notification endpoint is associated with the related (set of) Event ID(s). This is to assure the UDM can receive the notification of subscription change related event. The UDM sends the Namf_EventExposure_Subscribe request to all serving AMF(s) (if subscription applies to a UE or a group of UE(s)), or to all the AMF(s) in the same PLMN as UDM (if subscription applies to any UE). The UDM stores the subscription even if the target UE or group member UE is not registered at the time of subscription. NOTE 1: If the single target UE, or group member UE, registers later on with an AMF which does not have event subscription or group event subscription(s) for that UE or UE group, then the UDM creates subscriptions to those event(s) with the AMF during the Registration procedure as specified in clause 4.2.2.2.2. If the subscription applies to a group of UE(s), the UDM shall include the same notification endpoint of itself, i.e. Notification Target Address (+ Notification Correlation Id), in the subscriptions to all UE's serving AMF(s). NOTE 2: The same notification endpoint of UDM is to help the AMF identify whether the subscription for the requested group event is same or not when a new group member UE is registered. If Nudm_EventExposure_Subscribe with update is received in step 1 indicating removal of event notification subscription for certain UEs in a group of UEs for which there is an event notification subscription, the UDM provides impacted UE information (e.g. SUPI, MSISDN) and operation indication (cancellation) to AMF via Namf_EventExposure_Subscribe without cancelling the entire group-based event notification subscription, for the event monitored by AMF. If Nudm_EventExposure_Subscribe with update is received in step 1 indicating addition of event notification subscription for certain UEs in a group of UEs for which there is an event notification subscription, the UDM provides impacted UE information (e.g. SUPI, MSISDN) and operation indication (addition) to AMF via Namf_EventExposure_Subscribe for the event monitored by AMF. 2b. [Conditional] AMF acknowledges the execution of Namf_EventExposure_Subscribe. 3. UDM acknowledges the execution of Nudm_EventExposure_Subscribe. If the subscription is applicable to a group of UE(s) and the Maximum number of reports is included in the Event Report information in step 1, the Number of UEs (including all group member UEs irrespective of their registration state) within this group is included in the acknowledgement. If AMF provides the first event report in step 2b, the UDM includes the event report in the acknowledgement. 4a - 4b. [Conditional - depending on the Event] The UDM detects the monitored event occurs and sends the event report, by means of Nudm_EventExposure_Notify message, to the associated notification endpoint of the NEF, along with the time stamp. NEF may store the information in the UDR along with the time stamp using either Nudr_DM_Create or Nudr_DM_Update service operation as appropriate. If Nudm_EventExposure_Subscribe with update is received in step 1 indicating removal of event notification subscription for certain UEs in a group of UEs for which there is an event notification subscription, the UDM shall stop the event notification for the impacted UEs. If Maximum number of Reports is applied, the UDM shall set the number of reports of the indicated UE(s) to Maximum Number of Reports for the events monitored by UDM. If Nudm_EventExposure_Subscribe with update is received in step 1 indicating addition of event notification subscription for certain UEs in a group of UEs for which there is an event notification subscription, the UDM shall create subscription to the event notification for the impacted UEs so as to detect the monitored event and send the event report for such impacted UEs. 4c - 4d. [Conditional - depending on the Event] The AMF detects the monitored event occurs and sends the event report, by means of Namf_EventExposure_Notify message, to the associated notification endpoint of the NEF, along with the time stamp. NEF may store the information in the UDR along with the time stamp using either Nudr_DM_Create or Nudr_DM_Update service operation as appropriate. If the AMF has a maximum number of reports stored for the UE, the AMF shall decrease its value by one for the reported event. If Namf_EventExposure_Subscribe with update is received in step 2a indicating removal of event notification subscription for certain UEs in a group of UEs for which there is an event notification subscription, the AMF shall stop the event notifications for the impacted UEs. If Maximum number of Reports is applied, the AMF shall set the number of reports of the indicated UE(s) to Maximum Number of Reports. If Namf_EventExposure_Subscribe with update is received in step 2a indicating addition of event notification subscription for certain UEs in a group of UEs for which there is an event notification subscription, the AMF shall create subscription to the event notification for the impacted UEs so as to detect the monitored event and send the event report for such impacted UEs. For both step 4a and step 4c, when the maximum number of reports is reached and if the subscription is applied to a UE, The NEF unsubscribes the monitoring event(s) to the UDM and the UDM unsubscribes the monitoring event(s) to AMF serving that UE. For both step 4a and step 4c, when the maximum number of reports is reached for an individual group member UE, the NEF uses the Number of UEs received in step 3 and the Maximum number of reports to determine if reporting for the group is complete. If the NEF determines that reporting for the group is complete, the NEF unsubscribes the monitoring event(s) to the UDM and the UDM unsubscribes the monitoring event(s) to all AMF(s) serving the UEs belonging to that group. NOTE 3: If an expiry time as specified in clause 6.2.6.2.6 of TS 29.518[ 5G System; Access and Mobility Management Services; Stage 3 ] [18] is not included in the event subscription, then the life time of the event subscription needs to be controlled by other means as there is no time based cancellation at all even if any group member UEs fail to register. When the Maximum duration of reporting expires in the NEF, the UDM and the AMF, then each of these nodes shall locally unsubscribe the monitoring event. 5. [Conditional - depending on the Event] The AMF detects the subscription change related event occurs, e.g. Subscription Correlation ID change due to AMF reallocation or addition of new Subscription Correlation ID due to a new group UE registered, it sends the event report by means of Namf_EventExposure_Notify message to the associated notification endpoint of the UDM. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.15.3.2.2 |
1,693 | 5.6.2.2.2 Paging for EPS services through E-UTRAN using IMSI | Paging for EPS services using IMSI is an abnormal procedure used for error recovery in the network. The network may initiate paging for EPS services using IMSI with CN domain indicator set to "PS" if the S-TMSI is not available due to a network failure (see example in figure 5.6.2.2.2.1). Figure 5.6.2.2.2.1: Paging procedure using IMSI In S1 mode, to initiate the procedure the EMM entity in the network requests the lower layer to start paging. If the TAI list is not available due to a network failure, the network may perform the paging within all tracking areas served by the MME (see 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [22] and 3GPP TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [23]). When a UE receives a paging for EPS services using IMSI from the network before a UE initiated EMM specific procedure has been completed, then the UE shall abort the EMM specific procedure and proceed according to the description in this clause. Upon reception of a paging for EPS services using IMSI, the UE shall stop timer T3346, if it is running, locally deactivate any EPS bearer context(s), if any, and locally detach from EPS. Additionally the UE shall delete the following parameters: last visited registered TAI, TAI list, GUTI and KSIASME. The UE shall set the EPS update status to EU2 NOT UPDATED and change the state to EMM-DEREGISTERED. The UE shall stop all timers T3396 that are running. If A/Gb mode or Iu mode is supported by the UE, the UE shall in addition handle the GMM parameters GMM state, GPRS update status, P-TMSI, P-TMSI signature, RAI, and GPRS ciphering key sequence number as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13] for the case when a paging for GPRS services using IMSI is received. After performing the local detach, the UE shall then perform an attach procedure as described in clause 5.5.1.2. If the UE is operating in CS/PS mode 1 or CS/PS mode 2 of operation, then the UE shall perform a combined attach procedure as described in clause 5.5.1.3. For this attach procedure and its reattempts, if any, the MS shall ignore the contents of the list of "forbidden tracking areas for roaming", as well as the list of "forbidden tracking areas for regional provision of service". NOTE 1: In some cases, user interaction can be required, thus the UE cannot activate the dedicated bearer context(s), if any, automatically. NOTE 2: The UE does not respond to the paging except with the ATTACH REQUEST message, hence timers T3413 and T3415 in the network are not used when paging with IMSI. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.6.2.2.2 |
1,694 | 16.9.10 Sidelink CA | Carrier aggregation (CA) in sidelink is supported for mode 2 and in V2X case only. It applies to both in coverage UEs and out of coverage UEs. Each resource pool (pre)configured for sidelink is associated to a single carrier. A UE using mode 2 resource allocation performs carrier (re)selection and may select one or more carriers used for sidelink. The carrier(s) that can be used for transmitting data are provided by the V2X layer per QoS flow, and LCP ensures that data from a SLRB is transmitted on a carrier for which all mapped QoS flows are allowed to use the carrier. For groupcast and broadcast, when the V2X layer provides multiple carriers in QoS flow to carrier mapping information to the AS, TX profile is used to indicate whether the transmission corresponding to the QoS flow is backward compatible or not. When backward compatibility is needed, the TX UE uses only the legacy carrier without PDCP duplication, or uses PDCP duplication with at least the legacy carrier. For groupcast and broadcast, carrier selection is performed at MAC layer, depending on the CBR of the configured carriers and logical channel priority. Carrier (re)selection may be performed when resource (re)selection is triggered, or when there is no SL grant for a sidelink process on any allowed carrier, and is triggered for each sidelink process. In order to avoid frequent switching across different carriers, the UE may keep using a carrier already selected for transmission, if the measured CBR on this carrier is lower than a (pre)configured threshold. For a UE using mode 2 resource allocation, logical channel prioritization is performed for a sidelink resource on a carrier depending on the CBR measured on the carrier and the logical channel priority, as specified in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [6]. For unicast, SL CA related capability is exchanged between the TX UE and RX UE, and the TX UE delivers the carrier configuration to the RX UE in PC5-RRC. For unicast, carrier selection and logical channel prioritization is performed similar to groupcast and broadcast among the carriers delivered in the carrier configuration. SL CA for unicast is not applied until the carrier configuration signalling is complete. Carrier (re)selection may be performed and a new carrier configuration is sent to the RX UE when the TX UE detects carrier failure on a specific carrier, as specified in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [6]. Sidelink packet duplication is supported for sidelink CA and is performed at PDCP layer. For sidelink packet duplication for transmission, a PDCP PDU is duplicated at the PDCP entity. The duplicated PDCP PDUs of the same PDCP entity are submitted to two different RLC entities and associated to two different sidelink logical channels respectively. The duplicated PDCP PDUs of the same PDCP entity are only allowed to be transmitted on different sidelink carriers. For a SL DRB, sidelink packet duplication is (pre)configured in the bearer configuration. For applicable SL SRBs, whether to use duplication is decided by the TX UE. In unicast, the TX UE sends the duplication configuration to the RX UE in PC5-RRC. There are specified logical channel identities which apply to the sidelink logical channel used for sidelink packet duplication exclusively as specified in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [6]. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.9.10 |
1,695 | 8.2.1.2 Intra-gNB-DU handover | This procedure is used for the case that the UE moves from one cell to another cell within the same gNB-DU or for the case that intra-cell handover is performed during NR operation, and supported by the UE Context Modification (gNB-CU initiated) procedure as specified in TS 38.473[ NG-RAN; F1 Application Protocol (F1AP) ] [4]. When the intra-gNB-DU handover is performed (either inter-cell or intra-cell), the gNB-CU provides new UL GTP TEID to the gNB-DU and the gNB-DU provides new DL GTP TEID to the gNB-CU. The gNB-DU shall continue sending UL PDCP PDUs to the gNB-CU using the previous UL GTP TEID until it re-establishes the RLC, and after then start sending using the new UL GTP TEID. The gNB-CU shall continue sending DL PDCP PDUs to the gNB-DU using the previous DL GTP TEID until it performs PDCP re-establishment or PDCP data recovery, and after then start sending using the new DL GTP TEID. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 8.2.1.2 |
1,696 | 4.26 Network Function/NF Service Context Transfer Procedures 4.26.1 General | Network Function/NF Service Context Transfer Procedures allow transfer of Service Context of a NF/NF Service from a Source NF/NF Service Instance to the Target NF/NF Service Instance, e.g. before the Source NF/NF Service can gracefully close its NF/NF Service. If SMF sets are deployed this applies from an SMF instance within an SMF set to an SMF instance of another SMF set. A request (push procedure, see clause 4.26.2) or response (pull procedure, see clause 4.26.3) from a Source NF/NF Service Instance to a Target NF/NF Service Instance contains either - the context being transferred, e.g. SM context (direct mode); or - optionally, an endpoint address from which Target NF/NF Service Instance can retrieve the context, see TS 29.501[ 5G System; Principles and Guidelines for Services Definition; Stage 3 ] [62] (indirect mode). It assumes that access to a given context endpoint address can be restricted to single Target NF/NF Service Instance. NOTE: Which procedures need to be executed for indirect mode is part of the specific context transfer procedures as specified in clause 4.26.5. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.26 |
1,697 | 6.8.1.2.3 Establishment of keys for cryptographically protected traffic in non-3GPP access | In the case of non-3GPP access, there are no individual radio bearers set up between the UE and N3IWF. For non-3GPP access, an IPsec tunnel is established between the UE and the interworking function N3IWF. The main SA is used solely for the transport of NAS messages between the UE and the AMF/SMF. Corresponding to the PDU session of the UE, based on the policies and configuration, N3IWF determines the number of IPsec child SAs to be established and the QoS profiles associated with each IPsec child SA. For example, the N3IWF may decide to establish one IPsec child SA and associate all QoS profiles with this IPsec child SA. In this case, all QoS Flows of the PDU Session would be transferred over one IPsec child SA. N3IWF may also decide to establish different child SAs corresponding to the different QoS flows. Corresponding to radio bearers in 3GPP access which are mapped to QoS values, for non-3GPPaccess there are only child SAs mapped to QoS values. Cryptographically each child SA is different with distinct key materials exchanged as per RFC 7296 [25]. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.8.1.2.3 |
1,698 | 6.11.1 Description | A variety of sensors such as accelerometer, gyroscope, magnetometer, barometer, proximity sensor, and GPS can be integrated in a UE. Also, different applications running on the UE can have different communication needs (e.g. different traffic time). In addition, a UE can support different access technologies such as NR, E-UTRA, WLAN access technology, and fixed broadband access technology. The information gathered by sensors, the utilized access technologies, the application context, and the application traffic characteristics can provide useful information to the applications installed in the UE and can also help the 5G system utilize resources in an efficient and optimized way. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.11.1 |
1,699 | – SL-MeasConfigInfo | The IE SL-MeasConfigInfo is used to set RSRP measurement configurations for unicast destinations. SL-MeasConfigInfo information element -- ASN1START -- TAG-SL-MEASCONFIGINFO-START SL-MeasConfigInfo-r16 ::= SEQUENCE { sl-DestinationIndex-r16 SL-DestinationIndex-r16, sl-MeasConfig-r16 SL-MeasConfig-r16, ... } SL-MeasConfig-r16 ::= SEQUENCE { sl-MeasObjectToRemoveList-r16 SL-MeasObjectToRemoveList-r16 OPTIONAL, -- Need N sl-MeasObjectToAddModList-r16 SL-MeasObjectList-r16 OPTIONAL, -- Need N sl-ReportConfigToRemoveList-r16 SL-ReportConfigToRemoveList-r16 OPTIONAL, -- Need N sl-ReportConfigToAddModList-r16 SL-ReportConfigList-r16 OPTIONAL, -- Need N sl-MeasIdToRemoveList-r16 SL-MeasIdToRemoveList-r16 OPTIONAL, -- Need N sl-MeasIdToAddModList-r16 SL-MeasIdList-r16 OPTIONAL, -- Need N sl-QuantityConfig-r16 SL-QuantityConfig-r16 OPTIONAL, -- Need M ... } SL-MeasObjectToRemoveList-r16 ::= SEQUENCE (SIZE (1..maxNrofSL-ObjectId-r16)) OF SL-MeasObjectId-r16 SL-ReportConfigToRemoveList-r16 ::= SEQUENCE (SIZE (1..maxNrofSL-ReportConfigId-r16)) OF SL-ReportConfigId-r16 SL-MeasIdToRemoveList-r16 ::= SEQUENCE (SIZE (1..maxNrofSL-MeasId-r16)) OF SL-MeasId-r16 -- TAG-SL-MEASCONFIGINFO-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
1,700 | 4.4.2.4 Establishment of an EPS security context during inter-system change from N1 mode to S1 mode in 5GMM-CONNECTED mode | In order for the UE operating in single-registration mode in a network supporting N26 interface to derive a mapped EPS security context for an inter-system change from N1 mode to S1 mode in 5GMM-CONNECTED mode, the AMF shall prepare a mapped EPS security context for the target MME as indicated in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]. The AMF shall derive a K'ASME using the KAMF key and the downlink NAS COUNT of the current 5G NAS security context, include the corresponding NAS sequence number in the N1 mode to S1 mode NAS transparent container IE (see subclause 9.11.2.7) and then increments its stored downlink NAS COUNT value by one. NOTE: The creation of the N1 mode to S1 mode NAS transparent container and the increment of the stored downlink NAS COUNT value by one are performed in prior to transferring the mapped EPS security context to the MME. The AMF shall select the NAS algorithms identifiers to be used in the target MME after the inter-system change from N1 mode to S1 mode in 5GMM-CONNECTED mode, for encryption and integrity protection. The uplink and downlink NAS COUNT associated with the newly derived K'ASME key are set to the uplink and downlink NAS COUNT value of the current 5G NAS security context, respectively. The eKSI for the newly derived K'ASME key shall be defined such as the value field is taken from the ngKSI and the type field is set to indicate a mapped security context. When the UE operating in single-registration mode in a network supporting N26 interface receives a command to perform inter-system change from N1 mode to S1 mode in 5GMM-CONNECTED mode, the UE shall derive the mapped EPS security context, i.e. derive K'ASME from KAMF using a downlink NAS COUNT based on the NAS sequence number received in the N1 mode to S1 mode NAS transparent container IE (see subclause 9.11.2.7) as described in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]. The UE shall set the uplink and downlink NAS COUNT values associated with the newly derived K'ASME key to the uplink and downlink NAS COUNT values of the current 5G NAS security context respectively. The eKSI for the newly derived K'ASME key is defined such that the value field is taken from the ngKSI and the type field is set to indicate a mapped security context. The UE shall also derive the NAS keys as specified in 3GPP TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [23A] using the EPS NAS security algorithms identifiers that are stored in the UE's 5G NAS security context. If the received N1 mode to S1 mode NAS transparent container IE does not have a valid NAS COUNT (see subclause 4.4.3.2) the UE shall discard the content of the received N1 mode to S1 mode NAS transparent container IE and inform the lower layers that the received N1 mode to S1 mode NAS transparent container is invalid. If the inter-system change from N1 mode to S1 mode in 5GMM-CONNECTED mode is not completed successfully, the AMF and the UE shall delete the new mapped EPS security context. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.4.2.4 |
Subsets and Splits