System and method for energy control

Abstract

At least one aspect relates to the following system, method, device, or computer readable medium. A first network entity (e.g., a base station (BS)) can subscribe to an energy credit configured for a service or a user equipment (UE). The first network entity can receive, from a second network entity, a first message notifying the energy credit. In some embodiments, the second network entity can transmit the first message notifying the energy credit to the first network entity.

Description

Technical Field

[0001] This disclosure generally relates to wireless communications, including but not limited to systems and methods for energy control. Background Technology

[0002] The standards organization 3GPP is currently specifying a new radio interface called 5G New Radio (5G NR) and a next-generation packet core network (NG-CN or NGC). 5G NR will have three main components: 5G Access Network (5G-AN), 5G Core Network (5GC), and User Equipment (UE). To facilitate the implementation of different data services and requirements, the elements of 5GC (also known as network functions) have been simplified, some software-based and some hardware-based, allowing for customization as needed. Electricity consumption is a significant factor in the operating costs of mobile network operators (MNOs). Statistics show that electricity costs are already the highest expense in operators' operating and maintenance costs. Climate change and increased energy consumption are prompting mobile network operators to improve energy efficiency. Energy efficiency is a strategic priority for telecom operators worldwide. In the future, energy usage by user equipment or other specific services may be restricted, resulting in energy quota limitations. Within 3GPP, several scenarios and requirements have been studied to improve the energy efficiency and energy saving of 5G systems. The principle is that energy efficiency can be considered a service standard, allowing services to be provided with different energy efficiency and energy consumption strategies. However, the use of energy usage quotas and energy consumption to control service delivery or policy control has not been well established. In this disclosure, energy quotas, energy quota data, energy quota limits, and energy credit limits are used interchangeably. Summary of the Invention

[0003] The exemplary embodiments disclosed herein are intended to address problems related to one or more issues arising in the prior art and provide additional features that will become apparent when taken in conjunction with the accompanying drawings and the following detailed description. Exemplary systems, methods, apparatuses, and computer program products are disclosed herein according to various embodiments. However, it should be understood that these embodiments are presented by way of example and not as limiting, and that various modifications may be apparent to those skilled in the art who read this disclosure while remaining within the scope of this disclosure.

[0004] At least one aspect relates to a system, method, apparatus, or computer-readable medium. A first network entity (e.g., a base station (BS)) may subscribe to an energy credit limit configured for a service or user equipment (UE). The first network entity may receive a first message notifying the energy credit limit from a second network entity. In some embodiments, the second network entity may transmit the first message notifying the energy credit limit to the first network entity. The energy credit limit is configured for the service, and wherein the service is identified by at least one of an application identifier, IP address information, a data network name (DNN), or single network slice selection assist information (S-NSSAI). The first network entity is also configured to identify the user equipment by at least one of a subscription permanent identifier (SUPI) or a general public subscription identifier (GPSI). In some embodiments, a request sent from a third network entity, including a user equipment identifier (UE ID) and an energy credit limit, is stored as UE subscription data in the second network entity. In some embodiments, a request sent from a third network entity, which may include one or more service identifiers and corresponding energy credit limits, is stored as application data in the second network entity.

[0005] The wireless communication method can update energy credit limits or latest energy consumption data stored in a second network entity. In some embodiments, the wireless communication method can receive a second message requesting the latest energy consumption of a service or user equipment. A first network entity can send a third message to the second network entity indicating the latest energy consumption of a service or user equipment. In some embodiments, the wireless communication method can send a fourth message from a fourth network entity to a fifth network entity to request the latest energy consumption of a service or user equipment. The fourth network entity can receive a fifth message responding to the request from the fifth network entity. In some embodiments, the fourth network entity is configured to determine whether a request sent from a third network entity can be authorized based on the response to the fifth message. The fifth message can include at least one of the following: the amount of energy credit limit used, the amount of energy credit limit remaining, the energy credit limit, an allowed service, or a denied service. In some embodiments, the fourth network entity is a Network Open Function (NEF 306) entity or a Policy and Charging Function (PCF 302) entity. In some embodiments, the fifth network entity is an Energy Consumption and Efficiency Function (ECEF 316) entity or a Unified Data Repository (UDR 310) entity. Furthermore, the fifth network entity is configured to determine whether resource reservation can be authorized based on notifications. In some embodiments, the fifth network entity sends a sixth message to the first or second network entity, requesting energy credit limits and / or the latest energy consumption of the service or user equipment, and receives a response from the first or second network entity. The wireless communication method may include subscribing to energy credit limits or the latest energy consumption of the service or user equipment by a fourth network entity. The wireless communication method may receive notifications from the first or second network entity. Attached Figure Description

[0006] Various exemplary embodiments of this solution are described in detail below with reference to the accompanying drawings. The drawings are for illustrative purposes only and depict only exemplary embodiments of the solution to facilitate the reader's understanding. Therefore, the drawings should not be construed as limiting the breadth, scope, or applicability of the solution. It should be noted that these drawings are not necessarily drawn to scale for clarity and ease of explanation.

