WO2020222093A1

WO2020222093A1 - Method for load coordination in multi-radio secondary node selection

Info

Publication number: WO2020222093A1
Application number: PCT/IB2020/053863
Authority: WO
Inventors: Angelo Centonza; Pablo SOLDATI
Original assignee: Telefonaktiebolaget Lm Ericsson (Publ)
Priority date: 2019-05-02
Filing date: 2020-04-23
Publication date: 2020-11-05

Abstract

A method performed by a source secondary network node (S-SN) maintaining an active data plane connection with a wireless device includes receiving resource status information from a target secondary network node (T-SN) and determining to change the active data plane connection for the wireless device to the T-SN based on the resource status information. The S-SN transmits, to a master network node (MN) having a control plane connection with the wireless device, the resource status information received from the T-SN.

Description

METHOD FOR LOAD COORDINATION IN MULTI-RADIO

SECONDARY NODE SELECTION

TECHNICAL FIELD

The present disclosure relates, in general, to wireless communications and, more particularly, systems and methods for load coordination in multi-radio secondary node selection.

BACKGROUND

FIGURE 1 illustrates the current Next Generation-Radio Access Network (NG-RAN) architecture, as described in 3GPP TS38.401. The NG architecture can be further described as follows:

• The NG-RAN consists of a set of gNodeBs (gNBs) connected to the 5^th Generation Core (5GC) through the NG.

• A gNB can support Frequency Division Duplex (FDD) mode, Time Division Duplex (TDD) mode or dual mode operation.

• gNBs can be interconnected through the Xn.

• A gNB may consist of a gNB-Central Unit (gNB-CU) and gNB-Distributed Units (gNB-DUs).

• A gNB-CU and a gNB-DU are connected via FI logical interface.

• One gNB-DU is connected to only one gNB-CU.

The architecture in FIGURE 1 can be expanded by spitting the gNB-CU into two entities. One gNB-CU-User Plane (gNB-CU-UP), which serves the user plane (UP) and hosts Packet Data Convergence Protocol (PDCP) and one gNB-CU-Control Plane (gNB-CU-CP), which serves the control plane (CP) and hosts the PDCP and Radio Resource Control (RRC) protocol. The interface connecting gNB-CU-CP and gNB-CU-UP is named El.

NG, Xn, El and FI are logical interfaces. For NG-RAN, the NG and Xn-C interfaces for a gNB consisting of a gNB-CU and gNB-DUs, terminate in the gNB-CU. For Evolved- Universal Terrestrial Radio Access Network New Radio - Dual Connectivity (EN-DC), the Sl-U and X2-C interfaces for a gNB consisting of a gNB-CU and gNB-DUs, terminate in the gNB-CU. The gNB-CU and connected gNB-DUs are only visible to other gNBs and the 5GC as a gNB.

The NG-RAN is layered into a Radio Network Layer (RNL) and a Transport Network Layer (TNL). The NG-RAN architecture, which includes the NG-RAN logical nodes and interfaces between them, is defined as part of the RNL. For each NG-RAN interface (NG, Xn, El, FI) the related TNL protocol and the functionality are specified. The TNL provides services for user plane transport and signaling transport. In NG-Flex configuration, each gNB is connected to all Access and Mobility Management Functions (AMFs) within an AMF Region. The AMF Region is defined in 3GPP TS 23.501.

A similar architecture can be foreseen in a 4^th Generation (4G) network too, either as future 3^rd Generation Partnership Project (3GPP) development or a proprietary product development. The concept of CU, DU and FI interface can be applied to a 4G eNodeB (eNB) also. Accordingly, as used herein, the term gNB is used generically and is intended to include both gNB and eNB. Similarly, the terms gNB-CU and gNB-DU are intended to include eNB- CU and eNB-DU, respectively. Likewise, FI is intended to refer to FI as per 3GPP standardization and any other possible proprietary interface between eNB-DU and eNB-CU.

The 3^rd Generation Partnership Project New Radio system enables a radio cell to be configured to transmit multiple Synchronization Signals Blocks (SSBs) and Physical Broadcast Channel (PBCH) blocks for the purpose of cell search and synchronization. An SSB consists of a primary synchronization signal (PSS) and secondary synchronization signal (SSS), each occupying 1 symbol and 127 subcarriers, and a PBCH signal spanning across 3 Orthogonal Frequency Division Multiplexing (OFDM) symbols and 240 subcarriers, but on one symbol leaving an unused part in the middle for SSS.

The possible time locations of SSBs, within a half-frame, are determined by sub-carrier spacing and the periodicity of the half-frames where SSBs are transmitted is configured by the network. During a half-frame, different SSBs may be transmitted in different spatial directions (i.e. using different spatial beams, spanning the coverage area of a cell). Within the frequency span of a carrier, multiple SSBs can be transmitted. The Primary Cell Identifiers (PCIs) of SSBs transmitted in different frequency locations do not have to be unique, i.e. different SSBs in the frequency domain can have different PCIs. However, when an SSB is associated with an Remaining Minimum System Information (RMSI), the SSB corresponds to an individual cell, which has a unique NR Cell Global Identity (NCGI), as discussed in subclause 8.2 of 3GPP TS38.401. Such an SSB is referred to as a Cell-Defining SSB (CD-SSB). A Primary Cell (PCell) is always associated to one and only one CD-SSB located on the synchronization raster.

Since SSB beams can be transmitted to cover different parts of the cell’s coverage area, and given that, from a user equipment (UE) point of view, measurement reports are based on detection of such SSBs, it is possible to divide the cell in SSB coverage areas and to determine parameters such as load, composite capacity, resource status information to such partition of the cell. With this approach, SSB measurement reports from a UE allow the network to assess which portion of the cell the UE is in proximity of and the resource status information for that partition of the NR cell. This provides a much finer granularity than in Long Term Evolution (LTE) where resource status information is available at a per cell level.

FIGURE 2 illustrates an example of unbalanced load distribution between SSB within an NR cell that could allow MLB to the coverage area of SSB with low load. FIGURE 2 demonstrates that introducing resource status information per SSB beam can be beneficial for enhancing MLB in NR. In this example, an NR serving cell is considered, where the cell is highly loaded at least in some local area defined, for instance, by the coverage area of different SSB beams. A target UE in the loaded area may report measurements that a neighbor cell-A is detected with good radio conditions, possibly including beam measurements, and also reports another cell that is farther away, e.g. cell-B. Assuming to use the LTE MLB solution as baseline for NR, the serving node can request resource status information from the target node which would indicate a high load in Cell-A, as at least the same number of UEs and same traffic as in the serving cell might be experienced.

If only cell-specific resource status information is available, the loaded serving node may be led to believe that the target node is also overloaded. However, with SSB-beam specific resource status information available, the serving cell can determine that, in the beam coverage area where the UE is moving, Cell-A has enough available capacity to accept the UE. Resource status information associated to the coverage area of an SSB beam, such as available capacity, resource utilization, etc. can be exchanged between network nodes to improve and assist mobility-based decisions, such as handover, load balancing and load sharing, etc.

In the LTE system, the resource status information for a network node is expressed in terms of several parameters. One such parameter is the cell Composite Available Capacity (CAC) to indicate the overall available resource level in a cell in either Downlink (DL) or Uplink (UL). As disclosed in 3GPP TS 32.522, the CAC is defined as: Composite Available Capacity = Cell Capacity Class Value * Capacity Value where:

The Cell Capacity Class Value (CCCV) indicates the value that classifies the cell capacity with regards to the other cells. The Cell Capacity Class Value IE only indicates resources that are configured for traffic purposes and it is expressed with an integer ranging from 1, indicating the minimum cell capacity, to 100 indicating the maximum cell capacity, following a linear relation between cell capacity and the Cell Capacity Class Value 3GPP TS 36.331. In 3GPP TS 36.423, the cell capacity class value is an optional parameter in case of intra-LTE load balancing. If cell capacity class value is not present, then 3GPP TS 36.423 assumes that bandwidth should be used instead to assess the capacity.

The Capacity Value (CV) indicates the amount of resources that are available relative to the total Evolved-Universal Terrestrial Radio Access Network (E-UTRAN) resources. The capacity value should be measured and reported so that the minimum E-UTRAN resource usage of existing services is reserved according to implementation. The Capacity Value IE ranges between 0, indicating no available capacity, and 100 which indicates maximum available capacity. Capacity Value should be measured on a linear scale

Standardization work for the 3GPP NG-RAN system at the time of writing is focusing on defining self-organizing (SON) functions such as load balancing and load sharing. While there is a broad consensus that the basic LTE solution for load sharing and load balancing can provide a good baseline for introducing this feature in NG-RAN, it is important to recall that the LTE solution to load balance does not consider Dual Connectivity (DC). Multi Radio Dual Connectivity (MR-DC), on the other hand, is a key feature in NG-RAN that generalized the Intra-E-UTRA DC. Therefore, load balancing and load sharing in NG-RAN must coexist with MR-DC.

In MR-DC, multiple receiver (Rx)/transmitter (Tx) user equipment (UE) may be configured to utilize resources provided by two different nodes connected via non-ideal backhaul, one providing NG-RAN access and the other one providing either Evolved Universal Terrestrial Radio Access (E-UTRA) or NR access. One node acts as the master node (MN) providing coverage and the other as the secondary node (SN) providing additional capacity. The MN provide RRC connectivity anchor to the UE and is responsible for handling UE mobility decisions as well as to handle MR-DC decisions, such as changing/adding/modifying/releasing a SN or changing a MN by triggering an handover (HO) procedure. The MN and SN are connected via a network interface and at least the MN is connected to the core network, i.e. either the Evolved Packet Core (EPC) for MR-DC in Evolved Universal Terrestrial Radio Access Network (E-UTRAN) or the 5^th Generation Core (5GC) for MR-DC in NG-RAN.

MR-DC with EPC

E-UTRAN supports MR-DC via E-UTRA-NR Dual Connectivity (EN-DC), in which a UE is connected to one eNB that acts as a MN and one en-gNB that acts as a SN. The eNB is connected to the EPC via the S I interface and to the en-gNB via the X2 interface. The en- gNB might also be connected to the EPC via the S 1 -U interface and other en-gNBs via the X2- U interface.

FIGURE 3 illustrates the EN-DC architecture as discussed in 3GPP TS 37.340.

MR-DC with 5GC

In the case of MR-DC with 5GC, there are three possible scenarios:

- E-UTRA-NR Dual Connectivity, where a UE is connected to one ng- eNB that acts as a MN and one gNB that acts as a SN. The ng-eNB is connected to the 5GC and the gNB is connected to the ng-eNB via the Xn interface.

