Signaling supported available bitrate information in next generation-random access network during handover and dual connectivity procedures

Abstract

A first network node in a communications network can receive (610) configuration information from a second network node including an indication of a threshold value and requesting that the first network node perform threshold-based reporting of an available bit rate for a quality of service, QoS flow using the threshold value The first network node can further transmit (630) an indication to the second network node of whether the first network node supports threshold-based reporting of the available bit rate for the QoS flow based on the threshold value.

Description

SIGNALING SUPPORTED AVAILABLE BITRATE INFORMATION IN NEXT GENERATION-RANDOM ACCESS NETWORK DURING HANDOVER AND DUAL CONNECTIVITY PROCEDURESTECHNICAL FIELD

[0001] The present disclosure is related to wireless communication systems and more particularly to signaling supported available bitrate information in next generation radio access network (NG-RAN) during handover and dual connectivity procedures.BACKGROUND

[0002] FIG. 1 illustrates an example of a new radio (NR) network (e.g., a 5th Generation (5G) network) including a 5G core (5GC) network 130, network nodes 120a-b (e.g., 5G base station (gNB)), multiple communication devices 110 (also referred to as user equipment (UE)).

[0003] FIG. 2 illustrates an example of current NG-RAN architecture. The NG-RAN architecture can be further described as follows. The NG-RAN includes a set of 5G base stations (referred to herein as gNBs) connected to the 5GC through the NG network. A gNB can support frequency division duplex (FDD) mode, time division duplex (TDD) mode or dual mode operation. gNBs can be interconnected through the Xn interface. A gNB can include a gNB-central unit (CU) and gNB-distributed units (DUs). A gNB-CU and a gNB-DU are connected via a Fl logical interface. One gNB-DU is connected to only one gNB-CU. For resiliency, a gNB-DU may be connected to multiple gNB-CU by appropriate implementation. NG, Xn, and Fl are logical interfaces. The NG-RAN is layered into a Radio Network Layer (RNL) and a Transport Network Layer (TNL). The NG-RAN architecture (e.g., the NG-RAN logical nodes and interfaces between them) is defined as part of the RNL. For each NG-RAN interface (e.g., NG, Xn, and Fl) the related TNL protocol and the functionality are specified. The TNL provides services for user plane transport and signaling transport. NG, Xn and Fl are logical interfaces.

[0004] For NG-RAN, the NG and Xn-C interfaces for a gNB consisting of a gNB-CU and gNB-DUs, terminate in the gNB-CU. For EN-DC, the Sl-U and X2-C interfaces for a gNB including a gNB-CU and gNB-DUs, terminate in the gNB-CU. The gNB-CU and connected gNB-DUs are only visible to other gNBs and the 5GC as a gNB.

[0005] In some examples of network sharing with multiple cell ID broadcast, each Cell Identity associated with a subset of PLMNs corresponds to a gNB-DU and the gNB-CU it is connected to, for example, the corresponding gNB-DUs share the same physical layer cell resources. For resiliency, a gNB-DU may be connected to multiple gNB-CUs by appropriate implementation.

[0006] For NG-RAN, the NG and Xn-C interfaces for a gNB consisting of a gNB-CU and gNB-DUs, terminate in the gNB-CU. For EN-DC, the Sl-U and X2-C interfaces for a gNB consisting of a gNB-CU and gNB-DUs, terminate in the gNB-CU. The gNB-CU and connected gNB-DUs are only visible to other gNBs and the 5GC as a gNB.

[0007] The node hosting user plane part of NR PDCP (e.g., gNB-CU, gNB-CU-UP, and for EN-DC, MeNB or SgNB depending on the bearer split) shall perform user inactivity monitoring and further informs its inactivity or (re)activation to the node having C-plane connection towards the core network (e.g., over El, X2). The node hosting NR RLC (e.g. gNB-DU) may perform user inactivity monitoring and further inform its inactivity or (re)activation to the node hosting control plane, e.g. gNB-CU or gNB-CU-CP.

[0008] UL PDCP configuration (i.e. how the UE uses the UL at the assisting node) is indicated via X2-C (for EN-DC), Xn-C (for NG-RAN) and Fl-C. Radio Link Outage / Resume for DL and / or UL is indicated via X2-U (for EN-DC), Xn-U (for NG-RAN) and Fl-U.

[0009] The NG-RAN is layered into a RNL and a TNL. The NG-RAN architecture (e.g., the NG-RAN logical nodes and interfaces between them) is defined as part of the RNL. For each NG-RAN interface (NG, Xn, Fl) the related TNL protocol and the functionality are specified. The TNL provides services for user plane transport, signalling transport. In NG-Flex configuration, each NG-RAN node is connected to all AMFs of AMF Sets within an AMF Region supporting at least one slice also supported by the NG-RAN node. The AMF Set and the AMF Region are defined in 3GPP. If security protection for control plane and user plane data on TNL of NG-RAN interfaces has to be supported, NDS / IP 3GPP TS 33.501 shall be applied.

[0010] The Xn-C interface connects two gNB-CUs and Fl interface between gNB-CU and gNB-DU. FIG. 3 illustrates an example of a user plane interface (NG-U) between a 5GC (here a user plane function (UPF)) and a NG-RAN (here either a master node (MN) or a secondary node (SN)). FIG. 4 illustrates an example of a control plane interface (NG-C) between a 5GC (here an access management and mobility function (AMF)) and a NG-RAN and 5G Core.

[0011] The overall architecture for separation of gNB-CU-CP and gNB-CU-UP is depicted in FIG. 5. A gNB-CU hosts the RRC and the control plane part of the PDCP; gNB-DU hosts RLC, MAC and the physical layer. El interface connects between gNB-CU-CP and gNB-CU-UP.