[0007] Figure 1 An example cellular communication network according to an embodiment of the present disclosure is shown, wherein the techniques disclosed herein can be implemented; Figure 2 Block diagrams of example base stations and user equipment according to some embodiments of the present disclosure are shown; Figure 3 An example 5G energy-efficient architecture according to an embodiment of the present disclosure is shown; Figure 4 An example method for providing energy credit lines to 5GS according to embodiments of the present disclosure is shown; Figure 5 An example method for providing energy credit limits for a service, according to embodiments of the present disclosure, is described; Figure 6 An example method for providing energy credit limits for a service, according to embodiments of the present disclosure, is described; Figure 7 An example method for transmitting and receiving energy data according to an embodiment of the present disclosure is shown; Figure 8 An example method for performing service control based on energy consumption according to embodiments of the present disclosure is described; Figure 9 An example method for performing service control based on energy consumption according to an embodiment of the present disclosure is shown; Figure 10 A flowchart of a method for energy control according to an embodiment of the present disclosure is shown. Detailed Implementation

[0008] Mobile communication technology and environment Figure 1 An example wireless communication network and / or system 100 according to embodiments of the present disclosure is illustrated, in which the techniques disclosed herein can be implemented. In the following discussion, wireless communication network 100 can be any wireless network, such as a cellular network or a narrowband Internet of Things (NB-IoT) network, referred to herein as "network 100". Such an example network 100 includes base station 102 (hereinafter referred to as "BS 102"; also referred to as a wireless communication node) and user equipment 104 (hereinafter referred to as "UE 104"; also referred to as a wireless communication device), which can communicate with each other via communication link 110 (e.g., a wireless communication channel), and a cluster of cells 126, 130, 132, 134, 136, 138, and 140 covering a geographic area 101. Figure 1 In this context, BS 102 and UE 104 are contained within the corresponding geographical boundaries of cell 126. Each of the other cells 130, 132, 134, 136, 138, and 140 may include at least one base station operating on its allocated bandwidth to provide sufficient radio coverage to its intended users.

[0009] For example, BS 102 can operate within the allocated channel transmission bandwidth to provide sufficient coverage to UE 104. BS 102 and UE 104 can communicate via downlink radio frame 118 and uplink radio frame 124, respectively. Each radio frame 118 / 124 can be further divided into subframes 120 / 127, and subframes 120 / 147 may include data symbols 122 / 128. In this disclosure, BS 102 and UE 104 are generally described as non-limiting examples of "communication nodes" that can practice the methods disclosed herein. According to various embodiments of this solution, such communication nodes are capable of wireless and / or wired communication.

[0010] Figure 2 A block diagram of an example wireless communication system 200 for transmitting and receiving wireless communication signals (e.g., OFDM / OFDMA signals) according to some embodiments of this solution is shown. System 200 may include components and elements configured to support known or conventional operating characteristics that do not need to be described in detail herein. In one illustrative embodiment, system 200 can be used in wireless communication environments (such as...) Figure 1 In a wireless communication environment 100, communication (e.g., transmission and reception) data symbols are as described above.

[0011] System 200 typically includes a base station 202 (hereinafter referred to as "BS 202") and a user equipment 204 (hereinafter referred to as "UE 204"). BS 202 includes a BS (Base Station) transceiver module 210, a BS antenna 212, a BS processor module 214, a BS memory module 216, and a network communication module 218, each module being coupled and interconnected with each other as needed via a data communication bus 220. UE 204 includes a UE (User Equipment) transceiver module 230, a UE antenna 232, a UE memory module 234, and a UE processor module 236, each module being coupled and interconnected with each other as needed via a data communication bus 240. BS 202 communicates with UE 204 via a communication channel 250, which can be any wireless channel or other medium suitable for data transmission as described herein.

[0012] Those skilled in the art will understand that system 200 may also include, in addition to Figure 2Any number of modules other than those shown herein. Those skilled in the art will understand that the various illustrative blocks, modules, circuits, and processing logic described in connection with the embodiments disclosed herein can be implemented in hardware, computer-readable software, firmware, or any practical combination thereof. To clearly illustrate this interchangeability and compatibility of hardware, firmware, and software, various illustrative components, blocks, modules, circuits, and steps are typically described according to their functionality. Whether this functionality is implemented as hardware, firmware, or software depends on the specific application and the design constraints imposed on the system as a whole. Those skilled in the art can implement these functions appropriately for each specific application, but these implementation decisions should not be construed as limiting the scope of this disclosure.

[0013] According to some embodiments, UE transceiver 230 may be referred to herein as "uplink" transceiver 230, which includes a radio frequency (RF) transmitter and an RF receiver, each including circuitry coupled to antenna 232. A duplex switch (not shown) may alternatively couple the uplink transmitter or receiver to the uplink antenna in a time-duplex manner. Similarly, according to some embodiments, BS transceiver 210 may be referred to herein as "downlink" transceiver 210, which includes an RF transmitter and an RF receiver, each including circuitry coupled to antenna 212. A downlink duplex switch may alternatively couple the downlink transmitter or receiver to downlink antenna 212 in a time-duplex manner. The operation of the two transceiver modules 210 and 230 may be time-coordinated such that the uplink receiver circuitry is coupled to the uplink antenna 232 for receiving transmissions via wireless transmission link 250 while the downlink transmitter is coupled to the downlink antenna 212. Conversely, the operation of the two transceivers 210 and 230 can be time-coordinated, such that the downlink receiver is coupled to the downlink antenna 212 for receiving transmissions via the wireless transmission link 250 while the uplink transmitter is coupled to the uplink antenna 232. In some embodiments, there is tight time synchronization with a minimum guard time between changes in duplex direction.

