Method and apparatus for supporting energy consumption information in wireless communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting higher data transmission rates. An operating method of a consumer network function (NF) in a wireless communication system, according to an embodiment of the present disclosure, may comprise the steps of: transmitting, to a network repository function (NRF), an NF discovery request message including a user equipment (UE) ID, single network slice selection assistance information (S-NSSAI), a locality, or a service area; receiving, from the NRF, an NF discovery response message including an energy influence function (EIF) profile; and selecting, on the basis of the NF discovery response message, an EIF corresponding to the EIF profile.

Description

Method and device for supporting energy consumption information in a wireless communication system

[0001] The present disclosure relates to a method and apparatus for supporting energy consumption information in a wireless communication system.

[0002] 5G mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, and can be implemented not only in frequency bands below 6 GHz ('Sub 6 GHz'), such as 3.5 gigahertz (3.5 GHz), but also in ultra-high frequency bands called millimeter waves (mmWave), such as 28 GHz and 39 GHz ('Above 6 GHz'). In addition, for 6G mobile communication technology, which is referred to as a system beyond 5G, implementation in the terahertz band (e.g., the 3 terahertz (3 THz) band at 95 GHz) is being considered to achieve transmission speeds 50 times faster and ultra-low latency reduced to one-tenth compared to 5G mobile communication technology.

[0003] In the early stages of 5G mobile communication technology, aiming to satisfy service support and performance requirements for enhanced Mobile BroadBand (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and massive Machine-Type Communications (mMTC), technologies such as beamforming and Massive MIMO to mitigate path loss and increase transmission distance in ultra-high frequency bands, support for various numerologies (such as the operation of multiple subcarrier spacings) and dynamic operation of slot formats for the efficient utilization of ultra-high frequency resources, initial access techniques to support multi-beam transmission and broadband, definition and operation of Band-Width Parts (BWP), Low Density Parity Check (LDPC) codes for high-volume data transmission, new channel coding methods such as Polar Codes for the reliable transmission of control information, and L2 pre-processing (L2 Standardization has been carried out for pre-processing, network slicing which provides a dedicated network specialized for specific services, and other methods.

[0004] Currently, discussions are underway to improve and enhance the performance of the initial 5G mobile communication technology, taking into account the services that the 5G mobile communication technology was intended to support. Additionally, standardization of the physical layer is in progress for technologies such as V2X (Vehicle-to-Everything), which helps autonomous vehicles make driving decisions and enhance user convenience based on their own location and status information transmitted by the vehicle; NR-U (New Radio Unlicensed), which aims for system operation in unlicensed bands to comply with various regulatory requirements; NR terminal low power consumption technology (UE Power Saving); Non-Terrestrial Network (NTN), which is direct terminal-satellite communication for securing coverage in areas where communication with the terrestrial network is impossible; and positioning.

[0005] In addition, standardization is underway in the field of wireless interface architecture / protocols for technologies such as the Industrial Internet of Things (IIoT) for supporting new services through linkage and convergence with other industries, Integrated Access and Backhaul (IAB) which provides nodes for expanding network service areas by integrating wireless backhaul links and access links, Mobility Enhancement including Conditional Handover and Dual Active Protocol Stack (DAPS) Handover, and 2-step Random Access (2-step RACH for NR) which simplifies random access procedures. Standardization is also underway in the field of system architecture / services for 5G baseline architectures (e.g., Service based Architecture, Service based Interface) for incorporating Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC), which provides services based on the location of the terminal.

[0006] When such 5G mobile communication systems are commercialized, connected devices, which are increasing explosively, will be connected to communication networks. Accordingly, it is expected that there will be a need to enhance the functionality and performance of 5G mobile communication systems and to integrate the operation of connected devices. To this end, new research is planned to be conducted on 5G performance improvement and complexity reduction, support for AI services, support for metaverse services, and drone communication using eXtended Reality (XR), Artificial Intelligence (AI), and Machine Learning (ML) to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR).

[0007] Furthermore, the advancement of these 5G mobile communication systems encompasses multi-antenna transmission technologies such as new waveforms to guarantee coverage in the terahertz band of 6G mobile communication technology, Full Dimensional MIMO (FD-MIMO), array antennas, and large-scale antennas; metamaterial-based lenses and antennas to improve terahertz band signal coverage; high-dimensional spatial multiplexing technology using OAM (Orbital Angular Momentum); and Reconfigurable Intelligent Surface (RIS) technology; as well as Full Duplex technology for enhancing frequency efficiency and system networks in 6G mobile communication technology; AI-based communication technologies that realize system optimization by utilizing satellites and AI from the design stage and internalizing end-to-end AI support functions; and the realization of services of complexity exceeding the limits of terminal computing capabilities by utilizing ultra-high-performance communication and computing resources. It could serve as a foundation for the development of next-generation distributed computing technologies.

[0008] The present invention proposes a method for discovering energy information functions in a 5G system.

[0009] A method of operation of a consumer network function (NF) in a wireless communication system according to one embodiment of the present disclosure may include: transmitting an NF discovery request message to an energy influence function (NRF) that includes a user equipment (UE) ID, single network slice selection assistance information (S-NSSAI), locality, or service area; receiving an NF discovery response message from the NRF that includes an energy influence function (EIF) profile; and selecting an EIF corresponding to the EIF profile based on the NF discovery response message.

[0010] According to one embodiment, the consumer NF may be a PCF (policy control function) or an AF (application function).

[0011] According to one embodiment, the EIF profile may include the address of the EIF and the ID of the EIF.

[0012] According to one embodiment, the method of operation of the consumer NF may further include the step of transmitting a subscription request message for an energy consumption event of the UE to the selected EIF. The subscription request message may include at least one of an event ID, a UE ID, an S-NSSAI, an IP filter, a reporting frequency, or area information.

[0013] According to one embodiment, the method of operation of the consumer NF may further include the step of receiving a response message for the subscription request message from the EIF. The response message may include result information indicating success if the subscription request is successful, and the response message may include result information indicating failure and cause information if the subscription request fails.

[0014] A method of operation of an energy influence function (EIF) in a wireless communication system according to one embodiment of the present disclosure may include: receiving a subscription request message for an energy consumption event of a user equipment (UE) from a consumer network function (NF); and transmitting a response message for the subscription request message to the consumer NF. The EIF may be selected by the consumer NF based on an EIF profile included in an NF discovery response message.

[0015] In a wireless communication system according to one embodiment of the present disclosure, a consumer network function (NF) may include a transceiver; and a control unit. The control unit controls the transmission of an NF discovery request message to an energy influence function (NRF) that includes a user equipment (UE) ID, single network slice selection assistance information (S-NSSAI), locality, or service area, receives an NF discovery response message from the NRF that includes an energy influence function (EIF) profile, and selects an EIF corresponding to the EIF profile based on the NF discovery response message.

[0016] In a wireless communication system according to one embodiment of the present disclosure, an energy influence function (EIF) may include a transceiver; and a control unit. The control unit may receive a subscription request message regarding an energy consumption event of user equipment (UE) from a consumer network function (NF) and control the transmission of a response message to the subscription request message to the consumer NF. The EIF may be selected by the consumer NF based on an EIF profile included in an NF discovery response message.

[0017] In the method and apparatus according to the embodiment of the present disclosure, a network operator can improve the load balancing effect and the reliability of the energy information provision function by introducing a plurality of Energy Information Functions (EIFs) (for example, introducing an EIF responsible for a specific region for each region, or introducing an EIF responsible for one or more network slices).

[0018] FIG. 1 shows a 5G system architecture according to an embodiment of the present disclosure.

[0019] FIG. 2 illustrates an EIF registration and discovery method through NRF according to an embodiment of the present disclosure.

