Methods to enable energy aware edge application enabler services

Abstract

Described herein are methods to enable energy aware edge enabler services to equip service layers, UEs, and networks with the capability to operate with increased levels of energy efficiency and awareness. The methods also provide increased exposure and aware of energy management to application clients and servers hosted in the network and on UEs. Energy aware edge application enabler services functionality is described herein for the 3GPP SA6 defined EEL. In an example, an apparatus may determine one or more energy aware edge enabler layer (EEL) profiles comprising one or more energy centric information elements. Based on energy aware EEL profile information, the apparatus may detect one or more events. Based on the energy aware EEL profile information and the one or more events, and using one or more analytics or artificial intelligence (AI) functions or services, the apparatus may perform one or more energy aware EEL operations.

Description

CNV15060W001 / 101859.002202METHODS TO ENABLE ENERGY AWAREEDGE APPLICATION ENABLER SERVICESCROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Patent Application No. 63 / 725,786, filed November 27, 2024, which is hereby incorporated by reference in its entirety.BACKGROUND

[0002] Edge application enabler service layers such as the 3GPP defined Edge Enabler Layer (EEL) currently lack energy aware features and capabilities. This lack of energy awareness prevents edge application enabler service lay ers from supporting certain energy aware functionality. Accordingly, there is a need for improved energy aware features and capabilities.SUMMARY

[0003] This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter. Furthermore, the claimed subject matter is not limited to limitations that solve any or all disadvantages noted in any part of this disclosure.

[0004] Described herein are methods to enable energy aware edge enabler sendees to equip service layers, UEs, and networks with the capability to operate with increased levels of energy efficiency and awareness. The methods also provide increased exposure and awareness of energy management to application clients and servers hosted in the network and on UEs. Energy' aware edge application enabler sendees functionality is described herein for the 3GPP SA6 defined EEL. The techniques disclosed herein are also applicable to non-standards-based edge application enabler services. In an example, an apparatus may determine one or more energy aware EEL profiles comprising one or more energy centric information elements. Based on energy aware EEL profile information, the apparatus may detect one or more events. BasedCNV15060W001 / 101859.002202 on the energy aware EEL profile information and the one or more events, and using one or more analytics or artificial intelligence (Al) functions or services, the apparatus may perform one or more energy aware EEL operations.BRIEF DESCRIPTION OF THE DRAWINGS

[0005] In order to facilitate a more robust understanding of the application, reference is now made to the accompanying drawings, in which like elements are referenced with like numerals. These drawings should not be construed to limit the application and are intended only to be illustrative.

[0006] FIG. 1 shows an example of the Edge Enabler Layer (EEL) architecture as described in 3GPP TS 23.558, Architecture for enabling Edge Applications (EEL); (Release 19);

[0007] FIG. 2 shows an example energy aware EEL architecture;

[0008] FIG. 3 shows an example overview of energy aware EEL operational procedures;

[0009] FIG. 4 shows an example of energy' aware ECS service provisioning;

[0010] FIG. 5 shows an example of energy' aware AC registration;

[0011] FIG. 6 shows an example of energy’ aware EEC registration;

[0012] FIG. 7 shows an example of energy' aware EAS registration;

[0013] FIG. 8 shows an example of energy' aware EES registration;

[0014] FIG. 9 shows an example of energy' aware EAS discovery7;

[0015] FIG. 10 shows an example of energy aware EEL event subscriptions;

[0016] FIG. 11 shows an example of energy aware EEL event notifications;

[0017] FIG. 12 shows an example of energy aware EEL service continuity;

[0018] FIG. 13 shows an example of energy’ aware EEL charging;

[0019] FIG. 14 shows an example energy' aware EEL preferences GUI;

[0020] FIG. 15 A illustrates an example communications system;

[0021] FIG. 15B shows a system diagram of an example RAN and core network;

[0022] FIG. 15C shows a system diagram of an example RAN and core network;

[0023] FIG. 15D shows a system diagram of an example RAN and core network;

[0024] FIG. 15E illustrates another example communications system;CNVI5060W001 / 101859.002202

[0025] FIG. 15F is a block diagram of an example apparatus or device, such as a WTRU; and

[0026] FIG. 15G is a block diagram of an exemplary computing system.DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

[0027] Methods and procedures are described herein to enhance EEL architectures such as but not limited to the 3GPP defined Edge Enabler Layer (EEL) with energy aware capabilities.

[0028] The following abbreviations are described herein:CNV15060W001 / 101859.002202

[0029] The following terms are described herein:CNV15060W001 / 101859.002202

[0030] Edge Computing and an Edge Enabler Layer is described herein. Edge Computing is a network architecture concept that enables computing capabilities and service environments to be deployed closer to devices / UEs. It promises several benefits such as lower latency, higher bandwidth, reduced backhaul traffic and prospects for new services compared to cloud environments.

[0031] 3GPP has defined an Edge Enabler Layer (EEL) that provides services for enabling edge applications over 3GPP networks as described in 3GPP TS 23.558, Architecture for enabling Edge Applications (EEL); (Release 19).

[0032] FIG. 1 shows the EEL architecture 50 defined by the 3GPP SA6 working group as described in 3GPP TS 23.558, Architecture for enabling Edge Applications (EEL); (Release 19). EEL refers to the overall functionality provided by various EEL client and server entities such as Edge Enabler Clients (EECs), Edge Enabler Servers (EESs) and Edge Configuration Servers (ECSs) necessary for enabling UE Application Clients (ACs) to interact with Edge Application Servers (EASs) over 3GPP networks. For edge computing, it is essential that UE ACs can locate and connect with the most suitable EASs available within the Edge Data Networks (EDNs) that the UEs are located in. This is dependent on the needs of the ACs and the availability of EASs in edge data networks. The EEL supports a set of services and exposes those services via APIs defined for each of the EEL defined reference points (e.g., EDGE-1 thru EDGE-9).

[0033] Some of these EEL defined services include but are not limited to:

[0034] Sen ices for discovery' of ECSs and provisioning of edge computing services based on a UEs location and service requirements;

[0035] Sendees for registration of EECs to EESs and EASs to EESs;

[0036] Sendees for providing continuity of service between ACs and EASs (e.g., when a UE moves from one EDN to another EDN); and

[0037] Exposure of 5GC services for use by EASs.CNV15060W001 / 101859.002202

[0038] Edge application enabler service layers such as the 3GPP defined EEL currently lack energy aware features and capabilities. This lack of energy' awareness prevents edge application enabler service layers from supporting energy aware functionality including but not limited to the following:

[0039] Lack of awareness of available energy credits of a subscriber;

[0040] Lack of awareness of renewable energy preferences of a subscriber;

[0041] Lack of capability to provision EECs and their associated ACs and EESs to EDNs which support energy profiles to meet their energy profile preferences (e.g., support a desired renewable energy mix);

[0042] Lack of capability that allows EECs and their associated ACs and EESs to discover EASs which meet their energy profile preferences;

[0043] Lack of capability’ to enable EASs with awareness of energy profile preferences of ACs and EESs; and

[0044] Lack of capability for EASs, EECs, ACs, and ESSs to receive energy aware EEL event information such as when changes to supported and / or preferred energy profiles of EEL entities occur.

[0045] Methods and procedures are described herein to enhance EEL architectures such as but not limited to the 3GPP defined EEL with energy aware capabilities. The following is a summary of EEL energy aware capabilities proposed herein. More detailed descriptions are captured in the subsequent procedures defined below.

[0046] EEL entities may be equipped with energy aware functionality’ capable of:

[0047] (1) Creating, storing, updating, retrieving and sharing energy aware EEL profiles for ESSs, ACs, EECs, EESs, EASs, and ECSs comprising energy centric information elements such as those defined in Tables 1-6. E.g.. energy credits, energy mix, energy sources, energy providers, energy score, energy’ rate.

[0048] (2) Based on energy' aware EEL profile information, detecting events such as: detecting an EEC having EEC, AC, and / or ESS energy profile information which meets the energy aware event criteria of the EAS (e.g., has registered to the EES); detecting an EEC has performed an EAS discovery request comprising EAS discovery criteria which meet the energy aware event criteria of the EAS; detecting an EAS having EAS energy' profile information which meets the energy aware event criteria of the EEC has been detected (e.g., has registered to the EES); detecting an EAS’s energy profile no longer meets the energy profile preferencesCNV15060W001 / 101859.002202 of an EEC or vice versa; and detecting an EES has performed a service continuity operation, and the EEC has been assigned to a different EAS having a different energy profde than the EAS which the EEC was assigned to.

[0049] (3) Based on energy aware EEL profiles and events, performing energy aware EEL operations such as: energy aware ECS service provisioning, energy aware AC registration, energy aware EEC registration, energy aware EAS registration, energy' aware EES registration, energy aware EAS discovery, energy’ aware EEL event subscriptions and notifications, energy aware ELL service continuity, and energy aware EEL charging.

[0050] (4) Using analytics and Al functions or services in the system to perform energy EEL aware operations such as: predict and / or learn future availability of supported energy mixes, supported energy types, supported energy providers, supported energy scores, supported energy rates, supported energy credits, and / or supported KPIs of an EEL entity; predict and / or leam future energy score for an EEL entity; perform proactive energy' aware operations such as triggering the instantiation of an EAS with a supported energy profile meeting the required energy profile of one or more ACs or ESSs; and predict and / leam the need to switch an AC to different EAS(s) based on energy profile related information and / or events, or learning energy aware EEL event occurrences or patterns.

[0051] FIG. 2 shows an example energy' aware EEL architecture 200. To enable energy aware EEL functionality within the EEL architecture 200, energy' aware capabilities are proposed herein within several EEL entities (EEC, ECS and EES) as shown in FIG. 2. This proposed functionality enables EEL operations to take place in an energy aware manner. Energy awareness may mean that EEL operations such as EEL registration, EAS discovery, EEL event exposure, EEL service continuity and EEL charging operations are performed based on energy' profile information applicable to EEL entities such as ESSs, ACs, EECs, EESs, ECSs, and EASs. For example, EASs having supported energy profiles may be discovered by ACs with energy profile preferences. Energy profiles may comprise energy centric information. For example, information such as preferred and / or supported types of renewable energy' mixes, types, credits, and / or suppliers.

[0052] Energy aware EEL profiles are described herein. EEL entities may originate and / or be configured with certain types of energy aware EEL profiles. For example, energy aware EEL profiles may be configured onto EEL entities such as EECs, ECSs, EESs, EASs, or ACs. Energy’ aware EEL profiles may also be associated with ECSPs and ESSs. Energy' awareCNV15060W001 / 101859.002202EEL profiles may comprise EEL energy centric information elements. Energy aware EEL profiles may be used by EEL entities to perform local EEL operations in an energy' aware manner. EEL entities may also exchange energy’ aware EEL profiles when performing energy aware EEL operations. Lastly, EEL entities may interact with other functions in the system (e.g., 3GPP core network or RAN functions) to collect energy aware EEL profile related information such as energy' consumption information and / or preferences.

[0053] Energy aware EEL profiles may be comprised of one or more information elements such as but not limited to those defined in Tables 1 - 6 for ESSs, ACs, EECs, ECSs, EASs and EESs, respectively.

[0054] Energy aware EEL profiles may comprise information stored and maintained by one or more EEL entities. The energy aware EEL profiles may be stored and maintained on a single entity in the system (e.g., on an ECS) or distributed across multiple entities in the system (e.g., on one or more EECs and / or EESs). If energy aware EEL profiles are stored and maintained in a distributed manner, EEL entities may support methods to keep the profiles synchronized with one another. In addition, if energy' aware EEL profiles are stored and maintained in a distributed manner, then some entities may only require storing a subset of the profiles (e.g., an EEC may only require storing a subset of the profiles while the EES server may store the complete set of profiles).

[0055] EEL entities may support functionality (e.g., APIs) for creating, storing, updating, retrieving and sharing energy profile information.

[0056] Note, the information shown in Tables 1 - 6 may be grouped together into one or more profiles. An EEL entity may be configured with these one or more profiles and in turn use these profiles to perform energy aware EEL operations. An EEL entity7may be configured with the one or more profiles based on procedures proposed in this invention and / or by other means.Table 1 - ESS Energy ProfileCNV15060W001 / 101859.002202CNV15060W001 / 101859.002202Table 2 - AC Energy ProfileTable 3 - EEC Energy ProfileCNV15060W001 / 101859.002202Table 4 - ECS Energy ProfileCNV15060W001 / 101859.002202Table 5 - EAS Energy ProfileCNV15060W001 / 101859.002202CNV15060W001 / 101859.002202Table 6 - EES Energy ProfileCNV15060W001 / 101859.002202

