WO2024035314A1

WO2024035314A1 - Signaling of discontinuous transmission and/or reception information

Info

Publication number: WO2024035314A1
Application number: PCT/SE2023/050796
Authority: WO
Inventors: Philipp BRUHN; Nianshan SHI; Sina MALEKI
Original assignee: Telefonaktiebolaget Lm Ericsson (Publ)
Priority date: 2022-08-08
Filing date: 2023-08-08
Publication date: 2024-02-15

Abstract

A method (1600) by a first network node (102, 302, 1200) for signaling Discontinuous Transmission and/or Reception, DTRX, information (120, 320) is provided. The method includes transmitting (1602), by the first network node to a second network node (104, 304, 1200), first DTRX information associated with at least one of a DTRX pattern and/or cycle that is employed and a DTRX pattern and/or cycle that is to be employed at or by the first network node.

Description

SIGNALING OF DISCONTINUOUS TRANSMISSION AND/OR RECEPTION

INFORMATION

TECHNICAL FIELD

The present disclosure relates, in general, to wireless communications and, more particularly, systems and methods for signaling of Discontinuous Transmission and/or Reception DTRX information.

BACKGROUND

FIGURE 1 illustrates the current overall architecture of 5^th Generation (5G) Radio Access Network (RAN), which is also referred to as Next Generation-RAN (NG-RAN) and is described in 3GPP TS 38.401 v. 17.0.0.

The NG-RAN consists of a set of gNodeBs (gNBs) connected to the 5G Core (5GC) through the Next Generation (NG) interface.

A gNB can support Frequency Division Duplex (FDD) mode, Time Division Duplex (TDD) mode, or dual mode operation. gNBs can be interconnected through the Xn interface.

