Method for resource coordination between neighboring RAN nodes over a network interface

Abstract

A method and system for coordinating resources between neighboring network nodes and cells in a telecommunications network is described. Adjacent cells or nodes may experience contention, such as co-channel interference. To enable coordination between nodes or cells, it has been necessary to establish a full-fledged cell-to-cell relationship with the network interface. This can be cost and resource intensive, even if most of the functionality on the interface remains unused. A system and method are disclosed for enabling resource coordination without incurring a full-fledged relationship between cells, enabling more efficient use of resources.

Description

[Technical Field]

[0001] (CROSS-REFERENCE TO RELATED APPLICATIONS) This application claims the benefit of U.S. Priority Application No. 63 / 277491, filed November 9, 2021, entitled "Method for Resource Coordination Between Neighboring RAN Nodes Over a Network Interface."

[0002] (Technical field) TECHNICAL FIELD The present disclosure relates generally to the technical field of wireless communications, and more particularly to resource coordination among neighboring nodes. [Background technology]

[0003] The current 5G RAN (NG-RAN (Next Generation Radio Access Network)) architecture is shown and described in 3GPP TS 38.401 version 16.5.0. The overall architecture of the NG-RAN is shown in Figure 1.

[0004] NR Architecture The NG-RAN includes a collection of gNBs (NR (New Radio) base stations) connected to the 5G Core (5GC) via the NG. The gNBs can support FDD (Frequency Division Duplex), TDD (Time Division Duplex), or dual-mode operation. The gNBs can be interconnected via an Xn interface (an interface between two gNBs in NR). The gNBs can consist of a gNB-CU (Central Unit) and a gNB-DU (Distributed Unit). The gNB-CU and gNB-DU are interconnected via a logical interface called F1. A gNB-DU is preferably connected to only one gNB-CU. For resilience, a gNB-DU can be connected to multiple gNB-CUs through appropriate implementation.

[0005] 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 the interfaces between them, are defined as part of the RNL. For each NG-RAN interface (NG, Xn, F1), the associated TNL protocols and functions are specified. The TNL provides services for user plane transport and control plane (signaling) transport. If security protection for control plane and user plane data on the TNL of the NG-RAN interface must be supported, NDS / IP (Network Domain Security / Internet Protocol) (3GPP TS 33.401) is applied.

[0006] A gNB may also be connected to an LTE (Long Term Evolution) eNB (Evolved Node B (LTE base station)) via an X2 interface (the interface between two eNBs in LTE). Another architectural option is when an LTE eNB connected to an evolved packet core network is connected via an X2 interface with a so-called en-gNB, which is a gNB that is not directly connected to the CN but is connected to an eNB via X2 for the sole purpose of implementing dual connectivity.

[0007] The architecture of Figure 1 can be extended by splitting the gNB-CU into two entities (see Figure 2). In the split architecture option, the RAN protocol stack functions are separated into different parts. The gNB-CU-CP (or CU-CP (Central Unit - Control Plane)) is expected to handle the RRC (Radio Resource Control) layer, the gNB-CU-UP (or CU-UP (Central Unit - User Plane)) handles the PDCP (Packet Data Convergence Protocol) layer, and the gNB-DU handles the RLC, MAC (Medium Access Control), and PHY (Physical) layers of the protocol stack. In some further splits, the gNB-DU can have a separate unit that handles the PHY part separately compared to the RLC and MAC layers that are handled in the gNB-DU.

[0008] As different units handle different protocol stack functions, inter-node communication between the gNB-DU, gNB-CU-UP, and gNB-CU-CP is required. This is achieved via the F1-C interface related to control plane signaling, via the F1-U interface related to user plane signaling for communication between the gNB-CU and gNB-DU, and via the E1 interface for communication between the gNB-CU-UP and gNB-CU-CP.

[0009] The E1 interface is a logical interface. It supports the exchange of signaling information between endpoints. From a logical point of view, the E1 interface is a point-to-point interface between the gNB-CU-CP and the gNB-CU-UP. The E1 interface allows the exchange of UE (User Equipment) related and non-UE related information. The E1 interface is a control interface and is not used for user data transfer.

[0010] Random Access in NR Random access (RA) is performed when a UE wants to transition from an idle / inactive state to a connected state, e.g., to transmit data or signaling. Similar to LTE, NR uses a four-step random access procedure (see Figure 3) with the following steps: 1 - The UE transmits a preamble (also known as Msg1) on the Physical Random Access Channel (RACH) 2 - The network responds with a Random Access Response (RAR) (also known as Msg2) indicating receipt of the preamble and providing a time alignment command to adjust the UE's transmit timing based on the timing of the received preamble 3-4 - The UE and the network exchange messages (uplink message Msg3 and subsequent downlink message Msg4) to resolve potential collisions due to simultaneous transmission of the same preamble from multiple devices within the cell.

[0011] If successful, Msg4 also transitions the UE to a connected state. Once random access is complete, the UE is in a connected state and subsequent communication is performed using a dedicated channel.

[0012] In addition to the basic four-step random access procedure described above, NR Release 16 also supports a two-step random access procedure consisting of only two messages, MsgA and MsgB, where MsgA essentially replaces Msg1+Msg3, and MsgB essentially replaces Msg2+Msg4 (see Figure 4). The two-step random access procedure reduces the idle-to-connected transition time, but in practice is limited to small cells with a timing advance of 0, since the Msg3 (or PUSCH (Physical Uplink Shared Channel)) part of MsgA is sent before uplink timing alignment is established.

[0013] The above is a so-called contention-based random access procedure, where there is no coordination between UEs and therefore the same preamble is transmitted from multiple UEs at the same time. In connected mode, there is also a contention-free random access procedure, used for example during handover, where the network assigns a dedicated preamble for the UE to use in the random access procedure, and therefore there is no collision. The focus of this disclosure is on contention-based random access procedures.

[0014] RACH Optimization Optimizing the RACH configuration in a cell is key to optimizing the system performance of mobile networks. optimization The RACH is a network feature. A poorly configured RACH may result in higher call setup and handover delays due to frequent RACH collisions or low preamble detection probability and limited coverage. The amount of uplink resources reserved for the RACH also affects system capacity. Therefore, network operators should carefully monitor that RACH parameters are properly set, taking into account factors such as RACH load, uplink interference, traffic patterns, and population under cell coverage.

[0015] The RACH optimization function facilitates automatic configuration of PRACH (Physical RACH) parameters (including PRACH resource configuration, preamble root sequence, and cyclic shift configuration) to avoid preamble collisions with neighboring cells. The principle of this automatic configuration is similar to the automatic PCI (Physical Cell Identifier) ​​configuration SON function, where PRACH configuration information is included in the "X2 Setup" and "eNB Configuration Update" procedures in LTE. Therefore, whenever a new eNB is initialized and learns about its neighbors through the ANR (Automatic Neighbor Relation) function, it can simultaneously learn neighboring PRACH configurations. It can then select its own PRACH configuration to avoid conflicts with those of its neighbors. This is facilitated when neighboring eNBs / cells are synchronized.

[0016] Whenever a conflict is identified, one of the cells should change its configuration, but the algorithm for selecting which cell to change and how is not specified. Network operators can also combine PRACH self-optimization with manual configuration if desired, but this is generally more error-prone and time-consuming than automatic RACH optimization.

[0017] Signaling for RACH over the X2 interface in LTE Next, we will describe signaling related to RACH over the X2 interface in an LTE network. Generally, a RAN node may trigger, internally or in coordination with other RAN nodes, analysis of information reported by one or more UEs. In this regard, as part of the LTE solution, eNB PRACH configuration parameters can be exchanged over the X2 interface using X2AP (X2 Application Protocol) signaling procedures, including X2 SETUP REQUEST / X2 SETUP RESPONSE message exchange and ENB CONFIGURATION UPDATE / ENB CONFIGURATION UPDATE ACKNOWLEDGE message exchange. This IE indicates the PRACH resources used in neighboring cells.

[0018] Such information can be exchanged between RAN nodes that have cells identified as neighboring cells. Neighboring cells are identified by RRM (Radio Resource Management) measurements provided by the UE. Upon detecting a new neighbor, the RAN node can set up an X2 interface and later request a configuration update if it has changed. This is accomplished as part of the X2 SETUP REQUEST or ENB CONFIGURATION UPDATE X2AP signaling, which includes the PRACH Configuration IE as part of the Served Cell Information IE.

[0019] In addition to the above-mentioned mechanisms for exchanging RACH-related configuration information over the X2 interface as part of X2 setup and eNB configuration update signaling, a Uu-based (air interface for LTE and 5G NR) signaling mechanism is defined to use UE assistance information to detect potential problems and further improve RACH performance by performing finer-grained optimizations that rely on the provided UE assistance information.

[0020] E-UTRA-NR Cell Resource Adjustment This section describes E-UTRA-NR (Evolved Universal Terrestrial Radio Access-NR) cell resource coordination. The purpose of the E-UTRA-NR cell resource coordination procedure is to enable coordination of radio resource allocations between ng-eNBs and gNBs that share spectrum and have fully or partially overlapping coverage areas. During the procedure, the ng-eNB and gNB exchange their intended resource allocations for data traffic and, if possible, converge on shared resources. This procedure should only be used for E-UTRA-NR spectrum sharing purposes. The procedure may use non-UE-related signaling.

[0021] As specified in TS 38.300, in case of network sharing with multiple cell IDs broadcast using shared Xn-C signaling transport, the E-UTRA-NR CELL RESOURCE COORDINATION REQUEST message and the E-UTRA-NR CELL RESOURCE COORDINATION RESPONSE message should include an Interface Instance Indication IE to identify the corresponding interface instance.

[0022] Figure 6 shows a successful E-ULTRA-NR cell resource coordination request initiated by the ng-eNB (a node providing E-UTRA user plane and control plane protocol terminations toward the UE and connected to the 5GC via the NG interface). The ng-eNB initiates the procedure by sending an E-UTRA-NR CELL RESOURCE COORDINATION request message to the gNB via the Xn interface. The gNB extracts the data traffic resource indication IE and responds by sending an E-UTRA-NR CELL RESOURCE COORDINATION RESPONSE message. The gNB calculates the complete ng-eNB resource allocation by combining the most recently received data traffic resource indication IE from the ng-eNB with the protected E-UTRA resource indication IE. In the event of a conflict between the most recently received data traffic resource indication IE and the most recently received protected E-UTRA resource indication IE, the gNB gives priority to the protected E-UTRA resource indication IE.

[0023] Figure 7 shows an E-ULTRA-NR cell resource coordination request initiated by a gNB, with successful operation. The gNB starts the procedure by sending an E-UTRA-NR CELL RESOURCE COORDINATION request message to the ng-eNB. The ng-eNB responds with an E-UTRA-NR CELL RESOURCE COORDINATION RESPONSE message. In the event of a conflict between the most recently received data traffic resource indication IE and the most recently received protection E-UTRA resource indication IE, the gNB gives priority to the protection E-UTRA resource indication IE.

[0024] ANR function The explanation from 3GPP TS 36.300 can help to explain the details of the neighbor relationships between neighboring RAN nodes.

[0025] The purpose of the ANR function is to relieve operators from the burden of manually managing Neighbor Cell Relations (NCRs). Figure 8 shows the ANR and its environment. The ANR function resides in the eNB and manages a conceptual Neighbor Cell Relation Table (NCRT). The Neighbor Discovery function located in the ANR finds new neighbors and adds them to the NCRT. The ANR also contains a Neighbor Removal function that removes old NCRs. The Neighbor Discovery and Neighbor Removal functions are implementation specific.

[0026] NCR in the context of ANR is defined as follows: The existing neighbor relationship from the source cell to the target cell is determined by the eNB controlling the source cell: 1. Recognize the ECGI / CGI (E-UTAN Cell Global Identifier or Cell Global Identifier) ​​and PCI of the target cell, 2. The source cell has an entry in its NCRT identifying the target cell; 3. The attributes of this NCRT entry are defined as O&M (Operations and Maintenance) or set to default values.

