Method and device for collecting energy consumption information on network slices
Patent Information
- Application Number
- PCT/KR2026/004833
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-09-12
- Filing Date
- 2026-03-26
- Publication Date
- 2026-10-01
Smart Images
Figure KR2026004833_01102026_PF_FP_ABST
Abstract
Description
Method and device for collecting energy consumption information on network slices
[0001] The present disclosure relates to a method and apparatus for collecting energy consumption information for a network slice.
[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 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 and apparatus for collecting energy consumption information for network slices.
[0009] According to one embodiment of the present invention, a method performed by a session management function (SMF) in a wireless communication system may include: receiving a protocol data unit (PDU) session establishment request message from a terminal, establishing a PDU session with the terminal, and transmitting a message accepting the establishment of the PDU session to the terminal; receiving a subscription request message for calculating energy consumption from an energy information function (EIF), which includes a terminal ID and single network slice selection assistance information (S-NSSAI); identifying that the S-NSSAI for the PDU session has been replaced with an alternative S-NSSAI; transmitting a message including the terminal ID and the alternative S-NSSAI to a user plane function (UPF) associated with the PDU session; receiving data usage information for the alternative S-NSSAI from the UPF; and transmitting a notification message including data usage information for the S-NSSAI and the alternative S-NSSAI to the EIF.
[0010] The step of receiving data usage information for the Alternative S-NSSAI from the above UPF can be repeated at specific time intervals.
[0011] The subscription request message for calculating the energy consumption above may further include an event ID indicating data usage.
[0012] The above notification message may further include the base station ID and the ID of the UPF.
[0013] According to another embodiment of the present invention, a method performed by an energy information function (EIF) in a wireless communication system may include: receiving a subscription request message for energy consumption information from a consumer network function (NF); obtaining information of a session management function (SMF) related to the subscription request message from a unified data management (UDM) or a unified data repository (UDR); transmitting a subscription request message for calculating energy consumption to the SMF, the message including a terminal ID and single network slice selection assistance information (S-NSSAI); and receiving a notification message from the SMF that includes data usage information for the S-NSSAI and an alternative S-NSSAI.
[0014] Network operators may introduce multiple Energy Information Functions (EIFs) (for example, introducing an EIF responsible for a specific region or an EIF responsible for one or more network slices), and accordingly, load balancing effects and increased reliability of energy information provision functions may occur.
[0015] Figure 1 shows the 5G system architecture.
[0016] Figure 2 illustrates a method of not performing ECI collection for Alternative S-NSSAI when changing slices.
[0017] Figure 3 shows the procedure for collecting ECI for Alternative S-NSSAI when changing slices.
[0018] Figure 4 is a diagram illustrating the procedure for PCF-based slice replacement notification and ECI subscription processing.
[0019] FIG. 5 is a diagram illustrating the structure of a user terminal (UE) according to one embodiment of the present invention.
[0020] FIG. 6 is a diagram illustrating a network entity according to an embodiment of the present invention.
[0021] Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the attached drawings. In this regard, it should be noted that identical components in the attached drawings are indicated by the same reference numerals whenever possible. Furthermore, detailed descriptions of known functions and configurations that may obscure the essence of the present invention will be omitted.
[0022] In describing the embodiments in this specification, technical details that are well known in the technical field to which this disclosure belongs and are not directly related to the present invention are omitted. This is intended to convey the essence of this disclosure more clearly without obscuring it by omitting unnecessary explanations.
[0023] For the same reason, some components in the attached drawings have been exaggerated, omitted, or schematically depicted. Additionally, the size of each component does not entirely reflect its actual dimensions. Identical or corresponding components in each drawing have been assigned the same reference number.
[0024] The advantages and features of the present disclosure and the methods for achieving them will become clear by referring to the embodiments described below in detail together with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below but may be implemented in various different forms. The embodiments provided are merely to ensure that the disclosure is complete and to fully inform those skilled in the art of the scope of the disclosure, and the disclosure is defined only by the scope of the claims. Throughout the specification, the same reference numerals refer to the same components.
[0025] Furthermore, in describing the present disclosure, if it is determined that a detailed description of related functions or configurations could unnecessarily obscure the essence of the present disclosure, such detailed description is omitted. Additionally, the terms described below are defined in consideration of their functions within the present disclosure, and these definitions may vary depending on the intentions or practices of the user or operator. Therefore, their definitions should be based on the content throughout this specification.
[0026] Hereinafter, a base station is an entity that performs resource allocation for terminals and may be at least one of a gNode B (gNB), eNode B (eNB), Node B, BS (Base Station), wireless access unit, base station controller, or a node on a network. A terminal may include a UE (User Equipment), MS (Mobile Station), cellular phone, smartphone, computer, or a multimedia system capable of performing communication functions. In this disclosure, a downlink (DL) refers to a wireless transmission path of a signal transmitted by a base station to a terminal, and an uplink (UL) refers to a wireless transmission path of a signal transmitted by a terminal to a base station. Furthermore, while LTE, LTE-A, or 5G systems may be described as examples below, embodiments of this disclosure may also 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 therein, and the 5G below may be a concept that includes existing LTE, LTE-A, and other similar services. In addition, the present disclosure may be applied to other communication systems with some modifications made at the discretion of a person with skilled technical knowledge, without significantly departing from the scope of the present disclosure.
[0027] At this time, it will be understood that each block of the process flow diagrams and combinations of the flow diagrams can be executed by computer program instructions. Since these computer program instructions can be loaded into the processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment, the instructions executed through the processor of the computer or other programmable data processing equipment create means to perform the functions described in the flow diagram 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 the function in a specific way, the instructions stored in computer-available or computer-readable memory can also produce a manufactured item containing the means of instruction to perform the function described in the flow diagram block(s). Since computer program instructions can be loaded onto a computer or other programmable data processing equipment, instructions that perform a series of operation steps on the computer or other programmable data processing equipment to create a process executed by the computer can also provide steps for executing the functions described in the flowchart block(s).
[0028] 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). It should also be noted that in some alternative execution examples, the functions mentioned in the blocks may occur out of order. For instance, two blocks described in succession may actually be executed substantially simultaneously, or the blocks may be executed in reverse order according to their corresponding functions.
[0029] In this embodiment, the term "part" refers to a software or hardware component, such as an FPGA or ASIC, and the "part" performs certain roles. However, the meaning of "part" is not limited to software or hardware. The "part" may be configured to reside in an addressable storage medium or configured to operate one or more processors. Accordingly, as an example, the "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 operate one or more CPUs within a device or secure multimedia card. In addition, in the embodiment, '~part' may include one or more processors.
[0030] Figure 1 shows the 5G system architecture.
[0031] A 5G mobile communication network consists of a 5G UE (user equipment, terminal) (100), a 5G RAN (radio access network) (110), a base station, a gNB (5G nodeB), an eNB (evolved nodeB, etc.), and a 5G core network. The 5G core network consists of NFs such as an AMF (access and mobility management function) (120) that provides mobility management functions for the UE, an SMF (session management function) (135) that provides session management functions, a UPF (user plane function) (130) that performs data delivery roles, 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, and a UDR (unified data repository) that stores data of various network functions (NFs) such as the 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 can transmit and receive application data through a PDU (protocol data unit) session created 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 (EIF) (or energy monitoring function) can be defined as a function that collects energy consumption information related to a UE, calculates energy consumption information at a UE, PDU session and / or Service Data Flow (or QoS Flow), NF node, base station node, etc., and exposes 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 to control the energy consumption of the UE by the consumer NF. 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 energy collection information for the UE.
[0051] Figure 2 illustrates a method of not performing ECI collection for Alternative S-NSSAI when changing slices.
[0052] Step 0. The UE sends a PDU session establishment request message to the SMF. If the SMF accepts the PDU session establishment, it may send a PDU session establishment acceptance message to the UE. Additionally, the SMF may perform registration for the corresponding UE / PDU Session by sending a registration request message to the UDM or UDR containing the UE ID (e.g., SUPI or IP address), S-NSSAI, DNN, access type, and SMF ID.
[0053] Step 1. A Consumer NF (e.g., NEF, AF, PCF, AMF, NWDAF, etc.) may send a subscription message to the EIF requesting energy consumption information for the UE. The message may include the following information.
[0054] -Event ID: Event ID representing energy consumption
[0055] -UE ID: May include terminal identifier information.
[0056] -S-NSSAI(s): When requesting energy consumption information for specific S-NSSAI(s) used by the terminal, the S-NSSAI may be included.
[0057] -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.
[0058] -IP Filter: When requesting energy consumption information for a specific traffic flow used by a terminal, the corresponding IP filter information (e.g., source IP address / port, destination IP / port, protocol type, etc.) may be included, and one or more IP filter information may be included.
[0059] -access type: If you intend to collect ECI for a specific access type, information about the access type may be included. Information about the access type may consist of 3GPP access, non-3GPP access, or both.
[0060] -reporting frequency: May include the frequency for receiving energy consumption information notifications.
[0061] -area information: When requesting energy consumption information for a specific area, the relevant area information may be included and may be provided in the form of TAI(s) or geographical information.
[0062] Step 2. The EIF may send a request message to the UDM or UDR 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 1. If the message received in Step 1 includes access type information, the corresponding access type information may be included.
[0063] Step 3. If the message received from the EIF contains UE ID, S-NSSAI, DNN, (additionally access type) and the corresponding SMF ID(s) are stored in the UDR, the UDM may include the corresponding SMF ID, UE location information (TAI and / or cell ID), PDU Session ID, S-NSSAI and / or DNN (additionally access type) for each SMF in a response message sent to the EIF.
[0064] Step 4. The EIF may send a response message for Step 1 to the Consumer NF (e.g., NEF). The message may include the following information. If the processing of the subscription request fails (or the subscription request is rejected), the remaining steps are not performed. If the processing of the subscription request succeeds (or the subscription request is accepted), Step 6 may be performed.
[0065] - (If the subscription request is processed successfully) result=success, subscription correlation ID, expiry time, first corresponding energy-related information report (e.g., UE location information (TAI and cell ID), gNB ID, UPF ID, SMF ID)
[0066] - (If processing of the subscription request fails, depending on the response message received from the UDM in Step 3) result=failed, cause = UE is not registered (or serving AMF for UE is not found)
[0067] - (If the subscription request fails to process, depending on the response message received from the UDM in Step 3) result=failed, no PDU session established for the UE
[0068] Step 5. The remaining ECI collection and exposure procedures may be performed. If the message received from the UDM in Step 3 contains SMF ID(s), the EIF may send a subscription request message for calculating energy consumption for each SMF.
[0069] If the EIF receives a subscription request message for energy consumption information in Step 1, it may include an event ID in a message sent to the SMF. For example, the message sent by the EIF to the SMF may include an event ID representing data usage or an event ID representing energy consumption calculation.
[0070] If the message received by the EIF in step 1 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.
[0071] If the message received by the EIF in step 1 contains access type information, the EIF may include the corresponding access type information in the message sent to the SMF.
[0072] 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.
[0073] When the SMF receives a subscription request message from the EIF, it may send a subscription request message to the corresponding UPF(s) to collect data volume (or information necessary to calculate ECI) for the targets included in the message (e.g., UE ID, S-NSSAI, DNN, IP Filter, App ID included in the message). The message may include time period information that serves as the reference interval for calculating data usage. Based on the target information received from the SMF, the UPF may collect data volume usage (or information necessary to calculate ECI) according to the time period and send an event notification message to the SMF.
[0074] In the notification message sent to the EIF based on the notification message received from the UPF, the SMF includes the UE ID, S-NSSAI, DNN, IP Filter, App ID, and list of data volume entries.<UL / DL data volume, UPF ID(s), gNB ID(s), reference time interval> It can include the back.
[0075] Reference to time interval represents information indicating the time at which a measurement was taken. For example, the reference to time interval can consist of timestamp information.
[0076] If the message received from the SMF contains gNB IDs and / or UPF ID(s) and there is no associated node-level energy consumption information or node-level data volume, the EIF may send a message to the OAM (Operation, Administration, Maintenance) to request such information. The EIF may include the gNB ID(s) and / or UPF ID(s) contained in the message received from the SMF in the request message sent to the OAM. Upon receiving a request message containing gNB IDs from the EIF, the OAM may include the data volume and energy consumption measured at specific intervals for the gNB IDs in the message sent to the EIF.
[0077] 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 a message sent to the EIF.
[0078] 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, the EIF 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.
[0079] - E_G,N = (Energy consumption of G) * (Data volume transmitted by N to G) / (Data volume transmitted by N)
[0080] When 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 Consumer NF, it can calculate the energy consumption information for G by adding E_G,N for all nodes N (e.g., UPF, N3IWF, gNB) that handle the UE's traffic.
[0081] 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.
[0082] Step 6. The S-NSSAI of the PDU Session is replaced with an Alternative S-NSSAI. This replacement may be performed when the S-NSSAI is congested or unavailable. The PDU session is associated with the S-NSSAI and the Alternative S-NSSAI, and uses the resources of the Alternative S-NSSAI.
[0083] Step 6a. If an SMF has a subscription for information (or data usage / volume information) for associated ECI calculation for a UE and an S-NSSAI, and the S-NSSAI of a PDU Session has been replaced with an Alternative S-NSSAI, the SMF may send a request message (or a message to temporarily suspend notifications) to the UPF(s) responsible for the PDU session to unsubscribe from the data volume / usage subscription for the existing S-NSSAI. The message may include a subscription correlation ID. Upon receiving the unsubscribe request message, the UPF may delete the corresponding subscription information and stop sending notification messages to the SMF.
[0084] If UPF receives a request message to temporarily suspend notifications, it may not send any further notification messages to SMF until the suspension is lifted.
[0085] In another embodiment, if the network slice for the PDU Session (or N4 session) in step 6 is replaced with an Alternative S-NSSAI, the UPF may include one or more of the following information in a notification message sent to the SMF.
[0086] - Subscription termination indication, cause: An indicator indicating subscription cancellation; may include information indicating subscription cancellation due to slice changes.
[0087] - UL / DL Data volume: UL / DL data volume may be included. It may also be included for Alternative S-NSSAI and S-NSSAI respectively. If the slice is replaced, a value of 0 may be included for S-NSSAI.
[0088] - UL / DL Data rate: May include the UL / DL data rate for the IP Filter and application identifier. May also be included for Alternative S-NSSAI and S-NSSAI respectively. In this case, the time window may also be included. If the slice is replaced, a value representing 0 may be included for the S-NSSAI.
[0089] - S-NSSAI: Replaced S-NSSAI may be included.
[0090] - Alternative S-NSSAI: If the network slice for the PDU Session (or N4 session) is replaced with an Alternative S-NSSAI, Alternative S-NSSAI information may be included.
[0091] - gNB ID or UE location information: May contain a gNB identifier or UE location information (TAI and cell information). May also be included for Alternative S-NSSAI and S-NSSAI respectively. If the slice has been replaced, a value indicating NULL may be included for S-NSSAI.
[0092] - UPF ID: May be included for each Alternative S-NSSAI and S-NSSAI. May contain a UPF identifier. If the slice has been replaced, a value indicating NULL may be included for the S-NSSAI.
[0093] Step 7. The SMF may include the following information in the notification message sent to the EIF for a PDU session associated with an Alternative S-NSSAI: PDU session ID or UE ID, DNN, S-NSSAI, updated data volume entry
[0094] The updated data volume entry may include an empty data volume entry (i.e., the data volume entry may not be included in the notification message, or information containing a separate value indicating an empty data volume entry may be included), or the following data volume entries. For example, <ul dl data volume of upf id(s)="NULL," gnb id="NULL">Information such as that may be included.
[0095] In another embodiment, if there exists a subscription to information (or data usage / volume information) for ECI calculation associated with the UE and S-NSSAI (i.e., if the EIF is subscribing to information from the SMF) and the S-NSSAI of the PDU Session is replaced with an Alternative S-NSSAI (i.e., if the S-NSSAI of the PDU session is changed / replaced), the SMF may send a message to the EIF to unsubscribe from the subscription to data usage / volume information for ECI calculation associated with the PDU Session. That is, the SMF may send a notification message (i.e., Nsmf_EventExposure_Notify) to the EIF, and the message may include one or more of the following parameters: subscription termination indication, cause (i.e., the cause for subscription termination may include that the S-NSSAI has changed or the PDU Session has changed, etc.), Event ID (event ID indicating data volume / usage), Notification Correlation Information, UE ID(s), and PDU Session ID(s).
[0096] If an SMF receives a message from a UPF containing a subscription termdination indication, it may unsubscribe from that UPF.
[0097] Step 8. The EIF can calculate the ECI for the UE based on the message received in Step 7 and include it in the notification message sent to the Consumer NF.
[0098] If the EIF contains a subscription termination indication in the message received in step 7, and if there is corresponding subscription information for one or more of the Notification correlation information, UE ID, and PDU Session ID included in the message received from the SMF in step 7, the EIF may terminate the subscription (e.g., delete the corresponding subscription information). Additionally, the EIF may include information indicating that the subscription to energy-related information for the PDU Session has been terminated in a notification message sent to the Consumer NF.
[0099] Step 9. The S-NSSAI of the PDU Session is replaced from the Alternative S-NSSAI to the existing S-NSSAI. This replacement may be performed when the S-NSSAI becomes available again or when congestion is resolved. The PDU session is associated with the S-NSSAI and uses the resources of the S-NSSAI.
[0100] Step 10. For a PDU session where the network slice has been replaced from Alternative S-NSSAI back to the original S-NSSAI, if an information subscription for the associated ECI calculation exists (or if a data usage subscription exists), the SMF may send a message to the UPF(s) responsible for the PDU session to request a data volume / usage subscription.
[0101] The message may include target information for the information subscription for the associated ECI calculation (e.g., UE ID, S-NSSAI, DNN, IP Filter, etc.) and an event ID (e.g., an event ID representing data usage or information for the ECI calculation).
[0102] When UPF receives a new subscription request message from SMF, it can send a notification message to SMF containing UL / DL data usage for the target for time T.
[0103] Alternatively, SMF may send a message to UPF to lift the notification suspension. In this case, the message to lift the notification suspension may include a subscription correlation ID and an indicator to lift the notification suspension. When UPF receives a message from SMF containing the indicator to lift the notification suspension, it may resume sending notification messages to SMF containing UL / DL data usage for the target for time T.
[0104] When UPF receives an N4 message or SBI message from SMF for a subscription (or for resuming notifications), it may include information (such as data volume) necessary for the ECI measured for the subscription during that time in a notification message sent to SMF.
[0105] UPF may include UL / DL Data volume, UL / DL data rate (in this case, a time window for calculating the data rate is provided), UE location information (TAI and cell ID) or gNB ID, and Reference to time interval (timestamp information) in the notification message sent to the address corresponding to the SMF or notification information.
[0106] 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).
[0107] UPF may include UL / DL Data volume, UL / DL data rate (in this case, a time window for calculating the data rate is provided), UE location information (TAI and cell ID) or gNB ID, and Reference to time interval (timestamp information) in the notification message sent to the address corresponding to the SMF or notification information.
[0108] Step 11. The SMF may include the following information in the notification message sent to the EIF for a PDU session associated with S-NSSAI: PDU session ID or UE ID, DNN, S-NSSAI, updated data volume entry
[0109] An updated data volume entry may include the following information.
[0110] < UL / DL Data volume of UPF = includes information received from UPF, serving UPF ID(s) = serving UPF identifier(s) of the PDU Session, serving gNB ID = serving gNB identifier(s) of the PDU Session > may be included.
[0111] Step 11b. The EIF can calculate the ECI for the UE based on the message received in 11 and include the calculated ECI in a notification message sent to the Consumer NF.
[0112] Figure 3 shows the procedure for collecting ECI for Alternative S-NSSAI when changing slices.
[0113] Step 0. The UE sends a PDU session establishment request message to the SMF. If the SMF accepts the PDU session establishment, it may send a PDU session establishment acceptance message to the UE. Additionally, the SMF may perform registration for the corresponding UE / PDU Session by sending a registration request message to the UDM or UDR containing the UE ID (e.g., SUPI or IP address), S-NSSAI, DNN, access type, and SMF ID.
[0114] Step 1. A Consumer NF (e.g., NEF, AF, PCF, AMF, NWDAF, etc.) may send a subscription message to the EIF requesting energy consumption information for the UE. The message may include the following information.
[0115] -Event ID: Event ID representing energy consumption
[0116] -UE ID: May include terminal identifier information.
[0117] -S-NSSAI(s): When requesting energy consumption information for specific S-NSSAI(s) used by the terminal, the S-NSSAI may be included.
[0118] -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.
[0119] -IP Filter: When requesting energy consumption information for a specific traffic flow used by a terminal, the information may include the corresponding IP filter (e.g., source IP address / port, destination IP / port, protocol type, etc.), and one or more IP filter information may be included.
[0120] -access type: If you intend to collect ECI for a specific access type, information about the access type may be included. Information about the access type may consist of 3GPP access, non-3GPP access, or both.
[0121] -reporting frequency: May include the frequency for receiving energy consumption information notifications.
[0122] -area information: When requesting energy consumption information for a specific area, the relevant area information may be included and may be provided in the form of TAI(s) or geographical information.
[0123] Step 2. The EIF may send a request message to the UDM or UDR 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 1. If the message received in Step 1 includes access type information, the corresponding access type information may be included.
[0124] Step 3. If the UDM receives a message from the EIF containing UE ID, S-NSSAI, DNN, and (additionally access type) and the corresponding SMF ID(s) are stored in the UDR, the UDM may include the corresponding SMF ID, UE location information (TAI and / or cell ID), PDU Session ID, S-NSSAI, and / or DNN (additionally access type) for each SMF in a response message sent to the EIF.
[0125] Step 4. The EIF may send a response message for Step 1 to the Consumer NF (e.g., NEF). The message may include the following information. If the processing of the subscription request fails (or the subscription request is rejected), the remaining steps are not performed. If the processing of the subscription request succeeds (or the subscription request is accepted), Step 6 may be performed.
[0126] - (If the subscription request is processed successfully) result=success, subscription correlation ID, expiry time, first corresponding energy-related information report (e.g., UE location information (TAI and cell ID), gNB ID, UPF ID, SMF ID)
[0127] - (If processing of the subscription request fails, depending on the response message received from the UDM in Step 3) result=failed, cause = UE is not registered (or serving AMF for UE is not found)
[0128] - (If the subscription request fails to process, depending on the response message received from the UDM in Step 3) result=failed, no PDU session established for the UE
[0129] Step 5. The remaining ECI collection and exposure procedures may be performed. If the message received from the UDM in Step 3 contains SMF ID(s), the EIF may send a subscription request message for calculating energy consumption for each SMF.
[0130] If the EIF receives a subscription request message for energy consumption information in Step 1, it may include an event ID in a message sent to the SMF. For example, the message sent by the EIF to the SMF may include an event ID representing data usage or an event ID representing energy consumption calculation.
[0131] If the message received by the EIF in step 1 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.
[0132] If the message received by the EIF in step 1 contains access type information, the EIF may include the corresponding access type information in the message sent to the SMF.
[0133] 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.
[0134] When the SMF receives a subscription request message from the EIF, it may send a subscription request message to the corresponding UPF(s) to collect data volume (or information necessary to calculate ECI) for the targets included in the message (e.g., UE ID, S-NSSAI, DNN, IP Filter, App ID included in the message). The message may include time period information that serves as the base price for calculating data usage. Based on the target information received from the SMF, the UPF may collect data volume usage (or information necessary to calculate ECI) according to the time period and send an event notification message to the SMF.
[0135] In the notification message sent to the EIF based on the notification message received from the UPF, the SMF includes the UE ID, S-NSSAI, DNN, IP Filter, App ID, and list of data volume entries.<UL / DL data volume, UPF ID(s), gNB ID(s), reference time interval> It can include the back.
[0136] Reference to time interval represents information indicating the time at which a measurement was taken. For example, the reference to time interval can consist of timestamp information.
[0137] If the message received from the SMF contains gNB IDs and / or UPF ID(s) and there is no associated node-level energy consumption information or node-level data volume, the EIF may send a message to the OAM (Operation, Administration, Maintenance) to request such information. The EIF may include the gNB ID(s) and / or UPF ID(s) contained in the message received from the SMF in the request message sent to the OAM. Upon receiving a request message containing gNB IDs from the EIF, the OAM may include the data volume and energy consumption measured at specific intervals for the gNB IDs in the message sent to the EIF.
[0138] 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 a message sent to the EIF.
[0139] 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, the EIF 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.
[0140] - E_G,N = (Energy consumption of G) * (Data volume transmitted by N to G) / (Data volume transmitted by N)
[0141] When 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 Consumer NF, it can calculate the energy consumption information for G by adding E_G,N for all nodes N (e.g., UPF, N3IWF, gNB) that handle the UE's traffic.
[0142] 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.
[0143] Step 6. The S-NSSAI of the PDU Session is replaced with an Alternative S-NSSAI. This replacement may be performed when the S-NSSAI is congested or unavailable. The PDU session is associated with the S-NSSAI and the Alternative S-NSSAI, and uses the resources of the Alternative S-NSSAI.
[0144] Step 6a. If an information subscription for ECI computation exists for a UE ID (or DNN, IP Filter, etc.) and a slice of the PDU session for the UE ID (or DNN) is replaced from S-NSSAI to Alternative S-NSSAI, the SMF may send a request message to the UPF(s) responsible for the PDU session to perform the information subscription for ECI computation, data volume / usage for the UE ID and Alternative S-NSSAI.
[0145] UPF(s) may include the UE ID, Alternative S-NSSAI (additionally, DNN), and time interval in a notification message sent to the SMF when the message received from the SMF includes the UE ID, Alternative S-NSSAI (additionally, DNN), and time interval, or in another embodiment when the S-NSSAI for a PDU session is changed to an alternative S-NSSAI, by measuring the UL / DL data volume / usage for the UE ID and Alternative S-NSSAI (additionally, DNN) at the time interval. The message may include the following information.
[0146] - UL / DL Data volume: UL / DL data volume may be included. It may also be included for Alternative S-NSSAI and S-NSSAI respectively. If the slice is replaced, a value of 0 may be included for S-NSSAI.
[0147] - UL / DL Data rate: May include the UL / DL data rate for the IP Filter and application identifier. May also be included for Alternative S-NSSAI and S-NSSAI respectively. In this case, the time window may also be included. If the slice is replaced, a value representing 0 may be included for the S-NSSAI.
[0148] - S-NSSAI: Replaced S-NSSAI may be included.
[0149] - Alternative S-NSSAI: If the network slice for the PDU Session (or N4 session) is replaced with an Alternative S-NSSAI, Alternative S-NSSAI information may be included.
[0150] - gNB ID or UE location information: May contain a gNB identifier or UE location information (TAI and cell information). May also be included for Alternative S-NSSAI and S-NSSAI respectively. If the slice has been replaced, a value indicating NULL may be included for S-NSSAI.
[0151] - UPF ID: May be included for each Alternative S-NSSAI and S-NSSAI. May contain a UPF identifier. If the slice has been replaced, a value indicating NULL may be included for the S-NSSAI.
[0152] When UPF receives an N4 message or an SBI message from SMF, it may include information (such as data volume) necessary for the ECI measured during that time period in a notification message sent to SMF, based on the time information contained in the message.
[0153] UPF may include UL / DL Data volume, UL / DL data rate (in this case, a time window for calculating the data rate is provided), UE location information (TAI and cell ID) or gNB ID, and Reference to time interval (timestamp information) in the notification message sent to the address corresponding to the SMF or notification information.
[0154] 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).
[0155] Step 7. The SMF may include the following information in the notification message sent to the EIF for the PDU session associated with the Alternative S-NSSAI: PDU session ID or UE ID, DNN, S-NSSAI, Alternative S-NSSAI, updated data volume entry. The updated data volume entry may include the notification message received by the SMF from the UPF in Step 6.
[0156] Step 8. The EIF may calculate the ECI for the UE based on the message received in Step 7 and include it in a notification message sent to the Consumer NF. When the EIF calculates the ECI information for the UE ID, it may calculate the ECI by taking into account all data volume information used by the UE for all slices (e.g., S-NSSAI and Alternative S-NSSAI). For example, if the EIF has an ECI subscription for UE ID and S-NSSAI, and the notification message received from the SMF for the PDU Session for the UE ID and S-NSSAI contains the UE ID, UL / DL data volume, and Alternative S-NSSAI, the UL / DL data volume contained in the notification message may not be considered when calculating the ECI for the UE and S-NSSAI (for example, when calculating the UL / DL data volume used by the UE for S-NSSAI, the EIF may not include the UL / DL data volume contained in the notification message containing Alternative S-NSSAI from the SMF). If the Consumer NF is not an AF (or AMF, NEF) (for example, if it is a PCF or NWDAF), the EIF may not consider the UL / DL data volume for Alternative S-NSSAI when calculating the ECI for S-NSSAI for the UE. Additionally, if the Consumer NF is not an AF and the EIF receives a notification message from the SMF containing an Alternative S-NSSAI, the EIF may include the Alternative S-NSSAI and / or the ECI for the Alternative S-NSSAI and the UE (separate from the existing ECI for the UE and S-NSSAI) in the notification message sent to the Consumer NF.
[0157] If the Consumer NF is AF (or AMF, NEF), the EIF may consider the UL / DL data volume for the Alternative S-NSSAI when calculating the ECI for the S-NSSAI for the UE. Additionally, if the Consumer NF is AF and receives a notification message containing the Alternative S-NSSAI from the SMF, the EIF may include the ECI for the UE and the Alternative S-NSSAI along with the existing S-NSSAI in the notification message sent to the Consumer NF.
[0158] Step 9. The S-NSSAI of the PDU Session is replaced from the Alternative S-NSSAI to the existing S-NSSAI. This replacement may be performed when the S-NSSAI becomes available again or when congestion is resolved. The PDU session is associated with the S-NSSAI and uses the resources of the S-NSSAI.
[0159] Step 10. For a PDU session in which the network slice has been replaced from Alternative S-NSSAI back to the original S-NSSAI, if an information subscription for the associated ECI calculation exists (or if a data usage subscription exists), the SMF may send a message to the UPF(s) responsible for the PDU session to release the data volume / usage subscription for Alternative S-NSSAI.
[0160] Meanwhile, if a data volume / usage subscription for the UE ID and S-NSSAI exists, the UPF can send the corresponding notification message to the SMF.
[0161] Step 11. The SMF may include the following information in the notification message sent to the EIF for a PDU session associated with S-NSSAI: PDU session ID or UE ID, DNN, S-NSSAI, updated data volume entry
[0162] The updated data volume entry may include data volume information for the UE ID and S-NSSAI received by the SMF from the UPF in step 10.
[0163] Step 11b. The EIF can calculate the ECI for the UE based on the message received in 11 and include the calculated ECI in a notification message sent to the Consumer NF.
[0164] Figure 4 is a diagram illustrating the procedure for PCF-based slice replacement notification and ECI subscription processing.
[0165] Step 0-Step 5. Steps 0-5 described above can be performed through Fig. 2.
[0166] Step 5a. The EIF may send a PCF discovery request message to the binding support function (BSF) to receive the PCF Address for the UE ID, S-NSSAI, and DNN received in Step 1.
[0167] The BSF can include the PCF ID / address in the response message sent to the EIF.
[0168] Step 5b. The EIF may send a subscription request message for a network slice replacement event to the PCF based on the PCF address received from the BSF in Step 5a. The subscription request message may include a UE ID and an S-NSSAI. If the PCF is an AM PCF, the PCF may send a subscription request for the network slice replacement to the SM PCF (or SMF) responsible for the PDU session.
[0169] Step 5c. Step 5b described above can be performed through Fig. 2.
[0170] Step 6. Step 6 described above through Fig. 2 is performed.
[0171] Step 7. If the PCF changes the S-NSSAI of the PDU Session (i.e., receives a notification message from the SMF or SM PCF containing an Alternative S-NSSAI along with an indication that the slice has been replaced), the PCF may send a message to the EIF containing the UE ID, S-NSSAI, Alternative S-NSSAI, and indication of network slice replacement.
[0172] Step 8. If the EIF has an Alternative S-NSSAI and / or indication of network slice replacement in the message received from the PCF in Step 7, and there is an ECI subscription for the UE ID and S-NSSAI included in the message received from the PCF, and there is an event subscribed to to receive information for calculating the ECI for the UE ID and S-NSSAI from the SMF for the subscription, the EIF may send a message to the SMF to unsubscribe.
[0173] The message may include a subscription correlation ID.
[0174] Step 8b. The EIF may transmit the ECI for the UE to the Consumer NF. The ECI for the UE does not include the energy usage (or data volume) consumed by the UE through the Alternative S-NSSAI.
[0175] Step 9. Step 9 described above can be performed through Fig. 2.
[0176] Step 10. If the network slice of the PDU Session is changed from the Alternative S-NSSAI back to the original S-NSSAI, the PCF may send a message to the EIF containing the UE ID, S-NSSAI, and indication of the PDU session transferred back to the original network slice.
[0177] Step 11. If the EIF has an S-NSSAI and / or indication of a PDU session transferred back to the original network slice in the message received from the PCF in Step 10, and there is an ECI subscription for the UE ID and S-NSSAI included in the message received from the PCF (i.e., a subscription for the Consumer NF's ECI), and there are no events subscribed to for receiving information for calculating the ECI for the UE ID and S-NSSAI from the SMF for the subscription, the EIF may send a message to the SMF to request the subscription. The message may include the UE ID, S-NSSAI, DNN, etc. included in the Consumer NF's subscription for the ECI.
[0178] Step 12. SMF may send a notification message to EIF regarding the subscription received in Step 11. Based on the notification message received from SMF, EIF may send a notification message to Consumer NF containing an ECI for the UE.
[0179] FIG. 5 is a diagram illustrating the structure of a user terminal (UE) according to one embodiment of the present invention.
[0180] Referring to FIG. 5, the user terminal may include a transceiver (510), a control unit (520), and a storage unit (530). In the present invention, the control unit may be defined as a circuit or an application-specific integrated circuit or at least one processor.
[0181] The transmitting and receiving unit (510) can transmit and receive signals with other network entities. The transmitting and receiving unit (510) can, for example, transmit a PDU session establishment request message to an SMF.
[0182] The control unit (520) can control the overall operation of the user terminal according to the embodiment proposed in the present invention.
[0183] The storage unit (530) can store at least one of the information transmitted and received through the transmission and reception unit (510) and the information generated through the control unit (520). For example, the storage unit (530) can store information about PDU sessions and network slices.
[0184] FIG. 6 is a diagram illustrating a network entity according to an embodiment of the present invention.
[0185] The network entity illustrated in FIG. 6 may be composed of one of the various types of network entities disclosed in the present invention, for example, EIF, OAM, BSF, NRF, UPF, AMF, SMF, PCF, UDM, NSSF, NWDAF, NSACF, etc.
[0186] Referring to FIG. 6, the network entity may include a transceiver (610), a control unit (620), and a storage unit (630). In the present invention, the control unit may be defined as a circuit or an application-specific integrated circuit or at least one processor.
[0187] The transmitting and receiving unit (610) can transmit and receive signals with other network entities. The transmitting and receiving unit (610) can receive, for example, request messages for various information from a user terminal, a base station, or other network entities.
[0188] The control unit (620) can control the overall operation of a network entity according to an embodiment proposed in the present invention. For example, the control unit (620) can control the network entity to perform ECI calculation according to an embodiment disclosed in the present invention.
[0189] The storage unit (630) can store at least one of the information transmitted and received through the transmission and reception unit (610) and the information generated through the control unit (620).
[0190] It should be noted that the configuration diagrams, exemplary diagrams of control / data signal transmission and reception methods, and exemplary diagrams of operation procedures illustrated in FIGS. 1 to 6 are not intended to limit the scope of the embodiments of the present disclosure. That is, all components, entities, or steps of operation described in FIGS. 1 to 6 should not be interpreted as essential components for implementing the disclosure, and may be implemented to the extent that the essence of the disclosure is not compromised even if only some components are included.
[0191] The operations of the embodiments described above can be realized by providing a memory device storing the corresponding program code in any component within the device. That is, the control unit within the device can execute the operations described above by reading the program code stored in the memory device by a processor or a CPU (Central Processing Unit) and executing it.
[0192] Although the various embodiments described in this specification are described independently of one another, this does not mean that each embodiment must be implemented individually, and two or more embodiments may be combined and implemented together. Accordingly, those skilled in the art will understand that some features or components of the various embodiments may be combined and applied within the scope of the invention.
[0193] The embodiments of the invention disclosed in this specification and drawings are provided merely as specific examples to facilitate the explanation of the technical content of the invention and to aid in understanding the invention, and are not intended to limit the scope of the invention. It is obvious to those skilled in the art that other variations based on the technical concept of the invention are possible in addition to the embodiments disclosed herein.
Claims
1. A method performed by an SMF (session management function) in a wireless communication system, A step of receiving a PDU (protocol data unit) session establishment request message from a terminal, establishing a PDU session with the terminal, and transmitting a PDU session establishment acceptance message to the terminal; A step of receiving a subscription request message for calculating energy consumption from an EIF (energy information function), the message including a terminal ID and S-NSSAI (single network slice selection assistance information); A step of identifying that the S-NSSAI for the above PDU session has been replaced with an Alternative S-NSSAI; A step of transmitting a message including the terminal ID and the Alternative S-NSSAI to a UPF (user plane function) associated with the above PDU session; A step of receiving data usage information for the Alternative S-NSSAI from the above UPF; and A method comprising the step of transmitting a notification message containing data usage information for the S-NSSAI and the Alternative S-NSSAI to the EIF.
2. In Paragraph 1, A method in which the step of receiving data usage information for the Alternative S-NSSAI from the above UPF is repeated at a specific time interval.
3. In Paragraph 1, The subscription request message for calculating the above energy consumption is, A method that further includes an event ID indicating data usage.
4. In Paragraph 1, The above notification message further includes a base station ID and an ID of the UPF, a method.
5. In a method performed by the energy information function (EIF) in a wireless communication system, A step of receiving a subscription request message for energy consumption information from a consumer network function (NF); A step of obtaining information of an SMF (session management function) related to the subscription request message from a UDM (unified data management) or UDR (unified data repository); A step of transmitting a subscription request message for calculating energy consumption to the above SMF, the message including a terminal ID and S-NSSAI (single network slice selection assistance information); and A method comprising the step of receiving a notification message from the above SMF that includes data usage information for the S-NSSAI and Alternative S-NSSAI.
6. In Paragraph 5, A method in which the step of receiving the notification message from the above SMF is repeated at a specific time interval.
7. In Paragraph 5, The subscription request message for calculating energy consumption transmitted to the above SMF is, A method that further includes an event ID indicating data usage.
8. In Paragraph 5, The above notification message further includes a base station ID and a UPF (user plane function) ID, a method.
9. In a session management function (SMF) operating in a wireless communication system, Transmitter / receiver; and It includes a control unit, The above control unit is, Upon receiving a PDU (protocol data unit) session establishment request message from a terminal, a PDU session with said terminal is established, and a PDU session establishment acceptance message is sent to said terminal. Receives a subscription request message for calculating energy consumption from the EIF (energy information function), including a terminal ID and S-NSSAI (single network slice selection assistance information), and Identify that the S-NSSAI for the above PDU session has been replaced with an Alternative S-NSSAI, and A message including the terminal ID and the Alternative S-NSSAI is transmitted as a UPF (user plane function) associated with the above PDU session, and Receive data usage information for the Alternative S-NSSAI from the above UPF, and An SMF configured to transmit a notification message containing data usage information for the S-NSSAI and the Alternative S-NSSAI to the EIF.
10. In Paragraph 9, SMF in which the reception of data usage information for the Alternative S-NSSAI from the above UPF is repeated at a specific time interval.
11. In Paragraph 9, The subscription request message for calculating the above energy consumption is, SMF, which further includes an event ID indicating data usage.
12. In Paragraph 9, The above notification message is an SMF that further includes a base station ID and the ID of the UPF.
13. In an energy information function (EIF) operating in a wireless communication system, Transmitter / receiver; and It includes a control unit, The above control unit is, Receive a subscription request message for energy consumption information from a consumer network function (NF), and Information regarding the session management function (SMF) related to the subscription request message is obtained from the unified data management (UDM) or unified data repository (UDR), and To the above SMF, a subscription request message for calculating energy consumption, including a terminal ID and S-NSSAI (single network slice selection assistance information), is transmitted, and An EIF configured to receive a notification message from the above SMF containing data usage information for the S-NSSAI and Alternative S-NSSAI.
14. In Paragraph 13, The subscription request message for calculating energy consumption transmitted to the above SMF is, EIF, which further includes an event ID indicating data usage.
15. In Paragraph 13, The above notification message is an EIF that further includes a base station ID and a UPF (user plane function) ID.