A gNB may consist of a gNB-Central Unit (gNB-CU) and one or more gNB-Distributed Unit (gNB-DU(s). A gNB-CU and a gNB-DU are connected via the Fl interface. One gNB-DU is connected to only one gNB-CU. NG, Xn and Fl are logical interfaces.

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

As specified in 3GPP TS 38.300, NG-RAN could also consist of a set of Next Generation eNodeBs (ng-eNBs). An ng-eNB may consist of an ng-eNB Central Unit (ng-eNB-CU) and one or more ng-eNB-Distributed Units (ng-eNB-DUs). An ng-eNB-CU and an ng-eNB-DU is connected via the W1 interface. The general principles described herein as applying to an gNB may also apply to an ng-eNB and the W1 interface, unless explicitly stated otherwise.

FIGURE 2 illustrates the overall architecture for separation of gNB-CU-Control Plane (gNB-CU-CP) and gNB-CU-User Plane (gNB-CU-UP) as disclosed in 3GPP TS 38.401 v.17.0.0. The gNB-CU-CP and the gNB-CU-UP(s) are connected via El interface(s). The gNB-CU-CP and the gNB-DU are connected via the Fl-C interface. The gNB-CU-UP(s) and gNB-DU are connected via Fl-U interface(s).

NG-RAN node Configuration Update Procedure

Clause 8.4.2 of 3GPP TS 38.423 describes the NG-RAN node Configuration Update procedure, which allows an NG-RAN node to transmit to a neighboring NG-RAN node an update of configuration information that is essential for the two NG-RAN nodes to interoperate correctly over the Xn-C interface.

The NG-RAN node Configuration Update procedure uses non-User Equipment-associated signaling.

FIGURE 3 illustrates a successful operation of the NG-RAN node Configuration Update procedure. As illustrated, the first NG-RAN node initiates the procedure by sending a NG-RAN NODE CONFIGURATION UPDATE message to a second NG-RAN node. The NG-RAN NODE CONFIGURATION UPDATE message may comprise a list of served New Radio (NR) cells to update, or a list of served E-UTRA cells to update, or both, which may comprise a Served Cells NR To Modify IE and Served Cells E-UTRA To Modify IE, respectively.

If the Deactivation Indication IE is comprised in the Served Cells NR To Modify IE, it indicates that the corresponding cell was switched off for NW energy saving. Analogously, if the Deactivation Indication IE is comprised in the Served Cells E-UTRA To Modify IE, it indicates that the corresponding cell was switched off for NW energy saving.

Upon receipt of this message, the second NG-RAN node should update the configuration data associated to the first NG-RAN node that it has stored locally and send a NG-RAN NODE CONFIGURATION ACKNOWLEDGE message to the first NG-RAN node.

In contrast to FIGURE 3, FIGURE 4 illustrates an unsuccessful operation of the NG-RAN node Configuration Update procedure. Specifically, similar to FIGURE 3, the first NG-RAN node initiates the procedure by sending a NG-RAN NODE CONFIGURATION UPDATE message to a second NG-RAN node. If the second NG-RAN node cannot accept the update it should respond with a NG-RAN NODE CONFIGURATION UPDATE FAILURE message and with an appropriate cause value.

For further details, refer to 3GPP TS 38.423. CN - RAN nodes Setup, Configuration Update and Information Transfer Procedures

NG Setup procedure is used to exchange application level data needed for the NG-RAN node and the Application Management Function (AMF) to correctly interoperate on the NG-C interface. FIGURE 5 illustrates the NG Setup procedure, which includes the NG-RAN node sending a NG SETUP REQUEST to the AMF. Thereafter, the AMF sends a NG SETUP RESPONSE message to the NG-RAN node.

After the NG interface is setup, there are two configuration update procedures to update application level configuration data needed for the NG-RAN node and the AMF to interoperate correctly on the NG-C interface. One procedure is initiated by NG-RAN node, and the other procedure is initiated by AMF.

FIGURE 6 illustrates the configuration update procedure initiated by the NG-RAN node. As depicted, the NG-RAN node sends a RAN CONFIGURATION UPDATE message to the AMF, and then receives a RAN CONFIGURATION UPDATE ACKNOWLEDGE message from the AMF.

FIGURE 7 illustrates the configuration update procedure initiated by the AMF. As depicted, the AMF sends an AMF CONFIGURATION UPDATE message to the NG-RAN node, and then receives an AMF CONFIGURATION UPDATE ACKNOWLEDGE message from the NG-RAN node.

FIGURE 8 illustrates the Uplink (UL) RAN Configuration Transfer procedure, which is for transferring RAN configuration information from an NG-RAN node to the AMF. FIGURE 9 illustrates the Downlink (DL) RAN Configuration Transfer procedure, which is for the AMF to further transfer the information to another NG-RAN node. The AMF does not interpret the transferred RAN configuration information.

Network Energy Consumption/Saving

Energy consumption is a big challenge of the 5G system today. Most of the energy consumption comes from Radio Units (RUs) of the RANs. The network energy consumption is said to be less for NR compared to Long Term Evolution (LTE) because of the lean NR design. In the current implementation, however, NR will most likely consume more energy compared to LTE due to, for example, denser network deployment, larger number of antennas, larger bandwidths, more carriers, and other new, performance-enhancing features that cause additional energy consumption. Moreover, today’s RAN is typically deployed in a layered fashion. The RAN capabilities are enhanced by adding carriers or spectrum to macro sites and deploying micro and indoor sites to complement the macro layers to boost indoor coverage, absorb hotspot traffic, and improve user experience, especially during peak traffic hours. These RAN deployments will, however, lead to excess network capacity at times of low traffic demand, which will thus result in unnecessarily high energy consumption if not counteracted with suitable energy saving techniques.

Cell deactivation is a known/conventional energy saving technique in the spatial domain that takes advantage of the opportunity to offload User Equipments (UEs) and, thus, the associated traffic in a layered RAN structure with overlapping coverage areas to reduce the RAN energy consumption. However, cell deactivation comes at the price of long cell reactivation delays in case the additional network capacity is needed to provide a certain user experience or opportune for other reasons, which significantly limits the opportunities or amount of time for employing this energy saving technique.

For the above reasons, more granular energy saving techniques in time, frequency, spatial, and power domains are foreseen. An example for UE energy saving techniques in the time domain is Discontinuous Reception (DRX). Like LTE, NR comprises techniques supporting DRX for the UE to reduce the UE energy consumption. DRX can be used in both Radio Resource Control (RRC) Connected mode (C-DRX) and RRC Idle/Inactive mode (DRX). It resembles an agreement between the network and the UE such that, regardless of DL traffic, the network will only attempt to contact the UE during on-times of the configured DRX cycle/pattem. Thus, the UE must monitor/ decode the DL channels only as configured and can sleep, i.e., be in a low power/energy state, during off-times. In case of UL traffic, however, the UE may initiate transmission regardless of the DRX configuration. Simply put, the gNB must be prepared to receive UL traffic at any time.

DRX or Discontinuous Transmission and/or Reception (DTRX) for the network is a promising approach enabling the network to introduce certain off-times in which transmission and/or reception is suspended/interrupted at the network node. During DRX or DTRX, a Radio Unit (RU), or at least a part/element/component thereof, is put in a low power/energy state. In other words, DTRX enables the network to operate on a certain duty cycle by which the available network capacity is scaled accordingly (up or down). In such a way, the available network capacity can dynamically be adjusted to the required network capacity, always as per current traffic demand, but without having to offload UEs to neighboring cells with overlapping coverage areas. For example, UEs can stay connected to a cell employing DTRX, resulting in considerably smaller transition times and lower signaling overhead between NG-RAN nodes on the Xn-C interface. There currently exist certain challenge(s), however. For example, even though DTRX for the network is a promising, flexible method for network energy saving, NR does not include the necessary techniques to truly support it. There are several problems with the current NR technology manifesting a lack of support for network-side DTRX or resulting in inefficient and error-prone use of network-side DTRX. For example, one problem with the existing technology is that RAN nodes are not aware of the DTRX cycles/pattems employed at other (neighboring) RAN nodes. This may lead to the following problems:

• an NG-RAN node may decide the power/energy saving strategies alone, i.e., on its own, without fully utilizing or involving/relying on the neighboring NG-RAN nodes;

• an NG-RAN node may initiate the connectivity to the neighboring NG-RAN nodes which may interrupt their power/energy saving strategies;

• neighboring cells of neighboring NG-RAN nodes may be OFF and ON at the same or similar time to serve the connected UEs causing an interference peak/burst thereby negatively effecting one or more Quality of Service (QoS) and Quality of Experience (QoE) metrics; and

• the UEs which are supposed to perform neighbor cell/gNB measurements may not be aware of the DTRX of the neighboring cell/gNB, and this can potentially impact the Radio Resource Management (RRM) measurements performed by the UEs covered by neighboring cells/gNBs, particularly if the DTRX involves not transmitting sync reference signals such as Synchronization Signal Blocks (SSBs) during specific time periods, e.g., off time of DTRX.

Another problem with the existing technology is that RAN nodes have no option of coordinating the DTRX cycles/pattems employed at the RAN nodes. This may lead to the following problems:

• there is no method enabling NG-RAN nodes to intentionally align or offset/misalign the employed DTRX to achieve joint gains in terms of both increased energy saving and improved interference management in the time domain; and

• all the RAN nodes may be OFF at the same time, which can impact UEs that are in process of performing serving cell or neighbor cell measurements, or plan to start a handover and, thus, may be interrupted in their service or lose connectivity. Another problem with the existing technology is that the Core Network (CN) is not aware of the RAN nodes DTRX policy. This may lead to the following problems:

• the CN may page the UE in RRC Idle or RRC Inactive towards the RAN nodes at its “OFF” period, which may result in failed paging; and

• the CN may request configurations that lead to the NG-RAN node interrupting its energy saving policy.

SUMMARY

Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. For example, methods and systems are provided for enabling network nodes (e.g., RAN nodes such as gNB, gNB-CU, or gNB-DU, or CN nodes, or functions hosted therein, such as AMF) to exchange information associated to at least a DTRX pattern employed, or to be employed, at one or more network nodes. The methods and systems disclosed herein further enable network nodes to negotiate or coordinate information associated to at least a DTRX pattern employed, or to be employed, at one or more network nodes.

According to certain embodiments, a method by a first network node for signaling Discontinuous Transmission and/or Reception (DTRX) information includes transmitting to a second network node, first DTRX information associated with at least one of a DTRX pattem/cycle, i.e. DTRX pattern or cycle, that is employed and a DTRX pattem/cycle that is to be employed at or by the first network node.

According to certain embodiments, a first network node for signaling DTRX information includes processing circuitry adapted to transmit, to a second network node, first DTRX information associated with at least one of a DTRX pattem/cycle that is employed and a DTRX pattem/cycle that is to be employed at or by the first network node.

According to certain embodiments, a method by a second network node for signaling DTRX information includes receiving, from a first network node, first DTRX information associated with at least one of a DTRX pattem/cycle that is employed and a DTRX pattem/cycle that is to be employed at or by the first network node.

According to certain embodiments, a second network node for signaling DTRX information includes processing circuitry adapted to receive, from a first network node, first DTRX information associated with at least one of a DTRX pattem/cycle that is employed and a DTRX pattem/cycle that is to be employed at or by the first network node Certain embodiments may provide one or more of the following technical advantage(s). For example, certain embodiments may provide a technical advantage of enabling RAN nodes to coordinate/negotiate the employed DTRX cycles/pattems to achieve joint gains in terms of enhanced energy saving and improved interference management in the time domain, e.g., by intentionally offsetting/misaligning the employed DTRX cycles/pattems, which provides additional energy saving gains compare to a fractional frequency reuse-based interference management or coordination.

As another example, certain embodiments may provide a technical advantage of enabling the DTRX among neighboring RAN nodes (e.g., gNBs) to be well coordinated. Thus, the UEs under the coverage of the RAN nodes may not be impacted harmfully by potential misalignments of DTRX among the neighboring RAN nodes particularly when it comes to RRM measurements and handovers.

As yet another example, certain embodiments may provide a technical advantage of reduced network signaling (load), efficient information exchange, and low signaling latency for Network Energy Saving (NES) groups. Certain embodiments may also achieve NES strategy coordination with less signaling to cover larger network deployment area.

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

BRIEF DESCRIPTION OF THE DRAWINGS

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

FIGURE 1 illustrates the current overall architecture of 5G RAN;

FIGURE 2 illustrates the overall architecture for separation of gNB-CU-CP and gNB-CU- UP;

FIGURE 3 illustrates a successful operation of the NG-RAN node Configuration Update procedure;

FIGURE 4 illustrates an unsuccessful operation of the NG-RAN node Configuration Update procedure;

FIGURE 5 illustrates the NG Setup procedure;

FIGURE 6 illustrates the configuration update procedure initiated by the NG-RAN node;

FIGURE 7 illustrates the configuration update procedure initiated by the AMF; FIGURE 8 illustrates the UL RAN Configuration Transfer procedure;

FIGURE 9 illustrates the DL RAN Configuration Transfer procedure;

FIGURE 10 illustrates a flow chart and signaling diagram for the exchange, or negotiation, or coordination of information associated to at least a DTRX pattern/ cycle between network nodes, according to certain embodiments;

FIGURE 11 illustrates aNES group leader node, according to certain embodiments;

FIGURE 12 illustrates a flow chart wherein a second network node acts as a group leader coordinating DTRX information to be employed at two or more other network nodes, according to certain embodiments;

FIGURE 13 illustrates another example flow chart depicting signaling between the NES group leader node and its NES surrounding nodes, according to certain embodiments;

FIGURE 14 illustrates an example flow chart depicting signaling between NES group leader nodes for the exchange of information for groups, according to certain embodiments;

FIGURE 15 illustrates an example for the exchange or negotiation of DTRX information between a gNB-DU of an NG-RAN node and a gNB-CU (or a gNB-CU-CP) of the same NG-RAN node, according to certain embodiments;

FIGURE 16 illustrates an example for the exchange or negotiation of DTRX information between different DUs of a NG-RAN node with split architecture, according to certain embodiments;

FIGURE 17 illustrates an example for the exchange or negotiation of DTRX information between different DUs of different NG-RAN nodes with split architecture, according to certain embodiments;

FIGURE 18 illustrates an example for the exchange or negotiation of DTRX information between a DU of an NG-RAN node with split architecture and an eNodeB (eNB), according to certain embodiments;

FIGURE 19 illustrates an example communication system, according to certain embodiments;

FIGURE 20 illustrates an example UE, according to certain embodiments;

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

FIGURE 22 illustrates a block diagram of a host, according to certain embodiments;

FIGURE 23 illustrates a virtualization environment in which functions implemented by some embodiments may be virtualized, according to certain embodiments; FIGURE 24 illustrates a host communicating via a network node with a UE over a partially wireless connection, according to certain embodiments;

FIGURE 25 illustrates a method by a first network node for signaling DTRX information, according to certain embodiments.

FIGURE 26 illustrates a method by a second network node for signaling DTRX information, according to certain 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.

As used herein, ‘node’ can be a network node or a UE.

In some embodiments, the terms “radio network node” or simply “network node (NW node)” is used. Examples of network nodes are a RAN node, NodeB, base station (BS), multistandard radio (MSR) radio node such as MSR BS, eNodeB (eNB), gNodeB (gNB), Master eNB (MeNB), Secondary eNB (SeNB), a gNB acting as a secondary node in an EN-DC scenario (i. e. , in a Dual Connectivity (DC) scenario with an eNB as the master node and a gNB as the secondary node (en-gNB), ng-eNB, gNB-CU, gNB-CU-CP, gNB-CU-UP, eNB-CU, eNB-CU-CP, eNB-CU- UP, integrated access backhaul (IAB) node, lAB-donor DU, lAB-donor CU, IAB-DU, IAB- Mobile Termination (IAB-MT), network controller, radio network controller (RNC), base station controller (BSC), relay, donor node controlling relay, base transceiver station (BTS), Central Unit (e.g. in a gNB), Distributed Unit (e.g. in a gNB), Baseband Unit, Centralized Baseband, C-RAN, access point (AP), transmission points, transmission nodes, Remote Radio Unit (RRU), Remote Radio Head (RRH), nodes in distributed antenna system (DAS), core network node (e.g. Mobile Switching Center (MSC), Mobility Management Entity (MME), etc.), Operations & Maintenance (O&M), Operations Support System (OSS), Self Organizing Network (SON), positioning node (e.g. E-SMLC), Operation, Administration & Maintenance (OAM), a Service Management and Orchestration (SMO), a Network Management System (NMS), aNon-Real Time RAN Intelligent Controller (Non-RT RIC), a Real-Time RAN Intelligent Controller (RT-RIC), O-RAN-CU (O- CU), O-RAN-CU-CP (O-CU-CP), O-RAN-CU-UP (O-CU-UP), O-RAN-DU (O-DU), O-RAN- RU (O-RU), and O-RAN-eNB (O-eNB).

Another example of a node is UE, which is a non-limiting term and refers to any type of wireless device communicating with a network node and/or with another UE in a cellular or mobile communication system. Examples of UE are target device, device to device (D2D) UE, vehicular to vehicular (V2V), Machine Type Communication (MTC) UE or UE capable of machine to machine (M2M) communication, Personal Digital Assistant (PDA), tablet, mobile terminals, smart phone, laptop embedded equipment (LEE), laptop mounted equipment (LME), Unified Serial Bus (USB) dongles, etc.

The term radio access technology (RAT), may refer to any RAT such as, for example, Universal Terrestrial Radio Access Network (UTRA), Evolved Universal Terrestrial Radio Access Network (E-UTRA), narrow band internet of things (NB-IoT), WiFi, Bluetooth, next generation RAT, NR, 4^th Generation (4G), 5G, etc. Any of the equipment denoted by the terms node, network node or radio network node may be capable of supporting a single or multiple RATs.

The term DTRX refers to Discontinuous Transmission and/or Discontinuous Reception, or another Network Energy saving strategy. Furthermore, the terms “DTX” and “DRX” may refer to Discontinuous Transmission and Discontinuous Reception, respectively.

The terms “employed” and “used” are referred to interchangeably, herein.

According to certain embodiments, methods and systems are provided for enabling network nodes such as, for example, RAN nodes (such as gNB, gNB-CU, or gNB-DU, or CN nodes, or functions hosted therein, such as AMF) to exchange information associated to at least a DTRX pattern employed, or to be employed, at one or more network nodes. The methods and systems disclosed herein may, in particular embodiments, enable network nodes to negotiate or coordinate information associated to at least a DTRX pattern employed, or to be employed, at one or more network nodes. Herein, the term “DTRX information” is used to refer to any information associated and/or related to at least a DTRX pattern and/or DTRX cycle, employed or to be employed at one or more network nodes, or at/by at least a (physical or logical) part, or entity, or element, or component thereof.

In some embodiments, a first network node can signal to a second network node DTRX information employed, or to be employed, at the first network node.

In a particular embodiment, the second network node can request the first network node to signal to the second network node DTRX information employed, or to be employed, at the first network node.

In a particular embodiment, the second network node can propose/suggest to the first network node DTRX information to be employed at the first network node. In a particular embodiment, the first network node can indicate to the second network node accept or reject regarding the proposal/suggestion for the DTRX information to be employed at the first network node received from the second network node.

In a particular embodiment, the first network node can signal to the second network node one or more counterproposals. These may include, for example, alternative suggestions for the DTRX information to be employed at the first network node.

In a particular embodiment, the second network node can propose and/or suggest to the first network node DTRX information to be employed at the first network node based on or considering at least a proposal and/or suggestion for the said DTRX information received from the first network node.

In a particular embodiment, a second network node can coordinate, or enable or support the coordination of, DTRX information employed, or to be employed, at two or more first network nodes with the two or more first network nodes.

FIGURE 10 illustrates a flow chart and signaling diagram 100 for the exchange, or negotiation, or coordination of information associated to at least a DTRX pattem/cycle between network nodes, according to certain embodiments.

According to certain embodiments, a method executed by a first network node 102 in a communication network to exchange or negotiate or coordinate DTRX information employed, or to be employed, at the first network node 102 with a second network node 104 includes one or more of:

• at step 110, receiving, from the second network node 104, a request to transmit to the second network node DTRX information employed, or to be employed, at the first network node 102;

• at step 120, transmitting, to the second network node 104, DTRX information employed, or to be employed, at the first network node 102;

• at step 130, receiving, from the second network node 104, a proposal/suggestion for the DTRX information to be employed at the first network node 102;

• at step 140, checking the feasibility of the DTRX information proposal;

• at step 150 or 170, transmitting, to the second network node 104, an indication of accept or reject of the proposal/suggestion for the DTRX information received from the second network node 104;

• at step 160, when the proposal/suggestion for the DTRX information is accepted, implementing the DTRX information proposal; and • at step 180, when the proposal/suggestion for the DTRX information is rejected, transmitting, to the second network node 104, one or more counterproposals for the DTRX information.

According to certain embodiments, a method executed by the second network node 104 in a communication network to exchange or negotiate or coordinate DTRX information employed, or to be employed, at one or more first network nodes 102 with the one or more first network nodes 102 includes one or more of:

• at step 110, transmitting to the first network node 102, a request to receive from the first network node DTRX information employed, or to be employed, at the first network node 102;

• at step 120, receiving, from the first network node 102, DTRX information employed, or to be employed, at the first network node 102;

• at step 130, transmitting, to the first network node 102, a proposal/suggestion for the DTRX information to be employed at the first network node 102;

• at step 150 or 170, receiving, from the first network node 102, an indication of accept or reject of the proposal/suggestion for the DTRX information transmitted to the first network node 102;

• when the proposal/suggestion for the DTRX information is rejected by the first network node 102, receiving, from the first network node 102, one or more counterproposals for the DTRX information, at step 180; and

• at step 190, checking the suitability of the DTRX information counterproposal(s), if any, and returning to step 130, if needed.

The example methods are described in further detail below.

DTRX Information Exchange

According to certain embodiments, a first network node 102 can signal to a second network node 104, DTRX information employed, or to be employed, at the first network node 102. In various particular embodiments, the DTRX information can comprise one or more of the following: an on-duration timer; a DTRX long cycle, or a DTX long cycle and/or DRX long cycle; a DTRX short cycle, or a DTX short cycle and/or DRX short cycle; • a DTX and/or DRX cycle duration (e.g., an indication of how long a DTX or DRX cycle is);

• a DTRX inactivity timer;

• a DTRX cycle start offset or a DTX cycle start offset and/or DRX cycle start offset;

• a DTRX long cycle start offset, or a DTX long cycle start offset and/or DRX long cycle start offset;

• an indication related to a time (e.g., a time window or instance) during/at which the indicated DTRX information is employed, or to be employed, at the first network node, e.g., during/at which minute, hour, day, month, and/or year or, alternatively or additionally, during/at which minute of the hour, hour of the day, day of the week or month, and/or week or month of the year, etc.;

• an indication related to a load or traffic (e.g., a load or traffic metric) during/at which the indicated DTRX information is employed, or to be employed, at the first network node, e.g., a load or traffic threshold above or below which the indicated DTRX information is employed, or to be employed, at the first network node.

In a particular embodiment, the DTRX information can comprise multiple of the abovelisted items, e.g., multiple on-duration timers, and/or multiple DTRX cycle durations, and/or multiple DTRX inactivity timers, and/or multiple DTRX cycle start offsets. For example, DTRX information may include separate DTX and DRX information such as, for example, two on- duration timers, two cycle durations, and two cycle start offsets, in case the DTX and DRX cycles are not identical (e.g., not fully overlapping in time).

Based on the above, the first network node 102 can signal to the second network node 104 (e.g., planned/scheduled) DTRX information to be employed during/at day times and/or peak traffic times and/or night times and/or low traffic times. For example, the first network node 102 can inform the second network node 104 planned/scheduled longer DTRX cycles allowing for longer/deeper sleeps, or sleep periods, or sleep opportunities at night times.

In another particular embodiment, the DTRX information can further indicate whether or not the first network node 102, e.g., a RAN node, is able to communicate with UEs and/or other network nodes, e.g., other RAN nodes during the off times of the indicated DRX cycle/pattem.

The communication capabilities of the first network node 102, or at least a part, or entity, or element, or component thereof, during the off times of the indicated DRX cycle/pattem may further be divided into transmitting and receiving/listening. In another embodiment, the DTRX information can further indicate whether or not the first network node 102, or at least a part, or entity, or element, or component thereof, is able to transmit and/or receive/listen during the off times. The DTRX information can further comprise whether the first network node 102 is employing DTX and/or DRX.

In particular embodiments, the DTRX information can further comprise one or more of the following DTRX-related information:

• an indication whether or not the first network node 102 keeps transmitting certain signals, e.g., the minimum (broadcast) signals such as SSBs, System Information Blocks (SIBs), etc. during the off times; and/or

• information to instruct/indicate to which QoS group services or UE groups or paging groups the DRTX information applies.

The first network node 102 can use a procedure (e.g., either an existing procedure or a newly defined procedure) to transmit a DTRX information message 120, denoted as DTRX info (response) in in FIGURE 10, to the second network node 104.

In one scenario, both the first network node 102 and the second network node 104 are RAN nodes. In a related particular embodiment, the first network node 102 may use the NG-RAN node Configuration Update procedure to transmit a first DTRX information message 120 to the second network node 104. In a particular embodiment, the first DTRX information message 120 may be comprised in an NG-RAN NODE CONFIGURATION UPDATE message.

In another scenario, the first network node 102 is a RAN node, and the second network node 104 is a CN node. In a related particular embodiment, the first network node 102 may use the NG Setup procedure to transmit a first DTRX information message 120 to the second network node 104. In a further particular embodiment, the first DTRX information message 120 may be comprised in an NG SETUP REQUEST message. The first network node 102 may, in a particular embodiment, further use the RAN Configuration Update procedure to transmit a second DTRX information message 120 to the second network node 104. In a further particular embodiment, the second DTRX information message 120 may be comprised in a RAN CONFIGURATION UPDATE message. In a further particular embodiment, the first network node 102 may transmit a second DTRX information message 120 without preceding transmission of a first DTRX information message 120.

With respect to the above, it is recognized that using the NG-RAN node Configuration Update procedure or, the NG Setup procedure, or the RAN Configuration Update procedure requires changes in the NGAP and XnAP specifications defined in 3GPP TS 38.413 and 38.423, respectively. In another particular embodiment, the second network node 104 may, in preceding step, request the first network node 102 to signal to the second network node 104, DTRX information employed or to be employed at the first network node 102. Specifically, for example, the second network node 104 may further specify/request in the DTRX information request message 110, denoted as DTRX info request in FIGURE 10, to receive the DTRX information upon every change, upon certain change, with certain periodicity, etc., in certain particular embodiments.

CN and RAN Information Coordination

According to certain embodiments, a CN node can be used as a relay to convey gNB DTRX information or related Network Energy Saving (NES) information between the NG-RAN nodes when the Xn interface is not available.

In a particular embodiment, an NG-RAN node can transmit DTRX information or NES related information to the CN, e.g., via the “Uplink RAN Configuration Transfer” procedure. The CN will then transmit (i. e. , “forward”) the information to one or more other NG-RAN nodes such as, for example, via the “Downlink RAN Configuration Transfer” procedure.

A CN node may also utilize a RAN node’s DTRX information in some procedures to enhance the paging procedure or when setting up certain services, for example. When the CN is aware of the RAN node’s DRTX information, the CN may:

• hold the paging for certain, e.g., less important, services;

• include the DTRX or other NES related information for the neighboring network nodes to aid the RAN paging procedure;

• adjust the CN side QoS parameters, e.g. CN Packet Delay Budgets; and/or

• adjust the setup of the additional NG-U tunnels, which provide delivery of user plane Packet Data Units (PDUs) between the NG-RAN node and the User Plane Function (UPF) .

In a particular embodiment, RAN nodes transmit the DTRX information or NES related information to the CN via, for example, a NG Setup/Modification procedure. The CN node may also indicate different parameters (or parameter sets) related to service groups. In another embodiment, the CN node transmits a RAN node’s DTRX information or NES related information to other (e.g., neighboring) NG-RAN nodes via NGAP such as, for example, during a NG Setup procedure or using the AMF modification, or configuration update, procedure.

In another particular embodiment, a RAN node indicates to the CN that the DTRX or network energy saving procedure is switched off in the RAN node, or that at least a cell or an S SB beam controlled by the RAN node is switched off, and further that the RAN node, or at least a cell or an SSB beam controlled by the RAN node, is in full service or full capability/capacity mode again.

DTRX Information Negotiation/Coor dination

In a particular embodiment, a second network node can propose/ suggest to a first network node DTRX information to be employed at the first network node. For example, a second network node can tell a first network node that it prefers the first network node to keep the receiver ON during OFF times, i.e., to employ only DTX, instead of DTX and DRX, or that it prefers the first network node to keep transmitting certain signals such as, for example, certain broadcast signals, such as SSBs, during OFF times.

Since the DTRX information may include an indication related to a time as well as a load or traffic during/at which the indicated DTRX information is, or is to be, employed at the first network node 102 in certain embodiments, the proposal/ suggest! on for the DTRX information may refer to a future time instance or period as well as a current time instance or period.

In another particular embodiment, the first network node 102 can indicate to the second network node 104 whether the first network node 102 accepts (or has accepted) or rejects (or has rejected) the proposal/suggestion for DTRX information to be employed at the first network node received from the second network node 104.

In another particular embodiment, the first network node 102 may indicate/signal to the second network node 104 one or more counterproposals, i.e., alternative suggestions, for DTRX information to be employed at the first network node. The first network node may do this, for example, in response to rejecting a proposal/suggestion for DTRX information received from the second network node 104. For example, the first network node 102 may reject the proposal of the second network node 104 to keep the receiver ON, or to transmit SSBs, during OFF times. Then the second network node 104 may propose to the first network node 102 to keep the receiver ON in specific instances or periods of OFF time or to transmit SSBs with lower periodicity and sparser occasions.

In another particular embodiment, the second network node 104 can, for example, in a later step, propose/suggest to the first network node 102 a proposal/suggestion for DTRX information to be employed at the first network node. The second network node 104 may do this, for example, in response to receiving one or more counterproposals for the DTRX information from the first network node 102. In another particular embodiment, one network node such as, for example, a second network node 104, may act as a “group leader” of other surrounding or neighboring network nodes such as, for example, network nodes 102 that are deployed in the network area. It may request the other (first) network nodes 102 to report DTRX information and/or other information related to at least a network power/energy saving policy/strategy. The “leading” (second) network node 104 can then collect the information, and, while optionally considering the operator policy for the network area, make a decision related to the information to be employed at the other network nodes 102, and communicate the decision or the information to the other network nodes 102. This is to ensure that the networks nodes in the network area have a synchronized or somehow coordinated power/energy saving policy/strategy. In a particular embodiment, a first network node 102 may first indicate to the “group leader” network node 104 that it is interested to be included in the group.

In another particular embodiment, the NES group leader nodes exchange information on behalf of their groups. One NES group leader node indicates to other NES group leader nodes which NES surrounding nodes are included in its group and, further, which NES surrounding nodes in the other groups that the NES group leader node is interested in obtaining information for/from. This is to reduce the signaling load between the networks so as to enhance efficiency and reduce signaling latency, for example. Such communication may be carried over the Xn interface or the NG interface (in the case an Xn connection does not exist).

In yet another particular embodiment, the NES group leader node acts as NES-related information storage. The NES information from its subscribers, e.g., group members, are submitted and distributed transparently without any interpretation.

FIGURE 11 illustrates an example 200 that includes a NES group leader node 202, according to certain embodiments. The NES group leader node 202 may collect NES-related information such as, for example, including DTRX information, make a decision based on the DTRX information, and communicate that decision to the NES surrounding nodes 204. Such a NES group leader node 202 can be, for example, a network power/energy saving policy maker node/machine. The policy maker node/machine can be part of the CN such that it is a CN node or a function hosted therein, such as an AMF entity. Alternatively, the policy maker node/machine may be part of the RAN. For example, it can be a RAN node or a function located therein such as a “group leader gNB”.

In the approach depicted in FIGURE 11, the NES group leader network node 202 is negotiated and agreed among several (surrounding or participating) network nodes, which are called NES surrounding nodes 204. In an alternative approach, a network node such as, for example, a CN node, can determine the NES group leader network node 202 (which may be a RAN node, for example) and announce it to other (surrounding or participating) network nodes 204. Alternatively, the NES group leader 202 can announce itself as “group leader” to other network nodes 204 through regular interfaces.

FIGURE 12 illustrates a flow chart and signaling diagram 300 that includes a second network node 304 acting as a “group leader” and coordinating DTRX information to be employed at two or more other (first) network nodes 302 within a NES coordination group, according to certain embodiments. Thus, in the depicted example the second network node 304 negotiates with two or more first network nodes 302.

Specifically, as depicted, the method includes one or more of:

• at step 310, the second network node 304 transmits a request for DTRX information employed, or to be employed, at the first network node 302;

• at step 320, the two or more first network nodes 302 transmit, to the second network node 304, DTRX information employed, or to be employed, at the respective first network node 302;

• at step 330, the second network node 304 transmits, to the two or more first network nodes 302, a proposal/suggestion for DTRX information to be employed at the respective first network node 302;

• at step 340, the respective first network node 302 checks the feasibility of the DTRX information proposal;

• at step 350 or 370, the two or more first network node 302 transmit, to the second network node 304, a respective indication of accept or rej ect of the proposal/suggestion for DTRX information received from the second network node 304;

• at step 360, when the proposal/suggestion for the DTRX information is accepted, the first network node 302 implements the DTRX information proposal; and

• at step 380, when the proposal/suggestion for DTRX information is rejected, the first network node 302 transmits, to the second network node 304, one or more counterproposals for the DTRX information.

• at step 390, checking the suitability of the DTRX information counterproposal(s), if any, and returning to step 330, if needed. The desired NES information coordination, e.g., including DTRX information coordination, is achieved by applying the method described herein two or more times at two or more first network nodes 302 and at least a second network node 304. In a particular embodiment, the interactions and procedures described herein may be repeated until the desired NES information coordination result is achieved. The DTRX information exchange or signaling messages 310, 320 are in this case optional, but they can comprise information enabling faster convergence to the desired NES information coordination result.

FIGURE 13 illustrates another example flow chart 400 depicting signaling between the NES group leader node 404 and a NES surrounding node 402, according to certain embodiments.

At 406, information relating to the role(s) of the nodes is exchanged and an agreement relating to these role(s) may be reached. Specifically, as depicted, agreement may be reached with regard to which node is the NES group leader node 404 and which node(s) are the NES surrounding node(s) 402. Additionally, some NES surrounding nodes may subscribe to receive the distributed information from the NES group leader node 404 only. Agreement may also be reached with regard to how the information is to be distributed such as for example, on demand, periodically, or when certain threshold values are met.

At 408, the NES surrounding node(s) provides its own NES related information, e.g. to the NES group leader node 404. At any time, the NES surrounding node(s) may indicate not to receive information and/or not to update the NES group leader node 404 with new NES related information.

At 410, the NES group leader node 404 distributes the NES related information. In certain embodiments, the NES group leader node 404 may strategically coordinate the NES surrounding nodes 402, or at least a cell or SSB beam controlled by the NES surrounding nodes 402, to go to sleep, e.g., employ DTRX, at the given times, e.g., at different times, to ensure that there are always some cells to serve the UE, and the other cells can go to “deep sleep” to optimize/increase the network energy saving.

FIGURE 14 illustrates an example flow chart 500 depicting signaling between NES group leader nodes 502 and 504 for the exchange of information for groups, according to certain embodiments.

At 506, information is exchanged so that agreement(s) may be reached between the NES group leader nodes 502 and 504. Specifically, agreement may be reached with regard to which node(s) are the NES surrounding node(s). Additionally, agreement may be reached with respect to what kind of NES related information will be exchanged and/or how the information will be updated and/or exchanged.

At 508, the NES group leader nodes 502 and 504 exchange and/or distribute NES related information for their respective group.

Node-level Architecture Options

Certain embodiments described above provide a generic system description comprising a first network node and a second network node. Described now are some non-limiting examples of the realization of the system provided for specific technologies (e.g., the 3GPP LTE and NG-RAN systems).

In a particular embodiment, the first network node is a first RAN node (e.g., a gNB or an eNB) and the second network node is a second RAN node (e.g., another gNB or another eNB). The communication between the first network node and the second network node can occur directly or indirectly (e.g., via XnAP, X2AP) or via a third network node (e.g., NGAP, SI AP).

- In one example, the first network node and the second network node are enhanced NodeBs of a 3GPP Evolved Universal Terrestrial Radio Access Network (E-UTRAN) system. In this case and referring to FIGURE 10, the DTRX information exchange messages 110, 120 as well as the DTRX information negotiation messages 130, 150, 170, 180 can be exchanged using a X2 interface of the E-UTRAN system (e.g., LTE and/or LTE- A).

- In another example, the first network node and the second network node are NG-RAN nodes (e.g., gNB) of a 3GPP NG-RAN system (also knowns as NR system). In this case the DTRX information exchange messages 110, 120 and the DTRX information negotiation messages 130, 150, 170, 180 can be exchanged using an Xn interface of the NG-RAN system (e.g., NR and/or NR Advanced (NR- A)).

- In another example, the first network node is an NG-RAN node of an NG-RAN system, while the second network node is enhanced NodeB (e.g., eNB) of an E-UTRAN system. In this case, the DTRX information exchange messages 110, 120 and the DTRX information negotiation messages 130, 150, 170, 180 can be exchanged using a X2 interface between the E-UTRAN system and NG-RAN system: Without loss of generality, the first network node could be a RAN node, or a logical node of a RAN node, e.g., a gNB-CU, as depicted in FIGURE 18.

In a particular embodiment of the method with distributed architecture, a first network node is a first logical entity of a RAN node, and the second network node is a second logical entity of a RAN node. In one scenario, the first network node and the second network node can be two different logical entities of the same RAN node. In another scenario, the first network node and the second network node are two logical entities of two different RAN nodes. Examples of logical entities of aRAN node are, e.g., the CU of anNG-RAN node (e.g., agNB-CU or the corresponding control plane entity gNB-CU-CP) and the DU of an NG-RAN node (e.g., a gNB-DU). If present, a third network node is a third logical entity of a RAN node (e.g., a second gNB-DU).

FIGURE 15 illustrates an example system 600 for the exchange or negotiation of DTRX information between a gNB-DU 602 of an NG-RAN node and a gNB-CU (or a gNB-CU-CP) 604 of the same NG-RAN node, according to certain embodiments. In one particular embodiment, the first network node is a DU of an NG-RAN node (e.g., a gNB-DU), while the second network node is a CU of an NG-RAN node (e.g., a gNB-CU or the corresponding gNB-CU-CP). In this case, the DTRX information exchange messages 110, 120 and the DTRX information negotiation messages 130, 150, 170, 180 can be exchanged using an Fl interface of the NG-RAN system, as illustrated in FIGURE 15.

In a particular embodiment, the first network node is a CU of a NG-RAN node (e.g., a gNB-CU), while the second network node is a DU of a NG-RAN node (e.g., a gNB-DU). In this case, the DTRX information exchange messages 110, 120 and the DTRX information negotiation messages 130, 150, 170, 180 can be exchanged using an Fl interface of the NG-RAN system.

FIGURE 16 illustrates an example system 700 for the exchange or negotiation of DTRX information between different DUs of a NG-RAN node with split architecture, e.g., between different DUs controlling different (e.g., neighboring) radio cells. In the depicted example, an NG- RAN node 702 consists of three or more logical nodes comprising multiple DUs 704 (i.e., multiple gNB-DUs) controlled by a single CU 706 (i.e., a gNB-CU). In one embodiment, the method can be applied to pairs of nodes in a system with nodes to exchange or negotiate DTRX information. In this example, two gNB-DUs exchange or negotiate via a gNB-CU (or the corresponding gNB- CU-CP) DTRX information. The method is thereby applied: between the gNB-DUi 704 and the gNB-CU 706, with communication over an Fl interface; and between the gNB-CU 706 and the gNB-DU2 704, with communication over an Fl interface.

In a particular embodiment, the first network node is a first CU of a first NG-RAN node (e.g., a gNB-CUi), while the second network node is a second CU of a second NG-RAN node (e.g., agNB-CU2). In this case, the DTRX information exchange messages 110, 120 and the DTRX information negotiation messages 130, 150, 170, 180 can be exchanged using an Xn interface of the NG-RAN system, as shown in FIGURE 17.

FIGURE 17 further illustrates an example for the exchange or negotiation of DTRX information between different DUs of different NG-RAN nodes with split architecture, again, e.g., between different DUs controlling different (e.g., neighboring) radio cells. In this example, two gNB-DUs of two different NG-RAN nodes communicate via the respective CUs. For example, gNB-CUi 804 of NG-RAN nodei 802 and gNB-CU₂ 810 of NG-RAN node₂ 808 (or the gNB- CUi-CP and the gNB-CU₂-CP) respectively, to exchange or negotiate DTRX information. The method is thus applied: between the gNB-DUi 806 and the gNB-CUi 804, with communication over an Fl interface; between the gNB-CUi 804 and the gNB-CU₂ 810, with communication over an Xn interface; and between the gNB-CU₂ 810 and the gNB-DU₂ 812, with communication over an F 1 interface.

FIGURE 18 illustrates an example system 900 for the exchange or negotiation of DTRX information between a DU of an NG-RAN node 902 with split architecture and an eNB 904, again, e.g., between a DU 906 and an eNB 904 controlling different (e.g., neighboring) radio cells. In this example, a gNB-DU 906 of the NG-RAN node 902 communicates via its CU 908, i.e., gNB- CU (or the gNB-CU-CP), with an eNB to exchange or negotiate DTRX information. The method is therefore applied: between the gNB-DU 906 and the gNB-CU 908, with communication over an Fl interface; and between the gNB-CU 908 and the eNB 904, with communication over an X2 interface.

In a particular embodiment, the method described herein can be used to ensure that the OFF times of DTRX of neighboring RAN nodes, or cells or SSB beams controlled by the neighboring RAN nodes, are not completely overlapping so that the UE has access at least to some sync reference signals (e.g., SSBs, from serving cell or neighbor cells).

In another particular embodiment, the method described herein can be used to ensure that the ON times of DTRX of neighboring RAN nodes, or cells or SSB beams controlled by the neighboring RAN nodes, are non-overlapping (as much as possible) so that the inter-cell interference is minimized, while at the same time the energy saving is maximized. This is achieved by faster serving of the connected UEs and positively effecting their QoS and QoE due to higher possible modulation orders, less retransmissions, etc. and therefore faster returning to sleep (i.e. , low power/energy, states or modes).

FIGURE 19 shows an example of a communication system 1000 in accordance with some embodiments. In the example, the communication system 1000 includes a telecommunication network 1002 that includes an access network 1004, such as a radio access network (RAN), and a core network 1006, which includes one or more core network nodes 1008. The access network 1004 includes one or more access network nodes, such as network nodes 1010A and 1010B (one or more of which may be generally referred to as network nodes 1010), or any other similar 3^rd Generation Partnership Project (3GPP) access node or non-3GPP access point. The network nodes 1010 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 1012A, 1012B, 1012C, and 1012D (one or more of which may be generally referred to as UEs 1012) to the core network 1006 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 1000 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 1000 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system.

The UEs 1012 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 1010 and other communication devices. Similarly, the network nodes 1010 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs 1012 and/or with other network nodes or equipment in the telecommunication network 1002 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 1002.

In the depicted example, the core network 1006 connects the network nodes 1010 to one or more hosts, such as host 1016. 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 1006 includes one more core network nodes (e.g., core network node 1008) 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 1008. 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 UPF.

The host 1016 may be under the ownership or control of a service provider other than an operator or provider of the access network 1004 and/or the telecommunication network 1002, and may be operated by the service provider or on behalf of the service provider. The host 1016 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio/video content, data collection services such as 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 1000 of FIGURE 19 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 1002 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 1002 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 1002. For example, the telecommunications network 1002 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 1012 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 1004 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 1004. 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, the hub 1014 communicates with the access network 1004 to facilitate indirect communication between one or more UEs (e.g., UE 1012C and/or 1012D) and network nodes (e.g., network node 1010B). In some examples, the hub 1014 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 1014 may be a broadband router enabling access to the core network 1006 for the UEs. As another example, the hub 1014 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 1010, or by executable code, script, process, or other instructions in the hub 1014. As another example, the hub 1014 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 1014 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 1014 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 1014 then provides to the UE either directly, after performing local processing, and/or after adding additional local content. In still another example, the hub 1014 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 1014 may have a constant/persistent or intermittent connection to the network node 1010B. The hub 1014 may also allow for a different communication scheme and/or schedule between the hub 1014 and UEs (e.g., UE 1012C and/or 1012D), and between the hub 1014 and the core network 1006. In other examples, the hub 1014 is connected to the core network 1006 and/or one or more UEs via a wired connection. Moreover, the hub 1014 may be configured to connect to an M2M service provider over the access network 1004 and/or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 1010 while still connected via the hub 1014 via a wired or wireless connection. In some embodiments, the hub 1014 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 1010B. In other embodiments, the hub 1014 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 1010B, but which is additionally capable of operating as a communication start and/or end point for certain data channels.

FIGURE 20 shows a UE 1100 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 cameras, 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 (3GPP), 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 1100 includes processing circuitry 1102 that is operatively coupled via a bus 1104 to an input/ output interface 1106, apower source 1108, amemory 1110, a communication interface 1112, and/or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in FIGURE 20. 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 1102 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 1110. The processing circuitry 1102 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 1102 may include multiple central processing units (CPUs).

In the example, the input/ output interface 1106 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 1100. 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 1108 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 1108 may further include power circuitry for delivering power from the power source 1108 itself, and/or an external power source, to the various parts of the UE 1100 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 1108. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 1108 to make the power suitable for the respective components of the UE 1100 to which power is supplied.

The memory 1110 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 1110 includes one or more application programs 1114, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 1116. The memory 1110 may store, for use by the UE 1100, any of a variety of various operating systems or combinations of operating systems.

The memory 1110 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 1110 may allow the UE 1100 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 1110, which may be or comprise a device-readable storage medium.

The processing circuitry 1102 may be configured to communicate with an access network or other network using the communication interface 1112. The communication interface 1112 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 1122. The communication interface 1112 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 1118 and/or a receiver 1120 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 1118 and receiver 1120 may be coupled to one or more antennas (e.g., antenna 1122) and may share circuit components, software or firmware, or alternatively be implemented separately.

In the illustrated embodiment, communication functions of the communication interface 1112 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/intemet 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 1112, 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 to 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 a device which is or which is 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, amotion detector, a thermostat, asmoke detector, adoor/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 of the intended application of the loT device in addition to other components as described in relation to the UE 1100 shown in FIGURE 20.

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 3GPP 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 21 shows a network node 1200 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 1200 includes a processing circuitry 1202, a memory 1204, a communication interface 1206, and a power source 1208. The network node 1200 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 1200 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 1200 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 1204 for different RATs) and some components may be reused (e.g., a same antenna 1210 may be shared by different RATs). The network node 1200 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 1200, 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 1200.

The processing circuitry 1202 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node 1200 components, such as the memory 1204, to provide network node 1200 functionality. In some embodiments, the processing circuitry 1202 includes a system on a chip (SOC). In some embodiments, the processing circuitry 1202 includes one or more of radio frequency (RF) transceiver circuitry 1212 and baseband processing circuitry 1214. In some embodiments, the radio frequency (RF) transceiver circuitry 1212 and the baseband processing circuitry 1214 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 1212 and baseband processing circuitry 1214 may be on the same chip or set of chips, boards, or units.

The memory 1204 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 1202. The memory 1204 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 1202 and utilized by the network node 1200. The memory 1204 may be used to store any calculations made by the processing circuitry 1202 and/or any data received via the communication interface 1206. In some embodiments, the processing circuitry 1202 and memory 1204 is integrated.

The communication interface 1206 is used in wired or wireless communication of signaling and/or data between anetwork node, access network, and/or UE. As illustrated, the communication interface 1206 comprises port(s)/terminal(s) 1216 to send and receive data, for example to and from a network over a wired connection. The communication interface 1206 also includes radio front-end circuitry 1218 that may be coupled to, or in certain embodiments a part of, the antenna 1210. Radio front-end circuitry 1218 comprises filters 1220 and amplifiers 1222. The radio frontend circuitry 1218 may be connected to an antenna 1210 and processing circuitry 1202. The radio front-end circuitry may be configured to condition signals communicated between antenna 1210 and processing circuitry 1202. The radio front-end circuitry 1218 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 1218 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 1220 and/or amplifiers 1222. The radio signal may then be transmitted via the antenna 1210. Similarly, when receiving data, the antenna 1210 may collect radio signals which are then converted into digital data by the radio front-end circuitry 1218. The digital data may be passed to the processing circuitry 1202. In other embodiments, the communication interface may comprise different components and/or different combinations of components.

In certain alternative embodiments, the network node 1200 does not include separate radio front-end circuitry 1218, instead, the processing circuitry 1202 includes radio front-end circuitry and is connected to the antenna 1210. Similarly, in some embodiments, all or some of the RF transceiver circuitry 1212 is part of the communication interface 1206. In still other embodiments, the communication interface 1206 includes one or more ports or terminals 1216, the radio frontend circuitry 1218, and the RF transceiver circuitry 1212, as part of a radio unit (not shown), and the communication interface 1206 communicates with the baseband processing circuitry 1214, which is part of a digital unit (not shown).

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

The antenna 1210, communication interface 1206, and/or the processing circuitry 1202 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 1210, the communication interface 1206, and/or the processing circuitry 1202 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 1208 provides power to the various components of network node 1200 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 1208 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 1200 with power for performing the functionality described herein. For example, the network node 1200 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 1208. As a further example, the power source 1208 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 1200 may include additional components beyond those shown in FIGURE 21 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 1200 may include user interface equipment to allow input of information into the network node 1200 and to allow output of information from the network node 1200. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 1200.

FIGURE 22 is a block diagram of a host 1300, which may be an embodiment of the host 1016 of FIGURE 19, in accordance with various aspects described herein. As used herein, the host 1300 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 1300 may provide one or more services to one or more UEs.

The host 1300 includes processing circuitry 1302 that is operatively coupled via a bus 1304 to an input/output interface 1306, a network interface 1308, a power source 1310, and a memory 1312. 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 11 and 12, such that the descriptions thereof are generally applicable to the corresponding components of host 1300.

The memory 1312 may include one or more computer programs including one or more host application programs 1314 and data 1316, which may include user data, e.g., data generated by a UE for the host 1300 or data generated by the host 1300 for a UE. Embodiments of the host 1300 may utilize only a subset or all of the components shown. The host application programs 1314 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., FL AC, 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 1314 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 1300 may select and/or indicate a different host for over-the-top services for a UE. The host application programs 1314 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 23 is a block diagram illustrating a virtualization environment 1400 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 1400 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 1402 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment 1400 to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein.

Hardware 1404 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 1406 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 1408A and 1408B (one or more of which may be generally referred to as VMs 1408), and/or perform any of the functions, features and/or benefits described in relation with some embodiments described herein. The virtualization layer 1406 may present a virtual operating platform that appears like networking hardware to the VMs 1408.

The VMs 1408 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 1406. Different embodiments of the instance of a virtual appliance 1402 may be implemented on one or more of VMs 1408, 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 1408 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 1408, and that part of hardware 1404 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 1408 on top of the hardware 1404 and corresponds to the application 1402.

Hardware 1404 may be implemented in a standalone network node with generic or specific components. Hardware 1404 may implement some functions via virtualization. Alternatively, hardware 1404 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 1410, which, among others, oversees lifecycle management of applications 1402. In some embodiments, hardware 1404 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 1412 which may alternatively be used for communication between hardware nodes and radio units.

FIGURE 24 shows a communication diagram of a host 1502 communicating via a network node 1504 with a UE 1506 over a partially wireless connection in accordance with some embodiments.

Example implementations, in accordance with various embodiments, of the UE (such as a UE 1012A of FIGURE 19 and/or UE 1100 of FIGURE 20), network node (such as network node 1010A of FIGURE 19 and/or network node 1200 of FIGURE 21), and host (such as host 1016 of FIGURE 19 and/or host 1300 of FIGURE 22) discussed in the preceding paragraphs will now be described with reference to FIGURE 24. Like host 1300, embodiments of host 1502 include hardware, such as a communication interface, processing circuitry, and memory. The host 1502 also includes software, which is stored in or accessible by the host 1502 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 1506 connecting via an over-the-top (OTT) connection 1550 extending between the UE 1506 and host 1502. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection 1550.

The network node 1504 includes hardware enabling it to communicate with the host 1502 and UE 1506. The connection 1560 may be direct or pass through a core network (like core network 1006 of FIGURE 19) 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 1506 includes hardware and software, which is stored in or accessible by UE 1506 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 1506 with the support of the host 1502. In the host 1502, an executing host application may communicate with the executing client application via the OTT connection 1550 terminating at the UE 1506 and host 1502. 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 1550 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 1550.

The OTT connection 1550 may extend via a connection 1560 between the host 1502 and the network node 1504 and via a wireless connection 1570 between the network node 1504 and the UE 1506 to provide the connection between the host 1502 and the UE 1506. The connection 1560 and wireless connection 1570, over which the OTT connection 1550 may be provided, have been drawn abstractly to illustrate the communication between the host 1502 and the UE 1506 via the network node 1504, 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 1550, in step 1508, the host 1502 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 1506. In other embodiments, the user data is associated with a UE 1506 that shares data with the host 1502 without explicit human interaction. In step 1510, the host 1502 initiates a transmission carrying the user data towards the UE 1506. The host 1502 may initiate the transmission responsive to a request transmitted by the UE 1506. The request may be caused by human interaction with the UE 1506 or by operation of the client application executing on the UE 1506. The transmission may pass via the network node 1504, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 1512, the network node 1504 transmits to the UE 1506 the user data that was carried in the transmission that the host 1502 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 1514, the UE 1506 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 1506 associated with the host application executed by the host 1502.

In some examples, the UE 1506 executes a client application which provides user data to the host 1502. The user data may be provided in reaction or response to the data received from the host 1502. Accordingly, in step 1516, the UE 1506 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 1506. Regardless ofthe specific manner in which the user data was provided, the UE 1506 initiates, in step 1518, transmission of the user data towards the host 1502 via the network node 1504. In step 1520, in accordance with the teachings of the embodiments described throughout this disclosure, the network node 1504 receives user data from the UE 1506 and initiates transmission of the received user data towards the host 1502. In step 1522, the host 1502 receives the user data carried in the transmission initiated by the UE 1506.

One or more of the various embodiments improve the performance of OTT services provided to the UE 1506 using the OTT connection 1550, in which the wireless connection 1570 forms the last segment. More precisely, the teachings of these embodiments may improve one or more of, for example, data rate, latency, and/or power consumption and, thereby, provide benefits such as, for example, reduced user waiting time, relaxed restriction on file size, improved content resolution, better responsiveness, and/or extended battery lifetime.

In an example scenario, factory status information may be collected and analyzed by the host 1502. As another example, the host 1502 may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, the host 1502 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, the host 1502 may store surveillance video uploaded by a UE. As another example, the host 1502 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 1502 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 1550 between the host 1502 and UE 1506, 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 1502 and/or UE 1506. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 1550 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 1550 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node 1504. 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 1502. The measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 1550 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.

FIGURE 25 illustrates a method 1600 by a first network node 102, 302 for signaling DTRX information, according to certain embodiments. The method begins at step 1602 when the first network node 102, 302 transmits, to a second network node 104, 304, first DTRX information 120, 320 associated with at least one of a DTRX pattern and/or cycle that is employed and a DTRX pattern and/or cycle that is to be employed at or by the first network node 102, 302.

In a particular embodiment, the first network node 102, 302 receives, from the second network node 104, 304, a request for the first DTRX information, and the first DTRX information is transmitted to the second network node 104, 304 based on the request.

In a particular embodiment, the first network node 102, 302 receives second DTRX information from the second network node 104, 304, and the second DTRX information includes at least a portion of a DTRX pattern and/or cycle proposed to be employed at or by the first network node.

In a particular embodiment, the first network node 102, 302 determines whether to employ the second DTRX information received from the second network node 104, 304 and transmits, to the second network node 104, 304, an indication of an acceptance or a rejection of the second DTRX information received from the second network node.

In a particular embodiment, the first network node 102, 302 the indication is a rejection of the second DTRX information, and the first network node 102, 302 transmits third DTRX information to the second network node 104, 304. The third DTRX information includes a counterproposal of at least a portion of a DTRX pattern and/or cycle to be employed at or by the first network node 102, 302.

In a particular embodiment, at least one of the first DTRX information, the second DTRX information, and the third DTRX information includes at least one of: an on-duration timer; a DTX and/or DRX cycle duration; a DTRX inactivity timer; a DTX and/or a DRX cycle start offset; and an indication associated with a time or time period for employing the first, second, and/or third DTRX information.

In a particular embodiment, at least one of the first DTRX information, the second DTRX information, and the third DTRX information includes at least one of: an indication of a load or traffic metric during which the first, second, and/or third DTRX information is to be employed; an indication of whether the first network node or a component of the first network node may transmit a communication during an off time associated with the first, second, and/or third DTRX information; and an indication of whether the first network node or a component of the first network node may receive a communication during an off time associated with the first, second, and/or third DTRX information.

In a particular embodiment, the first network node 102, 302 is a first RAN node, the second network node 104, 304 is a second RAN node, and at least one of the first DTRX information, the second DTRX information, and the third DTRX information is transmitted to and/or received from the second network node 104, 304 via a Xn interface or an X2 interface.

In a particular embodiment, the first network node 102, 302 is a first logical entity of a first RAN node, the second network node 104, 304 is a second logical entity of a second RAN node, and at least one of the first DTRX information, the second DTRX information, and the third DTRX information is transmitted to and/or received from the second logical entity of the second network node 104, 304 via a Xn interface or an X2 interface.

In a further particular embodiment, the first logical entity is a first CU of the first RAN node 102, 302, and the second logical entity is a second CU of the second RAN node 104, 304.

In a further particular embodiment, at least one of the first DTRX information and the third DTRX information is transmitted in aNG-RAN NODE CONFIGURATION UPDATE message.

In a particular embodiment, the first network node 102, 302 is a first RAN node, the second network node 104, 304 is a second RAN node, and at least one of the first DTRX information, the second DTRX information, and the third DTRX information is transmitted to and/or received from the second network node 104, 304 via a core network node.

In a particular embodiment, the first network node 102, 302 is a first logical entity of a first RAN node, the second network node 104, 304 is a second logical entity of the first RAN node, and at least one of the first DTRX information, the second DTRX information, and the third DTRX information is transmitted to and/or received from the second network node 104, 304 via an Fl interface. In a further particular embodiment, the first logical entity is a DU of the first RAN node, and the second logical entity is a CU of the first RAN node.

In a further particular embodiment, the first logical entity is a CU of the first RAN node, and the second logical entity is a first DU of the first RAN node, and prior to transmitting the first DTRX information to the second logical entity, the first logical entity receives the first DTRX information from a third logical entity that is a second DU of the first RAN node.

In a particular embodiment, the first network node 102, 302 is a RAN node, the second network node 104, 304 is a Core network node, and the first DTRX information is transmitted in a NG SETUP REQUEST message or a RAN CONFIGURATION UPDATE message.

In a particular embodiment, the second network node 104, 304 operates as a group leader with respect to the first network node 102, 302 and at least one additional network node in a NES coordination group.

FIGURE 26 illustrates a method 1700 by a second network node 104, 304 for signaling DTRX information, according to certain embodiments. The method begins at step 1702 when the second network node 104, 304 receives, from a first network node 102, 302 first DTRX information associated with at least one of a DTRX pattern and/or cycle that is employed and a DTRX pattern and/or cycle that is to be employed at or by the first network node 102, 302.

In a particular embodiment, the second network node 104, 304 transmits, to the first network node, a request for the first DTRX information, and the first DTRX information is received from the first network node 102, 302 based on the request.

In a particular embodiment, the second network node 104, 304 transmits second DTRX information to the first network node, and the second DTRX information includes at least a portion of a DTRX pattern and/or cycle proposed to be employed at or by the first network node.

In a particular embodiment, the second network node 104, 304 receives, from a third network node, fourth DTRX information associated with at least one of a DTRX pattern and/or cycle that is employed and a DTRX pattern and/or cycle that is to be employed at or by the third network node. The second network node 104, 304 performs coordination between the first network node and the third network node to minimize conflict between the first DTRX information and the fourth DTRX information.

In a further particular embodiment, when performing coordination between the first network node and the third network node, the second network node 104, 304 determines that the first DTRX information and the fourth DTRX information conflict. Based on determining that the first DTRX information and the fourth DTRX information conflict, the second network node 104, 304 transmits second DTRX information to the first network node 102, 302, and the second DTRX information includes at least a portion of a DTRX pattern and/or cycle proposed to be employed at or by the first network node.

In a particular embodiment, the second network node 104, 304 receives, from the first network node 102, 302, an indication of an acceptance or a rejection of the second DTRX information transmitted to the first network node 102, 302.

In a particular embodiment, the indication is a rejection of the second DTRX information, and the second network node 104, 304 receives third DTRX information from the first network node 102, 302. The third DTRX information includes a counterproposal of at least a portion of a DTRX pattern and/or cycle to be employed at or by the first network node 102, 302.

In a particular embodiment, at least one of the first DTRX information, the second DTRX information, the third DTRX information, and the fourth DTRX information includes at least one of: an on-duration timer; a DTX and/or DRX cycle duration; a DTRX inactivity timer; a DTX and/or a DRX cycle start offset; and an indication associated with a time or time period for employing the first, second, third, and/or fourth DTRX information.

In a particular embodiment, at least one of the first DTRX information, the second DTRX information, the third DTRX information, and the fourth DTRX information includes at least one of: an indication of a load or traffic metric during which the first, second, third, and/or fourth DTRX information is to be employed; an indication of whether the first network node (or, where applicable according to the above, the third network node) or a component of the first network node (or, where applicable according to the above, the third network node) may transmit a communication during an off time associated with the first, second, third, and/or fourth DTRX information; and an indication of whether the first network node (or, where applicable according to the above, the third network node) or a component of the first network node (or, where applicable according to the above, the third network node) may receive a communication during an off time associated with the first, second, third, and/or fourth DTRX information.

In a particular embodiment, the first network node 102, 302 (or, where applicable according to the above, the third network node) is a first RAN node, the second network node 104, 304 is a second RAN node, and at least one of the first DTRX information, the second DTRX information, the third DTRX information, and the fourth DTRX information is transmitted to and/or received from the second network node 104, 304 via a Xn interface or an X2 interface.

In a particular embodiment, the first network node 102, 302 (or, where applicable according to the above, the third network node) is a first logical entity of a first RAN node, the second network node 104, 304 is a second logical entity of a second RAN node, and at least one of the first DTRX information, the second DTRX information, the third DTRX information, and the fourth DTRX information is transmitted to and/or received from the second logical entity of the second network node 104, 304 via a Xn interface or an X2 interface.

In a particular embodiment, the first logical entity is a first CU of the first RAN node, and the second logical entity is a second CU of the second RAN node.

In a particular embodiment, at least one of the first DTRX information and the third DTRX information is received in aNG-RAN NODE CONFIGURATION UPDATE message.

In a particular embodiment, the first network node 102, 302 (or, where applicable according to the above, the third network node) is a first RAN node, the second network node 104, 304 is a second RAN node, and at least one of the first DTRX information, the second DTRX information, the third DTRX information, and the fourth DTRX information is transmitted to and/or received from the first network node 102, 302 (or, where applicable according to the above, the third network node) via a core network node.

In a particular embodiment, the first network node 102, 302 (or, where applicable according to the above, the third network node) is a first logical entity of a first RAN node, the second network node 104, 304 is a second logical entity of the first RAN node, and at least one of the first DTRX information, the second DTRX information, the third DTRX information, and the fourth DTRX information is transmitted to and/or received from the second network node 104, 304 via an Fl interface.

In a particular embodiment, the first logical entity is a DU of the first RAN node, and the second logical entity is a CU of the first RAN node.

In a particular embodiment, the first logical entity is a CU of a first RAN node, and the second logical entity is a DU of the first RAN node, and the first DTRX information is associated with a third logical entity that is a second DU of the first RAN node and is received via the first logical entity.

In a particular embodiment, the first network node 102, 302 is a RAN node, the second network node 104, 304 is a Core network node, and the first DTRX information is received in a NG SETUP REQUEST message or a RAN CONFIGURATION UPDATE message.

In a particular embodiment, the second network node 104, 304 operates as a group leader with respect to the first network node 102, 302 and at least one additional network node in a NES coordination group. 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.

EXAMPLE EMBODIMENTS

Group A Example Embodiments

Example Embodiment Al. A method by a user equipment for signaling DTRX information, the method comprising: any of the user equipment steps, features, or functions described above, either alone or in combination with other steps, features, or functions described above.

Example Embodiment A2. The method of the previous embodiment, further comprising one or more additional user equipment steps, features or functions described above.

Example Embodiment A3. The method of any of the previous embodiments, further comprising: providing user data; and forwarding the user data to a host computer via the transmission to the network node.

Group B Example Embodiments

Example Embodiment Bl. A method performed by a first network node or second network node for signaling DTRX information, the method comprising: any of the network node steps, features, or functions described above, either alone or in combination with other steps, features, or functions described above.

Example Embodiment B2. The method of the previous embodiment, further comprising one or more additional network node steps, features or functions described above.

Example Embodiment B3. 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 Example Embodiments

Example Embodiment Cl. A method by a first network node for signaling DTRX information, the method comprising: transmitting, to a second network node, first DTRX information associated with at least one of a DTRX pattern and/or cycle that is employed or to be employed at or by the first network node.

Example Embodiment C2. The method of Example Embodiment Cl, comprising receiving, from the second network node, a request for the first DTRX information, wherein the first DTRX information is transmitted to the second network node based on the request.

Example Embodiment C3. The method of any one of Example Embodiments Cl to C2, comprising receiving second DTRX information from the second network node, the second DTRX information comprising at least a portion of a DTRX pattern and/or cycle proposed to be employed at or by the first network node.

Example Embodiment C4. The method of Example Embodiment C3, comprising: determining whether to employ the second DTRX information received from the second network node.

Example Embodiment C5. The method of any one of Example Embodiments C3 to C4, comprising transmitting, to the second network node, an indication of an acceptance or a rejection of the second DTRX information received from the second network node.

Example Embodiment C6. The method of Example Embodiment C5, wherein the indication is a rejection of the second DTRX information, and the method comprises transmitting third DTRX information to the second network node, the third DTRX information comprising a counterproposal of at least a portion of a DTRX pattern and/or cycle to be employed at or by the first network node.

Example Embodiment C7. The method of any one of Example Embodiments Cl to C6, wherein at least one of the first DTRX information, the second DTRX information, and the third DTRX information comprises at least one of: an on-duration timer; a DTRX long cycle; a DTX long cycle and/or DRX long cycle; a DTRX short cycle; a DTX short cycle and/or DRX short cycle; a DTRX inactivity timer; a DTRX long cycle start offset; a DTX long cycle start offset and/or a DRX long cycle start offset; an indication associated with a time or time period for employing the first, second, and/or third DTRX information; an indication of a load or traffic metric during which the first, second, and/or third DTRX information is to be employed; an indication of whether the first network node or a component of the first network node may transmit a communication during an off time associated with the first, second, and/or third DTRX information; and an indication of whether the first network node or a component of the first network node may receive a communication during an off time associated with the first, second, and/or third DTRX information.

Example Embodiment C8. The method of any one of Example Embodiments Cl to C7, wherein the first network node is a RAN node and the second network node is a RAN node, and the first DTRX information is transmitted in a NG-RAN NODE CONFIGURATION UPDATE message.

Example Embodiment C9. The method of Example Embodiment C8, wherein at least one of the first DTRX information, the second DTRX information, and the third DTRX information is transmitted to and/or received from the second network node via a Xn interface or an X2 interface.

Example Embodiment CIO. The method of Example Embodiment C8, wherein at least one of the first DTRX information, the second DTRX information, and the third DTRX information is transmitted to and/or received from the second network node via a core network node.

Example Embodiment Cl 1. The method of any one of Example Embodiments Cl to C7, wherein the first network node is a RAN node and the second network node is a Core network node, and the first DTRX information is transmitted in a NG SETUP REQUEST message or a RAN CONFIGURATION UPDATE message.

Example Embodiment Cl 2. The method of any one of Example Embodiments Cl to Cll, wherein: the first network node is a first logical entity of a first RAN node, and the second network node is a second logical entity of a second RAN node.

Example Embodiment Cl 3. The method of any one of Example Embodiments Cl to Cll, wherein: the first network node is a first logical entity of a first RAN node, and the second network node is a second logical entity of the first RAN node.

Example Embodiment Cl 4. The method of any one of Example Embodiments Cl to Cll, wherein: the first network node is a DU of a first RAN node, and the second network node is a CU of a second RAN node.

Example Embodiment Cl 5. The method of any one of Example Embodiments Cl to Cll, wherein: the first network node is a DU of a first RAN node, and the second network node is a CU of the first RAN node.

Example Embodiment Cl 6. The method of any one of Example Embodiments Cl to Cll, wherein: the first network node is a CU of a first RAN node, and the second network node is a DU of a second RAN node. Example Embodiment Cl 7. The method of any one of Example Embodiments Cl to Cl 1, wherein: the first network node is a first CU of a first RAN node, and the second network node is a DU of the first RAN node.

Example Embodiment Cl 8. The method of any one of Example Embodiments Cl to Cll, wherein: the first network node is a CU of a first RAN node, and the second network node is a CU of a second RAN node.

Example Embodiment Cl 9. The method of any one of Example Embodiments Cl to Cll, wherein: the first network node is a DU of a first RAN node, and the second network node is a DU of a second RAN node.

Example Embodiment C20.The method of any one of Example Embodiments Cl to Cl 9, wherein the second network node operates as a group leader with respect to the first network node and at least one additional network node in aNES coordination group.

Example Embodiment C21. The method of Example Embodiments Cl to C20, further comprising: obtaining user data; and forwarding the user data to a host or a user equipment.

Example Embodiment C22.A user equipment comprising processing circuitry configured to perform any of the methods of Example Embodiments Cl to C21.

Example Embodiment C23.A wireless device comprising processing circuitry configured to perform any of the methods of Example Embodiments Cl to C21.

Example Embodiment C24. A computer program comprising instructions which when executed on a computer perform any of the methods of Example Embodiments Cl to C21.

Example Embodiment C25. A computer program product comprising computer program, the computer program comprising instructions which when executed on a computer perform any of the methods of Example Embodiments Cl to C21.

Example Embodiment C26. A non-transitory computer readable medium storing instructions which when executed by a computer perform any of the methods of Example Embodiments Cl to C21.

Group D Example Embodiments

Example Embodiment DI. A method by a second network node for signaling DTRX information, the method comprising: receiving, from a first network node, first DTRX information associated with at least one of a DTRX pattern and/or cycle that is employed or to be employed at or by the first network node.

Example Embodiment D2. The method of Example Embodiment DI, comprising transmitting, to the first network node, a request for the first DTRX information, wherein the first DTRX information is received based on the request.

Example Embodiment D3. The method of any one of Example Embodiments DI to D2, comprising transmitting second DTRX information to the first network node, the second DTRX information comprising at least a portion of a DTRX pattern and/or cycle proposed to be employed at or by the first network node.

Example Embodiment D4. The method of Example Embodiment D3, comprising receiving, from the first network node, an indication of an acceptance or a rejection of the second DTRX information transmitted to the first network node.

Example Embodiment D5. The method of Example Embodiment D4, wherein the indication is a rejection of the second DTRX information, and the method comprises receiving third DTRX information from the first network node, the third DTRX information comprising a counterproposal of at least a portion of a DTRX pattern and/or cycle to be employed at or by the first network node.

Example Embodiment D6. The method of any one of Example Embodiments DI to D5, wherein at least one of the first DTRX information, the second DTRX information, and the third DTRX information comprises at least one of: an on-duration timer; a DTRX long cycle; a DTX long cycle and/or DRX long cycle; a DTRX short cycle; a DTX short cycle and/or DRX short cycle; a DTRX inactivity timer; a DTRX long cycle start offset; a DTX long cycle start offset and/or a DRX long cycle start offset; an indication associated with a time or time period for employing the first, second, and/or third DTRX information; an indication of a load or traffic metric during which the first, second, and/or third DTRX information is to be employed; an indication of whether the first network node or a component of the first network node may transmit a communication during an off time associated with the first, second, and/or third DTRX information; and an indication of whether the first network node or a component of the first network node may receive a communication during an off time associated with the first, second, and/or third DTRX information.

Example Embodiment D7. The method of any one of Example Embodiments DI to D6, wherein the first network node is a RAN node and the second network node is a RAN node, and the first DTRX information is received in a NG-RAN NODE CONFIGURATION UPDATE message.

Example Embodiment D8. The method of Example Embodiment D7, wherein at least one of the first DTRX information, the second DTRX information, and the third DTRX information is transmitted to and/or received from the first network node via a Xn interface or an X2 interface.

Example Embodiment D9. The method of Example Embodiment D7, wherein at least one of the first DTRX information, the second DTRX information, and the third DTRX information is transmitted to and/or received from the first network node via a core network node.

Example Embodiment DIO. The method of any one of Example Embodiments DI to D6, wherein the first network node is a RAN node and the second network node is a Core network node.

Example Embodiment Dll. The method of Example Embodiment DIO, wherein and the first DTRX information is received in a NG SETUP REQUEST message or a RAN CONFIGURATION UPDATE message.

Example Embodiment DI 2. The method of any one of Example Embodiments DI to DIO, wherein: the first network node is a first logical entity of a first RAN node, and the second network node is a second logical entity of a second RAN node.

Example Embodiment DI 3. The method of any one of Example Embodiments DI to DIO, wherein: the first network node is a first logical entity of a first RAN node, and the second network node is a second logical entity of the first RAN node.

Example Embodiment D14. The method of any one of Example Embodiments DI to DIO, wherein: the first network node is a DU of a first RAN node, and the second network node is a CU of a second RAN node.

Example Embodiment D15. The method of any one of Example Embodiments DI to DIO, wherein: the first network node is a U) of a first RAN node, and the second network node is a CU of the first RAN node.

