Method of user equipment, method of core network node, user equipment and core network node

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 architecture and mechanisms to support energy saving in the UE via Quality of Service (QoS) adjustments based on the reported UE battery status.

Description

METHOD OF USER EQUIPMENT, METHOD OF CORE NETWORK NODE, USER EQUIPMENT AND CORE NETWORK NODE

[0001] The present disclosure relates to a method of a user equipment, a method of a network node, a method of a core network node, a user equipment, a network node and a core network node.

[0002] Energy consumption is a significant source of operations costs for Mobile Network Operators (MNOs) and depending on the method of the energy generation that is generated and 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 [5] 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. SP-241915 [6] agreed at the 3GPP SAP#106 in December 2024 set the key priorities on UE and network energy efficiency work 3GPP Rel-20.

[0003] NPL 1: [1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". V18.0.0 (2024-03) NPL 2: [2] 3GPP TS 23.501: "System architecture for the 5G System (5GS)". V19.2.1 (2025-01) NPL 3: [3] 3GPP TS 23.502: "Procedures for the 5G System (5GS)". V19.2.0 (2024-12) NPL 4: [4] 3GPP TS 23.503: "Policy and charging control framework for the 5G System (5GS) Stage 2". V19.2.0 (2024-12) NPL 5: [5] SP-231192: https: / / www.3gpp.org / ftp / tsg_sa / TSG_SA / TSGs_101_Bangalore_2023-09 / Docs / SP-231192.zip NPL 6: [6] SP-241915: https: / / www.3gpp.org / ftp / tsg_sa / TSG_SA / TSGS_106_Madrid_2024-12 / Docs / SP-241915.zip

[0004] However, there is no technical solution in the current 3GPP standards for achieving the requirements set by SP-241915 [6].

[0005] For example, according to SP-241915 [6], there is a need to study potential framework for Supporting UE-based energy-saving with battery status reporting and QoS adjustments and there is no mechanism in the current 3GPP standards to achieve this need.

[0006] The disclosure has a method performed by a User Equipment (UE) comprising sending, to a core network node, a registration request message; and receiving, from the core network node, a registration accept message including first information about a battery threshold for a Quality of Service (QoS) adjustment for the UE.

[0007] The disclosure has a User Equipment (UE) comprising sending, to a core network node, a registration request message; and receiving, from the core network node, a registration accept message including first information about a battery threshold for a Quality of Service (QoS) adjustment for the UE.

[0008] The disclosure has a method performed by a core network node comprising receiving, from a User Equipment (UE), a registration request message; and sending, to the UE, a registration accept message including first information about a battery threshold for a Quality of Service (QoS) adjustment for the UE.

[0009] The disclosure has a core network node comprising receiving, from a User Equipment (UE), a registration request message; and sending, to the UE, a registration accept message including first information about a battery threshold for a Quality of Service (QoS) adjustment for the UE.

[0010] The disclosure has a method performed by a first core network node comprising receiving first information about a battery threshold for a Quality of Service (QoS) adjustment for a User Equipment (UE) receiving second information about the battery status of the UE; and determining, based on the first information and the second information, to request, to a second core network node, for updating the QoS adjustment for the UE.

[0011] The disclosure has a first core network node comprising receiving first information about a battery threshold for a Quality of Service (QoS) adjustment for a User Equipment (UE) receiving second information about the battery status of the UE; and determining, based on the first information and the second information, to request, to a second core network node, for updating the QoS adjustment for the UE.

[0012] 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 Third of the First Aspect.Fig. 4 is a signaling diagram of a Fourth example of the First Aspect.Fig. 5 is a signaling diagram of a First example of the Second Aspect.Fig. 6 is a signaling diagram of a Second example of the Second Aspect.Fig. 7 is a signaling diagram of a Third of the Second Aspect.Fig. 8 is a signaling diagram of a Fourth example of the Second Aspect.Fig. 9 is a diagram illustrating a system overview.Fig. 10 is a block diagram illustrating a UE.Fig. 11 is a block diagram illustrating an (R)AN node.Fig. 12 is a block diagram illustrating an AMF.Fig. 13 is a block diagram illustrating an SMF.Fig. 14 is a block diagram illustrating a UPF.Fig. 15 is a block diagram illustrating a PCF.Fig. 16 is a block diagram illustrating an NWDAF.Fig. 17 is a block diagram illustrating a UDM.Fig. 18 is a block diagram illustrating an AUSF.Fig. 19 is a block diagram illustrating an AAnF.Fig. 20 is a block diagram illustrating an NRF.Fig. 21 is a block diagram illustrating an NEF.Fig. 22 is a block diagram illustrating a UDR.Fig. 23 is a block diagram illustrating an OAM.Fig. 24 is a block diagram illustrating an AF.

[0013] <Abbreviations> 　　For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] 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 [1]. 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 AAnF　　AKMA Anchor Function ABBA　　Anti-Bidding down Between Architectures AF　　Application Function A-KID　　AKMA Key Identifier AKMA　　Authentication and Key Management for Applications 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 AP　　Authentication Proxy AR　　Augmented Reality ARFCN　　Absolute radio-frequency channel number AS　　Access Stratum ASN　　Abstract Syntax Notation A-TID　　AKMA Temporary UE Identifier 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 CDR　　Charging Data Record CHF　　Charging Function CN PDB　　Core Network Packet Delay Budget CP　　Control Plane CSG　　Closed Subscriber Group DAPS　　Dual Active Protocol Stacks DL　　Downlink DN　　Data Network DNAI　　DN Access Identifier DNN　　Data Network Name DRX　　Discontinuous Reception DSATSSS　　Dual Steer Access Traffic Steering, Switching, Splitting DSATSSS-LL　　Dual Steer Access Traffic Steering, Switching, Splitting- Low-Layer DSMA　　Dual Steer Multi Access DS-TT　　Device-side TSN translator ePDG　　evolved Packet Data Gateway EBI　　EPS Bearer Identity ECGI　　E-UTRAN Cell Global Identifier 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 KAF　　AKMA Application Key KAKMA　　AKMA Anchor Key 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 MR　　Mixed Reality 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 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 OAM　　Operations, Administration, and Maintenance 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　　Quality of Service RACS　　Radio Capabilities Signalling optimisation (R)AN　　(Radio) Access Network RAT　　Radio Access Technology RFID　　Radio Frequency Identification RG　　Residential Gateway RID　　Routing Indicator 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 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 VR　　Virtual Reality 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

[0014] <Definitions> 　　For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] 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 [1].

[0015] In addition, the following bullets explain the terms that the present document frequently uses: - URSP (UE Route Selection Policy) rule - The URSP rule is a UE policy information preconfigured in the UE for PDU Session Selection. The URSP rule can be characterized by a set of match criteria such as Data Network Name (DNN), application identifier, Fully Qualified Domain Name (FQDN), IP address / prefix, and Connection Capabilities component types of a Traffic Descriptor. The URSP rule may be provided to the UE by the PCF. - Route Selection Descriptor (RSD) - The RSD is a Route Selection Descriptor defined in the URSP rule. Once the UE finds a matching in the URSP rule, the RSD is referred to make associations with Network Slice, SSC mode and other session related characteristics.

[0016] <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. 　　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.

[0017] 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.

[0018] 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.

[0019] 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.

[0020] 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.

[0021] 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.

[0022] While the present disclosure has been particularly shown and described with reference to example embodiments and / or example aspects thereof, the present disclosure is not limited to these example embodiments and / or example 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 the claims. And each embodiment and / or aspect can be appropriately combined with other embodiments and / or aspects.

[0023] In addition, in this disclosure, the drawing(s) is associated with one or more embodiments, or one or more aspects.

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

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

[0026] A method of a communication apparatus according to example aspect of this disclosure includes sending information related to an energy saving service level.

[0027] A method of a communication apparatus according to example aspect of this disclosure includes receiving information related to an energy saving service level.

[0028] A method of a User Equipment (UE) according to example aspect of this disclosure includes sending information related to a capability for an energy saving service.

[0029] A method of a communication apparatus according to example aspect of this disclosure includes receiving information related to a capability for an energy saving service.

[0030] A method of a communication apparatus according to example aspect of this disclosure includes receiving information related to an energy saving service. The method includes sending a UE Route Selection Policy (URSP) rule including the information.

[0031] 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 an energy saving service level.

[0032] 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 an energy saving service level.

[0033] 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 send information related to a capability for an energy saving service.

[0034] 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 capability for an energy saving service.

[0035] 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 an energy saving service. The at least one hardware processor is configured to send a UE Route Selection Policy (URSP) rule including the information.

[0036] A method performed by a User Equipment (UE) according to example aspect of this disclosure includes sending, to a core network node, a registration request message. The method includes receiving, from the core network node, a registration accept message including first information about a battery threshold for a Quality of Service (QoS) adjustment for the UE.

[0037] A User Equipment (UE) according to example aspect of this disclosure includes means for sending, to a core network node, a registration request message. The UE includes means for receiving, from the core network node, a registration accept message including first information about a battery threshold for a Quality of Service (QoS) adjustment for the UE.

[0038] A User Equipment (UE) according to example aspect of this disclosure includes (or comprises) at least one memory configured to store instructions and at least one processor coupled to the at least one memory. The at least one processor execute the instructions to send, to a core network node, a registration request message. The at least one processor execute the instructions to receive, from the core network node, a registration accept message including first information about a battery threshold for a Quality of Service (QoS) adjustment for the UE.

[0039] A method performed by a core network node according to example aspect of this disclosure includes receiving, from a User Equipment (UE), a registration request message. The method includes sending, to the UE, a registration accept message including first information about a battery threshold for a Quality of Service (QoS) adjustment for the UE.

[0040] A core network node according to example aspect of this disclosure includes means for receiving, from a User Equipment (UE), a registration request message. The core network node includes means for sending, to the UE, a registration accept message including first information about a battery threshold for a Quality of Service (QoS) adjustment for the UE.

[0041] A core network node according to example aspect of this disclosure includes at least one memory configured to store instructions and at least one processor coupled to the at least one memory. The at least one processor execute the instructions to receive, from a User Equipment (UE), a registration request message. The at least one processor execute the instructions to send, to the UE, a registration accept message including first information about a battery threshold for a Quality of Service (QoS) adjustment for the UE.

[0042] A method performed by a first core network node according to example aspect of this disclosure includes receiving first information about a battery threshold for a Quality of Service (QoS) adjustment for a User Equipment (UE). The method includes receiving second information about the battery status of the UE. The method includes determining, based on the first information and the second information, to request, to a second core network node, for updating the QoS adjustment for the UE.

[0043] A first core network node according to example aspect of this disclosure includes means for receiving first information about a battery threshold for a Quality of Service (QoS) adjustment for a User Equipment (UE). The first core network node includes means for receiving second information about the battery status of the UE. The first core network node includes means for determining, based on the first information and the second information, to request, to a second core network node, for updating the QoS adjustment for the UE.

[0044] A first core network node according to example aspect of this disclosure includes at least one memory configured to store instructions and at least one processor coupled to the at least one memory. The at least one processor execute the instructions to receive first information about a battery threshold for a Quality of Service (QoS) adjustment for a User Equipment (UE). The at least one processor execute the instructions to receive second information about the battery status of the UE. The at least one processor execute the instructions to determine, based on the first information and the second information, to request, to a second core network node, for updating the QoS adjustment for the UE.

[0045] A method performed by a User Equipment (UE) according to example aspect of this disclosure includes sending, to a core network node, a registration request message including information indicating that the UE supports an energy credit policy control. The method includes receiving, from the core network node, a registration accept message including a first information indicating that the amount of energy or the remaining energy being available for the UE and a second information for determining that the UE is in a Low energy state.

[0046] A User Equipment (UE) according to example aspect of this disclosure includes means for sending, to a core network node, a registration request message including information indicating that the UE supports an energy credit policy control. The UE includes means for receiving, from the core network node, a registration accept message including a first information indicating that the amount of energy or the remaining energy being available for the UE and a second information for determining that the UE is in a Low energy state.

[0047] A User Equipment (UE) according to example aspect of this disclosure includes (or comprises) at least one memory configured to store instructions and at least one processor coupled to the at least one memory. The at least one processor execute the instructions to send, to a core network node, a registration request message including information indicating that the UE supports an energy credit policy control. The at least one processor execute the instructions to receive, from the core network node, a registration accept message including a first information indicating that the amount of energy or the remaining energy being available for the UE and a second information for determining that the UE is in a Low energy state.

[0048] A method performed by a core network node according to example aspect of this disclosure includes receiving, from a User Equipment (UE), a registration request message including information indicating that the UE supports an energy credit policy control. The method includes sending, to the UE, a registration accept message including a first information indicating that the amount of energy or the remaining energy being available for the UE and a second information for determining that the UE is in a Low energy state.

[0049] A core network node according to example aspect of this disclosure includes means for receiving, from a User Equipment (UE), a registration request message including information indicating that the UE supports an energy credit policy control. The core network node includes means for sending, to the UE, a registration accept message including a first information indicating that the amount of energy or the remaining energy being available for the UE and a second information for determining that the UE is in a Low energy state.

[0050] A core network node according to example aspect of this disclosure includes (or comprises) at least one memory configured to store instructions and at least one processor coupled to the at least one memory. The at least one processor execute the instructions to receive, from a User Equipment (UE), a registration request message including information indicating that the UE supports an energy credit policy control. The at least one processor execute the instructions to send, to the UE, a registration accept message including a first information indicating that the amount of energy or the remaining energy being available for the UE and a second information for determining that the UE is in a Low energy state.

[0051] A method performed by a User Equipment (UE) according to example aspect of this disclosure includes receiving, from a first core network node, first information indicating a behavior of the UE when the energy state of the UE is Low. the method includes sending, to the first core network node, second information indicating that the energy efficiency preference of the at least one service for the UE.

[0052] A User Equipment (UE) according to example aspect of this disclosure includes means for receiving, from a first core network node, first information indicating a behavior of the UE when the energy state of the UE is Low. The UE includes means for sending, to the first core network node, second information indicating that the energy efficiency preference of the at least one service for the UE.

[0053] A User Equipment (UE) according to example aspect of this disclosure includes (or comprises) at least one memory configured to store instructions and at least one processor coupled to the at least one memory. The at least one processor execute the instructions to receive, from a first core network node, first information indicating a behavior of the UE when the energy state of the UE is Low. The at least one processor execute the instructions to send, to the first core network node, second information indicating that the energy efficiency preference of the at least one service for the UE.

