WO2020032846A1

WO2020032846A1 - Pdu session information over f1 for uplink pdu session ambr traffic policing

Info

Publication number: WO2020032846A1
Application number: PCT/SE2019/050547
Authority: WO
Inventors: Nianshan SHI; Matteo FIORANI
Original assignee: Telefonaktiebolaget Lm Ericsson (Publ)
Priority date: 2018-08-10
Filing date: 2019-06-11
Publication date: 2020-02-13

Abstract

Systems and methods are disclosed herein for uplink Protocol Data Unit (PDU) Session Aggregate Maximum Bit Rate (AMBR) control in a base station having a split architecture in a Radio Access Network (RAN) of a cellular communications system. Embodiments of a method performed by a base station and corresponding embodiments of a base station are disclosed. In some embodiments, a method performed by a base station having a split architecture comprising a Centralized Unit (CU) and a Distributed Unit (DU) comprises sending, from the CU to the DU, PDU session information and an uplink PDU session AMBR for a PDU session. The method further comprises, at the DU, receiving the PDU session information and the uplink PDU session AMBR for the PDU session from the CU storing the PDU session information and the uplink PDU session AMBR for the PDU session.

Description

PDU SESSION INFORMATION OVER FI FOR UPLINK PDU SESSION AMBR

TRAFFIC POLICING

Related Applications

This application claims the benefit of provisional patent application serial number

62/717,308, filed August 10, 2018, the disclosure of which is hereby incorporated herein by reference in its entirety.

Technical Field

The present disclosure relates to a base station in a Radio Access Network (RAN) of a cellular communications system and, more particularly, to uplink Protocol Data Unit (PDU) session Aggregate Maximum Bit Rate (AMBR) traffic policing in a base station.

Background

The current Fifth Generation (5G) Radio Access Network (RAN) architecture is described in Third Generation Partnership Project (3GPP) Technical Specification (TS) 38.401 V15.2.0 as illustrated in Figure 1. The Next Generation (NG) architecture can be further described as follows. The NG RAN (NG-RAN) consists of a set of New Radio (NR) base stations (gNBs) connected to the Fifth Generation Core network (5GC) through the NG interface. A gNB can support Frequency Division Duplexing (FDD) mode, Time Division Duplexing (TDD) mode, or dual mode operation. gNBs can be interconnected through the Xn interface. A gNB may consist of a gNB Centralized Unit (gNB-CU) and one or more gNB Distributed Units (gNB-DUs). A gNB-CU and a gNB-DU are connected via the FI logical interface. One gNB-DU is connected to only one gNB-CU.

NG, Xn, and FI are logical interfaces. For NG-RAN, the NG and Xn-C interfaces for a gNB consisting of a gNB-CU and gNB-DUs terminate in the gNB-CU. For Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Dual Connectivity (EN-DC), the Sl-U and X2-C interfaces for a gNB consisting of a gNB-CU and gNB-DUs terminate in the gNB-CU. The gNB-CU and connected gNB-DUs are only visible to other gNBs and the 5GC as a gNB. The NG-RAN is layered into a Radio Network Layer (RNL) and a Transport Network Layer (TNL). The NG-RAN architecture, i.e. the NG-RAN logical nodes and interfaces between them, is defined as part of the RNL. For each NG-RAN interface (NG, Xn, FI), the related TNL protocol and the functionality are specified in the 3GPP standards. The TNL provides services for User Plane (UP) transport and signaling transport. In NG-Flex configuration, each gNB is connected to all Access and Mobility Management Functions (AMFs) within an AMF Region. The AMF Region is defined in 3GPP TS 23.501.

The general principles for the specification of the FI interface are as follows:

• the FI interface is to be open;

• the FI interface supports the exchange of signaling information between the

endpoints, in addition the interface shall support data transmission to the respective endpoints;

• from a logical standpoint, the FI interface is a point-to-point interface between the endpoints (a point-to-point logical interface should be feasible even in the absence of a physical direct connection between the endpoints);

• the FI interface supports Control Plane (CP) and UP separation;

• the FI interface separates RNL and TNL;

• the FI interface enable exchanges of User Equipment (UE) associated information and non-UE associated information;

• the FI interface is defined to be future proof to fulfil different new requirements, support new services, and new functions;

• one gNB-CU and set of gNB-DUs are visible to other logical nodes as a gNB. The gNB terminates X2, Xn, NG, and Sl-U interfaces; and

• the CU may be separated in CP and UP.

In 5G, a new Quality of Service (QoS) framework is currently being standardized. QoS flows are established between the NG-RAN and the 5GC, where each QoS flow has a defined QoS model. The 5G QoS model supports both QoS flows that require Guaranteed Flow Bit Rate (GBR QoS flows) and QoS flows that do not require guaranteed flow bit rate (Non-GBR QoS Flows). In 5G, the Protocol Data Unit (PDU) session (an association between the UE and a Data Network (DN) that provides a PDU connectivity service) consists of multiple QoS flows (GBR and non-GBR QoS flows). The UE could have multiple PDU sessions. Each PDU session of a UE is associated with the PDU Session Aggregate Maximum Bit Rate (PDU Session-AMBR). The PDU Session-AMBR limits the aggregate bit rate that can be expected to be provided across all Non-GBR QoS flows for a specific PDU session. The PDU Session- AMBR is not applicable to GBR QoS flows.

Each UE is associated with a UE AMBR (UE-AMBR). The UE-AMBR limits the aggregate bit rate that can be expected to be provided across all Non-GBR QoS flows of a UE. Each NG-RAN node sets its UE-AMBR to the sum of the PDU Session-AMBR of all PDU sessions with active UP.

The uplink and downlink aggregate bit rate are controlled separately. The downlink aggregate bit rate control is done in the NG-RAN node and the uplink aggregate bit rate control is done both by the NG-RAN node and the UE.

There currently exist certain challenge(s). In a NG-RAN node, it is decided that the downlink aggregate bit rate control is done in the Packet Data Convergence Protocol (PDCP) layer, and the uplink aggregate bit rate control is done in the Medium Access Control (MAC) layer. In the split NG-RAN node architecture, the PDCP entity resides in the gNB-CU, and the MAC entity resides in gNB-DU. The interface in between the gNB-CU and the gNB-DU is the FI interface, separate for UP and CP.

The solution agreed in 3GPP is summarized in the following (with reference to 3GPP TS 38.470 V15.2.0 and TS 37.340 V15.2.0). The gNB-CU-CP decides the split of downlink UE-AMBR and uplink UE-AMBR limits to be assigned to the gNB-CU-UP and the gNB-DU, respectively. The gNB-CU-CP indicates these downlink UE-AMBR limits and uplink UE- AMBR limits to the gNB-CU-UP and gNB-DU, respectively. The PDCP entity at the gNB-CU- UP applies the received downlink UE-AMBR limit to the set of all bearers for which the CU- UP hosts PDCP for the UE. The MAC entity at the DU applies the received uplink UE-AMBR limit to the scheduled uplink radio traffic at the DU for the UE.

However, currently, the technology does not exist in the gNB to achieve the agreed solution. Thus, there is a need for systems and methods to achieve the agreed solution. Summary

Systems and methods are disclosed herein for uplink Protocol Data Unit (PDU) Session Aggregate Maximum Bit Rate (AMBR) control in a base station having a split architecture in a Radio Access Network (RAN) of a cellular communications system.

Embodiments of a method performed by a base station and corresponding embodiments of a base station are disclosed. In some embodiments, a method performed by a base station having a split architecture comprising a Centralized Unit (CU) and a Distributed Unit (DU) comprises sending, from the CU to the DU, PDU session information and an uplink PDU session AMBR for a PDU session. The method further comprises, at the DU, receiving the PDU session information and the uplink PDU session AMBR for the PDU session from the CU storing the PDU session information and the uplink PDU session AMBR for the PDU session. In some embodiments, the method further comprises, at the DU, using the PDU session information and the uplink PDU session AMBR for the PDU session to provide uplink AMBR control for the PDU session.

Embodiments of a method performed by a CU of a base station having a split architecture and corresponding embodiments of a CU are also disclosed. In some embodiments, a method performed by a CU of a base station in a RAN comprises sending, from the CU of the base station to a DU of the base station, PDU session information and an uplink PDU session AMBR for a PDU session. In this manner, the DU is provided information that enables the DU to perform uplink AMBR control for the PDU session.

In some embodiments, the base station is a New Radio (NR) base station (gNB), the CU is a gNB-CU, and the DU is a gNB-DU. Further, in some embodiments, sending the PDU session information and the uplink PDU session AMBR for the PDU session comprises sending the PDU session information and the uplink PDU session AMBR for the PDU session over a FI interface that interconnects the gNB-CU and the gNB-DU.

In some embodiments, sending the PDU session information and the uplink PDU session AMBR for the PDU session comprises sending a User Equipment (UE) Context Setup Request message to the DU, wherein the UE Context Setup Request message comprises the PDU session information and the uplink PDU session AMBR for the PDU session. Further, in some embodiments, the UE Context Setup Request message comprises: a Data Radio Bearer (DRB) Identifier (ID) of a DRB associated with the PDU session, a PDU session ID of the PDU session, and the uplink PDU session AMBR associated with the PDU session ID. In some other embodiments, the UE Context Setup Request message comprises DRB information and a PDU session resource information list. The DRB information comprises a DRB ID of a DRB associated with the PDU session and a PDU session ID of the PDU session. The PDU session resource information list comprises PDU session resource information for each of one or more PDU sessions, wherein the one or more PDU sessions comprise the PDU session and the PDU session resource information for the PDU session comprises a PDU session ID of the PDU session and the uplink PDU session AMBR for the PDU session.

In some embodiments, sending the PDU session information and the uplink PDU session AMBR for the PDU session comprises sending a PDU session ID of the PDU session and the uplink PDU session AMBR together within a Quality of Service (QoS) Flow Level QoS Parameters structure.

In some embodiments, sending the PDU session information and the uplink PDU session AMBR for the PDU session comprises sending a message to the DU, wherein the message comprises QoS flow level QoS parameters information to be applied to a QoS flow or to a DRB associated with the PDU session. Further, the QoS flow level QoS parameters information comprises a PDU session ID of the PDU session and the uplink PDU session AMBR for the PDU session. In some embodiments, the message is a UE Context Setup Request message. In some other embodiments, the message is a UE Context Modification message.

In some embodiments, the PDU session is a PDU session for a wireless device.

In some embodiments, a CU of a base station in a RAN is adapted to send, from the CU of the base station to a DU of the base station, PDU session information and an uplink PDU session AMBR for a PDU session.

In some embodiments, the CU comprises an interface and processing circuitry associated with the interface, wherein the processing circuitry is configured to cause the CU to send, from the CU of the base station to a DU of the base station, PDU session information and an uplink PDU session AMBR for a PDU session.

Embodiments of a method performed by a DU of a base station and corresponding embodiments of the DU are also disclosed. In some embodiments, a method performed by a DU of a base station in a RAN comprises receiving, from a CU of the base station, PDU session information and an uplink PDU session AMBR for a PDU session and storing the PDU session information and the uplink PDU session AMBR for the PDU session.

In some embodiments, the method further comprises using the PDU session information and the uplink PDU session AMBR for the PDU session to perform uplink PDU session AMBR control for the PDU session.

In some embodiments, storing the PDU session information and the uplink PDU session AMBR for the PDU session comprises storing the PDU session information and the uplink PDU session AMBR for the PDU session in an associated UE context.