[0057] FIG. 3 provides an overview 300 of the different ty pes of energy7aware EEL operational procedures proposed herein. For each of the procedures defined in FIG. 3, separate detailed descriptions are defined in subsequent individual procedures herein. Note, the procedures defined in FIG. 3 may be sequenced in an order different than is shown. In addition, some procedures shown in FIG. 3 may be optional and / or performed independent of other procedures shown. In the example of FIG. 3, at step 1, the UE(s), EES, and ECS may perform energy aware ECS provisioning. At step 2, the AC(s) and EEC of the UE(s) may perform energy aware AC registration. At step 3, the EEC of the UE(s)s and the EES may performCNV15060W001 / 101859.002202 energy aware EEC registration. At step 4, the EES and EAS(s) may perform energy aware EAS registration. At step 5, the EES and ECS may perform energy aware EES registration. At step 6, the UE(s) and EES may perform energy aware EAS discovery. At step 7, the EES and EAS(s) may perform energy aware EEL event exposure. At step 8, the UE(s) and EES may perform energy aware EEL event exposure. At step 9, the UE(s), EES, ECS, and EAS(s) may perform energy aware EEL service continuity. At step 10, the UE(s), EES, ECS, and EAS(s) may perform energy aware EEL charging.

[0058] FIG. 4 shows an example of energy aware ECS service provisioning 400. ECS service provisioning involves configuring an EEC with information about available EES and EAS entities via interaction with an ECS. As shown in FIG. 4, ECS service provisioning may be performed in an energy aware manner. In the example of FIG. 4, at step 1, the EEC may send an energy aware service provisioning request to the ECS. The request may include EEC energy profile information defined in Table 3, AC energy profile information defined in Table 2, and / or ESS energy profile information defined in Table 1.

[0059] At step 2, upon receiving the request from the EEC, the ECS may determine, based on the EEC. AC, and / or ESS energy profile information, an EDN, EES, EAS. and / or bundle of EASs which meet the preferred energy profile of the EEC, ACs and / or ESSs. The ECS may7base this determination on the preferred energy mix, preferred energy types, preferred energy providers, preferred energy7score, preferred energy7rates, energy7credit information, and / or required KPIs specified by the EEC and / or AC. The ECS may compare this information against the supported energy mixes, supported energy types, supported energy providers, supported energy rates, supported energy credits, energy scores, and / or supported KPIs of the EESs, EASs, and / or bundles of EASs associated with ECS and / or its associated ECSP, EDN, or PLMN. The ECS may also base this determination on the energy profile information of one or more EESs or EASs. If an EES and / or EAS which meets the preferred energy profile of the EEC, ACs, or ESSs is not already instantiated, an ECS may trigger the instantiation of an EAS or bundle of EASs which meet the required energy profile of the EEC, ACs, or ESSs.

[0060] At step 3, the ECS may utilize the capabilities of the 3GPP core network to determine the supported energy mixes, supported energy types, supported energy providers, supported energy rates, supported energy credits, energy scores, and / or supported KPIs of the ECS and / or its associated ECSP, EDN, or PLMN. An ECS may also utilize the capabilities of the 3GPP core network to uery for the preferred energy7mix, preferred energy types, preferredCNV15060W001 / 101859.002202 energy providers, preferred energy scores, preferred energy rates, energy credit information, and / or required KPIs of an EEC, ACs, or ESSs. Alternatively, an ECS may send an EEC’s, AC's, or ESS’s preferred energy mix, preferred energy types, preferred energy providers, preferred energy scores, preferred energy rates, energy credit information, and / or required KPIs which it receives from an EEC, AC, ESS to one or more functions in the 3GPP core network. The ECS may invoke a NEF energy7aware API to obtain / send energy7preferences or other energy related information (e.g.. available energy credits) of an EEC, AC, or ESS from / to the 3 GPP core network.

[0061] At step 4, the ECS may utilize the capabilities of an analytics function or service in the system to obtain energy7centric predictions such as predicted future availability7of supported energy mixes, supported energy7types, supported energy providers, supported energy scores, supported energy rates, supported energy credits, and / or supported KPIs of the ECS and / or its associated ECSP, EDN, PLMN, EESs, and / or EASs. Based on the predicted future availability, an ECS may make more optimal and informed decisions regarding the selection of EDN(s) and EES(s) to provision to an EEC. An ECS may also use analytics to determine an energy score for an EES and / or EDN to rate which EDN(s) and EES(s) are optimal for a particular EEC / AC. This energy score may be generated by analytics and / or based on the analytics information and may be associated with an EDN, EAS or EES. The ECS may invoke a NEF, NWDAF, or AD AES energy7aware API to determine these energy7centric predictions. An ECS may also use analytics to predict energy consumption under a certain EDN configuration (e.g. estimating the total energy consumption / score for a certain set of scheduling and resource allocations of EESs), predict energy7consumption for instantiating a new EAS or EES, or predict energy7consumption change after a certain EEL event (e.g. service continuity ).

[0062] At step 5, the ECS may utilize the capabilities of an AIML function or sen ice in the system to leam energy centric patterns such as availability patterns and schedules of supported energy7mixes, supported energy ty pes, supported energy7providers, supported energy scores, supported energy rates, supported energy credits, and / or supported KPIs associated w ith an energy7rate. These learned energy centric patterns may be associated with an ECS and / or its associated ECSP, EDN, PLMN, EESs, and / or EASs. An ECS may also utilize the capabilities of an AIML function or service to perform one or more proactive energy7aware operations such as triggering the instantiation of an EAS with a supported energy7profile meeting the requiredCNV15060W001 / 101859.002202 energy profile of one or more ACs or ESSs. The ECS may invoke an energy aware API of a NEF or AIML function or service to assist in learning these energy' centric patterns or proactively performing these energy centric operations.

[0063] At step 6, if the processing of the request was successful, the ECS may respond to the EEC's request with an energy7aware service provisioning response. The response may comprise identifiers of EDN(s) and / or EES(s) supporting the renewable energy mix, renewable energy types, energy providers, energy7scores, energy rates, energy credit information, and / or KPI preferences of the EEC and / or AC(s) associated with the request. Alternatively, if the energy preferences cannot be met, the ECS may reject the request and return a response comprising an indication of the rejection.

[0064] FIG. 5 shows an example procedure 500 for the energy aware EEL registration operations described herein. Energy Aware AC Registration is shown in FIG. 5. As shown in FIG. 5, an AC may register to an EEC in an energy aware manner.

[0065] At step 1, an EEC may receive an energy aware registration request from an AC. The request may comprise AC energy profile information defined in Table 2. The request may also comprise ESS energy7profile information defined in Table 1.

[0066] At step 2, the EEC may, upon receiving the request from the AC, the EEC may determine, based on the AC and / or ESS energy profile information, if the ECSP(s), PLMN(s), EDN(s), ECS(s) EES(s), or EAS(s) that is has already been provisioned or registered with meet the preferred energy profile of the AC and / or ESS. The EEC may base this determination on the preferred energy mix, preferred energy types, preferred energy7providers, preferred energy scores, preferred energy7rates, energy credit information, and / or required KPIs specified by the AC and / or ESS. The EEC may compare this information against the supported energy mixes, supported energy ty pes, supported energy providers, supported energy scores, supported energy rates, supported energy credits, and / or supported KPIs of the ECSP(s), PLMN(s), EDN(s), ECS(s) EES(s), or EAS(s) that is has already been provisioned or registered with. If the EEC is unable to identify ECSP(s), PLMN(s), EDN(s), ECS(s) EES(s), or EAS(s) which meets the preferred energy7profile of the AC or ESS, an EEC may perform one or more energy aware ECS service provisioning operations or energy aware EEC registration operations.

[0067] At step 3, the EEC may utilize the capabilities of an analytics function or service in the system to obtain energy7centric predictions such as predicted future availability7CNV15060W001 / 101859.002202 of supported energy mixes, supported energy types, supported energy providers, supported energy scores, supported energy rates, supported energy credits, and / or supported KPIs of an ECS and / or its associated ECSP, EDN. PLMN, EESs, and / or EASs. Based on the predicted future availability, an EEC may make more optimal and informed decisions regarding the selection of ECSP(s), PLMN(s), EDN(s), ECS(s) EES(s), or EAS(s). An EEC may also use analytics to determine an energy score for an ECSP(s), PLMN(s), EDN(s), ECS(s) EES(s), or EAS(s) to rate which ECSP(s), PLMN(s), EDN(s), ECS(s) EES(s). or EAS(s) are optimal for use by the EEC, ACs or ESSs. This energy score may be generated by analytics and may be associated with an ECSP(s), PLMN(s), EDN(s), ECS(s) EES(s), or EAS(s). The EEC, via an AD AES client, may send one or more requests to an AD AES energy aware server to obtain these energy centric predictions.

[0068] At step 4, the EEC may utilize the capabilities of an AIML function or service in the system to leam energy centric patterns such as availability patterns and schedules of supported energy7mixes, supported energy ty pes, supported energy' providers, supported energy scores, supported energy rates, supported energy credits, and / or supported KPIs associated w ith an energy’ rate. These learned energy centric patterns may be associated with an EEC and / or its associated PLMN(s), EDN(s), ECS(s) EES(s), or EAS(s). An EEC may also utilize the capabilities of an AIML function or service to perform one or more proactive energy' aware operations such as triggering one or more energy' aware operation such as energy' aw are EAS discovery, energy aware EES registration, energy aware service continuity operations. The EEC. via an AIML client, may invoke an energy aware API available in an AIML function or service to assist in learning these energy centric patterns or proactively performing these energy centric operations.

[0069] At step 5, if the processing of the request was successful, the EEC may respond to the AC’s request with an energy aware AC registration response. The response may comprise identifiers of EAS(s) supporting the renewable energy' mix, renewable energy types, energy providers, energy' scores, energy' rates, energy credit information, and / or KPI preferences of the AC and / or ESS associated with the request. Alternatively, if the energy preferences cannot be met, the EEC may reject the request and return a response comprising an indication of the rejection.

[0070] FIG. 6 shows an example energy aware EEC registration procedure 600. As shown in FIG. 6, an EEC may register to an EES in an energy aware manner.CNV15060W001 / 101859.002202

[0071] At step 1, an EES may receive an energy aware registration request from an EEC. The request may comprise EEC energy profile information defined in Table 3, AC energy profile information defined in Table 2 pertaining to AC(s) associated with the EEC, and / or ESS energy profile information defined in Table 1 pertaining to ESS(s) associated with the AC(s).

[0072] At step 2, upon receiving the request from the EEC, the EES may determine, based on the EEC, AC and / or ESS energy profile information, if EAS(s) that have already registered with the EES meet the preferred energy’ profile of the EEC, ACs and / or ESSs. The EES may base this determination on the preferred energy- mix, preferred energy types, preferred energy providers, preferred energy scores, preferred energy rates, energy credit information, and / or required KPIs specified by the EEC, AC(s) and / or ESS(s). The EES may compare this information against the supported energy mixes, supported energy types, supported energy providers, supported energy scores, supported energy- rates, supported energy credits, and / or supported KPIs of the registered EAS(s). If the EES is unable identify EAS(s) which meet the preferred energy profile of the EEC, AC(s) and / or ESS(s), an EES may trigger a dynamic energy aware EAS instantiation operation to instantiate an EAS which meets the energy profile preferences.

[0073] At step 3, the EES may utilize the capabilities of the 3GPP core network to determine the supported energy mixes, supported energy types, supported energy providers, supported energy rates, supported energy- credits, energy- scores, and / or supported KPIs associated with an EES, ECSP, EDN, or PLMN. An EES may also utilize the capabilities of the 3GPP core network to query for the preferred energy mix, preferred energy types, preferred energy providers, preferred energy scores, preferred energy rates, energy credit information, and / or required KPIs of an EEC, ACs, or ESSs. Alternatively, an EES may send an EEC’s, AC’s, or ESS's preferred energy mix, preferred energy types, preferred energy providers, preferred energy scores, preferred energy- rates, energy credit information, and / or required KPIs which it receives from an EEC, AC, ESS to one or more functions in the 3GPP core network. The EES may invoke a NEF energy aware API to obtain / send energy preferences or other energy related information (e.g., available energy credits) of an EEC, AC or ESS from / to the 3GPP core network.