[0027] For each cell that the eNB has, the eNB maintains an NCR (see Figure 8). For each NCR, the NCR includes a Target Cell Identifier (TCI) that identifies the target cell. In the case of E-UTRAN, the TCI corresponds to the ECGI and PCI of the target cell. Furthermore, each NCR has three attributes: NoRemove, NoHO, and NoX2 attributes. These attributes have the following definitions: 1. No Remove: If checked, the eNB removes the NCR from the NCRT. Shouldn't 2. No HO: If checked, NCR is not used by the eNB for handover reasons. Shouldn't 3. No X2: If checked, the neighbor relationship uses the X2 interface to initiate procedures towards the eNB that parented the target cell. Shouldn't .

[0028] NCR is an inter-cell relationship, while X2 links are set up between two eNBs. NCR is unidirectional, while X2 links are bidirectional. Neighbor information exchange that occurs during the X2 setup procedure or the eNB configuration update procedure can be used for ANR purposes. The ANR function also allows O&M to manage NCRTs. O&M can add and delete NCRs. It can also change the attributes of NCRTs. The O&M system is informed of changes to NCRTs. Summary of the Invention

[0029] One embodiment according to the present disclosure comprises a method performed by an OAM (Operation, Administration, and Maintenance) node for configuring attribute configurations between a first cell served by a first network node and a second cell served by a second network node, the method comprising configuring at least one attribute configuration at the first network node and the second network node, the at least one attribute configuration identifying at least one service to be used over an interface between the first cell and the second cell.

[0030] Another embodiment of a method according to the present disclosure is a method performed by a first network node to configure an attribute configuration between a first cell served by the first network node and a second cell served by a second network node. The method comprises receiving at least one attribute configuration from an OAM, the at least one attribute configuration identifying at least one service to be used over an interface between the first cell and the second cell. It further includes setting up the interface between the first cell and the second cell and using the at least one service on the interface.

[0031] Another embodiment comprises a method, performed by a first network node, for managing attribute configurations of a first cell served by the first network node. The method comprises configuring at least one attribute configuration in the first network node as part of a neighbor relationship between the first cell and a second cell served by a second network node, and determining at least one service, identified by at least the attribute configuration, to be used on an interface between the first cell and the second cell. The method also includes indicating the at least one service and the at least one attribute configuration to the second network node, establishing the interface, and implementing the at least one service over the established interface.

[0032] Another possible embodiment according to the present disclosure is a method performed by a first network node co-located with a second network node to perform resource coordination with a third network node using the same frequency band as a first cell served by the first network node. The method comprises configuring a neighbor relationship for a second cell served by the second network node, the neighbor relationship identifying at least one service to be used over an interface between the first cell and the second cell. The method also includes indicating the neighbor relationship and the at least one service to the second network node and coordinating one or more resources with the second network node such that neighbor cells between the first network node and the third network node can coexist on a shared channel.

[0033] Additional embodiments comprise a network node or component for configuring a neighbor relationship between a first cell and a second cell for a particular service, the node or component comprising processing circuitry configured to perform any of the steps of any of the network node or component (e.g., OAM, O&M) based methods described herein, and further comprising power supply circuitry configured to provide power to the processing circuitry.

[0034] This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an indicator of the scope of the claimed subject matter. [Brief explanation of the drawings]

[0035] For a more complete understanding of the present disclosure, reference is now made to the following descriptions taken in conjunction with the accompanying drawings, in which:

[0036] [Figure 1] Figure 1 shows the overall NG-RAN architecture.

[0037] [Figure 2] Figure 2 shows a split gNB architecture in NG-RAN.

[0038] [Figure 3] FIG. 3 shows a flowchart of the four-step random access procedure.

[0039] [Figure 4] FIG. 4 shows a flowchart of a two-step random access procedure.

[0040] [Figure 5] FIG. 5 shows a table of exemplary PRACH configuration information elements.

[0041] [Figure 6] FIG. 6 shows a flowchart of the successful operation of an E-UTRA-NR cell resource adjustment request initiated by the ng-eNB.

[0042] [Figure 7] FIG. 7 shows a flowchart of the successful operation of an E-UTRA-NR cell resource adjustment request initiated by a gNB.

[0043] [Figure 8] FIG. 8 illustrates an embodiment of the interaction between eNB and O&M via ANR.

[0044] [Figure 9] Figure 9 shows a typical 4G wireless network deployment.

[0045] [Figure 10] FIG. 10 illustrates a flowchart of an embodiment of a method for resource coordination between two network nodes under the present disclosure.

[0046] [Figure 11] FIG. 11 illustrates a flowchart of a method embodiment for resource coordination among three network nodes under the present disclosure.

[0047] [Figure 12] FIG. 12 illustrates a flowchart of an embodiment of a method for resource coordination between two network nodes and an OAM in accordance with the present disclosure.

[0048] [Figure 13] FIG. 13 illustrates an embodiment of the interaction between a gNB and an OAM via ANR.

[0049] [Figure 14] FIG. 14 illustrates a flowchart of an embodiment of a method for resource coordination between a UE and two nodes / cells under the present disclosure.

[0050] [Figure 15] FIG. 15 shows an overview of an embodiment of a communication system in the present disclosure.

[0051] [Figure 16] FIG. 16 shows a schematic diagram of an embodiment of a user equipment in the present disclosure.

[0052] [Figure 17] FIG. 17 shows a schematic diagram of an embodiment of a network node in the present disclosure.

[0053] [Figure 18] FIG. 18 shows a schematic diagram of an embodiment of a host according to the present disclosure.

[0054] [Figure 19] FIG. 19 shows a schematic diagram of an embodiment of a virtualization environment in the present disclosure.

[0055] [Figure 20] FIG. 20 illustrates a schematic diagram of an embodiment of communication between nodes, hosts, and user equipment in the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0056] Before describing various embodiments of the present disclosure in detail, it should be understood that the present disclosure is not limited to the parameters of the particularly illustrated systems, methods, apparatus, products, processes, and / or kits, which may, of course, vary. Accordingly, while certain embodiments of the present disclosure will be described in detail with reference to specific configurations, parameters, components, elements, etc., the description is illustrative and should not be construed as limiting the scope of the claimed embodiments. Additionally, the terminology used herein is for the purpose of describing embodiments and is not necessarily intended to limit the scope of the claimed embodiments.

[0057] Currently, there are certain challenges for resource coordination between neighboring nodes. As mentioned above, for each cell owned by a RAN node (eNB in ​​a non-limiting example), the RAN node maintains an NCRT. For each NCR, the NCRT includes a TCI that identifies the target cell, e.g., the ECGI and PCI of the target cell. Furthermore, each NCR has three attributes: NoRemove, NoHO, and NoX2 attributes, as defined below. No Remove: If checked, the eNB shall not remove the NCR from the NRT. No HO: If checked, NCR shall not be used by the eNB for handover reasons No X2: If checked, the neighbor relationship does not use the X2 interface to initiate procedures towards the eNB parenting the target cell.

[0058] An attribute configuration can refer to a set of attributes, whether they are checked or not, and their respective functions can be implemented (or prohibited). A neighbor relation refers to an attribute configuration combined with the identity of the target cell. A neighbor relation is often a line or group of data within the NCRT.

[0059] Based on these attributes, the source and / or target RAN nodes are restricted in using the neighbor relationship (e.g., the interface between the RAN nodes shall not be used for handover purposes). However, current approaches (described above) do not allow operators to establish interfaces between neighboring RAN nodes to perform a specific set of features. This drawback can cause additional costs for network operators who need to support the entire interface capability with their associated setup and configuration requirements due to the limited set of functions performed on the established interface.

[0060] A non-limiting example problem can be described as follows. This example is based on an existing problem in a real network discussed at the 3GPP® RAN3#110e meeting. In the 4G era, 1.8 GHz was deployed in urban areas as a coverage layer, and 2.1 GHz was deployed in areas with high-capacity requirements as a capacity layer. As shown in Figure 9, the amount of 2.1 GHz cells is much smaller than that of 1.8 GHz cells. The 2.1 GHz band is also considered a good choice for the NR coverage layer. To enable a smooth transition between LTE and NR, it would be ideal to upgrade existing LTE 2.1 GHz sites to support resource coordination functions. This would enable the upgraded eNB to connect to a newly deployed gNB, for example, via the EN-DC (E-UTRA-NR Dual Connectivity) X2 interface, allowing both LTE and NR to coexist in the same spectrum. It is worth noting that a large number of NR cells sharing the same channel with LTE are planned to be deployed to establish continuous coverage for NR. As a result, co-channel interference between existing LTE cells in upgraded sites and newly built NR sites is very significant, and solutions to correct it are needed to avoid spectral efficiency degradation.

[0061] Certain aspects of the present disclosure and its embodiments can provide solutions to these and other problems. The embodiments below of the present disclosure can support the coordination of radio resource allocation between eNBs and en-gNBs sharing a spectrum via an E-UTRA-NR cell resource coordination procedure. However, to utilize the resource coordination function between E-UTRA and NR cells, a complete cell-to-cell relationship and network interface (e.g., the EN-DC X2 interface) was previously established, while most of the features on this established interface remain unused. This can result in prohibitive costs for operators in terms of complexity, configuration, and operational investment. Therefore, one problem is how to enable the use of resource coordination without incurring such high costs.

[0062] Some of the following embodiments of the present disclosure include enabling neighboring RAN nodes to configure and / or set up neighbor relations and establish network interfaces to neighboring RAN nodes only for specific functions / applications / services (or a specific set of functions, etc.) between the neighboring RAN nodes. This means, for example, that the inter-cell neighbor relations and established interfaces can be used to perform only specific functions selected by pre-configuration. The following embodiments of the present disclosure comprise methods and systems for configuring inter-cell neighbor relation interfaces between neighboring RAN nodes that enable the RAN nodes to perform only a specific set of functions using the established network interface.

[0063] Certain embodiments may provide various technical advantages. Certain embodiments according to the present disclosure may provide detailed means for a RAN node to use inter-cell neighbor relations and interfaces to other RAN nodes to perform certain functions, such as resource coordination or spectrum sharing or PRACH resource coordination. Certain method embodiments may provide the possibility to implement and operate co-channel cells belonging to non-co-located RAN nodes.

[0064] A non-limiting example may be resource coordination or dynamic spectrum sharing between neighboring RAN nodes owning cells where a particular function operates in the same or overlapping frequency bands. Another non-limiting example may be coordination of PRACH configurations between neighboring RAN nodes owning cells where a particular function operates in the same or overlapping frequency bands.

[0065] Some of the embodiments contemplated herein may now be more fully described with reference to the accompanying drawings. The embodiments are provided as examples to convey the scope of the subject matter to those skilled in the art. For purposes of this disclosure, the terms / names / abbreviations "CU," "DU," "CU-CP," and "CU-UP" may be considered equivalent to the respective terms / names / abbreviations "gNB-CU," "gNB-DU," "gNB-CU-CP," and "gNB-CU-UP," and further note that network nodes and RAN nodes in this disclosure may be used interchangeably and may be eNBs or gNB-CUs or eNB-CUs, gNB-DUs, or eNB-DUs. Additionally, a gNB-CU may be "represented" by a gNB-CU-CP, and / or an eNB-CU may be "represented" by an eNB-CU-CP.

[0066] One method embodiment according to the present disclosure is performed by a first network node managing the configuration of a first cell provided by a first RAN node, and the method configures at least one attribute in the first RAN node as part of a neighbor relationship configuration associated with a neighbor relationship between the first cell and a second cell provided by a second RAN node. The method determines, as part of the configured attributes, at least one function / service / application to be used on an established interface between the RAN nodes serving the first and second cells. One embodiment of this method is shown in FIG. 10. Method 1000 is performed by a first network node having the first cell to manage the configuration or neighbor relationship of the first cell with a second cell belonging to the second network node. Step 1010 configures at least one attribute in the first network node as part of a neighbor relationship configuration between the first cell and the second cell provided by the second network node. Step 1020 determines at least one function / service / application to be used over the established interface between the first network node and the second network node (e.g., resource coordination only, PRACH coordination only). Step 1030 indicates the neighbor relationship and at least one attribute to the second network node. Step 1040 may be optional, and involves receiving an acknowledgment or rejection of the neighbor relationship or the last one attribute from the second network node. After this, the interface can be established, and the function, service, or application can be executed over the interface between the first cell and the second cell.