Example Embodiment DI 6. The method of any one of Example Embodiments DI to DIO, wherein: the first network node is a CU of a first RAN node, and the second network node is a DU of a second RAN node.

Example Embodiment DI 7. The method of any one of Example Embodiments DI to DIO, wherein: the first network node is a first CU of a first RAN node, and the second network node is a DU of the first RAN node.

Example Embodiment DI 8. The method of any one of Example Embodiments DI to DIO, wherein: the first network node is a CU of a first RAN node, and the second network node is a CU of a second RAN node.

Example Embodiment DI 9. The method of any one of Example Embodiments DI to DIO, wherein: the first network node is a DU of a first RAN node, and the second network node is a DU of a second RAN node.

Example Embodiment D20. The method of any one of Example Embodiments DI to DI 9, wherein the second network node operates as a group leader with respect to the first network node and at least one additional network node in aNES coordination group.

Example Embodiment D21. The method of Example Embodiment D20, comprising: receiving, from a third network node, fourth DTRX information associated with at least one of a DTRX pattern and/or cycle that is employed or to be employed at or by the third network node; and performing coordination between the first network node and the second network node to minimize conflict between the first DTRX information and the fourth DTRX information.

Example Embodiment D22. The method of Example Embodiment D20 and D21, wherein performing coordination between the first network node and the second network node comprises determining that the first DTRX information and the fourth DTRX information conflict.

