Method and apparatus for supporting energy usage monitoring in wireless communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. According to the present disclosure, a first entity: receives, from a second entity, a request message for collecting information regarding energy consumption; transmits a message for energy monitoring to a session management function (SMF) entity; receives a response message for the energy monitoring from the SMF entity; and transmits a response message including an energy monitoring result as a response to the request message for collecting the information regarding the energy consumption. Therefore, a method for efficiently monitoring energy usage in a wireless communication system may be provided.

Description

Method and device for supporting energy usage monitoring in wireless communication systems

[0001] The present disclosure relates to a method and apparatus for providing energy usage monitoring in a wireless communication system.

[0002] 5G mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, and can be implemented not only in the sub-6GHz frequency band such as 3.5 gigahertz (3.5GHz), but also in the ultra-high frequency band called millimeter wave (mmWave) such as 28GHz and 39GHz ('Above 6GHz'). In addition, for 6G mobile communication technology, which is called the system after 5G communication (Beyond 5G), implementation in the terahertz band (for example, the 3 terahertz (3THz) band at 95GHz) is being considered to achieve a transmission speed that is 50 times faster than 5G mobile communication technology and an ultra-low latency time that is reduced to one-tenth.

[0003] In the early stages of 5G mobile communication technology, the goal is to support services and satisfy performance requirements for enhanced Mobile Broadband (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and massive Machine-Type Communications (mMTC). These include beamforming and massive MIMO to mitigate path loss of radio waves in ultra-high frequency bands and increase the transmission distance of radio waves, support for various numerologies (such as operation of multiple subcarrier intervals) and dynamic operation of slot formats for efficient use of ultra-high frequency resources, initial access technology to support multi-beam transmission and wideband, definition and operation of BWP (Bidth Part), new channel coding methods such as LDPC (Low Density Parity Check) codes for large-capacity data transmission and Polar Code for reliable transmission of control information, and L2 pre-processing (L2). Standardization has been made for network slicing, which provides dedicated networks specialized for specific services, and pre-processing.

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

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

[0006] Once these 5G mobile communication systems are commercialized, an explosive increase in connected devices will be connected to the communication network, necessitating enhanced functionality and performance of 5G mobile communication systems and integrated operation of these connected devices. To this end, new research will be conducted on improving 5G performance and reducing complexity, supporting AI services, supporting metaverse services, and drone communications by utilizing eXtended Reality (XR), Artificial Intelligence (AI), and Machine Learning (ML) to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR).

[0007] In addition, the development of these 5G mobile communication systems includes new waveforms to ensure coverage in the terahertz band of 6G mobile communication technology, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), Array Antenna, and Large Scale Antenna, metamaterial-based lenses and antennas to improve the coverage of terahertz band signals, high-dimensional spatial multiplexing technology using Orbital Angular Momentum (OAM), Reconfigurable Intelligent Surface (RIS) technology, as well as full duplex technology to improve the frequency efficiency and system network of 6G mobile communication technology, satellite, AI (Artificial Intelligence) from the design stage and AI-based communication technology that realizes system optimization by internalizing end-to-end AI support functions, and ultra-high-performance communication and computing resources to provide services with complexity that exceeds the limits of terminal computing capabilities. It can serve as a basis for the development of next-generation distributed computing technologies that can be realized by utilizing them.

[0008] An object of the present invention is to propose a method for monitoring energy usage in a 5G system.

[0009] According to one embodiment of the present disclosure, a method performed by a first entity for collecting information on energy consumption in a wireless communication system may include receiving a request message for collecting information on energy consumption from a second entity, transmitting a message for energy monitoring to a session management function (SMF) entity, receiving a response message for the energy monitoring from the SMF entity, and transmitting a response message including a result of energy monitoring as a response to the request message for collecting information on energy consumption.

[0010] Meanwhile, according to an embodiment of the present disclosure, a method performed by a session management function (SMF) entity in a wireless communication system may include a step of receiving a message for energy monitoring from a first entity for collecting information on energy consumption, a step of transmitting the message for energy monitoring to a user plane function (UPF), and a step of transmitting a response message for energy monitoring to the first entity when a response message is received from the UPF in response to the message for energy monitoring.

[0011] Meanwhile, according to an embodiment of the present disclosure, a first entity for collecting information on energy consumption in a wireless communication system may include a control unit that receives a request message for collecting information on energy consumption from a transceiver and a second entity through the transceiver, transmits a message for energy monitoring to a session management function (SMF) entity through the transceiver, receives a response message for the energy monitoring from the SMF entity through the transceiver, and transmits a response message including an energy monitoring result as a response to the request message for collecting information on energy consumption through the transceiver.

[0012] Meanwhile, in a wireless communication system according to an embodiment of the present disclosure, a session management function (SMF) entity may include a control unit that receives a message for energy monitoring from a first entity for collecting information on a transceiver and energy consumption through the transceiver, transmits a message for energy monitoring to a user plane function (UPF) through the transceiver, and, when a response message is received from the UPF in response to the message for energy monitoring, transmits a response message for energy monitoring to the first entity through the transceiver.

[0013] According to an embodiment of the present invention, through the energy usage monitoring method proposed in the present invention, a business operator can provide a function to monitor energy usage occurring in a contract network to a third party.

[0014] FIG. 1 is a diagram illustrating a 5G system architecture according to one embodiment of the present disclosure.

[0015] FIG. 2 is a diagram illustrating a method for performing energy monitoring in a UPF according to an embodiment of the present disclosure.

[0016] FIG. 3 is a diagram illustrating a method for performing energy monitoring in a RAN according to an embodiment of the present disclosure.

[0017] FIG. 4 is a diagram illustrating a method for performing energy monitoring for each S-NSSAI or DNN according to one embodiment of the present disclosure.

[0018] FIG. 5a is a diagram illustrating an energy monitoring method for QoS Flow(s) according to one embodiment of the present disclosure.

[0019] FIG. 5b is a diagram illustrating an energy monitoring method for QoS Flow(s) according to one embodiment of the present disclosure.

[0020] FIG. 6 is a block diagram illustrating the structure of an entity performing a network function (NF) according to one embodiment of the present disclosure.

[0021] FIG. 7 is a block diagram illustrating the structure of a device according to an embodiment of the present disclosure.

[0022] Hereinafter, preferred embodiments of the present disclosure will be described in detail with reference to the attached drawings. It should be noted that, where possible, identical components are represented by identical reference numerals throughout the attached drawings. Furthermore, detailed descriptions of well-known functions and configurations that may obscure the gist of the present disclosure will be omitted.

[0023] In describing the embodiments of this disclosure, descriptions of technical details that are well known in the technical field to which this disclosure pertains and are not directly related to this disclosure will be omitted. This is to more clearly convey the gist of this disclosure without obscuring it by omitting unnecessary explanations.