[0014] UE transceiver 230 and base transceiver 210 are configured to communicate via wireless data communication link 250 and cooperate with RF antenna devices 212 / 232 that are appropriately configured to support specific wireless communication protocols and modulation schemes. In some illustrative embodiments, UE transceiver 210 and base transceiver 210 are configured to support industry standards such as Long Term Evolution (LTE) and emerging 5G standards. However, it should be understood that this disclosure is not necessarily limited to the application of specific standards and related protocols. Rather, UE transceiver 230 and base transceiver 210 may be configured to support alternative or additional wireless data communication protocols, including future standards or variations thereof.

[0015] According to various embodiments, BS 202 may be, for example, an evolved Node B (eNB), a serving eNB, a target eNB, a femtocell, or a picocell. In some embodiments, UE 204 may be embodied in various types of user equipment, such as mobile phones, smartphones, personal digital assistants (PDAs), tablets, laptops, wearable computing devices, etc. Processor modules 214 and 236 may be implemented or realized using general-purpose processors, content-addressable memory, digital signal processors, application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), any suitable programmable logic devices, discrete gate or transistor logic, discrete hardware components, or any combination thereof, designed to perform the functions described herein. In this way, the processor may be implemented as a microprocessor, a controller, a microcontroller, a state machine, etc. The processor may also be implemented as a combination of computing devices, such as a combination of a digital signal processor and a microprocessor, multiple microprocessors, one or more microprocessors combined with a digital signal processor core, or any other such configuration.

[0016] Furthermore, the steps of the methods or algorithms described in conjunction with the embodiments disclosed herein can be directly embodied in hardware, firmware, software modules executed by processor modules 214 and 236 respectively, or any actual combination thereof. Memory modules 216 and 234 can be implemented as RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art. In this regard, memory modules 216 and 234 can be coupled to processor modules 210 and 230 respectively, such that processor modules 210 and 230 can read information from and write information to memory modules 216 and 234 respectively. Memory modules 216 and 234 can also be integrated into their respective processor modules 210 and 230. In some embodiments, memory modules 216 and 234 may each include a cache memory for storing temporary variables or other intermediate information during the execution of instructions executed by processor modules 210 and 230 respectively. Memory modules 216 and 234 may each include non-volatile memory for storing instructions executed by processor modules 210 and 230, respectively.

[0017] Network communication module 218 typically refers to the hardware, software, firmware, processing logic, and / or other components of base station 202 that enable bidirectional communication between base transceiver 210 and other network components and communication nodes configured to communicate with base station 202. For example, network communication module 218 may be configured to support Internet or WiMAX traffic. In a typical deployment, and not limitingly, network communication module 218 provides an 802.3 Ethernet interface, enabling base transceiver 210 to communicate with traditional Ethernet-based computer networks. In this way, network communication module 218 may include a physical interface for connecting to a computer network (e.g., a Mobile Switching Center (MSC)). The terms “configured for,” “configured to,” and variations thereof, used herein with respect to a specified operation or function, refer to a device, component, circuit, structure, machine, signal, etc., physically constructed, programmed, formatted, and / or implemented to perform the specified operation or function.

[0018] The Open Systems Interconnection (OSI) model (referred to herein as the "OSI model") is a conceptual and logical layout that defines network communication used by systems (such as wireless communication devices and wireless communication nodes) that can interconnect and communicate with other systems. The model is divided into seven sub-components or layers, each representing a set of concepts providing services to the layers above and below it. The OSI model also defines logical networks and efficiently describes computer packet transmissions using different layer protocols. The OSI model can also be referred to as the seven-layer OSI model or the seven-layer model. In some embodiments, the first layer may be the physical layer. In some embodiments, the second layer may be the Media Access Control (MAC) layer. In some embodiments, the third layer may be the Radio Link Control (RLC) layer. In some embodiments, the fourth layer may be the Packet Data Convergence Protocol (PDCP) layer. In some embodiments, the fifth layer may be the Radio Resource Control (RRC) layer. In some embodiments, the sixth layer may be the Non-Access Stratum (NAS) layer or the Internet Protocol (IP) layer, and the seventh layer is other layers.

[0019] Various exemplary embodiments of this solution are described below with reference to the accompanying drawings to enable those skilled in the art to manufacture and use this solution. As will be apparent to those skilled in the art, various changes or modifications can be made to the examples described herein without departing from the scope of this solution after reading this disclosure. Therefore, this solution is not limited to the exemplary embodiments and applications described and illustrated herein. Furthermore, the specific order or hierarchy of steps in the methods disclosed herein is merely exemplary. Based on design preferences, the specific order or hierarchy of steps in the disclosed methods or processes can be rearranged while remaining within the scope of this solution. Therefore, those skilled in the art will understand that the methods and techniques disclosed herein present various steps or actions in an exemplary order, and unless otherwise expressly stated, this solution is not limited to the specific order or hierarchy presented.