[0054] A method performed by a first core network node according to example aspect of this disclosure includes receiving, from a second core network node, first information indicating that an energy state of a User Equipment (UE) is Low. The method includes sending, to a third core network node, second information indicating a behavior of the UE when the energy state of the UE is Low.

[0055] A first core network node according to example aspect of this disclosure includes means for receiving, from a second core network node, information indicating that an energy state of a User Equipment (UE) is Low. The first core network node includes means for sending, to a third core network node, information indicating that the energy state of the UE energy is Low.

[0056] A first core network node according to example aspect of this disclosure includes (or comprises) at least one memory configured to store instructions and at least one processor coupled to the at least one memory. The at least one processor execute the instructions to receive, from a second core network node, information indicating that an energy state of a User Equipment (UE) is Low. The at least one processor execute the instructions to send, to a third core network node, information indicating that the energy state of the UE energy is Low.

[0057] A method performed by a User Equipment (UE) according to example aspect of this disclosure includes receiving, from a core network node, information for network slice selection in a case where an energy credit for first Single - Network Slice Selection Assistance Information (S-NSSAI) is Low. The method includes selecting second S-NSSAI based on the information.

[0058] A User Equipment (UE) according to example aspect of this disclosure includes means for receiving, from a core network node, information for network slice selection in a case where an energy credit for first Single - Network Slice Selection Assistance Information (S-NSSAI) is Low. The UE includes means for selecting second S-NSSAI based on the information.

[0059] A User Equipment (UE) according to example aspect of this disclosure includes (or comprises) at least one memory configured to store instructions and at least one processor coupled to the at least one memory. The at least one processor execute the instructions to receive, from a core network node, information for network slice selection in a case where an energy credit for first Single - Network Slice Selection Assistance Information (S-NSSAI) is Low. The at least one processor execute the instructions to select second S-NSSAI based on the information.

[0060] A method performed by a core network node according to example aspect of this disclosure includes means for replacing first information about first Single - Network Slice Selection Assistance Information (S-NSSAI) to second information about second S-NSSAI, in a case where an energy credit for the first S-NSSAI is Low. The first S-NSSAI and the second S-NSSAI is available for the UE. The method includes means for sending, to a second core network node, third information for network slice selection.

[0061] A core network node according to example aspect of this disclosure includes means for replacing first information about first Single - Network Slice Selection Assistance Information (S-NSSAI) to second information about second S-NSSAI, in a case where an energy credit for the first S-NSSAI is Low, wherein the first S-NSSAI and the second S-NSSAI is available for the UE. The core network includes means for sending, to a second core network node, third information for network slice selection.

[0062] A core network node according to example aspect of this disclosure includes (or comprises) at least one memory configured to store instructions and at least one processor coupled to the at least one memory. The at least one processor execute the instructions to replace first information about first Single - Network Slice Selection Assistance Information (S-NSSAI) to second information about second S-NSSAI, in a case where an energy credit for the first S-NSSAI is Low, wherein the first S-NSSAI and the second S-NSSAI is available for the UE. The at least one processor execute the instructions to send, to a second core network node, third information for network slice selection.

[0063] A method performed by a User Equipment (UE) according to example aspect of this disclosure includes receiving, from a first core network node, first information about first Single - Network Slice Selection Assistance Information (S-NSSAI) and second information about an energy credit for the first S-NSSAI. The method includes performing Protocol Data Unit (PDU) session establishment procedure related to second S-NSSAI, in a case where the second information indicates that an energy credit for the first S-NSSAI is Low.

[0064] A User Equipment (UE) according to example aspect of this disclosure includes means for receiving, from a first core network node, first information about first Single - Network Slice Selection Assistance Information (S-NSSAI) and second information about an energy credit for the first S-NSSAI. The UE includes means for performing Protocol Data Unit (PDU) session establishment procedure related to second S-NSSAI, in a case where the second information indicates that an energy credit for the first S-NSSAI is Low.

[0065] A User Equipment (UE) according to example aspect of this disclosure includes (or comprises) at least one memory configured to store instructions and at least one processor coupled to the at least one memory. The at least one processor execute the instructions to receive, from a first core network node, first information about first Single - Network Slice Selection Assistance Information (S-NSSAI) and second information about an energy credit for the first S-NSSAI. The at least one processor execute the instructions to perform Protocol Data Unit (PDU) session establishment procedure related to second S-NSSAI, in a case where the second information indicates that an energy credit for the first S-NSSAI is Low.

[0066] A method performed by a core network node according to example aspect of this disclosure includes sending, to a User Equipment (UE), first information about first Single - Network Slice Selection Assistance Information (S-NSSAI) and second information about an energy credit for the first S-NSSAI. The methos includes performing Protocol Data Unit (PDU) session establishment procedure related to second S-NSSAI, in a case where the second information indicates that an energy credit for the first S-NSSAI is Low.

[0067] A core network node according to example aspect of this disclosure includes means for sending, to a User Equipment (UE), first information about first Single - Network Slice Selection Assistance Information (S-NSSAI) and second information about an energy credit for the first S-NSSAI. The core network includes means for performing Protocol Data Unit (PDU) session establishment procedure related to second S-NSSAI, in a case where the second information indicates that an energy credit for the first S-NSSAI is Low.

[0068] A core network node according to example aspect of this disclosure includes (or comprises) at least one memory configured to store instructions and at least one processor coupled to the at least one memory. The at least one processor execute the instructions to send, to a User Equipment (UE), first information about first Single - Network Slice Selection Assistance Information (S-NSSAI) and second information about an energy credit for the first S-NSSAI. The at least one processor execute the instructions to perform Protocol Data Unit (PDU) session establishment procedure related to second S-NSSAI, in a case where the second information indicates that an energy credit for the first S-NSSAI is Low.

[0069] <<First Aspect>> 　　The First Aspect includes an architecture and a mechanism for QoS adjustment based on UE battery status during PDU Session establishment procedure.

[0070] <First Example of the First Aspect> 　　The First Example of the First Aspect in Fig. 1 includes a mechanism for UE indication of battery report capability during the Registration procedure. At UE registration, the UE 3 indicates its capability for battery status reporting in the Registration Request message. For example, the UE 3 may send the Registration Request message including a first indication indicating a capability for battery status (or indicating a UE battery reporting capability) and a second indication indicating a UE battery status.

[0071] If the UE 3 indicated capability for battery status reporting and the UE subscription allows for QoS adjustment or any other communications service adjustment based on the reported UE battery status, the network may inform the UE 3 about when (for example in terms of UE battery level reaching or crossing a threshold level) the network would trigger QoS adjustment or any other communications service adjustment for the services provided to UE 3, e.g. when the reported UE battery drops below a QoS adjustment battery threshold.

[0072] The detailed process of the Second example of the First Aspect is described below with reference to Fig. 1.

[0073] Step 1. The UE 3 may hold (or store) a subscription within the UE 3 subscription information in the UDM 75 for QoS adjustment or any other communications service adjustment based on the UE 3 battery status. The UDM 75 may also hold or store a QoS adjustment battery threshold parameter (or value). The QoS adjustment battery threshold parameter may be used as a trigger for QoS adjustment when the reported UE battery status, e.g. battery charge level represented in percentage of the whole battery capacity, is equal or drops below the QoS adjustment threshold parameter, if any.

[0074] Step 2. The UE 3 initiates a UE registration procedure. First, the UE 3 creates the RRC connection with the RAN 5 by sending RRC Connection Setup Request message or RRC Setup Request or a message for establishing the RRC connection to the RAN 5. The RRC Connection Setup Request message or the RRC Setup Request or the message for establishing the RRC connection may include at least one of the following parameters (hereafter, the word parameter may be noted as information or indication or value, instead of parameter.): - UE battery reporting capability - this is the UE battery reporting capability parameter or any other notation for a parameter which indicates the UE capability for reporting its battery status or battery charge level to the network. The UE 3 includes the UE battery reporting capability parameter in the RRC Connection Setup Request message or in the RRC Setup Request message or in a message for establishing of a RRC connection from the UE 3 to the RAN 5 when the UE 3 has a capability for monitoring and for reporting the UE battery status, e.g. UE remaining battery level in percentage or in any other numeration or expression. For example, the UE may send, to the RAN 5, a RRC message (for example, the RRC Connection Setup Request message or in the RRC Setup Request message or in a message for establishing of a RRC connection) including information about capability for reporting the battery status or the battery charge level of the UE 3. - UE battery status - this is the UE battery status parameter or any other notation for a parameter with the purpose to indicate the UE remaining battery level or charge, in percentage of the full battery capacity or in any other quantitative expression. - In addition, the UE battery status may include a battery feeding status. The battery feeding status (or the battery charging status) may indicate a feeding (charging) status of battery to the UE 3. For example, the UE 3 may send, to the RAN 5, a RRC message (for example, the RRC Connection Setup Request message or in the RRC Setup Request message or in a message for establishing of a RRC connection) including information about the battery status of the UE 3. The battery feeding status may have at least the following information. --- No battery feeding - No battery feeding (charging). --- Being charged - the UE 3 is being charged from other battery source. For example, AC power, solar power, mobile battery charger. 　　The UE battery status may also contain information as: --- Age of UE battery - the age of the UE battery may be represented by the number of the UE battery charging cycles undergone by that UE battery. --- Last usage of the UE battery - may be represented in actual date of last usage of the UE battery or in actual time span since the last use of the UE battery.

[0075] Step 3. If the UE 3 indicated capability for UE battery reporting to the RAN 5, the RAN 5 may use this information in order to select an AMF which also supports or is compatible with the UE battery reporting capability feature. For example, if the RAN 5 received the information about capability for reporting the battery status or the battery charge level of the UE 3, the RAN 5 may select an AMF which supports or is compatible with the UE battery reporting capability feature. The RAN 5 confirms the RRC connection establishment by returning to the UE 3 the RRC Connection Setup message or RRC Setup message or a message for establishing the RRC connection from the RAN 5 to the UE 3. If the RAN 5 receives the UE battery status from the UE 3, the RAN 5 maintains (or stores) the received UE battery status in the RAN 5.

[0076] Step 4. The RRC connection establishment is completed by sending from the UE 3 to RAN 5 the RRC Connection Setup Complete message or RRC Setup Complete message or a message for establishing the RRC connection from the UE 3 to the RAN 5. This message carries the Registration Request message from the UE 3 to the AMF 70. The UE 3 includes the UE battery reporting capability parameter or / and UE battery status in both messages, e.g. in the RRC Connection Setup Complete message to the RAN 5 or RRC Setup Complete message or a message for establishing the RRC connection from the UE 3 to the RAN 5 and in the Registration Request message to the AMF 70.

[0077] For example, the RRC Connection Setup Complete message or RRC Setup Complete message or a message for establishing the RRC connection from the UE 3 to the RAN 5 may include the UE battery reporting capability parameter and the UE battery status parameter.

[0078] For example, the Registration Request message or any other NAS message from the UE 3 to the AMF 70 may include the UE battery reporting capability parameter and the UE battery status parameter.

[0079] For example, the UE 3 may send, to the AMF 70, the Registration Request message including at least one of the information about capability for reporting the battery status or for reporting the battery charge level of the UE 3 or the information about the battery status of the UE 3.

[0080] For example, the UE 3 may send the registration request message including information about capability for reporting a battery status or for reporting a battery charge level of the UE.

[0081] For example, the UE 3 may send the registration request message including information about a battery status of the UE.

[0082] Step 5. If the UE battery reporting capability parameter was included in the RRC connection request message or RRC Connection Setup Complete message from the UE 3, the RAN 5 may make use of the UE battery reporting capability parameter for the AMF selection i.e. the RAN 5 selects an AMF node e.g. AMF 70 which supports the UE battery reporting capability feature.

[0083] For example, if the RAN 5 may receive the information about capability for reporting the battery status or the battery charge level of the UE 3, the RAN 5 may determine and select the AMF 70.

[0084] Step 6. After AMF selection (e.g., after selection of the AMF 70), the RAN 5 may forward the Registration Request message from UE 3 to the AMF 70 within the UE Initial message. The Registration Request message may contain the UE battery reporting capability parameter and / or the UE battery status parameter. The RAN 5 may also pass the UE battery reporting capability parameter and / or the UE batter status parameter in an NGAP Message e.g. Initial UE message to the AMF 70. For example, the Registration Request message may include the information about capability for reporting the battery status or the battery charge level of the UE 3. For example, the Registration Request message may include the information about the battery status of the UE 3.

[0085] Step 7. If the UE 3 indicated UE battery reporting capability or / and UE battery status in the Registration Request message, the AMF 70 stores the UE battery reporting capability indication or / and UE battery status in the UE context within the AMF 70. For example, if the AMF 70 may receive the Registration Request message, the AMF 70 may store the information about capability for reporting the battery status or the battery charge level of the UE 3. For example, if the AMF 70 may receive the Registration Request message, the AMF 70 may store the information about the battery status of the UE 3. Then, at location mobility when the UE 3 moves to a new AMF, the AMF 70 provides the UE battery reporting capability or / and UE battery status together with the UE context to the target AMF.

[0086] Step 8. The AMF 70 continues the UE registration procedure by sending a Nudm_UECM_Registration Request message to the UDM 75. The AMF 70 may include in the message to the UDM 75 the UE battery reporting capability parameter or / and UE battery status if received from the UE 3 within the Registration Request message. For example, the AMF 70 may send, to the UDM 75, the received information about capability for reporting the battery status or the battery charge level of the UE 3. For example, the AMF 70 may send, to the UDM 75, the received information about the battery status of the UE 3.

[0087] Step 9. If the UE indicated UE battery reporting capability and the UE battery reporting capability was passed to the UDM 75 by the AMF 70, the UDM 75 checks if the UE 3 has a subscription for QoS adjustment or any other communications service adjustment based on the reported UE battery status. For example, if the UDM 75 received the information about capability for reporting the battery status or the battery charge level of the UE 3, the UDM 75 may check if the UE 3 has a subscription for QoS adjustment or any other communications service adjustment based on the received information about the battery status of the UE 3.