[0012] A gNB may consist of a gNB-CU-CP, multiple gNB-CU-UPs and multiple gNB-DUs. The gNB-CU-CP is connected to the gNB-DU through the Fl-C interface. The gNB-CU-UP is connected to the gNB-DU through the Fl-U interface. The gNB-CU-UP is connected to the gNB-CU-CP through the El interface. One gNB-DU is connected to only one gNB-CU-CP. One gNB-CU-UP is connected to only one gNB-CU-CP. For resiliency, a gNB-DU and / or agNB-CU-UP may be connected to multiple gNB-CU-CPs by appropriate implementation. One gNB-DU can be connected to multiple gNB-CU-UPs under the control of the same gNB-CU-CP. One gNB-CU-UP can be connected to multiple DUs under the control of the same gNB-CU-CP.

[0013] The connectivity between a gNB-CU-UP and a gNB-DU is established by the gNB- CU-CP using Bearer Context Management functions. The gNB-CU-CP selects the appropriate gNB-CU-UP(s) for the requested services for the UE. In case of multiple CU-UPs they belong to same security domain. Data forwarding between gNB-CU-UPs during intra-gNB-CU-CP handover within a gNB may be supported by Xn-U.

[0014] For a GBR QoS Flow, based on the PCC rule from PCF, the SMF requests the NG-RAN to report the UL and / or DL available bitrate by indicating thresholds. The NG-RAN reports the UL and / or DL available bitrate information to the PSA UPF via the GTP-U header of UL packets when the measured bitrate matches the threshold.SUMMARY

[0015] According to some embodiments, a method of operating a first network node in a communications network is provided. The method includes receiving configuration information from a second network node including an indication of a threshold value and requesting that the first network node perform threshold-based reporting of an available bit rate for a quality of service, QoS flow using the threshold value. The method further includes transmitting an indication to the second network node of whether the first network node supports thresholdbased reporting of the available bit rate for the QoS flow based on the threshold value.

[0016] According to other embodiments, a method of operating a second network node in a communications network is provided. The method includes transmitting configuration information to a first network node including an indication of a threshold value and requesting that the first network node perform threshold-based reporting of an available bit rate for a quality of service, QoS flow using the threshold value. The method further includes, responsive to transmitting the configuration information, receiving an indication from the first network node of whether the first network node supports the threshold-based reporting of the available bit rate for the QoS flow based on the threshold value.

[0017] According to other embodiments, a communication device, a network node, a computer program, computer program product, non-transitory computer readable medium, host, or system is provided to perform one of the above methods.

[0018] Certain embodiments may provide one or more of the following technical advantages. Some embodiments herein provide support of available bit rate reporting in non-homogeneous network deployment, split architecture, and in dual connectivity procedures.BRIEF DESCRIPTION OF THE DRAWINGS

[0019] The accompanying drawings, which are included to provide a further understanding of the disclosure and are incorporated in and constitute a part of this application, illustrate certain non-limiting embodiments of inventive concepts. In the drawings:

[0020] FIG. 1 is a schematic diagram illustrating an example of a 5thgeneration (“5G”) network;

[0021] FIG. 2 is a block diagram illustrating an example of a NG-RAN;

[0022] FIG. 3 is a schematic diagram illustrating an example of a user plane interface between NG-RAN and the 5GC;

[0023] FIG. 4 is a schematic diagram illustrating an example of a control plane interface between NG-RAN and the 5GC;

[0024] FIG. 5 is a block diagram illustrating an example of a gNB with a split architecture;

[0025] FIG. 6 is a flow chart illustrating an example of operations performed by a first network node in accordance with some embodiments;

[0026] FIG. 7 is a flow chart illustrating an example of operations performed by a second network node in accordance with some embodiments;

[0027] FIG. 8 is a block diagram of a communication system in accordance with some embodiments;

[0028] FIG. 9 is a block diagram of a user equipment in accordance with some embodiments; and

[0029] FIG. 10 is a block diagram of a network node in accordance with some embodiments.DETAILED DESCRIPTION

[0030] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art, in which examples of embodiments of inventive concepts are shown. Inventive concepts may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of present inventive concepts to those skilled in theart. It should also be noted that these embodiments are not mutually exclusive. Components from one embodiment may be tacitly assumed to be present / used in another embodiment.

[0031] There currently exist certain challenge(s). In the current description of available bitrate reporting framework, when the NG-RAN is receiving the thresholds from the SMF, the NG-RAN is expected to perform bit rate reporting of the available Bitrate for a GBR QoS Flow when the available value crosses one of the indicated thresholds. However, if the NG-RAN does not support such threshold-based QoS Monitoring, or the threshold values themselves, the CN will not receive any available bitrate and failure of the PDU Session will happen.

[0032] Since bitrate is measured at the gNB-DU in split RAN architecture, if the gNB-CU does not know of gNB-DU capability, the gNB-CU may waste resources configuring the UP for the reporting, but receives no feedback from the gNB-DU, because the gNB-DU does not support threshold based reporting (or the threshold values).

[0033] Furthermore, in case of handover or dual connectivity procedure during a thresholdbased monitoring and reporting, when the QoS monitoring configuration is provided to the target node or secondary node, the source node or master node, respectively, does not know which thresholds or number of thresholds are supported by the other node or based on which value the available bitrate reporting can happen at the other node.

[0034] Various embodiments herein address the above challenges. In some embodiments, a handshake between CN and NG-RAN is provided in order to receive NG-RAN capability for supporting threshold based reporting of available bitrate for a QoS flow in a specific direction (UL / DL). In additional or alternative embodiments, the handshake is provided in order to agree on the values that can be supported by the NG-RAN that can actually be supported for the reporting in the respective direction(s). In additional or alternative embodiments, the handshake is provided in order to split gNB architecture, the thresholds are signaled between gNB-CU and gNB-DU, since the bitrate is measured at the gNB-DU. The gNB-CU needs also to know the threshold-based reporting capability of the gNB-DU. In additional or alternative embodiments, the handshake is provided to know that support of target gNB for bitrate reporting to continue the reporting to UPF. This handshake can happen during NG, Fl, El and Xn procedures.

