Method and device for processing energy information in wireless communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting higher data transmission rates. Provided is a method performed by a session management function (SMF) in a wireless communication system. The method comprises the steps of: receiving, from an energy information function (EIF), a subscription message for receiving notification of information about energy consumption related to a PDU session; acquiring, from a user plane function (UPF), information about a data volume related to the PDU session only when the PDU session is through a third generation partnership project (3GPP) access; and transmitting, to the EIF, a first notification message including information for calculating energy consumption on the basis of the acquired information about the data volume.

Description

Method and apparatus for processing energy information in a wireless communication system

[0001] The present disclosure relates to a method and apparatus for processing energy information in a wireless communication system, and in particular to supporting energy consumption information in a wireless communication system in a heterogeneous 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) to support new services through linkage and convergence with other industries, Integrated Access and Backhaul (IAB) which provides nodes to expand 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) to incorporate 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 has led to the development of 6G mobile communication technologies, including multi-antenna transmission technologies such as new waveforms, Full Dimensional MIMO (FD-MIMO), array antennas, and large-scale antennas to guarantee coverage in the terahertz band; metamaterial-based lenses and antennas to improve terahertz band signal coverage; high-dimensional spatial multiplexing technology using Orbital Angular Momentum; and Reconfigurable Intelligent Surface (RIS) technology. In addition, it includes Full Duplex technology for enhancing frequency efficiency and system networks, 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 next-generation distributed networks that realize 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 computing technology, etc.

[0008] The present invention proposes a method and device for supporting energy consumption information in a wireless communication system in a heterogeneous wireless communication system.

[0009] According to one embodiment, a method is provided to be performed by a session management function (SMF) in a wireless communication system. The method may include: receiving a subscription message to be notified of information regarding energy consumption associated with a PDU session from an energy information function (EIF); obtaining information regarding a data volume associated with a PDU session from a user plane function (UPF) only if the PDU session is through a third-generation partnership project (3GPP) access; and transmitting a first notification message to the EIF containing information for calculating energy consumption based on the information regarding the obtained data volume.

[0010] The above method may further include the step of transmitting a second notification message to the EIF containing the value of an uplink / downlink (UL / DL) data volume representing a value of 0 when the PDU session is through non-3GPP access.

[0011] The step of obtaining information about the data volume associated with the PDU session from the above UPF may include the step of transmitting an N4 request message to request the UPF to report the data volume of the required granularity.

[0012] The first notification message above may further include at least one of a gNB ID, an access type, or a UPF ID.

[0013] The subscription message may include at least one of an event ID indicating data usage or energy consumption calculation, an ID of the PDU session, a UE ID, and single-network slice selection auxiliary information (S-NSSAI).

[0014] According to one embodiment, a device for a session management function (SMF) in a wireless communication system is provided. The device may include a memory for storing instructions; and at least one processor operably connected to the memory. The instructions may be executable by the at least one processor to cause the device to execute operations. The operations may include receiving a subscription message to be notified of information regarding energy consumption associated with a PDU session from an energy information function (EIF); obtaining information regarding a data volume associated with a PDU session from a user plane function (UPF) only if the PDU session is through a third-generation partnership project (3GPP) access; and transmitting a first notification message to the EIF containing information for calculating energy consumption based on the information regarding the obtained data volume.

[0015] According to one embodiment, a non-transient computer-readable storage medium for storing commands is provided. The commands may be executable by at least one processor of the device to enable a device of a session management function (SMF) to execute operations. The operations may include receiving a subscription message to be notified of information regarding energy consumption associated with a PDU session from an energy information function (EIF); obtaining information regarding a data volume associated with a PDU session from a user plane function (UPF) only if the PDU session is through a third-generation partnership project (3GPP) access; and transmitting a first notification message to the EIF containing information for calculating energy consumption based on the information regarding the obtained data volume.

[0016] According to the embodiments of the present disclosure, the effect of distributing the load and improving the reliability of the energy information provision function can be achieved.

[0017] Figure 1 shows the 5G system architecture.

[0018] FIG. 2 illustrates a procedure for collecting / exposing energy consumption information (ECI) considering an access type according to one embodiment of the present disclosure.

[0019] FIG. 3 illustrates a procedure for collecting / exposing energy consumption information (ECI) considering 3GPP access according to one embodiment of the present disclosure.

