WO2024014998A1

WO2024014998A1 - Methods and apparatuses to improve carrier aggregation and dual- connectivity for network energy saving

Info

Publication number: WO2024014998A1
Application number: PCT/SE2023/050658
Authority: WO
Inventors: Meysam AGHIGHI; Nianshan SHI; Sofia Svedevall; Ari Kangas
Original assignee: Telefonaktiebolaget Lm Ericsson (Publ)
Priority date: 2022-07-14
Filing date: 2023-06-26
Publication date: 2024-01-18

Abstract

Embodiments described herein relate to methods and apparatuses for improving carrier aggregation and dual connectivity. A method in a distributed unit of a first network node comprises transmitting, to a central unit of the first network node, first sleep information related to one or more first cells serviced by the distributed unit of the first network node.

Description

METHODS AND APPARATUSES TO IMPROVE CARRIER AGGREGATION AND DUAL CONNECTIVITY FOR NETWORK ENERGY SAVING

TECHNICAL FIELD

Embodiments described herein relate to methods and apparatuses to improve carrier aggregation and dual connectivity for network energy saving.

BACKGROUND

NR Architecture

[1] In the higher layer split Next Generation Radio Access Network (NG-RAN) node architecture, each NG-RAN node comprises a gNB Central unit (gNB-CU) and one or more gNB distributed unit (gNB-DU) logical entities, as illustrated in Figure 1.

Figure 1 illustrates a next generation radio access network (NG-RAN) node architecture.

The Core Network (5GC) connects to the NG-RAN nodes over N2 interface at the control plane, and N3 interface over the user plane. These connections (e.g. N2 and N3) are depicted as a single NG interface in figure 1. gNBs in the NG-RAN are connected through an Xn interface between gNB-CUs. In the split architecture, each gNB-CU is connected to one or more gNB-DUs via Fl interfaces. Service Data Adaptation Protocol (SDAP)/ Packet Data Convergence Protocol (PDCP) and Radio Resource Control (RRC) protocol resides in gNB- CU. Radio Link Control (RLC)/ Media Access Control (MAC)/ Physical Layer (PHY) protocols reside in gNB-DU.

Handover

There are two types of handover in New Radio (NR): Xn based handover and NG based handover.

In the Xn based handover, the preparation and execution phase of the handover procedure are performed between the gNBs without involvement of the core network. In other words, the Xn interface is utilised to perform the handover.

In the NG based handover, the preparation and execution phase of the handover are performed using signalling via the core network (5GC).

Dual Connectivity

In NR Dual Connectivity (DC), a User Equipment (UE) may be connected to one gNB that acts as a Master node (MN) and another gNB that acts as a Secondary Node (SN). In addition, a UE may connect to a single gNB, acting both as a MN and as a SN, and configuring both a Master Cell Group (MCG) and a Secondary Cell Group (SCG).

Carrier Aggregation

In NR carrier aggregation, a UE may be connected to a PCell (Primary Cell) and one or several SCells (Secondary Cell). Then MAC layer on the PCell will multiplex the user data and distribute it among the serving cells (PCell and SCells).

Figure 2 illustrates NR carrier aggregation.

Time Critical Communication

Time critical communication comprises services that require bounded latency, given a minimum level of reliability. One example of time critical communication may be user-plane data which may be required to arrive at the UE in less than 20ms in more than 99.9% of cases. Examples of such time critical services may be voice data, remote control data, Augmented Reality (XR)/ Virtual Reality (VR), etc.

Network Energy Saving

A cell may be considered to be operating in a sleep mode if part of or all the cell is switched off to save energy.

There are different types of sleep mode for a cell. For example:

1. Short sleep: which may be performed when there is expected to be no transmission in the cell. A short sleep may not affect the accessibility of the cell and might have a small impact on the overall throughput. This kind of sleep is usually expected to be less than 20ms.

2. Long sleep: which may be performed when there is expected to be neither transmission nor a need to access the cell for a longer period than a short sleep. A long sleep may be likely to have an impact on the overall throughput and might also have a small impact on the overall accessibility. This kind of sleep is usually expected to be less than 160ms.

3. Deep sleep: which may be performed when there is no UE (User Equipment) connected to the cell and the cell is completely unusable for a period. This type of sleep may take from a few seconds up to a few hours and may be performed especially when the load is low in the network (e.g., during night-time).

Figure 3 illustrates different cells in a network. It will be appreciated that the cells are depicted vertically above a geographical area that they service or serve. For example, the area serviced by cells 301 overlaps with the area serviced by cells 302, 305 and 304. 301 overlaps with the area serviced/served by cells 302, 305 and 304. As an example, cells 301 and 303 may be put into a deep sleep mode during night-time without having an impact on the accessibility of the system. This is because the remaining cells/layers (302, 304 and 305) will be awake and may therefore be able to provide enough service to whichever few UEs still require night-time service that may otherwise have been served by the 301 or 303 cells. In principle, all cells except cell 304 may be put into (at least) the short sleep mode as soon as there is a period of no requested data transmission, as the cell 304 can cover the areas serviced/served by all of the other depicted cells.

Figure 3 illustrates examples of cells in a network.

SUMMARY

There currently exist certain challenge(s).

1. Presently, when a wireless device is configured with carrier aggregation or dual connectivity, the entity that is in charge of how data is split between serving cells (MAC multiplexer in case of carrier aggregation, and PDCP multiplexer in case of dual connectivity) may redirect data onto another serving cell that is in a short or a long sleep mode. This may result in performance degradation. Currently, there is no way to communicate the sleep status and/or type of sleep other serving cells are experiencing from one node to another node in the network.

2. Presently, when a wireless device is configured with carrier aggregation or dual connectivity, there is no mechanism for the serving cells to communicate and align their sleep patterns (a model under which the cells enter and leave sleep periods) with each other. This results in each cell either not entering sleep periods to avoid performance degradation when it may be well compensated for by other cells that are not in sleep periods, or entering sleep periods and thereby causing performance degradations in cases of ongoing carrier aggregation or dual connectivity as other cells are also entering sleep periods.

Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. Embodiments described herein provide methods and apparatuses for a gNB- DU to report sleep information (e.g. sleep statuses and sleep patterns) of its cells to its neighbor gNB-DUs. Whether they are served by the same gNB-CU or by different gNB- CU. In this way, the neighbor gNB-DUs may act accordingly when performing data splitting in relation to carrier aggregation or dual connectivity. In current solutions, a gNB- DU does not know the sleep status and the sleep pattern of the cells on other gNB-DUs, and due to this there may be performance degradation and/or accessibility problems when there is ongoing data splitting and energy saving features.