[0067] Method 1000 may include various additional or alternative steps or modifications. In one embodiment, the neighbor relationship is configured as part of an NCRT, and the associated configuration indicates that the network interface between the RAN nodes is used only for resource coordination purposes or for dynamic spectrum sharing between neighboring cells owned by neighboring RAN nodes. In another embodiment, the neighbor relationship is configured as part of an NCRT, and the associated configuration indicates that the network interface between the RAN nodes is used only for PRACH resource coordination, e.g., to resolve contention between neighboring network nodes.

[0068] In one embodiment, the first network node and the first or second RAN node may be the same node, i.e. Neighborhood Any RAN node serving one of the cells can configure attributes that determine which functions the interface is allowed to use.

[0069] In yet another embodiment, attributes regarding permitted functions / services / applications between a first network node and a second network node are configured by an Operations, Administration, and Maintenance (OAM) node. In yet another embodiment, attributes regarding permitted functions / services / applications between a first network node and a second network node are configured by a Service Management & Orchestrator (SMO) node. The terms "function," "service," and "application" may be used interchangeably in this disclosure. Each may refer to various applications, functionality, features, services, programs, algorithms, behaviors, or other similar aspects of a network node or cell and / or its relationship with other nodes or cells.

[0070] In all of the above embodiments, the configured attributes mean that functions required to set up and maintain the interface operating in a correct and efficient manner are still performed, i.e., features such as interface setup, transport network related maintenance, configuration updates, etc. may be allowed to run even if the attributes restrict the functions that can be used on the interface.

[0071] In yet another embodiment, a first RAN node or a second RAN node (e.g., co-located at the same site) may perform resource coordination on behalf of a third RAN node that is not co-located with the first and second RAN nodes but uses the same frequency band. For example, a first network node connected to a third network node (co-located with the second network node) may coordinate shared resources with the second network node such that the second and third network nodes share the same spectrum with minimal interference levels. An embodiment of this aspect is illustrated in the method shown in FIG. 11. Method 1100 may include: Although not colocatedA method is performed by a first network node co-located with a second network node to perform resource coordination for a third network node using the same frequency band. Step 1110 is configuring a neighbor relationship for a second cell served by the second network node. Step 1120 is setting attributes of the neighbor relationship. Step 1130 is determining at least one service to be used on the established interface between the first RAN node and the second RAN node. Step 1140 is indicating the neighbor relationship and the at least one attribute to the second network node. Step 1150 is receiving an acknowledgment or rejection of the neighbor relationship or the last one attribute from the second network node. Step 1160 is coordinating one or more resources with the second network node to enable neighbor cells between the first network node and the third network node to coexist on a shared channel. In a subembodiment, the first RAN node is an LTE eNB, and the second and third network nodes are gNBs connected by an Xn interface. Note that RAN node 1 and RAN node 2 preferably ensure that RAN node 3 does not interfere with them on a co-channel cell.

[0072] In another embodiment, in method 1300 shown in FIG. 12, OAM (Operations, Administration, and Maintenance) can configure attributes for resource coordination between two nodes. In step 1310, the OAM configures attributes for "resource coordination only" use for the interface between the two nodes. In step 1320, a first network node determines, as implemented by the OAM, to establish an interface with a second network node, e.g., an EN-DC X2 interface. In step 1330, the interface is established. In step 1340, the network node determines (via attribute configuration from the OAM) that only one function, e.g., E-UTRA-NR cell resource coordination, can be used on the interface. In step 1350, the two nodes coordinate resource utilization between any of the neighboring cells without having to support all other functions enabled by the EN-DC X2 interface.

[0073] It is worth noting that the configuration from step 1310 may be provided: 1. Per neighbor (e.g., a configuration valid for all interfaces established with a given neighbor) 2. Per neighbor cell (e.g., configuration valid for all interfaces established with neighbor nodes serving a given neighbor cell). 3. Per interface (e.g., a configuration valid for a particular interface established with one or more specific neighbors), or 4. A combination of the above.

[0074] In some embodiments or variations of method 1300, one node may have a first cell that is an E-UTRA cell. Another node may have a second cell (neighboring the first cell) that is an NR cell, or vice versa. The EN-DC X2 interface may allow these cells to coordinate resources. For example, "resource coordination only" may be an attribute of NCRT. When checked, the neighbor relationship between the first cell and the second cell only allows the X2 interface to be used to coordinate resources between each other (e.g., resource coordination, dynamic spectrum sharing, PRACH resource coordination). In some embodiments, Neighborhood The cells can be on the same network or RAN node, or they can share the same gNB in ​​a split architecture.

[0075] In some embodiments, the configuration need not be provided to both nodes, but may be provided to the first node. In this case, an attempt from the second node to use a function that is not permitted by the configured attributes may result in a failure of the procedure associated with that function. A specific cause value may be provided in the failure message to allow the first node to understand that the function is not permitted to be used.

[0076] Signaling configuration between nodes Now, configuration signaling between network or RAN nodes can be described: Upon establishing neighbor relations between cells and network interfaces between nodes, the first network node indicates to the second network node the attributes determined as part of the NCRT, e.g., the set of functions / services / applications to be performed on the associated interfaces.

[0077] In one embodiment, the interface may be an EN-DC X2 interface, or generally an MR-DC Xn or NG interface. In a non-limiting example, the signal exchanging attributes may be an X2 setup or Xn setup or NG RAN Node Configuration Update according to 3GPP® standards TS 36.423 or TS 38.423. In another example, the nodes do not signal attributes to one side but rely on the configuration to know which attributes the other node is configured with. Alternatively, the nodes may not signal attributes to one side but may learn over time what capabilities are supported by neighboring nodes, for example, through failed procedures.

[0078] Example Implementation One non-limiting example implementation of the embodiments proposed in the following disclosure is shown as part of 3GPP TS 36.300 and 38.300, respectively, as described below and in FIG. 8 . System 800 includes an O&M 810 in communication with an eNB 820. The eNB 820 includes an NCRT 850 and an ANR function 830. The ANR function 830 resides within the eNB 820 and conceptually manages the NCRT 850. The ANR function 840 includes an NCRT management function 840, a neighbor removal function 880, and a neighbor detection function 890. The ANR function 830 includes a neighbor removal function 880 that removes old NCRTs. Located within the ANR function 830, the neighbor detection function 890 finds new neighbors and adds them to the NCRT 850. The neighbor detection function 890 and the neighbor removal function 880 are implementation-specific. The NCRT management function 840 can obtain received information and update the NCRT 850. The NCR management function 840 can send NCR reports to the O&M 810 and receive additions or other updates to the NCR. One aspect of the ANR function 830 is to relieve the operator from the burden of manually managing the NCR.

[0079] An embodiment of NCR in the context of the ANR functionality as shown in Figure 8 can be illustrated as follows: An existing neighbor relationship from a source cell to a target cell is established when the eNB controlling the source cell: 1. Identify the ECGI / CGI and PCI of the target cell, 2. having an entry in the NCRT for the source cell that identifies the target cell; 3. The attributes of this NCRT entry are either defined by O&M or set to default values.

[0080] For each cell that the eNB has, the eNB maintains an NCR, as shown in Figure 8. For each NCR, the NCR includes a TCI that identifies the target cell. In the case of E-UTRAN, the TCI corresponds to the ECGI and PCI of the target cell. Furthermore, each NCR has several attributes. The attributes can have the following definitions, for example: 1. No Remove: If checked, the eNB shall not remove the NCR from the NCRT. 2. No HO: If checked, NCR shall not be used by the eNB for handover reasons 3. No X2: If checked, the neighbor relationship does not use the X2 interface to initiate procedures towards the eNB parenting the target cell. 4. Unique Resource adjustment If checked, the neighbor relationship uses the X2 interface only to coordinate resources between the source and target cells. 5. Dynamic spectrum sharing only: if checked, the neighbor relationship will only use the X2 interface for dynamic spectrum sharing with the target cell; 6. PRACH Resource Coordination Only: If checked, the neighbor relationship will only use the X2 interface to coordinate PRACH resources and resolve potential PRACH contention between the source and target RAN nodes.

[0081] NCR is a relationship between cells, while X2 links are established between two eNBs. NCR is unidirectional, while X2 links are bidirectional. Neighbor information exchange that occurs during the X2 setup procedure or during the eNB configuration update procedure can be used for the ANR function. The ANR function also allows O&M to manage NCRTs. O&M can add and delete NCRs. It can also change the attributes of NCRTs. The O&M system is informed of changes to NCRTs.

[0082] ANR function for NR ANR functionality for NR can also be described. The ANR functionality described in relation to Figure 8 can be applied to enhanced NR. The existence of NCR from the source E-UTRA cell to the target NR cell means that the eNB controlling the source cell knows the NCGI and PCI of the target cell. If NCR exists from the source E-UTRA cell to the target E-UTRA cell, the eNB controlling the source cell has information on whether the target E-UTRA cell has an existing NCR to the target NR cell to perform EN-DC. An X2 link can be established between the eNB and the en-gNB. The NoRemove, NoHO, and NoX2 attributes apply when the en-gNB parent the target cell. The NCR can have the following additional attributes: 1. No EN-DC: If checked, NCR is not used by the eNB for EN-DC; 2. Resource Coordination Only: If checked, the neighbor relationship will only use the X2 interface to coordinate resources between the source and target cells; 3. Dynamic Spectrum Sharing Only: If checked, the neighbor relationship will only use the X2 interface to coordinate dynamic spectrum sharing with the target cell. 4. PRACH Resource Coordination Only: If checked, the neighbor relationship will only use the X2 interface to coordinate PRACH resources and resolve potential PRACH contention between the source and target RAN nodes.

[0083] Each E-UTRA cell contains an inter-frequency search list, which contains all frequencies that can be searched. The PCI is defined by the frequency of the Synchronization Signal Block (SSB) and NR-PCI associated with the System Information Block 1 (SIB1).

[0084] In yet another non-limiting example, a solution can be implemented in 3GPP TS 38.300, as shown in the following description of application layer initialization.

[0085] Application Layer Initialization Once SCTP connectivity is established, the NG-RAN node and its candidate peer NG-RAN node are in a position to exchange application-level configuration data via XnAP, which is required for the two nodes to interact correctly over the Xn interface: The NG-RAN node provides relevant configuration information to the candidate NG-RAN node, which in turn provides the served cell information. Candidate NG-RAN nodes provide relevant configuration information to the initiating NG-RAN node, including served cell information Once the application layer initialization is successfully completed, the dynamic configuration procedure is completed and the Xn interface is operational. · An NG-RAN node shall keep neighboring NG-RAN nodes updated with the full list of served cells, or with a limited list of served cells if requested by a peer NG-RAN node, while the Xn interface is operational.

[0086] Automatic neighboring cell relations function The automatic neighbor cell relation function can now be further described. One purpose of the ANR function is to relieve operators from the burden of manually managing NCRs. Figure 13 shows another exemplary ANR and its environment in system 1700.

[0087] The system 1700 includes an OAM 1710 and a gNB 1720. An ANR function 1740 resides within the gNB 1720 and manages the NCRT 1730. A neighbor detection function 1760, located within the ANR function 1740, is communicatively coupled to the RRC 1780 and discovers new neighbors and adds them to the NCRT 1730 via an NCRT management function 1770. The ANR function 1740 also includes a neighbor removal function 1750 that removes old NCRs via the NCR management function 1770. The neighbor detection function 1760 and the neighbor removal function 1750 are implementation specific. The ANR function 1740 also enables the OAM 1710 to manage the NCRT 1730. The OAM 1710 can add and remove NCRs. It can also change the attributes of the NCRT 1730. The OAM 1710 is notified of changes to the NCRT 1730.