- NR-E-UTRA Dual Connectivity, where a UE is connected to one gNB that acts as a MN and one ng-eNB that acts as a SN. The gNB is connected to 5GC and the ng-eNB is connected to the gNB via the Xn interface.

- NR-NR Dual Connectivity, where a UE is connected to one gNB that

acts as a MN and another gNB that acts as a SN. The master gNB is connected to the 5GC via the NG interface and to the secondary gNB via the Xn interface. The secondary gNB might also be connected to the 5GC via the NG-U interface. In addition, NR-DC can also be used when a UE is connected to two gNB-DUs, one serving the MCG and the other serving the SCG, connected to the same gNB-CU, acting both as a MN and as a SN.

MR-DC radio protocol architecture control plane

In MR-DC, the UE has a single RRC state, based on the MN RRC and a single C-plane connection towards the Core Network. FIGURE 4 illustrates the control plane architecture for EN-DC and MR-DC as discussed in 3GPP TS 73.340. Specifically, the EN-DC control plane architecture is illustrated on the left and the MR-DC control plane architecture is illustrated on the right. Each radio node has its own RRC entity (E-UTRA version if the node is an eNB or NR version if the node is a gNB) which can generate RRC Packet Data Units (RRC PDUs) to be sent to the UE.

RRC PDUs generated by the SN can be transported via the MN to the UE. The MN always sends the initial SN RRC configuration via Master Cell Group (MCG) Signaling Radio Bearer (SRB), such as, for example, SRB 1, but subsequent reconfigurations may be transported via MN or SN. When transporting RRC PDU from the SN, the MN does not modify the UE configuration provided by the SN.

In E-UTRA connected to EPC, at initial connection establishment SRBl uses E-UTRA PDCP. If the UE supports EN-DC, regardless whether EN-DC is configured or not, after initial connection establishment, MCG SRBs (SRB 1 and SRB2) can be configured by the network to use either E-UTRA PDCP or NR PDCP (either SRB 1 and SRB2 are both configured with E- UTRA PDCP, or they are both configured with NR PDCP). Change from E-UTRA PDCP to NR PDCP (or vice-versa) is supported via a handover procedure (reconfiguration with mobility) or, for the initial change of SRBl from E-UTRA PDCP to NR PDCP, with a reconfiguration without mobility before the initial security activation.

If the SN is a gNB (i.e. for EN-DC, NGEN-DC and NR-DC), the UE can be configured to establish a SRB with the SN (SRB3) to enable RRC PDUs for the SN to be sent directly between the UE and the SN. RRC PDUs for the SN can only be transported directly to the UE for SN RRC reconfiguration not requiring any coordination with the MN. Measurement reporting for mobility within the SN can be done directly from the UE to the SN if SRB3 is configured. Split SRB is supported for all MR-DC options, allowing duplication of RRC PDUs generated by the MN, via the direct path and via the SN. Split SRB uses NRPDCP. This version of the specification does not support the duplication of RRC PDUs generated by the SN via the MN and SN paths.

In EN-DC, the SCG configuration is kept in the UE during suspension. The UE releases the SCG configuration (but not the radio bearer configuration) during resumption initiation.

In MR-DC with 5GC, the UE stores the PDCP/SDAP configuration when moving to RRC Inactive but it releases the SCG configuration.

Network interfaces for MR-DC

Control Plane

In MR-DC, there is an interface between the MN and the SN for control plane (CP or C-plane) signaling and coordination. For each MR-DC UE, there is also one C-plane connection between the MN and a corresponding Core Network (CN) entity. The MN and the SN involved in MR-DC for a certain UE control their radio resources and are primarily responsible for allocating radio resources of their cells.

FIGURE 5 illustrates C-plane connectivity of MN and SN involved in EN-DC and MR- DC for a certain UE, as discussed in 3GPP TS 37.340. Specifically, C-plane connectivity for EN-DC is illustrated on the left and C-plane connectivity for MR-DC with 5GC is illustrated on the right.

In MR-DC with EPC (EN-DC), the involved core network entity is the Mobility Management Entity (MME). S l-MME is terminated in MN and the MN and the SN are interconnected via X2-C.

In MR-DC with 5GC (NGEN-DC, NE-DC and NR-DC), the involved core network entity is the AMF. NG-C is terminated in the MN and the MN and the SN are interconnected via Xn-C.

User plane

There are different user plane (UP or U-plane) connectivity options of the MN and SN involved in MR-DC for a certain UE. FIGURE 6 illustrates U-plane connectivity for EN-DC and MR-DC with 5GC as discussed in 3GPP TS 37.340. Specifically, U-plane connectivity for EN-DC is shown on the left and U-plane connectivity for MR-DC with 5GC is shown on the right. The U-plane connectivity depends on the bearer option configured:

- For MN terminated bearers, the U-plane connection to the CN entity is terminated in the MN;

- For SN terminated bearers, the U-plane connection to the CN entity is terminated in the SN;

- The transport of user plane data over the Uu either involves MCG or SCG radio resources or both:

- For MCG bearers, only MCG radio resources are involved;

- For SCG bearers, only SCG radio resources are involved;

- For split bearers, both MCG and SCG radio resources are involved.

- For split bearers, MN terminated SCG bearers and SN terminated MCG bearers, PDCP data is transferred between the MN and the SN via the MN-SN user plane interface.

For MR-DC with EPC (EN-DC), X2-U interface is the user plane interface between MN and SN, and Sl-U is the user plane interface between the MN, the SN or both and the S- GW.

For MR-DC with 5GC (NGEN-DC, NE-DC and inter-gNB NR-DC), Xn-U interface is the user plane interface between MN and SN, and NG-U is the user plane interface between the MN, the SN or both and the UPF.

Multi-Connectivity operation related aspects

Multi-Connectivity operation related aspects for E-UTRAN and NG-RAN systems is defined in TS 37.340. The specifications distinguish between the cases whereimO

The MN is an eNB, a ng-eNB, or a gNB

The SN is a eNB, a ng-eNB, or a gNB.

The specifications further define MR-DC procedures for selecting a new master node for a UE connection or a new secondary node. Procedures related to the selection or reselection of a secondary node are relevant to the methods discussed herein. These procedures include:

Secondary node addition: This procedure is initiated by the MN and is used to establish a UE context at the SN to provide resources from the SN to the UE. For bearers requiring SCG radio resources, this procedure is used to add at least the first cell of the SCG. This procedure can also be used to configure an SN terminated MCG bearer (where no SCG configuration is needed).

Secondary node modification: This procedure may be initiated either by the MN or by the SN and be used to modify, establish or release bearer contexts, to transfer bearer contexts to and from the SN or to modify other properties of the UE context within the same SN. In case of MR-DC with 5GC, this procedure can additionally be used to modify the current user plane resource configuration (e.g. related to PDU session, Quality of Service (QoS) flow or data radio bearer (DRB)). It may also be used to transfer an NR RRC message from the SN to the UE via the MN and the response from the UE via MN to the SN (e.g. when SRB3 is not used).

Secondary node release: This procedure may be initiated either by the MN or by the SN and is used to initiate the release of the UE context at the SN. The recipient node of this request can reject it, e.g., if a SN change procedure is triggered by the SN.

Secondary node change: This procedure is initiated either by MN or SN and used to transfer a UE context from a source SN (S-SN) to a target SN (T-SN) and to change the SCG configuration in UE from one SN to another.

In the case of a SN change procedure initiated by the S-SN, the S-SN initiates the SN change procedure by sending the SN Change Required message, which contains a candidate target node ID and may include the SCG configuration (to support delta configuration) and measurement results related to the T-SN. FIGURE 7 illustrates the signalling aspects involved in a SN change procedure initiated by the S-SN as discussed in 3GPP TS 73.340.

Certain problems exist. For example, current solutions for changing/adding/modifying a SN in a MR-DC procedure initiated by a S-SN do not consider the load information associated to the T-SN. Additionally, once the MN receives a SN change request message from a S-SN that initializes a SN change procedure, the MN may not have up to date load information associated to the T-SN indicated by the S-SN. LTE procedures currently do not consider load information to decide whether to trigger a data plane connection establishment between a wireless device and a T-SN when the SN change procedure is initialized by the S-SN.

While the MN could request load information to the T-SN indicated by the S-SN within the SN change request message, the load information of the T-SN would become available at the MN only after a considerable delay. If the MN had to start load reporting from the T-SN ahead of accepting the change of SN from S-SN to T-SN, the establishment of a data plane connection between the wireless device and the T-SN may be delayed. Depending of the wireless device speed and type of traffic, such delay may not be tolerable. In addition, the MN may be aware of another T-SN that could serve the wireless device and has comparable channel quality toward the wireless device as the T-SN indicated by the S-SN. Load information would be beneficial in this case to determine the best T-SN to establish a new data plane connection with the wireless device.

SUMMARY

Certain aspects of the present disclosure and their embodiments may provide solutions to these or other challenges. For example, according to certain embodiments, a method is provided for load coordination in multi-radio secondary node (SN) selection.

According to certain embodiments, a method performed by a source secondary network node (S-SN) maintaining an active data plane connection with a wireless device includes receiving resource status information from a target secondary network node (T-SN) and determining to change the active data plane connection for the wireless device to the T-SN based on the resource status information. The S-SN transmits, to a master network node (MN) having a control plane connection with the wireless device, the resource status information received from the T-SN.

According to certain embodiments, a S-SN maintaining an active data plane connection with a wireless device includes processing circuitry configured to receive resource status information from a T-SN and determine whether to change the active data plane connection for the wireless device to the T-SN based on the resource status information. The processing circuitry transmits, to a MN having a control plane connection with the wireless device, the resource status information received from the T-SN.

According to certain embodiments, a method performed by a T-SN includes transmitting resource status information to a S-SN maintaining an active data plane connection with a wireless device and receiving a request to change the active data plane connection for the wireless device from the S-SN to the T-SN.

According to certain embodiments, a T-SN includes processing circuitry configured to transmit resource status information to a S-SN maintaining an active data plane connection with a wireless device and receive a request to change the active data plane connection for the wireless device from the S-SN to the T-SN.

According to certain embodiments, a method performed by a MN for a wireless device includes receiving resource status information from a S-SN having an active data plane connection with the wireless device. The resource status information is associated with a T- SN. Based on the resource status information, the MN determines whether to change the active data plane connection for the wireless device to the T-SN.

According to certain embodiments, a MN for a wireless device includes processing circuitry configured to receive resource status information from a S-SN having an active data plane connection with the wireless device. The resource status information is associated with a T-SN. The processing circuitry is configured to determine whether to change the active data plane connection for the wireless device to the T-SN based on the resource status information.