[0020] FIG. 4 illustrates an ECI collection procedure when the Access Type of a PDU Session is changed according to one embodiment of the present disclosure.

[0021] FIG. 5 is a block diagram of a device according to one embodiment of the present disclosure.

[0022] Figure 1 shows the 5G system architecture.

[0023] A 5G mobile communication network consists of 5G UE (user equipment, terminal), 5G RAN (radio access network, base station), gNB (5G nodeB), eNB (evolved nodeB, etc.), and a 5G core network. The 5G core network is composed of NFs such as AMF (access and mobility management function) which provides mobility management functions for UEs, SMF (session management function) which provides session management functions, UPF (user plane function) which performs data delivery roles, PCF (policy control function) which provides policy control functions, UDM (unified data management) which provides data management functions such as subscriber data and policy control data, and UDR (unified data repository) which stores data from various network functions (NFs) including UDM.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0038] - N14: Reference point between 2 AMFs

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

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

[0041] The present invention proposes a discovery method for an energy information function in a 5G system. An energy information function (EIF) (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.

[0042] 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 EIF or located in a different NF. If the function for controlling energy consumption is integrated into the EIF, the EIF may perform energy control for the UE based on the energy collection information for the UE.

[0043] FIG. 2 illustrates a procedure for collecting / exposing energy consumption information (ECI) considering an access type according to one embodiment of the present disclosure.

[0044] Step 0a. The UE sends 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.

[0045] Step 0b. The AF may send a request message to the network exposure function (NEF) to collect energy consumption-related information for a specific UE. The message may include the following information.

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

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

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

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

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

[0051] -access type: If you want to collect ECI for a specific access type, you may include the access type. It may include 3GPP access, non-3GPP access, or both.

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

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

[0054] Step 0c. If the UE identifier information received in Step 0b is GPSI, the NEF may include the GPSI in a request message to obtain the UE's SUPI sent to the UDM. The UDM may include the SUPI corresponding to the GPSI in a response message sent to the NEF.

[0055] Step 1. The NEF or AF may perform EIF discovery to request energy consumption information from the UE. The NEF may send an NF discovery request message to the NRF. The message may include NF type = EIF and service area information.

[0056] Step 2. The NRF may include NF profile(s) containing EIF addresses that satisfy the parameters included in the message received in Step 1 in the response message.

[0057] Step 3. The NEF can select one of the EIFs included in the message received from the NRF.

[0058] Step 3a. NEF may include result in the response message sent to AF.

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

[0060] If EIF selection is successful in Step 3, NEF may include a result indicating success in the response message sent to AF.

[0061] Step 3b. The NEF or AF may send a subscription message to the EIF requesting information on the UE's energy consumption. The message may include the following information. If the NF Consumer is the NEF, it may utilize the information included in the message received from the AF in Step 0b.

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

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

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

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

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

[0067] -access type: If you want to collect ECI for a specific access type, you may include the access type. It may include 3GPP access, non-3GPP access, or both.

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

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

[0070] Step 4a. The EIF may send a request message to the UDM to receive information from the SMF responsible for the UE. The message may include the UE ID, S-NSSAI, and DNN included in the message received in Step 3b. If the message received in Step 3b includes an access type, the corresponding access type may be included.

[0071] Step 4b. If the message received from the EIF contains UE ID, S-NSSAI, DNN, (additionally access type), and if the corresponding SMF ID(s) are stored, the UDM may include the corresponding SMF ID, UE location information (TAI and / or cell ID), PDU Session ID, S-NSSAI, DNN, (additionally access type) for each SMF in a response message sent to the EIF.

[0072] Step 5. The EIF may send a response message for Step 3b to the Consumer NF (e.g., NEF). The message may include the following information. If it fails, the remaining steps are not performed. If it succeeds, Step 6 is performed.

[0073] (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)

[0074] (If it fails, depending on the response message received from the UDM in Step 4b) result=failed, cause = UE is not registered (or serving AMF for UE is not found)

[0075] (If it fails, depending on the response message received from the UDM in Step 4d) result=failed, no PDU session established for the UE

[0076] Step 6. If the message received in Step 4b contains SMF ID(s), the EIF may send a subscription request message for calculating energy consumption for each SMF.

[0077] If the EIF receives a subscription request message for energy consumption information in step 3b, 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.

[0078] If the message received by the EIF in step 3b 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.

[0079] If the message received by the EIF in step 3b contains an access type, the EIF may include the corresponding access type in the message sent to the SMF.

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

[0081] Step 7. SMF can send a response message for Step 6 to EIF.

[0082] Step 8. The SMF receives the message of Step 6 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 more than one corresponding PDU Session, the SMF may send an SBI message or an N4 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.

[0083] If the message received in Step 6 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 in Step 6 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.

[0084] If the message received in Step 6 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 in 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.

[0085] 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 contained in the message.

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

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

[0088] Step 9. 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 generate information to be included in a notification message to be sent to the EIF. The SMF may aggregate measurement information based on the 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 timestamp are respectively added to derive the measurement result for the UE at that timestamp).

