Energy cost reduction of network slices

Abstract

A method includes receiving, by a distributed unit of an NG-RAN node (gNB-DU), a first message, the first message including a request for reporting an energy cost per network slice. The gNB-DU selects one or more user equipments (UEs), and transmits a second message to a central unit of the same NG-RAN node (gNB-CU), the second message including a report of the energy cost per network slice for the one or more UEs. The energy cost may be measured or predicted per UE and used to determine an energy saving action.

Description

FIELD

[0001] Various example embodiments relate generally to wireless networks and, more particularly, to support for anticipated resource management between slices. BACKGROUND

[0002] The third generation partnership project (3GPP) provides requirements (e.g., in TS 22.261) on energy saving related aspects to enable operators to save energy. Since best-effort traffic does not have any performance guarantees, policies can be defined to limit the energy consumption for those services related to best-effort traffic.

[0003] A slice may become more energy demanding because the reserved time and frequency resources are fully used. For example, depending on the quality of service (QoS) (e.g., higher QoS, with more stringent traffic-handling requirements) served by the slice, the energy consumed may be higher than for other slices serving a different QoS (e.g., lower QoS, with less stringent traffic-handling requirements). If time / frequency resources allocated to the slice are getting more fully loaded, energy demand may increase since a node may need to transmit at higher power in order to accommodate the additional traffic. SUMMARY

[0004] In an aspect of the present disclosure, a method includes receiving, by a first apparatus, a first message, the first message including a request for reporting an energy cost per network slice, selecting, by the first apparatus, one or more user equipments (UEs), and transmitting, by the first apparatus, a second message to a second apparatus, the second message including a report of the energy cost per network slice for the one or more UEs.

[0005] In an aspect of the method, the first message is received from a second apparatus.

[0006] In an aspect of the method, the first message includes a request for the energy cost per network slice for at least a first UE of the one or more UEs, and wherein the second message includes a report for the energy cost per network slice for the first UE of the one or more UEs.

[0007] In an aspect of the method, the report includes the energy cost for a plurality of network slices.

[0008] In an aspect of the method, selecting the one or more UEs includes receiving, by the first apparatus, in the first message, an action associated with the energy cost per network slice, receiving, by the first apparatus, a third message associated with a UE corresponding to the action requested m the first message, and selecting the one or more UEs for the transmission of the second message based upon the first message and the third message.

[0009] In an aspect of the method, selecting the one or more UEs includes receiving, by the first apparatus, in the first message an identifier of one or more UEs, and selecting the UEs for the transmission of the second message based upon the identifier of one or more UEs.

[0010] In an aspect of the method, the second message includes a report of the energy cost per network slice per cell over a list of cells for the one or more UEs.

[0011] In an aspect of the method, the list of cells is received in the first message.

[0012] In an aspect of the method, the list of cells corresponds to cells which have been used as Primary Secondary Cells (PSCells) by the first apparatus for the one or more UEs in a dual connectivity scheme where the secondary apparatus acted as master node.

[0013] In an aspect of the method, the reported energy cost per network slice corresponds to an energy cost per cell over a list of cells used for carrier aggregation for the one or more UEs.

[0014] In an aspect of the method, the method further includes receiving in the first message a list of one or more slices, and reporting in the second message the energy cost for the one or more UEs for each slice included in the received list of slices.

[0015] In an aspect of the method, the request for the energy cost per network slice is a request for a measured energy cost per UE or a request for a predicted energy cost per UE.

[0016] In an aspect of the method, the first apparatus is a first next generation radio access network (NG-RAN) node and the second apparatus is a second NG-RAN node.

[0017] In an aspect of the method, the first apparatus is a Distributed Unit of an NG-RAN node (gNB-DU) and the second apparatus is the Central Unit of the same NG-RAN node (gNB-CU).

[0018] In an aspect of the method, the first apparatus transmits the second message to the second apparatus periodically.

[0019] In an aspect of the method, the period for sending the second message is received in the first message.

[0020] In an aspect of the method, the method further includes receiving, by the second apparatus from the first apparatus, the second message including a report of the energy cost per network slice for the one or more UEs, and performing, by the second apparatus based on the received report, at least one energy saving action concerning the one or more UEs.

[0021] In an aspect of the present disclosure, an apparatus includes at least one processor, and at least one memory storing instructions which, when executed by the at least one processor, cause the apparatus at least to perform any of the foregoing methods.

[0022] In an aspect of the present disclosure, a processor-readable medium storing instructions which, when executed by at least one processor of an apparatus, cause the apparatus at least to perform any of the foregoing methods.

[0023] According to some aspects, there is provided the subject matter of the independent claims. Some further aspects are defined in the dependent claims. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] Some example embodiments will now be described with reference to the accompanying drawings.

[0025] FIG. 1 is a diagram of an example embodiment of wireless networking between a network system and a user equipment (UE), according to one illustrated aspect of the disclosure;

[0026] FIG. 2 is a diagram of example components of a network system, according to one illustrated aspect of the disclosure;

[0027] FIG. 3 is a diagram of an example artificial intelligence (AI) machine learning (ML) (AI / ML) model for next generation radio access network (NG-RAN) energy saving, according to one illustrated aspect of the disclosure;

[0028] FIG. 4 is a diagram of an example embodiment of signals and operations among UE, gNB-CU-CP and gNB-DU, according to one illustrated aspect of the disclosure;

[0029] FIG. 5 is a diagram of an example embodiment of signals and operations among UE, gNB-CU-CP and gNB-DU, according to another illustrated aspect of the disclosure;

[0030] FIG. 6 is a diagram of an example embodiment of signals and operations among UE, gNB-CU-CP and gNB-DU, according to another illustrated aspect of the disclosure;

[0031] FIG. 7 is a diagram of an example embodiment of signals and operations among a UE and NG-RANs, according to one illustrated aspect of the disclosure;

[0032] FIG. 8 is a diagram of an example embodiment of signals and operations among a UE and NG-RANs, according to another illustrated aspect of the disclosure;

[0033] FIG. 9 is a diagram of an example embodiment of signals and operations among UE, gNB-CU-CP and gNB-DU, according to another illustrated aspect of the disclosure;

[0034] FIG. 10 is a diagram of an example embodiment of signals and operations among a UE and NG-RANs, according to another illustrated aspect of the disclosure; and

[0035] FIG. 11 is a diagram of an example embodiment of components of a UE or of a network apparatus, according to one illustrated aspect of the present disclosure. DETAILED DESCRIPTION

[0036] In the following description, certain specific details are set forth in order to provide a thorough understanding of disclosed aspects. However, one skilled in the relevant art will recognize that aspects may be practiced without one or more of these specific details or with other methods, components, materials, etc. In other instances, well-known structures associated with transmitters, receivers, or transceivers have not been shown or described in detail to avoid unnecessarily obscuring descriptions of the aspects.

[0037] Reference throughout this specification to “one aspect” or “an aspect” means that a particular feature, structure, or characteristic described in connection with the aspect is included in at least one aspect. Thus, the appearances of the phrases “in one aspect” or “in an aspect” in various places throughout this specification are not necessarily all referring to the same aspect. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more aspects.

[0038] Embodiments described in the present disclosure may be implemented in wireless networking apparatuses, such as, without limitation, apparatuses utilizing Worldwide Interoperability' for Microwave Access (WiMAX), Global System for Mobile communications (GSM, 2G), GSM EDGE radio access Network (GERAN), General Packet Radio Service (GRPS), Universal Mobile Telecommunication System (UMTS, 3G) based on basic wideband-code division multiple access (W-CDMA), high-speed packet access (HSPA), Long Term Evolution (LTE), LTE-Advanced, enhanced LTE (eLTE), 5G New Radio (5G NR), 5G Advance, 6G (and beyond) and 802.1 lax (Wi-Fi 6), among other wireless networking systems. The term ‘eLTE’ here denotes the LTE evolution that connects to a 5G core. LTE is also known as evolved UMTS terrestrial radio access (EUTRA) or as evolved UMTS terrestrial radio access network (EUTRAN).

[0039] The present disclosure may use the term “serving network device” to refer to a network node or network device (or a portion thereof) that services a UE. As used herein, the terms “transmit to,” “receive from,” and “cooperate with,” (and their variations) include communications that may or may not involve communications through one or more intermediate devices or nodes. The term “acquire” (and its variations) includes acquiring in the first instance or reacquiring after the first instance. The term “connection” may mean a physical connection or a logical connection.

