Radio network node, and method performed therein in a communication network

Abstract

Embodiments herein relate to a method performed by a radio network node (120) for handling communication of a UE (10) in a communication network. The radio network node groups the UE (10) into a group of UEs upon connection establishment based on one or more connection properties. The radio network node (120) further selects a connection specific configuration for the UE (10) based on information related to the group.

Description

[0001] RADIO NETWORK NODE, AND METHOD PERFORMED THEREIN IN A COMMUNICATION NETWORK

[0002] TECHNICAL FIELD

[0003] Embodiments herein relate to a radio network node, and method performed therein regarding wireless communication. Furthermore, a computer program product and a computer readable storage medium are also provided herein. In particular, embodiments herein relate to handling communication of user equipments (UE) in a communication network.

[0004] BACKGROUND

[0005] In a typical communication network, UEs, also known as wireless communication devices, mobile stations, stations (STA) and / or wireless devices, communicate via a Radio Access Network (RAN) with one or more core networks (CN). The RAN covers a geographical area which is divided into service areas or cells, with each service area or cell being served by a radio network node such as an access node e.g. a Wi-Fi access point or a radio base station (RBS), which in some networks may also be called, for example, a NodeB, a gNodeB, or an eNodeB. The service area or cell is a geographical area where radio coverage is provided by the radio network node. The radio network node operates on radio frequencies to communicate over an air interface with the UEs within range of the radio network node. The radio network node communicates over a downlink (DL) to the UE, and the UE communicates over an uplink (UL) to the radio network node.

[0006] A Universal Mobile Telecommunications System (UMTS) is a third generation (3G) telecommunication network, which evolved from the second generation (2G) Global System for Mobile Communications (GSM). The UMTS terrestrial radio access network (UTRAN) is essentially a RAN using wideband code division multiple access (WCDMA) and / or High-Speed Packet Access (HSPA) for communication with user equipment. In a forum known as the Third Generation Partnership Project (3GPP), telecommunications suppliers propose and agree upon standards for present and future generation networks and investigate e.g. enhanced data rate and radio capacity. In some RANs, e.g. as in UMTS, several radio network nodes may be connected, e.g., by landlines or microwave, to a controller node, such as a radio network controller (RNC) or a base station controller (BSC), which supervises and coordinates various activities of the plural radio network nodes connected thereto. The RNCs are typically connected to one or more core networks.

[0007] Specifications for the Evolved Packet System (EPS) have been completed within the 3GPP and coming 3GPP releases, such as New Radio (NR), are worked on. The EPS comprises the Evolved Universal Terrestrial Radio Access Network (E-UTRAN), also known as the Long-Term Evolution (LTE) radio access network, and the Evolved Packet Core (EPC), also known as System Architecture Evolution (SAE) core network. E-UTRAN / LTE is a 3GPP radio access technology wherein the radio network nodes are directly connected to the EPC core network. As such, the RAN of an EPS has an architecture comprising radio network nodes connected directly to one or more core networks.

[0008] With the emerging 5G technologies such as NR, the use of very many transmit- and receive-antenna elements may be of great interest as it makes it possible to utilize beamforming, such as transmit-side and receive-side beamforming. Transmit-side beamforming means that the transmitter can amplify the transmitted signals in a selected direction or directions, while suppressing the transmitted signals in other directions. Similarly, on the receive-side, a receiver can amplify signals from a selected direction or directions, while suppressing unwanted signals from other directions. NR is connected to the 5G Core Network (5GC) which comprises a number of Network Functions (NF) such as Session Management Function (SMF), Access Management Function (AMF), Authentication Service Function (AUSF), Policy Control Function (PCF), Unified Data Manager (UDM), Network Repository Function (NRF), Network Exposure Function (NEF), just to mention some. In the 5GC, NFs can discover other NFs by using a discovery service provided by the NRF.

[0009] A gNB with a split architecture is depicted in Fig. 1 A. A gNB-central unit (CU) hosts the radio resource control (RRC) and the control plane (CP) part of the packet data convergence protocol (PDCP); gNB-distributed unit (DU) hosts radio link control (RLC), medium access control (MAC) and the physical layer (PHY).

[0010] SUMMARY

[0011] As part of developing embodiments herein one or more issues have been identified.

[0012] The following chapters were copied from 3GPP technical specifications to show the areas affected by embodiments discussed herein. The text parts that are relevant for embodiments herein are underlined. The paragraphs that are not directly involved are kept for completeness.

[0013] Interfaces and signaling

[0014] FROM 3GPP TS 38.423, Xn Application Protocol (XnAP) V15.15.0:

[0015] 8.4 Global procedures

[0016] 8.4.1 Xn Setup

[0017] 8.4.1.1 General

[0018] The purpose of the Xn Setup procedure is to exchange application level configuration data needed for two NG-RAN nodes to interoperate correctly over the Xn-C interface. NOTE 1 : If Xn-C signalling transport is shared among multiple Xn-C interface instances, one Xn Setup procedure is issued per Xn-C interface instance to be setup, i.e. several Xn Setup procedures may be issued via the same TNL association after that TNL association has become operational.

[0019] NOTE 2: Exchange of application level configuration data also applies between two NG-RAN nodes in case the SN (i.e. the gNB) does not broadcast system information other than for radio frame timing and SFN, as specified in the TS 37.340 [8]. How to use this information when this option is used is not explicitly specified.

[0020] The procedure uses non UE-associated signalling.

[0021] 8.4.1.2 Successful Operation

[0022] Fig. 1B or Figure 8.4.1.2: Xn Setup, successful operation

[0023] The NG-RAN nodei initiates the procedure by sending the XN SETUP REQUEST message to the candidate NG-RAN nodes. The candidate NG-RAN nodes replies with the XN SETUP RESPONSE message.

[0024] The AMF Region Information IE in the XN SETUP REQUEST message shall contain a complete list of Global AMF Region IDs to which the NG-RAN nodei belongs. The AMF Region Information IE in the XN SETUP RESPONSE message shall contain a complete list of Global AMF Region IDs to which the NG-RAN nodes belongs.

[0025] The List of Served Cells NR IE and the List of Served Cells E-UTRA IE, if contained in the XN SETUP REQUEST message, shall contain a complete list of cells served by NG-RAN nodei. The List of Served Cells NR IE and the List of Served Cells E-UTRA IE, if contained in the XN SETUP RESPONSE message, shall contain a complete list of cells served by NG-RAN nodes.

[0026] If Supplementary Uplink is configured at the NG-RAN nodei, the NG-RAN nodei shall include in the XN SETUP REQUEST message the SUL Information IE and the Supported SUL band List IE for each served cell where supplementary uplink is configured.

[0027] If Supplementary Uplink is configured at the NG-RAN nodes, the candidate NG-RAN nodes shall include in the XN SETUP RESPONSE message the SUL Information IE and the Supported SUL band List IE for each served cell where supplementary uplink is configured.

[0028] If the NG-RAN nodei is an ng-eNB, it may include the Protected E-UTRA Resource Indication IE into the XN SETUP REQUEST. If the XN SETUP REQUEST sent by an ng-eNB contains the Protected E-UTRA Resource Indication IE, the receiving gNB should take this into account for cell-level resource coordination with the ng-eNB. The gNB shall consider the received Protected E-UTRA Resource Indication IE content valid until reception of a new update of the IE for the same ng-eNB.

[0029] The protected resource pattern indicated in the Protected E-UTRA Resource Indication IE is not valid in subframes indicated by the Reserved Subframes IE, as well as in the non-control region of the MBSFN subframes i.e. it is valid only in the control region therein. The size of the control region of MBSFN subframes is indicated in the Protected E-UTRA Resource Indication IE. In case of network sharing with multiple cell ID broadcast with shared Xn-C signalling transport, as specified in TS 38.300 [9], the XN SETUP REQUEST message and the XN SETUP REQUEST ACKNOWLEDGE message shall include the Interface Instance Indication IE to identify the corresponding interface instance.

[0030] FROM 3GPP TS 36.423, E-UTRAN X2 Application Protocol (X2AP) V15.13.0:

[0031] 8.7 Procedures for E-UTRAN-NR Dual Connectivity

[0032] 8.7.1 EN-DC X2 Setup

[0033] 8.7.1.1 General

[0034] The purpose of the EN-DC X2 Setup procedure is to exchange application level configuration data needed for eNB and en-gNB to interoperate correctly over the X2 interface. This procedure erases any existing application level configuration data in the two nodes and replaces it by the one received. This procedure also resets the X2 interface like a Reset procedure would do.

[0035] NOTE 1 : If X2-C signalling transport is shared among multiple X2-C interface instances, one EN-DC X2 Setup procedure is issued per X2-C interface instance to be setup, i.e. several X2 Setup procedures may be issued via the same TNL association after that TNL association has become operational.

[0036] NOTE 2: Exchange of application level configuration data also applies between eNB and en-gNB in case the SN (i.e. the en-gNB) does not broadcast system information other than for radio frame timing and SFN, as specified in the TS 37.340

[0032] . How to use this information when this option is used is not explicitly specified.

[0037] The procedure uses non UE-associated signalling.

[0038] 8.7.1.2 Successful Operation

[0039] Fig. 1C or 8.7.1.2-1 : eNB Initiated EN-DC X2 Setup, successful operation

[0040] Fig. 2 or Figure 8.7.1.2-2: en-gNB Initiated EN-DC X2 Setup, successful operation

[0041] If case of network sharing with multiple cell ID broadcast with shared X2-C signalling transport, as specified in TS 36.300

[0015] , the EN-DC X2 SETUP REQUEST message and the EN-DC X2 SETUP RESPONSE message shall include the Interface Instance Indication IE to identify the corresponding interface instance. In the current version of this specification an eNB shall not include the Interface Instance Indication IE in the Initiating NodeType IE in the EN-DC X2 SETUP REQUEST message.

[0042] If the SFN Offset IE is included in the EN-DC X2 SETUP REQUEST or EN-DC X2 SETUP RESPONSE message, the receiving node shall, if supported, use this information to deduce the SFN0 time offset of the reported cell. The receiving node shall consider the received SFN Offset IE content valid until reception of an update of the IE for the same cell(s). eNB initiated EN-DC X2 Setup: An eNB initiates the procedure by sending the EN-DC X2 SETUP REQUEST message to a candidate en- gNB. The candidate en-gNB replies with the EN-DC X2 SETUP RESPONSE message. The initiating eNB shall transfer the complete list of its served cells to the candidate en-gNB. The candidate en-gNB shall reply with the complete list of its served cells or if supported, a partial list of its served cells together with the Partial List Indicator \E. according to the received information in Cell and Capacity Assistance Information IE in EN-DC X2 SETUP REQUEST message. If Supplementary Uplink is configured at the candidate en-gNB, the candidate en-gNB shall include in the EN-DC X2 SETUP RESPONSE message the SUL Information IE and the Supported SUL band List \E for each served cell where supplementary uplink is configured.

[0043] If the EN-DC X2 SETUP REQUEST message contains the Protected E-UTRA Resource Indication IE, the receiving en-gNB should take this into account for cell-level resource coordination with the eNB. The en-gNB shall consider the received Protected E-UTRA Resource Indication IE content valid until reception of a new update of the IE for the same eNB.

[0044] The protected resource pattern indicated in the Protected E-UTRA Resource Indication IE is not valid in subframes indicated by the Reserved Subframes IE, as well as in the non-control region of the MBSFN subframes i.e. it is valid only in the control region therein. The size of the control region of MBSFN subframes is indicated in the Protected E-UTRA Resource Indication IE.

[0045] If the Partial List Indicator ^ is set to "partial" in the EN-DC X2 SETUP RESPONSE message from the en- gNB, the eNB shall, if supported, assume that the en-gNB has included in the List of Served Cells NR IE a partial list of cells.

[0046] If the EN-DC X2 SETUP REQUEST message contains the TNL Transport Layer Address info IE, the receiving en-gNB shall, if supported, take this into account for IPSEC tunnel establishment.

[0047] If the EN-DC X2 SETUP RESPONSE message contains the TNL Transport Layer Address info IE, the receiving eNB shall, if supported, take this into account for IPSEC tunnel establishment.

[0048] If the NR Cell PRACH Configuration IE is included in the Served NR Cell Information IE contained in the EN- DC X2 SETUP RESPONSE message, the eNB may store the information.

[0049] If the CSI-RS Transmision Indication IE is contained in the EN-DC X2 SETUP REQUEST message, the en- gNB may use this information for neighbour NR cell’s CSI-RS measurement.

[0050] If the Intended TDD DL-UL Configuration NR IE is contained in the NR Neighbour Information IE in the EN- DC X2 SETUP REQUEST message, en-gNB should take this information into account for cross-link interference management. The en-gNB shall consider the received Intended TDD DL-UL Configuration NR IE content valid until reception of an update of the IE for the same cell(s).

[0051] Interaction with the eNB Configuration Update procedure:

[0052] The receiving eNB may forward the Intended TDD DL-UL Configuration NR IE received in the Served NR Cell Information IE in the EN-DC X2 SETUP RESPONSE message to neighbouring eNBs by triggering the eNB Configuration Update procedure.

[0053] Interaction with the EN-DC Configuration Update procedure:

[0054] The receiving eNB may forward the Intended TDD DL-UL Configuration NR IE received in the Served NR Cell Information IE in the EN-DC X2 SETUP RESPONSE message to neighbouring en-gNBs by triggering the EN-DC Configuration Update procedure. en-gNB initiated EN-DC X2 Setup:

[0055] An en-gNB initiates the procedure by sending the EN-DC X2 SETUP REQUEST message to a candidate eNB. The candidate eNB replies with the EN-DC X2 SETUP RESPONSE message. The initiating en-gNB shall transfer the complete list of its served cells or if supported, a partial list of its served cells together with the Partial List Indicator IE in the EN-DC X2 SETUP REQUEST message to the candidate eNB. The candidate eNB shall reply with the complete list of its served cells.

[0056] If Supplementary Uplink is configured at the en-gNB, the en-gNB shall include in the EN-DC X2 SETUP REQUEST message the SUL Information IE and the Supported SUL band List \E for each served cell where supplementary uplink is configured.

[0057] If the EN-DC X2 SETUP RESPONSE message contains the Protected E-UTRA Resource Indication IE, the receiving en-gNB should take this into account for cell-level resource coordination with the eNB. The en-gNB shall consider the received Protected E-UTRA Resource Indication IE content valid until reception of a new update of the IE for the same eNB.

[0058] If the Partial List Indicator ^ is set to "partial" in the EN-DC X2 SETUP REQUEST message from the en- gNB, the eNB shall, if supported, assume that the en-gNB has included in the List of Served Cells NR IE a partial list of cells.

[0059] If the Cell and Capacity Assistance Information IE is present in the EN-DC X2 SETUP RESPONSE message from the eNB, the en-gNB shall, if supported, store the collected information to be used for future interface management.

[0060] If the EN-DC X2 SETUP REQUEST message contains the TNL Transport Layer Address info IE, the receiving eNB shall, if supported, take this into account for IPSEC tunnel establishment.

[0061] If the EN-DC X2 SETUP RESPONSE message contains the TNL Transport Layer Address info IE, the receiving en-gNB shall, if supported, take this into account for IPSEC tunnel establishment.

[0062] If the NR Cell PRACH Configuration IE is included in the Served NR Cell Information IE contained in the EN- DC X2 SETUP REQUEST message, the eNB may store the information.

[0063] If the CSI-RS Transmision Indication IE is contained in the EN-DC X2 SETUP REQUEST message, the eNB should take it into account when forwarding neighbour NR cell’s CSI-RS configuration.

[0064] If the Intended TDD DL-UL Configuration NR IE is contained in the NR Neighbour Information IE in the EN- DC X2 SETUP RESPONSE message, en-gNB should take this information into account for cross-link interference management. The en-gNB shall consider the received Intended TDD DL-UL Configuration NR IE content valid until reception of an update of the IE for the same cell(s).

[0065] Interaction with the eNB Configuration Update procedure:

[0066] The receiving eNB may forward the Intended TDD DL-UL Configuration NR IE received in the Served NR Cell Information IE in the EN-DC X2 SETUP REQUEST message to neighbouring eNBs by triggering the eNB Configuration Update procedure.

[0067] Interaction with the EN-DC Configuration Update procedure: The receiving eNB may forward the Intended TDD DL-UL Configuration NR IE received in the Served NR Cell Information IE in the EN-DC X2 SETUP REQUEST message to neighbouring en-gNBs by triggering the EN-DC Configuration Update procedure.

[0068] FROM 3GPP TS 38.340 Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multiconnectivity; V15.16.0:

[0069] 4.3.1 Control Plane

[0070] 4.3.1 .1 Common MR-DC principles

[0071] In MR-DC, there is an interface between the MN and the SN for control plane signalling and coordination. For each MR-DC UE, there is also one control plane connection between the MN and a corresponding CN entity. The MN and the SN involved in MR-DC for a certain UE control their radio resources and are primarily responsible for allocating radio resources of their cells.

[0072] Figure 4.3.1 .1 -1 shows C-plane connectivity of MN and SN involved in MR-DC for a certain UE.

[0073] Fig. 3 or figure 4.3.1.1-1 : C-Plane connectivity for EN-DC (left) and MR-DC with 5GC (right).

[0074] 4.3.1.2 MR-DC with EPC

[0075] In MR-DC with EPC (EN-DC), the involved core network entity is the MME. S1 -MME is terminated in MN and the MN and the SN are interconnected via X2-C.

[0076] 4.3.1.3 MR-DC with 5GC

[0077] I n MR-DC with 5GC (NG EN-DC, NE-DC and NR-DC), the involved core network entity is the AMF. NG-C is terminated in the MN and the MN and the SN are interconnected via Xn-C.

[0078] 4.3.2 User Plane

[0079] 4.3.2.1 Common MR-DC principles

[0080] There are different U-plane connectivity options of the MN and SN involved in MR-DC for a certain UE, as shown in Figure 4.3.2.1 -1 . The U-plane connectivity depends on the bearer option configured:

[0081] - For MN terminated bearers, the user plane connection to the CN entity is terminated in the MN;

[0082] - For SN terminated bearers, the user plane connection to the CN entity is terminated in the SN;

[0083] - The transport of user plane data over the Uu either involves MCG or SCG radio resources or both:

[0084] - For MCG bearers, only MCG radio resources are involved: - For SCG bearers, only SCG radio resources are involved;

[0085] - For split bearers, both MCG and SCG radio resources are involved.

[0086] - For split bearers, MN terminated SCG bearers and SN terminated MCG bearers, PDCP data is transferred between the MN and the SN via the MN-SN user plane interface.

[0087] Fig. 4 or Figure 4.3.2.1-1 : U-Plane connectivity for EN-DC (left) and MR-DC with 5GC (right).

[0088] 4.3.2.2 MR-DC with EPC

[0089] For MR-DC with EPC (EN-DC), X2-U interface is the user plane interface between MN and SN, and S1 -U is the user plane interface between the MN, the SN or both and the S-GW.

[0090] 4.3.2.3 MR-DC with 5GC

[0091] For MR-DC with 5GC (NGEN-DC, NE-DC and inter-gNB NR-DC), Xn-U interface is the user plane interface between MN and SN, and NG-U is the user plane interface between the MN, the SN or both and the UPF.

[0092] 10.2 Secondary Node Addition

[0093] 10.2.1 EN-DC

[0094] The Secondary Node Addition procedure is initiated by the MN and is used to establish a UE context at the SN to provide resources from the SN to the UE. For bearers requiring SCG radio resources, this procedure is used to add at least the first cell of the SCG. This procedure can also be used to configure an SN terminated MCG bearer (where no SCG configuration is needed). Figure 10.2.1 -1 shows the Secondary Node Addition procedure.

[0095] Figure 5 or Fig. 10.2.1-1 : Secondary Node Addition procedure

[0096] 1 .The MN decides to request the SN to allocate resources for a specific E-RAB, indicating E-RAB characteristics (E-RAB parameters, TNL address information corresponding to bearer type). In addition, for bearers requiring SCG radio resources, MN indicates the requested SCG configuration information, including the entire UE capabilities and the UE capability coordination result. In this case, the MN also provides the latest measurement results for SN to choose and configure the SCG cell(s). The MN may request the SN to allocate radio resources for split SRB operation. The MN always provides all the needed security information to the SN (even if no SN terminated bearers are setup) to enable SRB3 to be setup based on SN decision. In case of bearer options that require X2-U resources between the MN and the SN, the MN provides X2-U TNL address information for the respective E- RAB, X2-U DL TNL address information for SN terminated bearers, X2-U UL TNL address information for MN terminated bearers. In case of SN terminated split bearers the MN provides the maximum QoS level that it can support. The SN may reject the request.

[0097] NOTE 1 : For split bearers, MCG and SCG resources may be requested of such an amount, that the QoS for the respective E-RAB is guaranteed by the exact sum of resources provided by the MCG and the SCG together, or even more. For MN terminated split bearers, the MNs decision is reflected in step 1 by the E-RAB parameters signalled to the SN, which may differ from E-RAB parameters received over S1 . NOTE 2: For a specific E-RAB, the MN may request the direct establishment of an SCG or a split bearer, i.e., without first having to establish an MCG bearer. It is also allowed that all E-RABs can be configured as SN terminated bearers, i.e. there is no E-RAB established as an MN terminated bearer.

[0098] 2. If the RRM entity in the SN is able to admit the resource request, it allocates respective radio resources and, dependent on the bearer option, respective transport network resources. For bearers requiring SCG radio resources, the SN triggers Random Access so that synchronisation of the SN radio resource configuration can be performed. The SN decides the PSCell and other SCG SCells and provides the new SCG radio resource configuration to the MN in a NR RRC configuration message contained in the SgNB Addition Request Acknowledge message. In case of bearer options that require X2-U resources between the MN and the SN, the SN provides X2-U TNL address information for the respective E-RAB, X2-U UL TNL address information for SN terminated bearers, X2-U DL TNL address information for MN terminated bearers. For SN terminated bearers, the SN provides the S1 -U DL TNL address information for the respective E-RAB and security algorithm. If SCG radio resources have been requested, the SCG radio resource configuration is provided.

[0099] NOTE 3: For the SN terminated split bearer option, the SN may either decide to request resources from the MN of such an amount, that the QoS for the respective E-RAB is guaranteed by the exact sum of resources provided by the MN and the SN together, or even more. The SNs decision is reflected in step 2 by the E-RAB parameters signalled to the MN, which may differ from E-RAB parameters received in step 1 . The QoS level requested from the MN shall not exceed the level that the MN offered when setting up the split bearer in step 1 .

[0100] NOTE 4: In case of MN terminated bearers, transmission of user plane data may take place after step 2.

[0101] NOTE 5: In case of SN terminated bearers , data forwarding and the SN Status Transfer may take place after step 2.

[0102] 3. The MN sends to the UE the RRCConnectionReconfiguration message including the NR RRC configuration message, without modifying it.

[0103] 4. The UE applies the new configuration and replies to MN with RRCConnectionReconfigurationComplete message, including a NR RRC response message, if needed. In case the UE is unable to comply with (part of) the configuration included in the RRCConnectionReconfiguration message, it performs the reconfiguration failure procedure.

[0104] 5. The MN informs the SN that the UE has completed the reconfiguration procedure successfully via SgNB ReconfigurationComp / ete message, including the encoded NR RRC response message, if received from the UE.

[0105] 6. If configured with bearers requiring SCG radio resources, the UE performs synchronisation towards the PSCell of the SN. The order the UE sends the RRCConnectionReconfigurationComplete message and performs the Random Access procedure towards the SCG is not defined. The successful RA procedure towards the SCG is not required for a successful completion of the RRC Connection Reconfiguration procedure.

[0106] 7. In case of SN terminated bearers using RLC AM, the MN sends SN Status Transfer.

[0107] 8. In case of SN terminated bearers using RLC AM, and dependent on the bearer characteristics of the respective E-RAB, the MN may take actions to minimise service interruption due to activation of EN- DC (Data forwarding). 9-12. For SN terminated bearers, the update of the UP path towards the EPC is performed.

[0108] 10.2.2 MR-DC with 5GC

[0109] The Secondary Node (SN) Addition procedure is initiated by the MN and is used to establish a UE context at the SN in order to provide resources from the SN to the UE. For bearers requiring SCG radio resources, this procedure is used to add at least the initial SCG serving cell of the SCG. This procedure can also be used to configure an SN terminated MCG bearer (where no SCG configuration is needed). Figure 10.2.2-1 shows the SN Addition procedure.

[0110] Fig. 6 or Figure 10.2.2-1 : SN Addition procedure

[0111] 1 . The MN decides to request the target SN to allocate resources for one or more specific PDU Sessions / QoS Flows, indicating QoS Flows characteristics (QoS Flow Level QoS parameters, PDU session level TNL address information, and PDU session level Network Slice info). In addition, for bearers requiring SCG radio resources, MN indicates the requested SCG configuration information, including the entire UE capabilities and the UE capability coordination result. In this case, the MN also provides the latest measurement results for SN to choose and configure the SCG cell(s). The MN may request the SN to allocate radio resources for split SRB operation. In NGEN-DC and NR-DC, the MN always provides all the needed security information to the SN (even if no SN terminated bearers are setup) to enable SRB3 to be setup based on SN decision.

[0112] For MN terminated bearer options that require Xn-U resources between the MN and the SN, the MN provides Xn-U UL TNL address information. For SN terminated bearers, the MN provides a list of available DRB IDs. The S-NG-RAN node shall store this information and use it when establishing SN terminated bearers. The SN may reject the request.

[0113] For SN terminated bearer options that require Xn-U resources between the MN and the SN, the MN provides in step 1 a list of QoS flows per PDU Sessions for which SCG resources are requested to be setup upon which the SN decides how to map QoS flows to DRB.

