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
⌀ |
|---|---|---|---|---|---|---|---|
6,601 | 16.7.2.3 Connected Mode | The source NG-RAN node is aware of the list of CAG IDs supported by the candidate target cells which are CAG cells. At the time of handover, the source NG-RAN node determines a target cell among the candidates which is compatible with the received PNI-NPN restrictions. At incoming handover, the target NG-RAN node receives the PNI-NPN mobility restrictions and checks that the selected target cell is compatible with the received mobility restrictions. Mobility between PNI-NPN and PLMN cells is supported according to the mobility restrictions in the UE context. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.7.2.3 |
6,602 | 5.4.1.3 GUTI reallocation completion by the UE | Upon receipt of the GUTI REALLOCATION COMMAND message, the UE shall: - store the GUTI; - store the TAI list, if provided; - store the DCN-ID, if provided; - in WB-S1 mode, if the UE supports RACS and the GUTI REALLOCATION COMMAND message includes: a) a UE radio capability ID deletion indication IE set to "Network-assigned UE radio capability IDs deletion requested", delete any network-assigned UE radio capability IDs associated with the registered PLMN stored at the UE, then the UE shall, after the completion of the ongoing GUTI reallocation procedure, initiate a tracking area updating procedure as specified in clause 5.5.3. If the UE has an applicable manufacturer-assigned UE radio capability ID for the current UE radio configuration, the UE shall include the UE radio capability ID availability IE set to "UE radio capability ID available" in the TRACKING AREA UPDATE REQUEST message; or b) a UE radio capability ID IE, store the UE radio capability ID as specified in annex C; and - send a GUTI REALLOCATION COMPLETE message to the MME. The UE considers the new GUTI as valid and the old GUTI as invalid. If the UE receives a new TAI list in the GUTI REALLOCATION COMMAND message, the UE shall consider the new TAI list as valid and the old TAI list as invalid; otherwise, the UE shall consider the old TAI list as valid. If the GUTI REALLOCATION COMMAND message contains the DCN-ID IE, then the UE shall store the included DCN-ID value together with the PLMN code of the registered PLMN in a DCN-ID list in a non-volatile memory in the ME as specified in annex C. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.4.1.3 |
6,603 | 5.8.13.2 NR sidelink discovery monitoring | A UE capable of NR sidelink discovery that is configured by upper layers to monitor NR sidelink discovery messages shall: 1> if the frequency used for NR sidelink discovery is included in sl-FreqInfoToAddModList in RRCReconfiguration message and sl-DiscConfig is included in RRCReconfiguration; or if the frequency used for NR sidelink discovery is included in sl-FreqInfoList included in SIB12 and sl-DiscConfigCommon is included in SIB12: 2> if the UE is configured with sl-DiscRxPool for NR sidelink discovery reception included in RRCReconfiguration message with reconfigurationWithSync (i.e. handover): 3> configure lower layers to monitor sidelink control information and the corresponding data using the resource pool indicated by sl-DiscRxPool for NR sidelink discovery reception in RRCReconfiguration; 2> else if the UE is configured with sl-RxPool for NR sidelink discovery reception included in RRCReconfiguration message with reconfigurationWithSync (i.e. handover): 3> configure lower layers to monitor sidelink control information and the corresponding data using the resource pool indicated by sl-RxPool for NR sidelink discovery reception in RRCReconfiguration; 2> else if the cell chosen for NR sidelink discovery reception provides SIB12: 3> if sl-DiscRxPool for NR sidelink discovery reception is included in SIB12: 4> configure lower layers to monitor sidelink control information and the corresponding data using the resource pool indicated by sl-DiscRxPool for NR sidelink discovery reception in SIB12; 3> else if sl-RxPool for NR sidelink discovery reception is included in SIB12: 4> configure lower layers to monitor sidelink control information and the corresponding data using the resource pool indicated by sl-RxPool for NR sidelink discovery reception in SIB12; 1> else: 2> if out of coverage on the concerned frequency for NR sidelink discovery: 3> if sl-DiscRxPool was preconfigured: 4> configure lower layers to monitor sidelink control information and the corresponding data using the resource pool that was preconfigured by sl-DiscRxPool for NR sidelink discovery reception in SL-PreconfigurationNR, as defined in clause 9.3; 3> else: 4> configure lower layers to monitor sidelink control information and the corresponding data using the resource pool that was preconfigured by sl-RxPool for NR sidelink discovery reception in SL-PreconfigurationNR, as defined in clause 9.3; NOTE: If sl-DiscRxPool and sl-RxPool are both included in SIB12 or preconfigured, it is up to UE implementation whether to monitor sidelink control information and the corresponding data using the resource pool indicated by sl-RxPool for NR sidelink discovery reception. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.8.13.2 |
6,604 | 4.3.3 Packet routing and transfer functions 4.3.3.1 General | A route is an ordered list of nodes used for the transfer of packets within and between the PLMN(s). Each route consists of the originating node, zero or more relay nodes and the destination node. Routing is the process of determining and using, in accordance with a set of rules, the route for transmission of a message within and between the PLMN(s). The EPS is an IP network and uses the standard routing and transport mechanisms of the underlying IP network. The Maximum Transfer Unit (MTU) size considerations in clause 9.3 of TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [7] are also applicable to EPS. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.3.3 |
6,605 | 17.8.2 Permanent Failures | Errors that fall within the Permanent Failures category are used to inform the peer that the request failed, and should not be attempted again. The Result-Code AVP values defined in Diameter Base IETF RFC 6733 [111] are applicable. Also the following specific Gmb Experimental-Result-Code values are defined for permanent failures: DIAMETER_ERROR_START_INDICATION (5120) This error covers the case when a MBMS Session Start procedure could not be performed due to some of the required session attributes that are necessary to activate the bearer resources are missing (QoS, MBMS Service Area…). The Failed-AVP AVP must contain the missing AVP. DIAMETER_ERROR_STOP_INDICATION (5121) An indication of session stop has been received with no session start procedure running. DIAMETER_ERROR_UNKNOWN_MBMS_BEARER_SERVICE (5122) The requested MBMS service is unknown at the BM-SC. DIAMETER_ERROR_SERVICE_AREA (5123) The MBMS service area indicated for a specific MBMS Bearer Service is unknown or not available. | 3GPP TS 29.061 | Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) | CT WG3 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 17.8.2 |
6,606 | 7.2 Remote Interference Management | The Remote Interference Management function in non-split gNB case is specified in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [2]. In case of split gNB architecture, in the victim set, a gNB-DU detects the remote interference. If remote interference is detected, the gNB-DU can send out the RIM-RS. In the aggressor set, if a gNB-DU detects the RIM-RS sent by the victim gNB(s), it sends to the gNB-CU the RIM-RS detection status and the victim Set ID. The gNB-CU acts as a coordinator on behalf of its affiliated gNB-DUs, where the gNB-CU merges the outgoing RIM information received from its gNB-DUs in the aggressor set and forwards the merged information to all the gNBs in the victim set. Similarly, in the victim set, the gNB-CU distributes the incoming RIM information to all the gNB-DUs in the set, as indicated in the RIM information received from the aggressor set. In addition, to facilitate consolidation of RIM information, the gNB-DU provides the associated aggressor set ID and the victim set ID of each serving cell to the gNB-CU. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 7.2 |
6,607 | 4.15.9.3 Time Synchronization activation, modification and deactivation 4.15.9.3.1 General | This procedure can be used by the AF to activate, modify or deactivate the (g)PTP instances in 5GS. The AF may activate the time synchronization service using the Nnef_TimeSynchronization_ConfigCreate service operation. The service operation creates a time synchronization configuration based on the service parameters as indicated in the create request. The AF may update the time synchronization configuration using the Nnef_TimeSynchronization_ConfigUpdate service operation. The AF may deactivate the time synchronization service using the Nnef_TimeSynchronization_ConfigDelete service operation, which deletes the corresponding time synchronization service configuration. The AF may subscribe to time synchronization status report by providing clock quality acceptance criteria via Nnef_TimeSynchronization_ConfigCreate service operation. The AF may receive time synchronization service status update via Nnef_TimeSynchronization_UpdateNotify service operation. 5GS may provide a time synchronization status report to the AF in case of a PTP port is activated or deactivated due to a detected failure, degradation, or improvement of the service. The Nnef_TimeSynchronization_ConfigCreate and Nnef_TimeSynchronization_ConfigUpdate request may contain the parameters as described in Table 4.15.9.3-1. Table 4.15.9.3-1: Description of Time Synchronization service parameters The AF may use Nnef_TimeSynchronization_CapsSubscribe service operation as described in clause 4.15.9.2 to learn the UE capabilities for time synchronization service. The Nnef_TimeSynchronization_CapsNotify service operation indicates the list of UE identities, User-plane Node ID and the Subscription Correlation ID. The AF can use the Subscription Correlation ID and the user-plane node ID received in the Nnef_TimeSynchronization_CapsNotify service operation as a target of the Nnef_TimeSynchronization_ConfigCreate request. The NEF uses the Subscription Correlation ID and user-plane node ID to determine the list of UEs and list of AF-sessions to which the Nnef_TimeSynchronization_ConfigCreate service operation is targeted to. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.15.9.3 |
6,608 | 4.2.2.5 Service State, SEARCH FOR PLMN, NORMAL SERVICE | When in state MM IDLE and service state SEARCH FOR PLMN, NORMAL SERVICE the mobile station shall: - if timer T3211 or T3213 expires in this state perform a location updating procedure at the latest if and when back to NORMAL SERVICE state and if the cell is not changed; - if timer T3212 expires in this state perform a periodic location updating procedure at the latest if and when back to NORMAL SERVICE state; - perform IMSI detach; - support requests from the CM layer; - listen as far as possible to paging, and respond; and - for an eCall only mobile station (as determined by information configured in USIM), perform the eCall inactivity procedure at expiry of timer T3242 or T3243. In addition, mobile stations supporting VGCS listening or VBS listening shall: - listen as far as possible to notifications and indicate notifications to the GCC or BCC layer; - respond to notification if the GCC or BCC sublayer requests the reception of a voice group or broadcast call for which no channel description has been received in the notification by the RR sublayer; - request the RR sublayer to receive a voice group or broadcast call if the GCC or BCC sublayer requests the reception of a voice group or broadcast call for which a channel description has been received in the notification by the RR sublayer. | 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.2.2.5 |
6,609 | 10.5.7.4a GPRS Timer 3 | The purpose of the GPRS timer 3 information element is to specify GPRS specific timer values, e.g. for the timer T3396. The GPRS timer 3 is a type 4 information element with 3 octets length. The GPRS timer 3 information element is coded as shown in figure 10.5.147a/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.163a/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Figure 10.5.147a/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : GPRS Timer 3 information element Table 10.5.163a/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : GPRS Timer 3 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.7.4a |
6,610 | 4.25.5 NEF Anchored Mobile Terminated Data Transport | Figure 4.25.5-1 illustrates the procedure using which the AF sends unstructured data to a given user as identified via External Identifier or MSISDN. Figure 4.25.5-1: NEF Anchored Mobile Terminated Data Transport 1a. If AF has already activated the NIDD service for a given UE and has downlink unstructured data to send to the UE, the AF sends a Nnef_NIDD_Delivery Request (GPSI, TLTRI, unstructured data, Reliable Data Service Configuration) message to the NEF. Reliable Data Service Configuration is an optional parameter that is used to configure the Reliable Data Service, it may be used to indicate if a Reliable Data Service acknowledgement is requested and port numbers for originator application and receiver application. 1b. AMF indicates to NEF that the UE has become reachable. Based on this the NEF re-starts delivering buffered unstructured data to the UE. 2. The NEF determines the 5GS QoS Flow Context based on the DNN associated with the NIDD configuration and the User Identity. If an NEF 5GS QoS Flow Context corresponding to the GPSI included in step 1 is found, then the NEF checks if the AF is authorised to send data and if it does not exceed its quota or rate. If these checks fail, then steps 3-15 are skipped and an appropriate error code is returned in step 17. 3. The NEF forwards the unstructured data to the (H-)SMF using Nsmf_NIDD_Delivery Request. If NEF has indicated support of Extended Buffering in Nnef_SMContext_Create Response during SMF-NEF connection establishment, then NEF keeps a copy of the data. 4. In the roaming case, the H-SMF sends the Nsmf_PDUSession_TransferMTData to the V-SMF including MT small data. 5. The (V-)SMF determines whether Extended Buffering applies based on local policy and based on whether NEF has indicated support of Extended Buffering in Nnef_SMContext_Create Response during SMF-NEF connection establishment. (V-)SMF compresses the header if header compression applies and forwards the data and the PDU session ID to the AMF using the Namf_Communication_N1N2MessageTransfer service operation. If Extended Buffering applies, then (V-SMF) includes "Extended Buffering support" indication in Namf_Communication_N1N2Message Transfer. 6. If AMF determines the UE is unreachable for the SMF (e.g. if the UE is in MICO mode or the UE is configured for extended idle mode DRX), then the AMF rejects the request from the SMF. The AMF may include in the reject message an indication that the SMF need not trigger the Namf_Communication_N1N2MessageTransfer Request to the AMF, if the SMF has not subscribed to the event of UE reachability. If the SMF included Extended Buffering support indication, the AMF indicates the Estimated Maximum Wait time, in the reject message, for the SMF to determine the Extended Buffering time. If the UE is in MICO mode, the AMF determines the Estimated Maximum Wait time based on the next expected periodic registration timer update expiration or by implementation. If the UE is configured for extended idle mode DRX, the AMF determines the Estimated Maximum Wait time based on the start of next PagingTime Window. The AMF stores an indication that the SMF has been informed that the UE is unreachable. 7. In the roaming case V-SMF sends Nsmf_PDUSession_TransferMTData (Result Indication) response to H-SMF. If the V-SMF receives an "Estimated Maximum Wait time" from the AMF and Extended Buffering applies, the V-SMF also passes the "Estimated Maximum Wait time" to the H-SMF. 8. If the (H-)SMF receives a failure indication, (H-)SMF also sends a failure indication to NEF. If (H-)SMF has received the "Estimated Maximum Wait time" and Extended Buffering applies, the (H-)SMF includes Extended Buffering time in the failure indication. The Extended Buffering time is determined by the (H-)SMF and should be larger or equal to the Estimated Maximum Wait time. The NEF stores the DL data for the Extended Buffering time. The NEF does not send any additional Nsmf_NIDD_Delivery Request message if subsequent downlink data packets are received. The procedures stop at this step. 9. If the AMF determines the UE to be reachable in Step 5, then Steps 3 to 6 of the UPF anchored Mobile Terminated Data Transport in Control Plane CIoT 5GS Optimisation procedure (clause 4.24.2) apply. If the Reliable Data Service header indicates that the acknowledgement is requested, then the UE shall respond with an acknowledgement to the DL data that was received. 10. If the AMF has paged the UE to trigger the NAS procedure in step 9, the AMF shall initiate the UE configuration update procedure as defined in clause 4.2.4.2 to assign a new 5G-GUTI. 11. If the UE has not responded to paging, the AMF sends a failure notification to the (V-)SMF. Otherwise the procedure continues at step 13. 12. In the roaming case, if V-SMF has received a failure notification from AMF, then V-SMF sends Nsmf_PDUSession_TransferMTData (Result Indication) response to H-SMF. 13. If (H-)SMF receives a failure notification, then SMF indicates to the NEF that the requested Nsmf_NIDD_Delivery has failed. If Extended Buffering applies, then NEF purges the copy of the data. The procedure continues at step 17. 14. Steps 9 to 11 of the UPF anchored Mobile Terminated Data Transport in Control Plane CIoT 5GS Optimisation procedure (clause 4.24.2) apply. 15. AMF informs (V-)SMF that data has been forwarded. 16. In the roaming case, V-SMF sends Nsmf_PDUSession_TransferMTData (Result Indication) response to H-SMF that the data has been forwarded. 17. (H-)SMF indicates to NEF that the data has been forwarded. If Extended Buffering applies then NEF purges the copy of the data. 18. The NEF sends a Nnef_NIDD_Delivery Response (cause) to the AF. The Reliable Data Service Acknowledgement Indication is used to indicate if an acknowledgement was received from the UE for the MT NIDD. If the Reliable Data Service was requested in step 1, then the Nnef_NIDD_Delivery Response is sent to the AF after the acknowledgement is received from the UE or, if no acknowledgment is received, then the Nnef_NIDD_Delivery Response is sent to the AF with a cause value indicating that no acknowledgement was received. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.25.5 |
6,611 | – SL-ResourcePool | The IE SL-ResourcePool specifies the configuration information for NR sidelink communication resource pool. SL-ResourcePool information element -- ASN1START -- TAG-SL-RESOURCEPOOL-START SL-ResourcePool-r16 ::= SEQUENCE { sl-PSCCH-Config-r16 SetupRelease { SL-PSCCH-Config-r16 } OPTIONAL, -- Need M sl-PSSCH-Config-r16 SetupRelease { SL-PSSCH-Config-r16 } OPTIONAL, -- Need M sl-PSFCH-Config-r16 SetupRelease { SL-PSFCH-Config-r16 } OPTIONAL, -- Need M sl-SyncAllowed-r16 SL-SyncAllowed-r16 OPTIONAL, -- Need M sl-SubchannelSize-r16 ENUMERATED {n10, n12, n15, n20, n25, n50, n75, n100} OPTIONAL, -- Need M dummy INTEGER (10..160) OPTIONAL, -- Need M sl-StartRB-Subchannel-r16 INTEGER (0..265) OPTIONAL, -- Need M sl-NumSubchannel-r16 INTEGER (1..27) OPTIONAL, -- Need M sl-Additional-MCS-Table-r16 ENUMERATED {qam256, qam64LowSE, qam256-qam64LowSE } OPTIONAL, -- Need M sl-ThreshS-RSSI-CBR-r16 INTEGER (0..45) OPTIONAL, -- Need M sl-TimeWindowSizeCBR-r16 ENUMERATED {ms100, slot100} OPTIONAL, -- Need M sl-TimeWindowSizeCR-r16 ENUMERATED {ms1000, slot1000} OPTIONAL, -- Need M sl-PTRS-Config-r16 SL-PTRS-Config-r16 OPTIONAL, -- Need M sl-UE-SelectedConfigRP-r16 SL-UE-SelectedConfigRP-r16 OPTIONAL, -- Need M sl-RxParametersNcell-r16 SEQUENCE { sl-TDD-Configuration-r16 TDD-UL-DL-ConfigCommon OPTIONAL, -- Need M sl-SyncConfigIndex-r16 INTEGER (0..15) } OPTIONAL, -- Need M sl-ZoneConfigMCR-List-r16 SEQUENCE (SIZE (16)) OF SL-ZoneConfigMCR-r16 OPTIONAL, -- Need M sl-FilterCoefficient-r16 FilterCoefficient OPTIONAL, -- Need M sl-RB-Number-r16 INTEGER (10..275) OPTIONAL, -- Need M sl-PreemptionEnable-r16 ENUMERATED {enabled, pl1, pl2, pl3, pl4, pl5, pl6, pl7, pl8} OPTIONAL, -- Need R sl-PriorityThreshold-UL-URLLC-r16 INTEGER (1..9) OPTIONAL, -- Need M sl-PriorityThreshold-r16 INTEGER (1..9) OPTIONAL, -- Need M sl-X-Overhead-r16 ENUMERATED {n0,n3, n6, n9} OPTIONAL, -- Need S sl-PowerControl-r16 SL-PowerControl-r16 OPTIONAL, -- Need M sl-TxPercentageList-r16 SL-TxPercentageList-r16 OPTIONAL, -- Need M sl-MinMaxMCS-List-r16 SL-MinMaxMCS-List-r16 OPTIONAL, -- Need M ..., [[ sl-TimeResource-r16 BIT STRING (SIZE (10..160)) OPTIONAL -- Need M ]], [[ sl-PBPS-CPS-Config-r17 SetupRelease { SL-PBPS-CPS-Config-r17 } OPTIONAL, -- Need M sl-InterUE-CoordinationConfig-r17 SetupRelease { SL-InterUE-CoordinationConfig-r17 } OPTIONAL -- Need M ]], [[ sl-CPE-StartingPositionsPSCCH-PSSCH-InitiateCOT-List-r18 SetupRelease { SL-CPE-StartingPositionsPSCCH-PSSCH-List-r18 } OPTIONAL, -- Need M sl-CPE-StartingPositionsPSCCH-PSSCH-InitiateCOT-Default-r18 INTEGER (1..9) OPTIONAL, -- Need M sl-CPE-StartingPositionsPSCCH-PSSCH-WithinCOT-List-r18 SetupRelease { SL-CPE-StartingPositionsPSCCH-PSSCH-List-r18 } OPTIONAL, -- Need M sl-CPE-StartingPositionsPSCCH-PSSCH-WithinCOT-Default-r18 INTEGER (1..9) OPTIONAL, -- Need M sl-Type1-LBT-BlockingOption1-r18 ENUMERATED {enabled} OPTIONAL, -- Need R sl-Type1-LBT-BlockingOption2-r18 ENUMERATED {enabled} OPTIONAL, -- Need R sl-NumInterlacePerSubchannel-r18 ENUMERATED {sc1, sc2} OPTIONAL, -- Need M sl-NumReferencePRBs-OfInterlace-r18 ENUMERATED {prb10, prb11} OPTIONAL, -- Need M sl-TransmissionStructureForPSFCH-r18 ENUMERATED {commonInterlace, dedicatedInterlace} OPTIONAL, -- Need M sl-NumDedicatedPRBs-ForPSFCH-r18 ENUMERATED {prb1, prb2, prb5} OPTIONAL, -- Need M sl-NumPSFCH-Occasions-r18 ENUMERATED {o1, o2, o3, o4} OPTIONAL, -- Need M sl-PSFCH-CommonInterlaceIndex-r18 INTEGER (0..9) OPTIONAL, -- Need M sl-CPE-StartingPositionPSFCH-r18 INTEGER (1..9) OPTIONAL, -- Need M sl-NumRefSymbolLength-r18 ENUMERATED {sym7, sym8, sym9, sym10, sym11, sym12, sym13, sym14} OPTIONAL, -- Need M sl-PSFCH-RB-SetList-r18 SEQUENCE (SIZE (1..4)) OF BIT STRING (SIZE (10..275)) OPTIONAL, -- Need M sl-IUC-RB-SetList-r18 SEQUENCE (SIZE (1..4)) OF BIT STRING (SIZE (10..275)) OPTIONAL, -- Need M sl-PSFCH-PowerOffset-r18 INTEGER (0..10) OPTIONAL, -- Need M sl-RBSetIndexOfResourcePool-r18 SEQUENCE (SIZE (1..5)) OF INTEGER (0..4) OPTIONAL, -- Need M sl-A2X-Service-r18 ENUMERATED {brid, daa, bridAndDAA, spare1} OPTIONAL, -- Need M sl-PRS-ResourcesSharedSL-PRS-RP-r18 SEQUENCE (SIZE (1..17)) OF SL-PRS-ResourceSharedSL-PRS-RP-r18 OPTIONAL, -- Need M numSym-SL-PRS-2ndStageSCI-r18 INTEGER (1..4) OPTIONAL, -- Need M sl-SCI-based-SL-PRS-Tx-Trigger-SCI2-D-r18 BOOLEAN OPTIONAL, -- Need M sl-TriggerConditionRequest-r17 INTEGER (0..1) OPTIONAL -- Need M ]] } SL-CPE-StartingPositionsPSCCH-PSSCH-List-r18 ::= SEQUENCE (SIZE (8)) OF SL-CPE-StartingPositionsPSCCH-PSSCH-r18 SL-CPE-StartingPositionsPSCCH-PSSCH-r18 ::= SEQUENCE { sl-Priority-r18 INTEGER (1..8), sl-CPE-StartingPositions-r18 SEQUENCE (SIZE (1..9)) OF INTEGER (1..9) } SL-ZoneConfigMCR-r16 ::= SEQUENCE { sl-ZoneConfigMCR-Index-r16 INTEGER (0..15), sl-TransRange-r16 ENUMERATED {m20, m50, m80, m100, m120, m150, m180, m200, m220, m250, m270, m300, m350, m370, m400, m420, m450, m480, m500, m550, m600, m700, m1000, spare9, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1} OPTIONAL, -- Need M sl-ZoneConfig-r16 SL-ZoneConfig-r16 OPTIONAL, -- Need M ... } SL-SyncAllowed-r16 ::= SEQUENCE { gnss-Sync-r16 ENUMERATED {true} OPTIONAL, -- Need R gnbEnb-Sync-r16 ENUMERATED {true} OPTIONAL, -- Need R ue-Sync-r16 ENUMERATED {true} OPTIONAL -- Need R } SL-PSCCH-Config-r16 ::= SEQUENCE { sl-TimeResourcePSCCH-r16 ENUMERATED {n2, n3} OPTIONAL, -- Need M sl-FreqResourcePSCCH-r16 ENUMERATED {n10,n12, n15, n20, n25} OPTIONAL, -- Need M sl-DMRS-ScrambleID-r16 INTEGER (0..65535) OPTIONAL, -- Need M sl-NumReservedBits-r16 INTEGER (2..4) OPTIONAL, -- Need M ... } SL-PSSCH-Config-r16 ::= SEQUENCE { sl-PSSCH-DMRS-TimePatternList-r16 SEQUENCE (SIZE (1..3)) OF INTEGER (2..4) OPTIONAL, -- Need M sl-BetaOffsets2ndSCI-r16 SEQUENCE (SIZE (4)) OF SL-BetaOffsets-r16 OPTIONAL, -- Need M sl-Scaling-r16 ENUMERATED {f0p5, f0p65, f0p8, f1} OPTIONAL, -- Need M ... } SL-PSFCH-Config-r16 ::= SEQUENCE { sl-PSFCH-Period-r16 ENUMERATED {sl0, sl1, sl2, sl4} OPTIONAL, -- Need M sl-PSFCH-RB-Set-r16 BIT STRING (SIZE (10..275)) OPTIONAL, -- Need M sl-NumMuxCS-Pair-r16 ENUMERATED {n1, n2, n3, n6} OPTIONAL, -- Need M sl-MinTimeGapPSFCH-r16 ENUMERATED {sl2, sl3} OPTIONAL, -- Need M sl-PSFCH-HopID-r16 INTEGER (0..1023) OPTIONAL, -- Need M sl-PSFCH-CandidateResourceType-r16 ENUMERATED {startSubCH, allocSubCH} OPTIONAL, -- Need M ... } SL-PTRS-Config-r16 ::= SEQUENCE { sl-PTRS-FreqDensity-r16 SEQUENCE (SIZE (2)) OF INTEGER (1..276) OPTIONAL, -- Need M sl-PTRS-TimeDensity-r16 SEQUENCE (SIZE (3)) OF INTEGER (0..29) OPTIONAL, -- Need M sl-PTRS-RE-Offset-r16 ENUMERATED {offset01, offset10, offset11} OPTIONAL, -- Need M ... } SL-UE-SelectedConfigRP-r16 ::= SEQUENCE { sl-CBR-PriorityTxConfigList-r16 SL-CBR-PriorityTxConfigList-r16 OPTIONAL, -- Need M sl-Thres-RSRP-List-r16 SL-Thres-RSRP-List-r16 OPTIONAL, -- Need M sl-MultiReserveResource-r16 ENUMERATED {enabled} OPTIONAL, -- Need M sl-MaxNumPerReserve-r16 ENUMERATED {n2, n3} OPTIONAL, -- Need M sl-SensingWindow-r16 ENUMERATED {ms100, ms1100} OPTIONAL, -- Need M sl-SelectionWindowList-r16 SL-SelectionWindowList-r16 OPTIONAL, -- Need M sl-ResourceReservePeriodList-r16 SEQUENCE (SIZE (1..16)) OF SL-ResourceReservePeriod-r16 OPTIONAL, -- Need M sl-RS-ForSensing-r16 ENUMERATED {pscch, pssch}, ..., [[ sl-CBR-PriorityTxConfigList-v1650 SL-CBR-PriorityTxConfigList-v1650 OPTIONAL -- Need M ]], [[ sl-NRPSSCH-EUTRA-ThresRSRP-List-r18 SL-Thres-RSRP-List-r16 OPTIONAL, -- Need M sl-NRPSFCH-EUTRA-ThresRSRP-List-r18 SL-Thres-RSRP-List-r16 OPTIONAL -- Need M ]] } SL-ResourceReservePeriod-r16 ::= CHOICE { sl-ResourceReservePeriod1-r16 ENUMERATED {ms0, ms100, ms200, ms300, ms400, ms500, ms600, ms700, ms800, ms900, ms1000}, sl-ResourceReservePeriod2-r16 INTEGER (1..99) } SL-SelectionWindowList-r16 ::= SEQUENCE (SIZE (8)) OF SL-SelectionWindowConfig-r16 SL-SelectionWindowConfig-r16 ::= SEQUENCE { sl-Priority-r16 INTEGER (1..8), sl-SelectionWindow-r16 ENUMERATED {n1, n5, n10, n20} } SL-TxPercentageList-r16 ::= SEQUENCE (SIZE (8)) OF SL-TxPercentageConfig-r16 SL-TxPercentageConfig-r16 ::= SEQUENCE { sl-Priority-r16 INTEGER (1..8), sl-TxPercentage-r16 ENUMERATED {p20, p35, p50} } SL-MinMaxMCS-List-r16 ::= SEQUENCE (SIZE (1..3)) OF SL-MinMaxMCS-Config-r16 SL-MinMaxMCS-Config-r16 ::= SEQUENCE { sl-MCS-Table-r16 ENUMERATED {qam64, qam256, qam64LowSE}, sl-MinMCS-PSSCH-r16 INTEGER (0..27), sl-MaxMCS-PSSCH-r16 INTEGER (0..31) } SL-BetaOffsets-r16 ::= INTEGER (0..31) SL-PowerControl-r16 ::= SEQUENCE { sl-MaxTransPower-r16 INTEGER (-30..33), sl-Alpha-PSSCH-PSCCH-r16 ENUMERATED {alpha0, alpha04, alpha05, alpha06, alpha07, alpha08, alpha09, alpha1} OPTIONAL, -- Need M dl-Alpha-PSSCH-PSCCH-r16 ENUMERATED {alpha0, alpha04, alpha05, alpha06, alpha07, alpha08, alpha09, alpha1} OPTIONAL, -- Need S sl-P0-PSSCH-PSCCH-r16 INTEGER (-16..15) OPTIONAL, -- Need S dl-P0-PSSCH-PSCCH-r16 INTEGER (-16..15) OPTIONAL, -- Need M dl-Alpha-PSFCH-r16 ENUMERATED {alpha0, alpha04, alpha05, alpha06, alpha07, alpha08, alpha09, alpha1} OPTIONAL, -- Need S dl-P0-PSFCH-r16 INTEGER (-16..15) OPTIONAL, -- Need M ..., [[ dl-P0-PSSCH-PSCCH-r17 INTEGER (-202..24) OPTIONAL, -- Need M sl-P0-PSSCH-PSCCH-r17 INTEGER (-202..24) OPTIONAL, -- Need S dl-P0-PSFCH-r17 INTEGER (-202..24) OPTIONAL -- Need M ]] } SL-PRS-ResourceSharedSL-PRS-RP-r18::= SEQUENCE { sl-PRS-ResourceID-r18 INTEGER (0..16) OPTIONAL, -- Need M mNumberOfSymbols-r18 INTEGER (1..9) OPTIONAL, -- Need M nCombSize-r18 ENUMERATED{n2,n4,n6} OPTIONAL, -- Need M sl-PRS-starting-symbol-r18 INTEGER (4..12) OPTIONAL, -- Need M sl-PRS-comb-offset-r18 INTEGER(1..5) OPTIONAL -- Need M } -- TAG-SL-RESOURCEPOOL-STOP -- ASN1STOP Editor's note: The value range of sl-PSFCH-PowerOffset may need to be updated based on RAN4 reply LS. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
6,612 | 7 Security for non-3GPP access to the 5G core network 7.1 General | Security for non-3GPP access to the 5G Core network is achieved by a procedure using IKEv2 as defined in RFC 7296 [25] to set up one or more IPsec ESP [4] security associations. The role of IKE initiator (or client) is taken by the UE, and the role of IKE responder (or server) is taken by the N3IWF. During this procedure, the AMF delivers a key KN3IWF to the N3IWF. The AMF derives the key KN3IWF from the key KAMF. The key KN3IWF is then used by UE and N3IWF to complete authentication within IKEv2. Security for trusted non-3GPP access to 5G Core network is defined in clause 7A. Trusted and untrusted Non-3GPP Access Networks are IP access networks that use access technology whose specification is out of the scope of 3GPP. Whether a non-3GPP IP access network is trusted or untrusted is not a characteristic of the access network. In non-roaming scenario it is the HPLMN's operator decision if a non-3GPP IP access network is used as trusted or untrusted non-3GPP access Network. When one or more of the security feature groups provided by the non-3GPP access network are considered not sufficiently secure by the home operator, the non-3GPP access may be identified as an untrusted non-3GPP access for that operator. However, this policy decision may additionally be based on reasons not related to security feature groups. In roaming scenario, the UDM in HPLMN makes the final decision of whether a non-3GPP IP access network is used as trusted or untrusted non-3GPP access network based on the identities of the access network and the visited network. The UDM may take the VPLMN's policy and capability returned from the AMF or roaming agreement into account For supporting multiple DNs, the same trust relationship shall apply to all the DNs the UE connects to from a certain non-3GPP access network, i.e. it shall not be possible to access one DN using the non-3GPP access network as trusted, while access to another PDN using the same non-3GPP access network as untrusted. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 7 |
6,613 | 5.4.2.2 HARQ process | Each HARQ process is associated with a HARQ buffer. For synchronous HARQ, each HARQ process shall maintain a state variable CURRENT_TX_NB, which indicates the number of transmissions that have taken place for the MAC PDU currently in the buffer, and a state variable HARQ_FEEDBACK, which indicates the HARQ feedback for the MAC PDU currently in the buffer. When the HARQ process is established, CURRENT_TX_NB shall be initialized to 0. The sequence of redundancy versions is 0, 2, 3, 1. The variable CURRENT_IRV is an index into the sequence of redundancy versions. This variable is up-dated modulo 4. For serving cells configured with pusch-EnhancementsConfig, BL UEs or UEs in enhanced coverage see clause 8.6.1 in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [2] for the sequence of redundancy versions and redundancy version determination. For NB-IoT UEs see clause 16.5.1.2 in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [2] for the sequence of redundancy versions and redundancy version determination. For an SPS configuration with totalNumberPUSCH-SPS-STTI-UL-Repetitions or totalNumberPUSCH-SPS-UL-Repetitions (TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8]), the redundancy version for each transmission within a bundle are determined by rv-SPS-STTI-UL-Repetitions or rv-SPS-UL-Repetitions in the SPS configuration (TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8]). For NB-IoT UEs, BL UEs or UEs in enhanced coverage for UL_REPETITION_NUMBER for Mode B operation, the same redundancy version is used multiple times before cycling to the next redundancy version as specified in clauses 16.5.1.2, 8.6.1 and 7.1.7.1 in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [2]. New transmissions are performed on the resource and with the MCS indicated on PDCCH or Random Access Response. Adaptive retransmissions are performed on the resource and, if provided, with the MCS indicated on PDCCH. Non-adaptive retransmission is performed on the same resource and with the same MCS as was used for the last made transmission attempt. For synchronous HARQ, the MAC entity is configured with a maximum number of HARQ transmissions and a maximum number of Msg3 HARQ transmissions by RRC: maxHARQ-Tx and maxHARQ-Msg3Tx respectively. For transmissions on all HARQ processes and all logical channels except for transmission of a MAC PDU stored in the Msg3 buffer, the maximum number of transmissions shall be set to maxHARQ-Tx. For transmission of a MAC PDU stored in the Msg3 buffer, the maximum number of transmissions shall be set to maxHARQ-Msg3Tx. For autonomous HARQ, each HARQ process shall maintain a state variable HARQ_FEEDBACK, which indicates the HARQ feedback for the MAC PDU currently in the buffer, and a timer aul-RetransmissionTimer which prohibits new transmission or retransmission for the same HARQ process on the configured autonomous uplink when the timer is running. When the HARQ feedback is received for this TB, the HARQ process shall: - set HARQ_FEEDBACK to the received value; - if running, stop the aul-RetransmissionTimer. When an uplink grant addressed to C-RNTI is received for this HARQ process and if the UL HARQ operation is autonomous, the HARQ process shall: - if running, stop the aul-RetransmissionTimer. When PUSCH transmission is performed for this TB and if the uplink grant is a configured grant for the MAC entity's AUL C-RNTI, the HARQ process shall: - start or restart the aul-RetransmissionTimer. If the HARQ entity requests a new transmission, the HARQ process shall: - if UL HARQ operation is synchronous: - set CURRENT_TX_NB to 0; - set HARQ_FEEDBACK to NACK; - set CURRENT_IRV to 0; - else: - if UL HARQ operation is autonomous asychronous: - set HARQ_FEEDBACK to NACK. - if the uplink grant was addressed to the AUL C-RNTI: - set CURRENT_IRV to 0. - else: - set CURRENT_IRV to the index corresponding to the redundancy version value provided in the HARQ information; - store the MAC PDU in the associated HARQ buffer; - store the uplink grant received from the HARQ entity; - generate a transmission as described below. If the HARQ entity requests a retransmission, the HARQ process shall: - if UL HARQ operation is synchronous: - increment CURRENT_TX_NB by 1; - if the HARQ entity requests an adaptive retransmission: - store the uplink grant received from the HARQ entity; - set CURRENT_IRV to the index corresponding to the redundancy version value provided in the HARQ information; - if UL HARQ operation is synchronous; or - if UL HARQ operation is autonomous: - set HARQ_FEEDBACK to NACK; - generate a transmission as described below. - else if the HARQ entity requests a non-adaptive retransmission: - if UL HARQ operation is asynchronous or HARQ_FEEDBACK = NACK: - if both skipUplinkTxSPS and fixedRV-NonAdaptive are configured and the uplink grant of the initial transmission of this HARQ process was performed on a configured grant and UL HARQ operation is not autonomous; or - if the uplink grant is a preallocated uplink grant: - set CURRENT_IRV to 0; - else if UL HARQ operation is autonomous: - set CURRENT_IRV to the index corresponding to the redundancy version value selected by the UE implementation. - generate a transmission as described below. NOTE 1: When receiving a HARQ ACK alone, the MAC entity keeps the data in the HARQ buffer. NOTE 2: When no UL-SCH transmission can be made due to the occurrence of a measurement gap or a Sidelink Discovery Gap for Transmission, or prioritization of V2X sidelink communication transmission described in clause 5.14.1.2.2, no HARQ feedback can be received and a non-adaptive retransmission follows. NOTE 3: For asynchronous HARQ operation, UL retransmissions are triggered only by adaptive retransmission grants, except for retransmissions within a bundle. To generate a transmission, the HARQ process shall: - if the MAC PDU was obtained from the Msg3 buffer; or - if Sidelink Discovery Gaps for Transmission are not configured by upper layers, and there is no measurement gap at the time of the transmission and, in case of retransmission, the retransmission does not collide with a transmission for a MAC PDU obtained from the Msg3 buffer in this TTI; or - if Sidelink Discovery Gaps for Transmission are configured by upper layers, and there is no measurement gap at the time of the transmission and, in case of retransmission, the retransmission does not collide with a transmission for a MAC PDU obtained from the Msg3 buffer, and there is no Sidelink Discovery Gap for Transmission in this TTI; or - if Sidelink Discovery Gaps for Transmission are configured by upper layers, and there is no measurement gap at the time of the transmission and, in case of retransmission, the retransmission does not collide with a transmission for a MAC PDU obtained from the Msg3 buffer, and there is a Sidelink Discovery Gap for Transmission, and there is no configured grant for transmission on SL-DCH in this TTI: - if there is neither transmission of V2X sidelink communication on SL-SCH nor transmission of NR sidelink communication in this TTI; or - if the transmission of the MAC PDU is prioritized over sidelink transmission: - instruct the physical layer to generate a transmission according to the stored uplink grant with the redundancy version corresponding to the CURRENT_IRV value; - increment CURRENT_IRV by 1 if UL HARQ operation is not autonomous; - if UL HARQ operation is synchronous and there is a measurement gap or Sidelink Discovery Gap for Reception at the time of the HARQ feedback reception for this transmission and if the MAC PDU was not obtained from the Msg3 buffer: - set HARQ_FEEDBACK to ACK at the time of the HARQ feedback reception for this transmission. After performing above actions, if UL HARQ operation is synchronous the HARQ process then shall: - if CURRENT_TX_NB = maximum number of transmissions – 1: - flush the HARQ buffer; The transmission of the MAC PDU is prioritized over sidelink transmission or can be performed simultaneously with sidelink transmission if one of the following conditions is met: - if there are both a configured grant for transmission of V2X sidelink communication on SL-SCH in this TTI and a sidelink grant for transmission of NR sidelink communication as described in clause 5.22.1.1 of TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [24] at the time of the transmission, and neither the transmissions of V2X sidelink communication is prioritized as described in clause 5.14.1.2.2 nor the transmission of NR sidelink communication is prioritized as described in clause 5.22.1.3.1a of TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [24]; or - if there are both a configured grant for transmission of V2X sidelink communication on SL-SCH in this TTI and a sidelink grant for transmission of NR sidelink communication as described in clause 5.22.1.1 of TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [24] at the time of the transmission, and the MAC entity is able to perform this UL transmission simultaneously with the transmissions of V2X sidelink communication and/or the transmission of NR sidelink communication; or - if there is only configured grant(s) for transmission of V2X sidelink communication on SL-SCH in this TTI, and either none of the transmissions of V2X sidelink communication is prioritized or the MAC entity is able to perform this UL transmission and the transmissions of V2X sidelink communication simultaneously; or - if there is only a sidelink grant for transmission of NR sidelink communication in this TTI as described in clause 5.22.1.1 of TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [24], and either no transmission of NR sidelink communication is prioritized as described in clause 5.22.1.3.1a of TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [24] or the MAC entity is able to perform this UL transmission simultaneously with the transmission of NR sidelink communication; or - if there are both a configured grant for transmission of V2X sidelink communication on SL-SCH in this TTI and a sidelink grant for transmission of NR sidelink communication as described in clause 5.22.1.1 of TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [24] at the time of the transmission, and either only the transmissions of V2X sidelink communication is prioritized as described in clause 5.14.1.2.2 or only the transmission of NR sidelink communication is prioritized as described in clause 5.22.1.3.1a of TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [24] and the MAC entity is able to perform this UL transmission simultaneously with the prioritized transmission of V2X sidelink communication or NR sidelink communication. NOTE 4: Among the UL transmissions where the MAC entity is able to perform all transmissions of V2X sidelink communication prioritized simultaneously, if there are more than one UL transmission which the MAC entity is not able to perform simultaneously, it is up to UE implementation whether this UL transmission is performed. NOTE 5: Among the UL transmissions that the MAC entity is able to perform simultaneously with the transmission of NR sidelink communication prioritized, if there are more than one UL transmission which the MAC entity is not able to perform simultaneously, it is up to UE implementation whether this UL transmission is performed. NOTE 6: Among the UL transmissions where the MAC entity is able to perform all transmissions of V2X sidelink communication prioritized simultaneously with the transmission of NR sidelink communication prioritized, if there are more than one UL transmission which the MAC entity is not able to perform simultaneously, it is up to UE implementation whether this UL transmission is performed. NOTE 7: If there is a sidelink grant for transmission of NR sidelink communication in this TTI as described in clause 5.22.1.1 of TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [24] and the MAC entity is not able to perform this UL transmission simultaneously with the transmission of NR sidelink communication, and prioritization-related information is not available prior to the time of the transmission due to processing time restriction, it is up to UE implementation whether this UL transmission is performed. | 3GPP TS 36.321 | Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification | RAN2 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 5.4.2.2 |
6,614 | 12.1 Overview | The 5G QoS model is based on QoS Flows (see TS 23.501[ System architecture for the 5G System (5GS) ] [3]) and supports both QoS Flows that require guaranteed flow bit rate (GBR QoS Flows) and QoS Flows that do not require guaranteed flow bit rate (non-GBR QoS Flows). At NAS level (see TS 23.501[ System architecture for the 5G System (5GS) ] [3]), the QoS flow is thus the finest granularity of QoS differentiation in a PDU session. A QoS flow is identified within a PDU session by a QoS Flow ID (QFI) carried in an encapsulation header over NG-U. The QoS architecture in NG-RAN, both for NR connected to 5GC and for E-UTRA connected to 5GC, is depicted in the Figure 12-1 and described in the following: - For each UE, 5GC establishes one or more PDU Sessions; - Except for NB-IoT, IAB-MT in SA mode, and NCR-MT, for each UE, the NG-RAN establishes at least one Data Radio Bearers (DRB) together with the PDU Session and additional DRB(s) for QoS flow(s) of that PDU session can be subsequently configured (it is up to NG-RAN when to do so); - If NB-IoT UE supports NG-U data transfer, the NG-RAN may establish Data Radio Bearers (DRB) together with the PDU Session and one PDU session maps to only one DRB; - The NG-RAN maps packets belonging to different PDU sessions to different DRBs; - NAS level packet filters in the UE and in the 5GC associate UL and DL packets with QoS Flows; - AS-level mapping rules in the UE and in the NG-RAN associate UL and DL QoS Flows with DRBs. Figure 12-1: QoS architecture NG-RAN and 5GC ensure quality of service (e.g. reliability and target delay) by mapping packets to appropriate QoS Flows and DRBs. Hence there is a 2-step mapping of IP-flows to QoS flows (NAS) and from QoS flows to DRBs (Access Stratum). At NAS level, a QoS flow is characterised by a QoS profile provided by 5GC to NG-RAN and QoS rule(s) provided by 5GC to the UE. The QoS profile is used by NG-RAN to determine the treatment on the radio interface while the QoS rules dictates the mapping between uplink User Plane traffic and QoS flows to the UE. A QoS flow may either be GBR or Non-GBR depending on its profile. The QoS profile of a QoS flow contains QoS parameters, for instance (see TS 23.501[ System architecture for the 5G System (5GS) ] [3]): - For each QoS flow: - A 5G QoS Identifier (5QI); - An Allocation and Retention Priority (ARP). - In case of a GBR QoS flow only: - Guaranteed Flow Bit Rate (GFBR) for both uplink and downlink; - Maximum Flow Bit Rate (MFBR) for both uplink and downlink; - Maximum Packet Loss Rate for both uplink and downlink; - Delay Critical Resource Type; - Notification Control. NOTE: The Maximum Packet Loss Rate (UL, DL) is only provided for a GBR QoS flow belonging to voice media. - In case of Non-GBR QoS only: - Reflective QoS Attribute (RQA): the RQA, when included, indicates that some (not necessarily all) traffic carried on this QoS flow is subject to reflective quality of service (RQoS) at NAS; - Additional QoS Flow Information. The QoS parameter Notification Control indicates whether notifications are requested from the RAN when the GFBR can no longer (or again) be fulfilled for a QoS Flow. If, for a given GBR QoS Flow, notification control is enabled and the RAN determines that the GFBR cannot be guaranteed, RAN shall send a notification towards SMF and keep the QoS Flow (i.e. while the NG-RAN is not delivering the requested GFBR for this QoS Flow), unless specific conditions at the NG-RAN require the release of the NG-RAN resources for this GBR QoS Flow, e.g. due to Radio link failure or RAN internal congestion. When applicable, NG-RAN sends a new notification, informing SMF that the GFBR can be guaranteed again. If Alternative QoS parameters Sets are received with the Notification Control parameter, the NG-RAN may also include in the notification a reference corresponding to the QoS Parameter Set which it can currently fulfil as specified in TS 23.501[ System architecture for the 5G System (5GS) ] [3]. The target NG-RAN node may include in the notification control indication the reference to the QoS Parameter Set which it can currently fulfil over Xn to the source NG-RAN node during handover. In addition, an Aggregate Maximum Bit Rate is associated to each PDU session (Session-AMBR), to each UE (UE-AMBR) and to each slice per UE (UE-Slice-MBR). The Session-AMBR limits the aggregate bit rate that can be expected to be provided across all Non-GBR QoS Flows for a specific PDU Session and is ensured by the UPF. The UE-AMBR limits the aggregate bit rate that can be expected to be provided across all Non-GBR QoS Flows of a UE and is ensured by the RAN (see clause 10.5.1). The UE-Slice-MBR limits the aggregate bit rate that can be expected to be provided across all GBR and Non-GBR QoS Flows corresponding to PDU Sessions of the UE for the same slice (S-NSSAI) as specified in TS 23.501[ System architecture for the 5G System (5GS) ] [3] and is ensured by the RAN (see clause 10.5.1). The 5QI is associated to QoS characteristics giving guidelines for setting node specific parameters for each QoS Flow. Standardized or pre-configured 5G QoS characteristics are derived from the 5QI value and are not explicitly signalled. Signalled QoS characteristics are included as part of the QoS profile. The QoS characteristics consist for instance of (see TS 23.501[ System architecture for the 5G System (5GS) ] [3]): - Priority level; - Packet Delay Budget (including Core Network Packet Delay Budget); - Packet Error Rate; - Averaging window; - Maximum Data Burst Volume. At Access Stratum level, the data radio bearer (DRB) defines the packet treatment on the radio interface (Uu). A DRB serves packets with the same packet forwarding treatment. The QoS flow to DRB mapping by NG-RAN is based on QFI and the associated QoS profiles (i.e. QoS parameters and QoS characteristics). Separate DRBs may be established for QoS flows requiring different packet forwarding treatment, or several QoS Flows belonging to the same PDU session can be multiplexed in the same DRB. In the uplink, the mapping of QoS Flows to DRBs is controlled by mapping rules which are signalled in two different ways: - Reflective mapping: for each DRB, the UE monitors the QFI(s) of the downlink packets and applies the same mapping in the uplink; that is, for a DRB, the UE maps the uplink packets belonging to the QoS flows(s) corresponding to the QFI(s) and PDU Session observed in the downlink packets for that DRB. To enable this reflective mapping, the NG-RAN marks downlink packets over Uu with QFI. - Explicit Configuration: QoS flow to DRB mapping rules can be explicitly signalled by RRC. The UE always applies the latest update of the mapping rules regardless of whether it is performed via reflecting mapping or explicit configuration. When a QoS flow to DRB mapping rule is updated, the UE sends an end marker on the old bearer. In the downlink, the QFI is signalled by NG-RAN over Uu for the purpose of RQoS and if neither NG-RAN, nor the NAS (as indicated by the RQA) intend to use reflective mapping for the QoS flow(s) carried in a DRB, no QFI is signalled for that DRB over Uu. In the uplink, NG-RAN can configure the UE to signal QFI over Uu. For each PDU session, a default DRB may be configured: if an incoming UL packet matches neither an RRC configured nor a reflective mapping rule, the UE then maps that packet to the default DRB of the PDU session. For non-GBR QoS flows, the 5GC may send to the NG-RAN the Additional QoS Flow Information parameter associated with certain QoS flows to indicate that traffic is likely to appear more often on them compared to other non-GBR QoS flows established on the same PDU session. Within each PDU session, it is up to NG-RAN how to map multiple QoS flows to a DRB. The NG-RAN may map a GBR flow and a non-GBR flow, or more than one GBR flow to the same DRB, but mechanisms to optimise these cases are not within the scope of standardization. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 12.1 |
6,615 | 5 Layer 1 related aspects | In MR-DC, two or more Component Carriers (CCs) may be aggregated over two cell groups. A UE may simultaneously receive or transmit on multiple CCs depending on its capabilities. The maximum number of configured CCs for a UE is 32 for DL and UL. Depending on UE's capabilities, up to 31 CCs can be configured for an E-UTRA cell group when the NR cell group is configured. For the NR cell group, the maximum number of configured CCs for a UE is 16 for DL and 16 for UL. A gNB may configure the same Physical Cell ID (PCI) to more than one NR cell it serves. To avoid PCI confusion for MR-DC, NR PCIs should be allocated in a way that an NR cell is uniquely identifiable by a PCell identifier. This PCell is in the coverage area of an NR cell included in the MR-DC operation. In addition, NR PCIs should only be re-used in NR cells on the same SSB frequency sufficiently distant from each other. X2-C/Xn-C signalling supports disambiguation of NR PCIs by including the CGI of the PCell in respective X2AP/XnAP messages (e.g. SGNB ADDITION REQUEST/S-NODE ADDITION REQUEST) and by providing neighbour cell relationship via non-UE associated signaling (e.g. via the Xn Setup procedure or the NG-RAN node Configuration Update procedure). NR-DC supports the case of no synchronization between PCell and PSCell. However, some UEs may support NR-DC only if slot-level synchronization between PCell and PSCell is ensured. In MR-DC, power sharing can be performed within a frequency range with either semi-static or dynamic power sharing. With semi-static power sharing, the maximum UE transmission power is semi-statically split between MCG and SCG by RRC configuration. With dynamic power sharing: - when determining the UL transmission power of an SCG transmission in (NG)EN-DC or in NR-DC, the UE takes into account transmission(s) on MCG overlapping with any part of the SCG transmission; - when determining the UL transmission power of an MCG transmission in NE-DC, the UE takes into account transmission(s) on SCG overlapping with any part of the MCG transmission. Details are specified in TS38.213[21]. In EN-DC, a UE configured with uplink Tx switching can have Tx dynamically switched between E-UTRA uplink carrier and NR uplink carrier for enabling 2Tx UL transmission on NR carrier. | 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 | 5 |
6,616 | 4.15.3.2.5 Information flow for downlink data delivery status with SMF buffering | The procedure is used if the SMF requests the UPF to forward downlink data packets that are subject of extended buffering in the SMF. The procedure describes a mechanism for the Application Function to subscribe downlink data delivery status notifications. The downlink data delivery status notifications relates to high latency communication, see also clauses 4.24.2 and 4.2.3.3. Cancelling the subscription is done by sending Nnef_EventExposure_Unsubscribe request identifying the subscription to cancel with Subscription Correlation ID in the same order as indicated in figure 4.15.3.2.5-1 for the corresponding subscribe requests. Step 0 and the notification steps 7 to 9 are not applicable in cancellation case. Figure 4.15.3.2.5-1: Information flow for downlink data delivery status with SMF buffering 0. The SMF (in the non-roaming case the 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 downlink data packets towards 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 3, 1. The AF sends Nnef_EventExposure_Subscribe Request to NEF requesting notification for event "Downlink data delivery status" with traffic descriptor (e.g. the source of the downlink IP or Ethernet traffic) for a UE or group of UEs. If the reporting event subscription is authorized by the NEF, the NEF records the association of the event trigger and the requester identity. The Downlink data delivery status events include: - First downlink Packet in extended buffering event: - This event is triggered when the first new downlink data packet is buffered with extended buffering matching the traffic descriptor. - in notifications about this Downlink data delivery status, the SMF provides the Extended Buffering time as determined in clause 4.2.3.3. - First downlink Packet discarded: - This event occurs when the first packet matching the traffic descriptor is discarded because the Extended Buffering time, as determined by the SMF, expires or the amount of downlink data to be buffered is exceeded. - First Downlink Packet transmitted: - This event occurs when the first packet matching the traffic descriptor is transmitted after previous buffering or discarding of corresponding packet(s) because the UE of the PDU Session becomes ACTIVE and buffered data can be delivered to UE according to clause 4.2.3.3. 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 in 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 5 indicating failure. 3. The UDM sends the Nsmf_EventExposure_Subscribe Request message to each SMF where at least one UE identified in step 2 has a PDU session established. If the UDM is able to derive the applicable DNN and S-NSSAI from the traffic descriptor via configured information, the UDM may send Nsmf_EventExposure_Subscribe Request messages only to SMFs with PDU sessions with that DNN and S-NSSAI for such UEs and includes the Identifier of the UE or Internal-Group-Id, traffic descriptor, monitoring event and the notification endpoint of NEF received in step 2 are included in the message. If the UDM becomes aware that such a UE has a PDU session established with the DNN and S-NSSAI corresponding to the traffic descriptor at a later time than when receiving step 2, the UDM then executes step 3. In the case of home-routed PDU session or PDU session with I-SMF, the UDM sends the Nsmf_EventExposure_Subscribe Request message to each H-SMF or SMF and the H-SMF or SMF further sends Nsmf_EventExposure_Subscribe Request message to each related V-SMF or I-SMF. Steps 7-8 are performed by V-SMF or I-SMF. 4. The SMF sends the Nsmf_EventExposure_Subscribe Response message to the UDM. 5. The UDM send sends the Nsmf_EventExposure_Subscribe response message to the NEF. 6. The NEF sends the Nsmf_EventExposure_Subscribe response to the AF. 7. The SMF detects a change in Downlink Data Delivery Status event as described in clause 4.2.3. The SMF becomes aware that Downlink Packet(s) require extended buffering via a Namf_Communication_N1N2MessageTransfer service operation with the AMF. If the SMF decides to discard packets, the "Downlink Packet(s) discarded event" is detected. The SMF detects that previously buffered packets can be transmitted by the fact that the related PDU session becomes ACTIVE. 8. The SMF sends the Nsmf_EventExposure_Notify with Downlink Delivery Status event message to NEF. 9. The NEF sends Nnef_EventExposure_Notify with Downlink Delivery Status event message 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.5 |
6,617 | 8.4.1.2.8 Enhanced Downlink Control Channel Performance Requirement Type B - 2 Tx Antenna Port with Non-Colliding CRS Dominant Interferer | The purpose of this test is to verify the Enhanced Downlink Control Channel Performance Requirement Type B for PDCCH/PCFICH with 2 transmit antennas for the case of dominant interferer with the non-colliding CRS pattern and applying interference model defined in clause B.7.1. For the parameters specified in Table 8.4.1-1 and Table 8.4.1.2.8-1, the average probability of a missed downlink scheduling grant (Pm-dsg) shall be below the specified value in Table 8.4.1.2.8-2. In Table 8.4.1.2.8-1, Cell 1 is the serving cell, and Cell 2 and Cell 3 are the agressor cells. The downlink physical channel setup is according to Annex C.3.2 for each of Cell 1, Cell 2 and Cell 3, respectively. The CRS assistance information [7] is provided and includes Cell 2 and Cell 3. Table 8.4.1.2.8-1: Test Parameters for PDCCH/PCFICH Table 8.4.1.2.8-2: Minimum Performance for PDCCH/PCFICH for Enhanced Downlink Control Channel Performance Requirement Type B | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.4.1.2.8 |
6,618 | 11.3 Timers of circuit-switched call control | Table 11.3/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Call control timers - MS side NOTE 1: T310 is not started if progress indicator #1, #2, or #64 has been delivered in the CALL PROCEEDING message or in a previous PROGRESS message. NOTE 2: The value of this timer is implementation dependent. Table 11.4/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Call control timers - network side NOTE 1: The network may already have applied an internal alerting supervision function; e.g. incorporated within call control. If such a function is known to be operating on the call, then timer T301 is not used. NOTE 2: These time values are set by the network operator. NOTE 3: When applied to the supplementary service CCBS, the timer T334 can either represent the recall timer T4 or the notification timer T10 (see 3GPP TS 23.093[ Technical realization of Completion of Calls to Busy Subscriber (CCBS); Stage 2 ] [88a]). Thus the timer T334 can take two different values. 3GPP TS 23.093[ Technical realization of Completion of Calls to Busy Subscriber (CCBS); Stage 2 ] [88a] defines the range of these values. | 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 | 11.3 |
6,619 | 6.3.12a Access Network selection for devices that do not support 5GC NAS over WLAN 6.3.12a.1 General | As specified in clause 4.2.8.5, devices that do not support 5GC NAS signalling over WLAN access (referred to as "Non-5G-Capable over WLAN" devices, or N5CW devices for short), may access 5GC in a PLMN or an SNPN via a trusted WLAN access network that supports a TWIF function. The following clause specifies (a) how a N5CW device selects a PLMN and (b) how it selects a trusted WLAN access network that can provide "5G connectivity-without-NAS" to the selected PLMN. This selection procedure is called access network selection. NOTE: For N5CW device accessing an SNPN refer to clause 5.30.2.15. Each WLAN access network that provides "5G connectivity-without-NAS" advertises with ANQP a list of PLMNs with which "5G connectivity-without-NAS" is supported. This list is called PLMN List-4, and is different from the PLMN List-1, PLMN List-2 and PLMN List-3 defined in clause 6.3.12. A WLAN advertises the PLMN List-4, when the WLAN supports a TWIF function. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 6.3.12a |
6,620 | 8.9.5 Change of gNB-CU-UP | Figure 8.9.5-1 shows the procedure used for the change of gNB-CU-UP within a gNB. Figure 8.9.5-1: Change of gNB-CU-UP 1. Change of gNB-CU-UP is triggered in gNB-CU-CP based on e.g., measurement report from the UE. 2-3. Bearer Context Setup procedure is performed as described in clause 8.9.2. 4. F1 UE Context Modification procedure is performed to change the UL TNL address information for F1-U for one or more bearers in the gNB-DU. 5-6. Bearer Context Modification procedure (gNB-CU-CP initiated) is performed to enable the gNB-CU-CP to retrieve the PDCP UL/DL status and to exchange data forwarding information for the bearer. 7-8. Bearer Context Modification procedure is performed as described in clause 8.9.2. 9. Data Forwarding may be performed from the source gNB-CU-UP to the target gNB-CU-UP. 10-12. PDU Session Resource Modify Indication procedure is performed to update the DL TNL address information for the NG-U towards the core network. 13-14. Bearer Context Release procedure (gNB-CU-CP initiated) is performed as described in clause 8.9.3. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 8.9.5 |
6,621 | 7.4.7 Alert MME Acknowledge | An Alert MME Acknowledge message shall be sent as a response to an Alert MME Notification message. Possible Cause values are specified in Table 8.4-1. NOTE: An SGSN implemented according to an earlier version of the specification will silently discard the Alert MME Notification message. An MME which does not receive an Alert MME Acknowledge message may not send further Alert MME Notification message to this SGSN. Table 7.4.7-1 specifies the presence requirements and the conditions of the IEs in the message. Table 7.4.7-1: Information Elements in Alert MME Acknowledge | 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.4.7 |
6,622 | 6.11 Security handling for RRC connection re-establishment procedure | NOTE: This clause applies only to the gNB. Inter-RAT RRC Connection Re-establishment (i.e., between gNB and ng-eNB) is not supported. The RRC Connection Re-establishment procedure for the ng-eNB is specified in TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [10]. The KNG-RAN* and token calculation at handover preparation are cell specific instead of gNB specific. During the handover procedure, at potential RRC connection reestablishment (e.g., in handover failure case), the UE may select a cell different from the target cell to initiate the reestablishment procedure. To ensure that the UE RRC connection re-establishment attempt is successful when the UE selects another cell under the control of the target gNB at handover preparation, the source gNB may prepare multiple KNG-RAN* keys and tokens for multiple cells which are under the control of the target gNB. The source gNB may prepare for multiple cells belonging to the serving gNB itself. The preparation of these cells includes sending security context containing KNG-RAN* keys and tokens for each cell to be prepared, as well as the corresponding NCC, the UE 5G security capabilities, and the security algorithms used in the source cell for computing the token, to the target gNB. The source gNB shall derive the KNG-RAN* keys as described in Annex A.11/A.12 based on the corresponding target cell’s physical cell ID and frequency ARFCN-DL. In order to calculate the token, the source gNB shall use the negotiated NIA-algorithm from the 5G AS Security context from the source gNB with the following inputs: source C-RNTI, source PCI and target Cell-ID, where source PCI and source C-RNTI are associated with the cell the UE last had an active RRC connection with and target Cell-ID is the identity of the target cell where the RRCReestablishmentRequest is sent to. - KEY shall be set to KRRCint of the source cell; - all BEARER bits shall be set to 1; - DIRECTION bit shall be set to 1; - all COUNT bits shall be set to 1. The token shall be the 16 least significant bits of the output of the used integrity algorithm. In order to avoid UE’s inability to perform the RRC re-establishment procedure due to a failure during a handover or a connection re-establishment, the UE shall keep the KgNB used in the source cell until the handover or a connection re-establishment has been completed successfully or until the UE has deleted the KgNB for other reasons (e.g., due to transitioning to CM-IDLE). For Xn handover, the target gNB shall use the received multiple KNG-RAN* keys. But for N2 handover, the target gNB discards the multiple KNG-RAN* keys received from the source gNB, and derives the KNG-RAN* keys as described in Annex A.11/A.12 based on the received fresh {NH, NCC} pair from AMF for forward security purpose. When an RRCReestablishmentRequest is initiated by the UE, the RRCReestablishmentRequest shall contain the token corresponding to the cell the UE tries to reconnect to. This message is transmitted over SRB0 and hence not integrity protected. If the target gNB receiving the RRCReestablishmentRequest has a prepared KNG-RAN* key and token for the specific cell, the target gNB receiving the RRCReestablishmentRequest shall validate the token received in the RRCReestablishmentRequest. However, if the target gNB has not prepared token for the cell, the target gNB extracts the C-RNTI and PCI from the RRCReestablishmentRequest message. The target gNB contacts the source gNB based on PCI by sending an Xn-AP Retrieve UE Context Request message with the following included: C-RNTI, PCI, the token and target Cell-ID, in order to allow the source gNB to validate the UE request and to retrieve the UE context including the UE 5G AS security context. The source gNB retrieves the stored UE context including the UE 5G AS security context from its database using the C-RNTI. The source gNB verifies the token. If the verification is successful, then the source gNB calculates KNG-RAN* using the target cell PCI, target ARFCN-DL and the KgNB/NH in the current UE 5G AS security context based on either a horizontal key derivation or a vertical key derivation according to whether the source gNB has an unused pair of {NCC, NH} as described in Annex A.11. The source gNB can obtain the target PCI and target ARFCN-DL from a cell configuration database by means of the target Cell-ID which was received from the target gNB. Then the source gNB shall respond with an Xn-AP Retrieve UE Context Response message to the target gNB including the UE context that contains the UE 5G AS security context. After successful verification of token by either target gNB or source gNB, the target gNB shall check whether it supports ciphering and integrity algorithms that the UE was using with the last source cell, if supports and these algorithms are the chosen algorithms or they are not the chosen algorithms by the target gNB, the target gNB shall use the KNG-RAN* corresponding to the selected cell as KgNB and derive new RRC keys (new KRRCint and new KRRCenc) based on the KgNB and the AS algorithms used in source cell. Then, the target gNB shall respond with an RRCReestablishment message containing the NCC received during the preparation phase or context fetch phase. This RRCReestablishment message is sent on SRB1 and is integrity protected in PDCP layer using the newly calculated KRRCint. If verification of the token is failed by either target gNB or source gNB, or the target gNB does not support the ciphering and integrity algorithms used in source cell, the target gNB shall reply with an RRCSetup message. The RRCSetup message is sent on SRB0 and hence not integrity protected. Next the target gNB and UE shall do the following: The UE shall firstly synchronize the locally kept NH parameter as defined in Annex A.10 if the received NCC value is different from the current NCC value in the UE itself. Then the UE shall derive KNG-RAN* as described in Annex A.11/A.12 based on the selected cell’s physical cell ID and its frequency ARFCN-DL. The UE shall use this KNG-RAN* as KgNB. The gNB uses the KNG-RAN* corresponding to the selected cell as KgNB. The UE shall derive the new RRC keys from the KgNB and the AS algorithms (ciphering and integrity algorithms) the UE was using with the source cell. The UE shall verify the integrity of the RRCReestablishment message by verifying the PDCP MAC-I using the newly derived KRRCint. NOTE: Void. If the UE successfully validate the integrity of the received RRCReestablishment message, the UE shall respond with an RRCReestablishmentComplete on SRB1 while being integrity protected and ciphered using the new RRC keys. The RRCConnectionReconfiguration procedure used to re-establish the remaining radio bearers shall only include integrity protected and ciphered messages. When the UE receives RRCSetup message, the UE shall perform the RRC connection establishment procedure as if the UE was in RRC_IDLE. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.11 |
6,623 | 5.5.2.3.5 Abnormal cases on the network side | The following abnormal cases can be identified: a) T3422 time-out On the first expiry of the timer, the network shall retransmit the DETACH REQUEST message and shall start timer T3422. This retransmission is repeated four times, i.e. on the fifth expiry of timer T3422, the detach procedure shall be aborted. If the detach type is "IMSI detach", or "re-attach not required" and the EMM cause value is #2 "IMSI unknown in HSS", the network shall not change the current EMM state; otherwise the network shall change to state EMM-DEREGISTERED. b) Lower layer failure The detach procedure is aborted. If the detach type indicates "IMSI detach", or "re-attach not required" and the EMM cause value is #2 "IMSI unknown in HSS", the network shall not change the current EMM state; otherwise the network shall change to state EMM-DEREGISTERED. c) Detach procedure collision If the network receives a DETACH REQUEST message with "switch off" indication, before the network initiated detach procedure has been completed, both procedures shall be considered completed. If the network receives a DETACH REQUEST message without "switch off" indication, before the network initiated detach procedure has been completed, the network shall send a DETACH ACCEPT message to the UE. d) Detach and attach procedure collision If the network receives an ATTACH REQUEST message before the network initiated detach procedure with detach type "re-attach not required" with no EMM cause IE, or "re-attach not required" and the EMM cause value not #2 "IMSI unknown in HSS", has been completed, the network shall ignore the ATTACH REQUEST message. If the Detach type IE, sent in the DETACH REQUEST message, indicates "re-attach required" the detach procedure is aborted and the attach procedure shall be progressed after the EPS bearer context(s) have been deleted. If the Detach type IE, sent in DETACH REQUEST message, indicates "IMSI detach", or "re-attach not required" and the EMM cause value is #2 "IMSI unknown in HSS", the detach procedure is aborted and the attach procedure shall be progressed. e) Detach and tracking area updating procedure collision If the Detach type IE, sent in DETACH REQUEST message, indicates "re-attach not required" with no EMM cause IE, or "re-attach not required" with EMM cause other than #2 "IMSI unknown in HSS" or indicates "re-attach required", and the network receives a TRACKING AREA UPDATE REQUEST message before the network initiated detach procedure has been completed, the detach procedure shall be progressed, i.e. the TRACKING AREA UPDATE REQUEST message shall be ignored. If the Detach type IE, sent in DETACH REQUEST message, indicates "re-attach not required" with EMM cause #2 "IMSI unknown in HSS" or indicates "IMSI detach" and the network receives a TRACKING AREA UPDATE REQUEST message before the network initiated detach procedure has been completed, the network shall abort the detach procedure, shall stop T3422 and shall progress the tracking area updating procedure. f) Detach and service request procedure collision If the network receives a SERVICE REQUEST message or an EXTENDED SERVICE REQUEST message for packet services before the network initiated detach procedure has been completed (e.g. the DETACH REQUEST message is pending to be sent to the UE) and the DETACH REQUEST contains detach type "re-attach not required" with EMM cause #2 "IMSI unknown in HSS" or detach type "IMSI detach", the network shall progress both procedures. If the DETACH REQUEST message contains detach type "re-attach not required" with no EMM cause IE, or "re-attach not required" with EMM cause other than #2 "IMSI unknown in HSS" or detach type "re-attach required", the network shall progress the detach procedure. If the network receives an EXTENDED SERVICE REQUEST message for CS fallback, but not for CS fallback for emergency call, before the network initiated detach procedure has been completed (e.g. the DETACH REQUEST message is pending to be sent to the UE) and the DETACH REQUEST contains detach type "re-attach not required" with EMM cause #2 "IMSI unknown in HSS" or detach type "IMSI detach", the network shall ignore the EXTENDED SERVICE REQUEST message and progress the detach procedure. If the network receives an EXTENDED SERVICE REQUEST message for CS fallback for emergency call before the network initiated detach procedure has been completed (e.g. the DETACH REQUEST message is pending to be sent to the UE) and the DETACH REQUEST contains detach type "re-attach not required" with EMM cause #2 "IMSI unknown in HSS" or detach type "IMSI detach", the network shall progress both procedures. g) Lower layers indication of non-delivered NAS PDU due to handover If the DETACH REQUEST message could not be delivered due to an intra MME handover and the target TA is included in the TAI list, then upon successful completion of the intra MME handover the MME shall retransmit the DETACH REQUEST message. If a failure of the handover procedure is reported by the lower layer and the S1 signalling connection exists, the MME shall retransmit the DETACH REQUEST message. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.5.2.3.5 |
6,624 | – UEAssistanceInformationSidelink | The UEAssistanceInformationSidelink message may include sidelink DRX assistance information used to determine the sidelink DRX configuration. Signalling radio bearer: SL-SRB3 RLC-SAP: AM Logical channel: SCCH Direction: UE to UE UEAssistanceInformationSidelink message -- ASN1START -- TAG-UEASSISTANCEINFORMATIONSIDELINK-START UEAssistanceInformationSidelink-r17 ::= SEQUENCE { criticalExtensions CHOICE { ueAssistanceInformationSidelink-r17 UEAssistanceInformationSidelink-r17-IEs, criticalExtensionsFuture SEQUENCE {} } } UEAssistanceInformationSidelink-r17-IEs ::= SEQUENCE { sl-PreferredDRX-ConfigList-r17 SEQUENCE (SIZE (1..maxNrofSL-RxInfoSet-r17)) OF SL-DRX-ConfigUC-SemiStatic-r17 OPTIONAL, -- Need R lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL } -- TAG-UEASSISTANCEINFORMATIONSIDELINK-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
6,625 | 5.3.20.3 Requirements for UE in an SNPN | If the UE is operating in SNPN access operation mode, the UE shall maintain, for each of the entries in the "list of subscriber data": - one SNPN-specific attempt counter for 3GPP access. The counter is applicable to access attempts via 3GPP access only; - one SNPN-specific attempt counter for non-3GPP access, if the UE supports access to SNPN over non-3GPP access. The counter is applicable in case of access to SNPN over non-3GPP access only; NOTE 1: If the UE accesses to SNPN service directly over non-3GPP access or if the UE accesses to SNPN services via a PLMN, the SNPN-specific attempt counter for non-3GPP access is used. - one counter for "the entry for the current SNPN considered invalid for 3GPP access" events; and - one counter for "the entry for the current SNPN considered invalid for non-3GPP access" events, if the UE supports access to SNPN over non-3GPP access. The counter is applicable in case of access to SNPN over non-3GPP access only. NOTE 2: If the UE accesses to SNPN service directly over non-3GPP access or if the UE accesses to SNPN services via a PLMN, the counter for "the entry for the current SNPN considered invalid for non-3GPP access" events is used.The UE shall store the above counters in its non-volatile memory. The UE shall erase the attempt counters and reset the event counters to zero when the selected entry of the "list of subscriber data" is updated or USIM is removed for the selected PLMN subscription. The counter values shall not be affected by the activation or deactivation of MICO mode or power saving mode (see 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15]). The UE implementation-specific maximum value for any of the above counters shall not be greater than 10. NOTE 3: Different counters can use different UE implementation-specific maximum values. If the UE receives a REGISTRATION REJECT or SERVICE REJECT message without integrity protection with 5GMM cause value #3, #6, #7, #12, #13, #15, #27, #72, #74, or #75 before the network has established secure exchange of NAS messages for the N1 NAS signalling connection, the UE shall stop timer T3510 or T3517, if running. If the SNPN sending the message was selected according to subclause 4.9.3.1.1 bullet a0) or subclause 4.9.3.2.1 bullet a0) of 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5] and there is next valid time period(s) for the SNPN, the UE shall start timer T3247 (see 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [12]) with a random value uniformly drawn from the range between the start time point of the next valid time period for localized services in SNPN and: a) for 5GMM cause value #74: 1) 30 minutes after the start time point of the next valid time period for localized services in SNPN, if the next valid time period is longer than 30 minutes; or 2) the end time point of the next valid time period for localized services in SNPN, if the next valid time period is not longer than 30 minutes; or b) for other 5GMM cause values: 1) 60 minutes after the start time point of the next valid time period for localized services in SNPN, if the next valid time period is longer than 60 minutes; or 2) the end time point of the next valid time period for localized services in SNPN, if the next valid time period is not longer than 60 minutes; otherwise between: a) 15 minutes and 30 minutes for 5GMM cause value #74; or b) 30 minutes and 60 minutes for other 5GMM cause values; if the timer is not running, and take the following actions: a) if the 5GMM cause value received is #3, #6, or #7 and the UE is neither registered for onboarding services in SNPN nor performing initial registration for onboarding services in SNPN: 1) if the 5GMM cause value is received over 3GPP access: i) if the UE is already registered over another access, the UE shall: A) store the current TAI in the list of "5GS forbidden tracking areas for roaming" for the current SNPN and, if the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both the selected entry of the "list of subscriber data" or the selected PLMN subscription, memorize the current TAI was stored in the list of "5GS forbidden tracking areas for roaming" for the current SNPN and, if the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, the selected entry of the "list of subscriber data" or the selected PLMN subscription, for non-integrity protected NAS reject message and enter the state 5GMM-DEREGISTERED.LIMITED-SERVICE; and B) search for a suitable cell in another tracking area according to 3GPP TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [28]; or ii) otherwise if the counter for "the entry for the current SNPN considered invalid for 3GPP access" events has a value less than a UE implementation-specific maximum value, the UE shall: A) set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2) and shall delete 5G-GUTI, last visited registered TAI, TAI list, and ngKSI for 3GPP access; A1) if the 5GMM cause value received is #3 or #6, delete the list of equivalent SNPNs, if any; B) increment the counter for "the entry for the current SNPN considered invalid for 3GPP access" events; C) reset the registration attempt counter in case of a REGISTRATION REJECT message or reset the service request attempt counter in case of a SERVICE REJECT message; D) store the current TAI in the list of "5GS forbidden tracking areas for roaming" for the current SNPN and, if the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, the selected entry of the "list of subscriber data" or the selected PLMN subscription, memorize the current TAI was stored in the list of "5GS forbidden tracking areas for roaming" for the current SNPN and, if the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, the selected entry of the "list of subscriber data" or the selected PLMN subscription, for non-integrity protected NAS reject message, and enter the state 5GMM-DEREGISTERED.LIMITED-SERVICE; and E) search for a suitable cell in another tracking area according to 3GPP TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [28]. As a UE implementation option, if access to SNPN over non-3GPP access is available and the selected entry of the "list of subscriber data" or the selected PLMN subscription is not considered invalid for non-3GPP access, then the UE may perform registration attempt over non-3GPP access; or iii) otherwise, the UE shall proceed as specified in subclauses 5.5.1 and 5.6.1; 2) if the 5GMM cause value is received over non-3GPP access: i) if the UE is already registered over another access, the UE shall enter the state 5GMM-DEREGISTERED.LIMITED-SERVICE; or ii) otherwise if the counter for "the entry for the current SNPN considered invalid for non-3GPP access" events has a value less than a UE implementation-specific maximum value, the UE shall: A) set the 5GS update status to 5U3 ROAMING NOT ALLOWED (and shall store it according to subclause 5.1.3.2.2) and shall delete the 5G-GUTI, last visited registered TAI, TAI list, and ngKSI for non-3GPP access; B) enter the state 5GMM-DEREGISTERED.LIMITED-SERVICE; and C) increment the counter for "the entry for the current SNPN considered invalid for non-3GPP access" events. As a UE implementation option, if 3GPP access is available and the selected entry of the "list of subscriber data" or the selected PLMN subscription is not considered invalid for 3GPP access, then the UE may make a registration attempt over 3GPP access; or iii) otherwise, the UE shall proceed as specified in subclauses 5.5.1 and 5.6.1; b) if the 5GMM cause value received is #12, #13, or #15, the UE shall proceed as specified in subclauses 5.5.1 and 5.6.1. Additionally: 1) if the 5GMM cause value is received over 3GPP access, access to SNPN over non-3GPP access is available, the UE is not registered over non-3GPP access yet, and the selected entry of the "list of subscriber data" or the selected PLMN subscription is not considered invalid for non-3GPP access, the UE may perform registration attempt over non-3GPP access; or 2) if the 5GMM cause value is received over non-3GPP access, 3GPP access is available, the UE is not registered to the current SNPN over 3GPP access yet, and the selected entry of the "list of subscriber data" or the selected PLMN subscription is not considered invalid for 3GPP access, the UE may make a registration attempt over 3GPP access; c) if the 5GMM cause value received is #27, the UE shall proceed as specified in subclauses 5.5.1 and 5.6.1. Additionally, if the SNPN-specific attempt counter for the respective access type and for the current SNPN has a value less than a UE implementation-specific maximum value, the UE shall increment this counter for the SNPN; c1) if the 5GMM cause value received is #72, the UE shall proceed as specified in subclauses 5.5.1 and 5.6.1. Additionally, if the SNPN-specific attempt counter for non-3GPP access for the current SNPN has a value less than a UE implementation-specific maximum value, the UE shall increment this counter for the SNPN; and d) if: 1) the 5GMM cause value received is #74 or #75; or 2) the 5GMM cause value received is #3, #6, or #7 and the UE is registered for onboarding services in SNPN or performing initial registration for onboarding services in SNPN; in addition to the UE requirements specified in subclauses 5.5.1 and 5.6.1: 1) if the message was received via 3GPP access and if the SNPN-specific attempt counter for 3GPP access for the SNPN sending the reject message has a value less than a UE implementation-specific maximum value, the UE shall increment the SNPN-specific attempt counter for 3GPP access for the SNPN; or 2) if the message was received via non-3GPP access and if the SNPN-specific attempt counter for non-3GPP access for the SNPN sending the reject message has a value less than a UE implementation-specific maximum value, the UE shall increment the SNPN-specific attempt counter for non-3GPP access for the SNPN. Upon expiry of timer T3247, the UE shall: - remove, for each SNPN, all tracking areas from the list of "5GS forbidden tracking areas for regional provision of service" and the list of "5GS forbidden tracking areas for roaming" for the SNPN and, if the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, the selected entry of the "list of subscriber data" or the selected PLMN subscription, which were stored in these lists for non-integrity protected NAS reject message; - set each entry of the "list of subscriber data" or the PLMN subscription to valid for 3GPP access, if the corresponding counter for "the entry for the current SNPN considered invalid for 3GPP access" events has a value less than a UE implementation-specific maximum value; - set each entry of the "list of subscriber data" or the PLMN subscription to valid for non-3GPP access, if the corresponding counter for "the entry for the current SNPN considered invalid for non-3GPP access" events has a value less than a UE implementation-specific maximum value; - remove each SNPN identity from the "permanently forbidden SNPNs" list for 3GPP access, "temporarily forbidden SNPNs" list, "permanently forbidden SNPNs for access for localized services in SNPN" list or "temporarily forbidden SNPNs for access for localized services in SNPN" list for 3GPP access which are, if the MS supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if the corresponding SNPN-specific attempt counter for 3GPP access has a value greater than zero and less than a UE implementation-specific maximum value and the SNPN identity is included in any of the "permanently forbidden SNPNs" list for 3GPP access, "temporarily forbidden SNPNs" list, "permanently forbidden SNPNs for access for localized services in SNPN" list or "temporarily forbidden SNPNs for access for localized services in SNPN" list for 3GPP access; - remove each SNPN identity from the "permanently forbidden SNPNs" list for non-3GPP access or "temporarily forbidden SNPNs" list for non-3GPP access which are, if the MS supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, associated with the selected entry of the "list of subscriber data" or the selected PLMN subscription, if the corresponding SNPN-specific attempt counter for non-3GPP access has a value greater than zero and less than a UE implementation-specific maximum value and the SNPN identity is included in any of the "permanently forbidden SNPNs" list for non-3GPP access or "temporarily forbidden SNPNs" list for non-3GPP access; - re-enable the N1 mode capability for 3GPP access and, for each SNPN-specific attempt counter for 3GPP access that has a value greater than zero and less than a UE implementation-specific maximum value, remove the respective SNPN from the list of SNPNs for which the N1 mode capability was disabled due to receipt of a reject from the network with 5GMM cause #27 "N1 mode not allowed" (see 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]); - re-enable the N1 mode capability for non-3GPP access and, for each SNPN-specific attempt counter for non-3GPP access that has a value greater than zero and less than a UE implementation-specific maximum value, remove the respective SNPN from the list of SNPNs for which N1 mode capability was disabled for non-3GPP access due to receipt of a reject from the network with 5GMM cause #27 "N1 mode not allowed" or 5GMM cause #72 "non-3GPP access to 5GCN not allowed"; and - initiate a registration procedure, if still needed, dependent on 5GMM state and 5GS update status, or perform SNPN selection according to 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]. When the UE is switched off or a UICC containing the USIM is removed: - for each SNPN-specific attempt counter for 3GPP access having a value greater than zero and less than the UE implementation-specific maximum value, the UE shall remove the respective SNPN identity from the "permanently forbidden SNPNs" list(s), "temporarily forbidden SNPNs" list(s), "permanently forbidden SNPNs for access for localized services in SNPN" list(s) or "temporarily forbidden SNPNs for access for localized services in SNPN" list(s) for 3GPP access, if available; and - for each SNPN-specific attempt counter for non-3GPP access having a value greater than zero and less than the UE implementation-specific maximum value, the UE shall remove the respective SNPN identity from the "permanently forbidden SNPNs" list(s) for non-3GPP access or "temporarily forbidden SNPNs" list(s) for non-3GPP access, if available. When an entry of the "list of subscriber data" is updated: - if the UE does not support access to an SNPN using credentials from a credentials holder and equivalent SNPNs, and the SNPN-specific attempt counter for 3GPP access for the SNPN corresponding to the entry has a value greater than zero and less than the UE implementation-specific maximum value, the UE shall remove the SNPN identity corresponding to the entry from the "permanently forbidden SNPNs" list for 3GPP access or "temporarily forbidden SNPNs" list for 3GPP access, if available; - if the UE does not support access to an SNPN using credentials from a credentials holder and equivalent SNPNs, and the SNPN-specific attempt counter for non-3GPP access for the SNPN corresponding to the entry has a value greater than zero and less than the UE implementation-specific maximum value, the UE shall remove the SNPN identity corresponding to the entry from the "permanently forbidden SNPNs" list for non-3GPP access or "temporarily forbidden SNPNs" list for non-3GPP access, if available; - if the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, and the SNPN-specific attempt counter for 3GPP access for an SNPN in the "permanently forbidden SNPNs" list for 3GPP access or "temporarily forbidden SNPNs" list for 3GPP access, associated with the entry, has a value greater than zero and less than the UE implementation-specific maximum value, the UE shall remove the SNPN identity corresponding to the SNPN from the "permanently forbidden SNPNs" list for 3GPP access or "temporarily forbidden SNPNs" list for 3GPP access, associated with the entry; - if the UE supports access to an SNPN providing access for localized services in SNPN, and the SNPN-specific attempt counter for 3GPP access for an SNPN in the "permanently forbidden SNPNs for access for localized services in SNPN" list or "temporarily forbidden SNPNs for access for localized services in SNPN" list, associated with the entry, has a value greater than zero and less than the UE implementation-specific maximum value, the UE shall remove the SNPN identity corresponding to the SNPN from the "permanently forbidden SNPNs for access for localized services in SNPN" list or "temporarily forbidden SNPNs for access for localized services in SNPN" list for 3GPP access, associated with the entry; and - if the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, and the SNPN-specific attempt counter for non-3GPP access for an SNPN in the "permanently forbidden SNPNs" list for non-3GPP access or "temporarily forbidden SNPNs" list for non-3GPP access associated with the entry, has a value greater than zero and less than the UE implementation-specific maximum value, the UE shall remove the SNPN identity corresponding to the SNPN from the "permanently forbidden SNPNs" list for non-3GPP access or "temporarily forbidden SNPNs" list for non-3GPP access, associated with the entry. | 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.20.3 |
6,626 | 7.3.19 RAN Information Relay | The RAN Information Relay message shall be sent on S3 interface between SGSN and MME to transfer the RAN information received by an SGSN from BSS or RNS (or GERAN Iu mode) or by an MME from eNodeB. The procedures are specified in 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [3]. This message shall also be sent on S16 interface to transfer the RAN information between GERAN or GERAN Iu mode or UTRAN. For handling of protocol errors the RAN Information Relay message is treated as a Response message. Table 7.3.19-1 specifies the presence requirements and conditions of the IEs in the message. Table 7.3.19-1: Information Elements in a RAN Information Relay | 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.3.19 |
6,627 | 5.2.21.4.2 Nnsacf_SliceEventExposure_Subscribe service operation | Service operation name: Nnsacf_SliceEventExposureSubscribe Description: This service operation is used by the consumer NF to subscribe or modify a subscription with the NSACF for event based notifications of the current number of UEs registered for a network slice or the current number of PDU Sessions established on a network slice. Inputs, Required: Event ID, Event Filter, Event Reporting information. The Event ID parameter defines whether to notify the number of UEs registered with a network slice or the number of PDU Sessions established on a network slice. The Event Filter parameter is the S-NSSAI for which the current number of UEs registered for a network slice or the current number of PDU Sessions established on a network slice or both are to be notified to the consumer NF. The Event Reporting information parameter defines whether the notification is threshold based (e.g. the notification is triggered when the current number of UEs or PDU Sessions with a network slice reaches a defined threshold value) or the notification is periodical (e.g. the notification is triggered at expiry of a periodic timer) and optionally the Immediate reporting flag. Inputs, Optional: Notification threshold, Notification periodicity. The Notification threshold parameter is optional. It is provided when the Notification is threshold base. The notification threshold parameter may be a numeric value or a percentage of the maximum number of the UEs or PDU Sessions per network slice. The Notification periodicity parameter is optional. It is provided when the Notification is periodical. The Notification periodicity parameter defines the time between the notification periodicity. Outputs, Required: Operation execution result response, Subscription Correlation Id. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.21.4.2 |
6,628 | 5.3.9A Handling of congestion control for transport of user data via the control plane | The network may activate congestion control for transport of user data via the control plane, as specified in 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [10]. If the congestion control for transport of user data via the control plane is active and if the UE has indicated support for the control plane data back-off timer, the network shall include a value for the control plane data back-off timer T3448 in ATTACH ACCEPT, TRACKING AREA UPDATE ACCEPT, SERVICE ACCEPT or SERVICE REJECT message, and shall store a control plane data back-off time on a per UE basis. The UE starts the timer T3448 with the value informed in the message. To avoid that large numbers of UEs simultaneously initiate deferred requests, the network should select the value for the timer T3448 for the informed UEs so that timeouts are not synchronised. The network sends TRACKING AREA UPDATE ACCEPT message or SERVICE ACCEPT message without T3448 value IE to stop the timer T3448 running in the UE as specified in clause 5.5.3.2.4 and clause 5.6.1.4.2. Based on the stored control plane data back-off time for the UE, the network may reject the transfer of user data via the control plane initiated by the UE. While the timer T3448 is running, the UE in EMM-IDLE mode shall not initiate the transport of user data via the control plane procedure (see clause 6.6.4), except if the UE is allowed to use exception data reporting (see the ExceptionDataReportingAllowed leaf of the NAS configuration MO in 3GPP TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [15A] or the USIM file EFNASCONFIG in 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [17]) and the user data is related to an exceptional event. Upon entering the state EMM-DEREGISTERED or a new PLMN which is not equivalent to the PLMN where the UE started the timer T3448, or upon being switched off while the timer T3448 is running, the UE shall stop the timer T3448. For further criteria to stop of timer T3448, refer to clause 5.5.3.2.4 and clause 5.6.1.4.2. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.3.9A |
6,629 | 14.3.2 Nnrf_AccessToken_Get Service Operation | Service Operation name: Nnrf_AccessToken_Get. Description: NF Service Consumer requests NRF to provide an Access Token. Inputs, Required: the NF Instance Id of the NF Service Consumer, the requested "scope" including the expected NF service name(s). Inputs, Optional: PLMN ID (or SNPN ID) of the requester NF Service Consumer, PLMN ID (or SNPN ID)of the requested NF Service Producer, NF Instance Id(s) of the requested NF Service Producer, NF type of the expected NF Service Producer instance and NF Service Consumer, "additional scope" information (i.e. requested resources and requested actions (service operations) on the resources), list of NSSAIs or list of NSI IDs for the expected NF Service Producer instances, NF Set ID of the expected NF Service Producer instances, list of S-NSSAIs of the NF Service Consumer. Outputs, Required: Access Token with appropriate claims, where the claims shall include NF Instance Id of NRF (issuer), NF Instance Id of the NF Service Consumer potentially appended with its PLMN ID (or SNPN ID) (subject), NF type of the NF Service Producers or NF Instance Id or several NF Instance Id(s) of the requested NF Service Producer, potentially appended with PLMN ID (or SNPN ID) (audience), expected service name (scope), optionally "additional scope" information (allowed resources and allowed actions (service operations) on the resources) and expiration time (expiration), may include list of NSSAIs or NSI IDs for the expected NF Service Producer instances, and may include the NF Set ID of the expected NF Service Producer instances. Outputs, Optional: None. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 14.3.2 |
6,630 | 5.6.7.2 Enhancement of UP path management based on the coordination with AFs | In order to avoid or minimize service interruption during PSA relocation for a PDU session of SSC mode 3, or a PDU session with UL CL or branch point, according to the indication of "AF acknowledgment to be expected" on AF subscription to corresponding SMF events (DNAI change) (that may be provided in PCC rules received from the PCF as defined in clause 5.6.7.1 except in HR-SBO case or that may be provided directly by V-NEF to V-SMF as defined in TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [130] clause 6.7.2 in case of HR-SBO) or according to local configuration (e.g. DN-related policies) the SMF may wait for a response from the AF after sending a notification (an early notification or a late notification) to the AF. In the case of late notification, based on the indication of "AF acknowledgment to be expected" on AF subscription, the SMF may send the notification before activating the UP path towards a new DNAI (possibly through a new PSA). NOTE 1: Before the UP path toward the new DNAI is activated, application traffic data (if any exists) is still routed toward the old DNAI. The notification sent from the SMF to the AF indicates UP path management events (DNAI change) as described in clause 5.6.7.1. The AF can confirm the DNAI change indicated in the notification with the SMF by sending a positive response to the notification to the SMF or reject the DNAI change by sending a negative response. NOTE 2: The AF can determine whether application relocation is needed according to the notification of DNAI change. If not, the AF can send a positive response to the SMF immediately; otherwise, the AF sends the positive response after application relocation is completed or a negative response if the AF determines that the application relocation cannot be completed on time (e.g. due to temporary congestion). The AF decision and behaviours on application relocation are not defined. However, the new DNAI may be associated with a new AF. In such cases, the SMF and the old AF cancel earlier subscribed UP path management event notifications, and the new AF subscribes to receive UP path management event notifications from the SMF. The AF can include N6 traffic routing information related to the target DNAI in a positive response sent to the SMF. The SMF configures the N6 traffic routing information from the AF response to the PSA on the UP path. The AF can include the EAS relocation Indication to indicate the application(s) to be relocated. In the case of early notification, based on the indication of "AF acknowledgment to be expected" on AF subscription, the SMF does not configure the UP path towards the new DNAI until it receives a positive AF response as specified in clause 4.3.6.3 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. In the case of late notification, based on the indication of "AF acknowledgment to be expected" on AF subscription, the SMF does not activate the UP path towards the new DNAI until it receives a positive AF response as specified in clause 4.3.5 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. NOTE 3: After the UP path toward the new DNAI is activated, data is routed toward the new DNAI. If the SMF receives a negative response at any time, the SMF keeps using the original DNAI and may cancel related PSA relocation or addition. The SMF may perform DNAI reselection afterwards if needed. The SMF can assume according to local policy a negative response if a response is expected and but not received from the AF within a certain time window. When Early/Late Notification happens, the SMF notifies AF about the target DNAI and may indicate capability of supporting EAS IP replacement in 5GC.When EAS relocation is performed, the AF sends an/a early/late notification response to the SMF after the EAS relocation is completed, which may include the Information for EAS IP Replacement in 5GC. The SMF may instruct the local PSA with the EAS IP address replacement using "Outer Header Creation" as defined in clause 5.8.5.6 and "Outer Header Removal" as defined in clause 5.8.5.3. If local PSA relocation is required, the SMF may request the target local PSA to buffer uplink traffic as described in clause 6.3.5 of TS 23.548[ 5G System Enhancements for Edge Computing; Stage 2 ] [130]. AF relocation may be triggered by SMF e.g. in relationship with DNAI change due to UE mobility. In the case of AF relocation involving different DNAI(s), it is possible that the source EHE is unaware of other/target EHE specific deployment details. In such cases, when SMF selects a target DNAI (e.g. based on current UE location), the SMF may determine based on the EDI that the target DNAI is not supported by the source AF. The SMF determines the target AF ID based on the target DNAI and the EDI. Accordingly, as part of Early/Late Notification, the SMF provides the target AF ID to the source AF as described in clause 4.3.6.3 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.6.7.2 |
6,631 | 5.5.1 Registration Management | This clause applies to Non-3GPP access network corresponding to the Untrusted Non-3GPP access network, to the Trusted Non-3GPP access network and to the W-5GAN. In the case of W-5GAN the UE mentioned in this clause corresponds to 5G-RG or to the W-AGF in the case of FN-RG. In the case of N5CW devices access 5GC via trusted WLAN access networks, the UE mentioned in this clause corresponds to TWIF. The UE shall enter RM-DEREGISTERED state and the AMF shall enter RM-DEREGISTERED state for the UE on non-3GPP access as follows: - at the UE and at the AMF, after performing an Explicit Deregistration procedure; - at the AMF, after the Network non-3GPP Implicit Deregistration timer has expired. - at the UE, after the UE non-3GPP Deregistration timer has expired. NOTE: This is assumed to leave sufficient time to allow the UE to re-activate UP connections for the established PDU Sessions over 3GPP or non-3GPP access. Whenever a UE registered over non-3GPP access enters CM-IDLE state for the non-3GPP access, it starts the UE non-3GPP Deregistration timer according to the value received from the AMF during a Registration procedure. Over non-3GPP access, the AMF runs the Network non-3GPP Implicit Deregistration timer. The Network non-3GPP Implicit Deregistration timer is started with a value longer than the UE's non-3GPP Deregistration timer, whenever the CM state for the UE registered over non-3GPP access changes to CM-IDLE for the non-3GPP access. For a UE that is registered over Non-3GPP access, a change of the point of attachment (e.g. change of WLAN AP) shall not lead the UE to perform a Registration procedure. A UE that is registered over non-3GPP access may trigger a Mobility Registration Update procedure via a new non-3GPP AN node (i.e. N3IWF or TNGF) to switch traffic from an old non-3GPP access to a new non-3GPP access. Traffic switching from an old non-3GPP access to and from a wireline access is not supported in this Release. Traffic switching from an old non-3GPP access to new non-3GPP access is supported only when PLMN of the new non-3GPP access is the same PLMN of the old non-3GPP access. A UE shall not provide 3GPP-specific parameters (e.g. indicate a preference for MICO mode) during registration over a non-3GPP access. During registration procedure the AMF may determine whether the serving N3IWF/TNGF is appropriate based on the slices supported by the N3IWFs/TNGFs as specified in clause 6.3.6 and clause 6.3.12 respectively. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.5.1 |
6,632 | – RateMatchPattern | The IE RateMatchPattern is used to configure one rate matching pattern for PDSCH, see TS 38.214[ NR; Physical layer procedures for data ] [19], clause 5.1.4.1. RateMatchPattern information element -- ASN1START -- TAG-RATEMATCHPATTERN-START RateMatchPattern ::= SEQUENCE { rateMatchPatternId RateMatchPatternId, patternType CHOICE { bitmaps SEQUENCE { resourceBlocks BIT STRING (SIZE (275)), symbolsInResourceBlock CHOICE { oneSlot BIT STRING (SIZE (14)), twoSlots BIT STRING (SIZE (28)) }, periodicityAndPattern CHOICE { n2 BIT STRING (SIZE (2)), n4 BIT STRING (SIZE (4)), n5 BIT STRING (SIZE (5)), n8 BIT STRING (SIZE (8)), n10 BIT STRING (SIZE (10)), n20 BIT STRING (SIZE (20)), n40 BIT STRING (SIZE (40)) } OPTIONAL, -- Need S ... }, controlResourceSet ControlResourceSetId }, subcarrierSpacing SubcarrierSpacing OPTIONAL, -- Cond CellLevel dummy ENUMERATED { dynamic, semiStatic }, ..., [[ controlResourceSet-r16 ControlResourceSetId-r16 OPTIONAL -- Need R ]] } -- TAG-RATEMATCHPATTERN-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
6,633 | 10.5.4.22a Reverse call setup direction | This information element may be included in a MODIFY and MODIFY COMPLETE message to indicate that the direction of the data call to which the MODIFY message relates is opposite to the call setup direction. The reverse call setup direction information element is coded as shown in figure 10.5.110/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The reverse call setup direction is a type 2 information element Figure 10.5.110/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Reverse call setup direction 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.22a |
6,634 | 5.8.10.2.3 Sidelink measurement identity addition/modification | The UE shall: 1> for each sl-MeasId included in the received sl-MeasIdToAddModList: 2> if an entry with the matching sl-MeasId exists in the sl-MeasIdList within the VarMeasConfigSL: 3> replace the entry with the value received for this sl-MeasId; 2> else: 3> add a new entry for this sl-MeasId within the VarMeasConfigSL; 2> remove the measurement reporting entry for this sl-MeasId from the VarMeasReportListSL, if included; 2> stop the periodical reporting timer and reset the associated information (e.g. sl-TimeToTrigger) for this sl-MeasId; | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.8.10.2.3 |
6,635 | 16.3 Network Slicing 16.3.1 General Principles and Requirements | In this clause, the general principles and requirements related to the realization of network slicing in the NG-RAN for NR connected to 5GC and for E-UTRA connected to 5GC are given. A network slice always consists of a RAN part and a CN part. The support of network slicing relies on the principle that traffic for different slices is handled by different PDU sessions. Network can realise the different network slices by scheduling and also by providing different L1/L2 configurations. Each network slice is uniquely identified by a S-NSSAI, as defined in TS 23.501[ System architecture for the 5G System (5GS) ] [3]. NSSAI (Network Slice Selection Assistance Information) includes one or a list of S-NSSAIs (Single NSSAI) where a S-NSSAI is a combination of: - mandatory SST (Slice/Service Type) field, which identifies the slice type and consists of 8 bits (with range is 0-255); - optional SD (Slice Differentiator) field, which differentiates among Slices with same SST field and consist of 24 bits. The list includes at most 8 S-NSSAI(s). The UE provides NSSAI (Network Slice Selection Assistance Information) for network slice selection in RRCSetupComplete, if it has been provided by NAS (see clause 9.2.1.3). While the network can support large number of slices (hundreds), the UE need not support more than 8 slices simultaneously. A BL UE or a NB-IoT UE supports a maximum of 8 slices simultaneously. Network Slicing is a concept to allow differentiated treatment depending on each customer requirements. With slicing, it is possible for Mobile Network Operators (MNO) to consider customers as belonging to different tenant types with each having different service requirements that govern in terms of what slice types each tenant is eligible to use based on Service Level Agreement (SLA) and subscriptions. The following key principles apply for support of Network Slicing in NG-RAN: RAN awareness of slices - NG-RAN supports a differentiated handling of traffic for different network slices which have been pre-configured. How NG-RAN supports the slice enabling in terms of NG-RAN functions (i.e. the set of network functions that comprise each slice) is implementation dependent. Selection of RAN part of the network slice - NG-RAN supports the selection of the RAN part of the network slice, by NSSAI provided by the UE or the 5GC which unambiguously identifies one or more of the pre-configured network slices in the PLMN. Resource management between slices - NG-RAN supports policy enforcement between slices as per service level agreements. It should be possible for a single NG-RAN node to support multiple slices. The NG-RAN should be free to apply the best RRM policy for the SLA in place to each supported slice. Support of QoS - NG-RAN supports QoS differentiation within a slice, and per Slice-Maximum Bit Rate may be enforced per UE, if feasible. How NG-RAN enables UE-Slice-MBR enforcement and rate limitation (see TS 23.501[ System architecture for the 5G System (5GS) ] [3]) is up to network implementation. RAN selection of CN entity - For initial attach, the UE may provide NSSAI to support the selection of an AMF. If available, NG-RAN uses this information for routing the initial NAS to an AMF. If the NG-RAN is unable to select an AMF using this information or the UE does not provide any such information the NG-RAN sends the NAS signalling to one of the default AMFs. - For subsequent accesses, the UE provides a Temp ID, which is assigned to the UE by the 5GC, to enable the NG-RAN to route the NAS message to the appropriate AMF as long as the Temp ID is valid (NG-RAN is aware of and can reach the AMF which is associated with the Temp ID). Otherwise, the methods for initial attach applies. Resource isolation between slices - The NG-RAN supports resource isolation between slices. NG-RAN resource isolation may be achieved by means of RRM policies and protection mechanisms that should avoid that shortage of shared resources in one slice breaks the service level agreement for another slice. It should be possible to fully dedicate NG-RAN resources to a certain slice. Some RACH resources can be associated to specific NSAG(s). Other aspects how NG-RAN supports resource isolation is implementation dependent. Access control - By means of the unified access control (see clause 7.4), operator-defined access categories can be used to enable differentiated handling for different slices. NG-RAN may broadcast barring control information (i.e. a list of barring parameters associated with operator-defined access categories) to minimize the impact of congested slices. Slice Availability - Some slices may be available only in part of the network. A slice is considered available in a cell if it is supported by the TA comprising the cell and the slice is not configured with zero resources, as specified in TS 23.501[ System architecture for the 5G System (5GS) ] [3]. A slice is supported within a TA if it is included in the slice support list for the TA signalled from the NG-RAN to the AMF. The NG-RAN supported S-NSSAI(s), NSAG(s) and NSAG related information such as NSAG associated Cell Reselection Priority and/or NSAG associated RACH resources are configured by OAM. Awareness in the NG-RAN of the slices supported in the cells of its neighbours may be beneficial for inter-frequency mobility in connected mode. In order to support the NSAG, the NG-RAN provides the AMF with the NSAG information per TA in the appropriate NG interface management procedures, as specified in TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [26]. Awareness in the NG-RAN of the NSAG information supported in the list(s) of neighbour cells may be configured by OAM, or exchanged with neighbour NG-RAN nodes. - The NG-RAN and the 5GC are responsible to handle a service request for a slice that may or may not be available in a given area. Admission or rejection of access to a slice may depend by factors such as support for the slice, availability of resources, support of the requested service by NG-RAN. - The NG-RAN may be signalled with the Partially Allowed NSSAI from the AMF as specified in TS 23.501[ System architecture for the 5G System (5GS) ] [3]. The NG-RAN may decide to use the Partially Allowed NSSAI for mobility decision. - Support for Network Slices with Network Slice Area of Service not matching deployed Tracking Areas is specified in TS 23.501[ System architecture for the 5G System (5GS) ] [3]. NG-RAN cells that are outside the Area of Service may be configured with zero resources for the concerned slice(s). The concerned slice(s) cannot use any dedicated, prioritized nor any shared resources of that cell. Awareness of zero resources configured for a slice in one or more cells may be exchanged with neighbour NG-RAN nodes for mobility reasons. Support for UE associating with multiple network slices simultaneously - In case a UE is associated with multiple slices simultaneously, only one signalling connection is maintained and for intra-frequency cell reselection, the UE always tries to camp on the best cell. For inter-frequency cell reselection, dedicated priorities can be used to control the frequency on which the UE camps. Granularity of slice awareness - Slice awareness in NG-RAN is introduced at PDU session level, by indicating the S-NSSAI corresponding to the PDU Session, in all signalling containing PDU session resource information. Validation of the UE rights to access a network slice - It is the responsibility of the 5GC to validate that the UE has the rights to access a network slice. Prior to receiving the Initial Context Setup Request message, the NG-RAN may be allowed to apply some provisional/local policies, based on awareness of which slice the UE is requesting access to. During the initial context setup, the NG-RAN is informed of the slice for which resources are being requested. Network slice replacement - NG-RAN may support network slice replacement for a PDU session as defined in TS 23.501[ System architecture for the 5G System (5GS) ] [3]. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.3 |
6,636 | – MCGFailureInformation | The MCGFailureInformation message is used to provide information regarding NR MCG failures detected by the UE. Signalling radio bearer: SRB1 RLC-SAP: AM Logical channel: DCCH Direction: UE to Network MCGFailureInformation message -- ASN1START -- TAG-MCGFAILUREINFORMATION-START MCGFailureInformation-r16 ::= SEQUENCE { criticalExtensions CHOICE { mcgFailureInformation-r16 MCGFailureInformation-r16-IEs, criticalExtensionsFuture SEQUENCE {} } } MCGFailureInformation-r16-IEs ::= SEQUENCE { failureReportMCG-r16 FailureReportMCG-r16 OPTIONAL, lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension SEQUENCE {} OPTIONAL } FailureReportMCG-r16 ::= SEQUENCE { failureType-r16 ENUMERATED {t310-Expiry, randomAccessProblem, rlc-MaxNumRetx, t312-Expiry-r16, lbt-Failure-r16, beamFailureRecoveryFailure-r16, bh-RLF-r16, spare1} OPTIONAL, measResultFreqList-r16 MeasResultList2NR OPTIONAL, measResultFreqListEUTRA-r16 MeasResultList2EUTRA OPTIONAL, measResultSCG-r16 OCTET STRING (CONTAINING MeasResultSCG-Failure) OPTIONAL, measResultSCG-EUTRA-r16 OCTET STRING OPTIONAL, measResultFreqListUTRA-FDD-r16 MeasResultList2UTRA OPTIONAL, ... } MeasResultList2UTRA ::= SEQUENCE (SIZE (1..maxFreq)) OF MeasResult2UTRA-FDD-r16 MeasResult2UTRA-FDD-r16 ::= SEQUENCE { carrierFreq-r16 ARFCN-ValueUTRA-FDD-r16, measResultNeighCellList-r16 MeasResultListUTRA-FDD-r16 } MeasResultList2EUTRA ::= SEQUENCE (SIZE (1..maxFreq)) OF MeasResult2EUTRA-r16 -- TAG-MCGFAILUREINFORMATION-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
6,637 | 28.3.2.2.6 FQDN for SNPN N3IWF | 28.3.2.2.6.1 SNPN Identifier based N3IWF FQDN and Visited Country FQDN for SNPN N3IWF The SNPN Identifier based N3IWF FQDN is used by a UE to access SNPN service in its subscribed SNPN via PLMN or directly via an untrusted non-3GPP access, as specified in clause 6.3.6.2a of 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [119]. The N3IWF FQDN is composed of seven labels. The last three labels shall be "pub.3gppnetwork.org". The third label and fourth labels together shall identify the SNPN (the country where it is located along with the SNPN ID). The first two labels shall be "n3iwf.5gc". Hence, the SNPN Identifier based N3IWF FQDN shall be constructed as follows: "n3iwf.5gc.snpnid<SNPNID>.mcc<MCC>.pub.3gppnetwork.org". The <MCC> coding used in this FQDN shall be: - <MCC> = 3 digits The <SNPNID> coding used in this FQDN shall be: - <SNPNID> = PLMN ID || NID where, PLMN ID = MCC || MNC NOTE 1: The MCC used in the SNPNID is not necessarily the same (e.g. it can be 999 reserved for internal use) as the one used in coding the <MCC>. NOTE 2: Locally assigned NIDs are not supported, since a DNS cannot be properly configured for multiple SNPNs using the same locally assigned NID. As an example, SNPN Identifier based N3IWF FQDN for MCC 098, SNPN MCC 999, MNC 305, and NID 456789ABCDE is coded in the DNS as: "n3iwf.5gc.snpnid999305456789ABCDE.mcc098.pub.3gppnetwork.org" The Visited Country FQDN for SNPN N3IWF, used by a UE in the visited country to determine whether the visited country mandates the selection of an N3IWF in this country for the SNPN identified by the SNPN Identifier provided by the UE, shall be constructed as described below. The Visited Country FQDN for SNPN N3IWF shall contain a MCC that uniquely identifies the country in which the UE is located, and the SNPN Identifier. The Visited Country FQDN for SNPN N3IWF is composed of eight labels. The last three labels shall be "pub.3gppnetwork.org". The fifth label shall be "visited-country". The fourth label shall uniquely identify the MCC of the visited country. The third label shall be the SNPN Identifier as specified in clause 12.7. The first and second labels shall be "n3iwf.5gc". The Visited Country FQDN for SNPN N3IWF shall be constructed as follows: "n3iwf.5gc.snpnid<SNPNID>.mcc<MCC>.visited-country.pub.3gppnetwork.org" The <MCC> coding used in this FQDN shall be: - <MCC> = 3 digits The <SNPNID> coding used in this FQDN shall be: - <SNPNID> = MCC || MNC || NID NOTE 1: The MCC used in the SNPNID is not necessarily the same (e.g. it can be 999 reserved for internal use) as the one used in coding the <MCC>. NOTE 2: Locally assigned NIDs are not supported, since a DNS cannot be properly configured for multiple SNPNs using the same locally assigned NID. As an example, the Visited Country FQDN for SNPN N3IWF for MCC 345, SNPN MCC 999, MNC 123, and NID 456789ABCDE is coded in the DNS as: "n3iwf.5gc.snpnid999123456789ABCDE.mcc345.visited-country.pub.3gppnetwork.org". NOTE 3: The identity (i.e. the corresponding DNS record) of an SNPN's N3IWF in the visited country can be any FQDN and is not required to include the SNPN identifier. 28.3.2.2.6.2 Visited Country FQDN for SNPN N3IWF supporting Onboarding SNPN N3IWF supporting Onboarding is specified in clause 5.30.2.12 of 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [119]. If an SNPN for onboarding has been selected, Visited Country FQDN for SNPN N3IWF indicates that the SNPN identified by the SNPN in the DNS response shall support onboarding. Visited Country FQDN for SNPN N3IWF supporting Onboarding is composed of eight labels. The last four labels shall be " visited-country.pub.3gppnetwork.org". The fourth label shall uniquely identify the MCC of the visited country. The second and third labels shall be "n3iwf.snpn-5gc". The first label shall be "onboarding". The resultant Visited Country FQDN for SNPN N3IWF supporting Onboarding shall be constructed as follows: "onboarding.n3iwf.snpn-5gc.mcc<MCC>.visited-country.pub.3gppnetwork.org" As an example, the Visited Country FQDN for SNPN N3IWF, which also supports Onboarding for MCC 345 is coded in the DNS as: "onboarding.n3iwf.snpn-5gc.mcc345.visited-country.pub.3gppnetwork.org". 28.3.2.2.6.3 Visited Country Emergency SNPN FQDN The Visited Country Emergency SNPN FQDN, used by a UE to determine whether the visited country mandates the selection of an SNPN N3IWF for emergency service in this country, shall be constructed as described below. The Visited Country Emergency SNPN FQDN shall contain a MCC that uniquely identifies the country in which the UE is located. The Visited Country Emergency SNPN FQDN is composed of eight labels. The last three labels shall be "pub.3gppnetwork.org". The fifth label shall be "visited-country". The forth label shall uniquely identify the MCC of the visited country. The second and third labels shall be "n3iwf.snpn-5gc". The first label shall be "sos"". The resulting Visited Country Emergency SNPN FQDN shall be constructed as follows: "sos.n3iwf.snpn-5gc.mcc<MCC>.visited-country.pub.3gppnetwork.org". As an example, the Visited Country Emergency SNPN FQDN for MCC 345 is coded in the DNS as: "sos.n3iwf.snpn-5gc.mcc345.visited-country.pub.3gppnetwork.org". 28.3.2.2.6.4 Replacement field used in DNS-based Discovery of regulatory requirements for emergency services in SNPN If the visited country mandates the selection of an SNPN N3IWF for emergency services in this country, the NAPTR record(s) associated to the Visited Country Emergency SNPN FQDN shall be provisioned with the replacement field containing the identity of the SNPN(s) in the visited country which may be used for N3IWF selection. The replacement field shall take the form of an SNPN Identifier based N3IWF FQDN as specified in clause 28.3.2.2.6.1 with the addition of the label "sos" before the labels "n3iwf.5gc" as "sos.n3iwf.5gc.snpnid<SNPNID>.mcc<MCC>.pub.3gppnetwork.org". As an example, the NAPTR records associated to the Visited Country Emergency SNPN FQDN for MCC 345, and for a) SNPN MCC 999, MNC 012, and NID 345678ABCDE; b) SNPN MCC 345, MNC 013, and NID 345678BCDEF; and c) SNPN MCC 999, MNC 014, and NID 234567CDEFG, are provisioned in the DNS as: sos.n3iwf.snpn-5gc.mcc345.visited-country.pub.3gppnetwork.org ; IN NAPTR order pref. flag service regexp replacement IN NAPTR 100 999 "" "" sos.n3iwf.5gc.snpnid999012345678ABCDE.mcc345.pub.3gppnetwork.org IN NAPTR 100 999 "" "" sos.n3iwf.5gc.snpnid345013345678BCDEF.mcc345.pub.3gppnetwork.org IN NAPTR 100 999 "" "" sos.n3iwf.5gc.snpnid999014234567CDEFG.mcc345.pub.3gppnetwork.org NOTE: The SNPN ID in the NAPTR records do not contain the NID using self-assignment model since a DNS cannot be properly configured for multiple SNPNs using the same self-assigned NID. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 28.3.2.2.6 |
6,638 | 9.11.3.87 NSAG information | The purpose of the NSAG information information element is to provide the NSAG information to the UE. The NSAG information information element is coded as shown in figures 9.11.3.87.1, 9.11.3.87.2 and 9.11.3.87.3, and table 9.11.3.87.1. The NSAG information information element can contain a maximum of 32 NSAG entries. In the NSAG information information element, at most 4 NSAG entries can contain a TAI list. The NSAG information is a type 6 information element, with a minimum length of 9 octets and a maximum length of 3143 octets. Figure 9.11.3.87.1: NSAG information information element Figure 9.11.3.87.2: NSAG Figure 9.11.3.87.3: S-NSSAI list of NSAG Table 9.11.3.87.1: NSAG information information element | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.11.3.87 |
6,639 | – MeasObjectNR | The IE MeasObjectNR specifies information applicable for SS/PBCH block(s) intra/inter-frequency measurements and/or CSI-RS intra/inter-frequency measurements. MeasObjectNR information element -- ASN1START -- TAG-MEASOBJECTNR-START MeasObjectNR ::= SEQUENCE { ssbFrequency ARFCN-ValueNR OPTIONAL, -- Cond SSBorAssociatedSSB ssbSubcarrierSpacing SubcarrierSpacing OPTIONAL, -- Cond SSBorAssociatedSSB smtc1 SSB-MTC OPTIONAL, -- Cond SSBorAssociatedSSB smtc2 SSB-MTC2 OPTIONAL, -- Cond IntraFreqConnected refFreqCSI-RS ARFCN-ValueNR OPTIONAL, -- Cond CSI-RS referenceSignalConfig ReferenceSignalConfig, absThreshSS-BlocksConsolidation ThresholdNR OPTIONAL, -- Need R absThreshCSI-RS-Consolidation ThresholdNR OPTIONAL, -- Need R nrofSS-BlocksToAverage INTEGER (2..maxNrofSS-BlocksToAverage) OPTIONAL, -- Need R nrofCSI-RS-ResourcesToAverage INTEGER (2..maxNrofCSI-RS-ResourcesToAverage) OPTIONAL, -- Need R quantityConfigIndex INTEGER (1..maxNrofQuantityConfig), offsetMO Q-OffsetRangeList, cellsToRemoveList PCI-List OPTIONAL, -- Need N cellsToAddModList CellsToAddModList OPTIONAL, -- Need N excludedCellsToRemoveList PCI-RangeIndexList OPTIONAL, -- Need N excludedCellsToAddModList SEQUENCE (SIZE (1..maxNrofPCI-Ranges)) OF PCI-RangeElement OPTIONAL, -- Need N allowedCellsToRemoveList PCI-RangeIndexList OPTIONAL, -- Need N allowedCellsToAddModList SEQUENCE (SIZE (1..maxNrofPCI-Ranges)) OF PCI-RangeElement OPTIONAL, -- Need N ..., [[ freqBandIndicatorNR FreqBandIndicatorNR OPTIONAL, -- Need R measCycleSCell ENUMERATED {sf160, sf256, sf320, sf512, sf640, sf1024, sf1280} OPTIONAL -- Need R ]], [[ smtc3list-r16 SSB-MTC3List-r16 OPTIONAL, -- Need R rmtc-Config-r16 SetupRelease {RMTC-Config-r16} OPTIONAL, -- Need M t312-r16 SetupRelease { T312-r16 } OPTIONAL -- Need M ]], [[ associatedMeasGapSSB-r17 MeasGapId-r17 OPTIONAL, -- Need R associatedMeasGapCSIRS-r17 MeasGapId-r17 OPTIONAL, -- Need R smtc4list-r17 SSB-MTC4List-r17 OPTIONAL, -- Need R measCyclePSCell-r17 ENUMERATED {ms160, ms256, ms320, ms512, ms640, ms1024, ms1280, spare1} OPTIONAL, -- Cond SCG cellsToAddModListExt-v1710 CellsToAddModListExt-v1710 OPTIONAL -- Need N ]], [[ associatedMeasGapSSB2-v1720 MeasGapId-r17 OPTIONAL, -- Cond AssociatedGapSSB associatedMeasGapCSIRS2-v1720 MeasGapId-r17 OPTIONAL -- Cond AssociatedGapCSIRS ]], [[ measSequence-r18 MeasSequence-r18 OPTIONAL, -- Need R cellsToAddModListExt-v1800 CellsToAddModListExt-v1800 OPTIONAL -- Cond ServingCell ]] } SSB-MTC3List-r16::= SEQUENCE (SIZE(1..4)) OF SSB-MTC3-r16 SSB-MTC4List-r17::= SEQUENCE (SIZE(1..3)) OF SSB-MTC4-r17 T312-r16 ::= ENUMERATED { ms0, ms50, ms100, ms200, ms300, ms400, ms500, ms1000} ReferenceSignalConfig::= SEQUENCE { ssb-ConfigMobility SSB-ConfigMobility OPTIONAL, -- Need M csi-rs-ResourceConfigMobility SetupRelease { CSI-RS-ResourceConfigMobility } OPTIONAL -- Need M } SSB-ConfigMobility::= SEQUENCE { ssb-ToMeasure SetupRelease { SSB-ToMeasure } OPTIONAL, -- Need M deriveSSB-IndexFromCell BOOLEAN, ss-RSSI-Measurement SS-RSSI-Measurement OPTIONAL, -- Need M ..., [[ ssb-PositionQCL-Common-r16 SSB-PositionQCL-Relation-r16 OPTIONAL, -- Cond SharedSpectrum ssb-PositionQCL-CellsToAddModList-r16 SSB-PositionQCL-CellsToAddModList-r16 OPTIONAL, -- Need N ssb-PositionQCL-CellsToRemoveList-r16 PCI-List OPTIONAL -- Need N ]], [[ deriveSSB-IndexFromCellInter-r17 ServCellIndex OPTIONAL, -- Need R ssb-PositionQCL-Common-r17 SSB-PositionQCL-Relation-r17 OPTIONAL, -- Cond SharedSpectrum2 ssb-PositionQCL-Cells-r17 SetupRelease {SSB-PositionQCL-CellList-r17} OPTIONAL -- Need M ]], [[ cca-CellsToAddModList-r17 PCI-List OPTIONAL, -- Need N cca-CellsToRemoveList-r17 PCI-List OPTIONAL -- Need N ]], [[ ssb-ToMeasureAltitudeBasedList-r18 SetupRelease { SSB-ToMeasureAltitudeBasedList-r18 } OPTIONAL -- Need M ]] } Q-OffsetRangeList ::= SEQUENCE { rsrpOffsetSSB Q-OffsetRange DEFAULT dB0, rsrqOffsetSSB Q-OffsetRange DEFAULT dB0, sinrOffsetSSB Q-OffsetRange DEFAULT dB0, rsrpOffsetCSI-RS Q-OffsetRange DEFAULT dB0, rsrqOffsetCSI-RS Q-OffsetRange DEFAULT dB0, sinrOffsetCSI-RS Q-OffsetRange DEFAULT dB0 } ThresholdNR ::= SEQUENCE{ thresholdRSRP RSRP-Range OPTIONAL, -- Need R thresholdRSRQ RSRQ-Range OPTIONAL, -- Need R thresholdSINR SINR-Range OPTIONAL -- Need R } CellsToAddModList ::= SEQUENCE (SIZE (1..maxNrofCellMeas)) OF CellsToAddMod CellsToAddModListExt-v1710 ::= SEQUENCE (SIZE (1..maxNrofCellMeas)) OF CellsToAddModExt-v1710 CellsToAddModListExt-v1800 ::= SEQUENCE (SIZE (1..maxNrofCellMeas)) OF CellsToAddModExt-v1800 CellsToAddMod ::= SEQUENCE { physCellId PhysCellId, cellIndividualOffset Q-OffsetRangeList } CellsToAddModExt-v1710 ::= SEQUENCE { ntn-PolarizationDL-r17 ENUMERATED {rhcp,lhcp,linear} OPTIONAL, -- Need R ntn-PolarizationUL-r17 ENUMERATED {rhcp,lhcp,linear} OPTIONAL -- Need R } CellsToAddModExt-v1800 ::= SEQUENCE { ntn-NeighbourCellInfo-r18 NTN-NeighbourCellInfo-r18 OPTIONAL -- Need R } RMTC-Config-r16 ::= SEQUENCE { rmtc-Periodicity-r16 ENUMERATED {ms40, ms80, ms160, ms320, ms640}, rmtc-SubframeOffset-r16 INTEGER(0..639) OPTIONAL, -- Need M measDurationSymbols-r16 ENUMERATED {sym1, sym14or12, sym28or24, sym42or36, sym70or60}, rmtc-Frequency-r16 ARFCN-ValueNR, ref-SCS-CP-r16 ENUMERATED {kHz15, kHz30, kHz60-NCP, kHz60-ECP}, ..., [[ rmtc-Bandwidth-r17 ENUMERATED {mhz100, mhz400, mhz800, mhz1600, mhz2000} OPTIONAL, -- Need R measDurationSymbols-v1700 ENUMERATED {sym140, sym560, sym1120} OPTIONAL, -- Need R ref-SCS-CP-v1700 ENUMERATED {kHz120, kHz480, kHz960} OPTIONAL, -- Need R tci-StateInfo-r17 SEQUENCE { tci-StateId-r17 TCI-StateId, ref-ServCellId-r17 ServCellIndex OPTIONAL -- Need R } OPTIONAL -- Need R ]], [[ ref-BWPId-r17 BWP-Id OPTIONAL -- Need R ]] } SSB-PositionQCL-CellsToAddModList-r16 ::= SEQUENCE (SIZE (1..maxNrofCellMeas)) OF SSB-PositionQCL-CellsToAddMod-r16 SSB-PositionQCL-CellsToAddMod-r16 ::= SEQUENCE { physCellId-r16 PhysCellId, ssb-PositionQCL-r16 SSB-PositionQCL-Relation-r16 } SSB-PositionQCL-CellList-r17 ::= SEQUENCE (SIZE (1..maxNrofCellMeas)) OF SSB-PositionQCL-Cell-r17 SSB-PositionQCL-Cell-r17 ::= SEQUENCE { physCellId-r17 PhysCellId, ssb-PositionQCL-r17 SSB-PositionQCL-Relation-r17 } SSB-ToMeasureAltitudeBasedList-r18 ::= SEQUENCE (SIZE (1..maxNrofAltitudeRanges-r18)) OF SSB-ToMeasureAltitudeBased-r18 SSB-ToMeasureAltitudeBased-r18 ::= SEQUENCE { altitudeRange-r18 SEQUENCE { altitudeMin-r18 Altitude-r18 OPTIONAL, -- Need S altitudeMax-r18 Altitude-r18 OPTIONAL, -- Need S altitudeHyst-r18 HysteresisAltitude-r18 OPTIONAL -- Need S }, ssb-ToMeasure-r18 SSB-ToMeasure OPTIONAL -- Need S } NTN-NeighbourCellInfo-r18 ::= SEQUENCE { epochTime-r18 EpochTime-r17, ephemerisInfo-r18 EphemerisInfo-r17 } -- TAG-MEASOBJECTNR-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
6,640 | 5.27.2 TSC Assistance Information (TSCAI) and TSC Assistance Container (TSCAC) 5.27.2.1 General | TSC Assistance Information (TSCAI) is defined in Table 5.27.2-1 and describes TSC traffic characteristics for use in the 5G System. TSCAI may be used by the 5G-AN, if provided by SMF. The knowledge of TSC traffic pattern is useful for 5G-AN as it allows more efficiently scheduling of QoS Flows that have a periodic, deterministic traffic characteristics either via Configured Grants, Semi-Persistent Scheduling or with Dynamic Grants. TSCAI can be provided for both GBR and non-GBR QoS flows. The TSCTSF determines the TSC Assistance Container (defined in Table 5.27.2-2) based on information provided by an AF/NEF or a DetNet controller as described in clause 5.27.2.3 and provides it to the PCF for IP type and Ethernet type PDU Sessions. In the case of integration with IEEE TSN network, the TSN AF determines TSC Assistance Container as described in clause 5.27.2.2 and provides it to the PCF for Ethernet PDU Sessions. The PCF receives the TSC Assistance Container from the TSCTSF or the TSN AF and forwards it to the SMF as part of PCC rule as described in clause 6.1.3.23a of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]. The SMF binds a PCC rule with a TSC Assistance Container to a QoS Flow as described in clause 6.1.3.2.4 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]. The SMF uses the TSC Assistance Container to derive the TSCAI for that QoS Flow and sends the derived TSCAI to the NG-RAN. The Periodicity, Periodicity Range, Burst Arrival Time (BAT), BAT Window and Survival Time components of the TSCAI are specified by the SMF with respect to the 5G clock. The SMF is responsible for mapping the Burst Arrival Time, BAT Window, Periodicity and Periodicity Range from an external clock (when available) to the 5G clock based on the time offset and cumulative rateRatio (when available) between the external clock time and 5GS time as measured and reported by the UPF. The SMF determines the TSCAI as described in clause 5.27.2.4. A Survival Time, which indicates the time period an application can survive without any data burst, may be provided by TSN AF/AF or by the TSCTSF either in terms of maximum number of messages (message is equivalent to all packets of a data burst) or in terms of time units. Only a single data burst is expected within a single time period referred to as the periodicity. The SMF may send an update of the TSCAI to the NG-RAN as defined in clauses 4.3.3.2, 4.9.1.2.2 and 4.9.1.3.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3] or as defined in clause 5.37.8.2. Table 5.27.2-1: TSC Assistance Information (TSCAI) Table 5.27.2-2: TSC Assistance Container (TSCAC) | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.27.2 |
6,641 | 5.3.6 Mobile initiated connection only mode | The UE can request the use of mobile initiated connection only (MICO) mode during the registration procedure (see 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8] and 3GPP TS 23.502[ Procedures for the 5G System (5GS) ] [9]). The UE shall not request use of MICO mode over non-3GPP access. Furthermore, the UE in 3GPP access shall not request the use of MICO mode during: a) a registration procedure for initial registration for emergency services (see subclause 5.5.1.2); b) a registration procedure for initial registration for initiating an emergency PDU session (see subclause 5.5.1.2); c) a registration procedure for mobility and periodic registration update (see subclause 5.5.1.3) for initiating an emergency PDU session if the UE is in the state 5GMM-REGISTERED.ATTEMPTING-REGISTRATION-UPDATE; or d) a registration procedure for mobility and periodic registration update (see subclause 5.5.1.3) when the UE has an emergency PDU session established. If the UE requests the use of MICO mode, the network can accept the use of MICO mode by providing a MICO indication when accepting the registration procedure. The UE may use MICO mode only if the network has provided the MICO indication IE during the last registration procedure. The UE may also request an active time value together with the MICO mode indication during the registration procedure. If the UE requests an active time by including an active time value, the UE may also include the Requested T3512 value IE to request a particular T3512 value to be allocated. If the network accepts the use of MICO mode and does not include an active time value in T3324 IE to the UE, the AMF may include an "all PLMN registration area allocated" indication in the MICO indication IE to the UE. If the UE indicated the support for strictly periodic registration timer in the MICO indication IE to the network, the network may include a "strictly periodic registration timer supported" indication in the MICO indication IE to the UE. If the UE requested the use of active time by including an active time value and the network accepts the use of MICO mode and the use of active time, the AMF shall include an active time value in the T3324 IE to the UE. If the AMF indicates active time value to the UE, AMF should not indicate "all PLMN registration area allocated" indication in the MICO indication IE to the UE. Upon entering 5GMM-IDLE mode, AMF shall start the active timer with the active time value indicated to the UE and shall consider the UE is reachable for paging as long as the timer is running. If the UE enters 5GMM-CONNECTED mode over 3GPP access when the active timer is running, the AMF shall stop the active timer. NOTE 1: The active time value assigned by AMF can be different from the active time value requested by the UE. AMF assigns the active time value based on several factors, e.g. local configuration, expected UE behaviour, UE requested active time value, UE subscription information, network policies etc. If the UE requested an active time and a requested T3512 value and the network accepts the use of MICO mode, the AMF shall take the UE requested T3512 value into consideration when assigning a value of timer T3512 to the UE. If the network accepts the use of MICO mode, the UE may deactivate the AS layer and activate MICO mode by entering the state 5GMM-REGISTERED.NO-CELL-AVAILABLE if: a) the UE is in 5GMM-IDLE mode over3GPP access; b) the UE is in the 5GMM-REGISTERED.NORMAL-SERVICE or 5GMM-REGISTERED.NON-ALLOWED-SERVICE (as described in subclause 5.3.5.2) state for 3GPP access; and c) no T3324 value is received from the network. If the network accepts the use of MICO mode and indicates an active time value to the UE in a successful registration procedure, the UE shall start the timer T3324 with the value received from the network after entering 5GMM-IDLE mode over 3GPP access. At the expiry of the timer T3324, the UE may activate MICO mode by entering the state 5GMM-REGISTERED.NO-CELL-AVAILABLE if the UE is in the 5GMM-REGISTERED.NORMAL-SERVICE or 5GMM-REGISTERED.NON-ALLOWED-SERVICE (as described in subclause 5.3.5.2) state for 3GPP access. If the UE enters 5GMM-CONNECTED mode over 3GPP access when the timer T3324 is running, the UE shall stop the timer T3324. When MICO mode is activated, all NAS timers are stopped and associated procedures aborted except for timers T3512, T3346, T3447, T3396, T3584, T3585, any back-off timers, T3247, and the timer T controlling the periodic search for HPLMN or EHPLMN or higher prioritized PLMNs (see 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5]). NOTE 2: When MICO mode is activated and if the UE is also registered over the non-3GPP access, the AMF will not send a NOTIFICATION message with access type indicating 3GPP access over the non-3GPP access for PDU sessions associated with 3GPP access. The UE may deactivate MICO mode and activate the AS layer at any time. Upon deactivating MICO mode, the UE may initiate 5GMM procedures (e.g. for the transfer of mobile originated signalling or user data). When an emergency PDU session is successfully established after the MICO mode was enabled, the UE and the AMF shall locally disable MICO mode. The UE and the AMF shall not enable MICO mode until the AMF accepts the use of MICO mode in the next registration procedure. To enable an emergency call back, the UE should wait for a UE implementation-specific duration of time before requesting the use of MICO mode after the completion of the emergency services. If the AMF accepts the use of MICO mode and does not indicate "strictly periodic registration timer supported" in the MICO indication IE to the UE, the AMF starts the implicit de-registration timer for 3GPP access when entering 5GMM-IDLE mode for 3GPP access. If AMF accepts the use of MICO mode and indicates "strictly periodic registration timer supported" in the MICO indication IE to the UE, AMF shall start the strictly periodic monitoring timer with T3512 value indicated in the T3512 value IE after the registration procedure is completed. The AMF shall neither stop nor reset the strictly periodic monitoring timer when the NAS signalling connection is established or released for the UE. If the strictly periodic monitoring timer expires when NAS signalling connection is established for the UE, AMF shall restart the strictly periodic monitoring timer with the T3512 value, otherwise AMF shall start the implicit de-registration timer. When an emergency PDU session is successfully established and the MICO mode is disabled, the UE shall stop timer T3512 if running and the AMF shall stop strictly periodic monitoring timer if running. The UE and the AMF shall behave as if no "strictly periodic registration timer supported" indication was given to the UE in the last registration attempt. Upon successful completion of an attach procedure or tracking area updating procedure after inter-system change from N1 mode to S1 mode (see 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15]), the UE operating in single-registration mode shall locally disable MICO mode. After inter-system change from S1 mode to N1 mode, the UE operating in single-registration mode may re-negotiate MICO mode with the network during the registration procedure for mobility and periodic registration update. When MICO mode is activated for a UE that has joined one or more multicast MBS sessions, the UE may deactivate MICO mode and activate the AS layer at the MBS start time and at any of the scheduled activation times of a multicast MBS session, if any of those times are available as specified in 3GPP TS 23.247[ Architectural enhancements for 5G multicast-broadcast services ] [53]. When MICO mode is activated for a UE, the UE may deactivate MICO mode and activate the AS layer at the broadcast start time and at any of the scheduled broadcast activation times of a broadcast MBS session if any of those times are available as specified in 3GPP TS 23.247[ Architectural enhancements for 5G multicast-broadcast services ] [53]. NOTE 3: The UE can obtain via the service announcement an MBS start time, a sequence of scheduled activation times (e.g. a first time and a periodicity) or both, of a multicast MBS session as described in 3GPP TS 23.247[ Architectural enhancements for 5G multicast-broadcast services ] [53], or both, which is out of scope of this specification. Similarly, the UE can obtain via the service announcement a broadcast start time, a sequence of scheduled broadcast activation times (e.g. a first time and a periodicity) or both, of a broadcast MBS session as described in 3GPP TS 23.247[ Architectural enhancements for 5G multicast-broadcast services ] [53], which is out of scope of this specification. NOTE 4: Deactivating MICO mode and activating the AS layer at the MBS start time and the scheduled multicast activation times of a multicast MBS session allows the UE to listen to paging for a multicast MBS session which the has UE joined and to respond to it if received. How long the UE needs to listen to paging is up to UE implementation. Similarly, deactivating MICO mode and activating the AS layer at the broadcast start time and the scheduled broadcast activation times of a broadcast MBS session allows the UE to acquire the traffic of the broadcast MBS session. When MICO mode is activated, the UE is allowed to join one or more multicast MBS sessions. In that case, the UE can deactivate MICO mode and activate the AS layer at the MBS start time and at any of the scheduled activation times of a multicast MBS session if any of those times are available as specified in 3GPP TS 23.247[ Architectural enhancements for 5G multicast-broadcast services ] [53], and the UE joins one or more multicast MBS sessions by using the UE-requested PDU session establishment procedure or the UE-requested PDU session modification procedure (see subclauses 6.4.1.2 and 6.4.2.2). NOTE 5: It is up to UE implementation whether to leave one or more multicast MBS sessions after each deactivation of each multicast MBS session and to re-join again at the next activation time or to keep a multicast MBS session that the UE has joined for the whole period of the session, as described in 3GPP TS 23.247[ Architectural enhancements for 5G multicast-broadcast services ] [53]. | 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.6 |
6,642 | 4 Overview | Ubiquitous coverage, high reliability and QoS, robust security, and seamless mobility are critical factors to supporting UAS functions over cellular networks. In addition, regulators are investigating safety and performance standards and Registration and licensing programs to develop a well-functioning private and civil UAS ecosystem which can safely coexist with commercial air traffic, general aviation, public and private infrastructure, and the general population. The present document studies the potential use cases and requirements for 3GPP to support remote identification of UAS and the usage of the remote identification. | 3GPP TS 22.825 | Study on Remote Identification of Unmanned Aerial Systems (UAS) | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 4 |
6,643 | 4.13.2.4 Number of successful WLAN releases from the LWA WLAN mobility set | a) This measurement provides the number of successful WLAN releases from the LWA WLAN mobility set. b) CC c) On receipt of RRCConnectionReconfigurationComplete message by the eNB, corresponding to the transmitted RRCConnectionReconfiguration message which includes the wlan-ToReleaseList in the lwa-MobilityConfig of lwa-Configuration information element (see TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [18]). d) An integer value e) LWI.LwaWlanRelSucc f) WLANMobilitySet g) Valid for packet switched traffic h) EPS | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.13.2.4 |
6,644 | 6.9 Physical hybrid ARQ indicator channel | The PHICH carries the hybrid-ARQ ACK/NACK. Multiple PHICHs mapped to the same set of resource elements constitute a PHICH group, where PHICHs within the same PHICH group are separated through different orthogonal sequences. A PHICH resource is identified by the index pair , where is the PHICH group number and is the orthogonal sequence index within the group. For frame structure type 1 and type 3, the number of PHICH groups is constant in all subframes and given by where is provided by higher layers. The index ranges from to . For frame structure type 2, the number of PHICH groups may vary between subframes and is given by where is given by the expression above and is given by Table 6.9-1 with the uplink-downlink configuration provided by the higher-layer parameter subframeAssignment. The index in a subframe with non-zero PHICH resources ranges from to . Table 6.9-1: The factor for frame structure type 2 | 3GPP TS 36.211 | Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation | RAN1 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.9 |
6,645 | 5.2.5 Access control and barring | When the UE needs to transmit an initial NAS message, the UE shall request to establish an RRC Connection first and the NAS shall provide the RRC establishment related information to the lower layer. The RAN handles the RRC Connection with priority during and after RRC Connection Establishment procedure, when UE indicates priority in Establishment related information Under high network load conditions, the network may protect itself against overload by using the Unified Access Control functionality for 3GPP access specified in TS 22.261[ Service requirements for the 5G system ] [2], TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [47] and TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [27] to limit access attempts from UEs. Depending on network configuration, the network may determine whether certain access attempt should be allowed or blocked based on categorized criteria, as specified in TS 22.261[ Service requirements for the 5G system ] [2] and TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [47]. The NG-RAN may broadcast barring control information associated with Access Categories and Access Identities as specified in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [27]. The NG-RAN node may initiate such Unified Access Control when: - AMFs request to restrict the load for UEs that access the network by sending OVERLOAD START message containing conditions defined in clause 5.19.5.2, or - requested by OAM, or - triggered by NG-RAN itself. If the NG-RAN node takes a decision to initiate UAC because of the reception of the N2 interface OVERLOAD START messages, the NG-RAN should only initiate such procedure if all the AMFs relevant to the request contained in the OVERLOAD START message and connected to this NG-RAN node request to restrict the load for UEs that access the network. If the UE supports both N1 and S1 modes NAS and, as defined in TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [26], the UE is configured for Extended Access Barring (EAB) but is not configured with a permission for overriding Extended Access Barring (EAB), when the UE wants to access the 5GS it shall perform Unified Access Control checks for Access Category 1 on receiving an indication from the upper layers as defined in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [47], TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [28], TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [51]. If the UE supports both N1 and S1 modes NAS and, as defined in TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [26], the UE is configured with a permission for overriding Extended Access Barring (EAB), when the UE wants to access the 5GS it shall ignore Unified Access Control checks for Access Category 1 on receiving an indication from the upper layers, as defined in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [47]. NOTE: UE signalling of Low Access Priority indication over N1 in 5GS is not supported in this release of the specification. Operator may provide one or more PLMN-specific Operator-defined access category definitions to the UE using NAS signalling, and the UE handles the Operator-defined access category definitions stored for the Registered PLMN, as specified in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [47]. The access control for the Disaster Roaming is described in TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [17] and TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [47]. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.5 |
6,646 | .1 FDD | For the parameters specified in Table .1-1, and using the downlink physical channels specified in Annex C.3.2, the minimum requirements are specified in Table 9.3.6.1-2 and by the following a) a sub-band differential CQI offset level of 0 shall be reported at least % of the time but less than % for each sub-band for CSI process 1, 2, or 3; b) a CQI index not in the set {median CQI -1, median CQI, median CQI +1} shall be reported at least % of the time for CSI process 0; c) the difference of the median CQIs of the reported wideband CQI for configurated CSI processes shall be greater or equal to the values as in Table .1-3; d) the ratio of the throughput obtained when transmitting on a randomly selected sub-band among the sub-bands with the highest differential CQI offset level the corresponding TBS and that obtained when transmitting the TBS indicated by the reported wideband CQI median on a randomly selected sub-band in set S shall be ≥ ; e) when transmitting on a randomly selected sub-band among the sub-bands with the highest differential CQI offset level the corresponding TBS, the average BLER for the indicated transport formats shall be greater or equal to 0.02. The requirements only apply for sub-bands of full size and the random scheduling across the sub-bands is done by selecting a new sub-band in each TTI for FDD, each available downlink transmission instance for TDD. Sub-bands of a size smaller than full size are excluded from the test. Table .1-1: Fading test for FDD Table .1-2: Minimum requirement (FDD) Table .1-3: Minimum median CQI difference between configured CSI processes (FDD) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | .1 |
6,647 | 5.5.1 In-band tones and announcements | When the network wants to make the mobile station attach the user connection (e.g. in order to provide in-band tones/announcement) before the mobile station has reached the "active" state of a call, the network may include a progress indicator IE indicating user attachment in a suitable CC message: - Either it includes the IE in a SETUP, CALL PROCEEDING, ALERTING, or CONNECT message that is send during call establishment - it sends a PROGRESS message containing the IE. A progress indicator IE indicates user attachment if it specifies a progress description in the set {1, 2, 3} or in the set {6, 7, 8, ..., 20}. On reception of a SETUP, CALL PROCEEDING, ALERTING, CONNECT, or PROGRESS message the mobile station shall proceed as specified elsewhere in clause 5; if the progress indicator IE indicated user attachment and a speech mode traffic channel is appropriate for the call the mobile station shall in addition: attach the user connection for speech as soon as an appropriate channel in speech mode is available. (If a new order to attach the user connection is received before the attachment has been performed, the new order shall supersede the previous one.) Under certain conditions the MS will have to attach the user connection before the CONNECT message. It is up to the network to ensure that no undesired end-to-end through connection takes place during the establishment of a MT call. NOTE: This allows the use of progress indicator IEs independently from the channel modes appropriate for the call. The network may generate multimedia CAT to a mobile station supporting multimedia CAT during the alerting phase of a mobile originated multimedia call establishment as specified in subclause 5.3.6.4. | 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.5.1 |
6,648 | 8.4.4.3 SN initiated SN Modification with SCG Activation or Deactivation | Figure 8.4.4.3-1: SCG Activation or Deactivation in SN initiated SN Modification procedure 1. SCG is deactivated or activated. 2. The SN-CU-CP may send the BEARER CONTEXT MODIFICATION REQUEST message to the SN-CU-UP to notify the SCG activation or deactivation. 3. The SN-CU-UP sends the BEARER CONTEXT MODIFICATION RESPONSE message to the SN-CU-CP. 4. The SN-CU sends the UE CONTEXT MODIFICATION REQUEST message to the SN-DU to indicate the request of SCG activation or deactivation. 5. The SN-DU sends the UE CONTEXT MODIFICATION RESPONSE message to the SN-CU, indicates the SCG status. 6. The SN-CU-CP may send the BEARER CONTEXT MODIFICATION REQUEST message to the SN-CU-UP to notify the SCG status. 7. The SN-CU-UP sends the BEARER CONTEXT MODIFICATION RESPONSE message to the SN-CU-CP. NOTE 1: Step 6 and 7 may be skipped in case the SN-DU accepted the SCG activation or deactivation request. 8. The SN sends the SN Modification Required message to the MN, indicates the request of SCG activation or deactivation. 9. The MN-CU-CP may send the BEARER CONTEXT MODIFICATION REQUEST message to the MN-CU-UP to notify the SCG status. 10. The MN-CU-UP sends the BEARER CONTEXT MODIFICATION RESPONSE message to the MN-CU-CP. NOTE 2: Based on implementation, step 9 and 10 can be performed after step 11. 11. The MN sends the SN Modification Confirm message to the SN. NOTE 3: Step 8-11 are not performed in case the SN-DU rejected the SCG activation or deactivation request. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 8.4.4.3 |
6,649 | 17.6.6 RE-Auth-Answer Command | The Re-Auth-Answer (RAA) command, defined in IETF RFC 6733 (DIAMETER BASE) [111], is indicated by the Command-Code set to 258 and the message flags’ ‘R’ bit clear, is sent in response to the RAR. The relevant AVPs that are of use for the Gmb interface are detailed in the ABNF description below. Other valid AVPs for this command are not used for Gmb purposes and should be ignored by the receiver or processed according to the relevant specifications. The bold marked AVPs in the message format indicate new optional AVPs for Gmb, or modified existing AVPs. Message Format: <RAA> ::= < Diameter Header: 258, PXY > < Session-Id > { Origin-Host } { Origin-Realm } [ Result-Code ] [ Experimental-Result ] [ MBMS-StartStop-Indication ] [ MBMS-GGSN-Address ] ; for unicast encapsulated user data [ MBMS-GGSN-IPv6-Address ] ; for unicast encapsulated user data [ MBMS-GW-UDP-Port] ; for unicast encapsulated user data [ MBMS-User-Data-Mode-Indication ] [ Origin-State-Id ] [ Error-Message ] [ Error-Reporting-Host ] [ Failed-AVP ] * [ Redirected-Host ] [ Redirected-Host-Usage ] [ Redirected-Host-Cache-Time ] * [ Proxy-Info ] If multicast user plane data are to be sent to the GGSN using IP unicast, the GGSN shall allocate an IP transport address and a separate UDP port for each MBMS bearer ( i.e the service uniquely identified by its TMGI and Flow ID and provided by the GPRS to deliver the same IP datagrams to multiple receivers in a designated location). The GGSN shall then use the destination unicast IP address and destination UDP port of user plane packets received over the Gi interface to determine on which MBMS bearer to forward the received user plane packet. | 3GPP TS 29.061 | Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) | CT WG3 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 17.6.6 |
6,650 | 9.10.2.1 FDD | The requirements are specified in Table 9.10.2.1-4, with the additional parameters in Table 9.10.2.1-1, Table 9.10.2.1-2 and Table 9.10.2.1-3. In Table 9.10.2.1-1, transmission point 1 (TP 1) is the serving cell transmitting PDCCH, synchronization signals, PBCH and can transmit PDSCH, and transmission point 2 (TP 2) has different Cell ID and can transmit PDSCH. The downlink physical channel setup for TP 1 is according to Table C.3.2 and for TP 2 according to Table C.3.2. Table 9.10.2.1-1: Test Parameters Table 9.10.2.1-2: Configurations of PQI and DL transmission hypothesis for each PQI set (Fixed TP1 case) Table 9.10.2.1-3: Configurations of PQI and DL transmission hypothesis for each PQI set (Follow CRI case) Table 9.10.2.1-4: Minimum requirement (FDD) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 9.10.2.1 |
6,651 | 16.9.7 Power Savings Resource Allocation | The SL UE in Mode 2 can support partial sensing-based resource allocation and random resource selection as power saving resource allocation methods. A SL mode 2 TX resource pool can be (pre)configured to allow full sensing only, partial sensing only, random selection only, or any combination(s) thereof. A UE decides which resource allocation scheme(s) can be used in the AS based on its capability (for a UE in RRC_IDLE/RRC_INACTIVE/OOC) and the allowed resource schemes in the resource pool configuration. Random resource selection is applicable to both periodic and aperiodic traffic. A UE capable for partial sensing can perform periodic-based partial sensing and/or contiguous partial sensing for resource (re)selection. Periodic-based partial sensing can only be performed if periodic resource reservation is configured in the resource pool. In periodic-based partial sensing, the UE monitors slots in periodic sensing occasion(s) for a given resource reservation periodicity. Contiguous partial sensing is performed by a UE capable of partial sensing when resource (re)selection is triggered by a UE in a TX pool configured with partial sensing. In contiguous partial sensing, the UE monitors slots in a contiguous sensing window which occur prior to the selected transmission resource. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.9.7 |
6,652 | 8.13.2.4 Management based MDT Activation in gNB-CU-UP | The signalling flow for Management based MDT Activation in gNB-CU-UP is shown in Figure 8.13.2.4-1. Figure 8.13.2.4-1 Management based MDT Activation in gNB-CU-UP 1. The gNB-CU-CP sends BEARER CONTEXT SETUP REQUEST message to the gNB-CU-UP, including Management based MDT PLMN List. The message may include Polluted Measurement Indicator. If the gNB-DU has received the Polluted Measurement Indicator IE, the gNB-DU includes the information contained in such indicator as part of the measurement report to be sent to the TCE so that the TCE is able to correlate and filter the affected measurements. 2. The gNB-CU-UP sends BEARER CONTEXT SETUP RESPONSE message to the gNB-CU-CP. 3. The EM sends a Trace Session activation request to the gNB-CU-UP. This request includes the parameters for configuring UE measurements. 4. The gNB-CU-UP shall select the suitable UEs for MDT data collection. If the serving PLMN is not within the Management Based MDT PLMN List the UE shall not be selected by the gNB-CU-UP for MDT data collection as defined in TS 32.422[ Telecommunication management; Subscriber and equipment trace; Trace control and configuration management ] [20]. For each selected UE, the gNB-CU-UP may send CELL TRAFFIC TRACE message to the gNB-CU-CP in the E1 UE associated signalling, including Trace ID for MDT 5. Upon reception of a CELL TRAFFIC TRACE message from E1, the gNB-CU-CP shall send CELL TRAFFIC TRACE message to the AMF for this UE, including Trace ID for MDT. The AMF forwards Trace ID and other information to the TCE as specified in TS 32.422[ Telecommunication management; Subscriber and equipment trace; Trace control and configuration management ] [20]. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 8.13.2.4 |
6,653 | 4.3.1 TMSI reallocation procedure 4.3.1.0 General | The purpose of the TMSI reallocation procedure is to provide identity confidentiality, i.e. to protect a user against being identified and located by an intruder (see 3GPP TS 42.009[ Security aspects ] [5], 3GPP TS 43.020[ Security related network functions ] [13] and 3GPP TS 33.102[ 3G security; Security architecture ] [5a]). If the identity confidentiality service is applied for an IMSI, a Temporary Mobile Subscriber Identity (TMSI) is used for identification within the radio interface signalling procedures. In a network supporting the feature 'Intra domain connection of RAN nodes to multiple CN nodes' a TMSI shall be allocated to each IMSI attached mobile station. See 3GPP TS 23.236[ Intra-domain connection of Radio Access Network (RAN) nodes to multiple Core Network (CN) nodes ] [94], subclause 4.3. The structure of the TMSI is specified in 3GPP TS 23.003[ Numbering, addressing and identification ] [10]. The TMSI has significance only within a location area. Outside the location area it has to be combined with the Location Area Identifier (LAI) to provide for an unambiguous identity. Usually the TMSI reallocation is performed at least at each change of a location area. (Such choices are left to the network operator). The reallocation of a TMSI can be performed either by a unique procedure defined in this subclause or implicitly by a location updating procedure using the TMSI. The implicit reallocation of a TMSI is described together with that procedure. If a TMSI provided by a mobile station is unknown in the network e.g. due to a data base failure, the network may require the mobile station to provide its International Mobile Subscriber Identity (IMSI). In this case the identification procedure (see subclause 4.3.3) should be used before the TMSI reallocation procedure may be initiated. The TMSI reallocation can be initiated by the network at any time whilst a RR connection exists between the network and the mobile station. NOTE 1: Usually the TMSI reallocation is performed in ciphered mode. NOTE 2: Normally the TMSI reallocation will take place in conjunction with another procedure, e.g. at location updating or at call setup (see 3GPP TS 29.002[ Mobile Application Part (MAP) specification ] [37]). NOTE 3: The explicit TMSI reallocation procedure is started by the network only if the mobile station is updated in the current location area or if a location updating procedure is ongoing for that particular mobile station, or if the network wishes to send a non-broadcast LAI according to 3GPP TS 23.236[ Intra-domain connection of Radio Access Network (RAN) nodes to multiple Core Network (CN) nodes ] [94] to the mobile station. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.3.1 |
6,654 | 5.27.1.7 Support for PTP grandmaster function in 5GS | The 5GS that is configured to operate as a time-aware system or Boundary Clock may support acting as a PTP grandmaster for a (g)PTP domain. The configuration of PTP instances in DS-TT and NW-TT for PTP grandmaster function is described in clause K.2. The following options may be supported (per DS-TT) for the 5GS to generate the Sync, Follow_Up and Announce messages for the Leader ports on the DS-TT: a) NW-TT generates the Sync, Follow_Up and Announce messages on behalf of DS-TT (e.g. if DS-TT does not support this). The NW-TT/UPF forwards the generated Sync, Follow_Up and Announce messages to the PDU session(s) related to the Leader ports on the DS-TT(s). The NW-TT timestamps the (g)PTP event message when the event message is sent to the PDU Session, and adds TSi corresponding to the timestamp to the Sync message and the OriginTimestamp corresponding to the timestamp to Sync message (if one-step operation is used) or PreciseOriginTimestamp corresponding to the timestamp to Follow_Up message (if two-step operation is used), and sets the cumulative rateRatio value with 1. The OriginTimestamp or PreciseOriginTimestamp shall be set by NW-TT/UPF to the 5GS internal clock. When DS-TT(s) receive the Sync, Follow_Up messages, it modifies the payload of the Sync, Follow_Up message as described for the PTP port in the egress TT in clause 5.27.1.2.2.2. b) DS-TT generates the Sync, Follow_Up and Announce messages in this DS-TT. The OriginTimestamp or PreciseOriginTimestamp shall be set by DS-TT to the 5GS internal clock. In both options, the NW-TT generates the Sync, Follow_Up and Announce messages for the Leader ports on the NW-TT. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.27.1.7 |
6,655 | 8.15.2.2.1 Eight Layer Spatial Multiplexing (User-Specific Reference Symbols) | 8.15.2.2.1.1 Minimum Requirement Eight-Layer Spatial Multiplexing 8 Tx Antenna Port The purpose of these tests is to verify the closed loop rank-eight performance with frequency selective precoding with 8Tx and 8Rx under CA. For CA with 2 DL CCs, the requirements are specified in Table 8.15.2.2.1.1-3, based on single carrier requirement specified in Table 8.15.2.2.1.1-2, with the addition of the parameters in Table 8.15.2.2.1.1-1 and the downlink physical channel setup according to Annex C.3.2. Table 8.15.2.2.1.1-1: Test Parameters for Multi-Layer Spatial Multiplexing (FRC) for CA Table 8.15.2.2.1.1-2: Single carrier performance for multiple CA configurations Table 8.15.2.2.1.1-3: Minimum performance (FRC) based on single carrier performance for CA with 2 DL CCs | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.15.2.2.1 |
6,656 | 6.6.1G Occupied bandwidth for V2X Communication | When UE is configured for E-UTRA V2X sidelink transmissions non-concurrent with E-UTRA uplink transmissions for E-UTRA V2X operating bands specified in Table Table 5.5G-1, the requirements in subclause 6.6.1 apply for E-UTRA V2X sidelink transmission. When UE is configured for simultaneous E-UTRA V2X sidelink and E-UTRA uplink transmissions for inter-band E-UTRA V2X / E-UTRA bands specified in Table 5.5G-2, the requirements in subclause 6.6.1 apply for V2X sidelink transmission and the E-UTRA uplink transmission. For intra-band contiguous multi-carrier operation, the occupied bandwidth is a measure of the bandwidth containing 99 % of the total integrated power of the transmitted spectrum. The OBW shall be less than the aggregated channel bandwidth defined in subclause . For V2X UE supporting Transmit Diversity, if the UE transmits on two antenna connectors at the same time, the requirements for occupied bandwidth is specified at each transmit antenna connector and the occupied bandwidth at each transmitter antenna shall be less than the channel bandwidth specified for single carrier. If V2X UE transmits on one antenna connector at a time, the requirements specified for single carrier shall apply to the active antenna connector. | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.6.1G |
6,657 | 6 Transmitter characteristics 6.1 General | Unless otherwise stated, the transmitter characteristics are specified at the antenna connector of the UE with a single or multiple transmit antenna(s). For UE with integral antenna only, a reference antenna with a gain of 0 dBi is assumed. Unless otherwise stated, NB1 and NB2 requirements specified for an E-UTRA band shall also apply for the re-farmed NR band (e.g. if NB1/NB2 requirements are specified for E-UTRA band 1, they shall also apply for NR band n1). The requirements of clause 6 do not apply to devices only supporting LTE based 5G terrestrial broadcast. | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6 |
6,658 | 5.7.5.3 Actions related to transmission of FailureInformation message | The UE shall: 1> if initiated to provide RLC failure information, set FailureInfoRLC-Bearer as follows: 2> set logicalChannelIdentity to the logical channel identity of the failing RLC bearer; 2> set cellGroupId to the cell group identity of the failing RLC bearer; 2> set the failureType as rlc-failure; 1> if initiated to provide DAPS failure information, set FailureInfoDAPS as follows: 2> set the failureType as daps-failure; 1> if used to inform the network about a failure for an MCG RLC bearer or DAPS failure information: 2> submit the FailureInformation message to lower layers for transmission via SRB1; 1> else if used to inform the network about a failure for an SCG RLC bearer: 2> if SRB3 is configured; 3> submit the FailureInformation message to lower layers for transmission via SRB3; 2> else; 3> if the UE is in (NG)EN-DC: 4> submit the FailureInformation message via E-UTRA SRB1 embedded in E-UTRA RRC message ULInformationTransferMRDC as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10]. 3> else if the UE is in NR-DC: 4> submit the FailureInformation message via SRB1 embedded in NR RRC message ULInformationTransferMRDC as specified in clause 5.7.2a.3. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.7.5.3 |
6,659 | 6.6.2.4 Abnormal cases in the UE | The following abnormal cases can be identified: a) Expiry of timer T3586: On the first expiry of the timer T3586, the UE shall resend the REMOTE UE REPORT message and shall reset and restart timer T3586. This retransmission is repeated two times, i.e. on the third expiry of timer T3586, the UE shall abort the procedure and release any resources for this procedure. NOTE: After the abortion of the remote UE report procedure, the remote UE report procedure for the remote UE(s) can be restarted and how to restart the procedure is left to UE implementation. b) Collision of network-requested PDU session release procedure and remote UE report procedure: If the UE receives a PDU SESSION RELEASE COMMAND message during the remote UE report procedure, and the PDU session indicated in the PDU SESSION RELEASE COMMAND message is the PDU session ID that the UE had indicated in the REMOTE UE REPORT message, the UE shall abort the remote UE report procedure and proceed with the network-requested PDU session release procedure. | 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.6.2.4 |
6,660 | 5.2.19.2 Naf_EventExposure service 5.2.19.2.1 General | Service description: This service enables consumer NF to subscribe and get notified of events. The events can be subscribed by a NF consumer are described in TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [50]. The following service operations are defined for the Naf_EventExposure service: - Naf_EventExposure_Subscribe. - Naf_EventExposure_Unsubscribe. - Naf_EventExposure_Notify. The following events can be subscribed by a NF consumer (Event ID is defined in clause 4.15.1): - Service Experience information, as defined in clause 6.4.2 of TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [50]. - Performance Data information, as defined in clauses 6.4.2 and clause 6.14.2 of TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [50]. - Collective Behaviour information, as defined in clause 6.5.2 of TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [50]. - UE Mobility information, as defined in clause 6.7.2.2 of TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [50]. - UE Communication information, as defined in clause 6.7.3.2 of TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [50]. - Exceptions information, as defined in clause 6.7.5.2 of TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [50]. - User Data Congestion information, as defined in clause 6.8.2 of TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [50]. - UE Data volume Dispersion information, as defined in clause 6.10.2 of TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [50]. - DN Performance information, as defined in clause 6.14.2 of TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [50]. - E2E data volume transfer time information, as defined in clause 6.18.2 of TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [50]. - Relative Proximity information, as defined in clause 6.19.2 of TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [50]. Event Filters are used to specify the conditions to match for notifying the event (i.e. "List of Parameter values to match"). If there are no conditions to match for a specific Event ID, then the Event Filter is not provided. The following table provides some examples on how the conditions to match for event reporting can be specified for various Event IDs for AF exposure. Table 5.2.19.2.1-1: Example of Event Filters for AF exposure events | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.19.2 |
6,661 | C.2.1 Definition of types of information | There are three different types of information that the calling PLMN user may specify during call setup to identify low layer capabilities needed in the network and in the destination terminal: a) type I information is information about the calling terminal which is only used at the destination end to allow a decision regarding terminal compatibility. An example would be the user information layer 3 protocol. Type I information is encoded in octets 5 to 7 of the low layer compatibility information element; b) type II information is only used by the network (PLMN) to which the calling user is connected for selection of PLMN specific network resources, e.g. channel type or specific functionality within the interworking function (IWF, see 3GPP TS 23.093[ Technical realization of Completion of Calls to Busy Subscriber (CCBS); Stage 2 ] [88a]). This type of information is always present. An example is the connection element. Type II information is coded in: i) octet 3 of the bearer capability information element when the information transfer capability required by the calling user is speech ; ii) octets 3, 4, 5, and optionally octet 7 of the bearer capability information element when the information transfer capability required by the calling user is not speech; c) type III information is required for selection of a basic service from the choice of basic services offered by the network and together with type II information for selection of an appropriate interworking function (IWF, see 3GPP TS 29.007[ General requirements on interworking between the Public Land Mobile Network (PLMN) and the Integrated Services Digital Network (ISDN) or Public Switched Telephone Network (PSTN) ] [38]), as well as for terminal compatibility checking at the destination terminal. An example is the information transfer capability. Type III information is always present and is encoded in: i) octet 3 of the bearer capability information element when the information transfer capability required by the calling user is speech ; ii) octets 3, 5, 6, 6a, 6b and 6c of the bearer capability information element when the information transfer capability required by the calling user is not speech; | 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 | C.2.1 |
6,662 | 6.4.7 Security aspects of SMS over NAS | Specific services of SMS over NAS are defined in TS 23.501[ System architecture for the 5G System (5GS) ] [2], and procedures for SMS over NAS are specified in TS 23.502[ Procedures for the 5G System (5GS) ] [8]. For registration and de-registration procedures for SMS over NAS, the details are specified in subclause 4.13.3.1 and 4.13.3.2 in TS 23.502[ Procedures for the 5G System (5GS) ] [8]. The NAS message can be protected by NAS security mechanisms. For MO/MT SMS over NAS via 3GPP/non-3GPP when the UE has already activated NAS security with the AMF before sending/receiving SMS, the NAS Transport message shall be ciphered and integrity protected using the NAS security context by the UE/AMF as described in sub-clause 6.4 in the present document. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.4.7 |
6,663 | 5.3.2.4 Support of a UE registered over both 3GPP and Non-3GPP access | This clause applies to Non-3GPP access network corresponding to the Untrusted Non-3GPP access network, to the Trusted Non-3GPP and to the W-5GAN. In the case of W-5GAN the UE mentioned in this clause corresponds to the 5G-RG. For a given serving PLMN there is one RM context for a UE for each access, e.g. when the UE is consecutively or simultaneously served by a 3GPP access and by a non-3GPP access (i.e. via an N3IWF, TNGF and W-AGF) of the same PLMN. UDM manages separate/independent UE Registration procedures for each access. When served by the same PLMN for 3GPP and non-3GPP accesses, an UE is served by the same AMF except in the temporary situation described in clause 5.17 i.e. after a mobility from EPS while the UE has PDU Sessions associated with non-3GPP access. The 5G NSWO authentication as defined in Annex S of TS 33.501[ Security architecture and procedures for 5G System ] [29] does not impact the RM state. An AMF associates multiple access-specific RM contexts for an UE with: - a 5G-GUTI that is common to both 3GPP and Non-3GPP accesses. This 5G-GUTI is globally unique. - a Registration state per access type (3GPP / Non-3GPP) - a Registration Area per access type: one Registration Area for 3GPP access and another Registration Area for non 3GPP access. Registration Areas for the 3GPP access and the Non-3GPP access are independent. - timers for 3GPP access: - a Periodic Registration timer; and - a Mobile Reachable timer and an Implicit Deregistration timer. - timers for non-3GPP access: - a UE Non-3GPP Deregistration timer; and - a Network Non-3GPP Implicit Deregistration timer. The AMF shall not provide a Periodic Registration Timer for the UE over a Non-3GPP access. Consequently, the UE need not perform Periodic Registration Update procedure over Non-3GPP access. Instead, during the Initial Registration procedure and Re-registration, the UE is provided by the network with a UE Non-3GPP Deregistration timer that starts when the UE enters non-3GPP CM-IDLE state. When the 3GPP access and the non-3GPP access for the same UE are served by the same PLMN, the AMF assigns the same 5G-GUTI for use over both accesses. Such a 5G-GUTI may be assigned or re-assigned over any of the 3GPP and Non-3GPP accesses. The 5G-GUTI is assigned upon a successful registration of the UE, and is valid over both 3GPP and Non-3GPP access to the same PLMN for the UE. Upon performing an initial access over the Non-3GPP access or over the 3GPP access while the UE is already registered with the 5G System over another access of the same PLMN, the UE provides the native 5G-GUTI for the other access. This enables the AN to select an AMF that maintains the UE context created at the previous Registration procedure via the GUAMI derived from the 5G-GUTI, and enables the AMF to correlate the UE request to the existing UE context via the 5G-GUTI. If the UE is performing registration over one access and intends to perform registration over the other access in the same PLMN (e.g. the 3GPP access and the selected N3IWF, TNGF or W-AGF are located in the same PLMN), the UE shall not initiate the registration over the other access until the Registration procedure over first access is completed. NOTE: To which access the UE performs registration first is up to UE implementation. When the UE is successfully registered to an access (3GPP access or Non-3GPP access respectively) and the UE registers via the other access: - if the second access is located in the same PLMN (e.g. the UE is registered via a 3GPP access and selects a N3IWF, TNGF or W-AGF located in the same PLMN), the UE shall use for the registration to the PLMN associated with the new access the 5G-GUTI that the UE has been provided with at the previous registration or UE configuration update procedure for the first access in the same PLMN. Upon successful completion of the registration to the second access, if the network included a 5G-GUTI in the Registration Accept, the UE shall use the 5G-GUTI received in the Registration Accept for both registrations. If no 5G-GUTI is included in the Registration Accept, then the UE uses the 5G-GUTI assigned for the existing registration also for the new registration. - if the second access is located in a PLMN different from the registered PLMN of the first access (i.e. not the registered PLMN), (e.g. the UE is registered to a 3GPP access and selects a N3IWF, TNGF or W-AGF located in a PLMN different from the PLMN of the 3GPP access, or the UE is registered over Non-3GPP and registers to a 3GPP access in a PLMN different from the PLMN of the N3IWF, TNGF or W-AGF), the UE shall use for the registration to the PLMN associated with the new access a 5G-GUTI only if it has got one previously received from a PLMN that is not the same as the PLMN the UE is already registered with. If the UE does not include a 5G-GUTI, the SUCI shall be used for the new registration. Upon successful completion of the registration to the second access, the UE has the two 5G-GUTIs (one per PLMN). A UE supporting registration over both 3GPP and Non-3GPP access to two PLMNs shall be able to handle two separate registrations, including two 5G-GUTIs, one per PLMN, and two associated equivalent PLMN lists. When a UE 5G-GUTI assigned during a Registration procedure over 3GPP (e.g. the UE registers first over a 3GPP access) is location-dependent, the same UE 5G-GUTI can be re-used over the Non-3GPP access when the selected N3IWF, TNGF or W-AGF function is in the same PLMN as the 3GPP access. When an UE 5G-GUTI is assigned during a Registration procedure performed over a Non 3GPP access (e.g. the UE registers first over a non-3GPP access), the UE 5G-GUTI may not be location-dependent, so that the UE 5G-GUTI may not be valid for NAS procedures over the 3GPP access and, in this case, a new AMF is allocated during the Registration procedure over the 3GPP access. When the UE is registered first via 3GPP access, if the UE registers to the same PLMN via Non-3GPP access, the UE shall send the GUAMI obtained via 3GPP access to the N3IWF, TNGF or W-AGF, which uses the received GUAMI to select the same AMF as the 3GPP access. The Deregistration Request message indicates whether it applies to the 3GPP access the Non-3GPP access, or both. If the UE is registered on both 3GPP and Non-3GPP accesses and it is in CM-IDLE over Non-3GPP access, then the UE or AMF may initiate a Deregistration procedure over the 3GPP access to deregister the UE only on the Non-3GPP access, in which case all the PDU Sessions which are associated with the Non-3GPP access shall be released. If the UE is registered on both 3GPP and non-3GPP accesses and it is in CM-IDLE over 3GPP access and in CM-CONNECTED over non-3GPP access, then the UE may initiate a Deregistration procedure over the non-3GPP access to deregister the UE only on the 3GPP access, in which case all the PDU Sessions which are associated with the 3GPP access shall be released. Registration Management over Non-3GPP access is further defined in clause 5.5.1. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.3.2.4 |
6,664 | 4.9 Paging Policy Differentiation | Paging policy differentiation is an optional feature that allows the MME, based on operator configuration, to apply different paging strategies as defined in clause 5.3.4.3 for different traffic or service types provided within the same PDN connection. When it supports Paging Policy Differentiation feature, the Serving GW provides a Paging Policy Indication in the Downlink Data Notification. The Paging Policy Indication is based on information received with the downlink packet that triggers the Downlink Data Notification. For example, as defined in TS 23.228[ IP Multimedia Subsystem (IMS); Stage 2 ] [52], the P-CSCF may support Paging Policy Differentiation by marking packet(s) to be sent towards the UE that relate to specific IMS services (e.g. conversational voice as defined in IMS multimedia telephony service). NOTE 1: This Paging Policy Differentiation feature can be used to determine the Paging Cause Indication for Voice Service, as described in clause 4.3.33.3. The PDN GW shall not modify the received downlink IP packet e.g. the DSCP (IPv4) / TC (IPv6). Unconditionally, for each bearer and for each packet of PDN type IPv4, IPv6 or IPv4v6 that triggers a Downlink Data Notification, the SGW shall send the DSCP in TOS (IPv4) / TC (IPv6) information received in the IP payload of the GTP-U packet from the PDN GW in the Paging Policy Indication in the Downlink Data Notification. It shall be possible for the operator to configure the MME in such a way that the Paging Policy Indicator only applies to certain HPLMNs and/or APNs and/or QCIs. NOTE 2: Network configuration needs to ensure that the information used as a trigger for Paging Policy Indication is not changed within the EPS. NOTE 3: Network configuration needs to ensure that the specific DSCP in TOS (IPv4) / TC (IPv6) value, used as a trigger for Paging Policy Indication, is managed correctly in order to avoid the accidental use of certain paging policies. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.9 |
6,665 | 9.11.3.51 SOR transparent container | The purpose of the SOR transparent container information element in the REGISTRATION ACCEPT message is to provide the list of preferred PLMN/access technology combinations (or HPLMN indication that 'no change of the "Operator Controlled PLMN Selector with Access Technology" list stored in the UE is needed and thus no list of preferred PLMN/access technology combinations is provided'), or a secured packet (see 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5] annex C) and optional indication of an acknowledgement request, SOR-CMCI, request the storage of the received SOR-CMCI in the ME, and SOR-SNPN-SI (or subscribed SNPN or HPLMN indication that 'no change of the SOR-SNPN-SI stored in the UE is needed and thus no SOR-SNPN-SI is provided'). The purpose of the SOR transparent container information element in the REGISTRATION COMPLETE message is to indicate the UE acknowledgement of successful reception of the SOR transparent container IE in the REGISTRATION ACCEPT message as well as to indicate the ME support of SOR-CMCI and the ME support of SOR-SNPN-SI. NOTE 1: When used in NAS transport procedure, the contents of the SOR transparent container information element in the Payload container IE of the DL NAS TRANSPORT message are used to provide the list of preferred PLMN/access technology combinations and optional indication of an acknowledgement request, SOR-CMCI, request the storage of the received SOR-CMCI in the ME, and SOR-SNPN-SI. The contents of the SOR transparent container information element in the Payload container IE of the UL NAS TRANSPORT message are used to indicate the UE acknowledgement of successful reception of the SOR transparent container IE in the DL NAS TRANSPORT message as well as to indicate the ME support of SOR-CMCI and the ME support of SOR-SNPN-SI. NOTE 2: The "Operator controlled signal threshold per access technology" content to update the USIM file EFOCST (see 3GPP TS 31.102[ Characteristics of the Universal Subscriber Identity Module (USIM) application ] [22]) can be included in the secured packet of the SOR transparent container. The SOR transparent container information element is coded as shown in figure 9.11.3.51.1, figure 9.11.3.51.2, figure 9.11.3.51.3, figure 9.11.3.51.4, figure 9.11.3.51.5, figure 9.11.3.51.6, figure 9.11.3.51.7, figure 9.11.3.51.8, figure 9.11.3.51.9, figure 9.11.3.51.9A, figure 9.11.3.51.10, figure 9.11.3.51.11, figure 9.11.3.51.11A, figure 9.11.3.51.11B, figure 9.11.3.51.11C, figure 9.11.3.51.11D, figure 9.11.3.51.11E, figure 9.11.3.51.11F, figure 9.11.3.51.11G, figure 9.11.3.51.11H, figure 9.11.3.51.11I, figure 9.11.3.51.12, figure 9.11.3.51.13, table 9.11.3.51.1, table 9.11.3.51.2, table 9.11.3.51.3, table 9.11.3.51.4, table 9.11.3.51.4A, table 9.11.3.51.5 and table 9.11.3.51.6. The SOR transparent container is a type 6 information element with a minimum length of 20 octets. Figure 9.11.3.51.1: SOR transparent container information element for list type with value "0" and SOR data type with value "0" Figure 9.11.3.51.2: SOR transparent container information element for list type with value "1", SOR data type with value "0", and additional parameters with value "0" Figure 9.11.3.51.2A: SOR transparent container information element for list type with value "1", SOR data type with value "0", additional parameters with value "1" Figure 9.11.3.51.3: PLMN ID and access technology list (m=22+5*n) Figure 9.11.3.51.4: SOR transparent container information element for SOR data type with value "1" Figure 9.11.3.51.5: SOR header for SOR data type with value "0" Figure 9.11.3.51.6: SOR header for SOR data type with value "1" Table 9.11.3.51.1: SOR transparent container information element Figure 9.11.3.51.7: SOR-CMCI Table 9.11.3.51.2: SOR-CMCI Figure 9.11.3.51.8: SOR-CMCI rule Table 9.11.3.51.3: SOR-CMCI rule Figure 9.11.3.51.9: SOR-SNPN-SI Table 9.11.3.51.4: SOR-SNPN-SI Figure 9.11.3.51.9A: SOR-SNPN-SI-LS Table 9.11.3.51.4A: SOR-SNPN-SI-LS Figure 9.11.3.51.10: CH controlled prioritized list of preferred SNPNs Figure 9.11.3.51.10A: CH controlled prioritized list of preferred SNPNs for access for localized services in SNPN Figure 9.11.3.51.10B: SNPN info Figure 9.11.3.51.11: SNPN identity Figure 9.11.3.51.11A: Time validity information Figure 9.11.3.51.11B: Location assistance information Figure 9.11.3.51.11C: Geographical area descriptions Figure 9.11.3.51.11D: Tracking area information of PLMNs Figure 9.11.3.51.11E: Tracking area information of PLMN Figure 9.11.3.51.11F: TAC list Figure 9.11.3.51.11G: Tracking area information of SNPNs Figure 9.11.3.51.11H: Tracking area information of SNPN Figure 9.11.3.51.11I: Location validity information Table 9.11.3.51.5: CH controlled prioritized list of preferred SNPNs and CH controlled prioritized list of preferred SNPNs for access for localized services in SNPN Figure 9.11.3.51.12: CH controlled prioritized list of GINs Figure 9.11.3.51.12A: CH controlled prioritized list of preferred GINs for access for localized services in SNPN Figure 9.11.3.51.12B: GIN info Figure 9.11.3.51.13: GIN Table 9.11.3.51.6: CH controlled prioritized list of GINs and CH controlled prioritized list of preferred GINs for access for localized services in SNPN | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.11.3.51 |
6,666 | 5.2.7 UE Radio Capability ID | The UE Radio Capability ID is a short pointer with format defined in TS 23.003[ Numbering, addressing and identification ] [9] that is used to uniquely identify a set of UE Radio Capabilities (excluding UTRAN and NB-IoT capabilities). The UE Radio Capability ID is assigned either by the serving PLMN or by the UE manufacturer, as follows: - UE manufacturer-assigned: The UE Radio Capability ID may be assigned by the UE manufacturer in which case it includes the UE manufacturer information (i.e. a Vendor ID). In this case, the UE Radio Capability ID uniquely identifies a set of UE radio capabilities and the UE Radio Capability for Paging for this manufacturer in any PLMN. - PLMN-assigned: If a UE manufacturer-assigned UE Radio Capability ID is not used by the UE or the serving network, or it is not recognised by the serving PLMN UCMF, the UCMF may allocate UE Radio Capability IDs for the UE corresponding to different sets of UE radio capabilities the PLMN may receive from the UE at different times. In this case, the UE Radio Capability IDs the UE receives are applicable to the serving PLMN and uniquely identify the corresponding sets of UE radio capabilities and the UE Radio Capability for Paging(s) in this PLMN. The PLMN assigned UE Radio Capability ID includes a Version ID in its format. The value of the Version ID is the one configured in the UCMF, at time the UE Radio Capability ID value is assigned. The Version ID value makes it possible to detect whether a UE Radio Capability ID is current or outdated. NOTE: For the case the PLMN is configured to store PLMN assigned IDs in the UE manufacturer-assigned operation requested list defined in clause 5.11.3a, then the algorithm for assignment of PLMN Assigned UE Radio Capability ID shall assign different UE Radio Capability IDs for UEs with different IMEI/TAC value. The type of UE Radio Capability ID (UE manufacturer-assigned or PLMN-assigned) is distinguished when a UE Radio Capability ID is signalled. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.7 |
6,667 | E.3 Delegated PCF discovery in the Roaming scenario | Figure E.3: Delegated Discovery of PCF in the Home Routed Scenario 1. The AMF sends Nnrf_NFDiscovery Request to the V-NRF in order to discover a PCF in HPLMN. The AMF may indicate the maximum number of H-PCF instances to be returned by the NRF. 2. The NRF in VPLMN and NRF in HPLMN interact using the Nnrf_NFDiscovery service. See step 2 in clause 4.17.5. 3. The AMF gets Nnrf_NFDiscovery service response with one or more profile(s) of PCF(s) in HPLMN. 4. The AMF selects a PCF instance in HPLMN. 5. The AMF builds a Npcf_UEPolicyControl Request that contains the H-PCF ID in the body of the request. If the AMF supports delegated PCF discovery and is configured to apply it, the AMF forwards the Npcf_UEPolicyControl Request to the selected SCP in VPLMN.together with Discovery & Selection parameter set to V-PCF instance ID. 6. The SCP in VPLMN selects the corresponding (V-)PCF instance for UE policy association based on Discovery & Selection parameter received from the AMF. 7. The SCP in VPLMN forwards the Npcf_UEPolicyControl Request to the selected PCF instance in VPLMN. 8. If the V-PCF does not support delegated PCF discovery or is not configured to apply it (Case A), the V-PCF sends Npcf_UEPolicyControl Request to the selected PCF instance. Otherwise (Case B), the V-PCF sends the Npcf_UEPolicyControl Request to a SCP in VPLMN but adds Discovery & Selection parameter set to H-PCF ID. 9. The SCP in VPLMN sends an Npcf_UEPolicyControl Request to the selected PCF instance in HPLMN indicated in step 8. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | E.3 |
6,668 | 6.3.2G UE Minimum output power for V2X Communication | When UE is configured for E-UTRA V2X sidelink transmissions non-concurrent with E-UTRA uplink transmissions for E-UTRA V2X operating bands specified in Table 5.5G-1, the minimum output power shall not exceed the values specified in Table 6.3.2G-1. Table 6.3.2G-1: Minimum output power When UE is configured for simultaneous E-UTRA V2X sidelink and E-UTRA uplink transmissions for inter-band E-UTRA V2X / E-UTRA bands specified in Table 5.5G-2, the requirements specified in subclause 6.3.2 shall apply for the uplink and the requirements specified in subclause 6.3.2G shall apply for the sidelink. For intra-band contiguous E-UTRA V2X multiple carrier transmissions, the requirements specified in subclause 6.3.2G shall apply for each sidelink carrier. For V2X UE supporting Transmit Diversity, if the UE transmits on two antenna connectors at the same time, the minimum output power is defined as the sum of the mean power at each transmit connector in one sub-frame (1ms). The minimum output power shall not exceed the values specified for single carrier. If the UE transmits on aone antenna connector at a time, the requirements specified for single carrier shall apply to the active antenna connector. | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.3.2G |
6,669 | 6.5.1.4A Handling the maximum number of active EPS bearer contexts | If the maximum number of active EPS bearer contexts is reached at the UE (see clause 6.5.0) and the upper layers of the UE request connectivity to a PDN the UE shall not send a PDN CONNECTIVITY REQUEST message unless an active EPS bearer is deactivated. If the UE needs to de-activate an active EPS bearer context, choosing which EPS bearer context to de-activate is implementation specific, however the UE shall not deactivate an EPS bearer context for emergency. NOTE: Clause 6.5.1.6 specifies that a PDN CONNECTIVITY REQUEST message with the same combination of APN and PDN type as an already existing, non-emergency PDN connection can be acceptable, in some cases. In these cases the UE does not need to de-activate an active EPS bearer context if the maximum number of active EPS bearer contexts is reached at the UE. If the UE needs to de-activate an EPS bearer context in order to request an emergency EPS bearer context, it shall either de-activate an EPS bearer context locally or via explicit signalling. If the UE performs local de-activation, the UE shall perform tracking area updating procedure to indicate EPS bearer context status to the network. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.5.1.4A |
6,670 | 5.8.17.3 Conditions for Selection and reselection of NR sidelink U2U Relay UE | A UE capable of NR sidelink U2U Remote UE operation shall initiate NR sidelink U2U Relay (re)slection procedure as specified in 5.8.17.4 when one of the following conditions is met: 1> if configured by upper layers to search for or select a NR sidelink U2U Relay UE; or 1> if the NR sidelink U2U Remote UE threshold conditions for direct PC5 link with the peer NR sidelink U2U Remote UE as specified in 5.8.17.2 are met within sl-RemoteUE-ConfigU2U if configured: 2> if the UE does not have a selected NR sidelink U2U Relay UE; or 2> if the UE has a selected NR sidelink U2U Relay UE, and SL-RSRP of the currently selected NR sidelink U2U Relay UE is available and is below sl-RSRP-ThreshU2U by sl-HystMinU2U within sl-RemoteUE-ConfigU2U if configured; or 2> if the UE has a selected NR sidelink U2U Relay UE, and SD-RSRP of the currently selected NR sidelink U2U Relay UE is available, and is below sd-RSRP-ThreshU2U by sd-HystMinU2U within sl-RemoteUE-ConfigU2U if configured; or NOTE: For relay selection, U2U Remote UE uses SL-RSRP measurements for relay selection trigger evaluation when there is data transmission from peer U2U Remote UE to U2U Remote UE. For relay reselection, U2U Remote UE uses SL-RSRP measurements for relay reselection trigger evaluation when there is data transmission from U2U Relay UE to U2U Remote UE. And in both cases, it is left to UE implementation whether to use SL-RSRP or SD-RSRP for relay (re)selection trigger evaluation in case of no data transmission. 2> if the UE has a selected NR sidelink U2U Relay UE, and upper layers indicate not to use the currently selected NR sidelink U2U Relay UE; or 2> if the UE has a selected NR sidelink U2U Relay UE, and upper layers request the release of the PC5-RRC connection with the current NR sidelink U2U Relay UE; or 2> if the UE has a selected NR sidelink U2U Relay UE, and sidelink radio link failure is detected on the PC5-RRC connection with the current NR sidelink U2U Relay UE as specified in clause 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.17.3 |
6,671 | 5.4.2.3 Reception of the RRCReconfiguration by the UE | The UE shall: 1> apply the default L1 parameter values as specified in corresponding physical layer specifications except for the parameters for which values are provided in SIB1; 1> apply the default MAC Cell Group configuration as specified in 9.2.2; 1> perform RRC reconfiguration procedure as specified in 5.3.5; NOTE: If the UE is connected to 5GC of the source E-UTRA cell, the delta configuration for PDCP and SDAP can be used for intra-system inter-RAT handover. For other cases, source RAT configuration is not considered when the UE applies the reconfiguration message of target RAT. Editor's Note: FFS whether to capture the agreement that all LTE QoE configurations are released at handover to NR in LTE specification or NR specification. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.4.2.3 |
6,672 | 8.11.3 PBCH | The receiver characteristics of the PBCH are determined by the probability of miss-detection of the PBCH for single decoding interval (Pm-bch-s) and the probability of miss-detection of the PBCH for multiple decoding intervals (Pm-bch-m), which are defined as The probability of miss-detection of the PBCH for single decoding interval (Pm-bch-s) is calculated under assumption of single PBCH TTI interval decoding. As is the number of correctly decoded MIB PDUs and Bs is the number of transmitted MIB PDUs (redundancy versions for the same MIB are not counted separately). The probability of miss-detection of the PBCH for multiple decoding intervals (Pm-bch-m) is calculated over multiple PBCH TTI intervals under assumption of independent PBCH decoding over these intervals. Am is the number of PBCH decoding intervals with at least one correctly decoded MIB PDU and Bm is the total number of PBCH decoding intervals. A multiple PBCH decoding interval has 1120 ms duration consisting of continuous PBCH TTIs during the test. | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.11.3 |
6,673 | A.2 Monitoring of E-RAB release | E-RAB is the key and limited resource for E-UTRAN to deliver services. The release of the E-RAB needs to be monitored as: - an abnormal release of the E-RAB will cause the call(/session) drop, which directly impacts the QoS delivered by the networks, and the satisfaction degree of the end user; - a successfully released E-RAB can be used to setup other requested calls(/sessions). The E-RAB failed to be released will still occupy the limited resource and hence it can not be used to admit other requested calls(/sessions). However, the abnormal release of the E-RAB has potential scenario where, regardless of receiving the UE Context Release Command with the cause related to abnormal release, the end user does not perceive it as abnormal. This scenario is explicitly related to VoLTE calls, for other services it is not possible to determine the reason behind the cause code. It is typical to encounter such scenario, a so called "double UE Context", when Radio Link Failure occurs during an ongoing VoLTE call and RRC Connection Re-establishment attempt fails on target or other cell. If then the UE does a new RRC Connection the QCI1 bearer is set-up during Initial Context Setup in the target or other cell. However, when MME receives that service request with the Initial UE message through the target or other cell, it realize that it already has the same UE Context but from the source cell (it has not been released yet). In such case, MME sends UE Context Release Command to the source cell. As the QCI1 E-RAB has been successfully setup in the target or other cell, the QCI1 E-RAB release in the source cell may not be perceived as a drop (abnormal release) by the end user, as the service has been sustained with some interruption time, and cannot be considered as a drop in the QCI1 E-RAB flow Drop Ratio. From a retainability measurement aspect, E-RABs do not need to be released because they are inactive, they can be kept to give fast access when new data arrives. To define (from an E-RAB release measurement point of view) if an E-RAB is considered active or not, the E-RABs can be divided into two groups: a) Continuous flow, E-RABs that are always considered active, i.e. independent of if there is ongoing traffic or not at the moment. Examples: VoIP sessions, Real-time sessions, Live streaming sessions. b) Bursty flow, E-RABs that are only considered active when there is data in UL/DL buffer. Example: Web sessions. How to decide for a particular QCI if the E-RAB is of type bursty flow or continuous flow is outside the scope of this document. The specific reason causing the abnormal and failed release of the E-RAB is required in order to find out the problem and ascertain the solutions. And due to different priority and tolerance for different service type with different OoS level in the networks, the monitor needs to be opened on each service type with OoS level. The E-RAB can be released by E-RAB Release procedure (See 3GPP TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [9]) , UE Context Release procedure (See 3GPP TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [9] and 3GPP TS 36.423[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 Application Protocol (X2AP) ] [10]) procedure, Reset procedure(See 3GPP TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [9]) either initiated by eNodeB or MM, Path Switch procedure (See 3GPP TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [9]) and Intra-eNB HO procedure (See 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8])E. So performance measurements related to E-RAB Release (See 3GPP TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [9]) and UE Context Release (See 3GPP TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [9]) procedure for each service type with QoS level are necessary to support the monitor of E-RAB release. The QCI1 E-RABs normally released on reception of the E-RAB Release Command message from MME with the RLF detected on eNB side in the last predefined time interval are recommended to be monitored via dedicated measurement as may help operator to optimize the network from retainability perspective. It is because in such a case the end user may perceive it as not a drop but as a gap in provided services which may present a room for optimization from QoS perspective. | 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 | A.2 |
6,674 | 6.1.1.3 Granularity of anchor key binding to serving network | The primary authentication and key agreement procedures shall bind the KSEAF to the serving network. The binding to the serving network prevents one serving network from claiming to be a different serving network, and thus provides implicit serving network authentication to the UE. This implicit serving network authentication shall be provided to the UE irrespective of the access network technology, so it applies to both 3GPP and non-3GPP access networks. Furthermore, the anchor key provided to the serving network shall also be specific to the authentication having taken place between the UE and a 5G core network, i.e. the KSEAF shall be cryptographically separate from the key KASME delivered from the home network to the serving network in earlier mobile network generations. The anchor key binding shall be achieved by including a parameter called "serving network name" into the chain of key derivations that leads from the long-term subscriber key to the anchor key. The value of serving network name is defined in sub-clause 6.1.1.4 of the present document. The chain of key derivations that leads from the long-term subscriber key to the anchor key is specified in sub-clause 6.1.3 of the present document for each (class) of authentication methods. The key derivation rules are specified in Annex A. NOTE: No parameter like 'access network type' is used for anchor key binding as 5G core procedures are supposed to be access network agnostic. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.1.1.3 |
6,675 | 8.3.20.4 Protocol configuration options | This IE shall be included in the message when the UE wishes to transmit (protocol) data (e.g. configuration parameters, error codes or messages/events) to the network, and: a) the UE is in WB-S1 mode; b) the requested PDN Type is different from non-IP and Ethernet; and c) the requested APN is not for UAS services. This IE shall be included if: a) the UE supports local IP address in traffic flow aggregate description and TFT filter; b) the UE is in WB-S1 mode; c) the requested PDN Type is different from non-IP and Ethernet; and d) the requested APN is not for UAS services. This IE shall not be included if the Extended 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.20.4 |
6,676 | 19.4.2.9A.7 Replacement field used in DNS-based Discovery of Emergency Numbers | The NAPTR record(s) associated to the Country based Emergency Numbers FQDN shall be provisioned with the replacement field containing the emergency numbers and related emergency service types. The replacement field shall take the following form and include both an emergency number and at least one emergency service type: <emergency-type>.<emergency-number>.sos.en.epc.mcc<MCC>.visited-country.pub.3gppnetwork.org The <emergency-number> and <emergency-type> shall follow the syntax defined in Table 19.4.2.9A.7-1. The <emergency-number> shall consist of a single label. The <emergency-type> shall consist of at least one label. Table 19.4.2.9A.7-1: Syntax of emergency number and emergency type emergency-number = DIGIT*DIGIT ; at least one DIGIT emergency-type = "sos" *("." sub-label) sub-label = let-dig [ *61let-dig-hyp let-dig ] let-dig-hyp = let-dig / "-" let-dig = ALPHA / DIGIT ALPHA = %x41-5A / %x61-7A ; A-Z / a-z As an example, the NAPTR records associated to the Country based Emergency Numbers FQDN for MCC 345 are provisioned in the DNS as: sos.en.epc.mcc345.visited-country.pub.3gppnetwork.org ; IN NAPTR order pref. flag service regexp replacement IN NAPTR 100 999 "" "" sos.ambulance.15.sos.en.epc.mcc345.visited-country.pub.3gppnetwork.org IN NAPTR 100 999 "" "" sos.police.17.sos.en.epc.mcc345.visited-country.pub.3gppnetwork.org IN NAPTR 100 999 "" "" sos.fire.18.sos.en.epc.mcc345.visited-country.pub.3gppnetwork.org IN NAPTR 100 999 "" "" sos.marine.196.sos.en.epc.mcc345.visited-country.pub.3gppnetwork.org | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 19.4.2.9A.7 |
6,677 | 6.5.2 5GSM status received in the UE | If the 5GSM entity of the UE receives a 5GSM STATUS message the UE shall take different actions depending on the received 5GSM cause value: #47 PTI mismatch. The UE shall abort any ongoing 5GSM procedure related to the received PTI value and stop any related timer. #81 invalid PTI value. The UE shall abort any ongoing 5GSM procedure related to the received PTI value and stop any related timer. #97 Message type non-existent or not implemented. The UE shall abort any ongoing 5GSM procedure related to the PTI or PDU session ID and stop any related timer. On receipt of a 5GSM STATUS message with any other 5GSM cause value no state transition and no specific action shall be taken as seen from the radio interface, i.e. local actions are possible. | 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.5.2 |
6,678 | 4.11.5.9 Network Slice Admission Control | Support of NSAC in conjunction with interworking with EPC is described in clause 5.15.11.5 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If EPS counting is required for a network slice, the SMF+PGW-C performs NSACF discovery that supports controlling the maximum number of PDU sessions per network slice as described in clause 6.3.22 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] and in clause 5.2.7.3.2. If non-Hierarchical NSAC or Centralized NSAC architecture is deployed at the network, the following impacts are applicable to clause 4.2.11.4 (Number of PDU Sessions per network slice availability check and update procedure): - The SMF+PGW-C invokes this procedure to perform network slice availability check on the number of PDU Sessions and update for S-NSSAI associated with the PDN connection during PDN connection establishment and PDN connection release. In this case the SMF in figure 4.2.11.4-1 is replaced with SMF+PGW-C. - Step 3: The NSACF determines whether or not to accept the request as described in clause 5.15.11.5 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If Hierarchical NSAC architecture is deployed at the network, the following impacts are applicable to clause 4.2.11.4a: - The SMF+PGW-C invokes this procedure to perform network slice availability check on the number of PDU Sessions and update for S-NSSAI associated with the PDN connection during PDN connection establishment. In this case the SMF in figure 4.2.11.4a-1 is replaced with SMF+PGW-C. - Step 8: The NSACF determines whether or not to accept the request as described in clause 5.15.11.5 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. When the local maximum number is reached, the NSACF may interact with the Primary NSACF before it returns the response back to the SMF+PGW-C as defined in clause 4.2.11.4a. The SMF+PGW-C performs NSACF discovery that supports controlling the maximum number of UEs per network slice as described in clause 6.3.22 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] and in clause 5.2.7.3.2. If non-Hierarchical NSAC or Centralized NSAC architecture is deployed at the network, the following impacts are applicable to clause 4.2.11.2 (Number of UEs per network slice availability check and update procedure): - The SMF+PGW-C invokes this procedure to perform network slice availability check on the number of UEs and update for S-NSSAI associated with the PDN connection during PDN connection establishment. In this case the AMF in figure 4.2.11.2-1 is replaced with SMF+PGW-C. - Step 2: The SMF+PGW-C includes in the message the S-NSSAI, identity of SMF+PGW-C, UE ID and update flag. In a centralized NSAC architecture, the SMF+PGW-C additionally includes the NSAC service area if available. - Step 3: The AMF ID is replaced by the SMF + PGW-C ID. - Step 3: The NSACF determines whether or not to accept the request as described in clause 5.15.11.5 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. If Hierarchical NSAC architecture is deployed at the network, the following impacts are applicable to clause 4.2.11.2a: - The SMF+PGW-C invokes perform network slice availability check on the number of UEs and update for S-NSSAI associated with the PDN connection during PDN connection establishment. In this case the AMF in figure 4.2.11.2a-1 is replaced with SMF+PGW-C. - Step 2: The SMF+PGW-C includes in the message the S-NSSAI, identity of SMF+PGW-C, UE ID and update flag. - Step 3: The AMF ID is replaced by the SMF + PGW-C ID. - Step 8: The NSACF determines whether or not to accept the request as described in clause 5.15.11.5 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. When the local maximum number is reached the NSACF may interact with the Primary NSACF before it returns the response back to the SMF+PGW-C as defined in clause 4.2.11.2a. The SMF+PGW-C shall continue the PDN Connection Establishment procedure only when the Network Slice subject to NSAC is available based on both numbers of PDU Sessions and number of UEs. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.11.5.9 |
6,679 | 5.4.7.2.4 Abnormal cases in the UE | The following abnormal cases can be identified: a) Transmission failure of the NETWORK SLICE-SPECIFIC AUTHENTICATION COMPLETE message with change in the current TAI If the current TAI is not in the TAI list, the network slice-specific authentication and authorization procedure shall be aborted and: - if the UE is in 5GMM-REGISTERED state, a registration procedure for mobility and periodic registration update indicating "mobility registration updating" in the 5GS registration type IE of the REGISTRATION REQUEST message shall be initiated; and - otherwise a registration procedure for initial registration shall be initiated. b) Transmission failure of NETWORK SLICE-SPECIFIC AUTHENTICATION COMPLETE message indication without change in the current TAI It is up to the UE implementation how to re-run the ongoing procedure that triggered the network slice-specific authentication and authorization procedure. c) Network slice-specific authentication and authorization procedure and de-registration procedure collision If the UE receives NETWORK SLICE-SPECIFIC AUTHENTICATION COMMAND message after sending a DEREGISTRATION REQUEST message and the access type included in the DEREGISTRATION REQUEST message is the same as the access in which the NETWORK SLICE-SPECIFIC AUTHENTICATION COMMAND message is received, then the UE shall ignore the NETWORK SLICE-SPECIFIC AUTHENTICATION COMMAND message and proceed with the de-registration procedure. Otherwise, the UE shall proceed with both procedures. d) Network slice-specific authentication and authorization procedure and service request procedure collision If the SERVICE REQUEST message includes the UE request type IE with the Request type value set to "NAS signalling connection release" and the UE receives a NETWORK SLICE-SPECIFIC AUTHENTICATION COMMAND message before the ongoing service request procedure has been completed, the UE shall ignore the NETWORK SLICE-SPECIFIC AUTHENTICATION COMMAND message and proceed with the service request procedure. If the the SERVICE REQUEST message does not include the UE request type IE with the Request type value set to "NAS signalling connection release" and the UE receives a NETWORK SLICE-SPECIFIC AUTHENTICATION COMMAND message before the ongoing service request procedure has been completed, the UE shall proceed with both procedures. e) Network slice-specific authentication and authorization procedure and registration procedure for mobility and periodic registration update collision If the REGISTRATION REQUEST message includes the Unavailability information IE and the UE receives a NETWORK SLICE-SPECIFIC AUTHENTICATION COMMAND message before the ongoing registration procedure for mobility and periodic registration update has been completed, the UE shall ignore the NETWORK SLICE-SPECIFIC AUTHENTICATION COMMAND message and proceed with the registration procedure for mobility and periodic registration update procedure. If the the REGISTRATION REQUEST message does not include the Unavailability information IE and the UE receives a NETWORK SLICE-SPECIFIC AUTHENTICATION COMMAND message before the ongoing registration procedure for mobility and periodic registration update has been completed, the UE shall proceed with both procedures. | 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.2.4 |
6,680 | 6.7.1.2 AMF change | If the change of the AMF at N2-Handover or mobility registration update results in the change of algorithm to be used for establishing NAS security, the target AMF shall indicate the selected algorithm to the UE as defined in Clause 6.9.2.3.3 for N2-Handover (i.e., using NAS Container) and Clause 6.9.3 for mobility registration update (i.e., using NAS SMC). The AMF shall select the NAS algorithm which has the highest priority according to the ordered lists (see sub-clause 6.7.1.1 of the present document). | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.7.1.2 |
6,681 | 5.17.2.5 Secondary DN authentication and authorization in EPS Interworking case | Secondary authentication/authorization by a DN-AAA server during the establishment of a PDN connection over 3GPP access to EPC, is supported based on following principles: - It is optional for the UE to support EAP-based secondary authentication and authorization by DN-AAA over EPC, - A SMF+PGW-C shall be used to serve DNN(s) requiring secondary authentication/authorization by a DN-AAA server, - For secondary authentication/authorization by a DN-AAA server, the SMF+PGW-C runs the same procedures with PCF, UDM and DN-AAA and uses the same corresponding interfaces regardless of whether the UE is served by EPS or 5GS, - The interface towards the UE is different (usage of NAS for EPS instead of NAS for 5GS) between the EPS and 5GS cases. This is further specified in Annex H of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. In this Release, EAP based Secondary authentication by a DN-AAA server during the establishment of a PDN connection over non-3GPP access to EPC is not supported. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.17.2.5 |
6,682 | 4.4 Regional Subscription Zone Identity (RSZI) | A PLMN-specific regional subscription defines unambiguously for the entire PLMN the regions in which roaming is allowed. It consists of one or more regional subscription zones. The regional subscription zone is identified by a Regional Subscription Zone Identity (RSZI). A regional subscription zone identity is composed as shown in figure 7. Figure 7: Structure of Regional Subscription Zone Identity (RSZI) The elements of the regional subscription zone identity are: 1) the Country Code (CC) which identifies the country in which the PLMN is located; 2) the National Destination Code (NDC) which identifies the PLMN in that country; 3) the Zone Code (ZC) which identifies a regional subscription zone as a pattern of allowed and not allowed location areas uniquely within that PLMN. CC and NDC are those of an ITU-T E.164 VLR or SGSN number (see clause 5.1) of the PLMN; they are coded with a trailing filler, if required. ZC has fixed length of two octets and is coded in full hexadecimal representation. RSZIs, including the zone codes, are assigned by the VPLMN operator. The zone code is evaluated in the VLR or SGSN by information stored in the VLR or SGSN as a result of administrative action. If a zone code is received by a VLR or SGSN during updating by the HLR and this zone code is related to that VLR or SGSN, the VLR or SGSN shall be able to decide for all its MSC or SGSN areas and all its location areas whether they are allowed or not allowed. For details of assignment of RSZI and of ZC as subscriber data see 3GPP TS 23.008[ Organization of subscriber data ] [2]. For selection of RSZI at location updating by comparison with the leading digits of the VLR or SGSN number and for transfer of ZC from the HLR to VLR and SGSN see 3GPP TS 29.002[ Mobile Application Part (MAP) specification ] [31]. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.4 |
6,683 | 14.9 Sustained downlink data rate with active sidelink | The purpose of this test is to verify the WAN and V2X operation is not impacted with each other when UE is under concurrent operation. This test case applies to UEs support concurrent operation of V2X communication with E-UTRA uplink/downlink on the operating bands combinations listed in Table 5.5G-2. The test parameters are in Table 14.9-1, and the test UE is expected to receive all PSSCH and PDSCH transmissions simultaneously. For PDSCH, the test cases apply to UE categories and bandwidth as specified in Table 14.9-2. The minimum requirements for PSSCH are specified in Table 14.7-2, Table 14.10-3 and Table 14.10-4 with corresponding test applicability and the minimum requirements for PDSCH downlink data rate are specified in Table 14.9-3. Both PDSCH and PSSCH performance will be verified simultaneously. The TB success rate in the cellular link shall be sustained during at least 300 frames. Table 14.9-1: Test parameters for sustained downlink data rate (FDD 64QAM) and maximum PSSCH processing capability Table 14.9-2: Test cases for sustained data rate Table 14.9-3: Minimum requirements (FDD 64QAM) 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 | 14.9 |
6,684 | 4.16.2.1.1 AM Policy Association Modification initiated by the AMF without AMF relocation | This procedure is applicable to Case A. Figure 4.16.2.1.1-1: AM Policy Association Modification initiated by the AMF This procedure concerns both roaming and non-roaming scenarios. In the non-roaming case the role of the V-PCF is performed by the PCF. For the roaming scenarios, the V-PCF interacts with the AMF. 1. When a Policy Control Request Trigger condition is met the AMF updates the AM Policy Association and provides information on the conditions that have changed to the PCF by invoking Npcf_AMPolicyControl_Update. 2. The (V-)PCF stores the information received in step 1 and makes the policy decision. In the non-roaming case, the PCF may subscribe to Analytics from NWDAF as defined in clause 6.1.1.3 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. If the PCF determines a change to policy counter status reporting is required, it may alter the subscribed list of policy counters using the Initial, Intermediate or Final Spending Limit Report Retrieval procedures as defined in clause 4.16.8. 3. The (V-)PCF responds to the AMF with the updated access and mobility related policy information as defined in clause 6.5 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20] and the updated Policy Control Request Trigger parameters. If an AF has previously subscribed to request for allocation of service area coverage outcome event, the (V-)PCF checks if reporting is needed, using the Policy Control Request Trigger that was met (see step 1) as input, then sends a respective notification to the AF using Npcf_AMPolicyAuthorization_Notify, 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]. 4. The AMF deploys the access and mobility related policy information, which includes storing the Service Area Restrictions and Policy Control Request Trigger of AM Policy Association, provisioning the Service Area Restrictions to the UE and provisioning the RFSP index, UE-AMBR, List of UE-Slice-MBR, Service Area Restrictions to the NG-RAN as defined in TS 23.501[ System architecture for the 5G System (5GS) ] [2] and request for notification of SM Policy association establishment and termination to a list of (DNN, S-NSSAI)(s) together with PCF for the UE binding information. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.16.2.1.1 |
6,685 | 4.2.9.3 AAA Server triggered Network Slice-Specific Re-authentication and Re-authorization procedure | Figure 4.2.9.3-1: AAA Server initiated Network Slice-Specific Re-authentication and Re-authorization procedure 1. The AAA-S requests the re-authentication and re-authorization for the Network Slice specified by the S-NSSAI in the AAA protocol Re-Auth Request message, for the UE identified by the GPSI in this message. This message is sent to a AAA-P, if the AAA-P is used (e.g. the AAA Server belongs to a third party), otherwise it is sent directly to the NSSAAF. 2. The AAA-P, if present, relays the request to the NSSAAF. 3a-3b. NSSAAF gets AMF ID from UDM using Nudm_UECM_Get with the GPSI in the received AAA message. If NSSAAF receives two different AMF address then the NSSAAF either decide to notify both AMFs or the NSSAF may decide to notify one AMF first and if NSSAA fails also notify the other AMF. 3c. The NSSAAF provides an acknowledgement to the AAA protocol Re-Auth Request message. If the AMF is not registered in UDM the procedure is stopped here. 4. If the AMF is registered in UDM, the NSSAAF notifies the AMF to re-authenticate/re-authorize the S-NSSAI for the UE using Nnssaaf_NSSAA_Re-AuthNotification with the GPSI and S-NSSAI in the received AAA message. The callback URI of the notification for the AMF is derived via NRF as specified in TS 29.501[ 5G System; Principles and Guidelines for Services Definition; Stage 3 ] [62]. 5. If the UE is registered with the S-NSSAI in the Mapping Of Allowed NSSAI, the AMF triggers the Network Slice-Specific Authentication and Authorization procedure defined in clause 4.2.9.1. If the S-NSSAI is included in the Allowed NSSAI for 3GPP access and non-3GPP access, AMF selects an access type to perform NSSAA based on network policies. If the S-NSSAI is only included in the Allowed NSSAI of non-3GPP access and UE is CM-IDLE in non-3GPP access, the AMF marks the S-NSSAI as pending. In this case, when UE becomes CM-CONNECTED in non-3GPP access, the AMF initiates NSSAA if needed. If the UE is registered but the S-NSSAI is not in the Mapping Of Allowed NSSAI, the AMF removes any status of the corresponding S-NSSAI subject to Network Slice-Specific Authentication and Authorization in the UE context it may have kept, so that an NSSAA is executed next time the UE requests to register with the S-NSSAI. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.2.9.3 |
6,686 | A.3 Example of PLMN Colour Codes (NCCs) for the European region | Austria : 0 Belgium : 1 Cyprus : 3 Denmark : 1 Finland : 0 France : 0 Germany : 3 Greece : 0 Iceland : 0 Ireland : 3 Italy : 2 Liechtenstein : 2 Luxembourg : 2 Malta : 1 Monaco : 3 (possibly 0(=France)) Netherlands : 0 Norway : 3 Portugal : 3 San Marino : 0 (possibly 2(= Italy)) Spain : 1 Sweden : 2 Switzerland : 1 Turkey : 2 UK : 2 Vatican : 1 (possibly 2(=Italy) Yugoslavia : 3 This allows a second operator for each country by allocating the colour codes n (in the table) and n + 4. More than 2 colour codes per country may be used provided that in border areas only the values n and/or n+4 are used. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | A.3 |
6,687 | 10.5.4.21a Recall type $(CCBS)$ | The purpose of the recall type information element is to describe the reason for the recall. The recall type information element is coded as shown in Figure 10.5.108/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and Table 10.5.128/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . The recall type is a type 3 information element with 2 octets length. Figure 10.5.108/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Recall type information element Table 10.5.128/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Recall type information element | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 10.5.4.21a |
6,688 | A.1 KDF interface and input parameter construction A.1.1 General | All key derivations (including input parameter encoding) for 5GC shall be performed using the key derivation function (KDF) specified in Annex B.2.0 of TS 33.220[ Generic Authentication Architecture (GAA); Generic Bootstrapping Architecture (GBA) ] [28]. This clause specifies how to construct the input string, S, and the input key, KEY, for each distinct use of the KDF. Note that "KEY" is denoted "Key" in TS 33.220[ Generic Authentication Architecture (GAA); Generic Bootstrapping Architecture (GBA) ] [28]. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | A.1 |
6,689 | 5.35A Support for Mobile Base Station Relay (MBSR) 5.35A.1 General | The MBSR uses the IAB architecture as defined in clause 5.35, and operates as an IAB node (with an IAB-UE and gNB-DU) with mobility when integrated with the serving PLMN. The architecture described in clause 5.35 applies unless specific handling is specified in clause 5.35A. Additionally, the following limitations apply to the MBSR: - the MBSR has a single hop to the IAB-donor node; - NR Uu is used for the radio link between a MBSR and served UEs, and between MBSR and IAB-donor node. Regulatory requirements (e.g. emergency services, priority services) are supported when UEs access 5GS via a MBSR. LCS framework as defined in TS 23.273[ 5G System (5GS) Location Services (LCS); Stage 2 ] [87] is used for providing the location service to the served UEs, with additional enhancements described in clause 5.35A.5. Roaming of the MBSR is supported, i.e. a MBSR can integrated with a VPLMN's IAB-donor node. The corresponding enhancements to support MBSR roaming are described in clause 5.35A.4. CAG mechanism as defined in clause 5.30 can be used for the control of UE's access to the MBSR. Optional enhancements to the CAG mechanism for MBSR use are described in clause 5.35A.6. For a MBSR node to operate as a MBSR, it provides a mobile IAB-indication to the IAB-donor-CU when the RRC connection is established as defined in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [28]. When the mobile IAB-indication is received, the IAB-donor-CU selects an AMF that supports mobile IAB-node and includes the mobile IAB-indication in the N2 INITIAL UE MESSAGE as defined in TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [34] so that the AMF can perform MBSR authorization as described in clause 5.35A.4. If the MBSR node is not authorized, e.g. due to the MBSR authorization indication from AMF, it also provides the mobile IAB-indication when establishing new RRC connection so that the AMF supporting mobile IAB-node will be selected by the IAB-donor-CU, to ensure that the operation related to MBSR authorization status change for a registered MBSR node can be performed as described in clause 5.35A.4. If the MBSR receives MBSR authorized indication from AMF, it provides the information about the authorization result to its IAB-DU component based on non-standardized interface as described in clause 5.35A.4. After the IAB-UE performs registration procedure in 5GS, further mobility procedure can be performed to change the IAB-donor-DU, the IAB-donor-CU as specified in TS 38.401[ NG-RAN; Architecture description ] [42]. The mobility support of UEs served by the MBSR is specified in clause 5.35A.3 | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.35A |
6,690 | – NTN-Config | The IE NTN-Config provides parameters needed for the UE to access NR via NTN access. NTN-Config information element -- ASN1START -- TAG-NTN-CONFIG-START NTN-Config-r17 ::= SEQUENCE { epochTime-r17 EpochTime-r17 OPTIONAL, -- Need R ntn-UlSyncValidityDuration-r17 ENUMERATED{ s5, s10, s15, s20, s25, s30, s35, s40, s45, s50, s55, s60, s120, s180, s240, s900} OPTIONAL, -- Cond SIB19 cellSpecificKoffset-r17 INTEGER(1..1023) OPTIONAL, -- Need R kmac-r17 INTEGER(1..512) OPTIONAL, -- Need R ta-Info-r17 TA-Info-r17 OPTIONAL, -- Need R ntn-PolarizationDL-r17 ENUMERATED {rhcp,lhcp,linear} OPTIONAL, -- Need R ntn-PolarizationUL-r17 ENUMERATED {rhcp,lhcp,linear} OPTIONAL, -- Need R ephemerisInfo-r17 EphemerisInfo-r17 OPTIONAL, -- Need R ta-Report-r17 ENUMERATED {enabled} OPTIONAL, -- Need R ... } EpochTime-r17 ::= SEQUENCE { sfn-r17 INTEGER(0..1023), subFrameNR-r17 INTEGER(0..9) } TA-Info-r17 ::= SEQUENCE { ta-Common-r17 INTEGER(0..66485757), ta-CommonDrift-r17 INTEGER(-257303..257303) OPTIONAL, -- Need R ta-CommonDriftVariant-r17 INTEGER(0..28949) OPTIONAL -- Need R } -- TAG-NTN-CONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
6,691 | 5.15.11.4 Network Slice status notifications and reports to a consumer NF | A consumer NF (e.g. AF, Primary NSACF) can subscribe with the NSACF for Network Slice status notifications and reports. Upon such subscription, the corresponding NSACF in different NSAC architecture as defined in clause 5.15.11.0 can provide event based notifications and reports to the consumer NF (e.g. to AF via NEF) related to the current number of UEs registered for a network slice or the current number of UEs with at least one PDU Session/PDN Connection in the case of EPC interworking or the current number of PDU Sessions established on a network slice. NOTE: The Primary NSACF subscribes Network Slice status from all the NSACF(s) it contacts with for the update of the maximum number of UE or PDU session configured at the NSACF. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.15.11.4 |
6,692 | 5.3.8.3 MME-initiated Detach procedure | The MME-Initiated Detach procedure when initiated by the MME is illustrated in Figure 5.3.8.3-1. This procedure may be also used as part of the SIPTO function when the MME determines that GW relocation is desirable for all PDN connection(s) serving SIPTO-allowed APNs. The MME initiates the "explicit detach with reattach required" procedure and the UE should then re-establish those PDN connections for the same APN(s). Figure 5.3.8.3-1: MME-Initiated Detach Procedure NOTE 1: For a PMIP-based S5/S8, procedure steps (A) are defined in TS 23.402[ Architecture enhancements for non-3GPP accesses ] [2]. Steps 3, 4 and 5 concern GTP based S5/S8. NOTE 2: Procedure steps (B) are used by the procedure steps (E) in clause 5.3.2.1. 1. The MME initiated detach procedure is either explicit (e.g. by O&M intervention) or implicit. The MME may implicitly detach a UE, if it has not had communication with UE for a long period of time. The MME does not send the Detach Request (Detach Type) message to the UE for implicit detach. The implicit detach is local to the MME, i.e. an SGSN registration will not be detached. If the UE is in ECM-CONNNECTED state the MME may explicitly detach the UE by sending a Detach Request message to the UE. The Detach Type may be set to re-attach in which case the UE should re-attach at the end of the detach process. If the UE is in ECM-IDLE state the MME pages the UE. For emergency attached UEs, MME initiated implicit detach procedures are based on an inactivity timeout specific to emergency. If this Detach procedure is due to the UE's Detach Request via a CSG cell which the UE is not allowed to access, i.e. the CSG subscription for this CSG ID and associated PLMN is absent or expired, the MME shall send a Detach Request to UE with an appropriate cause indicating the UE is not allowed to access this CSG. In the case of satellite access for Cellular IoT, the MME initiates detach procedure if it detects that the UE's registered PLMN is not allowed to operate in the present UE location (see clause 4.13.4). In this case, the MME shall include in the Detach Request message a suitable cause value. 2. If the UE has no activated PDN connection, then steps 2 to 10 are not executed. If the PLMN has configured secondary RAT usage reporting, the MME shall wait for step 11, if applicable, and perform step 12 before step 2 onwards. For any PDN connections to the SCEF, the MME indicates to the SCEF that the PDN connection for the UE is no longer available according to TS 23.682[ Architecture enhancements to facilitate communications with packet data networks and applications ] [74] and steps 2 to 10 are not executed. For PDN connections to the P-GW, any EPS Bearer Context information in the Serving GW regarding this particular UE and related to the MME are deactivated by the MME sending Delete Session Request (LBI, User Location Information (ECGI), NAS Release Cause if available, Secondary RAT usage data, PSCell ID) message per PDN connection to the Serving GW. If the UE Time Zone has changed, the MME includes the UE Time Zone IE in this message. NAS Release Cause is only sent by the MME to the PDN GW if this is permitted according to MME operator's policy. If Secondary RAT usage data report was received from the RAN, the MME includes this in the Delete Session Request message. If MME has received PSCell ID from eNodeB, the MME includes it in Delete Session Request. 3. When the S-GW receives the first Delete Session Request message from the MME or SGSN in ISR activated state, the Serving GW deactivates ISR, releases the related EPS Bearer context information and responds with Delete Session Response (Cause). When the S-GW receives the Delete Session Request message from the MME or SGSN in ISR deactivated state, the Serving GW releases the related EPS Bearer context information and jumps to step 6 by sending a Delete Session Request (LBI) message to the PDN GW. After step 7 the Serving GW responds back to the MME/SGSN with the Delete Session Response (Cause and, optionally, APN Rate Control Status according to clause 4.7.7.3) message. 4. If ISR is activated, MME sends Detach Notification (Cause) message to the associated SGSN. The cause indicates whether it is a local or complete detach. 5. If cause indicates complete detach then the SGSN sends a Delete Session Request (LBI, CGI/SAI) message per PDN connection to the Serving GW. If Cause indicates local detach then SGSN deactivates ISR and steps 5 to 9 shall be skipped. If the UE Time Zone has changed, the SGSN includes the UE Time Zone IE in this message. 6. If ISR is activated, Serving GW deactivates ISR. If ISR is not activated and the Serving GW received one or several Delete Bearer Request message(s) from SGSN in step 2, the Serving GW sends a Delete Session Request (LBI, User Location Information (ECGI or CGI/SAI), NAS Release Cause if available, Secondary RAT usage data) message for each associated PDN connection to the PDN GW. NAS Release Cause is the one received in the Delete Session Request from the MME. This message indicates that all bearers belonging to that PDN connection shall be released. If the MME and/or SGSN send(s) UE's Location Information, and/or UE Time Zone and/or Secondary RAT usage data in step 2 and/or step 5, the S-GW includes the User Location Information, and/or UE Time Zone Information with the least age in this message and/or Secondary RAT usage data. 7. The PDN GW acknowledges with Delete Session Response (Cause and, optionally, APN Rate Control Status according to clause 4.7.7.3) message. 8. The PDN GW employs an IP-CAN Session Termination procedure as defined in TS 23.203[ Policy and charging control architecture ] [6] with the PCRF to indicate to the PCRF that the EPS Bearer(s) are released if a PCRF is configured. If requested by the PCRF the PDN GW indicates User Location Information and/or UE Time Zone Information and NAS Release Cause (if available) to the PCRF as defined in TS 23.203[ Policy and charging control architecture ] [6]. 9. The Serving GW acknowledges with Delete Session Response (Cause, APN Rate Control Status) message. 10. The SGSN sends Detach Acknowledge message to the MME (APN Rate Control Status). The MME stores the APN Rate Control Status in the MM context. 11. If the UE receives the Detach Request message from the MME in the step 1, the UE sends a Detach Accept message to the MME any time after step 1. The eNodeB forwards this NAS message to the MME along with the TAI+ECGI of the cell which the UE is using. If Dual Connectivity is active for the UE, the PSCell ID shall be included in the Uplink NAS Transport that carries the Detach Accept message. If the UE receives Detach Request from the MME via a CSG cell with the cause indicating the UE is not allowed to access this CSG, the UE shall remove this CSG ID and associated PLMN from its Allowed CSG list, if present. 12. After receiving the Detach Accept message, Delete Session Response and, if appropriate, Detach Acknowledge message, the MME releases the S1-MME signalling connection for the UE by sending an S1 Release Command (Cause) message to the eNodeB. The details of this step are covered in the "S1 Release Procedure", as described in clause 5.3.5 by step 4 to step 6. If the Detach Type requests the UE to make a new attach, the UE reattaches after the RRC Connection Release is completed. NOTE 3: In the "S1 Release Procedure", if Dual Connectivity was active at the time of the release, the eNodeB includes the PSCell ID. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.3.8.3 |
6,693 | 5.35.6 IAB operation involving EPC | When the IAB-donor gNB has connection to both EPC and 5GC, based on PLMN configuration, there are two possible operation modes: - the IAB-node connects to a 5GC via the IAB-donor gNB, while the UEs served by the IAB-node connect to EPC with Dual Connectivity as defined in TS 37.340[ Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Overall Description; Stage-2 ] [31]. In this operation mode, the IAB-donor gNB has connection to an eNB, and the 5GC is restricted for IAB-node access only; and - the IAB-node connects to an EPC via the IAB-donor gNB with Dual Connectivity as defined in TS 37.340[ Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Overall Description; Stage-2 ] [31], while the UEs served by the IAB-node connect to the 5GC. In this operation mode, the EPC is restricted for IAB-node access only. To support the above operation modes, the IAB-UE shall be configured to select only a specific PLMN (as defined in TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [17]) and whether it needs to connect to 5GC or EPC. NOTE: For a particular PLMN, it is expected that only one of the modes would be deployed in a known region. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.35.6 |
6,694 | 5.6.16 Support for Service Function Chaining 5.6.16.1 General | Service Function Chaining, also called N6-LAN Traffic Steering, refers to the steering of subscriber's traffic flows to appropriate operator or 3rd party Service Functions (e.g. NAT, antimalware, parental control, DDoS protection) in the N6-LAN. The content of this clause applies to non-roaming and to Home Routed roaming scenario, i.e. to cases where the involved entities (AF, PCF, SMF, UPF) belong to the Home PLMN and the AF has an agreement with the Home PLMN. The PCF controls Service Function Chaining by provisioning and modifying traffic steering control information for N6-LAN Traffic Steering as described in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45], e.g. clause 6.1.3.14. The traffic steering control information for N6-LAN Traffic Steering consists of a traffic description and a reference to a traffic steering policy that is configured in the SMF/UPF. The PCF derives the TSP ID(s) (that can be different for uplink and downlink directions) based on operator configuration and sends the TSP ID(s) to the SMF as part of the N6-LAN Traffic Steering Enforcement Control information in the PCC rule as described in clause 6.3.1 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]. When the PCC rule is activated or updated with N6-LAN Traffic Steering Enforcement Control information, the SMF sets the Forwarding Policy (uplink and/or downlink) within the FAR(s) based on the authorized TSP ID(s) in the PCC rule and under consideration of the direction. In case that Application Function influence on traffic routing Enforcement Control information and N6-LAN Traffic Steering Enforcement Control information are both provided for the uplink direction, the SMF shall derive N4 rules which instruct the UPF to pass the traffic through the relevant Service Function(s) deployed in the N6-LAN before steering the traffic to the local data network. The SMF provides instructions to UPF for N6-LAN traffic steering as further detailed in clause 5.8.5.6. The UPF applies traffic steering mechanism based on Forwarding Policy, i.e. the UPF performs deployment specific actions as configured for the Forwarding Policy. NOTE 1: It is assumed that all UPFs in the operator network serving as PSA for the DNN/S-NSSAI/DNAI subject to N6-LAN traffic steering need to be configured with the same traffic steering information for N6-LAN traffic steering. When performing deployment specific actions configured for the Forwarding Policy, the UPF may support traffic steering related functionality and user plane encapsulation protocols that are out of 3GPP scope (e.g. as defined by other standards organizations). NOTE 2: The existing user plane mechanisms (e.g. VXLAN, NSH, GENEVE, GRE, VLAN, etc.) defined at IETF are reused as applicable by the PSA UPF to support N6-LAN traffic steering. The mechanism used for forwarding the traffic between the Service Functions within the N6-LAN is out of 3GPP scope. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.6.16 |
6,695 | 5.4.1.3.2 Authentication initiation by the network | The network may initiate a 5G AKA based primary authentication and key agreement procedure for a UE in 5GMM-CONNECTED mode at any time. For restrictions applicable after handover or inter-system change to N1 mode in 5GMM-CONNECTED mode, see subclause 5.5.1.3.3. The network initiates the 5G AKA based primary authentication and key agreement procedure by sending an AUTHENTICATION REQUEST message to the UE and starting the timer T3560 (see example in figure 5.4.1.3.2.1). The AUTHENTICATION REQUEST message shall contain the parameters necessary to calculate the authentication response (see 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]). This message shall include the ngKSI that will be used by the UE and AMF to identify the KAMF and the partial native security context that is created if the authentication is successful. This message shall also include the ABBA parameter. In this release of specification, the network shall set the length of ABBA IE to 2 and the ABBA contents to be 2 octets in length with value 0000H as described in subclause 9.11.3.10. If an ngKSI is contained in an initial NAS message during a 5GMM procedure, the network shall include a different ngKSI value in the AUTHENTICATION REQUEST message when it initiates a 5G AKA based primary authentication and key agreement procedure. Figure 5.4.1.3.2.1: 5G AKA based primary authentication and key agreement procedure | 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.3.2 |
6,696 | 5.5.1.2 Attach procedure for EPS services 5.5.1.2.1 General | This procedure can be used by a UE to attach for: - EPS services only; or - EPS services and "SMS only" if the UE supports NB-S1 mode only. When the UE initiates the attach procedure for normal service, the UE shall indicate "EPS attach" in the EPS attach type IE. When the UE initiates the attach procedure for emergency bearer services, the UE shall indicate "EPS emergency attach" in the EPS attach type IE. The attach procedure for emergency bearer services is not applicable for NB-S1 mode (see 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [10]). This procedure can also be used by a UE in limited service state to attach for access to RLOS. When the UE initiates the attach procedure for access to RLOS, the UE shall indicate "EPS RLOS attach" in the EPS attach type IE. The attach procedure for access to RLOS is not applicable for NB-S1 mode (see 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [10]). | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.5.1.2 |
6,697 | 21.2.1 QoE Measurement Collection Activation and Reporting | The feature is activated in the gNB either by direct configuration from the OAM system (management-based activation), or by signalling from the OAM via the 5GC (signalling-based activation), containing UE-associated QoE configuration. One or more QoE measurement collection jobs can be activated at a UE per service type, and each QoE measurement configuration is uniquely identified by a QoE reference. For signalling-based QoE measurements, the OAM initiates the QoE measurement activation for a specific UE via the 5GC, and the gNB receives one or more QoE measurement configurations by means of UE-associated signalling. The QoE measurement configuration for signalling-based activation includes an application layer measurement configuration list and the corresponding information for QoE measurement collection, e.g., QoE reference, service type, MCE IP address, slice scope, area scope, MDT alignment information, the indication of available RAN visible QoE metrics and assistance information. For management-based QoE measurement activation, the OAM sends one or more QoE measurement configurations directly to the gNB. The QoE measurement configuration for management-based activation also includes an application layer measurement configuration list and the corresponding information for QoE measurement collection. The gNB selects UE(s) that meet the required QoE measurement capability, area scope and slice scope. Application layer measurement configuration received by the gNB from OAM or 5GC is encapsulated in a transparent container, which is forwarded to a UE as Application layer configuration in the RRCReconfiguration message (there can be multiple configurations in the same message). Application layer measurement reports received from UE's application layer are encapsulated in a transparent container and sent to the network in the MeasurementReportAppLayer message, as specified in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [12]. The UE can send multiple application layer measurement reports to the gNB in one MeasurementReportAppLayer message. In order to allow the transmission of application layer measurement reports which exceed the maximum PDCP SDU size, segmentation of the MeasurementReportAppLayer message may be enabled by the gNB. A measurement configuration application layer ID conveyed in the RRC signalling is used to identify the application layer measurement configuration and report between the gNB and the UE. The measurement configuration application layer ID is mapped to the QoE reference in the gNB, and the gNB forwards the application layer measurement report to MCE together with the QoE reference. The gNB can release one or multiple application layer measurement configurations from the UE in one RRCReconfiguration message at any time. The UE may additionally be configured by the gNB to report when a QoE measurement session starts or stops for a certain application layer measurement configuration. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 21.2.1 |
6,698 | 4.4.3 Handling of NAS COUNT and NAS sequence number 4.4.3.1 General | Each EPS security context shall be associated with two separate counters NAS COUNT: one related to uplink NAS messages and one related to downlink NAS messages. The NAS COUNT counters use 24 bit internal representation and are independently maintained by UE and MME. The NAS COUNT shall be constructed as a NAS sequence number (8 least significant bits) concatenated with a NAS overflow counter (16 most significant bits). When NAS COUNT is input to NAS ciphering or NAS integrity algorithms it shall be considered to be a 32-bit entity which shall be constructed by padding the 24-bit internal representation with 8 zeros in the most significant bits. The value of the uplink NAS COUNT that is stored or read out of the USIM or non-volatile memory as described in annex C, is the value that shall be used in the next NAS message. The value of the downlink NAS COUNT that is stored or read out of the USIM or non-volatile memory as described in annex C, is the largest downlink NAS COUNT used in a successfully integrity checked NAS message. The value of the uplink NAS COUNT stored in the MME is the largest uplink NAS COUNT used in a successfully integrity checked NAS message. The value of the downlink NAS COUNT stored in the MME is the value that shall be used in the next NAS message. The NAS sequence number part of the NAS COUNT shall be exchanged between the UE and the MME as part of the NAS signalling. After each new or retransmitted outbound security protected NAS message, the sender shall increase the NAS COUNT number by one, except for the initial NAS messages if the lower layers indicated the failure to establish the RRC connection (see 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [22]). Specifically, on the sender side, the NAS sequence number shall be increased by one, and if the result is zero (due to wrap around), the NAS overflow counter shall also be incremented by one (see clause 4.4.3.5). The receiving side shall estimate the NAS COUNT used by the sending side. Specifically, if the estimated NAS sequence number wraps around, the NAS overflow counter shall be incremented by one. NOTE 0: When estimating a NAS COUNT, the receiver is required to ensure that a given NAS COUNT value is accepted at most one time, as specified in clause 4.4.3.2. After the derivation of a NAS token due to an inter-system change from S1mode to A/Gb mode or Iu mode in idle mode as specified in 3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13], the UE shall increase the uplink NAS COUNT by one. When the MME receives a NAS token via SGSN during an idle mode inter-system change from S1 mode to A/Gb mode or Iu mode, the MME shall check the NAS token as specified in 3GPP TS 33.401[ 3GPP System Architecture Evolution (SAE); Security architecture ] [19], clause 9.1.1, and update its uplink NAS COUNT with the uplink NAS COUNT value used for the successful check of the NAS token. NOTE 1: The MME does not check the NAS token if it is received via SGSN during a connected mode inter-system change from S1 mode to A/Gb mode or Iu mode. During the handover from UTRAN/GERAN to E-UTRAN, when a mapped EPS security context is derived and taken into use, the MME shall set both the uplink and downlink NAS COUNT counters of this EPS security context to zero. The UE shall set both the uplink and downlink NAS COUNT counters to zero. When a mapped EPS security context is derived as specified in 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [56] and taken into use in the following cases: - during the inter-system change from N1 mode to S1 mode in 5GMM-CONNECTED mode; or - during the inter-system change from N1 mode to S1 mode in EMM-IDLE mode for the UE operating in single-registration mode in a network supporting N26 interface, the MME shall store the mapped EPS NAS security context with the uplink and downlink NAS COUNT counters associated with the derived K'ASME key set to the uplink and downlink NAS COUNT counters of the mapped EPS NAS security context respectively. The UE shall set the uplink and downlink NAS COUNT counters to the uplink and downlink NAS COUNT counters of the current 5G NAS security context respectively. During the handover from E-UTRAN to UTRAN/GERAN the MME signals the current downlink NAS COUNT value in a NAS security transparent container (see clause 9.9.2.6). During handover to or from E-UTRAN, the MME shall increment downlink NAS COUNT by one after it has created a NAS security transparent container (see clause 9.9.2.6 and 9.9.2.7). NOTE 2: During the handover from UTRAN/GERAN to E-UTRAN, the NAS security transparent container (see clause 9.9.2.7) is treated as an implicit SECURITY MODE COMMAND message for the UE and the MME, and therefore the MME regards the sending of the NAS security transparent container as the sending of an initial SECURITY MODE COMMAND message in order to derive and take into use a mapped EPS security context for the purpose of the NAS COUNT handling. In some NAS messages only 5 of the 8 NAS sequence number bits are transmitted. When this is the case, the receiver shall estimate the remaining 3 most significant bits of the sequence number. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.4.3 |
6,699 | 5.2.6.7.6 Nnef_TrafficInfluence_AppRelocationInfo operation | Service operation name: Nnef_TrafficInfluence_AppRelocationInfo Description: Forward the acknowledgement to the notification of UP path management event report to SMF. Inputs, Required: Notification Correlation Information, cause code. Cause code indicates whether the acknowledgement is a positive response or a negative response. Inputs, Optional: N6 traffic routing information as described in clause 5.6.7 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], Indication that buffering of uplink traffic should start, Information for EAS IP Replacement in 5GC. Outputs, Required: None. Outputs, Optional: None. See clause 4.3.6.3 for details on usage of this service operation for example for the usage of the Indication that buffering of uplink traffic should start. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.6.7.6 |
6,700 | 5.4.1.2.5 EAP result message transport procedure | 5.4.1.2.5.1 General The purpose of the EAP result message transport procedure is to provide an EAP-success message or an EAP-failure message, and ngKSI from the network to the UE, when the EAP message cannot be piggybacked by another NAS message. The EAP result message transport procedure is initiated: - by an AUTHENTICATION RESULT message with the EAP message IE carrying the EAP-success message or the EAP-failure message; or - by an AUTHENTICATION REJECT message with the EAP message IE carrying the EAP-failure message. 5.4.1.2.5.2 EAP result message transport procedure initiation by the network In order to initiate the EAP result message transport procedure, the AMF shall create an AUTHENTICATION RESULT message or an AUTHENTICATION REJECT message. The AMF shall set the EAP message IE of the AUTHENTICATION RESULT message to an EAP-success message or an EAP-failure message to be sent to the UE. If the AUTHENTICATION RESULT message is provided to a 5G-RG that is acting on behalf of an AUN3 device and the EAP message IE is set to an EAP-success message, the AMF shall include the AUN3 device security key IE in the AUTHENTICATION RESULT message with its value set to: a) the Master session key, if the AUN3 device does not support 5G key hierarchy; or b) the KWAGF key, if the AUN3 device supports 5G key hierarchy. NOTE: The network is aware from the AUN3 device subscription data in UDM whether the AUN3 device supports 5G key hierarchy or not as specified in subclause 7B.7 of 3GPP TS 33.501[ Security architecture and procedures for 5G System ] [24]. The AMF shall set the EAP message IE of the AUTHENTICATION REJECT message to an EAP-failure message to be sent to the UE. The AMF shall set the ngKSI IE of the AUTHENTICATION RESULT message or the AUTHENTICATION REJECT message to the ngKSI value selected in subclause 5.4.1.2.2.2, subclause 5.4.1.2.3.1 or subclause 5.4.1.2.3A.1. The AMF shall send the AUTHENTICATION RESULT message or the AUTHENTICATION REJECT message to the UE (see example in figure 5.4.1.2.5.2.1). Figure 5.4.1.2.5.2.1: EAP result message transport procedure Upon receipt of an AUTHENTICATION RESULT message or an AUTHENTICATION REJECT message with the EAP message IE, the UE handles the EAP message received in the EAP message IE and the ABBA if received of the AUTHENTICATION RESULT message or in the AUTHENTICATION REJECT message, and the 5G-RG that is acting on behalf of an AUN3 device handles the AUN3 device security key IE if received in the AUTHENTICATION RESULT message. | 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.5 |
Subsets and Splits
No saved queries yet
Save your SQL queries to embed, download, and access them later. Queries will appear here once saved.