Energy cost reduction for network slicing

Abstract

Examples of the present disclosure relate to energy cost reduction of network slices. A method includes receiving, by a first device, a first message including a request for reporting an energy cost per network slice. The first apparatus selects one or more user equipments (UEs); and transmitting, by the first device, a second message to a second device, the second message comprising a report of energy costs per network slice for the one or more UEs.

Description

Technical Field

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

[0002] The 3rd Generation Partnership Project (3GPP) provides requirements for energy saving related aspects (e.g., in TS 22.261) to enable operators to save energy. Since best-effort services do not have any performance guarantees, policies can be defined to limit the energy consumption of those services related to best-effort services.

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

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

[0005] In one aspect of the method, the first message is received from the second device.

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

[0007] In one aspect of the method, the report includes energy costs for multiple network slices.

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

[0009] In one aspect of the method, selecting one or more UEs includes: receiving, by the first device, identifiers of the one or more UEs in a first message; and selecting UEs for transmission of the second message based on the identifiers of the one or more UEs.

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

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

[0012] In one aspect of the method, the list of cells corresponds to cells that have been used by the first device as primary secondary cells (PSCells) for one or more UEs in a dual connectivity scheme where the first device acts as a master node.

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

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

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

[0016] In one 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 one aspect of the method, the first device is a distributed unit of an NG-RAN node (gNB-DU) and the second device is a central unit of the same NG-RAN node (gNB-CU).

[0018] In one aspect of the method, the first device periodically transmits a second message to the second device.

[0019] In one aspect of the method, the period for transmitting the second message has been received in the first message.

[0020] In one aspect of the method, the method also includes: receiving, by the second device, a second message from the first device including a report on energy cost per network slice for one or more UEs; and performing, by the second device, at least one energy-saving action with respect to the one or more UEs based on the received report.

[0021] In one 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 to perform at least any one of the aforementioned methods.

[0022] In one aspect of the present disclosure, a processor-readable medium stores instructions that, when executed by at least one processor of a device, cause the device to perform at least any one of the aforementioned methods.

[0023] According to some aspects, the subject matter of the independent claims is provided. 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] Figure 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 present disclosure;

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

[0027] Figure 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 present disclosure;

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

[0029] Figure 5 is a diagram of an example embodiment of signals and operations between a UE, a gNB-CU-CP, and a gNB-DU according to another illustrative aspect of the present disclosure;

[0030] Figure 6 is a diagram of an example embodiment of signals and operations between a UE, a gNB-CU-CP, and a gNB-DU according to another illustrative aspect of the present disclosure;

[0031] Figure 7 is a diagram of an example embodiment of signals and operations between a UE and an NG-RAN according to one illustrated aspect of the present disclosure;

[0032] Figure 8 is a diagram of an example embodiment of signals and operations between a UE and an NG-RAN according to another illustrative aspect of the present disclosure;

[0033] Figure 9 is a diagram of an example embodiment of signals and operations between a UE, a gNB-CU-CP, and a gNB-DU according to another illustrative aspect of the present disclosure;

[0034] Figure 10 is a diagram of an example embodiment of signals and operations between a UE and an NG-RAN according to another illustrative aspect of the present disclosure; and

[0035] Figure 11 is a diagram of an example embodiment of components of a UE or network device 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 the disclosed aspects. However, one skilled in the relevant art will recognize that the various aspects can 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 are not shown or described in detail to avoid unnecessarily obscuring the description of the various aspects.

[0037] Reference throughout this specification to "one aspect" or "aspects" means that a particular feature, structure, or characteristic described in connection with that aspect is included in at least one aspect. Thus, 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] The embodiments described in the present disclosure may be implemented in wireless networking devices, such as, but not limited to, devices 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 Telecommunications System (UMTS, 3G) based on basic Wideband Code Division Multiple Access (W-CDMA), High Speed ​​Packet Access (HSPA), Long Term Evolution (LTE), Advanced LTE, Enhanced LTE (eLTE), 5G New Radio (5GNR), 5G Advanced, 6G (and beyond), and 802.11ax (Wi-Fi 6), among other wireless networking systems. The term "eLTE" herein refers to the evolution of LTE connected to a 5G core. LTE is also known as Evolved UMTS Terrestrial Radio Access (EUTRA) or Evolved UMTS Terrestrial Radio Access Network (EUTRAN).

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

[0040] This disclosure uses 5G NR as an example of a wireless network, and may use a smartphone and / or an augmented reality headset as an example of a UE. It is intended and should be understood that such examples are merely illustrative, and that this disclosure is applicable to other wireless networks and user equipment.

[0041] Figure 1 is a diagram depicting an example of a wireless network 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 devices 130 (e.g., test equipment). The network node 120 will be described in more detail below. As used herein, the term "network device" may refer to any component of the network system 100, such as a server 110, a network node 120, a network device 130, any (multiple) components of the foregoing, and / or any (multiple) other components of the network system 100. Examples of network devices include, but are not limited to, devices that implement various aspects of 5G NR. The present disclosure describes embodiments related to 5G NR and embodiments involving aspects defined by the Third Generation Partnership Project (3GPP). However, it is contemplated that embodiments related to other wireless network technologies are within the scope of the present disclosure.

[0042] The following description provides further details of an example of a network node. In a 5G NR network, a gNodeB (also referred to as a gNB) may include, for example, a node that provides New Radio (NR) user plane and control plane protocol terminations towards the UE and is connected to the 5G Core (5GC) via an NG interface, for example in accordance with 3GPP TS 38.300 V16.6.0 (2021-06) section 3.2, which is incorporated herein by reference.

[0043] The gNB supports various protocol layers, such as Layer 1 (L1) - physical layer, Layer 2 (L2), and Layer 3 (L3).