[0035] Various embodiments herein describe the addition of new parameters in NGAP signaling. In the NGAP signaling, for example., PDU Resource Setup procedure or NG- based Handover procedure, when the NG-RAN receives the QoS configuration with the thresholds for available bitrate reporting, if the NG-RAN supports such threshold-based reporting, it sends a new support indication to the CN. The NG-RAN further indicates the values of the thresholds that can be supported for the monitoring.

[0036] In the XnAP signaling, for example, during a Xn based handover or Dual connectivity, when the target node receives the QoS configuration with the thresholds for available bitrate reporting, if the target NG-RAN supports such threshold based reporting, it sends a new support indication to the source NG-RAN, indicating the threshold supported by the node such as minimum value. In the split bearer scenario, the gNB-CU maybe need to aggregate the report from the different gNB-DU; gNB-CU may further split the thresholds information per gNB-DU involved, based on the resource information.

[0037] In the Fl AP signaling, for example, UE context management procedure, when the gNB-DU receives the QoS configuration with the thresholds for available bitrate reporting from the gNB-CU, if the gNB-DU supports such threshold-based reporting, it sends a new support indication to the gNB-CU. The gNB-DU further indicates the values of the thresholds that can be supported for the monitoring.

[0038] In case of El CU-CP and CU-CP split, the gNB-CU-UP receives the thresholds as part of the QoS parameters in the bearer context management procedures. The gNB-CU-UP receives an indication from the gNB-CU-CP to report the bitrate to the UPF.

[0039] In some embodiments, the reporting can be carried over NG-RAN user plane and the NG-U user plane. The impact can be on the GTP-U extension container.

[0040] In some embodiments, a first network node (NG-RAN, gNB-DU), when it receives from a second network node (CN, second NG-RAN, gNB-CU) the QoS configuration (for UL and / or DL) with the thresholds for available bitrate reporting, signals to the second network node an indication that it supports reporting the measured bitrate according to the signaled thresholds. In some examples, such indication can be called threshold-reporting support indication IE. In additional or alternative examples, the first network node provides the default bitrate information supported at initial setup of the PDU session, which acts as capability support indication.

[0041] In additional or alternative embodiments, the first network node indicates, in addition to the threshold-reporting supporting indication IE, the supported thresholds values for available bit rate reporting to the second network node for a QoS Flow, indicating also the minimum supported threshold according to which it can measure the available bitrate.

[0042] In additional or alternative embodiments, the indication can be over NG signaling during a PDU Session management procedure or NG-based Handover procedure.

[0043] In additional or alternative embodiments, the indication can be over Xn signaling during a Xn-based handover, or dual connectivity procedures.

[0044] In additional or alternative embodiments, the indication can be over Fl signaling during a Fl UE context management procedure.

[0045] In additional or alternative embodiments, at the time of handover, the target node receives from the source node the last reported available bitrate, to be reported from target node to CN.

[0046] In additional or alternative embodiments, when the CN receives the last reported bit rate from the target, the CN also understands this is a capability indication of the target node to support available bitrate reporting.

[0047] In additional or alternative embodiments, after a successful Xn-based handover, the target NG-RAN indicates to the CN the threshold-reporting supporting indication IE and the supported bit rate thresholds reporting as new indications in the N2 PATH SWITCH REQUEST message for the indicated QoS flow, in the specific direction (for UL and / or DL).

[0048] In additional or alternative embodiments, the 5GCN signals to the new RAN node in the PATH SWITCH REQUEST ACKNOWLEDGE message, the thresholds value parameters to use for the accepted QoS flows in specific direction (UL / DL).

[0049] In additional or alternative embodiments, the threshold-reporting supporting indication is signaled by the target gNB following Xn HO from a non-supporting gNB to 5GCN, in, for example, the PATH SWITCH REQUEST procedure. Upon reception of the flag, the 5GCN considers the QoS flow that are accepted are subject to threshold-based monitoring and that the handover was done from a non threshold based supporting source gNB.

[0050] In additional or alternative embodiments, if the CN decides to modify the thresholds for available bitrate reporting, it sends new value in the NG-RAN PDU Session Modification procedure.

[0051] In additional or alternative embodiments, the gNB-DU receives an indication to modify the thresholds for available bitrate reporting in the UE CONTEXT MODIFICATION REQUEST message over F1AP from the gNB-CU.

[0052] In additional or alternative embodiments, in the split bearer scenario, the gNB-CU maybe need to aggregate the report from the different gNB-DU; gNB-CU may further split the thresholds information per gNB-DU involved, based on the resource information.

[0053] In additional or alternative embodiments, the gNB-CU-UP receives the thresholds indicator for available bitrate reporting from the gNB-CU-CP as new information element in the QoS flow information signaling in the bearer context setup request and bearer context modification request messages.

[0054] In additional or alternative embodiments, the gNB-CU-UP receives indication of the bitrate reporting from the gNB-DU via Fl-U signaling.

[0055] In additional or alternative embodiments, a network node, (e.g., RAN, gNB-DU, gNB-CU) receives an indication from a second network node (CN, gNB-CU), to stop thereporting of available bitrate. In some examples, this is achieved via a stop indication in the control plane message signaled over aNGAP, F1P, or XnAP message.

[0056] Operations of a network node 1000 (implemented using the structure of FIG. 10) will now be discussed with reference to the flow charts of FIGS. 6-7 according to some embodiments of inventive concepts. For example, modules may be stored in memory 1006 of FIG. 10, and these modules may provide instructions so that when the instructions of a module are executed by respective network node processing circuitry 1002, network node 1000 performs respective operations of the flow charts.

[0057] FIG. 6 illustrates an example of operations performed by a first network node.

[0058] At block 610, processing circuitry 1002 receives, via communication interface 1006, configuration information including an indication of a threshold value and requesting that the first network node perform threshold-based reporting of an available bit rate.

[0059] At block 620, processing circuitry 1002 determines whether the first network node supports the threshold-based reporting of the available bit rate based on the threshold value.

