Method of user equipment (UE), method of communication apparatus, UE and communication apparatus

Abstract

An aspect of this disclosure includes a method of a User Equipment (UE). The method includes communicating with a communication apparatus. The method includes receiving information related to a shutdown of a Radio Access Network (RAN).

Description

METHOD OF USER EQUIPMENT (UE), METHOD OF COMMUNICATION APPARATUS, UE AND COMMUNICATION APPARATUS

[0001] The present disclosure relates to a method of a User Equipment (UE), a method of a communication apparatus, a UE and a communication apparatus etc.

[0002] Energy consumption is a significant source of operations costs for Mobile Network Operators (MNOs) and depending on the energy generation that is used to power networks, it can also have impact on the environment. There has been increasing work in 3GPP on improving energy efficiency and energy saving. While the goal of energy efficiency is to provide the same services more efficiently, the goal of energy use control as service criteria will be to supervise services in an energy-aware manner, with ensuring the services offered as intended by service providers, network operators or subscribers, with determined constraints and consequences. 3GPP has already undertaken work in different working groups to provide recommendations on energy saving and actual OAM or Radio Network enhancements to save energy. SA plenary has issued also a 3GPP-wide recommendation in the contribution SP-231192 [NPL5] agreed at the 3GPP SAP#101 in September 2023 on considering Energy efficiency as an important design criterion for the technical solutions 3GPP defines in their specifications.

[0003] NPL 1: 3GPP TR 21.905, "Vocabulary for 3GPP Specifications", V17.1.0 (2021-12) NPL 2: 3GPP TR 22.882, " Study on Energy Efficiency as a service criteria", V19.0.0 (2023-06) NPL 3: 3GPP TS 23.501, "System architecture for the 5G System (5GS)", V18.3.0 (2023-09) NPL 4: 3GPP TS 23.502, "Procedures for the 5G System (5GS)", V18.3.0 (2023-09) NPL 5: Samsung, "New SID on 5GS Enhancement for Energy Efficiency and Energy Saving", SP-231192, https: / / www.3gpp.org / ftp / tsg_sa / TSG_SA / TSGs_101_Bangalore_2023-09 / Docs / SP-231192.zip NPL 6: 3GPP TS 23.003, "Numbering, addressing and identification", V18.3.0 (2023-09) NPL 7: IETF RFC 5580, "Carrying Location Objects in RADIUS and Diameter", (2009-08) NPL 8: 3GPP TS 24.501, "Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3", V18.4.0 (2023-09) NPL 9: 3GPP TS 23.503, "Policy and Charging Control Framework for the 5G System", V18.3.0 (2023-09)

[0004] However, there is no technical solution in the current 3GPP standards for achieving the above description in SP-231192 [NPL5].

[0005] For example, according to SP-231192 [NPL5] agreed at the 3GPP SAP#101 in September 2023, there is a need to study 5GS enhancements (e.g., energy usage adjustment for NF from CN aspect, energy saving related decision making, NF selection leveraging NF energy states) for network energy saving including 5GC(NFs) and NG-RAN interactions, analytics, etc. 　　However, there is no mechanism in the current 3GPP standards to achieve this need.

[0006] In one aspect, the present disclosure provides a method of a User Equipment (UE) comprising: communicating with a communication apparatus; and receiving information related to a shutdown of a Radio Access Network (RAN).

[0007] In one aspect, the present disclosure provides a method of a communication apparatus comprising: communicating with a User Equipment (UE); and sending information related to a shutdown of a Radio Access Network (RAN).

[0008] In one aspect, the present disclosure provides a method of a communication apparatus comprising: communicating with a User Equipment (UE); and sending information related to resuming of a Radio Access Network (RAN).

[0009] In one aspect, the present disclosure provides a method of a communication apparatus comprising: sending information related to a shutdown of a Radio Access Network (RAN); and receiving a message related to a handover of a User Equipment (UE) in a case of sending the information.

[0010] In one aspect, the present disclosure provides a method of a communication apparatus comprising: receiving information related to a shutdown of a Radio Access Network (RAN); and sending a message related to a handover of a User Equipment (UE) in a case of receiving the information.

[0011] In one aspect, the present disclosure provides a method of a communication apparatus comprising: communicating with another communication apparatus; and performing a procedure related to a handover of a User Equipment (UE) in case of a shutdown of a Radio Access Network (RAN).

[0012] In one aspect, the present disclosure provides a User Equipment (UE) comprising: means for communicating with a communication apparatus; and means for receiving information related to a shutdown of a Radio Access Network (RAN).

[0013] In one aspect, the present disclosure provides a communication apparatus comprising: means for communicating with a User Equipment (UE); and means for sending information related to a shutdown of a Radio Access Network (RAN).

[0014] In one aspect, the present disclosure provides a communication apparatus comprising: means for communicating with a User Equipment (UE); and means for sending information related to resuming of a Radio Access Network (RAN).

[0015] In one aspect, the present disclosure provides a communication apparatus comprising: means for sending information related to a shutdown of a Radio Access Network (RAN); and means for receiving a message related to a handover of a User Equipment (UE) in a case of sending the information.

[0016] In one aspect, the present disclosure provides a communication apparatus comprising: means for receiving information related to a shutdown of a Radio Access Network (RAN); and means for sending a message related to a handover of a User Equipment (UE) in a case of receiving the information.

[0017] In one aspect, the present disclosure provides a communication apparatus comprising: means for communicating with another communication apparatus; and means for performing a procedure related to a handover of a User Equipment (UE) in case of a shutdown of a Radio Access Network (RAN).

[0018] Fig. 1 is a signaling diagram of a First example of the First Aspect.Fig. 2 is a signaling diagram of a Second example of the First Aspect.Fig. 3 is a signaling diagram of a First example of the Second Aspect.Fig. 4 is a signaling diagram of a Second example of the Second Aspect.Fig. 5 is a signaling diagram of a Third example of the Second Aspect.Fig. 6 is a signaling diagram of a Fourth example of the Second Aspect.Fig. 7 is a signaling diagram of a Fifth example of the Second Aspect.Fig. 8 is a signaling diagram of a Sixth example of the Second Aspect.Fig. 9 is a signaling diagram of a Seventh example of the Second Aspect.Fig. 10 is a signaling diagram of an Eighth example of the Second Aspect.Fig. 11 is a signaling diagram of a First example of the Third Aspect.Fig. 12 is a signaling diagram of a Second example of the Third Aspect.Fig. 13 is a signaling diagram of a Third example of the Third Aspect.Fig. 14 is a diagram illustrating a system overview.Fig. 15 is a block diagram illustrating a UE.Fig. 16 is a block diagram illustrating an (R)AN node.Fig. 17 is a diagram illustrating System overview of (R)AN node based on O-RAN architecture.Fig. 18 is a block diagram illustrating an RU.Fig. 19 is a block diagram illustrating a DU.Fig. 20 is a block diagram illustrating a CU.Fig. 21 is a block diagram illustrating an AMF.Fig. 22 is a block diagram illustrating an SMF.Fig. 23 is a block diagram illustrating a UPF.Fig. 24 is a block diagram illustrating a PCF.Fig. 25 is a block diagram illustrating an NWDAF.Fig. 26 is a block diagram illustrating a UDM.Fig. 27 is a block diagram illustrating a CHF.Fig. 28 is a block diagram illustrating an NSACF.Fig. 29 is a block diagram illustrating an EECF.Fig. 30 is a block diagram illustrating an NEF.Fig. 31 is a block diagram illustrating an OAM.Fig. 32 is a block diagram illustrating an AF.

[0019] Abbreviations 　　For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [NPL1] and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in 3GPP TR 21.905 [NPL1]. 4G-GUTI　　4G Globally Unique Temporary UE Identity 5GC　　　　5G Core Network 5GLAN　　　　5G Local Area Network 5G HE AV　　5G Home Environment Authentication Vector 5G SE AV　　5G Serving Environment Authentication Vector 5GS　　　　5G System 5G-AN　　　　5G Access Network 5G-AN PDB　　5G Access Network Packet Delay Budget 5G-EIR　　　　5G-Equipment Identity Register 5G-GUTI　　5G Globally Unique Temporary Identifier 5G-BRG　　5G Broadband Residential Gateway 5G-CRG　　5G Cable Residential Gateway 5G GM　　　　5G Grand Master 5G-RG　　　　5G Residential Gateway 5G-S-TMSI　　5G S-Temporary Mobile Subscription Identifier 5G VN　　　　5G Virtual Network 5QI　　　　5G QoS Identifier ABBA　　　　Anti-Bidding down Between Architectures AF　　　　Application Function AF ID　　　　Application Function identity AMF　　　　Access and Mobility Management Function AMF-G　　　　Geographically selected Access and Mobility Management Function AMF-NG　　Non-Geographically selected Access and Mobility Management Function ANDSF　　　　Access Network Discovery and Selection Function APP ID　　　　Application Identifier ARFCN　　　　Absolute radio-frequency channel number AS　　　　Access Stratum ASN　　　　Abstract Syntax Notation ATSSS　　　　Access Traffic Steering, Switching, Splitting ATSSS-LL　　ATSSS Low-Layer AuC　　　　Authentication Centre AUSF　　　　Authentication Server Function AUTN　　　　Authentication token BCCH　　　　Broadcast Control Channel BMCA　　　　Best Master Clock Algorithm BSF　　　　Binding Support Function CAG　　　　Closed Access Group CAPIF　　　　Common API Framework for 3GPP northbound APIs CHF　　　　Charging Function CN PDB　　Core Network Packet Delay Budget CP　　　　Control Plane DAPS　　　　Dual Active Protocol Stacks DL　　　　Downlink DN　　　　Data Network DNAI　　　　DN Access Identifier DNN　　　　Data Network Name DRX　　　　Discontinuous Reception DS-TT　　　　Device-side TSN translator ePDG　　　　evolved Packet Data Gateway EBI　　　　EPS Bearer Identity ECGI　　　　E-UTRAN Cell Global Identifier EECF　　　　Energy Efficiency Control Function EPS　　　　Evolved Packet System EUI　　　　Extended Unique Identifier FAR　　　　Forwarding Action Rule FN-BRG　　Fixed Network Broadband RG FN-CRG　　Fixed Network Cable RG FN-RG　　　　Fixed Network RG FQDN　　　　Fully Qualified Domain Name GCI　　　　Global Cable Identifier GEO　　　　Geostationary Earth Orbit GFBR　　　　Guaranteed Flow Bit Rate GMLC　　　　Gateway Mobile Location Centre G-PDU　　　　GTP encapsulated user Plane Data Unit GPS　　　　Global Positioning System GPSI　　　　Generic Public Subscription Identifier GSO　　　　Geosynchronous Orbit GUAMI　　　　Globally Unique AMF Identifier GUTI　　　　Globally Unique Temporary UE Identity HPLMN　　Home Public Land Mobile Network HR　　　　Home Routed (roaming) HSS　　　　Home Subscriber Server IAB　　　　Integrated access and backhaul IEC　　　　International Electrotechnical Commission IMEI / TAC　　IMEI Type Allocation Code IMSI　　　　International Mobile Subscriber Identity IPsec　　　　Internet Protocol Security IPUPS　　　　Inter PLMN UP Security I-SMF　　　　Intermediate SMF ISO　　　　International Organization for Standardization I-UPF　　　　Intermediate UPF LADN　　　　Local Area Data Network LBO　　　　Local Break Out (roaming) LCS　　　　Location Service LEO　　　　Low Earth Orbit LMF　　　　Location Management Function LoA　　　　Level of Automation LPP　　　　LTE Positioning Protocol LRF　　　　Location Retrieval Function MA　　　　Multi Access MCC　　　　Mobile country code MCX　　　　Mission Critical Service MDBV　　　　Maximum Data Burst Volume ME　　　　Mobile Equipment MFBR　　　　Maximum Flow Bit Rate MICO　　　　Mobile Initiated Connection Only MINT　　　　Minimization of service interruption MITM　　　　Man In the Middle MME　　　　Mobility Management Entity MN　　　　Master Node MNC　　　　Mobile Network Code MNO　　　　Mobile Network Operator MOCN　　　　Multiple Operator Core Network MPS　　　　Multimedia Priority Service MPTCP　　　　Multi-Path TCP Protocol MT　　　　Mobile Termination, Mobile Terminating, Mobile terminated N3IWF　　　　Non-3GPP InterWorking Function N3GPP　　　　Non-3GPP access N5CW　　　　Non-5G-Capable over WLAN NAI　　　　Network Access Identifier NAS　　　　Non-Access-Stratum NCGI　　　　NR Cell Global Identity NCI　　　　NR Cell Identity NEF　　　　Network Exposure Function NF　　　　Network Function NGAP　　　　Next Generation Application Protocol NGSO　　　　Non-Geosynchronous Satellite Orbit NID　　　　Network identifier NMEA　　　　National Marine Electronics Association NPN　　　　Non-Public Network NR　　　　New Radio NSAG　　　　Network Slice Access Stratum Group NRF　　　　Network Repository Function NSAC　　　　Network Slice Admission Control NSACF　　　　Network Slice Admission Control Function NSI ID　　　　Network Slice Instance Identifier NSSAA　　　　Network Slice-Specific Authentication and Authorization NSSAAF　　Network Slice-Specific Authentication and Authorization Function NSSAI　　　　Network Slice Selection Assistance Information NSSF　　　　Network Slice Selection Function NSSP　　　　Network Slice Selection Policy NSSRG　　　　Network Slice Simultaneous Registration Group NW-TT　　　　Network-side TSN translator NWDAF　　Network Data Analytics Function OS ID　　　　Operating System Identifier PCF　　　　Policy Control Function PCO　　　　Protocol Configuration Options PCRF　　　　Policy and Charging Rules Function PDB　　　　Packet Delay Budget PDR　　　　Packet Detection Rule PDU　　　　Protocol Data Unit PEI　　　　Permanent Equipment Identifier PER　　　　Packet Error Rate PFD　　　　Packet Flow Description PLMN　　　　Public Land Mobile Network PNI-NPN　　Public Network Integrated Non-Public Network PPD　　　　Paging Policy Differentiation PPF　　　　Paging Proceed Flag PPI　　　　Paging Policy Indicator ProSe　　　　Proximity based Services PSA　　　　PDU Session Anchor PTP　　　　Precision Time Protocol QFI　　　　QoS Flow Identifier QoE　　　　Quality of Experience QoS ID　　　　5G QoS Identifier RACS　　　　Radio Capabilities Signalling optimisation (R)AN　　　　(Radio) Access Network RAT　　　　Radio Access Technology RFID　　　　Radio Frequency Identification RG　　　　Residential Gateway RIM　　　　Remote Interference Management RQA　　　　Reflective QoS Attribute RQI　　　　Reflective QoS Indication RRC　　　　Radio Resource Control RSC　　　　Relay Service Code RSD　　　　Route Selection Descriptor RSN　　　　Redundancy Sequence Number RSRP　　　　Reference Signal Received Power RSRQ　　　　Reference Signal Received Quality RTT　　　　Round-Trip Time RU　　　　Radio Unit RVAS　　　　Roaming Value Added Service SA NR　　　　Standalone New Radio SBA　　　　Service Based Architecture SBI　　　　Service Based Interface SCP　　　　Service Communication Proxy SD　　　　Slice Differentiator SEAF　　　　Security Anchor Functionality SENSE　　　　Signal Level Enhanced Network Selection SEPP　　　　Security Edge Protection Proxy SGW　　　　Serving Gateway SIB　　　　System Information Block SINR　　　　Signal to Interference plus Noise Ratio SLA　　　　Service Level Agreement SMF　　　　Session Management Function SMS　　　　Short Message Service SMSF　　　　Short Message Service Function SN　　　　Sequence Number SN　　　　Secondary Node SN name　　Serving Network Name SNPN　　　　Stand-alone Non-Public Network S-NSSAI　　Single Network Slice Selection Assistance Information SOR　　　　Steering of Roaming SSC　　　　Session and Service Continuity SSCMSP　　Session and Service Continuity Mode Selection Policy SST　　　　Slice / Service Type SUCI　　　　Subscription Concealed Identifier SUPI　　　　Subscription Permanent Identifier SV　　　　Software Version TAI　　　　Tracking Area Identity TAU　　　　Tracking Area Update TEID　　　　Tunnel Endpoint Identifier TMGI　　　　Temporary Mobile Group Identity TMSI　　　　Temporary Mobile Subscriber Identity TNAN　　　　Trusted Non-3GPP Access Network TNAP　　　　Trusted Non-3GPP Access Point TNGF　　　　Trusted Non-3GPP Gateway Function TNL　　　　Transport Network Layer TNLA　　　　Transport Network Layer Association TSC　　　　Time Sensitive Communication TSCAI　　　　TSC Assistance Information TSN　　　　Time Sensitive Networking TSN GM　　TSN Grand Master TSP　　　　Traffic Steering Policy TT　　　　TSN Translator TWIF　　　　Trusted WLAN Interworking Function UCMF　　　　UE radio Capability Management Function UCU　　　　UE Configuration Update UDM　　　　Unified Data Management UDR　　　　Unified Data Repository UDSF　　　　Unstructured Data Storage Function UE　　　　User Equipment UL　　　　Uplink UL CL　　　　Uplink Classifier UPF　　　　User Plane Function UPSI　　　　UE Policy Section Identifier URLLC　　　　Ultra Reliable Low Latency Communication URRP-AMF　　UE Reachability Request Parameter for AMF URSP　　　　UE Route Selection Policy USIM　　　　User Services Identity Module VID　　　　VLAN Identifier VLAN　　　　Virtual Local Area Network VPLMN　　Visited Public Land Mobile Network W-5GAN　　Wireline 5G Access Network W-5GBAN　　Wireline BBF Access Network W-5GCAN　　Wireline 5G Cable Access Network W-AGF　　　　Wireline Access Gateway Function WPT　　　　Wireless Power Transfer

[0020] Definitions 　　For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [NPL1] and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in 3GPP TR 21.905 [NPL1].

[0021] General 　　Those skilled in the art will appreciate that elements in the figures are illustrated for simplicity and may not have necessarily been drawn to scale. Furthermore, in terms of the construction of the device, one or more components of the device may have been represented in the figures by conventional symbols, and the figures may show only those specific details that are pertinent to understanding the Aspects of the present disclosure so as not to obscure the figures with details that will be readily apparent to those skilled in the art having the benefit of the description herein.

[0022] For the purpose of promoting an understanding of the principles of the disclosure, reference will now be made to the Aspect illustrated in the figures and specific language will be used to describe them. It will nevertheless be understood that no limitation of the scope of the disclosure is thereby intended. Such alterations and further modifications in the illustrated system, and such further applications of the principles of the disclosure as would normally occur to those skilled in the art are to be construed as being within the scope of the present disclosure.

[0023] The terms "comprises", "comprising", or any other variations thereof, are intended to cover a non-exclusive inclusion, such that a process or method that comprises a list of steps does not include only those steps but may include other steps not expressly listed or inherent to such a process or method. Similarly, one or more devices or entities or sub-systems or elements or structures or components preceded by "comprises... a" does not, without more constraints, preclude the existence of other devices, sub-systems, elements, structures, components, additional devices, additional sub-systems, additional elements, additional structures or additional components. Appearances of the phrase "in an Aspect", "in another Aspect" and similar language throughout this specification may, but not necessarily do, all refer to the same Aspect.

[0024] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by those skilled in the art to which this disclosure belongs. The system, methods, and examples provided herein are only illustrative and not intended to be limiting.

[0025] In the following specification and the claims, reference will be made to a number of terms, which may be defined to have the following meanings. The singular forms "a", "an", and "the" include plural references unless the context clearly dictates otherwise.

[0026] As used herein, information is associated with data and knowledge, as data is meaningful information and represents the values attributed to parameters. Further knowledge signifies understanding of an abstract or concrete concept. Note that this example system is simplified to facilitate description of the disclosed subject matter and is not intended to limit the scope of this disclosure. Other devices, systems, and configurations may be used to implement the Aspects disclosed herein in addition to, or instead of, a system, and all such Aspects are contemplated as within the scope of the present disclosure.

[0027] Each of Aspects and elements included in the each of Aspects described below may be implemented independently or in combination with any other. These Aspects include novel characteristics different from one another. Accordingly, these Aspects contribute to achieving objects or solving problems different from one another and contribute to obtaining advantages different from one another.

[0028] Any lists described in following aspects include at least one parameter or multiple parameters.

[0029] An example object of this disclosure is to provide a method and apparatus that can solve the above-mentioned problem.

[0030] In this disclosure, regarding listed parameters in the certain message, at least one of the listed parameters may be included in the certain message. For example, "the message including parameter A and parameter B" may mean "the message including at least one of parameter A and parameter B". In addition, for example, "A including (or containing, or similar wording etc.) B and C" may mean "A including at least one of B and C".

[0031] A method of a User Equipment (UE) according to example aspect of this disclosure includes communicating with a communication apparatus. The method includes receiving information related to a shutdown of a Radio Access Network (RAN).

[0032] A method of a communication apparatus according to example aspect of this disclosure includes communicating with a User Equipment (UE). The method includes sending information related to a shutdown of a Radio Access Network (RAN).

[0033] A method of a communication apparatus according to example aspect of this disclosure includes communicating with a User Equipment (UE). The method includes sending information related to resuming of a Radio Access Network (RAN).

[0034] A method of a communication apparatus according to example aspect of this disclosure includes sending information related to a shutdown of a Radio Access Network (RAN). The method includes receiving a message related to a handover of a User Equipment (UE) in a case of sending the information.

[0035] A method of a communication apparatus according to example aspect of this disclosure includes receiving information related to a shutdown of a Radio Access Network (RAN). The method includes sending a message related to a handover of a User Equipment (UE) in a case of receiving the information.

[0036] A method of a communication apparatus according to example aspect of this disclosure includes communicating with another communication apparatus. The method includes performing a procedure related to a handover of a User Equipment (UE) in case of a shutdown of a Radio Access Network (RAN).

[0037] A User Equipment (UE) according to example aspect of this disclosure includes at least one memory, and at least one hardware processor coupled to the at least one memory. The at least one hardware processor is configured to communicate with a communication apparatus. The at least one hardware processor is configured to receive information related to a shutdown of a Radio Access Network (RAN).

[0038] A communication apparatus according to example aspect of this disclosure includes at least one memory, and at least one hardware processor coupled to the at least one memory. The at least one hardware processor is configured to communicate with a User Equipment (UE). The at least one hardware processor is configured to send information related to a shutdown of a Radio Access Network (RAN).

[0039] A communication apparatus according to example aspect of this disclosure includes at least one memory, and at least one hardware processor coupled to the at least one memory. The at least one hardware processor is configured to communicate with a User Equipment (UE). The at least one hardware processor is configured to send information related to resuming of a Radio Access Network (RAN).

[0040] A communication apparatus according to example aspect of this disclosure includes at least one memory, and at least one hardware processor coupled to the at least one memory. The at least one hardware processor is configured to send information related to a shutdown of a Radio Access Network (RAN). The at least one hardware processor is configured to receive a message related to a handover of a User Equipment (UE) in a case of sending the information.

[0041] A communication apparatus according to example aspect of this disclosure includes at least one memory, and at least one hardware processor coupled to the at least one memory. The at least one hardware processor is configured to receive information related to a shutdown of a Radio Access Network (RAN). The at least one hardware processor is configured to send a message related to a handover of a User Equipment (UE) in a case of receiving the information.

[0042] A communication apparatus according to example aspect of this disclosure includes at least one memory, and at least one hardware processor coupled to the at least one memory. The at least one hardware processor is configured to communicate with another communication apparatus. The at least one hardware processor is configured to perform a procedure related to a handover of a User Equipment (UE) in case of a shutdown of a Radio Access Network (RAN).

[0043] First Aspect 　　According to SP-231192 [NPL5] agreed at the 3GPP SAP#101 in September 2023, there is a need to study potential framework for network energy consumption exposure. This will include whether and what information is exposed, how it is exposed (e.g., charging) and at what granularity, e.g., at RAN level, Core Network level, network slice level, UE level and / or PDU session level. 　　However, there is no mechanism in the current 3GPP standards to achieve this need.

[0044] The First Aspect includes a mechanism for energy usage exposure to a 3rdparty Service Provider in a granularity way (e.g. network level, CN level, RAN level, NF level, S-NSSAI level, PDU Session level, UE level) and a mechanism for parameters provision and update within the 3GPP system by 3rdparty Service Provider related to the Energy Efficiency.

[0045] First Example of the First Aspect 　　Fig. 1 illustrates a mechanism for energy usage and / or energy efficiency exposure to a 3rdparty Service Provider in a granularity way. It is assumed that a NF will be designated as energy efficiency monitoring and controlling entity in the network with the purpose of monitoring and controlling the energy usage / efficiency in the network and in the Network Functions. This energy usage / energy efficiency controlling entity may be a new NF called, for example, Energy Efficiency Control Function (EECF 78) or any other name for the purpose of energy usage / efficiency monitoring, evaluation and control in the network and in the Network Functions. The EECF 78 may also be embedded within an existing NFs like O&M, NWDAF, NEF, PCF, NSACF, UDM, NSACF or any other new or existing NF. The Fig. 1 below discloses an energy usage exposure to the AF 201 in different granularity levels, e.g., network level, NF level, S-NSSAI level, PDU Session level, UE level, etc. 　　One example, there is one EECF 78 in the PLMN. One another example, PLMN operator configures multiple EECFs 78 per location basis or per network domain.

[0046] The detailed processes of the First example of the First Aspect are described below, with reference to Fig. 1.

[0047] Step 0. It is assumed that the EECF 78 has subscribed to NF(s), as Energy usage entities, for the energy usage and energy efficiency monitoring and the EECF 78 maintains the energy usage and energy efficiency information for reporting. 　　For example, the EECF 78 has subscribed to NF(s) based on the processes as disclosed by the Second Aspect in this disclosure.

[0048] Step 1. A Network Operator or an external Service provider, e.g., AF 201, may require energy usage monitoring in the network and reporting with a granularity of the entire network or with granularity of specific parts of the network like a Network Function or specific entities of the network, like a network slice or a PDU Session. For this, the AF 201 needs a subscription for such monitoring and reporting purpose. The AF 201 may trigger the Nnef_EventExposure_Subscribe Request service operation in which the AF 201 may include the following parameters:

[0049] - AF ID: Application Function identity, this identity uniquely identifies an application function which is sending this request. This application identity is checked at NEF 79 or UDM 75 to verify the authenticity of the AF 201, e.g. NEF 79 or UDM 75 stores a list of valid AF IDs. When the UDM 75 or NEF 79 receives the AF ID the UDM 75 or NEF 79 verifies the AF ID by comparing it with the stored AF IDs. If the AF ID is matched with one of the stored AF IDs then it is a valid AF ID otherwise not. In case the AF ID is not valid then the NEF 79 or UDM 75 will ignore the message.

[0050] - Energy usage / efficiency request reference ID - The Energy usage / efficiency request reference ID is an identifier of the Energy usage / efficiency request from the AF 201. The Energy usage / efficiency request reference ID is generated by the AF 201 to uniquely identify the Energy usage request by both AF 201 and NEF 79. The Energy usage / efficiency request reference ID may be converted to another Energy usage / efficiency request reference ID by the NEF 79 in order to uniquely identify the Energy usage / efficiency request in Core network 7 (e.g., 5GC) and RAN 5.

[0051] - Energy usage / efficiency report request - or any other notation for a parameter with the purpose to indicate a subscription for energy usage / efficiency monitoring and reports. The energy usage / efficiency report request may be expressed in 'energy units' or 'energy credits', Watt, Joule, bit / Joule or in any other expression for energy usage / efficiency in order to indicate the level of the used energy or the level of the remaining energy for the whole network or for a network entity. The energy usage / efficiency report request may indicate that the entity which sends the energy usage / efficiency report request (e.g., AF 201) requests the energy usage / efficiency monitoring and reports. The energy usage / efficiency report request may indicate that the energy usage / efficiency monitoring and reports is requested or required. The energy usage / efficiency report request may indicate a request for details on energy usage / efficiency. For example, energy usage / efficiency per the RF power amplifier for DL and UP on control channel, per the RF power amplifier for DL and UP on data bear channel, per server, per air-conditioner at a cite, per air-conditioner at a data centre if the detail information is requested.

[0052] - Energy usage entity - this is the network entity for which the energy usage or energy usage levels report is required. The Energy usage entity may have different granularity. It may be the entire network, one or more Network Functions, one or more S-NSSAIs or one or more PDU Sessions or one or more UEs. Additionally, the Energy usage entity may include an Entity identifier. For example, the Entity identifier may be an equipment model name, a service provider, vender name, a vender number that are assigned by a PLMN or an organization in telecommunication standardization body or industry body. The Energy usage entity may indicate the network entity for which the energy usage or energy usage levels report is required. The network entity may include the entire network, one or more Network Functions, one or more S-NSSAIs or one or more PDU Sessions or one or more UEs. When the Energy usage entity indicates one or more UEs, the Energy usage / efficiency report request is about the amount of the energy used by the network to provide a service or services to the indicated UE(s).