[0020] Methods for energy control Figure 3 An example of a 5G energy-efficient architecture is illustrated. This system may include NG-RAN (e.g., a 5G radio access network), access and mobility control functions (hereinafter referred to as AMF 314), session management functions (hereinafter referred to as SMF 312), user plane functions (hereinafter referred to as UPF 320), unified data management (hereinafter referred to as UDM 304), policy control functions (hereinafter referred to as PCF 302), network openness functions (hereinafter referred to as NEF 306), and an application server (hereinafter referred to as AS). The system also includes application functions (hereinafter referred to as AF 308), a non-unified data repository (hereinafter referred to as UDR 310), a network repository function (hereinafter referred to as NRF 318), and energy consumption and efficiency functions (hereinafter referred to as ECEF 316).

[0021] UE 104 can access 5G systems (referred to herein as 5GS) and obtain services via NAS signaling through AMF 314 of the next-generation radio access network (NG-RAN) (e.g., 5G radio access network) and the core network. For ease of description, AMF 314 may include registration, connectivity, reachability, and mobility management. Furthermore, AMF 314 can perform authentication and authorization. NG-RAN can perform air interface resource scheduling and connectivity management for the network interacting with UE 104.

[0022] SMF 312 may include session management (e.g., session establishment), modification and release, UE IP address allocation and management, UP function selection and control, and downlink data notification. UPF 320 may include intra-RAT / inter-RAT mobility, packet routing and forwarding, traffic usage reporting, user plane QoS processing, downlink packet buffering, and downlink data notification triggering. UDM 304 may manage subscription profiles for one or more of UEs 104. Subscriptions may include data for mobility management and session management. In some implementations, AMF 314 and SMF 312 may receive subscriptions from UDM 304.

[0023] PCF 302 can support a unified policy framework for managing network behavior, providing policy rules to one or more control location functions to enforce those rules. NEF 306 can be used to exchange information between 5GS and external third parties. AF 308 and AS provide 5GS services. UDR 310 can support UDM 304 and PCF 302 for storing and retrieving subscription data, as well as for open structured data. NRF 318 can support network function (NF) instance profile registration and service catalogs. NRF 318 can receive NF discovery request forms from consumer NFs. Furthermore, NRF 318 can provide consumer NFs with information about discovered NF instances. ECEF 316 can store energy-related information in 5GS. Energy-related information can include energy consumption, energy efficiency, renewable energy, and carbon emissions. ECEF 316 can calculate and store energy usage status and transmit energy-related information to authorized consumers.

[0024] In some implementations, ECEF 316 can be a standalone NF, all or part of ECEF 316, and can be part of other 5G network functions (e.g., PCF 302, UDR 310, NEF 306). For example, ECEF 316 can be part of another 5G network function. ECEF 316 can be replaced by other 5G network functions. In some implementations, ECEF 316 can be part of UDR 310. For example, if ECEF 316 is part of UDR 310, then ECEF 316 can be replaced by UDR 310, and the interaction between ECEF 316 and UDR 310 occurs within UDR 310. In some embodiments, UE 104 or other services (such as Facebook, Instagram, X, etc.) may have energy quota limitations (such as energy credit limits). For example, if energy usage exceeds the energy quota, the network will stop UE 104's service or the packet service of that service. 3GPP may omit ECEF 316 and other procedures defined in ECEF 316. This disclosure provides a method for dynamically configuring energy quotas (e.g., energy credit limits) for one or more UEs 104 or services. Furthermore, this disclosure provides a method for controlling energy usage in 5GS. For ease of description, energy usage (in some implementations, energy usage may be energy consumption) can be expressed in joules (J) or watts (Wh).

[0025] Now for reference Figure 4 This document describes an example method for providing energy credit limits for services to 5GS. The method includes ECEF 316, UDR 310, NEF 306, and AF 308. ECEF collects energy usage data from the Operations Management and Maintenance (OAM) system. AF 308 can provide energy quota data for UE 104 or a service. For UE 104, the energy quota data can be stored in the subscription data within UDR 310. For a specific service, the energy quota data can be stored in UDR 310. In some implementations, AF 308 can request service authorization. For example, when AF 308 requests service authorization, NEF 306 or PCF 302 can check ECEF 316 or UDR 310 to understand the energy usage of UE 104 or the service performed on UE 104. If the energy usage of the UE or the specific service does not exceed the quota, AF 308 can receive the service authorization.

[0026] In step 402, ECEF 316 subscribes to energy data from UDR 310 using the Nudr_DM_subscribe service operation. The Nudr_DM_Subscribe service operation can identify the service using an application identifier, IP address information (e.g., FQDN, IP port), Data Network Name (DNN), or Single Network Slice Selection Auxiliary Information (S-NSSAI). In step 404, AF 308 can determine whether to provide energy data to 5GS for a specific service. In step 406, AF 308 can send a request to NEF 306, which can be an Nnef_ServiceParameter_Create / Update service operation. The energy data can be represented as J or Wh. The service identifier can be identified using an application identifier, IP address information (e.g., IP address, IP port, FQDN), DNN, or S-NSSAI.

