Energy-saving execution for wireless communications

Abstract

In wireless communications, energy utilization may be improved by an energy saving technique that enables a mobile network to meet service requirements (including reliable coverage in which a user wants to access a service, sufficient capacity to meet service traffic requirements, and quality of service desired by a user quality of service (QoS)). The base station / cell may enter an energy saving state by turning off certain network devices. A network energy saving (NES) policy is transmitted and executed by a base station. The NES policy may be associated with a user equipment (UE), a network node, or a sub-network. The NES policy is used to limit the energy consumption rate or to perform the target network energy efficiency.

Description

Technical Field

[0001] This document generally relates to wireless communication. More specifically, it addresses potential improvements in energy-saving technologies within mobile device communication systems. Background Technology

[0002] Wireless communication technology is propelling the world towards an increasingly interconnected and networked society. Wireless communication relies on efficient network resource management and allocation between user mobile stations and wireless access network nodes (including but not limited to wireless base stations). Next-generation networks promise to provide high-speed, low-latency, and ultra-reliable communication capabilities, meeting the requirements of various industries and users. User mobile stations or user equipment (UEs) are becoming increasingly complex, and the amount of data being communicated is constantly increasing. To improve communication, meet the reliability requirements of vertical industries, and support next-generation network services, communication improvements are necessary.

[0003] 5G New Radio (NR) can be designed to enable denser network deployments. This network density leads to higher energy utilization. In the Radio Access Network (RAN), energy is likely consumed primarily by the base stations. For 5G telecom operators, energy consumption costs can be a significant portion of operational expense (OPEX). With the anticipated deployment of more base stations with massive MIMO (Multiple-Input Multiple-Output) capabilities, energy efficiency (EE) in NR becomes even more pressing and challenging. Summary of the Invention

[0004] This document relates to wireless communication methods, systems, and devices that can improve energy utilization. Energy-saving technologies must still enable mobile networks to meet service requirements, including reliable coverage for users to access services, sufficient capacity to meet service traffic demands, and quality of service (QoS) expectations. Examples include energy-saving technologies that support different energy states and dynamically change the cell's energy state without compromising QoS while maintaining user satisfaction. To save network energy consumption and achieve "green communication," base stations / cells can enter an energy-saving state by shutting down certain network devices (e.g., power amplifiers, transceivers, and other network components). However, such energy-saving measures may negatively impact the QoS provided to users. The described energy-saving implementation examples avoid user dissatisfaction with QoS while ensuring network energy efficiency. These examples include network energy saving (NES) policies transmitted and executed by the base station. NES policies can be associated with user equipment (UE), network nodes, or subnetworks. NES policies are used to limit energy consumption rates or achieve target network energy efficiency.

[0005] In one embodiment, the wireless communication method includes: receiving a network energy saving (NES) policy at a network base station, the NES policy being associated with a user equipment (UE), a network node, or a sub-network; and having the network base station utilize the NES policy to limit energy consumption rate or perform a target network energy efficiency.

[0006] In one embodiment, a wireless communication device includes a processor and a memory, and the processor is configured to read code from the memory and implement any of the embodiments described above.

[0007] In one embodiment, a computer program product includes a computer-readable program medium on which code is stored, the code, when executed by a processor, causing the processor to implement any of the embodiments described above.

[0008] In some embodiments, a wireless communication device includes a processor and a memory, wherein the processor is configured to read code from the memory and implement any method described in any of the plurality of embodiments. In some embodiments, a computer program product includes a computer-readable program medium on which code is stored, the code, when executed by a processor, causes the processor to implement any method described in any of the plurality of embodiments. The above and other aspects and embodiments thereof are described in more detail in the accompanying drawings, specification, and claims. Attached Figure Description

[0009] Figure 1 An example base station is shown; Figure 2 An example random access (RA) message sending and receiving environment is shown; Figure 3 The network architecture of the base station centralized unit (CU) and the base station distributed unit (DU) is shown; Figure 4 An embodiment of a wireless network system architecture is illustrated; Figure 5 An example of a communication message with a network power saving (NES) policy associated with a user equipment (UE) is shown; Figure 6 An example of a communication message for a network power saving (NES) strategy associated with a user equipment (UE) is shown between a centralized unit (CU) and a distributed unit (DU) base station; Figure 7 An example of a communication message with a user equipment (UE) associated network power saving (NES) strategy utilizing dual connections between a master node (MN) and a secondary node (SN) is illustrated. Figure 8 An example of communication messages with network power saving (NES) strategies associated with network nodes is shown; Figure 9 An example of communication messages for a network energy saving (NES) strategy with sub-network association between neighboring base stations is shown. Detailed Implementation

[0010] This disclosure will now be described in detail below with reference to the accompanying drawings, which form a part of this disclosure and illustrate specific examples of embodiments by way of illustration. However, it should be noted that this disclosure may be embodied in various different forms, and therefore the subject matter covered or claimed is intended to be construed as not being limited to any of the embodiments set forth below.

[0011] Throughout the specification and claims, terms may have suggestive or implied meanings in the context, in addition to their expressly stated meanings. Similarly, the phrases “in one embodiment” or “in some embodiments” as used herein do not necessarily refer to the same embodiment, and the phrases “in another embodiment” or “in other embodiments” as used herein do not necessarily refer to different embodiments. For example, the claimed subject matter is intended to encompass, in whole or in part, exemplary embodiments or combinations of embodiments.

[0012] Generally, terms can be understood at least in part from their usage in the context. For example, terms such as “and,” “or,” or “and / or” as used herein can include a variety of meanings that may depend at least in part on the context in which they are used. Typically, “or,” when used in a list of associations (such as A, B, or C), is intended to mean A, B, and C (used herein in an inclusive sense) and A, B, or C (used herein in an exclusive sense). Furthermore, depending at least in part on the context, the terms “one or more” or “at least one” as used herein may be used to describe any feature, structure, or characteristic in a singular sense, or may be used to describe a combination of features, structures, or characteristics in a plural sense. Similarly, depending at least in part on the context, terms such as “a,” “an,” or “the” can be understood to convey either a singular or a plural usage. Furthermore, the terms “based on” or “determined by” can be understood as not necessarily intended to convey an exclusive set of factors, but rather, at least in part, depending on the context, may allow for additional factors that are not necessarily explicitly described.

[0013] Energy Saving (ES) state can be a state in which certain functions of a cell or network are turned off. To achieve energy saving or green RAN, energy-saving technologies (e.g., shutting down cells with no or very low load during off-peak conditions) can be used to reduce network energy consumption. Enhanced ES technology can achieve this by shutting down some cell equipment (including but not limited to power amplifiers, transceivers, and other network components) instead of shutting down the entire cell. This allows a cell to enter an energy-saving state while still providing some cell capacity. A cell can enter another energy-saving state with different cell capacities by shutting down more or fewer devices.

[0014] Energy conservation must still ensure that mobile networks can meet service requirements. Energy conservation must provide: reliable coverage where users want to access services, sufficient capacity to meet service traffic demands, and the quality of service (QoS) expected by users. When 5G RAN or base stations support different energy states and dynamically change cell energy states to conserve network energy, network coverage, capacity, and the QoS provided to users may be affected. The energy-saving techniques / solutions described in the following embodiments aim to maintain user satisfaction without compromising QoS.

[0015] Radio resource control (RRC) is a protocol layer at the IP level (Network Layer) between the UE and the base station. Various RRC states can exist, such as RRC_CONNECTED, RRC_INACTIVE, and RRC_IDLE. RRC messages are transmitted via the Packet Data Convergence Protocol (PDCP). As described, the UE can transmit data via either the Random Access Channel (RACH) protocol scheme or the Configured Grant (CG) scheme. CG can be used to reduce the waste of periodically allocated resources by enabling multiple devices to share periodic resources. The base station or node can allocate CG resources to eliminate packet transmission latency and improve the utilization of allocated periodic radio resources. The CG scheme is merely one example of a protocol scheme used for communication, and other examples, including but not limited to RACH, are possible. The wireless communication described herein can be implemented via radio access. Figures 1 to 4 An example of an energy-efficient radio access network (RAN) node (e.g., a base station) and user equipment and messaging environment applicable to the description below is shown.

[0016] Figure 1 Example base station 102 is shown. This base station can also be referred to as a wireless network node, and can be... Figure 1 as well as Figures 4 to 9The network nodes shown are (e.g., master node (MN), secondary node (SN), and source / target node). Base station 102 can also be identified as a nodeB (NB, e.g., eNB or gNB) in the mobile telecommunications context. An example base station may include a wireless Tx / Rx circuit 113 for receiving and transmitting with user equipment (UE) 104. The base station may also include a network interface circuit 116 coupling the base station to the core network 110, such as an optical interconnect or wired interconnect, Ethernet, and / or other data transmission media / protocols.