[0053] - Reporting mode - the reporting mode defines whether the energy usage or energy usage levels for a network or for a network entity or a network slice are to be reported event based (e.g. threshold based) or periodically.

[0054] - Reporting threshold - if the requested reporting mode is threshold based, the AF 201 provides reporting threshold defined in used energy or remaining energy credit units.

[0055] - Reporting period - the time period measured in time units when the energy usage reporting is triggered by the EECF 78. The Reporting period may indicate immediate report.

[0056] - Location - It is possible that the reports for energy usage levels or energy usage for the network entities (e.g., the energy usage / efficiency monitoring and reports) are required for network entities in specific location. If so, the AF 201 may provide a location information which can be a geographical location and any other definition of location. For example, Location can be a list of Tracking Area Identity (TAI), a list of NR Cell Global Identity (NCGI) as defined in the 3GPP TS 23.003 [NPL6], a list of NR Cell Identity (NCI) as defined in the 3GPP TS 23.003 [NPL6], a list of E-UTRAN Cell Global Identifier (ECGI) as defined in the 3GPP TS 23.003 [NPL6], a list of Global Cable Identifier (GCI) as defined in the 3GPP TS 23.003 [NPL6], a general City name, zip-code, formed with GPS location or a location expressed with civic and geospatial location formats as defined in IETF RFC 5580 [NPL7]. The Location information may be a single Location information or multiple Location information. The Location information may indicate that location where the reports for energy usage levels or energy usage for the network entities (e.g., the energy usage / efficiency monitoring and reports) is requested or required.

[0057] - PDU Sessions - The PDU Sessions, together with UE ID, indicates the PDU Session ID subject for the energy usage and energy efficiency monitoring. The PDU Session IDs may be a single PDU Session ID or multiple PDU Session IDs. The UE ID may take a form of Generic Public Subscription Identifier (GPSI), MSISDN or SUPI as defined in 3GPP TS 23.003 [NPL6]. The PDU Sessions may be configured without UE ID. PDU Sessions may be expressed as PDU Session IDs.

[0058] - S-NSSAIs - The S-NSSAIs indicates the S-NSSAI subject for the energy usage and energy efficiency monitoring. The S-NSSAIs may be a single S-NSSAI or multiple S-NSSAIs.

[0059] - UEs - The UEs indicates the UEs subject for the energy usage and energy efficiency monitoring. The UEs may be a single UE or multiple UEs. The UEs may take a form of Generic Public Subscription Identifier (GPSI), MSISDN or SUPI or IMEI as defined in 3GPP TS 23.003 [NPL6]. The UE could be UE type e.g., NB-IoT UEs, reduced capability or different types of the UE defined for EPS and 5GS.

[0060] - System type - This IE indicates whether the energy reporting is required from NFs of 5GS or 6GS or EPS (or another network system).

[0061] - RAT type - RAT type indicates energy reporting related to 3GPP RAT (e.g. NR or E-UTRAN) or non-3GPP RAT.DNN (Domain Network Name) - reporting of an energy consumption (e.g., the energy usage / efficiency monitoring and reports) for a particular DNN. The DNN may indicate DNN for which energy consumption needs to be reported.

[0062] - S-NSSAI and DNN combination - energy consumption related to a DNN and S-NSSAI combination. The S-NSSAI and DNN combination may indicate S-NSSAI and DNN combination for which energy consumption needs to be reported.

[0063] - PLMN ID - In case the 5GS is shared among multiple PLMNs, then the PLMN ID or list of PLMN IDs are sent to report the energy consumption related to the PLMN or the list of PLMNs. The PLMN ID may indicate PLMN ID for which energy consumption needs to be reported.

[0064] - QoS ID - request to report the energy consumption as per the QoS ID defined in the 3GPP TS 24.501 [NPL8]. The QoS ID may indicate QoS ID for which energy consumption needs to be reported.

[0065] - APP ID - request to report the energy consumption by application identified by an application identity. The application identity for an application is defined in 3GPP TS 24.501 [NPL8]. The APP ID may indicate an application identity of the application for which energy consumption needs to be reported. In one example, APP ID may be referred as OS specific Application Identifier (OSAppId) as defined in 3GPP TS 23.503 [NPL9]. In another example, APP ID may be referred as OS ID + APP ID.

[0066] Step 2. The NEF 79 may interact with the UDM 75 in order to authorize the AF 201 for the requested service subscription for energy usage reporting. 　　If the NEF 79 provides a general City name, zip-code, formed with GPS location or a location expressed with civic and geospatial location formats as defined in IETF RFC 5580 [NPL7] or another geographical location information (for example GPS), the UDM 75 converts it to a 3GPP location like a Cell, a list of Cell Id, TAI or a list of TAI and provides them to the NEF 79.

[0067] If the NEF 79 provides the UEs (e.g., "UEs" parameter) to the UDM 75, the UDM 75 may provide a following information to the NEF 79. - A name, FQDN or IP address of an associated AMF 70 with the UE 3. - A name, FQDN or IP address of associated PCFs 73 with the UE 3. - A name, FQDN or IP address of an associated RAN 5 with the UE 3. - A name, FQDN or IP address of an associated gNB CP with the UE 3. - A name, FQDN or IP address of an associated gNB UP with the UE 3. - A name, FQDN or IP address of an associated gNB DU with the UE 3.

[0068] If the NEF 79 provides the PDU Session IDs (together with associated UE ID) to the UDM 75, the UDM 75 may provide a following information to the NEF 79. - A name, FQDN or IP address of an associated AMF 70 with the UE 3. - A name, FQDN or IP address of associated SMFs 71 with the UE 3. - A name, FQDN or IP address of associated UPFs 72 with the UE 3. - A name, FQDN or IP address of associated PCFs 73 with the UE 3. - A name, FQDN or IP address of an associated RAN 5 with the UE 3. - A name, FQDN or IP address of an associated gNB CP with the UE 3. - A name, FQDN or IP address of an associated gNB UP with the UE 3. - A name, FQDN or IP address of an associated gNB DU with the UE 3.

[0069] Step 3. After successful authorisation of the subscription request from the AF 201 for energy usage or for energy status reporting (or after the NEF 79 receives at least one of the parameters mentioned in step 1), the NEF 79 forwards the request to the EECF 78 with or using the Neecf_EnergyUsageExposure_Subscription Request service operation or with or using any other existing or new service operation for the purpose of subscription with the EECF 78 for energy usage or energy status reporting to the AF 201 in which the NEF 79 includes all the parameters (e.g.., energy usage request reference ID, energy usage report request, energy usage entity, reporting mode, reporting threshold, reporting period, location PDU session IDs, S-NSSAIs, UEs, System type, RAT type, DNN) received from the AF 201.

[0070] The NEF 79 may send the at least one of the received parameters from the AF 201 in step 1. 　　The NEF 79 may send the Neecf_EnergyUsageExposure_Subscription Request message including the at least one of the received parameters from the AF 201 in step 1. 　　If location information was provided from the AF 201, the NEF 79 provides to the EECF 78 the 3GPP mapped location. If GPSI or MSISDN was provided by the AF 201, the NEF 79 provides a SUPI to the EECF 78 that is converted by the UDM 75.

[0071] In case that the NEF 79 needs to subscribe to multiple EECFs 78, the NEF 79 invokes multiple Neecf_EnergyUsageExposure_Subscription Request service operations to EECFs 78. For example, if the AF 201 designated two location information e.g., Tokyo and Osaka where the PLMN operator configures one EECF 78 for Tokyo area and another EECF 78 for Osaka area, the NEF 79 invokes two Neecf_EnergyUsageExposure_Subscription Request service operations to an EECF 78 in Tokyo and another EECF 78 in Osaka.

[0072] In one example, the UDM 75 may provide one or multiple EECFs 78 that the NEF 79 may contact for the energy usage and energy efficiency monitoring. In this case, a name, FQDN or IP address of the EECF 78 may be provided to the NEF 79.

[0073] For example, the UDM 75 may indicate, to the one or multiple EECFs 78, that the NEF 79 may contact the one or multiple EECFs 78 for the energy usage and energy efficiency monitoring. In this case, the UDM 75 may provide a name, FQDN or IP address of the EECF 78 to the NEF 79.

[0074] Step 4. The EECF 78 is called as Energy Efficiency Control Function or any other notation for a Network Function or network entity which is designated for monitoring and control of the energy efficiency and / or energy usage by the network entities or energy levels of the network entities like Network Functions or the UE or network slices or PDU Sessions. The EECF 78 may be a new Network Function or it can be an entity or functionality embedded in one of the existing NFs like O&M or UDM or PCF or SMF or UPF or NSSF or NSACF or NWDAF or any other existing or new NF. The EECF 78 stores the subscription information related to the energy usage reporting and confirms the subscription with or by the return of Neecf_EnergyUsage_Subscribe Response to the NEF 79. 　　For example, in a case where the EECF 78 receives at least one of the parameters in step 3, the EECF 78 may send the response to the NEF 79.

[0075] Step 5. The NEF 79 forwards the subscription response to the AF 201 in Nnef_EventExposure_Subscribe Response message.

[0076] Step 6. The EECF 78 evaluates the Neecf_EnergyUsageExposure_Subscription Request message from the NEF 79 in Step 3 and checks whether the EECF 78 has enough information to report (NOTIFY) to AF 201 or the NEF 79. 　　If the EECF 78 needs more energy usage and energy efficiency monitoring information to comply to the request in Step 3, the EECF 78 may additionally subscribe to NFs and collect necessary energy usage and efficiency information from NFs.

[0077] For example, the EECF 78 triggers the processes as disclosed by the Second Aspect in this disclosure to collect more energy usage and efficiency information. 　　The energy usage and efficiency information may include information indicating energy usage of NF(s) or network entity. 　　The energy usage and efficiency information may include information indicating energy efficiency of NF(s) or network entity.

[0078] The EECF 78 monitors and evaluates the energy usage and energy efficiency in the network, possibly per granularity level if so required in the subscription by the AF 201 via the NEF 79, e.g. per network level, CN level, RAN level, NF level, S-NSSAI level, PDU Session level and etc. The EECF 78 stores the evaluated energy usage, energy level and energy efficiency information for reporting, to the AF 201 or O&M for example, in periodic or event-based mode depending on the subscription by the NEF 79. The EECF 78 may also monitor the current Energy levels of the Network Functions or network slices or PDU Sessions which could be represented in energy credit units, for example. The Network Operator or the Service Provider may allocate energy credit units with the granularity, e.g. per network level, CN level, UE level, RAN level, NF level, S-NSSAI level, PDU Session level and etc. If the subscription is for event based reporting, when a reporting event occurs, for example the energy usage of one or more energy usage entities have reached a threshold level or the energy credit units allocated to a network usage entity reaches a threshold level, the EECF 78 triggers energy usage reporting to the O&M or to the AF 201 via the NEF 79. The energy usage reporting threshold levels may be provided to the EECF 78 by the AF 201 via the NEF 79 or alternatively are configured by the Network Operator in the EECF 78 or provided in the EECF 78 by the O&M entity. If the reporting mode is periodic, the EECF 78 triggers the energy usage reports periodically, with the periodicity provided during the subscription for the service by the AF 201 within the reporting period parameter.

[0079] Step 7. When the condition on the Reporting threshold is met or the condition on the Reporting period is met, the EECF 78 sends Neecf_EnergyUsageExposure_Notify message to the NEF 79 including the following parameters:

[0080] - Energy usage / efficiency request reference ID - The Energy usage / efficiency request reference ID is an identifier of the Energy usage / efficiency request from the AF 201. The Energy usage / efficiency request reference ID is generated by the AF 201 to uniquely identify the Energy usage request by both AF 201 and NEF 79. The Energy usage / efficiency request reference ID may be converted to another Energy usage / efficiency request reference ID by the NEF 79 in order to uniquely identify the Energy usage / efficiency request in Core network 7 (e.g., 5GC) and RAN 5. The Energy usage / efficiency request reference ID may be same to the Energy usage / efficiency request reference ID in step 3.

[0081] - Energy usage / efficiency report - the energy usage or efficiency report or any other notation for a parameter with the purpose of energy usage or energy efficiency or energy levels reporting. The energy usage / efficiency report may be expressed in 'energy units' or 'energy credits' or Joule or in any other expression for energy in order to indicate the level of the used energy or the level of the remaining energy of the enquired entity, network slice, PDU Session or UE or network slice and DNN combination. The Energy usage / efficiency report may include information indicating energy usage of NF(s) or network entity (e.g., NF(s) or network entity indicated by "Energy usage entity" parameter mentioned in step 1). The Energy usage / efficiency report may include information indicating energy efficiency of NF(s) or network entity (e.g., NF(s) or network entity indicated by "Energy usage entity" parameter mentioned in step 1). The Energy usage / efficiency report may include information indicating energy credits of NF(s) or network entity (e.g., NF(s) or network entity indicated by "Energy usage entity" parameter mentioned in step 1).

[0082] The Energy usage / efficiency report may include information indicating load or load level of NF(s) or network entity (e.g., NF(s) or network entity indicated by "Energy usage entity" parameter mentioned in step 1). The Energy usage / efficiency report may include information indicating energy usage related to PDU Session(s) (e.g., PDU Session(s) indicated by "PDU Sessions" parameter mentioned in step 1). The Energy usage / efficiency report may include information indicating energy efficiency related to PDU Session(s) (e.g., PDU Session(s) indicated by "PDU Sessions" parameter mentioned in step 1). The Energy usage / efficiency report may include information indicating energy credits related to PDU Session(s) (e.g., PDU Session(s) indicated by "PDU Sessions" parameter mentioned in step 1). The Energy usage / efficiency report may include information indicating load or load level related to PDU Session(s) (e.g., PDU Session(s) indicated by "PDU Sessions" parameter mentioned in step 1).

[0083] The Energy usage / efficiency report may include information indicating energy usage related to S-NSSAI(s) (e.g., S-NSSAI(s) indicated by "S-NSSAIs" parameter mentioned in step 1). The Energy usage / efficiency report may include information indicating energy efficiency related to S-NSSAI(s) (e.g., S-NSSAI(s) indicated by "S-NSSAIs" parameter mentioned in step 1). The Energy usage / efficiency report may include information indicating energy credits related to S-NSSAI(s) (e.g., S-NSSAI(s) indicated by "S-NSSAIs" parameter mentioned in step 1). The Energy usage / efficiency report may include information indicating load or load level related to S-NSSAI(s) (e.g., S-NSSAI(s) indicated by "S-NSSAIs" parameter mentioned in step 1).

[0084] The Energy usage / efficiency report may include information indicating energy usage related to UE(s) (e.g., UE(s) indicated by "UEs" parameter mentioned in step 1). The Energy usage / efficiency report may include information indicating energy efficiency related to UE(s) (e.g., UE(s) indicated by "UEs" parameter mentioned in step 1). The Energy usage / efficiency report may include information indicating energy credits related to UE(s) (e.g., UE(s) indicated by "UEs" parameter mentioned in step 1). The Energy usage / efficiency report may include information indicating load or load level related to UE(s) (e.g., UE(s) indicated by "UEs" parameter mentioned in step 1).

[0085] In the same manner as the above, the Energy usage / efficiency report may include information indicating energy usage related to at least one of the parameters mentioned in step 1 including for example energy usage / efficiency report per the RF power amplifier for DL and UP on control channel, per the RF power amplifier for DL and UP on data bear channel, per server, per air-conditioner at a cite, per air-conditioner at a data centre. 　　In the same manner as the above, the Energy usage / efficiency report may include information indicating energy efficiency related to at least one of the parameters mentioned in step 1 including for example energy usage / efficiency report per the RF power amplifier for DL and UP on control channel, per the RF power amplifier for DL and UP on data bear channel, per server, per air-conditioner at a cite, per air-conditioner at a data centre. 　　In the same manner as the above, the Energy usage / efficiency report may include information indicating energy credits related to at least one of the parameters mentioned in step 1 including for example energy credits report per the RF power amplifier for DL and UP on control channel, per the RF power amplifier for DL and UP on data bear channel, per server, per air-conditioner at a cite, per air-conditioner at a data centre. 　　In the same manner as the above, the Energy usage / efficiency report may include information indicating load or load level related to at least one of the parameters mentioned in step 1 including for example load or load level report per the RF power amplifier for DL and UP on control channel, per the RF power amplifier for DL and UP on data bear channel, per server, per air-conditioner at a cite, per air-conditioner at a data centre.

[0086] - Energy usage entity - this is the network entity for which the energy usage or energy levels report is applicable. Such energy usage entity may have different granularity. It may be the whole network, one or more Network Functions, one or more S-NSSAIs or one or more PDU Sessions. The energy usage entity may also be the UE 3, for example the AF 201 may allocate certain amount of energy credits per a UE or user in order for the network to control and limit the amount of the energy used by the network to deliver services to the UE 3. The Energy usage entity may indicate the NF(s) or network entity related to the Energy usage report. The Energy usage entity may indicate the NF(s) or network entity which reports the Energy usage report.

[0087] - Location - It is possible that the reports for energy usage levels or energy usage for the network entities or network slices are required for network entities in specific location. If so, the EECF 78 provides a location information for which the reporting is applicable. The Location may indicate location related to the Energy usage report. The Location may indicate location where the Energy usage report is made.

[0088] - PLMN ID - In case the 5GS is shared by more than one PLMN then the energy report will contain PLMN ID of the PLMN for which energy request was made. It may also contain RAT type e.g. NR or E-UTRAN. PLMN ID may indicate PLMN ID related to the Energy usage report.

[0089] For example, "Reporting threshold may define the amount of the energy usage and energy efficiency monitoring information. In a case where the amount of the energy usage and energy efficiency monitoring information which is collected by the EECF 78 in step 6 exceeds the amount defined by the Reporting threshold, the EECF 78 may send the Neecf_EnergyUsageExposure_Notify message to the NEF 79. 　　For example, the EECF 78 may send the Neecf_EnergyUsageExposure_Notify message to the NEF 79 regardless of the condition on the Reporting threshold or the condition on the Reporting period.

[0090] Step 8. The NEF 79 forwards the receive reporting information from the EECF 78 to the AF 201 in Nnef_EventExposure_Notify message. 　　The Nnef_EventExposure_Notify message includes the received reporting information in the received Neecf_EnergyUsageExposure_Notify message in Step 7.

[0091] In case that the NEF 79 is subscribed to multiple EECFs 78 in step 3, the NEF 79 waits all Neecf_EnergyUsageExposure_Notify message to come from invoked EECFs 78. Once all of them are received, the NEF 79 compiles the received information and generates a single Nnef_EventExposure_Notify message including the compiled information. 　　In a case where the NEF 79 is subscribed to multiple EECFs 78, each time the Neecf_EnergyUsageExposure_Notify message is received, the NEF 79 may send the Nnef_EventExposure_Notify message without the compiling.

[0092] Variant 1 of First Example of the First Aspect 　　In one example, if the EECF 78 resides in the NEF 79 (e.g., the EECF 78 is embedded in the NEF 79), steps 3, 4 and 7 in Fig. 1 are discarded and not executed.

[0093] Variant 2 of First Example of the First Aspect 　　In another example, the Energy usage / efficiency report may include information about what part of the used energy is a green energy, e,g, a renewable energy. The green energy may be expressed as a percentage of the whole used energy or in terms energy credit units or Joule or Watts per hour.

[0094] Variant 3 of First Example of the First Aspect 　　In one example, the UDM 75 stores a user consent for each subscriber whether an energy consumption or an energy efficiency report related to the user signaling or PDU session(s) is allowed to be reported by a NF or a RAN 5 to the AF 201 or EECF 78. The user consent parameter is sent: - to the NF (e.g., AMF 70) or EECF 78 during Registration procedure or any other existing procedure involving signalling with the UDM 75 in an existing message or in a new message between the UDM 75 and the NF or - to the NF (e.g., SMF) during a PDU session establishment procedure or PDU session modification procedure or in any other existing procedure involving signalling with the UDM 75 in an existing message or in a new message between the UDM 75 and NF.

[0095] Second Example of the First Aspect 　　Fig. 2 illustrates a mechanism for energy usage parameters provision by a 3rdparty Service Provider in a granularity way. It is assumed that a NF will be designated as energy efficiency monitoring and controlling entity in the network with the purpose for monitoring and controlling the energy usage / saving in the network and in the Network Functions. This energy efficiency monitoring and controlling entity may be a new NF called, for example, Energy Efficiency Control Function (EECF 78) or any other name for an entity for the purpose of energy usage monitoring, evaluation and control in the network and in the Network Functions and network slices. The EECF 78 may also be embedded within an existing NFs like O&M, NWDAF, PCF, NEF, NSACF, UDM, NSACF or any other existing or new NF. Fig. 2 below discloses an energy usage parameters provision and update by AF 201 in the network at different granularity levels, e.g. network level, NF level, S-NSSAI level, PDU Session level, UE level and etc.

[0096] The detailed processes of the Second example of the First Aspect are described below, with reference to Fig. 2.

[0097] Step 1. The AF 201 may decide to provide or update one or multiple parameters related to the energy usage monitoring and control in the network or a network slice by providing or updating (e.g. top-up) the energy credits allocated to the whole network or to one or more Network Functions (NF) or other network entities like network slices, network slice and DNN combination, or DNN, PDU sessions and etc. For example, the AF 201 may decide to update the load threshold used by the 3GPP system used in decisions for energy saving modes or energy saving states activation and deactivation in one or more NFs or network slices. In another example, the AF 201 may provide or update the energy credit / limit per network entity like NF or one or more NFs or network slice or network slice and DNN combination or PDU Session and etc. The AF 201 may also allocate energy credit per UE, meaning what amount energy in energy units a certain UE is allowed to use for specific time for example.

[0098] The energy credit may indicate the amount of energy that the UE(s) or NF(s) is allowed to use. 　　The energy credit may indicate the amount of energy that user(s) is allowed to use. 　　The energy credit may indicate the amount of energy available for a network slice. 　　The energy credit may indicate the amount of energy available for network slice and DNN combination. 　　The energy credit may indicate the amount of energy available for PDU Session.

[0099] Step 2. The AF 201 makes use of the Nnef_EnergyUsageParameter_Update Request service operation in which the AF 201 may include the following parameters: - Energy usage entity - this is the network entity for which the energy usage or energy levels control and report is required. The Energy usage entity may have different granularity. It may be the whole network, one or more Network Functions including the RAN node, one or more S-NSSAIs or one or more PDU Sessions or QoS ID or combination of network slice and DNN. The Energy usage entity may also be the UE, for example, the AF 201 may allocate certain amount of energy credits per a UE or user in order for the network to control and limit the amount of the energy used by the network to deliver services to the UE. In case that the Energy usage entity is the UE, a UE or a list of UEs is defined by a separate parameter "UEs" as mentioned below. For example, one or more UEs may be defined by the Energy usage entity or the "UEs" parameter. In case that the energy usage entity is S-NSSAI, S-NSSAI or a list of S-NSSAI(s) is defined by a separate parameter "S-NSSAIs" as mentioned below. For example, one or more S-NSSAI(s) may be defined by the Energy usage entity in the "S-NSSAIs" parameter. In case that energy usage entity is S-NSSAI and a DNN, S-NSSAI and DNN or a list of S-NSSAI(s) and DNN is defined by a separate parameter "S-NSSAI and DNN combination" as mentioned below. In case that energy usage entity is the QoS ID, QoS ID or a list of QoS IDs is defined by a separate parameter "QoS ID" as mentioned below. In case that energy usage entity is the APP ID, APP ID or a list of APP IDs is defined by a separate parameter "APP ID" as mentioned below. In case that the energy usage entity is the PDU Session, PDU Session or a list of PDU Session(s) is defined by a separate parameter "PDU Sessions" as mentioned below. For example, one or more PDU Session s may be defined by the Energy usage entity or the "PDU Sessions" parameter.

[0100] - energy saving state - refers to the energy saving state which indicates whether the energy usage and energy efficiency monitoring in the energy usage entity is activated or deactivated. The energy saving state in EECF 78 and in NFs may be called as EnergySavingState if activated or NotEnergySavingState if deactivated. EnergySavingState may indicate that the energy usage and energy efficiency monitoring is activated in the EECF 78 or the NF(s). EnergySavingState may indicate that the EECF 78 or the NF(s) needs to operate in less energy. NotEnergySavingState may indicate that the energy usage and energy efficiency monitoring is not activated or is deactivated in the EECF 78 or the NF(s). NotEnergySavingState may indicate that the EECF 78 or the NF(s) does not need to operate in less energy. NotEnergySavingState may indicate that the EECF 78 or the NF(s) can operate normally (i.e., can operate by consuming the energy as usual). NotEnergySavingState may refer to a situation that is not EnergySavingState. NotEnergySavingState may refer to the situation where the EECF 78 or the NF(s) operates in a state that is not EnergySavingState.

[0101] - energy credit - the energy credit is the amount of energy defined, for example, in energy credit units, which is allocated to the energy usage entity (e.g., NF(s), the network entity etc.). The energy usage entity may be in a granularity of the whole network or a part of the network like one or more NFs including the RAN node, one or more network slices or one or more PDU Sessions. The energy credit may also be allocated per UE or per user, for example the AF 201 may allocate certain amount of energy credits per a UE or per user in order for the network to control and limit the amount of the energy used by the network to deliver services to the UE or the user.

[0102] - Energy threshold - the AF may provide energy thresholds in the form of energy units, for example, per energy usage entity which could be for the whole network, for one or more NFs including RAN node and the UE, for one or more network slices or for one or more PDU Sessions. The energy threshold may also be in the form of a load level per the energy usage entity. The energy threshold is used for energy usage control in the network. For example, the energy usage entity may be used for switching between energy saving mode and non-energy saving mode or switching between energy saving state and non-energy saving state, for example or as a trigger for energy usage or energy credits reporting to the AF 201 and etc.

[0103] - Validity - It is possible that some or all of the parameters being provided by the AF 201 come with validity conditions or restrictions. Such conditions may be the location, meaning the provided parameters are valid only in the provided location. The location information may be provided as a geographical location which later is mapped to 3GPP compatible location by the UDM 75 like cell ID, TAI and etc. If location information is provided within the validity parameter, the provided energy saving parameters are applicable only in the locations defined by the validity parameter. In another example, the validity condition may be the time. In this case it is possible that some or all of the energy saving or controlling parameters being provided to the 3GPP system by the AF 201 are valid for a specific time duration or in a specific time window.

[0104] - Energy usage / efficiency report request - or any other notation for a parameter with the purpose to indicate a subscription for energy usage / efficiency monitoring and reports. Refer to step 1 in Fig. 1 for parameter details.

[0105] - Location - Refer to step 1 in Fig. 1 for parameter details. - PDU Sessions - Refer to step 1 in Fig. 1 for parameter details. - S-NSSAIs - Refer to step 1 in Fig. 1 for parameter details. - UEs - Refer to step 1 in Fig. 1 for parameter details. - APP ID- Refer to step 1 in Fig. 1 for parameter details. - DNN combination (e.g., S-NSSAI and DNN combination) - Refer to step 1 of Fig. 1 for parameter details. - QoS ID- Refer to step 1 of Fig. 1 for parameter details.

[0106] If the NEF 79 provides a general City name, zip-code, formed with GPS location or a location expressed with civic and geospatial location formats as defined in IETF RFC 5580 [8] or another geographical location information (for example GPS), the UDM 75 converts it to a 3GPP location like a Cell, a list of Cell Id, TAI or a list of TAI and provides them to the NEF 79.

[0107] Step 3. The NEF 79 may interact with the UDM 75 in order to authorize the AF 201 for the requested service of parameters provision for energy usage monitoring and control. If location information was provided from the AF 201, the NEF 79 provides to the EECF 78 the 3GPP mapped location. If GPSI or MSISDN or IMEI was provided by the AF 201, the NEF 79 provides, to the EECF 78, a SUPI that is converted by the UDM 75.

[0108] In one example, the UDM 75 may provide one or multiple EECFs 87 that the NEF 79 may contact for the energy usage parameters provision and update. In this case, a name, FQDN or IP address of the EECF 87 may be provided to the NEF 79. 　　For example, the UDM 75 may indicate, to the one or multiple EECFs 87, that the NEF 79 may contact the one or multiple EECFs 87 for the energy usage and energy efficiency monitoring. In this case, the UDM 75 may provide a name, FQDN or IP address of the EECF 87 to the NEF 79.

[0109] Step 4. The NEF 79 confirms the energy saving parameters provision by the AF 201 with the Nnef_EnergyUsageParameter_Update Response. 　　For example, in a case where the NEF 79 receives at least one of the parameters in step 2, the NEF 79 may send the response to the AF 201. For example, the NEF 79 sends acknowledgement message responds to the Nnef_EnergyUsageParameter_Create / Update Request message which the NEF 79 receives from the AF 201 in the step 2.

[0110] Step 5. The NEF 79 forwards parameters provided by the AF 201 to the EECF 78 with or by using the Neecf_EnergyUsageParameter_Update Request service operation. 　　For example, the NEF 79 may send, to the EECF 78, Neecf_EnergyUsageParameter_Update Request message including the parameters provided by the AF 201.