[0060] At block 630, processing circuitry 1002 transmits, via communication interface 1006, an indication of whether the first network node supports the threshold-based reporting of the available bit rate. In some embodiments, determining whether the first network node supports the threshold-based reporting includes determining that the first network node supports the threshold-based reporting of the available bit rate for the QoS flow based on the threshold value. In additional or alternative embodiments, transmitting the indication to the second network node includes transmitting an indication to the second network node indicating that the first network node supports the threshold-based reporting of the available bit rate for the QoS flow based on the threshold value.

[0061] In some examples, transmitting the indication that the first network node supports the threshold-based reporting includes transmitting a threshold-reporting supporting indication information element, IE, to the second network node.

[0062] In additional or alternative examples, transmitting the indication that the first network node supports the threshold-based reporting includes transmitting default bitrate information supported at initial setup of a data session associated with the QoS flow.

[0063] In additional or alternative embodiments, receiving the configuration information includes receiving an indication of a plurality of threshold values including the threshold value and a request that the first network node perform threshold-based reporting of the available bit rate for the QoS flow using one or more threshold values in the plurality of threshold values. Determining whether the first network node supports the threshold-based reporting includes determining that the first network node supports the threshold-based reporting of the availablebit rate for the QoS flow based on the one or more threshold values of the plurality of threshold values. Transmitting the indication to the second network node includes transmitting an indication to the second network node indicating the one or more threshold values supported by the first network for the threshold-based reporting of the available bit rate for the QoS flow.

[0064] In some examples, transmitting the indication to the second network node includes transmitting an indication to the second network node indicating a minimum supported threshold value supported by the first network node for threshold-based reporting of the available bit rate for the QoS flow.

[0065] In additional or alternative embodiments, the first network node includes a radio access network, RAN, node, and the second network node includes a core network, CN, node. In some examples, transmitting the indication includes transmitting the indication to the CN node via next generation, NG, signaling during a packet data unit, PDU, session management procedure or NG-based handover procedure. In additional or alternative examples, the CN node includes an access management and mobility function, AMF, and a user plane function, UPF. Receiving the configuration information includes receiving the configuration information from the AMF. Transmitting the indication includes transmitting the indication to the AMF.

[0066] In additional or alternative embodiments, the first network node includes a first radio access network, RAN, node, and the second network node comprises a second RAN node. In some examples, transmitting the indication includes transmitting the indication to the second RAN node via Xn signaling during a Xn-based handover of the second RAN node to the first RAN node or dual connectivity procedure.

[0067] In additional or alternative embodiments, the first network node includes a distributed unit, DU, of a radio access network, RAN, node, and the second network node includes a central unit, CU, of the RAN node. In some examples, transmitting the indication includes transmitting the indication to CU via Fl signaling during a Fl UE context management procedure.

[0068] In additional or alternative embodiments, the CU comprises a CU-control plane, CU-CP, and a CU-user plane, CU-UP. Receiving the configuration information includes receiving the configuration information from the CU-CP. Transmitting the indication includes transmitting the indication to the CU-CP.

[0069] At block 640, processing circuitry 1002 receives, via communication interface 1006, an indication of a last reported available bit rate by the second network node. At block 650, processing circuitry 1002 transmits, via communication interface 1006, an indication of the last reported available bit rate to a CN node. In some embodiments, the first network node includes a first radio access network, RAN, node, and the second network node comprises a second RANnode. In some examples, the last reported available bit rate of the second RAN node is received as part of a handover from the second RAN node to the first RAN node.

[0070] At block 660, processing circuitry 1002 transmits, via communication interface 1006, an indication of the available bit rate to the second network node. In some embodiments, the indication of the available bit rate is transmitted in response to meeting the threshold value.

[0071] In additional or alternative embodiments, the first network node includes a radio access network, RAN, node, and the second network node includes a core network, CN, node. In some examples, transmitting the indication of the available bit rate includes transmitting the indication of the available bit rate to the UPF.

[0072] In additional or alternative embodiments, the CU comprises a CU-control plane, CU-CP, and a CU-user plane, CU-UP. In some examples, the available bit rate is reported to the CU-UP.

[0073] At block 670, processing circuitry 1002 receives, via communication interface 1006, an indication to modify and / or stop the threshold-based reporting of the available bit rate.

[0074] FIG. 7 illustrates an example of operations performed by a second network node.

[0075] At block 710, processing circuitry 1002 transmits, via communication interface 1006, configuration information including an indication of a threshold value and requesting that a first network node perform threshold-based reporting.

[0076] At block 720, processing circuitry 1002 receives, via communication interface 1006, an indication from the first network node of whether the first network node supports the threshold-based reporting. In some embodiments, receiving the indication from the first network node includes receiving an indication from the first network node indicating that the first network node supports the threshold-based reporting of the available bit rate for the QoS flow based on the threshold value. In some examples, receiving the indication that the first network node supports the threshold-based reporting includes receiving a threshold-reporting supporting indication information element, IE, from the first network node. In additional or alternative examples, receiving the indication that the first network node supports the threshold-based reporting includes receiving default bitrate information supported at initial setup of a data session associated with the QoS flow.

[0077] In additional or alternative embodiments, transmitting the configuration information includes transmitting an indication of a plurality of threshold values including the threshold value and a request that the first network node perform threshold-based reporting of the available bit rate for the QoS flow using one or more threshold values in the plurality of threshold values. Receiving the indication from the first network node includes receiving an indication from the first network node indicating the one or more threshold values supported bythe first network for the threshold-based reporting of the available bit rate for the QoS flow. In some examples, receiving the indication from the first network node includes receiving an indication from the first network node indicating a minimum supported threshold value supported by the first network node for threshold-based reporting of the available bit rate for the QoS flow.

[0078] In additional or alternative embodiments, the first network node includes a radio access network, RAN, node, and the second network node includes a core network, CN, node. In some examples, receiving the indication includes receiving the indication from the RAN node via next generation, NG, signaling during a packet data unit, PDU, session management procedure or NG-based handover procedure. In additional or alternative examples, the CN node includes an access management and mobility function, AMF, and a user plane function, UPF. Transmitting the configuration information includes transmitting, by the AMF, the configuration information to the RAN node. Receiving the indication includes receiving, by the AMF, the indication from the RAN node.