[0017] The base station may also include system circuitry 122. System circuitry 122 may include one or more processors 124 and / or memory 126. Memory 126 may include operations 128 and control parameters 130. Operations 128 may include instructions for execution on one or more processors in processor 124 to support base station operation. For example, operations may process random access transmission requests from multiple UEs. Control parameters 130 may include parameters or may support the execution of operations 128. For example, control parameters may include network protocol settings, random access messaging format rules, bandwidth parameters, radio frequency mapping allocation, and / or other parameters.

[0018] Figure 2 An example random access messaging environment 200 is illustrated. In this environment, UE 104 can communicate with base station 102 via random access channel 252. In this example, UE 104 supports one or more Subscriber Identity Modules (SIMs), such as SIM1 202. Electrical and physical interfaces 206 connect SIM1 202 to the rest of the user equipment hardware, for example, via system bus 210.

[0019] Mobile device 200 includes a communication interface 212, system logic 214, and user interface 218. System logic 214 may include any combination of hardware, software, firmware, or other logic. System logic 214 may be implemented, for example, using one or more system-on-a-chip (SoC), application-specific integrated circuit (ASIC), discrete analog and digital circuits, and other circuits. System logic 214 is part of the implementation of any desired functionality in UE 104. In this regard, system logic 214 may include logic that facilitates operations such as: decoding and playing music and video (e.g., MP3, MP4, MPEG, AVI, FLAC, AC3, or WAV decoding and playback); running applications; accepting user input; saving and retrieving application data; establishing, maintaining, and terminating cellular phone calls or data connections (e.g., for internet connections); establishing, maintaining, and terminating wireless network connections, Bluetooth connections, or other connections; and displaying relevant information on user interface 218. User interface 218 and input 228 may include a graphical user interface, a touch-sensitive display, haptic feedback or other haptic output, voice or facial recognition input, buttons, switches, speakers, and other user interface elements. Additional examples of input 228 include microphones, video and still image cameras, temperature sensors, vibration sensors, rotation and orientation sensors, headphone and microphone input / output jacks, Universal Serial Bus (USB) connectors, memory card slots, radiation sensors (e.g., IR sensors), and other types of input.

[0020] System logic 214 may include one or more processors 216 and memory 220. Memory 220 stores, for example, control instructions 222 executed by processor 216 to achieve the desired functions of UE 104. Control parameters 224 provide and specify operational options and configurations for the control instructions 222. Memory 220 may also store any BT, WiFi, 3G, 4G, 5G, or other data 226 that UE 104 will send or has received via communication interface 212. In various embodiments, system power may be provided by a power storage device such as battery 282.

[0021] In communication interface 212, radio frequency (RF) transmission (Tx) and reception (Rx) circuitry (Tx / Rx circuitry) 230 processes the transmission and reception of signals via one or more antennas 232. Communication interface 212 may include one or more transceivers. The transceiver may be a wireless transceiver, which includes modulation / demodulation circuitry, a digital-to-analog converter (DAC), a shaper, an analog-to-digital converter (ADC), filters, waveform shapers, preamplifiers, power amplifiers, and / or other logic for transmission and reception via one or more antennas or (for some devices) via a physical (e.g., wired) medium.

[0022] The transmitted and received signals may follow any of a variety of formats, protocols, modulations (e.g., QPSK, 16-QAM, 64-QAM, or 256-QAM), channels, bit rates, and encodings. As a specific example, communication interface 212 may include a transceiver supporting transmission and reception under 2G, 3G, BT, WiFi, Universal Mobile Telecommunications System (UMTS), High Speed ​​Packet Access (HSPA)+, and 4G / Long Term Evolution (LTE) standards. However, the technologies described below, whether originating from the 3rd Generation Partnership Project (3GPP), the GSM Association, 3GPP2, IEEE, or other partners or standards bodies, are applicable to other wireless communication technologies.

[0023] Multiple RAN nodes (e.g., eNB, gNB) using the same or different radio access technologies (RATs) can be deployed on the same or different frequency carriers in certain geographical areas, and multiple RAN nodes can cooperate with each other through dual connectivity operation to provide joint communication services to (one or more) the same target UE. A Multi-RAT Dual Connectivity (MR-DC) architecture can have a non-co-located primary node (“MN”) and secondary node (“SN”). The Access Mobility Function (AMF) and Session Management Function (SMF) can be control plane entities, and the User Plane Function (UPF) is a user plane entity in the New Radio Interface (“NR”) or 5GC. The signaling connection between the AMF / SMF and the primary node (“MN”) can be a Next Generation-Control Plane (NG-C) / MN interface. The signaling connection between the MN and the SN can be an Xn-Control Plane (“Xn-C”) interface. The signaling connection between the MN and the UE is the Uu-Control Plane ("Uu-C") RRC interface. All these connections manage the configuration and operation of the MR-DC. The user plane connection between the User Plane Function ("UPF") and the MN can be an NG-U (MN) interface instance.

[0024] Figure 3 The network architecture of the base station centralized unit (CU) and the base station distributed unit (DU) is shown. Figure 3 A base station (denoted as "gNB") communicating with the entire network ("5GC") is shown. Each base station can communicate with each other via a control plane interface ("Xn-C"). A base station is shown as having one CU, which is connected to two DUs via an F1 interface. This is merely an example of a base station arrangement. In some embodiments, there may be one or any number of DUs connected to a single CU.

[0025] A base station can be divided into two physical entities, called a centralized unit (“CU”) and a distributed unit (“DU”). Typically, the CU provides support for higher layers of the protocol stack (such as SDAP, PDCP, and RRC), while the DU provides support for lower layers (such as RLC, MAC, and the physical layer). In addition to the functions specifically assigned to the DU, the CU may include operations such as user data delivery, mobility control, radio access network sharing, and session management. One or more DUs are logical nodes with a subset of base station functions and can be controlled by the CU.

[0026] A CU can be a logical node of the RRC, SDAP, and PDCP protocols of a managed base station, or the RRC and PDCP protocols of a base station, used to control the operation of one or more DUs. A DU can be a logical node of the RLC, MAC, and PHY layers of a managed base station, and its operation can be at least partially controlled by the CU. A single DU can support one or more cells. However, each cell is supported by only a single DU. Each base station can support many cells. As described in the embodiments herein, cell mobility between cells can originate from different CUs or DUs, or can be within the CU and / or DU.

[0027] Figure 4 An embodiment of a wireless network system architecture is illustrated. This architecture is merely an example, and more or fewer components may be present to implement the embodiments described herein. Interconnections or communications between the components are identified as N1, N2, N4, N6, N7, N8, N10, and N11, and these interconnections or communications may be referenced in the specification or other drawings. Figure 2 Example user equipment (UE) 104 is shown. UE 402 is a device accessing a wireless network (e.g., 5GS) and obtains services through an NG-RAN node or base station 404. UE 402 interacts with the access and mobility control function (AMF) 406 of the core network via non-access stratum (NAS) signaling. Figure 1 Example base station 102 or NG-RAN is shown. NG-RAN node 404 is responsible for air interface resource scheduling and air interface connection management of the network accessed by the UE. AMF 406 includes the following functions: registration management, connection management, reachability management, and mobility management. AMF 406 also performs access authentication and access authorization. AMF 406 is a NAS secure terminal and relays session management NAS between UE 402 and SMF 408, etc.

[0028] SMF 408 includes the following functions: session management (e.g., session establishment, modification, and release), UE IP address allocation and management (including optional authorization), selection and control of uplink functions, downlink data notification, etc. User plane function (UPF) 410 includes the following functions: anchor points for intra-RAT / inter-RAT mobility, packet routing and forwarding, service usage reporting, QoS processing for the user plane, downlink packet buffering, and downlink data notification triggering, etc. Unified Data Management (UDM) 412 manages the UE's subscription profile. The subscription includes data for mobility management (e.g., restricted areas) and session management (e.g., QoS profiles). The subscription data also includes slice selection parameters, which are used by AMF 406 to select the appropriate SMF 408. AMF 406 and SMF 408 obtain subscriptions from UDM 412. Subscription data can be stored in a unified data repository using UDM 412, which uses this data when it receives a request from AMF 406 or SMF 408. The Policy Control Function (PCF) 414 includes functions such as supporting a unified policy framework to manage network behavior, providing policy rules to one or more control plane functions to enforce policy rules, and enabling front-end access to subscription information related to policy decisions in the user data repository. The Network Exposure Function (NEF) 416 is optionally deployed for exchanging information with external third parties. In one embodiment, the Application Function (AF) 416 can store application information in the unified data repository via the NEF. UPF 410 communicates with the data network 418.