Certain embodiments may provide one or more of the following technical advantages. For example, one technical advantage may be that certain embodiments resolves the shortcomings of previous techniques by allowing to take decisions on SN changes that take the T-SN load into account. By enabling the S-SN to request load information to the T-SN prior to initializing the SN change procedure for a wireless device such as a user equipment (UE), the load distribution among SNs can be optimized and better quality of Service (QoS) can be provided when serving wireless devices. In addition, by enabling the S-SN to forward to the MN load information associated with the T-SN, the MN can avoid requesting load information from the T-SN prior to starting the SN change signaling to optimize the load between the SNs, thus reducing the delay in establishing a connection between the T-SN and the wireless device.

Other advantages may be readily apparent to one having skill in the art. Certain embodiments may have none, some, or all of the recited advantages.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the disclosed embodiments and their features and advantages, reference is now made to the following description, taken in conjunction with the accompanying drawings, in which:

FIGURE 1 illustrates the current Next Generation-Radio Access Network (NG-RAN) architecture, as described in 3GPP TS38.401; FIGURE 2 illustrates an example of unbalanced load distribution between Synchronization Signal Block (SSB) within an New Radio (NR) cell;

FIGURE 3 illustrates the Evolved- Universal Terrestrial Radio Access Network New Radio - Dual Connectivity (EN-DC) architecture as discussed in 3GPP TS 37.340;

FIGURE 4 illustrates the control plane architecture for EN-DC and Multi Radio Dual Connectivity (MR-DC) as discussed in 3GPP TS 73.340;

FIGURE 5 illustrates control plane connectivity of master node (MN) and secondary node (SN) involved in EN-DC and MR-DC as discussed in 3GPP TS 37.340;

FIGURE 6 illustrates user plane connectivity for EN-DC and MR-DC with 5GC as discussed in 3GPP TS 37.340;

FIGURE 7 illustrates the signalling aspects involved in a SN change procedure initiated by the source SN (S-SN) as discussed in 3GPP TS 73.340;

FIGURE 8 illustrates an example of S-SN requesting load information from a target SN (T-SN) for a wireless device, according to certain embodiments;

FIGURE 9 illustrates an example of a S-SN forwarding load information associated with a T-SN to the MN as part of the initialization of a procedure to request a new data plane connection for the wireless device with the T-SN, according to certain embodiments;

FIGURE 10 illustrates an alternative example of S-SN forwarding load information associated with a T-SN to the MN as part of the initialization of a procedure to request a new data plane connection for the wireless device with the T-SN, according to certain embodiments;

FIGURE 11 illustrates an example of how the signaling could be achieved in a Radio Access Network (RAN) split architecture, according to certain embodiments;

FIGURE 12 illustrates an example wireless network, according to certain embodiments;

FIGURE 13 illustrates an example network node, according to certain embodiments;

FIGURE 14 illustrates an example wireless device, according to certain embodiments;

FIGURE 15 illustrate an example user equipment, according to certain embodiments;

FIGURE 16 illustrates a virtualization environment in which functions implemented by some embodiments may be virtualized, according to certain embodiments;

FIGURE 17 illustrates an example method performed by a network node maintaining an active data plane connection with a wireless device, according to certain embodiments; FIGURE 18 illustrates an exemplary virtual computing device, according to certain embodiments;

FIGURE 19 illustrates an example method performed by a source secondary network node maintaining an active data plane connection with a wireless device, according to certain embodiments;

FIGURE 20 illustrates another exemplary virtual computing device, according to certain embodiments;

FIGURE 21 illustrates an example method performed by a network node operating as a target secondary network node, according to certain embodiments;

FIGURE 22 illustrates another exemplary virtual computing device, according to certain embodiments;

FIGURE 23 illustrates another example method performed by a target secondary network node, according to certain embodiments;

FIGURE 24 illustrates another exemplary virtual computing device, according to certain embodiments;

FIGURE 25 illustrates an example method performed by a network node operating as a master network node for a wireless device, according to certain embodiments;

FIGURE 26 illustrates another exemplary virtual computing device, according to certain embodiments;

FIGURE 27 illustrates another example method performed by a master network node for a wireless device, according to certain embodiments; and

FIGURE 28 illustrates another exemplary virtual computing device, according to certain embodiments.

DETAILED DESCRIPTION

Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Other embodiments, however, are contained within the scope of the subject matter disclosed herein, the disclosed subject matter should not be construed as limited to only the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art. Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and/or is implied from the context in which it is used. All references to a/an/the element, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any methods disclosed herein do not have to be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and/or where it is implicit that a step must follow or precede another step . Any feature of any of the embodiments disclosed herein may be applied to any other embodiment, wherever appropriate. Likewise, any advantage of any of the embodiments may apply to any other embodiments, and vice versa. Other objectives, features and advantages of the enclosed embodiments will be apparent from the following description.

In some embodiments, a more general term“network node” may be used and may correspond to any type of radio network node or any network node, which communicates with a UE (directly or via another node) and/or with another network node. Examples of network nodes are NodeB, MeNB, ENB, a network node belonging to MCG or SCG, base station (BS), multi-standard radio (MSR) radio node such as MSR BS, eNodeB, gNodeB, network controller, radio network controller (RNC), base station controller (BSC), relay, donor node controlling relay, base transceiver station (BTS), access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU), Remote Radio Head (RRH), nodes in distributed antenna system (DAS), core network node (e.g. Mobile Switching Center (MSC), Mobility Management Entity (MME), etc.), Operations & Maintenance (O&M), Operations Support System (OSS), Self-Optimizing Node (SON), positioning node (e.g. Evolved-Serving Mobile Location Centre (E-SMLC)), Minimization of Drive Test (MDT), test equipment (physical node or software), etc.

In some embodiments, the non-limiting term user equipment (UE) or wireless device may be used and may refer to any type of wireless device communicating with a network node and/or with another UE in a cellular or mobile communication system. Examples of UE are target device, device to device (D2D) UE, machine type UE or UE capable of machine to machine (M2M) communication, personal digital assistant (PDA), Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), Unified Serial Bus (USB) dongles, UE category Ml, UE category M2, Proximity Services (ProSe) UE, Vehicle-to-Vehicle (V2V) UE, Vehicle-to-Anything (V2X) UE, etc.

Additionally, terminologies such as base station/gNodeB and UE should be considered non-limiting and do in particular not imply a certain hierarchical relation between the two; in general,“gNodeB” could be considered as device 1 and“UE” could be considered as device 2 and these two devices communicate with each other over some radio channel. And in the following the transmitter or receiver could be either gNB, or UE.

Certain embodiments described herein are implemented in a radio communication network with multi-radio connectivity, wherein a wireless device (e.g., UE in 3GPP terminology) has a control plane connection established with a master network node (MN) and at least a data plane connection established with at least one secondary network node (SN). Without loss of generality, hereafter we shall use the LTE and NG-RAN terminology for multi radio connectivity. To this end, we shall refer to a SN with at least a data plane connection with a wireless device as a source SN (S-SN). We shall further refer to a SN candidate for establishing at least a data plane connection with a wireless device as a target SN (T-SN).

In MR-DC scenarios, the availability of load information of neighboring nodes is useful to select a new MN to which handover the UE and/or to add/change/modify a SN. In both cases, cell-specific load information of neighboring nodes can provide to the MN a qualitative assessment of the resources that each neighboring node can grant to serve the UE, either as a target MN or as a T-SN. In case of a gNB, load information per SSB beam coverage area can provide a more quantitative information of the resources and capability of a neighboring gNB to serve the UE, either as a target MN or as a T-SN.

In general, it is assumed that load information can be available at the MN in the case of MN initiated procedures for MN change/handover as well as for adding/modifying/changing SN. In these cases, it may be assumed that the load information associated to the target MN/SN is available to the MN.

However, load information associated to a T-SN may not be available at the MN when the SN modification/change/addition procedure is initiated by a S-SN. For instance, S-SN initiates the SN change procedure by sending SgNB Change Required message which contains T-SN ID information and may include the SCG configuration (to support delta configuration) and measurement results related to the T-SN. If the MN does not have an updated load status information of the T-SN, the MN could then request load information to the T-SN prior to triggering the SN change. However, it this would introduce long delay in the procedure. A more effective approach may be to allow the S-SN to forward the load information associated to T-SN to the MN as part of the SgNB Change Required message. To this end, once the S-SN has identified a T-SN, the S-SN could request a load status report to the T-SN prior to initiating a SN change procedure.

According to certain embodiments described herein, a method executed by a first network node is provided. In a particular embodiment, the first network node may include a S- SN and the method includes: transmitting a resource status request message to a second network node (the T-SN); receiving a resource status information report message from the second network node (the T-SN); determining whether to change an existing data plane connection for at least one wireless device to the second network node based on the resource status information report associated to the second network node as well as based on the measurements from the UE on the T-SN cell; transmitting a data plane connection change request message for at least one wireless device to a network control node (i.e., the MN) indicating the resource status information report (e.g., load information) associated to the second network node (the T-SN); and allowing the network control node to take a decision to accept the data plane connection change request based on the load information of the T-SN or alternatively rejecting such request on the bases of the acquired load information. As used herein, resource status information may also be called a resource status update or resource status update information. Likewise, resource status information may be requested by the S- SN in a resource status request message, which may also be called a resource status request or any similar term, and resource status information may be reported by the T-SN in a resource status report message, which may also be referred to as a resource status message, a resource status update, or any similar term.

According to certain embodiments, a method is provided in a S-SN with at least a data plane connection with a wireless device for requesting load information associated to a T-SN for a wireless device having a data plane connection with the S-SN and for determining, based on at least the load information of the T-SN, whether a SN new data plane connection for the wireless device shall be established with the T-SN. Furthermore, according to certain embodiments, the S-SN may initialize a SN change procedure based on the load information of the T-SN and that the load information of the T-SN is forwarded by the S-SN to the MN controlling the wireless device.

To this end, according to certain embodiments, the S-SN with an active data plane connection with the wireless device shall first determine whether another SN is a suitable candidate T-SN for establishing a data plane connection with the wireless device. This can be done, for instance, by configuring the wireless device to monitor neighboring cells and report radio measurements to the SN, either directly or via the MN, in a particular embodiment. Once a T-SN has been identified as a suitable candidate for establishing a data plane connection with the wireless device, the S-SN can request load information to the T-SN

FIGURE 8 illustrates an example signalling diagram 100 that includes a S-SN 105 requesting load information (e.g., resource status information report) from a T-SN 110 for wireless device and determining, based at least on the load information of the T-SN 110, whether to initialize a procedure to establish a data plane connection between the wireless device and the T-SN 110, according to certain embodiments. In an LTE compliant system, this can be done by means of the RESOURCE STATUS REPORTING procedure. For example, in this case, the S-SN 105 sends a resource status request message 120 to the T-SN 110. An equivalent message aimed at requesting load information for cells served by the T-SN 110 may be used by the S-SN 105. The T-SN 110 can then respond with a resource status acknowledgment message 125, namely a message acknowledging that reporting of load information can be performed, followed by a resource status report message 130 comprising load information associated to the T-SN 110, e.g. the available capacity of radio cells controlled by the T-SN 110.