[0027] In step 408, NEF 306 can authorize AF 308 request. NEF 306 can perform a mapping from the external application identifier to the corresponding application known in network 100. NEF 306 can store the AF 308 request information as "application data" in UDR 310. In step 410, UDR 310 can use Nudr_DM_Notify to send a notification of energy data for a specific service to ECEF 316. In some implementations, the notification can be an indication triggered by Nudr_DM_Notify.

[0028] The power credit limit for UE 104 can be a static subscription in UDM 304. AF 308 can provide the power credit limit for UE 104 to the UE subscription. Figure 5 An example method for providing energy credit limits to UE subscription data in UDM 304 is described. AF 308 can provide energy credit limits to UE subscriptions in UDM 304. This method may include ECEF 316, UDR 310, NEF 306, and AF 308 to transmit energy-related information over 5GS. Components of this method can interact with other components to perform configuration functions. For example, ECEF 316 can interact with UDR 310. In another example, AF 308 can interact with NEF 306.

[0029] In step 502, ECEF 316 can subscribe to UE104's energy data (e.g., energy credit limit) from UDR 310 using the Nudr_DM_subscribe service operation. In the Nudr_DM_Subscribe service operation, UE104 is identified by SUPI or GPSI. In step 504, AF 308 can provide energy data to the UE subscription data in UDM 304. In step 506, AF 308 can send a request to NEF 306. This request can be an Nnef_ParameterProvision Create / Update service operation. The UE ID and energy data can be carried in this request. The UE ID can be SUPI or GPSI.

[0030] In step 508, NEF 306 may authorize AF 308 to provide parameters in the request received in step 506. For example, if AF 308 is authorized by NEF 306 to provide parameters in the request received in step 506, NEF 306 may request UDM 304 to provide the parameters as part of the subscriber data. In step 510, UDM 304 may store the energy data from the UE subscription in UDR 310. In step 512, UDR 310 may use Nudr_DM_Notify to send a notification containing the energy data of UE 104 to ECEF 316.

[0031] ECEF 316 can notify and / or update UDR 310 based on the latest energy consumption of UE 104 or the service. Figure 6 An example method for transmitting and receiving energy data is illustrated. This method may include an ECEF 316 and a UDR 310 to transmit energy-related information over 5GS. Components of this method can interact with other components to perform configuration functions. For example, the ECEF 316 can transmit energy-related data to the UDR 310.

[0032] In step 602, ECEF 316 can collect energy quota data for UE 104 or the service. ECEF 316 can calculate the energy consumption of the corresponding UE 104 for a specific service from the OAM system. In step 604, ECEF 316 can store and update the energy data in UDR 310. ECEF 316 can send the consumed energy quota to UDR 310. In some implementations, ECEF 316 can send the remaining energy quota to UDR 310. In step 606, UDR 310 can send a response to ECEF 316 to acknowledge receipt of the energy data. In step 608, UDR 310 can determine the latest energy consumption data that may need to be updated. In some implementations, UDR 310 can check the timestamp on previous data to determine whether to send a response. For example, if the energy data received by UDR 310 has a timestamp greater than a threshold, UDR 310 can determine that the latest energy consumption data may need to be updated. In step 610, UDR 310 may send a request to ECEF 316 to obtain an updated value for the latest energy consumption of UE 104 or the service. In step 612, ECEF 316 may respond to UDR 310 to acknowledge receipt of the latest energy consumption for UE 104 or the service. The energy consumption may include the amount of used energy quota or remaining energy quota.

[0033] NEF 306 can check UDR 310 to authorize the services to be executed. Figure 7 An example method for NEF 306 to perform service control based on energy consumption is described. This method may include PCF 302, UDR 310, NEF 306, and AF 308 to inspect energy-related information via 5GS. Components of this method can interact with other components to perform functions requested by management. For example, UDR 310 can interact with PCF 302. In another example, AF 308 can interact with NEF 306.

[0034] In step 702, AF 308 may send a request to NEF 306 to reserve resources for an AF 308 session. For example, AF 308 may reserve a certain amount of resources in NEF 306 for one or more AF 308 sessions. In some implementations, AF 308 may use an Nnef_AFsessionWithQoS request message (e.g., UE address, AF 308 identifier, QoS parameters, etc.). In step 704, NEF 306 may determine energy consumption-based control for UE 104 or a specific service. This control may depend on local configuration or the indication in step 702. This indication may be obtained from a request message received from AF 308. NEF 306 may send a request to UDR 310 regarding energy consumption for UE 104 or a specific service.

[0035] In step 706, UDR 310 may send a response to NEF 306 with the latest energy consumption of UE 104 or the service. UDR 310 may check the latest energy consumption status of UE 104 or the service. The latest energy consumption may include the amount of energy quota used or the amount of remaining energy quota. In step 708, NEF 306 may determine whether to authorize AF 308's request based on the energy data received in step 706. The energy data may be the remaining energy quota to allow AF 308's request to continue to step 710. In step 710, NEF 306 may transmit the received parameters to PCF 302. In some implementations, the parameters may include the Npcf_PolicyAuthorization_Create / Update service operation.