[0029] The Access Mobility Function (AMF) and Session Management Function (SMF) are control plane entities, while the User Plane Function (UPF) is a user plane entity in New Radio (NR) or 5GC. The signaling connection between the AMF / SMF and the MN can be a Next Generation-Control Plane (NG-C) / MN interface. The signaling connection between the MN and the SN can be an Xn-Control Plane ("Xn-C") interface. The signaling connection between the MN and the UE can be a Uu-Control Plane ("Uu-C") RRC interface.

[0030] Figure 5 An example of a communication message with a Network Energy Saving (NES) policy associated with a User Equipment (UE) is illustrated. In block 502, the core network (CN) sends a message to the base station including the UE-associated Network Energy Saving (NES) policy. The UE-associated NES policy may be referred to as the UE NES policy. In one example, the NES policy is sent after the UE requests initial network access. In other examples, the NES policy may be sent when the UE context is updated / modified at the CN. For example, after the UE initiates a packet data unit (PDU) session resource establishment / modification request between the UE, the base station, and the CN, the CN sends an Initial Context Setup Request (INITIAL CONTEXT SETUP REQUEST) or a UE Context Modification Request (UE CONTEXT MODIFICATION REQUEST) message to the base station. In another example, the CN sends a PDU Session Setup / Modification Request (PDU SESSION SETUP / MODIFY REQUEST) message with the UE NES policy to the base station.

[0031] UE-associated Network Energy Saving (NES) policies In some embodiments, the UE NES policy at the base station can be configured by Operations, Administration and Maintenance (OAM). In some embodiments, the UE NES policy includes: • UE associated Maximum Energy Consumption Rate (UE MECR) information, which indicates the network energy consumption limit from the UE's perspective (i.e., "associated" with the UE); • UE-associated Target Energy Efficiency (UE TEE) information, which indicates the target or minimum network energy efficiency from the UE's perspective (i.e., "associated" with the UE); or • Add acceptable QoS information, which can indicate the acceptable quality of service (QoS) for the UE when the network is in an energy-saving state.

[0032] In some embodiments, the energy consumption rate may include the total amount of energy consumed by a certain number of network resources for a particular UE (“UE-associated” UE) or other UEs within a specific time interval (e.g., per second, per minute, per hour, or per day). Network resources may include, but are not limited to, one or more network slices, one or more network functions, or one or more network elements.

[0033] Network energy efficiency can be defined as the ratio between the service performance (i.e., data rate or latency) generated by the network and the energy consumed by network resources to provide services for a particular UE (“UE-associated” UE) or other UEs. The amount of data transmitted by the network can be used to measure the service provided by the network. In just one example, network energy efficiency = (data volume / energy) [bit / J] or [Mbit / kWh].

[0034] UE-associated maximum energy consumption rate (UE MECR) From the UE's perspective, UE NES policies can support maximum energy consumption rate (MECR) at different granularities or levels for the network resources used (e.g., network slices / network functions / network elements). This can be based on the UE, on the UE's allowed / used slices, on the UE's QoS flows (e.g., by service), or on the UE's Packet Data Unit (PDU) sessions. This can indicate energy consumption limits for specific network resources used by the corresponding UE. More specifically, this can include energy consumption limits for specific network resources used by the UE's allowed / used slices, UE's QoS flows, or UE's PDU sessions over a specific time interval.

[0035] The UE MECR information included in the UE NES policy may include at least one UE slice-level MECR for slices that the UE allows / uses, which can indicate network energy consumption limits for that allowed / used slice within a specific time interval. A UE can support one or more slices. The AMF can notify the UE of some of these supported slices via "one or more allowed slices". The base station can configure the UE to perform specific measurements related to its allowed slices and decide whether to request a change in the slices used by the UE based on these measurement results. The AMF can determine which slice is used for each PDU session of the UE. The AMF can configure this slice for the UE's PDU session; this slice may be referred to as the "used slice". UE subscription information may include the UE's optional slice MECR. This slice MECR may be referred to as the subscribed UE-slice-MECR of Single Network Slice Selection Assistance Information (S-NSSAI) and is used to uniquely identify the network slice. If a subscribed UE-slice-MECR is associated with an S-NSSAI in the subscription information, then when the CN provides the RAN with one or more allowed / used S-NSSAIs for a UE, the CN can provide the RAN with that subscribed UE-slice-MECR. For each allowed / used S-NSSAI, an optional subscribed UE-slice-MECR can be configured with that S-NSSAI.

[0036] In another example, the UE MECR information included in the UE NES policy may include a UE-level MECR for the UE, which may indicate a limit on the network energy consumption of the UE within a specific time interval (including the energy consumption of network resources used by all services of the UE).

[0037] In another example, the UE MECR information included in the UE NES policy may include at least one QoS flow level MECR of the UE's QoS flow, which may indicate a network energy consumption limit (including the energy consumption of network resources used by the UE's QoS flow) for the UE's QoS flow within a specific time interval.