Embodiments described herein provide methods for the gNB-DUs to not only inform each other of ongoing cell sleeps, but also coordinate the sleep durations and patterns in order to allow for maximum energy savings with minimum performance degradation.

Certain embodiments may provide one or more of the following technical advantage(s).

1. Reduced or no performance degradation due to cell sleep in carrier aggregation and dual connectivity, by reporting the sleep status of cells to neighbor nodes. Without the embodiments described herein, a Primary Cell (PCell) and Secondary Cell (SCell), or a Primary Cell (PCell) and Primary Secondary Cell (PSCell), may go to sleep at the same time and cause service interruption for time critical services. Furthermore, without the embodiments described herein a PCell may schedule data on an SCell (or PSCell) which is in sleep mode and may therefore cause performance degradation (lower throughput or higher latency or both).

2. Embodiments described herein allow serving cells in carrier aggregation and dual connectivity to enter sleep modes whilst resulting in no or little performance degradation, by reporting and coordinating the sleep pattern of cells to neighbor nodes. With the embodiments described herein, the serving cells (e.g., PCell and SCell) may therefore coordinate their sleep patterns with each other to secure performance. For example, to ensure that, for time-critical services that are configured with carrier aggregation and/or dual connectivity, at least one serving cell is not in a sleep mode, at all times.

According to some embodiments there is provided a method performed by a distributed unit of a first network node The method comprises transmitting, to a central unit of the first network node, first sleep information related to one or more first cells serviced by the distributed unit of the first network node.

According to some embodiments there is provided a method performed by a central unit of a first network node The method comprises receiving, from a distributed unit of the first network node, first sleep information related to one or more first cells serviced by the distributed unit of the first network node.

According to some embodiments there is provided a distributed unit of a first network node. The distributed unit comprises processing circuitry configured to cause the first network node to: transmit, to a central unit of the first network node, first sleep information related to one or more first cells serviced by the distributed unit of the first network node. According to some embodiments there is provided a central unit of a first network node. The central unit comprises processing circuitry configured to cause the central unit to: receive, from a distributed unit of the first network node, first sleep information related to one or more first cells serviced by the distributed unit of the first network node.

According to some embodiments there is provided a computer program comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out a method as described above.

According to some embodiments there is provided a computer program product comprising non transitory computer readable media having stored thereon a computer program as described above.

BRIEF DESCRIPTION OF THE DRAWINGS

For a better understanding of the embodiments of the present disclosure, and to show how it may be put into effect, reference will now be made, by way of example only, to the accompanying drawings, in which:

Figure 1 illustrates NG-RAN node architecture;

Figure 2 illustrates NR carrier aggregation;

Figure 3 illustrates examples of cells in a network;

Figure 4 illustrates a method in accordance with some embodiments;

Figure 5 illustrates a method in accordance with some embodiments;

Figure 6 illustrates an example how sleep information may be dispersed through the network;

Figure 7 illustrates an example of utilising sleep information in carrier aggregation;

Figure 8 illustrates an example of coordinating sleep patterns;

Figure 9 illustrates an example implementation using gNB-CU-CP and gNB-CU-UP

Figure 10 illustrates an example implementation using O-DU and O-CU-CP

Figure 11 shows an example of a communication system 1100 in accordance with some embodiments;

Figure 12 shows a UE 1200;

Figure 13 shows a network node 1300 in accordance with some embodiments;

Figure 14 shows a host 1400 in accordance with some embodiments; Figure 15 shows a virtualization environment 1500 in which functions implemented by some embodiments may be virtualized; and

Figure 16 shows a communication diagram of a host 1602 communicating via a network node 1604 with a UE 1606 over a partially wireless connection in accordance with some embodiments

DETAILED DESCRIPTION

Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art. Additional information may also be found in the document(s) provided in the Appendix.

Figure 4 illustrates a method in accordance with some embodiments.

Figure 4 depicts a method in accordance with particular embodiments. The method 4 may be performed by a first network node (e.g. the network node 1110 or network node 1300 as described later with reference to Figures 11 and 12 respectively). It will be appreciated that the method of figure 4 may be performed by a distributed unit of a first network node (e.g. gNB- DU). The method begins at step 402 with transmitting, to a central unit of the first network node, first sleep information related to one or more first cells serviced by the distributed unit of the first network node.

Figure 5 illustrates a method in accordance with some embodiments.

Figure 5 depicts a method in accordance with particular embodiments. The method of Figure 5 may be performed by a first network node (e.g. the network node 1110 or network node 1300 as described later with reference to Figures 11 and 13 respectively). It will be appreciated that the method of figure 5 may be performed by a central unit of a first network node. The method begins at step 502 with receiving, from a distributed unit of the first network node, first sleep information related to one or more first cells serviced by the distributed unit of the first network node.

In some embodiments the first sleep information comprises sleep statuses of the one or more first cells and/or sleep patterns of the one or more cells. The first sleep information may be transmitted over an Fl-AP interface between the distributed unit and the central unit of the first network node. For example, the distributed unit of the first network node may transmit to the central unit of the first network node, the ‘sleep status’ of its cells, for example over the Fl-AP interface. The sleep status may comprise any type of cell sleep that is already agreed upon over the system. E.g., short sleep, long sleep, deep sleep, etc. as mentioned above.

The central unit of the first network node may then forward the first sleep information to central units of one or more second network nodes. For example, the sleep status of the cells received from all distributed units that are connected to a central unit, may be forwarded to all the second central units that are connected to it, for example, over corresponding Xn- AP interfaces. The central unit of the first network node may therefore receive, from a central unit of a second network node, second sleep information related to one or more second cells serviced by the second network node. The second sleep information may be received over an XN-AP interface between the central unit of the first network node and the central unit of the second network node. The central unit of the first network node may then forward the second sleep information to one or more distributed units of the first network node, for example over an Fl-AP interface.

Figure 6 illustrates an example of how sleep information may be dispersed through the network. A distributed unit of a first network node may therefore receive an indication of second sleep information relating to one or more second cells serviced by one or more neighboring distributed units. The second sleep information may be received over an Fl-AP interface between the distributed unit and the central unit.