[0114] NOTE 1 : For split bearers, MCG and SCG resources may be requested of such an amount, that the QoS for the respective QoS Flow is guaranteed by the exact sum of resources provided by the MCG and the SCG together, or even more. For MN terminated split bearers, the MN decision is reflected in step 1 by the QoS Flow parameters signalled to the SN, which may differ from QoS Flow parameters received over NG.

[0115] NOTE 2: For a specific QoS flow, the MN may request the direct establishment of SCG and / or split bearers, i.e. without first having to establish MCG bearers. It is also allowed that all QoS flows can be mapped to SN terminated bearers, i.e. there is no QoS flow mapped to an MN terminated bearer.

[0116] 2. If the RRM entity in the SN is able to admit the resource request, it allocates respective radio resources and, dependent on the bearer type options, respective transport network resources. For bearers requiring SCG radio resources the SN triggers UE Random Access so that synchronisation of the SN radio resource configuration can be performed. The SN decides for the PSCell and other SCG SCells and provides the new SCG radio resource configuration to the MN within an SN RRC configuration message contained in the SN Addition Request Acknowledge message. In case of bearer options that require Xn-U resources between the MN and the SN, the SN provides Xn-U TNL address information for the respective DRB, Xn-U UL TNL address information for SN terminated bearers, Xn-U DL TNL address information for MN terminated bearers. For SN terminated bearers, the SN provides the NG-U DL TNL address information for the respective PDU Session and security algorithm. If SCG radio resources have been requested, the SCG radio resource configuration is provided.

[0117] NOTE 3: In case of MN terminated bearers, transmission of user plane data may take place after step 2.

[0118] NOTE 4: In case of SN terminated bearers, data forwarding and the SN Status Transfer may take place after step 2.

[0119] NOTE 5: For MN terminated NR SCG bearers for which PDCP duplication with CA is configured the MN allocates 2 separate Xn-U bearers.

[0120] For SN terminated NR MCG bearers for which PDCP duplication with CA is configured the SN allocates 2 separate Xn-U bearers.

[0121] 2a. For SN terminated bearers using MCG resources, the MN provides Xn-U DL TNL address information in the Xn-U Address Indication message.

[0122] 3. The MN sends the MN RRC reconfiguration message to the UE including the SN RRC configuration message, without modifying it.

[0123] 4. The UE applies the new configuration and replies to MN with MN RRC reconfiguration complete message, including an SN RRC response message for SN, if needed. In case the UE is unable to comply with (part of) the configuration included in the MN RRC reconfiguration message, it performs the reconfiguration failure procedure.

[0124] 5. The MN informs the SN that the UE has completed the reconfiguration procedure successfully via SN Reconfiguration Complete message, including the SN RRC response message, if received from the UE.

[0125] 6. If configured with bearers requiring SCG radio resources, the UE performs synchronisation towards the PSCell configured by the SN. The order the UE sends the MN RRC reconfiguration complete message and performs the Random Access procedure towards the SCG is not defined. The successful RA procedure towards the SCG is not required for a successful completion of the RRC Connection Reconfiguration procedure.

[0126] 7. In case of SN terminated bearers using RLC AM, the MN sends SN Status Transfer.

[0127] From 3GPP TS 38.463, E1 Application Protocol (E1AP) V15.10.0:

[0128] 8.3.1 Bearer Context Setup

[0129] 8.3.1.1 General

[0130] The purpose of the Bearer Context Setup procedure is to allow the gNB-CU-CP to establish a bearer context in the gNB-CU-UP. The procedure uses UE-associated signalling. 8.3.1.2 Successful Operation

[0131] Fig. 7 or Figure 8.3.1.2-1 : Bearer Context Setup procedure: Successful Operation.

[0132] The gNB-CU-CP initiates the procedure by sending the BEARER CONTEXT SETUP REQUEST message to the gNB- CU-UP. If the gNB-CU-UP succeeds to establish the requested resources, it replies to the gNB-CU-CP with the BEARER CONTEXT SETUP RESPONSE message.

[0133] The gNB-CU-UP shall report to the gNB-CU-CP, in the BEARER CONTEXT SETUP RESPONSE message, the result for all the requested resources in the following way:

[0134] For E-UTRAN:

[0135] 1. - A list of DRBs which are successfully established shall be included in the DRB Setup List IE;

[0136] 2. - A list of DRBs which failed to be established shall be included in the DRB Failed List IE;

[0137] For NG-RAN:

[0138] 3. - A list of PDU Session Resources which are successfully established shall be included in the PDU Session Resource Setup List IE;

[0139] 4. - A list of PDU Session Resources which failed to be established shall be included in the PDU Session Resource Failed List IE;

[0140] 5. - For each established PDU Session Resource, a list of DRBs which are successfully established shall be included in the DRB Setup List IE;

[0141] 6. - For each established PDU Session Resource, a list of DRBs which failed to be established shall be included in the DRB Failed List IE;

[0142] 7. - For each established DRB, a list of QoS Flows which are successfully established shall be included in the Flow Setup List IE;

[0143] 8. - For each established DRB, a list of QoS Flows which failed to be established shall be included in the Flow Failed List IE;

[0144] When the gNB-CU-UP reports the unsuccessful establishment of a PDU Session Resource, DRB or QoS Flow the cause value should be precise enough to enable the gNB-CU-CP to know the reason for the unsuccessful establishment.

[0145] If the Existing Allocated NG DL UP Transport Layer Information IE is contained in the BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP may re-use the indicated resources already allocated for this bearer context. If the gNB-CU-UP decides to re-use the indicated resources, it shall include the NG DL UP Unchanged IE in the BEARER CONTEXT SETUP RESPONSE message.

[0146] If the PDU Session Resource DL Aggregate Maximum Bit Rate IE is contained in the PDU Session Resource To Setup List IE in the BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP shall store and use the information for the down link traffic policing for the Non-GBR QoS flows for the concerned UE as specified in TS 23.501

[0020] .

[0147] If the Data Forwarding Information Request IE, PDU Session Data Forwarding Information Request IE or the DRB Data Forwarding Information Request IE are included in the BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP shall include the requested forwarding information in the Data Forwarding Information Response IE, PDU Session Data Forwarding Information Response IE or the DRB Data Forwarding Information Response IE in the BEARER CONTEXT SETUP RESPONSE message.

[0148] If the DL UP Parameters IE is contained in the DRB To Setup List IE in the BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP shall configure the corresponding information. For each PDU session for which the Security Indication IE is included in the PDU Session Resource To Setup List IE of the BEARER CONTEXT SETUP REQUEST message, and the Integrity Protection Indication IE or Confidentiality Protection Indication IE is set to "preferred", then the gNB-CU-UP should, if supported, perform user plane integrity protection or ciphering, respectively, for the concerned PDU session and shall notify whether it performed the user plane integrity protection or ciphering by including the Integrity Protection Result IE or Confidentiality Protection Result IE, respectively, in the PDU Session Resource Setup List IE of the BEARER CONTEXT SETUP RESPONSE message.

[0149] For each PDU session for which the Security Indication IE is included in the PDU Session Resource To Setup List IE of the BEARER CONTEXT SETUP REQUEST message, and the Integrity Protection Indication IE or Confidentiality Protection Indication IE is set to "required", then the gNB-CU-UP shall perform user plane integrity protection or ciphering, respectively, for the concerned PDU Session. If the gNB-CU-UP cannot perform the user plane integrity protection or ciphering, it shall reject the setup of the PDU Session Resources with an appropriate cause value.

[0150] For each PDU session for which the Security Indication IE is included in the PDU Session Resource To Setup List IE of the BEARER CONTEXT SETUP REQUEST message:

[0151] 9. - if the Integrity Protection Indication IE is set to "not needed", then the gNB-CU-UP shall not perform user plane integrity protection for the concerned PDU session;

[0152] 10. - if the Confidentiality Protection Indication IE is set to "not needed", then the gNB-CU-UP shall not perform user plane ciphering for the concerned PDU session.

[0153] For each PDU session, if the Data Forwarding to E-UTRAN Information List IE is included in the PDU Session Resource To Modify List IE in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall, if supported, use it for inter-system data forwarding from 5GS to EPS as specified in TS38.300 [8].

[0154] If the UE DL Maximum Integrity Protected Data Rate IE is contained in the BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP shall use this value when enforcing the maximum integrity protected data rate for the UE.

[0155] If the Bearer Context Status Change IE is contained in the BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP shall consider the UE RRC state and act as specified in TS 38.401 [2].

[0156] For each requested DRB, if the PDCP Duplication IE is included in the PDCP Configuration IE contained in the BEARER CONTEXT SETUP REQUEST message, then the gNB-CU-UP shall include two UP Transport Layer Information lEs in the BEARER CONTEXT SETUP RESPONSE message to support packet duplication. If only one cell group is included in the Cell Group Information IE for the concerned DRB, then the gNB-CU-UP shall consider that the first UP Transport Layer Information IE of the two UP Transport Layer Information lEs is for the primary path.

[0157] For each requested DRB, if the Additional PDCP duplication Information IE is included in the PDCP Configuration IE contained in the BEARER CONTEXT SETUP REQUEST message, then the gNB-CU-UP shall, if supported, include the same number of UP Transport Layer Information lEs indicated by the Additional PDCP duplication Information IE in the BEARER CONTEXT SETUP RESPONSE message to support packet duplication. If only one cell group is included in the Cell Group Information IE for the concerned DRB, then the gNB-CU-UP shall consider that the first UP Transport Layer Information IE of these UP Transport Layer Information lEs is for the primary path. If more than one cell group is included in the Cell Group Information IE, then the gNB-CU-UP shall consider that the number of duplication tunnels for each cell group is indicated by the Number of tunnels IE, and that the first UP Transport Layer Information IE for each cell group is for the primary path or the split secondary path.

[0158] If the PDCP SN Status Information IE is contained within the DRB To Setup List IE in the BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP shall take it into account and act as specified in TS 38.401 [2]. If the QoS Flow Mapping Indication IE is contained in the QoS Flows Information To Be Setup IE within the DRB To Setup List IE in the BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP may take it into account that only the uplink or downlink QoS flow is mapped to the DRB.

[0159] If the QoS Flows Remapping IE is contained within the DRB To Setup List IE in the BEARER CONTEXT SETUP REQUEST message for a DRB and set to "update", the gNB-CU-UP shall, if supported, consider that QoS flows mapped for the DRB is updated to the QoS flow(s) included in the QoS Flows Information To Be Setup IE after finishing handling forwarded PDCP SDUs during an intra-system handover procedure. If the QoS Flows Remapping IE is contained within the DRB To Setup List IE in the BEARER CONTEXT SETUP REQUEST message for a DRB and set to "source configuration", the gNB-CU-UP shall, if supported, consider that no QoS flow is mapped to the DRB after finishing handling forwarded PDCP SDUs over that DRB during an intra-system handover procedure and ignore the information included in the QoS Flows Information To Be Setup IE for the concerned DRB.

[0160] For each PDU Session Resource, if the Network Instance IE is included in the PDU Session Resource To Setup List IE in the BEARER CONTEXT SETUP REQUEST message and the Common Network Instance IE is not included, the gNB-CU-UP shall, if supported, use it when selecting transport network resource as specified in TS 23.501

[0020] .

[0161] For each PDU session, if the Common Network Instance IE is included in the PDU Session Resource To Setup List IE in the BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP shall, if supported, use it when selecting transport network resource as specified in TS 23.501

[0020] .

[0162] For each PDU session, if the Redundant NG UL UP Transport Layer Information IE is included in the PDU Session Resource To Setup List IE in the BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP shall, if supported, use it as the uplink termination point of the redundant tunnel for the user plane data of those QoS flows in this PDU session which need redundant transmission as described in TS 23.501

[0020] , and it shall include the Redundant NG DL UP Transport Layer Information IE in the PDU Session Resource Setup List IE in the BEARER CONTEXT SETUP RESPONSE message.

[0163] For each PDU Session Resource, if the Redundant Common Network Instance IE is included in the PDU Session Resource To Setup List IE in the BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP shall, if supported, use it when selecting transport network resource for the redundant transmission as specified in TS 23.501

[0020] ,

[0164] For each PDU session, if the Redundant QoS Flow Indicator IE is included in the QoS Flow QoS Parameters List IE in the BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP shall, if supported, consider it for the redundant transmission.

[0165] For each PDU session, if the Redundant PDU Session Information IE is included in the PDU Session Resource To Setup List IE contained in the BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP shall, if supported, set up the redundant user plane resources, as specified in TS 23.501

[0020] and include, if supported, the Used Redundant PDU Session Information IE in the PDU Session Resource Setup List IE in the BEARER CONTEXT SETUP RESPONSE message.

[0166] If UE Inactivity Timer IE or PDU session Inactivity Timer IE or DRB Inactivity Timer IE is contained in BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP shall take it into account when perform inactivity monitoring.

[0167] If the DRB QoS IE is contained within the DRB To Setup List IE in the BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP shall, if supported, take it into account as specified in TS 28.552

[0022] . If the gNB-DU-ID IE is contained in the BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP shall store the information received.

[0168] If the RAN UE ID IE is contained in the BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP shall store the information received.

[0169] For each successfully established DRB, the gNB-CU-UP shall provide, in the respective UL UP Parameters IE of the BEARER CONTEXT SETUP RESPONSE, one UL UP Transport Layer Information Item per cell group entry contained in the respective Cell Group Information IE of the BEARER CONTEXT SETUP REQUEST message.

[0170] If the Trace Activation IE is included in the BEARER CONTEXT SETUP REQUEST message the gNB-CU-UP shall, if supported, initiate the requested trace function as described in TS 32.422

[0024] . In particular, the gNB-CU-UP shall, if supported:

[0171] 11. - if the MDT Activation IE is set to "Immediate MDT Only", initiate the requested MDT session as described in TS 32.422

[0024] and the gNB-CU-UP shall ignore Interfaces To Trace IE, and Trace Depth IE;

[0172] 12. - if the MDT Activation IE is set to "Immediate MDT and Trace", initiate the requested trace session and MDT session as described in TS 32.422

[0024] ;

[0173] If the Management Based MDT PLMN List IE is contained in the BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP shall, if supported, store the received information, and use this information to allow subsequent selection of the UE for management based MDT defined in TS 32.422

[0024] .

[0174] For EN-DC, if the Subscriber Profile ID for RAT / Frequency priority IE is included in the BEARER CONTEXT SETUP REQUEST, the gNB-CU-UP may use it to apply specific RRM policies as specified in TS 36.300

[0025] . If the Additional RRM Policy Index IE is included in the BEARER CONTEXT SETUP REQUEST, the gNB-CU-UP may use it to apply specific RRM policies as specified in TS 36.300

[0025] .

[0175] If the TSC Traffic Characteristics IE is included in the BEARER CONTEXT SETUP REQUEST message, the gNB- CU-UP shall, if supported, take into account the corresponding information received in the TSC Traffic Characteristics IE.

[0176] For each QoS flow whose DRB has been successfully established and the QoS Monitoring Request IE was included in the QoS Flow Level QoS Parameters IE contained in the BEARER CONTEXT SETUP REQUEST message, the gNB- CU-UP shall store this information, and, if supported, perform delay measurement and QoS monitoring, as specified in TS 23.501

[0020] . If the QoS Monitoring Reporting Frequency IE was included in the QoS Flow Level QoS Parameters IE contained in the BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP shall store this information, and, if supported, use it for RAN part delay reporting.

[0177] If the BEARER CONTEXT SETUP REQUEST message contains the NPN Context Information IE the gNB-CU-UP shall, if supported, take it into account when allocating UP resources for the bearer context.

[0178] For each requested DRB, if the EHC Parameters IE is included in the PDCP Configuration IE, the gNB-CU-CP shall, if supported, also include ROHC Parameters IE in the PDCP Configuration IE in the BEARER CONTEXT SETUP REQUEST message, to enable the gNB-CU-UP to perform appropriate header compression.

[0179] If the EHC parameters IE is included in the PDCP Configuration IE contained in the BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP may take these parameters into account to perform appropriate header compression for the concerned DRB. If the EHC Downlink IE is included in the EHC parameters IE and the value of drb-ContinueEHC-DL IE is set to ‘true’, the gNB-CU-UP shall, if supported, configure Ethernet header compression for downlink and continue the downlink EHC header compression protocol as specified in TS 38.331 V 15.17.0

[0010] . If the EHC Downlink IE is included in the EHC parameters IE and the value of drb-ContinueEHC-DL IE is set to ‘false’, the gNB-CU-UP shall, if supported, configure Ethernet header compression for downlink and reset the downlink EHC header compression protocol during PDCP re-establishment as specified in TS 38.331 V15.17.0

[0010] . If the EHC Uplink IE is included in the EHC parameters IE and the value of drb-ContinueEHC-UL IE is set to ‘true’, the gNB-CU-UP shall, if supported, configure Ethernet header compression for uplink and continue the uplink EHC header compression protocol as specified in TS 38.331 V15.17.0

[0010] . If the EHC Uplink IE is included in the EHC parameters IE and the value of drb-ContinueEHC-UL IE is set to ‘false’, the gNB-CU-UP shall, if supported, configure Ethernet header compression for uplink and resets the uplink EHC header compression protocol during PDCP re-establishment as specified in TS 38.331 V15.17.0

[0010] .

[0180] If the DAPS Request Information IE is included for a DRB to be setup in the BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP shall consider that the request concerns a DAPS handover for that DRB and, if admitted, act as specified in TS 38.300 [4].

[0181] If the CHO Initiation IE is contained in the BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP shall consider that the request concerns conditional handover or conditional PSCell change and act as specified in TS 38.401 [2].

[0182] If the MCG Offered GBR QoS Flow Information IE is contained in the QoS Flows Information To Be Setup IE within the DRB To Setup List IE in the BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP may take it into account when two cell groups are served by the gNB-CU-UP.

[0183] If the Additional Handover Information IE is included in the BEARER CONTEXT SETUP REQUEST message and set to “Discard PDCP SN”, the gNB-CU-UP shall, if supported, remove the forwarded PDCP SNs if received in the forwarded GTP-U packets, and deliver the forwarded PDCP SDUs to the UE, as specified in TS 38.300 [8].

[0184] If the Ignore Mapping Rule Indication IE is contained within the DRB To Setup List IE for a DRB in the BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP shall, if supported, ignore the QoS flow mapping information indicated by the QoS Flows Information To Be Setup IE for the concerned DRB.

[0185] If the Direct Forwarding Path Availability IE set to "inter-system direct path available" is included in the BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP shall, if supported, assign the UP Transport Layer Information for inter-system direct data forwarding from the appropriate address space, if applicable.

[0186] If the Direct Forwarding Path Availability IE set to “intra-system direct path available” is included in the BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP shall, if supported, assign the UP Transport Layer Information for intra-system direct data forwarding from the appropriate address space, if applicable.

[0187] If the gNB-CU-UP UE E1AP ID IE is contained in the BEARER CONTEXT SETUP REQUEST message, the gNB- CU-UP may use it to identify the UE context as specified in TS 38.401 [2].

[0188] If the Data Forwarding Source IP Address IE is included in the DRB To Setup List E-UTRAN IE or in the QoS Flow Level QoS Parameters IE contained in the BEARER CONTEXT SETUP REQUEST message, the gNB-CU-UP shall, if supported, store this information in the UE context and use it as part of its ACL functionality configuration actions, if such ACL functionality is deployed.

[0189] If the Data Forwarding Source IP Address IE is included in the DRB Setup List E-UTRAN IE or in the Flow Setup List IE within the DRB Setup List IE in the PDU Session Resource Setup List IE of the BEARER CONTEXT SETUP RESPONSE message, the gNB-CU-CP shall, if supported, store this information in the UE context and use it as part of its ACL functionality configuration actions, if such ACL functionality is deployed. 8.3.2 Bearer Context Modification (gNB-CU-CP initiated)

[0190] 8.3.2.1 General

[0191] The purpose of the Bearer Context Modification procedure is to allow the gNB-CU-CP to modify a bearer context in the gNB-CU-UP. The procedure uses UE-associated signalling.

[0192] 8.3.2.2 Successful Operation

[0193] Figure 8 or 8.3.2.2-1 : Bearer Context Modification procedure: Successful Operation.

[0194] The gNB-CU-CP initiates the procedure by sending the BEARER CONTEXT MODIFICATION REQUEST message to the gNB-CU-UP. If the gNB-CU-UP succeeds to modify the bearer context, it replies to the gNB-CU-CP with the BEARER CONTEXT MODIFICATION RESPONSE message.

[0195] The gNB-CU-UP shall report to the gNB-CU-CP, in the BEARER CONTEXT MODIFICATION RESPONSE message, the result for all the requested resources in the following way:

[0196] For E-UTRAN:

[0197] A list of DRBs which are successfully established shall be included in the DRB Setup List IE;

[0198] A list of DRBs which failed to be established shall be included in the DRB Failed List IE;

[0199] A list of DRBs which are successfully modified shall be included in the DRB Modified List IE;

[0200] A list of DRBs which failed to be modified shall be included in the DRB Failed To Modify List IE;

[0201] For NG-RAN:

[0202] A list of PDU Session Resources which are successfully established shall be included in the PDU Session Resource Setup List IE;

[0203] A list of PDU Session Resources which failed to be established shall be included in the PDU Session Resource Failed List IE;

[0204] A list of PDU Session Resources which are successfully modified shall be included in the PDU Session Resource Modified List IE;

[0205] A list of PDU Session Resources which failed to be modified shall be included in the PDU Session Resource Failed To Modify List IE;

[0206] For each successfully established or modified PDU Session Resource, a list of DRBs which are successfully established shall be included in the DRB Setup List IE;

[0207] For each successfully established or modified PDU Session Resource, a list of DRBs which failed to be established shall be included in the DRB Failed List IE;

[0208] For each successfully modified PDU Session Resource, a list of DRBs which are successfully modified shall be included in the DRB Modified List IE;

[0209] For each successfully modified PDU Session Resource, a list of DRBs which failed to be modified shall be included in the DRB Failed To Modify List IE; For each successfully established or modified DRB, a list of QoS Flows which are successfully established shall be included in the Flow Setup List IE;

[0210] For each successfully established or modified DRB, a list of QoS Flows which failed to be established shall be included in the Flow Failed List IE;

[0211] When the gNB-CU-UP reports the unsuccessful establishment of a PDU Session Resource, DRB or QoS Flow the cause value should be precise enough to enable the gNB-CU-CP to know the reason for the unsuccessful establishment.

[0212] If the Security Information IE is contained in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall update the corresponding information.

[0213] If the UE DL Aggregate Maximum Bit Rate IE is contained in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall update the corresponding information.

[0214] If the UE DL Maximum Integrity Protected Data Rate IE is contained in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall update the corresponding information.

[0215] If the Bearer Context Status Change IE is contained in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall consider the UE RRC state and act as specified in TS 38.401 [2].

[0216] If the Data Forwarding Information Request IE, PDU Session Data Forwarding Information Request IE or the DRB Data Forwarding Information Request IE are included in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall include the requested forwarding information in the Data Forwarding Information Response IE, PDU Session Data Forwarding Information Response IE or the DRB Data Forwarding Information Response IE in the BEARER CONTEXT MODIFICATION RESPONSE message.

[0217] If the PDU Session Data Forwarding Information IE is included in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall, if supported, consider that data forwarding is applicable for the indicated QoS flows for the concerned PDU session.

[0218] If the Secondary PDU Session Data Forwarding Information IE is included in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall, if supported, consider that data forwarding is applicable for the indicated QoS flows for the concerned PDU session.

[0219] If the PDCP Configuration IE is contained in the DRB To Modify List IE in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall update the corresponding information, except for the PDCP SN UL Size IE, the PDCP SN DL Size IE and the RLC mode IE which shall be ignored.

[0220] If the E-UTRAN QoS IE is contained in the DRB To Modify List IE in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall update the corresponding information.

[0221] If the PDCP SN Status Request IE is contained in the DRB To Modify List IE in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall act as specified in TS 38.401 [2] and include the UL COUNT Value IE and the DL COUNT Value IE in the BEARER CONTEXT MODIFICATION RESPONSE message.

[0222] If the PDCP SN Status Information IE is contained in the DRB To Setup List IE or the DRB To Modify List IE in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall take it into account and act as specified in TS 38.401 [2].

[0223] If the DL UP Parameters IE is contained in the DRB To Modify List IE in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall update the corresponding information. If the PDCP COUNT Reset IE is contained within the DRB To Modify List IE for a DRB of the PDU Session Resource To Modify List IE in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall, if supported, reset the PDCP COUNT value for this DRB (i.e. set its HFN and PDCP-SN to value “0”).

[0224] If the Cell Group To Add IE or the Cell Group To Modify IE or the Cell Group To Remove IE is contained in the DRB To Modify List IE in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall add or modify or remove the corresponding cell group.

[0225] If the PDU Session Resource DL Aggregate Maximum Bit Rate IE is contained in the PDU Session Resource To Setup List IE in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall replace the information in the UE context and use it when enforcing downlink traffic policing for the non GBR QoS flows for the concerned UE, as specified in TS 23.501

[0020] .

[0226] If the PDU Session Resource DL Aggregate Maximum Bit Rate IE is contained in the PDU Session Resource To Modify List IE in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall update the corresponding information.

[0227] If the SDAP Configuration IE is contained in the DRB To Modify List IE in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall update the corresponding information.

[0228] If the Flow Mapping Information IE is contained in the DRB To Modify List IE in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall update the corresponding information.