[0089] The notification message that SMF sends to EIF may include the following information.

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

[0091] - Access Type: If the access type of the PDU Session is 3GPP access, 3GPP access may be included. If the access type of the PDU Session is non-3GPP access, non-3GPP access may be included. If the PDU session has UP resources for both 3GPP access and non-3GPP access, both (i.e., 3GPP access and non-3GPP access) may be included.

[0092] -List of <ul data volume, dl data upf id(s), gnb id, access type>: May include uplink data volume, downlink data volume, target UPF ID(s), gNB ID, and access type measured over a specific period. If the UE uses non-3GPP access, the gNB ID may not be included. Additionally, if the UE uses non-3GPP access, an access type indicating non-3GPP access may be included.

[0093] -List of <ul data volume, dl data upf id(s), n3iwf id, access type>: May include uplink data volume, downlink data volume, target UPF ID(s), N3IWF ID, and access type measured over a specific period. If the UE uses non-3GPP access, the N3IWF ID may be included. Additionally, if the UE uses non-3GPP access, an access type indicating non-3GPP access may be included.

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

[0095] The information that may be included in the notification message sent by SMF to EIF may be expressed as shown in Table 1 below. In the information below, UE Location Information (UE's TAI and cell ID) may be included instead of N3IWF ID.

[0096] InformationDescriptionUE IP addressUE IP address.UE IDSUPI.S-NSSAI +DNNSlice and DNN applicable to a PDU session.Access Type3GPP access or non-3GPP accessPacket FiltersPacket Filters for IP or Ethernet traffic.Application IdentifierIdentification for the traffic of the service data flow.List of Data Volume informationThe data volume and the associated UPF(s) and gNB(s) serving the UE within the time period.> UL / DL Data Volume of UPFThe UL / DL Data Volume of a PDU Session identified by (UE-ID, S-NSSAI / DNN) or a Service Data flow (UE ID, S-NSSAI, DNN, Packet Filters / Application Identifier).> (I-)UPF ID(s)Identifier of any (I-)UPF(s) associated to a reported data volume used by a PDU Session identified by (UE-ID, S-NSSAI / DNN) or a Service Data flow (UE ID, S-NSSAI, DNN, Packet Filters / Application Identifier).> gNB ID serving the UEThe gNB which serving the UE.> N3IWF ID serving the UEThe N3iWF which serving the UE.Time periodTime period of the collected information.

[0097] Steps 10a-10b. If the message received by the EIF from the SMF contains N3IWF 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 (Operations, Administration and Maintenance) to request such information. The EIF may include the N3IWF 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 from the EIF containing the N3IWF ID, it may include the Data Volume and energy consumption measured at specific intervals for the N3IWF ID in the message sent to the EIF to be transmitted.

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

[0099] The EIF can obtain the data volume consumed by the UE's gNB, N3IWF, and UPF during a specific period based on notification messages received from each SMF. Additionally, it can obtain the node-level data volume and node-level energy consumption consumed by the gNB, N3IWF, and UPF from the OAM. For granularity G (e.g., one of UE, UE and S-NSSAI, PDU Session, or Traffic Flow), the EIF can calculate the energy consumption (i.e., E_G,N) at each node N (e.g., X can be one of gNB, N3IWF, or UPF) as follows.

[0100] E_G,N = (Energy consumption of G) * (Data volume transmitted by N to G) / (Data volume transmitted by N)

[0101] Step 11. Based on the information received in Steps 9 and 10, 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).

[0102] If the EIF calculates the energy consumption for granularity G (e.g., UE, UE and S-NSSAI, PDU Session, Traffic Flow) based on request parameters received from the Consumer NF, the EIF can calculate the energy consumption information for G by adding E_G,N for all nodes N (e.g., UPF, N3IWF, gNB) that process the UE's traffic.