Example Embodiment D23. The method of Example Embodiment D3 and D22, wherein the second DTRX information, which is transmitted to the first network node, is based on determining that the first DTRX information and the fourth DTRX information conflict.

Example Embodiment D24. The method of any of Example Embodiments DI to D23, further comprising: obtaining user data; and forwarding the user data to a host or a user equipment.

Example Embodiment D25. A network node comprising processing circuitry configured to perform any of the methods of Example Embodiments DI to D24.

Example Embodiment D26. A computer program comprising instructions which when executed on a computer perform any of the methods of Example Embodiments DI to D24.

Example Embodiment D27. A computer program product comprising computer program, the computer program comprising instructions which when executed on a computer perform any of the methods of Example Embodiments DI to D24.

Example Embodiment D28. A non-transitory computer readable medium storing instructions which when executed by a computer perform any of the methods of Example Embodiments DI to D24.

Group E Example Embodiments

Example Embodiment El. A user equipment for signaling DTRX information, comprising: processing circuitry configured to perform any of the steps of any of the Group A Example Embodiments; and power supply circuitry configured to supply power to the processing circuitry. Example Embodiment E2. A network node for signaling DTRX information, the network node comprising: processing circuitry configured to perform any of the steps of any of the Group B, C, and D Example Embodiments; power supply circuitry configured to supply power to the processing circuitry.