In some examples, the second sleep information comprises sleep statuses of the one or more second cells. The distributed unit of the first network node may then execute data splitting with the one or more second cells in relation to carrier aggregation and/or dual connectivity for one or more wireless devices serviced by the one or more first cells based on the sleep statuses of the one or more second cells.

In other words, the distributed unit of the first network node may perform the data splitting in relation to carrier aggregation and dual connectivity in such a way to avoid causing performance degradation. Performance degradation may comprise but is not limited to lower throughput and/or higher latency.

Figure 7 illustrates an example of utilising sleep information in carrier aggregation. For example, in Figure 7 cell A serves as the PCell (Primary Cell) for both UEs. One UE is running a critical service (for example, GBR - Guaranteed Bitrate, or TCC - Time-Critical Communication) while the other UE is not running a critical service.

At the same time, cell A has received second sleep information from Cell B and Cell C. It is therefore aware that cell B is not in any sleep mode but cell C is in some sort of sleep mode (e.g. short, long, etc. the specific sleep type is not important in this example).

Then, cell A, may take the decision to configure cell B as the SCell (in carrier aggregation) or PSCell (in dual connectivity) for the UE with a critical service, while configuring cell C as the SCell or PSCell for the UE without a critical service. In other words, the distributed unit of the first network node (in the example of Figure 7 the gNB-DU servicing cell A) may split the data for a first wireless device running a critical service with a first one of the second cells (e.g. Cell B) that is not in a sleep mode. Conversely, the distributed unit of the first network node (in the example of Figure 7 the gNB-DU servicing cell A) may split the data for a second wireless device running a non-critical service with a second one of the second cells that is in a sleep mode (e.g. Cell C).

In some embodiments the second sleep information comprises sleep patterns of the one or more second cells.

The distributed node of the first network node may then adjust their sleep pattern in relation to their neighbor cells. For example, the distributed node of the first network node may adjust sleep patterns of the one or more first cells such that sleep periods of the one or more first cells do not overlap with sleep periods of the one or more second cells that serve at least partially overlapping geographical areas.

Figure 8 illustrates an example of coordinating sleep patterns.

For example, in figure 8, cells A and B have coordinated their sleep patterns to make sure that when cell A is in sleep, cell B can serve the critical UE and when cell B is in sleep, cell A can serve the critical UE.

In some embodiments, the first sleep information is transmitted as part of a GNB-DU CONFIGURATION UPDATE message, for example over the Fl-AP interface. A suggestion is presented below: (text is copied and modified (underlined) from 3GPP TS 38.473 v.17.1.0 section 9.2.1.7)

“9.2.1.7 GNB-DU CONFIGURATION UPDATE This message is sent by the gNB-DU to transfer updated information associated to an Fl-C interface instance.

NOTE: If Fl-C signalling transport is shared among several Fl-C interface instances, this message may transfer updated information associated to several Fl-C interface instances.

Direction: gNB-DU ® gNB-CU

Each sleep pattern may then be defined in many different ways, e.g., periodic with different durations and periodicities.

In some embodiments the first sleep information or second sleep information may be forwarded between a central unit of a first network node and a central unit of a second network node as part of one of an XN SETUP REQUEST message, an XN SETUP RESPONSE message, an NG-RAN NODE CONFIGURATION UPDATE message, and an NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE message.

One example for XN SETUP REQUEST is demonstrated below. The rest can be done similarly (text is copied and modified (underlined) from 3GPP TS 38.473 v.17.1.0 section 9.2.1.7).

“9.1.3.1 XN SETUP REQUEST

This message is sent by a NG-RAN node to a neighbouring NG-RAN node to transfer application data for an Xn-C interface instance.

Direction: NG-RAN nodei a NG-RAN node2.

ty

In some embodiments, the second sleep information is forwarded by a central unit of a first network node to a distributed unit of the first network node as part of a GNB-CU CONFIGURATION UPDATE message, for example over the Fl-AP interface. One proposal is demonstrated below (copied from 9.2.1.10 from 3GPP TS 38.473 (modifications underlined)):

"9.2.1.10 GNB-CU CONFIGURATION UPDATE

This message is sent by the gNB-CU to transfer updated information associated to an Fl-C interface instance.

Direction: gNB-CU ® gNB-DU

In some embodiments, if the XN-AP interface doesn’t exist between the network nodes, it is possible to send the first or second sleep information via an AMF in the core network (e.g. the 5GC illustrated in Figure 1 may comprise an AMF via which the first or second sleep information may be transmitted between network nodes). The AMF is the entity in the 5G core network that is in charge of mobility management in between the NG-RAN nodes, for example in Uplink RAN Configuration Transfer and Downlink RAN Configuration Transfer. Knowing the neighboring NG-RAN node information may help, e.g. during handover when choosing the idle target NG-RAN node.

It will be appreciated that the first sleep information or second sleep information may also be carried in messages other than those listed here. For example, over XnAP, in the NG-RAN node Configuration Update procedure when there is a modification, or using an Xn Dual connectivity message.

Figure 9 illustrates an example implementation using gNB-CU-CP and gNB-CU-UP In 3GPP Higher Layer Split (HLS), a gNB consists of a gNB-CU Control Plane (gNB-CU- CP), multiple gNB-CU User Planes (gNB-CU-UP)s and multiple gNB-DUs (as shown in Figure 9). Accordingly one gNB-CU may be connected to many gNB-DUs. This gives a holistic view to a gNB-CU-CP over all the cells on all the gNB-DUs that are connected to it. In relation to embodiments described herein, if there is a need for the two serving cells that need to coordinate their sleep patterns with each other, we have two cases:

1) The cells belong to gNB-DUs that are connected to the same gNB-CU-CP. In this case the sleep status and sleep pattern of the cells may be reported over Fl -C to/from the gNB-CU- CP that serves both gNB-DUs.

2) The cells belong to gNB-DUs that are connected to different gNB-CUs. In this case the sleep status and sleep pattern of the cells may be reported from gNB-DUl over Fl-C to gNB- CU-CP 1, and from gNB-CU-CP 1 over XN-AP to gNB-CU-CP2, and from gNB-CU-CP2 over Fl-C to gNB-DU2, and vice versa.