[0088] The existing NCR from the source cell to the target cell is that the gNB that controls the source cell 1. Know the global and physical ID of the target cell (e.g., NR CGI / NR PCI, ECGI / PCI), 2. having an entry in the NCRT for the source cell that identifies the target cell; 3. The attributes of this NCRT entry are either defined by the OAM or set to their default values, This means that...

[0089] NCR is an inter-cell relationship, while Xn link is set up between two gNBs. NCR is unidirectional, while Xn link is bidirectional. The exchange of neighbor information that occurs during the Xn setup procedure or gNB configuration update procedure can be used for ANR purposes.

[0090] Additionally, each NCR can have several attributes, which can have the following definitions: 1. Resource Coordination Only: If checked, the neighbor relationship shall only use the X2 interface to have resources coordinated between the source and target cells; 2. Dynamic spectrum sharing only: if checked, the neighbor relationship will only use the X2 interface for dynamic spectrum sharing with the target cell; 3. PRACH Resource Coordination Only: If checked, the neighbor relationship will only use the X2 interface to coordinate PRACH resources and resolve potential PRACH contention between the source and target RAN nodes.

[0091] Automatic in the system Neighborhood Cell-related functions An intra-system automatic neighbor cell relation function may also be implemented. Some examples may help to explain such an implementation. ANR relies on the NCGI and ANR reports of E-UTRA cells as specified in TS 36.300. Figure 14 shows an example in which an NG-RAN node serving cell A has ANR functionality. In RRC_CONNECTED, the NG-RAN node instructs each UE to perform measurements on neighboring cells. The NG-RAN node may use different policies for instructing the UE on when to perform measurements and report the measurements to the NG-RAN node. This measurement method is specified in TS 38.331 and TS 36.331. In step 1910, the UE sends a measurement report for cell B. This report includes the PCI of cell B but does not include the NCGI / ECGI. When the NG-RAN node receives a UE measurement report including the PCI, the following sequence may be used: In 1920, the NG-RAN node requests the UE to read all broadcast NCGI / ECGI, TAC, RANAC (RAN Area Code), PLMN ID, and NR frequency band of neighboring NR cells using the newly discovered PCI as a parameter. To do so, the NG-RAN node in step 1920 requests the UE to read all broadcast NCGI / ECGI, TAC, RANAC (RAN Area Code), PLMN ID, and NR frequency band of neighboring NR cells. NeighborhoodAn appropriate idle period may need to be scheduled to allow the UE to read the NCGI / ECGI from the cell's broadcast channel. How the UE reads the NCGI / ECGI is specified in TS 38.331 and TS 36.331. When the UE finds the NCGI / ECGI of a new cell, in 1940, the UE reports all broadcast NCGI / ECGI to the NG-RAN node serving the cell. In addition, the UE reports all tracking area codes, RANAC, PLMN IDs, and NR frequency bands for neighboring NR cells that were read by the UE. If the detected NR cell does not broadcast SIB1, the UE may report a noSIB1 indication as specified in TS 38.331. In possible embodiments, the NG-RAN node of cell A can perform additional steps. In some embodiments, the NG-RAN node decides to add this neighbor relationship and updates the PCI and NCGI / ECGI: 1. Transport layer address lookup to the new NG-RAN node; 2. Update of NCR list; 3. If necessary, set up a new Xn interface towards this NG-RAN node.

[0092] Additionally, each Intersystem NCR can have several attributes, which can have the following definitions: 1. Resource Coordination Only: If checked, the neighbor relationship shall only use the X2 interface to have resources coordinated between the source and target cells; 2. Dynamic spectrum sharing only: if checked, the neighbor relationship will only use the X2 interface for dynamic spectrum sharing with the target cell; 3. PRACH Resource Coordination Only: If checked, the neighbor relationship will only use the X2 interface to coordinate PRACH resources to resolve potential PRACH contention between the source and target RAN nodes.

[0093] Additional Embodiments 15 illustrates an example of a communications system 2100 according to some embodiments. In this example, the communications system 2100 includes a telecommunications network 2102 including an access network 2104, such as a radio access network (RAN), and a core network 2106 including one or more core network nodes 2108. The access network 2104 includes one or more access network nodes, such as network nodes 2110a and 2110b (one or more of which may be generally referred to as network nodes 2110), or some other similar 3GPP access node or non-3GPP access point. The network nodes 2110 facilitate direct or indirect connectivity of user equipment (UE), such as connecting UEs 2112a, 2112b, 2112c, and 2112d (one or more of which may be generally referred to as UEs 2112), to the core network 2106 over one or more wireless connections.

[0094] Exemplary wireless communications over wireless connections include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for carrying information without the use of wires, cables, or other material conductors. Moreover, in various embodiments, communications system 1100 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals, whether via wired or wireless connections. Communications system 2100 may include and / or interface with any type of communications, telecommunications, data, cellular, wireless networks, and / or other similar types of systems.

[0095] The UE 2112 may be any of a wide variety of communication devices, including wireless devices, that are positioned, configured, and / or operable to communicate wirelessly with the network node 2110 and other communication devices. Similarly, the network node 2110 is positioned, capable, configured, and / or operable to communicate, directly or indirectly, with the UE 2112 and / or with other network nodes or equipment within the telecommunications network 2102 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as management within the telecommunications network 2102.

[0096] In the illustrated example, the core network 2106 connects the network node 2110 to one or more hosts, such as the host 2116. These connections may be direct or indirect through one or more intermediary networks or devices. In other examples, the network nodes may be directly coupled to the hosts. The core network 2106 includes one or more core network nodes (e.g., the core network node 2108) structured with hardware and software components. The functionality of these components may be substantially similar to that described with respect to the UEs, network nodes, and / or hosts, and thus, these descriptions are generally applicable to the corresponding components of the core network node 2108. Exemplary core network nodes include one or more of a Mobile Switching Center (MSC), a Mobility Management Entity (MME), a Home Subscriber Server (HSS), an Access and Mobility Management Function (AMF), a Session Management Function (SMF), an Authentication Server Function (AUSF), a Subscription Identifier Deciphering Function (SIDF), a Unified Data Management (UDM), a Security Edge Protection Proxy (SEPP), a Network Publishing Function (NEF), and / or a User Plane Function (UPF).

[0097] Host 2116 may be owned or controlled by, and operated by or on behalf of, a non-operator service provider or provider of access network 2104 and / or telecommunications network 2102. Host 2116 may host a variety of applications to provide one or more services. Examples of such applications include live and pre-recorded audio / video content, data collection services such as acquiring and compiling data about various ambient conditions sensed by multiple UEs, analytics functionality, social media, functionality for controlling or otherwise interacting with remote devices, functionality for alarm and monitoring centers, or any other such functionality performed by a server.

[0098] 15 enables connectivity between UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as a particular standard, including, but not limited to, Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G), a wireless local area network (WLAN) standard, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard (WiFi), and / or any other suitable wireless communication standard, such as Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC), ZigBee, LiFi, and / or any low-power wide-area network (LPWAN) standard, such as LoRa and Sigfox.

[0099] In some examples, the telecommunications network 2102 is a cellular network that implements functions standardized by 3GPP. Thus, the telecommunications network 2102 may support network slicing to provide different logical networks to different devices connected to the telecommunications network 2102. For example, the telecommunications network 2102 may provide Ultra-Reliable Low Latency Communications (URLLC) services to some UEs, while providing enhanced Mobile Broadband (eMBB) services to other UEs and massive machine type communications (mMTC) / massive IoT services to still further UEs.

[0100] In some examples, the UE 2 The UE 112 is configured to transmit and / or receive information without direct human interaction. For example, the UE may be designed to transmit information to the access network 2104 on a predetermined schedule, when triggered by an internal or external event, or in response to a request from the access network 2104. Additionally, the UE may be configured to operate in a single or multi-RAT or multi-standard mode. For example, the UE may be configured and operate in any one or combination of Wi-Fi, NR (New Radio), and LTE, i.e., for Multi-Radio Dual Connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio-Dual Connectivity (EN-DC).

[0101] In the above example, the hub 2114 communicates with the access network 2104 to facilitate indirect communication between one or more UEs (e.g., UE 2112c and / or 2112d) and a network node (e.g., network node 2110b). In some examples, the hub 2114 may be a controller, a router, a content source, an analytics, or any of the other communication devices described herein with respect to a UE. For example, the hub 2114 may be a broadband router that enables access to the core network 2106 for the UE. As another example, the hub 2114 may be a controller that sends commands or instructions to one or more actuators in the UE. The commands or instructions may be received from the UE or the network node 2110 or may be accepted by executable code, scripts, processes, or other instructions in the hub 2114. As another example, the hub 2114 may be a data collector that acts as a temporary storage for UE data and, in some embodiments, may perform analysis or other processing of that data. As another example, the hub 2114 may be a content source. For example, for UEs that are VR headsets, displays, loudspeakers, or other media delivery devices, the hub 2114 may obtain media or data related to VR assets, video, audio, or other sensory information via a network node, and then provide it to the UE either directly, after performing local processing, and / or adding additional local content. In yet another example, the hub 2114 acts as a proxy server or orchestrator for the UEs, particularly if one or more of the UEs are low-energy IoT devices.

[0102] The hub 2114 may have a constant / permanent or intermittent connection to the network node 2110b. The hub 2114 may also enable different communication schemes and / or schedules between the hub 2114 and the UEs (UEs 2112c and / or 2112d) and between the hub 2114 and the core network 2106. In other examples, the hub 2114 is connected to the core network 2106 and / or one or more UEs via a wired connection. Moreover, the hub 2114 may be configured to connect to an M2M service provider over the access network 1104 and / or to other UEs over a direct connection. In some scenarios, a UE may establish a wireless connection with the network node 2110b while still being connected via the hub 2114 via a wired or wireless connection. In some embodiments, the hub 2114 may be a dedicated hub, i.e., a hub whose primary function is to route communications between UEs and the network node 2110b. In other embodiments, the hub 2114 may be a non-dedicated hub, i.e., a device that is operable to route communications between the UE and the network node 2110b, but that is also operable as an origin and / or termination point for communications for any data channel.

[0103] 16 illustrates a UE 2200 according to some embodiments. As used herein, a UE refers to a device capable of, configured, arranged, and / or operable to communicate wirelessly with network nodes and / or other UEs. Examples of a UE include, but are not limited to, a smartphone, a mobile phone, a cell phone, a Voice over IP (VoIP) phone, a wireless local loop phone, a desktop computer, a personal digital assistant (PDA), a wireless camera, a gaming console or device, a music storage device, a playback appliance, a wearable terminal device, a wireless endpoint, a mobile station, a tablet, a laptop, a laptop embedded equipment (LEE), a laptop mounted equipment (LME), a smart device, a wireless customer premises equipment (CPE), an in-vehicle or vehicle embedded / integrated wireless device, etc. Other examples include any UE identified by 3GPP, including a Narrowband Internet of Things (NB-IoT) UE, a Machine Type Communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[0104] A UE may support device-to-device (D2D) communications, for example, by implementing 3GPP standards for sidelink communications, dedicated short-range communications (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2E). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and / or operates the associated device. Instead, a UE may represent a device (e.g., a smart sprinkler controller) that is intended for sale to or operation by a human user, but that may not, at least initially, be associated with a particular human user. Alternatively, a UE may represent a device (e.g., a smart power meter) that is not intended for sale to or operation by an end user, but that may be associated with or operated for the benefit of a user.

