WO2020204779A1 - Distribution d'informations d'état de réseau de transport pour amélioration de procédure ran - Google Patents

Distribution d'informations d'état de réseau de transport pour amélioration de procédure ran Download PDF

Info

Publication number
WO2020204779A1
WO2020204779A1 PCT/SE2020/050242 SE2020050242W WO2020204779A1 WO 2020204779 A1 WO2020204779 A1 WO 2020204779A1 SE 2020050242 W SE2020050242 W SE 2020050242W WO 2020204779 A1 WO2020204779 A1 WO 2020204779A1
Authority
WO
WIPO (PCT)
Prior art keywords
transport network
node
performance information
transport
network performance
Prior art date
Application number
PCT/SE2020/050242
Other languages
English (en)
Inventor
Angelo Centonza
Gino Masini
Giovanni Fiaschi
Pablo SOLDATI
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Publication of WO2020204779A1 publication Critical patent/WO2020204779A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0823—Configuration setting characterised by the purposes of a change of settings, e.g. optimising configuration for enhancing reliability
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5003—Managing SLA; Interaction between SLA and QoS
    • H04L41/5019—Ensuring fulfilment of SLA
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/04—Interfaces between hierarchically different network devices
    • H04W92/12—Interfaces between hierarchically different network devices between access points and access point controllers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/16—Interfaces between hierarchically similar devices
    • H04W92/20—Interfaces between hierarchically similar devices between access points