[0040] The present disclosure uses 5G NR as an example of a wireless network and may use smartphones and / or extended reality headsets as an example of UEs. It is intended and shall be understood that such examples are merely illustrative, and the present disclosure is applicable to other wireless networks and user equipment.

[0041] FIG. 1 is a diagram depicting an example of wireless networking between a network system 100 and a user equipment (UE) 150. The network system 100 may include one or more network nodes 120, one or more servers 110, and / or one or more network equipment 130 (e.g., test equipment). The network nodes 120 will be described in more detail below. As used herein, the term “network apparatus” may refer to any component of the network system 100, such as the server 110, the network node 120, the network equipment 130, any component(s) of the foregoing, and / or any other component(s) of the network system 100. Examples of network apparatuses include, without limitation, apparatuses implementing aspects of 5G NR, among others. The present disclosure describes embodiments related to 5G NR and embodiments that involve aspects defined by 3rd Generation Partnership Project (3GPP). However, it is contemplated that embodiments relating to other wireless networking technologies are encompassed within the scope of the present disclosure.

[0042] The following description provides further details of examples of network nodes. In a 5G NR network, a gNodeB (also known as gNB) may include, e.g., a node that provides new radio (NR) user plane and control plane protocol terminations towards the LTE and that is connected via a NG interface to the 5G core (5GC), e.g., according to 3GPP TS 38.300 ¥16.6.0 (2021-06) section 3.2, which is hereby incorporated by reference herein.

[0043] A gNB supports various protocol layers, e.g., Layer 1 (LI) - physical layer. Layer 2 (L2), and Layer 3 (L3).

[0044] The layer 2 (L2) of NR is split into the following sublayers: Medium Access Control (MAC), Radio Link Control (RLC), Packet Data Convergence Protocol (PDCP) and Service Data Adaptation Protocol (SDAP), where, e.g.: o The physical layer offers to the MAC sublayer transport channels; o The MAC sublayer offers to the RLC sublayer logical channels; o The RLC sublayer offers to the PDCP sublayer RLC channels; o The PDCP sublayer offers to the SDAP sublayer radio bearers; o The SDAP sublayer offers to 5GC quality of service (QoS) flows; o Control channels include broadcast control channel (BCCH) and physical control channel (PCCH).

[0045] Layer 3 (L3) includes, e.g., radio resource control (RRC), e.g., according to 3GPP TS 38.300 VI 6.6.0 (2021-06) section 6, which is hereby incorporated by reference herein.

[0046] A gNB central unit (gNB-CU) includes, e.g., a logical node hosting, e.g., radio resource control (RRC), service data adaptation protocol (SDAP), and packet data convergence protocol (PDCP) protocols of the gNB or RRC and PDCP protocols of the en-gNB, that controls the operation of one or more gNB distributed units (gNB-DUs). The gNB-CU terminates the Fl interface connected with the gNB-DU A gNB-CU may also be referred to herein as a CU, a central unit, a centralized unit, or a control unit.

[0047] A gNB Distributed Unit (gNB-DU) includes, e.g., a logical node hosting, e.g., radio link control (RLC), media access control (MAC), and physical (PHY) layers of the gNB or en-gNB, and its operation is partly controlled by the gNB-CU. One gNB-DU supports one or multiple cells. One cell is supported by only one gNB-DU. The gNB-DU terminates the Fl interface connected with the gNB-CU. A gNB-DU may also be referred to herein as DU or a distributed unit.

[0048] As used herein, the term “network node” may refer to any of a gNB, a gNB-CU, or a gNB-DU, or any combination of them. A RAN (radio access network) node or network node such as, e.g., a gNB, gNB-CU, or gNB-DU, or parts thereof, may be implemented using, e.g., an apparatus with at least one processor and / or at least one memory with processor-readable instructions (“program”) configured to support and / or provision and / or process CU and / or DU related functionality and / or features, ami / or at least one protocol (sub-)layer of a RAN (radio access network), e.g., layer 2 and / or layer 3. Different functional splits between the central and distributed unit are possible. An example of such an apparatus and components will be described in connection with FIG. 11 below.

[0049] The gNB-CU and gNB-DU parts may, e.g., be co-located or physically separated. The gNB-DU may even be split further, e.g., into two parts, e.g., one including processing equipment and one including an antenna. A central unit (CU) may also be called baseband unit / radio equipment controller cloud-RAN / virtual-RAX (BBU / REC / C-RAN / V-RAN), open-RAN (O-RAN), or part thereof. A distributed unit (DU) may also be called remote radio head / remote radio unit / radio equipment / radio unit (RRH / RRU / RE / RU), or part thereof. Hereinafter, in various example embodiments of the present disclosure, a network node, which supports at least one of central unit functionality or a layer 3 protocol of a radio access network, may be, e.g., a gNB-CU. Similarly, a network node, which supports at least one of distributed unit functionality or a layer 2 protocol of the radio access network, may be, e.g., a gNB-DU.

[0050] A gNB-CU may support one or multiple gNB-DUs. A gNB-DU may support one or multiple cells and, thus, could support a serving cell for a user equipment (UE) or support a candidate cell for handover, dual connectivity, and / or carrier aggregation, among other procedures.

[0051] The user equipment (UE) 150 may be or include a wireless or mobile device, an apparatus with a radio interface to interact with a RAN (radio access network), a smartphone, an in-vehicle apparatus, an loT device, or a M2M device, among other types of user equipment. Such UE 150 may include: at least one processor; and at least one memory including program code; where the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus at least to perform certain operations, such as, e.g., RRC connection to the RAN. An example of components of a UE will be described in connection with FIG. 11. In embodiments, the UE 150 may be configured to generate a message (e.g., including a cell ID) to be transmitted via radio towards a RAN (e.g., to reach and communicate with a serving cell). In embodiments, the UE 150 may generate and transmit and receive RRC messages containing one or more RRC PDUs (packet data units). Persons skilled in the art will understand RRC protocol as well as other procedures a UE may perform.

[0052] With continuing reference to FIG. 1, in the example of a 5G NR network, the network system 100 provides one or more cells, which define a coverage area of the network system 100. As described above, the network system 100 may include a gNB of a 5G NR network or may include any other apparatus configured to control radio communication and manage radio resources within a cell. As used herein, the term “resource” may refer to radio resources, such as a resource block (RB), a physical resource block (PRB), a radio frame, a subframe, a time slot, a sub-band, a frequency region, a sub-carrier, a beam, etc. In embodiments, the network node 120 may be called a base station.

[0053] FIG. 1 provides an example and is merely illustrative of a network system 100 and a UE 150. Persons skilled in the art will understand that the network system 100 includes components not illustrated in FIG. 1 and will understand that other user equipment may be in communication with the network system 100.

[0054] FIG. 2 is a block diagram of example components of the network system 100 of FIG. 1. A 5G NR network may be described as an example of the network system 100, and it is intended that aspects of the following description shall be applicable to other types of network systems, as well. The network system may operate in accordance with the signals and connections shown in FIG. I such that tire UE 150 is in communication with the network system 100 through the radio access network 225. Additionally, the network system may be divided into user plane components and functions and control plane components and functions, as shown and described herein. Unless indicated otherwise, the terms “component”, “function”, and “service” may be used interchangeably herein, and they may refer to and be implemented by instructions executed by one or more processors.

[0055] Example functions of the components are described below. The example functions are merely illustrative, and it shall be understood that additional operations and functions may be performed by the components described herein. Additionally, the connections between components may be virtual connections over service-based interfaces such that any component may communicate with any other component. In this manner, any component may act as a service “producer,” for any other component that is a service “consumer,” to provide services for network functions.

[0056] For example, a core network 210 is described in the control plane of the network system. The core network 210 may include an authentication server function (AUSF) 211, an access and mobility function (AMF) 212, and a session management function (SMF) 213. The core network 210 may also include a network slice selection function (NSSF) 214, a network exposure function (NEF) 215, a network repository function (NRF) 216, and a unified data management function (UDM) 217, which may include a uniform data repository (UDR) 224.