In case of a NR-RAN T-SN, i.e. an S-gNB, the load information associated to the T- SN 110 could be expressed on finer granularity compared to only per cell load or per cell available capacity. For instance, the T-SN load or available capacity information could be expressed on a basis of a per SSB coverage area, per SSB group coverage area, per bandwidth part, per network slice, or any combination thereof.

Based on the load information associated to the T-SN 110, the SN 105 can determine at 135 whether a data plane connection can be established between the T-SN 110 and the wireless device,. If the S-SN 105 determines that the T-SN 110 is a candidate to establish a data plane connection with the wireless device, the S-SN 105 initializes a procedure with the MN 115 controlling the wireless device for establishing a data plane connection between the T-SN 110 and the wireless devices. In an LTE compliant system, this can be done by transmitting a SN change request message 140 to the MN 115 as illustrated in FIGURE 8, according to certain embodiments.

In a particular embodiment, the S-SN 105 further transmits to the MN 115 controlling the wireless device load information associated to a potential T-SN 110 for the wireless device as part of the initialization of a procedure for establishing a data plane connection between the T-SN 110 and the wireless device. In one possible implementation of the embodiment, the S- SN 105 forwards to the MN 115 controlling the wireless device load information associated to the T-SN 110 as part of the initialization of a procedure for establishing a data plane connection between the T-SN 110 and the wireless device. For an LTE compliant system, the S-SN 105 could append the load information associated to the T-SN 110 within the SN change request message. The SN change request message may further comprise load information associated to the S-SN 105 itself. This has the advantage of providing updated load information associated to the T-SN 110 to the MN 115 at the beginning of a SN change procedure, thereby reducing delay and improving performance. Based on this information, the MN 115 can further determine whether to change the SN data plane connection for the wireless device. The MN 115, for instance, may be aware of another potential candidate T-SN 110 forthe wireless device that are not visible to the S-SN 105. Thereby, the MN 115 may determine whether to establish a connection between the T-SN 110 indicated by the S-SN 105 and the wireless device based on load information and possibly radio measurements indicating the radio link quality between the T-SN 110 and the wireless device. If a connection shall be established, the MN 115 can then request the T-SN 110 to allocate resources for the wireless device, e.g. by means of the SgNB Addition procedure, including the measurement results related to the T-SN 110 received from the S-SN 105. If forwarding is needed, the T-SN 110 provides forwarding addresses to the MN 115. The T-SN 110 includes the indication of the full or delta RRC configuration.

FIGURE 9 illustrates example signalling diagram 200 wherein a S-SN 105 forwards load information associated with a T-SN 110 to the MN 115 as part of the initialization of a procedure to request a new data plane connection for the wireless device with the T-SN 110, according to certain embodiments. Steps that are similar to those described above with regard to FIGURE 8 are indicated using the same reference numerals.

In the illustrated example of FIGURE 9, the SN 105 transmits a SN change request message 240 to the MN 115, according to certain embodiments. The SN change request message 240 may be differentiated from the SN change request message 140 illustrated in FIGURE 8 because SN change request message 140 includes load information associated with the T-SN 110. Upon receiving the load information, MN 115 may determine, at 245, whether to change SN for the wireless device. This step may be performed as described above, according to certain embodiments.

FIGURE 10 illustrates another example signalling diagram 300 wherein a S-SN 105 forwarding load information associated to a T-SN to the MN as part of the initialization of a procedure to request a new data plane connection for the wireless device with the T-SN, according to certain alternative embodiments. In the illustrated example embodiment, the S- SN 105 may transmit to the MN 115 the load information associated with the potential T-SN 110 for the wireless device as part of a dedicated message 345 that follows a SN change request message 340. The S-SN 105 may further transmit load information associated to the S-SN itself, without waiting for the MN 115 to request load information, in a particular embodiment.

FIGURE 11 illustrates an example signalling diagram 400 for a RAN split architecture, according to certain embodiments. In a split architecture involving CU-CP, CU-UP and DU nodes, the load information herein described is provided by the DU to the CU-CP on a per cell basis. Herein, the example target gNB 410 is split into gNB-CU-CP 410A, gNB-CU-UP 410B, and gNB-DU 410C.

With this architecture assumption, the procedures described in the embodiments above of Load Status Request 120, Load Status Response 125, and Load Status Report 130 are run between the gNB-CU-CP 410A and the gNB-DU 410C and/or gNB-CU-UP 410B, according to a particular embodiment.

The gNB-CU-CP 410A is the node receiving a Load Status Request from a different RAN node (i.e., S-SN 105). In the scenario where the gNB-CU-CP 410 A is part of the T-SN 410, such nodes may receive the Load Status Request S-SN 120. Upon reception of the Load Status Request 120 over the Xn interface from the S-SN 105, the T-SN gNB-CU-CP 410A sends a Load Status Request 420A over the FI interface to the T-SN gNB-DU 410C and it may send the equivalent message 420B over the El interface to the T-SN gNB-CU-UP 425. The respective receiving nodes reply over appropriate interfaces with a Load Status Response 425A and 425B. After such procedures, the gNB-DU 410C and gNB-CU-UP 410B would report their load over the FI and El interface respectively via the Load Status Report procedure 430A and 430B. It shall be noted that the names ofthe procedures are purely given as examples. Any existing or dedicated procedure used to establish load reporting and to signal load information may be considered applicable to these methods.

The T-SN gNB-CU-CP 410A receiving load information from its connected gNB-DUs 410C and gNB-CU-UPs 410B would transfer such load information to the S-SN 105 over the Xn interface in Load Status Report 130. The S-SN 105 and MN 115 may then perform steps and signalling such as determinations 135, 245, and/or 350 and signalling 340 and 345, as described above with regard to FIGURES 9 and 10.

FIGURE 12 illustrates a wireless network, in accordance with some embodiments. Although the subject matter described herein may be implemented in any appropriate type of system using any suitable components, the embodiments disclosed herein are described in relation to a wireless network, such as the example wireless network illustrated in FIGURE 12. For simplicity, the wireless network of FIGURE 12 only depicts network 506, network nodes 560 and 560b, and WDs 510, 510b, and 510c. In practice, a wireless network may further include any additional elements suitable to support communication between wireless devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or end device. Of the illustrated components, network node 560 and wireless device (WD) 510 are depicted with additional detail. The wireless network may provide communication and other types of services to one or more wireless devices to facilitate the wireless devices’ access to and/or use of the services provided by, or via, the wireless network.

The wireless network may comprise and/or interface with any type of communication, telecommunication, data, cellular, and/or radio network or other similar type of system. In some embodiments, the wireless network may be configured to operate according to specific standards or other types of predefined rules or procedures. Thus, particular embodiments of the wireless network may implement communication standards, such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and/or other suitable 2^nd Generation (2G), 3^rd Generation (3G), 4^th Generation (4G), or 5^th Generation (5G standards; wireless local area network (WLAN) standards, such as the IEEE 802.11 standards; and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave and/or ZigBee standards. Network 506 may comprise one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTNs), packet data networks, optical networks, wide-area networks (WANs), local area networks (LANs), wireless local area networks (WLANs), wired networks, wireless networks, metropolitan area networks, and other networks to enable communication between devices.

Network node 560 and WD 510 comprise various components described in more detail below. These components work together in order to provide network node and/or wireless device functionality, such as providing wireless connections in a wireless network. In different embodiments, the wireless network may comprise any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections.

FIGURE 13 illustrates an example network node 560, according to certain embodiments. As used herein, network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a wireless device and/or with other network nodes or equipment in the wireless network to enable and/or provide wireless access to the wireless device and/or to perform other functions (e.g., administration) in the wireless network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)). Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and may then also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and/or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS). Yet further examples of network nodes include multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell/multicast coordination entities (MCEs), core network nodes (e.g., MSCs, MMEs), O&M nodes, OSS nodes, SON nodes, positioning nodes (e.g., E-SMLCs), and/or MDTs. As another example, a network node may be a virtual network node as described in more detail below. More generally, however, network nodes may represent any suitable device (or group of devices) capable, configured, arranged, and/or operable to enable and/or provide a wireless device with access to the wireless network or to provide some service to a wireless device that has accessed the wireless network.

In FIGURE 13, network node 560 includes processing circuitry 570, device readable medium 580, interface 590, auxiliary equipment 584, power source 586, power circuitry 587, and antenna 562. Although network node 560 illustrated in the example wireless network of FIGURE 13 may represent a device that includes the illustrated combination of hardware components, other embodiments may comprise network nodes with different combinations of components. It is to be understood that a network node comprises any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein. Moreover, while the components of network node 560 are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, a network node may comprise multiple different physical components that make up a single illustrated component (e.g., device readable medium 580 may comprise multiple separate hard drives as well as multiple RAM modules).

Similarly, network node 560 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which network node 560 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeB’s. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, network node 560 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate device readable medium 580 for the different RATs) and some components may be reused (e.g., the same antenna 562 may be shared by the RATs). Network node 560 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 560, such as, for example, Global System for Mobile Communication (GSM), Wide Code Division Multiplexing Access (WCDMA), Long Term Evolution (LTE), New Radio (NR), WiFi, or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 560.

Processing circuitry 570 is configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being provided by a network node. These operations performed by processing circuitry 570 may include processing information obtained by processing circuitry 570 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.

Processing circuitry 570 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node 560 components, such as device readable medium 580, network node 560 functionality. For example, processing circuitry 570 may execute instructions stored in device readable medium 580 or in memory within processing circuitry 570. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, processing circuitry 570 may include a system on a chip (SOC).

In some embodiments, processing circuitry 570 may include one or more of radio frequency (RF) transceiver circuitry 572 and baseband processing circuitry 574. In some embodiments, radio frequency (RF) transceiver circuitry 572 and baseband processing circuitry 574 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 572 and baseband processing circuitry 574 may be on the same chip or set of chips, boards, or units.

In certain embodiments, some or all of the functionality described herein as being provided by a network node, base station, eNB or other such network device may be performed by processing circuitry 570 executing instructions stored on device readable medium 580 or memory within processing circuitry 570. In alternative embodiments, some or all of the functionality may be provided by processing circuitry 570 without executing instructions stored on a separate or discrete device readable medium, such as in a hard-wired manner. In any of those embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry 570 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry 570 alone or to other components of network node 560 but are enjoyed by network node 560 as a whole, and/or by end users and the wireless network generally.

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