[0079] In additional or alternative embodiments, the first network node includes a first radio access network, RAN, node, and the second network node includes a second RAN node. In some examples, receiving the indication includes receiving the indication from the first RAN node via Xn signaling during a Xn-based handover of the second RAN node to the first RAN node or dual connectivity procedure.

[0080] In additional or alternative embodiments, the first network node includes a distributed unit, DU, of a radio access network, RAN, node and the second network node includes a central unit, CU, of the RAN node. In some examples, receiving the indication includes receiving the indication from the DU via Fl signaling during a Fl UE context management procedure. In additional or alternative examples, the CU includes a CU-control plane, CU-CP, and a CU-user plane, CU-UP. Transmitting the configuration information includes transmitting, by the CU-CP, the configuration information to the DU. Receiving the indication includes receiving, by the CU-CP, the indication from the DU.

[0081] At block 740, processing circuitry 1002 transmits, via communication interface 1006, an indication of a last reported available bit rate. In some embodiments, the first network node includes a first radio access network, RAN, node, and the second network node includes a second RAN node. In some examples, transmitting the indication of the last reported available bit rate includes transmitting the indication of the last reported available bit rate as part of a handover from the second RAN node to the first RAN node.

[0082] At block 760, processing circuitry 1002 receives, via communication interface 1006, an indication of the available bit rate. In some embodiments, the first network node includes aradio access network, RAN, node, and the second network node includes a core network, CN, node. The indication of the available bit rate can be received by the UPF.

[0083] In additional or alternative embodiments, the first network node includes a distributed unit, DU, of a radio access network, RAN, node and the second network node includes a central unit, CU, of the RAN node. In some examples, the indication of the available bit rate can be received by the CU-UP.

[0084] At block 770, processing circuitry 1002 transmits, via communication interface 1006, an indication to modify and / or stop the threshold-based reporting of the available bit rate.

[0085] Various operations from the flow charts of FIGS. 6-7 may be optional with respect to some embodiments of network nodes and related methods.

[0086] FIG. 8 shows an example of a communication system 800 in accordance with some embodiments.

[0087] In the example, the communication system 800 includes a telecommunications network 802 that includes an access network 804, such as a radio access network (RAN), and a core network 806, which includes one or more core network nodes 808. The access network 804 includes one or more access network nodes or base stations of various types, access network nodes 810A and 810B are depicted (which may be collectively referred to as network nodes 810), or any other similar 3rdGeneration Partnership Project (3GPP) access nodes or non-3GPP access points (APs). Some embodiments of the access network 804 may include more than one access network technology. The network nodes 810 of access network 804 facilitate direct or indirect connection of wireless devices, also referred to as user equipments (UEs), such as by connecting UEs 812A, 812B, 812C, and 812D (one or more of which may be generally referred to as UEs 812) to the core network 806 over one or more wireless connections.

[0088] 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 802 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a network node in the telecommunications network 802 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 802, including one or more access network nodes 810 and / or core network nodes 808.

[0089] 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 Al, Fl, Wl, El, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN network node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an 0-2 interface defined by the 0-RAN Alliance or comparable technologies.

[0090] The network nodes 810 facilitate direct or indirect connection of one or more UEs 812 to the core network 806 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 800 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 800 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0091] The UEs 812 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 810 and other communication devices. Similarly, the network nodes 808, 810 are arranged, capable, configured, and / or operable to communicate directly or indirectly (e.g., via other devices of telecommunications network 802) with the UEs 812 and / or with other network nodes or equipment in the telecommunications network 802 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 802. More specifically, UEs 812 may send messages, data, and / or other signals to network nodes 808, 810 or other elements of the telecommunications network 802 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 808, 810 may send messages, data, and other signals to UEs 8122, other network nodes 808, 810, and other devices in telecommunications network 802 directly or indirectly. As one specific example, a core network node 108 may transmit a particular message to a UE 812 by transmitting the message to an access network node 810 that will then transmit the message to the intended UE 812.Similarly, a core network node 108 may receive a particular message from a UE 812 by receiving the message from an access network node 810 that itself received the message from the UE 812.

[0092] In the depicted example, the core network 806 connects elements of the access network 804 (e.g., one or more of the network nodes 810) to one or more host computing systems, such as host 816. 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 806 includes one or more core network nodes (e.g., core network node 808) of various types, one or more of which may be generally referred to as network nodes 808. Network nodes 808 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 808. Example core network nodes provide functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[0093] The host 816 may be under the ownership or control of a service provider other than an operator or provider of the access network 804 and / or the telecommunications network 802. The host 816 may be operated by the service provider or on behalf of the service provider. The host 816 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.

[0094] As a whole, the communication system 800 of FIG. 8 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system 800 may beconfigured 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 800 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 800 supporting different standards, protocols, or rule sets.

[0095] As one example, in certain embodiments, access network 804 may contain some access network nodes 810 that support 3GPP radio access technologies (RAT), such as LTE or NR, while other access network nodes 810 support (or the same access network nodes 810 additionally support) non-3GPP RATs, such as Wi-Fi or a proprietary RAT. As another example, telecommunications network 802 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.

[0096] Telecommunications network 802 may support network slicing to provide different logical networks to different devices that are connected to the telecommunications network 802. For example, the telecommunications network 802 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.

[0097] In some examples, one or more of the UEs 812 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 804 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 804.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).

[0098] In the example, the hub 814 communicates with the access network 804 to facilitate indirect communication between one or more UEs (e.g., UE 812C and / or 812D) and network nodes (e.g., network node 81 OB). In some examples, the hub 814 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 814 may be a broadband router enabling access to the core network 806 for the UEs. As another example, the hub 814 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 810, or by executable code, script, process, or other instructions in the hub 814.

[0099] As another example, the hub 814 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 814 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 814 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 814 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 814 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.

