First network node, second network node, and methods performed therein in a communication network

Abstract

Embodiments herein relate to, for example, a method performed by a first network node (140) for handling communication in a communication network. The first network node (140) receives from a second network node (150), an indication, wherein the indication indicates a rate control of a QoS flow and / or a direction of communication for the rate control for the QoS flow.

Description

[0001] FIRST NETWORK NODE, SECOND NETWORK NODE, AND METHODS PERFORMED THEREIN IN A COMMUNICATION NETWORK

[0002] TECHNICAL FIELD

[0003] Embodiments herein relate to a first network node, a second network node, and methods performed therein regarding wireless communication. Furthermore, a computer program product and a computer readable storage medium are also provided herein. In particular, embodiments herein relate to handling communication in a communication network.

[0004] BACKGROUND

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

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

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

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

[0009] Real-time services such as voice calls, real time video, cloud gaming and / or extended reality (XR) are sensitive to performance degradation. XR includes services provided by computer technologies and wearables that allow for human-machine interaction in real and virtual mixed environments. XR includes virtual reality (VR), augmented reality (AR), mixed reality (MR), cloud gaming, and / or areas interpolated among them.

[0010] In RAN#105 (Sept. 2024), in the Rel-19 XR work item description (WID), an objective on UL rate control from RAN2 was added:

[0011]

[0012] Network exposure of per quality of service (QoS) flow and / or per data radio bearer (DRB) congestion information was discussed in RAN2, see R2-2213226. It was agreed that

[0013]

[0014]

[0015] RAN2 has informed RAN3 of its agreement on release (Rel)-19 XR UL bit rate control and requests feedback from RAN3 in the liaison copied below, see R3-250012:

[0016]

[0017] RAN3 has replied to RAN2 in R3-250805 agreeing that both options have an impact on the F1 interface. RAN3 will further discuss whether gNB-distributed unit (DU) can support per QoS flow data bit rate control when time unit (TU) is available.

[0018] Furthermore, RAN2 has made the following agreements :

[0019] >

[0020] >

[0021] >

[0022] >

[0023]

[0024] >

[0025] >

[0026]

[0027] The overall 5G RAN, also referred to as NG-RAN, architecture is depicted in Fig. 1A. An Xn-C interface connects two gNB-central units (CU) and an F1 interface between gNB- CU and gNB-DU.

[0028] The gNB with the split architecture is depicted in Fig. 1B.

[0029] A gNB- CU hosts the radio resource control (RRC) and / or the control plane part of the packet data convergence protocol (PDCP); a gNB-DU hosts radio link control (RLC), medium access control (MAC) and the physical layer (PHY). An E1 interface connects between a gNB-CU-control plane (CP) and a gNB-CU-user plane (UP).

[0030] In Dual Connectivity, the master node (MN) and secondary node (SN) host separate RRC in CP and MAC layer in the UP, see Fig. 1C.

[0031] SUMMARY

[0032] As part of developing embodiments herein one or more issues have been identified. In the current gNB F1 split architecture, the MAC scheduler in the gNB-DU works on per DRB basis for a MAC control element (CE) indication. But there is no related F1AP Information Element (IE) in TS 38.473 v.18.4.0 for the purpose of rate control. In fact, the gNB-DU may not know which DRB requires rate control, to reduce or throttle rate, in case of congestion detected, and to send the MAC CE to the UE.

[0033] Similarly, there is no indication for the QoS flow or flows that are multiplexed in the DRB which could serve to indicate which one requires bit rate control.

[0034] In case the CN is able to provide information on rate control such as XR rate control, the protocol between CN and RAN, such as NGAP, may need to be enhanced for this purpose. It is not clear in which assistance information the CN may indicate that one or several QoS flows will be subject to rate control, and for which associated direction, i.e., UL or DL.

[0035] Furthermore, in case of handover, a target node for handover cannot know the setup resources by the source node of the QoS flows in different protocol data unit (PDU) sessions, or within different DRBs, and the respective association among those DRBs with rate control are unknown to such a target node.This issue is also applicable to the dual connectivity (DC) architecture where the master node (MN) and / or secondary node (SN) are unaware whether the one or more QoS flows are subject to rate control.

[0036] That the rate control for a QoS flow or a DRB is unknown may reduce or limit performance and / or experienced performance of the communication network.

[0037] An object of embodiments herein is to improve performance of the communication network. According to an aspect the object is achieved, according to some embodiments herein, by providing a method performed by a first network node, such as an NG-RAN node, a DU, a UP unit, a source or target radio network node, for handling communication in a communication network. The first network node receives from a second network node, an indication indicating a rate control of a QoS flow and / or a direction of communication for the rate control for the QoS flow. The first network node may handle a session based on the indication. The first network node may determine which QoS flows that can be rate adapted, throttled, reduced, controlled, boosted, increased, and / or for which direction based on the indication.

[0038] According to another aspect the object is achieved, according to some embodiments herein, by providing a method performed by a second network node, such as CN node, a CU, a CP unit, a source or target radio network node, for handling communication in a communication network. The second network node transmits to a first network node, an indication indicating a rate control of a QoS flow and / or a direction of communication for the rate control for the QoS flow.

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

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