Figure 10 illustrates an example implementation using 0-DU and O-CU-CP

Aspects of embodiments may be included in the Fl-C, XN-Cor NG-C interface in an Open RAN deployment. An example is illustrated in Figure 10. Also, 0-DU may acquire part or all of sleep capabilities of its cells from 0-RU. Moreover, an rApp or xApp in Non-Real Time RAN Intelligent Controller (RIC) and Near-Real Time RIC, respectively, can control the configuration of energy saving functions in either 0-DU and O-CU-CP or both.

Figure 11 shows an example of a communication system 1100 in accordance with some embodiments.

In the example, the communication system 1100 includes a telecommunication network 1102 that includes an access network 1104, such as a radio access network (RAN), and a core network 1106, which includes one or more core network nodes 1108. The access network 1104 includes one or more access network nodes, such as network nodes 1110a and 1110b (one or more of which may be generally referred to as network nodes 1110), or any other similar 3^rd Generation Partnership Project (3 GPP) access node or non-3GPP access point. The network nodes 1110 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 1112a, 1112b, 1112c, and 1112d (one or more of which may be generally referred to as UEs 1112) to the core network 1106 over one or more wireless connections. Example wireless communications over a wireless connection include transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 1100 may include any number of wired or wireless networks, network nodes, UEs, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections. The communication system 1100 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system.

The UEs 1112 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and/or operable to communicate wirelessly with the network nodes 1110 and other communication devices. Similarly, the network nodes 1110 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs 1112 and/or with other network nodes or equipment in the telecommunication network 1102 to enable and/or provide network access, such as wireless network access, and/or to perform other functions, such as administration in the telecommunication network 1102.

In the depicted example, the core network 1106 connects the network nodes 1110 to one or more hosts, such as host 1116. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 1106 includes one more core network nodes (e.g., core network node 1108) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and/or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 1108. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and/or a User Plane Function (UPF).

The host 1116 may be under the ownership or control of a service provider other than an operator or provider of the access network 1104 and/or the telecommunication network 1102, and may be operated by the service provider or on behalf of the service provider. The host 1116 may host a variety of applications to provide one or more services. Examples of such applications include the provision of live and/or pre-recorded audio/video content, data collection services, for example, retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

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

In some examples, the telecommunication network 1102 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 1102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 1102. For example, the telecommunications network 1102 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and/or Massive Machine Type Communication (mMTC)/Massive loT services to yet further UEs.

In some examples, the UEs 1112 are configured to transmit and/or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 1104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 1104. Additionally, a UE may be configured for operating in single- or multi -RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).

In the example illustrated in Figure 11, the hub 1114 communicates with the access network 1104 to facilitate indirect communication between one or more UEs (e.g., UE 1112c and/or 1112d) and network nodes (e.g., network node 1110b). In some examples, the hub 1114 may be a controller, router, a content source and analytics node, or any of the other communication devices described herein regarding UEs. For example, the hub 1114 may be a broadband router enabling access to the core network 1106 for the UEs. As another example, the hub 1114 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 1110, or by executable code, script, process, or other instructions in the hub 1114. As another example, the hub 1114 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 1114 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 1114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 1114 then provides to the UE either directly, after performing local processing, and/or after adding additional local content. In still another example, the hub 1114 acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy loT devices. The hub 1114 may have a constant/persistent or intermittent connection to the network node 1110b. The hub 1114 may also allow for a different communication scheme and/or schedule between the hub 1114 and UEs (e.g., UE 1112c and/or 1112d), and between the hub 1114 and the core network 1106. In other examples, the hub 1114 is connected to the core network 1106 and/or one or more UEs via a wired connection. Moreover, the hub 1114 may be configured to connect to an M2M service provider over the access network 1104 and/or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 1110 while still connected via the hub 1114 via a wired or wireless connection. In some embodiments, the hub 1114 may be a dedicated hub - that is, a hub whose primary function is to route communications to/from the UEs from/to the network node 1110b. In other embodiments, the hub 1114 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 1110b, but which is additionally capable of operating as a communication start and/or end point for certain data channels.

Figure 12 shows a UE 1200 in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless camera, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle-mounted or vehicle embedded/integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3 GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.

A UE may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, a 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).

The UE 1200 includes processing circuitry 1202 that is operatively coupled via a bus 1204 to an input/output interface 1206, a power source 1208, a memory 1210, a communication interface 1212, and/or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 12. 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.

The processing circuitry 1202 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 1210. The processing circuitry 1202 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 1202 may include multiple central processing units (CPUs). The processing circuitry 1202 may be operable to provide, either alone or in conjunction with other UE 1200 components, such as the memory 1210, UE 1200 functionality. In the example, the input/output interface 1206 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and/or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into the UE 1200. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.

In some embodiments, the power source 1208 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used. The power source 1208 may further include power circuitry for delivering power from the power source 1208 itself, and/or an external power source, to the various parts of the UE 1200 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 1208. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 1208 to make the power suitable for the respective components of the UE 1200 to which power is supplied.

The memory 1210 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 1210 includes one or more application programs 1214, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 1216. The memory 1210 may store, for use by the UE 1200, any of a variety of various operating systems or combinations of operating systems. The memory 1210 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and/or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘ SIM card.’ The memory 1210 may allow the UE 1200 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 1210, which may be or comprise a device-readable storage medium.

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

In some embodiments, communication functions of the communication interface 1212 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented in according to one or more communication protocols and/or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol/internet protocol (TCP/IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth. Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 1212, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or controls a robotic arm performing a medical procedure according to the received input.

A UE, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are devices which are or which are embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door/window sensor, a flood/moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an loT device comprises circuitry and/or software in dependence on the intended application of the loT device in addition to other components as described in relation to the UE 1200 shown in Figure 12.

As yet another specific example, in an loT scenario, a UE may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another UE and/or a network node. The UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3 GPP NB-IoT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation.

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

Figure 13 shows a network node 1300 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a UE and/or with other network nodes or equipment, in a telecommunication 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 so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. 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).

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

The network node 1300 includes processing circuitry 1302, a memory 1304, a communication interface 1306, and a power source 1308, and/or any other component, or any combination thereof. The network node 1300 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 the network node 1300 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 NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 1300 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 1304 for different RATs) and some components may be reused (e.g., a same antenna 1310 may be shared by different RATs). The network node 1300 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1300, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z- wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 1300.

