Patent Application
20240196252
The present disclosure relates to methods for managing radio resources in a Radio Access Network (RAN) of a communication network. The present disclosure also relates to a first, second and third nodes in a RAN, and to a computer program and a computer program product configured, when run on a computer to carry out methods for managing radio resources in a RAN of a communication network.
Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and/or is implied from the context in which it is used. All references to a/an/the element, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any methods disclosed herein do not have to be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and/or where it is implicit that a step must follow or precede another step. Any feature of any of the examples disclosed herein may be applied to any other example, wherever appropriate. Likewise, any advantage of any of the examples may apply to any other examples, and vice versa. Other objectives, features and advantages of the enclosed examples will be apparent from the following description.
The current 5G RAN (NG-RAN) architecture, as illustrated in
The NG-RAN consists of a set of gNBs connected to the 5GC through the NG interface. A gNB can support FDD mode, TDD mode or dual mode operation. gNBs can be interconnected through the Xn interface. A gNB may consist of a gNB-CU and gNB-DUs. A gNB-CU and a gNB-DU are connected via the F1 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 F1 are logical interfaces. The NG-RAN is layered into a Radio Network Layer (RNL) and a Transport Network Layer (TNL). The NG-RAN architecture, i.e., the NG-RAN logical nodes, and interfaces between them, are defined as part of the RNL. For each NG-RAN interface (NG, Xn, F1) the related TNL protocol and the functionality are specified. The TNL provides services for user plane transport and signaling transport.
A gNB may also be connected to an LTE eNB via the X2 interface. Another architectural option is where an LTE eNB connected to the Evolved Packet Core network is connected over the X2 interface with a so called nr-gNB. The latter is a gNB not connected directly to a CN and connected via X2 to an eNB for the sole purpose of performing dual connectivity.
The architecture in
The XnAP and X2AP procedures are defined in 3GPP so that a RAN node can provide another RAN node with Resource Status Update related to different resources. The relevant procedures are:
In TS 36.423 v16.2.0 (X2AP):
In the example illustrated in
With a prediction model, it is possible to estimate the probability of data arriving in the downlink and/or uplink. This could for example be the probability of data arriving within time T, or data received within the frame T1 to T2. The prediction could be based on the history of data transmissions/receptions of the UE (i.e. traffic pattern), UE behavior (e.g. activity and mobility pattern, etc.), or those of other UEs, for example by using any of the following inputs:
Current telecommunication systems have several ways to measure and report metrics that allow determination of resources consumed or available in a given area of coverage. Such metrics can be used for various purposes. In one example of current solutions, mobility load balancing decisions consider load metrics reflecting measurements taken in the past and reported from one (source) node to another (target) RAN node. One of the uses the target RAN node makes of such information is to decide which mobility target cell is the best possible handover target. There currently exist certain challenges, including supporting other uses that could be envisaged for information regarding resources used in a cell served by a neighbor RAN node.
It is an aim of the present disclosure to provide methods, first and third RAN nodes, and a computer readable medium which at least partially address one or more of the challenges discussed above. It is a further aim of the present disclosure to provide methods, first and third RAN nodes, and a computer readable medium which facilitate the management of radio resources within a RAN.
According to a first aspect of the present disclosure, there is provided a computer implemented method for managing resources in a Radio Access Network (RAN) of a communication network. The method, performed by a first node in the RAN, comprises obtaining a record of resource status information describing usage, during a historical time period, of RAN resources controlled by a second node in the RAN. The method further comprises predicting, based on the obtained record, resource status information describing usage of RAN resources controlled by the second node during a future time period. The method then comprises performing at least one of using the predicted resource status information describing usage of RAN resources controlled by the second node in a process relating to management of RAN resources controlled by the first node, or sending, to a third node in the RAN, a representation of the predicted resource status information describing usage of RAN resources controlled by the second node.
According to another aspect of the present disclosure, there is provided a computer implemented method for managing resources in a Radio Access Network (RAN) of a communication network. The method, performed by a third node in the RAN, comprises receiving, from a first node in the RAN, a representation of predicted resource status information describing usage of RAN resources controlled by a second node in the RAN during a future time period. The method further comprises using the predicted resource status information describing usage of RAN resources controlled by the second node in a process relating to management of RAN resources controlled by the third node.
According to another aspect of the present disclosure, there is provided a computer program product comprising a computer readable medium, the computer readable medium having computer readable code embodied therein, the computer readable code being configured such that, on execution by a suitable computer or processor, the computer or processor is caused to perform a method according to any one or more of aspects or examples of the present disclosure.
According to another aspect of the present disclosure, there is provided a first node in a communication network comprising a RAN, the first node being configured to manage resources in the Radio Access Network, RAN. The first node is configured to obtain a record of resource status information describing usage, during a historical time period, of RAN resources controlled by a second node in the RAN and to predict, based on the obtained record, resource status information describing usage of RAN resources controlled by the second node during a future time period. The first node is further configured to perform at least one of using the predicted resource status information describing usage of RAN resources controlled by the second node in a process relating to management of RAN resources controlled by the first node, or sending, to a third node in the RAN, a representation of the predicted resource status information describing usage of RAN resources controlled by the second node.
According to another aspect of the present disclosure, there is provided a third node in a communication network comprising a RAN, the third node being configured to manage resources in the Radio Access Network, RAN. The third node is configured to receive, from a first node in the RAN, a representation of predicted resource status information describing usage of RAN resources controlled by a second node in the RAN during a future time period, and to use the predicted resource status information describing usage of RAN resources controlled by the second node in a process relating to management of RAN resources controlled by the third node.
Examples of the present disclosure thus propose methods according to which a first RAN node may predict resource use, for example in the form of load metrics, of another network node. The predicted resource utilization can be used as input to processes for traffic steering and optimization such as load balancing or radio resource management. Examples of the present disclosure also propose signaling support for exchanging the predicted values of resource use between RAN nodes.
For a better understanding of the present disclosure, and to show more clearly how it may be carried into effect, reference will now be made, by way of example, to the following drawings in which:
As discussed above, there are many potential uses within a RAN for information about resource use at different RAN nodes. There may be additional use cases if the information encompassed a prediction of resources that will be used, for example for different radio carrier frequencies. There is generally a lack of support for the exchange of anticipated resource use metrics, which metrics could be input to several RAN processes, including load balancing, mobility and radio resource management.
One case of interest is shown in
Examples of the present disclosure provide methods according to which a RAN node may estimate or predict resource utilization, for example in the form of load metrics, for another network node. The estimated or predicted resource use can be used as input to algorithms for traffic steering and optimization such as load balancing or radio resource management. Examples of the present disclosure also provide signaling support for exchanging the predicted values of resource use. The predicted values can be derived based on the actual and predicted status of resources in an given RAN node, and may also be derived based on the actual and predicted status of resources in other neighbor RAN nodes, and/or a history of load balancing decisions taken by the RAN node and its neighbor RAN nodes.
The predicted status of resource use can be obtained using rules based or other processes, using Artificial Intelligence or Machine Learning AI/ML algorithms and models found in literature, or by applying novel AI/ML algorithms and models. For the case illustrated in
Referring to
The method 400 of
Referring to
In some examples of the present disclosure, obtaining a record of resource status information from the second node, and sending a representation of predicted resource statis information to the third node, may be accomplished through the receiving and sending of resource utilization messages. One example implementation of the methods 400, 500 is illustrated in the message flow diagram of
Different examples of the present disclosure may vary the type and granularity of load metrics associated with the second network node that are estimated or predicted by the first network node on the basis of the resource status information, for example received measurements or resource utilization, of the second network node.
In one example, the first network node transmits a FIRST RESOURCE UTILIZATION REQUEST message to the second network node. The FIRST RESOURCE UTILIZATION REQUEST may for example be a RESOURCE STATUS REQUEST message defined in the 3GPP LTE and NR systems. The FIRST RESOURCE UTILIZATION REQIEST message may trigger the second network node to provide the resource status information obtained by the first network node in step 120 of the method 100.
In one example, the first node may collect measures of its own and other network node utilized resources in addition to resource status information for the second node, and may provide such measures, for example together with other information available at the node, as input to an algorithm or process that predicts the resources utilized by the second network node in a future time window. Such resource utilization prediction may be derived for different parts of the system, for example for the radio interface, for the transport network, for specific cells or beamformed coverage areas, for specific classes of services or network slices.
The first network node may further receive a SECOND RESOURCE UTILIZATION REQUEST message from the third network node, comprising a request for resource utilization associated with the second network node. In one possible implementation, the SECOND RESOURCE UTILIZATION REQUEST is a RESOURCE STATUS REQUEST message defined in the 3GPP LTE and NR systems.
In another example, the SECOND RESOURCE UTILIZATION REQUEST message from the third network node may comprise a list of cells served by the second network node. The list of cells may have been received by the third network node from the first network node (e.g. as part of “Neighbor Information NR” IE or “Neighbor Information E-UTRA” IE in XnAP XN SETUP REQUEST message). The list of cells may include cells served by the second network node for which the third node is interested to receive predicted load metrics information and/or measured load metrics. Non limiting examples of reasons for such an interest are:
In one example, the first network node may send the FIRST RESOURCE UTILIZATION REQUEST message to the second node in response to receiving the SECOND RESOURCE UTILIZATION REQUEST message from the third node. The first node may then forward information about the predicted use of resources by the second node to the third node, for example in response to the SECOND RESOURCE UTILIZATION REQUEST message. The third node may use this information for a number of purposes.
In one example, the third node receiving the prediction of resource utilization associated with the second network node may use it to optimize its traffic steering and radio resource management functions, e.g. mobility related decisions. For example, on the basis of a predicted load for a given future time window, the third network node may determine which of the potential handover target cells of the second network node may be the optimal to serve a moving UE and select the determined cell as target.
In another example, the third network node receiving the prediction of resource utilization associated with the second network node may use it to estimate the level of cross cell interference caused by communication on the utilized resources of neighboring cells of the second network node. This may assist the third network node in taking decisions on resource utilization or on configuration of radio channels that are affected by the resource utilization of the second network node.
Example methods of the present disclosure thus provide a process according to which a third network node may consider the predicted status of resources of a second network node, with which the first network node may have no direct signaling connection, as input for its traffic steering and radio resource management functions. The predicted status may be generated by a first network node having a direct signaling connection with each of the third and second network nodes. This provision of predicted resource status may have considerable advantages for the smooth execution and resource optimization of operations involving one, or more of the nodes. For example, a mobility related decision can be taken to move UEs between the first network node towards the second network node via indirect signaling. Traffic steering and radio resource management functions of the third network node can consequently be improved using inputs including prediction of resources used by the second network node, obtained via a first network node.
Some of the example methods and nodes contemplated herein will now be described more fully with reference to the accompanying drawings. Other examples, however, are contained within the scope of the subject matter disclosed herein, the disclosed subject matter should not be construed as limited to only the examples set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.
It will be appreciated that for the purposes of the present disclosure, a node of a Radio Access Network (RAN), also referred to herein as a RAN node, comprises a node that is operable to transmit, receive, process and/or orchestrate wireless signals. A RAN node may comprise a physical node and/or a virtualized network function.
The term RAN node may therefore refer to Long Term Evolution (LTE) or New Radio (NR) technology and may be one of eNB, gNB, en-gNB, ng-eNB, CU-CP, CU-UP, DU, gNB-CU, gNB-DU, gNB-CU-UP, gNB-CU-CP, eNB-CU, eNB-DU, eNB-CU-UP, eNB-CU-CP, IAB-node, IAB-donor DU, IAB-donor-CU, IAB-DU, IAB-MT, O-CU, O-CU-CP, O-CU-UP, O-DU, O-RU, O-eNB, or any future implementation of the above discussed functionality.
Also for the purposes of the present specification, the term RAN resources refers to any resources available to the RAN network, and under the control of one or more nodes of the RAN network. Such resources may include radio spectrum resources, examples of which include PRBs in downlink and uplink, PDCCH CCEs for downlink and uplink and other examples, such as are reported in TS38.423 for the IE Radio Resource Status. A coverage area of a RAN node refers to the geographical and/or radio area over which the RAN node provides access to the communication network.
Referring first to
As illustrated at 702a the request for a representation of predicted resource status information describing usage of RAN resources controlled by the second node may comprise a list of cells served by the second node and for which prediction of resource status information metrics is requested. The list may have been received from the first node, for example as part of a neighbor relation procedure. The request for a representation of predicted resource status information may comprise a modified Resource Status Request message, or any other newly specified or existing message suitable for conveying the request.
As illustrated at 702b, the request for a representation of predicted resource status information describing usage of RAN resources controlled by the second node may also or alternatively comprise at least one of a specification of resource status information metrics to be predicted, a requested granularity of prediction, a part of the communication network for which prediction is requested, and/or a reporting configuration for providing the requested representation. The part of the network could be a plurality of cells, a radio interface, network slice, or may correspond to any of the criteria illustrated at 721i to 721vix of
The specification of resource status information metrics to be predicted comprise any one or more of the metrics listed in
Referring still to
As illustrated at 704b, the second node may be a neighbor of the first node, such that a signaling connection is established between the first node and second node. The third node may or may not be a neighbor of the second node, and a signaling connection may or may not be established and/or functional between the third and second nodes.
In step 706, the first node receives from the second node an acknowledgment of the request sent in step 704. In some examples, the acknowledgement may comprise a Resource Status Response message, or any other newly specified or existing message suitable for conveying the acknowledgement. As illustrated at 706a, the acknowledgement may indicate at least one of an extent to which resource status information metrics specified in the request sent by the first node can be provided by the second node, and/or an extent to which a reporting configuration specified in the request sent by the first node will be respected by the second node. The extent to which the requested information can be provided could be all of the requested information, some of the requested information, or none of the requested information, in which case the acknowledgement may comprise a failure message.
If the first node performed step 702 of receiving a request for status information from the third node, the first node may then, at step 708, determine based on the acknowledgment received from the second node an extent to which the representation of predicted resource status information requested by the third node can be provided.
Referring now to
As illustrated at 710a, the first node may include in the acknowledgement to the third node at least one of (i) the determined extent to which the representation of predicted resource status information describing usage of RAN resources controlled by the second node, requested by the third node, can be provided, and/or (2) an extent to which a reporting configuration specified in the request sent by the third node will be respected by the first node.
In step 720, the first node receives in a message from the second node a record of resource status information describing usage, during a historical time period, of RAN resources controlled by the second node.
Referring now to
Further discussion of the above metrics is provided in later sections of the present disclosure. The record of resource status information could be included in a Resource Status Response message, or any other newly specified or existing message suitable for conveying examples of the above discussed resource utilization metrics.
Referring again to
As discussed above, while the example method 700 uses an ML model to predict resource status information for the second node during a future time period, other prediction processes, such as rule-based processes, may be envisaged for this step.
As illustrated at 730b, the prediction may also be based on at least one of:
The previously predicted information may comprise predictions generated by the first node or obtained predictions, for example received from the second or third nodes.
The measure of uncertainty may be per predicted matric or a global measure for the prediction.
As illustrated in
Referring now to
In step 750, the first node uses the predicted resource status information describing usage of RAN resources controlled by the second node in a process relating to management of RAN resources controlled by the first node. As illustrated at 750a, this may comprise inputting the received representation of predicted resource status information for RAN resources controlled by the second node to a resource optimization process. The resource optimization process may relate to load balancing, mobility events, or other resource management procedures, including for example handover, traffic steering to/from the second node, etc.
In step 732, if the first node is to send a representation of the predicted information to the third node, the first node checks for fulfillment of a trigger condition, which may comprise at least one of a timer or a threshold for a predicted metric. The trigger condition may for example have been specified in a request received from the third node in step 702. In step 740, on fulfillment of the trigger condition, the first node sends to the third node, a representation of the predicted resource status information describing usage of RAN resources controlled by the second node. As illustrated at 740a, the representation of the predicted resource status information describing usage of RAN resources controlled by the second node may comprise a change from a previously predicted value of a resource status information metric. The representation of the predicted resource status information could be included in a modified Resource Status Response message, or any other newly specified or existing message suitable for conveying the representation. In one example, the representation of the predicted resource status information could be included in a SECOND RESOURCE UTILIZATION MESSAGE, and may comprise elements described below in connection with that message.
In step 760, the first node may in some examples send the representation of the predicted resource status information describing usage of RAN resources controlled by the second node to the second node.
Referring now to
Referring first to
In step 804, the third node may send to a first node in the RAN a request for the representation of predicted resource status information describing usage of RAN resources controlled by the second node. As illustrated at 802 and 804, at least one of the first, second or third nodes may comprise at least one of an eNB; ng-eNB; eNB-CU; eNB-DU; eNB-CU-UP; eNB-CU-CP; gNB; en-gNB; gNB-CU; gNB-DU; gNB-CU-UP; and/or gNB-CU-CP. The request for a representation of predicted resource status information may in some examples comprise a modified Resource Status Request message as defined in LTE and 5G systems.
As illustrated at 804a, the second node may be a neighbor of the first node, such that a signaling connection is established between the first node and second node. The third node may or may not be a neighbor of the second node, and a signaling connection may or may not be established and/or functioning between the third and second nodes.
As illustrated at 804b, the request for a representation of predicted resource status information describing usage of RAN resources controlled by the second node may comprise a list of cells served by the second node and for which prediction of resource status information metrics is requested. The list may have been received from the first node, for example as part of a neighbor relation procedure. The request for a representation of predicted resource status information may comprise a modified Resource Status Request message, or any other newly specified or existing message suitable for conveying the request.
As illustrated at 804c, the request for a representation of predicted resource status information describing usage of RAN resources controlled by the second node may also or alternatively comprise at least one of a specification of resource status information metrics to be predicted, a requested granularity of prediction, a part of the communication network for which prediction is requested, and/or a reporting configuration for providing the requested representation. The part of the network could be a plurality of cells, a radio interface, network slice, or may correspond to any of the criteria illustrated at 721i to 721vix of
The specification of resource status information metrics to be predicted comprise any one or more of the metrics listed in
In step 806, the third node may receive from the first node an acknowledgement of the request for a representation of predicted resource status information describing usage of RAN resources controlled by the second node. The acknowledgement may for example be a modified Resource Status Response message, or any other newly specified or existing message suitable for conveying the acknowledgement. As illustrated at 806a, the acknowledgement may include at least one of (1) an extent to which the representation of predicted resource status information describing usage of RAN resources controlled by the second node, requested by the third node, can be provided by the first node, and/or (2) an extent to which a reporting configuration specified in the request sent by the third node will be respected by the first node.
Referring now to
In step 820, the third node uses the predicted resource status information describing usage of RAN resources controlled by the second node in a process relating to management of RAN resources controlled by the third node. As illustrated at 820a, this may comprise inputting the received representation of predicted resource status information for RAN resources controlled by the second node to a resource optimization process. The resource optimization process may relate to load balancing, mobility events, or other resource management procedures, including for example handover, traffic steering to/from the second node, etc.
a-f, and 8a-b discussed above provide an overview of methods which may be performed according to different examples of the present disclosure. The methods involve a first node in a RAN obtaining a record of resource status information for a second node in the RAN. The first node uses the record to predict resource usage for the second node in a future time period, and may use this prediction it its own resource optimization procedures, and may also or alternatively provide a representation of the prediction to a third node in the RAN. In this manner, predicted resource usage at different RAN nodes may be provided to other RAN nodes, so allowing such nodes to take this predicted usage into account in their own resource optimization procedures, resulting in improved overall resource management. There now follows a detailed discussion of how different process steps illustrated in
In the following example implementations, methods in accordance with the present disclosure are executed in a RAN in which a first RAN node is neighboring a second RAN node and a third RAN node. A signaling connection is established between the first network node and the second network node, and between the first network node and the third network node. The cells served by the second RAN node may provide coverage for a geographical area that is adjacent to the coverage provided by the cells served by the third RAN node. In some examples, there may also exist a direct signaling connection (e.g. via XnAP or X2AP) between the second RAN node and the third RAN node.
Implementation relating to the first network node (methods 400, 700)
According to a first example implementation, the first network node:
The FIRST RESOURCE UTILIZATION message received from the second network node comprises actual resource utilization information of the second network node, i.e. measurements of actual resource utilization performed by the second network node in previous measurement intervals. As such, this information can be obtained by the first network node via legacy methods, such as the RESOURCE STATUS REPORTING procedure of 3GPP LTE and NR systems. The first network node may determine an estimate or a prediction of the resource status or resource utilization associated with the second RAN node for future time instances based on the actual resource status or resource utilization information during past time instances. The first network node may adopt, for instance, machine learning and/or artificial intelligence (ML/AI) techniques to estimate and/or predict the future resource utilization of the second network node. The measurements received with the FIRST RESOURCE UTILIZATION message may provide a reference for the accuracy of the estimate performed in previous time instances.
In one example, the first network node uses the estimated or predicted resource utilization in neighboring coverage areas, such as neighboring cells, controlled by a second network node, to make improved mobility decisions, such as for handover or traffic steering to/from the second RAN node. In one example, the first network node may use the estimated or predicted (future) resource utilization associated for the second network node, in addition to or as a replacement for the resource utilization reported by the second network node for previous time instances, to deduce how much traffic can be handed over to the second network node coverage area, and therefore how much resource will be available in the coverage area provided by cells served by the first network node and by cells served by the second network node. In another example, the first network node may use its prediction of the future resource utilization associated with the second network node to deduce how much interference the second network node may cause to radio communications between the first network node and UEs camped on or served by cells served by first network node. This in turn provides an indication of how much resource the first network node needs to serve its UEs, for example with higher interference from neighbor cells, lower modulation and coding schemes may need to be selected and therefore less spectral efficiency is achieved.
In one example, the first network node may use the estimated or predicted resource utilization in neighboring coverage areas, such as neighboring cells, controlled by a second network node to assist mobility optimization decisions of a third network node. In this case, the first network node may additionally:
Scenarios that may benefit from the first network node sending the prediction to the third network node include:
In one example, the first network node additionally:
A RESOURCE UTILIZATION REQUEST from the third node to the first node could be implemented, for example, with enhancements to existing signaling procedures such as a RESOURCE STATUS REQUEST of the 3GPP LTE and NR systems, as illustrated in 9. The received request may specify which type of resource utilization metrics should be estimated/predicted, with what granularity (for example in the frequency domain, time domain or spatial domain, coverage beam, slice), the reporting mechanism (for example periodic or aperiodic reporting, reporting resources).
In the illustrated example, the FIRST RESOURCE UTILIZATION REQUEST could be implemented with existing signaling procedure such as a RESOURCE STATUS REQUEST of the 3GPP LTE and NR systems as illustrated in
In the example illustrated in
Upon receiving an acknowledgment message from the second network, the first network node may additionally:
In both of the above cases, the RESOURCE UTILIZATION ACKNOWLEDGEMENT message could be implemented, for example, with existing signaling procedure such as a RESOURCE STATUS RESPONSE message of the 3GPP LTE and NR systems as illustrated in
In the example illustrated in
Also in this case, the RESOURCE UTILIZATION FAILURE messages could be implemented, for example, with existing signaling procedure such as a RESOURCE STATUS FAILURE message of the 3GPP LTE and NR systems.
The SECOND RESOURCE UTILIZATION MESSAGE transmitted from the first network node to the third network node may comprise one or more information elements pertaining to predictions of resource status utilization for the second network node. The information elements may be selected from the group of:
Predicted Slice Available Capacity, in uplink and/or downlink namely a prediction of the capacity available over a specific radio coverage area of the node and for a specific network slice
It will be appreciated that the metrics listed above may be collected according to at least one of the following criteria:
In one example of the methods disclosed herein, the SECOND RESOURCE UTILIZATION MESSAGE may comprise one or more predictions of resource status utilization according to the SECOND RESOURCE UTILIZATION REQUEST received from third network node.
The first network node may determine an estimate or a prediction of the future resource status information associated with the second network node by means, for instance, of machine learning algorithms or estimation algorithms. The first network node may combine one or more information elements including:
In another example, the prediction can comprise a time-offset and value related to a previous prediction. In a related example, the first or third nodes can select a threshold for the granularity of reporting. For example, first node reports a new value when a new predicted value is T larger than previous value. The first node then signals the time-instance when the predicted value is larger than the threshold T.
Example ML models suitable for generating the predicted future resource status information are listed above, and include an Autoregressive model, a Feedforward Neural Network, a Convolutional Neural Network, a graph-based Neural Network, a Recurrent Neural Network and/or a Long Short-Term Memory process. It will be appreciated that a wide range of algorithms may be used to generate predictions for one or more different resource use metrics, depending on the nature of the metric for which information is to be predicted, computation resources and capabilities available at the first network node, and available inputs, which include the obtained report of resource usage at the second node, but may also include any one or more of the elements listed above. For example, a regression algorithm may be used to predict a continuous variable in one example, or a continuous variable may be divided into different possible value ranges, and a classification algorithm may be used to predict a value range in which the variable is likely to sit. In other examples, classification algorithms may be used to predict whether a continuous variable will exceed a threshold level, or to predict a value of a discrete variable.
Non-limiting examples of estimation algorithms suitable for generating the predicted future resource status information include regression algorithms, Kalman filters, maximum likelihood algorithms, etc.
According to another example implantation, the third node may:
The SECOND RESOURCE UTILIZATION REQUEST could be implemented, for example, with enhancements to existing signaling procedures such as a RESOURCE STATUS REQUEST of the 3GPP LTE and NR systems as illustrated in
The SECOND RESOURCE UTILIZATION REQUEST transmitted from the third network node to the first network node may comprise a request for one or more information elements pertaining to predictions of resource status utilization associated to resources controlled by the second network node. The information elements may be selected from the group of:
It will be appreciated that the metrics listed above may be collected according to at least one of the following criteria:
In one example of the methods disclosed herein, the SECOND RESOURCE UTILIZATION REQUEST may configure what the first network node should report in the SECOND RESOURCE UTILIZATION MESSAGE.
The third network node may additionally:
The following examples are illustrated and explained in the context of 3GPP LTE-A and 3GPP NG-RAN terminology, but it will be appreciated that these examples are not intended to be limiting upon the scope of the present disclosure. Similarly, the following examples are illustrated and explained using the RESOURCE UTILIZATION MESSAGE exchanged between the first network node and the second and third network nodes. However, will be appreciated that similar implementations of methods according to the present disclosure may be achieved using:
As discussed above, the first network node, the second network node and the third network node can be any type of node in the group of: evolved NodeB (eNB), NG-RAN node (also knowns as gNB), en-gNB, ng-eNB, CU-CP, CU-UP, DU, gNB-CU, gNB-DU, gNB-CU-UP, gNB-CU-CP, eNB-CU, eNB-DU, eNB-CU-UP, eNB-CU-CP, IAB-node, IAB-donor DU, IAB-donor-CU, IAB-DU, IAB-MT, O-CU, O-CU-CP, O-CU-UP, O-DU, O-RU, O-eNB.
In the example illustrated in
In the example illustrated in
In the example illustrated in
In the example illustrated in
In the example illustrated in
In the example of
In an alternative example, not illustrated in
This is beneficial to optimize one or more network operation functions (such as, RACH optimization, mobility robustness optimization, load balancing optimization etc.) involving an NG-RAN node and an E-UTRAN node.
There now follows an illustration of how example methods according to the present disclosure may be implemented using the XnAP procedure (3GPP TS 38.423 v16.5.0). The elements marked in Italic are specific to the present disclosure.
It will be appreciated that the following language is intended to represent typical syntax used in 3GPP specifications. The example consequently refers to the signaling between two NG-RAN nodes, referred to as NG-RAN node1 and NG-RAN node2, respectively. NG-RAN node1 is an example of a third network node according to the present disclosure, and NG-RAN node2 is an example of the first network node in the disclosure.
This message is sent by NG-RAN node1 to NG-RAN node2 to initiate a requested measurement according to the parameters given in the message.
Direction: NG-RAN node1 to NG-RAN node2.
0 . . . 1
1 . . .
<maxnoofCellsinNG-RANnode>
0 . . . 1
1 . . .
<maxnoofSSBAreas>
0 . . . 1
1 . . .
1
1 . . .
<maxnoofSliceItems>
Indirect prediction
0 . . . <maxnoofNG-
Request
RANnodesForPrediction>
> Global NG
—
RAN
M
9.2.2.3
Node ID
> Cell Measurement
1 . . .
Result Item
<maxnoofCellsinNG-RANnode>
>> Cell ID
M
Global NG-RAN Cell
Identity 9.2.2.27
>>>SSB To Report
0 . . . 1
List
>>>>SSB To Report
1 . . .
Item
<maxnoofSSBAreas>
>>>>>SSB-Index
M
INTEGER
>>>Slice To Report
0 . . . 1
List
>>>>Slice To Report
1 . . .
Item
<maxnoofBPLMNs>
>>>>>PLMN Identity
M
9.3.1.14
>>>>>S-NSSAI List
1
>>>>>>S-NSSAI Item
1 . . .
<maxnoofSliceItems>
>>>>>>>S-NSSAI
M
S-NSSAI 9.3.1.38
Indirect prediction
Request for indirect prediction
YES
Ignore
Request
updates
> Global NG
—
RAN
NG-RAN node for which prediction
YES
Reject
Node ID
updates are requested
> Cell Measurement
Result Item
>> Cell ID
>>>SSB To Report
SSB list to which the request
List
applies.
>>>>SSB To Report
Item
>>>>>SSB-Index
>>>Slice To Report
S-NSSAI list to which the request
List
applies.
>>>>Slice To Report
Item
>>>>>PLMN Identity
>>>>>S-NSSAI List
>>>>>>S-NSSAI Item
>>>>>>>S-NSSAI
maxnoofNG-RANnodesForPrediction
Maximum no. NG-RAN nodes for which predictions can be
provided. Value is 32.
This message is sent by NG-RAN node2 to NG-RAN node1 to report the results of the requested measurements.
Direction: NG-RAN node2 to NG-RAN node1.
1
1 . . .
<maxnoofCellsinNG-
RANnode>
Indirect prediction
0 . . . <maxnoofNG-
Information
YES
Ignore
updates
RANnodesForPrediction>
requested for
indirect
forwarding of
prediction
updates.
Time of prediction
M
ENUMERATED
validity
500 ms, 1 s, 2 s,
5 s, 10 s, 20 s
30 s, 40 s, 50 s,
1 m, 2 m, 5 m,
10 m, 20 m, 30 m,
40 m, 50 m,
1 h, . . .)
Predicted uncertainty
M
INTEGER
> Global NG
—
RAN
M
9.2.2.3
NG-RAN node
YES
Reject
Node ID
for which
prediction
updates are
provided
> Cell Measurement
1 . . .
Result Item
<maxnoofCellsinNG-
RANnode>
>> Cell ID
M
Global NG-RAN
Cell Identity
9.2.2.27
>> Radio Resource
M
9.2.2.50
Status Prediction
Update
>> TNL Capacity
M
9.2.2.49
Indicator Prediction
Update
>> Composite
M
9.2.2.51
Available Capacity
Group Prediction
Update
>> Slice Available
O
9.2.2.55
Capacity Prediction
Update
>> Number of Active
O
9.2.2.62
UEs Prediction
Update
>> RRC Connection
O
9.2.2.56
Prediction Update
maxnoofNG-RANnodesForPrediction
Maximum no. NG-RAN nodes for which predictions can be provided.
Value is 32.
As discussed above, the methods 400 and 700 are implemented by a first node in a RAN, and the present disclosure provides a first node that is adapted to perform any or all of the steps of the above discussed methods. The first node may be a physical or virtual node, and may for example comprise a virtualised function that is running in a cloud, edge cloud or fog deployment. The first node may for example comprise or be instantiated in any part of a logical Radio Access node. Any such communication network node may itself be divided between several logical and/or physical functions, and any one or more parts of the management node may be instantiated in one or more logical or physical functions of a communication network node.
Referring to
As discussed above, the methods 500 and 800 may be performed by a third node in a RAN, and the present disclosure provides a third node that is adapted to perform any or all of the steps of the above discussed methods. The third node may be a physical or virtual node, and may for example comprise a virtualised function that is running in a cloud, edge cloud or fog deployment. The third node may for example comprise or be instantiated in any part of a logical Radio Access node. Any such communication network node may itself be divided between several logical and/or physical functions, and any one or more parts of the management node may be instantiated in one or more logical or physical functions of a communication network node.
Referring to
Although the subject matter described herein may be implemented in any appropriate type of system using any suitable components, the embodiments disclosed herein are described in relation to a wireless network, such as the example wireless network illustrated in
The wireless network may comprise and/or interface with any type of communication, telecommunication, data, cellular, and/or radio network or other similar type of system. In some embodiments, the wireless network may be configured to operate according to specific standards or other types of predefined rules or procedures. Thus, particular embodiments of the wireless network may implement communication standards, such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and/or other suitable 2G, 3G, 4G, or 5G standards; wireless local area network (WLAN) standards, such as the IEEE 802.11 standards; and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave and/or ZigBee standards.
Network 2306 may comprise one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTNs), packet data networks, optical networks, wide-area networks (WANs), local area networks (LANs), wireless local area networks (WLANs), wired networks, wireless networks, metropolitan area networks, and other networks to enable communication between devices.
Network node 2360 and WD 2310 comprise various components described in more detail below. These components work together in order to provide network node and/or wireless device functionality, such as providing wireless connections in a wireless network. In different embodiments, the wireless network may comprise any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections.
As used herein, network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a wireless device and/or with other network nodes or equipment in the wireless network to enable and/or provide wireless access to the wireless device and/or to perform other functions (e.g., administration) in the wireless network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)). Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and may then also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and/or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such 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). Yet further examples of network nodes include multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell/multicast coordination entities (MCEs), core network nodes (e.g., MSCs, MMEs), O&M nodes, OSS nodes, SON nodes, positioning nodes (e.g., E-SMLCs), and/or MDTs. As another example, a network node may be a virtual network node as described in more detail below. More generally, however, network nodes may represent any suitable device (or group of devices) capable, configured, arranged, and/or operable to enable and/or provide a wireless device with access to the wireless network or to provide some service to a wireless device that has accessed the wireless network.
In
Similarly, network node 2360 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which network node 2360 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeB's. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, network node 2360 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate device readable medium 2380 for the different RATs) and some components may be reused (e.g., the same antenna 2362 may be shared by the RATs).
Network node 2360 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 2360, such as, for example, GSM, WCDMA, LTE, NR, WiFi, 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 2360.
Processing circuitry 2370 is configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being provided by a network node. These operations performed by processing circuitry 2370 may include processing information obtained by processing circuitry 2370 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.
Processing circuitry 2370 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 network node 2360 components, such as device readable medium 2380, network node 2360 functionality. For example, processing circuitry 2370 may execute instructions stored in device readable medium 2380 or in memory within processing circuitry 2370. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, processing circuitry 2370 may include a system on a chip (SOC).
In some embodiments, processing circuitry 2370 may include one or more of radio frequency (RF) transceiver circuitry 2372 and baseband processing circuitry 2374. In some embodiments, radio frequency (RF) transceiver circuitry 2372 and baseband processing circuitry 2374 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 2372 and baseband processing circuitry 2374 may be on the same chip or set of chips, boards, or units.
In certain embodiments, some or all of the functionality described herein as being provided by a network node, base station, eNB or other such network device may be performed by processing circuitry 2370 executing instructions stored on device readable medium 2380 or memory within processing circuitry 2370. In alternative embodiments, some or all of the functionality may be provided by processing circuitry 2370 without executing instructions stored on a separate or discrete device readable medium, such as in a hard-wired manner. In any of those embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry 2370 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 2370 alone or to other components of network node 2360, but are enjoyed by network node 2360 as a whole, and/or by end users and the wireless network generally.
Device readable medium 2380 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 processing circuitry 2370. Device readable medium 2380 may store any suitable instructions, data or information, including a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry 2370 and, utilized by network node 2360. Device readable medium 2380 may be used to store any calculations made by processing circuitry 2370 and/or any data received via interface 2390. In some embodiments, processing circuitry 2370 and device readable medium 2380 may be considered to be integrated.
Interface 2390 is used in the wired or wireless communication of signalling and/or data between network node 2360, network 2306, and/or WDs 2310. As illustrated, interface 2390 comprises port(s)/terminal(s) 2394 to send and receive data, for example to and from network 2306 over a wired connection. Interface 2390 also includes radio front end circuitry 2392 that may be coupled to, or in certain embodiments a part of, antenna 2362. Radio front end circuitry 2392 comprises filters 2398 and amplifiers 2396. Radio front end circuitry 2392 may be connected to antenna 2362 and processing circuitry 2370. Radio front end circuitry may be configured to condition signals communicated between antenna 2362 and processing circuitry 2370. Radio front end circuitry 2392 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry 2392 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 2398 and/or amplifiers 2396. The radio signal may then be transmitted via antenna 2362. Similarly, when receiving data, antenna 2362 may collect radio signals which are then converted into digital data by radio front end circuitry 2392. The digital data may be passed to processing circuitry 2370. In other embodiments, the interface may comprise different components and/or different combinations of components.
In certain alternative embodiments, network node 2360 may not include separate radio front end circuitry 2392, instead, processing circuitry 2370 may comprise radio front end circuitry and may be connected to antenna 2362 without separate radio front end circuitry 2392. Similarly, in some embodiments, all or some of RF transceiver circuitry 2372 may be considered a part of interface 2390. In still other embodiments, interface 2390 may include one or more ports or terminals 2394, radio front end circuitry 2392, and RF transceiver circuitry 2372, as part of a radio unit (not shown), and interface 2390 may communicate with baseband processing circuitry 2374, which is part of a digital unit (not shown).
Antenna 2362 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. Antenna 2362 may be coupled to radio front end circuitry 2390 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In some embodiments, antenna 2362 may comprise one or more omni-directional, sector or panel antennas operable to transmit/receive radio signals between, for example, 2 GHZ and 66 GHZ. An omni-directional antenna may be used to transmit/receive radio signals in any direction, a sector antenna may be used to transmit/receive radio signals from devices within a particular area, and a panel antenna may be a line of sight antenna used to transmit/receive radio signals in a relatively straight line. In some instances, the use of more than one antenna may be referred to as MIMO. In certain embodiments, antenna 2362 may be separate from network node 2360 and may be connectable to network node 2360 through an interface or port.
Antenna 2362, interface 2390, and/or processing circuitry 2370 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by a network node. Any information, data and/or signals may be received from a wireless device, another network node and/or any other network equipment. Similarly, antenna 2362, interface 2390, and/or processing circuitry 2370 may be configured to perform any transmitting operations described herein as being performed by a network node. Any information, data and/or signals may be transmitted to a wireless device, another network node and/or any other network equipment.
Power circuitry 2387 may comprise, or be coupled to, power management circuitry and is configured to supply the components of network node 2360 with power for performing the functionality described herein. Power circuitry 2387 may receive power from power source 2386. Power source 2386 and/or power circuitry 2387 may be configured to provide power to the various components of network node 2360 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). Power source 2386 may either be included in, or external to, power circuitry 2387 and/or network node 2360. For example, network node 2360 may be connectable to an external power source (e.g., an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry 2387. As a further example, power source 2386 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry 2387. The battery may provide backup power should the external power source fail. Other types of power sources, such as photovoltaic devices, may also be used.
Alternative embodiments of network node 2360 may include additional components beyond those shown in
As used herein, wireless device (WD) refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other wireless devices. Unless otherwise noted, the term WD may be used interchangeably herein with user equipment (UE). Communicating wirelessly may involve transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information through air. In some embodiments, a WD may be configured to transmit and/or receive information without direct human interaction. For instance, a WD may be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the network. Examples of a WD include, but are not limited to, a smart phone, a mobile phone, a cell phone, a voice over IP (VOIP) phone, a wireless local loop phone, a desktop computer, a personal digital assistant (PDA), a wireless cameras, a gaming console or device, a music storage device, a playback appliance, a wearable terminal device, a wireless endpoint, a mobile station, a tablet, a laptop, a laptop-embedded equipment (LEE), a laptop-mounted equipment (LME), a smart device, a wireless customer-premise equipment (CPE). a vehicle-mounted wireless terminal device, etc. A WD may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-everything (V2X) and may in this case be referred to as a D2D communication device. As yet another specific example, in an Internet of Things (IOT) scenario, a WD may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another WD and/or a network node. The WD may in this case be a machine-to-machine (M2M) device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the WD may be a UE implementing the 3GPP narrow band internet of things (NB-IOT) standard. Particular examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, or home or personal appliances (e.g. refrigerators, televisions, etc.) personal wearables (e.g., watches, fitness trackers, etc.). In other scenarios, a WD may represent a vehicle or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation. A WD as described above may represent the endpoint of a wireless connection, in which case the device may be referred to as a wireless terminal. Furthermore, a WD as described above may be mobile, in which case it may also be referred to as a mobile device or a mobile terminal.
As illustrated, wireless device 2310 includes antenna 2311, interface 2314, processing circuitry 2320, device readable medium 2330, user interface equipment 2332, auxiliary equipment 2334, power source 2336 and power circuitry 2337. WD 2310 may include multiple sets of one or more of the illustrated components for different wireless technologies supported by WD 2310, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, just to mention a few. These wireless technologies may be integrated into the same or different chips or set of chips as other components within WD 2310.
Antenna 2311 may include one or more antennas or antenna arrays, configured to send and/or receive wireless signals, and is connected to interface 2314. In certain alternative embodiments, antenna 2311 may be separate from WD 2310 and be connectable to WD 2310 through an interface or port. Antenna 2311, interface 2314, and/or processing circuitry 2320 may be configured to perform any receiving or transmitting operations described herein as being performed by a WD. Any information, data and/or signals may be received from a network node and/or another WD. In some embodiments, radio front end circuitry and/or antenna 2311 may be considered an interface.
As illustrated, interface 2314 comprises radio front end circuitry 2312 and antenna 2311. Radio front end circuitry 2312 comprise one or more filters 2318 and amplifiers 2316. Radio front end circuitry 2314 is connected to antenna 2311 and processing circuitry 2320, and is configured to condition signals communicated between antenna 2311 and processing circuitry 2320. Radio front end circuitry 2312 may be coupled to or a part of antenna 2311. In some embodiments, WD 2310 may not include separate radio front end circuitry 2312; rather, processing circuitry 2320 may comprise radio front end circuitry and may be connected to antenna 2311. Similarly, in some embodiments, some or all of RF transceiver circuitry 2322 may be considered a part of interface 2314. Radio front end circuitry 2312 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry 2312 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 2318 and/or amplifiers 2316. The radio signal may then be transmitted via antenna 2311. Similarly, when receiving data, antenna 2311 may collect radio signals which are then converted into digital data by radio front end circuitry 2312. The digital data may be passed to processing circuitry 2320. In other embodiments, the interface may comprise different components and/or different combinations of components.
Processing circuitry 2320 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 WD 2310 components, such as device readable medium 2330, WD 2310 functionality. Such functionality may include providing any of the various wireless features or benefits discussed herein. For example, processing circuitry 2320 may execute instructions stored in device readable medium 2330 or in memory within processing circuitry 2320 to provide the functionality disclosed herein.
As illustrated, processing circuitry 2320 includes one or more of RF transceiver circuitry 2322, baseband processing circuitry 2324, and application processing circuitry 2326. In other embodiments, the processing circuitry may comprise different components and/or different combinations of components. In certain embodiments processing circuitry 2320 of WD 2310 may comprise a SOC. In some embodiments, RF transceiver circuitry 2322, baseband processing circuitry 2324, and application processing circuitry 2326 may be on separate chips or sets of chips. In alternative embodiments, part or all of baseband processing circuitry 2324 and application processing circuitry 2326 may be combined into one chip or set of chips, and RF transceiver circuitry 2322 may be on a separate chip or set of chips. In still alternative embodiments, part or all of RF transceiver circuitry 2322 and baseband processing circuitry 2324 may be on the same chip or set of chips, and application processing circuitry 2326 may be on a separate chip or set of chips. In yet other alternative embodiments, part or all of RF transceiver circuitry 2322, baseband processing circuitry 2324, and application processing circuitry 2326 may be combined in the same chip or set of chips. In some embodiments, RF transceiver circuitry 2322 may be a part of interface 2314. RF transceiver circuitry 2322 may condition RF signals for processing circuitry 2320.
In certain embodiments, some or all of the functionality described herein as being performed by a WD may be provided by processing circuitry 2320 executing instructions stored on device readable medium 2330, which in certain embodiments may be a computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by processing circuitry 2320 without executing instructions stored on a separate or discrete device readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry 2320 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 2320 alone or to other components of WD 2310, but are enjoyed by WD 2310 as a whole, and/or by end users and the wireless network generally.
Processing circuitry 2320 may be configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being performed by a WD. These operations, as performed by processing circuitry 2320, may include processing information obtained by processing circuitry 2320 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by WD 2310, 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.
Device readable medium 2330 may be operable to store a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry 2320. Device readable medium 2330 may include computer memory (e.g., Random Access Memory (RAM) or Read Only Memory (ROM)), mass storage media (e.g., a hard disk), removable storage media (e.g., 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 processing circuitry 2320. In some embodiments, processing circuitry 2320 and device readable medium 2330 may be considered to be integrated.
User interface equipment 2332 may provide components that allow for a human user to interact with WD 2310. Such interaction may be of many forms, such as visual, audial, tactile, etc. User interface equipment 2332 may be operable to produce output to the user and to allow the user to provide input to WD 2310. The type of interaction may vary depending on the type of user interface equipment 2332 installed in WD 2310. For example, if WD 2310 is a smart phone, the interaction may be via a touch screen; if WD 2310 is a smart meter, the interaction may be through a screen that provides usage (e.g., the number of gallons used) or a speaker that provides an audible alert (e.g., if smoke is detected). User interface equipment 2332 may include input interfaces, devices and circuits, and output interfaces, devices and circuits. User interface equipment 2332 is configured to allow input of information into WD 2310, and is connected to processing circuitry 2320 to allow processing circuitry 2320 to process the input information. User interface equipment 2332 may include, for example, a microphone, a proximity or other sensor, keys/buttons, a touch display, one or more cameras, a USB port, or other input circuitry. User interface equipment 2332 is also configured to allow output of information from WD 2310, and to allow processing circuitry 2320 to output information from WD 2310. User interface equipment 2332 may include, for example, a speaker, a display, vibrating circuitry, a USB port, a headphone interface, or other output circuitry. Using one or more input and output interfaces, devices, and circuits, of user interface equipment 2332, WD 2310 may communicate with end users and/or the wireless network, and allow them to benefit from the functionality described herein.
Auxiliary equipment 2334 is operable to provide more specific functionality which may not be generally performed by WDs. This may comprise specialized sensors for doing measurements for various purposes, interfaces for additional types of communication such as wired communications etc. The inclusion and type of components of auxiliary equipment 2334 may vary depending on the embodiment and/or scenario.
Power source 2336 may, in some embodiments, be in the form of a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic devices or power cells, may also be used. WD 2310 may further comprise power circuitry 2337 for delivering power from power source 2336 to the various parts of WD 2310 which need power from power source 2336 to carry out any functionality described or indicated herein. Power circuitry 2337 may in certain embodiments comprise power management circuitry. Power circuitry 2337 may additionally or alternatively be operable to receive power from an external power source; in which case WD 2310 may be connectable to the external power source (such as an electricity outlet) via input circuitry or an interface such as an electrical power cable. Power circuitry 2337 may also in certain embodiments be operable to deliver power from an external power source to power source 2336. This may be, for example, for the charging of power source 2336. Power circuitry 2337 may perform any formatting, converting, or other modification to the power from power source 2336 to make the power suitable for the respective components of WD 2310 to which power is supplied.
In
In
In the depicted embodiment, input/output interface 2405 may be configured to provide a communication interface to an input device, output device, or input and output device. UE 2400 may be configured to use an output device via input/output interface 2405. An output device may use the same type of interface port as an input device. For example, a USB port may be used to provide input to and output from UE 2400. The output device may be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. UE 2400 may be configured to use an input device via input/output interface 2405 to allow a user to capture information into UE 2400. The input device may include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, another like sensor, or any combination thereof. For example, the input device may be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor.
In
RAM 2417 may be configured to interface via bus 2402 to processing circuitry 2401 to provide storage or caching of data or computer instructions during the execution of software programs such as the operating system, application programs, and device drivers. ROM 2419 may be configured to provide computer instructions or data to processing circuitry 2401. For example, ROM 2419 may be configured to store invariant low-level system code or data for basic system functions such as basic input and output (I/O), startup, or reception of keystrokes from a keyboard that are stored in a non-volatile memory. Storage medium 2421 may be configured to include memory such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, floppy disks, hard disks, removable cartridges, or flash drives. In one example, storage medium 2421 may be configured to include operating system 2423, application program 2425 such as a web browser application, a widget or gadget engine or another application, and data file 2427. Storage medium 2421 may store, for use by UE 2400, any of a variety of various operating systems or combinations of operating systems.
Storage medium 2421 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), floppy disk drive, 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 a subscriber identity module or a removable user identity (SIM/RUIM) module, other memory, or any combination thereof. Storage medium 2421 may allow UE 2400 to access computer-executable instructions, application programs or the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied in storage medium 2421, which may comprise a device readable medium.
In
In the illustrated embodiment, the communication functions of communication subsystem 2431 may include data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. For example, communication subsystem 2431 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. Network 2443b may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network 2443b may be a cellular network, a Wi-Fi network, and/or a near-field network. Power source 2413 may be configured to provide alternating current (AC) or direct current (DC) power to components of UE 2400.
The features, benefits and/or functions described herein may be implemented in one of the components of UE 2400 or partitioned across multiple components of UE 2400. Further, the features, benefits, and/or functions described herein may be implemented in any combination of hardware, software or firmware. In one example, communication subsystem 2431 may be configured to include any of the components described herein. Further, processing circuitry 2401 may be configured to communicate with any of such components over bus 2402. In another example, any of such components may be represented by program instructions stored in memory that when executed by processing circuitry 2401 perform the corresponding functions described herein. In another example, the functionality of any of such components may be partitioned between processing circuitry 2401 and communication subsystem 2431. In another example, the non-computationally intensive functions of any of such components may be implemented in software or firmware and the computationally intensive functions may be implemented in hardware.
In some embodiments, some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments 2500 hosted by one or more of hardware nodes 2530. Further, in embodiments in which the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node), then the network node may be entirely virtualized.
The functions may be implemented by one or more applications 2520 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operative to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein. Applications 2520 are run in virtualization environment 2500 which provides hardware 2530 comprising processing circuitry 2560 and memory 2590. Memory 2590 contains instructions 2595 executable by processing circuitry 2560 whereby application 2520 is operative to provide one or more of the features, benefits, and/or functions disclosed herein.
Virtualization environment 2500, comprises general-purpose or special-purpose network hardware devices 2530 comprising a set of one or more processors or processing circuitry 2560, which may be commercial off-the-shelf (COTS) processors, dedicated Application Specific Integrated Circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or special purpose processors. Each hardware device may comprise memory 2590-1 which may be non-persistent memory for temporarily storing instructions 2595 or software executed by processing circuitry 2560. Each hardware device may comprise one or more network interface controllers (NICs) 2570, also known as network interface cards, which include physical network interface 2580. Each hardware device may also include non-transitory, persistent, machine-readable storage media 2590-2 having stored therein software 2595 and/or instructions executable by processing circuitry 2560. Software 2595 may include any type of software including software for instantiating one or more virtualization layers 2550 (also referred to as hypervisors), software to execute virtual machines 2540 as well as software allowing it to execute functions, features and/or benefits described in relation with some embodiments described herein.
Virtual machines 2540, comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 2550 or hypervisor. Different embodiments of the instance of virtual appliance 2520 may be implemented on one or more of virtual machines 2540, and the implementations may be made in different ways.
During operation, processing circuitry 2560 executes software 2595 to instantiate the hypervisor or virtualization layer 2550, which may sometimes be referred to as a virtual machine monitor (VMM). Virtualization layer 2550 may present a virtual operating platform that appears like networking hardware to virtual machine 2540. As shown in
Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.
In the context of NFV, virtual machine 2540 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 virtual machines 2540, and that part of hardware 2530 that executes that virtual machine, be it hardware dedicated to that virtual machine and/or hardware shared by that virtual machine with others of the virtual machines 2540, forms a separate virtual network elements (VNE).
Still in the context of NFV, Virtual Network Function (VNF) is responsible for handling specific network functions that run in one or more virtual machines 2540 on top of hardware networking infrastructure 2530 and corresponds to application 2520 in
In some embodiments, one or more radio units 25200 that each include one or more transmitters 25220 and one or more receivers 25210 may be coupled to one or more antennas 25225. Radio units 25200 may communicate directly with hardware nodes 2530 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 signalling can be effected with the use of control system 25230 which may alternatively be used for communication between the hardware nodes 2530 and radio units 25200.
With reference to
Telecommunication network 2610 is itself connected to host computer 2630, which may be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server or as processing resources in a server farm. Host computer 2630 may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider. Connections 2621 and 2622 between telecommunication network 2610 and host computer 2630 may extend directly from core network 2614 to host computer 2630 or may go via an optional intermediate network 2620. Intermediate network 2620 may be one of, or a combination of more than one of, a public, private or hosted network; intermediate network 2620, if any, may be a backbone network or the Internet; in particular, intermediate network 2620 may comprise two or more sub-networks (not shown).
The communication system of
Example implementations, in accordance with an embodiment, of the UE, base station and host computer discussed in the preceding paragraphs will now be described with reference to
Communication system 2700 further includes base station 2720 provided in a telecommunication system and comprising hardware 2725 enabling it to communicate with host computer 2710 and with UE 2730. Hardware 2725 may include communication interface 2726 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of communication system 2700, as well as radio interface 2727 for setting up and maintaining at least wireless connection 2770 with UE 2730 located in a coverage area (not shown in
Communication system 2700 further includes UE 2730 already referred to. Its hardware 2735 may include radio interface 2737 configured to set up and maintain wireless connection 2770 with a base station serving a coverage area in which UE 2730 is currently located. Hardware 2735 of UE 2730 further includes processing circuitry 2738, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. UE 2730 further comprises software 2731, which is stored in or accessible by UE 2730 and executable by processing circuitry 2738. Software 2731 includes client application 2732. Client application 2732 may be operable to provide a service to a human or non-human user via UE 2730, with the support of host computer 2710. In host computer 2710, an executing host application 2712 may communicate with the executing client application 2732 via OTT connection 2750 terminating at UE 2730 and host computer 2710. In providing the service to the user, client application 2732 may receive request data from host application 2712 and provide user data in response to the request data. OTT connection 2750 may transfer both the request data and the user data. Client application 2732 may interact with the user to generate the user data that it provides.
It is noted that host computer 2710, base station 2720 and UE 2730 illustrated in
In
Wireless connection 2770 between UE 2730 and base station 2720 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to UE 2730 using OTT connection 2750, in which wireless connection 2770 forms the last segment. More precisely, the teachings of these embodiments may improve the traffic and resource management in the radio access network and thereby provide benefits such as reduced user waiting time, relaxed restriction on file sizes, better responsiveness, improved user experience, etc.
A measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring OTT connection 2750 between host computer 2710 and UE 2730, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring OTT connection 2750 may be implemented in software 2711 and hardware 2715 of host computer 2710 or in software 2731 and hardware 2735 of UE 2730, or both. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which OTT connection 2750 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software 2711, 2731 may compute or estimate the monitored quantities. The reconfiguring of OTT connection 2750 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect base station 2720, and it may be unknown or imperceptible to base station 2720. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling facilitating host computer 2710's measurements of throughput, propagation times, latency and the like. The measurements may be implemented in that software 2711 and 2731 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using OTT connection 2750 while it monitors propagation times, errors etc.
In step 2820, the host computer initiates a transmission carrying the user data to the UE. In step 2830 (which may be optional), the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 2840 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.
The methods of the present disclosure may be implemented in hardware, or as software modules running on one or more processors. The methods may also be carried out according to the instructions of a computer program, and the present disclosure also provides a computer readable medium having stored thereon a program for carrying out any of the methods described herein. A computer program embodying the disclosure may be stored on a computer readable medium, or it could, for example, be in the form of a signal such as a downloadable data signal provided from an Internet website, or it could be in any other form.
It should be noted that the above-mentioned examples illustrate rather than limit the disclosure, and that those skilled in the art will be able to design many alternative embodiments without departing from the scope of the appended claims or embodiments. The word “comprising” does not exclude the presence of elements or steps other than those listed in a claim or embodiment, “a” or “an” does not exclude a plurality, and a single processor or other unit may fulfil the functions of several units recited in the claims or embodiments. Any reference signs in the claims or embodiments shall not be construed so as to limit their scope.
The following are certain enumerated embodiments further illustrating various aspects the disclosed subject matter.
1. A computer implemented method (400) for managing resources in a Radio Access Network, RAN, of a communication network, the method, performed by a first node in the RAN, comprising:
2. The method of embodiment 1, wherein resource status information (701) describing usage of RAN resources controlled by the second node comprises at least one of the metrics:
3. The method of embodiment 2, wherein predicted resource status information describing predicted usage of RAN resources controlled by the second node comprises at least one of:
4. The method of embodiment 2 or 3, wherein resource status information and predicted resource status information are assembled according to at least one of the criteria:
5. The method of any one of embodiments 1 to 4, wherein predicting, based on the obtained record, resource status information describing usage of RAN resources controlled by the second node during a future time period comprises:
6. The method of any one of embodiments 1 to 5, wherein obtaining a record of resource status information describing usage, during a historical time period, of RAN resources controlled by a second node in the RAN comprises:
7. The method of any one of embodiments 1 to 6, further comprising sending to the second node a request for the record of resource status information (704).
8. The method of embodiment 7, further comprising:
9 The method of embodiment 8, wherein the acknowledgement indicates at least one of (706a):
10. The method of any one of embodiments 1 to 9, further comprising:
11. The method of embodiment 10, when dependent on embodiment 7, wherein sending to the second node a request for the record of resource status information comprises:
12. The method of embodiment 10 or 11, wherein the request for a representation of predicted resource status information describing usage of RAN resources controlled by the second node comprises:
13. The method of any one of embodiments 10 to 12, wherein the request for a representation of predicted resource status information describing usage of RAN resources controlled by the second node comprises at least one of (702b):
14 The method of embodiment 13, wherein the specification of resource status information metrics to be predicted comprise any one or more of the metrics listed in embodiment 2 or embodiment 3 (702c).
15. The method of any one of embodiments 10 to 14, further comprising:
sending to the third node an acknowledgement of the request for a representation of predicted resource status information describing usage of RAN resources controlled by the second node (710).
16. The method of embodiment 15, when dependent on embodiment 8 or 9, further comprising:
17. The method of any one of embodiments 1 to 16, wherein sending, to the third node, a representation of the predicted resource status information describing usage of RAN resources controlled by the second node comprises:
18. The method of any one of embodiments 1 to 17, wherein the representation of the predicted resource status information describing usage of RAN resources controlled by the second node comprises a change from a previously predicted value of a resource status information metric (740a).
19. The method of any one of embodiments 1 to 17, further comprising:
20. The method of any one of embodiments 1 to 18, further comprising:
21. The method of embodiment 20, further comprising:
22. The method of any one of embodiments 1 to 21, wherein predicting, based on the obtained record, resource status information describing usage of RAN resources controlled by the second node and during a future time period comprises using a Machine Learning, ML, process to predict the resource status information (730).
23. The method of any embodiment 22, wherein using an ML process to predict, based on the obtained record, resource status information describing usage of RAN resources controlled by the second node and during a future time period comprises using at least one of (730a):
24. The method of any one of embodiments 1 to 23, wherein the second node is a neighbor of the first node, such that a signaling connection is established between the first node and second node (704b).
25. The method of any one of embodiments 1 to 24, wherein using the predicted resource status information describing usage of RAN resources controlled by the second node in a process relating to management of RAN resources controlled by the first node comprises:
26. The method of any one of embodiments 1 to 25, wherein at least one of the first, second or third nodes comprises at least one of:
27. A computer implemented method (500) for managing resources in a Radio Access Network, RAN, of a communication network, the method, performed by a third node in the RAN, comprising:
28. The method of embodiment 27, wherein predicted resource status information describing predicted usage of RAN resources controlled by the second node comprises at least one of:
29. The method of embodiment 28, wherein the predicted resource status information is assembled according to at least one of the criteria:
30. The method of any one of embodiments 27 to 29, further comprising:
31. The method of embodiment 30, wherein the request for a representation of predicted resource status information describing usage of RAN resources controlled by the second node comprises:
32. The method of embodiment 31, further comprising:
33. The method of any one of embodiments 30 to 32, wherein the request for a representation of predicted resource status information describing usage of RAN resources controlled by the second node comprises at least one of (804c):
34 The method of embodiment 33, wherein the specification of resource status information metrics to be predicted comprise any one or more of the metrics listed in embodiment 28 (804d).
35. The method of any one of embodiments 30 to 34, further comprising:
36. The method of embodiment 35, wherein the acknowledgement includes at least one of (806a):
37. The method of any one of embodiments 27 to 36, wherein the representation of the predicted resource status information describing usage of RAN resources controlled by the second node comprises a change from a previously predicted value of a resource status information metric (810a).
38. The method of any one of embodiments 27 to 37, wherein the second node is a neighbor of the first node, such that a signaling connection is established between the first node and second node (804a).
39. The method of any one of embodiments 27 to 38, wherein using the predicted resource status information describing usage of RAN resources controlled by the second node in a process relating to management of RAN resources controlled by the third node comprises:
40. The method of any one of embodiments 27 to 39, wherein at least one of the first, second or third nodes comprises at least one of:
41. The method of any of the previous embodiments, further comprising:
42. A computer program product comprising a computer readable medium, the computer readable medium having computer readable code embodied therein, the computer readable code being configured such that, on execution by a suitable computer or processor, the computer or processor is caused to perform a method as claimed in any one of claims 1 to 41.
43. A first node (1900) in a communication network comprising a Radio Access Network, RAN, the first node being configured to manage resources in the Radio Access Network, RAN, whereby the first node is configured to:
44. The first node of embodiment 43, wherein the first node is further configured to perform the steps of any one of embodiments 2 to 26 or 41.
45. A third node (2100) in a communication network comprising a Radio Access Network, RAN, the third node being configured to manage resources in the Radio Access Network, RAN, whereby the third node is configured to:
46. The third node of embodiment 45, wherein the third node is further configured to perform the steps of any one of embodiments 28 to 41.
47. A first node for managing resources in a Radio Access Network, RAN, of a communication network, the first node comprising:
48. A second node for managing resources in a Radio Access Network, RAN, of a communication network, the second node comprising:
49. A communication system including a host computer comprising:
50. The communication system of the previous embodiment further including the radio access node.
51. The communication system of the previous 2 embodiments, further including the UE, wherein the UE is configured to communicate with the radio access node.
52. The communication system of the previous 3 embodiments, wherein:
53. A method implemented in a communication system including a host computer, a radio access node and a user equipment (UE), the method comprising:
54. The method of the previous embodiment, further comprising, at the radio access node, transmitting the user data.
55. The method of the previous 2 embodiments, wherein the user data is provided at the host computer by executing a host application, the method further comprising, at the UE, executing a client application associated with the host application.
56. A user equipment (UE) configured to communicate with a radio access node, the UE comprising a radio interface and processing circuitry configured to performs the steps of the previous 3 embodiments.
57. A communication system including a host computer comprising a communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a radio access node, wherein the radio access node comprises a radio interface and processing circuitry, the radio access node's processing circuitry configured to perform any of the steps of any of embodiments 1 to 41.
58. The communication system of the previous embodiment further including the radio access node.
59. The communication system of the previous 2 embodiments, further including the UE, wherein the UE is configured to communicate with the radio access node.
60. The communication system of the previous 3 embodiments, wherein:
| Filing Document | Filing Date | Country | Kind |
|---|---|---|---|
| PCT/EP2022/061040 | 4/26/2022 | WO |
| Number | Date | Country | |
|---|---|---|---|
| 63180733 | Apr 2021 | US |