[0041] Thus, according to an aspect the object is achieved, according to some embodiments herein, by providing a first network node for handling communication in a communication network. The first network node is configured to receive from a second network node, an indication indicating a rate control of a QoS flow and / or a direction of communication for the rate control for the QoS flow.

[0042] According to another aspect the object is achieved, according to some embodiments herein, by providing a second network node for handling communication in a communication network. The second network node is configured to transmit to a first network node, an indicationindicating a rate control of a QoS flow and / or a direction of communication for the rate control for the QoS flow.

[0043] Embodiments herein provide methods to allow, for example, the CN signaling assistance information in the QoS Flow level information on which QoS Flow that may be subject to XR rate control in a specific direction: UL and / or DL. The first network node, such as a NG-RAN node, may use the information to multiplex the QoS Flows subject to rate control into the DRB.

[0044] In another example, the gNB-Cll provides to a gNB-Dll an indication over the F1 interface that a DRB is subject to rate control, i.e. , reduced, or throttled.

[0045] During NG-based orXn based handover, the source gNB may indicate the indication, such as a rate control indication, of the QoS flow received from CN to a target gNB in a PDU Session.

[0046] During dual connectivity (DC) procedures, a MN or a SN may indicate to a SN or a MN which one or more QoS flows in a master cell group (MCG) and / or secondary cell group (SCG) terminated bearers are subject to rate control.

[0047] In case of CLI-CP and CU-LIP E1 split, the CU-LIP is an example of the first network node that is made aware of the rate control indication for the QoS flow by the indication transmitted by the CU-CP.

[0048] Embodiments herein may ensure that the first network node, such as a gNB, receives the indication in, for example, assistance information, from the second network node, such as a CN node, to be aware of which one or more QoS flows may be throttled, reduced, controlled, boosted, and / or increased and for which direction. Some embodiments herein may also fix a gap in the F1 split, where the gNB-Dll may not know which DRB, or QoS Flow identifier (QFI), that may be subject to the rate control indication over the MAC control element (CE). In the UL, this helps the gNB-DU to make a more informed decision on which UEs that may be subject to rate adaptation. Embodiments herein enable an efficient rate adaption or similar, and may improve performance, or experienced performance, of the communication network.

[0049] BRIEF DESCRIPTION OF THE DRAWINGS

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

[0051] Fig. 1A shows an architecture according to prior art;

[0052] Fig. 1B shows an architecture according to prior art;

[0053] Fig. 1C shows an architecture according to prior art;

[0054] Fig. 2 shows an overview depicting a communication network according to embodiments herein;

[0055] Fig. 3 is a combined flowchart and signaling scheme according to embodiments herein; Fig. 4 shows a flowchart illustrating a method performed by a first network node according to embodiments herein;Fig. 5 shows a flowchart illustrating a method performed by a second network node according to embodiments herein;

[0056] Fig. 6 shows a block diagram depicting embodiments of a first network node according to embodiments herein;

[0057] Fig. 7 shows a block diagram depicting embodiments of a second network node according to embodiments herein;

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

[0059] Fig. 9 shows a communication system 15200 in accordance with some embodiments; Fig. 10 shows a UE 15300 in accordance with some embodiments;

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

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

[0062] DETAILED DESCRIPTION

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

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

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

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

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

[0068] The communication network 1 may further comprise a number of core network nodes providing, e.g. in NR, network functions (NF) or actually instantiations of NFs also referred to as NF instances, such as a first core network node 16 providing, for example, an instantiation of an AMF or SMF, a second core network node 17 providing an instantiation of a NRF, and a third core network node 18 providing, for example, an instantiation of an PCF, or any other NF instances in the communication network 1. The different NF instances may have different tasks. Other functions may be for 6G, or LTE such as Mobility Management Entity (MME) or similar. The respective node may be a standalone server, a cloud-implemented server, a distributed server or processing resources in a server farm or same node. Embodiments hereinmay be implemented as physical bare metal, virtual or cloud native such as Kubernetes environment in e.g. hyper-cloud networks.

[0069] According to embodiments herein a second network node 150, such as the first core network node 16, the first radio network node 12, a CU, a CP node, the second radio network node 13 or similar, transmits to a first network node 140 such as the first radio network node 12, the second radio network node 13, a DU, a target radio network node, a UP node or similar, an indication, such as a value or index value, or flag, indicating a rate control of a QoS flow and / or a direction of communication for the rate control for the QoS flow. The rate control for the QoS flow may be per DRB. The first network node 140 handles a session based on the received indication. The first network node 140 may determine which QoS flows that can be throttled, reduced, controlled, boosted, increased, and / or for which direction based on the received indication. The indication may be referred to as bit rate control indication, rate indication, or rate control indication. The indication enables the first network node 140 to make a more informed decision on which UEs that may be subject to rate adaptation. Embodiments herein enable an efficient rate adaption or similar, and may improve performance, or experienced performance, of the communication network.

[0070] Embodiments herein provide one or more solutions to handle communications.

[0071] In one embodiment, the first network node 140 receives the indication from the second network node 150, for example, over an F1 Application Protocol (F1AP) message, with DRB information containing a rate control indication. Thus, the indication may be for QoS flow per DRB level. The F1AP message may be a UE CONTEXT SETUP REQUEST or UE CONTEXT MODIFICATION REQUEST message that contains the indication such as a Rate Control Needed information element (IE), as part of the DRB information IE in a DRB to Be Setup List IE.