[0111] Step 6. The EECF 78 evaluates the request from the NEF 79 in Step 5 and checks whether the EECF 78 has enough subscriptions to NFs to comply to the request. 　　If the EECF 78 needs more the energy usage and energy efficiency monitoring information or needs to update parameters to existing subscribed service, the EECF 78 may additionally subscribe to NFs or updates current subscribed information in NFs to collect energy usage and efficiency information based on the new request. 　　For example, the EECF 78 triggers the processes as disclosed by the Second Aspect in this disclosure to collect more energy usage and efficiency information or to update current subscribed information in NFs.

[0112] Variant 1 of Second Example of the First Aspect 　　In one example, the EECF 78 in Fig. 2 may be implemented as a functionality embedded in a NF, e.g. embedded in RAN, AMF, SMF, UPF, PCF, UDM, NSACF, NWDAF, NRF and etc. In this case the NEF 79 in step 5 forwards the received energy saving and controlling parameters from the AF 201 to one or multiple NFs with embedded energy usage control functionality depending on the energy usage entity parameter which defines the destination entity for the energy usage parameters. Then the NF with the embedded energy usage control functionality performs the energy usage monitoring and control actions as described in step 6 and the transitions between the EnergySavingState and NotEnergySavingState are controlled within the NF itself.

[0113] Variant 2 of Second Example of the First Aspect 　　In another example, if the EECF 78 resides in the NEF 79, step 5 in Fig. 2 is discarded and not executed.

[0114] According to at least one of the above Aspects or at least one of the above Variants, for example, it can solve the above-mentioned problem(s). 　　For example, at least one of the above Aspects or at least one of the above Variants can solve the problem that there is no technical solution in the current 3GPP standards for achieving the above description in SP-231192 [NPL5].

[0115] Second Aspect 　　According to SP-231192 [NPL5] agreed at the 3GPP SAP#101 in September 2023, there is a need to study enhancements for subscription and policy control to enable network energy savings as service criteria. 　　However, there is no mechanism in the current 3GPP standards to achieve this need.

[0116] The Second Aspect includes a mechanism for energy usage monitoring and control with granularity of the whole network or one or more NFs including RAN 5, UE 3, network slice and PDU Session.

[0117] First Example of the Second Aspect 　　Fig. 3 illustrates a mechanism for Energy usage monitoring and control. This mechanism is used based on the load level of NF and network slice or network slice and DNN combination. It is assumed that a NF would be designated as energy efficiency monitoring and controlling entity in the network. This energy efficiency monitoring and controlling entity may be a new NF called, for example, Energy Efficiency Control Function (EECF 78) or any other name for the purpose of energy efficiency monitoring and control. The EECF 78 may also be embedded within an existing NF like O&M, PCF, NWDAF, NSACF, UDM or any other existing or new NF. The Fig. 3 below discloses a Network Function energy efficiency / saving control. The NF node in the Fig. 3 may be one of the RAN 5, AMF 70, SMF 71, UPF 72, PCF 73, UDM 75, NSACF 77, NSSF or any other new and existing NF.

[0118] For example, the processes in Fig. 3 may be triggered at step 0 or 6 in Fig. 1 and step 6 in Fig. 2.

[0119] The detailed processes of the First example of the Second Aspect are described below, with reference to Fig. 3.

[0120] Step 1. The EECF 78 may trigger a subscription request via Neecf_NFLoadStatus_Subscribe Request service operation or any other notation for a service operation with the purpose to subscribe with a NF or a network slice for load level information reporting from that NF or a network slice. The NF in Fig. 3 is a representative entity and could be any one of the existing network functions, e.g. RAN node, AMF, SMF, UPF, PCF, UDM, NSACF, NSSF or a network slice. The EECF 78 may include the following parameters in the Neecf_NFLoadStatus_Subscribe Request message:

[0121] - Load level - the load level parameter indicates that the EECF 78 requires subscription for NF or a network slice load levels reporting. The load level may be expressed in percentage or in any other expression which reveals how busy the reporting entity is. The reported load level can be about the load level of the NF or about the load level of one or more S-NSSAIs if for example the reporting NF is the NSACF or the NWDAF.

[0122] - S-NSSAIs - if the reporting NF is the NSACF or the NWDAF or the network slice itself, the EECF 78 may enquire the load level of one or more network slices. In this case the EECF 78 may include in the subscription request one or more S-NSSAIs for which load lever reporting is required.

[0123] - Reporting mode - the reporting mode defines whether load level of the network entity or S-NSSAI is to be reported event based (e.g. threshold based) or periodically.

[0124] - Load threshold - when event-based load reporting is required, the EECF 78 provides one or more load thresholds. In this case the load reporting in the NF or S-NSSAI is triggered when the load levels in the NF or in the S-NSSAI crosses the provided load threshold. For example, when the load level of the NF or of the S-NSSAI drops to or is below the provided load threshold, the NF or the S-NSSAI (e.g., the NSACF or the NWDAF or the OAM or the any other NF which may monitor and control the load information for the S-NSSAI) will report its load level to the EECF 78. The NF or the S-NSSAI (e.g. the NSACF or the NWDAF or the OAM or the any other NF which may monitor and control the load information for the S-NSSAI) may report the load level also when the load level of the NF or of the S-NSSAI crossed back the load threshold, i.e. the load level of the NF or the S-NSSAI becomes higher that the provided load threshold.

[0125] - Reporting period - when load reporting is required periodically, the EECF 78 may include a reporting period parameter. In this case the NF would trigger load reporting each time the reporting period expires. - System type - This IE indicates whether the load level reporting is required from NFs of 5GS or 6GS or EPS.

[0126] - RAT type - RAT type indicates the load level reporting related to 3GPP RAT (e.g. NR or E-UTRAN) or non-3GPP RAT. The RAT type may be expressed as RAN type. - DNN (Domain Network Name): load level reporting for a particular DNN.

[0127] - PLMN ID - In case the 5GS is shared among multiple PLMN, then the PLMN ID or list of PLMN IDs are sent to report the load level related to the PLMN or the list of PLMN. - QoS ID - request to report the energy consumption as per the QoS ID defined in the 3GPP TS 24.501.

[0128] - APP ID - request to report the energy consumption by application identified by an application identity. The application identity for an application is defined in 3GPP TS 24.501 [NPL8]. One example, APP ID may be referred as OS specific Application Identifier (OSAppId) as defined in 3GPP TS 23.503 [NPL9]. One another example, APP ID may be referred as OS ID + APP ID.

[0129] In this disclosure, the S-NSSAI may mean the network slice indicated by the S-NSSAI, or NF(s) in the network slice indicated by the S-NSSAI.

[0130] Step 2. The NF confirms the subscription for load reporting with the Neecf_NFLoadStatus_Subscribe Response message. 　　For example, in a case where the NF receives the parameters in step 1, the NF may send the response to the EECF 78. For example, the NF may send acknowledgement message corresponds to the message which the NF receives from the EECF 78 in Step 1.

[0131] Step 3. Based on the reporting mode (periodic or threshold based) the NF triggers a notification to report the current load level of the NF or the S-NSSAI. For example, if the subscription is for event-based reporting and the load level of the network function or the S-NSSAI drops to or below the provided load threshold, the NF triggers load reporting to the EECF 78. The NF may also report when the load level of the NF or the S-NSSAI crosses back the threshold, i.e. the load level of the NF or the S-NSSAI becomes equal or higher than the load threshold. In another example, if the subscription is for periodic reporting, the NF triggers the load levels reporting for the NF or for the S-NSSAI with a periodicity provided by the EECF 78 in the subscription with the reporting period parameter.

[0132] Step 4. The NF sends Neecf_NFLoadStatus_Notification message in which the NF includes its current level of load if the reporting is about the NF load or the load level of an S-NSSAI if the reported load level is about an S-NSSAI which can be represented in percentage or in any other expression of how busy the NF or the S-NSSAI is. When the reported load level is for an S-NSSAI, the NF also include the S-NSSAI in the Neecf_NFLoadStatus_Notification message to the EECF 78.

[0133] The level of load may be related to S-NSSAI(s) which is defined by the "S-NSSAIs" parameter. 　　The level of load may be related to system type which is defined by the "system type" parameter. 　　The level of load may be related to RAT type which is defined by the "RAT type" parameter. 　　The level of load may be related to DNN which is defined by the "DNN" parameter. 　　The level of load may be related to PLMN which is defined by the "PLMN ID" parameter. 　　The level of load may be related to QoS ID which is defined by the "QoS ID" parameter. 　　The level of load may be related to the application which is defined by the "APP ID" parameter.

[0134] Step 5. If the NF reported load level for the NF or for an S-NSSAI has fallen to or below a load threshold value for that NF or for a S-NSSAI (the load threshold value may be configured in the EECF 78 by the operator or provided or retrieved by the EECF 78 from another NF like NWDAF or UDM or O&M or provided by the AF via the NEF), the EECF 78 may request the NF or the S-NSSAI (e.g. the NSACF or the NWDAF or the OAM or the any other NF which may monitor and control the S-NSSAI) to move to EnergySavingState, meaning the NF or the S-NSSAI (e.g. the network slice indicated by the S-NSSAI, or NF(s) in the network slice indicated by the S-NSSAI) now is not busy and it can switch to EnergySavingState and consume less energy. Otherwise, if the NF reported load level for the NF or for S-NSSAI has increased to or above a load threshold value for that NF or for a S-NSSAI, the EECF 78 may request the NF or the S-NSSAI (e.g. the network slice indicated by the S-NSSAI, or NF(s) in the network slice indicated by the S-NSSAI) to move to an NotEnergySavingState, meaning the NF or the S-NSSAI now is busy and it can switch to NotEnergySavingState so that the NF or the S-NSSAI can provide the expected service although the energy usage would be high.

[0135] In a case where the level of load is related to the system type, RAT type, DNN, PLMN, QoS ID, or the application mentioned in step 4, the load threshold value may be related to the system type, RAT type, DNN, PLMN, QoS ID, or the application. In this case, the EECF 78 may request the NF or the S-NSSAI to move to EnergySavingState or NotEnergySavingState based on the comparison of the load level and the load threshold in the same manner as the step 5 above.

[0136] Step 6. The EECF 78 sends Neecf_EnergyEfficiency_Control Request message to the NF in order to switch the NF or the S-NSSAI between EnergySavingState and NotEnergySavingState. For example, to switch the NF or S-NSSAI to EnergySavingState, the EECF 78 includes the EnergySavingState activation parameter in the Neecf_EnergyEfficiency_Control Request message. If the EECF 78 wants to switch the NF or S-NSSAI to NotEnerguSavingState, the EECF 78 includes the NotEnergySavingState activation parameter in the Neecf_EnergyEfficiency_Control Request message.

[0137] Step 7. The NF or the S-NSSAI activates the requested energy saving mode i.e. EnergySavingState or NotEnergySavingState with further actions specific to this NF or S-NSSAI functioning in the new energy saving state.

[0138] Variant 1 of First Example of the Second Aspect 　　In one example, each NF and S-NSSAI in the network may be allocated with energy credits represented in energy credit units as per the solution for parameters provision and update via O&M or AF in Fig. 2. In this case in Step 1 of Fig. 3 the EECF 78 may subscribe with a NF or S-NSSAI for reporting the amount of the current energy credit of the NF or the S-NSSAI instead of the load levels. If so, the EECF 78 may provide in step 1 of Fig. 3 to the NF energy credit level parameter instead of the load level parameter and also provide an energy credit threshold parameter instead of the load threshold parameter. The EECF 78 may also provide what part of the available energy credit or what part of the used energy credit come from green energy source, e.g, what part of the still available or green energy is renewable energy. Then, in step 4 of Fig. 3 the NF may report the current energy credit units, e.g. the remaining energy credit units of the NF or of the S-NSSAI to the EECF 78. In step 5 of Fig. 3 the EECF 78 may compare the energy credit units reported by the NF in step 4 with the energy credit thresholds available in the EECF 78 in order to switch the NF or the S-NSSAI between the EnergySavingState and NotEnergySavingState. For example, if the NF reported energy credit units level available for the NF or for an S-NSSAI has fallen to or is below the energy credit threshold value for that NF or for that S-NSSAI (the energy credit threshold value may be configured in the EECF 78 by the network operator or provided or retrieved by the EECF 78 from another NF like NWDAF or UDM or O&M or provided by the AF 201 via the NEF 79), the EECF 78 may request the NF or the S-NSSAI to move to EnergySavingState, meaning the NF or the S-NSSAI now is with low energy credit available to it and it can switch to EnergySavingState and consume less energy. Otherwise, if the NF reported energy credit units level for the NF or of an S-NSSAI has increased to or above the energy credit threshold value for that NF or for that S-NSSAI, the EECF 78 may request the NF to move to an NotEnergySavingState, meaning the NF or the S-NSSAI now have enough energy credit available to them so, they can switch to NotEnergySavingState so that the NF or the S-NSSAI can provide the full expected services.

[0139] Second Example of the Second Aspect 　　Fig. 4 illustrates a mechanism for Energy usage monitoring and control based on the NF load levels with assistance from the NWDAF. It is assumed that a NF will be designated as energy efficiency monitoring and controlling entity in the network. This energy efficiency monitoring and controlling entity may be a new NF called, for example, Energy Efficiency Control Function (EECF 78) or any other name for the purpose of energy efficiency monitoring and control. The EECF 78 may also be embedded within an existing NF like O&M, PCF, NWDAF, NSACF, UDM or any other existing NF. Fig. 4 below discloses a Network Function energy efficiency / saving control with NWDAF assistance. The NF node in Fig. 4 may be one of the RAN 5, AMF 70, SMF 71, UPF 72, PCF 73, UDM 75, NSACF 77, NSSF or any other new and existing NF.

[0140] For example, the processes in Fig. 4 may be triggered at step 0 or 6 in Fig. 1 and step 6 in Fig. 2.

[0141] The detailed processes of the Second example of the Second Aspect are described below, with reference to Fig. 4.

[0142] Step 1. The EECF 78 may trigger a subscription request to the NWDAF 74 via Neecf_NFLoadStatus_Subscribe Request service operation or any other notation for a service operation with the purpose to subscribe with the NWDAF 74 for load level information reporting from one or more NFs or S-NSSAIs. The EECF 78 may include the following parameters in the Neecf_NFLoadStatus_Subscribe Request message:

[0143] - Load level - the load level parameter indicates that the EECF 78 requires subscription for load levels reporting. The load level may be expressed in percentage or in any other expression which reveals how busy the reporting entity is. The reported load level can be about the load level of the NF or about the load level of one or more S-NSSAIs. - NF ID - the identity of the NF, e.g. RAN node, AMF, SMF, UPF, PCF, UDM, NSACF, NSSF and etc) for which a load level report is required.

[0144] - S-NSSAIs - one or more network slice identity for which a load level report is required. - Reporting mode - the reporting mode defines whether load level of the network entity or S-NSSAI is to be reported event based (e.g. threshold based) or periodically.

[0145] - Load threshold - when event-based load reporting is required, the EECF 78 provides one or more load thresholds. In this case the load reporting in the NWDAF 74 is triggered when the load levels in a NF or the S-NSSAI crosses the provided load threshold. For example, when the load level of the NF or S-NSSAI drops to or is below the provided load threshold, the NWDAF 74 will report the load level to the EECF 78. The NWDAF 74 may report the load level also when the load level of the NF or the S-NSSAI crosses back the load threshold, i.e. the load levels of the NF or the S-NSSAI become higher that the provided load threshold. It is supposed that the NWDAF 74 has subscribed with one or more NF and S-NSSAIs for load level reporting and the NWDAF 74 has the load information on these NF and S-NSSAIs available to provide to the EECF 78.

[0146] - Reporting period - when load reporting is required periodically, the EECF 78 may include a reporting period parameter. In this case the NWDAF 74 would trigger load reporting each time the reporting period expires.

[0147] Step 2. The NWDAF 74 confirms the subscription for load reporting with the Neecf_NFLoadStatus_Subscribe Response message. 　　For example, in a case where the NWDAF 74 receives at least one of the parameters in step 1, the NWDAF 74 may send the response to the EECF 78. For example, the NWDAF 74 may send acknowledgement message corresponds to the message which the NWDAF 74 receives from the EECF 78 in Step 1.

[0148] Step 3. Based on the reporting mode (periodic or threshold based) the NWDAF 74 triggers a notification to report the current load level of the NF or of the S-NSSAI for which the EECF 78 has subscribed. For example, if the subscription is for event based reporting and the load level of the NF or an S-NSSAI drops to or below the provided load threshold, the NWDAF 74 triggers load reporting to the EECF 78. The NWDAF 74 may also report when the load level of the NF or an S-NSSAI crosses back the threshold, i.e. the load level of the NF or the S-NSSAI becomes equal or higher than the load threshold. In another example, if the subscription is for periodic reporting, the NWDAF 74 triggers the load levels reporting for the NF or for the S-NSSAI with a periodicity provided by the EECF 78 in the subscription with the reporting period parameter.

[0149] Step 4. The NWDAF 74 sends Neecf_NFLoadStatus_Notification message in which the NWDAF 74 includes the current level of load for the NF or for the NSSAI. The NWDAF 74 also includes in the Neecf_NFLoadStatus_Notificatin message to the EECF 78 the NF ID or the network slice identity such as S-NSSAI for which the reported load level is applicable.

[0150] Step 5. If the NWDAF 74 reported load level for a NF or for an S-NSSAI has fallen to or below a load threshold value for that NF or for a S-NSSAI (the load threshold value may be configured in the EECF 78 by the network operator or provided or retrieved by the EECF 78 from another NF like UDM or O&M or provided by the AF via the NEF), the EECF 78 may request the NF or the S-NSSAI to move to EnergySavingState, meaning the NF or the S-NSSAI now is not busy and it can switch to EnergySavingState and consume less energy. Otherwise, if the NF reported load level for the NF or for a S-NSSAI has increased to or above a load threshold value for that NF or for a S-NSSAI the EECF 78 may request the NF to move to NotEnergySavingState, meaning the NF or the S-NSSAI now is busy and it can switch to NotEnergySavingState so that the NF or the S-NSSAI can provide the expected quality service although the energy usage would be high.

[0151] Step 6. The EECF 78 sends Neecf_EnergyEfficiency_Control Request message to the NF (which could be any one of the existing network functions, e.g. RAN node, AMF, SMF, UPF, PCF, UDM, NSACF, NSSF.) in order to switch the NF or the S-NSSAI between EnergySavingState and NotEnergySavingState. For example, to switch the NF or an S-NSSAI to EnergySavingState, the EECF 78 includes the EnergySavingState activation parameter in the Neecf_EnergyEfficiency_Control Request. If the EECF 78 wants to switch the NF or an S-NSSAI to NotEnerguSavingState, the EECF 78 includes the NotEnergySavingState activation parameter in the Neecf_EnergyEfficiency_Control Request message.

[0152] Step 7. The NF or the S-NSSAI activates the requested energy saving mode i.e. EnergySavingState or NotEnergySavingState with further actions specific to this NF or S-NSSAI functioning in the new energy saving state.

[0153] Variant 1 of Second Example of the Second Aspect 　　In one example, each NF and S-NSSAI in the network may be allocated with energy credits represented in energy credit units as per the solution for parameters provision and update via O&M or AF in Fig. 2. In this case in Step 1 of Fig. 4 the EECF 78 may subscribe with the NWDAF 74 for reporting the amount of the current energy credit of a NF or of S-NSSAI or S-NSSAI and DNN combination or DNN instead of the load levels. If so, the EECF 78 may provide in step 1 of Fig. 4 to the NWDAF 74 energy credit level parameter instead of load level parameter and also provide energy credit threshold parameter instead of the load threshold parameter. Then, in step 4 of Fig. 4 the NWDAF 74 may report the current energy credit units, e.g. the remaining energy credit units of a NF or of the S-NSSAI to the EECF 78 instead of the load level. In step 5 of Fig. 4 the EECF 78 may compare the energy credit units reported by the NWDAF 74 for a NF or for S-NSSAI in step 4 with the energy credit thresholds available in the EECF 78 in order to switch the NF or the S-NSSAI between the EnergySavingState and NotEnergySavingState. For example, if the NWDAF 74 reported energy credit units level available for a NF or for an S-NSSAI has fallen to or is below the energy credit threshold value for that NF or for a S-NSSAI (the energy credit threshold value may be configured in the EECF 78 by the network operator or provided or retrieved by the EECF 78 from another NF like NWDAF 74 or UDM 75 or O&M or provided by the AF via the NEF), the EECF 78 may request the NF or the S-NSSAI to move to EnergySavingState, meaning the NF or the S-NSSAI now is with low energy credit available to it and it can switch to EnergySavingState and consume less energy. Otherwise, if the NWDAF 74 reported energy credit units level for a NF or for a S-NSSAI has increased to or above the energy credit threshold value for that NF or for that S-NSSAI, the EECF 78 may request the NF to move to an NotEnergySavingState, meaning the NF or the S-NSSAI now have enough energy credit available to them so, they can switch to NotEnergySavingState so that the NF or the S-NSSAI can provide the full quality expected services.

[0154] Third Example of the Second Aspect 　　Fig. 5 illustrates a mechanism for Energy usage monitoring and control. The EECF 78 may initiate this process to one or multiple Energy usage entities that are required to energy usage and energy efficiency monitoring. 　　For example, in a case where the energy usage and energy efficiency monitoring are required for a PDU Session or for both Control plane and User plane, the EECF 78 may initiate this process at least twice one for the SMF 71 associated with the PDU Session and the other one for the UPF 72 associated with the PDU Session.

[0155] This energy efficiency monitoring and controlling entity may be a new NF called, for example, Energy Efficiency Control Function (EECF 78) or any other name for the purpose of energy efficiency monitoring and control. The EECF 78 may also be embedded within an existing NF like O&M, PCF, NWDAF, NSACF, UDM or any other existing NF. The Fig. 5 below discloses a Network Function energy efficiency / saving control. The NF node in the Fig. 5 may be one of the RAN 5, AMF 70, SMF 71, UPF 72, PCF 73, UDM 75, NSACF 77, NSSF or any other new and existing NF.

[0156] For example, the processes in Fig. 5 may be triggered at step 0 or 6 in Fig. 1 and step 6 in Fig. 2.

[0157] The detailed processes of the Third example of the Second Aspect are described below, with reference to Fig. 5.

[0158] Step 1. The EECF 78 invokes Nxxx_EnergyUsageExposure_Subscribe Request Service to an Energy usage entity (e.g., NF which performs the energy usage or for energy status reporting) including Energy usage request reference ID, energy usage report required, energy usage entity, reporting mode, reporting threshold, reporting period, location, PDU session IDs, S-NSSAIs and UEs. 　　Refer to step 1 in Fig. 1 for parameter details.

[0159] For example, the EECF 78 may send Nxxx_EnergyUsageExposure_Subscribe Request message including Energy usage request reference ID, energy usage report required, energy usage entity, reporting mode, reporting threshold, reporting period, location, PDU session IDs, S-NSSAIs and UEs. 　　The Nxxx_EnergyUsageExposure_Subscribe Request message may include at least one of the parameters mentioned in step 1 in Fig. 1.

[0160] The EECF 78 may invoke multiple Nxxx_EnergyUsageExposure_Subscribe Request Service to Energy usage entities in case one of the following conditions met: - The EECF 78 receives plural NFs as the energy usage entity (e.g., the EECF 78 receives one or more "Energy usage entity" parameters). - The EECF 78 receives one or more UEs (e.g., the EECF 78 receives one or more "UEs" parameters) and UEs (e.g., UE(s) indicated by the "UEs" parameters) are spread to multiple AMFs 70. For example, the EECF 78 may know which UE(s) belongs or registers which AMF in advance. For example, the "UEs" parameter may indicate the UE(s) indicated by the "UEs" parameter belongs which AMF.

[0161] - The EECF 78 receives one or more PDU Session IDs (or one or more PDU Sessions) and PDU Session IDs (e.g., PDU Session(s) indicated by the "PDU Session IDs" or "PDU Sessions" parameter) are spread to multiple AMFs 70, SMFs 71 and UPFs 72. For example, the EECF 78 may know which PDU Session(s) is related to which AMF(s), SMF(s) and UPF(s) in advance. For example, the "PDU Session IDs" or "PDU Sessions" parameter may indicate the PDU Session(s) indicated by the "PDU Session IDs" or "PDU Sessions" parameter is related to which AMF(s), SMF(s) and UPF(s). For example, the "PDU Session IDs" or "PDU Sessions" parameter may indicate on which AMF(s), SMF(s) and UPF(s) the PDU session indicated by the "PDU Session IDs" or "PDU Sessions parameter is established.

[0162] - The EECF 78 receives one or more S-NSSAIs and S-NSSAIs (e.g., network slice(s) indicated by S-NSSAIs) are spread to multiple AMFs 70, SMFs 71 and UPFs 72. For example, the EECF 78 may know which S-NSSAI is related to which AMF(s), SMF(s) and UPF(s) in advance. For example, the "S-NSSAIs" parameter may indicate the network slice indicated by the "S-NSSAIs" parameter is related to which AMF(s), SMF(s) and UPF(s).

[0163] - The EECF 78 receives one or more locations and locations are spread to multiple AMFs 70. For example, the EECF 78 may know location indicated by the "location" parameter is related to which AMF(s) in advance. For example, the "Location" parameter may indicate the location indicated by the "Location" parameter is related to which AMF(s).

[0164] - The EECF 78 receives one or more S-NSSAI and DNN combinations and one S-NSSAI and DNN combination or list of S-NSSAI and DNN combination(s) is spread to multiple AMFs 70, SMFs 71 and UPFs 72. For example, the EECF 78 may know which S-NSSAI or DNN is related to which AMF(s), SMF(s) and UPF(s) in advance. For example, the "S-NSSAI and DNN combination" parameter may indicate the S-NSSAI (or network slice(s) indicated by the S-NSSAI) or DNN is related to which AMF(s), SMF(s) and UPF(s).

[0165] - The EECF 78 receives one or more DNNs and DNNs are spread to multiple AMFs 70, SMFs 71 and UPFs 72. For example, the EECF 78 may know which DNN is related to which AMF(s), SMF(s) and UPF(s) in advance. For example, the "DNN" parameter may indicate the DNN indicated by the "DNN" parameter is related to which AMF(s), SMF(s) and UPF(s).

[0166] - The EECF 78 receives one or more 5G QoS IDs and 5G QoS IDs are spread to multiple AMFs 70, SMFs 71 and UPFs 72. For example, the EECF 78 may know which QoS ID is related to which AMF(s), SMF(s) and UPF(s) in advance. For example, the "QoS ID" parameter may indicate the QoS or ID indicated by the "QoS ID" parameter is related to which AMF(s), SMF(s) and UPF(s).

[0167] If the Energy usage entity is the gNB (or a base station), the Nxxx_EnergyUsageExposure_Subscribe Request message may be sent to the AMF 70 and may be encapsulated as an Energy Efficiency (EE) or Energy usage (EU) container in the NGAP message. The NGAP message may be NG Setup response message, RAN Configuration Update Acknowledge message, AMF Configuration Update message or any existing or new RANAP messages. The NGAP message may be sent to the base station.

[0168] Note that "xxx" in the Nxxx_EnergyUsageExposure_Subscribe Request Service implies the node name. For example, if the NF is an AMF 70, "xxx" is equal to AMF. For another example, if the NF is an SMF 71, "xxx" is equal to SMF.

[0169] Step 2. The NF sends the Nxxx_EventExposure_Subscribe Response message to the EECF 78. 　　If the Energy usage entity is the gNB, the Nxxx_EventExposure_Subscribe Response message may be encapsulated as an EE response container in the NGAP message and sent to the AMF 70. Then, the AMF 70 forwards the received NGAP message to the EECF 78. The NGAP message may be NG Setup message, RAN Configuration Update message, AMF Configuration Update Acknowledge message or any existing or new RANAP messages.

[0170] Note that "xxx" in the Nxxx_EventExposure_Subscribe Response message implies the node name. For example, if the NF is an AMF 70, "xxx" is equal to AMF. For another example, if the NF is an SMF 71, "xxx" is equal to SMF.

[0171] Step 3. The NF monitors and evaluates the energy usage and efficiency based on the received information in step 1. For example, the NF monitors and evaluates the energy usage and efficiency in the network, possibly per granularity level if required in the subscription by the AF, e.g., per network level, CN level, RAN level, NF level, S-NSSAI level, and PDU session level etc. The NF stores the evaluated energy usage and efficiency information for reporting, to the EECF 78 for example, in periodic or event-based mode depending on the EECF 78 subscription.

[0172] Step 4. When the Reporting period is met for the energy usage and energy efficiency monitoring, the NF sends the Nxxx_EnergyUsageExposure_Notify message to the EECF 78 including Energy usage request reference ID, energy usage report, energy usage entity and location. 　　Refer to step 7 in Fig. 1 for parameter details. 　　The NF may send the Nxxx_EnergyUsageExposure_Notify message regardless of the Reporting period.