The processing circuitry 1302 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, applicationspecific 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 1300 components, such as the memory 1304, network node 1300 functionality. For example, the processing circuitry 1302 may be configured to cause the network node (for example a distributed unit or central unit of the network node) to perform the methods as described with reference to Figures 4 or 5.

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

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

The communication interface 1306 is used in wired or wireless communication of signaling and/or data between a network node, access network, and/or UE. As illustrated, the communication interface 1306 comprises port(s)/terminal(s) 1316 to send and receive data, for example to and from a network over a wired connection. The communication interface 1306 also includes radio front-end circuitry 1318 that may be coupled to, or in certain embodiments a part of, the antenna 1310. Radio front-end circuitry 1318 comprises filters 1320 and amplifiers 1322. The radio front-end circuitry 1318 may be connected to an antenna 1310 and processing circuitry 1302. The radio front-end circuitry may be configured to condition signals communicated between antenna 1310 and processing circuitry 1302. The radio front-end circuitry 1318 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 1318 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1320 and/or amplifiers 1322. The radio signal may then be transmitted via the antenna 1310. Similarly, when receiving data, the antenna 1310 may collect radio signals which are then converted into digital data by the radio front-end circuitry 1318. The digital data may be passed to the processing circuitry 1302. In other embodiments, the communication interface may comprise different components and/or different combinations of components. In certain alternative embodiments, the network node 1300 does not include separate radio front-end circuitry 1318, instead, the processing circuitry 1302 includes radio front-end circuitry and is connected to the antenna 1310. Similarly, in some embodiments, all or some of the RF transceiver circuitry 1312 is part of the communication interface 1306. In still other embodiments, the communication interface 1306 includes one or more ports or terminals 1316, the radio front-end circuitry 1318, and the RF transceiver circuitry 1312, as part of a radio unit (not shown), and the communication interface 1306 communicates with the baseband processing circuitry 1314, which is part of a digital unit (not shown).

The antenna 1310 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. The antenna 1310 may be coupled to the radio front-end circuitry 1318 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In certain embodiments, the antenna 1310 is separate from the network node 1300 and connectable to the network node 1300 through an interface or port.

The antenna 1310, communication interface 1306, and/or the processing circuitry 1302 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by the network node. Any information, data and/or signals may be received from a UE, another network node and/or any other network equipment. Similarly, the antenna 1310, the communication interface 1306, and/or the processing circuitry 1302 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and/or signals may be transmitted to a UE, another network node and/or any other network equipment.

The power source 1308 provides power to the various components of network node 1300 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 1308 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 1300 with power for performing the functionality described herein. For example, the network node 1300 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 1308. As a further example, the power source 1308 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

Embodiments of the network node 1300 may include additional components beyond those shown in Figure 13 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein. For example, the network node 1300 may include user interface equipment to allow input of information into the network node 1300 and to allow output of information from the network node 1300. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 1300. Figure 14 is a block diagram of a host 1400, which may be an embodiment of the host 1116 of Figure 11, in accordance with various aspects described herein. As used herein, the host 1400 may be or comprise various combinations hardware and/or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm. The host 1400 may provide one or more services to one or more UEs.

The host 1400 includes processing circuitry 1402 that is operatively coupled via a bus 1404 to an input/output interface 1406, a network interface 1408, a power source 1410, and a memory 1412. Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Figures 12 and 13, such that the descriptions thereof are generally applicable to the corresponding components of host 1400.

The memory 1412 may include one or more computer programs including one or more host application programs 1414 and data 1416, which may include user data, e.g., data generated by a UE for the host 1400 or data generated by the host 1400 for a UE. Embodiments of the host 1400 may utilize only a subset or all of the components shown. The host application programs 1414 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, heads-up display systems). The host application programs 1414 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network. Accordingly, the host 1400 may select and/or indicate a different host for over-the-top services for a UE. The host application programs 1414 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc. Figure 15 is a block diagram illustrating a virtualization environment 1500 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 any device described herein, 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. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 1500 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized.

Applications 1502 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein.

Hardware 1504 includes processing circuitry, memory that stores software and/or instructions executable by hardware processing circuitry, and/or other hardware devices as described herein, such as a network interface, input/output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 1506 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 1508a and 1508b (one or more of which may be generally referred to as VMs 1508), and/or perform any of the functions, features and/or benefits described in relation with some embodiments described herein. The virtualization layer 1506 may present a virtual operating platform that appears like networking hardware to the VMs 1508.

The VMs 1508 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 1506. Different embodiments of the instance of a virtual appliance 1502 may be implemented on one or more of VMs 1508, and the implementations may be made in different ways. 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, a VM 1508 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 the VMs 1508, and that part of hardware 1504 that executes that VM, be it hardware dedicated to that VM and/or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 1508 on top of the hardware 1504 and corresponds to the application 1502.

Hardware 1504 may be implemented in a standalone network node with generic or specific components. Hardware 1504 may implement some functions via virtualization. Alternatively, hardware 1504 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 1510, which, among others, oversees lifecycle management of applications 1502. In some embodiments, hardware 1504 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes 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 provided with the use of a control system 1512 which may alternatively be used for communication between hardware nodes and radio units.

Figure 16 shows a communication diagram of a host 1602 communicating via a network node 1604 with a UE 1606 over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of the UE (such as a UE 1112a of Figure 11 and/or UE 1200 of Figure 12), network node (such as network node 1110a of Figure 11 and/or network node 1300 of Figure 13), and host (such as host 1116 of Figure 11 and/or host 1400 of Figure 14) discussed in the preceding paragraphs will now be described with reference to Figure 16.

Like host 1400, embodiments of host 1602 include hardware, such as a communication interface, processing circuitry, and memory. The host 1602 also includes software, which is stored in or accessible by the host 1602 and executable by the processing circuitry. The software includes a host application that may be operable to provide a service to a remote user, such as the UE 1606 connecting via an over-the-top (OTT) connection 1650 extending between the UE 1606 and host 1602. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection 1650. The network node 1604 includes hardware enabling it to communicate with the host 1602 and UE 1606. The connection 1660 may be direct or pass through a core network (like core network 1106 of Figure 11) and/or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, an intermediate network may be a backbone network or the Internet.