[0088] Step 10. If the UE 3 indicated UE battery reporting capability and the UDM 75 determines that the UE 3 holds a subscription for QoS adjustment or any other communications service adjustment based on the UE battery status, the UDM 75 returns Nudm_UECM_Registration Response message in which the UDM 75 includes at least one of the following parameters: - QoS adjustment active - or any other notation for a parameter with meaning that the network may trigger QoS adjustment or any other communications service adjustment for UE 3 services when the UE battery level drops below certain threshold. This threshold, for example called QoS adjustment battery threshold, may be a defined parameter in the UE subscription information per UE granularity or per all UEs granularity or operator configured parameter. For example, this information may indicate that the QoS adjustment or any other communications service adjustment for UE 3 services is active for the UE 3 and is to be triggered (or performed) on a certain condition. - QoS adjustment battery threshold - or any other notation for a UE battery level threshold which is used to decide or determine whether to trigger QoS adjustment or any other communications service adjustment for the services by the UE(s) when the UE 3 reported battery status drops to or below the QoS adjustment battery threshold. The QoS adjustment battery threshold may represent remaining UE battery level or UE battery charge in percentage of the full UE battery capacity or in any other quantitative expression comparable with the UE battery status expression reported by the UE 3. In one example the QoS adjustment battery threshold may represent the UE battery charge level represented in percentage of the UE full charge battery capacity. In another example the QoS adjustment battery threshold may represent the age of the UE battery e.g. the number of the UE battery charging cycles. In yet another example the QoS adjustment battery threshold may represent the time of the last UE battery use. For example, the UE 3 may determine whether to perform QoS adjustment or any other communications service adjustment for the services, based on the information about the QoS adjustment battery threshold.

[0089] Step 11. The AMF 70 stores the QoS adjustment active and the QoS adjustment battery threshold parameters in the UE context within the AMF 70. Then, at location mobility, when the UE 3 moves to a new AMF, the AMF 70 provides the QoS adjustment active and the QoS adjustment battery threshold parameters together with the UE context to the target AMF. For example, the AMF 70 may receive and store the information indicating that QoS adjustment is active for the UE 3. For example, the AMF 70 may receive and store the information about the QoS adjustment battery threshold.

[0090] Step 12. The AMF 70 confirms the UE registration procedure by sending the Registration Accept message in which the AMF 70 includes the QoS adjustment active parameter and the QoS adjustment battery threshold parameter. The UE 3 may store the QoS adjustment active and the QoS adjustment battery threshold parameters in a non-volatile memory within UE 3. Then, the UE 3 may indicate to the user information that the services by this user may be with degraded quality (e.g. QoS degraded or any other communications service adjustment) when the UE 3 battery level drops below the QoS adjustment battery threshold.

[0091] For example, the AMF 70 may send, to the UE 3, the Registration Accept message including the information indicating that QoS adjustment is active for the UE 3. For example, the AMF 70 may send, to the UE 3, the Registration Accept message including the information about the QoS adjustment battery threshold.

[0092] For example, the UE 3 may receive, from the core network node, the registration accept message including information about battery threshold for the QoS adjustment.

[0093] For example, the UE 3 may receive, from the core network node, the registration accept message including information about battery threshold for the QoS adjustment, in a case where the QoS adjustment is active for the UE.

[0094] For example, the UE 3 may receive, from the core network node, the registration accept message including information indicating that the QoS adjustment is active for the UE.

[0095] In the First Example of the First Aspect, for example, the UE 3 may send, to a core network node, a registration request message and may receive, from the core network node, a registration accept message including first information about a battery threshold for a Quality of Service (QoS) adjustment for the UE. For example, the UE 3 may receive registration accept message including first information, in a case where the QoS adjustment is active for the UE. For example, the registration accept message may include second information indicating that the QoS adjustment is active for the UE 3. For example, the registration request message may include third information about capability for reporting a battery status or for reporting a battery charge level of the UE 3. For example, the registration request message may include fourth information about a battery status of the UE. For example,

[0096] <Variant 1 of the First Example of the First Aspect> 　　In one example, UE 3 may hold the subscription information for QoS adjustment or any other communications service adjustment based on the UE battery status within the UE 3 subscription information in the UDR 80 instead of UDM 75. The UDR 80 may also hold the QoS adjustment battery threshold parameter. In this case, at Step 8 in Fig. 1, the AMF 70 may retrieve the information indicating that the QoS adjustment is active and the information about the QoS adjustment battery threshold parameter(s) from the UDR 80.

[0097] <Variant 2 of the First Example of the First Aspect> 　　When the AMF 70 sends the Registration Accept message to the UE 3 in Step 12, the Initial Context Setup Request message to the RAN 5, where the Registration Accept message is embedded, may include the information about the UE battery status, information indicating that the QoS adjustment is active for the UE3 (also denoted as information about the QoS adjustment active) and the information about the QoS adjustment battery threshold.

[0098] The information about the UE battery status may be received from the UE 3 at Step 6 in Fig. 1.

[0099] The information about the QoS adjustment active and the information about the QoS adjustment battery threshold are ones received from the UDM 75 at Step 10 in Fig. 1.

[0100] <Variant 3 of the First Example of the First Aspect> 　　In one example, Registration Request message at Steps 4 and 5 in Fig. 1 may be replaced with UL NAS transport message, new NAS message or existing NAS message.

[0101] Similarly, Registration Accept message at Step 12 in Fig. 1 may be replaced with DL NAS transport message, new NAS message or existing NAS message.

[0102] With this example, the UE 3 may send the UL NAS transport message, new NAS message or existing NAS message to the AMF 70 in case the UE battery status is changed in the UE 3 based on a pre-configured UE battery status reporting criteria. The pre-configured UE battery status reporting criteria may be stored in the USIM or non-volatile memory in the UE 3 via O&M or based on URSP rule or obtained from the AMF 70 over any NAS message.

[0103] <Variant 4 of the First Example of the First Aspect> 　　In one example, the UDR 80 or the UDM75 may store a UE battery reporting criteria, i.e. a criteria defining when the UE 3 to report the UE battery status expressed as an event or condition, and the UDM 75 may send the UE battery reporting criteria at step 10 in Fig. 1 for the user, e.g. UE 3to the AMF 75 in an existing message between the AMF 70 and the UDM 75. The AMF 70 may include the UE reporting criteria for the UE 3 during the registration procedure in the Registration Accept message. The UE 3 may store the UE battery reporting criteria. When the UE battery reporting criteria is fulfilled, the UE 3 may report the current UE battery status to the RAN 5 in an existing RRC message when the UE 3 transits to the RRC connected state. The RAN 5 then may send it to the AMF 70 in an existing NGAP message, The UE 3 may send the UE battery status in an existing NAS message or in a new NAS message. The UE battery reporting criteria may be one of the following event or conditions: - whenever UE transit from RRC IDLE mode to RRC Connected mode, or 5GMM IDLE mode 5GMM connected mode. - when the UE battery status is below some threshold. - periodically report UE battery status. For an example, the UE 3 is configured to report UE battery status every hour. In this case the UE 3 may report the UE battery status every hour if the UE 3 is in connected state or if the idle state then the UE 3 moves to the connected state and report the UE battery status in an existing RRC message or a NAS message.

[0104] <Variant 5 of the First Example of the First Aspect> 　　In one example, RAN 5 or the AMF 70 or an existing network function may fetch the UE battery status from the UE 3 using an existing RRC message or a NAS message. For example, when the UE 3 moves to RRC connected state the NG RAN fetches the UE battery status by sending an existing RRC message or a new RRC message requesting the UE 3 to send the UE battery status. The UE 3 on receiving the RRC message sends the current UE battery status to the NG-RAN in an existing RRC message or in a new RRC message. The UE 3 also reports the current UE battery status to the AMF 70 in an existing NAS message or in a new NAS message. The NAS message can be an 5GMM NAS message or 5GMM SM message.

[0105] <Second Example of the First Aspect> 　　The Second Example of the First Aspect in Fig. 2 includes a mechanism for UE battery status provision by the UE 3 to the PCF 73 or to the UDM 75 / UDR 80 within the PDU Session Establishment procedure. The UE battery status expressed in percentage e.g. battery charge level represented in percentage of the whole battery capacity or in any other quantitative expression, is used by the PCF 73 or by the UDM 75 / UDR 80 for decision making on whether to adjust the QoS for the PDU Session if the UE Battery level drops to or goes below a QoS adjustment battery threshold which is a parameter in the UE subscription or is configured by the network operator.

[0106] The detailed process of the Second Example of the First Aspect is described below with reference to Fig. 2.

[0107] Step 1. The UE 3 triggers the Registration procedure. The UE 3 may send battery reporting capability in the UE MM capability or as a separate parameter in the Registration Request message as described in Fig. 1. If the UE 3 subscription allows for QoS adjustment or any other communications service adjustment based on the reported UE battery status, the AMF 75 may send the QoS adjustment active parameter and the QoS adjustment battery threshold parameter to the UE 3 in the Registration Accept message.

[0108] For example, the UE 3 may send the registration request message including information about capability for reporting a battery status or for reporting a battery charge level of the UE as described in Fig. 1.

[0109] For example, the AMF 70 may send, to the UE 3, the Registration Accept message including the information indicating that QoS adjustment is active for the UE 3. For example, the AMF 70 may send, to the UE 3, the Registration Accept message including the information about the QoS adjustment battery threshold as described in Fig. 1.

[0110] For example, the UE 3 may receive, from the core network node, the registration accept message including information about battery threshold for the QoS adjustment as described in Fig. 1.

[0111] For example, the UE 3 may receive, from the core network node, the registration accept message including information about battery threshold for the QoS adjustment, in a case where the QoS adjustment is active for the UE as described in Fig. 1.

[0112] For example, the UE 3 may receive, from the core network node, the registration accept message including information indicating that the QoS adjustment is active for the UE as described in Fig. 1.

[0113] Step 2. At some stage the UE 3 triggers PDU Session Establishment procedure with the PDU Session Establishment Request message. If the UE 3 supports the UE battery reporting capability, the UE 3 may include in the PDU Session Establishment Request message a parameter called for example UE battery status parameter: - UE battery status - Refer to Step 2 in Fig. 1.

[0114] The PDU Session Establishment Request message from the UE 3 is carried to the AMF 70 via the UL NAS Transport message.

[0115] For example, If the UE 3 supports the UE battery reporting capability, the UE 3 may send the PDU Session Establishment Request message including information about the battery status of the UE 3.

[0116] Step 3. The AMF 70 forwards the PDU Session Establishment Request message along with the UE battery status (or the information about the battery status of the UE 3) to the SMF 71 within the Nsmf PDU Session CreateSMContext Request message.

[0117] Step 4. At SM Policy Association Establishment with the PCF 73, the SMF 71 may interact with the PCF 73 and provide the UE ID and the UE battery status parameter (or information about the battery status of the UE 3) received in PDU Session Establishment Request message to the PCF 73. The SMF 71 may make use of the Npcf_SMPolicyControl_Create request service operation or any other existing or a new PCF service operation to provide the UE ID and the UE battery status (or information about the battery status of the UE 3) to the PCF 73. The PCF 73 may store the UE ID and the UE battery status parameter (or information about the battery status of the UE 3).

[0118] Step 5. The PCF 73 triggers subscription information retrieval for UE 3 from the UDM 75 or from the UDR 80 related to UDM 75 and sends Nudr_DM_Query message to the UDM 75 or to the UDR 80 related to UDM 75. In the Nudr_DM_Query message the PCF 73 includes the UE ID and the UE battery status parameter (or information about the battery status of the UE 3).

[0119] Step 6. The UDM 75 or the UDR 80 related to UDM 75 checks if the UE 3 subscription allows for QoS adjustment or any other communications service adjustment based on the UE battery status provided by UE 3. The UDR 80 or the UDM 75 may have a designated subscription indication for UE 3 which indicates whether it is allowed to adjust the QoS for that UE 3 based on the reported UE battery status from UE 3. If the UE 3 subscription in the UDM 75 or in the UDR 80 related to UDM 75 allows for QoS adjustment, the UDM 75 or the UDR 80 related to UDM 75 provides the QoS adjustment battery threshold parameter to the PCF 73. For QoS adjustment battery threshold parameter description, see Step 10 in Fig. 1.

[0120] Step 7. The UDM 75 or the UDR 80 related to UDM 75 sends the Nudr_DM_Query response message to the PCF 73 in which message the UDM 75 or the UDR 80 related to UDM 75 includes the QoS adjustment battery threshold parameter for UE 3 (or information about the battery status of the UE 3), if available in the UE 3 subscription information within the UDM 75 or in the UDR 80 related to UDM 75.

[0121] Step 8. If the PCF 73 receives a QoS adjustment battery threshold parameter for UE 3 (or information about the battery status of the UE 3) within the Nudr_DM_Query response message, the PCF 73 checks whether the UE battery status level provided by the UE 3 and stored in the PCF 73 is equal or less than the QoS adjustment battery threshold. If the UE battery status (e.g. UE 3 battery level expressed in percentage or any other quantitative expression) is equal or lower than the QoS adjustment battery threshold retrieved from the UDM 75 or from the UDR 80 related to the UDM 75, the PCF 73 requests SMF 73 for QoS adjustment. (e.g. QoS downgrade or any other communications service adjustment).

[0122] For example, if the UE battery status reported by the UE 3 and the QoS adjustment battery threshold provided by the UDR 80 or UDM 75 are expressed in percentage of the full UE battery charge, the PCF 73 applies the QoS adjustment or any other communications service adjustment for the UE 3 if the UE battery status drops to or below the QoS adjustment battery threshold.

[0123] For example, if the UE battery status reported by the UE 3 and the QoS adjustment battery threshold provided by the UDR 80 or UDM 75 are expressed in number of battery charging cycles undergone by the UE 3, the PCF 73 applies the QoS adjustment or any other communications service adjustment for the UE 3 if the battery charging cycles in the UE battery status are equal or higher that the battery charging cycles in the QoS adjustment battery threshold.

[0124] For example, if the UE battery status reported by the UE 3 and the QoS adjustment battery threshold provided by the UDR 80 or UDM 75 are expressed with the date of the last battery use by the UE 3, the PCF 73 applies the QoS adjustment or any other communications service adjustment for the UE 3 if the date of the last battery use in the reported UE battery status is older than the date in the QoS adjustment battery threshold. If the last UE battery use is expressed with time interval rather than an actual date, then the PCF applies the QoS adjustment or any other communications service adjustment for the UE 3 when the time interval in the reported UE battery status is longer than the time interval in the QoS adjustment battery threshold.

[0125] For example, the PCF 73 may determine to send a request for QoS adjustment to the SMF 73, based on the retrieved QoS adjustment battery threshold parameter for UE 3 (or information about a battery status of the UE 3) and the UE battery status (or information about the battery status of the UE 3).

[0126] Step 9. The PCF 73 triggers QoS adjustment for the requested PDU Session or for the ongoing PDU Session by UE 3. The PCF 73 sends to SMF 71 instruction for QoS adjustment or any other communications service adjustment via a new message on the PCF / SMF interface or via one of the existing messages on the PCF / SMF interface in which message the PCF 73 includes the new QoS.