[0038] In another example, the UE MECR information included in the UE NES policy may include at least one PDU session-level MECR for the UE's PDU session, which may indicate network energy consumption limits for the UE's PDU session within a specific time interval (including the energy consumption of network resources used by the UE's PDU session).

[0039] UE-associated target energy efficiency (UE TEE) From the UE's perspective, UE NES policies can support target energy efficiency (TEE) at different granularities or levels for the network resources used (e.g., network slices / network functions / network elements). This can be based on the UE, on the UE's allowed / used slices, on the UE's QoS flow, or on the UE's PDU session, and can indicate the TEE for a specific network resource corresponding to the UE, the UE's allowed / used slices, the UE's QoS flow, or the UE's PDU session.

[0040] UE TEE information may include at least one of the following: • At least one UE slice level TEE that the UE allows / has used a slice, which can indicate the target network energy efficiency or minimum network energy efficiency of the slice that the UE allows / has used (e.g., network efficiency can be derived by the ratio of the energy consumption of the slice that the UE allows / has used to the traffic data throughput of the slice in a specific time interval). • A UE-level TEE for the UE, which can indicate the UE's target network energy efficiency or minimum network energy efficiency (e.g., network efficiency is calculated by the ratio of the energy consumption of network resources used by all services of the UE to the UE's total traffic data throughput over a specific time interval). • At least one QoS flow level TEE for the UE's QoS flow, which can indicate the target network energy efficiency or minimum network energy efficiency of the UE's QoS flow (e.g., network energy efficiency is calculated by the ratio of the energy consumption of network resources used by the UE's QoS flow to the traffic data throughput of the QoS flow within a specific time interval); or • At least one PDU session level TEE of the UE’s PDU session, which can indicate the target network energy efficiency or minimum network energy efficiency of the UE’s PDU session (for example, network efficiency is calculated by the ratio of the energy consumption of network resources used by the UE’s PDU session to the traffic data throughput of the PDU session within a specific time interval).

[0041] Additional acceptable QoS information The additional acceptable QoS information included in the UE NES policy may include at least one additional alternative QoS parameter for a QoS flow. This alternative QoS parameter can indicate the acceptable quality of the QoS flow / service for the UE when the network is in an energy-saving state or when certain energy-saving schemes are applied. The 5G Quality of Service (QoS) model is based on QoS flows. Each QoS flow has a unique identifier called a QoS Flow Identifier (QFI). A QoS flow can be the finest granularity for distinguishing QoS in a PDU session. Each QoS flow has a QoS profile, which includes QoS parameters and QoS characteristics. The RAN will execute the QoS profile to ensure the quality of service provided to users. User plane (UP) traffic with the same QFI receives the same forwarding / scheduling processing based on the QoS parameters. To reduce network energy consumption, operators may offer users energy-saving "green communication" services. Energy-saving measures may also reduce the user's service quality. Therefore, if a user subscribes to a "green communication" service, the user agrees to slightly reduce the quality of that service to reduce network-side energy consumption. In other words, the user agrees to accept a lower QoS parameter for the service in order to save network energy. In energy-saving mode, the network may implement a lower QoS profile instead of the original QoS parameters, and users may also incur lower costs due to reduced network energy consumption.

[0042] Other acceptable QoS information included in the UE NES policy may include at least one "green communication" indication for a QoS flow configured with best-effort service, which can instruct the network to prioritize reducing the energy consumption of such best-effort service provided to the UE. Best-effort traffic is a type of traffic for which service performance levels cannot be guaranteed in any standard. If a user subscribes to "green communication" for best-effort service, the user agrees to a slight reduction in service quality to reduce energy consumption on the network side. Since service performance cannot be guaranteed for best-effort service, alternative QoS parameters for carrying the QoS flow of the best-effort service may not be necessary. The principle by which the network provides best-effort traffic to UEs in the network may be to provide any best service to these UEs on an equal footing, without guaranteeing the performance of these services. If a UE is indicated to have subscribed to "green communication" for a specific best-effort service, the network may reduce the resource allocation and data transmission scheduling priority for that UE's best-effort service to conserve network energy.

[0043] The additional acceptable QoS information included in the UE NES policy can also include a "green communication" indication for the UE, which can instruct the network to reduce the energy consumption of all best-effort services provided to the UE. This indication indicates that the UE has subscribed to "green communication" for best-effort services provided to the UE, and that the user agrees to slightly reduce the quality of all best-effort services to reduce network-side energy consumption. The network may then reduce resource allocation and data transmission scheduling priority for all best-effort services of the UE to conserve network energy.

[0044] Return to reference Figure 5 Block 504 includes the base station allocating / modifying network resources or the UE context at the base station for the UE's connection. The base station stores the received UE NES policy, or updates the stored UE NES policy using the most recently received UE NES policy. The base station successfully allocates or modifies network resources or the UE context at the base station for the UE's connection. Then, in block 506, the base station sends a success response message to the CN.

[0045] In block 508, the base station determines a power-saving strategy based on the UE NES policy and executes the received UE NES policy at the base station. The power-saving strategy includes at least the following actions: • If a UE slice-level MECR (and / or TEE) for a used slice is received, the base station should execute the network energy consumption rate (and / or target or minimum network energy efficiency) indicated by the MECR (and / or TEE) for that used slice on the UE. • If a UE slice level MECR (and / or TEE) is received that is not used for a UE slice, and if the base station decides to use the slice for the UE, the base station needs to consider the MECR (and / or TEE) for slice handover, and the base station should ensure that the energy consumption rate (and / or target or minimum network energy efficiency) indicated by the slice can be met after the handover; • If the UE-level MECR (and / or TEE) of the UE is received, the base station shall implement the energy consumption rate (and / or target or minimum network energy efficiency) of network resources for all services of the UE as indicated by the MECR (and / or TEE). • If the QoS level MECR (and / or TEE) of the QoS flow of the UE is received, the base station shall execute the energy consumption rate (and / or target or minimum network energy efficiency) indicated by the MECR (and / or TEE) of the network resources used for the QoS flow (service) of the UE. • If the PDU session level MECR (and / or TEE) of the UE's PDU session is received, the base station shall execute the energy consumption rate (and / or target or minimum network energy efficiency) indicated by the MECR (and / or TEE) of the network resources used for the UE's PDU session. • If additional alternative QoS parameters are received from the QoS stream, the base station must also ensure that the alternative QoS requirements of the service are met when the base station performs any power-saving actions (e.g., changing the power-saving status of the network / cell / slice, adjusting the user's data rate, or adjusting the user's scheduling resources). • If a "green communication" indication is received for a QoS flow configured with best-effort service, the network can reduce the resource allocation and data transmission scheduling priority for that UE's best-effort service (QoS flow) to save network energy; or • If a “green communication” instruction is received for a UE, the network can reduce the resource allocation and data transmission scheduling priority for all best-effort services (QoS flows) of the UE to save network energy.

[0046] RAN nodes can apply network energy consumption rate (and / or target network energy efficiency) to specific network resources. For example, this can be done by changing the energy-saving status of the network / cell / slice, adjusting user data rates, or adjusting user scheduling resources to reduce network energy consumption.

[0047] The base station collects energy consumption, energy efficiency, and / or quality of service (QoS) measurements (e.g., packet delay, data throughput, jitter, etc.) of specific network resources used by the UE on the base station, and assesses the UE's UE NES status information (including in the UE NES status report). In block 510, the base station sends a message including the corresponding UE NES status report to the CN or one or more trusted third parties. The customer or third party then determines network energy consumption-related information for the UE (e.g., energy consumption, energy consumption rate, or energy consumption efficiency), and / or the QoS provided by the network in a network energy-saving state to ensure that the QoS is acceptable in the network energy-saving state. Network operators can use this information to optimize network energy consumption and network performance.

[0048] In block 510, the UE NES status report may include one or more UE identifiers or QoS measurement results. UE identifiers may include: • Network energy consumption for measuring network resources of the UE; • Network energy consumption rate for measuring network resources used by the UE; • Network energy efficiency for measuring network resources used by the UE; • Measured network energy consumption of a specific UE slice and the corresponding slice identifier; • Measured network energy consumption rate of a specific slice of the UE and the corresponding slice identifier; • Measured network energy efficiency for a specific slice of the UE and the corresponding slice identifier; • Measurement of network energy consumption for specific QoS flows of the UE and the corresponding QoS flow identifier; • Measurement of network energy consumption rate of network resources for a specific QoS flow of the UE and the corresponding QoS flow identifier; • Measurement of network energy efficiency of network resources for a specific QoS flow of the UE and the corresponding QoS flow identifier; • Measurement of network energy consumption for specific PDU sessions of the UE and the corresponding PDU session identifier; • Measurement of network energy consumption rate of network resources for a specific PDU session of the UE and the corresponding PDU session identifier; or • Measurement of network energy efficiency of network resources for a specific PDU session of the UE and the corresponding PDU session identifier.

[0049] QoS measurements can include packet loss rate, data rate, transmission delay, jitter, etc. QoS measurements can be targeted at specific QoS flows / services of the UE and their corresponding QoS flow identifiers. When the network is in an energy-saving state, different energy-related quality of service can be provided to users by issuing additional acceptable QoS information. This can include not only energy consumption / efficiency information of network resources, but also associated quality of service provided to the UE, which is collected and (e.g., through UE NES status reports sent by the base station to the CN or a trusted third party) made available to the customer or authorized third party. This helps customers obtain a more intuitive understanding of network service quality under network energy conditions.

[0050] Figure 6An embodiment of a communication message with a Network Energy Saving (NES) policy associated with a User Equipment (UE) is illustrated between a Centralized Unit (CU) and a Distributed Unit (DU) base station. In block 602, the Core Network (CN) sends a message to the base station including the UE-associated NES policy. For example, the NES policy is sent after the UE requests initial network access. In other examples, the NES policy may be sent when the UE context is updated / modified at the CN. For example, after the UE initiates a PDU session resource establishment / modification request between the UE, the base station, and the CN, the CN sends an INITIAL CONTEXT SETUPREQUEST or UE CONTEXT MODIFICATION REQUEST message to the base station. In another example, the CN sends a PDU SESSION SETUP / MODIFY REQUEST message with the NES policy to the base station.

[0051] and Figure 5 The difference lies in Figure 6 In this example, the base station includes centralized units (CU) and distributed units (DU), as shown in the reference. Figure 3 As described. CU and DU can be two physical entities. In this example, the UE connects to the network through one or more base station DUs of the base station. In block 602, the base station CU receives a message sent by the CN, and simultaneously stores the UE NES policy included in the message, or updates the stored UE NES policy using the most recently received UE NES policy. In some embodiments, the base station CU determines new UE MECR and / or UE TEE information in the UE NES policy used by the base station DU. In block 604, the base station CU sends a UE CONTEXT SETUP REQUEST or UE CONTEXT MODIFICATION REQUEST to the base station DU via the F1 interface to set or modify the UE context (including the UE NES policy in the message) at the base station DU. (See reference...) Figure 5 The background and examples of UE NES policies are described. UE NES policies at the base station CU can be directly configured by the OAM.

[0052] In one embodiment, if the UE's traffic is transmitted only through the base station DU, the base station CU may need to consider the UE MECR and UE TEE corresponding to the UE at the base station CU and determine an appropriate UE MECR and / or UE TEE for the base station DU. The UE MECR and / or UE TEE relate to specific network resources serving the UE at the base station CU and base station DU, and may include the UE MECR and / or UE TEE corresponding to the UE NES policy sent by the core network (CN). If the energy consumed by the base station CU is much less than the energy consumed by the base station DU (the radio frequency (RF) is located in the base station DU, then the energy consumed by the base station DU may be much greater than the energy consumed by the base station CU), the base station does not need to determine a new UE MECR and UE TEE for the base station DU, but instead directly sends the received UE NES policy sent by the CN to the base station DU.

[0053] For example, if the UE's traffic is transmitted through more than one base station DU, the base station CU may need to consider the UE MECR and / or UE TEE corresponding to the UE at the base station CU, and then determine the appropriate UE MECR and / or UE TEE for multiple base station DUs, so that the UE MECR and / or UE TEE involved in the specific network resources served by the base station CU and the base station DU for the UE can satisfy the UE MECR and / or UE TEE corresponding to the UE NES policy sent by the CN.

[0054] In block 606, the base station DU allocates / modifies network resources. For example, this may include the UE context at the base station DU for UE connection. The base station DU stores the UE NES policy received from the base station CU. The base station CU successfully allocates or modifies network resources, or the UE context at the base station DU, for UE connection. Then, in block 608, the base station DU sends a success response message to the base station CU. Then, in block 610, the base station CU sends a success response message to the CN.

[0055] In block 612, the base station DU determines a power-saving strategy based on the UE NES policy and executes the received UE NES policy at the base station. The power-saving strategy includes at least the following actions: • If a UE slice-level MECR (and / or TEE) for a used slice is received, the base station DU should execute the network energy consumption rate (and / or target or minimum network energy efficiency) indicated by the MECR (and / or TEE) for that used slice for the UE. • If a UE slice level MECR (and / or TEE) is received that is not used for a UE slice, and if the base station DU decides to use the slice for the UE, the base station DU needs to consider the MECR (and / or TEE) for slice handover, and the base station DU should ensure that the indicated energy consumption rate (and / or target or minimum network energy efficiency) of the slice can be met after the handover. • If a UE-level MECR (and / or TEE) is received, the base station DU should execute the energy consumption rate (and / or target or minimum network energy efficiency) indicated by the MECR (and / or TEE) of network resources for all services of the UE. • If the QoS level MECR (and / or TEE) of the QoS flow of the UE is received, the base station DU shall execute the energy consumption rate (and / or target or minimum network energy efficiency) indicated by the MECR (and / or TEE) of the network resources for the QoS flow (service) of the UE. • If the PDU session level MECR (and / or TEE) of the UE's PDU session is received, the base station DU shall execute the energy consumption rate (and / or target or minimum network energy efficiency) of the network resources indicated by the MECR (and / or TEE) for the UE's PDU session. • If additional alternative QoS parameters are received from the QoS stream, the base station DU must also ensure that the alternative QoS requirements of the service can be met when it performs any power-saving actions (e.g., changing the power-saving status of the network / cell / slice, adjusting the user's data rate, or adjusting the user's scheduling resources). • If a "green communication" indication is received for a QoS flow configured with best-effort service, the network can reduce the resource allocation and data transmission scheduling priority for that UE's best-effort service (QoS flow) to save network energy; or • If a “green communication” instruction is received for the UE, the network can reduce the resource allocation and data transmission scheduling priority of all best-effort services (QoS flows) of the UE to save network energy.

[0056] Base station DUs can apply network energy consumption rate (and / or target network energy efficiency) to specific network resources. For example, this can be done by changing the energy-saving status of the network / cell / slice, adjusting user data rates, or adjusting user scheduling resources to reduce network energy consumption.

[0057] The base station DU collects energy consumption, energy efficiency, and / or quality of service (QoS) measurements (e.g., packet delay, data throughput, jitter, etc.) from the specific network resources used by the UE on the base station, and assesses the UE's UE NES status information (including in the UE NES status report). In block 614, the base station DU sends a message including the corresponding UE NES status report to the base station CU, which may send this message to the CN or a trusted third party. The customer or third party then determines the UE's network energy consumption information (e.g., energy consumption, energy consumption rate, or energy consumption efficiency), and / or the QoS provided by the network in a network power-saving state to ensure that the QoS is acceptable in this state. Network operators can use this information to optimize network energy consumption and network performance.

[0058] In some embodiments, the base station CU can collect energy consumption, energy efficiency measurement results, and / or service quality from one or more base station DUs for specific network resources used by the UE. The UE connects to one or more base station DUs via one or more UE NES status reports sent by the one or more base station DUs, and the base station CU evaluates the UE NES status information of the specific network resources involved (including in the UE NES status report). The base station CU determines the final UE NES status of the UE and then sends the corresponding final UE NES status report to the CN.

[0059] Figure 7 An embodiment of a network power saving (NES) strategy with user equipment (UE) association is illustrated, utilizing dual connections between a primary node (MN) and a secondary node (SN). In this embodiment, the UE is configured to utilize resources provided by two interconnected base stations. One base station acts as the primary node (MN), and the other as the secondary node (SN). MN and SN are connected via a network interface (Xn interface), and at least MN is connected to the CN.

[0060] In block 702, the core network (CN) sends a message to the base station MN containing the Network Energy Saving (NES) policy associated with the UE. In one example, the NES policy is sent after the UE requests initial network access. In other examples, the NES policy may be sent when the UE context is updated / modified at the CN. For instance, when the UE initiates a PDU session resource establishment / modification request between the UE, the base station, and the CN, the CN sends an INITIAL CONTEXT SETUP REQUEST or UE CONTEXTMODIFICATION REQUEST message to the MN. In another example, the CN sends a PDU SESSIONSETUP / MODIFY REQUEST message with the UE NES policy to the MN. (See reference) Figure 5 The background and examples of UE NES policies are described. UE NES policies at base station MN can be directly configured by OAM.

[0061] The base station MN stores the UE NES policy included in the message, or updates the stored UE NES policy using the latest received UE NES policy. In some embodiments, the base station MN determines new UE MECR and / or UE TEE information in the UE NES policy of the base station SN. In block 704, the base station MN sends a UE CONTEXT SETUP REQUEST or UE CONTEXT MODIFICATION REQUEST to the base station SN via the F1 interface to establish or modify the UE context (including the UE NES policy in the message) at the base station SN.

[0062] For example, the MN may need to consider the UE MECR and / or UE TEE corresponding to the UE at the MN, and then determine the appropriate UE MECR and / or UE TEE for the SN. This allows the UE MECR and / or UE TEE associated with the specific network resources served by the MN and SN for the UE to satisfy the UE MECR and / or UE TEE corresponding to the UE NES policy sent by the CN. If the energy consumed by the MN is much less than that consumed by the SN (e.g., when the UE's traffic is only transmitted through the SN), then the MN does not need to determine a new UE MECR and UE TEE for the SN, but instead directly sends the received UE NES policy sent by the CN to the SN.

[0063] In block 706, the SN allocates / modifies network resources or the UE context at the SN for the UE's connection. The SN stores the UE NES policy received from the MN, or updates the stored UE NES policy using the most recently received UE NES policy. The SN successfully allocates or modifies network resources or the UE context at the SN for the UE's connection. Then, in block 708, the SN sends a success response message to the MN. Then, in block 710, the MN sends a success response message to the CN.

[0064] In block 712, the SN determines a power-saving strategy based on the UE NES policy and executes the received UE NES policy at the base station. The power-saving strategy includes at least the following actions: • If a UE slice-level MECR (and / or TEE) for a used slice is received, the SN shall execute the network energy consumption rate (and / or target or minimum network energy efficiency) indicated by the UE's MECR (and / or TEE) for that used slice. • If a UE slice level MECR (and / or TEE) is received that is not used for a UE slice, and if the SN decides to use the slice for the UE, the SN needs to consider the MECR (and / or TEE) for slice handover, and the SN should ensure that the indicated energy consumption rate (and / or target or minimum network energy efficiency) of the slice can be met after the handover. • If the UE-level MECR (and / or TEE) of the UE is received, the SN shall execute the energy consumption rate (and / or target or minimum network energy efficiency) indicated by the MECR (and / or TEE) of the network resources used for all services of the UE. • If the QoS level MECR (and / or TEE) of the UE's QoS flow is received, the SN shall execute the energy consumption rate (and / or target or minimum network energy efficiency) indicated by the MECR (and / or TEE) of the network resources used for the UE's QoS flow (service). • If the PDU session level MECR (and / or TEE) of the UE's PDU session is received, the SN shall execute the energy consumption rate (and / or target or minimum network energy efficiency) indicated by the MECR (and / or TEE) of the network resources used for the UE's PDU session. • If additional alternative QoS parameters are received from the QoS stream, the SN also needs to ensure that the alternative QoS requirements of the service can be met when it performs any power-saving actions (e.g., changing the power-saving status of the network / cell / slice, adjusting the user's data rate, or adjusting the user's scheduling resources). • If a "green communication" indication is received for a QoS flow configured with best-effort service, the network can reduce the resource allocation and data transmission scheduling priority for that UE's best-effort service (QoS flow) to save network energy; or • If a “green communication” instruction is received for the UE, the network can reduce the resource allocation and data transmission scheduling priority of all best-effort services (QoS flows) of the UE to save network energy.

[0065] SN can apply network energy consumption rate (and / or target network energy efficiency) to specific network resources. For example, this can be done by changing the energy-saving status of the network / cell / slice, adjusting the user's data rate, or adjusting the user's scheduling resources to reduce network energy consumption.

[0066] The SN collects energy consumption, energy efficiency, and / or quality of service (QoS) measurements (e.g., packet delay, data throughput, jitter, etc.) from the specific network resources used by the UE at the base station, and assesses the UE's UE NES status information (including in the UE NES status report). In block 714, the SN sends a message including the corresponding UE NES status report to the MN, which may then forward the message to the CN or a trusted third party. The customer or third party then determines the UE's network energy consumption information (e.g., energy consumption, energy consumption rate, or energy efficiency) and / or the QoS provided by the network in a network power-saving state to ensure that the QoS is acceptable in this state. Network operators can use this information to optimize network energy consumption and network performance.

[0067] The MN collects energy consumption and / or energy efficiency measurements and / or service quality of specific network resources used by the UE on the SN through one or more UE NES status reports sent by the SN, and assesses the UE NES status information of the specific network resources involved (including in the UE NES status reports). The MN determines the final UE NES status of the UE and then sends the corresponding final UE NES status report to the CN.

[0068] Figure 8 An embodiment of a communication message with a network power saving (NES) policy associated with network nodes is illustrated. In block 802, the core network (CN) sends a message to the base station. This message includes the node-associated network power saving (node ​​NES) policy. This can occur during the NG interface establishment process, when the base station first sends an NG SETUP REQUEST message to the CN, and the CN responds to the base station with an NG SETUP ACKNOWLEDGE message (including the node NES policy in the message). In some embodiments, if the CN decides to update the NG configuration at the base station, the CN sends an AMF CONFIGURATION message to the base station (including the node NES policy in the message). The node NES policy at the base station can be directly configured by the OAM. The node NES policy may include: • Node associated maximum energy consumption rate (Node MECR) information, used to indicate network energy consumption limits from the node's perspective (e.g., from the base station's perspective); or • Node-associated target energy efficiency (Node TEE) information, which indicates the target or minimum network energy efficiency from the node's perspective (e.g., from the base station's perspective).