Example Embodiment E3. A user equipment (UE) for signaling DTRX information, the UE comprising: an antenna configured to send and receive wireless signals; radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry; the processing circuitry being configured to perform any of the steps of any of the Group A Example Embodiments; an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry; an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and a battery connected to the processing circuitry and configured to supply power to the UE.

Example Embodiment E4. 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 cellular network for transmission to a user equipment (UE), wherein the UE comprises a communication interface and processing circuitry, the communication interface and processing circuitry of the UE being configured to perform any of the steps of any of the Group A Example Embodiments to receive the user data from the host.

Example Embodiment E5. The host of the previous Example Embodiment, wherein the cellular network further includes a network node configured to communicate with the UE to transmit the user data to the UE from the host.

Example Embodiment E6. The host of the previous 2 Example Embodiments, 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.

Example Embodiment E7. A method implemented by a host operating 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 UE performs any of the operations of any of the Group A embodiments to receive the user data from the host. Example Emboidment E8. The method of the previous Example Embodiment, further comprising: at the host, executing a host application associated with a client application executing on the UE to receive the user data from the UE.

Example Embodiment E9. The method of the previous Example Embodiment, further comprising: at the host, transmitting input data to the client application executing on the UE, the input data being provided by executing the host application, wherein the user data is provided by the client application in response to the input data from the host application.

