Search is not available for this dataset
doc_id
int64 1
6.72k
⌀ | Section
stringlengths 5
247
⌀ | Content
stringlengths 501
147k
⌀ | Source
stringclasses 456
values | Document Title
stringclasses 22
values | Working Group
stringclasses 21
values | Series Subject
stringclasses 9
values | Subclause
stringlengths 1
13
⌀ |
|---|---|---|---|---|---|---|---|
2,601 | – DRX-ConfigPTM | The IE DRX-Config-PTM is used to configure DRX related parameters for PTM transmission as specified in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3]. DRX-Config-PTM information element -- ASN1START -- TAG-DRX-CONFIGPTM-START DRX-ConfigPTM-r17 ::= SEQUENCE { drx-onDurationTimerPTM-r17 CHOICE { subMilliSeconds INTEGER (1..31), milliSeconds ENUMERATED { ms1, ms2, ms3, ms4, ms5, ms6, ms8, ms10, ms20, ms30, ms40, ms50, ms60, ms80, ms100, ms200, ms300, ms400, ms500, ms600, ms800, ms1000, ms1200, ms1600, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1 } }, drx-InactivityTimerPTM-r17 ENUMERATED { ms0, ms1, ms2, ms3, ms4, ms5, ms6, ms8, ms10, ms20, ms30, ms40, ms50, ms60, ms80, ms100, ms200, ms300, ms500, ms750, ms1280, ms1920, ms2560, spare9, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1 }, drx-HARQ-RTT-TimerDL-PTM-r17 INTEGER (0..56) OPTIONAL, -- Cond HARQFeedback drx-RetransmissionTimerDL-PTM-r17 ENUMERATED { sl0, sl1, sl2, sl4, sl6, sl8, sl16, sl24, sl33, sl40, sl64, sl80, sl96, sl112, sl128, sl160, sl320, spare15, spare14, spare13, spare12, spare11, spare10, spare9, spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1 } OPTIONAL, -- Cond HARQFeedback drx-LongCycleStartOffsetPTM-r17 CHOICE { ms10 INTEGER(0..9), ms20 INTEGER(0..19), ms32 INTEGER(0..31), ms40 INTEGER(0..39), ms60 INTEGER(0..59), ms64 INTEGER(0..63), ms70 INTEGER(0..69), ms80 INTEGER(0..79), ms128 INTEGER(0..127), ms160 INTEGER(0..159), ms256 INTEGER(0..255), ms320 INTEGER(0..319), ms512 INTEGER(0..511), ms640 INTEGER(0..639), ms1024 INTEGER(0..1023), ms1280 INTEGER(0..1279), ms2048 INTEGER(0..2047), ms2560 INTEGER(0..2559), ms5120 INTEGER(0..5119), ms10240 INTEGER(0..10239) }, drx-SlotOffsetPTM-r17 INTEGER (0..31) } -- TAG-DRX-CONFIGPTM-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
2,602 | 4.4.6.6 Time duration of Scheduled IP Throughput in UL | a) This measurement provides the time duration to transmit a data burst excluding the last piece of data transmitted in the TTI when the buffer is emptied in uplink. For an eNodeB serving one or more RNs, packets transmitted between the E-UTRAN and RNs are excluded, i.e., only packets transmitted between the eNodeB (or RN) and UEs are counted. The measurement is also applicable to RN. b) DER(n=1) c) This measurement is obtained according to the definition in 3GPP TS 36.314[ Evolved Universal Terrestrial Radio Access (E-UTRA); Layer 2 - Measurements ] [11] clause 4.1.6 as sum of ThpTimeUl. Separate counters are maintained for each QCI. d) Each measurement is a real value representing active transmission time of a data burst in ms. The number of measurements is equal to the number of QCIs. e) The measurement name has the form DRB.IPTimeUl.QCI where QCI identifies the E-RAB level quality of service class. f) EUtranCellFDD EUtranCellTDD g) Valid for packet switched traffic. h) EPS. i) This measurement is to support the Integrity KPI "E-UTRAN IP Throughput" defined in [13]. | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.4.6.6 |
2,603 | A.3.10 Guidelines on use of lists (without ToAddModList and ToReleaseList) | As per clause 6.1.3, when using lists without the ToAddModList and ToReleaseList structure, the contents of the lists are always replaced. To illustrate this, an example is provided below: -- /example/ ASN1START -- TAG_EXAMPLE_LISTS_START AnExampleIE ::= SEQUENCE { elementList SEQUENCE (SIZE (1..maxNrofElements)) OF Element OPTIONAL, -- Need M ..., [[ elementListExt-v2030 SEQUENCE (SIZE (1..maxNrofElementsExt)) OF Element OPTIONAL, -- Need M ]] } Element ::= SEQUENCE { useFeatureX BOOLEAN, aField INTEGER (0..127) OPTIONAL, -- Need M anotherField INTEGER (0..127) OPTIONAL, -- Need R ... } maxNrofElements INTEGER ::= 8 maxNrofElements-1 INTEGER ::= 7 maxNrofElementsExt INTEGER ::= 8 maxNrofElementsExt-1 INTEGER ::= 7 -- TAG_EXAMPLE_LISTS_STOP -- /example/ ASN1STOP As can be seen, the elementList list itself uses Need M, but each list entry Element contains mandatory, Need M and Need R fields. If the list is first signalled to UE with 3 entries, and subsequently again with 2 entries, UE shall retain only the latter list, i.e. the list with 2 elements will completely replace the list with 3 elements. That also means that the field aField will be treated as if it was newly created, i.e. network must include it if it wishes UE to utilize the field even if it was previously signalled. This also implies that the Need M field (aField) will be treated in the same way as the Need R field (anotherField), i.e. delta signalling is not applied and the network has to signal the field to ensure UE does not release the value (which is why Need M should not normally be used in the entries of these lists). | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | A.3.10 |
2,604 | 6.9.2.3.1 Intra-gNB-CU handover and intra-ng-eNB handover | The gNB shall have a policy deciding at which intra-gNB -CU handovers the KgNB can be retained and at which a new KgNB needs to be derived. At an intra-gNB-CU handover, the gNB shall indicate to the UE whether to change or retain the current KgNB in the HO Command message. Retaining the current KgNB shall only be done during intra-gNB-CU handover. NOTE: The option of retaining the KeNB at intra-ng-eNB handover is not supported in ng-eNB. If the current KgNB is to be changed, the gNB/ng-eNB and the UE shall derive a KNG-RAN* as in Annex A.11/A.12 using target PCI, its frequency ARFCN-DL/EARFCN-DL, and either NH or the current KgNB depending on the following criteria: the gNB shall use the NH for deriving KNG-RAN* if an unused {NH, NCC} pair is available in the gNB (this is referred to as a vertical key derivation), otherwise if no unused {NH, NCC} pair is available in the gNB, the gNB shall derive KNG-RAN* from the current KgNB (this is referred to as a horizontal key derivation). The gNB shall send the NCC used for the KNG-RAN*derivation to UE in HO Command message. The gNB/ng-eNB and the UE shall use the KNG-RAN* as the KgNB, after handover. If the current KgNB is to be retained, the gNB and the UE shall continue using the current KgNB, after handover. NOTE 1: This clause is also applicable when gNB is implemented as a single unit, i.e., when the gNB is not split into CU and DU. NOTE 2: The key derivation mechanism described in this clause is also applicable to CHO defined in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [52]. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.9.2.3.1 |
2,605 | 4.23.9.4 Simultaneous change of Branching Point or UL CL and additional PSA controlled by I-SMF | This clause describes simultaneous change of UL-CL/BP function and additional PSA, e.g. addition of a new UL CL/BP and PDU Session Anchor (i.e. PSA2) and release of the existing UL CL/BP and additional PDU Session Anchor (i.e. PSA0), with target UPF(s) and source UPF(s) are all controlled by I-SMF. This procedure may be triggered after N2 handover or Xn based handover procedure. Figure 4.23.9.4-1: Simultaneous change of Branching Point or UL CL and additional PSA controlled by I-SMF Comparing to the clause 4.23.9.3, this procedure in addition changes the source UL-CL/BP by a target UL-CL/BP. 1-2. These steps are the same steps 1-2 in clause 4.23.9.3. 3. The I-SMF selects a UPF and using N4 establishes the target UL CL or BP of the PDU Session. 4. The I-SMF invokes Nsmf_PDUSession_Update Request (Indication of Change of traffic offload, (new allocated IPv6 prefix @PSA2, DNAI(s) supported by PSA2), (Removal of IPv6 prefix @PSA0, DNAI(s) supported by PSA0), DL Tunnel Info of the new UL CL/Branching Point) to SMF. The DL Tunnel Info of target UL CL/Branching Point is provided to SMF. 5. The SMF updates the remote PSA (PSA1) via N4 with the DL Tunnel Info of the Target UL CL/BP for the downlink traffic. 6-8. These steps are the same as steps 4-6 in clause 4.23.9.3. If EAS session continuity upon UL CL relocation is required, in step 7 the SMF provides the I-SMF additionally with an indication that a N9 forwarding tunnel to support the EAS session continuity is required, UL traffic filter for N9 forwarding by the target UL CL and the value of the timer to detect the end of activity on the N9 forwarding tunnel to support the EAS session continuity. Based on the received information, the I-SMF uses N4 to establish between the source UL CL and target UL CL the N9 forwarding tunnel to support the EAS session continuity. The I-SMF configures the source UL CL to forward traffic received from source L-PSA related to that PDU session toward the target UL CL via the N9 forwarding tunnel. 9. Same as steps 6-8 of clause 4.3.5.4. The I-SMF updates (R)AN for uplink traffic. 10-11. If a N9 forwarding tunnel to support the EAS session continuity is not established between the source UL CL and target UL CL, the I-SMF releases via N4 the source UL-CL/BP as the source UL-CL/BP is replaced by the target UL-CL/BP. The I-SMF also releases via N4 the PSA0 if PSA0 is not collocated with source UL CL/BP ; 12. This step is the same as step 9 in clause 4.23.9.3. 12a. If a N9 forwarding tunnel to support the EAS session continuity is established between the source UL CL and target UL CL, the I-SMF releases the source UL-CL/BP and PSA0 and the N9 forwarding tunnel in target UL CL when detection of no active traffic over the N9 forwarding tunnel takes place per the value of the timer to detect the end of activity on the N9 forwarding tunnel to support the EAS session continuity received from SMF. The detection can be done by Source UL CL, which notifies the I-SMF of no active traffic over the N9 forwarding tunnel. The I-SMF invokes Nsmf_PDUSession_Update Request to inform the SMF of the release of the resource in UL CL/BP and PSA0 for the PDU Session. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.23.9.4 |
2,606 | 10.5.1.7 Mobile Station Classmark 3 | The purpose of the Mobile Station Classmark 3 information element is to provide the network with information concerning aspects of the mobile station. The contents might affect the manner in which the network handles the operation of the mobile station. The Mobile Station Classmark information indicates general mobile station characteristics and it shall therefore, except for fields explicitly indicated, be independent of the frequency band of the channel it is sent on. The Mobile Station Classmark 3 is a type 4 information element with a maximum of 34 octets length. The value part of a Mobile Station Classmark 3 information element is coded as shown in figure 10.5.1.7/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.1.7/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . NOTE: The 34 octet limit is so that the CLASSMARK CHANGE message will fit in up to two layer 2 frames. SEMANTIC RULE: a multiband mobile station shall provide information about all frequency bands it can support. A single band mobile station shall not indicate the band it supports in the Multiband Supported, GSM 400 Bands Supported, GSM 710 Associated Radio Capability, GSM 750 Associated Radio Capability, T-GSM 810 Associated Radio Capability, GSM 850 Associated Radio Capability or GSM 1900 Associated Radio Capability fields in the Mobile Station Classmark 3. Due to shared radio frequency channel numbers between GSM 1800 and GSM 1900, the mobile should indicate support for either GSM 1800 band OR GSM 1900 band. SEMANTIC RULE: a mobile station shall include the MS Measurement Capability field if the Multi Slot Class field contains a value of 19 or greater (see 3GPP TS 45.002[ None ] [32]). Typically, the number of spare bits at the end is the minimum to reach an octet boundary. The receiver may add any number of bits set to "0" at the end of the received string if needed for correct decoding. Figure 10.5.1.7/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] Mobile Station Classmark 3 information element Table 10.5.1.7/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Mobile Station Classmark 3 information element (continued...) Table 10.5.1.7/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] (continued): Mobile Station Classmark 3 information element Table 10.5.1.7/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] (continued): Mobile Station Classmark 3 information element Table 10.5.1.7/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] (continued): Mobile Station Classmark 3 information element Table 10.5.1.7/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] (continued): Mobile Station Classmark 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.1.7 |
2,607 | 5.2.18.3.3 Nucmf_UECapabilityManagement_Subscribe service operation | Service operation name: Nucmf_UECapabilityManagement_Subscribe Description: The NF consumer subscribes for updates to UCMF dictionary entries and provides the coding format in which UE Radio Access Capability is expected by NF. The UCMF shall check the requested consumer is authorized to subscribe to requested updates. Inputs, Required: Coding format. Inputs, Optional: None. Outputs, Required: None. Outputs, Optional: None. The Coding format indicates the format of the UE Radio Access Capability as defined in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [16] or TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [12]. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.18.3.3 |
2,608 | 10.3.1 EN-DC | The Secondary Node Modification procedure may be initiated either by the MN or by the SN and be used to modify, establish or release bearer contexts, to transfer bearer contexts to and from the SN or to modify other properties of the UE context within the same SN. It may also be used to transfer an NR RRC message from the SN to the UE via the MN and the response from the UE via MN to the SN (e.g. when SRB3 is not used). In case of CPA or inter-SN CPC, this procedure is used to modify CPA or inter-SN CPC configuration within the same candidate SN. In case of CPA or inter-SN CPC, this procedure may also be triggered by the candidate SN to add some prepared PSCells from the suggested list or cancel part of the prepared PSCells. In case of intra-SN CPC, this procedure is used to configure, modify or release intra-SN CPC configuration. This procedure may be initiated by the MN or SN to request the SN or MN to deactivate or activate the SCG. The Secondary Node modification procedure does not necessarily need to involve signalling towards the UE. MN initiated SN Modification Figure 10.3.1-1: SN Modification procedure - MN initiated The MN uses the procedure to initiate configuration changes of the SCG within the same SN, e.g. the addition, modification or release of SCG bearer(s) and the SCG RLC bearer of split bearer(s), as well as configuration changes for SN terminated MCG bearers. Bearer termination point change is realized by adding the new bearer configuration and releasing the old bearer configuration within a single MN initiated SN Modification procedure for the respective E-RAB. The MN uses this procedure to perform handover within the same MN while keeping the SN. The MN also uses the procedure to query the current SCG configuration, e.g. when delta configuration is applied in an MN initiated SN change. The MN also uses the procedure to provide the S-RLF related information to the SN. The MN also uses this procedure to activate or deactivate the SCG. The MN may not use the procedure to initiate the addition, modification or release of SCG SCells. The SN may reject the request, except if it concerns the release of SN terminated bearer(s) or the SCG RLC bearer of MN terminated bearer(s), or if it is used to perform handover within the same MN while keeping the SN. Figure 10.3.1-1 shows an example signalling flow for an MN initiated SN Modification procedure. 1. The MN sends the SgNB Modification Request message, which may contain bearer context related or other UE context related information, data forwarding address information (if applicable) and the requested SCG configuration information, including the UE capability coordination result to be used as basis for the reconfiguration by the SN. The MN may request the SCG to be activated or deactivated. In case a security key update in the SN is required, a new SgNB Security Key is included. In case of SCG RLC re-establishment for E-RABs configured with an MN terminated bearer with an SCG RLC bearer for which no bearer type change is performed, the MN provides a new UL GTP tunnel endpoint to the SN. The SN shall continue sending UL PDCP PDUs to the MN with the previous UL GTP tunnel endpoint until it re-establishes the RLC and use the new UL GTP tunnel endpoint after re-establishment. In case of PDCP re-establishment for E-RABs configured with an SN terminated bearer with an MCG RLC bearer for which no bearer type change is performed, the MN provides a new DL GTP tunnel endpoint to the SN. The SN shall continue sending DL PDCP PDUs to the MN with the previous DL GTP tunnel endpoint until it performs PDCP re-establishment and use the new DL GTP tunnel endpoint starting with the PDCP re-establishment. 2. The SN responds with the SgNB Modification Request Acknowledge message, which may contain SCG radio resource configuration information within a NR RRC configuration message and data forwarding address information (if applicable). If the MN requested the SCG to be activated or deactivated, the SN indicates whether the SCG is activated or deactivated. In case of a security key update (with or without PSCell change), for E-RABs configured with the MN terminated bearer option that require X2-U resources between the MN and the SN, for which no bearer type change is performed, the SN provides a new DL GTP tunnel endpoint to the MN. The MN shall continue sending DL PDCP PDUs to the SN with the previous DL GTP tunnel endpoint until it performs PDCP re-establishment or PDCP data recovery, and use the new DL GTP tunnel endpoint starting with the PDCP re-establishment or data recovery. In case of a security key update (with or without PSCell change), for E-RABs configured with the SN terminated bearer option that require X2-U resources between the MN and the SN, for which no bearer type change is performed, the SN provides a new UL GTP tunnel endpoint to the MN. The MN shall continue sending UL PDCP PDUs to the SN with the previous UL GTP tunnel endpoint until it re-establishes the RLC and use the new UL GTP tunnel endpoint after re-establishment. NOTE 00: In case SN includes the indication of full RRC configuration in SgNB Modification Request Acknowledge message to MN e.g. comprehension failure upon intra-CU inter-DU change, MN performs release and add of the NR SCG part of the configuration but does not release SN terminated radio bearers towards the UE. 3-5. The MN initiates the RRC connection reconfiguration procedure, including the NR RRC configuration message. The UE applies the new configuration, synchronizes to the MN (if instructed, in case of intra-MN handover) and replies with RRCConnectionReconfigurationComplete, including a NR RRC response message, if needed. In case the UE is unable to comply with (part of) the configuration included in the RRCConnectionReconfiguration message, it performs the reconfiguration failure procedure. 6. Upon successful completion of the reconfiguration, the success of the procedure is indicated in the SgNB Reconfiguration Complete message. 7. If instructed, the UE performs synchronisation towards the PSCell of the SN as described in SgNB addition procedure. Otherwise, the UE may perform UL transmission after having applied the new configuration. 8. If PDCP termination point is changed for bearers using RLC AM, and when RRC full configuration is not used, the SN Status Transfer takes place between the MN and the SN (Figure 10.3.1-1 depicts the case where a bearer context is transferred from the MN to the SN). NOTE 0: The SN may not be aware that a SN terminated bearer requested to be released is reconfigured to a MN terminated bearer. The SN Status for the released SN terminated bearers with RLC AM may also be transferred to the MN. 9. If applicable, data forwarding between MN and the SN takes place (Figure 10.3.1-1 depicts the case where a bearer context is transferred from the MN to the SN). 10. The SN sends the Secondary RAT Data Usage Report message to the MN and includes the data volumes delivered to and received from the UE over the NR radio for the E-RABs to be released and for the E-RABs for which the S1 UL GTP Tunnel endpoint was requested to be modified. NOTE 1: The order the SN sends the Secondary RAT Data Usage Report message and performs data forwarding with MN is not defined. The SN may send the report when the transmission of the related bearer is stopped. 11. If applicable, a path update is performed. SN initiated SN Modification with MN involvement Figure 10.3.1-2: SN Modification procedure - SN initiated with MN involvement The SN uses the procedure to perform configuration changes of the SCG within the same SN, e.g. to trigger the release of SCG bearer(s) and the SCG RLC bearer of split bearer(s) (upon which the MN may release the bearer or maintain current bearer type or reconfigure it to an MCG bearer, either MN terminated or SN terminated), to trigger the release of SCG resources (e.g., release SCG lower layer resources but keep SN), and to trigger PSCell change (e.g. when a new security key is required or when the MN needs to perform PDCP data recovery). The MN cannot reject the release request of SCG bearer and the SCG RLC bearer of a split bearer and the release request of SCG resources. The SN also uses this procedure to activate or deactivate the SCG. The MN shall either accept modification of all of the requested SCG bearer(s) and the SCG RLC bearer of split bearer(s) and the request of activation or deactivation of the SCG, or fail the procedure. Figure 10.3.1-2 shows an example signalling flow for an SN initiated SgNB Modification procedure, with MN involvement. 1. The SN sends the SgNB Modification Required message including a NR RRC configuration message, which may contain bearer context related, other UE context related information and the new SCG radio resource configuration. The SN may request the SCG to be activated or deactivated. For bearer release or modification, a corresponding E-RAB list is included in the SgNB Modification Required message. In case of change of security key, the PDCP Change Indication indicates that a S-KgNB update is required. In case the MN needs to perform PDCP data recovery, the PDCP Change Indication indicates that PDCP data recovery is required. In case SN decides to trigger SCG release, the E-RABs to be modified list includes all the E-RABs of the UE with SCG resource indicated as not present for each E-RAB. The SN can decide whether the change of security key is required. NOTE 1a: In case SN includes the indication of full RRC configuration in SgNB Modification Required message to MN e.g. comprehension failure upon intra-CU inter-DU change, MN performs release and add of the NR SCG part of the configuration but does not release SN terminated radio bearers towards the UE. NOTE 1b: In case that a MN initiated conditional reconfiguration (e.g. CHO or MN initiated inter-SN CPC) is prepared, and if any execution of a prepared SN initiated intra-SN CPC procedure or reconfiguration of the SCG, the SN notifies to the MN via the SgNB Modification Required message. In this case, the steps 2 and 3 are skipped. NOTE 1c: In case of SN initiated inter-SN CPC and in case that a candidate SN triggered the SN Initiated SN Modification procedure to include some more prepared PSCells (within the candidate cells suggested by the source SN in SN initiated inter-SN CPC) or to remove some prepared PSCells, the MN may decide to trigger the step 2 towards the source SN. 2/3. The MN initiated SN Modification procedure may be triggered by the SN Modification Required message (e.g. to provide information such as data forwarding addresses, new SN security key, measurement gap, etc...) NOTE 2: If only SN security key is provided in step 2, the MN does not need to wait for the reception of step 3 to initiate the RRC connection reconfiguration procedure. 4. The MN sends the RRCConnectionReconfiguration message including a NR RRC configuration message to the UE including the new SCG radio resource configuration. 5. The UE applies the new configuration and sends the RRCConnectionReconfigurationComplete message, including an encoded NR RRC response message, if needed. In case the UE is unable to comply with (part of) the configuration included in the RRCConnectionReconfiguration message, it performs the reconfiguration failure procedure. 6. Upon successful completion of the reconfiguration, the success of the procedure is indicated in the SgNB Modification Confirm message containing the encoded NR RRC response message, if received from the UE. 7. If instructed, the UE performs synchronisation towards the PSCell of the SN as described in SN addition procedure. Otherwise, the UE may perform UL transmission after having applied the new configuration. 8. If PDCP termination point is changed for bearers using RLC AM, and when RRC full configuration is not used, the SN Status Transfer takes place between the MN and the SN (Figure 10.3.1-2 depicts the case where a bearer context is transferred from the SN to the MN). NOTE 2a: The SN may not be aware that a SN terminated bearer requesting to release is reconfigured to a MN terminated bearer. The SN Status for the released SN terminated bearers with RLC AM may also be transferred to the MN. 9. If applicable, data forwarding between MN and the SN takes place (Figure 10.3.1-2 depicts the case where a bearer context is transferred from the SN to the MN). 10. The SN sends the Secondary RAT Data Usage Report message to the MN and includes the data volumes delivered to and received from the UE over the NR radio for the E-RABs to be released. NOTE 3: The order the SN sends the Secondary RAT Data Usage Report message and performs data forwarding with MN is not defined. The SN may send the report when the transmission of the related bearer is stopped. 11. If applicable, a path update is performed. SN initiated SN Modification without MN involvement Figure 10.3.1-3: SN modification - SN initiated without MN involvement The SN initiated modification without MN involved procedure is used to modify the configuration within SN in case no coordination with MN is required, including the addition/modification/release of SCG SCell and PSCell change (e.g. when the security key does not need to be changed and the MN does not need to be involved in PDCP recovery). The SN may initiate the procedure to configure, modify or release intra-SN CPC configuration within the same SN. Figure 10.3.1-3 shows an example signalling flow for SN initiated SN modification procedure, without MN involvement. The SN can decide whether the Random Access procedure is required. 1. The SN sends the RRCReconfiguration message to the UE through SRB3. The UE applies the new configuration. In case the UE is unable to comply with (part of) the configuration included in the RRCReconfiguration message, it performs the reconfiguration failure procedure. 2. If instructed, the UE performs synchronisation towards the PSCell of the SN. 3. The UE replies with the RRCReconfigurationComplete message. SN initiated Conditional SN Modification without MN involvement (SRB3 is used) Figure 10.3.1-3a: SN Modification - SN-initiated without MN involvement and SRB3 is used to configure intra-SN CPC. The SN initiates the procedure when it needs to transfer an NR RRC message to the UE and SRB3 is used to configure intra-SN CPC. 1. The SN sends the RRCReconfiguration message including CPC configuration to the UE through SRB3. 2. The UE applies the new configuration. In case the UE is unable to comply with (part of) the configuration included in the RRCReconfiguration message, it performs the reconfiguration failure procedure. The UE starts evaluating the CPC execution conditions for the candidate PSCell(s). The UE maintains connection with the source PSCell and replies with the RRCReconfigurationComplete message to the SN via SRB3. 3. If at least one CPC candidate PSCell satisfies the corresponding CPC execution condition, the UE detaches from the source PSCell, applies the stored configuration corresponding to the selected candidate PSCell and synchronises to the candidate PSCell. 4. The UE completes the CPC execution procedure by sending an RRCReconfigurationComplete message to the new PSCell. Transfer of an NR RRC message to/from the UE (when SRB3 is not used) Figure 10.3.1-4: Transfer of an NR RRC message to/from the UE The SN initiates the procedure when it needs to transfer an NR RRC message to the UE and SRB3 is not used. 1. The SN initiates the procedure by sending the SgNB Modification Required to the MN. 2. The MN forwards the NR RRC message to the UE in the RRCConnectionReconfiguration message. 3. The UE applies the new configuration and replies with the RRCConnectionReconfigurationComplete message. In case the UE is unable to comply with (part of) the configuration included in the NR RRC message, it performs the reconfiguration failure procedure. 4. The MN forwards the NR RRC response message, if received from the UE, to the SN in the SgNB Modification Confirm message. 5. If instructed, the UE performs synchronisation towards the PSCell of the SN as described in SgNB Addition procedure. Otherwise the UE may perform UL transmission after having applied the new configuration. SN initiated Conditional SN Modification without MN involvement (SRB3 is not used) Figure 10.3.1-5: SN Modification - SN-initiated without MN involvement and SRB3 is not used to configure intra-SN CPC The SN initiates the procedure when it needs to transfer an NR RRC message to the UE and SRB3 is not used to configure intra-SN CPC. 1. The SN initiates the procedure by sending the SgNB Modification Required to the MN including the SN RRC reconfiguration message with CPC configuration. 2. The MN forwards the SN RRC reconfiguration message to the UE including it in the RRCConnectionReconfiguration message. 3. The UE replies with the RRCConnectionReconfigurationComplete message by including the SN RRC reconfiguration complete message. In case the UE is unable to comply with (part of) the configuration included in the SN RRC reconfiguration message, it performs the reconfiguration failure procedure. The UE maintains connection with source PSCell after receiving CPC configuration, and starts evaluating the CPC execution conditions for the candidate PSCell(s). 4. The MN forwards the SN RRC response message, if received from the UE, to the SN by including it in the SgNB Modification Confirm message. 5. If at least one CPC candidate PSCell satisfies the corresponding CPC execution condition, the UE completes the CPC execution procedure by an ULInformationTransferMRDC message to the MN which includes an embedded RRCReconfigurationComplete message to the selected target PSCell. 6. The RRCReconfigurationComplete message is forwarded to the SN embedded in RRC Transfer message. 7. The UE detaches from the source PSCell, applies the stored corresponding configuration and synchronises to the selected candidate PSCell. | 3GPP TS 37.340 | Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Overall Description; Stage-2 | RAN2 | 3GPP Series : 37 , Multiple radio access technology aspects | 10.3.1 |
2,609 | 4.2.2 Signalling radio bearers | "Signalling Radio Bearers" (SRBs) are defined as Radio Bearers (RBs) that are used only for the transmission of RRC and NAS messages. More specifically, the following SRBs are defined: - SRB0 is for RRC messages using the CCCH logical channel; - SRB1 is for RRC messages (which may include a piggybacked NAS message) as well as for NAS messages prior to the establishment of SRB2, all using DCCH logical channel; - SRB2 is for NAS messages and for RRC messages which include logged measurement information, all using DCCH logical channel. SRB2 has a lower priority than SRB1 and may be configured by the network after AS security activation; - SRB3 is for specific RRC messages when UE is in (NG)EN-DC or NR-DC, all using DCCH logical channel; - SRB4 is for RRC messages which include application layer measurement report information, all using DCCH logical channel. SRB4 has a lower priority than SRB1 and can only be configured by the network after AS security activation. - SRB5 is for RRC messages which include application layer measurement report information, all using DCCH logical channel. SRB5 has a lower priority than SRB1 and SRB3 and can only be configured by the SN serving the SCG when the UE is in NR-DC, after AS security activation. In downlink, piggybacking of NAS messages is used only for one dependant (i.e. with joint success/failure) procedure: bearer establishment/modification/release. In uplink piggybacking of NAS message is used only for transferring the initial NAS message during connection setup and connection resume. NOTE 1: The NAS messages transferred via SRB2 are also contained in RRC messages, which however do not include any RRC protocol control information. Once AS security is activated, all RRC messages on SRB1, SRB2, SRB3, SRB4 and SRB5, including those containing NAS messages, are integrity protected and ciphered by PDCP. NAS independently applies integrity protection and ciphering to the NAS messages, see TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [23]. Split SRB is supported for all the MR-DC options as well as MP in both SRB1 and SRB2 (split SRB is not supported for SRB0, SRB3, SRB4 and SRB5). For operation with shared spectrum channel access in FR1, SRB0, SRB1 and SRB3 are assigned with the highest priority Channel Access Priority Class (CAPC), (i.e. CAPC = 1) while CAPC for SRB2 is configurable. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 4.2.2 |
2,610 | 13.4A Wildcarded Public User Identity | Public User Identities may be stored in the HSS as Wildcarded Public User Identities. A Wildcarded Public User Identity represents a collection of Public User Identities that share the same service profile and are included in the same implicit registration set. Wildcarded Public User Identities enable optimisation of the operation and maintenance of the nodes for the case in which a large amount of users are registered together and handled in the same way by the network. The format of a Wildcarded Public User Identity is the same as for the Wildcarded PSI described in clause 13.5. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 13.4A |
2,611 | 4.3.32.1 IAB architecture and functional entities | Integrated access and backhaul (IAB) enables wireless in-band and out-of-band relaying of NR Uu access traffic via NR Uu backhaul links. At high level, IAB has the following characteristics: - IAB uses the CU/DU architecture defined in TS 38.401[ NG-RAN; Architecture description ] [90], and the IAB operation via F1 (between IAB-donor and IAB-node) is invisible to the EPC. - IAB performs relaying at layer-2, and therefore does not require a local S/P-GW; - IAB supports multi-hop backhauling; - IAB supports dynamic topology update, i.e. the IAB-node can change the parent node, e.g. another IAB-node, or the IAB-donor, during operation, for example in response to backhaul link failure or blockage. Figure 4.3.32.1-1 shows the IAB reference architecture with two backhaul hops, when connected to EPC, where both the IAB-node and the UE connect to the 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 ] [85]. Figure 4.3.32.1-1: IAB architecture for EPS, with IAB-node and UE both connected to EPC Each relay, referred to as IAB-node, consists of a gNB-DU function and a UE function (referred to as IAB-UE). The gNB-DU in the IAB-node is responsible for providing NR Uu access to UEs and child IAB-nodes. The corresponding gNB-CU function resides on the IAB-donor gNB (referred to as IAB-donor-CU), which controls IAB-node gNB-DU via the F1 interface. When a UE connects to EPC via an IAB-node, the gNB-DU of the IAB-node appears as a normal secondary gNB to the UE. When the IAB-UE of another IAB-node connects to EPC via the IAB-node, the gNB-DU of the IAB-node also appears as a secondary gNB to the IAB-UE. The IAB-UE function reuses UE procedures to connect to: - the gNB-DU on a parent IAB-node or IAB-donor for access and backhauling; - the gNB-CU on the IAB-donor via RRC for control of the access and backhaul link; - EPC, e.g. MME, - OAM system via a PDN connection (based on implementation). NOTE: The EPC, e.g. MME, may detect that a PDN connection for the IAB-UE is for the OAM system access, e.g. by checking the APN and/or configuration. It is up to the operator configuration to choose whether to use 1 or multiple EPS bearers for OAM traffic and the appropriate QoS parameters, e.g. using QCI=6 for software downloading, and QCI=80 or a pre-configured QCI for alarm or control traffic. | 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.32.1 |
2,612 | 3.1 Symbols | For the purposes of the present document, the following symbols apply: Resource element with frequency-domain index and time-domain index Value of resource element [for antenna port] Matrix for supporting cyclic delay diversity Density of random access opportunities per radio frame Carrier frequency PRACH resource frequency index within the considered time-domain location PRACH frequency hopping offset, expressed as a number of resource blocks Start symbol in slot 0 for NPDCCH Start symbol in slot 0 for NPDSCH Bandwidth for PSBCH transmission, expressed as a number of subcarriers Bandwidth for PSBCH transmission, expressed as a number of resource blocks Bandwidth for PSCCH transmission, expressed as a number of subcarriers Bandwidth for PSCCH transmission, expressed as a number of resource blocks Bandwidth for PSDCH transmission, expressed as a number of subcarriers Bandwidth for PSDCH transmission, expressed as a number of resource blocks Scheduled bandwidth for PSSCH transmission, expressed as a number of subcarriers Scheduled bandwidth for PSSCH transmission, expressed as a number of resource blocks Scheduled bandwidth for uplink transmission, expressed as a number of subcarriers Scheduled bandwidth for uplink transmission, expressed as a number of resource blocks Scheduled number of repetitions of a NPUSCH transmission Scheduled number of repetitions of a NPDSCH transmission Scheduled bandwidth for uplink NPUSCH transmission, expressed as a number of subcarriers Number of repetitions of identical slots for NPUSCH Number of coded bits to transmit on a physical channel [for codeword ] Number of modulation symbols to transmit on a physical channel [for codeword ] Number of modulation symbols to transmit per layer for a physical channel Number of modulation symbols to transmit per antenna port for a physical channel Number of consecutive subcarriers in an UL resource unit for PUSCH sub-PRB allocation Number of slots in an UL resource unit for PUSCH sub-PRB allocation Number of SC-FDMA symbols in an uplink slot for PUSCH sub-PRB allocation Number of subcarriers in the frequency domain for PUSCH sub-PRB allocation Number of reference signal sequences available for the UL resource unit size for PUSCH sub-PRB allocation Number of scheduled UL resource units for PUSCH sub-PRB allocation A constant equal to 2048 for , 4096 for and 8192 for Downlink cyclic prefix length for OFDM symbol in a slot Cyclic shift value used for random access preamble generation Number of cyclic shifts used for PUCCH formats 1/1a/1b in a resource block with a mix of formats 1/1a/1b and 2/2a/2b Bandwidth available for use by PUCCH formats 2/2a/2b, expressed in multiples of The offset used for PUSCH frequency hopping, expressed in number of resource blocks (set by higher layers) Physical layer cell identity Narrowband physical layer cell identity MBSFN area identity Physical layer sidelink synchronization identity Positioning reference signal identity Downlink bandwidth configuration, expressed in multiples of Smallest downlink bandwidth configuration, expressed in multiples of Largest downlink bandwidth configuration, expressed in multiples of Uplink bandwidth configuration, expressed in multiples of Smallest uplink bandwidth configuration, expressed in multiples of Largest uplink bandwidth configuration, expressed in multiples of Sidelink bandwidth configuration, expressed in multiples of Duration of RSS measured in subframes Number of scheduled subframes for NPDSCH transmission Number of symbols for NPSS in a subframe Number of symbols for NSSS in a subframe Number of consecutive subcarriers in an UL resource unit for NB-IoT Number of reference signal sequences available for the UL resource unit size Number of scheduled UL resource units for NB-IoT Total number of uplink narrowbands Total number of uplink widebands Number of subcarriers in the frequency domain for NB-IoT Number of consecutive absolute subframes over which the scrambling sequence stays the same Total number of absolute subframes a PUSCH with repetition spans expressed as a number of absolute subframes Number of repetitions of a PUSCH transmission Number of consecutive absolute subframes over which PUCCH or PUSCH stays at the same narrowband before hopping to another narrowband, expressed as a number of absolute subframes Narrowband offset between one narrowband and the next narrowband a PUSCH hops to, expressed as a number of uplink narrowbands Total number of absolute subframes a PUCCH with repetition spans, expressed as a number of absolute subframes Number of repetitions of a PUCCH transmission Number of PRACH repetitions per preamble transmission attempt Number of subframes allowed for preamble transmission within a 1024-frame interval PRACH starting subframe periodicity Number of NPRACH repetitions per preamble transmission attempt NPRACH resource periodicity Frequency location of the first sub-carrier allocated to NPRACH Number of sub-carriers allocated to NPRACH Number of starting sub-carriers allocated for UE initiated random access NPRACH starting subframe Fraction for starting subcarrier index for UE support for multi-tone msg3 transmission Periodicity for NPDSCH/NPDCCH gaps Duration for NPDSCH/NPDCCH gaps Threshold for applying NPDSCH/NPDCCH gaps Total number of downlink narrowbands Total number of downlink widebands Total number of absolute subframes a PDSCH with repetition spans, expressed as a number of absolute subframes Number of repetitions of a PDSCH transmission Number of consecutive absolute subframes over which MPDCCH or PDSCH stays at the same narrowband before hopping to another narrowband, expressed as a number of absolute subframes Number of narrowbands over which MPDCCH or PDSCH frequency hops Narrowband offset between one narrowband and the next narrowband an MPDCCH or PDSCH hops to, expressed as a number of downlink narrowbands Number of times a PDSCH carrying SIB1-BR is transmitted over 8 radio frames Total number of absolute subframes a MPDCCH with repetition spans, expressed as a number of absolute subframes Number of repetitions of a MPDCCH transmission Total number of absolute subframes a MPDCCH search space with maximum repetition level spans, expressed as a number of absolute subframes Maximum repetition level of a MPDCCH search space Number of ECCEs in a subframe for one MPDCCH Number of OFDM symbols in a downlink slot Number of SC-FDMA symbols in an uplink slot Number of symbols in a guard period for narrowband or wideband retuning Number of consecutive slots in an UL resource unit for NB-IoT Number of SC-FDMA symbols in a sidelink slot Resource block size in the frequency domain, expressed as a number of subcarriers Number of sub-bands for PUSCH frequency-hopping with predefined hopping pattern Size of each sub-band for PUSCH frequency-hopping with predefined hopping pattern, expressed as a number of resource blocks Size of narrow-band random-access resource in number of subcarriers Number of downlink to uplink switch points within the radio frame Number of reference symbols per slot for PUCCH Number of reference symbols per subslot or per slot for SPUCCH Timing offset between uplink and downlink radio frames at the UE, expressed in units of Fixed timing advance offset, expressed in units of Timing offset between sidelink and timing reference frames at the UE, expressed in units of Resource index for PUCCH formats 1/1a/1b Resource index for PUCCH formats 2/2a/2b Resource index for PUCCH format 3 Number of PDCCHs present in a subframe Physical resource block number First physical resource block occupied by PRACH resource considered First physical resource block available for PRACH Lowest PRB number of RSS Subcarrier occupied by NPRACH resource considered Virtual resource block number Radio network temporary identifier Sidelink group destination identity System frame number Slot number within a radio frame Absolute subframe number Index for subframes allowed for preamble transmission Starting frame offset of RSS in each RSS period Number of antenna ports used for transmission of a channel Antenna port number Period of RSS measured in frames Codeword number Index for PRACH versions with same preamble format and PRACH density Qm Modulation order: 1 for π/2-BPSK, 2 for QPSK, 4 for 16QAM, 6 for 64QAM and 8 for 256QAM transmissions Time-continuous baseband signal for antenna port and SC-FDMA/OFDM symbol in a slot Radio frame indicator index of PRACH opportunity Half frame index of PRACH opportunity within the radio frame Uplink subframe number for start of PRACH opportunity within the half frame Radio frame duration Basic time unit Slot duration Precoding matrix for downlink spatial multiplexing Amplitude scaling for PRACH Amplitude scaling for NPRACH Amplitude scaling for PUCCH Amplitude scaling for PUSCH Amplitude scaling for NPUSCH Amplitude scaling for SPUCCH Amplitude scaling for sounding reference symbols Subcarrier spacing Subcarrier spacing for the random access preamble Number of transmission layers | 3GPP TS 36.211 | Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation | RAN1 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 3.1 |
2,613 | 6.8.2.3 VLR/SGSN | The R99+ VLR/SGSN shall perform GSM AKA using a triplet that is either: a) retrieved from the local database, b) provided by the HLR/AuC, or c) provided by the previously visited VLR/SGSN. NOTE: All triplets are originally provided by the HLR/AuC. GSM AKA results in the establishment of a GSM security context; the GSM cipher key Kc and the cipher key sequence number CKSN are stored in the VLR/SGSN. When the user is attached to a UTRAN, the R99+ VLR/SGSN derives the UMTS cipher/integrity keys from the GSM cipher key using the following conversion functions: a) c4: CK[UMTS] = Kc || Kc; b) c5: IK[UMTS] = Kc1 xor Kc2 || Kc || Kc1 xor Kc2; whereby in c5, Kci are both 32 bits long and Kc = Kc1 || Kc2. The UMTS cipher/integrity keys are then sent to the RNC where the ciphering and integrity algorithms are allocated. When the user is attached to a GSM BSS and the user receives service from an MSC/VLR, the cipher key Kc is sent to the BSC (and forwarded to the BTS). When the user receives service from an SGSN, the cipher key Kc is applied in the SGSN itself. | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | 6.8.2.3 |
2,614 | 6.1.2.3 Network slice constraints | The 5G system shall support a mechanism to prevent a UE from trying to access a radio resource dedicated to a specific private slice for any purpose other than that authorized by the associated third-party. NOTE 1: UEs that are not authorized to access a specific private slice will not be able to access it for emergency calls if the private slice does not support emergency services. The 5G system shall support a mechanism to configure a specific geographic area in which a network slice is accessible, i.e. a UE shall be within the geographical area in order to access the network slice. The 5G system shall support a mechanism to limit a UE to only receiving service from an authorized slice. For a UE authorized to access to multiple network slices of one operator which cannot be simultaneously used by the UE (e.g. due to radio frequency restrictions), the 5G system shall minimize service interruption time when the UE changes the access from one network slice to another network slice. (e.g. based on changes of active applications). For traffic pertaining to a network slice offered via a relay node, 5G system shall use only radio resources (e.g. frequency band) allowed for the network slice. NOTE 2: Allowed radio resources (e.g., frequency band) may be different for direct network connections (between UE and NG-RAN) than for backhaul connections (between the relay node and the NG-RAN). The 5G system shall support a mechanism to prevent a UE from registering with a network slice when the maximum number of UEs for that slice are registered. The 5G system shall support a mechanism to prevent a UE from establishing a new data session within a network slice when the maximum number of data sessions for that slice are established. NOTE 3: Based on national/regional regulations and operator policy, exemptions can be provided for UEs configured for priority services (e.g., MPS) and for priority service sessions. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.1.2.3 |
2,615 | 4.4.6.8 UL scheduled IP throughput distribution | a) This measurement provides the distribution of samples with UL UE IP throughput in different throughput ranges during one measurement period. This measurement is a useful measure of the statistics information to distinguish the scenarios that when some UEs experience is not good in uplink. For an eNodeB serving one or more RNs, packets transmitted between the E-UTRAN and RNs are excluded, i.e., only packets transmitted between the eNodeB (or RN) and UEs are counted. The measurement is also applicable to RN. b) CC c) Each measurement sample is obtained according to the definition in TS 36.314[ Evolved Universal Terrestrial Radio Access (E-UTRA); Layer 2 - Measurements ] [11] clause 4.1.11.2. Depending on the value of the sample, the proper bin of the counter is increased. The number of samples during one measurement period is provided by the operator. d) A set of integers, each representing the (integer) number of samples with a UL UE IP throughput in the range represented by that bin. e) DRB.IPThrUlDist.BinX which indicates the distribution of UL IP Throughput. f) EUtranCellFDD EUtranCellTDD g) Valid for packet switched traffic h) EPS | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.4.6.8 |
2,616 | 16.9.3 Radio Resource Allocation 16.9.3.1 General | For NR sidelink communication, the UE can operate in two modes as specified in 5.7.2 for resource allocation in sidelink: - Scheduled resource allocation, characterized by: - The UE needs to be RRC_CONNECTED in order to transmit data; - NG-RAN schedules transmission resources. - UE autonomous resource selection, characterized by: - The UE can transmit data when inside NG-RAN coverage, irrespective of which RRC state the UE is in, and when outside NG-RAN coverage; - The UE autonomously selects transmission resources from resource pool(s). For NR sidelink communication, the UE performs sidelink transmissions only on a single carrier. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.9.3 |
2,617 | 14.3 Root NAI | The Root NAI shall take the form of a NAI, and shall have the form username@realm as specified in clause 2.1 of IETF RFC 4282 [53]. The username part format of the Root NAI shall comply with IETF RFC 4187 [50] when EAP AKA authentication is used and with IETF RFC 4186 [51], when EAP SIM authentication is used. When the username part includes the IMSI, the Root NAI shall be built according to the following steps: 1. Generate an identity conforming to NAI format from IMSI as defined in EAP SIM [51] and EAP AKA [50] as appropriate; 2. Convert the leading digits of the IMSI, i.e. MNC and MCC, into a domain name, as described in clause 14.2. The result will be a root NAI of the form: "0<IMSI>@wlan.mnc<MNC>.mcc<MCC>.3gppnetwork.org", for EAP AKA authentication and "1<IMSI>@wlan.mnc<MNC>.mcc<MCC>.3gppnetwork.org", for EAP SIM authentication For example, for EAP AKA authentication: If the IMSI is 234150999999999 (MCC = 234, MNC = 15), the root NAI then takes the form [email protected]. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 14.3 |
2,618 | 16.3.2 PPP PDP type | Figure 23 describes the RADIUS message flows between a GGSN and an Authentication, Authorization and Accounting (AAA) server for the case where PPP is terminated at the GGSN. The case where PPP is relayed to an LNS is beyond the scope of the present document. NOTE 1: Separate accounting and Authentication servers may be used. NOTE 2: Actual messages depend on the used authentication protocol (e.g. PAP, CHAP). NOTE 3: If some external applications require RADIUS Accounting request (Start) information before they can process user packets, then the selected APN (GGSN) may be configured in such a way that the GGSN drops user data until the Accounting Response (START) is received from the AAA server. The GGSN may delete the PDP context if the Accounting Response (START) is not received. NOTE 4: An LCP termination procedure may be performed. Either the MS or the GGSN may initiate the context deactivation. NOTE 5: The Access-Request message shall be used for primary PDP context only. NOTE 6: Network Initiated deactivation. NOTE 7: User Initiated deactivation. Figure 23: RADIUS message flow for PDP type PPP (successful user authentication case) When a GGSN receives a Create PDP Context Request message for a given APN, the GGSN shall immediately send a Create PDP context response back to the SGSN. After PPP link setup, the authentication phase may take place. During Authentication phase, the GGSN sends a RADIUS Access-Request to an AAA server. The AAA server authenticates and authorizes the user. If RADIUS is also responsible for IP address allocation the AAA server shall return the allocated IP address or IPv6 prefix in the Access-Accept message (if the user was authenticated). If the user is not authenticated, the GGSN shall send a Delete PDP context request to the SGSN. Even if the GGSN was not involved in user authentication (e.g. for PPP no authentication may be selected), it may send a RADIUS Accounting-Request START message to an AAA server. This message contains parameters, e.g. a tuple which includes the user-id and IP address or IPv6 prefix, to be used by application servers (e.g. WAP gateway) in order to identify the user. This message also indicates to the AAA server that the user session has started, and the QoS parameters associated to the session. If some external applications require RADIUS Accounting request (Start) information before they can process user packets, then the selected APN (GGSN) may be configured in such a way that the GGSN drops user data until the Accounting Response (START) is received from the AAA server. The GGSN may delete the PDP context if the Accounting Response (START) is not received. The Authentication and Accounting servers may be separately configured for each APN. When the GGSN receives a Delete PDP Context Request message and providing a RADIUS Accounting-Request START message was sent previously, the GGSN shall send a RADIUS Accounting-Request STOP message to the AAA server, which indicates the termination of this particular user session. The GGSN shall immediately send a Delete PDP context response, without waiting for an Accounting-Response STOP message from the AAA server. The AAA server shall deallocate the IP address or IPv6 prefix (if any) initially allocated to the subscriber. Accounting-Request ON and Accounting-Request OFF messages may be sent from the GGSN to the AAA server to ensure the correct synchronization of the session information in the GGSN and the AAA server. The GGSN may send an Accounting-Request ON message to the AAA server to indicate that a restart has occurred. The AAA server may then release the associated resources. Prior to a scheduled restart, the GGSN may send Accounting-Request OFF message to the AAA server, the AAA server may then release the associated resources. If an Access-Challenge is sent to the GGSN when using PPP PDP type, the GGSN shall handle it by PPP CHAP providing PPP CHAP was the selected Authentication protocol. If CHAP authentication was not selected, authentication shall fail RFC 2865 [38]. | 3GPP TS 29.061 | Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) | CT WG3 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 16.3.2 |
2,619 | 7.2.26 Remote UE Report Notification | The direction of this message shall be from MME to SGW and from SGW to the PGW (see Table 6.1-1). This message is used by an MME to notify that at least one remote UE is newly connected to or disconnected from a ProSe UE-to-Network Relay when the MME receives such notification from the ProSe UE-to-Network Relay via the PDN connection established by the ProSe UE-to-Network Relay as specified in 3GPP TS 23.303[ Proximity-based services (ProSe); Stage 2 ] [72]. Table 7.2.26-1 specifies the presence of IEs in this message. Table 7.2.26-1: Information Elements in Remote UE Report Notification Table 7.2.26-2: Remote UE Context Connected within Remote UE Report Notification Table 7.2.26-3: Remote UE Context Disconnected with Remote UE Report Notification | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 7.2.26 |
2,620 | 4.14.2.10 Number of successful reconfigurations of LWIP DRB | a) This measurement provides the number of successful reconfigurations of LWIP DRB. b) CC c) On receipt of RRCConnectionReconfigurationComplete message (see TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8]) corresponding to transmitted RRCConnectionReconfiguration message which triggered the measurement "Number of attempted reconfigurations of LWIP DRB" (see section 4.x.z.9). d) An integer value e) LWI.LwipDrbReconfSucc 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.14.2.10 |
2,621 | 14 UE Capabilities | The UE capabilities in NR rely on a hierarchical structure where each capability parameter is defined per UE, per duplex mode (FDD/TDD), per frequency range (FR1/FR2), per band, per band combinations, … as the UE may support different functionalities depending on those (see TS 38.306[ NR; User Equipment (UE) radio access capabilities ] [11]). NOTE 1: Some capability parameters are always defined per UE (e.g. SDAP, PDCP and RLC parameters) while some other not always (e.g. MAC and Physical Layer Parameters). The UE capabilities in NR do not rely on UE categories: UE categories associated to fixed peak data rates are only defined for marketing purposes and not signalled to the network. Instead, the peak data rate for a given set of aggregated carriers in a band or band combination is the sum of the peak data rates of each individual carrier in that band or band combination, where the peak data rate of each individual carrier is computed according to the capabilities supported for that carrier in the corresponding band or band combination. For each block of contiguous serving cells in a band, the set of features supported thereon is defined in a Feature Set (FS). The UE may indicate several Feature Sets for a band (also known as feature sets per band) to advertise different alternative features for the associated block of contiguous serving cells in that band. The two-dimensional matrix of feature sets for all the bands of a band combination (i.e. all the feature sets per band) is referred to as a feature set combination. In a feature set combination, the number of feature sets per band is equal to the number of band entries in the corresponding band combination, and all feature sets per band have the same number of feature sets. Each band combination is linked to one feature set combination. This is depicted on Figure 14-1 below: Figure 14-1: Feature Set Combinations In addition, for some features in intra-band contiguous CA, the UE reports its capabilities individually per carrier. Those capability parameters are sent in feature set per component carrier and they are signalled in the corresponding FSs (per Band) i.e. for the corresponding block of contiguous serving cells in a band. The capability applied to each individual carrier in a block is agnostic to the order in which they are signalled in the corresponding FS. NOTE 2: For intra-band non-contiguous CA, there are as many feature sets per band signalled as the number of (groups of contiguous) carriers that the UE is able to aggregate non-contiguously in the corresponding band. To limit signalling overhead, the gNB can request the UE to provide NR capabilities for a restricted set of bands. When responding, the UE can skip a subset of the requested band combinations when the corresponding UE capabilities are the same. An eRedCap UE may ignore UE capability filtering and send all supported bands in the mirrored UE capability filter with an explicit indication on whether the filter was ignored or not. If supported by the UE and the network, the UE may provide an ID in NAS signalling that represents its radio capabilities for one or more RATs in order to reduce signalling overhead. The ID may be assigned either by the manufacturer or by the serving PLMN. The manufacturer-assigned ID corresponds to a pre-provisioned set of capabilities. In the case of the PLMN-assigned ID, assignment takes place in NAS signalling. The AMF stores the UE Radio Capability uploaded by the gNB as specified in TS 23.501[ System architecture for the 5G System (5GS) ] [3]. The gNB can request the UE capabilities for RAT-Types NR, EUTRA, UTRA-FDD. The UTRAN capabilities, i.e. the INTER RAT HANDOVER INFO, include START-CS, START-PS and "predefined configurations", which are "dynamic" IEs. In order to avoid the START values desynchronisation and the key replaying issue, the gNB always requests the UE UTRA-FDD capabilities before handover to UTRA-FDD. The gNB does not upload the UE UTRA-FDD capabilities to the AMF. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 14 |
2,622 | 5.8.9.6 Sidelink UE assistance information 5.8.9.6.1 General | Figure 5.8.9.6.1-1: Sidelink UE assistance information The purpose of this procedure is for a UE to inform its peer UE of the sidelink DRX assistance information used to determine the sidelink DRX configuration for unicast communication. For sidelink unicast, a UE may include its desired sidelink DRX configurations in the UEAssistanceInformationSidelink as the sidelink DRX assistance information which is transmitted to its peer UE. NOTE: It is up to UE implementation to determine its desired sidelink DRX configurations for unicast communication. When UE transmits SL-PRS in dedicated SL-PRS resource pool, the sidelink DRX configuration is not applied. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.8.9.6 |
2,623 | C.4.4.1 IMSI-based SUPI | The following test data set corresponds to ECIES-based encryption in the UE for IMSI-based SUPI and ECIES Profile B. IMSI consists of MCC|MNC: '274012' and MSIN: '001002086' ECIES test data The Scheme Output is computed in the UE as defined in Figure C.3.2-1 of clause C.3.2 with following data: Home Network Public Key: uncompressed: '0472DA71976234CE833A6907425867B82E074D44EF907DFB4B3E21C1C2256EBCD15A7DED52FCBB097A4ED250E036C7B9C8C7004C4EEDC4F068CD7BF8D3F900E3B4', if compressed: '0272DA71976234CE833A6907425867B82E074D44EF907DFB4B3E21C1C2256EBCD1' Home Network Private Key (Not available in the UE, provided here only for test purposes): 'F1AB1074477EBCC7F554EA1C5FC368B1616730155E0041AC447D6301975FECDA' Eph. Public Key: If compressed: '039AAB8376597021E855679A9778EA0B67396E68C66DF32C0F41E9ACCA2DA9B9D1' uncompressed: '049AAB8376597021E855679A9778EA0B67396E68C66DF32C0F41E9ACCA2DA9B9D1D1F44EA1C87AA7478B954537BDE79951E748A43294A4F4CF86EAFF1789C9C81F' If point compression applied (scheme output for Profile B always applies point compression for Eph. public key as specified in clause C.3.4.2 above) Eph. Private Key: '99798858A1DC6A2C68637149A4B1DBFD1FDFF5ADDD62A2142F06699ED7602529' Eph. Shared Key: '6C7E6518980025B982FBB2FF746E3C2E85A196D252099A7AD23EA7B4C0959CAE' Eph. Enc. Key: ' 8A65C3AED80295C12BD55087E965702A' ICB: 'EF285B4061C3BAEE858AB6EC68487DAE' Scheme-input corresponding to the plaintext-block: '00012080F6' Cipher-text vaue: '46A33FC271' Eph. mac key: : 'A5EBAC0BC48D9CF7AE5CE39CD840AC6C761AEC04078FAB954D634F923E901C64' MAC-tag value: '6AC7DAE96AA30A4D' Scheme Output: '039AAB8376597021E855679A9778EA0B67396E68C66DF32C0F41E9ACCA2DA9B9D146A33FC2716AC7DAE96AA30A4D' | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | C.4.4.1 |
2,624 | – CGI-InfoNR | The IE CGI-InfoNR indicates cell access related information, which is reported by the UE as part of report CGI procedure. CGI-InfoNR information element -- ASN1START -- TAG-CGI-INFO-NR-START CGI-InfoNR ::= SEQUENCE { plmn-IdentityInfoList PLMN-IdentityInfoList OPTIONAL, frequencyBandList MultiFrequencyBandListNR OPTIONAL, noSIB1 SEQUENCE { ssb-SubcarrierOffset INTEGER (0..15), pdcch-ConfigSIB1 PDCCH-ConfigSIB1 } OPTIONAL, ..., [[ npn-IdentityInfoList-r16 NPN-IdentityInfoList-r16 OPTIONAL ]], [[ cellReservedForOtherUse-r16 ENUMERATED {true} OPTIONAL ]] } -- TAG-CGI-INFO-NR-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
2,625 | 8.2 Structure of encoded RRC messages | An RRC PDU, which is the bit string that is exchanged between peer entities/across the radio interface contains the basic production as defined in X.691. RRC PDUs shall be mapped to and from PDCP SDUs (in case of DCCH) or RLC SDUs (in case of PCCH, BCCH or CCCH) upon transmission and reception as follows: - when delivering an RRC PDU as an PDCP SDU to the PDCP layer for transmission, the first bit of the RRC PDU shall be represented as the first bit in the PDCP SDU and onwards; and - when delivering an RRC PDU as an RLC SDU to the RLC layer for transmission, the first bit of the RRC PDU shall be represented as the first bit in the RLC SDU and onwards; and - upon reception of an PDCP SDU from the PDCP layer, the first bit of the PDCP SDU shall represent the first bit of the RRC PDU and onwards; and - upon reception of an RLC SDU from the RLC layer, the first bit of the RLC SDU shall represent the first bit of the RRC PDU and onwards. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 8.2 |
2,626 | 8.11.1.1.1 Closed-loop spatial multiplexing performance (Cell-Specific Reference Symbols) | 8.11.1.1.1.1 Minimum Requirement Single-Layer Spatial Multiplexing 2 Tx Antenna Port The requirements are specified in Table 8.11.1.1.1.1-2, with the addition of the parameters in Table 8.11.1.1.1.1-1 and the downlink physical channel setup according to Annex C.3.2. The purpose of these tests is to verify the closed loop rank-one performance with frequency selective precoding. Table 8.11.1.1.1.1-1: Test Parameters for Single-Layer Spatial Multiplexing (FRC) Table 8.11.1.1.1.1-2: Minimum performance Single-Layer Spatial Multiplexing (FRC) 8.11.1.1.1.2 Minimum Requirement Single-Layer Spatial Multiplexing 2 Tx Antenna Port with CRS assistance information The requirements are specified in Table 8.11.1.1.1.2-2, with the addition of parameters in Table 8.11.1.1.1.2-1. In Table 8.11.1.1.1.2-1, Cell 1 is the serving cell, and Cell 2 and Cell 3 are the aggressor cells. The downlink physical channel setup is according to Annex C.3.2 for each of Cell 1, Cell 2 and Cell 3, respectively. The CRS assistance information [7] is provided to the UE and includes information on Cell 2 and Cell 3. The purpose of the test is to verify the closed loop single-layer spatial multiplexing TM6 performance under assumption that UE applies CRS interference mitigation in the scenario with 2 CRS antenna ports in the serving and aggressor cells. Table 8.11.1.1.1.2-1: Test Parameters Table 8.11.1.1.1.2-2: Minimum performance for PDSCH 8.11.1.1.1.3 Minimum Requirement Single-Layer Spatial Multiplexing 4 Tx Antenna Port with CRS assistance information The requirements are specified in Table 8.11.1.1.1.3-2, with the addition of parameters in Table 8.11.1.1.1.3-1. In Table 8.11.1.1.1.3-1, Cell 1 is the serving cell, and Cell 2 and Cell 3 are the aggressor cells. The downlink physical channel setup is according to Annex C.3.2 for each of Cell 1, Cell 2 and Cell 3, respectively. The CRS assistance information [7] is provided to the UE and includes information on Cell 2 and Cell 3. The purpose of the test is to verify the closed loop single-layer spatial multiplexing TM6 performance under assumption that UE applies CRS interference mitigation in the scenario with 4 CRS antenna ports in the serving and aggressor cells. Table 8.11.1.1.1.3-1: Test Parameters Table 8.11.1.1.1.3-2: Minimum performance for PDSCH | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.11.1.1.1 |
2,627 | 5.27.1.2.2 Distribution of grandmaster clock and time-stamping | 5.27.1.2.2.1 Distribution of gPTP Sync and Follow_Up messages The mechanisms for distribution of TSN GM clock and time-stamping described in this clause are according to IEEE Std 802.1AS [104]. NOTE 1: It means Externally-observable behaviour of the 5GS bridge needs to comply with IEEE Std 802.1AS [104]. For downlink Time Synchronization, upon reception of a downlink gPTP message from NW-TT port in Follower state, the NW-TT makes an ingress timestamping (TSi) for each gPTP event (Sync) message and uses the cumulative rateRatio received inside the gPTP message payload (carried within Sync message for one-step operation or Follow_up message for two-step operation) to calculate the link delay from the upstream TSN node (gPTP entity connected to NW-TT) expressed in TSN GM time as specified in IEEE Std 802.1AS [104]. NW-TT then calculates the new cumulative rateRatio (i.e. the cumulative rateRatio of the 5GS) as specified in IEEE Std 802.1AS [104] and modifies the gPTP message payload (carried within Sync message for one-step operation or Follow_up message for two-step operation) as follows: - Adds the link delay from the upstream TSN node in TSN GM time to the correction field. - Replaces the cumulative rateRatio received from the upstream TSN node with the new cumulative rateRatio. - Adds TSi in the Suffix field of the gPTP packet as described in clause H.2. The UPF/NW-TT uses the ingress port number of the NW-TT, and domainNumber and sdoId in the received gPTP message to assign the gPTP message to a PTP instance in the NW-TT. If the NW-TT does not have a matching PTP instance, the UPF/NW-TT discards the message. The UPF/NW-TT then forwards the gPTP message from TSN network to the PTP ports in DS-TT(s) in Leader state within this PTP instance via PDU sessions terminating in this UPF that the UEs have established to the TSN network. The UPF/NW-TT also forwards the gPTP message to the PTP ports in NW-TT in Leader state within this PTP instance. All gPTP messages are transmitted on a QoS Flow that complies with the residence time upper bound requirement specified in IEEE Std 802.1AS [104]. NOTE 2: Leader and Follower terms in this specification maps to Master and Slave terms respectively for (g)PTP time synchronization as specified in IEEE Std 802.1AS [104] and IEEE Std 1588 [126]. This terminology can require update depending on the IEEE 1588 WG response to SA WG2. NOTE 3: The sum of the UE-DS-TT residence time and the PDB of the QoS Flow needs to be lower than the residence time upper bound requirement for a time-aware system specified in IEEE Std 802.1AS [104] in the following cases: a) If the PTP port in DS-TT is in Follower state and a PTP port in the NW-TT is in Leader state; or b) a PTP port in DS-TT is in Leader state and a PTP port in NW-TT is in Follower state. NOTE 4: If the PTP port in DS-TT is in a Follower state, and a PTP port in another DS-TT is in Leader state, then the sum of the residence time for these two DS-TT ports and the PDB of the QoS flow of the two PDU Sessions needs to be lower than the residence time upper bound requirement for a time-aware system specified in IEEE Std 802.1AS [104]. A UE receives the gPTP messages and forwards them to the DS-TT. The DS-TT then creates egress timestamping (TSe) for the gPTP event (Sync) messages for external TSN working domains. The difference between TSi and TSe is considered as the calculated residence time spent within the 5G system for this gPTP message expressed in 5GS time. The DS-TT then uses the rateRatio contained inside the gPTP message payload (carried within Sync message for one-step operation or Follow_up message for two-step operation) to convert the residence time spent within the 5GS in TSN GM time and modifies the payload of the gPTP message that it sends towards the downstream TSN node (gPTP entity connected to DS-TT) as follows: - Adds the calculated residence time expressed in TSN GM time to the correction field. - Removes Suffix field that contains TSi. If the ingress DS-TT has indicated support of the IEEE Std 802.1AS [104] PTP profile as described in clause K.2.1 and the network has configured a PTP instance with the IEEE Std 802.1AS [104] PTP profile for the ingress DS-TT, the ingress DS-TT performs the following operations for received UL gPTP messages for the PTP instance: - Adds the link delay from the upstream TSN node (gPTP entity connected to DS-TT) in TSN GM time to the correction field. - Replaces the cumulative rateRatio received from the upstream TSN node (gPTP entity connected to DS-TT) with the new cumulative rateRatio. - Adds TSi in the Suffix field of the gPTP packet. The UE transparently forwards the gPTP message from DS-TT to the UPF/NW-TT. If the ingress DS-TT port is in Passive state, the UPF/NW-TT discards the gPTP messages. If the ingress DS-TT port is in Follower state, the UPF/NW-TT forwards the gPTP messages as follows: - In the case of synchronizing end stations behind NW-TT, the egress port is in UPF/NW-TT. For the received UL gPTP messages, the egress UPF/NW-TT performs the following actions: - Adds the calculated residence time expressed in TSN GM to the correction field. - Removes Suffix field that contains TSi. - In the case of synchronizing TSN end stations behind DS-TT, the egress TT is DS-TT of the other UE, and the UPF/NW-TT uses the port number of the ingress DS-TT, and domainNumber and sdoId in the received gPTP message to assign the gPTP message to a PTP instance in the NW-TT. If the NW-TT does not have a matching PTP instance, the UPF/NW-TT discards the message. The UPF/NW-TT then forwards the received UL gPTP message to the PTP ports in DS-TT(s) in Leader state within this PTP instance. The egress DS-TT performs same actions as egress UPF/NW-TT in previous case. 5.27.1.2.2.2 Distribution of PTP Sync and Follow_Up messages This clause applies if DS-TT and NW-TT support distribution of PTP Sync and Follow_Up messages. PTP support by DS-TT and NW-TT may be determined as described in clause K.2.1. The mechanisms for distribution of PTP GM clock and time-stamping described in this clause are according to IEEE Std 1588 [126] for Transparent clock and for the case of Boundary clock when the GM is external, where the originTimestamp (or preciseOriginTimestamp) is not updated by the 5GS as described by the exemption in clause 5.27.1.1. If the 5GS acts as the GM with a PTP instance type Boundary clock, then the 5GS updates the originTimestamp (or preciseOriginTimestamp in case of two-step operation) with the 5GS internal clock, as described in clause 5.27.1.7. NOTE 1: This means externally-observable behaviour of the PTP instance in 5GS needs to comply with IEEE Std 1588 [126]. Upon reception of a PTP event message from the upstream PTP instance, the ingress TT (i.e. NW-TT or DS-TT) makes an ingress timestamping (TSi) for each PTP event (i.e. Sync) message. The PTP port in the ingress TT measures the link delay from the upstream PTP instance as described in clause H.4. The PTP port in the ingress TT modifies the PTP message payload (carried within Sync message for one-step operation or Follow_Up message for two-step operation) as follows: - (if the PTP port in the ingress TT has measured the link delay) Adds the measured link delay from the upstream PTP instance in PTP GM time to the correction field. - (if the PTP port in the ingress TT has measured the link delay and rateRatio is used) Replaces the cumulative rateRatio received from the upstream PTP instance with the new cumulative rateRatio. - Adds TSi in the Suffix field of the PTP message as described in clause H.2. NOTE 2: If the 5GS is configured to use the Cumulative frequency transfer method for synchronizing clocks as described in clause 16.10 in IEEE Std 1588 [126], i.e. when the cumulative rateRatio is measured, then the PTP port in the ingress TT uses the cumulative rateRatio received inside the PTP message payload (carried within Sync message for one-step operation or Follow_Up message for two-step operation) to correct the measured link delay to be expressed in PTP GM time as specified in IEEE Std 1588 [126]. The PTP port in the ingress TT then calculates the new cumulative rateRatio (i.e. the cumulative rateRatio of the 5GS) as specified in IEEE Std 1588 [126]. NOTE 3: If 5GS acts as an end-to-end Transparent Clock, since the end-to-end Transparent Clock does not support peer-to-peer delay mechanism, the residence time can be calculated with the residence time spent within the 5GS in 5G GM time and if needed, with a correction factor, for instance, as specified in Equation (6) of clause 12.2.2 of IEEE Std 1588 [126], this gives a residence time expressed in PTP GM time that is used to update the correction field of the received PTP Sync or Follow_Up message. The PTP port in the ingress TT then forwards the PTP message to the UPF/NW-TT. The UPF/NW-TT further distributes the PTP message as follows: - If the 5GS is configured to operate as Boundary Clock as described in IEEE Std 1588 [126], the UPF/NW-TT uses the port number of the ingress DS-TT and domainNumber and sdoId in the received PTP message to assign the PTP message to a PTP instance in the NW-TT. If the NW-TT does not have a matching PTP instance, the UPF/NW-TT discards the message. The UPF/NW-TT then regenerates the Sync and Follow_Up (for two-step operation) messages based on the received Sync and Follow_Up messages for the PTP ports in Leader state in NW-TT and DS-TT(s) within this PTP instance. The NW-TT/UPF forwards the regenerated Sync and Follow_Up (for two-step operation) messages to the Leader ports in NW-TT and the PDU session(s) related to the Leader ports in the DS-TT(s) within this PTP instance. - If the 5GS is configured to operate as a Transparent Clock as described in IEEE Std 1588 [126], the UPF/NW-TT uses the port number of the ingress TT and domainNumber and sdoId in the received PTP message to assign the PTP message to a PTP instance in the NW-TT. If the NW-TT does not have a matching PTP instance, the UPF/NW-TT discards the message. The UPF/NW-TT then forwards the received Sync messages to PTP ports in DS-TT(s) within this PTP instance via corresponding PDU Sessions terminating to this UPF, and to NW-TT ports within this PTP instance, except toward the ingress PTP port in the ingress TT. NOTE 4: If 5GS acts as a Transparent Clock, the 5GS does not maintain the PTP port states; the ingress PTP messages received on a PTP Port are retransmitted on all other PTP Ports of the Transparent Clock subject to the rules of the underlying transport protocol. NOTE 5: Due to the exemption described in clause 5.27.1.1, when the PTP instance in 5GS is configured to operate as a Boundary Clock, the 5GS does not need to synchronize its Local PTP Clock to the external PTP grandmaster. The PTP instance in 5GS measures the link delay and residence time and communicates these in a correction field. The externally observable behaviour of 5GS still conforms to the specifications for a Boundary Clock as described in IEEE Std 1588 [126]. The PTP port in the egress TT then creates egress timestamping (TSe) for the PTP event (i.e. Sync) messages for external PTP network. The difference between TSi and TSe is considered as the calculated residence time spent within the 5G system for this PTP message expressed in 5GS time. The PTP port in the egress TT then uses the rateRatio contained inside the PTP message payload (if available, carried within Sync message for one-step operation or Follow_Up message for two-step operation) to convert the residence time spent within the 5GS in PTP GM time. The PTP port in the egress TT modifies the payload of the PTP message (Sync message for one-step operation or Follow_Up message for two-step operation) that it sends towards the downstream PTP instance as follows: - Adds the calculated residence time to the correction field. - Removes Suffix field of the PTP message that contains TSi. NOTE 6: If 5GS acts as an end-to-end Transparent Clock, since the end-to-end Transparent Clock does not support peer-to-peer delay mechanism, the residence time is calculated with the residence time spent within the 5GS in 5G GM time and, if needed, corrected for instance with the factor as specified in Equation (6) of clause 12.2.2 of IEEE Std 1588 [126] to get it expressed in PTP GM time. The residence time is used to update the correction field of the received PTP event (e.g. Sync or Follow_Up) message. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.27.1.2.2 |
2,628 | 16.5 AAA Server triggered Slice-Specific Authorization Revocation | Figure 16.5-1: AAA Server-initiated Network Slice-Specific Authorization Revocation procedure 0. The UE is registered in 5GC via an AMF. The AMF ID is stored in the UDM. 1. The slice specific AAA-S requests the revocation of authorization for the Network Slice identified by the GPSI in the AAA Protocol Revoke Authorization Request message. This message is sent to NSSAAF instance interfacing with AAA-S or AAA-P if it is used. The AAA-P, if present, relays the request to the NSSAAF. 2. The NSSAAF checks whether the AAA-S is authorized to request the revocation by checking the local configuration of AAA-S address per S-NSSAI. If success,the NSSAAF requests UDM for the AMF serving the UE using the Nudm_UECM_Get (GPSI, AMF Registration) service operation. The UDM provides the NSSAAF with the AMF ID of the AMF serving the UE. 3. The NSSAAF sends an acknowledgement to the the AAA-S/AAA-P with AAA Protocol Revoke Authorization Response message. If the AMF is not registered in UDM the procedure is stopped here. 4. If the AMF is registered in UDM, the NSSAAF request the relevant AMF to revoke the S-NSSAI authorization for the UE using the Nnssaaf_NSSAA_RevocationNotification service operation. The AMF is implicitly subscribed to receive Nnssaaf_NSSAA_RevocationNotification service operations. The NSSAAF may discover the Callback URI for the Nnssaaf_NSSAA_RevocationNotification service operation exposed by the AMF via the NRF. The AMF acknowledges the Notification of Revocation request. 5. The AMF removes any status it may have kept of the corresponding S-NSSAI subject to Network Slice-Specific Authentication and Authorisation in the UE context and sends the UE Configuration Update message to revoke the S-NSSAI from the current Allowed NSSAI, for any Access Type for which NSSAA had been successfully run on this S-NSSAI. The AMF provides a new Allowed NSSAI to the UE by removing the S-NSSAI for which authorization has been revoked. The AMF provides new rejected NSSAIs to the UE including the S-NSSAI for which authorization has been revoked. If no S-NSSAI is left in Allowed NSSAI for an access after the revocation, and a Default NSSAI exists that requires no NSSAA or for which a NSSAA did not previously fail over this access, then the AMF may provide a new Allowed NSSAI to the UE containing the Default NSSAI. If no S-NSSAI is left in Allowed NSSAI for an access after the revocation, and no Default NSSAI can be provided to the UE in the Allowed NSSAI or a previous NSSAA failed for the Default NSSAI over this access, then the AMF shall execute the Network-initiated Deregistration procedure for the access as described in subclause 4.2.2.3.3 in TS 23.502[ Procedures for the 5G System (5GS) ] [8], and it shall include in the explicit De-Registration Request message the list of Rejected S-NSSAIs, each of them with the appropriate rejection cause value. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 16.5 |
2,629 | 4.3.17.2 Overview of protection from Potential MTC Related Overload | The number of MTC devices may be several orders of magnitude greater than "traditional" devices. Many (but not all) MTC devices will be relatively stationary and/or generate low volumes of traffic. However, these UEs have the capability to generate normal quantities of signalling. As normal signalling from large numbers of UEs may cause overload independently whether the UE is used for MTC or not, generic functionality for overload and congestion control is required. The total signalling from large numbers of UEs is a concern in at least two situations: - when an application (running in many UEs) requests many UEs to do "something" at the same time; and/or - when many UEs are roamers and their serving network fails, then they can all move onto the local competing networks, and potentially overload the not (yet) failed network(s). To counter these potential problems, the following standardised indications and mechanisms are provided in a generic manner. These permit node specific features to be developed to protect the networks. a) Where applicable, UEs can be configured for enhancements as described in subsequent bullets Post-manufacturing configuration can be performed remotely as described in clause 4.3.17.4. b) For mobile originated services, UEs configured for low access priority provide the E-UTRAN with information indicating that the RRC connection establishment request has low access priority (see clause 4.3.17.4). Clause 4.3.17.4 describes when low access priority is not applicable. c) RRC signalling has the capability of providing 'extended wait timers' when rejecting messages from UEs. These 'extended wait timers' are only used by UEs that access the network with low access priority. d) The MME can initiate rejection of RRC connection establishments in the E-UTRAN for UEs that access the network with low access priority as described in clause 4.3.7.4.1. In addition, MME signalling or O&M can trigger E-UTRAN to initiate Extended Access Barring. These mechanisms are further described in clause 4.3.7.4.1. e) Overload messages from the MME to E-UTRAN are extended to aid the RAN in performing the functionality in bullets b, c and d above. f) UEs configured with a long minimum periodic PLMN search time limit (see TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [69]) have an increased minimum time in between their searches for more preferred PLMNs. NOTE 1: Following the failure of a more preferred PLMN, UEs configured as above might change to other local competing networks. Expiry of this search timer will lead to the UE re-attempting to access the failed network, and then, if that network has not yet recovered, reaccessing one of the local competing networks. Use of a too short timer for the more preferred PLMN search can both prevent the failed network from recovering, and, impose more load on the local competing networks. g) At PLMN change, UEs configured to perform Attach with IMSI at PLMN change (see TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [69]) do this rather than a TA update with GUTI (thus avoiding the need to reject the TA update, and to request the IMSI following the subsequent Attach with GUTI). NOTE 2: In the case of a network failure, this reduces the message processing load on a local competing network and hence makes that network more likely to survive the failure of the other network. h) For mobile originated services, UEs configured for low access priority (see TS 24.368[ Non-Access Stratum (NAS) configuration Management Object (MO) ] [69]) provide a low access priority indication to the MME in NAS signalling that permit the MME to undertake protective measures (e.g. to permit the MME to immediately command the UE to move to a state where it does not need to generate further signalling messages and/or does not reselect PLMNs), as described in clause 4.3.7.4.1. Clause 4.3.17.4 describes when low access priority is not applicable. i) Using Periodic TAU timer value sent by the HSS and/or UE provided low access priority indication (bullet h above), the MME can allocate a long periodic TAU timer value to the UE. A long periodic TAU timer is likely to slow down the rate at which a UE detects a network failure and thus it slows down the rate of movement of UEs from a failed network to other local competing networks (see clause 4.3.17.3). j) Mechanisms for the MME and P-GW to detect congestion associated with a particular APN (see clauses 4.3.7.4.2 and 4.3.7.5). k) The addition of 'back off timers' to EMM and ESM signalling messages (e.g. to rejection messages). These include some time randomisation to guard against a repeat of a load peak. The MME should be able to apply this behaviour on a per-APN basis. as described in clause 4.3.7.4.2 l) Signalling that permits the P-GW to request the MME to generate the above ESM signalling with 'back off timers' (see clause 4.3.7.5). m) An MME overload control mechanism to selectively limit the number of Downlink Data Notification requests the S-GW sends to the MME for downlink low priority traffic received for UEs in idle mode (see clause 4.3.7.4.1a). n) UE configured for specific handling of the invalid USIM state, the "forbidden PLMN list", the "forbidden PLMNs for attach in S1mode list" and the "forbidden PLMNs for GPRS service list" remembers that the USIM is invalid and keeps the PLMN forbidden lists even if the UE is switched off and then switched on. o) When the UE has an activated PDN connection without low access priority or the UE is requested to establish such a PDN connection and the UE is configured with a permission for overriding low access priority the UE doesn't provide a low access priority indication to the MME in NAS MM signalling and also not to the RAN in the RRC requests. In the NAS request for activating a PDN connection this UE always indicates what the upper layers requested, i.e. the UE indicates low access priority in that NAS request unless the upper layers request activation of a PDN connection without low access priority. p) When the UE has an activated PDN connection that is without low access priority or the UE is requested to activate such a PDN connection and the UE is configured with a permission for overriding Extended Access Barring, then the UE ignores any Extended Access Barring (if it is activated in the network) as defined in TS 22.011[ Service accessibility ] [67]. NOTE 3: It is assumed that the mechanisms described in this entire clause are designed by Stage 3 in a manner that allows extensibility and forward compatibility. q) The eNodeB may use the low access priority indication provided by the UE to steer UEs configured for low access priority to specific MMEs. | 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.17.2 |
2,630 | 5.3.6A PDN GW Pause of Charging procedure | The PDN GW Pause of Charging procedure is optionally supported by the Serving GW and PDN GW and has the purpose to limit a mismatch between PDN GW and Serving GW charging volume and packet counts. Generally, it aims for the PDN GW charging and usage monitoring data to more accurately reflect the downlink traffic actually sent to the E-UTRAN. NOTE 1: A consequence of using this procedure is that PDN GW charging data does not correspond to the volume that traversed the PDN GW, and it is therefore not possible to count the downlink packets dropped between the PDN GW and the E-UTRAN. The Serving GW may indicate support of this function to the PDN GW when the PDN connection is activated or when a new/target Serving GW is used for a PDN connection. This is indicated to the PDN GW by a "PDN Charging Pause Support Indication" in the Create Session Request during PDN activation/Attach and in the Modify Bearer Request in procedures with a change of Serving GW. NOTE 2: It is assumed that Pause of PGW Charging is not invoked by SGW that is performing extended data buffering. The PDN GW may indicate if the feature is to be enabled on a per PDN connection basis, if the current Serving GW supports the feature and the operator's policy is to enable the feature. This is indicated to the Serving GW by a "PDN Charging Pause Enabled" Indication in the Create Session Response during PDN activation/Attach and in the Modify Bearer Response in procedures with a change of Serving GW. This is an indication to the Serving GW that when the criteria for pause of PDN GW charging are met (as described further down in this clause) the PDN GW charging can be paused. NOTE 3: PDNs where this function applies are based on an operator policy in the PDN GW. What enters into that policy is operator specific but may be based on for example if the PDN uses SDF based charging, UE is in home or visited network, APN employed, UE is configured for NAS signalling low priority, Charging Characteristics value etc. The PDN GW shall stop any charging and usage monitoring actions for the PDN connection upon receiving a "PDN Charging Pause Start" Indication in a Modify Bearer Request. When the PDN GW receives a Modify Bearer Request for a PDN connection for which charging has been stopped previously and, if the Modify Bearer Request contains a "PDN Charging Pause Stop" Indication or does not contain a "PDN Charging Pause Start" Indication, then the PDN GW shall continue charging for the PDN connection. NOTE 4: In addition to the Service Request Procedure, the PDN GW charging is also unpaused during mobility procedures involving the Serving GW based on Modify Bearer Request messages without "PDN Charging Pause Start" indication or during mobility procedures involving the Gn/Gp SGSN based on Update PDP Context Request messages. NOTE 5: A Delete Bearer Command or Delete Bearer Request or Delete Bearer Response for a dedicated bearer does not unpause a previously paused PDN charging. When bearers become suspended for a UE (see TS 23.272[ Circuit Switched (CS) fallback in Evolved Packet System (EPS); Stage 2 ] [58]), the PDN GW charging is no longer paused and the PDN GW continues charging for the PDN connection after suspended bearers are resumed. NOTE 6: The PDN GW discards packets received for a suspended UE as described in TS 23.272[ Circuit Switched (CS) fallback in Evolved Packet System (EPS); Stage 2 ] [58]. While the PDN GW charging is currently paused and the UE is in ECM-IDLE (for ISR case the device is at same time in PMM-IDLE or STANDBY in UTRAN/GERAN accesses) the following applies: - The PDN GW shall not perform charging and usage monitoring actions for downlink traffic on this PDN. NOTE 7: The Serving GW charges anyway only for the amount of transmitted downlink traffic as described in clause 5.7A. - Based on operator policy/configuration in the PDN GW, the PDN GW may limit the rate of downlink traffic sent to the Serving GW. Based on operator policy/configuration in the Serving GW, the Serving GW may discard rather than buffer the downlink user plane packets for this PDN connection while the PDN GW charging is paused. This is to avoid delivery of user plane packets to the UE that were not counted in the PDN GW for charging and usage monitoring purposes. Regardless of operator policy/configuration, the downlink user plane packets received from PDN GW at the Serving GW shall trigger Downlink Data Notifications as described in clause 5.3.4.3. When the Serving GW receives a Modify Bearer Request or Modify Access Bearers Request for a PDN connection triggering a Modify Bearer Request towards the PDN GW, the Serving GW shall consider the PDN charging as being unpaused if it has been paused previously. Figure 5.3.6A: PDN GW Pause of charging procedure 1. The Serving GW receives downlink data packets for a UE known as not user plane connected (i.e. the Serving GW context data indicates no downlink user plane TEID for the eNodeB) as described in clause 5.3.4.3 step 1, i.e. the packets are buffered or discarded in Serving GW based on operator policy. 2. Based on operator policy/configuration the Serving GW triggers the procedure to pause PDN charging. Triggering criteria are based on Serving GW operator policy/configuration. Example of such policy may be: a. Operator specified criteria/threshold (e.g. number/fraction of packets/bytes dropped at Serving GW in downlink since last time the UE was in ECM-CONNECTED state (or for ISR case PMM-CONNECTED state)). b. Recent indication of "Abnormal Release of Radio Link" (see clause 5.3.5) or a recent Downlink Data Notification Reject (clause 5.3.4.3) without UE shortly re-entering ECM-CONNECTED state (or for ISR case without also re-entering PMM-CONNECTED state). 3. Serving GW sends a Modify Bearer Request (PDN Charging Pause Start) message to the PDN GW. PDN Charging Pause Start indicates that PDN GW charging shall be paused. 4. PDN GW confirms with a Modify Bearer Response message. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.3.6A |
2,631 | 5.3.13.6 Cell re-selection or cell selection or L2 U2N relay (re)selection while T390, T319 or T302 is running or SDT procedure is ongoing (UE in RRC_INACTIVE) or SRS transmission in RRC_INACTIVE is configured | The UE shall: 1> if cell reselection occurs while T319 or T302 is running or while SDT procedure is ongoing; or 1> if relay reselection occurs while T319 is running; or 1> if cell changes due to relay reselection while T302 is running: 2> perform the actions upon going to RRC_IDLE as specified in 5.3.11 with release cause 'RRC Resume failure'; 1> else if cell selection or reselection occurs while T390 is running, or cell change due to relay selection or reselection occurs while T390 is running: 2> stop T390 for all access categories; 2> perform the actions as specified in 5.3.14.4. 1> else if cell reselection occurs when srs-PosRRC-Inactive is configured: 2> indicate to the lower layer to stop inactivePosSRS-TimeAlignmentTimer; 2> release the srs-PosRRC-Inactive. 1> else if cell reselection occurs when srs-PosRRC-InactiveValidityAreaConfig is configured and if the cell is not included in the srs-PosConfigValidityArea: 2> indicate to the lower layer to stop inactivePosSRS-ValidityAreaTAT; 1> else if cell reselection occurs when srs-PosRRC-InactiveValidityAreaConfig is configured and if the cell is included in the srs-PosRRC-InactiveValidityAreaConfig: 2> if autonomousTA-AdjustmentEnabled is configured; 3> indicate to the lower layer to update Timing Advance and stored RSRP. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.13.6 |
2,632 | 4.2.1 UE states and state transitions including inter RAT | A UE is either in RRC_CONNECTED state or in RRC_INACTIVE state when an RRC connection has been established. If this is not the case, i.e. no RRC connection is established, the UE is in RRC_IDLE state. The RRC states can further be characterised as follows: - RRC_IDLE: - A UE specific DRX may be configured by upper layers; - At lower layers, the UE may be configured with a DRX for PTM transmission of MBS broadcast; - UE controlled mobility based on network configuration; - The UE: - Monitors Short Messages transmitted with P-RNTI over DCI (see clause 6.5); - Monitors a Paging channel for CN paging using 5G-S-TMSI, except if the UE is acting as a L2 U2N Remote UE; - If configured by upper layers for MBS multicast reception, monitors a Paging channel for CN paging using TMGI; - Performs neighbouring cell measurements and cell (re-)selection; - Acquires system information and can send SI request (if configured); - Performs logging of available measurements together with location and time for logged measurement configured UEs; - Performs idle/inactive measurements for idle/inactive measurement configured UEs; - If configured by upper layers for MBS broadcast reception, acquires MCCH change notification and MBS broadcast control information and data. - RRC_INACTIVE: - A UE specific DRX may be configured by upper layers or by RRC layer; - At lower layers, the UE may be configured with a DRX for PTM transmission of MBS broadcast and/or a DRX for PTM transmission of MBS multicast; - UE controlled mobility based on network configuration; - The UE stores the UE Inactive AS context; - A RAN-based notification area is configured by RRC layer; - Transfer of unicast data and/or signalling to/from UE over radio bearers configured for SDT. - The UE: - Monitors Short Messages transmitted with P-RNTI over DCI (see clause 6.5); - While T319a is running, monitors control channels associated with the shared data channel to determine if data is scheduled for it; - While T319a is not running, monitors a Paging channel for CN paging using 5G-S-TMSI and RAN paging using fullI-RNTI, except if the UE is acting as a L2 U2N Remote UE; - If configured by upper layers for MBS multicast reception, while T319a is not running, monitors a Paging channel for paging using TMGI; - Performs neighbouring cell measurements and cell (re-)selection; - Performs RAN-based notification area updates periodically and when moving outside the configured RAN-based notification area; - Acquires system information and, while SDT procedure is not ongoing, can send SI request (if configured); - While SDT procedure is not ongoing, performs logging of available measurements together with location and time for logged measurement configured UEs; - While SDT procedure is not ongoing, performs idle/inactive measurements for idle/inactive measurement configured UEs; - If configured by upper layers for MBS broadcast reception, acquires MCCH change notification and MBS broadcast control information and data; - If configured for MBS multicast reception in RRC_INACTIVE, acquires multicast MCCH change notification and MBS multicast control information and data; - Transmits SRS for Positioning. - RRC_CONNECTED: - The UE stores the AS context; - Transfer of unicast data to/from UE; - Transfer of MBS multicast data to UE; - At lower layers, the UE may be configured with a UE specific DRX; - At lower layers, the UE may be configured with a DRX for PTM transmission of MBS broadcast and/or a DRX for MBS multicast; - At lower layers, the UE may be configured with a cell specific cell DTX/DRX; - For UEs supporting CA, use of one or more SCells, aggregated with the SpCell, for increased bandwidth; - For UEs supporting DC, use of one SCG, aggregated with the MCG, for increased bandwidth; - Network controlled mobility within NR, to/from E-UTRA, and to UTRA-FDD; - Network controlled mobility (path switch) between a serving cell and a L2 U2N Relay UE, or vice versa. - The UE: - Monitors Short Messages transmitted with P-RNTI over DCI (see clause 6.5), if configured; - Monitors control channels associated with the shared data channel to determine if data is scheduled for it; - Provides channel quality and feedback information; - Performs neighbouring cell measurements and measurement reporting; - Acquires system information; - Performs immediate MDT measurement together with available location reporting; - If configured by upper layers for MBS broadcast reception, acquires MCCH change notification and MBS broadcast control information and data. Figure 4.2.1-1 illustrates an overview of UE RRC state machine and state transitions in NR. A UE has only one RRC state in NR at one time. Figure 4.2.1-1: UE state machine and state transitions in NR Figure 4.2.1-2 illustrates an overview of UE state machine and state transitions in NR as well as the mobility procedures supported between NR/5GC, E-UTRA/EPC and E-UTRA/5GC. Figure 4.2.1-2: UE state machine and state transitions between NR/5GC, E-UTRA/EPC and E-UTRA/5GC Figure 4.2.1-3 illustrates the mobility procedure supported between NR/5GC and UTRA-FDD. Figure 4.2.1-3: Mobility procedure supported between NR/5GC and UTRA-FDD | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 4.2.1 |
2,633 | 4.6.3.2 ECM-CONNECTED | The UE location is known in the MME with an accuracy of a serving eNodeB ID. The mobility of UE is handled by the handover procedure, except for when the NB-IoT is being used, in which case there are no handover procedures. The UE performs the tracking area update procedure when the TAI in the EMM system information is not in the list of TA's that the UE registered with the network, or when the UE handovers to an E-UTRAN cell and the UE's TIN indicates "P-TMSI". For a UE in the ECM-CONNECTED state, there exists a signalling connection between the UE and the MME. The signalling connection is made up of two parts: an RRC connection and an S1_MME connection. The UE shall enter the ECM-IDLE state when its signalling connection to the MME has been released or broken. This release or failure is explicitly indicated by the eNodeB to the UE or detected by the UE. The S1 release procedure or, if the UE is enabled to use User Plane CIoT EPS Optimisation the S1 Connection Suspend procedure (clause 5.3.4A) changes the state at both UE and MME from ECM-CONNECTED to ECM-IDLE. NOTE 1: The UE may not receive the indication for the S1 release, e.g. due to radio link error or out of coverage. In this case, there can be temporal mismatch between the ECM-state in the UE and the ECM-state in the MME. After a signalling procedure, the MME may decide to release the signalling connection to the UE, after which the state at both the UE and the MME is changed to ECM-IDLE. NOTE 2: There are some abnormal cases where the UE transitions to ECM-IDLE. When a UE changes to ECM-CONNECTED state and the network initiates establishment of data radio bearers, then if a data radio bearer cannot be established, or the UE cannot maintain a data radio bearer in the ECM-CONNECTED state during handovers, the corresponding EPS bearer is deactivated. An exception to this is when the UE has been informed by the MME that a specific EPS bearer will never use a data radio bearer (e.g. because that EPS bearer is for a connection to the SCEF). | 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.6.3.2 |
2,634 | 4.7.7.10 Handling of keys at intersystem change from S1 mode to Iu mode or A/Gb mode | At an inter-system change from S1 mode to Iu mode, ciphering and integrity may be started (see 3GPP TS 25.331[ None ] [23c]) without any new authentication and ciphering procedure. At an inter-system change from S1 mode to A/Gb mode, ciphering may be started (see 3GPP TS 44.064[ Mobile Station - Serving GPRS Support Node (MS-SGSN); Logical Link Control (LLC) Layer Specification ] [78a]) without any new authentication and ciphering procedure. Deduction of the appropriate security keys for ciphering and integrity check in Iu mode or for ciphering in A/Gb mode, depends on the current EPS security context or the UMTS security context for the PS domain stored in the MS and the network. The ME shall handle the GPRS UMTS ciphering key, the GPRS UMTS integrity key, the GPRS GSM ciphering key and a potential GPRS GSM Kc128 according to table 4.7.7.10.1, table 4.7.7.10.2 and table 4.7.7.10.3. Table 4.7.7.10.1/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Inter-system change from S1 mode to Iu mode or A/Gb mode in connected mode. NOTE 1: For the case in table 4.7.7.10.1, because of deriving a new UMTS security context for the PS domain, a new GPRS GSM ciphering key needs to be derived from the new derived UMTS security keys (i.e. CK' and IK'). Note that the new GPRS GSM ciphering key is also part of the new UMTS security context for the PS domain, and therefore any old GPRS GSM ciphering key stored in the USIM and in the ME belongs to an old UMTS security context for the PS domain and can no longer be taken into use. Table 4.7.7.10.2/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Inter-system change from S1 mode to Iu mode or A/Gb mode in idle mode when the TIN indicates "GUTI". NOTE 2: For the case in table 4.7.7.10.2, because of deriving a new UMTS security context for the PS domain, a new GPRS GSM ciphering key needs to be derived from the new derived UMTS security keys (i.e. CK' and IK'). The new GPRS GSM ciphering key is also part of the new UMTS security context for the PS domain, and therefore any old GPRS GSM ciphering key stored in the USIM and in the ME belongs to an old UMTS security context for the PS domain and can no longer be taken into use. Table 4.7.7.10.3/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Inter-system change from S1 mode to Iu mode or A/Gb mode in idle mode when the TIN indicates "RAT-related TMSI" The network shall replace an already established UMTS security context for the PS domain, if any, when a handover from S1mode to Iu mode or from S1mode to A/Gb mode has been completed successfully. If the handover from S1mode to Iu mode or S1mode to A/Gb mode has not been completed successfully, the ME and the network shall delete the new derived UMTS security context for the PS domain. Additionally, the network shall delete the already established UMTS security context for the PS domain, if the CKSN of the already established UMTS security context is equal to the CKSN of the new derived security context for the PS domain. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.7.7.10 |
2,635 | 8.5.2.2.7 Enhanced Downlink Control Channel Performance Requirement Type B - 2 Tx Antenna Ports with Colliding CRS Dominant Interferer | For the parameters specified in Table 8.5.2-1 and Table 8.5.2.2.7-1, the average probability of a miss-detecting ACK for NACK (Pm-an) shall be below the specified value in Table 8.5.2.2.7-2. The purpose of this test is to verify the PHICH performance with 2 transmit antennas when the serving cell PHICH transmission is interfered by two interfering cells with the dominant interferer having the colliding CRS pattern and applying interference model defined in clause B.7.1. In Table 8.5.2.2.7-1, Cell 1 is the serving cell, and Cell 2 and Cell 3 are the aggressor cells. The downlink physical channel setup is according to Annex C.3.2 for each of Cell 1, Cell 2 and Cell 3, respectively. The CRS assistance information [7] is provided and includes Cell 2 and Cell 3. Table 8.5.2.2.7-1: Test Parameters for PHICH Table 8.5.2.2.7-2: Minimum performance PHICH 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.5.2.2.7 |
2,636 | 5.3.3.4 Reception of the RRCSetup by the UE | The UE shall perform the following actions upon reception of the RRCSetup: 1> if the RRCSetup is received in response to an RRCReestablishmentRequest; or 1> if the RRCSetup is received in response to an RRCResumeRequest or RRCResumeRequest1: 2> if the UE is NCR-MT: 3> indicate to NCR-Fwd to cease forwarding; 2> if sdt-MAC-PHY-CG-Config is configured: 3> instruct the MAC entity to stop the cg-SDT-TimeAlignmentTimer, if it is running; 3> instruct the MAC entity to start the timeAlignmentTimer associated with the PTAG, if it is not running; 2> if srs-PosRRC-Inactive is configured: 3> instruct the MAC entity to stop the inactivePosSRS-TimeAlignmentTimer, if it is running; 2> if srs-PosRRC-InactiveValidityAreaConfig is configured: 3> instruct the MAC entity to stop the inactivePosSRS-ValidityAreaTAT, if it is running; 2> discard any stored UE Inactive AS context and suspendConfig; 2> discard any current AS security context including the KRRCenc key, the KRRCint key, the KUPint key and the KUPenc key; 2> release radio resources for all established RBs except SRB0 and broadcast MRBs, including release of the RLC entities, of the associated PDCP entities and of SDAP; 2> release the RRC configuration except for the default L1 parameter values, default MAC Cell Group configuration, CCCH configuration and broadcast MRBs; 2> indicate to upper layers fallback of the RRC connection; 2> for each application layer measurement configuration with configForRRC-IdleInactive absent or not set to true: 3> discard any application layer measurement reports which were not transmitted yet; 3> inform upper layers about the release of all application layer measurement configurations; 2> stop timer T380, if running; 1> perform the cell group configuration procedure in accordance with the received masterCellGroup and as specified in 5.3.5.5; 1> perform the radio bearer configuration procedure in accordance with the received radioBearerConfig and as specified in 5.3.5.6; 1> if stored, discard the cell reselection priority information provided by the cellReselectionPriorities or inherited from another RAT; 1> stop timer T300, T301, T319; 1> if T319a is running: 2> stop T319a; 2> consider SDT procedure is not ongoing; 1> if T390 is running: 2> stop timer T390 for all access categories; 2> perform the actions as specified in 5.3.14.4; 1> if T302 is running: 2> stop timer T302; 2> perform the actions as specified in 5.3.14.4; 1> stop timer T320, if running; 1> if the RRCSetup is received in response to an RRCResumeRequest, RRCResumeRequest1 or RRCSetupRequest: 2> if T331 is running: 3> stop timer T331; 3> perform the actions as specified in 5.7.8.3; 2> enter RRC_CONNECTED; 2> stop the cell re-selection procedure; 2> stop relay (re)selection procedure if any for L2 U2N Remote UE; 1> consider the current cell to be the PCell; 1> perform the L2 U2N Remote UE configuration procedure in accordance with the received sl-L2RemoteUE-Config as specified in 5.3.5.16; 1> perform the sidelink dedicated configuration procedure in accordance with the received sl-ConfigDedicatedNR as specified in 5.3.5.14; 1> if the UE has radio link failure or handover failure information available in VarRLF-Report and if the RPLMN is included in plmn-IdentityList stored in VarRLF-Report: 2> if reconnectCellId in VarRLF-Report is not set after failing to perform reestablishment and if this is the first RRCSetup received by the UE after declaring the failure: 3> if the UE supports RLF-Report for conditional handover and if choCellId in VarRLF-Report is set: 4> set timeUntilReconnection in VarRLF-Report to the time that elapsed since the radio link failure or handover failure experienced in the failedPCellId stored in VarRLF-Report; 3> else: 4> set timeUntilReconnection in VarRLF-Report to the time that elapsed since the last radio link failure or handover failure; 3> set nrReconnectCellId in reconnectCellId in VarRLF-Report to the global cell identity and the tracking area code of the PCell; 1> if the UE supports RLF report for inter-RAT MRO NR as defined in TS 36.306[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio access capabilities ] [62], and if the UE has radio link failure or handover failure information available in VarRLF-Report of TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10] and if the RPLMN is included in plmn-IdentityList stored in VarRLF-Report of TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10]: 2> if reconnectCellId in VarRLF-Report of TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10] is not set after failing to perform reestablishment and if this is the first RRCSetup received by the UE after declaring the failure: 3> set timeUntilReconnection in VarRLF-Report of TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10] to the time that elapsed since the last radio link failure or handover failure in LTE; 3> set nrReconnectCellId in reconnectCellId in VarRLF-Report of TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10] to the global cell identity and the tracking area code of the PCell; 1> set the content of RRCSetupComplete message as follows: 2> if upper layers provide a 5G-S-TMSI: 3> if the RRCSetup is received in response to an RRCSetupRequest: 4> set the ng-5G-S-TMSI-Value to ng-5G-S-TMSI-Part2; 3> else: 4> set the ng-5G-S-TMSI-Value to ng-5G-S-TMSI; 2> if upper layers selected an SNPN or a PLMN and in case of PLMN UE is either allowed or instructed to access the PLMN via a cell for which at least one CAG ID is broadcast: 3> set the selectedPLMN-Identity from the npn-IdentityInfoList; 2> else: 3> set the selectedPLMN-Identity to the PLMN selected by upper layers from the plmn-IdentityInfoList; 2> if upper layers provide the 'Registered AMF': 3> include and set the registeredAMF as follows: 4> if the PLMN identity of the 'Registered AMF' is different from the PLMN selected by the upper layers: 5> include the plmnIdentity in the registeredAMF and set it to the value of the PLMN identity in the 'Registered AMF' received from upper layers; 4> set the amf-Identifier to the value received from upper layers; 3> include and set the guami-Type to the value provided by the upper layers; 2> if upper layers provide one or more S-NSSAI (see TS 23.003[ Numbering, addressing and identification ] [21]): 3> include the s-NSSAI-List and set the content to the values provided by the upper layers; 2> if upper layers provide onboarding request indication: 3> include the onboardingRequest; 2> set the dedicatedNAS-Message to include the information received from upper layers; 2> if connecting as an IAB-node: 3> include the iab-NodeIndication; 2> else if connecting as a mobile IAB-node: 3> include the mobileIAB-NodeIndication; 2> if connecting as an NCR-node: 3> include the ncr-NodeIndication; 2> if the SIB1 contains idleModeMeasurementsNR and the UE has NR idle/inactive measurement information concerning cells other than the PCell available in VarMeasIdleReport; or 2> if the SIB1 contains idleModeMeasurementsEUTRA and the UE has E-UTRA idle/inactive measurement information available in VarMeasIdleReport: 3> include the idleMeasAvailable; 2> if the UE has logged measurements available for NR and if the RPLMN is included in plmn-IdentityList stored in VarLogMeasReport; or 2> if the UE has logged measurements available for NR and if the current registered SNPN is included in snpn-ConfigIDList stored in VarLogMeasReport: 3> include the logMeasAvailable in the RRCSetupComplete message; 3> if Bluetooth measurement results are included in the logged measurements the UE has available for NR: 4> include the logMeasAvailableBT in the RRCSetupComplete message; 3> if WLAN measurement results are included in the logged measurements the UE has available for NR: 4> include the logMeasAvailableWLAN in the RRCSetupComplete message; 2> if the sigLoggedMeasType in VarLogMeasReport is included; or 2> if the UE is capable of reporting availability of signalling based logged MDT for inter-RAT (i.e. LTE to NR), and if the sigLoggedMeasType in VarLogMeasReport of TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10] is included: 3> if T330 timer is running (associated to the logged measurement configuration for NR or for LTE): 4> set sigLogMeasConfigAvailable to true in the RRCSetupComplete message; 3> else: 4> if the UE has logged measurements: 5> set sigLogMeasConfigAvailable to false in the RRCSetupComplete message; 2> if the UE has connection establishment failure or connection resume failure information available in VarConnEstFailReport or VarConnEstFailReportList and if the RPLMN is equal to plmn-Identity stored in VarConnEstFailReport or in at least one of the entries of VarConnEstFailReportList; or 2> if the UE has connection establishment failure information or connection resume failure information available in VarConnEstFailReport or VarConnEstFailReportList and if the current registered SNPN identity is equal to snpn-identity stored in VarConnEstFailReport or any entry of VarConnEstFailReportList: 3> include connEstFailInfoAvailable in the RRCSetupComplete message; 2> if the UE has radio link failure or handover failure information available in VarRLF-Report and if the RPLMN is included in plmn-IdentityList stored in VarRLF-Report, or 2> if the UE has radio link failure or handover failure information available in VarRLF-Report of TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10], and if the UE is capable of cross-RAT RLF reporting and if the RPLMN is included in plmn-IdentityList stored in VarRLF-Report of TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10]; or 2> if the UE has radio link failure or handover failure information available in VarRLF-Report and if the current registered SNPN is included in snpn-IdentityList stored in the VarRLF-Report: 3> include rlf-InfoAvailable in the RRCSetupComplete message; 2> if the UE has successful handover information available in VarSuccessHO-Report and if the RPLMN is included in plmn-IdentityList stored in VarSuccessHO-Report; or 2> if the UE has successful handover information available in VarSuccessHO-Report and if the current registered SNPN is included in snpn-IdentityList stored in the VarSuccessHO-Report: 3> include successHO-InfoAvailable in the RRCSetupComplete message; 2> if the UE has successful PSCell change or addition information available in VarSuccessPSCell-Report and if the RPLMN is included in plmn-IdentityList stored in VarSuccessPSCell-Report; or 2> if the UE has successful PSCell change or addition information available in VarSuccessPSCell-Report and if the current registered SNPN is included in snpn-IdentityList stored in the VarSuccessPSCell-Report: 3> include successPSCell-InfoAvailable in the RRCSetupComplete message; 2> if the UE supports storage of mobility history information and the UE has mobility history information available in VarMobilityHistoryReport: 3> include the mobilityHistoryAvail in the RRCSetupComplete message; 2> if the UE is configured with at least one application layer measurement with configForRRC-IdleInactive set to true: 3> for each application layer measurement configuration with configForRRC-IdleInactive set to true: 4> if the RPLMN is not included in plmn-IdentityList in VarAppLayerPLMN-ListConfig: 5> forward the measConfigAppLayerId and inform upper layers about the release of the application layer measurement configuration; 5> discard any application layer measurement reports which were not yet submitted to lower layers for transmission; 5> release the application layer measurement configuration in UE variables VarAppLayerIdleConfig and VarAppLayerPLMN-ListConfig; 5> consider itself not to be configured to send application layer measurement report for the measConfigAppLayerId; 3> if at least one stored application layer measurement configuration or application layer measurement report container has not been released: 4> include measConfigReportAppLayerAvailable in the RRCSetupComplete message; 2> if the UE supports uplink RRC message segmentation of UECapabilityInformation: 3> may include the ul-RRC-Segmentation in the RRCSetupComplete message; 2> if the RRCSetup is received in response to an RRCResumeRequest, RRCResumeRequest1 or RRCSetupRequest: 3> if speedStateReselectionPars is configured in the SIB2: 4> include the mobilityState in the RRCSetupComplete message and set it to the mobility state (as specified in TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [20]) of the UE just prior to entering RRC_CONNECTED state; 2> if the SIB1 contains musim-CapRestrictionAllowed and the UE capability is restricted for MUSIM operation: 3> if supported, include the musim-CapRestrictionInd in the RRCSetupComplete message upon determining it has temporary capability restriction; 2> if the UE has flight path information available: 3> include flightPathInfoAvailable; 1> submit the RRCSetupComplete message to lower layers for transmission, upon which the procedure ends. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.3.4 |
2,637 | 4.8.4 Core Network selection for UEs not using CIoT 5GS optimizations | If the UE is capable of both N1 mode and S1 mode, when the UE needs to use one or more functionalities not supported in 5GS but supported in EPS and the UE is in 5GMM-IDLE mode, the UE may disable the N1 mode capability for 3GPP access (see subclause 4.9.2). If the UE is capable of both N1 mode and S1 mode and lower layers provide an indication that the current E-UTRA cell is connected to both EPC and 5GCN without also providing an indication that a target core network type was received from the NG-RAN, the UE shall select a core network type (EPC or 5GCN) based on the PLMN selection procedures as specified in 3GPP TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [5] and provide the selected core network type information to the lower layer during the initial registration procedure. If the UE is capable of both N1 mode and S1 mode and the lower layers have provided an indication that the current E-UTRA cell is connected to both EPC and 5GCN and an indication of whether the network supports IMS emergency services via either EPC or 5GCN or both (see 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [25A]), the UE selects a core network type (EPC or 5GCN) as specified in 3GPP TS 23.167[ IP Multimedia Subsystem (IMS) emergency sessions ] [6] annex H.2 for initiating emergency calls when in the state 5GMM-DEREGISTERED.LIMITED-SERVICE or EMM-DEREGISTERED.LIMITED-SERVICE. NOTE 1: If the PLMN selection information provisioned in the USIM does not contain any prioritization between E-UTRAN and NG-RAN for a PLMN, which core network type to select for that PLMN is up to UE implementation. If the UE is capable of both N1 mode and S1 mode and lower layers provide an indication that the current E-UTRA cell is connected to both EPC and 5GCN with: 1) an indication that target core network type EPC was received from the NG-RAN, the UE shall select the EPC and proceed with the appropriate EMM procedure as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15]; or 2) an indication that target core network type 5GCN was received from the NG-RAN, the UE shall select the 5GCN and proceed with the appropriate 5GMM procedure. NOTE 2: The NG-RAN can provide a target core network type to the UE during RRC connection release with redirection (see 3GPP TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [25A] and 3GPP TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [30]). | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.8.4 |
2,638 | 9.1.1 NAS message format | Within the protocols defined in the present document, every 5GS NAS message is a standard L3 message as defined in 3GPP TS 24.007[ Mobile radio interface signalling layer 3; General Aspects ] [11]. This means that the message consists of the following parts: 1) if the message is a plain 5GS NAS message: a) extended protocol discriminator; b) security header type associated with a half spare octet or PDU session identity; c) procedure transaction identity; d) message type; e) other information elements, as required. 2) if the message is a security protected 5GS NAS message: a) extended protocol discriminator; b) security header type associated with a half spare octet; c) message authentication code; d) sequence number; e) plain 5GS NAS message, as defined in item 1 The organization of a plain 5GS NAS message is illustrated in the example shown in figure 9.1.1.1. Figure 9.1.1.1: General message organization example for a plain 5GS NAS message The PDU session identity and the procedure transaction identity are only used in messages with extended protocol discriminator 5GS session management. Octet 2a with the procedure transaction identity shall only be included in these messages. The organization of a security protected 5GS NAS message is illustrated in the example shown in figure 9.1.1.2. Figure 9.1.1.2: General message organization example for a security protected 5GS NAS message Unless specified otherwise in the message descriptions of clause 8 and annex D, a particular information element shall not be present more than once in a given 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 | 9.1.1 |
2,639 | 5.14.1.5 TX carrier (re-)selection for V2X sidelink communication | The MAC entity shall consider a CBR of a carrier to be one measured by lower layers according to TS 36.214[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer; Measurements ] [6] if CBR measurement results are available, or the corresponding defaultTxConfigIndex configured by upper layers for the carrier if CBR measurement results are not available. If the TX carrier (re-)selection is triggered for a Sidelink process according to clause 5.14.1.1, the MAC entity shall: - if there is no configured sidelink grant on any carrier allowed for the sidelink logical channel where data is available as indicated by upper layers (TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8] and TS 24.386[ User Equipment (UE) to V2X control function; protocol aspects; Stage 3 ] [15]): - for each carrier configured by upper layers associated with the concerned sidelink logical channel: - if the CBR of the carrier is below threshCBR-FreqReselection associated with the priority of the sidelink logical channel: - consider the carrier as a candidate carrier for TX carrier (re-)selection for the concerned sidelink logical channel. - else: - for each sidelink logical channel, if any, where data is available and that are allowed on the carrier for which Tx carrier (re-)selection is triggered according to clause 5.14.1.1: - if the CBR of the carrier is below threshCBR-FreqKeeping associated with priority of the sidelink logical channel: - select the carrier and the associated pool of resources. - else: - for each carrier configured by upper layers on which the sidelink logical channel is allowed, if the CBR of the carrier is below threshCBR-FreqReselection associated with the priority of the sidelink logical channel; - consider the carrier as a candidate carrier for TX carrier (re-)selection. The MAC entity shall: - if one or more carriers are considered as the candidate carriers for TX carrier (re-)selection: - for each sidelink logical channel allowed on the carrier where data is available and Tx carrier (re-)selection is triggered: - select one or more carrier(s) and associated pool(s) of resources among the candidate carriers with increasing order of CBR from the lowest CBR. NOTE 1: It is left to UE implementation how many carriers to select based on UE capability. NOTE 2: It is left to UE implementation to determine the sidelink logical channels among the sidelink logical channels where data is available and that are allowed on the carrier for which Tx carrier (re-) selection is triggered. NOTE 3: If the MAC entity is configured by the upper layer to receive a sidelink grant dynamically on the PDCCH, it is left to UE implementation to determine which carriers configured by upper layer in sl-V2X-ConfigDedicated, as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8] are considered as selected carriers for the sidelink synchronization procedures in clauses 5.10.7, 5.10.8 and 5.10.8a of TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [8]. | 3GPP TS 36.321 | Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification | RAN2 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 5.14.1.5 |
2,640 | 8.3 Mobile IP security | The introduction of Mobile IP functionality for end users in 3G has no influence on the security architecture for 3G. Mobile IP terminals may be equipped with security functionality independent of the 3G network access security in order to allow security functions outside the 3G network. 3G networks, supporting Mobile IP services, should support its inherent security functionality. On the other hand, 3G network access security architecture can not be influenced or reduced by the Mobile IP option. The Mobile IP security functionality must thus be separate from the 3G network access security and it is developed in an other forum, IETF. | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | 8.3 |
2,641 | 5.2.2.2.18 Namf_Communication_NonUeN2InfoSubscribe service operation | Service operation name: Namf_Communication_NonUeN2InfoSubscribe Description: The NF Service Consumer invokes this service operation to subscribe to the delivery of non-UE specific information from the NG-RAN node sent via N2 to the AMF. Input, Required: Notification Target Address, Notification Correlation ID, N2 information type to be subscribed. Input, Optional: Timing synchronization status reporting indication, TAI(s), NG-RAN node identifier(s). Output, Required: Subscription Correlation ID. Output, Optional: None. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.2.2.18 |
2,642 | 20.3.5 MBMS heartbeat procedure | The BM-SC initiates the MBMS heartbeat procedure to detect a SGmb path failure or the restart of the MBMS GW as specified in 3GPP TS 23.007[ Restoration procedures ] [104]. Figure 20.3.5.1: MBMS Heartbeat procedure initiated by the BM-SC 1. The BM-SC sends an RAR message to the MBMS GW and indicates this is a heartbeart request. The BM-SC also includes the Restart-Counter AVP set to its local restart counter. 2. The MBMS GW sends an RAA message to the BM-SC to acknowledge the heartbeat request. The MBMS GW also includes the Restart-Counter AVP set to its local restart counter. The MBMS GW initiates the MBMS heartbeat procedure to detect a SGmb path failure or the restart of the BM-SC as specified in 3GPP TS 23.007[ Restoration procedures ] [104]. Figure 20.3.5.2: MBMS Heartbeat procedure initiated by the MBMS GW 1. The MBMS GW sends an RAR message to the BM-SC and indicates this is a heartbeart request. The MBMS GW also includes the Restart-Counter AVP set to its local restart counter. 2. The BM-SC sends an RAA message to the MBMS GW to acknowledge the heartbeat request. The BM-SC also includes the Restart-Counter AVP set to its local restart counter. In the context of this procedure, the Diameter session shall be implicitly terminated, i.e. the client (server) shall behave as if the Auth-Session-State AVP was set to the value NO_STATE_MAINTAINED (1), as described in IETF RFC 6733 [111]. As a consequence, the server shall not maintain any state information about this session and the client shall not send any session termination request. NOTE: The Auth-Session-State AVP is not included in the RAR/RAA message as this is not permitted by the Diameter base protocol. See IETF RFC 6733 [111]. | 3GPP TS 29.061 | Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) | CT WG3 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 20.3.5 |
2,643 | 5.2.2.5 Essential system information missing | The UE shall: 1> if in RRC_IDLE or in RRC_INACTIVE or in RRC_CONNECTED while T311 is running: 2> if the UE is unable to acquire the MIB: 3> consider the cell as barred in accordance with TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [20]; 3> perform barring as if intraFreqReselection, or intraFreqReselectionRedCap for RedCap UEs, or intraFreqReselection-eRedCap for eRedCap UEs, is set to allowed; 2> else if the UE is unable to acquire the SIB1: 3> consider the cell as barred in accordance with TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [20]; 3> if the UE is a RedCap UE: 4> perform barring as if intraFreqReselectionRedCap is set to allowed; 3> else if the UE is an eRedCap UE: 4> perform barring as if intraFreqReselection-eRedCap is set to allowed; 3> else: 4> perform cell re-selection to other cells on the same frequency as the barred cell as specified in TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [20]. NOTE 1: The SIB19 is essential for NTN access. If UE is unable to acquire the SIB19 for NTN access, the action is up to UE implementation (e.g., cell re-selection to other cells). NOTE 2: The SIB22 is essential for ATG access. If UE is unable to acquire the SIB22 for ATG access, the action is up to UE implementation (e.g., cell re-selection to other cells). | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.2.2.5 |
2,644 | 5.5.2.2.3 Execution phase | Figure 5.5.2.2.3-1: UTRAN Iu mode to E-UTRAN Inter RAT HO, execution phase NOTE: For a PMIP-based S5/S8, procedure steps (A) and (B) are defined in TS 23.402[ Architecture enhancements for non-3GPP accesses ] [2]. Step (B) shows PCRF interaction in the case of PMIP-based S5/S8. Steps 9 and 9a concern GTP based S5/S8. The source RNC continues to receive downlink and uplink user plane PDUs. 1. The source SGSN completes the preparation phase towards source RNC by sending the message Relocation Command (Target RNC to Source RNC Transparent Container, RABs to be Released List, RABs Subject to Data Forwarding List). The "RABs to be Released list" IE will be the list of all NSAPIs (RAB Ids) for which a Bearer was not established in Target eNodeB. The "RABs Subject to Data forwarding list" IE may be included in the message and it shall be a list of 'Address(es) and TEID(s) for user traffic data forwarding' received from target side in step 7 of the preparation phase when 'Direct Forwarding' applies. If 'Indirect Forwarding' is applicable and Direct Tunnel is used the "RABs Subject to Data Forwarding List" IE includes the parameters received in Step 8a of the preparation phase. If 'Indirect Forwarding' is applicable and Direct Tunnel is not used the "RABs Subject to Data Forwarding List" IE includes the source SGSN address(es) and TEID(s) allocated for indirect data forwarding by Source SGSN. The Target RNC to Source RNC Transparent Container contains the value from the Target to Source Transparent Container received from the target MME. 2. The source RNC will command to the UE to handover to the target eNodeB via the message HO from UTRAN Command. The access network specific message to UE includes a transparent container including radio aspect parameters that the target eNodeB has set-up in the preparation phase. The source RNC may initiate data forwarding for the indicated RABs/EPS Bearer contexts specified in the "RABs Subject to Data Forwarding List". The data forwarding may go directly to target eNodeB, or alternatively go via the Serving GW if so decided by source SGSN and/or target MME in the preparation phase. Upon the reception of the HO from UTRAN Command message containing the Relocation Command message, the UE shall associate its RAB IDs to the respective bearers ID based on the relation with the NSAPI and shall suspend the uplink transmission of the user plane data. 3. Void. 4. The UE moves to the E-UTRAN and performs access procedures toward target eNodeB. 5. When the UE has got access to target eNodeB it sends the message HO to E-UTRAN Complete. The UE shall implicitly derive the EPS bearers for which an E-RAB was not established from the HO from UTRAN Command and deactivate them locally without an explicit NAS message at this step. 6. When the UE has successfully accessed the target eNodeB, the target eNodeB informs the target MME by sending the message Handover Notify (TAI+ECGI, Local Home Network ID). For SIPTO at the Local Network with stand-alone GW architecture, the target eNodeB shall include the Local Home Network ID of the target cell in the Handover Notify message. 7. Then the target MME knows that the UE has arrived to the target side and target MME informs the source SGSN by sending the Forward Relocation Complete Notification (ISR Activated, Serving GW change) message. If ISR Activated is indicated, this indicates to the source SGSN that it shall maintain the UE's contexts and activate ISR, which is only possible when the S-GW is not changed. The source SGSN shall also acknowledge that information. A timer in source SGSN is started to supervise when resources in the in Source RNC and Source Serving GW (for Serving GW relocation) shall be released Upon receipt of the Forward Relocation Complete Acknowledge message the target MME starts a timer if the target MME applies indirect forwarding. 8. The target MME will now complete the Inter-RAT Handover procedure by informing the Serving GW (for Serving GW relocation this will be the Target Serving GW) that the target MME is now responsible for all the bearers the UE have established. This is performed in the message Modify Bearer Request (Cause, MME Tunnel Endpoint Identifier for Control Plane, EPS Bearer ID, MME Address for Control Plane, eNodeB Address(es) and TEID(s) for User Traffic for the accepted EPS bearers and RAT type, ISR Activated) per PDN connection. As it is a mobility from UTRAN, if the target MME supports location information change reporting, the target MME shall include the User Location Information (according to the supported granularity) in the Modify Bearer Request, regardless of whether location information change reporting had been requested in the previous RAT by the PDN GW. If the PDN GW requested User CSG information (determined from the UE context), the MME also includes the User CSG Information IE in this message. If either the UE Time Zone has changed or Forward Relocation Request message from source SGSN indicated pending UE Time Zone change reporting (via Change to Report flag), the MME includes the UE Time Zone IE in this message. If either Serving GW is not relocated but the Serving Network has changed or Forward Relocation Request message from source SGSN indicated pending Serving Network change reporting (via Change to Report flag), the MME includes the new Serving Network IE in this message. If indicated, the information ISR Activated indicates that ISR is activated, which is only possible when the S-GW was not changed. When the Modify Bearer Request does not indicate ISR Activated and S-GW is not changed, the S-GW deletes any ISR resources by sending a Delete Bearer Request to the other CN node that has bearer resources on the S-GW reserved. The MME releases the non-accepted dedicated bearers by triggering the bearer release procedure as specified in clause 5.4.4.2. If the Serving GW receives a DL packet for a non-accepted bearer, the Serving GW drops the DL packet and does not send a Downlink Data Notification to the MME. If the default bearer of a PDN connection has not been accepted by the target eNodeB and there are other PDN connections active, the MME shall handle it in the same way as if all bearers of a PDN connection have not been accepted. The MME releases these PDN connections by triggering the MME requested PDN disconnection procedure specified in clause 5.10.3. 9. The Serving GW (for Serving GW relocation this will be the Target Serving GW) may inform the PDN GW the change of for example for Serving GW relocation or the RAT type that e.g. can be used for charging, by sending the message Modify Bearer Request per PDN connection. The S-GW also includes User Location Information IE and/or UE Time Zone IE and/or User CSG Information IE if they are present in step 8. Serving Network should be included if it is received in step 8 or in step 4 in clause 5.5.2.2.2. For Serving GW relocation, the Serving GW allocates DL TEIDs on S5/S8 even for non-accepted bearers and may include the PDN Charging Pause Support Indication. The PDN GW must acknowledge the request with the message Modify Bearer Response. In the case of Serving GW relocation, the PDN GW updates its context field and returns a Modify Bearer Response (Charging Id, MSISDN, PDN Charging Pause Enabled Indication (if PDN GW has chosen to enable the function), etc.) message to the Serving GW. The MSISDN is included if the PDN GW has it stored in its UE context. If location information change reporting is required and supported in the target MME, the PDN GW shall provide MS Info Change Reporting Action in the Modify Bearer Response. If PCC infrastructure is used, the PDN GW informs the PCRF about the change of, for example, the RAT type. If the Serving GW is relocated, the PDN GW shall send one or more "end marker" packets on the old path immediately after switching the path in order to assist the reordering function in the target eNodeB. The source Serving GW shall forward the "end marker" packets to the source SGSN or RNC. 10. The Serving GW (for Serving GW relocation this will be the Target Serving GW) acknowledges the user plane switch to the target MME via the message Modify Bearer Response (Cause, Serving GW Tunnel Endpoint Identifier for Control Plane, Serving GW Address for Control Plane, Protocol Configuration Options, MS Info Change Reporting Action). At this stage the user plane path is established for all bearers between the UE, target eNodeB, Serving GW (for Serving GW relocation this will be the Target Serving GW) and PDN GW. If the Serving GW does not change, the Serving GW shall send one or more "end marker" packets on the old path immediately after switching the path in order to assist the reordering function in the target eNodeB. 11. The UE initiates a Tracking Area Update procedure when one of the conditions listed in clause "Triggers for tracking area update" applies. The target MME knows that an IRAT Handover has been performed for this UE as it received the bearer context(s) by handover messages and therefore the target MME performs only a subset of the TA update procedure, specifically it excludes the context transfer procedures between source SGSN and target MME. If the Subscription Data received from the HSS (during the TAU in step 11) contains information that is necessary for the E-UTRAN to be aware of (e.g. a restriction in the UE's permission to use NR as a secondary RAT, Unlicensed Spectrum in the form of LAA/LWA/LWIP/NR-U (as specified in clause 4.3.30) or a combination of them), or an existing UE context in the MME indicates that the UE is not permitted to use NR as a secondary RAT or Unlicensed Spectrum or a combination of them and the MME has not provided this information to the target eNodeB during step 5 of the handover preparation phase, then the MME sends an updated Handover Restriction List in the Downlink NAS Transport message that it sends to RAN. If the UE is not allowed to use NR as Secondary RAT, the MME indicates that to the UE in TAU Accept message. 12. When the timer started in step 7 expires the source SGSN will clean-up all its resources towards source RNC by sending the Iu Release Command to the RNC. When there is no longer any need for the RNC to forward data, the source RNC responds with an Iu Release Complete message. When the timer started in step 7 expires and if the source SGSN received the Serving GW change indication in the Forward Relocation Response message, it deletes the EPS bearer resources by sending Delete Session Request (Cause, Operation Indication) messages to the Source Serving GW. The operation Indication flag is not set, that indicates to the Source Serving GW that the Source Serving GW shall not initiate a delete procedure towards the PDN GW. The Source Serving GW acknowledges with Delete Session Response (Cause) messages. If ISR has been activated before this procedure, the cause indicates to the Source S-GW that the Source S-GW shall delete the bearer resources on the other old CN node by sending Delete Bearer Request message(s) to that CN node. 13. If indirect forwarding was used then the expiry of the timer at source SGSN started at step 7 triggers the source SGSN to send a Delete Indirect Data Forwarding Tunnel Request message to the S-GW to release the temporary resources used for indirect forwarding. 14. If indirect forwarding was used and the Serving GW is relocated, then the expiry of the timer at target MME started at step 7 triggers the target MME to send a Delete Indirect Data Forwarding Tunnel Request message to the target S-GW to release temporary resources used for indirect forwarding. | 3GPP TS 23.401 | General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.5.2.2.3 |
2,645 | 6.50.2.2 Mobility and connectivity changes | Subject to HPLMN policy and network control, the 5G system shall be able to support mechanisms to minimize service interruption when switching a DualSteer device’s user data, for one or multiple services, between two 3GPP access networks. Subject to HPLMN policy and network control, for traffic steering and/or switching of user data across two 3GPP access networks, the 5G system may be able to support mechanisms to change one 3GPP access network to the non-3GPP access network of the same subscription (and vice versa). | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.50.2.2 |
2,646 | 5.7.5 Reflective QoS 5.7.5.1 General | Reflective QoS enables the UE to map UL User Plane traffic to QoS Flows without SMF provided QoS rules and it applies for IP PDU Session and Ethernet PDU Session. This is achieved by creating UE derived QoS rules in the UE based on the received DL traffic. It shall be possible to apply Reflective QoS and non-Reflective QoS concurrently within the same PDU Session. For a UE supporting Reflective QoS functionality, the UE shall create a UE derived QoS rule for the uplink traffic based on the received DL traffic if Reflective QoS function is used by the 5GC for some traffic flows. The UE shall use the UE derived QoS rules to determine mapping of UL traffic to QoS Flows. If the 3GPP UE supports Reflective QoS functionality, the UE should indicate support of Reflective QoS to the network (i.e. SMF) for every PDU Session. For PDU Sessions established in EPS and PDU Sessions transferred from EPS without N26 interface, the UE indicates Reflective QoS support using the PDU Session Establishment procedure. After the first inter-system change from EPS to 5GS for PDU Sessions established in EPS and transferred from EPS with N26 interface, the UE indicates Reflective QoS support using the PDU Session Modification procedure as described in clause 5.17.2.2.2. The UE as well as the network shall apply the information whether or not the UE indicated support of Reflective QoS throughout the lifetime of the PDU Session. NOTE: The logic driving a supporting UE under exceptional circumstances to not indicate support of Reflective QoS for a PDU Session is implementation dependent. Under exceptional circumstances, which are UE implementation dependent, the UE may decide to revoke previously indicated support for Reflective QoS using the PDU Session Modification procedure. In such a case, the UE shall delete all derived QoS rules for this PDU Session and the network shall stop any user plane enforcement actions related to Reflective QoS for this PDU Session. In addition, the network may provide signalled QoS rules for the SDFs for which Reflective QoS was used before. The UE shall not indicate support for Reflective QoS for this PDU Session for the remaining lifetime of the PDU Session. If under the same exceptional circumstances mentioned above and while NAS level MM or SM congestion control timer is running, the UE needs to revoke a previously indicated support for Reflective QoS, the UE performs PDU Session Release procedure that is exempt from MM and SM congestion control as defined in clause 5.19.7. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.7.5 |
2,647 | 4.6.2.2 NSSAI storage | If available, the configured NSSAI(s) shall be stored in a non-volatile memory in the ME as specified in annex C. For a configured NSSAI, if there is: a) associated NSSRG information, the NSSRG information shall also be stored in a non-volatile memory in the ME as specified in annex C; b) associated NSAG information, the NSAG information shall be stored in the ME; c) associated S-NSSAI time validity information, the S-NSSAI time validity information shall also be stored in a non-volatile memory in the ME as specified in annex C; d) associated S-NSSAI location validity information, the S-NSSAI location validity information shall also be stored in a non-volatile memory in the ME as specified in annex C; and e) associated network slice usage control information, the network slice usage control information shall also be stored in a non-volatile memory in the ME as specified in annex C. Each of the configured NSSAI stored in the UE, including the default configured NSSAI, is a set composed of at most 16 S-NSSAIs. Each of the configured NSSAI, except the default configured NSSAI, is associated with a PLMN identity or SNPN identity 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. The allowed NSSAI(s) should be stored in a non-volatile memory in the ME as specified in annex C. The partially allowed NSSAI(s) should be stored in a non-volatile memory in the ME as specified in annex C. For an allowed NSSAI, if there is associated alternative NSSAI, the alternative NSSAI should also be stored in a non-volatile memory in the ME as specified in annex C. Each of the allowed NSSAI stored in the UE is a set composed of at most 8 S-NSSAIs and is associated with a PLMN identity or SNPN identity, an access type 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. Each of the alternative NSSAI stored in the UE is a set composed of at most 8 pairs of S-NSSAI to be replaced and alternative S-NSSAI, and is associated with a PLMN identity or SNPN identity, an access type 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. Each of the partially allowed NSSAI stored in the UE is a set composed of at most 7 S-NSSAIs and a list of TAs for which S-NSSAI is supported, and is associated with a PLMN identity or SNPN identity, 3GPP access type 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. The number of S-NSSAI stored in the partially allowed NSSAI and the allowed NSSAI shall not exceed 8. Each of the pending NSSAI stored in the UE is a set composed of at most 16 S-NSSAIs and is associated with a PLMN identity or SNPN identity 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. Each of the rejected NSSAI is associated with a PLMN identity or SNPN identity 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. The S-NSSAI(s) in the rejected NSSAI for the current registration area are further associated with one or more tracking areas where the rejected S-NSSAI(s) is not available. The S-NSSAI(s) in the rejected NSSAI for the maximum number of UEs reached are further associated with the access type over which the rejected NSSAI was received. The S-NSSAI(s) in the partially rejected NSSAI are further associated with 3GPP access. There shall be no duplicated PLMN identities or SNPN identities associated with each of the list of configured NSSAI(s), pending NSSAI(s), rejected NSSAI(s) for the current PLMN or SNPN, rejected NSSAI(s) for the current registration area, rejected NSSAI(s) for the failed or revoked NSSAA, and rejected NSSAI for the maximum number of UEs reached. The UE stores NSSAIs as follows: a) The configured NSSAI shall be stored until a new configured NSSAI is received for a given PLMN or SNPN. The network may provide to the UE the mapped S-NSSAI(s) for the new configured NSSAI which shall also be stored in the UE. When the UE is provisioned with a new configured NSSAI for a PLMN or SNPN, the UE shall: 1) replace any stored configured NSSAI for this PLMN or SNPN with the new configured NSSAI for this PLMN or SNPN; 2) delete any stored mapped S-NSSAI(s) for the configured NSSAI and, if available, store the mapped S-NSSAI(s) for the new configured NSSAI; 3) delete any stored allowed NSSAI for this PLMN or SNPN and, if available, the stored mapped S-NSSAI(s) for the allowed NSSAI, if the UE received the new configured NSSAI for this PLMN or SNPN and the Configuration update indication IE with the Registration requested bit set to "registration requested", in the same CONFIGURATION UPDATE COMMAND message but without any new allowed NSSAI for this PLMN or SNPN included; 4) delete any stored rejected NSSAI and partially rejected NSSAI, and stop any timer T3526 associated with a deleted S-NSSAI in the rejected NSSAI for the maximum number of UEs reached if running; 4A) delete any stored mapped S-NSSAI(s) for the rejected NSSAI; and 5) delete any S-NSSAI(s) stored in the pending NSSAI that are not included in the new configured NSSAI for the current PLMN or SNPN or any mapped S-NSSAI(s), if any, stored in the pending NSSAI that are not included in the mapped S-NSSAI(s) for the configured NSSAI (if the UE is roaming or is in a non-subscribed SNPN); If the UE having a stored configured NSSAI for a PLMN ID, receives an S-NSSAI associated with a PLMN ID from the network during the PDN connection establishment procedure in EPS as specified in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15] or via ePDG as specified in 3GPP TS 24.302[ Access to the 3GPP Evolved Packet Core (EPC) via non-3GPP access networks; Stage 3 ] [16], the UE may store the received S-NSSAI in the configured NSSAI for the PLMN identified by the PLMN ID associated with the S-NSSAI, if not already included in the configured NSSAI and if the number of S-NSSAIs in the configured NSSAI is less than 16; The UE may continue storing a received configured NSSAI for a PLMN and associated mapped S-NSSAI(s), if available, when the UE registers in another PLMN. NOTE 1: The maximum number of configured NSSAIs and associated mapped S-NSSAIs for PLMNs other than the HPLMN that need to be stored in the UE, and how to handle the stored entries, are up to UE implementation. aa) The NSAG information shall be stored until: 1) a new NSAG information for the registered PLMN or the registered SNPN is received over 3GPP access; or 2) a new configured NSSAI without any associated NSAG information for the registered PLMN or the registered SNPN is received over 3GPP access. The UE shall remove any S-NSSAI from the NSAG information which is not part of the configured NSSAI, if any. NOTE 1A: If the UE is roaming or the current SNPN is a non-subscribed SNPN, the UE uses the S-NSSAI(s) in the configured NSSAI to compare against any S-NSSAI from the NSAG information. When a new NSAG information for the registered PLMN or the registered SNPN is received over 3GPP access, the UE shall replace any stored NSAG information for the registered PLMN and its equivalent PLMN(s) or the registered SNPN and its equivalent SNPN(s) with the new NSAG information for the registered PLMN or the registered SNPN. When a new configured NSSAI without any associated NSAG information for the registered PLMN or the registered SNPN is received over 3GPP access, the UE shall delete any stored NSAG information for the registered PLMN and its equivalent PLMN(s) or the registered SNPN and its equivalent SNPN(s). The UE shall be able to store 32 NSAG entries in the NSAG information stored for the registered PLMN or the registered SNPN. The UE shall be able to store TAI lists for up to 4 NSAG entries in the NSAG information stored for the registered PLMN or the registered SNPN. The UE needs not to store the NSAG information when the UE is switched off or when the UE is deregistered from the registered PLMN or the registered SNPN. NOTE 1B: The UE stores the NSAG information associated with the configured NSSAI for at least the registered PLMN and its equivalent PLMN(s) or the registered SNPN and its equivalent PLMN(s). b) The allowed NSSAI shall be stored and the mapped S-NSSAI(s) for the allowed NSSAI (if available) shall be stored for a given PLMN and its equivalent PLMN(s) in the registration area or SNPN until: 1) a new allowed NSSAI for the same access type (i.e. 3GPP access or non-3GPP access) is received for a given PLMN or SNPN; 2) the CONFIGURATION UPDATE COMMAND message with the Registration requested bit of the Configuration update indication IE set to "registration requested" is received and contains no other parameters (see subclauses 5.4.4.2 and 5.4.4.3); 3) the REGISTRATION ACCEPT message is received with the "NSSAA to be performed" indicator of the 5GS registration result IE set to "Network slice-specific authentication and authorization is to be performed", and the REGISTRATION ACCEPT message contains a pending NSSAI and no new allowed NSSAI as described in subclause 5.5.1.2.4 and subclause 5.5.1.3.4; or 4) a new partially allowed NSSAI via 3GPP access is received for a given PLMN or SNPN. The network may provide to the UE the mapped S-NSSAI(s) for the new allowed NSSAI (see subclauses 5.5.1.2 and 5.5.1.3) which shall also be stored in the UE. When a new allowed NSSAI for a PLMN or SNPN is received, the UE shall: 1) replace any stored allowed NSSAI for this PLMN and its equivalent PLMN(s) in the registration area or this SNPN for the same access type with the new allowed NSSAI for this PLMN or SNPN; 2) delete any stored mapped S-NSSAI(s) for the allowed NSSAI for this PLMN and its equivalent PLMN(s) in the registration area or this SNPN for the same access type and, if available, store the mapped S-NSSAI(s) for the new allowed NSSAI; 3) remove from the stored rejected NSSAI for the current PLMN or SNPN, the rejected NSSAI for the current registration area, rejected NSSAI for the maximum number of UEs reached and the partially rejected NSSAI, the S-NSSAI(s), if any, included in the new allowed NSSAI for the current PLMN or SNPN, unless the S-NSSAI in the rejected NSSAI or the partially rejected NSSAI is associated with one or more S-NSSAI(s) in the stored mapped rejected NSSAI or the stored mapped partially rejected NSSAI, and at least one of these mapped S-NSSAI(s) is not included in the mapped S-NSSAI(s) for the new allowed NSSAI, and stop any timer T3526 associated with a deleted S-NSSAI in the rejected NSSAI for the maximum number of UEs reached if running; 4) remove from the stored rejected NSSAI for the failed or revoked NSSAA, the S-NSSAI(s), if any, included in the new allowed NSSAI for the current PLMN (if the UE is not roaming) or the current SNPN (if the SNPN is the subscribed SNPN) or the mapped S-NSSAI(s) for the new allowed NSSAI for the current PLMN (if the UE is roaming) or the current SNPN (if the SNPN is a non-subscribed SNPN); 5) remove from the stored mapped S-NSSAI(s) for the rejected NSSAI for the current PLMN or SNPN, the stored mapped S-NSSAI(s) for the rejected NSSAI for the current registration area, the stored mapped S-NSSAI(s) for the partially rejected NSSAI and the mapped S-NSSAI(s) for the rejected NSSAI for the maximum number of UEs reached, the S-NSSAI(s), if any, included in the mapped S-NSSAI(s) for the new allowed NSSAI for the current PLMN (if the UE is roaming) or the current SNPN (if the SNPN is a non-subscribed SNPN), and stop any timer T3526 associated with a deleted S-NSSAI in the rejected NSSAI for the maximum number of UEs reached if running; and 6) remove from the stored pending NSSAI for this PLMN and its equivalent PLMN(s) in the registration area or this SNPN, one or more S-NSSAIs, if any, included in the new allowed NSSAI for the current PLMN and these equivalent PLMN(s) (if the UE is not roaming) or the current SNPN (if the SNPN is the subscribed SNPN) or the mapped S-NSSAI(s) for the new allowed NSSAI for the current PLMN and these equivalent PLMN(s) (if the UE is roaming) or the current SNPN (if the SNPN is a non-subscribed SNPN). NOTE 2: Whether the UE stores the allowed NSSAI and the mapped S-NSSAI(s) for the allowed NSSAI also when the UE is switched off is implementation specific. The network may provide to the UE the partially allowed NSSAI. When a new partially allowed NSSAI for a PLMN or SNPN is received, the UE shall replace any stored partially allowed NSSAI for this PLMN and its equivalent PLMN(s) in the registration area or this SNPN via the 3GPP access with the new partially allowed NSSAI for this PLMN or SNPN. ba) The alternative NSSAI and the mapped S-NSSAI(s) for the alternative NSSAI (if the UE is roaming) shall be stored for a given PLMN and its equivalent PLMN(s) or SNPN until a new alternative NSSAI for the same access type (i.e. 3GPP access or non-3GPP access) is received for a given PLMN or SNPN. When a new alternative NSSAI for a given PLMN or SNPN is received and the new alternative NSSAI includes a list of mapping information between the S-NSSAI to be replaced and the alternative S-NSSAI, the UE shall: 1) replace any stored alternative NSSAI for this PLMN and its equivalent PLMN(s) or this SNPN for the same access type with the new alternative NSSAI for this PLMN or SNPN; and 2) delete any stored mapped S-NSSAI(s) for the alternative NSSAI for this PLMN and its equivalent PLMN(s) or this SNPN for the same access type and, if available, store the mapped S-NSSAI(s) for the new alternative NSSAI. When a new alternative NSSAI for a given PLMN or SNPN is received and the new alternative NSSAI does not include any mapping information between the S-NSSAI to be replaced and the alternative S-NSSAI, the UE shall delete any stored alternative NSSAI for this PLMN and its equivalent PLMN(s) or this SNPN for the same access type. NOTE 3: Whether the UE stores the alternative NSSAI and the mapped S-NSSAI(s) for the alternative NSSAI also when the UE is switched off is implementation specific. c) When the UE receives the S-NSSAI(s) included in the rejected NSSAI in the REGISTRATION ACCEPT message, the REGISTRATION REJECT message, the DEREGISTRATION REQUEST message or in the CONFIGURATION UPDATE COMMAND message, or the S-NSSAI(s) included in the partially rejected NSSAI in the REGISTRATION ACCEPT message or the CONFIGURATION UPDATE COMMAND message, the UE shall: 1) store the S-NSSAI(s) into the rejected NSSAI and the mapped S-NSSAI(s) for the rejected NSSAI based on the associated rejection cause(s); 2) if the UE receives the S-NSSAI(s) included in the Rejected NSSAI IE, or if the UE receives the S-NSSAI(s) included in the Extended rejected NSSAI IE, or if the UE receives the S-NSSAI(s) included in the Partially rejected NSSAI IE in non-roaming case when not in SNPN access operation mode or in the subscribed SNPN, remove from the stored allowed NSSAI or partially allowed NSSAI for the current PLMN and its equivalent PLMN(s) in the registration area or the current SNPN, the S-NSSAI(s), if any, included in the: i) rejected NSSAI for the failed or revoked NSSAA, for each and every access type; ii) rejected NSSAI for the current PLMN or SNPN, for each and every access type; iii) rejected NSSAI for the current registration area, associated with the same access type; iv) rejected NSSAI for the maximum number of UEs reached, associated with the same access type; or v) partially rejected NSSAI, associated with 3GPP access; 3) if the UE receives the S-NSSAI(s) included in the Extended rejected NSSAI IE or if the UE receives the S-NSSAI(s) included in the Partially rejected NSSAI IE in roaming case or in a non-subscribed SNPN, remove from the stored allowed NSSAI or partially allowed NSSAI for the current PLMN and its equivalent PLMN(s) in the registration area or the current SNPN, the S-NSSAI(s), if any, included in the: i) rejected NSSAI for the current PLMN or SNPN, for each and every access type; ii) rejected NSSAI for the current registration area, associated with the same access type; iii) rejected NSSAI for the maximum number of UEs reached, associated with the same access type; or iv) partially rejected NSSAI, associated with 3GPP access; if the mapped S-NSSAI(s) for the S-NSSAI in the stored allowed NSSAI or partially allowed NSSAI for the current PLMN or SNPN are stored in the UE, and all of the mapped S-NSSAI(s) are included in the Extended rejected NSSAI IE or Partially rejected NSSAI IE; 4) remove from the stored mapped S-NSSAI(s) for the allowed NSSAI or partially allowed NSSAI (if available and if the UE is roaming or is a non-subscribed SNPN), the S-NSSAI(s), if any, included in the: i) rejected NSSAI for the failed or revoked NSSAA, for each and every access type; ii) mapped S-NSSAI(s) for the rejected NSSAI for the current PLMN or SNPN, for each and every access type; iii) mapped S-NSSAI(s) for the rejected NSSAI for the current registration area, associated with the same access type; iv) mapped S-NSSAI(s) for the rejected NSSAI for the maximum number of UEs reached, associated with the same access type; or v) partially rejected NSSAI, associated with 3GPP access; 5) if the UE receives the S-NSSAI(s) included in the Rejected NSSAI IE, or if the UE receives the S-NSSAI(s) included in the Extended rejected NSSAI IE in non-roaming case when not in SNPN access operation mode or in the subscribed SNPN, remove from the stored pending NSSAI for the current PLMN and its equivalent PLMN(s) in the registration area or the current SNPN, the S-NSSAI(s), if any, included in the: i) rejected NSSAI for the failed or revoked NSSAA, for each and every access type; ii) rejected NSSAI for the current PLMN or SNPN, for each and every access type; iii) rejected NSSAI for the current registration area, associated with the same access type; or iv) rejected NSSAI for the maximum number of UEs reached, associated with the same access type; 6) if the UE receives the S-NSSAI(s) included in the Extended rejected NSSAI IE in roaming case or in a non-subscribed SNPN, remove from the stored pending NSSAI for the current PLMN and its equivalent PLMN(s) in the registration area or the current SNPN, the S-NSSAI(s), if any, included in the: i) rejected NSSAI for the current PLMN or SNPN, for each and every access type; ii) rejected NSSAI for the current registration area, associated with the same access type; or iii) rejected NSSAI for the maximum number of UEs reached, associated with the same access type, if the mapped S-NSSAI(s) for the S-NSSAI in the stored pending NSSAI are stored in the UE, and all of the mapped S-NSSAI(s) are included in the Extended rejected NSSAI IE; and 7) remove from the stored mapped S-NSSAI(s) for the pending NSSAI (if available and if the UE is roaming or is in a non-subscribed SNPN), the S-NSSAI(s), if any, included in the: i) rejected NSSAI for the failed or revoked NSSAA, for each and every access type; ii) mapped S-NSSAI(s) for the rejected NSSAI for the current PLMN or SNPN, for each and every access type; iii) mapped S-NSSAI(s) for the rejected NSSAI for the current registration area, associated with the same access type; or iv) mapped S-NSSAI(s) for the rejected NSSAI for the maximum number of UEs reached, associated with the same access type; If the UE receives the CONFIGURATION UPDATE COMMAND message with the Registration requested bit of the Configuration update indication IE set to “registration requested” and contains no other parameters (see subclauses 5.4.4.2 and 5.4.4.3), the UE shall delete any stored rejected NSSAI. When the UE: 1) enters state 5GMM-DEREGISTERED following an unsuccessful registration for 5GMM causes other than #62 “No network slices available” for the current PLMN or SNPN; 2) successfully registers with a new PLMN or a new SNPN; 3) enters state 5GMM-DEREGISTERED following an unsuccessful registration with a new PLMN or a new SNPN; or 4) performs inter-system change from N1 mode to S1 mode and the UE successfully completes tracking area update procedure; and the UE is not registered with the PLMN or SNPN, which provided the rejected NSSAI, over another access, the rejected NSSAI for the current PLMN or SNPN and the rejected NSSAI for the failed or revoked NSSAA shall be deleted. When the UE receives ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message provided with S-NSSAI and the PLMN ID in the Protocol configuration options IE or Extended protocol configuration options IE (see subclause 6.5.1.3 of 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15]), the UE shall remove the S-NSSAI associated with the PLMN ID from the rejected NSSAI for the current PLMN. When the UE receives ACTIVATE DEFAULT EPS BEARER CONTEXT REQUEST message provided with S-NSSAI and the PLMN ID in the Protocol configuration options IE or Extended protocol configuration options IE (see subclause 6.5.1.3 of 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15]), the UE may remove the S-NSSAI from the rejected NSSAI for the maximum number of UEs reached for each and every access type, if any, and stop the timer T3526 associated with the S-NSSAI if running. When the UE: 1) deregisters over an access type; 2) successfully registers in a new registration area over an access type; 3) enters state 5GMM-DEREGISTERED or 5GMM-REGISTERED following an unsuccessful registration in a new registration area over an access type; or 4) performs inter-system change from N1 mode to S1 mode and the UE successfully completes tracking area update procedure; the rejected NSSAI for the current registration area corresponding to the access type and the partially rejected NSSAI shall be deleted; d) When the UE receives the pending NSSAI in the REGISTRATION ACCEPT message, the UE shall replace any stored pending NSSAI for this PLMN or SNPN with the new pending NSSAI received in the REGISTRATION ACCEPT message for this PLMN or SNPN. If the UE does not receive the pending NSSAI in the REGISTRATION ACCEPT message and the “NSSAA to be performed” indicator is not set to “Network slice-specific authentication and authorization is to be performed” in the 5GS registration result IE of the REGISTRATION ACCEPT message, the UE shall delete the stored pending NSSAI, if any, for this PLMN and its equivalent PLMN(s) in the registration area or this SNPN. If the registration area contains TAIs belonging to different PLMNs, which are equivalent PLMNs, then for each of the equivalent PLMNs, the UE shall replace any stored pending NSSAI with the pending NSSAI received in the registered PLMN. When the UE: 1) deregisters with the current PLMN or SNPN using explicit signalling or enters state 5GMM-DEREGISTERED for the current PLMN or SNPN; 2) successfully registers with a new PLMN not in the list of equivalent PLMNs or a new SNPN; 3) enters state 5GMM-DEREGISTERED following an unsuccessful registration with a new PLMN or SNPN; or 4) successfully initiates an attach or tracking area update procedure in S1 mode and the UE is operating in single-registration mode; and the UE is not registered with the PLMN or SNPN, which provided pending NSSAI, over another access, the pending NSSAI for the current PLMN and its equivalent PLMN(s) in the registration area or the current SNPN shall be deleted; e) When the UE receives the Network slicing indication IE with the Network slicing subscription change indication set to "Network slicing subscription changed" in the REGISTRATION ACCEPT message or in the CONFIGURATION UPDATE COMMAND message, the UE shall delete the network slicing information for each of the PLMNs or SNPNs that the UE has slicing information stored for (excluding the current PLMN or SNPN). The UE shall delete any stored rejected NSSAI and stop any timer T3526 associated with a deleted S-NSSAI in the rejected NSSAI for the maximum number of UEs reached if running. The UE shall not delete the default configured NSSAI. Additionally, the UE shall update the network slicing information for the current PLMN or SNPN (if received) as specified above in bullets a), b), c) and d); f) When the UE receives the new default configured NSSAI included in the default configured NSSAI update data in the Payload container IE of DL NAS TRANSPORT message, the UE shall replace any stored default configured NSSAI with the new default configured NSSAI. In case of SNPN, the UE shall replace the stored default configured NSSAI associated with the selected entry of the "list of subscriber data" or the PLMN subscription with the new default configured NSSAI; and g) When the UE receives the on-demand NSSAI in the REGISTRATION ACCEPT message or CONFIGURATION UPDATE COMMAND message, the UE shall replace any stored on-demand NSSAI for the serving PLMN with the new on-demand NSSAI. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.6.2.2 |
2,648 | 6.3.6 Handling of network rejection not due to based congestion control | The network may include a back-off timer value in an EPS session management reject message to regulate the time interval at which the UE may retry the same procedure. For ESM cause values other than #26 "insufficient resources", the network may also include the re-attempt indicator to indicate whether the UE is allowed to re-attempt the corresponding session management procedure for the same in A/Gb or Iu mode or N1 mode after inter-system change. NOTE 1: If the network includes this back-off timer value, then the UE is blocked from sending another ESM request for the same procedure for the same PLMN and combination for the specified duration. Therefore, the operator needs to exercise caution in determining the use of this timer value. NOTE 2: If the re-attempt indicator is not provided by the network, a UE registered in its HPLMN or in an EHPLMN (if the EHPLMN list is present) can use the configured SM_RetryAtRATChange value specified in the NAS configuration MO or in the USIM NASCONFIG file to derive the re-attempt indicator as specified in clauses 6.5.1.4.3, 6.5.3.4.3, and 6.5.4.4.3. If re-attempt in A/Gb or Iu mode or N1 mode is allowed, the UE shall consider the back-off timer to be applicable only to the EPS session management in S1 mode for the rejected EPS session management procedure and the given PLMN and combination. If re-attempt in A/Gb and Iu mode and N1 mode is not allowed, the UE shall consider the back-off timer to be applicable to all three NAS protocols, i.e. applicable to the EPS session management in S1 mode for the rejected EPS session management procedure, to the GPRS session management in A/Gb and Iu mode for the corresponding session management procedure and the given PLMN and combination and to the 5GS session management in N1 mode for the corresponding session management procedure and the given PLMN and APN combination. NOTE 3: In the present clause the terms APN and DNN are referring to the same parameter. The APN of the PLMN and APN combination associated with the back-off timer is the APN provided by the UE when the PDN connection is established. If no APN is included in the PDN CONNECTIVITY REQUEST or, when applicable, in the ESM INFORMATION RESPONSE message, then the back-off timer is associated with the combination of the PLMN and no APN. For this purpose the UE shall memorize the APN provided to the network during the PDN connection establishment. The back-off timer associated with the combination of a PLMN with no APN will never be started due to any ESM procedure related to an emergency PDN connection. If the back-off timer associated with the combination of a PLMN with no APN is running, it does not affect the ability of the UE to request an emergency PDN connection. The network may additionally indicate in the re-attempt indicator that a command to back-off is applicable not only for the PLMN in which the UE received the EPS session management reject message, but for each PLMN included in the equivalent PLMN list at the time when the EPS session management reject message was received. If the back-off timer is running or is deactivated for a given PLMN and APN combination, and the UE is a UE configured to use AC11 – 15 in selected PLMN, then the UE is allowed to initiate an attach procedure or any EPS session management procedure for this PLMN and APN combination. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.3.6 |
2,649 | 4.13.2.2 The procedure of "Application Triggering" Service | Figure 4.13.2.2-1: Device triggering procedure via Nnef 1. The AF determines the need to trigger the device. If the AF has no contact details for the NEF, it shall discover and select NEF services. 2. The AF invokes the Nnef_Trigger_Delivery request service. 3. The NEF checks that the AF is authorised to send trigger requests and that the AF has not exceeded its quota or rate of trigger submission over Nnef. If this check fails, the NEF sends an Nnef_Trigger_Delivery response with a cause value indicating the reason for the failure condition and the flow stops at this step. Otherwise, the flow continues with step 4. 4. The NEF invokes Nudm_SDM_Get (Identifier Translation, GPSI and AF Identifier) to resolve the GPSI to SUPI when the AF is authorized to trigger the UE. NOTE 1: Optionally, mapping from GPSI (External Id) to GPSI (MSISDN) is also provided for legacy SMS infrastructure not supporting MSISDN-less SMS. 5. The UDM may invoke the Nudr_DM_Query service to retrieve a list of AF's that are allowed to trigger the UE and determines, based on UDM policy, which identifier (SUPI or MSISDN) should be used to trigger the UE. The UDM provides a Nudm_SDM_Get response (SUPI, optionally MSISDN. If the AF is not allowed to send a trigger message to this UE, or there is no valid subscription information for this user, the NEF sends an Nnef_Trigger_Delivery response with a cause value indicating the reason for the failure condition and the flow stops at this step. Otherwise this flow continues with step 6. NOTE 2: The presence of an MSISDN in the reply is interpreted as an indication to the NEF that MSISDN is used (instead of IMSI) to identify the UE when sending the SMS to the SMS-SC via T4. 6. The NEF invokes Nudm_UECM_Get (GPSI, SMS) to retrieve the UE SMSF identities. 7. The UDM may invoke the Nudr_DM_Query service to retrieve the UE SMSF identities. The UDM provides a Nudm_UECM_Get response with the corresponding UE SMSF identities. UDM policy (possibly dependent on the VPLMN ID) may influence which serving node identities are returned. NOTE 3: The NEF can cache serving node information for the UE. However, this can increase the probability of trigger delivery attempt failures when the cached serving node information is stale. 8. The NEF selects a suitable SMS-SC based on configured information. The NEF acts as an MTC-IWF and sends a Submit Trigger (GPSI, SUPI, AF Identifier, trigger reference number, validity period, priority, SMSF serving node ID(s) (if available, are obtained from UDM in step 7), SMS Application port ID, trigger payload, Trigger Indication) message to the SMS-SC. If the NEF indicates that "Absent subscriber" was received from the UDM, the SMS-SC should not submit the message, but store it directly and send Routing Information for SM to request the UDM to add the SMS-SC address to the Message Waiting List. 9. The SMS-SC sends a Submit Trigger Confirm message to the NEF to confirm that the submission of the SMS has been accepted by the SMS-SC. 10. The NEF sends a Nnef_Trigger_Delivery response to the AF to indicate if the Device Trigger Request has been accepted for delivery to the UE. 11. The SMS_SC performs MT SMS delivery as defined in clause 4.13.3. The SMS-SC may provide the routing information that it received in step 6 to SMS-GMSC to avoid UDM interrogation. The SMS-SC generates the necessary CDR information and includes the AF Identifier. The SMS Application port ID, which is included in the SM User Data Header and the Trigger Indication are included in the CDRs in order to enable differentiated charging. The SMS-SC stores the trigger payload, without routing information. If the message delivery fails and is attempted to be delivered again, UDM interrogation will be performed. If the message delivery fails and the validity period of this trigger message is not set to zero, the SMS-SC shall send a SM Message Delivery Status Report to request the UDM to add the SMS-SC address to the Message Waiting list. When the message delivery is later re-attempted, a new UDM interrogation will be performed by the SMS-GMSC using SUPI or MSISDN. UDM interrogations using SUPI shall not be forwarded or relayed to SMS-Router or IP-SM-GWs. The UDM may include up to four serving node identities (MSC or MME, SGSN, IP-SM-GW, AMF) in the response to SMS-GMSC. 12. If the message delivery fails (either directly or when validity period of the trigger message expires) or when the message delivery succeeds, the SMS-SC shall send a Message Delivery Report (cause code, trigger reference number, AF Identifier) to the NEF. 13. The NEF provides a Nnef_Trigger_DeliveryNotify message to the AF with a Delivery Report indicating the trigger delivery outcome (e.g. succeeded, unknown or failed and the reason for the failure). The NEF generates the necessary CDR information including the GPSI and AF Identifier. 14. In response to the received device trigger, the UE takes specific actions and may take into consideration the content of the trigger payload. This action typically involves initiation of immediate or later communication with the AF. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.13.2.2 |
2,650 | 8.5.1.2.6 Enhanced Downlink Control Channel Performance Requirement Type A - 2 Tx Antenna Ports with Non-Colliding CRS Dominant Interferer | For the parameters specified in Table 8.5.1-1 and Table 8.5.1.2.6-1, the average probability of a miss-detecting ACK for NACK (Pm-an) shall be below the specified value in Table 8.5.1.2.6-2. The purpose of this test is to verify the PHICH performance with 2 transmit antennas when the serving cell PHICH transmission is interfered by two interfering cells with the dominant interferer having the non-colliding CRS pattern and applying interference model defined in clause B.7.1. In Table 8.5.1.2.6-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.5.1.2.6-1: Test Parameters for PHICH Table 8.5.1.2.6-2: Minimum performance PHICH for Enhanced Downlink Control Channel Performance Requirement Type A | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.5.1.2.6 |
2,651 | 4.7.2.2 Establishment cause for non-3GPP access | When establishment of an N1 NAS signalling connection over non-3GPP access is initiated, the UE shall: a) determine one or more access identities to be associated with the establishment of the N1 NAS signalling connection as specified in subclause 4.5.2 and table 4.5.2.1; b) select the establishment cause for non-3GPP access from the determined one or more access identities and the event which triggered initiation of the N1 NAS signalling connection over non-3GPP access by checking the rules specified in table 4.7.2.2.1; and c) provide the selected establishment cause for non-3GPP access to the lower layers. While an MMTEL voice call is ongoing: - any: 1) service request procedure; or 2) registration procedure; initiated in 5GMM-IDLE mode is mapped to "MO MMTel voice call" type access attempt. While an MMTEL video call is ongoing and no MMTEL voice call is ongoing: - any: 1) service request procedure; or 2) registration procedure; initiated in 5GMM-IDLE mode is mapped to "MO MMTel video call" type access attempt. While an SMSoIP is ongoing, no MMTEL video call is ongoing and no MMTEL voice call is ongoing: - any: 1) service request procedure; or 2) registration procedure; initiated in 5GMM-IDLE mode is mapped to "MO SMS over IP" type access attempt. If the access attempt matches more than one rule, the establishment cause for non-3GPP access of the lowest rule number shall be used. Table 4.7.2.2.1: Mapping table for determination of establishment cause for non-3GPP access | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.7.2.2 |
2,652 | 9.2.3.4 Conditional Handover 9.2.3.4.1 General | A Conditional Handover (CHO) is defined as a handover that is executed by the UE when one or more handover execution conditions are met. The UE starts evaluating the execution condition(s) upon receiving the CHO configuration, and stops evaluating the execution condition(s) once a handover is executed. The following principles apply to CHO: - The CHO configuration contains the configuration of CHO candidate cell(s) generated by the candidate gNB(s) and execution condition(s) generated by the source gNB. - An execution condition may consist of one or two trigger condition(s) (CHO events A3/A5, as defined in [12]). Only single RS type is supported and at most two different trigger quantities (e.g. RSRP and RSRQ, RSRP and SINR, etc.) can be configured simultaneously for the evalution of CHO execution condition of a single candidate cell. - Before any CHO execution condition is satisfied, upon reception of HO command (without CHO configuration), the UE executes the HO procedure as described in clause 9.2.3.2, regardless of any previously received CHO configuration. - While executing CHO, i.e. from the time when the UE starts synchronization with target cell, UE does not monitor source cell. CHO is also supported for the IAB-MT in context of intra- and inter-donor IAB-node migration and BH RLF recovery. CHO is not supported for NG-C based handover in this release of the specification. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 9.2.3.4 |
2,653 | 4.3.2 Domain selection for UE originating sessions / calls | The behaviour of the UE for domain selection is determined by: a) the UE usage setting; b) the availability of IMS voice; and c) whether the UE operates in single-registration mode or dual-registration mode (see 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8]). In the present document the condition "the UE supports IMS voice over 3GPP access" evaluates to "true" if at least one of the following is fulfilled: 1) the UE supports IMS voice over NR connected to 5GCN; 2) the UE supports IMS voice over E-UTRA connected to 5GCN; or 3) the UE supports IMS voice in EPS. In the present document the condition "the UE does not support IMS voice over 3GPP access" evaluates to "true" if the condition "the UE supports IMS voice over 3GPP access" evaluates to "false". In the present document the condition "the UE supports IMS voice over non-3GPP access" evaluates to "true" if the UE supports IMS voice over non-3GPP access connected to 5GCN. In the present document the condition "the UE does not support IMS voice over non-3GPP access" evaluates to "true" if the condition "the UE supports IMS voice over non-3GPP access" evaluates to "false". In the present document, "IMS voice not available" is determined per access type independently, i.e. 3GPP access or non-3GPP access. In the present document, "IMS voice not available" refers to one of the following conditions: a) the UE does not support IMS voice; b) the UE supports IMS voice, but the network indicates in the REGISTRATION ACCEPT message that IMS voice over PS sessions are not supported; or c) the UE supports IMS voice, the network indicates in the REGISTRATION ACCEPT message that IMS voice over PS sessions are supported, but the upper layers: 1) provide no indication that the UE is available for voice call in the IMS within a manufacturer determined period of time; or 2) indicate that the UE is not available for voice calls in the IMS. NOTE 1: If conditions a and b evaluate to false, the upper layers need time to attempt IMS registration. In the event an indication from the upper layers that the UE is available for voice calls in the IMS takes longer than the manufacturer determined period of time (e.g. due to delay when attempting IMS registration or due to delay in obtaining a QoS flow for SIP signalling), the NAS layer assumes the UE is not available for voice calls in the IMS. Other conditions may exist but these are implementation specific. In the present document, "IMS voice available" applies when "IMS voice not available" does not apply. When IMS voice is not available over 3GPP access, if the UE's usage setting is "voice centric", the UE operates in single-registration mode, and the UE: a) does not have a persistent PDU session, and: 1) if the UE is only registered over 3GPP access, or if the UE is registered over both 3GPP access and non-3GPP access and IMS voice is not available over non-3GPP access, the UE shall disable the N1 mode capability for 3GPP access and proceed as specified in subclause 4.9.2 with modifications described below; or 2) if the UE is registered over both 3GPP access and non-3GPP access and IMS voice is available over non-3GPP access, the UE may disable the N1 mode capability for 3GPP access and proceed as specified in subclause 4.9.2 with modifications described below; or b) has a persistent PDU session, then the UE waits until the radio bearer associated with the persistent PDU session has been released. When the radio bearer associated with the persistent PDU session has been released, then: 1) if the UE is only registered over 3GPP access, or if the UE is registered over both 3GPP access and non-3GPP access and IMS voice is not available over non-3GPP access,the UE shall disable the N1 mode capability for 3GPP access and proceed as specified in subclause 4.9.2 with modifications described below; or 2) If the UE is registered over both 3GPP access and non-3GPP access and IMS voice is available over non-3GPP access, the UE may disable the N1 mode capability for 3GPP access and proceed as specified in subclause 4.9.2 with modifications described below. The following modifications are applied to the procedure in subclause 4.9.2 for disabling the N1 mode capability for 3GPP access, if the UE's usage setting is "voice centric" and the UE operates in single-registration mode: a) in item a) of subclause 4.9.2, the UE shall attempt to select an E-UTRA cell connected to EPC. If such a cell is found, the UE shall then perform voice domain selection procedures as defined in 3GPP TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [15]; and b) in item b) of subclause 4.9.2, if an E-UTRA cell connected to EPC cannot be found, the UE shall attempt to select another supported radio access technology which supports voice services. When IMS voice is not available over non-3GPP access, if the UE's usage setting is "voice centric" and the UE operates in single-registration mode, then: a) if the UE is only registered over non-3GPP access, the UE shall disable the N1 mode capability for non-3GPP access (see subclause 4.9.3); or b) if the UE is registered over both 3GPP access and non-3GPP access and IMS voice is not available also over 3GPP access, the UE may disable the N1 mode capability for non-3GPP access (see subclause 4.9.3). NOTE 2: The UE can register over 3GPP access in another mode, e.g., S1 mode, for voice service, and in this case the UE can keep the N1 mode capability for non-3GPP access enabled. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.3.2 |
2,654 | 6.6.2.3.2 Minimum requirements UTRA | UTRA Adjacent Channel Leakage power Ratio (UTRAACLR) is the ratio of the filtered mean power centred on the assigned E-UTRA channel frequency to the filtered mean power centred on an adjacent(s) UTRA channel frequency. UTRA Adjacent Channel Leakage power Ratio is specified for both the first UTRA adjacent channel (UTRAACLR1) and the 2nd UTRA adjacent channel (UTRAACLR2). The UTRA channel power is measured with a RRC bandwidth filter with roll-off factor =0.22. The assigned E-UTRA channel power is measured with a rectangular filter with measurement bandwidth specified in Table 6.6.2.3.2-1. If the measured UTRA channel power is greater than –50dBm then the UTRAACLR shall be higher than the value specified in Table 6.6.2.3.2-1. UTRAACLR is not applicable to the power class 3 UE operating in Band 7, 12, 13, 17, 20, 24, 27, 30, 33, 35, 36, 37, 38, 40, 43, 44, 45, 47, 48, 50, 51, 52, 68, 70, 71, 85 and Scell operation in Band 46, 49. UTRAACLR is not applicable to the power class 2 UE operating in Band 38, 40, 41, 42 or 47 and Scell operation in Band 46. UTRAACLR is not applicable to the power class 1 UE operating in Band 3, 20, 28, 31 or 72. Table 6.6.2.3.2-1: Requirements for UTRAACLR1/2 | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.6.2.3.2 |
2,655 | – HighSpeedParameters | The IE HighSpeedParameters is used to convey capabilities related to high speed scenarios. HighSpeedParameters information element -- ASN1START -- TAG-HIGHSPEEDPARAMETERS-START HighSpeedParameters-r16 ::= SEQUENCE { measurementEnhancement-r16 ENUMERATED {supported} OPTIONAL, demodulationEnhancement-r16 ENUMERATED {supported} OPTIONAL } HighSpeedParameters-v1650 ::= CHOICE { intraNR-MeasurementEnhancement-r16 ENUMERATED {supported}, interRAT-MeasurementEnhancement-r16 ENUMERATED {supported} } HighSpeedParameters-v1700 ::= SEQUENCE { -- R4 18-1: Enhanced RRM requirements specified for CA for FR1 HST measurementEnhancementCA-r17 ENUMERATED {supported} OPTIONAL, -- R4 18-2: Enhanced RRM requirements specified for inter-frequency measurement in connected mode for FR1 HST measurementEnhancementInterFreq-r17 ENUMERATED {supported} OPTIONAL } -- TAG-HIGHSPEEDPARAMETERS-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
2,656 | – CA-BandwidthClassNR | The IE CA-BandwidthClassNR indicates the NR CA bandwidth class as defined in TS 38.101[ None ] -1 [15], table 5.3A.5-1 and TS 38.101[ None ] -2 [39], table 5.3A.4-1. CA-BandwidthClassNR information element -- ASN1START -- TAG-CA-BANDWIDTHCLASSNR-START -- R4 17-6: new CA BW Classes R2-R12 -- R4 17-7: new CA BW Classes V, W CA-BandwidthClassNR ::= ENUMERATED {a, b, c, d, e, f, g, h, i, j, k, l, m, n, o, p, q, ...,r2-v1730, r3-v1730, r4-v1730, r5-v1730, r6-v1730, r7-v1730, r8-v1730, r9-v1730, r10-v1730, r11-v1730, r12-v1730,v-v1770, w-v1770 } CA-BandwidthClassNR-r17 ::= ENUMERATED {r, s, t, u, ...} -- TAG-CA-BANDWIDTHCLASSNR-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
2,657 | I.10.3.2 Trusted non-3GPP access support in SNPN with CH | UE may use the credentials from a Credentials Holder AAA server to access SNPN services via Trusted Non-3GPP access. Figure I.10.3.2-1: Procedure for Trusted Non-3GPP Access using Credentials Holder AAA Server 0 prior conditions and assumptions are described in step 0 in clause I.2.2.2.2. 1-7a as specified in clause 7A.2.1. In addition, if the construction of SUCI as described in clause 6.12 cannot be used and if the employed EAP method supports SUPI privacy, the UE may send an anonymous SUPI based on configuration. 8 authentication and key agreement procedure between the UE and the AAA server, as specified in steps 2-15 in clause I.2.2.2.2. 9-19 as specified in clause I.10.3.1. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | I.10.3.2 |
2,658 | 5.11.2 UE Radio Capability Handling | The UE Radio Capability information contains information on RATs that the UE supports (e.g. power class, frequency bands, etc). Consequently, this information can be sufficiently large (e.g. >50 octets for a UE supporting a small number of frequency bands; or multiple kilo bytes for a UE supporting many frequency bands and a large multiplicity of combinations of these frequency bands) that it is undesirable to send it across the radio interface at every transition from ECM-IDLE to ECM-CONNECTED. To avoid this radio overhead, the MME stores the UE Capability information during ECM-IDLE state and the MME shall, if it is available, send its most up-to-date UE Radio Capability information to the E-UTRAN in the S1 interface INITIAL CONTEXT SETUP REQUEST message unless the UE is performing an Attach procedure or a Tracking Area Update procedure for the "first TAU following GERAN/UTRAN Attach" or for a "UE radio capability update". NOTE 1: The UTRAN Radio Capabilities are excluded from the information stored in the MME owing to issues with the handling of dynamic UMTS security parameters. If a UE supports both NB-IoT and WB-E-UTRAN, the UE handles the UE Radio capability information as follows: - When the UE is camping on NB-IoT the UE provides only NB-IoT UE radio capabilities to the network. - When the UE is camping on WB-E-UTRAN, the UE provides UE radio capabilities including WB-E-UTRAN UE radio capabilities but not NB-IoT UE radio capabilities to the network. In order to handle the distinct UE radio capabilities, the MME stores a separate NB-IoT specific UE Radio Capability information when the UE provides the UE Radio Capability information while camping on NB-IoT. When the UE is camping on NB-IoT, the MME sends, if available, the NB-IoT specific UE Radio Capability information to the E-UTRAN. When the UE is camping on WB-E-UTRAN, the MME sends, if available, UE radio capabilities including WB-E-UTRAN UE radio capabilities but not NB-IoT radio capabilities. For a UE that supports NR as a Secondary RAT, the UE's NR radio capabilities are contained within the UE Radio Capability IE. If the UE is performing an Attach procedure or a Tracking Area Update procedure for the "first TAU following GERAN/UTRAN Attach" or for "UE radio capability update", the MME shall delete (or mark as deleted) any UE Radio Capability information that it has stored, and, if the MME sends an S1 interface INITIAL CONTEXT SETUP REQUEST or UE RADIO CAPABILITY MATCH REQUEST message during that procedure, the MME shall not send any UE Radio Capability information to the E-UTRAN in that message. This triggers the E-UTRAN to request the UE Radio Capability from the UE and to upload it to the MME in the S1 interface UE CAPABILITY INFO INDICATION message. The size of the UE Radio Capability information may be greater than can be carried in single RRC message but less than the maximum size of messages on the S1 interface. In this case, to obtain the information that it needs the RAN should send multiple requests to the UE for different sub-sets of UE Radio Capability information (e.g. one request per RAT). Then the RAN shall combine these subsets (excluding UTRAN and NB-IoT capabilities) into a single UE Radio Capability IE and upload it to the MME in the S1 interface UE CAPABILITY INFO INDICATION message. The MME stores the UE Radio Capability information, and includes it in further INITIAL CONTEXT SETUP REQUEST or UE RADIO CAPABILITY MATCH REQUEST messages in other cases than Attach procedure, Tracking Area Update procedure for the "first TAU following GERAN/UTRAN Attach" and "UE radio capability update" procedure. If the UE is performing a Service Request (or other) procedure and the MME does not have UE Radio Capability information available (or it is available, but marked as "deleted"), then the MME sends an S1 interface INITIAL CONTEXT SETUP REQUEST message to the E-UTRAN without any UE Radio Capability information in it. This triggers the E-UTRAN to request the UE Radio Capability from the UE and upload it to the MME in the S1 interface UE CAPABILITY INFO INDICATION message. NOTE 2: This use of the INITIAL CONTEXT SETUP REQUEST message means that for a signalling only procedure such as a periodic Tracking Area Update, the UE Radio Capability would not be sent to the E-UTRAN. NOTE 3: If a "first TAU following GERAN/UTRAN Attach" Tracking Area Update is performed during ECM-CONNECTED mode, e.g. after an inter RAT handover, no INITIAL CONTEXT SETUP REQUEST is sent and the UE Radio Capability information in the MME will remain deleted until the next ECM-IDLE to ECM-CONNECTED transition (or later, e.g. if the next activity from the UE is another Tracking Area Update). When the CIoT EPS Optimisations do not apply, if the MME has not stored the UE Radio Capability information, in order to obtain UE radio capability for paging information, the MME can trigger the retrieval of the UE Radio Capability information by indicating UE Radio Capability request in DOWNLINK NAS TRANSPORT message during Attach or TAU procedure. For the CIoT EPS Optimisations, during the Attach procedure or the Tracking Area Update procedure e.g. for the "first TAU following GERAN/UTRAN Attach", or mobility between a cell that does not broadcast SystemInformationBlockType31(-NB) and an E-UTRA cell that broadcasts SystemInformationBlockType31(-NB)), if the MME does not send an S1 interface INITIAL CONTEXT SETUP REQUEST to the E-UTRAN, the MME should obtain the UE Radio Capability information by sending either the DOWNLINK NAS TRANSPORT message indicating UE Radio Capability request or the CONNECTION ESTABLISHMENT INDICATION message without UE Radio Capability information included to the E-UTRAN. This triggers the E-UTRAN to request the UE Radio Capability from the UE and upload it to the MME in the S1 interface UE CAPABILITY INFO INDICATION message, as specified in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [5]. In subsequent ECM connections, if the MME does not send an S1 interface INITIAL CONTEXT SETUP REQUEST to the E-UTRAN, the MME sends the UE Radio Capability to the E-UTRAN in the CONNECTION ESTABLISHMENT INDICATION message or DOWNLINK NAS TRANSPORT message. The UE Radio Capability is not provided directly from one CN node to another. It will be uploaded to the MME when the E-UTRAN requests the UE Radio Capability information from the UE. During handover via the MME (both intra RAT and inter RAT), the radio capability information for the source and target 3GPP RATs (with the possible exception of UTRAN and E-UTRAN) are transferred in the "source to target transparent container". Information on additional 3GPP RATs is optionally transferred in the "source to target transparent container". At handover, transfer of the radio capability information related to the source and/or additional RATs is beneficial as it avoids the need for the target RAT to retrieve the information from the UE prior to a subsequent inter-RAT handover. However, there may be situations where the size of the UE Radio Capability may be too large for the information on all of the UE's RATs to be carried in a single message on one or more of the network interfaces involved in the handover. Hence, the source RAN shall ensure that the size of the UE Radio Capability information does not cause the size of the "source to target transparent container" to exceed the limits that can be handled by interfaces involved in the handover (e.g. Iu interface (TS 25.413[ UTRAN Iu interface Radio Access Network Application Part (RANAP) signalling ] [22]) and, following SRVCC, E interface (TS 29.002[ Mobile Application Part (MAP) specification ] [86])). This may result in some radio capability information being omitted from the "source to target transparent container" at inter-RAT handover. In the case that a source RAN node omits some radio capability information from the "source to target transparent container" at handover, the source RAN node shall ensure that any future target RAN node can detect that that radio capability information has been omitted. Owing to issues with dynamic UTRAN security parameters, special rules apply to the handling of the UTRAN radio capability information at inter-RAT handover (see e.g. the HandoverPreparationInformation message description in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [37] and the usage of the PS Handover Complete Ack message in TS 43.129[ None ] [8] and TS 48.018[ None ] [42]) To allow for the addition of future radio technologies, frequency bands, and other enhancements, the MME shall store the UE Radio Capability Information as defined in TS 23.008[ Organization of subscriber data ] [28]. The E-UTRAN stores the UE Radio Capability information, received in the S1 interface INITIAL CONTEXT SETUP REQUEST message or obtained from the UE, for the duration of the RRC connection for that UE. Before any handover attempt from E-UTRAN to UTRAN, the E-UTRAN retrieves the UE's UTRAN Radio Capabilities from the UE. If the UE's non-UTRAN UE Radio Capability information changes while in ECM-IDLE state (including cases of being in GERAN/UTRAN coverage), the UE shall perform a Tracking Area Update indicating "UE radio capability update" when it next returns to E-UTRAN coverage. When the UE is in ECM-IDLE with AS information stored (as defined in clause 4.11 for User Plane CIOT EPS optimisation), NAS shall trigger AS to establish a new RRC connection and not resume the existing one in order to send Tracking Area Update indicating "UE radio capability update". As a result of this, the access stratum in the UE will discard the AS information and establish a new RRC connection as defined in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [37]. The UE shall perform a Tracking Area Update procedure at every change between a cell that does not broadcast SystemInformationBlockType31(-NB) and an E-UTRA cell that broadcasts SystemInformationBlockType31(-NB). This Tracking Area Update shall indicate that the Tracking Area Update is for a "UE radio capability update". The MME may also request for Voice Support Match Information. If requested, the eNodeB then derives and provides an indication to the MME whether the UE radio capabilities are compatible with the network configuration (e.g. whether the UE supports the frequency bands that the network may rely upon for providing "full" PS voice coverage or whether the UE supports the SRVCC configuration of the network e.g. E-UTRAN to GERAN) as defined in clause 5.3.14. The signalling of the UE Radio Access Capabilities described in this clause can be optimised by means of the RACS feature defined in clause 5.11.3a. | 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.11.2 |
2,659 | 5.31.7.2.2 Paging for extended idle mode DRX in E-UTRA and NR connected to 5GC | 5.31.7.2.2.0 General For WB-E-UTRA and LTE-M connected to 5GC, the extended idle mode DRX value range will consist of values starting from 5.12s (i.e. 5.12s, 10.24s, 20.48s, etc.) up to a maximum of 2621.44s (almost 44 min). For NB-IoT, the extended idle mode DRX value range will start from 20.48s (i.e. 20.48s, 40.96s, 81.92, etc.) up to a maximum of 10485.76s (almost 3 hours) (see TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [52]). For NR, the extended idle mode DRX value range will consist of values starting from 2.56s (i.e. 2.56s, 5.12s, 10.24s, 20.48s, etc.) up to a maximum of 10485.76s (almost 3 hours) (see TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [50]). The extended idle mode DRX cycle length is negotiated via NAS signalling. The AMF includes the extended idle mode DRX cycle length for NR, WB-E-UTRA, LTE-M or NB-IoT in paging message to assist the NG-RAN node in paging the UE. For NR, Paging Time Window applies for extended DRX lengths longer than 10.24s as defined in TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [50]. For WB-E-UTRA, LTE-M and NB-IoT, Paging Time Window applies for extended DRX lengths of 10.24s and longer as defined in TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [52]. The network follows the regular paging strategy as defined in clause 5.4.5 when the extended idle mode DRX cycle length is 5.12s or less for WB-E-UTRA, LTE-M and NB-IoT, or 10.24s or less for NR. Clauses 5.31.7.2.2.1, 5.31.7.2.2.2 and 5.31.7.2.2.3 apply when the extended idle mode DRX cycle length is 10.24s or longer for WB-E-UTRA, LTE-M and NB-IoT, or longer than 10.24s for NR. 5.31.7.2.2.1 Hyper SFN, Paging Hyperframe and Paging Time Window length A Hyper-SFN (H-SFN) frame structure is defined on top of the SFN used for regular idle mode DRX. Each H-SFN value corresponds to a cycle of the legacy SFN of 1024 radio frames, i.e. 10.24s. When extended idle mode DRX is enabled for a UE, the UE is reachable for paging in specific Paging Hyperframes (PH), which is a specific set of H-SFN values. The PH computation is a formula that is function of the extended idle mode DRX cycle, and a UE specific identifier, as described in TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [52] and TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [50]. This value can be computed at all UEs and AMFs without need for signalling. The AMF includes the extended idle mode DRX cycle length and the PTW length in paging message to assist the NG-RAN nodes in paging the UE. The AMF also assigns a Paging Time Window length, and provides this value to the UE during Registration Update procedures together with the extended idle mode DRX cycle length. The UE first paging occasion is within the Paging Hyperframe as described in TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [52] and TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [50]. The UE is assumed reachable for paging within the Paging Time Window. The start and end of the Paging Time Window is described in TS 36.304[ Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) procedures in idle mode ] [52] and TS 38.304[ NR; User Equipment (UE) procedures in Idle mode and in RRC Inactive state ] [50]. After the Paging Time Window length, the AMF considers the UE unreachable for paging until the next Paging Hyperfame. 5.31.7.2.2.2 Loose Hyper SFN synchronization NOTE: This clause applies when the extended DRX cycle length is 10.24s or longer for WB-E-UTRA, LTE-M and NB-IoT, and longer than 10.24s for NR. In order for the UE to be paged at roughly similar time, the H-SFN of all NG-RAN nodes and AMFs should be loosely synchronized. Each NG-RAN node and AMF synchronizes internally the H-SFN counter so that the start of H-SFN=0 coincides with the same a preconfigured time epoch. If NG-RAN nodes and AMFs use different epochs, e.g. due to the use of different time references, the GPS time should be set as the baseline, and the NG-RAN nodes and AMFs synchronize the H-SFN counter based on the GPS epoch considering the time offset between GPS epoch and other time-reference epoch a preconfigured time. It is assumed that NG-RAN nodes and AMFs are able to use the same H-SFN value with accuracy in the order of legacy DRX cycle lengths, e.g. 1 to 2 seconds. There is no need for synchronization at SFN level. There is no signalling between network nodes required to achieve this level of loose H-SFN synchronization. 5.31.7.2.2.3 AMF paging and paging retransmission strategy NOTE: This clause applies when the extended DRX cycle length is 10.24s or longer for WB-E-UTRA, LTE-M and NB-IoT, and longer than 10.24s for NR. When the AMF receives trigger for paging and the UE is reachable for paging, the AMF sends the paging request. If the UE is not reachable for paging, then the AMF pages the UE just before the next paging occasion. The AMF determines the Paging Time Window length and a paging retransmission strategy, and executes the retransmission scheme. For extended DRX length of 10.24s, in the paging request message the AMF sends the Paging Time Window to the ng-eNB but does not send the Paging Time Window to the gNB. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.31.7.2.2 |
2,660 | 13.4.1 OAuth 2.0 based authorization of Network Function service access 13.4.1.0 General | The authorization framework described in clause 13.4.1 allows NF Service Producers to authorize the requests from NF Service requestors. Subscription requests are also service requests. The authorization framework uses the OAuth 2.0 framework as specified in RFC 6749 [43]. Grants shall be of the type Client Credentials Grant, as described in clause 4.4 of RFC 6749 [43]. Access tokens shall be JSON Web Tokens as described in RFC 7519 [44] and are secured with digital signatures or Message Authentication Codes (MAC) based on JSON Web Signature (JWS) as described in RFC 7515 [45]. NOTE 1a: Securing the access token using Message Authentication Codes (MAC) based on JSON Web Signature (JWS) as described in RFC 7515 [45] requires a pairwise pre-shared symmetric key between the NRF and the NF Service Producer. The provisioning of such pre-shared symmetric key is outside the scope of this document. The basic extent provided by the authorization token is at service level (i.e. the "scope" claim includes allowed services per NF type). Depending on the NF Service Producer configuration, higher level of granularity for the authorization token can be defined adding "additional scope" information within the token e.g. to authorize specific service operations and/or resources/data sets within service operations per NF Service Consumer type. NOTE 1: The additional scope(s) included within the access token add additional security checks at the NF Service Producer that authorizes the services operations, resources and NF Service Consumer type related to the additional scope(s). The authorization framework described in clause 13.4.1 is mandatory to support for NRF and NF. The OAuth 2.0 framework does not apply to the notification operation. Extensions to the authorization framework specific for the security of enablers for Network Automation by 5GS are described in Annex X. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 13.4.1 |
2,661 | 5.8.2 Subscriber privacy related requirements to UDM and SIDF | The SIDF is responsible for de-concealment of the SUCI and shall fulfil the following requirements: - The SIDF shall be a service offered by UDM. - The SIDF shall resolve the SUPI from the SUCI based on the protection scheme used to generate the SUCI. The Home Network Private Key used for subscriber privacy shall be protected from physical attacks in the UDM. The UDM shall hold the Home Network Public Key Identifier(s) for the private/public key pair(s) used for subscriber privacy. The algorithm used for subscriber privacy shall be executed in the secure environment of the UDM. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 5.8.2 |
2,662 | B.2 Protocol errors (e.g., unknown message) | Cause #95 – Semantically incorrect message This 5GSM cause is used to report receipt of a message with semantically incorrect contents. Cause #96 – Invalid mandatory information This 5GSM cause indicates that the equipment sending this 5GSM cause has received a message with a non-semantical mandatory IE error. Cause #97 – Message type non-existent or not implemented This 5GSM cause indicates that the equipment sending this 5GSM cause has received a message with a message type it does not recognize either because this is a message not defined, or defined but not implemented by the equipment sending this 5GSM cause. Cause #98 – Message type not compatible with protocol state This 5GSM cause indicates that the equipment sending this 5GSM cause has received a message not compatible with the protocol state. Cause #99 – Information element non-existent or not implemented This 5GSM cause indicates that the equipment sending this 5GSM cause has received a message which includes information elements not recognized because the information element identifier is not defined or it is defined but not implemented by the equipment sending the 5GSM cause. However, the information element is not required to be present in the message in order for the equipment sending the 5GSM cause to process the message. Cause #100 – Conditional IE error This 5GSM cause indicates that the equipment sending this cause has received a message with conditional IE errors. Cause #101 – Message not compatible with protocol state This 5GSM cause indicates that a message has been received which is incompatible with the protocol state. Cause #111 – Protocol error, unspecified This 5GSM cause is used to report a protocol error event only when no other 5GSM cause in the protocol error class applies. | 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 | B.2 |
2,663 | 9.11.3.57 Uplink data status | The purpose of the Uplink data status information element is to indicate to the network which preserved PDU session(s) have uplink data pending or which preserved PDU session(s) are associated with active multicast MBS session(s). The Uplink data status information element is coded as shown in figure 9.11.3.57.1 and table 9.11.3.57.1. The Uplink data status information element is a type 4 information element with minimum length of 4 octets a maximum length of 34 octets. Figure 9.11.3.57.1: Uplink data status information element Table 9.11.3.57.1: Uplink data status 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.57 |
2,664 | 8.2.3.4 Minimum Requirement for Closed-loop spatial multiplexing performance 4Tx Antenna Port for dual connectivity | For dual connectivity the requirements are specified in Table 8.2.3.4-4, based on single carrier requirement specified in Table 8.2.3.4-2 and Table 8.2.3.4-3, with the addition of the parameters in Table 8.2.3.4-1 and the downlink physical channel setup according to Annex C.3.2. The purpose of these tests is to verify the closed loop rank-two performance with wideband and frequency selective precoding by using dual connectivity transmission. Table 8.2.3.4-1: Test Parameters for Multi-Layer Spatial Multiplexing (FRC) for TDD-FDD dual connectivity Table 8.2.3.4-2: FDD single carrier performance for multiple dual connectivity configurations Table 8.2.3.4-3: TDD single carrier performance for multiple dual connectivity configurations Table 8.2.3.4-4: Minimum performance Multi-Layer Spatial Multiplexing (FRC) for dual connectivity | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.2.3.4 |
2,665 | 5.5.4.20b Event Z1 (Serving L2 U2N Relay UE becomes worse than threshold1 and Candidate L2 U2N Relay UE becomes better than threshold2) | The UE shall: 1> consider the entering condition for this event to be satisfied when both condition Z1-1 and condition Z1-2, as specified below, are fulfilled; 1> consider the leaving condition for this event to be satisfied when condition Z1-3 or condition Z1-4, i.e. at least one of the two, as specified below, is fulfilled; Inequality Z1-1 (Entering condition 1) Mr + Hys < Thresh1 Inequality Z1-2 (Entering condition 2) Mn – Hys > Thresh2 Inequality Z1-3 (Leaving condition 1) Mr – Hys > Thresh1 Inequality Z1-4 (Leaving condition 2) Mn + Hys < Thresh2 The variables in the formula are defined as follows: Mr is the measurement result of the serving L2 U2N Relay UE, not taking into account any offsets. Mn is the measurement result of the candidate L2 U2N Relay UE, not taking into account any offsets. Hys is the hysteresis parameter for this event (i.e. hysteresis as defined within reportConfigInterRAT for this event). Thresh1 is the threshold parameter for this event (i.e. sl-rsrp in z1-Threshold1-Relay as defined within reportConfigInterRAT if the UE measures SL-RSRP, or sd-rsrp in z1-Threshold1-Relay as defined within reportConfigInterRAT if the UE measures SD-RSRP for this event). Thresh2 is the threshold parameter for this event (i.e. z1-Threshold2-Relay as defined within reportConfigInterRAT for this event). Mr is expressed in dBm or dB, depending on the measurement quantity of serving L2 U2N Relay UE. Mn is expressed in dBm or dB, depending on the measurement quantity of candidate L2 U2N Relay UE. Hys are expressed in dB. Thresh1 is expressed in the same unit as Mr. Thresh2 is expressed in the same unit as Mn. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.5.4.20b |
2,666 | 6.1.3.2.3 Abnormal cases | The following abnormal cases can be identified: a) Expiry of timers In the mobile station: On the first expiry of the timer T3380, the MS shall resend the ACTIVATE SECONDARY PDP CONTEXT REQUEST and shall reset and restart timer T3380. This retransmission is repeated four times, i.e. on the fifth expiry of timer T3380, the MS shall release all resources possibly allocated for this invocation and shall abort the procedure; no automatic PDP context activation re-attempt shall be performed. On the network side: On the first expiry of the timer T3385, the network shall resend the message REQUEST SECONDARY PDP CONTEXT ACTIVATION and shall reset and restart timer T3385. This retransmission is repeated four times, i.e. on the fifth expiry of timer T3385, the network shall release possibly allocated resources for this activation and shall abort the procedure. b) MS initiated secondary PDP context activation procedure for an already activated PDP context (On the network side) If the NSAPI matches that of an already activated PDP context, the network shall deactivate the existing PDP context locally without notification to the MS and proceed with the requested PDP context activation. The case of a TI match is described in subclause 8.3.2. c) no PDP context with linked TI activated (on the network side) The network shall then check whether there is an activated PDP context for the TI given in the Linked TI IE in the ACTIVATE SECONDARY PDP CONTEXT REQUEST message. If there is no active PDP context for the specified TI, the network shall reply with an ACTIVATE SECONDARY PDP CONTEXT REJECT message, cause code indicating "unknown PDP context". d) no PDP context with Linked TI activated (on the mobile station side) The MS shall check whether there is an activated PDP context for the TI given in the Linked TI IE in the REQUEST SECONDARY PDP CONTEXT ACTIVATION message. If there is no active PDP context for the specified TI, the MS shall reply with a REQUEST SECONDARY PDP CONTEXT ACTIVATION REJECT message, cause code indicating "unknown PDP context". e) MS initiated secondary PDP context activation procedure for a PDN connection established for emergency bearer services (on the network side) If the MS initiated secondary PDP context activation procedure is for a PDN connection established for emergency bearer services the network shall reply with an ACTIVATE SECONDARY PDP CONTEXT REJECT message, cause code indicating "activation rejected, unspecified". f) no TFT IE is received in the REQUEST SECONDARY PDP CONTEXT ACTIVATION message (on the mobile station side) The MS shall either: A) reply with a REQUEST SECONDARY PDP CONTEXT ACTIVATION REJECT message, cause code indicating "semantic error in the TFT operation"; or B) optionally, to support networks compliant with earlier versions of the protocol, accept the network requested secondary PDP context activation and proceed as specified in subclause 6.1.3.2.1a. If another PDP context with the same PDP address and APN without a TFT exists, the MS shall deactivate this old PDP context without a TFT by explicit peer-to-peer signalling between the MS and the network. If during a previous inter-system change from S1 mode to A/Gb or Iu mode the default PDP context linked to the new PDP context was mapped from an EPS bearer context, the MS shall follow option A. NOTE 1: A network implementing this version of the protocol will always include a request for a TFT when requesting the activation of a non-default PDP context. If a PDP context for the TI given in the Linked TI IE exists, then the TFT in the ACTIVATE SECONDARY PDP CONTEXT REQUEST or the REQUEST SECONDARY PDP CONTEXT ACTIVATION message is checked for different types of TFT IE errors as follows: a) Semantic errors in TFT operations: 1) When the TFT operation is an operation other than "Create a new TFT". The network shall reject the activation request with cause "semantic error in the TFT operation". The MS shall reject the activation request with cause "semantic error in the TFT operation". b) Syntactical errors in TFT operations: 1) When the TFT operation is "Create a new TFT" and the packet filter list in the TFT IE is empty. 2) Void. 3) When there are other types of syntactical errors in the coding of the TFT IE, such as a mismatch between the number of packet filters subfield, and the number of packet filters in the packet filter list. The network shall reject the activation request with cause "syntactical error in the TFT operation". The MS shall reject the activation request with cause "syntactical error in the TFT operation". c) Semantic errors in packet filters: 1) When a packet filter consists of conflicting packet filter components which would render the packet filter ineffective, i.e. no IP packet will ever fit this packet filter. How the network determines a semantic error in a packet filter is outside the scope of the present document. 2) When the resulting TFT does not contain any packet filter applicable for the uplink direction. NOTE 2: When BCM='MS only', the MS is allowed to include a TFT with packet filters without any explicit direction information, i.e. with value "00", and such packet filters are applicable for both uplink and downlink directions. The network shall reject the activation request with cause "semantic errors in packet filter(s)". The MS shall reject the activation request with cause "semantic errors in packet filter(s)". d) Syntactical errors in packet filters: 1) When the TFT operation is "Create a new TFT" and two or more packet filters in the resultant TFT would have identical packet filter identifiers. 2) When the TFT operation is "Create a new TFT" and two or more packet filters in all TFTs associated with this PDP address and APN would have identical packet filter precedence values. 3) When there are other types of syntactical errors in the coding of packet filters, such as the use of a reserved value for a packet filter component identifier. In case 2) the network shall not diagnose an error, further process the new activation request and, if it was processed successfully, delete the old packet filters which have identical filter precedence values. Furthermore, by means of explicit peer-to-peer signalling between the MS and the network, the network shall deactivate the PDP context(s) for which it has deleted the packet filters. In cases 1) and 3) the network shall reject the activation request with cause "syntactical errors in packet filter(s)". In case 2) the MS shall not diagnose an error, further process the new activation request and, if it was processed successfully, delete the old packet filters which have identical filter precedence values. Furthermore, by means of explicit peer-to-peer signalling between the network and the MS, the MS shall deactivate the PDP context(s) for which it has deleted the packet filters. In cases 1) and 3) the MS shall reject the activation request with cause "syntactical errors in packet filter(s)". Otherwise, the network shall accept the activation request by replying to the MS with an ACTIVATE SECONDARY PDP CONTEXT ACCEPT message. In case of network requested secondary PDP context activation procedure the MS shall accept the activation request by replying to the network with an ACTIVATE SECONDARY PDP CONTEXT REQUEST message. Figure 6.5/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : MS initiated secondary PDP context activation procedure Figure 6.5a/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Network requested secondary PDP context activation procedure | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.1.3.2.3 |
2,667 | Annex J (informative): Link MTU considerations | According to clause 5.6.10.4 networks can provide link MTU size for UEs. A purpose of the link MTU size provisioning is to limit the size of the packets sent by the UE to avoid packet fragmentation in the backbone network between the UE and the UPF acting as PSA (and/or across the N6 reference point). Fragmentation within the backbone network creates a significant overhead. Therefore operators might desire to avoid it. This Annex presents an overhead calculation that can be used by operators to set the link MTU size provided by the network. A UE might not employ the provided link MTU size, e.g. when the MT and TE are separated, as discussed in clause 5.6.10.4. Therefore, providing an MTU size does not guarantee that there will be no packets larger than the provided value. However, if UEs follow the provided link MTU value operators will benefit from reduced transmission overhead within backbone networks. One of the worst-case scenarios is when GTP packets, e.g. between a NG-RAN node and the 5GC, are transferred over IPSec tunnel in an IPv6 deployment. In that case the user packet first encapsulated in a GTP tunnel which results in the following overhead: - IPv6 header, which is 40 octets; - UDP overhead, which is 8 octets; - Extended GTP-U header, which is 16 octets. NOTE 1: The sending of a Reflective QoS Indicator within a GTP-U header extension, or the use of Long PDCP PDU numbers at handover will further increase the GTP-U header size (see TS 29.281[ General Packet Radio System (GPRS) Tunnelling Protocol User Plane (GTPv1-U) ] [75] and TS 38.415[ NG-RAN; PDU session user plane protocol ] [116]). In this scenario the GTP packet then further encapsulated into an IPSec tunnel. The actual IPSec tunnel overhead depends on the used encryption and integrity protection algorithms. TS 33.210[ Network Domain Security (NDS); IP network layer security ] [115] mandates the support of AES-GMAC with a key length of 128 bits and the use of HMAC_SHA-1 for integrity protection. Therefore, the overhead with those algorithms is calculated as: - IPv6 header, which is 40 octets; - IPSec Security Parameter Index and Sequence Number overhead, which is 4+4 octets; - Initialization Vector for the encryption algorithm, which is 16 octets; - Padding to make the size of the encrypted payload a multiple of 16; - Padding Length and Next Header octets (2 octets); - Integrity Check Value, which is 12 octets. In order to make the user packet size as large as possible a padding of 0 octet is assumed. With this zero padding assumption the total overhead is 142 octets, which results a maximum user packet size of transport MTU minus 142 octets. Note that in the case of transport MTU=1500, this user packet size will result in a 1424 octets payload length to be ciphered, which is a multiple of 16, thus the assumption that no padding is needed is correct (see Figure J.1). Similar calculations can be done for networks with transport that supports larger MTU sizes. Figure J-1: Overhead calculation for transport MTU=1500 octet The link MTU value that can prevent fragmentation in the backbone network between the UE and the UPF acting as PSA depends on the actual deployment. Based on the above calculation a link MTU value of 1358 is small enough in most of the network deployments. However for network deployments where the transport uniformly supports for example ethernet jumbo frames, transport MTU<=9216 octets can provide a much larger UE MTU and hence more efficient transfer of user data. One example of when it can be ensured that all links support larger packet sizes, is when the UE uses a specific Network Slice with a limited coverage area. Note that using a link MTU value smaller than necessary would decrease the efficiency in the network. Moreover, a UE might also apply some tunnelling (e.g. VPN). It is desirable to use a link MTU size that assures at least MTU minus 220 octets within the UE tunnel to avoid the fragmentation of the user packets within the tunnel applied in the UE. In the case transport MTU is 1500 octets, this results a link MTU of 1280 octets (for the transport), which is the minimum MTU size in the case of IPv6. The above methodology can be modified for calculation of the UE's link MTU when a UPF has MTU limits on the N6 reference point and is offering a PDU Session with Ethernet or Unstructured PDU Session type between the UPF and the UE. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | Annex |
2,668 | 5.2.20.2 Nnssaaf_NSSAA service 5.2.20.2.1 General | Service Description: The NSSAAF provides Network Slice- Specific Authentication and Authorization (NSSAA) service to the requester NF by relaying EAP messages towards a AAA-S or AAA-P and performing related protocol conversion as needed. It also provides notification to the current AMF where the UE is of the need to re-authenticate and re-authorize the UE or to revoke the UE authorization. The AMF to receive the notification is implicitly subscribed and it is found in the UDM by providing the UE GPSI. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.20.2 |
2,669 | 7.5 SRB3 | SRB3 is supported in EN-DC, NGEN-DC and NR-DC, but not in NE-DC. The decision to establish SRB3 is taken by the SN, which provides the SRB3 configuration using an SN RRC message. SRB3 establishment and release can be done at Secondary Node Addition and Secondary Node Change. SRB3 reconfiguration can be done at Secondary Node Modification procedure. SRB3 may be used to send SN RRC Reconfiguration, SN RRC Reconfiguration Complete, SN Measurement Report, SN Failure Information (i.e., in case of failure for an SCG RLC bearer), SN UE Assistance Information message and SN IABOtherInformation, only in procedures where the MN is not involved. SN RRC Reconfiguration Complete messages are mapped to the same SRB as the message initiating the procedure. SN Measurement Report messages are mapped to SRB3, if configured, regardless of whether the configuration is received directly from the SN or via the MN. No MN RRC messages are mapped to SRB3. If split SRB1 is not configured, SRB3 may be used by the UE to transmit to the MN an encapsulated MCG Failure Information message in the ULInformationTransferMRDC message and receive in response an encapsulated RRC reconfiguration message, MobilityFromNRCommand message, MobilityFromEUTRACommand message or RRC release message in the DLInformationTransferMRDC message. SRB3 is modelled as one of the SRBs defined in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [4] and uses the NR-DCCH logical channel type. RRC PDUs on SRB3 are ciphered and integrity protected using NR PDCP, with security keys derived from S-KgNB. The SN selects ciphering and integrity protection algorithms for the SRB3 and provides them to the MN within the SCG Configuration for transmission to the UE. NOTE: A NR SCG RRC message sent via E-UTRA MCG SRB is protected by E-UTRA MCG SRB security (NR security is not used in this case). SRB3 is of higher scheduling priority than all DRBs. The default scheduling priorities of split SRB1 and SRB3 are the same. There is no requirement on the UE to perform any reordering of RRC messages between SRB1 and SRB3. When SCG is released, SRB3 is released. | 3GPP TS 37.340 | Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Overall Description; Stage-2 | RAN2 | 3GPP Series : 37 , Multiple radio access technology aspects | 7.5 |
2,670 | 5.15.11.1.1 Non-Hierarchical NSAC architecture | The NSACF keeps track of the current number of UEs registered for a network slice so that it can ensure it does not exceed the maximum number of UEs allowed to register with the network slice. The NSACF also maintains a list of UE IDs registered with a network slice that is subject to NSAC. When an event related to a UE causes the current number of UEs registered with a network slice to increase, the NSACF first checks whether the UE Identity is already in the list of UEs registered with that network slice. If not, the NSACF checks whether the maximum number of UEs per network slice for that network slice has already been reached and if it has, the NSACF applies admission control policies. The AMF triggers a request to NSACF for NSAC for maximum number of UEs when the UE's registration status for a network slice subject to NSAC is changing, i.e. during the UE Registration procedure in clause 4.2.2.2.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3], UE Deregistration procedure in clause 4.2.2.3 of TS 23.502[ Procedures for the 5G System (5GS) ] [3], Network Slice-Specific Authentication and Authorisation procedure in clause 4.2.9.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3], AAA Server triggered Network Slice-Specific Re-authentication and Re-authorization procedure in clause 4.2.9.3 of TS 23.502[ Procedures for the 5G System (5GS) ] [3], AAA Server triggered Slice-Specific Authorization Revocation in clause 4.2.9.4 of TS 23.502[ Procedures for the 5G System (5GS) ] [3] and UE Configuration Update procedure in clause 4.2.4.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. NOTE 1: Early Admission Control (EAC) mode is applicable for Number of UEs per network slice admission control. The use of EAC in relation to the number of registered UEs is described in clauses 4.2.11.2 and 4.2.11.3 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. Since the UE may register or deregister for an S-NSSAI via 3GPP access and/or non-3GPP access as described in clause 5.15.5.2.1. The Allowed NSSAI for the access type may change while the UE is registering to a network. The AMF provides the Access Type to the NSACF when triggering a request to increase or decrease the current number of UEs registered with a S-NSSAI. The NSACF may take the Access Type into account for increasing and decreasing the number of UEs per network slice by storing the UE ID with the associated one or more Access Type(s), i.e. the NSACF is able to add or remove a registration for the UE ID for each Access Type and trigger the increase or decrease of the current number of UEs registered with a S-NSSAI based on a policy that takes the access type into account. If the Access Type provided by the AMF is not configured for NSAC in the NSACF, the NSACF always accepts the request from the AMF without increasing or decreasing the number of UEs. If the Access Type provided by the AMF is configured for NSAC in the NSACF and the maximum number is reached, the NSACF sends a reject response to the AMF including the access type. NOTE 2: For example, if the NSACF is configured to apply NSAC for 3GPP Access Type only, the NSACF counts registration via 3GPP access type only. If the NSACF is configured to apply NSAC for both Access Types, and the UE newly registers via 3GPP access while the UE is already registered via non-3GPP access (or vice versa), the NSACF updates the UE ID entry with both 3GPP Access Type and non-3GPP Access Type and the NSACF may count the UE once or twice based on its policy. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.15.11.1.1 |
2,671 | 5.3 Control plane | Figure 5.3-1 shows the control plane (signalling) protocol stacks on NG and Uu interfaces. Note 1: The radio interface protocols are defined in TS 38.2[ None ] xx and TS 38.3[ None ] xx. Note 2: The protocol is defined in TS 38.41[ None ] x. (Description of NG interface). Note 3: CM, SM: This exemplifies a set of NAS control protocols between UE and 5GC. The evolution of the protocol architecture for these protocols is outside the scope of the present document. Figure 5.3-1: NG and Uu control plane NOTE: Both the Radio protocols and the NG protocols contain a mechanism to transparently transfer NAS messages. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3 |
2,672 | 4.7.7a Authentication and ciphering procedure used for UMTS authentication challenge. | The purpose of the authentication and ciphering procedure is fivefold (see 3GPP TS 33.102[ 3G security; Security architecture ] [5a] and 3GPP TS 43.020[ Security related network functions ] [13]): - to permit the network to check whether the identity provided by the MS is acceptable or not; - to provide parameters enabling the MS to calculate a new GPRS UMTS ciphering key and a new GPRS UMTS integrity key; - to let the network set the GSM ciphering mode (ciphering /no ciphering) and GSM ciphering algorithm; - to permit the mobile station to authenticate the network; and - to let the network set GSM integrity protection and GSM integrity algorithm (for control plane and optionally for user plane). In Iu mode, and in the case of a UMTS authentication challenge, the authentication and ciphering procedure can be used for authentication only. The cases in which the authentication and ciphering procedure shall be used are defined in 3GPP TS 33.102[ 3G security; Security architecture ] [5a], 3GPP TS 43.020[ Security related network functions ] [13] and 3GPP TS 42.009[ Security aspects ] [5]. The authentication and ciphering procedure is always initiated and controlled by the network. However, in the case of a UMTS authentication challenge, there is the possibility for the MS to reject the network. The MS shall support the UMTS authentication challenge, if a USIM is inserted. The authentication and ciphering procedure can be used for any combination of the following: - authentication; - setting of the GSM ciphering mode and the GSM ciphering algorithm; and - setting of GSM integrity protection and the GSM integrity algorithm (for control plane and optionally for user plane). NOTE: Setting of GSM integrity protection and the GSM integrity algorithm in the authentication and ciphering procedure is only applicable for an MS and a network supporting integrity protection in A/Gb mode. In A/Gb mode, the network should not send any user data during the authentication and ciphering procedure. A UMTS security context is established in the MS and the network when a UMTS authentication challenge is performed in A/Gb mode or in Iu mode. After a successful UMTS authentication, the GPRS UMTS ciphering key, the GPRS UMTS integrity key, the GPRS GSM ciphering key and the GPRS ciphering key sequence number, are stored both in the network and the MS. Furthermore, in A/Gb mode both the ME and the network may derive and store a GPRS GSM Kc128 as part of the UMTS security context as described in the subclause 4.7.7.3a. Furthermore, in A/Gb mode, if integrity protection is used, both the MS and the network shall derive and store a GPRS GSM Kint as part of the UMTS security context as described in the subclause 4.7.7.3b. | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 4.7.7a |
2,673 | 5.2.6.28.4 Nnef_ASTI_Delete operation | Service operation name: Nnef_ASTI_Delete Description: The consumer requests to delete the 5G access stratum time distribution configuration and deactivate the corresponding 5G access stratum time distribution service, for which the NEF authorizes the request and invokes the corresponding service operation with TSCTSF (clause 5.2.27.4.4). Inputs, Required: As specified in clause 5.2.27.4.4. Inputs, Optional: As specified in clause 5.2.27.4.4. Outputs, Required: Operation execution result indication and in the case of successful operation, any outputs as specified in clause 5.2.27.4.4. Outputs, Optional: As specified in clause 5.2.27.4.4. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.2.6.28.4 |
2,674 | 6.5.2.5 Abnormal cases in the UE | The following abnormal cases can be identified: a) Expiry of timer T3492: On the first expiry of the timer T3492, the UE shall resend the PDN DISCONNECT REQUEST and shall reset and restart timer T3492. This retransmission is repeated four times, i.e. on the fifth expiry of timer T3492, the UE shall abort the procedure, deactivate all EPS bearer contexts for this PDN connection locally without peer-to-peer signalling between the UE and the MME, release the PTI allocated for this invocation and enter the state PROCEDURE TRANSACTION INACTIVE. In order to synchronize EPS bearer contexts status with the MME, on indication of "back to E-UTRAN coverage" from the lower layers, the UE shall send a TRACKING AREA UPDATE REQUEST message that includes the EPS bearer context status IE to the MME. b) Collision of UE requested PDN disconnect procedure and dedicated EPS bearer context activation procedure: When the UE receives an ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message during the PDN disconnect procedure, and the EPS bearer to be activated belongs to the PDN connection the UE wants to disconnect, the UE shall ignore the ACTIVATE DEDICATED EPS BEARER CONTEXT REQUEST message and proceed with the PDN disconnect procedure. c) Collision of UE requested PDN disconnect procedure and EPS bearer context modification: When the UE receives a MODIFY EPS BEARER CONTEXT REQUEST message during the PDN disconnect procedure, and the EPS bearer to be modified belongs to the PDN connection the UE wants to disconnect, the UE shall ignore the MODIFY EPS BEARER CONTEXT REQUEST message and proceed with the PDN disconnect procedure. d) Collision of UE requested PDN disconnect procedure and EPS bearer context deactivation procedure: When the UE receives a DEACTIVATE EPS BEARER CONTEXT REQUEST message during the PDN disconnect procedure, and the EPS bearer indicated in the DEACTIVATE EPS BEARER CONTEXT REQUEST message is a dedicated EPS bearer belonging to the PDN connection the UE wants to disconnect, the UE shall proceed with both procedures. | 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.2.5 |
2,675 | 4.23.3 Registration procedure | The following impacts are applicable to clause 4.2.2.2 (Registration procedure) when the UE has established PDU Session(s): - Step 5: The UE context transferred from old AMF includes SMF information. If I-SMF is available for the PDU Session(s), the received SMF information includes I-SMF information and SMF information. - Step 10: The (target) AMF determines whether I-SMF insertion/change/removal is needed. If the (target) AMF does not have the service area of the SMF(s), the (target) AMF queries the NRF to get service area information of the received SMF(s). The (target) AMF determines on a per PDU Session basis whether a (new) I-SMF needs to be selected based on UE location and service area of the received SMF information. It includes the following cases: a. if the received SMF information includes only SMF information and service area of SMF includes the area where the UE camps, new I-SMF selection is not needed; or b. if the received SMF information includes both I-SMF information and SMF information and service area of I-SMF includes the area where the UE camps, the I-SMF can be reused; or c. if the received SMF information includes both I-SMF information and SMF information and the UE moves into the service area of SMF, the I-SMF removal process is triggered; or d. if the received SMF information includes only SMF information and the service area of SMF does not include the area where the UE camps, the (target) AMF selects an I-SMF. The I-SMF insertion process is triggered; or e. if the received SMF information includes both I-SMF and SMF information and the service area of SMF and I-SMF does not include the area where the UE camps, the (target) AMF selects a new I-SMF. The change of I-SMF process is triggered. - For each PDU Session, if the UE context retrieved from the old AMF includes an I-SMF and the (target) AMF determines the I-SMF needs to be changed or removed, the (target) AMF includes a corresponding indication in Namf_Communication_RegistrationStatusUpdate sent to old AMF - Step 17: the (target) AMF contacts the SMF/I-SMF ("cases" below are same as for step 10). For case a), no additional change to step 17 of clause 4.2.2.2.2 is needed for the update of the PDU Session. For case b), the SMF in step 17 of clause 4.2.2.2.2 is changed to I-SMF and in addition, the reference clause 4.2.3.2 is changed to clause 4.23.4.2. If the AMF has changed, the new AMF invokes Nsmf_PDUSession_UpdateSMContext (SM Context ID at SMF) towards the I-SMF. For case c) i.e. for I-SMF removal, the (target) AMF invokes Nsmf_PDUSession_CreateSMContext (SM Context ID at SMF) towards the SMF. Steps from step 10 onwards as described in clause 4.23.4.3 are executed. For cases d) and e), i.e. for I-SMF insertion or change, the (target) AMF invokes Nsmf_PDUSession_CreateSMContext (PDU Session ID, SM Context ID at SMF) towards the new I-SMF. Steps from step 3 onwards as described in clause 4.23.4.3 are executed with the following enhancements:. - Step 9 (for cases d and e): The N2 SM information is only provided by the I-SMF to the AMF when N3 tunnel needs to be established (i.e. due to buffered DL data in old I-SMF/old-I-UPF or AMF has indicated to I-SMF to active user plane for the PDU session based on List of PDU Sessions To Be Activated received from the UE). - Step 16 (i.e. case c): The N2 SM information is only provided by the SMF to the AMF when N3 tunnel need to be established (i.e. due to buffered DL data in old I-SMF/old-I-UPF or the AMF has indicated to the SMF to active user plane for the PDU session based on List of PDU Sessions To Be Activated received from the UE). - Step 17 is executed when N3 tunnel needs to be established. The NAS message Service Accept is replaced with Registration Accept (i.e. step 21 in clause 4.2.2.2). - Step 17a and 17b is triggered by old AMF towards the old I-SMF based on the I-SMF change or removal indication received from target AMF, when the timer (i.e. started in step 5 of clause 4.2.2.2) in old AMF expires. NOTE: Step 17a is executed by old AMF together with steps 14d and 14e in clause 4.2.2.2. - Steps 18 to 21 (i.e. cases d and e) and steps 22 to 25 (i.e. case c): These steps are executed if N2 SM information is provided by the I-SMF/SMF in step 9 or step 16 above. - Step 21: This step is omitted if step 17 of clause 4.23.4.3 is executed as described above. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.23.3 |
2,676 | 5.3.25 Paging Early Indication with Paging Subgrouping Assistance | A UE may indicate its capability to support NR paging subgrouping during registration procedure when the UE: - initiates a registration procedure with 5GS registration type IE not set to "emergency registration"; and - does not have an active emergency PDU session. NOTE: The requirements for UE-ID based PEI are specified in 3GPP TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [27]. If a UE supporting NR paging subgrouping did not indicate its capability to support NR paging subgrouping during the last registration procedure due to an active emergency PDU session over 3GPP access, the UE shall initiate a registration procedure for mobility and periodic registration update procedure to indicate its capability to support NR paging subgrouping after the emergency PDU session is released over 3GPP access. If the UE indicates support of NR paging subgrouping the UE may include its paging probability information in the Requested PEIPS assistance information IE in the REGISTRATION REQUEST message. If the UE indicates support of NR paging subgrouping and the network supports and accepts the use of the PEIPS assistance information for the UE, the network provides to the UE the Negotiated PEIPS assistance information, including the Paging subgroup ID, in the REGISTRATION ACCEPT message or the CONFIGURATION UPDATE COMMAND message. The Paging subgroup ID is used to determine the NR paging subgroup for paging the UE. The UE NAS layer shall indicate the Paging subgroup ID to the access stratum layer. The network shall store the Paging subgroup ID in the 5GMM context of the UE. The UE shall use PEIPS assistance information only if the UE received the Negotiated PEIPS assistance information IE during the last registration procedure. If the UE did not receive the Negotiated PEIPS assistance information IE during the last registration procedure, the UE shall delete any existing PEIPS assistance information received from the network. If the network did not accept the request to use PEIPS assistance information during the registration procedure, the network shall delete the stored PEIPS assistance information for the UE, if available. If the UE supports the use of the PEIPS assistance information and the network supports and accepts the use of the PEIPS assistance information, the network may provide the PEIPS assistance information to the UE by including the Updated PEIPS assistance information IE in the CONFIGURATION UPDATE COMMAND message. When an emergency PDU session is successfully established over 3GPP access after the UE received the Negotiated PEIPS assistance information IE during the last registration procedure, the UE and the AMF shall not use PEIPS assistance information until: - the successful completion of the PDU session release procedure of the emergency PDU; - the UE receives PEIPS assistance information during a registration procedure with PDU session status IE or upon successful completion of a service request procedure, if the UE or the network locally releases the emergency PDU session; - the successful completion of handover of emergency PDU session to non-3GPP access; or - the successful transfer of the emergency PDU session in 5GS to the EPS or ePDG connected to EPC. | 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.25 |
2,677 | 5.5.6.2 Initiation | The UE shall: 1> if and only if upper layers indicate to start performing location measurements towards E-UTRA or NR or start subframe and slot timing detection towards E-UTRA, and the UE requires measurement gaps for these operations while measurement gaps are either not configured or not sufficient: 2> if preconfigured measurement gaps for positioning and posMG-Request are configured and the UE considers that at least one of the preconfigured measurement gaps for positioning is sufficient for the location measurement when activated: 3> trigger the lower layers to initiate the measurement gap activation request using UL MAC CE as specified in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3]; 2> else: 3> initiate the procedure to indicate start as specified in clause 5.5.6.3; NOTE 1: The UE verifies the measurement gap situation only upon receiving the indication from upper layers. If at this point in time sufficient gaps are available, the UE does not initiate the procedure. Unless it receives a new indication from upper layers, the UE is only allowed to further repeat the procedure in the same PCell once per frequency of the target RAT if the provided measurement gaps are insufficient. NOTE 1a: When indication is received from upper layers for performing location measurement and there is pre-configured measurement gap configured (not preconfigured measurement gap for positioning), the UE considers this preconfigured measurement gap to be not sufficient if the measurement gap is not considered to be always activated according to clause 9.1.7.2 of TS 38.133[ NR; Requirements for support of radio resource management ] [14]. 1> if and only if upper layers indicate to stop performing location measurements towards E-UTRA or NR or stop subframe and slot timing detection towards E-UTRA: 2> if there is no activated preconfigured measurement gap for positioning: 3> if there is previously triggered UL MAC CE transmission for the measurement gap activation for positioning: 4> indicate to the lower layers to cancel the triggered UL MAC CE transmission for the measurement gap activation as specified in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3]; 2> else if there is activated preconfigured measurement gap for positioning: 3> trigger the lower layers to deactivate all the activated measurement gap(s) for positioning as specified in TS 38.321[ NR; Medium Access Control (MAC) protocol specification ] [3]. 2> if there is configured measurement gap used for positioning and the measurement gap is not the activated preconfigured measurement gap for positioning: 3> initiate the procedure to indicate stop as specified in 5.5.6.3. NOTE 2: The UE may initiate the procedure to indicate stop even if it did not previously initiate the procedure to indicate start. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.5.6.2 |
2,678 | 5.5.2.2.3 UE initiated combined detach procedure completion | When the DETACH REQUEST message is received by the network, a DETACH ACCEPT message shall be sent to the UE, if the Detach type IE does not indicate "switch off". Otherwise, the procedure is completed when the network receives the DETACH REQUEST message. Depending on the value of the Detach type IE the following applies: - combined EPS/IMSI detach: The network and the UE shall deactivate the EPS bearer context(s) for this UE locally without peer-to-peer signalling between the UE and the MME. The UE is marked as inactive in the network for EPS and for non-EPS services. The states EMM-DEREGISTERED and MM-NULL are entered in both the UE and the network. - IMSI detach: The UE is marked as inactive in the network for non-EPS services. The states MM-NULL and EMM-REGISTERED are entered in both the UE and the network. The UE, when receiving the DETACH ACCEPT message, shall stop timer T3421. | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.5.2.2.3 |
2,679 | 6.8.6.2 GSM security context | A GSM security context in UTRAN is only established for GSM subscribers. At the network side, two cases are distinguished: a) In case of an intersystem change to a GSM BSS controlled by the same SGSN, the SGSN starts to apply the 64-bit GSM cipher key Kc agreed during the latest GSM AKA procedure. b) In case of an intersystem change to a GSM BSS controlled by another SGSN, the initial SGSN sends the 64-bit GSM cipher key Kc agreed during the latest GSM AKA procedure to the (new) SGSN controlling the BSC. The new SGSN stores the key and applies it. The new SGSN becomes the new anchor point for the service. At the user side, in both cases, the ME applies the GSM cipher key Kc received from the SIM during the latest GSM AKA procedure. | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | 6.8.6.2 |
2,680 | 8.2.1.3.3 Minimum Requirement 2 Tx Antenna Port (demodulation subframe overlaps with aggressor cell ABS) | The requirements for non-MBSFN ABS are specified in Table 8.2.1.3.3-2, with the addition of parameters in Table 8.2.1.3.3-1 and the downlink physical channel setup according to Annex C.3.2 and Annex C.3.3. The requirements for MBSFN ABS are specified in Table 8.2.1.3.3-4, with the addition of parameters in Table 8.2.1.3.3-3 and the downlink physical channel setup according to Annex C.3.2 and Annex C.3.3. The purpose is to verify the performance of large delay CDD with 2 transmitter antennas if the PDSCH transmission in the serving cell takes place in subframes that overlap with ABS [9] of the aggressor cell. In Tables 8.2.1.3.3-1 and 8.2.1.3.3-3, Cell 1 is the serving cell, and Cell 2 is the aggressor cell. The downlink physical channel setup for Cell 1 is according to Annex C.3.2 and for Cell 2 is according to Annex C.3.3, respectively. Table 8.2.1.3.3-1: Test Parameters for Large Delay CDD (FRC) – Non-MBSFN ABS Table 8.2.1.3.3-2: Minimum Performance Large Delay CDD (FRC) – Non-MBSFN ABS Table 8.2.1.3.3-3: Test Parameters for Large Delay CDD (FRC) – MBSFN ABS Table 8.2.1.3.3-4: Minimum Performance Large Delay CDD (FRC) – MBSFN ABS | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.2.1.3.3 |
2,681 | 3.1 Measurement family | The measurement names defined in the present document are all beginning with a prefix containing the measurement family name (e.g. RRC.AttConnEstab.Cause). This family name identifies all measurements which relate to a given functionality and it may be used for measurement administration (see TS 32.401[ Telecommunication management;Performance Management (PM);Concept and requirements ] [5]). The list of families currently used in the present document is as follows: - DRB (measurements related to Data Radio Bearer). - RRC (measurements related to Radio Resource Control). - RRU (measurements related to Radio Resource Utilization). - ERAB (measurements related to E-RAB). - HO (measurements related to Handover). - S1SIG (measurements related to S1 Signalling). - SRB (measurements related to Signalling Radio Bearer). - PAG (measurements related to Paging). - EQPT (measurements related to Equipment). - UECNTX (measurements related to UE CONTEXT). - TB (measurements related to Transport Block). - MR (measurements related to Measurement Report). - PEE (measurements related to Power, Energy and Environmental (PEE) parameters). - LWI (measurements related to LTE and WLAN integration, including LWA and LWIP). - ENDC (measurements related to E-UTRA-NR Dual Connectivity). | 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 | 3.1 |
2,682 | 8.132 Secondary RAT Usage Data Report | Secondary RAT Usage Data Report IE is coded as depicted in Figure 8.132-1. Figure 8.132-1: Secondary RAT Usage Data Report The following bits within Octet 5 shall indicate: - Bit 8 to 4 – Spare, for future use and set to zero. - Bit 3 – SRUDN (Secondary RAT Usage Data Report From NG-RAN): This bit indicates the presence of Length of Secondary RAT Data Usage Report Transfer and Secondary RAT Data Usage Report Transfer fields. If it is set to "1", the Length of Secondary RAT Data Usage Report Transfer and Secondary RAT Data Usage Report Transfer field shall be present, and the IRPGW bit shall be set to "1", octet 8 to 31 shall be set to "0"; otherwise, if it is set to "0", the Length of Secondary RAT Data Usage Report Transfer and Secondary RAT Data Usage Report Transfer field shall not be present. - Bit 2 – IRSGW (Intended Receiver SGW): This bit defines if the Usage Data Report shall be used by the SGW or not. If set to 1 the SGW shall store it. If set to zero the SGW shall not store it. - Bit 1 – IRPGW (Intended Receiver PGW): This bit defines if the Usage Data Report shall be sent to the PGW or not. If set to 1 the SGW shall forward it to PGW and PGW shall store it. If set to zero SGW shall not forward it to PGW. Octet 6 represents Secondary RAT Type Secondary RAT Type is coded as depicted in Table 8.132-1. Table 8.132-1: Secondary RAT Type values The EBI field in octet 7 shall contain the value indicating the EPS Bearer ID. The EBI field shall be encoded as the EBI field in the EPS Bearer ID (EBI) IE type (see clause 8.8). Octets 8 to 11 and 12 to 15 shall be encoded in the same format as the first four octets of the 64-bit timestamp format as defined in clause 6 of IETF RFC 5905 [53]. It indicates the UTC time when the recording of the Secondary RAT Usage Data was started and ended. NOTE: The encoding is defined as the time in seconds relative to 00:00:00 on 1 January 1900. Octets 16 to 23 and 24 to 31: The Usage Data UL/DL fields are encoded as octets in binary value. The range of Usage Data UL and Usage Data DL are specified in 3GPP TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [10]. Editors Note: The format and range is subject to be aligned with RAN specification. The timestamp and Usage Data UL and DL are received from relevant S1 messages. The Secondary RAT Data Usage Report Transfer field shall be encoded with the transparent copy of NGAP IE Secondary RAT Data Usage Report Transfer as specified in 3GPP TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [84]. (See also Annex B.3) | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 8.132 |
2,683 | 5.32.6.2.2 MPQUIC Functionality | The MPQUIC functionality enables steering, switching, and splitting of UDP traffic between the UE and UPF, in accordance with the ATSSS policy created by the network. The operation of the MPQUIC functionality is based on RFC 9298 [170] "proxying UDP in HTTP", which specifies how UDP traffic can be transferred between a client (UE) and a proxy (UPF) using the RFC 9114 [171] HTTP/3 protocol. The HTTP/3 protocol operates on top of the QUIC protocol (RFC 9000 [166], RFC 9001 [167] , RFC 9002 [168]), which supports simultaneous communication over multiple paths, as defined in draft-ietf-quic-multipath [174]. The MPQUIC functionality in the UE communicates with the MPQUIC Proxy functionality in the UPF (see Figure 4.2.10-1) using the user plane of the 3GPP access, or the non-3GPP access, or both. The MPQUIC functionality may be enabled for an MA PDU Session with type IPv4, IPv6 or IPv4v6, when both the UE and the network support this functionality. The MPQUIC functionality shall not be enabled when the type of the MA PDU Session is Ethernet. The MPQUIC functionality is composed of three components: 1) QoS flow selection & Steering mode selection: This component in the UE initiates the establishment of one or more multipath QUIC connections, after the establishment of the MA PDU Session and, for each uplink UDP flow, it selects a QoS flow (based on the QoS rules), a steering mode and a transport mode (based on the ATSSS rules). This component in the UPF selects, for each downlink UDP flow, a QoS flow (based on the N4 rules), a steering mode and a transport mode (based on the N4 rules). The supported transport modes are defined below. In the UE, this component is only used in the uplink direction, while, in the UPF, this component is only used in the downlink direction. 2) HTTP/3 layer: Supports the HTTP/3 protocol defined in RFC 9114 [171] and the extensions defined in: - RFC 9298 [170] for supporting UDP proxying over HTTP; - RFC 9297 [172] for supporting HTTP datagrams; and - RFC 9220 [173] for supporting Extended CONNECT. The HTTP/3 layer selects a multipath QUIC connection to be used for each UDP flow and allocates a new QUIC stream on this connection that is associated with the UDP flow. It also configures this QUIC stream to apply a specific steering mode. In the UE, the HTTP/3 layer implements an HTTP/3 client, while, in the UPF, it implements an HTTP/3 proxy. 3) QUIC layer: Supports the QUIC protocol as defined in the applicable IETF specifications (RFC 9000 [166], RFC 9001 [167], RFC 9002 [168]) and the extensions defined in: - RFC 9221 [169] for supporting unreliable datagram transport with QUIC; and - draft-ietf-quic-multipath [174] for supporting QUIC connections using multiple paths simultaneously. When the MPQUIC functionality is applied, the protocol stack of the user plane is depicted in figure below. Figure 5.32.6.2.2-1: UP protocol stack when the MPQUIC functionality is applied Editor's note: The above figure might need changes (e.g. related with the mandatory use of TLS) based on the security work in SA WG3. If the UE indicates that it is capable of supporting the MPQUIC functionality, as described in clause 5.32.2, and the network agrees to enable the MPQUIC functionality for the MA PDU Session then: i) An associated MPQUIC Proxy functionality is enabled in the UPF for the MA PDU Session. ii) The network allocates to UE one IP address/prefix for the MA PDU Session and two additional IP addresses/prefixes, called "MPQUIC link-specific multipath " addresses/prefixes; one associated with 3GPP access and another associated with the non-3GPP access. In the UE, these two IP addresses/prefixes are used only by the MPQUIC functionality. Each "MPQUIC link-specific multipath" address/prefix assigned to UE may not be routable via N6. The MPQUIC functionality in the UE and the MPQUIC Proxy functionality in the UPF shall use the "MPQUIC link-specific multipath" addresses/prefixes for transmitting UDP flows over non-3GPP access and over 3GPP access. The MPQUIC Proxy functionality shall use the IP address/prefix of the MA PDU session for the communication with the final destination. In Figure 5.32.6.1-1, the IP@3 corresponds to the IP address of the MA PDU Session and the IP@4 and IP@5 correspond to the "MPQUIC link-specific multipath" addresses. The following UE IP address management applies: - The MA PDU IP address/prefix shall be provided to the UE via mechanisms defined in clause 5.8.2.2. - The "MPQUIC link-specific multipath" IP addresses/prefixes shall be allocated by the UPF and shall be provided to the UE via SM NAS signalling. NOTE 1: After the MA PDU Session is released, the same UE IP addresses/prefixes are not allocated to another UE for MA PDU Session in a short time. iii) The network shall send MPQUIC proxy information to UE, i.e. one IP address of UPF, one UDP port number and the proxy type (e.g. "connect-udp"). This information is used by the UE for establishing multipath QUIC connections with the UPF, which implements the MPQUIC Proxy functionality. iv) After the MA PDU Session is established, the UE determines the number of multipath QUIC connections to be established with the UPF. The UE determines to establish at least as many multipath QUIC connections as the number of QoS flows of the MA PDU Session, i.e. one multipath QUIC connection per QoS flow. Each multipath QUIC connection carries the UDP traffic mapped to a single QoS flow. For the downlink traffic to which the MPQUIC functionality is to be applied, the QoS rules provided to UE include downlink QoS information and the UE applies the downlink QoS information to establish multipath QUIC connections for the QoS flows used for the downlink traffic only. v) During a QUIC connection establishment, the UE and UPF negotiate QUIC transport parameters and indicate (a) support of QUIC Datagram frames and (b) support of multipath. They indicate support of QUIC Datagram frames by providing the "max_datagram_frame_size" transport parameter with a non-zero value (see RFC 9221 [169]) and they indicate support of multipath by providing the "enable_multipath" transport parameter (see draft-ietf-quic-multipath [174]). In addition, during a QUIC connection establishment the QoS flow associated with this connection is determined. The UE sends all traffic of a QUIC connection over the QoS flow associated with this QUIC connection. This enables the UPF to determine the QoS flow associated with a QUIC connection and to select a QUIC connection for sending the downlink traffic of a QoS flow. vi) After a QUIC connection establishment, the HTTP/3 client in the UE and the HTTP/3 proxy in the UPF negotiate HTTP settings and indicate support of HTTP Datagrams (see RFC 9297 [172]) and support of Extended CONNECT (see RFC 9220 [173]). To use MPQUIC proxying for a UDP traffic flow, the UE then sends a HTTP/3 CONNECT request (see RFC 9298 [170]) to the HTTP/3 proxy in the UPF. vii) The network may indicate to UE the list of applications for which the MPQUIC functionality should be applied. This is achieved by using the Steering Functionality component of an ATSSS rule (see clause 5.32.8). 5.32.6.2.2.1 Supported Transport Modes The MPQUIC functionality supports the following transport modes for transmitting a UDP flow between UE and UPF. The PCF selects which of these transport modes shall be applied for a UDP flow (SDF). The selected transport mode is provided to UE and UPF within the ATSSS rules and N4/MAR rules respectively. - Datagram mode 2: This transport mode is the mode defined in RFC 9298 [170]. It encapsulates UDP packets within QUIC Datagram frames and provides unreliable transport with no sequence numbering and no packet reordering / deduplication. - Datagram mode 1: This transport mode is an extension of the mode defined in RFC 9298 [170]. It encapsulates UDP packets within QUIC Datagram frames and provides unreliable transport but with sequence numbering and with packet reordering / deduplication. It can be applied for any UDP flow. The details of the datagram mode 1, including the potential use of a Context ID (see RFC 9298 [170]), are considered in stage-3 specifications. Editor's note: A reference to the applicable stage-3 specification needs to be added to the above paragraph, to point to the stage-3 details of Datagram mode 1. - Stream mode: This transport mode is readily supported by the QUIC protocol. It encapsulates UDP packets within QUIC Stream frames and provides reliable transport with sequence numbering and with packet reordering / deduplication. It can be applied for UDP flows where it is known that the application does not perform retransmissions. NOTE 1: The Stream mode provides strict reliability and in-order delivery with re-transmissions and therefore can lead to melt down phenomena when reliable traffic (e.g. QUIC) is carried, or counteracts application decisions when UDP is selected to avoid reliability and/or in-order delivery. Therefore, it can be avoided for applications which perform their own reliability mechanisms. NOTE 2: When a steering mode is supported by ATSSS-LL for a UDP flow (e.g. Active-Standby), the MPQUIC steering functionality can be selected if additional features, which are not supported by the ATSSS-LL steering functionality and PMF, are required for the traffic steering/switching/splitting of the UDP flow. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.32.6.2.2 |
2,684 | 9.9.3.37A Extended emergency number list | The purpose of this information element is to encode one or more local emergency number(s) together with a sub-services field containing zero or more sub-services of the associated emergency service URN and a validity indication. An emergency service URN is a service URN with top level service type of "sos" as specified in IETF RFC 5031 [55]. EXAMPLE 1: If the associated emergency service URN is "urn:service:sos.gas", there is only one sub-service provided in the sub-services field which is "gas". EXAMPLE 2: If the associated emergency service URN is "urn:service:sos", there is no sub-services provided in the sub-services field and the length of the sub-services field is "0". NOTE: The associated emergency service URN can be a country-specific emergency service URN as defined in 3GPP TS 24.229[ IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 ] [13D]. The Extended emergency number list information element is coded as shown in figure 9.9.3.37A.1 and table 9.9.3.37A.1. The Extended emergency number list IE is a type 6 information element with a minimum length of 7 octets and a maximum length of 65538 octets. NOTE 1: The length shall contain the number of octets used to encode the number digits. NOTE 2: The number digit(s) in octet 6 precedes the digit(s) in octet 7 etc. The number digit, which would be entered first, is located in octet 6, bits 1 to 4. The contents of the number digits are coded as shown in table 10.5.118/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [13]. NOTE 3: If the emergency number contains an odd number of digits, bits 5 to 8 of the last octet of the respective emergency number shall be filled with an end mark coded as "1111". NOTE 4: The length shall contain the number of octets used to encode the sub-services field. NOTE 5: The characters of the sub-services of the associated emergency service URN shall be coded in accordance to GSM 7 bit default alphabet and the appropriate padding characters and bit-fill are added to octet boundary as specified in clause 6.1.2.3.1 of 3GPP TS 23.038[ Alphabets and language-specific information ] [3]and the first character starts in octet j+1, l+1 or n+1. Figure 9.9.3.37A.1 Extended Emergency Number List IE EXAMPLE 3: If the associated emergency service URN is "urn:service:sos.police.municipal", the sub-services field contains "police.municipal" and the first character is "p". Table 9.9.3.37A.1: Extended Emergency Number List Validity information IE | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.9.3.37A |
2,685 | 5.4.6 Core Network assistance information for RAN optimization 5.4.6.1 General | Core Network assistance information for RAN aids the RAN to optimize the UE state transition steering and the RAN paging strategy formulation in RRC_INACTIVE state. The Core Network assistance information includes the information set, Core Network assisted RAN parameters tuning, which assist RAN optimize the UE RRC state transition and CM state transition decision. It also includes the information set, Core Network assisted RAN paging information, which assist RAN to formulate an optimized paging strategy when RAN paging is triggered. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.4.6 |
2,686 | 16.7.4 Access Control | During the establishment of the UE-associated logical NG-connection towards the 5GC, the AMF checks whether the UE is allowed to access the cell as specified in TS 23.501[ System architecture for the 5G System (5GS) ] [3]. If the check is successful, the AMF sets up the UE-associated logical NG-connection and provides the NG-RAN node with the list of CAGs allowed for the UE and, whether the UE is allowed to access non-CAG cells. This information is used by the NG-RAN for access control of subsequent mobility. If the check is not successful, the AMF shall reject setting up the UE-associated NG connection and inform the NG-RAN node with an appropriate cause value as specified 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.7.4 |
2,687 | 24.3 ProSe Application Code 24.3.1 General | The ProSe Application Code as described in 3GPP TS 23.303[ Proximity-based services (ProSe); Stage 2 ] [103] is composed of the following two parts: - The PLMN ID of the ProSe Function that assigned the ProSe Application Code, i.e. Mobile Country Code (MCC) and Mobile Network Code (MNC). - A temporary identity that corresponds to the ProSe Application ID Name. The temporary identity is allocated by the ProSe Function and it may contain a metadata index. The internal structure of the temporary identity is not specified in 3GPP. The ProSe Application Code shall have a fixed length of 184 bits. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 24.3 |
2,688 | 9.2.1.1 Cell Selection | The principles of PLMN selection in NR are based on the 3GPP PLMN selection principles. Cell selection is required on transition from RM-DEREGISTERED to RM-REGISTERED, from CM-IDLE to CM-CONNECTED and from CM-CONNECTED to CM-IDLE and is based on the following principles: - The UE NAS layer identifies a selected PLMN and equivalent PLMNs; - Cell selection is always based on CD-SSBs located on the synchronization raster (see clause 5.2.4): - The UE searches the NR frequency bands and for each carrier frequency identifies the strongest cell as per the CD-SSB. It then reads cell system information broadcast to identify its PLMN(s): - The UE may search each carrier in turn ("initial cell selection") or make use of stored information to shorten the search ("stored information cell selection"). - The UE seeks to identify a suitable cell; if it is not able to identify a suitable cell it seeks to identify an acceptable cell. When a suitable cell is found or if only an acceptable cell is found it camps on that cell and commence the cell reselection procedure: - A suitable cell is one for which the measured cell attributes satisfy the cell selection criteria; the cell PLMN is the selected PLMN, registered or an equivalent PLMN; the cell is not barred or reserved and the cell is not part of a tracking area which is in the list of "forbidden tracking areas for roaming"; - An acceptable cell is one for which the measured cell attributes satisfy the cell selection criteria and the cell is not barred. - The IAB-MT and NCR-MT apply the cell selection procedure as described for the UE with the following differences: - The IAB-MT and NCR-MT ignore cell-barring or cell-reservation indications contained in cell system information broadcast; - The IAB-MT only considers a cell as a candidate for cell selection if the cell system information broadcast indicates IAB support for the selected PLMN or the selected SNPN, and the NCR-MT only considers a cell as a candidate for cell selection if the cell system information broadcast indicates Network-Controlled Repeater support. - The mobile IAB-MT applies the cell selection procedure as described for the IAB-MT with the following differences: - The mobile IAB-MT only considers a cell as a candidate cell for cell selection if the cell system information broadcast indicates mobile IAB support. Transition to RRC_IDLE: On transition from RRC_CONNECTED or RRC_INACTIVE to RRC_IDLE, a UE should camp on a cell as result of cell selection according to the frequency be assigned by RRC in the state transition message if any. Recovery from out of coverage: The UE should attempt to find a suitable cell in the manner described for stored information or initial cell selection above. If no suitable cell is found on any frequency or RAT, the UE should attempt to find an acceptable cell. In multi-beam operations, the cell quality is derived amongst the beams corresponding to the same cell (see clause 9.2.4). | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 9.2.1.1 |
2,689 | – TDD-UL-DL-ConfigDedicated | The IE TDD-UL-DL-ConfigDedicated determines the UE-specific Uplink/Downlink TDD configuration. TDD-UL-DL-ConfigDedicated information element -- ASN1START -- TAG-TDD-UL-DL-CONFIGDEDICATED-START TDD-UL-DL-ConfigDedicated ::= SEQUENCE { slotSpecificConfigurationsToAddModList SEQUENCE (SIZE (1..maxNrofSlots)) OF TDD-UL-DL-SlotConfig OPTIONAL, -- Need N slotSpecificConfigurationsToReleaseList SEQUENCE (SIZE (1..maxNrofSlots)) OF TDD-UL-DL-SlotIndex OPTIONAL, -- Need N ... } TDD-UL-DL-ConfigDedicated-IAB-MT-r16::= SEQUENCE { slotSpecificConfigurationsToAddModList-IAB-MT-r16 SEQUENCE (SIZE (1..maxNrofSlots)) OF TDD-UL-DL-SlotConfig-IAB-MT-r16 OPTIONAL, -- Need N slotSpecificConfigurationsToReleaseList-IAB-MT-r16 SEQUENCE (SIZE (1..maxNrofSlots)) OF TDD-UL-DL-SlotIndex OPTIONAL, -- Need N ... } TDD-UL-DL-SlotConfig ::= SEQUENCE { slotIndex TDD-UL-DL-SlotIndex, symbols CHOICE { allDownlink NULL, allUplink NULL, explicit SEQUENCE { nrofDownlinkSymbols INTEGER (1..maxNrofSymbols-1) OPTIONAL, -- Need S nrofUplinkSymbols INTEGER (1..maxNrofSymbols-1) OPTIONAL -- Need S } } } TDD-UL-DL-SlotConfig-IAB-MT-r16::= SEQUENCE { slotIndex-r16 TDD-UL-DL-SlotIndex, symbols-IAB-MT-r16 CHOICE { allDownlink-r16 NULL, allUplink-r16 NULL, explicit-r16 SEQUENCE { nrofDownlinkSymbols-r16 INTEGER (1..maxNrofSymbols-1) OPTIONAL, -- Need S nrofUplinkSymbols-r16 INTEGER (1..maxNrofSymbols-1) OPTIONAL -- Need S }, explicit-IAB-MT-r16 SEQUENCE { nrofDownlinkSymbols-r16 INTEGER (1..maxNrofSymbols-1) OPTIONAL, -- Need S nrofUplinkSymbols-r16 INTEGER (1..maxNrofSymbols-1) OPTIONAL -- Need S } } } TDD-UL-DL-SlotIndex ::= INTEGER (0..maxNrofSlots-1) -- TAG-TDD-UL-DL-CONFIGDEDICATED-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
2,690 | 5.7.4.2 Initiation | A UE capable of providing delay budget report in RRC_CONNECTED may initiate the procedure in several cases, including upon being configured to provide delay budget report and upon change of delay budget preference. A UE capable of providing overheating assistance information in RRC_CONNECTED may initiate the procedure if it was configured to do so, upon detecting internal overheating, or upon detecting that it is no longer experiencing an overheating condition. A UE capable of providing IDC assistance information in RRC_CONNECTED may initiate the procedure if it was configured to do so, upon detecting IDC problem if the UE did not transmit an IDC assistance information since it was configured to provide IDC indications, or upon change of IDC problem information. A UE capable of providing its preference on DRX parameters of a cell group for power saving in RRC_CONNECTED may initiate the procedure in several cases, if it was configured to do so, including upon having a preference on DRX parameters and upon change of its preference on DRX parameters. A UE capable of providing its preference on the maximum aggregated bandwidth of a cell group for power saving in RRC_CONNECTED may initiate the procedure in several cases, if it was configured to do so, including upon having a maximum aggregated bandwidth preference and upon change of its maximum aggregated bandwidth preference. A UE capable of providing its preference on the maximum number of secondary component carriers of a cell group for power saving in RRC_CONNECTED may initiate the procedure in several cases, if it was configured to do so, including upon having a maximum number of secondary component carriers preference and upon change of its maximum number of secondary component carriers preference. A UE capable of providing its preference on the maximum number of MIMO layers of a cell group for power saving in RRC_CONNECTED may initiate the procedure in several cases, if it was configured to do so, including upon having a maximum number of MIMO layers preference and upon change of its maximum number of MIMO layers preference. A UE capable of providing its preference on the minimum scheduling offset for cross-slot scheduling of a cell group for power saving in RRC_CONNECTED may initiate the procedure in several cases, if it was configured to do so, including upon having a minimum scheduling offset preference and upon change of its minimum scheduling offset preference. A UE capable of providing assistance information to transition out of RRC_CONNECTED state may initiate the procedure if it was configured to do so, upon determining that it prefers to transition out of RRC_CONNECTED state, or upon change of its preferred RRC state. A UE capable of providing configured grant assistance information for NR sidelink communication in RRC_CONNECTED may initiate the procedure in several cases, including upon being configured to provide traffic pattern information and upon change of traffic patterns. A UE capable of providing an indication of its preference in being provisioned with reference time information may initiate the procedure upon being configured to provide this indication, or if it was configured to provide this indication and upon change of its preference. A UE capable of providing an indication of its preference in FR2 UL gap may initiate the procedure if it was configured to do so, upon detecting the need of FR2 UL gap activation/deactivation. A UE capable of providing MUSIM assistance information for gap preference may initiate the procedure if it was configured to do so, upon determining it needs the gaps, or upon change of the gap preference information. A UE capable of providing MUSIM assistance information for gap priority preference may initiate the procedure if it was configured to do so, upon determining it has gap priority preference information. A UE capable of providing MUSIM assistance information for leave indication may initiate the procedure if it was configured to do so upon determining that it needs to leave RRC_CONNECTED state. A UE capable of providing MUSIM assistance information for temporary capability restriction may initiate the procedure if it was configured to do so, upon determining it has temporary capability restriction or upon determining the removal of the capability restriction. A UE capable of relaxing its RLM measurements of a cell group in RRC_CONNECTED state shall initiate the procedure for providing an indication of its relaxation state for RLM measurements upon being configured to do so, and upon change of its relaxation state for RLM measurements in RRC_CONNECTED state. A UE capable of relaxing its BFD measurements in serving cells of a cell group in RRC_CONNECTED shall initiate the procedure for providing an indication of its relaxation state for BFD measurements upon being configured to do so, and upon change of its relaxation state for BFD measurements in RRC_CONNECTED state. A UE capable of SDT initiates this procedure when data and/or signalling mapped to radio bearers that are not configured for SDT becomes available during SDT (i.e. while SDT procedure is ongoing). A UE capable of providing its preference for SCG deactivation may initiate the procedure if it was configured to do so, upon determining that it prefers or does no more prefer the SCG to be deactivated. A UE that has uplink data to transmit for a DRB for which there is no MCG RLC bearer while the SCG is deactivated shall initiate the procedure. A UE capable of providing an indication of fulfilment of the RRM measurement relaxation criterion in connected mode may initiate the procedure if it was configured to do so, upon change of its fulfilment status for RRM measurement relaxation criterion for connected mode. A UE capable of providing service link propagation delay difference between serving cell and neighbour cell(s) shall initiate the procedure upon being configured to do so, and upon determining that service link propagation delay difference between serving cell and a neighbour cell has changed more than threshPropDelayDiff compared with the last reported value. A UE capable of providing an indication of its preference on multi-Rx operation for FR2 may initiate the procedure if it was configured to do so, upon detecting having a preference on multi-Rx operation for FR2 and upon change of its preference on multi-Rx operation for FR2. A UE capable of indicating the availability of flight path information may initiate the procedure, if it was configured to do so, upon determining that an initial or updated flight path information is available. A UE capable of providing UL traffic information shall initiate the procedure when the information is available upon being configured to do so, and upon change of UL traffic information. A UE capable of N3C remote UE operation initiates the procedure upon being configured to report relay UE information on the available non-3GPP connection(s), and upon change of its available non-3GPP connection(s). A UE capable of providing configured grant assistance information including SL-PRS transmission periodicity and priority for NR sidelink positioning in RRC_CONNECTED may initiate the procedure. Editor's Note: FFS the details of configured grant assistance information. Upon initiating the procedure, the UE shall: 1> if configured to provide delay budget report: 2> if the UE did not transmit a UEAssistanceInformation message with delayBudgetReport since it was configured to provide delay budget report; or 2> if the current delay budget is different from the one indicated in the last transmission of the UEAssistanceInformation message including delayBudgetReport and timer T342 is not running: 3> start or restart timer T342 with the timer value set to the delayBudgetReportingProhibitTimer; 3> initiate transmission of the UEAssistanceInformation message in accordance with 5.7.4.3 to provide a delay budget report; 1> if configured to provide overheating assistance information: 2> if the overheating condition has been detected and T345 is not running; or 2> if the current overheating assistance information is different from the one indicated in the last transmission of the UEAssistanceInformation message including overheatingAssistance and timer T345 is not running: 3> start timer T345 with the timer value set to the overheatingIndicationProhibitTimer; 3> initiate transmission of the UEAssistanceInformation message in accordance with 5.7.4.3 to provide overheating assistance information; 1> if configured to provide IDC assistance information based on candidateServingFreqListNR included in idc-AssistanceConfig of a cell group: 2> if the UE did not transmit a UEAssistanceInformation message with idc-Assistance since it was configured to provide IDC assistance information: 3> if on one or more frequencies included in candidateServingFreqListNR, the UE is experiencing IDC problems that it cannot solve by itself; or 3> if on one or more supported UL CA or NR-DC combination comprising of carrier frequencies included in candidateServingFreqListNR, the UE is experiencing IDC problems that it cannot solve by itself: 4> initiate transmission of the UEAssistanceInformation message in accordance with 5.7.4.3 to provide IDC assistance information; 2> else if the current idc-Assistance information for the cell group is different from the one indicated in the last transmission of the UEAssistanceInformation message: 3> initiate transmission of the UEAssistanceInformation message in accordance with 5.7.4.3 to provide IDC assistance information; 1> if configured to provide IDC assistance information based on idc-FDM-AssistanceConfig included in idc-AssistanceConfig of a cell group: 2> if the UE did not transmit a UEAssistanceInformation message with idc-FDM-Assistance since it was configured to provide IDC assistance information: 3> if on one or more frequency ranges included in candidateServingFreqRangeListNR, the UE is experiencing IDC problems that it cannot solve by itself; or 3> if on one or more supported UL CA or NR-DC combination comprising of frequency ranges included in candidateServingFreqRangeListNR, the UE is experiencing IDC problems that it cannot solve by itself: 4> initiate transmission of the UEAssistanceInformation message in accordance with 5.7.4.3 to provide IDC assistance information; 2> else if the current idc-FDM-Assistance information for the cell group is different from the one indicated in the last transmission of the UEAssistanceInformation message: 3> initiate transmission of the UEAssistanceInformation message in accordance with 5.7.4.3 to provide IDC assistance information; 1> if configured to provide IDC assistance information based on idc-TDM-AssistanceConfig included in idc-AssistanceConfig of a cell group: 2> if the UE did not transmit a UEAssistanceInformation message with idc-TDM-Assistance since it was configured to provide IDC assistance information: 3> if on one or more frequencies included in candidateServingFreqListNR or frequency ranges included in candidateServingFreqRangeListNR, the UE is experiencing IDC problems that it cannot solve by itself; or 3> if on one or more supported UL CA or NR-DC combination comprising of carrier frequencies included in candidateServingFreqListNR or frequency ranges included in candidateServingFreqRangeListNR, the UE is experiencing IDC problems that it cannot solve by itself: 4> initiate transmission of the UEAssistanceInformation message in accordance with 5.7.4.3 to provide IDC assistance information; 2> else if the current idc-TDM-Assistance information for the cell group is different from the one indicated in the last transmission of the UEAssistanceInformation message: 3> initiate transmission of the UEAssistanceInformation message in accordance with 5.7.4.3 to provide IDC assistance information; NOTE 1: The term "IDC problems" refers to interference issues applicable across several subframes/slots where not necessarily all the subframes/slots are affected. NOTE 2: For the frequencies on which a serving cell or serving cells is configured that is activated, IDC problems consist of interference issues that the UE cannot solve by itself, during either active data exchange or upcoming data activity which is expected in up to a few hundred milliseconds. For frequencies on which a SCell or SCells is configured that is deactivated, reporting IDC problems indicates an anticipation that the activation of the SCell or SCells would result in interference issues that the UE would not be able to solve by itself. For a non-serving frequency, reporting IDC problems indicates an anticipation that if the non-serving frequency or frequencies became a serving frequency or serving frequencies then this would result in interference issues that the UE would not be able to solve by itself. 1> if configured to provide its preference on DRX parameters of a cell group for power saving: 2> if the UE has a preference on DRX parameters of the cell group and the UE did not transmit a UEAssistanceInformation message with drx-Preference for the cell group since it was configured to provide its preference on DRX parameters of the cell group for power saving; or 2> if the current drx-Preference information for the cell group is different from the one indicated in the last transmission of the UEAssistanceInformation message including drx-Preference for the cell group and timer T346a associated with the cell group is not running: 3> start the timer T346a with the timer value set to the drx-PreferenceProhibitTimer of the cell group; 3> initiate transmission of the UEAssistanceInformation message in accordance with 5.7.4.3 to provide the current drx-Preference; 1> if configured to provide its preference on the maximum aggregated bandwidth of a cell group for power saving: 2> if the UE has a preference on the maximum aggregated bandwidth of the cell group and the UE did not transmit a UEAssistanceInformation message with maxBW-Preference and/or maxBW-PreferenceFR2-2 for the cell group since it was configured to provide its preference on the maximum aggregated bandwidth of the cell group for power saving; or 2> if the current maxBW-Preference information for the cell group is different from the one indicated in the last transmission of the UEAssistanceInformation message including maxBW-Preference and/or maxBW-PreferenceFR2-2for the cell group and timer T346b associated with the cell group is not running: 3> start the timer T346b with the timer value set to the maxBW-PreferenceProhibitTimer of the cell group; 3> initiate transmission of the UEAssistanceInformation message in accordance with 5.7.4.3 to provide the current maxBW-Preference and/or maxBW-PreferenceFR2-2; 1> if configured to provide its preference on the maximum number of secondary component carriers of a cell group for power saving: 2> if the UE has a preference on the maximum number of secondary component carriers of the cell group and the UE did not transmit a UEAssistanceInformation message with maxCC-Preference for the cell group since it was configured to provide its preference on the maximum number of secondary component carriers of the cell group for power saving; or 2> if the current maxCC-Preference information for the cell group is different from the one indicated in the last transmission of the UEAssistanceInformation message including maxCC-Preference for the cell group and timer T346c associated with the cell group is not running: 3> start the timer T346c with the timer value set to the maxCC-PreferenceProhibitTimer of the cell group; 3> initiate transmission of the UEAssistanceInformation message in accordance with 5.7.4.3 to provide the current maxCC-Preference; 1> if configured to provide its preference on the maximum number of MIMO layers of a cell group for power saving: 2> if the UE has a preference on the maximum number of MIMO layers of the cell group and the UE did not transmit a UEAssistanceInformation message with maxMIMO-LayerPreference and/or maxMIMO-LayerPreferenceFR2-2 for the cell group since it was configured to provide its preference on the maximum number of MIMO layers of the cell group for power saving; or 2> if the current maxMIMO-LayerPreference information for the cell group is different from the one indicated in the last transmission of the UEAssistanceInformation message including maxMIMO-LayerPreference and/or maxMIMO-LayerPreferenceFR2-2 for the cell group and timer T346d associated with the cell group is not running: 3> start the timer T346d with the timer value set to the maxMIMO-LayerPreferenceProhibitTimer of the cell group; 3> initiate transmission of the UEAssistanceInformation message in accordance with 5.7.4.3 to provide the current maxMIMO-LayerPreference and/or maxMIMO-LayerPreferenceFR2-2; 1> if configured to provide its preference on the minimum scheduling offset for cross-slot scheduling of a cell group for power saving: 2> if the UE has a preference on the minimum scheduling offset for cross-slot scheduling of the cell group and the UE did not transmit a UEAssistanceInformation message with minSchedulingOffsetPreference and/or minSchedulingOffsetPreferenceExt for the cell group since it was configured to provide its preference on the minimum scheduling offset for cross-slot scheduling of the cell group for power saving; or 2> if the current minSchedulingOffsetPreference and/or minSchedulingOffsetPreferenceExt information for the cell group is different from the one indicated in the last transmission of the UEAssistanceInformation message including minSchedulingOffsetPreference and/or minSchedulingOffsetPreferenceExt for the cell group and timer T346e associated with the cell group is not running: 3> start the timer T346e with the timer value set to the minSchedulingOffsetPreferenceProhibitTimer of the cell group; 3> initiate transmission of the UEAssistanceInformation message in accordance with 5.7.4.3 to provide the current minSchedulingOffsetPreference and/or minSchedulingOffsetPreferenceExt; 1> if configured to provide its release preference and timer T346f is not running: 2> if the UE determines that it would prefer to transition out of RRC_CONNECTED state; or 2> if the UE is configured with connectedReporting and the UE determines that it would prefer to revert an earlier indication to transition out of RRC_CONNECTED state: 3> start timer T346f with the timer value set to the releasePreferenceProhibitTimer; 3> initiate transmission of the UEAssistanceInformation message in accordance with 5.7.4.3 to provide the release preference; 1> if configured to provide configured grant assistance information for NR sidelink communication: 2> initiate transmission of the UEAssistanceInformation message in accordance with 5.7.4.3 to provide configured grant assistance information for NR sidelink communication; 1> if configured to provide preference in being provisioned with reference time information: 2> if the UE did not transmit a UEAssistanceInformation message with referenceTimeInfoPreference since it was configured to provide preference; or 2> if the UE's preference changed from the last time UE initiated transmission of the UEAssistanceInformation message including referenceTimeInfoPreference: 3> initiate transmission of the UEAssistanceInformation message in accordance with 5.7.4.3 to provide preference in being provisioned with reference time information. 1> if configured to provide its preference on FR2 UL gap: 2> if the UE did not transmit a UEAssistanceInformation message with ul-GapFR2-Preference since it was configured to provide its preference on FR2 UL gap information: 3> if the UE has a preference on FR2 UL gap activation/deactivation: 4> initiate transmission of the UEAssistanceInformation message in accordance with 5.7.4.3 to provide FR2 UL gap preference; 2> else if the current FR2 UL gap preference is different from the one indicated in the last transmission of the UEAssistanceInformation message: 3> initiate transmission of the UEAssistanceInformation message in accordance with 5.7.4.3 to provide FR2 UL gap preference. 1> if configured to provide MUSIM assistance information for leaving RRC_CONNECTED: 2> if the UE needs to leave RRC_CONNECTED state and the timer T346g is not running: 3> initiate transmission of the UEAssistanceInformation message in accordance with 5.7.4.3 to provide MUSIM assistance information for leaving RRC_CONNECTED; 3> start the timer T346g with the timer value set to the musim-LeaveWithoutResponseTimer; 1> if configured to provide MUSIM assistance information for gap preference: 2> if the UE has a preference on the MUSIM gap(s) and the UE did not transmit a UEAssistanceInformation message with musim-GapPreferenceList since it was configured to provide MUSIM assistance information for gap preference; or 2> if the current musim-GapPreferenceList is different from the one indicated in the last transmission of the UEAssistanceInformation message including musim-GapPreferenceList and the timer T346h is not running: 3> initiate transmission of the UEAssistanceInformation message in accordance with 5.7.4.3 to provide the current musim-GapPreferenceList; 3> start or restart the timer T346h with the timer value set to the musim-GapProhibitTimer. NOTE 3: The UE does not need to initiate transmission of the UEAssistanceInformation message if the difference between the current musim-GapPreferenceList and the last transmission of the UEAssistanceInformation message including musim-GapPreferenceList is only due to removal of an ended aperiodic gap. 1> if configured to provide MUSIM assistance information for gap priority preference: 2> if the UE has a preference on the MUSIM gap(s) priority and the UE did not transmit a UEAssistanceInformation message with musim-GapPriorityPreferenceList since it was configured to provide MUSIM assistance information for gap priority preference; or 2> if the current musim-GapPriorityPreferenceList is different from the one indicated in the last transmission of the UEAssistanceInformation message including musim-GapPriorityPreferenceList and the timer T346h is not running: 3> initiate transmission of the UEAssistanceInformation message in accordance with 5.7.4.3 to provide the musim-GapPriorityPreferenceList; 3> start or restart the timer T346h with the timer value set to the musim-GapProhibitTimer. 1> if configured to provide MUSIM assistance information for temporary capability restriction: 2> if the UE has temporary capability restriction on the current configuration and timer T348 is not running: 3> initiate transmission of the UEAssistanceInformation message in accordance with 5.7.4.3 to provide the current musim-Cell-SCG-ToRelease and/or musim-CellToAffectList; 3> start the timer T348 with the timer value set to the musim-WaitTimer. 2> if the UE has temporary capability restriction on the current band(s) or combination(s) of bands and the UE did not transmit a UEAssistanceInformation message with musim-AffectedBandsList and/or musim-AvoidedBandsList since it was configured to provide MUSIM assistance information for temporary capability restriction; or 2> if the current musim-AffectedBandsList and/or musim-AvoidedBandsList is different from the one indicated in the last transmission of the UEAssistanceInformation message including musim-CapRestriction and timer T346n is not running: 3> initiate transmission of the UEAssistanceInformation message in accordance with 5.7.4.3 to provide the current musim-AffectedBandsList and/or musim-AvoidedBandsList; 3> start the timer T346n with the timer value set to the musim-ProhibitTimer. 2> if the UE has a preference on the measurement gap requirement information and the UE did not transmit a UEAssistanceInformation message with measurement gap requirement information or RRCReconfigurationComplete message or RRCResumeComplete message with measurement gap requirement information since it was configured to provide its preference on the measurement gap requirement information for MUSIM; or 2> if the current musim-NeedForGapsInfoNR is different from the one indicated in the last transmission of the UEAssistanceInformation message or RRCReconfigurationComplete message or RRCResumeComplete message including musim-CapRestriction to provide the needForGapsInfoNR for the measurement gap requirement of NR target bands: 3> initiate transmission of the UEAssistanceInformation message in accordance with 5.7.4.3 to provide the current musim-NeedForGapsInfoNR; Editor's Note: FFS whether UE should start a timer, e.g., Timer T348. 1> if configured to provide the relaxation state of RLM measurements of a cell group and RLM measurement of the cell group is not stopped: 2> if the UE did not transmit a UEAssistanceInformation message with rlm-MeasRelaxationState since it was configured to provide the relaxation state of RLM measurements for the cell group; or 2> if the relaxation state of RLM measurements for the cell group is currently different from the relaxation state reported in the last transmission of the UEAssistanceInformation message including rlm-MeasRelaxationState of the cell group and timer T346j associated with the cell group is not running: 3> start timer T346j with the timer value set to the rlm-RelaxtionReportingProhibitTimer; 3> initiate transmission of the UEAssistanceInformation message in accordance with 5.7.4.3 to provide the relaxation state of RLM measurements of the cell group; 1> if configured to provide the relaxation state of BFD measurements of serving cells of a cell group and BFD measurement of the cell group is not stopped: 2> if the UE did not transmit a UEAssistanceInformation message with bfd-MeasRelaxationState since it was configured to provide the relaxation state of BFD measurements for the cell group; or 2> if the relaxation state of BFD measurements in any serving cell of the cell group is currently different from the relaxation state reported in the last transmission of the UEAssistanceInformation message including bfd-MeasRelaxationState of the cell group and timer T346k associated with the cell group is not running: 3> start timer T346k with the timer value set to the bfd-RelaxtionReportingProhibitTimer; 3> initiate transmission of the UEAssistanceInformation message in accordance with 5.7.4.3 to provide the relaxation state of BFD measurements of serving cells of the cell group. 1> if data and/or signalling mapped to radio bearers not configured for SDT becomes available during SDT (i.e. while SDT procedure is ongoing): 2> if the UE did not transmit a UEAssistanceInformation message with nonSDT-DataIndication since the initiation of the current resume procedure for SDT: 3> initiate transmission of the UEAssistanceInformation message in accordance with 5.7.4.3 to provide nonSDT-DataIndication. 1> if configured to provide its preference for SCG deactivation and timer T346i is not running; 2> if the UE prefers the SCG to be deactivated and did not transmit a UEAssistanceInformation message with scg-DeactivationPreference since it was configured to provide its SCG deactivation preference; or 2> if the UE preference for SCG deactivation is different from the last indicated scg-DeactivationPreference: 3> start timer T346i with the timer value set to the scg-DeactivationPreferenceProhibitTimer; 3> initiate transmission of the UEAssistanceInformation message in accordance with 5.7.4.3 to provide the UE preference for SCG deactivation; 1> if the SCG is deactivated, and, 1> the UE has uplink data to send for an SCG RLC entity while the UE previously did not have any uplink data to send for any SCG RLC entity: 2> initiate transmission of the UEAssistanceInformation message in accordance with 5.7.4.3 to indicate that the UE has uplink data to send for a DRB whose DRB-Identity is not included in any RLC-BearerConfig in the CellGroupConfig associated with the MCG. 1> if configured to send indications of RRM measurement relaxation criterion fulfilment: 2> if the criterion in 5.7.4.4 is met for a period of TSearchDeltaP-StationaryConnected: 3> if the UE did not transmit a UEAssistanceInformation message with rrm-MeasRelaxationFulfilment as true since it was configured to provide indications of RRM measurement relaxation criterion fulfilment; or 3> the last UEAssistanceInformation message indicated the criterion in 5.7.4.4 is not fulfilled with rrm-MeasRelaxationFulfilment as false: 4> initiate transmission of the UEAssistanceInformation message in accordance with 5.7.4.3 to indicate that the criterion for RRM measurement relaxation for connected mode is fulfilled; 2> else: 3> if the last UEAssistanceInformation message indicated fulfilment of the criterion in 5.7.4.4 with rrm-MeasRelaxationFulfilment as true: 4> initiate transmission of the UEAssistanceInformation message in accordance with 5.7.4.3 to indicate that the criterion for RRM measurement relaxation for connected mode is not fulfilled. 1> if configured to provide service link propagation delay difference between serving cell and neighbour cell(s); 2> if the UE did not transmit a UEAssistanceInformation message with propagationDelayDifference since it was configured to provide service link propagation delay difference between serving cell and neighbour cell(s); or 2> for any neighbour cell in neighCellInfoList, if the service link propagation delay difference between serving cell and the neighbour cell has changed more than threshPropDelayDiff since the last transmission of the UEAssistanceInformation message including propagationDelayDifference: 3> initiate transmission of the UEAssistanceInformation message in accordance with 5.7.4.3 to provide service link propagation delay difference between serving cell and each neighbour cell included in the neighCellInfoList; 1> if configured to provide its preference for multi-Rx operation and timer T440 is not running; 2> if the UE has a preference on multi-Rx operation for FR2 and did not transmit a UEAssistanceInformation message with multiRx-PreferenceFR2 since it was configured to provide its preference on multi-Rx operation; or 2> if the UE has a different preference on multi-Rx operation for FR2 from the last indicated multiRx-PreferenceFR2: 3> start timer T440 with the timer value set to the multiRx-PreferenceReportingConfigFR2ProhibitTimer; 3> initiate transmission of the UEAssistanceInformation message in accordance with 5.7.4.3 to provide the UE preference for multi-Rx operation for FR2. 1> if configured to indicate the availability of flight path information and the UE has flight path information available: 2> if the UE had not previously provided a flight path information since last entering RRC_CONNECTED state; or 2> if at least one waypoint was not previously provided; or 2> if at least one upcoming waypoint that was previously provided is being removed; or 2> if flightPathUpdateDistanceThr is configured and for at least one waypoint, the 3D distance between the previously provided location and the new location is more than or equal to the distance threshold configured by flightPathUpdateDistanceThr; or 2> if flightPathUpdateTimeThr is configured and for at least one waypoint, the timestamp was not previously provided but is now available, or the time between the previously provided timestamp and the new timestamp, if available, is more than or equal to the time threshold configured by flightPathUpdateTimeThr: 3> initiate transmission of the UEAssistanceInformation message in accordance with 5.7.4.3 to indicate the availability of flight path information; NOTE 4: If neither flightPathUpdateDistanceThr nor flightPathUpdateTimeThr is configured, it is up to UE implementation whether to initiate transmission of the UEAssistanceInformation message when updated flight path information is available. 1> if configured to provide UL traffic information: 2> if the UE did not transmit a UEAssistanceInformation message with ul-TrafficInfo since it was configured to provide UL traffic information; or 2> if UL traffic information included in the previous UEAssistanceInformation has changed since the last transmission of the UEAssistanceInformation message containing ul-TrafficInfo for at least one QoS flow for which timer T346x is not running: 3> initiate transmission of the UEAssistanceInformation message in accordance with 5.7.4.3 to provide UL traffic information. NOTE 5: The UE only considers burstArrivalTime to have changed when it changes relative to the periodicity of the Data Burst arrival. 1> if configured to report relay UE information with non-3GPP connection(s); 2> if the UE did not transmit a UEAssistanceInformation message with n3c-relayUE-InfoList since it was configured to report available relay UE information with non-3GPP connection(s); or 2> if the UE has new available non-3GPP conection(s); or 2> if the non-3GPP connection(s) with the reported relay UE(s) is not available: 3> initiate transmission of the UEAssistanceInformation message in accordance with 5.7.4.3 to report relay UE information with non-3GPP connection(s) included in the n3c-relayUE-InfoList; 1> if configured to provide configured grant assistance information for NR sidelink positioning: 2> initiate transmission of the UEAssistanceInformation message in accordance with 5.7.4.3 to provide configured grant assistance information for NR sidelink positioning; | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.7.4.2 |
2,691 | 6.4.3.4 UE-requested PDU session release procedure not accepted by the network | Upon receipt of a PDU SESSION RELEASE REQUEST message, if the SMF does not accept the request to release the PDU session, the SMF shall create a PDU SESSION RELEASE REJECT message. The SMF shall set the 5GSM cause IE of the PDU SESSION RELEASE REJECT message to indicate the reason for rejecting the PDU session release. The 5GSM cause IE typically indicates one of the following SM cause values: #35 PTI already in use; or #43 Invalid PDU session identity; or #95 – 111: protocol errors. The SMF shall send the PDU SESSION RELEASE REJECT message. Upon receipt of a PDU SESSION RELEASE REJECT message and a PDU session ID, using the NAS transport procedure as specified in subclause 5.4.5, the UE shall stop timer T3582, release the allocated PTI value and locally release the PDU session. If there is one or more multicast MBS sessions associated with the PDU session, the UE shall locally leave the associated multicast MBS sessions. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.4.3.4 |
2,692 | 10.5.5.17 Update result | The purpose of the update result information element is to specify the result of the associated updating procedure. The update result is a type 1 information element. The update result information element is coded as shown in figure 10.5.131/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.149/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Figure 10.5.131/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Update result information element Table 10.5.149/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Update result information element | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 10.5.5.17 |
2,693 | 5.5.2 Scenario | A UAS is operating a mission in San Diego to transport blood for transplant surgery between 2 hospitals. The UAVs are flow under waypoint guidance and operate with a high degree of automation in normal operating modes. Because of the geography of San Diego, much of the route is planned to fly over canyons due to the direct route and the lower population density providing a lower risk factor. The canyons often have poor radio coverage due to physical distance from, and obstruction of, the nearest radio towers. These canyons also act as “highways” for UAVs due to the geography and risk factors. Therefore, UAV density is often quite high. Also, to take into account is the requirement to route around the U.S. Marine Corps base at Miramar which also provides a concentration of UAVs at the boundary of the no-fly zone. In this scenario a faster moving drone is approaching behind the subject of this use case. As there is limited radio coverage, both UAVs are in an automated mode of operation and there is no connection to a UTM to provide a separation service. They require distributed intelligence to maintain separation or else a collision will occur. Both UAVs are fitted with 3GPP ProSe-enabled communication modules and discover each other at a safe distance. They negotiate a separation method (typically they separate in the vertical plane) and execute route modifications to adapt to the presence of the other. This procedure also takes into account the presence of other UAVs in the area. The UAVs pass each other safely and resume their previously planned route. | 3GPP TS 22.825 | Study on Remote Identification of Unmanned Aerial Systems (UAS) | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 5.5.2 |
2,694 | P.1 PIN Reference Architecture | Figure P.1-1 shows the logical PIN reference architecture. Figure P.1-1: PIN reference architecture A Personal IoT Network (PIN) in 5GC consists of one or more devices providing gateway/routing functionality known as the PIN Element with Gateway Capability (PEGC), and one or more devices providing PIN management functionality known as the PIN Element with Management Capability (PEMC) to manage the Personal IoT Network; and device(s) called the PIN Elements (PINE). A PINE can be a non-3GPP device. The PIN service can also have an AF for PIN (see TS 23.542[ Application layer support for Personal IoT Network ] [181]). The AF can be deployed by mobile operator or by an authorized third party. When the AF is deployed by third party, the interworking with 5GS is performed via the NEF. With PIN-DN communication, the PEMC and PEGC communicates with the PIN Application Server at the application layer over the user plane. The PEGC and PEMC can communicate with each other via PIN direct communication using 3GPP access (e.g. PC5) or non-3GPP access (e.g. WiFi, BT) or via PIN indirect communication using a PDU Session in the 5GS. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | P.1 |
2,695 | 7.7.6 Missing Information Elements | A GTP entity shall check if all mandatory IEs are present in the received Request message. Apart from Echo Request message, if one or more mandatory information elements are missing in the received Request message, the GTP entity should log the error and shall send a Response message with Cause IE value set to "Mandatory IE missing" together with the type and instance of the missing mandatory IE. If a GTP entity receives a Response message with Cause IE value set to "Mandatory IE missing", it shall notify its upper layer. A GTP entity shall check if all mandatory IEs are present in the received Response message without a rejection Cause value. If one or more mandatory information elements are missing, the GTP entity shall notify the upper layer and should log the error. If a mandatory IE is missing in a Response message, which the SGW shall forward over another interface (e.g. when SGW forwards a message from PGW to MME), the SGW shall include the rejection Cause "Invalid Reply from remote peer" (see clause 8.4) in the forwarded Response message. A GTP entity shall check if conditional information elements are present in the received Request message, if possible (i.e. if the receiving entity has sufficient information available to check if the respective conditions were met). If one or more conditional information elements are missing, a GTP entity should log the error and shall send a Response message with Cause IE value set to "Conditional IE missing" together with the type and instance of the missing conditional IE. A GTP entity shall check if conditional information elements are present in the received Response message without a rejection Cause value, if possible (i.e. if the receiving entity has sufficient information available to check if the respective conditions were met). If one or more conditional information elements are missing, a GTP entity shall notify the upper layer and should log the error. For Response messages containing a rejection Cause value, see clause 6.1.1. If the Indication IE is applicable for the message as a conditional IE and if it is not present, the GTP entity shall not reject the message unless there are other reasons to reject the message. If the Indication IE is applicable for the message as conditional IE and if it is present with the value of all the applicable flags set to "0", the GTP entity shall not reject the message unless there are other reasons to reject the message. Absence of an optional information element shall not trigger any of the error handling processes. | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 7.7.6 |
2,696 | 4.23.4.2 UE Triggered Service Request without I-SMF change/removal | When both I-SMF and SMF are available for a PDU session and no I-SMF change or removal is needed during the service request procedure, the procedure in this clause is used. Compared to the procedure in clause 4.2.3.2, the SMF is replaced with the I-SMF and the impacted intermediate UPF(s) are UPFs that are controlled by I-SMF. Difference are captured below: - Steps 6a-6b, these steps are not needed as the CN Tunnel Info of UPF (PSA) allocated for N9 is available at the I-SMF when the I-SMF is inserted. - Step 7a, if a new intermediate UPF is selected, the I-SMF invokes Nsmf_PDUSession_Update Request (DN Tunnel Info of the new intermediate UPF. The I-SMF may also include UE location Information, Time Zone RAT type, Access Type and Operation Type set to "UP Activate", if those information is changed and need to be notified to SMF. If DL Tunnel Info of new intermediate UPF is received, the SMF provides the DL Tunnel Info of new intermediate UPF received from I-SMF to UPF(PSA). - Step 10, this step does not apply as in this scenario the I-UPF is always needed. - Step 16, If the I-SMF needs to update SMF with e.g. change of UE location information, change of Time Zone, change of RAT type and/or change of Access type, the I-SMF invokes Nsmf_PDUSession_Update Request to send User Location Information, Time Zone, RAT type and/or Access Type to SMF. If the I-SMF invoked Nsmf_PDUSession_Update Request in step 7a with Operation Type "UP Activate", the I-SMF also includes an Operation Type set to "UP Activated". If dynamic PCC is deployed and if Policy Control Request Trigger condition(s) have been met (e.g. change of Access Type, change of UE location), the SMF performs SMF initiated SM Policy Modification procedure as defined in clause 4.16.5.1 and may get the updated policy. - Steps 18a-18b, these steps do not apply as in this scenario the I-UPF is always needed. - Step 21a, this step does not apply as in this scenario the I-UPF is always needed. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.23.4.2 |
2,697 | 5.3.7 GUTI Reallocation procedure | The MME may initiate the GUTI Reallocation procedure to reallocate the GUTI and/or TAI list at any time when a signalling association is established between UE and MME. The GUTI Reallocation procedure allocates a new GUTI and/or a new TAI list and/or PLMN-assigned UE Radio Capability ID to the UE. The GUTI and/or the TAI list may also be reallocated by the Attach or the Tracking Area Update procedures. When the UE supports RACS, and the MME needs to configure the UE with a UE Radio Capability ID, and the MME already has the UE radio capabilities for the UE, the MME may initiate the GUTI Reallocation procedure to provide the UE with the UE Radio Capability ID for the UE radio capabilities the UCMF returns to the MME for this UE. When the UE supports RACS, and the MME needs to delete any previously assigned PLMN-assigned UE Radio Capability ID(s) for the UE, the MME may initiate the GUTI Reallocation procedure to signal a PLMN-assigned UE Radio Capability ID deletion indication. If the UE receives PLMN-assigned UE Radio Capability ID deletion indication, the UE shall delete any PLMN-assigned UE Radio Capability ID(s) for this PLMN. The GUTI Reallocation procedure is illustrated in Figure 5.3.7-1. Figure 5.3.7-1: GUTI Reallocation Procedure 1. The MME sends GUTI Reallocation Command (GUTI, TAI list, PLMN-assigned UE Radio Capability ID, PLMN-assigned UE Radio Capability ID deletion indication) to the UE. 2. The UE returns GUTI Reallocation Complete message to the MME. | 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.7 |
2,698 | – RadioBearerConfig | The IE RadioBearerConfig is used to add, modify and release signalling, multicast MRBs and/or data radio bearers. Specifically, this IE carries the parameters for PDCP and, if applicable, SDAP entities for the radio bearers. RadioBearerConfig information element -- ASN1START -- TAG-RADIOBEARERCONFIG-START RadioBearerConfig ::= SEQUENCE { srb-ToAddModList SRB-ToAddModList OPTIONAL, -- Cond HO-Conn srb3-ToRelease ENUMERATED{true} OPTIONAL, -- Need N drb-ToAddModList DRB-ToAddModList OPTIONAL, -- Cond HO-toNR drb-ToReleaseList DRB-ToReleaseList OPTIONAL, -- Need N securityConfig SecurityConfig OPTIONAL, -- Need M ..., [[ mrb-ToAddModList-r17 MRB-ToAddModList-r17 OPTIONAL, -- Need N mrb-ToReleaseList-r17 MRB-ToReleaseList-r17 OPTIONAL, -- Need N srb4-ToAddMod-r17 SRB-ToAddMod OPTIONAL, -- Need N srb4-ToRelease-r17 ENUMERATED{true} OPTIONAL -- Need N ]], [[ srb5-ToAddMod-r18 SRB-ToAddMod OPTIONAL, -- Need N srb5-ToRelease-r18 ENUMERATED{true} OPTIONAL -- Need N ]] } SRB-ToAddModList ::= SEQUENCE (SIZE (1..2)) OF SRB-ToAddMod SRB-ToAddMod ::= SEQUENCE { srb-Identity SRB-Identity, reestablishPDCP ENUMERATED{true} OPTIONAL, -- Need N discardOnPDCP ENUMERATED{true} OPTIONAL, -- Need N pdcp-Config PDCP-Config OPTIONAL, -- Cond PDCP ..., [[ srb-Identity-v1700 SRB-Identity-v1700 OPTIONAL -- Need M ]], [[ srb-Identity-v1800 SRB-Identity-v1800 OPTIONAL -- Need M ]] } DRB-ToAddModList ::= SEQUENCE (SIZE (1..maxDRB)) OF DRB-ToAddMod DRB-ToAddMod ::= SEQUENCE { cnAssociation CHOICE { eps-BearerIdentity INTEGER (0..15), sdap-Config SDAP-Config } OPTIONAL, -- Cond DRBSetup drb-Identity DRB-Identity, reestablishPDCP ENUMERATED{true} OPTIONAL, -- Need N recoverPDCP ENUMERATED{true} OPTIONAL, -- Need N pdcp-Config PDCP-Config OPTIONAL, -- Cond PDCP ..., [[ daps-Config-r16 ENUMERATED{true} OPTIONAL -- Cond DAPS ]] } DRB-ToReleaseList ::= SEQUENCE (SIZE (1..maxDRB)) OF DRB-Identity SecurityConfig ::= SEQUENCE { securityAlgorithmConfig SecurityAlgorithmConfig OPTIONAL, -- Cond RBTermChange1 keyToUse ENUMERATED{master, secondary} OPTIONAL, -- Cond RBTermChange ... } MRB-ToAddModList-r17 ::= SEQUENCE (SIZE (1..maxMRB-r17)) OF MRB-ToAddMod-r17 MRB-ToAddMod-r17 ::= SEQUENCE { mbs-SessionId-r17 TMGI-r17 OPTIONAL, -- Cond MRBSetup mrb-Identity-r17 MRB-Identity-r17, mrb-IdentityNew-r17 MRB-Identity-r17 OPTIONAL, -- Need N reestablishPDCP-r17 ENUMERATED{true} OPTIONAL, -- Need N recoverPDCP-r17 ENUMERATED{true} OPTIONAL, -- Need N pdcp-Config-r17 PDCP-Config OPTIONAL, -- Cond PDCP ... } MRB-ToReleaseList-r17 ::= SEQUENCE (SIZE (1..maxMRB-r17)) OF MRB-Identity-r17 -- TAG-RADIOBEARERCONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
2,699 | 5.15.11.3.2 VPLMN with HPLMN assistance NSAC Admission | In this admission mode HPLMN delegates NSAC for S-NSSAIs subject to NSAC to the VPLMN, both for number of registered UEs and the number of LBO PDU sessions. Every NSACF performing admission in the VPLMN for each S-NSSAI of the HPLMN that is subject to NSAC and mapped to a corresponding S-NSSAI of the VPLMN, fetches from the VPLMN primary NSACF in a hierarchal architecture the maximum number of registered UEs to be admitted and/or the maximum number of LBO PDU sessions to be allowed. The VPLMN primary or central NSACF, in turn, acquires the information from the HPLMN central or primary NSACF depending on the deployed architecture. The VPLMN is either configured or discovers the NSACF in the HPLMN for quota retrieval. If re-distribution of quota is required in the VPLMN in a hierarchal architecture, amongst multiple NSACFs than this is handled by the primary NSACF in VPLMN with no involvement from the HPLMN. The VPLMN NSACF discovers the HPLMN primary or central NSACF or be configured with the needed information. For any request(s) received in any NSACF in the VPLMN exceeding the received maximum number information, the NSACF interacts with the VPLMN primary NSACF which in turn interacts with HPLMN primary or central NSACF to receive an updated roaming quota for the corresponding mapped S-NSSAI, which is used to determine whether admission request is accepted or rejected, unless forbidden by the SLA. If an admission request is accepted, the UE entry is stored in the NSACF performing admission in the VPLMN. This applies to the number of registered UEs as well as the number of LBO PDU sessions. The primary NSACF in VPLMN may re-distribute the received updated roaming quota to the NSACFs in VPLMN to perform NSAC for Roaming UEs according to the principles described in clauses 5.15.11.1 and 5.15.11.2. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.15.11.3.2 |
2,700 | – SL-RemoteUE-ConfigU2U | The IE SL-RemoteUE-ConfigU2U specifies the threshold configuration information for NR sidelink U2U Remote UE. SL-RemoteUE-ConfigU2U information element -- ASN1START -- TAG-SL-REMOTEUE-CONFIGU2U-START SL-RemoteUE-ConfigU2U-r18::= SEQUENCE { sl-RSRP-ThreshU2U-r18 SL-RSRP-Range-r16 OPTIONAL, -- Need R sl-FilterCoefficientU2U-r18 FilterCoefficient OPTIONAL, -- Need R sl-HystMinU2U-r18 Hysteresis OPTIONAL, -- Cond SL-RSRP-ThreshU2U sd-RSRP-ThreshU2U-r18 SL-RSRP-Range-r16 OPTIONAL, -- Need R sd-FilterCoefficientU2U-r18 FilterCoefficient OPTIONAL, -- Need R sd-HystMinU2U-r18 Hysteresis OPTIONAL -- Cond SD-RSRP-ThreshU2U } -- TAG-SL-REMOTEUE-CONFIGU2U-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
Subsets and Splits
No saved queries yet
Save your SQL queries to embed, download, and access them later. Queries will appear here once saved.