[0173] Upon receiving the Nxxx_EnergyUsageExposure_Notify message from the NF, the EECF 78 may compile the received Nxxx_EnergyUsageExposure_Notify messages from another NF and generates an energy usage report that to be sent to the NEF 79 in step 7 of Fig. 1. In the same manner as at least one of the other aspects, the EECF 78 may send the received Nxxx_EnergyUsageExposure_Notify message without the compiling.

[0174] If the Energy usage entity is the gNB, the Nxxx_EnergyUsageExposure_Notify message may be encapsulated as an EE notify container in the NGAP message and sent to the AMF 70. Then, the AMF 70 forwards the received NGAP message to the EECF 78. The NGAP message may be NG Setup message, RAN Configuration Update message, AMF Configuration Update Acknowledge message or any existing or new RANAP messages.

[0175] Note that "xxx" in the Nxxx_EnergyUsageExposure_Subscribe Request Service implies the node name. For example, if the NF is an AMF 70, "xxx" is equal to AMF. For another example, if the NF is an SMF 71, "xxx" is equal to SMF.

[0176] Fourth Example of the Second Aspect 　　Fig. 6 illustrates a mechanism for Energy usage monitoring and control. The EECF 78 may initiate this process to one or multiple Energy usage entities that are required to energy usage and energy efficiency monitoring.

[0177] This energy efficiency monitoring and controlling entity may be a new NF called, for example, Energy Efficiency Control Function (EECF 78) or any other name for the purpose of energy efficiency monitoring and control. The EECF 78 may also be embedded within an existing NF like O&M, PCF, NWDAF, NSACF, UDM or any other existing NF. The Fig. 6 below discloses a Network Function energy efficiency / saving control. The NF node in the Fig. 6 may be a base station, the gNB 5, eNodeB or any other new and existing NF in RAN 5.

[0178] For example, the processes in Fig. 6 may be triggered at step 0 or 6 in Fig. 1 and step 6 in Fig. 2.

[0179] The detailed processes of the Fourth example of the Second Aspect are described below, with reference to Fig. 6.

[0180] Step 1. Steps 1 and 2 in Fig. 5 take place with replacing NF with AMF 70.

[0181] Step 2. The AMF 70 sends the Energy Usage reporting control message to the gNB 5 including Energy usage request reference ID, energy usage report required, energy usage entity, reporting mode, reporting threshold, reporting period, location, PDU session IDs, QoS IDs, S-NSSAIs and UEs. 　　Refer to step 1 in Fig. 1 for parameter details.

[0182] The AMF 70 may send multiple Energy Usage reporting control messages to the gNBs 5 in case one of the following conditions met: - The AMF 70 receives plural gNBs as the energy usage entity (e.g., the AMF 70 receives one or more "Energy usage entity" parameters indicating gNBs). - The AMF 70 receives the location information (e.g., a list of TAI) and there are multiple gNB that covers the received location. - The AMF 70 receives the PDU Session IDs and UEs while the UE 3 configures the multi connectivity, and the AMF 70 sends one for MN and the other one for SN (e.g., the AMF 70 may send one Energy Usage reporting control message to the MN and another Energy Usage reporting control message to the SN).

[0183] The Energy Usage reporting control message may be a different NGAP message. For example, NG Setup response message, RAN Configuration Update Acknowledge message, AMF Configuration Update message or any existing or new RANAP messages.

[0184] Step 3. The gNB 5 sends the Energy Usage reporting Response message to the AMF 70.

[0185] The Energy Usage reporting Response message may be a different NGAP message. For example, NG Setup message, RAN Configuration Update message, AMF Configuration Update Acknowledge message or any existing or new RANAP messages.

[0186] Step 4. The gNB 5 monitors and evaluates the energy usage and efficiency based on the received information in step 2. For example, the gNB 5 monitors and evaluates the energy usage and efficiency in the network, possibly per granularity level if required in the subscription by the AF, e.g., per RAN level, NF level, S-NSSAI level, PDU session level, UE level and etc.

[0187] Step 5. When the Reporting period is met for the energy usage and energy efficiency monitoring, the gNB 5 sends the Energy Usage reporting Notify message to the AMF 70 including Energy usage request reference ID, energy usage report, energy usage entity and location. 　　Upon receiving the Energy Usage reporting Notify message from the gNB 5, the AMF 70 may compile the received Energy Usage reporting Notify messages from another gNB 5 and generates an energy usage report that to be sent to the NEF 79 in step 7 of Fig. 1. Refer to step 7 in Fig. 1 for parameter details.

[0188] The gNB 5 may send the Energy Usage reporting Notify message regardless of the Reporting period. 　　In the same manner as at least one of the other aspects, the AMF 70 may send the received Energy Usage reporting Notify message without the compiling.

[0189] The Energy Usage reporting Notify message may be a different NGAP message. For example, NG Setup message, RAN Configuration Update message, AMF Configuration Update Acknowledge message or any existing or new RANAP messages.

[0190] Step 6. Step 4 in Fig. 5 takes place with replacing NF with AMF 70.

[0191] Variant 1 of the Fourth Example of the Second Aspect 　　In one example, based on the energy reporting when the EECF 78 determines that a particular combination including for example at least one of particular UE type (e.g. NB-IoT UEs), S-NSSAI, combination of S-NSSAI and DNN, QoS ID is consuming an energy above some threshold, then the EECF 78 sends a message to the AMF 70 to release the resources related to the UE type or the S-NSSAI or the S-NSSAI and DNN combination or the QoS ID. Upon receiving the message, the AMF 70 releases the DRB or PDU session related to the UE type or the S-NSSAI or the S-NSSAI and DNN combination or the QoS ID. Optionally, the AMF 70 also sends an existing or a new NAS message to the UE(s) 3 including back-off timer related to the S-NSSAI and DNN combination or the QoS ID. When the UE 3 receives the NAS message including the back-off timer associated with the S-NSSAI or the S-NSSAI and DNN combination or the QoS ID, the UE 3 may not send any NAS signaling related to the S-NSSAI or the S-NSSAI and DNN combination or the QoS ID, till back off timer expires. In addition, the AMF 70 sends an existing NGAP message or a new NGAP message to the NG-RAN (or RAN) to perform access control for the S-NSSAI and DNN combination. On receiving the NGAP message the NG-RAN invokes access control in order to restrict the signaling related to the S-NSSAI and DNN combination or the QoS ID.

[0192] When EECF 78 determines that the energy consumption in the network decreases below some threshold, the EECF 78 sends a second message to the AMF 70 to revoke the access control related to the S-NSSAI or the S-NSSAI and DNN combination or the QoS ID. On the receiving the second message the AMF 70 revokes the access control by sending, to the NG-RAN, an existing NGAP message or a new NGAP message to revoke the access control. The NG-RAN on reception of the NGAP message lifts the access control procedure related to or S-NSSAI or the S-NSSAI and DNN combination or the QoS ID.

[0193] Fifth Example of the Second Aspect 　　Fig. 7 illustrates a mechanism for Energy usage monitoring and control. The EECF 78 may initiate this process to one or multiple Energy usage entities that are required to energy usage and energy efficiency monitoring. 　　This energy efficiency monitoring and controlling entity may be a new NF called, for example, Energy Efficiency Control Function (EECF 78) or any other name for the purpose of energy efficiency monitoring and control. The EECF 78 may also be embedded within an existing NF like O&M, PCF, NWDAF, NSACF, UDM or any other existing NF. The Fig. 6 below discloses a Network Function energy efficiency / saving control. The NF node in the Fig. 7 may be a base station, the gNB DU 61, eNodeB or any other new and existing NF in RAN 5.

[0194] For example, the processes in Fig. 7 may be triggered at step 0 or 6 in Fig. 1 and step 6 in Fig. 2.

[0195] The detailed processes of the Fifth example of the Second Aspect are described below, with reference to Fig. 7.

[0196] Step 1. Steps 1, 2 and 3 in Fig. 6 take place with replacing gNB 5 with gNB CU-CP 6201.

[0197] Step 2. The gNB CU-CP 6201 sends the F1 Energy Usage reporting control message to the gNB DU 61 including Energy usage request reference ID, energy usage report required, energy usage entity, reporting mode, reporting threshold, reporting period, location, PDU session IDs, S-NSSAIs and UEs. 　　Refer to step 1 in Fig. 1 for parameter details.

[0198] The gNB CU-CP 6201 may send multiple Energy Usage reporting control messages to the gNB DU 61 in case one of the following conditions met: - The gNB CU-CP 6201 receives plural gNB DUs as the energy usage entity (e.g., the gNB CU-CP 6201 receives one or more "Energy usage entity" parameters indicating gNB DUs). - The gNB CU-CP 6201 receives the location information (e.g., a list of TAI) and there are multiple gNB DU 61 that covers the received location. - The gNB CU-CP 6201 receives the PDU Session IDs and UEs while the UE configures the multi connectivity, and the gNB CU-CP 6201 sends one Energy Usage reporting control message for a gNB DU 61 as MN and another Energy Usage reporting control message for the other gNB DU 61 as SN.

[0199] The F1 Energy Usage reporting control message may be a different F1AP message. For example, F1 Setup response message, GNB-CU CONFIGURATION UPDATE message, GNB-DU CONFIGURATION UPDATE ACKNOWLEDGE message, GNB-DU RESOURCE COORDINATION REQUEST message or any existing or new F1AP messages.

[0200] Step 3. The gNB DU 61 sends the F1 Energy Usage reporting Response message to the gNB CU-CP 6201 or AMF 70.

[0201] The F1 Energy Usage reporting Response message may be a different F1AP message. For example, F1 Setup message, GNB-DU CONFIGURATION UPDATE message, GNB-CU CONFIGURATION UPDATE ACKNOWLEDGE message, GNB-DU RESOURCE COORDINATION RESPONSE message, GNB-DU STATUS INDICATION message or any existing or new F1NAP messages.

[0202] Step 4. The gNB DU 61 monitors and evaluates the energy usage and efficiency based on the received information in step 2. For example, the gNB monitors and evaluates the energy usage and efficiency in the network, possibly per granularity level if required in the subscription by the AF, e.g., per gNB DU level, RAN level, NF level, S-NSSAI level, PDU session level, and UE level etc.

[0203] Step 5. When the Reporting period is met for the energy usage and energy efficiency monitoring, the gNB DU 61 sends F1 Energy Usage reporting Notify message to the gNB CU-CP 6201 including Energy usage request reference ID, energy usage report, energy usage entity and location. 　　Refer to step 7 in Fig. 1 for parameter details. 　　The gNB DU 61 may send the F1 Energy Usage reporting Notify message regardless of the Reporting period.

[0204] Upon receiving the Energy Usage reporting Notify message from the gNB DU 61, the gNB CU-CP 6201 may compile the received F1 Energy Usage reporting Notify messages from another gNB DU 61 and generates an energy usage report that to be sent to the NEF 79 in step 7 of Fig. 1. 　　In the same manner as at least one of the other aspects, the gNB CU-CP 6201 may send the received F1 Energy Usage reporting Notify message without the compiling.

[0205] The F1 Energy Usage reporting Notify message may be a different F1AP message. For example, F1 Setup message, GNB-DU CONFIGURATION UPDATE message, GNB-CU CONFIGURATION UPDATE ACKNOWLEDGE message, GNB-DU RESOURCE COORDINATION RESPONSE message, GNB-DU STATUS INDICATION message or any existing or new F1NAP messages.

[0206] Step 6. Steps 5 and 6 in Fig. 6 take place with replacing gNB 5 with gNB CU-CP 6201.

[0207] Variant 1 of Fifth Example of the Second Aspect 　　In one example, if multiple gNB DUs 61 are deployed, the EECF 78, i.e. the energy efficiency control functionality may be embedded in the gNB DUs 61. In this case, the gNB CU-CP 6201 requests measurements related to the data usage from one or multiple gNB DUs 61 and the gNB CU-CP 6201 may compile the received energy usage reports before forwarding them to the AMF 70.

[0208] Sixth Example of the Second Aspect 　　Fig. 8 illustrates a mechanism for Energy usage monitoring and control. The EECF 78 may initiate this process to one or multiple Energy usage entities that are required to energy usage and energy efficiency monitoring. 　　This energy efficiency monitoring and controlling entity may be a new NF called, for example, Energy Efficiency Control Function (EECF 78) or any other name for the purpose of energy efficiency monitoring and control. The EECF 78 may also be embedded within an existing NF like O&M, PCF, NWDAF, NSACF, UDM or any other existing NF. The Fig. 6 below discloses a Network Function energy efficiency / saving control. The NF node in the Fig. 7 may be a base station, the gNB CU-UP 6202, eNodeB or any other new and existing NF in RAN 5.

[0209] For example, the processes in Fig. 8 may be triggered at step 0 or 6 in Fig. 1 and step 6 in Fig. 2.

[0210] The detailed processes of the Sixth example of the Second Aspect are described below, with reference to Fig. 8.

[0211] Step 1. Steps 1, 2 and 3 in Fig. 6 take place with replacing gNB 5 with gNB CU-CP 6201.

[0212] Step 2. The gNB CU-CP 6201 sends the E1 Energy Usage reporting control message to the gNB CU-UP 6202 including Energy usage request reference ID, energy usage report required, energy usage entity, reporting mode, reporting threshold, reporting period, location, PDU session IDs, S-NSSAIs and UEs. 　　Refer to step 1 in Fig. 1 for parameter details.

[0213] The gNB CU-CP 6201 may send multiple E1 Energy Usage reporting control messages to the gNB CU-UP 6202 in case one of the following conditions met: - The gNB CU-CP 6201 receives plural gNB CU-UP 6202 as the energy usage entity (e.g., the gNB CU-CP 6201 receives one or more "Energy usage entity" parameters indicating gNB CU-UP 6202). - The gNB CU-CP 6201 receives the location information (ex. a list of TAI) and there are multiple gNB CU-UP 6202 that covers the received location.

[0214] - The gNB CU-CP 6201 receives the PDU Session IDs and UEs while the UE configures the multi connectivity, and the gNB CU-CP 6201 sends one E1 Energy Usage reporting control message for a gNB CU-UP 6202 for MN and another E1 Energy Usage reporting control messages to the other gNB CU-UP 6202 for SN (e.g., the gNB CU-CP 6201 may send one E1 Energy Usage reporting control message to gNB CU-UP 6202 for the MN and another Energy Usage reporting control message to gNB CU-UP 6202 for SN).

[0215] The E1 Energy Usage reporting control message may be a different E1AP message. For example, GNB-CU-UP E1 SETUP RESPONSE message, GNB-CU-CP E1 SETUP REQUEST message, GNB-CU-UP CONFIGURATION UPDATE ACKNOWLEDGE message, GNB-CU-CP CONFIGURATION UPDATE message, RESOURCE STATUS REQUEST message or any existing or new E1 AP messages.

[0216] Step 3. The gNB CU-UP 6202 sends the E1 Energy Usage reporting Response message to the gNB CU-CP 6201.

[0217] The E1 Energy Usage reporting Response message may be a different E1AP message. For example, GNB-CU-UP E1 SETUP REQUEST message, GNB-CU-CP E1 SETUP RESPONSE message, GNB-CU-UP CONFIGURATION UPDATE message, GNB-CU-CP CONFIGURATION UPDATE ACKNOWLEDGE message, RESOURCE STATUS RESPONSE message, RESOURCE STATUS UPDATE message or any existing or new E1NAP messages.

[0218] Step 4. The gNB CU-UP 6202 monitors and evaluates the energy usage and efficiency based on the received information in step 2.

[0219] Step 5. When the Reporting period is met for the energy usage and energy efficiency monitoring, the gNB CU-UP 6202 sends E1 Energy Usage reporting Notify message to the gNB CU-CP 6201 including Energy usage request reference ID, energy usage report, energy usage entity and location. 　　Refer to step 7 in Fig. 1 for parameter details. 　　The CU-UP 6202 may send the E1 Energy Usage reporting Notify message regardless of the Reporting period.

[0220] Upon receiving the Energy Usage reporting Notify message from the gNB CU-UP 6202, the gNB CU-CP 6201 may compile the received E1 Energy Usage reporting Notify messages from another gNB DU 61 and generates an energy usage report that to be sent to the NEF 79 in step 7 of Fig. 1. 　　In the same manner as at least one of the other aspects, the gNB CU-CP 6201 may send the received E1 Energy Usage reporting Notify message without the compiling.

[0221] The E1 Energy Usage reporting Notify message may be a different E1AP message. For example, GNB-CU-UP E1 SETUP REQUEST message, GNB-CU-CP E1 SETUP RESPONSE message, GNB-CU-UP CONFIGURATION UPDATE message, GNB-CU-CP CONFIGURATION UPDATE ACKNOWLEDGE message, RESOURCE STATUS RESPONSE message, RESOURCE STATUS UPDATE message or any existing or new E1NAP messages.

[0222] Step 6. Steps 5 and 6 in Fig. 6 take place with replacing gNB 5 with gNB CU-CP 6201.

[0223] Variant 1 of Sixth Example of the Second Aspect 　　In one example, if multiple gNB CU-UPs 6202 are deployed, the EECF 78, i.e. the energy efficiency control functionality may be embedded in the gNB CU-UPs 6202. In this case, the gNB CU-CP 6201 requests measurements related to the data usage from one or multiple gNB CU-UPs 6202 and the gNB CU-CP 6201 may compile the received energy usage reports before forwarding them to the AMF 70.

[0224] Seventh Example of the Second Aspect 　　Fig. 9 illustrates a mechanism for energy usage monitoring and control with energy credits per UE during registration. It is assumed that each Energy Efficiency supporting subscriber UE is allocated (by the network operator via the O&M or by the Application Server AF via the NEF) with Energy Credit profile which is stored in the UE subscription information within the UDM and used for PCF policy control. The Energy Credit profile for a UE may contain information like energy credit units available to use by the UE, information how the UE should be treated at expiry of the energy credits (e.g., to be rejected with a new rejection cause (no energy credit left) and possibly with a back-off timer or the UE is still allowed for service but with a higher charging rate), information how and when the energy credits are restored, information when and where the energy credits are applicable, per service or in general and etc. Fig. 9 below discloses an energy usage monitoring and control with energy credits per UE during the UE registration procedure.

[0225] The detailed processes of the Seventh example of the Second Aspect are described below, with reference to Fig. 9.

[0226] Step 1. Each Energy Efficiency supporting subscriber UE, e.g., UE 3, is allocated (by the operator via the O&M or by the AF via the NEF) with Energy Credit profile which is stored in the UE 3 subscription information within the UDM 75 and used for PCF 73 policy control. The Energy Credit profile for a UE 3 may contain information like energy credit units available to use by the UE 3, information how the UE 3 should be treated at expiry of the energy credits (e.g., to be rejected with a new rejection cause (no energy credit left) and possibly with a back-off timer or the UE 3 is still allowed for service but with a higher charging rate), information how and when the energy credits are restored, information when and where the energy credits are applicable. The above-mentioned information may be configured per service or in general (e.g., configured in common) and etc.

[0227] Step 2. The UE 3 supporting energy efficiency feature triggers a request for registration with the network and the UE 3 sends Registration Request message to the AMF 70 which is relayed by the RRC Connection Setup Complete message from the UE 3 to the RAN 5 node and then relayed by the Initial UE Request message from the RAN 5 node to the AMF 70. In the Registration Request message, the UE 3 may include an indication for energy efficiency feature support, for example called Energy Efficiency support indication or any other notation for a parameter to indicate the support for energy efficiency feature by the UE 3. The Energy Efficiency support indication may be part of the network capability information element within the Registration Request message.

[0228] For example, the Energy Efficiency support indication may indicate that the UE 3 supports the Energy Credit units or Energy Credit. 　　For example, the Energy Efficiency support indication may indicate that the UE 3 is able to understand the Energy Credit units or Energy Credit. 　　The energy efficiency feature may be feature to support the Energy Credit units or Energy Credit. 　　The energy efficiency feature may be feature to be able to understand the Energy Credit units or Energy Credit. 　　For example, the UE having or supporting the energy efficiency feature may be the UE which is able to perform the process(es) in Fig. 9.

[0229] Step 3. If the UE 3 indicated support for energy efficiency by using the Energy Efficiency support indication, the AMF 70 includes the UE_ID and the Energy Efficiency support indication in the Nudm_UECM_Registration message to the UDM 75. The AMF 70 sends the Nudm_UECM_Registration message to the UDM 75.

[0230] Step 4. The UDM 75 confirms the UE 3's registration with the Nudm_UECM_Registration response message back to the AMF 70. 　　For example, the UDM 75 may send the Nudm_UECM_Registration response message to the AMF 70.

[0231] Step 5. If the UE 3 indicated support for Energy Efficiency, the UDM 75 provides the Energy Credit profile of UE 3 to the PCF 73. The Energy Credit profile for UE 3 may contain at least one of information like energy credit units available to use by the UE 3 (e.g., information indicating the energy credit units or the energy credit), information how the UE 3 should be treated at expiry of the energy credits if the UE 3 request a service from the network (e.g., to be rejected with a new rejection cause (for example "no energy credit left") and possibly with a back-off timer or the UE 3 is still allowed the service but with a higher charging rate), information how and when the energy credits for the UE 3 are restored, information when and where the energy credits are applicable. The above-mentioned information may be configured per service or in general and etc.

[0232] Step 6. The UDM 75 provides the Energy Credit profile of the UE 3 to the PCF 73 with or by using Nudr_DM_Notify message in which message the UDM 75 includes the UE ID and the Energy Credit profile for UE 3. 　　For example, the UDM 75 may send the Nudr_DM_Notify message including the UE ID and the Energy Credit profile for UE 3 to the PCF 73.

[0233] Step 7. The PCF 73 stores the Energy Credit profile for the UE 3. The PCF 73 may indicate to the UE 3, i.e., to the user of UE 3 certain information from the UE 3's Energy Credit profile like for example the remaining energy credit, for example in energy credit units for that UE 3. The energy credit units indicate the amount of the energy credit in energy credit units for example, or in any other expression of energy for the remaining amount of energy that the network can use to serve the UE 3. Every time the UE 3 requests and receives a service from the network, the network updates the energy credits that are available for the UE 3 by deducting the amount of the energy credit units used for each service. The UE 3 may estimate the amount of the energy credit units (or the energy credit or the energy itself) used for service(s) to be requested, and the UE 3 may request the service(s) in a case where the UE 3 determines that the UE 3 has the enough energy credit (e.g., the UE 3 has the enough energy credit for the estimated amount of the energy credit).

[0234] Step 8. The PCF 73 sends the Namf_Communication_N1N2MessageTransfer message to the AMF 70 in which the PCF 73 includes the UE ID, UE policy and the current energy credit units available to the UE 3, for example called Energy Credit units. If the PCF 73 decides there are no energy credits left for the UE 3, the PCF 73 may reject the UE registration and in this case the PCF 73 includes in the Namf_Communication_N1N2MessageTransfer message to the AMF 70 a reject cause, for example called as 'no energy credit' or any other notation for a reject cause with the purpose to indicate that there is no energy credits available to the UE 3. The PCF 73 may also suggest an energy back-off timer in the Namf_Communication_N1N2MessageTransfer message to the AMF 70 so that the UE 3 does not come back for a registration or service before the expiry of the energy back-off timer. If the 'no energy credit' reject cause is applicable for S-NNSAI for which the UE 3 ask registration for, then the 'no energy credit' reject cause would be applicable for that S-NSSAI and the PCF 73 would include the S-NSSAI for which the UE 3 has no more energy credit as a parameter in the Namf_Communication_N1N2MessageTransfer message to the AMF 70. In this case the UE 3 may not come back with registration request or service request for the rejected S-NSSAI for the duration of the energy back-off timer, if included.

[0235] Step 9. The AMF 70 initiates UE Configuration Update Commend message to the UE 3 in which message the AMF 70 provides the Energy Credit units to the UE 3. If the PCF 73 rejected one or more S-NSSAIs with the no energy credit reject cause, the AMF 70 adds the rejected S-NSSAIs in the Rejected NSSAI parameter to the UE 3 within the UE Configuration Update Commend message.

[0236] Depending upon a content in the Namf_Communication_N1N2MessageTransfer message from the PCF 73 in step 8, the AMF 70 takes either step 10-a or step 10-b.

[0237] Step 10-a. If the PCF 73 rejected the UE 3's registration with the network with a reject cause 'no energy credit' (e.g., the AMF 70 receives the reject cause 'no energy credit' from the PCF 73), the AMF 70 rejects the UE 3's registration with the network by sending Registration Reject message to the UE 3 in which the AMF 70 provides the reject cause 'no energy credit' and potentially energy back-off timer which may be suggested by the PCF 73 or suggested by the AMF 70 itself. If UE 3 receives Registration Reject message from the AMF 70 with a reject case 'no energy credit' the UE 3 may not attempt to register again or to request a service until the expiry of the energy back-off timer, if included. 　　For example, in a case where the UE 3 sends the Registration Request message including Requested S-NSSAI which includes S-NSSAI 1 and the AMF 70 receives from the PCF 73 the reject cause 'no energy credit' for S-NSSAI 1, the AMF 70 send the Registration Reject message.

[0238] Step 10-b. If the PCF 73 indicated to the AMF 70 that there still is available energy credit for the UE 3, the AMF 70 accepts the UE registration by sending Registration Accept message to the UE 3. The AMF 70 may include the information about the available energy credit for the UE 3 within the Energy Credit units parameter in the Registration Accept message. For example, the AMF 70 may include, in the Registration Accept message, information indicating the available energy credit for the UE 3. If the PCF 73 indicated 'no energy credit' for specific S-NSSAI(s) for which the UE 3 requested registration for, the AMF 70 adds the rejected S-NSSAIs in the Rejected NSSAI parameter to the UE 3 within the Registration Accept message. If an energy back-off timer was included as well in the Registration Accept message for the rejected S-NSSAI(s), the UE 3 may not attempt another registration for the rejected S-NSSAI(s) for the duration of the energy back-off timer.

[0239] For example, in a case where the UE 3 sends the Registration Request message including Requested S-NSSAI which includes S-NSSAI 1 and S-NSSAI 2 and the AMF 70 receives from the PCF 73 the reject cause 'no energy credit' for S-NSSAI 1 (e.g., on the other hand, S-NSSAI 2 is allowed to use based on the energy credit for S-NSSAI 2), the AMF 70 may add S-NSSAI 1 in the Rejected NSSAI and add S-NSSAI 2 in the Allowed NSSAI, and send the Registration Accept message including the Rejected NSSAI and the Allowed NSSAI.

[0240] Variant 1 of Seventh Example of the Second Aspect 　　One example, the step 9 may not be executed in case where the content in the Namf_Communication_N1N2MessageTransfer message from the PCF 73 in step 8 indicates the reject cause and the AMF 70 takes the step 10-a.

[0241] Variant 2 of Seventh Example of the Second Aspect 　　In one example, the UDM 75 may send energy credit units in the step 4 and the AMF 70 sends (e.g., to the UE 3) the energy credit units in the registration accept message or any existing NAS message or in a new NAS message. The energy credits can be per UE or S-NSSAI or per S-NSSAI and DNN combination or QoS ID or APP ID. The PCF 73 or the UDM 75 updates the UE 3 with the available energy credit by sending an existing message to the AMF 70 which will send the energy credit to the UE 3 in an existing NAS message or a new NAS message. 　　The energy credit can be green energy credit (energy credit of renewal energy resources e.g. solar energy or wind energy) or non-renewal energy resources (e.g. coal power or nuclear power). When the UE 3 receives the energy credits it will display on the UE 3 how much green energy resource is remaining and how much non-renewal energy credit is remaining.

[0242] The user can choose which energy type to be used for the UE 3 or S-NSSAI or S-NSSAI and DNN combination or a QoS ID or a APP ID. Based on the user selection the UE 3 sends the energy usage type information e.g. renewal energy or non-renewal energy resources in a NAS message (e.g. Registration request message or the PDU session establishment request message) to an NF (e.g. AMF or SMF). The NF will inform the other NF to use the energy related to the UE 3 or S-NSSAI or S-NSSAI and DNN combination or QoS ID as the indication.

[0243] Variant 3 of Seventh Example of the Second Aspect 　　In one example, the AMF 70 or the SMF 71 or PCF 73 retrieves an energy consumption report or an energy efficiency report from the UE in an existing NAS message or a new NAS message during an existing NAS procedure or in a new NAS procedure. The energy consumption report or the energy efficiency report consists of at least one of the following: - Energy consumed by the UE 3 over of a period of time (e.g. from last power on till the AMF 70, the SMF 71 or the PCF 73 sent a message to the UE 3). In one example the time period is sent by the AMF 70, the SMF 71 or the PCF 73 to the UE 3. - Energy consumed by an application over the period of time. (e.g. from last power on till the AMF 70, the SMF 71 or the PCF 73 sent a message to the UE 3). In one example the time period is sent by the AMF 70, the SMF 71 or the PCF 73 to the UE 3. - Energy consumed by the UE over of period of time for a particular Access Stratum (AS) procedure (e.g. RRC connection establishment procedure) or Non Access Stratum (NAS) procedure (Registration procedure).