[0100] The hub 814 may have a constant / persistent or intermittent connection to the network node 810B. The hub 814 may also allow for a different communication scheme and / or schedule between the hub 814 and UEs (e.g., UE 812C and / or 812D), and between the hub 814 and the core network 806. In other examples, the hub 814 is connected to the core network 806 and / or one or more UEs via a wired connection. Moreover, the hub 814 may be configured to connect to an M2M service provider over the access network 804 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 810 while still connected via the hub 814 via a wired or wireless connection. In some embodiments, the hub 814 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 810B. In other embodiments, the hub 814 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 810B, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0101] FIG. 9 shows a wireless device 900, which may be configured to operate in communication system 800 of FIG. 8 or in communication system QQ200 of FIG. QQ20. Thewireless device 900 may be alternatively referred to as a UE 900, like a UE 812 within the context of communication system 800, or as a station (STA) 900 or as a non-access-point station (non-AP STA) 900, like a STA QQ212 within the context of the communication system QQ200, 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-IoT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[0102] A wireless device 900 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 900 may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, wireless device 900 may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, wireless device 900 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).

[0103] In particular embodiments, wireless device 900 includes processing circuitry 902 that is operatively coupled via a bus 904 to an input / output interface 906, a power source 908, a memory 910, a communication interface 912, and / or any other component, or any combination thereof. Certain embodiments of wireless device 900 may include all or a subset of the components shown in FIG. 9. The level of integration between the components may vary from one embodiment of wireless device 900 to another. In general, in a particular embodiment of wireless device 900, processing circuitry 902, input / output interface 906, power source 908, memory 910, and communication interface 912 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 900. Further, certain embodiments of wireless devices 900 may contain multipleinstances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0104] The processing circuitry 902 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 910. The processing circuitry 902 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 902 may include multiple central processing units (CPUs).

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

[0106] In some embodiments, the power source 908 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 908 may further include power circuitry for delivering power from the power source 908 itself, and / or an external power source, to the various parts of wireless device 900 via input circuitry or an interface such as an electrical power cable. Power source 908 may perform any formatting, converting, or other modification to make accessible power suitable for the respective components of the wireless device 900 to which power is supplied.

[0107] The memory 910 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 readonly memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 910 includes one or more programs 914, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 916. The memory 910 may store, for use by wireless device 900, any of a variety of various operating systems or combinations of operating systems.

[0108] The memory 910 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 (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 910 may allow wireless device 900 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 910, which may be or comprise a device-readable storage medium.

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

[0110] In the illustrated embodiment, communication functions of the communication interface 912 may include cellular communication, Wi-Fi communication (e.g., according to anIEEE 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 / intemet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0111] In particular embodiments, wireless device 900 may provide an output of data captured via a sensor, through its communication interface 912, via a wireless connection to a network node, and / or in any appropriate manner. Data captured by sensors of a wireless device 900 can be communicated through a wireless connection to a network node via another wireless device 900. 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).

[0112] As another example, wireless device 900 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 900 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.

[0113] Wireless device 900, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a wearable for tactile augmentation or sensoryenhancement, 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 900 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 900 shown in FIG. 9.

[0114] As yet another specific example, in an loT scenario, wireless device 900 may represent a machine or other device that performs monitoring and / or measurements, and transmits the results of such monitoring and / or measurements to another wireless device and / or a network node. Wireless device 900 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 900 may implement the 3GPP NB-IoT standard. In other scenarios, wireless device 900 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.

[0115] In practice, any number of wireless devices 900 may be used together with respect to a single use case. For example, a first wireless device 900 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 900 that is a remote controller operating the drone. When a user makes changes from the remote controller, the first wireless device 900 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 900 can also include more than one of the functionalities described above. For example, wireless device 900 might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.

[0116] FIG. 10 shows a network node 1000 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 1000 may be configured to operate in communication system 800 of FIG. 8, like network nodes 808 or 810, or in communication system QQ200 of FIG. QQ2, like an AP QQ210 or a station QQ212. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) andNRNodeBs (gNBs)), O-RAN nodes or components of an O-RAN node (e.g., O-RU, O-DU, O-CU).

[0117] Network nodes 1000 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 1000 may be a relay node or a relay donor node controlling a relay. Network nodes 1000 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).

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

[0119] In particular embodiments, network node 1000 includes a processing circuitry 1002, a memory 1004, a communication interface 1006, and a power source 1008. In general, in a particular embodiment of network node 1000, processing circuitry 1002, memory 1004, communication interface 1006, and power source 1008 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 1000.

[0120] The network node 1000 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 1000 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 1000 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memories 1004 or portions of memory 1004 for different RATs) and some components may be reused (e.g., a same antenna 1010 may be shared by different RATs). The network node 1000 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1000, forexample 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 1000.

[0121] The processing circuitry 1002 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 1004, to provide network node 1000 functionality.

[0122] In some embodiments, the processing circuitry 1002 includes a system on a chip (SOC). In some embodiments, the processing circuitry 1002 includes one or more of radio frequency (RF) transceiver circuitry 1012 and baseband processing circuitry 1014. In some embodiments, the RF transceiver circuitry 1012 and the baseband processing circuitry 1014 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 1012 and baseband processing circuitry 1014 may be on the same chip or set of chips, boards, or units.

[0123] The memory 1004 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 non-volatile, non-transitory device-readable and / or computer-executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry 1002. The memory 1004 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 1002 and utilized by the network node 1000. The memory 1004 may be used to store any calculations made by the processing circuitry 1002 and / or any data received via the communication interface 1006. In some embodiments, the processing circuitry 1002 and memory 1004 is integrated.