[0229] For each requested DRB, if the PDCP Duplication IE or Additional PDCP duplication Information IE is included in the PDCP Configuration IE contained in the BEARER CONTEXT MODIFICATION REQUEST message, then the gNB- CU-CP shall include two or more UP Transport Layer Information IES in the BEARER CONTEXT MODIFICATION REQUEST message, and the gNB-CU-UP shall, if supported, also include two or more UP Transport Layer Information IEs in the BEARER CONTEXT MODIFICATION RESPONSE message to support packet duplication. If only one cell group is included in the Cell Group Information IE for the concerned DRB, then the gNB-CU-UP shall consider that the first UP Transport Layer Information IE of these UP Transport Layer Information IEs is for the primary path. If more than one cell group is included in the Cell Group Information IE, then the gNB-CU-UP shall consider that the number of duplication tunnels for each cell group is indicated by the Number of tunnels IE, and that the first UP Transport Layer Information IE for each cell group is for the primary path or the split secondary path.

[0230] For a certain DRB which was allocated with two or more GTP-U tunnels, if such DRB is modified and given one GTP- U tunnel via the Bearer Context Modification (gNB-CU-CP initiated) procedure, i.e. only one UP Transport Layer Information per Cell Group ID is present in DL UP Parameters IE for the concerned DRB, then the gNB-CU-UP shall consider that PDCP duplication is deconfigured for this DRB. If such Bearer Context Modification (gNB-CU-CP initiated) procedure occurs, the Duplication Activation IE shall not be included for the concerned DRB.

[0231] If the New UL TNL Information Required IE is contained in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall include the new UP Transport Layer Information in the BEARER CONTEXT MODIFICATION RESPONSE message.

[0232] For each PDU session for which the Security Indication IE is included in the PDU Session Resource To Setup List IE or the Security Indication Modify IE is included in the PDU Session Resource To Modify List IE of the BEARER CONTEXT MODIFICATION REQUEST message, and the Integrity Protection Indication IE or Confidentiality Protection Indication IE is set to "preferred", then the gNB-CU-UP should, if supported, perform user plane integrity protection or ciphering, respectively, for the concerned PDU session and shall notify whether it performed the user plane integrity protection or ciphering by including the Integrity Protection Result IE or Confidentiality Protection Result IE, respectively, in the PDU Session Resource Setup List IE or the PDU Session Resource Modified List IE of the BEARER CONTEXT MODIFICATION RESPONSE message.

[0233] For each PDU session for which the Security Indication IE is included in the PDU Session Resource To Setup List IE or the Security Indication Modify IE is included in the PDU Session Resource To Modify List IE of the BEARER CONTEXT MODIFICATION REQUEST message, and the Integrity Protection Indication IE or Confidentiality Protection Indication IE is set to "required", then the gNB-CU-UP shall perform user plane integrity protection or ciphering, respectively, for the concerned PDU Session. If the gNB-CU-UP cannot perform the user plane integrity protection or ciphering, it shall reject the setup of the PDU Session Resources with an appropriate cause value.

[0234] For each PDU session for which the Security Indication IE is included in the PDU Session Resource To Setup List IE or the Security Indication Modify IE is included in the PDU Session Resource To Modify List IE of the BEARER CONTEXT MODIFICATION REQUEST message:

[0235] 13. - if the Integrity Protection Indication IE is set to "not needed", then the gNB-CU-UP shall not perform user plane integrity protection for the concerned PDU session;

[0236] 14. - if the Confidentiality Protection Indication IE is set to "not needed", then the gNB-CU-UP shall not perform user plane ciphering for the concerned PDU session.

[0237] For each PDU Session Resource, if the Network Instance IE is included in the PDU Session Resource To Setup List IE or the PDU Session Resource To Modify List IE in the BEARER CONTEXT MODIFICATION REQUEST message and the Common Network Instance IE is not included, the gNB-CU-UP shall, if supported, use it when selecting transport network resource as specified in TS 23.501

[0020] .

[0238] For each PDU session, if the Common Network Instance IE is included in the PDU Session Resource To Setup List IE or the PDU Session Resource To Modify List IE in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall, if supported, use it when selecting transport network resource as specified in TS 23.501

[0020] .

[0239] For each PDU session, if the Redundant NG UL UP Transport Layer Information IE is included in the PDU Session Resource To Setup List IE or the PDU Session Resource To Modify List IE in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall, if supported, include the Redundant NG DL UP Transport Layer Information IE in the PDU Session Resource Setup List IE or the PDU Session Resource Modified List IE in the BEARER CONTEXT MODIFICATION RESPONSE message.

[0240] If the Redundant Common Network Instance IE is included in the PDU Session Resource To Setup List IE or the PDU Session Resource To Modify List IE in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU- UP shall, if supported, use it when selecting transport network resource for the redundant transmission as specified in TS 23.501

[0020] .

[0241] For each PDU session for which the Redundant QoS Flow Indicator IE is included in QoS Flows Information To Be Setup IE contained in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall, if support, shall store and use it as specified in TS 23.501

[0020] .

[0242] For each PDU session, if the Redundant QoS Flow Indicator IE is set to false for all QoS flows, the gNB-CU-UP shall, if supported, stop the redundant transmission and release the redundant tunnel for the concerned PDU session as specified in TS 23.501

[0020] .

[0243] If the QoS Flow Mapping Indication IE is contained in the QoS Flow QoS Parameters List IE in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall, if supported, replace any previously received value and take it into account that only the uplink or downlink QoS flow is mapped to the DRB. If the Data Discard Required IE is contained in the BEARER CONTEXT MODIFICATION REQUEST message and the value is set to “Required”, the gNB-CU-UP shall consider that a RAN Paging Failure occurred for that UE. The gNB-CU-UP shall discard the user plane data for that UE and consider that the bearer context is still suspended.

[0244] If UE Inactivity Timer IE or PDU session Inactivity Timer IE or DRB Inactivity Timer IE is contained in BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall take it into account when perform inactivity monitoring.

[0245] If the S-NSSAI IE is contained in the PDU Session Resource To Modify List IE in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall store the corresponding information and replace any existing information.

[0246] If the DRB QoS IE is contained within the DRB To Setup List IE in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall, if supported, take it into account for each DRB, as specified in TS 28.552

[0022] ,

[0247] If the DRB QoS IE is contained within the DRB To Modify List IE in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall, if supported, replace any previously received value and take it into account for each DRB, as specifed in TS 28.552

[0022] .

[0248] If the gNB-DU-ID IE is contained in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU- UP shall store and replace any previous information received.

[0249] If the RAN UE ID IE is contained in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall store and replace any previous information received.

[0250] If the gNB-CU-UP receives a BEARER CONTEXT MODIFICATION REQUEST message including Activity Notification Level IE and its value does not match the current bearer context, the gNB-CU-UP shall ignore the Activity Notification Level IE and also the requested modification of inactivity timer.

[0251] For each successfully established DRB, the gNB-CU-UP shall provide, in the respective UL UP Parameters IE of the BEARER CONTEXT MODIFICATION RESPONSE, one UL UP Transport Layer Information Item per cell group entry contained in the respective Cell Group Information IE of the BEARER CONTEXT MODIFICATION REQUEST message.

[0252] If the Old QoS Flow List - UL End Marker expected IE is included in the PDU Session Resource To Modify List IE of the BEARER CONTEXT MODIFICATION REQUEST message for a DRB to be modified, the gNB-CU-UP shall consider that the source NG-RAN node has initiated QoS flow re-mapping and has not yet received SDAP end markers, as described in TS 38.300 [8]. The gNB-CU-UP shall consider that the Old QoS Flow List - UL End Marker expected IE only contains UL QoS flow information for QoS flows for which no SDAP end marker has been yet received on the source side.

[0253] For EN-DC, if the Subscriber Profde ID for RAT / Frequency priority IE is included in the BEARER CONTEXT MODIFICATION REQUEST, the gNB-CU-UP may use it to apply specific RRM policies as specified in TS 36.300

[0025] . If the Additional RRM Policy Index IE is included in the BEARER CONTEXT MODIFICATION REQUEST, the gNB-CU-UP may use it to apply specific RRM policies as specified in TS 36.300

[0025] .

[0254] If there is at least one DRB removed by the gNB-CU-UP, the gNB-CU-UP shall, if supported, include the Retainability Measurements Information IE in the BEARER CONTEXT MODIFICATION RESPONSE message, providing information on the removed DRB(s) for retainability measurements in the gNB-CU-CP, as described in TS 32.425

[0026] and TS 28.552

[0022] , If the TSC Traffic Characteristics IE is included in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall, if supported, take into account the corresponding information received in the TSC Traffic Characteristics IE.

[0255] For each QoS flow whose DRB has been successfully established or modified and the QoS Monitoring Request IE was included in the QoS Flow Level QoS Parameters IE contained in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall store this information, and, if supported, perform delay measurement and QoS monitoring, as specified in TS 23.501

[0020] . If the QoS Monitoring Reporting Frequency IE was included in the QoS Flow Level QoS Parameters IE contained in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall store this information, and, if supported, use it for RAN part delay reporting.

[0256] For each requested DRB, if the QoS Mapping Information IE is contained in the DL UP Parameters IE in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall use it to set DSCP and / or flow label fields in the downlink IP packets which are transmitted through the GTP tunnels indicated by the UP Transport Layer Information IE. The Diffserv code point (DSCP) marking is performed as specified in TS 38.474

[0028] .

[0257] If the Early Forwarding COUNT Request IE is contained in the DRB To Modify List IE in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall act as specified in TS 38.401 [2] and include the requested FIRST DL COUNT Value IE or DISCARD DL COUNT Value IE in the BEARER CONTEXT MODIFICATION RESPONSE message.

[0258] If the Early Forwarding COUNT Information IE is contained in the DRB To Modify List IE in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall take it into account and act as specified in TS 38.401 [2].

[0259] If the Ignore Mapping Rule Indication IE is contained within the DRB To Setup List IE for a DRB in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall, if supported, ignore the QoS flow mapping information indicated by the QoS Flows Information To Be Setup IE for the concerned DRB.

[0260] If the DAPS Request Information IE is included for a DRB to be modified in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall consider that the request concerns a DAPS handover for that DRB and, if admitted, act as specified in TS 38.300 [4].

[0261] If the Early Data Forwarding Indicator IE set to “stop” is contained in the DRB To Modify List IE in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall, if supported and if already initiated, stop the early data forwarding for the concerned DRB. If the DRB Data forwarding information IE containing the DL Data Forwarding IE is included together in the DRB To Modify List IE, the gNB-CU-UP shall consider that the stop is only for the early data forwarding initiated toward that forwarding TNL.

[0262] If the Data Forwarding Source IP Address IE is included in the DRB To Setup Modification List E-UTRAN IE or in the QoS Flow Level QoS Parameters IE within the PDU Session Resource To Setup Modification List IE and the PDU Session Resource To Modify List IE contained in the BEARER CONTEXT MODIFICATION REQUEST message, the gNB-CU-UP shall, if supported, store this information in the UE context and use it as part of its ACL functionality configuration actions, if such ACL functionality is deployed.

[0263] If the Data Forwarding Source IP Address IE is included in the DRB Setup Modification List E-UTRAN IE or in the Flow Setup List IE within the PDU Session Resource Setup Modification List IE and the PDU Session Resource Modified List IE of the BEARER CONTEXT MODIFICATION RESPONSE message, the gNB-CU-CP shall, if supported, store this information in the UE context and use it as part of its ACL functionality configuration actions, if such ACL functionality is deployed. If the Inactivity Information Request IE is contained in the BEARER CONTEXT MODIFICATION REQUEST, the gNB-CU-UP shall, if supported, include the UE Inactivity Information IE in the BEARER CONTEXT MODIFICATION RESPONSE message.