[0036] NEF 306 can check ECEF 316 to authorize the services to be performed. Figure 8 An example method for NEF 306 to perform service control based on energy consumption is described. This method may include PCF 302, ECEF 316, NEF 306, and AF 308 to inspect energy-related information via 5GS. Components of this method can interact with other components to perform functions requested by management. For example, ECEF 316 can interact with PCF 302. In another example, AF 308 can interact with NEF 306.

[0037] In step 802, AF 308 may send a request to NEF 306 to reserve resources for an AF 308 session. For example, AF 308 may reserve a certain amount of resources in NEF 306 for one or more AF 308 sessions. In some implementations, AF 308 may use an Nnef_AF sessionWithQoS request message (e.g., UE address, AF 308 identifier, QoS parameters, etc.). In step 804, NEF 306 may determine energy consumption-based control for UE 104 or a specific service. This control may depend on local configuration or an indication from step 802. This indication may be obtained from a request message received from AF 308. NEF 306 may send a request for energy consumption for UE 104 or the service to ECEF 316.

[0038] In step 806, ECEF 316 may send a response to NEF 306 with the latest energy consumption of UE 104 or a specific service. ECEF 316 may check the latest energy consumption status of UE 104 or the service. The latest energy consumption may include the amount of energy quota used or the amount of remaining energy quota. In step 808, NEF 306 may determine whether to authorize AF 308's request based on the energy data received in step 806. The energy data may be the remaining energy quota to allow AF 308's request to continue to step 810. In step 810, NEF 306 may transmit the received parameters to PCF 302. In some arrangements, the parameters may include the Npcf_PolicyAuthorization_Create / Update service operation.

[0039] Figure 9 An example method is shown to check energy consumption from ECEF 316 and authorize services to be performed. This method may include PCF 302, ECEF 316, UDF, SMF 312, NEF 306, and AF 308 to check energy-related information via 5GS. Components of this method can interact with other components to perform functions requested for management. For example, ECEF 316 can interact with SMF 312. In another example, AF 308 can interact with NEF 306.

[0040] In step 902, UE 104 can perform PDU session establishment. PDU session establishment can be performed by ECEF 316, UDR 310, SMF 312, or PCF 302. SMF 312 can establish an SM policy association (e.g., an N7 session) with PCF 302. In step 904, PCF 302 can subscribe to energy quota and energy consumption data from ECEF 316 or UDR 310 for UE 104 or a specific service. This service can be identified by an application identifier, IP address information, DNN, or S-NSSAL. In step 904, when energy quota data changes, ECEF 316 or UDR 310 can notify PCF 302. For example, if energy quota data increases, the change can be notified to PCF 302.

[0041] In step 906, AF 308 may send a request to reserve resources for the AF 308 session in NEF 306. This request may contain an Nnef_FsessionWithQoS request message. In some implementations, Nnef_FsessionWithQoS may contain the UE 104 address. In some implementations, Nnef_FsessionWithQoS may contain the AF 308 identifier. In step 908, NEF 306 may transmit the received parameters to PCF 302. NEF 306 may use the Npcf_PolicyAuthorization_Create / Update service operation. In some implementations, AF 308 may be located in a trusted domain. For example, if AF 308 is in a trusted domain, AF 308 may transmit the request to PCF 302 without forwarding parameters from NEF 306. PCF 302 may determine whether resource reservation can be authorized based on the energy quota data received in step 906. In some implementations, when PCF 302 directly receives energy quota data in step 906, PCF 302 may decide to skip steps 910 and 912.

[0042] In step 912, PCF 302 can send a request to ECEF 316 or UDR 310 to obtain energy quota and energy consumption data for UE 104 or a specific service. In step 912, ECEF 316 or UDR 310 can check the latest energy consumption status of UE 104 or a specific service. In step 914, ECEF 316 or UDR 310 can send a response to PCF 302, including used energy quota, remaining energy quota, allowed services, or denied services. The interaction between ECEF 316 and UDR 310 can... Figure 6As observed in step 916, PCF 302 can determine whether resource reservation can be authorized based on the energy quota data received in step 906 or step 914. In some implementations, the energy quota data may be remaining energy quota to allow AF 308 to request continuation. In step 916, if PCF 302 determines that resource reservation can be authorized, PCF 302 can update the policy information. For example, PCF 302 can issue an Npcf_SMPolicyControl_UpdateNotify request with updated policy information from SMF 312. The updated policy information may include information about the PDU session.

[0043] It should be understood that one or more features in the above / below embodiments are not unique to a particular embodiment, but can be combined in any way (e.g., in any priority and / or order, simultaneously or otherwise).

[0044] Figure 10 A flowchart of a method 1000 for energy control is shown. Method 1000 can be combined with the present document. Figures 1-9 The method is performed by any one or more components and devices described in detail. Generally, in some embodiments, method 1000 may be performed by a wireless communication node (e.g., a base station (BS) or radio access network (RAN) node, or ECEF, PCF). Depending on the embodiment, additional, fewer, or different operations may be performed in method 1000. At least one aspect of the operation relates to a system, method, apparatus, or computer-readable medium.