[0072] Additionally, or alternatively, the first network node 140 may receive the indication from the second network node over F1AP message with QoS Flow information containing the rate control indication for the QoS Flow multiplexed in the DRB.

[0073] Additionally, or alternatively, the first network node 140 may receive the indication from the second network node 150 in the QoS Flow Information indicating which QoS flows that can be subject to rate control, i.e., are rate adaptive.

[0074] The indication may further indicate the direction, i.e., UL, DL, or both for which the QoS flow may be subject to rate control.

[0075] The indication may be included: in PDU Session information sent over PDU Session Content Management procedures defined in Next Generation Application Protocol (NGAP); in Handover Request Procedure defined in NGAP; in NGAP PATH SWITCH REQUEST message; in an E1 message during Bearer Context management procedures; and / or as part of the QoS parameters over XnAP.Embodiments herein may ensure that the first network node 140 receives the indication of rate control such as in the assistance information from the second network node 150 to be aware of which one or more QoS flows that can or may be throttled, reduced, controlled, boosted, increased, and / or for which direction. Some embodiments herein may also fix a gap in the F1 split, where the gNB-Dll cannot know which DRB, or QFI, that may be subject to Rate control indication over MAC CE. In the UL, the gNB-Dll may take the indication into account and make a more informed decision on which UEs should be subject to rate adaptation. Embodiments herein provide an efficient handling of resources and improve performance, or experienced performance, of the communication network.

[0076] Fig. 3 is a combined flow chart and signaling scheme according to some embodiments herein. Actions performed in some optional embodiments are marked with dashed boxes.

[0077] Action 301. The second network node 150 transmits to the first network node 140, such as the first radio network node 12 and / or the second radio network node 13, the UP node, or the DU, the indication indicating the rate control of the QoS flow and / or the direction of communication for the rate control for the QoS flow. The rate control may be XR rate control, and the direction may be UL, DL, or both. Thus, the second network node 150 may transmit a value of an XR rate control parameter in an QoS message.

[0078] Action 302. The first network node 140 may handle the session based on the indication. The first network node may determine which QoS flows that can be rate adapted, throttled, reduced, controlled, boosted, and / or increased; and / or for which direction, based on the indication.

[0079] Action 303. The first network node 140 may transmit a second indication to the second network node 150 and / or transmits a second query indication from the UE 10 requesting to boost or increase the bit rate for an application. The second indication indicates congestion at the first network node 140.

[0080] Action 304. The second network node 150 may transmit to the first network node 140, a third indication indicating to boost or increase the bit rate of the application within the range of the supported bit rates.

[0081] Action 305. The first network node 140 may handle the session based on the third indication.

[0082] The method actions performed by the first network node 140, such as a radio network node, a DU, the second radio network node 13, the UP node, and / or the first radio network node 12, for handling communication in the communication network, for example, handling a session, according to embodiments herein will now be described with reference to a flowchart depicted in Fig. 4. The actions do not have to be taken in the order stated below, but may be taken in any suitable order. Actions performed in some embodiments are marked with dashed boxes.Action 401. The first network node 140 receives from the second network node 150 the indication indicating the rate control of a QoS flow and / or a direction of communication for the rate control for the QoS flow. The rate control for the QoS flow may be per DRB level. The rate control may be XR rate control, and / or the direction may be UL, DL, or both. Thus, the second network node 150 may transmit a value of an XR rate control parameter in an QoS message. The indication may be a value, index value, or a flag of the rate control parameter. The indication may be received in a NGAP message, E1AP message, F1AP message, and / or an XnAP message. The indication may indicate one or more QoS flows that are subject to downlink and / or uplink rate control.

[0083] Action 402. The first network node 140 may handle the session based on the indication. The first network node 140 may determine which one or more QoS flows that can be rate controlled, and / or for which direction based on the indication. The first network node 140 may determine which one or more QoS flows that can be rate adapted, throttled, reduced, controlled, boosted, increased, and / or for which direction based on the received indication. The first network node 140 may use the indication to multiplex QoS Flows subject to rate control into a DRB.

[0084] Action 403. The first network node 140 may transmit the second indication to the second network node 150, and / or may transmit the second query indication from the UE, requesting to boost or increase the bit rate for the application. The second indication may indicate congestion at the first network node 140. The second indication may comprise a confirmation indication whether the rate control has been applied in a F1AP message to the second network node 150 being exemplified as a gNB-Cll, and the decision of the control, i.e. , reduced, or throttled the session.

[0085] Action 404. The first network node 140 may further receive from the second network node 150, the third indication indicating to boost or increase the bit rate of the application within the range of the supported bit rates.

[0086] Action 405. The first network node 140 may then handle the session based on the third indication. The first network node 140 may boost or increase the bit rate of the application of the session.

[0087] The first network node 140 may comprise a distributed unit and the second network node 150 may comprise a central unit; the first network node 140 may comprise a target radio network node and the second network node 150 may comprise a source radio network node; or the first network node 140 may comprise a radio network node and the second network node may comprise a core network node.

[0088] Embodiments herein provide methods to allow, for example, CN signaling assistance information in the QoS Flow level information on which QoS Flow may be subject to XR rate control in a specific direction: UL and / or DL. The first network node 140 such as an NG-RAN may use the information to multiplex the QoS Flows subject to rate control into the DRB. The rate control may be for QoS flows per DRB.Alternatively, or additionally, the first network node 140 such as a gNB-Cll may provide the indication over the F1 interface indicating that the DRB, or one or more QoS flows per DRB, is subject to rate control, i.e., reduced, or throttled.