[0074] At step 4, the EES may utilize the capabilities of an analytics function or service in the system to obtain energy centric predictions such as predicted future availability of supported energy- mixes, supported energy- ty pes, supported energy providers, supportedCNV15060W001 / 101859.002202 energy scores, supported energy rates, supported energy credits, and / or supported KPIs of the EES and / or its associated ECSP, EDN, PLMN, and / or EASs. Based on the predicted future availability, an EES may make more optimal and informed decisions regarding the selection of EDN(s) and EAS(s) to provision to an EEC, AC or ESS. An EES may also use analytics to determine an energy profile and / or energy scores for an EAS and / or EDN to rate which EDN(s) and EAS(s) are optimal for a particular EEC, AC. This energy7profile or score may be generated by analytics and / or based on the analytics information and may be associated with an EDN or EAS. The EES may invoke a NEF, NWDAF, or AD AES energy' aware API to determine these energy centric predictions. An EES may also use analytics to predict energy consumption under a certain EDN configuration (e.g. estimating the total energy consumption / score for a certain set of scheduling and resource allocations of EEL entities), predict energy consumption for instantiating a new EAS. or predict energy consumption change after a certain EEL event (e.g. service continuity).

[0075] At step 5, the EES may utilize the capabilities of an AIML function or sendee in the system to leam energy centric patterns such as availability patterns and schedules of supported energy mixes, supported energy types, supported energy7providers, supported energy scores, supported energy rates, supported energy credits, and / or supported KPIs associated with an energy rate associated with EEL entities. These learned energy centric patterns may be associated with EEL entities such as an EEC or EAS and / or an associated ECSP, EDN, PLMN. An EES may also utilize the capabilities of an AIML function or service to perform one or more proactive energy aware operations such as triggering the instantiation of an EAS with a supported energy7profile meeting the required energy profile of one or more ACs or ESSs. An EES may leam demand patterns of EAS(s) with certain energy profiles. Based on the predictions an EES may make more optimal and informed decisions regarding the selection of EAS(s) to return in energy aware EAS discovery responses. The EES may invoke an energy aware API of a NEF or AIML function or service to assist in learning these energy centric patterns or proactively' performing these energy centric operations.

[0076] At step 6, if the processing of the request was successful, the EES may respond to the EEC’s request with an energy aware EEC registration response. The response may comprise identifiers of EAS(s) supporting the renewable energy mix, renewable energy types, energy providers, energy scores, energy rates, energy credit information, and / or KPI preferences of the EEC, AC(s), and / or ESS(s) associated with the request. Alternatively, if theCNV15060W001 / 101859.002202 energy preferences cannot be met, the EES may reject the request and return a response comprising an indication of the rejection such as indication that the energy preferences specified by the EEC cannot be met.

[0077] FIG. 7 shows an example energy aware EAS registration procedure 700. As shown in FIG. 7, an EAS may register to an EES in an energy aware manner.

[0078] At step 1, an EES may receive an energy' aw are registration request from an EAS. The request may comprise EAS energy profile information defined in Table 5.

[0079] At step 2, upon receiving the request from the EAS, the EES may store the EAS energy profile information such that the EES may make use of this information when performing energy aware operations such as energy aware EAS discovery, energy aware EEC registration, and energy' aw are EEL service continuity operations.

[0080] At step 3. the EES may utilize the capabilities of the 3GPP core network to query for the preferred energy' mix, preferred energy types, preferred energy providers, preferred energy scores, preferred energy' rates, energy' credit information, and / or required KPIs of one or more EEL entities (e.g., an EAS or its associated ACs or ESSs). Alternatively, an EES may send an EAS’s or its associated AC’s or ESS’s preferred energy mix. preferred energy ty pes, preferred energy providers, preferred energy' scores, preferred energy rates, energy credit information, and / or required KPIs which it receives from an EAS to one or more functions in the 3GPP core network. The EES may invoke a NEF energy aw are API to obtain / send energy' preferences or other energy related information (e.g., available energy credits) from / to the 3GPP core network.

[0081] At step 4, the EES may utilize the capabilities of an analytics function or service in the system to obtain energy' centric predictions such as predicted future availability of supported energy mixes, supported energy' types, supported energy providers, supported energy scores, supported energy rates, supported energy’ credits, and / or supported KPIs of the EAS and / or its associated ACs or ESSs. Based on the predicted future availability, an EES may make more optimal and informed decisions regarding the selection of EAS(s). An EES may also use analytics to determine an energy demands and / or energy' scores for an EAS. This energy demand or score may be generated by analytics and / or based on the analytics information and may be associated with an EAS. The EES may invoke a NEF, NWDAF, or ADAES energy aware API to determine these energy' centric predictions. An EES may also use analytics to predict energy' consumption under a certain EAS configuration (e.g. estimatingCNV15060W001 / 101859.002202 the total energy consumption / score for a certain set of scheduling and resource allocations of EAS), predict energy consumption for instantiating a new EAS, or predict energy consumption change after a certain EEL event (e.g. service continuity).

[0082] At step 5, the EES may utilize the capabilities of an AIML function or sendee in the system to leam energy centric patterns such as availability patterns and schedules of supported energy mixes, supported energy types, supported energy' providers, supported energy scores, supported energy rates, supported energy credits, and / or supported KPIs associated with an energy rate associated with an EAS. An EES may leam demand patterns of EAS(s) with certain energy profiles or energy' consumption patterns of certain EAS(s). Based on the predictions an EES may make more optimal and informed decisions regarding the selection of EAS(s) to return in energy aware EAS discovery responses. The EES may invoke an energy aware API of a NEF or AIML function or service to assist in learning these energy centric patterns or proactively performing these energy centric operations.

[0083] At step 6, if the processing of the request was successful, the EES may respond to the EAS with an energy aware EAS registration response comprising an indication that the request was successfully processed. Otherwise, the response may comprise a failure indication such as indication that the energy profile specified by the EAS cannot be supported.

[0084] FIG. 8 shows an example energy' aware EES registration procedure 800. As shown in FIG. 8, an EES may register to an ECS in an energy' aware manner.

[0085] At step 1, an ECS may receive an energy aware registration request from an EES. The request may comprise one or more EES energy profile information elements defined in Table 5 such as a list of EAS energy profiles for EASs w hich have already registered to the EES or which are EAS types supported by the EES.

[0086] At step 2, upon receiving the request from the EES, the ECS may store the EES energy profile information such that the ECS may make use of this information when performing energy aware operations such as energy aware ECS service provisioning operations. In addition, an ECS may7also determine supported ECS energy' profiles applicable to the EES and corresponding values for one or more of the ECS energy7profile information elements defined in Table 4. For example, the ECS's supported energy mix, energy sources, energy rates which to share with the ESS. An ECS may utilize the capabilities of an analytics function or service in the system to assist it with processing the energy aware EES registration request. For example, predicting optimal ECS energy7profile settings. An ECS may utilize theCNV15060W001 / 101859.002202 capabilities of an AIML function or service in the system to leam optimal ECS energy profile settings.

[0087] At step 3. the ECS may perform one or more energy aware operations with a 3GPP CN such as but not limited to the operations defined in step 3 of the ECS Sendee Provisioning procedure described herein.

[0088] At step 4, the ECS may perform one or more analytics-enabled energy' aware operations such as but not limited to the operations defined in step 4 of the ECS Service Provisioning procedure described herein.

[0089] At step 5, the ECS may perform one or more AIML-enabled energy aware operations such as but not limited to the operations defined in step 5 of the ECS Service Provisioning procedure described herein.

[0090] At step 6, if the processing of the request was successful, the ECS may respond to the EES with an energy aware EES registration response comprising an indication that the request was successfully processed. The response may also comprise ECS energy profile information elements such as those defined in Table 4. Otherwise, the response may comprise a failure indication such as indication that the energy profile specified by the EES cannot be supported.

[0091] FIG. 9 shows an example energy aware EAS discovery procedure 900. As shown in FIG. 9, an AC and / or EEC may send an energy' aware EAS discovery request to an EES to process in an energy aware manner.

[0092] At step 1. an EEC may receive an energy aware EAS discovery request from an AC. The request may include one or more energy aware EAS discovery' criteria. The EAS discovery' criteria may be based on one or more conditions. The conditions may be based on one or more EAS (or EAS bundle) supported energy profile information elements defined in Table 5, one or more AC preferred energy profile information elements defined in Table 2, and / or one or more ESS preferred energy profile information elements defined in Table 1. For example, a supported renewable energy' mix above a certain percentage, a supported energy provider, or a supported energy rate below' a certain value.

[0093] At step 2, upon receiving an energy aware EAS discovery request from an AC, the EEC may determine whether it is already aware of an EAS which meets the energy aw are EAS discovery criteria, and if so, return information of this EAS to the AC as described in step 11.CNV15060W001 / 101859.002202

[0094] At step 3, the EEC may utilize the capabilities of an analytics function or service in the system to assist it with processing the energy aware EAS discover)' request. For example, an EEC may leverage the capabilities of an analytics function in the system to assist in the selection of an EAS which is most likely able to meet the energy preferences and requirements of the AC. The analytics may consider historical energy centric pattens and trends of an EAS such as energy rates, energy mixes, energy7suppliers associated with an EAS. Based on the historical information, the analytics may be used to predict which EAS(s) are the best candidates to service the AC and meet its associated energy preferences.

[0095] At step 4, the EEC may utilize the capabilities of an AIML function or service in the system to leam current and / or future energy profiles of EASs and EAS availability7patterns. This information may in turn be compared against energy aware EAS discovery criteria to select one or more EASs which are the best candidate EAS(s) to service the AC both at the current time as well as into the future. For example, based on the current as well as the predicted future energy7mixes and rates. To perform these operations, the EEC may invoke an energy aware EAS discovery7API of an AIML function or service.

[0096] At step 5, the EEC may send energy aware EAS discovery7request(s) to EES(s) comprising the energy aware EAS discover}' criteria.

[0097] At step 6, upon receiving an energy7aware EAS discovery' request from an EEC or another EES, the EES may determine whether an EAS has already registered to the EES which meets the energy aware EAS discovery criteria, and if so, return information of this EAS to the EEC or the other EES as described in step 10.

[0098] At step 7, the EES may utilize the capabilities of an analytics function or service in the system to assist it with processing the energy7aware EAS discovery' request. An EES may leverage the capabilities of an analytics function in the sy stem to assist in the selection of an EAS which is able to meet the energy preferences and requirements of the EEC / AC. The analytics may consider historical energy7centric pattens and trends of an EAS such as energy rates, energy7mixes, energy suppliers associated with an EAS. Based on the historical information, the analytics may be used to predict which EAS(s) are the best candidates to service the EEC / AC and meet its associated energy preferences.

[0099] At step 8, the EES may utilize the capabilities of an AIML function or sendee in the system to leam current and / or future energy profiles of EASs and EAS availability patterns. This information may in turn be compared against energy' aware EAS discovery7CNV15060W001 / 101859.002202 criteria to select one or more EASs which are the best candidate EAS(s) to service the EEC / AC. For example, based on the current as well as the predicted future energy mixes and rates. To perform these operations the EES may invoke an energy aware EAS discovery API of an AIML function or service.

[0100] At step 9, the EES may trigger an energy aware instantiation of an EAS which meets the energy aware EAS discovery criteria. The EES may determine whether EAS instantiation should be triggered based on one or more criteria such as comparing the extra energy consumption of instantiating a new EAS and using existing less energy-efficient EAS.

[0101] At step 10, the EES may return an energy aware EAS discovery response to the EEC comprising information of a discovered EAS which meets the energy aware EAS discovery criteria. The response may include a list of EASs and certain information from their energy profile such as an energy score and an energy rate. The response may also include predicted or learned energy profile centric information of EASs such that this information may be used by EEC / AC to determine which EASs currently meet their energy preferences as well as which EASs are likely to continue to meet their energy7preferences for some desired time window / duration. For example, current as well as predicted EAS energy rates and mixes may be included in the response.

[0102] At step 11, the EEC may return an energy7aware EAS discovery response to the AC comprising information of a discovered EAS which meets the energy aware EAS discovery criteria. The response may include a list of EASs and certain information from their energy profile such as an energy score and an energy rate.

[0103] Energy7aware EEL event exposure is described herein. An EES may allow EASs or EECs to subscribe to energy aware events. Based on the energy aware event subscriptions, an EES may monitor and detect if / when the energy7related events occur. Based on the occurrence of the energy aware events, an EES may send energy7aware notifications to EASs or EECs to inform of them of the occurrence of these energy aware events. An EES may also perform one or more energy aware actions based on the occurrence of the energy' aware events.