[0045] A first network entity (e.g., a base station (BS), ECEF, PCF, or NEF) can subscribe to an energy credit limit configured for a service or user equipment (UE). The first network entity can receive a first message notifying the energy credit limit from a second network entity. In some embodiments, the second network entity can transmit the first message notifying the energy credit limit to the first network entity. The energy credit limit is configured for a service, and the service is identified by at least one of an application identifier, IP address information, a data network name (DNN), or single network slice selection assist information (S-NSSAI). The first network entity is also configured to identify the user equipment by at least one of a Subscription Permanent Identifier (SUPI) or a General Public Subscription Identifier (GPSI). In some embodiments, a request sent from a third network entity, including a user equipment identifier (UE ID) and an energy credit limit, is stored as UE subscription data in the second network entity. In some embodiments, a request sent from a third network entity, including one or more service identifiers and corresponding energy credit limits, is stored as application data in the second network entity.

[0046] The wireless communication method can update energy credit limits or latest energy consumption data stored in a second network entity. In some embodiments, the wireless communication method can receive a second message requesting the latest energy consumption of a service or user equipment. A first network entity can send a third message to the second network entity indicating the latest energy consumption of a service or user equipment. In some embodiments, the wireless communication method can send a fourth message from a fourth network entity to a fifth network entity to request the latest energy consumption of a service or user equipment. The fourth network entity can receive a fifth message responding to the request from the fifth network entity. In some embodiments, the fourth network entity is configured to determine whether a request sent from a third network entity can be authorized based on the response to the fifth message. The fifth message can include at least one of the following: the amount of energy credit limit used, the amount of energy credit limit remaining, the energy credit limit, an allowed service, or a denied service. In some embodiments, the fourth network entity is a Network Open Function (NEF 306) entity or a Policy and Charging Function (PCF 302) entity. In some embodiments, the fifth network entity is an Energy Consumption and Efficiency Function (ECEF 316) entity or a Unified Data Repository (UDR 310) entity. Furthermore, the fifth network entity is configured to determine whether resource reservation can be authorized based on notifications. In some embodiments, the fifth network entity sends a sixth message to the first or second network entity, requesting energy credit limits and / or the latest energy consumption of the service or user equipment, and receives a response from the first or second network entity. The wireless communication method may include subscribing to energy credit limits or the latest energy consumption of the service or user equipment by a fourth network entity. The wireless communication method may receive notifications from the first or second network entity.

[0047] While various embodiments of the present solution have been described above, it should be understood that they are merely examples and not limitations. Similarly, various accompanying drawings may depict exemplary architectures or configurations provided to enable those skilled in the art to understand exemplary features and functionality of the present solution. However, those skilled in the art will understand that the solution is not limited to the illustrated exemplary architectures or configurations, but can be implemented using various alternative architectures and configurations. Furthermore, as those skilled in the art will understand, one or more features of one embodiment may be combined with one or more features of another embodiment described herein. Therefore, the breadth and scope of this disclosure should not be limited by any of the illustrative embodiments described above.

[0048] It should also be understood that any reference to elements using names such as "first," "second," etc., in this document generally does not restrict the number or order of these elements. Rather, these names can be used as a convenient means of distinguishing two or more elements or instances of elements in this document. Therefore, mentioning the first and second elements does not imply that only two elements can be used, nor does it imply that the first element must precede the second element in some way.

[0049] Furthermore, those skilled in the art will understand that information and signals can be represented using any of a variety of different techniques and skills. For example, data, instructions, commands, information, signals, bits, and symbols that may be referenced in the above description can be represented by voltage, current, electromagnetic waves, magnetic fields or particles, light fields or particles, or any combination thereof.

[0050] Those skilled in the art will further understand that any of the various illustrative logic blocks, modules, processors, devices, circuits, methods, and functions described in conjunction with the aspects disclosed herein can be implemented by electronic hardware (e.g., digital implementation, analog implementation, or a combination of both), firmware, various forms of program or design code containing instructions (which may be referred to herein as "software" or "software module" for convenience), or any combination of these technologies. To clearly illustrate this interchangeability of hardware, firmware, and software, the various illustrative components, blocks, modules, circuits, and steps have been generally described above according to their functionality. Whether such functionality is implemented as hardware, firmware, or software, or a combination of these technologies, depends on the specific application and the design constraints imposed on the system as a whole. Those skilled in the art can implement the described functionality in various ways for each specific application, but such implementation decisions will not depart from the scope of this disclosure.

[0051] Furthermore, those skilled in the art will understand that the various illustrative logic blocks, modules, devices, components, and circuits described herein can be implemented within or executed by integrated circuits (ICs), which may include general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, or any combination thereof. Logic blocks, modules, and circuits may also include antennas and / or transceivers for communicating with various components within a network or device. A general-purpose processor may be a microprocessor, but may also be any conventional processor, controller, or state machine. A processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors combined with a DSP core, or any other suitable configuration performing the functions described herein.