[0089] Alternatively, or additionally, during NG-based or Xn based handover, the first network node 140 such as a source gNB transmits the indication of the QoS flow received from CN to a target node in the PDU Session.

[0090] Alternatively, or additionally, during DC procedures, an MN and / or an SN indicates to an SN and / or an MN which QoS flows in the master cell group and / or secondary cell group (MCG / SCG) terminated bearers are subject to rate control.

[0091] In case of CLI-CP and CU-LIP E1 split, the CU-LIP is made aware of the indication indicating the rate control for the QoS flow.

[0092] The method actions performed by the second network node 150, such as a CN node, a CU, a source / target radio network node, a CP node, an AMF or an SMF, for handling communication in the communication network 1 according to embodiments herein will now be described with reference to a flowchart depicted in Fig. 5. The actions do not have to be taken in the order stated below, but may be taken in any suitable order. Actions performed in some embodiments are marked with dashed boxes.

[0093] Action 501. The second network node 150 transmits to the first network node 140 the indication indicating the rate control of the QoS flow and / or the direction of communication for the rate control for the QoS flow. The rate control may be XR rate control, the direction may be UL, DL, or both. Thus, the second network node 150 may transmit a value of an XR rate control parameter in an QoS message. The indication may be transmitted in a NGAP message, E1AP message, F1AP message, and / or an XnAP message. The indication may indicate one or more QoS flows that are subject to downlink and / or uplink rate control.

[0094] Action 502. The second network node 150 may receive the second indication from the first network node 140, and / or receive the second query indication from the UE 10, requesting to boost or increase the bit rate for the application. The second indication indicates congestion at the first network node 140.

[0095] Action 503. The second network node 150 may transmit to the first network node 140, the third indication indicating to boost or increase the bit rate of the application within the range of the supported bit rates.

[0096] The first network node 140 may comprise a distributed unit and the second network node 150 may comprise a central unit; the first network node 140 may comprise a target radio network node and the second network node 150 may comprise a source radio network node; or the first network node 140 may comprise a radio network node and the second network node 150 may comprise a core network node.F1AP embodiments:

[0097] In one embodiment, the first network node 140 being exemplified as a gNB-Dll, may receive the indication from the second network node 150 being exemplified as a gNB-Cll, over an F1AP message with DRB information containing the indication.

[0098] In one embodiment, the F1AP message may comprise a UE CONTEXT SETUP REQUEST or UE CONTEXT MODIFICATION REQUEST message that contains the indication of a Rate Control Needed IE, as part of the DRB information IE in the DRB to Be Setup List IE. In one embodiment, the indication of the Rate Control Needed IE may be a flag ENUMERATED (true, ...), or indicating to reduce or throttle, or a range of supported bit rates.

[0099] In one embodiment, the first network node 140 being exemplified as the gNB-DU may provide a confirmation indication whether the rate control has been applied in a F1AP message to the second network node 150 being exemplified as a gNB-CU, and the decision of the control, i.e., reduced, or throttled. This can be UE CONTEXT SETUP RESPONSE or UE CONTEXT MODIFICATION RESPONSE or NOTIFY message.

[0100] In one alternative embodiment to 1), the first network node 140 being exemplified as a gNB-DU receives the indication from the second network node 150 being exemplified as a gNB-CU over F1AP message with QoS Flow information containing the indication for the QoS Flow multiplexed in the DRB.

[0101] In another embodiment, the first network node 140 receives the third indication from the second network node 150 over an F1AP message to boost or increase the bit rate of the application within the range of the supported bit rates. In another aspect, the third indication may be received either in response to the second indication from the first network node 140 with information on congestion at the first network node 140 and / or a second “query” indication from the UE 10 requesting to boost or increase the bit rate for the application.

[0102] NGAP embodiments:

[0103] In one embodiment, the first network node 140 being exemplified as a NG-RAN receives the indication from the second network node 150 being exemplified as a CN node in the QoS Flow QoS Information indicating which QoS flows that are subject to rate control, i.e., is rate adaptive.

[0104] In one embodiment, the second network node 150 may further indicate the direction, i.e., UL, DL, or both, for which the QoS flow is subject to rate control.

[0105] In one embodiment, the indication may be included in the PDU Session information sent over PDU Session Content Management procedures defined in NGAP.In one embodiment, the indication of QoS rate control may be included in a Handover Request Procedure defined in NGAP.

[0106] During NGAP handover, the first network node 140 being exemplified as a CN node receives the indication from the second network node 150 being exemplified as a NG-RAN node including the indication for the QoS flow in the NGAP HANDOVER REQUEST ACKNOWLEDGE message in the container towards the target NG-RAN.

[0107] During XnAP handover and Path Switch Request, the first network node 140 being exemplified as a CN node receives the indication from the second network node 150 being exemplified as a NG-RAN including the indication for the QoS flow in the NGAP PATH SWITCH REQUEST message.

[0108] E1AP General embodiments.