[0020] FIG. 3 illustrates a procedure for collecting and exposing energy consumption information (ECI), including a process of discovering EIF through NRF according to an embodiment of the present disclosure.

[0021] FIG. 4 illustrates the EIF registration and discovery procedure through UDM according to an embodiment of the present disclosure.

[0022] FIG. 5 illustrates an EIF reselection procedure according to an embodiment of the present disclosure.

[0023] FIGS. 6a and 6b illustrate a context transfer procedure of an EIF according to an embodiment of the present disclosure.

[0024] FIG. 7 is a block diagram showing the structure of a terminal according to an embodiment of the present disclosure.

[0025] FIG. 8 is a block diagram showing the structure of a network entity according to an embodiment of the present disclosure.

[0026] Embodiments of the present invention will be described in detail below with reference to the accompanying drawings. Furthermore, in describing the present invention, detailed descriptions of related known functions or configurations are omitted if it is determined that such detailed descriptions would unnecessarily obscure the essence of the present invention. Additionally, terms described below are defined in consideration of their functions in the present invention, and these may vary depending on the intentions or conventions of the user or operator. Therefore, such definitions should be based on the content throughout this specification. For the same reason, some components in the accompanying drawings may be exaggerated, omitted, or schematically depicted. Furthermore, the size of each component does not entirely reflect its actual size. Identical or corresponding components in each drawing are assigned the same reference number. The advantages and features of the technical concept according to the present disclosure, and the methods for achieving them, will become clear by referring to the embodiments described in detail below with reference to the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below but may be implemented in various different forms; these embodiments are provided merely to ensure that the present disclosure is complete and to fully inform those skilled in the art of the scope of the invention, and the present disclosure is defined only by the scope of the claims. Throughout the specification, the same reference numerals refer to the same components. Furthermore, in describing the present disclosure, detailed descriptions of related functions or configurations are omitted if it is determined that such detailed descriptions would unnecessarily obscure the essence of the technical concept according to the present disclosure. Additionally, terms described below are defined considering their functions in the present disclosure, and these may vary depending on the intentions or practices of the user or operator. Therefore, their definitions should be based on the content throughout the specification.

[0027] Hereinafter, the base station is an entity that performs resource allocation for terminals and may be at least one of an eNode B, Node B, BS (Base Station), RAN (Radio Access Network), AN (Access Network), RAN node, wireless access unit, base station controller, or a node on a network. The terminal may include a UE (User Equipment), MS (Mobile Station), cellular phone, smartphone, computer, or a multimedia system capable of performing communication functions. In the present invention, the downlink (DL) refers to the wireless transmission path of a signal transmitted by the base station to the terminal, and the uplink (UL) refers to the wireless transmission path of a signal transmitted by the terminal to the base station. Furthermore, although the embodiments of the present disclosure are described below using an LTE or LTE-A system as an example, the embodiments of the present disclosure may be applied to other communication systems having similar technical backgrounds or channel types. For example, 5th generation mobile communication technology (5G, new radio, NR) developed after LTE-A may be included in a system to which the embodiments of the present disclosure can be applied, and the 5G below may be a concept that includes existing LTE, LTE-A, and other similar services. Furthermore, the embodiments of the present disclosure may be applied to other communication systems with some modifications made at the discretion of a person skilled in the art, without departing significantly from the scope of the present invention. In this case, it will be understood that each block of the processing flowcharts and combinations of the flowcharts may be executed by computer program instructions.

[0028] Since these computer program instructions can be loaded onto the processor of a general-purpose computer, a computer for special purposes, or other programmable data processing equipment, the instructions executed through the processor of the computer or other programmable data processing equipment create means for performing the functions described in the flowchart block(s). Since these computer program instructions can also be stored in computer-available or computer-readable memory that can be directed toward the computer or other programmable data processing equipment to implement functions in a specific way, the instructions stored in computer-available or computer-readable memory can also produce a manufactured item containing means of instruction for performing the functions described in the flowchart block(s). Since the computer program instructions can also be loaded onto the computer or other programmable data processing equipment, the instructions that perform a series of operation steps on the computer or other programmable data processing equipment to create a computer-executable process can also provide steps for performing the functions described in the flowchart block(s).

[0029] Additionally, each block may represent a module, segment, or part of code containing one or more executable instructions for executing a specified logical function(s). Also, it should be noted that in some alternative examples of execution, the functions mentioned in the blocks may occur out of order. For example, two blocks described in succession may actually be executed substantially simultaneously, or the blocks may be executed in reverse order according to the corresponding function. In this case, the term “part” as used in the embodiments of the present disclosure refers to software or hardware components such as a Field Programmable Gate Array (FPGA) or Application Specific Integrated Circuit (ASIC), and the “part” may perform certain roles. However, the “part” is not limited to software or hardware. The “part” may be configured to reside in an addressable storage medium or may be configured to run one or more processors. Accordingly, as an example, 'part' includes components such as software components, object-oriented software components, class components, and task components, as well as processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functions provided within the components and 'parts' may be combined into a smaller number of components and 'parts' or further separated into additional components and 'parts'. Furthermore, the components and 'parts' may be implemented to utilize one or more CPUs within a device or secure multimedia card. Additionally, in an embodiment, 'part' may include one or more processors.

[0030] FIG. 1 shows a 5G system architecture according to an embodiment of the present disclosure.

[0031] Referring to FIG. 1, a 5G mobile communication network consists of a 5G UE (user equipment, terminal) (100), a 5G RAN (radio access network, base station), a gNB (5G nodeB), an eNB (evolved nodeB, etc.) (110), and a 5G core network. The 5G core network includes an AMF (access and mobility management function) (120) that provides mobility management functions for the UE, a UPF (user plane function) (130) that performs data delivery roles, an SMF (session management function) (135) that provides session management functions, a PCF (policy control function) (140) that provides policy control functions, a UDM (unified data management) (145) that provides data management functions such as subscriber data and policy control data, a NSSF (network slice selection function) (160) that provides network slice selection functions, a NWDAF (network data analytics function) (165) that provides network data analysis functions, and an NSACF (network slice admission control function) (180) that provides network slice admission control functions. It consists of NFs such as an AF (application function) (170) that provides a policy linkage interface between an application (service) provider and a 5G core network, a DN (data network) (175) which is an external network where the UE (100) uses data services, and a UDR (unified data repository) that stores data of various network functions (NF: network function) such as UDM.

[0032] In 3GPP systems, a conceptual link connecting NFs within a 5G system is defined as a reference point. The following is an example of a reference point included in the 5G system architecture depicted in Figure 1.

[0033] - N1: Reference point between UE and AMF

[0034] - N2: Reference point between (R)AN and AMF

[0035] - N3: Reference point between (R)AN and UPF

[0036] - N4: Reference point between SMF and UPF

[0037] - N5: Reference point between PCF and AF

[0038] - N6: Reference point between UPF and DN

[0039] - N7: Reference point between SMF and PCF

[0040] - N8: Reference point between UDM and AMF

[0041] - N9: Reference point between 2 core UPFs

[0042] - N10: Reference point between UDM and SMF

[0043] - N11: Reference point between AMF and SMF

[0044] - N12: Reference point between AMF and AUSF

[0045] - N13: Reference point between UDM and the authentication server function (AUSF)

[0046] - N14: Reference point between 2 AMFs

[0047] - N15: Reference point between PCF and AMF in non-roaming scenarios, reference point between PCF and AMF within the visited network in roaming scenarios

[0048] In 5G systems, network slicing technology refers to a technology and structure that enables multiple virtualized, independent logical networks within a single physical network. Network operators provide services by configuring virtual end-to-end networks called network slices to satisfy the specialized requirements of services / applications. At this time, network slices are distinguished by an identifier called S-NSSAI (single-network slice selection assistance information). During a terminal registration procedure (e.g., UE registration procedure), the network transmits a set of allowed slices (e.g., allowed NSSAI(s)) to the terminal, and the terminal transmits and receives application data through a PDU (protocol data unit) session generated via one of these S-NSSAIs (i.e., network slice).