[0069] Network energy consumption rate and network energy efficiency can be referenced as follows Figure 5 As described.

[0070] Maximum energy consumption rate associated with a node (node ​​MECR) From a node perspective, the node NES policy can support maximum energy consumption rate (MECR) at different granularities or levels for the network resources used (e.g., network slices / network functions / network elements). This can be per node, per node-allowed / used slices, or per cell. This can indicate energy consumption limits for specific network resources used by a corresponding node. More specifically, this can include energy consumption limits for specific network resources used by a node-allowed / used slice, node, or cell within a specific time interval. In this embodiment, a network node is described as a "node," but it can simply be the base station mentioned above, or it can be other network components.

[0071] The node MECR information included in the node NES policy may include at least one node slice-level MECR of the slices that the node allows / has used, which may indicate the network energy consumption limit of the allowed / used slice of the node within a specific time interval.

[0072] In another example, the node MECR information included in the node NES policy may include a cell-level MECR for the node, which may indicate the network energy consumption limits of the cell within a specific time interval (including the energy consumption of network resources used for all services of the cell).

[0073] In another example, the node MECR information included in the node NES policy may include a base station-level MECR for the node, which may indicate the network energy consumption limits of the base station within a specific time interval (including the energy consumption of network resources used for all services in the cell).

[0074] Target energy efficiency of node association (node ​​TEE) From a node perspective, node NES policies can support target energy efficiency (TEE) at different granularities or levels for the network resources used (e.g., network slices / network functions / network elements). This can be based on base station slices, base stations, or cells, indicating the TEE for specific network resources corresponding to a base station slice, base station, or cell. Node TEE information can include at least one of the following: • At least one base station slice level TEE for which the node allows / has used a slice, the at least one base station slice level TEE can indicate the target or minimum network energy efficiency of the node for that allowed / used slice (e.g., network efficiency can be derived by the ratio of the energy consumption of the node's allowed / used slice to the traffic data throughput of the node's slice over a specific time interval). • At least one cell-level TEE for a cell of a base station, which can indicate the target or minimum network energy efficiency of that cell. Network efficiency can be calculated as the ratio of the energy consumption of the base station to the total traffic data throughput of the UEs served by the base station over a specific time interval.