[0044] NR's Layer 2 (L2) is divided into the following sublayers: Medium Access Control (MAC), Radio Link Control (RLC), Packet Data Convergence Protocol (PDCP), and Service Data Adaptation Protocol (SDAP), where for example: oThe physical layer provides transport channels to the MAC sublayer; oMAC sublayer provides logical channels to RLC sublayer; oRLC sublayer provides RLC channels to PDCP sublayer; The oPDCP sublayer provides radio bearer to the SDAP sublayer; The oSDAP sublayer provides services to the 5GC Quality of Service (QoS) flow; o Control channels include the Broadcast Control Channel (BCCH) and the Physical Control Channel (PCCH).

[0045] Layer 3 (L3) includes, for example, Radio Resource Control (RRC), for example according to 3GPP TS 38.300 V16.6.0 (2021-06) section 6, which is incorporated herein by reference.

[0046] The gNB Central Unit (gNB-CU) includes, for example, a logical node that hosts protocols such as Radio Resource Control (RRC), Service Data Adaptation Protocol (SDAP), and Packet Data Convergence Protocol (PDCP) for the gNB, or RRC and PDCP for the en-gNB, and controls the operation of one or more gNB Distributed Units (gNB-DUs). The gNB-CU terminates the F1 interface with the gNB-DUs. The gNB-CU may also be referred to herein as a CU, central unit, centralized unit, or control unit.

[0047] The gNB distributed unit (gNB-DU) includes, for example, a logical node that hosts the radio link control (RLC), medium access control (MAC), and physical (PHY) layers of a gNB or en-gNB, and its operation is partially controlled by the gNB-CU. A gNB-DU supports one or more cells. A cell is supported by only one gNB-DU. The gNB-DU terminates the F1 interface with the gNB-CU. The gNB-DU may also be referred to herein as a DU or distributed unit.

[0048] As used herein, the term "network node" may refer to any one of a gNB, a gNB-CU or a gNB-DU or any combination thereof. A RAN (Radio Access Network) node or a network node (such as, for example, a gNB, a gNB-CU or a gNB-DU or a portion thereof) may be implemented using, for example, a device having at least one processor and / or at least one memory having processor-readable instructions ("program") configured to support and / or provide and / or process CU and / or DU related functions and / or features, and / or at least one protocol (sub) layer (e.g., layer 2 and / or layer 3) of a RAN (Radio Access Network). There may be different functional divisions between central units and distributed units. This will be discussed below in conjunction with Figure 11 Examples of such devices and assemblies are described.

[0049] The gNB-CU and gNB-DU portions can, for example, be co-located or physically separated. The gNB-DU can even be further split into two parts, for example, one part including processing equipment and one part including antennas. The central unit (CU) can also be referred to as a baseband unit / radio equipment controller / cloud RAN / virtual RAN (BBU / REC / C-RAN / V-RAN), an open RAN (O-RAN), or a portion thereof. The distributed unit (DU) can also be referred to as a remote radio head / remote radio unit / radio equipment / radio unit (RRH / RRU / RE / RU), or a portion thereof. Hereinafter, in various exemplary embodiments of the present disclosure, a network node supporting at least one of the central unit functions or layer 3 protocols of a radio access network can be, for example, a gNB-CU. Similarly, a network node supporting at least one of the distributed unit functions or layer 2 protocols of a radio access network can be, for example, a gNB-DU.

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

[0051] User equipment (UE) 150 may be or include a wireless or mobile device, a device having a radio interface connected to a RAN (Radio Access Network) interface, a smart phone, a vehicle-mounted device, an IoT device, or an M2M device, as well as other types of user equipment. Such a UE 150 may include: at least one processor; and at least one memory including program code; wherein the at least one memory and the computer program code are configured to, together with the at least one processor, cause the device to at least perform certain operations, such as, for example, an RRC connection to the RAN. Figure 11 An example of components of a UE is described. In an embodiment, the UE 150 may be configured to generate a message (e.g., including a cell ID) to be transmitted over the radio to the RAN (e.g., to reach and communicate with a serving cell). In an embodiment, the UE 150 may generate, transmit, and receive an RRC message containing one or more RRCPDUs (packet data units). Those skilled in the art will understand the RRC protocol and other procedures that the UE may perform.

[0052] Continue to refer Figure 1In the example of a 5G NR network, the network system 100 provides one or more cells that define the coverage area of ​​the network system 100. As described above, the network system 100 may include a gNB of the 5G NR network, or may include any other device configured to control radio communications and manage radio resources within a cell. As used herein, the term "resource" may refer to radio resources, such as resource blocks (RBs), physical resource blocks (PRBs), radio frames, subframes, time slots, subbands, frequency regions, subcarriers, beams, etc. In an embodiment, the network node 120 may be referred to as a base station.

[0053] Figure 1 The example is provided and only the network system 100 and the UE 150 are described. Those skilled in the art will appreciate that the network system 100 includes Figure 1 Components not shown, and it will be understood that other user devices may communicate with the network system 100.

[0054] Figure 2 yes Figure 1 A block diagram of example components of a network system 100 is shown. A 5G NR network may be described as an example of a network system 100, and it is intended that aspects described below should also be applicable to other types of network systems. The network system may be based on Figure 1 The signals and connections shown operate to enable UE 150 to communicate with network system 100 via radio access network 225. Additionally, the network system can be divided into user plane components and functions and control plane components and functions, as shown and described herein. Unless otherwise specified, the terms "component," "function," and "service" are used interchangeably herein and may refer to instructions executed by one or more processors and implemented thereby.

[0055] The following describes example functionality of the components. The example functionality is illustrative only, and it should be understood that additional operations and functionality can be performed by the components described herein. Additionally, connections between components can be virtual connections via service-based interfaces, enabling any component to communicate with any other component. In this manner, any component can be used to act as a service "producer" for any other component acting as a service "consumer" to provide network functionality.