Interface 590 is used in the wired or wireless communication of signalling and/or data between network node 560, network 506, and/or WDs 510. As illustrated, interface 590 comprises port(s)/terminal(s) 594 to send and receive data, for example to and from network 506 over a wired connection. Interface 590 also includes radio front end circuitry 592 that may be coupled to, or in certain embodiments a part of, antenna 562. Radio front end circuitry 592 comprises filters 598 and amplifiers 596. Radio front end circuitry 592 may be connected to antenna 562 and processing circuitry 570. Radio front end circuitry may be configured to condition signals communicated between antenna 562 and processing circuitry 570. Radio front end circuitry 592 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry 592 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 598 and/or amplifiers 596. The radio signal may then be transmitted via antenna 562. Similarly, when receiving data, antenna 562 may collect radio signals which are then converted into digital data by radio front end circuitry 592. The digital data may be passed to processing circuitry 570. In other embodiments, the interface may comprise different components and/or different combinations of components.

In certain alternative embodiments, network node 560 may not include separate radio front end circuitry 592, instead, processing circuitry 570 may comprise radio front end circuitry and may be connected to antenna 562 without separate radio front end circuitry 592. Similarly, in some embodiments, all or some of RF transceiver circuitry 572 may be considered a part of interface 590. In still other embodiments, interface 590 may include one or more ports or terminals 594, radio front end circuitry 592, and RF transceiver circuitry 572, as part of a radio unit (not shown), and interface 590 may communicate with baseband processing circuitry 574, which is part of a digital unit (not shown).

Antenna 562 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. Antenna 562 may be coupled to radio front end circuitry 590 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In some embodiments, antenna 562 may comprise one or more omni-directional, sector or panel antennas operable to transmit/receive radio signals between, for example, 2 GHz and 66 GHz. An omni-directional antenna may be used to transmit/receive radio signals in any direction, a sector antenna may be used to transmit/receive radio signals from devices within a particular area, and a panel antenna may be a line of sight antenna used to transmit/receive radio signals in a relatively straight line. In some instances, the use of more than one antenna may be referred to as MIMO. In certain embodiments, antenna 562 may be separate from network node 560 and may be connectable to network node 560 through an interface or port.

Antenna 562, interface 590, and/or processing circuitry 570 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by a network node. Any information, data and/or signals may be received from a wireless device, another network node and/or any other network equipment. Similarly, antenna 562, interface 590, and/or processing circuitry 570 may be configured to perform any transmitting operations described herein as being performed by a network node. Any information, data and/or signals may be transmitted to a wireless device, another network node and/or any other network equipment. Power circuitry 587 may comprise, or be coupled to, power management circuitry and is configured to supply the components of network node 560 with power for performing the functionality described herein. Power circuitry 587 may receive power from power source 586. Power source 586 and/or power circuitry 587 may be configured to provide power to the various components of network node 560 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). Power source 586 may either be included in, or external to, power circuitry 587 and/or network node 560. For example, network node 560 may be connectable to an external power source (e.g., an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry 587. As a further example, power source 586 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry 587. The battery may provide backup power should the external power source fail. Other types of power sources, such as photovoltaic devices, may also be used.

Alternative embodiments of network node 560 may include additional components beyond those shown in FIGURE 13 that may be responsible for providing certain aspects of the network node’s functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein. For example, network node 560 may include user interface equipment to allow input of information into network node 560 and to allow output of information from network node 560. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for network node 560.

FIGURE 14 illustrates an example wireless device 510, according to certain embodiments. As used herein, wireless device (WD) refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other wireless devices. Unless otherwise noted, the term WD may be used interchangeably herein with user equipment (UE). Communicating wirelessly may involve transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information through air. In some embodiments, a WD may be configured to transmit and/or receive information without direct human interaction. For instance, a WD may be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the network. Examples of a WD include, but are not limited to, a smart phone, a mobile phone, a cell phone, a voice over IP (VoIP) phone, a wireless local loop phone, a desktop computer, a personal digital assistant (PDA), a wireless cameras, a gaming console or device, a music storage device, a playback appliance, a wearable terminal device, a wireless endpoint, a mobile station, a tablet, a laptop, a laptop-embedded equipment (LEE), a laptop-mounted equipment (LME), a smart device, a wireless customer-premise equipment (CPE) a vehicle-mounted wireless terminal device, etc. A WD may support device -to-de vice (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-everything (V2X) and may in this case be referred to as a D2D communication device. As yet another specific example, in an Internet of Things (IoT) scenario, a WD may represent a machine or other device that performs monitoring and/or measurements and transmits the results of such monitoring and/or measurements to another WD and/or a network node. The WD may in this case be a machine-to-machine (M2M) device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the WD may be a UE implementing the 3GPP narrow band internet of things (NB- IoT) standard. Particular examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, or home or personal appliances (e.g. refrigerators, televisions, etc.) personal wearables (e.g., watches, fitness trackers, etc.). In other scenarios, a WD may represent a vehicle or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation. A WD as described above may represent the endpoint of a wireless connection, in which case the device may be referred to as a wireless terminal. Furthermore, a WD as described above may be mobile, in which case it may also be referred to as a mobile device or a mobile terminal.

As illustrated, wireless device 510 includes antenna 511, interface 514, processing circuitry 520, device readable medium 530, user interface equipment 532, auxiliary equipment 534, power source 536 and power circuitry 537. WD 510 may include multiple sets of one or more of the illustrated components for different wireless technologies supported by WD 510, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, just to mention a few. These wireless technologies may be integrated into the same or different chips or set of chips as other components within WD 510.

Antenna 511 may include one or more antennas or antenna arrays, configured to send and/or receive wireless signals, and is connected to interface 514. In certain alternative embodiments, antenna 511 may be separate from WD 510 and be connectable to WD 510 through an interface or port. Antenna 511, interface 514, and/or processing circuitry 520 may be configured to perform any receiving or transmitting operations described herein as being performed by a WD. Any information, data and/or signals may be received from a network node and/or another WD. In some embodiments, radio front end circuitry and/or antenna 511 may be considered an interface.

As illustrated, interface 514 comprises radio front end circuitry 512 and antenna 511. Radio front end circuitry 512 comprise one or more filters 518 and amplifiers 516. Radio front end circuitry 514 is connected to antenna 511 and processing circuitry 520 and is configured to condition signals communicated between antenna 511 and processing circuitry 520. Radio front end circuitry 512 may be coupled to or a part of antenna 511. In some embodiments, WD 510 may not include separate radio front end circuitry 512; rather, processing circuitry 520 may comprise radio front end circuitry and may be connected to antenna 511. Similarly, in some embodiments, some or all of RF transceiver circuitry 522 may be considered a part of interface 514. Radio front end circuitry 512 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry 512 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 518 and/or amplifiers 516. The radio signal may then be transmitted via antenna 511. Similarly, when receiving data, antenna 511 may collect radio signals which are then converted into digital data by radio front end circuitry 512. The digital data may be passed to processing circuitry 520. In other embodiments, the interface may comprise different components and/or different combinations of components.

Processing circuitry 520 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and/or encoded logic operable to provide, either alone or in conjunction with other WD 510 components, such as device readable medium 530, WD 510 functionality. Such functionality may include providing any of the various wireless features or benefits discussed herein. For example, processing circuitry 520 may execute instructions stored in device readable medium 530 or in memory within processing circuitry 520 to provide the functionality disclosed herein. As illustrated, processing circuitry 520 includes one or more of RF transceiver circuitry 522, baseband processing circuitry 524, and application processing circuitry 526. In other embodiments, the processing circuitry may comprise different components and/or different combinations of components. In certain embodiments processing circuitry 520 of WD 510 may comprise a SOC. In some embodiments, RF transceiver circuitry 522, baseband processing circuitry 524, and application processing circuitry 526 may be on separate chips or sets of chips. In alternative embodiments, part or all of baseband processing circuitry 524 and application processing circuitry 526 may be combined into one chip or set of chips, and RF transceiver circuitry 522 may be on a separate chip or set of chips. In still alternative embodiments, part or all of RF transceiver circuitry 522 and baseband processing circuitry 524 may be on the same chip or set of chips, and application processing circuitry 526 may be on a separate chip or set of chips. In yet other alternative embodiments, part or all of RF transceiver circuitry 522, baseband processing circuitry 524, and application processing circuitry 526 may be combined in the same chip or set of chips. In some embodiments, RF transceiver circuitry 522 may be a part of interface 514. RF transceiver circuitry 522 may condition RF signals for processing circuitry 520.

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

Processing circuitry 520 may be configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being performed by a WD. These operations, as performed by processing circuitry 520, may include processing information obtained by processing circuitry 520 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by WD 510, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.

Device readable medium 530 may be operable to store a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry 520. Device readable medium 530 may include computer memory (e.g., Random Access Memory (RAM) or Read Only Memory (ROM)), mass storage media (e.g., a hard disk), removable storage media (e.g., a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non- transitory device readable and/or computer executable memory devices that store information, data, and/or instructions that may be used by processing circuitry 520. In some embodiments, processing circuitry 520 and device readable medium 530 may be considered to be integrated.

User interface equipment 532 may provide components that allow for a human user to interact with WD 510. Such interaction may be of many forms, such as visual, audial, tactile, etc. User interface equipment 532 may be operable to produce output to the user and to allow the user to provide input to WD 510. The type of interaction may vary depending on the type of user interface equipment 532 installed in WD 510. For example, if WD 510 is a smart phone, the interaction may be via a touch screen; if WD 510 is a smart meter, the interaction may be through a screen that provides usage (e.g., the number of gallons used) or a speaker that provides an audible alert (e.g., if smoke is detected). User interface equipment 532 may include input interfaces, devices and circuits, and output interfaces, devices and circuits. User interface equipment 532 is configured to allow input of information into WD 510 and is connected to processing circuitry 520 to allow processing circuitry 520 to process the input information. User interface equipment 532 may include, for example, a microphone, a proximity or other sensor, keys/buttons, a touch display, one or more cameras, a USB port, or other input circuitry. User interface equipment 532 is also configured to allow output of information from WD 510, and to allow processing circuitry 520 to output information from WD 510. User interface equipment 532 may include, for example, a speaker, a display, vibrating circuitry, a USB port, a headphone interface, or other output circuitry. Using one or more input and output interfaces, devices, and circuits, of user interface equipment 532, WD 510 may communicate with end users and/or the wireless network and allow them to benefit from the functionality described herein. Auxiliary equipment 534 is operable to provide more specific functionality which may not be generally performed by WDs. This may comprise specialized sensors for doing measurements for various purposes, interfaces for additional types of communication such as wired communications etc. The inclusion and type of components of auxiliary equipment 534 may vary depending on the embodiment and/or scenario.

Power source 536 may, in some embodiments, be in the form of a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic devices or power cells, may also be used. WD 510 may further comprise power circuitry 537 for delivering power from power source 536 to the various parts of WD 510 which need power from power source 536 to carry out any functionality described or indicated herein. Power circuitry 537 may in certain embodiments comprise power management circuitry. Power circuitry 537 may additionally or alternatively be operable to receive power from an external power source; in which case WD 510 may be connectable to the external power source (such as an electricity outlet) via input circuitry or an interface such as an electrical power cable. Power circuitry 537 may also in certain embodiments be operable to deliver power from an external power source to power source 536. This may be, for example, for the charging of power source 536. Power circuitry 537 may perform any formatting, converting, or other modification to the power from power source 536 to make the power suitable for the respective components ofWD 510 to which power is supplied.

FIGURE 15 illustrates one embodiment of a UE 600 in accordance with various aspects described herein. As used herein, a user equipment or UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter). UE 600 may be any UE identified by the 3^rd Generation Partnership Project (3GPP), including a NB-IoT UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE. UE 600, as illustrated in FIGURE 15, is one example of a WD configured for communication in accordance with one or more communication standards promulgated by the 3^rd Generation Partnership Project (3GPP), such as 3GPP’s GSM, UMTS, LTE, and/or 5G standards. As mentioned previously, the term WD and UE may be used interchangeable. Accordingly, although FIGURE 15 is a UE, the components discussed herein are equally applicable to a WD, and vice-versa.

In FIGURE 15, UE 600 includes processing circuitry 601 that is operatively coupled to input/output interface 605, radio frequency (RF) interface 609, network connection interface 611, memory 615 including random access memory (RAM) 617, read-only memory (ROM) 619, and storage medium 621 or the like, communication subsystem 631, power source 633, and/or any other component, or any combination thereof. Storage medium 621 includes operating system 623, application program 625, and data 627. In other embodiments, storage medium 621 may include other similar types of information. Certain UEs may utilize all of the components shown in FIGURE 15, or only a subset of the components. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

In FIGURE 15, processing circuitry 601 may be configured to process computer instructions and data. Processing circuitry 601 may be configured to implement any sequential state machine operative to execute machine instructions stored as machine-readable computer programs in the memory, such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logic together with appropriate firmware; one or more stored program, general-purpose processors, such as a microprocessor or Digital Signal Processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 601 may include two central processing units (CPUs). Data may be information in a form suitable for use by a computer.

In the depicted embodiment, input/output interface 605 may be configured to provide a communication interface to an input device, output device, or input and output device. UE 600 may be configured to use an output device via input/output interface 605. An output device may use the same type of interface port as an input device. For example, a USB port may be used to provide input to and output from UE 600. The output device may be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. UE 600 may be configured to use an input device via input/output interface 605 to allow a user to capture information into UE 600. The input device may include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence- sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, another like sensor, or any combination thereof. For example, the input device may be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor.

In FIGURE 15, RF interface 609 may be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna. Network connection interface 611 may be configured to provide a communication interface to network 643a. Network 643a may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network 643a may comprise a Wi-Fi network. Network connection interface 611 may be configured to include a receiver and a transmitter interface used to communicate with one or more other devices over a communication network according to one or more communication protocols, such as Ethernet, TCP/IP, SONET, ATM, or the like. Network connection interface 611 may implement receiver and transmitter functionality appropriate to the communication network links (e.g., optical, electrical, and the like). The transmitter and receiver functions may share circuit components, software or firmware, or alternatively may be implemented separately.

RAM 617 may be configured to interface via bus 602 to processing circuitry 601 to provide storage or caching of data or computer instructions during the execution of software programs such as the operating system, application programs, and device drivers. ROM 619 may be configured to provide computer instructions or data to processing circuitry 601. For example, ROM 619 may be configured to store invariant low-level system code or data for basic system functions such as basic input and output (I/O), startup, or reception of keystrokes from a keyboard that are stored in a non-volatile memory. Storage medium 621 may be configured to include memory such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, floppy disks, hard disks, removable cartridges, or flash drives. In one example, storage medium 621 may be configured to include operating system 623, application program 625 such as a web browser application, a widget or gadget engine or another application, and data fde 627. Storage medium 621 may store, for use by UE 600, any of a variety of various operating systems or combinations of operating systems.

Storage medium 621 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), floppy disk drive, flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro- DIMM SDRAM, smartcard memory such as a subscriber identity module or a removable user identity (SIM/RUIM) module, other memory, or any combination thereof. Storage medium 621 may allow UE 600 to access computer-executable instructions, application programs or the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied in storage medium 621, which may comprise a device readable medium.

In FIGURE 15, processing circuitry 601 may be configured to communicate with network 643b using communication subsystem 631. Network 643a and network 643b may be the same network or networks or different network or networks. Communication subsystem 631 may be configured to include one or more transceivers used to communicate with network 643b. For example, communication subsystem 631 may be configured to include one or more transceivers used to communicate with one or more remote transceivers of another device capable of wireless communication such as another WD, UE, or base station of a radio access network (RAN) according to one or more communication protocols, such as IEEE 802.6, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like. Each transceiver may include transmitter 633 and/or receiver 635 to implement transmitter or receiver functionality, respectively, appropriate to the RAN links (e.g., frequency allocations and the like). Further, transmitter 633 and receiver 635 of each transceiver may share circuit components, software or firmware, or alternatively may be implemented separately.

In the illustrated embodiment, the communication functions of communication subsystem 631 may include data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. For example, communication subsystem 631 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. Network 643b may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network 643b may be a cellular network, a Wi-Fi network, and/or a near-field network. Power source 613 may be configured to provide alternating current (AC) or direct current (DC) power to components of UE 600.

The features, benefits and/or functions described herein may be implemented in one of the components of UE 600 or partitioned across multiple components of UE 600. Further, the features, benefits, and/or functions described herein may be implemented in any combination of hardware, software or firmware. In one example, communication subsystem 631 may be configured to include any of the components described herein. Further, processing circuitry 601 may be configured to communicate with any of such components over bus 602. In another example, any of such components may be represented by program instructions stored in memory that when executed by processing circuitry 601 perform the corresponding functions described herein. In another example, the functionality of any of such components may be partitioned between processing circuitry 601 and communication subsystem 631. In another example, the non-computationally intensive functions of any of such components may be implemented in software or firmware and the computationally intensive functions may be implemented in hardware.

FIGURE 16 is a schematic block diagram illustrating a virtualization environment 700 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to a node (e.g., a virtualized base station or a virtualized radio access node) or to a device (e.g., a UE, a wireless device or any other type of communication device) or components thereof and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components (e.g., via one or more applications, components, functions, virtual machines or containers executing on one or more physical processing nodes in one or more networks). In some embodiments, some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments 700 hosted by one or more of hardware nodes 730. Further, in embodiments in which the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node), then the network node may be entirely virtualized.