[0244] The UE 3 is configured to measure at least one of the above events by the network (e.g. UDM 75, AMF 70 or SMF 71 or EECF 78 or PCF 73) in an existing message of an existing procedure or in a new message between the network and the UE 3. In one example, the network configures the UE 3 during the registration procedure by send the information element in an existing or a new message between the AMF 70 and the UDM 75. When the information element is received by the AMF, the AMF70 sends the information element in an existing NAS message e.g. Registration Accept message. When the UE 3 receives the information element is the NAS message, the UE 3 starts measuring the event as per the value of the information element. One of the value of the information element is mentioned above. In one example, the PCF 73 sends the information element in the URSP policy to the UE 3 or in an existing message to the UE 3.

[0245] In one example when the network requests the UE 3 to send the energy report then the UE 3 may choose not to send the energy report (e.g. if the user chooses not to share the energy report), to the network. The UE may ask to the user to consent the energy report sharing to the network. The UE 3 share the energy report to the network only when the user gives the consent to the UE 3.

[0246] Eighth Example of the Second Aspect 　　Fig. 10 illustrates a mechanism for energy usage monitoring and control with energy credits per UE during service delivery to the UE, e.g. PDU Session establishment procedure. It is assumed that each Energy Efficiency supporting subscriber UE is allocated (by the network operator via the O&M or by the Application Server AF 201 via the NEF 79) with Energy Credit profile which is stored in the UE 3 subscription information within the UDM 75 and used for PCF policy control. The Energy Credit profile for a UE 3 may contain information like energy credit units available to use by the UE, information how the UE should be treated at expiry of the energy credits (e.g., to be rejected with a new rejection cause (no energy credit left) and possibly with a back-off timer or the UE is still allowed for service but with a higher charging rate), information how and when the energy credits are restored, information when and where the energy credits are applicable, per service or in general and etc. Fig. 10 below discloses an energy usage monitoring and control with energy credits per UE during the UE PDU Session establishment procedure.

[0247] The detailed processes of the Eighth example of the Second Aspect are described below, with reference to Fig. 10.

[0248] Step 1. The UE 3 initiates a request for service by sending PDU Session Establishment Request message to the AMF 70. If the UE 3 is energy efficiency feature supporting UE, the UE 3 indicates within the PDU Session Establishment Request message the Energy Efficiency support indication or any other notation for a parameter to indicate that the UE 3 supports the energy efficiency or usage control feature or any other notation for a parameter to indicate the support for energy efficiency feature by the UE 3. The PDU Session Establishment Request message is delivered to the AMF 70 within the NAS Uplink message. 　　For example, the UE 3 may include in the PDU Session Establishment Request message UE ID, PDU Session ID, S-NSSAI and the Energy Efficiency support indication. 　　The energy efficiency feature may be expressed as the energy efficiency or usage control feature. 　　For example, the UE having or supporting the energy efficiency feature may be the UE which is able to perform the process(es) in Fig. 10.

[0249] Step 2. If the Energy Efficiency support indication was included in the PDU Session Establishment Request message from the UE 3, the AMF 70 may select a SMF, e.g., SMF 71 with or having energy efficiency control or energy usage saving capability. Then the AMF 70 sends Nsmf_PDUSession_CreateSMContext Request message to the selected SMF 71 in which message the AMF 70 includes the Energy Efficiency support indication. 　　For example, the SMF having energy efficiency control or energy usage saving capability may be the SMF which is able to perform the process(es) in Fig. 10.

[0250] Step 3. The SMF 71 confirms the request for SM context creation with the Nsmf_PDUSession_CreateSMContext Response message back to AMF 70.

[0251] Step 4. If the AMF 70 included the Energy Efficiency support indication in the Nsmf_PDUSession_CreateSMContext Request to the SMF 71, the SMF 71 may trigger SM policy control creation procedure with a PCF 73. The SMF 71 invokes Npcf_SMPolicyControl_Create service operation to the PCF 73. For example, the SMF 71 may send, to the PCF 73, Npcf_SMPolicyControl_Create message including the UE ID, PDU Session ID, S-NSSAI, the Energy Efficiency support indication.

[0252] Step 5. If the Energy Efficiency support indication was included in the Npcf_SMPolicyControl_Create message from the SMF 71, the PCF 73 may trigger enquiry with the UDM 75. The PCF 73 sends Nudr_DM_Query message to the UDM 75 in which message the PCF 73 includes the UE ID and the Energy Efficiency support indication.

[0253] Step 6. The UDM 75 checks if the UE 3 has an Energy Credit profile within the UDM 75. If so, the UDM 75 decides to provide the Energy Credit profile for the UE 3 to the PCF 73.

[0254] Step 7. The UDM 75 returns Nudr_DM_Query response message to the PCF 73 in which message the UDM 75 includes the UE ID and the Energy Credit profile for the UE 3. The Energy Credit profile for a UE 3 may contain information like energy credit units available to use by the UE 3, information how the UE 3 should be treated at expiry of the energy credits if the UE 3 requests a service from the network (e.g., to be rejected with a new rejection cause (for example no energy credit left) and possibly with a back-off timer or the UE 3 is still allowed for service but with a higher charging rate), information how and when the energy credits for the UE 3 are restored, information when and where the energy credits are applicable. The above-mentioned information may be configured per service or in general and etc.

[0255] Step 8. The PCF 73 stores the Energy Credit profile for the UE 3. The PCF 73 may indicate to the UE 3, i.e., to the user of UE 3, certain information from the UE 3's Energy Credit profile like for example the remaining energy credit before the current service is provided to the user, for example in energy credit units for that UE 3. The energy credit units indicate the amount of the energy credit in energy credit units for example, or in any other expression of energy for the remaining amount of the energy that the network can use to serve the UE 3. Step 8 may be same to step 7 in Fig. 9.

[0256] Step 9. If there is no energy credit available for the UE 3 or for the S-NSSAI on which the UE 3 requires a PDU Session establishment, the PCF 73 may reject the PDU Session establishment and may send the Namf_Communication_N1N2MessageTransfer message to the AMF 70 in which the PCF 73 includes PDU Session reject cause such as 'no energy credit'. The PCF 73 may include energy back-off timer in the message. If the PDU Session establishment rejection is because of no energy credit for the S-NSSAI on which the PDU Session is requested, the PCF 73 also includes the S-NSSAI for which the UE 3 has no energy credit left. For example, the Namf_Communication_N1N2MessageTransfer message may include information for UE ID, reject cause, back-off timer and S-NSSAI. 　　For example, in a case where the UE 3 sends the PDU Session Establishment Request message including S-NSSAI 1 in step 1 and the PDU Session establishment on S-NSSAI 1 is rejected due to no energy credit, the Namf_Communication_N1N2MessageTransfer message may include S-NSSAI 1.

[0257] Step 10. If the AMF 70 receives PDU Session rejection cause such as 'no energy credit' from the PCF 73, the AMF 70 may reject the PDU Session establishment and send the PDU Session Establishment Reject message to the UE 3 with or by using a Downlink NAS Transfer message and the AMF 70 includes in the PDU Session Establishment Reject message PDU Session reject cause such as 'no energy credit'. The AMF 70 may include the energy back-off timer, suggested by the PCF 73 in the Namf_Communication_N1N2MessageTransfer message or suggested by the AMF 70 itself.

[0258] When the UE 3 receives PDU Session Establishment Reject message including the reject cause 'no energy credit', the UE 3 may not trigger another PDU Session request. In a case where the energy back-off timer is included in the received message, the UE 3 may not trigger another PDU Session request until the expiry of the energy back-off timer. If the 'no energy credit' PDU Session reject cause is related to S-NSSAI, the UE 3 may not trigger another PDU Session Establishment Request for that S-NNSAI until the expiry of the energy back-off timer. The reject cause may be related to S-NSSAI sent by the UE 3 in step 1. The reject cause may be related to S-NSSAI which is sent by the UE 3 in step 1 and which is rejected due to no energy credit. For example, the PDU Session Establishment Reject message may include information for UE ID, PDU session reject cause, back-off timer and S-NSSAI. The PDU Session Establishment Reject message may include the UE ID and the S-NSSAI which is rejected due to no energy credit.

[0259] Step 11. If the PCF 73 decides that there is energy credit available to the UE 3, the PCF 73 completes the SM policy creation with returning Npcf_SMPolicyControl_Create response message to the SMF 71.

[0260] Step 12. After step 11, the PDU Session establishment procedure continues from step 8 to the end of the PDU Session Establishment procedure as per 4.3.2.2.1 of TS23.502 [NPL4].

[0261] Step 13. At the end of the PDU Session the CHF 76 sends Nchf_SpendingLimitControl_Notify message to the PCF 73 in which the CHF 76 includes the UE ID and the amount of energy used for the PDU Session in Energy Credit units for example or in any other expression to indicate the amount of the energy used for the PDU Session. Alternatively, the CHF 76 may include the current amount of energy available for the UE 3 after the PDU Session, expressed in Energy Credit units available for that UE 3 or in any other expression to indicate the amount of energy available for use by the UE 3, e.g. the user of UE 3.

[0262] Step 14. The PCF 73 updates the remaining Energy Credit units available for the UE 3. Every time the UE 3 requests and receives a service from the network, the network, e.g. the PCF 73, updates the energy credits that are available for the UE 3 by deducting the amount of the energy credit units used for each service to the UE 3. 　　For example, the PCF 73 may update the remaining Energy Credit units or Energy Credit available for the UE 3 based on the Energy Credit units or Energy Credit received from the CHF 76. 　　For example, the PCF 73 may update the remaining Energy Credit units or Energy Credit available for the UE 3 based on the amount of energy used for the PDU Session in Energy Credit units or Energy Credit received from the CHF 76.

[0263] For example, the PCF 73 may update the remaining Energy Credit units or Energy Credit available for the UE 3 by subtracting the Energy Credit units or Energy Credit received from the CHF 76, from the Energy Credit units or Energy Credit available for the UE 3 before the PDU Session. 　　For example, the PCF 73 may update the remaining Energy Credit units or Energy Credit available for the UE 3 by subtracting the amount of energy used for the PDU Session in Energy Credit units received from the CHF 76, from the amount of energy indicated by the Energy Credit units or Energy Credit available for the UE 3 before the PDU Session.

[0264] Step 15. The PCF 73 may decide to update the UE 3, i.e. the user of UE 3, with the amount of the energy remaining available for the UE 3 after the latest service to the UE 3 e.g. after the end of the PDU Session. The PCF 73 sends Namf_Communication_N1N2MessageTransfer message to the AMF 70 in which the PCF 73 includes the UE ID, the amount of the energy still available to the UE 3 after the PDU Session, expressed within the Energy Credit units available to the UE 3 and the amount of the energy used for the last service by UE 3, expressed within the Energy Credit units used parameter. 　　The PCF 73 may send the Namf_Communication_N1N2MessageTransfer message including the Energy Credit units or Energy Credit updated in step 14.

[0265] Step 16. The AMF 70 forwards the received energy usage information from the PCF 73 to the UE 3 with or by using the UE Configuration Update Command message in which the AMF 70 includes the amount of the energy still available to the UE 3 after the PDU Session, expressed within the Energy Credit units available parameter and the amount of the energy used for the last service, expressed within the Energy Credit units used parameter. 　　The AMF 70 may send the UE Configuration Update Command message including the information received from the PCF 73 in step 15.

[0266] Step 17. If the AF 201 has a subscription with the network, e.g. the PCF 73, for energy usage exposure, the PCF 73 may notify the AF 201 via the NEF 79 about the energy still available to the UE 3 and about the energy used for the latest service to the UE 3, e.g. for the PDU Session. The PCF 73 sends Npcf_EnergyUsageExposure_Notify message to the NEF 79 in which the PCF 73 includes the amount of the energy still available to the UE 3 after the PDU Session expressed within the Energy Credit units available and the amount of the energy used for the last service expressed within the Energy Credit units used parameter. 　　The PCF 73 may send the Npcf_EnergyUsageExposure_Notify message including the Energy Credit units or Energy Credit updated in step 14.

[0267] Step 18. The NEF 79 exposes or sends to the AF 201 the information received from the PCF 73 with or by using the Nnef_EventExposure_Notify service operation in which the NEF 79 includes the UE ID and the amount of the energy still available to the UE 3 after the PDU Session, expressed within the Energy Credit units available parameter and the amount of the energy used for the last service expressed within the Energy Credit units used parameter. This way, the AF 201 may monitor the used and the still available amount of energy for use by the UE 3 and the AF 201 may take decision to top-up the available amount of energy to the UE 3 or take restrictive measures. 　　The NEF 79 may send the Nnef_EventExposure_Notify message including the information received from the PCF 73 in step 17.

[0268] According to at least one of the above Aspects or at least one of the above Variants, for example, it can solve the above-mentioned problem(s). 　　For example, at least one of the above Aspects or at least one of the above Variants can solve the problem that there is no technical solution in the current 3GPP standards for achieving the above description in SP-231192 [NPL5].

[0269] Third Aspect 　　One of the strategies to save energy within mobile networks is to shut down RAN node(s) at times of low usage. Eventually only one coverage layer or part of the coverage layers would be used. Thus, there is a potential for further gain to be exploited by pooling the coverage layer on a local basis among operators at times of low usage. Pooling the coverage layer may mean that one or more coverages or one or more networks are prepared for the shutdown RAN node(s) at times of low usage to achieve the energy saving. The Third Aspect includes a mechanism where an agreement could be put in place between network operators so that in the low load periods (e.g. night time) only one of or part of multiple mobile networks may be active in an area and will provide coverage to the subscribers of all networks, whereas the other networks can apply cell shutdown to obtain network energy savings.

[0270] First Example of the Third Aspect 　　Fig. 11 illustrates a mechanism for coverage pooling for UE(s) in idle mode. PLMN-1 and PLMN-2 have geographical coverage overlap, e.g. RAN-1 from PLMN-1 and RAN-2 from PLMN-2 coverage area overlaps. There are mutual agreements between PLMN-1 (called beneficiary PLMN) and PLMN-2 (called donor PLMN) allowing the donor PLMN-2 to provide services to the subscribers of the beneficiary PLMN-1 when the beneficiary PLMN-1 is not active in an area of low load. The operator of the beneficiary PLMN-1 and of the donor PLMN-2 may define e.g. on a daily basis or for specific locations and time, when the coverage pooling starts and ends, i.e. the time window when the subscribers of the beneficiary PLMN-1 can be served by the donor PLMN-2 while the UE(s) would still display being served by their home beneficiary PLMN-1. Fig. 11 below discloses a coverage pooling for UE(s) in idle mode.

[0271] The detailed processes of the First example of the Third Aspect are described below, with reference to Fig. 11.

[0272] Step 1. AMF-1 7001 in the beneficiary PLMN-1 and AMF-2 7002 in the donor PLMN-2 may be configured by the network operators of the beneficiary PLMN-1 and of the donor PLMN-2 with or by using parameters for coverage pooling based on location and time, e.g. service shut down time which is set to T1 and service resume time which is set to T2. T1 may be certain time e.g., 0:00 AM. T2 may be certain time e.g., 8:00 AM. The parameters for coverage pooling may include the service shut down time and the service resume time.

[0273] Step 2. The UE 3 is registered with the beneficiary PLMN-1.

[0274] Step 3. At some point, before the service shut down time T1 for the RAN-1 501 in the beneficiary PLMN-1, the AMF-1 7001 in beneficiary PLMN-1 triggers N2 message to the RAN-1 501 in the beneficiary PLMN-1.

[0275] Step 4. In the N2 message to RAN-1 501, the AMF-1 7001 includes the following parameters: - shut down notification - the shut down notification or any other notation for a parameter to notify the UE 3 to start moving, via cell reselection for example, to a donor PLMN, for example PLMN-2. The shut down notification may indicate that the RAN-1 5001 will shut down. The shut down notification may indicate that the RAN-1 5001 will shut down at time indicated by the service shut down time.

[0276] - service shut down time - the time, for example the absolute time, when the RAN node, for example RAN-1 501 in the beneficiary PLMN-1, will shut down. The service shut down time may be set to T1. - donor PLMN - the identity of the donor PLMN, for example PLMN-2, to which the UE 3 needs to start moving as soon as the beneficiary PLMN, for example PLMN-1, starts broadcasting the shut down notification. The donor PLMN may be set to PLMN-2. The donor PLMN may be set to PLMN ID of PLMN-2. - service resume time - The time, for example the absolute time, when the RAN node, for example the RAN-1 501 of the beneficiary PLMN-1 resumes service. The service resume time may be set to T2.

[0277] Step 5. The RAN-1 501 in the beneficiary PLMN-1 starts broadcasting the shut down notification, the service shut down time T1, the donor PLMN (e.g., PLMN-2) and the service resume time T2 by using one of the SI broadcast messages. At service shut down time T1, the RAN-1 501 of the beneficiary PLMN-1 shuts down slowly so that any UE 3 still connected to RAN-1 501, e.g. legacy UEs, move naturally to a cell in another PLMN. 　　At service shut down time T1, the RAN-1 501 of the beneficiary PLMN-1 may shut down so that any UE 3 still connected to RAN-1 501, e.g. legacy UEs, move naturally to a cell in another PLMN. 　　At service shut down time T1, the RAN-1 501 of the beneficiary PLMN-1 may shut down.

[0278] Step 6. When the UE 3 reads or receives the shut down notification in the SI broadcast message from RAN-1 501 of the beneficiary PLMN-1, the UE 3 moves to a cell in a donor PLMN, for example PLMN-2. The donor PLMN-2 identity and the service resume time T2 for the RAN-1 501 in the beneficiary PLMN-1 is also broadcast in the SI message from RAN-1 501.The UE 3 may start a random timer which expires before the service shut down time T1, so that not all UEs in the area attempt to move to a cell in the donor PLMN-2 at the same time. 　　For example, in a case where the UE 3 receives the shut down notification, the UE 3 may select or reselect a cell of the donor PLMN-2, and may camp or move to the cell.

[0279] Step 7. When the UE 3 moves to a cell in the donor PLMN, for example PLMN-2, via cell reselection or cell selection for example, the UE 3 triggers a request for registration to the donor PLMN by sending a Registration Request message. In the Registration Request message to the AMF in the donor PLMN, for example AMF-2 7002 in the donor PLMN-2, the UE 3 includes an indication that the registration request is triggered because of coverage pooling. For this, the UE 3 includes in the Registration Request message a new registration type, for example called coverage pooling or the UE 3 indicates the coverage pooling in a new independent parameter within the Registration Request message.

[0280] The indication that the registration request is triggered because of coverage pooling may be expressed as the registration type which is set to "coverage pooling". 　　For example, the UE 3 may send the Registration Request message including the registration type which is set to "coverage pooling". 　　The indication that the registration request is triggered because of coverage pooling may mean that the registration request is triggered because at least one of the coverages or networks (e.g., RANs or PLMNs) will shut down. 　　The registration type which is set to "coverage pooling" may mean that the registration is triggered because at least one of the coverages or networks (e.g., RANs or PLMNs) will shut down.

[0281] Step 8. The AMF-2 7002 in the donor PLMN-2, continues the registration procedure by sending Nudm_UECM_Registration Request message to the UDM-2 7502 in the donor PLMN-2. The AMF-2 7002 includes the coverage pooling parameter in the Nudm_UECM_Registration Request message to the UDM-2 7502 to indicate the reason or the type for the registration. For example, the AMF-2 7002 may include the registration type which is set to "coverage pooling" in Nudm_UECM_Registration Request message, and send the Nudm_UECM_Registration Request message to the UDM-2 7502. 　　The coverage pooling parameter may include the registration type which is set to "coverage pooling".

[0282] Step 9. The UDM-2 7502 of the donor PLMN-2 grants the registration for the UE 3 on the basis of the coverage pooling, as indicated by the UE 3 in the Registration Request message and verified by the UDM-2 7502 based on the coverage pooling agreement between the donor PLMN-2 and the beneficiary PLMN-1 which is available in the UDM-2 7502. 　　For example, the UDM-2 7502 may determine that the UE 3 is allowed to roam in PLMN-2. 　　Step 9 may be omitted.

[0283] Step 10. The UDM-2 7502 of the donor PLMN-2 confirms the UE 3's registration with or by sending the Nudm_UECM_Registration Response message to the AMF-2 7002. 　　In a case where the UDM-2 7502 of the donor PLMN-2 receives the message in step 8, the UDM-2 7502 may send the Nudm_UECM_Registration Response message.

[0284] Step 11. The AMF-2 7002 of the donor PLMN-2 completes the registration procedure with or by sending the Registration Accept message to the UE 3 in which the AMF-27002 may include the service resume time T2.

[0285] Step 12. The UE 3, although now served by the donor PLMN-2, it may still display beneficiary PLMN-1 as serving PLMN (e.g., the UE 3 may display PLMN-1 as serving PLMN on the UE 3 (e.g., on the UE 3's display or on the UE 3's screen)). At certain time defined by service resume time T2 the UE 3 selects or reselects back to a cell in the beneficiary PLMN-1. The UE 3 may again start a random timer before moving back the to a cell in the beneficiary PLMN -1 so that not all UEs in the area attempt to move to a cell in the beneficiary PLMN-1 at the same time.

[0286] Variant 1 of First Example of the Third Aspect 　　When UE(s) is in connected mode in step 4, the RAN-1 501 may release the RRC connection by sending RRC connection Release message, the existing RRC message or a new dedicated RRC message containing at least one of the information elements of the N2 message received in step 4. When the UE 3 receives the RRC connection Release message or the existing RRC message or the new RRC message, the UE 3 performs action(s) in step 6 defined above.

[0287] Variant 2 of First Example of the Third Aspect 　　When UE(s) is in connected mode in step 4, the RAN-1 501 may perform the handover of the UE 3 to the target RAN-2 502 as per the procedure defined in the TS 23.502 [NPL4]. In this case the Handover Required message to the AMF-1 7001 may contain at least one of the parameters received in the N2 message in step 4. The AMF-1 7001 may initiate the handover procedure to the AMF-2 7002 as per the procedure defined in TS 23.502.

[0288] Second Example of the Third Aspect 　　Fig. 12 illustrates a mechanism for coverage pooling for UE(s) in connected mode. PLMN-1 and PLMN-2 have geographical coverage overlap, e.g. RAN-1 and RAN-2 coverage area overlaps. There are mutual agreements between PLMN-1 (called beneficiary PLMN) and PLMN-2 (called donor PLMN) allowing the donor PLMN-2 to provide services to the subscribers of the beneficiary PLMN-1 when the beneficiary PLMN-1 is not active in an area of low load for example. The operators of the beneficiary PLMN-1 and the donor PLMN-2 may define e.g. on a daily basis or for specific locations and time, when the coverage pooling starts and ends, i.e. the time window when the subscribers of the beneficiary PLMN-1 can be served by the donor PLMN-2 while the UE(s) would still display as being served by their home beneficiary PLMN-1.

[0289] The detailed processes of the Second example of the Third Aspect are described below, with reference to Fig. 12.

[0290] Step 1. AMF-1 7001 in the beneficiary PLMN-1 and AMF-2 7002 in the donor PLMN-2 may be configured by the operators of the beneficiary PLMN-1 and of the donor PLMN-2 with parameters for coverage pooling based on location and time, e.g. service shut down time which is set to T1 and service resume time which is set to T2.

[0291] Step 2. The UE 3 is registered with the beneficiary PLMN-1 and the UE 3 is in connected mode with active PDU Session. 　　For example, the UE 3 may be registered with the beneficiary PLMN-1 and the UE 3 may be in connected mode, and may have the active PDU Session.

[0292] Step 3. At some point, before the service shut down time T1 for the RAN-1 501 in the beneficiary PLMN-1, the AMF-1 7001 in beneficiary PLMN-1 triggers N2 message to the RAN-1 501 in the beneficiary PLMN-1.

[0293] Step 4. In the N2 message to RAN-1 501, the AMF-1 7001 includes the following parameters: - shut down notification - the shut down notification or any other notation for a parameter to notify the UE 3 to start moving, via cell reselection for example, to a donor PLMN, for example PLMN-2. - service shut down time - the time, for example the absolute time, when the RAN node, for example RAN-1 501 in the beneficiary PLMN-1, will shut down. - donor PLMN - the identity of the donor PLMN, for example PLMN-2, to which the UE 3 needs to start moving as soon as the beneficiary PLMN, for example PLMN-1, starts broadcasting the shut down notification. - service resume time - The time, for example the absolute time, when the RAN node, for example the RAN-1 501 of the beneficiary PLMN-1 resumes service.

[0294] The definition of the parameters in step 4 in Fig. 11 may be applied to the parameters in step 4 in Fig. 12.

[0295] Step 5. Upon receiving the shut down notification from AMF-1 7001, the RAN-1 501 triggers the NG-RAN node N2 based handover procedure by sending the N2 handover required message to the AMF-1 7001.

[0296] Step 6. The RAN-1 501 sends Handover Required message to the AMF-1 7001 in which the RAN-1 501 includes the UE ID and a coverage pooling parameter or any other notation for a parameter to indicate that the trigger for the handover is the coverage pooling. 　　The coverage pooling parameter may indicate that the trigger for the handover is that at least one of the coverages or networks (e.g., RANs or PLMNs) will shut down. 　　The coverage pooling parameter may indicate that the trigger for the handover is the shutdown of the RAN-1 501.

[0297] Step 7. If coverage pooling parameter is included in the Handover Required message from RAN-1 501, the AMF-1 7001 selects an AMF in the donor PLMN-2, i.e. AMF-2 7002.

[0298] Step 8. The AMF-1 7001 sends Namf_Communication_CreateUEContext Request message to the AMF-2 7002 in which the AMF-1 7001 includes the UE_ID and the coverage pooling parameter or any other notation for a parameter to indicate to AMF-2 7002 that the Handover procedure is due to coverage pooling reason. 　　The AMF-1 7001 may include, in the Namf_Communication_CreateUEContext Request message, the coverage pooling parameter received in step 6.

[0299] Step 9. Continue with the N2 handover with steps 4 to 12 in section 4.9.1.3.2 and steps 1 to 11 in section 4.9.1.3.3 in 3GPP TS 23.502 [NPL4] until the active PDU Sessions are transferred.

[0300] Step 10. When the UE 3 moves to a cell in the donor PLMN, for example PLMN-2, via N2 handover for example, the UE 3 triggers a request for registration. The UE 3 sends Registration Request message to the AMF-2 7002 in the donor PLMN-2.

[0301] Step 11. The AMF-2 7002 in the donor PLMN-2 continues the registration procedure by sending Nudm_UECM_Registration Request message to the UDM-2 7502 in the donor PLMN-2. The AMF-2 7002 includes the coverage pooling parameter in the Nudm_UECM_Registration Request message to the UDM-2 7502 to indicate the reason or the type for the registration. 　　The coverage pooling parameter may indicate that the registration request is triggered because of coverage pooling. 　　The coverage pooling parameter may indicate that the registration request is triggered because at least one of the coverages or networks (e.g., RANs or PLMNs) will shut down. 　　The coverage pooling parameter may indicate that the registration is triggered because at least one of the coverages or networks (e.g., RANs or PLMNs) will shut down. 　　For example, in a case where the AMF-2 7002 receives the UE_ID in step 10 which is same to the UE_ID in step 8 (e.g., in a case where the UE 3 which is hand-overed in step 9 sends the Registration Request message in step 10), the AMF-2 7002 may include the coverage pooling parameter in the Nudm_UECM_Registration Request message.

[0302] Step 12. The UDM-2 7502 of the donor PLMN-2 grants the registration for the UE 3 on the basis of the coverage pooling, as indicated by the AMF-2 7002 in the Nudm_UECM_Registration Request message and verified by the UDM-2 7502 based on the coverage pooling agreement between the donor PLMN-2 and the beneficiary PLMN-1 which is available in the UDM-2 7502. 　　For example, the UDM-2 7502 may determine that the UE 3 is allowed to roam in PLMN-2. 　　Step 12 may be omitted.

[0303] Step 13. The UDM-2 7502 of the donor PLMN-2 confirms the UE 3's registration with or by sending the Nudm_UECM_Registration Response message to the AMF-2 7002. 　　In a case where the UDM-2 7502 of the donor PLMN-2 receives the message in step 11, the UDM-2 7502 may send the Nudm_UECM_Registration Response message.

[0304] Step 14. When all UE(s), e.g. UE 3, connected via RAN-1 501 are transferred to RAN-2 502 via the handover, the RAN-1 501 shuts down slowly and stays shut until the service resume time T2. 　　When the UE 3 connected via RAN-1 501 is transferred to RAN-2 502 via the handover, the RAN-1 501 may shut down and stay shut until the service resume time T2.