[0049] The present invention proposes a discovery method for an energy information function in a 5G system. An energy information function (or energy monitoring function) is defined to collect energy consumption information related to a UE, calculate energy consumption information at a UE, PDU session and / or Service Data Flow (or QoS Flow), NF node, base station node, etc., and expose the energy consumption information to authorized consumer NF(s) (AF / NEF or 5GC NF) according to the operator's policy.

[0050] Energy consumption information can be used by the consumer NF to control the energy consumption of the UE. The function for controlling energy consumption may be integrated into the energy influence function (EIF) or located in another NF. If the function for controlling energy consumption is integrated into the EIF, the EIF may perform energy control for the UE based on energy collection information for the UE.

[0051] FIG. 2 illustrates an EIF registration and discovery method through NRF according to an embodiment of the present disclosure.

[0052] Referring to FIG. 2, in step 201, the energy influence function (EIF) can send an NF registration request message (Nnrf_NFRegister Request) to the network repository function (NRF). The NF registration request message may include at least one of the following information.

[0053] - NF Type: Information indicating the type of NF, which may include information indicating EIF.

[0054] - NF ID / address: May include the ID of the EIF and / or the address of the EIF (e.g., FQDN or IP address / port number).

[0055] - list of S-NSSAIs: May contain identifiers of network slice(s) supported by the EIF.

[0056] - Capability: May include whether the collection / disclosure of energy consumption information is supported and whether energy control functions are supported. If the EIF supports the collection / disclosure of energy consumption information, it may include unit information of the supported energy consumption information (e.g., granularity) along with indicator information supporting such functions, and may include one or more of the following: UE unit, UE and slice unit, PDU Session unit, and Traffic Flow unit.

[0057] If the EIF supports a control function for energy consumption information, it may include unit information that supports energy consumption control along with indicator information that supports such function, and may include one or more of UE units, Node units, and S-NSSAI units.

[0058] - Area-related information: May include information indicating the area of ​​responsibility of the EIF. Depending on the placement options of the EIF, one or more of the following may be included.

[0059] - Service area: May include a list of TAIs (tracking area identifiers) for which the EIF provides energy collection / exposure services.

[0060] - EIF service area identifiers: May include identifier(s) representing the area where the EIF provides energy collection / exposure services. If the EIF is responsible for the entire PLMN, a Service area identifier representing the “Entire PLMN” may be included. Where an EIF service area identifier is used, all NF consumers performing discovery of the EIF may have the EIF service area identifier(s) stored in the configuration information and may perform EIF discovery / selection using the EIF service identifier stored in the configuration information.

[0061] - SUPI range (or UE routing indicator range): May include a list (or range) of supported SUPI ranges or UE routing indicator ranges. When a UE routing indicator is used, all NF consumers performing EIF discovery may obtain the routing indicator from the UE ID (i.e., SUPI) from which they wish to collect energy information, and then use the routing indicator to perform EIF discovery / selection.

[0062] - PLMN ID: May include a PLMN ID supported by the EIF.

[0063] - PLMN ID information: If the EIF supports a connection with the EIF of another PLMN, it may include information (PLMN ID, etc.) of the PLMN that supports such a connection. This may be used when it is necessary to contact the HPLMN EIF of the terminal that is roaming.

[0064] In step 202 of FIG. 2, when the NRF receives an NF register request from the EIF, it can send a response message (Nnrf_NFRegister Response (result)) containing information on the processing result of the NF register request to the EIF.

[0065] If the registration request is successful, the NRF may store the information in the form of an NF profile and include processing result information indicating success in a response message sent to the EIF. If the registration request fails, the NRF may include processing result information indicating failure and the cause of failure in a response message sent to the EIF.

[0066] In step 203 of FIG. 2, the Consumer NF can send a request message (Nnrf_NFDiscovery Request) to the NRF to discover the EIF for energy consumption information collection. In FIG. 2, the Consumer NF can be implemented as, for example, AF, NEF, PCF, or NWDAF.

[0067] Consumer NF can send a discovery request message for collecting energy consumption information in at least one of the following cases.

[0068] - If the Consumer NF is NEF, when it receives a subscription request message from the AF containing the UE ID and an event ID indicating energy consumption

[0069] - In the case where the Consumer NF is an AF directly responsible for a specific S-NSSAI(s), and the purpose is to obtain energy consumption information for the UE(s) using the said S-NSSAI(s).

[0070] - In the case where the Consumer NF is an AF responsible for a specific application, and the purpose is to obtain energy consumption information for the UE(s) using that application

[0071] - If the Consumer NF is NWDAF and receives an analytics request message regarding energy consumption information for a specific UE from another NF (e.g., PCF, AMF, etc.)

[0072] - When the Consumer NF is a PCF and energy consumption information for a UE is to be obtained in order to create or update an access and mobility management (AM) policy (e.g., RFSP index, slice replacement policy, etc.) for the UE by considering energy consumption information (e.g., energy consumption or the ratio of reusable energy within energy consumption).

[0073] - When the Consumer NF is a PCF and the purpose is to obtain energy consumption information for the UE in order to create or update a session management (SM) policy (QoS profile, etc.) for the UE by considering energy consumption information (e.g., energy consumption or the ratio of reusable energy within energy consumption).

[0074] - In the case where the Consumer NF is a PCF and energy consumption information for a UE is to be obtained in order to generate or update a UE policy (e.g., ANDSP (access network discovery and selection policy), URSP (UE route selection policy) rule, etc.) for the UE by considering energy consumption information (e.g., energy consumption or the ratio of reusable energy within energy consumption).

[0075] - When the Consumer NF is AMF and the NAS back-off timer for the UE is determined by considering energy consumption information (e.g., energy consumption or the ratio of reusable energy to energy consumption)

[0076] - When receiving an analytics request message regarding energy consumption information for a specific UE from another NF

[0077] The NF discovery message transmitted by the Consumer NF may include the following information.

[0078] - NF Type: Information representing the EIF

[0079] - Consumer NF type: Information indicating the Consumer NF (e.g., may include information indicating AF, NEF, PCF, NWDAF, AMF, etc.)

[0080] - Capability: May include one or more of UE units, UE and slice units, PDU Session units, and Traffic Flow units.

[0081] - UE Unit (or UE and Slice Unit): A UE unit may be included in the following cases: when a Consumer NF is an NEF and the NEF receives a request from an AF to expose energy information including a UE ID; when a Consumer NF is an NWDAF and the NWDAF receives a request from another NF to analyze energy information including a UE ID; when a Consumer NF is a PCF and the PCF receives a request from an AMF to create or update a UE policy association for a UE, etc.

[0082] - PDU Session Unit: A PDU Session unit may be included in the following cases: when a Consumer NF is an NEF and the NEF receives a request from an AF for energy information exposure including UE ID, S-NSSAI, and DNN; when a Consumer NF is an NWDAF and the NWDAF receives a request from another NF for energy information analysis including UE ID, S-NSSAI, and DNN; when a Consumer NF is a PCF and the PCF receives a request from an SMF to create or update an SM policy association for a UE, etc.

[0083] - Traffic flow unit: PDU Session unit: A PDU Session unit may be included in the following cases: when a Consumer NF is an NEF and the NEF receives a request from an AF to expose energy information including a UE ID and IP Filter; when a Consumer NF is an NWDAF and the NWDAF receives a request from another NF to analyze energy information including a UE ID and IP Filter; when a Consumer NF is a PCF and the PCF receives a request from an SMF or AF to create or update an SM policy association including a UE ID and IP Filter, etc.