[0109] In one embodiment, the first network node 140 being exemplified as a gNB-CU-UP, receives from the second network node 150 being exemplified as a gNB-CU-CP the indication of the QoS Flow as part of QoS parameters over E1 message during Bearer Context management procedures.

[0110] XnAP General embodiments.

[0111] In one embodiment, the first network node 140 being exemplified as a NG-RAN receives the indication for a QoS Flow as part of QoS parameters over XnAP message from the second network node 150 being exemplified as a NG-RAN in the following procedures: a. HANDOVER REQUEST message and RETRIEVE UE CONTEXT REQUEST message.

[0112] b. S-NODE ADDITION REQUEST message.

[0113] c. S-NODE MODIFICATION REQUEST .

[0114] i. In PDU Session Resource Setup Information - SN terminated IE or ii. the PDU Session Resource Modification Information - SN terminated IE or iii. the PDU Session Resource Setup Information - MN terminated IE or iv. the PDU Session Resource Modification Information - MN terminated IE

[0115] TS 38.473 implementation example below with added lEs are bold, underlined and in italic font.

[0116] TS 38.473

[0117] 9.2.2.1 UE CONTEXT SETUP REQUEST

[0118] This message is sent by the gNB-CU to request the setup of a UE context.

[0119] > <>

[0120] >

[0121] >

[0122] <

[0123] >

[0124] >

[0125] >

[0126] >

[0127] >

[0128]

[0129] >

[0130]

[0131]

[0132]

[0133]

[0134] Fig. 6 is a block diagram depicting the first network node 140, such as the first radio network node 12, the second radio network node 13, UP node, or DU, for handling communication in the communication network 1 according to embodiments herein.

[0135] The first network node 140 may comprise a distributed unit and the second network node 150 may comprise a central unit; the first network node 140 may comprise a target radio network node and the second network node 150 may comprise a source radio network node; or the first network node 140 may comprise a radio network node and the second network node 150 may comprise a core network node.

[0136] The first network node 140 may comprise processing circuitry 601, e.g. one or more processors, configured to perform the methods herein.

[0137] The first network node 140 and / or the processing circuitry 601 is configured to receive from the second network node 150, the indication. The indication indicates the rate control of the QoS flow and / or the direction of communication for the rate control for the QoS flow. The rate control may be XR rate control, the direction may be UL, DL, or both. Thus, the first network node 140 and / or the processing circuitry 601 may be configured to receive a value of an XR rate control parameter in a QoS message. The indication may be a value or index value, flag of the rate control parameter. The indication may be received in a NGAP message, E1AP message, F1AP message, and / or an XnAP message. The indication may indicate one or more QoS flows that are subject to downlink and / or uplink rate control.

[0138] The first network node 140 and / or the processing circuitry 601 may be configured to handle the session based on the indication. The first network node 140 and / or the processing circuitry 601 may be configured to determine which one or more QoS flows that can be rate controlled, and / or for which direction based on the indication. The first network node 140 and / or the processing circuitry 601 may be configured to determine which one or more QoS flows that can be rate adapted, throttled, reduced, controlled, boosted, increased, and / or for which direction based on the indication.The first network node 140 and / or the processing circuitry 601 may be configured to transmit the second indication to the second network node 150, and / or transmit the second query indication from the UE 10, requesting to boost or increase the bit rate for the application. The second indication indicates congestion at the first network node 140.

[0139] The first network node 140 and / or the processing circuitry 601 may be configured to receive from the second network node 150, the third indication indicating to boost or increase the bit rate of the application within the range of the supported bit rates.

[0140] The first network node 140 and / or the processing circuitry 601 may be configured to handle the session based on the third indication.

[0141] The first network node 140 may comprise a memory 605. The memory 605 comprises one or more units to be used to store data on, such as data packets, indications, rate adaptation, messages, rate control information, events and applications to perform the methods disclosed herein when being executed, and similar. Furthermore, the first network node 140 may comprise a communication interface 606 such as comprising a transmitter, a receiver, a transceiver and / or one or more antennas.

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

[0143] Fig. 7 is a block diagram depicting the second network node 150, such as the CN node, the source radio network node, the CU, the CP node, the target radio network node, for handling communication in the communication network 1 according to embodiments herein.

[0144] The first network node 140 may comprise a distributed unit and the second network node 150 may comprise a central unit; the first network node 140 may comprise a target radio network node and the second network node 150 may comprise a source radio network node; or the firstnetwork node 140 may comprise a radio network node and the second network node 150 may comprise a core network node.

[0145] The second network node 150 may comprise processing circuitry 701, e.g. one or more processors, configured to perform the methods herein.

[0146] The second network node 150 and / or the processing circuitry 701 is configured to transmit to the first network node 140 the indication. The indication indicates the rate control of a QoS flow and / or the direction of communication for the rate control for the QoS flow. The rate control may be XR rate control, the direction may be UL, DL, or both. Thus, the second network node 150 and / or the processing circuitry 701 may be configured to transmit a value of an XR rate control parameter in a QoS message. The indication may be transmitted in a NGAP message, E1AP message, F1AP message, and / or an XnAP message. The indication may indicate one or more QoS flows that are subject to downlink and / or uplink rate control.

[0147] The second network node 150 and / or the processing circuitry 701 may be configured to receive the second indication from the first network node 140, and / or receive the second query indication from the UE 10, requesting to boost or increase the bit rate for the application. The second indication indicates congestion at the first network node 140.