In some embodiments, the base station is a gNB, the CU is a gNB-CU, and the DU is a gNB-DU. Further, in some embodiments, receiving the PDU session information and the uplink PDU session AMBR for the PDU session comprises receiving the PDU session information and the uplink PDU session AMBR for the PDU session over a FI interface that interconnects the gNB-CU and the gNB-DU.

In some embodiments, receiving the PDU session information and the uplink PDU session AMBR for the PDU session comprises receiving a UE Context Setup Request message from the CU, wherein the UE Context Setup Request comprises the PDU session information and the uplink PDU session AMBR for the PDU session. Further, in some embodiments, the UE Context Setup Request message comprises a DRB ID of a DRB associated with the PDU session, a PDU session ID of the PDU session, and the uplink PDU session AMBR associated with the PDU session ID. In some other embodiments, the UE Context Setup Request message comprises DRB information and a PDU session resource information list. The DRB information comprises a DRB ID of a DRB associated with the PDU session and a PDU session ID of the PDU session. The PDU session resource information list comprises PDU session resource information for each of one or more PDU sessions, wherein the one or more PDU sessions comprise the PDU session and the PDU session resource information for the PDU session comprises a PDU session ID of the PDU session and the uplink PDU session AMBR for the PDU session.

In some embodiments, receiving the PDU session information and the uplink PDU session AMBR for the PDU session comprises receiving a PDU session ID of the PDU session and the uplink PDU session AMBR together within a QoS Flow Level QoS

Parameters structure.

In some embodiments, receiving the PDU session information and the uplink PDU session AMBR for the PDU session comprises receiving a message from the CU, wherein the message comprises QoS flow level QoS parameters information to be applied to a QoS flow or to a DRB associated with the PDU session. Further, the QoS flow level QoS parameters information comprises a PDU session ID of the PDU session and the uplink PDU session AMBR for the PDU session. In some embodiments, the message is a UE Context Setup Request message. In some other embodiments, the message is a UE Context Modification message.

In some embodiments, the PDU session is a PDU session for a wireless device.

In some embodiments, a DU for a base station in a RAN is adapted to receive, from a CU of the base station, PDU session information and an uplink PDU session AMBR for a PDU session and store the PDU session information and the uplink PDU session AMBR for the PDU session.

In some embodiments, the DU comprises an interface and processing circuitry associated with the interface, wherein the processing circuitry is configured to cause the DU to receive the PDU session information and the uplink PDU session AMBR for the PDU session from the CU and store the PDU session information and the uplink PDU session AMBR for the PDU session.

Brief Description of the Drawings

The accompanying drawing figures incorporated in and forming a part of this specification illustrate several aspects of the disclosure, and together with the description serve to explain the principles of the disclosure. Figure 1 illustrates the current Fifth Generation (5G) Radio Access Network (RAN) architecture;

Figure 2 illustrates the 5G RAN architecture in which the Centralized Unit (CU) in the 5G New Radio (NR) base station (gNB) provides Protocol Data Unit (PDU) session information an PDU Session Aggregate Maximum Bit Rate (PDU Session-AMBR) to

Distributed Unit(s) (DU(s)) of the gNB in accordance with some embodiments of the present disclosure;

Figure 3 illustrates the operation of a gNB-CU and a gNB-DU in accordance with at least some of embodiments of the present disclosure;

Figure 4 illustrates a User Equipment (UE) Context Setup Request procedure for successful operation in accordance with some embodiments of the present disclosure;

Figure 5 illustrates a UE Context Setup Request procedure for unsuccessful operation in accordance with some embodiments of the present disclosure;

Figure 6 illustrates a UE Context Modification procedure for successful operation in accordance with some embodiments of the present disclosure;

Figure 7 illustrates a UE Context Modification procedure for unsuccessful operation in accordance with some embodiments of the present disclosure;

Figure 8 illustrates one example of a wireless network in which embodiments of the present disclosure may be implemented;

Figure 9 illustrates one embodiment of a UE in accordance with various aspects described herein;

Figure 10 is a schematic block diagram illustrating a virtualization environment in which functions implemented by some embodiments of the present disclosure may be virtualized;

Figure 11 illustrates one embodiment of a communication system in which embodiments of the present disclosure may be implemented;

Figure 12 illustrates example embodiments of a UE, base station, and host computer of Figure 11; Figures 13 through 16 are flow charts that illustrate the operation of the communication system of Figures 11 and 12 in accordance with some embodiments of the present disclosure; and

Figure 17 illustrates a schematic block diagram of an apparatus in a wireless network (for example, the wireless network shown in Figure 8).

Detailed Description

The embodiments set forth below represent information to enable those skilled in the art to practice the embodiments and illustrate the best mode of practicing the embodiments. Upon reading the following description in light of the accompanying drawing figures, those skilled in the art will understand the concepts of the disclosure and will recognize applications of these concepts not particularly addressed herein. It should be understood that these concepts and applications fall within the scope of the disclosure.

Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and/or is implied from the context in which it is used. All references to a/an/the element, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any methods disclosed herein do not have to be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and/or where it is implicit that a step must follow or precede another step. Any feature of any of the embodiments disclosed herein may be applied to any other embodiment, wherever appropriate. Likewise, any advantage of any of the embodiments may apply to any other embodiments, and vice versa. Other objectives, features, and advantages of the enclosed embodiments will be apparent from the following description.

Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Other embodiments, however, are contained within the scope of the subject matter disclosed herein, the disclosed subject matter should not be construed as limited to only the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

As discussed above, in a Third Generation Partnership Project (3GPP) Fifth

Generation (5G) New Radio (NR) Radio Access Network (RAN), which is referred to as a Next Generation (NG) RAN (NG-RAN), it is decided that downlink aggregate bit rate control is done in the Packet Data Convergence Protocol (PDCP) layer, and uplink aggregate bit rate control is done in the Medium Access Control (MAC) layer. In the split NG-RAN node architecture, the PDCP entity resides in a NR base station (gNB) Centralized Unit (gNB-CU), and the MAC entity resides in a gNB Distributed Unit (gNB-DU), where the interface between the gNB-CU and the gNB-UE is the FI interface and is separate for User Plane (UP) and Control Plane (CP).

The solution agreed in 3GPP is summarized in the following (with reference to 3GPP Technical Specification (TS) 38.470 V15.2.0 and TS 37.340 V15.2.0). The CP portion of the gNB-CU (denoted herein as gNB-CU-CP) decides the split of downlink User Equipment (UE) Aggregate Maximum Bit Rate (UE-AMBR) and uplink UE-AMBR limits to be assigned to the UP portion of the gNB-CU (denoted herein as gNB-CU-UP) and the gNB-DU, respectively. The gNB-CU-CP indicates these downlink UE-AMBR limits and uplink UE-AMBR limits to the gNB-CU-UP and the gNB-DU, respectively. The PDCP entity at the gNB-CU-UP applies the received downlink UE-AMBR limit to the set of all bearers for which the gNB-CU-UP hosts PDCP for the UE. The MAC entity at the gNB-DU applies the received uplink UE-AMBR limit to the scheduled uplink radio traffic at the DU for the UE.

In the NG-RAN, several Quality of Service (QoS) flows can be mapped to one Data Radio Bearer (DRB). The gNB-DU is working on the DRB level, even if the gNB-DU is aware of the QoS flow models and QoS to DRB mapping. The gNB-DU does not know about the Protocol Data Unit (PDU) sessions, i.e. the gNB-DU does not know which QoS flows are included in which PDU session and how many PDU sessions are included in the UE. Because the gNB-DU does not know about PDU sessions, it is currently not possible for the gNB-DU to do uplink aggregate bit rate control on the PDU session level. The gNB- DU can only do uplink aggregate bit rate control on the UE level. On the other hand, based on SA2 requirements (3GPP TS 23.501), the gNB (DU) must also be able to perform uplink bit rate control on the PDU session level.

Certain aspects of the present disclosure and their embodiments may provide solutions to these or other challenges. In the present disclosure, solutions are provided for the gNB-DU to be aware of the PDU sessions, e.g. the session information and the PDU Session-AMBR. Only when this information is available in the gNB-DU could the gNB-DU perform uplink aggregate bit rate control for the traffic on the PDU session level (as per SA2 requirements).

In some embodiments, the PDU session information over F1AP is provided as follows:

1. When the gNB-CU sets up the UE context in the gNB-DU over FI, the gNB-CU

provides a PDU Session Identifier (ID). Note that only QoS flows from the same PDU session can be multiplexed to one DRB.

2. The gNB-CU provides the PDU Session-AMBR per PDU session in the UE context setup procedure.

3. When the gNB-DU has received the information, upon the reception of the UE

Context Setup Request message, the gNB-DU stores the information in the UE context and uses this information for, e.g., uplink aggregate bit rate control.

The same approach can be extended to allow the gNB-CU to modify the PDU session related information. For example, PDU Session-AMBR per PDU session in gNB-DU.

In some embodiments, a method is disclosed that allows a gNB-CU to send the PDU session uplink AMBR information to the gNB-DU for monitoring and enforcement.

Certain embodiments may provide one or more of the following technical

advantage(s). The proposed embodiments enable the support of the aggregate bit rate control defined in 3GPP TS 23.501 in case the NG-RAN node is split in the gNB-CU and gNB-DU. Embodiments of the present disclosure let the gNB-DU be aware that the PDU session information may have other potential uses.

Now, the discussion will turn to a more detailed description of some example embodiments of the present disclosure. In this regard, Figure 2 illustrates a NG-RAN architecture 200 in which a gNB 202 has a split architecture including a gNB-CU 204 and a number of gNB-DUs 206-1, 206-2 (generally referred to herein collectively as gNB-DUs 206 and individually as gNB-DU 206) in accordance with some embodiments of the present disclosure. As illustrated, the gNB-CU 204 provides PDU session information and PDU- AMBR to the gNB-DU(s) 206, as described below in more detail.

Figure 3 illustrates the operation of a gNB-CU 204 and a gNB-DU 206 of a gNB 202 in accordance with at least some of the embodiments disclosed herein. Optional steps are illustrated with dashed lines. As shown, the gNB-CU 204 sends PDU session information (e.g., a PDU session ID) and a PDU Session-AMBR for a PDU session to the gNB-DU 206 (step 300). In this example, this information is sent via the FI interface. The PDU session is preferably an uplink PDU session for a UE. In other words, the PDU Session-AMBR is preferably an uplink PDU Session-AMBR for the uplink PDU session for the UE, where the uplink PDU Session-AMBR is to be enforced at the MAC layer in the gNB-DU 206. The gNB- DU 206 stores the PDU session information and the PDU Session-AMBR, e.g., in an associated UE context (i.e., in a context of the associated UE) (step 302). Optionally, the gNB-DU 206 applies the PDU Session-AMBR for the PDU session, as will be understood by one of ordinary skill in the art (step 304).

In the following, examples are described to show how the present disclosure can be implemented over the FI interface.

Please note that the information of PDU session ID and the related PDU session information needs to be sent from the gNB-CU to the gNB-DU in the split architecture. The information could be sent in other UE related messages or within other information.

Please also note the message structure to allow PDU session information to be sent to the gNB-DU may be used to send other related information to serve other purposes in the future.

Example 1

In this example, the gNB-CU uses the "UE Context Setup Request" message to setup the UE context in the DU.

• In the UE Context Setup Request message, the gNB-CU sends the PDU session ID together with the DRB ID in the "DRB Information". • The gNB-CU sends the PDU Session Resource Information List to the gNB-DU in the UE Context Setup Request message. In this list, for each PDU session, the PDU session ID and the uplink PDU Session Aggregate Maximum Bit Rate are included.