[0105] The UE 2200 includes a processing circuit 2202, a power source 2208, a memory 2210, a communication interface 2212, and / or any other components, or any combination thereof, operably coupled via a bus 2204 to an input / output interface 2206. A given UE may utilize all or a subset of the components shown in FIG. 16. The level of integration between components may vary from one UE to another. Furthermore, a given UE may include multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0106] The processing circuitry 2202 is configured to process instructions and data, and may be configured to implement any sequential state machine operable to execute instructions stored as a machine-readable computer program in memory 2210. The processing circuitry 2202 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, a field programmable gate array (FPGA), an application-specific integrated circuit (ASIC), etc.), programmable logic with appropriate firmware, one or more stored computer programs, a general-purpose processor such as a microprocessor or digital signal processor (DSP) with appropriate software, or any combination of the above. For example, the processing circuitry 2 202 may include multiple central processing units (CPUs).

[0107] In the above example, the input / output interface 2206 may be configured to provide one or more interfaces for an input device, an output device, or one or more input / output devices. Examples of output devices include speakers, sound cards, video cards, displays, monitors, printers, actuators, emitters, smart cards, other output devices, or any combination thereof. An input device may enable a user to capture information from the UE 2200. Examples of input devices include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, digital video camera, webcam, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, and a smart card. A presence-sensitive display may include a capacitive or resistive touch sensor for sensing input from a user. The sensor may be, for example, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetic sensor, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as the input device. For example, a universal serial bus (USB) port may be used to provide an input device and an output device.

[0108] In some embodiments, the power source 2208 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electrical outlet), a photovoltaic device, or a battery, may also be used. The power source 2208 may further include power circuitry for transferring power from the power source 2208 itself and / or the external power source to various parts of the UE 2200 via interfaces, such as input circuits or power cables. The power transfer may be for charging the power source 2208, for example. The power circuitry may perform some shaping, conversion, or other modification of the power from the power source 2208 to make it suitable for the respective components of the UE 2200 that it powers.

[0109] The memory 2210 may be or be configured to include random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disk, optical disk, hard disk, removable cartridge, flash drive, etc. In one example, the memory 2210 includes one or more application programs 2214, such as an operating system, a web browser application, a widget, a gadget engine, or other applications, and corresponding data 22216. The memory 2210 may store any of a wide variety of operating systems or combinations of operating systems for use by the UE 2100.

[0110] The memory 2210 may be configured to include multiple physical drive units such as a redundant array of independent disks (RAID), flash memory, a USB flash drive, an external hard disk drive, a thumb drive, a pen drive, a key drive, a high-density digital versatile disc (HD-DVD), an optical disk drive, an internal hard disk drive, a Blu-ray optical disk drive, a holographic digital data storage (HDDS) optical disk drive, an external mini-DIMM (Dual In-Line Memory Module), a synchronous dynamic random access memory (SDRAM), an external micro-DIMM (SDRAM), a smart card memory such as a tamper-resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs) such as a USIM and / or an ISIM, other memory, or any combination thereof. The UICC may be, for example, an embedded UICC (eUICC), an integrated UICC (iUICC), or a removable UICC commonly known as a "SIM card." The memory 2210 may enable the UE 2200 to access instructions, application programs, and the like stored on a temporary or non-transitory storage medium to offload or upload data. An item of manufacture, such as one utilizing a communication system, may be tangibly embodied as or within the memory 2210, which may be or include a device-readable storage medium.

[0111] The processing circuit 2202 may be configured to communicate with an access network or other networks using a communication interface 2212. The communication interface 2212 may include one or more communication subsystems and may include or be communicatively coupled to an antenna 2222. The communication interface 2212 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of other devices capable of wireless communication (e.g., other UEs or network nodes within the access network). Each transceiver may include a transmitter 2218 and / or receiver 2220 appropriate for providing network communications (e.g., optical, electrical, frequency-assigned, etc.). Moreover, the transmitter 2218 and receiver 2220 may be coupled to one or more antennas (e.g., antenna 2222), which may share circuit components, software, or firmware, or may alternatively be implemented separately.

[0112] In the illustrated embodiment, the communication interface 2 The communication capabilities of 212 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communication such as Bluetooth, near-field communication, location-based communication such as using the Global Positioning System (GPS) for determining location, other similar communication capabilities, or any combination thereof. Communication may be implemented according to one or more communication protocols and / or standards, such as, for example, IEEE 802.11, Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, Transmission Control Protocol / Internet Protocol (TCP / IP), Synchronous Optical Networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), etc.

[0113] Regardless of the type of sensor, the UE must have its own communication interface.2 212 to a network node via a wireless connection. Data captured by the UE's sensors may be communicated via other UEs to the network node via a wireless connection. The output may be periodic (e.g., once every 15 minutes when reporting sensed temperature), random (e.g., to balance the load of notifications from multiple sensors), in response to a triggering event (e.g., moisture detected and an alert sent), on request (e.g., a user initiated request), or as a continuous stream (e.g., a live video feed of a patient).

[0114] As another example, the UE may include an actuator, motor, or switch associated with a communications interface configured to receive wireless input from a network node via a wireless connection. The state of the actuator, motor, or switch may change in response to the received wireless input. For example, the UE may include a motor that adjusts a control surface or rotor of a drone in flight in accordance with the received input, or a robotic arm that performs a medical procedure in accordance with the received input.

[0115] If the UE is in the form of an Internet of Things (IoT) device, it may be a device for use in one or more application domains, including but not limited to wearable technology in the city, extended industrial applications, and healthcare. Non-limiting examples of such IoT devices include, or are incorporated into, devices such as a connected refrigerator or freezer, a TV, a connected lighting fixture, an electric meter, a robot vacuum, a voice-controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electric door lock, a connected doorbell, an air conditioning system such as a heat pump, an autonomous vehicle, a surveillance system, a weather monitor, a vehicle parking monitor, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for augmented reality (AR) or virtual reality (VR), a wearable for haptic augmentation or sensory enhancement, a water sprinkler, an animal or object tracker, a sensor for monitoring plants or animals, an industrial robot, an unmanned aerial vehicle (UAV), and any type of medical device such as a heart rate monitor or a remote-controlled surgical robot. A UE in the form of an IoT device comprises other components such as those described in connection with the UE 2200 shown in FIG. 16, in addition to circuitry and / or software depending on the intended application of the IoT device.

[0116] As yet another specific example, in an IoT scenario, a UE may represent a machine or other device that performs monitoring and / or measurements and transmits the results of such monitoring and / or measurements to other UEs and / or network nodes. The UE, in this case, may be an M2M device, which may also be referred to as an MTC device in the 3GPP® context. As one example, the UE may implement the 3GPP® NB-IoT standard. In other scenarios, the UE may represent a car, truck, ship, or aircraft, or other equipment that can monitor and / or report on its operational status or other functionality associated with its operation.

[0117] In practice, any number of UEs may be used together for a single use case. For example, a first UE may be a drone or integrated into a drone and provide drone speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When a user makes changes from the remote controller, the first UE may adjust the drone's throttle (e.g., by controlling an actuator) to increase or decrease the drone's speed. The first and / or second UE may also include more than one of the above-described functionalities. For example, a UE may include a sensor and an actuator and handle communication of data for both the speed sensor and the actuator.

[0118] 17 illustrates a network node 3300 according to some embodiments. As used herein, a network node refers to a device that is capable of, configured, arranged, and / or operable to communicate directly or indirectly with UEs and / or other network nodes or devices in a telecommunications network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., wireless access points) and base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs), and NR Node Bs (gNBs)).

[0119] Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power levels), and thus may be referred to as femto, pico, micro, or macro base stations, depending on the amount of coverage provided. A base station may also be a relay node or a relay donor node that controls a relay. A network node may include one or more (or all) parts of a distributed radio base station, such as a centralized digital unit and / or a remote radio unit (RRU), sometimes referred to as a remote radio head (RRH). Such remote radio units may or may not be integrated with an antenna, such as an antenna-integrated radio. Some distributed radio base stations may also be referred to as nodes in a distributed antenna system (DAS).