[0104] FIG. 10 shows an example energy7aware EEL event subscription procedure 1000. As shown in FIG. 10, an EES may receive an energy aware subscription request from an EAS or EEC.CNV15060W001 / 101859.002202

[0105] At step 1, the EES may receive an energy aware subscription request from an EAS or EEC. The request may comprise energy aware event criteria. The energy aware event criteria may be based on conditions dependent upon one or more EES energy profile information elements defined in Table 6, one or more EAS energy profile information elements defined in Table 5, one or more EEC preferred energy profile information elements defined in Table 3one or more AC preferred energy' profile information elements defined in Table 2, and / or one or more ESS preferred energy’ profile information elements defined in Table 1. The energy aware event criteria may also be dependent upon one or more energy’ aware EEL operations such as an energy ayvare AC registration, energy aware EEC registration, energy aware EAS registration, energy ayvare EAS discovery, an energy ayvare ECS service provisioning, or energy aware service continuity operations. For example, an EAS may subscribe to receive notifications if / when an EEC registers to an EES having AC energy profile information having a certain preferred energy credit, energy mix, and energy source yvhich matches the supported energy credits, energy mix and energy sources of the EAS. Likeyvise, an EEC may subscribe to receive notifications if / when an EAS registers to an EES having an EAS energy profile having preferred energy credits, energy’ mix. or energy sources yvhich match the energy profile preferences of the EEC and / or its associated ACs or ESSs.

[0106] At step 2, upon receiving an energy ayvare EAS subscription request from an EAS or EEC, the EES may process the request by storing the subscription information including the energy ayvare event criteria. The EES may also start monitoring to detect if / when the energy aware event criteria have been met.

[0107] At step 3, the EES may utilize the capabilities of a 3GPP core network function or service to assist it with processing the energy ayvare subscription request. An EES may send one or more energy' aware subscription requests to a 3GPP core network function or service. The requests may comprise one or more energy aware event criteria parameters such as those described in Step 1.

[0108] At step 4, the EES may utilize the capabilities of an analytics function or service in the system to assist it with processing the energy aware subscription request. An EES may send one or more energy aware analytics requests to an analytics function or serv ice requesting analytics to performed related to one or more energy aware event criteria parameters such as those described in Step 1.CNV15060W001 / 101859.002202

[0109] At step 5, the EES may also utilize the capabilities of an AIML function or sen-ice in the system to assist it with processing the energy aware subscription request. An EES may send one or more energy aware requests to an AIML function or service requesting AIML inferencing operations to performed related to one or more energy aware event criteria parameters such as those described in Step 1.

[0110] At step 6, if the processing of the energy aware subscription request was successful, the EES may respond to the EAS or EEC with an energy aware EAS subscription response comprising an indication that the request was successfully processed. Otherwise, the response may comprise a failure indication.

[0111] FIG. 11 shows an example energy aware EEL event notification procedure 1100. As shown in FIG. 11, an EES may send an energy aware notification to an EES or EEC.

[0112] At step 1. an EES may utilize the capabilities of a 3GPP core network function or service, analytics function or service, and / or AIML function or service in the system to detect if / when the energy aware event criteria have been met. The EES may receive one or more energy aware notifications from these entities with energy aware EES subscription(s). The notifications may comprise one or more energy aware information elements such as but not limited to those defined in Table 1, Table 2, Table 3, Table 4, Table 5, or Table 6.

[0113] At step 2, based on notifications received in step 1 and / or locally detection of energy aware events, the EES determines energy- aware EEL event criteria associated with an EAS subscription have been met. This determination may be based on the information the EES receives from a 3GPP CN. analytics, and / or AIML function or service in the system as described above in steps 1, 2, and 3.

[0114] At step 3, the EES may perform one or more energy- EEL actions based on determining the energy aware EEL event criteria have been met. An EES may perform energy aware service continuity- operations such as triggering an EEC to perform an EEL sen-ice continuity operation or EAS discovery operation if / when the current EAS servicing an EEC no longer meets the preferred energy profile of an EEC, AC or ESS. For example, trigger an EEL sen-ice continuity- operation or EAS discovery- operation if / when the EAS renewable energy mix, available energy credits, and / or energy rates no longer meet the preferred energy profile of an EEC, AC or ESS. In addition, an EES may trigger the instantiation of an EAS which meets the preferred energy profile of an EEC, AC or ESS if an EAS is no longer available.CNV15060W001 / 101859.002202

[0115] At step 4, the EES may send an energy aware notification to an EAS or EEC. The notification may comprise one or more energy centric information elements such as but not limited energy profile information elements defined in Table 1. Table 2, Table 3, Table 4, Table 5, or Table 6. The notification may also comprise an energy aware event identifier indicating the type of an energy aware event that has been detected by the EES. For example, the energy aware event identifier may indicate one or more of the following types of energy aware events:

[0116] The EEC having EEC, AC, and / or ESS energy profile information which meets the energy aware event criteria of the EAS has been detected (e.g., has registered to the EES),

[0117] An EEC has performed an EAS discovery request comprising EAS discovery criteria which meet the energy aware event criteria of the EAS,

[0118] An EAS having EAS energy profile information which meets the energy aware event criteria of the EEC has been detected (e.g., has registered to the EES, has been instantiated),

[0119] An EAS’s energy profile no longer meets (or is predicted to no longer meet) the energy profile preferences of an EEC or vice versa,

[0120] An EES has performed a service continuity operation, and the EEC has been assigned to a different EAS having a different energy profile than the EAS which the EEC was assigned to.

[0121] An EAS has been updated with renewable energy mix.

[0122] An EAS has been updated with a new energy score.

[0123] An EAS has updated energy' rate information.

[0124] A new energy profile is available.

[0125] A new energy provider is online and available.

[0126] At step 5, upon receiving an energy aware notification, the EAS or EEC may process the notification to determine the occurrence of one or more energy' aware events. Based on the notification, the EAS or EEC may perform one or more actions such as but not limited to:

[0127] Trigger one or more EEL service continuity operations (e.g., to switch to a different EAS),CNV15060W001 / 101859.002202

[0128] Reserve EAS or EEC compute and energy resources to service future requests from EEL entities such as ACs or ESSs,

[0129] Switch to using a different energy profile compatible with other EEL entities (e.g., an EAS can switch to using an energy profile aligned with the preferred energy profiles of one or more ACs or ESSs),

[0130] Perform one or more energy' aware EAS discovery request to discover another EAS with an energy’ profile aligned with the energy’ profile preferences of an EEC and / or its associated ACs or ESSs.

[0131] FIG. 12 shows an example energy aware EEL service continuity' procedure 1200. In certain energy' related circumstances, the EAS(s) servicing an AC may need to be switched to different EAS(s). As shown in FIG. 12, an EEL entity such as an EES, ECS, EAS, EEC. or AC may trigger and / or execute energy aware EEL service continuity operations.

[0132] At step 1, an EEL entity (e.g., EES, ECS, EAS, or EEC / AC) may detect the need to perform an EEL service continuity operation such as switching an AC to a different EAS or switching an EEC to a different EES. This detection may be performed in an energy- aware manner using energy profile information such as but not limited to the information elements defined in Tables 1-6. For example, the energy profile preferences of an AC (and its associated ESS) may no longer align with the supported energy profile of an EAS (and it associated ECSP). In such circumstances, the EEL entity’ may detect this condition. The EEL entity may perform this detection in a reactive manner such as when changes to the preferred and / or supported energy profiles of EEL entities occur. Alternatively, an EEL entity may perform this detection in a proactive manner based on predicting and / or learning when switches to different EAS(s) will be needed. In another example, an EEC may require switching to a different EES for to load balance energy consumption across EESs.

[0133] At step 2, the EEL entity may utilize the capabilities of a 3GPP core network function or service to assist it with detecting the need to switch an AC to different EAS(s) based on energy profile related information and / or events. An EEL entity may' send one or more energy aware requests to a 3GPP core network function or service to obtain information which the EEL entity uses for this detection. For example, a 3GPP core network function or service may send a notification to the EEL entity if / when a change is made to the energy profile preferences (e.g., preferred renewable energy' mix) of a subscriber. The EEL entity' may useCNV15060W001 / 101859.002202 this information to determine if / when to switch to different EAS(s) and / or which EAS(s) to switch to.

[0134] At step 3, the EEL entity’ may utilize the capabilities of an analytics function or service in the system to assist it with detecting the need to switch an AC to different EAS(s) based on energy profile related information and / or events. An EEL entity may send one or more energy aware analytics requests to an analytics function or service requesting analytics be performed related to one or more energy profile information elements and / or energy’ aware events. For example, an analytics function or service may send a notification to the EEL entity if / when it predicts a change in the supported energy profile of an EAS (e g., supported energy sources). The EEL entity may use this information to determine i f / when to switch to different EAS(s) and / or which EAS(s) to switch to.

[0135] At step 4. the EEL entity may also utilize the capabilities of an AIML function or service in the system to assist it with detecting the need to switch an AC to different EAS(s) based on energy’ profile related information and / or events. An EEL entity may send one or more energy' aware requests to an AIML function or service requesting AIML inferencing operations be performed related to one or more energy profile information elements and / or energy ayvare events. For example, an AIML function or service may leam patterns regarding changes in the supported energy profile of EAS(s) such as different energy’ rate or mix availability schedules. The AIML function or service may share this information with the EEL entity to enable it to determine if / when to switch to different EAS(s) and / or which EAS(s) to switch to.

[0136] At step 5, after detecting the need to switch an AC to different EAS(s) based on energy’ profile related information and / or events, an EEL entity may itself execute one or more energy aware EEL service continuity operations. Alternatively, an EEL entity may request another EEL entity to perform the operation(s). The types of energy aware EEL sendee continuity operations may include discovering different and selecting new EAS(s) yvith supported energy profiles yvhich are aligned yvith the energy profile preferences of an AC, transferring energy profile information from the EAS(s) currently serving an AC to the new EAS(s).

[0137] At step 6, the EEL may inform and EEC / AC and current EAS(s) of the change in EAS(s) including any changes in energy profile information.CNV15060W001 / 101859.002202

[0138] FIG. 13 shows an example energy' aware EEL charging procedure 1300. As shown in FIG. 13, an EEL entity such as an EES, ECS or EAS may perform energy aware EEL charging operations with a charging function (CHF) in the system.

[0139] At step 1, an EEL entity (e.g., EES, ECS or EAS) may perform an EEL operation in an energy aware manner. For example, an energy aware ECS service provisioning, energy aware EEL registration, energy aware EAS discovery, energy7aware EEL event exposure operation, or energy aware EEL service continuity7operation.

[0140] At step 2, the EEL entity may send an energy aware EEL charging data request to a charging function (CHF) in the system. The request may comprise one or more EEL energy7profile information elements such as those defined in Table 1, Table 2, Table 3, Table 4, Table 5, or Table 6. The request may comprise information (e.g., operation identifier) regarding one or more EEL energy aware operations performed by the EEL such as the operations mentioned in step 1. The request may comprise information (e.g., event identifier) regarding one or more energy7aware EEL events which an EEL entity7detects and reports to the CHF. For example, the request may comprise information regarding the energy credits consumed to perform EEL operation(s). The request may comprise energy consumption information of the EEL infrastructure hosting the EEL entities such as mean energy consumed, measured energy7consumed, energy mix during consumption, energy rate during consumption, energy consumption start time, and / or energy7consumption end time.

[0141] At step 3, upon receiving the request, the CHF may create an energy aware EEL charging data record (CDR). The CDR may comprise one or more EEL energy centric information elements such as those received in the request and described in step 2. The CHF may store the energy7aware EEL CDR. The CHF may send the energy7aware EEL CDR to one or more other entities in the system for further processing.

[0142] At step 4, the CHF may return an energy aware EEL charging data response to the EEL entity. The response may comprise an indication if the request was successfully processed and an associated energy7aware EEL CDR was created. The response may also include information from the energy aware EEL CDR.

[0143] A RESTful energy aware EEL embodiment is described herein. In one embodiment, EEL clients and servers may implement energy aware EEL profiles and services using RESTful APIs. These APIs may be realized as resources having unique addresses (e g. URIs, URNs, etc.) and may also have one or more attributes that contain resource data and / orCNV15060W001 / 101859.002202 metadata. These energy aware EEL profiles and sendee resources may be created, retrieved, discovered, updated, or deleted by VAL clients and servers, EEL entities such as EESs, ECSs, as well as other clients and servers in the system. The EEL clients and servers may realize these APIs using RESTful protocols such as HTTP and CoAP. In addition, subscriptions may also be made to profiles and service resources to receive notifications if / when any modifications are made to the resources.