[0264] From TS 38..473 F1 Application Protocol (F1 API V15.16.0:

[0265] 8.3.1 UE Context Setup

[0266] 8.3.1.1 General

[0267] The purpose of the UE Context Setup procedure is to establish the UE Context including, among others, SRB, DRB, BH RLC channel, Uu Relay RLC channel, PC5 Relay RLC channel, and SL DRB configuration. The procedure uses UE-associated signalling.

[0268] 8.3.1.2 Successful Operation

[0269] Figure 9 or 8.3.1.2-1 : UE Context Setup Request procedure: Successful Operation

[0270] The gNB-CU initiates the procedure by sending UE CONTEXT SETUP REQUEST message to the gNB-DU. If the gNB-DU succeeds to establish the UE context, it replies to the gNB-CU with UE CONTEXT SETUP RESPONSE. If no UE-associated logical Fl -connection exists, the UE-associated logical Fl -connection shall be established as part of the procedure. Except for RACH based SDT and UE configured with BWP specific ServingCellMO, the gNB-CU shall perform RRC Reconfiguration or RRC connection resume to send UE to the RRC CONNECTED state as described in TS 38.331 181, and in this case, the CellGroupConfig IE shall transparently be signaled to the UE as specified in TS 38.331 181. In the cases of RACH based SDT procedure and UE configured with BWP specific ServingCellMO, the CellGroupConfig IE shall be ignored by the gNB-CU.

[0271] If the UE-CapabilityRAT-ContainerList IE is included in the UE CONTEXT SETUP REQUEST, the gNB-DU shall take this information into account for UE specific configurations.

[0272] If the ServingCellMO IE is included in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall configure ServingCellMO for the indicated SpCell accordingly.

[0273] If the ServingCellMO List IE is included in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, select ServingCellMO after determining the list of BWPs for the UE and include the list of servingCellMOs that have been encoded in CellGroupConfig IE as ServingCellMO-encoded-in-CGC List IE in the UE CONTEXT SETUP RESPONSE message.

[0274] If the Configured BWP List IE is included in the UE CONTEXT SETUP RESPONSE message, the gNB-CU shall, if supported, take it into account when requesting the gNB-DU for generating preconfigured measurement GAP for the indicated BWPs.

[0275] If the SpCell UL Configured IE is included in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall configure UL for the indicated SpCell accordingly.

[0276] If the SCell To Be Setup List IE is included in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall consider it as a list of candidate SCells to be set up. If the SCell UL Configured IE is included in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall configure UL for the indicated SCell accordingly. If the ServingCellMO IE is included in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall configure ServingCellMO for the indicated SCell accordingly. If the DRX Cycle IE is contained in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall use the provided value from the gNB-CU.

[0277] If the Non-Integer DRX Cycle IE is contained in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, use the provided value from the gNB-CU.

[0278] If the UL Configuration IE in DRB to Be Setup Item IE is contained in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall take it into account for UL scheduling.

[0279] If the SRB To Be Setup List IE is contained in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall act as specified in TS 38.401 [4]. If Duplication Indication IE is contained in the SRB To Be Setup List IE, the gNB-DU shall, if supported, setup two RLC entities for the indicated SRB. If the. Additional Duplication Indication IE is contained in the SRB To Be Setup List IE, the gNB-DU shall, if supported, setup the indicated RLC entities for the indicated SRB. If the SDT RLC Bearer Configuration IE is contained in the SRB To Be Setup List IE, the gNB-DU shall, if supported, use it for packet transmission belonging to the SDT SRB indicated by the SRB ID IE. If the SRB Mapping Info IE is contained in the SRB To Be Setup List IE, the gNB-DU shall, if supported, store the mapping information indicated in the SRB Mapping Info IE for the SRB identified by the SRB ID IE and the Uu Relay RLC channel identified by the SRB Mapping Info IE. The gNB-DU shall use the mapping information stored for the mapping of SRB data to Uu Relay RLC channel.

[0280] If the DRB To Be Setup List IE is contained in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall act as specified in TS 38.401 [4]. If the QoS Flow Mapping Indication IE is included in the DRB To Be Setup List IE for a QoS flow, the gNB-DU may take it into account that only the uplink or downlink QoS flow is mapped to the indicated DRB. If the SDT RLC Bearer Configuration IE is contained in the DRB To Be Setup List IE, the gNB-DU shall, if supported, use it for packet transmission belonging to the SDT DRB indicated by the DRB ID IE. If the DRB Mapping Info IE is contained in the DRB To Be Setup List IE, the gNB-DU shall, if supported, store the mapping information indicated in the DRB Mapping Info IE for the DRB identified by the DRB ID IE and the Uu Relay RLC channel identified by the DRB Mapping Info IE. The gNB-DU shall use the mapping information stored for the mapping of DRB data to Uu Relay RLC channel.

[0281] If the PSI based SDU Discard UL IE is included in the DRB To Be Setup List IE, the gNB-DU shall, if supported, take it into account to perform UL PSI based SDU discarding activation or deactivation for the indicated DRB as defined in TS 38.321

[0016] .

[0282] For each GBR DRB, if the Alternative QoS Parameters Sets IE is included in the GBR QoS Flow Information IE in the UE CONTEXT SETUP REQUEST message, gNB-DU shall, if supported, behave the same as the NG-RAN node in the PDU Session Resource Setup procedure, specified in TS 38.413 [3].

[0283] If the BH Information IE is included in the UL UP TNL Information to be setup List IE or the Additional PDCP Duplication TNL List IE for a DRB, the gNB-DU shall, if supported, use the indicated BAP Routing ID and BH RLC channel for transmission of the corresponding GTP-U packets to the lAB-donor, as specified in TS 38.340

[0030] .

[0284] If the BH RLC Channel To Be Setup List IE is included in the UE CONTEXT SETUP REQUEST message, the gNB- DU shall act as specified in TS 38.401 [4]. If the Traffic Mapping Information IE is included in the BH RLC Channel To Be Setup Item IES IE for a BH RLC Channel, the gNB-DU shall, if supported, process the Traffic Mapping Information IE as follows: if the IP to layer2 Traffic Mapping Info IE is included, the gNB-DU shall store the mapping information contained in the IP to layer2 Traffic Mapping Info To Add IE, if present, for the egress BH RLC channel identified by the BH RLC CH ID IE, and shall remove the previously stored mapping information as indicated by the IP to Icryer2 Mapping Traffic Info To Remove IE, if present. The gNB-DU shall use the mapping information stored for the mapping of IP traffic to layer 2, as specified in TS 38.340

[0030] . if the BAP layer BH RLC channel Mapping Info IE is included, the gNB-DU shall store the mapping information contained in the BAP layer BH RLC channel Mapping Info To Add IE, if present, for the egress or ingress BH RLC channel identified by the BH RLC CH ID IE, and shall remove the previously stored mapping information as indicated by the BAP layer BH RLC channel Mapping Info To Remove IE, if present. The gNB-DU shall use the mapping information stored when forwarding traffic on BAP sublayer, as specified in TS 38.340

[0030] .

[0285] If two UL UP TNL Information IES are included in UE CONTEXT SETUP REQUEST message for a DRB, gNB-DU shall include two DL UP TNL Information IEs in UE CONTEXT SETUP RESPONSE message and setup two RLC entities for the indicated DRB. gNB-CU and gNB-DU use the UL UP TNL Information IEs and DL UP TNL Information IEs to support packet duplication for intra-gNB-DU CA as defined in TS 38.470 [2]. The first UP TNL Information IE of the two UP TNL Information IEs is for the primary path.

[0286] If one or two Additional PDCP Duplication UP TNL Information IEs are included in the UE CONTEXT SETUP REQUEST message for a DRB, the gNB-DU shall, if supported, include one or two Additional PDCP Duplication UP TNL Information IEs in the UE CONTEXT SETUP RESPONSE message and setup one or two additional RLC entities for the indicated DRB. The gNB-CU and the gNB-DU use the Additional PDCP Duplication UP TNL Information IEs to support packet duplication for intra-gNB-DU CA as defined in TS 38.470 [2].

[0287] If Duplication Activation IE is included in the UE CONTEXT SETUP REQUEST message for a DRB, gNB-DU should take it into account when activating / deactivating CA based PDCP duplication for the DRB. If the RLC Duplication State List IE is included in the RLC Duplication Information IE contained in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, take it into account when activating / deactivating CA based PDCP duplication for the DRB with more than two RLC entities.

[0288] If DC Based Duplication Configured IE is included in the UE CONTEXT SETUP REQUEST message for a DRB, gNB-DU shall regard that DC based PDCP duplication is configured for this DRB if the value is set to be "true" and it should take the responsibility of PDCP duplication activation / deactivation. If DC Based Duplication Activation IE is included in the UE CONTEXT SETUP REQUEST message for a DRB, gNB-DU should take it into account when activating / deactivating DC based PDCP duplication for this DRB. If the RLC Duplication State List IE is included in the RLC Duplication Information IE contained in the UE CONTEXT SETUP REQUEST message for a DRB, the gNB- DU shall, if supported, take it into account when activating / deactivating DC based PDCP duplication for the DRB with more than two RLC entities. If the Primary Path Indication IE is included in the RLC Duplication Information IE, the gNB-DU shall, if supported, take it into account when performing DC based PDCP duplication for the DRB with more than two RLC entities.

[0289] If UL PDCP SN length IE is included in the UE CONTEXT SETUP REQUEST message for a DRB, gNB-DU shall, if supported, store this information and use it for lower layer configuration.

[0290] For EN-DC operation, and if the Subscriber Profde ID for RAT / Frequency priority IE is received from an MeNB, the UE CONTEXT SETUP REQUEST message shall contain the Subscriber Profile ID for RAT / Frequency priority IE. If the Additional RRM Policy Index IE is received from an MeNB, the UE CONTEXT SETUP REQUEST message shall, if supported, contain the Additional RRM Policy Index IE. The gNB-DU shall store the received Subscriber Profile ID for RAT / Frequency priority in the UE context and use it as defined in TS 36.300

[0020] . The gNB-DU shall, if supported, store the received Additional RRM Policy Index in the UE context and use it as defined in TS 36.300

[0020] .

[0291] If the Index to RAT / Frequency Selection Priority IE is available at the gNB-CU, the Index to RAT / Frequency Selection Priority IE shall be included in the UE CONTEXT SETUP REQUEST. The gNB-DU may use it for RRM purposes. The gNB-DU shall report to the gNB-CU, in the UE CONTEXT SETUP RESPONSE message, the result for all the requested DRBs, SRBs, BH RLC channels, PC5 Relay RLC channels, and SL DRBs in the following way:

[0292] A list of DRBs which are successfully established shall be included in the DRB Setup List IE;

[0293] A list of DRBs which failed to be established shall be included in the DRB Failed to Setup List IE;

[0294] A list of SRBs which failed to be established shall be included in the SRB Failed to Setup List IE.

[0295] A list of successfully established SRBs with logical channel identities for primary path shall be included in the SRB Setup List IE only if CA based PDCP duplication is initiated for the concerned SRBs.

[0296] A list of BH RLC channels which are successfully established shall be included in the BH RLC Channel Setup List IE;

[0297] A list of BH RLC channels which failed to be established shall be included in the BH RLC Channel Failed to be Setup List IE;

[0298] A list of SL DRBs which are successfully established shall be included in the SL DRB Setup List IE;

[0299] A list of SL DRBs which failed to be established shall be included in the SL DRB Failed to Setup List IE.

[0300] A list of Uu Relay RLC channels which are successfully established shall be included in the Uu RLC Channel Setup List IE;

[0301] A list of Uu Relay RLC channels which failed to be established shall be included in the Uu RLC Channel Failed to be Setup List IE;

[0302] A list of PC5 Relay RLC channels which are successfully established shall be included in the PC5 RLC Channel Setup List IE;

[0303] A list of PC5 Relay RLC channels which failed to be established shall be included in the PC5 RLC Channel Failed to be Setup List IE;

[0304] If Duplication Indication IE in SL DRB To Be Setup List IE is contained in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, generate two PC5 RLC bearer configurations for the indicated SL DRB.

[0305] When the gNB-DU reports the unsuccessful establishment of a DRB or SRB or SL DRB or a BH RLC channel or a PC5 Relay RLC channel, the cause value should be precise enough to enable the gNB-CU to know the reason for the unsuccessful establishment.

[0306] For EN-DC operation, the gNB-CU shall include in the UE CONTEXT SETUP REQUEST the E-UTRAN QoS IE. The allocation of resources according to the values of the Allocation and Retention Priority IE included in the E-UTRAN QoS IE shall follow the principles described for the E-RAB Setup procedure in TS 36.413

[0015] .

[0307] For NG-RAN operation, the gNB-CU shall include in the UE CONTEXT SETUP REQUEST the DRB Information IE.

[0308] For DC operation, the CG-Configlnfo IE shall be included in the CU to DU RRC Information IE at the gNB acting as secondary node. If the CG-Configlnfo IE is included in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall regard it as a reconfiguration with sync as defined in TS 38.331 [8].

[0309] For sidelink operation, the CG-Configlnfo IE shall be included in the CU to DU RRC Information IE if the gNB-CU receives sidelink related UE information from UE. If the CG-Configlnfo IE is included in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall regard it as an indication of V2X sidelink information or NR sidelink information as defined in TS 38.331 [8]. If the HandoverPreparationlnformation IE is included in the CU to DU RRC Information IE in the UE CONTEXT SETUP REQUEST message, the gNB-DU of the gNB acting as master node shall regard it as a reconfiguration with sync as defined in TS 38.331 [8]. The gNB-CU shall only initiate the UE Context Setup procedure for handover or secondary node addition when at least one DRB is setup for the UE, or at least one BH RLC channel is set up for IAB- MT. If the HandoverPreparationlnformation IE containing the sidelink related UE information is included in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall regard it as an indication of V2X sidelink information or NR sidelink information as defined in TS 38.331 [8].

[0310] If the received CU to DU RRC Information IE does not include source cell group configuration, the gNB-DU shall generate the cell group configuration using full configuration. Otherwise, delta configuration is allowed.

[0311] If the gNB-CU includes the SMTC information of the measured frequency(ies) in the MeasurementTimingConfiguration IE of the CU to DU RRC Information IE that is included in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall generate the measurement gaps based on the received SMTC information. Then the gNB-DU shall send the measurement gaps information to the gNB-CU in the MeasGapConfig IE of the DU to CU RRC Information IE that is included in the UE CONTEXT SETUP RESPONSE message.

[0312] If the MeasConfig IE is included in the CU to DU RRC Information IE in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall deduce that changes to the measurements configuration need to be applied. If the measObjectToAddModList IE is included in the MeasConfig IE, then the frequencies added in such IE are to be activated. Then the gNB-DU shall decide if measurement gaps are needed or not and, if needed, the gNB-DU shall send the measurement gaps information to the gNB-CU in the MeasGapConfig IE of the DU to CU RRC Information IE that is included in the UE CONTEXT SETUP RESPONSE message. If the measObjectToRemoveList IE is included in the MeasConfig IE, the gNB-DU shall ignore it.

[0313] If the NeedForGapsInfoNR IE is included in the CU to DU RRC Information IE in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, use it as described in TS 38.331 [8]. If the NeedForGapNCSG- InfoNR IE is included in the CU to DU RRC Information IE in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, use it as described in TS 38.331 [8].

[0314] If the NeedForGapNCSG-InfoEUTRA IE is included in the CU to DU RRC Information IE in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, use it as described in TS 38.331 [8].

[0315] If the NeedForlnterruptionlnfoNR IE is included in the CU to DU RRC Information IE in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, use it as described in TS 38.331 [8].

[0316] For EN-DC operation, if the gNB-CU includes the Resource Coordination Transfer Information IE in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, use it for the purpose of resource coordination. If the Ignore PRACH Configuration IE is present and set to "true" the E-UTRA PRACH Configuration IE in the UE CONTEXT SETUP REQUEST message shall be ignored. If the gNB-CU received the MeNB Resource Coordination Information as defined in TS 36.423 [9], it shall transparently transfer it to the gNB-DU via the Resource Coordination Transfer Container IE in the UE CONTEXT SETUP REQUEST message. The gNB-DU shall use the information received in the Resource Coordination Transfer Container IE for reception of MeNB Resource Coordination Information at the gNB acting as secondary node as described in TS 36.423 [9]. If the Resource Coordination E-UTRA Cell Information IE is included in the Resource Coordination Transfer Information IE, the gNB- DU shall store the information replacing previously received information for the same E-UTRA cell, and use the stored information for the purpose of resource coordination.

[0317] For NGEN-DC or NE-DC operation, if the gNB-CU includes the Resource Coordination Transfer Information IE in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, use it for the purpose of resource coordination. If the gNB-CU received the MR-DC Resource Coordination Information as defined in TS 38.423

[0028] , it shall transparently transfer it to the gNB-DU via the Resource Coordination Transfer Container IE in the UE CONTEXT SETUP REQUEST message. The gNB-DU shall use the information received in the Resource Coordination Transfer Container IE for reception of MR-DC Resource Coordination Information at the gNB as described in TS 38.423

[0028] .

[0318] The UEAssistancelnformation IE shall be included in CU to DU RRC Information IE in the UE CONTEXT SETUP REQUEST message if the gNB-CU received this IE from the UE; if the UEAssistancelnformation IE is included in the CU to DU RRC Information IE in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, take it into account when configuring resources for the UE.

[0319] The UEAssistancelnformationEUTRA IE shall be included in CU to DU RRC Information IE in the UE CONTEXT SETUP REQUEST message if the gNB-CU received this IE from the UE; if the UEAssistancelnformationEUTRA IE is included in the CU to DU RRC Information IE in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, take it into account when configuring LTE sidelink resources for the UE.

[0320] If the Resource Coordination Transfer Container IE is included in the UE CONTEXT SETUP RESPONSE, the gNB- CU shall transparently transfer this information for the purpose of resource coordination as described in TS 36.423 [9], TS 38.423

[0028] .

[0321] If the Masked IMEISV IE is contained in the UE CONTEXT SETUP REQUEST message the gNB-DU shall, if supported, use it to determine the characteristics of the UE for subsequent handling.

[0322] If the SCell Failed To Setup List IE is contained in the UE CONTEXT SETUP RESPONSE message, the gNB-CU shall regard the corresponding SCell(s) failed to be set up with an appropriate cause value for each SCell failed to setup.

[0323] If the Inactivity Monitoring Request IE is contained in the UE CONTEXT SETUP REQUEST message, gNB-DU may consider that the gNB-CU has requested the gNB-DU to perform UE inactivity monitoring. If the Inactivity Monitoring Response IE is contained in the UE CONTEXT SETUP RESPONSE message and set to "Not-supported", the gNB-CU shall consider that the gNB-DU does not support UE inactivity monitoring for the UE.

[0324] If the ServCelllnfoList IE is included in the DU to CU RRC Information IE contained in the UE CONTEXT SETUP RESPONSE message, the gNB-CU shall take it into account to generate the content of inter-node RRC message, i.e., CG-Config or CG-Configlnfo, as described in TS 38.331 [8].

[0325] If the Full Configuration IE is contained in the UE CONTEXT SETUP RESPONSE message, the gNB-CU shall consider that the gNB-DU has generated the CellGroupConfig IE using full configuration.

[0326] If the C-RNTI IE is included in the UE CONTEXT SETUP RESPONSE, the gNB-CU shall consider that the C-RNTI has been allocated by the gNB-DU for this UE context.

[0327] The UE Context Setup Procedure is not used to configure SRBO.

[0328] If the UE CONTEXT SETUP REQUEST message contains the RRC-Container IE, the gNB-DU shall send the corresponding RRC message to the UE via SRB1.

[0329] If the Notification Control IE is included in the DRB to Be Setup List IE contained in the UE CONTEXT SETUP REQUEST message and it is set to active, the gNB-DU shall, if supported, monitor the QoS of the DRB and notify the gNB-CU if the QoS cannot be fulfilled any longer or if the QoS can be fulfilled again. The Notification Control IE can only be applied to GBR bearers.

[0330] If the UL PDU Session Aggregate Maximum Bit Rate IE is included in the QoS Flow Level QoS Parameters IE contained in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall store the received UL PDU Session Aggregate Maximum Bit Rate and use it when enforcing uplink traffic policing for non-GBR Bearers for the concerned UE as specified in TS 23.501

[0021] .

[0331] The gNB-DU shall store the received gNB-DU UE Aggregate Maximum Bit Rate Uplink and use it for non-GBR Bearers for the concerned UE.

[0332] If the UE CONTEXT SETUP REQUEST message contains the QoS Flow Mapping Indication IE, the gNB-DU may take it into account that only the uplink or downlink QoS flow is mapped to the DRB.

[0333] If the UE CONTEXT SETUP REQUEST message contains the New gNB-CU UE F1AP ID IE, the gNB-DU shall, if supported, replace the value received in the gNB-CU UE F1AP ID IE by the value of the New gNB-CU UE F1AP ID and use it for further signalling.

[0334] If the RAN UE ID IE is contained in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall store and replace any previous information received.

[0335] If the Trace Activation IE is included in the UE CONTEXT SETUP REQUEST message the gNB-DU shall, if supported, initiate the requested trace function as described in TS 32.422

[0029] .

[0336] In particular, the gNB-DU shall, if supported: if the Trace Activation IE includes the MDT Activation IE set to "Immediate MDT and Trace", initiate the requested trace session and MDT session as described in TS 32.422

[0029] ; if the Trace Activation IE includes the MDT Activation IE set to "Immediate MDT Only", initiate the requested MDT session as described in TS 32.422

[0029] and the gNB-DU shall ignore Interfaces To Trace IE, and Trace Depth IE. If the Management Based MDT PLMN List IE is contained in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, store the received information in the UE context, and use this information to allow subsequent selection of the UE for management based MDT defined in TS 32.422

[0029] .

[0337] For each QoS flow whose DRB has been successfully established and the QoS Monitoring Request IE was included in the QoS Flow Level QoS Parameters IE contained in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall store this information, and, if supported, perform delay measurement and QoS monitoring, as specified in TS 23.501

[0021] ,

[0338] If the UE CONTEXT SETUP REQUEST message contains the Configured BAP Address IE, the gNB-DU shall, if supported, store this BAP address configured for the corresponding child lAB-node and use it as specified in TS 38.340

[0030] ,

[0339] If the BAP Control PDU Channel IE is included in the BHRLC Channel to be Setup List IE, the gNB-DU shall, if supported, consider that the configured BH RLC channel can be used to transmit BAP Control PDUs, and use this BH RLC channel as specified in TS 38.340

[0030] .

[0340] If the Fl-C Transfer Path IE is included in UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, take it into account.

[0341] If the NR V2X Services Authorized IE is contained in the UE CONTEXT SETUP REQUEST message and it contains one or more lEs set to "authorized", the gNB-DU node shall, if supported, consider that the UE is authorized for the relevant service(s).

[0342] If the LTE V2X Services Authorized IE is contained in the UE CONTEXT SETUP REQUEST message and it contains one or more lEs set to "authorized", the gNB-DU node shall, if supported, consider that the UE is authorized for the relevant service(s). If the NR UE Sidelink Aggregate Maximum Bit Rate IE is contained in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, use it for the concerned UE's sidelink communication in network scheduled mode for NR V2X services.

[0343] If the LTE UE Sidelink Aggregate Maximum Bit Rate IE is contained in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, use it for the concerned UE's sidelink communication in network scheduled mode for LTE V2X services.

[0344] If the PC5 Link Aggregate Bit Rate IE is contained in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, use it for the concerned UE's sidelink communication in network scheduled mode for NR V2X services as defined in TS 23.287

[0040] .

[0345] If the NR A2X Services Authorized IE is contained in the UE CONTEXT SETUP REQUEST message and it contains one or more IES set to "authorized", the gNB-DU node shall, if supported, consider that the UE is authorized for the relevant service(s).

[0346] If the LTE A2X Services Authorized IE is contained in the UE CONTEXT SETUP REQUEST message and it contains one or more IEs set to "authorized", the gNB-DU node shall, if supported, consider that the UE is authorized for the relevant service(s).

[0347] If the NR UE Sidelink Aggregate Maximum Bit Rate for A2X IE is contained in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, use it for the concerned UE's sidelink communication in network scheduled mode for NR A2X services.

[0348] If the LTE UE Sidelink Aggregate Maximum Bit Rate for A2X IE is contained in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, use it for the concerned UE's sidelink communication in network scheduled mode for LTE A2X services.

[0349] If the TSC Traffic Characteristics IE is included in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, take into account the corresponding information received in the TSC Traffic Characteristics IE. If the RAN Feedback Type IE is included in the TSC Assistance Information Uplink IE of the TSC Traffic Characteristics IE, the gNB-DU shall, if supported, take this information into account when determining the feedback to provide in the TSC Traffic Characteristics Feedback IE in the UE CONTEXT SETUP RESPONSE message.

[0350] If the Conditional Inter-DU Mobility Information IE is included in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall consider that the request concerns a conditional handover, conditional PSCell addition, conditional PSCell change, or subsequent CPAC for the included SpCell ID IE and shall include it as the Requested Target Cell ID IE in the UE CONTEXT SETUP RESPONSE message. The gNB-DU shall regard it as a reconfiguration with sync as defined in TS 38.331 [8].

[0351] If the Target gNB-DU UE F1AP ID IE is contained in the Conditional Inter-DU Mobility Information IE included in the UE CONTEXT SETUP REQUEST message, then the gNB-DU shall replace the existing prepared conditional handover, conditional PSCell addition or conditional PSCell change, or subsequent CPAC identified by the Target gNB- DU UE F1AP ID IE and the SpCell ID IE.

[0352] If the Serving NID IE is contained in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall combine the Serving NID IE with the Serving PLMN IE to identify the serving NPN, and may take it into account for UE context establishment.

[0353] If the Estimated Arrival Probability IE is contained in the Conditional Inter-DU Mobility Information IE included in the UE CONTEXT SETUP REQUEST message, then the gNB-DU may use the information to allocate necessary resources for the UE. If the S-CPAC Request IE is included within the Conditional Inter-DU Mobility Information IE in the UE CONTEXT SETUP REQUEST message and is set to "initiation", the gNB-DU shall, if supported, consider that the procedure is triggered for S-CPAC preparation.

[0354] If for a given E-RAB for EN-DC operation the ENB DL Transport Layer Address IE is included in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, use it as part of its ACL functionality configuration actions, if such ACL functionality is deployed.

[0355] If for a given Qos flow for NG-RAN operation the PDCP Terminating Node DL Transport Layer Address IE is included in the UE CONTEXT SETUP REQUEST message, then the gNB-DU shall, if supported, use it as part of its ACL functionality configuration actions, if such ACL functionality is deployed.

[0356] If the Fl-C Transfer Path NRDC IE is included in UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, take it into account.

[0357] If the MDT Polluted Measurement Indicator IE is included in the UE CONTEXT SETUP REQUEST, the gNB-DU shall take this information into account as specified in TS 38.401 [4].

[0358] If the SCG Activation Request IE is included in the UE CONTEXT SETUP REQUEST message, the gNB-DU may use it to configure SCG resources as specified in TS 37.340 [7], and if supported, shall include the SCG Activation Status IE in the UE CONTEXT SETUP RESPONSE message. If the SCG Activation Request IE in the UE CONTEXT SETUP REQUEST message is set to “Activate SCG”, the gNB-DU shall activate the SCG resources and set the SCG Activation Status IE in the UE CONTEXT SETUP RESPONSE message to “SCG Activated”.

[0359] If the Old CG-SDT Session Info IE is included in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, retrieve the old CG-SDT resource configuration and old UE context based on the indicated gNB-CU Fl AP UE ID and gNB-DU Fl AP UE ID.

[0360] If the 5G ProSe Authorized IE is contained in the UE CONTEXT SETUP REQUEST message and it contains one or more lEs set to "authorized", the gNB-DU node shall, if supported, consider that the UE is authorized for the relevant service(s).

[0361] If the 5G ProSe UE PC5 Aggregate Maximum Bit Rate IE is contained in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, use it for the concerned UE's sidelink communication in network scheduled mode for 5G ProSe services.

[0362] If the 5G ProSe PC5 Link Aggregate Bit Rate IE is contained in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, use it for the concerned UE's sidelink communication in network scheduled mode for 5G ProSe services as defined in TS 23.304

[0044] .

[0363] If the PC5 RLC Channel To Be Setup List IE is contained in the UE CONTEXT SETUP REQUEST message, the gNB- DU shall, if supported, act as specified in TS 38.401 [4]. gNB-DU generates the PC5 Relay RLC channel configurations for a L2 U2N Remote UE, a L2 U2U Remote UE or a L2 U2U Relay UE.

[0364] If the Path Switch Configuration IE is contained in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, use it to configure the path switch from direct path to indirect path as specified in TS 38.401 [4] or from indirect path to indirect path as specified in TS 38.331 [8].

[0365] If the MUSIM-GapConfig IE is contained in the CU to DU RRC Information IE included in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, decide to use this IE for MUSIM gap configuration or select another one based on the received UEAssistancelnformation IE. If gNB-DU selects a different MUSIM gap configuration from received UEAssistancelnformation IE, then it shall include the selected MUSIM gap information to the gNB-CU in the MUSIM-GapConfig IE of the DU to CU RRC Information IE that is included in the UE CONTEXT SETUP RESPONSE message.

[0366] If MUSIM-GapConfig IE is not contained in the CU to DU RRC Information IE, then gNB-DU shall, if supported, send the selected MUSIM gap configuration based on the received UEAssistancelnformation IE, to the gNB-CU in the MUSIM-GapConfig IE of the DU to CU RRC Information IE that is included in the UE CONTEXT SETUP RESPONSE message. When MUSIM-GapConfig IE is received, the gNB-CU should use this value.

[0367] If the gNB-DU UE Slice Maximum Bit Rate List IE is included in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, store and use the information for the uplink traffic policing for each concerned slice as specified in TS 23.501

[0021] .

[0368] If the Multicast MBS Session Setup List IE is contained in the UE CONTEXT SETUP REQUEST message the gNB-DU shall, if supported, store and use the information for configuring MBS Session Resources, if applicable.

[0369] If the UE Multicast MRB To Be Setup List IE is contained in the UE CONTEXT SETUP REQUEST message, the gNB- DU shall, if supported, take it into account for configuring MBS Session Resources, if applicable. And if the MBS PTP Retransmission Tunnel Required IE is included in the UE Multicast MRB to Be Setup Item IES IE, the gNB-DU shall, if supported trigger the establishment of the MBS PTP Retransmission Fl-U tunnel. If the MBS PTP Forwarding Tunnel Required Information IE is included in the UE Multicast MRB to Be Setup Item IEs IE, the gNB-DU shall, if supported trigger the establishment of the MBS PTP Forwarding Fl-U tunnel. If the Source MRB ID IE is included in the UE Multicast MRB to Be Setup Item IEs IE, the DU shall, if supported, use it to identify the MRB configuration as provided to the UE in the source cell and take it into account for configuring MBS Session Resources.

[0370] If the Dedicated SI Delivery Indication IE is included in the UE CONTEXT SETUP RESPONSE message, the gNB- CU shall, if supported, take it into account for the system information delivery to the UE as described in TS 38.331 [8].

[0371] If the PDU Set QoS Parameters IE is included in the QoS Flow Level QoS Parameters IE contained in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, store this information and use it as specified in TS 23.501

[0021] ,

[0372] If the ECN Marking or Congestion Information Reporting Request IE is included in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, use it accordingly for the specific DRB. If the ECN Marking or Congestion Information Reporting Status IE is included in the UE CONTEXT SETUP RESPONSE message, the gNB- CU shall, if supported, use it to deduce if ECN marking or congestion information reporting is active or not active.

[0373] If the InterFrequencyConfig-NoGap IE is included in the DU to CU RRC Information IE contained in the UE CONTEXT SETUP RESPONSE message, the gNB-CU shall, if supported, use it as described in TS 38.331 [8].

[0374] If the ul-GapFR2-Config IE is contained in the DU to CU RRC Information IE that is included in the UE CONTEXT SETUP RESPONSE message, the gNB-CU shall, if supported, use it as described in TS 38.331 [8].

[0375] If the TwoPHRModeMCG IE or the TwoPHRModeSCG IE is contained in the DU to CU RRC Information IE that is included in the UE CONTEXT SETUP RESPONSE message, the gNB-CU shall, if supported, use this value as described in TS 38.331 [8].

[0376] If the MBSInterestlndication IE is included in the CU to DU RRC Information IE in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, take it into account when configuring resources for the UE.

[0377] If the ncd-SSB-RedCapInitialBWP-SDT IE is contained in the DU to CU RRC Information IE that is included in the UE CONTEXT SETUP RESPONSE message, the gNB-CU shall, if supported, use it as described in TS 38.331 [8]. If the Network Controlled Repeater Authorized IE is contained in the UE CONTEXT SETUP REQUEST message and it is set to "authorized", the gNB-DU node shall, if supported, consider that the UE is authorized as Network Controlled Repeater.

[0378] If the musim-CapabilityRestrictionlndication IE is included in the CU to DU RRC Information IE in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, use it as described in TS 38.331 [8].

[0379] If the LTM Indicator IE set to "true" is contained in the LTM Information Setup IE included in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, consider that the request concerns LTM for the included SpCell ID IE and shall include it as the Requested Target Cell ID IE in the UE CONTEXT SETUP RESPONSE message. The gNB-DU shall regard it as a reconfiguration with sync as defined in TS 38.331 [8].

[0380] If the Request for Lower Layer Configuration IE set to "true" is contained within the Reference Configuration IE in the LTM Information Setup IE included in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, provide the lower layer configuration in the Reference Configuration Information IE in the LTM Configuration!!! in the UE CONTEXT SETUP RESPONSE message for the gNB-CU to generate the LTM reference configuration.

[0381] If the Reference Configuration Information IE is contained within the Reference Configuration IE in the LTM Information Setup IE included in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, take it into account for generating the LTM lower layer configuration.

[0382] If the CSI Resource Configuration is contained in the LTM Information Setup IE included in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, use it to generate the LTM CSI reporting configuration(s) in the CellGroupConfig IE for the requested LTM candidate cell.

[0383] If the LTM Configuration ID Mapping List IE is contained in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, consider this as the mapping information for the LTM candidate cell(s).

[0384] If the Early Sync Information Request IE is included in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, include the Early Sync Information IE of the accepted candidate cell for early TA acquisition (early UL synchronisation), in the UE CONTEXT SETUP RESPONSE message. If the Early UL Sync Configuration IE is included in the UE CONTEXT SETUP RESPONSE message, the gNB-CU shall, if supported, consider it as the generated early UL sync information from the accepted candidate cell in the gNB-DU. If the Early UL Sync Configuration for SUL IE is included in the UE CONTEXT SETUP RESPONSE message, the gNB-CU shall, if supported, consider it as the generated early UL sync information for SUL from the accepted candidate cell in the gNB- DU.

[0385] If the LTM Configuration IE is included in the UE CONTEXT SETUP RESPONSE message, the gNB-CU shall, if supported, consider it as the generated configuration for LTM from the accepted candidate cell in the candidate gNB- DU.

[0386] If the Complete Candidate Configuration Indicator IE set to "complete" is contained in the LTM Configuration IE included in the UE CONTEXT SETUP RESPONSE message, the gNB-CU shall, if supported, consider that the LTM candidate configuration is a complete candidate configuration.

[0387] If the Direct Path Addition IE is contained in the Path Addition Information IE which is included in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, consider that the request concerns the direct path addition for the included SpCell ID IE as specified in TS 38.401 [4] and regard it as a reconfiguration with sync as defined in TS 38.331 [8]. If the Indirect Path Addition IE is contained in the Path Addition Information IE which is included in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, consider that the request concerns the indirect path addition for the MP Remote UE using PC5 link and use it as specified in TS 38.401 [4].

[0388] If the N3C Indirect Path Addition IE is contained in the Path Addition Information IE, the gNB-DU shall, if supported, consider that the request concerns the indirect path addition for the MP Remote UE using N3C and use it as specified in TS 38.401 [4],

[0389] If the S-CPAC Lower Layer Reference Config Request IE set to "true" is contained in the Conditional Inter-DU Mobility Information IE included in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, provide the lower layer configuration in the Reference Configuration Information IE in the S-CPAC Configuration IE in the UE CONTEXT SETUP RESPONSE message for the gNB-CU to generate the S-CPAC reference configuration.

[0390] If the Complete Candidate Configuration Indicator IE set to "complete" is contained in the S-CPAC Configuration IE included in the UE CONTEXT SETUP RESPONSE message, the gNB-CU shall, if supported, consider that the S- CPAC candidate configuration is a complete candidate configuration.

[0391] If the musim-CandidateBandList IE is included in the CU to DU RRC Information IE in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, use it for temporary capability restriction.

[0392] If the DL LBT Failure Information Request IE is included in the UE CONTEXT SETUP REQUEST message, the gNB- DU shall, if supported, consider that the gNB-CU has requested the DL LBT failure information of the UE in the target cell during handover, and act as specified in TS 38.401 [4].

[0393] If the Ranging and Sidelink Positioning Service Information IE is contained in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall, if supported, take it into account for the UE’s Ranging and Sidelink Positioning service.

[0394] 8.3.4 UE Context Modification (gNB-CU initiated)

[0395] 8.3.4.1 General

[0396] The purpose of the UE Context Modification procedure is to modify the established UE Context, e.g., establishing, modifying and releasing radio resources or sidelink resources. This procedure is also used to command the gNB-DU to stop data transmission for the UE for mobility (see TS 38.401 [4]). The procedure uses UE-associated signalling.

[0397] 8.3.4.2 Successful Operation

[0398] Figure 10 or Fig. 8.3.4.2-1: UE Context Modification procedure. Successful operation

[0399] The UE CONTEXT MODIFICATION REQUEST message is initiated by the gNB-CU.

[0400] Upon reception of the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall perform the modifications, and if successful reports the update in the UE CONTEXT MODIFICATION RESPONSE message.

[0401] If the SpCell ID IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall replace any previously received value and regard it as a reconfiguration with sync as defined in TS 38.331 [8]. If the ServCelllndex IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall take this into account for the indicated SpCell. If the SpCell UL Configured IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall configure UL for the indicated SpCell accordingly. If the servingCellMO IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall configure servingCellMO for the indicated SpCell accordingly. If the servingCellMO List IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, configure servingCellMO after determining the list of BWPs for the UE and include the list of servingCellMOs that have been encoded in CellGroupConfig IE as ServingCellMO-encoded-in-CGC List IE in the UE CONTEXT MODIFICATION RESPONSE message.

[0402] If the Configured BWP List IE is included in the UE CONTEXT MODIFICATION RESPONSE message the gNB-CU shall, if supported, take it into account when requesting the gNB-DU for generating preconfigured measurement GAP for the indicated BWPs.

[0403] If the Preconfigured Measurement GAP Request IE is present in the CU to DU RRC Information IE in the UE CONTEXT MODIFICATON REQUEST message, the gNB-DU shall, if supported, consider that the content of the previous CellGroupConfig IE was not sent to the UE and generate the pre-configured measurement GAP for the indicated BWPs in the MeasConfig IE. If the gNB-DU successfully generates pre-configured measurement GAP for the indicated BWPs, the gNB-DU shall update the CellGroupConfig IE with the content of the previous CellGroupConfig IE and the preconfigured measurement GAP configuration in the UE CONTEXT MODIFICATION RESPONSE message.

[0404] If the SCell To Be Setup List IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall consider it as a list of candidate SCells to be set up. If the SCell To Be Setup List IE is included in the UE CONTEXT MODIFICATION REQUEST message and the indicated SCell(s) are already setup, the gNB-DU shall replace any previously received value. If the SCell UL Configured IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall configure UL for the indicated SCell accordingly. If the servingCellMO IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall configure servingCellMO for the indicated SCell accordingly.

[0405] If the SCell To Be Removed List IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB- DU shall consider it as a list of SCells to be removed.

[0406] If the DRX Cycle IE is contained in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall use the provided value from the gNB-CU. If the DRX configuration indicator IE is contained in the UE CONTEXT MODIFICATION REQUEST message and set to "release", the gNB-DU shall release DRX configuration.

[0407] If the Non-Integer DRX Cycle IE is contained in the UE CONTEXT MODIFICATION REQUEST message, the gNB- DU shall, if supported, use the provided value from the gNB-CU.

[0408] If the SL DRX Cycle list IE is contained in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, use the provided value from the gNB-CU for the indicated RX UE of this UE. If the SL DRX configuration indicator IE is contained in the UE CONTEXT MODIFICATION REQUEST message and set to "release", the gNB-DU shall, if supported, release SL DRX configuration for the indicated RX UE of this UE.

[0409] If the SRB To Be Setup List IE is contained in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall act as specified in the TS 38.401 [4], and replace any previously received value. If Duplication Indication IE is contained in the SRB To Be Setup List IE, the gNB-DU shall, if supported, setup two RLC entities for the indicated SRB if the value is set to be "true", or delete the RLC entity of secondary path if the value is set to be "false". If the Additional Duplication Indication IE is contained in the SRB To Be Setup List IE, the gNB-DU shall, if supported, setup the indicated RLC entities for the indicated SRB. If the SRB Mapping Info IE is contained in the SRB To Be Setup List IE, the gNB-DU shall, if supported, store the mapping information indicated in the SRB Mapping Info IE for the SRB identified by the SRB ID IE and the Uu Relay RLC channel identified by the SRB Mapping Info. The gNB- DU shall use the mapping information stored for the mapping of SRB data to Uu Relay RLC channel. If the Path Addition Information IE and the SRB Mapping Info IE are both contained in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, setup one RLC entity if necessary for the direct path and map the indicated SRB to the Uu Relay RLC channel based on the SRB Mapping Info IE. If the Duplication Indication IE and SRB Mapping Info IE are both contained in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, setup one RLC entity for the direct path if the value is set to be "true", and map the indicated SRB to the Uu Relay RLC channel based on the SRB Mapping Info IE. If the Additional Duplication Indication IE and SRB Mapping Info IE are both contained in the SRB To Be Setup List IE, the gNB-DU shall, if supported, setup the indicated RLC entities for the indicated SRB, and map the indicated SRB to the Uu Relay RLC channel based on the SRB Mapping Info IE. The number of RLC entities to be set up is the indicated value of Additional Duplication Indication IE minus 1.

[0410] If the DRB To Be Setup List IE is contained in the UE CONTEXT MODIFICATION REQUEST message, the gNB- DU shall act as specified in the TS 38.401 [4]. If the DRB Mapping Info IE is contained in the DRB To Be Setup List IE, the gNB-DU shall, if supported, store the mapping information indicated in the DRB Mapping Info IE, if present, for the DRB identified by the DRB ID IE and the Uu Relay RLC channel identified by the DRB Mapping Info. The gNB-DU shall use the mapping information stored for the mapping of DRB data to Uu Relay RLC channel.

[0411] If the PSI based SDU Discard UL IE is included in the DRB To Be Setup List IE or the DRB To Be Modified List IE, the gNB-DU shall, if supported, take it into account to perform UL PSI based SDU discarding activation or deactivation for the indicated DRB as defined in TS 38.321

[0016] .

[0412] If the BH Information IE is included in the UL UP TNL Information to be setup List IE or the Additional PDCP Duplication TNL List IE for a DRB, the gNB-DU shall, if supported, use the indicated BAP Routing ID and BH RLC channel for transmission of the corresponding GTP-U packets to the lAB-donor, as specified in TS 38.340

[0030] .

[0413] If the BH RLC Channel To Be Setup List IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall act as specified in TS 38.401 [4]. If the Traffic Mapping Information IE is included in the BH RLC Channel To Be Setup Item IES IE for a BH RLC Channel, the gNB-DU shall, if supported, process the Traffic Mapping Information IE following the behaviour described for the UE Context Setup procedure.

[0414] If the BH RLC Channel To Be Modified List IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall act as specified in TS 38.401 [4]. If the Traffic Mapping Information IE is included in the BH RLC Channel To Be Modified Item IEs IE for a BH RLC Channel, the gNB-DU shall, if supported, process the Traffic Mapping Information IE following the behaviour described for the UE Context Setup procedure.

[0415] If the BH RLC Channel To Be Released List IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall release the BH RLC channels in the list.

[0416] If two UL UP TNL Information IEs are included and the DRB Mapping Info IE is not contained in UE CONTEXT MODIFICATION REQUEST message for a DRB, the gNB-DU shall include two DL UP TNL Information IEs in UE CONTEXT MODIFICATION RESPONSE message and setup two RLC entities for the indicated DRB. If the UL UP TNL Information IE with the DRB Mapping Info IE and the UL UP TNL Information IE without the DRB Mapping Info IE are both contained in the UE CONTEXT MODIFICATION REQUEST message for a DRB, the gNB-DU shall, if supported, include two DL UP TNL Information IEs in UE CONTEXT MODIFICATION RESPONSE message, setup one RLC entity for the UL UP TNL Information IE without the DRB Mapping Info IE, and map the indicated DRB to the Uu Relay RLC channel based on the DRB Mapping Info IE. gNB-CU and gNB-DU use the UL UP TNL Information IEs and DL UP TNL Information IEs to support packet duplication for intra-gNB-DU CA and multi-path relay as defined in TS 38.470 [2]. The first UP TNL Information IE of the two UP TNL Information IEs is for the primary path.

[0417] If one or two Additional PDCP Duplication UP TNL Information IEs are included in the UE CONTEXT MODIFICATION REQUEST message for a DRB, the gNB-DU shall, if supported, include one or two Additional PDCP Duplication UP TNL Information IEs in the UE CONTEXT MODIFICATION RESPONSE message and setup one or two additional RLC entities for the indicated DRB. The gNB-CU and the gNB-DU use the Additional PDCP Duplication UP TNL Information IES to support packet duplication for intra-gNB-DU CA and multi-path relay as defined in TS 38.470 [2].

[0418] If Duplication Activation IE is included in the UE CONTEXT MODIFICATION REQUEST message for a DRB, the gNB-DU should take it into account when activating / deactivating CA based PDCP duplication or multi-path relay based PDCP duplication for the DRB. If the RLC Duplication State List IE is included in the RLC Duplication Information IE contained in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, take it into account for the DRB with more than two RLC entities.

[0419] If DC Based Duplication Configured IE is included in the UE CONTEXT MODIFICATION REQUEST message for a DRB, the gNB-DU shall regard that DC based PDCP duplication is configured for this DRB if the value is set to be "true" and it should take the responsibility of PDCP duplication activation / deactivation. Otherwise, the gNB-DU shall regard that DC based PDCP duplication is de-configured for this DRB id the value is set to be "false", and it should stop PDCP duplication activation / deactivation by MAC CE. If DC Based Duplication Activation IE is included in the UE CONTEXT MODIFICATION REQUEST message for a DRB, the gNB-DU should take it into account when activating / deactivating DC based PDCP duplication for this DRB. If the RLC Duplication State List IE is included in the RLC Duplication Information IE contained in the UE CONTEXT MODIFICATION REQUEST message for a DRB, the gNB-DU shall, if supported, take it into account when activating / deactivating DC based PDCP duplication for the DRB with more than two RLC entities. If the Primary Path Indication IE is included in the RLC Duplication Information IE, the gNB-DU shall, if supported, take it into account when performing DC based PDCP duplication for the DRB with more than two RLC entities.

[0420] For a certain DRB which was allocated with two GTP-U tunnels, if such DRB is modified and given one GTP-U tunnel via the UE Context Modification procedure, the gNB-DU shall consider that the CA based PDCP duplication or multipath relay based PDCP duplication for the concerned DRB is de-configured. If such UE Context Modification procedure occurs, the Duplication Activation IE shall not be included for the concerned DRB.

[0421] If the UL Configuration IE in DRB to Be Setup Item IE or DRB to Be Modified Item IE is contained in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall take it into account for UL scheduling.

[0422] If the RRC Reconfiguration Complete Indicator IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall consider the ongoing reconfiguration procedure involving changes of the L1 / L2 configuration at the gNB-DU signalled to the gNB-CU via the CellGroupConfig IE for MR-DC operation or standalone operation has been successfully performed when such IE is set to ‘true’; otherwise (when such IE is set to ‘failure’), the gNB-DU shall consider the ongoing reconfiguration procedure has been failed and it shall continue to use the old L1 / L2 configuration.

[0423] If DL PDCP SN length IE is included in the UE CONTEXT MODIFICATION REQUEST message for a DRB, gNB- DU shall, if supported, store this information and use it for lower layer configuration.

[0424] If UL PDCP SN length IE is included in the UE CONTEXT MODIFICATION REQUEST message for a DRB, gNB- DU shall, if supported, store this information and use it for lower layer configuration.

[0425] If the RLC Failure Indication IE is included in UE CONTEXT MODIFICATION REQUEST message, the gNB-DU should consider that the RLC entity indicated by such IE needs to be re-established when the CA-based packet duplication is active, and the gNB-DU may include the Associated SCell List IE in UE CONTEXT MODIFICATION RESPONSE by containing a list of SCell(s) associated with the RLC entity indicated by the RLC Failure Indication IE.

[0426] If the UE CONTEXT MODIFICATION REQUEST message contains the RRC-Container IE, the gNB-DU shall send the corresponding RRC message to the UE. If the UE CONTEXT MODIFICATION REQUEST message includes the Execute Duplication IE, the gNB-DU shall perform CA based duplication or multi-path relay based duplication, if configured, for the SRB for the included RRC-Container IE.

[0427] If the UE CONTEXT MODIFICATION REQUEST message contains the Transmission Action Indicator IE, the gNB- DU shall stop or restart (if already stopped) data transmission for the UE, according to the value of this IE. It is up to gNB-DU implementation when to stop or restart the UE scheduling.

[0428] For EN-DC operation, if the DRB to Be Setup List IE is present in the UE CONTEXT MODIFICATION REQUEST message the gNB-CU shall include the E-UTRAN QoS IE. The allocation of resources according to the values of the Allocation and Retention Priority IE included in the E-UTRAN QoS IE shall follow the principles described for the E- RAB Setup procedure in TS 36.413

[0015] . For NG-RAN operation, the gNB-CU shall include the DRB Information IE in the UE CONTEXT MODIFICATION REQUEST message.

[0429] If the gNB-CU includes the SMTC information of the measured frequency(ies) in the MeasurementTimingConfiguration IE of the CU to DU RRC Information IE that is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall generate the measurement gaps based on the received SMTC information. Then the gNB-DU shall send the measurement gaps information to the gNB-CU in the MeasGapConfig IE of the DU to CU RRC Information IE that is included in the UE CONTEXT MODIFICATION RESPONSE message.

[0430] If the MeasConfig IE is included in the CU to DU RRC Information IE in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall deduce that changes to the measurements’ configuration need to be applied.

[0431] The gNB-DU shall take the received info, e.g. the measObjectToAddModList IE, and / or the measObjectToRemoveList IE into account, when generating measurement gap and when deciding if a measurement gap is needed or not.

[0432] If the NeedForGapsInfoNR IE is included in the CU to DU RRC Information IE in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, use it as described in TS 38.331 [8]. If the NeedForGapNCSG-InfoNR IE is included in the CU to DU RRC Information IE in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, use it as described in TS 38.331 [8]. If the NeedForGapNCSG-InfoEUTRA IE is included in the CU to DU RRC Information IE in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, use it as described in TS 38.331 [8]. If the NeedForlnterruptionlnfoNR IE is included in the CU to DU RRC Information IE in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, use it as described in TS 38.331 [8].

[0433] For DC operation, if the gNB-CU includes the CG-Config IE in the CU to DU RRC Information IE that is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU may initiate low layer parameters coordination taking this information into account.

[0434] For sidelink operation, the CG-Configlnfo IE shall be included in the CU to DU RRC Information IE if the gNB-CU receives sidelink related UE information from UE. If the CG-Configlnfo IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall regard it as an indication of V2X sidelink information or NR sidelink information as defined in TS 38.331 [8].

[0435] For EN-DC operation, if the gNB-CU includes the Resource Coordination Transfer Information IE in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, use it for the purpose of resource coordination. If the gNB-CU received the MeNB Resource Coordination Information as defined in TS 36.423 [9], after completion of UE Context Setup procedures, the gNB-CU shall transparently transfer it to the gNB-DU via the Resource Coordination Transfer Container IE in the UE CONTEXT MODIFICATION REQUEST message. The gNB- DU shall use the information received in the Resource Coordination Transfer Container IE for reception of MeNB Resource Coordination Information at the gNB acting as secondary node as described in TS 36.423 [9]. If the Resource Coordination E-UTRA Cell Information IE is included in the Resource Coordination Transfer Information IE, the gNB- DU shall store the information replacing previously received information for the same E-UTRA cell, and use the stored information for the purpose of resource coordination. If the Ignore PRACH Configuration IE is present and set to "true" the E-UTRA PRACH Configuration IE in the UE CONTEXT MODIFICATION REQUEST message shall be ignored.

[0436] For NGEN-DC or NE-DC operation, if the gNB-CU includes the Resource Coordination Transfer Information IE in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, use it for the purpose of resource coordination. If the gNB-CU received the MR-DC Resource Coordination Information as defined in TS 38.423

[0028] , after completion of UE Context Setup procedures, the gNB-CU shall transparently transfer it to the gNB-DU via the Resource Coordination Transfer Container IE in the UE CONTEXT MODIFICATION REQUEST message. The gNB-DU shall use the information received in the Resource Coordination Transfer Container IE for reception of MR- DC Resource Coordination Information at the gNB as described in TS 38.423

[0028] .

[0437] For EN-DC operation, and if the Subscriber Profile ID for RAT / Frequency priority IE is received from an MeNB, the UE CONTEXT MODIFICTION REQUEST message shall contain the Subscriber Profile ID for RAT / Frequency priority IE. If the Additional RRM Policy Index IE is received from an MeNB, the UE CONTEXT MODIFICATION REQUEST message shall, if supported, contain the Additional RRM Policy Index IE. The gNB-DU shall store the received Subscriber Profile ID for RAT / Frequency priority in the UE context and use it as defined in TS 36.300

[0020] . The gNB-DU shall, if supported, store the received Additional RRM Policy Index in the UE context and use it as defined in TS 36.300

[0020] .

[0438] If the Index to RAT / Frequency Selection Priority IE is modified at the gNB-CU, the Index to RAT / Frequency Selection Priority IE shall be included in the UE CONTEXT MODIFICATION REQUEST. The gNB-DU may use it for RRM purposes.

[0439] Only one of the following IES shall be contained in the UE CONTEXT MODIFICATION REQUEST message: the Uplink TxDirectCurrentList Information IE or the Uplink TxDirectCurrentTwoCarrierList Information IE or the Uplink TxDirectCurrentMoreCarrierList Information IE. If the UE CONTEXT MODIFICATION REQUEST message contains one of the Uplink TxDirectCurrentList Information IE or the Uplink TxDirectCurrentTwoCarrierList Information IE or the Uplink TxDirectCurrentMoreCarrierList Information IE, the gNB-DU may take that into account when selecting LI configuration.

[0440] The UEAssistancelnformation IE shall be included in CU to DU RRC Information IE in the UE CONTEXT MODIFICATION REQUEST message if the gNB-CU received this IE from the UE; if the UEAssistancelnformation IE is included in the CU to DU RRC Information IE in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, take it into account when configuring resources for the UE.

[0441] The UEAssistancelnformationEUTRA IE shall be included in CU to DU RRC Information IE in the UE CONTEXT MODIFICATION REQUEST message if the gNB-CU received this IE from the UE; if the UEAssistancelnformationEUTRA IE is included in the CU to DU RRC Information IE in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, take it into account when configuring LTE sidelink resources for the UE.

[0442] The gNB-DU shall report to the gNB-CU, in the UE CONTEXT MODIFICATION RESPONSE message, the result for all the requested or modified DRBs, SRBs, BH RLC Channels, Uu Relay RLC channels, PC5 Relay RLC channels, and SL DRBs in the following way:

[0443] A list of DRBs which are successfully established shall be included in the DRB Setup List IE;

[0444] A list of DRBs which failed to be established shall be included in the DRB Failed to be Setup List IE;

[0445] A list of DRBs which are successfully modified shall be included in the DRB Modified List IE;

[0446] A list of DRBs which failed to be modified shall be included in the DRB Failed to be Modified List IE; A list of SRBs which failed to be established shall be included in the SRB Failed to be Setup List IE.

[0447] A list of successfully established SRBs with logical channel identities for primary path shall be included in the SRB Setup List IE only if CA based PDCP duplication is initiated for the concerned SRBs.

[0448] A list of successfully modified SRBs with logical channel identities for primary path shall be included in the SRB Modified List IE only if CA based PDCP duplication is initiated for the concerned SRBs.

[0449] A list of BH RLC channels which are successfully established shall be included in the BH RLC Channel Setup List IE;

[0450] A list of BH RLC channels which failed to be established shall be included in the BH RLC Channel Failed to be Setup List IE;

[0451] A list of BH RLC channels which are successfully modified shall be included in the BH RLC Channel Modified List IE;

[0452] A list of BH RLC channels which failed to be modified shall be included in the BH RLC Channel Failed to be Modified List IE;

[0453] A list of Uu Relay RLC channels which are successfully established shall be included in the Uu RLC Channel Setup List IE;

[0454] A list of Uu Relay RLC channels which failed to be established shall be included in the Uu RLC Channel Failed to be Setup List IE;

[0455] A list of Uu Relay RLC channels which are successfully modified shall be included in the Uu RLC Channel Modified List IE;

[0456] A list of Uu Relay RLC channels which are failed to be modified shall be included in the Uu RLC Channel Failed to be Modified List IE;

[0457] A list of PC5 Relay RLC channels which are successfully established shall be included in the PC5 RLC Channel Setup List IE;

[0458] A list of PC5 Relay RLC channels which failed to be established shall be included in the PC5 RLC Channel Failed to be Setup List IE;

[0459] A list of PC5 Relay RLC channels which are successfully modified shall be included in the PC5 RLC Channel Modified List IE;

[0460] A list of PC5 Relay RLC channels which failed to be modified shall be included in the PC5 RLC Channel Failed to be Modified List IE;

[0461] A list of SL DRBs which are successfully established shall be included in the SL DRB Setup List IE;

[0462] A list of SL DRBs which failed to be established shall be included in the SL DRB Failed to be Setup List IE;

[0463] A list of SL DRBs which are successfully modified shall be included in the SL DRB Modified List IE;

[0464] A list of SL DRBs which failed to be modified shall be included in the SL DRB Failed to be Modified List IE.

[0465] If Duplication Indication IE in SL DRB To Be Setup List IE is contained in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, generate two PC5 RLC bearer configurations for the indicated SL DRB. If Duplication Indication IE is contained in the SL DRB To Be Modified List IE, the gNB-DU shall, if supported, generate two PC5 RLC bearer configurations for the indicated SL DRB, if the value is set to be"true" and duplication is not already configured for the indicated SL DRB.

[0466] If Duplication Indication IE is contained in the SL DRB To Be Modified List IE, the gNB-DU shall, if supported, release the additional PC5 RLC configuration for the indicated SL DRB, if the value is set to be "false".

[0467] For each GBR DRB, if the Alternative QoS Parameters Sets IE is included in the GBR QoS Flow Information IE in the UE CONTEXT MODIFICATION REQUEST message, gNB-DU shall, if supported, behave the same as the NG-RAN node in the PDU Session Resource Setup procedure, specified in TS 38.413 [3].

[0468] If the BAP Control PDU Channel IE is included in the BH RLC Channel to be Setup List IE, the gNB-DU shall, if supported, consider that the configured BH RLC channel can be used to transmit BAP Control PDUs, and use this BH RLC channel as specified in TS 38.340

[0030] .

[0469] If the BAP Control PDU Channel IE is included in the BH RLC Channel to be Modified List IE, the gNB-DU shall, if supported, consider that the configured BH RLC channel can be used to transmit BAP Control PDUs, and use this BH RLC channel as specified in TS 38.340

[0030] . Otherwise, if the BAP Control PDU Channel IE is not present for any BH RLC channel, any available BH RLC channel can be used to transmit BAP Control PDUs as specified in TS 38.340

[0030] ,

[0470] If the Fl-C Transfer Path IE is included in UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, take it into account.

[0471] When the gNB-DU reports the unsuccessful establishment of a DRB or SRB or SL DRB or a BH RLC channel or a Uu Relay RLC channel or a PC5 Relay RLC channel, the cause value should be precise enough to enable the gNB-CU to know the reason for the unsuccessful establishment.

[0472] If the Resource Coordination Transfer Container IE is included in the UE CONTEXT MODIFICATION RESPONSE, the gNB-CU shall transparently transfer this information for the purpose of resource coordination as described in TS 36.423 [9], TS 38.423

[0028] .

[0473] If the DU to CU RRC Information IE is included in the UE CONTEXT MODIFICATION RESPONSE message, except for the CG-SDT procedure and UE configured with BWP specific ServingCellMO, the gNB-CU shall perform RRC Reconfiguration as described in TS 38.331 [8]. The CellGroupConfig IE shall transparently be signaled to the UE as specified in TS 38.331 [8]. In the cases of CG-SDT, and UE configured with BWP specific ServingCellMO, the CellGroupConfig IE shall be ignored by the gNB-CU.

[0474] If the ServCelllnfoList IE is included in the DU to CU RRC Information IE contained in the UE CONTEXT MODIFICATION RESPONSE message, the gNB-CU shall take it into account to generate the content of inter-node message, i.e., CG-Config or CG-Configlnfo, as described in TS 38.331 [8].

[0475] If the UE-CapabilityRAT-ContainerList IE is included in the UE CONTEXT MODIFICATION REQUEST, the gNB- DU shall take this information into account for UE specific configurations.

[0476] If the SCell Failed To Setup List IE is contained in the UE CONTEXT MODIFICATION RESPONSE message, the gNB-CU shall regard the corresponding SCell(s) failed to be set up with an appropriate cause value for each SCell failed to setup.

[0477] If the C-RNTI IE is included in the UE CONTEXT MODIFICATION RESPONSE, the gNB-CU shall consider that the C-RNTI has been allocated by the gNB-DU for this UE context. If the Inactivity Monitoring Request IE is contained in the UE CONTEXT MODIFICATION REQUEST message, gNB-DU may consider that the gNB-CU has requested the gNB-DU to perform UE inactivity monitoring. If the Inactivity Monitoring Response IE is contained in the UE CONTEXT MODIFICATION RESPONSE message and set to "Not-supported", the gNB-CU shall consider that the gNB-DU does not support UE inactivity monitoring for the UE.

[0478] The UE Context Modify Procedure is not used to configure SRBO.

[0479] If in the UE CONTEXT MODIFICATION REQUEST, the Notification Control IE is included in the DRB to Be Setup List IE or the DRB to Be Modified List IE and it is set to active, the gNB-DU shall, if supported, monitor the QoS of the DRB and notify the gNB-CU if the QoS cannot be fulfilled any longer or if the QoS can be fulfilled again. The Notification Control IE can only be applied to GBR bearers.

[0480] If the UL PDU Session Aggregate Maximum Bit Rate IE is included in the QoS Flow Level QoS Parameters IE containded in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall replace the received UL PDU Session Aggregate Maximum Bit Rate and use it as specified in TS 23.501

[0021] .

[0481] If the gNB-DU UE Aggregate Maximum Bit Rate Uplink IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall: replace the previously provided gNB-DU UE Aggregate Maximum Bit Rate Uplink with the new received gNB-DU UE Aggregate Maximum Bit Rate Uplink; use the received gNB-DU UE Aggregate Maximum Bit Rate Uplink for non-GBR Bearers for the concerned UE.

[0482] The gNB-DU UE Aggregate Maximum Bit Rate Uplink IE shall be sent in the UE CONTEXT MODIFICATION REQUEST if DRB to Be Setup List IE is included and the gNB-CU has not previously sent it. The gNB-DU shall store and use the received gNB-DU UE Aggregate Maximum Bit Rate Uplink IE.

[0483] If the RLC Status IE is included in the UE CONTEXT MODIFICATION RESPONSE message, the gNB-CU shall assume that RLC has been reestablished at the gNB-DU and may trigger PDCP data recovery.

[0484] If the GNB-DU Configuration Query IE is contained in the UE CONTEXT MODIFICATION REQUEST message, gNB-DU shall include the DU To CU RRC Information IE in the UE CONTEXT MODIFICATION RESPONSE message.

[0485] If the Bearer Type Change IE is included in DRB to Be Modified List IE in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall either reset the lower layers or generate a new LCID for the affected bearer as specified in TS 37.340 [7],

[0486] For NE-DC operation, if NeedforGap IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall generate measurement gap for the SeNB.

[0487] If the QoS Flow Mapping Indication IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, replace any previously received value and take it into account that only the uplink or downlink QoS flow is mapped to the DRB.

[0488] If the Lower Layer presence status change IE set to "suspend lower layers" is included in the UE CONTEXT MODIFICATION REQUEST, the gNB-DU shall keep all lower layer configuration for UEs, and not transmit or receive data from UE. If the Lower Layer presence status change IE set to "resume lower layers" is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall use the previously stored lower layer configuration for the UE.

[0489] If the Full Configuration IE is contained in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall generate a CellGroupConfig IE using full configuration and include it in the UE CONTEXT MODIFICATION RESPONSE.

[0490] If the Full Configuration IE is contained in the UE CONTEXT MODIFICATION RESPONSE message, the gNB-CU shall consider that the gNB-DU has generated the CellGroupConfig IE using full configuration.

[0491] For each QoS flow whose DRB has been successfully established or modified and the QoS Monitoring Request IE was included in the QoS Flow Level QoS Parameters IE contained in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall store this information, and, if supported, perform delay measurement and QoS monitoring, as specified in TS 23.501

[0021] .

[0492] If the NR V2X Services Authorized IE is contained in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, update its V2X services authorization information for the UE accordingly. If the NR V2X Services Authorized IE includes one or more lEs set to "not authorized", the gNB-DU shall, if supported, initiate actions to ensure that the UE is no longer accessing the relevant service(s).

[0493] If the LTE V2X Services Authorized IE is contained in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, update its V2X services authorization information for the UE accordingly. If the LTE V2X Services Authorized IE includes one or more lEs set to "not authorized", the gNB-DU shall, if supported, initiate actions to ensure that the UE is no longer accessing the relevant service(s).

[0494] If the LTE UE Sidelink Aggregate Maximum Bit Rate IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported: replace the previously provided UE LTE Sidelink Aggregate Maximum Bit Rate, if available in the UE context, with the received value; use the received value for the concerned UE’s sidelink communication in network scheduled mode for LTE V2X services.

[0495] If the NR UE Sidelink Aggregate Maximum Bit Rate IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported: replace the previously provided UE NR Sidelink Aggregate Maximum Bit Rate, if available in the UE context, with the received value; use the received value for the concerned UE’s sidelink communication in network scheduled mode for NR V2X services.

[0496] If the NR A2X Services Authorized IE is contained in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, update its A2X services authorization information for the UE accordingly. If the NR A2X Services Authorized IE includes one or more lEs set to "not authorized", the gNB-DU shall, if supported, initiate actions to ensure that the UE is no longer accessing the relevant service(s).

[0497] If the LTE A2X Services Authorized IE is contained in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, update its A2X services authorization information for the UE accordingly. If the LTE A2X Services Authorized IE includes one or more lEs set to "not authorized", the gNB-DU shall, if supported, initiate actions to ensure that the UE is no longer accessing the relevant service(s). If the LTE UE Sidelink Aggregate Maximum Bit Rate for A2X IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported: replace the previously provided UE LTE Sidelink Aggregate Maximum Bit Rate for A2X, if available in the UE context, with the received value; use the received value for the concerned UE’s sidelink communication in network scheduled mode for LTE A2X services.

[0498] If the NR UE Sidelink Aggregate Maximum Bit Rate for A2X IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported: replace the previously provided UE NR Sidelink Aggregate Maximum Bit Rate for A2X, if available in the UE context, with the received value; use the received value for the concerned UE’s sidelink communication in network scheduled mode for NR A2X services.

[0499] If the PC5 Link Aggregate Maximum Bit Rate IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported: replace the previously provided UE PC5 Link Aggregate Bit Rate, if available in the UE context, with the received value; use the received value for the concerned UE’s sidelink communication in network scheduled mode for NR V2X services as defined in TS 23.287

[0040] .

[0500] If the TSC Traffic Characteristics IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, take into account the corresponding information received in the TSC Traffic Characteristics IE. If the RAN Feedback Type IE is included in the TSC Assistance Information Uplink IE of the TSC Traffic Characteristics IE, the gNB-DU shall, if supported, take this information into account when determining the feedback to provide in the TSC Traffic Characteristics Feedback IE in the UE CONTEXT MODIFICATION RESPONSE message.

[0501] If the CP AC MCG Information IE is included in the UE CONTEXT MODIFICATION REQUEST message and the CP AC Trigger is set to "CPAC-preparation", the gNB-DU shall, if supported, consider that the request concerns a conditional PSCell addition or conditional PSCell change or subsequent CP AC. The gNB-DU takes the included CG- Config and / or CG-Configlnfo IE into account, and may provide a corresponding CellGroupConfig IE for MCG configuration preparation in the UE CONTEXT MODIFICATION RESPONSE message. The UE CONTEXT MODIFICATION RESPONSE message also includes a Requested Target Cell ID IE corresponding to the PSCell ID IE in the UE CONTEXT MODIFICATION REQUEST message.

[0502] If the CP AC MCG Information IE is included in the UE CONTEXT MODIFICATION REQUEST message and the CP AC Trigger is set to "CPAC-executed", the gNB-DU shall, if supported, consider that, for the included PSCell ID IE corresponding to the selected PSCell, the UE has successfully executed the CPAC preparation. The gNB-DU shall apply the corresponding CellGroupConfig IE for MCG configuration.

[0503] If the Conditional Intra-DU Mobility Information IE is included in the UE CONTEXT MODIFICATION REQUEST message and the CHO Trigger is set to "CHO-initiation", the gNB-DU shall consider that the request concerns a conditional handover, conditional PSCell addition, conditional PSCell change, or subsequent CPAC for the included SpCell ID IE and shall include it as the Requested Target Cell ID IE in the UE CONTEXT MODIFICATION RESPONSE message. The gNB-DU shall regard it as a reconfiguration with sync as defined in TS 38.331 [8]. If the Conditional Intra-DU Mobility Information IE is included in the UE CONTEXT MODIFICATION REQUEST message and the CHO Trigger is set to "CHO-replace", the gNB-DU shall replace the existing prepared conditional mobility identified by the gNB-DU UE Fl AP ID IE and the SpCell ID IE.

[0504] If the Conditional Intra-DU Mobility Information IE is included in the UE CONTEXT MODIFICATION REQUEST message and the CHO Trigger is set to "CHO-cancel", the gNB-DU shall consider that the gNB-CU is about to remove any reference to, and release any resources previously reserved for the cells identified by the included NR CGIs in the Candidate Cells To Be Cancelled List IE.

[0505] If the S-CPAC Request IE is included within the Conditional Intra-DU Mobility Information IE in the UE CONTEXT MODIFICATION REQUEST message and is set to "initiation", the gNB-DU shall, if supported, consider that the procedure is triggered for S-CPAC preparation.

[0506] If the Transmission Stop Indicator IE is included within the DRB to Be Modified Item IE in the UE CONTEXT MODIFICATION REQUEST message and set to “true”, the gNB-DU shall, if supported, stop the data transmission for the DRB. It is up to gNB-DU implementation when to stop the UE scheduling for that DRB.

[0507] If the SCG Indicator IE is contained in the UE CONTEXT MODIFICATION REQUEST message and it is set to “released”, the gNB-DU shall, if supported, deduce that an SCG is removed.

[0508] If the Estimated Arrival Probability IE is contained in the Conditional Intra-DU Mobility Information IE included in the UE CONTEXT MODIFICATION REQUEST message, then the gNB-DU may use the information to allocate necessary resources for the UE.

[0509] If the Location Measurement Information IE is included in the CU to DU RRC Information IE in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, take it into account when configuring measurement gaps for the UE.

[0510] If the Fl-C Transfer Path NRDC IE is included in UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, take it into account.

[0511] If for a given E-RAB for EN-DC operation the ENB DL Transport Layer Address IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, use it as part of its ACL functionality configuration actions, if such ACL functionality is deployed.

[0512] If for a given Qos flow for NG-RAN operation the PDCP Terminating Node DL Transport Layer Address IE is included in the UE CONTEXT MODIFICATION REQUEST message, then the gNB-DU shall, if supported, use it as part of its ACL functionality configuration actions, if such ACL functionality is deployed.

[0513] If the gNB-DU is an IAB-DU, and if the IAB Conditional RRC Message Delivery Indication IE is included in the UE CONTEXT MODIFICATION REQUEST message together with the RRC-Container IE, and if its value is set to “true”, and if the RRC-Container IE is for a child IAB-MT of the gNB-DU, the gNB-DU shall, if supported, withhold the RRC message until one of the following conditions is met:

[0514] If the gNB-DU belongs to a migrating lAB-node, whose co-located IAB-MT has successfully performed the random-access procedure to the target parent node, and if the migrating lAB-node has one or more routing entries for the target path.

[0515] The gNB-DU receives a subsequent Fl AP message including an RRC-Container IE for the same child node.

[0516] If the gNB-DU belongs to a descendant node of the migrating lAB-node, whose co-located IAB-MT has received an RRCReconfiguration message including the intra-donor migration configurations, e.g., new TNL address(es) and the new default UL BAP routing ID. If the gNB-DU belongs to a migrating lAB-node, whose co-located IAB-MT has successfully performed RLF recovery after handover failure, and if the migrating lAB-node has one or more routing entries for the target path.

[0517] If the MDT Polluted Measurement Indicator IE is included in the UE CONTEXT MODIFICATION REQUEST, the gNB-DU shall take this information into account as specified in TS 38.401 [4].

[0518] If the SCG Activation Request IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB- DU may use it to configure SCG resources as specified in TS 37.340 [7], and if supported, shall include the SCG Activation Status IE in the UE CONTEXT MODIFICATION RESPONSE message.

[0519] If the CG-SDT Query Indication IE is included in the UE CONTEXT MODIFICATION REQUEST message and set to ‘true’, the gNB-DU shall, if supported, provide the CG-SDT related resource configuration for the bearers indicated as SDT bearers in the SDT-MAC-PHY-CG-Config IE within the DU to CU RRC Information IE contained in the UE CONTEXT MODIFICATION RESPONSE message to the gNB-CU. If the SDT-MAC-PHY-CG-Config IE is also included in the UE CONTEXT MODIFICATION REQUEST message within the CU to DU RRC Information IE, the gNB-DU may provide the delta signalling version of the SDT-MAC-PHY-CG-Config IE within the DU to CU RRC Information IE contained in the UE CONTEXT MODIFICATION RESPONSE message to the gNB-CU.

[0520] If the 5G ProSe Authorized IE is contained in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, update its 5G ProSe services authorization information for the UE accordingly. If the 5G ProSe Authorized IE includes one or more IES set to "not authorized", the gNB-DU shall, if supported, initiate actions to ensure that the UE is no longer accessing the relevant service(s).

[0521] If the SDT Bearer Configuration Query Indication IE is contained in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, provide the RLC bearer configuration in the SDT Bearer Configuration Info IE in the UE CONTEXT MODIFICATION RESPONSE message for each bearer indicated as SDT bearer.

[0522] If the 5G ProSe UE PC5 Aggregate Maximum Bit Rate IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported: replace the previously provided 5G ProSe UE PC5 Aggregate Maximum Bit Rate, if available in the UE context, with the received value; use the received value for the concerned UE’s sidelink communication in network scheduled mode for 5G ProSe services.

[0523] If the 5G ProSe PC5 Link Aggregate Bit Rate IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported: replace the previously provided 5G ProSe PC5 Link Aggregate Bit Rate, if available in the UE context, with the received value; use the received value for the concerned UE’s sidelink communication in network scheduled mode for 5G ProSe services as defined in TS 23.304

[0044] .

[0524] If the Updated Remote UE Local ID IE is contained in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, replace the previously provided Remote UE Local ID, if available in the UE context, with the received value.

[0525] If the Uu RLC Channel To Be Setup List IE is contained in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, act as specified in TS 38.401 [4]. If the Uu RLC Channel To Be Modified List IE is contained in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, act as specified in TS 38.401 [4].

[0526] If the Uu RLC Channel To Be Release List IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, release the Uu Relay RLC channels in the list.

[0527] If the PC5 RLC Channel To Be Setup List IE is contained in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, act as specified in TS 38.401 [4]. gNB-DU generates the PC5 Relay RLC channel configurations for a L2 U2N Remote UE, U2N Relay UE, a L2 U2U Remote UE or a L2 U2U Relay UE. If the FlAP-IDs are associated with a U2N Relay UE, the PC5 RLC Channel to be Setup Item lEs IE shall include the Remote UE Local ID and correspondingly, the PC5 RLC Channel Setup Item lEs IE and the PC5 RLC Channel Failed to be Setup Item IE in the UE CONTEXT MODIFICATION RESPONSE message shall include the Remote UE Local ID IE.

[0528] If the PC5 RLC Channel To Be Modified List IE is contained in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, act as specified in TS 38.401 [4]. gNB-DU generates the PC5 Relay RLC channel configurations for a L2 U2N Remote UE , U2N Relay UE, a L2 U2U Remote UE or a L2 U2U Relay UE. If the Fl AP-IDs are associated with a U2N Relay UE, the PC5 RLC Channel to be Modified Item lEs IE shall include the Remote UE Local ID IE and correspondingly, the PC5 RLC Channel Modified Item lEs IE and the PC5 RLC Channel Failed to be Modified Item lEs IE in the UE CONTEXT MODIFICATION RESPONSE message shall include the Remote UE Local ID IE.

[0529] If the PC5 RLC Channel To Be Release List IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, release the PC5 Relay RLC channels in the list. If the Fl AP-IDs are associated with a U2N Relay UE, the PC5 RLC Channel to be Released Item lEs IE shall include the Remote UE Local ID IE.

[0530] If the Path Switch Configuration IE is contained in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, use it to configure the path switch from direct path to indirect path as specified in TS 38.401 [4] or from indirect path to indirect path as specified in TS 38.331 [8], or to release the direct path during the MP as specified in TS 38.331 [8].

[0531] If the MUSIM-GapConfig IE is contained in the CU to DU RRC Information IE included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, decide to use this IE for MUSIM gap configuration or select another one based on the received UEAssistancelnformation IE. If gNB-DU selects a different MUSIM gap configuration from received UEAssistancelnformation IE, then it shall include the selected MUSIM gap information to the gNB-CU in the MUSIM-GapConfig IE of the DU to CU RRC Information IE that is included in the UE CONTEXT MODIFICATION RESPONSE message.

[0532] If MUSIM-GapConfig IE is not contained in the CU to DU RRC Information IE, then gNB-DU shall, if supported, send the selected MUSIM gap configuration based on the received UEAssistancelnformation IE, to the gNB-CU in the MUSIM-GapConfig IE of the DU to CU RRC Information IE that is included in the UE CONTEXT MODIFICATION RESPONSE message. When MUSIM-GapConfig IE is received, the gNB-CU should use this value.

[0533] If the gNB-DU UE Slice Maximum Bit Rate List IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, store and replace the previously provided gNB-DU UE Slice Maximum Bit Rate List, if any, with the new received gNB-DU UE Slice Maximum Bit Rate List; use the received gNB-DU UE Slice Maximum Bit Rate List for the uplink traffic policing for each concerned slice as specified in TS 23.501

[0021] . If the Multicast MBS Session Setup List IE or the Multicast MBS Session Remove List IE or both IES are contained in the UE CONTEXT MODIFICATION REQUEST message the gNB-DU shall, if supported, store and use the information for configuring MBS Session Resources, if applicable.

[0534] If the UE Multicast MRB To Be Setup at Modify List IE is contained in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, take it into account for configuring MBS Session Resources, if applicable, and shall include the Multicast Fl-U Context Reference CU IE, if available, in the UE CONTEXT MODIFICATION RESPONSE message. And if the MBS PTP Retransmission Tunnel Required IE is included in the UE Multicast MRB to Be Setup at Modify Item IEs IE, the gNB-DU shall, if supported trigger the establishment of the MBS PTP Retransmission Fl-U tunnel.

[0535] If the MBS PTP Forwarding Tunnel Required Information IE is included in the UE Multicast MRB to Be Setup at Modify Item IEs IE, the gNB-DU shall, if supported trigger the establishment of the MBS PTP Forwarding Fl-U tunnel.

[0536] If the Management Based MDT PLMN Modification List IE is contained in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, overwrite any previously stored Management Based MDT PLMN List information in the UE context and use the received information to determine subsequent selection of the UE for management based MDT defined in TS 32.422

[0029] .

[0537] If the Dedicated SI Delivery Indication IE is included in the UE CONTEXT MODIFICATION RESPONSE message, the gNB-CU shall, if supported, take it into account for the system information delivery to the UE as described in TS 38.331 [8].

[0538] If the PDU Set QoS Parameters IE is included in the QoS Flow Level QoS Parameters IE contained in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, store this information and use it as specified in TS 23.501

[0021] .

[0539] If the ECN Marking or Congestion Information Reporting Request IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, use it accordingly for the specific DRB. If the ECN Marking or Congestion Information Reporting Status IE is included in the UE CONTEXT MODIFICATION RESPONSE message, the gNB-CU shall, if supported, use it to deduce if ECN marking or congestion information reporting is active or not active.

[0540] If the InterFrequencyConfig-NoGap IE is included in the DU to CU RRC Information IE contained in the UE CONTEXT MODIFICATION RESPONSE message, the gNB-CU shall, if supported, use it as described in TS 38.331 [8].

[0541] If the ul-GapFR2-Config IE is contained in the DU to CU RRC Information IE that is included in the UE CONTEXT MODIFICATION RESPONSE message, the gNB-CU shall, if supported, use it as described in TS 38.331 [8].

[0542] If the TwoPHRModeMCG IE or the TwoPHRModeSCG IE is contained in the DU to CU RRC Information IE that is included in the UE CONTEXT MODIFICATION RESPONSE message, the gNB-CU shall, if supported, use this value as described in TS 38.331 [8].

[0543] If the MBSInterestlndication IE is included in the CU to DU RRC Information IE in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, take it into account when configuring resources for the UE.

[0544] If the ncd-SSB-RedCapInitialBWP-SDT IE is contained in the DU to CU RRC Information IE that is included in the UE CONTEXT MODIFICATION RESPONSE message, the gNB-CU shall, if supported, use it as described in TS 38.331 [8]. If the Network Controlled Repeater Authorized IE is contained in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, update its authorization information for the UE accordingly. If the Network Controlled Repeater Authorized IE is set to "not authorized", the gNB-DU shall, if supported, initiate actions to ensure that the UE is no longer accessing as a Network Controlled Repeater.

[0545] If the LTM Indicator IE set to "true" is contained in the LTM Information Modify IE included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, consider that the request concerns LTM for the included SpCell ID IE and shall include it as the Requested Target Cell ID IE in the UE CONTEXT MODIFICATION RESPONSE message. The gNB-DU shall regard it as a reconfiguration with sync as defined in TS 38.331 [8]. If the gNB-DU accepts the request for LTM for that SpCell, the gNB-DU shall generate and include the CellGroupConfig IE for the accepted LTM candidate cell in the UE CONTEXT MODIFICATION RESPONSE message.

[0546] If the Request for Lower Layer Configuration IE set to "true" is contained within the Reference Configuration IE in the LTM Information Modify IE included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, include the Reference Configuration Information IE in the LTM Configuration IE in the UE CONTEXT MODIFICATION RESPONSE message to provide lower layer configuration for the gNB-CU to generate the LTM reference configuration.

[0547] If the Reference Configuration Information IE is contained within the Reference Configuration IE in the LTM Information Modify IE included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, take it into account for generating the LTM lower layer configuration.

[0548] If the CSI Resource Configuration IE is contained in the LTM Information Modify IE included in the UE CONTEXT MODIFICATION REQUEST message and the SpCell ID IE is also included, the gNB-DU shall, if supported, use it to generate the LTM CSI reporting configuration in the CellGroupConfig IE for the requested LTM candidate cell identified by the SpCell ID IE.

[0549] If the CSI Resource Configuration IE is contained in the LTM Information Modify IE included in the UE CONTEXT MODIFICATION REQUEST message while the SpCell ID IE is absent, the gNB-DU shall, if supported, use it to generate the LTM CSI reporting configuration in the CellGroupConfig IE for the serving cell.

[0550] If the LTM Configuration ID Mapping List IE is contained in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, consider this as the mapping information for the LTM candidate cell(s).

[0551] If the Early Sync Information Request IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, include Early Sync Information IE of the accepted candidate cell for early TA acquisition (early UL synchronisation) in the UE CONTEXT MODIFICATION RESPONSE message. If the Early UL Sync Configuration IE is included in the UE CONTEXT MODIFICATION RESPONSE message, the gNB-CU shall, if supported, consider it as the generated early UL sync information from the accepted candidate cell in the gNB-DU. If the Early UL Sync Configuration for SUL IE is included in the UE CONTEXT MODIFICATION RESPONSE message, the gNB-CU shall, if supported, consider it as the generated early UL sync information for SUL from the accepted candidate cell in the gNB-DU.

[0552] If the Early Sync Candidate Cell Information List IE is contained in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, use it as specified in TS 38.401 [4]. If the UE Based TA Measurement Configuration IE is contained in the Early Sync Candidate Cell Information List IE for some candidate cell, the gNB- DU shall, if supported, take them into account for UE based TA measurement during LTM cell switch as specified in TS 38.331 [8].

[0553] If the Early Sync Serving Cell Information IE is contained in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, use it as specified in TS 38.401 [4]. If the UE Based TA Measurement Configuration IE is contained in the Early Sync Serving Cell Information IE, the gNB-DU shall, if supported, take it into account for UE based TA measurement during LTM cell switch as specified in TS 38.331 [8].

[0554] If the LTM CFRA Resource Config List IE is contained in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, use it for the LTM cell switch command as specified in TS 38.321

[0016] .

[0555] If the LTM Configuration IE is included in the UE CONTEXT MODIFICATION RESPONSE message, the gNB-CU shall, if supported, consider it as the generated configuration for LTM from the accepted candidate cell in the gNB-DU.

[0556] If the LTM Cells to be Released List IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, release the configured candidate cells in the list.

[0557] If the Complete Candidate Configuration Indicator IE set to "complete" is contained in the LTM Configuration IE included in the UE CONTEXT MODIFICATION RESPONSE message, the gNB-CU shall, if supported, consider that the LTM candidate configuration is a complete candidate configuration.

[0558] If the Direct Path Addition IE is contained in the Path Addition Information IE which is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, consider that the request concerns the direct path addition for the included SpCell ID IE as specified in TS 38.401 [4] and regard it as a reconfiguration with sync as defined in TS 38.331 [8]. If the Indirect Path Addition IE is contained in the Path Addition Information IE, the gNB-DU shall, if supported, consider that the request concerns the indirect path addition for the MP Remote UE using PC5 link and use it as specified in TS 38.401 [4]. If the N3C Indirect Path Addition IE is contained in the Path Addition Information IE, the gNB-DU shall, if supported, consider that the request concerns the indirect path addition for the MP Remote UE using N3C and use it as specified in TS 38.401 [4].

[0559] If the S-NSSAI IE is included within the DRB to Be Modified Item IE in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, store the corresponding information and replace any existing information.

[0560] If the S-CPAC Lower Layer Reference Config Request IE set to "true" is contained in the Conditional Intra-DU Mobility Information IE included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, provide the lower layer configuration in the Reference Configuration Information IE in the S-CPAC Configuration IE in the UE CONTEXT MODIFICATION RESPONSE message for the gNB-CU to generate the S- CPAC reference configuration.

[0561] If the Complete Candidate Configuration Indicator IE set to "complete" is contained in the S-CPAC Configuration IE included in the UE CONTEXT MODIFICATION RESPONSE message, the gNB-CU shall, if supported, consider that the S-CPAC candidate configuration is a complete candidate configuration.

[0562] If the musim-CandidateBandList IE is included in the CU to DU RRC Information IE in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, use it for temporary capability restriction.

[0563] If the DL LBT Failure Information Request IE is included in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, consider that the gNB-CU has requested the DL LBT failure information of the UE and act as specified in TS 38.401 [4].

[0564] If the Ranging and Sidelink Positioning Service Information IE is contained in the UE CONTEXT MODIFICATION REQUEST message, the gNB-DU shall, if supported, update its service information for the UE accordingly. If the Ranging and Sidelink Positioning Authorized IE within the Ranging and Sidelink Positioning Service Information IE is set to "not authorized", the gNB-DU shall, if supported, initiate actions to ensure that the UE is no longer accessing the Ranging and Sidelink Positioning service. Interaction with UE Inactivity Notification procedure

[0565] If the SDT Volume Threshold IE is contained in the UE CONTEXT MODIFICATION REQUEST message, the gNB- DU shall, if supported, use the information during an SDT transaction to inform the gNB-CU via the UE INACTIVITY NOTIFICATION message as specified in TS 38.401 [4],

[0566] Interaction with UE Context Setup or UE Context Modification (gNB-CU initiated) procedures

[0567] If the UE CONTEXT MODIFICATION REQUEST message is sent for a UE context set up for S-CPAC and contains the Transmission Action Indicator IE set to "stop", the gNB-DU shall, if supported, reset the UE context for the included SpCell ID IE, prepare for subsequent CPAC. The gNB-DU shall include the SpCell ID IE as the Requested Target Cell ID IE in the UE CONTEXT MODIFICATION RESPONSE message.

[0568] Many functionalities in a secondary node (SN), such as a secondary gNB, are configured using a fixed set of attributes regardless of any connection type inputs, for example primary cell (PCell) and primary secondary cell (PSCell) frequency combination. gNBs may deploy multiple cells with different frequency bands and bandwidths, which leads to multiple combinations of PCell and PSCell frequency combinations for each of the gNBs. With a single configuration per gNB, it is not possible to optimize it for each of such combinations individually. This means that configuration may be optimized for only one of the frequency combinations, leading to suboptimal performance for the others. Alternatively, a configuration that tries to balance performance for all of the frequency combinations may be applied, which, again, leads to suboptimal performance for all of the frequency combinations.

[0569] Fig. 11 shows an existing solution overview.

[0570] Independent configuration tailored for each of those frequency deployments to achieve optimized performance without compromising performance of other frequency deployments is not provided by the existing technology.

[0571] Operators have limited ability to tune parameters on a frequency band basis when cells use frequencies those belong to different bands that are handled by the same CU-CP, CU-user plane (UP), or DU. When shared resources are utilized for all instances for different bands such as low frequency band (LB) and mid frequency band (MB), then the same set of parameters are used for all which then results in a compromise in the network performance. The typical CU-CP, CU-UP, and DU configuration does not allow multiple parameter settings for a particular functionality, e.g., PDCP for different band deployments such as LB and MB which then results in usage of suboptimal parameters. An example scenario where the same set of parameters are used for LB and / or MB is depicted in Fig. 12.

[0572] Fig. 12 shows an example scenario with common Cloud RAN (CR) CU-UP Pool for LB and / or MB.

[0573] Currently, it is not possible to use different parameters settings for a functionality based on connection properties where cells belong to different bands within the same gNB. For instance, it is not possible to differentiate PDCP parameter settings for connections with cells on different bands of a gNB. Therefore, a UE is affected by the performance of the network due to unavailability of different parameter sets for different bands.

[0574] Fig. 13 shows an example of possible connections. Fig. 13 represents different scenarios of connections for UEs. For instance, using different parameter settings of a functionality for the UE in the 1stand 3rdconnections or 8thand 9thinstead of using the same settings for all may provide a more optimized performance for the UEs.

[0575] Fig. 14 shows that many gNBs are required for individual configuration per connection scenario.

[0576] An object of embodiments herein is to provide an efficient handling of communication of a UE in a communication network.

[0577] According to an aspect the object is achieved, according to some embodiments herein, by providing a method performed by a radio network node for handling communication of a UE in a communication network. The radio network node groups the UE into a group of UEs upon connection establishment based on one or more connection properties, e.g., a frequency band of master cell group (MCG) and / or secondary cell group (SCG), a cell bandwidth, a number of MIMO layers, and / or a cell load. The radio network node further selects a connection specific configuration for the UE based on information related to the group. The configuration may be either used internally in the radio network node or sent to the UE via RRC.

[0578] It is furthermore provided herein a computer program product comprising instructions, which, when executed on at least one processor, cause the at least one processor to carry out the methods herein, as performed by the radio network node. It is additionally provided herein a computer-readable storage medium, having stored thereon a computer program product comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out the methods herein, as performed by the radio network node.

[0579] Furthermore, according to another aspect the object is achieved, according to some embodiments herein, by providing a radio network node configured to perform the methods herein, respectively.

[0580] According to another aspect the object is achieved, according to some embodiments herein, by providing a radio network node, such as an gNB, for handling communication of a UE in a communication network. The radio network node is configured to group the UE into a group of UEs upon connection establishment based on one or more connection properties, e.g., a frequency band of MCG and / or SCG, a cell bandwidth, a number of MIMO layers, and / or a cell load. The radio network node is further configured to select a connection specific configuration for the UE based on information related to the group.

[0581] Embodiments herein support selection of configuration of functionalities or features based on the connection properties of the UE. Then each UE is expected to get a more optimal performance that suits its target use case. Embodiments herein applies for radio network nodes providing one or more RATs such as NR Standalone, NR-NR dual connectivity, and E-UTRAN-NR (EN)-dual connectivity (DC). This means that both a master node (MN) and a secondary node (SN) may implement embodiments herein. Thus, embodiments herein provide an efficient handling of communication of the UE.

[0582] BRIEF DESCRIPTION OF THE DRAWINGS

[0583] Embodiments will now be described in more detail in relation to the enclosed drawings, in which:

[0584] Fig. 1 A shows a gNB with a split architecture according to prior art;

[0585] Fig. 1 B shows Xn Setup according to prior art;

[0586] Fig. 1 C shows eNB initiated EN-DC X2 Setup according to prior art;

[0587] Fig. 2 shows en-gNB initiated EN-DC X2 Setup according to prior art;

[0588] Fig. 3 shows C-Plane connectivity for EN-DC and multi radio-dual connectivity (MR-DC) with 5GC according to prior art;

[0589] Fig. 4 shows U-Plane connectivity for EN-DC and MR-DC with 5GC according to prior art;

[0590] Fig. 5 shows Secondary Node Addition procedure according to prior art;

[0591] Fig. 6 shows SN Addition procedure according to prior art;

[0592] Fig. 7 shows Bearer Context Setup procedure according to prior art;

[0593] Fig. 8 shows Bearer Context Modification procedure according to prior art;

[0594] Fig. 9 shows UE Context Setup Request procedure according to prior art;

[0595] Fig. 10 shows UE Context Modification procedure according to prior art;

[0596] Fig. 11 shows an existing solution overview;

[0597] Fig. 12 shows an example scenario with common CU-UP Pool for LB / MB;

[0598] Fig. 13 shows an example of possible connections according to prior art;

[0599] Fig. 14 shows that many gNBs are required for individual configuration per connection scenario;

[0600] Fig. 15 shows an overview of a communication network according to embodiments herein;

[0601] Fig. 16 is a combined flowchart and signaling scheme according to embodiments herein;

[0602] Fig. 17A shows an overview according to some embodiments herein;

[0603] Fig. 17B shows a flowchart illustrating a method according to some embodiments herein;

[0604] Fig. 18 shows an overview according to some embodiments herein;

[0605] Fig. 19 shows CU-CP Managed Object Model (MOM) Target

[0606] Fig. 20 shows an overview according to some embodiments herein;

[0607] Fig. 21 shows a flowchart according to some embodiments herein;

[0608] Fig. 22 shows an overview according to some embodiments herein;

[0609] Fig. 23 shows a flowchart illustrating a method performed by a radio network node according to embodiments herein; Fig. 24 shows a block diagram depicting embodiments of a radio network node according to embodiments herein;

[0610] Fig. 25 shows an example of a communication system 15100 in accordance with some embodiments;

[0611] Fig. 26 shows a communication system 15200 in accordance with some embodiments;

[0612] Fig. 27 shows a UE 15300 in accordance with some embodiments;

[0613] Fig. 28 is a block diagram of a network node 15400 in accordance with various aspects described herein; and

[0614] Fig. 29 is a block diagram illustrating a virtualization environment 15500 in which functions implemented by some embodiments may be virtualized.

[0615] DETAILED DESCRIPTION

[0616] Embodiments herein relate to communication networks in general. Fig. 15 is a schematic overview depicting a communication network 1. The communication network 1 comprises one or more RANs and one or more CNs. The communication network 1 may use one or a number of different technologies. Embodiments herein relate to recent technology trends that are of particular interest in a NR context, however, embodiments are also applicable in further development of existing wireless communications systems such as e.g. LTE or Wideband Code Division Multiple Access (WCDMA) and also upcoming 6G.

[0617] In the communication network 1 , a UE 10 exemplified herein as a wireless device such as a mobile station, a non-access point (non-AP) station (STA), a STA and / or a wireless terminal, is comprised communicating via e.g. one or more Access Networks (AN), e.g. RAN, to one or more CN. It should be understood by the skilled in the art that “UE” is a non-limiting term which means any terminal, wireless communications terminal, user equipment, narrowband internet of things (NB-loT) device, Machine Type Communication (MTC) device, Device to Device (D2D) terminal, or node e.g. smart phone, laptop, smart watch, wearable for tactile augmentation or sensory enhancement, industrial robot, Unmanned Aerial Vehicle, mobile phone, sensor, relay, mobile tablets or even a small base station capable of communicating using radio communication with a radio network node within an area served by the radio network node.

[0618] The communication network 1 comprises a first radio network node 12 or just radio network node, providing radio coverage over a geographical area, a first service area 11 or first cell, of a first radio access technology (RAT), such as NR, LTE, or similar. The radio network node 12 may be a transmission and reception point such as an access node, an access controller, a base station, e.g. a radio base station such as a gNB, an eNB, a NodeB, a base transceiver station, a radio remote unit, an Access Point Base Station, a base station router, a Wireless Local Area Network (WLAN) access point or an Access Point Station (AP STA), a transmission arrangement of a radio base station, a stand-alone access point or any other network unit or node capable of communicating with a UE within the area served by the first radio network node 12 depending e.g. on the first radio access technology and terminology used. The first radio network node 12 may be referred to as a master node, or a serving radio network node wherein the service area may be referred to as a serving cell, and the serving radio network node communicates with the UE 10 in form of DL transmissions to the UE 10 and UL transmissions from the UE 10. It should be noted that a service area may be denoted as cell, beam, beam group or similar to define an area of radio coverage.

[0619] The communication network 1 comprises a second radio network node 13 or just radio network node, providing radio coverage over a geographical area, a second service area 14 or second cell, of a second RAT, such as 6G, NR, LTE, or similar. The second radio network node 13 may be a transmission and reception point such as an access node, an access controller, a base station, e.g. a radio base station such as a gNB, an eNB, a NodeB, a base transceiver station, a radio remote unit, an Access Point Base Station, a base station router, a WLAN access point or an AP STA, a transmission arrangement of a radio base station, a stand-alone access point or any other network unit or node capable of communicating with a UE within the area served by the second radio network node 13 depending e.g. on the second RAT and terminology used. The second radio network node 13 may be referred to as a secondary radio network node, wherein the service area may be referred to as a secondary cell, and the second radio network node 13 communicates with the UE 10 in form of DL transmissions to the UE 10 and UL transmissions from the UE 10. It should be noted that a service area may be denoted as cell, beam, beam group or similar to define an area of radio coverage.

[0620] The first RAT may be the same RAT as the second RAT or the first RAT may be a different RAT than the second RAT.

[0621] Each radio network node 12,13 may comprise a CU and one or more DUs, and may furthermore comprise a CU-CP and / or CU-UP.

[0622] According to embodiments herein a radio network node 120, such as the second radio network node 13 or the first radio network node 12, groups the UE 10 into a group upon connection establishment based on one or more connection properties, e.g., frequency band of MCG and / or SCG, cell bandwidth, number of MIMO layers, and / or cell load. The radio network node 120 further selects a connection specific configuration for the UE 10 (or per UE) based on information related to the group. The configuration may be either used internally in the radio network node 120 or sent to the UE 10 via RRC.

[0623] By providing a connection specific configuration for each connection, embodiments herein provide optimal network performance for different use cases. Based on the used connection properties in evaluation of the cell group categorization, it provides, for example, the SCG with information of MCG in case of dual connectivity. Fig. 16 is a combined flow chart and signaling scheme according to some embodiments, wherein the radio network node 120 comprises a CU-CP 121 and a CU-UP or a DU 122.

[0624] Action 1601. The radio network node 120, such as the CU-CP 121 , groups the UE 10 into a group of UEs upon connection establishment based on one or more the connection properties, e.g., a frequency band of MCG and / or SCG, a cell bandwidth, a number of MIMO layers, and / or a cell load. The radio network node 120 may evaluate a Cell Group Category based on the one or more connection properties.

[0625] Action 1602. The radio network node 120 may further provide information related to the group of the UE to CU-CP, CU-UP, and / or DU 122 for connection specific configuration selection. The provided information may comprise a Cell Group Category identifier and may be distributed in the radio network node 120 to the CU-CP 121 , CU-UP, and / or DU 122 for connection specific configuration selection.

[0626] Action 1603. The radio network node 120 selects the connection specific configuration per UE based on the information related to the group. For example, the CU-CP 121 , CU-UP, and / or DU 122 (as shown) may select the connection specific configuration per UE based on the Cell Group Category identifier.

[0627] Action 1604. The radio network node 120, such as the CU-CP 121 , CU-UP, and / or DU 122 (as shown), may further use the selected connection specific configuration internally in the radio network node 120 and / or send the connection specific configuration to the UE 10 via RRC.

[0628] Figure 17A shows an overview according to some embodiments herein.

[0629] 1 . Cell Group Category evaluation may be triggered at UE connection establishment and modification

[0630] 2. Cell Group Category may be evaluated for a particular UE, such as UE 10, in the CU-CP 121 based on any of the connection properties, e.g., the frequency band of MCG and / or SCG, the cell bandwidth, the number of MIMO layers, or the cell load.

[0631] 3. Cell Group Category information may be distributed in the radio network node 120 to CU- CP 121 , CU-UP, and DU 122 so that the Cell Group Category information may be used for connection specific configuration selection.

[0632] 4. Connection specific configuration per UE is selected based on the Cell Group Category information. The connection specific configuration may be either used internally in the radio network node 120 or sent to the UE 10 via RRC.

[0633] Embodiments herein make it possible to adjust functionality parameters in the connection specific configuration based on the connection property or properties, which are network parameters that have impact on expected UE performance. Hence, a performance which is close to the performance of a network with separate radio network nodes for cells of different bands may be achieved within the same radio network node 120 with cell group categories, since there would be different settings available for each cell group category.

[0634] Connection properties of the UE 10 may be used to form category criteria or criterion which then is used to evaluate and identify cell group category for the particular UE 10 for each connection setup or modification.

[0635] Resulting cell group category may be propagated via E1AP or F1AP to CU-CP 121 and DU 122, respectively, or may be utilized in CU-UP 122.

[0636] Next step according to embodiments herein may be to use the identified cell group category information to select most suitable parameter settings of the targeted feature for the UE 10. This selection may be done in CU-CP 121 , CU-UP 122, or in DU 122 depending on the where the selection feature that makes use of embodiments herein is handled. Embodiments herein provide a generic functionality that may be used by any feature where the goal is to perform parameter selection based on Cell Group Category. Actions of some embodiments herein are as follows, see Fig. 17B:

[0637] Use required connection information from relevant stored parameters as input, action 171

[0638] Evaluate one or more Category Criteria to determine Cell Group Category, action 172

[0639] - Select the most suitable feature parameters based on the one or more Category Criteria, action 173.

[0640] Based on the connection properties used in one or more category criteria, as one of the important contributions of embodiments herein, the radio network node 120, such as a SN, is provided with information on, e.g., MCG to be able to evaluate Cell Group Category to address the lack of information about the other cell group during dual connectivity.

[0641] Fig. 18 shows that only two radio network nodes 120, such as gNBs, are needed for individual configuration per connection scenario when embodiments herein are deployed.

[0642] Embodiments herein may utilize MOM parameters from internal and external cells as input variables and produces a category based on the connection which is then used to select a feature parameter set. This makes it possible to apply different configurations to UE connections based on their connection and / or band type. This solution is designed to be used by any feature where the goal is to perform profile selection based on Cell Group Category.

[0643] Cell Group Category evaluation may be done in the CU-CP 121 and produce the output as cell group category which may then be used for selection of feature attributes. Depending on the feature that makes use of Cell Group Category evaluation, the selection of feature attributes may be done both in either in CU-CP 121 or CU-UP 122. A new Managed Object (MO) class - CellGroupCategoryDefinition holding MO attribute cell group category - cgCategory - may be introduced as a child of GNBCUCPFunction. Identified cgCategory represents the category based on the connection information used in categorycriteria for the particular UE 10. cgCategory may then be utilized to select feature attributes. New or updated cgCategory from the Cell Group Category evaluation may be performed in radio control function (RCF) and distributed to relevant features that differentiated configuration selection using Cell Group Categorization is desired.

[0644] Introduction of CellGroupCategoryDefinition MO Class in CU-CP is shown in Fig. 19, wherein Fig. 19 shows CU-CP MOM Target.

[0645] New MO Class CellGroupCategoryDefinition holds an MO attribute categorycriteria of type string to determine cgCategory to be sent to relevant functionalities that make use of Cell Group Category Evaluation. It may be possible to use relational operators for these variables. The syntax of categorycriteria is defined in Backus-Naur form and may be defined as follows:

[0646] MOM target incorporating the algorithm to perform configuration selection based on Cell Group Category is shown in Fig. 20.

[0647] <Profile>Cfg and <Profile>CgCatCfg MO Classes model configuration attributes that may be set differently for UEs, such as the UE 10, depending on the cell group category they belong to. This is achieved by using the attribute cgCategoryList.

[0648] This MOM structure may be placed in the MOM wherever cell group category specific configuration is needed. cgCategory may be used to form cgCategoryList and to determine which configuration instance should be selected. Therefore, from each configuration instance there exists a reference to user plane profile instances. Hence, the cardinality of the user plane profile may be increased and made sure that there exists one set of configuration instances. <Feature configuration attributes> may be the configuration parameters that are determined based on the cgCategory identifiers and cell group categories. It is herein disclosed a decision flow that determines the Cell Group Category information for a particular UE such as the UE 10. Each instance of a cell group category may be defined by one or more category criteria.

[0649] Input:

[0650] Connection properties of a particular UE. categorycriteria is defined as:

[0651] CellGroupCategoryDefinition::categoryCriteria

[0652] Output:

[0653] Cell group category (cgCategory) .

[0654] Decision flow:

[0655] In order to determine the cell group category, evaluation is done based on the categorycriteria.

[0656] • CellGroupCategoryDefinition::categoryCriteria

[0657] • The category criteria evaluation is done per UE for the current connection information

[0658] • Connection of the UE 10 belongs to a cell group category if the category criterion or criteria is evaluated to true for the UE 10.

[0659] • Empty category criterion or criteria, or empty expressions in category criterion or criteria may always be evaluated to true.

[0660] • A Variable Expression evaluates to Unknown if a particular connection information variable value of the UE 10 is not known or if the variable value is not valid.

[0661] • A Variable Expression evaluates to True or False if a particular connection information variable value for the UE 10 is known and valid.

[0662] • The logical operators And, Or and Not, that may be part of a category criterion or criteria, apply three-way logic as defined below:

[0663] F=False; T=True; U=Unknown.

[0664] A=Evaluation result of Expression List or Variable Expression.

[0665] B=Evaluation result of Expression List or Variable Expression. • If category criteria and / or criterion is evaluated to True, then cell group category is assigned to the UE 10:

[0666] 1 . CellGroupCategoryDefinition::cgCategory

[0667] • If connection information of the UE 10 does not match any category criterion, it is associated with the base category instance or category type:

[0668] 1 . cgCategory = 0

[0669] A decision flow may describe how the radio network node 120 selects cell group category specific parameters.

[0670] MO Class: <Profile>CgCatCfg

[0671] Input:

[0672] • Cell group category information as assigned to the UE 10 by the decision flow “Determine Cell Group Category”

[0673] 1 . cgCategory

[0674] • CgCatCfg MO class for which the selection shall be done

[0675] Output:

[0676] • Selected CgCatCfg MO instance

[0677] Decision Flow:

[0678] Select cell group category configuration instance with the following set of criterion or criteria:

[0679] • There is at least one cell group category configuration instance MO.

[0680] 1 . If there is no cell group category configuration instance MO, then attribute default values according to MO definitions of the feature may be used to create a base configuration instance.

[0681] • Select matching one among cell group category configuration instance MOs based on cell group category information. Corresponding MO for a cell may be found in the following order:

[0682] 1 . Select a cell group category configuration instance MO with matching cgCategory in cgCategoryList

[0683] 2. Select Base cell group category configuration instance MO

[0684] The base configuration instance, i.e. , the default instance MO containing the standard data for a cell group category configuration, may be created automatically as long as the parent MO is created. cgCategoryList of base configuration instance may not be populated, only allowing an empty list meaning ‘all not otherwise specified’.

[0685] Example Use Case: Selection of PDCP parameters based on Cell Group Category. An example use case is presented to demonstrate how some embodiments herein work where the goal is to select the most suitable User Plane Profile instances based on the cell group category evaluation for differentiated PDCP parameters, such as frequency band and / or radio parameters. As connection properties, PCell and / or PSCell frequencies are used within category criterion or criteria for evaluation of the cell group category. To this end, another aspect of the embodiments herein is that it addresses the lack of information about the other cell group during dual connectivity. Addition of PCell ID to the information exchange during NR-DC may allow the radio network node 120, such as a secondary gNB, to make better decisions. Connection properties of the UE 10, such as UL and / or DL frequency parameters of the PCell and / or PSCell with PCell ID, form the category criterion or criteria - categorycriteria - to be used to identify cgCategory.

[0686] Actions of embodiments may be adapted for this use case as follows in Fig. 21 : Figure 21 shows actions for choosing UserPlaneProfile instance.

[0687] Use MOM parameters from internal and external cells as input, action 2101 Determine cgCategory in CU-CP 121 , action 2102

[0688] - Send cgCategory to CU-UP 122 over E1AP, action 2103

[0689] - Select a UserPlaneProfileCgCatCfg instance based on cgCategory, action 2104.

[0690] The framework may work as follows: frequency parameters from NRCelICU, ExternalNRCelICU, ExternalEUtranCell, PCell ID from S-Node Addition Request, and PSCell information from the PSCell selection may be used as inputs to produce the cell group category as an output to be propagated to the features that utilizes cgCategory to make the selection of the most suitable feature attribute for a particular connection.

[0691] Input:

[0692] Extern alNRCellCU / ExternalEUtranCell

[0693] UL / DL frequency parameters

[0694] PCell ID

[0695] NRCelICU

[0696] UL / DL frequency parameters categorycriteria

[0697] Output: cgCategory

[0698] Above shows categoryCiteria modified for PCell and PSCell frequency variables

[0699] As an example, categorycriteria may be used as:

[0700] CellGroupCategoryDefinition.categoryCriteria = PCellDIFreq>2.5e9 && PCellDIFreq<2.8e9 to check whether the PCell DL frequency is between 2.5 GHz and 2.8 GHz.

[0701] There may be cases where both PCell and PSCell frequencies are available or PSCell is not available before dual connectivity is configured. Then, the case before dual connectivity configuration may be evaluated as unknown for PSCell frequency in categorycriteria.

[0702] Cell attributes for the cells contained in X2 / Xn Setup Request may be stored in MOM ExternalEUtranCell / ExternalNRCelICU and frequency parameters for PCell and PSCell may be read during S-Node Addition process in case of dual connectivity. Therefore, PCell ID may be sent to the secondary node during S-Node Addition and / or S-Node Modification procedures.

[0703] Following the determination of new and / or updated cgCategory in CU-CP 121 , the new and / or updated cgCategory may be distributed from CU-CP 121 , or RCF, to CU-UP 122, or packet processing function (PPF), over E1 interface via BEARER CONTEXT SETUP REQUEST and BEARER CONTEXT MODIFICATION REQUEST. Setup and / or modification may occur in a few cases such as :

[0704] New UE,

[0705] Additional protocol data unit (PDU) sessions and / or data radio bearers (DRB),

[0706] During mobility,

[0707] RRC re-establish / resume from RRC inactive state

[0708] To be able to select UserPlaneProfile instances based on cell group category evaluation, MOM structure may be updated as shown in Fig. 22 - CU-CP MOM target to select UserPlaneProfile based on cgCategory

[0709] To be able to choose the most suitable User Plane Profile instance based on Cell Group Category of a particular connection, “UserPlaneProfile” may be used for “<Profile>”. As a first step, CU-UP-may select UserPlaneProfile based on cgCategory which may be received via E1AP during bearer setup and / or modify procedures. If no UserPlaneProfile comprises requested cgCategory, a default UserPlaneProfile may be selected according to the corresponding decision flow in Fig. 22.

[0710] The method actions performed by the radio network node 120 for handling communication of the UE 10 in the communication network, for example, handling configuration of the UE 10, according to embodiments herein will now be described with reference to a flowchart depicted in Fig. 23. The actions do not have to be taken in the order stated below, but may be taken in any suitable order. Actions performed in some embodiments are marked with dashed boxes.

[0711] Action 2300. The radio network node 120 may establish a connection to the UE 10.

[0712] Action 2301 . The radio network node 120, such as the CU-CP 121 , groups the UE 10 into the group of UEs upon connection establishment based on the one or more connection properties. The one or more connection properties may comprise e.g., the frequency band of MCG and / or SCG, the cell bandwidth, the number of MIMO layers, and / or the cell load. The radio network node 120 may evaluate a Cell Group Category based on the one or more connection properties.

[0713] Action 2302. The radio network node 120 may further provide the information related to the group of the UE 10 to the CU-CP 121 , the CU-UP 122, and / or the DU 122 of the radio network node 120 for selecting the connection specific configuration, i.e., so that the CU-CP 121 , CU-UP 122, and / or DU 122 may use it for configuration selection. The provided information may comprise Cell Group Category identifier and may be distributed in the radio network node 120 to the CU-CP

[0714] 121 , CU-UP 122, and / or DU 122 for connection specific configuration selection.

[0715] Action 2303. The radio network node 120 selects the connection specific configuration for the UE 10 based on the information related to the group. For example, the CU-CP 121 , CU-UP

[0716] 122, and / or DU 122 may select the connection specific configuration per UE based on the Cell Group Category identifier.

[0717] Action 2304. The radio network node 120 may further use the selected connection specific configuration internally in the radio network node 120 and / or send the connection specific configuration to the UE 10, for example, sent via RRC.

[0718] Fig. 24 is a block diagram depicting the radio network node 120, such as a first 12 or the second radio network node 13, for handling communication of the UE 10 in the communication network 1 according to embodiments herein.

[0719] The radio network node 120 may comprise processing circuitry 2401 , e.g. one or more processors, configured to perform the methods herein.

[0720] The radio network node 120, such as the CU-CP 121 , and / or the processing circuitry 2401 is configured to group the UE 10 into the group upon connection establishment based on the one or more connection properties, e.g., the frequency band of the MCG and / or the SCG, the cell bandwidth, the number of MIMO layers, and / or the cell load. The radio network node 120 and / or the processing circuitry 2401 may be configured to evaluate the Cell Group Category based on the one or more connection properties.

[0721] The radio network node 120 and / or the processing circuitry 2401 may be configured to provide the information related to the group of the UE 10 to CU-CP 121 , CU-UP 122, and / or DU 122 for selecting the connection specific configuration, i.e., so that the CU-CP 121 , CU-UP 122, and / or DU 122 may use it for configuration selection. The provided information may comprise Cell Group Category identifier and may be distributed in the radio network node 120 to the CU-CP 121 , CU-UP 122, and / or DU 122 for connection specific configuration selection.

[0722] The radio network node 120 and / or the processing circuitry 2401 is configured to select the connection specific configuration for the UE 10 based on the information related to the group. The CU-CP 121 , CU-UP 122, and / or DU 122 may be configured to select the connection specific configuration for the UE 10 based on the Cell Group Category identifier.

[0723] The radio network node 120 and / or the processing circuitry 2401 may be configured to use the selected connection specific configuration internally in the radio network node 120 and / or send the connection specific configuration to the UE 10, e.g., via RRC.

[0724] The radio network node 120 may comprise a memory 2405. The memory 2405 comprises one or more units to be used to store data on, such as data packets, indications, messages, groups, UEs, connection properties, connection specific configurations, further indications, information, events and applications to perform the methods disclosed herein when being executed, and similar. Furthermore, the radio network node 120 may comprise a communication interface 2406 such as comprising a transmitter, a receiver, a transceiver and / or one or more antennas.

[0725] The methods according to the embodiments described herein for the radio network node 120 are respectively implemented by means of e.g. a computer program product 2407 or a computer program, comprising instructions, i.e., software code portions, which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the radio network node 120. The computer program product 2407 may be stored on a computer-readable storage medium 2408, e.g., a disc, a universal serial bus (USB) stick or similar. The computer-readable storage medium 2408, having stored thereon the computer program product, may comprise the instructions which, when executed on at least one processor, cause the at least one processor to carry out the actions described herein, as performed by the radio network node 120. In some embodiments, the computer-readable storage medium may be a transitory or a non-transitory computer-readable storage medium. Thus, embodiments herein may disclose the radio network node 120 for handling communication of the UE 10 in a communication network, wherein the radio network node 120 comprises processing circuitry and a memory, said memory comprising instructions executable by said processing circuitry whereby said radio network node 120 is operative to perform any of the methods herein.

[0726] In some embodiments a more general term “network node” is used and it can correspond to any type of radio-network node or any network node, which communicates with a UE and / or with another network node.

[0727] In some embodiments the non-limiting term wireless device or user equipment (UE) is used and it refers to any type of wireless device communicating with a network node and / or with another wireless device in a cellular or mobile communication system. Examples of UE are target device, device to device (D2D) UE, proximity capable UE (aka ProSe UE), loT capable device, machine type UE or UE capable of machine to machine (M2M) communication, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles etc.

[0728] Embodiments are applicable to any RAT or multi-RAT systems, where the wireless device receives and / or transmit signals (e.g. data) e.g. NR, Wi-Fi, LTE, LTE-Advanced, Wideband Code Division Multiple Access (WCDMA), Global System for Mobile communications / enhanced Data rate for GSM Evolution (GSM / EDGE), Worldwide Interoperability for Microwave Access (WiMax), or Ultra Mobile Broadband (UMB), just to mention a few possible implementations.

[0729] As will be readily understood by those familiar with communications design, that functions means or circuits may be implemented using digital logic and / or one or more microcontrollers, microprocessors, or other digital hardware. In some embodiments, several or all of the various functions may be implemented together, such as in a single application-specific integrated circuit (ASIC), or in two or more separate devices with appropriate hardware and / or software interfaces between them. Several of the functions may be implemented on a processor shared with other functional components of a wireless device or network node, for example.

[0730] Alternatively, several of the functional elements of the processing means discussed may be provided through the use of dedicated hardware, while others are provided with hardware for executing software, in association with the appropriate software or firmware. Thus, the term “processor” or “controller” as used herein does not exclusively refer to hardware capable of executing software and may implicitly include, without limitation, digital signal processor (DSP) hardware and / or program or application data. Other hardware, conventional and / or custom, may also be included. Designers of communications devices will appreciate the cost, performance, and maintenance trade-offs inherent in these design choices.

[0731] Any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses. Each virtual apparatus may comprise a number of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory (RAM), cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and / or data communications protocols as well as instructions for carrying out one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more embodiments of the present disclosure.

[0732] Fig. 25 shows an example of a communication system 15100 in accordance with some embodiments.

[0733] In the example, the communication system 15100 includes a telecommunications network 15102 that includes an access network 15104, such as a radio access network (RAN), and a core network 15106, which includes one or more core network nodes 15108. The access network 15104 includes one or more access network nodes or base stations of various types, access network nodes 15110A and 15110B are depicted (which may be collectively referred to as network nodes 15110 being examples of the radio network node 120), or any other similar 3rdGeneration Partnership Project (3GPP) access nodes or non-3GPP access points (APs). Some embodiments of the access network 15104 may include more than one access network technology. The network nodes 15110 of access network 15104 facilitate direct or indirect connection of wireless devices, also referred to as UEs, such as by connecting UEs 15112A, 15112B, 15112C, and 15112D (one or more of which may be generally referred to as UEs 15112 being examples of the UE 10) to the core network 15106 over one or more wireless connections.

[0734] Moreover, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunications network 15102 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a network node in the telecommunications network 15102 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other network nodes to implement one or more functionalities of any network node in the telecommunications network 15102, including one or more access network nodes 15110 and / or core network nodes 15108.

[0735] Examples of an ORAN network node include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O-CU-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). An ORAN network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an A1 , F1 , W1 , E1 , E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN network node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an 0-2 interface defined by the O- RAN Alliance or comparable technologies.