[0084] - Area information: May include one or more of the following information.

[0085] - service area: May include the TAI list supported by the consumer NF.

[0086] - EIF service area identifiers: An NF consumer may include one or more of the EIF service area identifier(s) stored in the configuration information.

[0087] - list of UE routing indicator: The NF consumer may include the UE ID (i.e., SUPI) from which it wants to collect energy information, or the routing indicator included in the said SUPI.

[0088] - PLMN ID information: If the UE ID for which the NF consumer intends to collect energy information is not a PLMN ID under its charge (i.e., if the UE is a roaming UE), the NF consumer may include the PLMN ID corresponding to the HPLMN of the UE ID.

[0089] In step 204 of FIG. 2, if the NF discovery request message received from the Consumer NF in step 203 contains an NF type representing an EIF, the NRF may include NF profile(s) for one or more EIF instance(s). The NF profile may include the address of the EIF (e.g., FQDN or IP address) and an EIF ID.

[0090] If the NF discovery request message received from the Consumer NF in step 203 contains S-NSSAI(s), the NRF may include the NF profile(s) of the EIF instance(s) that support the S-NSSAI(s) in a response message (Nnrf_NFDiscovery response) that sends them to the Consumer NF.

[0091] If the NF discovery request message received from the Consumer NF in step 203 contains a Capability, the NRF may include the NF profile(s) of an EIF instance(s) that supports the corresponding capability (e.g., along with information indicating an energy collection / control function, and if a UE unit is included, the NF profile(s) of an EIF that supports the UE unit among the EIFs that support energy exposure) in a response message (Nnrf_NFDiscovery response) that sends the NF profile(s) of an EIF that supports the UE unit among the EIFs that support energy exposure.

[0092] If the NF discovery request message received from the Consumer NF in step 203 contains a TAI list, the NRF may include the NF profile(s) of the EIF instance(s) that support the TAI list (i.e., EIF instance(s) that have the TAI(s) included in the TAI list in the service area) in a response message (Nnrf_NFDiscovery response) that sends the NF profile(s) to the Consumer NF.

[0093] If the NF discovery request message received from the Consumer NF in step 203 contains a service area identifier, the NRF may include the NF profile(s) of the EIF instance(s) that support the service area identifier (i.e., the EIF instance(s) that support the service area identifier) ​​in a response message (Nnrf_NFDiscovery response) that sends the NF profile(s) to the Consumer NF.

[0094] If the NF discovery request message received from the Consumer NF in step 203 contains a preferred locality (i.e., a value indicating a specific data center or geographic location where the NF instance is located), the NRF may include the NF profile(s) of the EIF instance(s) that support the locality in a response message (Nnrf_NFDiscovery response) that sends the information to the Consumer NF.

[0095] If the NF discovery request message received from the Consumer NF in step 203 contains a SUPI or routing indicator, the NRF may include the NF profile(s) of the EIF instance(s) that support the said SUPI or routing indicator (i.e., EIF instance(s) that include the said SUPI or routing indicator in the supported SUPI range or routing indicator range among the EIFs) in a response message (Nnrf_NFDiscovery response) that sends to the Consumer NF.

[0096] If the NF discovery request message received from the Consumer NF in step 203 contains PLMN information, the NRF may include the NF profile(s) of the EIF instance(s) that support the PLMN ID (i.e., the EIF instance(s) that support the connection with the PLMN ID) in a response message (Nnrf_NFDiscovery response) that sends the NF profile(s) to the Consumer NF.

[0097] The response message that the NRF sends to the Consumer NF may include, for each EIF instance, an address for the EIF (FQDN or IP address), S-NSSAI(s) supported by the EIF, area information of the EIF (e.g., supported TAI(s), supported service area identifier(s), supported SUPI range or routing indicator range emd), PLMN information, etc.

[0098] In step 205 of FIG. 2, the Consumer NF can select an EIF based on information about the EIF instance(s) included in the NF discovery response message received from the NRF in step 4.

[0099] If a Consumer NF wants to collect energy information for an S-NSSAI (or a UE and an S-NSSAI) (e.g., several Consumer NF cases described in Step 3 may apply), it can select an EIF instance that supports the S-NSSAI.

[0100] If a Consumer NF wants to collect energy information for the UE and S-NSSAI (e.g., several Consumer NF cases described in step 203 may apply), it can select the corresponding UE ID (i.e., SUPI (subscription permanent identifier)) and an EIF instance that supports S-NSSAI.

[0101] If a Consumer NF wants to collect energy information about a UE (e.g., several Consumer NF cases described in step 203 may apply), it can select an EIF instance that supports the corresponding UE ID (i.e., SUPI).

[0102] If a Consumer NF wants to collect energy information about a UE (e.g., several Consumer NF cases described in step 203 may apply), it may select an EIF instance that supports the Consumer NF's service area (i.e., TAI(s)) or the UE's location information (i.e., TAI).

[0103] If the Consumer NF wants to collect energy information about the UE (for example, this may apply to several Consumer NF cases described in Step 3), it can select an EIF instance that supports the service area identifier set in the Consumer NF.

[0104] If a Consumer NF wants to collect energy information about a UE (for example, this may apply to several Consumer NF cases described in Step 3), the Consumer NF can select an EIF instance that supports the preferred locality information.

[0105] In step 206 of Fig. 2, the Consumer NF can send an energy consumption information subscription request message (Neif_EventExposure_Subscribe request) for the UE ID to the selected EIF.

[0106] In step 207 of FIG. 2, the EIF can collect / calculate energy consumption information for the UE ID received in step 6 and send a message to the Consumer NF to notify the Consumer of the information.

[0107] FIG. 3 illustrates a procedure for collecting and exposing energy consumption information (ECI), including a process of discovering EIF through NRF according to an embodiment of the present disclosure.

[0108] Referring to FIG. 3, in step 300a, the UE may send a PDU session establishment request message to the SMF. If the SMF accepts the PDU session establishment, it sends a PDU session establishment acceptance message to the UE. Additionally, the SMF performs registration for the corresponding UE / PDU Session by sending a registration request message to the UDM containing the UE ID (e.g., SUPI or IP address), S-NSSAI, DNN, access type, and SMF ID.

[0109] In step 300b of FIG. 3, AF may send a request message (Nnef_EventExposure_Subscribe Request) to NEF to collect energy consumption-related information for a specific UE. The request message (Nnef_EventExposure_Subscribe Request) may include at least one of the following information.

[0110] -Event ID: Event ID representing energy consumption

[0111] -UE ID: May include terminal identifier information.

[0112] -S-NSSAI(s): When requesting energy consumption information for specific S-NSSAI(s) used by the terminal, the S-NSSAI may be included.

[0113] -S-NSSAI / DNN: When requesting energy consumption information for specific S-NSSAI and DNN used by the terminal, S-NSSAI and DNN may be included.

[0114] - IP Filter: When requesting energy consumption information for a specific traffic flow used by the terminal, the corresponding IP filter (e.g., source IP address / port, destination IP / port, protocol type, etc.) may be included. One or more IP Filter information may be included.

[0115] -reporting frequency: May include the frequency for receiving energy consumption information notifications.

[0116] -area information: When requesting energy consumption information for a specific area, the relevant area information may be included. TAI(s) or geographical information may be included.

[0117] In step 300c of FIG. 3, if the UE identifier information received in step 300b is GPSI, the NEF may include GPSI in a request message to obtain the UE's SUPI sent to the UDM. The UDM may include the SUPI corresponding to GPSI in a response message sent to the NEF.