[0057] Additional components and functions of the core network 210 may include an application function 218, policy control function (PCF) 219, network data analytics function (NWDAF) 220, analytics data repository function (ADRF) 221, management data analytics function (MDAF) 222, and operations and management function (0AM.) 223.

[0058] The user plane includes the UE 150, a radio access network (RAN) 225, a user plane function (UPF) 226, and a data network (DN) 227. The RAN 225 may include one or more components described m connection with FIG. 1, such as one or more network nodes. However, the RAN 225 may not be limited to such components. The UPF 226 provides connection for data being transmitted over the RAN 225. The DN 226 identifies services from service providers, Internet access, and third party services, for example.

[0059] The AMF 212 processes connection and mobility tasks. The AUSF 211 receives authentication requests from the AMF 212 and interacts with UDM 217 to authenticate and validate network responses for determination of successful authentication. The SMF 213 conducts packet data unit (PDU) session management, as well as manages session context with the UPF 226.

[0060] The NSSF 214 may select a network slicing instance (NSI) and determine the allowed network slice selection assistance information (NSSAI). This selection and determination is utilized to set the AMF 212 to provide sendee to the UE 150. The NEF 215 secures access to network services for third parties to create specialized network services. The NRF 216 acts as a repository to store network functions to allow the functions to register with and discover each other.

[0061] The UDM 217 generates authentication vectors for use by the AUSF 211 and ADM 212 and provides user identification handling. The UDM 217 may be connected to the UDR 224 which stores data associated with authentication, applications, or the like. The AF 218 provides application services to a user (e.g., streaming services, etc.). The PCF 219 provides policy control functionality. For example, the PCF 219 may assist in network slicing and mobility management, as well as provide quality of service (QoS) and charging functionality.

[0062] The NWDAF 220 collects data (e.g., from the UE 150 and the network system) to perform network analytics and provide insight to functions that utilize the analytics m the providing of services. The ADRF 221 allows the storage, retrieval, and removal of data and analytics by consumers. The MDAF 222 provides additional data analytics services for network functions. The 0AM 223 provides provisioning and management processing functions to manage elements in or connected to the network (e.g., UE 150, network nodes, etc.).

[0063] FIG. 2 is merely an example of components of a network system, and variations are contemplated to be within the scope of the present disclosure. In embodiments, the network system may include other components not illustrated in FIG. 2. In embodiments, the network system may not include every component illustrated in FIG. 2. In embodiments, the components and connections may be implemented with different connections than those illustrated in FIG. 2. Such and other embodiments are contemplated to be within the scope of the present disclosure.

[0064] Although further detail will be provided below, described herein is a method to enable a RAN (e.g., NG-RAN) to adapt its actions to satisfy the energy-related requirements (e.g., as specified in TS 22.261). In various embodiments, the method relies on the use of a Network Energy Cost metric on the used slice defined over different granularities.

[0065] As mentioned above, a slice (e.g., network slice) may become more energy demanding because the reserved time and frequency resources are fully used. For example, depending on the QoS (higher QoS, with more stringent traffic-handling requirements) served by the slice, the energy consumed may be higher than for other slices serving a different QoS (lower QoS, with less stringent traffic-handling requirements). This may be especially true if time / frequency resources allocated to the slice are getting more fully loaded since a node may need to transmit at higher power in order to accommodate the additional traffic.

[0066] In various embodiments, a slice may be uniquely identified via S-NSSAI (SingleNetwork Slice Selection Assistance Information), which may be appreciated by those skilled in the art. NSSAI (Network Slice Selection Assistance Information) includes one or a list of S-NSSAIs.

[0067] Accordingly, described herein is a method of optimizing the energy cost of slice operation. This problem can be addressed both in the RAN and in the core network. Specifically, in case of RAN optimization, the NG-RAN node has some means to reduce the energy cost required to operate the NG-RAN part of network slices. These means include, for example: moving UEs between frequency layers; start / stop carrier aggregation or add / remove SCells for carrier aggregation for one or more UEs; modify QoS parameters e.g. maximum bit rate for one or more UEs; start / stop Dual Connectivity operation for one or more UEs; reallocate slice resources for one or more UEs; and / or adapt cell coverage configuration according to energy criteria.

[0068] In various embodiments, the Network Energy Cost (EC) metric may be per one or more of the following: Slice per node: Indicates how much a certain slice contributes to the Energy Cost of a node; Slice per gNB-DU: Indicates how much a certain slice contributes to the Energy Cost of a gNB-DU; Slice configuration per node: Indicates how much a certain slice configuration contributes to the Energy Cost of a node. Slice configuration may comprise a set of slices configured over cells of the node. Slice configuration may be provided only over a subset of the total cells of the node; Slice configuration per gNB-DU: Indicates how much a certain slice configuration contributes to the Energy Cost of a gNB-DU. Slice configuration may comprise a set of slices configured over cells of the node. Slice configuration may be provided only over a subset of the total cells of the gNB-DU; Slice per cell: Indicates how much a certain slice contributes to the Energy Cost of a cell; and / or Slice per UE: Indicates how much a certain UE contributes to the Energy Cost of a slice.

[0069] In various embodiments, the Energy Cost metric may correspond to an Energy Consumption e.g., m Joules, to an Energy Efficiency metric, e.g., m terms of a data volume or number of active UEs over an energy consumption, or to a unitless index, that normalizes an Energy Consumption value through scaling to an integer number.

[0070] In case of RAN-related optimization, the energy cost metric may act as a reward or cost to enable the RAN take different actions as described above. The energy cost metric may be used by the NG-RAN node to determine an energy saving action together with other information available (measured or configured) in the NG-RAN node, e.g. measured radio measurements, measured UE performance, configured UE QoS, configured cell topology information. As a result the entity making the energy saving action should receive (e.g., through request) a cost or reward, based on the slice-dependent network energy cost metric, that is derived from the action taken by the RAN.

[0071] In various embodiments as used herein, the terms gNB-DU, gNB-CU-CP and gNB-CU-UP may also be understood to cover ng-eNB-DU, ng-eNB-CU-CP and ng-eNB-CU-UP, respectively. Similarly, in various embodiments, the term Fl (corresponding to the Fl interface within the split gNB architecture) may be understood to cover the term W1 (corresponding to the W1 interface within the split ng-eNB architecture).

[0072] As used herein, a communication with a radio access network (RAN) may refer to and mean a communication with a portion of a RAN, such as with a network node (e.g., a DU and / or a CU), or another portion of a RAN. As used herein, a communication with a core network may refer to and mean a communication with one or more services / applications of the core network, such as AMF or another service of a core network.

[0073] As used herein, the terms “first” and “second”, or the like, may refer to a first or second instance of a message being transmitted / received by a component (e.g., UE, apparatus, etc.), or a first or second component in a sequence of described components. As such, the terms are used in a non-limiting manner, and can refer to any message, operation, device, component, or the like.

[0074] In accordance with the brief description, FIG. 3 is a diagram of an example artificial intelligence (AI) machine learning (ML) (AI / ML) model 300 for next generation radio access network (NG-RAN) energy saving, according to one illustrated aspect of the disclosure. As shown in FIG. 3, model 300 includes an AI / ML model for NG-RAN energy saving action 310, that includes an input 301, output 302, and a feedback 303.

[0075] In various embodiments, example measured and / or predicted Network Energy Cost information is used by the AI / ML model 300 located in the NG-RAN node to make traffic-aware energy saving decisions. The measured Network energy cost (EC) information may be used to determine an action immediately needed, while the use of predicted Network Energy Cost information may be used to plan and rationalize the required actions.

[0076] In various embodiments, input 301 may include one or more of the following: measured network Energy Cost per slice per UE; predicted network Energy Cost per slice per UE; UE performance information; UE QoS; UE radio condition information; cell neighbor relation information; measure network Energy Cost per slice per cell; and / or predicted network Energy Cost per slice per cell. In various embodiments, output 302 may include a recommended NG-RAN energy saving action per UE or per group of UEs including one or more of the following: e.g., moving UEs between frequency layers, starting / stopping carrier aggregation or adding / removing SCells for carrier aggregation for one or more UEs, modifying QoS parameters e.g. in terms of a maximum bit rate for one or more UEs, starting / stopping dual connectivity operation for one or more UEs; reallocating slice resources for one or more UEs; and / or adapting cell coverage configuration according to energy criteria.