The UE 1606 includes hardware and software, which is stored in or accessible by UE 1606 and executable by the UE’s processing circuitry. The software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE 1606 with the support of the host 1602. In the host 1602, an executing host application may communicate with the executing client application via the OTT connection 1650 terminating at the UE 1606 and host 1602. In providing the service to the user, the UE's client application may receive request data from the host's host application and provide user data in response to the request data. The OTT connection 1650 may transfer both the request data and the user data. The UE's client application may interact with the user to generate the user data that it provides to the host application through the OTT connection 1650.

The OTT connection 1650 may extend via a connection 1660 between the host 1602 and the network node 1604 and via a wireless connection 1670 between the network node 1604 and the UE 1606 to provide the connection between the host 1602 and the UE 1606. The connection 1660 and wireless connection 1670, over which the OTT connection 1650 may be provided, have been drawn abstractly to illustrate the communication between the host 1602 and the UE 1606 via the network node 1604, without explicit reference to any intermediary devices and the precise routing of messages via these devices.

As an example of transmitting data via the OTT connection 1650, in step 1608, the host 1602 provides user data, which may be performed by executing a host application. In some embodiments, the user data is associated with a particular human user interacting with the UE 1606. In other embodiments, the user data is associated with a UE 1606 that shares data with the host 1602 without explicit human interaction. In step 1610, the host 1602 initiates a transmission carrying the user data towards the UE 1606. The host 1602 may initiate the transmission responsive to a request transmitted by the UE 1606. The request may be caused by human interaction with the UE 1606 or by operation of the client application executing on the UE 1606. The transmission may pass via the network node 1604, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 1612, the network node 1604 transmits to the UE 1606 the user data that was carried in the transmission that the host 1602 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 1614, the UE 1606 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 1606 associated with the host application executed by the host 1602.

In some examples, the UE 1606 executes a client application which provides user data to the host 1602. The user data may be provided in reaction or response to the data received from the host 1602. Accordingly, in step 1616, the UE 1606 may provide user data, which may be performed by executing the client application. In providing the user data, the client application may further consider user input received from the user via an input/output interface of the UE 1606. Regardless of the specific manner in which the user data was provided, the UE 1606 initiates, in step 1618, transmission of the user data towards the host 1602 via the network node 1604. In step 1620, in accordance with the teachings of the embodiments described throughout this disclosure, the network node 1604 receives user data from the UE 1606 and initiates transmission of the received user data towards the host 1602. In step 1622, the host 1602 receives the user data carried in the transmission initiated by the UE 1606.

One or more of the various embodiments improve the performance of OTT services provided to the UE 1606 using the OTT connection 1650, in which the wireless connection 1670 forms the last segment. More precisely, the teachings of these embodiments may improve the, for example, latency or data rate and thereby provide benefits such as for example, reduced user waiting time.

In an example scenario, factory status information may be collected and analyzed by the host 1602. As another example, the host 1602 may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, the host 1602 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, the host 1602 may store surveillance video uploaded by a UE. As another example, the host 1602 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs. As other examples, the host 1602 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing and/or transmitting data.

In some examples, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection 1650 between the host 1602 and UE 1606, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of the host 1602 and/or UE 1606. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 1650 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 1650 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node 1604. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by the host 1602. The measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 1650 while monitoring propagation times, errors, etc.

Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and/or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware. In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device- readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer-readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and/or by end users and a wireless network generally.

EMBODIMENTS

Group B Embodiments

1. A method performed by a distributed unit of a first network node, the method comprising: transmitting, to a central unit of the first network node, first sleep information related to one or more first cells serviced by the distributed unit of the first network node.

2. The method of embodiment 1, wherein the first sleep information comprises sleep statuses of the one or more first cells.

3. The method of embodiment 1 or 2, wherein the first sleep information comprises sleep patterns of the one or more first cells.

4. The method of any one of embodiments 1 to 3 wherein the first sleep information is transmitted over an Fl-AP interface between the distributed unit and the central unit.

5. The method of embodiment 4 wherein the first sleep information is transmitted as part of a GNB-DU CONFIGURATION UPDATE message.

6. The method of any one of embodiments 1 to 5 further comprising receiving an indication of second sleep information relating to one or more second cells serviced by one or more neighboring distributed units.

7. The method of embodiment 6 wherein the second sleep information is received over an Fl-AP interface between the distributed unit and the central unit.

8. The method of embodiment 7 wherein the second sleep information is received as part of a GNB-CU CONFIGURATION UPDATE message.

9. The method of any one of embodiments 6 to 8 wherein the second sleep information comprises sleep statuses of the one or more second cells.

10. The method of embodiment 9 further comprising executing data splitting with the one or more second cells in relation to carrier aggregation and/or dual connectivity for one or more wireless devices serviced by the one or more first cells based on the sleep statuses of the one or more second cells.

11. The method of embodiment 10 wherein the step of executing comprises: splitting the data for a first wireless device running a critical service with a first one of the second cells that is not in a sleep mode.

12. The method of embodiment 10 or 11 wherein the step of executing comprises: splitting the data for a second wireless device running a non-critical service with a second one of the second cells that is in a sleep mode. The method of any one of embodiments 6 to 12 wherein the second sleep information comprises sleep patterns of the one or more second cells. The method of embodiment 13 further comprising: adjusting sleep patterns of the one or more first cells such that sleep periods of the one or more first cells do not overlap with sleep periods of the one or more second cells that serve at least partially overlapping geographical areas. A method performed by a central unit of a first network node, the method comprising: receiving, from a distributed unit of the first network node, first sleep information related to one or more first cells serviced by the distributed unit of the first network node. The method of embodiment 15 further comprising forwarding the first sleep information to central units of one or more second network nodes. The method of embodiment 16 wherein the first sleep information is forwarded over a XN-AP interface. The method of embodiment 16 or 17 wherein the first sleep information is forwarded as part of one of: an XN SETUP REQUEST message, an XN SETUP RESPONSE message, an NG-RAN NODE CONFIGURATION UPDATE message, and an NG- RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE message. The method of any one of embodiments 15 to 18 wherein the first sleep information is received over an Fl-AP interface between the central unit of the first network node and the distributed unit of the first network node. The method of embodiment 19 wherein the first sleep information is received as part of a GNB-DU CONFIGURATION UPDATE message. The method of any one of embodiments 15 to 20 further comprising receiving, from a central unit of a second network node, second sleep information related to one or more second cells serviced by the second network node. The method of embodiment 21 wherein the second sleep information is received over an XN-AP interface between the central unit of the first network node and the central unit of the second network node. The method of embodiment 22 wherein the second sleep information is received as part of one of: using an XN SETUP REQUEST message, an XN SETUP RESPONSE message, an NG-RAN NODE CONFIGURATION UPDATE message, and an NG- RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE message.