Example Emboidment E10. 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 cellular network for transmission to a user equipment (UE), wherein the UE comprises a communication interface and processing circuitry, the communication interface and processing circuitry of the UE being configured to perform any of the steps of any of the Group A Example Embodiments to transmit the user data to the host.

Example Emboidment Ell. The host of the previous Example Embodiment, wherein the cellular network further includes a network node configured to communicate with the UE to transmit the user data from the UE to the host.

Example Embodiment El 2. The host of the previous 2 Example Embodiments, 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.

Example Embodiment El 3. 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, receiving user data transmitted to the host via the network node by the UE, wherein the UE performs any of the steps of any of the Group A Example Embodiments to transmit the user data to the host.

Example Embodiment E14. The method of the previous Example Embodiment, further comprising: at the host, executing a host application associated with a client application executing on the UE to receive the user data from the UE.

Example Embodiment El 5. The method of the previous Example Embodiment, further comprising: at the host, transmitting input data to the client application executing on the UE, the input data being provided by executing the host application, wherein the user data is provided by the client application in response to the input data from the host application. Example Embodiment E16. 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, C, and D Example Embodiments to transmit the user data from the host to the UE.

Example Embodiment El 7. The host of the previous Example 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.

Example Embodiment El 8. 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, C, and D Example Embodiments to transmit the user data from the host to the UE.

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