[0077] In various embodiments, feedback 303 may include one or more of the following: measured network Energy Cost per slice per UE; measured network Energy Cost per slice per cell; and / or UE performance information. Feedback can be sent after a decision by the AI / ML Model in order to provide additional input information with respect to the performance of the recommended decisions by the AI / ML Model.

[0078] In various embodiments, other information (e.g., radio conditions information, cell neighbor relation information, UE performance information e.g., related to an Average UL / DL Throughput, Average DL, Average Packet Loss DL, etc., UE QoS) may be made available in the NG-RAN node / gNB-CU-CP either using existing measurements or via 0AM configuration.

[0079] In various embodiments, examples below are described in more detail that may include network Energy Cost information.

[0080] In various embodiments the network Energy Cost information may include: Measured Network Energy Cost information per slice per UE, which may be obtained from the gNB-DU to determine energy saving decisions within the NG-RAN. An energy saving decision can be requested for the purpose of training an AI / ML model or as part of feedback information to an AI / ML model. This information may also be obtained through periodic signaling or upon request (e.g., for the purpose of monitoring of an Energy Cost pertaining to a UE as a function of the variation of the radio conditions). In various embodiments, the information may be obtained from a Secondary Node (e.g, NG-RAN node 2) in case of Dual Connectivity, to determine the Network Energy Cost related to an SCG (Secondary Cell Group), and used to decide whether to maintain a UE in Dual Connectivity.

[0081] In various embodiments, the information may be Predicted Network Energy Cost information per slice per UE, which may be obtained from the gNB-DU and / or from the Secondary Node (NG-RAN node 2) in case of Dual Connectivity to anticipate on traffic-aware energy saving decisions within the NG-RAN. The gNB-DU and / or the Secondary Node may determine this information by anticipating on UE traffic and radio conditions. The predicted Network Energy Cost information per slice per UE obtained from the Secondary Node (NG-RAN node 2) may be used to determine the future Network Energy Cost related to an SCG (Secondary Cell Group), and to determine whether the UE should be kept in Dual Connectivity in the future, and hence plan future slice resource allocation for the case where the UE could be entirely served in Single Connectivity.

[0082] In various embodiments, the information may be Measured Network Energy Cost information per slice per cell, obtained from the gNB-DU to determine energy saving actions within the NG-RAN for a group of UEs determined by the served cell(s) and / or the S-NSSAI(s), and / or obtained from the Secondary Node (NG-RAN node 2) in case of Dual Connectivity, to determine the network energy cost related to UEs served via SCG (Secondary Cell Group). This information may be used to evaluate the overall cost of keeping UEs in Dual Connectivity.

[0083] In various embodiments, the information may be Predicted Network Energy Cost information per slice per cell, obtained from the gNB-DU to determine future energy saving actions within the NG-RAN for a group of UEs, and / or obtained from the Secondary Node (NG-RAN node 2) in case of Dual Connectivity, to determine the network energy cost related to UEs served via SCG (Secondary Cell Group). This information may be used to evaluate the overall cost of keeping UEs in Dual Connectivity.

[0084] In various embodiments, the NG-RAN node is split into a gNB-CU-CP (or gNB-CU) and a gNB-DU, and the gNB-DU executes an energy saving action. In this case, the measured Network Energy Cost information relative to the energy saving action may be retrieved by the gNB-CU-CP from the gNB-DU at the granularity level of ‘per slice per UE’. The Network Energy Cost can be reported over a list of S-NSSAIs. The Network Energy Cost may also be reported over a list of cells, e.g. if the UE is served using Carrier Aggregation or in case of successive intra-gNB-DU handovers.

[0085] In accordance with the brief description, FIG. 4 is a diagram of an example embodiment of signals and operations among UE, gNB-CU-CP and gNB-DU, according to one illustrated aspect of the disclosure. In various embodiments, the components depicted in FIG. 4 may correspond to similar components described above in FIGS. 1 and 2. It will be understood that a described signal may have associated operations and a described operation may have associated signals.

[0086] At operation 401, the gNB-CU-CP transmits a measurement configuration request message to the gNB-DU and the gNB-DU receives the measurement configuration request message. In various embodiments, the measurement configuration request message includes a gNB-CU measurement ID and may include measurement configuration information. In various embodiments, the measurement configuration request message includes a bitmap that includes an nth bit for action associated measured network energy cost for UE.

[0087] At operation 402, the gNB-DU transmits a measurement configuration response message to the gNB-CU-CP and the gNB-CU-CP receives the measurement configuration response message. In various embodiments, the measurement configuration response message may include gNB-CU measurement ID and may include one or more of the following: gNB-DU measurement ID and / or a failed reporting characteristics bitmap. In various embodiments, operations 401 and 402 may be a measurement configuration.

[0088] At operation 403, the gNB-CU-CP transmits an action request message to the gNB-DU and the gNB-DU receives the action request message. In various embodiments, the action request message includes an F1AP UE ID, a data collection ID comprising a gNB-CU measurement ID and a gNB-DU measurement ID, and / or parameters for action. Based upon the received action request, an action (e.g., as described above) may be taken at operation 404. In various embodiments, operations 403 and 404 may be a measurement collection trigger.

[0089] At operation 405, the gNB-DU transmits a measurement report to the gNB-CU-CP and the gNB-CU-CP receives the measurement report. In various embodiments, the measurement report includes gNB-CU measurement ID, gNB-DU measurement ID, F1AP UE ID, measured Network Energy Cost per UE associated to action per slice per cell. In various embodiments, operation 405 is measurement reporting. In other examples the gNB-DU reports the measured Network Energy Cost per UE associated to action per slice overall for all cells serving the UE. The gNB-CU-CP may then determine the measured Network Energy Cost per UE associated to action per slice per cell based e.g. on information already available in the gNB-CU-CP about Carrier Aggregation for the UE.

[0090] In various embodiments, the Measurement Configuration Request / Response messages may be realized as e.g. F1AP Resource Status Request / Response messages (e.g., as described in TS 38.473). In various embodiments, the Data Collection Request / Response messages in XnAP could be introduced also in Fl AP to implement Measurement Configuration Request / Response messages. Similarly, the Measurement Report may be realized as e.g., an F1AP Resource Status Update message or the XnAP message Data Collection Update can be introduced also in Fl AP.

[0091] The operations of FIG. 4 are merely illustrative, and variations are contemplated to be within the scope of the present disclosure. In embodiments, the operations may include other operations not illustrated in FIG. 4. In embodiments, the operations may not include every operation illustrated in FIG. 4. In embodiments, the operations may be implemented in a different order than that illustrated in FIG. 4. Such and other embodiments are contemplated to be within the scope of the present disclosure. Persons of skill in the art will appreciate that, although various example components are described as perform various functions, other components may perform those functions described in FIG. 4.

[0092] In accordance with the brief description, FIG. 5 is a diagram of an example embodiment of signals and operations among UE, gNB-CU-CP and gNB-DU, according to another illustrated aspect of the disclosure. In various embodiments, the components depicted in FIG. 5 may correspond to similar components described above in FIGS. 1 and 2. It will be understood that a described signal may have associated operations and a described operation may have associated signals.

[0093] At operation 501, the gNB-CU-CP transmits a measurement configuration request message to the gNB-DU and the gNB-DU receives the measurement configuration request message. In various embodiments, the measurement configuration request message includes the gNB-CU measurement ID and may include one or more of the following: measurement configuration, reporting period, and / or prediction time. In various embodiments, the measurement configuration request message includes a bitmap that includes an nth bit for measured network energy cost for UE and an mth bit for predicted Network Energy Cost for UE. In some examples the gNB-CU-CP only requests measured energy cost to be reported by the gNB-DU. In these examples, the gNB-CU-CP may determine the Predicted Network Energy Cost based on traffic information retrieved from the gNB-CU-UP and available radio condition information.

[0094] At operation 502, the gNB-DU transmits a measurement configuration response message to the gNB-CU-CP and the gNB-CU-CP receives the measurement configuration response message. In various embodiments, the measurement configuration response message includes the gNB-CU measurement ID and may include one or more of the following: gNB-DU measurement ID, and / or a failed reporting characteristics bitmap. In various embodiments, operations 501 and 502 may be a measurement configuration.