[0127] For example, the PCF 73 may send a request for updating (changing) the QoS adjustment to the SMF 73, based on the retrieved QoS adjustment battery threshold parameter for UE 3 (or information about the battery status of the UE 3) and the UE battery status.

[0128] Step 10. The SMF 71 continues with the PDU Session establishment (as per 3GPP TS 23.502 [3], section.4.3.2.2) with the updated new QoS (i.e. QoS downgrade or any other communications service adjustment for UE battery save). If the SMF 73 receives instructions for QoS adjustment during and ongoing PDU Session, the SMF 73 triggers the PDU Sessin Modification procedure in order to adjust the current QoS for the ongoing PDU Session. The SMF 71 also provides the new QoS to the RAN 5.

[0129] In the Second Example of the First Aspect, for example, a first core network node may receive first information about a battery threshold for a Quality of Service (QoS) adjustment for a User Equipment (UE) and receive second information about the battery status of the UE. For example, a first core network node may determine, based on the first information and the second information, to request, to a second core network node, for updating the QoS adjustment for the UE.

[0130] <Variant 1 of the Second Example of the First Aspect> 　　In one example, if the UDM 75 or the UDR 80 related to UDM 75 receives the UE battery status from the PCF 73 at step 5 in Fig. 2, the UDM 75 or the UDR 80 related to UDM 75 may compare the UE battery status of the UE 3 with the QoS adjustment battery threshold for UE 3 instead of tasking this job to the PCF 73. In this case the UDM 75 or the UDR 80 related to the UDM 75 may check at Step 6 in Fig. 2 whether the UE battery status provided by the UE 3 via the PCF 73 is equal or less than the QoS adjustment battery threshold for UE 3. If the UE battery status (e.g. UE 3 battery level expressed in percentage expression or in any other quantitative expression) is equal or lower than the QoS adjustment battery threshold, the UDM 75 or the UDR 80 related to UDM 75 instructs the PCF 73 for QoS adjustment. (e.g. QoS downgrade or any other communications service adjustment).

[0131] For example, if the UE battery status reported by the UE 3 and the QoS adjustment battery threshold in the UDR 80 or UDM 75 are expressed in percentage of the full UE battery charge, the UDR 80 or the UDM 75 request the PCF 73 to apply the QoS adjustment or any other communications service adjustment for the UE 3 if the UE battery status drops to or below the QoS adjustment battery threshold.

[0132] For example, if the UE battery status reported by the UE 3 and the QoS adjustment battery threshold in the UDR 80 or UDM 75 are expressed in number of battery charging cycles undergone by the UE 3, the UDR 80 or the UDM 75 request PCF 73 to apply the QoS adjustment or any other communications service adjustment for the UE 3 if the battery charging cycles in the reported UE battery status are equal or higher that the battery charging cycles in the QoS adjustment battery threshold.

[0133] For example, if the UE battery status reported by the UE 3 and the QoS adjustment battery threshold in the UDR 80 or UDM 75 are expressed with the date of the last battery use by the UE 3, the UDR 80 or the UDM 75 request the PCF 73 to apply the QoS adjustment or any other communications service adjustment for the UE 3 if the date of the last battery use in the reported UE battery status is older than the date of the last battery use in the QoS adjustment battery threshold. If the last UE battery use is expressed with time interval rather than an actual date, then the PCF applies the QoS adjustment for the UE 3 when the time interval in the reported UE battery status is longer than the time interval in the QoS adjustment battery threshold.

[0134] <Variant 2 of the Second Example of the First Aspect> 　　One example, PDU Session Establishment Request message in Steps 2 and 3 in Fig. 2 may be replaced with PDU Session Modification Request message, new NAS message defined in the future (e.g. defined in 6G or 7G etc.) or existing NAS message.

[0135] Similarly, PDU Session Establishment message in Step 10 in Fig. 2 may be replaced with PDU Session Modification Command message, new NAS message or existing NAS message.

[0136] <Variant 3 of the Second Example of the First Aspect> 　　In one example, during the PDU session establishment procedure, the UE 3 sends the UE battery reporting capability of the UE 3 to the AMF 70 or to the SMF 73 in an existing NAS message or in a new NAS message. The AMF 70 or the SMF 71 stores the UE battery reporting capability of the UE 3. The AMF 70 or the SMF 71 may forward to an existing Network Function (e.g. UDM 75, PCF 73 ) in an existing message between the AMF 70 or the SMF 71 and the NF. The AMF 70, the SMF 71 or an existing NF may trigger the current UE battery reporting as the procedure defined above in the First example of the First aspect.

[0137] <Variant 4 of the Second Example of the First Aspect> 　　In another example, for each UE battery status range, the UDM 75 or PCF 73 may define a QoS value. When the UE battery status falls on a particular range the UDM 75 or PCF 73 or any existing NF uses the corresponding QoS value to modify the QoS using the procedure defined in the embodiments defined here. For example, the UE 3, the UDM 75 or the PCF 73 may maintain following battery power status and QoS mapping.

[0138]

[0139] <Variant 5 of the Second Example of the First Aspect> 　　One example, when a NF (e.g. AMF 70 or SMF 71) or AF 201, may determine that the UE battery status is below some threshold then the NF determines to move or handover the PDU session to a RAT (NR to E-UTRAN, or NR to non-3GPP access) or system (e.g. 5GS to EPS) where the UE 3 at the target RAT or system may consume less battery power.

[0140] <Variant 6 of the Second Example of the First Aspect> 　　One example, when the PDU session is established already and the UE 3 reported UE battery status, the NF (e.g. AMF 70 or SMF 71) determines to change the QoS for the PDU session, the NF sends an existing NAS message or a new NAS message to the UE 3 containing the target QoS. On receiving this NAS message, the UE 3 may show or display the target QoS to the user. When the user accepts the target QoS and then UE 3 may send an existing NAS message to the NF indicating the user has accepted the target QoS. On receiving the message, the NF may decide to modify the QoS to the target QoS sent to the UE 3. The NF may perform the network initiated SM procedure to modify the QoS as defined in TS 23.502 and TS 24.501.

[0141] <Variant 7 of the Second Example of the First Aspect> 　　In one example, if the battery status, e.g. battery charge level, falls below some threshold, then the NF (e.g. UDM 75, SMF 71, AMF 70, PCF 73) initiates deactivation of the PDU session. The NF (e.g. UDM 75, PCF 73) initiates deactivation of the PDU session to the SMF 71. The SMF 71 initiates the PDU session deactivation procedure as defined in the TS 23.501 and TS 23.502. In this case, the SMF 71 includes 5GSM cause IE in the PDU SESSION RELEASE COMMAND message indicating that the PDU session is released due to battery status falling below some threshold. When the UE 3 receives the PDU SESSION RELEASE COMMAND message, the UE 3 may not initiate the PDU session establishment procedure for this PDU session e.g. the S-NSSAI and APN combination.

[0142] In anoter example, the UE 3 may send user consent in the registration request message or in the PDU session establishment request message to the AMF 70 or SMF 71 to indicate that the user is willing to modify the QoS. When the NF (e.g. AMF 70 / SMF 71 / PCF 73) receives the user consent information, it checks whether the UE 3 has sent user consent to modify the QoS when the NF decides to modify the QoS based on the battery status. If the user has given consent to modify the QoS then the NF (e.g. AMF 70 / SMF 71 / PCF 73) will modify the QoS.

[0143] <Third Example of the First Aspect> 　　The Third Example of the First Aspect in Fig. 3 includes a mechanism for UE battery status provision by the AF 201 to the PCF 73 via NEF 79 within the Nnef_ServiceParameter Update service operation. The UE battery status, for example expressed in percentage e.g. in battery charge level represented in percentage of the whole battery capacity or in any other quantitative expression, is used by the PCF 73 or by the UDR 80 for decision making on whether to adjust the QoS for an ongoing PDU Session if the UE Battery level drops to or goes below a QoS adjustment battery threshold which is a parameter in the UE subscription or is configured by the network operator.

[0144] The detailed process of the Third Example of the First Aspect is described below with reference to Fig. 3.

[0145] Step 1. The UE 3 has been registered with the network and has established a PDU Session with certain QoS. During the PDU Session establishment the PCF 71 may have already retrieved from the UDR 80 the QoS adjustment battery threshold parameter (or information about the battery threshold for the QoS adjustment for the UE 3) as a subscription information as per Fig. 2. UE battery status (e.g. in percentage level or in any other quantitative expression) is assumed to be regularly provided to the AF 201 by the UE 3 on the application level. Refer to Step 2 in Fig. 1 for details on the UE battery status presentation and to Step 10 in Fig. 1 for the details on QoS adjustment battery threshold presentation.

[0146] Step 2. The AF 201 regularly updates the 3GPP system with the UE battery status for the UE 3.

[0147] Step 3. The AF 201 makes use of the Nnef_ServiceParameter Update service operation to regularly update the 3GPP system via the NEF 79 with the UE battery status of UE 3. The UE battery status parameter or any other notation for a parameter with the purpose to indicate the UE battery level or information about a battery status of the UE 3 may be represented in percentage of the maximum battery level or in any other quantitative expression.

[0148] Step 4. The NEF 79 stores the UE battery status provided by the AF 201 in the UDR 80 as an application subscription or as a Policy control subscription information.

[0149] Step 5. The UDR 80 triggers notification to the PCF 71 and provides the UE battery status and the QoS adjustment battery threshold for UE 3 which were provided by the AF 201 via the PCF 79.

[0150] Step 6. The UDR 80 sends Nudr_DM_Notify message to the PCF 73 in which the UDR 80 includes the UE ID and the UE battery status for the UE 3. If the UDR 80 holds a QoS adjustment battery threshold parameter in the UE subscription information for the UE 3, the UDR 80 also includes the QoS adjustment battery threshold parameter in the Nudr_DM_Notify message to the PCF 71.

[0151] Step 7. The PCF 73 stores the UE battery status and the QoS adjustment battery threshold parameters received from the UDR 80. The PCF 73 checks if the UE battery status for UE 3 is equal or less than the QoS adjustment battery threshold for the UE 3. If the UE battery status for UE 3 is equal or less than the QoS adjustment battery threshold for the UE 3, the PCF 73 triggers a request to SMF 71 for QoS update of the ongoing PDU Session for UE 3.

[0152] For example, the PCF 73 may determine to send a request for QoS adjustment to the SMF 73, based on the retrieved QoS adjustment battery threshold parameter for UE 3 (or information about a battery status of the UE 3) and the UE battery status (or information about the battery status of the UE 3).

[0153] Step 8. The PCF 73 triggers QoS adjustment for the requested PDU Session or for the ongoing PDU Session by UE 3. The PCF 73 sends to SMF 71 instruction for QoS adjustment via a new message on the PCF / SMF interface or via one of the existing messages on the PCF / SMF interface in which message the PCF 73 includes as a parameter the new QoS for the ongoing PDU Session. The PCF 73 may also include the UE ID and the UE battery status for UE 3 in the message to the SMF 71.

[0154] For detailed PCF 73 behaviour refer to Step 8 in Fig. 2.

[0155] For example, the PCF 73 may send a request for updating (changing) the QoS adjustment to the SMF 73, based on the retrieved QoS adjustment battery threshold parameter for UE 3 (or information about the battery status of the UE 3) and the UE battery status.

[0156] Step 9. If the SMF 71 receives a request for QoS adjustment for UE 3 from the PCF 73, the SMF 71 also forwards the new updated QoS to the RAN 5 so that the RAN 5 can optimize the radio bearers for UE battery saving purpose. The PCF 73 may also include the UE ID and the UE battery status for UE 3 in the message to the RAN 5.

[0157] Step 10. If the SMF 71 receives a request for QoS adjustment for UE 3 from the PCF 73, the SMF 71 triggers the PDU Session Modification procedure as per 3GPP TS 23.502 [3] in order to update the current QoS of the PDU Session to the new QoS requested by the PCF 73 so that a power / battery saving in the UE 3 is achieved.

[0158] <Fourth Example of the First Aspect> 　　The Fourth Example of the First Aspect in Fig. 4 includes a mechanism for UE battery status provision by the AF 201 to the PCF 73 via NEF 79 within the Nnef_ServiceParameter Update service operation. The UE battery status, for example expressed in percentage e.g. in battery charge level represented in percentage of the whole battery capacity or in any other quantitative expression, is used by the UDM 75 for decision making on whether to adjust the QoS for an ongoing PDU Session if the UE battery level drops to or goes below the QoS adjustment battery threshold which is a parameter in the UE subscription or is configured by the network operator.

[0159] The detailed process of the Fourth Example of the First Aspect is described below with reference to Fig. 4.

[0160] Step 1. The UE 3 has been registered with the network and has established a PDU Session with certain QoS. During the PDU Session establishment the PCF 71 may have already retrieved from the UDM 75 or from UDR 80 the QoS adjustment battery threshold parameter as a subscription information as per Fig. 2. UE battery status (e.g. in percentage level or in any other quantitative expression) is assumed to be regularly provided to the AF 201 by the UE 3 on the application level. Refer to Step 2 in Fig. 1 for details on the UE battery status presentation and to Step 10 in Fig. 1 for the details on QoS adjustment battery threshold presentation.

[0161] Step 2. The AF 201 regularly updates the 3GPP system with the UE battery status for the UE 3.

[0162] Step 3. The AF 201 makes use of the Nnef_ServiceParameter Update service operation to regularly update the 3GPP system via the NEF 79 with the UE battery status of UE 3. The UE battery status parameter or any other notation for a parameter with the purpose to indicate the UE battery level is represented in percentage of the maximum battery level for that UE or in any other quantitative expression.

[0163] Step 4. The NEF 79 stores the UE battery status provided by the AF 201 in the UDM 75 as a subscription information.

[0164] Step 5. The UDM 75 play the QoS adjustment decision making role in the example solution. The UDM 75 checks whether the UE battery status for the UE 3 is equal or lower than the QoS adjustment battery threshold for the UE 3. If the UE battery level for UE 3 is equal or less than the QoS adjustment battery threshold for UE 3, the UDM 75 requests the SMF 71 for QoS update for the ongoing PDU Session. For detailed UDM 75 behaviour refer to Variant 1 of the Second Example of the First Aspect.

[0165] Step 6. The UDM 75 sends Nudm_SDM_Notification message to the SMF 71 in which the UDM 75 includes the new QoS for the PDU Session, the UE ID and the UE battery status for the UE 3.

[0166] Step 7. If the SMF 71 receives a request for QoS adjustment for UE 3 from the UDM 75 in the Nudm_SDM_Notification message with new QoS parameter included, the SMF 71 forwards the new updated QoS parameters for UE 3 to the RAN 5 so that the RAN 5 can optimize the radio bearers for UE battery saving purpose. The SMF 71 may also include the UE ID and the UE battery status for the UE 3 in the QoS Update request message to the RAN 5.