Definitions

  • the present disclosure generally relates to the field of wireless network communications, and more particularly, to radio access network (RAN) nodes that determine and signal transport network performance information.
  • RAN radio access network
  • the fifth-generation (5G) radio access network (RAN) under development by members of the 3 rd -Generation Partnership Project (3GPP) is sometimes referred to as“NR,” or“New Radio,” and is referred to herein as“NG-RAN.”
  • the NG-RAN architecture is shown in a simplified form in Figure 1 and is described in 3GPP TS 38.401, vl5.4.0.
  • the NG-RAN consists of a set of gNBs connected to the 5GC through the NG interface.
  • a gNB can support frequency division duplex (FDD) mode, time division duplex (TDD) mode or dual mode operation.
  • gNBs can be interconnected through the Xn interface.
  • a gNB may consist of a gNB central unit (gNB-CU) and gNB distributed units (gNB-DUs).
  • gNB-CU and a gNB-DU are connected via an FI logical interface.
  • One gNB-DU generally is connected to only one gNB-CU.
  • a gNB-DU may be connected to multiple gNB- CUs by appropriate implementation.
  • NG, Xn and FI are logical interfaces.
  • the NG-RAN is layered into a Radio Network Layer (RNL) and a Transport Network Layer (TNL).
  • RNL Radio Network Layer
  • TNL Transport Network Layer
  • the NG-RAN architecture i.e., the NG-RAN logical nodes and interfaces between them, is defined as part of the RNL.
  • NG, Xn, FI For each NG-RAN interface (NG, Xn, FI), 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 a Long Term Evolution (LTE) eNB via the X2 interface.
  • LTE Long Term Evolution
  • EPC Evolved Packet Core
  • nr-gNB a so called nr-gNB.
  • the latter is a gNB not connected directly to a core network (CN) but connected via X2 to an eNB for the sole purpose of performing dual connectivity.
  • a gNB may be connected to an eNB via an Xn interface. In this option, both the gNB and the eNB are connected to the 5GC and can communicate over the Xn interface.
  • RAN nodes can communicate not only via direct interfaces such as the X2 and Xn but also via CN interfaces such as the NG and SI interfaces. Such communication requires the involvement of CN nodes and/or transport nodes (such as IP packet routers, Ethernet switches, microwave links or optical reconfigurable optical add-drop multiplexers (ROADMs)) to route and forward messages from the source RAN node to the target RAN node.
  • transport nodes such as IP packet routers, Ethernet switches, microwave links or optical reconfigurable optical add-drop multiplexers (ROADMs)
  • the architecture in Figure 1 can be expanded by spitting the gNB-CU into two entities, i.e., a gNB-CU-UP, which serves the user plane and hosts the packet data convergence protocol (PDCP) protocol and a gNB-CU-CP, which serves the control plane and hosts the PDCP and RRC protocol.
  • a gNB-DU hosts the radio link control (RLC)/medium access control (MAC)/ and physical layer (PHY) protocols.
  • RLC radio link control
  • MAC medium access control
  • PHY physical layer
  • Handover procedures in RANs are used to change the connection of a user device from a source cell (i.e., the serving cell) to a target cell that can provide better connectivity.
  • Handover decisions from a source cell to a target cell are typically made based on RAN parameters, e.g., by comparing the radio signal strength of source and target cell.
  • a typical measure of signal strength is the reference signal received power (RSRP) measured by the user device of reference signals transmitted by a cell. Therefore, a handover may be triggered when the difference between the RSRP of the target cell and the RSRP of the source cell exceeds a certain threshold.
  • RSRP reference signal received power
  • Network Slicing is a concept to allow differentiated treatment on network equipment that is shared by different customers, depending on each customer’s requirements.
  • MNO Mobile Network Operators
  • SLA Service Level Agreement
  • a network slice always consists of a RAN part and a CN part.
  • the support of network slicing relies on the principle that traffic for different slices is handled by different packet data unit (PDU) sessions, or in other words, by different bearers between the RAN and the CN.
  • PDU packet data unit
  • the network can realize the different network slices by scheduling and also by providing different L1/L2 configurations.
  • a PDU Session creation between the RAN and the CN results in the creation of a DRB (Dedicated Radio Bearer).
  • the DRB is a communication channel established within the RAN and between the RAN and the UE to transfer user plane data to and from a UE.
  • PDU Sessions and DRBs are assigned a network slice identifier named S-NSSAI (Single Network Slice Selection Assistance Information).
  • the concept of network slicing can be extended also to the transport network. Namely, for a given network slice, PDU Sessions and DRBs may be utilized for its channels for data exchange. Such channels are identified by single network slice selection assistance information (S-NSSAI). It is also possible to create a partition of the transport network so that network slice traffic is served with particular and dedicated policies tailored to the network slice services.
  • S-NSSAI single network slice selection assistance information
  • Embodiments of the techniques and apparatus described herein provide for the exchanging and use of richer and more granular information regarding the status of a transport network.
  • the performance in the fronthaul and backhaul transport network may be known on a per radio base station basis at a RAN node. Such performance can be measured directly by the RAN node over the transport interfaces or be received from a transport node.
  • a method is provided for exchanging, between RAN nodes, the transport network status/statistics associated with the (transport) interfaces connecting the RAN nodes or interfaces connecting a RAN node and a core network node.
  • Some embodiments enable a RAN node to optimize one or more RAN functionalities, such as mobility functions (e.g., handover, mobility setting changes, cell reselection, dual or multi connectivity, secondary cell choice, etc.), load shifting and load balance, network slicing, etc., based both on RAN specific parameters and the transport network status information.
  • the transport network status information may be associated with one or more interfaces connecting: the RAN node to another RAN node; a neighboring RAN node to another RAN node; the RAN node to a core network node; and/or a neighboring RAN node to a core network node.
  • a method in a first node of a RAN that serves one or more user wireless devices, includes determining transport network performance information corresponding to each of one or more transport network interfaces between a RAN node and one or more other network nodes.
  • This RAN node may be the first node or another RAN node, in various embodiments.
  • the method also includes signaling the transport network performance information to another node, or performing one or more radio access network management or optimization tasks, based on the transport network performance information, or both.
  • the transport network for the purposes of this method, is defined to include the interfaces and connections for transferring user data between nodes of a radio access network and between a node of a radio access network and another network (such as a core network). While a transport network as defined here may include radio links, it does not include the wireless links between user wireless devices (UEs, MTC devices, etc.) and radio access nodes.
  • UEs user wireless devices
  • MTC devices mobile communications
  • the embodiments described herein enable a smooth intervention of the cell selection function in various procedures (e.g., connection mobility control (CMC) and dual connectivity) of the radio access to mitigate temporary or permanent transport network bottlenecks in a smooth way, to prevent congestions and dynamically adapt to evolving transport network states.
  • CMC connection mobility control
  • Quantitative information on various aspects of the transport network may be used to inform a RAN node or CN node of the current transport network status and performance.
  • Figure 1 illustrates NG-RAN architecture.
  • Figure 2 illustrates an example of signaled information, according to some embodiments.
  • Figure 3 illustrates a signaling diagram for communicating parameters, according to some embodiments.
  • Figure 4 illustrates is a block diagram of a network node, according to some embodiments.
  • Figure 5 illustrates a flowchart illustrating a method in the network node, according to some embodiments.
  • Figure 6 illustrates is a block diagram of a wireless device, according to some embodiments.
  • Figure 7 schematically illustrates a telecommunication network connected via an intermediate network to a host computer, according to some embodiments.
  • Figure 8 is a generalized block diagram of a host computer communicating via a base station with a user equipment over a partially wireless connection, according to some embodiments.
  • Figures 9 to 12 are flowcharts illustrating example methods implemented in a communication system including a host computer, a base station and a user equipment.
  • Figure 13 is a block diagram illustrating a functional implementation of a network node, according to some embodiments.
  • Causes affecting transport network capability may be of various different natures, and include external traffic in dual-use fronthaul and backhaul networks, exceptional events concentrating traffic on a portion of the fronthaul/backhaul network that is not dimensioned for the peaks, and microwave links in bad weather conditions. These conditions may vary over time, and network performance would benefit from smooth, proactive adaptations rather than from sudden reactions to critical situations.
  • the current standards for E-UTRAN define transport network information exchange over the X2 interface, but the specified information is currently too vague to provide a usable indication of the current capabilities.
  • the X2 application protocol (AP) allows for the exchange of the SI TNL Load Indicator per eNB. This indication consists of the following information:
  • the TNL load is indicated in a very imprecise way. This causes ambiguity if a decision on target cells for a UE needs to be made on the basis of an exact knowledge of TNL.
  • a gNB may be split into multiple nodes, e.g., the gNB-CU and the gNB-DU.
  • TNL load is not only related to the load over the RAN to CN interface but also to RAN internal interfaces such as the FI interface or even the El interface, which connects the gNB-CU-CP (portion of the gNB-CU in charge of control plane functions) and the gNB-CU-UP (portion of the gNB- CU in charge of control plane functions).
  • Embodiments of the techniques and apparatus described in detail below provide for the exchanging and use of richer and more granular information regarding the status of a transport network.
  • the performance in the fronthaul and backhaul transport network may be known on a per radio base station basis at a RAN node. Such performance can be measured directly by the RAN node over the transport interfaces or be received from a transport node.
  • a method is provided for exchanging, between RAN nodes, the transport network status/statistics associated with the (transport) interfaces connecting the RAN nodes or interfaces connecting a RAN node and a core network node.
  • Some embodiments enable a RAN node to optimize one or more RAN functionalities, such as mobility functions (e.g., handover, mobility setting changes, cell reselection, dual or multi connectivity, secondary cell choice, etc.), load shifting and load balance, network slicing, etc., based both on RAN specific parameters and the transport network status information.
  • the transport network status information may be associated with one or more interfaces connecting: the RAN node to another RAN node; a neighboring RAN node to another RAN node; the RAN node to a core network node; and/or a neighboring RAN node to a core network node.
  • the NG-RAN supports services with specific requirements on reliability, robustness and latency.
  • One class of such services is named URLLC (Ultra Reliable Low Latency Communication).
  • URLLC Ultra Reliable Low Latency Communication
  • Transport network status may be included in connection mobility control (CMC) information, to keep into account, for example, possible transport network congestion and attaching to cells with a worse radio signal in favor of a better transport path. Values for signal quality and transport network status may be used. Handover may be initiated in the presence of explicit congestion, or in other words, to exclude the cells connected to congested portions of the transport network from the cell selection mechanisms.
  • CMC connection mobility control
  • Embodiments described herein involve sending information about the performance of the fronthaul and backhaul transport network to the radio access nodes responsible for cell selection procedures, to allow for a better quality of experience and resource management considering the overall set of network resources.
  • This information may be used to change the cell selection algorithms (e.g., in CMC and dual connectivity). This allows for proactively and smoothly diverting the traffic towards radio cells connected to transport portions with better capability, if the cells with the best radio signal risk experiencing congestion.
  • Quantitative mathematical formulas may be used. These include configuration parameters to tune the algorithm according to the network characteristics/arrangements and the network operator’s choices.
  • One of the proposed formulas has been successfully tested in several handover simulations, and the formulas exhibit a robust and consistent behavior in all the performed simulations. The results are significantly better than using the normal handover procedures, where clear asymmetries are present (in traffic load or in the transport network). The results are not worse than using the normal procedures, if no asymmetries are present in the scenario.
  • the use of the formulas may be simple enough to be practically implemented in production radio base stations.
  • Embodiments described herein make available, to the radio access network, information regarding the transport network status portions in a quantitative manner. This transport network status information can then be used by RAN procedures to make informed decisions considering not only the radio resource availability but also the quality of the transport connectivity in support of the RAN interfaces.
  • RAN interfaces to be monitored may be backhaul interfaces towards the core network (NG, SI), inter-eNodeB/gNodeB interfaces for coordination or dual connectivity (X2, Xn) and IP fronthaul interfaces for split RAN architecture connectivity (FI, El).
  • NG core network
  • X2, Xn inter-eNodeB/gNodeB interfaces for coordination or dual connectivity
  • FI split RAN architecture connectivity
  • the transport network status information can be expressed in terms of various performance indicators and statistics reflecting the connectivity quality.
  • One of these statistics may be packet loss rate, a basic parameter indicating the raw amount of lost traffic. It can be calculated at the endpoints of the interface by means of dedicated protocols such as sFlow.
  • sFlow dedicated protocols
  • Such a statistic provides an estimate of the robustness and reliability of the transport network. This is very useful for determining whether special services such as URLLC can be admitted to a RAN node served by a given transport - a loss rate that is too high may imply that the URLLC service cannot be admitted to the RAN node. This might play a role in mobility procedures and it might trigger mobility towards a different target RAN node, where the URLLC service could be admitted successfully.
  • Another statistic is bit error rate, as an alternative to packet loss rate. It can be measured at lower layers with more direct means. This provides a similar robustness indication as packet loss rate and can be used for the same purposes.
  • Another statistic is average packet delay, a secondary parameter important for delay-sensitive traffic.
  • One statistic may be packet delay variation, a secondary parameter important for a subset of delay sensitive traffic. Average packet delay and delay variation provide a measure of the performance of the transport network in terms of timely delivery of traffic. Too high a delay and delay variation might mean that special services such as vehicular communication may not be admitted to a RAN node whose transport network is affected by poor delay and delay variation performance. This might play a role in mobility procedures and it might trigger mobility towards a different target RAN node (where the service could be admitted successfully).
  • Another statistic is available bandwidth, which is more complex to calculate but still viable. It would require information about the capacity of all the links along the interface route and all the traffic sent through them. Then, the residual bandwidth on the bottleneck link can be used.
  • the transport network statistics listed above may be exchanged between RAN nodes and/or from a transport node to a RAN node.
  • a gNB-DU may signal to a gNB-CU the above statistics for its serving transport connection.
  • the gNB-DU may directly measure the transport network statistics associated with its interfaces (e.g., the FI interface) or it may first receive such information from a transport node residing between the gNB-DU and the gNB- CU.
  • the gNB-CU upon collecting network transport information associated with the interfaces between the gNB-CU and the connected gNB-CUs, may then signal to another connected gNB-DU the transport network conditions affecting the FI interface of that gNB- DU. This would enable the gNB-DUs controlled by the gNB-CU to optimize their RAN functions (such as mobility, load balancing, network slicing, dual connectivity, etc.) based on both on RAN-specific parameters and the transport network status.
  • RAN functions
  • the gNB-CU may measure or receive, from a transport node, the transport network statistics associated to the interfaces connecting the gNB-CU with a neighbor gNB-CU or eNB, such as Xn or X2 interfaces, respectively. Therefore, the gNB-CU may signal to a neighbor gNB-CU or eNB the transport network conditions affecting its X2 or Xn interface.
  • the gNB-CU may signal to a neighbor gNB-CU or to a neighbor eNB the transport network conditions affecting the X2 and/or Xn interface, plus the transport conditions affecting each FI interface connecting the gNB-CU to its gNB-DUs.
  • the gNB- CU may also signal to a neighbor gNB-CU, to a neighbor eNB or to connected gNB-DUs, the transport network conditions on a per cell basis, where each cell would be associated to a gNB- DU and where the cell transport conditions equal the transport conditions of the transport network connecting the gNB-DU serving the cell to the gNB-CU.
  • the gNB-CU may additionally measure (or receive from a transport node) the transport network status/statistics associated to the interfaces connecting the gNB-CU to a core network node (e.g., the NG interface in the 5G system). Therefore, the gNB-CU may signal to a neighbor gNB-CU or eNB, using common interfaces such as Xn or X2, the transport network conditions affecting its interfaces with nodes in the core network. This information can then be used by the gNB-CUs to establish proper connections and configuration for dual or multi connectivity (i.e., to configure the user device in the RAN network to have two or more connections toward two or more RAN nodes simultaneously).
  • a core network node e.g., the NG interface in the 5G system.
  • the gNB-CU may receive from the core transport network status/statistics information associated to interfaces of a neighbor gNB-CU or eNB.
  • This information may include: transport network status/statistics associated to interfaces between the neighbor gNB-CU and the corresponding gNB-DUs (e.g., FI interfaces); information per cell and or per network slide; transport network status/statistics associated with interfaces between the neighbor gNB-CU and its neighboring gNB-CUs or eNBs; and/or transport network status/statistics associated with interfaces between the neighbor eNB and its neighboring gNB-CUs or eNBs.
  • transport network status/statistics associated to interfaces between the neighbor gNB-CU and the corresponding gNB-DUs e.g., FI interfaces
  • information per cell and or per network slide transport network status/statistics associated with interfaces between the neighbor gNB-CU and its neighboring gNB-CUs or eNBs
  • transport network status/statistics associated to interfaces between the neighbor gNB-CU and its neighboring gNB-CUs or eNBs e.g., FI
  • the gNB-CU can communicate to a neighbor gNB-CU or to a neighbor eNB, the transport network status (namely the set of statistics defined above and specifying the transport network performance) on a per cell basis, where such status represents the cumulative performance over the FI and X2 and/or Xn interface associated to each cell of the gNB-CU.
  • the transport network status namely the set of statistics defined above and specifying the transport network performance
  • the information signaled between RAN nodes may not relate to the entire transport network connecting two RAN nodes, but only to a portion of it, namely the portion that is assigned to serve a specific network slice.
  • the transport network statistics described above may be signaled on a per transport network slice index.
  • Such network transport statistics per network slice may be associated/measured with interfaces between RAN nodes, such as the FI and X2 and/or Xn interfaces, or between a RAN node and a core network node, such as the NG interface in the 5G system.
  • Such an index can be achieved in different ways.
  • such an index may be constituted by a Diff Serve Code Point (DSCP) included in the IP headers of traffic exchanged over the transport between two RAN nodes.
  • DSCP Diff Serve Code Point
  • Such a DSCP may be used for traffic pertaining to a network slice. All traffic marked with such an index will be treated (e.g., at scheduling level) with policies that are specific to the network slice to which the index refers.
  • the transport network slice index is an S-NSSAI.
  • RAN nodes will signal to each other transport network statistics like the ones defined above, on a per S-NSSAI basis. The node receiving such statistics can deduce that the transport network serving the network slice corresponding to the associated S-NSSAI is subject to the signaled condition.
  • An example of how the information may be signaled over a common interface is shown in the table of Figure 2.
  • FIG. 3 illustrates an example message sequence chart with a generic description of the signaling mechanisms for embodiments described herein.
  • one or more of the above parameters shall be communicated from the transport network to the RAN to make resource allocation decisions taking into account the transport status.
  • a RAN node can use this information to optimize one or more RAN functionalities, such as mobility functions (e.g., handover, mobility setting changes, cell reselection, secondary cell selection, etc.), load shifting and load balance, dual or multi connectivity setting, network slicing, etc., based both on RAN specific parameters and the transport network status.
  • mobility functions e.g., handover, mobility setting changes, cell reselection, secondary cell selection, etc.
  • load shifting and load balance e.g., load shifting and load balance, dual or multi connectivity setting, network slicing, etc., based both on RAN specific parameters and the transport network status.
  • the RAN node may determine whether to initiate a handover (HO) procedure based both on RAN specific parameters and the transport network status. In another embodiment, the RAN node may determine whether to initiate an HO procedure based both on RAN specific parameters and the transport network status.
  • HO handover
  • the RAN node may initiate the HO procedure for a user device from a source cell to a target cell if the target cell offers a better signal strength and/or if the transport network status at the target cell is better or equal to the transport network status at the source cell.
  • the second condition requires that the packet loss rate at the target cell should be less or equal to the packet loss rate at the source cell.
  • the handover procedure currently selects the cell with the best RSRP.
  • a simple alternative could be replacing it with RSRP - l ⁇ PLR, where PLR is the packet loss rate and l is a configurable parameter modulating the relative importance of the transport penalty versus the radio signal power.
  • the RAN node could determine the best secondary NB (e.g., SeNB) or secondary cell (i.e., the Scell) to add to the RRC connection of a user device using both RAN specific parameters and the transport network status associated with one or more interface required to establish the new communication link with the user device.
  • This method can be used to add an arbitrary number of communication links between the user device and the access nodes of the RAN.
  • the advantage of this method is that a new communication link would be added not only based on the availability of radio resources at the new RAN node/cell, but also based on the congestion status of the transport network interfaces that would be involved to support the new communication link.
  • C is the link capacity
  • TT the current total throughput on that link
  • the assumption that the RAN interface path is known is reasonable for transport networks with sufficient control of the resources, e.g., if it includes path tracing mechanisms or if it has direct routing control (like in multi -protocol label switching (MPLS) with traffic engineering or in segment routing).
  • MPLS multi -protocol label switching
  • the link capacity value LCV k is given by the following formula: assuming that the cell is connected to the central unit or the packet core with a path R k and that the relevant links in path R k are indicated as Li.
  • a hysteretic link capacity value for a cell where the UE is already attached can be used:
  • H is the hysteretic weight replacing W. H works exactly like W, except for being smaller, which favors the choice of the current cell in the final formulas.
  • the UE measures the radio signal strength or quality (RSRP or RSRQ) for all the reachable cells. This is normally a measurement in dB having a negative value. Then hysteresis may be added to the currently attached cell measurement, to favor it and reduce the handover frequency.
  • the final value for cell k may be indicated with S k. The cell with the highest S k is then selected.
  • D is a damping parameter to mitigate the effect of the transport network status in the final formula.
  • HLCVk can be used in place of LCVk in the above formula if the hysteretic behavior is implemented and k is the serving eNodeB.
  • the capacity and total throughput on all the relevant links affecting the communication from the base stations to the packet core nodes may be collected and used to determine the transport network status in the form of a different penalty for each base station. Then, the value ordinarily used to represent the radio signal characteristics may be divided by the penalty calculated in the transport network.
  • the new algorithm includes three parameters to tune its behavior according to the network characteristics and operator’s choices: W modulates the relative weight of the throughput with respect to the link capacity; H introduces hysteresis in the transport network status; and D modulates the importance of the transport network status with respect to the radio signal characteristics.
  • the parameters W and H must be configured via operation and management in the transport network to allow the LCV k and HLCV k calculations before their communication to the relevant RAN nodes.
  • the LCV k values are exchanged among neighboring RAN nodes.
  • the HLCV k values once communicated by the transport network to the relevant RAN nodes, if used, are consumed locally and do not need to be exchanged via a standardized protocol.
  • the parameter D is configured on the RAN by means of operation and management.
  • Figure 4 shows an example network node 30 that may be configured to carry out one or more of these disclosed techniques.
  • Network node 30 may be an evolved Node B (eNodeB), Node B or gNB.
  • While a network node 30 is shown in Figure 4, the operations can be performed by other kinds of network access nodes, including a radio network node such as base station, radio base station, base transceiver station, base station controller, network controller, NR BS, Multi cell/multicast Coordination Entity (MCE), relay node, access point, radio access point, Remote Radio Unit (RRU) Remote Radio Head (RRH), or a multi-standard BS (MSR BS).
  • a radio network node such as base station, radio base station, base transceiver station, base station controller, network controller, NR BS, Multi cell/multicast Coordination Entity (MCE), relay node, access point, radio access point, Remote Radio Unit (RRU) Remote Radio Head (RRH), or a multi-standard BS (MSR BS).
  • MCE Multi cell/multicast Coordination Entity
  • RRU Remote Radio Unit
  • RRH Remote Radio Head
  • MSR BS multi-standard BS
  • network node 30 will be described as being configured to operate as a first node in the LTE network or NR network.
  • the technique can be implemented in the RRC layer.
  • the RRC layer could be implemented by one or more network nodes in a cloud environment and hence some embodiments can be implemented in a cloud environment.
  • each type of node may be adapted to carry out one or more of the methods and signaling processes described herein, e.g., through the modification of and/or addition of appropriate program instructions for execution by processing circuits 32.
  • Network node 30 facilitates communication between wireless terminals (e.g., UEs), other network access nodes and/or the core network.
  • Network node 30 may include communication interface circuitry 38 that includes circuitry for communicating with other nodes in the core network, radio nodes, and/or other types of nodes in the network for the purposes of providing data and/or cellular communication services.
  • Network node 30 communicates with wireless devices using antennas 34 and transceiver circuitry 36.
  • Transceiver circuitry 36 may include transmitter circuits, receiver circuits, and associated control circuits that are collectively configured to transmit and receive signals according to a radio access technology, for the purposes of providing cellular communication services.
  • Network node 30 also includes one or more processing circuits 32 that are operatively associated with the transceiver circuitry 36 and, in some cases, the communication interface circuitry 38.
  • Processing circuitry 32 comprises one or more digital processors 42, e.g., one or more microprocessors, microcontrollers, Digital Signal Processors (DSPs), Field Programmable Gate Arrays (FPGAs), Complex Programmable Logic Devices (CPLDs), Application Specific Integrated Circuits (ASICs), or any mix thereof. More generally, processing circuitry 32 may comprise fixed circuitry, or programmable circuitry that is specially configured via the execution of program instructions implementing the functionality taught herein, or some mix of fixed and programmed circuitry.
  • Processor 42 may be multi core, i.e., having two or more processor cores utilized for enhanced performance, reduced power consumption, and more efficient simultaneous processing of multiple tasks.
  • Processing circuitry 32 also includes a memory 44.
  • Memory 44 stores one or more computer programs 46 and, optionally, configuration data 48.
  • Memory 44 provides non-transitory storage for the computer program 46 and it may comprise one or more types of computer-readable media, such as disk storage, solid-state memory storage, or any mix thereof.
  • “non-transitory” means permanent, semi-permanent, or at least temporarily persistent storage and encompasses both long-term storage in non-volatile memory and storage in working memory, e.g., for program execution.
  • memory 44 comprises any one or more of SRAM, DRAM, EEPROM, and FLASH memory, which may be in processing circuitry 32 and/or separate from processing circuitry 32.
  • Memory 44 may also store any configuration data 48 used by the network access node 30.
  • Processing circuitry 32 may be configured, e.g., through the use of appropriate program code stored in memory 44, to carry out one or more of the methods and/or signaling processes detailed hereinafter.
  • Network node 30 may be configured to be a network node of a RAN that serves one or more wireless devices.
  • processing circuitry 32 is configured to determine transport network performance information corresponding to each of one or more transport network interfaces between a RAN node (such as itself) and one or more other network nodes and signal the transport network performance information to another network node, or perform one or more radio access network management or optimization tasks, based on the transport network performance information, or both.
  • Processing circuitry 32 may also be configured to perform a corresponding method 500, shown in Figure 5.
  • Method 500 includes determining transport network performance information corresponding to each of one or more transport network interfaces between a RAN node and one or more other nodes (block 502).
  • Method 500 also includes signaling the transport network performance information to another node, or performing one or more radio access network management or optimization tasks, based on the transport network performance information, or both (block 504).
  • the transport network is the interfaces and connections for transferring user data between nodes of a radio access network and between a node of a radio access network and another network (such as a core network).
  • the transport network does not include the wireless links between user wireless devices and RAN nodes.
  • the one or more transport network interfaces may include: an interface connecting the network node to another RAN node; an interface connecting a neighboring RAN node to another RAN node; an interface connecting the network node to a core network node; and/or an interface connecting a neighboring RAN node to a core network node.
  • the transport network performance information may include, for at least one of transport network interfaces, any one or more of the following parameters: packet loss rate; bit error rate; average packet delay; packet delay variation; and available bandwidth.
  • At least one parameter of the determined transport network performance information for at least one of the transport network interfaces may be determined on a per-cell basis for two or more cells associated with the network node and/or on a per-network-slice basis for two or more network slices associated with the network node.
  • performing one or more radio access network management or optimization tasks, based on the transport network performance information comprises configuring connections to the RAN for one or more user wireless devices, based on the transport network performance information.
  • performing one or more radio access network management or optimization tasks, based on the transport network performance information includes configuring or triggering handovers for one or more user wireless devices, based on the transport network performance information.
  • performing one or more radio access network management or optimization tasks, based on the transport network performance information includes configuring dual- or multi -connectivity for one or more user wireless devices, based on the transport network performance information.
  • the node carrying out the method shown in Figure 5, or a similar method may be a distributed unit (DU) of a base station, where determining the transport network performance information for at least one of the transport network interfaces includes measuring all or part of the transport network performance information, and where the DU signals the transport network information to a central unit (CU) of the base station.
  • the node carrying out the method shown in Figure 5, or a similar method may be a CU of a base station, where determining the transport network performance information for at least one of the transport network interfaces includes receiving all or part of the transport network performance information from a DU of the base station and/or from a neighboring CU, and where the CU signals the transport network information to a core network node.
  • FIG. 6 illustrates a diagram of a wireless device 50 configured to perform any actions to support and/or utilize the techniques described above for network node 30, according to some embodiments.
  • Wireless device 50 may be considered to represent any wireless devices or terminals that may operate in a network, such as a UE in a cellular network as in the techniques described above.
  • Other examples may include a communication device, target device, MTC device, IoT device, device to device (D2D) UE, machine type UE or UE capable of machine to machine communication (M2M), a sensor equipped with UE, PDA (personal digital assistant), tablet, IPAD tablet, mobile terminal, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, Customer Premises Equipment (CPE), etc.
  • Wireless device 50 is configured to communicate with a network node or base station in a wide- area cellular network via antennas 54 and transceiver circuitry 56.
  • Transceiver circuitry 56 may include transmitter circuits, receiver circuits, and associated control circuits that are collectively configured to transmit and receive signals according to a radio access technology, for the purposes of using cellular communication services.
  • Wireless device 50 also includes one or more processing circuits 52 that are operatively associated with the radio transceiver circuitry 56.
  • Processing circuitry 52 comprises one or more digital processing circuits, e.g., one or more microprocessors, microcontrollers, DSPs, FPGAs, CPLDs, ASICs, or any mix thereof. More generally, processing circuitry 52 may comprise fixed circuitry, or programmable circuitry that is specially adapted via the execution of program instructions implementing the functionality taught herein, or may comprise some mix of fixed and programmed circuitry. Processing circuitry 52 may be multi-core.
  • Processing circuitry 52 also includes a memory 64.
  • Memory 64 stores one or more computer programs 66 and, optionally, configuration data 68.
  • Memory 64 provides non-transitory storage for computer program 66 and it may comprise one or more types of computer-readable media, such as disk storage, solid-state memory storage, or any mix thereof.
  • memory 64 comprises any one or more of SRAM, DRAM, EEPROM, and FLASH memory, which may be in processing circuitry 52 and/or separate from processing circuitry 52.
  • Memory 64 may also store any configuration data 68 used by wireless device 50.
  • Processing circuitry 52 may be configured, e.g., through the use of appropriate program code stored in memory 64, to carry out one or more of the methods and/or signaling processes detailed hereinafter.
  • Processing circuitry 52 of wireless device 50 is configured, according to some embodiments, to support and/or utilize the operations of network node 30 described above.
  • Figure 7 illustrates a communication system that includes a telecommunication network 710, such as a 3GPP-type cellular network, which comprises an access network 711, such as a radio access network, and a core network 714.
  • the access network 711 comprises a plurality of base stations 712a, 712b, 712c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 713a, 713b, 713c.
  • Each base station 712a, 712b, 712c is connectable to the core network 714 over a wired or wireless connection 715.
  • a first UE 791 located in coverage area 713c is configured to wirelessly connect to, or be paged by, the corresponding base station 712c.
  • a second UE 792 in coverage area 713a is wirelessly connectable to the corresponding base station 712a. While a plurality of UEs 791, 792 are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station 712.
  • the telecommunication network 710 is itself connected to a host computer 730, which may be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server or as processing resources in a server farm.
  • the host computer 730 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.
  • the connections 721, 722 between the telecommunication network 710 and the host computer 730 may extend directly from the core network 714 to the host computer 730 or may go via an optional intermediate network 720.
  • the intermediate network 720 may be one of, or a combination of more than one of, a public, private or hosted network; the intermediate network 720, if any, may be a backbone network or the Internet; in particular, the intermediate network 720 may comprise two or more sub-networks (not shown).
  • the communication system of Figure 7 as a whole enables connectivity between one of the connected UEs 791, 792 and the host computer 730.
  • the connectivity may be described as an over-the-top (OTT) connection 750.
  • the host computer 730 and the connected UEs 791, 792 are configured to communicate data and/or signaling via the OTT connection 750, using the access network 711, the core network 714, any intermediate network 720 and possible further infrastructure (not shown) as intermediaries.
  • the OTT connection 750 may be transparent in the sense that the participating communication devices through which the OTT connection 750 passes are unaware of routing of uplink and downlink communications.
  • a base station 712 may not or need not be informed about the past routing of an incoming downlink communication with data originating from a host computer 730 to be forwarded (e.g., handed over) to a connected UE 791. Similarly, the base station 712 need not be aware of the future routing of an outgoing uplink communication originating from the UE 791 towards the host computer 730.
  • a host computer 810 comprises hardware 815 including a communication interface 816 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of the communication system 800.
  • the host computer 810 further comprises processing circuitry 818, which may have storage and/or processing capabilities.
  • the processing circuitry 818 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.
  • the host computer 810 further comprises software 811, which is stored in or accessible by the host computer 810 and executable by the processing circuitry 818.
  • the software 811 includes a host application 812.
  • the host application 812 may be operable to provide a service to a remote user, such as a UE 830 connecting via an OTT connection 850 terminating at the UE 830 and the host computer 810. In providing the service to the remote user, the host application 812 may provide user data which is transmitted using the OTT connection 850.
  • the communication system 800 further includes a base station 820 provided in a telecommunication system and comprising hardware 825 enabling it to communicate with the host computer 810 and with the UE 830.
  • the hardware 825 may include a communication interface 826 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of the communication system 800, as well as a radio interface 827 for setting up and maintaining at least a wireless connection 870 with a UE 830 located in a coverage area (not shown in Figure 8) served by the base station 820.
  • the communication interface 826 may be configured to facilitate a connection 860 to the host computer 810.
  • connection 860 may be direct or it may pass through a core network (not shown in Figure 8) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system.
  • the hardware 825 of the base station 820 further includes processing circuitry 828, 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.
  • the base station 820 further has software 821 stored internally or accessible via an external connection.
  • the communication system 800 further includes the UE 830 already referred to.
  • Its hardware 835 may include a radio interface 837 configured to set up and maintain a wireless connection 870 with a base station serving a coverage area in which the UE 830 is currently located.
  • the hardware 835 of the UE 830 further includes processing circuitry 838, 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.
  • the UE 830 further comprises software 831, which is stored in or accessible by the UE 830 and executable by the processing circuitry 838.
  • the software 831 includes a client application 832.
  • the client application 832 may be operable to provide a service to a human or non-human user via the UE 830, with the support of the host computer 810.
  • an executing host application 812 may communicate with the executing client application 832 via the OTT connection 850 terminating at the UE 830 and the host computer 810.
  • the client application 832 may receive request data from the host application 812 and provide user data in response to the request data.
  • the OTT connection 850 may transfer both the request data and the user data.
  • the client application 832 may interact with the user to generate the user data that it provides.
  • the host computer 810, base station 820 and UE 830 illustrated in Figure 8 may be identical to the host computer 1330, one of the base stations 712a, 712b, 712c and one of the UEs 791, 792 of Figure 7, respectively.
  • the inner workings of these entities may be as shown in Figure 8 and independently, the surrounding network topology may be that of Figure 7.
  • the OTT connection 850 has been drawn abstractly to illustrate the communication between the host computer 810 and the use equipment 830 via the base station 820, without explicit reference to any intermediary devices and the precise routing of messages via these devices.
  • Network infrastructure may determine the routing, which it may be configured to hide from the UE 830 or from the service provider operating the host computer 810, or both. While the OTT connection 850 is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).
  • the wireless connection 870 between the UE 830 and the base station 820 is in accordance with the teachings of the embodiments described throughout this disclosure, such as provided by nodes such as wireless device 50 and network node 30, along with the corresponding method 500.
  • the embodiments described herein enable a smooth intervention of the cell selection function in various procedures (e.g., CMC and dual connectivity) of the radio access to mitigate temporary or permanent transport network bottlenecks in a smooth way, to prevent congestions and dynamically adapt to evolving transport network states.
  • the teachings of these embodiments may improve the throughput, quality, latency and/or power consumption for the network and improve the experience for the user of a UE 830 that uses the OTT connection 850.
  • 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.
  • the measurement procedure and/or the network functionality for reconfiguring the OTT connection 850 may be implemented in the software 811 of the host computer 810 or in the software 831 of the UE 830, or both.
  • sensors (not shown) may be deployed in or in association with communication devices through which the OTT connection 850 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 811, 831 may compute or estimate the monitored quantities.
  • the reconfiguring of the OTT connection 850 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect the base station 820, and it may be unknown or imperceptible to the base station 820. Such procedures and functionalities may be known and practiced in the art.
  • measurements may involve proprietary UE signaling facilitating the host computer’s 810 measurements of throughput, propagation times, latency and the like.
  • the measurements may be implemented in that the software 811, 831 causes messages to be transmitted, in particular empty or‘dummy’ messages, using the OTT connection 850 while it monitors propagation times, errors etc.
  • FIG. 9 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 7 and 8. For simplicity of the present disclosure, only drawing references to Figure 9 will be included in this section.
  • the host computer provides user data.
  • the host computer provides the user data by executing a host application.
  • the host computer initiates a transmission carrying the user data to the UE.
  • 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.
  • the UE executes a client application associated with the host application executed by the host computer.
  • FIG. 10 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 7 and 8. For simplicity of the present disclosure, only drawing references to Figure 10 will be included in this section.
  • the host computer provides user data.
  • the host computer provides the user data by executing a host application.
  • the host computer initiates a transmission carrying the user data to the UE. The transmission may pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure.
  • the UE receives the user data carried in the transmission.
  • FIG 11 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 7 and 8. For simplicity of the present disclosure, only drawing references to Figure 11 will be included in this section.
  • the UE receives input data provided by the host computer.
  • the UE provides user data.
  • the UE provides the user data by executing a client application.
  • the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer.
  • the executed client application may further consider user input received from the user.
  • the UE initiates, in an optional third substep 1130, transmission of the user data to the host computer.
  • the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.
  • FIG 12 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment.
  • the communication system includes a host computer, a base station and a UE which may be those described with reference to Figures 7 and 8. For simplicity of the present disclosure, only drawing references to Figure 12 will be included in this section.
  • the base station receives user data from the UE.
  • the base station initiates transmission of the received user data to the host computer.
  • the host computer receives the user data carried in the transmission initiated by the base station.
  • each functional module corresponds to a functional unit of software executing in an appropriate processor or to a functional digital hardware circuit, or some combination of both.
  • Figure 13 illustrates an example functional module or circuit architecture for a first network node 30 that includes a determining module 1302 for determining transport network performance information corresponding to each of one or more transport network interfaces between a RAN node and one or more other network nodes.
  • the implementation also includes a signaling module 1304 for signaling the transport network performance information to another network node, or performing one or more radio access network management or optimization tasks, based on the transport network performance information, or both.
  • Example embodiments can include, but are not limited to, the following enumerated examples:
  • transport network performance information comprises, for at least one of transport network interfaces, any one or more of the following parameters:
  • performance information comprises configuring connections to the RAN for one or more user wireless devices, based on the transport network performance information.
  • performance information comprises configuring or triggering handovers for one or more user wireless devices, based on the transport network performance information.
  • performance information comprises configuring dual- or multi -connectivity for one or more user wireless devices, based on the transport network performance information.
  • the network node is a distributed unit (DU) of a base station
  • determining the transport network performance information for at least one of the transport network interfaces comprises measuring all or part of the transport network performance information
  • the DU signals the transport network information to a central unit (CU) of the base station.
  • the network node is a central unit (CU) of a base station
  • determining the transport network performance information for at least one of the transport network interfaces comprises receiving all or part of the transport network performance information from a DU of the base station and/or from a neighboring CU, and wherein the CU signals the transport network information to a core network node.
  • CU central unit
  • the network node is a central unit (CU) of a base station
  • determining the transport network performance information for at least one of the transport network interfaces comprises receiving all or part of the transport network performance information from a distributed unit (DU) of the base station, and wherein the CU performs one or more radio access network management or optimization tasks, based on the transport network performance information.
  • DU distributed unit
  • the network node is a central unit (CU) of a base station
  • determining the transport network performance information for at least one of the transport network interfaces comprises measuring all or part of the transport network performance information, and wherein the CU performs one or more radio access network management or optimization tasks, based on the transport network performance information.
  • the network node is a central unit (CU) of a base station
  • determining the transport network performance information for at least one of the transport network interfaces comprises receiving all or part of the transport network performance information from a neighboring CU or base station, and wherein the CU performs one or more radio access network management or optimization tasks, based on the transport network performance information.
  • a network node adapted to perform the methods of any of example embodiments 1-13.
  • a network node comprising transceiver circuitry and processing circuitry operatively associated with the transceiver circuitry and configured to perform the methods of any of example embodiments 1-13.
  • a computer program comprising instructions that, when executed on at least one processing circuit, cause the at least one processing circuit to carry out the method according to any one of example embodiments 1-13.
  • a communication system including a host computer comprising:
  • processing circuitry configured to provide user data
  • a communication interface configured to forward the user data to a cellular network for transmission to a user equipment (UE), wherein the cellular network comprises a base station having a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the operations comprising embodiments 1-13.
  • UE user equipment
  • the communication system of the previous embodiment further including the base station.
  • A3 The communication system of the previous two embodiments, further including the UE, wherein the UE is configured to communicate with the base station.
  • the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data
  • the UE comprises processing circuitry configured to execute a client application associated with the host application.
  • the host computer providing user data; and at the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the base station performs any of the steps of any of embodiments 1-13.
  • A6 The method of the previous embodiment, further comprising, at the base station, transmitting the user data.
  • A7 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.
  • a user equipment configured to communicate with a base station, the UE comprising a radio interface and processing circuitry configured to perform any of the previous 3 embodiments.
  • a communication system including a host computer comprising:
  • processing circuitry configured to provide user data
  • a communication interface configured to forward user data to a cellular network for transmission to a user equipment (UE),
  • UE user equipment
  • the UE comprises a radio interface and processing circuitry, the UE’s
  • the cellular network further includes a base station configured to communicate with the UE.
  • the processing circuitry of the host computer is configured to execute a host
  • the UE’s processing circuitry is configured to execute a client application associated with the host application.
  • a method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising: at the host computer, providing user data; and
  • the host computer initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the UE performs any of the steps of any of embodiments 1-13.
  • a communication system including a host computer comprising:
  • UE user equipment
  • the UE comprises a radio interface and processing circuitry, the UE’s
  • processing circuitry configured to perform any of the steps of any of embodiments 1-13.
  • A15 The communication system of the previous embodiment, further including the UE.
  • the communication system of the previous 2 embodiments further including the base station, wherein the base station comprises a radio interface configured to communicate with the UE and a communication interface configured to forward to the host computer the user data carried by a transmission from the UE to the base station.
  • the processing circuitry of the host computer is configured to execute a host
  • the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data.
  • the processing circuitry of the host computer is configured to execute a host
  • the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data in response to the request data.
  • A19. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising:
  • the host computer receiving user data transmitted to the base station from the UE, wherein the UE performs any of the steps of any of embodiments 1-13.
  • A20 The method of the previous embodiment, further comprising, at the UE, providing the user data to the base station.
  • a communication system including a host computer comprising a communication interface configured to receive user data originating from a transmission from a User equipment (UE) to a base station, the base station comprising a radio interface and processing circuitry configured to communicate with the base station and cooperatively perform operations of any of embodiments 1-13.
  • UE User equipment
  • the communication system of the previous embodiment further including the base station.
  • A25 The communication system of the previous two embodiments, further including the UE, wherein the UE is configured to communicate with the base station.
  • A26 The communication system of the previous three embodiments, wherein: the processing circuitry of the host computer is configured to execute a host
  • the UE is further configured to execute a client application associated with the host application, thereby providing the user data to be received by the host computer.
  • A27 A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising:
  • the host computer receiving, from the base station, user data originating from a transmission which the base station has received from the UE, wherein the UE performs any of the steps of any of embodiments 1-13.
  • A28 The method of the previous embodiment, further comprising at the base station, receiving the user data from the UE.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Environmental & Geological Engineering (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Selon un aspect, un noeud de réseau, d'un RAN qui dessert un ou plusieurs dispositifs sans fil d'utilisateur, détermine des informations de performance de réseau de transport correspondant à chacune d'une ou de plusieurs interfaces de réseau de transport entre un noeud RAN et un ou plusieurs autres nœuds de réseau. Le noeud de réseau signale également les informations de performance de réseau de transport à un autre noeud de réseau, ou effectue des tâches de gestion ou d'optimisation de réseau d'accès radio, sur la base des informations de performance de réseau de transport, ou les deux.
PCT/SE2020/050242 2019-03-29 2020-03-05 Distribution d'informations d'état de réseau de transport pour amélioration de procédure ran WO2020204779A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201962826502P 2019-03-29 2019-03-29
US62/826,502 2019-03-29

Publications (1)

Publication Number Publication Date
WO2020204779A1 true WO2020204779A1 (fr) 2020-10-08

Family

ID=69780267

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SE2020/050242 WO2020204779A1 (fr) 2019-03-29 2020-03-05 Distribution d'informations d'état de réseau de transport pour amélioration de procédure ran

Country Status (1)

Country Link
WO (1) WO2020204779A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100091667A1 (en) * 2006-10-03 2010-04-15 Muhammad Kazmi Method and Arrangement in a Telecommunication System
US20190075552A1 (en) * 2017-11-07 2019-03-07 Intel Corporation Enabling network slicing in a 5g network with cp/up separation

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100091667A1 (en) * 2006-10-03 2010-04-15 Muhammad Kazmi Method and Arrangement in a Telecommunication System
US20190075552A1 (en) * 2017-11-07 2019-03-07 Intel Corporation Enabling network slicing in a 5g network with cp/up separation

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
HUAWEI: "Discussion on Load Balancing", vol. RAN WG3, no. Athens, Greece; 20190225 - 20190301, 15 February 2019 (2019-02-15), XP051604322, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg%5Fran/WG3%5FIu/TSGR3%5F103/Docs/R3%2D190381%2Ezip> [retrieved on 20190215] *
ZTE: "Discussion on Load Management for SON in NR", vol. RAN WG3, no. Athens, Greece; 20190225 - 20190301, 15 February 2019 (2019-02-15), XP051604353, Retrieved from the Internet <URL:http://www.3gpp.org/ftp/tsg%5Fran/WG3%5FIu/TSGR3%5F103/Docs/R3%2D190412%2Ezip> [retrieved on 20190215] *

Similar Documents

Publication Publication Date Title
US11950124B2 (en) Methods, apparatus and systems for integrated access and backhaul bearer management
EP2781123B1 (fr) Réalisation d&#39;un équilibrage de charge de mobilité et d&#39;une optimisation de robustesse de mobilité entre des n uds d&#39;accès pour seulement un sous-ensemble d&#39;équipements d&#39;utilisateurs
CN113424499A (zh) 用于在集成接入回程（iab）网络中转发数据的中央单元（cu）、分布式单元（du）及其中的方法
US10045362B2 (en) Uplink based selection of downlink connectivity configuration
US11943164B2 (en) Minimization of driving test (MDT) logs reporting method and device, MDT logs reporting control method and device, storage medium, and electronic device
US20210037587A1 (en) Protocols and Architectures for NR-NR Dual Connectivity (NR-DC)
EP3695642B1 (fr) Gestion de débit binaire pour des supports d&#39;ue
US10993246B2 (en) User equipment, network node and methods in a wireless communications network
US20220295349A1 (en) Slice level load reporting and balancing in wireless communications
US10812224B2 (en) NR user plane signaling controlled triggering of PDCP duplication
US20170201366A1 (en) Carrier Aggregation inter eNB activation
WO2017097349A1 (fr) Commande d&#39;un réseau d&#39;accès radio sur la base d&#39;une capacité de réseau de transport
WO2022005346A1 (fr) Procédé de planification multiples flux de données répliquées sur un certain nombre de voies de transmission sans fil
US20190268814A1 (en) Network Node and Methods Therein for User Plane Switching
US11956665B2 (en) Detecting congestion at an intermediate IAB node
KR20220098739A (ko) 2차 셀 교체
US20230388848A1 (en) First Network Node, Second Network Node and Methods in a Wireless Communications Network
WO2020204779A1 (fr) Distribution d&#39;informations d&#39;état de réseau de transport pour amélioration de procédure ran
US20230292349A1 (en) Method and apparatus for resource restriction
WO2017081360A1 (fr) Multi-connectivité de dispositif de terminal dans un système cellulaire
WO2023068978A1 (fr) Nœuds de réseau et procédés dans un domaine technique de réseau de communication sans fil
WO2020034470A1 (fr) Augmentation de l&#39;efficacité dans les communications sans fil
CN117440429A (zh) 数据传输方法和相关设备
CN117479213A (zh) 信息传输方法、装置及网络节点

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20710317

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20710317

Country of ref document: EP

Kind code of ref document: A1