• It is specified that the DU should store the received PDU session resource

information in the UE context and use it for, e.g., aggregate bit rate control.

In other words, looking back at Figure 3, the UE Context Setup Request message is sent from the gNB-CU 204 to the gNB-DU 206 in step 300. This UE Context Setup Request message includes the PDU session information (e.g., the PDU session ID) and the uplink PDU Session-AMBR for each of a number of PDU sessions included in the PDU Session Resource Information List.

The table below shows the change in chapter 9.2.2.1 UE CONTEXT SETUP REQUEST in 3GPP TS 38.473 V15.2.0. The Information Elements (IEs) PDU session ID within the DRB information and the PDU Session Resource Information List are introduced.

Table 1: Example of introduce PDU Session resource Information over F1AP

Example 2

In this example, the gNB-CU sends the PDU session ID and the PDU Session-AMBR together within the QoS Flow Level QoS Parameters structure. In F1AP, the "QoS Flow Level QoS Parameters" IE defines QoS to be applied to a QoS flow or to a DRB.

• The gNB-CU includes the PDU session resource information, e.g. PDU session ID and uplink PDU Session-AMBR for each QoS flow.

• When received, the gNB-DU stores the PDU session resource information in the UE context and uses this information (e.g., for non-Guaranteed Flow Bit Rate (GBR) bearers for the concerned PDU sessions and the concerned UE, e.g., as specified in 3GPP TS 25.501).

In other words, looking back at Figure 3, the QoS Flow Level QoS Parameters IE is sent from the gNB-CU 204 to the gNB-DU 206 in step 300. The QoS Flow Level QoS Parameters IE is contained in the UE Context Setup Request message sent from the gNB-CU 204 to the gNB-DU 206. This IE includes the PDU session information (e.g., the PDU session ID) and the uplink PDU Session-AMBR for each QoS flow.

PDU sessions may contain many QoS flows. If we have PDU session resource information attached to each QoS flow, then the same information is repeated. However, in some embodiments, the IEs are defined as optional present, and the gNB-CU and gNB- DU could handle this issue. For example, the gNB-CU could include the information only for the first QoS flow, and the gNB-DU can interpret that the information is applicable to the entire corresponding PDU session.

Table 2 below shows the changes to chapter 9.3.1.45 QoS Flow Level QoS

Parameters in 3GPP TS 38.473 V15.2.0. PDU Session ID and uplink PDU Session

Aggregate Maximum Bit Rate are introduced.

Table 2: Example of introduce PDU Session resource Information over F1AP in QoS Flow

Level QoS Parameters

The following is one example implementation of Example 2 shown as a text proposal for 3GPP TS 38.473:

8.3.1 U E Context Setup

8.3.1.1 General

The purpose of the UE Context Setup procedure is to establish the UE Context including, among others, SRB, and DRB configuration. The procedure uses UE-associated signalling.

8.3.1.2 Successful Operation

[REPRODUCED AS FIGURE 4]

Figure 8.3.1.2-1 : UE Context Setup Request procedure: Successful Operation

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.

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.

If the SCell 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 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 DRX Cycle IE is contained in the UE CONTEXT SETUP REQUEST message, the gNB-DU shall use the provided value from the gNB-CU.

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.

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 setup two RLC entities for the indicated SRB and send the LCID IE for the primary path in the UE CONTEXT SETUP RESPONSE message.

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 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. 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]

If Duplication Activation IE is included in the UE CONTEXT SETUP REQUEST message for a DRB, gNB-DU should take it into account when activing/deactiving PDCP duplication for the DRB.

ForEN-DC operation, and if the Subscriber Profile 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. 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 [20]

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 and SRBs in the following way:

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

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

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

When the gNB-DU reports the unsuccessful establishment of a DRB or SRB, the cause value should be precise enough to enable the gNB-CU to know the reason for the unsuccessful establishment.

For EN-DC operation, the gNB-CU shall include in the UE CONTEXT SETUP REQUEST the E- UTPAN 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 [15]

For NG-RAN operation, the gNB-CU shall include in the UE CONTEXT SETUP REQUEST the DRB Information IE. For DC operation, the CG-Configlnfo IE shall be included in the CU to DU RRC Information IE.

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 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]

lithe Masked IMEISVTE 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.

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 established with an appropriate cause value for each SCell failed to setup.

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.

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.

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.

The UE Context Setup Procedure is not used to configure SRB0.

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

If the Notification Control IE is included in the DRB to Be Setup 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.

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 SETUP REQUEST message, the gNB-DU shall store the received UL PDU Session Aggregate Maximum Bit Rate and use it for non-GBR Bearers for the concerned PDU sessions and the concerned UE as specified in TS 23.501 [21]. 8.3.1.3 Unsuccessful Operation

[REPRODUCED AS FIGURE 5]

Figure 8.3.1.3-1 : UE Context Setup Request procedure: unsuccessful Operation

If the gNB-DU is not able to establish an Fl UE context, or cannot even establish one bearer it shall consider the procedure as failed and reply with the UE CONTEXT SETUP FAILURE message.

If the gNB-DU is not able to accept the SpCelllD IE in UE CONTEXT SETUP REQUEST message, it shall reply with the UE CONTEXT SETUP FAILURE message with an appropriate cause value. Further, if the Candidate SpCell List IE is included in the UE CONTEXT SETUP REQUEST message and the gNB-DU is not able to accept the SpCell ID IE, the gNB-DU shall, if supported, include the Potential SpCell List IE in the UE CONTEXT SETUP FAILURE message and the gNB-CU should take this into account for selection of an opportune SpCell. The gNB-DU shall include the cells in the Potential SpCell List IE in a priority order, where the first cell in the list is the one most desired and the last one is the one least desired (e.g., based on load conditions). If the Potential SpCell List IE is present but no Potential SpCell Item IE is present, the gNB-CU should assume that none of the cells in the Candidate SpCell ListlE are acceptable for the gNB-DU.

8.3.1.4 Abnormal Conditions

Not applicable.

8.3.4 UE Context Modification (gNB-CU initiated)

8.3.4.1 General

The purpose of the UE Context Modification procedure is to modify the established UE Context, e.g., establishing, modifying and releasing radio 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.

8.3.4.2 Successful Operation

[REPRODUCED AS FIGURE 6]

Figure 8.3.4.2-1 : UE Context Modification procedure. Successful operation

The Fl AP UE CONTEXT MODIFICATION REQUEST message is initiated by the gNB-CU.

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 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 SCell To Be Setup List IE or SCell To Be Removed 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 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 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.

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 setup two RLC entities for the indicated SRB and feedback the LCID for the primary path in the UE CONTEXT SETUP RESPONSE message.

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 two UL UP TNL Information IEs are included in UE CONTEXT MODIFICATION REQUEST message for a DRB, gNB-DU shall include two DL UP TNL Information IEs in UE CONTEXT MODIFICATION RESPONSE message. 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]

If Duplication Activation IE is included in the UE CONTEXT MODIFICATION REQUEST message for a DRB, gNB-DU should take it into account when activing/deactiving PDCP duplication for the DRB.

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. The gNB-CU may include the PRC Reconfiguration Complete Indicator IE in the UE CONTEXT MODIFICATION REQUEST message to inform the gNB-DU that the ongoing reconfiguration procedure has been successfully performed by the UE. The gNB-DU does not need to wait for this confirmation for using the new UE configuration or taking other actions towards the UE. It is up to gNB-DU implementation when to use the new UE configuration configured.

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

If the UE CONTEXT MODIFICATION REQUEST message contains the Transmission Stop 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. 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 [3] For NG-RAN operation, the gNB-CU shall include t e DRB Information IE in the UE CONTEXT MODIFICATION REQUEST message.

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]

For EN-DC operation, and if the Subscriber Profile ID for RAT/Frequency priority IE is received from an MeNB, the UE CONTEXT MODIFIC TION REQUEST message shall contain the Subscriber Profile ID for RAT/Frequency priority 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 [20]

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.

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.

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 and SRBs in the following way:

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

- A list of DRBs which failed to be modified shall be included in the DRB Failed to be Modified List IE;

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] If the UE CONTEXT MODIFICATION RESPONSE message contains the Of f To CURRC Information IE, the gNB-CU shall take this into account.

If the SC ell 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 established with an appropriate cause value for each SCell failed to setup.

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.

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

If 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.

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 [21]

8.3.4.3 Unsuccessful Operation

[REPRODUCED AS FIGURE 7]

Figure 8.3.4.3-1 : UE Context Modification procedure. Unsuccessful operation

In case none of the requested modifications of the UE context can be successfully performed, the gNB-DU shall respond with the UE CONTEXT MODIFICATION FAILURE message with an appropriate cause value.

If the gNB-DU is not able to accept the SpCell ID IE in UE CONTEXT MODIFICATION

REQUEST message, it shall reply with the UE CONTEXT MODIFICATION FAILURE message.

8.3.4.4 Abnormal Conditions

Not applicable. 9.3.1.45 QoS Flow Level QoS Parameters

This IE defines the QoS to be applied to a QoS flow or to a DRB.

9.4.5 Information Element Definitions

— Information Element Definitions

FlAP-IEs {

itu-t (0) identified-organization (4) etsi (0) mobileDomain (0) ngran-access (22) modules (3) flap (3) versionl (1) flap-IEs (2) }

DEFINITIONS AUTOMATIC TAGS ::=

BEGIN

IMPORTS

id-gNB-CUSystemlnformation,

id-HandoverPreparationlnformation,

id-TAISliceSupportList,

id-RANAC,

maxNRARFCN,

maxnoofErrors ,

maxnoofBPLMNs ,

maxnoofDLUPTNLInformation,

maxnoofNrCellBands ,

maxnoofULUPTNLInformation,

maxnoofQoSFlows ,

QoSFlowLevelQoSParameters ::= SEQUENCE {

qoS-Characteristics QoS-Characteristies , nGRANallocationRetentionPriority

NGRANAllocationAndRetentionPriority,

gBR-QoS-Flow-Information GBR-QoSFIowlnformation

OPTIONAL,

reflective-QoS-Attribute ENUMERATED {subject-to, ...}

OPTIONAL,

pDUSessionID PDUSessionID

OPTIONAL,

dLPDUSessionAggregateMaximumBitRate BitRate

OPTIONAL,

iE-Extensions ProtocolExtensionContainer { {

QoSFlowLevelQoSParameters-ExtIEs } } OPTIONAL

}