The functions may be implemented by one or more applications 720 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operative to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein. Applications 720 are run in virtualization environment 700 which provides hardware 730 comprising processing circuitry 760 and memory 790. Memory 790 contains instructions 795 executable by processing circuitry 760 whereby application 720 is operative to provide one or more of the features, benefits, and/or functions disclosed herein.

Virtualization environment 700, comprises general-purpose or special-purpose network hardware devices 730 comprising a set of one or more processors or processing circuitry 760, which may be commercial off-the-shelf (COTS) processors, dedicated Application Specific Integrated Circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or special purpose processors. Each hardware device may comprise memory 790-1 which may be non-persistent memory for temporarily storing instructions 795 or software executed by processing circuitry 760. Each hardware device may comprise one or more network interface controllers (NICs) 770, also known as network interface cards, which include physical network interface 780. Each hardware device may also include non-transitory, persistent, machine-readable storage media 790-2 having stored therein software 795 and/or instructions executable by processing circuitry 760. Software 795 may include any type of software including software for instantiating one or more virtualization layers 750 (also referred to as hypervisors), software to execute virtual machines 740 as well as software allowing it to execute functions, features and/or benefits described in relation with some embodiments described herein.

Virtual machines 740, comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 750 or hypervisor. Different embodiments of the instance of virtual appliance 720 may be implemented on one or more of virtual machines 740, and the implementations may be made in different ways.

During operation, processing circuitry 760 executes software 795 to instantiate the hypervisor or virtualization layer 750, which may sometimes be referred to as a virtual machine monitor (VMM). Virtualization layer 750 may present a virtual operating platform that appears like networking hardware to virtual machine 740.

As shown in FIGURE 16, hardware 730 may be a standalone network node with generic or specific components. Hardware 730 may comprise antenna 7225 and may implement some functions via virtualization. Alternatively, hardware 730 may be part of a larger cluster of hardware (e.g. such as in a data center or customer premise equipment (CPE)) where many hardware nodes work together and are managed via management and orchestration (MANO) 7100, which, among others, oversees lifecycle management of applications 720.

Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

In the context of NFV, virtual machine 740 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of virtual machines 740, and that part of hardware 730 that executes that virtual machine, be it hardware dedicated to that virtual machine and/or hardware shared by that virtual machine with others of the virtual machines 740, forms a separate virtual network elements (VNE).

Still in the context of NFV, Virtual Network Function (VNF) is responsible for handling specific network functions that run in one or more virtual machines 740 on top of hardware networking infrastructure 730 and corresponds to application 720 in FIGURE 16.

In some embodiments, one or more radio units 7200 that each include one or more transmitters 7220 and one or more receivers 7210 may be coupled to one or more antennas 7225. Radio units 7200 may communicate directly with hardware nodes 730 via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be affected with the use of control system 7230 which may alternatively be used for communication between the hardware nodes 730 and radio units 7200.

FIGURE 17 depicts a method 800 by a first network node 560 maintaining an active data plane connection with a wireless device 510, according to certain embodiments. At step 802, the first network node 560 receives resource status information from a second network node. At step 804, the first network node 560 determines whether to change the active data plane connection for the wireless device 510 to the second network node based on the resource status information.

In a particular embodiment, the first network node 560 transmits a resource status request to the second network node. The resource status information is received from the second network node in response to the resource status request.

In a particular embodiment, the first network node 560 comprises a S-SN 105 and the second network node comprises a T-SN 110.

In a particular embodiment, determining whether to change the active data plane connection is also based on at least one measurement associated with a cell associated with the secondary-SN node.

In a particular embodiment, the first network node 560 receives the at least one measurement from the wireless device 510. In a further particular embodiment, the first network node 560 receives the at least one measurement from a third network node operating as a MN 115.

In a particular embodiment, the first network node 560 may determine to change the active data plane connection for the wireless device 510 and transmit a data plane connection change request to a third network node. In a further particular embodiment, the third network node comprises a MN 115, which has a control plane connection with the wireless device 510.