[0095] At operation 503, the gNB-CU-CP transmits a UE context setup request message to the gNB-DU and the gNB-DU receives one or more UE context setup request messages. In various embodiments, the UE context setup request messages include one or more of the following: an F1AP UE ID, data collection, gNB-CU measurement ID, and / or gNB-DU measurement ID. Based upon the received action request, an RRC connection establishment / re-establishment resume may be taken at operation 504. In various embodiments, operations 503 and 504 may be a measurement collection trigger.

[0096] At operation 506 and 507, the gNB-DU transmits measurement reports to the gNB-CU-CP and the gNB-CU-CP receives the measurement reports. In various embodiments, the measurement reports may include one or more of the following: gNB-CU-CP measurement ID, gNB-CU-UP measurement ID, Network Energy Cost (measured and / or predicted) per UE per slice per cell. In various embodiments, operations 506 and 507 may be measurement reporting. In other examples the gNB-DU reports the Network Energy Cost (measured or predicted) per UE associated to action per slice overall for all cells serving the UE. The gNB-CU-CP may then determine the measured Network Energy Cost per UE associated to action per slice per cell based e.g. on information already available in the gNB-CU-CP about Carrier Aggregation for the UE. The measurement reports contain network energy cost (measured or predicted) for one or more UEs that connected, reestablished or resumed their RRC connection at operation 504.

[0097] Accordingly, the gNB-CU-CP triggers periodic collection of measured and predicted Network Energy Cost per slice per UE, hence receiving periodic measurements which may be taken into account together with variation in e.g, in UE radio conditions. The gNB-CU-CP configures such periodic signaling using, for example, Measurement Configuration Request / Response messages, and indicates during the FlAP UE CONTEXT SETUP REQUEST message for which UE the measurement configuration applies. The Network Energy Cost (measured or predicted) can be reported over a list of S-NSSAIs. The Network Energy Cost (measured or predicted) may also be reported over a list of cells if the UE is served using Carrier Aggregation or in case of successive intra-gNB-DU handovers.

[0098] FIG. 5 shows a measurement configuration request from a gNB-CU-CP to a gNB-DU to request reporting of a measured / predicted Energy Cost for a UE. The configuration may contain additional bits to indicate a measured network Energy Cost for UE and a predicted network Energy Cost for UE. The configuration from gNB-CU-CP may include timing information regarding the reporting, namely an indication whether the reporting will take place in one-shot or whether it will be periodic reporting. Periodic reporting could be indicated by including a Reporting Periodicity IE inside the MEASUREMENT CONFIGURATION REQUEST message. In the response, MEASUREMENT CONFIGURATION RESPONSE message, gNB-DU can include its measurement ID and a bitmap indicating whether some of the measurements requested by the gNB-CU may not be initiated. This can be done by including a Failed Report Characteristics bitmap in the response message, indicating by setting the corresponding entries with 1 the measurements which cannot be initiated by the gNB-DU with appropriate cause values on the reason of failure. gNB-DU may receive from gNB-CU-CP a trigger indication for a given UE to calculate a measured Network Energy Cost for this UE.

[0099] The operations of FIG. 5 are merely illustrative, and variations are contemplated to be within the scope of the present disclosure. In embodiments, the operations may include other operations not illustrated in FIG. 5. In embodiments, the operations may not include every operation illustrated in FIG. 5. In embodiments, the operations may be implemented in a different order than that illustrated in FIG. 5. Such and other embodiments are contemplated to be within the scope of the present disclosure. Persons of skill in the art will appreciate that, although various example components are described as perform various functions, other components may perform those functions described in FIG. 5.

[00100] In accordance with the brief description, FIG. 6 is a diagram of an example embodiment of signals and operations among UE, gNB-CU-CP and gNB-DU, according to another illustrated aspect of the disclosure. In various embodiments, the components depicted in FIG. 6 may correspond to similar components described above in FIGS. 1 and 2. It will be understood that a described signal may have associated operations and a described operation may have associated signals.

[00101] At operation 601, the gNB-CU transmits a UE Energy Cost request message to the gNB-DU and the gNB-DU receives the UE Energy Cost request message. In various embodiments, the UE Energy Cost request message includes one or more of the following: a UE Fl AP ID, an indication whether a measured, a predicted, or both measured and predicted Energy Cost is requested and in case of a prediction a prediction time when the prediction should be taken. In some examples the gNB-CU-CP only requests measured energy cost to be reported by the gNB-DU. In these examples, the gNB-CU-CP may determine the Predicted Network Energy Cost based on traffic information retrieved from the gNB-CU-UP and available radio condition information.

[00102] At operation 602, the gNB-DU transmits a UE Energy Cost response message to the gNB-CU and the gNB-CU receives the UE Energy Cost response message. In various embodiments, the UE Energy Cost response message includes one or more of the following: UE Fl AP ID, Network Energy Cost (measured and / or predicted) per UE per slice per cell. In various embodiments, the Network Energy Cost (measured or predicted) can be reported over a list of S-NSSAIs. Also, the Network Energy Cost (measured or predicted) may be reported over a list of cells (e.g., if the UE is served using Carrier Aggregation).

[00103] The operations of FIG. 6 are merely illustrative, and variations are contemplated to be within the scope of the present disclosure. In embodiments, the operations may include other operations not illustrated in FIG. 6. In embodiments, the operations may not include every operation illustrated in FIG. 6. In embodiments, the operations may be implemented in a different order than that illustrated in FIG. 6. Such and other embodiments are contemplated to be within the scope of the present disclosure. Persons of skill in the art will appreciate that, although various example components are described as perform various functions, other components may perform those functions described in FIG. 6.

[00104] In various embodiments, the NG-RAN node 1 triggers periodic collection of measured and predicted Network Energy Cost at the NG-RAN node 2 for the purpose of monitoring energy cost related to dual connectivity, and hence receiving periodic measurements which may be taken into account together with variation in (e.g., UE radio conditions). The NG-RAN node 1 configures such periodic signaling using Measurement Configuration Request / Response messages, and indicates in the XnAP SN ADDITION message for which UE the measurement configuration applies. The Network Energy Cost (measured or predicted) can be reported over a list of S-NSSAIs. The Network Energy Cost (measured or predicted) may also be reported over a list of cells e.g. if the UE is served using Carrier Aggregation or in case of measurement report covering one or more change of PSCell for the UE.

[00105] In accordance with the brief description, FIG. 7 is a diagram of an example embodiment of signals and operations among a UE and NG-RANs, according to one illustrated aspect of the disclosure. In various embodiments, the components depicted in FIG. 7 may correspond to similar components described above in FIGS. 1 and 2. It will be understood that a described signal may have associated operations and a described operation may have associated signals.

[00106] At operation 701, the NG-RAN 1 transmits a measurement configuration request message to the NG-RAN 2 and the NG-RAN 2 receives the measurement configuration request message. In various embodiments, the measurement configuration request message includes one or more of the following: NG-RAN 1 measurement ID, measurement configuration, reporting period, and / or prediction time in case the request pertains to a prediction. In various embodiments, the measurement configuration request message includes a bitmap that includes an nth bit for measured network energy cost for UE and an mth bit for predicted energy cost for UE.

[00107] At operation 702, the NG-RAN 2 transmits a measurement configuration response message to the NG-RAN 1 and the NG-RAN 1 receives the measurement configuration response message. In various embodiments, the measurement configuration response message may include one or more of the following: NG-RAN 1 measurement ID, NG-RAN 2 measurement ID, and / or a failed reporting characteristics bitmap to indicate which measurements cannot be initiated at NG-RAN node 2. In various embodiments, operations 701 and 702 may be performed by a new procedure e.g., a Measurement Configuration Reporting Initiation procedure.

[00108] At operation 703, the NG-RAN 1 transmits SN addition message to the NG-RAN 2 and the NG-RAN 2 receives the SN addition message. In various embodiments, the SN addition message includes an XnAP UE ID and a data collection ID that comprises an NG-RAN 1 measurement ID and an NG-RAN 2 measurement ID. Based upon the received SN addition message, SCG setup occurs at operation 704. In various embodiments, operations 703 and 704 may be a measurement collection trigger.