QoSFlowLevelQoSParameters-ExtIEs F1AP-PROTOCOL-EXTENSION ::= {

PDUSessionID ::= INTEGER (0..255)

Although the subject matter described herein may be implemented in any appropriate type of system using any suitable components, the embodiments disclosed herein are described in relation to a wireless network, such as the example wireless network illustrated in Figure 8. For simplicity, the wireless network of Figure 8 only depicts a network 806, network nodes 860 and 860B, and Wireless Devices (WDs) 810, 810B, and 810C. In practice, a wireless network may further include any additional elements suitable to support communication between wireless devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or end device. Of the illustrated components, the network node 860 and the WD 810 are depicted with additional detail. The wireless network may provide communication and other types of services to one or more wireless devices to facilitate the wireless devices' access to and/or use of the services provided by, or via, the wireless network.

The wireless network may comprise and/or interface with any type of

communication, telecommunication, data, cellular, and/or radio network or other similar type of system. In some embodiments, the wireless network may be configured to operate according to specific standards or other types of predefined rules or procedures. Thus, particular embodiments of the wireless network may implement communication standards, such as Global System for Mobile Communications (GSM), Universal Mobile

Telecommunications System (UMTS), Long Term Evolution (LTE), and/or other suitable Second, Third, Fourth, or Fifth Generation (2G, 3G, 4G, or 5G) standards; Wireless Local Area Network (WLAN) standards, such as the IEEE 802.11 standards; and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, and/or ZigBee standards. As discussed above, in the preferred embodiments described herein, the wireless network implements the 5G NR standards, where the network node 860 is a gNB having a split CU/DU architecture.

The network 806 may comprise one or more backhaul networks, core networks, Internet Protocol (IP) networks, Public Switched Telephone Networks (PSTNs), packet data networks, optical networks, Wide Area Networks (WANs), Local Area Networks (LANs), WLANs, wired networks, wireless networks, metropolitan area networks, and other networks to enable communication between devices.

The network node 860 and the WD 810 comprise various components described in more detail below. These components work together in order to provide network node and/or wireless device functionality, such as providing wireless connections in a wireless network. In different embodiments, the wireless network may comprise any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, 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.

As used herein, network node refers to equipment capable, configured, arranged, and/or operable to communicate directly or indirectly with a wireless device and/or with other network nodes or equipment in the wireless network to enable and/or provide wireless access to the wireless device and/or to perform other functions (e.g.,

administration) in the wireless network. Examples of network nodes include, but are not limited to, Access Points (APs) (e.g., radio APs), Base Stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs), and gNBs). Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and may then also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and/or Remote Radio Units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such RRUs 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). Yet further examples of network nodes include Multi-Standard Radio (MSR) equipment such as MSR BSs, network controllers such as Radio Network Controllers (RNCs) or BS Controllers (BSCs), Base Transceiver Stations (BTSs), transmission points, transmission nodes, Multi-Cell/Multicast Coordination Entities (MCEs), core network nodes (e.g., Mobile Switching Centers (MSCs), Mobility Management Entities (MMEs)), Operation and

Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Center (E- SMLCs)), and/or Minimization of Drive Tests (MDTs). As another example, a network node may be a virtual network node as described in more detail below. More generally, however, network nodes may represent any suitable device (or group of devices) capable, configured, arranged, and/or operable to enable and/or provide a wireless device with access to the wireless network or to provide some service to a wireless device that has accessed the wireless network.

In Figure 8, the network node 860 includes processing circuitry 870, a device readable medium 880, an interface 890, auxiliary equipment 884, a power source 886, power circuitry 887, and an antenna 862. Although the network node 860 illustrated in the example wireless network of Figure 8 may represent a device that includes the illustrated combination of hardware components, other embodiments may comprise network nodes with different combinations of components. It is to be understood that a network node comprises any suitable combination of hardware and/or software needed to perform the tasks, features, functions, and methods disclosed herein. Moreover, while the components of the network node 860 are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, a network node may comprise multiple different physical components that make up a single illustrated component (e.g., the device readable medium 880 may comprise multiple separate hard drives as well as multiple Random Access Memory (RAM) modules).