[0305] Third Example of the Third Aspect 　　Fig. 13 illustrates a mechanism for coverage pooling. PLMN-1 and PLMN-2 have geographical coverage overlap. There are mutual agreements between PLMN-1 (called beneficiary PLMN) and PLMN-2 (called donor PLMN) allowing the donor PLMN-2 to provide services to the subscribers of the beneficiary PLMN-1 when the beneficiary PLMN-1 is not active in an area of low load for example. The two PLMN operators may define e.g. on a daily basis or for specific locations and time when the coverage pooling starts and ends. i.e. the time window when the subscribers of the beneficiary PLMN-1 can be served by the donor PLMN-2 while the UEs would still display as being served by their home beneficiary PLMN-1.

[0306] The detailed processes of the Third example of the Third Aspect are described below, with reference to Fig. 13.

[0307] Step 1. Bilateral coverage pooling agreement between PLMN-1 and PLMN-2 is concluded. For example, at night (e.g., 22:00 PM-04:00 AM), all Cell(s) (or RAN-1 5001) in PLMN-1 is switched-off according to the bilateral coverage pooling agreement that all UE(s) in the PLMN-1 are gracefully transferred to cells that are provided by the PLMN-2.

[0308] Step 2. The OAM-2 8002 in donor PLMN-2 sends an OAM message to the AMF-2 7002 in the donor PLMN-2 to configure the AMF-2 7002 based on the bilateral coverage pooling agreement. 　　For example, the AMF-2 7002 is configured as follows: - The cell(s) in the coverage pooling area starts broadcasting the PLMN-1 (e.g., identifier (ID) of PLMN-1 or ID indicating PLMN-1, PLMN ID for PLMN-1 etc.) as for example the 5G Multiple Operator Core Network (MOCN) at 21:30. The coverage pooling area may be an area where the coverage of the PLMN-1 and the coverage of the PLMN-2 overlap. The coverage pooling area may be an area where the coverage of the PLMN-1 and the coverage of the PLMN-2 overlap and where the UE 3 can be served in case of the shutdown of one of the cell(s) (or RAN(s)) in either the PLMN-1 or PLMN-2. Regarding the above time "21:30", it may be any time before 22:00 when all Cell(s) (or RAN-1 5001) in PLMN-1 shut down. - The cell(s) in the coverage pooling area stops broadcasting the PLMN-1 (e.g., ID of PLMN-1 or ID indicating PLMN-1, PLMN ID for PLMN-1 etc.) as for example the 5G Multiple Operator Core Network (MOCN) at 4:00.

[0309] Step 3. The OAM-1 8001 in beneficiary PLMN-1 sends an OAM message to the AMF-1 7001 in the beneficiary PLMN-1 to configure the AMF-1 7001 based on the bilateral coverage pooling agreement. 　　For example, the AMF-1 7001 is configured as follows: - The cell(s) in the coverage pooling area starts broadcasting the TAI list for pre-blockaded at 21:30. Regarding the above time "21:30", it may be any time before 22:00 when all Cell(s) (or RAN-1 5001) in PLMN-1 shut down. - The cell(s) in the coverage pooling area starts broadcasting that Cell barred in MIB. - The cell(s) in the coverage pooling area stops broadcasting the TAI list for pre-blockaded at 4:00. - The cell(s) in the coverage pooling area stops broadcasting that Cell barred in MIB.

[0310] Step 4. As the preparation of the bilateral coverage pooling (or the coverage pooling) with the PLMN-1, the RAN-2 502 of the donner PLMN-2 has been configured by the TAC(s) for the beneficiary PLMN-1. 　　For example, TAC(s) for PLMN-1 may be assigned to all cell(s) in PLMN-2. TAC(s) for PLMN-1 may not be broadcast over SIB 1 by RAN-2 5002 in PLMN-2.

[0311] Step 5. Although the RAN-2 502 has been configured by the TAC(s) for the beneficiary PLMN-1, the RAN-2 502 does not broadcast the configured TAC(s) for the beneficiary PLMN-1 over SIB 1. 　　I.e., at this point, the UE 3 which has the PLMN-1 as the HPLMN cannot access with the RAN-2 502. 　　For example, the RAN-2 502 may broadcast PLMN-2 (e.g., ID of PLMN-2 or ID indicating PLMN-2, PLMN ID for PLMN-2 etc.).

[0312] Step 6. At 21:30, the AMF-2 7002 sends the DOWNLINK RAN CONFIGURATION TRANSFER message to one or multiple RAN-2s 502 that covers the coverage pooling area including the following parameters: - PLMN ID to be added - The PLMN ID to be added indicates a PLMN ID that is requested to add to a list of PLMN ID over the SIB 1 as the 5G Multiple Operator Core Network (MOCN). For example, if the PLMN ID to be added has a PLMN ID for the PLMN-1, the PLMN ID for the PLMN-1 is added to the list of PLMN ID over the SIB 1. - target TAIs or Cells - The target TAIs or Cells indicates which cell(s) that the PLMN ID to be added apply for. I.e., the PLMN ID to be added apply to those of cells that are in the target TAIs or Cells. - addition end time - The addition end time indicates a time when the PLMN ID to be added is withdrawn. I.e., at time indicated by the addition end time, the PLMN ID being added to the list of PLMN ID over the SIB 1 will be removed from the list of PLMN ID over the SIB 1.

[0313] Step 7. Upon receiving the DOWNLINK RAN CONFIGURATION TRANSFER message in step 6, all cell(s) that match with the target TAIs or Cells adds the received PLMN ID in the PLMN ID to be added to the list of PLMN ID in the SIB 1. 　　For example, in a case where the PLMN ID to be added indicates the PLMN ID for the PLMN-1, the RAN-2 502 may broadcast the SIB 1 including PLMN ID for the PLMN-2 and PLMN ID for the PLMN-1. 　　For example, in a case where the PLMN ID to be added indicates the PLMN ID for the PLMN-1, the RAN-2 502 may broadcast, in the cell(s) indicated by the target TAIs or Cells, the SIB 1 including PLMN ID for the PLMN-2 and PLMN ID for the PLMN-1.

[0314] Step 8. At 21:30, the AMF-1 7001 sends the DOWNLINK RAN CONFIGURATION TRANSFER message to one or multiple RAN-1s 501 that covers the coverage pooling area including the following parameters: - Pre-blockaded indication - The Pre-blockaded indication indicates that the pre-blockaded indication is requested to be broadcast over the BCCH. The pre-blockaded indication indicates that no new UE(s) 3 to be associated with the cell. I.e., UE(s) 3 which haven't established the RRC connection with the cell cannot newly establish the RRC connection. However, the UE(s) 3 which have the RRC connection established can stay in the cell. For example, in a case where the UE(s) 3 which haven't established the RRC connection with the cell receives the pre-blockaded indication in the cell, the UE(s) 3 may not establish the new RRC connection in the cell. The Pre-blockaded indication may indicate that RAN-1 will shut down. - target TAIs or Cells - The target TAIs or Cells indicates which cells that the pre-blockaded indication to apply for. I.e., the Pre-blockaded indication is to apply to those of cells that are in the target TAIs or Cells. - Pre-blockaded end time - The Pre-blockaded end time indicates a time when the pre-blockaded indication is withdrawn. I.e., at time indicated by the Pre-blockaded end time, the pre-blockaded indication over the BCCH will be removed.

[0315] Step 9. Upon receiving the DOWNLINK RAN CONFIGURATION TRANSFER message in step 8, all cell(s) that match with the target TAIs or Cells starts broadcasting the pre-blockaded indication over the BCCH. The pre-blockaded indication may be a single information over the BCCH that apply to all TAIs that the cell is associated with. Alternatively, the pre-blockaded indication may be broadcasted with TAI(s) over the BCCH where the TAI(s) needs to be pre-blockaded. 　　For example, the RAN-1 501 may broadcast the SIB 1 including the pre-blockaded indication. 　　For example, the RAN-1 501 may broadcast, in the cell(s) indicated by the target TAIs or Cells, the pre-blockaded indication.

[0316] Step 10. If the UE(s) 3 are capable to receive the pre-blockaded indication over the BCCH and the UE 3 has not established the RRC connection, the UE 3 does not choose (or does not select or does not reselect) a cell that broadcasts the pre-blockaded indication and starts the cell selection or the cell reselection of cell(s) other than the cell that broadcasts the pre-blockaded indication. I.e., none of UE(s) 3 will newly establish the RRC connection with the cells that broadcasts the pre-blockaded indication. 　　Since cell(s) in donor PLMN-2 broadcast the PLMN ID for the PLMN-1 after Step 7, UE(s) 3 in the PLMN-1 may move to cell(s) in the donor PLMN-2. 　　For example, the UE(s) 3 may select cell(s) in the PLMN-2, and move to or camp on the selected cell(s). 　　For example, the UE(s) 3 may select cell(s) which broadcasts the SIB 1 mentioned in step 7, and move to or camp on the selected cell(s). 　　For example, in a case where the UE(s) 3 receives the SIB 1 mentioned in step 7, the UE(s) 3 may determine that the cell(s) which broadcasts the SIB 1 is for coverage pooling and may select the cell(s) which broadcasts the SIB 1 mentioned in step 7, and move to or camp on the selected cell(s).

[0317] Step 11. At 22:00, the AMF-1 7001 sends the DOWNLINK RAN CONFIGURATION TRANSFER message to one or multiple RAN-1s 501 that covers the coverage pooling area including the following parameters: - Cell barred - The Cell barred indicates that the cell is requested to be barred. - target TAIs or Cells - The target TAIs or Cells indicates which cell(s) that the Cell barred is to apply for. I.e., the Cell barred is to apply to those of cells that are in the target TAIs or Cells. - Barring end time - The Barring end time indicates a time when the Barring is withdrawn. I.e., at time indicated by the Barring end time, the Cell barred information over the MIB will be removed.

[0318] Step 12. Upon receiving the DOWNLINK RAN CONFIGURATION TRANSFER message in step 11, all cell(s) that match with the target TAIs or Cells starts broadcasting the Cell barred information over the MIB. 　　For example, the RAN-1 501 may broadcast the MIB including the Cell barred. 　　For example, the RAN-1 501 may broadcast, in the cell(s) indicated by the target TAIs or Cells, the MIB including the Cell barred. Instead of MIB, SIB may be used.

[0319] Step 13. As the result of Cell barred information being broadcasted over the MIB in step 12, all UE(s) 3, including UE in the RRC Idle state, RRC Inactive state and the RRC Connected state, are forcibly moved to another cell (e.g., cell(s) in PLMN-2). 　　For example, in a case where the UE 3 receives the MIB, the UE 3 may select or reselect another cell in PLMN-2 (e.g., another cell in PLMN-2 that is different from the cell which broadcast the MIB), and move to camp on another cell. 　　For example, in a case where the UE 3 receives the MIB, the UE(s) 3 may select or reselect cell(s) which broadcasts the SIB 1 mentioned in step 7, and move to or camp on the selected cell(s).

[0320] Step 14. All cell(s) that match with the target TAIs or Cells in the beneficiary PLMN-1 can safely be switched off (or power off) without any service disruptions to any UE(s) 3 (e.g., any UE(s) in PLMN-1).

[0321] Variant 1 of the Third Example of the Third Aspect

[0322] The processes as disclosed in the Third Example of the Third Aspect with Fig. 13 also works within the PLMN if one wide-coverage-cell (Macro cell) overlaps with many narrow-coverage-cells (Micro cells) and the narrow-coverage-cells are shut-down if traffic becomes low including no traffic.

[0323] According to at least one of the above Aspects or at least one of the above Variants, for example, it can solve the above-mentioned problem(s). 　　For example, at least one of the above Aspects or at least one of the above Variants can solve the problem that there is no technical solution in the current 3GPP standards for achieving the above description in SP-231192 [NPL5].

[0324] System overview 　　Fig. 14 schematically illustrates a telecommunication system 1 for a mobile (cellular or wireless) to which the above aspects are applicable. 　　The telecommunication system 1 represents a system overview in which an end-to-end communication is possible. For example, UE 3 (or user equipment, 'mobile device' 3) communicates with other UEs 3 or service servers in the data network 20 via respective (R)AN nodes 5 and a core network 7. 　　The (R)AN node 5 supports any radio accesses including a 5G radio access technology (RAT), an E-UTRA radio access technology, a beyond 5G RAT, a 6G RAT and non-3GPP RAT including wireless local area network (WLAN) technology as defined by the Institute of Electrical and Electronics Engineers (IEEE). 　　The (R)AN node 5 may split into a Radio Unit (RU), Distributed Unit (DU) and Centralized Unit (CU). In some aspects, each of the units may be connected to each other and structure the (R)AN node 5 by adopting an architecture as defined by the Open RAN (O-RAN) Alliance, where the units above are referred to as O-RU, O-DU and O-CU respectively.

[0325] The (R)AN node 5 may be split into control plane function and user plane function. Further, multiple user plane functions can be allocated to support a communication. In some aspects, user traffic may be distributed to multiple user plane functions and user traffic over each user plane functions are aggregated in both the UE 3 and the (R)AN node 5. This split architecture may be called as 'dual connectivity' or 'Multi connectivity'. 　　The (R)AN node 5 can also support a communication using the satellite access. In some aspects, the (R)AN node 5 may support a satellite access and a terrestrial access. 　　In addition, the (R)AN node 5 can also be referred as an access node for a non-wireless access. The non-wireless access includes a fixed line access as defined by the Broadband Forum (BBF) and an optical access as defined by the Innovative Optical and Wireless Network (IOWN).

[0326] The core network 7 may include logical nodes (or 'functions') for supporting a communication in the telecommunication system 1. For example, the core network 7 may be 5G Core Network (5GC) that includes, amongst other functions, control plane functions and user plane functions. Each function in logical nodes can be considered as a network function. The network function may be provided to another node by adapting the Service Based Architecture (SBA). 　　A Network Function can be deployed as distributed, redundant, stateless, and scalable that provides the services from several locations and several execution instances in each location by adapting the network virtualization technology as defined by the European Telecommunications Standards Institute, Network Functions Virtualization (ETSI NFV). 　　The core network 7 may support the Non-Public Network (NPN). The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN).

[0327] As is well known, a UE 3 may enter and leave the areas (i.e. radio cells) served by the (R)AN node 5 as the UE 3 is moving around in the geographical area covered by the telecommunication system 1. In order to keep track of the UE 3 and to facilitate movement between the different (R)AN nodes 5, the core network 7 comprises at least one access and mobility management function (AMF) 70. The AMF 70 is in communication with the (R)AN node 5 coupled to the core network 7. In some core networks, a mobility management entity (MME) or a mobility management node for beyond 5G or a mobility management node for 6G may be used instead of the AMF 70.

[0328] The core network 7 also includes, amongst others, a Session Management Function (SMF) 71, a User Plane Function (UPF) 72, a Policy Control Function (PCF) 73, a Network Data Analytics Function (NWDAF) 74, a Unified Data Management (UDM) 75, a Charging Function (CHF) 76 and a Network Slice Admission Control Function (NSACF) 77, Energy Efficiency Control Function (EECF) 78, Network Exposure Function (NEF) 79 and Operations & Maintenance (OAM or O&M) 80. When the UE 3 is roaming to a visited Public Land Mobile Network (VPLMN), a home Public Land Mobile Network (HPLMN) of the UE 3 provides the UDM 75 and at least some of the functionalities of the SMF 71, UPF 72, PCF 73 and NSACF 77 for the roaming-out UE 3.

[0329] The UE 3 and a respective serving (R)AN node 5 are connected via an appropriate air interface (for example the so-called "Uu" interface and / or the like). Neighboring (R)AN node 5 are connected to each other via an appropriate (R)AN node 5 to (R)AN node interface (such as the so-called "Xn" interface and / or the like). Each (R)AN node 5 is also connected to nodes in the core network 7 (such as the so-called core network nodes) via an appropriate interface (such as the so-called "N2" / "N3" interface(s) and / or the like). From the core network 7, connection to a data network 20 is also provided. The data network 20 can be an internet, a public network, an external network, a private network or an internal network of the PLMN. In case that the data network 20 is provided by a PLMN operator or Mobile Virtual Network Operator (MVNO), the IP Multimedia Subsystem (IMS) service may be provided by that data network 20. The UE 3 can be connected to the data network 20 using IPv4, IPv6, IPv4v6, Ethernet or unstructured data type. The data network may include an Application Function (AF) 201.

[0330] The "Uu" interface may include a Control plane of Uu interface and User plane of Uu interface. 　　The User plane of Uu interface is responsible to convey user traffic between the UE 3 and a serving (R)AN node 5. The User plane of Uu interface may have a layered structure with SDAP, PDCP, RLC and MAC sublayer over the physical connection (i.e. PHY sublayer). The Control plane of Uu interface is responsible to establish, modify and release a connection between the UE 3 and a serving (R)AN node 5. The Control plane of Uu interface may have a layered structure with RRC, PDCP, RLC and MAC sublayers over the physical connection. For example, the following messages are communicated over the RRC layer to support AS signaling.

[0331] - RRC Setup Request message: This message is sent from the UE 3 to the (R)AN node 5. In addition to the parameters that are disclosed by Aspects in this disclosure, following parameters may be included together in the RRC Setup Request message. 　　- - establishmentCause and ue-Identity. The ue-Identity may have a value of ng-5G-S-TMSI-Part1 or randomValue. - RRC Setup message: This message is sent from the (R)AN node 5 to the UE 3. In addition to the parameters that are disclosed by Aspects in this disclosure, following parameters may be included together in the RRC Setup message. 　　- - masterCellGroup and radioBearerConfig. - RRC setup complete message: This message is sent from the UE 3 to the (R)AN node 5. In addition to the parameters that are disclosed by Aspects in this disclosure, following parameters may be included together in the RRC setup complete message. 　　- - guami-Type, iab-NodeIndication, idleMeasAvailable, ue-MeasurementsAvailable, mobilityState, ng-5G-S-TMSI-Part2, registeredAMF, selectedPLMN-Identity, s-NSSAI-List , onboardingRequest.

[0332] The UE 3 and the AMF 70 are connected via an appropriate interface (for example the so-called N1 interface and / or the like). The N1 interface is responsible to provide a communication between the UE 3 and the AMF 70 to support NAS signaling. The N1 interface may be established over a 3GPP access and over a non-3GPP access. For example, the following messages are communicated over the N1 interface. - registration request message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters that are disclosed by Aspects in this disclosure, following parameters may be included together in the registration request message. 　　- - 5GS registration type, ngKSI, 5GS mobile identity, Non-current native NAS key set identifier, 5GMM capability, UE security capability, Requested NSSAI, Last visited registered TAI, S1 UE network capability, Uplink data status, PDU session status, MICO indication, UE status, Additional GUTI, Allowed PDU session status, UE's usage setting, Requested DRX parameters, EPS NAS message container, LADN indication, Payload container type, Payload container, Network slicing indication, 5GS update type, Mobile station classmark 2, Supported codecs, NAS message container, EPS bearer context status, Requested extended DRX parameters, T3324 value, UE radio capability ID, Requested mapped NSSAI, Additional information requested, Requested WUS assistance information, N5GC indication and Requested NB-N1 mode DRX parameters.

[0333] - registration accept message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters that are disclosed by Aspects in this disclosure, following parameters may be included together in the registration accept message. 　　- - 5GS registration result, 5G-GUTI, Equivalent PLMNs, TAI list, Allowed NSSAI, Rejected NSSAI, Configured NSSAI, 5GS network feature support, PDU session status, PDU session reactivation result, PDU session reactivation result error cause, LADN information, MICO indication, Network slicing indication, Service area list, T3512 value, Non-3GPP de-registration timer value, T3502 value, Emergency number list, Extended emergency number list, SOR transparent container, EAP message, NSSAI inclusion mode, Operator-defined access category definitions, Negotiated DRX parameters, Non-3GPP NW policies, EPS bearer context status, Negotiated extended DRX parameters, T3447 value, T3448 value, T3324 value, UE radio capability ID, UE radio capability ID deletion indication, Pending NSSAI, Ciphering key data, CAG information list, Truncated 5G-S-TMSI configuration, Negotiated WUS assistance information, Negotiated NB-N1 mode DRX parameters and Extended rejected NSSAI.

[0334] - Registration Complete message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters that are disclosed by Aspects in this disclosure, following parameters may be included together in the Registration Complete message. 　　- - SOR transparent container. - Authentication Request message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters that are disclosed by Aspects in this disclosure, following parameters may be included together in the Authentication Request message. 　　- - ngKSI, ABBA, Authentication parameter RAND (5G authentication challenge), Authentication parameter AUTN (5G authentication challenge) and EAP message. - Authentication Response message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters that are disclosed by Aspects in this disclosure, following parameters may be populated together in the Authentication Response message. 　　- - Authentication response message identity, Authentication response parameter and EAP message.

[0335] - Authentication Result message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters that are disclosed by Aspects in this disclosure, following parameters may be populated together in the Authentication Result message. 　　- - ngKSI, EAP message and ABBA. - Authentication Failure message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters that are disclosed by Aspects in this disclosure, following parameters may be populated together in the Authentication Failure message. 　　- - Authentication failure message identity, 5GMM cause and Authentication failure parameter. - Authentication Reject message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters that are disclosed by Aspects in this disclosure, following parameters may be populated together in the Authentication Reject message. 　　- - EAP message.

[0336] - Service Request message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters that are disclosed by Aspects in this disclosure, following parameters may be populated together in the Service Request message. 　　- - ngKSI, Service type, 5G-S-TMSI, Uplink data status, PDU session status, Allowed PDU session status, NAS message container. - Service Accept message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters that are disclosed by Aspects in this disclosure, following parameters may be populated together in the Service Accept message. 　　- - PDU session status, PDU session reactivation result, PDU session reactivation result error cause, EAP message and T3448 value. - Service Reject message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters that are disclosed by Aspects in this disclosure, following parameters may be populated together in the Service Reject message. 　　- - 5GMM cause, PDU session status, T3346 value, EAP message, T3448 value and CAG information list.

[0337] - Configuration Update Command message: This message is sent from the AMF 70 to the UE 3. In addition to the parameters that are disclosed by Aspects in this disclosure, following parameters may be populated together in the Configuration Update Command message. 　　- - Configuration update indication,5G-GUTI, TAI list, Allowed NSSAI, Service area list, Full name for network, Short name for network, Local time zone, Universal time and local time zone, Network daylight saving time, LADN information, MICO indication, Network slicing indication, Configured NSSAI, Rejected NSSAI, Operator-defined access category definitions, SMS indication, T3447 value, CAG information list, UE radio capability ID, UE radio capability ID deletion indication, 5GS registration result, Truncated 5G-S-TMSI configuration, Additional configuration indication and Extended rejected NSSAI. - Configuration Update Complete message: This message is sent from the UE 3 to the AMF 70. In addition to the parameters that are disclosed by Aspects in this disclosure, following parameters may be populated together in the Configuration Update Complete message. 　　- - Configuration update complete message identity.

[0338] User equipment (UE) 　　Fig. 15 is a block diagram illustrating the main components of the UE 3 (mobile device 3). As shown, the UE 3 includes a transceiver circuit 31 which is operable to transmit signals to and to receive signals from the connected node(s) via one or more antennas 32. Further, the UE 3 may include a user interface 34 for inputting information from outside or outputting information to outside. Although not necessarily shown in the Figure, the UE 3 may have all the usual functionality of a conventional mobile device and this may be provided by any one or any combination of hardware, software and firmware, as appropriate. Software may be pre-installed in the memory and / or may be downloaded via the telecommunication network or from a removable data storage device (RMD), for example. A controller 33 controls the operation of the UE 3 in accordance with software stored in a memory 36. The software includes, among other things, an operating system 361 and a communications control module 362 having at least a transceiver control module 3621. The communications control module 362 (using its transceiver control module 3621) is responsible for handling (generating / sending / receiving) signalling and uplink / downlink data packets between the UE 3 and other nodes, such as the (R)AN node 5 and the AMF 70. Such signalling may include, for example, appropriately formatted signalling messages (e.g. a registration request message and associated response messages) relating to access and mobility management procedures (for the UE 3). The controller 33 interworks with one or more Universal Subscriber Identity Module (USIM) 35. If there are multiple USIMs 35 equipped, the controller 33 may activate only one USIM 35 or may activate multiple USIMs 35 at the same time.

[0339] The UE 3 may, for example, support the Non-Public Network (NPN), The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN). 　　The UE 3 may, for example, be an item of equipment for production or manufacture and / or an item of energy related machinery (for example equipment or machinery such as: boilers; engines; turbines; solar panels; wind turbines; hydroelectric generators; thermal power generators; nuclear electricity generators; batteries; nuclear systems and / or associated equipment; heavy electrical machinery; pumps including vacuum pumps; compressors; fans; blowers; oil hydraulic equipment; pneumatic equipment; metal working machinery; manipulators; robots and / or their application systems; tools; molds or dies; rolls; conveying equipment; elevating equipment; materials handling equipment; textile machinery; sewing machines; printing and / or related machinery; paper converting machinery; chemical machinery; mining and / or construction machinery and / or related equipment; machinery and / or implements for agriculture, forestry and / or fisheries; safety and / or environment preservation equipment; tractors; precision bearings; chains; gears; power transmission equipment; lubricating equipment; valves; pipe fittings; and / or application systems for any of the previously mentioned equipment or machinery etc.).

[0340] The UE 3 may, for example, be an item of transport equipment (for example transport equipment such as: rolling stocks; motor vehicles; motor cycles; bicycles; trains; buses; carts; rickshaws; ships and other watercraft; aircraft; rockets; satellites; drones; balloons etc.). 　　The UE 3 may, for example, be an item of information and communication equipment (for example information and communication equipment such as: electronic computer and related equipment; communication and related equipment; electronic components etc.). 　　The UE 3 may, for example, be a refrigerating machine, a refrigerating machine applied product, an item of trade and / or service industry equipment, a vending machine, an automatic service machine, an office machine or equipment, a consumer electronic and electronic appliance (for example a consumer electronic appliance such as: audio equipment; video equipment; a loud speaker; a radio; a television; a microwave oven; a rice cooker; a coffee machine; a dishwasher; a washing machine; a dryer; an electronic fan or related appliance; a cleaner etc.). 　　The UE 3 may, for example, be an electrical application system or equipment (for example an electrical application system or equipment such as: an x-ray system; a particle accelerator; radio isotope equipment; sonic equipment; electromagnetic application equipment; electronic power application equipment etc.).

[0341] The UE 3 may, for example, be an electronic lamp, a luminaire, a measuring instrument, an analyzer, a tester, or a surveying or sensing instrument (for example a surveying or sensing instrument such as: a smoke alarm; a human alarm sensor; a motion sensor; a wireless tag etc.), a watch or clock, a laboratory instrument, optical apparatus, medical equipment and / or system, a weapon, an item of cutlery, a hand tool, or the like. 　　The UE 3 may, for example, be a wireless-equipped personal digital assistant or related equipment (such as a wireless card or module designed for attachment to or for insertion into another electronic device (for example a personal computer, electrical measuring machine)). 　　The UE 3 may be a device or a part of a system that provides applications, services, and solutions described below, as to "internet of things (IoT)", using a variety of wired and / or wireless communication technologies. 　　Internet of Things devices (or "things") may be equipped with appropriate electronics, software, sensors, network connectivity, and / or the like, which enable these devices to collect and exchange data with each other and with other communication devices. IoT devices may comprise automated equipment that follow software instructions stored in an internal memory. IoT devices may operate without requiring human supervision or interaction. IoT devices might also remain stationary and / or inactive for a long period of time. IoT devices may be implemented as a part of a (generally) stationary apparatus. IoT devices may also be embedded in non-stationary apparatus (e.g. vehicles) or attached to animals or persons to be monitored / tracked.

[0342] It will be appreciated that IoT technology can be implemented on any communication devices that can connect to a communications network for sending / receiving data, regardless of whether such communication devices are controlled by human input or software instructions stored in memory. 　　It will be appreciated that IoT devices are sometimes also referred to as Machine-Type Communication (MTC) devices or Machine-to-Machine (M2M) communication devices or Narrow Band-IoT UE (NB-IoT UE). It will be appreciated that a UE 3 may support one or more IoT or MTC applications. 　　The UE 3 may be a smart phone or a wearable device (e.g. smart glasses, a smart watch, a smart ring, or a hearable device). For a wearable device, the UE 3 may be a reduced capability device (RedCap). 　　The UE 3 may be a car, or a connected car, or an autonomous car, or a vehicle device, or a motorcycle or V2X (Vehicle to Everything) communication module (e.g. Vehicle to Vehicle communication module, Vehicle to Infrastructure communication module, Vehicle to People communication module and Vehicle to Network communication module).

[0343] (R)AN node 　　Fig. 16 is a block diagram illustrating the main components of an exemplary (R)AN node 5, for example a base station ('eNB' in LTE, 'gNB' in 5G, a base station for 5G beyond, a base station for 6G). As shown, the (R)AN node 5 includes a transceiver circuit 51 which is operable to transmit signals to and to receive signals from connected UE(s) 3 via one or more antennas 52 and to transmit signals to and to receive signals from other network nodes (either directly or indirectly) via a network interface 53. A controller 54 controls the operation of the (R)AN node 5 in accordance with software stored in a memory 55. Software may be pre-installed in the memory and / or may be downloaded via the telecommunication network or from a removable data storage device (RMD), for example. The software includes, among other things, an operating system 551 and a communications control module 552 having at least a transceiver control module 5521.