[0736] The network nodes 15110 facilitate direct or indirect connection of one or more UEs 15112 to the core network 15106 over one or more wireless connections. Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 15100 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system 15100 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0737] The UEs 15112 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes 15110 and other communication devices. Similarly, the network nodes 15108, 15110 are arranged, capable, configured, and / or operable to communicate directly or indirectly (e.g., via other devices of telecommunications network 15102) with the UEs 15112 and / or with other network nodes or equipment in the telecommunications network 15102 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunications network 15102. More specifically, UEs 15112 may send messages, data, and / or other signals to network nodes 15108, 15110 or other elements of the telecommunications network 15102 by transmitting such signals to the relevant device directly without the signals passing through any intervening devices or by transmitting such signals to the relevant device indirectly through an intervening device (or multiple intervening devices) that then transmit the signal to the relevant device. Similarly, network nodes 15108, 15110 may send messages, data, and other signals to UEs 151122, other network nodes 15108, 15110, and other devices in telecommunications network 15102 directly or indirectly. As one specific example, a core network node 108 may transmit a particular message to a UE 15112 by transmitting the message to an access network node 15110 that will then transmit the message to the intended UE 15112. Similarly, a core network node 108 may receive a particular message from a UE 15112 by receiving the message from an access network node 15110 that itself received the message from the UE 15112.