[0167] Step 8. If the SMF 71 receives a request for QoS adjustment for UE 3 from the UDM 75 in the Nudm_SDM_Notification message in Step 6 with new QoS parameter included, the SMF 71 triggers the PDU Session Modification procedure as per 3GPP TS 23.502 [3] with request to update the current QoS of the PDU Session to the new QoS received from the UDM 75 so that- a power / battery saving in the UE is achieved.

[0168] <Fifth Example of the First Aspect> 　　In Figs. 1-4, the names of network nodes (e.g., AMF, SMF, PCF, UDM, UDR, NEF, RAN, etc.) are described using the nomenclature of the 5G system. However, this First Aspect is also applicable to systems other than 5G (such as 6G system and 7G system). In such cases, the network nodes in these Figures can be interpreted as 'core network nodes' or 'network nodes'. In other words, this First Aspect can be applied to systems other than 5G systems (such as 6G system and 7G system etc.) by replacing the names of nodes in the 5G system with "core network nodes" or "network nodes", etc.

[0169] <<Second Aspect>> 　　The First Aspect includes an architecture and a mechanism for UE energy credit control with the UE Policy.

[0170] <First Example of the Second Aspect> 　　The First Example of the Second Aspect in Fig. 5 includes a mechanism for UE indication of energy credit policy control capability during the Registration procedure. At UE registration, the UE 3 indicates its capability for energy credit policy control support in the Registration Request message. If the UE 3 indicated capability for energy credit policy control and the UE subscription holds UE energy credit, the network may inform the UE about the remaining energy credit for consumption by the UE with the UE energy credit parameter.

[0171] The detailed process of the First Example of the Second Aspect is described below with reference to Fig. 5.

[0172] Step 1. The UE 3 may hold 'UE energy credit' and 'UE energy credit threshold' as a subscription information in the UDM 75. - the UE energy credit is the amount of energy the UE 3 is allocated for consumption from the network for specific time defined by the network operator. The amount of UE energy credit may be expressed in energy units or energy credits, watt, Joule, bit / Joule or in any other expression for energy consumption by the UE 3 from the network in order to indicate the level of the consumed energy or the level of the remaining energy per UE. The UE energy credit may be subject to SLA and may depend on UE 3 subscription details and priorities. The UE energy credit may be an indication or information indicating an amount of energy that is available for the UE 3. The UE energy credit may be an indication or information indicating a total amount of energy that is available for the UE 3. The UE energy credit may be an indication or information indicating a remaining amount of energy that is available for the UE 3. - the UE energy credit threshold is the amount of energy where after the UE 3 energy consumption exceeds this threshold, e.g., the remaining UE energy credit drops to or below the UE energy credit threshold, then UE 3 is considered to have a low energy and the UE 3 may be subject to service restrictions depending on the operator energy credit policies. The UE energy credit threshold may be expressed in energy units or energy credits, watt, Joule, bit / Joule or in any other expression for energy consumption by the UE 3 from the network, comparable with the UE energy credit, in order to indicate the level of the consumed energy or the level of the remaining energy per UE. The UE energy credit threshold may be a value. The UE energy credit threshold may be an indication or information indicating threshold to determine (consider) that the UE is a lower energy state. For example, the UE 3 may be determined (or considered) to be restricted a service that the UE 3 receives when the energy of the UE 3 exceeds the UE energy credit threshold.

[0173] Step 2. The UE 3 initiates the UE registration procedure. First, the UE 3 creates the RRC connection with the RAN 5 by sending RRC Connection Setup Request message or RRC Setup Request or a message for establishing the RRC connection to the RAN 5. The RRC Connection Setup Request message or the RRC Setup Request or the message for establishing the RRC connection may include at least one of the following parameters: - energy credit policy control capability - the energy credit policy control capability parameter or any other notation for a parameter which indicates the UE capability for energy credit policy control feature support. The energy credit policy control capability parameter may be an indication or information indicating that the UE 3 supports the energy credit policy control. The energy credit policy control capability parameter may be an indication or information indicating whether the UE 3 supports the energy credit policy control. The UE 3 includes the energy credit policy control capability parameter in the RRC Connection Setup Request message or in the RRC Setup Request message or in a message for establishing of a RRC connection from the UE 3 to the RAN 5 when the UE 3 has a capability to support energy credit policy control feature. energy credit policy control may mean that the UE can be controlled based on the energy credit of the UE or based on the rest of energy (battery) of the UE.

[0174] Step 3. If the UE 3 indicated capability for energy credit policy control to the RAN 5, RAN 5 may use this information in order to select an AMF which also supports or is compatible with the energy credit policy control feature. The RAN 5 confirms the RRC connection establishment by returning to the UE 3 the RRC Connection Setup message or RRC Setup message or a message for establishing the RRC connection from the RAN 5 to the UE 3.

[0175] Step 4. The RRC connection establishment is completed by sending from the UE 3 to RAN 5 the RRC Connection Setup Complete message or RRC Setup Complete message or a message for establishing the RRC connection from the UE 3 to the RAN 5. This message carries the Registration Request message from the UE 3 to the AMF 70. The UE 3 includes the energy credit policy control capability parameter in both messages, e.g. in the RRC Connection Setup Complete message to the RAN 5 or RRC Setup Complete message or a message for establishing the RRC connection from the UE 3 to the RAN 5 and in the Registration Request message to the AMF 70.

[0176] For example, the RRC Connection Setup Complete message or RRC Setup Complete message or a message for establishing the RRC connection from UE 3 to the RAN 5 may include the energy credit policy control parameter.

[0177] For example, the Registration Request message or any other NAS message from the UE 3 to the AMF 70 may include the energy credit policy control capability parameter.

[0178] Step 5. If the energy credit policy control capability parameter was included in the RRC connection request message or RRC Connection Setup Complete message from the UE 3, the RAN 5 makes use of the energy credit policy control capability parameter for an AMF selection i.e. the RAN 5 selects an AMF node e.g. AMF 70 which supports the energy credit policy control capability feature.

[0179] Step 6. After AMF selection (e.g., after selection of the AMF 70), the RAN 5 forwards the Registration Request message from UE 3 to the AMF 70 within the UE Initial message. The Registration Request message contains the energy credit policy control capability parameter. The RAN 5 may also pass the energy credit policy control capability parameter in an NGAP Message e.g. Initial UE message to the AMF 70.

[0180] Step 7. If the UE 3 indicated energy credit policy control capability in the Registration Request message, the AMF 70 stores the energy credit policy control capability parameter in the UE context within the AMF 70. Then, at location mobility when the UE 3 moves to a new AMF, the AMF 70 provides the energy credit policy control capability parameter together with the UE context to the target AMF.

[0181] Step 8. The AMF 70 continues the UE registration procedure by sending a Nudm_UECM_Registration Request message to the UDM 75. The AMF 70 may include in the message to the UDM 75 the energy credit policy control capability parameter if received from the UE 3 within the Registration Request message.

[0182] Step 9. If the UE 3 indicated energy credit policy control capability, the UDM 75 checks if the UE 3 has an allocated UE energy credit and an UE energy credit threshold as a subscription information.

[0183] For example, the energy credit policy control capability parameter may be an indication or information indicating whether the UE 3 supports the energy credit policy control. In this case, when the energy credit policy control capability parameter indicates that the UE 3 supports the energy credit policy control, then the UDM 75 may determine whether the UE 3 has an allocated UE energy credit and a UE energy credit threshold as a subscription information. When the energy credit policy control capability parameter indicates that the UE 3 does not support the energy credit policy control, then the UDM 75 may determine that the UE 3 does not support the energy credit policy control.

[0184] Step 10. If the UE 3 indicated energy credit policy control capability and the UDM 75 determines that the UE 3 holds UE energy credit and UE energy credit threshold as a subscription information, the UDM 75 returns Nudm_UECM_Registration Response message in which the UDM 75 includes at least one of the following parameters: - UE energy credit - the UE energy credit is the amount of energy the UE 3 is allocated for consumption from the network for specific time defined by the network operator. The amount of UE energy credit may be expressed in energy units or energy credits, watt, Joule, bit / Joule or in any other expression for energy consumption by the UE 3 from the network in order to indicate the level of the consumed energy or the level of the remaining energy for consumption for the UE 3. The UE energy credit may be subject to SLA and may depend on UE 3 subscription details and priorities. The UE energy credit may be an indication or information indicating an amount of energy that is available for the UE 3. The UE energy credit may be an indication or information indicating a total amount of energy that is available for the UE 3. The UE energy credit may be an indication or information indicating a remaining amount of energy that is available for the UE 3. - UE energy credit threshold - the UE energy credit threshold is the amount of energy where after the UE 3 energy consumption exceeds this threshold, e.g the remaining UE energy credit drops to or below the UE energy credit threshold, then the UE 3 is considered to have a low energy and the UE 3 may be subject to service restrictions depending on the operator energy credit policies and configurations. The UE energy credit threshold may be expressed in energy units or energy credits, watt, Joule, bit / Joule or in any other expression for energy consumption by the UE 3 from the network, comparable with the UE energy credit, in order to indicate the level of the consumed energy or the level of the remaining energy per UE. The UE energy credit threshold may be a value. The UE energy credit threshold may be an indication or information indicating threshold to determine (consider) that the UE is a lower energy state. For example, the UE 3 may be determined (or considered) to be restricted a service that the UE 3 receives when the energy of the UE 3 exceeds the UE energy credit threshold.

[0185] Step 11. The AMF 70 stores the remaining UE energy credit and the UE energy credit threshold parameters in the UE context within the AMF 70. Then, at location mobility, when the UE 3 moves to a new AMF, the AMF 70 provides the remaining UE energy credit and the UE energy credit threshold parameters together with the UE context to the target AMF.

[0186] Step 12. The AMF 70 may forward the UE ID and the remaining UE energy credit to the RAN 5 via one of the existing N2 message or in a new N2 message. The RAN 5 may consider the UE energy credit (i.e. the remaining UE energy credit for UE 3) in decisions for activating one or more of the available for the RAN 5 energy saving features.

[0187] Step 13. The AMF 70 confirms the UE registration procedure by sending the Registration Accept message in which the AMF 70 includes the remaining UE energy credit and the UE energy credit threshold parameters. The UE 3 may store the remaining UE energy credit and the UE energy credit threshold parameters in a non-volatile memory within UE 3. Then, the UE 3 may indicate to the user information related to the UE energy credit remaining for consumption by the UE 3. The UE 3 may also deploy some service restrictions within the UE 3 and may indicate to the network a preference for energy saving if the remaining UE energy credit has dropped below the UE energy credit threshold. The AMF 70 may send, to the UE 3, the Registration Accept message including an indication or information indicating a total amount or a remaining amount of energy that is available for the UE 3.

[0188] The AMF 70 may send, to the UE 3, the Registration Accept message including an indication or information indicating threshold to determine (consider) that the UE is a lower energy state.

[0189] In the First Example of the Second Aspect, the UE 3 may send, to a core network node, a registration request message including information indicating that the UE supports an energy credit policy control. The UE 3 may receive, from the core network node, a registration accept message including a first information indicating that the amount of energy or the remaining energy being available for the UE 3 and a second information for determining that the UE is in a Low energy state.

[0190] <Variant 1 of the First Example of the Second Aspect> 　　In one example, UE 3 may hold the UE energy credit and the UE energy credit threshold subscription information in the UDR 80 instead of UDM 75. In this case at Step 8 the AMF 70 may retrieve the UE energy credit and the UE energy credit threshold parameters from the UDR 80.

[0191] <Variant 2 of the First Example of the Second Aspect> 　　In one example, The AMF 70 may deliver the UE energy credit and the UE energy credit threshold parameters received from the UDM 75 or from the UDR 80 any time after Step 10. The AMF 70 may trigger the UE Configuration Update procedure and may deliver the UE energy credit and the UE energy credit threshold parameters to the UE 3 within the UE Configuration Update Command message.

[0192] <Second Example of the Second Aspect> 　　The Second Example of the Second Aspect in Fig. 6 includes a mechanism where a UE 3 may be allocated with UE energy credit and UE energy credit threshold as part of its subscription information. When the UE energy credit drops to or below the UE energy credit threshold, the UDR 80 notifies the PCF 73. In the PCF 73 the Route Selection Descriptor (RSD) in the URSP rules has a new attribute 'UE energy credit'. When the UE energy credit for a certain UE becomes Low, the PCF 73 sets the UE energy credit attribute of the RSD for that UE to Low and the PCF 73 triggers URSP rules update for the UE 3.

[0193] The detailed process of the Second Example of the Second Aspect is described below with reference to Fig. 6.

[0194] Step1. The UE 3 may be allocated with UE energy credit and UE energy credit threshold as part of its subscription information. - UE energy credit - the UE energy credit is the amount of energy the UE 3 is allocated for consumption from the network for specific time defined by the network operator. The amount of UE energy credit may be expressed in energy units or energy credits, watt, Joule, bit / Joule or in any other expression for energy consumption by the UE 3 from the network in order to indicate the level of the remaining energy for consumption for the UE 3. The UE energy credit may be subject to SLA and may depend on UE 3 subscription details and priorities. The UE energy credit may be an indication or information indicating an amount of energy that is available for the UE 3. The UE energy credit may be an indication or information indicating a total amount of energy that is available for the UE 3. The UE energy credit may be an indication or information indicating a remaining amount of energy that is available for the UE 3. - UE energy credit threshold - the UE energy credit threshold is the amount of energy where after the UE 3 energy credit consumption exceeds this threshold, e.g the remaining UE energy credit drops below the UE energy credit threshold, the UE 3 is considered to have a low energy and the UE 3 may be subject to service restrictions depending on the operator energy credit policies and configurations. The UE energy credit threshold may be expressed in energy units or energy credits, watt, Joule, bit / Joule or in any other expression for energy consumption by the UE 3 from the network, comparable with the UE energy credit, in order to indicate the level of the consumed energy or the level of the remaining energy per UE. The UE energy credit threshold may be a value. The UE energy credit threshold may be an indication or information indicating threshold to determine (consider) that the UE is a lower energy state. For example, the UE 3 may be determined (or considered) to be restricted a service that the UE 3 receives when the energy of the UE 3 exceeds the UE energy credit threshold.