Example Emboidment E20. The method of any of the previous 2 Example 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.

Example Embodiment E21. 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, C, and D Example Embodiments to transmit the user data from the host to the UE.

Example Embodiment E22. The communication system of the previous Example Embodiment, further comprising: the network node; and/or the user equipment. Example Embodiment E23. 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, C, and D Example Embodiments to receive the user data from a user equipment (UE) for the host.

Example Embodiment E24. The host of the previous 2 Example Embodiments, 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.

Example Embodiment E25.The host of the any of the previous 2 Example Embodiments, wherein the initiating receipt of the user data comprises requesting the user data.

Example Embodiment E26. 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, C, and D Example Embodiments to receive the user data from the UE for the host.

Example Embodiment E27. The method of the previous Example Embodiment, further comprising at the network node, transmitting the received user data to the host.

Claims

1. A method (1600) by a first network node (102, 302) for signaling Discontinuous Transmission and/or Reception, DTRX, information, the method comprising: transmitting (1602), to a second network node (104, 304), first DTRX information (120, 320) associated with at least one of a DTRX pattem/cycle that is employed and a DTRX pattem/cycle that is to be employed at or by the first network node.

2. The method of Claim 1, comprising receiving, from the second network node, a request for the first DTRX information, wherein the first DTRX information is transmitted to the second network node based on the request.