[0075] The base station can send a response message to the AMF (e.g., the CN sends an AMF configuration update message to the base station). In block 804, the base station can respond to the AMF via a configuration update acknowledgment message. In block 806, the base station determines an energy-saving strategy based on the node NES policy and executes the received node NES policy at the base station. This execution may include at least the following actions: • If the base station receives a slice at the slice level MECR (and / or TEE), the base station shall execute the network energy consumption rate (and / or target or minimum network energy efficiency) indicated by the base station's slice MECR (and / or TEE). • If a base station-level MECR (and / or TEE) is received from the base station, the base station should execute the energy consumption rate (and / or target or minimum network energy efficiency) indicated by the base station's MECR (and / or TEE); or • If a cell-level MECR (and / or TEE) is received from the base station, the base station shall execute the energy consumption rate (and / or target or minimum network energy efficiency) indicated by the cell's MECR (and / or TEE).

[0076] Base stations can apply network energy consumption rate (and / or target network energy efficiency) parameters to specific network resources. This can include changing the energy-saving status of the network / cell / slice, adjusting user data rates, or adjusting user scheduling resources to reduce network energy consumption. When a base station performs any energy-saving action, if it receives additional acceptable QoS information from a UE, the base station also needs to ensure the quality of service for at least some UEs indicated by that additional acceptable QoS information. (Reference) Figure 5 Additional acceptable QoS information is discussed.

[0077] Base stations (e.g., by base station slice, or by base station) collect energy consumption and / or energy efficiency data for specific network resources. If necessary, base stations also collect quality of service (GHS) measurements (e.g., packet delay, data throughput, jitter, etc.) for slices, cells, or disconnected UEs on the base station. Base stations evaluate node NES status information (included in node NES status reports). In block 808, the base station sends a message to the CN including the corresponding node NES status report. Customers or third parties can then obtain network energy consumption information (e.g., energy consumption, energy consumption rate, or energy efficiency) from a network perspective. This may also include the quality of service provided by the network in a network energy-saving state (to ensure that the GHS is acceptable in a network energy-saving state). Network operators can also use this information to optimize network energy consumption and network performance. Node NES status reports may include: • Measured network energy consumption of a specific slice of a base station and the corresponding slice identifier; • Measured network energy consumption rate of a specific slice of a base station and the corresponding slice identifier; • Measured network energy efficiency of a specific slice of a base station and the corresponding slice identifier; • Measured network energy consumption of a specific cell in a base station and the corresponding cell identifier; • Measured network energy consumption rate and corresponding cell identifier for a specific cell of the base station; • Measured network energy efficiency and corresponding cell identifier for a specific cell of a base station; • Measurement of network energy consumption at base stations; • Measurement of network energy consumption rate at base stations; • Measurement of network energy efficiency at base stations; • One or more UE identifiers, and for each UE indicated by the UE identifier, the QoS measurement results of the specific QoS flow / service of that UE (e.g., packet loss rate, data rate, transmission delay, jitter, etc.) and the corresponding QoS flow identifier; • For all UEs served by a specific slice of a base station, the average QoS measurement results (e.g., packet loss rate, data rate, transmission delay, jitter, etc.) of a specific QoS flow / service with the same QoS flow identifier (QFI) for these UEs, along with the corresponding slice identifier and QFI; • For all UEs served by the base station, the average QoS measurement results (e.g., packet loss rate, data rate, transmission delay, jitter, etc.) for a specific QoS flow / service with the same QoS Flow Identifier (QFI) for these UEs, along with the corresponding slice identifier and QFI; or • For all UEs served by the cell, the average QoS measurement results (e.g., packet loss rate, data rate, transmission delay, jitter, etc.) for a specific QoS flow / service with the same QoS flow identifier (QFI) for these UEs, along with the corresponding cell identifier and QFI.