[0024] For the same reason, some components in the attached drawings are exaggerated, omitted, or schematically depicted. Furthermore, the dimensions of each component do not entirely reflect its actual size. Identical or corresponding components in each drawing are assigned the same reference numbers.

[0025] The advantages and features of the present disclosure, and methods for achieving them, will become clearer with reference to the embodiments described below in detail together with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below and may be implemented in various different forms. These embodiments are provided solely to ensure that the present disclosure is complete and to fully inform those skilled in the art of the scope of the disclosure, and the present disclosure is defined only by the scope of the claims. Like reference numerals designate like elements throughout the specification.

[0026] At this time, it will be understood that each block of the processing flowchart drawings and combinations of the flowchart drawings can be performed by computer program instructions. These computer program instructions can be installed in a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment, so that the instructions executed by the processor of the computer or other programmable data processing equipment create a means for performing the functions described in the flowchart block(s). These computer program instructions can also be stored in a computer-available or computer-readable memory that can direct a computer or other programmable data processing equipment to implement the functions in a specific manner, so that the instructions stored in the computer-available or computer-readable memory can also produce a manufactured item that includes an instruction means for performing the functions described in the flowchart block(s). Since the computer program instructions may be installed on a computer or other programmable data processing device, a series of operational steps may be performed on the computer or other programmable data processing device to create a computer-executable process, and the instructions that cause the computer or other programmable data processing device to perform the steps for performing the functions described in the flowchart block(s) may also provide steps for performing the functions described in the flowchart block(s).

[0027] Additionally, each block may represent a module, segment, or portion of code that contains one or more executable instructions for performing a specific logical function(s). It should also be noted that in some alternative implementation examples, the functions described in the blocks may occur out of order. For example, two blocks depicted in succession may actually be executed substantially concurrently, or the blocks may sometimes be executed in reverse order, depending on their respective functions.

[0028] Here, the term '~ unit' used in the present embodiment means software or hardware components such as FPGA (Field Programmable Gate Array) or ASIC (Application Specific Integrated Circuit), and the '~ unit' performs certain roles. However, the '~ unit' is not limited to software or hardware. The '~ unit' may be configured to be on an addressable storage medium and may be configured to play one or more processors. Therefore, as an example, the '~ unit' includes components such as software components, object-oriented software components, class components, and task components, processes, functions, properties, 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 '~ units' may be combined into a smaller number of components and '~ units' or further separated into additional components and '~ units'. Additionally, components and '~parts' may be implemented to regenerate one or more CPUs within a device or secure multimedia card.

[0029] Hereinafter, the base station is an entity that performs resource allocation of a terminal, and may be at least one of a Node B, a BS (Base Station), an eNB (eNode B), a gNB (gNode B), a wireless access unit, a base station controller, or a node on a network. The terminal may include a UE (User Equipment), an MS (Mobile Station), a 5G UE, a cellular phone, a smartphone, a computer, or a multimedia system capable of performing a communication function. In addition, the embodiments of the present disclosure may be applied to other communication systems having a similar technical background or channel type to the embodiments of the present disclosure described below. In addition, the embodiments of the present disclosure may be applied to other communication systems with some modifications without significantly departing from the scope of the present disclosure at the discretion of a person having skilled technical knowledge. For example, the 5th generation mobile communication technology (5G, new radio, NR) developed after LTE-A may be included here, and the 5G below may also 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 within a scope that does not significantly deviate from the scope of the present disclosure, as judged by a person having skilled technical knowledge.

[0030] In the following description, terms used to identify connection nodes, terms referring to network entities or network functions (NFs), terms referring to messages, terms referring to interfaces between network objects, terms referring to various identification information, etc. are provided as examples for convenience of explanation. Therefore, the present disclosure is not limited to the terms described below, and other terms referring to objects having equivalent technical meanings may be used.

[0031] For convenience of explanation below, some terms and names defined in the 3rd generation partnership project (3GPP) LTE (long term evolution) standard and / or 3GPP NR (new radio) standard may be used. However, the present disclosure is not limited to the above terms and names, and can be equally applied to systems conforming to other standards.

[0032] FIG. 1 illustrates a 5G system architecture according to one embodiment of the present disclosure.