[0144] A Pub / Sub energy aware EEL embodiment is described herein. In another embodiment, EEL clients and servers may implement energy aware EEL profiles and services as topics within the topic space of a message broker (e.g., MQTT broker, AMQP broker, etc.). An EEL client and / or server may function as the message broker. Alternatively, the message broker may be hosted external to the EEL client and / or server by another node or function in the network which the EEL client and / or server communicates with to create, update, retrieve, delete, and subscribe to energy aware EEL profiles and service topics.

[0145] The topics may have unique addresses (e.g. topic names, etc.) and one or more attributes that contain topic data and / or metadata. These profiles and service topics maybe published to or subscribed to by VAL clients and servers as well as EEL clients and servers.

[0146] FIG. 14 shows an example of an energy Aware EEL graphical user interface embodiment 1400. The example of FIG. 14 is an energy management GUI embodiment for the techniques described herein.

[0147] The 3rd Generation Partnership Project (3GPP) develops technical standards for cellular telecommunications network technologies, including radio access, the core transport network, and service capabilities - including work on codecs, security, and quality of sendee. Recent radio access technology (RAT) standards comprise WCDMA (commonly referred as 3G), LTE (commonly referred as 4G), LTE-Advanced standards, and New Radio (NR), which is also referred to as “5G” 3GPP NR standards development is expected to continue and comprise the definition of next generation radio access technology (new RAT), which is expected to comprise the provision of new flexible radio access below 7 GHz, and the provision of new ultra-mobile broadband radio access above 7 GHz. The flexible radio access is expected to consist of a new. non-backwards compatible radio access in new spectrum below 7 GHz, and it is expected to comprise different operating modes that may be multiplexed together in the same spectrum to address a broad set of 3GPP NR use cases with diverging requirements. The ultra-mobile broadband is expected to comprise cmWave and mmWaveCNV15060W001 / 101859.002202 spectrum that may provide the opportunity for ultra-mobile broadband access for, e.g., indoor applications and hotspots. In particular, the ultra-mobile broadband is expected to share a common design framework with the flexible radio access below 7 GHz, with cmWave and mmWave specific design optimizations.

[0148] 3GPP has identified a variety of use cases that NR is expected to support, resulting in a wide variety of user experience requirements for data rate, latency, and mobility. The use cases comprise the following general categories: enhanced mobile broadband (eMBB) ultra-reliable low-latency Communication (URLLC), massive machine type communications (mMTC), network operation (e.g., network slicing, routing, migration and interworking, energy savings), and enhanced vehi cl e-to-every thing (eV2X) communications, which may comprise any of Vehicle-to-Vehicle Communication (V2V), Vehicle-to-Infrastructure Communication (V2I), Vehicle-to-Network Communication (V2N), Vehicle-to-Pedestrian Communication (V2P), and vehicle communications with other entities. Specific sendee and applications in these categories comprise, e.g., monitoring and sensor networks, device remote controlling, bi-directional remote controlling, personal cloud computing, video streaming, wireless cloud-based office, first responder connectivity, automotive ecall, disaster alerts, realtime gaming, multi-person video calls, autonomous driving, augmented reality, tactile internet, virtual reality, home automation, robotics, and aerial drones to name a few. All of these use cases and others are contemplated herein.

[0149] FIG. 15A illustrates an example communications system 100 in which the systems, methods, and apparatuses described and claimed herein may be used. The communications system 100 may comprise wireless transmit / receive units (WTRUs) 102a, 102b, 102c, 102d, 102e, 102f, and / or 102g, which generally or collectively may be referred to as WTRU 102 or WTRUs 102. The communications system 100 may comprise, a radio access network (RAN) 103 / 104 / 105 / 103b / 104b / 105b, a core network 106 / 107 / 109, a public switched telephone network (PSTN) 108, the Internet 110, other networks 112, and Network Services 113. 113. Network Services 113 may comprise, for example, a V2X server, V2X functions, a ProSe server, ProSe functions, loT services, video streaming, federated learning (FL) sendees, and / or edge computing, etc.

[0150] It may be appreciated that the concepts disclosed herein may be used with any number of WTRUs, base stations, networks, and / or network elements. Each of the WTRUs 102 may be any type of apparatus or device configured to operate and / or communicate in aCNV15060W001 / 101859.002202 wireless environment. In the example of FIG. 15 A, each of the WTRUs 102a-d is depicted in FIGs. 15A-15E as a hand-held wireless communications apparatus. It is understood that with the wide variety of use cases contemplated for wireless communications, each WTRU may comprise or be comprised in any type of apparatus or device configured to transmit and / or receive wireless signals, including, by way of example only, user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a pager, a cellular telephone, a personal digital assistant (PDA), a smartphone, a laptop, a tablet, a netbook, a notebook computer, a personal computer, a wireless sensor, consumer electronics, a wearable device such as a smart watch or smart clothing, a medical or eHealth device, a robot, industrial equipment, a drone, a vehicle such as a car, bus or truck, a train, or an airplane, and the like.

[0151] The communications system 100 may also comprise a base station 114a and a base station 114b. In the example of FIG. 15 A, each base stations 114a and 114b is depicted as a single element. In practice, the base stations 114a and 114b may comprise any number of interconnected base stations and / or network elements. Base stations 114a may be any type of device configured to wirelessly interface with at least one of the WTRUs 102a, 102b, and 102c to facilitate access to one or more communication networks, such as the core network 106 / 107 / 109, the Internet 1 10, Network Services 113, and / orthe other networks 112. Similarly, base station 114b may be any type of device configured to wiredly and / or wirelessly interface with at least one of the Remote Radio Heads (RRHs) 118a, 118b, Transmission and Reception Points (TRPs) 119a, 119b, and / or Roadside Units (RSUs) 120a and 120b to facilitate access to one or more communication networks, such as the core network 106 / 107 / 109. the Internet 110, other networks 112, and / or Network Services 113. RRHs 118a, 118b may be any type of device configured to wirelessly interface with at least one of the WTRUs 102, e.g., WTRU 102c, to facilitate access to one or more communication networks, such as the core network 106 / 107 / 109. the Internet 110, Network Services 113. and / or other networks 112.

[0152] TRPs 119a, 119b may be any type of device configured to wirelessly interface with at least one of the WTRU 102d, to facilitate access to one or more communication networks, such as the core network 106 / 107 / 109, the Internet 110, Network Services 113, and / or other networks 112. RSUs 120a and 120b may be any type of device configured to wirelessly interface w ith at least one of the WTRU 102e or 102f, to facilitate access to one or more communication networks, such as the core network 106 / 107 / 109, the Internet 110, other networks 112, and / or Netw ork Services 113. By w ay of example, the baseCNV15060W001 / 101859.002202 stations 114a, 114b may be a Base Transceiver Station (BTS), a Node-B, an eNode B, a Home Node B, a Home eNode B, a Next Generation Node-B (gNode B), a satellite, a site controller, an access point (AP), a wireless router, and the like.

[0153] The base station 114a may be part of the RAN 103 / 104 / 105, which may also comprise other base stations and / or network elements (not shown), such as a Base Station Controller (BSC), a Radio Network Controller (RNC), relay nodes, etc. Similarly, the base station 114b may be part of the RAN 103b / 104b / 105b, which may also comprise other base stations and / or network elements (not shown), such as a BSC, a RNC, relay nodes, etc. The base station 114a may be configured to transmit and / or receive wireless signals within a particular geographic region, which may be referred to as a cell (not shown). Similarly, the base station 114b may be configured to transmit and / or receive wired and / or wireless signals within a particular geographic region, which may be referred to as a cell (not shown). The cell may further be divided into cell sectors. For example, the cell associated with the base station 114a may be divided into three sectors. Thus, for example, the base station 114a may comprise three transceivers, e.g., one for each sector of the cell. The base station 114a may employ Multiple-Input Multiple Output (MIMO) technology and, therefore, may utilize multiple transceivers for each sector of the cell, for instance.

[0154] The base station 114a may communicate with one or more of the WTRUs 102a, 102b, 102c, and 102g over an air interface 115 / 116 / 117, which may be any suitable wireless communication link (e.g., Radio Frequency (RF), microwave, infrared (IR), ultraviolet (UV), visible light. cmWave. mmWave, etc.). The air interface 115 / 116 / 117 may be established using any suitable Radio Access Technology (RAT).

[0155] The base station 114b may communicate with one or more of the RRHs 118a and 118b, TRPs 119a and 119b, and / or RSUs 120a and 120b, over a wired or air interface 115b / l 16b / l 17b. which may be any suitable wired (e.g., cable, optical fiber, etc.) or wireless communication link (e.g., RF, microwave, IR, UV, visible light, cmWave, mmWave, etc.). The air interface 115b / l 16b / l 17b may be established using any suitable RAT.

[0156] The RRHs 118a, 118b, TRPs 119a, 119b and / or RSUs 120a, 120b, may communicate with one or more of the WTRUs 102c, 102d, 102e, 102f over an air interface 115c / l 16c / l 17c, which may be any suitable wireless communication link (e.g., RF, microwave, IR, ultraviolet UV, visible light, cmWave, mmWave, etc.) The air interface 115c / l 16c / l 17c may be established using any suitable RAT.CNV15060W001 / 101859.002202

[0157] The WTRUs 102 may communicate with one another over a direct air interface 115d / l 16d / l 17d, such as Sidelink communication which may be any suitable wireless communication link (e.g., RF. microwave. IR, ultraviolet UV, visible light. cmWave, mmWave, etc.) The air interface 1 15d / l 16d / l 17d may be established using any suitable RAT.

[0158] The communications system 100 may be a multiple access system and may employ one or more channel access schemes, such as CDMA, TDMA, FDMA, OFDMA, SC- FDMA, and the like. For example, the base station 114a in the RAN 103 / 104 / 105 and the WTRUs 102a, 102b. 102c. or RRHs 118a. 118b,TRPs 1 19a, 119b and / or RSUs 120a and 120b in the RAN 103b / 104b / 105b and the WTRUs 102c, 102d, 102e, and 102f, may implement a radio technology such as Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access (UTRA), which may establish the air interface 115 / 116 / 117 and / or 115c / l 16c / l 17c respectively using Wideband CDMA (WCDMA). WCDMA may comprise communication protocols such as High-Speed Packet Access (HSPA) and / or Evolved HSPA (HSPA+). HSPA may comprise High-Speed Downlink Packet Access (HSDPA) and / or High- Speed Uplink Packet Access (HSUPA).

[0159] The base station 114a in the RAN 103 / 104 / 105 and the WTRUs 102a, 102b, 102c, and 102g, or RRHs 118a and 118b, TRPs 119a and 119b, and / or RSUs 120a and 120b in the RAN 103b / 104b / 105b and the WTRUs 102c, 102d, may implement a radio technology such as Evolved UMTS Terrestrial Radio Access (E-UTRA), which may establish the air interface 115 / 116 / 117 or 115c / l 16c / l 17c respectively using Long Term Evolution (LTE) and / or LTE- Advanced (LTE- A), for example. The air interface 115 / 116 / 117 or 115c / l 16c / 117c may implement 3GPP NR technology. The LTE and LTE-A technology may comprise LTE D2D and / or V2X technologies and interfaces (such as Sidelink communications, etc.) Similarly, the 3GPP NR technology' may comprise NR V2X technologies and interfaces (such as Sidelink communications, etc.)

[0160] The base station 114a in the RAN 103 / 104 / 105 and the WTRUs 102a, 102b, 102c, and 102g or RRHs 118a and 118b, TRPs 119a and 119b, and / or RSUs 120a and 120b in the RAN 103b / 104b / 105b and the WTRUs 102c, 102d, 102e, and 102f may implement radio technologies such as IEEE 802.16 (e g., Worldwide Interoperability’ for Microwave Access (WiMAX)), CDMA2000, CDMA2000 IX, CDMA2000 EV-DO, Interim Standard 2000 (IS- 2000), Interim Standard 95 (IS-95), Interim Standard 856 (IS-856), Global System for MobileCNV15060W001 / 101859.002202 communications (GSM), Enhanced Data rates for GSM Evolution (EDGE), GSM EDGE (GERAN), and the like.