Similarly, the network node 860 may be composed of multiple physically separate components (e.g., a Node B component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node 860 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple Node Bs.

In such a scenario, each unique Node B and RNC pair may in some instances be considered a single separate network node. In some embodiments, the network node 860 may be configured to support multiple Radio Access Technologies (RATs). In such embodiments, some components may be duplicated (e.g., a separate device readable medium 880 for the different RATs) and some components may be reused (e.g., the same antenna 862 may be shared by the RATs). The network node 860 may also include multiple sets of the various illustrated components for different wireless technologies integrated into the network node 860, such as, for example, GSM, Wideband Code Division Multiple Access (WCDMA), LTE, NR, WiFi, or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or a different chip or set of chips and other components within the network node 860.

The processing circuitry 870 is configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being provided by a network node. These operations performed by the processing circuitry 870 may include processing information obtained by the processing circuitry 870 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. The processing circuitry 870 may comprise a combination of one or more of a microprocessor, a controller, a microcontroller, a Central Processing Unit (CPU), a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field

Programmable Gate Array (FPGA), 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 network node 860 components, such as the device readable medium 880, network node 860 functionality. For example, the processing circuitry 870 may execute instructions stored in the device readable medium 880 or in memory within the processing circuitry 870. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, the processing circuitry 870 may include a System on a Chip (SOC).

In some embodiments, the processing circuitry 870 may include one or more of Radio Frequency (RF) transceiver circuitry 872 and baseband processing circuitry 874. In some embodiments, the RF transceiver circuitry 872 and the baseband processing circuitry 874 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 the RF transceiver circuitry 872 and the baseband processing circuitry 874 may be on the same chip or set of chips, boards, or units.

In certain embodiments, some or all of the functionality described herein as being provided by a network node, base station, eNB, or other such network device may be performed by the processing circuitry 870 executing instructions stored on the device readable medium 880 or memory within the processing circuitry 870. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry 870 without executing instructions stored on a separate or discrete device readable medium, such as in a hard-wired manner. In any of those embodiments, whether executing instructions stored on a device readable storage medium or not, the processing circuitry 870 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry 870 alone or to other components of the network node 860, but are enjoyed by the network node 860 as a whole, and/or by end users and the wireless network generally. The device readable medium 880 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, 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 non-volatile, 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 870. The device readable medium 880 may store any suitable instructions; data or information, including a computer program; software; an application including one or more of logic, rules, code, tables, etc.; and/or other instructions capable of being executed by the processing circuitry 870 and utilized by the network node 860. The device readable medium 880 may be used to store any calculations made by the processing circuitry 870 and/or any data received via the interface 890. In some embodiments, the processing circuitry 870 and the device readable medium 880 may be considered to be integrated.

The interface 890 is used in the wired or wireless communication of signaling and/or data between the network node 860, a network 806, and/or WDs 810. As illustrated, the interface 890 comprises port(s)/terminal(s) 894 to send and receive data, for example to and from the network 806 over a wired connection. The interface 890 also includes radio front end circuitry 892 that may be coupled to, or in certain embodiments a part of, the antenna 862. The radio front end circuitry 892 comprises filters 898 and amplifiers 896. The radio front end circuitry 892 may be connected to the antenna 862 and the processing circuitry 870. The radio front end circuitry 892 may be configured to condition signals communicated between the antenna 862 and the processing circuitry 870. The radio front end circuitry 892 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. The radio front end circuitry 892 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of the filters 898 and/or the amplifiers 896. The radio signal may then be transmitted via the antenna 862. Similarly, when receiving data, the antenna 862 may collect radio signals which are then converted into digital data by the radio front end circuitry 892. The digital data may be passed to the processing circuitry 870. In other embodiments, the interface 890 may comprise different components and/or different combinations of components.

In certain alternative embodiments, the network node 860 may not include separate radio front end circuitry 892; instead, the processing circuitry 870 may comprise radio front end circuitry and may be connected to the antenna 862 without separate radio front end circuitry 892. Similarly, in some embodiments, all or some of the RF transceiver circuitry 872 may be considered a part of the interface 890. In still other embodiments, the interface 890 may include the one or more ports or terminals 894, the radio front end circuitry 892, and the RF transceiver circuitry 872 as part of a radio unit (not shown), and the interface 890 may communicate with the baseband processing circuitry 874, which is part of a digital unit (not shown).

The antenna 862 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. The antenna 862 may be coupled to the radio front end circuitry 892 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In some embodiments, the antenna 862 may comprise one or more omni-directional, sector, or panel antennas operable to

transmit/receive radio signals between, for example, 2 gigahertz (GFIz) and 66 GFIz. An omni-directional antenna may be used to transmit/receive radio signals in any direction, a sector antenna may be used to transmit/receive radio signals from devices within a particular area, and a panel antenna may be a line of sight antenna used to

transmit/receive radio signals in a relatively straight line. In some instances, the use of more than one antenna may be referred to as Multiple Input Multiple Output (MIMO). In certain embodiments, the antenna 862 may be separate from the network node 860 and may be connectable to the network node 860 through an interface or port.

The antenna 862, the interface 890, and/or the processing circuitry 870 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by a network node. Any information, data, and/or signals may be received from a WD, another network node, and/or any other network equipment. Similarly, the antenna 862, the interface 890, and/or the processing circuitry 870 may be configured to perform any transmitting operations described herein as being performed by a network node. Any information, data, and/or signals may be transmitted to a WD, another network node, and/or any other network equipment.

The power circuitry 887 may comprise, or be coupled to, power management circuitry and is configured to supply the components of the network node 860 with power for performing the functionality described herein. The power circuitry 887 may receive power from the power source 886. The power source 886 and/or the power circuitry 887 may be configured to provide power to the various components of the network node 860 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 886 may either be included in, or be external to, the power circuitry 887 and/or the network node 860. For example, the network node 860 may be connectable to an external power source (e.g., an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to the power circuitry 887. As a further example, the power source 886 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, the power circuitry 887. The battery may provide backup power should the external power source fail. Other types of power sources, such as photovoltaic devices, may also be used.

Alternative embodiments of the network node 860 may include additional components beyond those shown in Figure 8 that may be responsible 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 860 may include user interface equipment to allow input of information into the network node 860 and to allow output of information from the network node 860. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 860.

As used herein, WD refers to a device capable, configured, arranged, and/or operable to communicate wirelessly with network nodes and/or other WDs. Unless otherwise noted, the term WD may be used interchangeably herein with UE.

Communicating wirelessly may involve transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information through air. In some embodiments, a WD may be configured to transmit and/or receive information without direct human interaction. For instance, a WD may be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the network. Examples of a WD include, but are not limited to, a smart phone, a mobile phone, a cell phone, a Voice over IP (VoIP) phone, a wireless local loop phone, a desktop computer, a Personal Digital Assistant (PDA), a wireless camera, a gaming console or device, a music storage device, a playback appliance, a wearable terminal device, a wireless endpoint, a mobile station, a tablet, a laptop, Laptop Embedded Equipment (LEE), Laptop Mounted Equipment (LME), a smart device, a wireless Customer Premise Equipment (CPE), a vehicle mounted wireless terminal device, etc.. A WD may support Device-to- Device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Vehicle-to-Vehicle (V2V), Vehicle-to-Infrastructure (V2I), Vehicle-to-Everything (V2X), and may in this case be referred to as a D2D communication device. As yet another specific example, in an Internet of Things (IoT) scenario, a WD 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 WD and/or a network node. The WD may in this case be a Machine-to-Machine (M2M) device, which may in a 3GPP context be referred to as a Machine-Type Communication (MTC) device. As one particular example, the WD may be a UE implementing the 3GPP Narrowband IoT (NB-IoT) standard. Particular examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, home or personal appliances (e.g., refrigerators, televisions, etc.), or personal wearables (e.g., watches, fitness trackers, etc.). In other scenarios, a WD may represent a vehicle or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation. A WD as described above may represent the endpoint of a wireless connection, in which case the device may be referred to as a wireless terminal. Furthermore, a WD as described above may be mobile, in which case it may also be referred to as a mobile device or a mobile terminal. As illustrated in Figure 8, a WD 810 includes an antenna 811, an interface 814, processing circuitry 820, a device readable medium 830, user interface equipment 832, auxiliary equipment 834, a power source 836, and power circuitry 837. The WD 810 may include multiple sets of one or more of the illustrated components for different wireless technologies supported by the WD 810, such as, for example, GSM, WCDMA, LTE, NR,

WiFi, WiMAX, or Bluetooth wireless technologies, just to mention a few. These wireless technologies may be integrated into the same or different chips or set of chips as other components within the WD 810.

The antenna 811 may include one or more antennas or antenna arrays configured to send and/or receive wireless signals and is connected to the interface 814. In certain alternative embodiments, the antenna 811 may be separate from the WD 810 and be connectable to the WD 810 through an interface or port. The antenna 811, the interface 814, and/or the processing circuitry 820 may be configured to perform any receiving or transmitting operations described herein as being performed by a WD. Any information, data, and/or signals may be received from a network node and/or another WD. In some embodiments, radio front end circuitry and/or the antenna 811 may be considered an interface.

As illustrated, the interface 814 comprises radio front end circuitry 812 and the antenna 811. The radio front end circuitry 812 comprises one or more filters 818 and amplifiers 816. The radio front end circuitry 812 is connected to the antenna 811 and the processing circuitry 820 and is configured to condition signals communicated between the antenna 811 and the processing circuitry 820. The radio front end circuitry 812 may be coupled to or be a part of the antenna 811. In some embodiments, the WD 810 may not include separate radio front end circuitry 812; rather, the processing circuitry 820 may comprise radio front end circuitry and may be connected to the antenna 811. Similarly, in some embodiments, some or all of RF transceiver circuitry 822 may be considered a part of the interface 814. The radio front end circuitry 812 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. The radio front end circuitry 812 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of the filters 818 and/or the amplifiers 816. The radio signal may then be transmitted via the antenna 811. Similarly, when receiving data, the antenna 811 may collect radio signals which are then converted into digital data by the radio front end circuitry 812. The digital data may be passed to the processing circuitry 820. In other embodiments, the interface 814 may comprise different components and/or different combinations of components.

The processing circuitry 820 may comprise a combination of one or more of a microprocessor, a controller, a microcontroller, a CPU, a DSP, an ASIC, a FPGA, 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 WD 810 components, such as the device readable medium 830, WD 810 functionality. Such functionality may include providing any of the various wireless features or benefits discussed herein. For example, the processing circuitry 820 may execute instructions stored in the device readable medium 830 or in memory within the processing circuitry 820 to provide the functionality disclosed herein.

As illustrated, the processing circuitry 820 includes one or more of the RF

transceiver circuitry 822, baseband processing circuitry 824, and application processing circuitry 826. In other embodiments, the processing circuitry 820 may comprise different components and/or different combinations of components. In certain embodiments, the processing circuitry 820 of the WD 810 may comprise a SOC. In some embodiments, the RF transceiver circuitry 822, the baseband processing circuitry 824, and the application processing circuitry 826 may be on separate chips or sets of chips. In alternative embodiments, part or all of the baseband processing circuitry 824 and the application processing circuitry 826 may be combined into one chip or set of chips, and the RF transceiver circuitry 822 may be on a separate chip or set of chips. In still alternative embodiments, part or all of the RF transceiver circuitry 822 and the baseband processing circuitry 824 may be on the same chip or set of chips, and the application processing circuitry 826 may be on a separate chip or set of chips. In yet other alternative

embodiments, part or all of the RF transceiver circuitry 822, the baseband processing circuitry 824, and the application processing circuitry 826 may be combined in the same chip or set of chips. In some embodiments, the RF transceiver circuitry 822 may be a part of the interface 814. The RF transceiver circuitry 822 may condition RF signals for the processing circuitry 820.

In certain embodiments, some or all of the functionality described herein as being performed by a WD may be provided by the processing circuitry 820 executing instructions stored on the device readable medium 830, which in certain embodiments may be a computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry 820 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 device readable storage medium or not, the processing circuitry 820 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry 820 alone or to other components of the WD 810, but are enjoyed by the WD 810 as a whole, and/or by end users and the wireless network generally.

The processing circuitry 820 may be configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being performed by a WD. These operations, as performed by the processing circuitry 820, may include processing information obtained by the processing circuitry 820 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by the WD 810, 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.

The device readable medium 830 may be operable to store a computer program; software; an application including one or more of logic, rules, code, tables, etc.; and/or other instructions capable of being executed by the processing circuitry 820. The device readable medium 830 may include computer memory (e.g., RAM or ROM), mass storage media (e.g., a hard disk), removable storage media (e.g., a CD or a DVD), and/or any other volatile or non-volatile, 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 820. In some embodiments, the processing circuitry 820 and the device readable medium 830 may be considered to be integrated.

The user interface equipment 832 may provide components that allow for a human user to interact with the WD 810. Such interaction may be of many forms, such as visual, audial, tactile, etc. The user interface equipment 832 may be operable to produce output to the user and to allow the user to provide input to the WD 810. The type of interaction may vary depending on the type of user interface equipment 832 installed in the WD 810. For example, if the WD 810 is a smart phone, the interaction may be via a touch screen; if the WD 810 is a smart meter, the interaction may be through a screen that provides usage (e.g., the number of gallons used) or a speaker that provides an audible alert (e.g., if smoke is detected). The user interface equipment 832 may include input interfaces, devices and circuits, and output interfaces, devices and circuits. The user interface equipment 832 is configured to allow input of information into the WD 810, and is connected to the processing circuitry 820 to allow the processing circuitry 820 to process the input information. The user interface equipment 832 may include, for example, a microphone, a proximity or other sensor, keys/buttons, a touch display, one or more cameras, a Universal Serial Bus (USB) port, or other input circuitry. The user interface equipment 832 is also configured to allow output of information from the WD 810 and to allow the processing circuitry 820 to output information from the WD 810. The user interface equipment 832 may include, for example, a speaker, a display, vibrating circuitry, a USB port, a headphone interface, or other output circuitry. Using one or more input and output interfaces, devices, and circuits of the user interface equipment 832, the WD 810 may communicate with end users and/or the wireless network, and allow them to benefit from the functionality described herein.

The auxiliary equipment 834 is operable to provide more specific functionality which may not be generally performed by WDs. This may comprise specialized sensors for doing measurements for various purposes, interfaces for additional types of communication such as wired communications, etc. The inclusion and type of components of the auxiliary equipment 834 may vary depending on the embodiment and/or scenario. The power source 836 may, in some embodiments, be in the form of a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic devices, or power cells may also be used. The WD 810 may further comprise the power circuitry 837 for delivering power from the power source 836 to the various parts of the WD 810 which need power from the power source 836 to carry out any functionality described or indicated herein. The power circuitry 837 may in certain embodiments comprise power management circuitry. The power circuitry 837 may additionally or alternatively be operable to receive power from an external power source, in which case the WD 810 may be connectable to the external power source (such as an electricity outlet) via input circuitry or an interface such as an electrical power cable. The power circuitry 837 may also in certain embodiments be operable to deliver power from an external power source to the power source 836. This may be, for example, for the charging of the power source 836. The power circuitry 837 may perform any formatting, converting, or other modification to the power from the power source 836 to make the power suitable for the respective components of the WD 810 to which power is supplied.

Figure 9 illustrates one embodiment of a UE in accordance with various aspects described herein. As used herein, a user equipment or UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device. Instead, a UE 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, a UE 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). A UE 900 may be any UE identified by 3GPP, including a NB-IoT UE, a MTC UE, and/or an enhanced MTC (eMTC) UE. The UE 900, as illustrated in Figure 9, is one example of a WD configured for communication in accordance with one or more communication standards promulgated by 3GPP, such as 3GPP's GSM, UMTS, LTE, and/or 5G standards. As mentioned previously, the term WD and UE may be used interchangeable. Accordingly, although Figure 9 is a UE, the components discussed herein are equally applicable to a WD, and vice-versa. In Figure 9, the UE 900 includes processing circuitry 901 that is operatively coupled to an input/output interface 905, an RF interface 909, a network connection interface 911, memory 915 including RAM 917, ROM 919, and a storage medium 921 or the like, a communication subsystem 931, a power source 913, and/or any other component, or any combination thereof. The storage medium 921 includes an operating system 923, an application program 925, and data 927. In other embodiments, the storage medium 921 may include other similar types of information. Certain UEs may utilize all of the components shown in Figure 9, or only a subset of the components. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

In Figure 9, the processing circuitry 901 may be configured to process computer instructions and data. The processing circuitry 901 may be configured to implement any sequential state machine operative to execute machine instructions stored as machine- readable computer programs in the memory, such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logic together with appropriate firmware; one or more stored programs, general purpose processors, such as a microprocessor or DSP, together with appropriate software; or any combination of the above. For example, the processing circuitry 901 may include two CPUs. Data may be information in a form suitable for use by a computer.

In the depicted embodiment, the input/output interface 905 may be configured to provide a communication interface to an input device, output device, or input and output device. The UE 900 may be configured to use an output device via the input/output interface 905. An output device may use the same type of interface port as an input device. For example, a USB port may be used to provide input to and output from the UE 900. The output device may be 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. The UE 900 may be configured to use an input device via the input/output interface 905 to allow a user to capture information into the UE 900. The input device may 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, another like sensor, or any combination thereof. For example, the input device may be an

accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor.

In Figure 9, the RF interface 909 may be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna. The network connection interface 911 may be configured to provide a communication interface to a network 943A. The network 943A may encompass wired and/or wireless networks such as a LAN, a WAN, a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, the network 943A may comprise a WiFi network. The network connection interface 911 may be configured to include a receiver and a transmitter interface used to communicate with one or more other devices over a communication network according to one or more communication protocols, such as Ethernet, Transmission Control Protocol (TCP) / IP, Synchronous Optical

Networking (SONET), Asynchronous Transfer Mode (ATM), or the like. The network connection interface 911 may implement receiver and transmitter functionality appropriate to the communication network links (e.g., optical, electrical, and the like). The transmitter and receiver functions may share circuit components, software, or firmware, or

alternatively may be implemented separately.

The RAM 917 may be configured to interface via a bus 902 to the processing circuitry 901 to provide storage or caching of data or computer instructions during the execution of software programs such as the operating system, application programs, and device drivers. The ROM 919 may be configured to provide computer instructions or data to the processing circuitry 901. For example, the ROM 919 may be configured to store invariant low-level system code or data for basic system functions such as basic Input and Output (I/O), startup, or reception of keystrokes from a keyboard that are stored in a non- volatile memory. The Storage medium 921 may be configured to include memory such as RAM, ROM, Programmable ROM (PROM), Erasable PROM (EPROM), Electrically EPROM (EEPROM), magnetic disks, optical disks, floppy disks, hard disks, removable cartridges, or flash drives. In one example, the storage medium 921 may be configured to include the operating system 923, the application program 925 such as a web browser application, a widget or gadget engine, or another application, and the data file 927. The storage medium 921 may store, for use by the UE 900, any of a variety of various operating systems or combinations of operating systems.

The storage medium 921 may be configured to include a number of physical drive units, such as a Redundant Array of Independent Disks (RAID), a floppy disk drive, flash memory, a USB flash drive, an external hard disk drive, a thumb drive, a pen drive, a key drive, a High-Density Digital Versatile Disc (HD-DVD) optical disc drive, an internal hard disk drive, a Blu-Ray optical disc drive, a Holographic Digital Data Storage (HDDS) optical disc drive, an external mini-Dual In-Line Memory Module (DIMM), Synchronous Dynamic RAM (SDRAM), external micro-DIMM SDRAM, smartcard memory such as a Subscriber Identity Module (SIM) or a Removable User Identity (RUIM) module, other memory, or any combination thereof. The storage medium 921 may allow the UE 900 to access computer- executable instructions, application programs, or 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 in the storage medium 921, which may comprise a device readable medium.

In Figure 9, the processing circuitry 901 may be configured to communicate with a network 943B using the communication subsystem 931. The network 943A and the network 943 B may be the same network or networks or different network or networks.

The communication subsystem 931 may be configured to include one or more transceivers used to communicate with the network 943B. For example, the communication subsystem 931 may be configured to include one or more transceivers used to communicate with one or more remote transceivers of another device capable of wireless communication such as another WD, UE, or base station of a RAN according to one or more communication protocols, such as IEEE 802.9, Code Division Multiple Access (CDMA), WCDMA, GSM, LTE, Universal Terrestrial RAN (UTRAN), WiMax, or the like. Each transceiver may include a transmitter 933 and/or a receiver 935 to implement transmitter or receiver functionality, respectively, appropriate to the RAN links (e.g., frequency allocations and the like).

Further, the transmitter 933 and the receiver 935 of each transceiver may share circuit components, software, or firmware, or alternatively may be implemented separately.

In the illustrated embodiment, the communication functions of the communication subsystem 931 may include 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.

For example, the communication subsystem 931 may include cellular communication, WiFi communication, Bluetooth communication, and GPS communication. The network 943B may encompass wired and/or wireless networks such as a LAN, a WAN, a computer network, a wireless network, a telecommunications network, another like network, or any combination thereof. For example, the network 943B may be a cellular network, a WiFi network, and/or a near-field network. A power source 913 may be configured to provide Alternating Current (AC) or Direct Current (DC) power to components of the UE 900.

The features, benefits, and/or functions described herein may be implemented in one of the components of the UE 900 or partitioned across multiple components of the UE 900. Further, the features, benefits, and/or functions described herein may be

implemented in any combination of hardware, software, or firmware. In one example, the communication subsystem 931 may be configured to include any of the components described herein. Further, the processing circuitry 901 may be configured to communicate with any of such components over the bus 902. In another example, any of such components may be represented by program instructions stored in memory that, when executed by the processing circuitry 901, perform the corresponding functions described herein. In another example, the functionality of any of such components may be partitioned between the processing circuitry 901 and the communication subsystem 931.

In another example, the non-computationally intensive functions of any of such

components may be implemented in software or firmware and the computationally intensive functions may be implemented in hardware. Figure 10 is a schematic block diagram illustrating a virtualization environment 1000 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 a node (e.g., a virtualized base station or a virtualized radio access node) or to a device (e.g., a UE, a WD, or any other type of communication device) 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 (e.g., via one or more applications, components, functions, virtual machines, or containers executing on one or more physical processing nodes in one or more networks).

In some embodiments, some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines

implemented in one or more virtual environments 1000 hosted by one or more of hardware nodes 1030. Further, in embodiments in which the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node), then the network node may be entirely virtualized.