In a particular embodiment, the first network node 560 receives a message from the third network node, and the message includes an indication that the data plane connection change request is accepted.

In a particular embodiment, the first network node 560 receives a message from the third network node, and the message includes an indication that the data plane connection change request is rejected. In a particular embodiment, the resource status information comprises load information associated with the second network node. In a further particular embodiment, determining whether to change the active data plane connection is based on the load information associated with the second network node. In yet another further particular embodiment, the load information indicates an available capacity of at least one radio cell associated with the second network node. For example, in a particular embodiment, the available capacity of the at least one radio cell comprises at least one of: per SSB coverage area, per SSB group coverage area, per bandwidth part, and per network slice.

FIGURE 18 illustrates a schematic block diagram of a virtual apparatus 900 in a wireless network (for example, the wireless network shown in FIGURE 12). The apparatus may be implemented in a wireless device or network node (e.g., wireless device 510 or network node 560 shown in FIGURE 12). Apparatus 900 is operable to carry out the example method described with reference to FIGURE 17 and possibly any other processes or methods disclosed herein. It is also to be understood that the method of FIGURE 17 is not necessarily carried out solely by apparatus 900. At least some operations of the method can be performed by one or more other entities.

Virtual Apparatus 900 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments. In some implementations, the processing circuitry may be used to cause receiving module 910, determining module 920, and any other suitable units of apparatus 900 to perform corresponding functions according one or more embodiments of the present disclosure.

According to certain embodiments, receiving module 910 may perform certain of the receiving functions of the apparatus 900. For example, receiving module 910 may receive resource status information from a second network node. According to certain embodiments, determining module 920 may perform certain of the determining functions of the apparatus 900. For example, determining module 920 may determine whether to change the active data plane connection for the wireless device 510 to the second network node based on the resource status information.

The term unit may have conventional meaning in the field of electronics, electrical devices and/or electronic devices and may include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein.

FIGURE 19 depicts a method 1000 by a first network node 560 such as a S-SN 105 that maintains an active data plane connection with a wireless device 510, according to certain embodiments. At step 1002, S-SN 105 receives resource status information from a T-SN 110. At step 1004, S-SN 105 determines whether to change the active data plane connection for the wireless device 510 to the T-SN 110 based on the resource status information. At step 1006, S- SN 105 transmits, to a MN 115 having a control plane connection with the wireless device 510, the resource status information received from the T-SN.

In a particular embodiment, the resource status information is transmitted to the MN with a data plane connection change request.

In a particular embodiment, S-SN 105 receives a message from the MN 115, and the message includes an indication that the data plane connection change request is accepted or an indication that the data plane connection change request is rejected.

In a particular embodiment, S-SN 105 transmits a resource status request to the T-SN 110, and the resource status information is received from the T-SN 110 in response to the resource status request.

In a particular embodiment, the step of determining whether to change the active data plane connection at 1004 is based on at least one measurement associated with a cell associated with the target secondary node. In a further particular embodiment, S-SN 105 receives the at least one measurement from the wireless device 510 or a MN 115.

In a particular embodiment, the resource status information comprises at least one of load information associated with the target secondary network node and an available capacity associated with the target secondary network node. The step of determining whether to change the active data plane connection at step 1004 is based on at least one of the load information and the available capacity associated with the target network node. In a further particular embodiment, at least one of the load information and the available capacity associated with the T-SN is associated with at least one of: a per SSB coverage area, a per SSB group coverage area, a coverage area of one or more SSB beams, a per bandwidth part, and a per network slice.

FIGURE 20 illustrates a schematic block diagram of a virtual apparatus 1100 in a wireless network (for example, the wireless network shown in FIGURE 12). The apparatus may be implemented in a wireless device or network node (e.g., wireless device 510 or network node 560 shown in FIGURE 12). Apparatus 1100 is operable to carry out the example method described with reference to FIGURE 19 and possibly any other processes or methods disclosed herein. It is also to be understood that the method of FIGURE 19 is not necessarily carried out solely by apparatus 1100. At least some operations of the method can be performed by one or more other entities.

Virtual Apparatus 1100 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments. In some implementations, the processing circuitry may be used to cause receiving module 1110, determining module 1120, transmitting module 1130, and any other suitable units of apparatus 1100 to perform corresponding functions according one or more embodiments of the present disclosure.

According to certain embodiments, receiving module 1110 may perform certain of the receiving functions of the apparatus 1100. For example, receiving module 1110 may receive resource status information from a T-SN 110.

According to certain embodiments, determining module 1120 may perform certain of the determining functions of the apparatus 1100. For example, determining module 1120 may determine whether to change the active data plane connection for the wireless device 510 to the T-SN 110 based on the resource status information. According to certain embodiments, transmitting module 1130 may perform certain of the transmitting functions of the apparatus 1100. For example, transmitting module 1130 may transmit, to a MN 115 having a control plane connection with the wireless device 510, the resource status information received from the T-SN.

FIGURE 21 depicts a method 1200 by a first network node 560, according to certain embodiments. At step 1202, the first network node 560 transmits resource status information to a second network node. At step 1204, the first network node 560 receives, from the second network node, a request to change an active data plane connection for a wireless device 510 from the second network node to a first network node 560.

In a particular embodiment, the first network node 560 receives a resource status request from the second network node. The resource status information is transmitted to the second network node in response to receiving the resource status request from the second network node.

In a particular embodiment, the second network node comprises a S-SN 105 and the first network node comprises a T-SN 110.

In a particular embodiment, the resource status information comprises load information associated with the first network node 560. In a further particular embodiment, the load information indicates an available capacity of at least one radio cell associated with the first network node. For example, in a particular embodiment, the available capacity of the at least one radio cell comprises at least one of: per SSB coverage area, per SSB group coverage area, per bandwidth part, and per network slice.

FIGURE 22 illustrates a schematic block diagram of a virtual apparatus 1300 in a wireless network (for example, the wireless network shown in FIGURE 12). The apparatus may be implemented in a wireless device or network node (e.g., wireless device 510 or network node 560 shown in FIGURE 12). Apparatus 1300 is operable to carry out the example method described with reference to FIGURE 21 and possibly any other processes or methods disclosed herein. It is also to be understood that the method of FIGURE 21 is not necessarily carried out solely by apparatus 1300. At least some operations of the method can be performed by one or more other entities.

Virtual Apparatus 1300 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments. In some implementations, the processing circuitry may be used to cause transmitting module 1310, receiving module 1320, and any other suitable units of apparatus 1300 to perform corresponding functions according one or more embodiments of the present disclosure.

According to certain embodiments, transmitting module 1310 may perform certain of the transmitting functions of the apparatus 1300. For example, transmitting module 1310 may transmit resource status information to a second network node.

According to certain embodiments, receiving module 1320 may perform certain of the receiving functions of the apparatus 1300. For example, receiving module 1320 may receive, from the second network node, a request to change an active data plane connection for a wireless device from the second network node to a first network node.

FIGURE 23 depicts a method 1400 by a first network node 560 that operates as a T-SN 110, according to certain embodiments. At step 1402, the T-SN 110 transmits resource status information to a S-SN 105 maintaining an active data plane connection with a wireless device 510. At step 1404, the T-SN 110 receives a request to change the active data plane connection for the wireless device 510 from the S-SN 105 to the T-SN 110. In a particular embodiment, the step of receiving of step 1404 includes receiving a resource status request from the S-SN 105, and the resource status information is transmitted to the S-SN 105 in response to receiving the resource status request from the S-SN 105.

In a particular embodiment, the resource status information includes at least one of load information associated with the target secondary network node and an available capacity associated with the target secondary network node. In a further particular embodiment, at least one of the load information and the available capacity associated with the T-SN is associated with at least one of: a per SSB coverage area, a per SSB group coverage area, a coverage area of one or more SSB beams, a per bandwidth part, and a per network slice.

FIGURE 24 illustrates a schematic block diagram of a virtual apparatus 1500 in a wireless network (for example, the wireless network shown in FIGURE 12). The apparatus may be implemented in a wireless device or network node (e.g., wireless device 510 or network node 560 shown in FIGURE 12). Apparatus 1500 is operable to carry out the example method described with reference to FIGURE 23 and possibly any other processes or methods disclosed herein. It is also to be understood that the method of FIGURE 23 is not necessarily carried out solely by apparatus 1500. At least some operations of the method can be performed by one or more other entities.

Virtual Apparatus 1500 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments. In some implementations, the processing circuitry may be used to cause transmitting module 1510, receiving module 1520, and any other suitable units of apparatus 1500 to perform corresponding functions according one or more embodiments of the present disclosure.

According to certain embodiments, transmitting module 1510 may perform certain of the transmitting functions of the apparatus 1500. For example, transmitting module 1510 may transmit resource status information to a S-SN 105 maintaining an active data plane connection with a wireless device 510.

According to certain embodiments, receiving module 1520 may perform certain of the receiving functions of the apparatus 1500. For example, receiving module 1520 may receive a request to change the active data plane connection for the wireless device 510 from the S-SN 105 to the T-SN 110.

FIGURE 25 depicts a method 1600 by a first network node 560 operating as a MN 115 for a wireless device 510, according to certain embodiments. At step 1602, the first network node 560 receives resource status information from a second network node operating as a S- SN 105 for the wireless device 510. The S-SN 105 has an active data plane connection with the wireless device 510. At step 1604, the first network node 560 determines whether to change the active data plane connection for the wireless device 510 to a third network node based on the resource status information.

In a particular embodiment, the second network node comprises S-SN 105 node and the third network node comprises a T-SN 110.

In a particular embodiment, determining whether to change the active data plane connection is also based on at least one measurement associated with a cell associated with the T-SN 110. In a particular embodiment, the first network node 560 receives the at least one measurement from the wireless device 510. In another particular embodiment, the firstnetwork node 560 may receive the at least one measurement from the second network node.

In a particular embodiment, the determining comprises determining to change the active data plane connection for the wireless device 510 and transmitting a data plane connection change request to a third network node.

In a particular embodiment, the first network node 560 has a control plane connection with the wireless device 510. In a particular embodiment, the first network node 560 receives a message to the second network node, and the message includes an indication that the data plane connection change request is accepted.

In a particular embodiment, the first network node 560 transmits a message to the second network node, and the message comprises an indication that the data plane connection change request is rejected.

In a particular embodiment, the resource status information comprises load information associated with the third network node.

In a particular embodiment, determining whether to change the active data plane connection is based on the load information associated with the third network node.

In a particular embodiment, the load information indicates an available capacity of at least one radio cell associated with the third network node. For example, in a particular embodiment, the available capacity of the at least one radio cell comprises at least one of: per SSB coverage area, per SSB group coverage area, per bandwidth part, and per network slice.