[0103] The EIF can include the energy consumption for granularity G (e.g., UE, UE and S-NSSAI, PDU Session, Traffic Flow) subscribed to by the Consumer NF in a notification message sent to the Consumer NF.

[0104] If the access type is included in the subscription message received from the Consumer NF in step 3b, the EIF may calculate energy consumption information for the UE by adding only the E_G,N for the corresponding access type. For example, if the access type is 3GPP access, the EIF may calculate the energy consumption for G during that time by adding up all E_G,N for the nodes N responsible for the session established by 3GPP access (e.g., gNB and UPF responsible for the PDU Session) and include this value in the notification message sent to the Consumer NF. For example, if the access type is non-3GPP access, the EIF may calculate the energy consumption for G during that time by adding up all E_G,N for the nodes N responsible for the session established by non-3GPP access (e.g., N3IWF and / or UPF responsible for the PDU Session) and include this value in the notification message sent to the Consumer NF.

[0105] If the subscription message received from the Consumer NF in step 3b does not indicate or include both access types, the EIF may calculate the sum of all E_G and N for all access types as the energy consumption for G during that time and include it in the notification message sent to the Consumer NF.

[0106] The notification message sent by the EIF to the Consumer NF may include one or more of the following: Subscription correlation ID, UE IP address, UE ID, S-NSSAI, DNN, Packet filters, Application identifier, access type, Energy consumption for the required granularity, and time period.

[0107] Step 12. If the Consumer NF is NEF and the NEF receives a subscription request message from AF in Step 0b, it may send a notification message to AF containing energy consumption information for the UE (or Granulrity G) included in the message received in Step 11.

[0108] FIG. 3 illustrates a procedure for collecting / exposing energy consumption information (ECI) considering 3GPP access according to one embodiment of the present disclosure.

[0109] Step 0a. The UE sends 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.

[0110] Step 0b. The AF may send a request message to the NEF to collect energy consumption-related information for a specific UE. The message may include the following information.

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

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

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

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

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

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

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

[0118] Step 0c. If the UE identifier information received in Step 0b is GPSI, the NEF may include the GPSI in a request message to obtain the UE's SUPI sent to the UDM. The UDM may include the SUPI corresponding to the GPSI in a response message sent to the NEF.

[0119] Step 1. The NEF or AF may perform EIF discovery to request energy consumption information from the UE. The NEF may send an NF discovery request message to the NRF. At this time, the same procedure as Step 1 of FIG. 2 may be used.

[0120] Step 2. The same procedure as Step 2 of Fig. 2 can be used.

[0121] Step 3. Step 2. The same procedure as Step 3 of Fig. 2 may be used.

[0122] Step 3a. NEF may include result in the response message sent to AF.

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

[0124] If EIF selection is successful in Step 3, NEF may include a result indicating success in the response message sent to AF.

[0125] Step 3b. The NEF or AF may send a subscription message to the EIF requesting information on the UE's energy consumption. The message may include the following information. If the NF Consumer is the NEF, it may utilize the information included in the message received from the AF in Step 0b.

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

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

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

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

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

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

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

[0133] Step 4a. The EIF may send a request message to the UDM to receive information from the SMF responsible for the UE. The message may include the UE ID, S-NSSAI, and DNN included in the message received in Step 3b.

[0134] Step 4b. If the message received from the EIF contains UE ID, S-NSSAI, DNN, (additionally access type), and if the corresponding SMF ID(s) are stored, the UDM may include the corresponding SMF ID, UE location information (TAI and / or cell ID), PDU Session ID, S-NSSAI, DNN, (additionally access type) for each SMF in a response message sent to the EIF.

[0135] Step 4c. In one embodiment, the EIF may send a subscription request for a change of access type for the PDU session to the SMF included in the information received in Step 4b. In other embodiments, steps 4c-4d may not be performed.

[0136] Step 4d. When the SMF receives the message of Step 4c, it may include the access type for the PDU session in a notification message sent to the EIF or in a response message to Step 4c. Additionally, if the access type for the PDU session changes, the SMF may include the changed access type in the notification message sent to the EIF.

[0137] Step 5. The EIF may send a response message for Step 3b to a Consumer NF (e.g., NEF). The EIF may include in the response message sent to the Consumer NF a cause (UE not registered over 3GPP access, no PDU Session over 3GPP access) along with a result indicating failure for the granularity received in Step 3b (e.g., information including one or more of S-NSSAI, DNN, IP Filter along with UE ID), if the UE does not have a session established over 3GPP access, or if the UE is not registered over 3GPP access.