[0344] The communications control module 552 (using its transceiver control sub-module) is responsible for handling (generating / sending / receiving) signalling between the (R)AN node 5 and other nodes, such as the UE 3, another (R)AN node 5, the AMF 70 and the UPF 72 (e.g. directly or indirectly). The signalling may include, for example, appropriately formatted signalling messages relating to a radio connection and a connection with the core network 7 (for a particular UE 3), and in particular, relating to connection establishment and maintenance (e.g. RRC connection establishment and other RRC messages), NG Application Protocol (NGAP) messages (i.e. messages by N2 reference point) and Xn application protocol (XnAP) messages (i.e. messages by Xn reference point), etc. Such signalling may also include, for example, broadcast information (e.g. Master Information and System information) in a sending case. 　　The controller 54 is also configured (by software or hardware) to handle related tasks such as, when implemented, UE mobility estimate and / or moving trajectory estimation. 　　The (R)AN node 5 may support the Non-Public Network (NPN), The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN). 　　The RAN in this disclosure may have same components to the (R)AN node 5. The (R)AN node 5 may be expressed as a RAN node, RAN, (R)AN etc.

[0345] System overview of (R)AN node 5 based on O-RAN architecture 　　Fig. 17 schematically illustrates a (R)AN node 5 based on O-RAN architecture to which the (R)AN node 5 aspects are applicable. 　　The (R)AN node 5 based on O-RAN architecture represents a system overview in which the (R)AN node is split into a Radio Unit (RU) 60, Distributed Unit (DU) 61 and Centralized Unit (CU) 62. In some aspects, each unit may be combined. For example, the RU 60 can be integrated / combined with the DU 61 as an integrated / combined unit, the DU 61 can be integrated / combined with the CU 62 as another integrated / combined unit. Any functionality in the description for a unit (e.g. one of RU 60, DU 61 and CU 62) can be implemented in the integrated / combined unit above. Further, CU 62 can separate into two functional units such as CU Control plane (CP) and CU User plane (UP). The CU CP has a control plane functionality in the (R)AN node 5. The CU UP has a user plane functionality in the (R)AN node 5. Each CU CP is connected to the CU UP via an appropriate interface (such as the so-called "E1" interface and / or the like).

[0346] The UE 3 and a respective serving RU 60 are connected via an appropriate air interface (for example the so-called "Uu" interface and / or the like). Each RU 60 is connected to the DU 61 via an appropriate interface (such as the so-called "Front haul", "Open Front haul", "F1" interface and / or the like). Each DU 61 is connected to the CU 62 via an appropriate interface (such as the so-called "Mid haul", "Open Mid haul", "E2" interface and / or the like). Each CU 62 is also connected to nodes in the core network 7 (such as the so-called core network nodes) via an appropriate interface (such as the so-called "Back haul", "Open Back haul", "N2" / "N3" interface(s) and / or the like). In addition, a user plane part of the DU 61 can also be connected to the core network nodes via an appropriate interface (such as the so-called "N3" interface(s) and / or the like). 　　Depending on functionality split among the RU 60, DU 61 and CU 62, each unit provides some of the functionality that is provided by the (R)AN node 5. For example, the RU 60 may provide a functionalities to communicate with a UE 3 over air interface, the DU 61 may provide functionalities to support MAC layer and RLC layer, the CU 62 may provide functionalities to support PDCP layer, SDAP layer and RRC layer.

[0347] Radio Unit (RU) 　　Fig. 18 is a block diagram illustrating the main components of an exemplary RU 60, for example a RU part of base station ('eNB' in LTE, 'gNB' in 5G, a base station for 5G beyond, a base station for 6G). As shown, the RU 60 includes a transceiver circuit 601 which is operable to transmit signals to and to receive signals from connected UE(s) 3 via one or more antennas 602 and to transmit signals to and to receive signals from other network nodes or network unit (either directly or indirectly) via a network interface 603. A controller 604 controls the operation of the RU 60 in accordance with software stored in a memory 605. Software may be pre-installed in the memory and / or may be downloaded via the telecommunication network or from a removable data storage device (RMD), for example. The software includes, among other things, an operating system 6051 and a communications control module 6052 having at least a transceiver control module 60521.

[0348] The communications control module 6052 (using its transceiver control sub-module) is responsible for handling (generating / sending / receiving) signalling between the RU 60 and other nodes or units, such as the UE 3, another RU 60 and DU 61 (e.g. directly or indirectly). The signalling may include, for example, appropriately formatted signalling messages relating to a radio connection and a connection with the RU 60 (for a particular UE 3), and in particular, relating to MAC layer and RLC layer. 　　The controller 604 is also configured (by software or hardware) to handle related tasks such as, when implemented, UE mobility estimate and / or moving trajectory estimation. 　　The RU 60 may support the Non-Public Network (NPN), The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN). 　　As described above, the RU 60 can be integrated / combined with the DU 61 as an integrated / combined unit. Any functionality in the description for the RU 60 can be implemented in the integrated / combined unit above.

[0349] Distributed Unit (DU) 　　Fig. 19 is a block diagram illustrating the main components of an exemplary DU 61, for example a DU part of a base station ('eNB' in LTE, 'gNB' in 5G, a base station for 5G beyond, a base station for 6G). As shown, the apparatus includes a transceiver circuit 611 which is operable to transmit signals to and to receive signals from other nodes or units (including the RU 60) via a network interface 612. A controller 613 controls the operation of the DU 61 in accordance with software stored in a memory 614. Software may be pre-installed in the memory 614 and / or may be downloaded via the telecommunication network or from a removable data storage device (RMD), for example. The software includes, among other things, an operating system 6141 and a communications control module 6142 having at least a transceiver control module 61421. The communications control module 6142 (using its transceiver control module 61421) is responsible for handling (generating / sending / receiving) signalling between the DU 61 and other nodes or units, such as the RU 60 and other nodes and units.

[0350] The DU 61 may support the Non-Public Network (NPN), The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN). 　　As described above, the RU 60 can be integrated / combined with the DU 61 or CU 62 as an integrated / combined unit. Any functionality in the description for DU 61 can be implemented in one of the integrated / combined unit above. 　　The DU 61 may be expressed as gNB DU. The gNB DU in this disclosure may have same components to the DU 61.

[0351] Centralized Unit (CU) 　　Fig. 20 is a block diagram illustrating the main components of an exemplary CU 62, for example a CU part of base station ('eNB' in LTE, 'gNB' in 5G, a base station for 5G beyond, a base station for 6G). As shown, the apparatus includes a transceiver circuit 621 which is operable to transmit signals to and to receive signals from other nodes or units (including the DU 61) via a network interface 622. A controller 623 controls the operation of the CU 62 in accordance with software stored in a memory 624. Software may be pre-installed in the memory 624 and / or may be downloaded via the telecommunication network or from a removable data storage device (RMD), for example. The software includes, among other things, an operating system 6241 and a communications control module 6242 having at least a transceiver control module 62421. The communications control module 6242 (using its transceiver control module 62421) is responsible for handling (generating / sending / receiving) signalling between the CU 62 and other nodes or units, such as the DU 61 and other nodes and units.

[0352] The CU 62 may support the Non-Public Network (NPN), The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN). 　　As described above, the CU 62 can be integrated / combined with the DU 61 as an integrated / combined unit. Any functionality in the description for the CU 62 can be implemented in the integrated / combined unit above. 　　The gNB CU-CP and the gNB CU-UP in this disclosure may have same components to the CU 62.

[0353] AMF 　　Fig. 21 is a block diagram illustrating the main components of the AMF 70. As shown, the apparatus includes a transceiver circuit 701 which is operable to transmit signals to and to receive signals from other nodes (including the UE 3, the NSSF) via a network interface 702. A controller 703 controls the operation of the AMF 70 in accordance with software stored in a memory 704. Software may be pre-installed in the memory 704 and / or may be downloaded via the telecommunication network or from a removable data storage device (RMD), for example. The software includes, among other things, an operating system 7041 and a communications control module 7042 having at least a transceiver control module 70421. The communications control module 7042 (using its transceiver control module 70421) is responsible for handling (generating / sending / receiving) signalling between the AMF 70 and other nodes, such as the UE 3 (e.g. via the (R)AN node 5) and other core network nodes (including core network nodes in the HPLMN of the UE 3 when the UE 3 is roaming-in). Such signalling may include, for example, appropriately formatted signalling messages (e.g. a registration request message and associated response messages) relating to access and mobility management procedures (for the UE 3).

[0354] The AMF 70 may support the Non-Public Network (NPN), The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN). The AMF in this disclosure may have same components to the AMF 70.

[0355] SMF 　　Fig. 22 is a block diagram illustrating the main components of the SMF 71. As shown, the apparatus includes a transceiver circuit 711 which is operable to transmit signals to and to receive signals from other nodes (including the AMF 70) via a network interface 712. A controller 713 controls the operation of the SMF 71 in accordance with software stored in a memory 714. Software may be pre-installed in the memory 714 and / or may be downloaded via the telecommunication network or from a removable data storage device (e.g. a removable memory device (RMD)), for example. The software includes, among other things, an operating system 7141 and a communications control module 7142 having at least a transceiver control module 71421. The communications control module 7142 (using its transceiver control module 71421) is responsible for handling (generating / sending / receiving) signalling between the SMF 71 and other nodes, such as the AMF 70 and other core network nodes (including core network nodes in the HPLMN of the UE 3 when the UE 3 is roaming-in). Such signalling may include, for example, appropriately formatted signalling messages (e.g. a HTTP restful methods based on the service based interfaces) relating to policy management procedures (for the UE 3).

[0356] The SMF 71 may support the Non-Public Network (NPN), The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN). The SMF in this disclosure may have same components to the SMF 71.

[0357] UPF 　　Fig. 23 is a block diagram illustrating the main components of the UPF 72. As shown, the apparatus includes a transceiver circuit 721 which is operable to transmit signals to and to receive signals from other nodes (including the SMF 71) via a network interface 722. A controller 723 controls the operation of the UPF 72 in accordance with software stored in a memory 724. Software may be pre-installed in the memory 724 and / or may be downloaded via the telecommunication network or from a removable data storage device (e.g. a removable memory device (RMD)), for example. The software includes, among other things, an operating system 7241 and a communications control module 7242 having at least a transceiver control module 72421. The communications control module 7242 (using its transceiver control module 72421) is responsible for handling (generating / sending / receiving) signalling between the UPF 72 and other nodes, such as the SMF 71 and other core network nodes (including core network nodes in the HPLMN of the UE 3 when the UE 3 is roaming-in). Such signalling may include, for example, appropriately formatted signalling messages (e.g. a HTTP restful methods based on the service based interfaces) relating to policy management procedures (for the UE 3).

[0358] The UPF 72 may support the Non-Public Network (NPN), The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN). The UPF in this disclosure may have same components to the UPF 72.

[0359] PCF 　　Fig. 24 is a block diagram illustrating the main components of the PCF 73. As shown, the apparatus includes a transceiver circuit 731 which is operable to transmit signals to and to receive signals from other nodes (including the AMF 70) via a network interface 732. A controller 733 controls the operation of the PCF 73 in accordance with software stored in a memory 734. Software may be pre-installed in the memory 734 and / or may be downloaded via the telecommunication network or from a removable data storage device (e.g. a removable memory device (RMD)), for example. The software includes, among other things, an operating system 7341 and a communications control module 7342 having at least a transceiver control module 73421. The communications control module 7342 (using its transceiver control module 73421) is responsible for handling (generating / sending / receiving) signalling between the PCF 73 and other nodes, such as the AMF 70 and other core network nodes (including core network nodes in the HPLMN of the UE 3 when the UE 3 is roaming-in). Such signalling may include, for example, appropriately formatted signalling messages (e.g. a HTTP restful methods based on the service based interfaces) relating to policy management procedures (for the UE 3).

[0360] The PCF 73 may support the Non-Public Network (NPN), The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN). The PCF in this disclosure may have same components to the PCF 73.

[0361] NWDAF 　　Fig. 25 is a block diagram illustrating the main components of the NWDAF 74. As shown, the apparatus includes a transceiver circuit 741 which is operable to transmit signals to and to receive signals from other nodes (including the AMF 70 and the UDM 75) via a network interface 742. A controller 743 controls the operation of the NWDAF 74 in accordance with software stored in a memory 744. Software may be pre-installed in the memory 744 and / or may be downloaded via the telecommunication network or from a removable data storage device (e.g. a removable memory device (RMD)), for example. The software includes, among other things, an operating system 7441 and a communications control module 7442 having at least a transceiver control module 74421. The communications control module 7442 (using its transceiver control module 74421) is responsible for handling (generating / sending / receiving) signalling between the NWDAF 74 and other nodes, such as the AMF 70 and other core network nodes (including core network nodes in the HPLMN of the UE 3 when the UE 3 is roaming-in). Such signalling may include, for example, appropriately formatted signalling messages (e.g. a HTTP restful methods based on the service based interfaces) relating to policy management procedures (for the UE 3).

[0362] The NWDAF 74 may support the Non-Public Network (NPN), The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN). The NWDAF in this disclosure may have same components to the NWDAF 74.

[0363] UDM 　　Fig. 26 is a block diagram illustrating the main components of the UDM 75. As shown, the apparatus includes a transceiver circuit 751 which is operable to transmit signals to and to receive signals from other nodes (including the AMF 70) via a network interface 752. A controller 753 controls the operation of the UDM 75 in accordance with software stored in a memory 754. Software may be pre-installed in the memory 754 and / or may be downloaded via the telecommunication network or from a removable data storage device (RMD), for example. The software includes, among other things, an operating system 7541 and a communications control module 7542 having at least a transceiver control module 75421. The communications control module 7542 (using its transceiver control module 75421) is responsible for handling (generating / sending / receiving) signalling between the UDM 75 and other nodes, such as the AMF 70 and other core network nodes (including core network nodes in the VPLMN of the UE 3 when the UE 3 is roaming-out). Such signalling may include, for example, appropriately formatted signalling messages (e.g. a HTTP restful methods based on the service based interfaces) relating to mobility management procedures (for the UE 3).

[0364] The UDM 75 may support the Non-Public Network (NPN), The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN). The UDM in this disclosure may have same components to the UDM 75.

[0365] CHF 　　Fig. 27 is a block diagram illustrating the main components of the CHF 76. As shown, the apparatus includes a transceiver circuit 761 which is operable to transmit signals to and to receive signals from other nodes (including the AMF 70) via a network interface 762. A controller 763 controls the operation of the CHF 76 in accordance with software stored in a memory 764. Software may be pre-installed in the memory 764 and / or may be downloaded via the telecommunication network or from a removable data storage device (RMD), for example. The software includes, among other things, an operating system 7641 and a communications control module 7642 having at least a transceiver control module 76421. The communications control module 7642 (using its transceiver control module 76421) is responsible for handling (generating / sending / receiving) signalling between the CHF 76 and other nodes, such as the AMF 70 and other core network nodes (including core network nodes in the VPLMN of the UE 3 when the UE 3 is roaming-out). Such signalling may include, for example, appropriately formatted signalling messages (e.g. a HTTP restful methods based on the service based interfaces) relating to mobility management procedures (for the UE 3).

[0366] The CHF 76 may support the Non-Public Network (NPN), The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN). The CHF in this disclosure may have same components to the CHF 76.

[0367] NSACF 　　Fig. 28 is a block diagram illustrating the main components of the NSACF 77. As shown, the apparatus includes a transceiver circuit 771 which is operable to transmit signals to and to receive signals from other nodes (including the AMF 70) via a network interface 772. A controller 773 controls the operation of the NSACF 77 in accordance with the software stored in a memory 774. The Software may be pre-installed in the memory 774 and / or may be downloaded via the telecommunication network or from a removable data storage device (e.g. a removable memory device (RMD)), for example. The software includes, among other things, an operating system 7741 and a communications control module 7742 having at least a transceiver control module 77421. The communications control module 7742 (using its transceiver control module 77421) is responsible for handling (generating / sending / receiving) signalling between the NSACF 77 and other nodes, such as the AMF 70 and other core network nodes (including core network nodes in the HPLMN of the UE 3 when the UE 3 is roaming-in). Such signalling may include, for example, appropriately formatted signalling messages (e.g. a HTTP restful methods based on the service based interfaces) relating to network data analytics function procedures (for the UE 3).

[0368] The NSACF 77 may support the Non-Public Network (NPN), The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN). The NSACF in this disclosure may have same components to the NSACF 77.

[0369] EECF 　　Fig. 29 is a block diagram illustrating the main components of the EECF 78. As shown, the apparatus includes a transceiver circuit 781 which is operable to transmit signals to and to receive signals from other nodes (including the AMF 70) via a network interface 782. A controller 783 controls the operation of the EECF 78 in accordance with the software stored in a memory 784. The Software may be pre-installed in the memory 784 and / or may be downloaded via the telecommunication network or from a removable data storage device (e.g. a removable memory device (RMD)), for example. The software includes, among other things, an operating system 7841 and a communications control module 7842 having at least a transceiver control module 78421. The communications control module 7842 (using its transceiver control module 78421) is responsible for handling (generating / sending / receiving) signalling between the EECF 78 and other nodes, such as the AMF 70 and other core network nodes (including core network nodes in the HPLMN of the UE 3 when the UE 3 is roaming-in). Such signalling may include, for example, appropriately formatted signalling messages (e.g. a HTTP restful methods based on the service based interfaces) relating to network data analytics function procedures (for the UE 3).

[0370] The EECF 78 may support the Non-Public Network (NPN), The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN). The EECF in this disclosure may have same components to the EECF 78.

[0371] NEF 　　Fig. 30 is a block diagram illustrating the main components of the NEF 79. As shown, the apparatus includes a transceiver circuit 791 which is operable to transmit signals to and to receive signals from other nodes (including the AMF 70) via a network interface 792. A controller 793 controls the operation of the NEF 79 in accordance with the software stored in a memory 794. The Software may be pre-installed in the memory 794 and / or may be downloaded via the telecommunication network or from a removable data storage device (e.g. a removable memory device (RMD)), for example. The software includes, among other things, an operating system 7941 and a communications control module 7942 having at least a transceiver control module 79421. The communications control module 7942 (using its transceiver control module 79421) is responsible for handling (generating / sending / receiving) signalling between the NEF 79 and other nodes, such as the AMF 70 and other core network nodes (including core network nodes in the HPLMN of the UE 3 when the UE 3 is roaming-in). Such signalling may include, for example, appropriately formatted signalling messages (e.g. a HTTP restful methods based on the service based interfaces) relating to network data analytics function procedures (for the UE 3).

[0372] The NEF 79 may support the Non-Public Network (NPN), The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN). The NEF in this disclosure may have same components to the NEF 79.

[0373] OAM 　　Fig. 31 is a block diagram illustrating the main components of the OAM 80. As shown, the apparatus includes a transceiver circuit 801 which is operable to transmit signals to and to receive signals from other nodes (including the AMF 70) via a network interface 802. A controller 803 controls the operation of the OAM 80 in accordance with the software stored in a memory 804. The Software may be pre-installed in the memory 804 and / or may be downloaded via the telecommunication network or from a removable data storage device (e.g. a removable memory device (RMD)), for example. The software includes, among other things, an operating system 8041 and a communications control module 8042 having at least a transceiver control module 80421. The communications control module 8042 (using its transceiver control module 80421) is responsible for handling (generating / sending / receiving) signalling between the OAM 80 and other nodes, such as the AMF 70 and other core network nodes (including core network nodes in the HPLMN of the UE 3 when the UE 3 is roaming-in). Such signalling may include, for example, appropriately formatted signalling messages (e.g. a HTTP restful methods based on the service based interfaces) relating to network data analytics function procedures (for the UE 3). 　　The OAM 80 may support the Non-Public Network (NPN), The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN). The OAM in this disclosure may have same components to the OAM 80.

[0374] AF 　　Fig. 32 is a block diagram illustrating the main components of the AF 201. As shown, the apparatus includes a transceiver circuit 2011 which is operable to transmit signals to and to receive signals from other nodes (including the UE 3) via a network interface 2012. A controller 2013 controls the operation of the AF 201 in accordance with software stored in a memory 2014. Software may be pre-installed in the memory 2014 and / or may be downloaded via the telecommunication network or from a removable data storage device (e.g. a removable memory device (RMD)), for example. The software includes, among other things, an operating system 20141 and a communications control module 20142 having at least a transceiver control module 201421. The communications control module 20142 (using its transceiver control module 201421) is responsible for handling (generating / sending / receiving) signalling between the AF 201 and other nodes, such as the UE 3 and other core network nodes (including core network nodes in the HPLMN of the UE 3 when the UE 3 is roaming-in). Such signalling may include, for example, appropriately formatted signalling messages (e.g. a HTTP restful methods based on the service based interfaces) relating to policy management procedures (for the UE 3).

[0375] The AF 201 may support the Non-Public Network (NPN), The NPN may be a Stand-alone Non-Public Network (SNPN) or a Public Network Integrated NPN (PNI-NPN). The AF in this disclosure may have same components to the AF 201.

[0376] Modifications and Alternatives 　　Detailed aspects have been described above. As those skilled in the art will appreciate, a number of modifications and alternatives can be made to the above aspects whilst still benefiting from the disclosures embodied therein. By way of illustration only a number of these alternatives and modifications will now be described. 　　In the above description, the UE 3 and the network apparatus are described for ease of understanding as having a number of discrete modules (such as the communication control modules). Whilst these modules may be provided in this way for certain applications, for example where an existing system has been modified to implement the disclosure, in other applications, for example in systems designed with the inventive features in mind from the outset, these modules may be built into the overall operating system or code and so these modules may not be discernible as discrete entities. These modules may also be implemented in software, hardware, firmware or a mix of these.

[0377] Each controller may comprise any suitable form of processing circuitry including (but not limited to), for example: one or more hardware implemented computer processors; microprocessors; central processing units (CPUs); arithmetic logic units (ALUs); input / output (IO) circuits; internal memories / caches (program and / or data); processing registers; communication buses (e.g. control, data and / or address buses); direct memory access (DMA) functions, hardware or software implemented counters, pointers and / or timers; and / or the like. In the above aspects, a number of software modules were described. As those skilled in the art will appreciate, the software modules may be provided in compiled or un-compiled form and may be supplied to the UE 3 and the network apparatus as a signal over a computer network, or on a recording medium. Further, the functionality performed by part or all of this software may be performed using one or more dedicated hardware circuits. However, the use of software modules is preferred as it facilitates the updating of the UE 3 and the network apparatus in order to update their functionalities. 　　In the above aspects, a 3GPP radio communications (radio access) technology is used. However, any other radio communications technology (e.g. WLAN, Wi-Fi, WiMAX, Bluetooth, etc.) and other fix line communications technology (e.g. BBF Access, Cable Access, optical access, etc.) may also be used in accordance with the above aspects.

[0378] Items of user equipment might include, for example, communication devices such as mobile telephones, smartphones, user equipment, personal digital assistants, laptop / tablet computers, web browsers, e-book readers and / or the like. Such mobile (or even generally stationary) devices are typically operated by a user, although it is also possible to connect so-called 'Internet of Things' (IoT) devices and similar machine-type communication (MTC) devices to the network. For simplicity, the present application refers to mobile devices (or UEs) in the description but it will be appreciated that the technology described can be implemented on any communication devices (mobile and / or generally stationary) that can connect to a communications network for sending / receiving data, regardless of whether such communication devices are controlled by human input or software instructions stored in memory. 　　Various other modifications will be apparent to those skilled in the art and will not be described in further detail here.

[0379] As will be appreciated by one of skill in the art, the present disclosure may be embodied as a method, and system. Accordingly, the present disclosure may take the form of an entirely hardware embodiment, a software embodiment or an embodiment combining software and hardware aspects.

[0380] It will be understood that each block of the block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general-purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a plurality of microprocessors, one or more microprocessors, or any other such configuration.

[0381] The methods or algorithms described in connection with the examples disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. A storage medium may be coupled to the processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC.

[0382] The previous description of the disclosed examples is provided to enable any person skilled in the art to make or use the present disclosure. Various modifications to these examples will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other examples without departing from the spirit or scope of the disclosure. Thus, the present disclosure is not intended to be limited to the examples shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

[0383] While the disclosure has been particularly shown and described with reference to exemplary Aspects thereof, the disclosure is not limited to these Aspects. It will be understood by those of ordinary skill in the art that various changes in form and details may be made therein without departing from the spirit and scope of the present disclosure as defined by this document. For example, the Aspects above are not limited to 5GS, and the Aspects are also applicable to communication system other than 5GS (e.g., 6G system, 5G beyond system).

[0384] Supplementary notes 　　The whole or part of the example Aspects disclosed above can be described as, but not limited to, the following supplementary notes.

[0385] <First Supplementary notes> 　　Supplementary note 1. A method of a communication apparatus comprising: 　　communicating with another communication apparatus; and 　　receiving information related to energy usage to the another communication apparatus.

[0386] Supplementary note 2. A method of a communication apparatus comprising: 　　communicating with another communication apparatus; and 　　sending information related to energy usage to the another communication apparatus.

[0387] Supplementary note 3. A communication apparatus comprising: 　　means for communicating with another communication apparatus; and 　　means for receiving information related to energy usage to the another communication apparatus.

[0388] Supplementary note 4. A communication apparatus comprising: 　　means for communicating with another communication apparatus; and 　　means for sending information related to energy usage to the another communication apparatus.

[0389] <Second Supplementary notes> 　　Supplementary note 1. A method of a communication apparatus comprising: 　　communicating with another communication apparatus; and 　　receiving first information related to energy usage to the another communication apparatus, wherein the communication apparatus receives the first information based on second information related to the energy usage, wherein the second information is provided by an application server.

[0390] Supplementary note 2. A method of a communication apparatus comprising: 　　communicating with another communication apparatus; and 　　sending first information related to energy usage to the another communication apparatus, wherein the communication apparatus sends the first information based on second information related to the energy usage, wherein the second information is provided by an application server.

[0391] Supplementary note 3. A method of a communication apparatus comprising: 　　communicating with another communication apparatus, 　　sending, to the another communication apparatus, a request message with report timing information related to a load level, 　　receiving, from the another communication apparatus, a response message corresponds to the request message, 　　receiving, from the another communication apparatus, a message including load information, after receiving the response message, 　　determining the load level based on the load information and threshold value; and 　　sending, to the another communication apparatus, an indication to move to energy saving state or non-energy saving state after the determining the load level.

[0392] Supplementary note 4. A method of a communication apparatus comprising: 　　communicating with another communication apparatus; 　　receiving, from the another communication apparatus, a request message with report timing information related to a load level, 　　sending, to the another communication apparatus, a response message corresponds to the request message, 　　determining the report timing based on the report timing information, 　　sending, to the another communication apparatus, a message including load information, receiving, from the another communication apparatus, an indication to move to energy saving state or not energy saving state; and activating energy saving mode or non-energy saving mode based on the indication.

[0393] Supplementary note 5. A method of a first communication apparatus comprising: 　　communicating with a second communication apparatus, 　　sending, to the second communication apparatus, a request message with report timing information related to a load level, 　　receiving, from the second communication apparatus, a response message corresponds to the request message, 　　receiving, from the second communication apparatus, a message including load information, after receiving the response message, 　　determining the load level based on the load information and threshold value; and 　　sending, to a third communication apparatus, an indication to move to energy saving state or non-energy saving state after the determining the load level.

[0394] Supplementary note 6. A method of a second communication apparatus comprising: 　　communicating with a first communication apparatus; 　　receiving, from the first communication apparatus, a request message with report timing information related to a load level, 　　sending, to the first communication apparatus, a response message corresponds to the request message, 　　determining the report timing based on the report timing information; and 　　sending, to the first communication apparatus, a message including load information.

[0395] Supplementary note 7. A method of a communication apparatus comprising: 　　sending, to another communication apparatus, a request message including ID related to energy usage, information for an energy usage entity, request information for a report of energy usage information for report period, information for User Equipment (UE) and at least one of Protocol Data Unit (PDU) session ID and Single Network Slice Selection Assistance Information (S-NSSAI), 　　receiving, from the another communication apparatus, a response message corresponds to the request message; and 　　receiving, from the another communication apparatus, a message including the ID related to energy usage, the information for the energy usage entity, the report of energy usage and location information.

[0396] Supplementary note 8. A method of a communication apparatus comprising: 　　receiving, from the another communication apparatus, a request message including ID related to energy usage, information for an energy usage entity, request information for a report of energy usage, information for report period, information for User Equipment (UE) and at least one of Protocol Data Unit (PDU) session ID and Single Network Slice Selection Assistance Information (S-NSSAI), 　　sending, to the another communication apparatus, a response message corresponds to the request message, 　　evaluating energy efficiency per network level, Core Node (CN) level, Radio Access Networks (RAN) level, Network Function (NF)level, Single Network Slice Selection Assistance Information (S-NSSAI) level, or Protocol Data Unit (PDU) Session level; and 　　sending, to the another communication apparatus, a message including the ID related to energy usage, the information for the energy usage entity, the report of energy usage and location information.