[0161] The base station 114c in FIG. 15A may be a wireless router, Home Node B, Home eNode B, or access point, for example, and may utilize any suitable RAT for facilitating wireless connectivity in a localized area, such as a place of business, a home, a vehicle, a train, an aerial, a satellite, a manufactory, a campus, and the like. The base station 114c and the WTRUs 102, e.g., WTRU 102e, may implement a radio technology such as IEEE 802.11 to establish a Wireless Local Area Network (WLAN). Similarly, the base station 114c and the WTRUs 102, e.g., WTRU 102d, may implement a radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN). The base station 114c and the WTRUs 102, e.g., WRTU 102e, may utilize a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE. LTE-A, NR, etc.) to establish a picocell or femtocell. As shown in FIG. 15A. the base station 114c may have a direct connection to the Internet 110. Thus, the base station 114c may not be required to access the Internet 110 via the core network 106 / 107 / 109.

[0162] The RAN 103 / 104 / 105 and / or RAN 103b / 104b / 105b may be in communication with the core network 106 / 107 / 109, which may be any type of network configured to provide voice, data, messaging, authorization and authentication, applications, and / or Voice Over Internet Protocol (VoIP) services to one or more of the WTRUs 102. For example, the core network 106 / 107 / 109 may provide call control, billing sendees, mobile location-based services, pre-paid calling, Internet connectivity, packet data network connectivity. Ethernet connectivity, video distribution, etc., and / or perform high-level security functions, such as user authentication.

[0163] Although not shown in FIG. 15 A, it may be appreciated that the RAN 103 / 104 / 105 and / or RAN 103b / 104b / 105b and / or the core network 106 / 107 / 109 may be in direct or indirect communication with other RANs that employ the same RAT as the RAN 103 / 104 / 105 and / or RAN 103b / l 04b / 105b or a different RAT. For example, in addition to being connected to the RAN 103 / 104 / 105 and / or RAN 103b / 104b / l 05b, which may be utilizing an E-UTRA radio technology, the core network 106 / 107 / 109 may also be in communication with another RAN (not shown) employing a GSM or NR radio technology.

[0164] The core network 106 / 107 / 109 may also serve as a gatew ay for the WTRUs 102 to access the PSTN 108, the Internet 110, and / or other networks 112. The PSTN 108 may comprise circuit-switched telephone networks that provide Plain Old Telephone ServiceCNV15060W001 / 101859.002202(POTS). The Internet 110 may comprise a global system of interconnected computer networks and devices that use common communication protocols, such as the Transmission Control Protocol (TCP), User Datagram Protocol (UDP), and the internet protocol (IP) in the TCP / IP internet protocol suite. The other networks 112 may comprise wired or wireless communications networks owned and / or operated by other service providers. For example, the networks 112 may comprise any type of packet data network (e.g., an IEEE 802.3 Ethernet network) or another core network connected to one or more RANs, which may employ the same RAT as the RAN 103 / 104 / 105 and / or RAN 103b / 104b / 105b or a different RAT.

[0165] Some or all of the WTRUs 102a, 102b, 102c, 102d, 102e, and 102f in the communications system 100 may comprise multi-mode capabilities, e.g., the WTRUs 102a, 102b, 102c, 102d, 102e, and 102f may comprise multiple transceivers for communicating with different wireless networks over different wireless links. For example, the WTRU 102g shown in FIG. 15A may be configured to communicate with the base station 114a, which may employ a cellular-based radio technology, and with the base station 114c, which may employ an IEEE 802 radio technology.

[0166] Although not shown in FIG. 15 A, it may be appreciated that a User Equipment may make a wired connection to a gateway. The gateway maybe a Residential Gateway (RG). The RG may provide connectivity to a Core Network 106 / 107 / 109. It may be appreciated that many of the ideas contained herein may equally apply to UEs that are WTRUs and UEs that use a wired connection to connect to a network. For example, the ideas that apply to the wireless interfaces 115, 116. 117 and 115c / l 16c / l 17c may equally apply to a wired connection.

[0167] FIG. 15B is a system diagram of an example RAN 103 and core network 106. As noted above, the RAN 103 may employ a UTRA radio technology to communicate with the WTRUs 102a, 102b, and 102c over the air interface 115. The RAN 103 may also be in communication w ith the core network 106. As shown in FIG. 15B, the RAN 103 may comprise Node-Bs 140a, 140b, and 140c, which may each comprise one or more transceivers for communicating with the WTRUs 102a, 102b, and 102c over the air interface 115. The Node-Bs 140a, 140b. and 140c may each be associated with a particular cell (not shown) within the RAN 103. The RAN 103 may also comprise RNCs 142a, 142b. It may be appreciated that the RAN 103 may comprise any number of Node-Bs and Radio Network Controllers (RNCs.)CNV15060W001 / 101859.002202

[0168] As shown in FIG. 15B, the Node-Bs 140a, 140b may be in communication with the RNC 142a. Additionally, the Node-B 140c may be in communication with the RNC 142b. The Node-Bs 140a, 140b. and 140c may communicate with the respective RNCs 142a and 142b via an lub interface. The RNCs 142a and 142b may be in communication with one another via an lur interface. Each of the RNCs 142aand 142b may be configured to control the respective Node-Bs 140a, 140b, and 140c to which it is connected. In addition, each of the RNCs 142aand 142b may be configured to carry out or support other functionality, such as outer loop power control, load control, admission control, packet scheduling, handover control, macro-diversity, security functions, data encryption, and the like.

[0169] The core network 106 shown in FIG. 15B may comprise a media gateway (MGW) 144, a Mobile Switching Center (MSC) 146, a Serving GPRS Support Node (SGSN) 148, and / or a Gateway GPRS Support Node (GGSN) 150. While each of the foregoing elements are depicted as part of the core network 106, it may be appreciated that any one of these elements may be owned and / or operated by an entity other than the core netw ork operator.

[0170] The RNC 142a in the RAN 103 may be connected to the MSC 146 in the core network 106 via an luCS interface. The MSC 146 may be connected to the MGW 144. The MSC 146 and the MGW 144 may provide the WTRUs 102a, 102b, and 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, and 102c, and traditional land-line communications devices.

[0171] The RNC 142a in the RAN 103 may also be connected to the SGSN 148 in the core network 106 via an luPS interface. The SGSN 148 may be connected to the GGSN 150. The SGSN 148 and the GGSN 150 may provide the WTRUs 102a, 102b, and 102c with access to packet-switched networks, such as the Internet 110, to facilitate communications between and the WTRUs 102a, 102b, and 102c, and IP-enabled devices.

[0172] The core network 106 may also be connected to the other networks 112, which may comprise other wired or wireless networks that are ow ned and / or operated by other service providers.

[0173] FIG. 15C is a system diagram of an example RAN 104 and core network 107. As noted above, the RAN 104 may employ an E-UTRA radio technology to communicate with the WTRUs 102a, 102b, and 102c over the air interface 116. The RAN 104 may also be in communication with the core network 107.CNV15060W001 / 101859.002202

[0174] The RAN 104 may comprise eNode-Bs 160a, 160b, and 160c, though it may be appreciated that the RAN 104 may comprise any number of eNode-Bs. The eNode-Bs 160a, 160b, and 160c may each comprise one or more transceivers for communicating with the WTRUs 102a, 102b, and 102c over the air interface 116. For example, the eNode-Bs 160a, 160b, and 160c may implement MIMO technology. Thus, the eNode-B 160a, for example, may use multiple antennas to transmit wireless signals to, and receive wireless signals from, the WTRU 102a.

[0175] Each of the eNode-Bs 160a, 160b, and 160c may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the uplink and / or downlink, and the like. As shown in FIG. 15C, the eNode-Bs 160a, 160b, and 160c may communicate with one another over an X2 interface.

[0176] The core network 107 shown in FIG. 15C may comprise a Mobility Management Gateway (MME) 162, a serving gateway 164, and a Packet Data Network (PDN) gateway 166. While each of the foregoing elements are depicted as part of the core network 107, it may be appreciated that any one of these elements may be owned and / or operated by an entity other than the core network operator.

[0177] The MME 162 may be connected to each of the eNode-Bs 160a, 160b, and 160c in the RAN 104 via an SI interface and may sen e as a control node. For example, the MME 162 may be responsible for authenticating users of the WTRUs 102a, 102b, and 102c, bearer activation / deactivation. selecting a particular serving gateway during an initial attach of the WTRUs 102a, 102b, and 102c, and the like. The MME 162 may also provide a control plane function for switching between the RAN 104 and other RANs (not shown) that employ other radio technologies, such as GSM or WCDMA.

[0178] The serving gateway 164 may be connected to each of the eNode-Bs 160a, 160b, and 160c in the RAN 104 via the SI interface. The serving gateway 164 may generally route and forward user data packets to / from the WTRUs 102a, 102b, and 102c. The serving gateway 164 may also perform other functions, such as anchoring user planes during inter- eNode B handovers, triggering paging when downlink data is available for the WTRUs 102a, 102b, and 102c, managing and storing contexts of the WTRUs 102a, 102b, and 102c, and the like.CNV15060W001 / 101859.002202

[0179] The serving gateway 164 may also be connected to the PDN gateway 166, which may provide the WTRUs 102a, 102b, and 102c with access to packet-switched networks, such as the Internet 110. to facilitate communications between the WTRUs 102a, 102b, 102c, and IP-enabled devices.

[0180] The core network 107 may facilitate communications with other networks. For example, the core network 107 may provide the WTRUs 102a, 102b, and 102c with access to circuit-switched networks, such as the PSTN 108, to facilitate communications between the WTRUs 102a, 102b, and 102c and traditional land-line communications devices. For example, the core network 107 may comprise, or may communicate with, an IP gateway (e g., an IP Multimedia Subsystem (IMS) server) that serves as an interface between the core network 107 and the PSTN 108. In addition, the core network 107 may prov ide the WTRUs 102a, 102b, and 102c with access to the networks 112. which may comprise other wired or wireless networks that are owned and / or operated by other service providers.

[0181] FIG. 15D is a system diagram of an example RAN 105 and core network 109. The RAN 105 may employ an NR radio technology to communicate with the WTRUs 102a and 102b over the air interface 117. The RAN 105 may also be in communication with the core network 109. A Non-3GPP Interworking Function (N3IWF) 199 may employ a non- 3GPP radio technology to communicate with the WTRU 102c over the air interface 198. The N3IWF 199 may also be in communication with the core network 109.

[0182] The RAN 105 may comprise gNode-Bs 180a and 180b. It may be appreciated that the RAN 105 may comprise any number of gNode-Bs. The gNode-Bs 180a and 180b may each comprise one or more transceivers for communicating with the WTRUs 102a and 102b over the air interface 117. When integrated access and backhaul connection are used, the same air interface may be used between the WTRUs and gNode-Bs, which may be the core network 109 via one or multiple gNBs. The gNode-Bs 180a and 180b may implement MIMO, MU- MIMO, and / or digital beamforming technology. Thus, the gNode-B 180a, for example, may use multiple antennas to transmit wireless signals to, and receive wireless signals from, the WTRU 102a. It should be appreciated that the RAN 105 may employ of other types of base stations such as an eNode-B. It may also be appreciated the RAN 105 may employ more than one type of base station. For example, the RAN may employ eNode-Bs and gNode-Bs.

[0183] The N3IWF 199 may comprise a non-3GPP Access Point 180c. It may be appreciated that the N3IWF 199 may comprise any number of non-3GPP Access Points. TheCNV15060W001 / 101859.002202 non-3GPP Access Point 180c may comprise one or more transceivers for communicating with the WTRUs 102c over the air interface 198. The non-3GPP Access Point 180c may use the 802. 11 protocol to communicate with the WTRU 102c over the air interface 198.

[0184] Each of the gNode-Bs 180a and 180b may be associated with a particular cell (not shown) and may be configured to handle radio resource management decisions, handover decisions, scheduling of users in the uplink and / or downlink, and the like. As shown in FIG. 15D. the gNode-Bs 180a and 180b may communicate with one another over an Xn interface, for example.

[0185] The core network 109 shown in FIG. 15D may be a 5G core network (5GC). The core network 109 may offer numerous communication services to customers who are interconnected by the radio access network. The core network 109 comprises a number of entities that perform the functionality’ of the core network. As used herein, the term “core network entity7” or “network function” refers to any entity7that performs one or more functionalities of a core netw ork. It is understood that such core network entities may be logical entities that are implemented in the form of computer-executable instructions (softw are) stored in a memory of, and executing on a processor of, an apparatus configured for wireless and / or network communications or a computer system, such as system 90 illustrated in FIG. 15G.