The functions may be implemented by one or more applications 1020 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operative to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein. The applications 1020 are run in the virtualization environment 1000 which provides hardware 1030 comprising processing circuitry 1060 and memory 1090. The memory 1090 contains instructions 1095 executable by the processing circuitry 1060 whereby the application 1020 is operative to provide one or more of the features, benefits, and/or functions disclosed herein.

The virtualization environment 1000 comprises general-purpose or special-purpose network hardware devices 1030 comprising a set of one or more processors or processing circuitry 1060, which may be Commercial Off-the-Shelf (COTS) processors, dedicated ASICs, or any other type of processing circuitry including digital or analog hardware components or special purpose processors. Each hardware device 1030 may comprise memory 1090-1 which may be non-persistent memory for temporarily storing instructions 1095 or software executed by the processing circuitry 1060. Each hardware device 1030 may comprise one or more Network Interface Controllers (NICs) 1070, also known as network interface cards, which include a physical network interface 1080. Each hardware device 1030 may also include non-transitory, persistent, machine-readable storage media 1090-2 having stored therein software 1095 and/or instructions executable by the processing circuitry 1060. The software 1095 may include any type of software including software for instantiating one or more virtualization layers 1050 (also referred to as hypervisors), software to execute virtual machines 1040, as well as software allowing it to execute functions, features, and/or benefits described in relation with some embodiments described herein.

The virtual machines 1040, comprise virtual processing, virtual memory, virtual networking or interface, and virtual storage, and may be run by a corresponding virtualization layer 1050 or hypervisor. Different embodiments of the instance of virtual appliance 1020 may be implemented on one or more of the virtual machines 1040, and the implementations may be made in different ways.

During operation, the processing circuitry 1060 executes the software 1095 to instantiate the hypervisor or virtualization layer 1050, which may sometimes be referred to as a Virtual Machine Monitor (VMM). The virtualization layer 1050 may present a virtual operating platform that appears like networking hardware to the virtual machine 1040.

As shown in Figure 10, the hardware 1030 may be a standalone network node with generic or specific components. The hardware 1030 may comprise an antenna 10225 and may implement some functions via virtualization. Alternatively, the hardware 1030 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 a Management and Orchestration (MANO) 10100, which, among others, oversees lifecycle management of the applications 1020.

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 CPE.

In the context of NFV, the virtual machine 1040 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 virtual machines 1040, and that part of the hardware 1030 that executes that virtual machine 1040, be it hardware dedicated to that virtual machine 1040 and/or hardware shared by that virtual machine 1040 with others of the virtual machines 1040, forms a separate Virtual Network Element (VNE).

Still in the context of NFV, Virtual Network Function (VNF) is responsible for handling specific network functions that run in one or more virtual machines 1040 on top of the hardware networking infrastructure 1030 and corresponds to the application 1020 in Figure 10.

In some embodiments, one or more radio units 10200 that each include one or more transmitters 10220 and one or more receivers 10210 may be coupled to the one or more antennas 10225. The radio units 10200 may communicate directly with the hardware nodes 1030 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 effected with the use of a control system 10230, which may alternatively be used for communication between the hardware nodes 1030 and the radio unit 10200.

With reference to Figure 11, in accordance with an embodiment, a communication system includes a telecommunication network 1110, such as a 3GPP-type cellular network, which comprises an access network 1111, such as a RAN, and a core network 1114. The access network 1111 comprises a plurality of base stations 1112A, 1112B, 1112C, such as NBs, eNBs, gNBs, or other types of wireless APs, each defining a corresponding coverage area 1113A, 1113B, 1113C. Each base station 1112A, 1112B, 1112C is connectable to the core network 1114 over a wired or wireless connection 1115. A first UE 1191 located in coverage area 1113C is configured to wirelessly connect to, or be paged by, the

corresponding base station 1112C. A second UE 1192 in coverage area 1113A is wirelessly connectable to the corresponding base station 1112A. While a plurality of UEs 1191, 1192 are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station 1112.

The telecommunication network 1110 is itself connected to a host computer 1130, which may be embodied in the hardware and/or software of a standalone server, a cloud- implemented server, a distributed server, or as processing resources in a server farm. The host computer 1130 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider. Connections 1121 and 1122 between telecommunication network 1110 and the host computer 1130 may extend directly from the core network 1114 to the host computer 1130 or may go via an optional intermediate network 1120. The intermediate network 1120 may be one of, or a combination of more than one of, a public, private, or hosted network; the intermediate network 1120, if any, may be a backbone network or the Internet; in particular, the intermediate network 1120 may comprise two or more sub-networks (not shown).

The communication system of Figure 11 as a whole enables connectivity between the connected UEs 1191, 1192 and the host computer 1130. The connectivity may be described as an Over-the-Top (OTT) connection 1150. The host computer 1130 and the connected UEs 1191, 1192 are configured to communicate data and/or signaling via the OTT connection 1150, using the access network 1111, the core network 1114, any intermediate network 1120, and possible further infrastructure (not shown) as

intermediaries. The OTT connection 1150 may be transparent in the sense that the participating communication devices through which the OTT connection 1150 passes are unaware of routing of uplink and downlink communications. For example, the base station 1112 may not or need not be informed about the past routing of an incoming downlink communication with data originating from the host computer 1130 to be forwarded (e.g., handed over) to a connected UE 1191. Similarly, the base station 1112 need not be aware of the future routing of an outgoing uplink communication originating from the UE 1191 towards the host computer 1130. Example implementations, in accordance with an embodiment, of the UE, base station, and host computer discussed in the preceding paragraphs will now be described with reference to Figure 12. In a communication system 1200, a host computer 1210 comprises hardware 1215 including a communication interface 1216 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of the communication system 1200. The host computer 1210 further comprises processing circuitry 1218, which may have storage and/or processing capabilities. In particular, the processing circuitry 1218 may comprise one or more programmable processors, ASICs, FPGAs, or combinations of these (not shown) adapted to execute instructions. The host computer 1210 further comprises software 1211, which is stored in or accessible by the host computer 1210 and executable by the processing circuitry 1218. The software 1211 includes a host application 1212. The host application 1212 may be operable to provide a service to a remote user, such as a UE 1230 connecting via an OTT connection 1250 terminating at the UE 1230 and the host computer 1210. In providing the service to the remote user, the host application 1212 may provide user data which is transmitted using the OTT connection 1250.

The communication system 1200 further includes a base station 1220 provided in a telecommunication system and comprising hardware 1225 enabling it to communicate with the host computer 1210 and with the UE 1230. The hardware 1225 may include a communication interface 1226 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of the communication system 1200, as well as a radio interface 1227 for setting up and maintaining at least a wireless connection 1270 with the UE 1230 located in a coverage area (not shown in Figure 12) served by the base station 1220. The communication interface 1226 may be configured to facilitate a connection 1260 to the host computer 1210. The connection 1260 may be direct or it may pass through a core network (not shown in Figure 12) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system. In the embodiment shown, the hardware 1225 of the base station 1220 further includes processing circuitry 1228, which may comprise one or more programmable processors, ASICs, FPGAs, or combinations of these (not shown) adapted to execute instructions. The base station 1220 further has software 1221 stored internally or accessible via an external connection.

The communication system 1200 further includes the UE 1230 already referred to. The UE's 1230 hardware 1235 may include a radio interface 1237 configured to set up and maintain a wireless connection 1270 with a base station serving a coverage area in which the UE 1230 is currently located. The hardware 1235 of the UE 1230 further includes processing circuitry 1238, which may comprise one or more programmable processors, ASICs, FPGAs, or combinations of these (not shown) adapted to execute instructions. The UE 1230 further comprises software 1231, which is stored in or accessible by the UE 1230 and executable by the processing circuitry 1238. The software 1231 includes a client application 1232. The client application 1232 may be operable to provide a service to a human or non-human user via the UE 1230, with the support of the host computer 1210.

In the host computer 1210, the executing host application 1212 may communicate with the executing client application 1232 via the OTT connection 1250 terminating at the UE 1230 and the host computer 1210. In providing the service to the user, the client application 1232 may receive request data from the host application 1212 and provide user data in response to the request data. The OTT connection 1250 may transfer both the request data and the user data. The client application 1232 may interact with the user to generate the user data that it provides.

It is noted that the host computer 1210, the base station 1220, and the UE 1230 illustrated in Figure 12 may be similar or identical to the host computer 1130, one of the base stations 1112A, 1112B, 1112C, and one of the UEs 1191, 1192 of Figure 11, respectively. This is to say, the inner workings of these entities may be as shown in Figure 12 and independently, the surrounding network topology may be that of Figure 11.

In Figure 12, the OTT connection 1250 has been drawn abstractly to illustrate the communication between the host computer 1210 and the UE 1230 via the base station 1220 without explicit reference to any intermediary devices and the precise routing of messages via these devices. The network infrastructure may determine the routing, which may be configured to hide from the UE 1230 or from the service provider operating the host computer 1210, or both. While the OTT connection 1250 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).