[0138] Step 6. If the message received in Step 4b contains SMF ID(s), the EIF may send a subscription request message for calculating energy consumption for each SMF.

[0139] In the case of an embodiment where the EIF performs steps 4c-4d, the EIF may send a subscription request message only to the SMF(s) responsible for the PDU session whose access type is 3GPP access, based on the message received in step 4d.

[0140] In another embodiment, if the EIF does not perform steps 4c-4d, the EIF does not know the access type of the PDU session managed by the SMF. In this case, the EIF may send a subscription request message for the information necessary to calculate energy consumption to all SMFs managed by the UE's PDU Session or granularity (i.e., information including the UE ID and one or more of S-NSSAI, DNN, IP Filter, and application identifier, from which energy consumption information is to be collected).

[0141] If the EIF receives a subscription request message for energy consumption information in step 3b, 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.

[0142] If the message received by the EIF in step 3b 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.

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

[0144] Step 7. The SMF may send a response message regarding Step 6 to the EIF. If a PDU session is established with non-3GPP access for the UE ID, S_NSSAI, and DNN received in Step 6 (or if no PDU session established with 3GPP access exists for the UE ID, S_NSSAI, and DNN received in Step 6), the SMF may include a result indicating failure and a cause (e.g., the access type is non-3GPP access) in the response message sent to the EIF. In this case, the EIF may not send a subscription request message to the SMF again.

[0145] In another embodiment, the MF may include a result indicating success, information indicating no user plane resources established for 3GPP access, and a subscription correlation ID in a response message transmitted to the EIF. The SMF may then perform information collection and exposure for ECI calculation (i.e., perform steps 8 and 9) if a PDU session is established for 3GPP access with respect to the UE ID, S-NSSAI, and DNN (or PDU session ID) received in step 6.

[0146] Step 8. The SMF receives the message of Step 6 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 more than one corresponding PDU Session, the SMF may send an SBI message or an N4 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.

[0147] If the message received in Step 6 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 in Step 6 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.

[0148] If the message received in Step 6 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 in 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.

[0149] 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 contained in the message.

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

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

[0152] If the corresponding PDU session was established via non-3GPP access, the SMF may not send a request message for N4 reporting to the UPF. The SMF may send a request message for N4 reporting to the UPF only if the corresponding PDU session was established via 3GPP access.

[0153] Step 9. 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 generate information to be included in a notification message to be sent to the EIF. The SMF may aggregate measurement information based on the 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 timestamp are respectively added to derive the measurement result for the UE at that timestamp).

[0154] The notification message that SMF sends to EIF may include the following information.

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

[0156] - Access Type: If the access type of the PDU Session is 3GPP access, 3GPP access may be included. If the access type of the PDU Session is non-3GPP access, non-3GPP access may be included. If the PDU session has UP resources for both 3GPP access and non-3GPP access, both (i.e., 3GPP access and non-3GPP access) may be included.

[0157] -List of <ul data volume, dl data upf id(s), gnb id, access type>: May include uplink data volume, downlink data volume, target UPF ID(s), gNB ID, and access type measured over a specific period. If the UE uses non-3GPP access, the gNB ID may not be included. Additionally, if the UE uses non-3GPP access, an access type indicating non-3GPP access may be included.

[0158] -List of <ul data volume, dl data upf id(s), n3iwf id, access type>: May include uplink data volume, downlink data volume, target UPF ID(s), N3IWF ID, and access type measured over a specific period. If the UE uses non-3GPP access, the N3IWF ID may be included. Additionally, if the UE uses non-3GPP access, an access type indicating non-3GPP access may be included.

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