24. The method of any one of embodiments 21 to 23 further comprising forwarding the second sleep information to one or more distributed units of the first network node.

25. The method of embodiment 24 further comprising forwarding the second sleep information over an Fl-AP interface between the central unit of the first network node and the one or more distributed units of the first network node.

26. The method of embodiment 25 wherein the second sleep information is forwarded as part of a GNB-CU CONFIGURATION UPDATE message.

27. The method of any of the previous embodiments, further comprising: obtaining user data; and forwarding the user data to a host or a user equipment.

Group C Embodiments

28. A network node, the network node comprising: processing circuitry configured to cause the network node to perform any of the steps of any of the Group B embodiments; power supply circuitry configured to supply power to the processing circuitry.

29. A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a network node in a cellular network for transmission to a user equipment (UE), the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B embodiments to transmit the user data from the host to the UE.

30. The host of the previous embodiment, wherein: the processing circuitry of the host is configured to execute a host application that provides the user data; and the UE comprises processing circuitry configured to execute a client application associated with the host application to receive the transmission of user data from the host. 31. A method implemented in a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: providing user data for the UE; and initiating a transmission carrying the user data to the UE via a cellular network comprising the network node, wherein the network node performs any of the operations of any of the Group B embodiments to transmit the user data from the host to the UE.

32. The method of the previous embodiment, further comprising, at the network node, transmitting the user data provided by the host for the UE.

33. The method of any of the previous 2 embodiments, wherein the user data is provided at the host by executing a host application that interacts with a client application executing on the UE, the client application being associated with the host application.

34. A communication system configured to provide an over-the-top service, the communication system comprising: a host comprising: processing circuitry configured to provide user data for a user equipment (UE), the user data being associated with the over-the-top service; and a network interface configured to initiate transmission of the user data toward a cellular network node for transmission to the UE, the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B embodiments to transmit the user data from the host to the UE.

35. The communication system of the previous embodiment, further comprising: the network node; and/or the user equipment.

36. A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to initiate receipt of user data; and a network interface configured to receive the user data from a network node in a cellular network, the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B embodiments to receive the user data from a user equipment (UE) for the host.

37. The host of the previous embodiment, wherein: the processing circuitry of the host is configured to execute a host application, thereby providing the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.

38. The host of the any of the previous 2 embodiments, wherein the initiating receipt of the user data comprises requesting the user data.

39. A method implemented by a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: at the host, initiating receipt of user data from the UE, the user data originating from a transmission which the network node has received from the UE, wherein the network node performs any of the steps of any of the Group B embodiments to receive the user data from the UE for the host.

40. The method of the previous embodiment, further comprising at the network node, transmitting the received user data to the host.

REFERENCES

1 . 3GPP TS 38.423 v17.1 .0 XN Application Protocol

2. 3GPP TS 38.473 v17.1 .0 F1 Application Protocol

3. 3GPP TS 38,413 v17.1.0 NG Application Protocol ABBREVIATIONS

At least some of the following abbreviations may be used in this disclosure. If there is an inconsistency between abbreviations, preference should be given to how it is used above. If listed multiple times below, the first listing should be preferred over any subsequent listing(s).

NES Network Energy Saving

UE User Equipment (Wireless device in 3GPP systems)

NR New Radio

LTE Long Term Evolution gNB Base station in NR eNB Base station in LTE

RRC Radio Resource Control gNB-CU gNB Control Unit gNB-DU gNB Distributed Unit lx RTT CDMA2000 lx Radio Transmission Technology

3 GPP 3rd Generation Partnership Project

5G 5th Generation

6G 6th Generation

ABS Almost Blank Subframe

ARQ Automatic Repeat Request

AWGN Additive White Gaussian Noise

BCCH Broadcast Control Channel

BCH Broadcast Channel

CA Carrier Aggregation

CC Carrier Component

CCCH SDU Common Control Channel SDU

CDMA Code Division Multiplexing Access

CGI Cell Global Identifier

CIR Channel Impulse Response

CP Cyclic Prefix

CPICH Common Pilot Channel CPICH Ec/No CPICH Received energy per chip divided by the power density in the band

CQI Channel Quality information

C-RNTI Cell RNTI

CSI Channel State Information

DCCH Dedicated Control Channel

DL Downlink

DM Demodulation

DMRS Demodulation Reference Signal

DRX Discontinuous Reception

DTX Discontinuous Transmission

DTCH Dedicated Traffic Channel

DUT Device Under Test

E-CID Enhanced Cell-ID (positioning method) eMBMS evolved Multimedia Broadcast Multicast Services

E-SMLC Evolved-Serving Mobile Location Centre

ECGI Evolved CGI eNB E-UTRAN NodeB ePDCCH Enhanced Physical Downlink Control Channel

E-SMLC Evolved Serving Mobile Location Center

E-UTRA Evolved UTRA

E-UTRAN Evolved UTRAN

FDD Frequency Division Duplex

FFS For Further Study gNB Base station in NR

GNSS Global Navigation Satellite System

HARQ Hybrid Automatic Repeat Request

HO Handover

HSPA High Speed Packet Access

HRPD High Rate Packet Data

LOS Line of Sight

LPP LTE Positioning Protocol

LTE Long-Term Evolution

MAC Medium Access Control

MAC Message Authentication Code MBSFN Multimedia Broadcast multicast service Single Frequency Network

MBSFN ABS MBSFN Almost Blank Subframe

MDT Minimization of Drive Tests

MIB Master Information Block

MME Mobility Management Entity

MSC Mobile Switching Center

NPDCCH Narrowband Physical Downlink Control Channel

NR New Radio

OCNG OFDMA Channel Noise Generator

OFDM Orthogonal Frequency Division Multiplexing

OFDMA Orthogonal Frequency Division Multiple Access

OSS Operations Support System

OTDOA Observed Time Difference of Arrival

O&M Operation and Maintenance

PBCH Physical Broadcast Channel