The wireless connection 1270 between the UE 1230 and the base station 1220 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to the UE 1230 using the OTT connection 1250, in which the wireless connection 1270 forms the last segment. More precisely, the teachings of these embodiments may improve, e.g., data rate, latency, and/or power consumption and thereby provide benefits such as, e.g., reduced user waiting time, relaxed restriction on file size, better

responsiveness, and/or extended battery lifetime.

A measurement procedure may be provided for the purpose of monitoring data rate, latency, and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection 1250 between the host computer 1210 and the UE 1230, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring the OTT connection 1250 may be implemented in the software 1211 and the hardware 1215 of the host computer 1210 or in the software 1231 and the hardware 1235 of the UE 1230, or both. In some embodiments, sensors (not shown) may be deployed in or in association with communication devices through which the OTT connection 1250 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which the software 1211, 1231 may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 1250 may include message format, retransmission settings, preferred routing, etc.; the reconfiguring need not affect the base station 1220, and it may be unknown or imperceptible to the base station 1220. Such procedures and functionalities may be known and practiced in the art. In certain embodiments,

measurements may involve proprietary UE signaling facilitating the host computer 1210's measurements of throughput, propagation times, latency, and the like. The measurements may be implemented in that the software 1211 and 1231 causes messages to be transmitted, in particular empty or 'dummy' messages, using the OTT connection 1250 while it monitors propagation times, errors, etc.

Figure 13 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station, and a UE which may be those described with reference to Figures 11 and 12. For simplicity of the present disclosure, only drawing references to Figure 13 will be included in this section. In step 1310, the host computer provides user data. In sub-step 1311 (which may be optional) of step 1310, the host computer provides the user data by executing a host application. In step 1320, the host computer initiates a transmission carrying the user data to the UE. In step 1330 (which may be optional), the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 1340 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

Figure 14 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station, and a UE which may be those described with reference to Figures 11 and 12. For simplicity of the present disclosure, only drawing references to Figure 14 will be included in this section. In step 1410 of the method, the host computer provides user data. In an optional sub-step (not shown) the host computer provides the user data by executing a host application. In step 1420, the host computer initiates a transmission carrying the user data to the UE. The transmission may pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure. In step 1430 (which may be optional), the UE receives the user data carried in the transmission.

Figure 15 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station, and a UE which may be those described with reference to Figures 11 and 12. For simplicity of the present disclosure, only drawing references to Figure 15 will be included in this section. In step 1510 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step 1520, the UE provides user data. In sub-step 1521 (which may be optional) of step 1520, the UE provides the user data by executing a client application. In sub-step 1511 (which may be optional) of step 1510, the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer. In providing the user data, the executed client application may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the UE initiates, in sub-step 1530 (which may be optional), transmission of the user data to the host computer. In step 1540 of the method, the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.

Figure 16 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station, and a UE which may be those described with reference to Figures 11 and 12. For simplicity of the present disclosure, only drawing references to Figure 16 will be included in this section. In step 1610 (which may be optional), in accordance with the teachings of the embodiments described throughout this disclosure, the base station receives user data from the UE. In step 1620 (which may be optional), the base station initiates transmission of the received user data to the host computer. In step 1630 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

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 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 ROM, 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.

Figure 17 illustrates a schematic block diagram of an apparatus 1700 in a wireless network (for example, the wireless network shown in Figure 8). The apparatus may be implemented in a wireless device or network node (e.g., the WD 810 or the network node 860 shown in Figure 8). The apparatus 1700 is operable to carry out the example method described with reference to Figure 3 for the gNB-CU and/or the gNB-DU, and possibly any other processes or methods disclosed herein. It is also to be understood that the method of Figure 3 is not necessarily carried out solely by the apparatus 1700. At least some operations of the method can be performed by one or more other entities.

The virtual apparatus 1700 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include 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 ROM, 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 several embodiments. In some implementations, the processing circuitry may be used to cause one or more units 1702 to perform the method of Figure 3 and any other suitable units of the apparatus 1700 to perform corresponding functions according one or more

embodiments of the present disclosure.

The term unit may have conventional meaning in the field of electronics, electrical devices, and/or electronic devices and may include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein.

Some example embodiments described herein are as follows.

Group A Embodiments

Embodiment 1: A method performed by a centralized unit of a base station in a radio access network, the method comprising: sending (300), from the centralized unit of the base station to a distributed unit of the base station, Protocol Data Unit, PDU, session information and a PDU session Aggregate Maximum Bit Rate, AMBR, for a PDU session.

Embodiment 2: The method of embodiment 1 wherein the base station is a New Radio base station, gNB, the centralized unit is a gNB-CU, and the distributed unit is a gNB- DU.

Embodiment 3: The method of embodiment 2 wherein sending the PDU session information and the PDU session AMBR for the PDU session comprises sending the PDU session information and the PDU session AMBR for the PDU session over a FI interface that interconnects the gNB-CU and the gNB-DU.

Embodiment 4: The method any one of embodiments 1 to 3 wherein sending the PDU session information and the PDU session AMBR for the PDU session comprises sending a User Equipment, UE, Context Setup Request message to the gNB-DU, wherein the UE Context Setup Request message comprises the PDU session information and the PDU session AMBR for the PDU session.

Embodiment 5: The method of embodiment 4 wherein the UE Context Setup Request message comprises a Data Radio Bearer, DRB, Identifier, ID, a PDU session ID of the PDU session associated with the DRB ID, and the PDU session AMBR associated with the PDU session ID.

Embodiment 6: The method of any one of embodiments 1 to 3 wherein sending the PDU session information and the PDU session AMBR for the PDU session comprises sending a PDU session Identifier, ID, of the PDU session and the PDU session AMBR together within a Quality of Service, QoS, Flow Level QoS Parameters structure. Embodiment 7: The method of any one of embodiments 1 to 6 wherein the PDU session is a PDU session for a wireless device.

Embodiment 8: A method performed by a distributed unit of a base station in a radio access network, the method comprising: receiving (300), from a centralized unit of the base station, Protocol Data Unit, PDU, session information and a PDU session

Aggregate Maximum Bit Rate, AMBR, for a PDU session; and storing (302) the PDU session information and the PDU session AMBR for the PDU session.

Embodiment 9: The method of embodiment 8 wherein storing the PDU session information and the PDU session AMBR for the PDU session comprises storing the PDU session information and the PDU session AMBR for the PDU session in an associated User Equipment, UE, context.

Embodiment 10: The method of embodiment 8 or 9 wherein the base station is a New Radio base station, gNB, the centralized unit is a gNB-CU, and the distributed unit is a gNB-DU.

Embodiment 11: The method of embodiment 10 wherein receiving the PDU session information and the PDU session AMBR for the PDU session comprises receiving the PDU session information and the PDU session AMBR for the PDU session over a FI interface that interconnects the gNB-CU and the gNB-DU.

Embodiment 12: The method any one of embodiments 8 to 11 wherein receiving the PDU session information and the PDU session AMBR for the PDU session comprises receiving a UE Context Setup Request message from the gNB-CU, wherein the UE Context Setup Request comprises the PDU session information and the PDU session AMBR for the PDU session.

Embodiment 13: The method of embodiment 12 wherein the UE Context Setup Request message comprises a Data Radio Bearer, DRB, Identifier, ID, a PDU session ID of the PDU session associated with the DRB ID, and the PDU session AMBR associated with the PDU session ID.

Embodiment 14: The method of any one of embodiments 8 to 11 wherein receiving the PDU session information and the PDU session AMBR for the PDU session comprises receiving a PDU session ID of the PDU session and the PDU session AMBR together within a Quality of Service, QoS, Flow Level QoS Parameters structure.

Embodiment 15: The method of any one of embodiments 8 to 14 wherein the PDU session is a PDU session for a wireless device.

Embodiment 16: The method of any of the previous embodiments, further comprising: obtaining user data; and forwarding the user data to a host computer or a wireless device.

Group B Embodiments

Embodiment 17: A base station, the base station comprising: processing circuitry configured to perform any of the steps of any of the Group A embodiments; and power supply circuitry configured to supply power to the base station.

Embodiment 18: A communication system including a host computer comprising: processing circuitry configured to provide user data; and a communication interface configured to forward the user data to a cellular network for transmission to a User Equipment, UE; wherein the cellular network comprises a base station having a radio interface and processing circuitry, the base station's processing circuitry configured to perform any of the steps of any of the Group A embodiments.

Embodiment 19: The communication system of the previous embodiment further including the base station.

Embodiment 20: The communication system of the previous 2 embodiments, further including the UE, wherein the UE is configured to communicate with the base station.

Embodiment 21: The communication system of the previous 3 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and the UE comprises processing circuitry configured to execute a client application associated with the host application.

Embodiment 22: A method implemented in a communication system including a host computer, a base station, and a User Equipment, UE, the method comprising: at the host computer, providing user data; and at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the base station performs any of the steps of any of the Group A embodiments.

Embodiment 23: The method of the previous embodiment, further comprising, at the base station, transmitting the user data.

Embodiment 24: The method of the previous 2 embodiments, wherein the user data is provided at the host computer by executing a host application, the method further comprising, at the UE, executing a client application associated with the host application.

Embodiment 25: A User Equipment, UE, configured to communicate with a base station, the UE comprising a radio interface and processing circuitry configured to perform the method of the previous 3 embodiments.

Embodiment 26: A communication system including a host computer comprising a communication interface configured to receive user data originating from a transmission from a User Equipment, UE, to a base station, wherein the base station comprises a radio interface and processing circuitry, the base station's processing circuitry configured to perform any of the steps of any of the Group A embodiments.

Embodiment 27: The communication system of the previous embodiment further including the base station.

Embodiment 28: The communication system of the previous 2 embodiments, further including the UE, wherein the UE is configured to communicate with the base station.

Embodiment 29: The communication system of the previous 3 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application; and the UE is configured to execute a client application associated with the host application, thereby providing the user data to be received by the host computer.

At least some of the following abbreviations may be used in this disclosure. If there is an inconsistency between abbreviations, preference should be given to how it is used above. If listed multiple times below, the first listing should be preferred over any subsequent listing(s).

• 2G Second Generation

• 3G Third Generation • 3GPP Third Generation Partnership Project

. 4G Fourth Generation

• 5G Fifth Generation

• 5GC Fifth Generation Core Network

. AC Alternating Current

• AMBR Aggregate Maximum Bit Rate

• AMF Access and Mobility Management Function

• AP Access Point

• ASIC Application Specific Integrated Circuit

• ATM Asynchronous Transfer Mode

. BS Base Station

• BSC Base Station Controller

• BTS Base Transceiver Station

. CD Compact Disk

• CDMA Code Division Multiple Access

• COTS Commercial Off-the-Shelf

• CP Control Plane

• CPE Customer Premise Equipment

• CPU Central Processing Unit

• CU Centralized Unit

• D2D Device-to- Device

• DAS Distributed Antenna System

. DC Direct Current

• DIMM Dual In-Line Memory Module

• DN Data Network

• DRB Data Radio Bearer

• DSP Digital Signal Processor

• DU Distributed Unit

• DVD Digital Video Disk

• EEPROM Electrically Erasable Programmable Read Only Memory • eMTC Enhanced Machine-Type Communication

• eNB Evolved Node B

• EN-DC Evolved Universal Terrestrial Radio Access Network Dual

Connectivity

• EPROM Erasable Programmable Read Only Memory

• E-SMLC Evolved Serving Mobile Location Center