[0186] In the example of FIG. 15D, the 5G Core Network 109 may7comprise an access and mobility7management function (AMF) 172, a Session Management Function (SMF) 174, User Plane Functions (UPFs) 176a and 176b, a User Data Management Function (UDM) 197, an Authentication Server Function (AUSF) 190, a Network Exposure Function (NEF) 196, a Policy Control Function (PCF) 184, a Non-3GPP Interworking Function (N3IWF) 199, a User Data Repository7(UDR) 178. While each of the foregoing elements are depicted as part of the 5G core network 109, it may be appreciated that any one of these elements may be owned and / or operated by an entity other than the core network operator. It may also be appreciated that a 5G core network may not consist of all of these elements, may consist of additional elements, and may consist of multiple instances of each of these elements. FIG. 15D shows that network functions directly connect to one another, how ever, it should be appreciated that they may communicate via routing agents such as a diameter routing agent or message buses.

[0187] In the example of FIG. 15D, connectivity between network functions is achieved via a set of interfaces, or reference points. It may be appreciated that network functions may be modeled, described, or implemented as a set of services that are invoked, orCNV15060W001 / 101859.002202 called, by other network functions or sendees. Invocation of a Network Function service may be achieved via a direct connection between network functions, an exchange of messaging on a message bus. calling a software function, etc.

[0188] The AMF 172 may be connected to the RAN 105 via an N2 interface and may serve as a control node. For example, the AMF 172 may be responsible for registration management, connection management, reachability7management, access authentication, access authorization. The AMF may be responsible forwarding user plane tunnel configuration information to the RAN 105 via the N2 interface. The AMF 172 may receive the user plane tunnel configuration information from the SMF via an Ni l interface. The AMF 172 may generally route and forward NAS packets to / from the WTRUs 102a, 102b, and 102c via an N1 interface. The N1 interface is not shown in FIG. 15D.

[0189] The SMF 174 may be connected to the AMF 172 via an Ni l interface. Similarly, the SMF may be connected to the PCF 184 via an N7 interface, and to the UPFs 176a and 176b via an N4 interface. The SMF 174 may serve as a control node. For example, the SMF 174 may be responsible for Session Management, IP address allocation for the WTRUs 102a, 102b. and 102c, management and configuration of traffic steering rules in the UPF 176a and UPF 176b, and generation of downlink data notifications to the AMF 172.

[0190] The UPF 176a and UPF 176b may provide the WTRUs 102a, 102b, and 102c with access to a Packet Data Network (PDN), such as the Internet 110, to facilitate communications between the WTRUs 102a. 102b, and 102c and other devices. The UPF 176a and UPF 176b may also provide the WTRUs 102a, 102b. and 102c with access to other types of packet data networks. For example, Other Networks 112 may be Ethernet Networks or any ty pe of network that exchanges packets of data. The UPF 176a and UPF 176b may receive traffic steering rules from the SMF 174 via the N4 interface. The UPF 176a and UPF 176b may provide access to a packet data network by connecting a packet data network with an N6 interface or by connecting to each other and to other UPFs via an N9 interface. In addition to providing access to packet data networks, the UPF 176 may be responsible packet routing and forwarding, policy rule enforcement, quality7of sen ice handling for user plane traffic, downlink packet buffering.

[0191] The AMF 172 may also be connected to the N3IWF 199, for example, via an N2 interface. The N3IWF facilitates a connection between the WTRU 102c and the 5G core network 170, for example, via radio interface technologies that are not defined by 3GPP. TheCNV15060W001 / 101859.002202AMF may interact with the N3IWF 199 in the same, or similar, manner that it interacts with the RAN 105.

[0192] The PCF 184 may be connected to the SMF 174 via an N7 interface, connected to the AMF 172 via an N15 interface, and to an Application Function (AF) 188 via an N5 interface. The N15 and N5 interfaces are not shown in FIG. 15D. The PCF 184 may provide policy rules to control plane nodes such as the AMF 172 and SMF 174, allowing the control plane nodes to enforce these rules. The PCF 184 may send policies to the AMF 172 for the WTRUs 102a, 102b, and 102c so that the AMF may deliver the policies to the WTRUs 102a, 102b, and 102c via an N1 interface. Policies may then be enforced, or applied, at the WTRUs 102a, 102b, and 102c.

[0193] The UDR 178 may act as a repository' for authentication credentials and subscription information. The UDR may connect to network functions, so that network function may add to, read from, and modify the data that is in the repository. For example, the UDR 178 may connect to the PCF 184 via an N36 interface. Similarly, the UDR 178 may connect to the NEF 196 via an N37 interface, and the UDR 178 may connect to the UDM 197 via an N35 interface.

[0194] The UDM 197 may serve as an interface between the UDR 178 and other network functions. The UDM 197 may authorize network functions to access of the UDR 178. For example, the UDM 197 may connect to the AMF 172 via an N8 interface, the UDM 197 may connect to the SMF 174 via an N10 interface. Similarly, the UDM 197 may connect to the AUSF 190 via an N13 interface. The UDR 178 and UDM 197 may be tightly integrated.

[0195] The AUSF 190 performs authentication related operations and connects to the UDM 178 via an N13 interface and to the AMF 172 via an N12 interface.

[0196] The NEF 196 exposes capabilities and services in the 5G core network 109 to Application Functions (AF) 188. Exposure may occur on the N33 API interface. The NEF may connect to an AF 188 via an N33 interface, and it may connect to other network functions in order to expose the capabilities and sendees of the 5G core network 109.

[0197] Application Functions 188 may interact with network functions in the 5G Core Network 109. Interaction between the Application Functions 188 and network functions may be via a direct interface or may occur via the NEF 196. The Application Functions 188 may be considered part of the 5G Core Network 109 or may be external to the 5G Core NetworkCNV15060W001 / 101859.002202109 and deployed by enterprises that have a business relationship with the mobile network operator.

[0198] Network Slicing is a mechanism that may be used by mobile network operators to support one or more ’virtual’ core networks behind the operator’s air interface. This involves ‘slicing’ the core network into one or more virtual networks to support different RANs or different senice types running across a single RAN. Network slicing enables the operator to create networks customized to provide optimized solutions for different market scenarios which demands diverse requirements, e.g., in the areas of functionality, performance and isolation.

[0199] 3GPP has designed the 5G core network to support Network Slicing. Network Slicing is a good tool that network operators may use to support the diverse set of 5G use cases (e.g.. massive loT. critical communications. V2X, and enhanced mobile broadband) which demand very diverse and sometimes extreme requirements. Without the use of network slicing techniques, it is likely that the network architecture would not be flexible and scalable enough to efficiently support a wider range of use cases need when each use case has its own specific set of performance, scalability, and availability requirements. Furthermore, introduction of new network services should be made more efficient.

[0200] Referring again to FIG. 15D, in a network slicing scenario, a WTRU 102a, 102b, or 102c may connect to an AMF 172, via an N1 interface. The AMF may be logically part of one or more slices. The AMF may coordinate the connection or communication of WTRU 102a, 102b, or 102c with one or more UPF 176a and 176b. SMF 174, and other network functions. Each of the UPFs 176a and 176b, SMF 174, and other network functions may be part of the same slice or different slices. When they are part of different slices, they may be isolated from each other in the sense that they may utilize different computing resources, security credentials, etc.

[0201] The core network 109 may facilitate communications with other networks. For example, the core network 109 may comprise, or may communicate with, an IP gateway, such as an IP Multimedia Subsystem (IMS) server, that serves as an interface between the 5G core network 109 and a PSTN 108. For example, the core network 109 may comprise, or communicate with a short message service (SMS) service center that facilities communication via the short message service. For example, the 5G core network 109 may facilitate the exchange of non-IP data packets between the WTRUs 102a, 102b, and 102c and servers orCNV15060W001 / 101859.002202 applications functions 188. In addition, the core network 170 may provide the WTRUs 102a, 102b, and 102c with access to the networks 112, which may comprise other wired or wireless networks that are owned and / or operated by other service providers.

[0202] The core network entities described herein and illustrated in FIGs. 15 A, 15C, 15D, and 15E are identified by the names given to those entities in certain existing 3GPP specifications, but it is understood that in the future those entities and functionalities may be identified by other names and certain entities or functions may be combined in future specifications published by 3GPP. including future 3GPP NR specifications. Thus, the particular netw ork entities and functionalities described and illustrated in FIGs. 15 A, 15B, 15C, 15D, and 15E are provided by way of example only, and it is understood that the subject matter disclosed and claimed herein may be embodied or implemented in any similar communication system, whether presently defined or defined in the future.

[0203] FIG. 15E illustrates an example communications system 111 in which the systems, methods, apparatuses described herein may be used. Communications system 111 may comprise Wireless Transmit / Receive Units (WTRUs) A, B, C, D, E, F, abase station gNB 121, a V2X server 124, and Road Side Units (RSUs) 123a and 123b. In practice, the concepts presented herein may be applied to any number of WTRUs, base station gNBs, V2X netw orks, and / or other network elements. One or several or all WTRUs A, B, C, D, E, and F may be out of range of the access netw ork coverage 131. WTRUs A, B, and C form a V2X group, among which WTRU A is the group lead and WTRUs B and C are group members.

[0204] WTRUs A, B. C, D, E, and F may communicate with each other over a Uu interface 129 via the gNB 121 if they are w ithin the access network coverage 131. In the example of FIG. 15E, WTRUs B and F are shown within access network coverage 131. WTRUs A, B, C, D, E, and F may communicate with each other directly via a Sidelink interface (e.g., PC5 or NR PC5) such as interface 125a. 125b, or 128. whether they are under the access network coverage 131 or out of the access network coverage 131. For instance, in the example of FIG. 15E, WRTU D, which is outside of the access network coverage 131, communicates with WTRU F, which is inside the coverage 131.

[0205] WTRUs A, B, C, D, E, and F may communicate with RSU 123a or 123b via a Vehicle-to-Network (V2N) 133 or Sidelink interface 125b. WTRUs A, B, C, D, E, and F may communicate to a V2X Server 124 via a Vehicle-to-Infrastructure (V2I) interface 127. WTRUsCNV15060W001 / 101859.002202A, B, C, D, E, and F may communicate to another UE via a Vehicle-to-Person (V2P) interface 128.

[0206] FIG. 15F is a block diagram of an example apparatus or device WTRU 102 that may be configured for wireless communications and operations in accordance with the systems, methods, and apparatuses described herein, such as a WTRU 102 of FIG. 15A, 15B, 15C, 15D, or 15E. As show n in FIG. 15F, the example WTRU 102 may comprise a processor 118, a transceiver 120, a transmit / receive element 122, a speaker / microphone 124, a keypad 126, a display / touchpad / indicators 128, non-removable memory 130, removable memory 132, a power source 134, a global positioning system (GPS) chipset 136, and other peripherals 138. It may be appreciated that the WTRU 102 may comprise any sub-combination of the foregoing elements. Also, the base stations 114a and 114b, and / or the nodes that base stations 114a and 114b may represent, such as but not limited to transceiver station (BTS), a Node-B, a site controller, an access point (AP), a home node-B, an evolved home node-B (eNodeB), a home evolved node-B (HeNB), a home evolved node-B gateway, a next generation node-B (gNode- B), and proxy nodes, among others, may comprise some or all of the elements depicted in FIG. 15F and described herein.

[0207] The processor 1 18 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Array (FPGAs) circuits, any other type of integrated circuit (IC), a state machine, and the like. The processor 118 may perform signal coding, data processing, power control, input / output processing, and / or any other functionality that enables the WTRU 102 to operate in a wireless environment. The processor 118 may be coupled to the transceiver 120, which may be coupled to the transmit / receive element 122. While FIG. 15F depicts the processor 118 and the transceiver 120 as separate components, it may be appreciated that the processor 118 and the transceiver 120 may be integrated together in an electronic package or chip.

[0208] The transmit / receive element 122 of a UE may be configured to transmit signals to, or receive signals from, a base station (e.g.. the base station 114a of FIG. 15 A) over the air interface 115 / 116 / 117 or another UE over the air interface 115d / l 16d / l 17d. For example, the transmit / receive element 122 may be an antenna configured to transmit and / or receive RF signals. The transmit / receive element 122 may be an emitter / detector configured toCNV15060W001 / 101859.002202 transmit and / or receive IR, UV, or visible light signals, for example. The transmit / receive element 122 may be configured to transmit and receive both RF and light signals. It may be appreciated that the transmit / receive element 122 may be configured to transmit and / or receive any combination of wireless or wired signals.