[0195] The UDR 80 monitors and regularly compare the remaining UE energy credit for UE 3 and when the UE energy credit for UE 3 drops to or below the UE energy credit threshold for UE 3, the UDR 80 notifies the PCF 73. For example, when the UDR 80 determines that the UE energy credit for UE 3 drops to or below the UE energy credit threshold for UE 3, the UDR 80 notifies the PCF 73.

[0196] Step 2. The UDR 80 sends to the PCF 73 the Nudr_DM_Notify message in which the UDR 80 includes the UE ID of the UE 3 for which the UE energy credit has dropped to or below the UE energy credit threshold and the UDR 80 also includes in the Nudr_DM_Notify message the UE energy credit parameter set to Low. For example, the PCF 73 may receive, from the UDR 80, information indicating that an energy state of a User Equipment (UE) is Low.

[0197] Step 3. A new attribute 'UE energy credit' is added to the Route Selection Descriptor (RSD) in the URSP rules for the UE 3. When the UDR 80 indicates that the UE energy credit for UE 3 has dropped below the UE energy credit threshold for the UE 3, i.e. the UE energy credit for the UE 3 is indicated as Low (or as any other expression to indicate that the UE energy credit threshold is reached or crossed meaning the remaining UE energy credit becomes less than the UE energy credit threshold) from the UDR 80, then the PCF 73 sets the UE energy credit attribute of the Route Selection Descriptor (RSD) in the URSP rules for UE 3 to Low and the PCF 73 triggers the URSP rules update procedure for the UE 3.

[0198] Step 4. The PCF 73 sends the Namf_Communication_N1N2MessageTransfer message to the AMF 70 in which message the PCF 73 includes the UE ID of UE 3 and the new updated URSP rules for UE 3 with the UE energy credit attribute in the Route Selection Descriptor (RSD) of the URSP rules for UE 3 set to Low. For example, the PCF 73 may send, to the AMF 70, information indicating that the UE energy credit attribute is Low. For example, the PCF 73 may send, to the AMF 70, second information indicating a behaviour of the UE when the energy state of the UE is Low.

[0199] Step 5. When the AMF 70 receives a request for URSP rules update from the PCF 73, the AMF 70 triggers the UE Configuration Update procedure and forwards to the UE 3 the new updated URSP rules in the UE Configuration Update Command with the UE energy credit attribute in the Route Selection Descriptor (RSD) of the URSP rules for UE 3 set to Low. For example, the AMF 70 may send, to the UE 3, the information indicating that the UE energy credit attribute is Low. For example, the UE 3 receives, from the AMF 70, information indicating a behavior of the UE 3 when the energy state of the UE 3 is Low.

[0200] Step 6. When the UE 3 receives the new updated URSP rules in the UE Configuration Update Command where the UE energy credit attribute in the Route Selection Descriptor (RSD) of the URSP rules for UE 3 is set to Low or set to any other expression to indicate that the UE energy credit threshold is reached or crossed meaning the remaining UE energy credit becomes less than the UE energy credit threshold, the UE 3 may trigger or transition to or change to energy saving mode within UE 3 and also the UE 3 may indicate to the network an energy efficiency preference or an energy efficiency priority for at least one service or all services or only for services triggered by Applications other than IMS or Real-Time interaction which may mean service quality (e.g. QoS) degradation by the network for services that are not time sensitive like IMS and Real Time interaction services with the purpose of saving on UE energy credits for the UE 3. For example, an energy efficiency preference may indicate the preference degree of service which is tolerated (or allowed) degradation of service quality when the UE 3 saves the energy credit. For example, an energy efficiency priority may indicate the order of service which is tolerated (or allowed) degradation of service quality when the UE 3 saves the energy credit.

[0201] For example, the energy efficiency preference may be the preference of service which is tolerated (or allowed) degradation of service quality when the UE 3 saves the energy credit.

[0202] For example, the energy efficiency priority may indicate the order of service which is tolerated (or allowed) degradation of service quality when the UE 3 saves the energy credit.

[0203] For example, the UE 3 may indicate, to the network, that the energy efficiency preference or the energy efficiency priority of the at least one service which the UE 3 receives.

[0204] For example, the UE 3 may indicate, to the network, preference for one or more of the energy efficiency or energy saving services the UE 3 is allowed by the UE 3 subscription information in the UDR 80 or UDM 75. The UE 3 may be subscribed for one or more energy efficiency or energy saving services, for example a UE subscription for a service where the network may deploy UE energy efficiency / saving features without degrading the services, e.g. QoS, for the UE 3 or a subscription for a service where the network may deploy UE energy efficiency / saving features which may degrade the services, e.g. QoS, for the UE 3. The UE 3 energy efficiency / saving preference may be indicated to the network, for example, during the Registration procedure within the Registration Request message or during the PDU Session establishment procedure within the PDU Session Establishment Request message or during the PDU Session modification procedures within the PDU Session Modification Request message.

[0205] If the UE 3 is in connected mode with active PDU Sessions, the UE 3 may even drop at least one services with low priority. The UE 3 may maintain the energy saving behaviour until the UE 3 is updated with information about URSP rules where the UE energy credit attribute in the Route Selection Descriptor (RSD) of the URSP rules is not set to Low anymore.

[0206] For example, when the UE 3 receives the information indicating that the UE energy credit attribute is set to Low, then the UE 3 may maintain the energy saving state until the UE 3 may receive information indicating that the energy state of the UE 3 is not Low.

[0207] For example, when the UE 3 receives the information indicating that the UE energy credit attribute is set to Low, then the UE 3 may indicate, to the network (e.g., AMF 70, PCF 73, SMF 71, UDR 80, RAN 5 etc.), that the energy efficiency preference (or the energy efficiency priority) of the at least one service.

[0208] For example, when the UE 3 receives the information indicating that the UE energy credit attribute is set to Low, then the UE 3 may send, to the network (e.g., AMF 70, PCF 73, SMF 71, UDR 80, RAN 5 etc.), information indicating that the energy efficiency preference (or the energy efficiency priority) of the at least one service.

[0209] For example, when the UE 3 receives the information indicating that the UE energy credit attribute is set to Low, then the UE 3 may consider whether or not to drop or terminate at least one service.

[0210] For example, when the UE 3 receives the information indicating that the UE energy credit attribute is set to Low, then the UE 3 may drop or terminate at least one service.

[0211] For example, the UE 3 may send, to the AMF 70, the information indicating that the energy efficiency preference of the at least one service for the UE 3.

[0212] In the Second Example of the Second Aspect, the UE 3 may receive, from a first core network node, first information indicating a behavior of the UE when the energy state of the UE is Low, and send, to the first core network node, second information indicating that the energy efficiency preference of the at least one service for the UE. A first core network node may receive, from a second core network node, information indicating that an energy state of a User Equipment (UE) is Low, and may send, to a third core network node, information indicating that the energy state of the UE energy is Low.