[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 open function (NEF) 215, a network repository function (NRF) 216, and a unified data management function (UDM) 217, which may include a unified data repository (UDR) 224.

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

[0058] The user plane includes the UE 150, the radio access network (RAN) 225, the user plane function (UPF) 226, and the data network (DN) 227. The RAN 225 may include a combination of Figure 1 The RAN 225 may be configured to include one or more components, such as one or more network nodes. However, the RAN 225 may not be limited to such components. The UPF 226 provides connectivity for data transmitted through the RAN 225. For example, the DN 226 identifies services from service providers, Internet access, and third-party services.

[0059] AMF 212 handles connection and mobility tasks. AUSF 211 receives authentication requests from AMF 212 and interacts with UDM 217 to authenticate and verify network responses to confirm successful authentication. SMF 213 performs packet data unit (PDU) session management and manages session context with UPF 226.

[0060] The NSSF 214 can select a network slice instance (NSI) and determine the allowed network slice selection assistance information (NSSAI). This selection and determination is used to set up the AMF 212 to provide services for the UE 150. The NEF 215 protects third-party access to network services to create dedicated network services. The NRF 216 acts as a repository for storing network functions to allow functions to register and discover each other.

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

[0062] The NWDAF 220 collects data (e.g., from UE 150 and network systems) to perform network analysis and provide insights to functions that utilize the analysis when providing services. The ADRF 221 allows consumers to store, retrieve, and remove data and analysis. The MDAF 222 provides additional data analysis services to network functions. The OAM 223 provides provisioning and management processing functions to manage elements in or connected to the network (e.g., UE 150, network nodes, etc.).

[0063] Figure 2 are merely examples of components of a network system, and variations are contemplated within the scope of this disclosure. In an embodiment, a network system may include Figure 2 Other components not shown in FIG. In an embodiment, the network system may not include Figure 2 Each component shown. In an embodiment, the components and connections can be used with Figure 2 Such and other embodiments are contemplated to be within the scope of this disclosure.

[0064] Although further details will be provided below, this document describes a method for enabling a RAN (e.g., NG-RAN) to adapt its actions to meet 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 slices defined at different granularities.

[0065] As described above, a slice (e.g., a network slice) may become more energy-intensive as the reserved time and frequency resources are fully utilized. For example, depending on the QoS served by the slice (a higher QoS has more stringent traffic handling requirements), the energy consumed may be higher than other slices serving different QoS (a lower QoS has less stringent traffic handling requirements). This may be particularly true if the time / frequency resources allocated to the slice become more fully loaded, as nodes may need to transmit at higher power to accommodate the additional traffic.

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

[0067] Therefore, this paper describes a method for optimizing the energy cost of slice operation. This problem can be solved in both the RAN and the core network. Specifically, in the case of RAN optimization, the NG-RAN node has some means to reduce the energy cost required to operate the NG-RAN part of the network slice. These means include, for example: moving UEs between frequency layers; starting / stopping carrier aggregation or adding / removing SCells used for carrier aggregation for one or more UEs; modifying QoS parameters, such as the 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 the cell coverage configuration according to energy criteria.

[0068] In various embodiments, the network energy cost (EC) metric may be one or more of the following: per-node slice: indicates how much a particular slice contributes to the energy cost of the node; per-gNB-DU slice: indicates how much a particular slice contributes to the energy cost of the gNB-DU; per-node slice configuration: indicates how much a particular slice configuration contributes to the energy cost of the node. The slice configuration may include a set of slices configured on a cell of the node. The slice configuration may be provided only for a subset of the total cells of the node; per-gNB-DU slice configuration: indicates how much a particular slice configuration contributes to the energy cost of the gNB-DU. The slice configuration may include a set of slices configured on a cell of the node. The slice configuration may be provided only for a subset of the total cells of the gNB-DU; per-cell slice: indicates how much a particular slice contributes to the energy cost of the cell; and / or per-UE slice: indicates how much a particular UE contributes to the energy cost of a slice.

[0069] In various embodiments, the energy cost metric may correspond to energy consumption (e.g., in joules), to an energy efficiency metric (e.g., based on the amount of data or number of active UEs on energy consumption), or to a unitless index that normalizes the energy consumption value by scaling it to an integer.

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

[0071] In various embodiments 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 F1 (corresponding to the F1 interface within a split gNB architecture) may be understood to cover the term W1 (corresponding to the W1 interface within a split ng-eNB architecture).

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

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

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

[0075] In various embodiments, the AI / ML model 300 located in the NG-RAN node uses example measured and / or predicted network energy cost information to make traffic-aware energy-saving decisions. Measured network energy cost (EC) information can be used to determine immediately required actions, while the use of predicted network energy cost information can be used to plan and rationalize required actions.

[0076] In various embodiments, input 301 may include one or more of the following: measured network energy cost per UE per slice; predicted network energy cost per UE per slice; UE performance information; UE QoS; UE radio condition information; cell neighbor relation information; measured network energy cost per cell per slice; and / or predicted network energy cost per cell per slice. In various embodiments, output 302 may include recommended NG-RAN energy saving actions per UE or per group of UEs, including one or more of the following: for example, moving UEs between frequency layers, starting / stopping carrier aggregation or adding / removing SCells for carrier aggregation of one or more UEs, for example, modifying QoS parameters based on the maximum bit rate of 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 based on energy criteria.

[0077] In various embodiments, feedback 303 may include one or more of: measured network energy cost per UE per slice; measured network energy cost per cell per slice; and / or UE performance information. Feedback may be sent after the AI / ML model makes a decision to provide additional input information for the AI / ML model to implement its recommended decision.

[0078] In various embodiments, other information (e.g., radio condition information, cell neighbor relation information, UE performance information such as 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 using existing measurements or via OAM configuration.

[0079] In various embodiments, examples of how network energy cost information may be included are described in more detail below.

[0080] In various embodiments, the network energy cost information may include: measured network energy cost information per UE per slice, which may be obtained from the gNB-DU to determine energy saving decisions within the NG-RAN. Energy saving decisions may be requested for training AI / ML models or as part of feedback information for AI / ML models. This information may also be obtained through periodic signaling or upon request (e.g., to monitor energy costs associated with the UE based on changes in radio conditions). In various embodiments, in the case of dual connectivity, information may be obtained from a secondary node (e.g., NG-RAN node 2) to determine the network energy cost associated with the SCG (Secondary Cell Group) and used to decide whether to maintain the UE in dual connectivity.

[0081] In various embodiments, the information may include per-UE per-slice predicted network energy cost information, which may be obtained from the gNB-DU and / or from the secondary node (NG-RAN Node 2) in the case of dual connectivity to anticipate traffic-aware energy conservation decisions within the NG-RAN. The gNB-DU and / or secondary node may determine this information based on expected UE traffic and radio conditions. The per-UE per-slice predicted network energy cost information obtained from the secondary node (NG-RAN Node 2) may be used to determine future network energy costs associated with the SCG (Secondary Cell Group) and to determine whether the UE should maintain dual connectivity in the future, and thus plan future slice resource allocations for scenarios where the UE can be fully served in a single connection.

[0082] In various embodiments, this information may be measured network energy cost information per cell per slice, obtained from the gNB-DU to determine energy saving actions within the NG-RAN for a group of UEs determined by the serving cell(s) and / or S-NSSAI(s), and / or obtained from the secondary node (NG-RAN Node 2) in the case of dual connectivity to determine the network energy cost associated with UEs served via the SCG (Secondary Cell Group). This information may be used to assess the total cost of maintaining the UE in dual connectivity.

[0083] In various embodiments, this information can be per-cell per-slice predicted network energy cost information, 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 the case of dual connectivity to determine the network energy cost associated with UEs served via the SCG (Secondary Cell Group). This information can be used to assess the total cost of maintaining the UE in dual connectivity.

[0084] In various embodiments, the NG-RAN node is divided into a gNB-CU-CP (or gNB-CU) and a gNB-DU, and the gNB-DU performs energy-saving actions. In this case, the gNB-CU-CP can retrieve measured network energy cost information relative to the energy-saving actions from the gNB-DU at a "per-UE per-slice" granularity. The network energy cost can be reported via a list of S-NSSAIs. The network energy cost can also be reported via a list of cells, for example, if carrier aggregation is used or a UE is served in the case of consecutive intra-gNB-DU handovers.

[0085] According to the brief description, Figure 4 is a diagram of an example embodiment of signals and operations between a UE, a gNB-CU-CP, and a gNB-DU according to one illustrated aspect of the present disclosure. In various embodiments, Figure 4 The components depicted in may correspond to those described above in Figure 1 and Figure 2 It should be understood that the described signals may have associated operations, and the described operations may have associated signals.

[0086] At step 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 the gNB-CU measurement ID and may include measurement configuration information. In various embodiments, the measurement configuration request message includes a bitmap including the nth bit for an action associated with network energy cost measured for the UE.

[0087] At step 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 the gNB-CU measurement ID and may include one or more of the following: the gNB-DU measurement ID and / or a failed reporting characteristics bitmap. In various embodiments, operations 401 and 402 may be measurement configurations.

[0088] At step 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 the F1AP UE ID, a data collection ID including the gNB-CU measurement ID and the gNB-DU measurement ID, and / or parameters for the action. Based on 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 measurement collection triggers.

[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 the gNB-CU measurement ID, the gNB-DU measurement ID, the F1AP UE ID, and the measured network energy cost per UE associated with the per-cell per-slice action. In various embodiments, operation 405 is a measurement report. In other examples, the gNB-DU reports the measured network energy cost per UE, which is associated with the overall per-slice action for all cells serving the UE. The gNB-CU-CP can then determine the measured network energy cost per UE associated with the per-cell per-slice action based on, for example, information about the UE's carrier aggregation already available in the gNB-CU-CP.

[0090] In various embodiments, the measurement configuration request / response message may be implemented as, for example, a F1AP resource status request / response message (e.g., as described in TS 38.473). In various embodiments, the data collection request / response message in XnAP may also be introduced into F1AP to implement the measurement configuration request / response message. Similarly, the measurement report may be implemented as, for example, a F1AP resource status update message, or the XnAP message data collection update may also be introduced into F1AP.

[0091] Figure 4 The operations are illustrative only, and variations are contemplated within the scope of this disclosure. In an embodiment, the operations may include Figure 4 Other operations not shown in FIG. In an embodiment, the operation may not include Figure 4 In an embodiment, each operation shown in FIG. Figure 4 Such and other embodiments are contemplated to be within the scope of this disclosure. Those skilled in the art will appreciate that although various example components are described as performing various functions, other components may perform Figure 4 Those functions described in .

[0092] According to the brief description, Figure 5 is a diagram of an example embodiment of signals and operations between a UE, a gNB-CU-CP, and a gNB-DU according to another illustrated aspect of the present disclosure. In various embodiments, Figure 5 The components depicted in may correspond to those described above in Figure 1 and Figure 2 It should be understood that the described signals may have associated operations, and the described operations may have associated signals.

[0093] In step 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 predicted time. In various embodiments, the measurement configuration request message includes a bitmap including the nth bit for the measured network energy cost for the UE and the mth bit for the predicted network energy cost for the UE. In some examples, the gNB-CU-CP requests that only the measured energy cost 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] In step 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: the gNB-DU Measurement ID and / or a Failed Reporting Characteristics Bitmap. In various embodiments, operations 501 and 502 may be measurement configurations.

[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 message includes one or more of the following: F1AP UE ID, data collection, gNB-CU measurement ID, and / or gNB-DU measurement ID. Based on the received action request, an RRC connection establishment / re-establishment / resuming operation may be initiated at operation 504. In various embodiments, operations 503 and 504 may be measurement collection triggers.

[0096] At operations 506 and 507, 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 may include one or more of the following: a gNB-CU-CP measurement ID, a gNB-CU-UP measurement ID, and a per-cell per-slice per-UE network energy cost (measured and / or predicted). In various embodiments, operations 506 and 507 may be measurement reports. In other examples, the gNB-DU reports a per-UE network energy cost (measured or predicted) associated with the overall per-slice action for all cells serving the UE. The gNB-CU-CP may then determine the per-UE measured network energy cost associated with the per-cell per-slice action based on, for example, information about the UE's carrier aggregation already available in the gNB-CU-CP. The measurement report includes the (measured or predicted) network energy cost for one or more UEs that connected, re-established, or resumed their RRC connection at operation 504.

[0097] Therefore, the gNB-CU-CP triggers periodic collection of per-UE per-slice measurements and predicted network energy costs, thereby receiving periodic measurements that can account for changes in, for example, UE radio conditions. The gNB-CU-CP configures such periodic signaling using, for example, Measurement Configuration Request / Response messages and indicates to which UE the measurement configuration applies during the F1AP UE Context Setup Request message. The (measured or predicted) network energy costs can be reported on a list of S-NSSAIs. If carrier aggregation is used or the UE is served in the case of consecutive intra-gNB-DU handovers, the (measured or predicted) network energy costs can also be reported on a list of cells.

[0098] Figure 5 A measurement configuration request is shown from the gNB-CU-CP to the gNB-DU requesting reporting of measured / predicted energy costs for a UE. The configuration may include additional bits to indicate the measured network energy cost for the UE and the predicted network energy cost for the UE. The configuration from the gNB-CU-CP may include timing information regarding the reporting, i.e., whether the reporting will occur once or periodically. Periodic reporting may be indicated by including a Report Periodicity IE within the Measurement Configuration Request message. In the response, the Measurement Configuration Response message, the gNB-DU may include its measurement ID and a bitmap indicating whether some measurements requested by the gNB-CU may not be initiated. This may be accomplished by including a Failure Reporting Characteristics bitmap in the response message, indicating measurements that could not be initiated by the gNB-DU with the appropriate cause value for the failure reason by setting the corresponding entry to 1.

[0099] Figure 5The operations are illustrative only, and variations are contemplated within the scope of this disclosure. In an embodiment, the operations may include Figure 5 Other operations not shown in FIG. In an embodiment, the operation may not include Figure 5 Each operation shown in . In an embodiment, it can be Figure 5 Such and other embodiments are contemplated to be within the scope of this disclosure. Those skilled in the art will appreciate that although various example components are described as performing various functions, other components may perform Figure 5 Those functions described in .

[0100] According to the brief description, Figure 6 is a diagram of an example embodiment of signals and operations between a UE, a gNB-CU-CP, and a gNB-DU according to another illustrated aspect of the present disclosure. In various embodiments, Figure 6 The components depicted in may correspond to those described above in Figure 1 and Figure 2 It should be understood that the described signals may have associated operations, and the described operations may have associated signals.

[0101] 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: UE F1AP ID, an indication of whether measured, predicted, or both measured and predicted energy costs are requested, and, in the case of prediction, a predicted time at which the prediction should be taken. In some examples, the gNB-CU-CP only requests that the measured energy cost be reported by the gNB-DU. In these examples, the gNB-CU-CP may determine the predicted network energy cost based on traffic information and available radio condition information retrieved from the gNB-CU-UP.

[0102] 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 F1AP ID, and (measured and / or predicted) per-cell per-slice per-UE network energy cost. In various embodiments, the (measured or predicted) network energy cost may be reported on a list of S-NSSAIs. Additionally, the (measured or predicted) network energy cost may be reported on a list of cells (e.g., if carrier aggregation is used to serve the UE).

[0103] Figure 6 The operations are illustrative only, and variations are contemplated within the scope of this disclosure. In an embodiment, the operations may include Figure 6 Other operations not shown in FIG. In an embodiment, the operation may not include Figure 6 Each operation shown in . In an embodiment, it can be Figure 6 Such and other embodiments are contemplated to be within the scope of this disclosure. Those skilled in the art will appreciate that although various example components are described as performing various functions, other components may perform Figure 6 Those functions described in .

[0104] In various embodiments, NG-RAN node 1 triggers periodic collection of measured and predicted network energy costs at NG-RAN node 2 for the purpose of monitoring energy costs associated with dual connectivity, and thus receives periodic measurements that can be taken into account with changes (e.g., UE radio conditions). NG-RAN node 1 configures such periodic signaling using Measurement Configuration Request / Response messages and indicates in an XnAP SN Add message which UE the measurement configuration applies to. Network energy costs (measured or predicted) may be reported on the S-NSSAI list. Network energy costs (measured or predicted) may also be reported on the cell list, for example, if carrier aggregation is used to serve the UE, or if the measurement report covers one or more changes to the PSCell for the UE.

[0105] According to the brief description, Figure 7 is a diagram of an example embodiment of signals and operations between a UE and an NG-RAN according to one illustrative aspect of the present disclosure. In various embodiments, Figure 7 The components depicted in may correspond to those described above in Figure 1 and Figure 2 It should be understood that the described signals may have associated operations, and the described operations may have associated signals.

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

[0107] At step 702, NG-RAN 2 transmits a measurement configuration response message to NG-RAN 1, and 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: an NG-RAN 1 measurement ID, an 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, such as a measurement configuration report initiation procedure.

[0108] At step 703, NG-RAN 1 transmits an SN Add message to NG-RAN 2, and NG-RAN 2 receives the SN Add message. In various embodiments, the SN Add message includes the XnAP UE ID and a data collection ID including the NG-RAN 1 measurement ID and the NG-RAN 2 measurement ID. Based on the received SN Add message, SCG establishment occurs at operation 704. In various embodiments, operations 703 and 704 may be measurement collection triggers.

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

[0110] Figure 7 The operations are illustrative only, and variations are contemplated within the scope of this disclosure. In an embodiment, the operations may include Figure 7 Other operations not shown in FIG. In an embodiment, the operation may not include Figure 7 Each operation shown in . In an embodiment, it can be Figure 7 Such and other embodiments are contemplated to be within the scope of this disclosure. Those skilled in the art will appreciate that although various example components are described as performing various functions, other components may perform Figure 7 Those functions described in .

[0111] According to the brief description, Figure 8 is a diagram of an example embodiment of signals and operations between a UE and an NG-RAN according to another illustrated aspect of the present disclosure. In various embodiments, Figure 8 The components depicted in may correspond to those described above in Figure 1 and Figure 2 It should be understood that the described signals may have associated operations, and the described operations may have associated signals.

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

[0113] At step 802, NG-RAN 2 transmits a UE Energy Cost Response message to NG-RAN 1, and 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: (measured and / or predicted) network energy cost per cell per slice per UE. In various embodiments, the (measured or predicted) network energy cost may be reported on a list of S-NSSAIs. Additionally, the network energy cost (measured or predicted) may be reported on a list of cells, for example, if carrier aggregation is used to serve the UE, or if the measurement report covers one or more changes to the PSCell for the UE.

[0114] Figure 8 The operations are illustrative only, and variations are contemplated within the scope of this disclosure. In an embodiment, the operations may include Figure 8 Other operations not shown in FIG. In an embodiment, the operation may not include Figure 8 In an embodiment, each operation shown in FIG. Figure 8 Such and other embodiments are contemplated to be within the scope of this disclosure. Those skilled in the art will appreciate that although various example components are described as performing various functions, other components may perform Figure 8 Those functions described in .

[0115] In various embodiments, the gNB-CU-CP triggers periodic collection of per-cell, per-slice measurements and predicted network energy costs, thereby receiving periodic measurements that can 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 this 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 can report the requested information for all of its cells. For example, if carrier aggregation is used to serve the UE, the (measured or predicted) network energy costs can be reported on the cell list. The (measured or predicted) network energy costs can be reported on the S-NSSAI list.

[0116] Figure 9 is a diagram of an example embodiment of signals and operations between a UE, a gNB-CU-CP, and a gNB-DU according to another illustrated aspect of the present disclosure. In various embodiments, Figure 9 The components depicted in may correspond to those described above in Figure 1 and Figure 2 It should be understood that the described signals may have associated operations, and the described operations may have associated signals.

[0117] At step 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 the gNB-CU measurement ID and may include one or more of the following: measurement configuration, reporting period, predicted time, S-NSSAI list, and / or a list of cell IDs. In various embodiments, the measurement configuration request message includes a bitmap including the nth bit for the measured slice network energy cost and the mth bit for the predicted slice network energy cost. In some examples, the gNB-CU-CP requests only the 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 and available radio condition information retrieved from the gNB-CU-UP.

[0118] At step 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 the gNB-CU Measurement ID and may include one or more of the following: the gNB-DU Measurement ID and / or a Failed Reporting Characteristics Bitmap. In various embodiments, operations 901 and 902 may be measurement configurations.

[0119] At operations 903 and 904, 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 may include one or more of the following: a gNB-CU-CP measurement ID, a gNB-DU measurement ID, and a per-cell per-slice network energy cost (measured and / or predicted). In other examples, the gNB-DU reports the per-slice (measured and / or predicted) network energy cost aggregated across all cells served by the gNB-DU. The gNB-CU-CP may then determine the per-cell per-slice (measured and / or predicted) network energy cost based on, for example, cell load information already available in the gNB-CU-CP. In various embodiments, operations 903 and 904 may be measurement reports.

[0120] Figure 9 The operations are illustrative only, and variations are contemplated within the scope of this disclosure. In an embodiment, the operations may include Figure 9 Other operations not shown in FIG. In an embodiment, the operation may not include Figure 9 In an embodiment, each operation shown in FIG. Figure 9 Such and other embodiments are contemplated to be within the scope of this disclosure. Those skilled in the art will appreciate that although various example components are described as performing various functions, other components may perform Figure 9 Those functions described in .

[0121] In various embodiments, NG-RAN node 1 triggers periodic collection of measured and predicted network energy costs per cell and per slice at NG-RAN node 2 for the purpose of monitoring current and future energy costs associated with maintaining a UE in dual connectivity. NG-RAN node 1 configures such periodic signaling using a measurement configuration request / response message. If a list of PSCell IDs is not included in the measurement configuration request message, NG-RAN node 2 may include the PSCells used by NG-RAN node 2 for UEs for which NG-RAN node 1 is the primary node. In one example, in the case of carrier aggregation, the network energy cost in the SCell may be reported together with the network energy cost in the PSCell. If carrier aggregation is used to serve the UE, the (measured or predicted) network energy cost may be reported on a cell list. The (measured or predicted) network energy cost may be reported on an S-NSSAI list.

[0122] In various embodiments, NG-RAN node 1 may determine whether dual connectivity is beneficial with respect to the network energy cost metric for the selected UE in the slice of a given cell, or whether it should be deactivated. Similarly, in the case of carrier aggregation, NG-RAN2 may observe the network energy cost on its cells and determine (through internal actions) to maintain CA or deactivate it.

[0123] According to the brief description, Figure 10 is a diagram of an example embodiment of signals and operations between a UE and an NG-RAN according to another illustrated aspect of the present disclosure. In various embodiments, Figure 10 The components depicted in may correspond to those described above in Figure 1 and Figure 2 It should be understood that the described signals may have associated operations, and the described operations may have associated signals.

[0124] At step 1001, NG-RAN 1 transmits a measurement configuration request message to NG-RAN 2, and NG-RAN 2 receives the measurement configuration request message. In various embodiments, the measurement configuration request message includes the NG-RAN 1 measurement ID and may include one or more of the following: measurement configuration, reporting period, prediction time, a list of S-NSSAIs, and a list of cell IDs. In various embodiments, the measurement configuration request message includes a bitmap including the nth bit for slice network energy cost measured for dual connectivity and the mth bit for slice network energy cost predicted for dual connectivity.

[0125] At step 1002, NG-RAN 2 transmits a measurement configuration response message to NG-RAN 1, which is received by NG-RAN 1. In various embodiments, the measurement configuration response message includes: the NG-RAN 1 measurement ID, the NG-RAN 2 measurement ID, and a possible failure reporting characteristic bitmap. In various embodiments, operations 1001 and 1002 may be measurement configuration.

[0126] At operation 1003 , the UE is in dual connectivity, where NG-RAN 1 is the MN and NG-RAN 2 is the SN.

[0127] At operations 1004 and 1005, NG-RAN 2 transmits a measurement report to NG-RAN 1, and NG-RAN 1 receives the measurement report. In various embodiments, the measurement report may include one or more of the following: an NG-RAN 1 measurement ID, an NG-RAN 2 measurement ID, and a per-cell per-slice network energy cost for dual connectivity (measured and / or predicted). In various embodiments, operations 1004 and 1005 may be measurement reports. In various embodiments, the cells reported at 1004 and 1005 may be PSCells for UEs served in dual connectivity. In other examples, NG-RAN 2 reports the per-slice network energy cost for dual connectivity (measured and / or predicted) aggregated across all cells where NG-RAN 2 uses the UE as a secondary node and NG-RAN 1 is the primary node. In some examples, NG-RAN 1 may then estimate the per-cell per-slice network energy cost for dual connectivity (measured and / or predicted) based on, for example, UE traffic information already available in NG-RAN 1.

[0128] Figure 10 The operations are illustrative only, and variations are contemplated within the scope of this disclosure. In an embodiment, the operations may include Figure 10 Other operations not shown in FIG. In an embodiment, the operation may not include Figure 10 Each operation shown in . In an embodiment, it can be Figure 10 Such and other embodiments are contemplated to be within the scope of this disclosure. Those skilled in the art will appreciate that although various example components are described as performing various functions, other components may perform Figure 10 Those functions described in .

[0129] Operations are described below from the perspective of an apparatus, which in various embodiments may include an NG-RAN node, a distributed unit (gNB-DU) of the NG-RAN node, or a central unit (gNB-CU) of the same NG-RAN node. From such a perspective, a method may include receiving, by a first apparatus, a first message comprising a request for reporting energy cost per network slice. The first apparatus selects one or more user equipments (UEs) and transmits, to a second apparatus, a second message comprising a report of energy cost per network slice for the one or more UEs.

[0130] Now refer to Figure 11, a block diagram of example components of a UE or network device (e.g., of a RAN or core network) is shown. The device includes an electronic storage device 1110, a processor 1120, a network interface 1140, and a memory 1150. The various components can be communicatively coupled to each other. The processor 1120 can be and can 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 a chip (SoC), or any other type of processor. The memory 1150 can be a volatile type of memory, such as RAM, or a non-volatile type of memory, such as NAND flash memory. The memory 1150 includes processor-readable instructions that are executable by the processor 1120 to cause the device to perform various operations, including those mentioned herein, such as Figure 3-10 The operations described in .

[0131] Electronic storage 1110 may be and include any type of electronic storage for storing data, such as a hard drive, a solid-state drive, an optical disk, and / or other non-transitory computer-readable media, as well as other types of electronic storage. Electronic storage 1110 stores processor-readable instructions for causing the device to execute or be configured to cause the device to execute its operations, and also stores data associated with such operations, such as data related to the 5G NR standard and other data. Network interface 1140 may implement wireless networking technologies such as 5G NR and / or other wireless networking technologies.

[0132] Figure 11 The components shown are merely examples, and those skilled in the art will appreciate that the device includes other components not shown, and may include multiples of any of the components shown. Such and other embodiments are contemplated within the scope of the present disclosure. For example, a transmitter and a receiver may be included as components for transmitting and receiving signals.

[0133] Other embodiments of the present disclosure include the following embodiments.

[0134] Example 1. A method for communication, comprising: receiving, by a first device, a first message comprising a request to report energy cost per network slice; selecting, by the first device, one or more user equipments (UEs); and A second message is transmitted by the first device to the second device, the second message including a report of energy cost per network slice for one or more UEs.

[0135] Example 2. The method of example 1, wherein the first message is received from the second device.

[0136] Example 3. A method according to Example 1 or 2, wherein the first message includes a request for energy cost per network slice for at least a first UE among the one or more UEs, and wherein the second message includes a report for energy cost per network slice for the first UE among the one or more UEs.

[0137] Example 4. A method according to Example 1 or 2, wherein the report includes energy costs for multiple network slices.

[0138] Example 5. The method of Example 1 or 2, wherein selecting one or more UEs comprises: receiving, by the first device, in a first message, an action associated with an energy cost per network slice; receiving, by the first device, a third message associated with the UE, the UE corresponding to the action requested in the first message; and One or more UEs are selected based on the first message and the third message for transmission of the second message.

[0139] Example 6. The method of Example 1 or 2, wherein selecting one or more UEs comprises: receiving, by the first device, identifiers of one or more UEs in a first message; A UE is selected for transmission of the second message based on an identifier of the one or more UEs.

[0140] Example 7. The method of Example 1 or 2, wherein selecting one or more UEs comprises: Any UE served by the first device and involved in the relevant slice is selected within a configured time period.

[0141] Example 8. A method according to Example 1 or 2, wherein the second message includes a report of energy cost per network slice per cell on a list of cells for one or more UEs.

[0142] Example 9. The method of Example 8, wherein the list of cells is received in the first message.

[0143] Example 10. The method of Example 8, wherein the list of cells corresponds to cells that have been used by the first apparatus as primary secondary cells (PSCells) for one or more UEs in a dual connectivity scenario in which the second apparatus acts as a master node.

[0144] Example 11. The method of Example 1 or 2, wherein the reported energy cost per network slice corresponds to an energy cost per cell on a list of cells used for carrier aggregation for one or more UEs.

[0145] Example 12. The method of example 1 or 2, further comprising: receiving a list of one or more slices in a first message; and The energy cost for the one or more UEs for each slice included in the received list of slices is reported in the second message.

[0146] Example 13. A method according to Example 1 or 2, wherein the request for energy cost per network slice is a request for measured energy cost per UE or a request for predicted energy cost per UE.

[0147] Example 14. The method of Example 1 or 2, 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.

[0148] Example 15. The method of Example 1 or 2, wherein the first apparatus is a distributed unit of an NG-RAN node (gNB-DU) and the second apparatus is a central unit of the same NG-RAN node (gNB-CU).

[0149] Example 16. The method of example 1 or 2, wherein the first device periodically transmits the second message to the second device.

[0150] Example 17. The method of Example 16, wherein the period for transmitting the second message has been received in the first message.

[0151] Example 18. The method of example 1 or 2, further comprising: receiving, by the second device from the first device, a second message comprising a report of energy cost per network slice for one or more UEs; and At least one energy saving action is performed by the second device on one or more UEs based on the received report.

[0152] Example 19. An apparatus for communication, comprising: at least one processor; and at least one memory, the at least one memory storing instructions that, when executed by the at least one processor, cause the apparatus to at least perform: receiving, by a first device, a first message comprising a request to report energy cost per network slice; selecting one or more user equipments (UEs); and A second message is transmitted by the first device to the second device, the second message including a report of energy cost per network slice for one or more UEs.

[0153] Example 20. An apparatus for communication, comprising: at least one processor; and At least one memory, the at least one memory storing instructions that, when executed by at least one processor, cause the apparatus to at least perform the method according to any one of Examples 1 to 18. Example 21. A processor-readable medium storing instructions that, when executed by at least one processor of an apparatus, cause the apparatus to at least perform the method according to any one of Examples 1 to 18.

[0154] The embodiments and aspects disclosed herein are examples of the present disclosure and can be embodied in various forms. For example, although some embodiments herein are described as separate embodiments, each embodiment herein can be combined with one or more other embodiments herein. The specific structural and functional details disclosed herein should not be interpreted as restrictive, but as the basis for the claims, and as a representative basis for teaching those skilled in the art to adopt the present disclosure differently in almost any appropriately detailed structure. Throughout the description of the drawings, the same reference numerals may refer to similar or identical elements.

[0155] The phrases "in one aspect," "in an aspect," "in various aspects," "in some aspects," or "in other aspects" may each refer to one or more of the same or different aspects according to the invention. The phrase "plurality" may refer to two or more.

[0156] In various embodiments, the terms "first message" and "second message," as well as any subsequent messages, may refer to any messages sent or received in sequence and are not necessarily limited to any particular message.

[0157] The phrases “in one embodiment,” “in an embodiment,” “in various embodiments,” “in some embodiments,” or “in other embodiments” may each refer to one or more of the same or different embodiments according to the present disclosure. Phrases of the form “A or B” mean “(A), (B), or (A and B).” Phrases of the form “at least one of A, B, or C” mean “(A); (B); (C); (A and B); (A and C); (B and C); or (A, B, and C).”

[0158] Any method, program, algorithm or code described herein can be converted into a programming language or computer program or represented in a programming language or computer program. As used herein, the terms "programming language" and "computer program" include any language for specifying instructions to a computer, and include, but are not limited to, the following languages ​​and their derivatives: assembler, Basic, batch file, BCPL, C, C+, C++, Delphi, Fortran, Java, JavaScript, machine code, operating system command language, Pascal, Perl, PL1, Python, scripting language, Visual Basic, the metalanguage that specifies the program itself, and all first, second, third, fourth, fifth or other generation computer languages. Also included are databases and other data models and any other metalanguages. It does not distinguish between interpreted languages, compiled languages, or languages ​​that use both compiled and interpreted methods. It does not distinguish between compiled and source versions of a program. Therefore, when a programming language may exist in more than one state (such as source, compiled, object, or link), a reference to a program is a reference to any and all of these states. A reference to a program can encompass actual instructions and / or the intent of those instructions.

[0159] Although various aspects of the present disclosure have been illustrated in the accompanying drawings, this is not intended to be limited thereto, as the disclosure is intended to be as broad in scope as the art will allow, and the specification should be read similarly. Therefore, the above description should not be interpreted as limiting, but merely as illustrative of particular aspects. Those skilled in the art will envision other modifications within the scope and spirit of the appended claims.

Claims

1. A method for communication, comprising: Receiving, by a first device, a first message comprising a request to report energy cost per network slice; Selecting one or more user equipments UE by the first device; as well as A second message is transmitted by the first device to the second device, the second message including a report of the energy cost per network slice for the one or more UEs. The method of claim 1 , wherein the first message is received from a second device.

3. The method of claim 1 or 2, wherein the first message comprises a request for the energy cost per network slice for at least a first UE among the one or more UEs, and wherein the second message comprises a report for the energy cost per network slice for the first UE among the one or more UEs.

4. The method of claim 1 or 2, wherein the report includes the energy cost for multiple network slices.

5. The method according to claim 1 or 2, wherein selecting the one or more UEs comprises: receiving, by the first device, 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; as well as The one or more UEs are selected based on the first message and the third message for the transmission of the second message.

6. The method according to claim 1 or 2, wherein selecting the one or more UEs comprises: receiving, by the first apparatus, identifiers of one or more UEs in the first message; The UE is selected based on identifiers of the one or more UEs for the transmission of the second message.

7. The method according to claim 1 or 2, wherein selecting the one or more UEs comprises: Any UE involved in the slice that is served by the first device and is associated with is selected within a configured time period.

8. The method of claim 1 or 2, wherein the second message comprises a report of the energy cost per network slice for each cell on a list of cells for the one or more UEs.

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

10. The method of claim 8, wherein the list of cells corresponds to cells that have been used by the first apparatus as primary secondary cells (PSCells) for the one or more UEs in a dual connectivity scheme in which the second apparatus acts as a master node.

Images