[0148] The second network node 150 and / or the processing circuitry 701 may be configured to transmit to the first network node 140, the third indication indicating to boost or increase the bit rate of the application within the range of the supported bit rates.

[0149] The second network node 150 may comprise a memory 705. The memory 705 comprises one or more units to be used to store data on, such as data packets, rate control information, indications, messages, information, events and applications to perform the methods disclosed herein when being executed, and similar. Furthermore, the second network node 150 may comprise a communication interface 706 such as comprising a transmitter, a receiver, a transceiver and / or one or more antennas.

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

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

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

[0153] Moreover, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunications network 15102 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a network node in the telecommunications network 15102 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other network nodes to implement one or more functionalities of any network node in the telecommunications network 15102, including one or more access network nodes 15110 and / or core network nodes 15108, all being examples of the first and second network nodes herein. Examples of an ORAN network node include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O-CU-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). An ORAN network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an A1, F1, W1, E1, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN network node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualizationenvironment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an 0-2 interface defined by the O-RAN Alliance or comparable technologies.

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

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

[0156] Similarly, a core network node 108 may receive a particular message from a UE 15112 by receiving the message from an access network node 15110 that itself received the message from the UE 15112.

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

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

[0159] As a whole, the communication system 15100 of Figure 8 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system 15100 may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (Wi-Fi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (Wi-Max), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, Li-Fi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox. Moreover, the communication system 15100 may be configured to support multiple different standards, protocols, or other rule sets, with individual components supporting all of the relevant rule sets or with different components or sub-systems within the communication system 15100 supporting different standards, protocols, or rule sets.As one example, in certain embodiments, access network 15104 may contain some access network nodes 15110 that support 3GPP radio access technologies (RAT), such as LTE or NR, while other access network nodes 15110 support (or the same access network nodes 15110 additionally support) non-3GPP RATs, such as Wi-Fi or a proprietary RAT. As another example, telecommunications network 15102 may support multiple generations of related communication standards, e.g., 4G and 5G 3GPP communication standards, and, as a result, may include an access network 104 and / or a core network 106 that supports multiple different standard generations or may include multiple access networks 104 and / or multiple core networks 106 with individual networks 104, 106 supporting different standard generations.

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

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

[0162] In the example, the hub 15114 communicates with the access network 15104 to facilitate indirect communication between one or more UEs (e.g., UE 15112C and / or 15112D) and network nodes (e.g., network node 15110B). In some examples, the hub 15114 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 15114 may be a broadband router enabling access to the core network 15106 for the UEs. As another example, the hub 15114 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 15110, or by executable code, script, process, or other instructions in the hub 15114.

[0163] As another example, the hub 15114 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 15114 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 15114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node,which the hub 15114 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 15114 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.

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

[0165] Figure 9 is another example of a communication system 15200 according to some embodiments. As used herein, the communication system 15200 includes multiple access points (APs) 15210 (with four exemplary APs 15210A, 15210B, 15210C, and 15210D being depicted) and multiple wireless devices, referred to in the context of communication system 15200 as stations (STAs) 15212 (referred to individually as STA 15212A, STA 15212B, STA 15212C, STA 15212D, and STA 15212E). STA 15212A is served by AP 15210A in a first basic service set (BSS) 15220A. STA 15210B and STA 15210C are served by AP 15210B in a second BSS, BSS 15220B. STA 15212D is served by AP 15210C in a third BSS, BSS 15220C. STA 15212E is served by AP 15210D in a fourth BSS, BSS 15220D. Stations 15212 may be non-AP STAs and correspond to various kinds of wireless devices, for example, user terminals, such as mobile or stationary computing devices like smartphones, laptop computers, desktop computers, tablet computers, gaming devices, head-mounted displays (HMDs) for Augmented Reality (AR) or Virtual Reality (VR), or the like. Further, stations 15212 could, for example, correspond to other kinds of equipment like smart home devices, printers, multimedia devices, data storage devices, or the like.

[0166] Each of STAs 15212 may connect through a radio link to one of APs 15210. For example, depending on location or channel conditions experienced by a given STA 15212, the STA may select an appropriate AP and BSS for establishing the radio link. The radio link may be based on one or more orthogonal frequency-division multiplexing (OFDM) carriers from a frequency spectrum that is shared on the basis of a contention-based mechanism, e.g., an unlicensed orlicense exempt band like 2.4 GHz Industrial, Scientific, and Medical (ISM) band, the 5 GHz band, the 6 GHz band, or the 60 GHz band.

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

[0168] Figure 10 shows a wireless device 15300, which may be configured to operate in communication system 15100 of Figure 8 or in communication system 15200 of Figure 9. The wireless device 15300 may be alternatively referred to as a UE 15300, like a UE 15112 within the context of communication system 15100, or as a station (STA) 15300 or as a non-access-point station (non-AP STA) 15300, like a STA 15212 within the context of the communication system 15200, in accordance with respective embodiments. As used herein, a wireless device refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other wireless devices. Examples of a wireless device include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle, vehicle-mounted or vehicle embedded / integrated wireless device, and wireless terminal. Other examples include any type of UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-loT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[0169] A wireless device 15300 may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, wireless device 15300 may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, wireless device 15300 may represent a device that is intended for sale to, or operation by, a human user but whichmay not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, wireless device 15300 may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).

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

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