[0078] When the network is in an energy-saving state, additional acceptable QoS information can be emitted via signals to provide users with different energy-related quality of service. In this embodiment, not only energy consumption / efficiency information of network resources is included, but also the associated quality of service provided to the UE is collected, and (e.g., through node NES status reports sent by the base station to the CN or a trusted third party) this associated quality of service is made available to the customer or authorized third party. This will help the customer obtain a more intuitive network service quality under the network energy status.

[0079] Figure 9 An embodiment of a communication message for a network energy saving (NES) strategy with subnetwork association between neighboring base stations is illustrated. In block 902, the core network (CN) sends a message to a centralized base station or a source base station. This base station can be an energy-saving entity. The message includes a subnetwork associated network energy saving (subnetwork NES) strategy. The subnetwork NES strategy may include: • Maximum energy consumption rate associated with subnetworks (subnetwork MECR) information, which indicates the network energy consumption limit from the subnetwork's perspective; or • Target energy efficiency (subnetwork TEE) information associated with subnetworks, which indicates the target or minimum network energy efficiency from the perspective of the subnetwork; • Subnetwork area scope information associated with the subnetwork NES policy, which can be indicated by the following items: base station identifier list, cell identifier list, tracking area (TA) identifier list, public land mobile network (PLMN) identifier list, or non-public network (NPN) identifier list.

[0080] Network energy consumption rate and network energy efficiency can be found in the reference. Figure 5 As described.

[0081] Maximum energy consumption rate of subnetwork association (subnetwork MECR) From a sub-network perspective, the NES policy associated with a sub-network can support different granularities or levels of MECR (Mean Energy Consumption Limitation) for the network resources used. This can be based on sub-network slices or sub-networks. It can indicate the energy consumption limits of the corresponding slice of a sub-network or the network resources of a sub-network within a specific time interval. The sub-network MECR information included in the sub-network NES policy can include: • A subnetwork slice-level MECR for a slice of a subnetwork, used to indicate the energy consumption limit of that slice of the subnetwork within a specific time interval; or • A subnetwork-level MECR for a subnetwork, which indicates the energy consumption limits of network resources used by the subnetwork within a specific time interval.

[0082] Target energy efficiency of subnetwork association (subnetwork TEE) From a sub-network perspective, the NES strategy associated with a sub-network can support TEEs at different granularities or levels for the network resources used. This can be based on sub-network slices or sub-networks. It can indicate the target or minimum energy efficiency of the network resources of the corresponding slice or sub-network. The sub-network TEE information included in the sub-network NES strategy can include: • At least one subnetwork slice-level TEE for a slice of a subnetwork, which can indicate the target or minimum network energy efficiency for that slice of the subnetwork (e.g., network efficiency is calculated by the ratio of the energy consumption of that slice of the subnetwork to the total traffic throughput of the UEs served on that slice of the subnetwork over a specific time interval); or • A subnetwork-level TEE for a subnetwork that can indicate the target or minimum network energy efficiency of that subnetwork (e.g., network efficiency is calculated as the ratio of the energy consumption of the network resources of that subnetwork to the total traffic data throughput of the UEs served on that subnetwork over a specific time interval).

[0083] In block 904, the source base station / centralized base station receives energy-saving status information from neighboring base stations. The energy status information includes at least one of the following: • List of power-saving states supported by the base station; • A list of energy-saving states supported by a specific cell of the base station; • A list of energy-saving states supported by a specific area of ​​the base station; • The current energy-saving status of the base station; • The current energy-saving status of a specific cell within the base station; • The current power-saving status of a specific slice of the base station; • For each energy-saving state supported by a base station, cell, or slice, at least one of the following information can be provided: the minimum energy consumption rate, maximum energy consumption rate, or average energy consumption rate of the base station, cell, or slice in that state; or • For each energy-saving state supported by a base station, cell, or slice, at least one of the following information can be provided: the minimum energy efficiency, maximum energy efficiency, or average energy efficiency of the base station, cell, or slice in that state.

[0084] In block 906, to execute the received sub-network NES policy, the base station determines the initial node NES policy of its neighboring base stations and sends the node NES policy to the neighboring base stations. (Node NES policy reference) Figure 8 The following description is provided. When only the source base station receives the subnetwork NES policy, the source base station can execute the subnetwork NES policy by assigning the node NES policy to other nodes within the subnetwork (e.g., neighboring base stations). Figure 9 The additional communications associated with the node are shown. For example... Figure 8 As shown, in block 908, the neighboring base station determines the energy-saving strategy based on the node NES policy and executes the received node NES policy at the base station. In block 910, the neighboring base station collects node NES status information and sends a node NES status report to the source base station / centralized base station. In block 912, the source base station / centralized base station determines the energy-saving strategy based on the sub-network NES policy. In order to execute the received sub-network NES policy on the sub-network, the source base station should make a decision based on the following information: the received node NES status report and / or the energy-saving status information sent by the neighboring base station.

[0085] In block 914, after determining the energy-saving strategy, the source base station sends a message for network energy saving to neighboring base stations if necessary. This message may include at least one of the following: a node NES strategy; an energy-saving status requesting a base station handover; a list of cells and the energy-saving status of the requested handover for each cell; or a list of slices and the energy-saving status of the requested handover for each slice. (Node NES strategy reference) Figure 8 It has been described.

[0086] If a neighboring base station receives a node NES policy, it stores the node NES policy or updates its stored node NES policy using the most recently received one. In block 916, the neighboring base station determines an energy-saving policy based on the node NES policy and executes the received node NES policy at its base station. If a request to switch energy-saving states is received from a base station / cell / slice, the base station / cell / slice switches its current energy-saving state to the corresponding received energy-saving state. This may include actions such as shutting down more or fewer devices in the network (e.g., power amplifiers, transceivers, and / or other network resources of the base station / cell / slice).

[0087] In block 918, neighboring base stations collect node NES state information but send node NES state reports to the source base station. The source base station can evaluate the average subnetwork NES state based on the received node NES state reports from one or more other base stations.

[0088] The systems and processes described above may be encoded in a signal-bearing medium, a computer-readable medium (such as memory), programmed within a device (such as one or more integrated circuits, one or more processors), or processed by a controller or computer. The data may be analyzed in a computer system and used to generate a spectrum. If the method is executed by software, the software may reside in a memory that communicates with the transmitter, such as a storage device, synchronizer, communication interface, or non-volatile or volatile memory, or be connected via an interface to such a storage device, synchronizer, communication interface, or non-volatile or volatile memory. A circuit or electronic device is designed to transmit data to another location. The memory may include an ordered list of executable instructions for implementing logical functions. The described logical functions or any system elements may be implemented by optical circuitry, digital circuitry, source code, analog circuitry, analog sources (such as analog electrical, audio, or video signals, or combinations thereof). The software may be implemented in any computer-readable medium or signal-bearing medium for use by or connected to an instruction-executable system, apparatus, or device. Such systems may include computer-based systems, processor-integrated systems, or other systems that can selectively retrieve instructions from instruction-executable systems, apparatuses, or devices that also execute instructions.

[0089] "Computer-readable medium," "machine-readable medium," "signal propagation medium," and / or "signal-bearing medium" can include any device that includes, stores, transmits, propagates, or transmits software for use by, or connection to, an instruction-executable system, apparatus, or device. Machine-readable media may optionally be, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, devices, or propagation media. A non-exhaustive list of examples of machine-readable media will include: an electrical connection "electronic device" having one or more wires, a portable magnetic disk or optical disk, volatile memory such as Random Access Memory (RAM), Read-Only Memory (ROM), Erasable Programmable Read-Only Memory (EPROM, or flash memory), or optical fiber. Since software can be electrically stored as an image or other format (e.g., by optical scanning) and then compiled and / or interpreted or otherwise processed, machine-readable media may also include tangible media on which software is printed. The processed medium can then be stored in computer and / or machine memory.

[0090] The illustrations of the embodiments described herein are intended to provide a general understanding of the structure of various embodiments. The illustrations are not intended to be a complete description of all elements and features of apparatuses and systems utilizing the structures or methods described herein. Many other embodiments will be apparent to those skilled in the art upon review of this disclosure. Other embodiments may be utilized and derived from this disclosure, allowing for structural and logical substitutions and changes without departing from the scope of this disclosure. Furthermore, the illustrations are representative only and may not be drawn to scale. Some scales within the illustrations may be exaggerated, while others may be reduced. Therefore, this disclosure and the accompanying drawings should be considered illustrative rather than restrictive.