[00109] At operation 705 and 706, the NG-RAN 2 transmits measurement reports to the NG-RAN 1 and the NG-RAN 1 receives the measurement reports. In various embodiments, the measurement reports may include one or more of the following: NG-RAN 1 measurement ID, NG-RAN 2 measurement ID, Network Energy Cost (measured and / or predicted) per UE per slice per cell. In various embodiments, operations 705 and 706 may be measurement reporting. The measurement reports contain network energy cost (measured or predicted) for one or more UEs that established an SCG at NG-RAN 2 at operation 704.

[00110] The operations of FIG. 7 are merely illustrative, and variations are contemplated to be within the scope of the present disclosure. In embodiments, the operations may include other operations not illustrated in FIG. 7. In embodiments, the operations may not include every operation illustrated in FIG. 7. In embodiments, the operations may be implemented in a different order than that illustrated in FIG. 7. Such and other embodiments are contemplated to be within the scope of the present disclosure. Persons of skill in the art will appreciate that, although various example components are described as perform various functions, other components may perform those functions described in FIG. 7.

[00111] In accordance with the brief description, FIG. 8 is a diagram of an example embodiment of signals and operations among a UE and NG-RANs, according to another illustrated aspect of the disclosure. In various embodiments, the components depicted in FIG. 8 may correspond to similar components described above in FIGS. 1 and 2. It will be understood that a described signal may have associated operations and a described operation may have associated signals.

[00112] At operation 801, NG-RAN 1 transmits a UE Energy Cost request message to the NG-RAN 2 and the NG-RAN 2 receives the UE Energy Cost request message. In various embodiments, the UE Energy Cost request message includes UE XnAP ID and may include one or more of the following: an indication whether a measured or a predicted Energy Cost or both are requested and in case of a prediction a prediction time when the prediction is requested.

[00113] At operation 802, the NG-RAN 2 transmits a UE Energy Cost response message to the NG-RAN 1 and the NG-RAN 1 receives the UE Energy Cost response message. In various embodiments, the UE Energy Cost response message includes one or more of the following: Network Energy Cost (measured and / or predicted) per UE per slice per cell. In various embodiments, the Network Energy Cost (measured or predicted) can be reported over a list of S-NSSAIs. Also, the Network Energy Cost (measured or predicted) may be reported over a list of cells e.g. if the UE is served using Carrier Aggregation or in case of measurement report covering one or more change of PSCell for the UE.

[00114] The operations of FIG. 8 are merely illustrative, and variations are contemplated to be within the scope of the present disclosure. In embodiments, the operations may include other operations not illustrated in FIG. 8. In embodiments, the operations may not include every operation illustrated in FIG. 8. In embodiments, the operations may be implemented in a different order than that illustrated in FIG. 8. Such and other embodiments are contemplated to be within the scope of the present disclosure. Persons of skill in the art will appreciate that, although various example components are described as perform various functions, other components may perform those functions described in FIG. 8.

[00115] In various embodiments, the gNB-CU-CP triggers periodic collection of measured and predicted Network Energy Cost per slice per cell, hence receiving periodic measurements which may be taken to determine immediate or future energy saving actions within the NG-RAN for UEs served by the gNB-DU. The gNB-CU-CP configures such periodic signaling using Measurement Configuration Request / Response messages. If the list of Cell IDs is not included in the Measurement Configuration Request message, the gNB-DU may report the requested information for all its cells. The Network Energy Cost (measured or predicted) may be reported over a list of cells e.g. if the UE is served using Carrier Aggregation. The Network Energy Cost (measured or predicted) can be reported over a list of S-NSSAIs.

[00116] FIG. 9 is a diagram of an example embodiment of signals and operations among UE, gNB-CU-CP and gNB-DU, according to another illustrated aspect of the disclosure. In various embodiments, the components depicted in FIG. 9 may correspond to similar components described above in FIGS. 1 and 2. It will be understood that a described signal may have associated operations and a described operation may have associated signals.

[00117] At operation 901, the gNB-CU-CP transmits a measurement configuration request message to the gNB-DU and the gNB-DU receives the measurement configuration request message. In various embodiments, the measurement configuration request message includes gNB-CU measurement ID and may include one or more of the following: measurement configuration, reporting period, prediction time, list of S-NSSAI, and / or list of cell IDs. In various embodiments, the measurement configuration request message includes a bitmap that includes an nth bit for measured slice network energy cost and an mth bit for predicted slice network energy cost. In some examples the gNB-CU-CP only requests measured energy cost to be reported by the gNB-DU. In these examples, the gNB-CU-CP may determine the Predicted Network Energy Cost based on traffic information retrieved from the gNB-CU-UP and available radio condition information.

[00118] At operation 902, the gNB-DU transmits a measurement configuration response message to the gNB-CU-CP and the gNB-CU-CP receives the measurement configuration response message. In various embodiments, the measurement configuration response message includes gNB-CU measurement ID and may include one or more of the following:, gNB-DU measurement ID, and / or a failed reporting characteristics bitmap. In various embodiments, operations 901 and 902 may be a measurement configuration.

[00119] At operation 903 and 904, the gNB-DU transmits measurement reports to the gNB-CU-CP and the gNB-CU-CP receives the measurement reports. In various embodiments, the measurement reports may include one or more of the following: gNB-CU-CP measurement ID, gNB-DU measurement ID, Network Energy Cost (measured and / or predicted) per slice per cell. In other examples the gNB-DU reports the Network Energy Cost (measured and / or predicted) per slice aggregated over all cells served by the gNB-DU. The gNB-CU-CP may then determine the Network Energy Cost (measured and / or predicted) per slice per cell based e.g. cell load information already available in the gNB-CU-CP. In various embodiments, operations 903 and 904 may be measurement reporting.

[00120] The operations of FIG. 9 are merely illustrative, and variations are contemplated to be within the scope of the present disclosure. In embodiments, the operations may include other operations not illustrated in FIG. 9. In embodiments, the operations may not include every operation illustrated in FIG. 9. In embodiments, the operations may be implemented in a different order than that illustrated in FIG. 9. Such and other embodiments are contemplated to be within the scope of the present disclosure. Persons of skill m the art will appreciate that, although various example components are described as perform various functions, other components may perform those functions described in FIG. 9.

[00121] In various embodiments, the NG-RAN node 1 triggers periodic collection of measured and predicted Network Energy Cost per slice per cell at the NG-RAN node 2 for the purpose of monitoring current and future energy cost related to keeping UEs in dual connectivity. The NG-RAN node 1 configures such periodic signaling using Measurement Configuration Request / Response messages. If the list of PSCell IDs is not included in the Measurement Configuration Request message, the NG-RAN node 2 may include the PSCells used by the NG-RAN node 2 for UEs for which the NG-RAN node 1 is Master Node. In one example, in case of Carrier Aggregation, the Network Energy Cost in SCells may be reported together with the Network Energy Cost in the PSCell. The Network Energy Cost (measured or predicted) may be reported over a list of cells if the UE is served using Carrier Aggregation. The Network Energy Cost (measured or predicted) can be reported over a list of S-NSSAis.

[00122] In various embodiments, the NG-RAN Node 1 can determine whether dual connectivity is beneficial with respect to Network Energy Cost metric for the chosen UEs in the slice for the given cells or whether it should be de-activated. Similarly, in case of carrier aggregation the NG-RAN 2 can observe the Network Energy Cost over its cells and determine (through internal actions) to maintain CA or to deactivate it.

[00123] In accordance with the brief description, FIG. 10 is a diagram of an example embodiment of signals and operations among a UE and NG-RANs, according to another illustrated aspect of the disclosure. In various embodiments, the components depicted in FIG. 10 may correspond to similar components described above in FIGS. 1 and 2. It will be understood that a described signal may have associated operations and a described operation may have associated signals.

[00124] At operation 1001, the NG-RAN 1 transmits a measurement configuration request message to the NG-RAN 2 and the NG-RAN 2 receives the measurement configuration request message. In various embodiments, the measurement configuration request message includes NG-RAN 1 measurement ID and may include one or more of the following: measurement configuration, reporting period, prediction time, list of S-NSSAI, list of Cell IDs. In various embodiments, the measurement configuration request message includes a bitmap that includes an nth bit for measured slice network energy cost for Dual Connectivity and an mth bit for predicted slice network energy cost for Dual Connectivity.