[0172] In the example, the input / output interface 15306 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices.

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

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

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

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

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

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

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

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

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

[0182] As yet another specific example, in an loT scenario, wireless device 15300 may represent a machine or other device that performs monitoring and / or measurements, and transmits the results of such monitoring and / or measurements to another wireless device and / or a network node.

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

[0184] In practice, any number of wireless devices 15300 may be used together with respect to a single use case. For example, a first wireless device 15300 might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second wireless device 15300 that is a remote controller operating the drone. When a user makes changes from the remote controller, the first wireless device 15300 may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone’s speed. The first and / or the second wireless device 15300 can also include more than one of the functionalities described above. For example, wireless device 15300 might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.

[0185] Figure 11 shows a network node 15400, being an example of the first and / or second network node, in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunications network. In accordance with respective embodiments, network node 15400 may be configured to operate in communication system 15100 of Figure 8, like network nodes 15108 or 15110, or in communication system 15200 of Figure 9, like an AP 15210 or a station 15212. Examples ofnetwork nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)), O-RAN nodes or components of an O-RAN node (e.g., 0-Rll, 0-Dll, O-CU).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0201] Hardware 15504 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices asdescribed herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 15506 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VM 15508A and VM 15508B (which may be collectively referred to as VMs 15508), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 15506 may present a virtual operating platform that appears like networking hardware to one or more of the VMs 15508.

[0202] The VMs 15508 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by virtualization layer 15506. Different embodiments of the instance of a virtual appliance 15502 may be implemented on one or more of VMs 15508, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

[0203] In the context of NFV, each of the VMs 15508 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 15508, and that part of hardware 15504 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more of the VMs 15508 on top of the hardware 15504 and corresponds to an application 15502.

[0204] Hardware 15504 may be implemented in a standalone network node with generic or specific components. Hardware 15504 may implement some functions via virtualization.

[0205] Alternatively, hardware 15504 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 15510, which, among others, oversees lifecycle management of applications 15502. In some embodiments, hardware 15504 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 15512 which may alternatively be used for communication between hardware nodes and radio units.

[0206] Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed toperform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.

[0207] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer-readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally.

[0208] The embodiments herein are not limited to the above described preferred embodiments. Various alternatives, modifications and equivalents may be used.

[0209] It will be appreciated that the foregoing description and the accompanying drawings represent non-limiting examples of the methods and apparatus taught herein. As such, the apparatus and techniques taught herein are not limited by the foregoing description and accompanying drawings. Instead, the embodiments herein are limited only by the following claims and their legal equivalents.

[0210] Embodiments:

[0211] Embodiment A1.

[0212] A method performed by a first network node (140) for handling communication in a communication network, the method comprisingreceiving (401) from a second network node (150), an indication, wherein the indication indicates a rate control of a QoS flow and / or DRB; and / or a direction of communication for the rate control.

[0213] Embodiment A2:

[0214] The method according to embodiment A1, wherein the indication is received in a NGAP message, E1AP message, F1AP message, and / or an XnAP message.

[0215] Embodiment B1.

[0216] A method performed by a second network node (150) for handling communication in a communication network, the method comprising

[0217] - transmitting (501) to a first network node (140), an indication, wherein the indication indicates a rate control of a QoS flow and / or DRB; and / or a direction of communication for the rate control.

[0218] Embodiment B2:

[0219] The method according to embodiment B1, wherein the indication is transmitted in a NGAP message, E1AP message, F1AP message, and / or an XnAP message.

[0220] Embodiment C1.

[0221] A first network node (140) for handling communication in a communication network, wherein the first network node is configured to:

[0222] receive from a second network node (150) an indication indicating a rate control of a QoS flow and / or DRB; and / or a direction of communication for the rate control.

[0223] Embodiment C2.

[0224] The first network node according to embodiment C1 , wherein the first network node is configured to perform the method according to embodiment A2.

[0225] Embodiment D1.

[0226] A second network node (150) for handling communication in a communication network, wherein the second network node is configured to:

[0227] - transmit to a first network node (140), an indication, wherein the indication indicates a rate control of a QoS flow and / or DRB; and / or a direction of communication for the rate control.

[0228] Embodiment D2.The second network node according to embodiment D1, wherein the second network node is configured to perform the method according to embodiment B2.

[0229] Embodiment E1.

[0230] A computer program product comprising instructions, which, when executed on at least one processor, cause the at least one processor to carry out the method according to any of the embodiments A1-A2 or B1-B2, as performed by the second network node and the first network node, respectively.

[0231] Embodiment F1.

[0232] A computer-readable storage medium, having stored thereon a computer program product comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out the method according to any of the embodiments A1-A2 or B1-B2, as performed by the second network node and the first network node, respectively.

Claims

CLAIMS1. A method performed by a first network node (140) for handling communication in a communication network, the method comprising- receiving (401) from a second network node (150), an indication, wherein the indication indicates a rate control of a quality of service, QoS, flow and / or a direction of communication for the rate control for the QoS flow.

2. The method according to claim 1, wherein the indication is received in a NGAP message, an E1AP message, an F1AP message, and / or an XnAP message.

3. The method according to any of the claims 1-2, wherein the indication indicates one or more QoS flows that are subject to downlink and / or uplink rate control.

