Search is not available for this dataset
doc_id
int64 1
6.72k
⌀ | Section
stringlengths 5
247
⌀ | Content
stringlengths 501
147k
⌀ | Source
stringclasses 456
values | Document Title
stringclasses 22
values | Working Group
stringclasses 21
values | Series Subject
stringclasses 9
values | Subclause
stringlengths 1
13
⌀ |
|---|---|---|---|---|---|---|---|
2,201 | 13.4B Temporary Public User Identity | For 3GPP systems, if there is no ISIM application to host the Public User Identity, a Temporary Public User Identity shall be derived, based on the IMSI. The Temporary Public User Identity shall be of the form as described in clause 13.4 and shall consist of the string "sip:" appended with a username and domain portion equal to the IMSI derived Private User Identity, as described in clause 13.2. An example using the same example IMSI from clause 13.2 can be found below: EXAMPLE: "sip:[email protected]". The temporary public user identity for a Stand-alone Non-Public Network (SNPN) subscriber with an IMSI-based SUPI type, shall use the IMSI-based derivation described above, and append nid<NID> of the SNPN, in between the "ims." and "mnc<MNC>" labels. NOTE: The UE takes the NID from "list of subscriber data" as specified in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [139], from the entry selected by the UE. EXAMPLE for an SNPN: "sip:[email protected]". The temporary Public User Identity for a Stand-alone Non-Public Network (SNPN) subscriber identified by a SUPI containing a network-specific identifier that takes the form of an NAI consists of the string "sip:" appended with a username and realm portion equal to the NAI SUPI derived Private User Identity. For 3GPP2 systems, if there is no IMC present, the UE shall derive the public user identity as described in Annex C of 3GPP2 X.S0013-004 [67]. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 13.4B |
2,202 | 7 Handling of unknown, unforeseen, and erroneous protocol data 7.1 General | The procedures specified in the present document apply to those messages which pass the checks described in this subclause. This subclause also specifies procedures for the handling of unknown, unforeseen, and erroneous protocol data by the receiving entity. These procedures are called "error handling procedures", but in addition to providing recovery mechanisms for error situations they define a compatibility mechanism for future extensions of the protocols. Subclauses 7.1 to 7.8 shall be applied in order of precedence. Detailed error handling procedures in the network are implementation dependent and may vary from PLMN to PLMN. However, when extensions of this protocol are developed, networks are assumed to have the error handling which is indicated in this subclause as mandatory ("shall") and that is indicated as strongly recommended ("should"). Also, the error handling of the network is only considered as mandatory or strongly recommended when certain thresholds for errors are not reached during a dedicated connection. For definition of semantical and syntactical errors see 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [11], subclause 11.4.2. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 7 |
2,203 | 10.2.2.1 Resource grid | The transmitted signal on one antenna port in each slot is described by a resource grid of size one resource block as defined in clause 6.2.3. Only is supported. Narrowband positioning reference signals are transmitted on antenna port . The channel over which a symbol on antenna port is conveyed can be inferred from the channel over which another symbol on the same antenna port is conveyed only within consecutive subframes where - if the higher layer parameter nprsBitmap is configured , equals the length of the nprsBitmap; - if the higher layer parameter nprsBitmap is not configured, where is configured by higher layers. | 3GPP TS 36.211 | Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation | RAN1 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 10.2.2.1 |
2,204 | 4.15.3.2.7 Information flow for Availability after DDN Failure with SMF buffering | The procedure is used if the SMF requests the UPF to forward packets that are subject of buffering in the SMF. The procedure describes a mechanism for the Application Function to subscribe to notifications about availability after downlink data notification failure. The Availability after Downlink Data Notification failure event is related to high latency communication, see also clauses 4.24.2 and 4.2.3.3. Cancelling the subscription is done by sending EventExposure_Unsubscribe requests identifying the subscription to cancel with the Subscription Correlation ID in the same order as indicated in figure 4.15.3.2.7-1 for the corresponding subscribe requests (the AMF unsubscribes the DDN Failure status notification by sending the Nsmf_PDUSession_UpdateSMContext Request message to each SMF in step 5). Step 0 and the notification steps 9 to 13 are not applicable in the cancellation case. Figure 4.15.3.2.7-1: Information flow for availability after DDN Failure with SMF buffering 0. The SMF (in the no-roaming case the H-SMF. in the roaming case the V-SMF, in the case of PDU session with I-SMF the I-SMF) configures the relevant UPF to forward packets to the SMF as described in clause 5.8.3 in 23.501 [2]. The SMF decides to apply this behaviour based on the "expected UE behaviour". Alternatively, step 0 is triggered by step 5. 1. The AF sends Nnef_EventExposure_Subscribe Request to the NEF requesting notifications for "Availability after DDN Failure" for a UE or group of UEs and providing a traffic descriptor identifying the source of the downlink IP or Ethernet traffic. If the reporting event subscription is authorized by the NEF, the NEF records the association of the event trigger and the requester identity. The AF may include Idle Status Indication request in the Nnef_EventExposure_Subscribe Request. If Idle Status Indication request is included, the NEF includes it in Nudm_EventExposure_Subscribe message. If the NEF does not support the requested Idle Status Indication, then depending on operator policies, the NEF rejects the request. 2. The NEF sends the Nudm_EventExposure_Subscribe Request to UDM. Identifier of the UE or group of UEs, the traffic descriptor, monitoring event received from AF at step 1 and notification endpoint of the NEF are included in the message. If the reporting event subscription is authorized by the UDM, the UDM records the association of the event trigger and the requester identity. Otherwise, the UDM continues in step 7 indicating failure. If the UDM receives Idle Status Indication request, it includes it in Namf_EventExposure_Subscribe message. 3. The UDM sends Namf_EventExposure_Subscribe messages to the AMF(s) which serve the UE(s) identified in step2 to subscribe to "Availability after DDN Failure". The UDM includes the DNN and S-NSSAI as well as the Traffic Descriptor if available A separate subscription is used for each UE. The NEF notification endpoint received in step 2 is included in the message. If the UDM becomes aware that such a UE is registered at a later time than when receiving step 2, the UDM then executes step 3. 4. The AMF acknowledges the execution of Namf_EventExposure_Subscribe. 5. If PDU Session exists for the DNN and S-NSSAI, the AMF subscribes to DDN Failure status notification by sending the Nsmf_PDUSession_UpdateSMContext Request message to each SMF, requesting the SMF to notify DDN Failure. The AMF also includes in Nsmf_PDUSession_UpdateSMContext the Traffic Descriptor and NEF correlation ID if received from the UDM. For new PDU Session establishment towards a DNN and S-NSSAI, the AMF subscribes to DDN Failure status notification in Nsmf_PDUSession_CreateSMContext Request message if the UDM has subscribed to Availability after DDN Failure event. In the case of home-routed PDU session or PDU session with I-SMF, the AMF sends Nsmf_PDUSession_UpdateSMContext Request message(s) to the related V-SMF(s) or I SMF(s). Steps 9-10 are performed by those V-SMF(s) or I-SMF(s). 6. The (I/V-)SMF sends the Nsmf_PDUSession_UpdateSMContext response message to the AMF. NOTE: Step 7 can happen any time after step 4. 7. The UDM sends the Nudm_EventExposure_Subscribe response to the NEF. 8. The NEF sends the Nsmf_EventExposure_Subscribe response to the AF. 9-10. The SMF is informed that the UE is unreachable via a Namf_Communication_N1N2MessageTransfer service operation. The SMF then decides to discard downlink packets received from the UPF. By comparing those discarded downlink packets received from the UPF with the Traffic Descriptor(s) received in the event subscription(s), the SMF determines whether DDN Failure due to any traffic from an AF is to be notified to the AMF and if so, the SMF sends the DDN Failure status, by means of Nsmf_PDUSession_SMContextStatusNotify message including NEF Correlation ID, to the AMF. If the UE is not reachable after the AMF received the DDN Failure notification from the SMF, the AMF shall set a Notify-on-available-after-DDN-failure flag corresponding to the NEF Correlation ID. 11-12. [Conditional] The AMF detects the UE is reachable and sends the event report(s) based on the Notify-on-available-after-DDN-failure flag, by means of Namf_EventExposure_Notify message(s), only to the NEF(s) indicated as notification endpoint(s) identified via the corresponding subscription in step 3. In this way, only the AF(s) for which DL traffic transmission failed are notified. If the AMF received Idle Status Indication request in step 3 and the AMF supports Idle Status Indication, the AMF includes also the Idle Status Indication. 13. The NEF sends Nnef_EventExposure_Notify message with the "Availability after DDN Failure" event to AF. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.15.3.2.7 |
2,205 | 5.38.5 Paging Restriction | A Multi-USIM UE and the network may support Paging Restriction. A Multi-USIM UE, if the AMF indicates that the network supports Paging Restriction feature, may indicate Paging Restriction Information in the Service Request or Registration Request message (including the case where the Registration Request is sent due to mobility outside the Registration Area, i.e. before detecting whether the network supports the feature in the new Tracking Area, provided that the network has already indicated support for Paging Restriction feature in the current stored Registration Area) as specified in clauses 5.38.2 and 5.38.4. Based on operator policy the AMF may accept or reject the Paging Restriction Information requested by the UE. If the AMF accepts the Paging Restriction Information from the UE, the AMF stores the Paging Restriction Information from the UE in the UE context. If the AMF rejects the Paging Restriction Information, the AMF removes any stored Paging Restriction Information from the UE context and discards the UEs requested Paging Restriction Information. The AMF informs the UE about the acceptance/rejection of the requested Paging Restriction Information in the Registration Accept or Service Accept message. If the UE does not provide any Paging Restriction Information in the Service Request over 3GPP access or the Registration Request over 3GPP access, the AMF removes any stored Paging Restriction Information from the UE context. The Paging Restriction Information may indicate any of the following: a) all paging is restricted; or b) all paging is restricted, except paging for voice service (IMS voice); or c) all paging is restricted, except for certain PDU Session(s); or d) all paging is restricted, except paging for voice service (IMS voice) and certain PDU session(s). NOTE 1: The UE expects not to be paged for any purpose in case a). The UE expects to be paged only for voice service in case b). The UE expects to be paged only for certain PDU Session(s) in case c). The UE expects to be paged for voice service and certain PDU session(s) in case d). The AMF can page the UE for mobile terminated signalling based on local policy considering the stored Paging Restriction Information, except for case a). In this case, to comply with the UE provided Paging Restriction Information, the AMF can trigger AN release procedure as soon as possible after the mobile terminated signalling procedure is executed. NOTE 2: In the case of roaming, the Paging Restrictions for voice service implied by bullet b) and d) depends on the existence of an agreement with the HPLMN to support voice service via IMS. Hence the support of Paging Restrictions in bullets b) and d) takes the IMS voice service agreement into consideration. NOTE 3: When there is no PLMN-wide support for the Paging Restriction feature, it can occur that upon Mobility Registration Update with Paging Restriction Information the UE detects the network does not support the feature. If so, the UE assumes that no Paging Restriction Information is applied. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.38.5 |
2,206 | 5.2.3.6.2 Nudm_ParameterProvision_Update service operation | Service operation name: Nudm_ParameterProvision_Update. Description: The consumer updates the UE related information (e.g. Expected UE Behaviour, Network Configuration parameters, Location Privacy Indication parameters, Enhanced Coverage Restriction Information, ECS Address Configuration Information), 5G VN group related information (5G VN group data, 5G VN membership management), Multicast MBS group related information, or Application-Specific UE Behaviour. Inputs, Required: AF Identifier, Transaction Reference ID(s). Inputs, Optional: GPSI or SUPI, External Group ID, DNN, S-NSSAI, at least one of the Expected UE Behaviour parameters (optionally with associated confidence and/or accuracy levels) or at least one of the Application-Specific Expected UE Behaviour parameters (optionally with associated confidence and/or accuracy levels) or at least one of the Network Configuration parameters or 5G VN group related information, MTC Provider Information, Validity Time or Location Privacy Indication parameters or Enhanced Coverage Restriction Information or ECS Address Configuration Information, Multicast MBS related information, or Application-Specific UE Behaviour. Outputs, Required: Transaction Reference ID(s), Operation execution result indication, or DNN and S-NSSAI specific Group Parameters. Outputs, Optional: Transaction specific parameters, if available. For Multicast MBS related information, refer to TS 23.247[ Architectural enhancements for 5G multicast-broadcast services ] [78]. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.3.6.2 |
2,207 | 8.5.1.2.4 Minimum Requirement 2 Tx Antenna Port (demodulation subframe overlaps with aggressor cell ABS and CRS assistance information are configured) | For the parameters specified in Table 8.5.1-1 and Table 8.5.1.2.4-1, the average probability of a miss-detecting ACK for NACK (Pm-an) shall be below the specified value in Table 8.5.1.2.4-2. In Table 8.5.1.2.4-1, Cell 1 is the serving cell, and Cell 2 and Cell 3 are the aggressor cells. The downlink physical channel setup for Cell 1 is according to Annex C.3.2 and for Cell 2 and Cell 3 is according to Annex C.3.3, respectively. The CRS assistance information [7] including Cell 2 and Cell 3 is provided. Table 8.5.1.2.4-1: Test Parameters for PHICH Table 8.5.1.2.4-2: Minimum performance PHICH | 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.5.1.2.4 |
2,208 | 4.15.3.2.1 AMF service operations information flow | The procedure is used by the NF to subscribe to notifications and to explicitly cancel a previous subscription. Cancelling is done by sending Namf_EventExposure_UnSubscribe request identifying Subscription Correlation ID. The notification steps 3 and 4 are not applicable in cancellation case. Figure 4.15.3.2.1-1: Namf_EventExposure_Subscribe, Unsubscribe and Notify operations 1. A NEF sends a request to subscribe to a (set of) Event ID(s) in AMF in Namf_EventExposure_Subscribe request. The NEF could be the same NF subscribing to receive the event notification reports (i.e. Event Receiving NF) or it could be a different NF. The NEF subscribes to one or several Event(s) (identified by Event ID) and provides the associated notification endpoint of the Event Receiving NF. If the NEF itself is not the Event Receiving NF, the NEF shall additionally provide the notification endpoint of itself besides the notification endpoint of Event Receiving NF. Each notification endpoint is associated with the related (set of) Event ID(s). This is to assure the NEF can receive the notification of subscription change related event (e.g. Subscripiont Correlation ID Change). Event Reporting information defines the type of reporting requested. If the reporting event subscription is authorized by the AMF, the AMF records the association of the event trigger and the requester identity. 2. AMF acknowledges the execution of Namf_EventExposure_Subscribe. 3. [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 notification endpoint of the Event Receiving NF. 4. [Conditional- depending on the Event] The AMF detects the subscription change related event occurs, e.g. Subscription Correlation ID change due to AMF reallocation, it sends the event report by means of Namf_EventExposure_Notify message to the NEF. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.15.3.2.1 |
2,209 | 5.2.3.6.4 Nudm_ParameterProvision_Delete service operation | Service operation name: Nudm_ParameterProvision_Delete Description: The consumer deletes one or more previously created Network Configuration parameters, or a 5G VN group, or ECS Address Configuration Information, or Multicast MBS related information. Inputs, Required: AF Identifier, Transaction Reference ID(s). Inputs, Optional: GPSI, External Group ID, for 5G VN group deletion or for Multicast MBS deletion or Network Configuration of Parameters. Outputs, Required: Transaction Reference ID(s), Operation execution result indication. Outputs, Optional: None. For Multicast MBS related information, refer to TS 23.247[ Architectural enhancements for 5G multicast-broadcast services ] [78]. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.3.6.4 |
2,210 | 4.7.1.6.3 Change of network mode of operation at Iu mode to A/Gb mode inter-system change | Whenever an MS moves to a new RA supporting the A/Gb mode radio interface, the procedures executed by the MS depend on the network mode of operation in the old and new routing area. In case the MS is in state GMM-REGISTERED or GMM-ROUTING-AREA-UPDATING-INITIATED and is in operation mode: a) A in Iu mode, an MS that changes to GPRS operation mode A or B in A/Gb mode shall execute: Table 4.7.1.6.5/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Mode A in Iu mode changing to GPRS mode A or B in A/Gb mode b) C in Iu mode, the MS shall change to GPRS operation mode C in A/Gb mode and shall execute the normal Routing Area Update procedure. c) CS in Iu mode, the MS shall execute the normal Location Update procedure. (*) Intended to remove the Gs association in the MSC/VLR. (**) Intended to establish the Gs association in the MSC/VLR. (***) If the MS that needs only GPRS services and "SMS-only service" moves to a new routing area, see subclause 4.1.1.2.2. Further details are implementation issues. | 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.6.3 |
2,211 | 5.4.7.3.1 Network slice-specific EAP result message transport procedure initiation | In order to initiate the network slice-specific EAP result message transport procedure, the AMF shall create a NETWORK SLICE-SPECIFIC AUTHENTICATION RESULT message. The AMF shall set the EAP message IE of the NETWORK SLICE-SPECIFIC AUTHENTICATION RESULT message to the EAP-success or EAP-failure message provided by the AAA-S via the NSSAAF. The AMF shall set the S-NSSAI IE of the NETWORK SLICE-SPECIFIC AUTHENTICATION RESULT message to the HPLMN S-NSSAI or the SNPN S-NSSAI to which the EAP-success or EAP-failure message is related. The AMF shall send the NETWORK SLICE-SPECIFIC AUTHENTICATION RESULT message. The AMF shall retain the authentication result for the UE and the HPLMN S-NSSAI or the SNPN S-NSSAI while the UE is registered to the PLMN (see subclause 5.15.10 in 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8]). Upon receipt of a NETWORK SLICE-SPECIFIC AUTHENTICATION RESULT message, the UE shall pass: a) the EAP-success or EAP-failure message received in the EAP message IE; and b) the HPLMN S-NSSAI or the SNPN S-NSSAI in the S-NSSAI IE; to the upper layers. Apart from this action, the network slice-specific authentication and authorization procedure is transparent to the 5GMM layer of the UE. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.4.7.3.1 |
2,212 | 6.15.2.2 UE Parameters Update Counter | The AUSF and the UE shall associate a 16-bit counter, CounterUPU, with the key KAUSF. The UE shall initialize the CounterUPU to 0x00 0x00 when the newly derived KAUSF is stored (see clause 6.2.2.2). The UE shall store the UPU counter . If the USIM supports both 5G parameters storage and 5G parameters extended storage, then CounterUPU shall be stored in the USIM. Otherwise, CounterUPU shall be stored in the non-volatile memory of the ME. To generate the UPU-MAC-IAUSF, the AUSF shall use the CounterUPU. The CounterUPU shall be incremented by the AUSF for every new computation of the UPU-MAC-IAUSF. The CounterUPU is used as freshness input into UPU-MAC-IAUSF and UPU-MAC-IUE derivations as described in the Annex A.19 and Annex A.20 respectively, to mitigate the replay attack. The AUSF shall send the value of the CounterUPU (used to generate the UPU-MAC-IAUSF) along with the UPU-MAC-IAUSF to the UE. The UE shall only accept CounterUPU value that is greater than stored CounterUPU value. The UE shall update the stored CounterUPU with the received CounterUPU, only if the verification of the received UPU-MAC-IAUSF is successful. The UE shall use the CounterUPU received from the UDM, when deriving the UPU-MAC-IUE for the UE Parameters Upadate Data acknowledgement. The AUSF and the UE shall maintain the CounterUPU for lifetime of the KAUSF. The AUSF that supports the UE parameters update using control plane procedure shall initialize the CounterUPU to 0x00 0x01 when the newly derived KAUSF is stored (see clause 6.2.2.1). The AUSF shall set the CounterUPU to 0x00 0x02 after the first calculated UPU-MAC-IAUSF, and monotonically increment it for each additional calculated UPU-MAC-IAUSF. The UPU Counter value of 0x00 0x00 shall not be used to calculate the UPU-MAC-IAUSF and UPU-MAC-IUE. The AUSF shall suspend the UE Parameters Update protection service for the UE, if the CounterUPU associated with the KAUSF of the UE, is about to wrap around. When a fresh KAUSF is generated for the UE, the CounterUPU at the AUSF is reset to 0x00 0x01 as defined above and the AUSF shall resume theUE Parameters Update protection service for the UE. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.15.2.2 |
2,213 | 10.3.2 Composition of the FPBI 10.3.2.1 FPBI general structure | bit No 19 1 +-------------------------------------+ | | | +-------------------+ Type| Significant Part | FPBI 19 bits <-------------------------------------> Figure 14: General structure of FPBI The FPBI is composed of the following elements: - FPBI Type. Its length is 2 bits; - FPBI Significant Part. Its length is 17 bits. NOTE: The three LSBs bits of the FPBI form the 3-bit training sequence code (TSC). See 3GPP TS 45.056[ None ] [35]. The following FPBI Type values have been allocated for use by CTS: 00 FPBI class A: residential and single-cell systems; 01 FPBI class B: multi-cell PABXs. All other values are reserved and CTS-MSs shall treat these values as FPBI class A. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 10.3.2 |
2,214 | 9.2.3.3 Re-establishment procedure | A UE in RRC_CONNECTED may initiate the re-establishment procedure to continue the RRC connection when a failure condition occurs (e.g. radio link failure, reconfiguration failure, integrity check failure…). The following figure describes the re-establishment procedure started by the UE: Figure 9.2.3.3-1: Re-establishment procedure 1. The UE re-establishes the connection, providing the UE Identity (PCI+C-RNTI) to the gNB where the trigger for the re-establishment occurred. 2. If the UE Context is not locally available, the gNB, requests the last serving gNB to provide UE Context data. 3. The last serving gNB provides UE context data. 4/4a. The gNB continues the re-establishment of the RRC connection. The message is sent on SRB1. 5/5a. The gNB may perform the reconfiguration to re-establish SRB2 and DRBs when the re-establishment procedure is ongoing. 6/7. If loss of user data buffered in the last serving gNB shall be prevented, the gNB provides forwarding addresses, and the last serving gNB provides the SN status to the gNB. 8/9. The gNB performs path switch. 10. The gNB triggers the release of the UE resources at the last serving gNB. The IAB-MT in SA mode follows the same re-establishment procedure as described for the UE. After the backhaul has been established, the re-establishment procedure of the IAB-MT is part of the intra-CU backhaul RLF recovery procedure for IAB-nodes defined in TS 38.401[ NG-RAN; Architecture description ] [4]. Modifications to the configuration of BAP sublayer and higher protocol layers above the BAP sublayer are described in TS 38.401[ NG-RAN; Architecture description ] [4]. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 9.2.3.3 |
2,215 | 4.13.3.7 MT SMS over NAS in CM-CONNECTED state via 3GPP access | MT SMS in CM-CONNECTED procedure is specified by reusing the MT SMS in CM-IDLE state with the following modification: - There is no need for the AMF to perform Paging of the UE and can immediate continue with a message to SMSF via N20 to allow the SMSF to start forward the MT SMS. - If the delivery of the NAS PDU containing the SMS fails e.g. if the UE is in RRC_INACTIVE and NG-RAN paging was not successful, the NG-RAN initiate the UE context release in the AN procedure and provide notification of non-delivery to the AMF. The AMF provides an indication of non-delivery to the SMSF. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.13.3.7 |
2,216 | 6.9.5.2 Rules related to parallel NAS connections | Concurrent runs of security procedures in parallel over two different NAS connections when terminated in the same AMF can lead to race conditions and mismatches between the security contexts in the network and the UE. In order to avoid such mismatches, the following rules shall be followed: 1. The SEAF/AMF shall not initiate a primary authentication or NAS SMC procedure in case a primary authentication or a NAS SMC procedure is ongoing on a parallel NAS connection. Authentication procedures followed by a NAS SMC procedures taking the new 5G security context into use, shall be performed on one NAS signalling connection at a time. 2. When the AMF has sent a NAS Security Mode Command to a UE in order to take a new KAMF into use and receives a context transfer request message for the UE from another AMF, the AMF shall wait for the completion of the NAS SMC procedure (e.g. receiving NAS Security Mode Complete) before transferring the context. 3. The UE shall not initiate a NAS registration over a second NAS connection to an AMF of the same network before primary authentication on the first NAS connection is complete. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.9.5.2 |
2,217 | 9.2 Security mechanisms for the N2 interface | N2 is the reference point between the AMF and the 5G-AN. It is used, among other things, to carry NAS signalling traffic between the UE and the AMF over 3GPP and non-3GPP accesses. The transport of control plane data over N2 shall be integrity, confidentiality and replay-protected. In order to protect the N2 reference point, it is required to implement IPsec ESP and IKEv2 certificates-based authentication as specified in sub-clause 9.1.2 of the present document. IPsec is mandatory to implement on the gNB and the ng-eNB. On the core network side, a SEG may be used to terminate the IPsec tunnel. In addition to IPsec, DTLS shall be supported as specified in RFC 6083 [58] to provide mutual authentication, integrity protection, replay protection and confidentiality protection. Security profiles for DTLS implementation and usage shall follow the TLS profile given in clause 6.2 of TS 33.210[ Network Domain Security (NDS); IP network layer security ] [3] and the certificate profile given in clause 6.1.3a of TS 33.310[ Network Domain Security (NDS); Authentication Framework (AF) ] [5]. The identities in the end entity certificates shall be used for authentication and policy checks. Mutual authentication shall be supported over the N2 interface between the AMF and the 5G-AN using DTLS and/or IKEv2. NOTE 1: The use of transport layer security, via DTLS, does not rule out the use of network layer protection according to NDS/IP as specified in TS 33.210[ Network Domain Security (NDS); IP network layer security ] [3]. In fact, IPsec has the advantage of providing topology hiding. NOTE 2: The use of cryptographic solutions to protect N2 is an operator's decision. In case the NG-RAN node (gNB or ng-eNB) has been placed in a physically secured environment then the 'secure environment' includes other nodes and links beside the NG-RAN node. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 9.2 |
2,218 | 10.5.4.23 Signal | The purpose of the signal information element is to allow the network to convey information to a user regarding tones and alerting signals (see subclauses 5.2.2.3.2 and 7.3.3.). The signal information element is coded as shown in figure 10.5.112/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.130/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The signal is a type 3 information element with 2 octets length. Figure 10.5.112/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Signal information element Table 10.5.130/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Signal 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.4.23 |
2,219 | C.2.1 Protection against wrap around of counter in the USIM | The USIM will not accept arbitrary jumps in sequence numbers, but only increases by a value of at most . Therefore (before applying the freshness conditions of Annex C.2.2) the received sequence number SQN shall only be accepted by the USIM if SEQ-SEQMS ≤ . If SQN can not be accepted then the USIM shall generate a synchronisation failure message using SQNMS. Conditions on the choice of : (1) shall be sufficiently large so that the MS will not receive any sequence number with SEQ - SEQMS > if the HE/AuC functions correctly. (2) In order to prevent that SEQMS ever reaches the maximum batch number value SEQmax during the lifetime of the USIM the minimum number of steps SEQmax / required to reach SEQmax shall be sufficiently large. | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | C.2.1 |
2,220 | 8.2.3.2 Intra-CU topology adaptation procedure in NSA using MCG SRB | This procedure is used when the migrating IAB-MT moves from source parent node to target parent node within the same IAB-donor-CU while only MCG SRB is available for IAB-node during EN-DC operation. The target parent node may use a different IAB-donor-DU than the one used by the source parent node. The source path may have common nodes with the target path. Figure 8.2.3.2-1 shows the topology adaptation procedure using MCG SRB of IAB-MT in EN-DC, where the target parent node uses a different IAB-donor-DU than the source parent node. Figure 8.2.3.2-1: IAB intra-CU topology adaptation procedure using MCG SRB in EN-DC 1. The migrating IAB-MT sends an ULInformationTransferMRDC message to the MeNB 2. The MeNB sends RRC TRANSFER message to the IAB-donor-CU. 3. The IAB-donor-CU may send UE CONTEXT MODIFICATION REQUEST message to the source parent node IAB-DU, to query the latest SCG configuration. 4. The source parent node IAB-DU responds with a UE CONTEXT MODIFICATION RESPONSE message that includes full configuration information. 5. The IAB-donor-CU sends a UE CONTEXT SETUP REQUEST message to the target parent node IAB-DU, to create a UE context for migrating IAB-MT and set up one or more bearers. These bearers can be used by the migrating IAB-MT for its own signalling, and, optionally, data traffic. The UE CONTEXT SETUP REQUEST message includes CG-ConfigInfo. 6. The target parent node IAB-DU responds to the IAB-donor-CU with a UE CONTEXT SETUP RESPONSE message. 7. The IAB-donor-CU sends a UE CONTEXT MODIFICATION REQUEST message to the source parent node IAB-DU, this message includes the Transmission Action Indicator IE, which instructs the source parent node IAB-DU to stop the data transmission to the migrating IAB-node. The source parent node IAB-DU also sends a Downlink Data Delivery Status frame to inform the IAB-donor-CU about the unsuccessfully transmitted downlink data to the migrating IAB-node. 8. The source parent node IAB-DU responds to the IAB-donor-CU with a UE CONTEXT MODIFICATION RESPONSE message. 9. The IAB-donor-CU sends an SGNB MODIFICATION REQUIRED message to the MeNB. 10/11. The MeNB initiated SgNB Modification procedure may be triggered by the SgNB initiated SgNB Modification procedure (e.g. to provide information such as data forwarding addresses, new SN security key, measurement gap, etc.). 12. The MeNB and the migrating IAB-MT perform RRC Connection Reconfiguration procedure. The RRCConnectionReconfiguration message includes information as described for the intra-CU topology adaptation procedure in SA in clause 8.2.3.1. 13. The MeNB sends an SGNB MODIFICATION CONFIRM message to the IAB-donor-CU. 14. The migrating IAB-MT performs Random Access procedure at the target parent node IAB-DU. 15-19. The remaining steps of the procedure follow the steps 11-15 of the intra-CU topology adaptation procedure in SA scenario, as defined in clause 8.2.3.1. The main difference is that the RRC message for the migrating IAB-node, if involved, will be transmitted using the MCG SRB. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 8.2.3.2 |
2,221 | 5.2.4 Narrowbands and widebands | A narrowband is defined as six non-overlapping consecutive physical resource blocks in the frequency domain. The total number of uplink narrowbands in the uplink transmission bandwidth configured in the cell is given by The narrowbands are numbered in order of increasing physical resource-block number where narrowband is composed of physical resource-block indices where If , a wideband is defined as four non-overlapping narrowbands in the frequency domain. The total number of uplink widebands in the uplink transmission bandwidth configured in the cell is given by and the widebands are numbered in order of increasing narrowband number where wideband is composed of narrowband indices where . If , then and the single wideband is composed of the non-overlapping narrowband(s). | 3GPP TS 36.211 | Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation | RAN1 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 5.2.4 |
2,222 | 6.2.9.3 ProSeP | The ProSeP requires interaction between upper layers and the 5GSM entities in the UE acting as a 5G ProSe layer-3 UE-to-network relay UE (see 3GPP TS 24.554[ Proximity-services (ProSe) in 5G System (5GS) protocol aspects; Stage 3 ] [19E] for further details). The upper layers may request the 5GSM entity: a) to establish a PDU session indicating one or more PDU session attributes; or b) to release the existing PDU session; or c) to establish a PDU session indicating one or more PDU session attributes, and to release the existing PDU session. Each of the 5GSM entities in the UE acting as a 5G ProSe layer-3 UE-to-network relay UE shall indicate attributes (e.g. PDU session identity, SSC mode, S-NSSAI, DNN, PDU session type, access type, PDU address) of the newly established PDU session to the upper layers. If the PDU session is released, the 5GSM entity handling the PDU session shall inform the PDU session identity of the released PDU session to the upper layers. | 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.9.3 |
2,223 | 8.57 APN Restriction | The APN Restriction information element contains an unsigned integer value indicating the level of restriction imposed on EPS Bearer Contexts created to the associated APN. The APN Restriction IE is coded as depicted in Figure 8.57-1: Figure 8.57-1: APN Restriction Type Information Element An APN Restriction value may be configured for each APN in the PGW. It is used to determine, on a per UE basis, whether it is allowed to establish EPS bearers to other APNs. Table 8.57-1: Valid Combinations of APN Restriction | 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.57 |
2,224 | 4.17.7 NF/NF service status subscribe/notify in the same PLMN | Figure 4.17.7-1: NF/NF service status subscribe/notify in the same PLMN 1. The NF service consumer subscribes to be notified of newly registered/updated/deregistered NF instances along with its NF services. The NF service consumer invokes Nnrf_NFManagement_NFStatusSubscribe Request from an appropriate configured NRF in the same PLMN. 2. The NRF authorizes the Nnrf_NFManagement_NFStatusSubscribe Request. Based on the profile of the expected NF/NF service and the type of the NF service consumer, the NRF determines whether the NF service consumer is allowed to subscribe to the status of the target NF instance(s) or NF service instance(s). 3. If allowed, the NRF acknowledges the execution of Nnrf_NFManagement_NFStatusSubscribe Request. 4. NRF notifies about newly registered/updated/deregistered NF instances along with its NF services to the subscribed NF service consumer. NOTE 1: The NF service consumer unsubscribes to receive NF status notifications by invoking Nnrf_NFManagement_NFStatusUnSubscribe service operation. NOTE 2: When the NF or NF service intance becomes unavailable, the NRF invokes Nnrf_NFManagement_NFStatusNotify service to notify the NF service consumer based on the subscription. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.17.7 |
2,225 | 7.7.9 Unknown or unexpected Information Element | The receiver of a GTP message including an unexpected information element with known Type value, but with the instance value that is not defined for this message shall discard the IE and log an error. The receiver shall process the message. An information element with a Type value which is defined in clause 8.1 of the present specification but whose Instance Value is not expected in the received GTP signalling message according to the grammar defined in clause 7 of the present specification shall be silently discarded (skipped) and the rest of the message processed as if this information element was not present. NOTE: An Information Element in an encoded GTPv2 message or grouped IE is identified by the pair of IE Type and Instance value. | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 7.7.9 |
2,226 | 6.28.2.2 Smart Grid | For the 5G system to support the Smart Grid, the 5G systems needs to fulfil at minimum the following requirements. - 3GPP TS 22.104[ Service requirements for cyber-physical control applications in vertical domains ] clauses 5.2, 5.3, and 5.6 for requirements related to periodic communication, aperiodic communication, and clock synchronization; - 3GPP TS22.104[ Service requirements for cyber-physical control applications in vertical domains ] , clause 5.6.1, 5.6C, 9 and A.4 for Smart Grid specific service requirements; - 3GPP TS 22.261[ Service requirements for the 5G system ] , clauses 6.10, 6.13, 6.14, and 6.26 for requirements related to the support of secured communication between the 5G system and a trusted third-party; - 3GPP TS 22.261[ Service requirements for the 5G system ] , clauses 6.23 for the requirements related to information exchange between the 5G system and a trusted third-party; - 3GPP TS 22.261[ Service requirements for the 5G system ] , clause 8.9 for the requirements on security. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.28.2.2 |
2,227 | 6.3.9 Handling of APN rate control | APN rate control controls the maximum number of uplink user data messages including uplink exception data reporting sent by the UE in a time interval for the APN in accordance with 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [10]. The UE shall limit the rate at which it generates uplink user data messages to comply with the APN rate control policy. The NAS shall provide the indicated rates to upper layers for enforcement. The indicated rates in a NAS procedure applies to the APN the NAS procedure corresponds to, and the indicated rates are valid until a new value is indicated or the last PDN connection using this APN is released. If the UE supports APN rate control, the UE shall provide the support indication of APN rate control and additional APN rate control for exception data reporting to the network. If the UE indicates support of additional APN rate control for exception data reporting, the network may provide the APN rate control parameters for exception data to the UE. If the UE does not indicate support of additional APN rate control for exception data reporting, the network shall not provide the APN rate control parameters for exception data to the UE. If an allowed indication of additional exception reports is provided with the APN rate control parameters and: - the additional APN rate control parameters for exception data is provided and the limit for additional rate for exception data reporting is not reached; or - the additional APN rate control parameters for exception data is not provided, the UE is allowed to send uplink exception reports even if the limit for the APN rate control has been reached. NOTE 1: The HPLMN can discard or delay user data that exceeds the limit provided for APN rate control. Upon inter-system change from S1 mode to N1 mode, the UE shall store the current APN rate control status for each APN associated with PDN connection(s) to be transferred from S1 mode to N1 mode as specified in 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [58]. NOTE 2: How long the UE stores the current APN rate control status is implementation specific. Upon inter-system change from N1 mode to S1 mode, the UE shall use the stored APN rate control status, if any, to comply with the APN rate control policy for an APN as specified in 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [58] if: a) there is at least one PDN connection associated with this APN was transferred from N1 mode to S1 mode; and b) the validity period of the stored APN rate control status has not expired. After inter-system change from S1 mode to N1 mode, if all the PDU sessions associated with the same APN that was used in S1 mode are released, the UE shall delete the stored APN rate control status for this APN. | 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.3.9 |
2,228 | 9.9.4.15 Traffic flow aggregate description | The purpose of the Traffic flow aggregate description information element is to specify the aggregate of one of more packet filters and their related parameters and operations. The traffic flow aggregate description may contain the aggregate of packet filters for the downlink direction, the uplink direction or packet filters that apply for both directions. The packet filters determine the traffic mapping to EPS bearer contexts. The downlink packet filters shall be applied by the network, and the uplink packet filters shall be applied by the UE. A packet filter that applies for both directions shall be applied by the network as a downlink packet filter and by the UE as an uplink packet filter. When the traffic flow aggregate description is used in the UE requested bearer resource allocation procedure or the UE requested bearer resource modification procedure, it is associated to a particular procedure identified by a procedure transaction identity (PTI). Therefore, the UE shall release the traffic flow aggregate description when the UE requested bearer resource allocation procedure or the UE requested bearer resource modification procedure is completed. The UE shall not include the packet filters of a particular traffic flow aggregate description in any other traffic flow aggregate description when multiple UE requested bearer resource allocation procedures and/or UE requested bearer resource modification procedures are ongoing in parallel. The Traffic flow aggregate description information element is encoded using the same format as the Traffic flow template (TFT) information element (see clause 10.5.6.12 in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13]). When sending this IE in the BEARER RESOURCE ALLOCATION REQUEST message or the BEARER RESOURCE MODIFICATION REQUEST message, the UE shall set the packet filter identifier values to 0 when the UE requests to "Create a new TFT" or "Add packet filters to existing TFT" ; otherwise, the UE shall set the packet filter identifier values from those of already assigned packet filter identifiers of the existing EPS bearer, so that they are unique across all packet filters for the EPS bearer context indicated by the EPS bearer identity IE. | 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.4.15 |
2,229 | 4.3.6.3 Notification of User Plane Management Events | The SMF may send a notification to the AF if the AF had subscribed to user plane management event notifications as described in clause 4.3.6.2 and in clause 5.6.7 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The following are the examples of such events: - A PDU Session Anchor identified in the AF subscription request has been established or released. - A DNAI has changed. - The SMF has received a request for AF notification and the on-going PDU Session meets the conditions to notify the AF. - Ethernet PDU Session Anchor Relocation as defined in clause 4.3.5.8. - Candidate DNAI(s) has changed. - A common EAS has changed. The SMF uses notification reporting information received from PCF to issue the notification either via an NEF (2a, 2b and 4a, 4b) or directly to the AF (2c and 4c). In the case of the AF interacting with VPLMN in the HR-SBO case, the NF(s) in the procedure are located in VPLMN. NOTE 1: 1a: In HR-SBO case, no PCF in VPLMN is involved. The following flow depicts the sequence of events: Figure 4.3.6.3-1: Notification of user plane management event 1. A condition for an AF notification has been met as described above. The SMF sends notification to the NF that is subscribed for SMF notifications. Further processing of the SMF notification depends on the receiving NF, as shown in steps 2a and 2c. If immediate reporting flag is included in AF subscription for user plane management event as described in clause 5.6.7 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], SMF sends notification, as shown in steps 2a or 2c. 2a. If early notification via NEF is requested by the AF, the SMF notifies the NEF of the target DNAI or candidate DNAI(s) of the PDU Session or indication of EAS rediscovery and may indicate capability of supporting EAS IP replacement in 5GC by invoking Nsmf_EventExposure_Notify service operation. The SMF may provide the target AF ID if it determines that the target DNAI is not supported by the source AF as specified in TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [74]. The SMF may consider the UE location and available DNAI list provided by AF to select the closest available DNAI(s) as candidate DNAI(s). The SMF may also provide the candidate DNAI(s) in a prioritized order. NOTE 2: For the reporting of candidate DNAIs from SMF/NEF to AF, only early notification is used. 2b. When the NEF receives Nsmf_EventExposure_Notify, the NEF performs information mapping (e.g. AF Transaction Internal ID provided in Notification Correlation ID to AF Transaction ID, SUPI to GPSI, etc.) as applicable according to clause 5.6.7 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] and triggers the appropriate Nnef_TrafficInfluence_Notify message. In this case, step 2c is not applicable. 2c. If early direct notification is requested by the AF, the SMF notifies the AF of the target DNAI or candidate DNAI(s) of the PDU Session or indication of EAS rediscovery and may indicate capability of supporting EAS IP replacement in 5GC by invoking Nsmf_EventExposure_Notify service operation. The SMF may provide the target AF ID if it determines that the target DNAI is not supported by the source AF. 2d. The AF replies to Nnef_TrafficInfluence_Notify by invoking Nnef_TrafficInfluence_AppRelocationInfo service operation either immediately or after any required application relocation in the target DNAI is completed. The AF may include N6 traffic routing details corresponding to the target DNAI and /or the 'uplink buffering' indication to indicate that buffering of uplink traffic to the target DNAI is needed. The AF may include Information for EAS IP Replacement in 5GC. AF may reply in negative e.g. if the AF determines that the application relocation cannot be completed successfully and/or on time. NOTE 3: The maximum time the new PSA is to buffer UL data relates to the maximum delay between steps 4a-4c and step 4f/4g of Figure 4.3.6.3-1. SMF local policies can control this maximum time. NOTE 4: The traffic being buffered is the traffic associated with the PCC rule that has requested the notification. 2d-a. If information sent via Nnef_TrafficInfluence_Create is to be changed e.g. N6 traffic routing details corresponding to the target DNAI, the AF invokes Nnef_TrafficInfluence_update service operation in order for PCF to be able to include this information in PCC rules sent to SMF. If the AF includes information such as N6 traffic routing details corresponding to the target DNAI in Nnef_TrafficInfluence_AppRelocationInfo it shall include the same information in Nnef_TrafficInfluence_update. If common DNAI or common EAS is required for set of UEs and AF is used to select common DNAI or common EAS according to operator's configuration, the AF determines the common DNAI/EAS according to the candidate DNAI(s) of each UE of the set reported by SMF(s) serving the set of UEs, then informs SMF(s) of each UE of the selected common DNAI as clause 6.2.3.2.6 of TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [74] or the selected common EAS as clause 6.2.3.2.5 of TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [74]. 2e. When the NEF receives Nnef_TrafficInfluence_AppRelocationInfo, the NEF triggers the appropriate Nsmf_EventExposure_AppRelocationInfo message. 2e-a. When the NEF receives Nnef_TrafficInfluence_update, the NEF triggers step 3a as in Figure 4.3.6.2-1 or step 2 of Figure 4.3.6.4-1 if targeting an individual UE by a UE address. 2f. The AF replies to Nsmf_EventExposure_Notify by invoking Nsmf_EventExposure_AppRelocationInfo service operation either immediately or after any required application relocation in the target DNAI is completed. The AF may include N6 traffic routing details corresponding to the target DNAI and /or the 'uplink buffering' indication to indicate that buffering of uplink traffic to the target DNAI is needed. The AF may include Information for EAS IP Replacement in 5GC. AF may reply in negative e.g. if the AF determines that the application relocation cannot be completed successfully on time. 2f-a. If information sent via Npcf_PolicyAuthorization_Create is to be changed e.g. N6 traffic routing details corresponding to the target DNAI, the AF invokes Npcf_PolicyAuthorization_Update service operation in order for PCF to be able to include this information in PCC rules sent to SMF. If the AF includes information such as N6 traffic routing details corresponding to the target DNAI in Nsmf_EventExposure_AppRelocationInfo it shall include the same information in Npcf_PolicyAuthorization_Update. 3. The SMF enforces the change of DNAI or addition, change, or removal of a UPF. This may correspond to the mechanisms described in Figure 4.3.5.6-1 or in Figure 4.3.5.7-1. If the runtime coordination between 5GC and AF is enabled based on local configuration, according to the indication of "AF acknowledgment to be expected" included in AF subscription to SMF events, the SMF may wait for a response from the AF to the early notification before this step. The SMF does not perform this step until it receives a positive response from the AF, as described in clause 5.6.7 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. 4a. If late notification via NEF is requested by the AF, the SMF notifies the NEF of the target DNAI of the PDU Session or indication of EAS rediscovery and may indicate capability of supporting EAS IP replacement in 5GC by invoking Nsmf_EventExposure_Notify service operation. The SMF may provide the target AF ID if it determines that the target DNAI is not supported by the source AF. If the runtime coordination between 5GC and AF is enabled based on local configuration, according to the indication of "AF acknowledgment to be expected" included in AF subscription to SMF events, the SMF may send late notification and wait for a positive response from the AF before activating the new UP path, as described in clause 5.6.7 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. 4b. When the NEF receives Nsmf_EventExposure_Notify, the NEF performs information mapping (e.g. AF Transaction Internal ID provided in Notification Correlation ID to AF Transaction ID, SUPI to GPSI, etc.) as applicable according to clause 5.6.7 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] and triggers the appropriate Nnef_TrafficInfluence_Notify message. In this case, step 4c is not applicable. 4c. If late direct notification is requested by the AF, the SMF notifies the AF of the target DNAI of the PDU Session or indication of EAS rediscovery may indicate capability of supporting EAS IP replacement in 5GC by invoking Nsmf_EventExposure_Notify service operation. The SMF may provide the target AF ID if it determines that the target DNAI is not supported by the source AF. 4d. When the AF receives either the Nnef_TrafficInfluence_Notify message or the Nsmf_EventExposure_Notify message, the AF checks whether it can serve the target DNAI. If the AF instance change is needed, the AF determines the proper target AF for the target DNAI (e.g. based on locally configured information or the AF ID provided by the SMF in step 4a or 4c) and performs the AF migration. NOTE 5: If the source AF is already locally configured with information associated with the target DNAI, the source AF is assumed to use the locally configured information, even if it has received from the SMF target AF ID in a previous step above. NOTE 6: The determination of the target AF for the target DNAI and the AF migration to the target AF are out of the scope of this release. 4e. The AF replies to Nnef_TrafficInfluence_Notify by invoking Nnef_TrafficInfluence_AppRelocationInfo service operation either immediately or after any required application relocation in the target DNAI is completed. AF includes N6 traffic routing details corresponding to the target DNAI. AF may reply in negative e.g. if the AF determines that the application relocation cannot be completed successfully on time. Nnef_TrafficInfluence_AppRelocationInfo with positive response may indicate that buffering of uplink traffic to the target DNAI is no more needed. If SMF has sent an EAS re-discovery request to the UE as defined in TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [74], e.g. due to change of common EAS, the SMF sends an indication to the AF that an EAS re-discovery request has been sent to the UE. NOTE 7: The action taken by the AF when receiving such an indication that an EAS re-discovery request has been sent to the UE is out of scope of 3GPP specifications. 4e-a. If information sent via Nnef_TrafficInfluence_Create/Update is to be changed e.g. N6 traffic routing details corresponding to the target DNAI, the AF invokes Nnef_TrafficInfluence_Create or Nnef_TrafficInfluence_Update service operation in order for PCF to be able to include this information in PCC rules sent to SMF. The Nnef_TrafficInfluence_Create shall be used if the AF is notified (e.g. in step 4b) that the UE IP address is changed and the initial Nnef_TrafficInfluence_Create was targeted to an individual UE address, otherwise the Nnef_TrafficInfluence_Update may be used. If the AF includes information such as N6 traffic routing details corresponding to the target DNAI in Nnef_TrafficInfluence_AppRelocationInfo it shall include the same information in Nnef_TrafficInfluence_Create or Nnef_TrafficInfluence_Update, whichever is appropriate. 4f. When the NEF receives Nnef_TrafficInfluence_AppRelocationInfo, the NEF triggers the appropriate Nsmf_EventExposure_AppRelocationInfo message. 4f-a. When the NEF receives Nnef_TrafficInfluence_Create/update, the NEF triggers step 3a as in Figure 4.3.6.2-1 or step 2 of Figure 4.3.6.4-1 if targeting an individual UE by a UE address. 4g. The AF replies to Nsmf_EventExposure_Notify by invoking Nsmf_EventExposure_AppRelocationInfo service operation either immediately or after any required application relocation in the target DNAI is completed. AF includes N6 traffic routing details corresponding to the target DNAI. AF may reply in negative e.g. if the AF determines that the application relocation cannot be completed successfully on time. Nsmf_EventExposure_AppRelocationInfo with positive response may indicate that buffering of uplink traffic to the target DNAI is no more needed. 4g-a. If information sent via Npcf_PolicyAuthorization_Create/Update is to be changed e.g. N6 traffic routing details corresponding to the target DNAI, the AF invokes Npcf_PolicyAuthorization_Create or Npcf_PolicyAuthorization_Update service operation in order for PCF to be able to include this information in PCC rules sent to SMF. The Npcf_PolicyAuthorization_Create shall be used if the AF is notified (e.g. in step 4c) that the UE IP address is changed, otherwise the Npcf_PolicyAuthorization_Update may be used. If the AF includes information such as N6 traffic routing details corresponding to the target DNAI in Nsmf_EventExposure_AppRelocationInfo it shall include the same information in Npcf_PolicyAuthorization_Create or Npcf_PolicyAuthorization_Update, whichever is appropriate. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.3.6.3 |
2,230 | 4.13.7.2 The procedure of MSISDN-less MO SMS Service | Figure 4.13.7.2-1: MSISDN-less MO SMS procedure via Nnef 1. The UE uses SMS over NAS procedures in clause 4.13.3 to send an SMS to the AF. The service centre address points to the SMS-SC which contains the function described in this procedure, the destination SME address is set to short/long code of the AF and the Application Port ID element of the TP-User-Data field is set to the appropriate value. For MSISDN-less subscription, the dummy MSISDN is used. This MSISDN and the IMSI of the UE are sent to SMS-SC. 2. SMS-SC uses the destination SME address (long/short code of the AF) to identify the corresponding NEF based on a pre-configured mapping table. SMS-SC extracts the SMS payload, Application port ID and IMSI of the UE and delivers them to NEF along with the destination SME address (long/short code of the AF). The NEF acts as an MTC-IWF in this procedure. 3. The NEF invokes Nudm_SDM_Get (Identifier Translation, IMSI, Application Port ID, AF Identifier) to resolve the IMSI and Application Port ID to a GPSI (External Id). 4. The UDM provides a Nudm_SDM_Get response (GPSI). If the UE is not allowed to send an SMS payload to this AF, or there is no valid subscription information for this user, the flow proceeds to step 6. 5. The NEF provides a Nnef_MSISDN-less_MO_SMSNotify (SMS payload, GPSI and Application Port ID) message to the AF. The AF is identified with the destination SME address (long/short code of the AF) received from step 2. The payload is delivered directly to the AF, it is not processed by NEF. 6. The NEF, acting as an MTC-IWF, returns a success or failure delivery indication to SMS-SC. 7. SMS-SC indicates success/failure back to UE using existing SMS delivery report defined in TS 23.040[ Technical realization of the Short Message Service (SMS) ] [7]. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.13.7.2 |
2,231 | 4.2.1.3 Piggybacked Messages | A piggybacked initial message is carried as a concatenation after a triggered response message and they share a common UDP header (see Figure 4.2.0-2). The UDP Destination port for the IP packet containing both the triggered response message and the piggybacked initial message shall be the same as the port number used for the triggered response message. The UDP Source port for the IP packet containing both the triggered response message and the piggybacked initial message shall be the same as the port number used for the triggered response message. | 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 | 4.2.1.3 |
2,232 | 4.11.1.3.3A EPS to 5GS Idle mode mobility using N26 interface with data forwarding | Figure 4.11.1.3.3A-1 describes the idle mode mobility registration procedure from EPS to 5GS when N26 is supported with data forwarding. Figure 4.11.1.3.3A-1: EPS to 5GS Idle mode mobility using N26 interface with data forwarding 1. Step 1-7 from clause 4.11.1.3.3 with the following enhancements: - In step 5b of the figure 4.11.1.3.3-1, if the old MME indicates Buffered DL Data Waiting in the Context Response (as specified in step 5 of clause 5.3.3.1A in TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13]). - For Control Plane CIoT EPS Optimisation, when the DL data is buffered in old MME and the DL Data Expiration Time has not expired, the old MME shall discard the buffered DL data (as specified in step of clause 5.3.3.1A in TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13]). 2. Steps 9-18 from clause 4.11.1.3.3 with following enhancements: In step 14a of the figure 4.11.1.3.3-1, the AMF forwards the Buffered DL Data Waiting indication from above to (V-)SMF in Nsmf_PDUSession_CreateSMContext service operation. If the Buffered DL Data Waiting indication is provided by AMF, the (V-)SMF and (V-)UPF shall allocate the user plane resource and include the N2 SM information (i.e. the V-CN Tunnel-Info) in the Nsmf_PDUSession_CreateSMContext Response towards the AMF in step 14d of the figure 4.11.1.3.3-1 to trigger the user plane setup in NG-RAN. NOTE: AMF may send NAS message Registration Accept in step 17 of figure 4.11-1.3.3-1 as part of the N2 message in step 3 below. 3. AMF to NG-RAN: N2 message (N2 MM information, N2 SM information list). If N2 SM information is received from SMF in step 2 above, the AMF sends a N2 request message to setup the user plane resource. NG-RAN performs RRC connection Reconfiguration with the UE to setup the user plane resource and response to AMF with N2 response message with N2 SM information. 4. Steps 11-13 from clause 4.11.1.2.2.2 with the following enhancement: Based on Buffered DL Data Waiting indication received in step 2 above, the (V-)SMF and (V-)UPF allocate data forwarding tunnel resource and provide the CN tunnel information for data forwarding from EPS (i.e. Forwarding F TEID) in Nsmf_PDUSession_UpdateSMContext Response to AMF in step 13 of figure 4.11.1.2.2.2-1. The (V-) SMF also starts a timer for release of resources for data forwarding. The (V-) SMF may select a different UPF from the serving (V-)UPF for data forwarding. The (V-)SMF shall not provide Charging Enforcement Rules and QoS Enforcement Rules to the (V-)UPF for DL packets that were received via the forwarding tunnel. 5. Steps 14-18 from clause 5.3.3.1A in TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13] with following changes. The AMF sends the Context Acknowledge message to MME as in step 14 of figure 5.3.3.1A-1 in TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13], including the CN tunnel information (i.e. Forwarding F TEID) for data forwarding from EPS received from (V-)SMF in step 4 above. The Serving GW forwards the buffered DL data to the (V-)UPF based on the Forwarding F-TEID received from MME. The data received by the (V-)UPF on the forwarding F-TEID is forwarded by the (V-)UPF on the (newly) established N3 tunnel to the NG-RAN. 6. SMF to UPF: N4 Session Termination/Modification. At the expiration of the timer started in step 4 above, the (V-) SMF starts the release of resource established in step 4 for data forwarding and informs the (V-)UPF. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.11.1.3.3A |
2,233 | – BeamFailureRecoveryConfig | The IE BeamFailureRecoveryConfig is used to configure the UE with RACH resources and candidate beams for beam failure recovery in case of beam failure detection. See also TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3], clause 5.1.1. BeamFailureRecoveryConfig information element -- ASN1START -- TAG-BEAMFAILURERECOVERYCONFIG-START BeamFailureRecoveryConfig ::= SEQUENCE { rootSequenceIndex-BFR INTEGER (0..137) OPTIONAL, -- Need M rach-ConfigBFR RACH-ConfigGeneric OPTIONAL, -- Need M rsrp-ThresholdSSB RSRP-Range OPTIONAL, -- Need M candidateBeamRSList SEQUENCE (SIZE(1..maxNrofCandidateBeams)) OF PRACH-ResourceDedicatedBFR OPTIONAL, -- Need M ssb-perRACH-Occasion ENUMERATED {oneEighth, oneFourth, oneHalf, one, two, four, eight, sixteen} OPTIONAL, -- Need M ra-ssb-OccasionMaskIndex INTEGER (0..15) OPTIONAL, -- Need M recoverySearchSpaceId SearchSpaceId OPTIONAL, -- Need R ra-Prioritization RA-Prioritization OPTIONAL, -- Need R beamFailureRecoveryTimer ENUMERATED {ms10, ms20, ms40, ms60, ms80, ms100, ms150, ms200} OPTIONAL, -- Need M ..., [[ msg1-SubcarrierSpacing SubcarrierSpacing OPTIONAL -- Need M ]], [[ ra-PrioritizationTwoStep-r16 RA-Prioritization OPTIONAL, -- Need R candidateBeamRSListExt-v1610 SetupRelease{ CandidateBeamRSListExt-r16 } OPTIONAL -- Need M ]], [[ spCell-BFR-CBRA-r16 ENUMERATED {true} OPTIONAL -- Need R ]] } PRACH-ResourceDedicatedBFR ::= CHOICE { ssb BFR-SSB-Resource, csi-RS BFR-CSIRS-Resource } BFR-SSB-Resource ::= SEQUENCE { ssb SSB-Index, ra-PreambleIndex INTEGER (0..63), ... } BFR-CSIRS-Resource ::= SEQUENCE { csi-RS NZP-CSI-RS-ResourceId, ra-OccasionList SEQUENCE (SIZE(1..maxRA-OccasionsPerCSIRS)) OF INTEGER (0..maxRA-Occasions-1) OPTIONAL, -- Need R ra-PreambleIndex INTEGER (0..63) OPTIONAL, -- Need R ... } CandidateBeamRSListExt-r16::= SEQUENCE (SIZE(1.. maxNrofCandidateBeamsExt-r16)) OF PRACH-ResourceDedicatedBFR -- TAG-BEAMFAILURERECOVERYCONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
2,234 | 16.7 Public Network Integrated NPN 16.7.1 General | A PNI-NPN is a network deployed for non-public use which relies on network functions provided by a PLMN (see clause 4.8). In PNI-NPN, a Closed Access Groups (CAG) identifies a group of subscribers who are permitted to access one or more CAG cells associated to the CAG. A CAG is identified by a CAG identifier broadcast in SIB1. A CAG-capable UE can be configured with the following per PLMN (see clause 5.30.3.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [3]): - an Allowed CAG list containing the CAG identifiers which the UE is allowed to access; and - a CAG-only indication if the UE is only allowed to access 5GS via CAG cells. Dual Connectivity is supported and may involve both PNI-NPN and PLMN cells, according to the mobility restrictions in the UE context as described in TS 37.340[ Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Overall Description; Stage-2 ] [21]. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.7 |
2,235 | – SidelinkParameters | The IE SidelinkParameters is used to convey capabilities related to NR and V2X sidelink communications. SidelinkParameters information element -- ASN1START -- TAG-SIDELINKPARAMETERS-START SidelinkParameters-r16 ::= SEQUENCE { sidelinkParametersNR-r16 SidelinkParametersNR-r16 OPTIONAL, sidelinkParametersEUTRA-r16 SidelinkParametersEUTRA-r16 OPTIONAL } SidelinkParametersNR-r16 ::= SEQUENCE { rlc-ParametersSidelink-r16 RLC-ParametersSidelink-r16 OPTIONAL, mac-ParametersSidelink-r16 MAC-ParametersSidelink-r16 OPTIONAL, fdd-Add-UE-Sidelink-Capabilities-r16 UE-SidelinkCapabilityAddXDD-Mode-r16 OPTIONAL, tdd-Add-UE-Sidelink-Capabilities-r16 UE-SidelinkCapabilityAddXDD-Mode-r16 OPTIONAL, supportedBandListSidelink-r16 SEQUENCE (SIZE (1..maxBands)) OF BandSidelink-r16 OPTIONAL, ..., [[ relayParameters-r17 RelayParameters-r17 OPTIONAL ]], [[ -- R1 32-x: Use of new P0 parameters for open loop power control p0-OLPC-Sidelink-r17 ENUMERATED {supported} OPTIONAL ]], [[ pdcp-ParametersSidelink-r18 PDCP-ParametersSidelink-r18 OPTIONAL ]] } SidelinkParametersEUTRA-r16 ::= SEQUENCE { sl-ParametersEUTRA1-r16 OCTET STRING OPTIONAL, sl-ParametersEUTRA2-r16 OCTET STRING OPTIONAL, sl-ParametersEUTRA3-r16 OCTET STRING OPTIONAL, supportedBandListSidelinkEUTRA-r16 SEQUENCE (SIZE (1..maxBandsEUTRA)) OF BandSidelinkEUTRA-r16 OPTIONAL, ... } RLC-ParametersSidelink-r16 ::= SEQUENCE { am-WithLongSN-Sidelink-r16 ENUMERATED {supported} OPTIONAL, um-WithLongSN-Sidelink-r16 ENUMERATED {supported} OPTIONAL, ... } MAC-ParametersSidelink-r16 ::= SEQUENCE { mac-ParametersSidelinkCommon-r16 MAC-ParametersSidelinkCommon-r16 OPTIONAL, mac-ParametersSidelinkXDD-Diff-r16 MAC-ParametersSidelinkXDD-Diff-r16 OPTIONAL, ... } UE-SidelinkCapabilityAddXDD-Mode-r16 ::= SEQUENCE { mac-ParametersSidelinkXDD-Diff-r16 MAC-ParametersSidelinkXDD-Diff-r16 OPTIONAL } MAC-ParametersSidelinkCommon-r16 ::= SEQUENCE { lcp-RestrictionSidelink-r16 ENUMERATED {supported} OPTIONAL, multipleConfiguredGrantsSidelink-r16 ENUMERATED {supported} OPTIONAL, ..., [[ drx-OnSidelink-r17 ENUMERATED {supported} OPTIONAL ]], [[ sl-LBT-FailureDectectionRecovery-r18 ENUMERATED {supported} OPTIONAL ]] } MAC-ParametersSidelinkXDD-Diff-r16 ::= SEQUENCE { multipleSR-ConfigurationsSidelink-r16 ENUMERATED {supported} OPTIONAL, logicalChannelSR-DelayTimerSidelink-r16 ENUMERATED {supported} OPTIONAL, ... } BandSidelinkEUTRA-r16 ::= SEQUENCE { freqBandSidelinkEUTRA-r16 FreqBandIndicatorEUTRA, -- R1 15-7: Transmitting LTE sidelink mode 3 scheduled by NR Uu gnb-ScheduledMode3SidelinkEUTRA-r16 SEQUENCE { gnb-ScheduledMode3DelaySidelinkEUTRA-r16 ENUMERATED {ms0, ms0dot25, ms0dot5, ms0dot625, ms0dot75, ms1, ms1dot25, ms1dot5, ms1dot75, ms2, ms2dot5, ms3, ms4, ms5, ms6, ms8, ms10, ms20} } OPTIONAL, -- R1 15-9: Transmitting LTE sidelink mode 4 configured by NR Uu gnb-ScheduledMode4SidelinkEUTRA-r16 ENUMERATED {supported} OPTIONAL } BandSidelink-r16 ::= SEQUENCE { freqBandSidelink-r16 FreqBandIndicatorNR, --15-1 sl-Reception-r16 SEQUENCE { harq-RxProcessSidelink-r16 ENUMERATED {n16, n24, n32, n48, n64}, pscch-RxSidelink-r16 ENUMERATED {value1, value2}, scs-CP-PatternRxSidelink-r16 CHOICE { fr1-r16 SEQUENCE { scs-15kHz-r16 BIT STRING (SIZE (16)) OPTIONAL, scs-30kHz-r16 BIT STRING (SIZE (16)) OPTIONAL, scs-60kHz-r16 BIT STRING (SIZE (16)) OPTIONAL }, fr2-r16 SEQUENCE { scs-60kHz-r16 BIT STRING (SIZE (16)) OPTIONAL, scs-120kHz-r16 BIT STRING (SIZE (16)) OPTIONAL } } OPTIONAL, extendedCP-RxSidelink-r16 ENUMERATED {supported} OPTIONAL } OPTIONAL, --15-2 sl-TransmissionMode1-r16 SEQUENCE { harq-TxProcessModeOneSidelink-r16 ENUMERATED {n8, n16}, scs-CP-PatternTxSidelinkModeOne-r16 CHOICE { fr1-r16 SEQUENCE { scs-15kHz-r16 BIT STRING (SIZE (16)) OPTIONAL, scs-30kHz-r16 BIT STRING (SIZE (16)) OPTIONAL, scs-60kHz-r16 BIT STRING (SIZE (16)) OPTIONAL }, fr2-r16 SEQUENCE { scs-60kHz-r16 BIT STRING (SIZE (16)) OPTIONAL, scs-120kHz-r16 BIT STRING (SIZE (16)) OPTIONAL } }, extendedCP-TxSidelink-r16 ENUMERATED {supported} OPTIONAL, harq-ReportOnPUCCH-r16 ENUMERATED {supported} OPTIONAL } OPTIONAL, --15-4 sync-Sidelink-r16 SEQUENCE { gNB-Sync-r16 ENUMERATED {supported} OPTIONAL, gNB-GNSS-UE-SyncWithPriorityOnGNB-ENB-r16 ENUMERATED {supported} OPTIONAL, gNB-GNSS-UE-SyncWithPriorityOnGNSS-r16 ENUMERATED {supported} OPTIONAL } OPTIONAL, --15-10 sl-Tx-256QAM-r16 ENUMERATED {supported} OPTIONAL, --15-11 psfch-FormatZeroSidelink-r16 SEQUENCE { psfch-RxNumber ENUMERATED {n5, n15, n25, n32, n35, n45, n50, n64}, psfch-TxNumber ENUMERATED {n4, n8, n16} } OPTIONAL, --15-12 lowSE-64QAM-MCS-TableSidelink-r16 ENUMERATED {supported} OPTIONAL, --15-15 enb-sync-Sidelink-r16 ENUMERATED {supported} OPTIONAL, ..., [[ --15-3 sl-TransmissionMode2-r16 SEQUENCE { harq-TxProcessModeTwoSidelink-r16 ENUMERATED {n8, n16}, scs-CP-PatternTxSidelinkModeTwo-r16 ENUMERATED {supported} OPTIONAL, dl-openLoopPC-Sidelink-r16 ENUMERATED {supported} OPTIONAL } OPTIONAL, --15-5 congestionControlSidelink-r16 SEQUENCE { cbr-ReportSidelink-r16 ENUMERATED {supported} OPTIONAL, cbr-CR-TimeLimitSidelink-r16 ENUMERATED {time1, time2} } OPTIONAL, --15-22 fewerSymbolSlotSidelink-r16 ENUMERATED {supported} OPTIONAL, --15-23 sl-openLoopPC-RSRP-ReportSidelink-r16 ENUMERATED {supported} OPTIONAL, --13-1 sl-Rx-256QAM-r16 ENUMERATED {supported} OPTIONAL ]], [[ ue-PowerClassSidelink-r16 ENUMERATED {pc2, pc3, spare6, spare5, spare4, spare3, spare2, spare1} OPTIONAL ]], [[ --32-4a sl-TransmissionMode2-RandomResourceSelection-r17 SEQUENCE { harq-TxProcessModeTwoSidelink-r17 ENUMERATED {n8, n16}, scs-CP-PatternTxSidelinkModeTwo-r17 CHOICE { fr1-r17 SEQUENCE { scs-15kHz-r17 BIT STRING (SIZE (16)) OPTIONAL, scs-30kHz-r17 BIT STRING (SIZE (16)) OPTIONAL, scs-60kHz-r17 BIT STRING (SIZE (16)) OPTIONAL }, fr2-r17 SEQUENCE { scs-60kHz-r17 BIT STRING (SIZE (16)) OPTIONAL, scs-120kHz-r17 BIT STRING (SIZE (16)) OPTIONAL } } OPTIONAL, extendedCP-Mode2Random-r17 ENUMERATED {supported} OPTIONAL, dl-openLoopPC-Sidelink-r17 ENUMERATED {supported} OPTIONAL } OPTIONAL, --32-4b sync-Sidelink-v1710 SEQUENCE { sync-GNSS-r17 ENUMERATED {supported} OPTIONAL, gNB-Sync-r17 ENUMERATED {supported} OPTIONAL, gNB-GNSS-UE-SyncWithPriorityOnGNB-ENB-r17 ENUMERATED {supported} OPTIONAL, gNB-GNSS-UE-SyncWithPriorityOnGNSS-r17 ENUMERATED {supported} OPTIONAL } OPTIONAL, --32-4c enb-sync-Sidelink-v1710 ENUMERATED {supported} OPTIONAL, --32-5a-2 rx-IUC-Scheme1-PreferredMode2Sidelink-r17 ENUMERATED {supported} OPTIONAL, --32-5a-3 rx-IUC-Scheme1-NonPreferredMode2Sidelink-r17 ENUMERATED {supported} OPTIONAL, --32-5b-2 rx-IUC-Scheme2-Mode2Sidelink-r17 ENUMERATED {n5, n15, n25, n32, n35, n45, n50, n64} OPTIONAL, --32-6-1 rx-IUC-Scheme1-SCI-r17 ENUMERATED {supported} OPTIONAL, --32-6-2 rx-IUC-Scheme1-SCI-ExplicitReq-r17 ENUMERATED {supported} OPTIONAL ]], [[ -- R4 45-2: SL reception in intra-carrier guard band sl-ReceptionIntraCarrierGuardBand-r18 ENUMERATED {supported} OPTIONAL ]] } RelayParameters-r17 ::= SEQUENCE { relayUE-Operation-L2-r17 ENUMERATED {supported} OPTIONAL, remoteUE-Operation-L2-r17 ENUMERATED {supported} OPTIONAL, remoteUE-PathSwitchToIdleInactiveRelay-r17 ENUMERATED {supported} OPTIONAL, ..., [[ relayUE-U2U-OperationL2-r18 ENUMERATED {supported} OPTIONAL, remoteUE-U2U-OperationL2-r18 ENUMERATED {supported} OPTIONAL, remoteUE-U2N-PathSwitchOperationL2-r18 ENUMERATED {supported} OPTIONAL, multipathRemoteUE-PC5L2-r18 ENUMERATED {supported} OPTIONAL, multipathRelayUE-PC5L2-r18 ENUMERATED {supported} OPTIONAL, multipathRelayUE-N3C-r18 ENUMERATED {supported} OPTIONAL, multipathRemoteUE-N3C-r18 ENUMERATED {supported} OPTIONAL, remoteUE-IndirectPathAddChangeToIdleInactiveRelay-r18 ENUMERATED {supported} OPTIONAL, pdcp-DuplicationMoreThanOneUuRLC-r18 ENUMERATED {supported} OPTIONAL ]] } PDCP-ParametersSidelink-r18 ::= SEQUENCE { pdcp-DuplicationSRB-sidelink-r18 ENUMERATED {supported} OPTIONAL, pdcp-DuplicationDRB-sidelink-r18 ENUMERATED {supported} OPTIONAL, ... } -- TAG-SIDELINKPARAMETERS-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
2,236 | – SIB12 | SIB12 contains NR sidelink communication/discovery configuration. SIB12 information element -- ASN1START -- TAG-SIB12-START SIB12-r16 ::= SEQUENCE { segmentNumber-r16 INTEGER (0..63), segmentType-r16 ENUMERATED {notLastSegment, lastSegment}, segmentContainer-r16 OCTET STRING } SIB12-IEs-r16 ::= SEQUENCE { sl-ConfigCommonNR-r16 SL-ConfigCommonNR-r16, lateNonCriticalExtension OCTET STRING OPTIONAL, ..., [[ sl-DRX-ConfigCommonGC-BC-r17 SL-DRX-ConfigGC-BC-r17 OPTIONAL, -- Need R sl-DiscConfigCommon-r17 SL-DiscConfigCommon-r17 OPTIONAL, -- Need R sl-L2U2N-Relay-r17 ENUMERATED {enabled} OPTIONAL, -- Need R sl-NonRelayDiscovery-r17 ENUMERATED {enabled} OPTIONAL, -- Need R sl-L3U2N-RelayDiscovery-r17 ENUMERATED {enabled} OPTIONAL, -- Need R sl-TimersAndConstantsRemoteUE-r17 UE-TimersAndConstantsRemoteUE-r17 OPTIONAL -- Need R ]], [[ sl-FreqInfoListSizeExt-v1800 SEQUENCE (SIZE (1..maxNrofFreqSL-1-r18)) OF SL-FreqConfigCommon-r16 OPTIONAL, -- Need R sl-RLC-BearerConfigListSizeExt-v1800 SEQUENCE (SIZE (1..maxSL-LCID-r16)) OF SL-RLC-BearerConfig-r16 OPTIONAL, -- Need R sl-SyncFreqList-r18 SEQUENCE (SIZE (1..maxNrofFreqSL-r16)) OF SL-Freq-Id-r16 OPTIONAL, -- Need R sl-SyncTxMultiFreq-r18 ENUMERATED {true} OPTIONAL, -- Need R sl-MaxTransPowerCA-r18 P-Max OPTIONAL, -- Need R sl-DiscConfigCommon-v1800 SL-DiscConfigCommon-v1800 OPTIONAL -- Need R ]] } SL-ConfigCommonNR-r16 ::= SEQUENCE { sl-FreqInfoList-r16 SEQUENCE (SIZE (1..maxNrofFreqSL-r16)) OF SL-FreqConfigCommon-r16 OPTIONAL, -- Need R sl-UE-SelectedConfig-r16 SL-UE-SelectedConfig-r16 OPTIONAL, -- Need R sl-NR-AnchorCarrierFreqList-r16 SL-NR-AnchorCarrierFreqList-r16 OPTIONAL, -- Need R sl-EUTRA-AnchorCarrierFreqList-r16 SL-EUTRA-AnchorCarrierFreqList-r16 OPTIONAL, -- Need R sl-RadioBearerConfigList-r16 SEQUENCE (SIZE (1..maxNrofSLRB-r16)) OF SL-RadioBearerConfig-r16 OPTIONAL, -- Need R sl-RLC-BearerConfigList-r16 SEQUENCE (SIZE (1..maxSL-LCID-r16)) OF SL-RLC-BearerConfig-r16 OPTIONAL, -- Need R sl-MeasConfigCommon-r16 SL-MeasConfigCommon-r16 OPTIONAL, -- Need R sl-CSI-Acquisition-r16 ENUMERATED {enabled} OPTIONAL, -- Need R sl-OffsetDFN-r16 INTEGER (1..1000) OPTIONAL, -- Need R t400-r16 ENUMERATED {ms100, ms200, ms300, ms400, ms600, ms1000, ms1500, ms2000} OPTIONAL, -- Need R sl-MaxNumConsecutiveDTX-r16 ENUMERATED {n1, n2, n3, n4, n6, n8, n16, n32} OPTIONAL, -- Need R sl-SSB-PriorityNR-r16 INTEGER (1..8) OPTIONAL -- Need R } SL-NR-AnchorCarrierFreqList-r16 ::= SEQUENCE (SIZE (1..maxFreqSL-NR-r16)) OF ARFCN-ValueNR SL-EUTRA-AnchorCarrierFreqList-r16 ::= SEQUENCE (SIZE (1..maxFreqSL-EUTRA-r16)) OF ARFCN-ValueEUTRA SL-DiscConfigCommon-r17 ::= SEQUENCE { sl-RelayUE-ConfigCommon-r17 SL-RelayUE-Config-r17, sl-RemoteUE-ConfigCommon-r17 SL-RemoteUE-Config-r17 } SL-DiscConfigCommon-v1800 ::= SEQUENCE { sl-RelayUE-ConfigCommonU2U-r18 SL-RelayUE-ConfigU2U-r18, sl-RemoteUE-ConfigCommonU2U-r18 SL-RemoteUE-ConfigU2U-r18 } -- TAG-SIB12-STOP -- ASN1STOP Editor's Note: FFS whether the old indication for R17 U2N Relay can be used for R18 U2U Relay or a new U2U Relay-specific indication is needed for gNB capability of supporting U2U Relay. Editor's Note: The mapping configuration (from e2e SLRB to RLC channel) is needed in pre-configuration. The existing table format is used as a baseline, subject to discussion during maintenance. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
2,237 | 8 Performance requirement | This clause contains performance requirements for the physical channels specified in TS 36.211[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation ] [4]. The performance requirements for the UE in this clause are specified for the measurement channels specified in Annex A.3, the propagation conditions in Annex B and the downlink channels in Annex C.3.2. NOTE: For the requirements in the following sections, similar Release 8 and 9 requirements apply for time domain measurements restriction under colliding CRS. | 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,238 | 5.19.5.2 AMF Overload Control | Under unusual circumstances, if AMF has reached overload situation, the AMF activates NAS level congestion control as specified in Clause 5.19.7 and AMF restricts the load that the 5G-AN node(s) are generating, if the 5G-AN is configured to support overload control. N2 overload control can be achieved by the AMF invoking the N2 overload procedure (see TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [27] and TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [34]) to all or to a proportion of the 5G-AN nodes with which the AMF has N2 connections. The AMF may include the S-NSSAI(s) in NGAP OVERLOAD START message sent to 5G-AN node(s) to indicate the Network Slice(s) with which NAS signalling is to be restricted. To reflect the amount of load that the AMF wishes to reduce, the AMF can adjust the proportion of 5G-AN nodes which are sent NGAP OVERLOAD START message, and the content of the overload start procedure. When NGAP OVERLOAD START is sent by multiple AMFs or from the same AMF set in the same PLMN towards the 5G-AN, it should be ensured that the signalling load is evenly distributed within the PLMN and within each AMF set. A 5G-AN node supports restricting of 5G-AN signalling connection when a signalling connection establishment are attempted by certain UEs (which are registered or attempting to register with the 5GC), as specified in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [28] and TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [51]. Additionally, a 5G-AN node provides support for the barring of UEs as described in TS 22.261[ Service requirements for the 5G system ] [2]. These mechanisms are further specified in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [28] and TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [51]. For 3GPP Access Type, the signalling connection establishment attempt includes a RRC Connection Resume procedure from RRC_INACTIVE. By sending the NGAP OVERLOAD START message, the AMF can request the 5G-AN node to apply the following behaviour for UEs that the AMF is serving: a) Restrict 5G-AN signalling connection requests that are not for emergency, not for exception reporting and not for high priority mobile originated services; or b) Restrict 5G-AN signalling connection requests for uplink NAS signalling transmission to that AMF; c) Restrict 5G-AN signalling connection requests where the Requested NSSAI at AS layer only includes the indicated S-NSSAI(s) in the NGAP OVERLOAD START message. This applies also to RRC_INACTIVE Connection Resume procedure where the Allowed NSSAI in the stored UE context in the RAN only includes S-NSSAIs included in the NGAP OVERLOAD START. d) only permit 5G-AN signalling connection requests for emergency sessions and mobile terminated services for that AMF; or e) only permit 5G-AN signalling connection requests for high priority sessions, exception reporting and mobile terminated services for that AMF; The above applies for RRC Connection Establishment procedure and RRC Connection Resume procedures over 3GPP access, as well as for the UE-N3IWF connection establishment over untrusted Non-3GPP access and for the UE-TNGF connection establishment over trusted Non-3GPP access. The AMF can provide a value that indicates the percentage of connection requests to be restricted in the NGAP OVERLOAD START, and the 5G-AN node may consider this value for congestion control. When restricting a 5G-AN signalling connection, the 5G-AN indicates to the UE an appropriate wait timer that limits further 5G-AN signalling connection requests until the wait timer expires. During an overload situation, the AMF should attempt to maintain support for emergency services and for MPS. When the AMF is recovering, the AMF can either: - send a NGAP OVERLOAD START message with a new percentage value that permits more connection requests to be successful, or - send a NGAP OVERLOAD STOP message. to the same 5G-AN node(s) the NGAP OVERLOAD START was previously sent. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.19.5.2 |
2,239 | 7.6.2.1F Minimum requirements for category NB1 and NB2 | The category NB1 and NB2 UE throughput shall be ≥ 95% of the maximum throughput of the reference measurement channels as specified in Annexes A.3.2 with parameters specified in Table 7.6.2.1F-1. For Table 7.6.2.1F-1 in frequency range 1, 2 and 3, up to 24 exceptions are allowed for spurious response frequencies in each assigned frequency channel when measured using a 1MHz step size. For these exceptions the requirements of subclause 7.7.1F spurious response are applicable. Table 7.6.2.1F-1: Out-of-band blocking parameters for category NB1 and NB2 UE | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 7.6.2.1F |
2,240 | – BWP-DownlinkDedicated | The IE BWP-DownlinkDedicated is used to configure the dedicated (UE specific) parameters of a downlink BWP. BWP-DownlinkDedicated information element -- ASN1START -- TAG-BWP-DOWNLINKDEDICATED-START BWP-DownlinkDedicated ::= SEQUENCE { pdcch-Config SetupRelease { PDCCH-Config } OPTIONAL, -- Need M pdsch-Config SetupRelease { PDSCH-Config } OPTIONAL, -- Need M sps-Config SetupRelease { SPS-Config } OPTIONAL, -- Need M radioLinkMonitoringConfig SetupRelease { RadioLinkMonitoringConfig } OPTIONAL, -- Need M ..., [[ sps-ConfigToAddModList-r16 SPS-ConfigToAddModList-r16 OPTIONAL, -- Need N sps-ConfigToReleaseList-r16 SPS-ConfigToReleaseList-r16 OPTIONAL, -- Need N sps-ConfigDeactivationStateList-r16 SPS-ConfigDeactivationStateList-r16 OPTIONAL, -- Need R beamFailureRecoverySCellConfig-r16 SetupRelease {BeamFailureRecoveryRSConfig-r16} OPTIONAL, -- Cond SCellOnly sl-PDCCH-Config-r16 SetupRelease { PDCCH-Config } OPTIONAL, -- Need M sl-V2X-PDCCH-Config-r16 SetupRelease { PDCCH-Config } OPTIONAL -- Need M ]], [[ preConfGapStatus-r17 BIT STRING (SIZE (maxNrofGapId-r17)) OPTIONAL, -- Cond PreConfigMG beamFailureRecoverySpCellConfig-r17 SetupRelease { BeamFailureRecoveryRSConfig-r16} OPTIONAL, -- Cond SpCellOnly harq-FeedbackEnablingforSPSactive-r17 BOOLEAN OPTIONAL, -- Need R cfr-ConfigMulticast-r17 SetupRelease { CFR-ConfigMulticast-r17 } OPTIONAL, -- Need M dl-PPW-PreConfigToAddModList-r17 DL-PPW-PreConfigToAddModList-r17 OPTIONAL, -- Need N dl-PPW-PreConfigToReleaseList-r17 DL-PPW-PreConfigToReleaseList-r17 OPTIONAL, -- Need N nonCellDefiningSSB-r17 NonCellDefiningSSB-r17 OPTIONAL, -- Need R servingCellMO-r17 MeasObjectId OPTIONAL -- Cond MeasObject-NCD-SSB ]], [[ tci-SelectionPresentIn-DCI-r18 ENUMERATED { enabled } OPTIONAL, -- Need R applyIndicatedTCI-StateDCI-1-0-r18 ENUMERATED {first, second, both} OPTIONAL -- Need R ]] } SPS-ConfigToAddModList-r16 ::= SEQUENCE (SIZE (1..maxNrofSPS-Config-r16)) OF SPS-Config SPS-ConfigToReleaseList-r16 ::= SEQUENCE (SIZE (1..maxNrofSPS-Config-r16)) OF SPS-ConfigIndex-r16 SPS-ConfigDeactivationState-r16 ::= SEQUENCE (SIZE (1..maxNrofSPS-Config-r16)) OF SPS-ConfigIndex-r16 SPS-ConfigDeactivationStateList-r16 ::= SEQUENCE (SIZE (1..maxNrofSPS-DeactivationState)) OF SPS-ConfigDeactivationState-r16 DL-PPW-PreConfigToAddModList-r17 ::= SEQUENCE (SIZE (1..maxNrofPPW-Config-r17)) OF DL-PPW-PreConfig-r17 DL-PPW-PreConfigToReleaseList-r17 ::= SEQUENCE (SIZE (1..maxNrofPPW-Config-r17)) OF DL-PPW-ID-r17 -- TAG-BWP-DOWNLINKDEDICATED-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
2,241 | 5.3.5.2 3GPP access service area restrictions | The service area restrictions consist of tracking areas forming either an allowed area, or a non-allowed area. The tracking areas belong to the registered PLMN, its equivalent PLMNs in the registration area, or the registered SNPN. The allowed area can contain up to 16 tracking areas or include all tracking areas in the registered PLMN and its equivalent PLMN(s) in the registration area, or in the registered SNPN. The non-allowed area can contain up to 16 tracking areas. The network conveys the service area restrictions to the UE by including either an allowed area, or a non-allowed area, but not both, in the Service area list IE of a REGISTRATION ACCEPT message or a CONFIGURATION UPDATE COMMAND message. If the network does not convey the service area restrictions to the UE in the Service area list IE of a REGISTRATION ACCEPT message, the UE shall treat all tracking areas in the registered PLMN, its equivalent PLMN(s) in the registration area, or in the registered SNPN, as allowed area and delete the stored list of "allowed tracking areas" or the stored list of "non-allowed tracking areas". When the UE receives a Service area list IE with an allowed area indication during a registration procedure or a generic UE configuration update procedure: a) if the "Type of list" included in the Service area list IE does not indicate "all TAIs belonging to the PLMNs in the registration area are allowed area", the UE shall delete the old list of "allowed tracking areas" and store the tracking areas in the allowed area as the list of "allowed tracking areas". If the UE has a stored list of "non-allowed tracking areas", the UE shall delete that list; or b) if the "Type of list" included in the Service area list IE indicates "all TAIs belonging to the PLMNs in the registration area are allowed area", the UE shall treat all tracking areas in the registered PLMN and its equivalent PLMN(s), or in the registered SNPN, as allowed area and delete the stored list of "allowed tracking areas" or the stored list of "non-allowed tracking areas". When the UE receives a Service area list IE with a non-allowed area indication during a registration procedure or a generic UE configuration update procedure, the UE shall delete the old list of "non-allowed tracking areas" and store the tracking areas in the non-allowed area as the list of "non-allowed tracking areas". If the UE has a stored list of "allowed tracking areas", the UE shall delete that list. If the UE is successfully registered to a PLMN or SNPN and has a stored list of "allowed tracking areas": a) while the current TAI is in the list of "allowed tracking areas", the UE shall stay in, or enter, the state 5GMM-REGISTERED.NORMAL-SERVICE and is allowed to initiate any 5GMM and 5GSM procedures; and b) while the UE is camped on a cell which is in the registered PLMN, a PLMN from the list of equivalent PLMNs, or the registered SNPN, and the current TAI is not in the list of "allowed tracking areas", the UE shall enter the state 5GMM-REGISTERED.NON-ALLOWED-SERVICE, and: 1) if the UE is in 5GMM-IDLE mode or 5GMM-IDLE mode with suspend indication over 3GPP access, the UE: i) shall not include the Uplink data status IE in the registration procedure for mobility and periodic registration update except for emergency services or for high priority access; ii) shall not perform the registration procedure for mobility and periodic registration update with Follow-on request indicator set to "Follow-on request pending", except for: - emergency services; - high priority access; - indicating a change of 3GPP PS data off UE status; - sending an SOR transparent container; - sending a UE policy container; or - sending a UE parameters update transparent container; iii) shall not initiate a service request procedure or request the lower layers to resume a suspended connection, except for: - emergency services; - emergency services fallback; - high priority access; - responding to paging; - responding to notification received over non-3GPP access; - indicating a change of 3GPP PS data off UE status; - sending an SOR transparent container; - sending a UE policy container; or - sending a UE parameters update transparent container. The UE shall not include the Uplink data status IE in the SERVICE REQUEST message or CONTROL PLANE SERVICE REQUEST message except for emergency services or for high priority access. In case of emergency services, the UE shall indicate that uplink data is pending only for the PDU session for emergency services; iv) if the UE responds to a paging which includes an indication for non-3GPP access type, the UE shall include the Allowed PDU session status IE in the SERVICE REQUEST, CONTROL PLANE SERVICE REQUEST or REGISTRATION REQUEST message and indicate for each PDU session in the information element that re-establishment of the user-plane resources via 3GPP access is not allowed; and 2) if the UE is in 5GMM-CONNECTED mode or 5GMM-CONNECTED mode with RRC inactive indication over 3GPP access, the UE: i) shall not perform the registration procedure for mobility and periodic registration update with Uplink data status IE except for emergency services or for high priority access; ii) shall not initiate a service request procedure except for: - emergency services; - emergency services fallback; - high priority access; - responding to paging or responding to a notification. The UE shall not include the Uplink data status IE in the SERVICE REQUEST message or CONTROL PLANE SERVICE REQUEST message except for emergency services or for high priority access. In case of emergency services, the UE shall indicate that uplink data is pending only for the PDU session for emergency services; iii) shall not initiate a 5GSM procedure except for: - emergency services; - high priority access; or - indicating a change of 3GPP PS data off UE status; iv) shall not perform the NAS transport procedure except for the sending: - SMS; - an LPP message; - a UPP-CMI container; - an SLPP message; - a location services message; - an SOR transparent container; - a UE policy container; - a UE parameters update transparent container; or - a CIoT user data container; and NOTE 1: The contents of CIoT user data container can be data that is not for exception reports, or data that is for exception reports if allowed for the UE (see subclause 6.2.13). v) if the UE responds to a notification which includes an indication for non-3GPP access type, the UE shall include the Allowed PDU session status IE in the SERVICE REQUEST, CONTROL PLANE SERVICE REQUEST or REGISTRATION REQUEST message and indicate for each PDU session in the information element that re-establishment of the user-plane resources via 3GPP access is not allowed. If the UE is successfully registered to a PLMN or an SNPN and has a stored list of "non-allowed tracking areas": a) while the UE is camped on a cell which is in the registered PLMN,a PLMN from the list of equivalent PLMNs, or the registered SNPN, and the current TAI is not in the list of "non-allowed tracking areas", the UE shall stay in, or enter, the state 5GMM-REGISTERED.NORMAL-SERVICE and is allowed to initiate any 5GMM and 5GSM procedures; and b) while the current TAI is in the list of "non-allowed tracking areas", the UE shall enter the state 5GMM-REGISTERED.NON-ALLOWED-SERVICE, and: 1) if the UE is in 5GMM-IDLE mode or 5GMM-IDLE mode with suspend indication over 3GPP access, the UE: i) shall not include the Uplink data status IE in the registration procedure for mobility and periodic registration update except for emergency services or for high priority access; ii) shall not perform the registration procedure for mobility and periodic registration update with Follow-on request indicator set to "Follow-on request pending", except for: - emergency services; - high priority access; - indicating a change of 3GPP PS data off UE status; - sending an SOR transparent container; - sending a UE policy container; or - sending a UE parameters update transparent container; and iii) shall not initiate a service request procedure or request the lower layers to resume a suspended connection, except for: - emergency services; - emergency services fallback; - high priority access; - responding to paging; - responding to notification received over non-3GPP access; - indicating a change of 3GPP PS data off UE status; - sending an SOR transparent container; - sending a UE policy container; or - sending a UE parameters update transparent container. The UE shall not include the Uplink data status IE in the SERVICE REQUEST message or CONTROL PLANE SERVICE REQUEST message except for emergency services or for high priority access. In case of emergency services, the UE shall indicate that uplink data is pending only for the PDU session for emergency services; iv) if the UE responds to a paging which includes an indication for non-3GPP access type, the UE shall include the Allowed PDU session status IE in the SERVICE REQUEST, CONTROL PLANE SERVICE REQUEST or REGISTRATION REQUEST message and indicate for each PDU session in the information element that re-establishment of the user-plane resources via 3GPP access is not allowed; and 2) if the UE is in 5GMM-CONNECTED mode or 5GMM-CONNECTED mode with RRC inactive indication over 3GPP access, the UE: i) shall not perform the registration procedure for mobility and periodic registration update with the Uplink data status IE except for emergency services or for high priority access; ii) shall not initiate a service request procedure or request the lower layers to resume a suspended connection, except for: - emergency services; - emergency services fallback; - high priority access; or - responding to paging or responding to a notification. The UE shall not include the Uplink data status IE in the SERVICE REQUEST message or CONTROL PLANE SERVICE REQUEST message except for emergency services or for high priority access. In case of emergency services, the UE shall indicate that uplink data is pending only for the PDU session for emergency services; iii) shall not initiate a 5GSM procedure except for: - emergency services; - high priority access; or - indicating a change of 3GPP PS data off UE status; iv) shall not perform the NAS transport procedure except for the sending: - SMS; - an LPP message; - a UPP-CMI container; - an SLPP message; - a location services message; - an SOR transparent container; - a UE policy container; - a UE parameters update transparent container; or - a CIoT user data container; and NOTE 2: The contents of CIoT user data container can be data that is not for exception reports, or data that is for exception reports if allowed for the UE (see subclause 6.2.13). v) if the UE responds to a notification which includes an indication for non-3GPP access type, the UE shall include the Allowed PDU session status IE in the SERVICE REQUEST, CONTROL PLANE SERVICE REQUEST or REGISTRATION REQUEST message and indicate for each PDU session in the information element that re-establishment of the user-plane resources via 3GPP access is not allowed. The list of "allowed tracking areas", as well as the list of "non-allowed tracking areas" shall be erased when: a) the UE is switched off; and b) the UICC containing the USIM is removed or an entry of the "list of subscriber data" with the SNPN identity of the SNPN is updated. When a tracking area is added to the list of "5GS forbidden tracking areas for roaming" or to the list of "5GS forbidden tracking areas for regional provision of service" as specified in the subclauses 5.5.1.2.5 or 5.5.1.3.5, the tracking area shall be removed from the list of "allowed tracking areas" if the tracking area is already present in the list of "allowed tracking areas" and from the list of "non-allowed tracking areas" if the tracking area is already present in the list of "non-allowed tracking areas". | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.3.5.2 |
2,242 | 9.5.22 Activate MBMS Context Request | This message is sent by the MS to the network as an explicit response to a Request MBMS Context Activation message See table 9.5.22/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Message type: activate MBMS context REQUEST Significance: global Direction: MS to network Table 9.5.22 : Activate MBMS context request message content NOTE: The MBMS NSAPI will be used in Iu mode when the network chooses a point-to-point MBMS bearer for the transfer of MBMS data in the user plane. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.5.22 |
2,243 | 6.1.3.6 Receiving a SM STATUS message by a SM entity | If the SM entity of the MS receives an SM STATUS message the MS shall take different actions depending on the received SM cause value: #81 Invalid transaction identifier value The MS shall abort any ongoing SM procedure related to the received transaction identifier value, stop any related timer, and deactivate the corresponding PDP or MBMS context locally (without peer to peer signalling between the MS and the network). If one or more MBMS contexts are linked to a PDP context that has been deactivated, the MS shall deactivate all those MBMS Contexts locally (without peer to peer signalling between the MS and the network). #97 Message type non-existent or not implemented The MS shall abort any ongoing SM procedure related to the received transaction identifier value and stop any related timer. If the SM entity of the MS receives a SM STATUS message with any other SM cause value no state transition and no specific action shall be taken as seen from the radio interface, i.e. local actions are possible. If the SM entity of the network receives an SM STATUS message the network shall take different actions depending on the received SM cause value: #81 Invalid transaction identifier value The network shall abort any ongoing SM procedure related to the received transaction identifier value, stop any related timer, and deactivate the corresponding PDP or MBMS context locally (without peer to peer signalling between the MS and the network). If one or more MBMS contexts are linked to a PDP context that has been deactivated, the MS shall deactivate all those MBMS Contexts locally (without peer to peer signalling between the MS and the network). #97 Message type non-existent or not implemented The network shall abort any ongoing SM procedure related to the received transaction identifier value and stop any related timer. The actions to be taken in the network on receiving a SM STATUS message with any other SM cause value are an implementation dependent option. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.1.3.6 |
2,244 | Change Notification Response | The Change Notification Response message may be sent on the S11/S4 interface by the SGW to the MME/SGSN and is sent on the S5/S8 interface by the PGW to the SGW as part of location dependent charging related procedures to acknowledge the receipt of a Change Notification Request. If SGW does not support the feature (see clause 7.3.14 "Change Notification Request"), SGW may silently discard Change Notification Request message from MME/SGSN. If the MME/ SGSN does not receive Change Notification Response, the MME/SGSN may either send Change Notification Request to the same SGW next time UE location changes, or not (marking SGW as not supporting the feature). The Cause value indicates whether or not the Change Notification Request was received correctly. Possible Cause values are specified in Table 8.4-1. Message specific cause values are: "Request accepted". "Request accepted partially". "IMSI/IMEI not known". In this version of the specification, the sender shall set the header TEID value to that of the peer node's Control Plane TEID on S11/S4 interface or to the peer node's Control Plane TEID on S5/S8 interface. However a receiver shall be prepared to receive messages in which the header TEID value is set to zero from implementation conforming to earlier versions of this specification. When that is the case, the receiver identifies the subscriber context based on the included LBI, IMSI, and/or MEI IEs. If the IMSI is unknown, or the IMEI is unknown when the UE is emergency attached and UICCless or the UE is emergency attached but the IMSI is not authenticated for the receiving GTP-C entity, then the message shall be silently discarded and no further processing of the IEs shall continue. If the MME/SGSN receives Change Notification Response containing a Cause value of "IMSI/IMEI not known" and CS bit set to 1, this indicates that the associated PDN connection does not exist within the PGW. The Change Reporting mechanism shall be stopped in the receiving SGSN/MME for all Bearers of the associated PDN connection. The SGSN/MME shall then initiate PDN disconnection for all of these PDN Connections. If the PDN Connection associated of the Change Notification Request message received by the SGW does not exist within the SGW, the SGW shall return Change Notification Response with the CS bit set to 0 to the MME/SGSN. The Change Reporting mechanism shall be stopped in the receiving SGSN/MME for all Bearers of the associated PDN connection, and the MME/SGSN shall then locally delete the PDN connection and release all associated resources. If the location Change Reporting mechanism is to be stopped or modified for this subscriber in the SGSN/MME, then the PGW shall include the Change Reporting Action IE in the message and shall set the value of the Action field appropriately. If the MME has sent the "MO Exception Data Counter" for the RRC Cause "MO Exception data" in the Change Notification Resquest, the MME shall reset the counter value when receiving the Change Notification Response message. Table -1: Information Element in Change Notification 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 | Change |
2,245 | 5.4.3 Paging strategy handling 5.4.3.1 General | Based on operator configuration, the 5GS supports the AMF and NG-RAN to apply different paging strategies for different types of traffic. In the case of UE in CM-IDLE state, the AMF performs paging and determines the paging strategy based on e.g. local configuration, what NF triggered the paging and information available in the request that triggered the paging. If NWDAF is deployed, the AMF may also use analytics (i.e. statistics or predictions) on the UE's mobility as provided by NWDAF (see TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [86]). In the case of UE in CM-CONNECTED with RRC_INACTIVE state, the NG-RAN performs paging and determines the paging strategy based on e.g. local configuration, and information received from AMF as described in clause 5.4.6.3 and SMF as described in clause 5.4.3.2. In the case of Network Triggered Service Request from SMF, the SMF determines the 5QI and ARP based on the downlink packet (if the SMF performs buffering) or the Downlink Data Report received from UPF (if the UPF performs buffering). The SMF includes the 5QI and ARP corresponding to the QoS Flow of the received downlink PDU in the request sent to the AMF. If the UE is in CM IDLE, the AMF uses e.g. the 5QI and ARP to derive different paging strategies as described in clause 4.2.3.3 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. NOTE: The 5QI is used by AMF to determine suitable paging strategies. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.4.3 |
2,246 | 6.1.1 Presence requirements of Information Elements | There are four different presence requirements (Mandatory, Conditional, Optional, or Conditional-Optional) for an IE within a given GTP-PDU: - Mandatory means that the IE shall be included by the sending side, and that the receiver diagnoses a "Mandatory IE missing" error, when detecting that the IE is not present. A response including a "Mandatory IE missing" cause, shall include the type of the missing IE. - Conditional means: - that the IE shall be included by sending entity if the conditions specified in the relevant protocol specification are met; - the receiver shall check the conditions as specified in the corresponding message type description, based on the parameter combination in the message and/or on the state of the receiving node, to infer if a conditional IE shall be expected. Only if a receiver has sufficient information the following applies. A conditional IE, which is absolutely necessary for the receiving entity to complete the procedure, is missing, then the receiver shall abort the procedure. - Conditional-Optional means: - that the IE shall be included by the up-to-date sending entity, if the conditions specified in the relevant protocol specification are met. An entity, which is at an earlier version of the protocol and therefore is not up-to-date, obviously cannot send such new IE. - the receiver need not check the presence of the IE in the message. If the receiver checks the presence of the Conditional-Optional IE, then the IE's absence shall not trigger any of the error handling procedures. The handling of an absence or erroneous such IEs shall be treated as Optional IEs as specified in clause 7.7 "Error Handling". - Optional means: - that the IE shall be included as a service option. Therefore, the IE may be included or not in a message. The handling of an absent optional IE, or an erroneous optional IE is specified in clause 7.7 "Error Handling". For conditional IEs, the clause describing the GTP-PDU explicitly defines the conditions under which the inclusion of each IE becomes mandatory or optional for that particular GTP-PDU. These conditions shall be defined so that the presence of a conditional IE only becomes mandatory if it is critical for the receiving entity. The definition might reference other protocol specifications for final terms used as part of the condition. For grouped IEs, the presence requirement of the embedded IE shall follow the rules: - The grouped IE is Mandatory within a given message: the presence requirements of individual embedded IEs are as stated within the Mandatory grouped IE for the given message. - The grouped IE is Conditional within a given message: if the embedded IE in the grouped IE is Mandatory or Conditional, this embedded IE is viewed as Conditional IE by the receiver. If the embedded IE in the grouped IE is Conditional-Optional, this embedded IE is viewed as Optional IE by the receiver. If the embedded IE in the grouped IE is Optional, this embedded IE is viewed as Optional IE by the receiver. - The grouped IE is Conditional-Optional within a given message: if the embedded IE in the grouped IE is Mandatory or Conditional, this embedded IE is viewed as Conditional-Optional IE by the receiver. If the embedded IE in the grouped IE is Conditional-Optional, this embedded IE is viewed as Optional IE by the receiver. If the embedded IE in the grouped IE is Optional, this embedded IE is viewed as Optional IE by the receiver. - The grouped IE is Optional within a given message: all embedded IEs in the grouped IE are viewed as Optional IEs by the receiver. In all of the above cases, appropriate error handling as described in clause 7.7 shall be applied for protocol errors of the embedded IEs. Only the Cause information element at message level shall be included in the response if the Cause contains a value that indicates that the request is not accepted regardless of whether there are other mandatory or conditional information elements defined for a given response message. The following are exceptions: - Optionally, the Protocol Configuration Options, Recovery, User Location Information (ULI), Load Control Information, Overload Control Information, Bearer Context and Local Distinguished Name (LDN) information elements may be included. - For the rejection response of a Forward Relocation Request, the Forward Relocation Response message may also include an F-Cause IE as specified in clause 7.3.2. - For the rejection response of a SRVCC PS to CS Request, the SRVCC PS to CS Response message may also include an SRVCC Cause IE as specified in clause 5.2.3 in 3GPP TS 29.280[ Evolved Packet System (EPS); 3GPP Sv interface (MME to MSC, and SGSN to MSC) for SRVCC ] [15]. - A Downlink Data Notification Acknowledge (with or) without an indication of success may also include a DL low priority traffic Throttling IE and the IMSI IE. - The PGW Back-Off Time IE may also be returned when rejecting a Create Session Request with the cause "APN Congestion". - Change Notification Response message may also include the IMSI and MEI information elements. - Failure Indication type messages do not have "Accept" types of Cause values, i.e. all used values indicate the rejection, therefore for Failure Indication type of triggered messages, other information elements, other than the Cause IE, shall also be included according to the conditions of presence specified in the respective message, if they are available. - The Context Response message (sent by an SGSN or MME) should also include the IMSI IE if the Cause IE contains the value "P-TMSI Signature mismatch", except if the UE is emergency or RLOS attached and the UE is UICCless. - The Create Bearer Response message, the Update Bearer Response message and the Delete Bearer Response message shall include the RAN/NAS Cause IE according to the conditions specified in clauses 7.2.4, 7.2.16 and 7.2.10.2. - The UE Registration Query Response message shall include IMSI to allow the SGSN to correlate the response message with the corresponding request. If the Cause information element at Grouped IE level contains a value that indicates that the Grouped IE is not handled correctly, e.g. "Context Not Found" at Bearer Context IE level, the other information elements in this Grouped IE, other than the Cause IE, may not be included. | 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 | 6.1.1 |
2,247 | 9.1 Overview | Load balancing is achieved in NR with handover, redirection mechanisms upon RRC release and through the usage of inter-frequency and inter-RAT absolute priorities and inter-frequency Qoffset parameters. Measurements to be performed by a UE for connected mode mobility are classified in at least four measurement types: - Intra-frequency NR measurements; - Inter-frequency NR measurements; - Inter-RAT measurements for E-UTRA; - Inter-RAT measurements for UTRA. For each measurement type one or several measurement objects can be defined (a measurement object defines e.g. the carrier frequency to be monitored). For each measurement object one or several reporting configurations can be defined (a reporting configuration defines the reporting criteria). Three reporting criteria are used: event triggered reporting, periodic reporting and event triggered periodic reporting. The association between a measurement object and a reporting configuration is created by a measurement identity (a measurement identity links together one measurement object and one reporting configuration of the same RAT). By using several measurement identities (one for each measurement object, reporting configuration pair) it is then possible to: - Associate several reporting configurations to one measurement object and; - Associate one reporting configuration to several measurement objects. The measurements identity is used as well when reporting results of the measurements. Measurement quantities are considered separately for each RAT. Measurement commands are used by NG-RAN to order the UE to start, modify or stop measurements. Handover can be performed within the same RAT and/or CN, or it can involve a change of the RAT and/or CN. Inter system fallback towards E-UTRAN is performed when 5GC does not support emergency services, voice services, for load balancing etc. Depending on factors such as CN interface availability, network configuration and radio conditions, the fallback procedure results in either RRC_CONNECTED state mobility (handover procedure) or RRC_IDLE state mobility (redirection), see TS 23.501[ System architecture for the 5G System (5GS) ] [3] and TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [12]. SRVCC from 5G to UTRAN, if supported by both the UE and the network, may be performed to handover a UE with an ongoing voice call from NR to UTRAN. The overall procedure is described in TS 23.216[ Single Radio Voice Call Continuity (SRVCC); Stage 2 ] [34]. See also TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [12] and TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [26]. In the NG-C signalling procedure, the AMF based on support for emergency services, voice service, any other services or for load balancing etc, may indicate the target CN type as EPC or 5GC to the gNB node. When the target CN type is received by gNB, the target CN type is also conveyed to the UE in RRCRelease Message. Inter-gNB CSI-RS based mobility, i.e. handover, is supported between two neighbour gNBs by enabling that neighbour gNBs can exchange and forward their own CSI-RS configurations and on/off status. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 9.1 |
2,248 | 5.4.4.2.5 Completion of clearing | A call control entity of the mobile station in any call control state shall, upon receipt of a RELEASE COMPLETE message from its peer entity in the network: stop all running call control timers; release the MM connection; and return to the "null" state. 5.4.4.2.5.1 Abnormal cases The call control entity of the mobile station in the "release request" state shall at first expiry of timer T308 retransmit the RELEASE message and restart timer T308. At second expiry of timer T308, the call control entity of the mobile station shall: release the MM connection; and return to the "null" state. The retransmitted RELEASE message need not contain the Facility IE including an Invoke=CCBSRequest, even if the original RELEASE message did contain this IE.5.4.5 Clear collision Clear collision occurs when both the mobile station and the network simultaneously transfer DISCONNECT messages specifying the same call. The behaviour of the network call control entity receiving a DISCONNECT message whilst in the "disconnect indication" state is specified in subclause 5.4.3. The behaviour of the MS call control entity receiving a DISCONNECT message whilst in the "disconnect request" state is defined in subclause 5.4.4. Clear collision can also occur when both sides simultaneously transfer RELEASE messages related to the same call. The entity receiving such a RELEASE message whilst within the "release request" state shall: stop timer T308; release the MM connection; and enter the "null" state (without sending a RELEASE COMPLETE message). | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.4.4.2.5 |
2,249 | 5.32.5.4 Protocol stack for user plane measurements and measurement reports | Figure 5.32.5.4-1: UE/UPF measurements related protocol stack for 3GPP access and for an MA PDU Session with type IP In the case of an MA PDU Session with type Ethernet, the protocol stack over 3GPP access is that same as the one in the above figure, but the PMF protocol operates on top of Ethernet, instead of UDP/IP. Figure 5.32.5.4-2: UE/UPF measurements related protocol stack for Untrusted non-3GPP access and for an MA PDU Session with type IP In the case of an MA PDU Session with type Ethernet, the protocol stack over Untrusted non-3GPP access is the same as the one in the above figure, but the PMF protocol operates on top of Ethernet, instead of UDP/IP. Figure 5.32.5.4-3: UE/UPF measurements related protocol stack for Trusted non-3GPP access and for an MA PDU Session with type IP In the case of an MA PDU Session with type Ethernet, the protocol stack over Trusted non-3GPP access is the same as the one in the above figure, but the PMF protocol operates on top of Ethernet, instead of UDP/IP. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.32.5.4 |
2,250 | 8.2.7.54 Registration accept type 6 IE container 8.2.7.54.1 General | This information element may be included only if the network knows that the UE will not treat this IE as unknown 'comprehension required' IE. Otherwise, the network shall not include this IE (see the 'comprehension required' scheme in subclause 11.2.5 of 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [11]). In this version of the specification, only the transfer of the information elements specified in table 8.2.7.54.1.1 is supported in the Registration accept type 6 IE container information element in the present message. For the handling of an information element with an IEI not listed in table 8.2.7.54.1.1, i.e., with an IEI unknown in the Registration accept type 6 IE container information element, see subclause 7.6.4.1. Table 8.2.7.54.1.1: Information elements and IEIs for the Registration accept type 6 IE container | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 8.2.7.54 |
2,251 | 6.10.1.2 Dual Connectivity protocol architecture for MR-DC with 5GC | The dual connectivity protocol architecture for MR-DC with 5GC is shown in figure 6.10.1.2-1. The TS 37.340[ Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Overall Description; Stage-2 ] [51] is to be referred for further details of the architecture illustrating MCG, SCG, and Split bearers for both SRBs and DRBs. The architecture has the following variants: - NG-RAN E-UTRA-NR Dual Connectivity (NGEN-DC) is the variant when the UE is connected to one ng-eNB that acts as a Master Node (MN) and one gNB that acts as a Secondary Node (SN). The ng-eNB is connected to the 5GC and the gNB is connected to the ng-eNB via Xn interface. - NR-E-UTRA Dual Connectivity (NE-DC) is the variant when the UE is connected to one gNB that acts as a MN and one ng-eNB that acts as a SN. The MN (i.e., gNB) is connected to 5GC and the ng-eNB (i.e., SN) is connected to the gNB via Xn interface. - NR-NR Dual Connectivity (NR-DC) is the variant when the UE is connected to one gNB that acts as a MN and one gNB that acts as a SN. The MN is connected to 5GC while the SN is connected to MN via Xn interface. Figure 6.10.1.2-1 Multi-Radio dual connectivity (MR-DC) protocol architecture. When the MN establishes security context between an SN and the UE for the first time for a given AS security context shared between the MN and the UE, the MN generates the KSN for the SN and sends it to the SN over the Xn-C. To generate the KSN, the MN associates a counter, called an SN Counter, with the current AS security context. The SN Counter is used as freshness input into KSN derivations as described in the clause 6.10.3.2. The MN sends the value of the SN Counter to the UE over the RRC signalling path when it is required to generate a new KSN. The KSN is used to derive further RRC and UP keys that are used between the UE and SN. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.10.1.2 |
2,252 | 24.2.4 Usage of wild cards in place of PLMN ID in ProSe Application ID | If the scope of the ProSe Application ID is country-specific, the PLMN ID part in the ProSe Application ID shall be replaced by "mcc<MCC>.mnc*" with <MCC> set to the MCC of the corresponding country. NOTE: Handling of the case when a country has been allocated more than one MCC value is outside the scope of 3GPP. If the scope of the ProSe Application ID is global, the PLMN ID part in the ProSe Application ID shall be replaced by "mcc*.mnc*". EXAMPLE: For a ProSe Application ID specific to a country with MCC 345, the PLMN ID part will be replaced by "mcc345.mnc*". | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 24.2.4 |
2,253 | 5.6.1 Channel bandwidths per operating band | a) The requirements in this specification apply to the combination of channel bandwidths and operating bands shown in Table 5.6.1-1. The transmission bandwidth configuration in Table 5.6.1-1 shall be supported for each of the specified channel bandwidths. The same (symmetrical) channel bandwidth is specified for both the TX and RX path. Table 5.6.1-1: E-UTRA channel bandwidth b) The use of different (asymmetrical) channel bandwidth for the TX and RX is not precluded and is intended to form part of a later release. | 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.6.1 |
2,254 | 5.17.1 Support for Migration from EPC to 5GC 5.17.1.1 General | Clause 5.17.1 describes the UE and network behaviour for the migration from EPC to 5GC. Deployments based on different 3GPP architecture options (i.e. EPC based or 5GC based) and UEs with different capabilities (EPC NAS and 5GC NAS) may coexist at the same time within one PLMN. It is assumed that a UE that is capable of supporting 5GC NAS procedures may also be capable of supporting EPC NAS (i.e. the NAS procedures defined in TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [13]) to operate in legacy networks e.g. in the case of roaming. The UE will use EPC NAS or 5GC NAS procedures depending on the core network by which it is served. In order to support smooth migration, it is assumed that the EPC and the 5GC have access to a common subscriber database, that is HSS in the case of EPC and the UDM in the case of 5GC, acting as the master data base for a given user as defined in TS 23.002[ Network architecture ] [21]. The PCF has access to the UDR that acts as a common subscriber database for a given user identified by a SUPI using the Nudr services defined in TS 23.502[ Procedures for the 5G System (5GS) ] [3]. Figure 5.17.1.1-1: Architecture for migration scenario for EPC and 5G CN A UE that supports only EPC based Dual Connectivity with secondary RAT NR: - always performs initial access through E-UTRA (LTE-Uu) but never through NR; - performs EPC NAS procedures over E-UTRA (i.e. Mobility Management, Session Management etc) as defined in TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [13]. A UE that supports camping on 5G Systems with 5GC NAS: - performs initial access either through E-UTRAN that connects to 5GC or NR towards 5GC; - performs initial access through E-UTRAN towards EPC, if supported and needed; - performs EPC NAS or 5GC NAS procedures over E-UTRAN or NR respectively (i.e. Mobility Management, Session Management etc) depending on whether the UE requests 5GC access or EPC access, if the UE also supports EPC NAS. When camping on an E-UTRA cell connected to both EPC and 5GC, a UE supporting EPC NAS and 5GC NAS shall select a core network type (EPC or 5GC) and initiate the corresponding NAS procedure as specified in TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [17]. In order to support different UEs with different capabilities in the same network, i.e. both UEs that are capable of only EPC NAS (possibly including EPC based Dual Connectivity with NR as secondary RAT) and UEs that support 5GC NAS procedures in the same network: - eNB that supports access to 5GC shall broadcast that it can connect to 5GC. Based on that, the UE AS layer indicates "E-UTRA connected to 5GC" capability to the UE NAS layer. In addition the eNB broadcasts the supported CIoT 5GS Optimisations that the UE uses for selecting a core network type. - It is also expected that the UE AS layer is made aware by the UE NAS layer whether a NAS signalling connection is to be initiated to the 5GC. Based on that, UE AS layer indicates to the RAN whether it is requesting 5GC access (i.e. "5GC requested" indication). The RAN uses this indication to determine whether a UE is requesting 5GC access or an EPC access. RAN routes NAS signalling to the applicable AMF or MME accordingly. NOTE: The UE that supports EPC based Dual Connectivity with secondary RAT only does not provide this "5GC requested" indication at Access Stratum when it performs initial access and therefore eNB uses the "default" CN selection mechanism to direct this UE to an MME The 5GC network may steer the UE from 5GC based on: - Core Network type restriction (e.g. due to lack of roaming agreements) described in clause 5.3.4.1.1; - Availability of EPC connectivity; - UE indication of EPC Preferred Network Behaviour; and - Supported Network Behaviour. The UE that wants to use one or more of these functionalities not supported by 5G System, when in CM-IDLE may disable all the related radio capabilities that allow the UE to access 5G System. The triggers to disable and re-enable the 5GS capabilities to access 5G System in this case are left up to UE implementation. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.17.1 |
2,255 | 28.7.8 NAI format for 5G-GUTI | The NAI format of the 5G-GUTI shall have the form username@realm as specified in clause 2.2 of IETF RFC 7542 [126]. The username part of the NAI shall take the following form: tmsi<5G-TMSI>.pt<AMF Pointer>.set<AMF Set Id>.region<AMF Region Id> <5G-TMSI>, <AMF Pointer>, <AMF Set Id> and <AMF Region Id> are the hexadecimal strings of the 5G-TMSI, AMF Pointer, AMF Set ID and AMF Region ID. If there are less than 8 significant digits in <5G-TMSI>, "0" digit(s) shall be inserted at the left side to fill the 8 digits coding. If there are less than 2 significant digits in <AMF Pointer> or <AMF Region Id>, "0" digit(s) shall be inserted at the left side to fill the 2 digits coding of the AMF Pointer or AMF Region Id respectively. If there are less than 3 significant digits in <AMF Set Id>, "0" digit(s) shall be inserted at the left side to fill the 3 digits coding. Example: Assuming 5G-TMSI = 06666666 (hexadecimal), AMF Pointer=12 (hexadecimal), AMF Set = 001 (hexadecimal), AMF Region = 48 (hexadecimal), the username part of the NAI is encoded as: "tmsi06666666.pt12.set001.region48" The NAI for an N5CW device in a PLMN (either HPLMN or VPLMN) with MNC=012 and MCC=345, to which the N5CW device attempts to connect via the trusted non-3GPP access, according to clause 28.7.7 is: "tmsi06666666.pt12.set001.region48@nai.5gc-nn.mnc012.mcc345.3gppnetwork.org" | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 28.7.8 |
2,256 | 5.32.8 ATSSS Rules | As specified in clause 5.32.3, after the establishment of a MA PDU Session, the UE receives a prioritized list of ATSSS rules from the SMF. The structure of an ATSSS rule is specified in Table 5.32.8-1. Table 5.32.8-1: Structure of ATSSS Rule The UE evaluates the ATSSS rules in priority order. Each ATSSS rule contains a Traffic Descriptor (containing one or more components described in Table 5.32.8-1) that determines when the rule is applicable. An ATSSS rule is determined to be applicable when every component in the Traffic Descriptor matches the considered service data flow (SDF). Depending on the type of the MA PDU Session, the Traffic Descriptor may contain the following components (the details of the Traffic Descriptor generation are described in clause 5.32.3): - For IPv4, or IPv6, or IPv4v6 type: Application descriptors and/or IP descriptors. - For Ethernet type: Application descriptors and/or Non-IP descriptors. One ATSSS rule with a "match all" Traffic Descriptor may be provided, which matches all SDFs. When provided, it shall have the least Rule Precedence value, so it shall be the last one evaluated by the UE. NOTE 1: The format of the "match all" Traffic descriptor of an ATSSS rule is defined in stage-3. Each ATSSS rule contains an Access Selection Descriptor that contains the following components: - A Steering Mode, which determines how the traffic of the matching SDF should be distributed across 3GPP and non-3GPP accesses. The following Steering Modes are supported: - Active-Standby: It is used to steer a SDF on one access (the Active access), when this access is available, and to switch the SDF to the available other access (the Standby access), when Active access becomes unavailable. When the Active access becomes available again, the SDF is switched back to this access. If the Standby access is not defined, then the SDF is only allowed on the Active access and cannot be transferred on another access. - Smallest Delay: It is used to steer a SDF to the access that is determined to have the smallest Round-Trip Time (RTT). As defined in clause 5.32.5, measurements may be obtained by the UE and UPF to determine the RTT over 3GPP access and over non-3GPP access. In addition, if one access becomes unavailable, all SDF traffic is switched to the other available access. It can only be used for the Non-GBR SDF. - Load-Balancing: It is used to split a SDF across both accesses if both accesses are available. It contains the percentage of the SDF traffic that should be sent over 3GPP access and over non-3GPP access. Load-Balancing is only applicable to Non-GBR SDF. In addition, if one access becomes unavailable, all SDF traffic is switched to the other available access, as if the percentage of the SDF traffic transported via the available access was 100%. - Priority-based: It is used to steer all the traffic of an SDF to the high priority access, until this access is determined to be congested. In this case, the traffic of the SDF is sent also to the low priority access, i.e. the SDF traffic is split over the two accesses. In addition, when the high priority access becomes unavailable, all SDF traffic is switched to the low priority access. How UE and UPF determine when a congestion occurs on an access is implementation dependent. It can only be used for the Non-GBR SDF. - Redundant (without Threshold Values): It is used to duplicate traffic of an SDF on both accesses if both accesses are available. A Primary Access (either 3GPP access or Non-3GPP access) may be provided to the UE in the ATSSS rules and to the UPF in the N4 rules. If a Primary Access is provided, UE and UPF shall send all data packets of the SDF on the Primary Access and may duplicate data packets of the SDF on the other access. How many and which data packets are duplicated by UE and UPF on the other access is based on implementation. If the Primary Access is not provided to UE and UPF, the UE and UPF shall send all data packets of the SDF on both accesses. It can be used for GBR and Non-GBR SDF. - A Steering Mode Indicator, which indicates that the UE may change the default steering parameters provided in the Steering Mode component and may adjust the traffic steering based on its own decisions. Only one of the following Steering Mode Indicators may be provided: - Autonomous load-balance indicator: This indicator may be provided only when the Steering Mode is Load-Balancing. When provided, the UE may ignore the percentages in the Steering Mode component (i.e. the default percentages provided by the network) and may autonomously determine its own percentages for traffic splitting, in a way that maximizes the aggregated bandwidth in the uplink direction. The UE is expected to determine its own percentages for traffic splitting by performing measurements across the two accesses. The UPF may apply a similar behaviour when the autonomous load-balance indicator is included in an N4 rule. - UE-assistance indicator: This indicator may be provided only when the Steering Mode is Load-Balancing. When provided by the network, it indicates that (a) the UE may decide how to distribute the UL traffic of the matching SDF based on the UE's internal state (e.g. when the UE is in the special internal state, e.g. lower battery level), and that (b) the UE may inform the UPF how it decided to distribute the UL traffic of the matching SDF. In the normal cases, although with this indicator provided, the UE shall distribute the UL traffic as indicated by the network. NOTE 2: Typically, the UE-assistance indicator can be provided for SDFs for which the network has no strong steering requirements. For example, when the network has no strong steering requirements for the default traffic of an MA PDU Session, the network can indicate (i) that this traffic must be steered with Load-Balancing steering mode using 50% - 50% split percentages, and (ii) that the UE is allowed to use other split percentages, such as 0% - 100%, if this is needed by the UE to optimize its operation (e.g. to minimize its battery consumption). - Threshold Values: One or more threshold values may be provided when the Steering Mode is Priority-based or when the Steering Mode is Load-Balancing with fixed split percentages (i.e. without the Autonomous load-balance indicator or UE assistance indicator). One threshold value may be provided when the Steering Mode is Redundant. A threshold value may be either a value for RTT or a value for Packet Loss Rate. The threshold values are applicable to both accesses and are applied by the UE and UPF as follows: - Load-Balancing Steering Mode with fixed split percentages (i.e. without the Autonomous load-balance indicator or UE assistance indicator): When at least one measured parameter (i.e. RTT or Packet Loss Rate) on one access exceeds the provided threshold value, the UE and UPF may stop sending traffic on this access, or may continue sending traffic on this access but should reduce the traffic on this access by an implementation specific amount and shall send the amount of reduced traffic on the other access. When all measured parameters (i.e. RTT and Packet Loss Rate) for both accesses do not exceed the provided threshold values, the UE and UPF shall apply the fixed split percentages. - Priority-based Steering Mode: When one or more threshold values are provided for the Priority-based Steering Mode, these threshold values should be considered by UE and UPF to determine when an access becomes congested. For example, when a measured parameter (i.e. RTT or Packet Loss Rate) on one access exceeds the provided threshold value, the UE and UPF may consider this access as congested and send the traffic also to the low priority access. - Redundant Steering Mode: When the measured Packet Loss Rate exceeds the provided threshold value on both accesses, the UE and UPF shall duplicate the traffic of the SDF on both accesses. When the measured RTT exceeds the provided threshold value on both accesses, the UE and UPF may duplicate the traffic of the SDF on both accesses based on implementation. When the measured parameter (i.e. either RTT or Packet Loss Rate) exceeds the provided threshold value on one access only, the UE and UPF shall send the traffic of the SDF only over the other access. When the measured parameter (i.e. either RTT or Packet Loss Rate) does not exceed the provided threshold value on any access, the UE and UPF shall send the traffic of the SDF only over the Primary Access. The Primary Access (either 3GPP access or Non-3GPP access) may be provided to the UE in the ATSSS rules and to the UPF in the N4 rules. If the Primary Access is not provided to the UE and UPF, UE and UPF shall select a Primary Access based on their own implementation (e.g. using the lowest RTT access or the lowest Packet Loss Rate access). If measurement results on an access are not available for a parameter, it is considered that the measured parameter for this access has not exceeded the provided threshold value. If a threshold value is provided when the Steering Mode is Redundant, the Steering Mode can only be used for Non-GBR SDF. - A Steering Functionality, which identifies whether the MPTCP functionality, or the MPQUIC functionality, or the ATSSS-LL functionality should be used to steer the traffic of the matching SDF. This is used when the UE supports multiple functionalities for ATSSS, as specified in clause 5.32.6 ("Support of Steering Functions"). - A Transport Mode, which identifies the transport mode that should be applied by the MPQUIC functionality for the matching traffic. The transport modes supported by the MPQUIC functionality are defined in clause 5.32.6.2.2.1. NOTE 3: There is no need to update the ATSSS rules when one access becomes unavailable or available. As an example, the following ATSSS rules could be provided to UE: a) "Traffic Descriptor: UDP, DestAddr 1.2.3.4", "Steering Mode: Active-Standby, Active=3GPP, Standby=non-3GPP": - This rule means "steer UDP traffic with destination IP address 1.2.3.4 to the active access (3GPP), if available. If the active access is not available, use the standby access (non-3GPP)". b) "Traffic Descriptor: TCP, DestPort 8080", "Steering Mode: Smallest Delay": - This rule means "steer TCP traffic with destination port 8080 to the access with the smallest delay". The UE needs to measure the RTT over both accesses, in order to determine which access has the smallest delay. c) "Traffic Descriptor: TCP traffic of Application-1", "Steering Mode: Load-Balancing, 3GPP=20%, non-3GPP=80%", "Steering Functionality: MPTCP": - This rule means "send 20% of the TCP traffic of Application-1 to 3GPP access and 80% to non-3GPP access by using the MPTCP functionality". d) "Traffic Descriptor: TCP traffic of Application-1", "Steering Mode: Load-Balancing, 3GPP=20%, non-3GPP=80%, "Threshold Value for Packet Loss Rate: 1%", "Steering Functionality: MPTCP": - This rule means "send 20% of the TCP traffic of Application-1 to 3GPP access and 80% to non-3GPP access as long as the Packet Loss Rate does not exceed 1% on both accesses, by using the MPTCP functionality. If the measured Packet Loss Rate of an access exceeds 1%, then the TCP traffic of Application-1 may be reduced on this access and sent via the other access". e) "Traffic Descriptor: UDP traffic of Application-1", "Steering Mode: Load-Balancing, 3GPP=30%, non-3GPP=70%", "Steering Functionality: MPQUIC", "Transport Mode: Datagram mode 1": - This rule means "send 30% of the UDP traffic of Application-1 to 3GPP access and 70% to non-3GPP access by using the MPQUIC functionality with the Datagram mode 1". f) "Traffic Descriptor: com.example.app0, TCP", "Steering Mode: Redundant", "Steering Functionality: MPTCP": - This rule means "traffic duplication is applied by the MPTCP steering functionality to the TCP traffic of application com.example.app0 and 100% of the traffic is duplicated over both accesses". g) "Traffic Descriptor: com.example.app1, TCP", "Steering Mode: Redundant, Primary Access=3GPP, Threshold Value for Packet Loss Rate: 0.1%", "Steering Functionality: MPTCP": - This rule means "traffic duplication is applied to the TCP traffic of application com.example.app1. If the measured PLR exceeds 0.1% on both accesses, all matched traffic is duplicated on both accesses. If the measured PLR exceeds 0.1% on one access only (either 3GPP or non-3GPP access), all matched traffic is sent over the other access only. If the measured PLR does not exceed 0.1% on any access, all matched traffic is sent over 3GPP access only as this is the Primary Access". h) "Traffic Descriptor: com.example.app2, TCP", "Steering Mode: Redundant, Threshold Value for Packet Loss Rate: 0.1%", "Steering Functionality: MPTCP". - This rule means "traffic duplication is applied to the TCP traffic of application com.example.app2. If the measured PLR exceeds 0.1% on both accesses, all matched traffic is duplicated and transmitted on both accesses. If the measured PLR exceeds 0.1% on one access only (either 3GPP or non-3GPP access), all matched traffic is sent over the other access only. If the measured PLR does not exceed 0.1% on any access, the UE or UPF selects the access based on their own implementation, e.g. the access with lower Packet Loss Rate to transmit all matched traffic". | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.32.8 |
2,257 | 5.8.9.10.2 Initiation | The Relay UE may initiate the procedure when one of the following conditions is met: 1> if the UE is acting as U2N Relay UE: 2> upon Uu RLF as specified in 5.3.10; 2> upon reception of an RRCReconfiguration including the reconfigurationWithSync; 2> upon cell reselection; 2> upon L2 U2N Relay UE's RRC connection failure including RRC connection reject as specified in 5.3.3.5 and 5.3.13.10, and T300 expiry as specified in 5.3.3.7, and RRC resume failure as specified in 5.3.13.5; 1> if the UE is acting as L2 U2U Relay UE: 2> upon detection of PC5 RLF with L2 U2U Remote UE as specified in 5.8.9.3; | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.8.9.10.2 |
2,258 | 13.5 Public Service Identity (PSI) | The public service identity shall take the form of either a SIP URI (see IETF RFC 3261 [26]) or a Tel URI (see IETF RFC 3966 [45]). A public service identity identifies a service, or a specific resource created for a service on an application server. The domain part is pre-defined by the IMS operators and the IMS system provides the flexibility to dynamically create the user part of the PSIs. The PSIs are stored in the HSS either as a distinct PSI or as a wildcarded PSI. A distinct PSI contains the PSI that is used in routing , whilst a wildcarded PSI represents a collection of PSIs. Wildcarded PSIs enable optimisation of the operation and maintenance of the nodes. A wildcarded PSI consists of a delimited regular expression located either in the userinfo portion of the SIP URI or in the telephone-subscriber portion of the Tel URI. The regular expression in the wildcarded PSI shall take the form of Extended Regular Expressions (ERE) as defined in chapter 9 in IEEE 1003.1-2004 Part 1 [60]. The delimiter shall be the exclamation mark character ("!"). If more than two exclamation mark characters are present in the userinfo portion or telephone-subscriber portion of a wildcarded PSI then the outside pair of exclamation mark characters is regarded as the pair of delimiters (i.e. no exclamation mark characters are allowed to be present in the fixed parts of the userinfo portion or telephone-subscriber portion). When stored in the HSS, the wildcarded PSI shall include the delimiter character to indicate the extent of the part of the PSI that is wildcarded. It is used to separate the regular expression from the fixed part of the wildcarded PSI. Example: The following PSI could be stored in the HSS - "sip:chatlist!.*[email protected]". When used on an interface, the exclamation mark characters within a PSI shall not be interpreted as delimiter.. Example: The following PSIs communicated in interface messages to the HSS will match to the wildcarded PSI of "sip:chatlist!.*[email protected]" stored in the HSS: sip:[email protected] sip:[email protected] sip:[email protected] sip:[email protected] sip:[email protected] Note that sip:[email protected] and sip:[email protected] are regarded different specific PSIs, both matching the wildcarded PSI sip:chatlist!.*[email protected]. When used by an application server to identify a specific resource (e.g. a chat session) over Inter Operator Network to Network Interface (II-NNI), the PSI should be a SIP URI without including a port number. NOTE: Based on local configuration policy, a PSI can be routed over Inter Operator Network to Network Interface (II-NNI). Details of this routing are operator specific and out of scope of this specification. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 13.5 |
2,259 | 5.15.8 Configuration of Network Slice availability in a PLMN | A Network Slice may be supported in the whole PLMN or in one or more Tracking Areas of the PLMN. Network Slices may also be available with an NS-AoS not matching deployed Tracking Areas as defined in clause 5.15.18. The availability of a Network Slice refers to the support of the S-NSSAI in the involved NFs. In addition, policies in the NSSF may further restrict from using certain Network Slices in a particular TA, e.g. depending on the HPLMN of the UE. The UE can receive, for a Network Slice where the NS-AoS does not match the whole set of cells in one or more TAs, S-NSSAI location availability information as described in clause 5.15.18. The support of a Network Slice in a TA is established end-to-end using a combination of OAM and signalling among network functions. It is derived by using the S-NSSAIs supported per TA in 5G-AN, the S-NSSAIs supported in the AMF and operator policies per TA in the NSSF. The AMF learns the S-NSSAIs supported per TA by the 5G-AN when the 5G-AN nodes establish or update the N2 connection with the AMF (see TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [34]) and TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [27]). One or all AMF per AMF Set provides and updates the NSSF with the S-NSSAIs support per TA. The 5G-AN learns the S-NSSAIs per PLMN ID the AMFs it connects to support when the 5G-AN nodes establishes the N2 connection with the AMF or when the AMF updates the N2 connection with the 5G-AN (see TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [34] and TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [27]). The NSSF may be configured with operator policies specifying under what conditions the S-NSSAIs can be restricted per TA and per HPLMN of the UE. The per TA restricted S-NSSAIs may be provided to the AMFs of the AMF Sets at setup of the network and whenever changed. The AMF may be configured for the S-NSSAIs it supports with operator policies specifying any restriction per TA and per HPLMN of the UE. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.15.8 |
2,260 | 7.3 UE capability coordination | In (NG)EN-DC and NE-DC, the capabilities of a UE supporting MR-DC are carried by different capability containers. Some MR-DC related capabilities are in the MR-DC container e.g. MR-DC band combinations, while other MR-DC related capabilities are contained in the E-UTRA and NR capability containers e.g. feature sets as described in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [3]. The MR-DC capabilities in the MR-DC container need to be visible to both MN and SN, while the capabilities in the E-UTRA and NR containers only need to be visible to the node of the concerned RAT. In NR-DC, all NR-DC related capabilities are in the NR capability container and are visible to both MN and SN. When retrieving MR-DC related capabilities, the MN shall provide an MR-DC filter that affects the MR-DC related capabilities in MR-DC, E-UTRA and NR capability containers. When using different UE capability enquiry messages to retrieve the different containers, the MN shall employ the same MR-DC filter in all enquiry messages. In the E-UTRA RRC UE capability enquiry, the MR-DC filter is also used for retrieval of NR capabilities i.e. there is in fact one MR-DC/NR filter (while there is a separate filter for E-UTRA capabilities). Furthermore, the MN stores the retrieved capabilities and the corresponding filter, used to retrieve those capabilities, in the core network for later use. For the UE capabilities requiring coordination between E-UTRA and NR (i.e. band combinations, feature sets and the maximum power for FR1 the UE can use in SCG) or between NR MN and NR SN (i.e. band combinations, feature sets and the maximum power for FR1 and FR2), it is up to the MN to decide on how to resolve the dependency between MN and SN configurations. The MN then provides the resulting UE capabilities usable for SCG configuration to the SN, including the list of allowed MR-DC band combinations and feature sets, and the SN indicates the selected band combination and feature set to the MN. When subsequently reconfiguring the SCG, the SN should inform the MN whenever the band combination and/or feature set it selected for the SCG changes (i.e. even if the selection concerns a band combination and feature set that is allowed). As part of an SN initiated SN modification, the SN may also indicate the desired UE capabilities usable for SCG configuration (e.g. a band combination and a feature set) outside those allowed by the MN (i.e. it may re-negotiate the UE capabilities for SCG configuration), and it is up to the MN to make the final decision whether to accept or reject the request. If the MN accepts the request, the MN may provide the resulting UE capabilities e.g. by indicating the allowed band combinations and feature sets. If MN accepts but does not provide resulting UE capabilities, SN assumes the UE capabilities usable for SCG configuration are updated in accordance with the modification it requested. Otherwise, the MN rejects the request by sending X2/Xn refuse message. In EN-DC and MR-DC with 5GC, the MN may provide the UE radio capability ID to the SN. For EN-DC, the SN may retrieve the UE Radio Capability information associated to a UE radio capability ID from the MN. For MR-DC with 5GC, the SN may retrieve the UE radio capability information associated to a UE radio capability ID from the 5GC. For MUSIM operation, when the UE is configured to operate in NR-DC in Network A (as described in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [3]), the MN may indicate the temporary capability restriction to the SN based on the temporary capability restrictions indicated by the UE. | 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 | 7.3 |
2,261 | 5.27.2.3 TSC Assistance Container determination by TSCTSF | The TSCTSF constructs TSC Assistance Container (defined in Table 5.27.2-2) based on information provided (directly or via NEF) by the AF for IP or Ethernet type PDU Sessions, or by the DetNet controller for IP type PDU Sessions. In the case of an AF request, the AF may provide Flow Direction, Burst Arrival Time (optional) at the UE/DS-TT (uplink) or UPF/NW-TT (downlink), Maximum Burst Size, Periodicity, Survival Time (optional), and a Time Domain (optional) to the TSCTSF. If the AF is able to adjust the burst sending time, the AF may in addition provide a BAT Window or the Capability for BAT adaptation to the TSCTSF. Addtionally if the AF is able to adjust the periodicity, the AF may also provide the Periodicity Range along with the Periodicity to the TSCTSF. Based on these parameters, the TSCTSF constructs a TSC Assistance Container and provides it to PCF. If the AF provides to the TSCTSF a Burst Arrival Time or Periodicity without corresponding Time Domain, the TSCTSF sets the Time Domain = "5GS" in the TSC Assistance Container. If the AF is able to adjust the transmission time and periodicity then in addition to above parameters, it may provide a BAT Window (optional) or the capability for BAT adaptation (optional), or Periodicity Range (optional), to the TSCTSF. NOTE: The Maximum Burst Size is signalled separately, i.e. it is not part of the TSC Assistance Container. The AF provides these parameters to the NEF and the NEF forwards these parameters to the TSCTSF. The AF trusted by the operator provides these parameters to the TSCTSF directly. In the case of Deterministic Networking, the TSCTSF constructs the TSC Assistance Container based on information provided by the DetNet controller as defined in clause 6.1.3.23b of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]. The TSCTSF sends the TSC Assistance Container to the PCF as follows: - The TSCTSF uses the UE IP address/DS-TT port MAC address to identify the PCF and N5 association related to the PDU Session of a UE/DS-TT. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.27.2.3 |
2,262 | 4.2.4 Roaming reference architectures | Figure 4.2.4-1 depicts the 5G System roaming architecture with local breakout with service-based interfaces within the Control Plane. Figure 4.2.4-1: Roaming 5G System architecture- local breakout scenario in service-based interface representation NOTE 1: In the LBO architecture. the PCF in the VPLMN may interact with the AF in order to generate PCC Rules for services delivered via the VPLMN, the PCF in the VPLMN uses locally configured policies according to the roaming agreement with the HPLMN operator as input for PCC Rule generation, the PCF in VPLMN has no access to subscriber policy information from the HPLMN. NOTE 2: An SCP can be used for indirect communication between NFs and NF services within the VPLMN, within the HPLMN, or in within both VPLMN and HPLMN. For simplicity, the SCP is not shown in the roaming architecture. NOTE 3: For clarity, the NWDAF(s) with roaming exchange capability (RE-NWDAF) and their connections with other NFs, are not depicted in the service-based architecture diagram. For more information on network data analytics architecture refer to TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [86]. NOTE 4: Depending on the architecture deployed, the Primary or Centralized NSACF at the VPLMN can fetch the maximum number of registered UEs or the maximum number of LBO PDU sessions to be enforced from the HPLMN Primary or Centralized NSACF as described in clause 5.15.11.3.1. Figure 4.2.4-2: Void Figure 4.2.4-3 depicts the 5G System roaming architecture in the case of home routed scenario with service-based interfaces within the Control Plane. Figure 4.2.4-3: Roaming 5G System architecture - home routed scenario in service-based interface representation NOTE 4: An SCP can be used for indirect communication between NFs and NF services within the VPLMN, within the HPLMN, or in within both VPLMN and HPLMN. For simplicity, the SCP is not shown in the roaming architecture. NOTE 5: UPFs in the home routed scenario can be used also to support the IPUPS functionality (see clause 5.8.2.14). NOTE 6: For clarity, the NWDAF(s) with roaming exchange capability (RE-NWDAF) and their connections with other NFs, are not depicted in the service-based architecture diagram. For more information on network data analytics architecture refer to TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [86]. Figure 4.2.4-4 depicts 5G System roaming architecture in the case of local break out scenario using the reference point representation. Figure 4.2.4-4: Roaming 5G System architecture - local breakout scenario in reference point representation NOTE 7: The NRF is not depicted in reference point architecture figures. Refer to Figure 4.2.4-7 for details on NRF and NF interfaces. NOTE 8: For the sake of clarity, SEPPs are not depicted in the roaming reference point architecture figures. NOTE 9: For clarity, the NWDAF(s) with roaming exchange capability (RE-NWDAF) and their connections with other NFs, are not depicted in the reference point architecture figure. For more information on network data analytics architecture refer to TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [86]. The following figure 4.2.4-6 depicts the 5G System roaming architecture in the case of home routed scenario using the reference point representation. Figure 4.2.4-6: Roaming 5G System architecture - Home routed scenario in reference point representation The N38 references point can be between V-SMFs in the same VPLMN, or between V-SMFs in different VPLMNs (to enable inter-PLMN mobility). NOTE 10: For clarity, the NWDAF(s) with roaming exchange capability (RE-NWDAF) and their connections with other NFs, are not depicted in the reference point architecture figure. For more information on network data analytics architecture refer to TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [86]. For the roaming scenarios described above each PLMN implements proxy functionality to secure interconnection and hide topology on the inter-PLMN interfaces. Figure 4.2.4-7: NRF Roaming architecture in reference point representation NOTE 11: For the sake of clarity, SEPPs on both sides of PLMN borders are not depicted in figure 4.2.4-7. Figure 4.2.4-8: Void Operators can deploy UPFs supporting the Inter PLMN UP Security (IPUPS) functionality at the border of their network to protect their network from invalid inter PLMN N9 traffic in home routed roaming scenarios. The UPFs supporting the IPUPS functionality in VPLMN and HPLMN are controlled by the V-SMF and the H-SMF of that PDU Session respectively. A UPF supporting the IPUPS functionality terminates GTP-U N9 tunnels. The SMF can activate the IPUPS functionality together with other UP functionality in the same UPF, or insert a separate UPF for the IPUPS functionality in the UP path (which e.g. may be dedicated to be used for IPUPS functionality). Figure 4.2.4-9 depicts the home routed roaming architecture where a UPF is inserted in the UP path for the IPUPS functionality. Figure 4.2.4-3 depicts the home routed roaming architecture where the two UPFs perform the IPUPS functionality and other UP functionality for the PDU Session. NOTE 12: Operators are not prohibited from deploying the IPUPS functionality as a separate Network Function from the UPF, acting as a transparent proxy which can transparently read N4 and N9 interfaces. However, such deployment option is not specified and needs to take at least into account very long lasting PDU Sessions with infrequent traffic and Inter-PLMN handover. The IPUPS functionality is specified in clause 5.8.2.14 and TS 33.501[ Security architecture and procedures for 5G System ] [29]. Figure 4.2.4-9: Roaming 5G System architecture - home routed roaming scenario in service-based interface representation employing UPF dedicated to IPUPS | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.2.4 |
2,263 | 5.3.4.3.3 Redirection to dedicated frequency band(s) for an S-NSSAI | If a Network Slice, S-NSSAI, is configured to be available only in TAs covering specific dedicated frequency band(s), then there may be a need to redirect the UE to the dedicated frequency band(s) when such S-NSSAI is requested. If the Requested NSSAI contains S-NSSAI(s) that are not available in the UE's current TA, see clause 5.15.8, the AMF itself or by interacting with the NSSF as described in clause 5.15.5.2.1 may determine a Target NSSAI to be used by the NG-RAN, in addition to the information the AMF receives, such as the Allowed NSSAI and the RFSP for the Allowed NSSAI, to attempt to redirect the UE to a cell and TA in another frequency band and TA that supports the S-NSSAIs in the Target NSSAI. The Target NSSAI includes at least one S-NSSAI from the Requested NSSAI not available in the current TA, but available in another TA in different frequency band possibly overlapping with the current TA, and optionally additional S-NSSAIs from the Requested NSSAI that are configured to be available within the same TAs as the S-NSSAIs not available in the current TA. If the serving PLMN supports the subscription-based restrictions to simultaneous registration of network slices (see clause 5.15.12), and if the UE has NSSRG as part of the subscription information received from the HPLMN, the Target NSSAI includes only S-NSSAIs sharing at least one NSSRG. The Target NSSAI may be excluding some of the S-NSSAIs in the Allowed NSSAI and include some of the rejected S-NSSAIs due to lack of support in the TA where the UE is located based on network policies that are in line with customer and operator agreements. The Target NSSAI shall only include S-NSSAIs that can be provided in an Allowed NSSAI, or in an Allowed NSSAI and Partially Allowed NSSAI, for the UE. The Target NSSAI includes at least one Rejected S-NSSAI and may include e.g.: - all or a subset of the Rejected S-NSSAIs for RA, all or a subset of the S-NSSAIs rejected partially in the RA, all or a subset of Partially Allowed NSSAI when none of the S-NSSAIs in the Requested S-NSSAI were available in the TA where the UE is; - all the S-NSSAIs of the Allowed NSSAI, all the S-NSSAIs of the Partially Allowed NSSAI and all or a subset of the Rejected S-NSSAIs for the RA and all or subset of S-NSSAIs rejected partially in the RA; - a subset of the S-NSSAIs in the Allowed NSSAI, a subset of the S-NSSAIs in the Partially Allowed NSSAI and all or a subset of the Rejected S-NSSAIs for the RA and all or subset of S-NSSAIs rejected partially in the RA, if the operator policy is to prefer this Target S-NSSAI to the Allowed NSSAI. The AMF should retrieve an RFSP Index suitable for the Target NSSAI and includes the RFSP Index in the information sent to the NG-RAN. The AMF retrieves the RFSP Index from the PCF or, in case PCF is not deployed the AMF determines the RFSP Index according to local configuration. The RFSP index associated to the Target NSSAI is considered if the NG-RAN succeeds to redirect the UE to a new TA where the Target NSSAI, or some S-NSSAIs of the Target NSSAI are supported, otherwise the RFSP index of the Allowed NSSAI is considered. If the Requested NSSAI contains S-NSSAI(s) which map to S-NSSAI(s) of the HPLMN subject to Network Slice-Specific Authentication and Authorization that are not available in the UE's current TA, the AMF shall proceed with the Network Slice-Specific Authentication and Authorization procedure as described in clause 4.2.9 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. If the AMF determines a new Allowed NSSAI and/or Partially Allowed NSSAI at the end of Network Slice-Specific Authentication and Authorization steps and some S-NSSAI is not available in the UE's current TA, a Target NSSAI and corresponding RFSP index may be determined and provided to NG-RAN during UE Configuration Update procedure as described in clause 4.2.4.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. The NG-RAN shall attempt to find cells of TAs that can support all the S-NSSAIs in the Target S-NSSAIs, and if no such cell of a TA is available the RAN can attempt to select cells of TAs that best match the Target S-NSSAI. The NG-RAN shall attempt to ensure continuity of the PDU Sessions with activated User Plane associated with the S-NSSAIs in the Allowed NSSAI and/or Partially Allowed NSSAI which are in the Target NSSAI. Also, the NG-RAN should attempt to ensure continuity of service for the S-NSSAIs of the Allowed NSSAI and/or Partially Allowed NSSAI also available in the Target NSSAI, before prioritizing cells that are not supporting one or more of the S-NSSAI of the Allowed NSSAI and/or Partially Allowed NSSAI also available in the Target NSSAI. The NG-RAN attempts to determine target cell(s) supporting the Target NSSAI considering the UE Radio Capabilities (i.e. the AMF (if available in the UE context) shall provide the NG-RAN with the current UE Radio Capability Information or the RACS UE Radio Capability ID when a Target NSSAI is provided, if the NG-RAN had not yet received any of them, or, if the AMF cannot provide any of these, the UE Radio Capability Information may be retrieved by the NG-RAN from the UE). Once the target cells are determined, the NG-RAN initiates RRC redirection procedure towards the target cells, or the NG-RAN initiates handover for the UE with active PDU Sessions associated with the S-NSSAIs which are in the Target NSSAI, if possible. After a successful redirection or handover of the UE to a new TA inside the current RA, the UE may request a PDU Session and activate UP resources for a PDU Session for S-NSSAIs of Partially Allowed NSSAI that are supported in the new TA, and the UE may request to register S-NSSAIs rejected partially in the RA that are not rejected in the new TA, as described in clause 5.15.17. After a successful redirection or handover of the UE to a new TA outside the current RA, the UE shall perform a Mobility Registration Update procedure and the S-NSSAIs that the new TA supports can be allowed if the UE requests them. In order to ensure that the UE is redirected to a TA outside the current RA when there are S-NSSAIs Rejected for the RA, thus triggering a Mobility Registration Update procedure enabling the UE to request the S-NSSAI(s) that were rejected for the RA, the AMF shall set the RA so that the RA does not include TAs supporting the S-NSSAIs rejected for the RA included in the Target NSSAI when the AMF provides a Target NSSAI to the RAN. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.3.4.3.3 |
2,264 | A.4 RES* and XRES* derivation function | When deriving RES* from RES, RAND, and serving network name in the UE and when deriving XRES* from XRES, RAND, and the serving network name in the ARPF, the following parameters shall be used to form the input S to the KDF. - FC = 0x6B, - P0 = serving network name, - L0 = length of the serving network name (variable length as specified in 24.501 [35]), - P1 = RAND, - L1 = length of RAND (i.e. 0x00 0x10), - P2 = RES or XRES, - L2 = length RES or XRES (i.e. variable length between 0x00 0x04 and 0x00 0x10). The input key KEY shall be equal to the concatenation CK || IK of CK and IK. The serving network name shall be constructed as specified in clause 6.1.1.4. The (X)RES* is identified with the 128 least significant bits of the output of the KDF. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | A.4 |
2,265 | – NPN-Identity | The IE NPN-Identity includes either a list of CAG-IDs or a list of NIDs per PLMN Identity. Further information regarding how to set the IE is specified in TS 23.003[ Numbering, addressing and identification ] [21]. NPN-Identity information element -- ASN1START -- TAG-NPN-IDENTITY-START NPN-Identity-r16 ::= CHOICE { pni-npn-r16 SEQUENCE { plmn-Identity-r16 PLMN-Identity, cag-IdentityList-r16 SEQUENCE (SIZE (1..maxNPN-r16)) OF CAG-IdentityInfo-r16 }, snpn-r16 SEQUENCE { plmn-Identity-r16 PLMN-Identity, nid-List-r16 SEQUENCE (SIZE (1..maxNPN-r16)) OF NID-r16 } } CAG-IdentityInfo-r16 ::= SEQUENCE { cag-Identity-r16 BIT STRING (SIZE (32)), manualCAGselectionAllowed-r16 ENUMERATED {true} OPTIONAL -- Need R } NID-r16 ::= BIT STRING (SIZE (44)) -- TAG-NPN-IDENTITY-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
2,266 | 13.3 PDN Interworking Model of P-GW for DHCP | A DHCP Client shall be located in the P-GW used for interworking with the IP network as illustrated in Figure 16g. Figure 16g: The protocol stacks for the Sgi IP reference point for DHCP The DHCP client function in P-GW shall be used to allocate IP address(es) to the UE and/or to configure associated parameters via external DHCP servers in PDN(s). As both IPv4 and IPv6 address allocation are supported in EPS, the P-GW shall have both DHCPv4 and DHCPv6 client functions. The procedures where the DHCP client function in the P-GW is used are further described in TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [3], TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [77] and TS 23.402[ Architecture enhancements for non-3GPP accesses ] [78]. The procedures are IPv4 address allocation and IPv4 parameter configuration via an external DHCPv4 server in a PDN; IPv6 Prefix allocation via stateless address autoconfiguration; and IPv6 parameter configuration via stateless DHCPv6. These procedures are detailed in the subclauses below. | 3GPP TS 29.061 | Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) | CT WG3 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 13.3 |
2,267 | 9.3.4 Congestion control | This message is sent by the network to indicate the establishment or termination of flow control on the transmission of USER INFORMATION messages. See table 9.58/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Message type: CONGESTION CONTROL Significance: local (note) Direction: network to mobile station Table 9.58/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : CONGESTION CONTROL message content NOTE: This message has local significance, but may carry information of global significance. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.3.4 |
2,268 | 10.4 FDD with 5G terrestrial broadcast | For all tests in section 10.4 the applicability rules are defined in Table 10.4-1 depending on the capabilities of the UE. The requirements in clause 10.4 are applicable to UEs that support 5G terrestrial broadcast. Table 10.4-1: 5G terrestrial broadcast tests applicability For the requirements defined in this section, the difference between CRS EPRE and the MBSFN RS EPRE should be set to 16dB for subcarrier spacing as 0.37kHz, 7.8 dB for subcarrier spacing as 2.5kHz because the UE demodulation performance might be different when this condition is not met (e.g. in scenarios where power offsets are present, such as scenarios when reserved cells are present). | 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 | 10.4 |
2,269 | 8.15.1.2 Multicast MBS Session Context Establishment | Figure 8.15.1.2-1 illustrates an exemplified interaction of NGAP, E1AP, F1AP and RRC protocol functions for Multicast MBS Session Context Establishment with a UE joining an active multicast session as the first UE joining in its serving gNB. Figure 8.15.1.2-1: Multicast MBS Session Context establishment 0. For a certain multicast MBS session (TMGI), which is currently active, no multicast MBS session context is yet established in the gNB. 1. The UE joins the multicast session. NOTE 1: NAS related details for PDU Session signalling are not shown in Figure 8.15.1.2-1. 2/3. The gNB-CU-CP establishes the multicast bearer context at the gNB-CU-UP. For unicast NG-U transport the GTP DL TEID is retrieved. 4/5. The gNB-CU CP triggers the NGAP Distribution Setup procedure. For unicast NG-U transport, DL GTP TEID is provided to the 5GC. For multicast NG-U transport, multicast address information is retrieved from the 5GC. Multicast session QoS parameters are provided by the 5GC. 5a/5b. The gNB-CU-CP triggers the setup of MRB resources via the E1AP MC Bearer Context Modification procedure. For multicast NG-U transport the 5GC shared NG-U multicast address information is provided to the gNB-CU-UP. Multicast session QoS parameters are provided to the gNB-CU-UP. 6/7. The gNB-CU-CP establishes the Multicast Context at the gNB-DU, providing MRB configuration. It may contain MBS Area Session ID information. 8/9. The gNB-CU-CP retrieves the MRB configuration for the joined UE from the gNB-DU via F1 UE Context Management procedures. NOTE 2: The interactions between the gNB-CU-CP and gNB-CU-UP for UE specific Berarer Context management before and after step 8/9 are not illustrated in this Figure. 10. The gNB-DU triggers the establishment of F1-U resources, which are established either per gNB-DU or per cell or per MBS Area Session ID. 11/12. The gNB-CU-UP side of the F1-U is established by means of the E1AP MC Bearer Context Modification procedure, providing the gNB-DU side F1-U TNL to the gNB-CU-UP, which provides the gNB-CU-UP side F1-U TNL address in return. 13. The gNB-CU-UP side F1-U TNL address is provided to the gNB-DU. 14. In case of NG-U multicast transport, the gNB-CU-UP joins the NG-U multicast group. 15. The gNB successfully terminates the NGAP procedure for establishing the multicast session context. 16. The gNB-CU-CP RRC-configures each UE which has joined the multicast group. 17. The multicast MBS media stream is provided to the UEs. On NG-U, in case of location dependent multicast MBS Sessions, multiple shared NG-U transport tunnels may need to be setup, one per Area Session ID served by the gNB. In case of shared NG-U termination, - the gNB-CU-UP may provide the gNB-CU-CP at E1 setup or configuration update about established shared NG-U terminations, indicated by one or several MBS Session IDs. - at establishment of the MC bearer context in the gNB-CU-UP, the gNB-CU- CP may request the gNB-CU-UP to either apply the available MRB configuration of the shared NG-U termination, or to apply the MRB configuration requested by the gNB-CU-CP. The gNB-CU-UP provides the MRB configuration to the gNB-CU-CP if the MRB configuration requested by the gNB-CU-CP and the available MRB configuration of the shared NG-U termination are different. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 8.15.1.2 |
2,270 | 7.3.2 PDU Session identity | The following network procedures shall apply for handling an unknown, erroneous, or unforeseen PDU session identity received in the header of a 5GSM message (specified as the header of a standard L3 message, see 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [11]): a) If the network receives a PDU SESSION MODIFICATION REQUEST message which includes an unassigned or reserved PDU session identity value, the network shall respond with a PDU SESSION MODIFICATION REJECT message including 5GSM cause #43 "invalid PDU session identity". b) If the network receives PDU SESSION RELEASE REQUEST message which includes an unassigned or reserved PDU session identity value, the network shall respond with a PDU SESSION RELEASE REJECT message including 5GSM cause #43 "invalid PDU session identity". c) Upon receipt of an UL NAS TRANSPORT message, the network takes the following actions: 1) If the Request type IE is set to "initial request" or "initial emergency request" and the message includes a reserved PDU session identity value, the network shall respond with a DL NAS TRANSPORT message with 5GMM cause #90 "payload was not forwarded"; 2) otherwise, if the message includes an unassigned or reserved PDU session identity value, the network shall respond with a DL NAS TRANSPORT message with 5GMM cause #90 "payload was not forwarded". d) If the network receives a 5GSM message other than those listed in items a) through c) above in which the message includes a reserved PDU session identity value or an assigned value that does not match an existing PDU session, the network shall ignore the message. The following UE procedures shall apply for handling an unknown, erroneous, or unforeseen PDU session identity received in the header of a 5GSM message: a) If the UE receives a 5GSM message which includes an unassigned or reserved PDU session identity value, the UE shall ignore the message. b) If the UE receives a 5GSM message which includes a PDU session identity belonging to any PDU session in state PDU SESSION INACTIVE in the UE, the UE shall respond with a 5GSM STATUS message including 5GSM cause #43 "invalid PDU session identity". | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 7.3.2 |
2,271 | 6.8.1.3 R99+ VLR/SGSN | The AKA procedure will depend on the terminal capabilities, as follows: UMTS subscriber with R99+ ME When the user has R99+ ME, the VLR/SGSN shall send the ME a UMTS authentication challenge (i.e. RAND and AUTN) using a quintet that is either: a) retrieved from the local database, b) provided by the HLR/AuC, or c) provided by the previously visited R99+ VLR/SGSN. Note: Originally all quintets are provided by the HLR/AuC. When the ME is capable of the USIM-ME interface, then UMTS AKA is performed and the VLR/SGSN receives the UMTS response RES. UMTS AKA results in the establishment of a UMTS security context; the UMTS cipher/integrity keys CK and IK and the key set identifier KSI are stored in theVLR/SGSN. When the user is attached to a UTRAN, the UMTS cipher/integrity keys are sent to the RNC, where the cipher/integrity algorithms are allocated. When the user is attached to a GSM BSS, UMTS AKA is followed by the derivation of the GSM cipher keys Kc (and Kc128 when needed)from the UMTS cipher/integrity keys. When the user receives service from an MSC/VLR, the derived cipher keys Kc (and Kc128 when needed) are then sent to the BSC (and forwarded to the BTS). When the user receives service from an SGSN, the derived cipher key Kc or Kc128 applied in the SGSN itself. UMTS authentication and key freshness is always provided to UMTS subscribers with R99+ ME independently of the radio access network. When the ME is not capable of the USIM-ME interface, then GSM AKA is performed and the VLR/SGSN receives the GSM response SRES. GSM AKA results in the establishment of a GSM security context; the 64-bit GSM cipher key Kc and the cipher key sequence number CKSN are stored in the VLR/SGSN. The R99+ VLR/SGSN shall reject authentication if SRES is received in response of a UMTS challenge (RAND, AUTN) over an Iu-Interface. The R99+ VLR/SGSN shall accept authentication if a valid SRES is received in response of a UMTS challenge (RAND, AUTN) over A or Gb-Interface. This will happen in case a UICC is inserted in a ME that is not capable of UMTS AKA and is attached to a GSM BSS. In this case the R99+ VLR/SGSN uses function c2 to convert RES (from the quintet) to SRES to verify the received SRES. UMTS subscriber with R98- ME When the user has R98- ME, the R99+ VLR/SGSN sends the ME a GSM authentication challenge using a triplet that is either: a) derived by means of the conversion functions c2 and c3 in the R99+ VLR/SGSN from a quintet that is: i) retrieved from the local database, ii) provided by the HLR/AuC, or iii) provided by the previously visited R99+ VLR/SGSN, or b) provided as a triplet by the previously visited VLR/SGSN. NOTE 1: R99+ VLR/SGSN will always provide quintets for UMTS subscribers. NOTE 2: For a UMTS subscriber, all triplets are derived from quintets, be it in the HLR/AuC or in an VLR/SGSN. GSM AKA results in the establishment of a GSM security context; the 64-bit GSM cipher key Kc and the cipher key sequence number CKSN are stored in the VLR/SGSN. In this case the user is attached to a GSM BSS. When the user receives service from an MSC/VLR, the 64-bit GSM cipher key is sent to the BSC (and forwarded to the BTS). When the user receives service from an SGSN, the derived cipher key Kc is applied in the SGSN itself. UMTS authentication and key freshness cannot be provided to UMTS subscriber with R98- ME. | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | 6.8.1.3 |
2,272 | 4.3.1.1.5 Successful outgoing intra-DeNB handover executions from DeNB cell to RN per handover cause | This measurement provides the number of successful outgoing intra-DeNB handovers from DeNB cell to RN per handover cause; this measurement is only applicable to DeNB. CC. Receipt by the source DeNB of X2AP message UE CONTEXT RELEASE from the RN following a successful handover (see TS 36.423[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 Application Protocol (X2AP) ] [10]), the forwarded X2AP message UE CONTEXT RELEASE for the handover from another RN, eNB or DeNB to the RN is exclusive. Each outgoing intra-DeNB handover from DeNB cell to RN is added to the relevant per handover cause measurement, the possible causes are included in TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [9]. The sum of all supported per cause measurements shall equal the total number of succesful outgoing intra-eNB handovers from DeNB cell to RN. In case only a subset of per cause measurements is supported, a sum subcounter will be provided first. Each measurement is an integer value. The number of measurements is equal to the number of causes supported plus a possible sum value identified by the .sum suffix. HO.IntraDenbOutToRnSucc.Cause where Cause identifies the cause for handover. EUtranCellFDD EUtranCellTDD Valid for packet switched traffic EPS | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.3.1.1.5 |
2,273 | 4.7.7.3 Authentication and ciphering completion by the network | Upon receipt of the AUTHENTICATION AND CIPHERING RESPONSE message, the network stops the timer T3360 and checks the validity of the response (see 3GPP TS 43.020[ Security related network functions ] [13] and 3GPP TS 33.102[ 3G security; Security architecture ] [5a]). For this, it may use the A&C reference number information element within the AUTHENTICATION AND CIPHERING RESPONSE message to determine whether the response is correlating to the last request that was sent. In A/Gb mode, in a UMTS authentication challenge if the MS has indicated support of integrity protection to the network and if the AUTHENTICATION AND CIPHERING REQUEST message authentication, then the network shall check and verify the message authentication code received in the AUTHENTICATION AND CIPHERING RESPONSE message from the MS by using the new integrity key GPRS GSM Kint derived from the new UMTS security context as described in subclause 4.7.7.3b and annex H in 3GPP TS 43.020[ Security related network functions ] [13]. When a successful authentication takes place after a successful verification of the RES and the message authentication code received in the AUTHENTICATION AND CIPHERING RESPONSE message from the MS, the GMM layer in the network shall indicate this successful authentication to the LLC layer. If the check and verification of the message authentication code included in the AUTHENTICATION AND CIPHERING RESPONSE message fails in the network, then the network shall ignore the GMM message. If the AUTHENTICATION AND CIPHERING RESPONSE message is received in the network without a message authentication code then the network shall silently discard the GMM message. In A/Gb mode, in the case of an established GSM security context, the GMM layer shall notify the LLC sublayer if ciphering shall be used or not. Furthermore, if ciphering shall be used, then the GMM layer shall also notify the LLC sublayer which GEA algorithm and GPRS GSM ciphering key that shall be used (see 3GPP TS 44.064[ Mobile Station - Serving GPRS Support Node (MS-SGSN); Logical Link Control (LLC) Layer Specification ] [78a]). In A/Gb mode, in the case of an established UMTS security context, the GMM layer shall notify the LLC sublayer if ciphering shall be used or not. Furthermore, if ciphering shall be used, then the GMM layer shall also notify the LLC sublayer which GEA algorithm and which ciphering key (i.e. GPRS GSM ciphering key or GPRS GSM Kc128) that shall be used (see 3GPP TS 44.064[ Mobile Station - Serving GPRS Support Node (MS-SGSN); Logical Link Control (LLC) Layer Specification ] [78a]). If the network has selected a GEA ciphering algorithm that requires a 128-bit ciphering key, then the ME shall derive a GPRS GSM Kc128 as described in the subclause 4.7.7.3a. In A/Gb mode, if an established UMTS security context context is available in the network, if the MS has indicated support of integrity protection to the network, the GMM layer in the network shall assign the GPRS GSM integrity algorithm and the GPRS GSM Kint integrity key to the LLC layer, after it has received the AUTHENTICATION AND CIPHERING RESPONSE message from the MS (see 3GPP TS 43.020[ Security related network functions ] [13] and 3GPP TS 44.064[ Mobile Station - Serving GPRS Support Node (MS-SGSN); Logical Link Control (LLC) Layer Specification ] [78a]). Upon receipt of the AUTHENTICATION AND CIPHERING FAILURE message, the network stops the timer T3360. In Synch failure case, the core network may renegotiate with the HLR/AuC and provide the MS with new authentication parameters. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.7.7.3 |
2,274 | 15.4.2.1 Intra-system energy saving | The solution builds upon the possibility for the NG-RAN node owning a capacity booster cell to autonomously decide to switch-off such cell to lower energy consumption (inactive state). The decision is typically based on cell load information, consistently with configured information. The switch-off decision may also be taken by O&M. The NG-RAN node may initiate handover actions in order to off-load the cell being switched off and may indicate the reason for handover with an appropriate cause value to support the target node in taking subsequent actions, e.g. when selecting the target cell for subsequent handovers. All neighbour NG-RAN nodes are informed by the NG-RAN node owning the concerned cell about the switch-off actions over the Xn interface, by means of the NG-RAN node Configuration Update procedure. All informed nodes maintain the cell configuration data, e.g., neighbour relationship configuration, also when a certain cell is inactive. If basic coverage is ensured by NG-RAN node cells, NG-RAN node owning non-capacity boosting cells may request a re-activation over the Xn interface if capacity needs in such cells demand to do so. This is achieved via the Cell Activation procedure. During switch off time period of the boost cell, the NG-RAN node may prevent idle mode UEs from camping on this cell and may prevent incoming handovers to the same cell. The NG-RAN node receiving a request should act accordingly. The switch-on decision may also be taken by O&M. All peer NG-RAN nodes are informed by the NG-RAN node owning the concerned cell about the re-activation by an indication on the Xn interface. The solution also builds upon the possibility for the NG-RAN node owning a coverage cell to request neighbouring NG-RAN node(s) owning a capacity booster cell to switch on some SSB beams within the cell which are deactivated. The receiving NG-RAN node should act accordingly. The solution also builds upon the possibility for an NG-RAN node to page certain UEs (e.g., stationary UEs) in RRC_INACTIVE state on a limited set of beams, instead of paging on all the beams within the cell. It is up to the gNB's implementation to select the UEs in RRC_INACTIVE for which paging in limited set of beams applies. If the paging over the limited set of beams fails, the gNB performs subsequent paging by implementation, e.g., by ensuring the same paging message is repeated in all the transmitted SSB beams. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 15.4.2.1 |
2,275 | 6.3.5B Power control for UL-MIMO | For UE supporting UL-MIMO, the power control tolerance applies to the sum of output power at each transmit antenna connector. The power control requirements specified in subclause 6.3.5 apply to UE with two transmit antenna connectors in closed-loop spatial multiplexing scheme. The requirements shall be met with UL-MIMO configurations specified in Table 6.2.2B-2, wherein - The Maximum output power requirements for UL-MIMO are specified in subclause 6.2.2B - The Minimum output power requirements for UL-MIMO are specified in subclause 6.3.2B - The requirements for configured transmitted power for UL-MIMO are specified in subclause 6.2.5B. If UE is configured for transmission on single-antenna port, the requirements in subclause 6.3.5 apply. | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.3.5B |
2,276 | 5.6.1.4 Setting band combinations, feature set combinations and feature sets supported by the UE | The UE invokes the procedures in this clause if the NR or E-UTRA network requests UE capabilities for nr, eutra-nr or eutra. This procedure is invoked once per requested rat-Type (see clause 5.6.1.3 for capability enquiry by the NR network; see TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10], clause 5.6.3.3 for capability enquiry by the E-UTRA network). The UE shall ensure that the feature set IDs are consistent across feature sets, feature set combinations and band combinations in all three UE capability containers that the network queries with the same fields with the same values, i.e. UE-CapabilityRequestFilterNR, UE-CapabilityRequestFilterCommon and fields in UECapabilityEnquiry message (i.e. requestedFreqBandsNR-MRDC, requestedCapabilityNR, eutra-nr-only flag, and requestedCapabilityCommon) as defined in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] , where applicable. NOTE 1: Capability enquiry without frequencyBandListFilter is not supported. NOTE 2: In (NG)EN-DC, the gNB needs the capabilities for RAT types nr and eutra-nr and it uses the featureSets in the UE-NR-Capability together with the featureSetCombinations in the UE-MRDC-Capability to determine the NR UE capabilities for the supported MRDC band combinations. Similarly, the eNB needs the capabilities for RAT types eutra and eutra-nr and it uses the featureSetsEUTRA in the UE-EUTRA-Capability together with the featureSetCombinations in the UE-MRDC-Capability to determine the E-UTRA UE capabilities for the supported MRDC band combinations. Hence, the IDs used in the featureSets must match the IDs referred to in featureSetCombinations across all three containers. The requirement on consistency implies that there are no undefined feature sets and feature set combinations. NOTE 3: If the UE cannot include all feature sets and feature set combinations due to message size or list size constraints, it is up to UE implementation which feature sets and feature set combinations it prioritizes. The UE shall: 1> if the UE is an eRedCap UE, the UE may in the remainder of this procedure assume frequencyBandListFilter to be the filter containing all the supported bands of the UE; 1> compile a list of "candidate band combinations" according to the filter criteria in capabilityRequestFilterCommon (if included), only consisting of bands included in frequencyBandListFilter, and prioritized in the order of frequencyBandListFilter (i.e. first include band combinations containing the first-listed band, then include remaining band combinations containing the second-listed band, and so on), where for each band in the band combination, the parameters of the band do not exceed maxBandwidthRequestedDL, maxBandwidthRequestedUL, maxCarriersRequestedDL, maxCarriersRequestedUL, ca-BandwidthClassDL-EUTRA or ca-BandwidthClassUL-EUTRA, whichever are received; 1> for each band combination included in the list of "candidate band combinations": 2> if the network (E-UTRA) included the eutra-nr-only field, or 2> if the requested rat-Type is eutra: 3> remove the NR-only band combination from the list of "candidate band combinations"; NOTE 4: The (E-UTRA) network may request capabilities for nr but indicate with the eutra-nr-only flag that the UE shall not include any NR band combinations in the UE-NR-Capability. In this case the procedural text above removes all NR-only band combinations from the candidate list and thereby also avoids inclusion of corresponding feature set combinations and feature sets below. 2> if it is regarded as a fallback band combination with the same capabilities of another band combination included in the list of "candidate band combinations", and 2> if this fallback band combination is generated by releasing at least one SCell or uplink configuration of SCell or SUL according to TS 38.306[ NR; User Equipment (UE) radio access capabilities ] [26]: 3> remove the band combination from the list of "candidate band combinations"; NOTE 5: Even if the network requests (only) capabilities for nr, it may include E-UTRA band numbers in the frequencyBandListFilter to ensure that the UE includes all necessary feature sets needed for subsequently requested eutra-nr capabilities. At this point of the procedure the list of "candidate band combinations" contains all NR- and/or E-UTRA-NR band combinations that match the filter (frequencyBandListFilter) provided by the NW and that match the eutra-nr-only flag (if RAT-Type nr is requested by E-UTRA). In the following, this candidate list is used to derive the band combinations, feature set combinations and feature sets to be reported in the requested capability container. 1> if the requested rat-Type is nr: 2> include into supportedBandCombinationList as many NR-only band combinations as possible from the list of "candidate band combinations", starting from the first entry; 3> if srs-SwitchingTimeRequest is received: 4> if SRS carrier switching is supported; 5> include srs-SwitchingTimesListNR and srs-SwitchingAffectedBandsListNR for each band combination; 4> set srs-SwitchingTimeRequested to true; 2> include, into featureSetCombinations, the feature set combinations referenced from the supported band combinations as included in supportedBandCombinationList according to the previous; 2> compile a list of "candidate feature set combinations" referenced from the list of "candidate band combinations" excluding entries (rows in feature set combinations) with same or lower capabilities; 2> if uplinkTxSwitchRequest is received: 3> include into supportedBandCombinationList-UplinkTxSwitch as many NR-only band combinations that supported UL TX switching as possible from the list of "candidate band combinations", starting from the first entry; 4> if srs-SwitchingTimeRequest is received: 5> if SRS carrier switching is supported; 6> include srs-SwitchingTimesListNR and srs-SwitchingAffectedBandsListNR for each band combination; 5> set srs-SwitchingTimeRequested to true; 3> include, into featureSetCombinations, the feature set combinations referenced from the supported band combinations as included in supportedBandCombinationList-UplinkTxSwitch according to the previous; NOTE 6: This list of "candidate feature set combinations" contains the feature set combinations used for NR-only as well as E-UTRA-NR band combinations. It is used to derive a list of NR feature sets referred to from the feature set combinations in the UE-NR-Capability and from the feature set combinations in a UE-MRDC-Capability container. 2> if sidelinkRequest is received: 3> for a sidelink band combination the UE included in supportedBandCombinationListSidelinkEUTRA-NR, supportedBandCombinationListSL-RelayDiscovery, supportedBandCombinationListSL-U2U-RelayDiscovery or supportedBandCombinationListSL-NonRelayDiscovery: 4> if the UE supports partial sensing for a band of the sidelink band combination, include the partial sensing capabilities for the band using the sl-TransmissionMode2-PartialSensing-r17; 3> set sidelinkRequested to true; 2> include into featureSets the feature sets referenced from the "candidate feature set combinations" and may exclude the feature sets with the parameters that exceed any of maxBandwidthRequestedDL, maxBandwidthRequestedUL, maxCarriersRequestedDL or maxCarriersRequestedUL, whichever are received; 1> else, if the requested rat-Type is eutra-nr: 2> include into supportedBandCombinationList and/or supportedBandCombinationListNEDC-Only as many E-UTRA-NR band combinations as possible from the list of "candidate band combinations", starting from the first entry; 3> if srs-SwitchingTimeRequest is received: 4> if SRS carrier switching is supported; 5> include srs-SwitchingTimesListNR, srs-SwitchingTimesListEUTRA and srs-SwitchingAffectedBandsListNR for each band combination; 4> set srs-SwitchingTimeRequested to true; 2> include, into featureSetCombinations, the feature set combinations referenced from the supported band combinations as included in supportedBandCombinationList according to the previous; 2> if uplinkTxSwitchRequest is received: 3> include into supportedBandCombinationList-UplinkTxSwitch as many E-UTRA-NR band combinations that supported UL TX switching as possible from the list of "candidate band combinations", starting from the first entry; 4> if srs-SwitchingTimeRequest is received: 5> if SRS carrier switching is supported; 6> include srs-SwitchingTimesListNR, srs-SwitchingTimesListEUTRA and srs-SwitchingAffectedBandsListNR for each band combination; 5> set srs-SwitchingTimeRequested to true; 3> include, into featureSetCombinations, the feature set combinations referenced from the supported band combinations as included in supportedBandCombinationList-UplinkTxSwitch according to the previous; 1> else (if the requested rat-Type is eutra): 2> compile a list of "candidate feature set combinations" referenced from the list of "candidate band combinations" excluding entries (rows in feature set combinations) with same or lower capabilities; NOTE 7: This list of "candidate feature set combinations" contains the feature set combinations used for E-UTRA-NR band combinations. It is used to derive a list of E-UTRA feature sets referred to from the feature set combinations in a UE-MRDC-Capability container. 2> include into featureSetsEUTRA (in the UE-EUTRA-Capability) the feature sets referenced from the "candidate feature set combinations" and may exclude the feature sets with the parameters that exceed ca-BandwidthClassDL-EUTRA or ca-BandwidthClassUL-EUTRA, whichever are received; 1> if the UE is an eRedCap UE and the UE assumes frequencyBandListFilter to be the filter containing all the supported bands of the UE: 2> include all the supported bands of the UE in the field appliedFreqBandListFilter; 1> else: 2> include the received frequencyBandListFilter in the field appliedFreqBandListFilter of the requested UE capability, except if the requested rat-Type is nr and the network included the eutra-nr-only field; 1> if the network included ue-CapabilityEnquiryExt: 2> include the received ue-CapabilityEnquiryExt in the field receivedFilters; | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.6.1.4 |
2,277 | 5.3.7.2 Initiation | The UE initiates the procedure when one of the following conditions is met: 1> upon detecting radio link failure of the MCG and t316 is not configured, in accordance with 5.3.10; or 1> upon detecting radio link failure of the MCG while SCG transmission is suspended, in accordance with 5.3.10; or 1> upon detecting radio link failure of the MCG while PSCell change or PSCell addition is ongoing, in accordance with 5.3.10; or 1> upon detecting radio link failure of the MCG while the SCG is deactivated, in accordance with 5.3.10; or 1> upon re-configuration with sync failure of the MCG, in accordance with clause 5.3.5.8.3; or 1> upon mobility from NR failure, in accordance with clause 5.4.3.5; or 1> upon integrity check failure indication from lower layers concerning SRB1 or SRB2, except if the integrity check failure is detected on the RRCReestablishment message; or 1> upon an RRC connection reconfiguration failure, in accordance with clause 5.3.5.8.2; or 1> upon detecting radio link failure for the SCG while MCG transmission is suspended, in accordance with clause 5.3.10.3 in NR-DC or in accordance with TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10] clause 5.3.11.3 in NE-DC; or 1> upon reconfiguration with sync failure of the SCG while MCG transmission is suspended in accordance with clause 5.3.5.8.3; or 1> upon SCG change failure while MCG transmission is suspended in accordance with TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10] clause 5.3.5.7a; or 1> upon SCG configuration failure while MCG transmission is suspended in accordance with clause 5.3.5.8.2 in NR-DC or in accordance with TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10] clause 5.3.5.5 in NE-DC; or 1> upon integrity check failure indication from SCG lower layers concerning SRB3 while MCG is suspended; or 1> upon T316 expiry, in accordance with clause 5.7.3b.5; or 1> upon detecting sidelink radio link failure by L2 U2N Remote UE in RRC_CONNECTED which is not configured with MP, in accordance with clause 5.8.9.3; or 1> upon reception of NotificationMessageSidelink including indicationType by L2 U2N Remote UE in RRC_CONNECTED which is not configured with MP, in accordance with clause 5.8.9.10; or 1> upon PC5 unicast link release for the serving L2 U2N Relay UE indicated by upper layer at L2 U2N Remote UE in RRC_CONNECTED which is not configured with MP while T301 is not running; or 1> if MP is configured, upon detecting radio link failure of the MCG (i.e. direct path) in accordance with clause 5.3.10 while the transmission of indirect path is suspended as specified in 5.3.5.17; or 1> if MP is configured, upon detecting sidelink radio link failure of SL indirect path by L2 U2N Remote UE, in accordance with clause 5.8.9.3, while MCG transmission (i.e. direct path) is suspended as specified in clause 5.7.3b; or 1> if MP is configured, upon reception of NotificationMessageSidelink including indicationType in accordance with clause 5.8.9.10, while MCG transmission (i.e. direct path) is suspended as specified in clause 5.7.3b; or 1> if MP is configured, upon PC5 unicast link release indicated by upper layer at L2 U2N Remote UE, while MCG transmission (i.e. direct path) is suspended as specified in clause 5.7.3b; or 1> if MP is configured, upon detecting the failure of N3C indirect path by N3C remote UE in accordance with clause 5.7.3c, while MCG transmission (i.e. direct path) is suspended. NOTE 0: It is up to UE implementation whether to initiate the procedure while T346g is running. Upon initiation of the procedure, the UE shall: 1> stop timer T310, if running; 1> stop timer T312, if running; 1> stop timer T304, if running; 1> start timer T311; 1> stop timer T316, if running; 1> if UE is not configured with attemptCondReconfig; and 1> if UE is not configured with attemptLTM-Switch: 2> reset MAC; 2> release spCellConfig, if configured; 2> suspend all RBs, and BH RLC channels for IAB-MT, and Uu Relay RLC channels for L2 U2N Relay UE, except SRB0 and broadcast MRBs; 2> release the MCG SCell(s), if configured; 2> if MR-DC is configured: 3> perform MR-DC release, as specified in clause 5.3.5.10; 2> perform the LTM configuration release procedure for the MCG and the SCG as specified in clause 5.3.5.18.7; 2> release delayBudgetReportingConfig, if configured and stop timer T342, if running; 2> release overheatingAssistanceConfig, if configured and stop timer T345, if running; 2> release idc-AssistanceConfig, if configured; 2> release btNameList, if configured; 2> release wlanNameList, if configured; 2> release sensorNameList, if configured; 2> release drx-PreferenceConfig for the MCG, if configured and stop timer T346a associated with the MCG, if running; 2> release maxBW-PreferenceConfig for the MCG, if configured and stop timer T346b associated with the MCG, if running; 2> release maxCC-PreferenceConfig for the MCG, if configured and stop timer T346c associated with the MCG, if running; 2> release maxMIMO-LayerPreferenceConfig for the MCG, if configured and stop timer T346d associated with the MCG, if running; 2> release minSchedulingOffsetPreferenceConfig for the MCG, if configured stop timer T346e associated with the MCG, if running; 2> release rlm-RelaxationReportingConfig for the MCG, if configured and stop timer T346j associated with the MCG, if running; 2> release bfd-RelaxationReportingConfig for the MCG, if configured and stop timer T346k associated with the MCG, if running; 2> release releasePreferenceConfig, if configured stop timer T346f, if running; 2> release onDemandSIB-Request if configured, and stop timer T350, if running; 2> release referenceTimePreferenceReporting, if configured; 2> release sl-AssistanceConfigNR, if configured; 2> release obtainCommonLocation, if configured; 2> release musim-GapAssistanceConfig, if configured and stop timer T346h, if running; 2> release musim-GapPriorityAssistanceConfig, if configured; 2> release musim-LeaveAssistanceConfig, if configured; 2> release musim-CapabilityRestrictionConfig, if configured and stop timer T346n, if running; 2> release ul-GapFR2-PreferenceConfig, if configured; 2> release scg-DeactivationPreferenceConfig, if configured, and stop timer T346i, if running; 2> release propDelayDiffReportConfig, if configured; 2> release rrm-MeasRelaxationReportingConfig, if configured; 2> release maxBW-PreferenceConfigFR2-2, if configured; 2> release maxMIMO-LayerPreferenceConfigFR2-2, if configured; 2> release minSchedulingOffsetPreferenceConfigExt, if configured; 2> release multiRx-PreferenceReportingConfigFR2, if configured, and stop timer T440, if running; 2> release uav-FlightPathAvailabilityConfig, if configured; 2> release ul-TrafficInfoReportingConfig, if configured, and stop all instances of timer T346x, if running; 1> release successHO-Config, if configured; 1> release successPSCell-Config configured by the PCell, if configured; 1> release successPSCell-Config configured by the PSCell, if configured; 1> if any DAPS bearer is configured: 2> reset the source MAC and release the source MAC configuration; 2> for each DAPS bearer: 3> release the RLC entity or entities as specified in TS 38.322[ NR; Radio Link Control (RLC) protocol specification ] [4], clause 5.1.3, and the associated logical channel for the source SpCell; 3> reconfigure the PDCP entity to release DAPS as specified in TS 38.323[ NR; Packet Data Convergence Protocol (PDCP) specification ] [5]; 2> for each SRB: 3> release the PDCP entity for the source SpCell; 3> release the RLC entity as specified in TS 38.322[ NR; Radio Link Control (RLC) protocol specification ] [4], clause 5.1.3, and the associated logical channel for the source SpCell; 2> release the physical channel configuration for the source SpCell; 2> discard the keys used in the source SpCell (the KgNB key, the KRRCenc key, the KRRCint key, the KUPint key and the KUPenc key), if any; 1> release sl-L2RelayUE-Config, if configured; 1> release sl-L2RemoteUE-Config, if configured; 1> release the SRAP entity, if configured; 1> release NCR-FwdConfig, if configured; 1> if the UE is NCR-MT: 2> indicate to NCR-Fwd to cease forwarding; 1> if SL indirect path is configured: 2> release cell identity and relay UE ID configured in sl-IndirectPathAddChange; 2> indicate upper layers to trigger PC5 unicast link release of the SL indirect path; 1> if N3C indirect path is configured: 2> release n3c-IndirectPathAddChange; 2> consider the non-3GPP connection is not used; 1> if the UE is acting as a N3C relay UE: 2> release n3c-IndirectPathConfigRelay; 2> consider the non-3GPP connection is not used; 1> if the UE is acting as L2 U2N Remote UE and MP via L2 U2N Relay UE is not configured: 2> if the PC5-RRC connection with the U2N Relay UE is determined to be released: 3> indicate upper layers to trigger PC5 unicast link release; 3> perform either cell selection in accordance with the cell selection process as specified in TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [20], or relay selection as specified in clause 5.8.15.3, or both; 2> else (i.e., maintain the PC5 RRC connection): 3> consider the connected L2 U2N Relay UE as suitable and perform actions as specified in clause 5.3.7.3a; NOTE 1: It is up to Remote UE implementation whether to release or keep the current PC5 unicast link. 1> else: 2> if the UE is capable of L2 U2N Remote UE: 3> perform either cell selection as specified in TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [20], or relay selection as specified in clause 5.8.15.3, or both; 2> else: 3> perform cell selection in accordance with the cell selection process as specified in TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [20]. NOTE 2: For L2 U2N Remote UE, if both a suitable cell and a suitable relay are available, the UE can select either one based on its implementation. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.7.2 |
2,278 | 6.2.3 MAC payload for Random Access Response | The MAC RAR is of fixed size and consists of the following fields: - R: Reserved bit, set to "0". For a BL UE or a UE in CE, this bit is set to "1" to indicate that an UL Grant in Random Access Response is for EDT; - Timing Advance Command: The Timing Advance Command field indicates the index value TA (0, 1, 2… 1282) used to control the amount of timing adjustment that the MAC entity has to apply (see clause 4.2.3 of TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [2]), except for NB-IoT UEs using preamble format 2, where the Timing Advance Command field indicates the index value TA (0, 1, 2… 1536). The size of the Timing Advance Command field is 11 bits; - UL Grant: The Uplink Grant field indicates the resources to be used on the uplink (see clause 6.2 of TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [2], or for NB-IoT UEs, see clause 16.3.3 of TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [2]). The size of the UL Grant field is 20 bits, except for NB-IoT UEs, where the size of UL grant field is 15 bits, and except for BL UEs and UEs in enhanced coverage level 2 or 3, where the size of the UL grant field is 12 bits. - ER: Extended RAPID bits, indicating the two least significant bits of extended RAPID used when PRACH preamble format 2 is transmitted. - Temporary C-RNTI: The Temporary C-RNTI field indicates the temporary identity that is used by the MAC entity during Random Access. The size of the Temporary C-RNTI field is 16 bits. The MAC RAR is octet aligned. | 3GPP TS 36.321 | Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification | RAN2 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.2.3 |
2,279 | – UL-DCCH-Message | The UL-DCCH-Message class is the set of RRC messages that may be sent from the UE to the network on the uplink DCCH logical channel. -- ASN1START -- TAG-UL-DCCH-MESSAGE-START UL-DCCH-Message ::= SEQUENCE { message UL-DCCH-MessageType } UL-DCCH-MessageType ::= CHOICE { c1 CHOICE { measurementReport MeasurementReport, rrcReconfigurationComplete RRCReconfigurationComplete, rrcSetupComplete RRCSetupComplete, rrcReestablishmentComplete RRCReestablishmentComplete, rrcResumeComplete RRCResumeComplete, securityModeComplete SecurityModeComplete, securityModeFailure SecurityModeFailure, ulInformationTransfer ULInformationTransfer, locationMeasurementIndication LocationMeasurementIndication, ueCapabilityInformation UECapabilityInformation, counterCheckResponse CounterCheckResponse, ueAssistanceInformation UEAssistanceInformation, failureInformation FailureInformation, ulInformationTransferMRDC ULInformationTransferMRDC, scgFailureInformation SCGFailureInformation, scgFailureInformationEUTRA SCGFailureInformationEUTRA }, messageClassExtension CHOICE { c2 CHOICE { ulDedicatedMessageSegment-r16 ULDedicatedMessageSegment-r16, dedicatedSIBRequest-r16 DedicatedSIBRequest-r16, mcgFailureInformation-r16 MCGFailureInformation-r16, ueInformationResponse-r16 UEInformationResponse-r16, sidelinkUEInformationNR-r16 SidelinkUEInformationNR-r16, ulInformationTransferIRAT-r16 ULInformationTransferIRAT-r16, iabOtherInformation-r16 IABOtherInformation-r16, mbsInterestIndication-r17 MBSInterestIndication-r17, uePositioningAssistanceInfo-r17 UEPositioningAssistanceInfo-r17, measurementReportAppLayer-r17 MeasurementReportAppLayer-r17, indirectPathFailureInformation-r18 IndirectPathFailureInformation-r18, spare5 NULL, spare4 NULL, spare3 NULL, spare2 NULL, spare1 NULL }, messageClassExtensionFuture-r16 SEQUENCE {} } } -- TAG-UL-DCCH-MESSAGE-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
2,280 | 5.2.6.33.3 Nnef_AF_request_for_QoS_Notify service operation | Service operation name: Nnef_AF_request_for_QoS Notify Description: NEF reports the QoS Flow level event(s) to the consumer. Inputs, Required: Reports of the events as defined 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: When the event report is for QoS Monitoring, includes Packet delay for UL, DL, or round trip of the single UP path or two UP paths in the case of redundant transmission, as defined in clause 5.33.3.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. Outputs, Required: None. Output (optional): None. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.6.33.3 |
2,281 | 5.4.1.2.3B Procedures related to EAP methods used for primary authentication of an N5GC device | 5.4.1.2.3B.1 General This subclause applies when an EAP method: a) supporting mutual authentication; and b) other than EAP-AKA', is used for primary authentication of an N5GC device, when an W-AGF supports acting on behalf of the N5GC device, the AMF supports serving the W-AGF acting on behalf of the N5GC device and the AUSF supports authentication of the N5GC device. EAP-TLS is an example of such EAP method. NOTE 1: Neither the N5GC device nor the AUSF derive any 5G related keys during or after the primary authentication. The AUSF supporting authentication of the N5GC device shall support acting as EAP server of at least one such EAP method as specified in annex O of 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]. NOTE 2: The N5GC device supports acting as EAP peer of at least one such EAP method as specified in annex O of 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24], which is also supported by the AUSF. The W-AGF acting on behalf of the N5GC device provides to the N5GC device an EAP-request message, an EAP-success message or an EAP-failure message received from the network according to subclause 5.4.1.2.1 and sends to the network according to subclause 5.4.1.2.1 an EAP-response provided by the N5GC device. The N5GC device can inform the W-AGF acting on behalf of the N5GC device that the N5GC device fails to authenticate the network. Details of communication between the N5GC device and the W-AGF acting on behalf of the N5GC device are out of scope of this specification. When initiating an EAP based primary authentication and key agreement procedure using such EAP method, the network shall select an ngKSI value. The network shall send the selected ngKSI value to the W-AGF acting on behalf of the N5GC device along with each EAP message. The network shall send the ABBA value as described in subclause 9.11.3.10 to the W-AGF acting on behalf of the N5GC device along with the EAP-request message and EAP-success message. The W-AGF acting on behalf of the N5GC device shall not forward the ngKSI value or the ABBA value to the N5GC device. NOTE 3: The network provides the ngKSI value and the ABBA value since the ngKSI IE and the ABBA IE are mandatory IEs in AUTHENTICATION REQUEST message. The W-AGF acting on behalf of the N5GC device does not use the ngKSI value or the ABBA value provided by the network. If the N5GC device fails to authenticate the network, the W-AGF acting on behalf of the N5GC device shall start timer T3520 when the AUTHENTICATION RESPONSE message containing the EAP-response message is sent. Furthermore, the W-AGF acting on behalf of the N5GC device shall stop any of the retransmission timers that are running (e.g. T3510, T3517 or T3521). Upon receiving an AUTHENTICATION REQUEST message with the EAP message IE containing an EAP-request message from the network, the W-AGF acting on behalf of the N5GC device shall stop timer T3520, if running, and then provides the EAP-request message to the N5GC device as normally. If the network fails to authenticate the N5GC device, the network handling depends upon the type of identity used by the W-AGF acting on behalf of the N5GC device in the initial NAS message, that is: a) if the 5G-GUTI was used; or b) if the SUCI was used. If the 5G-GUTI was used, the network should transport the EAP-failure message in the AUTHENTICATION RESULT message of the EAP result message transport procedure, initiate an identification procedure to retrieve SUCI from the W-AGF acting on behalf of the N5GC device and restart the EAP based primary authentication and key agreement procedure with the received SUCI. If the SUCI was used for identification in the initial NAS message or in a restarted EAP based primary authentication and key agreement procedure, or the network decides not to initiate the identification procedure to retrieve SUCI from the W-AGF acting on behalf of the N5GC device after an unsuccessful EAP based primary authentication and key agreement procedure, the network should transport the EAP-failure message in an AUTHENTICATION REJECT message of the EAP result message transport procedure. If the EAP-failure message is received in an AUTHENTICATION REJECT message, the W-AGF acting on behalf of the N5GC device shall start timer T3247 with a random value uniformly drawn from the range between 30 minutes and 60 minutes, if the timer is not running (see subclause 5.3.20). Additionally, the W-AGF acting on behalf of the N5GC device shall: a) if the counter for "USIM considered invalid for 5GS services over non-3GPP access" events has a value less than a W-AGF implementation-specific maximum value, proceed as specified in list item 1)-b) of subclause 5.3.20.2 for the case that the 5GMM cause value received is #3; or b) otherwise, set the update status to 5U3 ROAMING NOT ALLOWED, delete the stored 5G-GUTI, TAI list, last visited registered TAI and ngKSI. The USIM shall be considered invalid for 5GS services via non-3GPP access until switching off or the UICC containing the USIM is removed. If the AUTHENTICATION REJECT message is received by the W-AGF acting on behalf of the N5GC device, the W-AGF acting on behalf of the N5GC device shall abort any 5GMM signalling procedure, stop any of the timers T3510, T3517, T3519 or T3521 (if they were running), enter state 5GMM-DEREGISTERED and delete any stored SUCI. Upon receiving an EAP-success message, the W-AGF acting on behalf of the N5GC device shall consider the procedure complete. Upon receiving an EAP-failure message, the W-AGF acting on behalf of the N5GC device shall consider the procedure complete. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.4.1.2.3B |
2,282 | 9.2.5a CM service prompt $(CCBS)$ | A mobile station that does not support the "Network initiated MO call" option shall treat this message as a message with message type not defined for the PD. This message is sent by the network to the mobile station to request the mobile to establish a service for the specified CM protocol using the specified SAPI, e.g. circuit switched connection establishment on SAPI 0, supplementary services activation on SAPI 0, or short message transfer on SAPI 3. See Table 9.2.7/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Message type: CM SERVICE PROMPT Significance: dual Direction: network to mobile station Table 9.2.7/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : CM SERVICE PROMPT message content | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.2.5a |
2,283 | 4.15.6.9 Procedures for AF-triggered dynamically changing access and mobility management policies 4.15.6.9.1 General | Access and mobility management policies may be modified due to several inputs including the AF as described in clause 4.16.2. Clause 4.15.6.9 describes the procedures for triggering such modifications in scenarios belonging to "case B" of clause 4.16.2.0 that are initiated by the AF. The following cases can be distinguished: - AF requests targeting an individual UE (identified by its SUPI or GPSI) without conditions related to the application traffic; these requests are routed (by the AF or by the NEF) to the PCF for the UE as described in clause 6.2.1.6 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20], This case is described in clause 4.15.6.9.2. - AF requests targeting an individual UE (identified by its GPSI), a group of UEs (identified by an Internal Group Identifier or an External Group Identifier), any UE accessing a combination of DNN and S-NSSAI, or any UE, or any inbound roaming UEs identified by their home PLMN ID(s) using an application identified by an External Application Identifier. For such requests the AF shall contact the NEF and the NEF stores the AF request information in the UDR. The PCF(s) receive a corresponding notification if they had subscribed to the creation / modification / deletion of the AF request information corresponding to UDR Data Keys / Data Sub-Keys. The AF is not aware if the target UEs are with or without an already established AM Policy Association and with or without ongoing PDU Sessions. This case is described in clause 4.15.6.9.3. NOTE: "any UE" refers to the UEs within the PLMN of the NEF. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.15.6.9 |
2,284 | 4.3.1.2 Charging Data Function | The Charging Data Function (CDF) receives charging events from the CTF via the Rf reference point. It then uses the information contained in the charging events to construct CDRs. This procedure is characterised by the following conditions: - CDRs may be constructed from single charging events, i.e. a 1:1 relation between event and CDR. - CDRs may be constructed from a set of several charging events, i.e. a n:1 relation between event and CDR. - Each charging event is used for exactly one CDR, i.e. a 1:n relation between event and CDR (with n>1) is not possible. - Multiple charging events that are used to create a single CDR may not necessarily be of the same type. - There is no requirement or assumption of any synchronisation between the reception of the charging event(s) and the creation of the resulting CDR. However, the CDF shall be capable of receiving and processing charging events and generating the resulting CDR in near real-time. - The relationship between CDF and CTF may be 1:1 (integrated CDF) or 1:n (separated CDF) (refer to clause 4.5 for possible physical configurations of the logical charging functions). This includes the possibility of NEs of different types feeding charging events into the same CDF. - All charging events used to build a CDR must originate from the same NE, i.e. there is no cross-NE or cross-NE-type correlation of charging events in the CDF. The results of the CDF tasks are CDRs with a well-defined content and format. The content and format of these CDRs are specified per domain / subsystem / service in the related middle tier TS (e.g. TS 32.250[ Telecommunication management; Charging management; Circuit Switched (CS) domain charging ] [10] for the CS domain and TS 32.251[ Telecommunication management;Charging management;Packet Switched (PS) domain charging ] [11] for the PS domain, etc,). | 3GPP TS 32.240 | Telecommunication management; Charging management; Charging architecture and principles | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.3.1.2 |
2,285 | 4.15.3.2.11 Network-initiated explicit event notification subscription cancel procedure | The procedure is used by the UDM to delete an event notification subscription (see clause 4.15.1). Figure 4.15.3.2.11-1: Network-initiated event subscription removal procedure 0. An event notification subscription procedure according to clause 4.15.3.2.2 or clause 4.15.3.2.2 has already executed successfully. 1-1a. If UE subscription is withdrawn in UDM, UE authorisation to the subscribed monitoring event or UE is removed from the subscribed target group, the UDM triggers Nudm_EventExposure_Notify towards the associated notification endpoint indicating the removal of the event notification along with the time stamp. The 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. In order to remove 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 or External Identity) to the NEF and indicates the removal of the event notification subscription for these UE(s). 2a-2b. If UE subscription information changes (e.g. UE group information changes), the UDM sends Nudm_SDM_Notification request to related serving AMF(s) to update event notification subscription information. If the UE was a group member of a previous accepted group-based 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 UE subscription data is withdrawn, the UDM sends Nudm_UECM_DeregistrationNotification request to related serving AMF(s) to remove UE subscription information. If the UE was a group member of a previous accepted group-based event notification subscription, the AMF shall keep the accepted group-based event notification subscription unless all UEs subscriptions in the group are withdrawn. 3. The NEF sends Nnef_EventExposure_Nofity to the AF reporting event received by Nudm_EventExposure_Notify. If the NEF receives UE Identifier(s) in step 1 for a group-based event notification subscription and the Maximum Number of Reports applies to the group-based event notification subscription, the NEF sets the number of reports of the indicated UE(s) to Maximum Number of Reports. The NEF sends Nnef_EventExposure_Notify to the AF and includes MSISDN(s) or External Identifier(s). If NEF determines that the reporting for the group is complete based on the update above, the NEF deletes the associated event notification subscription and requests that the UDM deletes the related event notification subscription for the group. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.15.3.2.11 |
2,286 | 4.5.3 DL Total PRB Usage | This measurement provides the total usage (in percentage) of physical resource blocks (PRBs) on the downlink for any purpose. If there is one or more RNs served in a cell, for that cell the eNodeB performs PRB usage measurements separately for all traffic(including transmissions to/from RNs and UEs directly connected to the eNodeB) and for RN traffic. The measurement is also applicable to RNs. SI This measurement is obtained according to the definition in 3GPP TS 36.314[ Evolved Universal Terrestrial Radio Access (E-UTRA); Layer 2 - Measurements ] [11]. A single integer value from 0 to 100. RRU.PrbTotDl, which indicats the DL PRB Usage for all traffic RRU.PrbTotDlRN, which indicates the DL PRB Usage for the RN traffic EUtranCellFDD EUtranCellTDD Valid for packet switched traffic EPS | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.5.3 |
2,287 | 5.2.8.2.10 Nsmf_PDUSession_ContextRequest service operation | Service operation name: Nsmf_PDUSession_ContextRequest. Description: This service operation is used by the NF Consumer to request for SM Context (e.g. during EPS IWK, HO, SM Context transfer indication), or during mobility procedure with I-SMF (or V-SMF) changes or may be triggered by OAM. Input, Required: SM Context ID, SM context type. Input, Optional: Target MME Capability, EBI list not to be transferred, PDU Session ID (include PDU Session ID when available), SMF transfer indication, indication of no NG-RAN change. Output, Required: One of the following: - SM Context Container. - Endpoint where SM Context can be retrieved. Output, Optional: Small Data Rate Control Status. The SM context type indicates the type of SM context to be requested, e.g. PDN Connection Context, 5G SM Context or both. The SM context type may also indicate that only a specific part of 5G SM Context is requested, e.g. only the AF Coordination Information part. If the SM context type is PDN Connection Context, the SM Context included in the SM Context container is the PDN Connection Context. If the SM context type is all, the SM Context included in the SM Context container includes both the PDN Connection Context and the 5G SM Context. Table 5.2.8.2.10-1 illustrates the SM Context that may be transferred between I-SMF(s) or between V-SMF(s) in home-routed roaming case. Table 5.2.8.2.10-1: SM Context of a PDU Session transferred between I-SMF(s) or between V-SMF(s) or between I/V-SMF and (H-)SMF | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.8.2.10 |
2,288 | 8.3.14.4 Extended protocol configuration options | This IE shall be included in the message when, during the attach procedure, the UE wishes to transmit security protected (protocol) data (e.g. configuration parameters, error codes or messages/events) to the network, and: a) the UE is in NB-S1 mode; b) the requested PDN Type is non-IP or Ethernet; or c) the requested APN is for UAS services. This IE shall be included if: a) the UE supports local IP address in traffic flow aggregate description and TFT filter, the UE is in NB-S1 mode and the requested PDN Type is different from non-IP and Ethernet; or b) the UE supports local IP address in traffic flow aggregate description and TFT filter, the requested PDN Type is different from non-IP and Ethernet, and the requested APN is for UAS services. This IE shall not be included if the Protocol configuration options IE is included in the message. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 8.3.14.4 |
2,289 | B.2.2 Serving PLMN Rate Control information handling in the PGW | If Serving PLMN rate control information is received in the Serving PLMN Rate Control IE from the MME, the PGW shall store this information and use that for rate control enforcement DL for this UE. If the PGW previously have received Serving PLMN rate control information, the PGW shall behave as follows: - If the PGW receives new Serving PLMN rate control information in the Serving PLMN Rate Control IE from the MME, the PGW shall replace the old Serving PLMN rate control information with the new Serving PLMN rate control information and use that for rate control enforcement DL for this UE. - If the PGW receives no Serving PLMN rate control information in the Serving PLMN Rate Control IE from the MME in an IP-CAN session establishment or an IP-CAN session modification , the PGW shall still consider the latest received Serving PLMN rate control information from the MME as valid. - If PGW receives an indication that Serving PLMN rate control does not apply in the Serving PLMN Rate Control IE, the PGW shall remove the rate control information based on Serving PLMN rate control information. See 3GPP TS 29.274[ 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 ] [81] for Serving PLMN Rate Control IE definition. APN rate control, if configured, also applies for the same IP-CAN session, see subclause B.2.1. | 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 | B.2.2 |
2,290 | 5.13 Support for Edge Computing | Edge computing enables operator and 3rd party services to be hosted close to the UE's access point of attachment, so as to achieve an efficient service delivery through the reduced end-to-end latency and load on the transport network. Edge Computing support by 5GC is specified in this specification and in TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [130]. NOTE: Edge Computing typically applies to non-roaming and LBO roaming scenarios. For HR roaming scenarios, Edge Computing applies only for "Home Routed with Session Breakout in VPLMN (HR-SBO)" which is described in clause 6.7 of TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [130]. The 5G Core Network selects a UPF close to the UE and forwards traffic to enable the local access to the DN via a N6 interface according to the provided traffic steering rules to the UPF. This may be based on the UE's subscription data, UE location, the information from Application Function (AF) as defined in clause 5.6.7, the EAS information reported from EASDF (as defined in TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [130]), policy or other related traffic rules. Due to user or Application Function mobility, the service or session continuity may be required based on the requirements of the service or the 5G network. The 5G Core Network may expose network information and capabilities to an Edge Computing Application Function. NOTE: Depending on the operator deployment, certain Application Functions can be allowed to interact directly with the Control Plane Network Functions with which they need to interact, while the other Application Functions need to use the external exposure framework via the NEF (see clause 6.2.10 for details). Edge computing can be supported by one or a combination of the following enablers: - User plane (re)selection: the 5G Core Network (re)selects UPF to route the user traffic to the local part of the DN as described in clause 6.3.3; - Local Routing and Traffic Steering: the 5G Core Network selects the traffic to be routed to the applications in the local part of the DN; - this includes the use of a single PDU Session with multiple PDU Session Anchor(s) (UL CL / IP v6 multi-homing) as described in clause 5.6.4 and the use of a PDU Session with Distributed Anchor Point using SSC mode 2/3. - Session and service continuity to enable UE and application mobility as described in clause 5.6.9; - An Application Function may influence UPF (re)selection and traffic routing via PCF or NEF as described in clause 5.6.7; - Network capability exposure: 5G Core Network and Application Function to provide information to each other via NEF as described in clause 5.20 or directly as described in clause 4.15 of TS 23.502[ Procedures for the 5G System (5GS) ] [3] or from the UPF as described in clause 6.4 of TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [130]; - QoS and Charging: PCF provides rules for QoS Control and Charging for the traffic routed to the local part of the DN; - Support of Local Area Data Network: 5G Core Network provides support to connect to the LADN in a certain area where the applications are deployed as described in clause 5.6.5. - Discovery and re-discovery of Edge Applications Servers as described in TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [130]. - Support of Edge Relocation as described in TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [130] and the case of involving AF change as described in clauses 4.3.6.2, 4.3.6.3 and 4.3.6.4 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. Support of 5GC triggered Edge relocation within the same hosting PLMN's EHEs. - Support of (I-)SMF (re)selection based on DNAI as described in clauses 4.3.5.1, 4.3.5.2 and 4.23.5.1 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. - Support of finer sets of UEs. - Support of common EAS discovery and common DNAI determination for set of UEs as described in clause 6.2 of TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [130]. - Support of mapping information between EAS IP/IP range and DNAI as described in clause 6.8 of TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [130]. - Support of AF request for DNAI as described in clause 6.8 of TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [130]. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.13 |
2,291 | 6.8.1.2.2 Establishment of keys for cryptographically protected radio bearers in 3GPP access | This sub-clause applies to establishment of keys for cryptographically protected radio bearers in 3GPP access only. The procedure the UE uses to establish cryptographic protection for radio bearers is initiated by an NAS Service Request message or Registration Request message with "PDU session(s) to be re-activated" included from the UE to the AMF. The AMF may initiate the procedure to establish cryptographic protection for radio bearers when "PDU session(s) to be re-activated" is not included in the Registration request and but there is pending downlink UP data or pending downlink signalling. Upon receipt of the NAS message, if the AMF does not require a NAS SMC procedure before initiating the NGAP procedure INITIAL CONTEXT SETUP, the AMF shall derive key KgNB/KeNB as specified in Annex A using the uplink NAS COUNT (see TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [35]) corresponding to the NAS message that initiated transition from CM-IDLE to CM-CONNECTED state and the KAMF of the current 5G NAS security context. The AMF shall communicate the KgNB/KeNB to the serving gNB/ng-eNB in the NGAP procedure INITIAL CONTEXT SETUP. The UE shall derive the KgNB/KeNB from the KAMF of the current 5G NAS security context using the NAS uplink COUNT corresponding to the NAS message that initiated transition from CM-IDLE to CM-CONNECTED state. As a result of the NAS Service Request or Registration procedure, with "PDU session(s) to be re-activated" radio bearers are established, and the gNB/ng-eNB sends an AS SMC to the UE. When the UE receives the AS SMC without having received a NAS Security Mode Command, it shall use the NAS uplink COUNT corresponding to the NAS message that initiated transition from CM-IDLE to CM-CONNECTED state as freshness parameter in the derivation of the KgNB/KeNB. The KDF as specified in Annex A shall be used for the KgNB/KeNB derivation using the KAMF of the current 5G NAS security context. From the KgNB/KeNB the RRC protection keys and the UP protection keys are derived by the UE and the gNB/ng-eNB as described in sub-clause 6.2. If the NAS procedure establishing radio bearers contains a primary authentication run (which is optional), the NAS uplink and downlink COUNT for the new KAMF shall be set to the start values (i.e. zero). If the NAS procedure establishing radio bearers contains a NAS SMC (which is optional), the value of the uplink NAS COUNT corresponding to the most recent NAS Security Mode Complete shall be used as freshness parameter in the KgNB/KeNB derivation from fresh KAMF of the current 5G NAS security context when executing an AS SMC. The KDF as specified in Annex A shall be used for the KgNB/KeNB derivation also in this case. The case that the UE is using Control Plane CIoT 5GS optimisation to send data over NAS and N3 bearers are established (due to either a request from the UE or decided by the AMF - see 5.31.4 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]) works as follows. The UE and AMF shall always use the value of the uplink NAS COUNT from the Control Plane Service Request that was sent to transition the UE from idle to active as freshness parameter in the derivation of the KeNB unless there has been a subsequent NAS Security Mode Complete. If there was a subsequent NAS Security Mode Complete, then the UE and AMF use the value of the uplink NAS COUNT from the latest NAS Security Mode Complete message as freshness parameter in the derivation of the KeNB. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.8.1.2.2 |
2,292 | 5.5.3.2.3 EMM common procedure initiation | If the network receives a TRACKING AREA UPDATE REQUEST message containing the Old GUTI type IE, and the network does not follow the use of the most significant bit of the <MME group id> to distinguish the node type as specified in 3GPP TS 23.003[ Numbering, addressing and identification ] [2], clause 2.8.2.2.2, the network shall use the Old GUTI type IE to determine whether the mobile identity included in the Old GUTI IE is a native GUTI or a mapped GUTI. During the tracking area updating procedure, the MME may initiate EMM common procedures, e.g. the EMM authentication and security mode control procedures. The MME may be configured to skip the authentication procedure even if no EPS security context is available and proceed directly to the execution of the security mode control procedure as specified in clause 5.4.3, during a tracking area updating procedure for a UE that has only a PDN connection for emergency bearer services or for RLOS. The MME shall not initiate an EMM authentication procedure before completion of the tracking area updating procedure, if the following conditions apply: a) the UE initiated the tracking area updating procedure after handover or inter-system handover to S1 mode; b) the target cell is a shared network cell; and - the UE has provided its GUTI in the Old GUTI IE or the Additional GUTI IE in the TRACKING AREA UPDATE REQUEST message, and the PLMN identity included in the GUTI is different from the selected PLMN identity of the target cell; or - the UE has mapped the P-TMSI and RAI into the Old GUTI IE and not included an Additional GUTI IE in the TRACKING AREA UPDATE REQUEST message, and the PLMN identity included in the RAI is different from the selected PLMN identity of the target cell. | 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.3.2.3 |
2,293 | 6.5.4.3 FRESH | The network-side nonce FRESH is 32 bits long. There is one FRESH parameter value per user. The input parameter FRESH protects the network against replay of signalling messages by the user. At connection set-up the RNC generates a random value FRESH and sends it to the user in the (RRC) security mode command. The value FRESH is subsequently used by both the network and the user throughout the duration of a single connection. This mechanism assures the network that the user is not replaying any old MAC-Is. At handover with relocation of the S-RNC, the new S-RNC generates its own value for the FRESH parameter and sends it to the ME in the RRC message that indicates a new UTRAN Radio Network Temporary Identity due to a SRNC relocation (see TS 25.331[ None ] [17]). | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | 6.5.4.3 |
2,294 | 6.2.4A.1 A-MPR for CA_NS_01 for CA_1C | If the UE is configured to CA_1C and it receives IE CA_NS_01 the allowed maximum output power reduction applied to transmissions on the PCC and the SCC for contiguously aggregated signals is specified in table 6.2.4A.1-1. Table 6.2.4A.1-1: Contiguous allocation A-MPR for CA_NS_01 If the UE is configured to CA_1C and it receives IE CA_NS_01 the allowed maximum output power reduction applied to transmissions on the PCell and the SCell with non-contiguous resource allocation is defined as follows A-MPR = CEIL {MA, 0.5} Where MA is defined as follows MA = -22.5 A + 17 ; 0 ≤ A < 0.20 -11.0 A + 14.7 ; 0.20 ≤ A < 0.70 -1.7 A + 8.2 ; 0.70 ≤ A ≤ 1 Where A = NRB_alloc / NRB_agg. | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.2.4A.1 |
2,295 | 5.5.2.2.4 Abnormal cases in the UE | The following abnormal cases can be identified: a) Access barred because of access class barring, EAB or NAS signalling connection establishment rejected by the network In WB-S1 mode, if access is barred for "originating signalling" (see 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [22]), the detach signalling procedure shall not be started. The UE stays in the current serving cell and applies the normal cell reselection process. The detach signalling procedure is started as soon as possible and if still necessary, i.e. when access for "originating signalling" is granted on the current cell or when the UE moves to a cell where access for "originating signalling" is granted. The UE may perform a local detach either immediately or after an implementation dependent time. In NB-S1 mode, if access is barred for "originating signalling" (see 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [22]), the detach signalling procedure shall not be started. The UE stays in the current serving cell and applies the normal cell reselection process. Further UE behaviour is implementation specific, e.g. the detach signalling procedure is started again after an implementation dependent time. NOTE 1: In NB-S1 mode, the EMM layer cannot receive the access barring alleviation indication from the lower layers (see 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [22]). b) Lower layer failure or release of the NAS signalling connection before reception of DETACH ACCEPT message The detach procedure shall be aborted and the UE proceeds as follows: - if the detach procedure was performed due to disabling of EPS services, the UE shall enter the EMM-NULL state; - if "EPS detach" was requested for reasons other than disabling of EPS services, the UE shall enter the EMM-DEREGISTERED state; - if "IMSI detach" was requested, the UE shall enter the EMM-REGISTERED.NORMAL-SERVICE state and the MM-NULL state; or - if "combined EPS/IMSI detach" was requested, the UE shall enter the EMM-DEREGISTERED state and the MM-NULL state. c) T3421 timeout On the first four expiries of the timer, the UE shall retransmit the DETACH REQUEST message and shall reset and restart timer T3421. On the fifth expiry of timer T3421, the detach procedure shall be aborted and the UE proceeds as follows: - if the detach procedure was performed due to disabling of EPS services, the UE shall enter the EMM-NULL state; - if "EPS detach" was requested for reasons other than disabling of EPS services, the UE shall enter the EMM-DEREGISTERED state; - if "IMSI detach" was requested, the UE shall enter the EMM-REGISTERED.NORMAL-SERVICE state and the MM-NULL state; or - if "combined EPS/IMSI detach" was requested, the UE shall enter the EMM-DEREGISTERED state and the MM-NULL state. d) Detach procedure collision Detach containing cause "switch off" within the Detach type IE: - If the UE receives a DETACH REQUEST message before the UE initiated detach procedure has been completed, this message shall be ignored and the UE initiated detach procedure shall continue. Detach containing other causes than "switch off" within the Detach type IE: - If the UE receives a DETACH REQUEST message before the UE initiated detach procedure has been completed, it shall treat the message as specified in clause 5.5.2.3.2 with the following modifications: - If the DETACH REQUEST message received by the UE contains detach type "re-attach required", and the UE initiated detach procedure is with detach type "EPS detach" or "combined EPS/IMSI detach", the UE need not initiate the attach or combined attach procedure. - If the DETACH REQUEST message received by the UE contains detach type "IMSI detach", and the UE initiated detach procedure is with detach type "IMSI detach", the UE need not re-attach to non-EPS services. - If the DETACH REQUEST message received by the UE contains detach type "IMSI detach", and the UE initiated detach procedure is with detach type "EPS detach" or "combined EPS/IMSI detach", the UE shall progress both procedures. The UE need not re-attach to non-EPS services. e) Detach and EMM common procedure collision Detach containing cause "switch off": - If the UE receives a message used in an EMM common procedure before the detach procedure has been completed, this message shall be ignored and the detach procedure shall continue. Detach containing other causes than "switch off" and containing detach type "IMSI detach": - If the UE receives a message used in an EMM common procedure before the detach procedure has been completed, both the EMM common procedure and the detach procedure shall continue. Detach containing other causes than "switch off" and containing other detach types than "IMSI detach": - If the UE receives a GUTI REALLOCATION COMMAND, an EMM STATUS or an EMM INFORMATION message before the detach procedure is completed, this message shall be ignored and the detach procedure shall continue. - If the UE receives an AUTHENTICATION REQUEST, SECURITY MODE COMMAND or IDENTITY REQUEST message before the detach procedure has been completed, the UE shall respond to it as described in clause 5.4.2, 5.4.3 and 5.4.4 respectively and the detach procedure shall continue. f) Change of cell into a new tracking area If the UE detects the current TAI is not in the stored TAI list occurs before the UE initiated detach procedure is completed, the UE proceeds as follows: 1) If the detach procedure was initiated for reasons other than removal of the USIM or the UE is to be switched off, the detach procedure shall be aborted and re-initiated after successfully performing a tracking area updating procedure; or 2) If the detach procedure was initiated due to removal of the USIM or the UE is to be switched off, the UE shall abort the detach procedure, perform a local detach and enter the state EMM-DEREGISTERED. g) Transmission failure of DETACH REQUEST message indication with TAI change from lower layers If the current TAI is not in the TAI list, the UE proceeds as follows: 1) If the detach procedure was initiated for reasons other than removal of the USIM or the UE is to be switched off, the detach procedure shall be aborted and re-initiated after successfully performing a tracking area updating procedure; or 2) If the detach procedure was initiated due to removal of the USIM or the UE is to be switched off, the UE shall abort the detach procedure, perform a local detach and enter the state EMM-DEREGISTERED. If the current TAI is still part of the TAI list, the UE shall restart the detach procedure. h) Transmission failure of DETACH REQUEST message indication without TAI change from lower layers The UE shall restart the detach procedure. i) Detach and paging procedure collision If the UE receives a CS SERVICE NOTIFICATION message before the UE initiated combined detach procedure with detach type "IMSI detach" or "combined EPS/IMSI detach" has been completed, then this message shall be ignored and the UE initiated combined detach procedure shall continue. For the cases b, f and g: - Timer T3421 shall be stopped if still running. | 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.2.2.4 |
2,296 | 8.10.4.1.1 FDD | The parameters specified in Table 8.10.4.1.1-1 are valid for all FDD distributed EPDCCH test with 4Rx unless otherwise stated. Table 8.10.4.1.1-1: Test Parameters for Distributed EPDCCH with 4Rx For the parameters specified in Table 8.10.4.1.1-1 the average probability of a missed downlink scheduling grant (Pm-dsg) shall be below the specified value in Table 8.10.4.1.1-2. The downlink physical setup is in accordance with Annex C.3.2. Table 8.10.4.1.1-2: Minimum performance Distributed EPDCCH with 4Rx Antenna ports | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.10.4.1.1 |
2,297 | 6.2.5.1.1.3 Derived QoS rules | Derived QoS rules are applicable only for PDU session of IPv4, IPv6, IPv4v6 or Ethernet PDU session type. The reflective QoS in the UE creates derived QoS rules associated with a PDU session based on DL user data packets received via the PDU session. Each derived QoS rule contains: a) a QoS flow identifier (QFI); b) a packet filter for UL direction; and c) a precedence value of 80 (decimal). NOTE: On the network side, the corresponding QoS rule can be associated with a different precedence value in the range from 70 to 99 (decimal). Within a PDU session: a) there can be zero, one or more derived QoS rules associated with a given QFI; and b) there can be up to one derived QoS rule associated with a given packet filter for UL direction. In the UE, a timer T3583 runs for each derived QoS rule. Reflective QoS is not supported in NB-N1 mode. Reflective QoS is not applicable for a PDU session with control plane only indication. | 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.5.1.1.3 |
2,298 | 8.10.1.2.12 Closed loop spatial multiplexing performance - Single-Layer Spatial Multiplexing with CRS assistance information (User-Specific Reference Symbols) | The requirements are specified in Table 8.10.1.2.12-2, with the addition of parameters in Table 8.10.1.2.12-1. In Table 8.10.1.2.12-1, Cell 1 is the serving cell, and Cell 2 and Cell 3 are the aggressor cells. The downlink physical channel setup is according to Annex C.3.2 for each of Cell 1, Cell 2 and Cell 3, respectively. The CRS assistance information [7] is provided to the UE and includes information on Cell 2 and Cell 3. The purpose of the test is to verify the closed loop single layer TM9 performance under assumption that UE applies CRS interference mitigation in the scenario with 2 CRS antenna ports in the serving and aggressor cells. Table 8.10.1.2.12-1: Test Parameters Table 8.10.1.2.12-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.2.12 |
2,299 | 16.7.2 Mobility 16.7.2.1 General | The same principles as described in 9.2 apply to CAG cells except for what is described below. Cell selection/reselection to CAG cells may be based on a UE autonomous search function, which determines itself when/where to search, but cannot contradict the dedicated cell reselection priority information if any is stored. A range of PCI values reserved by the network for use by CAG cells may be broadcast. A CAG Member Cell for a UE is a cell broadcasting the identity of the selected PLMN, registered PLMN or equivalent PLMN, and for that PLMN, a CAG identifier belonging to the Allowed CAG list of the UE for that PLMN. The UE checks the suitability of CAG cells based on the Allowed CAG list provided by upper layers and a CAG-only cell can only be suitable for its subscribers but can be acceptable for the rest. NOTE: A non-CAG-capable UE (e.g. Rel-15 UE) considers a CAG-only cell as acceptable cell if the cell is not barred to Rel-15 UEs, and if a PLMN ID without CAG list is broadcast and that PLMN is forbidden (e.g. by use of a PLMN ID for which all registration attempts are rejected such that the PLMN ID becomes forbidden). When the UE is configured with a CAG-only indication, only CAG Member Cells can be suitable. A non-suitable cell can be acceptable though if the UE is configured with a CAG-only indication for one of the PLMN broadcast by the cell. In addition, manual selection of CAG cell(s) is supported, for which an HRNN(s) can be optionally provided. The roaming and access restrictions applicable to PNI-NPN are described in clause 9.4. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.7.2 |
2,300 | 5.14.2.1 SCI reception | SCI transmitted on the PSCCH indicate if there is a transmission on SL-SCH and provide the relevant HARQ information. The MAC entity shall: - for each subframe during which the MAC entity monitors PSCCH: - if SCI for this subframe has been received on the PSCCH for sidelink communication with a Group Destination ID of interest to this MAC entity: - determine the set of subframes in which reception of the first transport blocks occur according to clause 14.2.2 of TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [2] using the received SCI; - store the SCI and associated HARQ information as SCI valid for the subframes corresponding to first transmission of each transport block; - else if SCI for this subframe has been received on the PSCCH for V2X sidelink communication: - determine the set of subframes in which reception of the transport block occur according to clause 14.1.2 of TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [2] using the received SCI; - store the SCI and associated HARQ information as SCI valid for the subframes corresponding to transmission(s) of the transport block; - for each subframe for which the MAC entity has a valid SCI: - deliver the SCI and the associated HARQ information to the Sidelink HARQ Entity. | 3GPP TS 36.321 | Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification | RAN2 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 5.14.2.1 |
Subsets and Splits
No saved queries yet
Save your SQL queries to embed, download, and access them later. Queries will appear here once saved.