[0118] In step 301 of FIG. 3, the NF Consumer (NEF or AF) may perform EIF discovery to request energy consumption information from the UE. The NEF may send an NF discovery request message (Nnrf_NFDiscovery request) to the NRF. At this time, the same procedure as step 203 of FIG. 2 may be performed in step 301 of FIG. 3.

[0119] Step 302 of Fig. 3 may use the same procedure as Step 204 of Fig. 2.

[0120] Step 303 of Fig. 3 may use the same procedure as Step 205 of Fig. 2.

[0121] In step 303a of Fig. 3, NEF may include result in the response message (Nnef_EventExposure_Subscribe Response) sent to AF.

[0122] If EIF selection fails in step 303 (for example, if the message received from the NRF in step 302 does not contain any EIF addresses, or if the message received from the NRF in step 302 contains EIF addresses but there are no EIFs satisfying the selection conditions), a response message (Nnef_EventExposure_Subscribe Response) containing a result and cause indicating failure (for example, energy consumption function not found or energy consumption exposure service not supported, etc.) can be sent to the AF.

[0123] If the EIF selection is successful in step 303, the NEF may include a result indicating success in the response message (Nnef_EventExposure_Subscribe Response) sent to the AF.

[0124] In step 303b of FIG. 3, the NF Consumer (NEF or AF) may send a subscription message (Neif_EventExposure_Subscribe) to the EIF requesting information on the UE's energy consumption. The subscription message (Neif_EventExposure_Subscribe) may include at least one of the following information (if the NF Consumer is an NEF, it may utilize the information included in the message received from the AF in step 0b).

[0125] -Event ID: Event ID representing energy consumption

[0126] -UE ID: May include terminal identifier information.

[0127] -S-NSSAI(s): When requesting energy consumption information for specific S-NSSAI(s) used by the terminal, the S-NSSAI may be included.

[0128] -S-NSSAI / DNN: When requesting energy consumption information for specific S-NSSAI and DNN used by the terminal, S-NSSAI and DNN may be included.

[0129] - IP Filter: When requesting energy consumption information for a specific traffic flow used by the terminal, the corresponding IP filter (e.g., source IP address / port, destination IP / port, protocol type, etc.) may be included. One or more IP Filter information may be included.

[0130] -reporting frequency: May include the frequency for receiving energy consumption information notifications.

[0131] -area information: When requesting energy consumption information for a specific area, the relevant area information may be included. TAI(s) or geographical information may be included.

[0132] In step 304a of FIG. 3, the EIF may send a request message (Nudm_UECM_Get request or subscription request) to the UDM to receive information from the AMF responsible for the UE. Alternatively, the EIF may send a subscription request message to the UDM to subscribe to the UE's registration status (e.g., registered or deregistered).

[0133] The message may include the UE ID included in the message received in step 303b.

[0134] In step 304b of FIG. 3, if the request message received from the EIF contains a UE ID, and if the AMF ID responsible for the UE is stored, the UDM may include the AMF ID in the response message (Nudm_UECM_Get response or notify) sent to the EIF. If the message received from the EIF contains an access type (3GPP access or non-3GPP access or both), the UDM may include the AMF ID responsible for the UE for the corresponding access type in the response message (Nudm_UECM_Get response or notify).

[0135] Alternatively, if the subscription request message received from the EIF includes a UE ID and an event identifier indicating registration status, the UDM may include the UE's registration status (registered or deregistered) in a response message (Nudm_UECM_Get response or notify) sent to the EIF. If the message received from the EIF includes an access type (3GPP access, non-3GPP access, or both), the UDM may include the UE's registration status for the corresponding access type in the response message (Nudm_UECM_Get response or notify).

[0136] If the response message received from the UDM in step 304b does not include an AMF ID, the EIF may determine that there is no AMF responsible for the UE. Alternatively, if the EIF receives a notification message from the UDM in step 304b and, according to the message, the UE's registration status information is not registered, the EIF may determine that the UE is not registered. In this case, step 5 may be performed. If an AMF ID responsible for the UE exists or the UE is in a registered state, step 304c may be performed.

[0137] In step 304c of FIG. 3, the EIF may send a request message (Nudm_UECM_Get request) to the UDM to receive information from the SMF responsible for the UE. The request message (Nudm_UECM_Get request) may include the UE ID, S-NSSAI, and DNN included in the message received in step 3b.

[0138] In step 304d of FIG. 3, if the UDM contains UE ID, S-NSSAI, and DNN in the message received from the EIF, and if the corresponding SMF ID is stored, the UDM may include the corresponding SMF ID, UE location information (TAI and / or cell ID), PDU Session ID, S-NSSAI, and DNN in a response message (Nudm_UECM_Get response) that sends to the EIF.

[0139] In step 305 of FIG. 3, the EIF may send a response message (Neif_EventExposure_Subscribe response) for step 3b to the Consumer NF (e.g., NEF). The response message (Neif_EventExposure_Subscribe response) may include at least one of the following information (if it fails, the remaining steps are not performed. If it succeeds, step 306 of FIG. 3 is performed).

[0140] - (If successful) result=success, subscription correlation ID, expiry time, first corresponding energy related information report (eg, UE location information (TAI and cell ID), gNB ID, UPF ID, SMF ID)

[0141] - (If failed, depending on the response message received from the UDM in step 304b) result=failed, cause = UE is not registered (or serving AMF for UE is not found)

[0142] - (If failed, depending on the response message received from the UDM in step 304d) result=failed, no PDU session established for the UE

[0143] In step 306 of Fig. 3, if the message received in step 304b contains SMF ID(s), the EIF can send a subscription request message (Nsmf_EventExposure_Subscribe request) for calculating energy consumption for each SMF.

[0144] If the EIF receives a subscription request message for energy consumption information in step 303b, it may include an event ID in the message sent to the SMF. For example, it may include an event ID representing data usage or an event ID representing energy consumption calculation.

[0145] If the message received by the EIF in step 303b contains one or more of the UE ID, S-NSSAI, and DNN IP Filter, the EIF may include the corresponding parameters in the message sent to the SMF.

[0146] The EIF may include a reporting period and notification information in the message sent to the SMF. If the EIF wants to directly receive information for energy consumption calculation from the UPF (e.g., user data usage information, such as UL / DL data volume information for a certain period of time), it may include address information to receive the notification (e.g., FQDN or IP Address) in the notification information along with a direct notification indicator in the message sent to the SMF.

[0147] In step 307 of Fig. 3, the SMF can send a response message (Nsmf_EventExposure_Subscribe response) for step 6 to the EIF.

[0148] In step 308 of FIG. 3, the SMF receives the message of step 306 and may request the UPF responsible for the PDU Session to report the data volume of the required granularity (e.g., UE unit, UE and S-NSSAI unit, PDU Session unit, SDF unit, etc.) for the parameters (one or more of UE ID, S-NSSAI, DNN, PDU Session ID, IP Filter) included in the message. The message may include an event ID indicating data usage or an event ID indicating energy consumption calculation. If there is one or more corresponding PDU Sessions, the SMF may send a request message to the PDU Session-specific UPF(s) (e.g., PSA UPF and I-UPF(s)) for all PDU Sessions to subscribe to the data volume for a specific period.

[0149] If the message received at step 306 contains an IP Filter or application ID (i.e., at the SDF level), the SMF may send an N4 request message to the UPF for data volume collection. If the message received at step 306 contains notification information (i.e., at the SDF level), the SMF may include notification information in the N4 request message to the UPF for data volume collection.

[0150] If the message received at step 306 does not contain an IP Filter or application ID (i.e., at the UE unit, UE and S-NSSAI unit, or PDU Session unit), the SMF may send an N4 request or SBI message to the UPF for data volume collection. If the message received at step 6 contains notification information (i.e., at the SDF unit), the SMF may include notification information in the Nupf_EventExposure Subscribe message to the UPF for data volume collection.