[0120] Other examples of network nodes include multi-transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as an MSR BS, a network controller such as a radio network controller (RNC) or base station controller (BSC), a base transceiver station (BTS), a transmission point, a transmitting node, a multi-cell / multicast coordination entity (MCE), an operation and maintenance (O&M) node, an operation support system (OSS) node, a self-organizing network (SON) node, a positioning node (e.g., an evolved serving mobile location center (E-SMLC) and / or a minimized drive test (MDT).

[0121] The network node 3300 includes a processing circuit 3302, a memory 3304, a communication interface 3306, and a power source 3308. The network node 3300 may be composed of multiple physically separate components (e.g., a Node B component and an RNC component, or a BTS component and a BSC component, etc.), each of which may have its own respective components. In some scenarios in which the network node 3300 includes multiple separate components (e.g., a BTS and a BSC component), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple Node Bs. In such scenarios, each unique pair of Node B and RNC may, in some examples, be considered a single separate network node. In some embodiments, the network node 3300 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be redundant (e.g., separate memories 3304 for different RATs) and some components may be reused (e.g., the same antenna 3310 may be shared by different RATs). The network node 3300 may also include multiple sets of the various illustrated components for different wireless technologies, such as GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, RFID (Radio Frequency Identification), or Bluetooth wireless technologies, that are integrated into the network node 3300. The wireless technologies may be integrated into the same or different chips or chipsets and other components within the network node 3300.

[0122] The processing circuitry 3302 may include one or more combinations of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application specific integrated circuit, field programmable gate array, or other suitable computing device, resources, or combination of hardware, software, and / or coded logic operable, alone or in conjunction with other network node 3300 components, such as memory 3304, to provide the functionality of the network node 3300.

[0123] In some embodiments, the processing circuit 3302 comprises a system on a chip (SOC). In some embodiments, the processing circuit 3302 includes one or more of a radio frequency (RF) transceiver circuit 3312 and a baseband processing circuit 3314. In some embodiments, the radio frequency (RF) transceiver circuit 3312 and the baseband processing circuit 3314 may be on separate chips (or chipsets), boards, or units, such as a radio unit and a digital unit. In alternative embodiments, some or all of the RF transceiver circuit 3312 and the baseband processing circuit 3314 may be on the same chip or chipset, board, or unit.

[0124] The memory 3304 may include any form of volatile or non-volatile computer-readable memory, including, but not limited to, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (e.g., hard disk), removable storage media (e.g., flash drive, compact disc (CD) or digital video disc (DVD)), and / or any other volatile or non-volatile non-transitory device-readable and / or computer-executable memory device that stores information, data and / or instructions that can be used by the processing circuit 3302. The memory 3304 may store any suitable instructions, data or information, including applications, including one or more of computer programs, software, logic, rules, code, tables, and / or other instructions, that are executable by the processing circuit 3302 and usable by the network node 3300. The memory 3304 may be used to store any computational results produced by the processing circuit 3302 and / or any data received via the interface 3306. In some embodiments, the processing circuit 3302 and the memory 3304 are integrated.

[0125] The communications interface 3306 is used for wired or wireless communication of signaling and / or data between network nodes, access networks, and / or UEs. As shown, the communications interface 3306 includes a port / terminal 3316 for transmitting and receiving data to and from a network over a wired connection, for example. The communications interface 3306 also includes radio front-end circuitry 3318, which is coupled to the antenna 3310 or, in some embodiments, may be part of the antenna 3310. The radio front-end circuitry 3318 includes a filter 3320 and an amplifier 3322. The radio front-end circuitry 3318 may be connected to the antenna 3310 and the processing circuitry 3302. The radio front-end circuitry may be configured to condition signals communicated between the antenna 3310 and the processing circuitry 3302. The radio front-end circuitry 3318 may accept digital data to be sent to another network node or UE over a wireless connection. The radio front-end circuitry 3318 may convert the digital data into a radio signal having appropriate channel and bandwidth parameters using a combination of filters 3320 and / or amplifiers 3322. The radio signal may then be transmitted via the antenna 3310. Similarly, when data is received, the antenna 3310 collects the radio signal, which may then be converted into digital data by the radio front-end circuitry 33318. The digital data may be passed to the processing circuitry 3302. In other embodiments, the communication interface may include different components and / or different combinations of components.

[0126] In an alternative embodiment, the network node 3300 may not include a separate radio front-end circuit 3318; rather, the processing circuit 3302 may include the radio front-end circuitry and may be connected to the antenna 3310. Similarly, in some embodiments, all or some of the RF transceiver circuitry 3312 is part of the communications interface 3306. In yet another embodiment, the communications interface 3306 includes one or more ports or terminals 3316, the radio front-end circuitry 3318, and the RF transceiver circuitry 3312 as part of a radio unit (not shown), and the communications interface 3306 communicates with baseband processing circuitry 3314 that is part of a digital unit (not shown).

[0127] The antenna 3310 may include one or more antennas or an antenna array configured to transmit and / or receive wireless signals. The antenna 3310 may be coupled to the radio front end circuitry 3318 and may be any type of antenna capable of wirelessly transmitting and receiving data and / or signals. In some embodiments, the antenna 3310 is separate from the network node 3300 and connectable to the network node 3300 through an interface or port.

[0128] The antenna 3310, the communication interface 3316, and / or the processing circuit 3302 may be configured to perform any receiving operation and / or certain acquisition operation described herein as being performed by a network node. Any information, data, and / or signals may be received from a UE, another network node, and / or any other network equipment. Similarly, the antenna 3310, the communication interface 3306, and / or the processing circuit 3302 may be configured to perform any transmitting operation described herein as being performed by a network node. Any information, data, and / or signals may be transmitted to a UE, another network node, and / or any other network equipment.

[0129] The power supply 3308 provides power to the various components of the network node 3300 in a format appropriate for each component (e.g., at the voltage and current levels required for each component). The power supply 3308 may include or be coupled to power management circuitry for providing power to the components of the network node 3300 to perform the functionality described herein. For example, the network node 3300 may be connectable to an external power source (e.g., a power grid, an electrical outlet) via an input circuit or interface such as an electrical cable, whereby the external power source provides power to the power circuitry of the power supply 3308. As a further example, the power supply 3308 may include a source of power in the form of a battery or battery pack connected to or integrated into the power circuitry. The battery may provide backup power in case of failure of the external power source.

[0130] Embodiments of network node 3300 may include additional components other than those shown in Figure 18 to provide certain aspects of the network node's functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, network node 3300 may include user interface devices that allow information to be input into and output from network node 3300. This may enable a user to perform diagnostic, maintenance, repair, and other administrative functions on network node 3300.

[0131] 18 is a block diagram of a host 4400, which may be an embodiment of the host 2116 of FIG. 15, in accordance with various aspects described herein. As used herein, the host 4400 may be or include hardware and / or software in various combinations, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, a container, or processing resources within a server farm. The host 4400 may provide one or more services to one or more UEs.

[0132] The host 4400 includes a processing circuit 4402, a network interface 4408, a power supply 4410, and memory 4412 operably coupled via a bus 4404 to an input / output interface 4406. In other embodiments, other components may be included, the functionality of which may be substantially similar to those described with respect to the devices in previous figures, such as Figures 17 and 18, and therefore those descriptions are generally applicable to the corresponding components of the host 4400.

[0133] Memory 4412 may include one or more computer programs, including one or more host application programs 4414, and data 4416, which may include user data, such as data generated by a UE for the host 4400 or data generated by the host 4400 for the UE. An embodiment of the host 4400 may utilize only a subset or all of the illustrated components. The host application programs 4414 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for different UE classes, types, or implementations (e.g., handsets, desktop computers, wearable display systems, heads-up display systems). Additionally, the host application programs 4 Host 4400 may also provide user authentication and license checks, and may periodically report health, route, and content availability to a central node, such as a device in or at the edge of the core network. Thus, Host 4400 may select and / or point to different hosts for over-the-top services for the UE. Host application program 4414 may support a variety of protocols, such as HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc.

[0134] FIG. 19 is a block diagram illustrating a virtualization environment 5500 in which functionality implemented according to some embodiments may be virtualized. In this context, virtualization means for creating a virtual version of an apparatus or device may include a virtualized hardware platform, storage devices, and networking resources. As used herein, virtualization may apply to any device or component thereof described herein and refers to implementations in which at least a portion of its functionality is implemented as one or more virtual components. Some or all of the functionality described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented within one or more virtual environments 5500 hosted by one or more hardware nodes, such as a network node, a UE, a core network node, or a hardware computing device acting as a host. Furthermore, in embodiments in which a virtualized node does not require wireless connectivity (e.g., a core network node or host), the node may be virtualized in its entirety.

[0135] An application 5502 (which may alternatively be referred to as a software instance, a virtual appliance, a network function, a virtual node, a virtual network function, etc.) runs in the virtualized environment 5500 to implement some of the features, functionality and / or benefits of some of the embodiments disclosed herein.

[0136] The hardware 5504 may include processing circuitry, memory storing software and / or instructions executable by the processing circuitry, and / or hardware devices as described herein, such as network interfaces and input / output interfaces. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 5506 (also referred to as a hypervisor or virtual machine monitor (VMM)), provide VMs 5508a and 5508b (one or more of which may be collectively referred to as VMs 5508), and / or perform any of the functions, features, and / or benefits described in connection with some embodiments described herein. The virtualization layer 5506 may present a virtual operating platform that appears to the virtual machines 5508 as networking hardware.

[0137] The VMs 5508 may include virtual processing, virtual memory, virtual networking or interfaces, and virtual storage, and may be executed by a corresponding virtualization layer 5506. Various embodiments of instances of virtual appliances 5502 may be implemented in one or more of the VMs 5508, and the implementation may be done in various ways. Hardware virtualization is referred to in some contexts as network functions virtualization (NFV). NFV may be used to aggregate many network equipment types into industry-standard, high-capacity server hardware, physical switches, and physical storage that may be located in data centers and customer premises equipment.

[0138] In the context of NFV, a VM 5508 may be a software implementation of a physical machine that runs programs as if they were running on a physical, non-virtualized machine. Each VM 5508 and the portion of hardware 5504 on which it runs, whether the hardware is dedicated to that VM and / or shared by that VM with other VMs, forms a separate virtual network element. Also in the context of NFV, a virtual network function is responsible for handling specific network functions running in one or more VMs 5508 on top of the hardware 5504 and corresponds to the application 5502.

[0139] The hardware 5504 may be implemented in a standalone network node with generic or proprietary components. The hardware 5504 may implement some functions via virtualization. Alternatively, the hardware 5504 may be part of a larger hardware cluster (e.g., in a data center or CPE) where multiple hardware nodes cooperate and are managed via a management and orchestration 5510, which oversees, among other things, the lifecycle management of the application 5502. In some embodiments, the hardware 5504 is coupled to one or more radio units, each including one or more transmitters and one or more receivers, which may be coupled to one or more antennas. The radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces or may be used in combination with virtual components, such as radio access nodes or base stations, to provide wireless capabilities to virtual nodes. In some embodiments, some signaling may be provided with the use of a control system 5512, which may alternatively be used for communication between the hardware nodes and the radio units.

[0140] 20 illustrates a communication diagram of a host computer 6602 communicating with a UE 6606 via a network node 6604 over a partially wireless connection according to some embodiments. Exemplary implementations according to various embodiments of the UE (UE 2112a of FIG. 15 and / or UE 2200 of FIG. 16), network node (network node 2110a of FIG. 15 and / or network node 3300 of FIG. 17), and host (host 2116 of FIG. 15 and / or host 4400 of FIG. 18) discussed in the preceding paragraphs will now be described with reference to FIG. 20.

[0141] Similar to the host 4400, an embodiment of the host 6602 includes hardware such as a communications interface, processing circuitry, and memory. The host 6602 also includes software stored within or accessible by the host 6602 and executable by the processing circuitry. The software includes a host application that may be operable to provide services to a remote user, such as a UE 6606, connecting via an over-the-top (OTT) connection 6650 extending between the UE 6606 and the host 6602. During the provision of services to the remote user, the host application may provide user data that is transmitted using the OTT connection 6650.

[0142] The network node 6604 includes hardware that enables communication with the host 6602 and the UE 6606. The connection 6660 may be direct or may pass through one or more other intermediate networks, such as a core network (such as the core network 2106 of FIG. 15) and / or one or more public, private, or hosted networks. For example, the intermediate network may be a backbone network or the Internet.

[0143] The UE 6606 also includes software stored within or accessible by the UE 6606 and executable by the UE's processing circuitry. This software includes client applications, such as a web browser or operator-specific "apps," that, with the support of the host 6602, may be operable to provide services to a human or non-human user via the UE 6606. Host applications running on the host 6602 may communicate with client applications running on the host 6602 via an OTT connection 6650 that terminates at the UE 6606 and the host 6602. During the provision of services to the user, the client applications on the UE may receive request data from the host applications on the host and provide user data in response to the request data. The OTT connection 6650 may transport both the request data and user data. The client applications on the UE may interact with the user to generate user data that they provide to the host applications over the OTT connection 6650.

[0144] The OTT connection 6650 may extend via a connection 6660 between the host 6602 and the network node 6604 and via a wireless connection 6670 between the network node 6604 and the UE 6606, providing connectivity between the host 6602 and the UE 6606. The connection 6660 and the wireless connection 6670 over which the OTT connection 6650 may be provided are depicted abstractly to illustrate communication between the host 6602 and the UE 6606 via the network node 6604 without explicit reference to any intermediate devices and the precise routing of messages through those devices.

[0145] As an example of transmitting data over the OTT connection 6650, in step 6608, the host 6602 provides user data, which may be done by executing a host application. In some embodiments, the user data is associated with a specific human user interacting with the UE 6606. In other embodiments, the user data is associated with the UE 6606 sharing data with the host 6602 without explicit human interaction. In step 6610, the host 6602 initiates a transmission to the UE 6606 carrying user data. The host 6602 may initiate the transmission in response to a request sent by the UE 6606. The request may be triggered by human interaction with the UE 6606 or by the operation of a client application running on the UE 6606. The transmission may pass through the network node 6604 in accordance with the teachings of embodiments described throughout this disclosure. In response, at step 6612, the network node 6604 transmits the user data carried in the transmission initiated by the host 6602 to the UE 6606, in accordance with the teachings of embodiments described throughout this disclosure. At step 6614, the UE 6606 receives the user data carried in the transmission, which may be done by a client application executing on the UE 6606 that is associated with a host application executed by the host 6602.

[0146] In some examples, the UE 6606 executes a client application, which provides user data destined for the host 6602. The user data may be provided in reaction or response to receiving data from the host 6602. In response, the UE 6606 may provide the user data in step 6616, which may be done by executing the client application. During the provision of the user data, the client application may further consider user input received from a user via an input / output interface of the UE 6606. Regardless of the specific manner in which the user data is provided, the UE 6606 initiates transmission of the user data to the host 6602 via the network node 6604 in step 6618. In step 6620, the network node 6604 receives the user data from the UE 6606 and initiates transmission of the received user data to the host 6602, in accordance with the teachings of embodiments described throughout this disclosure. In step 6622, the host 6602 receives the user data carried in the transmission initiated by the UE 6606.

[0147] One or more of the various embodiments improve the performance of OTT services provided to the UE 6606 using the OTT connection 6650, of which the wireless connection 6670 forms the final segment. More precisely, the teachings of these embodiments may improve data rates, latency, and power consumption, thereby providing benefits such as reduced user wait times, relaxed constraints on file sizes, improved content resolution, better responsiveness, and increased battery life.

[0148] In an example scenario, factory status information may be collected and analyzed by the host 6602. As another example, the host 6602 may process audio and video data, possibly obtained from UEs, for use in generating maps. As another example, the host 6602 may collect and analyze real-time data to assist in vehicular congestion control (e.g., traffic light control). As another example, the host 6602 may store surveillance video uploaded by UEs. As another example, the host 6602 may store or control access to media content, such as video, audio, VR, or AR, that may be broadcast, multicast, or unicast to UEs. As another example, the host 6602 may be used for energy pricing, remote control of non-time-critical power loads for balancing power generation needs, location services, presentation services (e.g., compiling diagrams from data collected from remote devices), or any other function that collects, acquires, stores, analyzes, and / or transmits data.

[0149] In some examples, measurement procedures may be provided to monitor data rates, latency, and other factors that are improved by one or more embodiments. There may also be optional network functionality for reconfiguring the OTT connection 6650 between the host 6602 and the UE 6606 in response to fluctuations in the measurements. The measurement procedures and / or network functionality for reconfiguring the OTT connection may be implemented in software and hardware in the host 6602 and / or the UE 6606. In some embodiments, sensors (not shown) may be deployed in or associated with other devices through which the OTT connection 6650 passes, and these sensors may participate in the measurement procedures by providing values ​​for the monitored quantities exemplified above or other physical quantities from which the monitored quantities may be calculated or estimated by software. Reconfiguration of the OTT connection 6650 may include message formats, retransmission settings, preferred routing, etc., and the reconfiguration need not directly change the operation of the network node 6604. Such procedures and functionality may be known or practiced in the art. In one embodiment, the measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation time, latency, etc. by the host 6602. The measurements may be implemented by software sending messages over the OTT connection 6650, specifically empty or "dummy" messages, while monitoring propagation time, errors, etc.

[0150] While the computing devices (e.g., UEs, network nodes, hosts) described herein may include combinations of the illustrated hardware components, other embodiments may include computing devices with different combinations of components. It should be understood that the computing devices may include any suitable combination of hardware and / or software required to perform the tasks, features, functions, and methods disclosed herein. The determining, calculating, obtaining, or similar operations described herein may be performed by processing circuitry, which may process information by, for example, transforming the obtained information into other information, comparing the obtained or transformed information with information stored at a network node, and / or performing one or more operations based on the obtained or transformed information, and making a decision as a result of the processing. Moreover, while components are depicted as single boxes located within larger boxes or nested within multiple boxes, in reality, the computing device may include multiple different physical components that make up the illustrated single component, and functionality may be partitioned among the separate components. For example, a communication interface may be configured to include any of the components described herein, and the functionality of those components may be partitioned between the processing circuitry and the communication interface. In other examples, the computationally less intensive functions of any of these components may be implemented in software or firmware, and the computationally intensive functions may be implemented in hardware.

[0151] In some embodiments, some or all of the functionality described herein may be provided by a processing circuit executing instructions stored in a memory, which in some embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by a processing circuit, such as in a hardwired manner, without executing instructions stored on a separate or discrete device-readable storage medium. In any of these specific embodiments, the processing circuit can be configured to perform the described functionality regardless of whether it executes instructions stored on a non-transitory computer-readable storage medium. Benefits provided by such functionality are not limited to just the processing circuit or other components of the computing device, but are enjoyed by the computing device as a whole and / or by end users and wireless networks in general.

[0152] Computer system of the present disclosure It will be appreciated that computer systems take an increasingly wide variety of forms. As used herein and in the claims, the terms “controller,” “computer system,” or “computing system” are broadly defined to include any device or system, or combination thereof, that includes at least one physical and tangible processor and physical and tangible memory capable of having computer-executable instructions thereon that can be executed by the processor. By way of example and not limitation, the term “computer system” or “computing system,” as used herein, is intended to include personal computers, desktop computers, laptop computers, tablets, handheld devices (e.g., cell phones, PDAs, pagers), microprocessor-based or programmable consumer electronics, minicomputers, mainframe computers, multiprocessor systems, network PCs, distributed computing systems, data centers, message processors, routers, switches, and even devices not traditionally considered computing systems, such as wearables (e.g., eyeglasses).

[0153] Memory may take any form and may depend on the nature and form of the computing system. Memory may be physical system memory including volatile memory, non-volatile memory, or some combination of the two. The term "memory" may also be used herein to refer to non-volatile mass storage devices such as physical storage media.

[0154] Additionally, a computing system has multiple structures that are often referred to as "executable components"; for example, a computing system's memory may contain executable components. The term "executable component" is a name for a structure that is well understood by those skilled in the art of computing to be a structure that may be software, hardware, or a combination thereof.

[0155] For example, those skilled in the art will understand that when implemented in software, the structure of an executable component may include software objects, routines, methods, etc. that may be executed by one or more processors on a computing system, whether such executable components reside in the heap of the computing system or whether the executable components reside on a computer-readable storage medium. The structure of the executable component resides on the computer-readable medium in a form that, when executed by one or more processors of the computing system, is operable to cause the computing system to perform one or more functions, such as the functions and methods described herein. Such a structure may be directly computer-readable by the processor, such as when the executable component is binary. Alternatively, the structure may be structured to be interpretable and / or compilable, whether in a single step or multiple steps, to generate such a binary that is directly interpretable by the processor.

[0156] The term "executable component" will also be well understood by those skilled in the art to include structure that is implemented exclusively or nearly exclusively in hardware logic components, such as field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), program specific standard products (ASSPs), system-on-chip systems (SOCs), complex programmable logic devices (CPLDs), or any other specialized circuitry. Thus, the term "executable component" is a term for structure that is well understood by those skilled in the art of computing, whether implemented in software, hardware, or a combination thereof.