[0738] In the depicted example, the core network 15106 connects elements of the access network 15104 (e.g., one or more of the network nodes 15110) to one or more host computing systems, such as host 15116. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 15106 includes one or more core network nodes (e.g., core network node 15108) of various types, one or more of which may be generally referred to as network nodes 15108. Network nodes 15108 are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, access network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 15108. Example core network nodes provide functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier Deconcealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[0739] The host 15116 may be under the ownership or control of a service provider other than an operator or provider of the access network 15104 and / or the telecommunications network 15102. The host 15116 may be operated by the service provider or on behalf of the service provider. The host 15116 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

[0740] As a whole, the communication system 15100 of Figure 25 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system 15100 may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (Wi-Fi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (Wi-Max), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, Li-Fi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox. Moreover, the communication system 15100 may be configured to support multiple different standards, protocols, or other rule sets, with individual components supporting all of the relevant rule sets or with different components or sub-systems within the communication system 15100 supporting different standards, protocols, or rule sets.

[0741] As one example, in certain embodiments, access network 15104 may contain some access network nodes 15110 that support 3GPP radio access technologies (RAT), such as LTE or NR, while other access network nodes 15110 support (or the same access network nodes 15110 additionally support) non-3GPP RATs, such as Wi-Fi or a proprietary RAT. As another example, telecommunications network 15102 may support multiple generations of related communication standards (e.g., 4G and 5G 3GPP communication standards) and, as a result, may include an access network 104 and / or a core network 106 that supports multiple different standard generations or may include multiple access networks 104 and / or multiple core networks 106 with individual networks 104, 106 supporting different standard generations.

[0742] Telecommunications network 15102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunications network 15102. For example, the telecommunications network 15102 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC) / Massive loT services to yet further UEs.