[0213] <Third Example of the Second Aspect> 　　The Third Example of the Second Aspect in Fig. 7 includes a mechanism where a network slice may be allocated with S-NSSAI energy credit and with S-NSSAI energy credit threshold as part of its subscription information. When the S-NSSAI energy credit for certain S-NSSAI drops below the S-NSSAI energy credit threshold, the UDR 80 notifies the PCF 73. The Route Selection Descriptor (RSD) in the URSP rules in the PCF 73 has an attribute 'Network Slice Selection'. When the S-NSSAI energy credit for a certain S-NSSAI becomes Low, the PCF 73 may replace this S-NSSAI within the RSD with an Alternatives S-NSSAI for all or some UEs or replaces this S-NSSAI within the RSD with an Alternatives S-NSSAI for some Applications only (e.g. IMS and / or Real-Time Applications so that energy saving on the S-NSSAI with Low energy credit is achieved. Then the PCF 73 updates the affected UEs with the updated URSP rules. In the Third Example of the Second Aspect, each S-NSSAI (or each network slice, not each UE) may be allocated the energy credit and the energy credit threshold to them.

[0214] The detailed process of the Third Example of the Second Aspect is described below with reference to Fig. 7.

[0215] Step1. A network slice may be allocated with 'S-NSSAI energy credit' and with 'S-NSSAI energy credit threshold' as part of its subscription information. When the S-NSSAI energy credit for certain S-NSSAI drops below the S-NSSAI energy credit threshold for that S-NSSAI, the UDR 80 notifies the PCF 73. - S-NSSAI energy credit - the S-NSSAI energy credit is the amount of energy the S-NSSAI is allocated for consumption from the network for specific time defined by the network operator. The amount of S-NSSAI energy credit may be expressed in energy units or energy credits, watt, Joule, bit / Joule or in any other expression for energy consumption by the S-NSSAI from the network in order to indicate the level of the remaining energy for consumption for that S-NSSAI. The S-NSSAI energy credit may be subject to SLA or network operation policy. The S-NSSAI energy credit may be an indication or information indicating an amount of energy that is available for the S-NSSAI. The S-NSSAI energy credit may be an indication or information indicating a total amount of energy that is available for using the network service corresponding to the S-NSSAI. The S-NSSAI energy credit may be an indication or information indicating a remaining amount of energy that is available for using the network service corresponding to the S-NSSAI. - S-NSSAI energy credit threshold - the S-NSSAI energy credit threshold is the amount of energy where after the S-NSSAI energy credit consumption exceeds the S-NSSAI energy credit threshold, e.g. the remaining available S-NSSAI energy credit drops to or below the S-NSSAI energy credit threshold, the S-NSSAI is considered to have a Low energy and the S-NSSAI may be subject to service restrictions depending on the operator energy credit policies and configurations. The S-NSSAI energy credit threshold may also be expressed in energy units or energy credits, watt, Joule, bit / Joule or in any other expression for energy consumption by the S-NSSAI from the network, comparable with the S-NSSAI energy credit, in order to indicate the level of the consumed energy or the level of the remaining energy per S-NSSAI. The S-NSSAI energy credit threshold may be a value. The S-NSSAI energy credit threshold may be an indication or information indicating threshold to determine (consider) that a lower energy is remained to use the S-NSSAI. For example, it may be determined (or considered) to be restricted a service corresponding to the S-NSSAI used by the UE 3 when the remained energy for the S-NSSAI drops (or exceeds) the S-NSSAI energy credit threshold.

[0216] The UDR 80 monitors and regularly compare the remaining S-NSSAI energy credit for the S-NSSAI and when the S-NSSAI energy credit for certain S-NSSAI drops below the S-NSSAI energy credit threshold for that S-NSSAI, the UDR 80 notifies the PCF 73. For example, when the UDR 80 determines that the S-NSSAI energy credit drops to or below the S-NSSAI energy credit threshold for the S-NSSAI, the UDR 80 notifies the PCF 73. For example, when the UDR 80 determines that the S-NSSAI energy credit drops to or below the S-NSSAI energy credit threshold for the S-NSSAI, then the UDR 80 may send, to the PCF 73, information indicating that the S-NSSAI energy credit is Low.

[0217] Step 2. The UDR 80 sends to the PCF 73 the Nudr_DM_Notify message in which the UDR 80 includes the S-NSSAI ID for which the S-NSSAI energy credit has dropped to or below the S-NSSAI energy credit threshold and the S-NSSAI energy credit threshold parameter set to Low and the UDR 80 may also include one or more UE IDs to identify the UEs (e.g. UE 3) for which the S-NSSAI energy credit Low is applicable. In one example the S-NSSAI energy credit set to Low parameter may be applicable to all UEs subscribed to that S-NSSAI. For example, the UDR 80 may send, to the AMF 70, information indicating that the S-NSSAI energy credit of the S-NSSAI (S-NSSAI-1) is Low.

[0218] Step 3. The Route Selection Descriptor (RSD) in the URSP rules within the PCF 73 has an attribute called 'Network Slice Selection'. The Network Slice Selection attribute in the RSD of the URSP rules defines per each UE, e.g. UE 3 the S-NSSAI and DNN the Applications of that UE 3 shall be selecting per Application granularity as per URSP rules description in TS23.503. When the PCF 73 receives the S-NSSAI energy credit parameter (or indication or information) set to Low (which means less energy remains for the S-NSSAI) from the UDR 80 for certain S-NSSAI, the PCF 73 may: - replaces this S-NSSAI within the 'Network Slice Selection' policy within the URSP rules with an Alternatives S-NSSAI for the UE(s) indicated by the UDR 80, e.g. UE 3. or - replaces this S-NSSAI within the Network Slice Selection' policy within the URSP rules with an Alternatives S-NSSAI for some Applications only of the associated UE(s), e.g. UE 3 (e.g. IMS and / or Real-Time Applications which would not tolerate QoS degradation on the S-NSSAI for which the S-NSSAI energy credit is Low).

[0219] For example, when the PCF 73 receives, from the UDR 80, information indicating that the S-NSSAI energy credit parameter (or indication or information) of a S-NSSAI (S-NSSAI 1) is Low, then the PCF 73 may replace the S-NSSAI (S-NSSAI 1) to alternate S-NSSAI (S-NSSAI 2). The replaced S-NSSAI (S-NSSAI 2) may be specified by the UDR 80 or other network node or network operator. For example, the replaced S-NSSAI (S-NSSAI 2) may be related to a service that is not allowed or tolerated QoS degradation.

[0220] This way an energy saving is achieved on the S-NSSAI, the S-NSSAI for which the S-NSSAI energy credit parameter is set to Low by replacing it for some UE or all UEs (e.g. UE 3) or for some Applications only on some UEs, e.g. UE 3 with an Alternative S-NSSAI. Then the PCF 73 updates the affected UEs (e.g. UE 3) with the updated Network Slice Selection policy in the URSP rules.

[0221] Step 4. The PCF 73 sends the Namf_Communication_N1N2MessageTransfer message to the AMF 70 in which message the PCF 73 includes one or more UE IDs and the new updated URSP rules for these UEs. For example, the PCF 73 may send, to the AMF 70, information for network slice selection (network slice selection information). For example, the information about network slice selection may be used to select S-NSSAI(s). For example, the information about network slice selection may indicate that the rule or policy.

[0222] Step 5. When the AMF 70 receives a request for URSP rules update from the PCF 73, the AMF 70 triggers the UE Configuration Update procedure and forwards the updated URSP rules to the UE(s) identified by the UE ID(s), e.g. UE 3. If the UE 3 was in idle state, i.e. not connected with the network when the AMF received a request for URSP riles update, the AMF 70 first pages the UE3 and after UE 3 respond and establishes connection with the AMF 70, the AMF 70 triggers the UE Configuration Update procedure and forwards the updated URSP rules to the UE(s) identified by the UE ID(s), e.g. UE 3.

[0223] For example, the AMF 70 may send, to the UE 3, the information for network slice selection.

[0224] Step 6. When UE 3 receives the updated Network Slice Selection policy in the URSP rules in the UE Configuration Update Command the UE 3 store the updated URSP rules and start applying the updated Network Selection policy where the S-NSSAI with the S-NSSAI energy credit set to Low was replaced with Alternative S-NSSAI. Based on the updated Network Slice Selection policy within the URSP rules, the UE 3 starts using the Alternative slice for all or some Applications as per the Network Slice Selection policy and this way the S-NSSAI for which the S-NSSAI energy credit had dropped to or below the S-NSSAI energy credit threshold would be used less leading to energy consumption saving for that S-NSSAI.

[0225] For example, the UE 3 may consider (determine) Alternative S-NSSAI (S-NSSAI-2) replaced with the S-NSSAI (S-NSSAI-1) based on the information for network slice selection.

[0226] For example, the UE 3 may select and use Alternative S-NSSAI (S-NSSAI-2) replaced with the S-NSSAI (S-NSSAI-1) based on the information for network slice selection.

[0227] For example, when the S-NSSAI energy credit of the S-NSSAI (S-NSSAI-1) is Low, then the UE 3 may select and use Alternative S-NSSAI (S-NSSAI-2) replaced with the S-NSSAI (S-NSSAI-1) based on the information for network slice selection.

[0228] In the Third Example of the Second Aspect, the UE 3 may receive, from a core network node, information for network slice selection in a case where an energy credit for first Single - Network Slice Selection Assistance Information (S-NSSAI) is Low. The UE 3 may select second S-NSSAI based on the information. A core network node may replace first information about first Single - Network Slice Selection Assistance Information (S-NSSAI) to second information about second S-NSSAI, in a case where an energy credit for the first S-NSSAI is Low. the first S-NSSAI and the second S-NSSAI may be available for the UE. The core network node may send, to a second core network node, third information for network slice selection.

[0229] <Fourth Example of the Second Aspect> 　　The Fourth Example of the Second Aspect in Fig. 8 includes a mechanism where a network slice may be allocated with 'S-NSSAI energy credit' and with 'S-NSSAI energy credit threshold' as part of its subscription information. When the S-NSSAI energy credit for certain S-NSSAI drops to or below the S-NSSAI energy credit threshold, the UDR notifies the AMF. The AMF stores the S-NSSAI(s) (or ID of the S-NSSAI(s)) for which the S-NSSAI energy credit is reported to be Low. When the UE initiates a service, e.g. PDU Session Establishment Request on such S-NSSAI, the AMF may trigger the network slice replacement procedure, i.e. replaces the S-NSSAI with low S-NSSAI energy credit with an Alternative S-NSSAI as per the network slice replacement procedure in 3GPP TS 23.502 [3].

[0230] The detailed process of the Fourth Example of the Second Aspect is described below with reference to Fig. 8.

[0231] Step1. A network slice may be allocated with 'S-NSSAI energy credit' and with 'S-NSSAI energy credit threshold' as part of its subscription information. When the S-NSSAI energy credit for certain S-NSSAI drops below the S-NSSAI energy credit threshold for that S-NSSAI, the UDR 80 notifies the PCF 73. - S-NSSAI energy credit - the S-NSSAI energy credit is the amount of energy the S-NSSAI is allocated for consumption from the network for specific time defined by the network operator. The amount of S-NSSAI energy credit may be expressed in energy units or energy credits, watt, Joule, bit / Joule or in any other expression for energy consumption by the S-NSSAI from the network in order to indicate the level of the remaining energy for consumption for that S-NSSAI. The S-NSSAI energy credit may be subject to SLA or network operation policy. The S-NSSAI energy credit may be an indication or information indicating an amount of energy that is available for the S-NSSAI. The S-NSSAI energy credit may be an indication or information indicating a total amount of energy that is available for using the network service corresponding to the S-NSSAI. The S-NSSAI energy credit may be an indication or information indicating a remaining amount of energy that is available for using the network service corresponding to the S-NSSAI. - S-NSSAI energy credit threshold - the S-NSSAI energy credit threshold is the amount of energy where after the S-NSSAI energy credit consumption exceeds the S-NSSAI energy credit threshold, e.g. the remaining available S-NSSAI energy credit drops below the S-NSSAI energy credit threshold, the S-NSSAI is considered to have a Low energy and the S-NSSAI may be subject to service restrictions depending on the operator energy credit policies and configurations. The S-NSSAI energy credit threshold may also be expressed in energy units or energy credits, watt, Joule, bit / Joule or in any other expression for energy consumption by the S-NSSAI from the network, comparable with the S-NSSAI energy credit, in order to indicate the level of the consumed energy or the level of the remaining energy per S-NSSAI. The S-NSSAI energy credit threshold may be a value. The S-NSSAI energy credit threshold may be an indication or information indicating threshold to determine (consider) that a lower energy is remained to use the S-NSSAI. For example, it may be determined (or considered) to be restricted a service corresponding to the S-NSSAI used by the UE 3 when the remained energy for the S-NSSAI drops (or exceeds) the S-NSSAI energy credit threshold. The S-NSSAI energy credit threshold may be prepared for each of S-NSSAIs. The S-NSSAI energy credit threshold may be a same value for every S-NSSAI.

[0232] The UDR 80 monitors and regularly compare the remaining S-NSSAI energy credit for the S-NSSAI and when the S-NSSAI energy credit for certain S-NSSAI drops below the S-NSSAI energy credit threshold for that S-NSSAI, the UDR 80 notifies the AMF 70. For example, when the UDR 80 determines that the S-NSSAI energy credit drops to or below the S-NSSAI energy credit threshold for the S-NSSAI, the UDR 80 notifies the AMF 70. For example, when the UDR 80 determines that the S-NSSAI energy credit drops to or below the S-NSSAI energy credit threshold for the S-NSSAI, then the UDR 80 may send, to the AMF 70, information indicating that the S-NSSAI energy credit is Low.

[0233] Step 2. The UDR 80 sends to the AMF 70 the Namf_DM_Notify message in which the UDR 80 includes one or more S-NSSAI ID(s) for which the S-NSSAI energy credit has dropped to or below the S-NSSAI energy credit threshold and the S-NSSAI energy credit threshold parameter set to Low.

[0234] Step 3. The AMF 70 stores the S-NSSAI(s) for which the S-NSSAI energy credit is reported to be Low. For example, the AMF 70 may receive, from the UDR 80, the ID(s) of the S-NSSAI(s) which is considered that the S-NSSAI energy credit is Low and the information indicating that the S-NSSAI energy credit of the S-NSSAI (e.g., S-NSSAI 1) is Low.

[0235] Step 4. The AMF 70 may also pass the S-NSSAI(s) for which the S-NSSAI energy credit is Low along with the S-NSSAI energy credit parameter set to Low to RAN 5. The RAN 5 may deploy energy saving features available in RAN 5 for these S-NSSAI(s) with S-NSSAI energy credit set to Low. For example, the RAN 5 may receive, from the AMF 70, the ID(s) of the S-NSSAI(s) (e.g., S-NSSAI 1) which is considered that the S-NSSAI energy credit is Low and the information indicating that the S-NSSAI energy credit of the S-NSSAI (e.g., S-NSSAI 1) is Low.

[0236] Step 5. At some point the UE 3 initiates PDU Session Establishment procedure and sends the PDU Session Establishment Request message in which the UE 3 includes the S-NSSAI based on the Network Slice selection policy within the URSP rules for UE 3. For example, the UE 3 may send, to the AMF 70, the PDU Session Establishment Request message including information about a S-NSSAI (e.g., S-NSSAI 1).

[0237] Step 6. When the UE 3 triggers the PDU Session Establishment Request, the AMF 70 checks whether the S-NSSAI on which the UE 3 requires service (i.e. the S-NSSAI included in the PDU Session Establishment Request message) is one of the S-NSSAIs with S-NSSAI energy credit set to Low. If the S-NSSAI included in the PDU Session Establishment Request message matches one of the S-S-NSSAI with S-NSSAI energy credit set to Low stored in the AMF 70, the AMF 70 triggers the network slice replacement procedure as per 3GPP TS 23.502 [3] and the PDU Session Establishment procedure continues on the Alternative S-NSSAI instead of on the initially requested by the UE 3 S-NSSAI in the PDU Session Request message for which the S-NSSAI energy credit is set to Low. This allows to achieve energy saving on the S-NSSAI for which the S-NSSAI energy credit is set to Low.

[0238] For example, when the AMF receives the PDU Session Establishment Request message, the AMF 70 may consider (determine) whether the energy credit of the S-NSSAI (e.g., S-NSSAI 1) regarding to the information about the S-NSSAI is set to Low. When the energy credit of the S-NSSAI 1 is set to Low, then the AMF 70 and the UE 3 may perform the PDU Session Establishment procedure for alternative S-NSSAI (e.g., S-NSSAI 2, not S-NSSAI 1).

[0239] In the Fourth Example of the First Aspect, the UE 3 may receive, from a first core network node, first information about first Single - Network Slice Selection Assistance Information (S-NSSAI) and second information about an energy credit for the first S-NSSAI. The UE 3 may perform Protocol Data Unit (PDU) session establishment procedure related to second S-NSSAI, in a case where the second information indicates that an energy credit for the first S-NSSAI is Low.

[0240] <Fifth Example of the Second Aspect> 　　In Figs. 5-8, the names of network nodes (e.g., AMF, SMF, PCF, UDM, UDR, NEF, RAN, etc..) are described using the nomenclature of the 5G system. However, this Second Aspect is also applicable to systems other than 5G (such as 6G system and 7G system). In such cases, the network nodes in these Figures can be interpreted as 'core network nodes' or 'network nodes'. In other words, this First Aspect can be applied to systems other than 5G systems (such as 6G system and 7G system etc.) by replacing the names of nodes in the 5G system with "core network nodes" or "network nodes", etc.

[0241] <<System overview>> 　　Fig. 9 schematically illustrates a telecommunication system 1 for a mobile (cellular or wireless) to which the above aspects are applicable.

[0242] 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.

[0243] 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).

[0244] 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.

[0245] 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'.

[0246] 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.

[0247] 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).

[0248] 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).

[0249] 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).

[0250] 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).

[0251] 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.

[0252] 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 Authentication Server Function (AUSF) 76 and an AKMA Anchor Function (AAnF) 77. 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 AAnF 77 for the roaming-out UE 3.

[0253] The OAM 8 includes, amongst others, Operational functions, Administrational functions and Maintenance related functions. The OAM 8 has interfaces with RAN 5, logical nodes in the core network 7 in a PLMN. In addition, the OAM 8 has interfaces to the AF 201 and other entities that are located in the data network 20.

[0254] 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 AAnF 77 for the roaming-out UE 3.

[0255] 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.

[0256] The "Uu" interface may include a Control plane of Uu interface and User plane of Uu interface.

[0257] 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).

[0258] 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.

[0259] For example, the following messages are communicated over the RRC layer to support AS signaling. - 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.

[0260] 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. - 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. - 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. - 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. - 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. - 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.

[0261] <User equipment (UE)> 　　Fig. 10 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.

[0262] 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).

[0263] 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.).

[0264] 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.).

[0265] 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.).

[0266] 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.).

[0267] 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.).

[0268] 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.

[0269] 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)).

[0270] 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.

[0271] 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.

[0272] 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.

[0273] 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.

[0274] 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).

[0275] 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).

[0276] <(R)AN node> 　　Fig. 11 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.

[0277] 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.

[0278] Such signalling may also include, for example, broadcast information (e.g. Master Information and System information) in a sending case.

[0279] 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.

[0280] 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).

[0281] The (R)AN node 5 may be expressed as a RAN node, RAN, (R)AN etc.

[0282] <AMF> 　　Fig. 12 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) 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).

[0283] 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).

[0284] <SMF> 　　Fig. 13 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 (e.g., the Network Relay UE 300 and 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).

[0285] 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).

[0286] <UPF> 　　Fig. 14 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 (e.g., the Network Relay UE 300 and 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).

[0287] 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).

[0288] <PCF> 　　Fig. 15 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 (e.g., the Network Relay UE 300 and 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).

[0289] 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).

[0290] <NWDAF> 　　Fig. 16 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).

[0291] 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).

[0292] <UDM> 　　Fig. 17 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 (e.g., the Network Relay UE 300 and 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).

[0293] 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).

[0294] <AUSF> 　　Fig. 18 is a block diagram illustrating the main components of the AUSF 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 AUSF 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 AUSF 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).

[0295] The AUSF 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).

[0296] <AAnF> 　　Fig. 19 is a block diagram illustrating the main components of the AAnF 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 AAnF 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 AAnF 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).

[0297] The AAnF 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).

[0298] <NRF> 　　Fig. 20 is a block diagram illustrating the main components of the NRF 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 NRF 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 NRF 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).

[0299] The NRF 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).

[0300] <NEF> 　　Fig. 21 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).

[0301] 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).

[0302] <UDR> 　　Fig. 22 is a block diagram illustrating the main components of the UDR 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 UDR 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 UDR 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).

[0303] The UDR 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).

[0304] <OAM> 　　Fig. 23 is a block diagram illustrating the main components of the OAM 8. As shown, the apparatus includes a transceiver circuit 811 which is operable to transmit signals to and to receive signals from other nodes via a network interface 8012. A controller 813 controls the operation of the OAM 8 in accordance with software stored in a memory 814. Software may be pre-installed in the memory 814 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 8141 and a communications control module 8142 having at least a transceiver control module 81421. The communications control module 8142 (using its transceiver control module 81421 is responsible for handling (generating / sending / receiving) signalling between the OAM 8 and other nodes. 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).

[0305] The OAM 8 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).

[0306] <AF> 　　Fig. 24 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 (e.g., the Network Relay UE 300 and 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).

[0307] 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).

[0308] <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.

[0309] 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.

[0310] 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.

[0311] 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.

[0312] 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.

[0313] 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.

[0314] Various other modifications will be apparent to those skilled in the art and will not be described in further detail here.

[0315] 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.

[0316] 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.

[0317] 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.

[0318] 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.