3. The method of any one of Claims 1 to 2, comprising receiving second DTRX information from the second network node, the second DTRX information comprising at least a portion of a DTRX pattern and/or cycle proposed to be employed at or by the first network node.

4. The method of Claim 3, comprising: determining whether to employ the second DTRX information received from the second network node; and transmitting, to the second network node, an indication of an acceptance or a rejection of the second DTRX information received from the second network node.

5. The method of Claim 4, wherein the indication is a rejection of the second DTRX information, and the method comprises transmitting third DTRX information to the second network node, the third DTRX information comprising a counterproposal of at least a portion of a DTRX pattern and/or cycle to be employed at or by the first network node.

6. The method of any one of Claims 1 to 5, wherein at least one of the first DTRX information, the second DTRX information, and the third DTRX information comprises at least one of: an on-duration timer; a DTX and/or DRX cycle duration; a DTRX inactivity timer; a DTX and/or a DRX cycle start offset; and an indication associated with a time or time period for employing the first, second, and/or third DTRX information.

7. The method of any one of Claims 1 to 6, wherein at least one of the first DTRX information, the second DTRX information, and the third DTRX information comprises at least one of: an indication of a load or traffic metric during which the first, second, and/or third DTRX information is to be employed; an indication of whether the first network node or a component of the first network node may transmit a communication during an off time associated with the first, second, and/or third DTRX information; and an indication of whether the first network node or a component of the first network node may receive a communication during an off time associated with the first, second, and/or third DTRX information.

8. The method of any one of Claims 1 to 7, wherein: the first network node is a first Radio Access Network, RAN, node, the second network node is a second RAN node, and at least one of the first DTRX information, the second DTRX information, and the third DTRX information is transmitted to and/or received from the second network node via an Xn interface or an X2 interface.

9. The method of any one of Claims 1 to 7, wherein: the first network node is a first logical entity of a first Radio Access Network, RAN, node, the second network node is a second logical entity of a second RAN node, and at least one of the first DTRX information, the second DTRX information, and the third DTRX information is transmitted to and/or received from the second logical entity of the second network node via an Xn interface or an X2 interface.

10. The method of Claim 9, wherein: the first logical entity is a first Central Unit, CU, of the first RAN node, and the second logical entity is a second CU of the second RAN node.

11. The method of any one of Claims 8 to 10, wherein at least one of the first DTRX information and the third DTRX information is transmitted in a NG-RAN NODE CONFIGURATION UPDATE message.

12. The method of any one of Claims 1 to 7, wherein: the first network node is a first Radio Access Network, RAN, node, the second network node is a second RAN node, and at least one of the first DTRX information, the second DTRX information, and the third DTRX information is transmitted to and/or received from the second network node via a core network node.

13. The method of any one of Claims 1 to 7, wherein: the first network node is a first logical entity of a first RAN node, the second network node is a second logical entity of the first RAN node, and at least one of the first DTRX information, the second DTRX information, and the third DTRX information is transmitted to and/or received from the second network node via an Fl interface.

14. The method of Claim 13, wherein: the first logical entity is a distributed unit, DU, of the first RAN node, and the second logical entity is a Central Unit, CU, of the first RAN node.

15. The method of Claim 13, wherein: the first logical entity is a Central Unit, CU, of the first RAN node, and the second logical entity is a first distributed unit, DU, of the first RAN node, and prior to transmitting the first DTRX information to the second logical entity, the first logical entity receives the first DTRX information from a third logical entity that is a second DU of the first RAN node.

16. The method of any one of Claims 1 to 7, wherein: the first network node is a RAN node, the second network node is a Core network node, and the first DTRX information is transmitted in a NG SETUP REQUEST message or a RAN CONFIGURATION UPDATE message.

17. The method of any one of Claims 1 to 16, wherein the second network node operates as a group leader with respect to the first network node and at least one additional network node in a Network Energy Saving, NES, coordination group.

18. A method (1700) by a second network node (104, 304) for signaling Discontinuous Transmission and/or Reception, DTRX, information, the method comprising: receiving (1702), from a first network node (102, 302), first DTRX information (120, 320) associated with at least one of a DTRX pattem/cycle that is employed and a DTRX pattem/cycle that is to be employed at or by the first network node.

19. The method of Claim 18, comprising transmitting, to the first network node, a request for the first DTRX information, wherein the first DTRX information is received based on the request.

20. The method of any one of Claims 18 to 19, comprising transmitting second DTRX information to the first network node, the second DTRX information comprising at least a portion of a DTRX pattern and/or cycle proposed to be employed at or by the first network node.

21. The method of any one of Claims 18 to 19, comprising: receiving, from a third network node, fourth DTRX information associated with at least one of a DTRX pattem/cycle that is employed and a DTRX pattem/cycle that is to be employed at or by the third network node; and performing coordination between the first network node and the third network node to minimize conflict between the first DTRX information and the fourth DTRX information.

22. The method of Claim 21, wherein: performing coordination between the first network node and the third network node comprises determining that the first DTRX information and the fourth DTRX information conflict, and based on determining that the first DTRX information and the fourth DTRX information conflict, transmitting second DTRX information to the first network node, the second DTRX information comprising at least a portion of a DTRX pattern and/or cycle proposed to be employed at or by the first network node.

23. The method of any one of Claims 20 to 22, comprising receiving, from the first network node, an indication of an acceptance or a rejection of the second DTRX information transmitted to the first network node.

24. The method of Claim 23, wherein the indication is a rejection of the second DTRX information, and the method comprises receiving third DTRX information from the first network node, the third DTRX information comprising a counterproposal of at least a portion of a DTRX pattern and/or cycle to be employed at or by the first network node.

25. The method of any one of Claims 18 to 24, wherein at least one of the first DTRX information, the second DTRX information, the third DTRX information, and the fourth DTRX information comprises at least one of: an on-duration timer; a DTX and/or DRX cycle duration; a DTRX inactivity timer; a DTX and/or a DRX cycle start offset; and an indication associated with a time or time period for employing the first, second, third, and/or fourth DTRX information.

26. The method of any one of Claims 18 to 25, wherein at least one of the first DTRX information, the second DTRX information, the third DTRX information, and the fourth DTRX information comprises at least one of: an indication of a load or traffic metric during which the first, second, third, and/or fourth DTRX information is to be employed; an indication of whether the first network node or a component of the first network node may transmit a communication during an off time associated with the first, second, third, and/or fourth DTRX information; and an indication of whether the first network node or a component of the first network node may receive a communication during an off time associated with the first, second, third, and/or fourth DTRX information.

27. The method of any one of Claims 18 to 26, wherein: the first network node is a first Radio Access Network, RAN, node, the second network node is a second RAN node, and at least one of the first DTRX information, the second DTRX information, the third DTRX information, and the fourth DTRX information is transmitted to and/or received from the second network node via an Xn interface or an X2 interface.

28. The method of any one of Claims 18 to 26, wherein: the first network node is a first logical entity of a first Radio Access Network, RAN, node, the second network node is a second logical entity of a second RAN node, and at least one of the first DTRX information, the second DTRX information, the third DTRX information, and the fourth DTRX information is transmitted to and/or received from the second logical entity of the second network node via an Xn interface or an X2 interface.

29. The method of Claim 28, wherein: the first logical entity is a first Central Unit, CU, of the first RAN node, and the second logical entity is a second CU of the second RAN node.

30. The method of any one of Claims 28 to 29, wherein at least one of the first DTRX information and the third DTRX information is received in aNG-RAN NODE CONFIGURATION UPDATE message.

31. The method of any one of Claims 18 to 26, wherein: the first network node is a first Radio Access Network, RAN, node, the second network node is a second RAN node, and at least one of the first DTRX information, the second DTRX information, the third DTRX information, and the fourth DTRX information is transmitted to and/or received from the first network node via a core network node.

32. The method of any one of Claims 18 to 26, wherein: the first network node is a first logical entity of a first RAN node, the second network node is a second logical entity of the first RAN node, and at least one of the first DTRX information, the second DTRX information, the third DTRX information, and the fourth DTRX information is transmitted to and/or received from the second network node via an Fl interface.

33. The method of Claim 31, wherein: the first logical entity is a distributed unit, DU, of the first RAN node, and the second logical entity is a Central Unit, CU, of the first RAN node.

34. The method of Claim 32, wherein: the first logical entity is a Central Unit, CU, of a first RAN node, and the second logical entity is a Distributed Unit, DU, of the first RAN node, and the first DTRX information is associated with a third logical entity that is a second DU of the first RAN node and is received via the first logical entity.

35. The method of any one of Claims 18 to 26, wherein: the first network node is a RAN node, the second network node is a Core network node, and the first DTRX information is received in a NG SETUP REQUEST message or a RAN CONFIGURATION UPDATE message.

36. The method of any one of Claims 18 to 35, wherein the second network node operates as a group leader with respect to the first network node and at least one additional network node in a Network Energy Saving, NES, coordination group.

37. A first network node (102, 302, 1200) for signaling Discontinuous Transmission and/or Reception, DTRX, information (120, 320), the first network node comprising processing circuitry (1202) configured to: transmit, to a second network node (104, 304, 1200), first DTRX information associated with at least one of a DTRX pattem/cycle that is employed and a DTRX pattem/cycle that is to be employed at or by the first network node.

38. The first network node of Claim 37, wherein the processing circuitry is configured to perform any of the methods of Claims 2 to 17.

39. A second network node (104, 304, 1200) for signaling Discontinuous Transmission and/or Reception, DTRX, information (120, 320), the second network node comprising processing circuitry configured to: receive, from a first network node (102, 302, 1200), first DTRX information associated with at least one of a DTRX pattem/cycle that is employed and a DTRX pattem/cycle that is to be employed at or by the first network node.

40. The second network node of Claim 39, wherein the processing circuitry is configured to perform any of the methods of Claims 19 to 36.