[0151] When UPF receives an N4 message or an SBI message from SMF, it may include the data volume measured during that time period in a notification message sent to SMF, based on the time information included in the message.

[0152] If the UPF contains notification information in the message received from the SMF, it may directly send a notification message to the corresponding FQDN or IP address (e.g., the FQDN or IP Address of the EIF).

[0153] UPF can include a reference to time interval (timestamp information) in the notification message sent to the address corresponding to the SMF or notification information.

[0154] In step 309 of FIG. 3, if the subscription for the request message received in step 6 includes one or more PDU Sessions, the SMF may receive and aggregate notifications from all corresponding UPF(s) and then generate information to be included in a notification message (Nsmf_EventExposure_Notify) to be sent to the EIF. The SMF may aggregate measurement information based on timestamp information included in the information received from the UPFs (for example, if notification messages are received from different UPFs for a specific UE, the UL Data Volume and DL Data Volume measured at the same time (timestamp) are respectively added to derive the measurement result for the UE at that time (timestamp)).

[0155] The notification message (Nsmf_EventExposure_Notify) that SMF sends to EIF may include at least one of the following information.

[0156] -UE IP address, UE ID, S-NSSAI, DNN, IP Filter

[0157] -List of <ul data volume, dl data upf id(s), gnb id>: May include uplink data volume, downlink data volume, target UPF ID(s), and gNB ID measured over a specific period.

[0158] -Reference to time interval: May include information indicating the time at which the measurement was taken. For example, timestamp information may be included.

[0159] In step 310 of FIG. 3, if the message received by the EIF from the SMF contains gNB ID and / or UPF ID(s) and there is no associated node-level energy consumption information and node-level data volume, the EIF may send a message to the OAM to request such information. The EIF may include the gNB RAN ID(s) and / or UPF ID(s) contained in the message received from the SMF in the request message sent to the OAM. When the OAM receives a request message containing the gNB ID from the EIF, it may include the Data Volume and energy consumption measured at a specific period for the gNB ID in a message sent to the EIF to be transmitted.

[0160] When the OAM receives a request message containing a UPF ID from the EIF, it can include the Data Volume and energy consumption measured at a specific period for the UPF ID in the message sent to the EIF to be transmitted.

[0161] When the OAM receives a request message containing S-NSSAI from the EIF, it can include the Data Volume and energy consumption measured at specific intervals for the S-NSSAI in the message sent to the EIF to transmit.

[0162] In step 311 of FIG. 3, the EIF can calculate energy-related information regarding the granularity (i.e., granularity according to the parameters included in the subscription request message received in step 3b) based on the information received in steps 309 and 310.