[00125] At operation 1002, the NG-RAN 2 transmits a measurement configuration response message to the NG-RAN 1 and the NG-RAN 1 receives the measurement configuration response message. In various embodiments, the measurement configuration response message includes : NG-RAN 1 measurement ID NG-RAN 2 measurement ID, and possibly a failed reporting characteristics bitmap. In various embodiments, operations 1001 and 1002 may be a measurement configuration.

[00126] At operation 1003, UEs are in Dual Connectivity where NG-RAN 1 is the MN and NG-RAN 2 is the SN.

[00127] At operation 1004 and 1005, the NG-RAN 2 transmits measurement reports to the NG-RAN 1 and the NG-RAN 1 receives the measurement reports. In various embodiments, the measurement reports may include one or more of the following: NG-RAN 1 measurement ID, NG-RAN 2 measurement ID, Network Energy Cost for Dual Connectivity (measured and / or predicted) per slice per cell. In various embodiments, operations 1004 and 1005 may be measurement reporting. In various embodiments, the cells reported at 1004 and 1005 may be PSCells for UEs served in Dual Connectivity. In other examples the NG-RAN 2 reports the Network Energy Cost for Dual Connectivity (measured and / or predicted) per slice aggregated over all cells in which the NG-RAN 2 serves UEs as Secondary Node, and for which the NG-RAN 1 is Master Node. The NG-RAN 1 may then, in some examples, estimate the Network Energy Cost for Dual Connectivity (measured and / or predicted) per slice per cell based on e.g. UE traffic information already available in the NG-RAN 1.

[00128] The operations of FIG. 10 are merely illustrative, and variations are contemplated to be within the scope of the present disclosure. In embodiments, the operations may include other operations not illustrated in FIG. 10. In embodiments, the operations may not include every operation illustrated in FIG. 10. In embodiments, the operations may be implemented in a different order than that illustrated in FIG. 10. Such and other embodiments are contemplated to be within the scope of the present disclosure. Persons of skill in the art will appreciate that, although various example components are described as perform various functions, other components may perform those functions described in FIG. 10.

[00129] The following describes operations from the perspective of an apparatus, which in various embodiments may include an NG-RAN node, a Distributed Unit of an NG-RAN node (gNB-DU), or a Central Unit of a same NG-RAN node (gNB-CU). From such a perspective, a method may include receiving, by a first apparatus, a first message, the first message including a request for reporting an energy cost per network slice. The first apparatus selects one or more user equipments (UEs), and transmits a second message to a second apparatus, the second message including a report of the energy cost per network slice for the one or more UEs.

[00130] Referring now to FIG. 11, there is shown a block diagram of example components of a UE or a network apparatus (e.g., of a RAN or a core network). The apparatus includes an electronic storage 1110, a processor 1120, a network interface 1140, and a memory 1150. The various components may be communicatively coupled with each other. The processor 1120 may be and may include any type of processor, such as a single-core central processing unit (CPU), a multi-core CPU, a microprocessor, a digital signal processor (DSP), a System-on-Chip (SoC), or any other type of processor. The memory 1150 may be a volatile type of memory, e.g., RAM, or a non-volatile type of memory, e.g., NAND flash memory. The memory 1150 includes processor-readable instructions that are executable by the processor 1120 to cause the apparatus to perform various operations, including those mentioned herein, such as the operations described in FIGS. 3-10.

[00131] The electronic storage 1110 may be and include any type of electronic storage used for storing data, such as hard disk drive, solid state drive, optical disc, and / or other non-transitory computer-readable mediums, among other types of electronic storage. The electronic storage 1110 stores processor-readable instructions for causing or configured for causing the apparatus to perform its operations and also stores data associated with such operations, such as storing data relating to 5G NR standards, among other data. The network interface 1140 may implement wireless networking technologies such as 5G NR and / or other wireless networking technologies.

[00132] The components shown in FIG. 11 are merely examples, and persons skilled in the art will understand that an apparatus includes other components not illustrated and may include multiples of any of the illustrated components. Such and other embodiments are contemplated to be within the scope of the present disclosure. For example, a transmitter and a receiver may be included as components for transmitting and receiving signals.

[00133] Further embodiments of the present disclosure include the following examples.

[00134] Example 1.1. An apparatus, comprising: means for receiving, by a first apparatus, a first message, the first message including a request for reporting an energy cost per network slice; means for selecting, by the first apparatus, one or more user equipments (UEs); and means for transmitting, by the first apparatus, a second message to a second apparatus, the second message including a report of the energy cost per network slice for the one or more UEs.

[00135] Example 1.2. The apparatus of example 1.1, wherein the first message is received from the second apparatus.

[00136] Example 1.3. An apparatus as in any one of examples 1.1 or 1.2, wherein the first message includes a request for the energy cost per network slice for at least a first UE of the one or more UEs, and wherein the second message includes a report for the energy cost per network slice for the first UE of the one or more UEs.

[00137] Example 1.4. An apparatus as in any one of examples 1.1 to 1.3, wherein the report comprises the energy cost for a plurality of network slices.

[00138] Example 1.5. An apparatus as in any one of examples 1.1 to 1.4, wherein selecting the one or more UEs comprises receiving, by the first apparatus, in the first message, an action associated with the energy cost per network slice, receiving, by the first apparatus, a third message associated with a UE corresponding to the action requested in the first message, and selecting the one or more UEs for the transmission of the second message based upon the first message and the third message.

[00139] Example 1.6. An apparatus as in any one of examples 1.1 to 1.4, wherein selecting the one or more UEs comprises receiving, by the first apparatus, in the first message an identifier of one or more UEs, and selecting the UEs for the transmission of the second message based upon the identifier of one or more UEs.

[00140] Example 1.7. An apparatus as in any one of examples 1.1 to 1.6, wherein the second message includes a report of the energy cost per network slice per cell over a list of cells for the one or more UEs.

[00141] Example 1.8. The apparatus of example 1.7, wherein the list of cells is received in the first message.

[00142] Example 1.9. The apparatus of example 1.7, wherein the list of cells corresponds to cells which have been used as Primary Secondary Cells (PSCells) by the first apparatus for the one or more UEs in a dual connectivity scheme where the secondary apparatus acted as master node.

[00143] Example 1.10. An apparatus as in any one of examples 1.1 to 1.9, wherein the reported energy cost per network slice corresponds to an energy cost per cell over a list of cells used for carrier aggregation for the one or more UEs.

[00144] Examplel.il. An apparatus as in any one of examples 1.1 to 1.10, further comprising receiving in the first message a list of one or more slices, and reporting in the second message the energy cost for the one or more UEs for each slice included in the received list of slices.

[00145] Example 1.12. An apparatus as in any one of examples 1.1 to 1.11, wherein the request for the energy cost per network slice is a request for a measured energy cost per UE or a request for a predicted energy cost per UE.

[00146] Example 1.13. An apparatus as in any one of examples 1.1 to 1.12, wherein the first apparatus is a first next generation radio access network (NG-RAN) node and the second apparatus is a second NG-RAN node.

[00147] Example 1.14. An apparatus as in any one of examples 1.1 to 1.13, wherein the first apparatus is a Distributed Unit of an NG-RAN node (gNB-DU) and the second apparatus is the Central Unit of the same NG-RAN node (gNB-CU).

[00148] Example 1.15. An apparatus as in any one of examples 1.1 to 1.14, wherein the first apparatus transmits the second message to the second apparatus periodically.

[00149] Example 1.16. An apparatus as in any one of examples 1.1 to 1.15, wherein the period for sending the second message has been received in the first message.

[00150] Example 1.17. An apparatus as in any one of examples 1.1 to 1.16, further comprising receiving, by the second apparatus from the first apparatus, the second message including a report of the energy cost per network slice for the one or more UEs, and performing, by the second apparatus based on the received report, at least one energy saving action concerning the one or more UEs.

[00151] The embodiments and aspects disclosed herein are examples of the present disclosure and may be embodied in various forms. For instance, although certain embodiments herein are described as separate embodiments, each of the embodiments herein may be combined with one or more of the other embodiments herein. Specific structural and functional details disclosed herein are not to be interpreted as limiting, but as a basis for the claims and as a representative basis for teaching one skilled in the art to variously employ the present disclosure in virtually any appropriately detailed structure. Like reference numerals may refer to similar or identical elements throughout the description of the figures.