4. The method according to any of the claims 1-3, further comprising- handling (402) a session based on the indication comprising determining which one or more QoS flows that can be rate controlled, and / or for which direction based on the indication.

5. The method according to any of the claims 1-4, further comprising- transmitting (403) a second indication to the second network node (150), and / or a second query indication from a user equipment, UE, (10), requesting to increase a bit rate for an application, and wherein the second indication indicates congestion at the first network node (140).

6. The method according to any of the claims 1-5, further comprising- receiving (404) from the second network node (150), a third indication indicating to increase a bit rate of an application within a range of supported bit rates; and - handling (405) a session based on the third indication.

7. The method according to any of the claims 1-6, wherein the first network node (140) comprises a distributed unit and the second network node (150) comprises a central unit, the first network node (140) comprises a target radio network node and the second network node (150) comprises a source radio network node, or the first network node (140) comprises a radio network node and the second network node (150) comprises a core network node.

8. A method performed by a second network node (150) for handling communication in a communication network, the method comprisingtransmitting (501) to a first network node (140), an indication, wherein the indication indicates a rate control of a quality of service, QoS, flow and / or a direction of communication for the rate control for the QoS flow.

9. The method according to claim 8, wherein the indication is transmitted in a NGAP message, E1AP message, F1AP message, and / or an XnAP message.

10. The method according to any of the claims 8-9, wherein the indication indicates one or more QoS flows that are subject to downlink and / or uplink rate control.

11. The method according to any of the claims 8-10, further comprising- receiving (502) a second indication from the first network node (140), and / or a second query indication from a user equipment, UE, (10), requesting to increase a bit rate for an application, and wherein the second indication indicates congestion at the first network node (140).

12. The method according to any of the claims 8-11 , further comprising- transmitting (503) to the first network node (140), a third indication indicating to increase a bit rate of an application within a range of supported bit rates.

13. The method according to any of the claims 8-12, wherein the first network node (140) comprises a distributed unit and the second network node (150) comprises a central unit, the first network node (140) comprises a target radio network node and the second network node (150) comprises a source radio network node, or the first network node (140) comprises a radio network node and the second network node (150) comprises a core network node.

14. A first network node (140) for handling communication in a communication network, wherein the first network node (140) is configured toreceive from a second network node (150), an indication, wherein the indication indicates a rate control of a quality of service, QoS, flow and / or a direction of communication for the rate control for the QoS flow.

15. The first network node (140) according to claim 14, wherein the indication is received in a NGAP message, E1AP message, F1AP message, and / or an XnAP message.

16. The first network node (140) according to any of the claims 14-15, wherein the indication indicates one or more QoS flows that are subject to downlink and / or uplink rate control.

17. The first network node (140) according to any of the claims 14-16, wherein the first network node (140) is configured to:handle a session based on the indication by determining which one or more QoS flows that can be rate controlled, and / or for which direction based on the indication.

18. The first network node (140) according to any of the claims 14-17, wherein the first network node (140) is configured to:transmit a second indication to the second network node (150), and / or a second query indication from a user equipment, UE, (10), requesting to increase a bit rate for an application, and wherein the second indication indicates congestion at the first network node (140).

19. The first network node (140) according to any of the claims 14-18, wherein the first network node (140) is configured to:receive from the second network node (150), a third indication indicating to increase a bit rate of an application within a range of supported bit rates; and handle a session based on the third indication.

20. The first network node (140) according to any of the claims 14-19, wherein the first network node (140) comprises a distributed unit and the second network node (150) comprises a central unit, the first network node (140) comprises a target radio network node and the second network node (150) comprises a source radio network node, or the first network node (140) comprises a radio network node and the second network node (150) comprises a core network node.

21. A second network node (150) for handling communication in a communication network, wherein the second network node (150) is configured totransmit to a first network node (140), an indication, wherein the indication indicates a rate control of a quality of service, QoS, flow and / or a direction of communication for the rate control for the QoS flow.

22. The second network node (150) according to claim 21, wherein the indication is transmitted in a NGAP message, E1AP message, F1AP message, and / or an XnAP message.

23. The second network node (150) according to any of the claims 21-22, wherein the indication indicates one or more QoS flows that are subject to downlink and / or uplink rate control.

24. The second network node (150) according to any of the claims 21-23, wherein the second network node (150) is configured toreceive a second indication from the first network node (140), and / or a second query indication from a user equipment, UE, (10), requesting to increase a bit rate for an application, and wherein the second indication indicates congestion at the first network node (140).

25. The second network node (150) according to any of the claims 21-24, wherein the second network node (150) is configured totransmit to the first network node (140), a third indication indicating to increase a bit rate of an application within a range of supported bit rates.

26. The second network node (150) according to any of the claims 21-25, wherein the first network node (140) comprises a distributed unit and the second network node (150) comprises a central unit, the first network node (140) comprises a target radio network node and the second network node comprises a source radio network node, or the first network node (140) comprises a radio network node and the second network node (150) comprises a core network node.

27. A computer program product comprising instructions, which, when executed on at least one processor, cause the at least one processor to carry out the method according to any of the claims 1-13, as performed by the first network node (140) and the second network node (150), respectively.

28. A computer-readable storage medium, having stored thereon a computer program product comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out the method according to any of the claims 1-13, as performed by the first network node (140) and the second network node (150), respectively.

Images