[0052] If implemented in software, these functions can be stored as one or more instructions or code on a computer-readable medium. Therefore, the steps of the methods or algorithms disclosed herein can be implemented as software stored on a computer-readable medium. Computer-readable media include computer storage media and communication media, encompassing any medium capable of transferring computer programs or code from one place to another. Storage media can be any available medium accessible to a computer. For example (but not limited to), such computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disc storage, disk storage or other magnetic storage devices, or any other medium that can be used to store the required program code in the form of instructions or data structures and is accessible to a computer.

[0053] In this document, the term "module" refers to software, firmware, hardware, and any combination of these elements used to perform the functions described herein. Furthermore, for ease of discussion, various modules are described herein as discrete modules; however, it will be apparent to those skilled in the art that, according to embodiments of this solution, two or more modules can be combined into a single module to perform the relevant functions.

[0054] Furthermore, embodiments of this solution may also employ memory or other storage devices, as well as communication components. It should be understood that, for clarity, the above description refers to different functional units and processors in illustrating implementations of this solution. However, it is apparent that any suitable allocation of functions among different functional units, processing logic elements, or domains can be employed without diminishing the effectiveness of this solution. For example, a function originally purported to be performed by a separate processing logic element or controller may also be performed by the same processing logic element or controller. Therefore, references to specific functional units merely indicate suitable means of providing said function and do not represent a strict logical or physical structure or organizational form.

[0055] Various modifications to the implementations described herein will become apparent to those skilled in the art, and the general principles defined herein can be applied to other implementations without departing from the scope of this disclosure. Therefore, this disclosure is not intended to be limited to the embodiments shown herein, but should be given the broadest scope consistent with the novel features and principles disclosed herein, as set forth in the following claims.

Claims

1. A wireless communication method, comprising: The first network entity subscribes to the energy credit limit configured for the service or user equipment from the second network entity; as well as The first network entity receives a first message from the second network entity notifying the energy credit limit.

2. The wireless communication method according to claim 1, wherein, The energy credit limit is configured for the service, and the service is identified by at least one of the following: application identifier, IP address information, data network name (DNN), or single network slice selection aid information (S-NSSAI).

3. The wireless communication method according to claim 2, wherein, Requests sent from the third network entity, including one or more service identifiers and corresponding energy credit limits, are stored as application data in the second network entity.

4. The wireless communication method according to claim 1, wherein, The energy credit limit is configured for the user equipment, and the user equipment is identified by at least one of a Subscription Permanent Identifier (SUPI) or a General Public Subscription Identifier (GPSI).

5. The wireless communication method according to claim 4, wherein, The request, which includes the User Equipment Identifier (UE ID) and the energy credit limit, sent from the third network entity, is stored as UE subscription data in the second network entity.

6. The wireless communication method according to any one of claims 1 to 5, further comprising: The first network entity updates the energy credit limit or the latest energy consumption data stored in the second network entity.

7. The wireless communication method according to any one of claims 1 to 5, further comprising: The first network entity receives a second message from the second network entity requesting the latest energy consumption of the service or user equipment.

8. The wireless communication method according to claim 7, further comprising: The first network entity sends a third message to the second network entity, indicating the latest energy consumption of the service or user equipment.

9. A wireless communication method, comprising: A fourth message is sent from the fourth network entity to the fifth network entity to request the latest energy consumption of the service or user equipment. as well as The fourth network entity receives a fifth message in response to the request from the fifth network entity.

10. The wireless communication method according to claim 9, wherein, The fourth network entity is either a Network Open Function (NEF 306) entity or a Policy and Accounting Function (PCF 302) entity.

11. The wireless communication method according to claim 9, wherein, The fifth network entity is either the Energy Consumption and Energy Efficiency Function (ECEF 316) entity or the Unified Data Repository (UDR 310) entity.

12. The wireless communication method according to claim 10, further comprising: The fourth network entity subscribes to the energy credit limit or latest energy consumption of the service or user equipment from the first or second network entity. as well as Receive notifications from the first or second network entity.

13. The wireless communication method according to claim 9, wherein, The fifth message includes at least one of the following: the amount of energy credit limit used, the amount of energy credit limit remaining, the energy credit limit, and the allowed or denied service.

14. The wireless communication method according to claim 9, wherein, The fourth network entity is configured to determine whether it can authorize the request sent from the third network entity based on the response to the fifth message.

15. The wireless communication method according to claim 12, wherein, The fifth network entity is configured to determine whether resource reservation can be authorized based on the notification.

16. The wireless communication method according to claim 13, wherein, The fifth network entity sends a sixth message to the first network entity or the second network entity, requesting the energy credit limit and / or the latest energy consumption of the service or the user equipment, and receives a response from the first network entity or the second network entity.

17. A wireless communication method, comprising: A first message is transmitted from a second network entity to a first network entity to notify the energy credit limit, wherein the first network entity subscribes to the energy credit limit configured for the service or user equipment.

18. 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 of any one of claims 1 to 17.

19. A computer program product comprising computer-readable program medium code stored thereon, the code causing the processor to implement the method of any one of claims 1 to 17 when executed by a processor.

Images