[0033] A 5G mobile communication network is composed of a 5G user equipment (UE) (100), a 5G radio access network (RAN, base station, gNB (5g nodeB), eNB (evolved nodeB, etc.) (110), and a 5G core network. The 5G core network may be composed of NFs such as an access and mobility management function (AMF) (120) that provides a mobility management function of the UE, a session management function (SMF) (135) that provides a session management function, a user plane function (UPF) (130) that performs a data transfer role, a policy control function (PCF) (140) that provides a policy control function, a unified data management (UDM) (145) that provides a data management function such as subscriber data and policy control data, and a unified data repository (UDR) that stores data of various network functions (NFs) such as UDM.

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

[0035] - N1: Reference point between UE (100) and AMF (120)

[0036] - N2: Reference point between (R)AN(110) and AMF(120)

[0037] - N3: Reference point between (R)AN(110) and UPF(130)

[0038] - N4: Reference point between SMF (135) and UPF (130)

[0039] - N5: Reference point between PCF (140) and AF (150)

[0040] - N6: Reference point between UPF (130) and DN (155)

[0041] - N7: Reference point between SMF (135) and PCF (140)

[0042] - N8: Reference point between UDM (145) and AMF (120)

[0043] - N9: Reference point between two core UPFs (130)

[0044] - N10: Reference point between UDM (145) and SMF (135)

[0045] - N11: Reference point between AMF (120) and SMF (135)

[0046] - N12: Reference point between AMF (120) and authentication server function (AUSF)

[0047] - N13: Reference point between UDM(145) and AUSF

[0048] - N14: Reference point between two AMFs (120)

[0049] - N15: For non-roaming scenarios, reference point between PCF (140) and AMF (120), for roaming scenarios, reference point between PCF (140) and AMF (120) within the visited network.

[0050] In 5G systems, network slicing technology refers to the technology and architecture 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 meet the specialized requirements of services / applications. At this time, network slices are identified by an identifier called single-network slice selection assistance information (S-NSSAI). 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 through one S-NSSAI (e.g., network slice) among the received slice sets.

[0051] According to one embodiment of the present disclosure, a method for monitoring energy usage in a 5G system is proposed. When energy usage monitoring is activated, an energy monitoring function can collect energy usage information from target entities (e.g., User Equipments (UEs), Radio Access Networks (RANs), and / or User Plane Functions (UPFs). In this case, the energy monitoring function can be activated for each terminal or each network slice.

[0052] Meanwhile, FIG. 2 is a diagram illustrating a method for performing energy monitoring in UPF according to one embodiment of the present disclosure.

[0053] First, in step 1 of S220, a Consumer NF (e.g., SMF) (200) may transmit a request to the UPF (210) to monitor energy monitoring related information.

[0054] The message for the above request may include at least one of the following parameters:

[0055] -event id: This may contain an event id corresponding to Energy monitoring (EM) or an indicator requesting EM.

[0056] -energy monitoring parameter(s): Parameter(s) to be monitored may be included. For example, the parameters to be monitored may include energy consumption (EC) or energy consumption rate (ECR).

[0057] The above EC may represent the energy consumption for providing a service, or the energy usage for providing a service per unit time.

[0058] The above ECR may indicate an energy consumption rate or consumption speed or bitrate (e.g., UL bitrate, DL bitrate, or sum of UL / DL bitrate) for providing a service.

[0059] -target monitoring information: May contain information indicating the target of energy monitoring.

[0060] - S-NSSAI, DNN: When Consumer NF (200) requests energy monitoring for a service identified by S-NSSAI and / or DNN, it may include S-NSSAI (slice identifier information) and DNN (data network identifier information).

[0061] - N4 Session ID: When Consumer NF (200) requests energy monitoring for a specific / random / predefined PDU session, it may include the PDU session ID (PDU session identifier information) or the N4 Session ID of the PDU session (identifier information of the session between UPF and SMF for the PDU session).

[0062] - Traffic filter: When Consumer NF (200) requests energy monitoring for traffic with a specific / random / predefined destination address, it can include information such as destination IP address, destination port number, and protocol type.

[0063] -notification address: Indicates the address to receive energy monitoring notifications.

[0064] -location information: When a Consumer NF (200) requests energy monitoring for a specific / arbitrary / predefined region, location information may be included. For example, cell identifier(s), Tracking area (TA) identifier(s), geographical information (e.g., name of a specific region, etc.) may be included.

[0065] -time window: When a Consumer NF (200) requests energy monitoring for a time window, the corresponding time information may be included. For example, the corresponding time information may include a monitoring start time, a monitoring end time, or a monitoring duration.

[0066] -Reporting frequency: Can indicate the energy monitoring message notification cycle.

[0067] -EC reporting threshold: This can be included if you want to be notified when the EC reaches a certain level (e.g. threshold).

[0068] -ECR reporting threshold: You can include this if you want to be notified when ECR reaches a certain level (e.g. threshold).

[0069] In step 2 of S230, when the UPF (210) receives the message of step 1, the UPF (210) can transmit a response message to the Consumer NF (200) including at least one of the following information:

[0070] -result: Can indicate success or failure. UPF (210) can indicate success if energy monitoring is possible for the target monitoring information included in step 1 and / or for the location information and time information included in step 1.

[0071] -Transaction ID: Indicates an identifier for a connection for energy monitoring between Consumer NF (200) and UPF (210). When UPF (210) receives the message of step 1 from Consumer NF (200), UPF (210) can generate a transaction ID.

[0072] In step S240, UPF (210) can activate energy monitoring.

[0073] According to one embodiment of the present disclosure, if the message of step 1 includes a time window, UPF (210) can activate energy monitoring during the corresponding time window.

[0074] According to one embodiment of the present disclosure, when UPF (210) decides to perform energy monitoring for the request of step 1, energy monitoring can be activated for traffic for parameter(s) included in target information within UPF (210).

[0075] According to one embodiment of the present disclosure, when target information includes S-NSSAI and DNN, UPF (210) may start EC (or ECR) measurement for PDU Session(s) corresponding to the S-NSSAI and / or DNN.

[0076] According to one embodiment of the present disclosure, if the target information includes an N4 Session ID, the UPF (210) may start measuring EC (or ECR) for user plane traffic processing (e.g., packet forwarding, etc.) for the corresponding N4 Session ID.

[0077] According to one embodiment of the present disclosure, when the target information includes a traffic filter, the UPF (210) may start measuring EC (or ECR) for user plane traffic processing (e.g., packet forwarding, etc.) among packet detection rule(s) (PDRs).

[0078] In step 3 of S250, if energy monitoring is activated in S240, UPF (210) may decide to transmit a notification message to Consumer NF (200) based on the information included in the message received in step 1.

[0079] According to one embodiment of the present disclosure, UPF (210) can transmit notification messages for energy monitoring periodically or based on events.

[0080] According to one embodiment of the present disclosure, when a reporting frequency exists for energy monitoring, UPF (210) can transmit a notification message based on the corresponding cycle.

[0081] According to one embodiment of the present disclosure, when an EC reporting threshold exists for energy monitoring, the UPF (210) can transmit a notification message when the EC reaches the EC reporting threshold.

[0082] According to one embodiment of the present disclosure, when an ECR reporting threshold exists for energy monitoring, the UPF (210) can transmit a notification message when the ECR reaches the ECR reporting threshold.

[0083] According to one embodiment of the present disclosure, if the message received in step 1 includes at least one of a reporting frequency, an EC reporting threshold, or an ECR reporting threshold, the UPF (210) may determine when to transmit a notification message based on at least one of the reporting frequency, the EC reporting threshold, or the ECR reporting threshold.

[0084] According to one embodiment of the present disclosure, if the message received in step 1 does not include a reporting frequency, an EC reporting threshold, or an ECR reporting threshold, the UPF (210) may determine when to transmit a notification message based on at least one of a preset reporting frequency, an EC reporting threshold, or an ECR reporting threshold.

[0085] According to one embodiment of the present disclosure, the UPF (210) may include the following information in a notification message transmitted to the Consumer NF (200):

[0086] -transaction ID: Indicates an identifier for the connection for energy monitoring between Consumer NF (200) and UPF (210).

[0087] -energy monitoring result:

[0088] - Depending on the energy monitoring request, EC or ECR or both EC and ECR may be included.

[0089] - May contain information indicating that the ECR reporting threshold or EC reporting threshold has been reached.

[0090] After receiving an energy monitoring notification message containing EC or ECR, the Consumer NF (e.g., SMF) (200) may decide to limit the allowable bit rate, etc. for energy monitoring target traffic (e.g., traffic for information included in the target information of step 1) when the EC or ECR reaches a predefined total EC threshold or total ECR threshold.

[0091] Meanwhile, FIG. 3 is a diagram illustrating a method for performing energy monitoring in a RAN according to one embodiment of the present disclosure.

[0092] First, in step 1 of S320, a Consumer NF (e.g., AMF) (300) may transmit a request to RAN (310) to monitor energy monitoring related information.

[0093] The message for the above request may include at least one of the following parameters:

[0094] -event id: This may contain an event id corresponding to Energy monitoring (EM) or an indicator requesting EM.

[0095] -energy monitoring parameter(s): Parameter(s) to be monitored may be included. For example, the parameters to be monitored may include energy consumption (EC) or energy consumption rate (ECR).

[0096] The above EC may represent the energy consumption for providing a service, or the energy usage for providing a service per unit time.

[0097] The above ECR may indicate an energy consumption rate or consumption speed or bitrate (e.g., UL bitrate, DL bitrate, or sum of UL / DL bitrate) for providing a service.

[0098] -target monitoring information: May contain information indicating the target of energy monitoring.

[0099] - S-NSSAI, DNN: When Consumer NF (300) requests energy monitoring for a service identified by S-NSSAI and / or DNN, it may include S-NSSAI (slice identifier information) and DNN (data network identifier information).

[0100] - PDU Session ID: When Consumer NF (300) requests energy monitoring for a specific / random / predefined PDU session, it may include a PDU session ID.

[0101] - Traffic filter: When Consumer NF (300) requests energy monitoring for traffic with a specific / random / predefined destination address, it can include information such as destination IP address, destination port number, and protocol type.

[0102] -notification address: Indicates the address to receive energy monitoring notifications.

[0103] -location information: When a Consumer NF (300) requests energy monitoring for a specific / arbitrary / predefined region, location information may be included. For example, cell identifier(s), Tracking area (TA) identifier(s), geographical information (e.g., name of a specific region, etc.) may be included.

[0104] -time window: When a Consumer NF (300) requests energy monitoring for a time window, the corresponding time information may be included. For example, the corresponding time information may include a monitoring start time, a monitoring end time, or a monitoring duration.

[0105] -Reporting frequency: Can indicate the energy monitoring message notification cycle.

[0106] -EC reporting threshold: This can be included if you want to be notified when the EC reaches a certain level (e.g. threshold).

[0107] -ECR reporting threshold: You can include this if you want to be notified when ECR reaches a certain level (e.g. threshold).

[0108] In step 2 of S330, when the RAN (310) receives the message of step 1, the RAN (310) may transmit a response message to the Consumer NF (300) including at least one of the following information:

[0109] -result: Can indicate success or failure. RAN (310) can indicate success if energy monitoring is possible for the target monitoring information included in step 1 and / or for the location information and time information included in step 1.

[0110] -Transaction ID: Indicates an identifier for a connection for energy monitoring between Consumer NF (300) and RAN (310). When RAN (310) receives the message of step 1 from Consumer NF (300), RAN (310) can generate a transaction ID.

[0111] At step S340, RAN (310) may activate energy monitoring.

[0112] According to one embodiment of the present disclosure, if the message of step 1 includes a time window, the RAN (310) may activate energy monitoring during the corresponding time window.

[0113] According to one embodiment of the present disclosure, when the RAN (310) decides to perform energy monitoring for the request of step 1, energy monitoring may be activated for traffic for the parameter(s) included in the target information within the RAN (310).

[0114] According to one embodiment of the present disclosure, when target information includes S-NSSAI and DNN, RAN (310) may start EC (or ECR) measurement for PDU Session(s) corresponding to the S-NSSAI and / or DNN.

[0115] According to one embodiment of the present disclosure, when the target information includes a PDU Session ID, the RAN (310) may start measuring EC (or ECR) for user plane traffic processing (e.g., packet forwarding, etc.) for the corresponding PDU Session ID and / or energy used for transmitting / receiving traffic for the corresponding PDU Session ID (e.g., energy used during wireless communication, etc.).

[0116] According to one embodiment of the present disclosure, when target information includes a traffic filter, the RAN (310) may start measuring EC (or ECR) for user plane traffic processing (e.g., packet forwarding, etc.) for the traffic filter and / or energy used for transmitting / receiving traffic (e.g., energy used during wireless communication, etc.).

[0117] In step 3 of S350, if energy monitoring is activated in S340, RAN (310) may decide to transmit a notification message to Consumer NF (300) based on the information included in the message received in step 1.

[0118] According to one embodiment of the present disclosure, the RAN (310) may transmit notification messages for energy monitoring periodically or based on events.

[0119] According to one embodiment of the present disclosure, when a reporting frequency exists for energy monitoring, the RAN (310) can transmit a notification message based on the corresponding cycle.

[0120] According to one embodiment of the present disclosure, when an EC reporting threshold exists for energy monitoring, the RAN (310) may transmit a notification message when the EC reaches the EC reporting threshold.

[0121] According to one embodiment of the present disclosure, when an ECR reporting threshold exists for energy monitoring, the RAN (310) may transmit a notification message when the ECR reaches the ECR reporting threshold.

[0122] According to one embodiment of the present disclosure, if the message received in step 1 includes at least one of a reporting frequency, an EC reporting threshold, or an ECR reporting threshold, the RAN (310) may determine when to transmit a notification message based on at least one of the reporting frequency, the EC reporting threshold, or the ECR reporting threshold.

[0123] According to one embodiment of the present disclosure, if the message received in step 1 does not include a reporting frequency, an EC reporting threshold, or an ECR reporting threshold, the RAN (310) may determine when to transmit a notification message based on at least one of a preset reporting frequency, an EC reporting threshold, or an ECR reporting threshold.

[0124] According to one embodiment of the present disclosure, the RAN (310) may include the following information in a notification message transmitted to the Consumer NF (300):

[0125] -transaction ID: Indicates an identifier for a connection for energy monitoring between Consumer NF (300) and RAN (310).

[0126] -energy monitoring result:

[0127] - Depending on the energy monitoring request, EC or ECR, or both EC and ECR may be included.

[0128] - May contain information indicating that the ECR reporting threshold or EC reporting threshold has been reached.

[0129] After receiving an energy monitoring notification message containing EC or ECR, the Consumer NF (e.g., AMF) (300) may decide to limit the allowable bit rate, etc. for energy monitoring target traffic (e.g., traffic for information included in the target information of step 1) when the EC or ECR reaches a predefined total EC threshold or total ECR threshold.

[0130] Meanwhile, FIG. 4 is a diagram illustrating a method for performing energy monitoring by S-NSSAI or DNN according to one embodiment of the present disclosure.

[0131] First, in step 1 of S401, the Consumer NF (400) may transmit a request for energy monitoring to the Energy Monitoring Function (EMF) (410). According to one embodiment, the EMF (410) may be located in the NEF, PCF, NWDAF, or OAM.

[0132] The message for the above request may contain one or more of the following information:

[0133] -event id: An event id corresponding to Energy monitoring (EM) or an indicator requesting EM may be included in the message for the request.

[0134] -energy monitoring parameter(s): Parameter(s) to be monitored may be included. For example, parameters to be monitored, such as energy consumption (EC) or energy consumption rate (ECR), may be included in the message for the request.

[0135] The above EC may represent the energy consumption for providing a service, or the energy usage for providing a service per unit time.

[0136] The above ECR may represent an energy consumption rate or consumption speed for providing a service or a bitrate for the service (e.g., UL bitrate, DL bitrate, or the sum of UL / DL bitrate).

[0137] -target monitoring information: Information indicating the target of energy monitoring may be included in the message for the above request.

[0138] - S-NSSAI, DNN or AF-service-Identifier: When the Consumer NF (400) requests energy monitoring for a service identified by S-NSSAI and / or DNN, it may include S-NSSAI (slice identifier information) and DNN (data network identifier information) in the message for the request. Instead of S-NSSAI or DNN, AF-Service-Identifier (an identifier that can identify the AF service) may be included in the message for the request.

[0139] - Traffic filter: When Consumer NF (400) requests energy monitoring for traffic with a specific / random / predefined destination address, it can include information such as destination IP address, destination port number, and protocol type in the message for the request.

[0140] -notification address: Indicates the address to receive energy monitoring notifications.

[0141] -location information: When a Consumer NF (400) requests energy monitoring for a specific / arbitrary / predefined region, the region information may be included in the message for the request. For example, cell identifier(s), Tracking area (TA) identifier(s), geographical information (e.g., name of a specific region, etc.) may be included in the message for the request.

[0142] -time window: When a Consumer NF (400) requests energy monitoring for a time window, the corresponding time information may be included in the message for the request. For example, the monitoring start time, monitoring end time, or monitoring duration may be included.

[0143] -Reporting frequency: Can indicate the energy monitoring message notification cycle.

[0144] -EC reporting threshold: This can be included if you want to be notified when the EC reaches a certain level (e.g. threshold).

[0145] -ECR reporting threshold: If you want to be notified when ECR reaches a certain level (e.g. threshold), you can include this in the message for the request.

[0146] In step 2 of S402, when EMF (410) receives the message of step 1, it can decide to perform monitoring for S-NSSAI (or DNN) included in target monitoring information.

[0147] According to one embodiment of the present disclosure, if the message of step 1 includes an AF-service-identifier, the EMF (410) can find out the corresponding S-NSSAI based on the configuration information.

[0148] EMF (410) can transmit a message for energy monitoring to SMF (420) for S-NSSAI. EMF (410) can also obtain the SMF address for S-NSSAI / DNN via UDM (145). The message for energy monitoring can include at least one of the following information:

[0149] -event id: This may contain an event id corresponding to Energy monitoring (EM) or an indicator requesting EM.

[0150] -energy monitoring parameter(s): This may include the information contained in the message received in step 1.

[0151] -target monitoring information: May contain information indicating the target of energy monitoring.

[0152] - S-NSSAI, DNN or AF-service-Identifier: When the Consumer NF (400) requests energy monitoring for a service identified by S-NSSAI and / or DNN, it may include S-NSSAI (slice identifier information) and DNN (data network identifier information) in the message for energy monitoring. Instead of S-NSSAI or DNN, AF-Service-Identifier (an identifier that can identify the AF service) may also be included.

[0153] - Traffic filter: When Consumer NF (400) requests energy monitoring for traffic with a specific destination address, it can include information such as destination IP address, destination port number, and protocol type in the message for energy monitoring.

[0154] -notification address: This can indicate the address to receive energy monitoring notifications. Here, EMF (410) can include the address to receive energy monitoring notifications in the message for energy monitoring.

[0155] -location information: Among the location information received in step 1, information about the area covered by the SMF (420) may be included. For example, cell identifier(s) and Tracking area (TA) identifier(s) may be included in the message for energy monitoring.

[0156] -time window: Information about the time window received in step 1 may be included in the message for energy monitoring.

[0157] -Reporting frequency: Can indicate the energy monitoring message notification cycle.

[0158] -EC reporting threshold: This can be included if you want to be notified when the EC reaches a certain level (e.g., threshold). For example, the EC reporting threshold received in step 1 can be included. In one embodiment, if there are multiple SMFs to which the EMF (410) transmits messages, the EC reporting threshold received in step 1 can be a value distributed by the EMF (410) to each SMF.

[0159] -ECR reporting threshold: This can be included if you want to be notified when the ECR reaches a certain level (e.g., a threshold). For example, the ECR reporting threshold received in step 1 can be included. In one embodiment, if there are multiple SMFs to which the EMF (410) transmits messages, the ECR reporting threshold received in step 1 can be a value distributed by the EMF (410) to each SMF.

[0160] In steps 3 and 4 of S403 and S404, when the SMF (420) receives the message of step 2, it can transmit a message for energy monitoring to the UPF (430). Then, the UPF (430) can transmit a response message corresponding to the message for energy monitoring to the SMF (420).

[0161] Steps 3 and 4 may refer to steps 1 and 2 of the embodiment in which Consumer NF is SMF in FIG. 2.

[0162] According to one embodiment of the present disclosure, when there are multiple UPFs (430) to which the SMF (420) transmits a message, the EC reporting threshold received by the SMF (420) in step 2 may be a value distributed to each UPF.

[0163] According to one embodiment of the present disclosure, when there are multiple UPFs (430) to which the SMF (420) transmits a message, the ECR reporting threshold received by the SMF (420) in step 2 may be a value distributed to each UPF.

[0164] In step 5 of S405, when the SMF (420) receives the response message in step 4 from the UPF (430), it may transmit a response message for step 2 to the EMF (410). The response message may include at least one of the following information.

[0165] -result: Can indicate success or failure. SMF (420) can determine success or failure based on the result included in the message received from at least one UPF (430) in step 4. For example, if a result indicating success is received for all UPFs (430), a success message can be included.

[0166] -transaction ID: This can indicate an identifier for a connection for energy monitoring between EMF (410) and SMF (420).

[0167] In step 6 of S406, EMF (410) may transmit a message for energy monitoring to AMF (440) for S-NSSAI. The message for the request may include the same information as in step 2.

[0168] In steps 7 and 8 of S407 and S408, when the AMF (440) receives the message of step 6, it may transmit an N2 message to the RAN (450). Steps 7 and 8 may refer to steps 1 and 2 of the embodiment in which the Consumer NF is an AMF in FIG. 3.

[0169] In step 9 of S409, AMF (440) may transmit a response message for step 6 to EMF (410). The response message may include at least one of the following information:

[0170] -result: Can indicate success or failure. AMF (440) can determine success or failure based on the result included in the message received from at least one RAN (450) in step 8 of S408. For example, if a result indicating success is received for all RANs, a success message can be included.

[0171] -transaction ID: Indicates an identifier for the connection for energy monitoring between EMF (410) and AMF (440).

[0172] In step 10 of S410, EMF (410) may transmit a response message for step 1 to Consumer NF (400). The response message may include at least one of the following information:

[0173] -result: Can indicate success or failure. Success or failure can be determined based on the result contained in the message received in steps 5 and 9.

[0174] -transaction ID: This can indicate an identifier for a connection for energy monitoring between Consumer NF (400) and EMF (410).

[0175] Step 11a of S411 may refer to step 3 of the embodiment in which the Consumer NF is an SMF in FIG. 2. For example, in step 11a, at least one UPF (430) may send a notification message to an SMF (420).

[0176] According to one embodiment of the present disclosure, in step 11b of S412, when the SMF (420) receives the notification message from the UPF (430), the SMF (420) may transmit a message including at least one of the following information to the EMF (410).

[0177] -transaction ID: Indicates an identifier for the connection.

[0178] -energy monitoring result:

[0179] - Depending on the energy monitoring request, EC or ECR or both EC and ECR may be included.

[0180] - May contain information indicating that the ECR reporting threshold or EC reporting threshold has been reached.

[0181] -time: May contain information about the time the EC or ECR was created.

[0182] In step 11c of S413, if the notification address received by UPF (430) from SMF (420) in step 3 includes the address of EMF (410), UPF (430) can directly transmit a notification to the EMF (410).

[0183] In step 12a of S414, reference may be made to step 3 of the embodiment in which Consumer NF is AMF in FIG. 3.

[0184] In step 12b of S415, AMF (440) may transmit a notification message to EMF (410). The notification message may include at least one of the following information.

[0185] -transaction ID: Can indicate an identifier for the connection.

[0186] -energy monitoring result:

[0187] - Depending on the energy monitoring request, EC or ECR, or both EC and ECR may be included.

[0188] -Information indicating that the ECR reporting threshold or EC reporting threshold has been reached may be included in the above notification message.

[0189] -time: The time information when the EC or ECR was created may be included in the above notification message.

[0190] In step 12c of S416, if the notification address received from AMF (440) in step 3 includes the address of EMF (410), RAN (450) can directly transmit a notification to EMF (410).

[0191] In step 13 of S417, the EMF (410) may collect notifications received from the SMF (420) (or UPF (430)) and / or AMF (440) (or RAN (450)) and send a notification to the Consumer NF (400). If the ECR included in the received notification message indicates a bitrate, the EMF (410) may derive the ECR corresponding to the bitrate included in each message based on energy-related conversion information for each bitrate (for example, 2.5 J / s is consumed in case of 1 Mbps). Then, the EMF (410) may include the converted value in a notification message sent to the Consumer NF (400).

[0192] At this time, the above notification message may be sent periodically, depending on the setting information or information included in the message of step 1.

[0193] At this time, depending on the setting information or the information contained in the message of Step 1, a notification message may be sent when a specific EC or ECR is reached.

[0194] The above notification message may include at least one of the following information:

[0195] -transaction ID: Can indicate an identifier for the connection.

[0196] -energy monitoring result:

[0197] - Depending on the energy monitoring request, either EC or ECR, or both EC and ECR, may be included in the above notification message.

[0198] -Information indicating that the ECR reporting threshold or EC reporting threshold has been reached may be included in the above notification message.

[0199] -time: The time information when the EC or ECR was created may be included in the above notification message.

[0200] Meanwhile, FIGS. 5a and 5b illustrate an energy monitoring method for QoS Flow(s).

[0201] In step 1 of S501, the Consumer NF (500) may transmit a request for energy monitoring to the Energy Monitoring Function (EMF) (510). At this time, the EMF (510) may be located in the NEF, PCF, NWDAF, or OAM.

[0202] To enable energy monitoring for newly created QoS Flow(s), the request may be transmitted in a Create message.

[0203] To enable energy monitoring for previously created QoS Flow(s), the request may be transmitted in an Update message. Transaction ID(s) identifying the existing QoS Flow(s) may be included.

[0204] The message for the above request may include at least one of the following information:

[0205] -event id: This may contain an event id corresponding to Energy monitoring (EM) or an indicator requesting EM.

[0206] -energy monitoring parameter(s): Parameter(s) to be monitored may be included. For example, energy consumption (EC) or energy consumption rate (ECR) may be included in the message for the request.

[0207] The above EC may represent the energy consumption for providing a service, or the energy usage for providing a service per unit time.

[0208] The above ECR may indicate an energy consumption rate or consumption speed or bitrate (e.g., UL bitrate, DL bitrate, or sum of UL / DL bitrate) for providing a service.

[0209] -target monitoring information: Information indicating the target to which energy monitoring is to be applied may be included in the message for the above request.

[0210] - S-NSSAI, DNN or AF-service-Identifier: When the Consumer NF (500) requests energy monitoring for a service identified by S-NSSAI and / or DNN, it may include S-NSSAI (slice identifier information) and DNN (data network identifier information). Instead of S-NSSAI or DNN, AF-Service-Identifier (an identifier that can identify the AF service) may be included in the message for the request.

[0211] - Traffic filter: When Consumer NF (500) requests energy monitoring for traffic with a specific destination address, it can include information such as destination IP address, destination port number, and protocol type.

[0212] - UE ID(s), group ID(s): The identifier(s) of the UE or the group identifier(s) representing multiple UEs may be included in the message for the request.

[0213] -notification address: You can indicate the address to receive energy monitoring notifications.

[0214] -location information: When a Consumer NF (500) requests energy monitoring for a specific / arbitrary / predefined region, the region information may be included in the message for the request. For example, cell identifier(s), Tracking area (TA) identifier(s), geographical information (e.g., name of a specific region, etc.) may be included in the message for the request.

[0215] -time window: When a Consumer NF (500) requests energy monitoring for a time window, the corresponding time information may be included in the message for the request. For example, the monitoring start time, monitoring end time, or monitoring duration may be included.

[0216] -Reporting frequency: Can indicate the energy monitoring message notification cycle.

[0217] -EC reporting threshold: This can be included if you want to be notified when the EC reaches a certain level (e.g. threshold).

[0218] -ECR reporting threshold: If you want to be notified when ECR reaches a certain level (e.g. threshold), you can include this in the message for the request.

[0219] In step 2 of S502, when EMF (510) receives the message of step 1, it can decide to perform monitoring for S-NSSAI (or DNN) included in target monitoring information.

[0220] If the message in step 1 includes an AF-service-identifier, EMF (510) can find out the corresponding S-NSSAI based on the configuration information.

[0221] EMF (510) can identify / confirm UE ID(s) to perform energy monitoring based on the target monitoring information received in step 1 above, and transmit a request message to activate energy monitoring to at least one PCF(s) (520) responsible for the corresponding UE ID(s).

[0222] The above request message may be transmitted per UE. The request message may include one or more of the following information:

[0223] -UE ID (UE IP address, SUPI, or GPSI)

[0224] -S-NSSAI, DNN

[0225] -traffic filter

[0226] -energy monitoring parameter(s) (e.g., EC or ECR), notification address, reporting frequency

[0227] In step 3 of S503, PCF (520) may decide to activate energy monitoring for a PDU session corresponding to the UE ID (if present, S-NSSAI, DNN) included in the message received in step 2, if present.

[0228] PCF (520) may decide to activate energy monitoring for EC or ECR or both EC / ECR based on the information received in step 2 above, and may transmit a message to SMF (530) to activate energy monitoring.

[0229] The message for activating the above energy monitoring may include at least one of the following information:

[0230] -SM Policy Association ID: Identifier for policy per PDU session

[0231] -energy monitoring parameter(s) (e.g., EC or ECR), notification address, reporting frequency

[0232] In step 4 of S504, when the SMF (530) receives a message for activating energy monitoring from the PCF (520), it may transmit an N4 message to the UPF (540) for activating energy monitoring. The N4 message may include at least one of the following information:

[0233] -N4 session ID: N4 session identifier per PDU session

[0234] -energy monitoring parameter(s)

[0235] -traffic filter

[0236] In step 5 of S505, if the information received from the PCF (520) includes energy monitoring parameter(s), the UPF (540) may activate energy monitoring for the PDU session (or corresponding N4 session) included in the message received in step 4.

[0237] According to one embodiment of the present disclosure, if a traffic filter does not exist in an energy monitoring request message from an SMF (530), the UPF (540) may activate energy monitoring for all UL and DL traffic corresponding to the PDU session (or corresponding N4 session).

[0238] According to one embodiment of the present disclosure, if a traffic filter exists in an energy monitoring request message from an SMF (530), the UPF (540) may activate energy monitoring for traffic corresponding to the traffic filter among the PDU sessions (or corresponding N4 sessions).

[0239] UPF (540) may transmit a response message for step 4 including the energy monitoring processing result (e.g., success or failure) to SMF (530).

[0240] In step 6 of S506, the SMF (530) may transmit an N2 message to the RAN (560) via the AMF (550) to activate energy monitoring.

[0241] In steps 7 and 8 of S507 and S508, if the message received in step 6 includes an N2 message, the AMF (550) may transmit the N2 message to the RAN (560) responsible for the PDU session included in the message received in step 6.

[0242] According to one embodiment of the present disclosure, steps 7 and 8 may refer to steps 1 and 2 of the aforementioned FIG. 3.

[0243] In step 9 of S509, AMF (550) may send a response message to SMF (530).

[0244] At step 10 of S510, SMF (530) may send a response message for step 3 to PCF (520).

[0245] In step 11 of S511, upon receiving a response message from SMF (530), PCF (520) may transmit a response message for step 2 to EMF (510). The message may include whether energy monitoring per UE was successful.

[0246] In step 12 of S512, the EMF (510) may receive the message of step 11 from one or more PCFs, and may collate the information and include it in a response message to be transmitted to the Consumer NF (500).

[0247] The above response message may include a transaction ID and whether energy monitoring processing was successful for each UE.

[0248] In step 13 of S513, when energy monitoring is activated, UPF (510) can transmit a notification message to EMF (510) via SMF (530) and PCF (520).

[0249] The part of transmitting a notification message from UPF (540) to SMF (530) can refer to step 3 in the case where Consumer NF is SMF in the aforementioned Fig. 2.

[0250] When SMF (530) receives a message from UPF (540), it can transmit a message including at least one of the following information to PCF (520).

[0251] -SM policy association ID or PDU Session ID

[0252] -energy monitoring result:

[0253] - Depending on the energy monitoring request, EC or ECR, or both EC and ECR may be included.

[0254] -The message may include information indicating that the ECR reporting threshold or EC reporting threshold has been reached.

[0255] -time: The time information when the EC or ECR was created may be included in the message.

[0256] PCF (520) can transmit a message received from SMF (530) to EMF (510). The message may include at least one of the following information:

[0257] -transaction ID

[0258] -energy monitoring result:

[0259] - Depending on the energy monitoring request, EC or ECR, or both EC and ECR may be included.

[0260] -The message may include information indicating that the ECR reporting threshold or EC reporting threshold has been reached.

[0261] -time: The time information when the EC or ECR was created may be included in the message.

[0262] In step 14 of S514, when energy monitoring is activated, RAN (530) may transmit a notification message to EMF (510) via AMF (550), SMF (530), and PCF (520).

[0263] The part of transmitting a notification message from RAN (560) to AMF (550) can refer to step 3 in FIG. 3 when Consumer NF is AMF.

[0264] When AMF (550) receives a message from RAN (560), it can transmit the following message to SMF (530).

[0265] -PDU Session ID

[0266] -energy monitoring result:

[0267] - Depending on the energy monitoring request, EC or ECR, or both EC and ECR may be included.

[0268] -The message may include information indicating that the ECR reporting threshold or EC reporting threshold has been reached.

[0269] -time: The time information when the EC or ECR was created may be included in the message.

[0270] SMF (530) can include a message received from AMF (550) in a message transmitted to EMF (510) via PCF (520).

[0271] At step 15 of S515, the EMF (510) may collate notifications received from the SMF (530) (or UPF (510)) and / or the AMF (550) (or RAN (530)), and at step 16 of S516, may send a notification to the Consumer NF (500).

[0272] At this time, depending on the setting information or the information included in the message of step 1, EMF (510) may periodically transmit a notification message.

[0273] At this time, depending on the setting information or the information included in the message of step 1, when a specific EC or ECR is reached, the EMF (510) may transmit a notification message.

[0274] The above notification message may include at least one of the following information:

[0275] -transaction ID: Indicates an identifier for the connection.

[0276] -energy monitoring result:

[0277] - Depending on the energy monitoring request, it may include either per-UE EC, per-UE ECR, or both per-UE EC / ECR.

[0278] - May contain information indicating that the ECR reporting threshold or EC reporting threshold has been reached.

[0279] -time: May contain information about the time the EC or ECR was created.

[0280] In step 17 of S517, the Consumer NF (500) may adjust QoS parameters (e.g., UL bitrate and / or DL ​​bitrate of QoS Flow(s)) based on the information contained in the message received in step 16.

[0281] For example, if the message in step 16 includes information indicating that the ECR reporting threshold or EC reporting threshold has been reached, the Consumer NF (500) may reduce the bitrate for the corresponding QoS Flows or request release for some of the corresponding QoS Flows.

[0282] Meanwhile, FIG. 6 is a block diagram illustrating the structure of an entity performing a network function (NF) according to an embodiment of the present disclosure. According to an embodiment of the present disclosure, the NF entity of FIG. 6 may be an SMF entity as disclosed in FIG. 2 as a consumer NF, or an AMF entity as disclosed in FIG. 3.

[0283] Referring to FIG. 6, the NF 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.

[0284] The transceiver (610) can transmit and receive signals with other network entities. The transceiver (610) can transmit and receive messages according to an embodiment of the present disclosure, for example, with a UPF or RAN.

[0285] The control unit (620) can control the overall operation of the NF entity according to the embodiment proposed in the present invention. For example, the control unit (620) can control the signal flow between each block to perform operations according to the flowchart described above. Specifically, the control unit (620) can control to transmit a request to monitor energy monitoring-related information including at least one according to the embodiment of the present invention.

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

[0287] Meanwhile, FIG. 7 is a block diagram illustrating the structure of a device according to an embodiment of the present disclosure. For example, the device illustrated in FIG. 7 may be a device that receives a request for energy monitoring from a consumer NF, such as a UPF or RAN, and activates energy monitoring.

[0288] Referring to FIG. 7, the device may include a transceiver (710), a control unit (720), and a storage unit (730). In the present invention, the control unit may be defined as a circuit or an application-specific integrated circuit or at least one processor.

[0289] The transceiver (710) can transmit and receive signals with other network entities. The transceiver (710) can transmit and receive messages according to an embodiment of the present disclosure, for example, with SMF or AMF.

[0290] The control unit (720) can control the overall operation of the device according to an embodiment proposed in the present invention. For example, the control unit (720) can control the signal flow between each block to perform operations according to the flowchart described above. Specifically, when the control unit (720) receives a request to monitor energy monitoring-related information including at least one according to an embodiment of the present invention, the control unit (720) can control to transmit a response to the request and activate energy monitoring.

[0291] The storage unit (730) can store at least one of the information transmitted and received through the transmission and reception unit (710) and the information generated through the control unit (720).

[0292] The methods according to the embodiments described in the claims or specification of the present invention may be implemented in the form of hardware, software, or a combination of hardware and software.

[0293] When implemented in software, a computer-readable storage medium storing one or more programs (software modules) may be provided. The one or more programs stored in the computer-readable storage medium are configured for execution by one or more processors within an electronic device. The 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 the present invention.

[0294] 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 device, magnetic cassette. Or, they may be stored in a memory configured as a combination of some or all of these. In addition, each configuration memory may be included in multiple numbers.

[0295] Additionally, the program may be stored in an attachable storage device that is accessible via a communication network such as the Internet, an intranet, a local area network (LAN), a wide local area network (WLAN), a storage area network (SAN), or a combination thereof. Such a storage device may be connected to a device implementing an embodiment of the present invention via an external port. Additionally, a separate storage device on the communication network may be connected to a device implementing an embodiment of the present invention.

[0296] In the specific embodiments of the present invention described above, components included in the invention are expressed in the singular or plural form depending on the specific embodiment presented. However, the singular or plural expressions are selected to suit the presented situation for convenience of explanation, and the present invention is not limited to singular or plural components. Even components expressed in the plural form may be composed of singular elements, or even components expressed in the singular form may be composed of plural elements.

[0297] While the detailed description of the present invention has described specific embodiments, it is clear that various modifications are possible without departing from the scope of the present invention. Therefore, the scope of the present invention should not be limited to the described embodiments, but should be defined not only by the scope of the following claims but also by equivalents thereof.

Claims

1. A method performed by a first entity for collecting information on energy consumption in a wireless communication system, A step of receiving a request message for collecting information on energy consumption from a second entity; A step for sending a message for energy monitoring to a session management function (SMF) entity; A step of receiving a response message for energy monitoring from the SMF entity; and A method comprising: a step of transmitting a response message including an energy monitoring result as a response to a request message for collecting information on the energy consumption; 2. In paragraph 1, A method characterized in that when a message for energy monitoring is transmitted from the SMF entity to the user plane function (UPF), and a response message is transmitted from the UPF to the SMF in response to the message for energy monitoring, a response message for the energy monitoring is received from the SMF entity.

3. In paragraph 1, The request message for collecting information on the above energy consumption is: A method characterized by including information on criteria for collecting information on energy consumption.

4. In paragraph 1, Upon receiving the above request message, a step of transmitting a request message requesting information about the SMF to unified data management (UDM); and A method characterized by further comprising: a step of obtaining information about the SMF based on the request message from the UDM; 5. In paragraph 1, The response message including the above energy monitoring results is: A method characterized in that it is transmitted to the second entity via a network exposure function (NEF).

6. A method performed by a session management function (SMF) entity in a wireless communication system, A step of receiving a message for energy monitoring from a first entity for collecting information on energy consumption; A step of transmitting a message for energy monitoring using a user plane function (UPF); and A method comprising: a step of transmitting a response message for energy monitoring to the first entity when a response message is received from the UPF in response to the message for energy monitoring; 7. In paragraph 6, The message for the received energy monitoring is received when the first entity receives a request message for collecting information on energy consumption from the second entity, A method characterized in that the request message for collecting information on the energy consumption includes information on criteria for collecting information on energy consumption.

8. In a first entity for collecting information on energy consumption in a wireless communication system, Transmitter and receiver; and Receive a request message for collecting information on energy consumption from a second entity through the above-mentioned transceiver, The session management function (SMF) entity transmits messages for energy monitoring through the above-mentioned transceiver. Receive a response message for energy monitoring from the SMF entity through the transceiver, A first entity including a control unit that controls transmission of a response message including an energy monitoring result through the transceiver as a response to a request message for collecting information on the energy consumption; 9. In paragraph 8, A first entity characterized in that when a message for energy monitoring is transmitted from the SMF entity to the user plane function (UPF), and a response message for the energy monitoring is transmitted from the UPF to the SMF in response to the message for energy monitoring, the response message for the energy monitoring is received from the SMF entity.

10. In paragraph 8, The request message for collecting information on the above energy consumption is: A first entity characterized by including information on criteria for collecting information on energy consumption.

11. In paragraph 8, The above control unit, Upon receipt of the above request message, a request message requesting information about the SMF is transmitted to unified data management (UDM), A first entity characterized by controlling to obtain information about the SMF based on the request message from the UDM.

12. In paragraph 8, The response message including the above energy monitoring results is: A first entity characterized in that it is transmitted to the second entity via a network exposure function (NEF).

13. In a wireless communication system, for a session management function (SMF) entity, Transmitter and receiver; and Receive a message for energy monitoring from a first entity for collecting information on energy consumption through the transceiver, A message for energy monitoring is transmitted through the above transceiver using the user plane function (UPF). An SMF entity including a control unit that controls transmission of a response message for energy monitoring to the first entity through the transceiver unit when a response message is received from the UPF in response to a message for energy monitoring.

14. In paragraph 13, The message for the received energy monitoring is received when the first entity receives a request message for collecting information on energy consumption from the second entity, An SMF entity, characterized in that the request message for collecting information on the energy consumption includes information on criteria for collecting information on energy consumption.

Images