[0157] The terms "component," "service," "engine," "module," "control," "generator," etc. may also be used in this description. As used herein and in this case, these terms, whether expressed with or without a modifier, are also intended to be synonymous with the term "executable component," and as such, also have a structure well understood by those skilled in the computing arts.

[0158] In one embodiment, a communication system may include a complex of computing devices that perform any of the methods of the above-described embodiments and data storage devices, which may be server parks and data centers.

[0159] With respect to computer implementation, a computer is generally understood to include one or more processors or one or more controllers, and the terms computer, processor, and controller may be used interchangeably. When provided by a computer, processor, or controller, the functions may be provided by a single dedicated computer or processor or controller, by a single shared computer or processor or controller, or by multiple individual computers or processors or controllers, some of which may be shared or distributed. Furthermore, the term "processor" or "controller" also refers to other hardware capable of performing such functions and / or running software, such as the exemplary hardware listed above.

[0160] In general, various exemplary embodiments may be implemented in hardware or dedicated chips, circuits, software, logic, or any combination thereof. For example, some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software that may be executed by a controller, microprocessor, or other computing device, although the present disclosure is not limited thereto. While various aspects of exemplary embodiments of the present disclosure may be illustrated and described as block diagrams, flowcharts, or using some other graphical representation, it is fully understood that these blocks, apparatus, systems, techniques, or methods described herein may be implemented in, by way of non-limiting example, hardware, software, firmware, dedicated circuits or logic, general-purpose hardware or controller, or other computing device, or some combination thereof.

[0161] While not all computing systems require a user interface, some embodiments include a user interface for use in communicating information to and from a user. A user interface can include output mechanisms as well as input mechanisms. The principles described herein are not limited to the exact output or input mechanisms, as such will depend on the nature of the device. However, output mechanisms can include, for example, speakers, displays, tactile output, projection, holograms, etc. Examples of input mechanisms can include, for example, microphones, touchscreens, projection, holograms, cameras, keyboards, stylus, mouse or other pointer input, any type of sensor, etc.

[0162] Accordingly, the embodiments described herein may comprise or utilize special-purpose or general-purpose computing systems. The embodiments described herein also include physical and other computer-readable media for carrying or storing computer-executable instructions and / or data structures. Such computer-readable media may be any available media that can be accessed by a general-purpose or special-purpose computing system. Computer-readable media that store computer-executable instructions are physical storage media. Computer-readable media that carry computer-executable instructions are transmission media. Thus, by way of example, and not limitation, the embodiments disclosed or contemplated herein may include at least two distinctly different types of computer-readable media: storage media and transmission media.

[0163] Computer-readable storage media include RAM, ROM, EEPROM, solid-state drives ("SSD"), flash memory, phase-change memory ("PCM"), CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other physical and tangible storage medium that can be used to store desired program code in the form of computer-executable instructions or data structures, and that can be accessed and executed by a general-purpose or special-purpose computing system to implement the disclosed functions or functionality. For example, computer-executable instructions can be embodied on one or more computer-readable storage media to form a computer program product.

[0164] Transmission media can be used to carry desired program code in the form of computer-executable instructions or data structures and can include networks and / or data links that can be accessed and executed by a general-purpose or special-purpose computing system. Combinations of the above should also be included within the scope of computer-readable media.

[0165] Additionally, upon reaching various computing system components, program code in the form of computer-executable instructions or data structures may be automatically transferred from transmission media to storage media (or vice versa). For example, computer-executable instructions or data structures received over a network or data link may be buffered in RAM within a network interface module (e.g., a "NIC") and then ultimately transferred to computing system RAM and / or a less volatile storage medium within the computing system. Thus, it should be understood that storage media may be included in computing system components that also or primarily utilize transmission media.

[0166] Those skilled in the art will further appreciate that a computing system may also include communication channels that enable it to communicate with other computing systems, for example, over a network. Accordingly, the methods described herein may be implemented in network computing environments having many types of computing systems and computing system configurations. The disclosed methods may also be implemented in distributed system environments in which local and / or remote computing systems that are linked via a network (either by wired data links, wireless data links, or a combination of wired and wireless data links) both perform tasks. In a distributed system environment, processing power, memory power, and / or storage power may also be distributed.

[0167] Those skilled in the art will also understand that the disclosed methods can be implemented in a cloud computing environment. A cloud computing environment may be distributed, but this is not required. When distributed, a cloud computing environment can have components that are distributed internationally within an organization and / or owned across multiple organizations. For purposes of this specification and the claims that follow, "cloud computing" is defined as a model for enabling on-demand network access to a shared pool of configurable computing resources (e.g., networks, servers, storage, applications, and services). The definition of "cloud computing" is not limited to any of the many other benefits that can be obtained from such a model when properly deployed.

[0168] Cloud computing models may consist of various characteristics such as on-demand self-service, pervasive network access, resource pooling, rapid elasticity, measured service, etc. Cloud computing models may also take the form of various service models, such as, for example, Software as a Service (SaaS), Platform as a Service (PaaS), and Infrastructure as a Service (IaaS). Cloud computing models may also be deployed using different deployment models, such as private cloud, community cloud, public cloud, hybrid cloud, etc.

[0169] Abbreviations and Definitions To aid in understanding the scope and content of the specification and appended claims, certain selected terms are directly defined below. Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs.

[0170] The terms "approximately," "about," and "substantially," as used herein, refer to an amount or condition that is close to a particular stated amount or condition that still performs a desired function or achieves a desired result. For example, the terms "approximately," "about," and "substantially" can refer to an amount or condition that deviates from the specifically stated amount or condition by less than 10%, or less than 5%, or less than 1%, or less than 0.1%, or less than 0.01%.

[0171] Various aspects of the present disclosure, including devices, systems, and methods, may be described with reference to one or more embodiments or implementations that are exemplary in nature. As used herein, the term "instance" means "serving as an instance, instance, or instance" and should not necessarily be construed as preferred or advantageous over other embodiments disclosed herein. Additionally, reference to "implementing" the present disclosure or an embodiment includes specific reference to one or more embodiments thereof, and vice versa, and is intended to provide illustrative examples without limiting the scope of the present disclosure, which is indicated by the appended claims and not by this specification.

[0172] As used herein, words appearing in the singular include their plural counterparts, and words appearing in the plural include their singular counterparts unless implicitly or explicitly understood or stated otherwise. Accordingly, as used herein and in the appended claims, it should be noted that the singular forms "a," "an," and "the" include plural referents unless the context clearly dictates otherwise. For example, a reference to a singular referent (e.g., "widget") includes one, two, or more referents unless implicitly or explicitly understood or stated otherwise. Similarly, a reference to a plural referent should be interpreted as including a single referent and / or multiple referents unless the content and / or context clearly dictate otherwise. For example, a reference to a plural referent (e.g., "widget") does not necessarily require a plurality of such referents. Instead, it will be understood that one or more references are contemplated herein, regardless of the number of references inferred, unless otherwise stated.