[0124] The communication interface 1006 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 1006 comprises port(s) / terminal(s) 1016 to send and receive data, for example to and from a network over a wired connection. In particular embodiments, network node 900 may be capable of wireless communication andcommunication interface 1006 may also include radio front-end circuitry 1018 that may be coupled to, or in certain embodiments a part of, an antenna 1010. Particular embodiments of radio front-end circuitry 1018 include filter(s) 1020 and amplifier(s) 1022. The radio front-end circuitry 1018 may be connected to an antenna 1010 and processing circuitry 1002. The radio front-end circuitry may be configured to condition signals communicated between antenna 1010 and processing circuitry 1002. The radio front-end circuitry 1018 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 1018 may convert the digital data into a radio signal(s) having the appropriate channel and bandwidth parameters using a combination of filters 1020 and / or amplifiers 1022. The radio signal(s) may then be transmitted via the antenna 1010. Similarly, when receiving data, the antenna 1010 may collect radio signals which are then converted into digital data by the radio front-end circuitry 1018. The digital data may be passed to the processing circuitry 1002. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0125] In certain alternative embodiments, network node 1000 may be capable of wireless communication but does not include separate radio front-end circuitry 1018, instead, the processing circuitry 1002 includes radio front-end circuitry and is connected to the antenna 1010. Similarly, in some embodiments, all or some of the RF transceiver circuitry 1012 is part of the communication interface 1006. In still other embodiments, the communication interface 1006 includes one or more ports or terminals 1016, the radio front-end circuitry 1018, and the RF transceiver circuitry 1012, as part of a radio unit (not shown), and the communication interface 1006 communicates with the baseband processing circuitry 1014, which is part of a digital unit (not shown).

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

[0127] The antenna 1010, communication interface 1006, and / or the processing circuitry 1002 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 1000. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna 1010, the communication interface 1006, and / or the processing circuitry 1002 may be configured to perform some or all of the transmitting or sending operations described herein as being performed by the network node 1000. Anyinformation, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.

[0128] The power source 1008 provides power to the various components of network node 1000 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 1008 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 1000 with power for performing the functionality described herein. For example, the network node 1000 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 1008. As a further example, the power source 1008 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.

[0129] Embodiments of the network node 1000 may include additional components beyond those shown in FIG. 10 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 1000 may include user interface equipment to allow input of information into the network node 1000 and to allow output of information from the network node 1000. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 1000.

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

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

Claims

CLAIMS1. A method of operating a first network node in a communications network, the method comprising:receiving (610) configuration information from a second network node including an indication of a threshold value and requesting that the first network node perform thresholdbased reporting of an available bit rate for a quality of service, QoS flow using the threshold value; andtransmitting (630) an indication to the second network node of whether the first network node supports threshold-based reporting of the available bit rate for the QoS flow based on the threshold value.

2. The method of Claim 1, further comprising:responsive to receiving the configuration information, determining (620) whether the first network node supports the threshold-based reporting of the available bit rate for the QoS flow based on the threshold value3. The method of Claim 2, wherein determining whether the first network node supports the threshold-based reporting comprises determining that the first network node supports the threshold-based reporting of the available bit rate for the QoS flow based on the threshold value; andwherein transmitting the indication to the second network node comprises transmitting an indication to the second network node indicating that the first network node supports the threshold-based reporting of the available bit rate for the QoS flow based on the threshold value.

4. The method of Claim 3, wherein transmitting the indication that the first network node supports the threshold-based reporting comprises transmitting at least one of:a threshold-reporting supporting indication information element, IE, to the second network node; anda default bitrate information supported at initial setup of a data session associated with the QoS flow.

5. The method of any of Claims 2-4, wherein receiving the configuration information comprises receiving an indication of a plurality of threshold values including the threshold valueand a request that the first network node perform threshold-based reporting of the available bit rate for the QoS flow using one or more threshold values in the plurality of threshold values, wherein determining whether the first network node supports the threshold-based reporting comprises determining that the first network node supports the threshold-based reporting of the available bit rate for the QoS flow based on the one or more threshold values of the plurality of threshold values; andwherein transmitting the indication to the second network node comprises transmitting an indication to the second network node indicating the one or more threshold values supported by the first network for the threshold-based reporting of the available bit rate for the QoS flow.

6. The method of Claim 5, wherein transmitting the indication to the second network node comprises transmitting an indication to the second network node indicating a minimum supported threshold value supported by the first network node for threshold-based reporting of the available bit rate for the QoS flow.

7. The method of any of Claims 1-6, wherein the first network node comprises a radio access network, RAN, node, andwherein the second network node comprises a core network, CN, node8. The method of Claim 7, wherein transmitting the indication comprises transmitting the indication to the CN node via next generation, NG, signaling during a packet data unit, PDU, session management procedure or NG-based handover procedure.

9. The method of any of Claims 7-8, wherein the CN node comprises an access management and mobility function, AMF, and a user plane function, UPF,wherein receiving the configuration information comprises receiving the configuration information from the AMF, andwherein transmitting the indication comprises transmitting the indication to the AMF.

10. The method of Claim 9, further comprising:responsive to meeting the threshold value, transmitting (660) an indication of the available bit rate reporting to the UPF.

11. The method of any of Claims 1 -6, wherein the first network node comprises a first radio access network, RAN, node, andwherein the second network node comprises a second RAN node.

12. The method of Claim 11, wherein transmitting the indication comprises transmitting the indication to the second RAN node via Xn signaling during a Xn-based handover of the second RAN node to the first RAN node or dual connectivity procedure.

13. The method of any of Claims 11-12, further comprising:receiving (640), as part of a handover from the second RAN node to the first RAN node, an indication of last reported available bitrate by the second network node; andtransmitting (650) an indication of the last reported available bitrate to a core network, CN, node to indicate that the first RAN node supports threshold-based reporting.

14. The method of any of Claims 1-6, wherein the first network node comprises a distributed unit, DU, of a radio access network, RAN, node, andwherein the second network node comprises a central unit, CU, of the RAN node.

15. The method of Claim 14, wherein transmitting the indication comprises transmitting the indication to the CU via Fl signaling during a Fl UE context management procedure.

16. The method of any of Claims 14-15, wherein the CU comprises a CU-control plane, CU-CP, and a CU-user plane, CU-UP,wherein receiving the configuration information comprises receiving the configuration information from the CU-CP, andwherein transmitting the indication comprises transmitting the indication to the CU-CP.