P-CCPCH Primary Common Control Physical Channel

PCell Primary Cell

PCFICH Physical Control Format Indicator Channel

PDCCH Physical Downlink Control Channel

PDCP Packet Data Convergence Protocol

PDP Profile Delay Profile

PDSCH Physical Downlink Shared Channel

PGW Packet Gateway

PHICH Physical Hybrid-ARQ Indicator Channel

PLMN Public Land Mobile Network

PMI Precoder Matrix Indicator

PRACH Physical Random Access Channel

PRS Positioning Reference Signal

PSS Primary Synchronization Signal

PUCCH Physical Uplink Control Channel

PUSCH Physical Uplink Shared Channel

RACH Random Access Channel

QAM Quadrature Amplitude Modulation

RAN Radio Access Network RAT Radio Access Technology

RLC Radio Link Control

RLM Radio Link Management

RNC Radio Network Controller

RNTI Radio Network Temporary Identifier

RRC Radio Resource Control

RRM Radio Resource Management

RS Reference Signal

RSCP Received Signal Code Power

RSRP Reference Symbol Received Power OR Reference Signal Received Power

RSRQ Reference Signal Received Quality OR Reference Symbol Received Quality

RS SI Received Signal Strength Indicator

RSTD Reference Signal Time Difference

SCH Synchronization Channel

SCell Secondary Cell

SDAP Service Data Adaptation Protocol

SDU Service Data Unit

SFN System Frame Number

SGW Serving Gateway

SI System Information

SIB System Information Block

SNR Signal to Noise Ratio

SON Self Optimized Network

SS Synchronization Signal

SSS Secondary Synchronization Signal

TDD Time Division Duplex

TDOA Time Difference of Arrival

TOA Time of Arrival

TSS Tertiary Synchronization Signal

TTI Transmission Time Interval

UE User Equipment

UL Uplink

USIM Universal Subscriber Identity Module

UTDOA Uplink Time Difference of Arrival WCDMA Wide CDMA

WLAN Wide Local Area Network

Claims

2. The method of claim 1, wherein the first sleep information comprises sleep statuses of the one or more first cells.

3. The method of claim 1 or 2, wherein the first sleep information comprises sleep patterns of the one or more first cells.

4. The method of any one of claims 1 to 3 wherein the first sleep information is transmitted over an Fl-AP interface between the distributed unit and the central unit.

5. The method of claim 4 wherein the first sleep information is transmitted as part of a GNB-DU CONFIGURATION UPDATE message.

6. The method of any one of claims 1 to 5 further comprising receiving an indication of second sleep information relating to one or more second cells serviced by one or more neighboring distributed units.

7. The method of claim 6 wherein the second sleep information is received over an Fl- AP interface between the distributed unit and the central unit.

8. The method of claim 7 wherein the second sleep information is received as part of a GNB-CU CONFIGURATION UPDATE message.

9. The method of any one of claims 6 to 8 wherein the second sleep information comprises sleep statuses of the one or more second cells. The method of claim 9 further comprising executing data splitting with the one or more second cells in relation to carrier aggregation and/or dual connectivity for one or more wireless devices serviced by the one or more first cells based on the sleep statuses of the one or more second cells. The method of claim 10 wherein the step of executing comprises: splitting the data for a first wireless device running a critical service with a first one of the second cells that is not in a sleep mode. The method of claim 10 or 11 wherein the step of executing comprises: splitting the data for a second wireless device running a non-critical service with a second one of the second cells that is in a sleep mode. The method of any one of claims 6 to 12 wherein the second sleep information comprises sleep patterns of the one or more second cells. The method of claim 13 further comprising: adjusting sleep patterns of the one or more first cells such that sleep periods of the one or more first cells do not overlap with sleep periods of the one or more second cells that serve at least partially overlapping geographical areas. A method performed by a central unit of a first network node, the method comprising: receiving, from a distributed unit of the first network node, first sleep information related to one or more first cells serviced by the distributed unit of the first network node. The method of claim 15 further comprising forwarding the first sleep information to central units of one or more second network nodes. The method of claim 16 wherein the first sleep information is forwarded over a XN- AP interface. The method of claim 16 or 17 wherein the first sleep information is forwarded as part of one of: an XN SETUP REQUEST message, an XN SETUP RESPONSE message, an NG-RAN NODE CONFIGURATION UPDATE message, and an NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE message. The method of any one of claims 15 to 18 wherein the first sleep information is received over an Fl-AP interface between the central unit of the first network node and the distributed unit of the first network node. The method of claim 19 wherein the first sleep information is received as part of a GNB-DU CONFIGURATION UPDATE message. The method of any one of claims 15 to 20 further comprising receiving, from a central unit of a second network node, second sleep information related to one or more second cells serviced by the second network node. The method of claim 21 wherein the second sleep information is received over an XN-AP interface between the central unit of the first network node and the central unit of the second network node. The method of claim 22 wherein the second sleep information is received as part of one of: using an XN SETUP REQUEST message, an XN SETUP RESPONSE message, an NG-RAN NODE CONFIGURATION UPDATE message, and an NG- RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE message. The method of any one of claims 21 to 23 further comprising forwarding the second sleep information to one or more distributed units of the first network node. The method of claim 24 further comprising forwarding the second sleep information over an Fl-AP interface between the central unit of the first network node and the one or more distributed units of the first network node. The method of claim 25 wherein the second sleep information is forwarded as part of a GNB-CU CONFIGURATION UPDATE message. A distributed unit of a first network node, wherein the distributed unit comprises processing circuitry configured to cause the first network node to: transmit, to a central unit of the first network node, first sleep information related to one or more first cells serviced by the distributed unit of the first network node. The distributed unit of the first network node as claimed in claim 27 wherein the processing circuitry is further configured to cause the distributed unit to perform the method as claimed in any one of claims 2 to 14. A central unit of a first network node, wherein the central unit comprises processing circuitry configured to cause the central unit to: receive, from a distributed unit of the first network node, first sleep information related to one or more first cells serviced by the distributed unit of the first network node. The central unit as claimed in claim 29 wherein the processing circuitry is further configured to cause the distributed unit to perform the method as claimed in any one of claims 16 to 26. A computer program comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out a method according to any of claims 1 to 26. A computer program product comprising non transitory computer readable media having stored thereon a computer program according to claim 31.