• E-UTRAN Evolved Universal Terrestrial Radio Access Network

• FDD Frequency Division Duplexing

• FPGA Field Programmable Gate Array

• GBR Guaranteed Flow Bit Rate

• GHz Gigahertz

. gNB New Radio Base Station

• gNB-CU New Radio Base Station Centralized Unit

• gNB-DU New Radio Base Station Distributed Unit

• GPS Global Positioning System

• GSM Global System for Mobile Communications

• HDDS Holographic Digital Data Storage

• HD- DVD High-Density Digital Versatile Disc

• ID Identifier

• IE Information Element

. I/O Input and Output

• IoT Internet of Things

• IP Internet Protocol

• LAN Local Area Network

• LEE Laptop Embedded Equipment

• LME Laptop Mounted Equipment

• LTE Long Term Evolution

• M2M Machine-to-Machine

• MAC Medium Access Control

• MANO Management and Orchestration • MCE Multi-Cell/Multicast Coordination Entity

• MDT Minimization of Drive Tests

• MIMO Multiple Input Multiple Output

• MME Mobility Management Entity

• MSC Mobile Switching Center

• MSR Multi-Standard Radio

• MTC Machine-Type Communication

• NB-IoT Narrowband Internet of Things

• NFV Network Function Virtualization

• NG Next Generation

• NIC Network Interface Controller

• NR New Radio

• O&M Operation and Maintenance

• OSS Operations Support System

. OTT Over-the-Top

• PDA Personal Digital Assistant

• PDCP Packet Data Convergence Protocol

• PDU Protocol Data Unit

• PROM Programmable Read Only Memory

• PSTN Public Switched Telephone Networks

• QoS Quality of Service

• RAID Redundant Array of Independent Disks

• RAM Random Access Memory

• RAN Radio Access Network

• RAT Radio Access Technology

• RF Radio Frequency

• RNC Radio Network Controller

• RNL Radio Network Layer

• ROM Read Only Memory

• RRH Remote Radio Head • RRU Remote Radio Unit

• RUIM Removable User Identity

• SDRAM Synchronous Dynamic Random Access Memory

• SIM Subscriber Identity Module

• SOC System on a Chip

• SON Self-Organizing Network

• SONET Synchronous Optical Networking

• TCP Transmission Control Protocol

• TDD Time Division Duplexing

• TNL Transport Network Layer

• TS Technical Specification

• UE User Equipment

• UMTS Universal Mobile Telecommunications System

• UP User Plane

• USB Universal Serial Bus

• UTRAN Universal Terrestrial Radio Access Network

• V2I Vehicle-to-Infrastructure

• V2V Vehicle-to-Vehicle

• V2X Veh icle-to- Everyth i ng

• VMM Virtual Machine Monitor

• VNE Virtual Network Element

• VNF Virtual Network Function

• VoIP Voice over Internet Protocol

• WAN Wide Area Network

• WCDMA Wideband Code Division Multiple Access

• WD Wireless Device

• WiMax Worldwide Interoperability for Microwave Access

• WLAN Wireless Local Area Network Those skilled in the art will recognize improvements and modifications to the embodiments of the present disclosure. All such improvements and modifications are considered within the scope of the concepts disclosed herein.

Claims

Claims What is claimed is:

1. A method performed by a base station (202) in a radio access network, the base station (202) having a split architecture comprising a centralized unit (204) and a distributed unit (206), the method comprising:

sending (300), from the centralized unit (204) to the distributed unit (206), Protocol Data Unit, PDU, session information and an uplink PDU session Aggregate Maximum Bit Rate, AMBR, for a PDU session;

receiving (300), at the distributed unit (206) from the centralized unit (204), the PDU session information and the uplink PDU session AMBR for the PDU session; and

storing (302) the PDU session information and the uplink PDU session AMBR for the PDU session at the distributed unit (206).

2. The method of claim 1 further comprising using (304), at the distributed unit (206), the PDU session information and the uplink PDU session AMBR for the PDU session to provide uplink AMBR control for the PDU session.

3. A method performed by a centralized unit (204) of a base station (202) in a radio access network, the method comprising:

sending (300), from the centralized unit (204) of the base station (202) to a distributed unit (206) of the base station (202), Protocol Data Unit, PDU, session information and an uplink PDU session Aggregate Maximum Bit Rate, AMBR, for a PDU session.

4. The method of claim 3 wherein the base station (202) is a New Radio base station, gNB, the centralized unit (204) is a gNB Centralized Unit, gNB-CU, and the distributed unit (206) is a gNB Distributed Unit, gNB-DU.

5. The method of claim 4 wherein sending (300) the PDU session information and the uplink PDU session AMBR for the PDU session comprises sending (300) the PDU session information and the uplink PDU session AMBR for the PDU session over a FI interface that interconnects the gNB-CU and the gNB-DU.

6. The method any one of claims 3 to 5 wherein sending (300) the PDU session information and the uplink PDU session AMBR for the PDU session comprises sending a User Equipment, UE, Context Setup Request message to the distributed unit (206), wherein the UE Context Setup Request message comprises the PDU session information and the uplink PDU session AMBR for the PDU session.

7. The method of claim 6 wherein the UE Context Setup Request message comprises: a Data Radio Bearer, DRB, Identifier, ID, of a DRB associated with the PDU session; a PDU session ID of the PDU session; and

the uplink PDU session AMBR associated with the PDU session ID.

8. The method of claim 6 wherein the UE Context Setup Request message comprises:

• Data Radio Bearer, DRB, information comprising:

o a DRB Identifier, ID, of a DRB associated with the PDU session; and o a PDU session ID of the PDU session; and

• a PDU session resource information list comprising PDU session resource

information for each of one or more PDU sessions, wherein the one or more PDU sessions comprise the PDU session and the PDU session resource information for the PDU session comprises:

o a PDU session ID of the PDU session; and

o the uplink PDU session AMBR for the PDU session.

9. The method of any one of claims 3 to 5 wherein sending (600) the PDU session information and the uplink PDU session AMBR for the PDU session comprises sending a PDU session Identifier, ID, of the PDU session and the uplink PDU session AMBR together within a Quality of Service, QoS, Flow Level QoS Parameters structure.

10. The method of any one of claims 3 to 5 wherein sending (600) the PDU session information and the uplink PDU session AMBR for the PDU session comprises sending a message to the distributed unit (206), wherein:

the message comprises Quality of Service, QoS, flow level QoS parameters information to be applied to a QoS flow or to a Data Resource Bearer, DRB, associated with the PDU session; and

the QoS flow level QoS parameters information comprises a PDU session Identifier, ID, of the PDU session and the uplink PDU session AMBR for the PDU session.

11. The method of claim 10 wherein the message is a User Equipment, UE, Context Setup Request message.

12. The method of claim 10 wherein the message is a User Equipment, UE, Context Modification message.

13. The method of any one of claims 3 to 12 wherein the PDU session is a PDU session for a wireless device.

14. A centralized unit (204) of a base station (202, 860) in a radio access network, the centralized unit (204) adapted to:

send (300), from the centralized unit (204) of the base station (202, 860) to a distributed unit (206) of the base station (202, 860), Protocol Data Unit, PDU, session information and an uplink PDU session Aggregate Maximum Bit Rate, AMBR, for a PDU session.

15. The centralized unit (204) of claim 14 wherein the centralized unit (204) is further adapted to perform the method of any one of claims 4 to 13.

16. The centralized unit (204) of claim 14 comprising:

an interface (890); and processing circuitry (870) associated with the interface (890), the processing circuitry (870) configured to cause the centralized unit (204) to send (300), from the centralized unit (204) of the base station (202, 860) to the distributed unit (206) of the base station (202, 860), PDU session information and an uplink PDU session AMBR for a PDU session.

17. A method performed by a distributed unit (206) of a base station (202) in a radio access network, the method comprising:

receiving (300), from a centralized unit (204) of the base station (202), Protocol Data Unit, PDU, session information and an uplink PDU session Aggregate Maximum Bit Rate, AMBR, for a PDU session; and

storing (302) the PDU session information and the uplink PDU session AMBR for the PDU session.

18. The method of claim 17 further comprising using (304) the PDU session information and the uplink PDU session AMBR for the PDU session to provide uplink PDU session AMBR control for the PDU session.

19. The method of claim 17 or 18 wherein storing (302) the PDU session information and the uplink PDU session AMBR for the PDU session comprises storing (302) the PDU session information and the uplink PDU session AMBR for the PDU session in an associated User Equipment, UE, context.

20. The method of any one of claims 17 to 19 wherein the base station (202) is a New Radio base station, gNB, the centralized unit (204) is a gNB Centralized Unit, gNB-CU, and the distributed unit (206) is a gNB Distributed Unit, gNB-DU.

21. The method of claim 20 wherein receiving (300) the PDU session information and the uplink PDU session AMBR for the PDU session comprises receiving (300) the PDU session information and the uplink PDU session AMBR for the PDU session over a FI interface that interconnects the gNB-CU and the gNB-DU.

22. The method any one of claims 17 to 21 wherein receiving (300) the PDU session information and the uplink PDU session AMBR for the PDU session comprises receiving a UE Context Setup Request message from the centralized unit (204), wherein the UE Context Setup Request message comprises the PDU session information and the uplink PDU session AMBR for the PDU session.

23. The method of claim 22 wherein the UE Context Setup Request message comprises: a Data Radio Bearer, DRB, Identifier, ID, of a DRB associated with the PDU session; a PDU session ID of the PDU session; and

the uplink PDU session AMBR associated with the PDU session ID.

24. The method of claim 22 wherein the UE Context Setup Request message comprises:

• Data Radio Bearer, DRB, information comprising:

• a PDU session resource information list comprising PDU session resource

o a PDU session ID of the PDU session; and

o the uplink PDU session AMBR for the PDU session.

25. The method of any one of claims 17 to 21 wherein receiving (300) the PDU session information and the uplink PDU session AMBR for the PDU session comprises receiving a PDU session Identifier, ID, of the PDU session and the uplink PDU session AMBR together within a Quality of Service, QoS, Flow Level QoS Parameters structure.

26. The method of any one of claims 17 to 21 wherein receiving (600) the PDU session information and the uplink PDU session AMBR for the PDU session comprises receiving a message from the centralized unit (204), wherein: the message comprises Quality of Service, QoS, flow level QoS parameters information to be applied to a QoS flow or to a Data Resource Bearer, DRB, associated with the PDU session; and

27. The method of claim 26 wherein the message is a UE Context Setup Request message.

28. The method of claim 26 wherein the message is a UE Context Modification message.

29. The method of any one of claims 17 to 28 wherein the PDU session is a PDU session for a wireless device.

30. A distributed unit (206) for a base station (202, 860) in a radio access network, the distributed unit (206) adapted to:

receive (300), from a centralized unit (204) of the base station (202, 860), Protocol Data Unit, PDU, session information and an uplink PDU session Aggregate Maximum Bit Rate, AMBR, for a PDU session; and

store (302) the PDU session information and the uplink PDU session AMBR for the PDU session.

31. The distributed unit (206) of claim 30 wherein the distributed unit (206) is further adapted to perform the method of any one of claims 18 to 29.

32. The distributed unit (206) of claim 30 comprising:

an interface (890); and

processing circuitry (870) associated with the interface (890), the processing circuitry (870) configured to cause the distributed unit (206) to receive (300) the PDU session information and the uplink PDU session AMBR for the PDU session from the centralized unit (204) and store (302) the PDU session information and the uplink PDU session AMBR for the PDU session.