[0160] The notification messages that SMF sends to EIF may include the information shown in Table 2. In the information below, UE Location Information (UE's TAI and cell ID) may be included instead of N3IWF ID.

[0161] InformationDescriptionUE IP addressUE IP address.UE IDSUPI.S-NSSAI +DNNSlice and DNN applicable to a PDU session.Access Type3GPP access or non-3GPP accessPacket FiltersPacket Filters for IP or Ethernet traffic.Application IdentifierIdentification for the traffic of the service data flow.List of Data Volume informationThe data volume and the associated UPF(s) and gNB(s) serving the UE within the time period.> UL / DL Data Volume of UPFThe UL / DL Data Volume of a PDU Session identified by (UE-ID, S-NSSAI / DNN) or a Service Data flow (UE ID, S-NSSAI, DNN, Packet Filters / Application Identifier).> (I-)UPF ID(s)Identifier of any (I-)UPF(s) associated to a reported data volume used by a PDU Session identified by (UE-ID, S-NSSAI / DNN) or a Service Data flow (UE ID, S-NSSAI, DNN, Packet Filters / Application Identifier).> gNB ID serving the UEThe gNB which serving the UE.> N3IWF ID serving the UEThe N3iWF which serving the UE.Time periodTime period of the collected information.

[0162] In another embodiment, if the SMF does not have a PDU session established via 3GPP access, the SMF may include a value indicating 0 in the UL / DL Data Volume of UPF in the List of Data Volume of information in the message transmitted to the EIF, or may not include the List of Data Volume of information. Steps 10a-b. 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 transmit a message to request such information from the OAM. The EIF may include the gNB ID(s) and / or UPF ID(s) included in the message received from the SMF in the request message transmitted to the OAM. When the OAM receives a request message containing gNB ID from the EIF, it may include the Data Volume and energy consumption measured at a specific period for the gNB ID in the message transmitted to the EIF.

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

[0164] The EIF can obtain the data volume consumed by the UE's gNB and UPF during a specific period based on notification messages received from each SMF. Additionally, it can obtain the node-level data volume and node-level energy consumption consumed by the gNB and UPF from the OAM. For granularity G (e.g., one of UE, UE and S-NSSAI, PDU Session, or Traffic Flow), the EIF can calculate the energy consumption (i.e., E_G,N) at each node N (e.g., X can be either a gNB or a UPF) as follows.

[0165] E_G,N = (Energy consumption of G) * (Data volume transmitted by N to G) / (Data volume transmitted by N)

[0166] The EIF may not send request information to the OAM for the UPF ID included in the message received from the SMF if the message received from the SMF contains information indicating non-3GPP access, or if the message received from the SMF contains ULI (UE location information) and the ULI indicates non-3GPP access, or if the SMF is an SMF responsible only for PDU sessions established with non-3GPP access, or if the message received from the SMF does not contain a gNB ID. Additionally, the EIF calculates E_G,N only for Node N responsible for PDU sessions established with 3GPP access.

[0167] Step 11. Based on the information received in Steps 9 and 10, 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).

[0168] If the EIF calculates the energy consumption for granularity G (e.g., UE, UE and S-NSSAI, PDU Session, Traffic Flow) based on request parameters received from the Consumer NF, the EIF can calculate the energy consumption information for G by adding E_G,N for all nodes N (e.g., UPF, gNB) that handle traffic to the UE's 3GPP access.

[0169] The EIF can include the energy consumption for granularity G (e.g., UE, UE and S-NSSAI, PDU Session, Traffic Flow) subscribed to by the Consumer NF in a notification message sent to the Consumer NF.

[0170] If the EIF can calculate energy consumption information for the UE by adding only E_G and N for the 3GPP access, the EIF can calculate the energy consumption for G during that time by adding all E_G and N for the nodes N responsible for the session established by the 3GPP access (e.g., gNB and UPF responsible for the PDU Session) and include the result in a notification message sent to the Consumer NF.

[0171] The notification message sent by the EIF to the Consumer NF may include one or more of the following: Subscription correlation ID, UE IP address, UE ID, S-NSSAI, DNN, Packet filters, Application identifier, access type, Energy consumption for the required granularity, and time period.

[0172] Step 12. If the Consumer NF is NEF and the NEF receives a subscription request message from AF in Step 0b, it may send a notification message to AF containing energy consumption information for the UE (or Granulrity G) included in the message received in Step 11.

[0173] FIG. 4 illustrates an ECI collection procedure when the Access Type of a PDU Session is changed according to one embodiment of the present disclosure.

[0174] Step 0. Step 12 is performed in Step 0a of Fig. 3.

[0175] The EIF can send a subscription request message to the SMF containing one or more of the UE ID, S-NSSAI, and DNN, and an event ID (e.g., one of data usage, information for ECI calculation, or change of access type).

[0176] Step 1. The access type of the PDU session may change, or the node information responsible for the PDU session may change.