[0743] In some examples, one or more of the UEs 15112 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 15104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 15104. Additionally, a UE may be configured for operating in single- or multi-RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).

[0744] In the example, the hub 15114 communicates with the access network 15104 to facilitate indirect communication between one or more UEs (e.g., UE 15112C and / or 15112D) and network nodes (e.g., network node 15110B). In some examples, the hub 15114 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 15114 may be a broadband router enabling access to the core network 15106 for the UEs. As another example, the hub 15114 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 15110, or by executable code, script, process, or other instructions in the hub 15114. As another example, the hub 15114 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 15114 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 15114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 15114 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 15114 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.

[0745] The hub 15114 may have a constant / persistent or intermittent connection to the network node 15110B. The hub 15114 may also allow for a different communication scheme and / or schedule between the hub 15114 and UEs (e.g., UE 15112C and / or 15112D), and between the hub 15114 and the core network 15106. In other examples, the hub 15114 is connected to the core network 15106 and / or one or more UEs via a wired connection. Moreover, the hub 15114 may be configured to connect to an M2M service provider over the access network 15104 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 15110 while still connected via the hub 15114 via a wired or wireless connection. In some embodiments, the hub 15114 may be a dedicated hub - that is, a hub whose primary function is to route communications to / from the UEs from / to the network node 15110B. In other embodiments, the hub 15114 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 15110B, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0746] Fig. 26 is another example of a communication system 15200 according to some embodiments. As used herein, the communication system 15200 includes multiple access points (APs) 15210 (with four exemplary APs 15210A, 15210B, 15210C, and 15210D being depicted) and multiple wireless devices, referred to in the context of communication system 15200 as stations (STAs) 15212 (referred to individually as STA 15212A, STA 15212B, STA 15212C, STA 15212D, and STA 15212E). STA 15212A is served by AP 15210A in a first basic service set (BSS) 15220A. STA 15210B and STA 15210C are served by AP 15210B in a second BSS, BSS 15220B. STA 15212D is served by AP 15210C in a third BSS, BSS 15220C. STA 15212E is served by AP 15210D in a fourth BSS, BSS 15220D. Stations 15212 may be non-AP STAs and correspond to various kinds of wireless devices, for example, user terminals, such as mobile or stationary computing devices like smartphones, laptop computers, desktop computers, tablet computers, gaming devices, head-mounted displays (HMDs) for Augmented Reality (AR) or Virtual Reality (VR), or the like. Further, stations 15212 could, for example, correspond to other kinds of equipment like smart home devices, printers, multimedia devices, data storage devices, or the like. Each of STAs 15212 may connect through a radio link to one of APs 15210. For example, depending on location or channel conditions experienced by a given STA 15212, the STA may select an appropriate AP and BSS for establishing the radio link. The radio link may be based on one or more orthogonal frequency-division multiplexing (OFDM) carriers from a frequency spectrum that is shared on the basis of a contention-based mechanism, e.g., an unlicensed or license exempt band like 2.4 GHz Industrial, Scientific, and Medical (ISM) band, the 5 GHz band, the 6 GHz band, or the 60 GHz band.