[0209] In addition, although the transmit / receive element 122 is depicted in FIG. 15F as a single element, the WTRU 102 may comprise any number of transmit / receive elements 122. More specifically, the WTRU 102 may employ MIMO technology. Thus, the WTRU 102 may comprise two or more transmit / receive elements 122 (e.g., multiple antennas) for transmitting and receiving wireless signals over the air interface 115 / 116 / 117.

[0210] The transceiver 120 may be configured to modulate the signals that are to be transmitted by the transmit / receive element 122 and to demodulate the signals that are received by the transmit / receive element 122. As noted above, the WTRU 102 may have multi-mode capabilities. Thus, the transceiver 120 may comprise multiple transceivers for enabling the WTRU 102 to communicate via multiple RATs, for example NR and IEEE 802. 11 or NR and E-UTRA, or to communicate with the same RAT via multiple beams to different RRHs, TRPs, RSUs, or nodes.

[0211] The processor 1 18 of the WTRU 102 may be coupled to, and may receive user input data from, the speaker / microphone 124, the keypad 126, and / or the display / touchpad / indicators 128 (e.g., a liquid crystal display (LCD) display unit or organic light-emitting diode (OLED) display unit. The processor 118 may also output user data to the speaker / microphone 124, the keypad 126. and / or the display / touchpad / indicators 128. In addition, the processor 118 may access information from, and store data in, any type of suitable memory. such as the non-removable memory 130 and / or the removable memory 132. The nonremovable memory' 130 may comprise random-access memory (RAM), read-only memory (ROM), a hard disk, or any other type of memory storage device. The removable memory 132 may comprise a subscriber identity module (SIM) card, a memory stick, a secure digital (SD) memory card, and the like. The processor 118 may access information from, and store data in, memory7that is not physically located on the WTRU 102, such as on a sen' er that is hosted in the cloud or in an edge computing platform or in a home computer (not shown).

[0212] The processor 118 may receive power from the power source 134 and may be configured to distribute and / or control the power to the other components in the WTRU 102. The power source 134 may be any suitable device for powering the WTRU 102. For example,CNV15060W001 / 101859.002202 the power source 134 may comprise one or more dry7cell batteries, solar cells, fuel cells, and the like.

[0213] The processor 118 may also be coupled to the GPS chipset 136, which may be configured to provide location information (e.g., longitude and latitude) regarding the current location of the WTRU 102. In addition to, or in lieu of, the information from the GPS chipset 136, the WTRU 102 may receive location information over the air interface 115 / 116 / 117 from a base station (e.g., base stations 114a, 114b) and / or determine its location based on the timing of the signals being received from two or more nearby base stations. It may be appreciated that the WTRU 102 may acquire location information by way of any suitable location-determination method.

[0214] The processor 118 may further be coupled to other peripherals 138, which may comprise one or more software and / or hardware modules that provide additional features, functionality, and / or wired or wireless connectivity. For example, the peripherals 138 may comprise various sensors such as an accelerometer, biometrics (e.g., finger print) sensors, an e-compass, a satellite transceiver, a digital camera (for photographs or video), a universal serial bus (USB) port or other interconnect interfaces, a vibration device, a television transceiver, a hands free headset, a Bluetooth® module, a frequency modulated (FM) radio unit, a digital music player, a media player, a video game player module, an Internet browser, and the like.

[0215] The WTRU 102 may be comprised in other apparatuses or devices, such as a sensor, consumer electronics, a wearable device such as a smart watch or smart clothing, a medical or eHealth device, a robot, industrial equipment, a drone, a vehicle such as a car, truck, train, or an airplane. The WTRU 102 may connect to other components, modules, or systems of such apparatuses or devices via one or more interconnect interfaces, such as an interconnect interface that may comprise one of the peripherals 138.

[0216] FIG. 15G is a block diagram of an exemplary computing system 90 in which one or more apparatuses of the communications networks illustrated in FIGs. 15 A, 15C, 15D and 15E may be embodied, such as certain nodes or functional entities in the RAN 103 / 104 / 105, Core Network 106 / 107 / 109, PSTN 108, Internet 110, Other Networks 112, or Network Services 113. Computing system 90 may comprise a computer or server and may be controlled primarily by computer readable instructions, which may be in the form of software, wherever, or by whatever means such software is stored or accessed. Such computer readable instructions may be executed within a processor 91, to cause computing system 90 to do work.CNV15060W001 / 101859.002202The processor 91 may be a general purpose processor, a special purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASICs), Field Programmable Gate Array (FPGAs) circuits, any other type of integrated circuit (IC), a state machine, and the like. The processor 91 may perform signal coding, data processing, power control, input / output processing, and / or any other functionality that enables the computing system 90 to operate in a communications network. Coprocessor 81 is an optional processor, distinct from main processor 91, that may perform additional functions or assist processor 91. Processor 91 and / or coprocessor 81 may receive, generate, and process data related to the methods and apparatuses disclosed herein.

[0217] In operation, processor 91 fetches, decodes, and executes instructions, and transfers information to and from other resources via the computing system’s main data- transfer path, system bus 80. Such a system bus connects the components in computing system 90 and defines the medium for data exchange. System bus 80 typically comprises data lines for sending data, address lines for sending addresses, and control lines for sending interrupts and for operating the system bus. An example of such a system bus 80 is the PCI (Peripheral Component Interconnect) bus.

[0218] Memories coupled to system bus 80 comprise random access memory (RAM) 82 and read only memory (ROM) 93. Such memories comprise circuitry that allows information to be stored and retrieved. ROMs 93 generally contain stored data that may not easily be modified. Data stored in RAM 82 may be read or changed by processor 91 or other hardware devices. Access to RAM 82 and / or ROM 93 may be controlled by memory controller 92. Memory' controller 92 may provide an address translation function that translates virtual addresses into physical addresses as instructions are executed. Memory controller 92 may also provide a memory protection function that isolates processes within the system and isolates system processes from user processes. Thus, a program running in a first mode may access only memory mapped by its own process virtual address space; it may not access memory within another process’s virtual address space unless memory7sharing between the processes has been set up.

[0219] In addition, computing system 90 may contain peripherals controller 83 responsible for communicating instructions from processor 91 to peripherals, such as printer 94, keyboard 84, mouse 95, and disk drive 85.CNV15060W001 / 101859.002202

[0220] Display 86, which is controlled by display controller 96, is used to display visual output generated by computing system 90. Such visual output may comprise text, graphics, animated graphics, and video. The visual output may be provided in the form of a graphical user interface (GUI). Display 86 may be implemented with a CRT-based video display, an LCD-based flat-panel display, gas plasma-based flat-panel display, or a touchpanel. Display controller 96 comprises electronic components required to generate a video signal that is sent to display 86.

[0221] Further, computing system 90 may contain communication circuitry, such as for example a wireless or wired network adapter 97, that may be used to connect computing system 90 to an external communications network or devices, such as the RAN 103 / 104 / 105, Core Network 106 / 107 / 109, PSTN 108, Internet 110, WTRUs 102. or Other Networks 112 of FIGs. 15A. 15B, 15C, 15D, and 15E, to enable the computing system 90 to communicate with other nodes or functional entities of those networks. The communication circuitry, alone or in combination with the processor 91 , may be used to perform the transmitting and receiving steps of certain apparatuses, nodes, or functional entities described herein.

[0222] It is understood that any or all of the apparatuses, systems, methods and processes described herein may be embodied in the form of computer executable instructions (e.g., program code) stored on a computer-readable storage medium which instructions, when executed by one or more processors, such as processors 118 or 91, cause the one or more processors to perform and / or implement the systems, methods and processes described herein. Specifically, any of the steps, operations, or functions described herein may be implemented in the form of such computer executable instructions, executing on the processor(s) of an apparatus or computing system configured for wireless and / or wired network communications. Computer readable storage media comprises volatile and nonvolatile, removable and nonremovable media implemented in any non-transitory (e.g., tangible or physical) method or technology for storage of information, but such computer readable storage media do not comprise signals. Computer readable storage media comprise, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other tangible or physical medium which may be used to store the desired information and which may be accessed by a computing system.

Claims

CNV15060W001 / 101859.002202What is claimed:

1. An apparatus, comprising one or more processors, and memory storing instructions which, when executed by the one or more processors, cause the apparatus to: receive, from a user equipment (UE), a request comprising energy' profile information; store the energy profile information; receive, from the UE, an energy aware discovery request comprising one or more discovery' criteria; determine, based on the discovery' request and the energy profile information, one or more servers that meet the one or more discovery criteria; and send, to the UE, information indicative of the one or more servers that meet the one or more discovery criteria.

2. The apparatus of claim 1, wherein the energy' profile information indicates one or more of: a supported energy mix, one or more supported energy sources, one or more supported energy providers, one or more supported energy rates, one or more key performance indicators (KPIs), or one or more supported energy credits.

3. The apparatus of claim 1, wherein the supported energy' mix indicates, for an energy profile associated with the energy profile information, a renewable and non-renewable energy usage mix.

4. The apparatus of claim 1, wherein the one or more supported energy sources indicate, for an energy profile associated with the energy profile information, one or more types of renewable or non-renewable energy usable for the energy’ profile.

5. The apparatus of claim 1, wherein the one or more supported energy providers indicate, for an energy' profile associated with the energy' profile information, one or more energy suppliers or energy distributors.CNV15060W001 / 101859.0022026. The apparatus of claim 1, wherein the one or more supported energy rates indicate, for an energy’ profile associated with the energy profile information, an amount of money charged or energy credits consumed for energy usage.

7. The apparatus of claim 1, wherein the one or more KPIs indicate, for an energy profile associated with the energy profile information, latency, bandwidth, or availability.

8. The apparatus of claim 1, wherein the one or more supported energy credits indicate, for an energy profile associated with the energy profile information, one or more types or amounts of energy credits accepted and usable when consuming services associated with the energy profile.

9. An apparatus, comprising one or more processors, and memory storing instructions which, when executed by the one or more processors, cause the apparatus to: send, to a server, a request comprising energy profile information to cause the server to store the energy profile information; send, to the server, an energy aware discovery request comprising one or more discovery criteria to cause the server to determine, based on the discovery' request and the energy profile information, one or more servers that meet the one or more discovery criteria; and receive, from the server, information indicative of the one or more servers that meet the one or more discovery criteria.

10. The apparatus of claim 9, wherein the energy profile information indicates one or more of a supported energy’ mix, one or more supported energy sources, one or more supported energy providers, one or more supported energy rates, one or more key performance indicators (KPIs), or one or more supported energy’ credits.CNV15060W001 / 101859.00220211. The apparatus of claim 9, wherein the supported energy mix indicates, for an energy profile associated with the energy profile information, a renewable and non-renewable energy usage mix.

12. The apparatus of claim 9, wherein the one or more supported energy sources indicate, for an energy profile associated with the energy profile information, one or more types of renewable or non-renewable energy usable for the energy profile.

13. The apparatus of claim 9, wherein the one or more supported energy providers indicate, for an energy' profile associated with the energy profile information, one or more energy suppliers or energy distributors.

14. The apparatus of claim 9, wherein the one or more supported energy rates indicate, for an energy' profile associated with the energy profile information, an amount of money charged or energy’ credits consumed for energy’ usage.

15. The apparatus of claim 9, wherein the one or more KPIs indicate, for an energy profile associated with the energy' profile information, latency, bandwidth, or availability7.

16. The apparatus of claim 9, wherein the one or more supported energy credits indicate, for an energy profile associated with the energy7profile information, one or more ty pes or amounts of energy’ credits accepted and usable when consuming services associated with the energy profile.

17. A method comprising: receiving, from a user equipment (UE), a request comprising energy profile information; storing the energy profile information; receiving, from the UE. an energy aware discovery request comprising one or more discovery' criteria;CNV15060W001 / 101859.002202 determining, based on the discovery request, one or more servers that meet the one or more discovery criteria; and sending, to the UE. information indicative of the one or more servers that meet the one or more discovery criteria.

18. The method of claim 17, wherein the energy profile information indicates one or more of: a supported energy mix, one or more supported energy sources, one or more supported energy providers, one or more supported energy rates, one or more key performance indicators (KPIs), or one or more supported energy credits.

19. The method of claim 17, wherein the supported energy mix indicates, for an energy profile associated with the energy profile information, a renewable and non-renewable energy usage mix.

20. The method of claim 17, wherein the one or more supported energy7sources indicate, for an energy profile associated with the energy profile information, one or more types of renewable or non-renewable energy usable for the energy profile.

Images