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
⌀ |
|---|---|---|---|---|---|---|---|
4,401 | 13.9.1.2 Format of XCAP Root URI | The XCAP Root URI, as defined in IETF RFC 4825 [94], is an HTTP URI that should have the following format: "http://xcap.<domain>" in which "<domain>" identifies the domain hosting the XCAP server. NOTE 1: The XCAP Root URI does not contain a port portion or an abs path portion of a standard HTTP URI. If a preconfigured or provisioned XCAP Root URI is available then the UE shall use it. When a preconfigured or provisioned XCAP Root URI does not exist then the UE shall create the XCAP Root URI as follows: - The first label shall be "xcap". - The next label(s) shall identify the home network as follows: 1. When the UE has an ISIM, the domain name from the IMPI shall be used (see 3GPP TS 31.103[ Characteristics of the IP Multimedia Services Identity Module (ISIM) application ] [93]) as follows: a. if the last two labels of the domain name from the IMPI are "3gppnetwork.org": i. the next labels shall be all labels of the domain name from the IMPI apart from the last two labels; and ii. the last three labels shall be "pub.3gppnetwork.org"; b. if the last two labels of the domain name from the IMPI are other than the "3gppnetwork.org": i. the next labels shall be all labels of the domain name from the IMPI; 2. When the UE has a USIM and does not have ISIM, the home network shall be "ims.mnc<MNC>.mcc<MCC>.pub.3gppnetwork.org" where <MNC> and <MCC> shall be derived from the components of the IMSI defined in clause 2.2. If there are only two significant digits in the MNC, one "0" digit shall be inserted at the left side to fill the 3 digits coding of MNC in the FQDN of XCAP Root URI. As an example for the case when the UE has ISIM, where the IMPI is "[email protected]", the overall XCAP Root URI used by the UE would be: "http://xcap.operator.com". As an example for the case when the UE has ISIM, where the IMPI is "[email protected]", the overall XCAP Root URI used by the UE would be: "xcap.ims.mnc015.mcc234.pub.3gppnetwork.org". As an example for the case when the UE has USIM and does not have ISIM, where the MCC is 345 and the MNC is 12, the overall XCAP Root URI created and used by the UE would be: "xcap.ims.mnc012.mcc345.pub.3gppnetwork.org" | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 13.9.1.2 |
4,402 | 8.9.14 Mobile IAB-node authorization | During the mobile IAB-node integration procedure, the RRC-terminating IAB-donor-CU receives the authorization status of the mobile IAB-node from the 5GC. If the authorization status is “not authorized”, the RRC-terminating IAB-donor-CU will neither establish any backhaul resources nor allocate any BAP address, TNL address or default BAP configuration for this mobile IAB-node. If the authorization status for the mobile IAB-node changes, the 5GC sends an updated authorization status to the RRC-terminating IAB-donor-CU. In case the mobile IAB-MT and its co-located mobile IAB-DU connect to same IAB-donor-CU, and the updated authorization status received from the 5GC is “not authorized”, the IAB-donor-CU will perform the following actions in this order: it will attempt to hand over the UEs served by the mobile IAB-node to other cell(s), release the F1 interface towards the mobile IAB-DU, and release all backhaul resources (including the BAP address, TNL address and default BAP reconfiguration) for this mobile IAB-node. In case the mobile IAB-MT and its co-located mobile IAB-DU connect to different IAB-donor-CUs, the RRC-terminating IAB-donor sends the updated authorization status to the F1-terminating IAB-donor-CU via the IAB TRANSPORT MIGRATION MODIFICATION REQUEST message. The F1-terminating IAB-donor-CU confirms the reception of the updated authorization status via the IAB TRANSPORT MIGRATION MODIFICATION RESPONSE message. NOTE: In absence of Xn connectivity between the RRC-terminating IAB-donor-CU and the F1-terminating IAB-donor-CU, the passing of the authorization status is left up to implementation. If the updated authorization status for the mobile IAB-node is “not authorized”, the F1-terminating IAB-donor, attempts to hand over the UEs served by the mobile IAB-node to other cell(s), and then releases the F1 interface towards the mobile IAB-DU. After that, the F1-terminating IAB-donor requests from the RRC-terminating IAB-donor the release of all the offloaded traffic via the IAB TRANSPORT MIGRATION MANAGEMENT REQUEST message. The RRC-terminating IAB-donor releases the offloaded traffic and all backhaul resources (including BAP address, TNL address and default BAP reconfiguration) for this mobile IAB-node. The RRC-terminating IAB-donor may send an indication which indicates that the mobile IAB-MT can be deregistered, to AMF. If the authorization status is changed back from “not authorized” to “authorized”, the phase 2 and phase 3 of the mobile IAB-node integration procedure as defined in clause 8.12.3 are carried out. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 8.9.14 |
4,403 | 5.5.3.9 Charging principles for 5G Roaming architecture with local breakout | The 5G System roaming architecture with local breakout is specified in TS 23.501[ System architecture for the 5G System (5GS) ] [215]. The breakout point for both the control plane signalling and user plane traffic is in the VPLMN, i.e. the vSMF and vUPF respectively. The VPLMN charging mechanism collects charging information related to the 5G data connectivity usage for each UE detected as in-bound roamer. The information collected include details of the services used by the visiting subscriber and it is conveyed to both the CHF in VPLMN and to the CHF in the HPLMN. The CHF in the VPLMN uses the collected charging information for wholesale charging including service aware towards the HPLMN The CHF in the HPLMN uses the collected charging information for retail charging towards the home subscriber while roaming. Charging for Roaming with Local Breakout is covered by the 5G data connectivity domain converged charging architecture specified in TS 32.255[ Telecommunication management; Charging management; 5G data connectivity domain charging; Stage 2 ] [15], using the SMF embedding the CTF. | 3GPP TS 32.240 | Telecommunication management; Charging management; Charging architecture and principles | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 5.5.3.9 |
4,404 | 5.8.9.1.9 Reception of an RRCReconfigurationCompleteSidelink by the UE | The UE shall perform the following actions upon reception of the RRCReconfigurationCompleteSidelink: 1> stop timer T400 for the destination, if running; 1> consider the configurations in the corresponding RRCReconfigurationSidelink message to be applied. 2> if the RRCReconfigurationCompleteSidelink message includes the sl-DRX-ConfigReject: 3> consider no sidelink DRX to be applied for the corresponding sidelink unicast communication. 5.8.9.1.10 Sidelink reset configuration The UE shall: 1> release/clear current sidelink radio configuration of this destination received in the RRCReconfigurationSidelink; 1> release the sidelink DRBs of this destination, in according to clause 5.8.9.1a.1; 1> release the additional sidelink RLC bearer of this destination, if configured, in according to clause 5.8.9.1a.5; 1> reset the sidelink specific MAC of this destination. NOTE 1: Sidelink radio configuration is not just the resource configuration but may include other configurations included in the RRCReconfigurationSidelink message except the sidelink DRBs of this destination. NOTE 2: After the sidelink DRB release procedure, UE may perform the sidelink DRB addition according to the current sidelink configuration of this destination, received in sl-ConfigDedicatedNR, SIB12 and SidelinkPreconfigNR, according to clause 5.8.9.1a.2. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.8.9.1.9 |
4,405 | 6.6.3G Spurious emission for V2X Communication | This clause specifies the additional requirements for inter-band con-current V2X operation with the single CC uplink assigned to two E-UTRA bands for coexistence with protected bands for the specified simultaneous transmission of the inter-band con-current V2X configurations in Table 6.6.3G-0. The intersection of the requirements for the individual bands specified in clause 6.6.3.2 shall also apply for the specified simultaneous transmission of the inter-band con-current V2X. Intersection of a requirement means that both UL or sidelink transmission constituent bands have the same protected band requirement specified and if one or both protected bands have note(s) associated those note(s) also apply. When UE is configured for E-UTRA V2X sidelink transmissions non-concurrent with E-UTRA uplink transmissions for E-UTRA V2X operating bands specified in Table 5.5G-1, the requirements in subclause 6.6.3 apply. When UE is configured for simultaneous E-UTRA V2X sidelink and E-UTRA uplink transmissions for inter-band E-UTRA V2X / E-UTRA bands specified in Table 5.5G-2, the UE-coexistence requirements in Table 6.6.3G-0 in subclause 6.6.3G apply as as specified for the corresponding inter-band con-current operation with uplink assigned to two bands. NOTE: For inter-band con-current V2X operation with uplink assigned to E-UTRA band and slidelink transmission assigned to E-UTRA V2X operating bands, the requirements in Table 6.6.3G-0 could be verified by measuring spurious emissions at the specific frequencies where second and third order intermodulation products generated by the two transmitted carriers can occur; in that case, the requirements for remaining applicable frequencies in Table 6.6.3G-0 and in clause 6.6.3.2 would be considered to be verified by the measurements verifying the one uplink inter-band con-current UE to UE co-existence requirements. Table 6.6.3G-0: Requirements for inter-band con-current V2X operation For intra-band contiguous multi-carrier operation, the boundary between E-UTRA out of band and spurious emission domain for intra-band contiguous carrier aggregation specified in Table 6.6.3.1A-1 shall apply. For intra-band contiguous multi-carrier operation, the spurious emission requirements in Table 6.6.3G-1 shall apply for coexistence with protected bands. NOTE: For measurement conditions at the edge of each frequency range, the lowest frequency of the measurement position in each frequency range should be set at the lowest boundary of the frequency range plus MBW/2. The highest frequency of the measurement position in each frequency range should be set at the highest boundary of the frequency range minus MBW/2. MBW denotes the measurement bandwidth defined for the protected band. Table 6.6.3G-1: Requirements for intraband multi-carrier V2X operation For V2X UEs supportingTransmit Diversity, the requirements specified for single carrier shall apply to each transmit antenna connector. If V2X UE is configured for transmission on single-antenna connector, the general requirements specified for single carrier shall apply to the active antenna connector. | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.6.3G |
4,406 | 16.21.3.1 Path Management | The L2 MP Remote UE needs to establish both a direct path and an indirect path. The L2 MP Remote UE adds the indirect path using PC5 link on top of the only direct path under the same gNB. And also, the L2 MP Remote UE using PC5 link adds the direct path on top of the only indirect path under the same gNB. Meanwhile, the L2 MP Remote UE adds the indirect path using N3C link on the only direct path under the same gNB. But it is not allowed that the L2 MP Remote UE using N3C link adds the direct path on the indirect path. The MP Relay UE using N3C indirect path is restricted to serve only one MP Remote UE. For L2 MP Remote UE, only a single cell group is configured (i.e., only MCG is configured for the direct path and indirect path). The primary path of split SRB1 and SRB2 is always configured on direct path. In the L2 MP Remote UE, non-split SRB1/2 is allowed to be configured only on direct path. Figure 16.21.3.1-1 describes the procedures for the indirect path addition on the direct path for the L2 MP relaying. This procedure is applicable to the L2 MP Remote UE using SL indirect path or N3C indirect path except step 5. Figure 16.21.3.1-1: Procedure for indirect path addition on top of direct path 0. The L2 MP Remote UE performs data transmission and reception by using direct path on PCell. 1. If the L2 MP Remote UE will be connected with L2 MP Relay UE using PC5 link, the L2 MP Remote UE reports at least the list of the candidate L2 MP Relay UE ID and the cell ID of the candidate L2 MP Relay UEs. Meanwhile, if the MP Remote UE will be connected with L2 MP Relay UE using N3C link, the MP Remote UE reports at least the list of the C-RNTI and the cell ID of the connected candidate MP Relay UEs. NOTE 1: The C-RNTI and cell ID of MP Relay UE using N3C link can be reported only if the secure connection between MP Remote UE and MP Relay UE is established. 2. The gNB decides to add the indirect path for the L2 MP Remote UE. The cell serving the direct path and the cell serving the L2 MP Relay UE on the indirect path belong to the same gNB but can be same or different. 3. The gNB sends an RRCReconfiguration message to the L2 MP Relay UE to configure the indirect path of the L2 MP Remote UE, if the L2 MP Relay UE is in RRC_CONNECTED. 4. The gNB sends the RRCReconfiguration message to the L2 MP Remote UE. 5. The L2 MP Remote UE establishes a PC5 unicast link with the target L2 MP Relay UE. NOTE 2: For the N3C indirect path addition, step 5 is omitted. It is L2 MP Remote UE's implementation how to make N3C indirect path between L2 MP Remote UE and L2 MP Relay UE. 6a. The L2 MP Remote UE sends the RRCReconfigurationComplete message to the gNB at least via the direct path in order to complete the indirect path addition procedure. 6b. If a split SRB1 with duplication is configured, the L2 MP Remote UE also sends the RRCReconfigurationComplete message to the gNB via the indirect path served by the L2 MP Relay UE. NOTE 3: Step 5 can be executed after step 6a. Step 5 is independent of step 6a. 7. The L2 MP Remote UE performs data transmission and reception by using both the direct path on PCell and the indirect path served by a L2 MP Relay UE. In the case that the selected L2 MP Relay UE for indirect path addition is in RRC_IDLE or RRC_INACTIVE, after receiving the path addition command, the L2 MP Remote UE should trigger the L2 MP Relay UE in RRC_IDLE or RRC_INACTIVE to move to RRC_CONNECTED. If the L2 MP Remote UE and L2 MP Relay UE are connected by using N3C link, it is L2 MP Remote/Relay UE's implementation on how to trigger the RRC_IDLE/RRC_INACTIVE L2 MP Relay UE to initiate RRC connection establishment procedure. If the split SRB1 with duplication is not configured at the L2 MP Remote UE, the L2 MP Remote UE using SL indirect path sends PC5-RRC message to the L2 MP Relay UE. Upon receiving the PC5-RRC message, the L2 MP Relay UE in RRC_IDLE or RRC_INACTIVE initiates a Uu RRC connection establishment or an RRC connection resume. If the split SRB1 with duplication is configured at the L2 MP Remote UE, the L2 MP Relay UE in RRC_IDLE or RRC_INACTIVE received RRCReconfigurationComplete message from the L2 MP Remote UE may a Uu RRC connection establishment or an RRC connection resume for sending the RRCReoncfigurationComplete message to the gNB. Figure 16.21.3.1-2 describes the procedures for the indirect path change under the single direct path in the L2 MP Relay operation. This procedure is applicable to the L2 MP Remote UE using SL indirect path or N3C indirect path except step 5. Figure 16.21.3.1-2: Procedure for indirect path change under a single procedure 0. The L2 MP Remote UE performs data transmission and reception by using both the direct path on PCell and the indirect path served by a source L2 MP Relay UE. 1. The L2 MP Remote UE and the L2 MP Relay UE perform measurements based on measurement configuration. When the measurement reporting is triggered, the L2 MP Remote UE using SL indirect link reports at least signal strength (e.g., SD-RSRP/SL-RSRP) of the serving indirect path, the list of the candidate L2 MP Relay UE ID and the cell ID of the candidate L2 MP Relay UEs. Meanwhile, the MP Remote UE using N3C link reports at least the list of the C-RNTI and the cell ID of the connected candidate MP Relay UEs. 2. The gNB decides to change the indirect path of L2 MP Remote UE from the source L2 MP Relay UE to a target L2 MP Relay UE. The cell serving the direct path and the cell serving the source/target L2 MP Relay UE on the indirect path belong to the same gNB but can be same or different. 3a. The gNB sends an RRCReconfiguration message to the source L2 MP Relay UE to release the indirect path of the L2 MP Remote UE. 3b. The gNB sends an RRCReconfiguration message to the target L2 MP Relay UE to add the indirect path for the L2 MP Remote UE. 4. The gNB sends the RRCReconfiguration message to the L2 MP Remote UE on the direct path and/or the indirect path for indirect path change. If SRB1 is configured either direct path or indirect path to the L2 MP Remote UE, the RRCReconfiguration message is sent via one of the path on which the SRB1 is configured. If split SRB1 is configured, it is up to gNB implementation whether the RRCReconfiguration is sent via one of the paths or both paths. 5. The L2 MP Remote UE establishes a PC5-RRC connection with the target L2 MP Relay UE for using SL indirect path. NOTE 4: For the N3C indirect path addition, step 5 is omitted. It is L2 MP Remote UE's implementation how to make N3C indirect path between L2 MP Remote UE and L2 MP Relay UE. 6a. The L2 MP Remote UE sends the RRCReconfigurationComplete message to the gNB at least via the direct path in order to complete the indirect path change procedure. NOTE 5: Step 5 can be executed after step 6a. Step 5 is independent of step 6a. 6b. If a split SRB1 with duplication is configured, the L2 MP Remote UE also sends the RRCReconfigurationComplete message to the gNB via the indirect path served by the target L2 MP Relay UE. 7. The L2 MP Remote UE performs data transmission and reception by using both the direct path on PCell and the indirect path served by a target L2 MP Relay UE. In the case that the selected target L2 MP Relay UE for indirect path change is in RRC_IDLE or RRC_INACTIVE, after receiving the path change command, the L2 MP Remote UE should trigger the target L2 MP Relay UE in RRC_IDLE or RRC_INACTIVE to be in RRC_CONNECTED. If the target L2 MP Relay UE is not in RRC_CONNECTED in step 3, the gNB sends an RRCReconfiguration message to the target L2 MP Relay UE after the target L2 MP Relay UE enters RRC_CONNECTED. If the split SRB1 with duplication is not configured at the L2 MP Remote UE, the L2 MP Remote UE sends the RRCReconfigurationComplete message only on the direct path in Step 6a. The L2 MP Remote UE using SL indirect path can send a PC5-RRC message to the target L2 MP Relay UE in RRC_IDLE or RRC_INACTIVE after or during Step 5. The target L2 MP Relay UE in RRC_IDLE or RRC_INACTIVE initiates an RRC connection establishment or an RRC connection resume upon receiving the PC5-RRC message from the L2 MP Remote UE. If the target L2 MP Relay UE is in RRC_IDLE or RRC_INACTIVE, the RRCReconfigurationComplete message at Step 6b is sent to the gNB after the target L2 MP Relay UE enters RRC_CONNECTED. If the split SRB1 with duplication is configured at the L2 MP Remote UE, the target L2 MP Relay UE in RRC_IDLE or RRC_INACTIVE receiving RRCReconfigurationComplete message from the L2 MP Remote UE initiates an RRC connection establishment or an RRC connection resume for sending the RRCReconfigurationComplete message to the gNB at Step 6b. Figure 16.21.3.1-3 describes the procedures for the direct path addition on top of the indirect path for the L2 MP Relay operation. This procedure is only applicable to the L2 MP Remote UE using SL indirect path. Figure 16.21.3.1-3: Procedure for direct path addition on top of indirect path 0. The L2 MP Remote UE performs data transmission and reception by using indirect path via PC5 link. 1. The L2 MP Remote UE perform measurements based on measurement configuration. When the measurement reporting is triggered, the L2 MP Remote UE reports at least the Uu signal strength of the serving cell and neighbour cells with the cell IDs (i.e., NCGI/NCI). 2. The gNB decides to add the direct path for the L2 MP Remote UE. The cell serving the direct path and the cell serving the L2 MP Relay UE on the indirect path belong to the same gNB but can be same or different. 3. The gNB sends an RRCReconfiguration message to the L2 MP Relay UE to update the indirect path configuration, if necessary. 4. The gNB sends the RRCReconfiguration message to the L2 MP Remote UE via the L2 MP Relay UE. The contents in the RRCReconfiguration message includes at least a target cell within direct path addition configuration. 5. The L2 MP Remote UE synchronizes to DL of the target cell serving the direct path and performs random access procedure towards the cell serving the direct path. The L2 MP Remote UE configures the target cell as PCell. 6a. The L2 MP Remote UE sends the RRCReconfigurationComplete message to the gNB at least via the direct path in order to complete the direct path addition procedure. 6b. If a split SRB1 with duplication is configured, the L2 MP Remote UE also sends the RRCReconfigurationComplete message to the gNB via the indirect path served by the L2 MP Relay UE. 7. The L2 MP Remote UE performs data transmission and reception by using both the direct path on PCell and the indirect path served by a L2 MP Relay UE. Figure 16.21.3.1-4 describes the procedures for the direct path change on top of the indirect path for the L2 MP Relay operation. This procedure is only applicable to the L2 MP Remote UE using SL indirect path. Figure 16.21.3.1-4: Procedure for direct path change under a single procedure 0. The L2 MP Remote UE performs data transmission and reception by using both the direct path on the source PCell and the indirect path served by a L2 MP Relay UE. 1. The L2 MP Remote UE and the L2 MP Relay UE perform measurements based on measurement configuration. The L2 MP Remote UE may report measurement results. 2. The gNB decides to change the direct path of the L2 MP Remote UE from the PCell (i.e. source PCell) to a new cell (i.e. target PCell). The source/target PCell serving the old/new direct path and the cell serving the L2 MP Relay UE on the indirect path belong to the same gNB but can be same or different. 3. The gNB sends an RRCReconfiguration message to the L2 MP Relay UE to update the indirect path configuration, if necessary. 4. The gNB sends the RRCReconfiguration message to the L2 MP Remote UE on the direct path and/or the indirect path for direct path change. 5. The L2 MP Remote UE synchronizes to DL of the target PCell serving the new direct path and performs random access procedure towards the target PCell serving the new direct path. 6a. The L2 MP Remote UE sends the RRCReconfigurationComplete message to the gNB at least via the direct path in order to complete the direct path change procedure. 6b. If a split SRB1 with duplication is configured, the L2 MP Remote UE also sends the RRCReconfigurationComplete message to the gNB via the indirect path served by the L2 MP Relay UE. 7. The L2 MP Remote UE performs data transmission and reception by using both the direct path on the target PCell and the indirect path served by a L2 MP Relay UE. If the direct path addition/change is failed, the L2 U2N Remote UE always shall trigger RRCReestablishment. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.21.3.1 |
4,407 | 4.3.12.11 Support of eCall Only Mode | For service requirements for eCall only mode, refer to TS 22.101[ Service aspects; Service principles ] [80]. A UE configured for eCall Only Mode shall remain in EMM-DEREGISTERED state, shall camp on a network cell when available but shall refrain from any Mobility Management or other signalling with the network. The UE may instigate Mobility Management and Connection Management procedures in order to establish, maintain and release an eCall Over IMS session or a session to any non-emergency MSISDN(s) or URI(s) configured in the UICC for test and/or terminal reconfiguration services. Following the release of either session, the UE starts a timer whose value depends on the type of session (i.e. whether eCall or a session to a non-emergency MSISDN or URI for test/reconfiguration). While the timer is running, the UE shall perform normal Mobility Management procedures and is permitted to respond to paging to accept and establish an incoming session (e.g. from an emergency centre, PSAP or HPLMN operator). When the timer expires, the UE shall perform a UE-initiated detach procedure if still attached and enter EMM-DEREGISTERED state. NOTE 1: An HPLMN operator can change the eCall Only Mode configuration state of a UE in the UICC. An HPLMN operator can also instead add, modify or remove a non-emergency MSISDN or URI in the UICC for test and/or terminal reconfiguration services. This can occur following a UE call to a non-emergency MSISDN or URI configured for reconfiguration. When the eCall Only Mode configuration is removed, the UE operates as a normal UE that can support eCall over IMS. NOTE 2: A test call and a reconfiguration call can be seen as normal (non-emergency) call by a serving PLMN and normal charging rules can apply depending on operator policy. NOTE 3: An MSISDN configured in the UICC for test and/or terminal reconfiguration services for eCall Over IMS can differ from an MSISDN configured in the UICC for test services for eCall over the CS domain. When attaching to EPS for E-UTRAN access, a UE configured for eCall Only Mode may indicate support for radio capabilities for IRAT Handover (for UTRAN) or SRVCC Handover (for GERAN), but shall not indicate support for IMS Voice over RATs other than E-UTRAN. NOTE 4: Access to the PS domain for a UE configured for eCall Only Mode is only supported by E-UTRAN in this version of the specification. | 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.12.11 |
4,408 | 4.4.2.2 N4 Session Level Reporting Procedure | This procedure is used by the UPF to report events related to an N4 session for an individual PDU Session. The triggers for event reporting were configured on the UPF during N4 Session Establishment/Modification procedures by the SMF. Figure 4.4.2.2-1: N4 Session Level Reporting procedure 1. The UPF detects that an event has to be reported. The reporting triggers include the following cases: (1) Measurement information reporting (Usage Report). Measurement information shall be collected in the UPF and reported to the SMF as defined in clause 5.8 and clause 5.12 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. NOTE 1: The Usage Report is also used for the reporting of other events or information. For details refer to clause 7.5.8.3 of TS 29.244[ Interface between the Control Plane and the User Plane nodes ] [69]. (2) Start of traffic detection (Usage Report). When traffic detection is requested by SMF and the start of traffic is detected for a Packet Detection Rule (PDR) as described in clause 5.8 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], the UPF shall report the start of traffic detection to the SMF and indicate the corresponding PDR rule ID. (3) Stop of traffic detection (Usage Report). When traffic detection is requested by SMF and the end of traffic is detected for a PDR as described in clause 5.8 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], the UPF shall report the stop of traffic detection to the SMF and indicate the corresponding PDR rule ID. (4) Detection of 1st downlink packet for a QoS Flow of a PDU Session with UP Connection deactivated (Downlink Data Report). When UPF receives the first downlink packet for a QoS Flow but no N3/N9 tunnel for downlink data transmission exists and the buffering is performed by the UPF, it shall report the detection of 1st downlink packet to SMF also indicating the QoS Flow for which the downlink packet was received (for the purpose of downlink data notification). The UPF shall also report the DSCP of the packet if the PDU Session type is IP (to support the Paging Policy Differentiation feature described in clause 5.4.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]). (5) Detection of PDU Session Inactivity for a specified period (User Plane Inactivity Report). When an Inactivity Timer for a PDU Session is provided by SMF during N4 Session Establishment/Modification procedure and the UPF detects the PDU Session has no data transfer for a period specified by the Inactivity Timer, it shall report PDU Session Inactivity to the SMF. NOTE 2: As described in clause 4.3.7, an Inactivity Timer to the UPF is not provided by the SMF for always-on PDU Sessions. (6) QoS Monitoring Report (Session Report). When the QoS Monitoring is enabled for the QoS Flow, performs the necessary actions as described in clause 5.45 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. The details about when and how the UPF sends the QoS Monitoring reports are described in clause 5.8.2.18 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. When receiving the QoS monitoring reports from the UPF, the SMF sends the reports to the target NF according to the information for QoS Monitoring received in the PCC rules as described in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [20]. (7) TSC Management Information available (TSC Management Information). When TSC management information is available, the UPF shall provide the TSC management information in the TSC Management Information to the SMF as defined in clause 5.8.5.14 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. (8) Discard Downlink Traffic detection (Downlink Data Report). When discarded downlink traffic detection is requested by SMF for a PDR and the first downlink packet is discarded after being buffered for this PDR as described in clause 5.8.3.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], the UPF shall report the discarded downlink traffic detection to the SMF and indicate the corresponding PDR rule ID (for the purpose of downlink data delivery status notification). (9) Buffered Downlink Traffic detection (Downlink Data Report). When buffered downlink traffic detection is requested by SMF for a PDR and the first downlink packet is buffered for this PDR as described in clause 5.8.3.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], the UPF shall report the buffered downlink traffic detection to the SMF and indicate the corresponding PDR rule ID (for the purpose of downlink data delivery status notification). (10) N6 Traffic Parameter Measurement Report (Session Report). When the N6 Traffic Parameters measurement report is requested by SMF for a QoS Flow as described in clause 5.37.8.2 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], the UPF shall report to the SMF the N6 Traffic Parameter(s) for the specified QoS Flow (i.e. the N6 jitter range associated with the DL periodicity and conditionally, the UL/DL periodicity). 2. The UPF sends an N4 session report message (N4 Session ID, list of [Usage Report, Downlink Data Report, Session Report, User Plane Inactivity Report, TSC Management Information]) to the SMF. 3. The SMF identifies the N4 session context based on the received N4 Session ID and applies the reported information for the corresponding PDU Session. The SMF responds with an N4 session report ACK message. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.4.2.2 |
4,409 | – EUTRA-MultiBandInfoList | The IE EUTRA-MultiBandInfoList indicates the list of frequency bands in addition to the band represented by CarrierFreq for which cell reselection parameters are common, and a list of additionalPmax and additionalSpectrumEmission. EUTRA-MultiBandInfoList information element -- ASN1START -- TAG-EUTRA-MULTIBANDINFOLIST-START EUTRA-MultiBandInfoList ::= SEQUENCE (SIZE (1..maxMultiBands)) OF EUTRA-MultiBandInfo EUTRA-MultiBandInfo ::= SEQUENCE { eutra-FreqBandIndicator FreqBandIndicatorEUTRA, eutra-NS-PmaxList EUTRA-NS-PmaxList OPTIONAL -- Need R } -- TAG-EUTRA-MULTIBANDINFOLIST-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
4,410 | 5.8.2.2 UE IP Address Management 5.8.2.2.1 General | The UE IP address management includes allocation and release of the UE IP address as well as renewal of the allocated IP address, where applicable. The UE shall perform the association of the application to a new PDU Session described in clause 6.1.2.2.1 of TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45], with the following considerations: - If there is a matching URSP rule, except the URSP rule with the "match all" Traffic descriptor, or a matching UE Local Configuration containing a PDU Session Type of "IPv4", "IPv6" or "IPv4v6", then the UE shall set the requested PDU Session Type to the PDU Session Type contained in the matching URSP rule or in the matching UE Local Configuration, if this PDU Session Type is supported by the UE's IP stack capabilities Detailed operation is described in TS 24.526[ User Equipment (UE) policies for 5G System (5GS); Stage 3 ] [110]. - Otherwise, if a URSP Rule with the "match all" Traffic descriptor exists, the UE shall set the requested PDU Session Type to the PDU Session Type contained in the "match all" URSP Rule, if this PDU Session Type is supported by the UE's IP stack capabilities. Detailed operation is described in TS 24.526[ User Equipment (UE) policies for 5G System (5GS); Stage 3 ] [110]. - Otherwise, the UE shall set the requested PDU Session Type during the PDU Session Establishment procedure based on its IP stack capabilities as follows: - A UE which supports IPv6 and IPv4 shall set the requested PDU Session Type "IPv4v6". - A UE which supports only IPv4 shall request for PDU Session Type "IPv4". - A UE which supports only IPv6 shall request for PDU Session Type "IPv6". - When the IP version capability of the UE is unknown in the UE (as in the case when the MT and TE are separated and the capability of the TE is not known in the MT), the UE shall request for PDU Session Type "IPv4v6". The SMF selects PDU Session Type of the PDU Session as follows: - If the SMF receives a request with PDU Session Type set to "IPv4v6", the SMF selects either PDU Session Type "IPv4" or "IPv6" or "IPv4v6" based on DNN configuration, subscription data and operator policies. - If the SMF receives a request for PDU Session Type "IPv4" or "IPv6" and the requested IP version is supported by the DNN the SMF selects the requested PDU Session type. In its answer to the UE, the SMF may indicate the PDU Session Types not allowed for the combination of (DNN, S-NNSAI). In this case, the UE shall not request another PDU Session to the same (DNN, S-NNSAI) for PDU Session Types indicated as not allowed by the network. In the case that the initial PDU Session was established with a PDU Session Type and the UE needs another single IP version PDU Session Type, the UE may initiate another PDU Session Establishment procedure to this (DNN, S-NNSAI) in order to activate a second PDU session with that PDU Session Type. An SMF shall ensure that the IP address management procedure is based on the selected PDU Session Type. If IPv4 PDU Session Type is selected, an IPv4 address is allocated to the UE. Similarly, if IPv6 PDU Session type is selected, an IPv6 prefix is allocated. If IPv4v6 PDU Session Type is selected, both an IPv4 address and an IPv6 prefix are allocated. For Roaming case, the SMF in this clause refers to the SMF controlling the UPF(s) acting as PDU Session Anchor. i.e. H-SMF in home routed case and V-SMF in local breakout case. For home routed case, V-SMF forwards the PDU Session Type requested by UE to H-SMF without interpreting it. V-SMF sends back to UE the PDU Session Type selected by H-SMF. The SMF shall process the UE IP address management related messages, maintain the corresponding state information and provide the response messages to the UE. The 5GC and UE support the following mechanisms: a. During PDU Session Establishment procedure, the SMF sends the IP address to the UE via SM NAS signalling. The IPv4 address allocation and/or IPv4 parameter configuration via DHCPv4 (according to RFC 2131 [9]) can also be used once PDU Session is established. b. /64 IPv6 prefix allocation shall be supported via IPv6 Stateless Auto-configuration according to RFC 4862 [10], if IPv6 is supported. The details of Stateless IPv6 Address Autoconfiguration are described in clause 5.8.2.2.3. IPv6 parameter configuration via Stateless DHCPv6 (according to RFC 8415 [182]) may also be supported. IPv6 Prefix Delegation using DHCPv6 may be supported for allocating additional IPv6 prefixes for a PDU Session. The details of Prefix Delegation are described in clause 5.8.2.2.4. For scenarios with RG connecting to 5GC, additional features for IPv6 address allocation and IPv6 prefix delegation are supported, as described in TS 23.316[ Wireless and wireline convergence access support for the 5G System (5GS) ] [84]. To allocate the IP address via DHCPv4, the UE may indicate to the network within the Protocol Configuration Options that the UE requests to obtain the IPv4 address with DHCPv4, or obtain the IP address during the PDU Session Establishment procedure. This implies the following behaviour both for static and dynamic address allocation: - The UE may indicate that it requests to obtain an IPv4 address as part of the PDU Session Establishment procedure. In such a case, the UE relies on the 5GC network to provide IPv4 address to the UE as part of the PDU Session Establishment procedure. - The UE may indicate that it requests to obtain the IPv4 address after the PDU Session Establishment procedure by DHCPv4. That is, when the 5GC network supports DHCPv4 and allows that, it does not provide the IPv4 address for the UE as part of the PDU Session Establishment procedure. The network may respond to the UE by setting the allocated IPv4 Address to 0.0.0.0. After the PDU Session Establishment procedure is completed, the UE uses the connectivity with the 5GC and initiates the IPv4 address allocation on its own using DHCPv4. However, if the 5GC network provides IPv4 address to the UE as part of the PDU Session Establishment procedure, the UE should accept the IPv4 address indicated in the PDU Session Establishment procedure. - If the UE sends no IP Address Allocation request, the SMF determines whether DHCPv4 is used between the UE and the SMF or not, based on per DNN configuration. If dynamic policy provisioning is deployed, and the PCF was not informed of the IPv4 address at PDU Session Establishment procedure, the SMF shall inform the PCF about an allocated IPv4 address. If the IPv4 address is released, the SMF shall inform the PCF about the de-allocation of an IPv4 address. In order to support DHCP based IP address configuration, the SMF shall act as the DHCP server towards the UE. The PDU Session Anchor UPF does not have any related DHCP functionality. The SMF instructs the PDU Session Anchor UPF serving the PDU Session to forward DHCP packets between the UE and the SMF over the user plane. When DHCP is used for external data network assigned addressing and parameter configuration, the SMF shall act as the DHCP client towards the external DHCP server. The UPF does not have any related DHCP functionality. In the case of DHCP server on the external data network, the SMF instructs a UPF with N6 connectivity to forward DHCP packets between the UE and the SMF and the external DHCP server over the user plane. The 5GC may also support the allocation of a static IPv4 address and/or a static IPv6 prefix based on subscription information in the UDM or based on the configuration on a per-subscriber, per-DNN basis and per-S-NSSAI. If the static IP address/prefix is stored in the UDM, during PDU Session Establishment procedure, the SMF retrieves this static IP address/prefix from the UDM. If the static IP address/prefix is not stored in the UDM subscription record, it may be configured on a per-subscriber, per-DNN and per-S-NSSAI basis in the DHCP/DN-AAA server and the SMF retrieves the IP address/prefix for the UE from the DHCP/DN-AAA server. This IP address/prefix is delivered to the UE in the same way as a dynamic IP address/prefix. It is transparent to the UE whether the PLMN or the external data network allocates the IP address and whether the IP address is static or dynamic. For IPv4 or IPv6 or IPv4v6 PDU Session Type, during PDU Session Establishment procedure, the SMF may receive a Subscriber's IP Index from the UDM. If the UE IP address/prefix was not already allocated and provided to PCF when SMF initiates the SM policy association, the SMF may receive a Subscribers IP Index from the PCF. If the SMF received a Subscriber's IP index from both UDM and PCF, the SMF shall apply the Subscriber's IP Index received from the PCF. The SMF may use the Subscriber's IP Index to assist in selecting how the IP address is to be allocated when multiple allocation methods, or multiple instances of the same method are supported. In the case of Home Routed roaming, the H-SMF may receive the IP index from the H-PCF. NOTE: The IP Index can e.g. be used to select between different IP pools, including between IP pools with overlapping private address range. To support deployments with overlapping private IPv4 address, the IP domain corresponding to IP index can also be provided from UDM to SMF as part of the subscription data and then provided to PCF. When Static IP addresses for a PDU session are not used, the actual allocation of the IP Address(es) for a PDU Session may use any of the following mechanisms: - The SMF allocates the IP address from a pool that corresponds to the PDU Session Anchor (UPF) that has been selected - The UE IP address is obtained from the UPF. In that case the SMF shall interact with the UPF via N4 procedures to obtain a suitable IP address. The SMF provides the UPF with the necessary information allowing the UPF to derive the proper IP address (e.g. the network instance). - In the case that the UE IP address is obtained from the external data network, additionally, the SMF shall also send the allocation, renewal and release related request messages to the external data network, i.e. DHCP/DN-AAA server, and maintain the corresponding state information. The IP address allocation request sent to DHCP/DN-AAA server may include the IP address pool ID to identify which range of IP address is to be allocated. In this case the SMF is provisioned with separate IP address pool ID(s), and the mapping between IP address pool ID and UPF Id, DNN, S-NSSAI, IP version. The provision is done by OAM or during the N4 Association Setup procedure. A given IP address pool is controlled by a unique entity (either the SMF or the UPF or an external server). The IP address managed by the UPF can be partitioned into multiple IP address pool partition(s), i.e. associated with multiple IP address pool ID(s). When the SMF is configured to obtain UE IP addresses from the UPF, the SMF may select a UPF based upon support of this feature. The SMF determines whether the UPF supports this feature via NRF or via N4 capability negotiation during N4 Association Setup. If no appropriate UPF support the feature, the SMF may allocate UE IP addresses, if configured to do so. The IP address/prefix is released by the SMF (e.g. upon release of the PDU Session), likewise the UPF considers that any IP address it has allocated within a N4 session are released when this N4 session is released. UPF may use NAT between the UE and the Data Network, and thus the 5GC allocated (private) UE IP address may not be visible on the N6 reference point. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.8.2.2 |
4,411 | – NCR-PeriodicFwdResourceSet | The IE NCR-PeriodicFwdResourceSet is used to configure a list of periodic forwarding resources for NCR-Fwd access link. Each periodic forwarding configuration includes a list of periodic forwarding resources, a common periodicity and a common reference SCS. NCR-PeriodicFwdResourceSet information element -- ASN1START -- TAG-NCR-PERIODICFWDRESOURCESET-START NCR-PeriodicFwdResourceSet-r18 ::= SEQUENCE { periodicFwdRsrcSetId-r18 NCR-PeriodicFwdResourceSetId-r18, periodicFwdRsrcToAddModList-r18 SEQUENCE (SIZE (1..maxNrofPeriodicFwdResource-r18)) OF NCR-PeriodicFwdResource-r18 OPTIONAL, -- Need N periodicFwdRsrcToReleaseList-r18 SEQUENCE (SIZE (1..maxNrofPeriodicFwdResource-r18)) OF NCR-PeriodicFwdResourceId-r18 OPTIONAL, -- Need N referenceSCS-r18 SubcarrierSpacing OPTIONAL, -- Need M priorityFlag-r18 ENUMERATED {true} OPTIONAL, -- Need R ... } NCR-PeriodicFwdResource-r18 ::= SEQUENCE { periodicFwdRsrcId-r18 NCR-PeriodicFwdResourceId-r18, beamIndex-r18 INTEGER (0..63), periodicTimeRsrc-r18 SEQUENCE { periodicityAndOffset-r18 NCR-PeriodicityAndOffset-r18, symbolOffset-r18 INTEGER (0..maxNrofSymbols-1), durationInSymbols-r18 INTEGER (1..112) } } NCR-PeriodicFwdResourceId-r18 ::= INTEGER (0..maxNrofPeriodicFwdResource-1-r18) -- TAG-NCR-PERIODICFWDRESOURCESET-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
4,412 | 10.5.5.12a MS Radio Access capability | The purpose of the MS Radio Access capability information element is to provide the radio part of the network with information concerning radio aspects of the mobile station. The contents might affect the manner in which the network handles the operation of the mobile station. The MS Radio Access capability is a type 4 information element, with a maximum length of 52 octets. The MS Radio Access capability information element is coded as shown in figure 10.5.128a/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.146/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . For the indication of the radio access capabilities the following conditions shall apply: - Among the three Access Type Technologies GSM 900-P, GSM 900-E and GSM 900-R only one shall be present. - Due to shared radio frequency channel numbers between GSM 1800 and GSM 1900, the mobile station should provide the relevant radio access capability for either GSM 1800 band OR GSM 1900 band, not both. - The MS shall indicate its supported Access Technology Types during a single MM procedure. - If the alternative coding by using the Additional access technologies struct is chosen by the mobile station, the mobile station shall indicate its radio access capability for the serving BCCH frequency band in the first included Access capabilities struct, if this information element is not sent in response to an Access Technologies Request from the network or if none of the requested Access Technology Types is supported by the MS. Otherwise, the mobile station shall include the radio access capabilities for the frequency bands it supports in the order of priority requested by the network (see 3GPP TS 44.060[ None ] [76]). - The first Access Technology Type shall not be set to "1111". For error handling the following shall apply: If a received Access Technology Type is unknown to the receiver, it shall ignore all the corresponding fields. If within a known Access Technology Type a receiver recognizes an unknown field it shall ignore it. For more details about error handling of MS radio access capability see 3GPP TS 48.018[ None ] [86]. NOTE: The requirements for the support of the A5 algorithms in the MS are specified in 3GPP TS 43.020[ Security related network functions ] [13]. Figure 10.5.128a/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] MS Radio Access Capability information element Table 10.5.146/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : MS Radio Access Capability Information Element < MS RA capability value part > ::= < MS RA capability value part struct > <spare bits>**; -- may be used for future enhancements <MS RA capability value part struct >::= --recursive structure allows any number of Access technologies { { < Access Technology Type: bit (4) > exclude 1111 < Access capabilities : <Access capabilities struct> > } | { < Access Technology Type: bit (4) == 1111 > -- structure adding Access technologies with same capabilities < Length : bit (7) > -- length in bits of list of Additional access technologies and spare bits < bit (val (Length)) & { { 1 < Additional access technologies: < Additional access technologies struct > > } ** 0 <spare bits>** } > } } { 0 | 1 <MS RA capability value part struct> } ; < Additional access technologies struct > ::= < Access Technology Type : bit (4) > < GMSK Power Class : bit (3) > < 8PSK Power Class : bit (2) > ; < Access capabilities struct > ::= < Length : bit (7) > -- length in bits of Content and spare bits < bit (val (Length)) & { <Access capabilities : <Content>> <spare bits>** } > ; -- expands to the indicated length < Content > ::= < RF Power Capability : bit (3) > { 0 | 1 <A5 bits : <A5 bits> > } -- zero means that the same values apply for parameters as in the immediately preceding Access capabilities field within this IE < ES IND : bit > < PS : bit > < VGCS : bit > < VBS : bit > { 0 | 1 < Multislot capability : Multislot capability struct > } -- zero means that the same values for multislot parameters as given in an earlier Access capabilities field within this IE apply also here -- Additions in release 99 { 0 | 1 < 8PSK Power Capability : bit(2) >} < COMPACT Interference Measurement Capability : bit > < Revision Level Indicator : bit > < UMTS FDD Radio Access Technology Capability : bit > -- 3G RAT < UMTS 3.84 Mcps TDD Radio Access Technology Capability : bit > -- 3G RAT < CDMA 2000 Radio Access Technology Capability : bit > -- 3G RAT -- Additions in release 4 < UMTS 1.28 Mcps TDD Radio Access Technology Capability: bit > -- 3G RAT < GERAN Feature Package 1 : bit > { 0 | 1 < Extended DTM GPRS Multi Slot Class : bit(2) > < Extended DTM EGPRS Multi Slot Class : bit(2) > } < Modulation based multislot class support : bit > -- Additions in release 5 { 0 | 1 < High Multislot Capability : bit(2) > } 0 -- The value '1' was allocated in an earlier version of the protocol and shall not be used. < GMSK Multislot Power Profile : bit (2) > < 8-PSK Multislot Power Profile : bit (2) > -- Additions in release 6 < Multiple TBF Capability : bit > < Downlink Advanced Receiver Performance : bit(2) > < Extended RLC/MAC Control Message Segmentation Capability : bit > < DTM Enhancements Capability : bit > { 0 | 1 < DTM GPRS High Multi Slot Class : bit(3) > { 0 | 1 < DTM EGPRS High Multi Slot Class : bit(3) > } } < PS Handover Capability : bit > -- Additions in release 7 < DTM Handover Capability : bit > { 0 | 1 < Multislot Capability Reduction for Downlink Dual Carrier: bit (3) > < Downlink Dual Carrier for DTM Capability : bit> } < Flexible Timeslot Assignment : bit > < GAN PS Handover Capability : bit > < RLC Non-persistent Mode : bit > < Reduced Latency Capability : bit > < Uplink EGPRS2 : bit(2) > < Downlink EGPRS2 : bit(2) > -- Additions in release 8 < E-UTRA FDD support : bit > < E-UTRA TDD support : bit > < GERAN to E-UTRA support in GERAN packet transfer mode: bit(2) > < Priority-based reselection support : bit > -- Additions in release 9 < Enhanced Flexible Timeslot Assignment : Enhanced Flexible Timeslot Assignment struct> < Indication of Upper Layer PDU Start Capability for RLC UM : bit > < EMST Capability : bit > < MTTI Capability : bit > < UTRA CSG Cells Reporting : bit > < E-UTRA CSG Cells Reporting : bit > -- Additions in release 10 < DTR Capability : bit > < EMSR Capability : bit > < Fast Downlink Frequency Switching Capability : bit > < TIGHTER Capability : bit(2) > -- Additions in release 11 < FANR Capability : bit > < IPA Capability : bit> < GERAN Network Sharing support : bit> < E-UTRA Wideband RSRQ measurements support : bit> -- Additions in release 12 < UTRA Multiple Frequency Band Indicators support : bit > < E-UTRA Multiple Frequency Band Indicators support : bit > { 0 -- DLMC not supported | 1 < DLMC Capability : DLMC Capability struct > } < Extended TSC Set Capability support : bit > -- Late addition of a release 11 feature < Extended EARFCN value range: bit> -- Additions in release 13 < (EC-)PCH monitoring support: bit(2)> -- Additions in release 14 { 0 -- Default requirement as specified in TS 45.010[ None ] applies | 1 < MS Sync Accuracy: bit (4) > } < EC uplink coverage enhancement support : bit (1)> -- Additions in release 15 < MTA Access Security support: bit(1) > < EC paging indication channel monitoring support: bit(1) >; -- error: struct too short, assume features do not exist -- error: struct too long, ignore data and jump to next Access technology Table 10.5.146/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] (continued): MS Radio Access Capability IE Table 10.5.146/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] (concluded): MS Radio Access Capability IE | 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.12a |
4,413 | 28.17 DNS subdomain for operator usage in 5GC | The 5GC nodes DNS subdomain (DNS zone) shall be derived from the MNC and MCC by adding the label "node" to the beginning of the Home Network Domain for 5GC (see clause 28.2) and shall be constructed as: node.5gc.mnc<MNC>.mcc<MCC>.3gppnetwork.org This DNS subdomain is formally placed into the operator's control. 3GPP shall never take this DNS subdomain back or any zone cut/subdomain within it for any purpose. As a result the operator can safely provision any DNS records it chooses under this subdomain without concern about future 3GPP standards encroaching on the DNS names within this zone. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 28.17 |
4,414 | 10.3.2.2 FPBI class A | This class is intended to be used for small residential and private (PBX) single cell CTS-FP. bit No 19 1 +-------------------------------------+ |0 0| | +-------------------+ Type| FPN | FPBI 19 bits <-------------------------------------> Figure 15: Structure of FPBI class A The FPBI class A is composed of the following elements: - FPBI Class A Type. Its length is 2 bits and its value is 00; - Fixed Part Number (FPN). Its length is 17 bits. The FPN contains the least significant bits of the Serial Number part of the IFPEI. The FPBI Length Indicator shall be set to 19 for a class A FPBI. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 10.3.2.2 |
4,415 | – SL-MeasConfigCommon | The IE SL-MeasConfigCommon is used to set the cell specific SL RSRP measurement configurations for unicast destinations. SL-MeasConfigCommon information element -- ASN1START -- TAG-SL-MEASCONFIGCOMMON-START SL-MeasConfigCommon-r16 ::= SEQUENCE { sl-MeasObjectListCommon-r16 SL-MeasObjectList-r16 OPTIONAL, -- Need R sl-ReportConfigListCommon-r16 SL-ReportConfigList-r16 OPTIONAL, -- Need R sl-MeasIdListCommon-r16 SL-MeasIdList-r16 OPTIONAL, -- Need R sl-QuantityConfigCommon-r16 SL-QuantityConfig-r16 OPTIONAL, -- Need R ... } -- TAG-SL-MEASCONFIGCOMMON-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
4,416 | 4.3.5.2 Change of SSC mode 3 PDU Session Anchor with multiple PDU Sessions | The following procedure is triggered by SMF in order to change the PDU Session Anchor serving a PDU Session of SSC mode 3 for a UE. This procedure releases the existing PDU Session associated with an old PDU Session Anchor (i.e. UPF1 in figure 4.3.5.2-1) after having established a new PDU Session to the same DN with a new PDU Session Anchor (i.e. UPF2 in figure 4.3.5.2-1), which is controlled by the same SMF. The SMF may determine that a new SMF needs to be reallocated. Figure 4.3.5.2-1: Change of SSC mode 3 PDU Session Anchor with multiple PDU Sessions 1. The SMF determines that the serving UPF or the SMF needs to be changed. If the "Indication of application relocation possibility" attributes in the PCC rule indicates no DNAI change takes place once selected for this application, the SMF determines that the SMF can not be changed. 1a. If the UPF (PSA) cannot connect to the target DNAI(s) that SMF received from SM-PCF, the SMF invokes Nsmf_PDUSession_SMContextStatusNotify Request (target DNAI information) service operation to the AMF. The SMF also indicate the SMF selection is expected. If the runtime coordination between 5GC and AF (Figure 4.3.6.3-1) is enabled, the SMF includes in the Nsmf_PDUSession_SMContextStatusNotify Request the SM Context ID as a reference to the SM Context that includes AF Coordination Information stored in the SMF. The target DNAI information are used for SMF selection which can control UPF connecting to that DNAI at next PDU session establishment towards the same DNN and S-NSSAI. Due to it is for SMF selection, the AMF stores the target DNAI information received from SMF selection. The target DNAI information is not transferred outside, e.g. to support the UE context transfer between AMFs for AMF relocation. 2. If the SMF had sent an early notification to the AF and the runtime coordination between 5GC and AF is enabled based on local configuration as specified in clause 4.3.6.3, according to the indication of "AF acknowledgment to be expected" included in AF subscription to SMF events, the SMF waits for a notification response from the AF. If the SMF receives a negative notification response from the AF, the SMF may stop the procedure. This is defined in Figure 4.3.6.3-1. The SMF invokes the Namf_Communication_N1N2MessageTransfer (PDU Session ID, SMF Reallocation requested indication, N1 SM container (PDU Session Modification Command (Cause, PCO (PDU Session Address Lifetime value)))) where PDU Session ID indicates the existing PDU Session to be relocated and Cause indicates that a PDU Session re-establishment to the same DN is required. The SMF Reallocation requested indication indicates whether the SMF is requested to be reallocated. The PDU Session Address Lifetime value is delivered to the UE upper layers in PCO and indicates how long the network is willing to maintain the PDU Session. The SMF starts a PDU Session Release timer corresponding to the PDU Session Address Lifetime value. 3a. The AMF forwards the NAS message to the UE. The UE can provide the release timer value to the upper layers if received in the PDU Session Modification Command. 3b. The UE acknowledges the PDU Session Modification Command. 3c. The AMF forwards the N1 SM container (PDU Session Modification Command ACK) received from the (R)AN to the SMF1 via Nsmf_PDUSession_UpdateSMContext service operation. 3d. The SMF1 replies with a Nsmf_PDUSession_UpdateSMContext Response. 4. If the UE receives PDU Session Modification Command, the UE may decide to initiate the PDU Session Establishment procedure described in clause 4.3.2.2, to the same DN with the following differences: In Step 1 of clause 4.3.2.2.1, according to the SSC mode, UE generates a new PDU Session ID and initiates the PDU Session Establishment Request using the new PDU Session ID. The new PDU Session ID is included as PDU Session ID in the NAS request message and the Old PDU Session ID which indicates the existing PDU Session to be released is also provided to AMF in the NAS request message. In Step 2 of clause 4.3.2.2.1, if SMF reallocation was requested in Step 2 of this clause, the AMF selects a different SMF. Otherwise, the AMF sends the Nsmf_PDUSession_CreateSMContext Request to the same SMF serving the Old PDU Session ID. If target DNAI information has been received from old SMF (i.e. SMF1), for the PDU Session toward same DNN and S-NSSAI the AMF selects the new SMF using the stored target DNAI information. The AMF includes the target DNAI in the Nsmf_PDUSession_CreateSMContext Request and deletes the stored target DNAI information. If the AMF has received the SM Context ID from the old SMF, the AMF includes the SM Context ID in the Nsmf_PDUSession_CreateSMContext Request. In Step 3 of clause 4.3.2.2.1, if the SMF is not to be reallocated, the AMF include both PDU Session ID and Old PDU Session ID in Nsmf_PDUSession_CreateSMContext Request. The SMF detects that the PDU Session establishment request is related to the trigger in step 2 based on the presence of an Old PDU Session ID in the Nsmf_PDUSession_CreateSMContext Request. In Step 3 of clause 4.3.2.2.1, the SMF stores the new PDU Session ID and selects a new PDU Session Anchor (i.e. UPF2) for the new PDU Session. If the new SMF receives an SM Context ID in the Nsmf_PDUSession_CreateSMContext Request, the new SMF retrieves the AF Coordination Information by sending a Nsmf_PDUSession_ContextRequest to the old SMF and indicates that "AF Coordination Information" part of 5G SM Context is requested. If the SMF receives a target DNAI in the Nsmf_PDUSession_CreateSMContext Request, the SMF selects the new PDU Session Anchor using the target DNAI. If the AF Coordination Information in the Nsmf_PDUSession_ContextRequest Response includes a notification correlation id associated with an "uplink buffering" indication, the SMF may also indicate PSA2 to buffer the uplink data associated with the same notification correlation id in the PCC Rules. If the PCC Rules received from the PCF as in step 7b or step 9 in clause 4.3.2.2.1 indicate that a late notification is requested by the AF (directly or via NEF), the SMF sends a late notification to the AF before step 11 of clause 4.3.2.2.1 in Nsmf_EventExposure_Notify service operation, as in step 4a or step 4c in Figure 4.3.6.3-1 (directly or via NEF, respectively). The late notification contains the Source DNAI and the UE IP address in the Source DNAI included in the AF Coordination Information as received in the Nsmf_PDUSession_CreateSMContext Response from the old SMF. If the SMF received a negative notification response from the AF, the SMF may stop the procedure. This is defined in Figure 4.3.6.3-1. Otherwise the SMF continue the following procedures to activate the UP path of the new PDU Session. The SMF may also indicate PSA2 to stop buffering and start forwarding uplink data. 5. After the new PDU Session is established the UE starts using the IP address/prefix associated with the new PDU Session for all new traffic and may also proactively move existing traffic flow (where possible) from the old PDU Session to the new PDU Session. NOTE: The mechanisms used by the UE to proactively move existing traffic flows from one IP address/prefix to another are outside the scope of 3GPP specifications. 6. The old PDU Session is released as described in clause 4.3.4 either by the UE before the timer provided in step 3 expires (e.g. once the UE has consolidated all traffic on new PDU Session or if the session is no more needed) or by the SMF upon expiry of this timer. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.3.5.2 |
4,417 | – MeasurementReportAppLayer | The MeasurementReportAppLayer message is used for sending application layer measurement report. Signalling radio bearer: SRB4, SRB5 RLC-SAP: AM Logical channel: DCCH Direction: UE to Network MeasurementReportAppLayer message -- ASN1START -- TAG-MEASUREMENTREPORTAPPLAYER-START MeasurementReportAppLayer-r17 ::= SEQUENCE { criticalExtensions CHOICE { measurementReportAppLayer-r17 MeasurementReportAppLayer-r17-IEs, criticalExtensionsFuture SEQUENCE {} } } MeasurementReportAppLayer-r17-IEs ::= SEQUENCE { measurementReportAppLayerList-r17 MeasurementReportAppLayerList-r17, lateNonCriticalExtension OCTET STRING OPTIONAL, nonCriticalExtension MeasurementReportAppLayer-v1800-IEs OPTIONAL } MeasurementReportAppLayer-v1800-IEs ::= SEQUENCE { measurementReportAppLayerList-r18 MeasurementReportAppLayerList-r18 OPTIONAL, nonCriticalExtension SEQUENCE{} OPTIONAL } MeasurementReportAppLayerList-r17 ::= SEQUENCE (SIZE (1..maxNrofAppLayerMeas-r17)) OF MeasReportAppLayer-r17 MeasurementReportAppLayerList-r18 ::= SEQUENCE (SIZE (1..maxNrofAppLayerMeas-r17)) OF MeasReportAppLayer-r18 MeasReportAppLayer-r17 ::= SEQUENCE { measConfigAppLayerId-r17 MeasConfigAppLayerId-r17, measReportAppLayerContainer-r17 OCTET STRING OPTIONAL, appLayerSessionStatus-r17 ENUMERATED {start, stop} OPTIONAL, ran-VisibleMeasurements-r17 RAN-VisibleMeasurements-r17 OPTIONAL } MeasReportAppLayer-r18 ::= SEQUENCE { idleInactiveConfig-r18 AppLayerIdleInactiveConfig-r18 OPTIONAL, ... } RAN-VisibleMeasurements-r17 ::= SEQUENCE { appLayerBufferLevelList-r17 SEQUENCE (SIZE (1..8)) OF AppLayerBufferLevel-r17 OPTIONAL, playoutDelayForMediaStartup-r17 INTEGER (0..30000) OPTIONAL, pdu-SessionIdList-r17 SEQUENCE (SIZE (1..maxNrofPDU-Sessions-r17)) OF PDU-SessionID OPTIONAL, ..., [[ pdu-SessionIdList-r18 SEQUENCE (SIZE (1..maxNrofPDU-Sessions-r17)) OF QFI-List-r18 OPTIONAL ]] } AppLayerBufferLevel-r17 ::= INTEGER (0..30000) QFI-List-r18 ::= SEQUENCE (SIZE (1..maxNrofQFIs)) OF QFI -- TAG-MEASUREMENTREPORTAPPLAYER-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
4,418 | 7.8.1D Minimum requirements for ProSe | The throughput shall be ≥ 95% of the maximum throughput of the reference measurement channels as specified in Annex A.6.2 with parameters specified in Table 7.8.1D-1, Table 7.8.1D-2, and Table 7.8.1D-3 for the specified wanted signal mean power in the presence of two interfering signals Table 7.8.1D-1: Wide band intermodulation parameters for ProSe Direct Discovery Table 7.8.1D-2: Wide band intermodulation for ProSe Direct Communication Table 7.8.1D-3: Wide band intermodulation for ProSe For the UE which supports inter band CA configuration in Table 7.3.1-1A, Pinterferer1 and Pinterferer2 powers defined in Table 7.8.1D-3 are increased by the amount given by ΔRIB,c in Table 7.3.1-1A. | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 7.8.1D |
4,419 | 4.13.2.5 Number of attempted additions of LWA DRB | a) This measurement provides the number of attempted additions of LWA DRB. b) CC c) On transmission of RRCConnectionReconfiguration message which includes the drb-ToAddModList in the radioResourceConfigDedicated information element by the eNB, and the drb-ToAddModList contains at least one drb-Identity that is not part of the current UE configuration and the drb-TypeLWA of this DRB set to TRUE (see TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [18]). d) An integer value e) LWI.LwaDrbAddAtt f) WLANMobilitySet g) Valid for packet switched traffic h) EPS | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.13.2.5 |
4,420 | – SIB8 | SIB8 contains a CMAS notification. SIB8 information element -- ASN1START -- TAG-SIB8-START SIB8 ::= SEQUENCE { messageIdentifier BIT STRING (SIZE (16)), serialNumber BIT STRING (SIZE (16)), warningMessageSegmentType ENUMERATED {notLastSegment, lastSegment}, warningMessageSegmentNumber INTEGER (0..63), warningMessageSegment OCTET STRING, dataCodingScheme OCTET STRING (SIZE (1)) OPTIONAL, -- Cond Segment1 warningAreaCoordinatesSegment OCTET STRING OPTIONAL, -- Need R lateNonCriticalExtension OCTET STRING OPTIONAL, ... } -- TAG-SIB8-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
4,421 | 6.3.3.2 Network-requested PDU session release procedure initiation | In order to initiate the network-requested PDU session release procedure, the SMF shall create a PDU SESSION RELEASE COMMAND message. The SMF shall set the 5GSM cause IE of the PDU SESSION RELEASE COMMAND message to indicate the reason for releasing the PDU session. The 5GSM cause IE typically indicates one of the following 5GSM cause values: #8 operator determined barring; #26 insufficient resources; #29 user authentication or authorization failed; #36 regular deactivation; #38 network failure; #39 reactivation requested; #46 out of LADN service area; #67 insufficient resources for specific slice and DNN; #69 insufficient resources for specific slice. If the selected SSC mode of the PDU session is "SSC mode 2" and the SMF requests the relocation of SSC mode 2 PDU session anchor with different PDU sessions as specified in 3GPP TS 23.502[ Procedures for the 5G System (5GS) ] [9], the SMF shall include 5GSM cause #39 "reactivation requested". If the selected SSC mode of the PDU session is "SSC mode 2" or "SSC mode 1", the S-NSSAI or the mapped S-NSSAI of the PDU session needs to be replaced, the SMF shall include the Alternative S-NSSAI IE and 5GSM cause #39 "reactivation requested" in the PDU SESSION RELEASE COMMAND message. NOTE 1: The relocation of SSC mode 2 PDU session anchor with different PDU sessions can also be initiated by the SMF in case of the SMF is requested by the AMF to release the PDU session due to the network slice instance of the PDU session is changed as specified in subclause 5.15.5.3 of 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8]. If the network-requested PDU session release procedure is triggered by a UE-requested PDU session release procedure, the SMF shall set the PTI IE of the PDU SESSION RELEASE COMMAND message to the PTI of the PDU SESSION RELEASE REQUEST message received as part of the UE-requested PDU session release procedure and shall not include the Access type IE in the PDU SESSION RELEASE COMMAND. If the network-requested PDU session release procedure is not triggered by a UE-requested PDU session release procedure, the SMF shall set the PTI IE of the PDU SESSION RELEASE COMMAND message to "No procedure transaction identity assigned". If the PDU session ID included in PDU SESSION RELEASE COMMAND message is associated with one or more multicast MBS sessions and either the Access type IE is not included or the Access type IE indicates "3GPP access", the SMF shall consider the UE as removed from the associated multicast MBS sessions. Based on the local policy and user's subscription data, if the SMF decides to release the PDU session after determining: a) the UE has moved between a tracking area in NB-N1 mode and a tracking area in WB-N1 mode; b) the UE has moved between a tracking area in NB-S1 mode and a tracking area in WB-N1 mode; c) the UE has moved between a tracking area in WB-S1 mode and a tracking area in NB-N1 mode; or d) a PDU session is not only for control plane CIoT 5GS optimization any more, the SMF shall: a) include the 5GSM cause value #39 "reactivation requested" in the 5GSM cause IE of the PDU SESSION RELEASE COMMAND message; or b) include a 5GSM cause value other than #39 "reactivation requested" in the 5GSM cause IE of the PDU SESSION RELEASE COMMAND message. NOTE 2: The included 5GSM cause value is up to the network implementation. If the SMF receives UE presence in LADN service area from the AMF indicating that the UE is out of the LADN service area and the SMF decides to release the PDU session, the SMF shall include the 5GSM cause value #46 "out of LADN service area" in the 5GSM cause IE of the PDU SESSION RELEASE COMMAND message. Upon receipt of the 5GSM cause value #46 "out of LADN service area" in the 5GSM cause IE of the PDU SESSION RELEASE COMMAND message, the UE shall release the PDU session. The SMF may include a Back-off timer value IE in the PDU SESSION RELEASE COMMAND message when the 5GSM cause value #26 "insufficient resources" is included in the PDU SESSION RELEASE COMMAND message. If the 5GSM cause value is #26 "insufficient resources" and the PDU SESSION RELEASE COMMAND message is sent to a UE configured for high priority access in selected PLMN or SNPN or the request type was set to "initial emergency request" or "existing emergency PDU session" for the establishment of the PDU session, the network shall not include a Back-off timer value IE. The SMF may include a Back-off timer value IE in the PDU SESSION RELEASE COMMAND message when the 5GSM cause value #67 "insufficient resources for specific slice and DNN" is included in the PDU SESSION RELEASE COMMAND message. If the 5GSM cause value is #67 "insufficient resources for specific slice and DNN" and the PDU SESSION RELEASE COMMAND message is sent to a UE configured for high priority access in selected PLMN or SNPN or the request type was set to "initial emergency request" or "existing emergency PDU session" for the establishment of the PDU session, the network shall not include a Back-off timer value IE. The SMF may include a Back-off timer value IE in the PDU SESSION RELEASE COMMAND message when the 5GSM cause #69 "insufficient resources for specific slice" is included in the PDU SESSION RELEASE COMMAND message. If the 5GSM cause value is #69 "insufficient resources for specific slice" and the PDU SESSION RELEASE COMMAND message is sent to a UE configured for high priority access in selected PLMN or SNPN or the request type was set to "initial emergency request" or "existing emergency PDU session" for the establishment of the PDU session, the network shall not include a Back-off timer value IE. The SMF should include a Back-off timer value IE in the PDU SESSION RELEASE COMMAND message when the 5GSM cause value #29 "user authentication or authorization failed" is included in the PDU SESSION RELEASE COMMAND message. If the service-level-AA procedure is triggered for the established PDU session for UAS services with re-authentication purpose, and the SMF is informed by the UAS-NF that UUAA-SM is unsuccessful or if the SMF receives UUAA revocation notification message from the UAS-NF as described in 3GPP TS 23.256[ Support of Uncrewed Aerial Systems (UAS) connectivity, identification and tracking; Stage 2 ] [6AB], the SMF shall transmit the PDU SESSION RELEASE COMMAND message to the UE, including: a) the service-level-AA response in the Service-level-AA container IE, with the SLAR field set to the value of "Service level authentication and authorization was not successful or service level authorization is revoked"; and b) the 5GSM cause value #29 "user authentication or authorization failed" in the 5GSM cause IE of the PDU SESSION RELEASE COMMAND message. If the PDU session was established for C2 communication and the SMF is informed by UAS-NF that C2 authorization is revoked, the SMF shall include: a) the service-level-AA response with the value of the C2AR field set to the "C2 authorization was not successful or C2 authorization is revoked" in the service-level-AA container IE of the PDU SESSION RELEASE COMMAND message, and b) the 5GSM cause value #29 "user authentication or authorization failed" in the 5GSM cause IE of the PDU SESSION RELEASE COMMAND message. The SMF shall send: a) the PDU SESSION RELEASE COMMAND message; and b) the N1 SM delivery skip allowed indication: 1) if the SMF allows the AMF to skip sending the N1 SM container to the UE and the 5GSM cause IE is not set to #39 "reactivation requested"; or 2) if the SMF allows the AMF to skip sending the N1 SM container to the UE and the Access type IE is not included towards the AMF, and the SMF shall start timer T3592 (see example in figure 6.3.3.2.1). Figure 6.3.3.2.1: Network-requested PDU session release procedure | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.3.3.2 |
4,422 | 28.3.2.5 AMF Name | The AMF Name FQDN shall uniquely identify an AMF. The AMF Name FQDN for an AMF within an operator's PLMN shall be constructed as follows: "<AMF-id>.amf.5gc.mnc<MNC>.mcc<MCC>.3gppnetwork.org" where - the <MNC> and <MCC> shall identify the PLMN where the AMF is located and shall be encoded as - <MNC> = 3 digits - <MCC> = 3 digits If there are only 2 significant digits in the MNC, one "0" digit shall be inserted at the left side to fill the 3 digits coding of MNC in the AMF Name FQDN. - the <AMF-id> shall contain at least one label. As example, - If <AMF-id> is amf1.cluster1.net2, the AMF Name FQDN for MCC 345 and MNC 12 is: "amf1.cluster1.net2.amf.5gc.mnc012.mcc345.3gppnetwork.org" The AMF Name FQDN for an AMF within an operator's SNPN, if not pre-configured in the NF, shall be constructed as follows: "<AMF-id>.amf.5gc.nid<NID>.mnc<MNC>.mcc<MCC>.3gppnetwork.org" where - <MNC> and <MCC> shall be encoded as specified above; - NID shall be encoded as hexadecimal digits as specified in clause 12.7. As example, - If <AMF-id> is amf1.cluster1.net2, the AMF Name FQDN for MCC 345, MNC 12 and NID 000007ed9d5 (hexadecimal) is: "amf1.cluster1.net2.amf.5gc.nid000007ed9d5.mnc012.mcc345.3gppnetwork.org" | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 28.3.2.5 |
4,423 | 6.1.2 Grouped Information Elements | Information elements can contain other IEs. This type of IE is called "Grouped IEs". Grouped IEs have a length value in the TLIV encoding, which includes the added length of all the embedded IEs. Overall coding of a grouped information element with 4 octets long IE header is defined in clause 8.2 "Information Element Format". Each information element within a grouped IE also shall also contain 4 octets long IE header. Grouped IEs are not marked by any flag or limited to a specific range of IE type values. The clause describing an IE in this specification shall explicitly state if it is grouped. NOTE 1: Each entry into each Grouped IE creates a new scope level. Exit from the grouped IE closes the scope level. The GTPv2 message level is the top most scope. This is analogous to the local scope of a subroutine/function. If more than one grouped information elements of the same type, but for a different purpose are sent with a message, these IEs shall have different Instance values. If more than one grouped information elements of the same type and for the same purpose are sent with a message, these IEs shall have exactly the same Instance value to represent a list. NOTE 2: For instance, all "Bearer Contexts Modified" IEs of the type "Bearer Context" in a "Modify Bearer Response" message shall have the Instance value of 0, while all "Bearer Contexts Marked for Removal" IEs of the type "Bearer Context" in the same message shall have the Instance value of 1. | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 6.1.2 |
4,424 | 5.9.3.2 Requirements for Security Edge Protection Proxy (SEPP) | The SEPP shall act as a non-transparent proxy node. The SEPP shall protect application layer control plane messages between two NFs belonging to different PLMNs or SNPNs that use the N32 interface to communicate with each other. The SEPP shall perform mutual authentication and negotiation of cipher suites with the SEPP in the roaming network. The SEPP shall handle key management aspects that involve setting up the required cryptographic keys needed for securing messages on the N32 interface between two SEPPs. The SEPP shall perform topology hiding by limiting the internal topology information visible to external parties. As a reverse proxy the SEPP shall provide a single point of access and control to internal NFs. The receiving SEPP shall be able to verify whether the sending SEPP is authorized to use the PLMN ID or SNPN ID in the received N32 message. The SEPP to SEPP communication may go via up to two Roaming Intermediaries. The changes made by Roaming Intermediaries to messages originated by a SEPP, based on the originating PLMNs policy, shall be identifiable by the receiving SEPP. The SEPP shall be able to clearly differentiate between certificates used for authentication of peer SEPPs and certificates used for authentication of Roaming Intermediaries performing message modifications. The SEPP shall support multiple trust anchors. NOTE 1: Such a differentiation and support of multiple trust anchors could be done, e.g. , by implementing separate certificate storages. The SEPP shall discard malformed N32 signaling messages. The sending SEPP shall reject messages received from the NF (directly or via SCP) with JSON including "encBlockIndex" (regardless of the encoding used for that JSON request). The receiving SEPP shall reject any message in which a Roaming Intermediary has inserted or relocated references to encBlockIndex. The SEPP shall implement rate-limiting functionalities to defend itself and subsequent NFs against excessive CP signaling. This includes SEPP-to-SEPP signaling messages. The SEPP shall implement anti-spoofing mechanisms that enable cross-layer validation of source and destination address and identifiers (e.g. FQDNs or PLMN IDs). NOTE 2: An example for such an anti-spoofing mechanism is the following: If there is a mismatch between different layers of the message or the destination address does not belong to the SEPP’s own PLMN (or SNPN), the message is discarded. The SEPP shall be able to use one or more PLMN IDs (or SNPN IDs). In the situation that a PLMN (or SNPN) is using more than one PLMN ID (or SNPN ID), this PLMN’s SEPP (or SNPN’s SEPP) may use the same N32-connection for all of the networks PLMN IDs (or SNPN IDs), with each of the PLMN’s (or SNPN’s) remote partners. If different PLMNs (or SNPNs) are represented by the PLMN IDs (or SNPN IDs) supported by a SEPP, the SEPP shall use separate N32-connections for each pair of home and visited PLMN (or SNPN). NOTE 3: If PRINS is used by a roaming hub, the roaming hub can use the same N32-f connection between the roaming hub and the adjecent PLMNs for the PLMNs accessed via the roaming hub NOTE 4: in this case PRINS provides origin authentication and the originatining PLMN_ID. Error messages may be originated from either PLMN SEPPs to adjacent Roaming Hubs or Roaming Hubs to adjacent PLMN SEPPs, in an identifiable way. Editor's Note: Whether the error messages are on N32 layer or on SBA signalling layer or both is ffs. If allowed by the PLMN policy, the SEPP shall be able to send error messages on the N32 interface to a roaming hub via the N32-f. Specific error messages relevant to Roaming Hubs shall be supported (such as 'an IE is encrypted while it was expected to be available in the clear', 'an IE is not encrypted while its availability in the clear is not required', 'the N32 connection cannot be setup due to contractual reasons', 'the N32 connection cannot be setup due to a connectivity issue' and 'the message was not delivered due to contractual reasons'). Sending SEPP behavior for the 3gpp-Sbi-Originating-Network-Id header specified in TS 29.500[ 5G System; Technical Realization of Service Based Architecture; Stage 3 ] [74]: - If the sending NF or the SCP has inserted the 3gpp-Sbi-Originating-Network-Id header in the signaling message (service/subscription request or notification message), the sending SEPP shall compare the PLMN ID in the 3gpp-Sbi-Originating-Network-Id header in the received signaling message with the PLMN ID(s) that the sending SEPP represents by its certificate. - If the PLMN ID does not match with any of the PLMN IDs that the sending SEPP represents, the sending SEPP shall discard the received signaling message. - If the PLMN ID matches with any of the PLMN IDs that the sending SEPP represents, the sending SEPP shall forward the signaling message to the receiving SEPP. - If the sending NF and the SCP have not included the 3gpp-Sbi-Originating-Network-Id header in the signalling message, the sending SEPP shall include the 3gpp-Sbi-Originating-Network-Id header and send the updated signaling message to the receiving SEPP. - If the sending SEPP only represents one PLMN-ID, the sending SEPP shall insert the 3gpp-Sbi-Originating-Network-Id header with this ID. - If the sending SEPP represents multiple PLMN-IDs, it is up to configuration and deployment to determine which PLMN-ID value should be included in the header. Receiving SEPP behavior for the 3gpp-Sbi-Originating-Network-Id header: - The receiving SEPP shall check whether the 3gpp-Sbi-Originating-Network-Id header included in the signalling message belongs to the sending SEPP’s own PLMN. It does this by verifying that the asserted PLMN ID in the 3gpp-Sbi-Originating-Network-Id header matches one of the sending SEPP's own PLMN ID(s) either in the N32-f context, the sending SEPP's certificate, or a locally configured list of PLMN-IDs that the sending SEPP represents. - If the 3gpp-Sbi-Originating-Network-Id header does not match with any of the PLMN IDs belonging to the peer sending SEPP, the receving SEPP shall discard the received signaling message. - If the 3gpp-Sbi-Originating-Network-Id header matches with any PLMN ID of the PLMN IDs belonging to the peer sending SEPP, the header is successfully verified, and the receiving SEPP shall forward the received signaling message to the target NF. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 5.9.3.2 |
4,425 | 4.11.1.2.2 EPS to 5GS handover using N26 interface | 4.11.1.2.2.1 General N26 interface is used to provide seamless session continuity for single registration mode. The procedure involves a handover to 5GS and setup of QoS Flows in 5GS. In the home routed roaming case, the PGW-C+ SMF in the HPLMN always receives the PDU Session ID from UE and provides PDN Connection associated 5G QoS parameter(s) and S-NSSAI to the UE. This also applies in the case that the HPLMN operates the interworking procedure without N26. In the case of handover to a shared 5GS network, the source E-UTRAN determines a PLMN to be used in the target network as specified by clause 5.2a of TS 23.251[ Network sharing; Architecture and functional description ] [35] for eNodeB functions. A supporting MME may provide the AMF via N26 with an indication that source EPS PLMN is a preferred PLMN when that PLMN is available at later change of the UE to an EPS shared network. NOTE 1: If the UE has active EPS bearer for normal voice or IMS emergency voice, the source E-UTRAN can be configured to not trigger any handover to 5GS. If the PDN Type of a PDN Connection in EPS is non-IP and is locally associated in UE and SMF to PDU Session Type Ethernet or Unstructured, the PDU Session Type in 5GS shall be set to Ethernet or Unstructured respectively. NOTE 2: If the non-IP PDN Type is locally associated in UE and SMF to PDU Session Type Ethernet, it means that Ethernet PDN Type is not supported in EPS. NOTE 3: The IP address continuity can't be supported, if SMF+PGW-C in the HPLMN doesn't provide the mapped QoS parameters. In order to support the E-UTRAN NTN enhancements defined in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [46], for handover from EPS to 5GS, the following applies related to handling of UE's radio capabilities: - If the target NG-RAN node knows (e.g. by configuration) that the UE's E-UTRA radio capabilities applicable to the target NG-RAN node may be different to the E-UTRA radio capabilities stored in the source eNodeB (e.g. for handover from an eNodeB that supports the NTN enhancements as defined in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [46]), then the target NG-RAN node shall trigger retrieval of the E-UTRA radio capability information again from the UE. In order to support the E-UTRAN NTN enhancements defined in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [46], for handover from 5GS to EPS, the following applies related to handling of UE's radio capabilities: - If the target eNodeB node knows (e.g. by configuration) that the UE's E-UTRA radio capabilities applicable to the target eNodeB may be different to the E-UTRA radio capabilities stored in the source NG-RAN node (e.g. for handover to eNodeB that supports the NTN enhancements as defined in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [46]), then the target eNodeB shall trigger retrieval of the E-UTRA radio capability information again from the UE. 4.11.1.2.2.2 Preparation phase Figure 4.11.1.2.2.2-1 shows the preparation phase of the Single Registration-based Interworking from EPS to 5GS procedure. Figure 4.11.1.2.2.2-1: EPS to 5GS handover using N26 interface, preparation phase This procedure applies to the Non-Roaming (TS 23.501[ System architecture for the 5G System (5GS) ] [2] Figure 4.3.1-1), Home-routed roaming (TS 23.501[ System architecture for the 5G System (5GS) ] [2] Figure 4.3.2-1) and Local Breakout roaming Local Breakout (TS 23.501[ System architecture for the 5G System (5GS) ] [2] Figure 4.3.2-2) cases. - For non-roaming scenario, V-SMF, v-UPF and v-PCF are not present - For home-routed roaming scenario, the SMF+PGW-C and UPF+PGW-U are in the HPLMN. v-PCF are not present - For local breakout roaming scenario, V-SMF and v-UPF are not present. SMF+PGW-C and UPF+PGW-U are in the VPLMN. In local-breakout roaming case, the v-PCF interacts wit the SMF+PGW-C. 1 - 2. Step 1 - 2 from clause 5.5.1.2.2 (S1-based handover, normal) in TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13]. 3. Step 3 from clause 5.5.1.2.2 (S1-based handover, normal) in TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13] with the following modifications: An additional optional parameter Return preferred. Return preferred is an optional indication provided by the MME to indicate a preferred return of the UE to the last used EPS PLMN at a later access change to an EPS shared network. Based on the Return Preferred indication, the initial AMF may store the last used EPS PLMN ID in the UE Context. The initial AMF converts the received EPS MM Context into the 5GS MM Context. This includes converting the EPS security context into a mapped 5G security context as described in TS 33.501[ Security architecture and procedures for 5G System ] [15]. The MME UE context includes IMSI, ME Identity, UE security context, UE Network Capability and EPS Bearer context(s) and may also include LTE-M Indication. The MME EPS Bearer context(s) include for each EPS PDN connection the IP address and FQDN for the S5/S8 interface of the SMF+PGW-C and APN and for each EPS bearer the IP address and CN Tunnel Info at the UPF+PGW-U for uplink traffic. If the AMF received the LTE-M indication in the EPS MM Context, then it considers that the RAT Type is LTE-M. The initial AMF queries the (PLMN level) NRF in serving PLMN by issuing the Nnrf_NFDiscovery_Request including the FQDN for the S5/S8 interface of the SMF+PGW-C and the NRF provides the IP address or FQDN of the N11/N16 interface of the SMF+PGW-C. If the initial AMF cannot retrieve the address of the corresponding SMF for a PDN connection, it will not move the PDN connection to 5GS. NOTE 1: If the initial AMF holds a native 5G security context for the UE, the initial AMF may activate this native 5G security context by initiating a NAS SMC upon completing the handover procedure. 4. The initial AMF invokes the Nsmf_PDUSession_CreateSMContext service operation (UE EPS PDN Connection, initial AMF ID, data Forwarding information, Target ID) on the SMF identified by the SMF+PGW-C address and indicates HO Preparation Indication (to avoid switching the UP path). The initial AMF ID uniquely identifies the initial AMF serving the UE. This step is performed for each PDN Connection and the corresponding SMF+PGW-C address/ID in the UE context the initial AMF received in step 3. The SMF finds the corresponding PDU Session based on EPS Bearer Context(s). Based on configuration and the Direct Forwarding Flag received from the MME, the initial AMF determines the applicability of data forwarding and indicates to the SMF whether the direct data forwarding or indirect data forwarding is applicable. Target ID corresponds to Target ID provided by the MME in step 3. For home-routed roaming scenario, the initial AMF selects a default V-SMF per PDU Session and invokes the Nsmf_PDUSession_CreateSMContext service operation (UE PDN Connection Contexts, initial AMF ID, SMF + PGW-C address, S-NSSAI). The S-NSSAI is the S-NSSAI configured in initial AMF for interworking, which is associated with default V-SMF. The default V-SMF selects the SMF+PGW-C using the received H-SMF address as received from the initial AMF and initiates a Nsmf_PDUSession_Create service operation with the SMF+PGW-C and indicates HO Preparation Indication. The V-SMF provides the QoS constraints of the VPLMN to the H-SMF. Step 5 and step 6 are skipped if the SMF+PGW-C (H-SMF+PGW-C in the case of home-routed scenario) determines that session continuity from EPS to 5GS is not supported for the PDU Session (e.g. PDU Session ID was not received for the PDN connection in EPS, or PDU Session ID was received but mapped 5GS parameters were not provided to the UE due to 5GC interworking restricted). 5. If dynamic PCC is deployed, the SMF+ PGW-C (H-SMF for home-routed scenario) may initiate SMF initiated SM Policy Modification towards the PCF. 6. The SMF+PGW-C requests the PGW-U+UPF to allocate the CN Tunnel Info for PDU Session. The SMF+PGW-C send N4 Session modification to PGW-U+UPF to establish the CN tunnel for PDU Session at PGW-U+UPF. The PGW-U+UPF is ready to receive the uplink packets from NG-RAN. The PGW-U+UPF allocates the PGW-U CN Tunnel Info for PDU Session and sends it to the SMF+PGW-C. This step is performed at all SMF+PGW-Cs allocated to the UE for each PDU Session of the UE. 7. The SMF+PGW-C (default V-SMF in the case of home-routed roaming scenario only) sends a Nsmf_PDUSession_CreateSMContext Response (PDU Session ID, S-NSSAI, allocated EBIs, N2 SM Information (QoS Profile(s), EPS Bearer Setup List, Mapping between EBI(s) and QFI(s), CN Tunnel-Info, cause code)) to the initial AMF. For home-routed roaming scenario the step 8 need be executed first. The CN Tunnel-Info provided to the initial AMF in N2 SM Information is the V-CN Tunnel-Info. The SMF includes mapping between EBI(s) and QFI(s) as part of N2 SM Information container. If the P-GW-C+SMF (H-SMF in the case of home-routed scenario) determines that seamless session continuity from EPS to 5GS is not supported for the PDU Session (e.g. PDU Session ID was not received for the PDN connection in EPS), then it does not provide SM information for the corresponding PDU Session but includes the appropriate cause code for rejecting the PDU Session transfer within the N2 SM Information and release the PDN connection locally in the SMF+PGW-C. If neither indirect forwarding nor direct forwarding is applicable, the SMF shall further include a "Data forwarding not possible" indication in the N2 SM information container. If SMF is indicated that Direct Forwarding is applicable in step 4, the SMF shall further include a "Direct Forwarding Path Availability" indication in the N2 SM information container. In home routed roaming case, the S-NSSAI included in N2 SM Information container is the S-NSSAI received in step 4. The initial AMF stores an association of the PDU Session ID, S-NSSAI and the SMF ID. The AMF stores also the allocated EBI(s) associated to the PDU Session ID. If the PDN Type of a PDN Connection in EPS is non-IP and is locally associated in SMF to PDU Session Type Ethernet, the PDU Session Type in 5GS shall be set to Ethernet. If the PDN type of a PDN Connection in EPS is non-IP and is locally associated in UE and SMF to PDU Session Type Unstructured, the PDU Session Type in 5GS shall be set to Unstructured. NOTE 2: If the non-IP PDN Type is locally associated in SMF to PDU Session Type Ethernet, it means that Ethernet PDN Type is not supported in EPS. In the case of PDU Session Type Ethernet, that was using PDN type non-IP in EPS, the SMF creates QoS rules and QoS Flow level QoS parameters for the QoS Flow(s) associated with the QoS rule(s) based on the PCC Rules received from PCF. In the case of home-routed roaming scenario, the V-SMF may apply VPLMN policies as described in TS 23.501[ System architecture for the 5G System (5GS) ] [2], clause 5.17.1.3. The SMF includes the User Plane Security Policy as part of N2 SM Information container. The SMF determines the User Plane Security Policy as described in clause 5.10.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. 8. For home-routed roaming scenario only: The default V-SMF selects a default v-UPF and initiates an N4 Session Establishment procedure with the selected default v-UPF. The default V-SMF provides the default v-UPF with packet detection, enforcement and reporting rules to be installed on the UPF for this PDU Session, including H-CN Tunnel Info. The default v-UPF acknowledges by sending an N4 Session Establishment Response message. The V-CN Tunnel Info is allocated by the v-UPF and provided to the default V-SMF in this step. 8a. Based on the received S-NSSAI from the SMF+PGW-C, the Initial AMF may reselect a target AMF as described in clause 5.15.5.2.1 of TS 23.501[ System architecture for the 5G System (5GS) ] [2] and invokes Namf_Communication_RelocateUEContext request (SUPI, Target 5GAN Node ID, PDU session ID and the S-NSSAI associated with N2 SM Information received in step 7, Source to Target Transparent Container, 5GS MM Context, MME Tunnel Endpoint Identifier for Control Plane, MME Address for Control plane, PDU Session ID and its associated S-NSSAI of the VPLMN value for each PDU Session, the corresponding S-NSSAI of HPLMN value for home routed PDU Session(s), SMF+PGW-C ID of each PDU Session, default V-SMF ID and SM Context ID of each PDU Session, allocated EBIs of each PDU Session, Allowed NSSAI received from NSSF) to the selected target AMF. NOTE 3: When there is no need of AMF reallocation, then the target AMF in following steps is the same as the initial AMF. NOTE 4: In the case of Home routed PDU Session the S-NSSAI associated with N2 SM information used in steps 8, 8a and 9 is the S-NSSAI configured for interworking in the initial AMF. Otherwise the S-NSSAI received from the SMF in step 7 can be used in steps 8, 8a and 9 for the S-NSSAI associated with N2 SM information. 9. The target AMF sends a Handover Request (Source to Target Transparent Container, Allowed NSSAI, PDU session ID and the S-NSSAI received from Source AMF associated with the corresponding N2 SM Information (QFI(s), QoS Profile(s), EPS Bearer Setup List, V-CN Tunnel Info, Mapping between EBI(s) and QFI(s)), Mobility Restriction List, UE Radio Capability ID) message to the NG-RAN. If available, the target AMF provides NG-RAN with a PLMN list in the Mobility Restriction List containing at least the serving PLMN, which may also include the last used EPS PLMN ID if it is the preferred PLMN for subsequent mobility to EPS. See TS 38.413[ NG-RAN; NG Application Protocol (NGAP) ] [10], clause 9.3.1.85 for details about the Mobility Restriction List. NG-RAN can use the source to target transparent container and N2 SM Information container to determine which QoS flows have been proposed for forwarding and decide for which of those QoS flows it accepts the data forwarding or not. The target AMF provides the UE Radio Capability ID to NG-RAN if RACS is supported. If the UE Radio Capability ID is included in the Handover Request message, when there is no corresponding UE radio capabilities set for UE Radio Capability ID at NG-RAN and no UE radio access capabilities are provided in the Source to Target transparent container, NG-RAN shall request the T-AMF to provide the UE radio capabilities set corresponding to UE Radio Capability ID to the NG-RAN. If the Source to Target transparent container contains the UE radio access capabilities and the T-RAN did not receive the UE Radio Capability ID from the T-AMF, NG-RAN shall proceed with handover using the received UE access radio capabilities. If the T-RAN received both the UE radio access capabilities and the UE Radio Capability ID, then the T-RAN shall use any locally stored UE radio access capability information corresponding to the UE Radio Capability ID. If none are stored locally, the T-RAN may request the full UE radio access capability information from the core network. If the full UE radio access capability information is not promptly received from the core network, or the T-RAN chooses not to request them, then the T-RAN shall proceed with the UE radio access capabilities sent by the source RAN node. The T-RAN shall not use the UE radio access capability information received from the source RAN node for any other UE with the same the UE Radio Capability ID. 10. The NG-RAN sends a Handover Request Acknowledge (Target to Source Transparent Container, List of PDU Sessions to Hand-over with N2 SM response (PDU Session ID, list of accepted QFI(s), AN Tunnel Info, Data Forwarding Tunnel Info), List of PDU Sessions that failed to be established with the failure cause given in the N2 SM information element, PDU Set Based Handling Support Indication included in the N2 SM information) message to the target AMF. If indirect data forwarding is applied, the NG-RAN includes one assigned TEID/TNL address per PDU Session (for which there is at least one QoS flow for which it has accepted the forwarding) within the SM Info container. It also includes the list of QoS flows for which it has accepted the forwarding. According to the mapping between EBI(s) and QFI(s), if one EPS bearer in EPS is mapped to multiple QoS flows in 5GS, all such QoS flows need to be accepted to support indirect data forwarding during EPS to 5GS mobility. Otherwise, the NG RAN rejects the indirect data forwarding for the QoS flows which are mapped to the EPS bearer. If direct data forwarding is applied, the NG-RAN includes one assigned TEID/TNL per E-RAB accepted for direct data forwarding. When the target NG-RAN rejects the handover with a Handover Failure, steps 11-13 and step 16 are not executed. The NG-RAN includes the PDU Set Based Handling Support Indication in N2 SM information as described in clause 5.37.5.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2]. 11. The target AMF sends an Nsmf_PDUSession_UpdateSMContext Request (PDU Session ID, N2 SM response received from NG-RAN in step 10) message to the SMF for updating N3 tunnel information. In home routed roaming case, the Data Forwarding Tunnel Info is handled by the default V-SMF and will not be sent to the SMF+PGW-C. 12. SMF+PGW-C (default V-SMF in home-routed roaming scenario) performs preparations for N2 Handover by indicating N3 UP address and Tunnel ID of NG-RAN to the UPF if N2 Handover is accepted by NG-RAN. If indirect data forwarding is applied, SMF+PGW-C indicates the mapping between the TEID where the UPF receives data forwarded by the source SGW and the QFI(s) and N3 Tunnel Info for data forwarding where the UPF is selected to forward such data (e.g. an intermediate UPF). If the EPS bearer is mapped to multiple QoS flows and an intermediate UPF is selected for data forwarding, only one QFI is selected by the SMF+PGW-C from QFIs corresponding to the QoS flows. If indirect data forwarding is applied in home routed roaming case, the default V-SMF sends a default V-UPF for data forwarding the mapping between the TEID where the UPF receives data forwarded by the source SGW and the QFI and N3 Tunnel Info for data forwarding. If the EPS bearer is mapped to multiple QoS flows and an intermediate UPF is selected for data forwarding, only one QFI is selected by the SMF+PGW-C from QFIs corresponding to the QoS flows. If N2 Handover is not accepted by NG-RAN, SMF+PGW-C deallocates N3 UP address and Tunnel ID of the selected UPF. The EPS Bearer Setup list is a list of EPS bearer Identifiers successfully handover to 5GC, which is generated based on the list of accepted QFI(s). If a PDU Session is rejected by the Target NG-RAN with an indication that the PDU session was rejected because User Plane Security Enforcement is not supported in the Target NG-RAN and the User Plane Enforcement Policy indicates "Required" as described in clause 5.10.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], the SMF triggers the release of this PDU Session. In all other cases of PDU Session rejection, the SMF can decide whether to release the PDU Session or to deactivate the UP connection of this PDU Session. If some of the QoS Flows of a PDU Session are not accepted by the Target NG-RAN, the SMF shall initiate the PDU Session Modification procedure to remove the non-accepted QoS Flows from the PDU Session(s) after the handover procedure is completed. 13. SMF+PGW-C (default V-SMF in home-routed roaming scenario) to target AMF: Nsmf_PDUSession_UpdateSMContext Response (PDU Session ID, EPS Bearer Setup List). The data forwarding information is included in the EPS Bearer Setup List. In home routed roaming case, the default V-SMF provides the tunnel information for data forwarding. This message is sent for each received Nsmf_PDUSession_UpdateSMContext_Request message. 14. The target AMF sends the message Forward Relocation Response (Cause, Target to Source Transparent Container, Serving GW change indication, EPS Bearer Setup List, target AMF Tunnel Endpoint Identifier for Control Plane, Addresses and TEIDs) to MME. The EPS Bearer Setup list is the combination of EPS Bearer Setup list from different SMF+PGW-C(s). In the case of Handover Failure in step 10, the target AMF provides to the MME the failure related information such as the Target RAN to Source RAN Failure Information. 15. The target AMF invokes Namf_Communication_RelocateUEContext response (Cause) to the initial AMF if step 8a had been performed. The target AMF indicates whether the Relocate UE Context (hand-Over) succeeded or failed. If the target NG RAN has rejected the Handover Request in step 10, the Namf_Communication_RelocateUEContext response indicates a failure due to RAN rejection. Then the initial AMF invokes the Nsmf_PDUSession_UpdateSMContext request towards the SMF+PGW-C(s) contacted at step 4 indicating . The Nsmf_PDUSession_UpdateSMContext request contains an indication that this is due to a handover rejected by the target RAN. 16. Step 8 from clause 5.5.1.2.2 (S1-based handover, normal) in TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13] is executed if the source MME determines that indirect data forwarding applies. Upon completion of the handover procedure, based on the PDU Set Based Handling Support Indication received in step 10 as described in clause 5.37.5.3 of TS 23.501[ System architecture for the 5G System (5GS) ] [2], the SMF may initiate the PDU Session modification procedure to provide PDU Set QoS parameters to NG-RAN and configure the PSA UPF to activate/deactivate the PDU Set identification and marking. 4.11.1.2.2.3 Execution phase Figure 4.11.1.2.2.3-1 shows the Single Registration-based Interworking from EPS to 5GS procedure. Figure 4.11.1.2.2.3-1: EPS to 5GS handover using N26 interface, execution phase NOTE: Step 6 P-GW-C+SMF Registration in the UDM is not shown in the figure for simplicity. 1 - 2. Step 9 - 11 from clause 5.5.1.2.2 (S1-based handover, normal) in TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13]. Different from step 9a of clause 5.5.1.2.2 (S1-based handover, normal) in TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13], upon reception of Handover Command, the UE will keep the QoS Flow context for which it did not receive the corresponding radio resources in the NG-RAN until the QoS Flow is released by the network using PDU Session Modification procedure in clause 4.3.3. If the QoS Flow with a default QoS Rule of a PDU Session does not have the corresponding radio resources in the NG-RAN, UE considers that the user plane of this PDU Session is deactivated. 3. Handover Confirm: the UE confirms handover to the NG-RAN. The UE moves from the E-UTRAN and synchronizes with the target NG-RAN. The UE may resume the uplink transmission of user plane data only for those QFIs and Session IDs for which there are radio resources allocated in the NG-RAN. The E-UTRAN sends DL data to the Data Forwarding address received in step 1. If the indirect data forwarding is applied, the E-UTRAN forward the DL data to NG-RAN via the SGW and the v-UPF. The v-UPF forwards the data packets to the NG-RAN using the N3 Tunnel Info for data forwarding, adding the QFI information. The target NG-RAN prioritizes the forwarded packets over the fresh packets for those QoS flows for which it had accepted data forwarding. If Direct data forwarding is applied, the E-UTRAN forwards the DL data packets to the NG-RAN via the direct data forwarding tunnel. 4. Handover Notify: the NG-RAN notifies to the target AMF that the UE is handed over to the NG-RAN. 5. Then the target AMF knows that the UE has arrived to the target side and informs the MME by sending a Forward Relocation Complete Notification message. 6. Step 14 from clause 5.5.1.2.2 (S1-based handover, normal) in TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13]. 7. Target AMF to SMF +PGW-C (V-SMF in the case of roaming and Home-routed case): Nsmf_PDUSession_UpdateSMContext Request (Handover Complete Indication for PDU Session ID). In the Home-routed roaming case, the V-SMF invokes Nsmf_PDUSession_Update Request (V-CN Tunnel Info, Handover Complete Indication) to SMF+PGW-C. Handover Complete Indication is sent per each PDU Session to the corresponding SMF +PGW-C (sent by V-SMF in the roaming and Home-routed case) to indicate the success of the N2 Handover. If indirect forwarding is used, a timer in SMF+PGW-C (V-SMF in the case of roaming and Home-routed case) is started to supervise when resources in UPF (for indirect data forwarding) shall be released. 8. The SMF + PGW-C updates the UPF + PGW-U with the V-CN Tunnel Info, indicating that downlink User Plane for the indicated PDU Session is switched to NG-RAN or V-UPF in the case of roaming in Home-routed case and the CN tunnels for EPS bearers corresponding to the PDU session can be released. For each EPS Bearer one or more "end marker" is sent to Serving GW by the UPF+PGW-U immediately after switching the path. The UPF + PGW-U starts sending downlink packets to the V-UPF. 9. If PCC infrastructure is used, the SMF + PGW-C informs the PCF about the change of, for example, the RAT type and UE location. 10. SMF +PGW-C to target AMF: Nsmf_PDUSession_UpdateSMContext Response (PDU Session ID). SMF +PGW-C confirms reception of Handover Complete. - If the SMF has not yet registered for this PDU Session ID, then the SMF registers with the UDM using Nudm_UECM_Registration (SUPI, DNN, PDU Session ID) for a given PDU Session as in step 4 of PDU Session Establishment Procedure in clause 4.3.2. 11. For home-routed roaming scenario: The V-SMF provides to the v-UPF with the N3 DL AN Tunnel Info. This step is executed after step 7. 12. The UE performs the EPS to 5GS Mobility Registration Procedure from step 2 in clause 4.11.1.3.3. The UE includes the UE Policy Container containing the list of PSIs, indication of UE support for ANDSP and OSId if available. If the UE holds a native 5G-GUTI it also includes the native 5G-GUTI as an additional GUTI in the Registration Request. The UE shall select the 5G-GUTI for the additional GUTI as follows, listed in decreasing order of preference: - a native 5G-GUTI assigned by the PLMN to which the UE is attempting to register, if available; - a native 5G-GUTI assigned by an equivalent PLMN to the PLMN to which the UE is attempting to register, if available; - a native 5G-GUTI assigned by any other PLMN, if available. The additional GUTI enables the target AMF to find the UE's 5G security context (if available). The target AMF provides NG-RAN with a PLMN list in the Handover Restriction List containing at least the serving PLMN, taking into account of the last used EPS PLMN ID and Return preferred indication as part of the Registration procedure execution and target AMF signalling to NG-RAN. The Handover Restriction List contains a list of PLMN IDs as specified by TS 23.501[ System architecture for the 5G System (5GS) ] [2]. 13. Step 19 from clause 5.5.1.2.2 (S1-based handover, normal) in TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13]. Step 20a - 20b from clause 5.5.1.2.2 (S1-based handover, normal) in TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13], with the following modification: For the PDN connections that are not possible to be transferred to 5GS (e.g. PDN connections are anchored in a standalone PGW), the MME initiates PDN connection release procedure as specified in TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13]. 14. If indirect forwarding was used, then the expiry of the timer started at step 7 triggers the SMF+PGW-C (V-SMF in the case of roaming and Home-routed case) to release temporary resources used for indirect forwarding that were allocated at steps 11 to 13 in clause 4.11.1.2.2.2. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.11.1.2.2 |
4,426 | 5.19.7.6 Control Plane data specific NAS level congestion control | Under overload conditions the AMF may restrict requests from UEs for data transmission via Control Plane CIoT 5GS Optimisation. A Control Plane data back-off timer may be returned by the AMF (e.g. in Registration Accept messages, Service Reject message or Service Accept message). While the Control Plane data back-off timer is running, the UE shall not initiate any data transfer via Control Plane CIoT 5GS Optimisation, i.e. the UE shall not send any Control Plane Service Request with uplink data as defined in TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [47]. The AMF shall store the Control Plane data back-off timer per UE and shall not process any further requests (other than exception reporting and a response to paging) for Data Transport via a Control Plane Service Request from that UE while the Control Plane data back-off timer is still running. NOTE 1: The Control Plane data back-off timer does not affect any other mobility management or session management procedure. NOTE 2: The Control Plane data back-off timer does not apply to user plane data communication. If the UE is allowed to send exception reporting, the UE may send an initial NAS Message for exception reporting even if Control Plane data back-off timer is running. The UE may respond to paging with an initial NAS Message without uplink data even if the Control Plane data back-off timer is running. If the AMF receives an initial NAS Message in reponse to a paging, and the AMF has a Control Plane data back-off timer running for the UE, and the AMF is not overloaded, and AMF decides to accept the Control Plane Service Request, then the AMF shall respond with Service Accept without the Control Plane data back-off timer and stop the Control Plane data back-off timer. If the UE receives a Service Accept without the Control Plane data back-off timer from the AMF while the Control Plane data back-off timer is running, the UE shall stop the Control Plane data back-off timer. The Control Plane data back-off timer in the UE and the AMF is stopped at PLMN change. If the AMF receives a Control Plane Service Request with uplink data, and decides to send the UE a Control Plane data back-off timer, the AMF may decide to process the Control Plane Service Request with uplink data, i.e. decrypt and forward the data payload, or not based on the following: - If the UE has indicated Release Assistance Information that no further Uplink and Downlink Data transmissions are expected, then the AMF may process (integrity check/decipher/forward) the received Control Plane data packet, and send a Service Accept to the UE with Control Plane data back-off timer. The UE interprets this as successful transmission of the Control Plane data packet starts the Control Plane data back-off timer. - For all other cases, the AMF may decide to not process the received Control Plane data packet and send a Service Reject to the UE with Control Plane data back-off timer. The UE interprets this indication as unsuccessful delivery of the control plane data packet and starts the Control Plane data back-off timer. The AMF may take into consideration whether the PDU Session is set to Control Plane only to make the decision whether to reject the packet and send Service Reject or move the PDU Session to user plane and process the data packet as described in next bullet. - Alternatively, if UE has not provided Release Assistance Information, and the PDU Session not set to Control Plane only, and UE supports N3 data transfer, then the AMF may initiate establishment of N3 bearer according to the procedure defined in clause 4.2.3 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. In this case the AMF may also return a Control Plane data back-off timer within the Service Accept. The AMF only includes the Control Plane data back-off timer if the UE has indicated support for Control Plane CIoT 5GS optimizations in the Registration Request. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.19.7.6 |
4,427 | 9.3.8.2.2 TDD | For the parameters specified in Table 9.3.8.2.2-1, and using the downlink physical channels specified in Annex C, the minimum requirements are specified in 9.3.8.2.2-2 and by the following a) the ratio of the throughput obtained when transmitting the transport format indicated by each reported wideband CQI index subject to interference sources with NeighCellsInfo-r12 configured and that obtained when transmitting the transport format indicated by each reported wideband CQI index subject to interference sources without NeighCellsInfo-r12 configured shall be ≥ ; Table 9.3.8.2.2-1 Fading test for TDD Table 9.3.8.2.2-2 Minimum requirement (TDD) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 9.3.8.2.2 |
4,428 | 10.1.2.1 Resource grid | A transmitted physical channel or signal in a slot is described by one or several resource grids of subcarriers and SC-FDMA symbols. The resource grid is illustrated in Figure 10.1.2.1-1. The slot number within a radio frame is denoted where for and for . Figure 10.1.2.1-1: Uplink resource grid for NB-IoT The uplink bandwidth in terms of subcarriers , and the slot duration are given in Table 10.1.2.1-1. Table 10.1.2.1-1: NB-IoT parameters. A single antenna port is used for all uplink transmissions. | 3GPP TS 36.211 | Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation | RAN1 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 10.1.2.1 |
4,429 | 5.2.3.2.4 PLMN-SEARCH | The UE may enter this substate when it is in automatic network selection mode and the maximum allowed number of subsequently unsuccessful tracking area updating have been performed. The UE may also enter this substate as a result of a tracking area update rejected by the network (see clause 5.5.3) or as a result of a service request rejected by the network (see clause 5.6.1). If a new PLMN is selected, the UE shall reset the tracking area updating attempt counter and initiate the tracking area updating or combined tracking area updating procedure (see clause 5.5.3). If the selected cell is known not to be able to provide normal service: - the UE may detach locally and initiate attach for emergency bearer services; or - the UE may detach locally and initiate attach for access to RLOS. | 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.2.3.2.4 |
4,430 | 4.11.3.1 Handover from EPS to 5GC-N3IWF | Figure 4.11.3.1-1: Handover from EPS to 5GC-N3IWF 0. Initial status: one or more PDN connections have been established in EPC between the 5G capable UE and the PGW via E-UTRAN. 1. The UE initiates Registration procedure on untrusted non-3GPP access via N3IWF (with 5G-GUTI is available or SUCI if not) per clause 4.12.2. 2. The UE initiates a UE requested PDU Session Establishment with Existing PDU Session indication in 5GC via Untrusted non-3GPP Access via N3IWF per clause 4.12.5. If the Request Type indicates "Existing Emergency PDU Session", the AMF shall use the Emergency Information received from the HSS+UDM which contains SMF+PGW-C FQDN for S5/S8 interface for the emergency PDN connection established in EPS and the AMF shall use the S-NSSAI locally configured in Emergency Configuration Data. The combined PGW+SMF/UPF initiates a PDN GW initiated bearer deactivation as described in clause 5.4.4.1 of TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13] to release the EPC and E-UTRAN resources. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.11.3.1 |
4,431 | 16.12 Sidelink Relay 16.12.1 General | Sidelink relay is introduced to support 5G ProSe UE-to-Network Relay (U2N Relay) function (specified in TS 23.304[ Proximity based Services (ProSe) in the 5G System (5GS) ] [48]) to provide connectivity to the network for U2N Remote UE(s). Both L2 and L3 U2N Relay architectures are supported. The L3 U2N Relay architecture is transparent to the serving NG-RAN of the U2N Relay UE, except for controlling sidelink resources. The detailed architecture and procedures for L3 U2N Relay can be found in TS 23.304[ Proximity based Services (ProSe) in the 5G System (5GS) ] [48]. A U2N Relay UE shall be in RRC_CONNECTED to perform relaying of unicast data. For L2 U2N Relay operation, the following RRC state combinations are supported: - Both L2 U2N Relay UE and L2 U2N Remote UE shall be in RRC_CONNECTED to perform transmission/reception of relayed unicast data; and - The L2 U2N Relay UE can be in RRC_IDLE, RRC_INACTIVE or RRC_CONNECTED as long as all the L2 U2N Remote UE(s) that are connected to the L2 U2N Relay UE are either in RRC_INACTIVE or in RRC_IDLE. A single unicast link is established between one L2 U2N Relay UE and one L2 U2N Remote UE. The traffic to the NG-RAN of L2 U2N Remote UE via a given L2 U2N Relay UE and the traffic of the L2 U2N Relay UE shall be separated in different Uu RLC channels. For L2 U2N Relay, the L2 U2N Remote UE can only be configured to use resource allocation mode 2 (as specified in 5.7.2 and 16.9.3.1) for data to be relayed. Sidelink relay is introduced to support 5G ProSe UE-to-UE Relay (U2U Relay) function (specified in TS 23.304[ Proximity based Services (ProSe) in the 5G System (5GS) ] [48]) to provide connectivity between U2U Remote UEs. Both L2 and L3 U2U Relay architectures are supported. The L3 U2U Relay architecture is transparent to the AS layer of the U2U Relay UE. The detailed architecture and procedures for L3 U2U Relay can be found in TS 23.304[ Proximity based Services (ProSe) in the 5G System (5GS) ] [48]. A U2U Relay UE is to support the U2U Relay function as specified in TS 23.304[ Proximity based Services (ProSe) in the 5G System (5GS) ] [48] to provide coverage extension of the sidelink transmissions between two U2U Remote UEs. For the coverage extension, the U2U Remote UE can communicate with the peer U2U Remote UE(s) which are not reachable within the sidelink coverage. The U2U Relay UE and U2U Remote UE can be in any RRC state. The U2U Relay UE and the U2U Remote UEs can be in the coverage of different cells or out-of-coverage. Both sidelink resource allocation modes, i.e., mode 1 and mode 2 are supported for the U2U Relay UE and U2U Remote UEs. For U2U Relay, NR sidelink is supported between U2U Relay UE and U2U Remote UEs. After NR sidelink establishment between U2U Relay UE and U2U Remote UEs, end-to-end PC5 unicast link connection establishment is performed between U2U Remote UEs. Only unicast is supported between U2U Relay UE and U2U Remote UEs. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.12 |
4,432 | 8.2.1.9.1 Minimum Requirement | The purpose of this test is to verify UE performance in the HST-SFN scenario defined in B.3A when highSpeedEnhancedDemodulationFlag [7] is received. For single carrier, the requirements are specified in Table 8.2.1.9.1-2, with the addition of the parameters in Table 8.2.1.9.1-1 and the downlink physical channel setup according to Annex C.3.2. For CA with 2 DL CC, the requirements are specified in Table 8.2.1.9.1-5, based on single carrier requirement speicified in Table 8.2.1.9.1-4, with the addition of the parameters in Table 8.2.1.9.1-3 and the downlink physical channel setup according to Annex C.3.2. For CA with 3 DL CCs, the requirements are specified in Table 8.2.1.9.1-6, based on single carrier requirement specified in Table 8.2.1.9.1-4, with the addition of the parameters in Table 8.2.1.9.1-3 and the downlink physical channel setup according to Annex C.3.2. For CA with 4 DL CCs, the requirements are specified in Table 8.2.1.9.1-7, based on single carrier requirement specified in Table 8.2.1.9.1-4, with the addition of the parameters in Table 8.2.1.9.1-3 and the downlink physical channel setup according to Annex C.3.2. For CA with 5 DL CCs, the requirements are specified in Table 8.2.1.9.1-8, based on single carrier requirement specified in Table 8.2.1.9.1-4, with the addition of the parameters in Table 8.2.1.9.1-3 and the downlink physical channel setup according to Annex C.3.2. The test coverage for different number of component carriers is defined in 8.1.2.4. Table 8.2.1.9.1-1: Test Parameters for UE performance in HST-SFN scenario (FRC) Table 8.2.1.9.1-2: Minimum performance UE in HST-SFN scenario (FRC) Table 8.2.1.9.1-3: Test Parameters for Large Delay CDD (FRC) for CA Table 8.2.1.9.1-4: Single carrier performance for multiple CA configurations Table 8.2.1.9.1-5: Minimum performance Large Delay CDD (FRC) for CA with 2DL CCs Table 8.2.1.9.1-6: Minimum performance (FRC) based on single carrier performance for CA with 3 DL CCs Table 8.2.1.9.1-7: Minimum performance (FRC) based on single carrier performance for CA with 4 DL CCs Table 8.2.1.9.1-8: Minimum performance (FRC) based on single carrier performance for CA with 5 DL CCs | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.2.1.9.1 |
4,433 | 4.3.18.3a MPS for Data Transport Service | MPS for Data Transport Service is an on-demand service that may be invoked/revoked by an authorized MPS Service User using a UE with a subscription for MPS (i.e. according to its MPS profile), or using a UE that does not have a subscription for MPS (using methods not in scope of this specification). MPS for Data Transport Service requires explicit invocation. The Service User invokes the service by communicating with an AF. The authorization of an MPS for Data Transport Service request is done by the AF or by the PCRF according to clause 6.1.11.5 of TS 23.203[ Policy and charging control architecture ] [6]. Upon successful authorization the PCRF performs the necessary actions to achieve appropriate ARP and QCI settings for the bearers (see clause 6.1.11.5 of TS 23.203[ Policy and charging control architecture ] [6]). NOTE 1: MPS for Data Transport Service can be applied to any APN other than the well-known APN for IMS. MPS for Data Transport Service enables the prioritization of all traffic on the default bearer and other bearers upon AF request. The QoS modification to the default bearer and other bearers is done based on operator policy and regulatory rules by means of local PCRF configuration. NOTE 2: If no configuration is provided, MPS for Data Transport Service applies only to the default bearer. NOTE 3: MPS for Data Transport Service controls the priority of traffic on bearers independent of the application(s) being used. Other mechanisms (e.g., Priority EPS Bearer Service) can be used to control the priority of traffic on other bearers not under control by MPS for Data Transport Service, based on operator policy. For MPS for Data Transport Service, the AF may also create an SDF for signalling priority between the UE and the AF (see clause 6.1.11.5 of TS 23.203[ Policy and charging control architecture ] [6]). NOTE 4: The network can hide its topology from the AF supporting MPS for Data Transport Service. At the same time, the UE needs to provide its locally known IP address to the AF supporting MPS for Data Transport Service to support Diameter routing to the applicable PCRF. Thus, there can be no NAT of the UE IP address between the PDN-GW and the AF supporting MPS for Data Transport Service. | 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.18.3a |
4,434 | 4.16.1.7 Number of Path Update Request at Secondary Node Additions | a) This measurement provides the number of Path Update Request at Secondary Node Addition. b) CC c) On transmission by the MN of an E-RAB modification indication message to MME at Secondary Node Additions. Each path update is added to the relevant measurement. SgNB Addition Trigger Indication (TS 36.423[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); X2 Application Protocol (X2AP) ] [10]) excludes SN change, inter-eNB HO, intra-eNB HO. d) Each measurement is an integer value. e) The measurement name has the form ENDC.PathUpdateAttAtSNAddition. f) EUtranCellFDD EUtranCellTDD g) Valid for packet switched traffic h) EPS | 3GPP TS 32.425 | Telecommunication management; Performance Management (PM); Performance measurements Evolved Universal Terrestrial Radio Access Network (E-UTRAN) | SA WG5 | 3GPP Series : 32 , OAM&P and Charging | 4.16.1.7 |
4,435 | 5.9.3 Requirements for e2e core network interconnection security 5.9.3.1 General | The present sub-clause contains requirements common to sub-clauses 5.9.2 and 5.9.3. A solution for e2e core network interconnection security shall satisfy the following requirements. The solution shall support application layer mechanisms for addition, deletion and modification of message elements by intermediate nodes except for specific message elements described in the present document. NOTE: Typical example for such a case is IPX providers modifying messages for routing purposes. The solution shall provide confidentiality and/or integrity end-to-end between source and destination network for specific message elements identified in the present document. For this requirement to be fulfilled, the SEPP – cf [2], clause 6.2.17 shall be present at the edge of the source and destination networks dedicated to handling e2e Core Network Interconnection Security. The confidentiality and/or integrity for the message elements is provided between two SEPPs of the source and destination PLMN–. The destination network shall be able to determine the authenticity of the source network that sent the specific message elements protected according to the preceding bullet. For this requirement to be fulfilled, it shall suffice that a SEPP in the destination network that is dedicated to handling e2e Core Network Interconnection Security can determine the authenticity of the source network. The solution should have minimal impact and additions to 3GPP-defined network elements. The solution should be using standard security protocols. The solution shall cover interfaces used for roaming purposes. The solution should take into account considerations on performance and overhead. The solution shall cover prevention of replay attacks. The solution shall cover algorithm negotiation and prevention of bidding down attacks. The solution should take into account operational aspects of key management. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 5.9.3 |
4,436 | 4.3.19.2 MSB in LAC and MME Group ID | For PLMNs deployed with such mechanism the MME differentiates between a GUMMEI mapped from P-TMSI/RAI and a native GUMMEI based on the value of most significant bit of the MME Group ID; i.e. the MSB is set to "0" then the GUMMEI is mapped from P-TMSI/RAI and if MSB is set to "1", the GUMMEI is a native one, as specified in TS 23.003[ Numbering, addressing and identification ] [9]. For PLMNs deployed with such mechanism the S4-SGSN differentiates between a P-TMSI/RAI mapped from GUTI and a native P-TMSI/RAI based on the value of most significant bit of the LAC; i.e. the MSB is set to "1" then the P-TMSI/RAI is mapped from GUTI and if MSB is set to "0", the P-TMSI/RAI is a native one, as specified in TS 23.003[ Numbering, addressing and identification ] [9]. | 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.19.2 |
4,437 | 4.11.0a.4 PGW Selection | When the UE requests to establish a non-emergency PDN connection to an APN, the MME may use the UE's support for 5GC NAS indication included in the UE Network Capability and/or UE's subscription from HSS that includes UE's mobility restriction parameters related to 5GS and/or indication of support for interworking with 5GS for this APN to determine if SMF+PGW-C or a standalone PGW-C should be selected. If both PGW-C and SMF+PGW-C is available, then MME may select SMF+PGW-C when UE's subscription from HSS indicate support for interworking with 5GS for the APN. NOTE: If restriction for Core Network Type indicates that the UE can access to 5GC, it implies that the UE has 5G subscription data. When the UE performs emergency attach or requests to establish an emergency PDN connection, the MME may use the UE's support for 5GC NAS indication included in the UE Network Capability and/or local configuration to determine if an emergency SMF+PGW-C or a standalone emergency PGW-C should be selected. An emergency SMF+PGW-C needs to be configured in Emergency Configuration Data in the MME if it is to be selected. To enable a differentiation of the emergency gateway based on UE´s support of 5GC NAS, the Emergency Configuration Data in the MME defined in TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [13] is extended with the IE listed in Table 4.11.0a.4-1. Table 4.11.0a.4-1: MME Emergency Configuration Data Extensions | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.11.0a.4 |
4,438 | – OLPC-SRS-Pos | The IE OLPC-SRS-Pos is used to convey OLPC SRS positioning related parameters specific for a certain band. OLPC-SRS-Pos information element -- ASN1START -- TAG-OLPC-SRS-POS-START OLPC-SRS-Pos-r16 ::= SEQUENCE { olpc-SRS-PosBasedOnPRS-Serving-r16 ENUMERATED {supported} OPTIONAL, olpc-SRS-PosBasedOnSSB-Neigh-r16 ENUMERATED {supported} OPTIONAL, olpc-SRS-PosBasedOnPRS-Neigh-r16 ENUMERATED {supported} OPTIONAL, maxNumberPathLossEstimatePerServing-r16 ENUMERATED {n1, n4, n8, n16} OPTIONAL } --TAG-OLPC-SRS-POS-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
4,439 | 9 Reporting of Channel State Information 9.1 General | This section includes requirements for the reporting of channel state information (CSI). For all test cases in this section, the definition of SNR and SINR are in accordance with the one given in clause 8.1.1. For the performance requirements specified in this clause, it is assumed that NRX=2 unless otherwise stated. Unless otherwise stated, 4-bit CQI Table in Table 7.2.3-1 in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [6], and Modulation and TBS index table in Table 7.1.7.1-1 for PDSCH in TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [6] are applied in all the CSI requirements. | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 9 |
4,440 | 6.3.1.3.2 Abnormal cases in the UE | The following abnormal cases can be identified: a) PDU session inactive for the received PDU session ID. If the PDU session ID in the PDU SESSION AUTHENTICATION RESULT message belongs to any PDU session in state PDU SESSION INACTIVE in the UE, the UE shall send a 5GSM STATUS message with the 5GSM cause IE set to #43 "Invalid PDU session identity". b) Collision of UE-requested PDU session release procedure and a PDU EAP result message transport procedure. When the UE receives a PDU SESSION AUTHENTICATION RESULT message during the UE-requested PDU session release procedure, and the PDU session indicated in PDU SESSION AUTHENTICATION RESULT message is the PDU session that the UE had requested to release, the UE shall ignore the PDU SESSION AUTHENTICATION RESULT message and proceed with the UE-requested PDU session release procedure. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.3.1.3.2 |
4,441 | 10.18.5 RA Report retrieval | In MR-DC, when a UE performs successful random access attempts which are only known by the SN (e.g., beam failure recovery, UL synchronization issue, scheduling request failure, no PUCCH resource available), the SN may inform the MN about the occurrences of successful random access procedures in the SN via a RACH indication. The MN may then retrieve the RA Report from the UE(s) based on the RACH indication received from the SN. A UE while being in EN-DC and NGEN-DC can collect E-UTRA RA Reports and NR RA Reports upon performing RACH in MN and SN respectively. When a E-UTRAN node retrieves the E-UTRA RA Report, it can also request UE to include the NR RA Report. If available, the UE then includes the NR RA Report in a container along with a list of PSCells associated to the NR RA Report within the E-UTRA RA Report. The retrieiving E-UTRAN node may then forward it to the corresponding SNs serving the PSCells indicated within the E-UTRA RA Report. In case of NGEN-DC, in case there is no Xn connectivity between the ng-eNB retrieving the NR RA Report from the UE and the gNB serving the PSCells indicated by UE in the NR RA Report, the ng-eNB may forward the NR RA Report via Xn to an ng-eNB connected to a gNB serving the PSCells indicated in the RA Report. In case of EN-DC, in case there is no X2 connectivity between the eNB retrieving the NR RA Report from the UE and the en-gNB serving the PSCells indicated by UE in the NR RA Report, the eNB may forward the NR RA Report via X2 to an eNB connected to an en-gNB serving the PSCells indicated in the RA Report. | 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.18.5 |
4,442 | – RACH-ConfigGeneric | The IE RACH-ConfigGeneric is used to specify the random-access parameters both for regular random access as well as for beam failure recovery. RACH-ConfigGeneric information element -- ASN1START -- TAG-RACH-CONFIGGENERIC-START RACH-ConfigGeneric ::= SEQUENCE { prach-ConfigurationIndex INTEGER (0..255), msg1-FDM ENUMERATED {one, two, four, eight}, msg1-FrequencyStart INTEGER (0..maxNrofPhysicalResourceBlocks-1), zeroCorrelationZoneConfig INTEGER(0..15), preambleReceivedTargetPower INTEGER (-202..-60), preambleTransMax ENUMERATED {n3, n4, n5, n6, n7, n8, n10, n20, n50, n100, n200}, powerRampingStep ENUMERATED {dB0, dB2, dB4, dB6}, ra-ResponseWindow ENUMERATED {sl1, sl2, sl4, sl8, sl10, sl20, sl40, sl80}, ..., [[ prach-ConfigurationPeriodScaling-IAB-r16 ENUMERATED {scf1,scf2,scf4,scf8,scf16,scf32,scf64} OPTIONAL, -- Need R prach-ConfigurationFrameOffset-IAB-r16 INTEGER (0..63) OPTIONAL, -- Need R prach-ConfigurationSOffset-IAB-r16 INTEGER (0..39) OPTIONAL, -- Need R ra-ResponseWindow-v1610 ENUMERATED { sl60, sl160} OPTIONAL, -- Need R prach-ConfigurationIndex-v1610 INTEGER (256..262) OPTIONAL -- Need R ]], [[ ra-ResponseWindow-v1700 ENUMERATED {sl240, sl320, sl640, sl960, sl1280, sl1920, sl2560} OPTIONAL -- Need R ]] } -- TAG-RACH-CONFIGGENERIC-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
4,443 | 10.5.5.29 P-TMSI type | The purpose of the P-TMSI type information element is to indicate whether the P-TMSI included in the same message in an information element of type mobile identity, or the P-TMSI used by the MS to derive a foreign TLLI (see subclause 4.7.1.4.1) represents a native P-TMSI or a mapped P-TMSI. The P-TMSI type information element information element is coded as shown in figure 10.5.5.29.1 and table 10.5.5.29.1. The P-TMSI type is a type 1 information element. Figure 10.5.5.29.1: P-TMSI type information element Table 10.5.5.29.1: P-TMSI type information element | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 10.5.5.29 |
4,444 | 9.5.2.8 Extended protocol configuration options | This IE is included in the message when the network wishes to transmit (protocol) data (e.g. configuration parameters, error codes or messages/events) to the MS and the extended protocol configuration options IE is supported by both the MS and the network end-to-end for the PDN connection (see subclause 6.1.3.7). This IE is also included to indicate the selected Bearer Control Mode to be applied as well as the network support for Local IP address in TFTs for all active PDP contexts sharing the same PDP Address and APN, if the PDN type is different from Non-IP, and the extended protocol configuration options IE is supported by both the MS and the network end-to-end for the PDN connection (see subclause 6.1.3.7). | 3GPP TS 24.008 | Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.5.2.8 |
4,445 | 4.22.9.2 UE Triggered Service Request | The signalling flow for a UE Triggered Service Request is based on the signalling flow in Figure 4.2.3.2-1 with the following differences and clarifications: - In step 1, if the UE wants to re-activate the user plane of the MA PDU Session(s) over the access the Service Request message is sent to, the UE indicates PDU Session ID(s) of the MA PDU Session(s) in the List Of PDU Sessions To Be Activated. If the UE locally releases the MA PDU Session(s), the UE indicates it in the PDU Session Status. If the AMF receives the PDU Session Status and finds mismatch, regardless of roaming mode of the MA PDU Session (i.e. non-roaming, local breakout roaming, home routed roaming in the same PLMN or home routed roaming in different PLMNs), the AMF invokes Nsmf_PDUSession_ReleaseSMContext service towards the SMF(s) in order to release any network resources related to the MA PDU Session(s). In step 4, if the UE indicated to re-activate MA PDU Session(s) in the List Of PDU Sessions To Be Activated the AMF includes access type which the Service Request message is received on when the AMF triggers Nsmf_PDUSession_UpdateSMContext service operation. The SMF only re-activates user plane resources of the access type the Service Request message is received on. - In step 12, if the AMF indicates that the PDU Session(s) has been released in the PDU Session Status to the UE in Service Accept message, the UE removes locally any internal resources related to the MA PDU Session(s) that are not marked as established. NOTE: For an MA PDU session established when UE was registered on only one access, during the registration on the second access, the AMF does not notify the SMF (for this MA PDU session) that the UE is now registered on the second access since this will occur later, i.e. when the UE sends the second PDU Session Establishment Request to add user plane resources. | 3GPP TS 23.502 | Procedures for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 4.22.9.2 |
4,446 | 6.5.3 5GSM status received in the SMF | If the SMF receives a 5GSM STATUS message the SMF shall take different actions depending on the received 5GSM cause value: #43 invalid PDU session identity. The SMF shall abort any ongoing 5GSM procedure related to the PTI or PDU session ID, stop any related timer and locally release the PDU session indicated in the 5GSM STATUS message. #47 PTI mismatch. The SMF shall abort any ongoing 5GSM procedure related to the received PTI value and stop any related timer. If the PTI indicated in the 5GSM STATUS message is related to a PDU SESSION ESTABLISHMENT ACCEPT message, the SMF shall perform a local release of the PDU session indicated in the PDU SESSION ESTABLISHMENT ACCEPT message. #81 invalid PTI value. The SMF shall abort any ongoing 5GSM procedure related to the received PTI value and stop any related timer. #96 invalid mandatory information. The SMF shall abort any ongoing 5GSM procedure related to the PTI or PDU session ID and stop any related timer. #97 message type non-existent or not implemented. The SMF shall abort any ongoing 5GSM procedure related to the PTI or PDU session ID and stop any related timer. The local actions to be taken by the SMF on receipt of a 5GSM STATUS message with any other 5GSM cause value are implementation dependent. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.5.3 |
4,447 | 6.9.6 Security handling in registration with AMF reallocation via direct NAS reroute | In registration with AMF reallocation via direct NAS reroute, the initial AMF shall send the complete Registration Request in clear text to the target AMF. NOTE: The completeRegistration Request in clear text is obtained based on the Registration Request initially received by the initial AMF if the UE have a valid NAS sececurity context, or the Registration Request received by the initial AMF as part of the Security Mode Complete if it is executed. In registration with AMF reallocation via direct NAS reroute, the initial AMF shall use its local policy to determine whether to perform horizontal KAMF derivation on current KAMF. As described in Clause 6.9.3, if the initial AMF decides not to change KAMF, the initial AMF shall send the current security context to the target AMF; otherwise, the initial AMF shall derive new security context and send to the target AMF the derived security context and the indication of horizontal KAMF derivation (i.e., keyAmfHDerivationInd). If the target AMF receives the indication of horizontal KAMF derivation (i.e., keyAmfHDerivationInd) from the initial AMF, it shall initiate NAS SMC. If the target AMF does not receive keyAmfHDerivationInd, the target AMF shall use the received security context from initial AMF and send protected NAS message including protected authentication request message if authentication is needed. The target AMF decides whether to perform authentication based on local policy. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 6.9.6 |
4,448 | 9.8 Demodulation reference signals | Demodulation reference signals associated with PSSCH, PSCCH, PSDCH, and PSBCH transmission shall be transmitted according to PUSCH in clause 5.5.2.1 with the following exceptions: - The parameters in Tables 9.8-1, 9.8-2, and 9.8-3 shall be used. - The term PUSCH shall be replaced by PSSCH, PSCCH, PSDCH or PSBCH, depending on the physical channel to which the reference signal is associated. - Antenna ports are given by Table 9.2-1. - The set of physical resource blocks used in the mapping process shall be identical to the corresponding PSSCH/PSCCH/PSDCH/PSBCH transmission. - The index in the mapping process in clause 5.5.2.1.2 corresponding to the case where higher-layer parameter ul-DMRS-IFDMA is not set shall be identical to that for the corresponding PSSCH/PSCCH/PSDCH/PSBCH transmission. - For sidelink transmission modes 3 and 4 on the PSSCH and PSCCH, the mapping shall use and for the first slot in the subframe and and for the second slot in the subframe. - For sidelink transmission modes 3 and 4 on the PSBCH, the mapping shall use and for the first slot in the subframe and for the second slot in the subframe. - For sidelink transmission modes 1 and 2, the pseudo-random sequence generator in clause 5.5.1.3 shall be initialized at the start of each slot fulfilling . For sidelink transmission modes 3 and 4 the pseudo-random sequence generator in clause 5.5.1.3 shall be initialized at the start of each slot fulfilling . - For sidelink transmission modes 3 and 4 on the PSCCH, the cyclic shift to be applied for all DM-RS in a subframe shall be chosen according to clause 14.2.1 of [4]. - For sidelink transmission modes 1and 2 and sidelink discovery, the quantity in clause 5.5.2.1.1 takes the values and for sidelink transmission modes 3and 4, the quantity in clause 5.5.2.1.1 takes the values for PSSCH and for PSBCH. - For sidelink transmission modes 3 and 4, the quantity equals the decimal representation of CRC on the PSCCH transmitted in the same subframe as the PSSCH according to with and given by clause 5.1.1 in [3]. Table 9.8-1: Reference signal parameters for PSSCH. Table 9.8-2: Reference signal parameters for PSCCH. Table 9.8-3: Reference signal parameters for PSDCH and PSBCH. | 3GPP TS 36.211 | Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation | RAN1 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 9.8 |
4,449 | 15.5.2.2.3 Connection failure due to inter-system mobility | One of the functions of Mobility Robustness Optimization is to detect connection failures that occurred due to Too Early or Too Late inter-system handovers or inter-system Mobility Failure for Voice Fallback. These problems are defined as follows: - Inter-system/ Too Late Handover: an RLF occurs after the UE has stayed in a cell belonging to an NG-RAN node for a long period of time; the UE attempts to re-connect to a cell belonging to an E-UTRAN node. - Inter-system/ Too Early Handover: an RLF occurs shortly after a successful handover from a cell belonging to an E-UTRAN node to a target cell belonging to an NG-RAN node; the UE attempts to re-connect to the source cell or to another cell belonging to an E-UTRAN node. - Inter-system Mobility Failure for Voice Fallback: an RLF occurs shortly after a successful handover triggered due to Voice Fallback, or a failure occurs during an handover triggered due to Voice Fallback, from a cell belonging to an NG-RAN node to a cell belonging to an E-UTRAN node; the UE attempts to re-connect to a cell belonging to an E-UTRAN node, or an NG-RAN node. Detection mechanism A failure indication may be sent to the node last serving the UE when the NG-RAN node fetches the RLF REPORT from UE by triggering: - The Failure Indication procedure over Xn; - The Uplink RAN configuration transfer procedure and Downlink RAN configuration transfer procedure over NG. In case the last serving node is an E-UTRAN node, the detection mechanism proceeds as defined in TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [2]. In case the last serving node is an NG-RAN node, the detection mechanisms for Too Late Inter-system Handover, Too Early Inter-system Handover, and Inter-system Mobility Failure for Voice Fallback are carried out through the following: - Too Late Inter-system Handover: the connection failure occurs while being connected to a NG-RAN node, and there is no recent handover for the UE prior to the connection failure i.e., the UE reported timer is absent or larger than the configured threshold, e.g., Tstore_UE_cntxt, and the first node where the UE attempts to re-connect is a E-UTRAN node. - Too Early Inter-system Handover: the connection failure occurs while being connected to a NG-RAN node, and there is a recent inter-system handover for the UE prior to the connection failure i.e., the UE reported timer is smaller than the configured threshold, e.g., Tstore_UE_cntxt, and the first cell where the UE attempts to re-connect and the node that served the UE at the last handover initialisation are both E-UTRAN node. - Inter-system Mobility Failure for Voice Fallback: in case the connection failure occurs during an inter-system handover for voice fall back from NR, the RLF Report from the UE includes a voice fallback indication, as defined in TS 38.331[ NR; Radio Resource Control (RRC); Protocol specification ] [12]. The "UE reported timer" above indicates the time elapsed since the last handover initialisation until connection failure. The UE may make the RLF Report available to an NG-RAN node. The NG-RAN node may forward the information using the FAILURE INDICATION message over Xn or by means of the Uplink RAN configuration transfer procedure and Downlink RAN configuration transfer over NG to the node that served the UE before the reported connection failure. In case the failure is a Too Early Inter-system Handover, the NG-RAN node receiving the failure indication may inform the E-UTRAN node by means of the Uplink RAN Configuration Transfer procedure over NG. This may include the RLF report. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 15.5.2.2.3 |
4,450 | 8.5.1.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.1-1 and Table 8.5.1.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.1.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.1.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.1.2.7-1: Test Parameters for PHICH Table 8.5.1.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.1.2.7 |
4,451 | 5.11.2 Requirements for algorithm selection | a) UE in RRC_Connected and a serving network shall have agreed upon algorithms for - Ciphering and integrity protection of RRC signalling and user plane (to be used between UE and gNB) - Ciphering and integrity protection of RRC signalling and user plane (to be used between UE and ng-eNB) - NAS ciphering and NAS integrity protection (to be used between UE and AMF) b) The serving network shall select the algorithms to use dependent on - the UE security capabilities of the UE, - the configured allowed list of security capabilities of the currently serving network entity c) The UE security capabilities shall include NR NAS algorithms for NAS level, NR AS algorithms for AS layer and LTE algorithms for AS level if the UE supports E-UTRAN connected to 5GC. NOTE: If the UE supports both E-UTRAN and NR connected to 5GC, the UE 5G security capabilities include both the LTE and NR algorithms. d) Each selected algorithm shall be indicated to a UE in a protected manner such that a UE is ensured that the integrity of algorithm selection is protected against manipulation. e) The UE security capabilities shall be protected against "bidding down attacks". f) It shall be possible that the selected AS and NAS algorithms are different at a given point of time. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | 5.11.2 |
4,452 | 8.10.1.1.12 Closed loop spatial multiplexing performance - Single-Layer Spatial Multiplexing with CRS assistance information (User-Specific Reference Symbols) | The requirements are specified in Table 8.10.1.1.12-2, with the addition of parameters in Table 8.10.1.1.12-1. In Table 8.10.1.1.12-1, Cell 1 is the serving cell, and Cell 2 and Cell 3 are the aggressor cells. The downlink physical channel setup is according to Annex C.3.2 for each of Cell 1, Cell 2 and Cell 3, respectively. The CRS assistance information [7] is provided to the UE and includes information on Cell 2 and Cell 3. The purpose of the test is to verify the closed loop single layer TM9 performance under assumption that UE applies CRS interference mitigation in the scenario with 2 CRS antenna ports in the serving and aggressor cells. Table 8.10.1.1.12-1: Test Parameters Table 8.10.1.1.12-2: Minimum Performance for PDSCH | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.10.1.1.12 |
4,453 | 6.2.2A UE maximum output power for CA | The following UE Power Classes define the maximum output power for any transmission bandwidth within the aggregated channel bandwidth. The maximum output power is measured as the sum of the maximum output power at each UE antenna connector. The period of measurement shall be at least as defined in Table 6.2.2A-0a. Table 6.2.2A-0a: Measurement period for UE maximum output power for CA For inter-band carrier aggregation with one uplink component carrier assigned to one E-UTRA band the requirements in subclause 6.2.2 apply. For inter-band carrier aggregation with two uplink contiguous component carrier assigned to one E-UTRA band the requirements specified in Table 6.2.2A-1 apply for that band. For inter-band carrier aggregation with one uplink component carrier assigned to one E-UTRA band in Band 38, 40, 41 or 42, the requirements for power class 2 are not applicable and the corresponding requirements for a power class 3 UE shall apply. For inter-band carrier aggregation with one uplink component carrier assigned to one E-UTRA band in Band 3, 20, 28, or 31, the requirements for power class 1 are not applicable and the corresponding requirements for a power class 3 UE shall apply. For inter-band carrier aggregation with uplink assigned to two E-UTRA bands, UE maximum output power shall be measured over all component carriers from different bands. If each band has separate antenna connectors, maximum output power is measured as the sum of maximum output power at each UE antenna connector. The maximum output power is specified in Table 6.2.2A-0. For E-UTRA CA bands including an uplink LAA Scell in Band 46, the UE shall meet the following additional requirements for transmission within the frequency ranges 5150-5350 MHz and 5470-5725 MHz: - a maximum mean power density of 10 dBm in any 1 MHz band when the network signaling value NS_28 or NS_29 is indicated in the LAA Scell; - a maximum mean power density of 11 dBm in any 1 MHz band when the network signaling value NS_30 is indicated in the LAA Scell; the following additional requirements for transmission within the frequency range 5230-5250 MHz: - a maximum mean power density of 4 dBm in any 1 MHz band when the network signaling value NS_31 is indicated in the LAA Scell; the following additional requirements for transmission within the frequency ranges 5150-5230 MHz, 5250-5350 MHz, 5470-5725 MHz and 5725-5850 MHz: - a maximum mean power density of 10 dBm in any 1 MHz band when the network signaling value NS_31 is indicated in the LAA Scell; where the said network signaling values are specified in clause 6.2.4. Table 6.2.2A-0: UE Power Class for uplink interband CA (two bands) For uplink intra-band contiguous carrier aggregation the maximum output power is specified in Table 6.2.2A-1. For downlink intra-band contiguous carrier aggregation with a single uplink component carrier configured in the E-UTRA band, the maximum output power is specified in Table 6.2.2-1. For a power class 2 capable UE operating with intra-band uplink contiguous CA bandwidth class C on Band 41, when an IE P-max as defined in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [7] of 23 dBm or lower is indicated in the cell or if the uplink/downlink configuration is 0 or 6, the requirements for power class 2 are not applicable, and the corresponding requirements for a power class 3 UE shall apply. Table 6.2.2A-1: CA UE Power Class for intraband contiguous CA For intra-band non-contiguous carrier aggregation with one uplink carrier on the PCC, the requirements in subclause 6.2.2 apply. For intra-band non-contiguous carrier aggregation with two uplink carriers the maximum output power is specified in Table 6.2.2A-2. Table 6.2.2A-2: UE Power Class for intraband non-contiguous CA | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.2.2A |
4,454 | 6.2.3G.1 MPR for Power class 3 V2X UE | For contiguous allocation of PSCCH and PSSCH simultaneous transmission, the allowed MPR for the maximum output power for V2X physical channels PSCCH and PSSCH shall be as specified in Table 6.2.3G.1-1 for power class 3. Table 6.2.3G.1-1: Maximum Power Reduction (MPR) for power class 3 V2X Communication (Contiguous PSCCH and PSSCH transmission) For non-contiguous allocation of PSCCH and PSSCH simultaneous transmission, the allowed MPR for the maximum output power for V2X physical channels PSCCH and PSSCH shall be as specified as follows MPR = CEIL {MA, 0.5} Where MA is defined as follows MA = 4.5 ; 0.00< A ≤ 0.2 5.5 –5.833A ; 0.2< A ≤0.6 2.0 ; 0.6< A ≤1.00 Where A = NRB_alloc / NRB. CEIL{MA, 0.5} means rounding upwards to closest 0.5dB. The allowed MPR for the maximum output power for V2X physical channels PSBCH and PSSS shall be as specified in subclause 6.2.3 for the corresponding modulation and transmission bandwidth. The allowed MPR for the maximum output power for V2X physical signal SSSS is specified in Table 6.2.3D-1. When UE is configured for simultaneous E-UTRA V2X sidelink and E-UTRA uplink transmissions for inter-band E-UTRA V2X / E-UTRA bands specified in Table 5.5G-2, the allowed MPR requirements in subclause 6.2.3G apply for V2X PSSCH and PSCCH transmission. The allowed MPR requirements in subclause 6.2.3D apply for other V2X sidelink transmission (PSBCH/PSSS/SSSS). The MPR requirements in subclause 6.2.3 apply for uplink transmission. For intra-band contiguous multi-carrier operation bandwidth class B the allowed Maximum Power Reduction (MPR) for the maximum output power in Table 6.2.2G.1-2 due to higher order modulation is specified as follows. Table 6.2.3G.1-2: Void MPR = CEIL { MA, 0.5} Where MA is defined as follows for QPSK, 16 QAM and 64 QAM MA = 6.5 ; 0 ≤ A < 0.1 8 - 15A ; 0.1 ≤ A < 0.2 5.75 – 3.75A ; 0.2 ≤ A < 0.6 3.5 ; 0.6≤ A ≤ 1For intra-band contiguous multi-carrier operation bandwidth class C the allowed Maximum Power Reduction (MPR) for the maximum output power can be specified as follows. In case the modulation format is different on different component carriers then the MPR is determined by the rules applied to higher order of those modulations. MPR = CEIL { MA, 0.5} Where MA is defined as follows for QPSK, 16 QAM and 64 QAM [MA = 6.5 ; 0 ≤ A < 0.1 8.5 - 20A ; 0.1 ≤ A < 0.2 5.25 – 2.5A ; 0.2 ≤ A < 0.6 3.5 ; 0.6≤ A ≤ 1] | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 6.2.3G.1 |
4,455 | 10.5.5.1 Attach result | The purpose of the attach result information element is to specify the result of a GPRS attach procedure. The attach result is a type 1 information element. The attach result information element is coded as shown in figure 10.5.117a/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] and table 10.5.134a/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] . Figure 10.5.117a/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Attach result information element Table 10.5.134a/3GPP TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] : Attach 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.1 |
4,456 | 16.1.6.1 Redundant user plane paths based on dual connectivity | UE may initiate two redundant PDU Sessions over the 5G network. The 5GS sets up the user plane paths of the two redundant PDU sessions to be disjoint. When PDU session setup or modification is initiated, the RAN can configure dual connectivity in one NG-RAN node or two NG-RAN nodes for the two redundant PDU sessions to ensure the disjoint user plane paths according to the redundancy information received from the 5GC. The RAN shall ensure that the resources of the data radio bearers for the two redundant PDU sessions are isolated. If the RAN cannot satisfy the disjoint user plane requirement, the redundant PDU sessions may be kept or not kept according to the RAN local configuration. The redundancy information is transferred to the target NG-RAN node in case of handover. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.1.6.1 |
4,457 | 15.5.1.2 Load reporting for intra-RAT and intra-system inter-RAT load balancing | The load reporting function is executed by exchanging load information over the Xn/X2/F1/E1 interfaces. The following load related information should be supported which consists of: - Radio resource usage (per-cell and per SSB area PRB usage: DL/UL GBR PRB usage, DL/UL non-GBR PRB usage, DL/UL total PRB usage, and DL/UL scheduling PDCCH CCE usage; PRB usage for slice(s): DL/UL GBR PRB usage, DL/UL non-GBR PRB usage, and DL/UL Total PRB allocation); - TNL capacity indicator (UL/DL TNL offered capacity and available capacity); - Cell Capacity Class value (UL/DL relative capacity indicator); - Capacity value (per cell, per SSB area and per slice: UL/DL available capacity); - HW capacity indicator (offered throughput and available throughput over E1, percentage utilisation over F1); - RRC connections (number of RRC connections, and available RRC Connection Capacity); - Number of active UEs; - NR-U channel load (DL/UL channel occupancy time percentage, DL/UL energy detection threshold, radio resource usage). To achieve load reporting function, Resource Status Reporting Initiation & Resource Status Reporting procedures are used. 15.5.1.3 Load balancing action based on handovers The source cell may initiate handover due to load. The target cell performs admission control for the load balancing handovers. A handover preparation related to a mobility load balancing action is distinguishable from other handovers, so that the target cell is able to apply appropriate admission control. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 15.5.1.2 |
4,458 | 5.3.5.13.4a Conditional reconfiguration evaluation of SN initiated inter-SN CPC for EN-DC | The UE shall: 1> for each condReconfigurationId within the VarConditionalReconfiguration specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10]: 2> for each measId included in the measIdList within VarMeasConfig indicated in the CondReconfigExecCondSCG contained in the triggerConditionSN associated to the condReconfigurationId as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10]: 3> if the entry condition(s) applicable for the event associated with that measId, is fulfilled for the applicable cells for all measurements after layer 3 filtering taken during the corresponding timeToTrigger defined for this event associated with that measId: 4> consider this event to be fulfilled; 3> if the measId for this event has been modified; or 3> if the leaving condition(s) applicable for this event associated with that measId, is fulfilled for the applicable cells for all measurements after layer 3 filtering taken during the corresponding timeToTrigger defined for this event associated with that measId: 4> consider this event associated to that measId to be not fulfilled; 2> if trigger conditions for all events associated with the measId(s) indicated in the CondReconfigExecCondSCG contained in the triggerConditionSN as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10]), are fulfilled: 3> consider the target cell candidate within the RRCReconfiguration message contained in nr-SecondaryCellGroupConfig in the RRCConnectionReconfiguration message, as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10], contained in the stored condReconfigurationToApply, associated to that condReconfigurationId as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10]), clause 5.3.5.9.4, as a triggered cell; 3> initiate the conditional reconfiguration execution, as specified in TS 36.331[ Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification ] [10]), clause 5.3.5.9.5; NOTE: Void. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.5.13.4a |
4,459 | – ProcessingParameters | The IE ProcessingParameters is used to indicate PDSCH/PUSCH processing capabilities supported by the UE. ProcessingParameters information element -- ASN1START -- TAG-PROCESSINGPARAMETERS-START ProcessingParameters ::= SEQUENCE { fallback ENUMERATED {sc, cap1-only}, differentTB-PerSlot SEQUENCE { upto1 NumberOfCarriers OPTIONAL, upto2 NumberOfCarriers OPTIONAL, upto4 NumberOfCarriers OPTIONAL, upto7 NumberOfCarriers OPTIONAL } OPTIONAL } NumberOfCarriers ::= INTEGER (1..16) -- TAG-PROCESSINGPARAMETERS-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
4,460 | – MsgA-PUSCH-Config | The IE MsgA-PUSCH-Config is used to specify the PUSCH allocation for MsgA in 2-step random access type procedure. MsgA-PUSCH-Config information element -- ASN1START -- TAG-MSGA-PUSCH-CONFIG-START MsgA-PUSCH-Config-r16 ::= SEQUENCE { msgA-PUSCH-ResourceGroupA-r16 MsgA-PUSCH-Resource-r16 OPTIONAL, -- Cond InitialBWPConfig msgA-PUSCH-ResourceGroupB-r16 MsgA-PUSCH-Resource-r16 OPTIONAL, -- Cond GroupBConfigured msgA-TransformPrecoder-r16 ENUMERATED {enabled, disabled} OPTIONAL, -- Need R msgA-DataScramblingIndex-r16 INTEGER (0..1023) OPTIONAL, -- Need S msgA-DeltaPreamble-r16 INTEGER (-1..6) OPTIONAL -- Need R } MsgA-PUSCH-Resource-r16 ::= SEQUENCE { msgA-MCS-r16 INTEGER (0..15), nrofSlotsMsgA-PUSCH-r16 INTEGER (1..4), nrofMsgA-PO-PerSlot-r16 ENUMERATED {one, two, three, six}, msgA-PUSCH-TimeDomainOffset-r16 INTEGER (1..32), msgA-PUSCH-TimeDomainAllocation-r16 INTEGER (1..maxNrofUL-Allocations) OPTIONAL, -- Need S startSymbolAndLengthMsgA-PO-r16 INTEGER (0..127) OPTIONAL, -- Need S mappingTypeMsgA-PUSCH-r16 ENUMERATED {typeA, typeB} OPTIONAL, -- Need S guardPeriodMsgA-PUSCH-r16 INTEGER (0..3) OPTIONAL, -- Need R guardBandMsgA-PUSCH-r16 INTEGER (0..1), frequencyStartMsgA-PUSCH-r16 INTEGER (0..maxNrofPhysicalResourceBlocks-1), nrofPRBs-PerMsgA-PO-r16 INTEGER (1..32), nrofMsgA-PO-FDM-r16 ENUMERATED {one, two, four, eight}, msgA-IntraSlotFrequencyHopping-r16 ENUMERATED {enabled} OPTIONAL, -- Need R msgA-HoppingBits-r16 BIT STRING (SIZE(2)) OPTIONAL, -- Cond FreqHopConfigured msgA-DMRS-Config-r16 MsgA-DMRS-Config-r16, nrofDMRS-Sequences-r16 INTEGER (1..2), msgA-Alpha-r16 ENUMERATED {alpha0, alpha04, alpha05, alpha06, alpha07, alpha08, alpha09, alpha1} OPTIONAL, -- Need S interlaceIndexFirstPO-MsgA-PUSCH-r16 INTEGER (1..10) OPTIONAL, -- Need R nrofInterlacesPerMsgA-PO-r16 INTEGER (1..10) OPTIONAL, -- Need R ... } MsgA-DMRS-Config-r16 ::= SEQUENCE { msgA-DMRS-AdditionalPosition-r16 ENUMERATED {pos0, pos1, pos3} OPTIONAL, -- Need S msgA-MaxLength-r16 ENUMERATED {len2} OPTIONAL, -- Need S msgA-PUSCH-DMRS-CDM-Group-r16 INTEGER (0..1) OPTIONAL, -- Need S msgA-PUSCH-NrofPorts-r16 INTEGER (0..1) OPTIONAL, -- Need S msgA-ScramblingID0-r16 INTEGER (0..65535) OPTIONAL, -- Need S msgA-ScramblingID1-r16 INTEGER (0..65535) OPTIONAL -- Need S } -- TAG-MSGA-PUSCH-CONFIG-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
4,461 | 5.16.3.11 P-CSCF discovery and selection | P-CSCF selection functionality may be used by the SMF to select the P-CSCF for an IMS PDU Session of the UE. The SMF can utilize the Network Repository Function to discover the P-CSCF instance(s). The NRF provides the IP address or the FQDN of P-CSCF instance(s) to the SMF. The P-CSCF selection function in the SMF selects the P-CSCF instance(s) based on the available P-CSCF instances obtained from NRF or based on the configured P-CSCF information in the SMF. If the SMF receives FQDN(s) from the NRF or is configured with FQDN(s) the SMF shall resolve these to IP addresses for sending to the UE in the PDU session response. The following factors may be considered during the P-CSCF discovery and selection: - S-NSSAI of the PDU Session. - UE location information. - Local operator policies. - Availability of candidate P-CSCFs. - UE IP address. - Access Type. - Proximity to location of selected UPF. - Selected Data Network Name (DNN). | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.16.3.11 |
4,462 | 6.39.1 Description | The 5G system is expected to support advanced capabilities and performance of enhanced IMS multimedia telephony service to meet new demands from consumers, business customers and vertical markets. Nowadays 3GPP has introduced new network capabilities and new types of devices (e.g. AR/VR/XR devices, robot, etc.), which can bring promising improvements to IMS multimedia telephony service. While more and more individual consumers enjoy multimedia telephony services across the globe, multimedia telephony services become popular also among business customers. There are several primary business functions that organizations use multimedia telephony services for, including internal communication, talking with prospects (sales call), contacting current customers and clients, customer support, and contact centre (or call centre) activities. While business customers consider the multimedia telephony services offer attractive features to their business, they also experience some practical issues that expect support from the 5G system. | 3GPP TS 22.261 | Service requirements for the 5G system | SA WG1 | 3GPP Series : 22 , Service aspects ("stage 1") | 6.39.1 |
4,463 | 5.21.2.3 Procedure for AMF Auto-recovery | In order to try and handle AMF failure in a graceful manner (i.e. without impacting the UE), AMF can either back up the UE contexts in UDSF, or per GUAMI granularity in other AMFs (serving as backup AMF for the indicated GUAMI). NOTE 1: Frequency of backup is left to implementation. For deployments without UDSF, for each GUAMI the backup AMF information (in association to the GUAMI) is configured in the AMF. The AMF sends this information to 5G-AN and other CP NFs during the N2 setup procedure or the first (per NF) interaction with other CP NFs. In the case that an AMF fails and the 5G-AN/peer CP NFs detect that the AMF has failed, or the 5G-AN/peer CP NFs receives notification from another AMF in the same AMF set that this AMF has failed, following actions are taken: - The OAM deregister the AMF from NRF indicating due to AMF failure. - 5G-AN marks this AMF as failed and not consider the AMF for selection until explicitly notified. - For UE(s) in CM-CONNECTED state, 5G-AN considers failure detection or failure notification as a trigger to release the NGAP UE-TNLA-binding(s) with the corresponding AMF for the respective UE(s) while maintaining N3 (user plane connectivity) and other UE context information. For subsequent N2 message, if the backup AMF information of the corresponding failed AMF is not available the 5G-AN should select a different AMF (as in clause 6.3.5) from the same AMF set when the subsequent N2 message needs to be sent for the UE(s). If no other AMF from the AMF set is available, then it can select an AMF (implementation dependent) from the same AMF Region as in clause 6.3.5. If backup AMF information of the corresponding failed AMF is available, the 5G-AN forwards the N2 message to the backup AMF. NOTE 2: One AMF in the AMF set may be configured to send this failure notification message. - For UE(s) in CM-IDLE state, when it subsequently returns from CM-IDLE state and the 5G-AN receives an initial NAS message with a S-TMSI or GUAMI pointing to an AMF that is marked failed, if the backup AMF information of the corresponding failed AMF is not available the 5G-AN should select a different AMF from the same AMF set and forward the initial NAS message. If no other AMF from the AMF set is available, then it can select an AMF (implementation dependent) from the same AMF Region as in clause 6.3.5. If backup AMF information of the corresponding failed AMF is available, the 5G-AN forwards the N2 message to the backup AMF. - Peer CP NFs consider this AMF as unavailable while retaining the UE context. - For the UE(s) that were associated to the corresponding AMF, when the peer CP NF needs to initiate a transaction towards the AMF, if backup AMF information of the corresponding failed AMF is not available, CP NF should select another AMF from the same AMF set and forward the transaction together with the old GUAMI. If neither the backup AMF nor any other AMF from the AMF set is available, then CP NF can select an AMF from the same AMF Region as in clause 6.3.5. If backup AMF information of the corresponding failed AMF is available, the CP NF forwards transaction to the backup AMF. If CP NF needs to send a notification to new AMF which is associated with a subscription from the old AMF, the CP NF shall exchange the old AMF information embedded in the Notification Address with the new AMF information, and use that Notification Address for subsequent communication. - When the 5G-AN or CP NFs need to select a different AMF from the same AMF set, - For deployments with UDSF, any AMF from the same AMF set can be selected. - For deployments without UDSF, the backup AMF is determined based on the GUAMI of the failed AMF. Following actions should be taken by the newly selected AMF: - For deployments with UDSF, when there is a transaction with the UE the newly selected AMF retrieves the UE context from the UDSF using SUPI, 5G-GUTI or AMF UE NGAP ID and it processes the UE message accordingly and updates the 5G-GUTI towards the UE, if necessary. - For deployments without UDSF, backup AMF (the newly selected AMF), based on the failure detection of the old AMF, instructs peer CP NFs and 5G-AN that the UE contexts corresponding to the GUAMI of the failed AMF is now served by this newly selected AMF. The backup AMF shall not use old GUAMI to allocate 5G-GUTI for UE(s) that are being served by Target AMF. The backup AMF uses the GUAMI to locate the respective UE Context(s). - When there is a transaction with the UE, the new AMF updates the peer NFs (that subscribed to receive AMF unavailability notification from old AMF) with the new AMF information. - If the new AMF is aware of a different AMF serving the UE (by implementation specific means) it redirects the uplink N2 signalling to that AMF, or reject the transaction from the peer CP NFs with a cause to indicate that new AMF has been selected. The peer CP NFs may wait for the update from the new AMF and resend the transaction to the new AMF. NOTE 3: This bullet above addresses situations where 5G-AN node selects an AMF and other CP NFs select an AMF for the UE concurrently. It also addresses the situation where CP NFs select an AMF for the UE concurrently. NOTE 4: It is assumed that the UE contexts from the old AMF include all event subscriptions with peer CP NFs. - If the UE is in CM-IDLE state and the new AMF does not have access to the UE context, the new AMF selects one available AMF from the old AMF set as described in clause 6.3.5. The selected AMF retrieves the UE context from the UDSF and provides the UE context to the new AMF. If the new AMF doesn't receive the UE context then the AMF may force the UE to perform Initial Registration. - If the UE is in CM-CONNECTED state, the new AMF may also update the NGAP UE association with a new AMF UE NGAP ID towards the 5G-AN and replace the GUAMI in the UE context stored at the 5G-AN with the new GUAMI associated with the newly selected AMF if the 5G-GUTI has been updated. NOTE 5: The above N2 TNL association selection and AMF management is applied to the selected PLMN. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.21.2.3 |
4,464 | 9 Security related aspects | MR-DC can only be configured after security activation in the MN. In EN-DC and NGEN-DC, for bearers terminated in the MN the network configures the UE with KeNB; for bearers terminated in the SN the network configures the UE with S-KgNB. In NE-DC, for bearers terminated in the MN the network configures the UE with KgNB; for bearers terminated in the SN the network configures the UE with S-KeNB. In NR-DC, for bearers terminated in the MN the network configures the UE with KgNB; for bearers terminated in the SN the network configures the UE with S-KgNB. In NE-DC and NR-DC, a PCell change without KgNB change does not require a S-KeNB change (NE-DC case) or a S-KgNB change (NR-DC case). In EN-DC, NGEN-DC and NR-DC, for a PSCell change that does not require a KeNB change (i.e. no simultaneous PCell handover in EN-DC and NGEN-DC) or a KgNB change (in NR-DC), S-KgNB key refresh is not required if the PDCP termination point of the SN is not changed. In NE-DC, a PSCell change always requires a S-KeNB change. In EN-DC, the UE supports the NR security algorithms corresponding to the E-UTRA security algorithms signalled at NAS level and the UE NR AS Security capability is not signalled to the MN over RRC. Mapping from E-UTRA security algorithms to the corresponding NR security algorithms, where necessary, is performed at the MN. The MN sends the complete UE security capabilities including all security capability bits previously received (after mapping, where necessary) to the SN. An EN-DC capable UE supporting user plane integrity protection when connected to E-UTRA/EPC (see TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [22]) shall support integrity protection for all DRBs (MN and SN terminated) at any data rate, up to and including the highest data rate supported by the UE for both UL and DL. MN and/or SN terminated DRBs can have UP integrity protection activation either on or off, on a per radio bearer basis. For MR-DC with 5GC, UP integrity protection can be configured on a per radio bearer basis. All DRBs which belong to the same PDU session always have the same UP integrity protection activation, i.e., either on or off: - For NR-DC: MN and/or SN terminated DRBs of a PDU session can have UP integrity protection activation either on or off. A UE configured to operate in NR-DC shall support integrity protection for all DRBs (MN and SN terminated) at any data rate, up to and including the highest data rate supported by the UE for both UL and DL (see TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [3]). - For NE-DC: MN terminated DRBs of a PDU session can have UP integrity protection activation on; however, in this case, the MN will not at any point offload any DRB of such PDU session to the SN. A UE configured to operate in NE-DC shall support integrity protection for all MN terminated DRBs at any data rate, up to and including the highest data rate supported by the UE's radio access capabilities for both UL and DL (see TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [3]). SN terminated DRBs of a PDU session always have UP integrity protection activation off. - For NGEN-DC: Both MN terminated and SN terminated DRBs of a PDU session always have UP integrity protection activation off. In MR-DC with 5GC, the MN sends the complete UE security capabilities to the SN including all NR and E-UTRA security capability bits previously received by the MN from the Core Network or from another NG-RAN node as specified in TS 38.300[ NR; NR and NG-RAN Overall description; Stage-2 ] [3]. In (NG)EN-DC and NR-DC, if the SCG is deactivated as described in clause 7.13, whether to perform security key update upon SCG activation is up to network implementation. | 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 | 9 |
4,465 | 5.11.1 Support for Dual Connectivity | Dual Connectivity involves two radio network nodes in providing radio resources to a given UE (with active radio bearers), while a single N2 termination point exists for the UE between an AMF and the RAN. The RAN architecture and related functions to support Dual Connectivity is further described in RAN specifications (e.g. TS 37.340[ Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Overall Description; Stage-2 ] [31]). In this Release of the specification, the Dual Connectivity function does not apply to the NR RedCap UE. The RAN node at which the N2 terminates, performs all necessary N2 related functions such as mobility management, relaying of NAS signalling, etc. and manages the handling of user plane connection (e.g. transfer over N3). It is called the Master RAN Node. It may use resources of another RAN node, the Secondary RAN node, to exchange User Plane traffic of an UE. Master RAN node takes into account the RSN and/or PDU Session Pair ID to determine if dual connectivity shall be set up and ensure appropriate PDU session handling ensures fully redundant user plane path as described in clause 5.33.2.1. If the UE has Mobility Restriction (either signalled from the UDM, or, locally generated by the Serving PLMN policy in the AMF) the AMF signals these restrictions to the Master RAN Node as Mobility Restriction List; This may prevent the Master RAN node from setting up a Dual Connectivity for an UE. NOTE 1: Subject to policies in the NG-RAN, configuration of Dual Connectivity for a Data Radio Bearer can also be based on the Network Slice that the PDU Session belongs to. Dual Connectivity provides the possibility for the Master RAN node to request SMF: - For some or all PDU Sessions of an UE: Direct all the DL User Plane traffic of the PDU Session to the either the Master RAN Node or to the Secondary RAN Node. In this case, there is a single N3 tunnel termination at the RAN for such PDU Session. NOTE 2: The terminating RAN Node, can decide to keep traffic for specific QFI(s) in a PDU Session for a UE on a single RAT, or split them across the two RATs. - For some other PDU Sessions of an UE: Direct the DL User Plane traffic of some QoS Flows of the PDU Session to the Secondary (respectively Master) RAN Node while the remaining QoS Flows of the PDU Session are directed to the Master (respectively Secondary) RAN Node. In this case there are, irrespective of the number of QoS Flows, two N3 tunnel terminations at the RAN for such PDU Session. The Master RAN node may create and change this assignment for the user plane of a PDU Session at any time during the life time of the PDU Session; In both cases, a single PDU Session Id is used to identify the PDU Session. Additional functional characteristics are: - User location information is based on the identity of the cell that is serving the UE in the Master RAN node. The cell identity of the Primary cell in the secondary RAN node may also be included. NG-RAN includes the user location information in NGAP messages where the contents of the user location information may change during the corresponding procedure. - Path update signalling related with Dual Connectivity and UPF re-allocation cannot occur at the same time. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.11.1 |
4,466 | – SL-BWP-DiscPoolConfigCommon | The IE SL-BWP-DiscPoolConfigCommon is used to configure the cell-specific NR sidelink discovery dedicated resource pool. SL-BWP-DiscPoolConfigCommon information element -- ASN1START -- TAG-SL-BWP-DISCPOOLCONFIGCOMMON-START SL-BWP-DiscPoolConfigCommon-r17 ::= SEQUENCE { sl-DiscRxPool-r17 SEQUENCE (SIZE (1..maxNrofRXPool-r16)) OF SL-ResourcePool-r16 OPTIONAL, -- Need R sl-DiscTxPoolSelected-r17 SEQUENCE (SIZE (1..maxNrofTXPool-r16)) OF SL-ResourcePoolConfig-r16 OPTIONAL, -- Need R ... } -- TAG-SL-BWP-DISCPOOLCONFIGCOMMON-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
4,467 | 5.6.1.2.2 UE is using 5GS services with control plane CIoT 5GS optimization | The UE shall send a CONTROL PLANE SERVICE REQUEST message, start T3517 and enter the state 5GMM-SERVICE-REQUEST-INITIATED. For case a), and case b) in subclause 5.6.1.1, the Control plane service type of the CONTROL PLANE SERVICE REQUEST message shall indicate "mobile terminating request". If: a) the UE only has uplink CIoT user data or SMS to be sent, the UE shall: 1) if the data size is not more than 254 octets and there is no other optional IE to be included in the message: i) for sending CIoT user data, set the Data type field to "control plane user data", include the PDU session ID, data, and Downlink data expected (DDX) (if available), in the CIoT small data container IE; and ii) for sending SMS, set the Data type field to "SMS", include SMS in the CIoT small data container IE; and 2) otherwise if the data size is more than 254 octets or there are other optional IEs to be included in the message: i) for sending CIoT user data, set the Payload container type IE to "CIoT user data container", include the PDU session ID in the PDU session ID IE and include data in the Payload container IE as described in subclause 5.4.5.2.2; and ii) for sending SMS, set the Payload container type IE to "SMS" and include data in the Payload container IE as described in subclause 5.4.5.2.2; and b) the paging request or the notification includes an indication for non-3GPP access type, the UE has at least one PDU session that is not associated with control plane only indication, the Allowed PDU session status IE shall be included in the CONTROL PLANE SERVICE REQUEST message. If the UE is in a non-allowed area or the UE is not in an allowed area, the UE shall set the Allowed PDU session status IE as specified in subclause 5.3.5.2. If the UE has PDU session(s) associated with non-3GPP access for which the associated S-NSSAI(s) are included in the allowed NSSAI for 3GPP access or the S-NSSAI associated with the PDU session is included in the partially allowed NSSAI for 3GPP access and the TAI where the UE is currently camped is in list of TAs for which the S-NSSAI is supported, the UE shall indicate the PDU session(s) for which the UE allows the user-plane resources to be re-established over 3GPP access in the Allowed PDU session status IE. Otherwise, the UE shall not indicate any PDU session(s) in the Allowed PDU session status IE. NOTE 1: The term DDX used in the present document corresponds to the term NAS RAI used in 3GPP TS 23.502[ Procedures for the 5G System (5GS) ] [9]. For case c), and case d), when the UE is located outside the LADN service area, the UE shall not perform the service request procedure to send CIoT user data via the control plane for a PDU session for LADN. For case c), and case d) if the UE has pending CIoT user data that is to be sent via the control plane in subclause 5.6.1.1, the UE shall set the Control plane service type of the CONTROL PLANE SERVICE REQUEST message to "mobile originating request". If the UE has only uplink CIoT user data, SMS or location services message to be sent, the UE shall: a) if the data size is not more than 254 octets, there is no other optional IE to be included in the CONTROL PLANE SERVICE REQUEST message, and the data being sent is: 1) CIoT user data, set the Data type field to "control plane user data", include the PDU session ID, data, and Downlink data expected (DDX) (if available), in the CIoT small data container IE; 2) location services message, set the Data type field to "Location services message container" and Downlink data expected (DDX), if available, in the CIoT small data container IE, and: i) if routing information is provided by upper layers: A) set the length of additional information field in the CIoT small data container IE to the length of routing information provided by upper layer location services application (see subclause 9.11.3.67), and set the additional information field in the CIoT small data container IE to the routing information provided by upper layer location services application (see subclause 9.11.3.67); or B) otherwise set the length of additional information field in the CIoT small data container IE to zero. In this case the Additional information field of the CIoT small data container IE shall not be included; and ii) set the Data contents field of the CIoT small data container IE to the location services message payload; or 3) SMS, set the Data type field to "SMS", include SMS in the CIoT small data container IE; or b) otherwise if the data size is more than 254 octets or there are other optional IEs to be included in the CONTROL PLANE SERVICE REQUEST message, and the data being sent is: 1) CIoT user data, set the Payload container type IE to "CIoT user data container", include the PDU session ID in the PDU session ID IE and include data in the Payload container IE as described in subclause 5.4.5.2.2; 2) location services message, set the Payload container type IE to "Location services message container", include data in the Payload container IE as described in subclause 5.4.5.2.2. If the upper layer location services application provides the routing information set the Additional information IE to the routing information as described in subclause 5.4.5.2.2; or 3) SMS, set the Payload container type IE to "SMS" and include data in the Payload container IE as described in subclause 5.4.5.2.2. For case a), and case b) in subclause 5.6.1.1, if the UE has pending user data that is to be sent via the user plane, the UE shall set the Control plane service type of the CONTROL PLANE SERVICE REQUEST message to "mobile terminating request". The UE shall include the Uplink data status IE in the CONTROL PLANE SERVICE REQUEST message to indicate which PDU session(s) have pending user data to be sent via user-plane resources. For case c) in subclause 5.6.1.1, if the UE is in WB-N1 mode and the CONTROL PLANE SERVICE REQUEST message is triggered by a request for emergency services from the upper layer, the UE shall set the Control plane service type of the CONTROL PLANE SERVICE REQUEST message to "emergency services". For cases d) and k), if the UE has pending user data that is to be sent via the user plane in subclause 5.6.1.1: a) and if there exists an emergency PDU session which is indicated in the Uplink data status IE, the UE shall set the Control plane service type of the CONTROL PLANE SERVICE REQUEST message to "emergency services"; or b) otherwise, the UE shall set the Control plane service type to "mobile originating request". The UE shall include the Uplink data status IE in the CONTROL PLANE SERVICE REQUEST message to indicate which PDU session(s) have pending user data to be sent via user-plane resources or are associated with active multicast MBS session(s). NOTE 2: For a UE in NB-N1 mode, the Uplink data status IE cannot be used to request the establishment of user-plane resources such that there will be user-plane resources established for a number of PDU sessions that exceeds the UE's maximum number of supported user-plane resources. For case h) in subclause 5.6.1.1, if the UE is in WB-N1 mode and the UE does not have any PDU session that is associated with control plane only indication, the UE shall send a CONTROL PLANE SERVICE REQUEST message with the Control plane service type set to "emergency services fallback" and without an Uplink data status IE. For case i) in subclause 5.6.1.1, the Control plane service type of the CONTROL PLANE SERVICE REQUEST message shall indicate "mobile originating request". If the pending message is an UL NAS TRANSPORT message with the Payload container type IE set to: a) "SMS", "Location services message container", or "CIoT user data container", the UE shall send the CONTROL PLANE SERVICE REQUEST and include the SMS, location services message, or CIoT user data as described in this subclause; or b) otherwise, the UE shall send the CONTROL PLANE SERVICE REQUEST: 1) without including the CIoT small data container IE and without including the NAS message container IE if the UE has no other optional IE to be sent; or 2) with the NAS message container IE if the UE has an optional IE to be sent as described in this subclause. For case j) in subclause 5.6.1.1, the Control plane service type of the CONTROL PLANE SERVICE REQUEST message shall indicate "mobile originating request". The UE shall include the Uplink data status IE in the CONTROL PLANE SERVICE REQUEST message indicating the PDU session(s) for which user-plane resources were active prior to receiving the fallback indication, if any. For cases o) and p) in subclause 5.6.1.1, the UE shall not include the Uplink data status IE and the Allowed PDU session status IE in the CONTROL PLANE SERVICE REQUEST message. Further, - for case o) in subclause 5.6.1.1, the UE shall set Request type to "NAS signalling connection release" in the UE request type IE and Control plane service type to "mobile originating request"; - for case p) in subclause 5.6.1.1, the UE shall set Request type to "Rejection of paging" in the UE request type IE and Control plane service type to "mobile terminating request"; and may include its paging restriction preferences in the Paging restriction IE in the CONTROL PLANE SERVICE REQUEST message. For case m) in subclause 5.6.1.1, the Control plane service type of the CONTROL PLANE SERVICE REQUEST message shall indicate "mobile originating request". The UE shall not include the Paging restriction IE in the CONTROL PLANE SERVICE REQUEST message. The UE may include the UE request type IE and set Request type to "NAS signalling connection release" to remove the paging restriction and request the release of the NAS signalling connection at the same time. If the UE requests the release of the NAS signalling connection, the UE shall not include the Uplink data status IE in the SERVICE REQUEST message. For all cases, if the UE includes the Uplink data status IE and the UE is located outside the LADN service area of a PDU session, the UE shall not include the PDU session for LADN in the Uplink data status IE. If the UE is in a non-allowed area or the UE is not in an allowed area, the UE shall apply the restrictions for the inclusion of the Uplink data status IE specified in subclause 5.3.5.2. The UE may include the PDU session status IE in the CONTROL PLANE SERVICE REQUEST message to indicate which PDU session(s) associated with the access type the CONTROL PLANE SERVICE REQUEST message is sent over are active in the UE. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 5.6.1.2.2 |
4,468 | 6.4.1.5A Handling the maximum number of allowed active user-plane resources for PDU sessions of UEs in NB-N1 mode | For a UE in NB-N1 mode, the UE's maximum number of supported user-plane resources is two (as defined in 3GPP TS 36.300[ Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 ] [25B]) when the UE sets the Multiple user-plane resources support bit to "Multiple user-plane resources supported" during the registration procedure for initial registration or for mobility and periodic registration update, and one otherwise. For a UE operating in NB-N1 mode, if: a) the UE's maximum number of supported user-plane resources is one, then only one PDU session can have active user-plane resources even though that UE might have established more than one PDU session; or b) the UE's maximum number of supported user-plane resources is two, then only two PDU sessions can have active user-plane resources even though that UE might have established more than two PDU sessions. When the maximum number of active user-plane resources is reached and upper layers request for more user-plane resources for PDU sessions other than the PDU sessions with those active user-plane resources, the UE can choose to release one or more of the PDU sessions with active user-plane resources to cater for the upper layer request. The choice of which PDU sessions to be released is implementation specific. However if there is a PDU session with an active user-plane that is used for exception data reporting (see subclause 6.2.13), that PDU session shall not be released. If the maximum number of active user-plane resources is reached and the upper layers of the UE request user-plane resources for exception data reporting (see subclause 6.2.13), the UE shall release a PDU session that has user-plane resources to cater for the request for exception data reporting. The choice of which PDU session to be released is implementation specific. If the UE decides to release one or more active user-plane resources to cater for upper layer request, the UE shall release the PDU session via explicit 5GSM signalling. | 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.1.5A |
4,469 | 12.2.1 Principles of load control | The stage 2 requirements on GTP-C load control solution are defined in clause 4.3.7.1a.1 of 3GPP TS 23.401[ General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access ] [3] and clause 5.3.6.1a of 3GPP TS 23.060[ General Packet Radio Service (GPRS); Service description; Stage 2 ] [35]. The high level principles are summarized below: a) Load Control is an optional feature; b) a GTP-C node may signal its Load Control Information to reflect the operating status of its resources, allowing the receiving GTP-C peer node to use this information to augment the existing GW selection procedures; c) the calculation of the Load Control Information is implementation dependent and its calculation and transfer shall not add significant additional load to the node itself and to its corresponding peer nodes; d) the Load Control Information may provide load information of a GTP-C node (e.g. a PGW) or, if the APN level load control feature is supported, may provide the load information about specific APN(s); e) the SGW may send its Load Control Information to the MME/S4-SGSN. The PGW may send its Load Control Information to the MME/S4-SGSN via the SGW. For non-3GPP access based interfaces, the PGW may send its Load Control Information to the ePDG and TWAN; f) the Load Control Information shall be piggybacked in GTP-C request or response messages such that the exchange of Load Control Information does not trigger extra signalling; NOTE: The inclusion of Load Control Information in existing messages means that the frequency of transmission of load control information increases as the session load increases, allowing for faster feedback and thus better regulation of the load. g) a node supporting Load Control sends Load Control Information to a peer GTP-C node based on local configuration (see clause 12.2.6); h) the format of the Load Control Information shall be specified with enough precision to guarantee a common interpretation of this information allowing interoperability between nodes of different vendors; i) for the inter-PLMN case, local configuration may restrict the exchange and use of Load Control Information across PLMNs; j) the GTP-C node may decide to send different values of Load Control Information on inter-network (roaming) and on intra-network (non-roaming) interfaces based on local configuration, i.e. the values sent on intra-network interfaces may differ from the values sent on inter-network interfaces. However, on intra-network interfaces, the node should send the same values between the 3GPP and non-3GPP access based interfaces. k) the Load Control Information received via GTP-C signalling shall be used in conjunction with the information received from the DNS, during the node selection procedure. Refer to 3GPP TS 29.303[ Domain Name System Procedures; Stage 3 ] [32] for further details. | 3GPP TS 29.274 | 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C); Stage 3 | CT WG4 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 12.2.1 |
4,470 | 5.4.9 Timing Advance Reporting | The UE may be configured to report information about timing advance during a Random Access procedure and in RRC_CONNECTED Mode. The Timing Advance reporting procedure is used in a non-terrestrial network to provide the eNB with an estimate of the UE's Timing Advance, see TTA in TS 36.211[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation ] [7] clause 8.1. Timing Advance reporting shall be triggered if any of the following events occur: - if triggered by upper layers; - upon configuration of offsetThresholdTA by upper layers, if the UE has not previously reported Timing Advance value to current Serving Cell; - if the variation between current information about Timing Advance and the last reported information about Timing Advance is equal to or larger than offsetThresholdTA, if configured. If the Timing Advance reporting procedure determines that at least one Timing Advance Report has been triggered and not cancelled: - if the MAC entity has UL resources allocated for new transmission for this TTI, and; - if the allocated UL resources can accommodate the Timing Advance Report MAC control element plus its subheader, as a result of logical channel prioritization: - instruct the Multiplexing and Assembly procedure to generate the Timing Advance report MAC control element as defined in clause 6.1.3.20. A MAC PDU shall contain at most one Timing Advance Report MAC CE, even when multiple events have triggered a Timing Advance report. The Timing Advance Report MAC CE shall be generated based on the latest available estimate of the UE's Timing Advance value prior to the MAC PDU assembly. All triggered Timing Advance reports shall be cancelled when a Timing Advance Report MAC CE is included in a MAC PDU for transmission. | 3GPP TS 36.321 | Evolved Universal Terrestrial Radio Access (E-UTRA); Medium Access Control (MAC) protocol specification | RAN2 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 5.4.9 |
4,471 | 5.1.1 User identity confidentiality | The following security features related to user identity confidentiality are provided: - user identity confidentiality: the property that the permanent user identity (IMSI) of a user to whom a services is delivered cannot be eavesdropped on the radio access link; - user location confidentiality: the property that the presence or the arrival of a user in a certain area cannot be determined by eavesdropping on the radio access link; - user untraceability: the property that an intruder cannot deduce whether different services are delivered to the same user by eavesdropping on the radio access link. To achieve these objectives, the user is normally identified by a temporary identity by which he is known by the visited serving network. To avoid user traceability, which may lead to the compromise of user identity confidentiality, the user should not be identified for a long period by means of the same temporary identity. To achieve these security features, in addition it is required that any signalling or user data that might reveal the user's identity is ciphered on the radio access link. Clause 6.1 describes a mechanism that allows a user to be identified on the radio path by means of a temporary identity by which he is known in the visited serving network. This mechanism should normally be used to identify a user on the radio path in location update requests, service requests, detach requests, connection re-establishment requests, etc. | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | 5.1.1 |
4,472 | 5.7.1 Time and frequency structure | The physical layer random access preamble, illustrated in Figure 5.7.1-1, consists of a cyclic prefix of length and a sequence part of length. The parameter values are listed in Table 5.7.1-1 and depend on the frame structure and the random access configuration. Higher layers control the preamble format. Figure 5.7.1-1: Random access preamble format Table 5.7.1-1: Random access preamble parameters The transmission of a random access preamble, if triggered by the MAC layer, is restricted to certain time and frequency resources. These resources are enumerated in increasing order of the subframe number within the radio frame and the physical resource blocks in the frequency domain such that index 0 correspond to the lowest numbered physical resource block and subframe within the radio frame. PRACH resources within the radio frame are indicated by a PRACH configuration index, where the indexing is in the order of appearance in Table 5.7.1-2 and Table 5.7.1-4. For non-BL/CE UEs there are up to two PRACH configurations in a cell. The first PRACH configuration is configured by higher layers with a PRACH configuration index (prach-ConfigurationIndex) and a PRACH frequency offset (prach-FrequencyOffset). The second PRACH configuration (if any) is configured by higher layers with a PRACH configuration index (prach-ConfigurationIndexHighSpeed) and a PRACH frequency offset (prach-FrequencyOffsetHighSpeed). For BL/CE UEs, for each PRACH coverage enhancement level, there is a PRACH configuration configured by higher layers with a PRACH configuration index (prach-ConfigurationIndex), a PRACH frequency offset (prach-FrequencyOffset), a number of PRACH repetitions per attempt (numRepetitionPerPreambleAttempt) and optionally a PRACH starting subframe periodicity (prach-StartingSubframe). PRACH of preamble format 0-3 is transmitted times, whereas PRACH of preamble format 4 is transmitted one time only. For BL/CE UEs and for each PRACH coverage enhancement level, if frequency hopping is enabled for a PRACH configuration by the higher-layer parameter prach-HoppingConfig, the value of the parameter depends on the SFN and the PRACH configuration index and is given by - In case the PRACH configuration index is such that a PRACH resource occurs in every radio frame when calculated as below from Table 5.7.1-2 or Table 5.7.1-4, - otherwise where is the system frame number corresponding to the first subframe for each PRACH repetition, corresponds to a cell-specific higher-layer parameter prach-HoppingOffset. If frequency hopping is not enabled for the PRACH configuration then . For frame structure type 1 with preamble format 0-3, for each of the PRACH configurations there is at most one random access resource per subframe. Table 5.7.1-2 lists the preamble formats according to Table 5.7.1-1 and the subframes in which random access preamble transmission is allowed for a given configuration in frame structure type 1. The start of the random access preamble shall be aligned with the start of the corresponding uplink subframe at the UE assuming , where is defined in clause 8.1. For PRACH configurations 0, 1, 2, 15, 16, 17, 18, 31, 32, 33, 34, 47, 48, 49, 50 and 63 the UE may for handover purposes assume an absolute value of the relative time difference between radio frame in the current cell and the target cell of less than . The first physical resource block allocated to the PRACH opportunity considered for preamble formats 0, 1, 2 and 3 is defined as . Table 5.7.1-2: Frame structure type 1 random access configuration for preamble formats 0-3 For frame structure type 2 with preamble formats 0-4, for each of the PRACH configurations there might be multiple random access resources in an UL subframe (or UpPTS for preamble format 4) depending on the UL/DL configuration [see table 4.2-2]. Table -3 lists PRACH configurations allowed for frame structure type 2 where the configuration index corresponds to a certain combination of preamble format, PRACH density value, and version index, . For frame structure type 2 with PRACH configuration indices 0, 1, 2, 20, 21, 22, 30, 31, 32, 40, 41, 42, 48, 49, 50, or with PRACH configuration indices 51, 53, 54, 55, 56, 57 in UL/DL configuration 3, 4, 5, the UE may for handover purposes assume an absolute value of the relative time difference between radio frame in the current cell and the target cell is less than . Table -3: Frame structure type 2 random access configurations for preamble formats 0-4 Table 5.7.1-4 lists the mapping to physical resources for the different random access opportunities needed for a certain PRACH density value, . Each quadruple of the format indicates the location of a specific random access resource, where is a frequency resource index within the considered time instance, indicates whether the resource is reoccurring in all radio frames, in even radio frames, or in odd radio frames, respectively, indicates whether the random access resource is located in first half frame or in second half frame, respectively, and where is the uplink subframe number where the preamble starts, counting from 0 at the first uplink subframe between 2 consecutive downlink-to-uplink switch points, with the exception of preamble format 4 where is denoted as (*). The start of the random access preamble formats 0-3 shall be aligned with the start of the corresponding uplink subframe at the UE assuming and the random access preamble format 4 shall start before the end of the UpPTS at the UE, where the UpPTS is referenced to the UE's uplink frame timing assuming. The random access opportunities for each PRACH configuration shall be allocated in time first and then in frequency if and only if time multiplexing is not sufficient to hold all opportunities of a PRACH configuration needed for a certain density value without overlap in time. For preamble format 0-3, the frequency multiplexing shall be done according to where is the number of uplink resource blocks, is the first physical resource block allocated to the PRACH opportunity considered and where is the first physical resource block available for PRACH. For preamble format 4, the frequency multiplexing shall be done according to whereis the system frame number and whereis the number of DL to UL switch points within the radio frame. For BL/CE UEs, only a subset of the subframes allowed for preamble transmission are allowed as starting subframes for the repetitions. The allowed starting subframes for a PRACH configuration are determined as follows: - Enumerate the subframes that are allowed for preamble transmission for the PRACH configuration as where and correspond to the two subframes allowed for preamble transmission with the smallest and the largest absolute subframe number , respectively. - If a PRACH starting subframe periodicity is not provided by higher layers, the periodicity of the allowed starting subframes in terms of subframes allowed for preamble transmission is . The allowed starting subframes defined over are given by where - If a PRACH starting subframe periodicity is provided by higher layers, it indicates the periodicity of the allowed starting subframes in terms of subframes allowed for preamble transmission. The allowed starting subframes defined over are given by where - No starting subframe defined over such that is allowed. Each random access preamble occupies a bandwidth corresponding to 6 consecutive resource blocks for both frame structures. Table 5.7.1-4: Frame structure type 2 random access preamble mapping in time and frequency | 3GPP TS 36.211 | Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation | RAN1 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 5.7.1 |
4,473 | D.2.1.3 Network-requested UE policy management procedure accepted by the UE | If all instructions included in the UE policy section management list IE were executed successfully by the UE, the UE shall: a) create a MANAGE UE POLICY COMPLETE message including the PTI value received within the MANAGE UE POLICY COMMAND message; and b) transport the MANAGE UE POLICY COMPLETE message using the NAS transport procedure as specified in subclause 5.4.5. Upon receipt of the MANAGE UE POLICY COMPLETE message, the PCF shall stop timer T3501. The PCF should ensure that the PTI value assigned to this procedure is not released immediately. NOTE: The way to achieve this is implementation dependent. For example, the PCF can ensure that the PTI value assigned to this procedure is not released during the time equal to or greater than the default value of timer T3501. | 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 | D.2.1.3 |
4,474 | 4.15.2.3 Void 4.22.1 General | A 5GS can support UAV identification, authentication, and authorization (see 3GPP TS 23.256[ Support of Uncrewed Aerial Systems (UAS) connectivity, identification and tracking; Stage 2 ] [6AB]). This subclause describes NAS-specific aspects of the 5GS features to support UAV identification, authentication, authorization and C2 communication authorization. Before accessing 5GS for UAS services, the UE supporting UAS services must have an assigned CAA-level UAV ID. The UE can be registered to 5GS for UAS services if there is a valid aerial subscription in the UE's subscription. | 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.15.2.3 |
4,475 | 5.4.11.4 Verification of UE location | In order to ensure that the regulatory requirements are met, the network may be configured to enforce that the selected PLMN is allowed to operate in the current UE location by verifying the UE location during Mobility Management and Session Management procedures. In this case, when the AMF receives a NGAP message containing User Location Information for a UE using NR satellite access, the AMF may decide to verify the UE location. If the AMF determines based on the Selected PLMN ID and ULI (including Cell ID) received from the gNB that it is not allowed to operate at the present UE location the AMF should reject any NAS request with a suitable cause value. If the UE is already registered to the network when the AMF determines that it is not allowed to operate at the present UE location, the AMF may initiate deregistration of the UE. The AMF should not reject the request or deregister the UE unless it has sufficiently accurate UE location information to determine that the UE is located in a geographical area where the PLMN is not allowed to operate. NOTE: The area where the UE is allowed to operate can be determined based on the regulatory area where the PLMN is allowed to operate based on its licensing conditions. If the AMF, based on the ULI, is not able to determine the UE's location with sufficient accuracy to make a final decision or if the received ULI is not sufficiently reliable, the AMF proceeds with the Mobility Management or Session Management procedure and may initiate UE location procedure after the Mobility Management or Session Management procedure is complete, as specified in clause 6.10.1 of TS 23.273[ 5G System (5GS) Location Services (LCS); Stage 2 ] [87], to determine the UE location. The AMF shall be prepared to deregister the UE if the information received from LMF indicates that the UE is registered to a PLMN that is not allowed to operate in the UE location. In the case of a NAS procedure, the AMF should either reject any NAS request targeted towards a PLMN that is not allowed to operate in the known UE location and indicate a suitable cause value, or accept the NAS procedure and initiate deregistration procedure once the UE location is known. In the deregistration message to the UE, the AMF shall include a suitable cause value. For UE processing of the cause value indicating that the PLMN is not allowed to operate in the current UE location, see TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [17] and TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [47]. In the case of a handover procedure, if the (target) AMF determines that it is not allowed to operate at the current UE location, the AMF either rejects the handover, or accepts the handover and later deregisters the UE. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.4.11.4 |
4,476 | 8.134 Maximum Packet Loss Rate | The Maximum Packet Loss Rate IE is used to carry bearer loss rate for uplink and downlink traffic. It is coded as shown in Figure 8.134-1. Figure 8.134-1: Maximum Packet Loss Rate The UL flag in octet 5 indicates whether the Maximum Packet Loss Rate UL value in octets 'm to m+1' shall be present. If UL is set to '1', then the Maximum Packet Loss Rate UL value shall be present. If UL is set to '0', then octets 'm to m+1' shall not be present. The DL flag in octet 5 indicates whether the Maximum Packet Loss Rate DL value in octets 'o to o+1' shall be present. If DL is set to '1', then the Maximum Packet Loss Rate DL value shall be present. If DL is set to '0', then octets 'o to o+1' shall not be present. The Maximum Packet Loss Rate for UL and DL shall be coded as an unsigned integer in the range of 0 to 1000. It shall be interpreted as Ratio of lost packets per number of packets sent, expressed in tenth of percent. | 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.134 |
4,477 | 10.2.3.4 Mapping to resource elements | Each NPDSCH codeword can be mapped to one or more than one subframes, , as given by clause 16.4.1.3 of TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [4], each of which shall be transmitted times. For each of the antenna ports used for transmission of the physical channel, the block of complex-valued symbols shall be mapped to resource elements which meet all of the following criteria in the current subframe: - the subframe is not used for transmission of NPBCH, NPSS, or NSSS, and - except in a special subframe when , they are assumed by the UE not to be used for NRS, and - they are not overlapping with resource elements used for CRS as defined in clause 6 (if any), and - the index in the first slot in a subframe fulfils where is given by clause 16.4.1.4 of TS 36.213[ Evolved Universal Terrestrial Radio Access (E-UTRA); Physical layer procedures ] [4], and - in addition, for frame structure type 2 - in a special subframe, if , they are in DwPTS - in a special subframe, if , they are not NRS locations in subframes which are not special subframes. The mapping of in sequence starting with to resource elements on antenna port meeting the criteria above shall be in increasing order of first the index and then the index, starting with the first slot and ending with the second slot in a subframe. For NPDSCH not carrying BCCH, after mapping to a subframe, the subframe shall be repeated for additional subframes, before continuing the mapping of to the following subframe. The resource elements in a special subframe that are not part of DwPTS are counted but not used in the mapping if . When , the resource elements in a special subframe assumed by the UE for NRSs are counted but not used in the mapping if . For frame structure type 1, - for NPDSCH associated with C-RNTI when interferenceRandomisationConfig is used according to [9], or - for NPDSCH associated with RA-RNTI, TC-RNTI or P-RNTI and transmitted in an NB-IoT carrier configured by SystemInformationBlockType22-NB, or - for NPDSCH associated with C-RNTI in an NB-IoT carrier configured by SystemInformationBlockType22-NB when RadioResourceConfigDedicted-NB is not configured by higher layer, or - for NPDSCH associated with PUR-RNTI/G-RNTI/ SC-RNTI, or for frame structure type 2, - for NPDSCH not carrying the BCCH, define as the block of complex-valued symbols mapped to subframe number and radio frame number . Each complex-valued symbol shall be multiplied with before its transmission, with where the scrambling sequence is given by clause 7.2 and shall be initialized at the start of each subframe with . The mapping of is then repeated until subframes have been transmitted. For frame structure type 2, the resource elements in a special subframe that are not part of DwPTS are counted but not used in the repetition. When , the resource elements in a special subframe assumed by the UE for NRSs are counted but not used in the repetition. For NPDSCH carrying BCCH, the is mapped to subframes in sequence and then repeated until subframes have been transmitted, where - for mapping NPDSCH carrying SystemInformationBlockType1-NB to subframe #3 for frame structure type 1; - otherwise. The NPDSCH transmission can be configured by higher layers with transmission gaps where the NPDSCH transmission is postponed. There are no gaps in the NPDSCH transmission if where is given by the higher layer parameter dl-GapThreshold and is given by [4]. The gap starting frame and subframe is given by where the gap periodicity,, is given by the higher layer parameter dl-GapPeriodicity. The gap duration in number of subframes is given by , where is given by the higher layer parameter dl-GapDurationCoeff. For NPDSCH carrying the BCCH there are no gaps in the transmission. The UE shall not expect NPDSCH in subframe if it is not a NB-IoT downlink subframe, except for transmissions of NPDSCH carrying SystemInformationBlockType1-NB in - subframes 3 and 4 for frame structure type 1; and - subframes 0, 4, and 5 for frame structure type 2. In case of NPDSCH transmissions, in subframes that are not NB-IoT downlink subframes, the NPDSCH transmission is postponed until the next NB-IoT downlink subframe. If higher layer parameter resourceReservationConfigDL is configured, then in case of NPDSCH transmission associated with C-RNTI using UE-specific NPDCCH search space with the Resource reservation field in the DCI set to 1, - In a subframe that is fully reserved as defined in clause 16.4 in [4], the NPDSCH transmission is postponed until the next NB-IoT downlink subframe that is not fully reserved. - In a subframe that is partially reserved, the reserved OFDM symbols shall be counted in the NPDSCH mapping but not used for transmission of the NPDSCH. | 3GPP TS 36.211 | Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation | RAN1 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 10.2.3.4 |
4,478 | 5.3.13.5 Handling of failure to resume RRC Connection | The UE shall: 1> if timer T319 expires: 2> if the UE supports multiple CEF report: 3> if the UE has connection establishment failure information or connection resume failure information available in VarConnEstFailReport and if the RPLMN is equal to plmn-identity stored in VarConnEstFailReport; and 3> if the cell identity of current cell is not equal to the cell identity stored in measResultFailedCell in VarConnEstFailReport and if the maxCEFReport-r17 has not been reached: 4> append the VarConnEstFailReport as a new entry in the VarConnEstFailReportList; 2> if the UE has connection establishment failure information or connection resume failure information available in VarConnEstFailReport and if the RPLMN is not equal to plmn-identity stored in VarConnEstFailReport; or 2> if the cell identity of current cell is not equal to the cell identity stored in measResultFailedCell in VarConnEstFailReport: 3> reset the numberOfConnFail to 0; 2> if the UE has connection establishment failure information or connection resume failure information available in VarConnEstFailReportList and if the RPLMN is not equal to plmn-identity stored in any entry of VarConnEstFailReportList: 3> clear the content included in VarConnEstFailReportList; 2> clear the content included in VarConnEstFailReport except for the numberOfConnFail, if any; 2> store the following connection resume failure information in the VarConnEstFailReport by setting its fields as follows: 3> set the plmn-Identity to the PLMN selected by upper layers (see TS 24.501[ Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 ] [23]) from the PLMN(s) included in the plmn-IdentityInfoList in SIB1; 3> set the measResultFailedCell to include the global cell identity, tracking area code, the cell level and SS/PBCH block level RSRP, and RSRQ, and SS/PBCH block indexes, of the failed cell based on the available SSB measurements collected up to the moment the UE detected connection resume failure; 3> if available, set the measResultNeighCells, in order of decreasing ranking-criterion as used for cell re-selection, to include neighbouring cell measurements for at most the following number of neighbouring cells: 6 intra-frequency and 3 inter-frequency neighbours per frequency as well as 3 inter-RAT neighbours, per frequency/ set of frequencies per RAT and according to the following: 4> for each neighbour cell included, include the optional fields that are available; NOTE: The UE includes the latest results of the available measurements as used for cell reselection evaluation, which are performed in accordance with the performance requirements as specified in TS 38.133[ NR; Requirements for support of radio resource management ] [14]. 3> if available, set the locationInfo as in 5.3.3.7; 3> set perRAInfoList to indicate the performed random access procedure related information as specified in 5.7.10.5; 3> if numberOfConnFail is smaller than 8: 4> increment the numberOfConnFail by 1; 2> perform the actions upon going to RRC_IDLE as specified in 5.3.11 with release cause 'RRC Resume failure'. 1> else if upon receiving integrity check failure indication from lower layers while T319 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 indication from the MCG RLC that the maximum number of retransmissions has been reached is received while SDT procedure is ongoing; or 1> if random access problem indication is received from MCG MAC while SDT procedure is ongoing; or 1> if the lower layers indicate that cg-SDT-TimeAlignmentTimer or the configuredGrantTimer expired before receiving network response for the UL CG-SDT transmission with CCCH message while SDT procedure is ongoing; or 1> if integrity check failure indication is received from lower layers while SDT procedure is ongoing; or 1> if T319a expires: 2> consider SDT procedure is not ongoing; 2> perform the actions upon going to RRC_IDLE as specified in 5.3.11 with release cause 'RRC Resume failure'. The UE may discard the connection resume failure or connection establishment failure information, i.e. release the UE variable VarConnEstFailReport and the UE variable VarConnEstFailReportList, 48 hours after the last connection resume failure is detected. The L2 U2N Relay UE either indicates to upper layers (to trigger PC5 unicast link release) or sends NotificationMessageSidelink message to the connected L2 U2N Remote UE(s) in accordance with 5.8.9.10. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.3.13.5 |
4,479 | X.9 Authorization of selection of participant NWDAF instances in the Federated Learning group | The authorization for selecting participant NWDAF instances in the Federated Learning (FL) group uses token-based authorization as specified in clause 13.4.1, with the following additions. Figure X.9-1 depicts the authorization mechanism for NWDAF containing MTLF acting as FL Server to initiate the Federated Learning process on the NWDAF containing MTLF(s) acting as FL Client(s). The authorization is based upon the FL capability type (FL server or FL client) provided by the NWDAF containing MTLF acting as FL server during registration, and the Analytics ID and Interoperability Indicator per Analytics ID provided by the NWDAF containing MTLF acting as FL client during registration. Editor’s note: The use of Service area and Availability time requirement for authorization is FFS. Figure X.9-1: FL Authorization for selecting participant NWDAF instances Step 1a. The NWDAF containing MTLF acting as FL client registers to the NRF with its FL related information, including supported FL capability (FL client), Analytics ID(s) and Interoperability Indicator per Analytics ID as described in clause 5.2 of TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] . Step 1b. The NWDAF containing MTLF acting as FL server registers to the NRF with its FL capability (FL Server). Step 2. The NWDAF containing MTLF acting as FL server (NF Service Consumer) sends a discovery request to NRF and receives the available NWDAFs containing MTLF acting as FL client(s) (NF Service Producer) as a response, as specified in clause 6.2C.2.1 of TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [105]. Step 3. The NWDAF containing MTLF acting as FL server (NF Service Consumer) sends an access token request to the NRF as specified in clause 13.4.1. The access token request may contain the Analytics ID for the requested Federated Learning process. Step 4. The NRF authorizes the NWDAF containing MTLF acting as FL server (NF Consumer) based upon the information received in Step 1b, and after verifying that the Server NWDAF’s Vendor ID is included in the Interoperability Indicator for the requested Analytics ID provided in Step 1a. If the authorization succeeds, NRF generates the access token(s) as specified in clause 13.4.1. The access token claims may include the Analytics ID for the request Federated Learning process. NOTE: Fine-grained authorization can be done locally at the NWDAFs containing MTLF acting as FL client(s) (NF Service Producer). Step 5a, 5b. The NRF sends the access token to the NWDAF containing MTLF acting as FL Server, or rejects the request in case of failed authorization, as described in clause 13.4.1. Step 6. The NWDAF containing MTLF acting as FL server sends the service request to the NWDAF(s) containing MTLF acting as FL client with the access token received in Step 5a. along with the Analytics ID information for which the FL process is to be performed, as described in TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [105]. Step 7, 8. The NWDAF containing MTLF acting as FL client (NF Service Producer) verifies the received access token as specified in clause 13.4.1. In case of successful access token verification, the NWDAF containing MTLF acting as FL client sends a success response to the NWDAF containing MTLF acting as FL server, as described in TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [105]. Step 9. After a successful response from the NWDAF(s) containing MTLF acting as FL client, the NWDAF containing MTLF acting as FL server initiates the Federated Learning process as described in TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [105]. Authorization of the NWDAF containing MTLF acting as FL client is implicit, since it can join a Federated Learning group only when selected by the NWDAF containing MTLF acting as FL server. | 3GPP TS 33.501 | Security architecture and procedures for 5G System | SA WG3 | 3GPP Series : 33 , Security aspects | X.9 |
4,480 | 5.5.4.20 Event Y2 (Candidate L2 U2N Relay UE becomes better than threshold) | The UE shall: 1> consider the entering condition for this event to be satisfied when condition Y2-1, as specified below, is fulfilled; 1> consider the leaving condition for this event to be satisfied when condition Y2-2, as specified below, is fulfilled; Inequality Y2-1 (Entering condition) Mr– Hys > Thresh Inequality Y2-2 (Leaving condition) Mr + Hys < Thresh The variables in the formula are defined as follows: Mr 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). Thresh is the threshold parameter for this event (i.e. y2-Threshold-Relay as defined within reportConfigInterRAT for this event). Mr is expressed in dBm or dB, depending on the measurement quantity of candidate L2 U2N Relay UE. Hys are expressed in dB. Thresh is expressed in the same unit as Mr. | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 5.5.4.20 |
4,481 | – FeatureCombination | The IE FeatureCombination indicates a feature or a combination of features to be associated with a set of Random Access resources (i.e. an instance of FeatureCombinationPreambles). FeatureCombination information element -- ASN1START -- TAG-FEATURECOMBINATION-START FeatureCombination-r17 ::= SEQUENCE { redCap-r17 ENUMERATED {true} OPTIONAL, -- Need R smallData-r17 ENUMERATED {true} OPTIONAL, -- Need R nsag-r17 NSAG-List-r17 OPTIONAL, -- Need R msg3-Repetitions-r17 ENUMERATED {true} OPTIONAL, -- Need R msg1-Repetitions-r18 ENUMERATED {true} OPTIONAL, -- Need R eRedCap-r18 ENUMERATED {true} OPTIONAL, -- Need R spare2 ENUMERATED {true} OPTIONAL, -- Need R spare1 ENUMERATED {true} OPTIONAL -- Need R } NSAG-List-r17 ::= SEQUENCE (SIZE (1.. maxSliceInfo-r17)) OF NSAG-ID-r17 -- TAG-FEATURECOMBINATION-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
4,482 | 5.31.17 Inter-UE QoS for NB-IoT | To allow NG-RAN to prioritise resource allocation between different UEs accessing via NB-IoT when some of the UEs are using Control Plane CIoT 5GS Optimisation, NG-RAN may, based on configuration, retrieve from the AMF the subscribed NB-IoT UE Priority for any UE accessing via NB-IoT by using the UE's 5G-S-TMSI as the identifier. In order to reduce signalling load on the AMF, NG-RAN may be configured to request the NB-IoT UE Priority from the AMF e.g. only when the NG-RAN's NB-IoT load exceeds certain threshold(s) or when the NG-RAN needs to cache the QoS profile. | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.31.17 |
4,483 | 16.9.6.2 Unicast | For unicast, SL DRX is configured per pair of source L2 ID and destination L2 ID. The UE maintains a set of SL DRX timers for each direction per pair of source L2 ID and destination L2 ID. The SL DRX configuration for a pair of source/destination L2 IDs for a direction may be negotiated between the UEs in the AS layer. For SL DRX configuration of each direction, where one UE is the TX UE and the other is the RX UE: - RX UE may send assistance information, which includes its desired SL on-duration timer, SL DRX start offset, SL DRX slot offset, and SL DRX cycle, to the TX UE and the TX UE using mode 2 resource allocation may use it to determine the SL DRX configuration for the RX UE; - Regardless of whether assistance information is provided or not, the TX UE in RRC_IDLE/RRC_INACTIVE/OOC, or in RRC_CONNECTED and using mode 2 resource allocation, determines the SL DRX Configuration for the RX UE. For a TX UE in RRC_CONNECTED and using mode 1 resource allocation, the SL DRX configuration for the RX UE is determined by the serving gNB of the TX UE; - TX UE sends the SL DRX configuration to be used by the RX UE to the RX UE; - The RX UE may accept or reject the SL DRX configuration. When the TX UE is in RRC_CONNECTED and using mode 1 resource allocation, the TX UE may report the received assistance information or the received SL DRX configuration reject information to its serving gNB supporting SL DRX and sends the SL DRX configuration to the RX UE upon receiving the SL DRX configuration in dedicated RRC signalling from the gNB. When the RX UE is in RRC_CONNECTED and using mode 1 resource allocation, the RX UE can report the received SL DRX configuration to its serving gNB supporting SL DRX, e.g. for alignment of the Uu and SL DRX configurations. SL on-duration timer, SL inactivity-timer, SL HARQ RTT timer, and SL HARQ retransmission timer are supported in unicast. SL HARQ RTT timer and SL HARQ retransmission timer are maintained per SL process at the RX UE. In addition to (pre)configured values for each of these timers, SL HARQ RTT timer value can be derived from the retransmission resource timing when SCI indicates more than one transmission resource. SL HARQ RTT timer can be set to different values to support both HARQ enabled and HARQ disabled transmissions. SL DRX MAC CE is introduced for SL DRX operation in unicast only. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.9.6.2 |
4,484 | 17.5.7.1 BM-SC Initiated Multicast Service Deactivation | This section defines the BM-SC initiated Multicast Service Deactivation procedure. Figure 32a: BM-SC initiated MBMS Service deactivation procedure 1. The BM-SC sends an ASR to the GGSN, indicating that the UE shall be removed from the multicast service. The session to be terminated is uniquely identified by the Diameter session-id. 2. Upon reception of the ASR, the GGSN sends an ASA to the BM-SC 3. Upon reception of the ASR the GGSN sends an MBMS UE Context Deactivation Request to the SGSN. The IP multicast address, APN and IMSI together identify the MBMS UE Context to be deleted by the SGSN. Steps from 5 to 9 of figure 32 in section 17.5.7 follow. | 3GPP TS 29.061 | Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN) | CT WG3 | 3GPP Series : 29 , Signalling protocols ("stage 3") - intra-fixed-network | 17.5.7.1 |
4,485 | 4.2.2.5 Number of E-RAB failed to release | a) This measurement provides the number of E-RAB failed to release. The measurement is split into subcounters per failure cause. b) CC c) On transmission by the eNodeB/RN of an E-RAB RELEASE RESPONSE message, each E-RAB failed to release is added to the relevant measurement per cause, the possible causes are included in TS 36.413[ Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1 Application Protocol (S1AP) ] [9]. The sum of all supported per cause measurements shall equal the total number of E-RABs failed to release. In case only a subset of per cause measurements is supported, a sum subcounter will be provided first. d) Each measurement is an integer value. The number of measurements is equal to the number of causes plus a possible sum value identified by the .sum suffix. e) The measurement name has the form ERAB.RelFailNbr.Cause where Cause identifies the cause resulting in the E-RAB release failure. f) EUtranCellFDD EUtranCellTDD g) Valid for packet switched traffic h) EPS i) One usage of this measurement is to support the coverage ratio (CR) calculation for EE coverage area determination in [21]. | 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.2.2.5 |
4,486 | 12.7.3 Group ID for Network Selection (GIN) | The "Group ID for Network Selection" (GIN) identifies a group (e.g. a consortium) of Credential Holders or Default Credential Servers (see 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [119], clause 5.30.2) that can be used to authenticate and authorize the access to an SNPN; the GIN is used during SNPN selection by the UE to enhance the likelihood of selecting a preferred SNPN. The GIN has the same structure as the SNPN identifier (see clause 12.7.1) and shall consist of MCC, MNC and NID, where the NID contains 44 bits, i.e. 11 hexadecimal digits; one digit (4 bits) for representing an assignment mode and 10 digits (40 bits) for a NID value, as shown in figure 12.7.1-1. The GIN can be assigned using the following assignment models: a) Self-assignment: GINs are chosen individually and may therefore not be unique; this assignment model is encoded by setting the assignment mode to value 1. b) Coordinated assignment: GINs are assigned using one of the following two options: - option 1: the GIN is assigned such that the NID is globally unique independent of the PLMN ID used. Option 1 of this assignment model is encoded by setting the assignment mode to value 0. - option 2: the GIN is assigned such that the combination of the NID and the PLMN ID is globally unique. Option 2 of this assignment model is encoded by setting the assignment mode to value 2. Other Assignment mode values are spare, for future use. | 3GPP TS 23.003 | Numbering, addressing and identification | CT WG4 | 3GPP Series : 23 , Technical realization ("stage 2") | 12.7.3 |
4,487 | 4.9.5 Network-controlled repeater management | Network-Controlled Repeater identification is performed in RAN, and Network-Control Repeater authorization is performed in 5GC. The general procedure of the Network-Controlled Repeater management is illustrated in Figure 4.9.5-1: Figure 4.9.5-1: Network-Controlled Repeater management. The gNB broadcasts the Network-Controlled Repeater supported information via system information. When a Network-Controlled Repeater is trying to access the network as a Network-Controlled Repeater, the Network-Controlled Repeater indication is sent to the serving gNB. The serving gNB selects an appropriate AMF for the Network-Controlled Repeater. AMF provides Network-Controlled Repeater authorization information to the gNB. Other steps refer to the signalling flow as defined in 9.2.1.3. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 4.9.5 |
4,488 | 16.1.2 LCP Restrictions | With LCP restrictions in MAC, RRC can restrict the mapping of a logical channel to a subset of the configured cells, numerologies, PUSCH transmission durations, configured grant configurations and control whether a logical channel can utilise the resources allocated by a Type 1 Configured Grant (see clause 10.3) or whether a logical channel can utilise dynamic grants indicating a certain physical priority level. With such restrictions, it then becomes possible to reserve, for instance, the numerology with the largest subcarrier spacing and/or shortest PUSCH transmission duration for URLLC services. Furthermore, RRC can associate logical channels with different SR configurations, for instance, to provide more frequent SR opportunities to URLLC services. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 16.1.2 |
4,489 | 8.6.2 RRC inactive to other states | This clause gives the RRC inactive to other RRC states transition given that gNB consists of gNB-CU and gNB-DU(s), as shown in Figure 8.6.2-1. Figure 8.6.2-1: RRC inactive to other RRC states transition procedure 1. If data is received from 5GC, the gNB-CU sends PAGING message to the gNB-DU. 2. The gNB-DU sends Paging message to UE. NOTE: Step 1 and 2 only exist in case of DL data arrival. 3. The UE sends RRCResumeRequest message either upon RAN-based paging, UL data arrival or RNA update. 4. The gNB-DU includes RRCResumeRequest in a non-UE associated INITIAL UL RRC MESSAGE TRANSFER message and transfer to the gNB-CU. 5. For UE Inactive to UE Active transitions, excluding transitions due to signalling exchange only, the gNB-CU allocates gNB-CU UE F1AP ID and sends UE CONTEXT SETUP REQUEST message to gNB-DU, which may include SRB ID(s) and DRB ID(s) to be setup, CellGroupConfig stored in gNB-CU or retrieved from the old NG-RAN node may also be included. In case of NG-RAN sharing, the gNB-CU includes the serving PLMN ID (in case of SNPNs the serving NID). 6. The gNB-DU responds with UE CONTEXT SETUP RESPONSE message, which contains RLC/MAC/PHY configuration of SRB and DRBs provided by the gNB-DU. NOTE: Step 5 and step 6 exist for inactive to active transitions, excluding transitions due to signalling exchange only. When gNB-CU successfully retrieves and verifies the UE context, it may decide to let the UE enter into RRC active mode. gNB-CU shall trigger UE context setup procedure between gNB-CU and gNB-DU, during which both SRB1, SRB2 and DRB(s) can be setup. For signalling exchange only transitions, gNB-CU does not trigger UE Context Setup procedure. For inactive to Idle transitions the gNB-CU does not trigger the UE Context Setup procedure. 7. The gNB-CU generates RRCResume/RRCSetup/RRCReject/RRCRelease message or receives RRCRelease message from the old NG-RAN node towards the UE. The RRC message is encapsulated in DL RRC MESSAGE TRANSFER message together with SRB ID. 8. The gNB-DU forwards RRC message to the UE either over SRB0 or SRB1 as indicated by the SRB ID. NOTE: In step 7, it is expected that gNB-CU takes appropriate action, e.g. generates RRC resume message for inactive to active state transition(for both cases of signaling exchange only, and UP data exchange), generates RRCSetup message for fallback to establish a new RRC connection, and generates or receives from the old NG-RAN node either RRCRelease message without suspend configuration for inactive to idle state transition, or RRCRelease message with suspend configuration to remain in inactive state. If step 5 and 6 are not performed, the gNB-DU deduces the SRB on which to deliver the RRC message in step 7 from the SRB ID, i.e. SRB ID “0” corresponds to SRB0, SRB ID “1” corresponds to SRB1. 9. The UE sends RRCResumeComplete/RRCSetupComplete message to the gNB-DU. 10. The gNB-DU encapsulates RRC in UL RRC MESSAGE TRANSFER message and send to the gNB-CU. NOTE: Step 9 and step 10 exist for inactive to active state transition (for both cases of signaling exchange only, and UP data exchange). UE generates RRCResumeComplete/RRCSetupComplete message for resume the existing RRC connection or fallback to a new RRC connection respectively. | 3GPP TS 38.401 | NG-RAN; Architecture description | RAN3 | 3GPP Series : 38 , Radio technology beyond LTE | 8.6.2 |
4,490 | 9.9.3.19 KSI and sequence number | The purpose of the KSI and sequence number information element is to provide the network with the key set identifier (KSI) value of the current EPS security context and the 5 least significant bits of the NAS COUNT value applicable for the message including this information element. The KSI and sequence number information element is coded as shown in figure 9.9.3.19.1 and table 9.9.3.19.1. The KSI and sequence number is a type 3 information element with a length of 2 octets. Figure 9.9.3.19.1: KSI and sequence number information element Table 9.9.3.19.1: KSI and sequence number information element | 3GPP TS 24.301 | Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 9.9.3.19 |
4,491 | 6.8.1 Authentication and key agreement of UMTS subscribers 6.8.1.1 General | For UMTS subscribers, authentication and key agreement will be performed as follows: - UMTS AKA shall be applied when the user is attached to a UTRAN. - UMTS AKA shall be applied when the user is attached to a GSM BSS, in case the user has a ME capable of UMTS AKA and also the VLR/SGSN is R99+. In this case, the 64-bit GSM cipher key Kc is derived from the UMTS cipher/integrity keys CK and IK, by the VLR/SGSN on the network side and by the USIM on the user side.The 128-bit GSM cipher key Kc128 is derived from the UMTS cipher/integrity keys CK and IK, by the VLR/SGSN on the network side and by the ME on the user side if needed to support 128-bit ciphering algorithms in GSM as described in subclause 6.3.3 of this specification. - GSM AKA shall be applied when the user is attached to a GSM BSS, in case the user has a ME not capable of UMTS AKA. In this case, the GSM user response SRES and the 64-bit GSM cipher key Kc are derived from the UMTS user response RES and the UMTS cipher/integrity keys CK and IK. A R98- VLR/SGSN uses the stored Kc and RES and a R99+ VLR/SGSN derives the SRES from RES and Kc from CK, IK. NOTE: To operate within a ME not capable of UMTS AKA, the USIM may support the SIM-ME interface as defined in GSM 11.11, and support GSM AKA which provides the corresponding GSM functionality for calculating SRES and Kc based on the authentication key K and the 3G authentication algorithm implemented in the USIM. Due to the fact that the UMTS authentication algorithm only computes CK/IK and RES, conversion of CK/IK to Kc shall be achieved by using the conversion function c3, and conversion of RES to SRES by c2. - GSM AKA shall be applied when the user is attached to a GSM BSS, in case the VLR/SGSN is R98-. In this case, the USIM derives the GSM user response SRES and the GSM cipher key Kc from the UMTS user response RES and the UMTS cipher/integrity keys CK, IK. The execution of the UMTS (resp. GSM) AKA results in the establishment of a UMTS (resp. GSM) security context between the user and the serving network domain to which the VLR/SGSN belongs. The user needs to separately establish a security context with each serving network domain. Figure 18 shows the different scenarios that can occur with UMTS subscribers in a mixed network architecture. Figure 18: Authentication and key agreement of UMTS subscribers Note that the UMTS parameters RAND, AUTN and RES are sent transparently through the UTRAN or GSM BSS and that the GSM parameters RAND and SRES are sent transparently through the GSM BSS. In case of a GSM BSS, ciphering is applied in the GSM BSS for services delivered via the MSC/VLR, and by the SGSN for services delivered via the SGSN. In the latter case the GSM cipher keys Kc or Kc128 are not sent to the GSM BSS. In case of a UTRAN, ciphering and integrity are always applied in the RNC, and the UMTS cipher/integrity keys CK an IK are always sent to the RNC. | 3GPP TS 33.102 | 3G security; Security architecture | SA WG3 | 3GPP Series : 33 , Security aspects | 6.8.1 |
4,492 | 9.4 Roaming and Access Restrictions | The roaming and access restriction information for a UE includes information on restrictions to be applied for subsequent mobility action during CM-CONNECTED state. It may be provided by the AMF and also may be updated by the AMF later. It includes the forbidden RAT, the forbidden area and the service area restrictions as specified in TS 23.501[ System architecture for the 5G System (5GS) ] [3]. It also includes serving PLMN/SNPN and may include a list of equivalent PLMNs or a list of equivalent SNPNs. It may also include PNI-NPN mobility restrictions (i.e. list of CAGs allowed for the UE and whether the UE can also access non-CAG cells). The gNB shall consider that roaming or access to CAG cells is only allowed if PNI-NPN mobility information is available for the UE. Upon receiving the roaming and access restriction information for a UE, if applicable, the gNB should use it to determine whether to apply restriction handling for subsequent mobility action, e.g., handover, redirection. If the roaming and access restriction information is not available for a UE at the gNB, the gNB shall consider that there is no restriction for subsequent mobility actions except for the PNI-NPN mobility as described in TS 23.501[ System architecture for the 5G System (5GS) ] [3]. Only if received over NG or Xn signalling, the roaming and access restriction information shall be propagated over Xn by the source gNB during Xn handover. If the Xn handover results in a change of serving PLMN (to an equivalent PLMN), the source gNB shall replace the serving PLMN with the identity of the target PLMN and move the serving PLMN to the equivalent PLMN list, before propagating the roaming and access restriction information. If the Xn handover results in a change of serving SNPN (to an equivalent SNPN), the source gNB shall replace the serving SNPN with the identity of the target SNPN and move the serving SNPN to the equivalent SNPN list, before propagating the roaming and access restriction information. If NG-RAN nodes with different versions of the XnAP or NGAP protocol are deployed, information provided by the 5GC within the NGAP Mobility Restriction List may be lost in the course of Xn mobility. In order to avoid such loss of information at Xn handover or UE context retrieval due to a source NG-RAN node or an old NG-RAN node not able to recognise the entire content, the source NG-RAN node or the old NG-RAN node may provide an 5GC Mobility Restriction List Container to the target NG-RAN node or the new NG-RAN node, containing the Mobility Restriction List as received from the 5GC. The target NG-RAN node or the new NG-RAN node shall use the information contained in the 5GC Mobility Restriction List Container as the Mobility Restriction List, except for the Serving PLMN/SNPN and the Equivalent PLMNs/SNPNs, which the NG-RAN node shall use from the XnAP Mobility Restriction List. The 5GC Mobility Restriction List Container may be propagated at future Xn handover and UE context retrieval. | 3GPP TS 38.300 | NR; NR and NG-RAN Overall description; Stage-2 | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | 9.4 |
4,493 | – NRDC-Parameters | The IE NRDC-Parameters contains parameters specific to NR-DC, i.e., which are not applicable to NR SA. NRDC-Parameters information element -- ASN1START -- TAG-NRDC-PARAMETERS-START NRDC-Parameters ::= SEQUENCE { measAndMobParametersNRDC MeasAndMobParametersMRDC OPTIONAL, generalParametersNRDC GeneralParametersMRDC-XDD-Diff OPTIONAL, fdd-Add-UE-NRDC-Capabilities UE-MRDC-CapabilityAddXDD-Mode OPTIONAL, tdd-Add-UE-NRDC-Capabilities UE-MRDC-CapabilityAddXDD-Mode OPTIONAL, fr1-Add-UE-NRDC-Capabilities UE-MRDC-CapabilityAddFRX-Mode OPTIONAL, fr2-Add-UE-NRDC-Capabilities UE-MRDC-CapabilityAddFRX-Mode OPTIONAL, dummy2 OCTET STRING OPTIONAL, dummy SEQUENCE {} OPTIONAL } NRDC-Parameters-v1570 ::= SEQUENCE { sfn-SyncNRDC ENUMERATED {supported} OPTIONAL } NRDC-Parameters-v15c0 ::= SEQUENCE { pdcp-DuplicationSplitSRB ENUMERATED {supported} OPTIONAL, pdcp-DuplicationSplitDRB ENUMERATED {supported} OPTIONAL } NRDC-Parameters-v1610 ::= SEQUENCE { measAndMobParametersNRDC-v1610 MeasAndMobParametersMRDC-v1610 OPTIONAL } NRDC-Parameters-v1700 ::= SEQUENCE { f1c-OverNR-RRC-r17 ENUMERATED {supported} OPTIONAL, measAndMobParametersNRDC-v1700 MeasAndMobParametersMRDC-v1700 } -- TAG-NRDC-PARAMETERS-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
4,494 | 8.13.3.7.2 Minimum Requirement for TDD PCell | The purpose of these tests is to verify the closed loop rank-four performance with wideband precoding with 4Tx and 4Rx under CA. For TDD FDD CA with TDD PCell and 2DL CCs, the requirements are specified in Table 8.13.3.7.2-4 based on single carrier requirement specified in Table 8.13.3.7.2-2 and Table 8.13.3.7.2-3, with the addition of the parameters in Table 8.13.3.7.2-1 and the downlink physical channel setup according to Annex C.3.2. The test coverage for different number of component carriers is defined in 8.1.2.4. Table 8.13.3.7.2-1: Test Parameters for Multi-Layer Spatial Multiplexing (FRC) for CA Table 8.13.3.7.2-2: Single carrier performance with different bandwidths for multiple CA configurations for FDD SCell (FRC) Table 8.13.3.7.2-3: Single carrier performance with different bandwidths for multiple CA configurations for TDD PCell and SCell (FRC) Table 8.13.3.7.2-4: Minimum performance for multiple CA configurations with 2DL CCs (FRC) | 3GPP TS 36.101 | Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment (UE) radio transmission and reception | RAN4 | 3GPP Series : 36 , LTE (Evolved UTRA), LTE-Advanced, LTE-Advanced Pro radio technology | 8.13.3.7.2 |
4,495 | 5.3.3.0 Triggers for tracking area update | A stand-alone tracking area update (with or without S-GW change, described in clauses 5.3.3.1 and 5.3.3.2 respectively) occurs when a GPRS-attached or E-UTRAN-attached UE experiences any of the following conditions: - UE detects it has entered a new TA that is not in the list of TAIs that the UE registered with the network (except for the case of a UE configured to perform Attach with IMSI when entering a TA in a new non-equivalent PLMN in RRC-IDLE mode); - the periodic TA update timer has expired; - UE was in UTRAN PMM_Connected state (e.g. URA_PCH) when it reselects to E-UTRAN; - UE was in GPRS READY state when it reselects to E-UTRAN; - the TIN indicates "P-TMSI" when the UE reselects to E-UTRAN (e.g. due to bearer configuration modifications performed on GERAN/UTRAN); - the RRC connection was released with release cause "load re-balancing TAU required"; - the RRC layer in the UE informs the UE's NAS layer that an RRC connection failure (in either E-UTRAN or UTRAN) has occurred; - a change of the UE Network Capability and/or MS Network Capability and/or UE Specific DRX Parameters and/or TS 24.008[ Mobile radio interface Layer 3 specification; Core network protocols; Stage 3 ] [47] MS Radio Access capability (e.g. due to GERAN radio capability change, E-UTRAN, NG-RAN capability change or cdma2000 Radio Access Technology Capability change) information of the UE. - for UE supporting RACS in ECM-IDLE as defined in clause 5.11.3a, a change in UE Radio Access capability (e.g. due to GERAN radio capability change, E-UTRAN, NG-RAN capability change or cdma2000 Radio Access Technology Capability change) corresponding to signalling a different UE Radio Capability ID. - at every change between a cell that does not broadcast SystemInformationBlockType31(-NB) and an E-UTRA cell that broadcasts SystemInformationBlockType31(-NB). - a change in conditions in the UE require a change in the extended idle mode DRX parameters previously provided by the MME. - for a UE supporting CS fallback, or configured to support IMS voice, or both, a change of the UE's usage setting or voice domain preference for E-UTRAN. - for a SR-VCC capable UE, a change of MS Classmark 2 and/or MS Classmark 3 and/or Supported Codecs. - UE manually selects a CSG cell whose CSG ID and associated PLMN is absent from both the UE's Allowed CSG list and the UE's Operator CSG list. - UE receives a paging request from the MME while the Mobility Management back off timer is running and the UE's TIN indicates "P-TMSI". - a change in any of the values of information included in Preferred Network Behaviour as defined in clause 4.3.5.10 that would create incompatibility with the Supported Network Behaviour provided by the serving MME. - with satellite access for Cellular IoT upon changing to a suitable cell indicating one or more TACs for the RPLMN all of which are outside the UE's Tracking Area List in both ECM-CONNECTED and ECM-IDLE. - a UE that is using a RAN that provides discontinuous coverage (e.g. for satellite access with discontinuous coverage) is about to leave the satellite network coverage as described in clause 4.13.8.2. - when the UE has informed the network that it is unreachable and now returns to coverage using either satellite or terrestrial access as described in clause 4.13.8.2. NOTE 1: The complete list of TAU triggers is specified in TS 24.301[ Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS); Stage 3 ] [46]. NOTE 2: With satellite access for Cellular IoT, more than one TAC can be indicated to a UE for each PLMN in any cell, see clause 4.13.6. The procedure is initiated by an UE in either ECM-IDLE state or ECM-CONNECTED state. The decision to perform S-GW change during the tracking area update procedure is made by the MME independently from the triggers above. If SIPTO is allowed for the APN associated with a PDN connection, the MME should re-evaluate whether the PDN GW location is still acceptable. If the MME determines that PDN GW re-location is needed, the MME may initiate PDN deactivation with reactivation requested according to clause 5.10.3 at the end of the tracking area/routing area update procedure. NOTE 3: It depends on the operator's configuration in the MME whether to use the deactivation with reactivation request or allow the continued usage of the already connected GW. If SIPTO at the local network is allowed for the APN associated with a PDN connection the MME handles the SIPTO at the Local Network PDN connection as follows. For a L-GW collocated with (H)eNB: - For intra-MME mobility, upon completion of the TAU procedure the MME shall deactivate the SIPTO at the local Network PDN connection with the "reactivation requested" cause value according to clause 5.10.3. If the UE has no other PDN connection, the MME initiates "explicit detach with reattach required" procedure according to clause 5.3.8.3. - For Inter-MME/SGSN mobility, as part of the Tracking Area Update procedure, the source MME shall remove the bearer(s) corresponding to the SIPTO at Local Network PDN connection and shall release the core network resources associated to the SIPTO at the Local Network PDN connection by performing the MME-initiated PDN Connection Deactivation before sending the Context Response message. For a stand-alone GW: - For intra-MME mobility, upon completion of the TAU procedure the MME checks that the Local Home Network ID has changed and decides whether to deactivate the SIPTO at the local Network PDN connection with the "reactivation requested" cause value according to clause 5.10.3. If the UE has no other PDN connection, the MME initiates "explicit detach with reattach required" procedure according to clause 5.3.8.3. - For Inter-MME/SGSN mobility, upon completion of the TAU/RAU procedure the new MME/SGSN checks that the Local Home Network ID has changed and decides whether to deactivate the SIPTO at the Local Network PDN connection with the "reactivation requested" cause value according to clause 5.10.3. If the UE has no other PDN connection, the MME initiates "explicit detach with reattach required" procedure according to clause 5.3.8.3. If LIPA is active for a PDN connection of the UE, the source MME (or S4-SGSN) shall not include LIPA bearer(s) in the EPS bearer Context during Tracking Area Update procedure and shall release the core network resources of this LIPA PDN connection by performing the MME requested PDN disconnection procedure according to steps 2 to 6 of clause 5.10.3 before it responds with the Context Response message in the case of inter-MME/SGSN mobility or after it receives Tracking Area Update Request in the case of intra-MME mobility. NOTE 4: The source MME may not be able to release the LIPA PDN connection after the Context Response is sent as when there is no S-GW relocation, the S-GW will assign the S11 control tunnel of the UE to the new MME after the new MME updates the context information. During the Tracking Area Update procedure, if the MME supports SRVCC and if the UE SRVCC capability has changed, the MME informs the HSS with the UE SRVCC capability e.g. for further IMS registration. The cell selection for UTRAN is described in TS 25.304[ None ] [12] and TS 25.331[ None ] [33]. If during the Tracking Area Update procedure the MME detects that the Serving GW or/and the MME needs be relocated, the old MME may reject any PDN GW initiated EPS bearer(s) request received since the Tracking Area Update procedure started and if rejected, the old MME shall include an indication that the request has been temporarily rejected due to mobility procedure in progress. The rejection is forwarded by the Serving GW to the PDN GW, with the indication that the request has been temporarily rejected. In the case of satellite access for Cellular IoT, upon receiving the TAU Request message, the MME may verify the UE location and determine whether the PLMN is allowed to operate at the UE location, as described in clause 4.13.4. If the UE receives a TAU Reject message with cause value indicating that the selected PLMN is not allowed to operate at the present UE location, the UE shall attempt to select a PLMN as specified in TS 23.122[ Non-Access-Stratum (NAS) functions related to Mobile Station (MS) in idle mode ] [10]. Upon reception of a rejection for an EPS bearer(s) PDN GW initiated procedure with an indication that the request has been temporarily rejected due to mobility procedure in progress, the PDN GW start a locally configured guard timer. The PDN GW shall re-attempt, up to a pre-configured number of times, when either it detects that the Tracking Area Update procedure is completed or has failed using message reception or at expiry of the guard timer. A Multi-USIM UE may trigger a TAU to send a Requested IMSI Offset in order to derive an alternative IMSI as defined in clause 4.3.33. NOTE 5: As an exception, during a TAU procedure due to mobility to a new Tracking Area outside the Tracking Area List and detecting paging collision at the same time, a Multi-USIM UE implementation can decide to indicate to the MME a Requested IMSI Offset even if it does not know whether the MME serving the new Tracking Area supports it. | 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.3.0 |
4,496 | 4.16 UE radio capability signalling optimisation | UE radio capability signalling optimisation (RACS) is a feature that is optional at both the UE and the network and which aims to optimise the transmission of UE radio capability over the radio interface (see 3GPP TS 23.501[ System architecture for the 5G System (5GS) ] [8]). RACS works by assigning an identifier to represent a set of UE radio capabilities. This identifier is called the UE radio capability ID. A UE radio capability ID can be either manufacturer-assigned or network-assigned. The UE radio capability ID is an alternative to the signalling of the radio capabilities container over the radio interface. In this release of the specification, RACS is applicable to neither NB-N1 mode nor non-3GPP access. If the UE supports RACS: a) the UE shall indicate support for RACS by setting the RACS bit to "RACS supported" in the 5GMM capability IE of the REGISTRATION REQUEST message; b) if the UE performs a registration procedure for initial registration and the UE has an applicable UE radio capability ID for the current UE radio configuration in the selected network, the UE shall include the UE radio capability ID in the UE radio capability ID IE as a non-cleartext IE in the REGISTRATION REQUEST message. If both a network-assigned UE radio capability ID and a manufacturer-assigned UE Radio Capability ID are applicable, the UE shall include the network-assigned UE radio capability ID in the REGISTRATION REQUEST message; c) if the radio configuration at the UE changes (for instance because the UE has disabled a specific radio capability) then: 1) if the UE has an applicable UE radio capability ID for the new UE radio configuration, the UE shall initiate a registration procedure for mobility and periodic registration update. The UE shall include the applicable UE radio capability ID in the UE radio capability ID IE of the REGISTRATION REQUEST message and shall include the 5GS update type IE in the REGISTRATION REQUEST message with the NG-RAN-RCU bit set to "UE radio capability update needed". If both a network-assigned UE radio capability ID and a manufacturer-assigned UE Radio Capability ID are applicable, the UE shall include the network-assigned UE radio capability ID in the REGISTRATION REQUEST message; and 2) if the UE does not have an applicable UE radio capability ID for the new UE radio configuration, the UE shall initiate a registration procedure for mobility and periodic registration update and include the 5GS update type IE in the REGISTRATION REQUEST message with the NG-RAN-RCU bit set to "UE radio capability update needed"; NOTE: Performing the registration procedure for mobility and periodic registration update and including the 5GS update type IE in the REGISTRATION REQUEST message with the NG-RAN-RCU bit set to "UE radio capability update needed" without a UE radio capability ID included in the REGISTRATION REQUEST message can trigger the network to assign a new UE radio capability ID to the UE. d) upon receiving a network-assigned UE radio capability ID in the REGISTRATION ACCEPT message or the CONFIGURATION UPDATE COMMAND message, the UE shall store the network-assigned UE radio capability ID and the PLMN ID or SNPN identity of the serving network 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 along with a mapping to the current UE radio configuration in its non-volatile memory as specified in annex C. The UE shall be able to store at least the last 16 received network-assigned UE radio capability IDs with the associated PLMN ID 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 and the mapping to the corresponding UE radio configuration; e) the UE shall not use a network-assigned UE radio capability ID assigned by a PLMN in PLMNs equivalent to the PLMN which assigned it or by an SNPN in SNPNs equivalent to the SNPN which assigned it; f) upon receiving a UE radio capability ID deletion indication IE set to "Network-assigned UE radio capability IDs deletion requested" in the REGISTRATION ACCEPT message or the CONFIGURATION UPDATE COMMAND message, the UE shall delete all network-assigned UE radio capability IDs stored at the UE for the serving network, initiate a registration procedure for mobility and periodic registration update and include an applicable manufacturer-assigned UE radio capability ID for the current UE radio configuration, if available at the UE, in the UE radio capability ID IE of the REGISTRATION REQUEST message; and g) if the UE performs a registration procedure for mobility and periodic registration update due to entering a tracking area that is not in the list of tracking areas that the UE previously registered in the AMF and the UE has an applicable UE radio capability ID for the current UE radio configuration in the selected network, the UE shall include the UE radio capability ID in the UE radio capability ID IE as a non-cleartext IE in the REGISTRATION REQUEST message. If both a network-assigned UE radio capability ID and a manufacturer-assigned UE Radio Capability ID are applicable, the UE shall include the network-assigned UE radio capability ID in the REGISTRATION REQUEST message. If the network supports RACS: a) the network may assign a network-assigned UE radio capability ID to a UE which supports RACS by including a UE radio capability ID IE in the REGISTRATION ACCEPT message or in the CONFIGURATION UPDATE COMMAND message; b) the network may trigger the UE to delete all network-assigned UE radio capability IDs stored at the UE for the serving network by including a UE radio capability ID deletion indication IE set to "Network-assigned UE radio capability IDs deletion requested" in the REGISTRATION ACCEPT message or in the CONFIGURATION UPDATE COMMAND message; and c) the network may send an IDENTITY REQUEST message to the UE that supports RACS to retrieve the PEI, if not available in the network. | 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.16 |
4,497 | – TCI-State | The IE TCI-State associates one or two DL reference signals with a corresponding quasi-colocation (QCL) type. TCI-State information element -- ASN1START -- TAG-TCI-STATE-START TCI-State ::= SEQUENCE { tci-StateId TCI-StateId, qcl-Type1 QCL-Info, qcl-Type2 QCL-Info OPTIONAL, -- Need R ..., [[ additionalPCI-r17 AdditionalPCIIndex-r17 OPTIONAL, -- Need R pathlossReferenceRS-Id-r17 PathlossReferenceRS-Id-r17 OPTIONAL, -- Cond JointTCI1 ul-powerControl-r17 Uplink-powerControlId-r17 OPTIONAL -- Cond JointTCI ]], [[ tag-Id-ptr-r18 ENUMERATED {n0,n1} OPTIONAL -- Cond 2TA ]] } QCL-Info ::= SEQUENCE { cell ServCellIndex OPTIONAL, -- Need R bwp-Id BWP-Id OPTIONAL, -- Cond CSI-RS-Indicated referenceSignal CHOICE { csi-rs NZP-CSI-RS-ResourceId, ssb SSB-Index }, qcl-Type ENUMERATED {typeA, typeB, typeC, typeD}, ... } -- TAG-TCI-STATE-STOP -- ASN1STOP | 3GPP TS 38.331 | NR; Radio Resource Control (RRC); Protocol specification | RAN2 | 3GPP Series : 38 , Radio technology beyond LTE | – |
4,498 | 5.6.5 Support for Local Area Data Network | The access to a DN via a PDU Session for a LADN is only available in a specific LADN service area. A LADN service area is a set of Tracking Areas. LADN is a service provided by the serving PLMN or the serving SNPN. It includes: - LADN service applies only to 3GPP accesses and does not apply in Home Routed case. - The usage of LADN DNN requires an explicit subscription to this DNN or subscription to a wildcard DNN. - Whether a DNN corresponds to a LADN service is an attribute of a DNN and is per PLMN or per SNPN. The UE is configured to know whether a DNN is a LADN DNN on a per-PLMN or per SNPN basis, and an association between application and LADN DNN. The configured association is considered to be a UE local configuration defined in TS 23.503[ Policy and charging control framework for the 5G System (5GS); Stage 2 ] [45]. Alternatively, the UE gets the information whether a DNN is a LADN DNN from LADN Information during (re-)registration procedure as described in this clause. NOTE 1: No other procedure for configuring the UE to know whether a DNN is a LADN DNN is defined in this release of the specifications. NOTE 2: The procedure for configuring the UE to know an association between application and LADN DNN is not defined in this release of the specifications. LADN service area and LADN DNN are configured in the AMF on a per DN basis, i.e. for different UEs accessing the same LADN, the configured LADN service area is the same regardless of other factors (e.g. UE's Registration Area or UE subscription). NOTE 3: If a LADN is not available in any TA of an AMF's service area, the AMF is not required to be configured with any LADN related information for that DNN. LADN Information (i.e. LADN Service Area Information and LADN DNN) is provided by AMF to the UE during the Registration procedure or UE Configuration Update procedure. For each LADN DNN configured in the AMF, the corresponding LADN Service Area Information includes a set of Tracking Areas that belong to the Registration Area that the AMF assigns to the UE (i.e. the intersection of the LADN service area and the assigned Registration Area). The AMF shall not create Registration Area based on the availability of LADNs. NOTE 4: It is thus possible that the LADN Service Area Information sent by the AMF to the UE contains only a sub-set of the full LADN service area as the LADN service area can contain TA(s) outside of the registration area of the UE or outside of the area served by the AMF. When the UE performs a successful (re-)registration procedure, the AMF may provide to the UE, based on local configuration (e.g. via OAM) about LADN, on UE location, and on UE subscription information received from the UDM about subscribed DNN(s), the LADN Information for the list of LADN available to the UE in that Registration Area in the Registration Accept message. The UE may provide either the LADN DNN(s) to retrieve the LADN Information for the indicated LADN DNN(s) or an indication of Requesting LADN Information to retrieve the LADN Information for all LADN(s) available in the current Registration Area. The list of LADN is determined as follows: - If neither LADN DNN nor an indication of requesting LADN Information is provided in the Registration Request message, the list of LADN is the LADN DNN(s) in subscribed DNN list except for wildcard DNN. - If the UE provides LADN DNN(s) in the Registration Request message, the list of LADN is LADN DNN(s) the UE requested if the UE subscribed DNN(s) includes the requested LADN DNN or if a wildcard DNN is included in the UE's subscription data. NOTE 5: It is assumed that an application can use only one LADN DNN at a time. - If the UE provides an indication of requesting LADN Information in the Registration Request message, the list of LADN is all the LADN DNN(s) configured in the AMF if the wildcard DNN is subscribed, or the LADN DNN(s) which is in subscribed DNN list and no wildcard DNN is subscribed. The UE considers the retrieved LADN Information valid only for the registered PLMN and the E-PLMN(s) if the LADN Service Area Information includes Tracking Areas that belong to E-PLMN(s). Additionally, an LADN DNN discovered by the UE via the retrieved LADN Information is considered an LADN DNN also in the E-PLMNs of the Registered PLMN, i.e. the UE can request LADN Information for the discovered LADN DNN in the E-PLMNs. During the subsequent Registration procedure, if the network does not provide LADN Information for a DNN, the UE deletes any LADN Information for that DNN. When the LADN Information for the UE in the 5GC is changed, the AMF shall update LADN Information to the UE through UE Configuration Update/Registration procedure as described in clauses 4.2.4 / 4.2.2.2.2 of TS 23.502[ Procedures for the 5G System (5GS) ] [3]. When receiving PDU Session Establishment with LADN DNN or Service Request for the established PDU Session corresponding to LADN, the AMF determines UE presence in LADN service area and forwards it to the SMF if the requested DNN is configured at the AMF as a LADN DNN. Based on the LADN Service Area Information in the UE, the UE determines whether it is in or out of a LADN service area. If the UE does not have the LADN Service Area Information for a LADN DNN, the UE shall consider it is out of the LADN service area. The UE takes actions as follows: a) When the UE is out of a LADN service area, the UE: - shall not request to activate UP connection of a PDU Session for this LADN DNN; - shall not attempt to send user data as payload of a NAS message (see clause 5.31.4.1) using a PDU Session for this LADN DNN; - shall not establish/modify a PDU Session for this LADN DNN (except for PS Data Off status change reporting for an established PDU Session); - need not release any existing PDU Session for this LADN DNN unless UE receives explicit SM PDU Session Release Request message from the network. b) When the UE is in a LADN service area, the UE: - may request a PDU Session Establishment/Modification for this LADN DNN; - may request to activate UP connection of the existing PDU Session for this LADN DNN; - may attempt to send user data as payload of a NAS message (see clause 5.31.4.1) using a PDU Session for this LADN DNN. NOTE 6: The evaluation of Service Area Restrictions will be performed before the evaluation of LADN service area, if the UE has overlapping areas between Service Area Restrictions and LADN service area. The SMF supporting a DNN is configured with information about whether this DNN is a LADN DNN or not. When receiving SM request corresponding an LADN from the AMF, the SMF determines whether the UE is inside LADN service area based on the indication (i.e. UE Presence in LADN service area) received from the AMF. If the SMF does not receive the indication, the SMF considers that the UE is outside of the LADN service area. The SMF shall reject the request if the UE is outside of the LADN service area. When the SMF receives a request for PDU Session Establishment with the LADN DNN, it shall subscribe to "UE mobility event notification" for reporting UE presence in Area of Interest by providing LADN DNN to the AMF as described in clauses 5.6.11 and 5.3.4.4. Based on the notification about the UE presence in LADN service area notified by AMF (i.e. IN, OUT, or UNKNOWN), the SMF takes actions as follows based on operator's policy: a) When SMF is informed that the UE presence in a LADN service area is OUT, the SMF shall: - release the PDU Session immediately; or - deactivate the user plane connection for the PDU Session and it shall not attempt to send user data as payload of a NAS message (see clause 5.31.4.1) while maintaining the PDU Session and ensure the Data Notification is disabled and the SMF may release the PDU Session if the SMF is not informed that the UE moves into the LADN service area after a period. b) When SMF is informed that the UE presence a LADN service area is IN, the SMF shall: - ensure that Data Notification is enabled. - trigger the Network triggered Service Request procedure for a LADN PDU Session to active the UP connection or send user data as payload of a NAS message (see clause 5.31.4.1) when the SMF receives downlink data or Data Notification from UPF. c) When the SMF is informed that the UE presence in a LADN service area is UNKNOWN, the SMF may: - ensure that Data Notification is enabled. - trigger the Network triggered Service Request procedure for a LADN PDU Session to active the UP connection or send user data as payload of a NAS message (see clause 5.31.4.1) when the SMF receives downlink data or Data Notification from UPF. SMF may make use of UE mobility analytics provided by NWDAF, as described in clause 6.7.2 of TS 23.288[ Architecture enhancements for 5G System (5GS) to support network data analytics services ] [86], to determine UE presence pattern in LADN service area and take a decision how to handle LADN PDN Session (e.g. release the PDU Session immediately, or deactivate the user plane connection for the PDU Session with maintaining the PDU Session). | 3GPP TS 23.501 | System architecture for the 5G System (5GS) | SA WG2 | 3GPP Series : 23 , Technical realization ("stage 2") | 5.6.5 |
4,499 | 8.54 RAB Context | The RAB Context shall be coded as is depicted in Figure 8.54-1. Figure 8.54-1: RAB Context The RAB Context IE may be repeated within a message with exactly the same Type and Instance to represent a list. The RAB context information element contains sequence number status for one RAB in RNC, which corresponds to one PDP context. The RAB contexts are transferred between the RNCs via the SGSNs at inter SGSN hard handover. NSAPI identifies the PDP context and the associated RAB for which the RAB context IE is intended. The following bits within Octet 5 shall indicate: - Bit 8 – ULPSI (UL PDCP Sequence Number Indication): This bit shall be set to "1" if the UL PDCP Sequence Number is not received from the source RNC and the UL PDCP Sequence Number field shall be set to "0"; - Bit 7 – DLPSI (UL PDCP Sequence Number Indication): This bit shall be set to "1" if the DL PDCP Sequence Number is not received from the source RNC and the DL PDCP Sequence Number field shall be set to "0"; - Bit 6 – ULGSI (UL GTP-U Sequence Number Indication): This bit shall be set to "1" if the UL GTP-U Sequence Number is not received from the source RNC and the UL GTP-U Sequence Number field shall be set to "0"; - Bit 5 – DLGSI (DL GTP-U Sequence Number Indication): This bit shall be set to "1" if the DL GTP-U Sequence Number is not received from the source RNC and the DL GTP-U Sequence Number field shall be set to "0".DL GTP-U Sequence Number is the number for the next downlink GTP-U T-PDU to be sent to the UE. UL GTP-U Sequence Number is the number for the next uplink GTP-U T-PDU to be tunnelled to the SGW. DL PDCP Sequence Number is the number for the next downlink PDCP-PDU to be sent to the UE. UL PDCP Sequence Number is the number for the next uplink PDCP-PDU to be received from the UE. | 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.54 |
4,500 | 6.6.2 Remote UE report procedure 6.6.2.1 General | The purpose of the 5G ProSe remote UE report procedure is for a UE acting as a 5G ProSe layer-3 UE-to-network UE relay to notify the network that a 5G ProSe remote UE is connected to the 5G ProSe layer-3 UE-to-network relay UE or disconnected from the 5G ProSe layer-3 UE-to-network relay UE as specified in 3GPP TS 23.304[ Proximity based Services (ProSe) in the 5G System (5GS) ] [6E]. The UE does not initiate the remote UE report procedure if the timer T3396 is running. The UE does not initiate the remote UE report procedure if the timer T3584 is running. The UE does not initiate the remote UE report procedure if the timer T3585 is running. | 3GPP TS 24.501 | Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 | CT WG1 | 3GPP Series : 24 , Signalling protocols ("stage 3") - user equipment to network | 6.6.2 |
Subsets and Splits
No saved queries yet
Save your SQL queries to embed, download, and access them later. Queries will appear here once saved.