17. The method of Claim 16, further comprising:responsive to meeting the threshold value, transmitting (660) an indication of the available bit rate reporting to the CU-UP.

18. The method of any of Claims 1-6, wherein the first network node comprises a gNB-central unit-user plane, gNB-CU-UP, andwherein the second network node comprises a gNB-central unit-control plane, gNB-CU-CP.

19. The method of any of Claims 1-18, further comprising:responsive to meeting the threshold value, transmitting (660) an indication of the available bit rate to the second network node.

20. The method of any of Claims 1-19, further comprising:subsequent to transmitting the indication to the second network node, receiving (670) at least one of:an indication to modify the threshold value from the second network node; and an indication to stop the threshold-based reporting of the available bit rate for the QoS flow.

21. A method of operating a second network node in a communications network, the method comprising:transmitting (710) configuration information to a first network node including an indication of a threshold value and requesting that the first network node perform thresholdbased reporting of an available bit rate for a quality of service, QoS flow using the threshold value;responsive to transmitting the configuration information, receiving (720) an indication from the first network node of whether the first network node supports the threshold-based reporting of the available bit rate for the QoS flow based on the threshold value.

22. The method of Claim 21, wherein receiving the indication from the first network node comprises receiving an indication from the first network node indicating that the first network node supports the threshold-based reporting of the available bit rate for the QoS flow based on the threshold value.

23. The method of Claim 22, wherein receiving the indication that the first network node supports the threshold-based reporting comprises receiving a threshold-reporting supporting indication information element, IE, from the first network node.

24. The method of any of Claims 22-23, wherein receiving the indication that the first network node supports the threshold-based reporting comprises receiving default bitrate information supported at initial setup of a data session associated with the QoS flow.

25. The method of any of Claims 22-24, wherein transmitting the configuration information comprises transmitting an indication of a plurality of threshold values including the thresholdvalue and a request that the first network node perform threshold-based reporting of the available bit rate for the QoS flow using one or more threshold values in the plurality of threshold values, andwherein receiving the indication from the first network node comprises receiving an indication from the first network node indicating the one or more threshold values supported by the first network for the threshold-based reporting of the available bit rate for the QoS flow.

26. The method of Claim 25, wherein receiving the indication from the first network node comprises receiving an indication from the first network node indicating a minimum supported threshold value supported by the first network node for threshold-based reporting of the available bit rate for the QoS flow.

27. The method of any of Claims 21-26, wherein the first network node comprises a radio access network, RAN, node, andwherein the second network node comprises a core network, CN, node28. The method of Claim 27, wherein receiving the indication comprises receiving the indication from the RAN node via next generation, NG, signaling during a packet data unit, PDU, session management procedure or NG-based handover procedure.

29. The method of any of Claims 27-28, wherein the CN node comprises an access management and mobility function, AMF, and a user plane function, UPF,wherein transmitting the configuration information comprises transmitting, by the AMF, the configuration information to the RAN node, andwherein receiving the indication comprises receiving, by the AMF, the indication from the RAN node.

30. The method of Claim 29, further comprising:receiving (760), by the UPF, an indication of the available bit rate from the RAN node.

31. The method of any of Claims 21-26, wherein the first network node comprises a first radio access network, RAN, node, andwherein the second network node comprises a second RAN node.

32. The method of Claim 31, wherein receiving the indication comprises receiving the indication from the first RAN node via Xn signaling during a Xn-based handover of the second RAN node to the first RAN node or dual connectivity procedure.

33. The method of any of Claims 31-32, further comprising:transmitting (740), as part of a handover from the second RAN node to the first RAN node, an indication of last reported available bitrate by the second network node.

34. The method of any of Claims 21-26, wherein the first network node comprises a distributed unit, DU, of a radio access network, RAN, node, andwherein the second network node comprises a central unit, CU, of the RAN node.

35. The method of Claim 34, wherein receiving the indication comprises receiving the indication from the DU via Fl signaling during a Fl UE context management procedure.

36. The method of any of Claims 34-35, wherein the CU comprises a CU-control plane, CU-CP, and a CU-user plane, CU-UP,wherein transmitting the configuration information comprises transmitting, by the CU-CP, the configuration information to the DU, andwherein receiving the indication comprises receiving, by the CU-CP, the indication from the DU.

37. The method of Claim 36, further comprising:receiving (760), by the CU-UP, an indication of the available bit rate from the DU.

38. The method of any of Claims 21-26, wherein the first network node comprises a gNB-central unit-user plane, gNB-CU-UP, andwherein the second network node comprises a gNB-central unit-control plane, gNB-CU-CP.

39. The method of any of Claims 21-38, further comprising:receiving (760) an indication of the available bit rate from the first network node.

40. The method of any of Claims 21-39, further comprising:subsequent to receiving the indication from the first network node, transmitting (770) at least one of:an indication to modify the threshold value to the first network node; and an indication to stop the threshold-based reporting of the available bit rate for the QoS flow.

41. A first network node (1000) adapted to perform any of the operations of Claims 1-20.

42. A computer program comprising program code to be executed by processing circuitry (1002) of a first network node (1000), whereby execution of the program code causes the first network node to perform any of the operations of Claims 1-20.

43. A computer program product comprising a non-transitory storage medium (1004) including program code to be executed by processing circuitry (1002) of a first network node (1000), whereby execution of the program code causes the first network node to perform any of the operations of Claims 1-20.

44. A second network node (1000) adapted to perform any of the operations of Claims 21-40.

45. A computer program comprising program code to be executed by processing circuitry (1002) of a second network node (1000), whereby execution of the program code causes the second network node to perform any of the operations of Claims 21-40.

46. A computer program product comprising a non-transitory storage medium (1004) including program code to be executed by processing circuitry (1002) of a second network node (1000), whereby execution of the program code causes the second network node to perform any of the operations of Claims 21-40.

Images