[0091] One or more embodiments of this disclosure may be referred to herein, individually and / or collectively, by the term "invention," merely for convenience and not intended to voluntarily limit the scope of this application to any particular invention or inventive concept. Furthermore, although specific embodiments have been shown and described herein, it should be understood that any subsequent arrangement designed to achieve the same or similar purpose may be substituted for the specific embodiments shown. This disclosure is intended to cover any and all subsequent adaptations or variations of the various embodiments. Combinations of the above embodiments and other embodiments not specifically described herein will be apparent to those skilled in the art upon review of this specification.

[0092] The phrase "coupled with" is defined as indicating a direct connection or indirect connection via one or more intermediate components. Such intermediate components may include both hardware-based and software-based components. The arrangement and type of components may be varied without departing from the spirit or scope of the claims described herein. Additional, different, or fewer components may be provided.

[0093] The subject matter disclosed above should be considered illustrative rather than restrictive, and the appended claims are intended to cover all such modifications, enhancements, and other embodiments falling within the true spirit and scope of the invention. Therefore, to the fullest extent permitted by law, the scope of the invention will be determined by the broadest permissible interpretation of the appended claims and their equivalents, and should not be limited or restricted by the foregoing description. While various embodiments of the invention have been described, it will be apparent to those skilled in the art that many more embodiments and implementations are possible within the scope of the invention. Therefore, the invention is not limited except by the appended claims and their equivalents.

Claims

1. A wireless communication method, the method comprising: Receive network power saving (NES) policies at network base stations, wherein the NES policies are associated with user equipment (UE), network nodes, or sub-networks. The network base station uses the NES strategy to limit energy consumption rate or implement target network energy efficiency.

2. The method according to claim 1, wherein, The reception is performed by the centralized unit (CU) of the base station from the core network (CN) or operation, management and maintenance (OAM), wherein the CU determines the maximum energy consumption rate (MECR) information or target energy efficiency (TEE) information of the distributed unit (DU) of the base station, and the CU sends the NES policy associated with the UE to the DU.

3. The method according to claim 1, wherein, The base station acts as the master node for determining the maximum energy consumption rate (MECR) or target energy efficiency (TEE) information, and sends the UE NES policy to the secondary node (SN).

4. The method according to claim 1, wherein, The NES policy associated with the UE is based on Maximum Energy Consumption Rate (MECR) information, wherein the UE MECR information includes at least one UE slice level, at least one Quality of Service (QoS) flow level, and at least one Packet Data Unit (PDU) session level.

5. The method according to claim 4, wherein, The UE MECR information is configured to indicate energy consumption limits for network resources used by the UE within a specific time interval, including energy consumption limits for network resources at the slice level, the QoS flow level, or the PDU session within a specific time interval.

6. The method according to claim 1, wherein, The NES policy associated with the UE is based on Target Energy Efficiency (TEE) information, wherein the TEE information includes at least one UE-level TEE, at least one UE slice-level TEE, at least one Quality of Service (QoS) flow-level TEE, and at least one Packet Data Unit (PDU) session-level TEE of a PDU session.

7. The method according to claim 6, wherein, The TEE information is configured to indicate the target energy efficiency or minimum energy efficiency of network resources used by the UE, including the target energy efficiency or minimum energy efficiency of network resources at the slice level, QoS flow level, or PDU session.

8. The method according to claim 1, wherein, The NES strategy associated with the network node includes the energy consumption rate of network resources and the target network energy efficiency from the perspective of the network base station.

9. The method according to claim 8, wherein, The NES policy associated with the network node is based on the maximum energy consumption rate (MECR) information associated with the network node, wherein the network node MECR information includes at least one base station slice level MECR, at least one base station level MECR, and at least one cell level MECR of a slice of the base station, and wherein the NES policy associated with the network node based on the MECR information associated with the network node indicates energy consumption limits for a specific level of network resources of the base station within a specific time interval.

10. The method according to claim 9, wherein, The NES policy associated with the network node is based on target energy efficiency (TEE) information, wherein the TEE information associated with the network node includes at least one base station slice level TEE, at least one base station level TEE of the base station, and at least one cell level TEE of the cell of the base station, and wherein the NES policy associated with the network node based on the TEE information associated with the network node indicates the target energy efficiency or minimum energy efficiency of a specific level of network resources of the base station.

11. The method according to claim 1, wherein, The NES strategy associated with the sub-network includes the energy consumption rate of network resources and the energy efficiency of the target network from the perspective of the sub-network.

12. The method according to claim 11, wherein, The NES policy associated with the sub-network is based on the maximum energy consumption rate (MECR) information associated with the sub-network, wherein the sub-network MECR information includes at least one sub-network slice-level MECR or at least one sub-network-level MECR of the sub-network slice, and wherein the NES policy associated with the sub-network based on the MECR information of the sub-network indicates an energy consumption limit on the network resources of the corresponding slice of the indicated sub-network or the network resources of the indicated sub-network within a specific time interval.

13. The method according to claim 12, wherein, The NES policy associated with the sub-network is based on Target Energy Efficiency (TEE) information, wherein the TEE information associated with the sub-network includes at least one sub-network slice-level TEE of a slice of the sub-network and at least one sub-network-level TEE of the sub-network, and wherein the NES policy associated with the sub-network based on the TEE information associated with the sub-network indicates the target energy efficiency or minimum energy efficiency of the network resources of the corresponding slice of the indicated sub-network or the network resources of the indicated sub-network.

14. The method according to claim 1, wherein, The NES policy associated with the sub-network includes sub-network area scope information, which is used to indicate the sub-network by at least one of the following: a base station identifier list, a cell identifier list, a tracking area (TA) identifier list, a PLMN identifier list, or a non-public network (NPN) identifier list.

15. The method according to claim 1, wherein, The NES policy includes a Quality of Service (QoS) flow level, which has acceptable QoS information that indicates an acceptable lower QoS to the UE when limiting the energy consumption rate or implementing the target network energy efficiency.

16. The method of claim 15, further comprising: When the utilization includes limiting the energy consumption rate or implementing the target network energy efficiency, the QoS is maintained.

17. The method of claim 1, further comprising: Collect measurement results of energy consumption, energy efficiency, or quality of service (QoS) information; as well as Based on the collected data, a status report is sent.

18. The method according to claim 17, wherein, The status report includes a UE identifier for each indicated UE, and includes measured network energy consumption, measured network energy consumption rate, measured network energy efficiency, measured network energy consumption for a specific slice of the UE, measured network energy consumption rate for a specific slice of the UE, measured network energy efficiency for a specific slice of the UE, measured network energy consumption of network resources for a specific QoS flow of the UE, measured network energy consumption rate of network resources for a specific QoS flow of the UE, measured network energy efficiency of network resources for the specific QoS flow of the UE, measured network energy consumption of network resources for a specific PDU session, measured network energy consumption rate of network resources for a specific PDU session of the UE, measured network energy efficiency of network resources for a specific PDU session of the UE, or QoS measurement results for a specific QoS flow of the UE.

19. The method according to claim 1, wherein, The target network energy efficiency is implemented by the network base station receiving the NES policy.

20. The method according to claim 1, further comprising: Receive energy-saving status information from neighboring base stations, wherein the energy status information includes a list of energy-saving statuses supported by the base station, a list of energy-saving statuses supported by a specific cell of the base station, a list of energy-saving statuses supported by a specific slice of the base station, the current energy-saving status of the base station, the current energy-saving status of a specific cell of the base station, or the current energy-saving status of a specific slice of the base station.

21. The method according to claim 20, wherein, For each energy-saving state supported by the base station, the cell, or the slice, at least one of the base station's minimum energy efficiency, maximum energy efficiency, or average energy efficiency is provided.

22. The method according to claim 20, wherein, For each energy-saving state supported by the base station, the cell, or the slice, at least one of the minimum energy consumption rate, maximum energy consumption rate, or average energy consumption rate of the base station is provided.

23. The method of claim 20, further comprising: Send a message to the neighboring base station, the message including at least one of the following: a node NES policy assigned to the neighboring base station, an energy-saving status requesting the neighboring base station to hand over, a cell list and the energy-saving status of the requested handover for each cell, a slice list and the energy-saving status of the requested handover for each slice.

24. A wireless communication device, comprising a processor and a memory, wherein, The processor is configured to read code from the memory and implement the method according to any one of claims 1 to 23.

25. A computer program product comprising a computer-readable program medium having code stored thereon, the code, when executed by a processor, causing the processor to perform the method according to any one of claims 1 to 23.

Images