[0163] For example, if the message received in step 303b contains a UE ID, information regarding energy consumption for the UE can be calculated (for example, among the energy consumption consumed by gNBs and UPF(s) handling the UE's traffic during a specific time, the ratio of the Data Volume transmitted to the UE during that time to the total Data Volume transmitted by gNBs and UPF(s) during that time can be estimated as the energy consumption for the UE), and the energy consumption information for the UE can be included in a notification message transmitted to the Consumer NF.

[0164] In step 312 of FIG. 3, if the Consumer NF is NEF and the NEF receives a subscription request message from AF in step 300b, it may send a notification message (Nnef_EventExposure_Notify) to AF that includes energy consumption information for the UE included in the message received in step 311.

[0165] FIG. 4 illustrates the EIF registration and discovery procedure through UDM according to an embodiment of the present disclosure.

[0166] Referring to FIG. 4, in step 401, the Consumer NF can perform EIF discovery and selection via the NRF to obtain energy consumption information for the UE. In FIG. 404, the Consumer NF can be implemented as an AF, NEF, or PCF. For EIF discovery, the Consumer NF can first send a message to the UDM requesting registered EIF information for the corresponding UE ID. If there is no registered EIF, the UDM can send a notification message to the Consumer NF to inform it that there is no registered EIF.

[0167] If the Consumer NF confirms that there is no EIF registered in the UDM, it can send an EIF discovery request message to the NRF to perform EIF discovery and selection.

[0168] In step 402 of Fig. 4, the Consumer NF can send a message (Neif_EventExposure_Subscribe request) to the EIF to subscribe to energy consumption information for the UE.

[0169] In step 403 of Fig. 4, the EIF can send a response message (Neif_EventExposure_Subscribe response) for step 402.

[0170] In step 404 of FIG. 4, the EIF may send a message (Nudm_UECM_Register request) to the UDM to register that it is a serving EIF to the UE. The message (Nudm_UECM_Register request) may include at least one of UE ID, S-NSSAI, DNN, NF Type=EIF, and access type.

[0171] In step 405 of Fig. 4, when the UDM receives the message of step 404, it can store the information in the UDR. Additionally, the UDM can send a response message (Nudm_UECM_Register response) to the message of step 4.

[0172] In step 406 of Fig. 4, the remaining energy consumption information collection procedure can be performed.

[0173] In step 407 of Fig. 4, the new Consumer NF can perform EIF discovery to request energy consumption information for the UE. The new Consumer NF can be implemented as an AF, NEF, or PCF. At this time, the message (Nudm_UECM_Get) sent to the UDM may include one or more pieces of information such as UE ID, S-NSSAI, and DNN< NF Type=EIF.

[0174] In step 408 of FIG. 4, if the UDM has EIF ID(s) stored in for the parameters included in the message received in step 7, it may include the EIF ID(s) in the response message (Nudm_UECM_Get response) sent to the Consumer NF.

[0175] The EIF ID may be stored in the UDR. In this case, the UDM can obtain the EIF ID from the UDR.

[0176] In step 409 of Fig. 4, the Consumer NF can select an EIF based on the information received from the UDM and then send an energy consumption information subscription request message (Neif_EventExposure_Subscribe request) to the EIF.

[0177] In step 410 of Fig. 4, the remaining energy consumption information collection procedure can be performed.

[0178] FIG. 5 illustrates an EIF reselection procedure according to an embodiment of the present disclosure.

[0179] Referring to FIG. 5, at step 500, the Consumer NF may subscribe to energy consumption information for a specific UE from the EIF and receive the information from the EIF. The Consumer NF may be implemented as an AF, NEF, or PCF.

[0180] In step 501 of Fig. 5, the Consumer NF can decide to re-select the EIF. This can be done in the following cases:

[0181] - When the UE location changes for a UE subscribing to energy consumption information, and the changed UE location is not included in the EIF's serving area

[0182] - When the Consumer NF is changed and the location of the changed Consumer NF is not included in the EIF's serving area

[0183] In step 502 of Fig. 5, if the Consumer NF decides to re-select the EIF, it may send an unsubscribe request message (Neif_EventExposure_Unsubscribe request) containing a subscription correlation ID to identify the subscription to the existing EIF.

[0184] In step 503 of FIG. 5, when the EIF receives the message of step 2 from the Consumer NF, it can delete the related subscription information and send a response message (Neif_EventExposure_Unsubscribe response) containing the result of the subscription cancellation (success or failure).

[0185] In step 504 of Fig. 5, the EIF can send a message for deregistration (Nudm_UECM_De-register request) to the UDM.

[0186] In step 505 of FIG. 5, when the UDM receives the message of step 504, it can delete the stored EIF ID for the UE ID included in the message. The UDM can send a response message (Nudm_UECM_De-register response) to the EIF.

[0187] In step 506 of Fig. 5, the Consumer NF can perform an EIF discovery and selection procedure (EIF discovery / selection).

[0188] FIGS. 6a and 6b illustrate a context transfer procedure of an EIF according to an embodiment of the present disclosure.

[0189] Referring to FIG. 6a, in step 600, an Old Consumer NF (implemented, e.g., AMF, SMF, PCF, or NWDAF) subscribes to energy consumption information for a UE and can receive a notification message containing energy consumption information for a UE from an Old EIF.

[0190] The Old consumer NF is a consumer NF of the EIF and simultaneously a serving NF for the UE. For example, a situation may occur where an AMF for a UE is subscribing to energy consumption information for the UE from the EIF, an SMF for a UE's PDU Session is subscribing to energy consumption information for the UE from the EIF, an NWDAF for one or more Analytics ID(s) for the UE is subscribing to energy consumption information for the EIF, or a PCF responsible for policies for the UE is subscribing to energy consumption information for the UE from the EIF.

[0191] In step 601 of Fig. 6a, the New Consumer NF can be selected as a new NF for the UE. For example, a new NF (implemented as, e.g., AMF, SMF, PCF, or NWDAF) may be selected for the UE by UE mobility.

[0192] In step 602 of FIG. 6a, the New Consumer NF may send a message (Context transfer request) requesting context for the UE from the Old Consumer NF. The message (Context transfer request) may include a UE ID. If the Consumer NF is an SMF, the new Consumer NF (i.e., SMF) may include a PDU Session ID in the context request message sent to the old consumer NF (i.e., old SMF).

[0193] In step 603 of FIG. 6a, the Old Consumer NF may transmit context information (Context transfer response) for the UE (or PDU Session) to the New Consumer NF. If the old Consumer NF has a subscription for energy consumption information for the UE, the information transmitted by the old consumer NF to the New consumer NF may include such information. The subscription information for energy consumption information for the UE may include at least one of the following information:

[0194] - Subscription correlation ID: May contain identifier information for the subscription.

[0195] - Event ID: May contain the event ID for the subscription.

[0196] - UE ID: May include the subscribed UE ID. May include one or more of SUPI, UE IP address, and GPSI.

[0197] - S-NSSAI, DNN, IP Filter: May contain information about the units subscribed to by the UE.

[0198] - EIF ID / address: May contain the identifier or address of the EIF.

[0199] In step 603b of FIG. 6a, the New Consumer NF may send a message (Nudm_UECM_registeration) to the UDM to register that it is a serving NF for the UE. The message (Nudm_UECM_registeration) may include at least one of a UE ID and an NF Type.

[0200] In step 604 of FIG. 6a, the New Consumer NF can perform an EIF discovery / selection procedure for the UE. The New Consumer NF can perform EIF discovery / selection based on the NRF or based on configuration information. At this time, the New Consumer NF can perform EIF discovery / selection through one or more of the UE's location, its own service area, and the UE's identifier.

[0201] In step 605 of FIG. 6a, the New Consumer NF may send a subscription request message (Neif_EventExposure_Subscribe request) to the newly selected EIF (i.e., New EIF) to collect energy consumption information. The New Consumer NF may send the subscription information for the Old EIF obtained in step 3 to the subscription request message sent to the New EIF. The message (Neif_EventExposure_Subscribe request) may include one or more of the following information:

[0202] - (Information for existing subscriptions, which may include one or more of the following) UE ID, S-NSSAI, DNN, IP Filter

[0203] - Old EIF ID / address

[0204] - Subscription correlation ID

[0205] In step 605a of FIG. 6a, if the New EIF does not have information about the Old EIF's information (ID or address) or information that can identify the Old EIF in the message received in step 5, it may send a request message (Nudm_UECM_Get) to the UDM to obtain the Old EIF ID / address for the UE ID (additionally, S-NSSAI and / or DNN may be included). When the UDM receives the message (Nudm_UECM_Get), it may include the EIF ID and / or EIF address for the Old EIF in a response message (Nudm_UECM_response) sent to the New EIF.

[0206] In step 606 of FIG. 6a, New EIF may send a response message (Neif_EventExposure_Subscribe response) to New Consumer NF for the subscription request received in step 605. The message (Neif_EventExposure_Subscribe response) may include the result of processing the subscription request (e.g., success or failure).

[0207] In step 607 of FIG. 6b, the New EIF may send a context transfer request message to the Old EIF regarding a subscription for collecting energy consumption information for the UE. The message (Context transfer request) may include one or more of the following information:

[0208] - (Information for existing subscriptions, which may include one or more of the following) UE ID, S-NSSAI, DNN, IP Filter

[0209] - Old EIF ID / address

[0210] - Subscription correlation ID

[0211] In step 608 of FIG. 6b, if the Old EIF has context information for a subscription corresponding to a parameter (UE ID or subscription correlation ID) included in the message received in step 607, it may include such context information in the message sent to the New EIF. The context information may include at least one of the following:

[0212] - Address / identifier information related to the data source for collecting energy consumption information for the UE: for example, the address / ID of the data source NF (e.g., may include one or more of the following: SMF ID / address, gNB ID / address, N3IWF ID / address, UPF ID / address, UE ID / address). Additionally, a subscription correlation ID may be included for each data source. The Old EIF may not transmit for some of the data source NF(s). This may be data source(s) for which collection is no longer required based on the request message transmitted by the New EIF, or data source(s) for features not supported by the New EIF.

[0213] - Information of Consumer NF(s) that subscribe to energy consumption information for UE: For Consumer NF(s) that subscribe to energy consumption information for UE, information may include subscription correlation ID, subscription granularity (e.g., may include S-NSSAI, DNN, IP Filter information), reporting frequency, reporting threshold, etc.

[0214] In step 609 of Fig. 6b, the Old EIF may send an unsubscribe request message (Nsmf_EventExposure_Unsubscribe request) to the data source NF(s) among the data source NF(s) that were not sent to the New EIf in step 8. The message (Nsmf_EventExposure_Unsubscribe request) may include a subscription correlation ID that can identify the subscription by data source NF.

[0215] In step 609b of FIG. 6b, the Old EIF may send a request message (Nudm_UECM_deregisteration) to the UDM for deregistration of the UE. The message (Nudm_UECM_deregisteration) may include at least one of a UE ID and an EIF ID.

[0216] In step 610 of FIG. 6b, the New EIF can collect and expose Energy consumption information (ECI) to the UE based on the context information contained in the message received from the Old EIF in step 608. If the New EIF requires a subscription for additional data collection to calculate the ECI for the UE, it can send a Subscribe request message to the data source NF(s).

[0217] In step 611 of Fig. 6b, the EIF can continue to provide ECI exposure services to Consumer NF(s) that are subscribing to ECI for the UE.

[0218] FIG. 7 is a block diagram showing the structure of a terminal according to an embodiment of the present disclosure.

[0219] The terminal described with reference to FIGS. 1 to 6b may correspond to the terminal of FIG. 7. Referring to FIG. 7, the terminal may be composed of a transceiver (710), a memory (720), and a control unit (730). The transceiver (710), the control unit (730), and the memory (720) of the terminal may operate according to the communication method of the terminal described above. However, the components of the terminal are not limited to the examples described above. For example, the terminal may include more components or fewer components than the components described above. Furthermore, the transceiver (710), the control unit (730), and the memory (720) may be implemented in the form of a single chip. Additionally, the control unit (730) may include one or more processors.

[0220] The transceiver (710) is a collective term for the receiver and the transmitter of a terminal, and can transmit and receive signals with a base station, a network entity, a server, or another terminal. The signals transmitted and received with the base station, a network entity, a server, or another terminal may include control information and data. To this end, the transceiver (710) may be composed of an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies a received signal and down-converts the frequency. However, this is merely one embodiment of the transceiver (710), and the components of the transceiver (710) are not limited to an RF transmitter and an RF receiver.

[0221] Additionally, the transmitting and receiving unit (710) can receive a signal through a wireless channel and output it to the control unit (730), and transmit the signal output from the control unit (730) through the wireless channel.

[0222] The memory (720) can store programs and data necessary for the operation of the terminal. Additionally, the memory (720) can store control information or data included in signals obtained from the terminal. The memory (720) may be composed of a storage medium or a combination of storage media such as ROM, RAM, hard disk, CD-ROM, and DVD. Additionally, the memory (720) may not exist separately but may be configured to be included in the processor (730).

[0223] The control unit (730) can control a series of processes so that the terminal can operate according to the embodiments of the present disclosure described above.

[0224] FIG. 8 is a block diagram showing the structure of a network entity according to an embodiment of the present disclosure.

[0225] The network entity described with reference to FIGS. 1 to 6b may correspond to the network entity of FIG. 8. For example, the network entity of FIG. 8 may be implemented as any one of the Consumer NF, NRF, EIF, UDM, SMF, UPF, RAN, AF, and NRF described in FIGS. 1 to 6b.

[0226] Referring to FIG. 8, a network entity may be composed of a transceiver (810), a memory (820), and a control unit (830). Depending on the communication method of the network entity described above, the transceiver (810), the control unit (830), and the memory (820) of the network entity may operate. However, the components of the network entity are not limited to the examples described above. For example, the network entity may include more components or fewer components than the components described above. Furthermore, the transceiver (810), the control unit (830), and the memory (820) may be implemented in the form of a single chip. Additionally, the control unit (830) may include one or more processors.

[0227] The transceiver (810) is a collective term for the receiver and the transmitter of a network entity, and can transmit and receive signals with a terminal or other network entity. The signals transmitted and received with a terminal or other network entity may include control information and data. To this end, the transceiver (810) may be composed of an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies a received signal and down-converts the frequency. However, this is merely one embodiment of the transceiver (810), and the components of the transceiver (810) are not limited to an RF transmitter and an RF receiver.

[0228] Additionally, the transceiver (810) can receive a signal through a wireless channel and output it to the control unit (830), and transmit the signal output from the control unit (830) through the wireless channel.

[0229] The memory (820) can store programs and data necessary for the operation of the network entity. Additionally, the memory (820) can store control information or data included in signals obtained from the network entity. The memory (820) may be composed of a storage medium or a combination of storage media such as ROM, RAM, hard disk, CD-ROM, and DVD. Additionally, the memory (820) may not exist separately but may be configured to be included in the processor (830).

[0230] The control unit (830) can control a series of processes so that the network entity can operate according to the embodiments of the present disclosure described above.

[0231] Methods according to the embodiments described in the claims or specification of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software.

[0232] When implemented in software, a computer-readable storage medium may be provided for storing one or more programs (software modules). One or more programs stored in the computer-readable storage medium are configured for execution by one or more processors within an electronic device. One or more programs include instructions that cause the electronic device to execute methods according to the embodiments described in the claims or specification of this disclosure.

[0233] Such programs (software modules, software) may be stored in random access memory, non-volatile memory including flash memory, read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), magnetic disc storage devices, compact disc-ROM (CD-ROM), digital versatile discs (DVDs), or other forms of optical storage devices, magnetic cassettes. Alternatively, they may be stored in memory composed of some or all of these. Additionally, each constituent memory may include multiple units.