[0397] Supplementary note 9. A method of an Access and Mobility Function (AMF) comprising: 　　sending, to a Radio Access Network (RAN), a message including ID related to energy usage, information for an energy usage entity, request information for a report of energy usage, information for report period, information for User Equipment (UE) and at least one of Protocol Data Unit (PDU) session ID and Single Network Slice Selection Assistance Information (S-NSSAI); and 　　receiving, from the RAN, a message including the ID related to energy usage, the information for the energy usage entity, the report of energy usage and location information.

[0398] Supplementary note 10. A method of a Radio Access Network (RAN) comprising: 　　receiving, from an Access and Mobility Function (AMF), a message including ID related to energy usage, information for an energy usage entity, request information for a report of energy usage, information for report period, information for a User Equipment (UE) and at least one of Protocol Data Unit (PDU) session ID and Single Network Slice Selection Assistance Information (S-NSSAI), 　　sending, to the AMF, a response message corresponds to the received message, 　　evaluating energy efficiency per network level, Core Node (CN) level, Radio Access Networks (RAN) level, Network Function (NF)level, Single Network Slice Selection Assistance Information (S-NSSAI) level, or Protocol Data Unit (PDU) Session level; and 　　sending, to the AMF, a message including the ID related to energy usage, the information for the energy usage entity, the report of energy usage and location information.

[0399] Supplementary note 11. A method of a gNB CU-CP comprising: 　　sending, to a gNB DU, a message including ID related to energy usage, information for an energy usage entity, request information for a report of energy usage, information for report period, information for a User Equipment (UE) and at least one of Protocol Data Unit (PDU) session ID and Single Network Slice Selection Assistance Information (S-NSSAI); and 　　receiving, from the gNB DU, communication apparatus, a message including the ID related to energy usage, the report of energy usage, the information for the energy usage entity and location information.

[0400] Supplementary note 12. A method of a gNB DU comprising: 　　receiving, from a gNB CU-CP, a message including ID related to energy usage, information for an energy usage entity, request information for a report of energy usage, information for report period, information for a User Equipment (UE) and at least one of Protocol Data Unit (PDU) session ID and Single Network Slice Selection Assistance Information (S-NSSAI), 　　sending, to the gNB CU-CP, a response message corresponds to the received message, 　　evaluating energy efficiency per network level, Core Node (CN) level, Radio Access Networks (RAN) level, Network Function (NF) level, Single Network Slice Selection Assistance Information (S-NSSAI) level, or Protocol Data Unit (PDU) Session level; and 　　sending, to the gNB CU-CP, a message including the ID related to energy usage, the report of energy usage, the information for the energy usage entity and location information.

[0401] Supplementary note 13. A method of a gNB CU-CP comprising: 　　sending, to a gNB CU-UP, a message including ID related to energy usage, information for an energy usage entity, request information for a report of energy usage, information for report period, information for a User Equipment (UE) and at least one of Protocol Data Unit (PDU) session ID and Single Network Slice Selection Assistance Information (S-NSSAI); and 　　receiving, from the gNB CU-UP, communication apparatus, a message including the ID related to energy usage, the report of energy usage, the information for the energy usage entity and location information.

[0402] Supplementary note 14. A method of a gNB CU-UP comprising: 　　receiving, from a gNB CU-CP, a message including ID related to energy usage, information for an energy usage entity, request information for a report of energy usage, information for report period, information for a User Equipment (UE) and at least one of Protocol Data Unit (PDU) session ID and Single Network Slice Selection Assistance Information (S-NSSAI), 　　sending, to the gNB CU-CP, a response message corresponds to the received message, 　　evaluating energy efficiency per network level, Core Node (CN) level, Radio Access Networks (RAN) level, Network Function (NF) level, Single Network Slice Selection Assistance Information (S-NSSAI) level, or Protocol Data Unit (PDU) Session level; and 　　sending, to the gNB CU-CP, a message including the ID related to energy usage, the report of energy usage, the information for the energy usage entity and location information.

[0403] Supplementary note 15. A method of a Unified Data management Function (UDM) comprising: 　　allocating a User Equipment (UE) for energy efficiency management, receiving, from an Access and Mobility Function (AMF), a request message including information indicating support for energy efficiency management, 　　sending, to the AMF, response message corresponds to the request message; and 　　sending, to a Policy Control Function (PCF), a message including information related to energy usage.

[0404] Supplementary note 16. A method of a Policy Control Function (PCF) comprising: 　　receiving, from a Unified Data management Function (UDM), a message including first information related to energy usage, 　　storing the first information; and 　　sending, to an Access and Mobility Function (AMF), second information related to energy usage.

[0405] Supplementary note 17. A method of an Access and Mobility Function (AMF) comprising: 　　receiving, from a UE, a message including information indicating support for energy efficiency management, 　　sending, to a Unified Data management Function (UDM), a request message including information indicating support for energy efficiency management, 　　receiving, from the UDM, a response message corresponds to the request message, receiving, from a Policy Control Function (PCF), information related to energy usage; and 　　sending, to a User Equipment (UE), at least one of information for amount of energy usage, information related to energy shortage and timer.

[0406] Supplementary note 18. A method of a User Equipment (UE) comprising: 　　sending, to an Access and Mobility Function (AMF), a message including information indicating support for energy efficiency management; and 　　receiving, from the AMF, at least one of information for amount of energy usage, information related to energy shortage and timer.

[0407] Supplementary note 19. A method of a Unified Data management Function (UDM), comprising: 　　receiving, from a Policy Control Function (PCF), a message including information indicating support for energy efficiency management; and 　　sending, to the PCF, a message including information related to energy usage.

[0408] Supplementary note 20. A method of a User Equipment (UE) comprising: 　　sending, to an Access and Mobility Function (AMF), Protocol Data Unit (PDU) session request message comprising information indicating support for energy efficiency management; and 　　receiving, from the AMF, energy usage information.

[0409] Supplementary note 21. A method of an Access and Mobility Function (AMF) comprising: 　　receiving, from a User Equipment (UE), Protocol Data Unit (PDU) session establishment request message including information indicating support for energy efficiency management, 　　sending, to a Session Management Function (SMF), a request message including the information indicating support for energy efficiency management, 　　receiving, from the SMF, response message corresponds to the request message; and 　　receiving, from a Policy Control Function (PCF), information indicating the PDU session is rejected with first energy management information.

[0410] Supplementary note 22. A method of an Access and Mobility Function (AMF) comprising: 　　receiving, from a User Equipment (UE), Protocol Data Unit (PDU) session establishment request message including information indicating support for energy efficiency management, 　　sending, to a Session Management Function (SMF), a request message including the information indicating support for energy efficiency management, 　　receiving, from the SMF, response message corresponds to the request message; and 　　receiving, from a Policy Control Function (PCF), information indicating second energy management information.

[0411] Supplementary note 23. A method of a Policy Control Function (PCF) comprising: 　　receiving, from a Session Management Function (SMF), a first message including information indicating support for energy efficiency management, 　　sending, to a Unified Data management Function (UDM), a second message including the information indicating support for energy efficiency management, 　　receiving, from the UDM, a message including information related to energy usage, 　　storing, the information related to energy usage; and 　　sending, to an Access and Mobility Function (AMF), information indicating the PDU session is rejected with first energy management information.

[0412] Supplementary note 24. A method of a Policy Control Function (PCF) comprising: 　　receiving, from a Session Management Function (SMF), a first message including information indicating support for energy efficiency management, 　　sending, to a Unified Data management Function (UDM), a second message including the information indicating support for energy efficiency management, 　　receiving, from the UDM, a message including information related to energy usage, 　　storing, the information related to energy usage, 　　sending, to the SMF, a response message corresponds to the first message, 　　receiving, from a Charging Function (CHF), energy usage information for a Protocol Data Unit (PDU) session, 　　updating information for energy usage based on the energy usage information for the PDU session, 　　sending, to an Access and Mobility Function (AMF), information indicating second energy management information; and 　　sending, to a Network Exposure Function (NEF) a message indicating energy usage exposure.

[0413] Supplementary note 25. A communication apparatus comprising: 　　means for communicating with another communication apparatus; and 　　means for receiving first information related to energy usage to the another communication apparatus, wherein the communication apparatus receives the first information based on second information related to the energy usage, wherein the second information is provided by an application server.

[0414] Supplementary note 26. A communication apparatus comprising: 　　means for communicating with another communication apparatus; and 　　means for sending first information related to energy usage to the another communication apparatus, wherein the communication apparatus sends the first information based on second information related to the energy usage, wherein the second information is provided by an application server.

[0415] Supplementary note 27. A communication apparatus comprising: 　　means for communicating with another communication apparatus, 　　means for sending, to the another communication apparatus, a request message with report timing information related to a load level, 　　means for receiving, from the another communication apparatus, a response message corresponds to the request message, 　　means for receiving, from the another communication apparatus, a message including load information, after receiving the response message, 　　means for determining the load level based on the load information and threshold value; and 　　means for sending, to the another communication apparatus, an indication to move to energy saving state or non-energy saving state after the determining the load level.

[0416] Supplementary note 28. A communication apparatus comprising: 　　means for communicating with another communication apparatus; 　　means for receiving, from the another communication apparatus, a request message with report timing information related to a load level, 　　means for sending, to the another communication apparatus, a response message corresponds to the request message, 　　means for determining the report timing based on the report timing information, 　　means for sending, to the another communication apparatus, a message including load information, 　　means for receiving, from the another communication apparatus, an indication to move to energy saving state or not energy saving state; and 　　means for activating energy saving mode or non-energy saving mode based on the indication.

[0417] Supplementary note 29. A first communication apparatus comprising: 　　means for communicating with a second communication apparatus, 　　means for sending, to the second communication apparatus, a request message with report timing information related to a load level, 　　means for receiving, from the second communication apparatus, a response message corresponds to the request message, 　　means for receiving, from the second communication apparatus, a message including load information, after receiving the response message, 　　means for determining the load level based on the load information and threshold value; and 　　means for sending, to a third communication apparatus, an indication to move to energy saving state or non-energy saving state after the determining the load level.

[0418] Supplementary note 30. A second communication apparatus comprising: 　　means for communicating with a first communication apparatus; 　　means for receiving, from the first communication apparatus, a request message with report timing information related to a load level, 　　means for sending, to the first communication apparatus, a response message corresponds to the request message, 　　means for determining the report timing based on the report timing information; and 　　means for sending, to the first communication apparatus, a message including load information.

[0419] Supplementary note 31. A communication apparatus comprising: 　　means for sending, to another communication apparatus, a request message including ID related to energy usage, information for an energy usage entity, request information for a report of energy usage information for report period, information for User Equipment (UE) and at least one of Protocol Data Unit (PDU) session ID and Single Network Slice Selection Assistance Information (S-NSSAI), 　　means for receiving, from the another communication apparatus, a response message corresponds to the request message; and 　　means for receiving, from the another communication apparatus, a message including the ID related to energy usage, the information for the energy usage entity, the report of energy usage and location information.

[0420] Supplementary note 32. A communication apparatus comprising: 　　means for receiving, from the another communication apparatus, a request message including ID related to energy usage, information for an energy usage entity, request information for a report of energy usage, information for report period, information for User Equipment (UE) and at least one of Protocol Data Unit (PDU) session ID and Single Network Slice Selection Assistance Information (S-NSSAI), 　　means for sending, to the another communication apparatus, a response message corresponds to the request message, 　　means for evaluating energy efficiency per network level, Core Node (CN) level, Radio Access Networks (RAN) level, Network Function (NF)level, Single Network Slice Selection Assistance Information (S-NSSAI) level, or Protocol Data Unit (PDU) Session level; and 　　means for sending, to the another communication apparatus, a message including the ID related to energy usage, the information for the energy usage entity, the report of energy usage and location information.

[0421] Supplementary note 33. An Access and Mobility Function (AMF) comprising: means for sending, to a Radio Access Network (RAN), a message including ID related to energy usage, information for an energy usage entity, request information for a report of energy usage, information for report period, information for User Equipment (UE) and at least one of Protocol Data Unit (PDU) session ID and Single Network Slice Selection Assistance Information (S-NSSAI); and 　　means for receiving, from the RAN, a message including the ID related to energy usage, the information for the energy usage entity, the report of energy usage and location information.

[0422] Supplementary note 34. A Radio Access Network (RAN) comprising: 　　means for receiving, from an Access and Mobility Function (AMF), a message including ID related to energy usage, information for an energy usage entity, request information for a report of energy usage, information for report period, information for a User Equipment (UE) and at least one of Protocol Data Unit (PDU) session ID and Single Network Slice Selection Assistance Information (S-NSSAI), 　　means for sending, to the AMF, a response message corresponds to the received message, 　　means for evaluating energy efficiency per network level, Core Node (CN) level, Radio Access Networks (RAN) level, Network Function (NF)level, Single Network Slice Selection Assistance Information (S-NSSAI) level, or Protocol Data Unit (PDU) Session level; and 　　means for sending, to the AMF, a message including the ID related to energy usage, the information for the energy usage entity, the report of energy usage and location information.

[0423] Supplementary note 35. A gNB CU-CP comprising: 　　means for sending, to a gNB DU, a message including ID related to energy usage, information for an energy usage entity, request information for a report of energy usage, information for report period, information for a User Equipment (UE) and at least one of Protocol Data Unit (PDU) session ID and Single Network Slice Selection Assistance Information (S-NSSAI); and 　　means for receiving, from the gNB DU, communication apparatus, a message including the ID related to energy usage, the report of energy usage, the information for the energy usage entity and location information.

[0424] Supplementary note 36. A gNB DU comprising: 　　means for receiving, from a gNB CU-CP, a message including ID related to energy usage, information for an energy usage entity, request information for a report of energy usage, information for report period, information for a User Equipment (UE) and at least one of Protocol Data Unit (PDU) session ID and Single Network Slice Selection Assistance Information (S-NSSAI), 　　means for sending, to the gNB CU-CP, a response message corresponds to the received message, 　　means for evaluating energy efficiency per network level, Core Node (CN) level, Radio Access Networks (RAN) level, Network Function (NF) level, Single Network Slice Selection Assistance Information (S-NSSAI) level, or Protocol Data Unit (PDU) Session level; and 　　means for sending, to the gNB CU-CP, a message including the ID related to energy usage, the report of energy usage, the information for the energy usage entity and location information.

[0425] Supplementary note 37. A gNB CU-CP comprising: 　　means for sending, to a gNB CU-UP, a message including ID related to energy usage, information for an energy usage entity, request information for a report of energy usage, information for report period, information for a User Equipment (UE) and at least one of Protocol Data Unit (PDU) session ID and Single Network Slice Selection Assistance Information (S-NSSAI); and 　　means for receiving, from the gNB CU-UP, communication apparatus, a message including the ID related to energy usage, the report of energy usage, the information for the energy usage entity and location information.

[0426] Supplementary note 38. A gNB CU-UP comprising: 　　means for receiving, from a gNB CU-CP, a message including ID related to energy usage, information for an energy usage entity, request information for a report of energy usage, information for report period, information for a User Equipment (UE) and at least one of Protocol Data Unit (PDU) session ID and Single Network Slice Selection Assistance Information (S-NSSAI), 　　means for sending, to the gNB CU-CP, a response message corresponds to the received message, 　　means for evaluating energy efficiency per network level, Core Node (CN) level, Radio Access Networks (RAN) level, Network Function (NF) level, Single Network Slice Selection Assistance Information (S-NSSAI) level, or Protocol Data Unit (PDU) Session level; and 　　means for sending, to the gNB CU-CP, a message including the ID related to energy usage, the report of energy usage, the information for the energy usage entity and location information.

[0427] Supplementary note 39 A Unified Data management Function (UDM) comprising: 　　means for allocating a User Equipment (UE) for energy efficiency management, means for receiving, from an Access and Mobility Function (AMF), a request message including information indicating support for energy efficiency management, means for sending, to the AMF, response message corresponds to the request message; and 　　means for sending, to a Policy Control Function (PCF), a message including information related to energy usage.

[0428] Supplementary note 40. A Policy Control Function (PCF) comprising: means for receiving, from a Unified Data management Function (UDM), a message including first information related to energy usage, 　　means for storing the first information; and 　　means for sending, to an Access and Mobility Function (AMF), second information related to energy usage.

[0429] Supplementary note 41. An Access and Mobility Function (AMF) comprising: 　　means for receiving, from a UE, a message including information indicating support for energy efficiency management, 　　means for sending, to a Unified Data management Function (UDM), a request message including information indicating support for energy efficiency management, 　　means for receiving, from the UDM, a response message corresponds to the request message, 　　means for receiving, from a Policy Control Function (PCF), information related to energy usage; and 　　means for sending, to a User Equipment (UE), at least one of information for amount of energy usage, information related to energy shortage and timer.

[0430] Supplementary note 42. A User Equipment (UE) comprising: 　　means for sending, to an Access and Mobility Function (AMF), a message including information indicating support for energy efficiency management; and 　　receiving, from the AMF, at least one of information for amount of energy usage, information related to energy shortage and timer.

[0431] Supplementary note 43. A Unified Data management Function (UDM), comprising: 　　means for receiving, from a Policy Control Function (PCF), a message including information indicating support for energy efficiency management; and 　　means for sending, to the PCF, a message including information related to energy usage.

[0432] Supplementary note 44. A User Equipment (UE) comprising: 　　means for sending, to an Access and Mobility Function (AMF), Protocol Data Unit (PDU) session request message comprising information indicating support for energy efficiency management; and 　　means for receiving, from the AMF, energy usage information.

[0433] Supplementary note 45. An Access and Mobility Function (AMF) comprising: 　　means for receiving, from a User Equipment (UE), Protocol Data Unit (PDU) session establishment request message including information indicating support for energy efficiency management, 　　means for sending, to a Session Management Function (SMF), a request message including the information indicating support for energy efficiency management, 　　means for receiving, from the SMF, response message corresponds to the request message; and 　　means for receiving, from a Policy Control Function (PCF), information indicating the PDU session is rejected with first energy management information.

[0434] Supplementary note 46. An Access and Mobility Function (AMF) comprising: 　　means for receiving, from a User Equipment (UE), Protocol Data Unit (PDU) session establishment request message including information indicating support for energy efficiency management, 　　means for sending, to a Session Management Function (SMF), a request message including the information indicating support for energy efficiency management, 　　means for receiving, from the SMF, response message corresponds to the request message; and 　　means for receiving, from a Policy Control Function (PCF), information indicating second energy management information.

[0435] Supplementary note 47. A Policy Control Function (PCF) comprising: 　　means for receiving, from a Session Management Function (SMF), a first message including information indicating support for energy efficiency management, 　　means for sending, to a Unified Data management Function (UDM), a second message including the information indicating support for energy efficiency management, 　　means for receiving, from the UDM, a message including information related to energy usage, 　　means for storing, the information related to energy usage; and 　　means for sending, to an Access and Mobility Function (AMF), information indicating the PDU session is rejected with first energy management information.

[0436] Supplementary note 48. A Policy Control Function (PCF) comprising: 　　means for receiving, from a Session Management Function (SMF), a first message including information indicating support for energy efficiency management, 　　means for sending, to a Unified Data management Function (UDM), a second message including the information indicating support for energy efficiency management, 　　means for receiving, from the UDM, a message including information related to energy usage, 　　means for storing, the information related to energy usage, 　　means for sending, to the SMF, a response message corresponds to the first message, 　　means for receiving, from a Charging Function (CHF), energy usage information for a Protocol Data Unit (PDU) session, 　　means for updating information for energy usage based on the energy usage information for the PDU session, 　　means for sending, to an Access and Mobility Function (AMF), information indicating second energy management information; and means for sending, to a Network Exposure Function (NEF) a message indicating energy usage exposure.

[0437] <Third Supplementary notes> 　　Supplementary note 1. A method of a User Equipment (UE) comprising: 　　communicating with a communication apparatus; and 　　receiving information related to a shutdown of a Radio Access Network (RAN).

[0438] Supplementary note 2. The method according to supplementary note 1, further comprising: 　　wherein the information related to the shutdown of the RAN is received in a first cell, 　　selecting a second cell in a case of receiving the information related to the shutdown of the RAN.

[0439] Supplementary note 3. The method according to supplementary note 2, further comprising: 　　receiving information related to resuming of the RAN, 　　selecting the first cell in a case of receiving the information related to resuming of the RAN.

[0440] Supplementary note 4. A method of a communication apparatus comprising: 　　communicating with a User Equipment (UE); and 　　sending information related to a shutdown of a Radio Access Network (RAN).

[0441] Supplementary note 5. A method of a communication apparatus comprising: 　　communicating with a User Equipment (UE); and 　　sending information related to resuming of a Radio Access Network (RAN).

[0442] Supplementary note 6. A method of a communication apparatus comprising: 　　sending information related to a shutdown of a Radio Access Network (RAN); and 　　receiving a message related to a handover of a User Equipment (UE) in a case of sending the information.

[0443] Supplementary note 7. A method of a communication apparatus comprising: 　　receiving information related to a shutdown of a Radio Access Network (RAN); and 　　sending a message related to a handover of a User Equipment (UE) in a case of receiving the information.

[0444] Supplementary note 8. A method of a communication apparatus comprising: 　　communicating with another communication apparatus; and 　　performing a procedure related to a handover of a User Equipment (UE) in case of a shutdown of a Radio Access Network (RAN).

[0445] Supplementary note 9. A User Equipment (UE) comprising: 　　means for communicating with a communication apparatus; and 　　means for receiving information related to a shutdown of a Radio Access Network (RAN).

[0446] Supplementary note 10. The UE according to supplementary note 9, further comprising: 　　wherein the information related to the shutdown of the RAN is received in a first cell, 　　means for selecting a second cell in a case of receiving the information related to the shutdown of the RAN.

[0447] Supplementary note 11. The UE according to supplementary note 10, further comprising: 　　receiving information related to resuming of the RAN, 　　selecting the first cell in a case of receiving the information related to resuming of the RAN.

[0448] Supplementary note 12. A communication apparatus comprising: 　　means for communicating with a User Equipment (UE); and 　　means for sending information related to a shutdown of a Radio Access Network (RAN).

[0449] Supplementary note 13. A communication apparatus comprising: 　　means for communicating with a User Equipment (UE); and 　　means for sending information related to resuming of a Radio Access Network (RAN).

[0450] Supplementary note 14. A communication apparatus comprising: 　　means for sending information related to a shutdown of a Radio Access Network (RAN); and 　　means for receiving a message related to a handover of a User Equipment (UE) in a case of sending the information.

[0451] Supplementary note 15. A communication apparatus comprising: 　　means for receiving information related to a shutdown of a Radio Access Network (RAN); and 　　means for sending a message related to a handover of a User Equipment (UE) in a case of receiving the information.

[0452] Supplementary note 16. A communication apparatus comprising: 　　means for communicating with another communication apparatus; and 　　means for performing a procedure related to a handover of a User Equipment (UE) in case of a shutdown of a Radio Access Network (RAN).

[0453] This application is based upon and claims the benefit of priority from Indian patent applications No. 202311072738, filed on October 25, 2023, the disclosure of which is incorporated herein in its entirety by reference.

[0454] 3　　UE 31　　transceiver circuit 32　　antenna 33　　controller 34　　user interface 35　　USIM 36　　memory 361　　operating system 362　　communications control module 3621　　transceiver control module 5　　gNB, (R)AN node 501　　RAN-1 502　　RAN-2 51　　transceiver circuit 52　　antenna 53　　network interface 54　　controller 55　　memory 551　　operating system 552　　communications control module 5521　　transceiver control module 60　　RU 601　　transceiver circuit 602　　antenna 603　　network interface 604　　controller 605　　memory 6051　　operating system 6052　　communications control module 60521　　transceiver control module 61　　DU 611　　transceiver circuit 612　　network interface 613　　controller 614　　memory 6141　　operating system 6142　　communications control module 61421　　transceiver control module 62　　CU 6201　　CU-CP 6202　　CU-UP 621　　transceiver circuit 622　　network interface 623　　controller 624　　memory 6241　　operating system 6242　　communications control module 62421　　transceiver control module 7　　core network 70　　AMF 7001　　AMF-1 7002　　AMF-2 701　　transceiver circuit 702　　network interface 703　　controller 704　　memory 7041　　operating system 7042　　communications control module 70421　　transceiver control module 71　　SMF 711　　transceiver circuit 712　　network interface 713　　controller 714　　memory 7141　　operating system 7142　　communications control module 71421　　transceiver control module 72　　UPF 721　　transceiver circuit 722　　network interface 723　　controller 724　　memory 7241　　operating system 7242　　communications control module 72421　　transceiver control module 73　　PCF 731　　transceiver circuit 732　　network interface 733　　controller 734　　memory 7341　　operating system 7342　　communications control module 73421　　transceiver control module 74　　NWDAF 741　　transceiver circuit 742　　network interface 743　　controller 744　　memory 7441　　operating system 7442　　communications control module 74421　　transceiver control module 75　　UDM 7501　　UDM-1 7502　　UDM-2 751　　transceiver circuit 752　　network interface 753　　controller 754　　memory 7541　　operating system 7542　　communications control module 75421　　transceiver control module 76　　CHF 761　　transceiver circuit 762　　network interface 763　　controller 764　　memory 7641　　operating system 7642　　communications control module 76421　　transceiver control module 77　　NSACF 771　　transceiver circuit 772　　network interface 773　　controller 774　　memory 7741　　operating system 7742　　communications control module 77421　　transceiver control module 78　　EECF 781　　transceiver circuit 782　　network interface 783　　controller 784　　memory 7841　　operating system 7842　　communications control module 78421　　transceiver control module 79　　NEF 791　　transceiver circuit 792　　network interface 793　　controller 794　　memory 7941　　operating system 7942　　communications control module 79421　　transceiver control module 80　　OAM 8001　　OAM-1 8002　　OAM-2 801　　transceiver circuit 802　　network interface 803　　controller 804　　memory 8041　　operating system 8042　　communications control module 80421　　transceiver control module 20　　data network 201　　AF 2011　　transceiver circuit 2012　　network interface 2013　　controller 2014　　memory 20141　　operating system 20142　　communications control module 201421　　transceiver control module

Claims

1. A method of a User Equipment (UE) comprising: 　　communicating with a communication apparatus; and 　　receiving information related to a shutdown of a Radio Access Network (RAN).

2. The method according to claim 1, further comprising: 　　wherein the information related to the shutdown of the RAN is received in a first cell, 　　selecting a second cell in a case of receiving the information related to the shutdown of the RAN.

3. The method according to claim 2, further comprising: 　　receiving information related to resuming of the RAN, 　　selecting the first cell in a case of receiving the information related to resuming of the RAN.

4. A method of a communication apparatus comprising: 　　communicating with a User Equipment (UE); and 　　sending information related to a shutdown of a Radio Access Network (RAN).

5. A method of a communication apparatus comprising: 　　communicating with a User Equipment (UE); and 　　sending information related to resuming of a Radio Access Network (RAN).

6. A method of a communication apparatus comprising: 　　sending information related to a shutdown of a Radio Access Network (RAN); and 　　receiving a message related to a handover of a User Equipment (UE) in a case of sending the information.

7. A method of a communication apparatus comprising: 　　receiving information related to a shutdown of a Radio Access Network (RAN); and 　　sending a message related to a handover of a User Equipment (UE) in a case of receiving the information.

8. A method of a communication apparatus comprising: 　　communicating with another communication apparatus; and 　　performing a procedure related to a handover of a User Equipment (UE) in case of a shutdown of a Radio Access Network (RAN).

9. A User Equipment (UE) comprising: 　　means for communicating with a communication apparatus; and 　　means for receiving information related to a shutdown of a Radio Access Network (RAN).

10. The UE according to claim 9, further comprising: 　　wherein the information related to the shutdown of the RAN is received in a first cell, 　　means for selecting a second cell in a case of receiving the information related to the shutdown of the RAN.

11. The UE according to claim 10, further comprising: 　　receiving information related to resuming of the RAN, 　　selecting the first cell in a case of receiving the information related to resuming of the RAN.

12. A communication apparatus comprising: 　　means for communicating with a User Equipment (UE); and 　　means for sending information related to a shutdown of a Radio Access Network (RAN).

13. A communication apparatus comprising: 　　means for communicating with a User Equipment (UE); and 　　means for sending information related to resuming of a Radio Access Network (RAN).

14. A communication apparatus comprising: 　　means for sending information related to a shutdown of a Radio Access Network (RAN); and 　　means for receiving a message related to a handover of a User Equipment (UE) in a case of sending the information.

15. A communication apparatus comprising: 　　means for receiving information related to a shutdown of a Radio Access Network (RAN); and 　　means for sending a message related to a handover of a User Equipment (UE) in a case of receiving the information.

16. A communication apparatus comprising: 　　means for communicating with another communication apparatus; and 　　means for performing a procedure related to a handover of a User Equipment (UE) in case of a shutdown of a Radio Access Network (RAN).

Images