[00152] The phrases “in an aspect,” “in aspects,” “in various aspects,” “in some aspects,” or “in other aspects” may each refer to one or more of the same or different aspects in accordance with this present disclosure. The phrase “a plurality of’ may refer to two or more.

[00153] In various embodiments, the terms “first message” and “second message”, as well as any subsequent messages may refer to any messages that are transmitted or received in an order and are not necessarily limited to any particular message.

[00154] The phrases “in an embodiment,” “in embodiments,” “m various embodiments,” “in some embodiments,” or “in other embodiments” may each refer to one or more of the same or different embodiments in accordance with the present disclosure. A phrase in the form “A or B” means “(A), (B), or (A and B).” A phrase in the form “at least one of A, B, or C” means “(A); (B); (C); (A and B); (A and C); (B and C); or (A, B, and C) ”

[00155] Any of the herein described methods, programs, algorithms or codes may be converted to, or expressed in, a programming language or computer program. The terms “programming language” and “computer program,” as used herein, each include any language used to specify instructions to a computer, and include (but is not limited to) the following languages and their derivatives: Assembler, Basic, Batch files, BCPL, C, C+, C++, Delphi, Fortran, Java, JavaScript, machine code, operating system command languages, Pascal, Perl, PL1, Python, scripting languages, Visual Basic, metalanguages which themselves specify programs, and all first, second, third, fourth, fifth, or further generation computer languages. Also included are database and other data schemas, and any other meta-languages. No distinction is made between languages which are interpreted, compiled, or use both compiled and interpreted approaches. No distinction is made between compiled and source versions of a program. Thus, reference to a program, where the programming language could exist m more than one state (such as source, compiled, object, or linked) is a reference to any and all such states. Reference to a program may encompass the actual instructions and / or the intent of those instructions.

[00156] While aspects of the present disclosure have been shown in the drawings, it is not intended that the present disclosure be limited thereto, as it is intended that the present disclosure be as broad in scope as the art will allow and that the specification be read likewise. Therefore, the above description should not be construed as limiting, but merely as exemplifications of particular aspects. Those skilled in the art will envision other modifications within the scope and spirit of the claims appended hereto.

Claims

1. A method, comprising:receiving, by a first apparatus, a first message, the first message including a request for reporting an energy cost per network slice;selecting, by the first apparatus, one or more user equipments (UEs); andtransmitting, by the first apparatus, a second message to a second apparatus, the second message including a report of the energy cost per network slice for the one or more UEs.

2. The method of claim 1, wherein the first message is received from a second apparatus.

3. A method as in any one of claims 1 or 2, wherein the first message includes a request for the energy cost per network slice for at least a first UE of the one or more UEs, and wherein the second message includes a report for the energy cost per network slice for the first UE of the one or more UEs.

4. A method as in any one of claims 1 to 3, wherein the report comprises the energy cost for a plurality of network slices.

5. A method as in any one of claims 1 to 4, wherein selecting the one or more UEs comprises:receiving, by the first apparatus, in the first message, an action associated with the energy cost per network slice;receiving, by the first apparatus, a third message associated with a UE corresponding to the action requested in the first message; andselecting the one or more UEs for the transmission of the second message based upon the first message and the third message.

6. A method as in any one of claims 1 to 4, wherein selecting the one or more UEs comprises:receiving, by the first apparatus, in the first message an identifier of one or more UEs;andselecting the UEs for the transmission of the second message based upon the identifier of one or more UEs.6bis. A method as in any one of claims 1 to 4, wherein selecting the one or more UEs comprises:Selecting any UE served by the first apparatus and involved by the concerned slice for a configured period of time.

7. A method as in any one of claims 1 to 6, wherein the second message includes a report of the energy cost per network slice per cell over a list of cells for the one or more UEs.

8. The method of claim 7, wherein the list of cells is received in the first message.

9. The method of claim 7, wherein the list of cells corresponds to cells which havebeen used as Primary Secondary Cells (PSCells) by the first apparatus for the one or more UEs in a dual connectivity scheme where the secondary apparatus acted as master node.

10. A method as in any one of claims 1 to 9, wherein the reported energy cost per network slice corresponds to an energy cost per cell over a list of cells used for carrier aggregation for the one or more UEs.

11. A method as in any one of claim 1 to 10, further comprising:receiving in the first message a list of one or more slices; andreporting in the second message the energy cost for the one or more UEs for each slice included in the received list of slices.

12. A method as in any one of claims 1 to 11, wherein the request for the energy cost per network slice is a request for a measured energy cost per UE or a request for a predicted energy cost per UE.

13. A method as in any one of claims 1 to 12, wherein the first apparatus is a first next generation radio access network (NG-RAN) node and the second apparatus is a second NG-RAN node.

14. A method as in any one of claims 1 to 13, wherein the first apparatus is a Distributed Unit of an NG-RAN node (gNB-DU) and the second apparatus is the Central Unit of the same NG-RAN node (gNB-CU).

15. A method as in any one of claims 1 to 14, wherein the first apparatus transmits the second message to the second apparatus periodically.

16. A method according to claim 15, wherein the period for sending the second message has been received in the first message.

17. A method as in any one of claims 1 to 16, further comprising:receiving, by the second apparatus from the first apparatus, the second message including a report of the energy cost per network slice for the one or more UEs; andperforming, by the second apparatus based on the received report, at least one energy saving action concerning the one or more UEs.

18. An apparatus, comprising:at least one processor; andat least one memory storing instructions which, when executed by the at least one processor, causes the apparatus at least to perform:receiving, by a first apparatus, a first message, the first message including a request for reporting an energy cost per network slice;selecting one or more user equipments (UEs); andtransmitting, by the first apparatus, a second message to a second apparatus, the second message including a report of the energy cost per network slice for the one or more UEs.

19. An apparatus, comprising:at least one processor; andat least one memory storing instructions which, when executed by the at least one processor, cause the apparatus at least to perform a method as in any of claims 1-17.5 20. A processor-readable medium storing instructions which, when executed by atleast one processor of an apparatus, cause the apparatus at least to perform a method as in any one of claims 1-17.Application No: GB2404542.9Examiner:Contract Unit ExaminerClaims searched: 1-20Date of search: 18 November 2024Patents Act 1977: Search Report under Section 17Documents considered to be relevant:Category Relevant to claims Identity of document and passage or figure of particular relevance Y 1-20 WO2022 / 229420 Al (ERICSSON TELEFON AB L M) paragraph [0004] - paragraph [0010]; figure 1, paragraph [0042] - paragraph [0131]; figures 2-9, paragraph [0153] - paragraph [0168]; claim 43 Y 1-20 3GPP DRAFT, vol 3GPP SA2, CHRIS PUDNEY ET AL, "[DRAFT] LS on per UE energy consumption in RAN" URL: https: / / www.3gpp.org / ftp / tsg sa / WG2 Arch / TSGS2 161 Athens 2024- 02 / Docs / S2-2403163.zip the whole document Y 1-5, 7-20 US2023 / 345359 Al (YANG SHUIGENET AL) paragraph [0131] - paragraph [0288]; figures 1-7 A 3GPP DRAFT, vol 3GPP RAN 3, 2023, JIAJUN CHEN ET AL, "(TP to 38.473 &37.483) Consideration on Measured Energy Cost over F1&E1 interface" URL: https: / / www,3 gpp.org / ftp / TSG_RAN / WG3_Iu / TSGR3_l21 -bis / Docs / R3-235429.zip page 1, section 1 Introduction - page 12, section 9.2.1.23 RESOURCE STATUS UPDATE; figures 8.2.10.2-1Categories:X Document indicating lack of novelty or inventive step A Document indicating technological background and / or state of the art. Y Document indicating lack of inventive step if P Document published on or after the declared priority date but combined with one or more other documents of same category. before the filing date of this invention. & Member of the same patent family E Patent document published on or after, but with priority date earlier than, the filing date of this application.Field of Search:www.gov.uk / ipoInternational Classification:Subclass Subgroup Valid From H04W 0024 / 10 01 / 01 / 2009 H04W 0052 / 02 01 / 01 / 2009www.gov.uk / ipo

Images