[0319] 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). <Supplementary notes> <Supplementary note (A)> 　　(Supplementary note 1) 　　A method performed by a User Equipment (UE) comprising: 　　sending, to a core network node, a registration request message; and 　　receiving, from the core network node, a registration accept message including first information about a battery threshold for a Quality of Service (QoS) adjustment for the UE. 　　(Supplementary note 2) 　　The method according to Supplementary note 1, 　　wherein the UE receives registration accept message including first information, in a case where the QoS adjustment is active for the UE. 　　(Supplementary note 3) 　　The method according to Supplementary note 1, 　　wherein the registration accept message includes second information indicating that the QoS adjustment is active for the UE. 　　(Supplementary note 4) 　　The method according to Supplementary note 1, 　　wherein registration request message includes third information about capability for reporting a battery status or for reporting a battery charge level of the UE. 　　(Supplementary note 5) 　　The method according to Supplementary note 1, 　　wherein registration request message includes fourth information about a battery status of the UE. 　　(Supplementary note 6) 　　A User Equipment (UE) comprising: 　　sending, to a core network node, a registration request message; and 　　receiving, from the core network node, a registration accept message including first information about a battery threshold for a Quality of Service (QoS) adjustment for the UE. 　　(Supplementary note 7) 　　The UE according to Supplementary note 6, 　　wherein the UE receives registration accept message including first information, in a case where the QoS adjustment is active for the UE. 　　(Supplementary note 8) 　　The UE according to Supplementary note 6, 　　wherein the registration accept message includes second information indicating that the QoS adjustment is active for the UE. 　　(Supplementary note 9) 　　The UE according to Supplementary note 6, 　　wherein registration request message includes third information about capability for reporting a battery status or for reporting a battery charge level of the UE. 　　(Supplementary note 10) 　　The UE according to Supplementary note 6, 　　wherein registration request message includes fourth information about a battery status of the UE. 　　(Supplementary note 11) 　　A method performed by a core network node comprising: 　　receiving, from a User Equipment (UE), a registration request message; and 　　sending, to the UE, a registration accept message including first information about a battery threshold for a Quality of Service (QoS) adjustment for the UE. 　　(Supplementary note 12) 　　The method according to Supplementary note 11, 　　wherein the core network node sends the registration accept message including first information, in a case where the QoS adjustment is active for the UE. 　　(Supplementary note 13) 　　The method according to Supplementary note 11, 　　wherein the registration accept message includes second information indicating that the QoS adjustment is active for the UE. 　　(Supplementary note 14) 　　The method according to Supplementary note 11, 　　wherein registration request message includes third information about capability for reporting a battery status or for reporting a battery charge level of the UE. 　　(Supplementary note 15) 　　The method according to Supplementary note 11, 　　wherein registration request message includes fourth information about a battery status of the UE. 　　(Supplementary note 16) 　　A core network node comprising: 　　receiving, from a User Equipment (UE), a registration request message; and 　　sending, to the UE, a registration accept message including first information about a battery threshold for a Quality of Service (QoS) adjustment for the UE. 　　(Supplementary note 17) 　　The core network node according to Supplementary note 16, 　　wherein core network node sends the registration accept message including first information, in a case where the QoS adjustment is active for the UE. 　　(Supplementary note 18) 　　The core network node according to Supplementary note 16, 　　wherein the registration accept message includes second information indicating that the QoS adjustment is active for the UE. 　　(Supplementary note 19) 　　The core network node according to Supplementary note 16, 　　wherein registration request message includes third information about capability for reporting a battery status or for reporting a battery charge level of the UE. 　　(Supplementary note 20) 　　The core network node according to Supplementary note 16, 　　wherein registration request message includes fourth information about a battery status of the UE. 　　(Supplementary note 21) 　　A method performed by a first core network node comprising: 　　receiving first information about a battery threshold for a Quality of Service (QoS) adjustment for a User Equipment (UE); 　　receiving second information about the battery status of the UE; and 　　determining, based on the first information and the second information, to request, to a second core network node, for updating the QoS adjustment for the UE. 　　(Supplementary note 22) 　　A first core network node comprising: 　　receiving first information about a battery threshold for a Quality of Service (QoS) adjustment for a User Equipment (UE); 　　receiving second information about the battery status of the UE; and 　　determining, based on the first information and the second information, to request, to a second core network node, for updating the QoS adjustment for the UE. <Supplementary note (B)> 　　(Supplementary note 1) 　　A method performed by a User Equipment (UE) comprising: 　　sending, to a core network node, a registration request message including information indicating that the UE supports an energy credit policy control; and 　　receiving, from the core network node, a registration accept message including a first information indicating that the amount of energy or the remaining energy being available for the UE and a second information for determining that the UE is in a Low energy state. 　　(Supplementary note 2) 　　A User Equipment (UE) comprising: 　　means for sending, to a core network node, a registration request message including information indicating that the UE supports an energy credit policy control; and 　　means for receiving, from the core network node, a registration accept message including a first information indicating that the amount of energy or the remaining energy being available for the UE and a second information for determining that the UE is in a Low energy state. 　　(Supplementary note 3) 　　A method performed by a core network node comprising: 　　receiving, from a User Equipment (UE), a registration request message including information indicating that the UE supports an energy credit policy control; and 　　sending, to the UE, a registration accept message including a first information indicating that the amount of energy or the remaining energy being available for the UE and a second information for determining that the UE is in a Low energy state. 　　(Supplementary note 4) 　　A core network node comprising: 　　means for receiving, from a User Equipment (UE), a registration request message including information indicating that the UE supports an energy credit policy control; and 　　means for, to the UE, a registration accept message including a first information indicating that the amount of energy or the remaining energy being available for the UE and a second information for determining that the UE is in a Low energy state. 　　(Supplementary note 5) 　　A method performed by a User Equipment (UE) comprising: 　　receiving, from a first core network node, first information indicating a behavior of the UE when the energy state of the UE is Low; and 　　sending, to the first core network node, second information indicating that the energy efficiency preference of the at least one service for the UE. 　　(Supplementary note 6) 　　A User Equipment (UE) comprising: 　　means for receiving, from a first core network node, first information indicating a behavior of the UE when the energy state of the UE is Low; and 　　means for sending, to the first core network node, second information indicating that the energy efficiency preference of the at least one service for the UE. 　　(Supplementary note 7) 　　A method performed by a first core network node comprising: 　　receiving, from a second core network node, first information indicating that an energy state of a User Equipment (UE) is Low; and 　　sending, to a third core network node, second information indicating a behavior of the UE when the energy state of the UE is Low. 　　(Supplementary note 8) 　　A first core network node comprising: 　　means for receiving, from a second core network node, information indicating that an energy state of a User Equipment (UE) is Low; 　　means for sending, to a third core network node, information indicating that the energy state of the UE energy is Low. 　　(Supplementary note 9) 　　A method performed by a User Equipment (UE) comprising: 　　receiving, from a core network node, information for network slice selection in a case where an energy credit for first Single - Network Slice Selection Assistance Information (S-NSSAI) is Low; and 　　selecting second S-NSSAI based on the information. 　　(Supplementary note 10) 　　A User Equipment (UE) comprising: 　　means for receiving, from a core network node, information for network slice selection in a case where an energy credit for first Single - Network Slice Selection Assistance Information (S-NSSAI) is Low; and 　　means for selecting second S-NSSAI based on the information. 　　(Supplementary note 11) 　　A method performed by a core network node comprising: 　　means for replacing first information about first Single - Network Slice Selection Assistance Information (S-NSSAI) to second information about second S-NSSAI, in a case where an energy credit for the first S-NSSAI is Low, 　　wherein the first S-NSSAI and the second S-NSSAI is available for the UE; and 　　means for sending, to a second core network node, third information for network slice selection. 　　(Supplementary note 12) 　　A core network node comprising: 　　replacing first information about first Single - Network Slice Selection Assistance Information (S-NSSAI) to second information about second S-NSSAI, in a case where an energy credit for the first S-NSSAI is Low, 　　wherein the first S-NSSAI and the second S-NSSAI is available for the UE; and 　　sending, to a second core network node, third information for network slice selection. 　　(Supplementary note 13) 　　A method performed by a User Equipment (UE) comprising: 　　receiving, from a first core network node, first information about first Single - Network Slice Selection Assistance Information (S-NSSAI) and second information about an energy credit for the first S-NSSAI; and 　　performing Protocol Data Unit (PDU) session establishment procedure related to second S-NSSAI, in a case where the second information indicates that an energy credit for the first S-NSSAI is Low. 　　(Supplementary note 14) 　　A User Equipment (UE) comprising: 　　means for receiving, from a first core network node, first information about first Single - Network Slice Selection Assistance Information (S-NSSAI) and second information about an energy credit for the first S-NSSAI; and 　　means for performing Protocol Data Unit (PDU) session establishment procedure related to second S-NSSAI, in a case where the second information indicates that an energy credit for the first S-NSSAI is Low. 　　(Supplementary note 15) 　　A method performed by a core network node comprising: 　　sending, to a User Equipment (UE), first information about first Single - Network Slice Selection Assistance Information (S-NSSAI) and second information about an energy credit for the first S-NSSAI; and 　　performing Protocol Data Unit (PDU) session establishment procedure related to second S-NSSAI, in a case where the second information indicates that an energy credit for the first S-NSSAI is Low. 　　(Supplementary note 16) 　　A core network node comprising: 　　means for sending, to a User Equipment (UE), first information about first Single - Network Slice Selection Assistance Information (S-NSSAI) and second information about an energy credit for the first S-NSSAI; and 　　means for performing Protocol Data Unit (PDU) session establishment procedure related to second S-NSSAI, in a case where the second information indicates that an energy credit for the first S-NSSAI is Low.

[0320] This application is based upon and claims the benefit of priority from Indian Patent Application No. 202511014402, filed on February 19, 2025, the disclosure of which is incorporated herein in its entirety by reference.

[0321] 3　　USER EQUIPMENT(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　　RADIO ACCESS NETWORK (RAN) 51　　TRANSCEIVER CIRCUIT 52　　ANTENNA 53　　NETWORK INTERFACE 54　　CONTROLLER 55　　MEMORY 551　　OPERATING SYSTEM 552　　COMMUNICATIONS CONTROL MODULE 5521　　TRANSCEIVER CONTROL MODULE 7　　CORE NETWORK 70　　AMF 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 751　　TRANSCEIVER CIRCUIT 752　　NETWORK INTERFACE 753　　CONTROLLER 754　　MEMORY 7541　　OPERATING SYSTEM 7542　　COMMUNICATIONS CONTROL MODULE 75421　　TRANSCEIVER CONTROL MODULE 76　　AUSF 761　　TRANSCEIVER CIRCUIT 762　　NETWORK INTERFACE 763　　CONTROLLER 764　　MEMORY 7641　　OPERATING SYSTEM 7642　　COMMUNICATIONS CONTROL MODULE 76421　　TRANSCEIVER CONTROL MODULE 77　　AAnF 771　　TRANSCEIVER CIRCUIT 772　　NETWORK INTERFACE 773　　CONTROLLER 774　　MEMORY 7741　　OPERATING SYSTEM 7742　　COMMUNICATIONS CONTROL MODULE 77421　　TRANSCEIVER CONTROL MODULE 78　　NRF 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　　UDR 801　　TRANSCEIVER CIRCUIT 802　　NETWORK INTERFACE 803　　CONTROLLER 804　　MEMORY 8041　　OPERATING SYSTEM 8042　　COMMUNICATIONS CONTROL MODULE 80421　　TRANSCEIVER CONTROL MODULE 8　　OAM 811　　TRANSCEIVER CIRCUIT 812　　NETWORK INTERFACE 813　　CONTROLLER 814　　MEMORY 8141　　OPERATING SYSTEM 8142　　COMMUNICATIONS CONTROL MODULE 81421　　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 performed by a User Equipment (UE) comprising: 　　sending, to a core network node, a registration request message; and 　　receiving, from the core network node, a registration accept message including first information about a battery threshold for a Quality of Service (QoS) adjustment for the UE.

2. The method according to claim 1, 　　wherein the UE receives registration accept message including first information, in a case where the QoS adjustment is active for the UE.

3. The method according to claim 1, 　　wherein the registration accept message includes second information indicating that the QoS adjustment is active for the UE.

4. The method according to claim 1, 　　wherein the registration request message includes third information about capability for reporting a battery status or for reporting a battery charge level of the UE.

5. The method according to claim 1, 　　wherein the registration request message includes fourth information about a battery status of the UE.

6. A User Equipment (UE) comprising: 　　sending, to a core network node, a registration request message; and 　　receiving, from the core network node, a registration accept message including first information about a battery threshold for a Quality of Service (QoS) adjustment for the UE.

7. The UE according to claim 6, 　　wherein the UE receives registration accept message including first information, in a case where the QoS adjustment is active for the UE.

8. The UE according to claim 6, 　　wherein the registration accept message includes second information indicating that the QoS adjustment is active for the UE.

9. The UE according to claim 6, 　　wherein the registration request message includes third information about capability for reporting a battery status or for reporting a battery charge level of the UE.

10. The UE according to claim 6, 　　wherein the registration request message includes fourth information about a battery status of the UE.

11. A method performed by a core network node comprising: 　　receiving, from a User Equipment (UE), a registration request message; and 　　sending, to the UE, a registration accept message including first information about a battery threshold for a Quality of Service (QoS) adjustment for the UE.

12. The method according to claim 11, 　　wherein the core network node sends the registration accept message including first information, in a case where the QoS adjustment is active for the UE.

13. The method according to claim 11, 　　wherein the registration accept message includes second information indicating that the QoS adjustment is active for the UE.

14. The method according to claim 11, 　　wherein the registration request message includes third information about capability for reporting a battery status or for reporting a battery charge level of the UE.

15. The method according to claim 11, 　　wherein the registration request message includes fourth information about a battery status of the UE.

16. A core network node comprising: 　　receiving, from a User Equipment (UE), a registration request message; and 　　sending, to the UE, a registration accept message including first information about a battery threshold for a Quality of Service (QoS) adjustment for the UE.

17. The core network node according to claim 16, 　　wherein the core network node sends the registration accept message including first information, in a case where the QoS adjustment is active for the UE.

18. The core network node according to claim 16, 　　wherein the registration accept message includes second information indicating that the QoS adjustment is active for the UE.

19. The core network node according to claim 16, 　　wherein the registration request message includes third information about capability for reporting a battery status or for reporting a battery charge level of the UE.

20. The core network node according to claim 16, 　　wherein the registration request message includes fourth information about a battery status of the UE.

21. A method performed by a first core network node comprising: 　　receiving first information about a battery threshold for a Quality of Service (QoS) adjustment for a User Equipment (UE); 　　receiving second information about the battery status of the UE; and 　　determining, based on the first information and the second information, to request, to a second core network node, for updating the QoS adjustment for the UE.

22. A first core network node comprising: 　　receiving first information about a battery threshold for a Quality of Service (QoS) adjustment for a User Equipment (UE); 　　receiving second information about the battery status of the UE; and 　　determining, based on the first information and the second information, to request, to a second core network node, for updating the QoS adjustment for the UE.

Images