[0173] References herein to "one embodiment," "embodiment," "exemplary embodiment," etc. indicate that the described embodiment may include a particular feature, structure, or characteristic, but not all embodiments need include the particular feature, structure, or characteristic. Moreover, such phrases do not necessarily refer to the same embodiment. Furthermore, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments, whether or not explicitly described.

[0174] Although terms such as "first" and "second" may be used herein to describe various elements, it should be understood that these elements are not limited by these terms. These terms are used only to distinguish one element from another. For example, a first element can be referred to as a second element, and similarly, a second element can be referred to as a first element, without departing from the scope of the exemplary embodiments. As used herein, the term "and / or" includes any and all combinations of one or more of the associated listed terms.

[0175] It will be further understood that the terms "comprises," "comprising," "has," "having," "includes," and / or "including," as used herein, specify the presence of stated features, elements, and / or components, etc., but do not exclude the presence or addition of one or more other features, elements, and / or combinations thereof.

[0176] conclusion The present disclosure includes any novel feature or combination of features disclosed herein, either explicitly or in any generalization thereof. Various modifications and adaptations to the foregoing exemplary embodiments of the present disclosure may become apparent to those skilled in the art in view of the foregoing description, when read in conjunction with the accompanying drawings. However, any and all changes will still fall within the scope of the non-limiting exemplary embodiments of the present disclosure.

[0177] It will be understood that for any given component or embodiment described herein, any possible candidates or alternatives listed for that component may generally be used individually or in combination with one another, unless implicitly or explicitly understood or otherwise stated. Furthermore, any listing of such candidates or alternatives will be understood to be merely exemplary and not limiting, unless implicitly or explicitly understood or otherwise stated.

[0178] Furthermore, unless otherwise indicated, numbers expressing quantities, components, distances, or other measurements used in the specification and claims should be understood to be modified by the term "about," as that term is defined herein. Accordingly, unless indicated to the contrary, the numerical parameters set forth in the specification and appended claims are approximations that may vary depending upon the desired properties sought to be obtained by the subject matter presented herein. At the very least, and not as an attempt to limit the application of the doctrine of equivalents to the scope of the claims, each numerical parameter should at least be construed in light of the number of reported significant digits and by applying ordinary rounding techniques. Notwithstanding that the numerical ranges and parameters setting forth the broad scope of the subject matter presented herein are approximations, the numerical values ​​set forth in the specific examples are reported as precisely as possible. However, any numerical value inherently contains certain errors necessarily resulting from the standard deviation found in their respective testing measurements.

[0179] Any headings and subheadings used herein are for organizational purposes only and are not meant to be used to limit the scope of the description or claims. The terms and expressions used herein are used as terms of description and not of limitation, and the use of such terms and expressions is not intended to exclude the features shown and described or equivalents thereof, but it is recognized that various modifications are possible within the scope of the present disclosure. Thus, while the present disclosure has been specifically disclosed in part by preferred embodiments, it should be understood that exemplary embodiments of the concepts disclosed herein, as well as optional features, modifications, and variations, may be utilized by those skilled in the art, and that such modifications and variations are considered to be within the scope of the present description.

[0180] It will also be understood that systems, devices, articles of manufacture, kits, methods, and / or processes according to certain embodiments of the present disclosure may include, incorporate, or otherwise include properties or characteristics (e.g., components, members, elements, parts, and / or portions) described in other embodiments disclosed and / or described herein. Thus, various features of certain embodiments may be compatible with, combined with, included in, and / or incorporated into other embodiments of the present disclosure. Thus, the disclosure of a particular feature for a particular embodiment of the present disclosure should not be construed as the application or inclusion of the feature for the particular embodiment. Rather, it will be understood that other embodiments may also include features, members, elements, portions, and / or portions without necessarily departing from the scope of the present disclosure.

[0181] Furthermore, unless a feature is described as requiring another feature in combination with it, any feature herein may be combined with any other feature of the same or different embodiments disclosed herein. Moreover, various well-known aspects of example systems, methods, devices, etc., are not described in particular detail herein to avoid obscuring aspects of the example embodiments. However, such aspects are also contemplated herein.

[0182] All references cited in this application are incorporated herein by reference in their entirety to the extent that they do not contradict the disclosure in this application. It will be apparent to those skilled in the art that methods, devices, device elements, materials, procedures, and techniques other than those specifically described herein can be applied to the practice of the described embodiments as broadly disclosed herein without resorting to undue experimentation. All art-known functional equivalents of the methods, devices, device elements, materials, procedures, and techniques specifically described herein are intended to be encompassed by this disclosure.

[0183] When a group of materials, compositions, ingredients, or compounds is disclosed herein, it is understood that all individual members of the group and all subgroups thereof are separately disclosed. When Markush groups or other groupings are used herein, all individual members of the group, and all combinations and possible subcombinations of the group, are intended to be individually included in the disclosure.

[0184] The above-described embodiments are by way of example only, and those of skill in the art will be able to effect alterations, modifications and variations to the particular embodiments without departing from the scope of the description, which is defined solely by the claims that follow.

Claims

1. 1. A method performed by an Operation, Administration and Maintenance (OAM) node (3300) for configuring attribute configuration between a first cell served by a first network node (3300) and a second cell served by a second network node (3300), comprising: transmitting 1310 at least one attribute configuration to the first network node and the second network node; the at least one attribute configuration identifies at least one service to be used over an interface between the first cell and the second cell; The at least one attribute configuration comprises: No EUTRA-NR dual connectivity (EN-DC), where the respective neighbor relations should not be used by the source cell for EN-DC; Resource coordination only, where each neighbor relationship should use the X2 interface only to coordinate resources between the source cell and the target cell; Dynamic spectrum sharing only, where each neighbor relationship should use the X2 interface only to coordinate dynamic spectrum sharing from the source cell with the target cell, or Physical Random Access Channel (PRACH) resource coordination only, where each neighbor relationship should use the X2 interface only to coordinate PRACH resources and resolve potential PRACH contention between the first network node and the second network node; The method comprising one or more of the following options:

2. The method of claim 1 , wherein the at least one service includes only one service at a time.

3. 10. The method of claim 1, wherein the interface is used only for one of the following services: dynamic spectrum sharing, resource coordination, or Physical Random Access Channel (PRACH) resource coordination and potential PRACH contention resolution.

4. 2. The method of claim 1, wherein the first cell comprises an Evolved Universal Terrestrial Radio Access (E-UTRA) cell and the second cell comprises a New Radio (NR) cell.

5. The method of claim 4, wherein the E-UTRA cell comprises a target cell and the NR cell comprises a source cell, or the E-UTRA cell comprises a source cell and the NR cell comprises a target cell.

6. The method of claim 1, wherein the interface is a logical interface and the first network node and the second network node are served by the same NR Node B (gNB).

7. The method of claim 1 , wherein the at least one service enables at least one of interface setup, transport network association maintenance, and configuration updates to continue to be performed.

8. 1. A method performed by a first network node for configuring an attribute configuration between a first cell served by the first network node and a second cell served by a second network node, the method comprising: receiving 1310 at least one attribute configuration from an Operation, Administration and Maintenance (OAM), the at least one attribute configuration identifying at least one service to be used over an interface between the first cell and the second cell; setting up the interface between the first cell and the second cell (1330); using the at least one service via the interface (1350); Including, The at least one attribute configuration comprises: No EUTRA-NR dual connectivity (EN-DC), where the respective neighbor relations should not be used by the source cell for EN-DC; Resource coordination only, where each neighbor relationship should use the X2 interface only to coordinate resources between the source cell and the target cell; Dynamic spectrum sharing only, where each neighbor relationship should use the X2 interface only to coordinate dynamic spectrum sharing from the source cell with the target cell, or Physical Random Access Channel (PRACH) resource coordination only, where each neighbor relationship should use the X2 interface only to coordinate PRACH resources and resolve potential PRACH contention between the first network node and the second network node; The method comprising one or more of the following options:

9. 2. The method of claim 1 , wherein the interface includes a EUTRA-NR Dual Connectivity (EN-DC) X2 interface.

10. The method of claim 8, wherein the interface includes an EUTRA-NR Dual Connectivity (EN-DC) X2 interface.

11. 10. The method of claim 8, wherein the at least one service comprises one of resource coordination only, dynamic spectrum sharing only, or physical random access channel (PRACH) resource coordination only.

12. The method of claim 1 , wherein the at least one attribute configuration comprises a portion of at least one neighbor relation configuration.

13. The method of claim 8, wherein the at least one attribute configuration includes a portion of at least one neighbor relationship configuration.

14. The method of claim 12 , wherein the neighbor relations configuration is configured as part of a Neighbor Cell Relations Table (NCRT).

15. The method described in claim 13, wherein the neighbor relation configuration is configured as part of a neighbor cell relation table (NCRT).

16. 9. The method of claim 8, wherein the first cell comprises one of an Evolved Universal Terrestrial Radio Access (E-UTRA) cell or an NR cell.

17. The method of claim 8 , wherein the first cell comprises one of a source cell or a target cell.

18. 9. The method of claim 8, further comprising sending a failure message to the second network node if the second network node attempts to use a service that is not allowed by the attribute configuration.

19. 9. The method of claim 8, wherein the first network node comprises an Automatic Neighbor Relation (ANR) function configured to manage an NCRT, the NCRT comprising one or more neighbor relations.

20. 20. The method of claim 19, wherein each of the one or more neighbor relations defines a relationship from a source cell to a target cell, and for each of the one or more neighbor relations, the first network node is characterized by at least one of: knowing an E-UTRA Cell Global Identifier (ECGI) and a Physical Cell Identifier (PCI) of the target cell; having an entry in the NCRT for the source cell that identifies the target cell; and having any attributes in the NCRT that are either defined by an OAM or set to default values.

21. 1. A method performed by a first network node for managing attribute configuration of a first cell served by the first network node, comprising: configuring at least one attribute configuration in the first network node as part of a neighbor relationship between the first cell and a second cell served by a second network node (1010, 1120); determining (1020, 1130) at least one service identified by at least an attribute configuration to be used on an interface between the first cell and the second cell; Indicating (1040, 1140) said at least one service and at least one attribute configuration to said second network node; establishing the interface (1160); Implementing (1160) the at least one service over the established interface; Including, The at least one attribute configuration comprises: No EUTRA-NR dual connectivity (EN-DC), where the respective neighbor relations should not be used by the source cell for EN-DC; Resource coordination only, where each neighbor relationship should use the X2 interface only to coordinate resources between the source cell and the target cell; Dynamic spectrum sharing only, where each neighbor relationship should use the X2 interface only to coordinate dynamic spectrum sharing from the source cell with the target cell, or Physical Random Access Channel (PRACH) resource coordination only, where each neighbor relationship should use the X2 interface only to coordinate PRACH resources and resolve potential PRACH contention between the first network node and the second network node; The method comprising one or more of the following options:

22. 1. A method performed by a first network node co-located with a second network node for performing resource coordination with a third network node that uses the same frequency band as a first cell served by the first network node, the method comprising: configuring (1110) a neighbor relation for a second cell served by the second network node, the neighbor relation identifying at least one service to be used over an interface between the first cell and the second cell; Indicating (1140) the neighbor relationship and at least one service to the second network node; coordinating (1160) one or more resources with the second network node so that neighboring cells between the first network node and the third network node can coexist on a shared channel; A method comprising:

23. The method of claim 22, wherein the interface is a logical interface and the co-location of the first network node and the second network node comprises sharing the same base station (gNB) in NR in a split architecture.

24. 1. A network node for configuring a neighbor relationship between a first cell and a second cell for a particular service, comprising: a processing circuit (3302) configured to perform the method of claim 1; a power supply circuit (3308) configured to provide power to the processing circuit; A network node comprising:

Images