FIGURE 26 illustrates a schematic block diagram of a virtual apparatus 1700 in a wireless network (for example, as shown in FIGURE 12). The apparatus may be implemented in a wireless device or network node (e.g., wireless device 510 or network node 560 shown in FIGURE 12). Apparatus 1700 is operable to carry out the example method described with reference to FIGURE 25 and possibly any other processes or methods disclosed herein. It is also to be understood that the method of FIGURE 25 is not necessarily carried out solely by apparatus 1700. At least some operations of the method can be performed by one or more other entities.

Virtual Apparatus 1700 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments. In some implementations, the processing circuitry may be used to cause receiving module 1710, determining module 1720, and any other suitable units of apparatus 1700 to perform corresponding functions according one or more embodiments of the present disclosure.

According to certain embodiments, receiving module 1710 may perform certain of the receiving functions of the apparatus 1700. For example, receiving module 1710 may receive resource status information from a second network node operating as a S-SN 105 for the wireless device 510. The S-SN 105 has an active data plane connection with the wireless device 510.

According to certain embodiments, determining module 1720 may perform certain of the determining functions of the apparatus 1700. For example, determining module 1720 may determine whether to change the active data plane connection for the wireless device 510 to a third network node based on the resource status information.

FIGURE 27 depicts another method 1800 by a first network node 560 operating as a MN 115 for a wireless device 510, according to certain embodiments. At step 1802, the MN 115 receives resource status information from a S-SN 105 having an active data plane connection with the wireless device 510. The resource status information is associated with a T-SN 110. Based on the resource status information, the MN 115 determines, at step 1802, whether to change the active data plane connection for the wireless device 510 to the T-SN 110

In a particular embodiment, the MN 115 receives a data plane connection change request from the S-SN 105 having the data plane connection with the wireless device 510. The S-SN 105 determines whether to change the active data plane connection for the wireless device 510 based on the receiving the data plane connection change request. In a further particular embodiment, the MN 115 transmits a message to the S-SN 105 that includes an indication that the data plane connection change request is accepted or an indication that the data plane connection change request is rejected.

In a particular embodiment, the step of determining whether to change the active data plane connection at step 1804 is based on at least one measurement associated with a cell associated with the T-SN 110. In a further particular embodiment, the MN 115 receives the at least one measurement from the wireless device 510 or the S-SN 105.

In a particular embodiment, the determining of step 1804 includes determining to change the active data plane connection for the wireless device 510 and transmitting a data plane connection change request to the T-SN 110. In a further particular embodiment, the MN 115 has a control plane connection with the wireless device 510.

In a particular embodiment, the resource status information comprises at least one of load information of at least one radio cell associated with the target secondary network node and an available capacity of at least one radio cell associated with the target secondary network node. In a further particular embodiment, the at least one of the load information and the available capacity of the at least one radio cell is associated with at least one of: a per SSB coverage area, a per SSB group coverage area, a per bandwidth part, and a per network slice.

In a particular embodiment, determining whether to change the active data plane connection at step 1804 is based on the load information of the at least one radio cell associated with the T-SN 110.

FIGURE 28 illustrates a schematic block diagram of a virtual apparatus 1900 in a wireless network (for example, as shown in FIGURE 12). The apparatus may be implemented in a wireless device or network node (e.g., wireless device 510 or network node 560 shown in FIGURE 12). Apparatus 1900 is operable to carry out the example method described with reference to FIGURE 27 and possibly any other processes or methods disclosed herein. It is also to be understood that the method of FIGURE 27 is not necessarily carried out solely by apparatus 1900. At least some operations of the method can be performed by one or more other entities.

Virtual Apparatus 1900 may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments. In some implementations, the processing circuitry may be used to cause receiving module 1910, determining module 1920, and any other suitable units of apparatus 1900 to perform corresponding functions according one or more embodiments of the present disclosure.

According to certain embodiments, receiving module 1910 may perform certain of the receiving functions of the apparatus 1900. For example, receiving module 1910 may receive resource status information from a S-SN 105 having an active data plane connection with the wireless device 510. The resource status information is associated with a T-SN 110.

According to certain embodiments, determining module 1920 may perform certain of the determining functions of the apparatus 1900. For example, determining module 1920 may determine whether to change the active data plane connection for the wireless device 510 to the T-SN 110 based on the resource status information.

Modifications, additions, or omissions may be made to the systems and apparatuses described herein without departing from the scope of the disclosure. The components of the systems and apparatuses may be integrated or separated. Moreover, the operations of the systems and apparatuses may be performed by more, fewer, or other components. Additionally, operations of the systems and apparatuses may be performed using any suitable logic comprising software, hardware, and/or other logic. As used in this document,“each” refers to each member of a set or each member of a subset of a set.

Modifications, additions, or omissions may be made to the methods described herein without departing from the scope of the disclosure. The methods may include more, fewer, or other steps. Additionally, steps may be performed in any suitable order.

Although this disclosure has been described in terms of certain embodiments, alterations and permutations of the embodiments will be apparent to those skilled in the art. Accordingly, the above description of the embodiments does not constrain this disclosure. Other changes, substitutions, and alterations are possible without departing from the spirit and scope of this disclosure.

Claims

1. A method (1000) performed by a source secondary network node, S-SN, (105) maintaining an active data plane connection with a wireless device (510), the method comprising:

receiving (1002) resource status information from a target secondary network node, T- SN, (110);

determining (1004) to change the active data plane connection for the wireless device to the T-SN based on the resource status information; and

transmitting, to a master network node, MN, having a control plane connection with the wireless device, the resource status information received from the T-SN.

2. The method of Claim 1, wherein the resource status information is transmitted to the MN with a data plane connection change request e.

3. The method of Claim 2, further comprising receiving a message from the MN, the message comprising:

an indication that the data plane connection change request is accepted, or an indication that the data plane connection change request is rejected.

4. The method of any one of Claims 1 to 3, further comprising transmitting a resource status request to the T-SN, and wherein the resource status information is received from the T- SN in response to the resource status request.

5. The method of any one of the Claims 1 to 4, wherein determining whether to change the active data plane connection is based on at least one measurement associated with a cell associated with the T-SN.

6. The method of Claim 5, further comprising receiving the at least one measurement from the wireless device or the MN.

7. The method of any one of Claims 1 to 6, wherein:

the resource status information comprises at least one of:

load information associated with the T-SN, or an available capacity associated with the T-SN, and

determining whether to change the active data plane connection is based on at least one of the load information and the available capacity associated with the T-SN.

8. The method of Claim 7, wherein at least one of the load information and the available capacity associated with the T-SN is associated with at least one of: a radio cell of the T-SN, a SSB coverage area, a SSB group coverage area, a coverage area of one or more SSB beams, a bandwidth part, and a network slice.

9. A method (1400) performed by a target secondary network node, T-SN (110), the method comprising:

transmitting (1402) resource status information to a source secondary network node, S- SN (105), maintaining an active data plane connection with a wireless device (510); and receiving (1404) a request to change the active data plane connection for the wireless device from the S-SN to the T-SN.

10. The method of Claim 9, further comprising receiving a resource status request from the S-SN, and wherein the resource status information is transmitted to the S-SN in response to receiving the resource status request from the S-SN.

11. The method of any one of Claims 9 to 10, wherein the resource status information comprises at least one of:

load information of at least one radio cell associated with the T-SN, and

an available capacity of at least one radio cell associated with the T-SN.

12. The method of Claim 11, wherein the at least one of load information and the available capacity of the at least one radio cell is associated with at least one of: a per SSB coverage area, a per SSB group coverage area, a per bandwidth part, and a per network slice.

13. A method (1800) performed by a master network node, MN (115), for a wireless device (510), the method comprising:

receiving (1802) resource status information from a source secondary network node, S- SN (105), having an active data plane connection with the wireless device, the resource status information being associated with a target secondary network node, T-SN (110); and

based on the resource status information, determining whether to change the active data plane connection for the wireless device to the T-SN.

14. The method of Claim 13, further comprising receiving a data plane connection change request from the S-SN having the data plane connection with the wireless device, and determining whether to change the active data plane connection for the wireless device based on the receiving the data plane connection change request.

15. The method of Claim 14, further comprising transmitting a message to the S-SN, the message comprising:

16. The method of any one of the Claims 13 to 15, wherein determining whether to change the active data plane connection is based on at least one measurement associated with a cell associated with the T-SN.

17. The method of Claim 16, further comprising receiving the at least one measurement from the wireless device or the S-SN.

18. The method of any one of Claims 13 to 17, wherein the determining comprises determining to change the active data plane connection for the wireless device and transmitting a data plane connection change request to T-SN.

19. The method of Claim 18, wherein the MN has a control plane connection with the wireless device.

20. The method of any one of Claims 13 to 19, wherein the resource status information comprises at least one of:

load information associated with the T-SN, and

an available capacity associated with the T-SN.

21. The method of Claim 20, wherein the at least one of the load information and the available capacity of the at least one radio cell is associated with at least one of: a radio cell of the T-SN, a SSB coverage area, a SSB group coverage area, a coverage area of one or more SSB beams, a bandwidth part, and a network slice.

22. The method of any one of Claims 20 to 21, wherein determining whether to change the active data plane connection is based on the load information of the at least one radio cell associated with the T-SN.

23. A source secondary network node, S-SN (105), maintaining an active data plane connection with a wireless device (510), the S-SN comprising:

processing circuitry (570) configured to:

receive resource status information from a target secondary network node, T-

SN (110); and

determine whether to change the active data plane connection for the wireless device to the T-SN based on the resource status information; and

transmit, to a master network node, MN, having a control plane connection with the wireless device, the resource status information received from the T-SN.

24. The S-SN of Claim 23, wherein the processing circuitry is configured to perform any of the steps of Claims 2 to 8.

25. A target secondary network node, T-SN (110), comprising:

processing circuitry (570) configured to:

transmit resource status information to a source secondary network node, S-SN (105), maintaining an active data plane connection with a wireless device (510); and

receive a request to change the active data plane connection for a wireless device from the S-SN to the T-SN.

26. The T-SN of Claim 25, wherein the processing circuitry is configured to perform any of the steps of Claims 10 to 12.

27. A master network node, MN (115), for a wireless device (510), the MN comprising: processing circuitry (570) configured to:

receive resource status information from a source secondary network node, S- SN (105), having an active data plane connection with the wireless device, the resource status information comprising load information associated with a target secondary network node, T- SN (110); and

based on the resource status information, determine whether to change the active data plane connection for the wireless device to the T-SN.

28. The MN of Claim 27, wherein the processing circuitry is configured to perform any of the steps of Claims 14 to 22.