[0234] Additionally, the program may be stored on an attachable storage device that can be accessed via a communication network such as the Internet, Intranet, LAN (local area network), WAN (wide area network), or SAN (storage area network), or a combination thereof. Such a storage device may be connected to a device performing an embodiment of the present disclosure through an external port. Additionally, a separate storage device on a communication network may be connected to a device performing an embodiment of the present disclosure.

[0235] In the specific embodiments of the present disclosure described above, the components included in the disclosure are expressed in a singular or plural form according to the specific embodiments presented. However, the singular or plural expression is selected to suit the situation presented for convenience of explanation, and the present disclosure is not limited to singular or plural components; even if a component is expressed in the plural form, it may be composed of a singular form, and even if a component is expressed in the singular form, it may be composed of a plural form.

[0236] Meanwhile, although specific embodiments have been described in the detailed description of the present disclosure, it is understood that various modifications are possible within the scope of the present disclosure. Therefore, the scope of the present disclosure should not be limited to the described embodiments, but should be defined by the claims set forth below as well as equivalents thereof.

Claims

1. In a method of operation of a consumer network function (NF) in a wireless communication system, A step of transmitting an NF discovery request message to an NRF (energy influence function) including a UE (user equipment) ID, S-NSSAI (single network slice selection assistance information), locality, or service area; A step of receiving an NF discovery response message including an EIF (energy influence function) profile from the NRF; and A method characterized by including the step of selecting an EIF corresponding to the EIF profile based on the above NF discovery response message.

2. A method according to claim 1, characterized in that the consumer NF is a PCF (policy control function) or an AF (application function).

3. A method according to claim 1, wherein the EIF profile includes the address of the EIF and the ID of the EIF.

4. In Paragraph 1, The method further includes the step of sending a subscription request message for the UE's energy consumption event to the selected EIF. A method characterized in that the above subscription request message includes at least one of an event ID, UE ID, S-NSSAI, IP filter, reporting frequency, or area information.

5. In Paragraph 4, The method further includes the step of receiving a response message to the above subscription request message from the above EIF, and The above response message includes result information indicating success when the subscription request is successful, and A method characterized in that the above response message includes result information indicating failure and cause information indicating failure when a subscription request fails.

6. In the method of operation of the EIF (energy influence function) in a wireless communication system, A step of receiving a subscription request message for an energy consumption event of a UE (user equipment) from a consumer NF (network function); and It includes the step of transmitting a response message to the above subscription request message to the above consumer NF, and A method characterized in that the above EIF is selected by the consumer NF based on an EIF profile included in an NF discovery response message.

7. A method according to claim 6, characterized in that the consumer NF is a PCF (policy control function) or an AF (application function).

8. A method according to claim 6, wherein the EIF profile includes the address of the EIF and the ID of the EIF.

9. In Paragraph 6, A method characterized in that the above subscription request message includes at least one of an event ID, UE ID, S-NSSAI, IP filter, reporting frequency, or area information.

10. In Paragraph 6, The above response message includes result information indicating success when the subscription request is successful, and A method characterized in that the above response message includes result information indicating failure and cause information indicating failure when a subscription request fails.

11. In the consumer network function (NF) of a wireless communication system, Transmitter / receiver; and It includes a control unit, and the control unit is: Controls the transmission of an NF discovery request message containing a UE (user equipment) ID, S-NSSAI (single network slice selection assistance information), locality, or service area to the NRF (energy influence function), and Receive an NF discovery response message containing an EIF (energy influence function) profile from the NRF, and A consumer NF characterized by selecting an EIF corresponding to the EIF profile based on the above NF discovery response message.

12. In paragraph 11, the control unit is: Controls sending a subscription request message for the UE's energy consumption event to the selected EIF, and A consumer NF characterized in that the above subscription request message includes at least one of an event ID, UE ID, S-NSSAI, IP filter, reporting frequency, or area information.

13. In Clause 12, the control unit is: Receive a response message to the above subscription request message from the above EIF, and The above response message includes result information indicating success when the subscription request is successful, and A consumer NF characterized by the above response message including result information indicating failure and cause information indicating the failure when the subscription request fails.

14. In the energy influence function (EIF) of a wireless communication system, Transmitter / receiver; and It includes a control unit, and the control unit is: Receive a subscription request message for an energy consumption event of a UE (user equipment) from a consumer NF (network function), and Controls the transmission of a response message to the above subscription request message to the above consumer NF, and The EIF is characterized by being selected by the consumer NF based on an EIF profile included in an NF discovery response message.

15. In Paragraph 14, The above response message includes result information indicating success when the subscription request is successful, and The above response message is characterized by including result information indicating failure and cause information indicating failure when the subscription request fails.

Images