[0177] Step 2. The SMF may send a notification message to the EIF containing changed information about the PDU Session. The message may include one or more of the access type and serving node ID(s) of the PDU session (e.g., N3IWF ID, gNB ID, UPF ID). The SMF may include the access type and serving node ID of the PDU Session only when the information has changed, or may continue to include them in periodic notification messages.

[0178] If the node identifier information is changed based on the information received from the SMF (e.g., UPF ID is changed, gNB ID is not included, N3IWF ID is added, etc.), the EIF can perform steps 3a-3b.

[0179] Based on the information received from the SMF, the EIF may perform steps 4a-4b if the access type changes (e.g., if it changes from 3GPP to non-3GPP).

[0180] Step 3a. If the existing Node ID (e.g., gNB ID) in the information received from the SMF has been removed, and if there is information from the OAM regarding subscriptions to that node (i.e., Energy Consumption and Data Volume information for the configuration time T), the EIF may send a request message to cancel the subscription. The message may include a Node ID (e.g., gNB ID or UPF ID) or a subscription correlation ID.

[0181] Step 3b. If the information received from the SMF includes a Node ID that was not previously present (e.g., N3IWF ID), the EIF may send a request message to the OAM to subscribe to Energy Consumption and Data Volume information for the corresponding node for the set time T. The message may include a node ID (e.g., N3iWF ID) or a subscription correlation ID.

[0182] Step 3c. OAM sends a notification message regarding the Energy Consumption and / or Data volume usage for T hours stored as configuration information for the node identifier requested by EIF in Step 3b.

[0183] Step 4a. If the access type changes from 3GPP access to non-3GPP access based on information received from the SMF, the EIF may not use the Data Volume information included in the information received from the SMF for the UE's ECI calculation. In this case, the EIF may send a request message to cancel the subscription for the Node IDs (e.g., UPF ID(s), gNB ID) included in the information received from the SMF. The message may include a Node ID (e.g., gNB ID or UPF ID) or a subscription correlation ID.

[0184] Step 4b. If the access type is changed from non-3GPP access to 3GPP access based on the information received from the SMF, the EIF may use the Data Volume information included in the information received from the SMF for the UE's ECI calculation. The EIF may send a request message to perform a subscription for the Node IDs (e.g., UPF ID(s), gNB ID) included in the information received from the SMF. The message may include the Node ID (e.g., gNB ID or UPF ID).

[0185] Step 4c. OAM sends a notification message regarding the Energy Consumption and / or Data volume usage for T hours stored as configuration information for the node identifier requested by EIF in Step 3b.

[0186] Step 5. The EIF can calculate the ECI for the subscribed granularity (UE ID and one or more of S-NSSAI, DNN, IP Filter, App Identifier) ​​and include it in the notification message sent to the Consumer NF.

[0187] FIG. 5 is a block diagram of a device according to one embodiment of the present disclosure.

[0188] The device may implement one of the UE or network entities described above (e.g., AN3IWF, AMF, OAM, UPF, SMF, UDM, NRF, EIF, NEF, and AF). Additionally, the device may implement a base station.

[0189] As illustrated in FIG. 5, the device of the present disclosure may include a transceiver (510), a memory (520), and a processor (530). The processor (530), transceiver (510), and memory (520) of the device may operate according to the communication method of the device described above. However, the components of the device are not limited to the examples described above. For example, the device may include more components or fewer components than the components described above. In addition, the processor (530), transceiver (510), and memory (520) may be implemented in the form of a single chip.

[0190] The transceiver (510) is a collective term for the receiving part of the device and the transmitting part of the device, and can transmit and receive signals with other devices or other network entities. At this time, the signals transmitted and received may include control information and data. To this end, the transceiver (510) may be composed of an RF transmitter that up-converts and amplifies the frequency of the transmitted signal, and an RF receiver that low-noise amplifies the received signal and down-converts the frequency. However, this is merely one embodiment of the transceiver (510), and the components of the transceiver (510) are not limited to the RF transmitter and the RF receiver. The transceiver (510) may include wired and wireless transceivers and may include various configurations for transmitting and receiving signals.

[0191] Additionally, the transceiver (510) can receive a signal through a communication channel (e.g., a wireless channel) and output it to a processor (530), and transmit the signal output from the processor (530) through the communication channel.

[0192] Additionally, the transceiver (510) receives a communication signal and outputs it to a processor, and can transmit the signal output from the processor to a terminal or another network entity through a wired or wireless network.