[0747] Each AP 15210 may provide data connectivity to STAs 15212 connected to a particular AP 15210. As illustrated, APs 15210 may be connected to a data network 15230. In this way, APs 15210 may also provide data connectivity between STAs 15212 and other entities, e.g., to one or more servers, service providers, data sources, data sinks, user terminals, or the like. Accordingly, the radio link established between a given STA 15212 and its serving AP 15210 may be used for providing various kinds of services to STA 15212, e.g., a voice service, a multimedia service, or other data service. Such services may be based on applications that are executed on STA 15212 and / or on a device linked to STA 15212. By way of example, Figure 26 illustrates an application service platform 15232 provided in data network 15230. The application(s) executed on STA 15212 and / or on one or more other devices linked to STA 15212 may use the radio link for data communication with one or more other STA 15212 and / or the application service platform 15232, thereby enabling utilization of the corresponding service(s) at STA 15212.

[0748] Fig. 27 shows a wireless device 15300 being example of the UE 10, which may be configured to operate in communication system 15100 of Figure 25 or in communication system 15200 of Figure 26. The wireless device 15300 may be alternatively referred to as a UE 15300, like a UE 15112 within the context of communication system 15100, or as a station (STA) 15300 or as a non-access-point station (non-AP STA) 15300, like a STA 15212 within the context of the communication system 15200, in accordance with respective embodiments. As used herein, a wireless device refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other wireless devices. Examples of a wireless device include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle, vehicle-mounted or vehicle embedded / integrated wireless device, and wireless terminal. Other examples include any type of UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-loT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE. A wireless device 15300 may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to- everything (V2X). In other examples, wireless device 15300 may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, wireless device 15300 may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, wireless device 15300 may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).

[0749] In particular embodiments, wireless device 15300 includes processing circuitry 15302 that is operatively coupled via a bus 15304 to an input / output interface 15306, a power source 15308, a memory 15310, a communication interface 15312, and / or any other component, or any combination thereof. Certain embodiments of wireless device 15300 may include all or a subset of the components shown in Figure 27. The level of integration between the components may vary from one embodiment of wireless device 15300 to another. In general, in a particular embodiment of wireless device 15300, processing circuitry 15302, input / output interface 15306, power source 15308, memory 15310, and communication interface 15312 may, in whole or in part, represent or include physical components common to or shared by one or more of the other elements of wireless device 15300. Further, certain embodiments of wireless devices 15300 may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0750] The processing circuitry 15302 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 15310. The processing circuitry 15302 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 15302 may include multiple central processing units (CPUs).

[0751] In the example, the input / output interface 15306 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into wireless device 15300. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.

[0752] In some embodiments, the power source 15308 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used to supply power to circuitry or to charge an associated battery. The power source 15308 may further include power circuitry for delivering power from the power source 15308 itself, and / or an external power source, to the various parts of wireless device 15300 via input circuitry or an interface such as an electrical power cable. Power source 15308 may perform any formatting, converting, or other modification to make accessible power suitable for the respective components of the wireless device 15300 to which power is supplied.

[0753] The memory 15310 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 15310 includes one or more programs 15314, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 15316. The memory 15310 may store, for use by wireless device 15300, any of a variety of various operating systems or combinations of operating systems.

[0754] The memory 15310 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or IS IM , other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUlCC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 15310 may allow wireless device 15300 to access instructions, programs and the like, stored on transitory or non- transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 15310, which may be or comprise a device-readable storage medium.

[0755] The processing circuitry 15302 may be configured to communicate with an access network or other network via or using the communication interface 15312. The communication interface 15312 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 15322. The communication interface 15312 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another wireless device or a network node in an access network). Each transceiver may include a transmitter 15318 and / or a receiver 15320 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 15318 and receiver 15320 may be coupled to one or more antennas (e.g., antenna 15322) and may share circuit components, software or firmware, or alternatively be implemented separately.

[0756] In the illustrated embodiment, communication functions of the communication interface 15312 may include cellular communication, Wi-Fi communication (e.g., according to an IEEE 802.11 family standard), LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented according to one or more communication protocols and / or standards, such as IEEE 802.11 , Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / internet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0757] In particular embodiments, wireless device 15300 may provide an output of data captured via a sensor, through its communication interface 15312, via a wireless connection to a network node, and / or in any appropriate manner. Data captured by sensors of a wireless device 15300 can be communicated through a wireless connection to a network node via another wireless device 15300. In particular embodiments, such output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

[0758] As another example, wireless device 15300 comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, wireless device 15300 may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.

[0759] Wireless device 15300, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. In particular embodiments, wireless device 15300 represents an loT device that comprises circuitry and / or software in dependence of the intended application of the loT device in addition to other components as described in relation to the example embodiment of wireless device 15300 shown in Figure 27.

[0760] As yet another specific example, in an loT scenario, wireless device 15300 may represent a machine or other device that performs monitoring and / or measurements, and transmits the results of such monitoring and / or measurements to another wireless device and / or a network node. Wireless device 15300 may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, wireless device 15300 may implement the 3GPP NB-loT standard. In other scenarios, wireless device 15300 may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.

[0761] In practice, any number of wireless devices 15300 may be used together with respect to a single use case. For example, a first wireless device 15300 might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second wireless device 15300 that is a remote controller operating the drone. When a user makes changes from the remote controller, the first wireless device 15300 may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone’s speed. The first and / or the second wireless device 15300 can also include more than one of the functionalities described above. For example, wireless device 15300 might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators. Fig. 28 shows a network node 15400, being example of the radio network node 120, in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunications network. In accordance with respective embodiments, network node 15400 may be configured to operate in communication system 15100 of Figure 25, like network nodes 15108 or 15110, or in communication system 15200 of Figure 26, like an AP 15210 or a station 15212. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)), O-RAN nodes or components of an O-RAN node (e.g., O-RU, O-DU, O-CU).

[0762] Network nodes 15400 may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. Network node 15400 may be a relay node or a relay donor node controlling a relay. Network nodes 15400 may also include one or more (or all) parts of a distributed radio base station such as centralized digital units, distributed units (e.g., in an O-RAN access node) and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

[0763] Other examples of network nodes 15400 include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, SelfOrganizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).

[0764] In particular embodiments, network node 15400 includes a processing circuitry 15402, a memory 15404, a communication interface 15406, and a power source 15408. In general, in a particular embodiment of network node 15400, processing circuitry 15402, memory 15404, communication interface 15406, and power source 15408 may, in whole or in part, represent or include physical components common to or shared by one or more of the other elements of network node 15400.

[0765] The network node 15400 may be composed of multiple distinct network entities (e.g., a NodeB entity and a RNC entity, or a BTS entity and a BSC entity, etc.), which may each have or utilize their own respective physical components. In certain scenarios in which the network node 15400 comprises multiple such entities (e.g., BTS and BSC), one or more of the separate entities may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 15400 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memories 15404 or portions of memory 15404 for different RATs) and some components may be reused (e.g., a same antenna 15410 may be shared by different RATs). The network node 15400 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 15400, for example GSM, WCDMA, LTE, NR, Wi-Fi (e.g., according to an IEEE 802.11 family standard), Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 15400.

[0766] The processing circuitry 15402 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operable to provide, either alone or in conjunction with other components, such as the memory 15404, to provide network node 15400 functionality.

[0767] In some embodiments, the processing circuitry 15402 includes a system on a chip (SOC). In some embodiments, the processing circuitry 15402 includes one or more of radio frequency (RF) transceiver circuitry 15412 and baseband processing circuitry 15414. In some embodiments, the RF transceiver circuitry 15412 and the baseband processing circuitry 15414 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 15412 and baseband processing circuitry 15414 may be on the same chip or set of chips, boards, or units.

[0768] The memory 15404 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or nonvolatile, non-transitory device-readable and / or computer-executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry 15402. The memory 15404 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry 15402 and utilized by the network node 15400. The memory 15404 may be used to store any calculations made by the processing circuitry 15402 and / or any data received via the communication interface 15406. In some embodiments, the processing circuitry 15402 and memory 15404 is integrated.

[0769] The communication interface 15406 is used in wired or wireless communication of signaling and / or data with UEs, other network nodes, and / or any other network equipment. In the illustrated embodiment, communication interface 15406 comprises port(s) / terminal(s) 15416 to send and receive data, for example to and from a network over a wired connection. In particular embodiments, network node 15300 may be capable of wireless communication and communication interface 15406 may also include radio front-end circuitry 15418 that may be coupled to, or in certain embodiments a part of, an antenna 15410. Particular embodiments of radio front-end circuitry 15418 include filter(s) 15420 and amplifier(s) 15422. The radio front-end circuitry 15418 may be connected to an antenna 15410 and processing circuitry 15402. The radio front-end circuitry may be configured to condition signals communicated between antenna 15410 and processing circuitry 15402. The radio front-end circuitry 15418 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 15418 may convert the digital data into a radio signal(s) having the appropriate channel and bandwidth parameters using a combination of filters 15420 and / or amplifiers 15422. The radio signal(s) may then be transmitted via the antenna 15410. Similarly, when receiving data, the antenna 15410 may collect radio signals which are then converted into digital data by the radio front-end circuitry 15418. The digital data may be passed to the processing circuitry 15402. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0770] In certain alternative embodiments, network node 15400 may be capable of wireless communication but does not include separate radio front-end circuitry 15418, instead, the processing circuitry 15402 includes radio front-end circuitry and is connected to the antenna 15410. Similarly, in some embodiments, all or some of the RF transceiver circuitry 15412 is part of the communication interface 15406. In still other embodiments, the communication interface 15406 includes one or more ports or terminals 15416, the radio front-end circuitry 15418, and the RF transceiver circuitry 15412, as part of a radio unit (not shown), and the communication interface 15406 communicates with the baseband processing circuitry 15414, which is part of a digital unit (not shown).

[0771] The antenna 15410 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 15410 may be coupled to the radio front-end circuitry 15418 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 15410 is separate from the network node 15400 and connectable to the network node 15400 through one or more interfaces or ports.

[0772] The antenna 15410, communication interface 15406, and / or the processing circuitry 15402 may be configured to perform some or all of the receiving operations and / or obtaining operations described herein as being performed by the network node 15400. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna 15410, the communication interface 15406, and / or the processing circuitry 15402 may be configured to perform some or all of the transmitting or sending operations described herein as being performed by the network node 15400. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.

[0773] The power source 15408 provides power to the various components of network node 15400 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 15408 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 15400 with power for performing the functionality described herein. For example, the network node 15400 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 15408. As a further example, the power source 15408 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

[0774] Embodiments of the network node 15400 may include additional components beyond those shown in Figure 28 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 15400 may include user interface equipment to allow input of information into the network node 15400 and to allow output of information from the network node 15400. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 15400.

[0775] Fig. 29 is a block diagram illustrating a virtualization environment 15500 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 15500 hosted by one or more of hardware nodes, such as a hardware computing device that operates as an access network node, UE, core network node, or host. Further, in embodiments in which a virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment 15500 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an 0-2 interface.

[0776] Applications 15502 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0777] Hardware 15504 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 15506 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VM 15508A and VM 15508B (which may be collectively referred to as VMs 15508), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 15506 may present a virtual operating platform that appears like networking hardware to one or more of the VMs 15508. The VMs 15508 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by virtualization layer 15506. Different embodiments of the instance of a virtual appliance 15502 may be implemented on one or more of VMs 15508, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment. In the context of NFV, each of the VMs 15508 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 15508, and that part of hardware 15504 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more of the VMs 15508 on top of the hardware 15504 and corresponds to an application 15502. Hardware 15504 may be implemented in a standalone network node with generic or specific components. Hardware 15504 may implement some functions via virtualization. Alternatively, hardware 15504 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 15510, which, among others, oversees lifecycle management of applications 15502. In some embodiments, hardware 15504 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 15512 which may alternatively be used for communication between hardware nodes and radio units. Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware. In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer- readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer-readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally. The embodiments herein are not limited to the above described preferred embodiments. Various alternatives, modifications and equivalents may be used. It will be appreciated that the foregoing description and the accompanying drawings represent non-limiting examples of the methods and apparatus taught herein. As such, the apparatus and techniques taught herein are not limited by the foregoing description and accompanying drawings. Instead, the embodiments herein are limited only by the following claims and their legal equivalents.

Claims

CLAIMS1 . A method performed by a radio network node (120) for handling communication of a user equipment, UE, (10) in a communication network, the method comprising:- grouping (2301 ) the UE (10) into a group of UEs upon connection establishment based on one or more connection properties; and- selecting (2303) a connection specific configuration for the UE (10) based on information related to the group.

2. The method according to claim 1 , comprising- providing (2302) the information related to the group of the UE (10) to a central unit control plane, CU-CP, (121 ), a central unit user plane, CU-UP, (122), and / or a distributed unit, DU, (122), of the radio network node (120) for selecting the connection specific configuration.

3. The method according to any of the claims 1 -2, comprising using (2304) the selected connection specific configuration internally in the radio network node (120); and / or sending (2304) the connection specific configuration to the UE (10).

4. The method according to any of the claims 1-3, wherein the one or more connection properties comprise one or more of the following: frequency band of master cell group, MCG, and / or second cell group, SCG; cell bandwidth; number of multiple input multiple output, MIMO, layers; and / or cell load.

5. The method according to any of the claims 1 -4, wherein grouping the UE (10) comprises evaluating a Cell Group Category based on the one or more connection properties6. The method according to claim 5, wherein the provided information comprises Cell Group Category identifier and is distributed in the radio network node (120) to the CU- CP (121), the CU-UP (122), and / or the DU (122) for connection specific configuration selection.

7. A radio network node (120) for handling communication of a user equipment, UE, (10) in a communication network, wherein the radio network node (120) is configured to: group the UE (10) into a group of UEs upon connection establishment based on one or more connection properties; andselect a connection specific configuration for the UE (10) based on information related to the group.

8. The radio network node (120) according to claim 7, wherein the radio network node (120) is configured to: provide the information related to the group of the UE (10) to a central unit control plane, CU-CP, (121), a central unit user plane, CU-UP, (122), and / or a distributed unit, DU, (122), of the radio network node (120) for selecting the connection specific configuration.

9. The radio network node (120) according to any of the claims 7-8, wherein the radio network node (120) is configured to: use the selected connection specific configuration internally in the radio network node (120); and / or send the connection specific configuration to the UE (10).

10. The radio network node (120) according to any of the claims 7-9, wherein the one or more connection properties comprise one or more of the following: frequency band of master cell group, MCG, and / or second cell group, SCG; cell bandwidth; number of multiple input multiple output, MIMO, layers; and / or cell load.11 . The radio network node (120) according to any of the claims 7-10, wherein the radio network node (120) is configured to group the UE (10) by the radio network node (120) being configured to evaluate a Cell Group Category based on the one or more connection properties12. The radio network node (120) according to claim 11 , wherein the provided information comprises Cell Group Category identifier and the radio network node (120) is configured to distribute in the radio network node (120) to the CU-CP (121), the CU-UP (122), and / or the DU (122) for connection specific configuration selection.

13. A computer program product comprising instructions, which, when executed on at least one processor, cause the at least one processor to carry out the method according to any of the claims 1-6, as performed by the radio network node (120).

14. A computer-readable storage medium, having stored thereon a computer program product comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out the method according to any of the claims 1-6, as performed by the radio network node (120).

Images