[0193] The memory (520) can store programs and data necessary for the operation of the device. Additionally, the memory (520) can store control information or data included in signals obtained from the device. The memory (520) may be composed of a storage medium or a combination of storage media such as ROM, RAM, hard disk, CD-ROM, and DVD. The memory (520) can store instructions. When executed by the processor (430), the instructions may cause the device (or processor (530)) to perform the operations described in the present disclosure.

[0194] The processor (530) can control a series of processes to enable the device to operate according to the embodiments of the present disclosure described above. The processor (530) can control the overall operations of the device. Accordingly, the operations of the device can be interpreted as substantially executed by the processor (530). The processor (530) may include at least one processor. 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.

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

[0196] These 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 device, compact disc-ROM (CD-ROM), digital versatile discs (DVDs), or other forms of optical storage devices, magnetic cassettes. Alternatively, they may be stored in a memory composed of some or all of these. Additionally, each constituent memory may include multiple units.

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

Claims

1. A method performed by a session management function (SMF) in a wireless communication system, A step of receiving a subscription message to be notified of information regarding energy consumption associated with a PDU session from an energy information function (EIF); A step of obtaining information about the data volume associated with the PDU session from a User Plane Function (UPF) only if the PDU session is through a Third Generation Partnership Project (3GPP) access; and A method comprising the step of transmitting to the EIF a first notification message containing information for calculating energy consumption based on information regarding the acquired data volume. method.

2. In Paragraph 1, If the above PDU session is through a non-3GPP access, the method further comprises the step of transmitting a second notification message to the EIF containing a value of an uplink / downlink (UL / DL) data volume representing a value of 0. method.

3. In Paragraph 2, The above second notification does not include a gNB identifier (ID), method.

4. In Paragraph 1, The step of obtaining information about the data volume associated with the PDU session from the above UPF is: A step comprising transmitting an N4 request message to request the above UPF to report the required granularity data volume, method.

5. In Paragraph 1, The above first notification message further includes at least one of a gNB ID, an access type, or a UPF ID, method.

6. In Paragraph 1, The above subscription message includes at least one of an event ID indicating data usage or energy consumption calculation, an ID of the PDU session, a UE ID, and single-network slice selection auxiliary information (S-NSSAI). method.

7. As a device for a session management function (SMF) in a wireless communication system, Memory for storing instructions; and It includes at least one processor operably connected to the above memory, and The above commands are executable by the at least one processor to cause the device to execute operations, and the operations are: The operation of receiving a subscription message to be notified of information regarding energy consumption related to a PDU session from the Energy Information Function (EIF); An operation to obtain information about the data volume associated with the PDU session from the User Plane Function (UPF) only if the above PDU session is through a Third Generation Partnership Project (3GPP) access; and The operation of transmitting a first notification message to the EIF, the message including information for calculating energy consumption based on information regarding the acquired data volume, device.

8. In Paragraph 7, The above operations are: If the above PDU session is through non-3GPP access, the operation further includes transmitting a second notification message to the EIF containing the value of an uplink / downlink (UL / DL) data volume representing a value of 0. device.

9. In Paragraph 8, The above second notification does not include a gNB identifier (ID), device.

10. In Paragraph 7, The operation of obtaining information about the data volume associated with the PDU session from the above UPF is: The operation of transmitting an N4 request message to request the above UPF to report the required granularity data volume, device.

11. In Paragraph 7, The above first notification message further includes at least one of a gNB ID, an access type, or a UPF ID, device.

12. In Paragraph 7, The above subscription message includes at least one of an event ID indicating data usage or energy consumption calculation, an ID of the PDU session, a UE ID, and single-network slice selection auxiliary information (S-NSSAI). device.

13. A non-transient computer-readable storage medium for storing instructions, wherein the instructions are executable by at least one processor of the device to enable a device of a session management function (SMF) to execute operations, and the operations are: The operation of receiving a subscription message to be notified of information regarding energy consumption related to a PDU session from the Energy Information Function (EIF); An operation to obtain information about the data volume associated with the PDU session from the User Plane Function (UPF) only if the above PDU session is through a Third Generation Partnership Project (3GPP) access; and The operation of transmitting a first notification message to the EIF, the message including information for calculating energy consumption based on information regarding the acquired data volume, Non-transient computer-readable storage media.

14. In Paragraph 13, The above operations include at least one operation according to the method of any one of claims 2 to 6, Non-transient computer-readable storage media.

Images